Feature Deployment and Testing Guide

RSEPS based HSUPA RRM

Feature ID: ZWF25-04-008

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-226

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

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

 Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Deployment in commercial network and user benefit........... 2-1
Chapter 3 Preparations .............................................................................. 3-1
Chapter 4 Data configuration .................................................................... 4-1
Chapter 5 Testing ....................................................................................... 5-1
5.1 Test Purpose...................................................................................................... 5-1
5.2 Steps for Test..................................................................................................... 5-1
5.3 Expected Results ............................................................................................... 5-1

Chapter 6 Counter List............................................................................... 6-1

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

 II

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

 Chapter 1
Functional Description
This feature provides measurement on Received Scheduled E-DCH Power Share
(RSEPS), which is used for admission control, load balance with certain accuracy so that
effective RRM is achieved.
According to 3GPP 25215-710, the 'Received scheduled E-DCH power share' is defined
as a report of 2 values for a considered cell:
1. RSEPS: defined as a quotient:
sum of all scheduled E-DPCCH and E-DPDCH power contributions determined
in the RSEPS measurement period T=t2-t1>0 for all UEs for which this cell is the
serving E-DCH cell divided by the corresponding received total wideband power
value determined for this cell during T.
2. RTWP*: This is the received total wideband power (RTWP) measured for this cell but
determined for the same time period T starting at t1 and ending at t2 during which
RSEPS is determined.
The reference point for the RSEPS and RTWP* measurements shall be the Rx antenna
connector.
When cell portions are defined in the cell, RSEPS (and RTWP*) shall be measured for
each cell portion.
The sum in the numerator of RSEPS is determined under the following conditions:
l The contributions are summed up TTI wise and only TTIs which are ending
between the time instants t1 and t2 are considered.
l In case a UE has not only a radio link to the considered cell but also other radio
links to the same Node B ('softer handover'): It is allowed to take into account the
power value combined for these radio links of the same Node B and divided by
the number of combined radio links.

Note:

For improved measurement performance it is possible to consider only the power

contribution determined for the considered cell.

The measurement model for physical layer measurements is represented in the figure
below. (Refer to 3GPP 25302)

1-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

Figure 1-1 Measurement model

HSUPA Admission Control

To perform E-DCH uplink Interference-based admission control in a HSUPA-capable cell,
Node B needs to periodically report HSUPA interference-related common measurement
information: RSEPS(and RTWP*).
For non GBR E-DCH traffic, Uplink Interference increment need not be calculated
(increment is 0), but Admission judgment is needed. For DCH and GBR E-DCH traffic,
both Uplink Interference increment calculation and Admission judgment are needed.
1. Effective load calculated
For Uplink Interference increment calculation and Uplink Interference-based
Admission judgment, Uplink Effective load should be got which cannot be controlled
by NodeB.
Uplink Effective load = load from UL DCH + load from non scheduled E-DCH + load
from non serving E-DCH + load from neighbor cell interference +load from GBR data
rate of scheduled E-DCH.
NodeB can send E-DCH Resources Information>ResourceOperationalState and
HSDPA Capability IE in AUDIT RESPONSE message. If the value of E-DCH
Resources Information>Resource Operational State IE is "Disabled" or "E-DCH
Capability" IE is "E-DCH non Capable", E-DCH will refuse to access any new E-DCH
traffic, the cause is "NodeB Capabiliy Limited".
If a=10^((RSEPS )/10 ), Itotal=10^((RTWP* )/10 ) [mW],
Then Uplink Effective load = Itotal (1-a) + load from GBR data rate of scheduled E-DCH
In which:
Itotal (1-a) means: base noise + load from UL DCH + load from non scheduled E-DCH
+ load from non serving E-DCH + load from neighbor cell interference, which can be
got from common measurement report of RTWP and RSEPS;
Load from GBR data rate of scheduled E-DCH can be calculated by the formula:

(which comes from: )

l Itotal comes from NodeB common measurement report (RTWP*)

1-2

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

 Chapter 1 Functional Description

l = 1 - N0 / Itotal
l N0 refers to uplink background and receiver noise power, which originates from
OriBckNoise (BckNoiseAdjSwh is set to OFF) or is obtained through automatic
uplink noise floor measurement (BckNoiseAdjSwh is set to ON), refers to 3.1.1.3
Automatic measurement of uplink noise floor

l Load estimate factor , W=3.84e6 [bit/s]

l refers to active factor (Alfa)
l UlInterFactor refers to the factor for uplink interference of adjacent cell on current
cell.(the value is 0.5)
l =10^((Eb/N0 )/10 ), Eb/N0 refers to uplink service quality factor
l =10^((Eb/N0 )/10 ),Eb/N0 refers to E-DCH service quality factor, with the value
of 1dB
l R refers to the total GBR data rate of scheduled E-DCH online
2. Uplink Interference increment (I) calculation for new E-DCH
For non GBR E-DCH traffic, Uplink Interference increment need not be calculated
(increment is 0), but Admission judgment is needed. For DCH and GBR E-DCH traffic,
both Uplink Interference increment calculation and Admission judgment are needed.
In the test, usually the interactive or background service is used, so the introduction
of uplink Interference increment for new E-DCH is omitted here.
3. Uplink Interference Access judgment
l Scheduled E-DCH Access Judgment
If I + Uplink Effective load > EdchAcThresh, then the new traffic is refused
to access the cell for the cause of Uplink Interference limited; else, Uplink
Interference not limited and access allowed.

l Non Scheduled E-DCH Access Judgment

If I + " load from UL DCH + load from non scheduled E-DCH" > DchUlAcThresh or
"I + Uplink Effective load" > EdchAcThresh, then the new DCH or non scheduled
E-DCH traffic is refused to access the cell for the cause of Uplink Interference
limited; else, Uplink Interference not limited and access allowed.
l Concurrent services Access Judgment:

For new traffic added to traffic online, only new traffic is need to judge whether
Uplink Interference will be limited and the procedure is the same to a new traffic.

For Concurrent traffic added to a cell for the same time (i.e Concurrent services
handover), Uplink Interference access judgment will be judged one traffic by one
traffic. Concurrent traffic will be refused to access the cell for the cause of Uplink
Interference limited if one traffic will be limited.

1-3

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

Figure 1-2 Configuration steps of E-DCH admission control threshold

HSUPA Congestion Control

For the HSUPA cell, if the services are rejected for the reason of uplink interference limited,
there are two possible factors: 1. the sum of all scheduled E-DCH power generated by
the GBR part is too high; 2. the sum of all DCH power and no scheduled E-DCH power is
too high. The RTWP of the cell and the RTWP of the scheduled E-DCH can be measured
through the Node B common measurement of RSEPS.

For the cells that support HSUPA, the power limit based E-DCH congestion control
requires that the Node B periodically reports the HSUPA power related Node B common
measurement information of RSEPS.

HSUPA Overload Control

As the measurement information of the RSEPS was introduced, the uplink load state of
HSUPA cell is judged based on the uplink effective load.

1-4

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

 Chapter 2
Deployment in commercial
network and user benefit
Before using NodeB common measurement report Received Scheduled E-DCH Power
Share (RSEPS), it will be difficult to distinguish the load between DCH and E-DCH.
This feature provides measurement on Received Scheduled E-DCH Power Share
(RSEPS), which is used for admission control, load balance with certain accuracy so that
effective RRM is achieved.

2-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

This page intentionally left blank.

2-2

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

 Chapter 3
Preparations
License
N/A

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

Table 3-1 Hardware Requirement

NE Requirement

RNC RNC

NodeB SDR

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

Table 3-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 1

Category: HSUPA
Category 5 or 6
Release : R6 or above

NodeB YES V4.11.10.14 ZTE equipment

RNC YES V3.11.10.11 ZTE equipment

MSCS YES None ZTE equipment

MGW YES None ZTE equipment

SGSN YES None ZTE equipment

GGSN YES None ZTE equipment

HLR YES None ZTE equipment

Topology
Topology is shown in Figure 3-1.

3-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

Figure 3-1 Topology

3-2

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

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

MSC/MGW - ZTE
N/A

HLR ZTE
The value of the following fields should be checked and recorded. These values are
subscribed on HLR.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_interactiv
e
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficHandlingPriority = 2
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB
_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.priorityLevel =
eRANAP_PriorityLevel_highest (=1)

RNC
l Enable the function of cell uplink admission control.
Cell Uplink Admission Control Switch: On

4-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > UTRAN Cell > Cell
Uplink Admission Control Switch
l Check the period NodeB Common Measurement Configuration index for RSEPS.
Period NodeB Common Measurement Configuration index for Received Scheduled
E-DCH Power Share: 6

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > NodeB Common
Measurement > Period NodeB Common Measurement Configuration index for
Received Scheduled E-DCH Power Share
l Check the Measurement Filter Coefficient and Report Period.

NodeB Common Measurement Configuration index: 6

A new index can be created and then referred by the cell.
Measurement Filter Coefficient: 3
This parameter indicates the L3 filter coefficient. The less of the value, the less
fluctuate of the common measurement report value; the larger of the value, the
more real-time of the common measurement report value. It is not suggest to be
adjusted.
Choice Report Periodicity Scale: ms

Report Period: 2000

4-2

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

 Chapter 4 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > NodeB Common Measurement Configuration
l Check the ARP and THP from the RAB_AssignmentRequestMsg in PS service.

In this example shown, trafficClass = Interactive, ARP = 1, THP = 2 (only for interactive
service).
From the mapping, ARPSeg = 1, THPSeg =1.

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

Basic Priority: 9

4-3

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > QOS Relevance Configuration > QOS Configuration >
QOS Configuration MCC: MNC > Basic Priority Management
l Check the admission control index of the cell.
Basic Priority AC Index: 1

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > UTRAN Cell Global
Information > Basic Priority AC Index
l Configure the E-DCH AC threshold (dB) according to the Basic Priority AC Index and
Basic Priority.

E-DCH AC threshold: 0.1

4-4

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

 Chapter 4 Data configuration

NodeB
N/A

4-5

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

This page intentionally left blank.

4-6

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

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

5.1 Test Purpose

The purpose of this test case is to verify if the function of RSEPS based HSUPA RRM is
working normally.
Related document:
l ZTE UMTS Admission Control Feature Guide
l ZTE UMTS Congestion Control Feature Guide
l ZTE UMTS Overload Control Feature

5.2 Steps for Test

1. Reset the cell to observe common measurement initiation and report.
2. Make a PS call with HSUPA UE in HSUPA cell.

5.3 Expected Results

1. Check the parameters in the common measurement initiation and measurement
report.

5-1

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

In the mapping of measured quantity for RTWP is defined. (Refer to 3GPP 25133 for
details)
RTWP Measured quantity value (dBm) = RTWP Reported value/10-112.1

Reported value Measured quantity value Unit

RTWP_LEV _000 RTWP < 112.0 dBm

RTWP_LEV _001 -112.0 RTWP < 111.9 dBm

RTWP_LEV _002 -111.9 RTWP < 111.8 dBm

... ... ...

RTWP_LEV _619 -50.2 RTWP < -50.1 dBm

RTWP_LEV _620 -50.1 RTWP < -50.0 dBm

RTWP_LEV _621 -50.0 RTWP dBm

In the mapping of measured quantity for RSEPS is defined. (Refer to 3GPP 25133 for
details)
RSEPS Measured quantity value = RSEPS Reported value/10-15.1

Reported value Measured quantity value Unit

RSEPS _LEV _000 RSEPS<15.0 dB

RSEPS _LEV _001 -15.0RSEPS<14.9 dB

RSEPS _LEV _002 -14.9RSEPS<14.8 dB

... ... ...

RSEPS _LEV _149 -0.2RSEPS<-0.1 dB

RSEPS _LEV _150 -0.1RSEPS<0 dB

RSEPS _LEV _151 0RSEPS dB

2. The service is refuse for Uplink Effective load > EdchAcThresh.

5-2

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

 Chapter 5 Testing

In this example, queuing is allowed; otherwise the RAB_AssignmentResponseMsg

will fail directly.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].r
AB_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.queuing
Allowed = eRANAP_QueuingAllowed_queueing_allowed

5-3

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

Feature Deployment and Testing Guide Feature ID: ZWF25-04-008

This page intentionally left blank.

5-4

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

 Chapter 6
Counter List
N/A

6-1

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