HPUG UA08 V05.04 Preliminary Ext

HSxPA Parameters User Guide

Document number: UMT/IRC/APP/016664 Document issue: V05.04 Document status: UA08.1 Preliminary Date: 16/Mar/2012

External Document

HSxPA Parameters User Guide 05.04 / EN EXTERNAL 16/Mar/2012 UMT/IRC/APP/016664 UA08.1 Preliminary

Volume 1 : Introduction

Passing on or copying of this document, use and communication of its contents not permitted without AlcatelLucent written authorization

Page 1/24

CONTENTS

1 INTRODUCTION..........................................................................................................12 1.1 OBJECT ..................................................................................................................... 12 1.2 SCOPE OF THIS DOCUMENT.............................................................................................. 13 1.3 AUDIENCE FOR THIS DOCUMENT........................................................................................ 13 1.4 NOMENCLATURE ........................................................................................................... 14 1.5 RELATED DOCUMENTS .................................................................................................... 16

2 PARAMETERS ORGANIZATION...................................................................................17

3 ABBREVIATIONS ........................................................................................................19




Page 2/24

PUBLICATION HISTORY

16/03/2012

Issue 05.04 / EN,

Updates:

In Volume 1: History update;

In Volume 2: Update of information for MIMO UE categories (number of HARQ processes).

Other format changes and overall spelling/content review.

In Volume 3: Rewriting of engineering recommendation for parameters minimumHsdschCreditPerTtiInNumberOfPdus and minimumHsdschCreditPerTtiInBytes, following redesign of feature PM97431.

Correction of formula for Proportional Throughput scheduler cost, when R < serviceMinRate.

Inclusion of engineering recommendation on parameter hsdpaAmpUsage to prevent power spikes and PA alarms due to too high power usage.

Rewriting of Power Measurements section to consider fast PMM measurements introduced with feature PM75998 (also removal of note stating change in power measurements reporting period).

Clarification of MAC-d priority queue accessing by schedulers in Dual Cell configuration.

Detailing of figure presenting relation between RLC PDU, MAC-d SDU/PDU and MAC-hs SDU/PDU.

Inclusion of engineering recommendation on prohibitedStatusTimer for networks with high penetration of low-rate capable HSDPA UEs.

Correction of default value for parameter hsdpaSpiRelativeWeight, as previous one was not relevant in terms of user differentiation.

Description of parameters waitTimeBeforeHspaDeactivation and waitForResourceReleaseForHsxpaConfiguration and associated setting recommendations.

Correction of class of parameter hsdpaActivation.




Page 3/24

Update value of parameter eligibleUeCategoryForSirTargetHsdpa to include category 19 and 20 HSDPA UEs.

Removal of contents related to feature PM34465. Clarification of meaning of letters in CQI mapping tables used for 64-QAM. Inclusion of subfeature of PM34246 in features list. Correction of value for parameter isDualCellAllowedForUeCategory. Other format changes and overall spelling/content review.

In Volume 4: Change recommended values for 82602/R2 thrThresholdForActiveState and thrThresholdForInactiveState.

Correction regarding the usage of {Reference E-TFCI; Reference Power Offset} tables instances suffixed with eCEM (they are used)

Correction for feature 30742 MBR Handling in MAC-e Scheduler: it is applicable to UCU-III. Activation flag updated.

Update regarding consistency rule for edchLoadEstimationAlgorithm and hspaHardwareAllocation: if the first one is SIR_BASED, the second one must be xCemOnly in UA7 and iCemNever in UA8.

Update regarding consistency rule for edchOlpcInactivitySirDecreaseLimit : it must be bounded with minimum Sir Target and maximum Sir Target.

Change the recommended value for PM121085 parameter edchOlpcInactivitySirDecreaseLimit

Additional details on the behaviour of PM121085 in case of mobility leading to imbalance SIR conditions

Change the recommended value for G-Rake activation: it is not recommended anymore due to lack of benefit observed in the field.

Clarification about the parameter edpchInfoClassId Clarification about the RLC throughput per EDCH UE Categories

In Volume 5: Update of RAB combinations allowed for HSDPA and HSUPA. Additional details on radio conditions for configuration of SRB on HSPA with F-DPCH.

Inclusion of section with interaction between PM29810 and Always-On transitions.

Inclusion of section with interactions between PM29810 and Dual Cell operation.




Page 4/24

Addition of RAN path in tables for parameters description for feature PM82602/R3.

Large update of section on multi-RAB handling on HSxPA, taking into consideration new RAB combinations available in UA08.1, in particular 3 PDP context support in GM (PM81449) and Hsdpa / Edch user service profiles.

Change of recommended setting for parameter isThreeRabAllowed for Global Market.

In volume 6: Clarification regarding the usage of the parameter isEdchIurRestrictionEnabled.

Clarification regarding the enhancement 367062 Reconfiguration SRB EDCH to DCH 3.4kbps in case of loss of EDCH Macro-Diversity for the Uplink SRB.

Update of description of parameter mobilityServiceType, with new location under HsdpaCombination object.

In volume 7: Global content review. Section DEPLOYMENT STATUS updated to clarify the use of x/eCEM modules.

Section CELL RESELECTION FOR UA08 DEPLOYMENTS revisited/enhanced. Section IMCRA FOR UA08 DEPLOYMENTS revisited/enhanced. Section SPECIFIC HANDLING OF NETWORKS WITH MORE THAN 3 CARRIERS revisited/enhanced.

Section TYPICAL SCENARIOS FOR NEIGHBOR DECLARATION revisited/enhanced.

New section introduced named TYPICAL STRATEGY FOR IRAT MOBILITY New section introduced named TYPICAL STRATEGY FOR SMALL CELLS MOBILITY

30/09/2011

Issue 05.03 / EN,

Updates:

In Volume 1: History update; Update of abbreviations list.




Page 5/24

In Volume 2: Inclusion of feature PM32520 - HSDPA AND E-DCH Service Indicator; Correction of reference list; Restructuring of sections with separated descriptions for iCEM and xCEM/eCEM, placing some for focus on the latter;

Update of information for MIMO categories (number of HARQ processes and modulation);


In Volume 3: Restructuring of sections with separated descriptions for iCEM and xCEM/eCEM, placing some for focus on the latter;

Removal of description of parameter activityFactorCcch (replaced by reference to UPUG, on which CAC procedure is described);

Reorganization of section 8 (power management) with inclusion of features PM75998 and PM29808, moving of sections covering hsdpaAmpUsage and HS-SCCH power;

Correction of range of maximumTokenGenerationRate parameters for UL and DL;

Clarifications in description of parameters defining the maximum number of simultaneous DC-HSDPA users;

Removal of section 9.1 (moved to Volume 2) on feature PM32520 - HSDPA AND E-DCH Service Indicator;


In Volume 4: Change recommended value for parameters nHarqRetransTargetS1, nHarqRetransTargetS2, nHarqRetransTargetS3 for SRB_EDCH

Clarification regarding the NodeB internal power checks rules on eagchPower, ehichPowerSignature and ergchPowerSignature.

Correction for the content of 10ms_2xSF4_xCEM reference power offset Reorganization of section 4 (Power management for E-DCH) with inclusion of iCEM specific features for UL load previously described in section 6(Mac-e scheduler for iCEM).

Change recommended values for edchThrRatioForHarqRetransTarget1, edchThrRatioForHarqRetransTarget2, nHarqRetransPowerLimitTarget2.

Removal of parameter guardTimeForNHarqTargetChange




Page 6/24

Removal of section 8 (Iu user traffic conformance): MBR feature is now described in section 6 (MAC-E scheduler).

Reorganization of section 6 (Mac-e scheduler for iCEM) and section 7 (Mac-e scheduler for xCEM, eCEM, UCU-III): both sections merged into one and focus done on xCEM, eCEM and UCU-III.

Removal of section 11 OneBTS Parameters: OneBTS Parameters spread in the relevant sections.


In Volume 5: Clarifications on criteria used for F-DPCH and SRB on HSPA configuration, interactions with feature PM33581 and UL power control configuration;

Correction of title of table 9; Inclusion of old section 2.2 in RAB Matching section (chapter 3.1); Correction for 125171/125567 E-DCH Enhanced NodeB CAC: the CAC formula for UCU-III is corrected and the recommended value for credits on UCU-III is updated.

Addition of a global overview of HSXPA CAC features and restructuring of sections with separated description for HSDPA CAC and EDCH CAC

Modification of the recommendation for the E-DCH CAC features: RNC EDCH CAC (34441.1) is not needed as soon as NODEB EDCH CAC (125171/125567 and 82602/R3) are activated.

Clarification for EDCH fallback mechanisms. Other format changes and overall spelling/content review.

In Volume 6: Section 3.3.5 added to describe SRB over HSDPA to SRB DCH 3.4KBPS reconfiguration.

In "Figure 3: E-DCH macro diversity general principle", it said "For a given CFN, multiple E-DCH Data Frames may be received from different NodeBs. First correctly received Data Frame is selected, others are discarded." Replaced CFN by TTI in section 3.3.3.1.1.

In section 3.3.3.1.1, added condition the new added cell is not over Iur when SRB on EDCH is used.

Refined the description and formulas used in sections 3.3.3.1.4, 3.3.3.2.3 and 3.3.3.2.4.

Refined text in section 3.6. Corrected typo in section 4.3. Added the definition of TMA in section 3.2.




Page 7/24

In section 3.3.3.2.2 figure 4, the maximum number of HoConfClass instance is up to 60 in UA8.1; correction made.

In Volume 7: Section 5.1 on PA Power Pooling has been transferred to Volume 3, as section 8.6;

New section added: SPECIFIC HANDLING OF NETWORKS WITH MORE THAN 3 CARRIERS;

Overall content review.

22/07/2011

Issue 05.02 / EN,

Updates:

In Volume 1: History update.

In Volume 2: Remove of the parameters related to HS-DPCCH power offset. A dedicated section for HS-DPCCH power management is created in Volume 3.

In Volume 3: Creation of a section dedicated to HS-DPCCH power management. Introduction of feature 82602/R7: Adaptive HS-DPCCH power offset Update values for minimumHsdschCreditPerTtiInNumberOfPdus and minimumHsdschCreditPerTtiInBytes parameters when feature PM97431 is active (engineering recommendations added)

Update values for hsdschSlowStartActivation parameter when feature PM97431 is active (engineering recommendations added)

Update of solution description for PM97431, following redesign of the feature, and inclusion of description in feature overview section

Correction of range of values allowed for serviceHighRate and serviceLowRate parameters

Introduction of feature 114637 Dual Cell HSDPA support on OneBTS Introduction of feature 104832/118154 Dual-Cell HSDPA capacity increase




Page 8/24

In Volume 4: Introduction of feature 82602/R1: Throughput increase in UE power limitation

Introduction of feature 82602/R2: Enhanced load criterion for adjusting HARQ retransmissions

Introduction of feature 121085: UL power saving with EDCH OLPC Introduction of feature 82602/R4: Optimized Iub Congestion Control Update edpchParameters name and selection algorithm. The content (reference etfci, reference power offset) is not changed, only naming is changed.

Update recommended value for maxNrOfErgchEhich: default recommendation is now to use the maximum value 4.

Replacement of some reserved parameters (temporary) with new permanent parameters

Details added on MAC-e scheduler behaviour in case of overload.

In Volume 5: Introduction of feature 82602/R3: Improved CAC scheme for 2ms TTI users Introduction of feature 29810: Fractional DPCH and SRB over HSPA Introduction of feature 125171/125567 NodeB E-DCH CAC Evolution Update recommendations for edchMaxLegs2msPerCell Update RAN model concerning the HSPA combinations: the 3-dimensions-array HsdpaCombinationList.HsdpaCombinationEntry.allowedList is replaced with a flat structure HsdpaCombination. Same for Edch.

In Volume 6: Introduction of feature 104832/118154 Dual-Cell HSDPA capacity increase (part of the feature dealing with the incoming relocation improvement)

Description of the enhancement reconfiguration of SRB from EDCH to DCH 3.4

Add a note on iurEdchDelayVariation (parameter defined but not used by the system)

In Volume 7: Complete and exhaustive reorganisation for Carrier Deployment and Strategy recommendations section to cope with UA08 functionalities. Some sections were deleted. New sections were included.

New section added: ONEBTS 6 CARRIER 2NB CONFIGURATION (120426).




Page 9/24

25/03/2011

Issue 05.01 / EN,

Updates:

In Volume 1: History update.

In Volume 2: Insertion of the RAN Path for all the parametrer description.

In Volume 3: Insertion of the RAN Path for all the parametrer description. Update regarding parameter hsdpaResourceActivation. Correction of the value (in MBit/s) corresponding to parameter maximumTokenGenerationRate.

Additional clarifications on how parameter enhancedQualityOfService (congestion management) relates with minBR.

In Volume 4: Insertion of the RAN Path for all the parametrer description. Update regarding the parameter edchResourceActivation. Reorganization and updates in the UL Load Management section. Reorganization and updates in the Priority Info in MACe Scheduler section. Correction regarding the maximum number of E-DCH Radio Links supported by one E-RGCH/E-HICH for the xCEM and eCEM: 18 is the maximum instead of 19.

Update regarding the maximum number of E-RGCH/E-HICH supported by the UCU-III: it is now 6 (instead of 4). It is unchanged (4) for the xCEM and eCEM.

Update feature 125855 E-DCH call retainability improvements.

In Volume 5: Insertion of the RAN Path for all the parametrer description. Clarification regarding the parameters edchMaxUsersPerCell and edchMaxLegs2msPerCell.




Page 10/24






Page 11/24

FIGURES

Figure 1: Static and Configuration Parameters 17




Page 12/24

1 INTRODUCTION

1.1 OBJECT

The HSxPA Parameters User Guide (HPUG) document provides parameters setting recommendations from Alcatel-Lucents experience, coming from studies, simulations and experimentations. It gives the rationales of these settings by describing the HSDPA & E-DCH (HSUPA) system from an engineering point of view. It also gives some engineering rules related to parameters settings. This includes a system description, configuration aspect and engineering recommendations.

The HPUG does not contain the complete list of configuration parameters, this objective being covered in [R01].

The parameters described in this document are mainly customer configuration parameters accessible by the customer (operator) via the MMI of the OMC. Nevertheless, some manufacturer configuration parameters as well as some static parameters are also covered when they are required to understand the different UMTS mechanisms.

In the case where the recommended values of the HPUG are different from any other document, the HPUG recommended should prevail.

The parameter values in HPUG are the recommended values by Alcatel-Lucent, which means that they are the best values to achieve the optimal network performance.

A common and single load is delivered to address the needs of all Alcatel-Lucent WCDMA customers, which are grouped into two different markets due to their particular functional specificities:

USA Market, i.e. customers with UTRAN where Alcatel-Lucent 939X Node B (former Lucent OneBTS) is deployed

Global Market, i.e. any other customers

This document provides a description of the features included in the UA06 release. At the beginning of each volume, a table has been added to clearly indicate to which market, among the two listed previously, each feature is applicable to. Note that one feature can belong to one or two markets but:

A feature which is not applicable to USA Market is not supported on a UTRAN with Alcatel-Lucent 939X Node B (former Lucent OneBTS).

For features common to USA market and Global markets, the behaviour on UTRAN with 939X Node B might be different from other Alcatel-Lucent Node B products, in which case the differences are described in the Hardware Dependencies section.

Features are by default not supported on 9313 neither Micro Node B nor 9314 Pico Node B. For the list of features supported on these products please refer to 33341 Alcatel-Lucent 9313 Micro Node B and 33342 Alcatel-Lucent 9314 Pico Node B descriptions.




Page 13/24

1.2 SCOPE OF THIS DOCUMENT

Features behaviour or features can be specific to one board or common for several boards. In the next volumes, the following rule is applied to define the feature applicability:

Tag [iCEM] indicates that the behaviour or the feature is specific to iCEM. Tag [xCEM] indicates that the behaviour or the feature is specific to xCEM

only or to xCEM and UCU-III if there is no [UCU-III] tag.

Tag [UCU-III] indicates that the behaviour or the feature is specific to [UCU-III].

Tag [eCEM] indicates that the behaviour or the feature is specific to eCEM. The term OneBTS in this document refers only to those NodeBs equipped with

UCU-III board in the US Market.

No tag indicates that the behaviour or the feature is common for all the boards.

R99 related features and settings are not part of this document. Please refer to [R01]a.[R02].

The HSxPA Parameters User Guide is not supposed to present the whole Plan of record. For accurate Plan of record and feature delivery information please refer to your account and PLM prime.

Refer also to [R06] for more information on features available for the current UTRAN release.

Restriction: Pico/Micro NodeB

The Pico/Micro NodeB product is out of scope of this document, thus all engg information, algorithms description and parameters values provided in this document are strictly related to standard Alcatel-Lucent NodeB products.

See [R07] for details related to HSxPA implementation in Pico & Micro NodeB.

1.3 AUDIENCE FOR THIS DOCUMENT

This document targets an audience involved in the following activities:

RF engineering UTRAN Data fill Trials and FOA




Page 14/24

1.4 NOMENCLATURE

The parameter names are written in bold italic. The objects names are written in bold. The parameters properties are presented as follow:

Parameter Object Range & Unit User Class

Granularity

Value

The protocol messages are written in CAPITAL LETTERS. The Information Elements (IE) contained in the protocol messages are written the

following way: TPC_DL_Step_Size.

The data fill rules are presented as the following: Rule:

The system restrictions are presented as the following: Restriction:

The engineering recommendations on parameter value are presented as the following:

Engineering Recommendation:

The difference between Release N and Release N-x are presented as the following:

UAN-x-UAN Delta:

Some parameters values can not be provided in this document; in that case, the following abbreviations are used:

o N.A.: Not Applicable. o N.S.: Not Significant.




Page 15/24

o O.D.: Operator Dependant (depends on operator network specific configuration. Example: addressing parameters).




Page 16/24

1.5 RELATED DOCUMENTS

Reference documents:

[R01] NTP 411-8111-813 Access Network Parameters

[R02] UMT/DCL/DD/0020 UTRAN Parameters User Guide

[R03] UMT/IRC/APP/0164 Iub transport Engineering Guide

[R04] UMT/IRC/APP/025147 CEM Capacity Engineering guide

[R05] UMT/IRC/APP/007147 Product Engineering Information

[R06] UMT/SYS/INF/030972 UA08.1 Feature Planning Guide

[R07] UMT/BTS/INF/016135 Micro NodeB & 9314 Pico NodeB Feature Planning Guide



2 PARAMETERS ORGANIZATION

In order to understand the definition and the role of the different parameters, it is appropriate to explain how these parameters are linked together and grouped within the RAN model.

For more information on the RAN model, please refer to [R01].


Page 17/24

RNC OMC WPS

Static

Non-Static

WPS Templates

Manufacturer

Customer

CIQ

OMC database System DRF

Figure 1: Static and Configuration Parameters

There are two main kinds of parameters in Alcatel-Lucents system, the static and configuration parameters.

The static parameters have the following characteristics:

They have a fixed value and cannot be modified at the OMC. They are part of the network element load. A new network element needs to be reloaded and built in order to change their values. The customer cannot modify them.

The configuration parameters have the following characteristics:

They are contained in the OMC database. They are subdivided in two main types: User / Manufacturer.

o Customer: Can be modified by the customer at the OMC (at the MMI or with DRFs).




Page 18/24

o Manufacturer: They represent system constants defined by the manufacturer. They do not appear at the MMI neither in the DRFs.

Regardless of the parameter type (customer or manufacturer), the parameters can have the following classes:

o Class 0: the value of the parameter is set at the parent object creation. Currently, most of the objects can only be killed and re-created through a new MIB built (either btsEquipmentMIB or rncMIB).

o Class 1: new parameter value is taken into account on the next RNC restart. This class is no longer valid.

o Class 2: parameters of an object created at the OMC-R (respectively OMC-B) can only be set when the object and its parent are both locked. The new value will be taken into account after the object is back to working state (administrative state set to unlocked).

o Class 3: parameters of an object created on the OMCR (respectively OMC-B) can be modified when the object (and parent object) is unlocked. The new value is taken into account immediately.

Class 3-A1: new value is immediately taken into account. Class 3-A2: new value is taken into account upon event reception

(service establishment, SRLR).

Class 3-B: new value is taken into account for next call.




Page 19/24

3 ABBREVIATIONS

ACK Acknowledgment

AICH Acquisition Indicator Channel

AM Acknowledged Mode

AMC Adaptive Modulation and Coding

ARP Allocation Retention Priority

ARQ Automatic Repeat Request

ATM Asynchronous Transfer Mode

AS Active Set

BBU Base-Band Unit

BLER Block Error Rate

CAC Call Admission Control

CC Chase Combining

CCPCH Common Control Physical Channel

CE Channel Element

CEM Channel Element Module

CFN Connection Frame Number

CM Compressed Mode

CN Core Network

CP Passport: Control Processor

CPICH Common Pilot Channel

CRC Cyclic Redundancy Check

CS Circuit Switched

DCH Dedicated Channel

DCPS Dual Core Packed Server

DCTM Dynamic Code Tree Management

DDM Dual Duplexer Module

DL Downlink

DPCCH Dedicated Physical Control Channel

DPDCH Dedicated Physical Data Channel

DS Delay Sensitive

DS1 Digital Signal level 1 (1.544 Mbit/s)

DTX Discontinuous Transmission

E-AGCH Enhanced Access Grant Channel

ECC E-DCH Congestion Control




Page 20/24

E-DCH Enhanced DCH (also referred as HSUPA or EUL)

E-DPCCH Enhanced Dedicated Physical Control Channel

E-DPDCH Enhanced Dedicated Physical Data Channel

E-HICH Enhanced Hybrid ARQ Indicator Channel

E-RGCH Enhanced Relative Grant Channel

E-TFC E-DCH Transport Format Combination

E-TFCI E-DCH Transport Format Combination Indicator

EUL Enhanced Uplink (stands for E-DCH)

EVM Error Vector Magnitude

FP 3GPP: Frame Protocol

Alcatel-Lucent Passport: Function Processor

FRS Feature Requirements Specification

GMM GPRS Mobility Management

G-RAKE Generalized rake receiver

GRF Global Reduction Factor

H-ARQ Hybrid ARQ

HCS Hierarchical Cell Structure

HS-DSCH High Speed Downlink Shared Channel

HS-SCCH Shared Control Channel for HS-DSCH

HSDPA High-Speed Downlink Packet Access

HSUPA High-Speed Uplink Packet Access

HHO Hard Handover

HO Handover

IE Information Element

iMCTA intelligent Multiple Carrier Traffic Allocation

iMCRA intelligent Multiple Carrier Re-direction Algorithm

iRM intelligent RAB mapping

IMEI International Mobile Equipment Identification

IMSI International Mobile Subscriber Identification

IP Internet Protocol

IR Incremental Redundancy

ISI Inter-Symbol interference

KPI Key Performance Indicator

LA Location Area

LAC Location Area Code

LCG Local Cell Group

LUT Look-Up Table

MAC Medium Access Control




Page 21/24

MCPA Multi-Carrier Power Amplifier (also referred as PA)

MCS Modulation and Coding Scheme

MIB 3GPP: Master Information Block;

Alcatel-Lucent RNC/NodeB: Management Information Base

MMI Man-Machine Interface

MO Mobile Originated

MPO Measurement Power Offset

MT Mobile Terminated

NACK Negative Acknowledgement

NAS Non Access Stratum

NBAP NodeB Application Part

NDS Non-Delay Sensitive

OAM Operations, Administration and Maintenance

OCNS Orthogonal Channel Noise Simulator

OLPC Outer-Loop Power Control

OLS Olympic Level Service

OMC Operations and Maintenance Center

OMC-B OMC NodeB

OMC-R OMC RNC

OVSF Orthogonal Variable Spreading Factor

PA Power Amplifier (stands for MCPA)

P-CCPCH Primary CCPCH

PCPCH Physical Common Packet Channel

P-CPICH Primary CPICH

PCR Peak Cell Rate

PDU Protocol Data Unit

PICH Paging Indicator Channel

PLMN Public Land Mobile Network

PRACH Physical Random Access Channel

PS Packet Switched

P-SCH Primary SCH

PSCR Physical Shared Channel Reconfiguration

PSFP Packet Server Functional Processor

QAM Quadrature Amplitude Modulation

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Registration Area

RAB Radio Access Bearer




Page 22/24

RACH Random Access Channel

RAN Radio Access Network

RANAP Radio Access Network Application Part

RAT Radio Access Technology

RB Radio Bearer

RG Relative Grant

RL Radio Link

RLS Radio Link Set

RLC Radio Link Control

RMS Root Mean Square

RNC Radio Network Controller

RNC-AN RNC Access Node

RNC-CN RNC Control Node

RNC-IN RNC Interface Node

RNS Radio Network Subsystem (an RNC and its associated NodeBs)

RoT Rise over Thermal

RRC Radio Resource Control

RRM Radio Resource Management

RSCP Received Signal Code Power

RSEPS Received Scheduled E-DCH Power Share

RSN Retransmission Sequence Number

RSSI Received Signal Strength Indicator

RTWP Received Total Wideband Power

SCCP Signalling Connection Control Part

S-CCPCH Secondary CCPCH

SCH Synchronization Channel

S-CPICH Secondary CPICH

SCR Sustainable Cell Rate

SDU Service Data Unit

SE Spectral Efficiency

SF Spreading Factor

SFN System Frame Number

SHO Soft Handover

SI Scheduling Information

SIB System Information Block

SM Session Management

SRB Signalling Radio Bearer

SRLR Synchronous Radio Link Reconfiguration




Page 23/24

SS7 Signalling System 7

S-SCH Secondary SCH

STM1 Synchronous Transport Module-1 (155.52 Mbit/s)

SW Scheduling Weight

TFC Transport Format Combination

TFCI Transport Format Combination Indicator

TFCS Transport Format Combination Set

THP Traffic Handling Priority

TM Transparent Mode

TNL Transport Network Layer

TPR Traffic-To-Pilot Ratio

TRB Traffic Radio Bearer

TrCH Transport Channel

TRM Transceiver Module

TS Technical Specification

TTI Transmission Time Interval

UBR Unspecified Bit Rate

UE User Equipment

UL Uplink

UM Unacknowledged Mode

URA UTRAN Registration Area

UTRAN Universal Terrestrial Radio Access Network

VCC Virtual Channel Connection

VP Virtual Path

WiPS Wireless Provisioning System




Page 24/24

Z END OF DOCUMENT Y

UMT/IRC/APP/016664 V05.04HSXPA PARAMETERS USER GUIDE UA08 16/MAR/2012

Copyright 2011 by Alcatel-Lucent. All Rights Reserved.

About Alcatel-Lucent

Alcatel-Lucent (Euronext Paris and NYSE: ALU) provides solutions that enable service providers, enterprises and governments worldwide, to deliver voice, data and video communication services to end-users. As a leader in fixed, mobile and converged broadband networking, IP technologies, applications, and services, Alcatel-Lucent offers the end-to-end solutions that enable compelling communications services for people at home, at work and on the move. For more information, visit Alcatel-Lucent on the Internet: http://all.alcatel-lucent.com

Notice

The information contained in this document is subject to change without notice. At the time of publication, it reflects the latest information on Alcatel-Lucents offer, however, our policy of continuing development may result in improvement or change to the specifications described.

Trademarks

Alcatel, Lucent Technologies, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Alcatel-Lucent Proprietary


CONTENTS

1 INTRODUCTION

2 HSXPA OVERVIEW

3 HSDPA PRINCIPLES, SCHEDULING & RESOURCE MANAGEMENT

4 HSUPA PRINCIPLES, SCHEDULING & RESOURCE MANAGEMENT

5 CALL MANAGEMENT

6 MOBILITY

7 DEPLOYMENT SCENARIOS



HSXPA PARAMETERS USER GUIDE

1 INTRODUCTION



HSXPA PARAMETERS USER GUIDE

2 HSXPA OVERVIEW



Volume 2 : HSxPA Overview


Page 1/40

CONTENTS

1 INTRODUCTION............................................................................................................4 1.1 OBJECT ....................................................................................................................... 4 1.2 SCOPE OF THIS DOCUMENT................................................................................................ 4

2 RELATED DOCUMENTS .................................................................................................5 2.1 HPUG VOLUMES ............................................................................................................ 5 2.2 REFERENCE DOCUMENTS ................................................................................................... 5

3 SYSTEM OVERVIEW......................................................................................................6 3.1 HSDPA ....................................................................................................................... 9

3.1.1 Transport and physical channels ............................................................................ 9 3.1.1.1 Downlink channels .......................................................................................... 12 3.1.1.2 Uplink channels............................................................................................... 13 3.1.2 Fast link adaptation ............................................................................................ 16 3.1.3 Fast Retransmission Mechanism (HARQ)............................................................... 17 3.1.3.1 Number of HARQ Processes ............................................................................. 17 3.1.3.2 RV Parameters................................................................................................ 19 3.1.3.3 State of HARQ Processes ................................................................................. 21 3.1.3.4 Choice of the HARQ type ................................................................................. 23 3.1.4 Fast scheduling .................................................................................................. 26

3.2 HSUPA (E-DCH) ........................................................................................................ 28 3.2.1 Transport and physical channels .......................................................................... 28 3.2.1.1 Uplink channels............................................................................................... 30 3.2.1.2 Downlink channels .......................................................................................... 33 3.2.2 UA7 implementation of E-DCH ............................................................................. 36

3.3 HSDPA AND E-DCH SERVICE INDICATOR ........................................................................... 36

4 UE CATEGORIES .........................................................................................................38 4.1 HSDPA ..................................................................................................................... 38 4.2 HSUPA ..................................................................................................................... 39




Page 2/40

TABLES

Table 1: HSUPA / HSDPA comparison 8 Table 2: Number of processes per UE category for xCEM and eCEM 17 Table 3: Number of processes per UE category for UCU-III 18 Table 4: Number of processes per UE category for iCEM 18 Table 5: RV coding for 16QAM 20 Table 6: RV coding for QPSK 20 Table 7: RV update table in the IR case (Trv[i]) 23 Table 8: RV update table in the CC case (Trv[i]) 23 Table 9: RV update table in the MIR case (Trv[i]) 24 Table 10: RV update table in the PIR case (Trv[i]) 24 Table 11: RV updates tables when harqType set to Dynamic Redundancy 25 Table 12: E-DPDCH slot formats 31 Table 13: E-DPCCH slot formats 31 Table 14: E-DPCCH power offset index vs. amplitude 33 Table 15: Relative grant information (E-RGCH) 34 Table 16: ACK/NACK information (E-HICH) 35 Table 17: HSDPA UE categories (3GPP TS25.306) 38 Table 18: HSUPA UE categories (3GPP TS25.306) 39




Page 3/40

FIGURES

Figure 1: R99 principle................................................................................................................. 6 Figure 2: HSDPA principle ............................................................................................................ 6 Figure 3: HSDPA layer2/layer1 flows ............................................................................................. 7 Figure 4: MAC-hs entity on UTRAN side......................................................................................... 7 Figure 5: Protocol Architecture of E-DCH .......................................................................................9 Figure 6: UE side MAC architecture ............................................................................................... 9 Figure 7: Transport channel configuration (without HSUPA) .......................................................... 10 Figure 8: HSDPA channels and associated R99 channels ............................................................... 11 Figure 9: HSDPA channels for HSDPA-DC operation...................................................................... 11 Figure 10: Timing relationship at NodeB between physical channels............................................... 12 Figure 11: HS-SCCH structure..................................................................................................... 13 Figure 12: HS-PDSCH structure .................................................................................................. 13 Figure 13: HS-DPCCH structure .................................................................................................. 14 Figure 14: HS-DPCCH ACK/NACK structure for dual cell/carrier calls............................................... 14 Figure 15: HS-DPCCH CQI mapping for dual cell/carrier calls......................................................... 15 Figure 16: Example of throughput or BLER versus radio conditions for different modulation............. 17 Figure 17: RV parameters assignment algorithm .......................................................................... 21 Figure 18: ACK/NACK/DTX management for HARQ processes........................................................ 22 Figure 19: Dynamic selection of HARQ type ................................................................................. 26 Figure 20: HSUPA channels and associated R99 channels ............................................................. 29 Figure 21: E-DPCCH / E-DPDCH frame structure .......................................................................... 31 Figure 22: E-DPDCH/E-DPCCH multiplexing on I/Q....................................................................... 32 Figure 23: Uplink physical channels multiplexing .......................................................................... 32 Figure 24: E-AGCH frame structure ............................................................................................. 33 Figure 25: E-HICH frame structure.............................................................................................. 35




Page 4/40

1 INTRODUCTION

1.1 OBJECT

The objective of this document is to describe from an engineering point of view the HSDPA & E-DCH (HSUPA) system.

This includes a system description, configuration aspect and engineering recommendations.

1.2 SCOPE OF THIS DOCUMENT

This document gives an overview of the HSxPA system.




Page 5/40

2 RELATED DOCUMENTS

2.1 HPUG VOLUMES

[Vol. 1] Introduction

[Vol. 2] HSxPA overview

[Vol. 3] HSDPA principles scheduling and resource management

[Vol. 4] E-DCH principles scheduling and resource management

[Vol. 5] Call Management

[Vol. 6] Mobility

[Vol. 7] Deployment scenarios

2.2 REFERENCE DOCUMENTS

[R01] 3GPP TS 25.308 UTRA High Speed Downlink Packet Access (HSPDA); Overall description; Stage 2

[R02] 3GPP TS 34.108 Common Test Environments for User Equipment (UE) Conformance Testing

[R03] 3GPP TS 25.212 Multiplexing and channel coding (Release6)

[R04] 3GPP TS 25.214 Physical layer procedures (FDD)

[R05] 3GPP TS 25.306 UE Radio Access capabilities definition

[R06] 3GPP TS 25.213 Spreading and modulation (FDD)

[R07] UMT/BTS/INF/016135 Micro NodeB & 9314 Pico NodeB Feature Planning Guide

[R08] UMT/IRC/APP/007147 UMTS BTS Product Engineering Information

[R09] UMT/SYS/DD/013319 HSDPA System Specification

[R10] UMT/BTS/DD/027736 eCEM/eCEM-U CCM OAM High Level Design



3 SYSTEM OVERVIEW

HSDPA

3GPP has standardized HSDPA in Release 5 [R01] in order to increase maximum user throughput for downlink packet data (streaming, interactive and background traffic classes) and decrease downlink packet transmission delay. This Release 5 is fully compatible with the previous Release 99 (R99).

In R99, data are transmitted on a dedicated channel with a given user throughput and a downlink transmitted power controlled according to the radio conditions:

PowerPowerControlControl

Data Power

Unused Power Data

Unused

Same Throughput

Figure 1: R99 principle

In HSDPA, data are transmitted on a shared channel by using all the available power and by controlling the downlink user throughput according to the radio conditions:

RateRateAdaptationAdaptation 100% Power

100%

Figure 2: HSDPA principle

Typically, a user in good radio conditions will receive his data with a high bit rate whereas a user in bad radio conditions will receive his data with a lower bit rate.

The efficiency of this rate adaptation is due to a new MAC entity, the MAC-hs layer, located in the NodeB (see the two following figures), near the physical channel, which allows a high reactivity in the resource allocation according to the RF conditions


Page 6/40



changes. This MAC-hs layer manages the scheduling of users and the retransmissions of packets.

HS-DSCHAssociated

UplinkSignaling

AssociatedDownlinkSignaling

DCCH DTCHDTCHMAC Control MAC ControlCCCH CTCHBCCHPCCHMAC Control

RRC (RNC)RRC (RNC)

RLC (RNC)RLC (RNC)


Page 7/40

HS-PDSCH

FACH

S-CCPCH

FACH

S-CCPCH

RACH

PRACH

RACH

PRACH

DSCH

PDSCH

DSCH

PDSCH

DCH

DPCH

CPCH

PCPCH

CPCH

PCPCH

PCH

S-CCPCH

PCHPCH

S-CCPCHHS-DPCCHHS-SCCH

MAC-c/sh(C-RNC)

MAC-c/sh(C-RNC)

DCH

DPDCH/DPCCH

R99 L1: Channel Coding / Multiplexing (NodeB)R99 L1: Channel Coding / Multiplexing (NodeB)R5 L1: HSDPA (NodeB)R5 L1: HSDPA (NodeB)

MAC-d(S-RNC)

MAC-hs(NodeB)

MAC-hs(NodeB)

Figure 3: HSDPA layer2/layer1 flows

Figure 4: MAC-hs entity on UTRAN side

HSDPA benefits are based on:

New transport and physical channels. Fast link adaptation.




Page 8/40

Fast retransmission mechanism (HARQ). Fast scheduling. Efficient load sharing between anchor and supplementary carriers

HSUPA

3GPP has standardized HSUPA (official name is E-DCH) in release 6 in order to increase maximum user coverage and throughput for uplink packet data and decrease uplink packet transmission delay. This Release 6 is fully compatible with the previous Releases (R99 and R5).

HSUPA uses the same new techniques of HSDPA:

Fast scheduling Fast retransmission mechanism (HARQ)

Macrodiv TTI Modulation

Channel coding

Power control

HARQ Fast

scheduling Fast link

adaptation

HSDPA Not

supported 2 ms only

QPSK, 16QAM, 64QAM

Turbo No Supported Supported Supported

HSUPA Supported 2 ms, 10 ms

BPSK and QPSK

Turbo Yes Supported Supported but less reactive

Supported but less reactive

Table 1: HSUPA / HSDPA comparison

The physical layer is similar to R99:

BPSK modulation only, QPSK is used when there is more than one E-DPDCH physical channel (SF4).

Turbo coding Spreading on a separate OVSF code and scrambling together with other

physical channels.

HSUPA is power controlled as for R99. Indeed, HSUPA channels have a power offset relative to DPCCH.



PHY PHY

EDCH FP EDCH FP

IubUE NodeBUu

DCCH DTCH

TNL TNL

DTCH DCCH

MAC-e

SRNC

MAC-d

MAC-e

MAC-d

MAC-es / MAC-e

MAC-es

Iur

TNL TNL

DRNC

Figure 5: Protocol Architecture of E-DCH

A ssociated D ow nlink S ignalling

E -D C H

M A C -d

FA C H R A C H

D C C H D TC HD T C H

D SC H D C H D C H

M A C C ontrol

U SC H ( T D D only )

C PC H ( FD D only )

C T C H B C C H C C C H SH C C H( T D D only )

PC C H

PC H FA C H

M A C -c/sh

U SC H ( T D D only )

D SC H

M A C -hs

H S-D SC H A ssociated

U plink S ignalling

A ssociated D ow nlink S ignalling

M A C -es / M A C -e

A ssociated U plink

S ignalling

Figure 6: UE side MAC architecture

3.1 HSDPA

3.1.1 TRANSPORT AND PHYSICAL CHANNELS

In R99, downlink data are sent on a DCH (Dedicated CHannel) which is mapped on the DPDCH (Dedicated Physical Data CHannel). In HSDPA, downlink data are sent on a HS-DSCH (High Speed Downlink Shared CHannel) which is mapped on one or several HS-PDSCH (High Speed Physical Downlink Shared CHannel). Users are multiplexed on the HS-DSCH channel in time and code. Transmission is based on shorter sub-frames of 2ms (TTI) instead of 10ms in R99.


Page 9/40



In downlink, the HS-PDSCH channels are transmitted with the HS-SCCH (High Speed Shared Control CHannel) channel. This channel is broadcasted over the cell but his information concerned only the user who has to receive the HS-PDSCH. The HS-SCCH allows the user to know if the HS-PDSCH is for him and to decode them correctly.

Radio conditions information and acknowledgement are reported by the UE to the NodeB through the HS-DPCCH channel. This channel allows the NodeB to adapt the downlink data rate and to manage retransmission process. The HS-DPCCH is divided in two parts. The first one is the Channel Quality Indicator (CQI) which is a value between 1 and 30 characterizing the radio conditions (1 = bad radio conditions and 30 = good radio conditions). The second one is the acknowledgement information: if data are well received by the UE, the UE sends to the NodeB an Ack, otherwise a Nack.

HS-DSCH channel is always associated to a DCH. This induces the following transport channel configuration for any UE established in HSDPA (see the following figure):

One DCH handling the signaling in both UL and DL, One DCH transporting the UL traffic (or E-DPDCH if HSUPA is used, please

refer to section 3.2),

One HS-DSCH for the DL traffic.

Figure 7: Transport channel configuration (without HSUPA)


Page 10/40



The following figure summarizes the different channels needed for a HSDPA call:

NodeB

HSDPA UE

HS-PDSCH for data (I/B) trafficHS-PDSCH for data (I/B) traffic


Page 11/40

HSDPA channelsHSDPA channels

HS-SCCH signaling part (UE id, ) associated to HS-PDSCHHS-SCCH signaling part (UE id, ) associated to HS-PDSCH

HS-DPCCH Feedback informationHS-DPCCH Feedback information

Associated DPCH for data, speech + SRB trafficAssociated DPCH for data, speech + SRB traffic

Figure 8: HSDPA channels and associated R99 channels

The maximum bit rate that can be achieved in the UL can be the bottleneck for the maximum bit rate achievable in the DL. For instance, excessive delay of RLC/TCP acknowledgements due to low bandwidth in the UL will limit the DL throughput, even if the RF conditions would allow more.

From UA04.2, the RB adaptation feature is supported. This feature dynamically adapts the UL bit rate to the amount of traffic carried over the RB. UL adaptation ranges from 8kbps up to 384kbps, but 8kbps is not recommended to be activated (configured as eligible). Therefore, although UL:8 DL:[max bit rate for low UE categories] will be allocated by the RNC if UL:8 is explicitly requested in the RAB assignment, it is not recommended to do so, otherwise the user will experience low throughput in the DL.

From UA7.1.2, dual cell HSDPA will target DC capable UE using two schedulers on adjacent carrier cells with following L1 channels on each cell.

Figure 9: HSDPA channels for HSDPA-DC operation



The following flowchart describes the timing relations between the different physical channels:

HS-SCCH#2

ACK ACK ACK7,5 slots

HS-SCCH#1

HS-PDSCH

N_acknack_transmit = 2

2 ms

HS-DPCCH

2 slots

Figure 10: Timing relationship at NodeB between physical channels

3.1.1.1 DOWNLINK CHANNELS

The mobile receives a HS-SCCH subframe (see the following figure) containing control information among which:

Channelization-code-set information (7 bits slot #0 of subframe) Modulation scheme information (1 bit slot #0 of subframe), i.e. value 0 is

QPSK and value 1 is 16QAM or 64-QAM (distinction between 16-QAM and 64-QAM is explained in [R09])

Transport-block size information (6 bits slots #1 & #2 of subframe) Hybrid-ARQ process information (3 bits slots #1 & #2 of subframe) Redundancy and constellation version (3 bit slots #1 & #2 of subframe) New data indicator (1 bit slots #1 & #2 of subframe) UE identity (16 bits used as a mask in slots #0, #1 & #2 of subframe), i.e.

subset of the HRNTI

The SF is fixed to 128. It indicates to which UE data is intended to, on which codes and with which parameters. There are as many HS-SCCH transmitted during a TTI as scheduled user number.


Page 12/40



Data

Slot #0 Slot #1 Slot #2

1 HS-SCCH subframe = 2ms

Tslot = 2560 chips = 40 bits

Figure 11: HS-SCCH structure

A mobile decoding its identity in the slot #0 of an HS-SCCH knows that it has been assigned resources on the HS-PDSCH channels (as indicated, with modulation, in this slot #0, other information are given in slots #1 and 2): the mobile receives a transport block on one or several HS-PDSCH (see the following figure).

M= 2 for QPSK (960 coded bits per TTI)M = 4 for 16QAM (1920 coded bits per TTI)M = 6 for 64QAM (2880 coded bits per TTI)

Data

Slot #0 Slot #1 Slot #2

1 HS-PDSCH subframe = 2ms

Tslot = 2560 chips = M*10*2k bits (k = 4, SF16)

Figure 12: HS-PDSCH structure

The HS-PDSCH on which is mapped the HS-DSCH carries only the data payload. The SF is equal to 16 and up to 15 codes can be reserved to HS-PDSCH per cell. One HS-DSCH can be mapped onto one or several HS-PDSCH (the maximum number of codes is given by UE capabilities).

3.1.1.2 UPLINK CHANNELS

When addressed on HS-SCCH, the UE will then send feedback frame(s) on HS-DPCCH (SF = 256), roughly 7.5 slots after HS-PDSCH frame, containing (see the following figure):

The HARQ Ack/Nack; The CQI (Channel Quality Indication).


Page 13/40



CQI

Subframe #0 Subframe #i Subframe #4

1 radio frame = 10ms

Tslot = 2560 chips = 10 bits

ACK/NACK

2.Tslot = 5120 chips = 20 bits

Figure 13: HS-DPCCH structure

For dual cell calls, DC capable UE have to combine the ACK/NACK and CQI for the two carriers on to the above physical channel structure of HS-DPCCH, which is common between the two carriers. 3GPP came up with the following mapping for performing this combination:

Figure 14: HS-DPCCH ACK/NACK structure for dual cell/carrier calls


Page 14/40



Figure 15: HS-DPCCH CQI mapping for dual cell/carrier calls

The HARQ Ack is possibly repeated in consecutive HS-DPCCH subframes using the N_acknack_transmit parameter, as specified in [R04] 6A.1.1.

Parameter ackNackRepetitionFactor Object HsdpaUserService RAN Path RNC / RadioAccessService / HsdpaUserService Range & Unit [1..4] User Customer Class 3-a2

Granularity HsdpaUserService[0..14]

Value 1

Note: Because of 33621 HSPA Configuration at site Granularity feature, its now possible to have until 15 different instances. Different values can also be defined per FDDCell for the parameters under the HsdpaUserService (this is possible using HsdpaUserServiceId under HsdpaResource).

Restriction: ackNackRepetitionFactor and [xCEM][eCEM]

Only value no repetition (ackNackRepetitionFactor = 1) is allowed, since xCEM and eCEM support only this value.

The CQI is only sent in some specific subframes, as specified in [R04] 6A.1.1, depending on the following parameters:

The CQI feedback cycle: k, The repetition factor of CQI: N_cqi_transmit.


Page 15/40




Page 16/40

Parameter cqiRepetitionFactor Object HsdpaUserService RAN Path RNC / RadioAccessService / HsdpaUserService Range & Unit [1..4] User Customer Class 3-a2


Value 1

Parameter cqiFeedbackCycleK Object HsdpaUserService RAN Path RNC / RadioAccessService / HsdpaUserService Range & Unit Enum {0, 2, 4, 8, 10, 20, 40, 80, 160} ms User Customer Class 3-a2


Value 2

Restriction: cqiFeedbackCycleK and [xCEM][eCEM]

Since UA7.1.2, new CQI information transmission (cqiFeedbackCycleK) has been limited to maximum of 20msec apart, irrespective of whether DC feature PM81204 is enabled or not and the OAM available range.

Rule: cqiRepetitionFactor and cqiFeedbackCycleK

These parameters have to respect the following rule:

cqiRepetitionFactor cqiFeedbackCycleK / 2

Note that cqiFeedbackCycleK = 0 is not supported.

Please refer to Volume 3 for a description of the HS-DPCCH power management.

3.1.2 FAST LINK ADAPTATION

Every TTI, Adaptive Modulation and Coding (AMC) is updated according to the radio conditions experienced by the UE and his category (see 4.1). AMC (number of codes, code rate and modulation type) is chosen among 30 possibilities corresponding to one CQI in order to reach the maximum bit rate while guarantying a certain QoS (10% BLER for example). The capabilities of the UE in terms of modulation depend on their category:

- categories 11 and 12 support only QPSK,

- categories lower or equal to 10, 15, 16, 21 and 22 support QPSK and 16QAM (categories 15 and 16 support MIMO)

- categories 13, 14, 17, 18, 23 and 24 support QPSK, 16QAM and 64QAM (categories 17 and 18 support MIMO)



16QAM modulation achieves higher bit rate than QPSK and 64QAM modulation allows even higher bit rate than 16QAM. The following figures illustrate the gain (in terms of throughput or BLER) according to the modulation:

QPSK QPSK QPSK 16QAM 16QAM

-20 -15 -10 -5 0 50

100

200

300

400

500

600

700

800

Ior/Ioc (dB)

Thro

ughp

ut (k

bps)

AMC Illustration



-20 -15 -10 -5 0 50

100

200

300

400

500

600

700

800

Ior/Ioc (dB)

Thro

ughp

ut (k

bps)

AMC Illustration

Figure 16: Example of throughput or BLER versus radio conditions for different modulation

3.1.3 FAST RETRANSMISSION MECHANISM (HARQ)

The HARQ (Hybrid Automatic Repeat Query) is a retransmission mechanism which consists in:

Retransmitting by the NodeB the data blocks not received or received with errors by the UE;

Combining by the UE the transmission and the retransmissions in order to increase the probability to decode correctly the information.

3.1.3.1 NUMBER OF HARQ PROCESSES

There is an HARQ process assigned per transport block for all the transmissions. The number of processes per UE is limited and depends on its category. The number of processes per UE category is the one given in [R02]:

[xCEM][eCEM]

Ue Category 1 2 3 4 5 6 7 8 9 10 11 12

Number of HARQ Processes 2 3 3 4 6 6 6 6 6 6 3 6

Ue Category 13 14 15 16 17 18 19 20 21 22 23 24


Table 2: Number of processes per UE category for xCEM and eCEM


Page 17/40




Page 18/40

[UCU-III]

Ue Category 1 2 3 4 5 6 7 8 9 10 11 12


Ue Category 13 14 15 16 17 18

Number of HARQ Processes 6 6 6 6 6 6

Table 3: Number of processes per UE category for UCU-III

[iCEM]

Ue Category 1 2 3 4 5 6 7 8 9 10 11 12


Table 4: Number of processes per UE category for iCEM

Category 21 to 24 have 12 processes when configured with dual cell call (6 for each cell) else these also have 6 processes for single carrier HSDPA calls.

Once this number is reached, the UE should not be eligible by the scheduler for new transmissions unless one of them is reset (ACK reception, discard timer expiration, max number of retransmissions reached). If the maximum number of retransmission is reached or if discard timer (discardTimer or timerT1) expiration, then the MAC-hs PDU is discarded leading to a RLC retransmission.

The maximum number of allowed MAC-hs retransmissions is:

[xCEM][eCEM]

Parameter harqNbMaxRetransmissionsXcem Object HsdpaConf RAN Path BTSEquipment / BTSCell / HsdpaConf Range & Unit [131] decimal User Customer Class 3

Granularity BTSCell

Value 7

[UCU-III]

For UCU-III, the maximum number of retransmissions is set to 10.

[iCEM]:

Parameter harqNbMaxRetransmissions Object HsdpaConf RAN Path BTSEquipment / BTSCell / HsdpaConf Range & Unit [131] decimal User Customer Class 3

Granularity BTSCell

Value 7 [iCEM][xCEM][eCEM]:




Page 19/40

The two following parameters are common for iCEM, xCEM and eCEM (RNC parameters):

Parameter discardTimer Object HsdpaUserService RAN Path RNC / RadioAccessService / HsdpaUserService Range & Unit Enum [20; 40; 60; 80; 100; 120; 140; 160; 180 ; 200; 250; 300; 400; 500; 750;

1000; 1250; 1500; 1750; 2000; 2500; 3000; 3500; 4000; 4500; 5000; 7500] ms User Customer Class 3-a2


Value 500

This parameter defines the time to live for a MAC-hs SDU starting from the instant of its arrival into an HSDPA Priority Queue.The Node B shall use this information to discard out-of-date MAC-hs SDUs from the HSDPA Priority Queues.

Parameter timerT1 Object HsdpaUserService RAN Path RNC / RadioAccessService / HsdpaUserService Range & Unit Enum [10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 120, 140, 160, 200, 300, 400] ms User Customer Class 3-a2


Value 100 This parameter is used by the NodeB to stop the re-transmission of the corresponding MAC-hs PDU (but ignored by the iCEM).

[UCU-III]

For UCU-III, the discard timer is set to 2000 msec and timerT1 is at 200 msec.

3.1.3.2 RV PARAMETERS

The IR (Incremental Redundancy) and modulation parameters necessary for the channel coding and modulation steps are: the r, s and b values. The r and s parameters (Redundancy Version or RV parameters) are used in the second rate matching stage, while the b parameter is used in the constellation rearrangement step (see [R03] for details):

s is used to indicate whether the systematic bits (s=1) or the non-systematic bits (s=0) are prioritized in transmissions.

r (range 0 to rmax-1) changes the initialization Rate Matching parameter value in order to modify the puncturing or repetition pattern.

The b parameter can take 4 values (0 3) and determines which operations are produced on the 4 bits of each symbol in 16QAM. This parameter is not used in QPSK and constitutes the 16QAM constellation rotation for averaging LLR at the turbo decoder input.

These three parameters are indicated to the UE by the Xrv value sent on the HS-SCCH (see section 3.1.1.1). The coding tables of Xrv are given hereafter:




Page 20/40

Xrv (Value) s r b

0 1 0 0

1 0 0 0

2 1 1 1

3 0 1 1

4 1 0 1

5 1 0 2

6 1 0 3

7 1 1 0

Table 5: RV coding for 16QAM

Xrv (Value) s r

0 1 0

1 0 0

2 1 1

3 0 1

4 1 2

5 0 2

6 1 3

7 0 3

Table 6: RV coding for QPSK

The determination of the s, r and b parameters will be based on the Xrv update, but not necessarily in the increasing order. The update indeed follows a predefined order stored in a table (called hereafter Trv). The only requirement to fill this table is that Trv[0] = 0 for QPSK, or Trv[0] = 0, 4, 5 or 6 for 16QAM (s = 1 and r = 0 must be the nominal configuration).

The rules to compute the Xrv parameters then are (see the following figure):

For the first transmission, Xrv is initialized to Trv[0]. Upon reception of a NACK, Xrv is assigned the next value in the table (once

the last value of the table, Nmax, has been set, the next value should be the first one again).

In case of no reception of ACK/NACK (DTX indication), the parameters must not be updated so that the same information not received by the UE should



be sent again (this ensure no systematic bits are lost, because all blocks may not be self-decodable).

New transmission ? Xrv = Trv[0]k = 0Y

N

DTX indication ? Xrv(n) = Xrv(n-1)Y

N

k = k + 1Xrv(n) = Trv[k mod Nmax]

Nmax = 1 (CC)= 4 (PIR - QPSK)= 6 (PIR 16QAM)= 8 (MIR)

Figure 17: RV parameters assignment algorithm

An update table is defined per HARQ type as described in section 3.1.3.4.

3.1.3.3 STATE OF HARQ PROCESSES

The following figure describes the different states of HARQ processes and possible actions related to these.


Page 21/40



ACK/NACK/DTX ?

HARQ process assignedby the scheduler

Y

Update of RV parametersData transmission

Wait for ACK/NACK reception

Insertion of DTX indication

Reset HARQ processRemove Mac-d PDUUpdate structures

Nret = Nret +1

Nret > Nret_max ?

Wait for retransmission

NACK

DTX

N

WACK state

NACK/DTX state

ACK

Figure 18: ACK/NACK/DTX management for HARQ processes

Once a UE is scheduled, an HARQ process is assigned that may correspond to either a new Transport Block or a retransmission. The RV parameters are computed accordingly as described before (see 3.1.3.2 RV Parameters section) and data is transmitted. The HARQ process is then waiting for feedback information (ACK/NACK/DTX) and is set in the so-called WACK state (Waiting for Ack/Nack/DTX). The exact timing for reception of the feedback information must be computed thanks to the chip offset and relatively to the TTI corresponding to the transmission.

Upon reception of the feedback information, three behaviors occur:

In case of an ACK, the HARQ process is reset and corresponding MAC-d PDUs are removed from memory. This HARQ process can now be used for a new transmission.

In case of a NACK, the number of retransmissions must be incremented. If the maximum number of retransmissions is not reached, the HARQ process is set in the so-called NACK state and then inserted in the NACK list of HARQ processes.

In case of a DTX indication, the same actions as for a NACK reception are done, except that a parameter must be updated to notify DTX detection (this


Page 22/40




Page 23/40

changes the RV parameter update compared to Nack reception, that is to say that the RV parameter update is not the same as for Nack, so no update, see 3.1.3.2 RV Parameters section). The process is then set in the DTX state.

The processes in the NACK or DTX state are just waiting for being re-scheduled for a new retransmission.

3.1.3.4 CHOICE OF THE HARQ TYPE

[xCEM][eCEM]

The HARQ type selection is done through the parameter harqTypeXcem:

Parameter harqTypeXcem Object HsdpaConf RAN Path BTSEquipment / BTSCell / HsdpaConf Range & Unit [ccType, irType] User Customer Class 3

Granularity BTSCell

Value irType

The following tables give according to [R03] the redundancy version and constellation depending on the modulation:

i 1 2 3 4

Xrv(QPSK) 0 2 5 6

Xrv(16QAM) 6 2 1 5

Xrv(64QAM) 6 2 1 5

Table 7: RV update table in the IR case (Trv[i])

[xCEM] [eCEM]:

i 1 2 3 4

Xrv(QPSK) 0 0 0 0

Xrv(16QAM) 0 4 5 6

Xrv(64QAM) 0 4 5 6

Table 8: RV update table in the CC case (Trv[i])

[iCEM]

A configurable parameter (CC/PIR/MIR) indicates the possibility of switching between Chase Combining, a Partial IR or a mix between Partial and Full IR sequence. It implies that 3 different tables must be stored (see below), chosen accordingly:




Page 24/40

The Chase Combining option corresponds to the first redundancy version always applied for all (re)transmissions.

The PIR indicates that for all redundancy versions, the systematic bits must be transmitted (blocks are self-decodable). Only the RV with s = 1 must be taken into account.

The MIR corresponds to a sequence where both systematic and non-systematic bits can be punctured. All possible redundancy versions are assumed and it corresponds to default version.

Each HARQ type is characterized by its update table Trv (see tables below):

i 1 2 3 4 5 6 7 8

Xrv(QPSK) 0 2 5 6 1 3 4 7

Xrv(16QAM) 6 2 1 5 0 3 4 7

Table 9: RV update table in the MIR case (Trv[i])

i 1 2 3 4 5 6

Xrv(QPSK) 0 2 4 6

Xrv(16QAM) 6 2 5 0 4 7

Table 10: RV update table in the PIR case (Trv[i])

The choice of the HARQ type (CC, MIR or PIR) is defined for all the retransmissions by setting the parameter harqType (= 1 for MIR, = 2 for PIR and = 3 for CC). When the HARQ type is selected, specific RV tables are used, one for QPSK and another one for 16QAM (as explained in the previous paragraphs).

With the feature HSDPA Performance Enhancement Optimal Redundancy Version for HARQ retransmission (29819), a fourth HARQ type can be selected: the Dynamic Redundancy noted DR (harqType = 4). This value is introduced to indicate that dynamic RV selection must be performed.

The aim of this sub-feature is to optimize the redundancy version (RV) of the retransmissions by dynamically selecting the most efficient HARQ type (and his corresponding RV table presented below) according to several parameters: UE category, number of HARQ processes and applied AMC for first transmission.

The different HARQ types (each one being associated to a restricted redundancy version set) that can be selected are:

Chase Combining (CC): same redundancy version than first transmission is applied (QPSK only).

RV = 0.

CC + Constellation rearrangement (CC+CoRe): same puncturing pattern is applied but constellation rotation is performed (16QAM only).



RV [0; 4; 5; 6]. Partial Incremental Redundancy (PIR): systematic bits are prioritized. RV [0; 2; 4; 6] in QPSK and [0; 2; 4; 5; 6; 7] in 16QAM. Full Incremental Redundancy (FIR): parity bits are prioritized. RV [1; 3; 5; 7] in QPSK and [1; 3] in 16QAM.

Table 11: RV updates tables when harqType set to Dynamic Redundancy

The principle is that incremental redundancy is only selected when required, i.e. as soon as punctured bits by the 2nd Rate Matching stage AND total number of softbits per HARQ process the UE can handle are higher than the number of transmitted bits. Otherwise, chase combining is sufficient. In case of IR, it is only necessary to puncture systematic bits (FIR) in case it is not possible to transmit all parity bits punctured by the 2nd RM stage in the first retransmission.

More in detail, during the Rate Matching step, following variables are computed:

NDATA: total number of radio bits, i.e. the number of HS-PDSCH codes times the modulation order (2 or 4) times 960 bits.

NIR: total number of softbits per HARQ process the UE can handle. It only depends on the UE category and the number of allocated HARQ processes.

NSYS: number of systematic bits (not equal to transport block size). NP1 and NP2: number of parity bits 1 and 2 after 1st RM step. NRM1 = NSYS + NP1 + NP2 NPUNC2 = NRM1 - NDATA: number of bits punctured by 2nd RM stage.

These values are then used to select the right HARQ type as explained by the following figure:


Page 25/40



Figure 19: Dynamic selection of HARQ type

Note: As the RV of the 1st transmission is identical whatever the HARQ type is, previous variables should then be stored during the rate matching of the first transmission. The HARQ Type only needs to be determined when 1st retransmission occurs.

Parameters Settings:

See [Vol. 3].

3.1.4 FAST SCHEDULING

The aim of the MAC-hs scheduler is to optimize the radio resources occupancy between users. Every TTI, it must then select Queue IDs for which data is going to be transmitted and the amount of corresponding MAC-d PDUs to transmit.

[xCEM][eCEM]

The aim of the scheduler is to share the resources between the different HSDPA users. xCEM and eCEM schedulers work in the following steps:

- To select a limited number of users from those which are ready for transmission in the current TTI (the number of users per TTI being


Page 26/40




Page 27/40

limited by the number of HS-SCCH configured and by the available resources mainly in terms of codes and power).

- To select of a Transport Format resource Combination (TFRC = {MAC-hs PDU size; number of HS-PDSCH codes; modulation alphabet}) of each user.

- To allocate power for the HS-SCCH and HS-DSCH of each user.

- To rank the users according to certain pre-defined scheduling metric, which may or may not take the chosen TFRC into account.

With xCEM and eCEM, the TFRC selection is based on the Spectral Efficiency (SE). The SE for a given SINR states the maximal number of bits before channel enco

Date post:	03-Oct-2015
Category:	Documents
Upload:	alselawi-ahmad
View:	9 times
Download:	6 times

HPUG UA08 V05.04 Preliminary Ext

Documents