Feature Deployment and Testing Guide

Code Resource Allocation

Feature ID: ZWF21-04-006

Version: V3.11.10

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-08-09 First edition

Serial Number: SJ-20120802112720-049

Publishing Date: 2012-08-09 (R1.0)

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Preparations .............................................................................. 2-1
Chapter 3 Data configuration .................................................................... 3-1
Chapter 4 Testing ....................................................................................... 4-1
4.1 Test Purpose...................................................................................................... 4-1
4.2 Steps for Test..................................................................................................... 4-1
4.3 Expected Results ............................................................................................... 4-2

Chapter 5 Counter List............................................................................... 5-1

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 II

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 1
Functional Description
As a spread spectrum communication system based on CDMA technology , Wideband
Code Division Multiple Access (WCDMA) differentiates user equipments (UEs) by using
scrambling codes (SC) in the uplink direction, and spreads the spectrum by using the
channelization codes (CC) of the Orthogonal Variable Spreading Factor (OVSF). In
the downlink direction, WCDMA differentiates cells by using the primary scrambling
codes (PSC), and spreads the spectrum by using CCs of the OVSF. WCDMA is used to
differentiate downlink channels in the same cell. The following figure shows the spreading
and scrambling process of WCDMA.

In the downlink direction, WCDMA contains a total of 8,192 SCs divided into 512 groups,
each of which contains one PSC and 15 secondary scrambling codes (SSC). Each cell is
assigned a unique PSC and corresponding SSC group. PSCs are used for the downlink
common channel to differentiate various cells.
In the downlink direction, WCDMA spreads the spectrum for channels by using the CCs of
the OVSF, and separates various downlink channels by using the orthogonality of different
CCs. The OVSF codes can be indicated through a code tree. A code in the code tree
can be expressed as Cch,SF,k, where, SF refers to the spreading factor, and k refers
to the code number (the number ranges from 0 to SF-1). The codes of the same SF
in the OVSF code tree are mutually orthogonal, the codes with different SFs in different
code tree branches are also mutually orthogonal, and the codes with different SFs in
the same code tree are not mutually orthogonal. But downlink channels are required to
be mutually orthogonal. Once a code is assigned, its lower-layer low-rate code nodes
and upper-layer high-speed code nodes in the corresponding code tree can no longer be
assigned, that is, they are blocked. Due to these features, the downlink CCs become
a limited resource. Irrational allocation of CCs reduces system capacity. Therefore, the
allocation and management of downlink CCs is crucial to the WCDMA system.

WCDMA has a total of 224 long SCs and 224 short SCs available in the uplink direction.
There are enough SC resources in uplink. When allocating SC resources, each UE shall
be assigned a different SC. When the spectrum is spread for the dedicated channel in the

1-1

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-04-006

uplink direction, each UE can use all CCs in a CC tree without sharing CCs with other UEs.
3gpp expressly stipulates the rules of allocating the SCs and CCs in the uplink common
channel.

When HSDPA and R99 use the same carrier frequency, the HSDPA service throughput of
each cell is affected by the number of the HS-PDSCHs, that is, the number of the codes with
the SF of 16 allocated to a HS-PDSCH. ZTE RNC supports dynamic or static allocation of
the HS-PDSCHs. Dynamic allocation can flexibly and quickly reflect the change of system
load.
ZTE RNC supports dynamic allocation of the CCs of the downlink HS-PDSCHs
and physical HS-SCCHs, that is, support the manually configuring of the number of
HS-PDSCH/HS-SCCH CCs in OMCR.

Support the reallocation of HS-PDSCCH/HS-SCCH CCs (increase or decrease the

number of these channels).
According to the data throughput of the HSDPA services and flow demand of the R99
services, the HS-PDSCH resources are dynamically adjusted and the CCs of the downlink
HS-PDSCHs are dynamically allocated. The number of HS-PDSCH CCs is re-estimated in
two ways:1.Fast prediction & adjustment mode; 2. Allocate HS-PDSCHs and total power
dynamically according to the congestion status, and re-allocate CCs.
The dynamic allocation of codes of the HSDPA also includes the dynamic adjustment of
code resource between the HSDPA and R99 service.

Code resource control is to allocate downlink CCs to cells dynamically according to certain
rules with a view to maximizing the utilization of code resources and increasing system
capacity.

The OVSF codes are used for the spread spectrum of the downlink. The mutually
orthogonal downlink spread spectrum codes are allocated to different channels. The
OVSF is expanded through a binary tree. The codes at the same layer are mutually
orthogonal, so do the codes that are in different layers and have no direct inheritance
relation. If a code is used, the lower-layer codes and the codes at the same branch from

1-2

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 1 Functional Description

this code to the code tree root are not available. Therefore, the downlink code resources
of each cell are limited and should be fully utilized.
Downlink CCs are allocated to a cell according to its level. The downlink CCs of the
common channel are first allocated when the cell is established. The downlink CCs of
the dedicated channel are dynamically allocated when the channel is established.
The code resources should be utilized to the utmost. During service setup, the RNC
calculates the SF according to the service rate, and allocates the corresponding CCs.
After the service is released, the CCs should also be released so as to allocate them to
other UEs. For each cell, the RNC maintains a CC table. The CC table records the status
of each code, for example, idle, allocated or shielded. When code resources are allocated,
prevent the idle code resource block caused by the allocation of codes from being shielded.

When HSDPA and R99 use the same carrier frequency, the HSDPA service throughput of
each cell is affected by the number of the HS-PDSCHs, that is, the number of the codes with
the SF of 16 allocated to a HS-PDSCH. ZTE RNC supports dynamic or static allocation of
the HS-PDSCHs. Dynamic allocation can flexibly and quickly reflect the change of system
load.
ZTE RNC supports dynamic allocation of the CCs of the downlink HS-PDSCHs and
physical HS-SCCHs, that is,

l Support the manually configuring of the number of HS-PDSCH/HS-SCCH CCs in

OMCR
l Support the reallocation of HS-PDSCCH/HS-SCCH CCs (increase or decrease the
number of these channels)
According to the data throughput of the HSDPA services and flow demand of the R99
services, the HS-PDSCH resources are dynamically adjusted and the CCs of the downlink
HS-PDSCHs are dynamically allocated. The number of HS-PDSCH CCs is re-estimated in
two ways:1.Fast prediction & adjustment mode; 2. Allocate HS-PDSCHs and total power
dynamically according to the congestion status, and re-allocate CCs.

The dynamic allocation of codes of the HSDPA also includes the dynamic adjustment of
code resource between the HSDPA and R99 service.
The HSUPA introduces three types of physical channels (E-AGCH, E-RGCH, and
E-HICH). The SF of an E-AGCH SF is 256, and the SF of a RGCH/E-HICH is 128. The
E-RGCH and E-HICH can use the same SF. They are discriminated through the signature
sequence. The E-RGCH, E-HICH, and E-AGCH have the same scrambling code.

The HSUPA code resources of the E-AGCH, E-RGCH, and E-HICH can be configured on
this principle: One E-RGCH/E-HICH channel can be shared by a maximum of 20 HSUPA
UEs, and one E-AGCH can be shared by a maximum of 16 to 25 HSUPA UEs.
RNC allocates the code resources for the PRACH ， AICH ， F-DPCH ， E-AGCH and
E-RGCH/HICH in uplink enhanced CELL_FACH when the cell is established. There are
only one PRACH, AICH and E-AGCH for the uplink enhanced CELL_FACH. RNC has
at most 32 resource configuration, and configure F-DCH/ E-RGCH/HICH information for
every resource.

1-3

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-04-006

This page intentionally left blank.

1-4

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 2
Preparations
License
N/A

Hardware Requirement
Hardware requirement is shown in Table 2-1.

Table 2-1 Hardware Requirement

NE Requirement

RNC None

NodeB None

Software Requirement
Software requirement is shown in Table 2-2.

Table 2-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 2

Category: None
Release : R99

NodeB YES V4.11.10.14

RNC YES V3.11.10.11

MSCS YES ZTE equipment

MGW YES ZTE equipment

SGSN YES ZTE equipment

GGSN NO

HLR NO

Topology
Topology is shown in Figure 2-1.

2-1

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-04-006

Figure 2-1 Topology

2-2

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 3
Data configuration
SGSN/GGSN - ZTE
N/A

MSC/MGW - ZTE
N/A

HLR – ZTE
N/A

RNC
N/A

NodeB
N/A

3-1

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-04-006

This page intentionally left blank.

3-2

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 4
Testing
Table of Contents
Test Purpose ..............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-2

4.1 Test Purpose

The purpose of this test case is to verify if the function of Code Resource Allocation is
working normally.
Related documents:
l ZTE UMST Code Resource Allocation Feature Guide.

4.2 Steps for Test

1. Before CS voice call is established, the code usage is like the following figure:

2. UE1 makes a CS voice call to UE2 in Cell1.

4-1

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-04-006

3. After CS voice call is established, the code usage is like the following figure.

CS voice call(12.2kbps) uses the SF128 code, we can find one UE used SF(128,11),
another used SF(128,12).
UE1 uses code SF(128,11)

UE2 uses code SF(128,12)

4.3 Expected Results

Two more SF128 code is used after the CS voice call established (Each UE uses one
SF128).

4-2

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 5
Counter List
Counter No. Description

C310424227 Current available ratio of code resource

C310424228 Maximum available ratio of code resource

C310426478 Minimum available ratio of code resource

C310424230 Sum available ratio of code resource

C310424231 Statistics times of code resource

C310424265 Current Number of Code Node Used, SF=128

C310424266 Maximum Number of Code Node Used, SF=128

C310426493 Minimum Number of Code Node Used, SF=128

C310424268 Summation Number of Code Node Used, SF=128

C310424269 Current Number of Code Node Free, SF=128

C310424270 Maximum Number of Code Node Free, SF=128

C310426496 Minimum Number of Code Node Free, SF=128

C310424272 Summation Number of Code Node Free, SF=128

C310424315 Times of 0 Code Node Used,SF=128

C310424316 Times of Code Node Used between 1 to 4, SF=128;

C310424317 Times of Code Node Used between 5 to 8, SF=128;

C310424318 Times of Code Node Used between 9 to 12, SF=128;

C310424319 Times of Code Node Used between 13 to 16, SF=128;

C310424320 Times of Code Node Used between 17 to 20, SF=128;

C310424321 Times of Code Node Used between 21 to 24, SF=128;

C310424322 Times of Code Node Used between 25 to 28, SF=128;

C310424323 Times of Code Node Used between 29 to 32, SF=128;

C310424324 Times of Code Node Used between 33 to 36, SF=128;

C310424325 Times of Code Node Used between 37 to 40, SF=128;

C310424326 Times of Code Node Used between 41 to 44, SF=128;

C310424327 Times of Code Node Used between 45 to 48, SF=128;

C310424328 Times of Code Node Used between 49 to 52, SF=128;

5-1

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-04-006

Counter No. Description

C310424329 Times of Code Node Used between 53 to 56, SF=128;

C310424330 Times of Code Node Used between 57 to 60, SF=128;

C310424331 Times of Code Node Used between 61 to 64, SF=128;

C310424332 Times of Code Node Used between 65 to 68, SF=128;

C310424333 Times of Code Node Used between 69 to 72, SF=128;

C310424334 Times of Code Node Used between 73 to 76, SF=128;

C310424335 Times of Code Node Used between 77 to 80, SF=128;

C310424336 Times of Code Node Used between 81 to 84, SF=128;

C310424337 Times of Code Node Used between 85 to 88, SF=128;

C310424338 Times of Code Node Used between 89 to 92, SF=128;

C310424339 Times of Code Node Used between 93 to 96, SF=128;

C310424340 Times of Code Node Used between 97 to 100, SF=128;

C310424341 Times of Code Node Used between 101 to 104, SF=128;

C310424342 Times of Code Node Used between 105 to 108, SF=128;

C310424343 Times of Code Node Used between 109 to 112, SF=128;

C310424344 Times of Code Node Used between 113 to 116, SF=128;

C310424345 Times of Code Node Used between 117 to 120, SF=128;

C310424346 Times of Code Node Used between 121 to 124, SF=128;

C310424347 Times of Code Node Used between 125 to 128, SF=128;

5-2

SJ-20120802112720-049|2012-08-09 (R1.0) ZTE Proprietary and Confidential