514
SYS202m2: Radio Network Controller Database — RRM Parameters USR7 SYS202m2: Radio Network Controller Database — RRM Parameters USR7 FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED © 2009 Motorola, Inc. USR7

SYS202m2 Usr7 Ver1 Rev2

Embed Size (px)

Citation preview

Page 1: SYS202m2 Usr7 Ver1 Rev2

SYS202m2: Radio Network Controller Database

— RRM Parameters USR7

SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 2: SYS202m2 Usr7 Ver1 Rev2

Copyrights

The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memoriesor other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs,including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computerprograms contained in the Motorola products described in this document may not be copied or reproduced in any manner without the expresswritten permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operationof law in the sale of a product.

Restrictions

The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/ordisclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorizedcopies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system,or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuraciesor omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any productsdescribed herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time totime in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of theapplication or use of any product or circuit described herein; neither does it convey license under its patent rights of others.

Trademarks

Motorola and the Motorola logo are registered trademarks of Motorola Inc.

M-Cell™, Taskfinder™ and Intelligence Everywhere™ are trademarks of Motorola Inc.

All other brands and corporate names are trademarks of their respective owners.

CE Compliance

The CE mark confirms Motorola Ltd’s statement of compliance withEU directives applicable to this product. Copies of the Declarationof Compliance and installation information in accordance with therequirements of EN50385 can be obtained from the local Motorolarepresentative or the CNRC help desk, contact details below:

Email: [email protected]

Tel: +44 (0) 1793 565 444

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

USR7

Page 3: SYS202m2 Usr7 Ver1 Rev2

Contents■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

SYS202m2: Radio Network Controller Database — RRM Parameters USR7General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2ETSI standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Reporting Safety Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Failure to comply with warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Specific warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Protective Equipment Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Devices sensitive to electrostatic discharge (ESD) . . . . . . . . . . . . . . . . . . . . . . . . 10Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1: UE Behaviors in Idle ModeChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Radio Resource Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Introduction to Radio Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Introduction to UE Behaviors in Idle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Cell Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Initial cell selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Stored information cell selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Cell Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Overall Cell Reselection Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Description of Cell Reselection Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Hierarchical Cell Structure (HCS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Speed Estimation for the UE for cell reselections . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Fast Speed Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Slow Speed Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

High Mobility State when HCS is not used . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Measurement Start Criteria — HCS Disabled . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Measurement Start Criteria — HCS Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Intra-Frequency and Inter-Frequency Measurement Criteria for Slow Moving UEs . . . . . . . 1-22Inter-RAT Measurements Criteria for Slow Moving UEs . . . . . . . . . . . . . . . . . . . . 1-22Intra- and inter-Frequency Measurement Criteria for UE in Fast Movement . . . . . . . . . . 1-24Inter-RAT Measurement Criteria for UE in Fast Movement . . . . . . . . . . . . . . . . . . 1-24

Cell Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26Cell Selection Criteria if HCS used (H Criteria) . . . . . . . . . . . . . . . . . . . . . . . . 1-26Cell Ranking Criteria (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26

Transient Neighbour detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28Calculation of TOn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28Calculation of Ln . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Cells Ranking Depending on Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30Scaling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32Cell Reservations and Access Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34

Cell Status and Cell Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

i

USR7

Page 4: SYS202m2 Usr7 Ver1 Rev2

Contents SYS202m2: Radio Network Controller Database — RRM Parameters USR7

Cell Status and Cell Reservation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36Function of Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36

Cell and URA Update Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38Purposes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38

Periodical Cell/URA Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40

Cell Reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42Cell System Information Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44

Set cell system information switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44Add cell measurement control system information . . . . . . . . . . . . . . . . . . . . . . . . 1-46ADD CELLMEAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48Radio Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50

Chapter 2: HSDPAChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Introduction to HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4HSDPA capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Impact on other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Realization of HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Realization of HSDPA on the RAN Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Realization of HSDPA at the CN side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6HSDPA Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Overview of HSDPA Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8HSDPA Physical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

High Speed Shared Control Channel (HS-SCCH) . . . . . . . . . . . . . . . . . . . . . . . 2-10High Speed Physical Downlink Shared Channel . . . . . . . . . . . . . . . . . . . . . . . . . 2-12High Speed dedicated Physical Control Channel (HS-DPCCH) . . . . . . . . . . . . . . . . . . 2-14

HS-DPCCH Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14HSDPA Channel Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

HS-DSCH Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Fractional — Dedicated Physical Channel (F-DPCH) . . . . . . . . . . . . . . . . . . . . . . . 2-18

Associated Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Enabling HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Enabling HSDPA at Cell Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20HSDPA Code Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Static Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22RNC-Controlled Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Increasing and Decreasing the Codes Reserved for the HS-PDSCH . . . . . . . . . . . . . . . 2-26

Increasing the Codes Reserved for the HS-PDSCH. . . . . . . . . . . . . . . . . . . . . . 2-26Decreasing the Codes Reserved for the HS-PDSCH . . . . . . . . . . . . . . . . . . . . . 2-26

NodeB-Controlled Dynamic Code Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28RNC v NodeB HS-PDSCH Dynamic Code Allocation . . . . . . . . . . . . . . . . . . . . . 2-28

Services Supported by the HS-DSCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30QoS Requirements of Different Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

QoS Parameters Mapped onto the MAC-hs Layer of the NodeB . . . . . . . . . . . . . . . 2-32QoS Mapping to SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Mapping ARP to User Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Setting Traffic Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Setting Traffic Handling Priority (THP) for Interactive Services. . . . . . . . . . . . . . . . . 2-34Mapping SPI to NodeB HSDPA Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

MAC-hs on the UTRAN Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36TRFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36HARQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

MAC-hs on the UE Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Overview of NodeB HSDPA Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40

Types of Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40Signalling of HSDPA Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

Capacity Allocation Frame Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Flow Control Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Flow Control Free Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Dynamic Flow Control Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Dynamic Flow Control Policy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

ii SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 5: SYS202m2 Usr7 Ver1 Rev2

SYS202m2: Radio Network Controller Database — RRM Parameters USR7 Contents

Adaptive Capacity Allocation Based on Uu Rate . . . . . . . . . . . . . . . . . . . . . . . . . 2-48Adaptive Adjustment of Available HSDPA Bandwidth . . . . . . . . . . . . . . . . . . . . . . . 2-50

Detection of Iub Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Iub Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52HSDPA MAC-hs Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54

Setting the Scheduling Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54Enhanced Proportional Fair (EPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56

Resource Limiting Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Overview of Transport Format Resource Control (TFRC) Selection . . . . . . . . . . . . . . . . 2-58

Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58TFRC Selection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60CQI Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62

Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62HSDPA Key Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64

Hybrid Automatic Repeat Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64HARQ Entity and Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66HSDPA Power Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68

Introduction to Cell Total Power Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68HSDPA Dynamic Power Resources Allocation . . . . . . . . . . . . . . . . . . . . . . . . 2-68

Default Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70

Chapter 3: HSUPAChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

HSUPA vs R99 DCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Key Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Impact on Radio Access Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6HSUPA Protocol Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

UE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Node B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8S-RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

HSUPA Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10E-DCH Dedicated Physical Data Channel (E-DPDCH) . . . . . . . . . . . . . . . . . . . . . . 3-12E-DCH Dedicated Physical Control Channel (E-DPCCH) . . . . . . . . . . . . . . . . . . . . . 3-14E-DCH Absolute Grant Channel (E-AGCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16E-DCH Relative Grant Channel (E-RGCH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18E-DCH HARQ Indicator Channel (E-HICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Reason for having 2 ms amd 10 ms TTIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Configuration of HSUPA Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Chapter 4: Load ControlChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Overview of Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Priorities Involved in Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

User Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8RAB Integrate Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Potential User Control (PUC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

PUC Loading Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12PUC Reselection Parameter Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Intelligent Access Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16IAC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Call Admission Control Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

QoS Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Supported Service Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Description of Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22CAC Based on Code Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Power Resource Admission Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Basic Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26Measurement Based Call Admission Control Algorithm . . . . . . . . . . . . . . . . . . . . . . 4-28Uplink Admission Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

iii

USR7

Page 6: SYS202m2 Usr7 Ver1 Rev2

Contents SYS202m2: Radio Network Controller Database — RRM Parameters USR7

Uplink CAC Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32Downlink Admission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34Downlink CAC Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36Equivalent Number of Users (ENU) Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39Node B Credit Resource Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40

NodeB Credit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40Procedure for NodeB Credit Resource Decision . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42Iub Resource Admission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44Handover User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44Rate Upsizing User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

Iub Resource Admission Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46HSDPA Cell Admission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48

Power resource admission control on HSDPA Channels . . . . . . . . . . . . . . . . . . . 4-48User Number Admission Decision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48

RRC Directed Retry Decision (DRD) and Redirection . . . . . . . . . . . . . . . . . . . . . . . 4-50DRD Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50

RRC DRD Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52Database Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52

Redirection Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54Database Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54

RAB Retry Decision Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56RAB DRD Basic Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Inter-Frequency DRD for Service Steering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58Cell Service Priorities Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58

Service Steering DRD Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

Inter-Frequency DRD for Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62Load Balancing DRD Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62

Load Balancing DRD Based on Power Resource . . . . . . . . . . . . . . . . . . . . . . . . . 4-64Algorithm 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64Algorithm 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64

Load balancing DRD based on Power Resource Procedure . . . . . . . . . . . . . . . . . . . 4-66Database Commands for Load balancing DRD based on Power Resource . . . . . . . . . . . . 4-68Load Balancing DRD Based on Code Resource . . . . . . . . . . . . . . . . . . . . . . . . . 4-70

Database Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70Relation Between Service Steering DRD and Load Balancing DRD . . . . . . . . . . . . . . . . 4-72Inter-frequency DRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74Inter-RAT DRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76Call Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78Call Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80Intra-Frequency Load Balancing (LDB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82

Algorithm Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82LDB Algorithm Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84Load Reshuffling Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86

Triggering of Basic Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86Code Resource Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88Iub Resources or Iub Bandwidth Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90

Congestion Detection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90NodeB Credit Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92Congestion Trigger Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94LDR Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96

LDR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96LDR Actions for Different Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98Inter-Frequency Load Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100

iv SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 7: SYS202m2 Usr7 Ver1 Rev2

SYS202m2: Radio Network Controller Database — RRM Parameters USR7 Contents

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100BE Rate Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102Uncontrolled Realtime QoS Renegotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104Inter-system handover in the CS domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106Inter-system handover in the PS domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108AMR Rate Reduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110

LDR Algorithm for AMR Rate Control in the Downlink . . . . . . . . . . . . . . . . . . . . . 4-110LDR Algorithm for AMR Rate Control in the Uplink . . . . . . . . . . . . . . . . . . . . . . 4-110

Code Reshuffling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112

Overload Control (OLC) Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114OLC Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114

General OLC Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116

OLC Algorithm for TF Control in the Downlink . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118OLC Algorithm for TF Control in the Uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-120Switching BE Services to Common Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122Release of some UEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124

Chapter 5: Rate Control DescriptionChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Rate Control Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Impact of AMRC/AMRC-WB on System Performance. . . . . . . . . . . . . . . . . . . . . 5-4DCCC Impact on System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Link Stability Control Algorithm Impact on System Performance. . . . . . . . . . . . . . . . 5-4

Initial Access Rate of AMRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Definition of Initial Access Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Value of Initial Access Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Controllable Mode Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

AMRC/AMRC-WB Algorithm Based on Uplink Stability . . . . . . . . . . . . . . . . . . . . . . 5-10UL Measurement and Event Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

UL Event Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12UL AMRC/AMRC-WB Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Principles of the UL AMRC/AMRC-WB Algorithm . . . . . . . . . . . . . . . . . . . . . . . 5-14Details of the UL AMRC/AMRC-WB Algorithm . . . . . . . . . . . . . . . . . . . . . . . . 5-14

UL AMRC Signalling Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16AMRC/AMRC-WB Algorithm Based on Downlink Stability. . . . . . . . . . . . . . . . . . . . . 5-18

DL Events and Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18DL AMRC Signalling Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Adaptive Multi Rate Control — Wide Band (AMRC-WB) . . . . . . . . . . . . . . . . . . . . . 5-22

AMRC-WB Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Dynamic Channel Configuration Control (DCCC) . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Algorithm Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Rate Re-allocation Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26Traffic Volume Triggering Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26Event 4a and Event 4b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

Uplink Rate Re-allocation Based on The Traffic Volume. . . . . . . . . . . . . . . . . . . . . . 5-28Associated Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

DL Rate-allocation Based on The Traffic Volume . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

Rate Reallocation Based on Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Throughput Measurement and Event Reporting. . . . . . . . . . . . . . . . . . . . . . . . 5-32

Rate Reallocation Based on Link Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Uplink Quality Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

Downlink Quality Measurement and Event Reporting . . . . . . . . . . . . . . . . . . . . . . . 5-36Downlink Quality Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Event E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

v

USR7

Page 8: SYS202m2 Usr7 Ver1 Rev2

Contents SYS202m2: Radio Network Controller Database — RRM Parameters USR7

UE State Transition Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38UE State Transition Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

HSDPA RRC State Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40Channel Switching between HS-DSCH and FACH . . . . . . . . . . . . . . . . . . . . . . 5-40Channel Switching between HS-DSCH and DCH . . . . . . . . . . . . . . . . . . . . . . . 5-40

RRC state switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42CELL_DCH to CELL_FACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

When UE State Transitions will not occur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44For BE services on the DCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44For BE services on the HS-DSCH or E-DCH . . . . . . . . . . . . . . . . . . . . . . . . . 5-44For real-time PS services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

CELL_FACH to CELL_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46CELL_PCH to URA_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48Link Stability Control Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50

Link Stability Control Algorithms for AMR/AMR-WB Services . . . . . . . . . . . . . . . . . 5-50Uplink Link Stability Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50

Downlink Link Stability Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52

Link Stability Control Algorithms for VP Services . . . . . . . . . . . . . . . . . . . . . . . . . 5-54Uplink Link Stability Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54Downlink Link Stability Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54

Link Stability Control Algorithms for BE Services . . . . . . . . . . . . . . . . . . . . . . . . . 5-56Uplink Link Stability Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56

Downlink Link Stability Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58

Chapter 6: Power ControlChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Introduction to Power Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Open Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Downlink Open Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Uplink Open Power Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Related Data base Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Related Power Control Settings — Continued . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Related Power Control Settings — Continued . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16Uplink Open-Loop Power Control on DPCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Maximum Allowed UL Transmit Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Establishment of Uplink Closed Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . 6-20

Transmit Power Control in the UL DPCCH Power Control Preamble. . . . . . . . . . . . . . 6-20Downlink Open-Loop Power Control on Dedicated Channel (DPDCH) . . . . . . . . . . . . . . 6-22Inner-Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24

The Closed Power Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24Uplink Inner-Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Single Radio Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26Downlink Inner Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28Outer Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30

Uplink Outer-Loop Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30SIR Target Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32DL Power Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34Power Balancing — Continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36

Chapter 7: Handover ControlChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Introduction to Handover Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Measurement Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Monitored List Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Detected Set Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Measurement Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Measurement Reporting Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Intra-frequency Event Driven Measurement Reporting Criteria . . . . . . . . . . . . . . . . . . 7-10Cell Individual Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Events 1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Event 1A Triggering Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

vi SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 9: SYS202m2 Usr7 Ver1 Rev2

SYS202m2: Radio Network Controller Database — RRM Parameters USR7 Contents

Event 1B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Event 1B Triggering Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Event 1C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20Event 1C Algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

Event 1D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22Event 1D Algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

Event 1J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24Event 1J Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

Intra-frequency Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Algorithm Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Intra-frequency Reporting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

Soft Handover Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28Description of SHO Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28Softer Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

Intra-frequency Hard Handover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30Inter-frequency Hard Handover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32

Overview of Inter-Frequency Hard Handover . . . . . . . . . . . . . . . . . . . . . . . . . 7-32Coverage-Based Inter-Frequency Handover Procedure. . . . . . . . . . . . . . . . . . . . . . 7-34QoS-Based Inter-Frequency Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . 7-36Load-Based Inter-Frequency Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . 7-38Speed-Based Inter-Frequency Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . 7-40Inter-frequency Handover Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42

Periodic Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42Event Triggered Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42Speed Based Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42

Calculation of Qused . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44Triggering Events 2D and 2F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46

Triggering Event 2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46Triggering Event 2F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46

Parameters for Events 2D and 2F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48Triggering of Event 2B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50Triggering of Event 2C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52Triggering of Event 1F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54Inter-Frequency Handover Compressed Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56

Compressed Mode Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56Compressed Mode Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58

Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58Compressed Mode Configuration Function (CMCF) Cell Type . . . . . . . . . . . . . . . . . . 7-60

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60Inter-Frequency Handover Decision and Execution . . . . . . . . . . . . . . . . . . . . . . . . 7-62

Coverage-Based and QoS-Based Inter-Frequency Handover Decision and Execution. . . . . 7-62Load-Based Inter-Frequency Handover Decision and Execution . . . . . . . . . . . . . . . . . 7-64

Description of Load-Based Inter-Frequency Handover Decision and Execution . . . . . . . . 7-64Intra-Frequency Handover Measurement Based on Conditional Blind Handover . . . . . . . . . 7-66

Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Speed-Based Inter-Frequency Handover Decision and Execution. . . . . . . . . . . . . . . . . 7-68

Decision and Execution of Micro Cell to Macro Cell Handover. . . . . . . . . . . . . . . . . 7-68Decision and Execution of Macro Cell to Micro Cell Handover. . . . . . . . . . . . . . . . . 7-68

Blind Handover Decision and Execution Based on Event 1F . . . . . . . . . . . . . . . . . . . 7-70Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70

Inter-RAT Hard Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72Algorithm Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72

UMTS-to-GSM Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74Coverage-based UMTS-to-GSM Handover Procedure . . . . . . . . . . . . . . . . . . . . 7-74

QoS-based UMTS-to-GSM Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 7-76Load-based UMTS-to-GSM Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 7-78Service-based UMTS-to-GSM Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . 7-80Preconditions for UMTS to GSM Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82

Overview of Preconditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82Service Handover Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82

GSM Cell Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-84Service Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-84UE Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-84Switches for UMTS to GSM Service-Based Handover. . . . . . . . . . . . . . . . . . . . . 7-84

Handover Procedures for UMTS to GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-86

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

vii

USR7

Page 10: SYS202m2 Usr7 Ver1 Rev2

Contents SYS202m2: Radio Network Controller Database — RRM Parameters USR7

UMTS to GSM Handover Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88UMTS GSM handover based on coverage . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88UMTS GSM handover based on load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88UMTS GSM handover based on service . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-88

Triggering of Events 2D and 2F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90Triggering of Event 2F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90

Triggering of Event 3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-92Triggering of Event 3C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94Handover Execution and Penalty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-96

UMTS to GSM Coverage-Based Handover - Periodical Reporting Mode . . . . . . . . . . . 7-96UMTS to GSM Coverage-Based Handover - Event Reporting Mode. . . . . . . . . . . . . . 7-96UMTS to GSM Handover Based on Load/Service . . . . . . . . . . . . . . . . . . . . . . . 7-97

Network Assisted Cell Change (NACC) from UTRAN to GERAN . . . . . . . . . . . . . . . . . 7-98Hierarchical Cell Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100HCS Handover Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102

Speed Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102HCS Handover Based on Speed Estimation . . . . . . . . . . . . . . . . . . . . . . . . . 7-102

Speed Estimation for the UE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-104Fast Speed Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-104Fast Inter-Hierarchy Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-104

Slow Speed Estimation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106Slow Inter-Hierarchy Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106

Anti-Pingpong Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-108

Chapter 8: Serving RNS Relocation (SRNSR)Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3SRNS Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

SRNS Relocation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Static Relocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Relocation Due to Hard Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Relocation Due to Cell or URA Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Relocation tion due to Cell or URA Update . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

SRNS Relocation and DSCR Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Relationship between SRNS Relocation and Handover . . . . . . . . . . . . . . . . . . . . 8-8

Static Relocation and DSCR Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

viii SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 11: SYS202m2 Usr7 Ver1 Rev2

About This Manual Version 1 Rev 2

SYS202m2: Radio Network Controller Database— RRM Parameters USR7■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1

USR7

Page 12: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 General information

General information

NOTEMotorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss orreduction in system performance arising directly or indirectly out of the failure of the customer,or any one acting on the customers behalf, to abide by the instructions, system parameters orrecommendations made in Motorola Customer Product Documentation.If this manual was obtained when attending a Motorola training course, it will not be updated oramended by Motorola. It is intended for TRAINING PURPOSES ONLY.

PurposeMotorola Technical Training manuals are intended to support the delivery of Technical Training only andare not intended to replace the use of Motorola Customer Product Documentation.

WARNINGFailure to comply with Motorola's operation, installation and maintenance instructions may, inexceptional circumstances, lead to serious injury or death.

These manuals are not intended to replace the system and equipment training offered by Motorola,although they can be used to supplement and enhance the knowledge gained through such training.

ETSI standardsThe standards in the table below are protected by copyright and are the property of the EuropeanTelecommunications Standards Institute (ETSI).

ETSI specification number

GSM 02.60 GSM 04.10 GSM 08.08

GSM 03.60 GSM 04.11 GSM 08.16

GSM 03.64 GSM 04.12 GSM 08.18

GSM 04.01 GSM 04.13 GSM 08.51

GSM 04.02 GSM 04.60 GSM 08.52

GSM 04.03 GSM 04.64 GSM 08.54

GSM 04.04 GSM 04.65 GSM 08.56

GSM 04.05 GSM 08.01 GSM 08.58

GSM 04.06 GSM 08.02 GSM 09.18

GSM 04.07 GSM 08.04 GSM 09.60

GSM 04.08 GSM 08.06

Figures from the above cited technical specifications standards are used, in this training manual, withthe permission of ETSI. Further use, modification, or redistribution is strictly prohibited. ETSI standardsare available from http://pda.etsi.org/pda/ and http://etsi.org/eds/

Structure of this manualThis manual is divided into uniquely identified and numbered chapters that, in turn, are divided intosections. Sections are not numbered, but are individually named at the top of each page, and are listedin the table of contents.

2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 13: SYS202m2 Usr7 Ver1 Rev2

General information Version 1 Rev 2

General information

Text conventionsThe following conventions are used in the Motorola cellular infrastructure manuals to represent keyboardinput text, screen output text and special key sequences.

InputCharacters typed in at the keyboard are shown like this.

Output

Messages, prompts, file listings, directories, utilities, and environmental variables

that appear on the screen are shown like this.

Special key sequencesSpecial key sequences are represented as follows:

CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.

¦ Press the pipe symbol key.

CR or RETURN Press the Return key.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3

USR7

Page 14: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Safety

SafetyThe following general safety guidelines apply to Motorola equipment:The power jack and mating plug of the power cable must meet International Electrotechnical Commission(IEC) safety standards.

NOTERefer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.

• Power down or unplug the equipment before servicing.• Using non-Motorola parts for repair could damage the equipment or void warranty. Contact Motorola

Warranty and Repair for service and repair instructions.• Portions of Motorola equipment may be damaged from exposure to electrostatic discharge. Use

precautions to prevent damage.

Electromagnetic energyRelevant standards (USA and EC) applicable when working with RF equipment are:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure toRadio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• Council recommendation of 12 July 1999 on the limitation of exposure of the general public toelectromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations.

• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on theminimum health and safety requirements regarding the exposure of workers to the risks arisingfrom physical agents (electromagnetic fields) (18th individual Directive within the meaning ofArticle 16(1) of Directive 89/391/EEC).

Reporting Safety IssuesWhenever a safety issue arises, carry out the following procedure in all instances. Ensure that all sitepersonnel are familiar with this procedure.

ProcedureWhenever a safety issue arises:

Procedure 1 Safety issue reporting

1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.

3 Report the problem directly to the Customer Network Resolution Centre,Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) andfollow up with a written report by fax, Swindon +44 (0)1793 430987 or China+86 10 68423633 (fax).

4 Collect evidence from the equipment under the guidance of the CustomerNetwork Resolution Centre.

4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 15: SYS202m2 Usr7 Ver1 Rev2

Warnings and cautions Version 1 Rev 2

Warnings and cautionsThe following describes how warnings and cautions are used in this manual and in all manuals of thisMotorola manual set.

WarningsA definition and example follow below:

Definition of WarningA warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, orill health. This includes hazards introduced during maintenance, for example, the use of adhesives andsolvents, as well as those inherent in the equipment.

Example and format

WARNINGDo not look directly into fibre optic cables or data in/out connectors. Laser radiation can comefrom either the data in/out connectors or unterminated fibre optic cables connected to data in/outconnectors.

Failure to comply with warningsObserve all warnings during all phases of operation, installation and maintenance of the equipmentdescribed in the Motorola manuals. Failure to comply with these warnings, or with specificwarnings elsewhere in the Motorola manuals, or on the equipment itself, violates safetystandards of design, manufacture and intended use of the equipment. Motorola assumes noliability for the customer's failure to comply with these requirements.

CautionsA definition and example follow below:

Definition of CautionA caution means that there is a possibility of damage to systems, software or individual items ofequipment within a system. However, this presents no danger to personnel.

Example and format

CAUTIONDo not use test equipment that is beyond its due calibration date; arrange for calibration to be carriedout.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5

USR7

Page 16: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 General warnings

General warningsObserve the following specific warnings during all phases of operation, installation and maintenance ofthe equipment described in the Motorola manuals:

• Potentially hazardous voltage.• Electric shock.• RF radiation.• Laser radiation.• Heavy equipment.• Parts substitution.• Battery supplies.• Lithium batteries,• Protective Equipment Recommendations

Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals,violates safety standards of design, manufacture and intended use of the equipment. Motorola assumesno liability for the customer's failure to comply with these requirements.

Warning labelsWarnings particularly applicable to the equipment are positioned on the equipment. Personnel workingwith or operating Motorola equipment must comply with any warning labels fitted to the equipment.Warning labels must not be removed, painted over or obscured in any way.

Specific warningsSpecific warnings used throughout the Technical Training manual set are shown below, and will beincorporated into procedures as applicable.These must be observed by all personnel at all times when working with the equipment, as must anyother warnings given in text, in the illustrations and on the equipment. Potentially hazardous voltage

Potentially hazardous voltage

WARNINGThis equipment operates using a potentially hazardous voltage of 230 V ac single phase or 415 V acthree phase supply. To achieve isolation of the equipment from the ac supply, the ac input isolatormust be set to off and locked.

When working with electrical equipment, reference must be made to the Electricity at Work Regulations1989 (UK), or to the relevant electricity at work legislation for the country in which the equipment is used.

NOTEMotorola equipment does not utilise high voltages.

Electric shock

WARNINGDo not touch the victim with your bare hands until the electric circuit is broken.Switch off. If this is not possible, protect yourself with dry insulating material and pull or push thevictim clear of the conductor.ALWAYS send for trained first aid or medical assistance IMMEDIATELY.

In cases of low voltage electric shock (including public supply voltages), serious injuries and even death,may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop.It can also cause skin burns at the points of entry and exit of the current.In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send fortrained first aid or medical assistance IMMEDIATELY.

6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 17: SYS202m2 Usr7 Ver1 Rev2

General warnings Version 1 Rev 2

General warningsIf the casualty is also suffering from burns, treat the affected area with cold water to cool the burn untiltrained first aid or medical assistance arrives.

RF radiation

WARNINGHigh RF potentials and electromagnetic fields are present in this equipment when in operation.Ensure that all transmitters are switched off when any antenna connections have to be changed.Do not key transmitters connected to unterminated cavities or feeders.

Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure toRadio Frequency Electromagnetic Fields, 3 kHz to 300 GHz

• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10 kHzto 300 GHz).

Laser radiation

WARNINGDo not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can comefrom either the data in/out connectors or unterminated fibre optic cables connected to data in/outconnectors.

Lifting equipment

WARNINGWhen dismantling heavy assemblies, or removing or replacing equipment, a competent responsibleperson must ensure that adequate lifting facilities are available. Where provided, lifting frames mustbe used for these operations.

When dismantling heavy assemblies, or removing or replacing equipment, the competent responsibleperson must ensure that adequate lifting facilities are available. Where provided, lifting frames must beused for these operations. When equipments have to be manhandled, reference must be made to theManual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislationfor the country in which the equipment is used.

Parts substitution

WARNINGDo not install substitute parts or perform any unauthorized modification of equipment, because of thedanger of introducing additional hazards. Contact Motorola if in doubt to ensure that safety featuresare maintained.

Battery supplies

WARNINGDo not wear earth straps when working with standby battery supplies.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7

USR7

Page 18: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 General warnings

General warningsLithium batteries

WARNINGLithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium batteries mustnot be removed or replaced. Any boards containing defective lithium batteries must be returned toMotorola for repair.

Contact your local Motorola office for how to return defective lithium batteries.

Protective Equipment Recommendations

Feet and LegsIn environments that may include electrostatic build-up, wet slippery surfaces, chemical splashes orabrasives, it is recommended that safety shoes or boots with protective toe caps and penetration-resistantmid-soles are worn.

Hands and ArmsIn environments that may endure temperature extremes, risks of cuts and punctures to the skin, diseaseor contamination from chemical substances, electrical shocks or skin infections, it is recommended thatsuitable gloves, gauntlets, mitts, wristcuffs or armlets are worn.

BreathingIn environments that may exude dust, vapour, gas or be an oxygen-deficient atmosphere, it isrecommended that suitable apparatus is worn (disposable filtering facepiece or respirator, half-orfull-face respirator, air-fed helmets or breathing apparatus).

Head ProtectionIn environments where there is risk from falling or flying objects, hair entanglement or head bumping, itis recommended that a safety helmet is worn and long hair kept in some form of restraint.

EyesIn environments where the eyes are at risk of metal splash, dust, projectiles, gas and vapour radiation,it is recommended that safety spectacles, goggles, visors, or faceshields are worn.

BodyIn environments that are at risk from chemical or metal splash, spray from pressure leaks or sprayguns, impact or penetration, contaminated dust, excessive wear or entanglement of own clothing, itis recommended that conventional or disposable overalls or other specialist protective clothing is worn.

8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 19: SYS202m2 Usr7 Ver1 Rev2

General cautions Version 1 Rev 2

General cautionsObserve the following cautions during operation, installation and maintenance of the equipmentdescribed in the Motorola manuals. Failure to comply with these cautions or with specific cautionselsewhere in the Motorola manuals may result in damage to the equipment. Motorola assumes noliability for the customer's failure to comply with these requirements.

Caution labelsPersonnel working with or operating Motorola equipment must comply with any caution labels fitted tothe equipment. Caution labels must not be removed, painted over or obscured in any way.

Specific cautionsCautions particularly applicable to the equipment are positioned within the text of this manual. Thesemust be observed by all personnel at all times when working with the equipment, as must any othercautions given in text, on the illustrations and on the equipment.

Fibre optics

CAUTIONFibre optic cables must not be bent in a radius of less than 30 mm.

Static discharge

CAUTIONMotorola equipment contains CMOS devices. These metal oxide semiconductor (MOS) devices aresusceptible to damage from electrostatic charge. See the section Devices sensitive to static in thepreface of this manual for further information.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

9

USR7

Page 20: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Devices sensitive to electrostatic discharge (ESD)

Devices sensitive to electrostatic discharge (ESD)Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation thatis susceptible to damage from electrostatic discharge. Such a charge applied to the leads of the devicecould cause irreparable damage.These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulationpacking material or by use of unearthed soldering irons.MOS devices are normally despatched from the manufacturers with the leads shorted together, forexample, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam.Provided the leads are shorted it is safe to handle the device.

Special handling techniquesIn the event of one of these devices having to be replaced, observe the following precautions whenhandling the replacement:

• Always wear an earth strap which must be connected to the electrostatic point (ESP) on theequipment.

• Leave the short circuit on the leads until the last moment. It may be necessary to replace theconductive foam by a piece of wire to enable the device to be fitted.

• Do not wear outer clothing made of nylon or similar man made material. A cotton overall ispreferable.

• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work surfaceswith an anti-static cloth before starting the operation.

• All metal tools should be used and when not in use they should be placed on an earthed surface.• Take care when removing components connected to electrostatic sensitive devices. These

components may be providing protection to the device.When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible toelectrostatic damage. However PCBs should be handled with care, preferably by their edges and notby their tracks and pins, they should be transferred directly from their packing to the equipment (or theother way around) and never left exposed on the workbench.

10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 21: SYS202m2 Usr7 Ver1 Rev2

UE Behaviors in Idle Mode Version 1 Rev 2

Chapter 1

UE Behaviors in Idle Mode

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-1

USR7

Page 22: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UE Behaviors in Idle Mode

This page intentionally left blank.

1-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 23: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter ObjectivesThe student should be able to demonstrate and understanding of:

• Cell selection• HCS implications for idle mode UEs• Cell reselection• Cell reservations and access restrictions• Cell and URA update procedures

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-3

USR7

Page 24: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Radio Resource Management Overview

Radio Resource Management Overview

Introduction to Radio Resource ManagementRadio Resource Management (RRM) consists of a series of procedures designed to achieve the mostefficient utilisation of the air interface (Uu). The purpose of RRM is to:

• Guarantee Quality of Service• Maintain planned coverage• Offer high capacity

To achieve this end, the objectives of RRM can be summarises as:

• Power Control - Minimise User/Network transmission power, whilst maintaining requested Qualityof Service, to reduce interference on the system, thus increasing capacity and coverage.

• Admission and Load Control - To maintain the load of the entire system at a steady, manageablelevel

• Handover Control - maintain QoS, even when the UE moves to other cells or systems

1-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 25: SYS202m2 Usr7 Ver1 Rev2

Radio Resource Management Overview Version 1 Rev 2

Radio Resource Management Overview

Coverage

Capacity

Qua

lity

of S

ervi

ce (Q

oS)

Power Control

Admission and Load Control

Handover Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-5

USR7

Page 26: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Introduction to UE Behaviors in Idle Mode

Introduction to UE Behaviors in Idle ModeUE behaviors in idle mode refers to a series of automatic actions for obtaining a service before finding anetwork or for obtaining a better service after connecting to the network.UE behaviors in idle mode include:

• PLMN selection - Used to ensure that the PLMN selected by the UE provides subscribed services.• Cell selection and reselection - Used to ensure that the UE finds a suitable cell to camp on.• Location registration - Used for the network to trace the current status of the UE, mainly for paging

services and to check that the UE is camped on the network when the UE does not perform anyoperation for a long period.

• Paging — Used by the network to send paging messages to a UE which is in idle mode, CELL_PCHstate, or URA_PCH state.

• System information reception — The network broadcasts the network information to a UE whichcamps on the cell to control the behaviors of the UE.

After the switch-on, the UE performs the following steps:

1. Selects a PLMN;2. Select cells from this PLMN;3. Select a best cell according to the system information;4. Camp on this cell;5. Initiate a location registration.The signal strengths of both the serving cell and neighboring cells vary when the UE moves. Thereforethe UE needs to select a most suitable cell to camp on. This procedure is called cell reselection.

1-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 27: SYS202m2 Usr7 Ver1 Rev2

Introduction to UE Behaviors in Idle Mode Version 1 Rev 2

Introduction to UE Behaviors in Idle Mode

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-7

USR7

Page 28: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Selection

Cell SelectionWhen the PLMN is selected and the UE is in idle mode, the UE starts to select a cell to camp on and toobtain services.There are four states involved in cell selection:

• Camped normally;• Any cell selection;• Camped on any cell;• Connected mode.

The cell selection is of two types:

• Initial cell selection - If no cell information is stored for the PLMN, the UE starts this procedure.• Stored information cell selection — If cell information is stored for the PLMN, the UE starts this

procedure.As shown in the slide opposite, in any state, the selection of a new PLMN leads the whole procedureback to position 1.The two procedures are described as follows.

Initial cell selectionIf no cell information is stored for the PLMN, the UE starts the initial cell selection. For this procedure, theUE need not know in advance which RF channels are UTRA bearers. The UE scans all RF channels inthe UTRA band according to its capabilities to find a suitable cell of the selected PLMN. On each carrier,the UE need only search for the strongest cell. Once a suitable cell is found, this cell shall be selected.UE state transition:

1. The UE finds a suitable cell — The UE selects this cell and enters in the "Camped normally" state.After leaving this state, the UE enters the corresponding state according to No. 2 or 4 in this list.

2. The UE does not find a suitable cell — The UE enters the “Any Cell Selection” state. After leavingthis state, the UE enters the corresponding state according to No. 3 in this list.

3. The UE finds an acceptable cell — The UE enters the “Camped on any cell” state. After leavingthis state, the UE enters the corresponding state according to No. 2 or 5 in this list.

4. The UE in the state of “Camped normally” leaves idle mode — The UE enters the connectedmode.

5. The UE in the state of “Camped on any cell” leaves idle mode — The UE enters the connectedmode (emergency cells only). After leaving this state, the UE enters the corresponding stateaccording to No. 2 or 3 in this table.

Stored information cell selectionFor this procedure, the UE needs to know the central frequency information and other optional cellparameters that are obtained from the measurement control information received previously, such asscrambling codes.After this procedure is started, the UE selects a suitable cell if it finds one. Otherwise, the “Initial cellselection” procedure is triggered.

1-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 29: SYS202m2 Usr7 Ver1 Rev2

Cell Selection Version 1 Rev 2

Cell Selection

Campednormally

NASregistration

rejected

nosuitable

cellfound

InitialCell Selection

CellReselection

Cell Selectionwhen leaving

connectedmode

StoredInformation

Cell Selection

ConnectedMode

1

go here whenevera new PLMNis selected

cell informationstored for the PLMN

no cell informationstored for the PLMN

no suitablecell found

no suitablecell found

suitable cell found

no suitable cell found

suitable cell found

suitablecell selected

trigger

suitablecell found

return toidle mode

leaveidle mode

Camped onAny Cell

suitablecell found

Any CellReselection

Cell Selectionwhen leaving

connectedmode

ConnectedMode

(Emergencycalls only)

1 USIM inserted

no acceptable cell found

no acceptable cell found

an acceptable cell found

acceptablecell selected

trigger

acceptablecell found

return toidle mode

leaveidle mode

Any CellSelection

1

go here when no USIM in the UE

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-9

USR7

Page 30: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Selection Criteria

Cell Selection CriteriaCell selection and reselection information is broadcast through SIB3 in a logical cell to perform cellselection/reselection related measurement control for UEs in states other than CELL_DCH.The cell selection criteria S is fulfilled when Srxlev > 0 and Squal > 0.Squal = Qqualmeas - (Qqualmin + QqualminOffset)Qqualmeas denotes the measured quality of the received pilot signal expressed in CPICH Ec/N0. Qqualmin,denotes the minimum required quality level of the received pilot signal CPICH Ec/N0.Srxlev = Qrxlevmeas - (Qrxlevmin QrxlevminOffset) - Pcompensation

Qrxlevmeas denotes the measured pilot signal level value. Qrxlevmin denotes the minimum required RX leveli.e., the minimum required CPICH RSCP. Pcompensation = max(Maximum TX power level allowed by thenetwork an UE may use when accessing the cell on RACH - Maximum RF output power of the UE,0), toaccount for UE power limitations.Note: The signalled values QqualminOffset and QrxlevminOffset are only applied when a cell isevaluated for cell selection as a result of a periodic search for a higher priority PLMN while campednormally in a VPLMN. During this periodic search for higher priority PLMN the UE may check the Scriteria of a cell using parameter values stored from a different cell of this higher priority PLMN.The UE sorts all the cells that satisfy the S criteria and selects a suitable cell as the serving cell to campon.The parameters that effect cell selection are found in the commands ADD CELLSELRESEL or MODCELLSELRESEL and are described below.Qqualmin — Value range: -24~0.Physical unit: dB.Content: The minimum required quality level corresponding to CPICH Ec/No. The UE can camp on thecell only when the measured CPICH Ec/No is greater than the value of this parameter.Recommended value: -18.Qrxlevmin — Value range: -58~-13.Physical value range: -115~-25; step: 2 (-58:-115; -57:-113; ..., - 13:25 ).Physical unit: dBm.Content: The minimum required RX level corresponding to CPICH RSCP. The UE can camp on the cellonly when the measured CPICH RSCP is greater than the value of this parameter. Recommended value:-58.MaxAllowedUlTxPower — Value range: -50~33.Physical unit: dBm.Content: The maximum allowed uplink transmit power of a UE in the cell, which is related to the networkplanning. Content: Allowed maximum power transmitted on RACH in the cell. It is related to networkplanning.Recommended value: 21.

1-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 31: SYS202m2 Usr7 Ver1 Rev2

Cell Selection Criteria Version 1 Rev 2

Cell Selection Criteria

SIB 3

Srxlev > 0 and Squal > 0 (FDD)

Where:

Squal = Qqualmeas – Q qualmin

Srxlev = Qrxlevmeas– Qrxlevmin - Pcompensation

Pcompensation = max(maximum TX pwr of UE on RACH – max o/p of UE)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-11

USR7

Page 32: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Overall Cell Reselection Procedure

Overall Cell Reselection ProcedureThe flow chart opposite describes the overall procedure for an UE to reselect to another cell. This is quitecomplicated because of layering of different types of cells i.e. macro, micro and 2G cells. Also whetherthe UE is in fast or slow moving state.

Description of Cell Reselection FlowchartThe first stage is to calculate the S criteria for each neighbour cell that the UE detects and then filterthe neighbour cells which do not meet this criteria. The S criteria has been described earlier in the CellSelection procedure.The next step is to choose intra/inter or inter-RAT measurements according to HCS priority and speed.Then calculate the H criteria or the R criteria depending on whether the UE is fast or slow and HCS isbeing used.Finally a delay is applied to the reselection for different types of cells to prevent constant reselections ifthe RF conditions are changing rapidly.

1-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 33: SYS202m2 Usr7 Ver1 Rev2

Overall Cell Reselection Procedure Version 1 Rev 2

Overall Cell Reselection Procedure

Cell reselection start

Calculate and filter neighbours with criteria S

Choose which cells to measure according to

HCS and speed

UE speed and HCS usage

Rank all cells according to criteria R

Filter all cells according to criteria H

Rank measured cells by highest HCS priority

according to R criteria

Rank all measured cells according to R

criteria

Keep ranking during Treselection with scaling

rules

UE selects to a new cell

Non-HCS environment or fast UE within HCS

For a slow UE within HCS

Cells fulfilling H criteria

No cells fulfilling H criteria

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-13

USR7

Page 34: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Hierarchical Cell Structure (HCS)

Hierarchical Cell Structure (HCS)In a 3G network, the so-called hot spots in radio communications may appear with an increase ofsubscribers and traffic. This requires more cells to increase the network capacity. More cells andsmaller cell radius indicate that more frequent handovers of UEs take place. For a UE in fast speed,frequent reselection to a small cell can reduce call quality, increase uplink interference, and increasesignaling load, when a call is established on that cell.In this situation, Hierarchical Cell Structure (HCS) is required to divide cells into different hierarchies.The RNC supports the HCS with eight hierarchies, typically there are three Macro Cells, Micro Cells andPico Cells.The features of different cells are as follows:Macro Cell:

• Large coverage• Continuous coverage networking• Low requirement on capacity• Fast-moving environment

Micro cell:

• Densely populated areas• High requirement on capacity• Slow-moving environment

Pico cell:

• Indoor coverage• Outdoor dead-area coverage.

Where, the pico cell has the highest priority and the macro cell has the lowest priority.

PurposeAccording to speed estimation, the RNC orders the fast-moving UE to handover to the cells of lowerpriority to reduce the number of handovers, and orders the slow-moving UEs to handover to the cellsof higher priority to increase network capacity. The cells of lower priority have larger coverage, and thecells of higher priority have smaller coverage.To add a HCS cell the command ADD CELLHCS is used. Within this command is the parameter is toset the hierarchies together with parameters that are configured when setting up cell reselections. Thecell reselections parameters are covered in an other part of the course.CellId - Uniquely identifying a cellValue range: 0 to 65535 (mandatory)Content: noneRecommended value (default value): noneUseOfHcs — Indicating whether HCS is usedValue range: USED, NOT_USEDContent: noneRecommended value (default value): NOT_USEDHCSPrio — Value range: 0 to 7Content: The value 0 indicates that the cell is of lowest priority and the value 7 the highest.Recommended value (default value): 0

1-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 35: SYS202m2 Usr7 Ver1 Rev2

Hierarchical Cell Structure (HCS) Version 1 Rev 2

Hierarchical Cell Structure (HCS)

Mac ro C ell

Mic ro C ell

P ic o C ell

Large coverage

Low capacity

F ast moving

Densely populated areas

High capacity

S low moving

Indoor C overage

Outdoor dead area coverage

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-15

USR7

Page 36: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Speed Estimation for the UE for cell reselections

Speed Estimation for the UE for cell reselectionsThis section looks at the database parameters to set the speed estimation for the UE in cell reselections.

Fast Speed EstimationThe UE fast speed decision is triggered by the number of cell selections during time period TCRmaxexceeding NCR

Slow Speed EstimationWhen the number of cell selections during time period TCRmax no longer exceeds NCR the UE willcontinue monitoring neighbour cells (as described in later sections) for time duration TCrmaxHyst. If thecriteria for entering high mobility is not detected during time period TCrmaxHyst, then exit high mobilitystate.The parameters that effect the speed estimation for the UE cell reselections are found in the commandADD CELLHCS or MOD CELLHCS and are described below.TCRmax — Value range: NOT_USED, D30, D60, D120, D180, D240.Physical unit: s.Content: Max cell reselection time.Recommended value: D60.CRMaxNum — Value range: 1~16.Content: Max number of cell reselections.Recommended value: 8.TCrmaxHyst — Value range: NOT_USED, D10, D20, D30, D40, D50, D60, D70.Physical unit: s.Content: Additional time period before the UE can revert to low-mobility measurements.Recommended value: D20.

1-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 37: SYS202m2 Usr7 Ver1 Rev2

Speed Estimation for the UE for cell reselections Version 1 Rev 2

Speed Estimation for the UE for cell reselections

TCRmax = 60s

CRMaxNum = 8

TCrmaxHyst = 20sR es election

R es eletion

R es election

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-17

USR7

Page 38: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 High Mobility State when HCS is not used

High Mobility State when HCS is not usedHigh-mobility, as applied in HCS case, is also applicable in non-HCS if the parameters non-HCS_TCRmax, non-HCS_NCR and non-HCS_TCRmaxhyst are sent on the system information broadcast.If in non-HCS environment the number of cell reselections during time period non-HCS_TCRmaxexceeds non-HCS_NCR, high-mobility state has been detected.When the number of cell reselections during time period non-HCS_TCRmax no longer exceedsnon-HCS_NCR, the UE shall:

• Continue in high-mobility state.• The criteria for entering high mobility is not detected during time period non-HCS-TCrmaxHyst:

– Exit high-mobility.If the UE is in non-HCS environment and in high-mobility state, the UE shall apply the speed dependentscaling rules as defined later in this chapter.The parameters that effect the non-HCS high mobility state are found in the command ADD/MODCELLSELRESEL and are described below.NonhcsInd — Value range: CONFIGURED, NOT_CONFIGURED.Physical unit: None.Content: This parameter indicates whether the non-HCS speed estimation parameters are configured.Recommended value: None.Tcrmaxnonhcs — Value range: not used,D30,D60,D120,D180,D240.Physical value range: not used,30,60,120,180,240.Physical unit: s. Content: time for non-HCS maximum cell reselection.Recommended value: not used.Ncrnonhcs — Value range: 1~16.Physical unit: None.Content: non-HCS maximum number of cell reselection.Recommended value: 8.Tcrmaxhystnonhcs — Value range: not used,D10, D20, D30, D40, D50, D60, D70.Physical value range: not used,10, 20, 30, 40, 50, 60, 70.Physical unit: s.Content: The extra time before a UE resumes its low mobility in a non-HCS cell.Recommended value: None.

1-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 39: SYS202m2 Usr7 Ver1 Rev2

High Mobility State when HCS is not used Version 1 Rev 2

High Mobility State when HCS is not used

TCRmaxNonHCS = 60s

CRMaxNumNonHCS = 8

TCrmaxHystNonHCS = 20sR es election

R es eletion

R es election

NonhcsInd = CONFIGURED

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-19

USR7

Page 40: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Reselection

Cell ReselectionAfter selecting a cell and camping on it, the UE periodically searches for a better cell according to the cellreselection criteria. The better cell is the most suitable one for the UE to camp on and obtain services orthe one in which the operator prefers the UE to reselect.Cell reselection criteria can be adjusted by modifying cell reselection parameters according to networkoperation policies. The Hierarchical Cell Structure (HCS), if used, may affect the measurement startcriteria for cell reselection. In idle mode, the cell reselection procedure is as for initial cell selection. aswell as having the same states.

Measurement Start Criteria — HCS DisabledIf the system messages broadcast by the serving cell indicates that the HCS is disabled, theintra-frequency, inter-frequency, and inter-RAT measurement criteria are as shown by the slide opposite.Intra-frequency measurements

• If Squal > Sintrasearch, the UE does not need to start the intra-frequency measurements;• If Squal ≤ Sintrasearch, the UE starts the intra-frequency measurements;• If system messages do not contain the Sintrasearch parameter, the intra-frequency measurement

is always started.Inter-frequency measurements

• If Squal > Sintersearch, the UE does not need to start the inter-frequency measurements;• If Squal ≤ Sintersearch, the UE starts the inter-frequency measurements;• If system messages do not contain Sintrasearch, the inter-frequency measurement is always

started.Inter-RAT measurements

• If Squal > SsearchRATm, the UE does not need to start the inter-RAT measurement;• If Squal ≤ SsearchRATm, the UE starts the inter-RAT measurement;• If system messages do not contain Sintrasearch, the inter-RAT measurement is always started.

The parameters that effect the intra frequency, inter frequency and inter RAT reselection are found in theADD CELLSELRESEL or MOD CELLSELRESEL and are described below.IdleSintrasearch — Value range: {{-16~10},{127}}.Physical value range: -32~20; step: 2.Physical unit: dB.Content: A threshold for intra-frequency cell reselection in idle mode. When the quality (CPICH Ec/Nomeasured by UE) of the serving cell is lower than this threshold plus the [Qqualmin] of the cell, theintra-frequency cell reselection procedure will be started.Recommended value: None.IdleSintersearch — Value range: {{-16~10},{127}}.Physical value range: -32~20; step: 2.Physical unit: dB.Content: A threshold for inter-frequency cell reselection in idle mode. When the quality (CPICH Ec/Nomeasured by UE) of the serving cell is lower than this threshold plus the [Qqualmin]of the cell, theinter-frequency cell reselection procedure will be started.Recommended value: None.SsearchRat — Value range: {{-16~10},{127}}.Physical value range: -32~20; step: 2.Physical unit: dB.Content: A threshold for inter-RAT cell reselection. When the quality (CPICH Ec/No measured by UE) ofthe serving cell is lower than this threshold plus the [Qqualmin] of the cell, the inter-RAT cell reselectionprocedure will be started.Recommended value: None.

1-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 41: SYS202m2 Usr7 Ver1 Rev2

Cell Reselection Version 1 Rev 2

Cell ReselectionMeasurement Start Criteria — HCS Disabled

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-21

USR7

Page 42: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Measurement Start Criteria — HCS Enabled

Measurement Start Criteria — HCS EnabledWhen the HCS is enabled, the measurement criteria for the UE changes as it involves UEs selectingcells in either slow moving or fast moving state. The way the UE behaves is described in the followingsub-sections.

Intra-Frequency and Inter-Frequency Measurement Criteria for SlowMoving UEs

If Srxlev <= SsearchhcsThen measure all intra-frequency and inter-frequency cellsIf Squal > SintrasearchThen measure all intra-frequency and inter-frequency cells which have a higher HCS priority level thanthe serving cell.If Squal <= Sintrarearch which have equal or higher HCS priority level than the serving cell.If Sintrasearch is not sent for the serving cell the UE measures on all intra-frequency cells and allinter-frequency cells with a higher HCS priority than that of the serving cell.

Inter-RAT Measurements Criteria for Slow Moving UEsIf Srxlev <= SHCSRAT or Squal <= SsearchRATThen UE measures on all inter-RAT cells.If Squal > SlimitSearchRATThen UE may choose not to measure interRAT neighbour cells, if the UE does allow, then the UE willmeasure all interRAT cells that have equal or higher HCS priority level than the serving cell.If the HCS is used and the SHCSRAT is not sent for the serving cell then the UE shall measure allinterRAT neighbour cells.The parameters that effect the HCS intra frequency, inter frequency and inter RAT reselection are foundin the ADD CELLHCS or MOD CELLHCS and are described below.SsearchHCS — Value range: -53~ 45.Physical value range: -105~91; step: 2 (-53:-105; -52:-103; ..., 45:91).Physical unit: dB.Content: Threshold of HCS cell reselection in the same system.Recommended value: 0.SHCSRat — Value range: -53~ 45.Physical value range: -105~91; step: 2 (-53:-105; -52:-103; ..., 45:91).Physical unit: dB. Content: Threshold of HCS cell reselection between different systems.Recommended value: 0.SlimitSearchRat — Value range: -16~10.Physical value range: -32~20; step: 2.Physical unit: dB.Content: Limit threshold of HCS cell reselection between different systems. The UE will not startinter-RAT measurement if it detects that the quality of the serving cell is higher than this threshold.Recommended value: 0

1-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 43: SYS202m2 Usr7 Ver1 Rev2

Measurement Start Criteria — HCS Enabled Version 1 Rev 2

Measurement Start Criteria — HCS Enabled

Intra-Frequency and Inter-Frequency Measurement Criteria for Slow Moving UEs

Inter-RAT Measurements Criteria for Slow Moving UEs

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-23

USR7

Page 44: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Measurement Start Criteria — HCS Enabled

Measurement Start Criteria — HCS Enabled

Intra- and inter-Frequency Measurement Criteria for UE in Fast MovementIF Srxlevs <= SsearchHCS or if Squal <= Sintersearch, or SsearchHCS, or Sintersearch are not sent forthe serving cell THENMeasure on all intra-frequency and inter-frequency cells.ELSEMeasure intra-frequency and inter-frequency neighbouring cells, which have equal or lower HCS prioritythan serving cell.

Inter-RAT Measurement Criteria for UE in Fast MovementIF Srxlevs <= SHCS,RAT or Squal <= SSearchRAT, or SHCS,RAT or SSearchRAT are not sent for theserving cell THENUE shall measure on all inter-RAT cells.ELSEMeasure the neighbouring cells in RAT, which have an equal or lower HCS priority than the serving cell

1-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 45: SYS202m2 Usr7 Ver1 Rev2

Measurement Start Criteria — HCS Enabled Version 1 Rev 2

Measurement Start Criteria — HCS Enabled

Intra- and inter-Frequency Measurement Criteria for UE in Fast Movement

Inter-RAT Measurement Criteria for UE in Fast Movement

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-25

USR7

Page 46: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Selection Criteria

Cell Selection CriteriaThe cell reselection criteria described here is applied to intra-frequency cells, inter-frequency cells, andinter-RAT cells.If HCS is being used in a cell then precedence can be given to neighbour cells of higher priority by usingthe H criteria, if HCS is not enabled then the H criteria calculation is bypassed and only the cell rankingcriteria R is used.

Cell Selection Criteria if HCS used (H Criteria)If HCS is enabled then the H criteria will be used.Hs = Qmeas,s - QhcsHn = Qmeas,n - Qhcs,n – TOn * LnThe parameters for TOn * Ln will be discussed in following pages only Qhcs is listed here.The parameter to set the Qhcs is found in the command ADD CELLHCS unless the cell is equipped inanother Horizon RAN Controller or it is a GSM cell. In this case it is found in the ADD NRNCCELL orADD GSMCELL cell respectively.Qhcs — Value range: 0~99Content: Quality threshold of HCS cell reselection. It can be used to calculate the quality level of thespecified cell in HCS reselection H rules. Formulation: H(quality level) = Qmeas(measured quality) -Qhc(this parameter)Physical value range: When CPICH Ec/No (FDD) is used, the unit of Qhcs is dB. The mappingrelationship is as follows: 0: -24 1: -23.5 2: -23 3: -22.5 ... 45: -1.5 46: -1 47: -0.5 48: 0 49: (spare) : ...98: (spare) : 99: (spare) :When CPICH RSCP (FDD) is used, the unit of Qhcs is dBm. The mapping relationship is as follows: 0:-115 1: -114 2: -113 : 88: -27 89: -26 90: -(spare) : 91: -(spare) : : 98: -(spare) : 99: -(spare) :Recommended value (default value): 20

Cell Ranking Criteria (R)If HCS is used then the R critieria will be used to rank the neighbour cells. The same criteria applies ifHCS is not used except that the H criteria is not calculated.Rs = Qmeas,s + QhystsRn = Qmeas,n — Qoffsets,n — TOn * (1 — Ln)The parameters for TOn * (1 — Ln) will be discussed in following pages only Qhyst and Qoffset and islisted here.The parameter to change Qhyst is found in the command ADD CELLSELRESEL and is shown below.IdleQhyst1s — Value range: 0~20.Physical value range: 0~40; step: 2.Physical unit: dB.Content: The hysteresis value in idle mode for serving FDD cells in case the quality measurement forcell selection and reselection is set to CPICH RSCP. It is related to the slow fading feature of the areawhere the cell is located. The greater the slow fading variance is, the greater this parameter.Recommended value: 2.IdleQhyst2s — Value range: {{0~20},{255}}.Physical value range: 0~40; step: 2.Physical unit: dB.Content: The hysteresis value in idle mode for serving FDD cells in case the quality measurement for cellselection and reselection is set to CPICH Ec/No. It is related to the slow fading feature of the area wherethe cell is located. The greater the slow fading variance is, the greater this parameter. It is optional. If itis not configured, [Hysteresis 1] will be adopted as the value.Recommended value: Qhyst1s for idle mode.The command to set the parameters applicable to the intrafrequency neighbours, interfrequencyneighbours and gsm neighbours are found in ADD INTRAFREQNCELL/ADD INTERFREQCELL/ADDGSMNCELL respectively and are described below.IdleQoffset1sn — Offset of cell CPICH RSCP measurement value in cell selection or reselection whenthe UE is in idle modeValue range: -50 to +50Physical unit: dB

1-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 47: SYS202m2 Usr7 Ver1 Rev2

Cell Selection Criteria Version 1 Rev 2

Cell Selection CriteriaContent: This parameter is used for moving the border of a cell. The larger the value of this parameter,the lower the probability of neighboring cell selection.Recommended value (default value): 0IdleQoffset2sn — Offset of cell CPICH Ec/No measurement value in cell selection or reselection whenthe UE is in idle modeValue range: -50 to +50Physical unit: dBContent: This parameter is used for moving the border of a cell. The larger the value of this parameter,the lower the probability of neighboring cell selection.Recommended value (default value): 0

UMTS – HCS Prio = 1 (Inter)

IntraFreq UMTS HCS Prio = 0

UMTS HCS Prio = 1 (inter)

IntraFreq UMTS HCS Prio = 0

Hs = Qmeas,s - Qhcs Hn = Qmeas,n - Qhcs,n – TOn * Ln

If HCS used H criteria calculated to prioritize cells:

If HCS used or not R Criteria calculated to rank cells:

Rs = Qmeas,s + Qhysts Rn = Qmeas,n — Qoffsets,n — TOn * (1 — Ln)

Qhcs -24 to 0dB if CPICH Ec/No used or -115 to -26dBm if CPICH RSCP used

Qhyst 0 to 40dB if CPICH Ec/No or CPICH RSCP used

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-27

USR7

Page 48: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Transient Neighbour detection

Transient Neighbour detectionWhen HCS is being used there is a need to exclude neighbour cells that are only detected for shortperiods of time before becoming too weak to serve the UE. This is dealt with in the H and R criteria bythe parameters TOn and Ln.

Calculation of TOnTOn is used within the H and R criteria and can apply a temporary offset depending on whether neighbourand serving cells have a different priority and a penalty time has been served.TOn is calculated by:TOn = TEMP_OFFSETn * W(PENALTY_TIMEn – Tn)W(x) = 0 for x < 0W(x) = 1 for x >= 0The timer Tn (internal UE timer) is implemented for each neighbouring cell. Tn is started from zero whenone of the following conditions become true:

• HCS_PRIOn <> HCS_PRIOs and Qmeas>= Qhcs• HCS_PRIOn = HCS_PRIOs and

– FDD using CPICH RSCP Qmeas,n > Qmeas,s + Qoffset1s,n– FDD using Ec/No Qmeas,n > Qmeas,s + Qoffset2s,n– All other cells Qmeas,n > Qmeas,s + Qoffset1s,n

The command to set TempOffset and TPenalty applicable to the intrafrequency neighbours,interfrequency neighbours and gsm neighbours are found in ADD INTRAFREQNCELL/ADDINTERFREQCELL/ADD GSMNCELL respectively and are described below.TempOffset1 — Offset of cell CPICH RSCP measurement value in HCS cell selection or reselectionValue range: D3, D6, D9, D12, D15, D18, D21, InfinityPhysical value range: 3, 6, 9, 12, 15, 18, 21, 255Physical unit: dB Content: The larger the value of the parameter, the lower the probability for neighboringcell selection.Recommended value (default value): D3TempOffset2 — Offset of cell CPICH Ec/No measurement value in HCS cell selection or reselectionValue range: D2, D3, D4, D6, D8, D10, D12, InfinityPhysical value range: 2, 3, 4, 6, 8, 10, 12, 255Physical unit: dB Content: The larger the value of the parameter, the lower the probability for neighboringcell selection.Recommended value (default value): D2TpenaltyHcsReselect —HCS cell reselection penalty timerValue range: D0, D10, D20, D30, D40, D50, D60Physical value range: 0, 10, 20, 30, 40, 50, 60Physical unit: s Content: The larger the value of this parameter, the longer the penalty time for HCS cellreselection.Recommended value (default value): D0

Calculation of LnLn = 0 if HCS_PRIOn = HCS_PRIOsLn = 1 if HCS_PRIOn <> HCS_PRIOs

1-28 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 49: SYS202m2 Usr7 Ver1 Rev2

Transient Neighbour detection Version 1 Rev 2

Transient Neighbour detectionCalculation of TOn

TOn = TEMP_OFFSETn * W(PENALTY_TIMEn – Tn)

W(x) = 0 for x < 0 W(x) = 1 for x >= 0

Tn (internal UE timer) started from zero when:

• HCS_PRIOn <> HCS_PRIOs and Qmeas >= Qhcs

OR

• HCS_PRIOn = HCS_PRIOs and

- FDD using CPICH RSCP Qmeas,n > Qmeas,s + Qoffset1s,n

- FDD using Ec/No Qmeas,n > Qmeas,s + Qoffset2s,n

- All other cells Qmeas,n > Qmeas,s + Qoffset1s,n

TempOffset(1 or 2) - 2 to 255dB depending on whether CPICH RSCP or Ec/No used

TpenaltyHCSReselect – 0 to 60s

TEMP_OFFSETn can either be applied or removed depending on the value of W(x)

∴ If UE detects neighbour cell for less than or equal to PENALTY_TIMEn, TEMP_OFFSETn applied

Calculation of LnLn = 0 if HCS_PRIOn = HCS_PRIOs Ln = 1 if HCS_PRIOn <> HCS_PRIOs

Hn = Qmeas,n - Qhcs,n – TOn * Ln - (If Priority the same exclude TEMP_OFFSET)

Rn = Qmeas,n — Qoffsets,n — TOn * (1 — Ln) – (If Priority different exclude TEMP_OFFSET)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-29

USR7

Page 50: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cells Ranking Depending on Speed

Cells Ranking Depending on SpeedAll cells that meet the criteria S are ranked by the following method.If HCS is not used in the serving cell the UE shall perform ranking of all cells that fulfil the criterion S,among all measured cells.If HCS is used in the serving cell the UE shall perform ranking of all cells that fulfil the criterion S among.When in low-mobility:

• Measured cells, that have the highest HCS_PRIO among those cells that fulfil the criterion H >= 0.• All measured cells, not considering HCS priority levels, if no cell fulfil the criterion H >= 0.

When in high-mobility:

• All measured cells, and among these cells:– If there are cells with a lower HCS priority than the serving cell that fulfil the criterion H >= 0:

◊ From the cells that have a lower HCS priority than the serving cell, all cells that have thehighest HCS_PRIO among those cells that fulfil the criterion H >=0;

– Else:◊ If there are cells that fulfil the criterion H >= 0 with an HCS priority higher or equal to the

HCS priority of the serving cell:◊ From the cells that have an HCS priority higher or equal to the HCS priority of the

serving cell, all cells that have the lowest HCS_PRIO among those cells that fulfil thecriterion H >=0;

– Else:◊ All cells not considering HCS priority levels.

The cells are then ranked by the R criteria specified previously.

1-30 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 51: SYS202m2 Usr7 Ver1 Rev2

Cells Ranking Depending on Speed Version 1 Rev 2

Cells Ranking Depending on Speed

• If HCS not used then rank all cells fulfilling criterion S.

• If HCS used

Low Mobility

All measured cells that have the highest HCS_PRIO amongst those cells which fulfil criterion H >= 0.

If no cells fulfil H >= 0 then all measured cells not considering HCS Priority levels.

High Mobility

Find cells with a lower HCS_PRIO than the serving cell that fulfil criterion H >= 0.

All cells that fulfil H >= 0 with a HCS_PRIO higher or equal to the HCS_PRIO of the serving cell, but ranked by the lowest HCS_PRIO first.

All cells not considering HCS_PRIO

• The cells are then ranked by the R criteria specified previously

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-31

USR7

Page 52: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Scaling Rules

Scaling RulesIn all cases, the UE shall reselect the new cell, only if the following conditions are met:

• The new cell is better ranked than the serving cell during a time interval Treselection. . For HCSwhen high mobility state has not been detected, if according to the HCS rules the serving cell is notranked then all the ranked cells are considered to be better ranked than the serving cell

Additionally the UE shall apply the following scaling rules to Treselections;

• For intra-frequency cells and high mobility state not detected:– no scaling applied.

• For intra-frequency cells and high mobility state is detected:– Multiply Treselections by the IE "Speed dependent ScalingFactor for_Treselection" if sent on

system information.• For inter-frequency cells and high mobility state not detected:

– multiply Treselections by the IE "Inter-Frequency ScalingFactor for Treselection" if sent onsystem information.

• For inter-frequency cells and high mobility state is detected:– Multiply Treselections by both the IEs "Speed dependent ScalingFactor for_Treselection" if sent

on system information and "Inter-Frequency ScalingFactor for Treselection" if sent on systeminformation.

• For inter-RAT cells and high mobility state not detected:– Multiply Treselections by the IE "Inter-RAT ScalingFactor for Treselection" if sent on system

information.

• For inter-RAT cells and high mobility state is detected:– Multiply Treselections by both the IEs “Speed dependent ScalingFactor for_Treselection” if

sent on system information and “Inter-RAT ScalingFactor for Treselection" if sent on systeminformation.

In case scaling is applied to Treselections the UE shall round up the result after all scalings to the nearestsecond. In case scaling is applied to Treselections,FACH, the UE shall round up the result after allscalings to the nearest 0.2 seconds.The parameters that effect this part of the reselection database are found in the command ADD/MODCELLSELRESEL and are described below.Treselections — Value range: 0~31.Physical unit: s.Content: If the signal quality of a neighboring cell is better than the serving cell during the specified timeof this parameter, the UE will reselect the neighboring cell. It is used to avoid ping-pong reselectionbetween different cells.Recommended value: 1.SpeedDependentScalingFactor — Value range: {{{0~10},{255}}.Physical value range: 0~1; step: 0.1.Physical unit: None.Content: For a high-mobility UE, multiples this parameter by its reselection delay to reduce the reselectiondelay of the UE. This parameter is invalid when its value is 255.Recommended value: None.InterFreqTreselScalingFactor/InterRatTreselScalingFactor — Value range: {{4~19},{255}}.Physical value range: 1~4.75.step: 0.25Physical unit: None.Content: This parameter is used to increase the inter-frequency reselection delay. This parameter isinvalid when its value is 255.Recommended value: None.

1-32 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 53: SYS202m2 Usr7 Ver1 Rev2

Scaling Rules Version 1 Rev 2

Scaling Rules

Rank candidates according to Rn> Rs for Treselection x Scaling Factor using CPICH RSCP for

UTRAN FDD cells and RSSI for GSM cells

Is a GSM cell best ranked?

Is a quality measure set to CPICH Ec/No?

Use CPICH Ec/No for deriving Qmeas,s and Qmeas,n and

recalculate ranking

Reselect to GSM cell

Rank candidates according to existing

Rn > Rs

Yes

Yes

No

No

1st ranking

2nd ranking

Treselection 0 to 31s

Intra/Inter/Inter-RAT-Frequency and highmobility – Scaling factor 0 to 1

Intra-Frequency and Low mobility - no scaling factor

Inter-frequency and low mobility – Scaling factor 1 to 4.75

Inter-RAT and low mobility –Scaling factor 1 to 4.75

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-33

USR7

Page 54: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Reservations and Access Restrictions

Cell Reservations and Access RestrictionsThere are two mechanisms which allow an operator to impose cell reservations or access restrictions.The first mechanism uses indication of cell status and special reservations for control of cell selectionand re-selection procedures. The second mechanism, referred to as Access Control, prevents selectedclasses of users from sending initial access messages for load control reasons. At subscription, one ormore Access Classes are allocated to the subscriber and stored in the USIM, which are employed forthis purpose.

Cell Status and Cell ReservationCell status and cell reservations are indicated with the Cell Access Restriction Information Element inthe System Information Message by means of three Information Elements:

• Cell barred (IE type: "barred" or "not barred"),• Cell Reserved for operator use (IE type: "reserved" or "not reserved"),• Cell reserved for future extension (IE type: "reserved" or "not reserved").

When cell status is indicated as "not barred", "not reserved" for operator use and "not reserved" for futureextension (Cell Reservation Extension):

• All UEs shall treat this cell as candidate during the cell selection and cell re-selection proceduresin Idle mode and in Connected mode.

When cell status is indicated as "not barred", "not reserved" for operator use and "reserved" for futureextension (Cell Reservation Extension):

• UEs shall behave as if cell status "barred" is indicated using the value "not allowed" in the IE"Intra-frequency cell re-selection indicator" and the maximum value for Tbarred.

When cell status is indicated as "not barred" and "reserved" for operator use:

• UEs assigned to Access Class 11 or 15 shall treat this cell as candidate during the cell selection andcell re-selection procedures in Idle mode and in Connected mode if the cell belongs to the homePLMN.

• UEs assigned to an Access Class in the range 0 to 9 and 12 to 14 shall behave as if cell status"barred" is indicated using the value "not allowed" in the IE "Intra-frequency cell re-selectionindicator" and the maximum value for Tbarred.

When cell status "barred" is indicated:

• The UE is not permitted to select/re-select this cell, not even for emergency calls;• The UE shall ignore the "Cell Reserved for future extension (Cell Reservation Extension) use" IE;• The UE is not permitted to receive any MBMS services.• The UE shall select another cell according to the following rule:

– If the "Intra-frequency cell re-selection indicator" IE in Cell Access Restriction IE is set to value"allowed", the UE may select another cell on the same frequency if selection/re-selection criteriaare fulfilled:◊ If the UE is camping on another cell, the UE shall exclude the barred cell from the

neighbouring cell list until the expiry of a time interval Tbarred. The time interval Tbarredis sent via system information in a barred cell together with Cell status information in theCell Access Restriction IE.

◊ If the UE does not select another cell, and the barred cell remains to be the "best" one,the UE shall after expiry of the time interval Tbarred again check whether the status of thebarred cell has changed.

– If the "Intra-frequency cell re-selection indicator" IE is set to "not allowed" the UE shall notre-select a cell on the same frequency as the barred cell. During an ongoing emergency call,the Intra-frequency cell re-selection indicator IE" shall be ignored, i.e. even if it is set to "notallowed" the UE may select another intra-frequency cell:◊ If the barred cell remains to be the "best" one, the UE shall after expiry of the time interval

Tbarred again check whether the status of the barred cell has changed.

1-34 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 55: SYS202m2 Usr7 Ver1 Rev2

Cell Reservations and Access Restrictions Version 1 Rev 2

Cell Reservations and Access Restrictions

ADD CELLACCESSSTRICT: CellId=4096, CellReservedForOperatorUse=NOT_RESERVED, CellReservationExtension=NOT_RESERVED, IsAccessClass0Barred=NOT_BARRED, IsAccessClass1Barred=NOT_BARRED, IsAccessClass2Barred=NOT_BARRED, IsAccessClass3Barred=NOT_BARRED, IsAccessClass4Barred=NOT_BARRED, IsAccessClass5Barred=NOT_BARRED, IsAccessClass6Barred=NOT_BARRED, IsAccessClass7Barred=NOT_BARRED, IsAccessClass8Barred=NOT_BARRED, IsAccessClass9Barred=NOT_BARRED, IsAccessClass10Barred=NOT_BARRED, IsAccessClass11Barred=NOT_BARRED, IsAccessClass12Barred=NOT_BARRED, IsAccessClass13Barred=NOT_BARRED, IsAccessClass14Barred=NOT_BARRED, IsAccessClass15Barred=NOT_BARRED, IdleCellBarred=NOT_BARRED, ConnCellBarred=NOT_BARRED;

SIB 3/4 – Cell access restrictions

• Operator use barring

• SOLSA use

• Access class barring

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-35

USR7

Page 56: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Status and Cell Reservation Parameters

Cell Status and Cell Reservation ParametersThe parameters to set the Cell Status and Cell Reservation are found in the command ADDCELLACCESSSTRICT and are described below.

Function of Access ControlWhen the access restriction information is added to a cell, including cell status, cell reserved informationand access control information. With such access control configuration information, operators caneffectively avoid access channel overload. The SIMs/USIMs of all the UEs are allocated with one ofAccess Class 0~9. In addition, one or more special access classes (Access Class 11~15) might beallocated to the SIM/USIM storage information of the UEs with high priority, as shown below:

• Access Class 15 — PLMN Staff;• Access Class 14 — Emergency Services;• Access Class 13 — Public Utilities;• Access Class 12 — Security Services;• Access Class 11 — For PLMN Use.

Different from Access Class 0~9 and 11 to 15, the control information of Access Class 10 is sent to UEsby means of air interface signalling, indicating whether the UEs belonging to Access Class 0~9 or withoutIMSI can be accessed to the network in case of emergency calls. For the UEs with Access Class 11to15, they cannot initiate the emergency calls when Access Class 10 and Access Class 11 to 15 are allbarred.The UE shall ignore Access Class related cell access restrictions when selecting a cell to camp on, i.e.it shall not reject a cell for camping on because access on that cell is not allowed for any of the AccessClasses of the UE. A change of the indicated access restriction shall not trigger cell re-selection by theUE.Access Class related cell access restrictions shall be checked by the UE before sending an RRCCONNECTION REQUEST message when entering Connected Mode from UTRAN Idle mode. AccessClass related cell access restrictions, if it is sent as a part of Domain Specific Access Restrictionparameters, shall also be checked by the UE before sending INITIAL DIRECT TRANSFER message.Otherwise, cell access restrictions associated with the Access Classes shall not apply for a UE whichalready is in Connected Mode.CellReservedForOperatorUse — Indicating whether the cell is reserved for operator useValue range: RESERVED, NOT_RESERVEDContent: If [Cell barred indicator] is NOT_BARRED, and the cell is reserved for operator use, the UEsallocated with Access Class 11 or 15 in the local PLMN can select or reselect the cell. While the UEsallocated with Access Class 0~9, 12 to14 cannot select or reselect the cell.Recommended value (default value): NOT_RESERVEDCellReservationExtension — Indicating whether the cell is reserved for extensionValue range: RESERVED, NOT_RESERVEDContent: If [Cell barred indicator] is NOT_BARRED, and the cell is not reserved for operator use but forextension, the UEs regard the cell as barred.Recommended value (default value): NOT_RESERVED.IsAccessClass0 (to 15) Barred — Indicating whether the UE allocated with Access Class 1 (to 15) canbe allowed to originate access to the radio network.Value range: BARRED, NOT_BARREDContent: The UE judges whether it belongs to this access class based on the SIM/USIM.Recommended value (default value): NOT_BARREDIdleCellBarred — Cell barred indicator for SIB3Value range: BARRED, NOT_BARREDContent: When the cell status is BARRED, it indicates that the UEs are barred to select/reselect the celleven in the case of emergency calls.Recommended value (default value): noneIdleIntraFreqReselection — Intra-freq cell reselection ind for SIB3Value range: ALLOWED, NOT_ALLOWEDContent: Indicating whether the UE in idle mode is allowed to reselect another intra-frequency cell. Thisparameter is valid when [Cell barred indicator for SIB3] is BARRED. If this parameter is ALLOWED, theUE in idle mode can select another intra-frequency cell when the cell selection/reselection condition issatisfied. If this parameter is NOT_ALLOWED, the UE in idle mod cannot select another intra-frequency

1-36 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 57: SYS202m2 Usr7 Ver1 Rev2

Cell Status and Cell Reservation Parameters Version 1 Rev 2

Cell Status and Cell Reservation Parameterscell. The indicator can be neglected in case of emergency calls. For detailed information of thisparameter, refer to 3GPP TS 25.331.Recommended value (default value): ALLOWEDIdleTbarred — Time barred for SIB3[s]Value range: D10, D20, D40, D80, D160, D320, D640, D1280Physical value range: 10, 20, 40, 80, 160, 320, 640, 1280Physical unit: sContent: This parameter is valid when [Cell barred indicator] is BARRED. The time barred can beincreased or reduced in network planning based on the actual time the cell is barred.Recommended value (default value): D320The following three parameters are similar to the last three parameters described, but relate to connectedmode (Cell_FACH, Cell_PCH and URA_PCH states).ConnCellBarredConnIntraFreqReselectionConnTbarred

ADD CELLACCESSSTRICT: CELLID=4096, ……………………………………IdleCellBarred=BARRED, IdleTbarred=D320, ConnCellBarred=BARRED, ConnIntraFreqReselection=ALLOWED, ConnTbarred=D1280;

SIB 3/4 – Cell access restrictions• Cell barring

Reselect to intrafreq cell

• Intra freq reselect allowed

• Delay to barring

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-37

USR7

Page 58: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell and URA Update Procedures

Cell and URA Update ProceduresCell/URA update is used to:

• Periodically Cell or URA update;• Cell or URA update triggered by Cell or URA reselection;• Switch the RRC connection state;• Report faults and transmit information.

PurposesCell/URA update enables UTRAN to manage a UE’s behavior. It can be applied in mobility, cellreselection and paging procedures, With cell update feature, it can:

• Enable UTRAN to monitor a UE’s status in CELL_FACH, CELL_PCH or URA_PCH state byperiodical cell/URA update;

• Let UTRAN know a UE’s current camping cell after the UE re-enters the service area, while the UEis in CELL_PCH, CELL_FACH or URA_PCH state;

• Let the UTRAN know in time which cells are in the active set after cell reselection;• Trigger a UE state transition from CELL_PCH, or URA_PCH state, to CELL_FACH state when

network is paging the UE;• To let the UE which requires the uplink data transmission transit from CELL_PCH or URA_PCH

state to CELL_FACH state;• Enable a UE with radio link failure to reestablish connection;• Enable the RNC to release the RRC connection of the UE or reestablish a RLC entity in the case

of RLC unrecoverable error.

1-38 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 59: SYS202m2 Usr7 Ver1 Rev2

Cell and URA Update Procedures Version 1 Rev 2

Cell and URA Update ProceduresUE State Transition and Status of the RRC Connection

Idle Mode

UTRAN Connected Mode

Camped on a UTRAN Cell Camped on a GSM/GPRS Cell

URA_PCHCELL_PCH

CELL_DCH (with HS-DSCH)

CELL_FACH

CELL_DCH

GSM Connected

Mode

GPRS Packet Transfer

ModeCell

Reselection

UTRAN Inter-RAT Handover

GSM Handover

Establish RR Connection

Release RR Connection

Release of temporary block flow

Initiation of temporary block flowRelease RRC

connection

Release RRC connection

Establish RRC connection

Establish RRC connection

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-39

USR7

Page 60: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Periodical Cell/URA Update

Periodical Cell/URA UpdateUpon entering CELL_FACH, CELL_PCH or URA_PCH state, the UE starts the Timer 305 (T305).If T305 expires, the UE performs cell update/ura with the cause "periodical cell/ura update".Correspondingly, RNC starts T305 for the UE in CELL_FACH, CELL_PCH or URA_PCH state. Uponreceiving a CELL/URA UPDATE message with this cause, RNC restarts T305 for this UE.If T305 has expired and the UE is detected as being “out of service area” then Timer 307 (T307) is started.If T307 is stopped after the UE detects “in service area”. If T307 expires then the UE enters idle mode.Note: — When the Cell Update or URA Update message is sent Timer 302 (T302) begins, if no CellUpdate Confirm or URA Update Confirm is not received after T302 expires then the Cell Update or URAUpdate can be resent up to a counter N302 times. The value of T305 should be set T305> T302*N302.

ParametersThe parameters that effect periodical cell update are found in the command SET CONNMODETIMERand are described below.T305 — Timer 305Value range: INFINITY, D5, D10, D30, D60, D120, D360, D720Physical value range: Infinity, 5, 10, 30, 60, 120, 360, 720Physical unit: minContent: T305 is started after the UE receives CELL UPDATE CONFIRM or URA UPDATE CONFIRMin CELL_FACH, URA_PCH or CELL_PCH state. T305 is stopped after the UE enters another state.CELL UPDATE is transmitted upon the expiry of this timer if T307 is not activated and the UE detects "inservice area". Otherwise, T307 is started. Protocol default value is 30. "Infinity" means that the cell isnot updated.Recommended value (default value): D30T307 - Timer 307Value range: D5, D10, D15, D20, D30, D40, D50Physical value range: 5, 10, 15, 20, 30, 40, 50Physical unit: sContent: T307 is started after T305 has expired and the UE detects "out of service area". T307 is stoppedafter the UE detects "in service area". The UE enters idle mode upon expiry.Protocol default value is 30.Recommended value (default value): none.

1-40 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 61: SYS202m2 Usr7 Ver1 Rev2

Periodical Cell/URA Update Version 1 Rev 2

Periodical Cell/URA Update

UE idle mode

UTRAN0

Timer 305

T305 Expires and ‘in service area or…

CELL/URA_UPDATE

0

Timer 307

0

Timer 307

T307 Expires – return to idle mode

Starts T305 when UE enters CELL_FACH/ CELL_PCH or URA_PCH

T307 > T302*N302

T302 Expires – resend CELL/URA_UPDATE N302 times

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-41

USR7

Page 62: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Reselection

Cell ReselectionIf a UE in CELL_FACH or CELL_PCH state reselects a new cell, it performs cell update with the cause"cell reselection".Upon receiving a CELL UPDATE message with this cause, RNC updates the camping cell of the UE.The procedure for cell reselection is actually the same as previously described with the exception that aunique set of parameters exist for the UE re-selecting in connected mode. These are described below.The command to set the parameters applicable to the intrafrequency neighbours, interfrequencyneighbours and gsm neighbours for connected mode are found in ADD INTRAFREQNCELL/ADDINTERFREQCELL/ADD GSMNCELL respectively and are described below.ConnQoffset1sn — Offset of cell CPICH RSCP measurement value in cell selection or reselection whenthe UE is in connected modeValue range: -50 to +50Physical unit: dBContent: This parameter is used for moving the border of a cell. The larger the value of this parameter,the lower the probability of neighboring cell selection.Recommended value (default value): 0ConnQoffset2sn — Offset of cell CPICH Ec/No measurement value in cell selection or reselection whenthe UE is in connected mode Value range: -50 to +50Physical unit: dBContent: This parameter is used for moving the border of a cell. The larger the value of this parameter,the lower the probability of neighboring cell selection.Recommended value (default value): 0The parameter to change Qhyst for connected mode is found in the command ADD CELLSELRESELand is shown below.ConnQhyst1s — Value range: 0~20.Physical value range: 0~40; step: 2.Physical unit: dB.Content: The hysteresis value in connect mode for serving FDD cells in case the quality measurementfor cell selection and reselection is set to CPICH RSCP. It is related to the slow fading feature of the areawhere the cell is located. The greater the slow fading variance is, the greater this parameter.Recommended value: 2.ConnQhyst2s — Value range: {{0~20},{255}}.Physical value range: 0~40; step: 2.Physical unit: dB.Content: The hysteresis value in connect mode for serving FDD cells in case the quality measurementfor cell selection and reselection is set to CPICH RSCP. It is related to the slow fading feature of the areawhere the cell is located. The greater the slow fading variance is, the greater this parameter.Recommended value: Qhyst1s for connect mode.Qhyst1spch — Value range: {{0~40},{255}}.Physical unit: dB.Content: If different reselection parameters can be selected according to different connection modes, thisparameter indicates that in the CELL_PCH or URA_PCH connection mode, the measurement hysteresisof the UE is 1. This parameter is invalid when its value is 255.Recommended value: None.Qhyst1sfach — Value range: {{0~40},{255}}.Physical unit: dB.Content: If different reselection parameters can be selected according to different connection modes,this parameter indicates that in the CELL_FACH connection mode, the measurement hysteresis of theUE is 1. This parameter is invalid when its value is 255.Recommended value: None.Qhyst2spch — Value range: {{0~40},{255}}.Physical unit: dB.Content: If different reselection parameters can be selected according to different connection modes, thisparameter indicates that in the CELL_PCH or URA_PCH connection mode, the measurement hysteresisof the UE is 2. This parameter is optional. If it is not specified, its default value is that of the Qhyst1spchparameter. This parameter is invalid when its value is 255.Recommended value: None.Qhyst2sfach — Value range: {{0~40},{255}}.Physical unit: dB.Content: If different reselection parameters can be selected according to different connection modes,this parameter indicates that in the CELL_FACH connection mode, the measurement hysteresis of the

1-42 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 63: SYS202m2 Usr7 Ver1 Rev2

Cell Reselection Version 1 Rev 2

Cell ReselectionUE is 2. This parameter is optional. If it is not specified, its default value is that of the Qhyst1sfachparameter. This parameter is invalid when its value is 255.Recommended value: None.Treselectionspch — Value range: {{0~31},{255}}.Physical unit: s.Content: If different reselection parameters can be selected according to different connection modes,this parameter indicates the reselection hysteresis of the UE in the CELL_PCH or URA_PCH connectionmode. This parameter is invalid when its value is 255.Recommended value: None.Treselectionsfach — Value range: {{0~31},{255}}.Physical value range: 0~6.2; step: 0.2.Physical unit: s.Content: If different reselection parameters can be selected according to different connection modes,this parameter indicates the reselection hysteresis of the UE in the CELL_FACH connection mode. Thisparameter is invalid when its value is 255.Recommended value: None.

SIB 4

Intra/Inter Freq UMTS Cell

Rn > Rs for Treselection timer x Scaling Factor

Rs = Qmeas,s + Qhysts

Rn = Qmeas,n - Qoffsets,n — TOn * (1 — Ln)Separate hyst and offset values available for connected mode.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-43

USR7

Page 64: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell System Information Configuration

Cell System Information ConfigurationA normally running Horizon RAN Network Controller cell broadcasts SIB1/3/5/7/11 and optionallySIB2/4/12 and 18. Configurations of SIBs. The following system information shall also be added beforecell activation.These parameters are closely related to the cell performance. They should be added based on thenetwork planning.

Set cell system information switchADD CELLSIBSWITCH can be used to determine whether to broadcast SIB2/18 or not within a logicalcell.Operators shall specify [Cell ID] to identify the logical cell. This parameter is already set, as describedin Section "Adding Logical Cell Basic Information". Operators shall then select according to actualrequirements SIB2/4/12 or SIB18 from [System information switch].

NOTE1) Operators can use ADD CELLSIBSWITCH before cell activation to determine whether the cellshall broadcast SIB2/18 when it is activated on the air interface and use MOD CELLSIBSWITCH tomodify the switch setting.2) [System information switch] of ADD CELLSIBSWITCH and MOD CELLSIBSWITCH cannot benull.3) The SIB switches listed in [System information switch] of MOD CELLSIBSWITCH have threestates i.e., selected, cleared and grayed. When selected, the switch will be enabled. When cleared,the switch will be disabled. When grayed, the switch state will remain unchanged.

SibCfgBitMap — Value range: SIB2,SIB4,SIB12,SIB18.Content: Determining the combinations of SIBs to be broadcast in a cell.Recommended value: None.FreqBandInd — Value range: BROADCAST,NOT_BROADCAST.Content: Determining whether the frequency band indication information will be broadcast in systeminformation.Recommended value: NOT_BROADCAST.Note:

• SIB2 — Cell URA• SIB4 — Connected mode selection/reselection• SIB12 — Measurement control in connected mode• SIB18 — PLMN ID for neighbour cells

1-44 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 65: SYS202m2 Usr7 Ver1 Rev2

Cell System Information Configuration Version 1 Rev 2

Cell System Information Configuration

SIB 2, 4, 12 and 18 also Frequency Band Indicator

ADD CELLSIBSWITCH: CellId=4096, SibCfgBitMap=SIB2-1&SIB4-1&SIB12-1&SIB18-1, FreqBandInd=BROADCAST;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-45

USR7

Page 66: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Add cell measurement control system information

Add cell measurement control system informationCell measurement control system information is broadcast through SIB11 in a logical cell to performmeasurement control for UEs in other states other than CELL_DCH.This section describes the FACH measurement occasion calculation in the case of inter-frequency cellreselection. The FACH measurement occasion calculation in the case of inter-RAT cell reselection issimilar.If the inter-frequency cell reselection function is enabled, UEs need to measure the inter-frequencyneighbouring cells periodically. Such measurement has no impact on the UE in URA_PCH/CELL_PCHstate or idle mode. However, some inter-frequency measurement occasions shall be specified for the UEin CELL_FACH state because there is a service data flow between the network and the UE. Otherwise,the data flow might be interrupted.According to 3GPP TS 25.331, the FACH measurement occasion cycles every 2k×N frames. "k"represents the FACH measurement occasion period length coefficient and "N" denotes the number offrames contained in a Transmission Time Interval (TTI). Each measurement is implemented at a TTI.Generally, the greater "k" is, the longer time a certain number of inter-frequency measurements willoccupy.

• The greater "k" is, the longer the interval between two measurements will be.• If the UE can not complete all inter-frequency measurements at one TTI, the remaining cells need

be measured at the next TTI. Therefore, the greater "k" is, the longer time it will take the UE tocomplete all inter-frequency measurements.

The parameters that effect the FACH measurement occasion are found in the command ADDCELLMEAS and are described below.IntraFreqMeasInd — Value range: REQUIRE, NOT_REQUIREPhysical unit: NoneContent: Indicating whether the intra-frequency measurement control information should be deliveredthrough the system information. Generally the cell should deliver the intra-frequency measurementcontrol information.Recommended value: NoneInterFreqInterRatMeasInd — Value range: NOT_REQUIRE, INTER_FREQ,INTER_RAT,INTER_FREQ_AND_INTER_RATPhysical unit: NoneContent: Indicating whether the inter-frequency , or inter-RAT , or inter-frequency and inter-RATmeasurement control information should be delivered through the system information.Recommended value: INTER_FREQ_AND_INTER_RATFACHMeasInd — Value range: REQUIRE, NOT_REQUIREPhysical unit: NoneContent: Indicating whether the FACH measurement occasion period length coefficient should bedelivered through the system information. If inter-freq or inter-RAT measurement control informationwas broadcast through the system information, some UEs in CELL_FACH state need the FACHmeasurement occasion period length coefficient for measurement. When [Inter-freq/Inter-RAT MeasCtrl Info Ind] is set as NOT_REQUIRE, this parameter is needless.Recommended value: NoneFACHMeasOccaCycleLenCoef — Value range: 1~12Physical unit: NoneContent: The FACH measurement occasion cycle length coefficient used to inform the UE in CELL_FACHstate the time to start inter-frequency or inter-RAT measurement. Generally this parameter ranges from1 to 5. The greater this parameter is set, the more time it will take for the UE to perform inter-frequency orinter-RAT measurement. This parameter is shared by both inter-frequency and inter-RAT measurement.Recommended value: 3

1-46 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 67: SYS202m2 Usr7 Ver1 Rev2

Add cell measurement control system information Version 1 Rev 2

Add cell measurement control system information

160,320,6401,2,38

160,320,402,3,44

80,160,320,6402,3,4,52

80,160,320,6403,4,5,61

Corresponding cycle period (ms)

KN

160,320,6401,2,38

160,320,402,3,44

80,160,320,6402,3,4,52

80,160,320,6403,4,5,61

Corresponding cycle period (ms)

KN

FACH Measurement Occasion Cycle = 2k N

N = Transmission Time IntervalK = FACH Measurement Filter Coefficient

The Larger “k” The Longer the Interval Between Measurementsand

The Longer it will take a UE to Complete All Measurements(When all can’t be Completed in One TTI)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-47

USR7

Page 68: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 ADD CELLMEAS

ADD CELLMEASThe other parameters included in the ADD CELLMEAS are described below. They are such things ashow many neighbours are to be reported.RptIndInd — Value range: REQUIRE, NOT_REQUIREContent: Identifying whether UE need to report RACH SFN-SFN time different or not.RptInd — Value range: NO_REPORT, TYPE1, TYPE2Physical unit: NoneContent: NO_REPORT, indicates the UE need not measure the SFN-SFN time difference. TYPE1,indicates the UE reports the SFN-SFN time difference. TYPE2, indicates the UE reports the CPICH RXtime difference between two cells. Refer to TS25.215.Recommended value: NoneMaxNumRptCellsInd — Value range: REQUIRE, NOT_REQUIREContent: Identifying whether UE need to report neighbouring cell or not.MaxNumRptCells — Value range: NO_REPORT, CURRENT_CELL,CURRENT_CELL_AND_BEST_NEIGHBOUR,CURRENT_CELL_AND_2BEST_NEIGHBOUR,CURRENT_CELL_AND_3BEST_NEIGHBOUR,CURRENT_CELL_AND_4BEST_NEIGHBOUR,CURRENT_CELL_AND_5BEST_NEIGHBOUR,CURRENT_CELL_AND_6BEST_NEIGHBOURPhysical unit: NoneContent: The maximum number of neighboring cells that can be contained in the UE RACH report.Recommended value: None

1-48 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 69: SYS202m2 Usr7 Ver1 Rev2

ADD CELLMEAS Version 1 Rev 2

ADD CELLMEAS

Intra/Inter Freq UMTS or GSM Cell

Serving Cell

ADD CELLMEAS: CELLID=4096, INTRAFREQMEASIND=REQUIRE, INTERFREQINTERRATMEASIND=INTER_FREQ_AND_INTER_RAT, MEASID=1, FILTERCOEF=D8, RPTIND=TYPE1, MAXNUMRPTCELLS=CURRENT_CELL_AND_6BEST_NEIGHBOUR, FACHMEASIND=REQUIRE, FACHMEASOCCACYCLELENCOEF=5;

Intra freq

Inter freq

Inter RAT

Measurements to be taken Averaging parameters Number of neighbours to be measured

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-49

USR7

Page 70: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Radio Link Failure

Radio Link FailureIf a UE in CELL_DCH state detects that the criteria for radio link failure are met, it performs cell updatewith the cause "radio link failure".Upon receiving a CELL UPDATE message with this cause, RNC deletes the current radio link,reestablishes a new radio link, and sends a CELL UPDATE CONFIRM to the UE with the parameters ofthe new radio link. Then the UE can re-establish connection on the new radio link.The parameters that effect the radio link failure and attempted recovery are found in the SETCONNMODETIMER command and are described below.T313 — Timer 313Value range: 0~15Physical unit: sContent: T313 is started after the UE detects N313 consecutive "out of sync" indications from L1. T313is stopped after the UE detects N315 consecutive "in sync" indications from L1. It indicates Radio Link(RL) failure upon expiry.Recommended value (default value): 3N313 — Constant 313Value range: D1, D2, D4, D10, D20, D50, D100, D200Physical value range: 1, 2, 4, 10, 20, 50, 100, 200Content: maximum number of consecutive "out of sync" indications received from L1Recommended value (default value): D50N315 — Constant 315Value range: D1, D2, D4, D10, D20, D50, D100, D200, D400, D600, D800, D1000Physical value range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000Content: maximum number of consecutive "in sync" indications received from L1 when T313 is activated.Recommended value (default value): D1

1-50 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 71: SYS202m2 Usr7 Ver1 Rev2

Radio Link Failure Version 1 Rev 2

Radio Link Failure

UMTS Cell

UE in CELL_DCH

The quality is checked every

radio frame (10ms)

0

Timer 313

If checked quality is below the threshold for 160ms (out of sync) then start:

If N313 ‘out of sync’ messages received within T313 then UE send Cell Update Message with CV ‘radio link fail’.

Or

If N315 ‘in sync’ messages received within T313 then UE maintains the radio link.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

1-51

USR7

Page 72: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Radio Link Failure

This page intentionally left blank.

1-52 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 73: SYS202m2 Usr7 Ver1 Rev2

HSDPA Version 1 Rev 2

Chapter 2

HSDPA

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-1

USR7

Page 74: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA

This page intentionally left blank.

2-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 75: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter Objectives

• Introduce HSDPA• Describe the technical implementation of HSDPA• Show how HSDPA is implemented

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-3

USR7

Page 76: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Introduction to HSDPA

Introduction to HSDPAHigh Speed Downlink Packet Access (HSDPA) is an important feature of the 3GPP R5. As a downlinkhigh-speed data transmission solution, its user maximum rate over the air interface is 14.4 Mbit/s atUSR7.The main features of HSDPA are as follows:

• The frames transmitted over the air interface are 2 ms;• The HARQ and AMC technologies are applied by the physical layer;• High order 16 QAM modulation mode is used to improve spectral efficiency;• Both code division and time division are used to schedule UEs.

PurposeHSDPA improves the performance of UMTS network in the following aspects:

• Higher DL peak transmission rate: the highest rate reaches 14.4 Mbit/s;• Shorter service delay: providing a faster service experience to the subscribers, for example in

receiving e-mails and browsing web pages;• More efficient DL codes and power utilization: for macro cell coverage, the capacity is 50% higher;

for micro cell coverage, the capacity is 200%–300% or higher.

HSDPA capabilitiesThe HSDPA capabilities are as follows:

• Peak rate per cell: 14.4 Mbit/s• Peak rate per user: 14.4 Mbit/s• Maximum number of users per cell: 64• Multiple RABs: 3 PS RABs• SRB over HSDPA• HSDPA over Iur• VoIP over HSPA• IMS signalling over HSPA• HS-DPCCH Preamble• F-DPCH

Impact on other FeaturesThe impact of HSDPA on the other Motorola UMTS RAN features are as follows:

• HSDPA does not prevent the other features from taking effect.• The realization of HSDPA needs the support of power control, load control, admission control, and

mobility management.• HSDPA and the other features have interactive influences on each other. For details see the

relevant chapters in this manual i.e. Load Control.

2-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 77: SYS202m2 Usr7 Ver1 Rev2

Introduction to HSDPA Version 1 Rev 2

Introduction to HSDPA

RNCRNCCNCN

Iu

Iub

NodeB

• 2ms Frames

• HARQ

• AMC

• 16QAM

14.4 Mbps Per Cell

14.4 Mbps Per User

Maximum of 64 HSDPA users per cell

HSDPA Capabilities

• Multiple RABs: 3 PS RABs

• SRB over HSDPA

• HSDPA over Iur

• VOIP over HSPA

• IMS signalling over HSPA

• HS-DPCCH Preamble

• F-DPCH

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-5

USR7

Page 78: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Realization of HSDPA

Realization of HSDPAHSDPA is realized in the RAN, CN and changes in the protocol stack.

Realization of HSDPA on the RAN SideThe feature of HSDPA is realized through enhancing the functions of the access stratum:

• Adding MAC-hs and HSDPA physical layer processing on both the UE and the NodeB sides.• Transmitting the user plane data flow through the HS-DSCH FP between the SRNC, CRNC, and

NodeB.

Realization of HSDPA at the CN sideBecause the UTRAN supports higher transmission rate, the PS domain needs to support higher rate ofservice assignment and user plane transmission and switching.

HSDPA Protocol StackThe MAC-hs are added on both the UE and NodeB sides after HSDPA is introduced.HSDPA data and control frames on the SRNC side are transmitted to the MAC-hs of NodeB in thefollowing two ways:

• Through Iub when the SRNC and the CRNC are the same.• Through lur and then Iub when the SRNC and the CRNC are different.

HSDPA Protocol Stack Model when the SRNC and the CRNC are the sameThe following points describe the above:

1. The MAC-d of the SRNC sends the MAC-d PDUs through FP to the MAC-hs of the NodeB.2. The MAC-hs of the NodeB completes the scheduling of the data between the UEs that camp on

the HSDPA cells.3. The MAC-hs of the NodeB sends the MAC-hs PDU through Uu interface to the equivalent MAC-hs

of the UE.

HSDPA Protocol Stack Model when the SRNC and the CRNC are the differentThe following points describe the above:

1. The MAC-d of the SRNC sends the MAC-d PDUs through FP to the MAC-hs of the CRNC.2. The MAC-c/sh is required to transfer MAC-d PDUs to NodeB through HS-DSCH FP from CRNC to

NodeB.3. The MAC-hs of the NodeB completes the scheduling of the data between the UEs that camp on

the HSDPA cells;.4. The MAC-hs of the NodeB sends the MAC-hs PDU through Uu interface to the equivalent MAC-hs

of the UE.

2-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 79: SYS202m2 Usr7 Ver1 Rev2

Realization of HSDPA Version 1 Rev 2

Realization of HSDPAHSDPA Protocol Stack SRNC and CRNC same

HSDPA Protocol Stack SRNC and CRNC different

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-7

USR7

Page 80: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Overview of HSDPA Physical Layer

Overview of HSDPA Physical LayerThe basic downlink channel configuration for a UE consists of one or several HS-PDSCHs, oneassociated DPCH, and several HS-SCCHs. In any given TTI, a UE can use a maximum of oneHS-SCCH.When Fractional-Dedicated Physical Control Channel (F-DPCH) is configured, all RABs/SRBs arecarried on HS-DSCH. The associated DPCH is replaced with the F-DPCH and there is no DPDCH.The basic uplink channel configuration of HSDPA is the same as that of R99, except that one HS-DPCCHis added for one UE.Seen from the UE side, the processing at the HSDPA-related physical layer is as follows:

• In each TTI, the UE detects the HS-SCCH channel to check whether the UE is scheduled or not.– If the UE is scheduled, it demodulates and decodes the data from HS-PDSCHs specified by

the related HS-SCCH. An ACK or NACK will be generated on the basis of the decoding resultof HS-PDSCHs and will be sent to the serving cell through HS-DPCCH.

– If the UE is not scheduled, it does not demodulate or decode the data from HS-PDSCHs.• The Channel Quality Indicator (CQI) is periodically reported through the HS-DPCCH regardless

of whether the UE is scheduled. CQI is a key input for Transport Format and ResourceCombination (TFRC) selection and scheduling based on channel quality at the MAC-hs layer.

Seen from the UTRAN side, the processing at the HSDPA-related physical layer is as follows:

• Multiple UEs can be multiplexed in the code domain within an HS-DSCH TTI. This process is calledcode division in one TTI.

• The physical resources of HS-DSCH are time shared by all HS-DSCH UEs in the cell.

2-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 81: SYS202m2 Usr7 Ver1 Rev2

Overview of HSDPA Physical Layer Version 1 Rev 2

Overview of HSDPA Physical Layer

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-9

USR7

Page 82: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA Physical Channels

HSDPA Physical ChannelsThere are three types of channels added for HSDPA at the physical layer:

• HS-SCCH• HS-PDSCH• HS-DPCCH

High Speed Shared Control Channel (HS-SCCH)The HS-SCCH is a fixed rate (60 kbps, SF=128) downlink physical channel used to carry downlinksignaling related to HS-DSCH transmission. The diagram below shows the subframe structure of theHS-SCCH.The following control information is carried by HS-SCCH:

• HS-PDSCH channelization code set information;• HS-PDSCH modulation scheme information;• Transport block size information;• Hybrid ARQ process information;• Redundancy and constellation version;• New data indicator;• UE identify.

2-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 83: SYS202m2 Usr7 Ver1 Rev2

HSDPA Physical Channels Version 1 Rev 2

HSDPA Physical ChannelsHS-SCCH

1s 60kbit/s SF = 128, QPSK

10ms Radio Frame, 600 bits

2ms Subframe (Tf), 120 bits

Tslot = 2560 chips, 40 bits

Slot # 6 Slot # 7 Slot # 8

Data Ndata1 bits

• HS-PDSCH channelization code set information

• HS-PDSCH modulation scheme information

• Transport block size information

• Hybrid ARQ process information

• Redundancy and constellation version

• New data indicator

• UE identifier

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-11

USR7

Page 84: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 High Speed Physical Downlink Shared Channel

High Speed Physical Downlink Shared ChannelThe HS-PDSCH is used to carry the HS-DSCH data.The spreading factor of the HS-PDSCH can be 16 only. Each cell can provide at most 15 HS-PDSCHswhose codes must be continuous. The number of HS-PDSCH codes used by the UE depends onUE category. The UE of category 10 can support a maximum of 15 HS-PDSCH codes and 16 QAMmodulation mode. The supported peak rate on the air interface can reach 14.4 Mbps.

2-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 85: SYS202m2 Usr7 Ver1 Rev2

High Speed Physical Downlink Shared Channel Version 1 Rev 2

High Speed Physical Downlink Shared Channel

1s 480kbit/s SF = 16, QPSK or 960kbit/s 16 QAM

10ms Radio Frame, 4800 bits QPSK

2ms Subframe (Tf), 960 bits QPSK or 1920 bits 16 QAM

Tslot = 2560 chips, 320 bits QPSK or 640 bits 16 QAM

Slot # 6 Slot # 7 Slot # 8

Data Ndata1 bits

10ms Radio Frame, 9600 bits 16 QAM

The UE of category 10 can support a maximum of 15 HS-PDSCH codes and 16 QAMmodulation mode. The supported peak rate on the air interface can reach 14.4 Mbps.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-13

USR7

Page 86: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 High Speed dedicated Physical Control Channel (HS-DPCCH)

High Speed dedicated Physical Control Channel (HS-DPCCH)The slide opposite shows the subframe structure of HS-DPCCH. The HS-DPCCH carries uplink feedbacksignaling related to downlink HS-DSCH transmission. The HS-DSCH related feedback signaling consistsof HARQ-ACK and CQI. The HARQ-ACK is carried in the first slot of the HS-DPCCH subframe, and theCQI is carried in the second slot and the third slot of a subframe.The spreading factor of the HS-DPCCH is 256, that is, there are 10 bits per uplink HS-DPCCH slot.

HS-DPCCH PreambleThe feature provides the function to control UL HS-DPCCH transmission power, aimed at decreasing theUL interference and saving UE power. On HS-DPCCH channel, when ACK and NACK are transmitted,the preamble is added. Generally, the ACK/NACK power is less 3dB than with no preamble condition.The feature is enabled with the command ADD CELLHSDPA.HsdpcchPreambleSwitch — Value range: Mode0, Mode1.Physical unit: None.Content: Whether this cell supports HS-DPCCH Preamble.Recommended value: Mode0

2-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 87: SYS202m2 Usr7 Ver1 Rev2

High Speed dedicated Physical Control Channel (HS-DPCCH) Version 1 Rev 2

High Speed dedicated Physical Control Channel (HS-DPCCH)

CQICQIHARQ-ACK CQICQIHARQ-ACK

1s 15kbit/s SF = 256

10ms Radio Frame, 150 bits

2ms Subframe (Tf), 30 bits

Tslot = 2560 chips, 10 bits

Slot # 6 Slot # 7 Slot # 8

Data Ndata1 bits

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-15

USR7

Page 88: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA Channel Mapping

HSDPA Channel Mapping

HS-DSCH MappingWhen a DL RAB is mapped to the HS-DSCH, UL DCH is set up regardless of the existence of UL data.UL DCH transmits the UL signaling, UL RLC acknowledgement message and possible UL service data.DL DCH is set up to transmit the DL signaling. These DCHs are called associated DCHs in the followingsections, and the corresponding DPCHs are called associated DPCHs.When the UE is in soft handover, its HSDPA DL data can be carried by one HS-DSCH cell at most whilethe non-HSDPA data can be carried by DPCHs in many cells.

2-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 89: SYS202m2 Usr7 Ver1 Rev2

HSDPA Channel Mapping Version 1 Rev 2

HSDPA Channel Mapping

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-17

USR7

Page 90: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Fractional — Dedicated Physical Channel (F-DPCH)

Fractional — Dedicated Physical Channel (F-DPCH)F-DPCH was added in Rel-6 to optimize the consumption of downlink channelization codes. When usingHS-DSCH, the main use for DL DPCH (also known as A-DPCH where A stands for Associated) is to carrypower control commands (TPC bits) to the UE in order to adjust the uplink transmission power. If all RBsincluding SRBs are mapped on to HS-DSCH then the DL codes are being wasted. SF 256 is used forA-DPCH and so every code being used by a user is seriously depleting the codes available for otherUE’s. To overcome this F-DPCH is used so that multiple UE’s can share a single DL channelisationcode. The limitation is 10 UEs in Rel-6.For several users, the network configures each user having the same code but different frame timingand, thus, users can be transmitted on the single code source. The original timing is thus retained whichavoids the need to adjust timings based on R99 power control loop implementation.During slots where the DPCCH is not transmitted, the NodeB cannot estimate the uplinksignal-to-interference ratio for power-control purposes and there is no reason for transmitting apower control bit in the downlink. Consequently, the UE shall not receive any power control commandson the F-DPCH in downlink slots corresponding to inactive uplink DPCCH slots.There are some restrictions for F-DPCH. It is not usable with services requiring data to be mapped to theDCH, such as AMR speech calls and CS video. Also, the lack of pilot information means that a methodlike feedback-based transmit diversity (closed loop mode) is not usable. The use of closed loop diversityis based on user-specific phase modification, wherein pilot symbols would be needed for verification ofthe phase rotation applied. On the other hand, when utilizing the F-DPCH, SRBs can benefit from highdata rates of HSDPA and reduce service setup times remarkablyBy using F-DPCH the cell capacity has been improved and at the same time for same number of users,the interference has gone down significantly.In R7, R6 limitation has been removed. In R6, for a given UE in soft handover the TPC from all F-DPCHhad to have the same offset timing. In R7, F-DPCH (TPC bits) can have different timing from differentcells. This is possible due to introduction of 9 new F-DPCH slot formats (slot format 0 is the legacyF-DPCH slot format). The RRC signalling is done separately for slot formats from the RNC to each ofthe cells.

Associated CommandsThere are two associated commands with this feature.SET FDPCHRLPWRFdpchMaxRefPwr — Value range: -350 to 150.Physical unit: 0.1dB. Content: Maximum reference power for the FDPCH.This parameter indicates themaximum value of Reference F-DPCH Tx Power. The correspondent IE is Maximum DL Power IE.Fordetailed information of this parameter, refer to 3GPP TS 25.433.Recommended value: -30.FdpchMinRefPwr — Value range: -350 to 150.Physical unit: 0.1dB.Content: Minimum reference power for the FDPCH.This parameter indicates the minimum value ofReference F-DPCH Tx Power. The correspondent IE is Minimum DL Power IE.For detailed informationof this parameter, refer to 3GPP TS 25.433.Recommended value: -200.SET FDPCHPARAFdpchPO2 — Value range: 0~24.Physical value range: 0~6; step: 0.25.Physical unit: dB. Content: Indicating the power offset of TPC command in F-DPCH channel comparativeto Reference F-DPCH TX power (expressed by Initial DL Transmission Power IE).Recommended value: 12.FdpchTpcCommandErrorRateTarget — Value range: 1~10.Physical value range: 0.01~0.1; step: 0.01.Physical unit: None.Content: Indicating the TPC command error rate target in F-DPCH channel.Recommended value: 4.

2-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 91: SYS202m2 Usr7 Ver1 Rev2

Fractional — Dedicated Physical Channel (F-DPCH) Version 1 Rev 2

Fractional — Dedicated Physical Channel (F-DPCH)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-19

USR7

Page 92: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Enabling HSDPA

Enabling HSDPAHSDPA is enabled at:

• CN for the provision of RABs to carry high speed data.• On the Iub paths (SYS202m1), these can be ATM or IP.• On a cell level so the channels maybe created and have characteristics defined by the operator.• Within the RNC so services can be mapped onto the channels that the operator has planned for.

Enabling HSDPA at Cell LevelThe command ADD CELLHSDPA is used to enable HSDPA on a cell level.

HSDPA Code Resource ManagementThe code resource consists of the following parts:

• Common channel and HS-SCCH channelization codes:– The number of HS-SCCH channelization codes in each TTI in the local cell determines the

maximum number of users scheduled on the Uu interface. The number is determined by thetraffic model of the cell. Generally, it is set to 4. Code Number for HS-SCCH is set by CodeNumber for HS-SCCH parameter within the command ADD CELLHSDPA.

– The number of common channelization codes is specified when the cell is set up.• HS-PDSCH channelization codes.• DPCH channelization codes:

– The number of DPCH codes varies with the number of DCH users in the cell.A key problem to be solved by code resource management is how to share code resource betweenDPCH and HS-PDSCH to increase the usage of the cell code resource.Three HS-PDSCH code allocation modes are described as follows:

• RNC controlled static code allocation:– In the static code allocation, the HS-PDSCH codes are configured by the command ADD

CELLHSDPA, and the allocated codes recorded on the RNC can be modified only throughthe Allocate Code Mode parameter also found in ADD CELLHSDPA.

• RNC controlled dynamic code allocation:– It is set through the Allocate Code Mode parameter.

• NodeB controlled dynamic code allocation:– It is set through the Dynamic Code Switch parameter in the command SET MACHSPARA.

HSDPA Code Resource Management Parameters for HS-SCCHThe command ADD CELLHSDPA allows the HS-SCCH codes to be set.HsScchCodeNum — Number of the HS-SCCH codesValue range: 1~15Content: This parameter decides the maximum number of subscribers that the NodeB can schedulein a TTI period. In the scenarios like outdoor macro cells with a power restriction, it is less likely toschedule multiple subscribers simultaneously, so two HS-SCCHs are configured. In the scenarios likeindoor pico with a code restriction, it is more likely to schedule multiple subscribers simultaneously, sofour HS-SCCHs are configured. If excessive HS-SCCHs are configured, the code resource is wasted.If insufficient HS-SCCHs are configured, the HS-PDSCH code resource or power resource is wasted.Both affect the cell throughput rate. For detailed information of this parameter, refer to 3GPP TS 25.308.Recommended value: 4

2-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 93: SYS202m2 Usr7 Ver1 Rev2

Enabling HSDPA Version 1 Rev 2

Enabling HSDPA

RNC – HS-PDSCH Dynamic Mode Supported

CNCN

Iu

Iub

Com

mC

H

HS

-SC

CH

Codes are set when cell established

1 to 15 Codes can

be set

Rec - 4

HS

-PD

SC

H

PD

CH

Code availability determined

by how many active DCH users in the

cell

1 to 15 Codes can

be set

Rec – 5

Static or Dynamic Modes

NB – HS-PDSCH Dynamic Mode Supported

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-21

USR7

Page 94: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Static Allocation

Static AllocationIn static allocation, the RNC reserves some codes for the HS-PDSCH. The DPCH, HS-SCCH and othercommon channels use the rest.The parameter of the codes reserved for the HS-PDSCH can be configured on the RNC LMT.The value of Code Number for HS-PDSCH is determined by the service model and the traffic model ofthe corresponding cell. This parameter is valid only when Allocate Code Mode is set to Manual.The parameters to set the parameters for the code mode and the number of codes to be reserved arefound in the command ADD CELLHSDPA and are described below.AllocCodeMode — Allocation mode of the HS-PDSCH codesValue range: Manual, AutomaticContent: If Manual is chosen, allocating [Code Number for HS-PDSCH] the equal of configuredHS-PDSCH code number. If Automatic is chosen, allocating HS-PDSCH code number betweenconfigured HS-PDSCH Maximum code number and HS-PDSCH Minimum code number.Recommended value (default value): ManualHsPdschCodeNum — Number of the HS-PDSCH codesValue range: 1~15Content: When [Allocate Code Mode] is set to Manual, this parameter is valid.Recommended value (default value): 5

2-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 95: SYS202m2 Usr7 Ver1 Rev2

Static Allocation Version 1 Rev 2

Static Allocation

ADD CELLHSDPA: CellId=4095, AllocCodeMode=Manual, HsPdschCodeNum=5, HsScchCodeNum=4, …………;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-23

USR7

Page 96: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 RNC-Controlled Dynamic Allocation

RNC-Controlled Dynamic AllocationIn the RNC-controlled dynamic allocation, the RNC adjusts the reserved HS-PDSCH codes according tothe real-time usage status of the codes.A minimum number of codes, defined by the Code Min Number for HS-PDSCH parameter, are reservedfor the HS-PDSCH in a cell. When the channelization codes in the cell are idle and adjacent to thereserved HS-PDSCH codes, the number of codes for the HS-PDSCH can be increased but cannotexceed the value of the Code Max Number for HS-PDSCH parameter. The difference codes betweenCode Max Number for HS-PDSCH and Code Min Number for HS-PDSCH are shared by the HS-PDSCHand the DPCH. The shared codes are allocated to the HS-PDSCH only when the DPCH does not usethem. The dynamic allocation includes the increase and decrease of the codes for the HS-PDSCH.The RNC adds one of shared codes to the codes reserved for the HS-PDSCH if the following cases arefulfilled:

• If in cell's code tree there is at least one code can be reserved and this code's SF is equal to or lessthan the Reserved SF threshold, the NodeB will try to increase HS-PDSCH code number.

• Among shared codes, the code which neighbours to the reserved codes for the HS-PDSCH is idle,which can be attained through reshuffling the cell code resource.

The RNC releases the minimum one of shared codes reserved for the HS-PDSCH to the DPCH whenthe minimum spread factor of the free spread codes is larger than the Reserved SF threshold.The parameters to set the dynamic allocation of codes are found in the command ADD CELLHSDPAand are described below.HsPdschMaxCodeNum — Maximum number of the HS-PDSCH codesValue range: 1~15Content: When [Allocate Code Mode] is set to Automatic, this parameter is valid.Recommended value (default value): 10HsPdschMinCodeNum — Minimum number of the HS-PDSCH codesValue range: 1~15Content: When [Allocate Code Mode] is set to Automatic, this parameter is valid.Recommended value (default value): 5

2-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 97: SYS202m2 Usr7 Ver1 Rev2

RNC-Controlled Dynamic Allocation Version 1 Rev 2

RNC-Controlled Dynamic Allocation

ADD CELLHSDPA: CellId=4095, AllocCodeMode=Automatic, HsPdschMaxCodeNum=8, HsPdschMinCodeNum=4, .......;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-25

USR7

Page 98: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Increasing and Decreasing the Codes Reserved for the HS-PDSCH

Increasing and Decreasing the Codes Reserved for theHS-PDSCH

Increasing the Codes Reserved for the HS-PDSCHThe top diagram shows the process for increasing the codes reserved for the HS-PDSCH. The solid dotsrepresent the occupied codes and the circles represent the idle codes.When the code consumption is reduced because of DCH RL deletion or RL reconfiguration (for example,SF is changed to a larger one), the RNC increases the codes reserved for the HS-PDSCH only whenthe following conditions are met:

• The shared code neighboring to the codes reserved for the HS-PDSCH is free.• After increasing the codes for the HS-DSCH, the SF of the remaining codes should be equal to or

smaller than the value of Cell LDR SF reserved threshold.Cell LDR SF reserved threshold is used to reserve code resources for new admission and avoid coderesource congestion and is described in more detail in the load control chapter.

Decreasing the Codes Reserved for the HS-PDSCHThe bottom diagram shows the process of reducing the codes reserved for the HS-PDSCH. The soliddots represent the occupied codes and the circles represent the idle codes.When the re-allocation of code resources is triggered by DCH RL setup, RL addition, or RLreconfiguration (for example, SF is changed to a smaller one), the RNC will reallocate one of the sharedcodes reserved for the HS-PDSCH to the DPCH. After reallocating, the minimum SF of free codesshould be lower than Cell LDR SF reserved threshold. The re-allocated code number should be thesmallest one.The parameter Cell LDR SF reserved threshold is found in the command ADD CELLLDR and isdescribed below.CellLdrSfResThd — Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256Physical unit: noneContent: Cell SF reserved threshold. The code load reshuffling could be triggered only when theminimum available SF of a cell is higher than this threshold. The lower the code resource LDR triggerthreshold is, the easier the downlink code resource enters the initial congestion status, the easier theLDR action is triggered, and the easier the subscriber perception is affected. But a lower code resourceLDR trigger threshold causes a higher admission success rate because the resource is reserved.Recommended value: SF8

2-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 99: SYS202m2 Usr7 Ver1 Rev2

Increasing and Decreasing the Codes Reserved for the HS-PDSCH Version 1 Rev 2

Increasing and Decreasing the Codes Reserved for theHS-PDSCH

Increasing

Decreasing

ADD CELLLDR: CellId=4095, CellLdrSfResThd=SF8;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-27

USR7

Page 100: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 NodeB-Controlled Dynamic Code Allocation

NodeB-Controlled Dynamic Code AllocationNodeB-controlled dynamic allocation allows the NodeB to use the HS-PDSCH codes allocated by theRNC. The NodeB can dynamically allocate the idle codes of the current cell to the HS-PDSCH.The NodeB detects the SF16 codes that are not for the HS-PDSCH every 2 ms. If the codes or sub-codesare allocated by the RNC to the DCH or common channels, they are regarded as occupied. Otherwise,they are regarded as unoccupied. Therefore, the HS-PDSCH codes available for the HS-PDSCH includethe codes allocated by the RNC and those unoccupied consecutive SF16 codes that are adjacent to thereserved HS-DSCH codes.For example, in a cell HS-PDSCH, the RNC allocates SF16 codes numbered 11 to 15 to HS-PDSCH,SF16 codes numbered 0 to 5 to the DCH and common channels. Then, in this TTI, the HS-PDSCH canuse SF16 codes numbered 6 to 15.If the DCH codes allocated by the RNC are temporarily occupied by the HS-PDSCH before the setup ofa radio link, the NBAP message is sent to the RNC, indicating that the radio link is set up successfully.Then, the DCH occupies the codes. The HS-PDSCH cannot use these codes until they are released bythe DCH.It is set through the Dynamic Code Switch parameter in the command SET MACHSPARA.DYNCODESW — Dynamic Code SwitchValue range: OPEN (OPEN), CLOSE (CLOSE)Default value: None

SET MACHSPARA: DYNCODESW=OPEN;

RNC v NodeB HS-PDSCH Dynamic Code AllocationNodeB-controlled dynamic allocation allows the NodeB to use the HS-PDSCH codes allocated by theRNC and also can dynamically allocate the idle codes of the current cell to the HS-PDSCH channel.It is more flexible to allocate the code for HS-PDSCH through the NodeB-controlled dynamic allocationthan the RNC-controlled dynamic allocation. NodeB-controlled dynamic allocation can save the signalingtraffic resource for code reconfiguration on the Iub interface, compared to the RNC-controlled dynamicallocation.The following HS-PDSCH code allocation scheme is preferred:

• The RNC uses the static code allocation. The fixed number of reserved HS-PDSCH codes isspecified by Code Number for HS-PDSCH. The NodeB uses the dynamic code allocation so thatthe HS-PDSCH codes can be increased.

• If the NodeB does not support the dynamic code allocation, you can enable the dynamic codeallocation on the RNC side through the parameters Code Max Number for HS-PDSCH and CodeMin Number for HS-PDSCH.

The HS-PDSCH code allocation mode can be set through Allocate Code Mode.

2-28 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 101: SYS202m2 Usr7 Ver1 Rev2

NodeB-Controlled Dynamic Code Allocation Version 1 Rev 2

NodeB-Controlled Dynamic Code Allocation

RNC – HS-PDSCH Dynamic Mode Supported

CNCN

Iu

Iub

NB – HS-PDSCH Dynamic Mode Supported

It is recommended to have the RNC on static allocation and NodeB on dynamic allocation if the NodeB

supports this feature

More Signalling

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-29

USR7

Page 102: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Services Supported by the HS-DSCH

Services Supported by the HS-DSCHThe HS-DSCH supports four traffic classes, as listed in the table below.

Traffic Classes Description

Streaming The parameters PS_STREAMING_ON_HSDPA_SWITCH and DLstreaming threshold on HSDPA decide whether the streamingservice is carried on HS-DSCH or DCH. If the algorithm switchPS_STREAMING_ON_HSDPA_SWITCH is set on and the DL MBR of thestreaming service is greater than or equal to the value of DL streamingthreshold on HSDPA, and the UE and the best cell support HSDPA, thestreaming service will be carried on HS-DSCH, otherwise, the streamingservice will be carried on DCH.

Interactive

Background

The generic term for the two services is BE service.If the DL MBR of BE service is greater than or equal to DL BEtraffic threshold on HSDPA, and the UE and the best cell support HSDPA,the BE service will be carried on HS-DSCH, otherwise, on DCH.

Conversational The parameters VoipChlType is used to decide whether conversationalservices should be carried on HS-DSCH or DCH.

The command SET CORRMALGOSWITCH is used to set the parameter for HSDPA services streaming. This is described below.HspaSwitch — PS_STREAMING_ON_HSDPA_SWITCH.The parameters to set the streaming, BE thresholds, Voice Over IP (VOIP) channel type and signallingchannel type are set in the SET FRCCHLTYPEPARA command and are described below.DlStrThsonHsdpa — Value range: D8, D16, D32, D64, D128, D144, D256, D384.Physical value range: 8, 16, 32, 64, 128, 144, 256, 384.Physical unit: kbit/s.Content: The rate decision threshold of DL PS domain streaming service to be carried on HS-DSCH.When the maximum DL service rate is greater than or equal to this threshold, the service will be carriedon HS-DSCH; otherwise, on DCH.Recommended value: D64.DlBeTraffThsOnHsdpa — Value range: D8, D16, D32, D64, D128, D144, D256, D384, D768, D1024,D1536, D1800, D2048, D3648, D7200, D10100, D14400.Physical value range: 8, 16, 32, 64, 128, 144, 256, 384, 768, 1024, 1536, 1800, 2048, 3648, 7200,10100, 14400.Physical unit: kbit/s.Content: The rate decision threshold of DL PS domain background/interactive service to be carried onHS-DSCH. When the maximum DL service rate is greater than or equal to this threshold, the service willbe carried on HS-DSCH; otherwise, on DCH.Recommended value: D8.VoipChlType — Value range: DCH, HSDPA, HSPAPhysical unit: None.Content: Indicating the channel type of VOIP service. -DCH: Both uplink and downlink are beared onDCH. -HSDPA: Uplink is beared on DCH, downlink beared on HS-DSCH. -HSPA:Uplink is beared onE-DCH, downlink beared on HS-DSCH.Recommended value: DCH.ImsChlType — Value range: DCH, HSDPA, HSPAPhysical unit: None.Content: Indicating the channel type of IMS signalling. -DCH: Both uplink and downlink are beared onDCH. -HSDPA: Uplink is beared on DCH, downlink beared on HS-DSCH. -HSPA:Uplink is beared onE-DCH, downlink beared on HS-DSCH.Recommended value: DCH.SrbChlType — Value range: DCH, HSDPA, HSPAPhysical unit: None.Content: Indicating the channel type of SRB. -DCH: Both uplink and downlink are beared on DCH.-HSDPA: Uplink is beared on DCH, downlink beared on HS-DSCH. -HSPA:Uplink is beared on E-DCH,downlink beared on HS-DSCH.Recommended value: DCH.SrbChlTypeRrcEffectFlag — Value range: FALSE, TRUEPhysical unit: None.Content: Indicating whether [Srb channel type] is valid in RRC setup process. -TRUE: [Srb channel type]

2-30 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 103: SYS202m2 Usr7 Ver1 Rev2

Services Supported by the HS-DSCH Version 1 Rev 2

Services Supported by the HS-DSCHis valid in RRC setup process and other processes. -FALSE:[Srb channel type] is invalid in RRC setupprocess, but valid in other processes.Recommended value: FALSE.

RNCRNCCNCN

Iu

Iub

NodeB• RAB Assignment Request

• Streaming, Best Effort, VOIP or Signalling Services

• Bit Rate

PS_STREAMING_ON_HSDPA_SWITCH (on/off)

DL streaming threshold on HSDPA [kbit/s]

DL BE traffic threshold on HSDPA [kbit/s]

VOIP carried on DCH, HSDPA (UL DCH) or HSPA

Signalling carried on DCH, HSDPA (UL DCH) or HSPA

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-31

USR7

Page 104: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 QoS Requirements of Different Services

QoS Requirements of Different ServicesDifferent services, such as SRB, IMS signaling, VoIP, streaming, interactive, and background services,can be mapped on HSDPA.The requirements for the QoS of different services are as follows:

• IMS/SRB: Signaling has a high requirement for transmission delay. If the requirement cannot bemet, the service may be affected. For example, an SRB delay may lead to a handover delay. Theaverage rate of signaling is lower than 20 kbit/s.

• VoIP: The VoIP service is highly delay sensitive. The end-to-end delay of a voice frame shouldbe shorter than 250 ms. The tolerant frame error rate is about 1%. The average rate of the VoIPservice with the header compressed is about 20 kbit/s.

• Streaming: The streams at the receiver end should be continuous. Compared with VoIP, thestreaming service has a relatively low delay sensitivity, because a buffer that can avoid jitter forseveral seconds is configured at the receiver end. When the rate of the streaming service is equalto or higher than the GBR, the QoS can be guaranteed.

• BE (background and interactive): The data rate at the service source end can reach a high value,for example, several Mbit/s during a burst. The BE service has a low requirement for transmissiondelay but has a high requirement for reliable transmission.

QoS Parameters Mapped onto the MAC-hs Layer of the NodeBThere are a number of parameters that effect the QoS when applied to the MAC-hs:

• MAC-hs Discard timer:• Scheduling Priority Indicator (SPI):• Guaranteed Bit Rate (GBR)

MAC-hs Discard timerA MAC-d PDU in a MAC-hs queue is discarded if the waiting time exceeds the length of this discardtimer. It is an optional IE on the Iub interface. For the VoIP service, the timer is set to 100 ms. For theBE and streaming services, the timer is not set. For an MAC-hs queue configured with the discard timer,the scheduler should send out the MAC-d PDUs before expiry of the timer.

Scheduling Priority Indicator (SPI)This parameter specifies the scheduling priority of an MAC-hs queue. The priority is derived from theTraffic Class, Traffic Handling Priority (THP), and User Priority that are mapped onto this queue.The service-oriented control algorithms are configured on an SPI basis on the NodeB side. For example,the QoS-oriented algorithms, such as the flow control algorithm, scheduling algorithm, CQI adjustmentalgorithm, and maximum number of HARQ process retransmissions, are all configured on an SPI basison the NodeB side.The user priority–oriented parameters are also configured on an SPI basis on the NodeB side. Forexample, the weight factor corresponding to the user priority is named Weight of SPI on the NodeB side.

Guaranteed Bit RateIt is configured on an MAC-hs queue basis. For the streaming service, the GBR specifies the rate thatcan meet the requirement of the user for viewing and the GBR of a queue is determined by the NAS. Forthe BE service, the GBR specifies the required minimum rate for the service of the users in the RAN. TheGBR of a BE service user is set through the SET USERGBR command on the RNC side. The setting isbased on the user priority, namely, gold user, silver user, or copper user.Services with different QoS requirements require different QoS guarantee policies. For example, theVoIP service has a high requirement for delay. To limit the delay caused by flow control or schedulingwithin a proper range, the algorithm grants the VoIP queue a priority to occupy resources first. Thestreaming service has a high requirement for GBR. Therefore, the scheduling and flow control algorithmsguarantee that the average rate of the service is not lower than the GBR during Iub traffic distribution andUu resources allocation. The BE service has a high requirement for reliability, which can be achievedthrough more retransmissions on the Uu interface.

2-32 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 105: SYS202m2 Usr7 Ver1 Rev2

QoS Requirements of Different Services Version 1 Rev 2

QoS Requirements of Different Services

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-33

USR7

dqfr38
Sticky Note
SPI=Scheduling Priority Indicator. This the one that sent to NodeB thru the NBAP
dqfr38
Sticky Note
Only for Interactive services. Sent by CN also mapped in RNC by command: SET IAVUSERTHPCLASS
Page 106: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 QoS Mapping to SPI

QoS Mapping to SPIThe SPI is a combination of three parameters namely:

• User Priority• Traffic Class• Traffic Handling Priority (THP) for interactive services.

Mapping ARP to User PriorityThe Allocation and Retention Policy (ARP) is set in the CN and sent to the RNC in the RANAP RABAssignment Request message. The values range that can be set are from 1 to 15, with 1 being thehighest priority and 15 the lowest.These ARPs are mapped onto three User Priorities within the RNC known as Gold, Silver and Bronze.The command that maps these is SET USERPRIORITY, the default mapping is shown in the table below.

ARP 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

UserPriority

1 1 1 1 1 2 2 2 2 2 3 3 3 3 3

User Priority 1 = GoldUser Priority 2 = SilverUser Priority 3 = Bronze

Setting Traffic ClassesThere are six different traffic classes supported currently:

• SRB signaling• IMS signaling• Conversational (VoIP)• Streaming• Interactive• Background

Setting Traffic Handling Priority (THP) for Interactive ServicesThe THP sets the relative priority of users of interactive services with THP of 1 being the highest priorityand 14 the lowest. A THP of 15 means that no priority is set .The command SET SCHEDULEPRIOMAP is used to map the THP, User Priority and Traffic Class to theSPI. The default mappings to the SPI are shown in the table at the end of this chapter.

2-34 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 107: SYS202m2 Usr7 Ver1 Rev2

QoS Mapping to SPI Version 1 Rev 2

QoS Mapping to SPI

Mapping SPI to NodeB HSDPA AlgorithmsThe SPI is sent to the NodeB in NBAP messages and forms the basis of how the NodeB algorithms willdeal with the QoS of the user. The algorithms effected are:

• HSDPA Flow Control• HSDPA MAC-hs Scheduling• HSDPA TFRC Selection• HSDPA Power Resource Management

There are key inputs that effect the NodeB HSDPA algorithms that are configured according to the SPI.These key inputs are:

• CQI Adjust Algorithm Switch• Residual Bler Target• Max Retransmission Count• EPF Schedule Algorithm Switch• Flow Control Algorithm Switch• Weight of SPI

The default values for these key inputs in relation to the SPI are shown at the end of this chapter.

RNCRNCCNCN

Iu

Iub

RANAP_RAB_ASSIGNMENT_REQ

ARP 1 Highest Priority

.

.

.

ARP 15 Lowest Priority

• ARP to User Priority Mapping

• SPI references:

1. User Priority

2. Traffic Handling Priority (Interactive Service)

3. Traffic Class

SPI Maps to NodeB Algorithms:

• HSDPA Flow Control

• HSDPA MAC-hs Scheduling

• HSDPA TFRC Selection

• HSDPA Power Resource Management

NBAP Signaling

• SPI given

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-35

USR7

Page 108: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 MAC-hs on the UTRAN Side

MAC-hs on the UTRAN SideThe MAC-hs on the UTRAN side manages the physical resources allocated to HS-DSCH.The MAC-hs consists of the following four different functional entities:

• Flow control• Scheduling• Transport Format and Resource Combination (TRFC) selection• Hybrid Automatic Repeat reQuest (HARQ)

Flow controlThe flow control entity controls the HSDPA data flow between RNC and NodeB.

• Purpose: to reduce the transmission time of HSDPA data on the UTRAN side and to reduce thedata discarded and retransmitted when the Iub interface or Uu interface is congested.

• The transmission capabilities of the Uu interface and Iub interface are taken into account in adynamic manner in flow control.

SchedulingThe scheduling entity handles the priority of the queues and schedules the priority queues or NACKHARQ processes of the HS-DSCH UEs in a cell to be transmitted on the HS-DSCH related physicalchannels in each TTI.

• Purpose: to achieve considerable cell throughput capability and to satisfy user experience.• The selection is implemented through the scheduling algorithm based on channel quality or QoS.

TRFCThe TFRC selection entity selects an appropriate transport format and resource for the data to betransmitted on HS-DSCH.

• The transport format includes the transport block size and modulation scheme. The resourceincludes the power resource and code resource of HS-PDSCH.

• TFRC for each UE is channel quality based, where Adaptive Modulation and Coding (AMC) isthe key technique.

HARQThe HARQ entity handles the HARQ protocol for each HS-DSCH UE.

• Each HS-DSCH UE has one HARQ entity on the MAC-hs of the UTRAN side to handle the HARQfunctionality.

• One HARQ entity can support multiple instances (HARQ processes) of stop and wait HARQprotocols. Based on the status reports from HS-DPCCH, a new transmission or retransmission isdetermined.

2-36 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 109: SYS202m2 Usr7 Ver1 Rev2

MAC-hs on the UTRAN Side Version 1 Rev 2

MAC-hs on the UTRAN Side

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-37

USR7

Page 110: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 MAC-hs on the UE Side

MAC-hs on the UE SideThe functional entities are described as follows:

• The HARQ entity handles the HARQ protocol on the receiver side. For example, it can generateACKs or NACKs.

• The reordering queue distribution entity routes the MAC-hs PDUs to the correct reordering bufferbased on the queue ID.

• The reordering entity reorders the received MAC-hs PDUs according to their TransmissionSequence Number (TSN) and the TSN may be out of sequence because of parallel HARQprocesses. For each queue ID, one reordering entity is configured on the UE.

• The disassembly entity extracts the MAC-d PDUs from the MAC-hs PDUs and delivers them to thehigher layer.

2-38 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 111: SYS202m2 Usr7 Ver1 Rev2

MAC-hs on the UE Side Version 1 Rev 2

MAC-hs on the UE Side

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-39

USR7

Page 112: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Overview of NodeB HSDPA Flow Control

Overview of NodeB HSDPA Flow ControlHSDPA Flow control is a process used to control HSDPA data flow from RNC MAC-d to NodeB MAC-hsaccording to Iub bandwidth and air interface bandwidth.After HSDPA is introduced, users’ rate on air and on Iub is not consistent. It is necessary to adjust rateon Iub according to its rate on air.The algorithm of NodeB HSDPA flow control is implemented through the signaling of HSDPA FlowControl. The NodeB allocates the capacity for each MAC-hs queue, and the RNC limits the downlinkrate of each MAC-hs queue according to the allocated capacity.The allocation process can be triggered by the capacity allocation request from RNC or from the NodeBflow control algorithm.

Types of Flow ControlNodeB and RNC can provide flow control functions. In NodeB, there are two types of flow control policies:

• Flow control free.• Dynamic flow control.

Dynamic flow control has three methods:

• No shaping.• Shaping without adaptive Iub bandwidth.• Shaping with adaptive Iub bandwidth.

2-40 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 113: SYS202m2 Usr7 Ver1 Rev2

Overview of NodeB HSDPA Flow Control Version 1 Rev 2

Overview of NodeB HSDPA Flow Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-41

USR7

Page 114: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Signalling of HSDPA Flow Control

Signalling of HSDPA Flow ControlThe signaling of HSDPA flow control is implemented through capacity request and allocation procedure.The signaling procedure is as follows:

• The CRNC sends an HS-DSCH Capacity Request to the NodeB, when some RLC PDUs arepending in the RLC entity and the credits (indicated in the latest HS-DSCH Capacity Allocationmessage) are used up. If there is no RLC PDU but the allocated capacity is greater than zero,the RNC also sends a Capacity Request to the NodeB, indicating that the NodeB can stop thecapacity allocation.

• The NodeB sends an HS-DSCH Capacity Allocation message to the CRNC as the response to theHS-DSCH capacity request or to the requirement of the Iub HSDPA flow control algorithm.

Capacity Allocation Frame FieldsIn the HS-DSCH Interval, the user can send a maximum number of HS-DSCH Credits MAC-d PDUs.The PDU size is limited by Maximum MAC-d PDU Length. The user can repeat the HS-DSCH Intervalin the period defined by HS-DSCH repetition period.

• CmCH-PI: Scheduling Priority Indicator (SPI) of the queue.• HS-DSCH Interval: time interval during which the HS-DSCH Credits granted in the HS-DSCH

CAPACITY ALLOCATION control frame can be used.• HS-DSCH Credits: number of MAC-d PDUs that a CRNC can transmit during an HS-DSCH Interval

granted in the HS-DSCH CAPACITY ALLOCATION control frame.• Maximum MAC-d PDU Length: maximum PDU size among the MAC-d PDU sizes configured in

the NBAP messages.• HS-DSCH repetition period: number of subsequent intervals during which the HS-DSCH Credits

IE granted in the HS-DSCH CAPACITY ALLOCATION control frame can be used and the value 0means that there is no limit to the repetition period.

2-42 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 115: SYS202m2 Usr7 Ver1 Rev2

Signalling of HSDPA Flow Control Version 1 Rev 2

Signalling of HSDPA Flow Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-43

USR7

Page 116: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Flow Control Policies

Flow Control PoliciesGenerally, the NodeB allocating the capacity to a MAC-hs queue considers the output rate on the Uuinterface and Iub available bandwidth. For different QoS requirements, the NodeB uses different flowcontrol policies, namely, flow control free and dynamic flow control.The flow control policies are based on Scheduling Priority Indicator (SPI) and are configured throughthe Flow Control Algorithm Switch parameter.

Flow Control Free PolicyAfter the HS-DSCH bearer is set up, the NodeB sends a capacity allocation message to the RNC,indicating that the DL traffic of the new MAC-hs queue is not limited and the RNC MAC-d can senddata as much as required. The allocation keeps unchanged for the service.The policy of no flow control policy is applied only to VoIP, IMS, and SRB, for these services are delaysensitive and have a relative low rate.

Dynamic Flow Control PolicyDynamic flow control is mainly applied to MAC-hs queues of BE service, these services are not delaysensitive, the rate varies over a wide range, and will reach a high rate during a burst.Dynamic flow control is also applied to MAC-hs queues for streaming services, as the streaming servicehas a relative high data rate and may result in congestion on Uu.This section mainly describes the method of shaping with adaptive Iub bandwidth using the dynamic flowcontrol policy. There are two other methods similar to shaping using adaptive Iub bandwidth, except thatthe functions of shaping using Iub adaptive bandwidth are ignored.Dynamic flow control process of Shaping with adaptive Iub bandwidth is as follows:

1. The congestion status of the transport network is reported to the NodeB through DRT and FSN.The NodeB adaptively adjusts the Iub bandwidth available for HSDPA based on the congestiondetected.

2. Depending on the available bandwidth and rate on air interface, the NodeB allocates bandwidth toHSDPA users and performs traffic shaping (Iub shaping) to avoid congestion and packet loss overthe Iub interface.

3. The RNC limits the flow of HS-DSCH data frames for each MAC-hs queue according to theHS-DSCH capacity allocation.

Dynamic Flow Control Policy ModulesDynamic flow control policy consists of the following modules:

• Adaptive capacity allocation:– NodeB adaptively allocates capacity to an MAC-hs queue based on its rate on the air interface.– Capacity means how much data RNC can send to the NodeB in an interval.

• Congestion control on Iub:– The total flow of all the MAC-hs queues should not exceed the available Iub bandwidth to avoid

congestion on Iub.– RNC provides the function of backpressure to avoid Iub congestion (see SYS202m1).– NodeB provides the following functions to avoid Iub congestion:

◊ Adaptive adjustment of Iub bandwidth:◊ NodeB periodically detects Iub congestion and adaptively adjusts the available Iub

bandwidth according to the Iub state.◊ Iub shaping:

◊ Iub shaping is used to allocate Iub bandwidth to every MAC-hs queue based on theavailable Iub bandwidth and ensure the total flow of the queues does not exceed theavailable Iub bandwidth. Thus, congestion control is achieved on the Iub interface,which increases the bandwidth usage and avoids overload.

2-44 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 117: SYS202m2 Usr7 Ver1 Rev2

Flow Control Policies Version 1 Rev 2

Flow Control Policies

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-45

USR7

Page 118: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Dynamic Flow Control Policy Configuration

Dynamic Flow Control Policy ConfigurationDynamic flow control policy is configured through the Hsdpa Switch within the SETHSDPAFLOWCTRLPARA command and the parameters depend on the version of NodeB being used.In this example a BTS3812 at USR7 is shown.SWITCH — If the switch is set to STATIC_BW_SHAPING, based on the configured Iub bandwidth andthe bandwidth occupied by R99 users, traffic is allocated to HSDPA users when the physical bandwidthrestriction is taken into account.If the switch is set to DYNAMIC_BW_SHAPING, according to the flow control of STATIC_BW_SHAPING,traffic is allocated to HSDPA users when the delay and packet loss on the Iub interface are taken intoaccount. The RNC use the R6 switch to perform this function. It is recommended that the RNC incompliance with R6 should perform this function.If the switch is set to NO_BW_SHAPING, the NodeB does not allocate bandwidth according to theconfiguration or delay on the Iub interface. The RNC allocates the bandwidth according to the bandwidthon the Uu interface reported by the NodeB. To perform this function, the reverse flow control switchmust be enabled by the RNC. The link is not congested when the delay is lower than this threshold.The link is not congested when frame loss ratio is no higher than this threshold.If the switch is set to BW_SHAPING_ONOFF_TOGGLE, if BW_SHAPING_ONOFF_TOGGLE isselected, the system automatically selects DYNAMIC_BW_SHAPING or NO_BW_SHAPING on thebasis of the NodeB congestion detection mechanism. In other words, DYNAMIC_BW_SHAPING isselected when congestion is detected; NO_BW_SHAPING is selected when there is no congestionwithin a specific time.

2-46 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 119: SYS202m2 Usr7 Ver1 Rev2

Dynamic Flow Control Policy Configuration Version 1 Rev 2

Dynamic Flow Control Policy Configuration

RNCRNCCNCN

Iu

Iub

NodeB

SET HSDPAFLOWCTRLPARA

• STATIC_BW_SHAPING

• DYNAMIC_BW_SHAPING

• NO_BW_SHAPING

• BW_SHAPING_ONOFF_TOGGLE

Flow control must be enabled at the RNC if SET HSDPAFLOWCTRLPARA is set to:

NO_BW_SHAPING

BW_SHAPING_ONOFF_TOGGLE

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-47

USR7

Page 120: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Adaptive Capacity Allocation Based on Uu Rate

Adaptive Capacity Allocation Based on Uu RateNodeB adaptively allocates capacity to an MAC-hs queue based on its rate on air interface (Uu).The Uu interface transmission rate of the MAC-hs queue varies dynamically with several factors, suchas the channel quality of the UE and activities of other users in the system.It makes sense to keep the queue occupancy in a reasonable level in order to reduce data transmissiondelay, L2 signal delay, and discarding as the result of priority queue congestion or reset during handover.In this sense, the functionality is called capacity allocation adaptive to Uu interface bit rate, where capacityallocation for each priority queue is based on the Uu interface bit rate and the buffer occupancy level.The Iub bandwidth allocation is based only on the rate of each queue on the Uu interface:

• If there is little data in the queue, a wide bandwidth is allocated.• If there is reasonable data in the queue, the bandwidth that is close to the rate on the Uu interface

is allocated.• If there is too much data in the queue, a narrow bandwidth or no bandwidth is allocated. Whether

there is enough data in the queue is judged by the time to send all the data in the priority queuewith the current Uu rate.

2-48 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 121: SYS202m2 Usr7 Ver1 Rev2

Adaptive Capacity Allocation Based on Uu Rate Version 1 Rev 2

Adaptive Capacity Allocation Based on Uu Rate

Uu transmission rate on MAC-hsqueue depends on:

• Channel quality of UE

• Activities of other HS users

Queue occupancy kept to a reasonable level to:

• Reduce transmission delay

• L2 signal delay

• Discarding packets due to congestion or reset during handover

Iub Bandwidth allocated based on rate of each queue on Uu Interface.

• Little data – Large B/W

• Reasonably data – match Uu B/W

• Too much data – Little or no B/W

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-49

USR7

Page 122: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Adaptive Adjustment of Available HSDPA Bandwidth

Adaptive Adjustment of Available HSDPA BandwidthBecause the NodeB dynamic bandwidth allocation is based on the service statistics, the dynamicbandwidth allocation does not reflect the real-time bandwidth occupancy need and the transport networkquality. So it is necessary for NodeB to dynamically adjust the available HSDPA bandwidth when thetraffic throughput changes or the transport network quality changes.Adaptive adjustment of Iub bandwidth available for HSDPA is a part of the mechanism to control thecongestion on Iub. The algorithm detects the Iub congestion and adjusts the available Iub bandwidthbased on the detection result.The adaptive adjustment of Iub bandwidth available for HSDPA takes effect only when the HsdpaSwitch parameter is set to DYNAMIC_BW_SHAPING or is set to BW_SHAPING_ONOFF_TOGGLEwhen congestion is detected ( BTS3812 at USR7).The output of this algorithm is an input of HSDPA flow control algorithm.

Detection of Iub CongestionThe transmission delay is detected through Delayed RNC Transmission (DRT) and frame loss isdetected through Frame Sequence Number (FSN). FSN and DRT are taken from the RNC to NodeBin a HS-DSCH frame.The algorithm periodically measures the congestion state based on transmission delay and frame loss.Frame loss is calculated as follows:

• Assume that for each MAC-d flow the HS-DSCH data frame must be delivered to the MAC-hs layerin FSN sequence.

• If the frames are not in sequence, the frames are lost. Then the number of lost frames is countedand the frame loss ratio at the Iub level in a specific time window is calculated.

Delay buildup is calculated as follows:

• The HS-DSCH data frame transmission delay is the interval from the time when HS-DSCH dataframe is generated in the RNC (identified as DRT) to the time when the frame arrives at the NodeBMAC-hs layer, including the buffer time in Iub Transport Network Layer (TNL).

• The delay buildup is the transmission delay increment comparing the sample delay with thereference one obtained when Iub is free of congestion.

Periodically the Iub congestion state is differentiated into three levels:

1. Congestion due to delay buildup means that the delay buildup is larger than the Time Delay:– Time Delay: is used to determine whether the Iub interface is congested because of delay

buildup. By default, this threshold is set to 20 ms. It can be adjusted on the basis of the delayjitter allowed on the transport network. Generally, the threshold is set to the allowed delay jitterplus several milliseconds. If the threshold is too high, the transmission on the Iub interface willbe much delayed when the Iub interface is the bottleneck. If the threshold is too low, the Iubinterface will be regarded as congested by mistake. Thus, the transmission resource cannotbe fully utilized.

2. Congestion due to frame loss that means the frame loss ratio is greater than the Discard Rate.Otherwise frame loss may be caused by an Iub bit error:– Discard Rate: is used to determine whether the Iub interface is congested because of frame

loss. Generally, frame losses due to bit error are less than those due to congestion. Bydefault, the threshold is set to 5%. It can be adjusted on the basis of transport network quality.The HS-DSCH frame error rate on the Iub interface within 300 ms can be a reference. If thethreshold is too high, the congestion on the Iub interface cannot be alleviated in time. If thethreshold is too low, the Iub interface will be regarded as congested in the case of frame lossdue to bit error. Thus, the Iub bandwidth cannot be fully utilized.

3. Congestion released means that there is no congestion due to delay buildup and no congestiondue to frame loss.

Adjustment of Available Iub bandwidthThe algorithm actively adjusts the available Iub bandwidth based on the congestion detection.

• If the Iub is in the congestion due to delay, the Iub bandwidth available for HSDPA is decreased bya step in direct proportion to the delay buildup.

• If the Iub is in the congestion due to frame loss, the Iub bandwidth available for HSDPA is decreasedby a big step regardless of the delay buildup.

2-50 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 123: SYS202m2 Usr7 Ver1 Rev2

Adaptive Adjustment of Available HSDPA Bandwidth Version 1 Rev 2

Adaptive Adjustment of Available HSDPA Bandwidth• If the Iub is in the congestion released, the Iub bandwidth available for HSDPA is increased by a

smaller step, applying the strategy of increasing slowly, yet decreasing fast.• In a time window of tens of seconds, if consecutive "congestion released" is detected, the Iub

resource is identified as not the bottleneck. In this case, Iub bandwidth available for HSDPA is equalto the bandwidth of Iub port minus the bandwidth of R99 services and flow control free services.

RNCRNC

Iub

NodeB

SET HSDPAFLOWCTRLPARA

• DYNAMIC_BW_SHAPING

• BW_SHAPING_ONOFF_TOGGLE

• Time Delay (20ms)

• Discard Rate (5%)

Congestion is detected by:

1. Jitter (Time Delay)

2. Frames discarded (Discard Rate)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-51

USR7

Page 124: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Iub Shaping

Iub ShapingThe allocation of the available Iub bandwidth to the MAC-hs queues is called Iub shaping. The availableIub bandwidth is from the algorithm of Adaptive Adjustment of Available HSDPA Bandwidth. Iub shapingensures that the total flow of the queues does not exceed the available Iub bandwidth.If the resource on the Uu interface is the bottleneck, the algorithm allocates the Iub bandwidth to MAC-hsqueue based rate on the Uu interface. The rate on the Uu interface is from Adaptive Capacity AllocationBased on Uu Rate.If the resource on the Iub interface is the bottleneck, the bandwidth allocation is based on the rate on theUu interface and the available Iub bandwidth.The algorithm considers the following factors of the MAC-hs queues:

• The bit rate allocated by Adaptive Capacity Allocation Based on Uu Rate.• NodeB buffer occupancy.• RNC buffer occupancy.• The bottleneck bandwidth available for HSDPA on the Iub interface from Adaptive Adjustment of

Available HSDPA Bandwidth.First, Iub resource for GBR is allocated. That is, the algorithm first considers the basic requirements forguaranteeing the user experience.Then, the algorithm considers the requirement for user differentiation. For all the users in the cell, thescheduler intends to allocate the Iub resource in proportion to their Weight of SPI, which is based onuser priorities, eg. gold, silver and copper.User priority differentiation is implemented when Iub is the bottleneck. The gold, silver, and copperusers obtain the resources in proportion to their priority weight factors (Weight of SPI). In addition, theresources necessary for guaranteeing the GBR must be allocated first before the resource allocationbased on the proportion. Two examples of this are given below:

• For example, assume that Iub is the bottleneck, gold, silver and copper users are using FTP servicesimultaneously. Then the Iub throughputs of gold, silver and copper users are in proportion to theratio of their SPI weights.

• For another example, assume that the silver user is using HTTP service, the gold and the copperuser are using FTP service, and the silver user is reading the HTTP page. Then the gold andcopper users share the Iub resource and the Iub throughput of the gold and copper users are inproportion to the ratio of their SPI weight.

The parameter used to set the Weight of SPI and. the range of SPI is found in the NodeB within thecommand SET MACHSSPIPARA.SSPI — The start Value of SPI Value range: 0~15Default value: 0ESPI — The end Value of SPI If end SPI and start SPI are set to the same value, you need to set onlyone SPIValue range: 0~15Default value: 15SPIWEIGHT — Weight of SPI(%)Value range: 1~100Unit: %Default value: NoneNote: The default values for Weight of SPI are found at the back of this chapter.

2-52 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 125: SYS202m2 Usr7 Ver1 Rev2

Iub Shaping Version 1 Rev 2

Iub Shaping

RNCRNC

Iub

NodeBRNC Buffer Occupancy

Bit Rate Allocated by Adaptive Capacity Allocation Based on Uu Rate

NodeB Buffer Occupancy

The bottleneck bandwidth available for HSDPA on the Iub interface from Adaptive

Adjustment of Available HSDPA Bandwidth

Capacity allocated on:

• GBR

• User differentiation based on weight of SPI

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-53

USR7

Page 126: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA MAC-hs Scheduling

HSDPA MAC-hs SchedulingOne of the most important characters of HSDPA is that the HS-DSCH channel is a shared channel amongall HS-DSCH users in a cell. Each user is possible to be scheduled in every 2 ms TTI. The resourcecompetition happens among the HSDPA users when the air interface resources available for HS-DSCHare limited. The MAC-hs scheduling algorithm is introduced to select MAC-hs queues to be scheduledin each TTI to achieve considerable cell throughput capability and to satisfy user experience.MAX C/I, Round Robin (RR), and Proportional Fair (PF) are the most popular scheduling algorithmsin industry. The scheduling principles of these three algorithms are described in the following table.

Algorithm Factor Considered inAlgorithm Scheduling Principle

MAX C/I CQI To select users according tothe CQI value in descendingorder. The radio channelquality is the only factorconsidered in this algorithmand therefore the fairnessamong users cannot beguaranteed.

RR Waiting time of data bufferedin the MAC-hs priority queue

To select users accordingto the waiting time of databuffered in the MAC-hspriority queue in descendingorder. The waiting time isthe only factor considered inthis algorithm and thereforethe fairness among users canbe guaranteed but the cellcapacity degrades becausethe channel quality is nottaken into account.

PF CQI,Average data rate ofthe MAC-hs priority queue

To select users accordingto the value of R/r indescending order, whereR is the maximum data ratecorresponding to the CQI,and r is the average data rateof the MAC-hs priority queue.The PF scheduler uses thevariation in the radio channelqualities of individual users(for example, multi-userdiversity) and providesthe user with an averagethroughput proportional to itsaverage CQI. This algorithmis a tradeoff between cellcapacity and fairness amongusers.

Enhanced Proportional Fair (EPF) is discussed overleaf.

Setting the Scheduling AlgorithmThe parameter to set which type of scheduling algorithm to use is set by the command SET MACHSPARAand is described below.SM — Scheduling MethodValue range: EPF (Enhanced PF), PF (PF), RR (Round Robin), MAXCI (Max C/I)Default value: None

2-54 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 127: SYS202m2 Usr7 Ver1 Rev2

HSDPA MAC-hs Scheduling Version 1 Rev 2

HSDPA MAC-hs Scheduling

Max C/I

Round Robin

Proportional Fair (PF)

Enhanced PF

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-55

USR7

Page 128: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Enhanced Proportional Fair (EPF)

Enhanced Proportional Fair (EPF)When the HS-DSCH carries only the BE service, the PF scheduling algorithm can make a tradeoffbetween user equity and cell throughput. When the HS-DSCH carries more types of services, suchas VoIP, streaming, SRB, and IMS, the HSDPA scheduling algorithm needs to guarantee the QoS.The reason is that such services have high requirements for delay or GBR. Based on the PF, the EPFalgorithm is designed to guarantee the QoS of the following services:

• SRB and IMS have high requirements for service connection delay and handover delay. In addition,the average traffic volume and the consumption of the Uu interface are low. Therefore, the algorithmalways selects the MAC-hs queues of SRB and IMS first.

• The VoIP service is highly delay sensitive. The maximum delay of MAC-d PDUs in a queueis specified by the discard timer of the MAC-hs queue. The scheduler needs to send out theMAC-d PDUs before the discard timer expires. The discard timer is usually shorter than 100ms. Therefore, the scheduler has little chance of considering the channel quality. The scheduleralways selects VoIP services after scheduling SRB and IMS services. Among MAC-hs queues ofVoIP, the selection is based on both delay and channel quality.

• The streaming service is usually the CBR (Constant Bit Rate) streaming service. If the rate of thisservice is not lower than the GBR, the user can obtain good experience. Therefore, the schedulerneeds to guarantee the GBR. When the average rate of the streaming service is lower than theGBR, the queues of the streaming service are selected first after SRB, IMS, and VoIP. Among theMAC-hs queues of the streaming service, the selection is based on PF.

• The BE service is allocated with the remaining resource after the resource requirements of theSRB, IMS, VoIP, and streaming services are met. Among the MAC-hs queues of the BE service,the selection is based on PF. In addition, the resource allocation complies with the following rules.Firstly, the GBR should be guaranteed first. Secondly, the algorithm considers the requirement foruser differentiation. For all the users in the cell, the scheduler intends to allocate the radio resourcein proportion to their Weight of SPI, which is based on user priorities, eg. gold, silver and copper.For example, assuming that radio resource is the bottleneck, gold , silver and copper users of samechannel quality are using FTP service simultaneously, then the Uu throughputs of gold, silver andcopper users are in proportion to the ratio of their SPI weights. For another example, assumingthat the silver user is using HTTP service, the gold and copper user are using FTP service, and thesilver user are reading the HTTP page, then the gold and copper users share the radio resource,and the Uu throughput of the gold and copper users are in proportion to the ratio of their SPI weight.

Resource Limiting SwitchIn a network, some UEs may be in a poor radio environment. More cell resources are used to ensurethe GBR of these UEs, and consequently, quite few cell resources are available for other UEs. To avoidthis problem, the resource limiting function is used. This function can be enabled through the parameterResource Limiting Switch, which can be set on the NodeB LMT.The command SET MACHSPARA is used to set the Resource Limiting Switch and is described below.RSCLMSW — Resource Limiting SwitchValue range: OPEN (OPEN), CLOSE (CLOSE)Default value: NoneResource limiting ratio is fixed according to GBR. The maximum ratio of the resource that can be usedby GBR users is shown as follows:

• 8k — 10%• 16k — 10%• 32k — 15%• 64k — 15%• 128k — 20%• 256k — 25%• 384k — 30%

2-56 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 129: SYS202m2 Usr7 Ver1 Rev2

Enhanced Proportional Fair (EPF) Version 1 Rev 2

Enhanced Proportional Fair (EPF)

RNCRNC

Iub

NodeB

If EPF set in NodeB

EPF Algorithm Selects:

1. SRB and IMS

2. VOIP based on delay and CQI

3. Streaming based on PF

4. BE based on PF and SPI weights

Resource Limiting Switch can be set so that services having a poor radio

environment cannot take the majority of system resources based

on maintaining their GBR

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-57

USR7

Page 130: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Overview of Transport Format Resource Control (TFRC) Selection

Overview of Transport Format Resource Control (TFRC)Selection

TFRC selection determines the transport block size, modulation type, HS-PDSCH codes, andHS-PDSCH transmission power. The UEs estimate and send CQI to the UTRAN to aid the TFRCselection.The HSDPA resources over the Uu interface are allocated on a per cell basis. The scheduling algorithmarranges the MAC-hs queues in a cell in a certain order and then allocates resources to users indescending order of scheduling priority. The resource allocation takes the total available Uu resources,channel quality, and amount of data cached in the MAC-hs queue into consideration, with the outputof the Transport Block Size (TBS), modulation mode, number of HS-PDSCH codes occupied, andallocated HS-PDSCH power of the HS-DSCH user within the current TTI.The Transport Format Resource Combination (TFRC) selection is based on CQI-Max TBS mappingtable, which reflects the application of Adaptive Modulation and Coding (AMC) in HSDPA. For AMC,the UE measures the downlink channel quality and provides CQI feedback in the uplink, and the networkadjusts the modulation and coding scheme for the UE based on the CQI in an adaptive manner. Forexample, when the channel quality is good, high order modulation can be applied to achieve higherthroughput.

ParametersIn general, macro cells have a poor radio environment, which results in power resource limited beforecode resource. In this situation, the downlink power of a cell is used up while the downlink code resourcesare redundant. On the contrary, indoor pico cells have a good radio environment, which results in coderesource limited before power resource. In this situation, the downlink codes resources of a cell areused up, while the power is redundant. To improve cell throughput, the Resource Allocate Methodparameter can be set on the NodeB LMT. For the scenario that the power resource is limited before thecode resource, the Resource Allocate Method may be set to CODE_prj. For the scenario that the coderesource is limited before the power resource, the Resource Allocate Method may be set to POWER_prjto improve the cell throughput.The command to set the Resource Allocation Method is SET MACHSPARA and is described below.RSCALLOCM — Resource Allocate Method, it refers to power limited cell and code limited cellValue range: CODE_Pri (Code Priority), POWER_Pri (Power Priority)Default value: None

2-58 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 131: SYS202m2 Usr7 Ver1 Rev2

Overview of Transport Format Resource Control (TFRC) Selection Version 1 Rev 2

Overview of Transport Format Resource Control (TFRC)Selection

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-59

USR7

dqfr38
Sticky Note
In NodeB
Page 132: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 TFRC Selection Process

TFRC Selection ProcessThe flowchart shows the process of TFRC selection.

1. Assuming that all the available Uu resources within the current Transmission Time Interval (TTI)are allocated to the UE, calculate the Transport Block Size maximum (TBSmax) based on theCQI from the UE and the reception capability of the UE. The calculation of TBSmax within thecurrent TTI takes the following factors into consideration:– Available power of the HS-PDSCH The HSDPA power allocated to the scheduled users within

the current TTI and the HS-SCCH power allocated to the UE within the current TTI are excluded.In addition, the total transmit power for one UE within a TTI cannot exceed the value of the MAXPOWER PER HS-USER parameter.

– Available codes of the HS-PDSCH– CQI from the UE. It is the output of the CQI adjustment algorithm within the current TTI.– UE capability. It denotes that the maximum number of HS-PDSCH code that the UE can use,

the maximum size of the transport block that the UE can receive, and whether the UE supports16QAM.

2. If there is sufficient amount of data cached in the MAC-hs queue (TBSmax < Queue length), thedata is scheduled for the UE as much as possible in the maximum format of TFRC, that is, TBS =TBSmax.

3. If there is insufficient amount of data cached in the queue (TBSmax > Queue length), the Uuresources necessary for the UE are allocated on the basis of the amount of data in the queue.Select the TFRC (power, code, and modulation mode) by searching the CQI-Max TBS mappingtable and taking the amount of data cached in the queue into consideration. The search is basedon the priority defined by the Resource Allocate Method parameter, that is, code preferable orpower preferable.Outdoor cells usually have sufficient code resources but limited power resources. Therefore, foroutdoor cells, codes take precedence over power during TFRC selection, so as to achieve resourceefficiency in both code and power and to improve the cell throughput. For indoor cells, the prioritiesof codes and power are just the opposite, that is, power usually takes precedence over codes.

4. After TFRC is determined, the matched CQI of TBS in the CQI-MaxTBS mapping table isdetermined. This CQI is expressed as CQIused. Then, the transmit power of the HS-PDSCHs iscalculated as follows:POWERHS-PDSCH = PCPICH + Γ – (CQIadjusted - CQIused).

Within one TTI, the HS-PDSCH power and HS-SCCH power allocated to one UE cannot exceed thevalue of the MAX POWER PER HS-USER parameter. The limitation on the total transmit power of asingle user is made for the following reason. In the initial deployment, only a few HSDPA users areincluded in a cell without high cell load expectation. The function of HSDPA power limitation per usercan limit the HSDPA cell load in this case. The HSDPA cell load is limited by The Offset of HSPA TotalPower parameter.

ParametersThe parameters associated with this command are found in the command SET MACHSPARA.MXPWRPHUSR — MAX POWER PER HS-USER(%)Every HSDPA user will limit the power configured by the parameter value.Value range: 1~100Default value: None

2-60 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 133: SYS202m2 Usr7 Ver1 Rev2

TFRC Selection Process Version 1 Rev 2

TFRC Selection Process

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-61

USR7

dqfr38
Text Box
4
Page 134: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 CQI Adjustment

CQI AdjustmentThe CQI indicates the number of bits that can be transmitted to the UE through certain HS-PDSCHpower, a certain modulation method (QPSK or 16QAM), and a certain number of HS-PDSCH codes withan initial transmission BLER of 10%.For the purpose of CQI reporting, the UE assumes the total received HS-PDSCH power as follows.POWERHS-PDSCH = PCPICH + Γ – (CQIadjusted - CQIused).Where:

• PCPICH is the power of the CPICH.• Γ = Max(-6, Min(13, PCellMAX - PCPICH - MPOconstant))

– MPOconstant represents HS-PDSCH MPO Constant and can be set on the RNC LMT.CQI is a key input for user resource allocation. The accuracy of CQI influences Uu resource efficiencyand user experience. For BE services, if the initial BLER is 10%, the residual BLER on the Uu interface issurely below 0.1% after retransmissions for more than three times, which is tolerable. For VoIP services,if the initial BLER is 10%, retransmissions for more than three times means that the delay of voice framesduring end-to-end transmission increases by at least 36 ms, which negatively affects user experience.Therefore, it is necessary to set Max Retransmission Count and adjust the CQI based on the servicetype. The two algorithms available for CQI adjustment are as follows:

• IBLER-based CQI adjustmentThis algorithm enables the BLER of MAC-hs PDUs during initial transfer to be converged to thetarget IBLER. The target IBLER is dynamically adjusted on the basis of the actual cell load for thepurpose of always achieving the optimal cell throughput.The algorithm adjusts the CQI based on the IBLER. In this case, with limited power, the algorithmadjusts the CQI on the assumption that the target is 10%, which can increase the throughput to anideal level.If the power is not limited and load is light, the throughput is directly related to the target IBLER.The greater the target IBLER is, the higher the retransmission ratio at the physical layer, and thelower the valid throughput is. The target IBLER should be lowered by a degree.This method can be applied to streaming, BE, SRB, and IMS services.

• RBLER-based CQI adjustmentThis algorithm enables the BLER of MAC-hs PDUs after the initial transfer and the maximumnumber of retransmissions to be converged to the Residual Bler Target. This method can beapplied to VoIP service.

ParametersThe parameters to adjust the CQI are found in the command SET MACHSSPIPARA (NodeB) and areshown below.CQIADJA — CQI Adjust Algorithm SwitchValue range: CQI_ADJ_BY_IBLER (CQI Adjusted by IBLER), CQI_ADJ_BY_RBLER (CQI Adjusted byRBLER), NO_CQI_ADJ (Not CQI Adjust Algorithm)Default value: NoneRBLERTARGET — Residual Bler TargetValue range: 1~50Default value: NoneMAXRETRANS — Max Retransmission CountValue range: 0~10Default value: None

2-62 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 135: SYS202m2 Usr7 Ver1 Rev2

CQI Adjustment Version 1 Rev 2

CQI AdjustmentCQI Tables

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-63

USR7

Page 136: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA Key Technologies

HSDPA Key TechnologiesHSDPA key technologies include:

• 2 ms TTI;• Link adaptation through HARQ and AMC at the physical layer;• Flexible scheduling by code division and time division.

Hybrid Automatic Repeat RequestIn R99, if errors occur when the UE decodes a transport block at the physical layer, the block is discarded,and the block will be retransmitted at a higher layer, for example, RLC. For HSDPA services at thephysical layer, if errors happen to decoding, the HARQ reserves the data before the decoding andcombines it with the retransmitted data.Compared with R99, HARQ retransmission is faster and more efficient than RLC retransmission. In thissense, the HARQ can be called a new technology and a combination of Forward Error Correction(FEC) and ARQ. HARQ has a higher downlink performance gain.The HARQ supports two coding combination modes as listed in the table below.

CodingCombination Description Comparison

Chasecombining

Chase combining, each retransmissionrepeats the first transmission or part ofit. While Chase combining is sufficient tomake AMC robust, IR offers the potentialfor better performance with high initialcode rates and FER operating points at thecost of additional memory and decodingcomplexity.

Advantages: Each transmissionand retransmission can be decodedindividually (self-decodable), timediversity gain, may be path diversity gain.Disadvantage: Transmission of theentire packet again which is wastage ofbandwidth.

IncrementalRedundancy(IR)

IR is the feature used to get maximumperformance out of the available bandwidth.It works by first sending only the minimumamount of redundant data, i.e. in mostcases, no redundant data. If the data is notdecoded properly, the system will resendthe same data using a different punctureor coding scheme, increasing the amountof redundant data and the likelihood ofrecovering from the errors. If data isretransmitted using a different punctureor coding scheme, it is then recombinedwith the first transmission to increaseredundancy.

Advantages: Reducing the effectivedata throughput/ bandwidth of auser and using this for another user.Disadvantage: The systematic bits areonly sent in the first transmission and notwith the retransmission, which makesthe retransmissions non-self, decodable.So, if the first transmission is lost due tolarge fading effects there is no chance ofrecovering from this situation.

The maximum amount of attempts of the HARQ process is set by the NodeB command SETMACHSPARA and is shown below.MXRETRAN — MAX Retransmission CountValue range: 0~10Default value: 14

2-64 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 137: SYS202m2 Usr7 Ver1 Rev2

HSDPA Key Technologies Version 1 Rev 2

HSDPA Key TechnologiesChase Combining HARQ

Incremental Redundancy HARQ

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-65

USR7

Page 138: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HARQ Entity and Process

HARQ Entity and ProcessEvery HSDPA user has an HARQ entity on both the UE and NodeB sides, each having up to six HARQprocesses.Several HARQ processes used together can fully utilize the transmission capability of the air interface,as shown in the diagram opposite.It takes about 12 ms for an HARQ from sending the MAC-hs PDU to receiving the ACK/NACK (RTT). Inan HARQ process, it takes only 2 ms to send data within an RTT.By using several HARQ processes, more data can be sent within an RTT:

• In this case, the first process sends data in the first 2 ms, and then starts to wait;• In the second 2 ms, the second process sends data, and then starts to wait;• With such multiple processes, each 2 ms can be used to send data to the UE.

The capability to receive the data on the HS-PDSCH every 2 ms depends on UE categories. UEs ofsome categories can only receive such data every 4 ms or 6 ms.

2-66 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 139: SYS202m2 Usr7 Ver1 Rev2

HARQ Entity and Process Version 1 Rev 2

HARQ Entity and ProcessHARQ Overview

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-67

USR7

dqfr38
Text Box
HARQ Process is a parallel 6 HARQs in 3G and 8 in LTE
dqfr38
Text Box
There is reordering in the UE
Page 140: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA Power Allocation

HSDPA Power AllocationThe power resources in this section refer to the power available in a cell. For example, the HSDPA powerrefers to the maximum transmit power that can be used by HS-SCCH and HS-PDSCH in a cell.

• The actual power of DPCH is adjusted through the inner and outer loop power control algorithm.• The actual power of the HSDPA channel is allocated dynamically among users by the NodeB

scheduling algorithm.

Introduction to Cell Total Power ResourcesThe cell total transmit power is the constant resources. The DL power consists of the following threeparts:

• Power of the HSDPA DL physical channel (HS-SCCH and HS-PDSCH);• Common channel power;• DPCH power.

Among the three parts, common channel power is reserved and the maximum available power of HSDPADL physical channel can be set on the RNC LMT.

HSDPA Dynamic Power Resources AllocationExcept for reserving for the common channels, the rest of the power resources of the cell are allocateddynamically between the DPCH and HSDPA DL physical channels. The power allocated for HSDPAcannot exceed the value of the HS-PDSCH And HS-SCCH Power. Moreover, the DPCH has higherpriority to use the rest of the power resources.As shown in the slide opposite, the NodeB detects the R99 power load every 2ms to determine theavailable power for HSDPA. In this way, the cell load is more stable. To obtain the available power forHSDPA, a power margin must be set aside to handle power increase caused by R99 power control ineach 2ms. The Power Margin parameter can be set on the NodeB LMT.The parameter to set the HS-PDSCH and the HS-SCCH power is found in the ADD CELLHSDPAcommand and is described below.HspaPower — .Total power of HSPA equals the cell maximum TX power and this parameter value. Thisparameter is the maximum value for dynamic power adjustment,which affects the throughput of HSDPAsubscribers on the edge of a cell. For detailed information of this parameter, refer to 3GPP TS 25.308.Value range: 0~500Physical value range: 0~50, step: 0.1Physical unit: dBmContent: noneRecommended value (default value): 430The parameter to set the power margin is set in the NodeB LMT and is found in the command SETMACHSPARA and is described below.PWRMGN — Power Margin RatioValue range: 0~100Default value: 10

2-68 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 141: SYS202m2 Usr7 Ver1 Rev2

HSDPA Power Allocation Version 1 Rev 2

HSDPA Power Allocation

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

2-69

USR7

Page 142: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Default Mapping Tables

Default Mapping TablesDefault mapping of traffic class, user priority, and THP to SPI

Traffic Class User Priority THP SPI

SRB signaling No ARP None 15

IMS signaling No ARP None 14

1 None 13

2 None 13

Conversational (VoIP)

3 None 13

1 None 12

2 None 11

Streaming

3 None 11

1 1 10

1 2 9

1 3 to 15 8

2 1 7

2 2 6

2 3 to 15 5

3 1 4

3 2 3

Interactive

3 3 to 15 2

1 None 8

2 None 5

Background

3 None 2

Note: SPI 0 and SPI 1 are not used.Default setting of algorithm based on SPI.

SPICQI AdjustAlgorithmSwitch

ResidualBlerTarget

MaxRetransCount

EPF Schedule AlgorithmSwitch

Flow Control AlgorithmSwitch

Weightof SPI

15 NO_CQI_ADJ NA 4 DS_PQ_SCHEDULE FLOW_CONTRL_FREE 100%

14 NO_CQI_ADJ NA 4 DS_PQ_SCHEDULE FLOW_CONTRL_FREE 100%

13 NO_CQI_ADJ 7 2 DS_URGENT_SCHEDULE FLOW_CONTRL_FREE 100%

12 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 100%

11 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 90%

10 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 100%

9 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 100%

8 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 100%

7 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 90%

6 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 90%

5 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 90%

4 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 80%

3 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 80%

2 NO_CQI_ADJ NA 4 TS_SCHEDULE FLOW_CONTRL_DYNAMIC 80%

2-70 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 143: SYS202m2 Usr7 Ver1 Rev2

HSUPA Version 1 Rev 2

Chapter 3

HSUPA

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-1

USR7

Page 144: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSUPA

This page intentionally left blank.

3-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 145: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter Objectives

• Describe the key technologies used in HSUPA• Describe the RAN architecture impacts• Describe the HSUPA transport and physical channels• Describe the different TTIs available for HSUPA

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-3

USR7

Page 146: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Introduction

IntroductionAfter the first release of HSDPA in 3GPP R5 in mid 2002 work started on the High Speed Uplink PacketAccess (HSUPA) and over the course of the next 3 years the concept materialized into the specificationsand was realized in 3GPP R6.

HSUPA vs R99 DCHHSUPA is not a standalone feature, but uses the basic features of R99 to operate. Cell selection, randomaccess and basic mobility features etc are used and remain unchanged with HSUPA operation. Thechange occurs in the way the user data is delivered from the UE to the NodeB on the uplink.HSUPA provides a flexible path beyond the 384 kbps uplink which is the realistic maximum beforeHSUPA. A similar technology to that of HSDPA is being used by introducing fast uplink HARQ, NodeBbased uplink scheduling and easier multicode transmission than that of R99.

Key TechnologiesThe new uplink transport channel Enhanced DCH (E-DCH) brings some of the same features to theuplink as the HSDPA with its new transport channel HS-DSCH to the downlink. The E-DCH supportsfast NodeB based scheduling,fast physical layer HARQ with incremental redundancy and at USR6.1 ashorter 2ms TTI. E-DCH is not a shared channel like HSDPA, but it is in fact a dedicated channel andcan therefore support technologies like fast power control, variable SFand soft handovers.

Uplink SchedulingThe uplink scheduling mechanism is of central importance for HSUPA. The uplink scheduler is locatedin the Node B close to the air interface in a similar way as HSDPA.Task of the uplink scheduler is to control the uplink resources the UEs in the cell are using. The schedulertherefore grants maximum allowed transmit power ratios to each UE. This effectively limits the transportblock size the UE can select and thus the uplink data rate.The scheduling mechanism is based on absolute and relative grants. The absolute grants are usedto initialize the scheduling process and provide absolute transmit power ratios to the UE, whereas therelative grants are used for incremental up- or downgrades of the allowed transmit power.Note that one UE has to evaluate scheduling commands possibly from different radio links. This is dueto the fact that uplink macro diversity is used in HSUPA.

Hybrid Automatic Repeat Request (HARQ)The HARQ protocol is a retransmission protocol improving robustness against link adaptation errors. TheNode B can request retransmissions of erroneously received data packets and will send for each packeteither an Acknowledgement (ACK) or a Negative Acknowledgement (NACK) to the UE. Furthermore,the Node B can do soft combining, i.e. combine the retransmissions with the original transmissions inthe receiver.Due to uplink macro diversity, one UE has to evaluate ACK/NACK information for the same packetpossibly from different radio links.

Reduction of Transmission Time IntervalTo accelerate packet scheduling and reduce latency, HSUPA allows for a reduced TTI of 2 mscorresponding to 3 timeslots. A WCDMA radio frame of 10 ms therefore consists of 5 subframes.Unlike HSDPA, however, the support of this 2 ms TTI in the UE is not mandatory. Instead, it is aUE capability. It is configured at call setup whether 2 ms TTI or 10 ms TTI is to be used for HSUPAtransmission.

3-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 147: SYS202m2 Usr7 Ver1 Rev2

Introduction Version 1 Rev 2

Introduction

RNCRNCCNCN

Iu

Iub

NodeB

• Variable SF

• HARQ

• BTS Based Scheduling

• Fast Power Control

• Soft Handover

• TTI Length of 2 and 10ms

60 Users Per Cell5.76 Mbps Per User

USR 7

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-5

USR7

Page 148: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Impact on Radio Access Network Architecture

Impact on Radio Access Network ArchitectureBoth the uplink scheduling and the HARQ protocol are located in the Node B, in order to move processingcloser to air interface and be able to react faster on the radio link situation.Macro diversity is exploited for HSUPA, i.e. the uplink data packets can be received by more than 1 cell.There is one serving cell controlling the serving radio link assigned to the UE. The serving cell is havingfull control of the scheduling process and is providing the absolute grant to the UE. The serving radio linkset is a set of cells contains at least the serving cell and possibly additional radio links from the sameNode B. The UE can receive and combine one relative grant from the serving radio link set.There can also be additional non-serving radio links at other Node Bs. The UE can have zero, one orseveral non-serving radio links and receive one relative grant from each of them.Different Node Bs will deliver correctly received data packets to the RNC. Therefore some selectivecombining functionality is needed in the RNC to sort out duplicates.

3-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 149: SYS202m2 Usr7 Ver1 Rev2

Impact on Radio Access Network Architecture Version 1 Rev 2

Impact on Radio Access Network Architecture

CN

UTRAN Radio Network Controller (RNC)

• Selective Combining

Node B (of serving radio link set):

• Scheduling: absolute/relative grants;

• HARQ: Soft-combining, generation of ACK/NACK

Node B (of non-serving radio link set):

• Scheduling: absolute/relative grants;

• HARQ: Soft-combining, generation of ACK/NACK

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-7

USR7

Page 150: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSUPA Protocol Architecture

HSUPA Protocol ArchitectureThe HSUPA related functionalities in Node B and RNC are also reflected in the protocol architectureas shown in the slide opposite (Serving and Controlling RNC are the same). New protocol entities arehighlighted by shading).Node B contains a new MAC entity called MAC-e, and the RNC contains a new MAC entity calledMAC-es. Both MAC-e and MAC-es entities terminate within the MAC layer of the UE.

UEA new MAC entity (MAC-es/MAC-e) is added in the UE located below MAC-d. MAC- es/MAC-e in theUE handles HARQ retransmissions, scheduling and MAC-e multiplexing, E-DCH TFC selection.

Node BA new MAC entity (MAC-e) is added in Node B which handles HARQ retransmissions, scheduling andMAC-e demultiplexing.

S-RNCA new MAC entity (MAC-es) is added in the SRNC to provide in-sequence delivery (reordering) and tohandle combining of data from different Node Bs in case of soft handover.

3-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 151: SYS202m2 Usr7 Ver1 Rev2

HSUPA Protocol Architecture Version 1 Rev 2

HSUPA Protocol Architecture

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-9

USR7

Page 152: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSUPA Channels

HSUPA ChannelsAs said before, HSUPA is a new uplink transport channel, E-DCH, which supports enhanced features tothose of the uplink transport channels of R99. Uplink transport channel processing for E-DCH is similar tothe processing of the uplink DCH with two exceptions. There can be only one E-DCH transport channelin the UE, unlike DCHs that are multiplexed together to a Single Coded Composite Transport Channel(CCTrCH) of DCH type. Nevertheless, the MAC layer can multiplex multiple parallel services to the singleE-DCH. The other significant difference is HARQ support for the E-DCH which is provided in the transportchannel processing chain.After transport channel processing, the E-DCH maps to one or multiple parallel new dedicated physicaldata channels – E-DPDCHs – for physical layer transmission. This is completely parallel to uplink DCHprocessing chain and physical channels, so both E-DCH and DCH can coexist in the same UE with therestriction that the maximum DCH data rate is 64 kbps when the E-DCH is configured.Using E-DPDCH transmissions a simultaneous and parallel control channel is sent a separate codechannel – E-DPCCH. This E-DPCCH transmits all the necessary information about the E-DPDCH thatis needed in order to know how to receive the data channel.In the downlink, 3 new channels are introduced for control purposes:

• E-AGCH: E-DCH Absolute Grant Channel is a common shared channel and distinguishesusers through the CRC related to E-RNTI. The E-AGCH is located in the serving E-DCH cell, itindicates the maximum uplink power to be used by UE in the next data transfer. (E-DCH trafficPilot Ratio—EDPDCH/DPCCH) and uses a fixed rate (SF=256);

• E-RGCH: E-DCH Relative Grant Channel is a dedicated channel (shared by multiple UEs), andcarries Relative Grants. The uplink available power of UE can be adjusted within a minimum of2ms. The fixed rate is SF=128;

• E-HICH: E-DCH Hybrid ARQ Indicator Channel is a dedicated channel. E-HICH is used to feedback the ACK/NACK information that indicates whether the data of user reception process is correct.The fixed rate is SF=128.

E-AGCH is only transmitted from the serving cell. E-RGCH and E-HICH are transmitted from radio linksthat are part of the serving radio link set and from non-serving radio links.Note that HSUPA channels are added on top of uplink / downlink dedicated channels. Each UE thereforeadditionally carries an uplink and downlink Dedicated Physical Channel (DPCH). In the downlink, aFractional Dedicated Channel (F-DPCH) can be used alternatively. The F-DPCH has been introducedin 3GPP release 6 in order to optimize the downlink channelization code usage. With this concept, severalUEs can share one downlink channelization code of SF 256. For this purpose, the F-DPCH uses a newslot format only containing the Transmit Power Control (TPC) bits. Unlike the regular downlink DPCHslot formats, no pilot or data fields are present. By assigning a UE specific timing offset, it is possible tomultiplex up to 10 UEs onto one channelization code for FDPCH. The F-DPCH is available in USR7.

3-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 153: SYS202m2 Usr7 Ver1 Rev2

HSUPA Channels Version 1 Rev 2

HSUPA Channels

Node B withnon-serving E-DCH radio link

Node B withserving E-DCH radio link set

E-DCH Relative Grant Channel – Relative grants

E-DCH Relative Grant Channel – Relative grants

E-DCH Hybrid ARQ Indicator Channel – ACK/NACK

E-DCH Hybrid ARQ Indicator Channel – ACK/NACK

E-DCH Absolute Grant Channel – Absolute grants

E-DCH Dedicated Physical Data Channel – Uplink data

E-DCH Dedicated Physical Data Channel – Uplink data

E-DCH Dedicated Physical Control Channel – Uplink RSN, E-TFCI, Happy Bit

E-DCH Dedicated Physical Control Channel – Uplink RSN, E-TFCI, Happy Bit

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-11

USR7

Page 154: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 E-DCH Dedicated Physical Data Channel (E-DPDCH)

E-DCH Dedicated Physical Data Channel (E-DPDCH)The E-DPDCH has a very similar structure to the DPDCH of R99 with a few exceptions. They bothsupport OVSFs to adjust the number of channel bits to the amount of data actually being transmitted.They both could go beyond the data rate that one physical data channel can support by transmittingmultiple channels in parallel. They both use BPSK modulation and follow the same fast power controlloop.The main difference are; the E-DPDCH supports fast physical layer level HARQ and fast Node B basedscheduling. However, these are not really properties of the physical data channel as such, but the HARQis visible in the transport channel processing chain and the scheduling is visible in the MAC layer.The biggest difference for E-DPDCH is the support of a SF of 2, which allows delivering twice as manychannel bits per code than the minimum spreading factor of 4 that the DPDCH supports. The maximumpossible data rate of 5.76 Mbps is achieved by allocating 2*SF2 and 2*SF4. The same result could beachieved by using 6 SF4 codes with DPDCH, but the power efficiency of the UE would be reduced incomparison to using SF2.An E-DCH transport block with user data is mapped onto one sub-frame of 2 ms in case a TTI of 2 mshas been configured, or onto one radio frame of 10 ms in case a TTI of 10 ms has been configured.The amount of data bits that can be carried within one timeslot depends on the selected slot format. Theslot format determines the Spreading Factor (SF) and therefore the amount of bits per slot. The slotformat is shown in the table below.

The E-DPDCH is time aligned with the uplink Dedicated Physical Control Channel (DPCCH).

3-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 155: SYS202m2 Usr7 Ver1 Rev2

E-DCH Dedicated Physical Data Channel (E-DPDCH) Version 1 Rev 2

E-DCH Dedicated Physical Data Channel (E-DPDCH)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-13

USR7

Page 156: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 E-DCH Dedicated Physical Control Channel (E-DPCCH)

E-DCH Dedicated Physical Control Channel (E-DPCCH)The E-DPCCH is a new uplink physical channel used for transmitting out-of-band information aboutE-DPDCH transmission from the mobile to the base station.The E-DPCCH has only one possible slot format, which uses a spreading factor of 256 with achannelization code of 1 and is capable of delivering 30 channel bits in a 2-ms sub-frame. It is designedto deliver 10 bits of information for each E-DPDCH TTI transmitted. The E-DPCCH uses the same (30,10) second-order Reed–Muller coding as used for TFCI coding in the DPCCH. This means that the10 information bits result in 30 bits to be transmitted in the physical channel. This number of bits canbe carried by the E-DPCCH in 2 ms sub frames. If the TTI length of the E-DPDCH is 10 ms, then the30-bit E-DPCCH sub-frame is repeated five times allowing reduced power level. With this procedurethe same E-DPCCH structure can be employed regardless of the TTI used for E-DPDCH transmission.The E-DPCCH frame structure is illustrated opposite.The 10 information bits on the E-DPCCH consist of three different segments::

• The Retransmission Sequence Number (RSN) the retransmission sequence number of 2 bitsinforming the HARQ sequence number of the transport block currently being sent on E-DPDCHs.The initial transmission of a transport block is sent with RSN = 0, the first retransmission with RSN= 1, the second retransmission with RSN = 2, and all subsequent transmissions with RSN = 3.;

• An E-DCH Transport Format Combination Indicator (E-TFCI) 7 bits indicating the transportformat being transmitted simultaneously on E-DPDCHs. In essence, the E-TFCI tells the receiverthe transport block size coded on the E-DPDCH. From this information the receiver can derivehow many E-DPDCHs are transmitted in parallel and what spreading factor is used;

• Happy bit – as inferred from the name – is 1 bit only. It indicates whether the UE is content withthe current data rate (or relative power allowed to be used for E-DPDCHs) or whether it could usehigher power allocation.This field takes two values: Unhappy and Happy. The Unhappy value indicates a higher data ratethan the currently desired serving grant because there is much data in the buffer and the UE hasenough power. Otherwise, it should be the Happy value.For every E-DCH transmission, the happy bit should be set to Unhappy if the following three criteriaare met:– The UE transmits as much scheduled data as allowed by the current serving grant during E-TFC

selection;– The UE has enough power to transmit data at a high rate;– Based on the power offset selected during E-TFC selection to transmit data in the TTI of the

happy bit, the Total E-DCH Buffer Status may require more than Happy_Bit_Delay_Conditionms to be transmitted with the current Serving_Grant multiplied by the ratio of the number ofactive processes to the total number of processes.

The E-DPCCH is time aligned with the uplink DPCCH.All channels transmitted in uplink (E-DPDCH, E-DPCCH, HS-DPCCH, DPCCH, possibly DPDCH) areIQ multiplexed.

3-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 157: SYS202m2 Usr7 Ver1 Rev2

E-DCH Dedicated Physical Control Channel (E-DPCCH) Version 1 Rev 2

E-DCH Dedicated Physical Control Channel (E-DPCCH)

• Retransmission Sequence Number (RSN) – 2 bits

• E-DCH Transport Format Indicator (E-TFCI) – 7 bits

• Happy Bit - 1 bit

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-15

USR7

Page 158: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 E-DCH Absolute Grant Channel (E-AGCH)

E-DCH Absolute Grant Channel (E-AGCH)The E-AGCH is a downlink physical channel used for transmitting an absolute value of the Node Bscheduler’s decision that lets the UE know the relative transmission power it is allowed to use for datachannel transmission (E-DPDCH), thus effectively telling the UE the maximum transmission data rate itmay use.The E-AGCH delivers 5 bits to the UE for the absolute grant value, indicating the exact power levelthe E-DPDCH may use in relation to the DPCCH. In addition, the E-AGCH carries a 1-bit indication forthe absolute grant scope. With this bit the Node B scheduler can allow/disallow UE transmission in aparticular HARQ process. This bit is only applicable for 2-ms TTI E-DCH operation. In addition to thisthe E-AGCH uses a primary and a secondary UE-id for identifying the intended receiver and deliveringone additional bit of information.The E-AGCH uses a fixed spreading factor of 256 and QPSK modulation.The absolute grant consists of a 5 bit grant value according to the table below and 1 bit indicating thescope of the grant. The scope of the absolute grant tells the UE whether the absolute grant is valid fora specific HARQ process or for all HARQ processes.The absolute grant is channel coded with convolutional coding of code rate 1/3. The resulting 60 bits aretransmitted in a 2 ms sub-frame in case of 2 ms TTI, or repeated in all 5 sub-frames in case of 10 ms TTI.Absolute grant value — is a 5-bit integer number ranging from 0 to 31 that has a specific mapping (asshown below) to the E-DPDCH/DPCCH power ratio the UE may use.

Absolute grant scope — can be used to activate/de-activate a particular HARQ process (identified bythe E-AGCH timing) or all HARQ processes. The absolute grant scope can only be used with a 2-msE-DCH TTI.Primary/Secondary UE-id or primary/secondary E-RNTI — is used to mask the CRC of the E-AGCH.Each UE may have up to two UE-ids which it checks from each E-AGCH and if it detects one or the otheras matching the transmission it knows that the E-AGCH transmission was destined for it.The structure of an E-AGCH is very similar to an HS-SCCH for HSDPA. A 16-bit CRC is calculatedover the 6 information bits and masked with either a primary or a secondary UE-id.With these ids theUE knows whether the E-AGCH transmission was meant for it or not. The package is then coded andrate-matched to fit the three-slot-long (2-ms) SF 256 channel. If a 10-ms E-DCH TTI is used the threeslots are repeated five times to fill the whole radio frame.For both 2 ms and 10 ms TTI, the E-AGCH timing is 5120 chips offset from P-CCPCH frame timing.

3-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 159: SYS202m2 Usr7 Ver1 Rev2

E-DCH Absolute Grant Channel (E-AGCH) Version 1 Rev 2

E-DCH Absolute Grant Channel (E-AGCH)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-17

USR7

Page 160: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 E-DCH Relative Grant Channel (E-RGCH)

E-DCH Relative Grant Channel (E-RGCH)At a fixed rate (60 kbit/s, SF = 128) dedicated downlink physical channel, the E-DCH Relative GrantChannel (E-RGCH) carries relative grants for uplink E-DCH scheduling. the frame structure of theE-RGCH is shown below.

• A relative grant is transmitted in 3, 12, or 15 consecutive slots. In each slot, a sequence of 40 binaryvalues is transmitted.

• If the cell transmitting the E-RGCH is in the E-DCH serving Radio Link Set (RLS), 3 or 12 slots areused, depending on whether the E-DCH TTI is 2 ms or 10 ms.

• If the cell transmitting the E-RGCH is not in the E-DCH serving RLS, 15 slots are used.The Relative Grant (RG) commands are mapped to the relative grant values.When the UE receive a RG commands, the serving grant should be adjusted upwards or downwards bya step. The step may be 1, 2 or 3 indexes in the SG table according to the current SG value and theconfiguration of E-RGCH 3-Index-Step Threshold and E-RGCH 2-Index-Step Threshold.

3-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 161: SYS202m2 Usr7 Ver1 Rev2

E-DCH Relative Grant Channel (E-RGCH) Version 1 Rev 2

E-DCH Relative Grant Channel (E-RGCH)

-1-1DOWN

00HOLD

Not Allowed1UP

RG Value (for other Radio Links)

RG Value (for Serving E-DCH RLS)

RG Command

-1-1DOWN

00HOLD

Not Allowed1UP

RG Value (for other Radio Links)

RG Value (for Serving E-DCH RLS)

RG Command

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-19

USR7

Page 162: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 E-DCH HARQ Indicator Channel (E-HICH)

E-DCH HARQ Indicator Channel (E-HICH)The E-HICH is a new downlink physical channel used for transmitting positive and negativeacknowledgements for uplink packet transmission. If the Node B received the transmitted E-DPDCH TTIcorrectly it will respond with a positive Acknowledgement (ACK) and if it received the TTI incorrectly itwill respond with a Negative Acknowledgement (NACK).E-HICH information is BPSK-modulated with on/off keying and the modulation depends on which cell istransmitting the E-HICH. If the E-HICH is coming from the radio link set contained in the serving E-DCHradio link (transmitted from the base station that has the serving E-DCH cell), then both ACKs and NACKsare transmitted. The E-HICHs transmitted by Node Bs that do not contain the serving E-DCH cell onlytransmit ACKs. If such a cell does not receive the E-DPDCH TTI correctly, then it does nothing. The UEwill continue retransmitting until at least one cell responds with an ACK.The purpose of this arrangement is to save downlink transmission power. The assumption behind thedifferent modulations is that those Node Bs that do not have the serving E-DCH cell are typically theones that do not have the best connection to the UE and are more likely not to receive the E-DPDCH TTIcorrectly and have a significantly larger portion of NACKs than ACKs to be transmitted. In this way onlythe ACKs actually consume downlink capacity. As for the serving E-DCH radio link set the assumptionis that typically more ACKs than NACKs are transmitted. When both ACK and NACK actually result inBPSK bit transmission (+1 and –1, respectively) the peak power required to transmit a reliable ACK issmaller when the receiver needs to separate +1 from –1 than would be the case if it needed to separate+1 from 0 (as no transmission).

All the cells in the same Node B are assumed to receive uplink E-DPDCH transmission in cooperationand, thus, even if there are multiple cells in the Node B participating in a softer handover the TTI receptioneither succeeds or fails only once, not separately in all the cells. Due to this all E-HICHs transmitted fromthe Node B containing the serving E-DCH cell transmit both ACKs and NACKs, effectively enabling theUE to combine the radio links for more reliable ACK/NACK detection.E-HICH and E-RGCH channel structures are exactly the same and are shown opposite. Each delivers1 bit of information in three slots. In the case of a 10-ms TTI the three slots are repeated four timesresulting in an 8-ms-long message. The exception is the E-RGCH transmitted from cells not belongingto the serving E-DCH radio link set. That channel always – regardless of the E-DCH TTI – transmits a10-ms-long message (i.e., the three slots are always repeated five times).The E-HICH/E-RGCH basic building block is a 40-bit-long orthogonal sequence which allows theorthogonal multiplexing of 40 bits in one slot on a single spreading factor 128-code channel. The sameE-HICH/E-RGCH bit is repeated three times over three slots, but uses a different signature in each ofthe three slots following a deterministic code hopping pattern. This is because different signature pairshave different isolations in a real radio environment and, thus, the effect is averaged this way.E-HICHs and E-RGCHs utilize 40-bit-long orthogonal sequences for multiplexing multiple E-HICHs andE-RGCHs (40 in total) to a single downlink code channel of spreading factor 128.One cell can use multiple channelization codes to exceed the limit of 40 signatures (e.g., 20 E-HICHsand 20 E-RGCHs in a code) with the constraint that the E-HICH and E-RGCH intended for the same UEmust be transmitted with the same channelization code.

3-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 163: SYS202m2 Usr7 Ver1 Rev2

E-DCH HARQ Indicator Channel (E-HICH) Version 1 Rev 2

E-DCH HARQ Indicator Channel (E-HICH)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-21

USR7

Page 164: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Reason for having 2 ms amd 10 ms TTIs

Reason for having 2 ms amd 10 ms TTIsWhile HSDPA only supports a single TTI (2 ms), with HSUPA there are two TTI lengths – 2 and 10 ms –that can be chosen. The motivation for the 2-ms length was the potential delay benefit while 10 ms wasneeded for range purposes to ensure cell edge operation.A potential delay benefit could be obtained if there are not too many retransmissions using a 2-ms TTI,as the delay between retransmissions is shorter compared with the 10- ms case. A problem occurs whenapproaching the cell edge where signalling using a 2-ms period starts to consume a lot of transmissionpower, especially at the Node B. The difference from HSDPA is that now potentially a much larger numberof users are expected to be active simultaneously and, thus, aiming to also provide downlink signallingto such a large number of users using a 2-ms period would become impossible.With data rates below 2Mbps there are no major differences from the capacity point of view regardlessof the TTI used. When going above 2 Mbps per user, then the block size using 10 ms would get too bigand, thus, data rates above 2 Mbps are only provided using a 2-ms TTI. As with macro-cells, practicaldata rates in the uplink have limitations due to transmission power limitations. This means the 10-msTTI is expected as the starting value for system deployment; this has also been reflected in terminalcapabilities (where a 2-ms TTI is optional for most categories).

The parameter to enable 2ms TTI is found in the command SET CORRMALGOSWITCH and is shownbelow.HspaSwitch — HSUPA_TTI_2MS_SWITCH. When it is checked, the 2ms TTI could be applied toHSUPA traffic.

3-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 165: SYS202m2 Usr7 Ver1 Rev2

Reason for having 2 ms amd 10 ms TTIs Version 1 Rev 2

Reason for having 2 ms amd 10 ms TTIs

NodeB

E-DCH/HSDPA Serving Cell

E-DCH Control

DCH/HSDPA

E-DCH/DCH

Area where only a 10ms TTI is acceptable

Area where both a 2ms and a 10ms TTI is acceptable

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-23

USR7

Page 166: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Configuration of HSUPA Cells

Configuration of HSUPA CellsThe command to add a cell as HSUPA capable is ADD CELLHSUPA and is described below.EagchCodeNum — Value range: 1~8.Physical unit: None.Content: The number of E-AGCH code.Recommended value: 1.ErgchEhichCodeNum — Value range: 1~8.Physical unit: None.Content: The number of E-RGCH/E-HICH code.Recommended value: 1.MaxTargetUlLoadFactor — Value range: 0~100.Physical value range: 0~1, step: 0.01.Physical unit: %.Content: The Maximum Target Uplink Load Factor.Recommended value: 75.NonServToTotalEdchPwrRatio — Value range: 0~100.Physical value range:0%~100% .Physical unit: %.Content: The target non-serving E-DCH to total E-DCH power ratio.Recommended value: 0.The types of service that use HSUPA are BE, Streaming and conversational. Streamingand conversational are optional services and can be enabled using the command SETCORRMALGOSWITCH, the parameter is described below.PS_CONVERSATION_ON_E_DCH_SWITCH — When it is checked, PS conversation traffic can bemapped to E-DCH when the uplink max bit rate is more than or equal to the conversation on HSUPAthreshold.The decision to use HSUPA is dependant on bit rates and whether the service is BE or streaming it isset using the SET FRC command. The parameters are described below.UlStrThsOnHsupa — Value range: D8, D16, D32, D64, D128, D144, D256, D384.Physical value range: 8, 16, 32, 64, 128, 144, 256, 384.Physical unit: kbit/s.Content: The rate decision threshold of UL PS domain streaming service to be carried on E-DCH. Whenthe maximum UL service rate is greater than or equal to this threshold, the service will be carried onE-DCH; otherwise, on DCH.Recommended value: D256.UlBeTraffThsOnHsupa — Value range: D8, D16, D32, D64, D128, D144, D256, D384, D608, D1450,D2048, D2890, D5760.Physical value range: 8, 16, 32, 64, 128, 144, 256, 384, 608, 1450, 2048, 2890, 5760.Physical unit: kbit/s.Content: The rate decision threshold of UL PS domain background/interactive service to be carried onE-DCH. When the maximum UL service rate is greater than or equal to this threshold, the service will becarried on E-DCH; otherwise, on DCH.Recommended value: D768.VoipChlType — Value range: DCH, HSDPA, HSPAPhysical unit: None.Content: Indicating the channel type of VOIP service. -DCH: Both uplink and downlink are bourne onDCH. -HSDPA: Uplink is bourne on DCH, downlink bourne on HS-DSCH. -HSPA:Uplink is bourne onE-DCH, downlink bourne on HS-DSCH.Recommended value: DCH.ImsChlType — Value range: DCH, HSDPA, HSPAPhysical unit: None.Content: Indicating the channel type of IMS signalling service. -DCH: Both uplink and downlink arebourne on DCH. -HSDPA: Uplink is bourne on DCH, downlink bourne on HS-DSCH. -HSPA:Uplink isbourne on E-DCH, downlink bourne on HS-DSCH.Recommended value: DCHThe decision whether to allow 2ms TTI is found in the command SET CORRMALGOSWITCH and isdescribed below.HSUPA_TTI_2MS_SWITCH — When it is checked, the 2ms TTI could be applied to HSUPA traffic.Other parameters that effect such things as power control and handovers are covered in SYS202m2.

3-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 167: SYS202m2 Usr7 Ver1 Rev2

Configuration of HSUPA Cells Version 1 Rev 2

Configuration of HSUPA Cells

RNCRNCCNCN

Iu

Iub

NodeB

HSUPA

ADD CELLHSUPA: CellId=1011, EagchCodeNum=1, ErgchEhichCodeNum=1, MaxTargetUlLoadFactor=75, NonServToTotalEdchPwrRatio=0;

SET CORRMALGOSWITCH: HspaSwitch=PS_STREAMING_ON_E_DCH_SWITCH-1;

SET FRCCHLTYPEPARA: VoipChlType=HSPA; ImsChlType=HSPA; SrbChlType=HSPA; UlStrThsOnHsupa=D256, UlBeTraffThsOnHsupa=D608; UlConvThsOnHsupa=D64;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

3-25

USR7

Page 168: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Configuration of HSUPA Cells

This page intentionally left blank.

3-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 169: SYS202m2 Usr7 Ver1 Rev2

Load Control Version 1 Rev 2

Chapter 4

Load Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-1

USR7

Page 170: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load Control

This page intentionally left blank.

4-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 171: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter Objectives

• Describe process of load control as a whole• Describe PUC• Describe Call Admission Control• Describe Intelligent Admission Control• Describe LDR• Describe Overload Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-3

USR7

Page 172: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Definition

DefinitionThe WCDMA system is a self interference system. With the load of the system increasing, theinterference rises. If the interference is high enough, it affects the coverage and QoS of establishedservices. Therefore, capacity, coverage and Quality of Service (QoS) of the WCDMA system aremutually affected. The purpose of load control is to maximize system capacity while ensuring thecoverage and QoS.In different phases of UE access as shown in the diagram below, different load control algorithms areused as follows:

• Before UE access: Potential User Control (PUC).• During UE access: Call Admission Control (CAC) and Intelligent Access Control (IAC)• After UE access: Intra-frequency Load Balancing (LDB), Load Reshuffling (LDR), and

Overload Control (OLC).

4-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 173: SYS202m2 Usr7 Ver1 Rev2

Definition Version 1 Rev 2

DefinitionLoad Control Phases

1. Before UE access 2. During UE access 3. After UE access

PUC CAC

IAC

LDR

OLC

time

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-5

USR7

Page 174: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Overview of Load Control

Overview of Load ControlThe load control algorithm is built into the RNC. The input of load control comes from the measurementinformation taken from the NodeB.Load control has the following sub-features:

• PUC — The function of PUC is to balance traffic load among inter-frequency cells. By modifyingcell selection and reselection parameters and broadcasting them through system information, PUCleads UEs to cells with light load. The UEs may be in idle mode, CELL_FACH state, CELL_PCHstate, or URA_PCH state.

• CAC — The function of CAC is to decide on resource requests from UEs, such as access,reconfiguration, and handover requests, according to the resource status of the cell.

• IAC — The purpose of IAC is to increase the access success rate with the current QoS assuredthrough rate negotiation, queuing, pre-emption, and DRD.

• LDR — The function of LDR is to reduce the load of a cell when the available resource of the cellreaches the specified alarm threshold. The purpose of LDR is to increase the access success ratein the following ways:– Inter-frequency load handover– Code reshuffling– BE service rate reduction– AMR voice service rate reduction– Uncontrolled realtime traffic QoS renegotiation– CS inter-system load handover– PS inter-system load handover– MBMS power reduction.

• OLC — The function of OLC is to reduce the cell load rapidly by restricting the Transport Format(TF) of the BE service, switching BE services to common channels or releasing UEs when the cellis overloaded. The purpose of OLC is to ensure the stability of the system and the QoS of mostUEs.

4-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 175: SYS202m2 Usr7 Ver1 Rev2

Overview of Load Control Version 1 Rev 2

Overview of Load Control

NodeB transmit power (noise)

Cell Load (number of subscribers)

PUC starts: to enable UEs in idle mode to camp on cells with light load Cell breathing starts: to switch loads of hot spot cells to othe r cells LDR starts: to check and release initial congestion in cells

Load control is unneeded

CAC: to prevent new calls into cells with heavy loadDRD starts: to enable rejected UEs toretry neighbouring cells or GSM cells

OLC starts: to reduce the TFs of BEsubscribers, and release some UEs forcibly

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-7

USR7

Page 176: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Priorities Involved in Load Control

Priorities Involved in Load ControlThe priorities involved in load control are user priority, Radio Access Bearer (RAB) integrate priority,and user integrate priority.

User PriorityThere are three levels of user priority (1, 2, and 3), which are denoted as gold (high priority), silver (middlepriority) and copper (low priority) users. The relation between user priority and Allocation RetentionPriority (ARP) can be set through SET USERPRIORITY command on the RNC; the typical relation isshown in the following table.

ARP 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

UserPriority

1 1 1 1 1 2 2 2 2 2 3 3 3 3 3

User Priority 1 = GoldUser Priority 2 = SilverUser Priority 3 = BronzeNote:

• ARP 15 is always the lowest priority and is not configurable. It corresponds to user priority 3(copper).

• If ARP is not received in messages from the Iu interface, the user priority is regarded as copper.The levels of user priority are mainly used to provide different QoS for different users, for example, settingdifferent Guaranteed Bit Rate (GBR) values according to the priority level of the users for a BE service.The GBR of BE services are configurable. According to the traffic class, priority level of users, and carriertype (DCH or HSPA), the different values of GBR are configured through the SET USERGBR command.Changes in the mapping between ARP and user priority have an influence on the following features:

• High Speed Downlink Packet Access (HSDPA)• High Speed Uplink Packet Access (HSUPA)• Adaptive Multi Rate (AMR)• AMR-WB• Iub overbooking

4-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 177: SYS202m2 Usr7 Ver1 Rev2

Priorities Involved in Load Control Version 1 Rev 2

Priorities Involved in Load ControlUser Priority

R NC

MS C S G S N

IuC S IuP S

R AB As s ignment R eques t

• T raffic C lass – C onversational

S treaming

Interactive

B ackground

• Allocation and R etention P riority (AR P ) 0 to 15

• T raffic Handling P riority (T HP ) 1 to 14

SET USERGBR

Gold Silver Copper

SET USERGBR

GBR of BE:

Traffic Class

ARP

DCH or HSPA

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-9

USR7

Page 178: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 RAB Integrate Priority

RAB Integrate PriorityRAB Integrate Priority is mainly used in load control algorithms.The values of RAB Integrate Priority are set according to the PriorityReference within SETUSERPRIORITY parameter as follows:

• If PriorityReference is set to Traffic Class, the integrate priority abides by the following rules:– Traffic classes: conversational -> streaming -> interactive -> background =>– Services of the same class: priority based on Allocation/Retention Priority (ARP) values,

that is, ARP1 -> ARP2 -> ARP3 -> ... -> ARP14 =>– Only for the interactive service of the same ARP value: priority based on Traffic Handling

Priority (THP), that is, THP1 -> THP2 -> THP3 -> ... -> THP14 =>– Services of the same ARP, traffic class and THP (only for interactive services): HSPA or DCH

service preferred depending on the value of the Indicator of CarrierTypePriorInd parameter.• If PriorityReference is set to ARP, the integrate priority abides by the following rules:

– ARP: ARP1 -> ARP2 -> ARP3 -> ... -> ARP14 =>– Services of the same ARP: priority based on traffic classes, that is, conversational -> streaming

-> interactive -> background =>– Only for the interactive service of the same ARP value: priority based on THP, that is, THP1 ->

THP2 -> THP3 -> ... -> THP14 =>– Services of the same ARP, traffic class and THP (only for interactive services): HSPA or DCH

service preferred depending on the value of the CarrierTypePriorInd parameter.

4-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 179: SYS202m2 Usr7 Ver1 Rev2

RAB Integrate Priority Version 1 Rev 2

RAB Integrate Priority

R NC

MS C S G S N

IuC S IuP S

R AB As s ignment R eques t

• T raffic C lass – C onversational

S treaming

Interactive

B ackground

• Allocation and R etention P riority (AR P ) 0 to 15

• T raffic Handling P riority (T HP ) 1 to 14

SET USERPRIORITY:PriorityReference=TrafficClass or ARP, CarrierTypePriorInd=DCH or HSPA;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-11

USR7

Page 180: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Potential User Control (PUC)

Potential User Control (PUC)

PUC Loading LevelsIn the WCDMA system, the mobility management of the UE in idle or connected mode (CELL_FACH,CELL_PCH, and URA_PCH) is performed by cell selection and cell reselection. The PUC algorithmcontrols the cell selection of a potential UE and prevents an idle UE from camping on a heavy load cell.The RNC periodically monitors the downlink load of the cell and compares the measurement results withthe configured threshold Load level division threshold 1, that is, load level division upper threshold andLoad level division threshold 2, that is, load level division lower threshold. When cell load is higherthan the load level division upper threshold plus theload level division hysteresis , it is decided tobe heavy. When cell load is lower than the load level lower threshold plus the load level divisionhysteresis, it is decided to be light.The parameters are set using the ADD/MOD CELLPUC command.SPUCLIGHT — Load level division threshold 2Value range: 0~100. Physical unit: %. Content: One of the thresholds used to judging cell load level, itis used to decide whether the cell load level is "Light" or not. Recommended value: 45.SPUCHEAVY — Load level division threshold 1Value range: 0~100. Physical unit: %. Content: Another threshold used to judging cell load level, it isused to decide whether the cell load level is "Heavy" or not. Recommended value: 70.SPUCHYST — Load level division hysteresisValue range: 0~100. Physical unit: %. Content: The hysteresis used while judging cell load level, it isused to avoid the unnecessary ping-pong of a cell between two load levels due to small load change.Recommended value: 5.Other parameters affecting this feature are found in the commands:

• ADD CELLALGOSWITCH• MOD CELLALGOSWITCH• SET LDCPERIOD• SET LDM• ADD CELLSELRESEL• ADD INTRAFREQNCELL• ADD INTERFREQNCELL• ADD GSMNCELL

4-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 181: SYS202m2 Usr7 Ver1 Rev2

Potential User Control (PUC) Version 1 Rev 2

Potential User Control (PUC)PUC Loading

f2 f2

f1

Reached load level division lower threshold + hyst

Light

Reached load level division higher threshold + hyst

Heavy

Normal

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-13

USR7

Page 182: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Potential User Control (PUC)

Potential User Control (PUC)

PUC Reselection Parameter ManipulationA UE obtains "cell reselection information" from the "system information block messages" (SIB3/SIB11)broadcast in the cell. The UE considers the Sintersearch value to decide when to start measuring newcells (new frequencies) and it uses Qoffset1 (corresponding to CPICH-RSCP Received Signal CodePower) and Qoffset2 (corresponding to CPICH Ec/No, Chip energy/total noise power density level) tomake the reselection decision.

• Sysintersearch is an optional parameter in SIB3. Its values range from -32 to 20 dB in incrementsof 2. All negative values are considered to be 0 by the UE.

• Qoffset1 and Qoffset2 are mandatory parameters in SIB11. They range from -50 to 50 dBIf the cell that the UE is camped on is tagged as heavy then the Sysintersearch parameter is manipulatedby the parameter OFFSINTERHEAVY. This will allow the UE to monitor inter frequency neighbours early.On the other hand if the camped cell is tagged as light then the Sysintersearch parameter is manipulatedby the parameter OFFSINTERLIGHT. This will allow the UE to monitor inter frequency neighbours later.Once the UE has started to monitor inter frequency neighbours then the Qoffset1 or Qoffset2can be manipulated by the parameters OFFQOFFSET1LIGHT or OFFQOFFSET2LIGHT andOFFQOFFSET1HEAVY or OFFQOFFSET2HEAVY. The effect of these are to encourage the UE toreselect to lightly loaded or normally loaded cells.OFFSINTERLIGHT — Sintersearch offset 1Value range: -10~10. Physical value range: -20~20; step 2. Physical unit: dB.Content: The offset of Sintersearch when camped cell load level is "Light".Recommended value: -2.OFFSINTERHEAVY — Sintersearch offset 2Value range: -10~10. Physical value range: -20~20; step 2. Physical unit: dB.Content: The offset of Sintersearch when camped cell load level is "Heavy"Recommended value: 2.The parameters are set using the ADD/MOD CELLPUC command.OFFQOFFSET1LIGHT — Qoffset1Value range: -20~20. Physical unit: dB.Content: The offset of Qoffset1 when neighbouring cell load is lighter than that of camped cell.Recommended value: -4.OFFQOFFSET2LIGHT — Qoffset2Value range: -20~20. Physical unit: dB.Content: The offset of Qoffset2 when neighbouring cell load is lighter than that of camped cell.Recommended value: -4.OFFQOFFSET1HEAVY — Qoffset1Value range: -20~20. Physical unit: dB.Content: The offset of Qoffset1 when neighbouring cell load is heavier than that of camped cell.Recommended value: -4.OFFQOFFSET2HEAVY — Qoffset2Value range: -20~20. Physical unit: dB.Content: The offset of Qoffset2 when neighbouring cell load is heavier than that of camped cell .Recommended value: -4.

4-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 183: SYS202m2 Usr7 Ver1 Rev2

Potential User Control (PUC) Version 1 Rev 2

Potential User Control (PUC)PUC Reselection Parameters

f2 f2

f1

Light

Heavy

Normal

Squal ≤ Sinterseach + OFFSINTERHEAVY

Rn = Qmeas,n -Qoffsets,n + OFFQOFFSET1LIGHT (or OFFQOFFSET2LIGHT)

Rs = Qmeas,s + Qhysts

Rn = Qmeas,n -Qoffsets,n

If Rn>Rs, for the duration of the “Treselection” timer reselect to that neighbour

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-15

USR7

Page 184: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Intelligent Access Control Algorithm

Intelligent Access Control AlgorithmThe access of a service to the network consists of setup of an RRC connection and an RAB. TheIntelligent Access Control (IAC) algorithm is used to improve the access success ratio. The IACprocedure includes rate negotiation, Call Admission Control (CAC), preemption, queuing, and DirectedRetry Decision (DRD).

IAC OverviewThe procedure for the UE access includes the RRC connection setup and RAB setup.As shown in the flowchart opposite, the procedure for the UE access includes the procedures for RRCconnection setup and RAB setup. The success in the RRC connection setup is one of the prerequisitesfor the RAB setup.During the RRC connection processing, if resource admission fails, DRD and redirection apply.During the RAB processing, the RNC performs the following steps:

• Performs RAB DRD to select a suitable cell to access, for service steering or load balancing.• Performs rate negotiation according to the service requested by the UE.• Performs cell resource admission decision. If the admission is passed, UE access is granted.

Otherwise, the RNC performs the next step.• Selects a suitable cell, according to the RAB DRD algorithm, from the cells where no admission

attempt has been made, and then goes to 2. If all DRD admission attempts to the cells fail, go tothe next step.

• Makes a preemption attempt. If the preemption is successful, UE access is granted. If thepreemption fails or is not supported, the RNC performs the next step.

• Makes a queuing attempt. If the queuing is successful, UE access is granted. If the queuing failsor is not supported, the RNC performs the next step.

• Rejects UE access.

Note: After the admission attempt of an HSPA service request fails in all candidate cells, the service falls back to the DCH. Then, the service reattempts to access the network.

4-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 185: SYS202m2 Usr7 Ver1 Rev2

Intelligent Access Control Algorithm Version 1 Rev 2

Intelligent Access Control Algorithm

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-17

USR7

dqfr38
Callout
In LTE it is centralized instead of be individual with 3G
Page 186: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Call Admission Control Overview

Call Admission Control OverviewAs the access decision procedure of IAC, Call Admission Control (CAC) is used to determine whetherthe system resources are sufficient to accept a new user’s access request. If the system resources aresufficient, the new user’s access request is accepted; otherwise, the user is rejected.

OverviewThe CAC algorithm consists of CAC based on power resource, CAC based on code resource, CACbased on credit resource, CAC based on Iub resource, and CAC based on HSPA user number.A CAC procedure contains RRC signaling admission control and RAB admission control.The admission decision is based on:

• Cell available code resource• Cell available power resource• NodeB resource state, that is, NodeB credits (They are used to measure the channel demodulation

capability of NodeBs.)• Available Iub transport layer resource, that is, Iub transmission bandwidth• Number of HSDPA users (only for HSDPA services)• Number of HSUPA users (only for HSUPA services)

A call can be admitted only when all of these resources are available.

Database ParametersExcept the mandatory code and Iub resource admission control, the admission control based on anyother resource can be disabled through the ADD CELLALGOSWITCH command.NBMCacAlgoSwitch — Value range : CRD_ADCTRL, HSDPA_UU_ADCTRL, HSDPA_GBP_MEAS,HSDPA_PBR_MEAS, HSUPA_UU_ADCTRL, MBMS_UU_ADCTRL,DOFFC ,HSUPA_PBR_MEAS andHSUPA_EDCH_RSEPS_MEAS.Content: The above values of the algorithms represent the following information:CRD_ADCTRL: Control NodeB Credit admission control algorithm Only whenIUB_CONG_CAC_SWITCH which is set by the SET CACALGOSWITCH command and this switch areon, the NodeB Credit admission control algorithm is valid.HSDPA_UU_ADCTRL: Control HSDPA UU Load admission control algorithmHSDPA_GBP_MEAS: Control HSDPA HS-DSCH Required Power measurementHSDPA_PBR_MEAS: Control HSDPA HS-DSCH Provided Bit Rate measurementHSUPA_UU_ADCTRL: Control HSUPA UU Load admission control algorithmMBMS_UU_ADCTRL: Control MBMS UU Load admission control algorithmDOFFC: Default DPCH offset configuration algorithmHSUPA_PBR_MEAS: Control HSUPA Provided Bit Rate measurementHSUPA_EDCH_RSEPS_MEAS: Control HSUPA Provided Received Scheduled EDCH Power Sharemeasurement.EMC_UU_ADCTRL: Control power admission for emergency userIfCRD_ADCTRL,HSDPA_UU_ADCTRL,HSDPA_GBP_MEAS,HSDPA_PBR_MEAS,HSUPA_UU_ADCTRL,MBMS_UU_ADCTRL, DOFFC, HSUPA_PBR_MEAS ,HSUPA_EDCH_RSEPS_MEAS andEMC_UU_ADCTRL are selected, the corresponding algorithms will be enabled; otherwise, disabled.Some CAC-related switches are available from the Cell CAC algorithm switch parameter.The power admission switch is available from the Uplink/Downlink CAC algorithm switch parameter.ADD CELLALGOSWITCH — See later

4-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 187: SYS202m2 Usr7 Ver1 Rev2

Call Admission Control Overview Version 1 Rev 2

Call Admission Control Overview

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-19

USR7

Page 188: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 QoS Classes

QoS ClassesW-CDMA defines 4 classes of services according to different QoS requirements. They are given below.

• Conversational: Service of this class is used for real-time service application, such as interactionbetween users and on-demand information transfer. The standard for the QoS of this classis dependent on the sensory satisfaction of people. Transmission delay might deteriorate theConversational service, and there is no critical restriction for the accuracy of the data packet. Inthe transmission of Conversational service data, the sequential relation between and after theinformation stream is emphasized, and the transmission delay and delay jitter is required to aproper range. Typical applications for the service are adaptive multi-Rate (AMR) speech andteleconference.

• Streaming: Service of this class is applied for real-time data stream and serves individual users,such as multimedia (audio and video) programs. It is unidirectional transmitted. The sequentialrelation between and after the information stream should be ensured, and there is no criticalrestrictions for the transmission delay during Streaming service data transmission. Typicalapplication for the service is video on demand.

• Interactive: Service of this class is oriented to data application and serves terminal users, e.g.,when a terminal online user waits for the reply within a certain period after sending a data requestto the remote server. The accuracy of the data packet should be guaranteed, and the loopback transmission delay should be restricted to a proper range during Interactive service datatransmission. Typical applications for the service are web page browse and database query.

• Background: Service of this class is oriented to data application and serves terminal users, e.g.,a computer sends and receives data files on PC background console. The accuracy of the datapacket should be guaranteed, and there is no requirement for the transmission delay. Typicalapplications for the service are short message service (SMS), background receiving E-Mail anddata file download.

4-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 189: SYS202m2 Usr7 Ver1 Rev2

QoS Classes Version 1 Rev 2

QoS Classes

E -mailData needs to be integral and correct

No requirementBackground

Web browser and location-based services

Data needs to be integral and correct

Fairly highInteractive

Multimedia serviceData needs to be transferred steadily and continuously

HighStreaming

Speech service and videophone

Errors are permitted to a certain degree

Very highConversational

ServiceRequirement for data

transmission

Requirement for realtime

performance

QoS Class

E -mailData needs to be integral and correct

No requirementBackground

Web browser and location-based services

Data needs to be integral and correct

Fairly highInteractive

Multimedia serviceData needs to be transferred steadily and continuously

HighStreaming

Speech service and videophone

Errors are permitted to a certain degree

Very highConversational

ServiceRequirement for data

transmission

Requirement for realtime

performance

QoS Class

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-21

USR7

Page 190: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Supported Service Rates

Supported Service RatesThe supported bit rates supported used in UMTS range somewhere between 0 to 7.2 mbit/s per user.However the actual bit rates are meaningless without defining the QoS offered together with the bitrates. The slides opposite illustrate typical data rates together with the types of service offered. Differentcombinations of the supported bit rates maybe put together in one call, for example you may have Sig3.4 kbit/s + CS service + PS Service.

Description of TerminologyIn the sub sections below the terminology used in the slides is explained.

Connection Oriented and Connectionless Oriented ServicesConnection-oriented — Requires a session connection (analogous to a phone call) be establishedbefore any data can be sent. This method is often called a "reliable" network service. It can guaranteethat data will arrive in the same order. Connection-oriented services set up virtual links between endsystems through a network.Connectionless — Does not require a session connection between sender and receiver. The sendersimply starts sending packets (called datagrams) to the destination. This service does not have thereliability of the connection-oriented method, but it is useful for periodic burst transfers. A connectionlessnetwork provides minimal services.

Traffic TypeThe bearer requirements are that the following is provided:

• Guaranteed/constant bit rate;• Non-guaranteed/dynamically variable bit rate;• Real time dynamically variable bit rate with a minimum guaranteed bit rate.• Real time and non real time services

Traffic CharacteristicsPoint-to-point services to be provided:

• Uni-directional — Service offered in one direction;• Bi-directional — Service offered in both directions;• Symmetric — The data rate is roughly the same uplink and downlink;• Asymmetric — The data rate is more heavily weighted in one direction.

Uni-directional Point-to-Multipoint:

• Multicast — Thie end user is specified before the connection is established. Multicast BroadcastMultimedia Service (MBMS) is an example of this:

• Broadcast — The messages are broadcast to to all UE”s and the end user is not known before.Cell Broadcast is an example of this.

4-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 191: SYS202m2 Usr7 Ver1 Rev2

Supported Service Rates Version 1 Rev 2

Supported Service Rates

57.6 kbit/sNon-transparent Data S ervice

64 kbit/s , 56 kbit/s , 32 kbit/s , and 28.8 kbit/sT ransparent Data S ervice

12.2 kbit/s , 23.85 kbit/sAMR S peech S ervice

Data R ateT R B C S S ervic e

57.6 kbit/sNon-transparent Data S ervice

64 kbit/s , 56 kbit/s , 32 kbit/s , and 28.8 kbit/sT ransparent Data S ervice

12.2 kbit/s , 23.85 kbit/sAMR S peech S ervice

Data R ateT R B C S S ervic e

3.4 kbit/s , 13.6 kbit/s , 27.2 kbit/sB idirectional S ignalling

Data R ateS R B S ervic e

3.4 kbit/s , 13.6 kbit/s , 27.2 kbit/sB idirectional S ignalling

Data R ateS R B S ervic e

14400 kbit/s , 10100 kbit/s , 7200 kbit/s , 5760 kbit/s , 3648 kbit/s , 2890 kbit/s , 2048 kbit/s , 1800 kbit/s , 1536 kbit/s , 1450 kbit/s , 1024 kbit/s , 768 kbit/s and 608 kbit/s

High-speed data service interactive, background and conversational unidirectional

384 kbit/s , 256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s , 16 kbit/s 8 kbit/s and 0 kbit/s

B idirectional symmetric or asymmetric background service

384 kbit/s , 256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s , 16 kbit/s , 8 kbit/s and 0 kbit/s

B idirectional symmetric or asymmetric interactive service

384 kbit/s , 256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s 16 kbit/s and 8 kbit/s

Unidirectional asymmetric s treaming service

256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s and 8 kbit/s

B idirectional symmetric or asymmetric s treaming service

64 kbit/s , 32 kbit/s , 16 kbit/s , 8 kbit/s38.4 kbit/s , 39.2 kbit/s , 40 kbit/s , 42.8 kbit/s

B idirectional symmetric V oIP speech service

Data R ateT R B P S S ervice

14400 kbit/s , 10100 kbit/s , 7200 kbit/s , 5760 kbit/s , 3648 kbit/s , 2890 kbit/s , 2048 kbit/s , 1800 kbit/s , 1536 kbit/s , 1450 kbit/s , 1024 kbit/s , 768 kbit/s and 608 kbit/s

High-speed data service interactive, background and conversational unidirectional

384 kbit/s , 256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s , 16 kbit/s 8 kbit/s and 0 kbit/s

B idirectional symmetric or asymmetric background service

384 kbit/s , 256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s , 16 kbit/s , 8 kbit/s and 0 kbit/s

B idirectional symmetric or asymmetric interactive service

384 kbit/s , 256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s 16 kbit/s and 8 kbit/s

Unidirectional asymmetric s treaming service

256 kbit/s , 144 kbit/s , 128 kbit/s , 64 kbit/s , 32 kbit/s and 8 kbit/s

B idirectional symmetric or asymmetric s treaming service

64 kbit/s , 32 kbit/s , 16 kbit/s , 8 kbit/s38.4 kbit/s , 39.2 kbit/s , 40 kbit/s , 42.8 kbit/s

B idirectional symmetric V oIP speech service

Data R ateT R B P S S ervice

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-23

USR7

Page 192: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 CAC Based on Code Resource

CAC Based on Code ResourceWhen a new service attempts to access the network, code resource admission is mandatory.Code resource admission is implemented as follows:

• For RRC connection setup requests, the code resource admission is successful if the currentremaining code resource is enough for the RRC connection.

• For handover services, the code resource admission is successful if the current remaining coderesource is enough for the service.

• For other R99 services, the RNC has to ensure that the remaining code does not exceed theconfigurable OM threshold (DlHoCeCodeResvSf) after admission of the new service.

For HSDPA services, the reserved codes are shared by all HSDPA services. Therefore, the coderesource admission is not needed.

Database ParametersThe parameters associated with this algorithm are found in the command ADD CELLCAC and aredescribed below.DlHoCeCodeResvSf — Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFFPhysical value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFFPhysical unit: NoneContent: Some cell resources can be reserved for handover UEs to guarantee handover success rateand improve access priority of handover services. This parameter defines the quantity of downlink codeand CE resources reserved for handover. SFOFF refers to that no resources is reserved. SF32 refersto that a code resource with SF = 32 and its corresponding credit resource are reserved. The backerposition the value is in {SF4,SF8,SF16,SF32,SF64,SF128,SF256,SFOFF}, the less code and creditresources reserved for handover UEs. The possibility of rejecting handover UE admissions increasesand performance of UEs cannot be guaranteed. The more frontal position the value is, the more thepossibility of rejecting new UEs is and some idle resources are wasted.Recommended value: SF32

4-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 193: SYS202m2 Usr7 Ver1 Rev2

CAC Based on Code Resource Version 1 Rev 2

CAC Based on Code Resource

SF = 32SF = 16

SF = 8

SF = 4

SF = 64

SF = ……

• RRC connection setup requests

• Handover services

• R99 services (dependancy on DlHoCeCodeResvSf)

ADD CELLCAC: DlHoCeCodeResvSf=SF32;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-25

USR7

Page 194: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Power Resource Admission Procedure

Power Resource Admission ProcedureThe following two algorithms are available for power resource admission decision:

• Algorithm 1: power resource admission decision based on power or interference• Algorithm 2: power resource admission decision based on the number of equivalent users• Algorithm 3: similar to algorithm 1 but the prediction of needed power of a new call will be set to

zero.

Basic PrinciplesThe basic principles for power resource admission decision are as follows:

• Admission control involves uplink and downlink. Their switches in the two directions areindependent of each other.

• If both the UL and DL CAC switches are enabled, a request for a non intra-frequency handover canbe accepted only when both uplink and downlink decisions are made.

• For an intra-frequency handover request, only downlink admission decision is needed.• Four basic load thresholds are used for admission decision. They are:

– Handover admission threshold– AMR conversational service admission threshold– Non AMR conversational service admission threshold– Other service admission thresholdsWith these thresholds, the RNC can define the proportion between speech service and otherservices while ensuring handover preference.

• For a rate reduction reconfiguration request, the RNC accepts it directly. For a rate increasereconfiguration request, the RNC performs the decision as shown in the flow chart opposite.

• For a rejected RRC connection request, the RNC performs DRD or redirection. For a rejectedservice request, the RNC performs preemption or queuing according to the actual situation.

The feature is enabled by the ADD CELLALGOSWITCH with the parameters shown below.NBMUlCacAlgoSelSwitch — Value range: ALGORITHM_OFF, ALGORITHM_FIRST,ALGORITHM_SECOND, and ALGORITHM_THIRDContent: The algorithms the above values represent are as follow:ALGORITHM_OFF: Disable uplink call admission control algorithm.ALGORITHM_FIRST: The load factor prediction algorithm will be used in uplink CAC.ALGORITHM_SECOND: The equivalent user number algorithm will be used in uplink CAC.ALGORITHM_THIRD: The loose call admission control algorithm will be used in uplink CAC.NBMDlCacAlgoSelSwitch — Value range: ALGORITHM_OFF, ALGORITHM_FIRST,ALGORITHM_SECOND, and ALGORITHM_THIRDContent: The algorithms the above values represent are as follow:ALGORITHM_OFF: Disable downlink call admission control algorithm.ALGORITHM_FIRST: The load factor prediction algorithm will be used in downlink CAC.ALGORITHM_SECOND: The equivalent user number algorithm will be used in downlink CAC.ALGORITHM_THIRD: The loose call admission control algorithm will be used in downlink CAC.

4-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 195: SYS202m2 Usr7 Ver1 Rev2

Power Resource Admission Procedure Version 1 Rev 2

Power Resource Admission Procedure

S erving C ell

256 kbit/s P S B ackground

384 kbit/s Interactive

64 kbit/s P S S treaming + 8 kbit/s P S C onv

12.2 kbit/s C S AMR

UE needs new res ource

QoS required

Trigger reas on

T es ts are c arried out to c heck whether the UE reques ting the new res ource will advers ely effec t the exis ting calls

• 1s t Algorithm – bas ed on P ower

• 2nd Algorithm – bas ed on E quivalent number of us ers

Note: To enable HSDPA/HSUPA power admission control use ADD CELLALGOSWITCH

• 3rd Algorithm – S imilar to alg 1 but new c all power s et to zero

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-27

USR7

Page 196: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Measurement Based Call Admission Control Algorithm

Measurement Based Call Admission Control AlgorithmIn WCDMA systems, admission of a new call will increase the loading in both uplink and downlink. In theuplink, the increase in the loading is indicated by the increase in the total interference level (i.e., ReceivedTotal Wideband Power RTWP). In the downlink, the increase in the loading is indicated by the increaseof transmitted power. The increase of loading in both uplink and downlink may cause the system to dropcalls.To guarantee the existing user’s transmission quality while maintaining coverage and optimal radioresource utilization, admission control is used to manage the allocation of radio resources using theDCH to the new call arrivals. The admission control is carried out for the following types of call requests:

• New call request• Soft handover request• Hard handover request• Existing call reconfiguration request• SRB request on DCH• HSDPA Request on associated UL HS-DPCCH

The admission control algorithm covers the power based admission control for dedicated transportchannels. For dedicated transport channels, the admission control process is divided into uplinkadmission control and downlink admission control, which are carried out separately in the uplink firstthen downlink. Different priority can be given to different services by setting up a higher threshold forthat service (UlConvThd vs. UlOtherThd) and Handover.Note that the call admission control algorithm described in this section covers only the power aspect ofthe overall call admission process. It does not cover code management, ATM backhaul link capacity,CPU usage, common channel FACH/RACH admission control. This power based CAC algorithm alsointeracts with other algorithms such as DCCC, DRD, PUC, LCC, Inter-carrier Load Balancing algorithms,and the Radio Resource Management (RRM). The final acceptance of the call is performed by the RRMbased on the result collected from other algorithms to ensure all the UTRAN resources are used properlyand efficiently.

4-28 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 197: SYS202m2 Usr7 Ver1 Rev2

Measurement Based Call Admission Control Algorithm Version 1 Rev 2

Measurement Based Call Admission Control Algorithm

Request Arrive

Emergency Request?

SRB Request or LU Detach

SRB Request or LU Detach

Overload Indicator

Other SRB Request HO request, Reconfiguration Request etc.

Other SRB Request HO request, Reconfiguration Request etc.

SHO Request?

Uplink Call Admission Control

Request Admitted Request Rejected

No

NoNo

No

A CB

Yes

Yes Yes

Yes

End

Admitted?

Get the service characteristic for the request and the current uplink load

Get the service characteristic for the request and the current uplink load

Downlink Call Admission Control

Request Admitted

Request Rejected

No

A CB

Yes

Get the service characteristic for the request and the current downlink load

Admitted?No

Yes

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-29

USR7

Page 198: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink Admission Control

Uplink Admission ControlFor new call requests, inter frequency hard handovers and call reconfigurations, the uplink admissioncontrol checks are performed as per the flowchart opposite. For SHO request and intra frequency hardhandover request the uplink admission algorithm is called but the request will be admitted immediatelywithout checking the load factor with the threshold.The procedure is described below.

1. Obtain data rate and Eb/No for the requested service.2. Obtain the current RTWP and background noise to calculate the current load factor.3. Obtain the UL common channel load factor.4. Calculate the predicted load factor per trigger of the CAC.5. Compare the calculated load factor with the defined threshold.6. If the defined threshold is exceeded, reject the new call.7. If the defined threshold is not exceeded, carry out Downlink CAC.

4-30 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 199: SYS202m2 Usr7 Ver1 Rev2

Uplink Admission Control Version 1 Rev 2

Uplink Admission Control

admissionrequest

get current RTWP andbackground noise

get uplink common channels'preset load factor, ηcomm

get data rate and Eb/N0requirement of request service

calculate therequest service's

load factor, L

according to thecharacteristic, get the

corresponding thresholdcalculate currentload factor, ηUL

calculate thepredicted load

factor, η'UL

exceed thethreshold?

rejected accepted

end

no

yes

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-31

USR7

Page 200: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink CAC Thresholds

Uplink CAC ThresholdsOnce the predicted load factor is calculated, this can then be compared to the relevant threshold. Thethresholds for the uplink are described below.ULCONVAMRTHD — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of conversational AMR service threshold to the 100% uplink load. It is sharedby algorithm 1 and algorithm 2. The UL load factor thresholds include this parameter, [UL thresholdof Conv non_AMR service],[UL handover access threshold] and [UL threshold of other services]. Thefour parameters can be used to limit the proportion between conversational service, handover user andother services in a specific cell, and to guarantee the access priority of conversational AMR service.Thisparameter is to guarantee the access priority of conversational AMR service. Recommended value: 75.ULCONVNONAMRTHD — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of conversational non_AMR service threshold to the 100% uplink load. It isshared by algorithm 1 and algorithm 2.UlOtherThd — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of other service threshold to the 100% uplink load. This parameter is sharedby algorithm 1 and algorithm 2.Recommended value: 60.UlHoThd — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of handover access service threshold to the 100% uplink load it is shared byalgorithm 1 and algorithm 2.This parameter only affects inter-frequency handover, because no CAC is used for intra-frequencyhandover.Recommended value: 80.

4-32 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 201: SYS202m2 Usr7 Ver1 Rev2

Uplink CAC Thresholds Version 1 Rev 2

Uplink CAC Thresholds

thresholdUL >'η

Conversational AMR use ULCONVAMRTHD

Non Conversational use UlOtherThd

Handover use UlHoThd

ADD CELLCAC

Conversational Non AMR use ULCONVNONAMRTHD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-33

USR7

Page 202: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Admission Control

Downlink Admission ControlFor new call requests, inter frequency hard handovers and call reconfigurations, the downlink admissioncontrol checks are performed as per the flowchart opposite.

1. Obtain data rate and Eb/No for the requested service.2. Calculate the downlink transmitter power increment (ΔP) for the request.3. Obtain the (Ec/No)i of all current services ,i .4. Obtain the current downlink total transmitted power for the serving cell — this is the NBAP “Tx

carrier power” or "Tx carrier power not used by HS-SCCH or HS-DSCH" measurement, filteredwith the moving average filter

5. Calculate the predicted transmitter power percentage6. Compare the calculated transmitter power percentage with the defined threshold.7. If the defined threshold is exceeded, reject the new call.8. If the defined threshold is not exceeded, admit the call.

4-34 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 203: SYS202m2 Usr7 Ver1 Rev2

Downlink Admission Control Version 1 Rev 2

Downlink Admission Control

admission request

get data rate and Eb/N0requirement of request service

Calculate the powerincreament for the request,

ΔP

get all the CIRs of the currentservice, (Ec/N0)i

get the downlink totaltransmit power of the cell,

P(N)

get downlink commonchannels' preset

percentage, λPcomm

calculate the predicted powerpercentage, η'DL

according to thecharacteristic, get the

corresponding threshold

exceed thethreshold?

rejected accepted

end

no

yes

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-35

USR7

Page 204: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink CAC Thresholds

Downlink CAC ThresholdsOnce the predicted load factor is calculated, this can then be compared to the relevant threshold. Thethresholds for the downlink are described below.DLCONVAMRTHD — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of conversational AMR service threshold to the 100% uplink load. It is sharedby algorithm 1 and algorithm 2. The DL load factor thresholds include this parameter, [DL thresholdof Conv non_AMR service],[DL handover access threshold] and [DL threshold of other services]. Thefour parameters can be used to limit the proportion between conversational service, handover user andother services in a specific cell, and to guarantee the access priority of conversational AMR service.Thisparameter is to guarantee the access priority of conversational AMR service. Recommended value: 80.DLCONVNONAMRTHD — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of conversational non_AMR service threshold to the 100% downlink load. It isshared by algorithm 1 and algorithm 2. Recommended value: 80.DlOtherThd — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of other service threshold to the 100% downlink load. This parameter is sharedby algorithm 1 and algorithm 2.Recommended value: 60.DlHoThd — Value range: 0~100.Physical value range: 0~1; step: 0.01.Content: The percentage of handover access service threshold to the 100% downlink load it is sharedby algorithm 1 and algorithm 2.This parameter only affects inter-frequency handover, because no CAC is used for intra-frequencyhandover.Recommended value: 85.

4-36 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 205: SYS202m2 Usr7 Ver1 Rev2

Downlink CAC Thresholds Version 1 Rev 2

Downlink CAC Thresholds

thresholdDL >'η

Conversational AMR use DLCONVAMRTHD

Non Conversational use DlOtherThd

Handover use DlHoThd

ADD CELLCAC

Conversational Non AMR use DLCONVNONAMRTHD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-37

USR7

Page 206: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Equivalent Number of Users (ENU) Algorithm

Equivalent Number of Users (ENU) AlgorithmThe 12.2 kbit/s AMR traffic is used to calculate the ENU of all other services. The 12.2 kbit/s AMR traffic’sENU is assumed to be 1. The ENU calculation of all other services is related to the following factors:

• Cell type, such as urban or suburban• Traffic domain, CS or PS• Coding type, turbo code or 1/2 1/3 convolutional code• Traffic Qos, or to say, BLER

The following is the typical ENU of some services (with activity factor 100%):

Equivalent Number of UsersService Uplink

for DCHDownlink for

DCH HSDPA HSUPA

3.4K Sig 0.44 0.42 0.28 1.76

13.6K Sig 1.11 1.11 0.74 1.89

3.4+12.2 1.44 1.42 — —

3.4+8(PS) 1.35 1.04 0.78 2.26

3.4+16(PS) 1.62 1.25 1.11 2.37

3.4+32(PS) 2.15 2.19 1.70 2.60

3.4+64(PS) 3.45 3.25 2.79 3.14

3.4+128(PS) 5.78 5.93 4.92 4.67

3.4+144(PS) 6.41 6.61 5.46 4.87

3.4+256(PS) 10.18 10.49 9.36 6.61

3.4+384(PS) 14.27 15.52 14.17 9.36

The procedure for ENU resource decision is as follows:

1. The RNC obtains the total ENU of all exist users

2. The RNC get the ENU of the new incoming user

3. The RNC uses the formula

to forecast the ENU load.Where ENUmax is the configured maximum ENU.

4. By comparing the forecasted ENU load with the corresponding threshold (the same threshold aspower resource), the RNC decides whether to accept the access request or not.

4-38 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 207: SYS202m2 Usr7 Ver1 Rev2

Equivalent Number of Users (ENU) Algorithm Version 1 Rev 2

Equivalent Number of Users (ENU) Algorithm

Database ParametersThe ADD CELLCAC command is used to set the following parameters related to Alg 2.The parameter DLTOTALEQUSERNUM is found in the ADD CELLCAC command.GUI range: 1–200Default value: 80Description: When algorithm 2 is used, this parameter defines the total equivalent user numbercorresponding to the 100% downlink load.The parameter ULTOTALEQUSERNUM is found in the ADD CELLCAC command.GUI range: 1–200Default value: 80Description: When algorithm 2 is used, this parameter defines the total equivalent user numbercorresponding to the 100% uplink load.

Serving Cell

256 kbit/s PS Background

384 kbit/s Interactive

64 kbit/s PS Streaming + 8 kbit/s PS Conv

12.2 kbit/s CS AMR

UE needs new resource

QoS required

Trigger reason

thresholdingCorrespondENU

ENUENU newtotal ≥+

max

Do not admit new call

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-39

USR7

Page 208: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Node B Credit Resource Check

Node B Credit Resource CheckWhen a new service accesses the network, NodeB credit resource admission is optional.Node B credit resource check is implemented as specified in TS25.433. Briefly, RNC keeps and updatesthe information of Node B credit sent by Node B through NBAP Audit Response message and ResourceStatus Indication message and each time when RNC performs the check, it uses the consumption lawwhich is also included in the two NBAP messages (refer to TS25.433 9.2.1.20A) to determine if currentNode B credit is sufficient to accommodate the new request. RNC also updates the current Node B creditbased on the calls admitted before the new Node B credit information is received, and if the data RNCmaintains is not consistent with the new information sent by Node B, RNC will replace its data with thenew data sent by Node B.According to the common and dedicated channels capacity consumption laws, and the addition, removal,and reconfiguration of the common and dedicated channels, the Controlling RNC (CRNC) debits theamount of the credit resource consumed from or credits the amount to the Capacity credit of the localcell (and local cell group, if any) based on the spreading factor.If the UL Capacity Credit and DL Capacity Credit are separate, the maintenance on the local cell (andlocal cell group, if any) is performed in UL and DL respectively. If the UL Capacity Credit and DL CapacityCredit are not separate, the maintenance only on the Global Capacity Credit is performed for the localcell (and local cell group, if any).Channel Element (CE) is normalized Credit (Based on 12.2kbps AMR service). The consumption ofCEs and the relationship between CE and credit is shown in the table below for DCH.

NodeB CreditCE stands for NodeB credit on the RNC side and for Channel Element on the NodeB side. It is used tomeasure the channel demodulation capability of the NodeBs.The resource of one equivalent 12.2 kbit/s AMR voice service, including 3.4 kbit/s signaling on the DCCH,consumed in baseband is defined as one CE. If there is only 3.4 kbit/s signaling on the DCCH but no voicechannel, one CE is consumed. Channel elements provide either uplink or downlink capacity for services.There are two kinds of CE. One is uplink CE supporting uplink services, and the other is downlink CEsupporting downlink services. Therefore, one 12.2 kbit/s AMR voice service consumes one uplink CEand one downlink CE.The principles of NodeB credit admission control are similar to those of power resource admission control,that is, to check in the local cell, local cell group (if any), and NodeB whether the remaining credit cansupport the requesting services.For detailed information about local cell, local cell group, and capacity consumption law, refers to the3GPP TS 25.433.

Traffic Class Direction SpreadingFactor

Numberof CEs

ConsumedCorresponding

Credits Consumed

DL 256 1 13.4kbps SRB

UL 256 1 2

DL 128 1 113.6kbps SRB

UL 64 1 2

DL 128 1 112.2kbps

UL 64 1 2

DL 32 2 264kbps VP

UL 16 3 6

DL 64 1 132kbps PS

UL 32 1.5 3

DL 32 2 264kbps PS

UL 16 3 6

4-40 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 209: SYS202m2 Usr7 Ver1 Rev2

Node B Credit Resource Check Version 1 Rev 2

Node B Credit Resource Check

Traffic Class Direction SpreadingFactor

Numberof CEs

ConsumedCorresponding

Credits Consumed

DL 16 4 4128kbps PS

UL 8 5 10

DL 8 8 8384 kbps PS

UL 4 10 20

Consumption of credits on the HSUPA (E-DPDCH)

Traffic Class Direction SpreadingFactor

Numberof CEs

Consumed

CorrespondingCredits

Consumed

16 kbps UL 64 1 2

32 kbps UL 32 1.5 3

64 kbps UL 16 3 6

128 kbps UL 8 5 10

384 kbps UL 4 10 20

1.45 Mbps UL 2*2 32 64

2.048 Mbps UL 2*2 32 64

2.89 Mbps UL 2*2 + 2*4 48 96

5.76 Mbps UL 2*2 + 2*4 48 96

Note:

• The reason for “UL Credit Consumption = 2 * UL CE Consumption” for the same data rates andservices” is that 1.5 CEs is consumed by UL PS 32kbps but only the INTEGER value can besupported in RESOURCE STATUS INDICATION over Iub. So in Motorola implementation, ULCredit is provided through multiplying UL CE by 2.

• For example, in “a standard low capacity license of DL48/UL48”, these are Channel Elements, sothe corresponding Credits is DL48/UL96.

• The amount of credits consumed by the E-DPCCH equals one.• Certain credits are reserved for HSDPA RAB; so credit admission for HSDPA is not needed.

When a service accesses the network, the credit resource admission is successful if the credit resourcesare allocated to the service successfully.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-41

USR7

Page 210: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Procedure for NodeB Credit Resource Decision

Procedure for NodeB Credit Resource DecisionWhen a new service tries to access the network, the credit resource admission is implemented as follows:

• For an RRC connection setup request, the credit resource admission is successful if the currentremaining credit resources of the local cell, local cell group (if any), and NodeB are sufficient forthe RRC connection.

• For a handover service, the credit resource admission is successful if the current remaining creditresources of the local cell, local cell group (if any), and NodeB are sufficient for the service.

• For other services, the RNC has to ensure that the remaining credit of the local cell,local cell group (if any), and NodeB does not exceed the configurable OM thresholds(UlHoCeResvSf/DlHoCeCodeResvSf) after admission of the new services.

Notes:

• The CE capabilities at the levels of local cell, local cell group, and NodeB are reported to the RNCthrough the NBAP_AUDIT_RSP message over the Iub interface.– The CE capability of local cell level indicates the maximum capability in terms of hardware that

can be used in the local cell.– The CE capability of local cell group level indicates the capability obtained after both license

and hardware are taken into consideration.– The CE capability of NodeB level indicates the number of CEs allowed to use as specified in

the license.• If the UL Capacity Credit and DL Capacity Credit are different, the credit resource admission is

implemented in the UL and DL, respectively.• If the UL Capacity Credit and DL Capacity Credit are the same, the credit resource admission is

implemented based on the total Capacity Credit.

Database ParametersThe database parameters are found in the command ADD CELLCAC and are described below.UlHoCeResvSf — Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFFPhysical value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFFPhysical unit: NoneContent: Uplink Credit Reserved by Spread Factor for HandOver. SFOFF means that none of themare reserved for handover. If the UL spare resource cant satisfy the reserved resource after the accessof a new service, the service will be rejected. If the value is too high, the credit resource reserved forhandover UEs will be less, leading to the increased possibility of rejecting handover UE admissions, andperformance of handover UEs cannot be guaranteed. If the value is too low, the possibility of rejectingnew UEs may increase and some idle resources are wasted.Recommended value: SF16DlHoCeCodeResvSf — Previously described.

4-42 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 211: SYS202m2 Usr7 Ver1 Rev2

Procedure for NodeB Credit Resource Decision Version 1 Rev 2

Procedure for NodeB Credit Resource Decision

R NCR NCIub

NodeB

• R esource S tatus Indication Mess age

C E C apability of NodeB hardware and UT R AN License taken into account

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-43

USR7

Page 212: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Iub Resource Admission

Iub Resource AdmissionThis section describes the admission control algorithm and takes the physical link as an example. Theadmission control policy for the transmission resource group is the same as that for the physical link.The requirements for the general algorithm for bandwidth admission control vary with whether it is a newuser, a handover user, or a rate upsizing user that is requiring admission.

New UserFor a new user, the following requirements apply:

• Total bandwidth allocated to the users on the path + required bandwidth for the new user < totalbandwidth configured for the path – bandwidth reserved for handover.

• Total bandwidth allocated to the users on the physical link + required bandwidth for the new user <total bandwidth of the physical link – bandwidth reserved for handover.

Handover UserFor a handover user, the following requirements apply:

• Total bandwidth allocated to the users on the path + required bandwidth for the handover user <total bandwidth configured for the path.

• Total bandwidth allocated to the users on the physical link + required bandwidth for the handoveruser < total bandwidth of the physical link.

Based on the preceding requirement, the user priorities are as follows:

• Handover user > new user > rate upsizing user

Rate Upsizing UserFor a rate upsizing user, the following requirements apply:

• Total bandwidth allocated to the users on the path + required bandwidth for the rate upsizing user< total bandwidth configured for the path – congestion threshold.

• Total bandwidth allocated to the users on the physical link + required bandwidth for the rate upsizinguser < total bandwidth of the physical link – congestion threshold.

Database ParametersThe database parameters used in the above algorithms are found in Port(ADD PORTCTRLER),Transmission resource group(ADD RSCGRP), IP Path(ADD IPPATH), AAL2 Path(ADD AAL2PATH),LGCPORT(ADD LGCPORT), VP(ADD VP) commands.TXBW — Forward bandwidth of the IP pathValue range: 1~ depends on commandContent: Forward bandwidth of the path.Recommended value (default value): NoneRXBW — Backward bandwidth of the IP pathValue range: 1~depends on commandContent: Backward bandwidth of the IP path.Recommended value (default value): NoneFWDHORSVBW — Forward handover reserved bandwidth.Value range: 0~depends on commandContent: Reserved forward bandwidth for handover user.Recommended value (default value): NoneBWDHORSVBW — Backward handover reserved bandwidthValue range: 0~ depends on commandContent: Reserved backward bandwidth for handover user.Recommended value (default value): None

4-44 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 213: SYS202m2 Usr7 Ver1 Rev2

Iub Resource Admission Version 1 Rev 2

Iub Resource AdmissionFWDCONGBW — Forward congestion thresholdValue range: 0~ depends on commandContent: If the available forward bandwidth is less than or equal to this value, the forward congestionalarm is emitted.Recommended value (default value): NoneBWDCONGBW — Backward congestion thresholdValue range: 0~ depends on commandContent: If the available backward bandwidth is less than or equal to this value, the backward congestionalarm is emitted.Recommended value (default value): NoneFWDCONGCLRBW — Forward congestion clear thresholdValue range: 0~depends on commandContent: If the available forward bandwidth is greater than this value, the forward congestion alarm iscleared.Recommended value (default value): noneBWDCONGCLRBW — Backward congestion clear thresholdValue range: 0~depends on commandContent: If the available backward bandwidth is greater than this value, the backward congestion alarmis cleared.Recommended value (default value): None

R NCR NC

Iub (ex)

NodeB

AAL2 RT

AAL2 HSPA RT

• New User

• Handover User

• Rate Upsizing User

Total bandwidth allocated to the users on the path + required bandwidth for the new user < total bandwidth configured for the path + bandwidth reserved for handover.

Total bandwidth allocated to the users on the physical link + required bandwidth for the new user < total bandwidth configured for the physical link + bandwidth reserved for handover.

Total bandwidth allocated to the users on the path + required bandwidth for the handover user < total bandwidth configured for the path

Total bandwidth allocated to the users on the physical link + required bandwidth for the handover user < total bandwidth configured for the physical link

Total bandwidth allocated to the users on the path + required bandwidth for the rate upsizing user < total bandwidth configured for the path + bandwidth reserved for handover.

Total bandwidth allocated to the users on the physical link + required bandwidth for the rate upsizing user < total bandwidth configured for the physical link

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-45

USR7

Page 214: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Iub Resource Admission Procedure

Iub Resource Admission ProcedurePrimary and secondary paths are used in admission control. According to the mapping between traffictypes and transmission resources, the RNC first selects the primary path for admission. If the admissionon the primary path fails, then the admission on the secondary path is performed.For example, assume that secondary paths are available for new users, handover users, and rateupsizing users. The following procedures describe the admission of these users on the Iub interfacerespectively.The admission procedure for a new user is as follows:

• The new user tries to be admitted to available bandwidth 1 of the primary path, as shown in thediagram.

• If the admission on the primary path is successful, the user is carried on the primary path.• If the admission on the primary path fails, the user tries to be admitted to available bandwidth 2 of

the secondary path, as shown in 2 on the diagram.• If the admission on the secondary path is successful, the user is carried on the secondary path. If

not, the bandwidth admission request of the user is rejected.Admission control for handover user and rate upsizing user are similar.

4-46 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 215: SYS202m2 Usr7 Ver1 Rev2

Iub Resource Admission Procedure Version 1 Rev 2

Iub Resource Admission Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-47

USR7

Page 216: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA Cell Admission Control

HSDPA Cell Admission ControlHSDPA admission control includes the following:

• Power resource admission control;• Iub transport layer resource admission;• User number admission decision.

Services can access the network only after all admission decisions are passed.

Power resource admission control on HSDPA ChannelsIn addition to the procedures described previously in this chapter for power based admission control,the admission of HSDPA services considers the load of total transmit power on the HSDPA channel,in addition to considering the load of total transmit power in a cell. A check is then made against theconfigured thresholds depending on the type of service requested.The thresholds for HSDPA part of admission control are found in the command ADD CELLCAC and aredescribed below.HsdpaStrmPBRThd — Value range: 0~100.Physical value range: 0~100%; step: 0.01.Physical unit: %.Content: The average throughput admission threshold of the HSDPA streaming traffic.Recommended value: 70.HsdpaBePBRThd — Value range: 0~100.Physical value range: 0~100%; step: 0.01.Physical unit: %.Content: The average throughput admission threshold of the HSDPA best effort traffic.Recommended value: 30.DlCellTotalThd — Value range: 0~100.Physical value range: 0~100%; step: 0.01.Physical unit: %.Content: The total downlink power threshold of the cell.Recommended value: 90.

User Number Admission DecisionThe maximum amount of HSDPA users is configured on a per cell and per NodeB basis. When a newHSDPA user wants access to the cell or NodeB these parameter thresholds are checked before access isallowed. The parameter to set the per cell value is found in ADD CELLCAC command and is describedbelow.Similar thresholds exist for HSUPA and are included here.MaxHSDSCHUserNum — Value range: 0~100.Physical unit: None.Content: Max number of users supported by HSDPA channel.Recommended value: 64.MaxHsupaUserNum — Value range: 0~100.Physical unit: None.Content: Max number of users supported by HSUPA channel.Recommended value: 20.The command to set the maximum amount of HSDPA users on a per NodeB basis is found in thecommand ADD NODEBALGOPARA and is described below.NodeBHsdpaMaxUserNum — Value range: 0~3840.Content: NodeB Max Hsdpa User Number.Recommended value: 3840.NodeBHsupaMaxUserNum — Value range: 0~3840.Content: NodeB Max Hsupa User Number.Recommended value: 3840.

4-48 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 217: SYS202m2 Usr7 Ver1 Rev2

HSDPA Cell Admission Control Version 1 Rev 2

HSDPA Cell Admission Control

Do not allow HSDPA channel to be used

No

Yes

HSDPA Channel required

Can CAC allow call?

Iub transport layer enough ?

Exceeded max users per cell/NodeB ?

No

Yes

Yes

No

Allow HSDPA channel to be used

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-49

USR7

Page 218: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 RRC Directed Retry Decision (DRD) and Redirection

RRC Directed Retry Decision (DRD) and Redirection

DRD ProcedureThe RRC Directed Retry Decision (DRD) algorithm includes two components:

• RRC Retry Decision algorithm• Redirection algorithm

The table below lists RRC DRD and Redirection, RAB Retry decision is similar to RRC DRD and iscovered in the handover chapter.

Procedure Description

RRC DRD During the RRC connection setup, if the UE fails to access thecell, the RNC chooses a suitable intra- or inter-frequency celland directs the UE to try this cell.

Redirection In the case of RRC DRD failure, the RNC includes aninter-frequency or inter-RAT redirection indication in the RRCCONNECTION REJECT message. This message directs theUE to initiate an inter-frequency or inter-RAT RRC connectionsetup after cell selection or resection.

The procedure is as follows:

• RRC setup request sub procedureThe UE sends an RRC CONNECTION REQUEST message to the RNC, requesting the RNC toset up a signaling RB (SRB) on DCH.

• RNC decision sub procedureAfter the RNC receives the request, the CAC algorithm decides whether an RRC connection canbe set up between the UE and the current cell.If yes, the RNC sends an RRC CONNECTION SETUP message to the UE.If no, the RNC searches for a proper cell from the candidate cell list of the UE.– If such a cell exists, the RNC indicates it to the UE through an RRC CONNECTION SETUP

message.– If such a cell does not exist, the RNC chooses another proper frequency or radio access system

such as GSM, and notifies the UE of it through the REDIRECTION IE in an RRC CONNECTIONREJECT message. The UE initiates an access request again at the specified frequency or inthe specified system.

4-50 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 219: SYS202m2 Usr7 Ver1 Rev2

RRC Directed Retry Decision (DRD) and Redirection Version 1 Rev 2

RRC Directed Retry Decision (DRD) and Redirection

UE RNCRRC Connection Request (Containing RACH Measurement Report)

Resource request succeeds?

Resource request succeeds?

Decide a redirectionRRC Connection Reject (Containing new cell info)

RRC Connection Setup

RRC Connection Setup Complete

Yes

Yes

No

No

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-51

USR7

Page 220: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 RRC DRD Algorithm

RRC DRD AlgorithmIf the DRD_SWITCH is set to OFF , then RRC DRD is not used, and RRC redirection is performed. Else,the RNC performs the following steps:

1. The RNC will select inter-frequency. These neighboring cells must be suitable for blind handoversi.e. be located in the same site and footprint of the serving cell.

2. The RNC generates a list of candidate DRD-supportive inter-frequency cells. The quality of thecandidate cell meets the requirements of inter-frequency DRD:– (CPICHECNO)RACH > (DRDECNO)ncell

Where:– (CPICHECNO)RACH is the cached CPICH Ec/N0 value included in the RACH measurement report.– (DRDECNO)ncell is the DRDEcN0Threshhold set for the inter-frequency neighboring cell.

3. The RNC selects a target cell from the candidate cells for UE access. If the candidate cell listcontains more than one cell, the UE tries a cell randomly:– If the admission is successful, the RNC initiates an RRC DRD procedure.– If the admission to a cell fails, the UE tries admission to another cell in the candidate cell list. If

all the admission attempts fail, the RNC makes an RRC redirection decision.4. If the candidate cell list does not contain any cell, then RRC DRD fails. The RNC performs the next

step, that is, RRC redirection.

Database CommandsThe command to set the RRC DRD Algorithm to enabled is found in the command SETCORRMALGOSWITCH and is described below.DrdSwitch — DRD_SWITCH: main DRD switch. When the switch is selected, DRD can be enabled forprocesses.The command to set the ECNO threshold for inter frequency neighbours is found in the command ADDINTERFREQNCELL, together with settings for blind handovers and is shown below.DRDEcN0Threshhold — This parameter is used as the DRD Ec/No threshold of whether to perform theblind handover.Value range: -24~0Physical unit: dBContent: This parameter is used as the DRD Ec/No threshold of whether to perform the blind handover.If the Ec/No measured value of the current cell is greater than this parameter of the inter-frequencyneighboring cell, this neighboring cell can be selected to be the candidate DRD cell.Recommended value: -18

4-52 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

dqfr38
Highlight
Page 221: SYS202m2 Usr7 Ver1 Rev2

RRC DRD Algorithm Version 1 Rev 2

RRC DRD AlgorithmRRC Retry Candidate List

f1 f1

f2

f3

Select strongest concentric cell inter-frequency neighbour

By CPICHEcNo_RACH > DRDEcN0Threshhold_NCELL (def -18dB)

Intra Frequency not allowed

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-53

USR7

Page 222: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Redirection Algorithm

Redirection AlgorithmWhen the RRC DRD fails, the associated RRC connection fails to be set up if RrcRedictSwitch is setto OFF. If RRC redirect switch is set to a value other than OFF, the RNC performs the following stepswhen the RRC DRD fails:

1. The RNC selects all inter-frequency but intra-band cells of the local cell.2. The RNC selects candidate cells. The candidate cells are the cells selected in step 1 but exclude

the cells that have carried out inter-frequency RRC DRD attempts.3. If more than one candidate cell is available, the RNC selects a cell randomly and redirects the UE

to the cell.4. If no such candidate cell is available:

– If RrcRedictSwitch is set to Only To Inter Frequency, the RRC connection setup fails.– If RrcRedictSwitch is set to Allowed To Inter RAT:

◊ If a neighboring GSM cell is configured, the RNC redirects the UE to that GSM cell.◊ If no neighboring GSM cell is configured, the RRC connection setup fails.

Database CommandsThe command to enable the RRC Redirection Algorithm to enabled is found in the command SET DRDand is described below.RrcRedictSwitch — Value range: OFF~0, Only_To_Inter_Frequency~1, Allowed_To_Inter_RAT~2.Physical unit: None.Content: This parameter specifies the RRC redirection strategy. -OFF: RRC redirection is not allowed. - Only_To_Inter_Frequency: Only RRC redirection tointer-frequency cells is allowed. -Allowed_To_Inter_RAT: RRC redirection to inter-frequency cells and redirection to inter-RAT cells areboth allowed.Recommended value: Only_To_Inter_Frequency.

4-54 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 223: SYS202m2 Usr7 Ver1 Rev2

Redirection Algorithm Version 1 Rev 2

Redirection Algorithm

StartStart

Select all inter-frequency cells (N) not already tried in RRC DRD

RrcRedictSwitch=Allowed_To_Inter_RAT?N = 0?

Redirect UE to GSM

RRC Connection failsN = 1?Redirect UE to UMTS Ncell

Redirect UE to Random UMTS Ncell

Yes

Yes

No

No

No

Yes

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-55

USR7

Page 224: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 RAB Retry Decision Algorithm

RAB Retry Decision AlgorithmThrough the RAB DRD procedure, the RNC selects a suitable cell for RAB processing during accesscontrol. RAB DRD is of two types: inter-frequency DRD and inter-RAT DRD. For inter-frequency DRD,the service steering and load balancing algorithms are available.

RAB DRD Basic ProcedureAfter receiving RANAP message RAB ASSIGNMENT REQUEST, the RNC initiates an RAB DRDprocedure to select a suitable cell for RAB processing during access control.The basic procedure for RAB DRD is as follows:

1. The RNC performs inter-frequency DRD. According to the purposes of directed retry, RAB directedretry is of the following types:– Service steering directed retry– Load balancing directed retry

2. If all admission attempts of inter-frequency DRD fail, the RNC performs an inter-RAT DRD.3. If all admission attempts of inter-RAT DRD fail, the RNC selects a suitable cell to perform preemption

and queuing.

Database CommandsWhether the DRD action is executable depends on the settings of the basic DRD algorithm switches.These are found in the command SET DRD or SET CORRMALGOSWITCH and are described below.DRD_SWITCH — This is the primary DRD algorithm switch. The secondary DRD switches are valid onlywhen this switch is on.COMB_SERV_DRD_SWITCH — DRD is applicable to combined services only when this switch is on.HSDPA_DRD_SWITCH — DRD is applicable to HSDPA services only when this switch is on.HSUPA_DRD_SWITCH — DRD is applicable to HSUPA services only when this switch is on.RAB_MODIFY_DRD_SWITCH — DRD is applicable to RAB modification only when this switch is on.RAB_DCCC_DRD_SWITCH — DRD is applicable to traffic-volume-based DCCC procedure or UE statetransition only when this switch is on.RAB_SETUP_DRD_SWITCH — DRD is applicable to RAB setup only when this switch is on.Note: A DRD action is executable only when all the related switches are on. The switches describedabove are basic switches for DRD algorithm, and there are corresponding switches for each type of DRD.For example, during the RAB setup process of an HSUPA service, DRD can be applied, if necessary,only when the DRD_SWITCH, RAB_SETUP_DRD_SWITCH, and the HSUPA_DRD_SWITCH are on.

4-56 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 225: SYS202m2 Usr7 Ver1 Rev2

RAB Retry Decision Algorithm Version 1 Rev 2

RAB Retry Decision Algorithm

(CCH) RRC Connection request

UE(RRC) RNC (RRC)

(CCH)RRC Connection Setup

(DCH) RRC Connection setup complete

CN (RANAP)RNC (RANAP)

RAB Assignment Request

Direct transfer messages for authentication and ciphering

NBAP Radio link setup procedures

RNC Selects performs inter-frequency DRD based on:

• Service steering

• Load balancing

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-57

USR7

Page 226: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-Frequency DRD for Service Steering

Inter-Frequency DRD for Service SteeringIf the UE requests a service in an area covered by multiple frequencies, the RNC selects the cell with thehighest service priority for UE access, based on the service type of RAB and the definitions of servicepriorities in the cells.The availability of the service steering DRD is defined by the ServiceDiffDrdSwitch switch parameter.

Cell Service Priorities IntroductionCell service priorities refer to the priorities of cells under the same coverage accepting specific servicetypes. These priorities help achieve traffic absorption in a hierarchical way.The priorities of specific service types in cells are configurable. If a cell does not support a service type,the priority of this service type is set to 0 in this cell. The group of service priorities in each cell is identifiedby the Service priority group Identity (SpgId) parameter.Service priority groups are configured on the LMT. In each group, priorities of R99 RT services, R99 NRTservices, HSPA services, and other services are defined.When selecting a target cell for RAB processing, the RNC selects a cell with a high priority, that is, a cellthat has a small value of service priority.The slide opposite shows an example of SPI:

• Cell B has a higher service priority of the R99 RT service than cell A. If the UE requests an RTservice in cell A, preferably the RNC selects cell B for the UE to access.

• If the requested service is a combination of multiple services, the RAB with the highest priority isused when a cell is selected for RAB processing. In addition, the target cell must support all theseservices.

Database CommandsThe command to set the Service Priority Group (SPG) is found in the command ADD SPG and isdescribed below.SpgId — Value range: 1~8.Physical unit: None.Content: This parameter identifies a group of cells that have specific capabilities for four service types:R99 real-time services, R99 non-real-time services, HSPA services, and other services.Recommended value: None.PriorityServiceForR99RT — Value range: 0~7.Physical unit: None.Content: This parameter specifies the capability of the cells with a specific [Service priority group Identity]for R99 real-time services. The value 0 means that these cells do not support R99 real-time services.The value 1 indicates the highest priority whereas the value 7 indicates the lowest. That is, R99 real-timeservices are preferably absorbed by this group of cells.Recommended value: 1.PriorityServiceForR99NRT — Value range: 0~7.Physical unit: None.Content: This parameter specifies the capability of the cells with a specific [Service priority group Identity]for R99 non-real-time services. The value 0 means that these cells do not support R99 non-real-timeservices. The value 1 indicates the highest priority whereas the value 7 indicates the lowest. That is,R99 non-real-time services are preferably absorbed by this group of cells.Recommended value: 1.PriorityServiceForHSPA — Value range: 0~7.Physical unit: None.Content: This parameter specifies the capability of the cells with a specific [Service priority group Identity]for HSPA services. The value 0 means that these cells do not support HSPA services. The value 1indicates the highest priority whereas the value 7 indicates the lowest. That is, HSPA services arepreferably absorbed by this group of cells.Recommended value: 1.PriorityServiceForExtRab — Value range: 0~7.Physical unit: None.Content: This parameter specifies the capability of the cells with a specific [Service priority group Identity]for extension services, such as CMB and MBMS. The value 0 means that these cells do not support

4-58 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 227: SYS202m2 Usr7 Ver1 Rev2

Inter-Frequency DRD for Service Steering Version 1 Rev 2

Inter-Frequency DRD for Service Steeringextension services. The value 1 indicates the highest priority whereas the value 7 indicates the lowest.That is, extension services are preferably absorbed by this group of cells.Recommended value: 1.Each cell is given a SPI by the commands ADD CELLSETUP or ADD QUICKCELLSETUP.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-59

USR7

dqfr38
Text Box
This feature is a new USR7 feature, it is very useful when deploying the second frequency for HSDPA. we should check it and compare with our actual configuration. when the R99 is congested this gonna help redirecting calls to HSDPA Cell.
dqfr38
Highlight
Page 228: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Service Steering DRD Procedure

Service Steering DRD ProcedureThe flowchart opposite and written description only take service steering DRD into considerations. Thatis, load balancing DRD is regarded as disabled.

DescriptionThe procedure for the service steering DRD is as follows:

• The RNC determines the candidate cells to which blind handovers can be performed and sorts thecandidate cells in descending order according to service priority. A candidate cell must meet thefollowing conditions:– The frequency of the candidate cell is within the band supported by the UE.– The quality of the candidate cell meets the requirements of inter-frequency DRD as for RRC

Connection Procedure.– The candidate cell supports the requested service.

• The RNC selects a target cell from the candidate cells in order of service priority for UE access. Ifthere is more than one cell with the same service priority:– When the cell, in which the UE requests the service, is one of the candidate cells with the same

service priority, preferably, the RNC selects this cell for admission decision.– Otherwise, the RNC randomly selects a cell as the target cell.

• The CAC algorithm makes an admission decision based on the status of the target cell:– If the admission attempt is successful, the RNC accepts the service request.– If the admission attempt fails, the RNC removes the cell from the candidate cells and then

checks whether all candidate cells are tried:◊ If there are any cells where no admission decision has been made, the algorithm goes back

to 2.◊ If admission decisions have been made in all the candidate cells, and

- The service request is an HSPA one, the HSPA request falls back to a DCH one.Then, the algorithm goes back to 1 to make an admission decision based on R99service priorities.

- The service request is a DCH one, the RNC initiates an inter-RAT DRD.

4-60 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 229: SYS202m2 Usr7 Ver1 Rev2

Service Steering DRD Procedure Version 1 Rev 2

Service Steering DRD Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-61

USR7

Page 230: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-Frequency DRD for Load Balancing

Inter-Frequency DRD for Load BalancingIf the UE requests a service setup or channel reconfiguration in an area covered by multiple frequencies,the RNC sets up the service on a carrier with a light load to achieve load balancing among the cells onthe different frequencies.

Load Balancing DRD OverviewLoad balancing considers two resources, power, and code.The availability of load balancing DRD is defined by the associated parameters as follows:

• The availability of power-based load balancing DRD for DCH service is defined by theLdbDRDSwitchDCH for DCH parameter.

• The availability of LdbDRDSwitchHSDPA for HSDPA service is defined by the Load balance DRDswitch for HSDPA parameter.

• The availability of code-based load balancing DRD is defined by the CodeBalancingDrdSwitchparameter.

In practice, it is recommended that only either a power-based load balancing DRD or a code-based loadbalancing DRD is activated. If both are activated, power-based load balancing DRD takes precedenceover code-based load balancing DRD.Code-based load balancing DRD is applicable to only R99 services because HSDPA services usereserved codes.

Database CommandsThe command which enables which type of load balancing DRD is used is set by the command ADDCELLDRD and is described below.LdbDRDSwitchDCH — Value range: ON, OFF.Physical unit: None.Content:This parameter specifies whether the load balancing DRD algorithm will be applied for servicescarried on DCH. - ON: The load balancing DRD algorithm will be applied. - OFF: The load balancingDRD algorithm will not be applied.Recommended value: OFF.LdbDRDSwitchHSDPA —Value range: ON, OFF.Physical unit: None.Content: This parameter specifies whether the load balancing DRD algorithm will be applied for servicescarried on HS-DSCH. - ON: The load balancing DRD algorithm will be applied. - OFF: The load balancingDRD algorithm will not be applied.Recommended value: OFF.CodeBalancingDrdSwitch — Value range: ON, OFF.Physical unit: None.Content: This parameter specifies whether the code balancing DRD algorithm will be applied. - ON: Thecode balancing DRD algorithm will be applied. - OFF: The code balancing DRD algorithm will not beapplied.Recommended value: OFF.

4-62 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 231: SYS202m2 Usr7 Ver1 Rev2

Inter-Frequency DRD for Load Balancing Version 1 Rev 2

Inter-Frequency DRD for Load Balancing

f1

f2

f3Load balancing based on Power: DCH and HSPA

LdbDRDSwitchDCH

LdbDRDSwitchHSDPA

Load balancing based on Code: DCH

CodeBalancingDrdSwitch

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-63

USR7

Page 232: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load Balancing DRD Based on Power Resource

Load Balancing DRD Based on Power ResourceIn this case DRD for service steering is disabled.The following two algorithms are available for power load balancing. If the power load balancing DRD isenabled, one of them can be used, and the algorithm used is defined by the LdbDRDchoice parameter.

Algorithm 1The load balancing DRD is performed according to the cell measurement values about the DLnon-HSDPA power and DL HS-DSCH required power.

• For DCH service, the RNC sets up the service on a carrier with a light load of non-HSDPA powerto achieve load balancing among the cells on the different frequencies.

• For HSDPA service, the RNC sets up the service on a carrier with a light load of HS-DSCH requiredpower to achieve load balancing among the cells on different frequencies.

Algorithm 2The load balancing DRD is performed according to the DCH Equivalent Number of Users (ENU) andHSDPA user number.

• For DCH service, the RNC sets up the service on a carrier with a light load of DCH ENU to achieveload balancing among the cells on different frequencies.

• For HSDPA service, the RNC sets up the service on a carrier with a light load of HSDPA user toachieve load balancing among the cells on different frequencies.

ExampleAn example is shown on the diagram opposite and explained below:

• Cell B has a lighter load of non-HSDPA power than Cell A. If the UE requests a DCH service in CellA, preferably, the RNC selects Cell B for the UE to access.

• Cell A has the lighter load of HS-DSCH required power than Cell B .If the UE requests an HSDPAservice in Cell B, preferably, the RNC selects Cell A for the UE to access.

Database CommandsThe command to set which algorithm is to be used for Load Balancing DRD Based on Power Resourceis found in SET DRD and is explained below.LdbDRDchoice — Value range: Power~1, UserNumber~0Physical unit: None.Content: This parameter specifies which choice the load balancing DRD algorithm will be applied. -Power: Power(Downlink none-HSDPA power is used for services carried on DCH, and downlink HSDPAguarantee power is used for services carried on HS-DSCH)will be applied to the load balancing DRDalgorithm. - UserNumber: User number(Downlink R99 equivalent user number is used for servicescarried on DCH, and downlink HSDPA user number is used for services carried on HS-DSCH)will beapplied to the the load balancing DRD algorithm.Recommended value: UserNumber.

4-64 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 233: SYS202m2 Usr7 Ver1 Rev2

Load Balancing DRD Based on Power Resource Version 1 Rev 2

Load Balancing DRD Based on Power Resource

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-65

USR7

Page 234: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load balancing DRD based on Power Resource Procedure

Load balancing DRD based on Power Resource ProcedureThe procedure for power-based load balancing DRD is as follows:

1. The RNC determines the candidate cells to which blind handovers can be performed. A candidatecell must meet the following conditions:– The frequency of the candidate cell is within the band supported by the UE.– The quality of the candidate cell meets the requirements of inter-frequency DRD.– The candidate cell supports the requested service.

2. If the current cell is not a candidate cell, the RNC selects a cell with the lightest load from thecandidate cells as the target cell. If the current cell is a candidate cell, go to 3.

3. The RNC determines whether the DL radio load of the current cell is lower than the power thresholdfor load balancing DRD (condition 1). Based on the bearer type (DCH or HSDPA) of the requestedservice, the RNC selects an appropriate condition.– For the algorithm 1, the condition 1 is as follows:

◊ For DCH bearer — (ThdAMR,cutcell — Pnon-H,cutcell) > Thdnon-H

◊ For HSDPA bearer — (Thdttotal,cutcell — PGBR,cutcell) > ThdH

– For the algorithm 2, the condition 1 is as follows:◊ For DCH bearer — (ThdAMR,cutcell — PD-ENU,cutcell) > Thdnon-H

◊ For HSDPA bearer — (ThdH-ue,cutcell — PH-ue,cutcell)/ThdH-ue,cutcell > ThdH

If condition 1 met go to 5, if not go to 4.4. The RNC selects a target cell from the inter-frequency neighboring cells for UE access. The RNC

determines whether any inter-frequency neighboring cell meets the following condition (condition2): Based on the bearer type (DCH or HSDPA) of the requested service, the RNC selects anappropriate condition as follow:– If algorithm 1 is used , the condition 2 is as follows:

◊ For a DCH service — (ThdAMR,nbcell — Pnon-H, nbcell) — (ThdAMR,cutcell — Pnon-H ,cutcell) > ThdD, loadoffset

(Thdtotal,cutcell — Pload, cutcell) — (Thdtotal,nbcell — Pload ,nbcell) <Thdtotal, loadoffset

◊ For an HSDPA service — (Thdtotal,nbcell — PGBR, nbcell) — (Thdtotal,cutcell — PGBR ,cutcell) > ThdH,

loadoffset

(Thdtotal,cutcell — Pload, cutcell) — (Thdtotal,nbcell — Pload ,nbcell) <Thdtotal, loadoffset

– If algorithm 2 is used ,the condition 2 is as follows:◊ For a DCH service — (ThdAMR,nbcell — PD-enu,nbcell) — (ThdAMR,cutcell — PD-enu,cutcell) > ThdD,loadoffset

◊ For an HSDPA service — (ThdH-ue,nbcell — PH-ue,nbcell)/ThdH-ue,nbcell — (ThdH-ue,cutcell —PH-ue,cutcell)/ThdH-ue,cutcell > ThdH,loadoffset

Then, the RNC selects the target cell as follows:If there is only one inter-frequency neighboring cell that meets the load balancing DRD conditions,the RNC selects this cell as the target cell. If there are multiple such cells:– For DCH service

◊ If the algorithm 1 is used, the RNC selects the cell with the lightest non-HSDPA load as thetarget cell.

◊ If the algorithm 2 is used, the RNC selects the cell with the lightest load of DCH ENU asthe target cell.

– For HSDPA service◊ If the algorithm 1 is used, the RNC selects the cell with the lightest load of HS-DSCH

required power as the target cell.◊ If the algorithm 2 is used, the RNC selects the cell with the lightest load of HSDPA user as

the target cell.If there is no such cell, the RNC selects the current cell as the target cell.

4-66 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 235: SYS202m2 Usr7 Ver1 Rev2

Load balancing DRD based on Power Resource Procedure Version 1 Rev 2

Load balancing DRD based on Power Resource Procedure5. The CAC algorithm makes an admission decision based on the status of the target cell.

– If the admission attempt is successful, the RNC admits the service request.– If the admission attempt fails, the RNC checks whether admission decisions have been made

in all candidate inter-frequency neighboring cells.◊ If there is any cell where no admission decision is made, the algorithm goes back to 2.◊ If admission decisions have been made in all the candidate cells:

◊ When the service request is HSPA , the HSPA request falls back to a DCH. Then,the algorithm goes back to 1 to make an admission decision based on R99 servicepriorities.

◊ When the service request is a DCH one, the RNC initiates an inter-RAT DRD.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-67

USR7

Page 236: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Database Commands for Load balancing DRD based on Power Resource

Database Commands for Load balancing DRD based on PowerResource

The following parameters relate to the algorithm above and are found in the SET DRD command.LdbDRDLoadRemainThdDCH — Value range: 0~100.Physical value range: 0%~100%.Physical unit: None.Content: This parameter specifies the downlink load threshold to trigger load balancing DRD for servicescarried on DCH. The load balancing DRD will probably be triggered only when the downlink cell remainingnon H power or remaining R99 equivalent user number is less than this threshold.Recommended value: 35.LdbDRDLoadRemainThdHSDPA — Value range: 0~100.Physical value range: 0%~100%.Physical unit: %.Content: This parameter specifies the downlink load threshold to trigger load balancing DRD for servicescarried on HS-DSCH. The load balancing DRD will probably be triggered only when the downlink cellremaining HSDPA guarantee power or remaining HSDPA user number is less than this threshold.Recommended value: 100.LdbDRDOffsetDCH — Value range: 0~100.Physical value range: 0%~100%.Physical unit: %.Content: This parameter specifies the threshold of remaining load offset between the current cell andthe target cell when load balancing DRD is applied for DCH users. Only when the remaining load offsetreaches this threshold can a neighboring cell be selected as a candidate DRD cell for DCH users.Recommended value: 10.LdbDRDOffsetHSDPA — Value range: 0~100.Physical value range: 0%~100%.Physical unit: %.Content: This parameter specifies the threshold of remaining load offset between the current cell and thetarget cell when load balancing DRD is applied for HSDPA users. Only when the remaining load offsetreaches this threshold can a neighboring cell be selected as a candidate DRD cell for HSDPA users.Recommended value: 10.LdbDRDTotalPwrProThd — Value range: 0~100.Physical value range: 0%~100%.Physical unit: %.Content: This parameter specifies the threshold of the downlink remaining total power difference betweenthe current cell and the target cell when load balancing DRD is applied and the load balancing DRDchoice is Power. Only when the downlink remaining total power difference is less than this threshold cana neighboring cell be selected as a candidate DRD cell.Recommended value: 30.Some parameters are borrowed form the CAC algorithm and are found in ADD CELLCAC and aredescribed below.DlConvAMRThd — Value range: 0~100Physical value range: 0~100%; step: 0.01Content: The percentage of the conversational AMR service threshold to the 100% downlink load. It isapplicable to algorithm 1 and algorithm 2.. Recommended value: 80DlCellTotalThd — Value range: 0~100Physical value range: 0~100%; step: 0.01Physical unit: noneContent: Admission threshold of the total cell downlink power. If the value is too high, too many userswill be admitted. However, the throughput of a single user is easy to be limited. If the value is too low,cell capacity will be wasted.Recommended value: 90MaxHSDSCHUserNum — Value range: 0~64Physical unit: noneContent: Maximum number of users supported by the HSDPA channel. The user in this parameter refersto the user with services on the HSDPA channel, regardless of the number of RABs carried on the HSDPAchannel. Maximum HSDPA user number cannot exceed the HSDPA capability of the NodeB product,In practice, the value can be set based on the cell type and the richness of the available HSDPA powerand code resources. If the value is too low, the cell HSDPA capacity may be reduced, leading to wastein HSDPA resources. If the value is too high, HSDPA services may be congested.Recommended value: 64

4-68 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 237: SYS202m2 Usr7 Ver1 Rev2

Database Commands for Load balancing DRD based on Power Resource Version 1 Rev 2

Database Commands for Load balancing DRD based on PowerResource

SET DRDLdbDRDLoadRemainThdDCH-Thdnon-H

SET DRDLdbDRDLoadRemainThdHSDPA-ThdH

SET DRDLdbDRDOffsetDCH-ThdD,loadoffset

SET DRDLdbDRDOffsetHSDPA-ThdH,loadoffset

-Total ENU of all existing DCH servicesPD-enu,nbcellPD-enu,cutcell

-Number of all existing HSDPA usersPH-ue,nbcellPH-ue,cutcell

ADD CELLCACMaxHSDSCHUserNumThdH-ue,nbcellThdH-ue,cutcell

ADD CELLCACDlConvAMRThdThdH-ue,nbcellThdAMR,cutcell

-Total power load. It is the sum of the non-HSDPA power and GBP.

Pload,nbcellPload,cutcell

-Non-HSDPA power loadPnon-H,nbcellPnon-H,cutcell

SET DRDLdbDRDTotalPwrProThd-Thdtotal,loadoffset

-HS-DSCH required power load (GBP)PGBP,nbcellPGBP,cutcell

ADD CELLCACDlCellTotalThdThdtotal,nbcellThdtotal,cutcell

Related commandDescriptionInter-frequency neighbour Cell

Current Cell

SET DRDLdbDRDLoadRemainThdDCH-Thdnon-H

SET DRDLdbDRDLoadRemainThdHSDPA-ThdH

SET DRDLdbDRDOffsetDCH-ThdD,loadoffset

SET DRDLdbDRDOffsetHSDPA-ThdH,loadoffset

-Total ENU of all existing DCH servicesPD-enu,nbcellPD-enu,cutcell

-Number of all existing HSDPA usersPH-ue,nbcellPH-ue,cutcell

ADD CELLCACMaxHSDSCHUserNumThdH-ue,nbcellThdH-ue,cutcell

ADD CELLCACDlConvAMRThdThdH-ue,nbcellThdAMR,cutcell

-Total power load. It is the sum of the non-HSDPA power and GBP.

Pload,nbcellPload,cutcell

-Non-HSDPA power loadPnon-H,nbcellPnon-H,cutcell

SET DRDLdbDRDTotalPwrProThd-Thdtotal,loadoffset

-HS-DSCH required power load (GBP)PGBP,nbcellPGBP,cutcell

ADD CELLCACDlCellTotalThdThdtotal,nbcellThdtotal,cutcell

Related commandDescriptionInter-frequency neighbour Cell

Current Cell

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-69

USR7

Page 238: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load Balancing DRD Based on Code Resource

Load Balancing DRD Based on Code ResourceThe procedure for load balancing DRD based on code resource is similar to that based on powerresource.The procedure is as follows:

• The RNC determines whether the minimum remaining spreading factor of the current cell is smallerthan CodeBalancingDrdMinSFThd.– If the minimum SF is smaller than CodeBalancingDrdMinSFThd for code balance DRD, the

RNC tries the admission of the service request to the current cell.– If the minimum SF is not smaller than CodeBalancingDrdMinSFThd, the RNC performs the

next step.• The RNC determines whether the code load of the current cell is lower than

CodeBalancingDrdCodeRateThd.– If the code load is lower than CodeBalancingDrdCodeRateThd, the service tries the

admission to the current cell.– If the code load is higher than or equal to CodeBalancingDrdCodeRateThd, the RNC selects

the cell with the lightest load or the current cell as the target cell. The RNC selects the cell asfollows:◊ If the minimum SF supported by the cell with the lightest code load is the same as the

minimum SF supported by the current cell, and the difference between the code resourceoccupancies of the cell and the current cell is larger than the value of Delta code occupiedrate, the RNC selects the cell with the lightest code load as the target cell. Otherwise, theRNC selects the current cell as the target cell.

◊ If the minimum SF supported by the cell with the lightest code load is smaller than theminimum SF supported by the current cell, the RNC selects the cell with the lightest codeload as the target cell.

Database CommandsThe database parameters related to Load Balancing DRD Based on Code Resource are found in thecommand SET DRD and are described below.CodeBalancingDrdMinSFThd — Value range: SF4~0, SF8~1, SF16~2, SF32~3, SF64~4, SF128~5,SF256~6.Physical unit: None.Content: This parameter specifies one of the triggering conditions of code balancing DRD. (The othercondition is the code occupancy.) This condition refers to that the minimum spreading factor of the bestcell is not smaller than the value of this parameter.Recommended value: SF8.CodeBalancingDrdCodeRateThd — Value range: 0~100.Physical value range: 0%~100%.Physical unit: %.Content: This parameter specifies one of the triggering conditions of code balancing DRD. (The othercondition is the minimum spreading factor.) This condition refers to that the code occupancy in the bestcell is not lower than the value of this parameter.Recommended value: 13.

4-70 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 239: SYS202m2 Usr7 Ver1 Rev2

Load Balancing DRD Based on Code Resource Version 1 Rev 2

Load Balancing DRD Based on Code Resource

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-71

USR7

Page 240: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Relation Between Service Steering DRD and Load Balancing DRD

Relation Between Service Steering DRD and Load BalancingDRD

When both service steering DRD and load balancing DRD are enabled, the general principles ofinter-frequency DRD are as follows:

• Service steering DRD takes precedence over load balancing DRD. That is, preferably take servicepriorities into consideration.

• To services of the same service priority, load balancing applies.For example, Universal Terrestrial Radio Access Network (UTRAN) f1, UTRAN f2, UTRAN f3, andUTRAN f4 shown in the diagram are inter-frequency cells with the same coverage. The service prioritiesof real-time R99 services in these cells are listed in the table in the diagram.According to the principles of inter-frequency DRD, the RAB DRD of a real-time R99 service will selectUTRAN f3 to make a CAC decision.

4-72 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 241: SYS202m2 Usr7 Ver1 Rev2

Relation Between Service Steering DRD and Load Balancing DRD Version 1 Rev 2

Relation Between Service Steering DRD and Load BalancingDRD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-73

USR7

Page 242: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-frequency DRD

Inter-frequency DRDIf the UE requests a service in an area covered by multiple frequencies, the RNC selects a suitable cellfor access based on the service priority in each candidate cell and the service type. In addition, duringcell selection, the RNC considers whether service steering DRD and load balancing DRD are enabled.

ProcedureThe procedure for inter-frequency DRD is as follows:

• If service steering DRD is enabled but load balancing DRD is disabled, as shown in A in the flowchart, the inter-frequency DRD procedure is the service steering DRD procedure.

• If load balancing DRD is enabled but service steering DRD is disabled, as shown in B in the flowchart, the inter-frequency DRD procedure is the service steering DRD procedure.

• If both load balancing DRD and service steering DRD are disabled:

1. The UE attempts to access the current cell when its service priority is not 0. If the service priorityof the current cell is 0, the UE attempts to access another candidate cell whose service priority isnot 0.

2. The CAC algorithm makes an admission decision based on the cell status.– If the admission attempt is successful, the RNC admits the service request.– If the admission attempt fails, the UE attempts to access another candidate cell.

3. If access to any of the candidate cells is rejected, and:– The service request is an HSPA one, the HSPA request falls back to a DCH one. Then, the

algorithm goes back to 1 to retry admission based on R99 service priorities.– The service request is a DCH one, the RNC initiates an inter-RAT DRD.

• If both load balancing DRD and service steering DRD are enabled:

1. The RNC determines the candidate cells to which blind handovers can be performed. A candidatecell must meet the following conditions:– The candidate cell supports the requested service.– The frequency of the candidate cell is within the band supported by the UE.– The quality of the candidate cell meets the requirements of inter-frequency DRD.

2. The RNC selects a target cell from the candidate cells for UE access based on the relation betweenservice steering DRD and load balancing DRD:– The RNC preferably selects the cell with the highest service priority.– If there are multiple cells with the highest service priority, load balancing applies to these cells.

In this case, the RNC follows the same DRD logic as described in Inter-Frequency DRD forLoad Balancing.

3. The CAC algorithm makes an admission decision based on the resource status of the cell.– If the admission attempt is successful, the RNC initiates an inter-frequency blind handover to

the cell.– If the admission attempt fails, the RNC removes the cell from the candidate cells and then

checks whether all candidate cells are tried.◊ If there is any candidate cell not tried, the algorithm goes back to 2 to try this cell.◊ If all candidate cells haven been tried, and:

◊ The service request is an HSPA one, the HSPA request falls back to a DCH one. Then,the algorithm goes back to 1 to retry admission based on R99 service priorities.

◊ The service request is a DCH one, the RNC initiates an inter-RAT DRD.

4-74 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

dqfr38
Highlight
Page 243: SYS202m2 Usr7 Ver1 Rev2

Inter-frequency DRD Version 1 Rev 2

Inter-frequency DRD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-75

USR7

Page 244: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-RAT DRD

Inter-RAT DRDWhen all admission attempts for inter-frequency DRD during RAB processing fail, the RNC determineswhether to initiate an inter-RAT DRD.

ProcedureThe inter-RAT DRD procedure is as follows:

1. If the current cell is configured with any neighboring GSM cell suitable for blind handover, and if theService Handover Indicator that is contained in the RAB assignment signaling assigned by the CNis “handover to GSM should be performed”, then the RNC performs step 2. Otherwise, the servicerequest undergoes preemption and queuing.

2. The RNC generates a list of candidate DRD-supportive inter-RAT cells that fulfill the followingrequirement:(CPICHECNO)RACH > (DRDECNO)ncell

Where:– (CPICHECNO)RACH is the cached CPICH Ec/N0 value included in the RACH measurement report.– (DRDECNO)ncell is the DRDEcN0Threshhold set for the inter-RAT neighboring cell.If the candidate cell list does not include any cell, the service request undergoes preemption andqueuing.

3. The service request then tries admission to a target GSM cell in order of blind handover priority.4. If all admission attempts fail or the number of inter-RAT directed retries exceeds 2, the service

request undergoes preemption and queuing.Note: The RAN10.0 does not support inter-RAT DRD for RABs of combined services, R99 PS servicesor HSPA services.

Database CommandsThe parameter is found in ADD GSMNCELL and is described below.DRDEcN0Threshhold — This parameter is used as the DRD Ec/No threshold of whether to perform theblind handover. Value range: -24~0Physical value range: -12~0, step: 0.5Physical unit: dB Content: This parameter is used as the DRD Ec/No threshold of whether to performthe blind handover. When choosing a DRD candidate cell, if the Ec/No value of the current cell is greaterthan the threshold of inter-RAT/inter-frequency neighboring cell, the DRD is permitted.Recommended value: -18

4-76 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 245: SYS202m2 Usr7 Ver1 Rev2

Inter-RAT DRD Version 1 Rev 2

Inter-RAT DRD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-77

USR7

Page 246: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Call Pre-emption

Call Pre-emptionPreemption guarantees the success in the access of a higher-priority user by forcibly releasing theresources of a lower-priority user.After cell resource admission fails, the RNC performs preemption if the following conditions are met:

• The RNC receives an RAB ASSIGNMENT REQUEST message indicating that preemption issupported.

• The preemption algorithm switch PreemptAlgoSwitch is set to ON.Preemption is applicable to the following cases:

• Setup or modification of a service.• Hard handover or SRNS relocation.• UE state transits from CELL_FACH to CELL_DCH.

ProcedureThe preemption procedure is as follows:

• The preemption algorithm determines which radio link sets can be preempted. The algorithmproceeds as follows:– Chooses SRNC users first. If no user under the SRNC is available, the algorithm chooses

users under the DRNC.– Sorts the pre-emptable users by user integrate priority, or sorts the pre-emptable RABs by RAB

integrate priority (Gold, Silver and Copper).– Determines candidate users or RABs.

Only the users or RABs with priorities lower than the RAB to be established are selected. Ifthe Integrate Priority Configured Reference parameter is set to Traffic Class and the switchPreemptRefArpSwitch is set to ON, only the ones with higher ARP and lower priority than theRAB to be established are selected. This applies to RABs of streaming or BE services.

– Selects as many users or RABs as necessary in order to match the resource needed by theRAB to be established. When the priorities of two users or RABs are the same, the algorithmchooses the user or RAB that can release the most resources.

• The RNC releases the resources occupied by the candidate users or RABs.• The requested service directly uses the released resources to access the network without admission

decision.

Database CommandsFor preemption, the RNC selects a suitable cell according to the settings of the DRD algorithms.The database command that controls whether preemption is enabled is SET QUEUEPREEMPT. Therelevant database parameter is described below.PREEMPTALGOSWITCH — Preempt algorithm switchValue range: OFF, ON.Content: Indicating whether to support the preemption function.Recommended value: ON.PreemptRefArpSwitch — Value range: ON, OFFPhysical unit: noneContent: Indicating whether ARP-based preemption between TCs is supported. This switch only hasimpact on the TC-based priorities. When the priority is based on the TC and the switch is enabled,for the following two situations, the preempting service should have a higher priority and ARP prioritythan the preempted service does: 1.The preempting service is the streaming service and the preemptedservice is the interactive or background service. 2. The preempting service is the interactive service andthe preempted service is the background service.Recommended value: ON

4-78 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 247: SYS202m2 Usr7 Ver1 Rev2

Call Pre-emption Version 1 Rev 2

Call Pre-emption

R NC

MS C S G S N

IuC S IuP S

R AB As s ignment R eques t

• P re-emption C apability IE = pre-emption allowedR AB As s ignment R es pons e

• S ucces s without admis s ion decis ion

P re-emption enabled at R NC

C all preempted with lower P riority than UE requesting service

C all takes preempted UE sresources directly

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-79

USR7

Page 248: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Call Queuing

Call QueuingAfter the admission of a service fails, the service request is put into a specific queue. Then admissionattempts for the service are made periodically during a defined period of time.After the cell resource decision fails, the RNC performs queuing if the RNC receives an RABASSIGNMENT REQUEST message indicating the queuing function is supported and QueueAlgoSwitchis set to ON.

ProcedureThe queuing algorithm is triggered by the heartbeat timer which equals 500 ms. Each time the timerexpires, the RNC chooses the service that meets the requirement to make an admission attempt. Thespecific process of the queuing algorithm is as follows:

• The queuing algorithm checks whether the queue is full, that is, whether the number of servicerequests in the queue exceeds the queue length which equals 5.

• The queuing algorithm proceeds as shown in the table below.

Checks whether there are requests whose integrate priorities are lower thanthat of the priority of the new request.• If yes, then the queuing algorithm

- Checks the weights of these requests. If not all weights are thesame, the algorithm rejects the request with the smallest weightvalue.

- Stamps the new request with the current time and then puts it intothe queue.

- Starts the heartbeat timer if it is not started.• If no, then the queuing algorithm rejects the new request directly.

Full

• Stamps this request with the current time.• Puts this request into the queue.• Starts the heartbeat timer if it is not started.

Not full

Then the queuing algorithm...If thequeue is...

Checks whether there are requests whose integrate priorities are lower thanthat of the priority of the new request.• If yes, then the queuing algorithm

- Checks the weights of these requests. If not all weights are thesame, the algorithm rejects the request with the smallest weightvalue.

- Stamps the new request with the current time and then puts it intothe queue.

- Starts the heartbeat timer if it is not started.• If no, then the queuing algorithm rejects the new request directly.

Full

• Stamps this request with the current time.• Puts this request into the queue.• Starts the heartbeat timer if it is not started.

Not full

Then the queuing algorithm...If thequeue is...

Weight (Pqueue = Telapsed)

After the heartbeat timer expires, the queuing algorithm proceeds as follows:

• Rejects the request if the actual waiting time of the request, Telapsed, is longer than the value ofthe MaxQueueTimeLen parameter for the service.

• Selects the request with the highest integrate priority for an attempt of resource allocation.• If more than one service has the same highest integrate priority, the RNC calculates the weights of

all requests in the queue and chooses the request with the greatest weight for an attempt of resourceallocation. The method of calculating the weight of a service request is described subsequently.

• If the attempt is successful, the heartbeat timer is restarted for the next processing upon expiry ofthis timer.

• If the attempt fails, the queuing algorithm proceeds as follows:– Puts the service request back into the queue with the time stamp unchanged for the next

attempt.– Chooses the request with the greatest weight from the rest and makes another attempt until a

request is accepted or all requests are rejected.The queuing weight is calculated with the following formula:Pqueue = Telapsed

Where:

• Pqueue is the weight for the queuing service request. The service with the highest value of Pqueueundergoes admission attempt.

• Telapsed is the time in milliseconds that the service request has spent in the queue. The value ofTelapsed is calculated by the current time stamp minus the recorded queuing time stamp of the servicerequest.

4-80 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 249: SYS202m2 Usr7 Ver1 Rev2

Call Queuing Version 1 Rev 2

Call QueuingDatabase CommandsThe database command that controls whether queuing is enabled and the setting off the maximumqueuing times is the SET QUEUEPREEMPT. The relevant database parameters are described below.QUEUEALGOSWITCH — Queue algorithm switchValue range: OFF, ON.Content: Indicating whether to support the queuing function.Recommended value: ON.QUEUELEN — Queue lengthValue range: 5~20.Content: Queue length.Recommended value: 10.PollTimerLen — Value range: 1~80Physical value range: 10~800 msPhysical unit: 10 msContent: Timer length of the queue poll. The queue is polled for every time specified in this parameter.During each poll, all the expired users are removed from the queue and this user fails in access. Amongall the unexpired users, resources are allocated in the order of high priority to low priority. If resourceallocation is successful, the user succeeds in access and traverse of this queue is stopped. Otherwise,the rest users are traversed until all the unexpired users go through this.Recommended value: 50MaxQueueTimeLen — Value range: 1~60Physical value range: 1~60sPhysical unit: sContent: Maximum queue time of users. When a user initiates a call, it joins the queue due to cellresource insufficiency. This parameter defines the maximum length of time required for queuing of auser. If cell resources are still insufficient after expiration, access fails.Recommended value: 5

R NC

MS C S G S N

IuC S IuP SR AB As s ignment R eques t

• Queuing Allowed IE

• AR P

C all F ails one of the Admis s ion C ontrol C hec ks

• C all goes into queue

• C hecks priority against other requests in the queue

• R eques t with larges t weight is at the front of the queue

R AB As s ignment R es pons e

• S ucces s or F ail

Queuing enabled at R NC

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-81

USR7

Page 250: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Intra-Frequency Load Balancing (LDB)

Intra-Frequency Load Balancing (LDB)

Algorithm OverviewWhen the loads of intra-frequency cells are not even, the distribution of cell load is balanced byautomatic adjusting the cell coverage (CPICH power) to improve the utilization of system resource i.e.cell breathing.The LDB algorithm is aimed at balancing the loads within cells with the same frequency. According tothe load level in one cell, the LDB module decides whether a load balance is needed. If the output isYES, the power of the pilot channel is changed. If the load level exceeds one load threshold, the pilotpower is decreased. As a result some UEs in the cell with the high load may leave the current cell andgo into the neighbour cell. Conversely, if the load level is below one load threshold, the pilot power isincreased. Some UEs in the neighbour high load cell may go into this cell.When the load of one cell is too heavy, it results in transmission loss and the quality of communicationsis decreased for the users at the edge of the cell. At the same time, neighbour cells could still have manyavailable resources. When this happens, cell breathing can be used to avoid this situation: the cell sizewill be reduced when the cell is over loaded and the cell size will be increased when the cell is lightlyloaded by adjusting the transmitted power of the pilot channel. The UE at the edge of the cell will beswitched to the neighbour cells when the cell is over loaded and the UE at the edge of neighbour cells willbe switched to the cell when it is lightly loaded. This results in a more efficient use of the radio resources.

NOTEIt should stressed that there is no coordination between cells for pilot power adjustment; the LDBalgorithm acts independently within individual cells, therefore coverage gaps can potentially becreated due to uncoordinated adjustments

4-82 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 251: SYS202m2 Usr7 Ver1 Rev2

Intra-Frequency Load Balancing (LDB) Version 1 Rev 2

Intra-Frequency Load Balancing (LDB)

PCPICH Power

ADD PCPICH: …………. PCPICHPOWER=300, MAXPCPICHPOWER=330, MINPCPICHPOWER=270;

30dBm27dBm 33dBm

Lightly loaded

Normally loaded

Heavily loaded

NodeB Power compared against threshold

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-83

USR7

Page 252: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 LDB Algorithm Implementation

LDB Algorithm ImplementationThe algorithm steps are:

1. Obtain the current DL Transmitted Carrier Power (periodic NBAP Transmitted Carrier Powermeasurement report from the Node B) for the cell and store it.

2. Compare the transmitted power with cell breathing thresholds. If the transmitted power is greaterthan the cell overloading threshold (CellOverrunThd), go to 3). If the transmitted power is lessthan the cell underloading threshold (CellUnderrunThd), go to 4.

3. If the transmitted power of pilot channel has already reached the minimum value(MinPCPICHPower), go to 6), otherwise reduce the transmitted power of downlink pilot channelby one step (PCPICHPowerPace) and go to 5).

4. If the transmitted power of pilot channel has already reached the maximum value(MaxPCPICHPower) then go to 6, otherwise increase the transmitted power of downlink pilotchannel by one step (PCPICHPowerPace) and go to 5).

5. Execute the NBAP Cell Reconfiguration procedure to set the new PCPICH power value in thecell at the Node B.

6. Wait for a given “waiting period” (Intra_carrier_LDB_period) and repeat above steps (1 to 6)Upon changing CPICH power, the Node B will re-compute all common channel powers (PSCH, SSCH,PCCPCH, SCCPCH, AICH, PICH) and dedicated channel Max Power Per Code and Min Power PerCode values. Following a pilot power change, the RNC also modify the information element containingCPICH power which is broadcast on BCH.The command that sets the parameters explained above are ADD CELLLDB.PCPICHPOWERPACE — Pilot power adjustment stepValue range: 0~100. Physical value range: 0~10; step: 0.1. Physical unit: dB. Content: Pilot poweradjustment step.Recommended value: 3.CELLOVERRUNTHD — Cell overload thresholdValue range: 0~100. Physical value range: 0~1; step: 0.01. Physical unit: None.Content: If the cell downlink load exceeds this threshold, the algorithm can decrease the pilot transmitpower of the cell so as to increase the whole system's capacity.Recommended value: 90% of [DL threshold of other services].CELLUNDERRUNTHD — Cell underload thresholdValue range: 0~100. Physical value range: 0~1; step: 0.01. Physical unit: None.Content: If the cell downlink load is lower than this threshold, the algorithm can increase the pilot transmitpower of the cell so as to share the load of other cells.Recommended value: [Cell overload threshold] - 10.Also SET LDCPERIOD.

4-84 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 253: SYS202m2 Usr7 Ver1 Rev2

LDB Algorithm Implementation Version 1 Rev 2

LDB Algorithm Implementation

Start

Obtain DL TPC

For Cell

DL TCP >

CellOverrunThd

CPICHPower =

MinPCPICHPowerDL TCP <

CellUnderrunThd

CPICHPower =

MaxPCPICHPower

Increase PCPCIHPower

by PCPICHPowerPace

dB

Decrease PCPCIHPower

by PCPICHPowerPace

dB

Wait

IntraCarrierLDBPeriod

Execute

NBAP CELL

Reconfiguration

Procedure

YES

YES

YES

YES

NO

NO

NO

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-85

USR7

Page 254: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load Reshuffling Algorithm

Load Reshuffling AlgorithmWhen the usage of cell resource exceeds the basic congestion triggering threshold, the cell enters thebasic congestion state. In this case, LDR is required to reduce the cell load and increase the accesssuccess ratio.The following lists the contents of this section:

• Basic Congestion Triggering• LDR Procedure• LDR Actions.

Triggering of Basic CongestionWhen the usage of cell resource exceeds the basic congestion trigger threshold, the cell enters the basiccongestion state. In this case, LDR is needed to reduce the cell load and increase the access successrate.The resources that can trigger basic congestion of the cell are:

• Power resources• Iub resources or Iub bandwidth• Code resource• NodeB credit resource.

Basic congestion is triggered when any of the resources reaches the basic congestion trigger threshold.When the load of all resources is lower than the basic congestion trigger threshold, the system comesback to normal.

Power Resource TriggeringDL_UU_LDR and UL_UU_LDR under the NBMLdcAlgoSwitch algorithm switch parameter control thefunctionality of the power congestion control algorithm.For an R99 cell:

• If the current UL/DL load of the R99 cell is higher than or equal to the basic congestion controlthreshold in UL/DL (UL/DL LDR Trigger threshold) for 1000ms, the cell works in the basic congestionstate, and the related load reshuffling actions apply.

• If the current UL/DL load of the R99 cell is lower than the UL/DL LDR Release threshold for 1000ms,the cell returns to the normal state.

For an HSPA cell:

• In the uplink, the object to be compared with the associated threshold (UL LDR Trigger threshold)for a decision is the uncontrollable load.

• In the downlink, the object to be compared with the associated threshold (DL LDR Trigger threshold)for decision is the sum of the non-HSDPA power (TCP of all codes not used for HS-PDSCH orHS-SCCH transmission) and the Power Requirement for GBR (GBP).

The parameter that enables power resource load reduction is found in the command ADDCELLALGOSWITCH and is described below.UL_UU_LDR — UL UU Load reshuffling algorithm. When the cell is heavily loaded in UL, thisalgorithm reduces the cell load in UL by using inter-frequency load handover, BE service rate reduction,uncontrollable real-time service QoS renegotiation, CS inter-RAT handover, and PS inter-RAT handover.DL_UU_LDR — DL UU load reshuffling algorithm. When the cell is heavily loaded in DL, thisalgorithm reduces the cell load in DL by using inter-frequency load handover, BE service rate reduction,uncontrollable real-time service QoS renegotiation, CS inter-RAT handover, and PS inter-RAT handover.The parameters that control the triggering of LDR for power resources are set by the ADD/MODCELLLDM command and are listed below.ULLDRTRIGTHD — UL LDR trigger thresholdValue range: 0~100 Physical value range: 0~1; step: 0.01.Content: If the UL load of the cell is not lower than this threshold, the UL load reshuffling function of thecell will be triggered.Recommended value: 55.ULLDRRELTHD — UL LDR release threshold

4-86 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 255: SYS202m2 Usr7 Ver1 Rev2

Load Reshuffling Algorithm Version 1 Rev 2

Load Reshuffling AlgorithmValue range: 0~100. Physical value range: 0~1; step: 0.01.Content: If the UL load of the cell is lower than this threshold, the UL load reshuffling function of the cellwill be stopped.Recommended value: 45.DLLDRTRIGTHD — DL LDR trigger thresholdValue range: 0~100. Physical value range: 0~1; step: 0.01.Content: If the DL load of the cell is not lower than this threshold, the DL load reshuffling function of thecell will be triggered.Recommended value: 70.DLLDRRELTHD — DL LDR release thresholdValue range: 0~100. Physical value range: 0~1; step: 0.01.Content: If the DL load of the cell is lower than this threshold, the DL load reshuffling function of the cellwill be stopped.Recommended value: 60.

ADD CELLALGOSWITCH: NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-87

USR7

Page 256: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Code Resource Triggering

Code Resource TriggeringCELL_CODE_LDR under the Cell LDC algorithm switch parameter command controls the functionalityof the code congestion control algorithm.If the SF corresponding to the current remaining code of the cell is larger than CellSfResThd, codecongestion is triggered and the related load reshuffling actions taken.

Database ParametersThe parameter that enables code resource load reduction is found in the command ADDCELLALGOSWITCH and is described below.CELL_CODE_LDR — Code reshuffling algorithm. When the cell CODE is heavily loaded, this algorithmreduces the cell CODE load by using BE service rate reduction and code tree reshuffling.The parameter to set the Cell SF reserve threshold is found in the ADD CELLLDR command and isdescribed below.CellSfResThd — Value range: SF8,SF16,SF32,SF64,SF128,SF256.Physical unit: None.Content: The code adjusting could be done only when the minimum available SF of a cell is larger thanthis threshold.Recommended value: SF8.

4-88 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 257: SYS202m2 Usr7 Ver1 Rev2

Code Resource Triggering Version 1 Rev 2

Code Resource Triggering

SF = 32SF = 16

SF = 8

SF = 4

SF = 64

SF = ……

ADD CELLLDR:CellSfResThd=SF8;

Minimum available code higher than SF=8 code resource LDR triggered

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-89

USR7

Page 258: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Iub Resources or Iub Bandwidth Triggering

Iub Resources or Iub Bandwidth TriggeringThe IUB_LDR of the NodeB LDC algorithm switch parameter in the ADD NODEBALGOPARA or MODNODEBALGOPARA command controls the functionality of the Iub congestion control algorithm.Iub congestion control in both the uplink and downlink is NodeB-oriented.. In the case of Iub congestion,LDR actions are applied to congestion resolution.

Congestion Detection MethodThe Forward congestion threshold and Backward congestion threshold parameters can be set forcongestion detection when a path, port, or resource group is configured. The default value for bothof the parameters is 0, which indicates that no congestion detection is performed. If the parametersare specified, TRM performs congestion detection based on the parameter values. For a path, port,or resource group, it is also possible to set the Forward congestion clear threshold and Backwardcongestion clear threshold parameters, both of which are used to determine whether the congestiondisappears.Congestion detection can be triggered in either of the following ways:

• Bandwidth adjustment because of resource allocation, modification or release.• Change in the configured bandwidth or the congestion threshold.• Physical link fault.

For example, if the forward parameters of a port for congestion detection are defined as follows, withCLEAR being greater than CON:

• Configured bandwidth: AVE• Forward congestion threshold: CON• Forward congestion clear threshold: CLEAR• Used bandwidth: USED

Then, the mechanism of congestion detection on the port is as follows:

• The congestion occurs on the path when CON + USED ≥ AVE.• The congestion disappears from the path when CLEAR + USED < AVE.

The congestion detection for a path or resource group is similar to that for a port.Generally, congestion thresholds only need to be set for a port or resource group. If different types ofAAL2 paths or IP paths require different congestion thresholds, the parameters for the paths are set asrequired.If a VP or LP is configured, congestion control is also applied to the VP or LP, and the congestion controlmechanism is the same as that of a resource group.

Database ParametersThe command to enable Iub congestion is ADD NODEBALGOPARA: and is described below.IUB_LDR – (Iub congestion control algorithm): When the NodeB Iub load is heavy, users are assembledin priority order among all the NodeBs and some users are selected for LDR action (such as BE servicerate reduction) in order to reduce the NodeB Iub load.The parameters that control the triggering of LDR for Iub resources are set by the ADD AAL2PATH/ADDIPPATH/ADD LGCPORT/ADD PORTCTRLER/ADD RSCGRP/ADD VP commands and are listed below.FWCONGESTCTHD — Forward congestion control thresholdValue range: 50~100Content: When the mean of an adjacent AAL2 node forward resource occupancies reaches or exceedsthis threshold, the congestive control shall be enabled.Default value 95BWCONGESTCTHD — Backward congestion control thresholdValue range: 50~100 Content: When the mean of an adjacent AAL2 node forward and backwardresource occupancies reaches or exceeds this threshold, the congestive control shall be enabled.Default value 95FWCONGESTRTHD — Forward congestion restore thresholdValue range: 40~100 Content: When the mean of an adjacent AAL2 node forward resource occupanciesare smaller than their threshold, the congestive control shall be stopped.Default value 80BWCONGESTRTHD — Backward congestion restore threshold

4-90 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 259: SYS202m2 Usr7 Ver1 Rev2

Iub Resources or Iub Bandwidth Triggering Version 1 Rev 2

Iub Resources or Iub Bandwidth TriggeringValue range: 40~100 Content: When the mean of an adjacent AAL2 node backward resourceoccupancies are smaller than their threshold, the congestive control shall be stopped.Default value 80

R NCR NCIub

NodeB

• Configured bandwidth: AVE

• Forward congestion threshold: CON

• Forward congestion clear threshold: CLEAR

• Used bandwidth: USED

The congestion occurs on the path when CON + USED >= AVE

The congestion disappears from the path when CLEAR + USED < AVE

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-91

USR7

Page 260: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 NodeB Credit Resource

NodeB Credit ResourceThe basic congestion for NodeB credit is of the following types:

• Type A: Basic congestion at local cell level.

If the cell UL/DL current remaining SF (mapped to credit resource) is higher than UL LDR CreditSF reserved threshold/DL LDR Credit SF reserved threshold (set through the ADD CELLLDRcommand), credit congestion at cell level is triggered and related load reshuffling actions are takenin the current cell.

• Type B: Basic congestion at local cell group level (if any)• Type C: Basic congestion at NodeB level

If the cell group or NodeB UL/DL current remaining SF (mapped to credit resource ) is higher thanUL LDR Credit SF reserved threshold/DL LDR Credit SF reserved threshold (set through theADD NODEBLDR command), credit congestion at cell group or NodeB level is triggered and relatedload reshuffling actions are taken. The range of LDR actions is the same as the first type, but therange of UEs to be sorted by priority is different. All the UEs in the normal-state cells that belongto the cell group or NodeB will be sorted based on the integrated priority.

Database ParametersThe table below shows for each type of NodeB Credit Congestion what parameters need to be enabled.

NODEB_CREDIT_LDRNODEB_CREDIT_LDR_SWITCHType C

LCG_CREDIT_LDRLCG_CREDIT_LDR_SWITCHType B

LC_CREDIT_LDR_SWITCHCELL_CREDIT_LDRType A

NodeB LDC AlgorithmSwitch

Load ControlAlgorithm Switch

Cell LDCAlgorithm Switch

Switches Need to Be EnabledAlgorithm

NODEB_CREDIT_LDRNODEB_CREDIT_LDR_SWITCHType C

LCG_CREDIT_LDRLCG_CREDIT_LDR_SWITCHType B

LC_CREDIT_LDR_SWITCHCELL_CREDIT_LDRType A

NodeB LDC AlgorithmSwitch

Load ControlAlgorithm Switch

Cell LDCAlgorithm Switch

Switches Need to Be EnabledAlgorithm

The command to enable Cell LDC Algorithm is set within the command ADD CELLALGOSWITCH andis described below.CELL_CREDIT_LDR:Credit reshuffling algorithm. When the cell credit is heavily loaded, this algorithmreduces the credit load of the cell by using BE service rate reduction, uncontrollable real-time serviceQoS renegotiation, CS inter-RAT handover, and PS inter-RAT handover.The command to enable the load control algorithm is set within the command SET LDCALGOPARA andis described below.LC_CREDIT_LDR_SWITCH: Local cell credit congestion control algorithm. This is an RNC-orientedalgorithm. When the local cell credit load is heavy, the load can be reshuffled through BE service ratereduction, renegotiation of uncontrollable real-time service QoS, and CS/PS inter-RAT handover.LCG_CREDIT_LDR_SWITCH: Local cell group credit congestion control algorithm. This is anRNC-oriented algorithm. When the local cell group credit load is heavy, the load can be reshuffledthrough BE service rate reduction, renegotiation of uncontrollable real-time service QoS, and CS/PSinter-RAT handover.NODEB_CREDIT_LDR_SWITCH: NodeB credit congestion control algorithm. This is an RNC-orientedalgorithm. When NodeB credit load is heavy, the load can be reshuffled through BE service rate reduction,renegotiation of uncontrollable real-time service QoS, and CS/PS inter-RAT handover.The parameters for type A NodeB congestion are found in the command ADD CELLLDR and aredescribed below.The command to set the

4-92 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 261: SYS202m2 Usr7 Ver1 Rev2

NodeB Credit Resource Version 1 Rev 2

NodeB Credit ResourceUlLdrCreditSfResThd — Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256Physical unit: noneContent: Reserved SF threshold in uplink credit LDR. The uplink credit LDR could be triggered only whenthe SF factor corresponding to the uplink reserved credit is higher than the uplink or downlink credit SFreserved threshold. The lower the parameter value is, the easier the credit enters the congestion status,the easier the LDR action is triggered, and the easier the user experience is affected. A lower coderesource LDR trigger threshold, however, causes a higher admission success rate because the resourceis reserved. The parameter should be set based on the operator’s requirement.Recommended value: SF8DlLdrCreditSfResThd — Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256Physical unit: noneContent: Reserved SF threshold in downlink credit LDR. The downlink credit LDR could be triggeredonly when the SF factor corresponding to the downlink reserved credit is higher than the uplink ordownlink credit SF reserved threshold. The lower the parameter value is, the easier the credit enters thecongestion status, the easier the LDR action is triggered, and the easier the user experience is affected.A lower code resource LDR trigger threshold, however, causes a higher admission success ratebecause the resource is reserved. The parameter should be set based on the operator’s requirement.Recommended value: SF8

R NCR NCIub

NodeB

Type A - Basic congestion at local cell level

UL LDR Credit SF reserved threshold

DL LDR Credit SF reserved threshold

Type B: Basic congestion at local cell group level (if any)

Type C: Basic congestion at NodeB level

UL LDR Credit SF reserved threshold

DL LDR Credit SF reserved threshold

ADD CELLLDR

ADD NODEBLDR

Integrated Priority Based

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-93

USR7

dqfr38
Callout
RNC Level
dqfr38
Callout
NB
dqfr38
Callout
When cells are shared between diff operators
Page 262: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Congestion Trigger Priority

Congestion Trigger PriorityIf the congestion of all resources is triggered in a cell, the congestion is resolved in order of resourcepriority for load reshuffling as configured through the SET LDCALGOPARA command.For example, if the parameters are set as follows:

• First priority for load reshuffling: IUBLDR• Second priority for load reshuffling: CREDITLDR• Third priority for load reshuffling: CODELDR• Fourth priority for load reshuffling: UULDR

The basic congestion is resolved in the following sequence:

• Iub resource• Credit resource• Code resource• Power resource

The information of cell status can be checked through the DSP CELLCHK command.

Database ParametersThe command to set the congestion priority is found in the command SET LDCALGOPARA and isdescribed below.LdrFirstPri — Value range: IUBLDR (Iub load reshuffling),CREDITLDR (Credit load reshuffling),CODELDR (Code load reshuffling),UULDR (Uu load reshuffling) Physical unit: noneContent: If congestion is triggered by multiple resources such as credit and code at the same time, thecongestion of resources specified in this parameter is processed with the first priority. IUBLDR refersto processing of LDR action trigged by Iub bandwidth. CREDITLDR refers to processing of LDR actiontrigged by credit. CODELDR refers to processing of LDR action trigged by code. UULDR refers toprocessing of LDR action trigged by Uu.Recommended value: IUBLDRLdrSecondPri — Recommended value: CREDITLDRLdrThirdPri — Recommended value: CODELDRLdrFourthPri — Recommended value: UULDR

4-94 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 263: SYS202m2 Usr7 Ver1 Rev2

Congestion Trigger Priority Version 1 Rev 2

Congestion Trigger Priority

R NCR NCIub

NodeB

SET LDCALGOPARA: LdrFirstPri=IUBLDR, LdrSecondPri=CREDITLDR, LdrThirdPri=CODELDR, LdrFourthPri=UULDR;

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-95

USR7

Page 264: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 LDR Procedure

LDR ProcedureThe RNC periodically takes actions if basic congestion is detected.The following procedures apply to HSPA cells and R99 cells. For R99 cells, only DCH UEs are selectedby LDR actions.When the cell is in basic congestion state, the RNC takes one of the following actions in each period(defined by the LDR period timer length parameter) until the congestion is resolved:

• Inter-frequency load handover• Code reshuffling• BE service rate reduction• AMR rate reduction• Inter-RAT load handover in the CS domain

– Inter-RAT Should Be Load Handover in the CS Domain– Inter-RAT Should Not Be Load Handover in the CS Domain

• Inter-RAT load handover in the PS domain– Inter-RAT Should Be Load Handover in the PS Domain– Inter-RAT Should Not Be Load Handover in the PS Domain

• Iu QoS renegotiation• MBMS power reduction

In RAN10.0, the sequence of the LDR actions can be changed through the ADD CELLLDR command,and the waiting timer for LDR period is defined by the LDR period timer length parameter through theSET LDCPERIOD command

LDR ParametersThe parameters that effect LDR with relation to the features that can be enabled and what order they areused can be found in the ADD/MOD CELLLDR command.DL/ULLDRFIRSTACTION — Value range: NOACT (NO ACTION), INTERFREQLDHO(INTER-FREQ LOAD HANDOVER), BERATERED (BE TRAFF RATE REDUCTION), QOSRENEGO(UNCONTROLLED REAL-TIME TRAFF QOS RE-NEGOTIATION), CSINTERRATLDHO (CS DOMAININTER-RAT LOAD HANDOVER), PSINTERRATLDHO (PS DOMAIN INTER-RAT LOAD HANDOVER),AMRRATERED (AMR TRAFF RATE REDUCTION), MBMSDECPOWER(MBMS DESCEND POWER),CODEADJ(CODE ADJUST).Content: None.Recommended value: CODEADJ (CODE ADJUST).DL/ULLDRSECONDACTION — DL/UL LDR second actionSame as above.Recommended value: .INTERFREQLDHO (INTER-FREQ LOAD HANDOVER).DL/ULLDRTHIRDACTION — DL/UL LDR third actionSame as above.Recommended value: BERATERED (BE TRAFF RATE REDUCTION)..DL/ULLDRFOURTHACTION — DL/UL LDR fourth actionSame as above.Recommended value: NOACT (NO ACTION).DL/ULLDRFIFTHACTION — DL/UL LDR Fifth actionSame as above.Recommended value: NOACT (NO ACTION).DL/ULLDRSIXTHACTION — DL/UL LDR Sixth actionSame as above.Recommended value: NOACT (NO ACTION).DL/ULLDRSEVENTHACTION — DL/UL LDR Seventh actionSame as above.Recommended value: NOACT (NO ACTION).DL/ULLDREIGHTHACTION — DL/UL LDR Eight actionSame as above.Recommended value: NOACT (NO ACTION).

4-96 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 265: SYS202m2 Usr7 Ver1 Rev2

LDR Procedure Version 1 Rev 2

LDR Procedure

R NCR NCIub

NodeB

• C ode R eshuffling

• Inter-F requency Load Handover (B lind)

• B E R ate R eduction

• AMR rate reduction

• Inter-S ystem Handover in C S Domain

• Inter-S ystem Handover in P S Domain

• Iu QoS Negotiation

• MB MS power reduction (not covered)

Da

tab

as

e C

on

fig

ura

ble

fo

r e

na

bli

ng

/dis

ab

lin

g a

nd

wh

at

ord

er

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-97

USR7

Page 266: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 LDR Actions for Different Resources

LDR Actions for Different ResourcesThe LDR actions taken are different depending on whether power or Iub resources trigger the LDRalgorithm. These differences are explained by the tables in the slides below and opposite.Note — If the downlink power admission uses the equivalent user number algorithm, basic congestionmay also be triggered by the equivalent number of users. In this situation, LDR actions do not involveAMR rate reduction.

☺☺DL

ULCode

☺☺☺☺☺DL

☺☺☺☺☺ULIub

☺☺☺☺☺☺DL

☺☺☺☺☺☺ULPower

Code Reshufffling

Iu QoSNegotiation

AMR Rate Reduction

Inter-System Handover in PS Domain

Inter-System Handover in CS Domain

BE Rate Reduction

Inter-frequency Load Handover

LDR ActionsUL/DL

Resource

☺☺DL

ULCode

☺☺☺☺☺DL

☺☺☺☺☺ULIub

☺☺*☺☺☺☺DL

☺☺☺☺☺☺ULPower

Code Reshufffling

Iu QoSNegotiation

AMR Rate Reduction

Inter-System Handover in PS Domain

Inter-System Handover in CS Domain

BE Rate Reduction

Inter-frequency Load Handover

LDR ActionsUL/DL

Resource

4-98 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 267: SYS202m2 Usr7 Ver1 Rev2

LDR Actions for Different Resources Version 1 Rev 2

LDR Actions for Different Resources

☺Code Reshufffling

☺Iu QoS Negotiation

☺AMR Rate Reduction

☺☺☺Inter-System Handover in PS Domain

☺Inter-System Handover in CS Domain

☺BE Rate Reduction

☺☺☺Inter-frequency Load Handover

HSUPAHSDPADCH

Channel TypeLDR Actions

☺Code Reshufffling

☺Iu QoS Negotiation

☺AMR Rate Reduction

☺☺☺Inter-System Handover in PS Domain

☺Inter-System Handover in CS Domain

☺BE Rate Reduction

☺☺☺Inter-frequency Load Handover

HSUPAHSDPADCH

Channel TypeLDR Actions

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-99

USR7

Page 268: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-Frequency Load Handover

Inter-Frequency Load HandoverThe Inter-Frequency Load Handover algorithm is restricted by the inter frequency hard handoveralgorithm switch. Inter-frequency load handover can only be performed when the inter frequency hardhandover algorithm is enabled.The LDR algorithm proceeds as follows:

1. The LDR checks whether the existing cell has a target cell of inter-frequency blind handover. Ifthere is not such a target cell, the action fails, and the LDR takes the next action.

2. The principles of selecting inter-freq handover target cell are different as a result of the differentresources which trigger the basic congestion.a. If the basic congestion is triggered by the power resource:

◊ The LDR checks whether the load difference between the current load and the basiccongestion triggering threshold of each target cell for blind handover is larger than theUL/DL HO load space threshold (both the uplink and downlink conditions must befulfilled), and the other resources (code resource, Iub bandwidth, and NodeB creditresource) in the target cell do not trigger basic congestion.

◊ If the difference is not larger than the threshold, the action fails, and the LDR takes the nextaction.

◊ If there is more than one cell meeting the requirements, the first one is selected as the blindhandover target cell.

b. If the basic congestion is triggered by the code resource:◊ Whether there are blind handover target cells meeting the requirements is decided by the

following conditions:◊ The minimum SF of the target cell is not greater than that of current cell.◊ The difference of code occupy rate between current cell and the target cell is greater

than InterFreq HO code used ratio space threshold.◊ The state of target cell is normal.◊ If there is no such cell, this action fails and the LDR performs the next action. If there

is more than one cell meeting the requirements, the first cell is selected as the blindhandover target cell.

c. If the LDR finds a target cell that meets the specified blind handover conditions, the LDRselects one UE to perform an inter-frequency blind handover to the cell according to the userintegrate priority. For the selected UE, its UL/DL current bandwidth for DCH or GBR bandwidthfor HSPA has to be less than the UL/DL HO maximum bandwidth parameter (both the uplinkand downlink conditions must be fulfilled).◊ If there is more than one such UE, the one with the greatest bandwidth is taken.◊ If the LDR cannot find such a UE, the action fails and the LDR takes the next action.

d. After selecting the target cell and UE, the LDR performs a handover based on the status of theUE and the measured signal quality.

Database ParametersThe parameters that effect LDR with relation to Inter-Frequency load handover can be found in theADD/MOD CELLLDR command.Ul(Dl)InterFreqHoCellLoadSpaceThd — DL/UL Inter-freq cell load handover load space thresholdValue range: 0~100. Physical unit: %.Content: The neighbour Inter-freq cell could be selected as the destination of a load handover, only whenits load space is larger than this threshold.Recommended value: 20.LdrCodeUsedSpaceThd — Value range: 0~100Physical value range: 0~100%, step: 0.01Physical unit: none Content: Code resource usage difference threshold. Inter-frequency handover istriggered when the difference of the resource usage of the current cell and that of the target cell is greaterthan this threshold. The smaller this parameter value, the easier it is to find the qualified target cell forblind handover. Excessively small values of the parameter, however makes the target cell easily entersthe congestion status. The higher the parameter value, the more difficult it is for the inter-frequency blindhandover occurs, and the easier it is to guarantee the stability of the target cell.Recommended value: 13

4-100 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 269: SYS202m2 Usr7 Ver1 Rev2

Inter-Frequency Load Handover Version 1 Rev 2

Inter-Frequency Load HandoverNote: — The smaller this parameter value, the easier it is to find the qualified target cell for blindhandover. However, too small a value easily makes the target cell enter congestion status. The largerthe value, the more difficult for the inter-frequency blind handover to happen and the easier to guaranteethe stability of the target cell.Ul(Dl)InterFreqHoBWThd — Value range: 0~400000Physical unit: bit/sContent: The UE can be selected to process load handover only when its bandwidth is less than thisthreshold. The higher the parameter is, the higher the service rate of the user in handover is, andthe more obviously the cell load is decreased. However, high value of the parameter gives rise to thefluctuation and congestion of the target cell load. The lower the parameter is, the smaller amplitude ofthe load decreases as a result of the inter-frequency load handover, and the easier it is to maintain thestability of the target cell load.Recommended value: 200000

C ongested C ell

Inter-F requency Neighbour C ell

F or each Inter F requency Neighbour C ell check:

• B lind handover allowed

• P ower res ource triggered - UL/DL HO load space threshold (%)

• Code Resource triggered - InterFreq HO code used ratio space (%)

T he UE s elected to be handed over is chos en by:

• UE with lowes t priority

• Is less than and has the least difference between UL/DL Inter-F requenc y C ell L oad Handover Max B andwidth

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-101

USR7

dqfr38
Callout
Cell must be a concentric cell->the same sector with 2 freq
Page 270: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 BE Rate Reduction

BE Rate ReductionThe BE rate reduction algorithm is controlled by the DCCC algorithm switch. BE rate reduction can beperformed only when the DCCC algorithm switch is turned on.Different from the TF restriction of the OLC algorithm, BE rate reduction is implemented by reconfiguringthe bandwidth. Bandwidth reconfiguration requires signalling interaction on the Uu interface and is arelatively long procedure because of this.The reasoning behind the BE rate reduction algorithm is in the same environment, different rates havedifferent downlink transmit powers. The higher the rate, the greater the downlink transmit power.Therefore, the load can be reduced by reconfiguring the bandwidth.For HSUPA services, the consumption of CEs is based on the bit rate. The higher the rate, the more theconsumption of CEs. Therefore, the consumption of CEs can be reduced by bandwidth reconfiguration.The LDR algorithm is implemented as follows:

• Based on the integrate priority, the LDR sorts the RABs in descending order. The top RABs relatedto the BE services (whose current rate is higher than its GBR configured by SET USERGBRcommand) are selected. If the integrate priorities of some RABs are identical, the RAB with thehighest rate is selected. The number of RABs to select is determined by the UL/DL LDR-BE ratereduction RAB number parameter.

• The bandwidth of the selected services is reduced to the specified rate.• If services can be selected, the action is successful. If services cannot be selected, the action fails.

The LDR performs the next action.• The reconfiguration is completed through the RB RECONFIGURATION message on the Uu

interface and through the RL RECONFIGURATION message on the Iub interface.

Database ParametersThe parameters that effect BE rate reduction are found in ADD CELLLDR and also look in the DCCCalgorithm description.UlLdrPsRTQosRenegRabNum — UL LDR-BE rate reduction user numberValue range: 1~10Content: Number of users selected in a UL LDR BE traffic rate reduction.Recommended value: 1.DlLdrBERateReductionRabNum — DL LDR-BE rate reduction user numberValue range: 1~10.Content: Number of users selected in a DL LDR BE traffic rate reduction.Recommended value: 1.

4-102 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 271: SYS202m2 Usr7 Ver1 Rev2

BE Rate Reduction Version 1 Rev 2

BE Rate Reduction

Serving Cell

256 kbit/s PS Background

384 kbit/s BE Interactive

64 kbit/s PS Streaming + 8 kbit/s PS Conv

12.2 kbit/s CS AMR

128 kbit/s BE background

Cell Load goes over thresholds

Uplink

•Reduce data rate of BE service by DCCC algorithm

Downlink

• Reduce data rate of BE service by DCCC algorithm

256 kbit/s BE interactive

Downlink

• Reduce data rate of BE service by DCCC algorithm

256 kbit/s BE interactive256 kbit/s BE interactive

Maximum number of users chosen for rate reduction set by UL/DL LDR-BE rate reduction user number

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-103

USR7

Page 272: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uncontrolled Realtime QoS Renegotiation

Uncontrolled Realtime QoS RenegotiationThe Uncontrolled Real-Time QoS Renegotiation algorithm is restricted by theIU_QOS_RENEG_SWITCH. The uncontrolled real-time QoS renegotiation can only be performedwhen the IU_QOS_RENEG_SWITCH is enabled.The load is reduced by adjusting the rate of the realtime services through uncontrolled realtime OoSrenegotiation. In 3GPP R5, the RNC initiates the RAB renegotiation procedure through the RABMODIFICATION REQUEST message on the Iu interface. Upon receipt of the message, the CN sendsthe RAB ASSIGNMENT REQUEST message to the RNC for RAB parameter reconfiguration. Based onthis function, the RNC can adjust the rate of realtime services to reduce the load.The LDR algorithm is implemented as follows:

1. Based on the integrated priority, the LDR sorts the realtime services in the PS domain in descendingorder. The top services are selected for QoS renegotiation.

2. The LDR performs QoS renegotiation for the selected services. The GBR during service setup isthe maximum rate of the service after QoS renegotiation.

3. The RNC initiates the RAB Modification Request message to the CN for QoS renegotiation.4. If the RNC cannot find a proper service for QoS renegotiation, the action fails. The LDR performs

the next action.

Database ParametersThe command to enable Uncontrolled Realtime QoS Renegotiation is set in the command SETCORRMALGOSWITCH and is described below.IU_QOS_NEG_SWITCH: When the switch is selected, Iu QoS negotiation is used for PS services if thereis the IE of optional RAB values in the RANAP RAB assignment request or relocation request.The parameters that effect BE rate reduction are found in ADD CELLLDR.ULLDRPSRTQOSRENEGUSERNUM — UL LDR un-ctrl RT Qos re-nego user numValue range: 1~10.Content: Number of users selected in a UL LDR uncontrolled real-time traffic QoS re-negotiation.Recommended value: 1.DLLDRPSRTQOSRENEGUSERNUM — DL LDR un-ctrl RT Qos re-nego user numValue range: 1~10.Content: Number of users selected in a DL LDR uncontrolled real-time traffic QoS re-negotiation.Recommended value: 1.

4-104 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 273: SYS202m2 Usr7 Ver1 Rev2

Uncontrolled Realtime QoS Renegotiation Version 1 Rev 2

Uncontrolled Realtime QoS Renegotiation

R NCR NCIub

NodeB

C NC N1. S orts realtime s ervices in P S domain by priority

2. LDR performs QoS renegotiation

3. R NC s ends R AB modification reques t to C N

4. If this action fails LDR performs next action

R AB Modification R equest

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-105

USR7

Page 274: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-system handover in the CS domain

Inter-system handover in the CS domainThe action is restricted by the CS inter-rat handover algorithm switch. This action can only beperformed when the CS inter-rat handover algorithm parameter is enabled.The procedure differs slightly depending on whether the CS users have the "service handover" IE setto "handover to GSM should not be performed" when the RAB was established. The two variants aredescribed below:

• Inter-RAT ’Should Be’ Load Handover in the CS Domain– The cell sizes and coverage modes of 2G and 3G systems are different. Therefore, the blind

handover across systems are not taken into account.– The LDR operates as follows:

◊ Based on the integrate priority, the LDR sorts the UEs with the service handover cells setto "handover to GSM should be performed" in the CS domain in descending order. The topCS services are selected, and the number of UEs is controlled by the UL/DL CS shouldbe ho user number parameter.

◊ For the selected UEs, the LDR module sends the load handover command to the inter-RAThandover module to ask the UEs to be handed over to the 2G system.

◊ The handover module decides to trigger the inter-RAT handover, depending on thecapability of the UE to support compressed mode.

◊ If no UE that satisfies the handover criteria is found, the LDR takes the next action.• Inter-RAT ’Should Not Be’ Load Handover in the CS Domain

– The algorithm for this action is the same as that in Inter-RAT Should Be Load Handover inthe CS Domain. The difference is that this action only involves CS users with the "servicehandover" IE set to "handover to GSM should not be performed".

– The number of UEs is controlled by the UL/DL CS should not be ho user number parameter.

Database ParametersThe parameter to enable Inter-system handover in the CS domain is found in SETCORRMALGOSWITCH and is described below.INTER_RAT_CS_OUT_SWITCH: When the switch is selected, the RNC is allowed to initiateinter-frequency measure control and the CS inter-RAT hard handover from the 3G network to the 2Gnetwork.The parameters to control how many UEs maybe handed over are found in the command ADD CELLLDRand are described below.DlCSInterRatShouldBeHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a DL LDR CS domain inter-RAT SHOULD BE load handover. Thetarget subscribers of this parameter are the CS domain subscribers. Because the CS domain subscribersare session subscribers in general and they have little impact on load, you can set this parameter to acomparatively high value.Recommended value: 3DlCSInterRatShouldBeHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a DL LDR CS domain inter-RAT SHOULD BE load handover. Thetarget subscribers of this parameter are the CS domain subscribers. Because the CS domain subscribersare session subscribers in general and they have little impact on load, you can set this parameter to acomparatively high value.Recommended value: 3UlCSInterRatShouldBeHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a UL LDR CS domain inter-RAT SHOULD BE load handover. Thetarget subscribers of this parameter are the CS domain subscribers. Because the CS domain subscribersare session subscribers in general and they have little impact on load, you can set this parameter to acomparatively high value.Recommended value: 3UlCSInterRatShouldNotHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a UL LDR CS domain inter-RAT SHOULD NOT BE load handover.The target subscribers of this parameter are the CS domain subscribers. Because the CS domain

4-106 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 275: SYS202m2 Usr7 Ver1 Rev2

Inter-system handover in the CS domain Version 1 Rev 2

Inter-system handover in the CS domainsubscribers are session subscribers in general and they have little impact on load, you can set thisparameter to a comparatively high value.Recommended value: 3

C onges ted C ell

Inter-S ys tem Neighbour C ell

T he UE s elec ted to be handed over is c hos en by:

• UE ’s with lowes t priority for P S number up to databas e relevant parameters

• C heck s elec ted UE ’s capabilities to make s ure it c an handover to G S M.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-107

USR7

Page 276: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-system handover in the PS domain

Inter-system handover in the PS domainThe action is restricted by the PS inter-rat handover algorithm switch. This action can only beperformed when the PS inter-rat handover algorithm is enabled.The procedure differs slightly depending on whether the PS users have the "service handover" IE setto "handover to GSM should not be performed" when the RAB was established. The two variants aredescribed below:

• Inter-RAT ’Should Be’ Load Handover in the PS Domain– The algorithm for this action is the same as that in Inter-RAT Should Be Load Handover in

the CS Domain. The difference is that this action only involves PS users with the "servicehandover" IE set to "handover to GSM should be performed", but not CS users.

– The number of UEs is controlled by the UL/DL PS should be ho user number parameter.• Inter-RAT ’Should Not Be’ Load Handover in the PS Domain

– The algorithm for this action is the same as that in Inter-RAT Should Not Be Load Handoverin the CS Domain. The difference is that this action only involves PS users with the "servicehandover" IE set to "handover to GSM should not be performed", but not CS users.

– The number of UEs is controlled by the UL/DL PS should not be ho user number parameter.

Database ParametersThe parameter to enable Inter-system handover in the PS domain is found in SETCORRMALGOSWITCH and is described below.INTER_RAT_PS_OUT_SWITCH: When the switch is selected, the RNC is allowed to initiateinter-frequency measure control and the PS inter-RAT hard handover from the 3G network to the 2Gnetwork.The parameters to control how many UEs maybe handed over are found in the command ADD CELLLDRand are described below.DlPSInterRatShouldBeHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a DL LDR PS domain inter-RAT SHOULD BE load handover. Thetarget subscribers of this parameter are the PS domain subscribers. Because the PS domain subscribersare session subscribers in general and they have little impact on load, you can set this parameter to acomparatively high value.Recommended value: 1DlPSInterRatShouldBeHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a DL LDR PS domain inter-RAT SHOULD BE load handover. Thetarget subscribers of this parameter are the PS domain subscribers. Because the PS domain subscribersare session subscribers in general and they have little impact on load, you can set this parameter to acomparatively high value.Recommended value: 1UlPSInterRatShouldBeHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a UL LDR PS domain inter-RAT SHOULD BE load handover. Thetarget subscribers of this parameter are the PS domain subscribers. Because the PS domain subscribersare session subscribers in general and they have little impact on load, you can set this parameter to acomparatively high value.Recommended value: 1UlPSInterRatShouldNotHOUeNum — Value range: 1~10Physical unit: noneContent: Number of users selected in a UL LDR PS domain inter-RAT SHOULD NOT BE load handover.The target subscribers of this parameter are the PS domain subscribers. Because the PS domainsubscribers are session subscribers in general and they have little impact on load, you can set thisparameter to a comparatively high value.Recommended value: 1

4-108 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 277: SYS202m2 Usr7 Ver1 Rev2

Inter-system handover in the PS domain Version 1 Rev 2

Inter-system handover in the PS domain

C onges ted C ell

Inter-S ys tem Neighbour C ell

T he UE s elec ted to be handed over is c hos en by:

• UE ’s with lowes t priority for P S number up to databas e relevant parameters

• C heck s elec ted UE ’s capabilities to make s ure it c an handover to G S M.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-109

USR7

Page 278: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 AMR Rate Reduction

AMR Rate ReductionThe action is restricted by the AMRC algorithm switch. This action can only be performed when theAMRC algorithm is enabled.In the WCDMA system, voice services work in eight AMR modes. Each mode has its own rate. Therefore,mode control is functionally equal to rate control.

LDR Algorithm for AMR Rate Control in the DownlinkThe LDR algorithm is implemented in the downlink as follows:

1. Based on the integrate priority, the LDR sorts the RABs in descending order. The top UEs accessingthe AMR services (conversational) and with the bit rate higher than the GBR are selected. Thenumber of selected RABs is determined by the DLLDRAMRRATEREDUCTIONRABNUMparameter.

2. The RNC sends the Rate Control request message through the Iu-UP to the CN to adjust the AMRrate to the GBR.

3. If the RNC cannot find a proper service for the AMR rate reduction, the action fails. The LDRperforms the next action.

LDR Algorithm for AMR Rate Control in the UplinkThe LDR algorithm is implemented in the uplink as follows:

1. Based on the integrate priority, the LDR sorts the RABs in descending order. The top UEs accessingthe AMR services (conversational) and with the bit rate higher than the GBR are selected. Thenumber of selected RABs is determined by the ULLDRAMRRATEREDUCTIONRABNUMparameter.

2. The RNC sends the TFC CONTROL command to the UE to adjust the AMR rate to the assuredrate.

3. If the RNC cannot find a proper service for the AMR rate reduction, the action fails. The LDRperforms the next action.

Database ParametersThe parameter to enable AMRC rate reduction is found in SET CORRMALGOSWITCH and is describedbelow.AMRC_SWITCH: When the switch is selected and the AMRC license is activated, the AMR controlfunction is enabled for AMR services.The parameters to configure AMRC rate reduction are found in the command ADD CELLLDR and aredescribed below.DlLdrAMRRateReductionRabNum — Value range: 1~10.Content: Number of RABs selected in a DL LDR AMR traffic rate reduction.Recommended value: 3.UlLdrAMRRateReductionRabNum — Value range: 1~10.Content: Number of RABs selected in a UL LDR AMR traffic rate reduction.Recommended value: 3.

4-110 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 279: SYS202m2 Usr7 Ver1 Rev2

AMR Rate Reduction Version 1 Rev 2

AMR Rate Reduction

S erving C ell

256 kbit/s P S B ackground

12.2 kbit/s C S AMR

12.2 kbit/s C S AMR

12.2 kbit/s C S AMR

Downlink

Integrate Priority

Bit Rate Higher than GBR

DlLdrAMRRateReductionRabNum

Uplink

Integrate Priority

Bit Rate Higher than GBR

UlLdrAMRRateReductionRabNum

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-111

USR7

Page 280: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Code Reshuffling

Code ReshufflingWhen the cell is in basic congestion for shortage of code resources, sufficient code resources can bereserved for subsequent service access through code reshuffling. Code subtree adjustment refers to theswitching of users from one code subtree to another. It is used for code tree defragmentation, so as tofree smaller codes first.The algorithm is implemented as follows:

1. Initialize the SF_Cur of the root node of subtrees to Cell LDR SF reserved threshold.2. Traverse all the subtrees with this SF_Cur at the root node. Leaving the subtrees occupied by

common channels and HSDPA channels out of account, take the subtrees in which the number ofusers is not larger than the value of the Max user number of code adjust parameter as candidatesfor code reshuffling.– If such candidates are available, go to 3.– If no such candidate is available, subtree selection fails. This procedure ends.

3. Select a subtree from the candidates according to the setting of the LDR code priority indicatorparameter.– If this parameter is set to TRUE, select the subtree with the largest code number from the

candidates.– If this parameter is set to FALSE, select the subtree with the smallest number of users from

the candidates. In the case that multiple subtrees have the same number of users, select thesubtree with the largest code number.

4. Treat each user in the subtree as a new user and allocate code resources to each user.5. Initiate the reconfiguration procedure for each user in the subtree and reconfigure the channel

codes of the users to the newly allocated code resources.– The reconfiguration procedure on the UU interface is implemented through the PHYSICAL

CHANNEL RECONFIGURATION message and that on the Iub interface through the RLRECONFIGURATION message.

The example shown Cell LDR SF reserved threshold is set to SF8 and Max user number of codeadjust is set to 1.

Database ParametersThe parameter that effects the code reshuffling is found in the command ADD CELLLDR and is explainedbelow.CellLdrSfResThd — Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256Physical unit: noneContent: Cell SF reserved threshold. The code load reshuffling could be triggered only when theminimum available SF of a cell is higher than this threshold. The lower the code resource LDR triggerthreshold is, the easier the downlink code resource enters the initial congestion status, the easier theLDR action is triggered, and the easier the subscriber perception is affected. But a lower code resourceLDR trigger threshold causes a higher admission success rate because the resource is reserved.Recommended value: SF8LdrCodePriUseInd — Value range: TRUE, FALSEPhysical unit: noneContent: FALSE means not considering the code priority during the code reshuffling. TRUE meansconsidering the code priority during the code reshuffling. If the parameter is TRUE, the codes with highpriority are reserved during the code reshuffling. It is good for the code resource dynamic sharing, whichis a function used for the HSDPA service.Recommended value: FALSEMaxUserNumCodeAdj — Value range: 1~3.Physical unit: None.Content: This parameter specifies the number of users selected in code reshuffling. Code reshuffling canbe triggered only when the number of users on a code is no greater than the threshold. Code reshufflinghas a big impact on the QoS. In addition, the reshuffled subscribers occupy two code resources duringcode reshuffling. Thus, the parameter should be set to a comparatively low value.Recommended value: 1.

4-112 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 281: SYS202m2 Usr7 Ver1 Rev2

Code Reshuffling Version 1 Rev 2

Code Reshuffling

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-113

USR7

Page 282: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Overload Control (OLC) Algorithm

Overload Control (OLC) AlgorithmAfter the UE access is granted, the power consumed by a single link is adjusted by the single link powercontrol algorithm. The power varies with the mobility of the UE and the changes in the environment andthe source rate. In some situations, the total power load of the cell may be higher than the target load.To ensure system stability, overload congestion must be handled.Only power resources could result in overload congestion. Hard resources such as equivalent usernumber, Iub bandwidth, and credit resources do not cause overload congestion.

OLC TriggeringOnly power resources and interference can result in overload congestion. Hard resources such as theequivalent number of users, Iub bandwidth, and credit resources do not cause overload congestion.UL_UU_OLC and DL_UU_OLC under the Cell LDC algorithm switch parameter control the functionalityof the overload congestion control algorithm.If the current UL/DL load of an R99 cell is higher than or equal to the UL/DL OLC Trigger threshold for1000ms, the cell works in overload congestion state and the related overload handling action is taken.If the current UL/DL load of the R99 cell is lower than the UL/DL OLC Release threshold for 1000ms,the cell comes back to the normal state.The HSPA cell has the same uplink decision criterion as the R99 cell. The load in the downlink, however,is the sum of load of the non-HSPA power (transmitted carrier power of all codes not used for HS-PDSCHor HS-SCCH transmission) and the GBP.In addition to periodic measurement, event-triggered measurement is applicable to OLC.If the OLC_EVENTMEAS is set to ON, the RNC requests the initiation of an event E measurement onpower resource in the NodeB. In the associated request message, the reporting criterion is specified,including the key factors,UL/DL OLC trigger threshold and UL/DL OLC release threshold. Then theNodeB checks the current power load in real time according to this criterion and reports the status to theRNC periodically if the conditions of reporting are met.

Database ParametersThe command to enable UL and DL OLC is found in the command ADD CELLALGOSWITCH and isdescribed below.UL_UU_OLC: UL UU overload congestion control algorithm. When the cell is overloaded in UL, thisalgorithm reduces the cell load in UL by quick TF restriction or UE release.DL_UU_OLC: DL UU overload congestion control algorithm. When the cell is overloaded in DL, thisalgorithm reduces the cell load in DL by quick TF restriction or UE release.OLC_EVENTMEAS: Control OLC event measurement. This algorithm starts the OLC eventmeasurement.The parameters that control OLC thresholds are found in the ADD CELLLDM command.ULOLCTRIGTHD — UL OLC trigger thresholdValue range: 0~100 Physical value range: 0~1; step: 0.01.Content: If the UL load of the cell is not lower than this threshold, the UL overload congestion controlfunction of the cell will be triggered.Recommended value: 95.ULOLCRELTHD — UL OLC release thresholdValue range: 0~100. Physical value range: 0~1; step: 0.01.Content: If the UL load of the cell is lower than this threshold, the UL overload congestion control functionof the cell will be stopped.Recommended value: 85.DLOLCTRIGTHD — DL OLC trigger thresholdValue range: 0~100 Physical value range: 0~1; step: 0.01.Content: If the DL load of the cell is not lower than this threshold, the DL overload congestion controlfunction of the cell will be triggered.Recommended value: 95.DLOLCRELTHD — DL OLC release threshold

4-114 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 283: SYS202m2 Usr7 Ver1 Rev2

Overload Control (OLC) Algorithm Version 1 Rev 2

Overload Control (OLC) Algorithm

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-115

USR7

Page 284: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 General OLC Procedure

General OLC ProcedureThe general OLC procedure covers the following actions: TF control of BE services, channel switching ofBE services, and release of RABs. The RNC takes periodical actions if overload congestion is detected.When the cell is overloaded, the RNC takes one of the following actions in each period (defined by theOLC period timer length parameter) until the congestion is resolved:

• TF control of BE service (only for DCH BE service)• Switching BE services to common channel• Choosing and releasing the RABs (for HSPA or DCH service)

If the first action fails or the first action is completed but the cell is still in congestion, then the secondaction is taken.

Database ParametersThe parameter to set the OLC period timer length is found in the command SET LDCPERIOD and isdescribed below.OlcPeriodTimerLen — Value range: 100~86400000Physical unit: msContent: Identifying the period of the OLC execution. When overload occurs, execution of OLC candynamically reduce the cell load. When setting the parameter, consider the hysteresis for whichthe load monitoring responds to the load change. For example, when the layer 3 filter coefficientis 6, the hysteresis for which the load measurement responds to the step-function signals is about2.8s, namely that the system can trace the load control effect about 3 s later after each loadcontrol. In this case, the OLC period timer length cannot be smaller than 3s. OlcPeriodTimerLenalong with ULOLCFTFRstrctUserNum, DLOLCFTFRstrctUserNum, ULOLCFTFRSTRCTTimes,DLOLCFTFRSTRCTTimes, ULOLCTraffRelUserNum, and DLOLCTraffRelUserNum determine the timeit takes to release the uplink/downlink overload. If the OLC period is excessively long, the systemmay respond very slowly to overload. If the OLC period is excessively short, unnecessary adjustmentmay occur before the previous OLC action has taken effect, and therefore the system performance isaffected.Recommended value: 3000

4-116 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 285: SYS202m2 Usr7 Ver1 Rev2

General OLC Procedure Version 1 Rev 2

General OLC Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-117

USR7

Page 286: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 OLC Algorithm for TF Control in the Downlink

OLC Algorithm for TF Control in the DownlinkThe OLC algorithm for TF control in the downlink is implemented as follows:

1. Based on the integrated priority, the OLC sorts the RABs in the descending order. The RABswith BE services and with its bit rate higher than DCCC rate reduction threshold and with thelowest integrated priority (with the highest integrated priority value) are selected. The selectedRAB number is DL OLC fast TF restrict RAB number.

2. The RNC sends the TF control indication message to the MAC, during a set time (till congestion isreleased and traffic volume upsizing), MAC will restricts the TFC selection of these BE services toreduce data rate step by step.MAC restricts the TFC selection by calculating the maximum TB number with the formula:TFmax(N+1) = TFmax(N)* RateRstrctCoefWhere:– TFmax(0) is the maximum TB number of BE service before it is selected to do the TF control.– TFmax(N+1) is the maximum TB number during time T0 + RateRstrctTimerLen * (N) to T0

+ RateRstrctTimerLen * (N+1), where T0 is the time MAC receiving TF control indicationmessage.

3. Each time, RNC will select a certain number of RABs (which is determined by “DL OLC fastTF restrict RAB number” ) to perform TF control, and each MAC of selected RABs will receiveone TF control indication message. The times to perform TF control is determined by theDLOLCFTFRSTRCTTimes parameter.

4. If the RNC cannot find a proper service for TF control, the action fails. The OLC performs the nextaction.

5. If the congestion is released, the RNC sends the congestion release indication to the MAC.6. If the congestion is released and 4A report is received, and if rate recover timer (which length is

RateRecoverTimerLen) is started and when this timer is expired, MAC will increase data rate stepby step.

The parameters that control this part of the feature are set in ADD/MOD CELLOLC and are describedbelow:RATERSTRCTCOEF — Data rate restrict coefficientValue range: 1~99. Physical unit: %.Content: Data rate restrict coefficient in fast TF restrict. The smaller this parameter is, the greater theTF restrict effect.Recommended value: 68.RATERSTRCTTIMERLEN — Data rate restrict timer lengthValue range: 1~65535. Physical unit: ms.Content: Data rate restrict timer length in fast TF restrict.Recommended value: 3000.DLOLCFTFRSTRCTTIMES/ULOLCFTFRSTRCTTIMES — DL/UL OLC fast TF restrict timesValue range: 0~100.Content: Times of fast TF restrict of DL/UL OLC.Recommended value: 3.DLOLCFTFRSTRCTUSERNUM/ULOLCFTFRSTRCTUSERNUM — DL/UL OLC fast TF restrict usernumberValue range: 1~10.Content: Number of users selected in a fast TF restrict of DL OLC.Recommended value: 3.

4-118 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 287: SYS202m2 Usr7 Ver1 Rev2

OLC Algorithm for TF Control in the Downlink Version 1 Rev 2

OLC Algorithm for TF Control in the Downlink

S elec ted R AB – 144 kbit/s Interactive (B E ) R AB (Max bloc k s ize is 9 with eac h bloc k 336 bits in T F S )

336336

336336

336336

336336

336336

336336

336336

336336

336336

Ins truc ted to reduc e T F

If R ateR strctCoef = 50%

9 x 50% = 4 (rounding down) T his format s upported in T F S

After T imer R ateR strctT imerLen expires again ins tructed to reduce T F

4 x 50% = 2 T his format s upported in TF S

Ins truc ted to res tore T F

Increas e T F by 1 (but format of 3 uns upported in T F S s o goes to 4)

After R ateR ecoverT imerLen expires again instructed to increas e T F by one, eventually returning to the maximum

T he times to perform T F control is determined by the DLOLCFTFR S TR CTTimes

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-119

USR7

Page 288: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 OLC Algorithm for TF Control in the Uplink

OLC Algorithm for TF Control in the UplinkFor UEs accessing the DCH service, the RNC, in compliance with 3GPP TS25.331, restricts the TFCof the UE by sending the TRANSPORT FORMAT COMBINATION CONTROL message to the UE. Theslide opposite shows the message flow, in which the UE does not have any response if the procedurecan be performed without failure.The OLC algorithm for TF control in the uplink is implemented as follows:

1. Based on the integrated priority, the OLC sorts the BE services in the descending order. The BEservices with the rate higher than DCCC rate reduction threshold and with the lowest integratedpriority (with the highest integrate priority value) are selected. The selected RAB number isrestricted by UL OLC fast TF restrict RAB number.

2. The RNC sends the TRANSPORT FORMAT COMBINATION CONTROL message to the UE thataccesses the specified service. TRANSPORT FORMAT COMBINATION CONTROL messageincludes the following IEs:– Transport Format Combination Set Identity: define the available TFC UE can select, or to say,

the restricted TFC sub-set, it is always the two TFC corresponding to the lowest data rate;– TFC Control duration: defines the period in multiples of 10ms frames for which the restricted

TFC sub-set is to be applied, it’s set to a random value range from 10ms to 5120ms to avoiddata upsizing at the same time.

After the TFC control duration expired, UE can apply any TFC of TFCS before TF control.3. Each time, RNC will select a certain number of RABs (which is determined by “UL OLC fast TF

restrict RAB number” ) to perform TF control, and each UE of selected RABs will receive theTRANSPORT FORMAT COMBINATION CONTROL message. The times to perform TF control isdetermined by the ULOLCFTFRSTRCTTimes parameter.

4. If the RNC cannot find a proper service the OLC performs the next action.The parameters that control this part of the feature are set in ADD/MOD CELLOLC and are describedbelow:ULOLCFTFRSTRCTTIMES — UL OLC fast TF restrict timesValue range: 0~100.Content: Times of fast TF restrict of UL OLC.Recommended value: 3.ULOLCFTFRSTRCTUSERNUM — UL OLC fast TF restrict user numberValue range: 1~10.Content: Number of users selected in a fast TF restrict of UL OLC.Recommended value: 3.

4-120 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 289: SYS202m2 Usr7 Ver1 Rev2

OLC Algorithm for TF Control in the Uplink Version 1 Rev 2

OLC Algorithm for TF Control in the Uplink

UE UT R AN

T R ANS P OR T F OR MAT C OMB INAT ION C ONT R OL

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-121

USR7

Page 290: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Switching BE Services to Common Channel

Switching BE Services to Common ChannelThe OLC algorithm for switching BE services to common channel operates as follows:

1. Based on the user integrate priority, the OLC sorts all UEs that only have PS services includingHSPA and DCH services (except UEs having also a streaming bearer) in descending order.

2. The top N UEs are selected. The number of selected UEs is equal to Transfer Common Channeluser number. If UEs cannot be selected, the action fails. The OLC performs the next action.

3. The selected UEs are switched to common channel.This function can be disabled by setting the Transfer Common Channel user number parameter to 0.Whether the selected UEs can be switched to common channel depends on thesetting of PS_BE_STATE_TRANS_SWITCH, HSDPA_STATE_TRANS_SWITCH, orHSUPA_STATE_TRANS_SWITCH.

Database ParametersThe parameter to set how many UEs can be moved to common channels is in the command ADDCELLOLC andis described below.TransCchUserNum — Transfer Common Channel User numberValue range: 0~10Content: When the system is overloaded and congested, users on the DCH can be reconfigured tothe CCH in order to reduce the cell load and recover the system. The mechanism of the OLC is thatan action is performed in each [OLC period] and some services are selected based on the action rulesto perform this action. This parameter defines the maximum number of users selected in executingreconfiguration to the CCH. If the parameter value is too high, the OLC action may fluctuate greatly andover control may occur (the state of overload and congestion turns into another extreme–underload).If the parameter value is too low, the OLC action has a slow response and the effect is not apparent,affecting the OLC performance.Recommended value (default value): 1Also set in SET CORRMALGOSWITCH are the parameters that allow the state changes.PS_BE_STATE_TRANS_SWITCH: When the switch is selected, UE RRC status transition(CELL_FACH/CELL_PCH/URA_PCH) is allowed at the RNC.HSDPA_STATE_TRANS_SWITCH: When the switch is selected, the status of the UE RRC that carryingHSDPA services can be changed to CELL_FACH at the RNC. If a PS BE service is carried over theHS-DSCH, the switch PS_BE_STATE_TRANS_SWITCH should be selected simultaneously. If a PSreal-time service is carried over the HS-DSCH, the switch PS_NON_BE_STATE_TRANS_SWITCHshould be selected simultaneously.HSUPA_STATE_TRANS_SWITCH: When the switch is selected, the status of the UE RRC thatcarrying HSUPA services can be changed to CELL_FACH at the RNC. If a PS BE service is carriedover the E-DCH, the switch PS_BE_STATE_TRANS_SWITCH should be selected simultaneously. Ifa PS real-time service is carried over the E-DCH, the switch PS_NON_BE_STATE_TRANS_SWITCHshould be selected simultaneously.

4-122 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 291: SYS202m2 Usr7 Ver1 Rev2

Switching BE Services to Common Channel Version 1 Rev 2

Switching BE Services to Common Channel

R NCR NCIub

NodeB

C NC N

Overload detected

Switch BE services to RACH/FACH

UptoTransCchUserNum

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-123

USR7

Page 292: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Release of some UEs

Release of some UEsThe OLC algorithm for release of some UEs is implemented as follows:

1. Based on the integrated priority, the OLC sorts all RABs in the descending order.2. The top RABs are selected. The number of selected UEs is equal to UL/DL OLC traff release

RAB number.3. The selected RABs are released directly.Note: — This function can be disabled by setting the ULOLCTRAFFRELRABNUM/DLOLCTRAFFRELRABNUM parameter to 0.The release of UEs is valid to only one OLC action. That is, the number of UEs released during each OLCaction is equal to the value defined by the ULOLCTRAFFRELRABNUM/DLOLCTRAFFRELRABNUMparameter.The parameters that control this part of the feature are set in ADD/MOD CELLOLC and are describedbelow:DLOLCTRAFFRELUSERNUM — DL OLC traff release user numberValue range: 0~10.Content: Number of users released in a DL OLC service release.Recommended value: 0.ULOLCTRAFFRELUSERNUM — UL OLC traff release user numberValue range: 0~10.Content: Number of users released in a UL OLC service release.Recommended value: 0.

4-124 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 293: SYS202m2 Usr7 Ver1 Rev2

Release of some UEs Version 1 Rev 2

Release of some UEs

• If the max number of fas t B E c ontrol iterations has been reac hed or if it was not pos s ible to identify at leas t one R AB to apply fas t B E c ontrol, the downlink OL C proceeds to the s election of us ers to be dropped.

S erving C ell

256 kbit/s P S B ackground

384 kbit/s B E Interactive

64 kbit/s P S S treaming + 8 kbit/s P S C onv

12.2 kbit/s C S AMR• P riority bas ed

• Upto UL /DL OL C traff releas e R AB number

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

4-125

USR7

Page 294: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Release of some UEs

This page intentionally left blank.

4-126 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 295: SYS202m2 Usr7 Ver1 Rev2

Rate Control Description Version 1 Rev 2

Chapter 5

Rate Control Description

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-1

USR7

Page 296: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Rate Control Description

This page intentionally left blank.

5-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 297: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter ObjectivesThe student will be able to:

• State the purpose and describe the function of AMR control algorithm• Describe the use of MML commands to add cell-oriented AMRC• State the purpose and describe the function of AMR—WB control algorithm• Describe the use of MML commands to add cell-oriented AMRC-WB• Describe the Dynamic Channel Configuration procedure;• Describe the UE state transition procedure.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-3

USR7

Page 298: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Rate Control Introduction

Rate Control IntroductionRate control triggers rate upsizing, rate downsizing, and handover for different services according to theconsumption of resources.Rate control in the WCDMA system has two types: rate control over Adaptive Multi Rate (AMR) servicesand rate control over Best Effort (BE) services. Rate control herein is described in terms of the followingalgorithms:

• Adaptive Multi-Rate Control (AMRC) / AMRC-WB algorithm. They are implemented by the RNC.They dynamically adjust the transport format based on the cell load, link power, and Iub resourceutilization, so as to achieve the balance between the system load, link stability, Iub resources,and link QoS. The UL AMRC/AMRC-WB algorithm and the DL AMRC/AMRC-WB algorithm workindependently.

• Dynamic Channel Configuration Control (DCCC) algorithm: It is implemented by the RNC. Itcontrols the rate of BE services according to the traffic volume, throughput, radio link quality, orcongestion state. The UL DCCC algorithm and the DL DCCC algorithm work independently.

• Ljnk stability control algorithm: It is implemented by the RNC. It triggers rate downsizing,inter-frequency handover and inter-RAT handover to guarantee the stability of links and QoSof services. The rate downsizing of this algorithm is the power-based rate downsizing inAMRC/AMRC-WB and DCCC.

Impact of AMRC/AMRC-WB on System PerformanceThe AMRC/AMRC-WB algorithm can be used to steer the UL permitted highest AMR/AMR-WB speechcodec mode down according to the UE transmit power. In this way, the UL coverage is expanded.The AMRC/AMRC-WB algorithm can be used to steer the permitted highest AMR/AMR-WB speechcodec mode down according to the downlink DPCH transmit code power or UE transmit power. In thisway, the system capacity is increased in terms of the maximum number of UEs that the system canprocess.The AMRC/AMRC-WB algorithm can be used to choose a proper AMR/AMR-WB speech codec modeaccording to the quality of the transmission environment. In this way the speech quality is ensured.

DCCC Impact on System PerformanceEvery time rate adjustment occurs, there is interactive signaling on the Uu amd Iub interfaces. Theimpact on the system performance has relations with the user profile mode and the user traffic mode. Ingeneral, there is little impact of DCCC on the system performance.

Link Stability Control Algorithm Impact on System PerformanceLink stability control algorithm has no impact on system performance

5-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 299: SYS202m2 Usr7 Ver1 Rev2

Rate Control Introduction Version 1 Rev 2

Rate Control Introduction

RNCRNCCN

Iu

Iub

• AMRC Rate Control

• DCCC Rate Control

• Link Stability

NB

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-5

USR7

Page 300: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Initial Access Rate of AMRC

Initial Access Rate of AMRCInitial Access Rate of AMRC provides the definition of initial access rate, values of initial access rate andcontrollable mode set in different situations.

Definition of Initial Access RateUplink, the initial access rate is not only the maximum permitted bit rate at the start of the communicationphase, but also the maximum bit rate that the UL AMRC algorithm can select, that is, the maximum bitrate in the uplink controllable AMR speech codec mode set (controllable mode set for short) and uplinksupported AMR speech codec mode set (supported mode set for short).Downlink, the initial access rate is the maximum permitted bit rate at the start of the communicationphase.

Value of Initial Access RateWhen the AMRC algorithm is enabled:

• If the cell load is in basic congestion, the initial access rate is the GBR in the RAB parameters.• If the cell load is normal, commonly, the initial access rate is the maximum rate that is in the RAB

assignment message sent from the CN and meets both the following conditions:– Higher than or equal to the GBR in the RAB assignment message sent from the CN– Lower than or equal to the UE-priority-oriented maximum rate that is set on the RNC LMT

The UE-priority-oriented maximum rate refers to the Max mode of narrowband AMRC for goldenusers, Max mode of narrowband AMRC for silver users, and Max mode of narrowband AMRC forcopper users parameters.If the UE-priority-oriented maximum rate is lower than the GBR in the RAB assignment message, thenthe initial access rate is the GBR.When the AMRC algorithm is disabled, the initial access rate is the maximum rate that is in the RABassignment message sent from the CN and meets both the following conditions:

• Higher than or equal to the GBR in the RAB assignment message sent from the CN• Lower than or equal to the UE-priority-oriented maximum rate that is set on the RNC LMT.

In this case, all the AMR rates in the controllable mode set, a subset of the set in the RAB assignmentmessage, are no lower than GBR and no higher than the UE-priority-oriented maximum rate configuredon the RNC LMT.

Database ParametersThe parameter to enable AMRC is found in the command SET CORRMALGOSWITCH and is describedbelow.AMRC_SWITCH: When the switch is selected and the AMRC license is activated, the AMR controlfunction is enabled for AMR services.The commands SET AMRC or ADD CELLAMRC is used to set the maximum rates for each type of userand is described below.GoldMaxMode — Value range: NBAMR_BITRATE_4.75K, NBAMR_BITRATE_5.15K,NBAMR_BITRATE_5.90K, NBAMR_BITRATE_6.70K, NBAMR_BITRATE_7.40K,NBAMR_BITRATE_7.95K, NBAMR_BITRATE_10.20K, NBAMR_BITRATE_12.20KPhysical value range: 4.75, 5.15, 5.90, 6.70, 7.40, 7.95, 10.20, 12.20Physical unit: kbit/s Content: maximum rate of the narrowband AMR speech service for gold usersRecommended value: NBAMR_BITRATE_12.20KSilverMaxMode — Value range: NBAMR_BITRATE_4.75K, NBAMR_BITRATE_5.15K,NBAMR_BITRATE_5.90K, NBAMR_BITRATE_6.70K, NBAMR_BITRATE_7.40K,NBAMR_BITRATE_7.95K, NBAMR_BITRATE_10.20K, NBAMR_BITRATE_12.20KPhysical value range: 4.75, 5.15, 5.90, 6.70, 7.40, 7.95, 10.20, 12.20Physical unit: kbit/s Content: maximum rate of the narrowband AMR speech service for silver usersRecommended value: NBAMR_BITRATE_12.20KCopperMaxMode — Value range: NBAMR_BITRATE_4.75K, NBAMR_BITRATE_5.15K,NBAMR_BITRATE_5.90K, NBAMR_BITRATE_6.70K, NBAMR_BITRATE_7.40K,NBAMR_BITRATE_7.95K, NBAMR_BITRATE_10.20K, NBAMR_BITRATE_12.20KPhysical value range: 4.75, 5.15, 5.90, 6.70, 7.40, 7.95, 10.20, 12.20

5-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 301: SYS202m2 Usr7 Ver1 Rev2

Initial Access Rate of AMRC Version 1 Rev 2

Initial Access Rate of AMRCPhysical unit: kbit/sContent: maximum rate of the narrowband AMR speech service for copper usersRecommended value: NBAMR_BITRATE_12.20K

RNCRNCCNCN

Iu

Iub

RAB ASSIGNMENT PROCEDURE

• Guaranteed Bit Rate (GBR)

RAB ASSIGNMENT PROCEDURE

• Guaranteed Bit Rate (GBR)Mode 8 12.2 Kbits/s

Mode 7 10.2 Kbits/s

Mode 6 7.95 Kbits/s

Mode 5 7.4 Kbits/s

Mode 4 6.7 Kbits/s

Mode 3 5.9 Kbits/s

Mode 2 5.15 Kbits/s

Mode 1 4.75 Kbits/s

SID 1.8 Kbit/s

0 bits

SET CORRMALGOSWITCH: ChSwitch=AMRC_SWITCH-1;

ADD CELLAMRC: GoldMaxMode=NBAMR_BITRATE_12.20K, SilverMaxMode=NBAMR_BITRATE_10.20K, CopperMaxMode=NBAMR_BITRATE_7.95K;

Normal State = Max rate in RAB Ass Proc

Congested State = GBR

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-7

USR7

dqfr38
Callout
Only two modes are supported.
Page 302: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Controllable Mode Set

Controllable Mode SetThe key terms involved in the AMRC/AMRC-WB (AMRC-WB not fully described) feature are:

• Guaranteed Bit Rate (GBR) — The GBR is the minimum bit rate for the RNC to adjust. It iscontained in the RAB assignment message that the CN sends to the RNC.

• The supported AMR speech codec mode set — The set consists of all the AMR speech codecmodes that can be used for the service transport. The set is decided by the RNC according to themode set specified by the RAB assignment.

• The controllable AMR speech codec mode set — The set consists of the AMR speech codec modesthat are contained in the supported AMR speech codec mode set and are equal to or larger thanthe GBR. The modes in this set can be selected by the AMRC/AMRC-WB algorithm.

Note: In the current version, there are two rates in the controllable mode set at most.

DescriptionOnly when AMRC algorithm is enabled, the controllable mode set is valid.

• For links in the uplink,– If the initial access rate is GBR in the RAB assignment message, the uplink controllable mode

set contains only one rate, that is, {GBR in the RAB assignment message}.– If the initial access rate is higher than the GBR in the RAB assignment message, the uplink

controllable mode set is {GBR in the RAB assignment message, initial access rate}.• For links in the downlink,

– In the case of Iu UP version 2 (predefined SDU size ref 3GPP 25.415), the downlink controllablemode set contains all the rates that are included in the RAB assignment message and higherthan or equal to the GBR.

– In the case of Iu UP version 1 (transparent mode ref 3GPP 25.415) and code-resource-savingalgorithm disabled, assume that the maximum rate that is in the RAB assignment messagesent from the CN and meets both of the following conditions is expressed as Rmax:◊ Higher than or equal to the GBR in the RAB assignment message sent from the CN◊ Lower than or equal to the UE-priority-oriented maximum rate that is set on the RNC LMTThen, if Rmax is higher than the GBR, the downlink controllable mode set is {GBR in the RABassignment message, Rmax}. Otherwise, the downlink controllable mode set contains onlyone rate, that is {GBR in the RAB assignment message}.

• In the case of Iu UP version 1 and code-resource-saving algorithm enabled,– If the initial access rate is the GBR in the RAB assignment message, the downlink controllable

mode set contains only one rate, that is, {GBR in the RAB assignment message}.– If the initial access rate is higher than the GBR in the RAB assignment message, the downlink

controllable mode set is {GBR in the RAB assignment message, initial access rate}.Note: The DL code-resource-saving algorithm is available for the RNC. This algorithm allows a singlespeech service which has a DL maximum rate of 7.95 kbit/s or lower to use 256 as the Spreading Factor(SF) for the downlink. When the DL code-resource-saving algorithm is disabled, SF128 is used for thedownlink.

Database ParametersThe parameter to allow DL code-resource-saving is found in the command ADD CELLFRC and isdescribed below.AllowedSaveCodeResource — Value range: TRUE, FALSE.Physical unit: None.Content: This parameter specifies whether the DL code-resource-saving mode is applicable tonarrowband AMR services, TRUE specifies the DL code-resource-saving mode is applicable tonarrowband AMR services, FALSE specifies the DL code-resource-saving mode is not applicable. Incode-resource-saving mode, a relatively low puncturing limit is used during calculation of the downlinkspreading factor.Recommended value: FALSE.

5-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 303: SYS202m2 Usr7 Ver1 Rev2

Controllable Mode Set Version 1 Rev 2

Controllable Mode Set

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-9

USR7

Page 304: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 AMRC/AMRC-WB Algorithm Based on Uplink Stability

AMRC/AMRC-WB Algorithm Based on Uplink StabilityThe UL AMRC algorithm steers the UL permitted highest AMR speech codec mode up or down accordingto the UE transmit power.

UL Measurement and Event ReportingMeasurement results serve as the basis of AMRC/AMRC-WB. By comparing the measurement resultswith associated thresholds, the UE reports events. Then, the RNC takes associated AMRC/AMRC-WBactions.In the uplink, the measurement quantity is the transmit power of the UE.UL AMRC/AMRC-WB events consist of 6A1, 6A2, 6B1, 6B2 and 6D.

Events 6A1, 6A2, 6B1, and 6B2Events 6A1, 6B1, 6A2, and 6B2 have their respective thresholds. The thresholds 6A1, 6B1, 6A2, and6B2 in the diagram are specific for measurement events 6A1, 6B1, 6A2, and 6B2 respectively.The Delta_6a1, Delta_6b1, Delta_6a2, and Delta_6b2 in the diagram refer to the following relative valuesrespectively:

• The relative value between the TX power threshold 6A1 and the Max UL TX power ofconversational service.

• The relative value between the TX power threshold 6B1 and the Max UL TX power ofconversational service.

• The relative value between the TX power threshold 6A2 and the Max UL TX power ofconversational service.

• The relative value between the TX power threshold 6B2 and the Max UL TX power ofconversational service.

Therefore, Delta_6a1, Delta_6b1, Delta_6a2, and Delta_6b2 are relative measurement thresholds.A set of relative measurement thresholds for all AMR/AMR-WB services is as follows:

• Uplink 6A1 event relative threshold• Uplink 6B1 event relative threshold• Uplink 6A2 event relative threshold• Uplink 6B2 event relative threshold

The values of the preceding relative thresholds are configured by default and cannot be changed fromUSR7. The table with these defaults are listed below.

5-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 305: SYS202m2 Usr7 Ver1 Rev2

AMRC/AMRC-WB Algorithm Based on Uplink Stability Version 1 Rev 2

AMRC/AMRC-WB Algorithm Based on Uplink Stability

The measurement thresholds, that is, the absolute measurement thresholds, are calculated on the basisof the following formula:

• Measurement threshold 6A1 = Max UL TX power of conversational service – Uplink 6A1 eventrelative threshold

• Measurement threshold 6B1 = Max UL TX power of conversational service – Uplink 6B1 eventrelative threshold

• Measurement threshold 6A2 = Max UL TX power of conversational service – Uplink 6A2 eventrelative threshold

• Measurement threshold 6B2 = Max UL TX power of conversational service – Uplink 6B2 eventrelative threshold

Event 6DThe threshold of event 6D is the maximum UE Tx power.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-11

USR7

Page 306: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UL Event Reporting

UL Event ReportingAfter establishing an AMR speech service, the UTRAN sends the UE a MEASUREMENT CONTROLmessage to configure:

• The TX power threshold of 6A1, 6B1, 6A2, 6B2, and 6D.• The trigger time of 6A1, 6B1, 6A2, 6B2, and 6D.

For AMR/AMR-WB service, the trigger time of 6A1, 6B1, 6A2 and 6B2 is set to 320 ms, and the triggertime of 6D is set to 640 ms.Then, the UE measures the TX power in real time, filters the measurement results, and makes decisionsas follows:

• If the UE TX power has been higher than TX power threshold 6A1 for a period longer than320 ms and the TRIGGERED_6A1_EVENT variable is FALSE, event 6A1 is triggered and theTRIGGERED_6A1_EVENT variable is set to TRUE.

• If the TRIGGERED_6A1_EVENT variable is TRUE and the UE TX power is lower than TX powerthreshold 6A1, the TRIGGERED_6A1_EVENT variable is set to FALSE.

• If the UE TX power has been lower than TX power threshold 6B1 for a period longer than320 ms and the TRIGGERED_6B1_EVENT variable is FALSE, event 6B1 is triggered and theTRIGGERED_6B1_EVENT variable is set to TRUE.

• If the TRIGGERED_6B1_EVENT variable is TRUE and the UE TX power is higher than TX powerthreshold 6B1, the TRIGGERED_6B1_EVENT variable is set to FALSE.

• If the UE TX power has been lower than TX power threshold 6B2 for a period longer than320 ms and the TRIGGERED_6B2_EVENT variable is FALSE, event 6B2 is triggered and theTRIGGERED_6B2_EVENT variable is set to TRUE.

• If the TRIGGERED_6B2_EVENT variable is TRUE and the UE TX power is lower than TX powerthreshold 6A1, the TRIGGERED_6B2_EVENT variable is set to FALSE.

• If the UE TX power has been higher than TX power threshold 6A2 for a period longer than320 ms and the TRIGGERED_6A2_EVENT variable is FALSE, event 6A2 is triggered and theTRIGGERED_6A2_EVENT variable is set to TRUE.

• If the TRIGGERED_6A2_EVENT variable is TRUE and the UE TX power is lower thaTX powerthreshold 6A2, the TRIGGERED_6A2_EVENT variable is set to FALSE.

• If the UE Tx power equals the maximum UE TX power for 240 ms and the variableTRIGGERED_6D_EVENT is set to FALSE, event 6D is triggered and the variableTRIGGERED_6D_EVENT to TRUE.

• If the variable TRIGGERED_6D_EVENT is set to TRUE and if the UE Tx power is less than themaximum UE TX power, set the TRIGGERED_6D_EVENT is set to FALSE.

Each time an event is triggered the UE sends a measurement report to the UTRAN and the ULAMRC/WB-AMRC makes an adjustment.

5-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 307: SYS202m2 Usr7 Ver1 Rev2

UL Event Reporting Version 1 Rev 2

UL Event Reporting

320ms

320ms

320ms

320ms

Tx power threshold 6A1=[MaxUlTxPower] -[UlTh6a1]

Tx power threshold 6B1 =[MaxUlTxPower] -[UlTh6b1]

Tx power threshold 6A2 =[MaxUlTxPower] -[UlTh6a2]

Tx power threshold 6B2 =[MaxUlTxPower] -[UlTh6b2]

ReportingEvent 6A2

ReportingEvent 6B2

Reportingevent 6A1

ReportingEvent 6B1

UE Tx power

Time

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-13

USR7

dqfr38
Text Box
In USR7 these thresholds were fixed in the firmware, so no need to change them. check the subsequent table.
Page 308: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UL AMRC/AMRC-WB Action

UL AMRC/AMRC-WB ActionBased on the event reports from the UE, the UL AMRC/AMRC-WB algorithm takes associatedAMRC/AMRC-WB actions.

Principles of the UL AMRC/AMRC-WB AlgorithmThe principles of the UL AMRC/AMRC-WB algorithm are as follows:

• To steer the UL permitted highest AMR/AMR-WB speech codec mode up, the followingrequirements must be satisfied:– The UE TX power is below a certain threshold.– The UL load resource is not in congestion state.

• To steer the UL permitted highest AMR/AMR-WB speech codec mode down, the UE TX power mustbe higher than a certain threshold.

The UL AMRC/AMRC-WB algorithm steers the UL permitted highest AMR/AMR-WB speech codec modeup or down in the controllable mode set by only one level each time.

Details of the UL AMRC/AMRC-WB AlgorithmThe UL AMRC/AMRC-WB algorithm adjusts the UL permitted highest AMR/AMR-WB speech codecmode as follows:

• When an event 6A1 or 6D is received, the UL AMRC/AMRC-WB algorithm decreases theUL permitted highest AMR/AMR-WB speech codec mode by one level and starts the ULAMRC/AMRC-WB timer whose length is defined by Wait Timer for Uplink Rate Adjustmentof Traffic AMR. If the rate before the decrease is GBR or rate decrease fails, handover can beperformed (see Stability Control section).– If the event 6B1 or 6B2 is received before the UL AMRC/AMRC-WB timer expires,

the adjustment is completed. Then, the UL AMRC/AMRC-WB algorithm stops the ULAMRC/AMRC-WB timer and ends the adjustment.

– If no event 6B1 or 6B2 is received before the UL AMRC/AMRC-WB timer expires and if thecurrent rate is higher than GBR, the adjustment is not complete. The UL AMRC/ AMRC-WBalgorithm decreases the UL permitted highest AMR/AMR-WB speech codec mode by one morelevel and restarts the UL AMRC/AMRC-WB timer. If the rate before the decrease is GBR,handover can be performed.

• When an event 6B2 is received and UL load resource is not in congestion state, the ULAMRC/AMRC-WB algorithm increases the UL permitted highest AMR/AMR-WB speech codecmode by one level and starts the UL AMRC/AMRC-WB timer whose length is defined by WaitTimer for Uplink Rate Adjustment of Traffic AMR. If the rate before the increase is the maximumone in the controllable mode set, no increase will be performed, and the UL AMRC/AMRC-WBtimer does not start.– If the event 6A2 or 6A1 is received before the UL AMRC/AMRC-WB timer expires,

the adjustment is completed. Then, the UL AMRC/AMRC-WB algorithm stops the ULAMRC/AMRC-WB timer and ends the adjustment.

– If no event 6A2 or 6A1 is received before the UL AMRC/AMRC-WB timer expires and ifUL load resource is still not in congestion state, the adjustment is not complete. The ULAMRC/AMRC-WB algorithm increases the UL permitted highest AMR/AMR-WB speech codecmode by one more level and restarts the UL AMRC/AMRC-WB timer. If the rate before theincrease is the maximum one in the controllable mode set, no increase will be performed, andthe UL AMRC/AMRC-WB timer does not restart.

Database ParametersThe parameter enables AMR adjustment and that sets the Wait Timer for Uplink Rate Adjustment ofTraffic AMR is found in the command SET QOSACT and is described below.(W)AmrUlRateAdjTimerLen — Value range: 20~64000Physical unit: msContent: timer for triggering a second adjustment of the UL AMR mode. This parameter specifies theduration of waiting for the voice quality enhanced acknowledgement after the UL AMR mode adjustmentwhen the associated command is delivered. The UL AMRC timer starts when AMRC mode adjustmentprocedure is triggered, and stops when the next measurement report is received. If no measurementreport is received when the UL AMRC timer expires, you can infer that the measured value remains in

5-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 309: SYS202m2 Usr7 Ver1 Rev2

UL AMRC/AMRC-WB Action Version 1 Rev 2

UL AMRC/AMRC-WB Actionthe same state as that before the previous UL AMRC mode adjustment. The previous AMRC modeadjustment is not effective, and another adjustment is required. The longer the UL AMRC timer is, theless frequently the AMRC mode is adjusted. In addition, the response to measurement reports becomesslower accordingly.Recommended value: 3000

ULAMRCTIMERLEN

Timer stopped when 6b1 rx’d. If 6b1 is not rx’dbefore timer expires then reduce to the next AMR mode and restart timer – same principle applies to

6b2

320ms

320ms

320ms

320ms

Tx power threshold 6A1=[MaxUlTxPower] -[UlTh6a1]

Tx power threshold 6B1 =[MaxUlTxPower] -[UlTh6b1]

Tx power threshold 6A2 =[MaxUlTxPower] -[UlTh6a2]

Tx power threshold 6B2 =[MaxUlTxPower] -[UlTh6b2]

ReportingEvent 6A2

ReportingEvent 6B2

Reportingevent 6A1

ReportingEvent 6B1

UE Tx power

Time

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-15

USR7

Page 310: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UL AMRC Signalling Procedure

UL AMRC Signalling ProcedureAs shown in the slide opposite UL AMRC algorithm sets the measurement thresholds for events 6A1,6B1, 6A2, and 6B2 by sending a MEASURMENT CONTROL message. The UE then reports events 6A1,6B1, 6A2, and 6B2 by sending a MEASUREMENT REPORT message if needed. The RNC adjusts thepermitted UL highest codec mode by sending a TFC CONTROL message, and adjusts the UL bandwidthby sending an AAL2 MODIFY message.

5-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 311: SYS202m2 Usr7 Ver1 Rev2

UL AMRC Signalling Procedure Version 1 Rev 2

UL AMRC Signalling Procedure

UERNC

NodeB

Measurement Control (6A1, 6A2, 6B1 and 6B2 parameters)

Measurement Report (6A1, 6A2, 6B1 and 6B2 events reports)

TFC Control (Adjusts the highest permitted UL AMR Codec)

QAAL Modify (Adjusts UL Bandwidth on IuB)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-17

USR7

Page 312: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 AMRC/AMRC-WB Algorithm Based on Downlink Stability

AMRC/AMRC-WB Algorithm Based on Downlink StabilityThe DL AMRC algorithm steers the DL permitted highest AMR speech codec mode up or down accordingto the DPDCH transmit power.

DL Events and ThresholdsDL AMRC/AMRC-WB events consist of E1, E2, F1, and F2.The thresholds E1, E2, F1, and F2 in the diagram are specific for measurement events E1, E2, F1, andF2 respectively:

• For event E1, the average TX power on the DPDCH is higher than the TX power threshold E1.• For event E2, the average TX power on the DPDCH is higher than the TX power threshold E2.• For event F1, the average TX power on the DPDCH is higher than the TX power threshold F1.• For event F1, the average TX power on the DPDCH is higher than the TX power threshold F2.

The Delta_E1, Delta_E2, Delta_F1, and Delta_F2 in the diagram refer to the following relative valuesrespectively:

• The relative value between the TX power threshold E1 and the RL Max DL TX power• The relative value between the TX power threshold E2 and the RL Max DL TX power• The relative value between the TX power threshold F1 and the RL Max DL TX power• The relative value between the TX power threshold F2 and the RL Max DL TX power

Therefore, Delta_E1, Delta_E2, Delta_F1, and Delta_F2 are relative measurement thresholds.A set of relative measurement thresholds for all AMR/AMR-WB services are configured. The set includesthe following parameters:

• DL E1 event relative threshold• DL E2 event relative threshold• DL F1 event relative threshold• DL F2event relative threshold

The measurement thresholds, that is, the absolute measurement thresholds, are calculated on the basisof the following formula:

• Measurement threshold E1 = RL Max DL TX power – DL E1 event relative threshold• Measurement threshold E2 = RL Max DL TX power – DL E2 event relative threshold• Measurement threshold F1 = RL Max DL TX power – DL F1 event relative threshold• Measurement threshold F2= RL Max DL TX power – DL F2 event relative threshold

Note: The change of codec works in the same way as the UL AMRC so is not repeated..

Database ParametersThe command to set the RL Max DL TX power are found in the command ADD CELLRLPWR and isdescribed below.RlMaxDlPwr — Value range: -350~150Physical value range: -35~15, step: 0.1Physical unit: dBContent: This parameter should fulfill the coverage requirement of the network planning, and the valueis relative to [PCPICH transmit power]. If the parameter is excessively high, downlink interference mayoccur. If the parameter is excessively low, the downlink power control may be affected. For detailedinformation of this parameter, refer to 3GPP TS 25.433.Recommended value: noneThe following parameters to set the event thresholds are found in the SET AMRC command.DLTHDE1Value range: 0~559.Physical range and unit: 0–55.9, step 0.1 (dB).The threshold E1 of DL AMR mode adjustment. For DL measurement, the periodical reporting modeis used. When the measured value is higher than the upper threshold E1, AMRC will decrease the DLAMR mode by one level. What defined by this parameter is a relative threshold. The absolute threshold= [MaxDlTxPower] - [DlThE1]. The greater this parameter is, the lower the absolute threshold. In thiscase, there are greater possibilities of satisfying the request for AMR mode decrease. Accordingly theAMR speech mode is more likely to be decreased. Recommended value: 50. Recommended value: 2.

5-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 313: SYS202m2 Usr7 Ver1 Rev2

AMRC/AMRC-WB Algorithm Based on Downlink Stability Version 1 Rev 2

AMRC/AMRC-WB Algorithm Based on Downlink StabilityDLTHDE2See LMT.ULTHDF1See LMTULTHDF2See LMT

E1 =[RlMaxDlPwr] - [DlThE1]

E2 =[RlMaxDlPwr] - [DlThE2]

F2 =[RlMaxDlPwr] - [DlThF2]

F1 =[RlMaxDlPwr] - [DlThF1]

DL DPDCH TX Power

Time

Reduce DL AMR mode

Increase DL AMR mode

Reportingevent 6E1

Reportingevent 6E2

Reportingevent 6F1

Reportingevent 6F2

RlMaxDlPwr

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-19

USR7

dqfr38
Text Box
For NB
Page 314: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 DL AMRC Signalling Procedure

DL AMRC Signalling ProcedureAs shown in the diagram opposite, the AMRC algorithm sets the periodic measurement report bysending a DEDICATED MEASUREMENT INITIATION REQUEST message. The NodeB reports themeasurement results by sending a DEDICATED MEASUREMENT REPORT message. The RNC willadjust if necessary the DL rate by sending an IUUP RATE CONTROL message, and adjusts the DLbandwidth by sending an AAL2 MODIFY message.

5-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 315: SYS202m2 Usr7 Ver1 Rev2

DL AMRC Signalling Procedure Version 1 Rev 2

DL AMRC Signalling Procedure

NodeB CNRNCDedicated Measurement Initiation Request (Periodic measurements)

Dedicated Measurement Initiation Response

Dedicated Measurement Report

IUuP Rate Control Request (DL Rate adust request)

IUuP Rate Control Response

QAAL2 Modify (IuB Bandwidth adj)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-21

USR7

Page 316: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Adaptive Multi Rate Control — Wide Band (AMRC-WB)

Adaptive Multi Rate Control — Wide Band (AMRC-WB)AMRC-WB is introduced to provide a better quality of service suitable for video phone and conferencecall services. It uses a sampling rate of 16khz rather than the 8khz used for narrow band AMR andproduces speech quality similar to face-to-face talk.

AMRC-WB Frame StructureThe bit rates available for AMRC-WB are shown on the slide opposite.The control mechanism is exactly the same as for AMRC-NB and so there is no need to repeat them.The command used change the control parameters is SET AMRCWB.

5-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 317: SYS202m2 Usr7 Ver1 Rev2

Adaptive Multi Rate Control — Wide Band (AMRC-WB) Version 1 Rev 2

Adaptive Multi Rate Control — Wide Band (AMRC-WB)

04057247723.8510

03897246123.059

03257239719.858

02937236518.257

02457231715.856

02137228514.255

01817225312.654

0113641778.853

078541326.602

004040SID1

0000No data0

Class CClass BClass ATotal number of bits

AMR-WBcodec mode

Frame Type

04057247723.8510

03897246123.059

03257239719.858

02937236518.257

02457231715.856

02137228514.255

01817225312.654

0113641778.853

078541326.602

004040SID1

0000No data0

Class CClass BClass ATotal number of bits

AMR-WBcodec mode

Frame Type

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-23

USR7

Page 318: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Dynamic Channel Configuration Control (DCCC)

Dynamic Channel Configuration Control (DCCC)

Algorithm OverviewDynamic Channel Configuration Control (DCCC) includes the following two parts.

Rate Re-allocationUpsize and downsize the data rate of the Best Effort (BE) services, (i.e. interactive and background) inthe CELL_DCH RRC state.Dynamically adjust the uplink and downlink bandwidth of the Dedicated Channel (DCH) according tothe traffic volume which reflects the state of data transmission.Dynamically adjust the bandwidth of the Dedicated Channel (DCH) according to the quality of radio linkdue to coverage.Dynamically adjust the bandwidth of the Dedicated Channel (DCH) according to the load congestion.This part of the algorithm works in conjunction with the load control mechanism.

UE State TransitionSwitch the UE state to the CELL_FACH and CELL_PCH/URA_PCH state when the UE inactivity isdetected, and back to CELL_DCH state when the UE activity is detected because there is data to betransmitted.

MeasurementsThe traffic volume measurement executed by UEs are used in the uplink bandwidth re-allocation processand the UE state transition to improve the resource utilization.The downlink Transmitted Code Power (TCP) measurements executed by NodeBs are used in thedownlink rate re-allocation to keep the link stability.The Traffic Volume Measurements (TVMs) executed by RNC are used in the downlink bandwidthre-allocation process and the UE state transition to improve the resource utilization.

PurposeThe DCCC is to improve the performance of the network resource utilization and to keep the link stability.This is done in three keys ways as listed below:

• In the downlink and uplink, the DCCC re-allocates the bandwidth based on the traffic volumemeasurement. In this way, the DCCC algorithm makes efficient use of the resource such as theOVSF code resources, the Channel Element (CE) resources of the NodeB and the transmissionresources on the Iub and the Iur interfaces.

• In the downlink, the DCCC downgrades the data rate if the link quality deteriorates, in order toprevent the call drop.

• The state of the UE can transit from CELL_DCH to CELL_FACH, or from CELL_FACH toCELL_PCH/URA_PCH. In the state of CELL_FACH or the CELL_PCH/URA_PCH, the resourcesof the network and the UE battery can be saved.

Database ParametersThe database parameter that enables DCCC is found in the command SET CORRMALGOSWITCH andis described below.DCCC_SWITCH: When the switch is selected, the dynamic channel reconfiguration control algorithm isused for the RNC.Warning: This DCCC switch should only be switch to off for testing. In the commercial network it shouldalways be enabled.

5-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 319: SYS202m2 Usr7 Ver1 Rev2

Dynamic Channel Configuration Control (DCCC) Version 1 Rev 2

Dynamic Channel Configuration Control (DCCC)

Rate Re-allocation

• Control of BE services

• Adjust DCH rate based on data throughput

• Adjust DCH rate based on link quality

• Adjust DCH rate based on congestion

UE State Transition

Switch the UE state based on activity

UL TVM taken in

UE

RNC

NodeB

DL TCP Taken in NodeB

DL TVM taken in the

RNC

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-25

USR7

Page 320: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Rate Re-allocation Algorithm

Rate Re-allocation AlgorithmThe rate re-allocation algorithm has three features, one is based on the traffic volume, one is based onthe downlink quality, and the other has a relation with load congestion.

Traffic Volume Triggering MechanismIn the uplink, the UE measures DTCH, (that is, buffer occupancy of RLC entities), to obtain the uplinktraffic volume.In the downlink, the RNC measures the DTCH, (that is, buffer occupancy of RLC entities), to obtain thedownlink traffic volume.Note: The traffic volume measurements defined in 3GPP TS 25.331 are applicable only to the uplink.Regarding the downlink traffic volume measurements and associated rate reallocation, the design andimplementation are Motorola specific.

Event 4a and Event 4bTraffic volume threshold of event 4a is defined by the traffic measurement event 4A threshold.When the current traffic rate is 0 kbit/s, the traffic measurement event 4A threshold is set to 16 byte;when the current traffic rate is not 0kbit/s, the traffic measurement event 4A threshold is set to 1024 byte.Traffic volume threshold of event 4b is defined by the traffic measurement event 4B threshold.When the current traffic rate is below 128 kbit/s, the traffic measurement event 4B threshold is set to 128byte; when the current traffic rate is above 128 kbit/s, the traffic measurement event 4B threshold is setto 256 byte.Traffic volume measurement triggering can be associated with both the time-to-trigger (time to trigger4A which is set to 240ms and time to trigger 4B — In uplink, the time to trigger 4B is 30s. In downlink,the time to trigger 4B is 5000ms) and the pending after trigger (pending_time_after trigger_4a andpending_time_after_trigger_4b, that are set to 4,000 ms). For the definitions of time-to-trigger andpending time after trigger, refer to section 14.4.3 "Traffic volume reporting mechanisms" in 3GPP TS25.331.Time-to-trigger is used to get time domain hysteresis, that is, the condition must be fulfilled during thetime-to-trigger period before a report is sent.Pending time after trigger is used to limit consecutive reports when one traffic volume measurementreport has already been sent.

UplinkIn the uplink:

• When the traffic volume is higher than the value of Traffic Measurement Event 4A threshold for aperiod of time defined by Time to trigger 4A, the UE reports an event 4a. No more events 4a arereported during the time defined by Pending time after trigger 4A.

• When the traffic volume is lower than the value of Traffic Measurement Event 4B threshold for aperiod of time defined by Time to trigger 4B, the UE reports an event 4b. No more events 4b arereported during the time defined by Pending time after trigger 4B.

DownlinkIn the downlink:

• When the traffic volume is higher than the value of Traffic Measurement Event 4A threshold for aperiod of time defined by Time to trigger 4A, the RNC reports internally an event 4a. No moreevents 4a are reported during the time defined by Pending time after trigger 4A.

• When the traffic volume is lower than the value of Traffic Measurement Event 4B threshold for aperiod of time defined by Time to trigger 4B, the RNC reports internally an event 4b. No moreevents 4b are reported during the time defined by Pending time after trigger 4B.

5-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 321: SYS202m2 Usr7 Ver1 Rev2

Rate Re-allocation Algorithm Version 1 Rev 2

Rate Re-allocation Algorithm

T ime

P ayload

E vent4AT hd

T imetoT rigger4A

R eporting 4A

P endingT ime4A

R eporting 4A

T imetoT rigger4AT imetoT rigger4A

P endingT ime4A

E vent4B T hd

T imetoT rigger4B

P endingT ime4B

R eporting 4B

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-27

USR7

Page 322: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink Rate Re-allocation Based on The Traffic Volume

Uplink Rate Re-allocation Based on The Traffic VolumeThe decision to re-allocate rate is made based on traffic volume, monitoring uplink direction on the logicalDTCH channel. The monitored traffic volume corresponds to the data which are actually sent over theradio interface. Therefore, this includes both user-PDUs (as they are submitted by higher layers to radioprotocols PDCP/RLC/MAC) and repeated RLC-frames.In the Motorola implementation, two strategies are provided: one is RATE_UP_AND_DOWN_ON_DCHstrategy and the other is RATE_UP_ONLY_ON_DCH strategy.The RATE_UP_AND_DOWN_ON_DCH strategy means that the rate can be both downsized andupsized. The RATE_UP_ONLY_ON_DCH strategy means that the rate can only be upsized. Thestrategy is selected through the parameter DCCC STRATEGY. If the system resources in thenetwork are limited, it is suggested selecting RATE_UP_AND_DOWN_ON_DCH strategy; whereas,RATE_UP_ONLY_ON_DCH is selected because there are the enough network resources.The principle of RATE_UP_AND_DOWN_ON_DCH strategy is that:

• Downsizing is performed if the RNC receives an uplink traffic volume event report 4b.• Upsizing is performed if RNC receives uplink traffic volume event report 4a.• The lowest rate which can be downsized to is the UPLINK BITRATE THRESHOLD FOR DCCC,

the highest rate which can be upsized to is MIN{the request maximum bit rate assigned by CN, themaximum rate supported by UE capabilities}.Note: in the following, we call the MIN {the request maximum bit rate assigned by CN, the maximumrate supported by UE capabilities} the highest rate.

• If the UPLINK RATE ADJUST LEVEL is set to 2_Rates, the data rate will be downsized directly tothe UPLINK BITRATE THRESHOLD FOR DCCC, or the rate will be upsized directly to the highestfrom the UPLINK BITRATE THRESHOLD FOR DCCC.

• If the UPLINK RATE ADJUST LEVEL is set to 3_Rates, the rate will be downsized to the UPLINKMID BITRATE THRESHOLD if the current rate is the highest, and will be downsized again toUPLINK BITRATE THRESHOLD FOR DCCC. In the process of upsize, the data rate will beupsized to the UPLINK MID BITRATE THRESHOLD if the current rate is the UPLINK BITRATETHRESHOLD FOR DCCC, and will be upsized again to the highest.

The principle of RATE_UP_ONLY_ON_DCH strategy is that:

• Downsizing is prohibited. If the UE is in low activity, the state of UE will be directly switched toCELL_FACH.

• Upsizing is performed if RNC receives uplink traffic volume event report 4a.• The highest rate which can be upsized to is MIN {the request maximum bit rate assigned by CN,

the maximum rate supported by UE capabilities}.• If the UPLINK RATE ADJUST LEVEL is set to 2_Rates, the rate will be upsized directly to the

highest from the UPLINK BITRATE THRESHOLD FOR DCCC.• If the UPLINK RATE ADJUST LEVEL is set to 3_Rates, the rate will be upsized to the UPLINK MID

BITRATE THRESHOLD if the current rate is the UPLINK BITRATE THRESHOLD FOR DCCC, andwill be upsized again to the highest.

Associated ParametersThe parameters associated with the TVM triggering mechanism are found in the SET DCCC databasecommand and are listed below.DCCCSTG — Value range: RATE_UP_AND_DOWN_ON_DCH, RATE_UP_ONLY_ON_DCH.Physical value range: 0, 1.Physical unit: None.Content: The rate of PS BE services adjustment strategy in CELL_DCH state.RATE_UP_AND_DOWN_ON_DCH strategy permits rates to go up and rate to godown. RATE_UP_ONLY_ON_DCH strategy just permits rate to go up. This means UEcan transit from CELL_DCH to CELL_FACH state at any rate. Recommended value:RATE_UP_AND_DOWN_ON_DCH.ULDCCCRATETHD — Value range: D8, D16, D32, D64, D128, D144, D256, D384.Physical value range: 8, 16, 32, 64, 128, 144, 256, 384.Physical unit: kbit/s.Content: The DCCC algorithm capability may be non-effective for some Best Effort (BE) services withvery low applied maximum rate. The UL DCCC algorithm does not activate for the BE service whoseapplied uplink maximum rate is smaller than or equal to the threshold. Recommended value: D64.

5-28 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 323: SYS202m2 Usr7 Ver1 Rev2

Uplink Rate Re-allocation Based on The Traffic Volume Version 1 Rev 2

Uplink Rate Re-allocation Based on The Traffic VolumeULRATEADJLEVEL — Value range: 2_Rates,3_RatesPhysical value range: 1, 2.Physical unit: None.Content: The parameter is used to judge uplink 2 rates or 3 rates adjusting. Recommended value:2_Rates.ULMIDRATECALC — Value range: AUTO_CALC,HAND_APPOINTPhysical value range: 0, 1.Physical unit: None.Content: The parameter is used to decide the uplink middle bit rate calculation method when using 3rates adjusting.Recommended value: AUTO_CALC.ULMIDRATETHD — Value range: D16, D32, D64, D128, D144, D256, D384.Physical value range: 16, 32, 64, 128, 144, 256, 384.Physical unit: kbit/s.Content: Uplink middle rate threshold when use 3 rate adjusting and middle rate caculate method isHAND_APPOINT.Recommended value: None.

UL TVM taken in

UE

RNC

NodeB

4b – Downsize

4a - Upsize

Highest Rate - min(requested bit rate assigned by CN, max bit rate supported by UE)

Lowest Rate – Set by ULDCCCRATETHD

The strategy and rate the UE will be adjusted to is determined by DCCCSTG, ULRATEADJLEVEL, ULMIDRATECALC and possibly ULMIDRATETHD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-29

USR7

Page 324: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 DL Rate-allocation Based on The Traffic Volume

DL Rate-allocation Based on The Traffic VolumeThe downlink rate-allocation based on TVM is based on the uplink version and re-uses 4a and4b thresholds and timers. The strategy used by the downlink is identical to the uplink so only theparameters are listed together with a slide to discuss the concepts.The parameters that effect the DL rate-allocation TVM algorithm are found in the SET DCCC commandand are listed below.

Database ParametersThe parameters associated with the TVM triggering mechanism are found in the SET DCCC databasecommand and are listed below.DLDCCCRATETHD — Value range: D8, D16, D32, D64, D128, D144, D256, D384.Physical value range: 8, 16, 32, 64, 128, 144, 256, 384.Physical unit: kbit/s.Content: The DCCC algorithm capability may be very low for some Best Effort (BE) service with verylow applied maximum rate. The DL DCCC algorithm does not activate for the BE service whose applieddownlink maximum rate is smaller than or equal to the threshold.Recommended value: D32.DLRATEADJLEVEL — Value range: 2_Rates,3_RatesPhysical value range: 1, 2.Physical unit: None.Content: The parameter is used to judge downlink 2 rates or 3 rates adjusting.Recommended value: 2_Rates.DLMIDRATECALC — Value range: AUTO_CALC,HAND_APPOINTPhysical value range: 0, 1.Physical unit: None.Content: The parameter is used to decide the downlink middle bit rate calculate method when 3 ratesadjusting. Recommended value: AUTO_CALC.DLMIDRATETHD — Value range: D16, D32, D64, D128, D144, D256, D384.Physical value range: 16, 32, 64, 128, 144, 256, 384.Physical unit: kbit/s.Content: Downlink middle rate threshold when use 3 rate adjusting and middle rate calculate method isHAND_APPOINT.Recommended value: None.

5-30 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 325: SYS202m2 Usr7 Ver1 Rev2

DL Rate-allocation Based on The Traffic Volume Version 1 Rev 2

DL Rate-allocation Based on The Traffic Volume

DL TVM taken in UTRAN

RNC

NodeB

4a – Downsize

4b - Upsize

Highest Rate - min(requested bit rate assigned by CN, max bit rate supported by UE)

Lowest Rate – Set by DLDCCCRATETHD

The strategy and rate the UTRAN will be adjusted to is determined by DCCCSTG, DLRATEADJLEVEL, DLMIDRATECALC and possibly DLMIDRATETHD

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-31

USR7

Page 326: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Rate Reallocation Based on Throughput

Rate Reallocation Based on ThroughputThis section describes how the DCCC of BE services are implemented through rate reallocation basedon the throughput.

Throughput Measurement and Event ReportingE-DCH and DCH BE services rate reallocation is based on the throughput measurement results. Aftercomparing the measurement results with associated thresholds, the RNC can trigger rate reallocation.

Throughput MeasurementIn each measurement period, the MAC-d takes statistics of the data volume properly received by thisRB. The result is then divided by the measurement period to obtain the throughput value.Note:

• For E-DCH service, the throughput measurement period is specified by the E-DCH Throu MeasPeriod parameter.

• For DCH service, the throughput measurement period is set to 1,000 ms.

Event 4a and Event 4bNotes:

• For throughput-based rate reallocation on the E-DCH, both events 4a and 4b apply, that is, bothrate upsizing and downsizing are applicable for uplink.

• For throughput-based rate reallocation on the DCH, only event 4b applies, that is, only ratedownsizing is applicable.

The diagram illustrates the mechanism of throughput measurement and reporting of events 4a and 4b.In this example, the time to trigger for 4a/4b is three consecutive measurement periods, and the pendingtime after trigger for 4a/4b is four consecutive measurement periods.Note: In RAN10.0, the time to trigger for 4a/4b is set to two consecutive measurement periods; thepending time after trigger for 4a/4b is set to sixteen consecutive measurement periods.The mechanism of reporting throughput-related events 4a and 4b is as follows:

• A specified group of adjustment rates and the associated throughput thresholds has to beconfigured:– {(R1, TR1), ... (Ri, TRi), ... (RN, TRN)}

Where:

• For E-DCH services,– The first figure in each pair of parentheses is the HSUPA adjustment rate which is set through

the HSUPA UpLink rate adjust set parameter.– The second figure is the associated throughput threshold of this HSUPA adjustment rate.

TRi = Ri x threshold rate ratio (between 70 to 90% depending on rate).– The RN is the highest rate in the set defined by the HSUPA UpLink rate adjust set parameter.

• For DCH services, the rate adjustment set is {rate threshold for DCCC, middle rate, maximum rate}permanently.– The rate threshold for DCCC is defined by the Uplink/Downlink bit rate threshold for DCCC

parameter.– The middle rate is defined by the Uplink/Downlink mid bit rate calculate method and

Uplink/Downlink mid bit rate threshold parameters.– The maximum rate is the MBR.

During each measurement period, throughput measurement on this RB is performed to obtain thethroughput of this period, defined as AvgThroughput.If the AvgThroughput is higher than the 4a threshold for two consecutive measurement periods and theTpend_4a timer, which is set to sixteen consecutive measurement periods after event 4a is triggered,is not started, event 4a is reported and the Tpend_4a timer is started.If the AvgThroughput is lower than the 4b threshold for two consecutive measurement periods and theTpend_4b timer, which is set to sixteen consecutive measurement periods after event 4b is triggered,is not started, event 4b is reported and the Tpend_4b timer is started.

5-32 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 327: SYS202m2 Usr7 Ver1 Rev2

Rate Reallocation Based on Throughput Version 1 Rev 2

Rate Reallocation Based on ThroughputDatabase ParametersTo enable rate reallocation based on throughput for DCH, set the THROU_DCCC_SWITCH of ChannelClass Algorithm Switch parameter to ON through the SET CORRMALGOSWITCH command.To enable rate reallocation based on throughput for HSUPA, set the HSUPA_DCCC_SWITCH of HspaAlgorithm Switch parameter to ON through the SET CORRMALGOSWITCH command.The parameter to set the E-DCH Throu Meas Period is found in the command SET UESTATETRANS.E2FThrouMeasPeriod — Period of E-DCH throughput ratio measurementValue range: 1~10000; step: 10Physical value range: 10~100000Physical unit: msContent: This parameter specifies the period of E-DCH throughput ratio measurement. The throughputratio over the E-DCH is periodically measured to implement state transition from E-DCH to FACH.Recommended value (default value): 30The parameter to set the HSUPA UpLink rate adjust set is found in the command SETEDCHRATEADJUSTSET and is described below.EdchRateAdjustSet — Rates — Rate_8Kbps Rate_16Kbps Rate_32Kbps Rate_64KbpsRate_128Kbps Rate_144Kbps Rate_256Kbps Rate_384Kbps Rate_608Kbps Rate_1450KbpsRate_2048Kbps Rate_2890Kbps Rate_5760KbpsThe actions taken for HSUPA are set in the command SET DCCC and are listed below.HsupaDcccStg — Value range: RATE_UP_AND_DOWN_ON_EDCH, RATE_UP_ONLY_ON_EDCH.Physical value range: 0, 1Physical unit: noneContent: strategy of the UE for rate adjustment over the EDCH. RATE_UP_AND_DOWN_ON_EDCHindicates that the rate over the EDCH can be raised or lowered. RATE_UP_ONLY_ON_EDCH indicatesthat the rate over the EDCH can only be raised, which means that the UE can switch to the FACH stateat any rate.Recommended value: RATE_UP_AND_DOWN_ON_EDCHNote: For DCH only rate downsizing is supported.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-33

USR7

Page 328: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Rate Reallocation Based on Link Quality

Rate Reallocation Based on Link QualityThis section describes how to make rate reallocation for BE services according to the link quality.

Uplink Quality MeasurementThere are two measurement quantities related to the uplink quality, uplink transmit power of the UE anduplink BLER.

• The measurements of uplink transmit power through Uu interface from UE. When the uplink transmitpower reaches the maximum power, it indicates that the radio link may be unstable.

• The measurement of uplink BLER can be implemented in RNC. When uplink BLER is high, it alsoindicates that the radio link may be unstable.

Event 6A and 6BIn the uplink, the measurement of UE transmit power can trigger event 6A or event 6B.#

• If the transmit power of the UE is above a certain threshold for a period of time, event 6A is triggered.Event 6A involves two thresholds: 6A1 and 6A2.

• If the transmit power of the UE is below a certain threshold for a period of time, event 6B is triggered.Event 6B involves two thresholds: 6B1 and 6B2.

The parameters related to events 6A and 6B are as follows:

• Be trigger time 6A1• Be trigger time 6A2• Be trigger time 6B1• Be trigger time 6B2

Event 6DIf the transmit power of the UE is equal to the maximum transmit power of the UE for a period of time (thetime is defined by the hysteresis), the UE reports event 6D. For BE services, the hysteresis is specifiedby the Be trigger time 6D parameter.

Event 5AThe uplink BLER reflects the uplink quality. The change in the BLER is indicated by event 5A.The RNC defines a sliding window of a certain length. If the number of error blocks during the slidingwindow is greater than or equal to a predefined number, event 5A is triggered.For a specific service parameter index, set the following parameters related to event 5A:

• Statistic Block Number for 5A Event: the length of the sliding window in which the number of errorblocks is counted (500 by default)

• Event 5A Threshold: the number of error blocks in a sliding window, which determines whether totrigger an event 5A or not (280 by default)

• Interval Block Number: After an event 5A is triggered, no more event 5A is triggered before anumber of blocks (the number is defined by this parameter) are received (512 by default).

Each time a block is received, the number of error blocks within the sliding window is compared with theEvent 5A Threshold parameter. If the number of error blocks is equal to or greater than the value of theparameter, an event 5A is triggered. When event 5A is triggered, a pending counter is started to preventfurther triggering of the event before a certain number of transport blocks which is specified by IntervalBlock Number are received.The whole process is based on the sliding window mechanism. This window slides with the arrival ofeach block. Each time a block is received, the decision on whether to trigger event 5A is made. Thenumber of error blocks is still counted when the pending timer after trigger timer works. However, noevent 5A is triggered even if the triggering conditions are met.

Database ParametersThe database parameters associated with uplink quality measurement are found in the command SETQUALITYMEAS and are described below.

5-34 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 329: SYS202m2 Usr7 Ver1 Rev2

Rate Reallocation Based on Link Quality Version 1 Rev 2

Rate Reallocation Based on Link QualityUlBeTrigTime6A — Value range: D0 to D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000Physical unit: msContent: duration when the measured value of Be keeps fulfilling the 6a1 measurement condition beforethe event 6a1 is triggered.Recommended value: D640UlBeTrigTime6B1 — Value range: D0 to D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000Physical unit: msContent: duration when the measured value of Be keeps fulfilling the 6b1 measurement condition beforethe event 6b1 is triggered.Recommended value: D2560UlBeTrigTime6A2 — Value range: D0 to D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000Physical unit: msContent: duration when the measured value of Be keeps fulfilling the 6a2 measurement condition beforethe event 6a2 is triggered.Recommended value: D1280UlBeTrigTime6B2 — Value range: D0 to D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000Physical unit: msContent: duration when the measured value of Be keeps fulfilling the 6b2 measurement condition beforethe event 6b2 is triggered.Recommended value: D1280UlBeTrigTime6D — Value range: D0 to D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000Physical unit: msContent: duration when the measured value of Be keeps fulfilling the 6d measurement condition beforethe event 6d is triggered.Recommended value: D240

• Event 6A and 6B – Relative power thresholds for a time

• Event 6D – Maximum power of UE for a time

• Event 5A – BLER reflecting UL quality

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-35

USR7

Page 330: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Quality Measurement and Event Reporting

Downlink Quality Measurement and Event ReportingThis section describes the downlink quality evaluation factors and corresponding events.

Downlink Quality MeasurementThere are two measurement quantities related to the downlink quality, Transmitted Code Power (TCP),and RLC PDU retransmission rate.

• The measurement of TCP is implemented on the NodeB side. When the transmit power of theDPDCH is higher than the threshold of event Ea, it indicates that the radio link may be unstable.

• The RLC PDU retransmission rate is optional. It is controlled by the Srnc Downlink RLC QOSAction Trigger Indicator of Traffic BE parameter.

Event EEvent E has two measurement thresholds, that is, threshold 1, and threshold 2.

• Event Ea means that the transmit power rises higher than measurement threshold 1.• Event Eb means that the transmit power falls below measurement threshold 2.

For different services, there are different Ea and Eb thresholds. For sake of the simplicity of parameters,we configure a set of comparative thresholds for all BE services and absolute Ea and Eb thresholds arecalculated by the following formula:Absolute threshold = maximum DL Power — comparative threshold + PO3Where:PO3 is the relative transmit power offset between pilot fields of the DPCCH and DPDCHs, maximum DLpower is configured by RLMAXDLPWR which configures the power of the DPDCHs. When the transmitpower of the pilot fields of the DPCCH stays above the measurement threshold 1 for a period longerthan T1 (EVENT E HYSTERESIS TIME), the event Ea is triggered. The NodeB periodically reports themeasurement results of the transmit power to the RNC. When the transmit power of the pilot fields of theDPCCH stays below the measurement threshold 2 for a period longer than T1 (EVENT E HYSTERESISTIME), the event Eb is triggered. The NodeB stops reporting the measurement results of the transmitpower. Before Event E measurement event evaluation and reporting, DL code TX power measurementfilter coefficient will be used.Note: Both Event Ea relative threshold and Event Eb relative threshold are set to 1dB.When the transmit power of the pilot fields of the DPCCH remains above the measurement threshold1 for a time period longer than T1 (Be trigger time of Event E), event Ea is triggered. The NodeBperiodically reports the measurement results of the transmit power to the RNC.When the transmit power of the pilot fields of the DPCCH remains below the measurement threshold 2for a time period longer than T1 (the trigger time of event E which is set to 640 ms for BE service), eventEb is triggered. The NodeB stops reporting the measurement results of the transmit power.Before event E measurement event evaluation and reporting, DL TCP Measurement Filter Coefficient isused to perform higher layer filtering.

Database ParametersThe parameter to set the Event E trigger time is SET QUALITYMEAS and is described below.DlBeTrigTimeE — Value range: 1~6000Physical value range: 10~60000, step: 10Physical unit: msContent: duration from when the Be TX power is beyond the threshold Ea or below the threshold Eb towhen the event Ea or Eb is triggered. This parameter is used to avoid faulty reporting due to instabilityof power.Recommended value: 64The parameter to set the RLC PDU retransmission rate option is found in SET QOSACT.SrncBeDlRlcQosSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: When the parameter is set to YES, QoS control for DL BE services is based on the TCP and

5-36 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 331: SYS202m2 Usr7 Ver1 Rev2

Downlink Quality Measurement and Event Reporting Version 1 Rev 2

Downlink Quality Measurement and Event ReportingRLC retransmission. When the parameter is set to NO, QoS control for DL BE services is based on theTCP. In both situations, QoS control is not performed across the Iur interface.Recommended value: YES

T1T1

Power

Time

T1

Ea EbPeriodicReports

Ea PeriodicReport

T1 – DlHystTimeForE

E vent Abs olute T hres hold = maximum DL P ower – E vent R elative T hres hold + P O3

E vent R elative thres holds are both s et to a default of 1dB

RLMAXDLPWR

Event Relative Threshold

Event Relative Threshold

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-37

USR7

Page 332: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UE State Transition Algorithm

UE State Transition AlgorithmAfter the RRC connection is set up, the RNC observes UE activity and uses the UE state transitionalgorithm to transit the UE state.

UE State Transition AlgorithmThe figure opposite shows the RRC states in UTRA RRC Connected Mode, including transitionsbetween UTRA RRC connected mode and GSM connected mode for CS domain services, and betweenUTRA RRC connected mode and GSM/GPRS packet modes for PS domain services. It also showsthe transitions between Idle Mode and UTRA RRC Connected Mode and furthermore the transitionswithin UTRA RRC connected mode. In our algorithm, we only care for the state transition in the UTRANconnected mode.The principle of UE state transition is that:

• The state of the UE transits from CELL_DCH to CELL_FACH or from CELL_FACH toCELL_PCH/URA_PCH if the activity of UE decreases.

• The state of the UE transits from CELL_PCH/URA_PCH to CELL_FACH or from CELL_FACH toCELL_DCH if the activity of UE increases.

Datebase ParametersAt the RNC, the following parameters are available to control the function of UE state transition:

• PS_BE_STATE_TRANS_SWITCH• PS_NON_BE_STATE_TRANS_SWITCH• HSDPA_STATE_TRANS_SWITCH• HSUPA_STATE_TRANS_SWITCH

These are found in the command SET CORRMALGOSWITCH and are described below.ChSwitch — PS_BE_STATE_TRANS_SWITCH: When the switch is selected, UE RRC status transition(CELL_FACH/CELL_PCH/URA_PCH) is allowed at the RNC.PS_NON_BE_STATE_TRANS_SWITCH: When the switch is selected, the status of the UE RRC thatcarrying real-time services can be changed to CELL_FACH at the RNC.

HspaSwitch — HSDPA_STATE_TRANS_SWITCH: When the switch is selected, the status ofthe UE RRC that carrying HSDPA services can be changed to CELL_FACH at the RNC. If a PSBE service is carried over the HS-DSCH, the switch PS_BE_STATE_TRANS_SWITCH shouldbe selected simultaneously. If a PS real-time service is carried over the HS-DSCH, the switchPS_NON_BE_STATE_TRANS_SWITCH should be selected simultaneously.HSUPA_STATE_TRANS_SWITCH: When the switch is selected, the status of the UE RRC thatcarrying HSUPA services can be changed to CELL_FACH at the RNC. If a PS BE service is carriedover the E-DCH, the switch PS_BE_STATE_TRANS_SWITCH should be selected simultaneously. If aPS real-time service is carried over the E-DCH, the switch PS_NON_BE_STATE_TRANS_SWITCHshould be selected simultaneously.The UE state transition has dependencies on the DCCC algorithm; these are described below.If the above state transition switches are set to on, and:

• The DCCC_SWITCH is on and DCCC strategy is RATE_UP_AND_DOWN_ON_DCH, the UEstate transition algorithm starts to work if the uplink and downlink bit rate equals or falls below theUplink/Downlink bit rate threshold for DCCC.

• The DCCC_SWITCH is on and DCCC strategy is RATE_UP_ONLY_ON_DCH, the UE statetransition algorithm always works.

• The DCCC_SWITCH is off; the UE state transition algorithm always works.

5-38 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 333: SYS202m2 Usr7 Ver1 Rev2

UE State Transition Algorithm Version 1 Rev 2

UE State Transition Algorithm

Idle Mode

UTRAN Connected Mode

Camped on a UTRAN Cell Camped on a GSM/GPRS Cell

URA_PCHCELL_PCH

CELL_DCH (with HS-DSCH)

CELL_FACH

CELL_DCH

GSM Connected

Mode

GPRS Packet Transfer

ModeCell

Reselection

UTRAN Inter-RAT Handover

GSM Handover

Establish RR Connection

Release RR Connection

Release of temporary block flow

Initiation of temporary block flowRelease RRC

connection

Release RRC connection

Establish RRC connection

Establish RRC connection

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-39

USR7

Page 334: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HSDPA RRC State Switching

HSDPA RRC State SwitchingWith introducing HSDPA technology, the UE has one more RRC state CELL_DCH (with HS-DSCH).Channel switching can occur between HS-DSCH and FACH and HS-DSCH and DCH.

UE State Transition Channel Switching

CELL_DCH (with HS-DSCH) <-> CELL_DCH HS-DSCH <-> DCH

CELL_DCH (with HS-DSCH) <-> CELL_FACH HS-DSCH <-> FACH

Channel Switching between HS-DSCH and FACHSince the HSDPA UE occupies the DPCH, the UE will switch its state from the HS-DSCH to the FACHto reduce occupation of the DPCH when the following conditions are met:

• The HS-DSCH carries the BE service or the PS streaming service for the UE and ;• There is no data flow of any of the services for a certain length of time.

On the other hand, when the data flow gets more active, for example, when the RNC receives a 4a eventmeasuring report, the UE is switched from the FACH to the HS-DSCH.

Channel Switching between HS-DSCH and DCHThe channel switching between HS-DSCH and DCH includes the switching from HS-DSCH to DCH andthe switching from DCH to HS-DSCH. The switching from DCH to HS-DSCH can be triggered by mobilitymanagement, the traffic volume or the timer. The switching from HS-DSCH to DCH can only be triggeredby mobility management.

• Triggered by Mobility Management — The mobility management aspects are covered in thehandover and directed retry chapters of this course.

• Triggered by Traffic Volume — When the activity of the UE that performs data services increasesand the RNC receives the report of the 4a event, the channel type of this UE will switch from DCHto HS-DSCH.

• Triggered by Timer — When the service is suitable to be carried on HSDPA and the UE supportsHSDPA but the service is actually mapped onto the DCH (for some reasons such as the UE isrejected to access a HSDPA cell by CAC Algorithm), a timer is used to periodically reattempt tomap the service onto the HS-DSCH. Firstly, attempt to map onto HS-DSCH of the current cell, iffailed, then attempt to map onto HS-DSCH of a inter-frequency blind handover cell with the samecoverage. This timer length is set to H Retry timer length.

The command to set the H Retry timer length is SET COIFTIMER and is described below.HRetryTimerLen — Timer length for H RetryValue range: 0, 1 to 180Physical unit: sContent: When the DCH is handed over to the HS-DSCH/E-DCH, a timer for retry needs to start. Youcan set the timer length in this parameter. When the timer length is set to zero, the retry function is off.Recommended value (default value): 5

5-40 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 335: SYS202m2 Usr7 Ver1 Rev2

HSDPA RRC State Switching Version 1 Rev 2

HSDPA RRC State Switching

CELL_DCH (with HS-

DSCH)

CELL_DCH

Switching to CELL_DCH by:

• mobility management i.e. Handovers and Directed Retry

Switching to CELL_DCH (with HS-DSCH) by:

• Traffic volume (4a Event)

• By timer (periodically attempt to move to HS Cell when allocated CELL_DCH)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-41

USR7

Page 336: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 RRC state switching

RRC state switchingThis subsection describes the algorithm used by RNC to perform RRC states switches. For thisalgorithm to be operative for PS BE services the PS_BE_STATE_TRANS_SWITCH must be enabledand for PS non BE services the PS_NON_BE_STATE_TRANS_SWITCH must be enabled. Also theDCCC_SWITCH maybe enabled. All these parameters are found in the SET CORRMALGOSWITCHcommand.

CELL_DCH to CELL_FACHWhen the RNC receives the event report 4b about the decrease of the UE activity (event 4b), it starts atimer on the RNC side. If both uplink and downlink 4B counters of traffic volume event 4b report equalsor exceeds a threshold before a timer expires. (The timer can be DCH TO FACH TRANSITION TIMERor BE HS-DSCH TO FACH TRANSITION TIMER or REALTIME TRAFF DCH OR HS-DSCH TO FACHTRANSITION TIMER or E-DCH TO FACH TRANSITION TIMER.The threshold is calculated by the formula:[ CELL_DCH to CELL_FACH transition time / (Time to trigger + Pending time after Trigger)* Statetrans traff redund coef ] (The rounded down value of the formula)These parameters which can be set for BE, Realtime or HS traffic are set in the command SETUESTATETRANS and are listed below.DtoFStateTransTimer/BeH2FStateTransTimer/RtDH2FStateTransTimer/BeE2FStateTransTimer —Value range: 1 to 65535Physical unit: sContent: This parameter is used to a. detect whether a non-real time service UE is stable in low activityb.to detect the stability of a UE in low activity state in CELL_DCH (with HS-DSCH) state c. to detectwhether a real-time service UE in CELL_DCH state is in stable low activity state d. to detect whether aBE service UE in E-DCH channel is in stable low activity state.Recommended value (default value): 5sD2F2PTvmThd/BeH2FTvmThd/RtDH2FTvmThd/BeE2FTvmThd — Value range: D8....D768Physical value range: 8....768kPhysical unit: Byte.Content: a. This threshold is used to judge whether a UE is in lowactivity state. If the UE is in CELL_DCH/(with HS-DSCH)/RT on DCH orHS-DSCH/E-DCH state. If the UE is below these thresholds when theDtoFStateTransTimer/BeH2FStateTransTimer/RtDH2FStateTransTimer/BeE2FDtoFStateTransTimeris running, the 4B counter increments by 1 every time the UE reports event 4b.Recommended value (default value): D64D2FTvmTimeToTrig/BeH2FTvmTimeToTrig/RtDH2FTvmTimeToTrig/BeE2FTvmTimeToTrig —Value range: D0....D5000Physical value range: 0....5000Physical unit: ms.Content: When the traffic volume is smaller than the lower threshold and lasts this time length, the UEreport event 4b. This parameter can avoid triggering unneeded events due to unstable traffic volumes.Recommended value (default value): D5000D2FTvmPTAT/BeH2FTvmPTAT/RtDH2FTvmPTAT/BeE2FTvmPTAT — Value range:D250.....D16000.Physical Range: 250.....16000Physical unit: ms.Content: Time interval of reporting event 4b. The parameter can avoid too many event 4b reports.Recommended value (default value): D16000

5-42 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 337: SYS202m2 Usr7 Ver1 Rev2

RRC state switching Version 1 Rev 2

RRC state switching

64K (def)

time-to-trigger (5s def)

Event 4a

Pending-time-after-trigger (1s def)

CELL_DCH to CELL_FACH transition-time (5s def)

DCH to FACH Transition

(t)

Transport channel traffic volume

4B Counter ≥ [ CELL_DCH to CELL_FACH transition time / (Time to trigger + Pending time after Trigger)* State trans traff redund coef (0.8 not configurable) ] (Round down)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-43

USR7

dqfr38
Text Box
4b
Page 338: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 When UE State Transitions will not occur

When UE State Transitions will not occurUE state transition, however, is not applicable in the following cases.

For BE services on the DCHIf PS_BE_STATE_TRANS_SWITCH is set to OFF, or other services which cannot perform statetransition are configured for the UE, no state transition is performed on the UE. Instead, if both uplinkand downlink 4b counters of traffic volume event 4b report are greater than or equal to a CELL_DCHto CELL_FACH transition threshold when the CELL_DCH to CELL_FACH transition timer expires, theUE is reconfigured to the low-activity rate that is defined through the Low activity bit rate thresholdparameter.However, if the value of Low activity bit rate threshold is greater than or equal to that ofUplink/Downlink bit rate threshold for DCCC, the reconfiguration to Low activity bit rate thresholdis prohibited.

For BE services on the HS-DSCH or E-DCHIf PS_BE_STATE_TRANS_SWITCH orHSDPA_STATE_TRANS_SWITCH/HSUPA_STATE_TRANS_SWITCH is set to OFF, or otherservices which cannot perform state transition are configured for the UE, the UE does notundergo state transition.

For real-time PS servicesIf PS_NON_BE_STATE_TRANS_SWITCH is set to OFF, or other services which cannot perform statetransition are configured for the UE, the UE does not undergo state transition.

Database ParametersThe parameters to set the DCCC thresholds describe in ’For BE services on the DCH’ are found in thecommand SET DCCC and are listed below.UlDcccRateThd — Value range: D8, D16, D32, D64, D128, D144, D256, D384Physical value range: 8, 16, 32, 64, 128, 144, 256, 384Physical unit: kbit/sContent: For a BE service that has a low maximum rate, the DCCC algorithm is not obviously effectiveyet it increases algorithm processing. Thus, the traffic-based DCCC algorithm is applied to BE serviceswhose maximum UL rate is greater than the threshold.Recommended value: D64DlDcccRateThd — Value range: D8, D16, D32, D64, D128, D144, D256, D384Physical value range: 8, 16, 32, 64, 128, 144, 256, 384Physical unit: kbit/sContent: For a BE service that has a low maximum rate, the DCCC algorithm is not obviously effectiveyet it increases algorithm processing. Thus, the traffic-based DCCC algorithm is applied to BE serviceswhose maximum DL rate is greater than the threshold.Recommended value: D64LittleRateThd — Value range: D0, D8, D16, D32, D64, D128, D144, D256, D384Physical value range: 0, 8, 16, 32, 64, 128, 144, 256, 384Physical unit: kbit/sContent: When the BE service rate of the UE decreases to the DCCC threshold rate, the UE, however,cannot be changed to the FACH state because, for example, the state transition switch is OFF or there areCS services. In this case, when traffic remains low for quite a long period, the service rate decreases tothis rate and D2F state transition is not performed. The time parameters and traffic volume measurementparameters for the function of low activity rate adjustment are the same as those in the D2F state transitionprocess.Recommended value: D64

5-44 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 339: SYS202m2 Usr7 Ver1 Rev2

When UE State Transitions will not occur Version 1 Rev 2

When UE State Transitions will not occur

For BE services on the DCHPS_BE_STATE_TRANS_SWITCH = OFF

However will reconfigure to Low activity bit rate threshold unless

Low activity bit rate threshold >= Uplink/Downlink bit rate threshold (SET DCCC)

For BE services on the DCHPS_BE_STATE_TRANS_SWITCH = OFF

However will reconfigure to Low activity bit rate threshold unless

Low activity bit rate threshold >= Uplink/Downlink bit rate threshold (SET DCCC)

For BE services on the HS-DSCH or E-DCHPS_BE_STATE_TRANS_SWITCH = OFF

Or

HSDPA_STATE_TRANS_SWITCH/HSUPA_STATE_TRANS_SWITCH = OFF

For BE services on the HS-DSCH or E-DCHPS_BE_STATE_TRANS_SWITCH = OFF

Or

HSDPA_STATE_TRANS_SWITCH/HSUPA_STATE_TRANS_SWITCH = OFF

For real-time PS servicesPS_BE_STATE_TRANS_SWITCH = OFF

For real-time PS servicesPS_BE_STATE_TRANS_SWITCH = OFF

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-45

USR7

Page 340: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 CELL_FACH to CELL_PCH

CELL_FACH to CELL_PCHThe process is similar to that for transiting from CELL_DCH to CELL_FACH. The RNC decides when tostart the transition through the UE activity measurement. When the RNC receives the report about thedecrease of the UE activity (event 4b) and the traffic volume of event report 4b is zero, it starts a timeron the RNC side.If both uplink and downlink 4B counter of traffic volume event 4b report equal or exceed a thresholdbefore a timer expires. (The timer is FACH TO PCH TRANSITION TIMER), And when the timer expiresthe UE state transits from CELL_FACH to CELL_PCH.This UE state transition happens only when the BE service of the PS domain exists.The threshold is calculated by the formula:[FACH TO PCH TRANSITION TIMER / (FACH to PCH 4B time to trigger + FACH to PCH 4B PendingTime after trigger)* State trans traff redund coef ] (The rounded down value of the formula)These parameters which can be set for BE, Realtime or HS traffic are set in the command SETUESTATETRANS and are listed below.FtoPStateTransTimer — Value range: 1 to 65535Physical unit: sContent: This parameter is used to detect whether a UE is stable in low activity. When it is set as 65535,the UE will not transit from FACH to PCH.Recommended value (default value): 180FtoDTvmThd — Value range: D8....D768Physical value range: 8....768kPhysical unit: Byte.Content: Upper threshold of traffic volume triggering event 4a, that is, triggering the transition from FACHto DCH.Recommended value (default value): D1024F2PTvmTimeToTrig — Value range: D0....D5000Physical value range: 0....5000Physical unit: ms.Content: When the traffic volume is smaller than the lower threshold and lasts this time length, the UEreport event 4b. This parameter can avoid triggering unneeded events due to unstable traffic volumes.Recommended value (default value): D5000F2PTvmPTAT — Value range:D250.....D16000.Physical Range: 250.....16000Physical unit: ms.Content: Time interval of reporting event 4b. The parameter can avoid too many event 4b reports.Recommended value (default value): D16000

5-46 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 341: SYS202m2 Usr7 Ver1 Rev2

CELL_FACH to CELL_PCH Version 1 Rev 2

CELL_FACH to CELL_PCH

CELL_FACH

Event 4b occurs

Transition timer begins 180s def

4B Counter ≥ [FACH to PCH Transition time / (FACH to PCH 4B time to trigger + FACH to PCH 4B Pending Time after trigger)* State trans traff redund coef ] (Round down)

Increment 4B counter when below TVM thresholds (O bytes fixed) during transition timer

CELL_PCH

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-47

USR7

Page 342: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 CELL_PCH to URA_PCH

CELL_PCH to URA_PCHThe state of the UE is CELL_PCH. During the cell reselection, the UE sends the CELL UPDATEmessages. The RNC starts a timer (CELL RESELECTION TIMER) and counts the number of the CELLUPDATE messages with the cause value of cell reselection. When the timer expires, the number of theCELL UPDATE messages may exceed the threshold (CELL RESELECTION COUNTER). In that case,the RNC initiates the state transition when the UE sends the CELL UPDATE message again. This UEstate transition happens when only the BE service of the PS domain exists.The state of the UE transits to CELL_FACH when the UE initiates the cell update process or when theUE is paged by UTRAN and the UE needs to exchange messages with the network side. This is thecase for both CELL_PCH and CELL_URA.

Database ParametersThe parameters to set the CELL_PCH to URA_PCH transition id found in the command SETUESTATETRANS and are described below.CellReSelectTimer — Length of the cell reselection frequency timerValue range: 1~65535 Unit: sContent: This parameter is used together with CellReSelectCounter to detect the frequency of cellreselection of the UE in the CELL_PCH state.Recommended value (default value): 180CellReSelectCounter — Threshold of cell reselection timesValue range: 1~65535Content: If the times the UE in the CELL_PCH state performs cell reselection is greater than or equal tothe threshold, it is regarded that the cell reselection is frequent. When the timer expires, the target stateis set to URA_PCH. In the next cell update procedure, the UE is informed of state transition to URA_PCHin the CELL_UPDATE_CONFIRM message.Recommended value (default value): 9

5-48 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 343: SYS202m2 Usr7 Ver1 Rev2

CELL_PCH to URA_PCH Version 1 Rev 2

CELL_PCH to URA_PCH

URA_PCH

CELL_PCH

CELL_FACH

C ell update with caus e value res elec tion

Timer CELL RESELECTION TIMER (180s def) begins and counts the Cell Update messages with the cause value reselection

If the number of Cell Update messages exceeds the CELL RESELECTION COUNTER (9 def) then on the next Cell Update transition to URA_PCH state

Cell Update

If the UE is paged or needs to perform Cell Update or URA Update then transitions back to CELL_FACH

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-49

USR7

Page 344: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Link Stability Control Algorithms

Link Stability Control AlgorithmsThe following lists the contents of this section:

• Link Stability Control Algorithms for AMR/AMR-WB Speech Services.• Link Stability Control Algorithms for VP Services.• Link Stability Control Algorithms for BE Services.

Link stability control only applies to the case where a single RAB is in operation.

Link Stability Control Algorithms for AMR/AMR-WB ServicesThe link stability control algorithms for AMR/AMR-WB services is used to trigger rate downsizing,inter-frequency handover, or inter-RAT handover when the uplink transmit power of the UE or downlinktransmitted code power of the NodeB exceeds the associated threshold, so as to guarantee the stabilityof links.The actions of the link stability control algorithm for AMR/AMR-WB speech services are rate downsizing,inter-frequency handover, and inter-RAT handover. They are controlled by individual switches butare performed in a fixed sequence of rate downsizing, inter-frequency handover, and then inter-RAThandover. For AMR/AMR-WB speech services, the rate downsizing refers to the link-quality-based ratedownsizing algorithm.

Uplink Link Stability Control AlgorithmWhen rate downsizing is configured, that is, when link-quality-based AMRC/AMRC-WB algorithmis enabled, if a 6A1 or 6D report is received and the UL AMRC timer (Wait Timer for UplinkRateAdjustment of Traffic AMR/WB-AMR) has expired, and the current rate is GBR, then:

• If InterFreq Handover Switch based on Uplink Traffic AMR/WB-AMR is set to YES,inter-frequency handover is performed.

• If InterRat Handover Switch based on Uplink Traffic AMR/WB-AMR is set to YES, inter-RAThandover is performed.

• If both switches are set to YES, the inter-frequency and inter-RAT measurement are started at thesame time, and then the RNC decides to perform which type of handover based on the first reportfrom the UE.

When rate downsizing is not configured, that is, when link-quality-based AMRC/AMRC-WB algorithm isnot enabled, if a 6A1 or 6D report is received, then:

• If InterFreq Handover Switch based on Uplink Traffic AMR/WB-AMR is set to YES,inter-frequency handover is performed.

• If InterRat Handover Switch based on Uplink Traffic AMR/WB-AMR is set to YES, inter-RAThandover is performed.

• If both switches are set to YES, the inter-frequency and inter-RAT measurement are started at thesame time, and then the RNC decides to perform which type of handover based on the first reportfrom the UE.

Database ParametersThe parameters for UL link stability control for AMR/WB-AMR are found in the command SET QOSACTand are described below.(W)AMRQosPerform — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: When the parameter is set to YES, the QOS control algorithm is used for (W)AMR services.When the parameter is set to NO, the QOS control algorithm is not used for AMR services.Recommended value: NOUlQos(W)AmrAdjSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: rate adjustment switch of link stability control for UL QoS of (W)AMR services. When theparameter is set to YES, UL rate of (W)AMR services can be adjusted.Recommended value: NO

5-50 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 345: SYS202m2 Usr7 Ver1 Rev2

Link Stability Control Algorithms Version 1 Rev 2

Link Stability Control AlgorithmsUlQos(W)AmrInterFreqHoSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: inter-frequency handover switch of link stability control for UL QoS of (W)AMR services. Whenthe parameter is set to YES, inter-frequency handover can be performed for (W)AMR services to ensurethe QoS.Recommended value: NOUlQos(W)AmrInterRatHoSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: inter-RAT handover switch of link stability control for UL QoS of (W)AMR services. When theparameter is set to YES, inter-RAT handover can be performed for (W)AMR services to ensure the QoS.Recommended value: NO

AmrUlRateAdjTimerLen

Timer stopped when 6b1 rx’d. If 6b1 is not rx’dbefore timer expires then reduce to the next AMR mode and restart timer – same principle applies to

6b2

320ms

Reportingevent 6A1

ReportingEvent 6B1

UE Tx power

If AMRC enabled and UE sends event 6A1 or 6D and bit rate = GBR and timer expired or

If AMRC not enabled and 6A1 or 6D reported by UE then:

Handover to Inter-Freq or Inter-RAT neighbour cell

6A1 Threshold

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-51

USR7

Page 346: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Link Stability Control Algorithm

Downlink Link Stability Control AlgorithmWith this algorithm it depends on whether the DL AMRC algorithm is enabled to decide which events touse:

• When rate downsizing is configured, that is, when link-quality-based AMRC/AMRC-WB algorithmis enabled, the measurement events are events E1 and E2.

• When rate downsizing is not configured, that is, when link-quality-based AMRC/AMRC-WBalgorithm is not enabled, the measurement events are events Ea and Eb.

Note: For an AMR service, the trigger time of event E is set to 640ms, and the reporting period of eventE is set to 4,800ms.

ActionsWhen rate downsizing is configured (that is, when link-quality-based AMRC/AMRC-WB algorithm isenabled) and the current rate is GBR, if the average DPDCH transmit power is lower than the E1 thresholdand higher than the E2 threshold but the AMR/AMR-WB status is "Rate-Down or higher than E1 threshold,then

• If InterFreq Handover Switch based on Downlink Traffic AMR/WAMR is set toYES,inter-frequency handover is performed.

• If InterRat Handover Switch based on Downlink Traffic AMR/WAMR is set to YES, inter-RAThandover is performed.

• If both switches are set to YES, the inter-frequency and inter-RAT measurement are started at thesame time, and then the RNC decides to perform which type of handover based on the first reportfrom the UE.

When rate downsizing is not configured, that is, when link-quality-based AMRC/AMRC-WB algorithm isnot enabled, if an event Ea report is received, then

• If InterFreq Handover Switch based on Downlink Traffic AMR/WAMR is set toYES,inter-frequency handover is performed.

• If InterRat Handover Switch based on Downlink Traffic AMR/WAMR is set to YES, inter-RAThandover is performed.

• If both switches are set to YES, the inter-frequency and inter-RAT measurement are started at thesame time, and then the RNC decides to perform which type of handover based on the first reportfrom the UE.

Database ParametersThe parameters for DL link stability control for AMR/WB-AMR are found in the command SET QOSACTand are described below.DlQos(W)AmrAdjSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: rate adjustment switch of link stability control for DL QoS of (W)AMR services. When theparameter is set to YES, DL rate of (W)AMR services can be adjusted.Recommended value: NODlQos(W)AmrInterFreqHoSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: inter-frequency handover switch of link stability control for DL QoS of (W)AMR services. Whenthe parameter is set to YES, inter-frequency handover can be performed for (W)AMR services to ensurethe QoS.Recommended value: NODlQos(W)AmrInterRatHoSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: inter-RAT handover switch of link stability control for DL QoS of (W)AMR services. When theparameter is set to YES, inter-RAT handover can be performed for (W)AMR services to ensure the QoS.Recommended value: NO

5-52 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 347: SYS202m2 Usr7 Ver1 Rev2

Downlink Link Stability Control Algorithm Version 1 Rev 2

Downlink Link Stability Control Algorithm

T1T1

Power

Time

T1

Ea EbPeriodicReports

Ea PeriodicReport

RLMAXDLPWR

Event Relative Threshold

Event Relative Threshold

If rate downsizing AMR algorithm is on and at GBR and requesting lower rate or above E1 threshold

Or

If rate downsizing AMR algorithm off and reporting Ea then:

• Handover to Inter-Freq or Inter-RAT neighbour cell

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-53

USR7

Page 348: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Link Stability Control Algorithms for VP Services

Link Stability Control Algorithms for VP ServicesThe link stability control algorithm for Video Phone (VP) services is used to trigger inter-frequencyhandover when the uplink transmit power of the UE or downlink transmitted code power of the NodeBexceeds the associated threshold, so as to guarantee the stability of the links.

Uplink Link Stability Control AlgorithmThe uplink link stability control algorithm for VP services is related to events 6A1, 6B1, and 6D.Note: For VP service the trigger time of event 6A1 and 6B1 are both set to 640 ms, and the trigger timeof event 6D is set to 240 ms.When link stability control algorithm for VP services is enabled for uplink (InterFreq Handover Switchbased on Uplink Traffic VP is set to YES), Inter-frequency handover is performed if an event 6A1 or6D report is received.

Downlink Link Stability Control AlgorithmThe downlink link stability control algorithm for VP services is related to event Ea and Eb.Note: For VP service, the trigger time of event E is set to 640 ms, and the reporting period of event E isset to 4,800 ms.When link stability control algorithm for VP services is enabled for downlink (InterFreq Handover Switchbased on Downlink Traffic VP is set to YES). Inter-frequency handover is performed if an Ea report isreceived.

Database ParametersThe parameters for DL/UL link stability control for VP services are found in the command SET QOSACTand are described below.VPQosPerform — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: When the parameter is set to YES, the QOS control algorithm is used for VP services. Whenthe parameter is set to NO, the QOS control algorithm is not used for VP services.Recommended value: NOUlQosVpInterFreqHoSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: inter-frequency handover switch of link stability control for UL QoS of VP services. When theparameter is set to YES, inter-frequency handover can be performed for VP services to ensure the QoS.Recommended value: NODlQosVpInterFreqHoSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: inter-frequency handover switch of link stability control for DL QoS of VP services. When theparameter is set to YES, inter-frequency handover can be performed for VP services to ensure the QoS.Recommended value: NO

5-54 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 349: SYS202m2 Usr7 Ver1 Rev2

Link Stability Control Algorithms for VP Services Version 1 Rev 2

Link Stability Control Algorithms for VP Services

RNCRNCCN

Iu

Iub

NBVideo Phone Call

Ea reported DL

6A1 or 6D reported UL

InterFrequencyHandover

Performed

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-55

USR7

Page 350: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Link Stability Control Algorithms for BE Services

Link Stability Control Algorithms for BE ServicesThe link stability control algorithm for BE services is used to trigger rate downsizing, inter-frequencyhandover, or inter-RAT handover so as to guarantee the stability of links when the uplink or downlink linkquality deteriorates, which is indicated by the high uplink/downlink transmitted power or the high BLER(for uplink)/high RLC retransmission rate (for downlink).

Uplink Link Stability Control AlgorithmFor the uplink link stability control algorithm for BE services, the RNC uses events 6A, 6B, 6D, and 5A.When Measurement of 6D Switch is ON, event 6D can directly trigger uplink link stability control action.When Uplink QOS Action Trigger Indicator of Traffic BE is SINGLE and Measurement of 6A1 Switchis ON, event 6A1 can trigger uplink link stability control action.When Uplink QOS Action Trigger Indicator of Traffic BE is SINGLE and Measurement of 5A Switchis ON, event 5A can trigger uplink link stability control action.When Uplink QOS Action Trigger Indicator of Traffic BE is COMBINE, the combination of event 6A1and event 5A can trigger uplink link stability control action.

Database ParametersThe parameters for the uplink stability control algorithm are found in the command SET QOSACT andare described below.BEQosPerform — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: When the parameter is set to YES, the QOS control algorithm is used for BE services. Whenthe parameter is set to NO, the QOS control algorithm is not used for BE services.Recommended value: YESBeUlEvTrigInd — Value range: SINGLE, COMBINEPhysical value range: 0~1Physical unit: noneContent: When the parameter is set to SINGLE, an UL event 6A1, 6D, or 5A can independently trigger theQOS enhancement action. The switch settings decides whether 6A1, 6D, or 5A measurement control isdelivered to trigger the action. When the parameter is set to COMBINE, combined events 6A1+5A or anevent 6D can trigger the QOS enhancement action. The switch settings decides whether the combined6A1+5A or the 6D measurement control is delivered to trigger the action.Recommended value: SINGLEBeUlAct1 — Value range: RateDegrade, InterFreqHO, InterRatHOPhysical value range: 0~3Physical unit: noneContent: the first action selected by the QoS control algorithm when the UL QoS deterioratesRecommended value: InterFreqHOBeUlAct2 — Value range: RateDegrade, InterFreqHO, InterRatHOPhysical value range: 0~3Physical unit: noneContent: the second action selected by the QoS control algorithm when the UL QoS deterioratesRecommended value: InterFreqHOBeUlAct3 — Value range: RateDegrade, InterFreqHO, InterRatHOPhysical value range: 0~3Physical unit: noneContent: the third action selected by the QoS control algorithm when the UL QoS deterioratesRecommended value: InterFreqHOBeUlRateAdjTimerLen — Value range: 20~64000Physical unit: msContent: timer to trigger the next QoS enhancement action for UL BE services. This parameter specifiesthe duration of waiting for the UL QoS enhanced acknowledgement after UL rate adjustment. The timerstarts when the UL rate adjustment procedure is triggered, and stops when the RNC receives a 6B1/6B2event or when the timer expires.Recommended value: 3000BeUlQos6A1McSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: none

5-56 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 351: SYS202m2 Usr7 Ver1 Rev2

Link Stability Control Algorithms for BE Services Version 1 Rev 2

Link Stability Control Algorithms for BE ServicesContent: event 6A1 measurement switch when BeUlEvTrigInd is set to SINGLE. If this parameter is setto YES, event 6A1 measurement is delivered.Recommended value: YESBeUlQos5AMcSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: event 5A measurement switch when BeUlEvTrigInd is set to SINGLE. If this parameter is setto YES, event 5A measurement is delivered.Recommended value: YESBeUlQos6DMcSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: UL event 6D measurement switch. If this parameter is set to YES, event 6D measurement isdelivered.Recommended value: NOThe parameter to set the uplink full coverage bitrate is found in the command ADD CELLDCCC and isdescribed below.UlFullCvrRate — Value range: D8, D16, D32, D64, D128, D144, D256, D384Physical value range: 8, 16, 32, 64, 128, 144, 256, 384Physical unit: kbit/sContent: maximum UL rate when coverage of the entire cell is ensured under certain load. For a BEservice that has a low maximum rate, the DCCC algorithm is not obviously effective yet it increasesalgorithm processing. Thus, the coverage-based DCCC algorithm is applied to BE services whosemaximum UL rate is greater than the threshold.Recommended value: D64

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-57

USR7

Page 352: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Link Stability Control Algorithm

Downlink Link Stability Control AlgorithmFor the downlink link stability control algorithm for BE services, the RNC uses events Ea, Eb, Fa, Fb,and A.When determining the downlink link stability control, the following two aspects are taken into account:

• One is the current transmit power. When the transmit power of the downlink channel reaches themaximum power, it is an indication that the radio link is unstable. The following condition must befulfilled: The transmit power of downlink channel exceeds the Ea event relative threshold whichequals to 1 dB.

• The other is RLC PDU retransmission rate in AM RLC mode. When the Srnc Downlink RLC QOSAction Trigger Indicator of Traffic BE is set to YES, the downlink link stability control algorithmis determined only if the RLC retransmission rate exceeds the retransmission threshold (that is,Event A threshold, which equals to 16%). When the Srnc Downlink RLC QOS Action TriggerIndicator of Traffic BE is set to NO, related actions are triggered so long as the current transmitpower fulfils the criteria.

ActionsThe actions taken are similar to the UL actions and can be summed up in the flowchart.The action in the dashed frame can be ignored in a link stability control procedure, if the last procedurehas contained the rate downsizing action and the current rate is above Downlink Full Coverage BitRate.

Database ParametersThe parameters for the downlink stability control algorithm are found in the command SET QOSACT andare described below.BeDlAct1 — Value range: None, RateDegrade, InterFreqHO, InterRatHOPhysical value range: 0~3Physical unit: noneContent: the first action selected by the QoS control algorithm when the DL QoS deterioratesRecommended value: InterFreqHOBeDlAct2 — Value range: None, RateDegrade, InterFreqHO, InterRatHOPhysical value range: 0~3Physical unit: noneContent: the second action selected by the QoS control algorithm when the DL QoS deterioratesRecommended value: RateDegradeBeDlAct3 — Value range: None, RateDegrade, InterFreqHO, InterRatHOPhysical value range: 0~3Physical unit: noneContent: the third action selected by the QoS control algorithm when the DL QoS deterioratesRecommended value: RateDegradeSrncBeDlRlcQosSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: When the parameter is set to YES, QoS control for DL BE services is based on the TCP andRLC retransmission. When the parameter is set to NO, QoS control for DL BE services is based on theTCP. In both situations, QoS control is not performed across the Iur interface.Recommended value: YESDrncBeDlRlcQosSwitch — Value range: NO, YESPhysical value range: 0~1Physical unit: noneContent: If the parameter is set to YES, QoS control for DL BE services is based on RLC retransmissionwhen the optimal cell is on the DRNC.Recommended value: NOThe parameter to set the downlink full coverage bitrate is found in the command ADD CELLDCCC andis described below.DlFullCvrRate — Value range: D8, D16, D32, D64, D128, D144, D256, D384Physical value range: 8, 16, 32, 64, 128, 144, 256, 384Physical unit: kbit/sContent: maximum DL rate when coverage of the entire cell is ensured under certain load. For a BEservice that has a low maximum rate, the DCCC algorithm is not obviously effective yet it increases

5-58 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 353: SYS202m2 Usr7 Ver1 Rev2

Downlink Link Stability Control Algorithm Version 1 Rev 2

Downlink Link Stability Control Algorithmalgorithm processing. Thus, the coverage-based DCCC algorithm is applied to BE services whosemaximum DL rate is greater than the threshold.Recommended value: D64

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

5-59

USR7

Page 354: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Link Stability Control Algorithm

This page intentionally left blank.

5-60 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 355: SYS202m2 Usr7 Ver1 Rev2

Power Control Version 1 Rev 2

Chapter 6

Power Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-1

USR7

Page 356: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Power Control

This page intentionally left blank.

6-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 357: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter Objectives

• State the purpose and briefly describe the function of power control• Describe the open loop power control• Describe the Downlink Closed Loop Power Control Mechanisms• Describe the Uplink Closed Loop Power Control Mechanism• Describe the outer closed loop mechanism• Describe the downlink load balancing algorithm

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-3

USR7

Page 358: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Introduction to Power Control

Introduction to Power ControlThe power control mechanism is an essential part of cellular systems using the spread spectrumtechnique of medium access. There are important functions of power control.First, is to support high system capacity, which is basically achieved in CDMA-based systems by reducingthe level of adverse interference. The major contribution to system interference level, in uplink anddownlink direction respectively, comes from simultaneous RF signal transmissions by many UEs andadjacent Node Bs on the same frequency.The second function of power control procedures is to preserve required radio communication qualityregardless of dynamic changes in the propagation environment resulting from the mobility of UEs, thechanging number of active users in the system, and the ever propagation characteristics of and radiochannel. The quality may be defined here as low delay and error-free transmission of digitised user datathrough radio channel.One of the ways to obtain, at the same time, large system capacity and high service quality is to keepUE and Node B RF signals transmission power at the lowest possible level and adjust it dynamicallyupon variations of propagation conditions. The more accurate are UE and Node B power controlmechanisms to follow real dynamic structure of RF environment, the higher system capacity and servicequality performance may be achieved.The goal of power control in WCDMA system is thus dynamic interference control, rather than widecoverage area support.The UE and UTRAN power control procedures use different sources of feedback information on temporalpropagation channel condition in the process of adjusting their transmitted signals power levels.

6-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 359: SYS202m2 Usr7 Ver1 Rev2

Introduction to Power Control Version 1 Rev 2

Introduction to Power Control

• To Support High System Capacity by reducing the level of Interference.• To Preserve The Required Radio Communication Quality Resulting From:

– Changes to the Propagating Environment due to UE Mobility– Changes to the number of active users– Changes to the Propagating Characteristics of the Radio Channel

Three Types of Power Control

• Open Loop Power Control• Inner Closed Loop Power Control• Outer Closed Loop Power Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-5

USR7

Page 360: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Open Loop Power Control

Open Loop Power ControlIn an open loop power control mechanism, the transmitter has to determine its transmit power without anyexplicit feedback, from the receiving entity, as to whether that power level is satisfactory. An exampleof such a mechanism occurs when the UE starts an access cycle transmitting on the PRACH. Notehowever that it does not mean that the transmitter has no information at all about the conditions of thereceiver. For example, the UE reports the CPICH measurements to the RNC and the RNC can use suchmeasurements to decide on the initial downlink transmit power that should be used by the Node B. Inthe opposite direction, the UE may know the uplink noise rise in a particular cell to compute the initialtransmit power to use on the PRACH.This is a fairly crude mechanism. For example, it assumes that the pathloss of the radio channel isidentical on the uplink and on the downlink, which can be a fair assumption over a long period of time butis certainly not the case over short periods. To compensate for such inaccuracies, either the transmittertends to include some margin in its transmit power estimation or further mechanisms are required toensure a suitable communication (for example, the power ramp used on the PRACH).If both the received signal power and its transmission power level at its origin are know, it is possible toestimate radio channel insertion loss called here path loss.

Downlink Open Loop Power ControlDL common channel power level is a function of system capacity, coverage area, services class, requiredquality of service and projected number of users in the cell. The Planning Guide document containsinformation on common physical channel power requirements.The power levels for the DL common physical channels concerned, are specified as an offset from thepower level of the CPICH. Where Dynamic variation of the CPICH TX level (Cell Breathing), is supported,their will be a corresponding dynamic variation in the other downlink channels.

6-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 361: SYS202m2 Usr7 Ver1 Rev2

Open Loop Power Control Version 1 Rev 2

Open Loop Power Control

• Determines Initial TX power on Specified Common Physical Channels

• Downlink– PICH– AICH– SCCPCH– Initial Dedicated Channel Power

• Uplink– PRACH– Initial Dedicated Channel Power

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-7

USR7

Page 362: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink Open Power Control Loop

Uplink Open Power Control LoopIn uplink open loop power control the UE makes decisions on power adjustment based on assumedsymmetry of uplink and downlink RF channel characteristics. This process requires initial estimation ofDL path loss, which is obtained through subtraction of measured PCPICH received signal code Power(RSCP) strength, from PCPICH transmitted power. The transmitted cell PCPICH power level value ispart of the system information broadcast.Open loop power control is used in uplink transmission on the Physical Random Access Channel(PRACH) to adjust its initial transmit power during random access procedures by the UE to UMTSservices.In order to assist the UE in accomplishing this the UTRAN broadcasts, in every cell, on the CommonBroadcast Channel (BCH) in System Information Block number 5 (SIB5) the following data:

• The cell transmitted power level of the Primary Common Pilot Channel (P-CPICH) signal encodedin parameter PcpichPower.

NOTEThe PcpichPower value must be set in the range confined by parameter value of MinPCPICHPowerand MaxPCPICHPower

• A recently measured value of cell interference power level in uplink channel UL interference level,• The constant UE preamble transmission power offset that compensate inequality in between UL and

DL transmission channel. The selection of the offset value should ensure that a preamble signal,received at the Node B, has sufficient power level to be detected. The offset is called constantvalue and it is encoded in parameter Constantvalue, which also specifies required level of C/I inthe uplink.

The UE measures the received pilot signal code power (CPICH_RSCP) on the P-CPICH in order toestimate the downlink path loss and then calculates the initial preamble transmission power level usingthe following formula:

UL interference is the aggregate uplink channel noise and interference power level measured by theNode B per cell basis within WCDMA frequency channel bandwidth. The value of UL inference level isbroadcast in the cell using SIB 7.The Node B receiver sensitivity for preamble detection is in turn controlled by a threshold given byparameter value of PreambleThd. If, when received at the Node B, the preamble signal power exceedsthis threshold Node B may initiate process of preamble decode. The Node B detection threshold forpreamble detection depends on the Node B receiver sensitivity. When the Node B detects that a preamblehas been received, it measures the signal-to-interference ratio during that preamble transmission. If thatmeasurement is greater than a given threshold specified by the parameter PreambleThd, a positiveacknowledgement (Acquisition Indicator) is sent on the Acquisition Indicator Channel (AICH). The powerused on the AICH is determined by the parameter AICHPowerOffset which specifies the power offsetbetween the AICH and the CPICH.

6-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 363: SYS202m2 Usr7 Ver1 Rev2

Uplink Open Power Control Loop Version 1 Rev 2

Uplink Open Power Control Loop

UE monitors SIB messages for PCPICH Power (dBm)

Uplink Interference (dBm)

Constant Value (dB)

The UE then calculates:

PRACH initial power [dBm] = PcpichPower [dBm] — CPICH_RSCP [dBm] + UL interference + Constantvalue [dB]

UE also takes a measurement of CPICH_RSCP (dBm)

Example: PCPICH Power = 30dBm

CPICH_RSCP = -80dBm

UL interference = -85dBm

Constantvalue = -23dB (Set in ADD PRACHBASIC)

PRACH Initial Power = 30 – (-80) + (-85) + (-23) = 2dBm

The cell has a minimum receive level that it must receive the preamble, this is set by:

PreambleThd (Set in ADD PRACHBASIC)

UE then transmits the first preamble on the PRACH – from the previous slide example this would be at a power of 2dBm

Example: The recommended value for PreambleThd is 32 this converts to 16dB.

Preamble message sent on PRACH

UL Interference = -85dBm

Preamble threshold relative to the UL interference is -101dBm

The downlink pathloss from the previous slide was 110dB hence the NodeB should receive the UL preamble at a level of :

2 – 110 = -108dBm (assuming a balanced DL and UL)

Clearly outside the PreambleThd.

1st Preamble rxlev = -108dBm

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-9

USR7

Page 364: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink Open Power Control Loop

Uplink Open Power Control LoopIf the UE does not receive a positive or negative Acquisition Indicator (AI) in the AICH following thepreamble transmission, it repeats the preamble transmission up to a maximum number of times definedby the parameter PreambleRetransMax. During a preamble access cycle, the preamble transmissionpower level increments after every preamble transmission by a given amount specified by the parameter.PowerRampStep.The UE transmission power on PRACH must not exceed a maximum limit specified by the parameterMaxAllowedUlTxPower which can be set on a per cell basis. Furthermore, in case the preambletransmission power computed by the UE exceeds the maximum allowed power by 6 dB, the UE wouldabort the physical random access procedure [TS 25.214].If no Acquisition Indicator is received and decoded after maximum number of preamble transmissionattempts, the UE repeats entire procedure, but no more than number of times defined by parameterMmaxWhen the UE decodes a positive Acquisition Indicator it initiates the transmission of the randomaccess message part. The transmission of random access message starts after the defined number ofuplink access slots from the last transmitted preamble. The transmission delay is specified by OMCprovisionable parameter AICHTxTiming according to the following rule:

• If AICHTxTiming = 0 then transmission occurs after 3 access timeslots delay between PRACHaccess preamble part and AICH acknowledgement,

• If AICHTxTiming = 1 then transmission occurs after 4 access timeslots delay between PRACHaccess preamble part and AICH acknowledgement.

Transmission power level of control message information of DPCCH is set to the level of the lasttransmitted preamble increased by ΔPp-m offset, as defined by the PowerOffsetPpm parameter. Themessage transmission power offset may be expressed as:ΔPp-m [dB] = Pmessage-control [dBm] — PP[dBm]where:

• Pmessage-control — is message transmission power,• PP — is last preamble transmission power level

The UE transmission power on PRACH must not exceed a maximum limit specified by the per cell basisparameter MaxAllowedUlTxPower.The power level of data message part on PRACH channel with respect to the control message part isset by gain parameters GainFactorBetaC and GainFactorBetaD. [TS 25.214 section 5.1.2.5.1]

6-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 365: SYS202m2 Usr7 Ver1 Rev2

Uplink Open Power Control Loop Version 1 Rev 2

Uplink Open Power Control LoopOpen Loop Power Control Ramping

The number of times the UE may ramp up the power is set by the parameter PreambleRetransMax (ADD PRACHBASIC)

From the last slide the first preamble failed to achieve the threshold. The UE having received no response will ramped up the power.

Example:

PowerRampStep = 2dB

PreambleRetransMax = 20

2nd preamble power is increased by PowerRampStep (ADD PRACHBASIC)

UL Interference = -85dBm

Preamble threshold relative to the UL interference is -101dBm

1st Preamble rxlev = -108dBm

Preamble rxlev is now better than the threshold (-100dBm) after four power ramps and the procedure can now proceed.

UE power ramped up to 10dBm

The power level transmitted on the AICH is governed by the parameter:

AICHPowerOffset (ADD CHPWROFFSET) which is offset from the PCPICH.

On the last slide the preamble was accepted by the NodeB and the procedure can continueThe NodeB responds by returning the

signature sent by the preamble back on AICH

Example:

PCPICH = 30dBm

AICHPowerOffset = -12dB

Hence 30 -12 = 18dBm AICH transmission power

AICH transmission power = 18dBm

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-11

USR7

Page 366: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Related Data base Parameters

Related Data base ParametersThere are no MML commands specifically to set Open Loop Power Control. The required parametersare defined during the “Cell Setup" procedure, described in SYS202 Module 1 Chapter 6.The following table gives a summary of the related database parameters, and the controlling command inwhich they are configured. the Tag “3GPP" indicates that the parameter is a “Standard 3GPP parameter"and “Motorola" stands for a “Motorola implementation specific parameter".

Parameter Name Range Descriptions Controlling Command

PcpichPower • Value range: -10~ 50;

• Unit: dBm;• Step: 0.1.

• CommonPilot channeltransmittedpower level

ADD PCPICH

Constantvalue • Value range: -35~ -10;

• Units dB;• Step: 0.1

• Preamblesignal receptionthreshold usedto calculatethe transmitpower of the firstpreamble in therandom accessprocess

• 3GPP

ADD PRACHBASIC

PreambleThd • Value range:-36.0~0.0;

• Step 0.5;• Unit: dB• (0 : -36.0,

1 : -35.5,2 : -35.0, ...,72 : 0.0)

• This parameterdefines thepreamblethreshold of thePRACH. Thepreamble willbe confirmedonly when theratio betweenthe preamblepower receivedin the preambleperiod and theinterference islarger than thisthreshold.

ADD PRACHBASIC

6-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 367: SYS202m2 Usr7 Ver1 Rev2

Related Data base Parameters Version 1 Rev 2

Related Data base ParametersOpen Loop Power Control — AICHTxTiming = 0

4096 C hips 4096 C hips

P owerR ampS tep = 2dB

4096 C hips

P owerR ampS tep = 2dB

P owerOffs etP pm = 2dB

Min value = 3 Access s lots (15360 chips )

7680 C hips

Acq. Ind.

P re-

amble

Pre

am

ble

Pre

am

ble

3 Access s lots (15360 chips )

P R AC H acces s s lots T X at UE

AIC H acces s s lots R X at UE

t

t

One access s lot 5120 chips

One acces s s lot 5120 chips

Min value = 3 Access s lots (15360 chips )

AIC H P ower = 18dB m

R amped P reamble power = 10dB m

12

dB

m

Up to P reambleR etransMaxpreambles allowed

1. If no Acquis ition Indicator Acquis ition Indicator received then UE can repeat the whole procedure up to Mmax times .

2. If negative Acquis ition Indicator received, UE aborts access procedure

Mes s age P art

G ainF actorB etaC

G ainF actorB etaD

Max power set by:MaxAllowedUlT xP ower.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-13

USR7

Page 368: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Related Power Control Settings — Continued

Related Power Control Settings — Continued

Parameter Name Range Descriptions ControllingCommand

AICHPowerOffset • Value range: -22~ 5;

• Unit: dB;• Step: 0.1

• Differencebetween thetransmit powerPCPICH andeach of AICH.

• 3GPP

ADD CHPWROFFSET

PreambleRetransMax • Value range: 1 ~64;

• Step: 1

• Maximumnumber ofpreamblestransmitted ina preambleramping cycle.

• 3GPP

ADD PRACHBASIC

PowerRampStep • Value range: 1 ~8;

• Unit: dB• Step: 1

• Power step upto be applied bythe UE when aNon AcquisitionIndicator isreceived orwhen noacquisitionindicator at allis received.

• 3GPP

ADD PRACHBASIC

Mmax • Value range:1 ~32;

• Step: 1

• Maximumnumber ofrandom accesspreambleramping cycles

• 3GPP

ADD RACH

AICHTxTiming • Value range:0 or 1;

• The timeslotoffset betweenthe accesspreamble ofthe PRACHand AICHacknowledgement

• 3GPP

ADD AICH

6-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 369: SYS202m2 Usr7 Ver1 Rev2

Related Power Control Settings — Continued Version 1 Rev 2

Related Power Control Settings — ContinuedOpen Loop Power Control - AICHTxTiming = 1

4096 C hips 4096 C hips

P owerR ampS tep = 2dB

4096 C hips

P owerR ampS tep = 2dB

P owerOffs etP pm = 2dB

Min value = 4 Access s lots (20480chips )

12800 C hips

Acq. Ind.

P re-

amble

Pre

am

ble

Pre

am

ble

4 Access s lots (20480 chips )

P R AC H acces s s lots T X at UE

AIC H acces s s lots R X at UE

t

t

One access s lot 5120 chips

One acces s s lot 5120 chips

Min value = 4 Access s lots (20480 chips )

AIC H P ower = 18dB m

R amped P reamble power = 10dB m

12

dB

m

1. If no Acquis ition Indicator Acquis ition Indicator received then UE can repeat the whole procedure up to Mmax times .

2. If negative Acquis ition Indicator received, UE aborts access procedure

Up to P reambleR etransMaxpreambles allowed Mes s age P art

G ainF actorB etaC

G ainF actorB etaD)

Max power set by:MaxAllowedUlT xP ower.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-15

USR7

dqfr38
Text Box
This is for large cells > 30Km
Page 370: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Related Power Control Settings — Continued

Related Power Control Settings — Continued

Parameter Name Range Descriptions ControllingCommand

PowerOffsetPpm • Value range: -5~ 10;

• Unit: dB;• Step: 1

• Power offsetbetween thepreamble andthe messagepart of thePRACH

• 3GPP

ADD PRACHTFC

MaxAllowedUlTxPower • Value range: -50~ 33;

• Unit: dBm;• Step: 1

• Maximumallowed powerUE transmittedon RACH.

• 3GPP

ADD CELLSELRESEL

GainFactorBetaC • Value range:0~15;

• Step: 1

• UL DPCCH gainset up

• 3GPP

ADD PRACHTFC

GainFactorBetaD • Value range:0~15;

• Step: 1

• UL DPDCH gainset up

• 3GPP

ADD PRACHTFC

6-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 371: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Related Power Control Settings — Continued

This page intentionally left blank.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-17

USR7

Page 372: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink Open-Loop Power Control on DPCCH

Uplink Open-Loop Power Control on DPCCHThe UL open-loop power control on dedicated channel aims to determine the initial power of the firstuplink DPCCH.When setting up the first DPCCH, the UE shall start the UL inner loop power control at a power level andset the initial power of uplink DPCCH with the following formula:

where:

• DefaultConstantValue - is provided a per cell basis, by SET FRC.• CPICH_RSCP — is the UE measured CPICH pilot received signal code power.

Maximum Allowed UL Transmit PowerThe maximum allowed UL transmit power defines the total maximum output power allowed for the UEand depends on the desired type of service. The information will be transmitted on the FACH, mappedon the S-CCPCH, to the UE in the RADIO BEARER SETUP message of the RRC protocol during thecall setup.For Motorola, the MAX ALLOWED UE UL TX POWER parameter is the maximum transmit power of thePRACH channel when the UE tries to access to the specified cell. This parameter is altered by ADDCELLSELRESEL or MOD CELLSELRESEL.In addition, there are four parameters (MAX UL TX POWER OF CONVERSATIONAL SERVICE, MAXUL TX POWER OF STREAMING SERVICE, MAX UL TX POWER OF INTERACTIVE SERVICE andMAX UL TX POWER OF BACKGROUND SERVICE) which correspond to the maximum allowed transmitpower of four classes of services: conversational, streaming, interactive and background respectively.These are changed by ADD CELLCAC; MOD CELLCAC.

6-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 373: SYS202m2 Usr7 Ver1 Rev2

Uplink Open-Loop Power Control on DPCCH Version 1 Rev 2

Uplink Open-Loop Power Control on DPCCH

UL Initial P ower Level

DP C C H Initial_power = DP C C H P ower_offs et – C P IC H_R S C P

W here:

DP C C H power_offs et [dB m] = P cpichP ower [dB m] + UL interference + DefaultC ons tantV alue [dB ]

Let:

DefaultC onstantV alue = -27dB , P cpichP ower = 30dB m, UL interference = -80dB m

DP C C H power_offs et = 30 + (-80) + (-27) = -77dB m

Let:

C P IC H_R S C P = -80dB m

DP C C H initial_power = -77 – (-80) = 3 dB m

UE initially trans mits on 3 dB m

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-19

USR7

dqfr38
Text Box
We start this when the mobile sends RRC Setup complete on the Dedicated channel
Page 374: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Establishment of Uplink Closed Loop Power Control

Establishment of Uplink Closed Loop Power ControlIn the DL the NodeB will send a repeating bit pattern in the Transmit Power Control (TPC) bits. This isto allow uplink synchronization to take place.

Transmit Power Control in the UL DPCCH Power Control PreambleAn uplink DPCCH Power Control Preamble (PC Preamble) is a period of uplink DPCCH transmissionprior to the start of the uplink DPDCH transmission in order to ensure that the inner loop power control hasconverged when the transmission of the data bits begins. It consists of a given number of DPCCH slotstransmitted prior to the data transmission on DPDCH. The RNC transmits the PC Preamble parameter(number of DPCCH preamble slots) in the “Uplink DPCH power control info” IE using the RRC signalling.In addition to the PC Preamble delay, the mobile will not send any data on signalling radio bearers duringthe number of frames indicated in the “SRB delay” IE, sent through RRC signaling in the “Uplink DPCHpower control info” IE.Considering the application scenarios, different values for PC Preamble and SRB delay parameters areconfigured.

• In the case of RRC connection establishment, the length of PC preamble is zero frames and SRBdelay is seven frames.

• In the case of hard handover, the length of PC Preamble is 7 frames and SRB delay is 7 frames.Inner loop power control is thus applied on the DPCCH only, in a first time, starting from the initial DPCCHtransmit power determined by the open loop power control process. Then, once PC Preamble DPCCHslots have been transmitted and SRB delay slots passed, data starts to be transmitted on the DPDCH atan initial transmit power deduced from the current DPCCH transmit power and DPDCH/DPCCH powerdifference (using β c and βd gain factors).The uplink DPCCH and DPDCH(s) are transmitted on different codes. In order to meet a given QoSrequirement on the transport channels whatever the transport format they use, various power differencesbetween DPDCH and DPCCH are defined through gain factors, called βc for DPCCH and βd for DPDCH.These are predefined in the RNC.

6-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 375: SYS202m2 Usr7 Ver1 Rev2

Establishment of Uplink Closed Loop Power Control Version 1 Rev 2

Establishment of Uplink Closed Loop Power Control

UL Initial P ower Level

UE initially trans mits on 3dB m

DP C C HDP C C HDP C C H

pc P reamble number of frames sent on DP C C H before data can be sent on DP DC H (0 – R R C C onn E st)

Also S rbDelay delays the data sent on S R B 0 to 4 by a set number of frames (7 – R R C C onnE st)

pc P reamble number of frames sent on DP C C H before data can be sent on DP DC H (0 – R R C C onn E st)

Also S rbDelay delays the data sent on S R B 0 to 4 by a set number of frames (7 – R R C C onnE st)

DP DC HDP DC HDP DC H

Offset by B d from C ontrol C hannel B c

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-21

USR7

Page 376: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Open-Loop Power Control on Dedicated Channel (DPDCH)

Downlink Open-Loop Power Control on Dedicated Channel(DPDCH)

The aim of the DL open-loop power control on DPDCH is to determine the transmit power of the traffic(dedicated) channel based on the downlink measurement report of the UE. Both UE and UTRAN shalltake part in downlink open-loop power control on the DPDCH.The formula on the slide opposite is used to calculate the initial power of the DPDCH when a traffic(dedicated) channel is set up:The inputs to this formula are shown below:

• R is the requested data bit rate by the user.• W is the chip rate.• (Eb / N0)DL is the Eb/No target to ensure the service quality. In Motorola implementation, RNC

searches for a value of Eb/No target dynamically using a set of pre-defined values correspondingto the specific cell environment type, code type, coding rate and BLER target.

• (Ec/N0)CPICH is the ratio of received energy per chip to noise spectral density of CPICH receivedby UE.

• α is the orthogonality factor in the downlink. In the WCDMA system, orthogonal codes are employedin the downlink to separate the users, and without any multi-path propagation on the orthogonalityremains when the Node B signal is received by the mobile station. However, if there is sufficientdelay spread in the radio channel, part of the base station signals will be regarded as multiple accessinterference by the mobile station. The orthogonality of 0 corresponds to perfectly orthogonal users(set to 0).

• Ptotal is the carrier power measured at the NodeB and reported to the RNC.To prevent waste of downlink power while adding a new radio link to the active set, a power offsetadjustment for the new radio link is used. Based on the calculation used for calculating the initial transmitpower of the DPDCH, the power of the new radio link is decreased by a power offset, which is 15 dB. Thisdecrease is only available when the branch parameter DOWNLINK_POWER_BALANCE_SWITCH ofthe Power control algorithm switch parameter is set to ON.The downlink dedicated traffic channel is limited by an upper and lower limit for each radio link. Thislimitation is set through the RL MAX DL TX POWER and RL MIN DL TX POWER parameters. Bothparameters are provided a value for the different data rate of radio access bearers. So they correspondto a set of values rather than a single value. These are set for each RAB by ADD CELLRLPWR/MODCELLRLPWR.

6-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 377: SYS202m2 Usr7 Ver1 Rev2

Downlink Open-Loop Power Control on Dedicated Channel (DPDCH) Version 1 Rev 2

Downlink Open-Loop Power Control on Dedicated Channel(DPDCH)

⎟⎟⎟⎟⎟

⎜⎜⎜⎜⎜

⎟⎟⎠

⎞⎜⎜⎝

⎛⎟⎟⎠

⎞⎜⎜⎝

⎛= Total

CPICH

c

CPICH

DL

binitial P

NEP

NE

WRP a

0

0

R = user data rateW = chip rate

Downlink eb/no target – set by

R NP

C P IC H power

UE measured

E c/No

Downlink orthogonality

factor

Measured NodeB total

carrier power

DL Initial P ower Level

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-23

USR7

dqfr38
Text Box
-orthogonality factor is put to 0 in USR7. Eb/No is fixed in the Firmware by RNP HW.
Page 378: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inner-Loop Power Control

Inner-Loop Power Control

The Closed Power Control LoopThe closed loop power control algorithm adjusts transmit power based on power control informationfeedback provided by the receiving network entity, thus closing the power control system loop.In WCDMA, closed loop power control is implemented on both the uplink and the downlink, i.e. boththe Node B and the UE provide feedback to each other and both use that feedback to adjust their owntransmit power. Closed loop power control comprises two different mechanisms:

• Inner loop power control• Outer loop power control

The outer loop is responsible for setting a Signal to Interference Ratio (SIR) target for a physical channel,or to be more precise, on the DPCCH. Such a target should be computed so that the QoS requirementsof the services carried over that physical channel are met. Typically (but not exclusively) the outer loopensures that a given average BLER target is met.

NOTEMultiple transport channels, each carrying a service with its own QoS requirement, can bemultiplexed on the same physical channel.

The inner loop power control is specified in the 3GPP specifications and mandatory for the Node B andthe UE. The principle is very simple: the receiver measures the SIR on the DPCCH (typically, but notexclusively, on the dedicated pilot bits) and compares that measured SIR with the SIR target determinedby the outer loop power control. If the measured SIR is less than the target SIR, the receiver sends a“power up” command to the transmitter, otherwise it sends a “power down” command. Such commandsare represented by the TPC bits in the DPCCH which are sent in every time slot.The outer loop power control algorithm is not specified in the 3GPP specifications and is a proprietaryalgorithm. But it is important to note that the 3GPP specifications state that the UTRAN is responsiblefor the uplink outer loop power control and that the UE is responsible for the downlink outer loop powercontrol. Therefore the UTRAN has no control over the downlink power control and this will vary with eachUE vendor.

6-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 379: SYS202m2 Usr7 Ver1 Rev2

Inner-Loop Power Control Version 1 Rev 2

Inner-Loop Power Control

S IR (DL)

S IR target

(DL)

S IR (UL)

S IR target

(UL)

S IR es t > S IR target

T P C command is set to ‘0’

S IR es t <= S IR target

T P C command is set to ‘1’

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-25

USR7

dqfr38
Text Box
SIR-UL is build in the firmware in SHO SHO the rate is 500 TPC/s instead of 1500 TPC/s due to cell should send 3 times the TPC.
Page 380: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Uplink Inner-Loop Power Control

Uplink Inner-Loop Power ControlUplink inner-loop power control is used to control the power of the uplink radio links. In fact, uplinkinner-loop power control is executed on the DPCCH, and related DPDCH transmit power is calculatedfrom DPCCH transmit power according to DPDCH/DPCCH power ratio (βd /βc).The RNC sends the SIR target to the NodeB and then the NodeB compares the estimated SIR with theSIR target of uplink DPCCH pilot symbol once every timeslot.

• If the estimated SIR is greater than the SIR target, the NodeB sends a TPC command “down” tothe UE on the downlink DPCCH TPC field.

• Otherwise, the NodeB sends a TPC command "Up".Note:

• The "Up" command means TPC = 1 and the "Down" command means TPC = 0.• For the SIR = RSCP / ISCP * SF

– The Received Signal Code Power (RSCP) is unbiased measurement of the received poweron one code.

– The Interference Signal Code Power (ISCP) is the interference on the received signal, andSF= the spreading factor used on the DPCCH.

The following describes the uplink inner-loop power control:

Single Radio LinkThere are two types of inner-loop PCA algorithm: PCA1 and PCA2. The RNC configures the PCAalgorithm based on the POWER CONTROL ALGORITHM SELECTION parameter (SET FRC).

• PCA1: UE adjusts uplink transmit power for each slot; the step of PCA1 should be 1dB or 2dB byUL CLOSED LOOP POWER CONTROL STEP SIZE parameter (SET FRC).

• PCA2: The UE adjusts the uplink transmit power for each 5-slot cycle and the step is 1 dB fixedly.

6-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 381: SYS202m2 Usr7 Ver1 Rev2

Uplink Inner-Loop Power Control Version 1 Rev 2

Uplink Inner-Loop Power Control

UL Initial P ower Level

UE initially trans mits on 3 dB m

DP C C HDP C C HDP C C H

S IR (UL)

S IR target

(UL)

S IR es t >= S IR target

T P C command is set to ‘0’

S IR est < S IR target

T P C command is set to ‘1’

If P wrC trlAlg = ALG OR IT HM1 (recommended)

T hen has UL step s ize can be 1dB or 2dB depending on the value of:

UlT pcS tepS ize (1dB recommended)

If received T P C value is equal to 0 then T P C _cmd for that s lot is -1

If received T P C value is equal to 1 then T P C _cmd for that s lot is 1

TPC_cmd TPCDPCCH ×Δ=Δ

UL Initial P ower Level

UE initially trans mits on 3 dB m

DP C C HDP C C HDP C C H

S IR (UL)

S IR target

(UL)

S IR es t >= S IR target

T P C command is set to ‘0’

S IR est < S IR target

T P C command is set to ‘1’

If P wrC trlAlg = ALG OR IT HM2

T hen has UL step s ize can only be 1dB

If all 5 hard decis ions within a set are 0 then T P C _cmd for that s lot is -1 in the 5th s lot

If all 5 hard decis ions within a set are 1 then T P C _cmd for that s lot is 1 in the 5th s lot

Otherwise, T P C _cmd = 0 in the 5th s lot

TPC_cmd TPCDPCCH ×Δ=Δ

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-27

USR7

Page 382: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Downlink Inner Loop Power Control

Downlink Inner Loop Power ControlThe Downlink Closed Inner Power Control algorithm resides in UE and it starts by comparing receiveddownlink SIR estimates with initial SIR target value.At physical channel establishment, the UE sets an initial downlink target SIR value based on the receivedIEs "DCH quality target" - BLER.The UE measures the SIR on a slot-by-slot basis comparing the measured SIR to its target value. If thetarget SIR is greater than SIR estimate then the UE transmits power up command (TPC) bits into theuplink Dedicated Physical Control Channel (DPCCH), otherwise the UE instructs the NodeB to decreaseits transmitted power level inserting power down TPC command bits.The Node B decodes the TPC bits and increases or decreases transmit downlink power, by a given step,starting from beginning of the next time slot. The power step size is defined by the FddTpcDlStepSizeparameter.

NOTESince the TPC bits are not coded (against errors over the radio channel) they are subject to errors,hence it is possible for the Node B to change its transmit power in the wrong direction. Howeverthe error rate on the TPC bits must be kept reasonably small for the system to operate efficiently,say around 4%. This is achieved by setting correctly the power ratio between the DPCCH and theDPDCH (beta_c and beta_d gains, respectively).

The frequency of power adjustments depends on the DPC mode selection, which is defined by theparameter value DpcMode (SET FRC). The DL power control mode operates according to the followingscheme:

• If DPC mode flag is set to “SINGLE_TPC" then transmitted power change occurs at the beginningof the next time slot after reception of new TPC command, which results from power control rate of1500Hz.

• If DPC mode flag is set to “TPC_TRIPLET_IN_SOFT" then transmit power change occur at thebeginning of next time slot after reception 3 consecutive TPC commands. In this case power controlrate is decreased to 500Hz (for SHO to prevent power deviation).

• If DPC mode flag is set to “TPC_AUTO_ADJUST” then an automatic adjustment mode is used ,indicating that the value of DPC_MODE can be modified by sending the ACTIVE SET UPDATEmessage to the UE.

When the UE is in soft handover (with different Node Bs), each Node B in the active set adjusts itstransmit power according to the procedure described in TS 25.214 section 5.2.1.2.2 and downlink powerbalancing. Since each Node B might decode the TPC command sent by the UE either correctly orincorrectly, the radio link transmit power of the different Node Bs in the active set can drift apart. Thisissue is addressed by the downlink power balancing algorithm..In the case of softer handover, i.e. when the UE is connected to more than one cell in the same Node B,the radio links associated with the same connection are managed by the same Node B which combinesthe TPC commands received from each link and formulates a unified decision.

6-28 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 383: SYS202m2 Usr7 Ver1 Rev2

Downlink Inner Loop Power Control Version 1 Rev 2

Downlink Inner Loop Power Control

S IR (DL)

S IR target

(DL)

S IR es t >= S IR target

T P C command is set to ‘0’

S IR es t < S IR target

T P C command is set to ‘1’

Data

T P CT F C

Data

PIL

OT

Data

T P CT F C

Data

PIL

OT

S IR target

adjusted within UE based on target B LE R for service user data rate

Dpc Mode:

S ING L E _TP C – P ower changes at the beginning of the next timeslot after reception of T P C command.

TP C _TR IP L E T_IN_S OF T – P ower change occurs at the beginning of the next timeslot after 3 consecutive T P C commands

TP C _AUT O_ADJ US T – Auto adjustment made via AC T IV E S E T UP DAT E message

P ower step s ize DL set by F ddT pcDlS tepS ize

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-29

USR7

Page 384: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Outer Loop Power Control

Outer Loop Power ControlThe aim of outer-loop power control is to maintain the communication quality at the level required by theservice bearer through adjustment of the SIR target. This control acts on each DCH belonging to thesame RRC connection.The SIR target needs to be adjusted when the UE speed or the multi-path propagation environmentchanges, so that the communication quality can maintain the same. If a fixed SIR target is selected, theresulting quality of the communication might be too low or too high, which may cause an unnecessarypower rise in most situations.The downlink outer-loop power control is implemented in the UE. Therefore, this algorithm isUE-manufacturer specific. The information signaled to the UE by the RNC is a quality target for eachradio bearer, expressed as a BLER target. Then, depending on the mobile-manufacturer specificouter-loop algorithm, an initial SIR target value may be deduced from this BLER value and then regularlyupdated or not.

Uplink Outer-Loop Power ControlThe uplink quality is observed after macro diversity selection combining in the RNC. Therefore, uplinkouter-loop power control is performed in the SRNC.The SRNC compares the RX BLER with the BLER target. If the RX BLER is greater than the BLERtarget, the SRNC increases the SIR target; otherwise, decreases.After adjusting the SIR target, the SRNC sends the new SIR target through FP frames to all NodeBs foruplink inner loop power control.The uplink outer-loop power control for all UEs can be deactivated by OLPC_SWITCH; or by setting SIRADJUSTMENT STEP to zero to deactivate uplink outer loop power control for different services.SET CORRMALGOSWITCHOLPC_SWITCH — 0,1 (OFF,ON)Default 1When it is ON, RNC will update the uplink SIR TARGET of RLs on the NODEB side by IUB DCH FPsignals.The initial SIR target value is provided by the RNC to the NodeB through the SIR INIT TARGET VALUEparameter which is service-dependent. This value is transmitted to the NodeB using NBAP signaling ateach RADIO LINK SETUP or RADIO LINK RECONFIGURATION PREPARE.These parameters are pre-configured.

6-30 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 385: SYS202m2 Usr7 Ver1 Rev2

Outer Loop Power Control Version 1 Rev 2

Outer Loop Power Control

R NCR NC NodeB

S et B LE R targets

S IR target setting

Outer loop

B LE R meas urement and

comparingS IR meas urement

and comparing

Inner loop

UE

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-31

USR7

Page 386: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 SIR Target Adjustment

SIR Target AdjustmentThe outer-loop power control adjusts SIR target through a OLPC ADJUSTMENT PERIOD parameter asshown below:

Where:

• i is the ith transmission channel.• n is the nth adjustment period.• SIRtar(n) is the SIR target used by the nth adjustment period which could be set by parameter

OLPC ADJUSTMENT PERIOD.• MAX is the maximum value in the total i transmission channels.• BLERmeas(n,i) is the instantaneous BLER measured for the ith transmission channel in the nth

adjustment period.• BLERtar(i) is the BLER target of the ith transmission channel, which could be set by parameter

SERVICE DCH_BLER TARGET VALUE.• Step(i) is the adjustment step of the ith transmission channel, which could be set by parameter SIR

ADJUSTMENT STEP.• Factor is the adjustment factor which could be set by parameter SIR ADJUSTMENT COEFFICIENT.

The principles to adjust SIR target in case of multi-services are described as follows:

• The maximum value of SIR target among multiple services is used for the SIR target adjustment.• If one of the services requires increasing the SIR target, the maximum value is used for the

adjustment in the increase.• Only when all the services require reducing the SIR target, the maximum value is used for the

adjustment in the decrease.The parameters that effect this feature are found in the command SET OLPC and are listed below.SirConvergeThd — Value range: 0 ~ 63.Physical value range: 0 ~ 31.5; step: 0.5.Physical unit: dB.Content: Exception in the link when the difference between the SIR measurement value and the SIRtarget value exceeds the threshold.Recommended value: 6.SirErrReportHyst — Value range: 1 ~ 6000.Physical value range: 10 ~ 60000; step: 10.Physical unit: ms.Content: Hystersis time after the SIR converge threshold is triggered. It is used to avoid ping-pong effect.Recommended value: 8.SirAdjustFactor — Value range: 1 ~ 10.Physical value range: 0.1 ~ 1; step: 0.1.Physical unit: None.Content: It is used to adjust the best OLPC step corresponding to different cells when the OLPC algorithmis given.Recommended value: 10.

6-32 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 387: SYS202m2 Usr7 Ver1 Rev2

SIR Target Adjustment Version 1 Rev 2

SIR Target Adjustment

)((i)BLERtarget

(i)BLERtarget - BLER . tepSirAdjustS .actor SirAdjustFMax SIR meas(i) Tar(n) dB⎥

⎤⎢⎣

⎡⎟⎟⎠

⎞⎜⎜⎝

⎛=Δ

SIR (UL)

SIRtarget

(UL)

Both values have recommended

setting of 1Calculates a -/+ ratio between measured BLER and target

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-33

USR7

Page 388: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 DL Power Balancing

DL Power BalancingDuring soft handover, the UL TPC command is demodulated in each RLS and due to demodulationerrors, the DL transmit power of the each branch drift separately, which causes loss to the macro-diversitygain.During the softer handover, the difference between the initial transmit power of added link and existinglink may also cause the power drift. The DL Power Balance (DPB) algorithm is introduced to reduce thepower drift between links during the soft handover and the softer handover.The power balancing procedures aim at correcting any drift of transmit power between the different NodeBs of a UE’s active set, these drifts being due to different errors on TPC commands on each radio link.The instantaneous adjustments of DL transmitted power on different radio links in the active set canresult in imbalance of DL transmitted power, due either to poor quality TPC received from the UE, ormisalignment between the power levels of existing radio links in active set and the initial DL transmittedpower associated with a newly added radio link. This “Power Drift" may cause either an increased levelof DL interferences, or the dropping of radio links and, obviously decreases system capacity.The power adjustment is a cyclic process repeated with the period given by parameter AdjustPeriodcorresponding to the number of N radio frames of length 10 ms.The RNC initiates DL power balancing adjustment whenever, in a measurement report period of lengthgiven by parameter RptPeriod x 10mS radio frames, the following condition is detected:

and procedure stops when:<

The parameters that effect the algorithms on this page are found in the command SET DPB and arelisted below.RptPeriod — Value range: 1 ~ 6000.Physical value range: 10 ~ 60000; step: 10.Physical unit: ms.Content: Downlink power measurement period.Recommended value: 70.DPBStartThd — Value range: 0~255.Physical value range: 0 ~ 127.5; step: 0.5.Physical unit: dB.Content: Downlink power balance trigger threshold.Recommended value: 6.DPBStopThd — Value range: 0~255.Physical value range: 0 ~ 127.5; step: 0.5.Physical unit: dB.Content: Downlink power balance stop threshold.Recommended value: 0.DefaultCPICHPower — Value range: -100 ~ 500.Physical unit: dBm.Content: default power of the CPICH.Recommended value: 33.

6-34 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 389: SYS202m2 Usr7 Ver1 Rev2

DL Power Balancing Version 1 Rev 2

DL Power Balancing

Scrambling Code A

Scrambling Code BTPC bits

corruptedTPC bits correct

Area of

inter

feren

ce

DL power drifting apart Say 27dBm

DL power drifting apart Say 21dBm

Pmax – Pmin >= DPBStartThd let DPBStartThd = 6 (dB)

27 – 21 >= 6

6 >= 6 (yes)

Pmax – Pmin =< DPBStopThd let DPBStopThd = 0 (dB)

Downlink Power Balancing stopped when each power is equal

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-35

USR7

dqfr38
Callout
To protect from PW drift in SHO area
Page 390: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Power Balancing — Continued

Power Balancing — ContinuedIn order to reduce unfavourable drift of DL transmit power on different radio links, the power balancingadjustment procedure is applied. This procedure is mostly defined in the 3GPP specifications 25.214 and25.433. and is superimposed on the inner loop power control. It estimates and provides to the Node B,downlink power correction Pbal(k), which adjusts radio link transmission powers in the active set towarda common reference power level.Based on TPC commands received from UE, the Node B estimates the TPCest commands to be 0 or 1and updates the power every slot (DPC_MODE = 0). NodeB adjusts the current downlink power P(k-1)to a new power P(k) according to the following formula:

where:

• PTPC(k) - the k:th is power adjustment due to the inner loop power control [TS 25.433 section 8.3.7;TS25.214 section 5.2.1.2.2]

• Pbal(k) — is k:th power correction result from power balance adjustment algorithm.• k - is successive timeslot number.

The power correction within one adjustment period cannot exceed either the value given by maximalDL power balancing adjustment step set by the MaxAdjustStep parameter or the value of maximal DLrelative channel power defined by RLMaxDlTxPwr parameter.The parameters that effect the algorithms on this page are found in the command SET DPB and arelisted below.MaxAdjustStep — Value range: 1 ~ 10.Physical unit: Slot.Content: The maximum adjustment step should not exceed 1dB during downlink radio link poweradjustment within the time specified by this parameter.Recommended value: 4.AdjustPeriod — Value range: 1 ~ 256.Physical unit: frame.Content: DPB adjustment period.Recommended value: 2.RatioForMaxPower — Value range: 0 ~ 100.Physical value range: 0 ~ 1.step: 0.01.Physical unit: None.Content: Ratio of the maximum power in calculation of reference power for downlink power balance.Recommended value: 50.

6-36 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 391: SYS202m2 Usr7 Ver1 Rev2

Power Balancing — Continued Version 1 Rev 2

Power Balancing — Continued

Pref = a(Pmax – PCPICHmax) + (1 - a) x (Pmin – PCPICHmin)

Let:

a = RatioForMaxPower (recommended value = 50, physical value 0.5)

PCPICHmax = 30

PCPICHmin = 30

Pref = 0.5(27 – 30) + (1 - 0.5) x (21 – 30)

Pref = -1.5 + (-4.5) = -6dB

∑ ±+= 0.5dB ofaccuracy an with )P -P r)(P - (1 P init CPICH refbal

Let:

r = AdjustRatio (recommended value = 0)

For leg with 27dBm power output:

Pbal = 1(-6 + 30 -27) = -3dB (power down by -3dB)

For leg with 21dBm power output:

Pbal = 1(-6 + 30 -21) = 3dB (power up by 3dB)

Note:

The value of the power step cannot exceed the value set by MaxAdjustStep (recommended value = 4dB) with the frame period set by AdjustPeriod (recommended value = 2 frames)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

6-37

USR7

dqfr38
Callout
RSCP of the Best
dqfr38
Callout
RSCP of the worst
Page 392: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Power Balancing — Continued

This page intentionally left blank.

6-38 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 393: SYS202m2 Usr7 Ver1 Rev2

Handover Control Version 1 Rev 2

Chapter 7

Handover Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-1

USR7

Page 394: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Handover Control

This page intentionally left blank.

7-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 395: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter Objectives

• Describe the intra-frequency handover procedure• Describe the inter-frequency handover procedure• Describe the inter-RAT handover procedure• Describe the HCS handover procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-3

USR7

Page 396: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Introduction to Handover Control

Introduction to Handover ControlThe handover function in UTRAN manages the mobility of the UE and the radio interface. It is based onradio measurements and cell topology and it is used to maintain the Quality of Service requested by theCore Network regardless of UE mobility. USR3.0 supports the following handover types:

• Intra-frequency soft, softer and hard handover,• Inter-frequency hard handover• Inter-RAT hard handover in both CS and PS domains.

In addition, the procedures may be intra-RNC or inter-RNC and may require the performance of SRNSrelocation.The decision on what handover type needs to be performed depends on a number of conditions andparameters that are presented in the following sections. In general, soft/softer handover has higherpriority than intra-frequency hard handover and inter-frequency and inter-RAT HHO only occurs in bordercells that have inter-frequency or inter-RAT neighbouring cells set accordingly.Three different handover causes are supported in USR7.0:

• Handover due to coverage• Handover due to overload — Load control• Handover due to QoS — Rate control• Handover due to speed.

7-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 397: SYS202m2 Usr7 Ver1 Rev2

Introduction to Handover Control Version 1 Rev 2

Introduction to Handover Control

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-5

USR7

dqfr38
Callout
Link Stability
Page 398: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Measurement Control

Measurement ControlThe handover algorithm also controls the measurement reporting performed by the UE in CELL_DCHstate for handover purposes. The MEASUREMENT CONTROL message is used to set up and modify theway measurements are taken by the UE. The contents and frequency of the MEASUREMENT REPORTmessages from the UE depends on the measurement type, the UE state and its measurement capability.The list of cells that the UE must monitor is divided into three different categories.

• Active Set: Group of UTRAN cells which the UE has a radio link established to, i.e. it is insoft/softer handover with. The Active Set contains only UTRAN cells that operate on the sameUMTS frequency. In USR3.0 the maximum number of cells in the Active Set is fixed to 3. Thisis a hard coded parameter in USR3.0.

• Monitored Set: Cells that are not currently in the Active Set, but the UE is monitoring for handoveraccording to a neighbour list assigned by UTRAN (stored as CELL_INFO_LIST in the UE). TheMonitored Set may contain UTRAN and GSM cells and the UTRAN cells may be under differentUMTS frequencies. The maximum number of cells to measure in USR3.0 is: 32 intra-frequency,32 inter-frequency and 32 inter-RAT cells.

• Detected Set: Cells that are not included in the neighbour list to monitor but are detected by theUE on its own. The UE only reports detected UTRAN cells that are under the same frequency asthe active cells and only when in CELL_DCH state. The purpose is to provide information to thenetwork operator for manually updating the neighbour cell list of cells.

Monitored List DeterminationThe best cell in the active set to control the monitored list. The strategy is as follows:

• If there is only one cell in the active set, use its neighbour list to build the monitored set list.• If there is more than one cell in the active set use the neighbour list of the best cell to build the

monitored set list.• If a 1D event is received, indicating a new best cell, use the neighbour list of the new best cell to

build the monitored set list.• If the best cell is removed, use the neighbour list of the best cell amongst those left in the active set

at that time in order to build the new monitored list.The parameter that sets the maximum number of neighbours in the Active Set is found in the commandADD CELLINTRAFREQHO and is shown below.MaxCellInActiveSet — Value range: 1~6Physical unit: noneContent: The maximum number of cells in the active set. This parameter is decided by systemspecification. Modification is not suggested.Recommended value: 3For E-DCH the maximum number of cells in the active set is configured in the command SET HOCOMMand is described below.MaxEdchCellInActiveSet — Value range: 1~4Physical unit: noneContent: Max number of links in the EDCH active set. When this RNC acts as the SRNC, the numberof all links in the EDCH active set for the UEs cannot exceed this parameter. If this parameter is toolarge, great amount of resources at the RAN side will be occupied in that the same data is transferredby multiple EDCH links in macro diversity, thus affecting the system performance; if this parameter istoo small, repeated transmission occurs in that insufficient combination gain can be achieved in the softhandover area by the EDCH, which affects the UE speed rate.Recommended value: 3

Detected Set ManagementThe purpose of Detected Set Management is to utilize the detection capabilities of the UE and provideinformation for the operator to manually update the neighbour cell list of cells. This can be accomplishedby recording the number of times a given cell is detected and the identity of the cells that were in theactive set when a given cell is detected.

7-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 399: SYS202m2 Usr7 Ver1 Rev2

Measurement Control Version 1 Rev 2

Measurement Control

Monitored Set

Detected Set

Detected Set

Detected Set

Detected Set

Active Set

Active Set

Active Set

Monitored Set

Monitored Set

Monitored Set

Monitored Set

Monitored Set

Monitored Set

Monitored Set

Monitored Set

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-7

USR7

Page 400: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Measurement Type

Measurement TypeThe same type of measurements may be used as input to different functions in UTRAN. Hence, theUE must support a number of measurements running in parallel (see TS 25.133). Also, the UE mustprovide support such that each measurement is controlled and reported independently of every othermeasurement. There are different types of measurements defined in the standards; the following aresupported in USR7.0.

• Intra-frequency measurements: Measurements on downlink physical channels with the samefrequency as the active set.

• Inter-frequency measurements: Measurements on downlink physical channels at frequenciesthat differ from the frequency of the active set.

• Inter-RAT measurements: Measurements on downlink physical channels belonging to anotherradio access system than UTRAN, e.g. GSM.

• UE Internal measurements: Only measurements of UE Rx-Tx time difference for radio linksynchronisation, i.e. 6F/6G events .

UE traffic volume measurements are also supported and used in the DCCC algorithm. Inter-carrierload balancing algorithm is based on Node B transmit carrier power measurements, as detailed in “CellOriented Algorithm Parameter Configuration"In the remainder of the discussion on measurements, only information pertaining to intra-frequency,inter-frequency and inter-RAT measurements will be covered since these are used to process handoverdue to poor radio link quality.

Measurement Reporting ModeThe measurement reporting mode associated with a specific measurement indicates when aMEASUREMENT REPORT message is sent by the UE to the UTRAN and whether or not the UEexpects an acknowledgement. The two measurement reporting modes are:

• Event Driven• Periodic

In general, periodic reports are sent in RLC unacknowledged mode and event-triggered reports in RLCacknowledged mode. This information is given to the UE in the IE “Measurement Reporting Mode"contained in the MEASUREMENT CONTROL message.

7-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 401: SYS202m2 Usr7 Ver1 Rev2

Measurement Type Version 1 Rev 2

Measurement Type

Measurement Types

• Intra-frequency Measurements• Inter-frequency Measurements• Inter-RAT Measurements• UE Internal Measurements

Measurement Modes

• Event Driven• Periodic

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-9

USR7

Page 402: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Intra-frequency Event Driven Measurement Reporting Criteria

Intra-frequency Event Driven Measurement Reporting CriteriaIntra-frequency handover is based on event-triggered reporting. However, for events 1A and 1C,when a cell that triggered the reporting is not used to update the active set, the UE reverts toperiodic reporting until UTRAN receives and processes these events. The amount-of-reporting(PeriodMRReportNumfor1x) and reporting-interval (ReportIntervalfor1x) parameters in the commandADD CELLINTRAFREQHO set the attributes of this periodic reporting mechanism.PeriodMRReportNumfor1A — Value range: D1, D2, D4, D8, D16, D32, D64 and infinityPhysical value range: 1, 2, 4, 8, 16, 32, 64 and infinityPhysical unit: timeContent: The number of 1A event periodic reports. When the number of 1A event periodical reportsexceeds this parameter value, periodic reporting comes to an end.Recommended value: D16ReportIntervalfor1A — Value range: NON_PERIODIC_REPORT, D250, D500, D1000, D2000, D4000,D8000 and D16000Physical value range: NON_PERIODIC_REPORT, 250, 500, 1000, 2000, 4000, 8000 and 16000Physical unit: msContent: 1A event reporting period. Generally the 1A event is reported only once. However, to avoidmeasurement report loss, event 1A event reporting can be turned into periodic reporting.Recommended value: D4000PeriodMRReportNumfor1C — Value range: D1, D2, D4, D8, D16, D32, D64 and infinityPhysical value range: 1, 2, 4, 8, 16, 32, 64 and infinityPhysical unit: timeContent: The number of 1C event periodic reports. When the number of 1C event periodic reportsexceeds this parameter value, periodic reporting comes to an end.Recommended value: D16ReportIntervalfor1C — Value range: NON_PERIODIC_REPORT, D250, D500, D1000, D2000, D4000,D8000 and D16000Physical value range: NON_PERIODIC_REPORT, 250, 500, 1000, 2000, 4000, 8000 and 16000Physical unit: msContent: 1C event reporting period. Generally 1C event is reported for only once. However, to avoidmeasurement report loss, 1C event can be turned to periodic reporting.Recommended value: D4000PeriodMRReportNumfor1J — Value range: D1, D2, D4, D8, D16, D32, D64, InfinityPhysical value range: 1, 2, 4, 8, 16, 32, 64, InfinityPhysical unit: noneContent: This parameter specifies the number of reporting times of event 1J for periodical reporting.When the actual reporting times exceeds the set value, the periodical reporting ends.Recommended value: D64ReportIntervalfor1J — Value range: NON_PERIODIC_REPORT (no periodical reporting), D250, D500,D1000, D2000, D4000, D8000, D16000Physical value range: no periodical reporting, 250, 500, 1000, 2000, 4000, 8000, 16000Physical unit: ms.Content: This parameter specifies the number of reporting times of event 1J for periodical reporting. Thatis, event 1J is reported at each reporting interval. Usually, event 1J is reported only once. Nevertheless,if the cell, where event 1J is reported, does not join the EDCH active set in a specified period of time, theUE can change the reporting of event 1J into periodical mode.to avoid missing of measurement reports.The event 1J of this cell is reported for PeriodMRReportNumfor1J times with the reporting period asthe set value.Recommended value: D1000

7-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 403: SYS202m2 Usr7 Ver1 Rev2

Intra-frequency Event Driven Measurement Reporting Criteria Version 1 Rev 2

Intra-frequency Event Driven Measurement Reporting Criteria

Event Event Description

Event 1a A Primary CPICH enters the Reporting Range.

Event 1b A Primary CPICH leaves the Reporting Range.

Event 1c A Non-active Primary CPICH becomes better than an active Primary CPICH

Event 1d Change of best cell

Event 1j RAN10.0 provides the solution to the issue of how to add an HSUPA cell in a DCHactive set to an E-DCH active set. Event 1J is added to the 3GPP protocol. This eventis triggered when a non-active E-DCH but active DCH primary CPICH becomes betterthan an active E-DCH primary CPICH.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-11

USR7

dqfr38
Callout
New in USR7
Page 404: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Cell Individual Offsets

Cell Individual OffsetsThe behaviour of intra-frequency, inter-frequency and inter-RAT measurement reporting can be modifiedby assigning an offset to each cell that is monitored. The offset can be either positive or negative.The UE receives the cell individual offset for each monitored cell in the measurement object field of theMEASUREMENT CONTROL message.This offset (dB) is added to the measurement quantity before the UE evaluates if an event has occurred ina way that measurement reports are triggered when primary CPICH plus the corresponding offset fulfilsthe reporting criteria. The mechanism provides the network with an efficient tool to change the reportingof an individual cell. For instance, by applying a positive offset, the UE will send measurement reportsas if the primary CPICH is offset x dB better than actually measured. This parameter is actually part ofan algorithm which will be explained for each event.Cell individual offsets can be set on a per neighbour basis for intra-frequency, inter-frequencyand inter-RAT measurements with the parameter CIOOffset of the ADD INTRAFREQCELL, ADDINTERFREQCELL and ADD GSMNCELL commands). On a serving cell basis the command CIO isfound in the command ADD CELLSETUP.

7-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 405: SYS202m2 Usr7 Ver1 Rev2

Cell Individual Offsets Version 1 Rev 2

Cell Individual Offsets

UTRAN Sends "Cell Individual Offset" ValueTo UE, Via "MEASUREMENT CONTROL"Message

UE Reports "Actual Measurement +/-"Cell Individual Offset" value

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-13

USR7

Page 406: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Events 1A

Events 1AEvent 1A enable then the addition of cells to the active set according to a relative dynamic criteriongiven by 3GPP TS 25.331 (but note that for a cell to be added to the active set following a 1A eventthe reported quality must exceed an absolute threshold, SHOQualmin). The criteria for cell additionis fulfilled when the signal strength (EcNo) of a new cell is good enough compared to the best cell (ingeneral to all cells in the active set), i.e. the candidate cell measurement is within a threshold below thebest cell measurement.The addition window of cells in event 1A is configured with the reporting range constant parameterIntraRelThdFor1ACSVP/IntraRelThdFor1ACSNVP/ IntraRelThdFor1APS (dependant on whether theservice is CS video phone, CS non video phone or PS), together with the hysteresis and time to triggerparameters.

Event 1A Triggering FormulaEvent 1A is triggered on the basis of the formula shown on the slide opposite.Where:

• MNew is the measurement value of the cell in the reporting range.• CIONew is Cell offset of the cell in the reporting range. It is set for the neighboring cell. Set in

ADD/MOD INTRAFREQCELL• W is the weighted value. The total quality of the best cell and the active set is weighted by the

Weighted factor parameter. Set in SET INTRAFREQHO / ADD CELLINTRAFREQHO / MODCELLINTRAFREQHO.

• Mi is the measurement value of the cell in the active set.• MBes is the measurement value of the best cell in the active set.• R1a is the reporting range or the relative threshold of soft handover. The threshold parameters

of the CS and PS services are CS service 1A event relative threshold, PS service 1A eventrelative threshold respectively. Set in SET INTRAFREQHO / ADD CELLINTRAFREQHO / MODCELLINTRAFREQHO.

• H1a is 1A hysteresis, the hysteresis value of event 1A. Set in SET INTRAFREQHO / ADDCELLINTRAFREQHO / MOD CELLINTRAFREQHO.

7-14 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 407: SYS202m2 Usr7 Ver1 Rev2

Events 1A Version 1 Rev 2

Events 1A

)2/(log.10).1(.10.log10 111

aabest

N

iinewnew HRMWMLogWCIOM

A

−−−+⎥⎦

⎤⎢⎣

⎡≥+ ∑

=

Calculation of general reporting level of all cells in active set shown as threshold curve in the graph

Calculation of reporting level of cell in the monitored set

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-15

USR7

Page 408: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Events 1A

Events 1AThe parameters are defined in the ADD CELLINTRAFREQHO command and are listed below.IntraRelThdFor1ACSVP/IntraRelThdFor1ACSNVP/ IntraRelThdFor1APS — Value range: 0~29Physical value range: 0~14.5 with the step size of 0.5Physical unit: dBContent: Relative threshold of the 1A event.Recommended value: 7Hystfor1A — Value range: 0~15Physical value range: 0~7.5 with the step size of 0.5Physical unit: dBContent: The hysteresis value of the event 1A. This parameter value is related to the slow fadingcharacteristic. The higher this parameter is set, the less ping-pong effect and misjudgement can becaused. However, the less likely that will be triggered in time.Recommended value: 0TrigTime1A — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: msContent: The trigger delay time of the event 1A. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the smaller the misjudgement probability, but the lowerthe response speed of the event to the measured signal changes.Recommended value: D320SHOQUALMIN — Value range: -24~0Physical unit: dbContent: minimum quality threshold for soft handover.Recommended value: -24Weight — Value range: 0~20Physical value range: 0~2 with the step size of 0.1

Physical unit: None.

Content: This parameter is used to define the soft handover relative threshold based on the measuredvalue of each cell in the active set. The greater this parameter is set, the higher the soft handover relativethreshold. When this parameter is set as 0, the soft handover relative threshold is only for the best cellin the active set.Recommended value: 10

7-16 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 409: SYS202m2 Usr7 Ver1 Rev2

Events 1A Version 1 Rev 2

Events 1A

Best Cell in Active Set

TrigTime1A (320ms)

Event 1A if active set contains two or less

Add Monitored cell to active set

Threshold Curve

Cell in the monitored

set

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-17

USR7

Page 410: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Event 1B

Event 1BEvents 1B enabled then the deletion of cells to the active set according to a relative dynamic criteriongiven by 3GPP TS 25.331.The drop window of cells in event 1B is set with the reporting range constant parameterIntraRelThdFor1BCSVP/IntraRelThdFor1BCSNVP/IntraRelThdFor1BPS in USR7.0. .

Event 1B Triggering FormulaEvent 1B is triggered on the basis of the formula shown on the slide opposite.Where:

• MOld is the measurement value of the cell in the reporting range.• CIOOld is Cell offset of the cell in the reporting range. It is set for the neighboring cell. Set in

ADD/MOD INTRAFREQCELL• W is the weighted value. The total quality of the best cell and the active set is weighted by the

Weighted factor parameter. Set in SET INTRAFREQHO / ADD CELLINTRAFREQHO / MODCELLINTRAFREQHO.

• Mi is the measurement value of the cell in the active set.• MBes is the measurement value of the best cell in the active set.• R1b is the reporting range or the relative threshold of soft handover. The threshold parameters

of the CS and PS services are CS service 1B event relative threshold, PS service 1B eventrelative threshold respectively. Set in SET INTRAFREQHO / ADD CELLINTRAFREQHO / MODCELLINTRAFREQHO.

• H1b is 1B hysteresis, the hysteresis value of event 1B. Set in SET INTRAFREQHO / ADDCELLINTRAFREQHO / MOD CELLINTRAFREQHO.

The parameters are defined in the ADD CELLINTRAFREQHO command and are listed below.IntraRelThdFor1BCSVP/IntraRelThdFor1BCSNVP/IntraRelThdFor1BPS — Value range: 0~29Physical value range: 0~14.5 with the step size of 0.5Physical unit: dBContent: Relative threshold of the 1B event.Recommended value: 12Hystfor1B – Value range: 0~15Physical value range: 0~7.5 with the step size of 0.5Physical unit: dBContent: The hysteresis value of the event 1B. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the less ping-pong effect and misjudgement can becaused. However, the less likely that the event will be triggered in time.Recommended value: 8TrigTime1B – Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10,20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: msContent: The trigger delay time of the event 1B. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the smaller the misjudgement probability, but the lowerthe response speed of the event to the measured signal changes.Recommended value: D640

7-18 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 411: SYS202m2 Usr7 Ver1 Rev2

Event 1B Version 1 Rev 2

Event 1B

)2/(log.10).1(.10.log10 111

bbbest

N

iioldold HRMWMLogWCIOM

A

−−−+⎥⎦

⎤⎢⎣

⎡≤+ ∑

=

C alculation of general reporting level of all cells (if calculated, usually best cell only) in active set shown as threshold curve in the graph

C alculation of reporting level of cell in the active set

Best Cell in Active Set

TrigTime1B (640ms)

Event 1B

Delete cell from active set

Threshold Curve

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-19

USR7

Page 412: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Event 1C

Event 1CEvent 1C occurs when one of the non-active pilots surpasses an active set pilot, regardless of itsabsolute strength (but note that for a cell to be added to the active set following a 1C event the reportedquality must also exceed an absolute threshold, SHOQualmin). The hysteresis and time to triggerparameters described previously control this cell addition mechanism. In addition, the parameterReplacement_Activation_Threshold (hard-coded to 3 in USR3.0) sets the minimum size of the activeset required for this event to be triggered.

Event 1C AlgorithmEvent 1C is triggered on the basis of the formula shown in the slide opposite.Where:

• MNew is the measurement value of the cell in the reporting range.• CIONew is Cell offset of the cell in the reporting range.• MInAS is the measurement value of the worst cell in the active set.• CIOInAS is Cell offset of the worst cell in the active set.• H1c is 1C hysteresis, the hysteresis value of event 1C.

The parameters are defined in the ADD CELLINTRAFREQHO command and are listed below.Hystfor1C — Value range: 0~15Physical value range: 0~7.5 with the step size of 0.5Physical unit: dBContent: The hysteresis value of the event 1C. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the less ping-pong effect and misjudgement can becaused. However, the less likely that the event will be triggered in time.Recommended value: 8TrigTime1C — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: msContent: The trigger delay time of the event 1C. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the smaller the misjudgement probability, but the lowerthe response speed of the event to the measured signal changes.Recommended value: D640

7-20 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 413: SYS202m2 Usr7 Ver1 Rev2

Event 1C Version 1 Rev 2

Event 1C

2/.10log10 1cInASInASnewnew HCIOLogMCIOM ++≥+

Calculation of worst cell in the active set Calculation of reporting level of cell in the monitored set

Active Set A

Active Set B

Active Set C

Monitored Cell

Event 1C triggered if active set has 3 cells

TrigTime1C (640ms)

Replace Active Set Cell C with Monitored Cell

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-21

USR7

Page 414: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Event 1D

Event 1DEvent 1D is used to keep track of the best cell at all times. The triggering condition for this event iscompletely defined by the hysteresis and time to trigger parameters.

Event 1D AlgorithmThe algorithm for event 1D is shown on the slide opposite. The CIO offsets are included in the algorithmdefined in the 3GPP specifications but are not used in this implementation.Where:

• MNotBest is the measurement value of a cell that is not on the list of the best cells.• MBest is the measurement value of the best cell in the active set.• H1d is 1D hysteresis, the hysteresis value of event 1D.

The parameters are defined in the ADD CELLINTRAFREQHO command and are listed below.Hystfor1D — Value range: 0~15Physical value range: 0~7.5 with the step size of 0.5Physical unit: dBContent: The hysteresis value of the event 1D. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the less ping-pong effect and misjudgement can becaused. However, the less likely that the event will be triggered in time.Recommended value: 8TrigTime1D — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: msContent: The trigger delay time of the event 1D. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the smaller the misjudgement probability, but the lowerthe response speed of the event to the measured signal changes.Recommended value: D640

7-22 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 415: SYS202m2 Usr7 Ver1 Rev2

Event 1D Version 1 Rev 2

Event 1D

2/log.10log10 1DbestNotBest HMM +≥

Calculation of best cell in active set Calculation of other cell in active set

Best Cell in Active Set

Active set cell B

Active set cell C Event 1D

TrigTime1D (640ms)

Change of ‘Best Cell’

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-23

USR7

Page 416: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Event 1J

Event 1JThis event is triggered when a non-active E-DCH but active DCH primary CPICH becomes better thanan active E-DCH primary CPICH.

Event 1J AlgorithmEvent 1J is triggered on the basis of the formula shown on the slide opposite.Where:

• MNew is the measurement result of the cell not included in the E-DCH active set but included in DCHactive set.

• CIONew is the individual cell offset for the cell not included in the E-DCH active set but included inDCH active set becoming better than the cell in the E-DCH active set if an individual cell offset isstored for that cell. Otherwise, it equals 0.

• MInAS is the measurement result of the cell in the E-DCH active set with the lowest measurementresult.

• CIOInAS is the individual cell offset for the cell in the E-DCH active set that is becoming worse thanthe new cell.

• H1J is the hysteresis parameter for event 1J.• If the measurement result is CPICH-Ec/No, MNew and MInAS are expressed as ratios.• If the measurement result is CPICH-RSCP, MNew and MInAS are expressed in mW.

The figure in the slide shows the first measurement report is sent when primary CPICH D becomesbetter than primary CPICH B. The "cell measurement event result" of the measurement report containsthe information of primary CPICH D and CPICH B.On the assumption that the E-DCH active set has been updated after the first measurement report(E-DCH active set is now primary CPICH A and primary CPICH D), the second report is sent whenprimary CPICH C becomes better than primary CPICH A. The "cell measurement event result" of thesecond measurement report contains the information of primary CPICH C and primary CPICH A.

Database ParametersThe parameters that control the event 1J are found in the command ADD CELLINTRAFREQHO and aredescribed below.TrigTime1J — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560, D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000Physical unit: ms.Content: This parameter specifies the time delay to trigger event 1J. The value of this parametercorrelates with slow fading. The larger the value of this parameter, the lower probability of incorrectdecision, but the slower the response of event to the change of measured signals. The purposes of thetime-to-trigger mechanism are as follows: Reducing the number of wrong event reports caused by burstsignals. Inhibiting the ping-pong handover to some extent. Reducing the influence of shadow fading onevent decisions. The hysteresis can effectively reduce the average number of handovers and wrongdecisions, and avoid unnecessary handovers. As for the impact on network performance: The largerthe value of this parameter, the smaller the average number of handovers, and the greater the possibilityof call drops. The TS 25.133 V3.6.0 protocol prescribes that the intra-frequency measurement physicallayer updates the measurement result once every 200 ms, so the time to trigger shorter than 200 msis invalid. The time-to-trigger parameter should be close to a multiple of 200 ms. The UE at differentrates may react differently to the hysteresis value for the event. For the fast-moving UE, the call droprate is more sensitive to the hysteresis value, whereas for the slow-moving UE, the call drop rate isless sensitive to the hysteresis value. This can also reduce ping-pong handovers or wrong handovers.Therefore, for the cell with most of the fast-moving UEs, this parameter can be set smaller, whereas forthe cell with most of the slow-moving UEs, this parameter can be set larger.Recommended value: D640HystFor1J — Value range: 0~15Physical value range: 0~7.5, step: 0.5Physical unit: dBContent: This parameter specifies the hysteresis value for event 1J. The value of this parametercorrelates with slow fading. The larger the value of this parameter, the less possibility of ping-pong effector wrong decision. But the event might not be triggered in time. For the definition, refer to 3GPP TS25.331. The value of this parameter is ranged from 2 dB to 5 dB. In addition, this parameter is relatedto filter coefficient and trigger delay. As for the impact on network performance: For the UE that enters

7-24 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 417: SYS202m2 Usr7 Ver1 Rev2

Event 1J Version 1 Rev 2

Event 1Jthe SHO area, increase of the hysteresis means decrease of the SHO area. But for the UE that leavesthe SHO area, that means enlarging of the SHO area. If the number of UEs entering the area and thenumber of UEs leaving the area are equal, the real SHO ratio will not be affected. The larger the valueof this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pong effectcan be resisted, but the varying of the signal in response to the handover algorithm becomes slower.Recommended value: 8

2/.10log10 1 jInASInASnewnew HCIOLogMCIOM ++≥+

C alculation of reporting level of cell in the monitored set

C alculation of worst cell in the active set

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-25

USR7

Page 418: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Intra-frequency Handover

Intra-frequency Handover

Algorithm DescriptionThe figure opposite shows the scenario where a mobile moves from one cell to another. It can be seenthat in CDMA there is blur zone where the mobile can be connected to both cells, maximizing the qualityof service. This is often referred to as Soft or Softer Handover.The handover control function for soft handover is responsible of the following tasks.

• Determining whether a soft handover is necessary.• Receiving intra-frequency measurement reports from UEs (intra-frequency measurement results

and information about intra-frequency events that triggered the measurement report), which mayrefer to Node Bs under the same or different RNCs.

• Deciding whether to add any of these reported cells to the active set or drop any of the cells fromthe active set (adding or deleting the radio links)

• When radio links are added, splitting/combining or splitting/selection functions in the appropriatenetwork elements are also instructed to begin diversity processing with the new radio link.

Intra-frequency Reporting EventsSoft handover algorithms rely on setting up intra-frequency events 1A through 1D to triggerMEASUREMENT REPORT messages at the UE.This section describes the most relevant soft handover parameters as per event type (1A, 1B, 1C, D),but before several concepts are introduced below.The parameter that decides whether soft and softer handovers are allowed is set in the SET HOCOMMcommand and is listed below.DivCtrlField — Value range: MAY, MUST, MUST_NOTPhysical value range: MAY, MUST, MUST NOTPhysical unit: noneThe indicator for the Node B to do softer combination. If it's set to "MAY", the Node B can decide whetherto do softer combination (the softer combination can be done for the radio links in different cells in thesame Node B). If it's set to "MUST", the Node B is forced to do softer combination for the radio links indifferent cells. If it's set to "MUST NOT", the Node B is not allowed to do softer combination.Recommended value: MAY

7-26 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 419: SYS202m2 Usr7 Ver1 Rev2

Intra-frequency Handover Version 1 Rev 2

Intra-frequency Handover

Cell CCell A

• The UE has a radio connection with cell A• The UE has a radio connection with cell A

Cell B

• When the UE established an additional radio connection with Cell B this is called a softer handover

• When the UE established an additional radio connection with Cell B this is called a softer handover

• When the UE establishes an additional radio connection with Cell C this is a soft handover even when Cell C is located under a different RNC

• When the UE establishes an additional radio connection with Cell C this is a soft handover even when Cell C is located under a different RNC

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-27

USR7

Page 420: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Soft Handover Processing

Soft Handover Processing

Description of SHO MethodThe diagram opposite shows the processing flow of event measurement reports by the soft handoveralgorithm. The algorithm makes use of intra-frequency reporting events 1A, 1B, 1C, 1D and 1J only.Hence, a cell is added to the active set when an event 1A is received (provided the active set is not full),and a cell is deleted from the active set when an event 1B is received (provided the active set is notempty).In addition, cells are also added to the active set on the reception of events 1C or 1D triggered by amonitored cell (not in the active set). In any case, before adding a cell to the active set, radio resourceshave to be successfully reserved, i.e. radio admission control and OVSF code allocation have to besuccessful.When the active set is full, the algorithm relies on event 1C to replace an active set cell with a bettermonitored cell and on event 1D to keep track of the best cell in the active set. When the best cell changes,a new monitored list is built and a MEASUREMENT CONTROL message sent to the UE to communicatethe neighbour list and also update any parameters to the settings of the new best cell.

Softer HandoverThe decision on whether an added radio link should be soft combined with existing radio links at the NodeB or whether the new added radio link should be treated as a new SHO leg, is usually left to the Node B.This is achieved by setting the Diversity Control field in the NBAP RL ADDITION REQUEST message to“may". Then it is up to the Node B to decide whether the current radio link is combined with the alreadyexisting radio links. However, USR7.0 allows the modification of this behaviour on a per RNC basis bysetting the parameter DivCtrlField differently.

7-28 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 421: SYS202m2 Usr7 Ver1 Rev2

Soft Handover Processing Version 1 Rev 2

Soft Handover Processing

Enter CELL_DCH

Receive MeasReport

AS< 3

No

CAC& ICAC

Reject Leg

ADD LEG

AS> 1DROP LEG

Event 1B

Event 1A

Yes

Yes

No

Change Best Cell

Event 1D

NewMonitored setNew SHO paramsMeas Ctrl msg

AS< 3CAC& ICAC

ADD LEG

Yes

Accept Leg

Accept Leg

Reject Leg

REPLACE LEG

Add newcellDelete worse cellAS Update msg

AS = AS- 1AS Update msg

AS = AS + 1AS Update msg

AS = AS + 1AS Update msg

Event 1C/1J

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-29

USR7

Page 422: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Intra-frequency Hard Handover

Intra-frequency Hard HandoverAlthough soft/softer handover is the preferred procedure to handle RRC connection mobility in USR3.0,there are times when only a hard handover can be performed. The hard handover procedure removesall the RL(s) in the active set and establishes new RL(s). An intra-frequency hard handover is onlyperformed when one of the following conditions apply.

• There is no Iur interface between the source and target RNC.• The UE is using a PS RAB at a bit rate above a preset threshold BEBitRateThd.

If one of the conditions described above holds, intra-frequency hard handover is performed on thereception of 1D events. Then the handover criteria is controlled by the parameters Hystfor1D andTrigTime1D. Once the hard handover is executed, the monitored set becomes the neighbour list of thenew best cell.The parameter BEBitRateThd, gives the operator the possibility to handle best effort services with bitrates above certain threshold in hard handover. This is to avoid employing too many valuable resources(OVSF codes, Node B power, etc) on radio bearers and coverage areas for which the system has notbeen designed.The question of whether it is more efficient to operate data calls (above certain rate) in hard handoveror in soft handover has been made with a comparison of 64/64 and 32/144 RABs in both soft and hardhandover. From the point of view of interference and downlink power consumption, in HHO it is expectedhigher power to be transmitted from one cell, whereas in SHO lower power is expected to be transmittedfrom more than one cell. This increases the probability of reaching the maximum power per code inthe case of HHO as it can be seen in opposite for that case of a 64/64k data service with and withoutsoft handover. On the other hand, from an OVSF code and backhaul point of view, it is obviously moreefficient to operate high data rate services in HHO as less resources are consumed.The balance between hard/soft handover and resource utilisation is closely linked to the guaranteedservice coverage given by the operator. During cell planning, the network is normally designed to havevoice coverage in all the cell area, and also for data services up to a certain rate (usually 64 kbps). Then,for services with a higher rate, coverage can only be achieved if soft handover is used, as otherwisethe maximum power per code is hit systematically. Then, for even higher rate services, only very limitedcoverage is possible within the cell, irrespective of whether SHO is enabled or not. A rule of thumb is toset BEBitRateThd to the maximum bit rate with guaranteed cell coverage.The parameter that effects this feature is found in the SET HOCOMM command is shown below.BEBitRateThd — Value range: D8, D32, D64, D128, D144, D256, D384Physical value range: 8k, 32k, 64k, 128k, 144k, 256k, 384kPhysical unit: bpsThe bit rate threshold used to determine whether to perform soft handover for the Best Effort (BE)service. When the maximum bit rate of the BE service is lower than or equal to this threshold, thesystem will perform soft handover for this user to guarantee the service quality. If the maximum bit rateof the BE service is higher than the threshold, the system will perform intra-frequency hard handover forthis user to avoid the too great effect of soft handover on the system capacity.Recommended value: D64

7-30 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 423: SYS202m2 Usr7 Ver1 Rev2

Intra-frequency Hard Handover Version 1 Rev 2

Intra-frequency Hard Handover

• A hard handover occurs when the UE has to release the old radio links before it establishes a radio connection with a new cell

Cell A

Cell BCell B

Occurs on 1D (change of best cell) event when:

1. There is no Iur interface between the source and target RNC2. The UE is using a BE PS RAB at a bit rate above a preset threshold BEBitRateThd

(64k)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-31

USR7

Page 424: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-frequency Hard Handover

Inter-frequency Hard Handover

Overview of Inter-Frequency Hard HandoverBased on handover triggering causes, inter-frequency handover includes the following types:

• Inter-frequency handover based on coverage The UE might leave the coverage of the currentfrequency during the movement of the UE. In this case, the RNC needs to trigger an inter-frequencyhandover based on coverage to avoid call drop.

• Inter-frequency handover based on load To balance the loads between inter-frequency concentriccells, the RNC would choose some UEs to do inter-frequency handover according to user andservice priorities.

• Inter-frequency handover based on speed When the Hierarchical Cell Structure (HCS) is used,cells are divided into different layers according to their coverage. Macro cell corresponds tolarge coverage and low priority and Micro cell corresponds to small coverage and high priority.Inter-frequency handover can be triggered by UE speed estimation algorithm of the HCS. The UEwith high speed is handed over to a cell with larger coverage to reduce the frequency of handover,while the UE with low speed is handed over to a cell with smaller coverage and larger capacityto improve the system capacity.

Handover Triggering ConditionsThe inter-frequency handover triggering conditions are as follows:

Inter-frequency Handover Type Triggering Conditions

Handover based on coverage UE Reporting of event 2D orperiodically measurement reporting.When receiving event 1F, the RNC will decideto try a blind handover to inter-frequency cell ifa blind handover neighboring cell is available.Note: Blind handovers only used in specificstrategic areas.

QoS-based inter-frequency handover According to the Link Stability Control Algorithm,the RNC needs to trigger the QoS-basedinter-frequency handover to avoid call drops.

Handover based on load Load could be shared by inter-frequency cells.Estimation decision from Load Reshuffling(LDR) Algorithm Module.

Handover based on estimation decision of theUE speed in HCS

Estimation decision of the UE speed in HCS

The parameters that effect these are found in the ADD CELLHOCOMM and are listed below.INTERFREQHOSWITCH — Value range: INTER_FREQ_COV, INTER_FREQ_COV_NCOV,INTER_FREQ_TA.Content: Type of inter-frequency handover supported by the cell.INTER_FREQ_COV: coverage-based inter-frequency handover.INTER_FREQ_COV_NCOV: coverage-based inter-frequency handover, and non-coverage-basedinter-frequency handover triggered by speed estimation.INTER_FREQ_TA: traffic-based inter-frequency handover, which includes the function similar tocoverage-based inter-frequency handover.Recommended value: INTER_FREQ_COV.

7-32 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 425: SYS202m2 Usr7 Ver1 Rev2

Inter-frequency Hard Handover Version 1 Rev 2

Inter-frequency Hard Handover

f1 f2

• Handover bas ed on c overage

• QoS -bas ed inter-frequenc y handover

• Handover bas ed on load

• Handover bas ed on s peed

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-33

USR7

Page 426: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Coverage-Based Inter-Frequency Handover Procedure

Coverage-Based Inter-Frequency Handover ProcedureThe following flowchart shows the four phases of coverage-based inter-frequency handover.The four phases are described in the list below:

• In the triggering phase– The RNC notifies the UE to measure through an inter-frequency measurement control

message. If the quality of the pilot signal in the current cell deteriorates, the CPICH Ec/Noor CPICH RSCP of the UMTS cell that the UE accesses is lower than the correspondingthreshold, and the UE reports event 2D.

• In the measurement phase– If the RNC receives a report of event 2D, the RNC requests the NodeB and UE to start

compressed mode to measure the qualities of inter-frequency neighboring cells, and the RNCsends an inter-frequency measurement control message. In the measurement phase, themethod of either periodical measurement report or event-triggered measurement report canbe used.

• In the decision phase– After the UE reports event 2B, the RNC performs the handover. Otherwise, the UE periodically

generates measurement reports, and the RNC makes a decision after evaluation.• In the execution phase

– The RNC executes the handover procedure.

7-34 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 427: SYS202m2 Usr7 Ver1 Rev2

Coverage-Based Inter-Frequency Handover Procedure Version 1 Rev 2

Coverage-Based Inter-Frequency Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-35

USR7

Page 428: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 QoS-Based Inter-Frequency Handover Procedure

QoS-Based Inter-Frequency Handover ProcedureThe flowchart shows the four phases of QoS-Based inter-frequency handover.The four phases are described in the list below:

• In the triggering phase– If the service quality of the current cell deteriorates, the Link Stability Control Algorithm makes

a handover measurement decision.• In the measurement phase

– The RNC requests the NodeB and the UE to start compressed mode to measure the qualitiesof inter-frequency neighboring cells. Then, the RNC sends an inter-frequency measurementcontrol message. In the measurement phase, the method of periodical measurement report orevent-triggered measurement report can be used.

• In the decision phase– After receiving the event 2B measurement reports of CPICH RSCP and CPICH Ec/No of the

inter-frequency cell, the RNC performs the handover. Otherwise, the UE periodically generatesmeasurement reports, and the RNC makes a decision after evaluation.

• In the execution phase– The RNC executes the handover procedure.

7-36 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 429: SYS202m2 Usr7 Ver1 Rev2

QoS-Based Inter-Frequency Handover Procedure Version 1 Rev 2

QoS-Based Inter-Frequency Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-37

USR7

Page 430: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load-Based Inter-Frequency Handover Procedure

Load-Based Inter-Frequency Handover ProcedureThe following figure shows the three phases of load-based inter-frequency handover.The three phases are described in the list below:

• In the triggering phase– The Load Reshuffling (LDR) module directly determines whether the current cell is overloaded

and whether an inter-frequency handover needs to be performed. The LDR module providesthe target cell information for the current cell, and the RNC performs the handover procedure.

• In the decision phase– The RNC decides to trigger an inter-frequency blind handover if the conditions are met.

◊ If the inter-frequency blind handover can be triggered, the RNC enters the decision phase.◊ If the inter-frequency blind handover cannot be triggered, the RNC does not perform the

handover.– After the inter-frequency handover is triggered, the RNC chooses a decision algorithm

according to whether the conditions of direct blind handover are met.◊ If the conditions of direct blind handover are met, the RNC performs an inter-frequency

blind handover.◊ If the conditions of direct blind handover are not met, the RNC initiates a measurement,

and then, if all the conditions are met, the RNC performs the handover.• In the execution phase

– The RNC performs the blind handover according to the decision result.

7-38 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 431: SYS202m2 Usr7 Ver1 Rev2

Load-Based Inter-Frequency Handover Procedure Version 1 Rev 2

Load-Based Inter-Frequency Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-39

USR7

dqfr38
Text Box
No CM -> Blind HO
Page 432: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Speed-Based Inter-Frequency Handover Procedure

Speed-Based Inter-Frequency Handover ProcedureThe following flowchart describes the procedure of the inter-frequency handover based on HCS speedestimation.The four phases are described in the list below:

• In the triggering phase– The RNC receives the handover request according to the HCS speed estimation. The handover

based on HCS speed estimation is of two types: handover from the macro cell to the micro celland handover from the micro cell to the macro cell. For different types of handover, the RNCacts differently.

• In the measurement phase– If the handover is performed from a macro cell to a micro cell, the RNC sends an inter-frequency

measurement control message.– If the handover is performed from a micro cell to a macro cell, the RNC directly performs blind

handover, ignoring the measurement procedure.• In the decision phase

– After the UE reports event 2C, the RNC performs the handover decision.• In the execution phase

– The RNC initiates the handover procedure.◊ If the handover is performed from a micro cell to a macro cell and the target cell of blind

handover is configured, the RNC performs blind handover to the target cell.◊ If the blind handover fails or the handover is performed from a macro cell to a micro

cell, the RNC starts the inter-frequency (or inter-RAT) measurement procedure. If theinter-frequency measurement mode is employed, the RNC performs the inter-frequencyhandover procedure to the cell with the best quality after receiving event 2C from the UE.

7-40 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 433: SYS202m2 Usr7 Ver1 Rev2

Speed-Based Inter-Frequency Handover Procedure Version 1 Rev 2

Speed-Based Inter-Frequency Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-41

USR7

Page 434: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-frequency Handover Measurement

Inter-frequency Handover MeasurementOnce a 2D event is received by UTRAN for load based inter frequency handovers, the UE is instructedto perform either periodic or event-triggered monitoring of FDD cells on different frequencies, dependingon the setting of the flag InterFreqReportMode

Periodic ReportingIn the case of periodic reporting, the interval for periodic measurements is set in thePeriodReportInterval attribute. On the reception of a 2F event, periodic inter-frequency reportingis disabled.

Event Triggered ReportingIn the case of event-triggered reporting, the UE is requested to report 2B events. This will also be disabledon reception of a 2F event.The parameters that decides whether to use periodic or event triggered reporting is found in the ADDCELLINTERFREQHOCOV command and are listed below.INTERFREQREPORTMODE — Value range: Periodical_ reporting, Event_trigger.Physical unit: None. Content: Inter-frequency measurement reporting mode. "Periodical_reporting"represents periodical reporting mode. "Event_trigger" represents event-triggered reporting mode.Recommended value: Periodical_reporting.INTERFREQMEASQUANTITY — Value range: CPICH_Ec/No, CPICH_RSCP.Physical unit: None.Content: Measurement item used in coverage-based inter-frequency measurement in event (2B/2D/2F)triggered and periodical reporting modes.Recommended value: CPICH_RSCP.PeriodReportInterval — Value range: , D250, D500, D1000, D2000, D4000, D8000, D16000, D20000,D24000, D28000, D32000 and D64000Physical value range: 250, 500, 1000, 2000, 4000, 8000, 16000, 20000, 24000, 28000, 32000 and64000Physical unit: msContent: Inter-frequency measurement reporting period.Recommended value: D500

Speed Based HandoversThe RNC starts the inter-frequency measurement or inter-system measurement for a UE after thehandover based on HCS speed estimation is triggered. After receiving a event 2C report message, theRNC decides to initiate an inter-frequency handover.Note: The event 2B/2D/2F or periodical measurement in inter-frequency handover can use CPICHEc/N0 or RSCP as the measurement quantity. The parameter is configured as Inter-frequency measurequantity. The event 2C only uses CPICH Ec/N0 as the measurement quantity.

7-42 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 435: SYS202m2 Usr7 Ver1 Rev2

Inter-frequency Handover Measurement Version 1 Rev 2

Inter-frequency Handover Measurement

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-43

USR7

Page 436: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Calculation of Qused

Calculation of QusedEvents 2D, 2F, 2B and 2C use a measured quality of either the serving cell or the neighbour cell. Thisis can be calculated by either taking the best cell in the active set or a combination of all the cells in theactive set, or some point in between. The algorithm that decides which method to use is shown on theslide opposite and the inputs are listed below.Qcarrierjis the logarithmic form of the estimated quality value of frequency jMcarrier j is the estimated quality value of frequency jMi j is the measurement result of cell i with the frequency of j in the virtual active setNA j is the number of cells with the frequency of j in the virtual active setMBest j is the measurement result of the best cell with the frequency of j in the virtual active setWj is the weight factorThe parameters that effect this are found in the command ADD CELLINTERFREQHOCOV and are listedbelow.WEIGHTFORUSEDFREQ — Value range: 0~20Physical value range: 0~2; step: 0.1Physical unit: NoneContent: The weighted factor required for comprehensive quality calculation of the used frequency. Thegreater this parameter is set, the higher the comprehensive quality of the active set. When this parameteris set as 0, the comprehensive quality of the active set refers to the quality of the best cell in the set.Recommended value: 0

7-44 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 437: SYS202m2 Usr7 Ver1 Rev2

Calculation of Qused Version 1 Rev 2

Calculation of Qused

jBestj

N

ijijjcarrierjcarrier LogMWMLogWLogMQ

jA

⋅⋅−+⎟⎟⎠

⎞⎜⎜⎝

⎛⋅⋅=⋅= ∑

=

10)1(10101

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-45

USR7

Page 438: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering Events 2D and 2F

Triggering Events 2D and 2FEvents 2D and 2F are used to start and stop compressed mode respectively. The triggering mechanismsfor these events are described below.

Triggering Event 2DEvent 2D algorithm is shown on the slide opposite.Where:

• QUsed is the measured quality of the cell that uses the current frequency.• TUsed2d is the absolute quality threshold of the cell that uses the current frequency. Based on the

service type (CS , PS domain R99 service, or PS domain HSPA service) and measurement quantity(CPICH Ec/No or RSCP), this threshold can be configured through one of the following parameters:– Inter-freq CS measure start Ec/No THD– Inter-freq R99 PS measure start Ec/No THD– Inter-freq H measure start Ec/No THD– Inter-freq CS measure start RSCP THD– Inter-freq R99 PS measure start RSCP THD– Inter-freq H measure start RSCP THDFor the PS and CS combined services, the threshold is set to the higher one of CS or PS services.If the UE has only signaling connections currently, the thresholds for CS services are used.

• H2d is the event 2D hysteresis value 2D hysteresis.After the conditions of Event 2D are fulfilled and maintained until the 2D event trigger delay time isreached, the UE reports the Event 2D measurement report message.Note: Inter-freq H measure start Ec/No (RSCP) THD is valid only when OVERLAY_SWITCH in thecommand SET CORRMALGOSWITCH is set to ON. Otherwise, the PS domain R99 and HSPA serviceswill take Inter-freq R99 PS measure start Ec/No (RSCP) THD as a measurement event threshold.

Triggering Event 2FEvent 2F algorithm is shown on the slide opposite.Where:

• QUsed is the measured quality of the cell that uses the current frequency.• TUsed2f is the absolute quality threshold of the cell that uses the current frequency. Based on the

service type (CS , PS domain R99 service or PS domain HSPA service) and measurement quantity(CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:– Inter-freq CS measure stop Ec/No THD– Inter-freq R99 PS measure stop Ec/No THD– Inter-freq H measure stop Ec/No THD– Inter-freq CS measure stop RSCP THD– Inter-freq R99 PS measure stop RSCP THD– Inter-freq H measure stop RSCP THD

• H2f is the event 2F hysteresis value 2F hysteresis.After the conditions of Event 2F are fulfilled and maintained until the 2F event trigger delay time isreached, the UE reports the Event 2F measurement report message.

7-46 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 439: SYS202m2 Usr7 Ver1 Rev2

Triggering Events 2D and 2F Version 1 Rev 2

Triggering Events 2D and 2F

2/22 ddusedused HTQ −≤

Event 2D

2/22 FFusedused HTQ −≤Event 2F

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-47

USR7

Page 440: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Parameters for Events 2D and 2F

Triggering Events 2D and 2FParameters for Events 2D and 2F

The parameter to decide which thresholds to use for 2D and 2F if using both inter-freq and inter-RAT arefound in the commands ADD CELLHOCOMM or SET HOCOMM and is described below.COEXISTMEASTHDCHOICE — Value range: COEXIST_MEAS_THD_CHOICE_INTERFREQ,COEXIST_MEAS_THD_CHOICE_INTERRAT.Content: Type of event 2D/2F measurement thresholds when inter-frequency and inter-RAT adjacentcells coexist.COEXIST_MEAS_THD_CHOICE_INTERFREQ: Event 2D/2F measurement thresholds forinter-frequency measurement.COEXIST_MEAS_THD_CHOICE_INTERRAT: Event 2D/2F measurement thresholds for inter-RATmeasurement.Recommended value: COEXIST_MEAS_THD_CHOICE_INTERFREQ.The parameter that effects whether the InterFreq thresholds are used to trigger 2d and 2f are set in theSET CELLINTERFREQHOCOV or ADD CELLINTERFREQHOCOV command and are listed below.InterFreqCSThd2DEcN0/InterFreqR99PsThd2DEcN0/InterFreqHThd2DEcN0 — Threshold to triggerinter-frequency measurement with measurement quantity of Ec/No for CS domain services, PS domainnon-HSPA services and PS domain HSPA services respectively.Value range: -24~0Physical unit: dBContent: Threshold to trigger inter-frequency measurement with measurement quantity of Ec/No for CSdomain services.Recommended value (default value): -14InterFreqCSThd2FEcN0/InterFreqR99PsThd2FEcN0/InterFreqHThd2FEcN0 — Value range: -24~0Physical unit: dBContent: Threshold to stop inter-frequency measurement with measurement quantity of Ec/No for CSdomain services, PS domain non-HSPA services and PS domain HSPA services respectively .Recommended value: -12Note: Thresholds can also be set for RSCP.HYSTFOR2D — Value range: 0~29.Physical value range: 0~14.5; step: 0.5.Physical unit: dB.Content: Event 2D trigger hysteresis. This parameter value is related to the slow fading characteristic.The greater this parameter is, the less the ping-pong effect and misjudgment that can be caused.Recommended value: 6.HYSTFOR2F — Value range: 0~29Physical value range: 0~14.5; step: 0.5Physical unit: dBContent: The hysteresis value of the event 2F. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the less ping-pong effect and misjudgement can becaused. Recommended value: 6TrigTime2D — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: ms.Content: 2D event trigger delay time. This parameter value is related to the slow fading characteristic.The higher this parameter is valued, the less the misjudgment probability is. However, the responsespeed of the event to the measurement signal change becomes lower.Recommended value: D640TrigTime2F — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10,20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: msContent: 2F event trigger delay time. This parameter value is related to the slow fading characteristic.The higher this parameter is valued, the less the misjudgment probability is. However, the responsespeed of the event to the measurement signal change becomes lower.Recommended value: D640

7-48 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 441: SYS202m2 Usr7 Ver1 Rev2

Parameters for Events 2D and 2F Version 1 Rev 2

Parameters for Events 2D and 2F

T rigT ime2F (640ms )

Hys tfor2F (6)INT E R F R E QxxT HDF OR 2F yy

INT E R F R E QxxT HDF OR 2Dyy

xx = Different thres holds can be s et for C S /P S and S ignalling

E vent 2F

Hys tfor2D (6dB )Hys tfor2D (6dB )

E vent 2D

R S C P /E C NO of s tronges t pilot in active s et (border cell)

If s tronges t cell has G S M or interfreq neighbours compress ed mode meas urements taken

T rigT ime2D (640ms )

yy = Different quality thres holds can be s et for E C NO and R S C P formats

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-49

USR7

Page 442: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering of Event 2B

Triggering of Event 2BEvent 2B is triggered when the current signal frequency is lower than the preset threshold and the signalquality of an inter-frequency neighbouring cell is higher than the preset threshold, the system triggers aninter-frequency handover based on coverage.The algorithm to trigger the event is shown on the slide opposite.Where:

• QNoused is the measured quality of the cell that uses other frequency.• TNoused2b is the absolute quality threshold of the cell that uses the other frequencies. Based on the

service type (CS , PS domain R99 service or PS domain HSPA service) and measurement quantity(CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:– Inter-freq CS target frequency trigger Ec/No THD– Inter-freq R99 PS target frequency trigger Ec/No THD– Inter-freq H target frequency trigger Ec/No THD– Inter-freq CS target frequency trigger RSCP THD– Inter-freq R99 PS target frequency trigger RSCP THD– Inter-freq H target frequency trigger RSCP THD

• QUsed is the measured quality of the cell that uses the current frequency.• TUsed2d is the absolute quality threshold of the cell that uses the current frequency.• H2b is the event 2B hysteresis value 2B hysteresis.

After the conditions of Event 2B are fulfilled and maintained until the 2B event trigger delay time isreached, the UE reports the Event 2B measurement report message.The parameters that effect event 2B are found in the ADD CELLINTERFREQHOCOV and are listedbelow.TargetFreqCsThdEcN0/TargetFreqR99PsThdEcN0/TargetFreqHThdEcN0 — Value range:–24~0.Physical unit: dB.Content: For CS domain services, PS domain services and HSPA services respectively, if the value of[Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set themeasurement control of event 2B.Recommended value: –12.UsedFreqCSThdEcN0/UsedFreqR99PsThdEcN0/UsedFreqHThdEcN0 — Value range: –24~0.Physical unit: dB.Content: For CS domain services, PS domain services and HSPA services respectively, if the value of[Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set themeasurement control of event 2B.Recommended value (default value): -12TargetFreqCsThdRSCP/TargetFreqR99PsThdRSCP/TargetFreqHThdRSCP — Value range:–.115~-25Physical unit: dBm.Content: For CS domain services, PS domain services and HSPA services respectively, if the value of[Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set themeasurement control of event 2B.Recommended value: –92.UsedFreqCSThdRSCP/UsedFreqR99PsThdRSCP/UsedFreqHThdRSCP — Value range: -115~-25.Physical unit: dBm.Content: For CS domain services, PS domain services and HSPA services respectively, if the value of[Inter-frequency measure report mode] is set to EVENT_TRIGGER, this parameter is used to set themeasurement control of event 2B.Recommended value (default value): -92HystFor2B — Value range: 0~29.Physical value range: 0~14.5; step: 0.5.Physical unit: dB.Content: Event 2B trigger hysteresis. This parameter value is related to the slow fading characteristic.The greater this parameter is, the less the ping-pong effect and misjudgment that can be caused.Recommended value: 4.TimeToTrig2B — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560, D5000.Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000.Physical unit: ms.Content: Event 2B trigger delay time. This parameter value is related to the slow fading characteristic.

7-50 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 443: SYS202m2 Usr7 Ver1 Rev2

Triggering of Event 2B Version 1 Rev 2

Triggering of Event 2BThe greater this parameter is, the smaller the misjudgment probability, but the lower the speed of eventresponse to measured signal changes.Recommended value: D0.

2/and2/ 2222 bbNousedNousedbbusedused HTQHTQ +≥−≤

f1 f2

Quality value of used frequency (f1) Quality value of other frequency (f2)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-51

USR7

Page 444: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering of Event 2C

Triggering of Event 2CThe event 2C is triggered when the estimated quality of the cell that uses other frequency is higher thana preset threshold. It is used to trigger an inter frequency handover based on speed.The algorithm to trigger the event is shown on the slide opposite.Where:

• QNoused is the measured quality of the cell that uses other frequency.• TNoused2cis the absolute quality threshold of the cell that uses other frequency. Inter-freq measure

target frequency trigger Ec/No THD.• H2c is the event 2C hysteresis value 2C hysteresis.

After the conditions of Event 2C are fulfilled and maintained until the 2C event trigger delay time isreached, the UE reports the Event 2C measurement report message.The parameters that effect Event 2C are found in the command ADD CELLINTERFREQHONCOV andare listed below.InterFreqCovHOThdEcN0 — Value range: –24~0.Physical unit: dB. Content: When the Ec/No value of the target frequency is higher than this threshold,event 2C can be triggered.Recommended value: –16.Hystfor2C — Value range: 0~29.Physical value range: 0~14.5; step: 0.5. Physical unit: dB. Content: Event 2C trigger hysteresis. Thisparameter value is related to the slow fading characteristic. The greater this parameter is, the lessthe ping-pong effect and misjudgment that can be caused. However, in this case, the event cannot betriggered in time.Recommended value: 6.TrigTime2C — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560, D5000.Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000.Physical unit: ms. Content: Event 2C trigger delay time. This parameter value is related to the slowfading characteristic. The greater this parameter is, the smaller the misjudgment probability, but thelower the speed of event response to measured signal changes.Recommended value: D640.

7-52 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 445: SYS202m2 Usr7 Ver1 Rev2

Triggering of Event 2C Version 1 Rev 2

Triggering of Event 2C

2/22 ccNousedNoused HTQ +≥

f1 f2

Absolute quality checked against thresholds and hysteresis values

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-53

USR7

Page 446: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering of Event 1F

Triggering of Event 1FWhen receiving event 1F, the RNC will decide to try a blind handover to inter-frequency cell if a blindhandover neighbouring cell is available.The algorithm to trigger the event is shown on the slide opposite.Where:

• MOld is the measurement value of the cell that becomes worse• T1f is an absolute threshold. The threshold parameters for different intra-frequency measurement

quantity are set to 1F event absolute EcNo threshold, 1F event absolute RSCP thresholdrespectively.

• H1f is 1F hysteresis, the hysteresis value of event 1F.If the signal quality of a cell not in the active set is worse than T1f - H1f/2 for a certain time 1F event triggerdelay time, the UE reports event 1F.The parameters are defined in the ADD CELLINTRAFREQHO command and are listed below.IntraAblThdFor1F — Value range: -24~0Physical unit: dBContent: Absolute threshold of the 1F eventRecommended value: -18Hystfor1F — Value range: 0~15Physical value range: 0~7.5 with the step size of 0.5Physical unit: dBContent: The hysteresis value of the event 1F. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the less ping-pong effect and mis-judgement can becaused. However, the less likely that the event will be triggered in time.Recommended value: 8TrigTime1F — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560 and D5000Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560 and 5000Physical unit: msContent: The trigger delay time of the event 1F. This parameter value is related to the slow fadingcharacteristic. The greater this parameter is set, the smaller the mis-judgement probability, but the lowerthe response speed of the event to the measured signal changes.Recommended value: D640

7-54 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 447: SYS202m2 Usr7 Ver1 Rev2

Triggering of Event 1F Version 1 Rev 2

Triggering of Event 1F

2/10 11 FFold HTLogM −≤

f1 f2

Source cell checked against threshold and hysteresis values

Blind Handover Attempted

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-55

USR7

Page 448: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-Frequency Handover Compressed Mode

Inter-Frequency Handover Compressed ModeCompressed mode is defined as the mechanism whereby certain idle periods are created in radio framesso that the UE can perform inter-frequency measurements during these periods.

Compressed Mode ConceptCompressed Mode control is a mechanism whereby certain idle periods are created in radio framesduring which the UE can perform measurements on other frequencies. The UE can carry outmeasurements in the neighbouring cell, such as GSM cell and FDD cell on other frequency. If the UEneeds to measure the pilot signal strength of an inter-frequency WCDMA or GSM cell and has onefrequency receiver only, the UE must use the compressed mode.Each physical frame can provide 3 to 7 timeslots for the inter-frequency or inter-RAT cell measurement,which enhances the transmit capability of physical channels but reduces the volume of data traffic.Therefore, the compressed mode is usually used in inter-frequency or inter-RAT handover. When thecorresponding handover algorithm decides a measurement in compressed mode based on the UEcapability, the RNC performs the following procedures:

• Sends parameters for the compressed mode to the NodeB and the UE.• Sets parameters for inter-frequency or inter-RAT cell measurement control.• Activates the compressed mode.• Updates the measurement control information to the UE when required.

7-56 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 449: SYS202m2 Usr7 Ver1 Rev2

Inter-Frequency Handover Compressed Mode Version 1 Rev 2

Inter-Frequency Handover Compressed Mode

UMTS S ourc e C ell

UMTS Interfreq C ell

F DD Meas urement G ap ac tivated

G S M C ell

R S S I

B S IC _ID

B S IC _re-c onfirm

C ombined

R S S I

B S IC _ID

F DD Measurement

10ms

Trans mis s ion gap available for inter-frequenc y meas urements

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-57

USR7

Page 450: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Compressed Mode Types

Compressed Mode TypesThe compressed mode is of the following two types:

• Spreading factor reduction (SF/2)• High layer scheduling

Parameter SettingsSelection of UL only, DL only or UL and DL compressed mode operation based on UE capabilities (singleor dual receiver) and neighbouring cell information (i.e. RatCellType and BandInd settings of the ADDGSMCELL command).

• DL only. To allow single receiver UEs to measure GSM 900 BCCH or CPICH• UL and DL. To allow single receiver UEs to measure close-by carriers (e.g. DCS 1800/PCS1900

and other FDD frequencies)• UL only. To allow dual receiver UEs to measure close-by frequencies

Which type of compressed mode to use is automatically decided by the RNC on the basis of the spreadingfactor used in the uplink or the downlink. A parameter in the command ADD CELLCMCF or SET CMCFenables the RNC to make this decision and is described below.DlSFTurnPoint — Value range: D8, D16, D32, D64, D128, D256Physical value range: 8, 16, 32, 64, 128, 256Physical unit: noneContent: CM implementation approach selection basis. When the downlink spreading factor is greaterthan or equal to this parameter value, the SF/2 approach will be preferred. Otherwise, the high-layerscheduling will be preferred. The SF/2 approach consumes more system resources and thereforethis approach is recommended only for low-rate users. The high-layer scheduling requires variablemultiplexing positions of transport channels and is applicable to a relatively narrow range. In addition,this approach affects the transmission rate of users and therefore is recommended only when the SF/2approach is unavailable or there are high-rate users.Recommended value: D64UlSFTurnPoint — Value range: D8, D16, D32, D64, D128, D256Physical value range: 8, 16, 32, 64, 128, 256Physical unit: noneContent: CM implementation approach selection basis. When the uplink spreading factor is greaterthan or equal to this parameter value, the SF/2 approach will be preferred. Otherwise, the high layerscheduling will be preferred. The SF/2 approach consumes more system resources and thereforethis approach is recommended only for low-rate users. The high-layer scheduling requires variablemultiplexing positions of transport channels and is applicable to a relatively narrow range. In addition,this approach affects the transmission rate of users and therefore is recommended only when the SF/2approach is unavailable or there are high-rate users.Recommended value: D64To initiate the high layer scheduling, set the following two switches:

• If the algorithm switch CMCF_DL_HLS_SWITCH in the command SET CORRMALGOSWITCH isset to ON, the DL high-layer scheduling for the compressed mode is allowed.

• If the algorithm switch CMCF_UL_HLS_SWITCH in the command SET CORRMALGOSWITCH isset to ON, the UL high-layer scheduling for the compressed mode is allowed.

7-58 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 451: SYS202m2 Usr7 Ver1 Rev2

Compressed Mode Types Version 1 Rev 2

Compressed Mode Types

UMTS S ourc e C ell

• Spreading factor reduction (SF/2)

• High layer scheduling (optiona)

- UL/DLSFTurnPoint

UL – Close by frequencies

DL – Monitor neighbours

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-59

USR7

Page 452: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Compressed Mode Configuration Function (CMCF) Cell Type

Compressed Mode Configuration Function (CMCF) Cell TypeThere are different types of compressed mode transmission gaps that can be configured depending onwhat type of cell in general it is.

Database ParametersThe parameter to set the CMCF cell type is found in the command ADD CELLCMCF or SET CMCF andis described below.CmcfCellType — Value range: WALKING_SPEED_AND_HOT_SPOT_CELLMID_SPEED_AND_HOT_SPOT_CELLHIGH_SPEED_AND_HOT_SPOT_CELLLOW_SPEED_AND_MEDIUM_COVERAGE_CELLHIGH_SPEED_AND_MEDIUM_COVERAGE_CELLLOW_SPEED_AND_HIGH_COVERAGE_CELLHIGH_SPEED_AND_HIGH_COVERAGE_CELLPICO_NODEB_TYPE_COVERAGE_CELLOTHER_CELLPhysical unit: NoneContent: CM type of the cell. The CMCF parameters are configured based on the CM cell type. Thenumber of the CM list is determined after the CM type of the cell is determined.Recommended value: WALKING_SPEED_AND_HOT_SPOT_CELL

7-60 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 453: SYS202m2 Usr7 Ver1 Rev2

Compressed Mode Configuration Function (CMCF) Cell Type Version 1 Rev 2

Compressed Mode Configuration Function (CMCF) Cell Type

• WALKING_SPEED_AND_HOT_SPOT_CELL

• MID_SPEED_AND_HOT_SPOT_CELL

• HIGH_SPEED_AND_HOT_SPOT_CELL

• LOW_SPEED_AND_MEDIUM_COVERAGE_CELL

• HIGH_SPEED_AND_MEDIUM_COVERAGE_CELL

• LOW_SPEED_AND_HIGH_COVERAGE_CELL

• HIGH_SPEED_AND_HIGH_COVERAGE_CELL

• PICO_NODEB_TYPE_COVERAGE_CELL

• OTHER_CELL

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-61

USR7

Page 454: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-Frequency Handover Decision and Execution

Inter-Frequency Handover Decision and ExecutionInter-Frequency Handover Decision and Execution describes the procedure of decision and executionof different types of inter-frequency handover.

• Coverage-Based and QoS-Based Inter-Frequency Handover Decision and Execution• Load-Based Inter-Frequency Handover Decision and Execution• Speed-Based Inter-Frequency Handover Decision and Execution• Blind Handover Decision and Execution Based on Event 1F• Inter-Frequency Anti-Ping-Pong Algorithm• Inter-Frequency Handover Retry

Coverage-Based and QoS-Based Inter-Frequency Handover Decision andExecution

The coverage-based and QoS-based inter-frequency handovers are categorized into two typesaccording to the following two measurement report modes: periodical measurement report modeand event-triggered measurement report mode. Each mode corresponds to a different decision andexecution procedure.

Coverage-Based and QoS-Based Inter-Frequency Handover in Periodical Measurement ReportModeAfter receiving the periodical measurement report of the inter-frequency cell, the RNC starts the followingdecision procedures:Step 1Decide whether both the CPICH Ec/No value and CPICH RSCP value of the pilot signal of the target cellmeet the requirement of inter-frequency handover.The evaluation formula is listed below:Mother_Freq + CIOother_Freq ≥ Tother_Freq + H/2Where:

• Mother_Freq is the CPICH Ec/No or CPICH RSCP measurement value of the target cell reported by theUE. Both of the two measurement values of the inter-frequency cell must satisfy the formula.

• CIOother_Freq is the cell individual offset value of the target cell. It is equal to the sum of Cell orientedCell Individual Offset and Neighboring cell oriented CIO.

• Tother_Freq is the decision threshold of inter-frequency hard handover.Based on the service type (CS or PS service) and measurement quantity (CPICH Ec/No or CPICHRSCP), this threshold can be configured through the following parameters:– Inter-freq CS target frequency trigger Ec/No THD– Inter-freq R99 PS target frequency trigger Ec/No THD– Inter-freq H target frequency trigger Ec/No THD– Inter-freq CS target frequency trigger RSCP THD– Inter-freq R99 PS target frequency trigger RSCP THD– Inter-freq H target frequency trigger RSCP THDNote: These thresholds are the same as the quality threshold of event 2B. For detailed information.

• H is the inter-frequency hard handover hysteresis value HHO hysteresis.• For the PS and CS combined services, one or more handover thresholds for CS services are used.

Step 2Start the hard handover time-to-trigger timer, which is configured through the parameter HHO periodtrigger delay time.Step 3Either the CPICH RSCP value or the CPICH Ec/No value of the inter-frequency cell satisfies the followingformula:Mother_Freq + CIOother_Freq < Tother_Freq - H/2Where the parameters are the same as those mentioned previously.Step 4

7-62 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 455: SYS202m2 Usr7 Ver1 Rev2

Inter-Frequency Handover Decision and Execution Version 1 Rev 2

Inter-Frequency Handover Decision and ExecutionSelect the cells in sequence, that is, from high quality cells to low quality ones, to initiate inter-frequencyhandover in the cells where the hard handover time-to-trigger timer expires. The quality of a cell isindicated by the measured RSCP.Each cell in the measurement report shall be evaluated as mentioned previously. When the HHO periodtrigger delay time of more than one cell expires at the same time, the latest measurement report isused for selecting the best inter-frequency neighboring cell for handover. For example, the cell with thehighest CPICH RSCP in the latest measurement report is selected.Database ParametersThe additional parameters involved in this procedure are found in the command ADDCELLINTERFREQHOCOV and are described below.HystForPrdInterFreq — Hysteresis for inter-frequency hard handover in periodical report modeValue range: 0~29Physical value range: 0~14.5, step: 0.5Physical unit: dBContent: This parameter is used to estimate the inter-frequency handover at the RNC. The larger thevalue of this parameter, the stronger the capability of resisting signal fluctuation. Thus, the ping-pongeffect can be resisted, but the speed of the handover algorithm to respond to signal change becomeslower, and therefore event 2B might not be triggered in time.Recommended value (default value): 0TimeToTrigForPrdInterFreq — Time delay for hard handover triggered by periodical reportsValue range: 0~64000Physical unit: msContent: Only the inter-frequency cell in which the signal quality meets the requirement in all periodicalreports during the period of time specified by this parameter can be selected as the target cell in theinter-frequency handover.Recommended value (default value): 0

Start

Do both CPICH Ec/No and RSCP meet

for each target cell

2/___ HTCIOM FreqotherFreqotherFreqother +≥+

Start HHO Period Trigger Delay Time

Does either CPICH Ec/No and RSCP meet

for each target cell

2/___ HTCIOM FreqotherFreqotherFreqother −<+

Evaluate target cells from best to worst and initiate handover to that cell

End

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-63

USR7

Page 456: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load-Based Inter-Frequency Handover Decision and Execution

Load-Based Inter-Frequency Handover Decision and ExecutionThe LDR algorithm may trigger an inter-frequency blind handover based on load. The following describesthe procedure for handover decision and execution.

Description of Load-Based Inter-Frequency Handover Decision andExecution

Step 1 — The LDR algorithm learns that a cell is overloaded and provides target cells and the UE withlow priority for handover.Step 2 — The RNC determines to trigger an inter-frequency blind handover through parameterLDR_HO_ALLOW_SHO_SWITCH of Handover Algorithm Switch parameter.

• If the switch is set to ON, the UE in soft handover supports an inter-frequency blind handover. TheRNC determines whether the cell that triggers LDR is the best cell.– If this cell is the best cell, the RNC initiates intra-frequency measurement for inter-frequency

blind handover.– If this cell is not the best cell, the RNC does not initiate an inter-frequency blind handover.

• If the switch is set to OFF, The RNC determines whether the UE has multiple RLs.– If the UE has multiple RLs, the RNC does not initiate an inter-frequency blind handover.– If the UE does not have multiple RLs, the RNC initiates inter-frequency measurement.

Step 3 — According to the parameter Blind handover condition, the RNC executes:

• If the value of the parameter of a cell is -115, the RNC performs direct blind handover to this cell. Ifthe neighboring cells have the same Blind handover condition value, the RNC chooses any one ofthem randomly.

• If there is no such cell with the parameter value -115, the RNC initiates an intra-frequencymeasurement for conditional blind handover.

Database ParametersThe database parameters effecting this algorithm are found in the command ADD INTERFREQNCELLand are described below.BlindHOFlag — Flag of target cell for blind handoversValue range: TRUE, FALSEContent: This parameter indicates whether the neighboring cell is the target cell for blind handovers. Ifthe value is TRUE, blind handovers can be performed to the neighboring cell.Recommended value (default value): FALSEBlindHOQualityCondition — Blind handover conditionValue range: -115~-25Physical unit: dBmContent: If the value is not -115, the handover is defined as Conditional Blind HO, which is used for theinter-frequency neighboring cells of the same coverage. If the value is -115, the handover is defined asDirect Blind HO, which is used for the inter-frequency neighboring cells of larger coverage.Recommended value (default value): -92

7-64 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 457: SYS202m2 Usr7 Ver1 Rev2

Load-Based Inter-Frequency Handover Decision and Execution Version 1 Rev 2

Load-Based Inter-Frequency Handover Decision and Execution

UMTS B es t C ell

UMTS C ell in AS

LDR_HO_ALLOW_SHO_SWITCH = 1

Which cell triggered LDR?

If Best Cell trigger intra-frequency measurements for inter-frequency blind HO.

If not - do not trigger intra-frequency measurements

LDR_HO_ALLOW_SHO_SWITCH = 0

Does the UE have multiple RLs?

Yes – do not trigger inter-frequency blind HO.

No – do trigger inter-frequency blind HO.

Check BlindHOQualityCondition

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-65

USR7

Page 458: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Intra-Frequency Handover Measurement Based on Conditional Blind Handover

Intra-Frequency Handover Measurement Based on ConditionalBlind Handover

The inter-frequency cells with the same coverage area have the same CPICH RSCP values. Bymeasuring the CPICH RSCP of the cell, the quality of the cells with the same coverage area can bedetermined, which increases the probability of successful blind handover.The intra-frequency measurement for conditional blind handover is described as follows:Step 1 — The RNC initializes the timer of intra-frequency measurement for blind handover. The timer isspecified by internal algorithm and needn’t be configured.Step 2 — The RNC modifies the measurement mode:

• The measurement reporting mode is changed to periodic reporting. The reporting period isIntrafrequency measurement report interval of blind HO. The measurement reporting numberis Intrafrequency measurement report amount of blind Handover.

• The intra-frequency measurement quantity is CPICH RSCP.• The list of cells to be measured includes only the cell that triggers LDR.

Step 3 After receiving from the UE the intra-frequency measurement reports for conditional blindhandover, the RNC checks whether the following condition is met:CPICH RSCP of the cell in the measurement report >= Blind handover condition

• If the condition is met, the RNC increments the counter of the number of intra-frequencymeasurement reports for blind handover by 1.

• If the condition is not met, the RNC does not perform a blind handover to the cell that triggers LDRand stops intra-frequency measurement for blind handover.

Step 4 — When the counter reaches the value of Intrafrequency measurement report amount ofblind handover, the RNC initiates a blind handover to the cell that triggers LDR. If the counter does notreach this value, the RNC waits for the next intra-frequency measurement report from the UE.Step 5 — If the timer of intra-frequency measurement for blind handover expires, the RNC does notperform a blind handover to the cell that triggers LDR and stops intra-frequency handover for blindhandover.Note: — When the inter-frequency handover based on coverage or QoS is triggered, the RNC stopsintra-frequency measurement for blind handover.

Database ParametersThe database parameters that effect the conditional blind handover are found in the command SETINTRAFREQHO and are described below.BlindHOIntrafreqMRInterval — Value range: D250, D500Physical value range: 250, 500Physical unit: msContent: This parameter specifies the intra-frequency measurement report interval of blind handover.It determines the intra-frequency measurement reporting interval of Load Reshuffling (LDR) blindhandover. The smaller the value of this parameter, the smaller the intra-frequency measurementreporting interval, and the smaller the time for intra-frequency measurement. But the greater theinfluence of signal fluctuation, which can result in wrong handover. On the contrary, the larger thevalue of this parameter, the longer the intra-frequency measurement reporting interval, and the less theinfluence of signal fluctuation, which can improve the possibility of successful blind handover. But if thetime for intra-frequency measurement becomes long, the handover may not be performed timely.Recommended value: D250BlindHOIntrafreqMRAmount — Value range: D1, D2, D4, D8Physical value range: 1, 2, 4, 8Content: This parameter is used in the algorithm of the load reshuffling (LDR) inter-frequency blindhandover. It defines the number of the intra-frequency measurement reports for blind handover. Thisparameter determines how many measurement reports are needed for making the blind handoverdecision. The RNC starts blind handover only if the UE continuously reports adequate intra-frequencymeasurement reports that meet the quality requirements of blind handover. During the measurementprocess, if the UE reports an unqualified measurement report, the process ends. And the RNC doesnot start blind handover on the target cell.Recommended value: D2

7-66 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

dqfr38
Highlight
dqfr38
Highlight
Page 459: SYS202m2 Usr7 Ver1 Rev2

Intra-Frequency Handover Measurement Based on Conditional Blind Handover Version 1 Rev 2

Intra-Frequency Handover Measurement Based on ConditionalBlind Handover

f1

f2

UMTS B es t C ell

BlindHOIntrafreqMRInterval (250ms Def)

BlindHOIntrafreqMRAmount (2 Def)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-67

USR7

Page 460: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Speed-Based Inter-Frequency Handover Decision and Execution

Speed-Based Inter-Frequency Handover Decision andExecution

Speed-Based Inter-Frequency Handover Decision and Execution covers the decision and execution ofmicro cell to macro cell, as well as that of macro cell to micro cell.

Decision and Execution of Micro Cell to Macro Cell HandoverIf the handover is performed from a micro cell to a macro cell and a target cell for blind handover isconfigured, the RNC performs a blind handover to the target cell. The blind handover procedure is asfollows:Step 1 — The RNC selects the neighboring cells with a lower HCS priority level to generate a cell set. Theneighboring cells whose frequency band is not supported by the UE are not taken into account. If thereare neighboring cells with several candidate frequencies, then the RNC selects one of the frequenciesrandomly.Step 2 — The RNC searches for neighboring cells for blind handover according to Blind handover flagfrom the cell set in step 1.Step 3 — The RNC chooses a neighboring cell whose Blind handover condition value is smallest forblind handover.Step 4 — The RNC determines whether the target cell supports the current service. If the target celldoes not support the current service, the RNC does not perform the blind handover.

Decision and Execution of Macro Cell to Micro Cell HandoverIf the blind handover fails or the handover is performed from a macro cell to a micro cell, the RNC startsthe inter-frequency (or inter-RAT) measurement procedure. If the inter-frequency measurement mode isemployed, the RNC starts the following procedure:

• Add all the pilot cells that trigger event 2C to a cell set and arrange the cells according to themeasurement quality in descending order.

• Select the cells in turn from the cell set to perform inter-frequency handover.

7-68 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

dqfr38
Highlight
Page 461: SYS202m2 Usr7 Ver1 Rev2

Speed-Based Inter-Frequency Handover Decision and Execution Version 1 Rev 2

Speed-Based Inter-Frequency Handover Decision andExecution

BlindHOFlag = TRUE

BlindHOQualityCondition(-92dBm Def)

All pilot cells that trigger event 2C to cell set according to quality measured

HCS = 0HCS = 0

HCS = 1HCS = 1HCS = 1

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-69

USR7

dqfr38
Callout
Blind HO. conditional.
dqfr38
Callout
Cannot use BHO. we use 2C. we start CM in this case when we detect EU in slow moving state
Page 462: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Blind Handover Decision and Execution Based on Event 1F

Blind Handover Decision and Execution Based on Event 1FWhen there is only one cell in the active set, the RNC performs inter-frequency blind handover afterreceiving event 1F.The procedure of blind handover decision and execution based on event 1F is as follows:Step 1 — The RNC determines whether the cell that reports event 1F is the best cell. If the cell is notthe best cell, the RNC does not initiate a blind handover.Step 2 — If the cell is the best cell, and the CPICH_RSCP of the cell is smaller than or equal to 1F eventblind handover trigger condition, the RNC searches for neighboring cells for blind handover accordingto Blind handover flag.Step 3 — If there are many neighboring cells, the RNC chooses a neighboring cell whose Blindhandover condition value is smallest for blind handover.

Database ParametersThe additional parameters for this procedure are found in the command ADD CELLINTRAFREQHO andis described below.BlindHORSCP1FThreshold — Value range: -115~-25Physical unit: dBmContent: This parameter specifies the quality threshold for the event 1F reported cell to trigger blindhandover. This parameter defines the lowest quality threshold of the emergency blind handover. Theblind handover is implemented only if the signal quality in the cell, which reports event 1F, exceeds thespecified threshold. Otherwise, the report will be discarded. This parameter is set to raise the possibilityof successful blind handover. If the signal quality in the cells that report event 1F are all very poor, thisindicates that the user is located at the edge of coverage area. Under this condition, if the blind handoveris initiated rashly, the possibility of call drop increases.Recommended value: -115

7-70 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 463: SYS202m2 Usr7 Ver1 Rev2

Blind Handover Decision and Execution Based on Event 1F Version 1 Rev 2

Blind Handover Decision and Execution Based on Event 1F

f1

f2

UMTS C ell

Edge of cell coverage

BlindHORSCP1FThreshold (-115dBm Def)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-71

USR7

dqfr38
Callout
Blind HO.
Page 464: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Inter-RAT Hard Handover

Inter-RAT Hard HandoverThe purpose of the inter-RAT handover procedure is to, under the control of the network, transfer a UEconnection from one radio access technology (e.g. UTRAN) to another (e.g. GSM). USR7 supportsboth, handover from GSM to UTRAN and, handover from UTRAN to GSM on CS and PS domains (CellChange Order), but not simultaneously. This section covers only handover from UTRAN to GSM as GSMto UTRAN is covered in 2G courses..

Algorithm OverviewIn order to offer worldwide coverage, the handover from UTRAN to GSM is a key feature, especiallyduring early deployment stages where islands of UMTS coverage are envisaged. The procedure isinitiated from UTRAN with a RRC message HANDOVER FROM UTRAN COMMAND. Then the UE mustestablish the connection to GSM and release all UMTS radio resources.When the UE works in CELL_DCH state, the UMTS GSM handover is the procedure during which theWCDMA RAN initiates handover (for CS services) or cell reselection (for PS services) to the GSM.Based on triggering causes, UMTS to GSM handover includes:

• UMTS to GSM coverage-based handover. The coverage of UMTS is usually discontinuous atthe very beginning of the network rollout. On the border, if the signal quality of UMTS rather thanGSM is poor and if all services of the UE are supported by GSM, UMTS to GSM coverage-basedhandover is triggered.

• QoS-based UMTS-to-GSM handover According to the Link Stability Control Algorithm, the RNCneeds to trigger the QoS-based UMTS-to-GSM handover to avoid call drops.

• UMTS to GSM load-based handover. If the load of UMTS rather than GSM is heavy and allservices of the UE are supported by GSM, UMTS GSM load-based handover is triggered.

• UMTS GSM service-based handover. Based on layered services, traffic of different classes ishanded over to different systems. For example, when an Adaptive Multi Rate (AMR) speechservice is requested, this call could be handed over to GSM.

• Speed based UMTS-to-GSM handover — When the Hierarchical Cell Structure (HCS) is used,the cells are divided into different layers on the basis of coverage. Typically, a macro cell has largecoverage and low priority, whereas a micro cell has small coverage and high priority. UMTS-to-GSMhandover can be triggered by the UE speed estimation algorithm of the HCS. A UE moving at highspeed is handed over to a cell with larger coverage to reduce the times of handover, whereas a UEmoving at low speed is handed over to a cell with smaller coverage.

UMTS to GSM Handover Triggering Conditions

• UMTS to GSM coverage-based handover. The CPICH Ec/N0 or CPICH RSCP of the UMTS cellto which the UE connects is lower than the corresponding threshold. In addition, there is a GSMcell whose GSM carrier RSSI is higher than the preset threshold.

• UMTS to GSM load-based handover. The load of the UMTS cell to which the UE connects ishigher than the threshold.

• UMTS to GSM service-based handover. When a service is established, the Core Network (CN)requests a handover of the service to GSM.

7-72 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 465: SYS202m2 Usr7 Ver1 Rev2

Inter-RAT Hard Handover Version 1 Rev 2

Inter-RAT Hard Handover

UMT S f1

G S M

UMT S f2

UMT S f1

UMT S f2

UMT S f1

G S M

UMT S f2

UMT S f1

UMT S f2

• UMTS to GSM coverage-based handover

• QoS-based UMTS-to-GSM handover

• UMTS to GSM load-based handover

• UMTS GSM service-based handover

• Speed based UMTS-to-GSM handover

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-73

USR7

Page 466: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UMTS-to-GSM Handover Procedure

UMTS-to-GSM Handover ProcedureThe UMTS-to-GSM handover procedure is divided into four phases: handover triggering, handovermeasurement, handover decision, and handover execution. The procedure varies with handover types.

• Coverage-based UMTS-to-GSM Handover Procedure• QoS-based UMTS-to-GSM Handover Procedure• Load-based UMTS-to-GSM Handover Procedure• Service-based UMTS-to-GSM Handover Procedure

Coverage-based UMTS-to-GSM Handover ProcedureThe flow chart for the procedure is shown in the diagram and described below.

• In the triggering phase — The RNC sends a MEASUREMENT CONTROL message to the UE,notifying the UE to measure the current carrier quality. This message defines the reporting rulesand thresholds of events 2D and 2F. If the quality of the pilot signal in the current cell deteriorates,the CPICH Ec/No or CPICH RSCP of the UMTS cell that the UE accesses is lower than thecorresponding threshold and the UE reports event 2D.

• In the measurement phase — If the RNC receives a report of event 2D, the RNC may request theNodeB and UE to start the compressed mode to measure the qualities of GSM cells. Then, the RNCmay send an inter-RAT measurement control message that defines the neighboring cell information,reporting period, and reporting rule. In the measurement phase, either periodical measurementreport mode or event-triggered measurement report mode can be used.

• In the decision phase — After the UE reports event 3A, the RNC makes a handover decision. Or,after the UE periodically sends the measurement reports, the RNC evaluates the reports first andthen makes a handover decision.

• In the execution phase — The RNC initiates a handover procedure.

7-74 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 467: SYS202m2 Usr7 Ver1 Rev2

UMTS-to-GSM Handover Procedure Version 1 Rev 2

UMTS-to-GSM Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-75

USR7

Page 468: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 QoS-based UMTS-to-GSM Handover Procedure

QoS-based UMTS-to-GSM Handover ProcedureThe flow chart for the procedure is shown in the diagram and described below.

• In the triggering phase — The Link Stability Control Algorithm makes a handover measurementdecision.

• In the measurement phase — The RNC requests the NodeB and the UE to start the compressedmode to measure the qualities of inter-RAT neighboring cells. Then, the RNC sends an inter-RATmeasurement control message. This message defines neighboring cell information, reportingperiod, and reporting rule. In the measurement phase, either periodical measurement report modeor event-triggered measurement report mode can be used.

• In the decision phase — After the UE reports event 3A, the RNC performs the handover.Otherwise, the UE periodically generates measurement reports, and the RNC makes a decisionafter evaluation.

• In the execution phase — The RNC initiates a handover procedure.

7-76 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 469: SYS202m2 Usr7 Ver1 Rev2

QoS-based UMTS-to-GSM Handover Procedure Version 1 Rev 2

QoS-based UMTS-to-GSM Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-77

USR7

Page 470: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Load-based UMTS-to-GSM Handover Procedure

Load-based UMTS-to-GSM Handover ProcedureThe flow chart for the procedure is shown in the diagram and described below.

• In the triggering phase — When the load of the UMTS cell that the UE accesses is higher thanthe related threshold, the Load Reshuffling (LDR) algorithm makes a handover decision.

• In the measurement phase — The RNC enables the compressed mode and starts the inter-RAThandover measurement.

• In the decision phase — After the UE reports event 3C, the RNC makes a handover decision.• In the execution phase — The RNC initiates a handover procedure.

7-78 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 471: SYS202m2 Usr7 Ver1 Rev2

Load-based UMTS-to-GSM Handover Procedure Version 1 Rev 2

Load-based UMTS-to-GSM Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-79

USR7

Page 472: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Service-based UMTS-to-GSM Handover Procedure

Service-based UMTS-to-GSM Handover ProcedureThe flow chart for the procedure is shown in the diagram and described below.

• In the triggering phase — When a service is established, the RNC requests the handover to theGSM based on the service type and service handover indicator assigned by the Core Network(CN).

• In the measurement phase — The RNC enables the compressed mode and starts the inter-RAThandover measurement.

• In the decision phase — After the UE reports event 3C, the RNC makes a handover decision.• In the execution phase — The RNC initiates a handover procedure.

7-80 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 473: SYS202m2 Usr7 Ver1 Rev2

Service-based UMTS-to-GSM Handover Procedure Version 1 Rev 2

Service-based UMTS-to-GSM Handover Procedure

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-81

USR7

Page 474: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Preconditions for UMTS to GSM Handover

Preconditions for UMTS to GSM Handover

Overview of PreconditionsBefore the UMTS GSM handover is performed, the following preconditions must be taken into account:

• Service handover indicators. The indicators are configured by CN and indicate CN policy forservice handover to GSM.

• GSM cell capability. The capability, Inter-RAT cell type, of each GSM cell must be configured at theRNC. The parameter indicates whether the cell supports GSM, GPRS, or EDGE. It also indicatesthat the cell may not be supported by 2G.

• Service capability. The required 2G Capability, of each service must be configured at the RNC. Theparameter indicates whether the service is supported by GSM, GPRS, or EDGE. It also indicatesthat the service may not be supported by 2G.

• UE capability. The RNC obtains the capability information of a UE according to the UE CAPABILITYINFORMATION reported by the UE. The information indicates whether the UE supports GSM,GPRS, or EDGE. It also indicates that the UE may not be supported by 2G.

Service Handover IndicatorsThe IE Service handover indicator indicates the CN policy for the service handover to the GSM. This IEis indicated in the Radio Access Bearer (RAB) assignment signaling assigned by the CN, or providedby the RNC side if required.The algorithm switch SERVICE_HO_BASED_ON_RNC_SWITCH of Handover Algorithm Switchparameter decides whether the service attribute of inter-RAT handover is based on the RNC or the CN.

• If the switch is set to ON, the service attribute of inter-RAT handover is based on the parameterconfigured on the RNC side.

• If the switch is set to OFF, the service attribute of inter-RAT handover is first based on the CN whenthe indicator is contained in the RAB assignment signaling assigned by the CN. If the CN doesn’tallocate service indicator, the service attribute of inter-RAT handover is based on the RNC side.

By default, the RNC does the following:

• For a UE with a single signaling RAB, the RNC supports the handover to the GSM. But it is notrecommended.

• For the UE accessing combined services (with CS services), the RNC sets the service handoverindicator of the UE to that of the CS service, because the CS service has the highest QoS priority.

• For the UE accessing combined services (with only PS services), the RNC sets the servicehandover indicator of the UE to that of the PS service, which has the highest QoS priority.

If service handover indicators are not configured by the CN, each indictor can be set to the Serviceparameter index of a service on the RNC BAM. Each Service parameter index involves a set ofservice type, source description, CN domain ID, and max rate (bit/s). This is set by the ADDTYPRABBASIC/MOD TYPRAB (hidden).

7-82 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 475: SYS202m2 Usr7 Ver1 Rev2

Preconditions for UMTS to GSM Handover Version 1 Rev 2

Preconditions for UMTS to GSM Handover

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-83

USR7

Page 476: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 GSM Cell Capability

GSM Cell CapabilityWith the Inter-RAT cell type capability, the RNC decides whether to start inter-RAT measurement. Thisis set by the ADD GSMCELL/MOD GSMCELL database parameters.RatCellType — Value range: NO_CAPABILITY, GSM, GPRS, EDGEPhysical unit: None.Content: Indicating the inter-RAT cell type.Recommended value: None.

Service CapabilityFor combined services, the RNC selects the Required 2G Capability parameter required by the RAB thathas the highest priority. This is set by the ADD TYPRABBASIC/MOD TYPRAB database parameters.SHInd — Handover typeValue range:HO_TO_GSM_SHOULD_BE_PERFORM,HO_TO_GSM_SHOULD_NOT_BE_PERFORM, HO_TO_GSM_SHALL_NOT_BE_PERFORMContent: - HO_TO_GSM_SHOULD_BE_PERFORM: Handover to the 2G network is performedwhenever 2G signals are available. - HO_TO_GSM_SHOULD_NOT_BE_PERFORM: Handover tothe 2G network is performed when 3G signals are weak but 2G signals are strong. -HO_TO_GSM_SHALL_NOT_BE_PERFORM: Handover to the 2G network is not performed evenwhen 3G signals are weak but 2G signals are strong. If the handover type is available from the serviceproperties assigned by the Core Network (CN), handovers are performed in the way specified by theCN. If the handover type is not specified by the CN, handovers are performed in the way specified inthe typical traffic parameter.Recommended value (default value): HO_TO_GSM_SHOULD_NOT_BE_PERFORM

UE CapabilityWith the UE CAPABILITY INFORMATION, the RNC decides whether to start inter-RAT measurement.

Switches for UMTS to GSM Service-Based HandoverTo allows UMTS to GSM service-based handover, the RNC must turn on the related switches for servicesin the CS and PS domains.

• When a single CS service is initially set up by the UE, the RNC allows the UMTS to GSMservice-based handover if Inter-RAT CS handover switch is set to ON.

• When a single PS service is initially set up by the UE, the RNC allows the UMTS to GSMservice-based handover if Inter-RAT PS handover switch is set to ON.

• For combined services, no service handover is triggered.These parameters are set by the ADD CELLHOCOMM / MOD CELLHOCOMM database command andare listed below.CSSERVICEHOSWITCH — Value range: ON, OFF.Content: Indicating whether the cell allows CS service inter-RAT handover.Recommended value: OFF.PSSERVICEHOSWITCH — Value range: ON, OFF.Content: Indicating whether the cell allows PS service inter-RAT handover.Recommended value: OFF.

7-84 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 477: SYS202m2 Usr7 Ver1 Rev2

GSM Cell Capability Version 1 Rev 2

GSM Cell Capability

RNCRNCCNCN

Iu

Iub

RAB ASSIGNMENT REQUEST

• Handover indicators (last slide)

UE Capabilities

Service Capabilities configured at the RNC

GSM Cell capabilities

i.e. supports GPRS/EDGE?

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-85

USR7

Page 478: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Handover Procedures for UMTS to GSM

Handover Procedures for UMTS to GSMThe UMTS to GSM handover includes the following four phases:

• Handover triggering• Handover measurement• Handover decision• Handover execution

Non coverage-based handover has two cases:

• UMTS to GSM handover based on load• UMTS to GSM handover based on service

When the UE works in CELL_FACH or CELL_PCH/URA_PCH state, the inter-RAT handover is initiatedby the UE. In this situation, the handover is the procedure for inter-RAT cell reselection. During cellreselection, the UE evaluates the quality of the existing cell on which it is camped, starts inter-RATmeasurement, selects a best cell in another system according to the cell reselection criteria, and theninitiates the access to GSM/GPRS/EDGE.The commands that effect coverage and non coverage based triggered handovers are foundin the commands ADD CELLINTERRATHOCOV for coverage based handovers and ADDCELLINTERRATHONCOV for non coverage based handovers.

7-86 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 479: SYS202m2 Usr7 Ver1 Rev2

Handover Procedures for UMTS to GSM Version 1 Rev 2

Handover Procedures for UMTS to GSM

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-87

USR7

Page 480: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 UMTS to GSM Handover Measurement

UMTS to GSM Handover Measurement

UMTS GSM handover based on coverageAfter receiving a 2D event report message, the RNC performs the following:1) Decides an inter-RAT handover measurement based on coverage.2) Starts periodic controlling or 3A event triggered measurement reporting. The Inter-RAT report modecan be set to Periodic reporting or Event trigger.3) Decides to initiate an inter-RAT handover based on measurement reports from the UE. If a 2F eventis received, the RNC will stop inter-RAT handover measurement.

UMTS GSM handover based on loadAfter receiving a 3C event report message, the RNC decides to initiate an inter-RAT handover.

UMTS GSM handover based on serviceAfter receiving a 3C event report message, the RNC decides to initiate an inter-RAT handover.Note: The measurement quantities for inter-RAT handover are as follows:CPICH Ec/N0 or CPICH RSCP for a UMTS cell: set to 2D2F Measure Quantity, 3A Measure Quantity.GSM Carrier RSSI for a GSM cellFor coverage based handovers the command ADD CELLINTERRATHOCOV is used to decide whetherto use periodical or event triggered reporting etc. This parameters are listed below.INTERRATREPORTMODE — Value range: Periodical_ reporting, Event_trigger.Physical unit: None. Content: Inter-RAT measurement reporting mode. "Periodical_reporting"represents periodical reporting mode. "Event_trigger" represents event-triggered reporting mode.Recommended value: Periodical_reporting.INTERRATPERIODREPORTINTERVAL — Value range: NON_PERIODIC_REPORT,D250, D500,D1000, D2000,D3000, D4000,D6000, D8000,D12000, D16000, D20000, D24000, D28000, D32000,D64000.Physical value range: NON_PERIODIC_REPORT,250, 500, 1000, 2000,3000, 4000,6000, 8000,12000,16000, 20000, 24000, 28000, 32000, 64000. Physical unit: ms.Content: Inter-RAT measurement reporting interval.Recommended value: D1000.

7-88 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 481: SYS202m2 Usr7 Ver1 Rev2

UMTS to GSM Handover Measurement Version 1 Rev 2

UMTS to GSM Handover Measurement

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-89

USR7

Page 482: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering of Events 2D and 2F

Triggering of Events 2D and 2FEvent 2D is triggered on the basis of the following formula.

Where:

• QUsed is the measurement value of the cell at the currently used frequency.• TUsed2d is the absolute quality threshold of the cell at the currently used frequency. Based on the

service type (CS , PS domain R99 service, or PS domain HSPA service) and measurement quantity(CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:– Inter-RAT CS measure start Ec/No THD– Inter-RAT R99 PS measure start Ec/No THD– Inter-RAT H measure start Ec/No THD– Inter-RAT CS measure start RSCP THD– Inter-RAT R99 PS measure start RSCP THD– Inter-RAT H measure start RSCP THD

• H2d is 2D hysteresis, the hysteresis value of event 2D.• For the PS and CS combined services, the threshold(s) for CS services is (are) used.

When the conditions for event 2D are met and maintained in time-to-trigger specified in 2D event triggerdelay time, the UE sends the measurement report of Event 2D.

Triggering of Event 2FEvent 2F is triggered on the basis of the following formula.

Where:

• QUsed is the measurement value of the cell at the currently used frequency.• TUsed2f is the absolute quality threshold of the cell at the currently used frequency. Based on the

service type (CS , PS domain R99 service, or PS domain HSPA service) and measurement quantity(CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:– Inter-RAT CS measure stop Ec/No THD– Inter-RAT R99 PS measure stop Ec/No THD– Inter-RAT H measure stop Ec/No THD– Inter-RAT CS measure stop RSCP THD– Inter-RAT R99 PS measure stop RSCP THD– Inter-RAT H measure stop RSCP THD

• H2f is 2F hysteresis, the hysteresis value of event 2F.• For the PS and CS combined services, the threshold(s) for CS services is (are) used.

When the conditions for event 2F are met and maintained in time-to-trigger specified in 2F event triggerdelay time, the UE sends the measurement report of Event 2F.The parameters that effect 2D and 2F events are set in the ADD CELLINTERRATHOCOV command. Asthe principles are discussed in some detail in Inter-Frequenct handovers they are not further discussedhere.

7-90 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 483: SYS202m2 Usr7 Ver1 Rev2

Triggering of Events 2D and 2F Version 1 Rev 2

Triggering of Events 2D and 2F

T rigT ime2F (640ms )

Hys tfor2F (6)INT E R R AT xxT HDF OR 2F yy

INT E R R AT xxT HDF OR 2Dyy

xx = Different thres holds can be s et for C S /P S and S ignalling

E vent 2F

Hys tfor2D (6dB )Hys tfor2D (6dB )

E vent 2D

R S C P /E C NO of s tronges t pilot in active s et (border cell)

If s tronges t cell has G S M neighbours compres s ed mode meas urements taken

T rigT ime2D (640ms )

yy = Different quality thres holds can be s et for E C NO and R S C P formats

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-91

USR7

Page 484: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering of Event 3A

Triggering of Event 3AIn the case of event triggered reporting, the UE is requested to report 3A events. This will also be disabledon reception of a 2F event. The triggering conditions for event 3A are:

Where:

• Qused is the quality estimate of the used UTRAN frequency• Tused is the absolute quality threshold of the cell that uses the current frequency.

Based on the service type (CS , PS domain R99 service, or PS domain HSPA service) andmeasurement quantity (CPICH Ec/No or RSCP) in the coverage-based handover, TUsed can beconfigured through the following parameters (These parameters are shared by the inter-freq andinter-RAT handover.):– Inter-RAT CS Used frequency trigger Ec/No THD– Inter-RAT R99 PS Used frequency trigger Ec/No THD– Inter-RAT H Used frequency trigger Ec/No THD– Inter-RAT CS Used frequency trigger RSCP THD– Inter-RAT R99 PS Used frequency trigger RSCP THD– Inter-RAT H Used frequency trigger RSCP THDIn the uplink QoS-based handover, based on the measurement quantity (CPICH Ec/No or RSCP),TUsed is configured as the maximum value according to 3GPP specifications, as described below:– If the measurement quantity is CPICH Ec/No, TUsed is configured as the maximum value 0 dB.– If the measurement quantity is CPICH RSCP, TUsed is configured as the maximum value -25

dBm.In the downlink QoS-based handover:– If the measurement quantity is CPICH Ec/No, TUsed is configured as the maximum value 0 dB.– If the measurement quantity is CPICH RSCP, based on the service type (CS, PS domain R99

service, or PS domain HSPA service), TUsed can be configured as one of the following sums:◊ Inter-RAT CS Used frequency trigger RSCP THD and Down Link RSCP Used-Freq THD

Hyst◊ Inter-RAT R99 PS Used frequency trigger RSCP THD and Down Link RSCP Used-Freq

THD Hyst◊ Inter-RAT H Used frequency trigger RSCP THD and Down Link RSCP Used-Freq THD

Hyst• H3a is the hysteresis parameter for event 3a.• MOtherRAT is the measurement quantity for the cell of the other system.• CIOOtherRAT is the cell individual offset value of the cell (in another RAT) in the reporting range which

is equal to the sum of Cell oriented Cell Individual Offset and Neighboring cell oriented CIO.• Wj is a weighting parameter sent from UTRAN to UE and used for frequency j.• TOtherRAT is the absolute inter-RAT handover threshold. Based on the service type (CS , PS domain

R99 service, or PS domain HSPA service), this threshold can be configured through the followingparameters:– Inter-RAT CS handover decision THD– Inter-RAT R99 PS handover decision THD– Inter-RAT H handover decision THD

• For the PS and CS combined services, the threshold(s) for CS services is (are) used.When the conditions for event 3A are met and maintained in time-to-trigger specified by 3A event triggerdelay time the UE sends the measurement report of event 3A.Note: During inter-RAN measurement, it is recommended that UE reports the GSM cell after the BSICof the GSM cell is verified. This can make handover more reliable. The switch is BSIC verify switch.The parameters that effect 3A Events are found in ADD CELLINTERRATHOCOV.

7-92 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 485: SYS202m2 Usr7 Ver1 Rev2

Triggering of Event 3A Version 1 Rev 2

Triggering of Event 3A

2/and2/ 333 aotherRATotherRATotherRATaausedused HTCIOMHTQ +≥+−≤

UMTS GSM

Quality value of UMTS Frequency Quality value of other RAT

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-93

USR7

Page 486: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Triggering of Event 3C

Triggering of Event 3CEvent 3C is triggered on the basis of the formula shown on the slide opposite.Where:

• MotherRAT is the measurement value of the cell (in another RAT) in the reporting range.• CIOOtherRat is cell individual offset, the offset value of the cell (in another RAT) in the reporting range.• TOtherRat is the absolute inter-RAT handover threshold. Based on CS or PS services, it can be

Inter-RAT CS handover decision THD or Inter-RAT PS handover decision THD.• H3c is 3C hysteresis, the hysteresis value of event 3C.

When the conditions for event 3C are met and the delay requirement specified by the 3C event triggerdelay time parameter can be satisfied, the UE sends the measurement report of event 3C.The parameters that effect 3C Events are found in ADD CELLINTERRATHONCOV and are listed below.INTERRATNCOVHOCSTHD — Value range: 0~63.Physical value range: –110 to –48 (1: –110; 2: –109; ...; 63: –48).Physical unit: dBm.Content: This parameter indicates the requirement of CS service inter-RAT handover for the quality ofinter-RAT cells. If the event-triggered reporting mode is adopted, event 3C might be triggered when thequality of the target frequency is higher than this threshold. If the periodical reporting mode is adopted,this parameter is used for coverage-based inter-RAT handover evaluation at the RNC side. The value 0means the physical value is smaller than –110 dBm. Recommended value: 21.INTERRATNCOVHOPSTHD — Value range: 0~63. Physical value range: –110 to –48 (1: –110; 2:–109; ...; 63: –48). Physical unit: dBm.Content: This parameter indicates the requirement of PS service inter-RAT handover for the quality ofinter-RAT cells. If the event-triggered reporting mode is adopted, event 3C might be triggered when thequality of the target frequency is higher than this threshold. If the periodical reporting mode is adopted,this parameter is used for coverage-based inter-RAT handover evaluation at the RNC side. The value 0means the physical value is smaller than̈ –110 dBm. Recommended value: 21.HYSTFOR3C — Value range: 0~15. Physical value range: 0~7.5; step: 0.5. Physical unit: dB. Content:Event 3C trigger hysteresis. This parameter value is related to the slow fading characteristic. The greaterthis parameter is, the less the ping-pong effect and misjudgment that can be caused. However, in thiscase, the event cannot be triggered in time.Recommended value: 0.TRIGTIME3C — Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,D640, D1280, D2560, D5000.Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000.Physical unit: ms. Content: Event 3C trigger delay time. This parameter value is related to the slowfading characteristic. The greater this parameter is, the smaller the misjudgment probability, but thelower the speed of event response to measured signal changes.Recommended value: D640.BSICVERIFY — Value range: Required, Not Required. Physical unit: None.Content: Controlling whether to report a detected cell. The value "Required" means that a detectedGSM cell will be reported only after its BSIC is decoded correctly. The value "Not Required" means thata detected GSM cell will be reported whether its BSIC is decoded or not as long as it meets reportingconditions.Recommended value: Required.

7-94 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 487: SYS202m2 Usr7 Ver1 Rev2

Triggering of Event 3C Version 1 Rev 2

Triggering of Event 3C

2/ 3cotherRATotherRATotherRAT HTCIOM +≥+

UMTS GSM

Quality value of other RAT only

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-95

USR7

Page 488: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Handover Execution and Penalty

Handover Execution and Penalty

UMTS to GSM Coverage-Based Handover - Periodical Reporting ModeAfter receiving the periodical measurement reports of GSM cells, the RNC performs handover decisionand execution as follows:

• Decide whether the quality of GSM cells can meet the conditions for inter-RAT handover.• Evaluate the cells that meet the quality requirement and run the time-to-trigger timer.• Stops evaluating the cells that do not meet the quality requirement and disables the time-to-trigger

timer.• Select cells for inter-RAT handover from the cells whose time-to-trigger timer times out, starting

from the cells with the best quality. The length of the time-to-trigger timer can be Time to triggerfor verified GSM cell (with BSIC acknowledged) or Time to trigger for non-verified GSM cell (withBSIC unacknowledged).

The RNC evaluates a GSM cell and starts the time-to-trigger timer if the condition of the algorithm shownof the slide opposite is met.Where:

• MOtherRat is the measurement value of the cell (in another RAT) in the reporting range.• CIOOtherRat is cell individual offset, the offset value of the cell (in another RAT) in the reporting range.• TOtherRatis the absolute inter-RAT handover threshold. Based on CS or PS services, it can be

Inter-RAT CS handover decision THD or Inter-RAT PS handover decision THD.• H3c is 3C hysteresis, the hysteresis value of event 3C.

UMTS to GSM Coverage-Based Handover - Event Reporting ModeAfter receiving the event reports of GSM cells, the RNC performs handover decision and execution asfollows:

• If the RNC receives event 3A reports, all the GSM cells that trigger event 3A form a cell set andthey are sequenced according the event 3A reports.

• Based on the sequence, the RNC selects the cells in the set. If the cells do not work in handoverpenalty state, the RNC executes the handover until the handover is made.

7-96 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 489: SYS202m2 Usr7 Ver1 Rev2

Handover Execution and Penalty Version 1 Rev 2

Handover Execution and Penalty

UMTS to GSM Handover Based on Load/ServiceAfter receiving the event reports of GSM cells, the RNC performs handover decision and execution asfollows:

• If the RNC receives event 3C reports, all the GSM cells that trigger event 3C form a cell set andthey are sequenced according the event 3C reports.

• Based on the sequence, the RNC selects the cells in the set. If the cells do not work in handoverpenalty state, the RNC executes the handover until the handover is made.

To avoid the impact of UE (in long-term measurement of compressed mode) on the radio network, theInter-RAT handover max attempt times parameter is set to restrict the maximum attempts of the UMTSto GSM handover based on load or service. The parameter involves handover attempts made to thesame cell or different cells.The two parameters Inter-RAT handover max attempt times and Inter-RAT measure timer length worktogether to reduce the number of inter-RAT measurements in compressed mode. The former restrictshandover attempts and the latter restricts handover timer length.

• Handover based on coverage - Period

• Handover based on coverage - event

• Handover based on load/service

2/ 3cotherRATotherRATotherRAT HTCIOM +≥+ For time to trigger timer

Build a list from the cells that triggered the 3A event

Build a list from the cells that triggered the 3C event

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-97

USR7

Page 490: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Network Assisted Cell Change (NACC) from UTRAN to GERAN

Network Assisted Cell Change (NACC) from UTRAN to GERANWhen the UE goes through cell change due to a PS interRAT handover procedure if the UE a serviceinterruption in the region of 4–8s can occur. The consequences of this are that some services can bestopped or degraded for instance TCP applications may time out or streaming applications may stop dueto client buffer depletion.In R5 of the 3GPP specifications provision is made for the GERAN (P)SI messages in the CELL CHANGEORDER FROM UTRAN message. These messages are the RAN Information Management (RIM)mechanism which was designed to be used with NACC.and reduces the delay significantly leading toservice improvements and user experience improvements.To enable this feature the command SET CORRMALGOSWITCH is used to set the flag shown below.PS_3G2G_CELLCHG_NACC_SWITCH — When it is checked, and inter-RAT handover of the PSdomain from UTRAN use cell change order method, inter-RAT handover support NACC function.The RIM mechanism is enabled or disabled on a cell by cell basis. The command to enable RIM is ADDGSMCELL and the parameter is described below.SuppRIMFlag — Value range: FALSE, TRUE.Content: Indicating whether Inter-RAT cell support RIM.Recommended value: FALSE.SuppPSHOFlag — Value range: FALSE, TRUE.Content: Indicating whether Inter-RAT cell support PS HO.Recommended value: FALSE.

7-98 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 491: SYS202m2 Usr7 Ver1 Rev2

Network Assisted Cell Change (NACC) from UTRAN to GERAN Version 1 Rev 2

Network Assisted Cell Change (NACC) from UTRAN to GERAN

UMT S G S M

L ong delays in the region of 4-8s c an oc c ur when P S UMT S to G S M handovers oc c ur .

NAC C c reates improvements and is enabled by:

P S _3G 2G _C E L L C HG _NAC C _S WIT C H

S uppR IMF lag

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-99

USR7

Page 492: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Hierarchical Cell Structure

Hierarchical Cell StructureIn a 3G network, the so-called hot spots in radio communications may appear with an increase ofsubscribers and traffic. This requires more cells to increase the network capacity. More cells andsmaller cell radius indicate that more frequent handovers of UEs take place. For a UE in fast speed,frequent handovers reduce call quality, increase uplink interference, and increase signaling load.In this situation, Hierarchical Cell Structure (HCS) is required to divide cells into different hierarchies.The RNC supports the HCS with eight hierarchies, typically there are three Macro Cells, Micro Cells andPico Cells.The features of different cells are as follows:Macro Cell:

• Large coverage• Continuous coverage networking• Low requirement on capacity• Fast-moving environment

Micro cell:

• Densely populated areas• High requirement on capacity• Slow-moving environment

Pico cell:

• Indoor coverage• Outdoor dead-area coverage.

Where, the pico cell has the highest priority and the macro cell has the lowest priority.

PurposeAccording to speed estimation, the RNC orders the fast-moving UE to handover to the cells of lowerpriority to reduce the number of handovers, and orders the slow-moving UEs to handover to the cellsof higher priority to increase network capacity. The cells of lower priority have larger coverage, and thecells of higher priority have smaller coverage.To add a HCS cell the command ADD CELLHCS is used. Within this command is the parameter is toset the hierarchies together with parameters that are configured when setting up cell reselections. Thecell reselections parameters are covered in an other part of the course.CellId - Uniquely identifying a cellValue range: 0 to 65535 (mandatory)Content: noneRecommended value (default value): noneUseOfHcs — Indicating whether HCS is usedValue range: USED, NOT_USEDContent: noneRecommended value (default value): NOT_USEDHCSPrio — Value range: 0 to 7Content: noneRecommended value (default value): 0The RNC wide command SET CORRMALGOSWITCH has to enable RNC-oriented UE speedestimation, the parameter is shown below.HoSwitch — HCS_SPD_EST_SWITCH:When it is checked, RNC evaluates the UE's moving speed when it is in an HCS cell, and initiatesinter-layer handover by fast-mobility decision according to the UE's speed.

7-100 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 493: SYS202m2 Usr7 Ver1 Rev2

Hierarchical Cell Structure Version 1 Rev 2

Hierarchical Cell Structure

Mac ro C ell

Mic ro C ell

P ic o C ell

Large coverage

Low capacity

F ast moving

Densely populated areas

High capacity

S low moving

Indoor C overage

Outdoor dead area coverage

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-101

USR7

Page 494: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 HCS Handover Overview

HCS Handover OverviewThe HCS handover is divided into the following two phases.

Speed EstimationThe speed estimation on each hierarchy of an HCS cell falls into one of the following types:

• Fast speed• Normal speed• Slow speed

According to the number of changes of the best cell within a given time unit, the speed estimationalgorithm estimates the moving speed of the UEs. See details as follows:

• If the number of changes of best cell for a UE is above the fast-speed threshold, this UE is calculatedto be in fast speed;

• If the number of changes of best cell for a UE is below the slow-speed threshold, this UE is calculatedto be in slow speed;

• If the number of changes of best cell for a UE is between fast-speed threshold and slow-speedthreshold, this UE is calculated to be in normal speed.

HCS Handover Based on Speed EstimationAfter the moving speed of the UE is estimated, inter-hierarchy handover algorithm initiates thecorresponding handover based on this speed decision.According to the results of speed estimation:

• The UE in fast speed is handed over to the cell of lower priority;• The UE in slow speed is handed over to the cell of higher priority;• The UE in normal speed is not required to be handed over to any cell.

7-102 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 495: SYS202m2 Usr7 Ver1 Rev2

HCS Handover Overview Version 1 Rev 2

HCS Handover Overview

T he change of best cell (E vent 1D) is monitored for a time period and if there has been no change of best cell with that time then handover to micro cell and vice versa.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-103

USR7

Page 496: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Speed Estimation for the UE

Speed Estimation for the UEThis section looks at the database parameters to set the speed estimation for the UE.

Fast Speed EstimationThe UE fast speed decision is triggered by 1D event:

• Tfast: time for UE fast speed decision Time window for UE fast speed decision• Nfast: threshold for UE fast speed decision Threshold for UE fast speed decision

Handover procedures:

• The UE fast speed decision is triggered after the 1D report is received;• The UE is decided in fast speed if the number of changes of best cells for the UE is above Threshold

for UE fast speed decision within Time window for UE fast speed decision.The parameters that effect the fast speed estimation are found in the commands ADD CELLHCSHO,SET CELLHCSHO and MOD CELLHCSHO.SpdEstSwitch — Indicating if UE speed estimation is allowed in this cell Value range: ON, OFF ValueON indicates UE speed estimation is allowed in this cell. Value OFF indicates UE speed estimation isnot allowed in this cell. Content: UE speed estimation cannot be triggered even if this switch is enabledin either of the following cases:

• The cell is not configured as a HCS cell by ADD CELLHCS or MOD CELLHCS.• The algorithm switch for RNC-oriented UE speed estimation is not enabled by SET

CORRMALGOSWITCHRecommended value (default value): OFFTFastSpdEst — Time window for estimating if the UE is in high-mobility state.Value range: 0~511Physical unit: sContent: The start point of the estimation is the moment of the last reporting of event 1D, and thebackdated time length is determined by this parameter. If the parameter is set to 0, the RNC doesnot decide if the UE is in high-mobility state.Recommended value (default value): 180NFastSpdEst — Threshold for deciding that the UE is in high-mobility stateValue range: 1~16Content: After the UE reports the event 1D, it is considered in high-mobility state if the number of changesof the best cell during TFASTSPDEST is larger than NFASTSPDEST. The smaller the value is, the morepossibly the UE is decided in high-mobility state.Recommended value (default value): 15

Fast Inter-Hierarchy HandoverWhen the RNC decides that the UE is in fast speed, this UE is handed over from the cell of high priorityto the cell of low priority.If the UE is located at the converged part between the cell of high priority and the cell of low priority, theblind handover is initiated.The target cell can be a UMTS cell or a GSM cell. The priority of intra-system inter-frequency blindhandover is higher than that of inter-system blind handover. If the neighboring cell for blind handover isnot configured or the blind handover fails, the measurement is initiated for cells of low priority. The targetcell is decided based on the measurement report from the UE.

7-104 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 497: SYS202m2 Usr7 Ver1 Rev2

Speed Estimation for the UE Version 1 Rev 2

Speed Estimation for the UE

T F as tS pdE st = 180s

NF astS pdE st = 15ID E vent

ID E vent

ID E vent

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-105

USR7

dqfr38
Callout
Less than 15 1D events n 3 min means the Mobile is slow moving
Page 498: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Slow Speed Estimation

Slow Speed EstimationThe UE slow speed decision is triggered by the expiry of the periodical timer.

• Tslow: time for UE slow speed decision Time window for UE slow speed decision• Nslow: threshold for UE slow speed decision Threshold for UE slow speed decision• Periodic timer for slow speed decision: The length of the periodic timer is set to Period of UE slow

speed decision.Handover procedures:

1. The UE slow speed decision is triggered after the periodic timer for slow speed decision is expired.2. The UE is decided to be in slow speed if the number of changes of best cell for the UE is below

Threshold for UE slow speed decision within Time window for UE slow speed decision.The parameters that effect the slow speed estimation are found in the commands ADD CELLHCSHO,SET CELLHCSHO and MOD CELLHCSHO.TCycleSlow — Cycle timer for deciding if the UE is in low-mobility stateValue range: 0~255Physical unit: sContent: This timer provides the time for deciding if the UE is in low-mobility state. The smaller the valueis, the more frequently the state estimation is triggered.Recommended value (default value): 60TSlowSpdEst — Time window for deciding if the UE is in low-mobility stateValue range: 0~511Physical unit: sContent: Every time the slow speed cycle timer times out, the RNC estimates if the UE is in low-mobilitystate and the backdated time length is set by this parameter. If the parameter is set to 0, the RNC doesnot decide if the UE is in low-mobility state.Recommended value (default value): 240NSlowSpdEst — Threshold for deciding if the UE in low-mobility stateValue range: 1~16Content: After slow speed timer times out, the UE is considered in low-mobility state if the number ofchanges of the best cell caused by UE's reporting of event 1D during TSLOWSPDEST is smaller thanNSLOWSPDEST. The larger the value is, the more possibly the UE is decided in low-mobility state.Recommended value (default value): 3

Slow Inter-Hierarchy HandoverWhen the RNC decides that the UE is in slow speed, this UE is handed over from the cell of low priorityto the cell of high priority.Because the coverage of high priority cells is smaller than that of low priority cells, slow speedinter-hierarchy handover algorithm needs to initiate the measurement for cells of high priority, and thendecides the target cell based on the measurement report from the UE.

7-106 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 499: SYS202m2 Usr7 Ver1 Rev2

Slow Speed Estimation Version 1 Rev 2

Slow Speed Estimation

T C ycleS low = 60s

T S lowS pdE s t = 240s

NS lowS pdE s t = 3ID E vent

ID E vent

ID E vent

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-107

USR7

Page 500: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Anti-Pingpong Recording

Anti-Pingpong RecordingDuring a given period of time, intra-frequency handover may be performed back and forth across two orthree cells, resulting in several event 1Ds of the same cell in the statistic queue and thus inaccurate UEspeed estimation.Therefore, a mechanism is used for anti-pingpong 1D recording. During the recent period Related lengthfor 1D records, a 1D event with a repeated cell would not be recorded.The parameters that effect the anti-pingpong recording are found in the commands ADD CELLHCSHO,SET CELLHCSHO and MOD CELLHCSHO.TRelateLength — Related length for 1D records in the best cellsValue range: 0~120Physical unit: sContent: In the speed estimation algorithm, an algorithm is adopted to avoid inaccurate estimationcaused by frequent handovers of best cells. That is, during the latest TRELATELENGTH, if more thanone event1D of a certain cell occur, the event 1D record is restored to the state when the 1st event 1Doccurs during the latest TRELATELENGTH. The given time length is set by this parameter. If the valueis set too large, the RNC judges a non-frequently changing best cell change as a frequently changingone by mistake.Recommended value (default value): 10

7-108 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 501: SYS202m2 Usr7 Ver1 Rev2

Anti-Pingpong Recording Version 1 Rev 2

Anti-Pingpong Recording

T R E LAT E LE NG T H = 10sR epeated ID E vent

ID E vent

ID E vent

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

7-109

USR7

Page 502: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Anti-Pingpong Recording

This page intentionally left blank.

7-110 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 503: SYS202m2 Usr7 Ver1 Rev2

Serving RNS Relocation (SRNSR) Version 1 Rev 2

Chapter 8

Serving RNS Relocation (SRNSR)

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

8-1

USR7

Page 504: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Serving RNS Relocation (SRNSR)

This page intentionally left blank.

8-2 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 505: SYS202m2 Usr7 Ver1 Rev2

Chapter Objectives Version 1 Rev 2

Chapter Objectives

• State the purpose and describe the function of SRNS Relocation• List and describe the use of the MML that contain parameters that have an influence on SRNS

relocation.

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

8-3

USR7

Page 506: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 SRNS Relocation

SRNS Relocation

SRNS Relocation OverviewThe Serving RNS (SRNS) manages the connection between the UE and the UTRAN and can berelocated. The SRNS relocation is of three types:

• Static relocation (UE not involved)• Relocation due to hard handover (UE involved)• Relocation due to cell or URA update (UE not involved)

Static relocation and relocation due to cell or URA update require that the Iur interface is available.

PurposesThe main benefits of SRNS relocation are as follows:When the Iur interface is involvedSRNS relocation can avoid data forwarding on the Iur interface, thus reducing the bandwidth occupiedby the Iur interface and shortening the transmission delay of the user plane.When the SRNC and the DRNC are separate, the data of cell-related radio resource managementalgorithms cannot be transmitted over the Iur interface. Thus, the associated algorithms cannot be usedto optimize t he radio resource management. This problem can be solved by initiating static relocationfrom the source RNC to the target RNC, that is from the original SRNC to the original DRNC.When the Iur interface is not involvedSRNS relocation can ensure communications not interrupted when the UE moves to the coverage areaof another RNC.

Static RelocationWhen the Iur interface exists, the UE may use the radio resources of one RNC (DRNC) and connects tothe CN through another RNC(SRNC).After a UE in CELL_DCH state adds or removes radio links during movement, if all the radio links are inthe DRNC instead of the SRNC, static relocation occurs.When a UE in CELL_FACH state undergoes a cell update to the DRNC, static relocation occurs if the UEcan be connected to the SRNC through the common channels on the Iur interface. The use of commonchannel decided by Iur CCH support flag.After SRNS relocation, the Iur resources for the UE are released. The target RNC (TRNC) not onlyprovides radio resources for the UE but also connects the UE to the CN.The purposes of the static SRNS relocation are as follows:

• To reduce the bandwidth occupied by the Iur interface• To reduce the transmission delay of user plane• To get the parameters of cell-level algorithms to optimize the performance

8-4 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 507: SYS202m2 Usr7 Ver1 Rev2

SRNS Relocation Version 1 Rev 2

SRNS Relocation

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

8-5

USR7

Page 508: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Relocation Due to Hard Handover

Relocation Due to Hard HandoverThe relocation happens when the UE is in CELL_DCH state and moves from one RNC to another RNCwith no Iur interface connecting the two RNCs.

Relocation Due to Cell or URA UpdateThis type of relocation occurs when a UE in CELL_DCH state is handed over from one RNC to anotherRNC and there is no Iur interface connecting the two RNCs. This relocation involves the UE..SRNS Relocation for Cell Update

Relocation tion due to Cell or URA UpdateThis type of relocation occurs when a UE in CELL_PCH, CELL_FACH or URA_PCH state performs acell reselection to another RNC. This relocation does not involve the UE.

8-6 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 509: SYS202m2 Usr7 Ver1 Rev2

Relocation Due to Hard Handover Version 1 Rev 2

Relocation Due to Hard HandoverSRNS Relocation due to Hard Handover

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

8-7

USR7

Page 510: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 SRNS Relocation and DSCR Algorithms

SRNS Relocation and DSCR AlgorithmsThis describes the static relocation algorithm, the relocation with UE involved algorithm, and the DirectedSignaling Connection Re-establishment (DSCR) algorithm.The DSCR procedure is used by the RNC to release the current RRC connection carrying non-real-timeRABs and to request the UE to re-establish the RABs immediately.Note: DSCR can be triggered only for non-real-time RABs. If the RRC connection does not carry anynon-real-time RAB, the RNC does not initiate DSCR to release the connection.

Relationship between SRNS Relocation and HandoverHandover, including intra-frequency soft handover, intra- or inter-frequency hard handover is introducedhere for:

• Static relocation may occur after handover on Iur• Relocation with UE involved may occur if handover over Iur is disabled• Handover over Iur may occur if DSCR (when Iur is not supporting HSPA) is not allowed.

Conditions when Handover over Iur is allowedWhen the target cell under the target RNC fulfils the criteria for intra-frequency soft handover, intra orinter-frequency hard handover, the conditions that the handover over Iur is triggered are as follows:

• If Iur interface is not available, all kinds of handovers over Iur are forbidden.Whether Iur interface is available depends on the setting of the Iur Interface Existing Indicationparameter.

• If Iur interface is available:– Whether intra- or inter- frequency hard handover is allowed over the Iur interface depends on

the setting of the HHO cross IUR trigger parameter.– Whether the soft handover is allowed over the Iur interface depends on the setting of the SHO

cross IUR trigger parameter.The SHO cross IUR trigger parameter consists of three sub switches:

• CS_SHO_SWTICH• HSPA_SHO_SWTICH• NON_HSPA_SHO_SWTICH

Related Database ParametersThe parameters to allow handover over Iur are found in the command ADD NRNC and are describedbelow.IurExistInd — IUR Interface Existing IndicationValue range: FALSE,TRUE.Content: Indicating whether to config neighbouring RNC’s DSP index.SHOTRIG — SHO cross IUR trigger1) CS_SHO_SWITCH. Triggering soft handover for CS cross the IUR interface between the RNC andthe neighboring RNC when the switch is checked.2) HSPA_SHO_SWITCH. Triggering soft handover for HSPA cross the IUR interface between the RNCand the neighboring RNC when the switch is checked.3) NON_HSPA_SHO_SWITCH. Triggering soft handover for PS(R99) cross the IUR interface betweenthe RNC and the neighboring RNC when the switch is checked.HHOTRIG — HHO cross IUR triggerValue range: ON, OFF.Content: Indicating whether to trigger hard handover cross the IUR interface between the RNC and theneighboring RNC.

8-8 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 511: SYS202m2 Usr7 Ver1 Rev2

SRNS Relocation and DSCR Algorithms Version 1 Rev 2

SRNS Relocation and DSCR Algorithms

S R NC

C N

Iu

C R NC

Iur

Based on:• HHO cross IUR trigger

• SHO cross IUR trigger for

CS

HSPA PS

R99 PS

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

8-9

USR7

Page 512: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Static Relocation and DSCR Algorithm

Static Relocation and DSCR AlgorithmWhen the target cell under the target RNC fulfils the criteria for intra-frequency soft handover, intra- orinter-frequency hard handover, if handover procedure over Iur is allowed and UE is in CELL_DCH state,then SRNC will trigger soft or hard handover procedures to move all radio links from SRNC to the TargetRNC.If the radio links of a UE in CELL_DCH state are provided only by the Target RNC (TRNC), the staticrelocation or DSCR can be triggered in one of the following four situations:

• SRNS relocation or DSCR based on delay optimization — The SRNC uses the Estimatednon-measurement delay offset parameter to calculate the transmission delay on theuser plane. To enable SRNS relocation or DSCR in this situation, set sub parameterSRNSR_DSCR_PROPG_DELAY_SWITCH of SRNSR Algorithm Switch to ON.

• SRNS relocation or DSCR based on transmission optimization — The SRNC calculates thebandwidth occupancy of the Iur interface. If the occupancy exceeds the threshold, the SRNCselects the three UEs with max bitrates on the congested path at a time, and then triggersrelocation or DSCR. The SRNC doesn’t stop selecting UEs on the congested path until theoccupancy becomes lower than the threshold or there is no UE that SRNS relocation or DSCRis applicable to.The following parameters are involved in this situation:– SRNSR Iur reselection timer– Forward congestion threshold– Backward congestion thresholdTo enable SRNS relocation or DSCR in this situation, set sub parameterSRNSR_DSCR_IUR_RESRCE_SWITCH of SRNSR Algorithm Switch to ON.

• SRNS relocation or DSCR based on separation time — If the radio links of a UE in CELL_DCHstate are provided only by the Target RNC for a period of time that exceeds the value of Durationof triggering static relocation, the SRNC initiates SRNS relocation or DSCR.To enable SRNS relocation or DSCR in this situation, set subparameterSRNSR_DSCR_SEPRAT_DUR_SWITCH of SRNSR Algorithm Switch to ON.

• SRNS relocation or DSCR based on location separation — The SRNC initiates SRNS relocationor DSCR if the UE moves to an area controlled by the DRNC that contains all the links and if all theintra-frequency neighbouring cells of the current best cell don’t belong to the SRNC.To enable SRNS relocation or DSCR in this situation, set sub parameterSRNSR_DSCR_LOC_SEPRAT_SWITCH of SRNSR Algorithm Switch to ON.

RNC initiates DSCR or static relocation according to the DSCR Indicator:

• When the value of DSCR Indicator for the DRNC is TRUE, the SRNC initiates the DSCR procedureinstead of the SRNS relocation procedure.

• Otherwise, SRNC initiates the static relocation procedure.

Database ParametersThe parameters that effect the static relocation and DSCR algorithm are found in the commands SETCORRMALGOSWITCH, ADD NRNC and SET SRNS and are described below.SrnsrSwitch — SRNSR Algorithm SwitchValue range: 1) SRNSR_DSCR_IUR_RESRCE_SWITCH: When the switch is selected, relocationfor transmission optimization over the Iur interface is allowed. When there is congestion over the Iurinterface, the UE may be selected to initiate relocation or DSCR if the UE has only a radio link overthe Iur interface and the link have the same attributes as the congested link. Based on DSCRInd ofADD NRNC, the RNC decides whether to initiate relocation or DSCR. When the RRC CONN RELmessage with the cause value "Directed Signalling Connection re-establishment" is sent to the UE, theUE initiates RRC reestablishment and updates the routing area once immediately.2) SRNSR_DSCR_LOC_SEPRAT_SWITCH: When the switch is selected, the RNC initiates staticrelocation or DSCR if the optimal cell and the intra-frequency neighboring cell of the optimal cell are noton the SRNC (the SRNC and the CRNC are separated). Based on DSCRInd of ADD NRNC, the RNCdecides whether to initiate relocation or DSCR.3) SRNSR_DSCR_PROPG_DELAY_SWITCH: When the switch is selected, the RNC initiates staticrelocation or DSCR if the delay over a link cannot meet QoS requirements (the SRNC and the CRNCare separated). Thus, delay over the link is reduced on the network side and the QoS is enhanced.Based on DSCRInd of ADD NRNC, the RNC decides whether to initiate relocation or DSCR.4) SRNSR_DSCR_SEPRAT_DUR_SWITCH: When the switch is selected, the RNC initiates static

8-10 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7

Page 513: SYS202m2 Usr7 Ver1 Rev2

Static Relocation and DSCR Algorithm Version 1 Rev 2

Static Relocation and DSCR Algorithmrelocation or DSCR if the duration of separation between the SRNC and the CRNC exceeds a configuredthreshold. Based on DSCRInd of ADD NRNC, the RNC decides whether to initiate relocation or DSCR.Content: switches of the relocation algorithms.Recommended value (default value): SRNSR_DSCR_IUR_RESRCE_SWITCH:OFFSRNSR_DSCR_LOC_SEPRAT_SWITCH:ONSRNSR_DSCR_PROPG_DELAY_SWITCH:OFFSRNSR_DSCR_SEPRAT_DUR_SWITCH:ONDSCRInd — Indicating whether to replace relocation procedure with DSCR procedure between the RNCand the neighboring RNC.Value range: FALSE,TRUEContent: Indicating whether to replace relocation procedure with DSCR procedure between the RNCand the neighboring RNC.Recommended value (default value): FALSESRNSRDelayOffset — Value range: 0~400Physical unit: msContent: When [Measurement transfer delay by FP Node synchronization between SRNC and DRNC]+[Estimated non-measurement delay offset] > [transfer delay provided by the QOS of the current traffic],the relocation will be triggered. The value of this parameter should be set according to the time delayconcerned requirements of the most common services over the Iur interface. If the value is too small,unnecessary relocation will occur; if the value is too large, the QoS of the services over the Iur interfacewill be affected. The transfer delay provided by the QOS of the current traffic is the parameter set at theCN and is notified to the RNC through an RAB ASSIGNMENT REQUEST message.Recommended value: 400SRNSRIurReselectTimerLen — Value range: 1~100Physical unit: sContent: time interval between two SRNS relocations based on Iur resource optimization. For each timeinterval, the RNC specifies several UEs to perform the relocation based on Iur resource optimization.The parameter should be set according to the the time interval of the Iur source congestion report. Thedifference between the previous two values cannot be too large. Individually changing a parameter willcause the time difference in the congestion report and the relocation triggering, and thus the algorithmcannot be efficiently performed.Recommended value: 5SrnsrSeparateDuration — Value range: 1~255Physical unit: s Content: If SRNSR_DSCR_SEPRAT_DUR_SWITCH of [PARA]SrnsrSwitch[/PARA] inSET CORRMALGOSWITCH is on, after the separation of the SRNC and the CRNC, a timer starts. Afterthe time is expired, the SRNS relocation is triggered. This parameter determines the number of UEsover the Iur interface. If this parameter is set too large, it will cause too much unnecessary occupied Iurresources; if the parameter is set too small, ping-pong relocation may occur.Recommended value: 30SrnsRabCnDomainType — Value range: RT, NRT, ALLPhysical value range: nonePhysical unit: none Content: SRNS relocation-allowed traffic type. This parameter determines thebearing policy over the Iur interface. If the parameter is set to RT, only the real-time service can triggerthe static relocation; if the parameter is set to NRT, only the non-real-time service can trigger the staticrelocation; if the parameter is set to ALL, all services can trigger the static relocation.Recommended value: NRT

© 2009 Motorola, Inc. SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

8-11

USR7

Page 514: SYS202m2 Usr7 Ver1 Rev2

Version 1 Rev 2 Static Relocation and DSCR Algorithm

Static Relocation and DSCR Algorithm

S R NC

C N

Iu

C R NC

Iur

SRNS Relocation Based on:

• Transmission delay on IurInterface

• Bandwidth occupancy (congestion)

• SRNC and CRNC Separation time

• UE controlled by CRNC

8-12 SYS202m2: Radio Network Controller Database — RRM Parameters USR7FOR TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED

© 2009 Motorola, Inc.

USR7