You are on page 1of 44

New Features September

10
Benchmarking 2013

The Vodacom CEO improvement project was a three weeks joint venture
of Huawei and Vodacom where Huawei improved the network
performance in three weeks. New features were part of the project and it
includes all the 2G and 3G new features that were implemented on this
project.
New Features Benchmarking

Table of Contents
3G FEATURES ................................................................................................................................ 6
1 Control Channel Parallel Interference Cancellation (Phase 2) .................................................. 6

1.1.1 DESCRIPTION ............................................................................................................ 6

1.1.2 BENEFIT: .................................................................................................................... 6

1.1.3 Trail result .................................................................................................................... 7

1.1.4 Further Action .............................................................................................................. 8

2 CE OVERBOOKING ............................................................................................................... 8

2.1.1 DESCRIPTION ............................................................................................................ 8

2.1.2 BENEFIT ..................................................................................................................... 9

2.1.3 Trail result .................................................................................................................. 10

2.1.4 Further Action ............................................................................................................ 11

3 CID ALLOCATION ALGORITHM ...................................................................................... 11

3.1.1 DESCRIPTION .......................................................................................................... 11

3.1.2 Trail result .................................................................................................................. 11

3.1.3 Further Action ............................................................................................................ 12

4 Adaptive Adjustment of HSUPA Small Target Retransmissions ........................................... 13

4.1.1 DESCRIPTION .......................................................................................................... 13

4.1.2 BENEFIT ................................................................................................................... 14

4.1.3 Trail result .................................................................................................................. 14

4.1.4 Further Action ............................................................................................................ 15

5 CQI Feedback Period Optimization ........................................................................................ 15

5.1.1 DESCRIPTION .......................................................................................................... 15

5.1.2 BENEFIT ................................................................................................................... 16

5.1.3 Trail result .................................................................................................................. 16

2013-9-10 New Features Benchmarking Page 2of 44


New Features Benchmarking

5.1.4 Further Action ............................................................................................................ 17

6 Load-based BLER configuration for R99 ............................................................................... 18

6.1.1 DESCRIPTION .......................................................................................................... 18

6.1.2 BENEFIT ................................................................................................................... 18

6.1.3 Trail result .................................................................................................................. 18

6.1.4 Further Action ............................................................................................................ 19

7 P2D transitions when CS services is triggered........................................................................ 19

7.1.1 DESCRIPTION .......................................................................................................... 19

7.1.2 BENEFIT ................................................................................................................... 20

7.1.3 Trail result .................................................................................................................. 20

7.1.4 Further Action ............................................................................................................ 21

8 Power Code Balance ............................................................................................................... 21

8.1.1 Description: ................................................................................................................ 21

8.1.2 Benefit: ....................................................................................................................... 21

8.1.3 Trail result .................................................................................................................. 21

8.1.4 Further Action ............................................................................................................ 22

9 CQI Adjustment Based on Dynamic BLER Target ................................................................ 22

9.1.1 Description ................................................................................................................. 22

9.1.2 Benefit: ....................................................................................................................... 23

10 Dynamic Configuration of HSDPA CQI Feedback Period ..................................................... 23

10.1.1 DESCRIPTION...................................................................................................... 23

10.1.2 BENEFIT ............................................................................................................... 24

10.1.3 Trail result .............................................................................................................. 24

10.1.4 Further Action ........................................................................................................ 25

11 Dynamic Target RoT Adjustment ........................................................................................... 26

2013-9-10 New Features Benchmarking Page 3of 44


New Features Benchmarking

11.1.1 DESCRIPTION...................................................................................................... 26

11.1.2 BENEFIT ............................................................................................................... 27

11.1.3 Trail result .............................................................................................................. 27

11.1.4 Further Action ........................................................................................................ 28

12 Enhanced Fast Dormancy ....................................................................................................... 28

12.1.1 DESCRIPTION...................................................................................................... 28

12.1.2 BENEFIT ............................................................................................................... 30

12.1.3 Trail result .............................................................................................................. 30

12.1.4 Further Action ........................................................................................................ 32

13 MULTIRAB OPTIMIZATION .............................................................................................. 32

13.1.1 Background ............................................................................................................ 32

13.1.2 Recommendation ................................................................................................... 32

13.1.3 Results .................................................................................................................... 33

13.1.4 Future Actions ........................................................................................................ 33

2G FEATURES .............................................................................................................................. 33
14 PDCH Busy Threshold............................................................................................................ 34

14.1.1 DESCRIPTION...................................................................................................... 34

14.1.2 BENEFIT ............................................................................................................... 34

14.1.3 Conclusion: ............................................................................................................ 34

15 Active TBF Allocation ............................................................................................................ 39

15.1.1 DESCRIPTION...................................................................................................... 39

15.1.2 BENEFIT ............................................................................................................... 39

15.1.3 Conclusion: ............................................................................................................ 40

16 Voice Quality Indicator ........................................................................................................... 40

16.1.1 DESCRIPTION...................................................................................................... 40

2013-9-10 New Features Benchmarking Page 4of 44


New Features Benchmarking

16.1.2 BENEFIT ............................................................................................................... 42

16.1.3 Conclusion: ............................................................................................................ 43

2013-9-10 New Features Benchmarking Page 5of 44


New Features Benchmarking

3G FEATURES
Following tables illustrates the brief details of New Features trialed in CEO Network
Quality Improvement Project

1 Control Channel Parallel Interference Cancellation (Phase 2)

1.1.1 DESCRIPTION

CCPIC is implemented for NodeB to regenerate signals of UEs on their respective


DPCCHs based on information, and cancel the interference on the regenerated
DPCCH signals by subtracting the regenerated DPCCH signals of all UEs carried on the
same CCPIC-capable board from the total received signals.
After the interference from the DPCCH is canceled, the DPDCH and E-DPDCH are
demodulated. This reduces interference from the DPCCH to other channels,
improving demodulation performance of the other channels.
CCPIC (Phase 2) introduces the advanced regeneration cancellation algorithm, which
makes DPCCH regeneration more accurate and improves CCPIC efficiency as a result.

1.1.2 BENEFIT:

This feature significantly increases the uplink system capacity. When the DPCCH uses
a large proportion of received total wideband power (RTWP) in a cell, this feature

2013-9-10 New Features Benchmarking Page 6of 44


New Features Benchmarking

increases system capacity by up to 20%. This gain is possible when, for example, the
uplink throughput is not high but there are a large number of UEs in the cell.

1.1.3 Trail result

This feature was implemented on 3G_JM07_JMY_SGS, 2013-8-21, 11:30AM.

0.2-0.3dB improvement on cell level after interference cancellation

Only 32 sites with WBBPd or WBBPf can support CCPIC phase2.


From these 32 sites, traffic increased a lot, no improvement can be seen.

RTWP increased due to traffic growth.

2013-9-10 New Features Benchmarking Page 7of 44


New Features Benchmarking

From RNC level, theres no obvious improvement by now.

1.1.4 Further Action

Need to trail on another RNC.

2 CE OVERBOOKING

2.1.1 DESCRIPTION

After Dynamic CE Resource Management is applied, the RNC calculates the credit
resource usage of an admitted HSUPA UE by using the following formula:
Credit resource usage = Max (Credit resources required for ensuring the GBR, Credit
resources required for transmitting one RLC PDU)
RNC performs this calculation to ensure HSUPA user experience. However, Because
the NodeB calculates the actual CE usage based on the UE rate which is lower than
the GBR or the rate at which an RLC PDU is transmitted in most cases due to the high
penetration rate of smart phones with a 2 ms HSUPA transmission time interval (TTI),
2013-9-10 New Features Benchmarking Page 8of 44
New Features Benchmarking

the actual CE usage of the NodeB is lower than the calculated credit resource usage
of the RNC. As a result, the RNC may reject new UE access attempts even if the
actual CE usage of the NodeB is low. This limits the RNC's capability to perform
admission control based on credit resource usage.
To address this issue, Huawei introduces CE Overbooking in which the NodeB
calculates the actual CE usage of admitted UEs, includes the calculated CE usage in a
private information element (IE) in a measurement report, and sends the report to
the RNC every measurement report period. The RNC then directly uses the reported
CE usage as the credit resource usage

2.1.2 BENEFIT

This maximizes the RNC's capability to perform admission control based on credit
resource usage.
When the penetration rate of smart phones with a 2ms HSUPA TTI is high, the
average HSUPA service throughput is low, and this feature provides the following
benefits:
Reduces the credit resource usage of admitted UEs.
Increases the number of admitted UEs and the number of HSUPA UEs with a
2ms TTI.
Increases cell uplink throughput when Uu and Iub resources are sufficient.

2013-9-10 New Features Benchmarking Page 9of 44


New Features Benchmarking

2.1.3 Trail result

Implemented on 3G_JM09_JMY_SGS, 3G_JM14_MTE_SGS, 3G_JF05_JFL_SGS and


3G_JF04_JFL_SGS, 2013-8-19, 09:30AM

RAB failures due to UL CE congestion are solved.

CE congestion related event issue solved.

CE utilization is stable.

2013-9-10 New Features Benchmarking Page 10of 44


New Features Benchmarking

2.1.4 Further Action

Already being rolled out

3 CID ALLOCATION ALGORITHM

3.1.1 DESCRIPTION

ALGO1 - RNC allocates the smallest available CID for an AAL2 path whose ownership
is local and allocates the biggest available CID for an AAL2 path whose ownership is
peer. This is available since R14 software.
ALGO2 - RNC allocates the available CIDs from 8 to 255 in succession for an AAL2
path whose ownership is local, and then restarts the allocation, starting from 8 again;
and the RNC allocates the available CIDs from 255 to 8 in succession for an AAL2
path whose ownership is peer, and then restarts the allocation, starting from 255
again.

3.1.2 Trail result

The result is positive. The CID confliction problem disappears after applying ALGO1.
The IUR between MT07 and MT01 was improved very much on Aug-27. The
abnormal CID is caused by IUR inter-failing starting from Aug-28 due to TX.

2013-9-10 New Features Benchmarking Page 11of 44


New Features Benchmarking

3.1.3 Further Action

Recommend to rollout for all IURs based on ATM transmission.

2013-9-10 New Features Benchmarking Page 12of 44


New Features Benchmarking

4 Adaptive Adjustment of HSUPA Small Target Retransmissions

4.1.1 DESCRIPTION

The hybrid automatic repeat request (HARQ) entity for High Speed Uplink Packet
Access (HSUPA) is located on the NodeB side and used to receive MAC-e protocol
data units (PDUs). When a cell cannot correctly receive MAC-e PDUs from a UE, the
HARQ entity requires the UE to retransmit MAC-e PDUs. The average number of
retransmissions on the NodeB side needs to converge to a target number of
retransmissions on the RNC side. This target number on the RNC side is dynamically
adjusted by the feature HSUPA Adaptive Retransmission.
With the HSUPA adaptive retransmission feature, a small target number of
retransmission is used under normal circumstances. When the uplink load or the UE
transmit power is limited, one UE is selected to use a large target number of
retransmissions during each period. Without this feature, a small target number of
retransmission is always used. For details about the HSUPA adaptive retransmission
feature, see HSUPA Feature Parameter Description.
In versions earlier than RAN14.0, the small target number of retransmissions is
specified by the EdchTargetLittleRetransNum parameter and cannot be adaptively
adjusted. When the uplink load is limited, a small target number of retransmissions
will require a high signal-to-interference ratio (SIR) on the Dedicated Physical Control
Channel (DPCCH), and the DPCCH must have a higher power. This leads to decreased
available power on the Enhanced Dedicated Channel (E-DCH) and Enhanced
Dedicated Physical Data Channel (E-DPDCH), a lower UE throughput, and a lower cell
throughput. To address these problems, RAN14.0 introduced the feature Adaptive
Adjustment of HSUPA Small Target Retransmissions. This feature supports an
alternative small target number of retransmissions for each typical type of service.
The actual small target number of retransmissions can dynamically shift between the
original fixed number and the alternative number based on the cell uplink load and
UE rates, which are configured by the EdchTargetLittleRetransNum and
EdchAltTarLittleRetransNum parameters, respectively. This improves the system
capacity when the uplink load is limited.
Figure 5- shows the relationship between the features HSUPA Adaptive
Retransmission and Adaptive Adjustment of HSUPA Small Target Retransmissions.
With the HSUPA Adaptive Retransmission feature, only one UE is selected to use the
large target number of retransmissions during each period. With the Adaptive
Adjustment of HSUPA Small Target Retransmissions feature, when the uplink load is
limited, multiple UEs are selected for adjustment to the small target number of
retransmissions. This further improves the cell throughput.

2013-9-10 New Features Benchmarking Page 13of 44


New Features Benchmarking

4.1.2 BENEFIT

This feature improves the uplink performance. It is recommended that this feature
be enabled if the uplink load of the cell is restricted and there are a large number of
HSUPA UEs using a 10 ms TTI. If some UEs in the cell are engaged in continuous
uploading, this feature improves the uplink throughput by 10% to 15%. If all services
in the cell are burst services, this feature lowers the RTWP by around 0.5 dB.

4.1.3 Trail result

This feature was implemented on 3G_RO15_PRS_NGA, 2013-8-30, 09:20AM.

RTWP on 31st August is lower than 24th August, but traffic is also decreased.
Besides, RTWP of RO15 was on a good level, hardly to get improvement.

2013-9-10 New Features Benchmarking Page 14of 44


New Features Benchmarking

No improvement on HSUPA throughput per UE.

4.1.4 Further Action

Need to trail on another RNC.

5 CQI Feedback Period Optimization

5.1.1 DESCRIPTION

CQI (Channel Quality Indicator) measures the channel conditions of a UE and is


reported from the UE to the NodeB. The NodeB determines an appropriate TBS
based on the reported CQI, system resources, and the TFRC policy.
With the PS traffic growth, more and more HSDPA connections are active in 3G
network. HSDPA uplink feedback channel HS-DPCCH generated a big part of uplink
interference which limits the uplink capacity and HSUPA throughput as well.

2013-9-10 New Features Benchmarking Page 15of 44


New Features Benchmarking

To improve uplink performance, its recommended to optimize CQI feedback period


according to network situation. Currently, CQI feedback period is set to 4ms, can be
optimized to 8ms.

5.1.2 BENEFIT

RTWP can be improved and also uplink capacity and HSUPA throughput.

5.1.3 Trail result

This action was implemented on 3G_MT04_MTA_SGC, 2013-8-22, 11:40AM.


RNC level RTWP was improved by 0.8dB.

CSSR is improved mainly due to P2D


PS CSSR is improved. Degradation during 25th to 30th is due to Tx issue.

2013-9-10 New Features Benchmarking Page 16of 44


New Features Benchmarking

HSDPA traffic is on the same level.

Average HSDPA throughput per UE is on the same level.

5.1.4 Further Action

Will be replaced with Dynamic HSDPA CQI feedback period


2013-9-10 New Features Benchmarking Page 17of 44
New Features Benchmarking

6 Load-based BLER configuration for R99

6.1.1 DESCRIPTION

Generally, a small target block error rate (BLER) is configured for an R99 channel. For
example, the typical target BLER for PS services over R99 channels is 1%. A small
target BLER raises data transmission rates and reduces the retransmission ratio but
requires high transmit power.
When the system load is heavy, a small target BLER restricts the number of UEs that
the system can serve. This compromises the uplink capacity of the system. To solve
this problem, raise the target BLER for each UE so that the transmit power of each
UE can be reduced and more UEs can be admitted. This approach sacrifices a little
throughput for a reduced load on each link and thereby increases the overall
capacity of the system.
The load-based uplink target BLER configuration function dynamically configures the
target BLER for each R99 link based on the system load. That is, a small target BLER is
configured for each link when the system load is light, and a large target BLER is
configured for each link when the system load is heavy.

6.1.2 BENEFIT

When the total uplink load and actual uplink service load in a cell are restricted,
increasing the target BLER lowers the uplink load in the cell and raises the uplink
throughput of the cell.
Emulation results show that the uplink load decreases by at most about 15% when
there are 30 online R99 UEs and the target BLER is adjusted.

6.1.3 Trail result

This feature was implemented on 3G_RO14_PRS_NGA, 2013-8-30, 09:20AM.

RTWP was improved on 30th and 31st August, but from 1st Sept, traffic increased,
cant benchmark.
Besides, RTWP of RO14 was on a good level, hardly to get improvement.

2013-9-10 New Features Benchmarking Page 18of 44


New Features Benchmarking

6.1.4 Further Action

Need to trail on another RNC.

7 P2D transitions when CS services is triggered

7.1.1 DESCRIPTION

With the traffic growth, FACH is showing more congestion, When UE is on PCH state
and CS is triggered, normally, UE will perform P2F then F2D, there is high risk of
setup failure due to FACH congestion.
With this feature enabled, when CS is triggered while UE is on PCH, UE will perform
P2D instead of P2F->F2D to avoid setup failure due to FACH congestion or complex
signaling procedure.

2013-9-10 New Features Benchmarking Page 19of 44


New Features Benchmarking

7.1.2 BENEFIT

CS CSSR can be improved, and FACH congestion can be released slightly.

7.1.3 Trail result

This feature was implemented on 3G_MT01_MTE_SGC, 3G_MT05_MTE_SGC,


3G_MT06_MTA_SGC, 3G_MT07_MTA_SGC, 3G_MT08_MTA_SGC, 2013-8-22,
11:47AM.

CS CSSR is improved by 0.2%.

CS traffic is on the same level.

PS traffic is on the same level.

2013-9-10 New Features Benchmarking Page 20of 44


New Features Benchmarking

7.1.4 Further Action

Already being rolled out

8 Power Code Balance

8.1.1 Description:

This feature can balance the consumption of currently available code resources and
power resources, to avoid code or power unilaterally congestion in order to improve
resource utilization, enhance cell capacity.
SET MACHSPARA: LOCELL=0, RSCALLOCM=POWERCODE_BAL;

8.1.2 Benefit:

Relative to the code priority, the power code balance can enhance the cell downlink
load, while reducing the resource utilization of code.

8.1.3 Trail result

This feature was implemented on 3G_PP14_PPQ_NGA, 2nd Sept, 15:40PM


Code congestion and HSDPA throughput is improved on 3G_Tuks_NGA

2013-9-10 New Features Benchmarking Page 21of 44


New Features Benchmarking

8.1.4 Further Action

Need to trail on another RNC.

9 CQI Adjustment Based on Dynamic BLER Target

9.1.1 Description

The CQI measures the channel conditions of a UE and is reported from the UE to the
NodeB. With this feature, the NodeB determines an appropriate TBS based on the
reported CQI, system resources, and the TFRC policy. If the reported CQI and related
conditions remain the same, the NodeB does not change the TBS because it does not
consider the ever-changing radio environments.
The constant changes in radio environments, caused by multipath effects and UE
mobility, lead to fluctuating channel quality. Under these circumstances, choosing a
TBS based on the reported CQI makes it difficult to always achieve the optimum
2013-9-10 New Features Benchmarking Page 22of 44
New Features Benchmarking

downlink throughput. With the feature CQI adjustment based on dynamic BLER
target, the NodeB monitors the channel quality fluctuations for HSDPA users in a cell
in real time and dynamically selects a proper BLER target based on the monitoring
result. The NodeB then uses the BLER target to adjust the CQI reported by the UE.
The BLER described in this section refers to the SBLER at the MAC-(e)hs layer and
reflects the average block error rate at the MAC layer. Accordingly, the BLER target
described in this section refers to the SBLER target at the MAC-(e)hs layer.
CQI Adjustment Process
CQI adjustment based on dynamic BLER target is performed in each TTI. The
following describes the adjustment process:
1. Based on the CQI reported by the UE, the NodeB checks the actual radio
environment, which is affected by multipath effects and UE mobility.
2. Based on the actual radio environment and channel quality of the UE, the NodeB
obtains an optimum BLER target, which helps to achieve the highest possible
throughput for the UE.
3. Based on the ACK, NACK, or DTX indication from the UE in the current TTI and on
the optimum BLER target, the NodeB calculates the CQI offset, which can be a
positive or negative number. The NodeB then uses the CQI offset to adjust the CQI.
4. Based on the adjusted CQI, the NodeB selects an appropriate TBS by using the
TFRC algorithm.

9.1.2 Benefit:

Based on the adjusted CQI, the NodeB determines an appropriate TBS to achieve
higher downlink throughput for HSDPA users and higher cell throughput.

10 Dynamic Configuration of HSDPA CQI Feedback Period

10.1.1 DESCRIPTION

A channel quality indicator (CQI) reported by an HSDPA UE reflects the radio quality
at the current location of the UE. Based on the CQI, the NodeB selects an
appropriate data block size and modulation scheme to ensure data transmission
performance. Due to fluctuations in the radio environment, the UE needs to report
CQIs promptly.
CQIs are periodically reported over the HS-DPCCH. If a short CQI feedback period is
used, CQIs are frequently reported. Consequently, the scheduling module promptly
learns about the radio quality and performs data scheduling accordingly. This way,
data blocks are more likely to be correctly transmitted on the downlink. However,
frequent CQI feedback imposes a heavy load on the uplink and requires UEs to use
high transmit power. As a result, call drop rates may increase at cell edges. This
feature supports three functions for dynamically adjusting the CQI feedback period:
2013-9-10 New Features Benchmarking Page 23of 44
New Features Benchmarking

-based dynamic configuration of the HSDPA CQI feedback period


Based on the uplink load in the cell, the NodeB dynamically configures an
appropriate CQI feedback period. When the uplink load is light, a short CQI feedback
period is used to ensure high-speed data transmission on the downlink. When the
uplink load is heavy, a long CQI feedback period is used to alleviate the uplink load.
for the combination of CS and
PS services
The combination of CS and PS services requires higher UE transmit power than an
individual CS or PS service. A long CQI feedback period needs to be used to prevent
decreases of CS service quality in the combination.

state transiting from the E-DCH to the DCH (E2D transition) due to limited coverage
When a service carried over HSUPA needs to fall back to the DCH channel due to
limited coverage. A long CQI feedback period needs to be used to ensure coverage.
These three functions can work side by side.

10.1.2 BENEFIT

When a large number of HSDPA UEs are online, CQIs sent over HS-DPCCHs
contribute to a large proportion of the uplink load and reduce uplink capacity. In this
case, if the total uplink load and actual uplink service load are both restricted, the
RNC configures the long CQI feedback period (which can improve capacity) for UEs to
reduce power occupied by control channels and increase power available on traffic
channels. This raises the uplink throughput.
Emulation tests were performed based on small-packet transmission. The test
results are as follows: If the CQI feedback period is adjusted from 2 ms to 8 ms and
there are 40 online HSDPA UEs, the uplink actual load decreases by a maximum of 20%
during busy hours. If the CQI feedback period is adjusted from 4 ms to 8 ms, the
uplink actual load decreases by a maximum of 10% during busy hours.

10.1.3 Trail result

This feature was implemented on 3G_PP14_PPQ_NGA, 2nd Sept, 15:40PM


RNC level shows 0.4dB improvement.

2013-9-10 New Features Benchmarking Page 24of 44


New Features Benchmarking

HSDPA traffic is increasing since 1st September.

HSDPA throughput per user is on the same level.

10.1.4 Further Action

Recommended to rollout in all RNCs


2013-9-10 New Features Benchmarking Page 25of 44
New Features Benchmarking

11 Dynamic Target RoT Adjustment

11.1.1 DESCRIPTION

Before Dynamic Target RoT Adjustment is introduced, the target uplink load level is
specified by MaxTargetUlLoadFactor. However, a fixed MaxTargetUlLoadFactor
value cannot account for varied scenarios. That is because a small value is required
to ensure the cell coverage in scenarios with poor coverage and a large value is
required to ensure high cell capacity in scenarios with good coverage. To consistently
achieve an optimum maximum uplink load level, there is a need to introduce
Dynamic Target RoT Adjustment.
The target RoT is obtained by subtracting the noise floor from the RTWP and is used
for NodeB fast scheduling. A large target RoT leads to a heavy cell load and
consequently a high cell throughput. However, UMTS is a system that produces
interference within itself. As a result, a heavy cell load leads to increased
interference and decreased cell coverage. Dynamic Target RoT Adjustment allows
the target RoT to be adjusted to increase the cell throughput without affecting key
performance indicators (KPIs) related to the call drop rate.
The relationship between the RoT and uplink load is as follows:
RoT = -10 x log10(1 Uplink load factor)
DynTgtRoTCtrlSwitch controls whether Dynamic Target RoT Adjustment is enabled.
MaxTargetUlLoadFactor specifies the initial target RoT.
Adjusting the target RoT for a cell depends on the RNC's decision on whether the
power of an R99 UE is insufficient and on the IE UL Timeslot ISCP. This IE is contained
in the COMMON MEASUREMENT REPORT message sent from the NodeB to the RNC.
Based on the transmit power of HSUPA UEs in the cell, cell throughput, and actual
RoT, the IE UL Timeslot ISCP can be set to one of the following values:
0: indicates that the NodeB requests the RNC to reduce the target RoT. This IE is
set to 0 when at least one HSUPA UE in the cell meets the following two
conditions:
The UE's transmit power approaches the maximum.
The UE throughput is low.
1: indicates that the NodeB requests the RNC to increase the target RoT. This IE is
set to 1 when no HSUPA UE in the cell meets the preceding two conditions and the
actual RoT is close to the target RoT.
2: indicates that the NodeB requests the RNC to keep the target RoT unchanged.
This IE is set to 2 when no HSUPA UE in the cell meets the preceding two
conditions and the actual RoT is not close to the target RoT.
The RNC decides whether to reduce or increase the target RoT every period specified
by TgtRoTAdjPeriod as follows:
If the transmit power of an R99 UE in the cell is insufficient or the value of the IE UL
Timeslot ISCP is 0, the RNC reduces the target RoT by one step, whose size is
2013-9-10 New Features Benchmarking Page 26of 44
New Features Benchmarking

specified by TgtRoTDownAdjStep. The lower limit is the target RoT corresponding


to MaxTargetUlLoadFactor.
If the transmit power of all R99 UEs in the cell is sufficient and the value of the IE
UL Timeslot ISCP is 1, the RNC increases the target RoT with a step size specified by
TgtRoTUpAdjStep. The upper limit is the target RoT corresponding to
UpLimitForMaxULTgtLdFactor.

11.1.2 BENEFIT

In scenarios where the cell coverage is not limited, this feature raises the target RoT
to increase the maximum uplink load for HSUPA UEs, increasing the uplink cell
throughput. When the uplink traffic is heavy, the uplink capacity can be increased by
up to 20%.

Cell coverage has an inverse relationship with cell capacity. In a cell where there are
no UEs with limited transmit power, this feature increases the target RoT for the cell
and cell coverage shrinks with the increase of uplink cell throughput. As a result, the
RRC connection success rate decreases. In a cell where there are UEs with limited
transmit power, this feature increases cell coverage by reducing the target RoT at a
step (MaxTargetUlLoadFactor specifies the lower limit). Before the target RoT is
adjusted to a proper value, call drops, handover failures, and throughput decrease
may occur on the UEs with limited transmit power.

11.1.3 Trail result

This feature was implemented on 3G_JG05_JGE_SGC, 2nd Sept, 16:00PM


Traffic increased from 1st September to 6th September, cant benchmark.
With the same traffic, RTWP on 7th September is slightly improved than 31st August.

2013-9-10 New Features Benchmarking Page 27of 44


New Features Benchmarking

11.1.4 Further Action

Need to trial on another RNC

12 Enhanced Fast Dormancy

12.1.1 DESCRIPTION

Some intelligent UEs on a live network send a Signaling Connection Release


Indication (SCRI) message to the RNC after PS data transmission is complete. By
sending the SCRI message, intelligent UEs request for a transition to idle mode or the
CELL_PCH or URA_PCH state to reduce battery consumption. Upon receiving the
SCRI, the RNC can release the signaling connection and put the UE into idle mode, or
the RNC can maintain the signaling connection and put the UE to CELL_FACH or
CELL_PCH/URA_PCH state. RSVDBIT1_BIT29 of the RsvdPara1 parameter in the SET
URRCTRLSWITCH command controls the UE through CELL_FACH to
CELL_PCH/URA_PCH or directly to CELL_PCH/URA_PCH. These procedures can
reduce battery consumption, depending on the UE capability and feature activation
on the RNC. By default, the RNC puts the UE into idle mode. A UE setting up PS
services in idle mode consumes more signaling resources than that in the CELL_PCH
or URA_PCH state. If there are a large number of UEs transited between idle mode
and CELL_DCH state, signaling storms may occur. The EFD feature puts UEs into the
CELL_FACH or CELL_PCH state to reduce signaling resource consumption and
eliminate signaling storms.
Huawei provides a comprehensive end-to-end solution based on network
characteristics to respond to network challenges. EFD is one component of the
solution. This feature alone is not enough to eliminate signaling storms caused by
intelligent UEs. However, when applied with professional services, EFD can be used
to optimize the quality of service (QoS) for the entire network.
The UEs on a live network can be divided into three types:
2013-9-10 New Features Benchmarking Page 28of 44
New Features Benchmarking

UEs that do not send SCRI messages because there is no PS data to be transmitted
Pre fast dormancy UEs. This type of UE does not read the T323 information element
(IE) carried in the system information block type 1 (SIB1) message. After PS data
transmission is complete, this type of UE sends an SCRI message to the RNC, but the
SCRI message does not carry the IE Signaling Connection Release Indication Cause.
Both T323 and Signaling Connection Release Indication Cause are introduced in 3GPP
Release 8.
R8 fast dormancy UEs. This type of UE reads the T323 IE carried in the SIB1 message
and sends an SCRI message to the RNC after PS data transmission is complete. The
SCRI message carries the IE Signaling Connection Release Indication Cause that is set
to "UE Requested PS Data session end."
The T323 IE carried in the SIB1 message controls the frequency at which the R8 fast
dormancy UEs send SCRI messages with the IE Signaling Connection Release
Indication Cause set to "UE Requested PS Data session end". The T323 timer starts
after an SCRI message is sent by the R8 fast dormancy UEs, and the second SCRI
message with the IE Signaling Connection Release Indication Cause set to "UE
Requested PS Data session end" can be sent only after the T323 timer expires.
The EFD feature applies only to the pre fast dormancy UEs and R8 fast dormancy UEs.
Users can configure EFD to be enabled for only the pre fast dormancy UEs or R8 fast
dormancy UEs.
When this feature is disabled, the RNC releases the signaling connection and puts
the UE into idle mode after receiving the SCRI message regardless the UE types.
When this feature is enabled, the RNC performs different processing based on the
UE type:
For the pre fast dormancy UEs, the RNC checks for compatibility issues after
receiving an SCRI message. If there are no compatibility issues, the RNC puts the UE
into the CELL_FACH or PCH state. If there is a compatibility issue, the RNC puts the
UE into idle mode.
For the R8 fast dormancy UEs, the RNC puts the UE into the CELL_FACH or PCH
state after receiving an SCRI message.
When there is no PS data to be transmitted, the intelligent UE sends the RNC an SCRI
message to request the UTRAN to release the signaling connection. This procedure
saves power. In addition, the UE periodically sends heartbeat messages to the core
network, for example, to check for new mails on the mail server. If the EFD feature is
disabled, the RNC releases the signaling connection and puts the UE into the idle
state. In this case, sending heartbeat messages leads to the procedures for RRC
connection setups, authentication, encryption, and RAB setups. These procedures
increase the RNC signaling processing load.
EFD addresses this problem. With EFD, the RNC transits a UE to the CELL_FACH or
PCH state instead of idle mode upon receiving an SCRI message from the UE. In this
case, when the UE periodically sends heartbeat messages, the signaling procedure
between the UE and RNC is simplified because the RRC connection is maintained. As
the number of signaling exchange messages decreases, significant CPU resources can
2013-9-10 New Features Benchmarking Page 29of 44
New Features Benchmarking

be saved for the RNC, and the UE consumes about the same low amount of battery
power as a UE in idle mode.

12.1.2 BENEFIT

Enable for battery savings


Less signalling load in network
Lower UL CE usage to reduce UL CE congestion

12.1.3 Trail result

Implemented on 3G_PC10_PCN_NGA, 2nd Sept, 09:20AM


RRC attempts reduced 30%.

PS RAB attempts reduced 40%.

SPU board load reduced.

2013-9-10 New Features Benchmarking Page 30of 44


New Features Benchmarking

PS RAB failure time is on the same level.

FACH congestion reduced.

PS CSSR degraded by 0.5%.

2013-9-10 New Features Benchmarking Page 31of 44


New Features Benchmarking

12.1.4 Further Action

Will revert back, PS CSSR degradation under investigation, and need to trail again
when solution provided

13 MULTIRAB OPTIMIZATION

13.1.1 Background

The Multi-RAB services increased as smart phone penetration is increasing.


General cause of drop rate of Multi-RAB higher than single CS RAB
Higher RF signal quality requirement comparing with CS Single RAB
More complicated signalling procedure comparing with Single RAB
To improve the CS call drop
Reduce the PS RF signal quality requirement for multi-RAB
Reduce the loss probability due to complicated signalling process.
Optimize the signalling procedures

13.1.2 Recommendation

2013-9-10 New Features Benchmarking Page 32of 44


New Features Benchmarking

13.1.3 Results

After implementation, IU Rejection due to security mode is reduced.

13.1.4 Future Actions

The following features and optimization parameters can be trailed.

2G FEATURES

2013-9-10 New Features Benchmarking Page 33of 44


New Features Benchmarking

14 PDCH Busy Threshold

14.1.1 DESCRIPTION

When PS traffic is heavy in a cell, namely when channel multiplexing ratio


(average number of MSs multiplexed on the PDCH in a cell) is higher than the
value of PSServiceBusyThreshold, channels are no longer assigned to new
MSs requesting access according to their timeslot capabilities.
Instead, only one UL and one DL channels are assigned to a new MS to ensure
its access to the network. In addition, the release delay of all downlink TBFs
in the cell is reduced to half the value of DNTBFRELDELAY. Reducing the delay
helps prevent new MSs from being denied access to the network due to
heavy traffic Channel assignment to MSs requesting channels again, however,
is not affected.
When PS traffic is light in a cell, namely when channel multiplexing ratio is
not higher than the value of PSServiceBusyThreshold, channel re-allocation
procedure will be triggered to assign channels anew to the new MSs that are
assigned one UL and one DL channels if necessary.

14.1.2 BENEFIT

Smartphones have different traffic model which result in the most of PS


service are small-sized data packets, the traditional algorithm based on the
MS multi-TS capability (3 or 4 TS) is not fit to smartphones traffic model fully
which wastes lots of channel resource.
This feature improves the capacity, the PS access performance, CS and PS
congestion rate, and the um interface quality would be improved as well.

14.1.3 Conclusion:

PW12 Trail: Changed the PS busy threshold to 20, PS interleaving was


improved obviously, and TBF establishment success rate and TBF drop rate
were improved at busy hour as well.
DR12 Trail: Changed the PS Busy threshold to 20 & reduced the No. of PDCHs
by 25%, all the PS/CS KPIs were stable while it saves 25% capacity.

By optimizing PS busy threshold to 20 can help to improve the capacity


without degrading CS/PS main KPIs, further more we can reduce the number
of PDCHs to improve the um interface quality and increase the CS Full rate to
improve the Voice quality.

PW11 Trail: Changed the PS busy threshold to 20


2013-9-10 New Features Benchmarking Page 34of 44
New Features Benchmarking

The PS interleaving improved from 3 to 2.

2013-9-10 New Features Benchmarking Page 35of 44


New Features Benchmarking

DR12 Trail: Changed the PS Busy threshold to 20 & reduced the No. of PDCHs
by 25%
It saved the PS channel resource by 25%. PS EDGE single TS throughput was
improved about 10%. It improved PDCH bearing efficiency as well.

2013-9-10 New Features Benchmarking Page 36of 44


New Features Benchmarking

2013-9-10 New Features Benchmarking Page 37of 44


New Features Benchmarking

2013-9-10 New Features Benchmarking Page 38of 44


New Features Benchmarking

15 Active TBF Allocation

15.1.1 DESCRIPTION

The number of TBFs multiplexed on a PDCH cannot reflect the actual PDCH
usage. For low throughput services, data transmission time is a small part of a
TBF life cycle. This leads to a PDCH usage.
The BSC implements the Active TBF Allocation feature as follows:
Monitors the downlink data transmission on each PDCH in real time and
periodically measures the downlink load of each PDCH.
Preferentially allocates PDCHs with lighter loads to MSs based on the latest
load information of PDCHs. This balances the loads between PDCHs and
improves the downlink user rate.

15.1.2 BENEFIT

Avoids unnecessary capacity expansion and brings economic benefit because


the number of activated PDCHs is reduced, and the efficiency for PDCHs to
carry TBFs is increased
Reduces interference from PDCHs to the network because the number of
PDCHs is reduced.
Allocates resources to PS services more efficiently and maintains a high data
rate for PS services while occupying fewer resources.
2013-9-10 New Features Benchmarking Page 39of 44
New Features Benchmarking

15.1.3 Conclusion:

After enabling this feature in PW12, the EDGE Downlink throughput per User was
improved, and all other CS/PS KPIs are keep stable.

16 Voice Quality Indicator

16.1.1 DESCRIPTION

The voice quality index (VQI) feature provides a direct method of measuring
the voice quality of the radio network. By measuring the uplink VQI and
downlink VQI, the voice quality of the network is quantified, which provides a
reference for future network optimization.
Obtaining the VQI Information
In each call, when the parameter RPTVOICE is enabled, the BTS receives the
customized extended measurement reports every five measurement report
periods (within 2.4 seconds). The uplink measurement reports contain the
short-time VQI information.
Classification of VQI Scores
The MOS analysis method is applied in VQI to measure the voice quality. MOS
is used to assess the quality of the middle-rate and low-rate voice codecs.
The MOS score ranges from 1 to 5.
5: Excellent
4: Good

2013-9-10 New Features Benchmarking Page 40of 44


New Features Benchmarking

3: Fair
2: Poor
1: Unsatisfactory
Measurement of Voice Quality
To avoid floating-point calculation when the VQI performance is measured,
the VQI score is multiplied by 50 and then the result is converted into an
integer. The integer is sent to the BSC. After receiving the VQI score integer,
the BSC forwards the score to the M2000 for processing. The M2000 divides
the value by 50 and then obtains the average short-time VQI score. The
methods of measuring VQI voice quality are as follows:
Voice quality levels
Based on the score range of the MOS analysis method, the voice quality is
further classified into 11 levels for measuring performance, as listed in Table
below.
Table Voice quality levels
Level Description

Initial level voice quality < 0.5

Level 1 0.5 < voice quality < 1.0

Level 2 1.0 < voice quality < 1.5

Level 3 1.5 < voice quality < 2.0

Level 4 2.0 < voice quality < 2.5


Level 5 2.5 < voice quality < 3.0
Level 6 3.0 < voice quality < 3.5

Level 7 3.5 < voice quality < 4.0

Level 8 4.0 < voice quality < 4.5

Level 9 4.5 < voice quality < 5.0

Level 10 voice quality > 5.0

2013-9-10 New Features Benchmarking Page 41of 44


New Features Benchmarking

16.1.2 BENEFIT

The VQI establishes the mapping between the radio network performance and voice
quality. The VQI value, which helps learn the voice quality, is calculated based on the
parameters related to the radio quality of the uplink/downlink speech signals. The
MOS analysis method is applied in VQI to measure the voice quality. The MOS is used
to assess the quality of the middle-rate and low-rate voice coding. The MOS value
ranges from 1 to 5.
Based on the MOS analysis method, Huawei further divides the voice quality into 11
levels. In this manner, the voice quality is quantified to facilitate the identification of
the voice problem and network optimization.

According to actual wireless environment signal quality, BSS adjusts coding rate
dynamically to improve the voice quality.

We trailed to reduce the AMR UL/DL coding rate adjust threshold to increase the
high codec proportion to improve the VQI.
2013-9-10 New Features Benchmarking Page 42of 44
New Features Benchmarking

Parameters Name Current Baseline Optimization Proposal


AMR UL Coding Rate adj.th1[F] 20 14
AMR UL Coding Rate adj.th2[F] 24 18
AMR UL Coding Rate adj.th3[F] 30 24
AMR DL Coding Rate adj.th1[F] 20 14
AMR DL Coding Rate adj.th2[F] 24 18
AMR DL Coding Rate adj.th3[F] 28 24
AMR UL Coding Rate adj.th1[H] 25 20
AMR UL Coding Rate adj.th2[H] 31 26
AMR UL Coding Rate adj.th3[H] 63 63
AMR DL Coding Rate adj.th1[H] 25 20
AMR DL Coding Rate adj.th2[H] 31 26
AMR DL Coding Rate adj.th3[H] 63 63

16.1.3 Conclusion:

No visible gain seen from RS13 trail, and also there were lots of operation on this
BSC, so it is recommended to trial in another BSC.

2013-9-10 New Features Benchmarking Page 43of 44


New Features Benchmarking

2013-9-10 New Features Benchmarking Page 44of 44

You might also like