ZWF23!04!021 Code Sharing Between Cells

Feature Deployment and Testing GuideCode Sharing Between CellsFeature ID:ZWF23-04-021

Version: V3.11.10

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 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-6-18 First eition

Serial Number: SJ-20120802112720-191

Publishing Date: 2012-06-18 (R1.0)

SJ-20120802112720-191|2012-06-18 (R1.0) ZTE Proprietary and Confidential

ContentsChapter 1 Functional Description............................................................. 1-1

Chapter 2 Preparations.............................................................................. 2-1

Chapter 3 Data configuration .................................................................... 3-1

Chapter 4 Testing ....................................................................................... 4-14.1 Test Purpose...................................................................................................... 4-1

4.2 Steps for Test..................................................................................................... 4-1

4.3 Expected Results ............................................................................................... 4-1

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

I


II


Chapter 1Functional DescriptionAs a spread spectrum communication system based on CDMA technology , WidebandCode Division Multiple Access (WCDMA) differentiates user equipments (UEs) by usingscrambling codes (SC) in the uplink direction, and spreads the spectrum by using thechannelization codes (CC) of the Orthogonal Variable Spreading Factor (OVSF). Inthe downlink direction, WCDMA differentiates cells by using the primary scramblingcodes (PSC), and spreads the spectrum by using CCs of the OVSF. WCDMA is used todifferentiate downlink channels in the same cell. The following figure shows the spreadingand 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 isassigned a unique PSC and corresponding SSC group. PSCs are used for the downlinkcommon channel to differentiate various cells.

In the downlink direction, WCDMA spreads the spectrum for channels by using the CCs ofthe OVSF, and separates various downlink channels by using the orthogonality of differentCCs. The OVSF codes can be indicated through a code tree. A code in the code treecan be expressed as Cch,SF,k, where, SF refers to the spreading factor, and k refersto the code number (the number ranges from 0 to SF-1). The codes of the same SFin the OVSF code tree are mutually orthogonal, the codes with different SFs in differentcode tree branches are also mutually orthogonal, and the codes with different SFs inthe same code tree are not mutually orthogonal. But downlink channels are required tobe mutually orthogonal. Once a code is assigned, its lower-layer low-rate code nodesand upper-layer high-speed code nodes in the corresponding code tree can no longer beassigned, that is, they are blocked. Due to these features, the downlink CCs becomea limited resource. Irrational allocation of CCs reduces system capacity. Therefore, theallocation 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 shallbe assigned a different SC. When the spectrum is spread for the dedicated channel in the

1-1


Feature Deployment and Testing Guide Feature ID:ZWF23-04-021

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 commonchannel.

When HSDPA and R99 use the same carrier frequency, the HSDPA service throughput ofeach cell is affected by the number of the HS-PDSCHs, that is, the number of the codeswiththe SF of 16 allocated to a HS-PDSCH. ZTE RNC supports dynamic or static allocation ofthe HS-PDSCHs. Dynamic allocation can flexibly and quickly reflect the change of systemload.

ZTE RNC supports dynamic allocation of the CCs of the downlink HS-PDSCHs andphysical 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 thenumber of these channels)

According to the data throughput of the HSDPA services and flow demand of the R99services, the HS-PDSCH resources are dynamically adjusted and the CCs of the downlinkHS-PDSCHs are dynamically allocated. The number of HS-PDSCHCCs is re-estimated intwo ways:1.Fast prediction & adjustment mode; 2. Allocate HS-PDSCHs and total powerdynamically according to the congestion status, and re-allocate CCs.

The dynamic allocation of codes of the HSDPA also includes the dynamic adjustment ofcode resource between the HSDPA and R99 service.

Due to the different development of services in each cell, the operator purchases differentnumber of HS-PDSCH code resources to satisfy the need of services. Every cell needsdifferent number of HS-PDSCH code resources in the different moment. Some cells do notneed so much code resources as the purchased code resources, while some need more.In order to satisfy the need of services and to reduce the operation cost, the cells of thesame Node B can share the HS-PDSCH code resources. The RNC periodically or whenCo-NodeB cells have changed calculates the maximum HS-PDSCH channel number foreach of the cells according to the need of services. The actually allocated code resourcesfor each cell are no more than this maximum value.

1-2


Chapter 2PreparationsLicense

Feature License

ZWF23-04-021 Code Sharing between Cells 　WCDMA whether permit to share code

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.

2-1



Table 2-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 1

Category: Any

Release : R6

NodeB YES V4.11.10.14

RNC YES V3.11.10.11

MSCS YES V3.10.20.P6.B1 ZTE equipment

MGW YES V3.10.20.P4.B3 ZTE equipment

SGSN YES V3.10.10.P2.B5N ZTE equipment

GGSN NO

HLR NO

Topology

Topology is shown in Figure 2-1.

Figure 2-1 Topology

2-2


Chapter 3Data configurationSGSN/GGSN - ZTE

N/A

MSC/MGW - ZTE

N/A

HLR – ZTE

UE1 subscribes background 8192kbps/2048kbps. Set allocation or retention priorityparameter in HLR.

RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = TRANAP_background

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 8192000

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[1] = 2048000

RNC

l HSPA Support Method：Support HSUPA HSDPA and DCH

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and CellReselection > HSPA Support Method

3-1



l Number of HS-PDSCH:1

Minimum Number of HS-PDSCH:1

Maximum Number of HS-PDSCH:5

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and CellReselection > Number of HS-PDSCH

l Co-NodeB HS-PDSCH Code Sharing Indicator : Sharing

3-2


Chapter 3 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Advanced Parameter> HSPA Configuration Information In A Cell

l Share cover Indication(cell2 as cell1’s adjacent cell) : Overlap

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Neighbouring Cell >cell UTRAN Cell xxx > Share cover Indication

l Share cover Indication(cell1 as cell2’s adjacent cell) : Overlap

3-3



Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Neighbouring Cell >cell UTRAN Cell xxx > Share cover Indication

l Co-NodeB HS-PDSCH Code Sharing Method : RNC Control

Path: View > Configuration Management > RNC Managed Element > RNCRadio Resource Management > NodeB Configuration Information > NodeBxxx > NodeB Configuration Information > Co-NodeB HS-PDSCH Code SharingMethod

NodeB

N/A

3-4


Chapter 4TestingTable of Contents

Test Purpose ..............................................................................................................4-1Steps for Test .............................................................................................................4-1Expected Results .......................................................................................................4-1

4.1 Test PurposeThe purpose of this test case is to verify if the function of Code Sharing between Cells isworking normally.

Related documents:

l ZTE UMST Code Resource Allocation Feature Guide

4.2 Steps for Test1. UE1 activates a PS call in Cell1 and starts FTP downloading.

4.3 Expected ResultsThe average DL data rate of the FTP downloading is more than 5.8M.

4-1



From the LMT, we can see the code number used by UE1 is 10. But the maximum numberof codes in Cell1 is 5. The other 5 codes in them are borrowed from Cell2.

4-2


Chapter 5Counter List

C310424227 Current available ratio of code resource

C310424228 Maximum available ratio of code resource

C310426478 Minimum available ratio of code resource

C310424241 Current Number of Code Node Used, SF=16

C310424242 Maximum Number of Code Node Used, SF=16

C310426483 Minimum Number of Code Node Used, SF=16

C310424408 Times of 10 Code Node Used,SF=16

C310434426 Current number of HS-PDSCH code nodes used

C310434427 Max number of HS-PDSCH code nodes used

C310436502 Min number of HS-PDSCH code nodes used

C310435946 Current occupation ratio of HSDPA code resource

C310434433 Maximum occupation ratio of HSDPA code

resource

C310436506 Minimum occupation ratio of HSDPA code

resource

5-1


Documents

ZWF23!04!021 Code Sharing Between Cells