pm89563 - enhanced layer 2 for uplink - feature assessment orf foa - may 2014 - v1

7/23/2019 PM89563 - Enhanced Layer 2 for Uplink - Feature Assessment ORF FOA - May 2014 - V1

http://slidepdf.com/reader/full/pm89563-enhanced-layer-2-for-uplink-feature-assessment-orf-foa-may-2014 1/44

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

PM89563 – ENHANCED LAYER 2 FOR UPLINKFeature Assessment – ORF FOA

MGR / TIPS / NEA / Wireless Features & PerformanceMay 2014 – Version 01.01



3


ENHANCED LAYER 2 FOR UPLINK FEATURE ASSESSMENT

1 | FEATURE OVERVIEW AND ACT IVAT ION STRATEGY



4


FEATURE OVERVIEW

Until LR13.3.W, the PDU size in uplink is fixed and this results in a reduced system performance due to unnecessary se

padding, overhead and Layer 2 processing.

The root of the problem is that a fixed PDU size is incapable of being adaptive to the dynamic of both imposed IP packvary a lot for different services) and available transport block space.

To overcome the limitations of fixed PDU size the 3GPP standardization body has introduced, in Release 8, a new featu2 for uplink – similar to its downlink counterpart in Release 7. This feature introduces a flexible RLC PDU size, a new Mand possible segmentation in RLC and/or MAC layers.

As per TS25.322, if flexible RLC PDU size is configured, the maximum size of the data field of the RLC PDU is 1503 octsize with flexible RLC solution can be as large as an IP packet, which is typically 1500 bytes, plus up to 3 bytes for PDC

In LR13.3.W enhanced layer 2 for uplink is applicable to HSPA users in Cell_DCH state.

It is possible to activate enhanced Layer 2 for uplink feature independently of enhanced Cell_FACH in uplink. This is do

objective of achieving a throughput gain on xCEM, that does not support the LR14.2.W feature. In the beginning, the nsupporting enhanced Cell_FACH in uplink is expected to be fairly low, but these may still benefit from MAC-i/is in Cell_



5


FEATURE BENEFITS

The advantages of using this feature are obtainable for the service provider and also for the end user/subscriber. The

attainable:

• Minimisation of unnecessary segmentation, padding, overhead and Layer 2 processing, associated to previously fixe

• Potential for higher throughput and improved user experience, as more processing resources will be available for th

with the reduced processing on UE side.

• Higher granularity available for uplink scheduling to better utilise dynamic physical resources (2 to 1505 bytes, ada

of IP packet sizes, very small to very large).

• In later software releases, this feature will enable Dual Cell HSUPA and further improve the throughput performanc

This feature can be considered as a spectrum efficiency booster: for a wireless communication system with a given po

enhanced Layer 2 for uplink (flexible RLC) will improve the spectrum efficiency.



6


MAC-I/IS CONCEPTS

A new Medium Access Control entity, MAC-i/is is introduced and it can be used as an alternative to MAC-e/es.

Both MAC-e/es and MAC-i/is are responsible for handling the data transmitted on E-DCH and managing the physical reE-DCH. Upper layers configure which of the two entities, MAC-e/es or MAC-i/is, should be applied to handle E-DCH traE-DCH functionality. The MAC-d entity has a connection to the MAC-e/es or MAC-i/is entity. This connection is used toE-DCH transport channel.

The main differences between MAC-i/is and MAC-e/es include:

• MAC-e/es and MAC-i/is headers are different.

• Using MAC-i/is the RLC PDUs may have different sizes (flexible RLC).

• There is a segmentation/reassembly function in MAC-i/is (MAC-i/is SDU may be segmented and sent in different TT

Basically, in the same way as downlink MAC-ehs, MAC-i/is allows the support of flexible RLC PDU sizes and segmentatifunction.

For each UE in CELL_DCH that uses E-DCH, one MAC-i (or MAC-e) entity per Node B and one MAC-is (or MAC-es) entity iconfigured on UTRAN side:

• MAC-i (/-e) in NodeB controls access to E-DCH, and serves MAC-is (/-es) in SRNC.

• MAC-is (/-es) further connects to MAC-d (one transport bearer per E-DCH MAC-d flow.



7


SELECTION OF MAC-I/IS AND FLEXIBLE RLC

The selection between Release 8 MAC-i/is and Release 6 MAC-e/es (i.e. to decide which entity is used to manage E-DC

the following events:

• RAB assignment on E-DCH.

• SRNS incoming relocation with UE involved.

• E-DCH mobility, depending on the target cell capabilities for inter-RNC soft handover, with Iur.

• DCH to E-DCH reconfiguration.

• Always-On upsize to E-DCH (RRC state transition to Cell_DCH).

• Update of MAC-i/is capability in the serving cell (NBAP RESOURCE STATUS INDICATION or AUDIT RESPONSE).

• RRC re-establishment in current or new cell.

When MAC-i/is has been selected, flexible RLC mode is chosen on a per radio bearer basis, indicated in several RRC m

RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION and RADIO BEARER RELEASE (‘RB Mapping Info’ IE‘Choice R

to “Flexible Size”):

• PS I/B radio bearers are always configured in flexible mode to achieve higher throughput (fixed RLC PDU size limits

and causes unnecessary segmentation, padding, overhead and layer 2 processing.

• Other radio bearers will be configured in fixed mode, either to avoid reconfigurations or because they don’t use UL



8


SUMMARY OF FLEXIBLE RLC AND MAC-I/IS CONFIGURATIONS IN UE AND N

The following sums up the conditions for configuration of flexible RLC and MAC-i/is:

• If the UE indicates that it is MAC-i/is capable, it also supports flexible RLC.

• If the Node B indicates that it is flexible size capable, it also supports MAC-i/is.

• MAC-i/is configuration is done per UE, according to UE and Node B capabilities.

• Flexible RLC is configured on a per radio bearer basis, according to service type and UE / Node B capability to supp

MAC-i/is.

• Flexible RLC needs MAC-i/is, but MAC-i/is can work either with fixed or flexible RLC.



9


ACTIVATION STRATEGY AND PARAMETER SETTINGS

Enhanced Layer 2 for Uplink feature was activated on 28/Apr at 12:23PM, in ORLEANSV1 RNC, with the following para

In order to perform the FTP testing in Chateauroux the feature was deactivated at 08:54PM on 6/May and reactivated

following day.

Parameter Object Description

isMaci isAl lowed RadioAccessService Activation flag at RNC level.

is7Bit LiAlwaysUsedForUlRlcFlexibl eMode EdchRncConf

Activation flag to force the use of 7 bits length indicator, regardless o

PDU size. When set to False, the RNC can dynamically set the length ibits or 15 bits), based on the maximum RLC PDU size. When set to Tr

indicator is statically used, independently of the RLC PDU size. The a7 bit length indicator size is to prevent RLC reestablishment during re

from fixed to flexible RLC mode.

isRlcFlexi bleSizeForPsSt rAll owed EdchRncConf Activation flag for the use of UL RLC flexible mode for PS streaming r

maciisMaximumPduSizePsIb EdchRncConf Maximum RLC PDU size allowed for PS I/B radio bearers.

macii sMaxim umPduSizePsSt r EdchRncConf Maximum RLC PDU size allowed for PS streaming radio bearers.

maciisMinimumPduSizePsIb EdchRncConf Minimum RLC PDU size allowed for PS I/B radio bearers.

macii sMinimumPduSizePsSt r EdchRncConf Minimum RLC PDU size allowed for PS streaming radio bearers.

maxMaciPduCont ent sSizeFor NonScheduledModeT t i2 EdchParameters Maximum number of bits per MAC-i PDU for non-scheduled transmissiomaxMaciPduCont ent sSizeFor NonScheduledModeT t i10 EdchParameters Maximum number of bits per MAC-i PDU for non-scheduled transmissio

isEdchFpBundlingModeForEdchTt i2msAllowed NodeBConfClass

Specifies if the NodeB shall bundle the E-DCH FP frame of 2ms into an

10ms, when a RAB is mapped on E-DCH. This parameter already existsis updated, to reflect the fact that it is only applicable to MAC-e/es c

isMaci isAl lowed FDDCell Activation flag at cell level.

isMaci isAl lowed NeighbouringRNC Activation flag at neighbouring RNC level.

isMaci isAl lowed RemoteFDDCell Activation flag at remote cell level.



10



2 | TEST ACT IVIT IES



11


FEATURE SPECIFIC LAB/LIVE TESTS AND STATUS (1/4)

The table below lists the feature specific tests performed on lab and live network, with the final outcome of each one

Test ID Test Name Location Status Comments

1 Check Feature Activation on WIPS Lab / Live PassedActivate feature on RNC NORTELRN1 in all FDDCell. Check errors O

FDDCell to avoid inconsistencies.

2 Check Feature Activation on OAM Lab / Live Passed

Activate feature on RNC NORTELRN1 in all FDDCell. Check featu

Bearer Setup (Flexible RLC PDU Size). Check If UE support MACRequest (supportOfMACiis OPTIONAL = 1), RRC Connection Setup C

= true).

3

Verify BTS support of MAC-i/is

capability by checking Audit

procedure on BTS after reset of BTS

Lab PassedReset BTS Equipment. Audit Response Message contains EDCH-M

flexibleSizeCapable (1).

4Check RSI after Lock/Unlock of

FDDCell of BTSLab Passed

Lock/unlock 1 BTS/FDDCell. RSI Message contains NBAP ResourceMACdPDU-SizeCapability: flexibleSizeCapable

5Check provisioning of

maciisMaximumPduSizePsIb for PS

IB call

Lab PassedRRC Message: Largest RLC PDU Size = 1503 which is related to pay

equal to Payload + 2 = 1505 due to PDCP pres

6

Check provisioning ofmaciisMinimumPduSizePsIb for PS

IB callLab Passed

RRC Message: Min RLC PDU Size = 0 which is related to payload. T

to Payload + 2 = 2 due to PDCP presence

7Check provisioning of

maci isMaxi mumPduSizePsSt r for

PS Streaming call

Lab N/A There is a restriction on ALU PS Streaming on H

8

Check provisioning ofmacii sMinimumPduSizePsSt r for PS

Streaming callLab N/A There is a restriction on ALU PS Streaming on H



12





9Softer HO EDCH(MAC-i/is 2ms) to

EDCH(MAC-i/is 2ms)Lab Passed CEV1_9 MAC-i/is 2ms TTI CEV1_11 MAC-i/is 2ms TTI CEV

10Softer HO EDCH(MAC-i/is 10ms) to

EDCH(MAC-i/is 10ms)Lab Passed CEV1_9 MAC-i/is 10ms TTI CEV1_11 MAC-i/is 10ms TTI CE

11Soft HO EDCH(MAC-i/is 2ms) to

EDCH(MAC-i/is 2ms)Lab Passed CEV1_9 MAC-i/is 2ms TTI CEV10_7 MAC-i/is 2ms TTI CEV

12Soft HO EDCH(MAC-i/is 10ms) to

EDCH(MAC-i/is 10ms)Lab Passed CEV1_9 MAC-i/is 10ms TTI CEV10_7 MAC-i/is 10ms TTI CE

13HHO DCH(MAC-i/is 2ms) to

EDCH(MAC-i/is 2ms) Inter-RNC

(feature activated on both RNC)

Lab N/A No 2nd RNC LR13.3 available.

14

HHO DCH(MAC-i/is 2ms) to

EDCH(MAC-i/is 2ms) Inter-RNC(feature activated on only one RNC)

Lab Passed Mobility HHO from RNC1 CEV1_0 MAC-i/is to RNC3 CEV7_1 (MACover DCH (SF4x2) to RNC1 CEV1_0.

15IFHHO Intra NB EDCH(MAC-i/is 2ms)

to EDCH(MAC-i/is 2ms)Lab Passed

IFHHO performed between CEV1_8_5 to CEV1_9. In the Radio Link mACd-PDU-Size-List {mACdPDU-Size 1505

16IFHHO Inter NB EDCH(MAC-i/is 2ms)

to EDCH(MAC-i/is 2ms)Lab Passed

IFHHO performed between MBI5_5 (not congested) to SmartComSetup: e-DCH-DDI-Value 0, mACd-PDU-Size-List {mACdP

17Always On EDCH(MAC-i/is 2ms) toCell_FACH to EDCH(MAC-i/is 2ms)

Lab Passed Cell_DCH MAC-i/is 2ms TTI Cell_FACH Cell_DCH M

18Always On EDCH(MAC-i/is 10ms) toCell_FACH to EDCH(MAC-i/is 10ms)

Lab Passed Cell_DCH MAC-i/is 10ms TTI Cell_FACH Cell_DCH M



13





19Always On EDCH(MAC-i/is 2ms) to

URA_PCH to EDCH(MAC-i/is 2ms)Lab N/A Cell_PCH / URA_PCH not activated.

20Always On EDCH(MAC-i/is 10ms) toURA_PCH to EDCH(MAC-i/is 10ms)

Lab N/A Cell_PCH / URA_PCH not activated.

21

Always On EDCH(MAC-i/is 2ms) to

URA_PCH to EDCH(MAC-i/is 2ms)Direct Upsize


22Always On EDCH(MAC-i/is 10ms) toURA_PCH to EDCH(MAC-i/is 10ms)

Direct Upsize


23

SRNS Relocation UE not involved

EDCH(MAC-i/is 2ms) to EDCH(MAC-i/is 2ms) (feature activated on both

RNC)

Lab N/A No second RNC in LR13.3 available.

24

SRNS Relocation UE not involved

EDCH(MAC-i/is 2ms) to EDCH(MAC-

i/is 2ms) (feature activated on onlyone RNC)

Lab Not executable SRNS Relocation not available.

253G2G Inter-RAT HO with EDCH(MAC-

i/is_2ms)Lab Passed 2G Cell CI_35_LAC 24_BCCH 874 CEV1_9 2ms TT

26Check EDCH 2ms throughput for

fixed vs. flexible PDU sizeLab Passed

Flexible PDU Size: 3.36Mbit/s. Fixed PDU Size: 3.

8% improvement.



14





27Check EDCH 10ms throughput for

fixed vs. flexible PDU sizeLab Passed

Flexible PDU Size: 1.89Mbit/s. Fixed PDU Size: 1.

7% improvement.

28

Check Counter

VS_RAB_MeanCellDCH_PS_EDCH_Ma

c_iis

Lab / Live PassedOnce the activation of counters was done, they are pegged, accord

during the validation tests.

29Check Counter

VS_MacIisReconfigurationsLab / Live Passed

Once the activation of counters was done, they are pegged, accord


30Check Counter

VS_UlRlcFlexibleSizeUsedLab / Live Passed

Once the activation of counters was done, they are pegged, accord


31Check if MAC-i/is is set for multiple

RAB PS+PSLab Passed

First PDP APN “hsdpa”, Radio Bearer Setup with MAC-i/is 2msTTIRadio Bearer Setup with MAC-i/is.

32

Check if MAC-i/is is set for multiple

RAB CS+PS Lab Passed Setup PS traffic, 2ms TTI MAC-i/is and add CS call. Radio Beare



15


ENDURANCE LAB/LIVE TESTS AND STATUS

The table below lists the endurance tests performed on lab and live network, with the final outcome of each one:

Test ID Test Name Priority Location Status C

1 Static: FTP Transfer 1MB UL 1 Lab PassedUE: Qualcomm MSM

Average Th


Average Th


Average Th

4 Static: FTP Transfer 5MB DL 1 Lab PassedUE: Qualcomm MSM

Average Th

5 Static: FTP Transfer 20MB DL 1 Lab PassedUE: Qualcomm MSM

Average Th

6 Static: FTP Transfer 1MB UL Good Radio Conditions 1 Live Passed

See

“Feature Per

7 Static: FTP Transfer 1MB UL Poor Radio Conditions 1 Live Passed

8 Static: FTP Transfer 5MB DL Good Radio Conditions 1 Live Passed

9 Static: FTP Transfer 5MB DL Poor Radio Conditions 1 Live Passed

10 Mobility: FTP Transfer 1MB UL 1 Live Passed

11 Mobility: FTP Transfer 5MB DL 1 Live Passed



16



3 | FEATURE PERFORMANCE EVALUAT ION



17


FTP TESTING IN CHATEAUROUX – PROTOCOL AND DATA ANALYSIS

The FTP testing on the live network, corresponding to endurance tests 6 to 11, was performed in Chateauroux on 7/Ma

The ideal timing and location for the testing was decided based on the average number of bearers on sites CHATEAUR

CHATEAUROUX_ST_DENIS, CHTX_GENDARMERIE and CHTX_ROCHAT. As seen in the charts below, the lowest traffic was

CHTX_ROCHAT between 2AM and 6AM, so this was the selected Node B and time interval for the static FTP tests.

The static testing procedure consisted in 10 successive uploads of a 1MB file and 10 downloads of a 5MB file, performe

to filter out variations in the results due, for instance, the call being affected by other users in the cell, the top 3 res

considered in the calculation of the average throughput.

For mobility no such filtering was applied and all the data transfers were considered for each drive. The file sizes used

in uploads and 5MB in downloads.

0

0.2

0.4

0.6

0.8

1

1.2

1.4

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 : 0 0

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 : 0 0

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 : 0 0

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 : 0 0

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1-May 2-May 3-May 4-May 5-May

VS_UlAsConfIdAvgNbrEstablished_UlAsCnfHsupa2msTTI_Avg(U1667_21_Avg)

CHATEAUR OU X_DEOLS CHATEAUR OU X_S T_DENI S

CHTX_GENDARMERIE CHTX_ROCHAT

0

0.05

0.1

0.15

0.2

0.25

0.3

0.35

0.4

0.45

0.5

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 : 0 0

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 : 0 0

0 : 0 0

2 : 0 0

4 : 0 0

6 : 0 0

8 : 0 0

1 0 : 0 0

1 2 : 0 0

1 4 : 0 0

1 6 : 0 0

1 8 : 0 0

2 0 : 0 0

2 2 0 0

1-May 2-May 3-May

VS_UlAsConfIdAvgNbrEstablished_UlAsCnfH

CHATEAUR OU X_DEOLS CH

CHTX_GENDARMERIE CHT



18


FTP TESTING IN CHATEAUROUX – TESTING LOCATIONS (1/2)

Two static locations were used, one under very good radio

conditions and another one with average to poor radio conditions.

The test location with very good radio conditions was approximately

at 150m from the site CHTX_ROCHAT, with line of sight to the

antennas. The average RSCP and Ec/No measured were -58dBm and-3dB, respectively.

The location for performing the testing under average to poor radio

conditions (within the coverage area of the same cell) was

approximately 400m from the site CHTX_ROCHAT, shadowed by

some houses and trees. The average RSCP and Ec/No measured were

–87dBm and -7dB, respectively.

The CDF distribution for RSCP and Ec/No in both locations is shown

on the right.

The mobility tests were done in a predefined route covering the

main roads and streets in Deols and Chateauroux.

The next slide includes the locations used.

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

- 9 5

- 9 4

- 9 3

- 9 2

- 9 1

- 9 0

- 8 9

- 8 8

- 8 7

- 8 6

- 8 5

- 8 4

- 8 3

- 8 2

- 8 1

- 8 0

- 7 9

- 7 8

- 7 7

- 7 6

- 7 5

- 7 4

- 7 3

- 7 2

- 7 1

- 7 0

- 6 9

- 6 8

- 6 7

RSCP Distribution (CD

G ood R adi o Condi ti ons

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

- 1

1

- 1 0 . 5

- 1

0

- 9 . 5 - 9

- 8 . 5 - 8

- 7 . 5 - 7

- 6 . 5 - 6

- 5 . 5 - 5

Ec/No Distribution (CD

G ood R adi o Condi ti ons



19


FTP TESTING IN CHATEAUROUX – TESTING LOCATIONS (2/2)

Testing Location (Good RF)

Testing Location (Average / Poor RF)



20


FTP TESTING IN CHATEAUROUX – STATIC GOOD RADIO CONDITIONS

The table and charts in this slide summarize the throughput values

of the top 3 results for FTP transfers of a 1MB file in uplink and a

5MB file in downlink in static, with good radio conditions.

It is possible to see an improvement in the average throughput for

the uplink data transfers, while for the downlink the average

throughput value is practically the same for both configurations,

with and without the feature activated.

This is in line with the expectations, although a higher benefit

would be expected while static and under very good radio

conditions. The next slide goes over some further analysis using

larger file sizes and taking into consideration the achieved

application throughput for the maximum ETFCI.

3040

3060

3080

3100

3120

3140

3160

3180

3200

3220

3240

Test 1 Test 2

App Throughput (Kbps) - FT

Feature On Feature Off

11400

11420

11440

11460

11480

11500

11520

11540

11560

11580

11600

11620

Test 1 Test 2



Static TestsGood RF

FTP UL 1MB (Kbps) FTP DL 5MB (Kbps)

Feature ON Feature OFF Feature ON Feature OFF

Test 1 3229.71 3170.83 11557.35 11590.94

Test 2 3194.89 3108.00 11544.01 11474.47

Test 3 3178.39 3108.00 11484.35 11467.89

Average 3201.00 3128.94 11528.57 11511.10

Delta +2.30% +0.15%



21


FTP TESTING IN CHATEAUROUX – ETFCI AND APPLICATION THROUGHPUT

With low traffic on the network and very few Enhanced Layer 2

capable users in the cell, the main feature benefits should be seen

at UE throughput level, with the most increase visible at maximum

rate.

To verify this, the value of the application throughput was extracted

from the UE log files, when ETFCI = 96, the maximum format

combination used by the UE, as seen in the chart on the right (only a

single transfer shown).

The idea is then to compare the application throughput distribution

between the two configurations (feature activated and feature

deactivated) when the maximum resources are available to the UE.

0

10

20

30

4050

60

70

80

90

100

2 5 : 3 9 . 1

2 5 : 4 3 . 4

2 5 : 4 5 . 9

2 5 : 4 6 . 3

2 5 : 4 6 . 7

2 5 : 4 7 . 1

2 5 : 4 7 . 5

2 5 : 4 7 . 9

2 5 : 4 8 . 3

2 5 : 4 8 . 7

2 5 : 4 9 . 1

2 5 : 4 9 . 5

2 5 : 4 9 . 9

2 5 : 5 0 . 3

2 5 : 5 0 . 7

2 5 : 5 1 . 1

2 5 : 5 1 . 5

2 5 : 5 1 . 9

2 5 : 5 2 . 3

2 5 5 2 7

Qualcomm HSUPA E-DPCH_

The charts in the next slide present the several cumulative distribution functions for the application throughput, for 1

transfers of 1MB, 5MB and 10MB files, in the location with good radio conditions. The table at the bottom left documenobtained for the 50%-ile of each distribution.

Comparing the several values, it is possible to see that the improvements achieved when the feature is activated are i

simulation expectations and test bed results.

FTP TESTING IN CHATEAUROUX ETFCI AND APPLICATION THROUGHPUT



22


FTP TESTING IN CHATEAUROUX – ETFCI AND APPLICATION THROUGHPUT

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

2 0 0

0

2 1 0

0

2 2 0

0

2 3 0

0

2 4 0

0

2 5 0

0

2 6 0

0

2 7 0

0

2 8 0

0

2 9 0

0

3 0 0

0

3 1 0

0

3 2 0

0

3 3 0

0

3 4 0

0

3 5 0

0

Throughput FTP UL 10M

F eature On Feat

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

2 0 0 0

2 1 0 0

2 2 0 0

2 3 0 0

2 4 0 0

2 5 0 0

2 6 0 0

2 7 0 0

2 8 0 0

2 9 0 0

3 0 0 0

3 1 0 0

3 2 0 0

3 3 0 0

3 4 0 0

3 5 0 0

Threoughput FTP UL 5M

F eature On Fea

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

2 0 0 0

2 1 0 0

2 2 0 0

2 3 0 0

2 4 0 0

2 5 0 0

2 6 0 0

2 7 0 0

2 8 0 0

2 9 0 0

3 0 0 0

3 1 0 0

3 2 0 0

3 3 0 0

3 4 0 0

3 5 0 0

3 6 0 0

3 7 0 0

3 8 0 0

3 9 0 0

4 0 0 0

4 1 0 0

4 2 0 0

4 3 0 0

4 4 0 0

4 5 0 0

Throughput FTP UL 1MB (kbps) - ETFCI = 96

Feature On F eature Off

Static TestsETFCI = 96(Good RadioConditions)

FTP UL (Kbps) 50%-ile

Feature ON Feature OFF Delta

1MB 3833.55 3639.74 +5.32%

5MB 3830.40 3624.96 +5.67%

10MB 3837.57 3577.22 +7.28%

FTP TESTING IN CHATEAUROUX STATIC AVERAGE / POOR RADIO CONDIT



23


FTP TESTING IN CHATEAUROUX – STATIC AVERAGE / POOR RADIO CONDIT

The table and charts in this slide summarize the throughput values

of the top 3 results for FTP transfers of a 1MB file in uplink and a

5MB file in downlink in static, with average / poor radio conditions.

Once again the downlink average throughput is very close for both

configurations, with and without the feature activated.

For the uplink the gain decreases slightly, as it is normal that the

eventual gain coming from MAC-i/is and flexible RLC is masked by

throughput fluctuations normally seen when the radio conditions

are average at most.2450

2500

2550

2600

2650

2700

2750

2800

Test 1 Test 2



10000

10050

10100

10150

10200

10250

10300

10350

10400

Test 1 Test 2



Static TestsPoor RF



Test 1 2771.04 2772.00 10341.26 10230.18

Test 2 2685.46 2589.83 10178.12 10224.95

Test 3 2623.81 2583.98 10139.42 10211.90

Average 2693.44 2648.60 10219.60 10222.34

Delta +1.69% -0.03%

FTP TESTING IN CHATEAUROUX MOBILITY



24


FTP TESTING IN CHATEAUROUX – MOBILITY

The table below summarizes the results obtained during the

mobility tests for FTP upload and download, respectively of 1MB

and 5MB files.

There is a greater variation in these results, when compared to the

static tests.

The overall radio conditions were quite similar in all drives. The

charts on the right show the distribution of RSCP and Ec/No for the

drive tests performed with the feature on and off. It is possible to

see that the 50%-ile is quite similar in both cases, differing by 2dB

for the RSCP and by 1dB for the Ec/No.

So, the larger difference between the results may be attributable

not just to the enhancements introduced by the feature but also to

a possible difference in traffic profile and number of users in the

four Node Bs used in the complete route.

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

- 1 0 0

- 9 9

- 9 8

- 9 7

- 9 6

- 9 5

- 9 4

- 9 3

- 9 2

- 9 1

- 9 0

- 8 9

- 8 8

- 8 7

- 8 6

- 8 5

- 8 4

- 8 3

- 8 2

- 8 1

- 8 0

- 7 9

- 7 8

- 7 7

- 7 6

- 7 5

- 7 4

- 7 3

- 7 2

- 7 1

- 7 0

- 6 9

- 6 8

- 6 7

- 6 6

RSCP Distribution (CDF)

Feature On

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

- 2 4

. 0

- 2 3

. 5

- 2 3

. 0

- 2 2

. 5

- 2 2

. 0

- 2 1

. 5

- 2 1

. 0

- 2 0

. 5

- 2 0

. 0

- 1 9

. 5

- 1 9

. 0

- 1 8

. 5

- 1 8

. 0

- 1 7

. 5

- 1 7

. 0

- 1 6

. 5

- 1 6

. 0

- 1 5

. 5

- 1 5

. 0

- 1 4

. 5

- 1 4

. 0

- 1 3

. 5

- 1 3

. 0

- 1 2

. 5

- 1 2

. 0

- 1 1

. 5

- 1 1

. 0

- 1 0

. 5

- 1 0

. 0

9

5

Ec/No Distribution (CDF

Feature On

MobilityTests



Average 2331.68 2071.33 9111.31 8941.16

Delta +12.57% +1.89%

FEATURE SPECIFIC COUNTERS HSUPA RABS USING MAC I/IS



25


FEATURE SPECIFIC COUNTERS – HSUPA RABS USING MAC-I/IS

The chart on the top left shows the average and maximum number

of bearers in the RNC that are using MAC-i/is with flexible PDU size.Per day, we have an average of 2 users with such a RAB established,

in the entire RNC. The maximum number is less than 40.

When looking at the global figures for EDCH average number of

bearers (chart on the top right) it is clear that the penetration of

Enhanced L2 for Uplink capable UEs is quite low, between 0.2% and

0.3%. This is in line with previous analysis done based on CTg (as per

February 2014), that indicated approximately 0.4% of capable UEs,

as shown in the bottom chart on the right.

0

5

10

15

20

25

30

35

40

0

0.5

1

1.5

2

2.5

3

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

ORLEANSV1

VS_RAB_MeanCellDCH_PS_EDCH_Mac_iis_Max(U1409_Max)(Event)

VS_RAB_MeanCellDCH_PS_EDCH_Mac_iis_Avg(U1409_Avg)(Event)

Feature ON

99.5%

99.6%

99.7%

99.8%

99.9%

100.0%

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

ORLEANSV1

VS_RAB_MeanCellDCH_PS_Bgrd_EDCH_HSDSCH_Avg

VS_RAB_MeanCellDCH_PS_Intact_EDCH_HSDSCH_Av

VS_RAB_MeanCellDCH_PS_EDCH_Mac_iis_Avg(U140

Feature ON

2.41%

15.37%

11.81%

1.74%1

0%

2%

4%

6%

8%

10%

12%

14%

16%

18%

R7_R8+FDPCH

R7_R8+eFDPCH

R7_R8 +DPCCH DTX

eFACH DL R7 eDRX

ORLEANSV1 UE Capabilit

FEATURE SPECIFIC COUNTERS MAC I/IS RECONFIGURATIONS



26


FEATURE SPECIFIC COUNTERS – MAC-I/IS RECONFIGURATIONS

0

10000

20000

30000

40000

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

ORLEANSV1

VS_MacIisReconfigurations_MACcInCellFachToMACiEdchInCellDch(U1410_5)(Event)

VS_MacIisReconfigurations_MACdDchToMaciEdch(U1410_3)(Event)

VS_MacIisReconfigurations_MACeToMACi(U1410_0)(Event)

VS_MacIisReconfigurations_MACiEdchInCellDchToMACcInCellFACH(U1410_4)(Event)

VS_MacIisReconfigurations_MACiEdchToMACdDch(U1410_2)(Event)

Feature ON

0

20

40

60

80

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 M

ORLEANSV1

VS_MacIisReconfigurations_MACdDchToMaciEdch

VS_MacIisReconfigurations_MACeToMACi(U1410

VS_MacIisReconfigurations_MACiEdchToMACdDc

VS_MacIisReconfigurations_MACiToMACe(U1410

Feature ON

The charts above show the number of successful reconfigurations between MAC-i/is and other MAC entities (MAC-c, MA

It is clear that the transitions between Cell_DCH (MAC-i/s) and Cell_FACH (MAC-c) are dominant, with just a few occureconfigurations.

Since the feature must be activated in all cells within the RNC, reconfigurations between MAC-i/is and MAC-e/es are o

in case of mobility over Iur or in case of loss of MAC-i/is capability. It is interesting to notice that on the day of activat

occurrences of MAC-i/is to MAC-e/es reconfigurations, probably related to the activation procedure, during which cell

capabilities are coexisting in the RNC.

Reconfigurations to MAC-d should happen in case of reconfigurations triggered by fallbacks or (not so probable) in case

e/es capabilities are lost simultaneously.

FEATURE SPECIFIC COUNTERS DISTRIBUTION OF UL RLC PDU SIZES



27


FEATURE SPECIFIC COUNTERS – DISTRIBUTION OF UL RLC PDU SIZES

97.5%

98.0%

98.5%

99.0%

99.5%

100.0%

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

ORLEANSV1

VS_UlRlcFl exibleSizeUsed_RlcPdu2To42(U1411_0)(Event) VS_UlRlcFl exib

VS_UlRlcFl exibleSizeUsed_RlcPdu83To123(U1411_2)(Event) VS_UlRlcFl exib

VS_UlRlcFl exibleSizeUsed_RlcPdu323to642(U1411_4)(Event) VS_UlRlcFl exib

Feature ONThe chart in this slide shows the distribution of the uplink RLC PDU

size for the radio bearers that use flexible RLC mode.

There is a clear dominance of the PDU sizes between 2 and 42

bytes (336 bits), which should be determined by the uplink call

profile in PS, normally more associated to short PDUs for

acknowledgments of HSDPA traffic. More than 98% of the PDUs is

336 bits long or less.

These results confirm the higher granularity that is now available

for the uplink scheduler to better utilise the dynamic physical

resources, adaptive to a wide range of IP packet sizes.

MAC-i/is supports segmentation, which means the UE can make use

of a lower ETFCI compared to MAC-e/es, which is particularly useful in case the UE is power limited.

With MAC-e/es and fixed PDU size of 336 bits the minimum ETFCI the UE can use to carry TRB traffic is 3, with a Powe

(power offset from DPCCH power level).

With MAC-i/is, a PDU can be of any size and therefore the UE can select ETFCI = 1 to send a minimum of 186 bits of da

requires 3dB less power compared to ETFCI = 3 (2.1dB power offset instead of 5.1dB), which gives the UE an extra 3dB

transmit data.

This is useful in the busy hours when more UEs are power limited due to high uplink load. In simulations this had a pos

reducing the number of TCP timeouts.




28



4 | NON-REGRESSION INDICATORS

GENERAL COMMENTS ON NON-REGRESSION ANALYSIS



29


GENERAL COMMENTS ON NON-REGRESSION ANALYSIS

As seen in the previous section, the penetration of the Enhanced Layer 2 for Uplink capable UEs is very low, so it woul

to see an effect on the main non-regression indicators.

The next slides go over the main indicators on accessibility, retainability, mobility, throughput, traffic and quality dom

On the same date of feature activation, site ST_MARCEL was heavily degraded, with the performance recovered on 5/

uncorrelated to any activities related to Enhanced Layer 2 for Uplink feature activation, deactivation or testing. As suanalysis in ORLEANSV1 RNC is done excluding this Node B.

NON-REGRESSION INDICATORS – ACCESSIBILITY CS



30


NON REGRESSION INDICATORS ACCESSIBILITY CS

The evolution of the call setup success rate for CS was not

influenced by the feature activation. There is a big decrease on1/May, but this should likely be related to the holiday and the

start of the long weekend.

The reported values for the RRC connection success rate and RAB

assignment success rate also remain within the same limits seen

before feature activation.

0

50000

100000

150000

200000

250000

300000

350000

400000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

OZ_IUB_ORLEANSV1_without_

FirstRRCConnectionRequest_RRC015_CR_Cs(U

FirstRRCConnectionSuccessRate_RRC013_CR_C

Feature ON

98.8%

98.9%

99.%

99.1%

99.2%

99.3%

99.4%

99.5%

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y

OZ_IUB_ORLEANSV1_without_ST_MARCEL (110)

CallSetupSuccessRateCS_CSSR006_C(UCSSR006_C)(%)

Feature ON

0

50000

100000

150000

200000

250000

300000

350000400000

450000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 M a y


RABEstablishmentRequestsPerRABType_RAB013_C_C

RABEstablishmentSuccessRatePerRequestedRAB_RAB

Feature ON

NON-REGRESSION INDICATORS – ACCESSIBILITY PS



31


NON REGRESSION INDICATORS ACCESSIBILITY PS

As for CS, the call setup rate for PS is not affected by the feature

activation. There is again a decrease on 1/May, but not as evidentas for CS or the one seen for 21/Apr.

The reported values for the RRC connection success rate and RAB

assignment success rate also remain within the same limits seen

before feature activation, although for the latter there seems to

be a slight decrease after 30/Apr, not correlated to any feature

activities.

99.3%

99.35%

99.4%

99.45%

99.5%

99.55%

99.6%

99.65%

99.7%

99.75%

99.8%

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


CallSetupSuccessRatePS_CSSR007_C(UCS…

Feature ON

0

2000000

4000000

6000000

8000000

10000000

12000000

14000000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y


FirstRRCConnectionRequest_RRC015_CR_Ps(U

FirstRRCConnectionSuccessRate_RRC013_CR_P

Feature ON

0

2000000

4000000

6000000

8000000

10000000

12000000

14000000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y


RABEstablishmentRequestsPerRABType_RAB013_C_P

RABEstablishmentSuccessRatePerRequestedRAB_RAB

Feature ON

NON-REGRESSION INDICATORS – RETAINABILITY CS



32


NON REGRESSION INDICATORS RETAINABILITY CS

The CS call drop rate does not change visibly after feature activation, with a similar number of dropped connections.

on 1/May, which coincides with the beginning of the long weekend, but overall the variations are within the range seeactivation.

The distribution of the causes for the Iu abnormal release requests in the CS domain is not changed either, with the m

‘Radio Connection With UE Lost’, ‘Failure in the Radio Interface Procedure’, ‘DL RLC Unrecoverable Error on SRB’ and

0.55%

0.6%

0.65%

0.7%

0.75%

0.8%

0.85%

0

500

1000

1500

2000

2500

3000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


IuAbnormalReleaseRequest_IU008_C_Cs(UIU008_C_Cs)(Event)

CallDropRate_IU006_C_Cs(UIU006_C_Cs)(%)

Feature ON

0

5000

10000

15000

20000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M

a y

2 - M

a y

3 - M

a y

4 - M

a y


VS_IuReleaseReqCs_AbnormalConditionTimerRelocExpiry(VS_IuReleaseReqCs_ConnectionWithNodeBLost(U576_1VS_IuReleaseReqCs_DlRLCErrSRB(U576_7)(Event)VS_IuReleaseReqCs_FailureInTheRadioInterfaceProceduVS_IuReleaseReqCs_OtherCause(U576_6)(Event)VS_IuReleaseReqCs_RadioConnectionWithUeLost(U576_4VS_IuReleaseReqCs_ReleaseDueToUtranGeneratedReasonVS_IuReleaseReqCs_RepeatedIntegrityCheckFailure(U57VS_IuReleaseReqCs_T360Expiry(U576_9)(Event)VS_IuReleaseReqCs_UeGeneratedSignallingConnectionRelVS_IuReleaseReqCs_UlRLCErrSRB(U576_8)(Event)VS_IuReleaseReqCs_UnspecifiedFailure(U576_1)(Event)

Feature ON

NON-REGRESSION INDICATORS – RETAINABILITY PS



33


NON REGRESSION INDICATORS RETAINABILITY PS

0.8%

0.9%

1.%

1.1%

1.2%

1.3%

1.4%

1.5%

0

20000

40000

60000

80000

100000

120000

140000

160000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


IuAbnormalReleaseRequest_IU008_C_Ps(UIU008_C_Ps)(Event)

Feature ON

0

50000

100000

150000

200000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y


VS_IuReleaseReqPs_CellReselFail(U599_19)(Event)VS_IuReleaseReqPs_DlRLCErrSRB(U599_8)(Event)VS_IuReleaseReqPs_DlRLCErrTRB(U599_10)(Event)VS_IuReleaseReqPs_FailureInTheRadioInterfaceProceduVS_IuReleaseReqPs_RadioCnxUeLost(U599_6)(Event)VS_IuReleaseReqPs_ReleaseDueToUtranGeneratedReasoVS_IuReleaseReqPs_RelocationTriggered(U599_22)(EveVS_IuReleaseReqPs_UlRLCErrSRB(U599_9)(Event)VS_IuReleaseReqPs_UlRLCErrTRB(U599_11)(Event)VS_IuReleaseReqPs_UnspecifiedFailure(U599_3)(Event

Feature ON

The CS call drop rate does not change visibly after feature activation, with a similar number of dropped connections.

after 1/May, and some higher values until 4/May, throughout the long weekend, but this is more influenced by the trafeature related activities.

The distribution of the causes for the Iu abnormal release requests in the PS domain is not changed either, with the m

RLC Unrecoverable Error on SRB’, ‘Release due to UTRAN Generated Reason’ and ‘Radio Connection With UE Lost’.

NON-REGRESSION INDICATORS – HSUPA MOBILITY INTRA-FREQUENCY



34


Q

For the intra-frequency mobility between E-DCH capable cells,

there is no visible effect from the feature activation. Both attemptsand success rate remain within the previously reported ranges.

For the mobility from E-DCH to non E-DCH capable cells, it is

possible to see a big variation on the success rate and number of

attempts on 2/May, so not related to any feature activities.

The success rate for mobility between non E-DCH and E-DCH

capable cells remains with similar values as the ones seen after

25/April, prior to feature activation.

99.5%

99.55%

99.6%

99.65%

99.7%

99.75%

99.8%

99.85%

0

200000

400000

600000

800000

1000000

1200000

1400000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


HSUPAMobilitySuccess_HSUPA016_CR_ItaFeDCHeDCH(UHSUPA016_CR_ItaFeDCHeDCH)(Event)

HSUPAMobilityUnsuccess_HSUPA017_CR_ItaFeDCHeDCH(UHSUPA017_CR_ItaFeDCHeDCH)(Event)

HSUPAMobilitySuccessRate_HSUPA001_CR_intraFeDCHeDCH(UHSUPA001_CR_ItaFeDCHeDCH)(%)

Feature ON

0

500

1000

1500

2000

2500

3000

3500

4000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 M a y


HSUPAMobilitySuccess_HSUPA016_CR_ItaFeDCHneDCH(UHSUP

HSUPAMobilityUnsuccess_HSUPA017_CR_ItaFeDCHneDCH(UHS

HSUPAMobilitySuccessRate_HSUPA001_CR_intraFeDCHneDCH(

Feature ON

0

2000

4000

6000

8000

10000

12000

14000

16000

18000

20000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y


HSUPAMobilitySuccess_HSUPA016_CR_ItaFneDCHeDCH(UHSUP

HSUPAMobilityUnsuccess_HSUPA017_CR_ItaFneDCHeDCH(UHS

HSUPAMobilitySuccessRate_HSUPA001_CR_intraFneDCHeDCH(U

Feature ON

NON-REGRESSION INDICATORS – HSUPA MOBILITY INTER-FREQUENCY



35


Q

Considering the number of attempts, only the mobility between E-

DCH capable cells and from non E-DCH to E-DCH cells is relevant interms of overall system performance. The latter does not change,

although the number of attempts decreases after 2/May.

The number of attempts and success rate for the mobility between

E-DCH capable cells visible decreases shortly after feature

activation. However, it is possible to see that this happens on

29/Apr, and not at the time of feature activation. This is related to

two Work Orders, not related to this feature, activated on this date

at 2PM-3PM timeframe. The big variation happens at this instant.

95.%

95.5%

96.%96.5%

97.%

97.5%

98.%

98.5%

99.%

99.5%

0

1000

2000

3000

4000

5000

6000

7000

8000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


HSUPAMobilitySuccess_HSUPA016_CR_ItrFeDCHeDCH(UHSUPA016_CR_ItrFeDCHeDCH)(Event)

HSUPAMobilityUnsuccess_HSUPA017_CR_ItrFeDCHeDCH(UHSUPA017_CR_ItrFeDCHeDCH)(Event)

HSUPAMobilitySuccessRate_HSUPA001_CR_interFeDCHeDCH(UHSUPA001_CR_ItrFeDCHeDCH)(%)

Feature ON

0

100

200

300

400

500

600

700

800

900

1000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 M a y


HSUPAMobilitySuccess_HSUPA016_CR_ItrFneDCHeDCH(UHSUPA

HSUPAMobilityUnsuccess_HSUPA017_CR_ItrFneDCHeDCH(UHSUHSUPAMobilitySuccessRate_HSUPA001_CR_interFneDCHeDCH(

Feature ON

0

50

100

150

200

250

300

350

400

450

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 : 0 0

1 3 : 0 0

1 4 : 0 0

1 5 : 0 0

1 6 : 0 0

1 7 : 0 0

1 8 : 0 0

1 9 : 0 0

2 0 : 0 0

2 1 : 0 0

2 2 : 0 0

2 3 : 0 0

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 : 0 0

1 3 : 0 0

1 4 : 0 0

1 5 : 0 0

1 6 : 0 0

1 7 : 0 0

1 8 : 0 0

1 9 : 0 0

2 0 : 0 0

2 1 : 0 0

2 2 : 0 0

2 3 : 0 0

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 0 0

27-Apr 28-Apr 29-A


HSUPAMobilitySuccess_HSUPA016_CR_ItrFeDCHeDC

Feature ON

NON-REGRESSION INDICATORS – THROUGHPUT HSDPA



36


There is no visible influence on the HSDPA throughput per user and per cell.

The main variation is seen on 30/Apr, but this is not related to any feature related activities.

2100

2150

2200

2250

2300

2350

2400

2450

2500

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


AvgDLThroughputPerUser_HSDPA093_CR(UHSDPA093_CR)(Kbps)

Feature ON

2950

3000

3050

31003150

3200

3250

3300

3350

3400

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y


HSDPAcellthroughput_HSDPA035_C

Feature ON

NON-REGRESSION INDICATORS – THROUGHPUT HSUPA



37


There is not a visible variation on the E-DCH cell and user throughput, either for 2ms and 10ms TTI.

Some oscillations are visible but their range is within the limits seen prior to feature activation.

50

70

90

110

130

150

170

190

210

230

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


AvgULThroughputPerUser_HSUPA009_CR_10ms(UHSUPA009_CR_10ms)(nb)

AvgULThroughputPerUser_HSUPA009_CR_2ms(UHSUPA009_CR_2ms)(nb)

Feature ON

60

80

100

120140

160

180

200

220

240

260

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y


E_DCHMAC_eCellThroughputWithoutRetransmissions_HSUPA015_

E_DCHMAC_eCellThroughputWithoutRetransmissions_HSUPA015_

Feature ON

NON-REGRESSION INDICATORS – E-DCH HARQ BLER



38


As for the inter-frequency E-DCH mobility, there is a change in the indicator behaviour, shortly after feature activation

on HARQ BLER starts on 29/Apr and the indicator reaches its final value on 30/Apr. As such, there is the same suspicio

again caused by the two Work Orders application.

The chart on the right shows that the main variation occurs again on 29/Apr after 2PM, coincident with the Work Orde

So, it is possible to conclude that the variations are not related to the activation of feature PM89563.

37.0%

38.0%

39.0%

40.0%

41.0%

42.0%

43.0%

44.0%

45.0%

46.0%

0

100000000

200000000

300000000

400000000

500000000

600000000

700000000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


EdchHarqRetransmissions_HSUPA024_CR(UHSUPA024_CR)(Event)

EdchHARQBler1stRtx_HSUPA021_CR(UHSUPA021_CR)(%)

Feature ON

0

5000000

10000000

15000000

20000000

25000000

30000000

35000000

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 : 0 0

1 3 : 0 0

1 4 : 0 0

1 5 : 0 0

1 6 : 0 0

1 7 : 0 0

1 8 : 0 0

1 9 : 0 0

2 0 : 0 0

2 1 : 0 0

2 2 : 0 0

2 3 : 0 0

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 : 0 0

1 3 : 0 0

1 4 : 0 0

1 5 : 0 0

1 6 : 0 0

1 7 : 0 0

1 8 : 0 0

1 9 : 0 0

2 0 : 0 0

2 1 : 0 0

2 2 : 0 0

2 3 : 0 0

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 : 0 0

1 3 : 0 0

1 4 : 0 0

1 5 : 0 0

27-Apr 28-Apr 29-Apr


EdchHarqRetransmissions_HSU PA024_CR(UHEdchHARQBler1stRtx_HSUPA021_CR(UHSUPA

Feature ON

NON-REGRESSION INDICATORS – UL RSSI



39


There is no major variation on the average UL RSSI on the day of

the feature activation. On 29/Apr there is a very slight increase,

by after 3/May the values are again close to the reference.

The maximum UL RSSI is within the normal range on the date of

activation, but on 29/Apr the value increases. However, one must

take into consideration that this indicator is based on the MAX

instance of a load counter, so a single sample is enough to have a

higher value for this indicator. For instance, on 29/Apr, there is a

single hour that stands out, as throughout the day the values are

within the same range as seen for 28/Apr.

-106

-105

-104

-103

-102

-101

-100

-99

-98

-97

-96

-95

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


UplinkRSSI_ULOAD002_CR_Avg(UULOAD002_CR_Avg)(dBm)

Feature ON

-65

-63

-61

-59

-57

-55

-53

-51

-49

-47

-45

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y


UplinkRSSI_ULOAD002_CR_Max(UULOAD00

Feature ON

-85

-80

-75

-70

-65

-60

-55

-50

-45

0 : 0 0

1 : 0 0

2 : 0 0

3 : 0 0

4 : 0 0

5 : 0 0

6 : 0 0

7 : 0 0

8 : 0 0

9 : 0 0

1 0 : 0 0

1 1 : 0 0

1 2 : 0 0

1 3 : 0 0

1 4 : 0 0

UplinkRSSI_ULOAD002_CR_Max(UULOAD002_CR_Ma

28-Apr 29-Apr

NON-REGRESSION INDICATORS – HSXPA FALLBACK



40


The number of attempts for fallback from HSxPA to DCH has the

same evolution as prior to feature activation. The success rate is

also comparable. As such, there is no real influence from the

feature in these indicators. The proportion of HSxPA remains the

same (less than 0.1%).

As for the fallback from 2ms TTI to 10ms TTI, there are some days

with lower values post feature activation, but this seems more

related to the traffic profile (two “short” weeks). The values on

15/May seem to recover to the original values seen in April.

0

100

200

300

400

500

600

700

800

900

1000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y


HsdpaToDchFallbackSuccess_HSDPA047_C_HsdpaDch(UHSDP

HsdpaToDchFallbackUnsuccess_HSDPA048_C_HsdpaDch(UHS

Feature ON

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

10000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


HsdpaToDchFallbackSuccess_HSDPA047_C_HsdpaEdch(UHSDPA047_C_HsdpaEdch)(Event)

HsdpaToDchFallbackUnsuccess_HSDPA048_C_HsdpaEdch(UHSDPA048_C_HsdpaEdch)(Event)

Feature ON

0

10000

20000

30000

40000

50000

60000

70000

80000

90000

100000

1

7 - A p r

1

8 - A p r

1

9 - A p r

2

0 - A p r

2

1 - A p r

2

2 - A p r

2

3 - A p r

2

4 - A p r

2

5 - A p r

2

6 - A p r

2

7 - A p r

2

8 - A p r

2

9 - A p r

3

0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y


VS_Edch2msTtiTo10msTtiF allbackSuccess(U2895)(Event) VS_Edch2msTti

Feature ON

NON-REGRESSION INDICATORS - TRAFFIC



41


Traffic indicators (Kbyte volume in uplink and downlink) remain constant, with similar values throughout the period of

prevalence of speech and E-DCH/HSDPA.

There are some periods with a slightly lower traffic, for instance the long weekend from 1/May to 4/May.

0

250000000

500000000

750000000

1E+09

1.25E+09

1.5E+09

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y

4 - M a y

5 - M a y

6 - M a y

7 - M a y

8 - M a y

9 - M a y

1 0 - M a y

1 1 - M a y

1 2 - M a y

1 3 - M a y

1 4 - M a y

1 5 - M a y


VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabCsData64(U1556_3)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabCsSpeech(U1556_2)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabHsdpa(U1556_5)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabOther(U1556_0)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb128(U1556_14)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb384(U1556_16)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb64(U1556_13)(Kbytes)VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabSRB(U1556_1)(Kbytes)

Feature ON

0

50000000

100000000

150000000

200000000

1 7 - A p r

1 8 - A p r

1 9 - A p r

2 0 - A p r

2 1 - A p r

2 2 - A p r

2 3 - A p r

2 4 - A p r

2 5 - A p r

2 6 - A p r

2 7 - A p r

2 8 - A p r

2 9 - A p r

3 0 - A p r

1 - M a y

2 - M a y

3 - M a y


VS_Dedic atedUplinkKbytesRlcReferenceCell_UlRabCsDatVS_DedicatedUplinkKbytesRlcReferenceCell_UlRabCsSpeecVS_DedicatedUplinkKbytesRlcReferenceCell_UlRabHsupa(UVS_DedicatedUplinkKbytesRlcReferenceCell_UlRabOther(UVS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb128VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb32(VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb384VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb64(VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabSRB(U1

Feature ON




42


5 | CONCLUSIONS

FEATURE BEHAVIOUR AND PERFORMANCE



43


After activation of the Enhanced Layer 2 for Uplink feature, it is possible to conclude that the feature works as design

There is no effect from the feature activation on the non-regression indicators, which is expected, considering the low

UEs supporting the feature.

The set of tests on both testbed and live network were passed, with the feature allowing a higher uplink throughut in

mobility scenarios.

The improvements measured for the maximum throughput (with E-TFCI = 96) are in line with simulation results showin

pm89563 - enhanced layer 2 for uplink - feature assessment orf foa - may 2014 - v1

Documents