You are on page 1of 21

Feature Deployment and Testing Guide

RAB Queuing
Feature ID: ZWF21-05-023

Version: V4.11.20

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-11-05 First edition

Serial Number: SJ-20120815154121-227

Publishing Date: 2012-11-05 (R1.0)

SJ-20120815154121-227|2012-11-05 (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-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


II

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 1
Functional Description
The feature of RAB queuing is introduced to have more attempts to access the network
for new service requirements when cell is in congestion, thus increasing the admission
success ratio and implementing the QoS differentiation.
The service queuing capability is determined by IE Queuing Allowed which is in RAB
parameters of RABASSIGNMENT REQUEST or RELOCATION REQUREST. The queuing
is allowed when the Queuing Allowed is TRUE. Otherwise, the queuing is not allowed.
For the service requirements in DRNC, if the IE Allowed Queuing Time in RADIO SETUP
REQUEST message over IUR is present, the queuing is allowed. Otherwise, the queuing
is not allowed.
When the cell is in congestion, the congestion scheduling is used to readmission
the queuing new service requirements and upgrading requirements according to the
scheduling priority(SP). The services with higher SPs are scheduled first to use the
resources spared from load decrease.

To improve call success ratio during readmission of the queuing services, the new service
requirement are scheduled for readmission first, and then the upgrading requirements
are admitted. As long as there is a new service requirement in the queue, no upgrading
requirement will be scheduled for admission. The new service requirements include
assigned services and incoming relocated services.
The new service requirements are scheduled in the sequence of scheduling priorities
(SP of RNC). A new service with a higher scheduling priority(SP) will be scheduled prior
to another with a lower scheduling priority(SP). For the mapping policies of scheduling
priorities(SP), refer to ZTE UMTS QoS Feature Guide. When sorting the upgrading
services, the current rates allocated to these services are taken into first consideration for
the sake of fairness and priorities. The services with a current rate smaller than the NBR
are put into the foremost set (set1), the services with a current rate equal to the NBR are
put into set2, and the services with a current rate larger than the NBR are put into the
last set (set3). Then the services in each set are sorted according to their scheduling
priorities(SP). The service ranking foremost will be scheduled first.
NBR is configured separately for uplink and downlink: UlNormBitRate and DlNormBitRate.
The time for scheduling queuing services: if the service with the highest scheduling
priority(SP) in the queue is suffering soft resource congestion, scheduling for admission
cannot be started until the common measurement is reported, because the soft resources
are judged on the basis of the common measurement report. If the service with the
highest scheduling priority(SP) in the queue is suffering just hard resource congestion,
the queue services will be rescheduled for admission whenever other online services
undergo release and downgrade. Besides, rescheduling is also triggered when the

1-1

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

common measurement is reported. Therefore, for hard resource limitation, there are
more chances of rescheduling for admission.

Figure 1-1 Flow Chart of Resource Preemption

1-2

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 2
Preparations
License
N/A

Hardware Requirement
NE Requirement

RNC None

NodeB None

Software Requirement
NE Involved Version Requirement

UE YES UMTS FDD Number: 2


Category: Any
Release : R99 or above

NodeB YES V4.11.10.14 ZTE equipment

RNC YES V4.11.20.06 ZTE equipment

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-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

Figure 2-1 Topology

2-2

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 3
Data Configuration
SGSN/GGSN - ZTE
SGSN should be set subscriber to allow queuing and not pre_emptable( or not
trigger_pre_emption), according to UE priority setting in HLR. IF the parameter is
configured correctly, check the element on RAB_AssignmentRequestMsg message
from SGSN. It should be as following:
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.pre_emptionVuln
erability = eRANAP_Pre_emptionVulnerability_not_pre_emptable
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.queuingAllowed
= eRANAP_QueuingAllowed_queueing_allowed

MSC/MGW - ZTE
None

HLR - ZTE
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.trafficClass = TRANAP_background
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.maxBitrate.elem[0] = 2048000
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.allocationOrRetentionPriority.queuingAllowed = TRANAP_queuein
g_allowed
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModify
ItemFirst.rAB_Parameters.allocationOrRetentionPriority.pre_emptionVulnerability =
eRANAP_Pre_emptionVulnerability_not_pre_emptable

RNC
Parameters setting in RNC

-HSPA Support Method: Support HSUPA,HSDPA and DCH

WCDMA Cell1 supports HSUPA, HSDPA and DCH.

3-1

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

Path: View > Configuration Management > Modify Area > UMTS Logical Function
Configuration > UTRAN Cell
-DRBC Method Switch Switch ON on UL& Switch ON on DL

3-2

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 3 Data Configuration

Path: View > Configuration Management > Modify Area > UMTS Logical Function
Configuration > PLMN Relating Configuration > Logic RNC Configuration
-Cell Downlink Admission Control SwitchOn

3-3

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

Path: View > Configuration Management > Modify Area > UMTS Logical Function
Configuration > UTRAN Cell > Extended Info of UTRAN Cell

-DchDlAcThresh(1.. 100)% step 1%


Configure the rational DCH DL power admission threshold, give an available value
to DchDlAcThresh. The value can be configured as an appropriate value. We can
get the TrafficClass and ARP fromRAB_AssignmentRequestMsg, then map the BP
of the service, configure the appropriate value based on the observation of common
measurement Report.
In this case:
UE1 makes a PS service:
1. Read ARP from RAB_AssignmentRequestMsg as below
TrafficClass=background
ARP=2

2. Map ARP to BP:

(ARP=2) and (Traffic Class=Background)>BP=7

3-4

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 3 Data Configuration

Path: View > Configuration Management > Modify Area > UMTS Logical
Function Configuration > PLMN Relating Configuration > Basic Priority Mapping
Relationship
3. Find Basic Priority AC Index of the Cell:
UBPriAcProfile=0

4. Modify DCH Downlink AC Threshold of the record which BP=7 and UBPriAcProfile=0
to an appropriate value. Make sure that UE1 makes a PS service and the service
setup successfully. UE2 makes a PS service but is queuing by congestion control.

3-5

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

Path: Veiw > Configuraiton Management > Modify Area > UMTS Logical Function
Configuration > Service Configuration > QOS Funciton > Access Control Related
to Basic Priority

3-6

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 3 Data Configuration

NodeB
None

3-7

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

This page intentionally left blank.

3-8

SJ-20120815154121-227|2012-11-05 (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 RAB Queuing is working normal.
Related document:

ZTE UMTS Congestion Control Feature Guide.doc

4.2 Steps for Test


1. UE1 activates a PS call in Cell1 and starts FTP downloading. The DL data rate of UE1
reaches 384Kbps after a while.

2. Observe the current DL power and configures the rational DCH DL power admission
threshold based on the priority of the service to restrict only one 384Kbps PS call is
allowed to be established on Cell1.

4-1

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

Make sure the BP of the service is correct based on the priority of the service.
3. UE2 activates a PS call but cant be admitted for the first attempt due to the DL power
shortage, then enters the queuing list and triggers DL congestion. The DL data rate
of UE1 rate is downgraded. The UE2 is admitted for the next attempt successfully.
a. UE2 enters the queuing list.

b. The DL data rate of UE1 rate is downgraded to 128kbps:

c. The DL data rate of UE1 rate is downgraded to 64kbps.

d. UE2 is admitted for the next attempt successfully.

4-2

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 4 Testing

4. Deactivate both the PDPs.

4.3 Expected Results


In step3, UE2 is admitted successfully. The DL data rate of UE1 is downgraded.

4-3

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-05-023

This page intentionally left blank.

4-4

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential


Chapter 5
Counter List
Counter No. Description

C310200611 Total queue time of SPEECH RAB assignment


setup

C310080001 Number of attempted RRC connection


establishment, Originating Conversational Call

C310080008 Number of attempted RRC connection


establishment, Terminating Conversational Call

C310080170 Number of successful RRC connection access,


MO Conversational Call

C310200616 Number of queue SPEECH RAB assignment


setup

5-1

SJ-20120815154121-227|2012-11-05 (R1.0) ZTE Proprietary and Confidential

You might also like