Вы находитесь на странице: 1из 12


Resource Manager

RN3710AEN16GLA0 © 2016 Nokia

Copyright and confidentiality

The contents of this document are proprietary and Such Feedback may be used in Nokia products are made in relation to the accuracy, reliability or
confidential property of Nokia. This document is and related specifications or other documentation. contents of this document. NOKIA SHALL NOT BE
provided subject to confidentiality obligations of the Accordingly, if the user of this document gives RESPONSIBLE IN ANY EVENT FOR ERRORS IN
applicable agreement(s). Nokia Feedback on the contents of this document, THIS DOCUMENT or for
Nokia may freely use, disclose, reproduce, license, any loss of data or income or any special,
This document is intended for use of Nokia’s distribute and otherwise commercialize the incidental, consequential, indirect or direct
customers and collaborators only for the purpose feedback in any Nokia product, technology, service, damages howsoever caused, that might arise from
for which this document is submitted by Nokia. No specification or other documentation. the use of this document or any contents of this
part of this document may be reproduced or made document.
available to the public or to any third party in any Nokia operates a policy of ongoing development.
form or means without the prior written permission Nokia reserves the right to make changes and This document and the product(s) it describes
of Nokia. This document is to be used by properly improvements to any of the products and/or are protected by copyright according to the
trained professional personnel. Any use of the services described in this document or withdraw applicable laws.
contents in this document is limited strictly to the this document at any time without prior notice.
use(s) specifically created in the applicable Nokia is a registered trademark of Nokia
agreement(s) under which the document is The contents of this document are provided "as is". Corporation. Other product and company names
submitted. The user of this document may Except as required by applicable law, no warranties mentioned herein may be trademarks or trade
voluntarily provide suggestions, comments or other of any kind, either express or implied, including, but names of their respective owners.
feedback to Nokia in respect of the contents of this not limited to, the implied warranties of
document ("Feedback"). merchantability and fitness for a particular purpose,

2 RN3710AEN16GLA0 © 2016 Nokia

Resource Manager:
Module Objectives

At the end of the module you will be able to:

• Explain the functions of Resource Manager

• Explain Channelization Code allocation strategies
• Explain code tree usage optimization & parameters

4 RN3710AEN16GLA0 © 2016 Nokia

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 CodeTreeOptimization
• Transport resource manager WCEL; 0 (not used);
• RNC HW manager (L1/L2) 1 (used)
• Maintains the code tree
• allocates the DL Channelization Codes, UL Scrambling Code,
UL Channelization Code type
• 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

5 RN3710AEN16GLA0 © 2016 Nokia

Resource Manager

• DL: Scrambling codes separate the cells (sectors); Channelization codes separate
• UL: Scrambling Codes separate the UEs
• All physical channels are spread with individual Channelization Codes, Cm(n) and
subsequently by the scrambling code, CFSCR

User Widespread
data data

Channelization Scrambling
Code Code

6 RN3710AEN16GLA0 © 2016 Nokia

Channelization Code Allocation

• Code Allocation Algorithm chooses the correct Channelization Code depending on the TFC
C 3 (0)=(…)
C 2 (0)=(1,1,1,1)
C 3 (1)=(…)
C 1 (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)=(…)
C 1 (1)=(1,-1)
C 3 (6)=(…)
C 2 (3)=(1,-1,-1,1)
C 3 (7)=(…)
Code Order Code Order Code Order 2 Code Order
0 (SF 1) 1 (SF 2) (SF 4) 3 (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 256) are available
• In UL code order 2 to 8 (SF 4 to 256) are available

7 RN3710AEN16GLA0 © 2016 Nokia

Spreading Code Allocation – Example

Ordinary DL speech channel, requires 30 ksps physical capacity (AMR 12.2 – 4.75 kbit/s).
The code order is 7, which means there are 128 chips to illustrate 1 symbol (2 n, n=7).
If the requested channel is 120 kbit/s (including DPCCH & channel coding) data
channel, then the code order is 5.

Code Channel Channel

Order symbolrate bitrate SF
(ksps) (kbps)

9 15 7.5 512 40

8 30 15 256 160
low rate AMR Speech possible
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 RN3710AEN16GLA0 © 2016 Nokia

DL Code Allocation – Common Channels
SF = 1
• Pilot (P-CPICH) and BCCH (P-CCPCH) have fixed code allocation
• P-CPICH: CH SF = 2
• P-CCPCH: CH256,1
SF = 4
• AICH and PICH codes in Nokia RAN
• AICH: CH256,2 SF = 8
• PICH: CH256,3
• S-CCPCH code allocation depends
SF = 16
on number of active S-CCPCH in Nokia RAN
• With 1 S-CCPCH: CH64,1
SF = 32

SF = 64 S-CCPCH1
SF = 128 X

SF = 256 X X


Codes for the cell common channels

9 RN3710AEN16GLA0 © 2016 Nokia
DL Code Allocation
When HSDPA is enabled at least 5 codes are allocated
Code allocation is dynamic from RAS06 on 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
Code for one
Codes for the cell common channels

max. 166 codes @ SF=256 available for the associated DCHs & non-HSDPA users,
if five HS-PDSCHs and one HS-SCCH are allocated
when code multiplexing is used, up to 4 HS-SCCH are transmitted and need a code

10 RN3710AEN16GLA0 © 2016 Nokia

Code Tree Optimization / De-fragmentation
• A code is always allocated from the optimum location in the code tree. It makes WCEL; 0 (not used);
the allocated code and the codes in the branches below and above the allocated 1 (used)
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 WCEL; 1..65535; 1;

min. usage of code tree
before rearrangement
0..100%; 1%;

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

11 RN3710AEN16GLA0 © 2016 Nokia

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 except 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 + n*m ULScrCodeMin
• where n is the number of ICSUs in the RNC & RNAC; 8192..16777215; 1; 1000000
m=8192 is the max number of user/ ICSU
• This suggests careful configuration when considering HW upgrades to avoid overlaps
ICSU: Interference Control & Signaling Unit

12 RN3710AEN16GLA0 © 2016 Nokia

RN3710AEN16GLA0 © 2016 Nokia