Course Content

Radio Resource Management Overview Power Control Load Control Admission Control Packet Scheduling Handover Control Resource Manager
HSDPA basics & RRM HSUPA basics & RRM HSPA+ features (Overview)

Nokia Siemens Networks

RN31638EN30GLA1

Module Objectives
At the end of the module you will be able to:
Explain the functions of Resource Manager Explain code tree usage optimisation & parameters

Nokia Siemens Networks

RN31638EN30GLA1

Resource Manager RM
Main function: allocate logical radio resources of BS according to the channel request by the RRC layer for each radio connection. The RM is located in the RNC and it works in close co-operation with AC & PS. The actual input for resource allocation comes from AC/PS and RM informs the PS about the resource situation The RM is able to switch codes & code types for different reasons such as SHO & defragmentation of code tree Manages the BS logical resources
BS reports the available logical HW resources

Requests for other resources such as ATM

Transport resource manager RNC HW manager (L1/L2)

Maintains the code tree

allocates the DL Channelization Codes, UL Scrambling Code, WCEL; 0 (not used); UL Channelization Code type 1 (used) prevents Code Tree fragmentation, which may cause extra IF or IS HO's with HSDPA, RM allocates a number of codes to a HSDPA code pool for HSDPA users NodeB PS then allocates Channelization Codes per user & TTI from the HSDPA pool

CodeTree Optimization

Nokia Siemens Networks

RN31638EN30GLA1

Resource Manager
DL: Scrambling codes separate the cells; Channelization codes separate connections UL: Scrambling Codes separate the UE's

All physical channels are spread with individual Channelization Codes, Cm(n) and subsequently by the scrambling code, CFSCR

User data Channelization Code Scrambling Code

Widespread data

Nokia Siemens Networks

RN31638EN30GLA1

Code Tree Optimization / De-fragmentation

A code is always allocated from the optimum location in the code tree. It makes the allocated code and the codes in the branches below and above the allocated code unavailable Code tree will fragment quickly if releases is not re-arranged Code tree Re-arrangements done by reallocating the codes in better locations
CodeTree Optimization
WCEL; 0 (not used); 1 (used)

CodeTree OptTimer
WCEL; 1..65535; 1; 3600s

CodeTreeUsage
min. usage of code tree before rearrangement

WCEL; 1..65535; 1; 3600s

MaxCode Releases In the above example 4 codes of equal order are allocated. The best locations are in the same branch and very close to one another. The badly located code is released and optimally reallocated allowing the use of upper layer codes Codes are only reallocated when there is a benefit at two code tree layers above the code being reallocated
Max. code releases before rearrangement

WCEL; 1..65535; 1; 3600s

Nokia Siemens Networks

RN31638EN30GLA1

DL & UL Scrambling Code Allocation

Each cell uses 1 semi-permanent DL Primary Scrambling Code that is allocated by O&M. It is taken into use when the cell is started, requiring scrambling code planning , e.g. for adjacent cells.
PriScrCode identifies the DL scrambling code of the cell is applied to all physical channels but SCH

PriScrCode
WCEL; 0..511; 1; no default

UL Scrambling Codes: are mobile specific and are allocated in connection establishment.
The codes are indexed from 0 to 224(16,777,216). Different UEs within the same cell must use different UL scrambling codes RM allocates UL scrambling code from a list of codes inside a single RNC.
For example RNC_123 can allocate codes from 1000000 to 1999999; finally starts from 1000000 again. This allocation unit saves all used codes in a table and checks if allocated code is used or not

Since different RNCs allocate their own codes there is a possibility that two mobiles get the same code. With code planning and Iur signaling (negotiating within RNCs) the above problem is avoided.
ULScrCodeMin the minimum value of UL scrambling code; it is unique for each MS. The maximum UL scrambling code number is calculated by the system as

ULScrCodeMin
RNC; 8192..16.777.215; 1; 1.000.000

ULScrCodeMin + n*m

where n is the number of ICSUs in the RNC & m=8192 is the max number of user/ ICSU This suggests careful configuration when considering HW upgrades to avoid overlaps
ICSU: Interference Control & Signalling Unit
6 Nokia Siemens Networks RN31638EN30GLA1