Feature Deployment and Testing Guide

QoS Mapping for HSUPA Service

Feature ID: ZWF25-05-001

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

Serial Number: SJ-20120802112720-228

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

SJ-20120802112720-228|2012-06-18 (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-3

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

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

 II

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

 Chapter 1
Functional Description
RNC maps RAB QoS parameters from CN to the basic priority used in the UTRAN. And
RNC maps basic priority to Scheduling Priority Indicator (SPI)for HSUPA service.
The HSUPA packet scheduler determines system resource utilization and load based on
the following information, and then allocates system resources to different UEs by following
certain priority policy:
l Uplink Reference Received Total Wide Band Power (RefRTWP) configured by RNC
through NBAP.
l Maximum Target Received Total Wideband Power (MaxRTWP) (refer to ZXWR RNC
Radio Network Controller Radio Parameter Reference (Volume II)).
l Target Non-serving E-DCH to Total E-DCH Power Ratio (NServToTotalPwr) (refer to
ZTE UTMS Overload Control Feature User Guide).
l UE reported status information.
l UE QoS configured by RNC through NBAP.
l Cell radio resources.
l Node B resource processing resources information.
The operating mechanism of the HSUPA packet scheduler is shown as follows:

Figure 1-1 Operating mechanism of HSUPA packet scheduler

1-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

The following figure shows the HSUPA scheduling procedure:

Figure 1-2 HSUPA scheduling procedure in Node B

The key algorithm of the scheduler implements scheduling in the following steps:
1. Collect and update UE status, cell radio resource and Node B processing information.
Collected information includes:
l The SI reported by UE (including SI and happy bit, used to obtain buffer area size
and UPH of UE).
l E-TFCI currently used by UE and MAC-e PDU multiplexing information (contained
in MAC-e PDU head and used to obtain the type of MAC-e PDU currently sent by
UE and data volume).
l Current DPCCH and E-DCH signal quality of UE (SIR and Eb/No, reported by the
Baseband Processing Unit and used to calculate UE-contributed load).
l QoS parameter configured by RNC for UE services: Scheduling Priority Indicator
(SPI) (This parameter is configured for Node B by RNC based on the service type
through NBAP. For details, refer to ZTE UMTS QoS Feature User Guide).
l QoS parameter configured by RNC for UE services: MAC-es Guaranteed Bit
Rate (This parameter is configured for Node B by RNC based on the service type
through NBAP. For details, refer to ZTE UMTS QoS Feature User Guide).
l QoS parameter configured by RNC for UE services: Maximum Number of
Bits per MAC-e PDU for Non-scheduled Transmission (The independent data
transmission capability obtained by UE without scheduling. This parameter is
configured for Node B by RNC based on the service type through NBAP).

1-2

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

 Chapter 1 Functional Description

l Cell interference information (RTWPcurrent is measured at Node B).

l CE resource indication.
l Reference Received Total Wide Band Power (RefRTWP), Maximum Target
Received Total Wideband Power (MaxRTWP), Target Non-serving E-DCH to
Total E-DCH Power Ratio (NServToTotalPwr) configured by RNC through NBAP.
2. Determine UE, air interface and Node B resource utilization and load:
l The measurement unit of Node B measures air interface interference, and sends
the measurement result RTWPcurrent to the scheduler. The scheduler calculates
current cell load Cell_Load_current and maximum target load Cell_Load_max (unit: %)
through the following equations:
RoT = Itotal/Pn (1)
Cell_Load_current = 11/RoT (2)
Cell_Load_max = 11/(MaxRTWP /Pn) (3)
Itotal refers to the total receive bandwidth power inclusive of background noise
power (unit: mW) and takes the value of RTWPcurrent.
Pn refers to background noise and takes the value of RefRTWP (Reference
Received Total Wide Band Power). The original unit of Pn is dBm and translated
into mW in the above equation. RNC notifies of Node B of Pn through NBAP
after internal measurement.
MaxRTWP refers to the Maximum Target Received Total Wideband Power. The
original unit of MaxRTWP is dBm and translated into mW in the above equation.
MaxRTWP is configured at combining and sent to Node B by RNC through NBAP.
RoT refers to Rise over Thermal. The original unit of RoT is dB, and converted
into dimensionless ratio during calculation.
l The scheduler calculates UE-contributed load by using the following method:
The Uplink Process Unit of Node B demodulates E-DPDCH in each TTI to obtain
MAC-e PDU, SI and Eb/No, and sends MAC-e PDU multiplexing information to
the scheduler which calculates UE-contributed load in the following equation:
UEload = 1/(1+(W/((Eb/No)R))) (4)
Where,
Itotal refers to the total receive bandwidth power inclusive of background noise
power (unit: mW) and takes the value of RTWPcurrent.
W refers to WCDMA chip rate and equals to 3.84M chips/s.
Eb/No refers to per bit signal energy divided by noise power spectral density, and
reflects service signal quality. It is dimensionless
R refers to the bit rate of UE (unit: bits/s).
3. Determine UE scheduling priority in HSUPA cell.
The HSUPA scheduler adopts the Enhanced Proportional Fair (PF) Algorithm, and
calculates scheduling priority which is a variable for each UE based on realtime

1-3

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

collected parameters, so as to ensure traffic fairness among UEs and make full use
of system resources as well. The PF algorithm features the following:
l The scheduling priority is in direct proportion to current uplink to-be-transmitted
data volume (or current available transmission rate), that is, the larger the data
volume in the buffer area of UE, the higher the scheduling priority and the more
chance the UE will be scheduled preferentially.
l The scheduling priority is in reverse proportion to the uplink average throughput
(or history throughput) of UE, that is, the lower the average throughput, the higher
the scheduling priority. The UE with low transmission throughput will be scheduled
preferentially so as to ensure fairness.
UEs with higher scheduling priorities will take precedence over UEs with lower ones in
preempting more resources, resulting in rate decrease for the latter. But UEs originally
with lower scheduling priorities are given higher scheduling priorities because of their
low transmission throughput, and thus they will be scheduled preferentially to ensure
fairness among all UEs.
The specific calculation procedure of scheduling priority is as follows:
At first, the average uplink throughput Rn obtained by UE m (the mth UE) before n
TTI(s) (n refers to current time).

The uplink throughput offered for UEs in past TTIs can be updated for all UEs in each
TTI by using the recursive expression:
l If services are offered for UE m:

Rn = (1-a)Rn-1 + aDn (5)

l Other cases:
Rn = (1-a)Rn-1 (6)
Rn-1 refers to the value of Rn in last TTI (Unit: bits/s).
R0 refers to the uplink rate of UE at initial moment (Unit: bits/s).
Dn refers to available uplink transmission rate of UE (Unit: bits/s), and takes the
smallest one of the following values: Data size in UE buffer area, size of data that
can be transmitted in relation to the rest power of UE, and maximum rate limit of
UE.
n refers to the nth transmission moment.

m refers to the mth UE.

a refers to forgetting factor. 1/a indicates the tolerability when a UE group cannot
receive data. It is an internal parameter and cannot be configured.

l Then calculate the scheduling priority of all UEs in a cell:

Priority = (Dn/Rn)^ FairnessWgtQoSweightUE_buff_status (7)

FairnessWgt refers to fairness factor. It is an internal parameter (value: 1) and

cannot be configured.

1-4

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

 Chapter 1 Functional Description

UE_buff_status: Refers to information about buffer area size in SI reported by UE.

The larger the data volume in the buffer area, the higher the scheduling priority of
UE.
QoSweight: refers to comprehensive weight after taking into account the QoS
information configured by RNC, including the Scheduling Priority Indicator (SPI),
and MAC-es Guaranteed Bit Rate (GBR). QoSweight is given in the following
equation:
QoSweight =(SPI_WEIGHT) (1 + GBRweight) (8)
SPI_WEIGHT is mapped through Table 1 according to SPI(0~15) configured
by RNC. The default mapping is the second column of Table 1. Operators can
configure the mapping.
l For UEs with Rn not less than GBR:
GBRweight = 0, (9)
l For UEs with Rn less than GBR:
GBRweight = MaxGBRWeightValue, (10)
MaxGBRWeightValue is an internal parameter, with value of 389376. If the actual
rate of a UE is lower than GBR, GBRweight will increase, resulting in a raise in UE
scheduling priority so that resources can be preferentially allocated for this UE.
l When Streaming services are carried on E-DCH, RNC informs Node B of the QoS
parameter MAC-es Guaranteed Bit Rate (GBR) through NBAP.
l When interactive-/background-class services are carried on E-DCH, RNC
provides configuration of nominal bit rate EdchNormBitRate. For details,
see ZTE UMTS QoS Feature User Guide. For interactive-/background-class
services, RNC maps EdchNormBitRate into the QoS parameter of UE: MAC-es
Guaranteed Bit Rate, and informs the HSUPA packet scheduler through NBAP.
The scheduler schedules such types of services according to the specified GBR.
The SPI configured for interactive-/background-class services is comparatively
low, so the ultimate scheduling priority of them will be lower than that of Streaming
services with higher SPI.
4. Allocate available system resources in descending sequence of UE priorities.
l Calculate available cell load based on the cell and UE load obtained in steps 1
and 2 as well as Node B processing capacity.
l Reserve load for R99 RT, R99 NRT, SRB and HSUPA non-scheduled transmission
services from the available cell load. (The scheduler thinks the load contributed
by these services is constant before or after scheduling).
l Determine the transmission rate requested by UE. The UE requested
transmission rate is subject to the service requirements (Service requirements
are jointly determined by the buffer area size in the SI as well as HappyBit
reported by UE. For UEs with HappyBit = Unhappy, their service requirements
equal to the size of buffer area; for UEs with HappyBit = Happy, their service
requirements equal to the size of data block corresponding with current grants
obtained), maximum rate in relation to UE category, maximum subscribed rate

1-5

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

(MBR) and maximum rate in relation to the UPH reported by UE (UPH in SI). The
smallest one of these values is taken as UE requested transmission rate.
l The HSUPA scheduler allocates resources for UEs in descending sequence of
their scheduling priorities.
l If current available system load and CE resources are larger than the summation
of load contributed by all UE requested transmission rates, the scheduler allocates
grants in relation to requested rates for all UEs.
l If current available system load or CE resources are less than the summation
of load contributed by all UE requested transmission rates, the scheduler first
calculates the load and CE resources contributed by the rate requested by the
UE with highest priority.
l The scheduler releases grants of UEs with low priorities one by one in ascending
sequence of scheduling priorities. Then it calculates the load contributed after
releasing grants until the load and CE resources released from UEs with low
priorities meet the requirements of the UE with highest priority. If the load released
from UEs with low priorities still fails to meet all requirements of the UE with highest
priority, the UE with highest priority will have to use the load and CE resources
released from those with low priorities.
l When allocating resources, the scheduler calculates CE resources currently used
by each UE as well as available CE resources of Node B. Then it allocates the
minimum available CE resources and load of Node B to the UE with highest
priority.
l The scheduler allocates CE resources and load to the rest UEs with high priorities
in the queue by following the above rule until all system resources are used up
(all UEs with low priorities have their resources released).
l Map load contributed by UEs into grants of UEs (the relation between
UE-contributed load and grant is as follows):
UE Serving Grants refers to the ratio of available E-DCH transmit power to DPCCH
transmit power:
SG = PE-DCH, TX / PDPCCH, TX (11)
PE-DCH, TX refers to E-DCH transmit power.
PDPCCH, TX refers to DPCCH transmit power.
DPCCH and E-DCH undergo the same fading process, and therefore, the relation
between receive powers of Node B DPCCH and E-DCH is given by the following
equation:
PE-DCH,RX / PDPCCH,RX = PE-DCH, TX / PDPCCH, TX (12)
And,
PDPCCH,RX(1 + SG)= PDPCCH,RX + PE-DCH,RX (13)
PE-DCH,RX refers to the receive power of E-DCH in Node B.
PDPCCH,RX refers to the receive power of DPCCH in Node B.
The relation between grant and UE-contributed load is given as follows:

1-6

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

 Chapter 1 Functional Description

((Eb/No)R)/W = (PDPCCH.RX + PE-DCH.RX)/No (14)

Substitute (13) into (14),
((Eb/No)R)/W = PDPCCH,RX(1 + SG)/No (15)
3GPP TS 25.214 defines the UE DPCCH SIR measured by Node B.
SIR = 256 PDPCCH,RX/No (16)
In the above equation, 256 refers to the processing gain of DPCCH. Substitute (16)
into (15):
((Eb/No)R)/W = SIR(1 + SG)/256 (17)
Substitute (17) into (4),
UEload = SIR(1 + SG)/ (256 + SIR(1 + SG)) (18)
The above equation indicates the correspondence between UE-contributed load and
UE grant. The UE service grant can be obtained through UE-contributed load, or vice
versa.
l For a UE with highest scheduling priority, the scheduler needs to send AG for
scheduling to facilitate the UE to quickly obtain required grant. The AG cannot
be used for the rest UEs after it is engaged because AGCH is shared among all
UEs. The RGCH, however, is dedicated control channel allocated for each UE.
Therefore, for the rest UEs, they can either get more resources or release their
resources by RG commands. The scheduler sends RG=UP to UEs allocated with
more resources, RG=DOWN to UEs with resources released and RG=HOLD to
UEs with grants retained during scheduling.
l When the ratio of the receive power of non-serving E-DCH RLS to the total receive
power of E-DCH is larger than NservToTotalPwr, Node B sends RG=DOWN to
non-serving RL UE.
The AGCH and RGCH may transmit data to UE in each TTI based on scheduling
requirements.

1-7

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

This page intentionally left blank.

1-8

SJ-20120802112720-228|2012-06-18 (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: 6 (E-DCH
category)
Release : R6

NodeB NO V4.11.10.14 None

RNC YES V3.11.10.11 ZTE equipment

MSCS YES None ZTE equipment

MGW YES None ZTE equipment

SGSN YES None ZTE equipment

GGSN NO None None

HLR NO None None

Topology
Topology is shown in Figure 2-1.

2-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

Figure 2-1 Topology

2-2

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

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

MSC/MGW - ZTE
N/A

HLR ZTE
1. UE1 subscribes background service, MBR= UL2Mbps/ DL8Mbps, with ARP1.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].
rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass
_background

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 8192000
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[1] = 2048000
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.priorityL
evel = 11
2. UE2 subscribes background service, MBR= UL2Mbps/ DL8Mbps, with ARP2.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].
rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass
_background
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 8192000

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[1] = 2048000
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.priorityL
evel = eRANAP_PriorityLevel_highest

RNC
l HSPA Support Method: Support HSUPA, HSDPA and DCH

3-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and Cell
Reselection > HSPA Support Method
l Maximum Target Received Total Wideband Power: 6

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 Check UE1 and UE2's SPI
UE1's APR is 2, so APR Segment is 1, Basic Priority is 7, Scheduling Priority is
7.

3-2

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

 Chapter 3 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNC
Radio Resource Management > QOS Relevance Configuration > QOS
Configuration
UE1's APR is 11, so APR Segment is 3, Basic Priority is 0, Scheduling Priority is
0.

Path: View > Configuration Management > RNC Managed Element > RNC
Radio Resource Management > QOS Relevance Configuration > QOS
Configuration

NodeB
N/A

3-3

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

This page intentionally left blank.

3-4

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

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

4.1 Test Purpose

The purpose of this test case is to verify if the function of QoS Mapping for HSUPA Service
is working normally.
Related document:
l ZTE UMTS QoS Feature Guide.docx
l ZTE UMTS HSUPA Packet Scheduling Feature Guide.docx

4.2 Steps for Test

1. UE1 activates a PS call in Cell1 and starts FTP uploading.

4-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

UE1 DU Meter Speed

2. UE2 activates another PS call in Cell1 and starts FTP uploading.

4-2

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

 Chapter 4 Testing

UE1 DU Meter Speed

UE2 DU Meter Speed

3. Deactivate both the PDPs.

4.3 Expected Results

The UL data rate of UE1 is decreased after UE2 activates the second PS call. According
to the service priority, the data rate of UE2 is higher than that of UE1.

4-3

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

Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

This page intentionally left blank.

4-4

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

 Chapter 5
Counter List
C310010153 Uplink traffic of HSUPA for Conversational class in best cell

C310010154 Uplink traffic of HSUPA for Streaming class in best cell

C310010155 Uplink traffic of HSUPA for Interactive class in best cell

C310010156 Uplink traffic of HSUPA for Background class in best cell

C310010177 Uplink traffic of HSUPA for Conversational class in non-best cell

C310010178 Uplink traffic of HSUPA for Streaming class in non-best cell

C310010179 Uplink traffic of HSUPA for Interactive class in non-best cell

C310010180 Uplink traffic of HSUPA for Background class in non-best cell

C310010292 Uplink Iub volume of HSUPA RAB for Conversational class

C310010293 Uplink Iub volume of HSUPA RAB for Streaming class

C310010294 Uplink Iub volume of HSUPA RAB for Interactive class

C310010295 Uplink Iub volume of HSUPA RAB for Background class

C310020426 Number of uplink HSUPA RLC PDU, Conversational class

C310020427 Number of uplink HSUPA RLC PDU, Streaming class

C310020428 Number of uplink HSUPA RLC PDU, Interactive class

C310020429 Number of uplink HSUPA RLC PDU, Background class

C310790005 Iu Uplink volume of HSUPA

C310800021 HSUPA Uplink volume of Iub for Conversational class

C310800022 HSUPA Uplink volume of Iub for Streaming class

C310800023 HSUPA Uplink volume of Iub for Interactive class

C310800024 HSUPA Uplink volume of Iub for Background class

C310800029 Uplink header volume of Iub HSUPA traffic

C310010162 Uplink volume of VoIP in E-DCH in best cell

C310010181 Uplink volume of VoIP in E-DCH in non-best cell

C310010303 Uplink Iub volume of VoIP in E-DCH

C310020407 Number of UL SDU sent by RLC, Traffic on E-DCH for PS domain

C310020415 Number of UL SDU received by RLC, Traffic on E-DCH for PS domain

5-1

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