PDF Fad Hsupa in Bts

Nokia Siemens Networks WCDMA RAN, Rel. RU20, Operating Documentation, Issue 02

WCDMA RAN HSUPA in BTS

DN70223925

Issue 03BApproval Date 2010-02-26

2 DN70223925Issue 03B


Id:0900d805807389f9

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN70223925Issue 03B

3


Id:0900d805807389f9

Table of ContentsThis document has 36 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1 HSUPA in WBTS6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.1 E-DCH Dedicated Physical Channel (E-DPCH) . . . . . . . . . . . . . . . . . . . 91.2.2 Relative Grant Channel (E-RGCH) and Hybrid ARQ Indicator Channel (E-

HICH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2.3 E-DCH Absolute Grant Channel (E-AGCH). . . . . . . . . . . . . . . . . . . . . . 111.2.4 Physical channel processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 HARQ Functionality for HSUPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4 MAC-e De-multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.5 Frame Protocol for the Interface between RNC and BTS (Iub) E-DCH data

stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.6 WCDMA BTS Packet Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.6.1 Packet Scheduling algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.7 HSUPA Digital Signal Processor (DSP) Resource Management . . . . . 171.7.1 Commissioned Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.7.2 Dynamically allocated resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.7.3 E-DCH Resource sharing between different E-DCH users . . . . . . . . . . 201.8 HARQ Process ID selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.9 HSUPA capability reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.10 Packet Scheduler configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.10.1 Cell-specific information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.10.2 UE specific information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.11 MAC-d flow configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.11.1 Multi NRT RABs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.12 Other transport channels with HSUPA user. . . . . . . . . . . . . . . . . . . . . . 241.13 HSUPA mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.14 Power control for the HSUPA channels . . . . . . . . . . . . . . . . . . . . . . . . . 251.15 HSUPA Congestion Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.16 Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2 Features per release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3 Management data for HSUPA in BTS . . . . . . . . . . . . . . . . . . . . . . . . . . 283.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 DN70223925Issue 03B


Id:0900d805807389f9

List of FiguresFigure 1 HSUPA entities in the WBTS6.0 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Figure 2 The physical channels and the E-DCH transport channel . . . . . . . . . . . . 9Figure 3 MAC-e PDU structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 4 Packet Scheduler environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 Resource types related to the HSUPA . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 6 The overview of the resource management concept in WBTS6.0 . . . . . 18Figure 7 DSP resource pool sharing between the E-DCH and the DCH . . . . . . . 19Figure 8 Dynamic resource allocation for the E-DCH . . . . . . . . . . . . . . . . . . . . . . 20

DN70223925Issue 03B

5


Id:0900d805807389f9

List of TablesTable 1 HSUPA basic characteristics in WBTS6.0 BTS . . . . . . . . . . . . . . . . . . . 7Table 2 FDD E-DCH physical layer categories . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 3 Cell-specific parameters used by the Packet Scheduler . . . . . . . . . . . 22Table 4 UE specific parameters used by the Packet Scheduler . . . . . . . . . . . . 23Table 5 MAC-d flow related parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 6 Features per release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 8 RAN826 Basic HSUPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 9 RAN1262: QoS Aware HSPA Scheduling . . . . . . . . . . . . . . . . . . . . . . 29Table 10 RAN1101 Cell Throughput Measurements in BTS . . . . . . . . . . . . . . . . 32Table 11 RAN1644 Continuous Packet Connectivity . . . . . . . . . . . . . . . . . . . . . . 32Table 12 RAN981 HSUPA 5.8 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 13 RAN1470 HSUPA 2 ms TTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Table 14 Parameters for LCG associated with HSUPA . . . . . . . . . . . . . . . . . . . . 34Table 15 Parameters for Minimum number of HSUPA UE per BTS . . . . . . . . . . 35Table 16 Parameters for Minimum baseband decoding capability [Mbps] . . . . . 35Table 17 Parameters for Mapping HSPA Cell to HW . . . . . . . . . . . . . . . . . . . . . 35Table 18 Parameters for Scheduling Weight for SPI class [0-15] . . . . . . . . . . . . 35Table 19 Parameters for Happy Bit -ratio ping filter . . . . . . . . . . . . . . . . . . . . . . . 35Table 20 Parameters for Happy Bit -ratio UPH threshold . . . . . . . . . . . . . . . . . . 36

6 DN70223925Issue 03B


Id:0900d805807499ea

Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Please note that our issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation.

Changes between issues 03A and 03BInformation on RAN1683: CS voice over HSPA feature has been moved to RU20 On Top release.

Changes between issues 3-0 and 03AInformation on RAN1231: HSPA over Iur feature has been removed from Features per release chapter.

Information on number of E-DPDCHs has been updated to Physical channels subchap-ter.

Information on the additional E-DCH channel establishment has been updated in Dynamically allocated resource subchapter.

Changes between issues 2-2 and 3-0Document name changed to WCDMA RAN HSUPA in BTS.

Updates in chapters: HSUPA in WBTS6.0, Features per release and Management data for HSUPA in BTS.

Section HARQ Process ID selection in chapter HSUPA in WBTS6.0 added.

RU20 features in chapter Features per release added.

New alarms, counters and parameters in chapter Management data for HSUPA in BTS added.

Changes between issues 2-1 and 2-2Updated Congestion Control algorithm description in section HSUPA Congestion control.

DN70223925Issue 03B

7

WCDMA RAN HSUPA in BTS HSUPA in WBTS6.0

Id:0900d80580749a5e

1 HSUPA in WBTS6.0

1.1 DescriptionThe scope of this document is to describe the High Speed Uplink Packet Access (HSUPA) related functionalities in the WBTS6.0 release (RAN Release RU20).

The document applies to Nokia Siemens Networks BTS products in the WBTS6.0 release.

The main functional aspects and restrictions related to the HSUPA feature in the WBTS6.0 are described in table HSUPA basic characteristics in WBTS6.0 BTS.

HSUPA basic characteristics WBTS6.0

E-DCH TTI Capability 10ms and 2ms TTI

E-DCH SF Capability 2xSF2 with 10ms TTI, 2xSF2+2xSF4 with 2ms TTI

UE categories 1-7 with above restrictions

E-DCH Maximum Bitrate per user 2.0 Mbps with 10ms TTI, 5.8 Mbps with 2ms TTI

Number of E-RGCH/E-HICH codes per cell One to four depending on the number of users

Number of E-AGCH per cell One or two depending on the 2ms TTI usage

Packet Scheduler algorithm Hybrid power and throughput based

E-DCH HARQ Combining capability IR and Chase Combining Capable

Max. number of HSUPA cells per LCG 6

Max. number of HSUPA users per cell 72

Max. number of HSUPA users per LCG 80*

Max. number of MAC-d flows per HSUPA user

6

Maximum number of MAC-e PDU retrans-missions

3

MAC-d PDU size 336 bits;

144 (for SRB);

56, 112, 136, 152, 176, 200, 264 and 272 (CS voice) in RU20 On Top

Allowed Active Set Size (# of SHOs) for HSUPA user

3

Compressed Mode for HSUPA Not used

Supported E-TFCI Table (E-TFCI Table Index)

Indices 0 and 1 for 10ms TTI. Index 0 for 2ms TTI

Supported WCDMA BTS roles Serving WCDMA BTS and Non-Serving WCDMA BTS

Table 1 HSUPA basic characteristics in WBTS6.0 BTS

8 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

*Max 80 users per LCG are supported if one frequency is allocated per LCG. In the special case that two frequencies are allocated to LCG, maximum 160 users per LCG are supported but still 80 per frequency. In rest of the document it is assumed that one frequency layer is configured per LCG.

Figure HSUPA entities in the WBTS6.0 BTS illustrates the functions and related HSUPA entities in the WBTS6.0.

Figure 1 HSUPA entities in the WBTS6.0 BTS

This document describes in detail the HSUPA functions and entities that are illustrated in figure HSUPA entities in the WBTS6.0 BTS:

• Physical layer processing • Hybrid Automatic Repeat request (HARQ) functionality • MAC-e Packet Data Unit (PDU) De-multiplexing • Frame Protocol (FP) • Packet Scheduler (PS) • Resource Manager

1.2 Physical channelsPhysical channels related to Enhanced Dedicated Transport Channel (E-DCH) are the following:

• Dedicated channels: • Uplink direction:

The E-DCH Dedicated Physical Data Channel (E-DPDCH) and E-DCH Dedi-cated Physical Control Channel (E-DPCCH), which are called E-DCH Dedicated Physical Channel (E-DPCH).

• Downlink direction:The Dedicated E-DCH Relative Grant Channel (E-RGCH) and Hybrid ARQ Indi-cator Channel (E-HICH).

• Common channel: • Downlink direction the Common E-DCH Absolute Grant Channel (E-AGCH).

MAC-dflow/UE2/

Queue

MAC-d flow/UE1/Queue

lub

Radio

E-DPCHHARQ

De-Mux

FPAAL

2

AAL2

FPDe-Mux

HARQE-DPCH

E-RGCH/E-HICH

E-AGCHResource Manager

Packet Scheduler

UE1

UE2

DN70223925Issue 03B

9


Id:0900d80580749a5e

The E-DCH transport channel and the related physical channels from the UE point of view are presented in figure The physical channels and the E-DCH transport channel.

Figure 2 The physical channels and the E-DCH transport channel

The UE can have:

• 1-4 E-DPDCH • 1-3 E-RGCH • 1-3 E-HICH and one E-DPCCH • E-AGCH

When the WBTS6.0 acts as a Non-Serving WCDMA BTS according to the standards, E-AGCH is not used for that particular UE.

The physical channels are described in detail in the next chapters.

1.2.1 E-DCH Dedicated Physical Channel (E-DPCH)WBTS6.0 supports the E-DCH categories 1-7 from table FDD E-DCH physical layer cat-egories up to 2xSF2 with 10ms TTI and up to 2xSF2+2xSF4 with 2ms TTI with QPSK modulation.

Note that if UE does not have UL DPDCH configured (as is the case with F-DPCH) the 10ms TTI maximum physical channel is 2xSF4.

E-DCH category

Maximum number of E-DCH codes transmitted

Minimum spreading factor

Support for 10 and 2 ms TTI EDCH

Maximum number of bits of an E-DCH trans-port block transmit-ted within a 10 ms E-DCH TTI


Category 1 1 SF4 10 ms TTI only

7110 -

Category 2 2 SF4 10 ms and 2 ms TTI

14484 2798

Table 2 FDD E-DCH physical layer categories

10 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

UEs of Categories 1 to 6 support QPSK only. UEs of Category 7 supports QPSK and 16QAM (Not supported in WBTS6.0).

Softer and Soft handover are also supported for the E-DPCH, and the maximum number of radio links in a Radio Link Set (RLS) is three.

For more information on FDD E-DCH physical layer categories, see 3GPP TS 25.306: UE Radio Access Capabilities.

1.2.2 Relative Grant Channel (E-RGCH) and Hybrid ARQ Indicator Channel (E-HICH)The E-DCH Relative Grant Channel (E-RGCH) is a dedicated to downlink physical channel carrying relative grants for the uplink E-DPCH. The relative grant is a ternary value which has three alternatives in Serving Radio Link Set:

• UP • HOLD • DOWN

The E-DCH Hybrid ARQ Indication Channel (E-HICH) is also dedicated to the downlink physical channel, which carries Hybrid ARQ acknowledgement indicator, which has two alternatives:

• ACK (Acknowledgement) • NACK (Negative Acknowledgement)

In the WBTS6.0 BTS, there is at least one E-HICH and E-RGCH in every cell and they always share the same common channelization code (the number of code channels depends on the number of users and can be from one to four). The separation of the


14484 -


20000 5772


20000 -


20000 11484


20000 22996

NOTE: When 4 codes are transmitted in parallel, two codes shall be transmitted with SF2 and two with SF4.

E-DCH category

Maximum number of E-DCH codes transmitted

Minimum spreading factor

Support for 10 and 2 ms TTI EDCH



Table 2 FDD E-DCH physical layer categories (Cont.)

DN70223925Issue 03B

11


Id:0900d80580749a5e

UEs is done by the orthogonal signature sequence. The maximum number of different sequences is 40 per channelization code, and all of them are used in WBTS6.0.

In WBTS6.0, the signature sequences of an E-RGCH/E-HICH code channel are dynam-ically divided between the E-HICH and E-RGCH channels, resulting that E-HICH can have 1-39 sequences and E-RGCH 1-20 sequences. The E-RGCH sequences are allo-cated in a cell so that each configured E-RGCH/E-HICH code channel has one sequence always for all Non-Serving radio links, and maximum 19 exists for the Serving radio links. The E-HICH sequences are always allocated freely between the Serving and Non-Serving radio links.

When the WBTS6.0 BTS has the Serving E-DCH radio link set for a 10ms TTI UE, the relative grant and ACK/NACK indicator is transmitted to all the cells that belong to the E-DCH radio link set. For 2ms TTI UEs the ACK/NACK indicator is transmitted to all the cells that belong to the E-DCH radio link set. Relative grant is used only for non-serving 2ms TTI UEs.

When the WBTS6.0 BTS has the Non-Serving E-DCH radio link set for the UE, the ACK/NACK indicator is transmitted as above with the UE-specific sequence, but the relative grant is transmitted through the cell-specific sequence.

The signature sequences are always allocated from the code channel that is closest to the beginning of the code tree for optimum code channel usage. The signature sequences are also reconfigured for code tree defragmentation purposes.

1.2.3 E-DCH Absolute Grant Channel (E-AGCH)The E-DCH Absolute Grant Channel (E-AGCH) is a common downlink physical channel, carrying absolute grants for the uplink E-DPCH. The difference between the absolute and relative grant is that by using relative grant, the granted bitrate can be increased and decreased only incrementally by the Radio Network Controller (RNC) pre-configured steps. With absolute grant, the granted bitrate can be adjusted without predefined steps.

If 2ms TTI is configured for a cell then two E-AGCH channels are set up. One channel is dedicated for 10ms TTI users and other channel is dedicated for 2ms TTI users.

In practice, for 10ms TTI UEs the relative grant is always used when granted bitrate is adjusted within the predefined steps. The absolute grant channel is used when the granted bitrate is adjusted with bigger steps, and in the WBTS6.0, it is used when the bitrate is ramped up or down quickly.

For 2ms TTI users only absolute grant is used for scheduling serving UEs and relative grant is used for non-serving UEs.

1.2.4 Physical channel processing

Processing of E-DPCH The WBTS6.0 BTS receives the E-DPCCH and E-DPDCH from the cells that belong to the E-DCH Radio Link Set and the radio signals from all the cells that are first combined in a rake receiver.

The combined E-DPDCH signal goes trough the HARQ combining and channel decoding functionality, and as a result, the BTS receives:

• MAC-e PDU which is forwarded to De-Multiplexing functionality and • Optionally, the Scheduling info, if received, is sent to the Packet Scheduler.

12 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

The rake combined E-DPCCH signal goes through the channel decoding functionality and as a successful result the BTS receives and/or calculates the following information:

• Retransmission Sequence Number (RSN) is used in the BTS for calculating how many times one MAC-e PDU is transmitted. RSN is used for the Hybrid-ARQ func-tionality.

• E-TFCI, which is used in data channel multiplexing and channel coding, and is also used by Packet Scheduler (PS).

• Happy bit, which is used in the Packet Scheduler. • Connection Frame Number (CFN), calculated by the BTS and it is the time when the

data was received. The CFN is transmitted to the RNC in frame protocol. • Channel Quality estimate, calculated by the BTS, and it is used in the Packet Sched-

uler.

Coding for the E-AGCH The WCDMA BTS Packet Scheduler determines the timing when the absolute grants are sent to the UE. When that happens, the WCDMA BTS Packet Scheduler initiates the absolute grant command transmission, which contains the following information:

• E-RNTI • Absolute Grant Index, which is used in L1 to determine the Absolute Value Informa-

tion. • Absolute Grant Scope (for 10ms TTI users the scope used is always ’All HARQ pro-

cesses’ and for 2ms TTI users the scopes used are both 'All HARQ processes' and 'per HARQ process'.)

• Timing information when Absolute Grants are sent in the physical channel.

Mapping for the E-RGCH and E-HICH E-RGCH: The Packet Scheduler (PS) determines the relative grant value to the UE. When the relative grant value is to be transmitted, the L1 maps the Relative Grant value to the bits by multiplying it first with 40 bit signature sequence.

E-HICH: The HARQ Entity determines when the reception of MAC-e PDU was success-ful or unsuccessful, and every time the decoding attempt is made, the HARQ entity sends the ACK or NACK to the UE. The mapping of ACK/NACK value to the bits is done in a similar way to E-RGCH.

1.3 HARQ Functionality for HSUPAIncremental Redundancy (HARQ) Functionality is a key feature in the HSUPA, and in WBTS6.0, HARQ consists of the following principles:

• The HARQ entity has four or eight Stop-and-Wait (SAW) processes per UE (the number depends of the configured TTI).

• The HARQ is based on synchronous downlink ACK/NACK signalling. • The HARQ is based on synchronous retransmissions in the UL. • The number of re-transmissions is limited by the Serving Radio Network Controller

(SRNC). • The SRNC informs the BTS which combining method is used for each UE: Chase

combining or Incremental Redundancy. • HARQ supports the softer combining. • 10ms and 2ms Transmission Time Intervals (TTI) are supported.

DN70223925Issue 03B

13


Id:0900d80580749a5e

Once the HARQ Entity is configured for the UE, it starts the operation and follows the input from the E-DPCCH control channel and the data in the E-DPDCH is processed based on that information. No further control information from higher layer is needed.

After every decoding attempt, the HARQ entity sends ACK or NACK information in the E-HICH to inform the UE whether decoding was successful or not.

If the decoding was successful, the HARQ forwards decoded MAC-e PDU to de-multi-plexing.

If the decoding was unsuccessful, the HARQ waits for the re-transmission, or if the maximum number of re-transmissions has been reached, the HARQ sends HARQ Failure to the Frame Protocol which forwards that information to the RNC.

1.4 MAC-e De-multiplexingThe MAC-e De-multiplexing is part of the MAC-e protocol entity. The purpose is to de-multiplex the MAC-es PDU(s) and related MAC-e header information from the MAC-e PDU and map them to the corresponding MAC-d flow.

To enable the MAC-e de-multiplexing, the RNC provides a Data Description Indicator (DDI) mapping information:

• MAC-d flow ID, which informs to which MAC-d flow each MAC-es PDU has to be mapped and

• the size of the MAC-d PDU • Logical channel ID

By using the DDI provided by the RNC, and DDI and N from the header of the MAC-e PDU, de-multiplexing in the BTS separates each MAC-es PDU from the MAC-e PDU, and maps MAC-es PDU to the corresponding MAC-d flow.

If the Scheduling Information (SI) is included into the end of the MAC-e PDU, the BTS detects it by calculating the total length of the MAC-e PDU first. Then by using the infor-mation provided by the DDI and N parameters in MAC-e PDU, the BTS detects the leftover bits, which contain the SI and possible padding.

Standalone SI is also handled in the BTS. In that case UE the did not have any data to be transmitted, or BTS has not allocated the grants yet.

Both MAC-e PDU alternatives are presented in figureMAC-e PDU structures.

14 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

Figure 3 MAC-e PDU structures

When the BTS has done the de-multiplexing, the MAC-es PDUs, DDI and N are sent to the Frame Protocol.

Scheduling Info (SI), if received, is sent to the Packet Scheduler.

Note that the WBTS 6.0 supports six MAC-d flow per UE, and MAC-e PDU contains maximum 9 MAC-es PDUs.

Note that the MAC-d flow contains data to one RAB.

1.5 Frame Protocol for the Interface between RNC and BTS (Iub) E-DCH data streamWBTS6.0 uses the Frame Protocol (FP) for four purposes:

1. to transmit MAC-es PDUs to the RNC2. to transmit HARQ Failure Indication to the RNC3. to transmit congestions related control information to the RNC4. to deliver OUTER LOOP POWER CONTROL – control frame from RNC to BTS

In the first case, the FP receives the following information from the de-multiplexer, and FP includes them in the E-DCH UL Data Frame when sending the MAC-es PDUs to the RNC:

• the number of HARQ Retransmissions used for successful decoding of the payload • the number of MAC-es PDUs to be included into the UL E-DCH Data Frame • DDI and N • the MAC-es PDUs

In the second case, when HARQ Entity detects that the maximum number of retrans-missions is exceeded for the MAC-e PDU, the HARQ Entity transmits HARQ Failure Indication to the Frame Protocol entity which forwards that to the RNC.

In the third case, FP includes the Frame Sequence Number (FSN) and Connection Frame Number (CFN) in every E-DCH UL Data Frame. They are used by the RNC,

MAC-es

PDU2

MAC-es

PDU1

DDI0NnDDInN2DDI2N1DDI1

MAC-es

PDUn

SIPadding

(Opt)

N1DDI1

MAC-es

PDU1

MAC-es

PDU2

N2DDI2 NnDDIn

MAC-es

PDUn

MAC-e PDU

SI

MAC-e PDU

(a) MAC-e PDU structure (including SI)

(b) MAC-e PDU structure (standalone SI)

DN70223925Issue 03B

15


Id:0900d80580749a5e

which sends TNL Congestion Indication when detects that the Iub interface becomes congested, or the congestion is over. For more information about HSUPA Congestion Control, see Section HSUPA Congestion Control.

In fourth case, the OUTER LOOP POWER CONTROL – control frame for closed loop power control algorithm is delivered through E-DCH FP if the user does not have DCH FP configured. This is the case with F-DPCH when DCH transport channels are not used at all.

The WBTS6.0 supports six MAC-d flows per UE so it means that the UE can have maximum of six MAC-d flows in the Iub Interface. Each MAC-d flow is carried with own transport bearer to RNC, therefore UE have maximum of six Frame protocol entities in the BTS.

1.6 WCDMA BTS Packet SchedulerThe WBTS6.0 supports the WCDMA BTS Controlled Scheduling. WBTS 6.0 has one WCDMA BTS Packet Scheduler if the BTS has one Local Cell Group (LCG). If two or more LCGs are configured in the BTS, the BTS has independent WCDMA BTS Packet Schedulers for each LCG.

In special case that two frequency layers are configured into LCG, then LCG contains two independent packet schedulers, that is, one for each frequency layer.

In the rest of the section, it is assumed that the BTS has one LCG. For more information on LCG, see Section HSUPA DSP Resource Management.

WCDMA BTS Packet Scheduler optimises the E-DCH base band processing resources and radio usage in all the cells in the BTS. The optimization is done during the schedul-ing cycle, which is affected by the:

• RNC parameters, which set the bases and limits for the E-DCH operation • available E-DCH Radio resources • scheduling requests from the UE • bitrate the UE is using • available Iub Transport Network resources

Packet Scheduler also considers the occasions when the UE does not listen to Serving Grant commands because of Continuous Packet Connectivity subfeature Discontinuous DL Reception.

The output of the scheduling is the Serving Grant, which is transmitted for the UEs, and then the next scheduling period and cycle starts. Scheduling is therefore a continuous process.

WBTS6.0 Packet Scheduling also takes into account the UEs for which BTS is a Non-serving WCDMA BTS.

The Packet Scheduler environment is shown in detail in figure Packet Scheduler envi-ronment.

16 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

Figure 4 Packet Scheduler environment

The Packet Scheduler algorithm, the RNC parameters, the Frame Protocol Congestion Indication and the Resource Management are presented in detail in the following sec-tions.

1.6.1 Packet Scheduling algorithmThe Packet Scheduling algorithm is Hybrid power and throughput-based.

Hybrid means that the algorithm is power-based in normal operation. The algorithm changes to throughput-based when the interference in radio interface changes sud-denly. The throughput-based algorithm guarantees that the UEs have a controlled bitrate, even the cell interference is over the Maximum Target Received Total Wideband Power For more information see(3GPP TS 25.433 UTRAN Iub interface NBAP).

The algorithm utilises Quality of Service parameters, trying to fulfil the Quality of Service requirements. Users without the Quality of Service parameters are treated with the best effort manner. The best effort algorithm is also fair as the allocated bit rate is balanced between the UEs (but not guaranteed to be equally shared).

The Packet Scheduling algorithm is optimized to cope with the following specific situa-tions:

- Low utilization UEs When the UE is uses lower bitrate than the allocated bitrate, the allocated bitrate is reduced.

- The UE using too high allocation The UE has detected grant falsely and the UE bitrate is reduced.

- Fast ramp-up When the UE amount in the cell is low, the bitrate is increased faster compared to situations when the UE amount in the cell is high.

Both 10ms TTI and 2ms TTI users are handled equally in Packet Scheduler.

Quality of Service Scheduling

HARQ

FPE-RGCH/E-HICH

E-AGCH

Resource Manager

L1measurement

E-TFCI, Happy bit,SI, Channel quality estimate

Received totalwideband power

CongestionIndication

RNCparameters

RelativeGrant

AbsolutGrant

Packet Scheduler

RNC

HW request

DN70223925Issue 03B

17


Id:0900d80580749a5e

- Non Real time data schedulingNon Real time classes, interactive and background are implemented with Scheduled transmission. Following Node-B Application Part (NBAP) Quality of Service (QoS) parameters are utilised for scheduled transmission:

• MAC-es Guaranteed Bit Rate (GBR) • Scheduling Priority Indicator (SPI) • E-DCH HARQ Power Offset FDD (HARQ PO)

In addition to NBAP parameters, SPI specific weight parameters are defined in commis-sioning. For more information, see Section Commissioning parameters.

Packet Scheduler utilizes GBR and SPI parameters. As the GBR parameter is used for NRT data, it is not really guaranteed, but it is considered as Nominal Bitrate (NBR).

Packet Scheduler allocates NBR to users in SPI order. If NBR cannot be fulfilled for some user because of high cell interference, then PS reduces the allocation from lower SPI user to free resources.

If Packet Scheduler is able to allocate NBR for each user, then PS uses weight param-eters to share excess capacity in the best effort manner.

PS calculates weighted bitrate for each user by scaling the current bitrate and allocating more bitrates to one having smallest bitrate.

PS selects the correct weight parameter based on user SPI and the scaling is done according to following algorithm:

Scaled bitrate = (current bitrate –NBR) / weight

HARQ power offset is not used in scheduling as such. The UE applies it to transmission in order to increase transmission power and decrease number of retransmissions for defined logical channel (lower BLER).

Best effort users (users without QoS parameters) are treated as QoS users with lowest priority and no NBR.

- Real Time data schedulingReal time classes, streaming and conversational, are implemented with Non-Scheduled transmission. For the scheduling, BTS cannot do anything, its under control of the RNC. The UE is allowed to send Non-Scheduled Transmission (NST) at any time.

1.7 HSUPA Digital Signal Processor (DSP) Resource Manage-ment The resource management has two levels in the BTS:

• BTS Resource Manager (BTS RM) • E-DCH Resource Manager (E-DCH RM)

The top level is the BTS RM, which controls all the resources in the BTS, including the DSP resource pool and resource sharing between the DCH and E-DCH. The mecha-nism how resource sharing is achieved is described in Section Dynamically allocated resource.

Regarding HSUPA, WBTS6.0 has the following types of resources, which are also described in detail in the following sections:

• Section Commissioned resource

18 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

• Section Dynamically allocated resource

There is no minimum resource allocation if no commissioned DSP resources are allo-cated.

Figure 5 Resource types related to the HSUPA

1.7.1 Commissioned ResourceThe resources that are commissioned are reserved from each of the Local Cell Group (LCG) separately. In figure The overview of the resource management concept in WBTS6.0, an example of BTS with two LCGs is presented.

Figure 6 The overview of the resource management concept in WBTS6.0

Each LCG consists of the following figures:

• Commissioned resource for E-DCH (which can be different in each LCG) • Maximum six cells • N number of clusters • Maximum 28 Mbps for HSUPA shared between all E-DCH users • Maximum 80 E-DCH users • E-DCH Resource Manager

When the commissioned resource is to be reserved, the LCG has to be selected first with the LCG associated with HSUPA parameter.

Once the LCG is selected, the commissioned resource allocation is configured by using the following parameters:

• Minimum baseband decoding capability [Mbps] • Minimum number of HSUPA UE per BTS*

Commissioned Resource

Dynamic Resource (resource pool which is sharedbetween DCH and E-DCH)

Resourc

es

Cluster1

Local Cell Group1 (LCG1)

Cluster N*

Commissionedresource for

E-DCH

BTSRM

DSP ResourcePool. Resources

are shared betweenE-DCH and DCH

*Note, that the exact number of clusters in WBTS6.0 can be foundfrom Dimensioning WCDMA RAN, Functional area Description

E-DCHRM

Cluster1

Local Cell Group2 (LCG2)

Cluster N*

E-DCHRM

DN70223925Issue 03B

19


Id:0900d80580749a5e

(*The parameter name is ‘per BTS’. This is the case when one LCG is installed in the BTS. When two or more LCGs are installed, the Minimum number of HSUPA UE is con-figured per LCG.)

The commissioned resource is reserved in the LCG immediately after the configuration.

HSUPA commissioned resource in the Ultrasite WCDMA BTS:In the Ultrasite WCDMA BTS (Ultrasite), one cluster is one WCDMA Signal Processor version C (WSPC) unit.

For more information on the relationship between the two commissioning parameters and the combined minimum baseband L1 throughput of all users see Chapters HSUPA and BTS dimensioning and Dimensioning UltraSite WCDMA BTS Section in Dimension-ing WCDMA RAN.

HSUPA commissioned resource in the Flexi WCDMA BTS:In the Flexi WCDMA BTS (FlexiBTS), one cluster is one Flexi submodule.

With Release 1 module the cluster includes three resource steps and with Release 2 module the cluster includes two resource steps. Resource steps are described in Chapter HSUPA CE allocation principles in Dimensioning WCDMA RAN.

For more information on the relationship between the two commissioning parameters and the combined minimum baseband L1 throughput of all users see Chapters HSUPA and BTS dimensioning and Dimensioning Flexi WCDMA BTS in Dimensioning WCDMA RAN.

1.7.2 Dynamically allocated resource The WBTS6.0 target for the DSP Resource Management is that all free resources are utilized to maximize the E-DCH throughput. This is achieved by the principle that the DCH and E-DCH resources share the same DSP resource pool. How this resource pool is divided is explained more in detail later in this chapter. The main principle is that the DCH has a higher priority than Non Real Time E-DCH and when the resources are left from the DCH, resources are given to the E-DCH. Priority is not so clear between DCH and Real Time E-DCH. This is explained in detail in later chapters. The result is that the resource pool usage remains high, and the uplink cell throughput is maximised.

Figure 7 DSP resource pool sharing between the E-DCH and the DCH

The BTS RM controls how the resources are allocated for the E-DCH RM. Figure Dynamic resource allocation for the E-DCH shows the principle of the dynamic resource allocation for E-DCH.

BTS RM controls all the resources that are not commissioned to the E-DCH. The E-DCH RM controls the resources that are statically commissioned, and the BTS RM has

DS

Pre

so

urc

ep

oo

lu

sa

ge

DCH

E-DCH

Time

20 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

dynamically allocated for the E-DCH. For more information on commissioned resource, see figure Dynamic resource allocation for the E-DCH. In figure Dynamic resource allo-cation for the E-DCH, commissioned resource is not shown.

Figure 8 Dynamic resource allocation for the E-DCH

The PS knows whether the UEs are happy or unhappy, and based on that information, the PS informs the E-DCH RM whether more E-DCH resources are needed, or whether the E-DCH resources can be released. The information transfer between Packet Sched-uler and E-DCH Resource Manager (RM) can be done every scheduling period, if there is a need, and information transfer is per UE.

The E-DCH RM requests additional resources from the BTS RM. The requests are trig-gered based on the resource need (requests received from the Packet Scheduler) and the amount of currently allocated resources. When the E-DCH RM has resources, it controls how these resources are allocated to different E-DCH users.

The BTS RM requests resources back from the E-DCH RM when additional DCH channels are created. This reduces the resources for the E-DCH channels and the E-DCH bitrate is reduced accordingly. The existing E-DCH channels always remain in the BTS and the minimum bitrate can be reduced down to 32kbps (with the exception of Real Time E-DCH which is not affected). When all the E-DCH channels have 32kbps (with the exception of Real Time E-DCH which is not reduced), the bitrate is not reduced further. If the DCH channels uses the remaining resource at that moment, additional DCH channels cannot be established.

Also, the additional E-DCH channel establishment cannot be done if all the existing E-DCH channels have the minimum resource reservation (for Non Real Time E-DCH channels it is 32 kbps and for Real Time E-DCH channels it depends on RNC parame-ters), and the remaining resource is reserved for the DCH channels.

1.7.3 E-DCH Resource sharing between different E-DCH usersWhen BTS RM has granted the resources for the E-DCH RM, the E-DCH RM shares that resource between all the E-DCH users. The sharing is done by giving the Real Time users the resources needed given by the QoS parameters. The remaining resources are shared by the Non Real Time users based on PS request.

For the Non Real Time classes the BTS guarantees only minimum HW reservation (32kbps).

For Real Time classes the BTS makes the HW allocation for Maximum Set of E-DPDCHs to guarantee the sufficient Real Time resources for the user.

E-DCH ResourceRequest

BTSRM

Packet Scheduler

E-DCH RM requestsresources

from BTS RM

E-DCH RM controls the E-DCH resourcesand shares that with all E-DCH users

E-DCHRM

Current dynamicE-DCH Resource

Current DCHResource

DN70223925Issue 03B

21


Id:0900d80580749a5e

E-DCH RM balances the load between clusters in the E-DCH resource pool. E-DCH RM monitors the load in clusters and E-DCH RM can reorganize the resources between the clusters to optimize the resource utilization. This way the resource utilization remains high even if the resource situation changes (resource pool size increases or decreases or user bitrates increase or decrease).

Both 10ms TTI and 2ms TTI users are handled equally in E-DCH RM.

1.8 HARQ Process ID selectionWith 2ms TTI it is possible that only some of eight HARQ processes are transmitting data. The HARQ processes for Scheduled Transmissions are controlled by Absolute Grant commands. The HARQ processes for Non-Scheduled Transmissions are selected during RL setup and RL reconfiguration procedures.

The serving BTS selects the HARQ processes so that the transmission of different users would be spread over time in the air interface. If the HARQ process allocation of NST is no longer optimal (for example because of user transfers or setups) Serving BTS sends Radio Link Parameter Update request to RNC to trigger RL reconfiguration. During the RL reconfiguration serving BTS re-selects the NST HARQ processes for optimal loca-tion.

1.9 HSUPA capability reportingThe RNC uses 3GPP NBAP procedure, NBAP: AUDIT REQUEST message to perform an audit of the configuration and status of the logical resources in the BTS. The BTS responses by the NBAP: AUDIT RESPONSE message, which contains in the cell object level the following information:

• whether the E-DCH is supported in the BTS • the E-DCH is supported in the same cells where the DCH is supported • If BTS contains FSMC/D/E or EUBB baseband HW units (and HSUPA is not forced

to WSPC/FSMB HW by commissioning parameters) then BTS supports minimum spreading factor of 2xSF2+2xSF4. Otherwise the BTS supports minimum spreading factor 2xSF2.

• If BTS contains FSMC/D/E or EUBB baseband HW units (and HSUPA is not forced to WSPC/FSMB HW by commissioning parameters) then BTS supports both 2ms TTI and 10ms TTI. Otherwise the BTS supports 10ms TTI.

• the BTS supports chase and Incremental Redundancy (IR) combining

1.10 Packet Scheduler configurationThis section presents the most important parameters transmitted from the RNC to the Packet Scheduler in the BTS.

1.10.1 Cell-specific informationThe Packet Scheduler is established for the BTS, when the RNC configures the first E-DCH related physical channels.

Physical channels are established with a cell-specific NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message. Therefore one message estab-lishes the code channels for the E-AGCH and E-RGCH/E-HICH, and gives the power

22 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

configuration for the cell. The parameters, which are configured by the RNC, are pre-sented in table Cell-specific parameters used by the Packet Scheduler.

1.10.2 UE specific informationThe E-DCH is set up for a user with the NBAP: Radio Link Setup or Radio Link Prepa-ration/Commit procedures. The Radio Link Setup is used when the RNC executes the Inter-Node B E-DCH Serving cell change or the RNC establishes the first radio link for the UE. The Radio Link Preparation/Commit procedures are used when the E-DCH is setup and the user already have an existing Radio Link in the BTS.

The deletion of the E-DCH is done by the Radio Link Preparation/Commit procedures or when the last radio link is deleted from the user by using the Radio Link Deletion proce-dure.

The Packet Scheduler takes into account the parameters transmitted from the RNC, as described in table UE specific parameters used by the Packet Scheduler.

Parameter Description

Maximum Target Received Total Wideband Power

The Maximum Target Received Total Wideband Power parameter indicates the maximum target UL interference for a certain cell under the Controlling RNC (CRNC), including the received wideband power from all sources. Mapping according to 3GPP TS 25.133 Requirements for support of radio resource management (FDD).

Reference Received Total Wideband Power

The Reference Received Total Wideband Power parameter indicates the reference UL interference (received noise level) for a certain cell under the CRNC. This value is used for E-DCH scheduling in WCDMA BTS.

The Value mapping is according to mapping for measurement type ’Received Total Wideband Power‘ in 3GPP TS 25.133.

Target Non-serving E-DCH to Total E-DCH Power Ratio

The Target Non-serving E-DCH to Total E-DCH Power Ratio parameter indicates the target ratio of the received E-DCH power from non-serving UEs to the received total E-DCH power.

E-AGCH and E-RGCH/HICH Codes Channelization codes. Up to four E-RGCH/HICH codes and two E-AGCH codes can be set up.

Table 3 Cell-specific parameters used by the Packet Scheduler

DN70223925Issue 03B

23


Id:0900d80580749a5e

* Reconfigurable means that the RNC can modify the parameter by using NBAP proce-dures to see how the RNC triggers the modification. For more information, see the RNC Radio Resource Management documentation.

Parameter Description Reconfigurable*

Maximum Set of the E-DPDCHs

It indicates the maximum number of physical channels and spreading factor for which the BTS is allowed to schedule. The WBTS6.0 supports up to V2xN2+2xN4 (with FSMC/D/E or EUBB HW that is 2ms TTI capable, with FSMB/WSPC HW 10ms TTI only and V2xN2).

Yes

E-DCH Minimum Set E-TFCI

A minimum set of E-TFCs, which is the largest E-TFC that can be used by the UE, independent of the UE power situation, given that a valid (absolute) grant is available and there is no transmission on DCH.

Yes

E-TFCI Table Index The WBTS6.0 supports tables 0 and 1 with 10ms TTI and table 0 for 2ms TTI (with FSMC/D/E or EUBB HW that is 2ms TTI capable)

No

HARQ Info for E-DCH The E-DCH HARQ Info is used to indicate the use of Redundancy Version (RV) for the EDCH HARQ transmissions.

Yes

E-DPCCH power offset It indicates the E-DPCCH power offset and is used for E-DCH load calculation.

Yes

Power offset for reference E-TFCI and Reference E-TFCI

The Reference E-TFCI Power Offset calculates the reference E-TFC gain factor.

Yes

E-DCH grant type Indicates E-DCH grant type, Non Scheduled Transmission and Sched-uled Transmission Grant is sup-ported in WBTS6.0

No

Serving E-DCH RL The Serving E-DCH RL where WCDMA BTS can transmit absolute grants.

Yes

E-RGCH 2-Index-Step Threshold

The E-RGCH 2-Index-Step-Thresh-old Information Element (IE) is a threshold value. Below the threshold, a UE increases its transmission power in two steps receiving the relative grant ’UP‘ command. It deter-mines the Serving Grant.

Yes

E-RGCH 3-Index-Step Threshold

The E-RGCH 3-Index-Step-Thresh-old IE determines the Serving Grant.

Yes

Table 4 UE specific parameters used by the Packet Scheduler

24 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

1.11 MAC-d flow configurationMAC-d flow is added and deleted for the user by using the NBAP: Radio Link Setup or Radio Link Preparation/Commit procedures.

The MAC-d flow related parameters are presented in table MAC-d flow related param-eters.

* Reconfigurable means that the RNC can modify the parameter by using NBAP proce-dures. For more information, see the RNC Radio Resource Management documenta-tion.

1.11.1 Multi NRT RABsBTS supports up to three Non Real time Radio Bearers simultaneously. Each RAB is carried through own MAC-d flows and they can have different QoS parameters. Together with CS voice and streaming service features and SRB on HSUPA, this means maximum of six MAC-d flows (in RU20 On Top) simultaneously.

1.12 Other transport channels with HSUPA userWhen the HSUPA (E-DCH) is configured for the user in UL, the HSDPA (HS-DSCH) is always in the DL. The E-DCH channel can also be changed to DCH channel and the other way round. The triggers for the channel switch are in the RNC.

The DCH is mainly used for the Signalling Radio Bearers (SRB) to enable the smooth mobility between the HSUPA capable BTS and the non-HSUPA capable BTSs.

Parameter Description Reconfigurable*

Maximum Number Of Retransmissions for E-DCH

The Maximum Number Of Retransmissions For E-DCH IE specifies the upper boundary for retransmis-sions for a single MAC-e PDU.

No

MAC-es Guaranteed Bit Rate (GBR)

Allocated Bit Rate for the user. As the GBR parame-ter is used for NRT data, it is not really guaranteed, but it is considered as Nominal Bitrate (NBR)

Yes

Scheduling Priority Indica-tor (SPI)

User scheduling prioritisa-tion

Yes

E-DCH HARQ Power Offset FDD (HARQ PO)

Transmission power is increased to achieve smaller Block Error Ratio (BLER)

No

Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission

Guaranteed bit rate for the MAC-d flow

No

Table 5 MAC-d flow related parameters

DN70223925Issue 03B

25


Id:0900d80580749a5e

If user is configured to 2ms TTI then SRB is mapped to E-DCH transport channel to allow high bitrates (2xSF2+2xSF4 physical data channel does not leave code channels for DPDCH).

If UE and cells support Fractional DPCH (F-DPCH) SRB is mapped to E-DCH transport channel to enable the F-DPCH usage.

The channel element consumption of the related DCH channels are not included in the HSPA numbers, see the Dimensioning WCDMA RAN.

Both DCH and E-DCH can be used for the AMR call. The E-DCH usage is supported by feature CS voice over HSPA with 2ms and 10ms TTI in WBTS6.0 On Top release. DCH is supported simultaneously with the HSUPA 10ms TTI, and that is already in the WBTS4.0.

1.13 HSUPA mobilityIn the WBTS6.0 release, Serving E-DCH Radio Link Change is supported and the Serving E-DCH Radio Link is the same as the Serving HS-DSCH Radio Link.

Serving E-DCH Radio Link Change can be either Intra-BTS (between cells inside the same BTS) or Inter-BTS (between different BTSs).

Softer and Soft handover for E-DPCH is supported containing maximum three radio links in an E-DCH Radio Link Set (RLS).

1.14 Power control for the HSUPA channelsE-DCHOuter Loop Power Control For the Outer Loop Power Control purposes, BTS sends

information to the RNC on that how many times the UE transmitted the MAC-e PDU before it was successfully decoded in the BTS. Or, if the maximum number of retransmissions is reached, the BTS transmits HARQ Failure.

Based on the number of retransmissions and HARQ Failure informa-tion, the RNC can transmit an additional Signal-to-interface Ration (SIR) Target to the BTS in the FP: OUTER LOOP POWER CONTROL control frame.

E-RGCH, E-AGCH and E-HICHE-RGCH, E-HICH and E-AGCH have power offsets which are configured by the RNC for each cell.

1.15 HSUPA Congestion ControlWhen the BTS sends an E-DCH Frame Protocol frame to the RNC, every frame includes two parameters for the congestion control purposes:

• the time when the MAC-e PDU was successfully received (CFN) • the Frame Sequence Number (FSN)

By using the CFN and FSN parameters, the RNC detects if the frames are lost in the Iub interface, and the build-up of relative delay that the frame protocol frame transmission took in the Iub interface.

26 DN70223925Issue 03B


Id:0900d80580749a5e

HSUPA in WBTS6.0

When the RNC detects the congestion, it starts the controlling actions by sending the Frame Protocol FP: TNL CONGESTION INDICATION control frame to the BTS. The Congestion Status parameter can be set to the following values:

• ‘TNL Congestion – detected by delay build-up’ • ‘TNL Congestion – detected by frame loss’

When the BTS receives the FP: TNL Congestion Indication control frame, the PS selects the user(s) to downgrade and starts to downgrade the bitrate by sending the relative grant ‘DOWN’ to the concerned UE. PS utilises mainly the same algorithm for selecting the users to congestion downgrade as it uses for cell power overload downgrades. If QoS parameters are defined they are automatically taken into account. Because of this selection method it is likely that congestion downgrade actions can affect also other users in the cell than the one that received the Congestion Indication from RNC. It is also possible that the user which got the Congestion Indication is not affected at all (note dif-ference to RAS06 algorithm, where QoS was not in place yet).

According to QoS PS algorithm the users are sorted according to the weighted bitrate and that defines the order in which the downgrade actions are done. Actions start from the one having the highest weighted bitrate and continue towards the one having the lowest weighted bitrate. For information of how weighted bitrate is defined see chapter Quality of Service Scheduling.

During congestion actions the user bitrates are gradually downgraded all the way to the NBR level (if the congestion situation continues long enough that NBR is reached).

When the RNC detects that the congestion is not anymore in the Iub, the RNC sends a ‘No TNL congestion’ indication, and when it is received, the PS goes gradually into normal operation.

1.16 MeasurementsL1 measurements Received Total Wideband Power (RTWP) is a common measurement and is measured from all the cells supporting E-DCH. The measurement values are used in WCDMA BTS Packet Scheduler and it is also transmitted to the RNC.

Transmitted carrier power of all codes is not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission . The measurement is a common measurement and the value is transmitted to the RNC.

For more information on RTWP, see 3GPP TS 25.215: Physical Layer – Measurements (FDD).

For more information on common measurement, see 3GPP TS 25.433.

MAC-e measurements the E-DCH provided bitrate measurement is a common measurement which is done as defined in the standard 3GPP TS 25.321 Medium Access Control (MAC) protocol spec-ification.

DN70223925Issue 03B

27

WCDMA RAN HSUPA in BTS Features per release

Id:0900d80580749aff

2 Features per releaseThe following table lists the features related to this functional area. The features are arranged according to the release in which they were introduced. Note that a feature might belong to more than one functional area.

RAS06

RAN826 Basic HSUPA

RAN968 HSUPA BTS Packet Scheduler

RAN970 HSUPA Handovers

RAN973 HSUPA Basic RRM

RAN974 HSUPA with Simultaneous AMR Voice Call

RAN979 HSUPA 2.0 Mbps

RAN992 HSUPA Congestion Control

RU10

RAN285 HSPA Multi NRT RABs

RAN930 PS RAB Reconfiguration

RAN1004 Streaming QoS for HSPA

RAN1101 Cell Throughput Measurements in BTS

RAN1262 QoS Aware HSPA Scheduling

RAN1465 HSUPA 60 Users per BTS

RU20

New features are supported with FSMC/D/E and EUBB hardware.

RAN981 HSUPA 5.8Mbps

RAN1201 Fractional DPCH

RAN1644 Continuous Packet Connectivity

RAN1686 HSPA 72 Users Per Cell

RU20 On Top

RAN1683 CS Voice over HSPA

Table 6 Features per release

28 DN70223925Issue 03B


Id:0900d80580734b33

Management data for HSUPA in BTS

3 Management data for HSUPA in BTS

3.1 AlarmsFor more information on alarms, see RNC base station alarms, customer document.

3.2 CountersFor more information on counters, see the WBTS counters customer document.

Database ID Fault name

135 HSUPA capacity decreased

Table 7 Alarms

PI ID Counter name

M5000C128 MAC-E PDU RETRANSMISSIONS 0 COUNTER













M5000C141 MAC-E PDU DTX COUNTER

M5003C19 MAC-E PDU LOST

M5000C142 MAC-E PDU HARQ FAILURE COUNTER

M5000C144 MAC-E PDU RETRANSMISSIONS UNKNOWN COUNTER

M5001C9 MAXIMUM NUMBER OF USED CE FOR HSUPA UL

M5001C10 MINIMUM NUMBER OF USED CE FOR HSUPA UL

M5001C11 AVERAGE NUMBER OF USED CE FOR HSUPA UL

M5001C12 MAXIMUM NUMBER OF USED CE FOR HSUPA DL

M5001C13 MINIMUM NUMBER OF USED CE FOR HSUPA DL

M5001C14 AVERAGE NUMBER OF USED CE FOR HSUPA DL

Table 8 RAN826 Basic HSUPA

DN70223925Issue 03B

29

WCDMA RAN HSUPA in BTS Management data for HSUPA in BTS

Id:0900d80580734b33

5000C145 HSUPA DL PHYSICAL CHANNEL POWER DISTRIBU-TION - CLASS 01

M5000C146 HSUPA DL PHYSICAL CHANNEL POWER DISTRIBU-TION - CLASS 02





M5000C151 HSUPA MINIMUM MAC-D THROUGHPUT

M5000C152 HSUPA MAXIMUM MAC-D THROUGHPUT

M5000C153 HSUPA AVERAGE MAC-D THROUGHPUT

M5000C154 HSUPA UL MINIMUM PHYSICAL CHANNEL POWER

M5000C155 HSUPA UL MAXIMUM PHYSICAL CHANNEL POWER

M5000C156 HSUPA UL AVERAGE PHYSICAL CHANNEL POWER

PI ID Counter name

M5002C22 TOTAL HSUPA DATA FOR SPI 0
















M5000C180 UE SERVING POWER HEADROOM VALUE 00


Table 9 RAN1262: QoS Aware HSPA Scheduling

Table 8 RAN826 Basic HSUPA (Cont.)

30 DN70223925Issue 03B


Id:0900d80580734b33
































M5000C212 UE NON-SERVING POWER HEADROOM VALUE 00







Table 9 RAN1262: QoS Aware HSPA Scheduling (Cont.)

DN70223925Issue 03B

31


Id:0900d80580734b33


























M5000C244 NON-SERVING E-RGCH COMMANDS

M5000C245 FRACTIONAL LOAD VALUE DISTRIBUTION - CLASS 00












32 DN70223925Issue 03B


Id:0900d80580734b33












M5000C266 HSUPA NUMBER OF HAPPY BITS

M5000C267 HSUPA NUMBER OF UNHAPPY BITS

PI ID Counter name

M5002C2 E-DCH DATA VOLUME FOR SERVING CELL UL

M5002C3 E-DCH DATA VOLUME FOR NON-SERVING CELL IN SERVING E-DCH RLS UL

M5002C4 E-DCH DATA VOLUME FOR NON-SERVING CELL IN NON-SERVING E-DCH RLS UL

M5003C7 E-DCH DATA VOLUME TO IUB-INTERFACE

Table 10 RAN1101 Cell Throughput Measurements in BTS

PI ID Counter name

M5000C285 SUM OF ACTIVE CPC USERS

M5000C286 MAXIMUM NUMBER OF ACTIVE CPC USERS

M5000C288 SUM OF CPC CONFIGURED USERS

M5000C289 MAXIMUM NUMBER CPC CONFIGURED USERS

M5000C327 CPC USERS DENOMINATOR

M5000C291 NUMBER OF NON DTX DPCCH SLOTS

M5000C292 NUMBER OF DPCCH SLOTS

Table 11 RAN1644 Continuous Packet Connectivity

PI ID Counter name

M5002C38 UE HSUPA THROUGHPUT CLASS 00


Table 12 RAN981 HSUPA 5.8 Mbps


DN70223925Issue 03B

33


Id:0900d80580734b33











M5000C320 HSUPA MACE PDUS WITH 2MS TTI

M5000C321 HSUPA MACE PDUS WITH 10MS TTI

M5000C322 HSUPA MACE PDU DATA WITH 2MS TTI

M5000C323 HSUPA MACE PDU DATA WITH 10MS TTI

M5000C324 SUM OF HSUPA USERS WITH 2MS TTI

M5000C325 SUM OF HSUPA USERS WITH 10MS TTI

M5000C293 HSUPA DL PWR RATIO DISTRIBUTION - CLASS 01





M5000C298 AVERAGE HSUPA DL PWR CONTROL CHANNELS

PI ID Counter name

M5000C299 UNHAPPY FRACTIONAL LOAD VALUE DISTRIBUTION - CLASS 00







Table 13 RAN1470 HSUPA 2 ms TTI

Table 12 RAN981 HSUPA 5.8 Mbps (Cont.)

34 DN70223925Issue 03B


Id:0900d80580734b33


3.3 ParametersThis chapter lists the commissioning parameters in WBTS6.0 release for operating HSUPA in WCDMA BTS.

If several LCGs are configured into BTS then the parameters are defined per LCG.

In special case that two frequency layers are configured into LCG, then parameters are defined per frequency layer.















Table 13 RAN1470 HSUPA 2 ms TTI (Cont.)

Commissioning parameter name:

LCG associated with HSUPA

Range 1..n

Table 14 Parameters for LCG associated with HSUPA

DN70223925Issue 03B

35


Id:0900d80580734b33


Minimum number of HSUPA UE per BTS

Range 0…24

Default value ’0’

Table 15 Parameters for Minimum number of HSUPA UE per BTS


Minimum baseband decoding capability [Mbps]

Range 0…5,6

Allowed values ‘0’, ‘<1.4’, ‘1.4’, ‘2.8’, ‘4.2’, ‘5.6’


Table 16 Parameters for Minimum baseband decoding capability [Mbps]

Commissioning Parameter name:

Mapping HSPA Cell to HW

Range FlexiBTS:

FSM1/ FSM2

UltraSite:

SUBRACK1 / SUB-RACKULTRA

Default value Automatic selection is done to subrack con-taining EUBB in Ultra-Site or FSMC/D/E in FlexiBTS

Table 17 Parameters for Mapping HSPA Cell to HW


Scheduling Weight for SPI class [0-15]

Range 0…99,100


Table 18 Parameters for Scheduling Weight for SPI class [0-15]


Happy Bit -ratio ping filter

Range ON/OFF

Table 19 Parameters for Happy Bit -ratio ping filter

36 DN70223925Issue 03B


Id:0900d80580734b33


Default value ON


Happy Bit -ratio UPH threshold

Range 0…30,31

Default value ‘10’

Table 20 Parameters for Happy Bit -ratio UPH threshold

Table 19 Parameters for Happy Bit -ratio ping filter (Cont.)

PDF Fad Hsupa in Bts

Documents

dimensioning wcdma ran

tnl congestion detected

nokia siemens networks

serving power headroom

ran826 basic hsupa

hsupa basic characteristics

wcdma ran hsupa

2ms tti capable