24_HSUPA_Workaround_for_MultiRadioPlanner

1 © Nokia Siemens Networks HSUPA Workaround for MultiRadio Planner / Kimmo Mäkeläinen / 13.11.2007For internal use


HSUPA Workaround for MultiRadio PlannerKimmo Mäkeläinen (GS MS NPO Tools Mgmt & Support)RU10 Dimensioning Workshop21-25 April 2008, Jakarta

3 © Nokia Siemens Networks HSUPA Workaround for MultiRadio Planner / Kimmo Mäkeläinen / 13.11.2007 For internal use

HSUPA in Release 6 of UMTS

HSUPA uses several techniques to improve the efficiency of the uplink communication. Some of these techniques - like fast HARQ protocols, fast Node B controlled scheduling, short frame size and improved QoS - are used both for HSDPA and HSUPA. HSUPA is more complex than HSDPA, since HSUPA incorporates:• soft handover support;• more complex scheduling algorithms;• uplink interference management scheme; and• coordination between Node Bs.


Rel. ’99 DCH, HSDPA and HSUPA Differences Feature DCH HSDPA (HS-DSCH) HSUPA (E-DCH)

Adaptive multirate coding

no up to 14.4 Mbit/s channel rate

up to 5.7 Mbit/s channel rate

Adaptive modulation no yes, QPSK/16-QAM no

Fast power control yes no yes

Soft handover yes no yes

Fast scheduling and link adaptation

no yes, point to multipoint

yes, multipoint to point

Physical layer retransmission

no yes yes

Variable spreading factor

yes, minimum SF=4 no, fixed SF=16 yes, minimum SF=2

TTI 80, 40, 20, 10 ms 2 ms 10, 2 ms

Non-scheduled transmission

no no yes, for minimum/ guaranteed bit rate


Examples of HSUPA Transport Formatsair interf. rate user data rate‡ [kbit/s]

SF combination coding rate† [kbit/s] 2 ms TTI 10 ms TTI

1xSF32 0.25 120 18 27.61xSF16 0.25 240 48 57.6

1xSF8 0.25 480 108 117.6

1xSF8 0.33 480 148 157.6

1xSF4 0.25 960 228 237.6

1xSF4 0.33 960 308 317.61xSF4 0.50 960 468 477.6

2xSF4 0.25 1920 468 477.6

2xSF4 0.33 1920 628 637.6

2xSF4 0.50 1920 948 957.6

2xSF2 0.25 3840 948 957.62xSF2 0.33 3840 1268 1277.6

2xSF2 0.50 3840 1908 1917.6

2xSF2+2xSF4 0.33 5760 1908 1917.6

2xSF2+2xSF4 0.50 5760 2868 1997.62xSF2+2xSF4 0.75 5760 4308 1997.6

2xSF2+2xSF4 1.00 5760 5748 1997.6

† coding rate of channel coding without CRC

‡ user data rate does not include the 24-bit CRC, which consumes 2.4 kbit/s for 10 ms TTI and 12 kbit/s for 2 ms TTI


HSUPA Terminal CategoriesThere are six different HSUPA terminal categories according to their radio access capabilities: • maximum number of E-DCH codes transmitted, • minimum spreading factor, and • support for 2 ms TTI.

Terminal category

Maximum number of

E-DCH codes

Minimum spreading

factor

Support for 10 and 2 ms

TTI

Max. L1 data rate with 10 ms TTI

[Mbit/s]

Max. L1 data rate with 2 ms TTI [Mbit/s]

1 1 SF4 10 ms 0.711 -2 2 SF4 2,10 ms 1.4484 1.3993 2 SF4 10 ms 1.4484 -4 2 SF2 2,10 ms 2 2.8865 2 SF2 10 ms 2 -6 4 SF2 2,10 ms 2 5.742

The max. L1 data rate of terminals restricts HSUPA user data rates at 10 ms TTI to be below 2 Mbit/s.


Real HSUPA Support for Planner is delayed

MultiRadio Planner 5.2 is supporting HSDPA, but it is not supporting HSUPA.

MultiRadio Planner 6.0 will not include HSUPA support, which is now postponed until version 6.1, and it may be still postponed further.

►During the year 2008 HSUPA can be only modeled in Planner by using workarounds that utilize the existing UMTS functionality.


HSUPA Modelling in MultiRadio Planner

The main HSUPA features to be modeled in the tool are:• multicode transmission,• 10 ms and 2 ms TTI,• variable SF,• HARQ,• soft handover,• power control,• packet scheduling.They are modelled by defining UMTS bearers with appropriate data rates, Eb/No requirements, power control and soft handover parameters


HSUPA Resource Consumption 1/2

The number of HSUPA users is specified as an UMTS resource.

In RAS06 the max. number of HSUPA users in a cell is 20, but in a Node B it is only 24.

Hence, the new resource HSUPA_users should be pooled at Node B level in all Node B Types that support HSUPA, and the limit for the HSUPA_users resource should be set to 24 in downlink.


HSUPA Resource Consumption 2/2

HSUPA is normally added to UMTS Nodes that are already supporting HSDPA.►UMTS resources and the HSDPA resource are already in

use at the Node.

MultiRadio Planner allows a Node B to use only 3 resources.►It may be necessary to combine the no. of HSUPA users with

one of the UMTS resources.For HSUPA bearers such resource will correspond to HSUPA users; for UMTS bearers it will be interpreted differently.


HSUPA Bearers 1/5Different transport formats (= TTI duration + SF combination + coding rate) are modelled by defining separate UMTS uplink bearers.Each different transport format is mapped onto an uplink UMTS bearer by defining the corresponding Air Interface and User rate as well as control overhead factor. The Resource Consumption of HSUPA_users is set to 1 for all bearers.

For example, a bearer at L1 data rate 1024 kbit/s, which is trans-ported at 10 ms TTI with SF combination 2xSF2, defines the following bearer.

The fact that two parallel codes are used is modeled only through the air interface rate.


HSUPA Bearers 2/5HSUPA bearers for 10 ms TTI with the following air interface and user rates have been used in Aalborg link simulations:

Bearer Air interf. rate [kbit/s] User rate [kbit/s] Control overh. factor [%]

HSUPA_10ms_1xSF32_32 120000 29600 8.1

HSUPA_10ms_1xSF16_64 240000 61600 3.9

HSUPA_10ms_1xSF8_128 480000 125600 1.9

HSUPA_10ms_1xSF8_160 480000 157600 1.5

HSUPA_10ms_1xSF4_256 960000 253600 0.9

HSUPA_10ms_1xSF4_320 960000 317600 0.8

HSUPA_10ms_1xSF4_448 960000 445600 0.5

HSUPA_10ms_2xSF4_512 1920000 509600 0.5

HSUPA_10ms_2xSF4_640 1920000 637600 0.4

HSUPA_10ms_2xSF4_928 1920000 925600 0.3

HSUPA_10ms_2xSF2_1024 3840000 1021600 0.2

HSUPA_10ms_2xSF2_1248 3840000 1245600 0.2

HSUPA_10ms_2xSF2_1920 3840000 1917600 0.1


HSUPA Bearers 3/5

The name of a bearer defines TTI, SF combination and L1 data rate. For example, the bearer HSUPA_10ms_2xSF4_512 uses the SF combination 2xSF4 at the L1 data rate 512 kbit/s at 10 ms TTI.

The Eb/No requirements have been computed from SINR values that include the (E-DPCCH) control channel power. Hence, the control overhead factors of HSUPA bearers in Planner include only the overhead of a 24-bit CRC within each TTI (2.4 kbit/s for 10 ms TTI and 12 kbit/s for 2 ms TTI).

The bearers for 2 ms and 10 ms TTIs have the same air interface rates and L1 rates, and hence they have the same Eb/No requirements. The only difference between bearers for 2 ms and 10 ms TTIs is that there are five 24-bit CRCs within a 10 ms frame for 2 ms bearers. Hence, the user data rates and control overhead factors are different, but all other parameters are equal.


HSUPA Bearers 4/5Air interface and user data rates and control overhead factors of HSUPA bearers for 2 ms TTI are:

Bearer Air interf. rate [kbit/s] User rate [kbit/s] Control overh. factor [%]

HSUPA_2ms_1xSF32_32 120000 20000 60.0

HSUPA_2ms_1xSF16_64 240000 52000 23.1

HSUPA_2ms_1xSF8_128 480000 116000 10.3

HSUPA_2ms_1xSF8_160 480000 148000 8.1

HSUPA_2ms_1xSF4_256 960000 244000 4.9

HSUPA_2ms_1xSF4_320 960000 308000 3.9

HSUPA_2ms_1xSF4_448 960000 436000 2.8

HSUPA_2ms_2xSF4_512 1920000 500000 2.4

HSUPA_2ms_2xSF4_640 1920000 628000 1.9

HSUPA_2ms_2xSF4_928 1920000 916000 1.3

HSUPA_2ms_2xSF2_1024 3840000 1012000 1.2

HSUPA_2ms_2xSF2_1248 3840000 1236000 1.0

HSUPA_2ms_2xSF2_1920 3840000 1908000 0.6


HSUPA Bearers 5/5

RAS06 of NSN does not support the SF combination 2xSF2+2xSF4. The fastest supported SF combination is 2xSF2.

Since the max. L1 data rate at 10 ms TTI is restricted to be below 2 Mbit/s, the SF combination 2xSF2+2xSF4 cannot provide much higher user data rates than 2xSF2. The SF combination 2xSF2+2xSF4 can only provide very high data rates at 2 ms TTI.

The Eb/No requirements for 2xSF2+2xSF4 bearers would be the same as for 2xSF2 bearers at corresponding coding rate.


HSUPA Bearers: Eb/No Requirements 1/6

The Eb/No requirements of UMTS bearers modeling HSUPA are specified in the Eb/No & Speed Delta tab of the Bearers dialog.

The user specifies the Eb/No target for the link and also the offsets in that Eb/No for different vehicular speeds.



The Eb/No requirements from Aalborg link simulations are defined for the L1 data rate (that includes user data and CRC). In NetAct Planner, Eb/No requirements must be given at the selected air interface rate.

Any Eb/No requirement that has been given for the L1 data rate R1 can be converted into a corresponding Eb/No requirement at the air interface rate Ra simply as

(Eb/No)a [dB] = (Eb/No)1 [dB] + 10 log(R1/Ra).

Conversion of Eb/No requirements to air interface rate is only required for the Link Eb/No values (with and without diversity). The speed offsets in dB are naturally the same irrespective of the assumed bit rate.

The Aalborg values are valid for 2-way Rx diversity. No values are currently available for reception without diversity.



The Link Eb/No values for Planner have been computed from the Aalborg link simulations for 3 km/h in Pedestrian A channel, and the Eb/No offsets for 3 km/h have been set to zero.

The 50 km/h Eb/No offsets for Planner have been computed from the link simulations for 30 km/h in Vehicular A channel without any adjustment for speed.

The 120 km/h Eb/No offsets for Planner have been set to be equal to the 50 km/h Eb/No offsets. Realistic Eb/No requirements at 120 km/h speed would probably be much higher that the ones at 50 km/h, especially at higher user data rates.

No values are currently available for other SF combinations (e.g. 2xSF2+2xSF4) or for higher coding rates.


HSUPA Bearers: Eb/No Requirements 4/6Eb/No

fromsimulations

Link Planner Eb/Nos

Bearer Layer 1 bit rate [kbit/s]

Air interface bit rate [kbit/s]

3 km/h (Ped A)

30 km/h (Veh A)

Link Eb/No Offset at 50 km/h

HSUPA_10ms_1xSF32_32 32 120 4.16 2.81 -0.58 -1.35

HSUPA_10ms_1xSF16_64 64 240 2.48 1.73 -2.26 -0.75HSUPA_10ms_1xSF8_128 128 480 0.80 0.93 -3.94 0.13

HSUPA_10ms_1xSF8_160 160 480 0.09 0.47 -3.68 0.38

HSUPA_10ms_1xSF4_256 256 960 -0.30 0.11 -5.04 0.41

HSUPA_10ms_1xSF4_320 320 960 -0.64 -0.15 -4.41 0.49HSUPA_10ms_1xSF4_448 448 960 -1.38 -0.78 -3.69 0.59

HSUPA_10ms_2xSF4_512 512 1920 -0.76 -0.43 -5.50 0.32

HSUPA_10ms_2xSF4_640 640 1920 -1.00 -0.60 -4.77 0.40

HSUPA_10ms_2xSF4_928 928 1920 -1.20 -0.78 -3.35 0.42

HSUPA_10ms_2xSF2_1024 1024 3840 -1.16 -0.76 -5.90 0.40HSUPA_10ms_2xSF2_1248 1248 3840 -1.31 -0.92 -5.19 0.39

HSUPA_10ms_2xSF2_1920 1920 3840 -0.90 -0.51 -2.91 0.39


HSUPA Bearers: Eb/No Requirements 5/6The Eb/No requirements of bearers using different SF combinations cannot be directly compared. In order to compare different 10 ms bearers, we have to look their SINR requirements

Bearer Link Eb/No [dB] SINR [dB]

HSUPA_10ms_1xSF32_32 -0.58 -15.63

HSUPA_10ms_1xSF16_64 -2.26 -14.30

HSUPA_10ms_1xSF8_128 -3.94 -12.97

HSUPA_10ms_1xSF8_160 -3.68 -12.72

HSUPA_10ms_1xSF4_256 -5.04 -11.06

HSUPA_10ms_1xSF4_320 -4.41 -10.43

HSUPA_10ms_1xSF4_448 -3.69 -9.71

HSUPA_10ms_2xSF4_512 -5.50 -8.51

HSUPA_10ms_2xSF4_640 -4.77 -7.78

HSUPA_10ms_2xSF4_928 -3.35 -6.36

HSUPA_10ms_2xSF2_1024 -5.90 -5.90

HSUPA_10ms_2xSF2_1248 -5.19 -5.19

HSUPA_10ms_2xSF2_1920 -2.91 -2.91



The computed SINR values are the SINR values at the antenna connector of a CDMA receiver.

The SINR requirements of HSUPA are about 5 dB lower than the SINR requirements of HSDPA at the same user data rates!

The HSUPA Eb/No values are for 2-way Rx diversity, which lowers the results somewhat, but it cannot fully explain a 5 dB difference.


HSUPA Bearers: Power Control and Soft Handover Parameters

HSUPA transmission is power controlled, and soft handover can be used with HSUPA terminals.

►All power control and soft handover parameters (power control headroom, average power rise, TXP Gain, PR Gain and PCH Gain) apply to HSUPA bearers in the same way as to normal UMTS uplink bearers. The recommended UMTS parameter values can be used as such also for HSUPA bearers.


HSUPA Services and Terminals 1/2

Different HSUPA terminal categories can be modelled by creating a different service for each category, and assigning one service to one terminal type.

Selection of bearers for a service depends on the terminal’s capabilities.

For example in order to model the terminal category 5, the corresponding service should have only bearers for 10 ms TTI, and it should not use more than two parallel codes.


HSUPA Services and Terminals 2/2The (power) activities of the UL bearers in the HSUPA service have been computed for the 128 kbit/s application data rate. Hence, the average data rate of every bearer is 128 kbit/s; except for the lowest-rate bearers that cannot provide so high user data rate.

UL Bearer Activity [%] Average bit rate [kbit/s]

HSUPA_10ms_1xSF32_32 100.0 29.6

HSUPA_10ms_1xSF16_64 100.0 61.6

HSUPA_10ms_1xSF8_128 100.0 125.6

HSUPA_10ms_1xSF8_160 81.2 128.0

HSUPA_10ms_1xSF4_256 50.5 128.0

HSUPA_10ms_1xSF4_320 40.3 128.0

HSUPA_10ms_1xSF4_448 28.7 128.0

HSUPA_10ms_2xSF4_512 25.1 128.0

HSUPA_10ms_2xSF4_640 20.1 128.0

HSUPA_10ms_2xSF4_928 13.8 128.0

HSUPA_10ms_2xSF2_1024 12.5 128.0

HSUPA_10ms_2xSF2_1248 10.3 128.0

HSUPA_10ms_2xSF2_1920 6.7 128.0


HSUPA XML Import Files

The embedded XML import files for HSUPA Workaround in NetAct Planner (ver. 5.2) contain:• new resource modeling no. of HSUPA users,• all HSUPA bearers (that have been presented earlier),• one HSUPA service that uses all the HSUPA bearers in uplink and no bearers in downlink,• one HSUPA terminal that uses the HSUPA service; due to selection of HSUPA bearers it

corresponds roughly to the HSUPA terminal category 5.

The HSUPA parameters should be imported by selecting the file INDEX001.xml.

The HSUPA terminal has HSDPA enabled in order to use HSDPA scheduling for HSUPA terminals. In most cases, the HSUPA terminal should use HSDPA bearers on downlink, then the HSDPA bearers should be added to the HSUPA service.

Resource limits for the HSUPA_users resource in Node Bs are not included in the XML import files. Users must edit them manually after XML import.

C:\HSUPA_XML_import.zip


Resource Limits 1/2

The best way to set the limits for the resource HSUPA_users is to define them in all Node B Types that support HSUPA (under Equipment | Node Types).The resource HSUPA_users should be pooled at Node B level, and the limit for the HSUPA_users resource should be set to 24 in downlink.


Resource Limits 2/2

The Node B Type can be assigned to selected Node B Types, and the resource limits for the HSUPA_users resource can be edited under Node Config tab of Global Editor in Site Database.


Thank you for your attention.

24_HSUPA_Workaround_for_MultiRadioPlanner

Documents

Transcript of 24_HSUPA_Workaround_for_MultiRadioPlanner