42 MBPS DL - DC HSDPA TRIAL

InstructionEricsson Internal

1 (38)Prepared (also subject responsible if other) No.

EAB/FJZ/M Mansour Akbari,Thommy Lindgren 16/221 01-FGB 101 135Approved Checked Date Rev Reference

EAB/FJZ/M Bengt Mäler 2012-02-29 D

Sale Trial Instruction - 42 Mbps (Multi Carrier)

Abstract

The main objective of this instruction is how to proof features value and connect to business case.

Contents1 Introduction.......................................................................................... 32 Prerequisites ........................................................................................ 3

2.1 WRAN...................................................................................... 32.2 Transport.................................................................................. 52.3 OSS ......................................................................................... 52.4 HLR.......................................................................................... 52.5 SGSN....................................................................................... 62.6 GGSN ...................................................................................... 62.7 Tools ........................................................................................ 7

3 Observability ........................................................................................ 73.1 Counters................................................................................... 7

4 Multi Carrier Cell Configuration .......................................................... 95 Trial Measurement ............................................................................. 11

5.1 Objectives .............................................................................. 115.2 Precondition ........................................................................... 115.3 Trial Execution........................................................................ 13

6 Capacity Gain Calculation ................................................................. 236.1 Double throughput in entire cell .............................................. 236.2 Multi Carrier Aggregation Gain ............................................... 24

7 Measurement graphs ......................................................................... 257.1 Peak throughput ..................................................................... 257.2 Double throughput in entire cell .............................................. 267.3 Multi Carrier Aggregation Gain ............................................... 27

8 Troubleshooting................................................................................. 298.1 Code verification..................................................................... 298.2 CQI Improvements ................................................................. 338.3 IRAT Consideration ................................................................ 34





8.4 RBS SuperTrace .................................................................... 34

9 References ......................................................................................... 3510 Appendix ............................................................................................ 35

10.1 Parameter List ........................................................................ 3610.2 Code Tree Usage................................................................... 3710.3 Activation PDP Context Accept message ............................... 37





1 Introduction

Test cases described in this document are intended for either non-commercial network (e.g. lab system) or commercial network (preferably indoor site). Prerequisites (HW, SW) for all nodes described are a must in order to reach proof point values.

2 Prerequisites

2.1 WRAN

2.1.1 Software

RNCRNC software release must be W10B or later

RBSRBS software release must be W10B or later

Note: RBS software release W10A does not support DUW base band HW. It gives a max peak rate of 32 Mbps due to code limitation (i.e. 26 codes available)

2.1.2 Features

Feature no Feature Title Feature Classification

Node

FAJ 121 1441 Multi Carrier A RBS

FAJ 121 1033 HSDPA Introduction Package A RBS/RNC

FAJ 121 1331 Support for 64 QAM A RBS

FAJ 121 1328 Enhanced Layer 2 B RBS

FAJ 121 903 HSDPA 16QAM A RBS

FAJ 121 0401 15 HSDPA codes per cell A RBS





FAJ 121 1023 Enhanced Uplink Introduction Package

A RBS/RNC

FAJ 121967 HSDPA Dynamic Code Allocation A RBS

FAJ 121 968 HSDPA Flexible Scheduler B RBS

FAJ 121 969 HSDPA Code Multiplexing and HS-SCCH Power Control

B RBS

FAJ 121 148 Interactive RAB up to 384 kbps Packet Data

C RNC

FAJ 121 1132 Iub over IP/Ethernet in RBS B RBS

FAJ 121 1118 Iub over IP transport in RNC B RNC

Feature HSDPA Link Adaptation FAJ 121 1358 is not required but it mightincrease peak rate in good radio condition.

Note: All features are subject to licensing. For more information about Feature Classification consult Product Catalog.

2.1.3 Hardware

2.1.3.1 RBS

RBS 3000 family

DUW 10 only for site configured with 1x2 with one MC cell

DUW 20 or DUW 30 for site with 3x2 configurations

RBS 6000 family

DUW 10 only for site configured with 1x2 with one MC cell

DUW 20 or DUW 30 for site with 3x2 configurations

Note: RBS 3000 without DUW base band HW has a max peak rate of 32 Mbps for MC cell.





2.1.3.2 RNC

Special purpose Processor Board, SPB3

RNC 3810 uses ET-MFX12 or 13

RNC 3820 uses ET-IPG

2.2 Transport

Iub over IP/Ethernet RBS/RNC

Transport network supports user data peak rate of 42 Mbps per MC cell (i.e. 51 Mbps bandwidth per MC cell)

See reference 2 for RBS 6000 transport solution.

2.3 OSS

OSS-O10.2 release or later

2.4 HLR

2.4.1 Software

R14.1 release with feature

Feature no Feature Title Node

FAJ 122 508/3 HSDPA in HLR HLR

Or

R13.2 release with market customization, patch MDE 6470 and correction R01MCXJM-7000 with feature


FAJ 122 508/3 HSDPA in HLR HLR





2.5 SGSN

2.5.1 Software

SGSN 2009B release or later

2.5.2 Features


FAJ 121 0050 Enhanced Uplink Support SGSN

FAJ 121 941 HSDPA Support, up to 4 Mbps SGSN

FAJ 121 942 HSDPA Support Expansion 1 SGSN




2.6 GGSN

2.6.1 Software

GGSN 2009B release or later

2.6.2 Features


FAJ 121 870/1 HSDPA Support, 2-4Mbps GGSN

FAJ 121 949/1 HSDPA Support Expansion 1, 4-8Mbps GGSN

FAJ 121 0079/1 HSDPA Support Expansion 2, 8-16Mbps

GGSN


GGSN





FAJ 121 0080/1 Enhanced Uplink Support (HSUPA), 2-4Mbps

GGSN


GGSN

2.7 Tools

TEMS Investigation 11.0.1 or later version AutoTest – RAN I&V test tool NetPerSec Software to measure application throughput live UE Cat 24/6 modem e.g. Sierra Wireless USB312 FTP server connected close to the GGSN with at least 2 GB file Laptop XP OS Wireshark on both sides (server and PC) to measure IP throughput Filezilla software for FTP downloading UDP server (one of the below options):

o Iperf software is needed on both sides (server and PC)o TPtest software is needed on both sides (server and PC)

Note: Iperf and Tptest software are available on internet as freeware.

Verify the laptop configuration for example using TCP Optimizer.

TCP Receiver Window Size 256 kB = < size < 512 kB Windows scaling: ON Selective Acknowledgement: ON Max number o duplicated ACKs: 2 or 3 TCP time stamping: OFF MTU size: 1400 -1460 Bytes

3 Observability

3.1 Counters

3.1.1 RBS

RBS counters





pmSumNonEmptyUserBuffersPqSpixx

pmSumAckedBitsPqSpixx

pmSumAckedBitsSpixx

pmNoActiveSubFrames

pmNoInactiveRequiredSubFrames

pmSumNonEmptyUserBuffersSpixx

pmRemainingResourceCheck

pmCapAllocIubHsLimitingRatioSpixx

pmTransmittedCarrierPowerHs

pmTransmittedCarrierPowerNonHs

pmTransmittedCarrierPower

pmUsedTbs16Qam

pmUsedTbs64Qam

pmReportedCqi

pmReportedCqi64Qam

pmUsedCqi

pmUsedADch

pmAck16Qam

pmAck64Qam

pmAckQpsk

pmNackReceived

pmAckReceived





3.1.1.1 KPI

HsCellThroughput = XX pmSumAckedBitsSpixx /(TTI*(pmNoActiveSubFrames+ pmNoInactiveRequiredSubFrames))

AvreageHsUserThroughput =XX pmSumAckedBitsPqSpixx/(TTI*XXpmSumNonEmptyUserBuffersPqSpixx)

IubHsCapacityLimitingRatio= pmCapAllocIubHsLimitingRatioSpixx

3.1.2 RNC

Average number of HSDPA user =pmSumBestPsHsAdchRabEstablish(UtranCell)/pmSamplesBestPsHsAdchRabEstablish(UtranCell)

3.1.3 UE

3.1.3.1 Tems

HS Phy Scheduled Throughput (kbits/s) Calculated as: Sum of TBSs for non-DTX blocks / Total TTI time for non-DTX blocks(CRC indication does not matter)

HS Phy Served Throughput Calculated as:

Sum of TBSs for blocks with CRC OK / Reporting period

HS-DSCH throughput is based on the "HSDPA HS-DSCH HARQ Statistics" report. Throughput is calculated as:Sum of received bits for every HARQ process) / Reporting interval. Report interval is specified as 2048 milliseconds.

4 Multi Carrier Cell Configuration

A simple way to check if a cell is configured as a MC cell, print the RNCparameter multiCarrierSupport. If multiCarrierSupport= on then the cell is MC capable otherwise it’s not. Check following to find out what is set wrongly:

RBS:





The two cells is configured to handle by the same TXM (HSDPAprocessing resources) e.g. DUW

The two cells must have the same settings for each of the following parameters:

o queueSelectAlgorithm

o airRateTypeSelector

o schPrioForAbsResSharing

o schMaxDelay

o schWeight

If all conditions above are fulfilled the RBS will set the read-only parameter RbsLocalCell: hsdpaMcCapability to HSDPA_MC_CAPABLE

RNC:

RBS has indicated to be HSDPA MC capable

EUL MO is created at least for one of the MC cells

The two cells have cell relation in MultiCarrier:cellRefsDl

>get . cellrefsdl cellname1|cellname2

UtranCell=6004A2,Hsdsch=1,Eul=1,MultiCarrier=1 cellRefsDl [1] = >>> cellRefsDl = RncFunction=1,UtranCell=6004A1UtranCell=6004A1,Hsdsch=1,Eul=1,MultiCarrier=1 cellRefsDl [1] = >>> cellRefsDl = RncFunction=1,UtranCell=6004A2

The configured frequencies are adjacent to each other.

Parameter value of tCell is equal for the cells.

All value combinations for parameter transmissionScheme are allowed except if one of the cells has the value = SINGLE_ANTENNA and the other has not. Default value = SINGLE_ANTENNA





5 Trial Measurement

5.1 Objectives

To demonstrate proof points of Multi Carrier (MC) benefits:

42 Mbps peak throughput

Double throughput in entire cell

Multi carrier aggregation gain i.e. more than double Single Carrier cell capacity

5.2 Precondition

Secure that parameter setting for proof point test cases in commercial network(preferably indoor site) is understood properly see bullets below:

In order to reach peak rate close to 42 Mbps parametermaxNumHsdpaUsers needs to be set to 1 indicating that only one HS user can enter the cell.

To secure 15 codes are available the following parameters shall be set accordingly

o numHsScchCodes = 1

o numEhichErgchCodes = 1

o maxNumHsPdschCodes = 15

If number of available codes is less than 15 means code tree fragmentation happened. See chapter 8.1

If speech users enter the cell (non-reserved cell) the number of available codes is ended up with 13. In this case it is recommended numHsScchCodes parameter is set to 2 instead of 1 which will guaranty 14 codes as maximum available codes.

To secure a peak throughput of 42 Mbps it is required SPB3 resources are prioritized and allocated to multicarrier UE. Set the following parameters accordingly:

o evolvedHsUePrioEnabled = 1

o evolvedHsUePrioLevel = 3 1





o evolvedHsUePrioLoadThresh = 50

Note: These parameters changes are affected the whole RNC.

The location where the test is performed must have good RF conditions (RSCP -50 dBm)

To reach a throughput of 42Mbps requires an output power of 30 W (44,7 dBm) per carrier.

To reach a throughput of 42Mbps the reported CQI need to be high, close to 30. If the reported CQI values (min, median and max) doesn’t show a value close to 30 try to move the UE to a position where all the CQI values (min, median and max) reported by Tems are as close as possible to 30. If CQI not reached 30 see chapter 8.2 for hints.

Ensure that the profile for the subscription (SIM) used during the test isset in the HLR to 42Mbps. Verify by Tems “ Activate PDP ContextAccept” layer 3 message shows Maximum bitrate for downlink is 42Mbps see chapter 10.3.

It is important to prevent or limit other users to enter the cell. In order to guaranty that No users other than test UE enter the cell, cell shall be reserved using a SIM card with Access Class 15.In case cell can not be reserved for test UE, the PS R99 users can be limited through following parameter settings. Note that speech and HS users can still access the cell

sf32Adm = 0

sf16Adm = 0

sf8Adm = 0

sf16gAdm = 0

sf16AdmUl = 0

sf8AdmUl = 0

sf4AdmUl = 0

sf8gAdmUl = 0

pwrAdm = 50

pwrOffset = 0





.

In lab environment when the UE is connected directly to the RBS via a cabling network, the interference from external UEs are minimized and thus parameter settings become different compared to the commercial network. For peak rate measurements with a signal level better than -50dBm CQIAdjustment feature could be turned off.

5.3 Trial Execution

5.3.1 Peak throughput

The purpose of the test is to show that Multi Carrier gives a peak rate up to 42 Mbps for single user.

5.3.1.1 Test Case 1: 42 Mbps peak throughput

Test Procedure

1. Following features shall be activated before the test

featureStateHsdpaMc FAJ 121 1441

featureState64QAM FAJ 121 1331

featureStateEnhancedLayer2 FAJ 121 1328

featureStateHsdpaDynamicCodeAllocation FAJ 121967


HSDPA Introduction Package FAJ 121 1033

Enhanced Uplink Introduction Package FAJ 121 1023

Interactive RAB up to 384 kbps Packet Data FAJ 121 148

2. Parameter settings

maxNumHsdpaUsers = 1

hsdpaUsersAdm = 1

maxNumEulUsers = 1





eulServingCellUsersAdm = 1

numHsPdschCodes = 14

maxNumHsPdschCodes = 15

numHsScchCodes = 1

numEhichErgchCodes = 1

hsMeasurementPowerOffset = 80

cqiAdjustmentOn = True

hsPowerMargin = 0

3. Set up a HSDPA call in the configured cell and start a minimum of three parallel FTP download sessions from a server connected to GGSN.

4. Start Tems or / and Wireshark recording.

5. Terminate the download measurements after 15 minutes and stop recording. Save log files.

6. If the expected peak rate is achieved go to step 7 otherwise;

Check chapter 5.2 how to reach high throughput

Activate feature HSDPA Link Adaptation FAJ 121 1358 to increase peak rate

7. Create throughput report, see Chapter 7.

Note: In case FTP downloading shows a lower throughput than expected try to use UDP instead.

5.3.2 Double throughput in entire cell

The purpose with this test is to show the DL throughput for MC is twice than the throughput for SC in any point of the entire cell, see figure 1. The test can be performed in two different ways.





1. Stationary: measure throughput in different locations (6 locations) with different RSCP levels.

2. Non-stationary: measure throughput starting close to the antenna the while driving towards cell border.

Figure 1 - Double throughput for a MC user compared to a SC user

5.3.2.1 Test Case 2: Throughput rate in entire cell - Multicarrier

Test Procedure

1. Following features shall be activated before starting the test













2. Parameter settings:


hsdpaUsersAdm = 1

maxNumEulUsers = 1




numHsScchCodes = 1




hsPowerMargin = 0

3. Measurement

One of the following options could be used.

Stationary measurement:

Step 1: Find a location close to the antenna with RSCP -50 dBm. Set up a HSDPA call and start a minimum of three parallel FTP downloadsessions from a server connected to GGSN.

Step 2: Repeat step1 in the following locations with respective RSCP:Location 2 RSCP -60 dBmLocation 3 RSCP -70 dBmLocation 4 RSCP -80 dBmLocation 5 RSCP -90 dBmLocation 6 RSCP -100 dBm





Use Tems to record the RSCP and HSDPA throughput.

Non-stationary measurement:

Set up a HSDPA call close to the antenna and start a minimum of three parallel FTP download sessions from a server connected to GGSN. Start recording RSCP and throughput.

Drive away from site while downloading until you reach the cell border. Make sure the UE has only one cell in active set during the entire drive test.

Use Tems to record the RSCP and HSDPA throughput

Terminate the FTP download and stop the recording.


5.3.2.2 Test Case 4: Throughput rate in entire cell – Single Carrier

Test Procedure

1. Following features shall be activated before the test.








2. Parameter settings:






hsdpaUsersAdm = 1

maxNumEulUsers = 1




numHsScchCodes = 1




hsPowerMargin = 0

3. Measurement

One of the following options could be used.

Stationary measurement:

Step 1: Find a location close to the antenna with RSCP -50 dBm. Set up a HSDPA call and start a minimum of three parallel FTP downloadsessions from a server connected to GGSN.

Step 2: Repeat step1 in the following locations with respective RSCP:Location 2 RSCP -60 dBmLocation 3 RSCP -70 dBmLocation 4 RSCP -80 dBmLocation 5 RSCP -90 dBmLocation 6 RSCP -100 dBm

Use Tems to record the RSCP and HSDPA throughput.

Non-stationary measurement:





Set up a HSDPA call close to the antenna and start a minimum of three parallel FTP download sessions from a server connected to GGSN. Start recording RSCP and throughput.

Drive away from site while downloading until you reach the cell border. Make sure the UE has only one cell in active set during the entire drive test.

Use Tems to record the RSCP and HSDPA throughput

Terminate the FTP download and stop the recording.


5.3.3 Multi Carrier Aggregation gain

The purpose of the test is to show the aggregation gain for Multi Carrier compared to two single carrier cells. The test is performed using 6 UEsdownloading a file with a certain size repetitively with a fixed random delay between download sessions.

5.3.3.1 Test Case 5: Multi user throughput - MC

Test Procedure














2. The following parameters need to be set accordingly to secure that 14 codes can be used and only six users are active in the cell. The parameter setting is valid for both carriers.


numHsScchCodes = 2




hsdpaUsersAdm = 6

maxNumEulUsers = 6




hsPowerMargin = 0

3. Use 6 UEs for multi user throughput as follow:

Set up a traffic profile for six users which has a sequence of 15 ftp downloads of 10 MB file per user. The time delay (D) is the same between each download during each profile measurement. Different D values generate different traffic profiles. The sequence looks like table below.

Start first measurement with D = 40s

UE Start delay (s)

Download session

Time delay(s)

Download session

Time delay(s)

Download session

Time delay(s)

Download session

1 0 1st download D 2nd download D ------------- D 15th download










4. Use Tems or other tools to generate traffic profile for 6 users.

5. Start Tems or/and Wireshark recording.

6. Close logs after measurements are finished. Save log files.

7. Repeat measurements with different time delay (D). Each time delaygenerates a different traffic profile. D= [5s, 10s, 20s, 30s, 50s].

8. Create user throughput report, see Chapter 6 and 7

5.3.3.2 Test Case 6: Multi user throughput - SC

Test Procedure













2. The following parameters need to be set accordingly to secure that 14 codes can be used and only three users are active in the cell. The parameter setting is valid for both carriers.


numHsScchCodes = 2




hsdpaUsersAdm = 3

maxNumEulUsers = 3




hsPowerMargin = 0

3. Use 6 UEs for multi user throughput as follow:

Set up a traffic profile for six users which has a sequence of 15 ftp downloads of 10 MB file per user. The time delay (D) is the same between each download during each profile measurement. Different D values generate different traffic profiles. The sequence looks like table below.

Start first measurement with D = 40s.

UE Start delay (s)

Download session

Time delay (s)

Download session

Time delay (s)

Download session

Time delay (s)

Download session











4. Use Tems or other tools to generate traffic profile for 6 users.

Note: Distribute traffic evenly on each carrier i .e. 3 users per carrier. Use feature HSDPA IFLS FAJ 121 1467 to steer traffic on each carrier. If the feature is not available then Cell Reselection determines on which frequency the UEs camp. In later case the distribution of traffic will not be evenly on each carrier.

5. Start Tems or/and Wireshark recording.

6. Close logs after measurements are finished. Save log files.

7. Repeat measurements with different time delay (D). Each time delaygenerates a different traffic profile. D= [5s, 10s, 20s, 30s, 50s].

8. Create user throughput report, see Chapter 6 and 7.

6 Capacity Gain Calculation

6.1 Double throughput in entire cell

Cell throughput could be calculated using two different methods:

1. Use Pm counters to calculate the average user throughput.

Multicarrier

XX pmSumAckedBitsPqSpixx/(TTI*XX pmSumNonEmptyUserBuffersPqSpixx)

Single carrier

XX pmSumAckedBitsSpixx/(TTI*XX pmSumNonEmptyUserBuffersSpixx)





2. Use the recorded values from Tems log or wireshark to calculate average user throughput.

6.2 Multi Carrier Aggregation Gain

The results from the measurements are compared with each other and the outcome is the difference in average user throughput or offered cell load between Multi carrier and two Single carrier.

The multi carrier aggregation gain could be calculated based on measurement results from:

Wireshark or Tems Investigation log

6.2.1 Calculation example

Below is an example from field measurement using wireshark log to calculate the multi carrier aggregation gain. Note that results from Tems investigation could be used in the same way.

Example 1: Offered cell loadFrom the MC and SC graphs in figure 6 at offered cell load of e.g. 15000 kbps it can be red the following throughput values:

MC throughput = 19500 kbps

2xSC throughput = 9000 kbps

MC Aggregation gain = (MC – 2xSC) / 2xSC = (19500-9000)/9000 = 116%

Example 2: User throughputFrom the MC and SC graphs in figure 6 at user throughput of e.g. 10000 kbps it can be red the following offered cell load:

MC offered cell load = 23000 kbps

2xSC offered cell load = 13500 kbps

MC Aggregation gain = (MC – 2xSC) / 2xSC = (23000-13500)/13500 = 70%

Note that the aggregation gain is depended on offered cell load. If offered cell load is 100%, there will be a little aggregation gain.





7 Measurement graphs

7.1 Peak throughput

7.1.1 Throughput graph using Tems Investigation

Figure 2 – Multi Carrier peak throughput

Note that the HS-DSCH throughput is not correct due to Tems miscalculation. All other throughput figures are correct.





7.1.2 Throughput graph using NetPerSec

Figure 3 - Throughput snapshoot from field measurement

7.1.3 Throughput graph using Wireshark

Use Wireshark to generate a graph to show IP level throughput

7.2 Double throughput in entire cell

The graphs show results extracted from Tems data on average user throughput for Multicarrier vs. Single carrier in the entire cell.





Figure 4 - Multi carrier average throughput

Figure 5 - Single carrier average throughput

7.3 Multi Carrier Aggregation Gain

Figure 6 shows the aggregation gain for multicarrier compared to two single carrier with different cell load.

Throughput vs. RSCP - MC

0

5000

10000

15000

20000

25000

30000

35000

40000

45000

50000

-37

-42

-58

-62

-71

-73

-76

-77

-78

-79

-82

-82

-83

-88

-88

-91

-99

-99

-99

-100

-10

0 -1

00

-101

-10

1 -1

01

-102

-1

03

-103

RSCP

kbp

s

0

5

10

15

20

25

30

35

CQ

I

HS Phy Served Throughput (kbit/s)HS CQI (Max)

Throughput vs. RSCP - SC

0

5000

10000

15000

20000

25000

-41

-42

-42

-61

-61

-62

-71

-73

-77

-77

-77

-78

-82

-83

-87

-87

-87

-92

-93

-93

-93

-94

-95

-95

-96

-96

-96

-97

-98

-99

-103

-109

-109

RSCP

kbps

HS-DSCH Throughput (kbit/s)





Figure 6 – MC vs. 2xSC average user throughput

The figure is based on a number of measurements with 6 UEs. Each measurement represents a traffic profile, see 5.3.3.1 Item 3. Table below shows the value from one of the traffic profile measurements.

Average UE throughput (kbps) = 8 x (10MB download1+ …+10MB download15) / (1000 x downloading time (s)) per UE.

Average user throughput (kbps) = (avgUE1+avgUE2+…+avgUE6) / number of UEs





Offered Cell Load (kbps) = (total downloaded bits / total measurement time x 1000)

Total downloaded bits = Total downloaded bits from all UEs (15 ftp download x 6 UEs x 10MB x 8).

Total measurement time (s) = Duration time from the start of the first ftp download to the end of the last ftp download for all UEs

Test Cases

Avg UE1 Tput (kbps)

Avg UE2 Tput (kbps)

Avg UE3 Tput (kbps)

Avg UE4 Tput (kbps)

Avg UE5Tput (kbps)

Avg UE6 Tput (kbps)

AvgUserTput (kbps)

OfferedCellLoad (kbps)

MC 28235 21557 28360 27244 28992 26930 26886 11393

SC (F1) 15302 15814 17153

SC (F2) 16232 14415 15038

15659 10960

8 Troubleshooting

8.1 Code verification

Verify if 15 Hs-Pdsch codes are available.

If you don’t get 15 HsPdsch codes after you have set parameters maxNumHsPdschCodes, numHsScchCodes and numEhichErgchCodes to recommended values, see TC1, do as follow:

1. Confirm parameters settings.

In this example the cell is called RBS-CallCenterA

RNCxxx > lget cellname codes ===============================================================

MO Attribute Value===============================================================





UtranCell=RBS-CallCenterA,Hsdsch=1 numHsPdschCodes 14UtranCell=RBS-CallCenterA,Hsdsch=1 numHsScchCodes 1UtranCell=RBS-CallCenterA,Hsdsch=1,Eul=1 numEagchCodes 1UtranCell=RBS-CallCenterA,Hsdsch=1,Eul=1 numEhichErgchCodes 1

===============================================================

RBSxxx> lget . maxNumHsPdschCodes

==========================================================================MO Attribute Value=========================================================================RbsLocalCell= RBS-CallCenterA maxNumHsPdschCodes 15

===============================================================

2. Verify that the numbers of codes are set correctly for every parameter.

3. Print the code tree usage for the cell.

RNCxxx> lhsh xxxxxx codetree -cid xxx.OrRNCxxx> lhsh xxxxxx codetree -cid xxx -full.

RNCxx> lhsh “board ” codetree -cid “cid”

To find the right board number, do as follow:

Find out what Module, MOD, the site is configured to,RNCxx> str1

Printout-------------------------------------------------------------------------------------------------------MOD IUBLINK CELLNAMES ------------------------------------------------------------------------------------------------------- 11 Iub_Site_CallCenter RBS-CallCenter-A/B/C

In this example Module number 11.

Find the board number with this commandRNCxx> bp mod

Printout

===============================================================================================





Board BoardType Mod SwAllocation/DevType BoardGroups===============================================================================================001400 GPB53 1 GPB_Module aal2ap aal2cpsrc aal2ncc 001500 GPB53 13 GPB_Module aal2ap aal2cpsrc aal2ncc 001600 GPB53 8 GPB_Module aal2ap aal2cpsrc aal2ncc 011200 GPB53 9 GPB_Module aal2ap aal2cpsrc aal2ncc 011300 GPB53 2 GPB_Module aal2ap aal2cpsrc aal2ncc 011400 GPB53 3 GPB_Module aal2ap aal2cpsrc aal2ncc 011500 GPB53 4 GPB_Module aal2ap aal2cpsrc aal2ncc 011600 GPB53 15 GPB_Module aal2ap aal2cpsrc aal2ncc 011700 GPB53 10 GPB_Module aal2ap aal2cpsrc aal2ncc 021200 GPB53 11 GPB_Module aal2ap aal2cpsrc aal2ncc 021300 GPB53 5 GPB_Module aal2ap aal2cpsrc aal2ncc 021400 GPB53 6 GPB_Module aal2ap aal2cpsrc aal2ncc 021500 GPB53 7 GPB_Module aal2ap aal2cpsrc aal2ncc 021600 GPB53 25 GPB_Module aal2ap aal2cpsrc aal2ncc 021700 GPB53 12 GPB_Module aal2ap aal2cpsrc aal2ncc ===============================================================================================

Cid is found by this command:RNCxx> lget RBS-CallCenterA cid

==========================================================================MO Attribute Value==========================================================================UtranCell=RBS-CallCenterA cId 20171==========================================================================Total: 1 MOs

Now we can check the code tree usage RNCxx> lhsh 021200 codetree -cid 20171

$ lhsh 021200 codetree -cid 20171Code tree usage for cell with cid 20171, cellFroId 2 sf free blocked allocated 4 0 4 0 8 2 6 0 16 1 1 14 32 9 23 0 64 19 44 1128 39 85 4256 79 172 5

If the printout doesn’t show the number of allocated code equal to numHsPdschCodes =14 and number of blocked code equal to 1, without any traffic in the cell the code tree is fragmented. To re-allocate the codes, block and





de-block the MO: RncFunction=1,UtranCell= xx,Hsdsch=hsdschxx,Eul=eulxx

Use command lst to get the proxy for concerned MO.

lst utrancell.= RBS-CallCentreA

080825-16:53:11 172.31.98.101 7.1 RNC_NODE_MODEL_K_6_0_COMPLETE stopfile=/tmp/23257===================================================================================Proxy Adm State Op. State MO=================================================================================== 2476 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA 2478 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Fach=1 2481 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Rach=1 2482 0 (LOCKED) 0 (DISABLED) RncFunction=1,UtranCell=RBS-CallCentreA,MbmsCch=1 2483 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Hsdsch=12484 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Hsdsch=1,Eul=1

2485 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Pch=1===================================================================================Total: 7 MOs

RNCxx>bl 2484 RNCxx>deb 2484

If there is traffic in cell the number of blocked codes will be more than 1.See printout below.

$ lhsh 021200 codetree -cid 20171Code tree usage for cell with cid 20171, cellFroId 2: sf free blocked allocated 4 0 4 0 8 2 6 0 16 0 2 14 32 9 23 0 64 19 44 1128 39 85 4256 79 172 5

In this case traffic should be released to get blocked codes = 1.

4. Verify that the cell is UNLOCKED and ENABLED

lst utrancell.= RBS-CallCentreA

080825-16:53:11 172.31.98.101 7.1 RNC_NODE_MODEL_K_6_0_COMPLETE stopfile=/tmp/23257===================================================================================Proxy Adm State Op. State MO=================================================================================== 2476 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA 2478 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Fach=1





2481 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Rach=1 2482 0 (LOCKED) 0 (DISABLED) RncFunction=1,UtranCell=RBS-CallCentreA,MbmsCch=1 2483 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Hsdsch=12484 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Hsdsch=1,Eul=1

2485 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=RBS-CallCentreA,Pch=1===================================================================================Total: 7 MOs

8.2 CQI Improvements

The HS throughput is determined by the size of the Transport BlockSize (TBS) transmitted per TTI. The TBS size is determined by the value of the achievable signal quality in the UE, RxQualAchivable, through a hard-coded lookup table. The RxQualAchivable is calculated based on the adjusted normalized CQI and the available HS power. RxQualAchievable = CQIadjusted + (PPDSCH - (PCPICH_TX + )) [dB].

To reach a throughput of 42Mbps the reported CQI need to be high, close to 30, to benefit from the increase of the normalized CQI, normCqi64Qam see table below.

Consider the two cases below how to reach a CQI of 30

In case a high CQI is not achievable Start to increase parameter hsMeasurementPowerOffset in step of 10 units (1 dB) until CQI reaches 30. You might also have to increase the CPICH power 1-2 dB to increase and get more stable CQI. If you get CQI around 30, but still throughput not reach above 40 Mbps the reason might be lack of available HS /RBS power.





In case a high CQI is achievedIf you don’t get the TBS size of 39984 or higher with a CQI value of 30 and BLER and DTX are around zero it seems that the HS connection is power limited. To increase the RxQualAchievable and the TBS size do as follow:

Reduce the parameter hsMeasurementPowerOffset in step of 10 units (1 dB) with the CQI and BLER maintained at 30 respectively 0 and observe the TBS and HS-DSCH throughput until you can notice a slightlylower CQI value. Now you should have got a higher TBS size and with that higher throughput. If not then the RBS has reached it’s maximum power utilization (i.e. lack of RBS power).

8.3 IRAT Consideration

If during downloading observed event 2d is triggered, this will affect the available power for HS due to compressed mode and consequently reduces throughput for HS. In such a case, the threshold level for HS RAB (UeRc =25) needs to be modified. Change serviceOffset2dEcno and serviceOffset2dRscp to avoid compressed mode for HS RAB.

8.4 RBS SuperTrace

Super Trace can be used to understand why Dl throughput doesn’t reach expected level

Trace activation

RBS3000

Activate following traces on TX board and run it on a file

lh tx6 te e trace1 trace2 trace3 HSSR3_SCHED_RBS_SUPER_TRACElh tx6 te e trace1 trace2 trace3 HSSR4_SCHED_RBS_SUPER_TRACE

lh tx6 te filter set "LEN <>48" HSSR3_SCHED_RBS_SUPER_TRACElh tx6 te filter set "LEN <>48" HSSR4_SCHED_RBS_SUPER_TRACE

lh tx6 te e trace2 HSSR3_FLClh tx6 te e trace2 HSSR4_FLC

RBS6000

Activate following traces on TX board and run it on a file





te e trace1 trace2 trace3 HSSR16896_SCHED_RBS_SUPER_TRACEte e trace1 trace2 trace3 HSSR16384_SCHED_RBS_SUPER_TRACEte e trace1 trace2 trace3 HSSR15872_SCHED_RBS_SUPER_TRACE

te filter set "LEN <>48" HSSR16896_SCHED_RBS_SUPER_TRACEte filter set "LEN <>48" HSSR16384_SCHED_RBS_SUPER_TRACEte filter set "LEN <>48" HSSR16384_SCHED_RBS_SUPER_TRACE

9 References

1. CPI documentation

2. RBS 6000 Transport Solutionhttp://anon.ericsson.se/eridoc/component/eriurl?docno=EAB-10:032227Uen&objectId=09004cff83d31548&action=approved&format=ppt8

10 Appendix

The trial instruction is based on Ericsson recommended parameter setting. Deviation is listed below and in each test case.

http://anon.ericsson.se/eridoc/component/eriurl?docno=EAB-10:032227Uen&objectId=09004cff83d31548&action=approved&format=ppt8

http://anon.ericsson.se/eridoc/component/eriurl?docno=EAB-10:032227Uen&objectId=09004cff83d31548&action=approved&format=ppt8





10.1 Parameter List

MO Class Name Parameter Name Node

NodeBFunction licenseStateHsdpaMc RBS ENABLED

RbsLocalCell featureStateHsdpaMc RBS ACTIVATED

NodeBFunction licenseState64QAM RBS ENABLED

NodeBFunction featureState64QAM RBS ACTIVATED

NodeBFunction licenseStateEnhancedLayer2 RBS ENABLED

RbsLocalCell featureStateEnhancedLayer2 RBS ACTIVATED

NodeBFunction licenseStateHsdpaDynamicCodeAllocation

RBS ENABLED

RbsLocalCell featureStateHsdpaDynamicCodeAllocation

RBS ACTIVATED

NodeBFunction licenseStateEnhancedUplinkIntroduction

RBS ENABLED

NodeBFunction licenseStateHsdpaFlexibleScheduler RBS ENABLED

NodeBFunction featureStateHsdpaFlexibleScheduler RBS ACTIVATED

IubDataStreams maxHsRate RBS 1000

Eul numEhichErgchCodes RNC 1

Hsdsch numHsScchCodes RNC 1

Hsdsch maxNumHsPdschCodes RBS 15

Hsdsch numHsPdschCodes RNC 14

Hsdsch hsMeasurementPowerOffset RNC 80

carrier hsPowerMargin RBS 1

carrier cqiAdjustmentOn RBS False

Utrancell sf32Adm RNC 0



Utrancell sf16gAdm RNC 0

Utrancell pwrAdm RNC 75





Utrancell pwrOffset RNC 15

QoSMaxBitrateDownlinkIu SGSN 48000

QoSMaxBitrateUplinkIu SGSN 8640

10.2 Code Tree Usage

Figure 6 shows code tree usage for common channels and one EUL/HS user.

Figure 6 - Code Tree Usage

10.3 Activation PDP Context Accept message

The content of “Activation PDP Context Accept” layer 3 message could be used to identify the allowed up and down link throughput for a given SIM.

42 MBPS DL - DC HSDPA TRIAL

Technology

Transcript of 42 MBPS DL - DC HSDPA TRIAL