11 Rn3163ben50gla0 Ranpar 1 Resourcemanager v1.0 Ru50 Nokia

27/01/2015 © Nokia 2014 - RN31679EN50GLA1 1 1 RN3163BEN50GLA0 © Nokia Solutions and Networks 2015

Resource Manager

2 RN3163BEN50GLA0 © Nokia Solutions and Networks 2015

Copyright and confidentiality

The contents of this document are proprietary and

confidential property of Nokia Solutions and Networks.

This document is provided subject to confidentiality

obligations of the applicable agreement(s).

This document is intended for use of Nokia Solutions

and Networks customers and collaborators only for the

purpose for which this document is submitted by Nokia

Solutions and Networks. No part of this document may

be reproduced or made available to the public or to any

third party in any form or means without the prior

written permission of Nokia Solutions and Networks.

This document is to be used by properly trained

professional personnel. Any use of the contents in this

document is limited strictly to the use(s) specifically

created in the applicable agreement(s) under which the

document is submitted. The user of this document may

voluntarily provide suggestions, comments or other

feedback to Nokia Solutions and Networks in respect of

the contents of this document ("Feedback"). Such

Feedback may be used in Nokia Solutions and

Networks products and related specifications or other

documentation. Accordingly, if the user of this

document gives Nokia Solutions and Networks

feedback on the contents of this document, Nokia

Solutions and Networks may freely use, disclose,

reproduce, license, distribute and otherwise

commercialize the feedback in any Nokia Solutions and

Networks product, technology, service, specification or

other documentation.

Nokia Solutions and Networks operates a policy of

ongoing development. Nokia Solutions and Networks

reserves the right to make changes and improvements

to any of the products and/or services described in this

document or withdraw this document at any time

without prior notice.

The contents of this document are provided "as is".

Except as required by applicable law, no warranties of

any kind, either express or implied, including, but not

limited to, the implied warranties of merchantability and

fitness for a particular purpose, are made in relation to

the accuracy, reliability or contents of this document.

NOKIA SOLUTIONS AND NETWORKS SHALL NOT

BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN

THIS DOCUMENT or for any loss of data or income or

any special, incidental, consequential, indirect or direct

damages howsoever caused, that might arise from the

use of this document or any contents of this document.

This document and the product(s) it describes are

protected by copyright according to the applicable laws.

Nokia is a registered trademark of Nokia Corporation.

Other product and company names mentioned herein

may be trademarks or trade names of their

respective owners.

© Nokia Solutions and Networks 2014


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


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,

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

CodeTreeOptimisation WCEL; 0 (not used);

1 (used)


Resource Manager

• DL: Scrambling codes separate the cells (sectors); Channelization codes separate

connections

• 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

data

Widespread

data

Channelization

Code

(Spreading

Code)

Scrambling

Code


Channelization Code Allocation

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

C 0 (0)=(1)

C 1 (0)=(1,1)

C 1 (1)=(1,-1)

C 2 (0)=(1,1,1,1)

C 2 (1)=(1,1,-1,-1)

C 2 (2)=(1,-1,1,-1)

C 2 (3)=(1,-1,-1,1)

C 3 (0)=(…)

C 3 (1)=(…)

C 3 (2)=(…)

C 3 (3)=(…)

C 3 (4)=(…)

C 3 (5)=(…)

C 3 (6)=(…)

C 3 (7)=(…)

Code Order 0 (SF 1)

Code Order 1 (SF 2)

Code Order 2 (SF 4)

Code Order 3 (SF 8)

• Code Allocation Algorithm chooses the correct Channelization Code depending on the TFC type


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 (2n, n=7).

If the requested channel is 120 kbit/s (including DPCCH & channel coding) data

channel, then the code order is 5.

Code Order

Channel symbolrate

(ksps)

Channel bitrate (kbps)

SF DPDCH

bits/frame

9 15 7.5 512 40

8 30 15 256 160

7 60 30 128 340

6 120 60 64 600

5 240 120 32 1400

4 480 240 16 2880

3 960 480 8 6080

2 1920 960 4 12480

AMR Speech

64 kbps data

128 kbps data

384 kbps data

low rate AMR Speech possible


SF = 128

SF = 256

SF = 64

SF = 32

SF = 8

SF = 16

SF = 4

SF = 2

SF = 1

Codes for the cell common channels

Code for one

HS-SCCH

Codes for 5

HS-PDSCH's

DL Code Allocation – Common Channels

• Pilot (P-CPICH) and BCCH (P-CCPCH) have fixed code allocation

• P-CPICH: CH256,0

• P-CCPCH: CH256,1

• AICH and PICH codes in Nokia RAN

• AICH: CH256,2

• PICH: CH256,3

• S-CCPCH code allocation depends on number of active S-CCPCH in Nokia RAN

• With 1 S-CCPCH: CH64,1

P-C

PIC

H

P-C

CP

CH

AIC

H

PIC

H

S-CCPCH1

(FACH)

X X

X


SF = 128

SF = 256

SF = 64

SF = 32

SF = 8

SF = 16

SF = 4

SF = 2

SF = 1

Codes for the cell common channels

Code for one

HS-SCCH

Codes for 5

HS-PDSCH's

• 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

• When HSDPA is enabled at least 5 codes are allocated

• Code allocation is dynamic from RAS06 on when more than 5 codes are allocated

DL Code Allocation


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

• 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

CodeTree

Optimisation WCEL; 0 (not used);

1 (used)

CodeTree

OptTimer WCEL; 1..65535; 1;

3600s

CodeTreeUsage min. usage of code tree

before rearrangement

WCEL;

0..100%; 1%;

40%

MaxCode

Releases Max. code releases

before rearrangement

WCEL; 1..65535; 1; 40


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

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

• 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 & signaling Unit

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

ULScrCodeMin RNAC; 8192..16777215; 1; 1000000

11 Rn3163ben50gla0 Ranpar 1 Resourcemanager v1.0 Ru50 Nokia

Documents

Transcript of 11 Rn3163ben50gla0 Ranpar 1 Resourcemanager v1.0 Ru50 Nokia