Course Content

Radio Resource Management

Overview
Parameter Configuration
Common Channels & Power
Control
Load Control
Admission Control
Packet Scheduling
Handover Control
Resource Manager
1 © 2006 Nokia
Module Objectives
• At the end of the module you will be able to:

• Explain spreading code allocation strategies

• Explain code tree usage optimisation and parameters

2 © 2006 Nokia
Resource Manager
• Functions
• Code Allocation

3 © 2006 Nokia
Resource Manager
• The main function of RM is to 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 and 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 and code types for different reasons such as
soft handover and 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 spreading (=channelization) codes, UL scrambling code, UL spreading
(=channelisation) code type
• Prevents fragmentation, may cause extra HO's

4 © 2006 Nokia
Resource Manager
• Downlink: Scrambling code separates the cells and spreading code separates
connections
• Uplink: Scrambling code separates the MS's
• All physical channels are spread with individual spreading codes, Cm(n) and
subsequently by the scrambling code, CFSCR
• RM generates DL spreading codes

user data widespread data

scrambling
spreading
code code

5 © 2006 Nokia
Resource Manager
• Functions
• Code Allocation

6 © 2006 Nokia
Spreading Code Allocation

• Code Allocation Algorithm chooses the correct spreading code depending on

the TFC type
C 3 (0)=(…)
C 2 (0)=(1,1,1,1)
C 3 (1)=(…)
C1 (0)=(1,1)
C 3 (2)=(…)
C 2 (1)=(1,1,-1,-1)
C 3 (3)=(…)
C 0 (0)=(1)
C 3 (4)=(…)
C 2 (2)=(1,-1,1,-1)
C 3 (5)=(…)
C1 (1)=(1,-1)
C 3 (6)=(…)
C 2 (3)=(1,-1,-1,1)
C 3 (7)=(…)
Code Code Code Order Code
Order 0 Order 1 2 (SF 4) Order 3
(SF 1) (SF 2) (SF 8)
The codes are layered from 0 to 11 according to the Spreading Factor (SF)
• Cm(n) : The code order, m, and the code number, n, designates each and every code in
the layered orthogonal code sequences
• In DL code order 2 to 8 (SF 4 to 512) are available (Nokia RAN does not support SF = 512)
• In UL code order 2 to 7 (SF 4 to 256) are available

7 © 2006 Nokia
Spreading Code Allocation – Example
Ordinary downlink speech channel, requires 30 ksps physical capacity (AMR
12.2 – 4.75 kbit/s). The code order is 8, which means there are 128 chips to
illustrate one symbol (2n, n=7). If the requested channel is 120kbit/s (including
DPCCH and channel coding) data channel, then the type of code is 6.
Spreading code cycle depends on the symbol rate.

Code Channel Channel

DPDCH
Order symbolrate bitrate SF
bits/frame
(ksps) (kbps)

9 15 7.5 512 40

8 30 15 256 160

7 60 30 128 340 AMR Speech

6 120 60 64 600

5 240 120 32 1400 64 kbps data

4 480 240 16 2880 128 kbps data
3 960 480 8 6080 384 kbps data
2 1920 960 4 12480

8 © 2006 Nokia
 Downlink Code Allocation
DPA with 5 codes allocated at cell MAC-hs start-up when HSDPA is enabled
de allocation is dynamic in future releases when more than 5 codes are allocated

SF = 1

SF = 2

SF = 4

SF = 8

SF =16

SF =32 Codes for 5

SF =64 HS-PDSCH's
SF =128

SF =256
Codefor one
HS-SCCH
Codes for thecell commonchannels

6 codes @ SF=256 available for the associated DCHs and non-HSDPA uses

9 © 2006 Nokia
Downlink Code Allocation – Common Channels
SF = 1
• Pilot (P-CPICH) and BCCH (P-CCPCH) need a fixed code allocation
• P-CPICH: CH256,0 SF = 2
• P-CCPCH: CH256,1
SF = 4RAN
• AICH and PICH codes in Nokia
• AICH: CH256,2
• PICH: CH256,3 SF = 8
• S-CCPCH code allocation depends on number of active S-CCPCH in Nokia RAN
• With 1 S-CCPCH: CH64,1
SF =16

SF =32

SF =64 S-CCPCH

SF =128 X

SF =256
Codef
X X
HS-S
P-CCPCH
P-CPICH

AICH

PICH
Codes for thecell commonchannels
10 © 2006 Nokia
Spreading Code Allocation
• 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
• Re-arrangements in the code tree is done by reallocating the codes in better locations

• The above code tree has 4 codes of equal order. The best locations are in the same
branch and very close to one another. The badly located codes are 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

11 © 2006 Nokia
 Spreading Code Allocation
• CodeTreeOptimisation
• The parameter indicates if rearrangement can be applied to a specific cell.

• range: 0 (optimization not used), 1 (optimization used) default: 1;

• CodeTreeOptTimer
• The parameter defines the timer value that triggers code tree optimization, if it is
not triggered otherwise
• range:1 ... 65535 s, step 1 s default: 3600 s; 1 ... 65535 s, step 1 s

12 © 2006 Nokia
 Spreading Code Allocation
• CodeTreeUsage
• The parameter defines the minimum usage of code tree before rearrangement is
applied to a specific cell.

• range: 0 ... 100 %, step 1 % default: 25%;

• MaxCodeReleases
• The parameter defines the maximum number of code release actions allowed in a
code tree before rearrangement is applied to this code tree.

• range: 1 ... 65535, step 1 default 25;

13 © 2006 Nokia
DL Scrambling Code Allocation
• Each cell uses one permanent DL scrambling code that is allocated by O&M
and is taken into use when the cell is started. This requires scrambling code
planning , e.g. for adjacent cells.

• PriScrCode
• range: 0 ... 511, step 1 default: No default

• Identifies the downlink scrambling code of the Primary CPICH (Common Pilot
Channel) of the Cell

14 © 2006 Nokia
UL Scrambling Code Allocation
• 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 should 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 and in the end it
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.

15 © 2006 Nokia
Scrambling Code Allocation
• ULScrCodeMax
• range: 8192 ... 16.777.215, step 1 default: 2.000.000

• Defines the maximum value of the uplink scrambling code. The uplink scrambling
code is unique for each MS, and it is used continuously even if the frequency is
changed. The first 0...8191 scrambling codes are reserved for future use.

• ULScrCodeMin
• range: 8192 ... 16.777.215, step 1 default:1.000.000

• Defines the minimum value of uplink scrambling code. The uplink scrambling code is
unique for each MS.

16 © 2006 Nokia
Chapter 8
-Resource Manager-

1. What are the tasks of resource manager?

2. What has the RM to do with the URA?

3. Which type of code allocation will typically be performed by a network

planning tool/team?

17 © 2006 Nokia