L115698 Minimum BitRate Enforcement For

nonGBR (LR13.1)
Adrian TRAIN, Wireless/MGR/NEA
October 9th 2013
CONTENTS

1 | FEATURE DESCRIPTION

2 | FEATURE ACTIVATION STRATEGY

3 | PERFORMANCE EVALUATION

4 | CONCLUSION

5 | APPENDIX A: XXXX
1
Feature Overview
Feature Overview
Scope

The feature L115698 provides following enhancements:

 Allowsthe eNB to differentiate resource reservation for different

nonGBR QCIs.

 Enables eNB to monitor and control the active throughput

performance for nonGBR radio bearers in DL and UL schedulers, thus
user experience can be more predictable.
Feature Overview

Per-QCI Resource Reservation for NonGBR in Resource

Reservation:

• Before only dl/ulminRateForBe were used in RAC an TAC

• Now extra differentiation of resource reservation is provided through
parameter prbReservationFactor which is configurable per QCI. The
resource reservation for nonGBR then becomes :

minRateForBE * prbReservationFactor

Which is combined metric for each nonGBR QCI on DL and UL(separately

configured)
Feature Overview

Per-QCI Resource Reservation for NonGBR in Resource

Reservation:

•eNB shall allow TrafficRadioBearerConf::prbReservationFactor

configuration for nonGBR bearers

•per-QCI prbReservationFactor along with the existing parameter

dl/ulMinRateForBE are used for the resource estimation during
radio admission control, congestion control and load balancing
procedures.
Feature Overview

Per-QCI Minimum Active Throughput Enforcement in RF Schedulers:

• Per QCI minimum throughput target concept into the dynamic RF schedulers
and it is monitored / controlled by the schedulers.

• Active throughput is defined as the user perceived throughput when the

bearer has outstanding data, i.e. idle intervals are discounted from throughput
evaluation.
 Feature Overview

Per-QCI Minimum Active Throughput Enforcement in RF Schedulers:

•When the active throughput falls below the minimum throughput target, the
scheduler boosts priority by applying a dynamic weight to the bearer thus
scheduling the traffic faster.

•Once the active throughput well exceeds the minimum throughput target,
the additional weight is removed.

•The maximum QoS weight that can be applied for minRate enforcement shall
be controlled by the parameter:

eNBRadioConf::dlNonGBRClippingFactor
QoS Performance Control GBR and nonGBR
Bearers
• Relative QoS performance between various nonGBR and GBR bearers
can be controlled by adjusting the QoS weight QoS_w(b) and QCI
weight QCI_w(b).
• QoS_w(b) is the dynamic weight evaluated based on the QoS target
and the achieved QoS performance of bearer b. (influences the level of
resource needs when a bearer fails to achieve its QoS target. )
• QoS_w(b) for nonGBR bearer is capped at exp(dlNonGbrClippingFactor)
for DL and MaxNonGBRQoSWeight for UL.
• QoS_w(b) for GBR bearer is capped at exp(dlGbrClippingFactor) for DL

• QCI_w(b) is the per-QCI weight configured based on the QCI of bearer

b. (influences the relative resource fairness among bearers of different
QCIs)
• Higher per-QCI weight provides a deterministic advantage in resource
allocation.
• Can be used to protect GBR performance when nonGBR QoS is activated.
9
Feature Overview

To account for network jitter and protocol delay, any data bursts with gaps lower
than a 150ms (default) configurable threshold (rabInactivity) is regarded as
one data burst
If gap >= 151ms then it is discounted from throughput calculation.
Feature Overview

•DL and UL dynamic scheduler shall be able to evaluate the active

throughput performance for nonGBR bearer if :

•“Rate” has been selected as the QoS metric for the bearer
•The minimum throughput target configured for the bearer is non
zero.

• The active throughput is defined as the short-term average served

throughput when the bearer has outstanding data backlog.

•DL and UL dynamic scheduler shall be able to apply a dynamic QoS

weight to a nonGBR bearer scheduling priority metric based on the
achieved active throughput and the minimum throughput target.
Feature Overview
• Configurable (DL and UL separately) minimum active throughput target per
nonGBR QCI.

• Allow customers to select the DL QoS metric per nonGBR QCI between:
• Rate bearer is under the minimum rate
• PDB* bearer is under the PDB-dependent QoS control
• None this QCI traffic radio bearer has no specific QoS metric to enforce.

• RF scheduler tracks the nonGBR bearer active throughput from eNB perspective.
When it approaches or falls below the minimum target, RF scheduler boosts
the scheduling priority to help improve the bearer performance.

• *PDB – Packed Delay Budget

12
Feature Overview

DL Scheduler

•Selection parameter (dlQoSMetricType) is provided to allow customers to

choose the desired metric for QoS enforcement, which offers flexible QoS control
across different QCIs.
•DL scheduler is operating on a radio bearer basis and tracks the performance of
each radio bearer.

UL Scheduler

•Unlike DLS, ULS does not have a good view on the UE data arrival, no full control
to determine which bearer’s data will be placed over PUSCH among multiple
bearers. Therefore, the UL min rate is enforced on an “aggregate UE level”
instead of “bearer level”.

•The UL rate enforcement hence will be based on the information that eNB has,
which is the per-logical channel BO view eNB maintains.
Feature Overview
Scheduling Illustration
Data burst Gap

Pkt
Arrivals

Scheduler
Buffer

Estimated
Active Minimum rate target
Throughput
Maximum weight boost
Scheduler
QoS Weight

Pkt
Scheduled
14
Feature Overview
FEATURE BENEFIT

Minimum data rate enforcement for nonGBR bearers in both DL and UL

direction.

Per-QCI choice of DL PDB or min-throughput control for non-GBR bearers,

so to allow customer to utilize both PDB and min-throughput control
functionalities offered by eNB.

Per-QCI PRB overbooking factor in CallP (RAC/CC/LB) so to offer resource

reservation flexibility for different nonGBR QCIs.
Feature Overview
Interactions

L92095 QCI parameters for enhanced scheduling :

• L92095 provides a PDB-based differentiation method for DL
nonGBR traffic. L115698 provides a min-rate enforcement for the
nonGBR differentiation.
• Configuration parameter dlQoSMetricType will be placed per
nonGBR QCI to allow customer to select between the min rate or
PDB Based QoS enforcement ( when both features are enabled in
the eNB)

• When L92095 is activated, DL dynamic scheduler shall evaluate

the PDB-based QoS weight for a nonGBR bearer if PDB has been
selected as the QoS metric for the bearer.
2
Feature Activation Strategy
Activation Strategy
eNB Configuration Model

EnbRadioConf

DedicatedConf EnbRadioConf

[1.. 32]

TrafficRadio
BearerConf

• dlMinThroughputTarget
• dlQoSMetricType
• ulMinThroughputTarget
• dlActiveThroughputAverageCoefficient
• ulActiveThroughputAverageCoefficient
• dlNonGbrClippingFactor
• ulMaxNonGbrQosWeight
• marginForNonGbrMinRateEnforcement
Activation Strategy

• Feature type: Optional

• Feature it’s not activated by default.

Feature activation flag:

ActivationService ::isNonGBRMinRateEnabled = TRUE

The parameter is ClassB – Cells of eNB.

 3. Performance Evaluation
In Object Parameter Recommende Range Parameter Description
d Name Name d Value

1 Activatio isNonGBRMinR True [True, This parameter is the feature activation flag for the nonGBR minRate
nService ateEnabled False] enforcement feature.

2 TrafficR dlQoSMetricTyp Rate Enumerate This parameter specifies the DL QoS metric for nonGBR service.
adioBear e
erConf {None, a) None, this QCI traffic radio bearer has no specific QoS metric to
Pdb, Rate} enforce.
b) Pdb, it means this bearer is under the PDB-dependent QoS control
c) Rate, it means the bearer is under the minimum rate QoS control
3 TrafficR dlMinThroughpu [see table] [0..5000] This parameter specifies the minimum DL active throughput target
adioBear tTarget with step = enforced by DL scheduler for non-GBR bearer per QCI, when the
erConf 50 Kbps bearer has data to be transmitted over DL. The parameter shall be
unset if feature is disable
4 TrafficR ulMinThroughpu [see table] [0..5000] This parameter specifies the minimum UL active throughput target
adioBear tTarget with step = enforced by UL scheduler for non-GBR bearer per QCI, when the
erConf 50 Kbps bearer has data to be transmitted over DL. The parameter shall be
unset if feature is disable.
5 EnbRadi ulActiveThrough 1014 [0, 1023] This parameter specifies the averaging coefficient for the DL active
oConf putAveragingCo step 1. bearer throughput evaluation. Used in min-Rate evaluation for non-
efficient GBR service. The value is divided by 1024 to provide a forgetting factor
between 0 and 0.999.
6 EnbRadi dlActiveThrough 1014 [0, 1023] This parameter specifies the averaging coefficient for the DL active
oConf putAveragingCo step 1. bearer throughput evaluation. Used in min-Rate evaluation for non-
efficient GBR service. The value is divided by 1024 to provide a forgetting factor
between 0 and 0.999.
3. Performance Evaluation

Ind Object Name Parameter Name Recom Range Parameter Description

mended
Value
7 EnbRadioConf marginForNonGbrMinRate 0,5 [0.1 – 3] step This parameter specifies the margin beyond the minimum
Enforcement 0.1 throughput target that scheduler starts to raise the
scheduling priority for the user/bearer. When the active
throughput falls below (1+m)*Rmin, the extra scheduling
priority starts to show up.
8 PerformanceM nonGbrMinRateReported True [True, False] This parameter specifies whether, or not, the group of
anagement counters related to NonGbrMinRate is selected to be
reported

9 EnbRadioConf dlNonGBRClippingFactor 2 [1..5] step 1 This parameter specifies the maximum DL QoS weight =
exp(dlNonGbrClippingFactor) for noNGBR service due to
QoS metric enforcement, including minRate and PDB.

10 EnbRadioConf ulMaxNonGBRQoSWeight 8 [1..64] step 1 This parameter specifies the maximum UL QoS weight for
noNGBR service due to QoS metric enforcement,
including minRate and PDB
Activation Strategy
Configuration Parameters
Here is the proposed activation strategy to validate this feature in live network:
Set the feature activation flag:
• isMinRateEnforcementEnabled = TRUE
For the QCIx that wishes to use min rate control , set:
• TrafficRadioBearerConfx::dlQoSMetricType=Rate

Packet Packet
ulQCISch dlQCISch
dlMinThroug ulMinThrou UL DL Delay Error
QCI Type eduling eduling Example Service
hputTarget ghputTarget Priority Priority Budget Loss
Weight Weight
[ms] Rate
1 GBR 16 16 N/A N/A 2 2 80 10e−2 Conversational Voice
2 GBR 8 8 N/A N/A 6 4 130 10e−3 Video Streaming
3 GBR 8 8 N/A N/A 5 3 30 10e−3 Real Time Gaming
Video (Buffered
4 GBR 4 4 N/A N/A 7 5 280 10e−6 Streaming)
Non-
5 GBR 16 16 0 kbps 0 kbps 3 1 80 10e−6 IMS Signaling
Non-
6 GBR 2 2 5000 kbps* 500 kbps* 8 6 280 10e−6 Gold Customer
Non- Video (Buffered
7 GBR 4 4 0 kbps 0 kbps 9 7 80 10e−3 Streaming)
Non-
8 GBR 1 1 500 kbps* 50 kbps* 10 8 280 10e−6 Silver Customer
Non-
9 GBR 0.5 0.5 0 kbps 0 kbps 11 9 280 10e−6 Bronze Customer

*subjected to discussion, should be based on customer needs

3
Performance Evaluation
3. Performance Evaluation
• E2E Testing

• When performing DL traffic recommended validation would be:

• 1 x Gold User – Cell Edge
• 1 x Silver User – Center Cell
• 2 x Bronze User – Near Cell
• Without feature, if QoS differentiation was already active (LA6 feature),
Gold would have a better throughput than silver and bronze, but may not
necessarily reach 5 Mbit/s.
• With feature activate, UE‘s doing traffic will be handled differently based
on classes , Gold and Silver will have better throughput now than before
while Bronze throughput will be the same

24
3. Performance Evaluation
• The KPIs to be measured are:

• Minimum UL/DL bitrate for non-GBR per QCI.

• Total cell throughput

• An example of test can be:
ul/dlminThroughputTarget for one nonGBR QCI can be set to a value
(ex:1Mbps). Depending on the load / UE’s RF condition, it may or may not
achieve the throughput, although scheduler will boost weight and try to
scheduler more PRBs to respective UE.
In multi-user conditions (e.g. all UE’s have the min bitrate set) it will be difficult
to reach the target.

25
3. Performance Evaluation
Counters
Counter Name Counter Counter Description
ID
This counter provides the total amount of time that DL nonGBR bearers
within the cell has achieved at least their minimum rate target if
VS.DLDurationNonGBRBearersS
12122 configured. Only the bearers that has data backlog will be evaluated for
atisfied
this counter.
The counter is screened per nonGBR QCI (5/6/7/8/9).
This counter provides the total amount of time that DL nonGBR bearers
within the cell has failed to achieve their minimum rate target if
VS.DLDurationNonGBRBearersU 12129 configured. Only the bearers that has data backlog will be evaluated for
nsatisfied this counter.
The counter is screened per nonGBR QCI (5/6/7/8/9).
This counter provides the total amount of time that UL nonGBR bearers
VS.ULDurationNonGBRBearersS within the cell has achieved at least their minimum rate target if
atisfied 12130 configured. Only the bearers that eNB believe it has data backlog will be
evaluated for this counter.
The counter is screened per nonGBR QCI (5/6/7/8/9).
This counter provides the total amount of time that UL nonGBR bearers
vS.ULDurationNonGBRBearersU within the cell fail to achieve their respective minimum rate target if
12123
nsatisfied configured. Only the bearers that eNB believe it has data backlog will be
evaluated for this counter.
The counter is screened per nonGBR QCI (5/6/7/8/9).
4
Conclusion
Conclusion

• This feature is part of ALU LTE QoS framework. It enhances the standard
nonGBR QoS which has no minimum rate control, only relative priority
differentiation.

• Now nonGBR QCIs can be used to carry content-rich services which are
often bursty and variable-rate in nature, but has a certain minimum
throughput tolerance level when the traffic is active.