DD-HSPA QoS Scheduling Priority Based on ARP PA2

Ericsson ConfidentialDEMO DESCRIPTION 1 (11)

Prepared (also subject responsible if other) No.

ELISOBR 39/155 52-HSD 101 02/10 UenApproved Checked Date Rev Reference

2012-09-03 PA2 EAccess

DD-HSPA QoS Scheduling Priority Based on ARP

Abstract

This document contains all information for internal and external customer. Internal information is stated with HIDDEN TEXT

To printout for internal select “Hidden Text” in print options.

For customers convert to PDF without “Hidden Text” in print options.

This document describes the recommended demo test cases for feature HSPA QoS Scheduling Priority Based on ARP (FAJ 121 1382)

Contents

1 General....................................................................................................21.1 Application..................................................................................21.2 Revision History..........................................................................21.3 Introduction.................................................................................21.4 References.................................................................................31.5 Terminology................................................................................31.6 Additional Information.................................................................31.7 Demo Execution Time................Error! Bookmark not defined.

2 Prerequisites...........................................................................................32.1 Configuration and Settings.........................................................32.2 Other Features Required............................................................32.3 Network Configuration................................................................42.4 Parameter Settings.....................................................................42.5 Tools...........................................................................................7

3 Demo Cases............................................................................................73.1 [W-11] Mapping of ARP to Scheduling Priority Indicator............7

4 Helpful Hints.........................................................................................104.1 Feature Related Alarms............................................................104.2 Feature Related Counters........................................................104.3 Other.........................................................................................10





1 General

1.1 Application

This document describes how to demonstrate features:

Feature no Feature Title (node) Demo no.

GS

M

WC

DM

A

FAJ 121 1382 HSPA QoS scheduling priority based on ARP X X

1.2 Revision History

Revision Comment Author DatePA1 First draft. ELISOBR 2012-09-03PA2 Updated after review ELISOBR 2012-09-10

1.3 Introduction

The feature “HSPA QoS scheduling priority based on ARP” introduces functionality to let the Allocation/Retention Priority (ARP) RAB parameter received from the core network (RANAP) influence the scheduling priority for HSPA connections. This feature is an extension/addition to the existing QoS mapping functions.

The feature can be activated/deactivated for UL and DL separately and supports both PS and CS networks. A pre-condition for this feature is that the existing feature "Flexible QoS and Allocation/Retention handling", FAJ 121 1093, is active.

The feature "Flexible QoS and Allocation/Retention handling”, contains of three different features FlexArpMap, QosMapUL and QosMapDL.

All three features have to be activated.

The new feature also gives the operator the means to adapt the ARP impact on the Scheduling Priorities by introduction of new operator parameters.





This feature will give the operator the possibility to let the ARP received from the CS and PS core networks influence the prioritization of the HSPA radio connection in WRAN, and thereby also giving the operator a mechanism for increased priority differentiation.

The HSPA QoS Scheduling Priority Based on ARP feature enables the selection of a SPI for HSPA radio connections in RAN based on the external ARP parameters received from the CN.

Please have a look at chapter 4.3.1 about “Iu Attribute Mapping to Scheduling Priority Indicators”, see reference [1].

1.4 References

[1] W12B CPI

1.5 Terminology

AMOS Advanced Managed Object ShellQoS Quality of ServiceCN Core networkARP Allocation/Retention PriorityRANAP Radio Access Network Application Part

1.6 Additional Information

-

2 Prerequisites

2.1 Configuration and Settings

2.1.1 Environment

Demo cases described in this document are intended for non-commercial systems.

2.2 Other Features Required

Feature Number Feature Name Feature Designation





FAJ 121 1093 Flexible QoS and Allocation/Retention Handling

FlexArpMap, QosMapUL, QosMapDL

FAJ 121 1094 Traffic Handling Priority ThpSupportHspaFAJ 121 1382 HSPA QoS scheduling priority based on ARP ArpToSpiMappingUL,

ArpToSpiMappingDL

2.3 Network Configuration

Figure 1: Network Configuration

2.4 Parameter Settings

The “Flexible QoS and Allocation/Retention handling“ feature contains three different license keys, FlexArpMap, QoSMapUL and QoSMapDL, All three license keys must be enabled.

set RncFeature=FlexArpMap featureState 1 (1=ACTIVATED) set RncFeature=QoSMapUL featureState 1 (1=ACTIVATED) set RncFeature=QoSMapDL featureState 1 (1=ACTIVATED)

Check that feature HSPA QoS Scheduling priority based on ARP is activated.

get RncFeature=ArpToSpiMappingUL featureState (1=ACTIVATED) get RncFeature=ArpToSpiMappingDL featureState (1=ACTIVATED)

If Core Network support signaling of THP (Traffic Handling Priority), then check that following feature is activated and configured:





- FAJ 121 1094, Traffic Handling Priority

Otherwise you will always get THP=2 for all PS Interactive traffic with TrafficClassPsInt=3.

MO Class Name Parameter Name Parameter Description Demo Value

ArpSpiMap externalArpMapping

List of SPI values to which External ARP priority values are mapped. All 14 elements must be set.The index of the sequence element (its position) corresponds to the external ARP value, and the value at that index points to the SpiQosClass instance to be used. A value of -1 indicates that the default value in the MO referring to this instance is used instead.

14,10,6,4,2,-1,-1,-1,-1,-1,-1,-1,-1,-1

RnlQoSClassProfile tcPsBgArpSpiMapRef

Reference to an instance containing external ARP to SPI mappings for PS Background

Takes effect: New connectionsDependencies: This reference must point at an instance of ArpSpiMap that is contained under the same profile as this instance.

ArpMap externalArpMapping

1 2 3 4 5 6 7 8 9 10 11 12 13 14

2.4.1 Demo Preparation

Core Network must be configured to send ARP to UTRAN

Create and configure one or more ArpSpiMap tables:

These instances are created as children of MO:RnlQosClassProfile, one per Uplink and another for Downlink.





cr RncFunction=1,RabHandling=1,RnlQosClassProfile=Downlink,ArpSpiMap=1

cr RncFunction=1,RabHandling=1,RnlQosClassProfile=Uplink,ArpSpiMap=1

This instances are created with a non-applicable pre-configured “externalArpMapping” attribute set to (-1), and should be manually set to the desired SpiQoSClass.

If the feature is enabled but no ArpSpiMap are created or the arpSpiRefMap and/or externalArpMapping are not specified then the SPI shall be chosen as if the feature is inactive, i.e. defaultQosRef parameter in the TrafficClass instance or the qosRef parameter in the TrafficClassPsInt instance shall be used as references to the SpiQosClass.

lset RncFunction=1,RabHandling=1,RnlQosClassProfile=Downlink,ArpSpiMap=1 externalArpMapping 14,10,6,4,2,-1,-1,-1,-1,-1,-1,-1,-1,-1

lset RncFunction=1,RabHandling=1,RnlQosClassProfile=Uplink,ArpSpiMap=1 externalArpMapping 14,10,6,4,2,-1,-1,-1,-1,-1,-1,-1,-1,-1

Configure the arpSpiMapRef for PS Background user service by setting the attribute RnlQoSClassProfile:tcPsBgArpSpiMapRef, for both downlink and uplink instances.

lset RncFunction=1,RabHandling=1,RnlQosClassProfile=Downlink tcPsBgArpSpiMapRef RabHandling=1,RnlQosClassProfile=Downlink,ArpSpiMap=1

lset RncFunction=1,RabHandling=1,RnlQosClassProfile=Uplink tcPsBgArpSpiMapRef RabHandling=1,RnlQosClassProfile=Uplink,ArpSpiMap=1

Configure the arpSpiMapRef for PS Interactive user services by assigning the reference to an ArpSpiMap table to the parameter TrafficClassPSInt:ArpSpiMapRef, for both downlink and uplink instances.

lset RncFunction=1,RabHandling=1,RnlQosClassProfile=Downlink,TrafficClassPSInt=1 arpSpiMapRef RabHandling=1,RnlQosClassProfile=Downlink,ArpSpiMap=1

lset RncFunction=1,RabHandling=1,RnlQosClassProfile=Uplink,TrafficClassPSInt=1 arpSpiMapRef RabHandling=1,RnlQosClassProfile=Uplink,ArpSpiMap=1











If Core Network do not send THP you will always get THP=2 for all PS Interactive traffic with TrafficClassPsInt=3.

2.5 Tools

2.5.1 Hardware Tools

-

2.5.2 Software Tools

AMOS

WinFiol (for HLR)

3 Demo Cases

3.1 [W-11] Mapping of ARP to Scheduling Priority Indicator

3.1.1 Objective

Demonstrate that the RANAP ARP parameter settings will impact the scheduling priority when it is configured differently for the same service.

3.1.2 Pass/Fail Criteria

The scheduling priority is impacted by RANAP ARP.

3.1.3 Parameter Setting

-

3.1.4 Preconditions

-





3.1.5 Demo Execution

Background PS call

Action 1 Deactivate features ArpToSpiMappingUL and ArpToSpiMappingDL in order to check how the mapping is done based on parameter SpiQoSClass in RnlQoSClassProfile for Background PS user service.

get ArpToSpiMappingUL featureState

get ArpToSpiMappingDL featureState

Action 2 Setup a Background PS call

Action 3 Check the internal ARP values, which those external ARP values. The external ARP mapping is configured in MO:ArpMap

Get . externalArpMapping

All ArpqosClassProfile:ArpMap tables are configured with

externalArpMapping i[14] = 1 2 3 4 5 6 7 8 9 10 11 12 13 14

The received CN ARP is mapped to its exact value.

Action 4 Check in RANAP RAB Assignment Request message, which ARP value is sent from CN.

Action 5 SPI values sent to the RBS are according to the configured tcPsBgQosRef parameter in RnlQoSClassProfile instance.

get RnlQoSClassProfile tcPsBgQosRef

Action 6 Activate features ArpToSpiMappingUL and ArpToSpiMappingDL.

set ArpToSpiMappingDL featureState 1

set ArpToSpiMappingUL featureState 1

Action 7 Setup a Background PS call

Action 8 Check the internal ARP values, which those external ARP values. The external ARP mapping is configured in MO:ArpMap (RncFunction, RabHandling, ArpqosClassProfile).







so the received CN ARP is mapped to its exact value.


Action 10 SPI values sent to the RBS are according to the configured externalArpMapping parameter in the ArpMap instance.

Interactive PS call

Action 1 Deactivate features ArpToSpiMappingUL and ArpToSpiMappingDL in order to check how the mapping is done based on parameter SpiQoSClass in TrafficClassPsInt for Interactive PS user service.

Action 2 Setup an Interactive PS call, by Dial-up a PS connection.






Action 5 SPI values sent to the RBS are according to the configured qosRef parameter into TrafficClassPsInt instance.

Action 6 Activate features ArpToSpiMappingUL and ArpToSpiMappingDL.

Action 7 Setup an Interactive PS call.










Action 10 SPI values sent to the RBS are according to the configured mapping table in parameter externalArpMapping parameter in the ArpSpiMap instance.

4 Helpful Hints

4.1 Feature Related Alarms

-

4.2 Feature Related Counters

-

4.3 Other

In this demo we use arpSpiMap(1) 14,10,6,4,2,-1,-1,-1,-1,-1-1,-1,-1,-1.

HLR useful commands to check relevant subscription properties:

# Print all QoS Profiles in the HLR: HGEQP:EQOSID=ALL;

# To change to EQOSID=2061 on PDPID=1 for an IMSI: HGPDC:IMSI=<IMSI_NUMBER>,PDPID=1, EQOSID=2061;

# Inserts new EQOSID into HLR: HGEQI: EQOSID=2062,INT,THP=1,ARP=2,DO=NO,SDU=150-7-4,MBRU=2048,MBRD=8192;

Check which QoS Profile is defined in HLR for the subscriber under test.

HGSDP:IMSI=<IMSI_NUMBER>,PDP; HGEQP: EQOSID=100;

In case Traffic Class is not a Background Traffic Class, with help of the HLR commands shown above change the EQOSID by a background profile.

HGSDP:IMSI=<IMSI_NUMBER>,PDP; HGEQP: EQOSID=302;

In case Traffic Class is not a Traffic Class Interactive PS, with help of the HLR useful commands showed above change the EQOSID by an Traffic Class Interactive profile.





With the following traces, you can check that the correct QoS mapping configuration is distributed from board 12 (O&M MP) to all RNC Module MPs. You can only see the traces if you restart the RNC Module MP or restart the node.

lh mod te config -run trace6 trace7 uehUeCtxtFroObjectArpSpiMapClas lh mod te config -run trace6 trace7 uehUeCtxtFroObjectRnlQosClassPr lh mod te config -run trace6 trace7 uehUeCtxtFroObjectTrafficClassP lh mod te config -run trace6 trace7 uehUeCtxtFroObjectTrafficClassC lh mod te config -run trace6 trace7 uehUeCtxtFroObjectTcMapC

When making a RAB Establishment, with the traces below (on the RNC Module MP) you can see the mapping from ARP-value to the SPI-value.

lh mod ueidtrace on -ue imsi <IMSI_NUMBER> lh mod te e all UE_ARP_MAP lh mod te e all ARP_MAP

With the traces below (on the RNC Module MP) you can see the ARP-value received from the CN (RANAP-RAB-Assigment Request message) and the SPI-values sent from RNC to RBS (NBAP-RL ReconfigurationPrepare message).

lh mod te e bus-send bus_receive RANAP_ASN lh mod te e bus_send bus_receive NBAP_ASN lh mod te filter set "[1]<>08 AND [1]<>18" NBAP_ASN

The SPI UL value (schedulingPriorityIndicator) is included in IE extensionValue E-DCH-FDD-Information and SPI DL value (schedulingPriorityIndicator) is included in the IE HSDSCH-FDD-Information in the NBAP RL ReconfigurationPrepare message.

Documents

DD-HSPA QoS Scheduling Priority Based on ARP PA2