ZWF23!05!001 QoS Mapping for HSDPA Service

Feature Deployment and Testing GuideQoS Mapping for HSDPA Service

Feature ID:ZWF23-05-001

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

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

SJ-20120802112720-192|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-3

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

I


II


Chapter 1Functional DescriptionRNC maps RAB QoS parameters from CN to the basic priority used in the UTRAN. AndRNC maps basic priority to Scheduling Priority Indicator (SPI)for HSDPA service

For subscribers connected to the cell, RNC allocates the radio resources based on thepriorities. The configuration of ARP depends on the following factors: ARP assigned bycore network in the service establishment phase, traffic class, THP of I services, radiochannel type, and real-time rate of the subscriber.

The priority used by the RNC is acquired by the mapping of the QoS parameters in theRAB assignment by the CN. Input parameters are:

l Traffic Classl THPl ARP

The RNC maps these parameters to logical channel priority, BP, SP, and AP. For thegeneral mapping scheme, see the following figure.(Note: C indicates conversation service,S indicates streaming service, I indicates interactive service, and B indicates backgroundservice.)

1-1


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

Note:

Frame Handling Priority (FHP), Scheduling Priority Indicator, and Common TransportChannel Priority Indicator on the lur/lub interface adopt the mapping results of BP directly,that is, the FHP, SPI and BP are the same for aRB. Where, the FHP is the priority ofNode B. It indicates the priority of data scheduling and resource allocation in the resourcecongestion. The SPI is used for the queue data scheduling of HSPA. It is an importantbasis for packet scheduling and resource allocation of Node B.

The following table is the summary of scenarios applied for basic priority(BP), schedulingpriority(SP) and application priority(AP).

Priority Function Scenarios

Basic Priority(BP) Admission Control

HSDPA Packet Scheduling

HSUPA Packet Scheduling

(1) When RAB is admitted, RNC

obtains admission threshold

based on BP.

(2) For HSDPA, when resources

for HSDPA are shared by

multiple users, RAN (Node B)

will allocate the code and power

resources to different HSDPA

mobiles according to SPI which

is equal to BP.

(3) For HSUPA, when resources

for HSUPA are shared by

multiple users, RAN (Node B)

will allocate the grant to different

HSUPA mobiles according to

SPI which is equal to BP.

SP of RNC(SP) Congestion Control (1) When forced release is

performed because of resource

congestion, RNC will select

users to perform forced release

based on SP.

(2) When queuing and

service admission again are

performed because of resource


users to perform admission

based on SP.

1-2


Chapter 1 Functional Description

Priority Function Scenarios

Application Priority(AP) Congestion Control

OverLoad Control

When DCH data rate

downgrading is performed

because of resource


users to perform downgrading

based on AP.

When overload happens, RNC

will select users to decrease

load based on AP.

1-3



This page intentionally left blank.

1-4


Chapter 2PreparationsLicense

Feature License

ZWF23-05-003 HSDPA Nominal Bit Rate for IB

Service

　WCDMA HSDPA Introduction Package(*)

Hardware RequirementHardware requirement is shown in Table 2-1.

Table 2-1 Hardware Requirement

NE Requirement

RNC None

NodeB None

Software RequirementSoftware requirement is shown in Table 2-2.

Table 2-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 1

Category: Any

Release : R6

2-1



NE Involved Version Requirement

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

SGSN should be configured to send the “allocationOrRetentionPriority”indication, and then UE can get its priority from HLR. , Please check the IE in“RAB_AssignmentRequestMsg” message from SGSN to RNC to make sure theparameter is configured correctly. It should be as below:

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.m.allocationOrRetentionPriorityPresent = 1

MSC/MGW - ZTE

N/A

HLR – ZTE

l UE1 :UE1 supports Background service. Set the allocation or retention priorityparameter in HLR by select an index among the SGSN configuration.

RANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_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.allocationOrRetentionPriority.priorityLevel = 2

l UE2 :UE2 supports Background service. Set the allocation or retention priorityparameter in HLR by select an index among the SGSN configuration.

RANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_background



3-1



TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.priorityLevel = 11

The UE1’s priority is higher than UE2’s

RNC

l ARP Segment Number

UE1’s priority=2, belongs to ARP Segment 1

UE2’s priority=11, belongs to ARP Segment 3

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > QOS Relevance Configuration > QOS Configuration >QOS Configuration > ARP Segment Number

l THP Segment Number

If the service type is Interactive, THP shoud be used to map the BP.

3-2


Chapter 3 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > QOS Relevance Configuration > QOS Configuration >QOS Configuration > THP Segment Number

l BP Segment

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > QOS Relevance Configuration > QOS Configuration >QOS Configuration > Basic Priority Segment Number

l Basic Priority

UE1:ARP Segment=1,corresponding Basic Priority=7

UE2:ARP Segment=3,corresponding Basic Priority=0

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > QOS Relevance Configuration > QOS Configuration >QOS Configuration > Basic Priority Management > Basic Priority

l SPI

3-3



For HSDPA ,RNC maps the basic priority to Scheduling Priority Indicator (SPI),so theSPI of UEs are:

UE1:BP=7 > SPI=7

UE1:BP=0 > SPI=0

NodeB

N/A

3-4


Chapter 4TestingTable of Contents

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

4.1 Test PurposeThe purpose of this test case is to verify whether the function of QoS Mapping for HSDPAService is working normally.

Related documents:

l ZTE UMTS QoS Feature Guide

4.2 Steps for Test1. UE1 activates a HSDPA PS service and starts FTP downloading. Maintain it for 90s.

2. Observe the downloading rate of UE1 from DU Meter.

4-1



3. UE2 activates another PS service and starts FTP downloading.

4. Observe the downloading rate of UE2 from DU Meter.

4-2


Chapter 4 Testing

5. After UE2 starts FTP downloading,compare the downloading rate of UE1 with UE2.The average downloading rate of UE1 is higher than that of UE2.

4.3 Expected ResultsDue to QOS Mapping for HSDPA Service, UE1’s SPI is higher than that of UE2. The FTPdownloading rate of UE1 will be higher than that of UE2.

4-3



This page intentionally left blank.

4-4


Chapter 5Counter List

C310080055 Number of attempted RRC connection ,UE

Support HSDPA

C310080197 Number of successful RRC connection

access,UE Support HSDPA

C310080210 Number of successful RRC connection access by

UE HSDPA categories 7 - 8

C310251478 Number of RAB normal release for HSDPA:UE

HSDPA categories 7 - 8,backgroud

C310040070 Holding time of HS-DSCH,Background class,on

best cell

C310030491 Number of Background class in HS-DSCH in the

best cell

C310010160 Downlink traffic of HSDPA for Background class

in best cell

C310010299 Downlink Iub volume of HSDPA RAB for

Background class

C310800028 HSDPA Downlink volume of Iub for Background

class

C310454513 Current utilizing rate of Hsdpa TCP

C310504782 Number of attempted access services,HSDPA

Background class services

5-1


ZWF23!05!001 QoS Mapping for HSDPA Service

Documents

Transcript of ZWF23!05!001 QoS Mapping for HSDPA Service