Académique Documents
Professionnel Documents
Culture Documents
Feature ID:ZWF23-04-021
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.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2012-6-18
First eition
SJ-20120802112720-191|2012-06-18 (R1.0)
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-1
I
SJ-20120802112720-191|2012-06-18 (R1.0)
II
SJ-20120802112720-191|2012-06-18 (R1.0)
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-191|2012-06-18 (R1.0)
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.
Due to the different development of services in each cell, the operator purchases different
number of HS-PDSCH code resources to satisfy the need of services. Every cell needs
different number of HS-PDSCH code resources in the different moment. Some cells do not
need 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 the
same Node B can share the HS-PDSCH code resources. The RNC periodically or when
Co-NodeB cells have changed calculates the maximum HS-PDSCH channel number for
each of the cells according to the need of services. The actually allocated code resources
for each cell are no more than this maximum value.
1-2
SJ-20120802112720-191|2012-06-18 (R1.0)
Chapter 2
Preparations
License
Feature
License
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
SJ-20120802112720-191|2012-06-18 (R1.0)
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
SJ-20120802112720-191|2012-06-18 (R1.0)
Chapter 3
Data configuration
SGSN/GGSN - ZTE
N/A
MSC/MGW - ZTE
N/A
HLR ZTE
UE1 subscribes background 8192kbps/2048kbps.
parameter in HLR.
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.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
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and Cell
Reselection > HSPA Support Method
3-1
SJ-20120802112720-191|2012-06-18 (R1.0)
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 Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and Cell
Reselection > Number of HS-PDSCH
l
3-2
SJ-20120802112720-191|2012-06-18 (R1.0)
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Advanced Parameter
> HSPA Configuration Information In A Cell
l
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Neighbouring Cell >
cell UTRAN Cell xxx > Share cover Indication
l
3-3
SJ-20120802112720-191|2012-06-18 (R1.0)
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Neighbouring Cell >
cell UTRAN Cell xxx > Share cover Indication
l
Path: View > Configuration Management > RNC Managed Element > RNC
Radio Resource Management > NodeB Configuration Information > NodeB
xxx > NodeB Configuration Information > Co-NodeB HS-PDSCH Code Sharing
Method
NodeB
N/A
3-4
SJ-20120802112720-191|2012-06-18 (R1.0)
Chapter 4
Testing
Table of Contents
Test Purpose ..............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-1
4-1
SJ-20120802112720-191|2012-06-18 (R1.0)
From the LMT, we can see the code number used by UE1 is 10. But the maximum number
of codes in Cell1 is 5. The other 5 codes in them are borrowed from Cell2.
4-2
SJ-20120802112720-191|2012-06-18 (R1.0)
Chapter 5
Counter List
C310424227
C310424228
C310426478
C310424241
C310424242
C310426483
C310424408
C310434426
C310434427
C310436502
C310435946
C310434433
C310436506
5-1
SJ-20120802112720-191|2012-06-18 (R1.0)