Radio Resource Partitioning.pdf

Radio Resource Partitioning
Feature Description
238/221 04-LZA 701 6014/1 Uen BH13B

Copyright
© Ericsson AB 2016-2020. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

Contents
1 Radio Resource Partitioning Overview 1
2 Dependencies of Radio Resource Partitioning 3
3 Feature Operation of Radio Resource Partitioning 9
3.1 Bearer Setup 11
3.2 Scheduling 13
3.3 Configuration 15
4 Network Impact of Radio Resource Partitioning 17
5 Parameters of Radio Resource Partitioning 18
6 Performance of Radio Resource Partitioning 20
7 Activate Radio Resource Partitioning 24
8 Deactivate Radio Resource Partitioning 25
9 Feature Change History 26
9.1 20.Q2: Static Resource Sharing 26
9.2 20.Q2: GBR Partitioning 27
Contents
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

1 Radio Resource Partitioning Overview
This feature enables the configuration of predefined shares of radio
resources in a network, when the resources are shared between user
categories.
Access Type: LTE
Feature Identity: FAJ 121 4571
Value Package Name: RAN Slicing
Value Package Identity: FAJ 801 0570
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license is
required for each radio.
Summary
The Radio Resource Partitioning feature ensures fair radio resource usage in a
network where resources are shared between user categories. This includes, for
example, different PLMNs in a Shared LTE RAN or a geographical split network.
In these networks, it is possible for one user category to be favored over another.
This depends on QoS settings or if there are large differences in user numbers for
each category.
The Radio Resource Partitioning feature enables the configuration of predefined
shares of radio resources. The partitions are based on PLMN for operators
sharing the radio network. For specific groups of UEs, the partitions are based on
SPID values.
SRBs are not partitioned, while non-GBR data bearers are always partitioned.
GBR bearers (including VoLTE and PTT), and IMS or MC signaling bearers are
partitioned when ResourcePartitions.gbrPartitioning attribute is set to
TRUE.
RBS resources can be dynamically or statically shared by the operators.
The Radio Resource Partitioning feature provides the following benefits in
dynamically shared resources:
— Free resources are shared among the partitions when available, while
ensuring that each partition is able to use its configured share when required.
— UE throughput increases for partitions which have a lower share of traffic
relative to the configured resource share.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 1

The Radio Resource Partitioning feature provides the following benefit in
dynamically and statically shared resources:
— Bearers in one partition are scheduled by QoS only in relation to bearers in
the same partition. This prevents lower QoS users in one partition from being
starved by higher QoS users in another partition.
The Radio Resource Partitioning feature provides the following benefit in
statically shared resources:
— Static resource partitioning does not allow non-GBR traffic to exceed the
configured share, even if unused capacity is available in the cell. In this way,
the use of unlimited resources can be restricted in shared LTE RAN
deployments.
Additional Information
For more information about related features and topics, see the following
documentation:
— Shared LTE RAN
— Subscriber Triggered Mobility
2 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

2 Dependencies of Radio Resource Partitioning
This feature is related to several other features.
Table 1 Feature Dependencies
Feature Relationship Description
Admission Control (FAJ 121
1857)
Related Admission Control feature is
agnostic to partitions, which
means that MSR does not
reflect the load in individual
partitions. Therefore, the
Admission Control feature
does not have the means to
protect individual partitions.
Baseband Resource Cell
Prioritization (FAJ 121 4915)
Related Baseband resource shortage
affects the radio resource
ratios in the partitions
configured by Radio Resource
Partitioning feature.
Baseband Resource Cell
Prioritization feature is
expected to increase the
occurrence of resource
shortage in normal priority
cells. In high priority cells, the
occurrence of resource
shortage is expected to be
decreased.
Note: Static Resource
Sharing and
Baseband Resource
Cell Prioritization
cannot be activated
together.
Carrier Aggregation (FAJ 121
3046)
Related The partition configuration
needs to be the same on all
cells in the eNodeB.
Differentiated Admission
Control (FAJ 121 1787)
partitions properly. Therefore,
the feature does not have the
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 3

means to protect individual
partitions in the desired way.
Downlink Frequency-Selective
Scheduling (FAJ 121 2053)
Related This Scheduler-related feature
are using channel quality. A
consequence of Radio
Resource Partitioning is
suboptimal scheduling
because of constraints
enforced by the configuration
of partitions. This can lead to
decreased gain from features
that tune the scheduler
behavior based on channel
quality (directly or indirectly).
Dynamic GBR Admission
partitions properly. Therefore,
the feature does not have the
means to protect individual
partitions in the desired way.
Dynamic QoS Modification
(FAJ 121 1749)
Related Bearer partition is
selected during bearer
creation, and it is not updated
later. Therefore both QCI and
ARP modification of existing
bearer is not reflected on
bearer partition.
Bearer remains at
the partition
received during bearer
creation.
Dynamic Uplink Resource
Allocation (FAJ 121 4619)
Elastic RAN (FAJ 121 4608) Related Sets of cells considered for use
as secondary cells are
4 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

expanded across multiple
eNodeBs.
Load-Based Access Barring
( FAJ 121 3093)
Related In automatic access barring,
the ratio between RRC
Connection Rejects and RRC
Connection Attempts is
calculated on a cell level and
not on a partition level.
Therefore, partitions cannot
be protected by automatic
access barring the same way
as the cell is protected.
Minimum Rate Proportional
Fair Scheduler (FAJ 121 0920)
Mission-Critical Push-to-Talk
(FAJ 121 4929)
Related If PTT or MC_SIGNALING
bearer is (High) Priority
Access bearer and
QciProfilePredefined.paP
artitionOverride is set to
true for QCI of that bearer,
bearer is not partitioned.
Otherwise, PTT bearer (as
GBR bearer) or MC_SIGNALING
bearer is partitioned when
ResourcePartitions.gbrPa
rtitioning is set to true.
Shared LTE RAN (FAJ 121
0860)
Related Radio Resource Partitioning
can be used to further
configure the utilization of
radio resources between
sharing operators.
Shared LTE RAN feature is
prerequisite for PLMN based
Radio Resource Partitioning.
Subscriber Triggered Mobility
(FAJ 121 1788)
Related Radio Resource Partitioning
and Subscriber Triggered
Mobility features are
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 5

complementary to each other.
Both features provide support
to apply specific radio
resource management
strategies based on Subscriber
Profile ID.
Uplink Carrier Aggregation
(FAJ 121 4425)
Related The configuration of PLMN or
SPID value and
ResourcePartition.partit
ionId needs to be the same
for all cells on both DUs or on
master eNodeB and
secondary eNodeB. There can
be less data scheduling
performance for Carrier
Aggregation-enabled UEs on
congested sCells.
Uplink Frequency-Selective
Scheduling (FAJ 121 1799)
Carrier Aggregation-Aware
IFLB (FAJ 121 3075)
Conflicting The Carrier Aggregation-
Aware IFLB feature cannot
estimate Carrier Aggregation
opportunities when the load is
such that the resource
partitioning feature actively
divides resources to the
partitions.
Carrier Aggregation FDD-TDD
(FAJ 121 4252)
Conflicting In DUs with both FDD and
TDD cells, the traffic in the
TDD cells can be limited
because higher priority is
given to the traffic reserved
for the respective partition in
the FDD cells.
Cross-DU Carrier Aggregation
Support (FAJ 121 3080)
Conflicting Partition utilization on SCell is
not considered for scheduling
Cross-DU CA traffic, and such
6 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

traffic does not contribute to
the partition utilization.
Dynamic UE Admission
Conflicting The Dynamic UE Admission
Control and Radio Resource
Partitioning cannot be
activated together.
Inter-eNodeB Carrier
Aggregation (FAJ 121 4469)
Conflicting This feature cannot be
activated together with Radio
Resource Partitioning.
Prioritized SR Scheduling (FAJ
121 4300)
Conflicting If the Prioritized SR
Scheduling feature is
activated together with Radio
Resource Partitioning, the
partitions do not reflect the
configured shares.
UE Throughput-Based
Mobility to Wi-Fi (FAJ 121
3064)
Conflicting The UE Throughput-Based
Mobility to Wi-Fi feature is
agnostic to partitions.
Therefore, UE throughput
calculation can be over- or
under-estimated, depending
on the partition configuration
and utilization.
UE Throughput-Aware IFLB
(FAJ 121 4219)
Conflicting The UE Throughput-Aware
IFLB feature is agnostic to
partitions which means that
UE throughput is estimated on
cell level and not on partition
level.
Hardware
No specific hardware requirement is expected for this feature.
Limitations
No limitations for this feature.
Network Requirements
No special network requirements for this feature.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 7

Affected System Functions
Table 2 Affected System Functions
Function Description
Throughput During congestion, the throughput can be
affected for UEs belonging to a partition
where there are more users than configured
shares.
Latency During congestion, latency can be affected for
UEs in a partition where there are more users
than configured shares. This is due to sparser
scheduling of the UEs. The configuration of the
PLMN or SPID value and
ResourcePartition.partitionId needs to
be the same on all cells for both DUs or on
master eNodeB and secondary eNodeB. There
may be less data scheduling performance for
Carrier Aggregation-enabled UEs on
congested ESCells.
8 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

3 Feature Operation of Radio Resource
Partitioning
This feature allows the configuration of predefined shares for the radio
resources.
Radio Resource Partitioning can be configured to partition bearers based on
either the serving PLMN of the UE or the SPID value of the UE. The partitions
along with their share of radio resources are configured by the operator at cell
level. Up to six partitions can be configured in each cell. These partitions are used
either for non-GBR data or for both GBR and non-GBR data, depending on the
configuration. In case of dynamic sharing, these partitions are prioritized
depending on the current use and the configured shares. In case of static sharing,
limitation for each partitions is done based on the configured share.
Configuration changes take effect at cell unlock. The use of PRBs uplink and
PRBs downlink for each partition can be observed by OSS PM counters in ENIQ.
Note: In order to make uplink resource partition work properly, the active UEs
must be at least four times the configuration of the SE or TTI capacity.
Otherwise, the legacy uplink scheduler does not fully support QoS
differentiation at low load, and it divides the spectrum in equal sizes.
It is recommended that following bearers have the same value for
paPartitionOverride:
— VOIP and IMS signaling bearers
— PTT and MC signaling bearers
To secure emergency calls it is recommended to set paPartitionOverride to
TRUE for VOIP and IMS signaling bearers.
Operational Process
1. The system tracks resource use for each configured partition, defined as
resource usage (PRBs and SEs, both uplink and downlink) divided by
maximum available resources. The maximum available resources are
adjusted by subtracting number of PRBs used for retransmissions.
2. In case of dynamic resource sharing, the radio resource partitioning down-
prioritizes partitions which use more than their configured share of
resources. The down-prioritized bearers are scheduled until free resources
are in the cell. If there is resource contention, it ensures that the configured
shares are not exceeded.
a. It is possible that not all available resources are configured for use in a
cell by the partitions. Those partitions which have the greatest load
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 9

compared to their configured share are more likely to receive the
remaining resources.
b. It is possible that more resources are configured for the partitions in a
cell than are available. Those partitions, which have the greatest load
compared to their configured share, are more likely to receive their full
configured share.
In case of static resource sharing, the radio resource partitioning limits the
partitions based on the configured share.
In both cases priority bearers excluded from partitioning can be configured.
High SRB, Paging or any other non-partitioned traffic load can affect the
resource use so it does not match the configured share. If any non-
partitioned resource becomes limiting, for example CCEs, it can also affect
the functionality so that configured shares do not match. CCE usage can, for
example, increase when coverage is bad.
3. The load from SRB and Paging and additionally from GBR (VoLTE or PTT)
and associated (IMS or MC) signaling when GBR partitioning is not activated
is deducted from the partition which has the least load compared to its
configured share.
4. Competition for the same resources can happen in the following ways:
a. First between partitions, prioritization is according to used resources and
agreed shares in dynamic resource sharing scenario.
b. Second within the partition, prioritization is according to QoS priority.
5. The resource usage is measured and adjusted in every TTI.
10 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

3.1 Bearer Setup
A set of new bearers is generated and assigned to a partition.
L0001440C
GBR or IMS or MC
Signaling?
gbrPartitioning
(H) PA bearer and
paPartitionOverride?
Bearer Setup
Scheduling
Partition based on
PLMN or SPID
Bearer not added
to a partition
E-RAB Setup Request,
Initial Context Setup,
Incoming Handover,
Re-establishment
No
No
No
Yes
Yes
Yes
Figure 1 Bearer Setup
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 11

Steps
1. A mobility action triggers a need to set up a set of new bearers.
2. SRB traffic keeps their priority and is not partitioned. If (High) Priority Access
bearer and QciProfileOperatorDefined.paPartitionOverride or
QciProfilePredefined.paPartitionOverride for the QCI are set to TRUE,
bearer is not added to a partition.
3. If the value of ResourcePartitons.gbrPartitioning is set to TRUE, bearer
is assigned to the appropriate partition based on the serving PLMN or SPID
value of the UE, depending on the cell configuration. The partition is used
during scheduling of radio resources.
4. If the value of ResourcePartitions.gbrPartitioning is set to FALSE,
GBR, IMS an MC signaling bearers are not partitioned.
5. All other bearers are assigned to the appropriate partition, based on the
serving PLMN or SPID value of the UE, depending on the cell configuration.
The partition is used during scheduling of radio resources.
6. Partition information is used during scheduling to try to ensure fair use of
radio resources according to the configured shares.
RELATED INFORMATION
3.2 Scheduling on page 13
3.3 Configuration on page 15
12 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

3.2 Scheduling
Bearers are checked if they belong to the overused partition. In case of
dynamic resource sharing bearers are penalized, while in case of static
resource sharing bearers are not scheduled.
3.2.1 Scheduling in Dynamic Resource Sharing
Scheduling of traffic
for one TTI
Belongs to overused
partition?
Penalize bearer
Scheduling
order
Yes
No
For every bearer
L0001469D
Yes
No
SRB, bearer
not belonging to
a partition?
SRB, bearers not belonging to
a partition and non-penalized bearers
Bearers belonging
to penalized partitions
Figure 2 Scheduling in Dynamic Resource Sharing
Steps
1. All bearers with data to send are checked to see if bearer is SRB or bearer not
belonging to a partition.
2. All remaining bearers are checked to see if they belong to a partition which
has overused its configured share in the previous TTI.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 13

3. Bearers from overused partitions are penalized. If no partition has overused
its share in the previous TTI, no bearers are penalized.
4. The resulting list is sent to the scheduler. In case of resource contention,
bearers belonging to penalized partitions (if any exist) are the last to be
scheduled.
3.2.2 Scheduling in Static Resource Sharing
L0002664C
Scheduling of traffic
for one TTI
SRB, GBR, IMS or MC signaling
bearers, and non-GBR bearers
Do not schedule bearer
For each bearer
Yes
No
Yes
No
Limit for partition crossed
SRB, bearer not belonging to a partition?
Scheduling
order
Figure 3 Scheduling in Static Resource Sharing
Steps
1. All bearers with data to send are checked to see if bearer is SRB or bearer not
belonging to a partition.
2. All remaining bearers are checked to see if partition limit is crossed.
3. If the limit is crossed, the bearer is not scheduled, otherwise it is scheduled
along with SRB and other traffic based on the priority.
14 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

3.3 Configuration
The configuration is done by creating ResourcePartition and
ResourcePartitionGroup MOs, which define the share of radio resources.
0..24
ENodeBFunction
ResourcePartitionGroup
resourceSharingType
EUtranCellFDD/TDD
resourcePartitionGroupRef
PmEventService
cellTracePartitionMcsResolution
ResourcePartitions
gbrPartitioning
ResourcePartition
partitionId: [0, 1..24]
plmnList: [0..6]
spidList: [0..20]
ResourcePartitionGroupMember
resourcePartitionRef:
resourcePartitionShare: [0..100]
0..6
0..24
1
L0001470D
Figure 4 New MO Structure for Radio Resource Partitioning
Configuration of the Radio Resource Partitioning feature is done in the following
way:
1. A set of ResourcePartition MOs is created. The
ResourcePartition.plmnList attribute is used if partitioning is done
based on PLMN, and ResourcePartition.spidList attribute is used if
partitioning is done based on SPID.
Note: The SPID value of 0 can exist in the ResourcePartition.spidList
to include UEs with no SPID value set by the core network. A
partition can be configured using an empty
ResourcePartition.spidList which will include all UEs with any
SPID value.
2. The ResourcecPartitions.gbrPartitioning attribute can be set to TRUE
(by default FALSE) to enable partitioning of GBR traffic.
3. A ResourcePartitionGroup MO is created. The group contains up to six
ResourcePartitionGroupMember MOs. Each MO references an existing
ResourcePartition MO and defines the share (in percentage) of radio
resources the partition can be granted in the cell.
DYNAMIC (by default) or STATIC resource sharing type can be configured for
each cell.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 15

It is possible to use the same partitioning criteria
(ResourcePartition.plmnList or ResourcePartition.spidList) in different
cells with different shares by creating additional ResourcePartititonGroup
MOs. These MOs must reference the same ResourcePartition MOs but
configure different shares.
Note: It is possible for the sum of the shares configured in a
ResourcePartitionGroup MO to be over or under 100%. This benefits
the partitions with the greatest load compared to their configured share.
Each cell that utilizes this feature refers to a ResourcePartitionGroup MO using
attribute EUtranCellFDD.resourcePartitionGroupRef or
EUtranCellTDD.resourcePartitionGroupRef.
RELATED INFORMATION
9.1 20.Q2: Static Resource Sharing on page 26
16 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

4 Network Impact of Radio Resource
Partitioning
This feature has impact on measurement reports from UE.
Capacity and Performance
No impact.
Interfaces
No impact.
Other Network Elements
Measurement reports from UE can be delayed due to resource partitioning.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 17

5 Parameters of Radio Resource Partitioning
The feature introduces new parameters, and affects two existing
parameters.
Table 3 Parameters
Parameter Type Description
ResourcePartition.partiti
onId
Introduced See MOM description.
ResourcePartition.plmnLis
t
ResourcePartition.spidLis
t
ResourcePartitions.gbrPar
titioning
ResourcePartitionGroup.re
sourceSharingType
ResourcePartitionGroupMem
ber.resourcePartitionRef
ResourcePartitionGroupMem
ber.resourcePartitionShar
e
EUtranCellFDD.resourcePar
titionGroupRef
EUtranCellTDD.resourcePar
titionGroupRef
QciProfileOperatorDefined
.paPartitionOverride
QciProfilePredefined.paPa
rtitionOverride
QciProfilePredefined.serv
iceType
Affecting When this parameter is set to
IMS_SIGNALING or
MC_SIGNALING and value of
titioning parameter is set to
FALSE, all bearers with QCI
keep their priority.
18 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

Parameter Type Description
QciProfileOperatorDefined
.serviceType
Affecting When this parameter is set to
IMS_SIGNALING or
MC_SIGNALING and value of
titioning parameter is set to
FALSE, all bearers with QCI
keep their priority.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 19

6 Performance of Radio Resource Partitioning
This feature has impact on the Retainability KPI, the Mobility KPI, and
events which help observe the resource partitions.
KPIs
This feature does not introduce any new Key Performance Indicators (KPIs) or
update any KPI.
The main KPIs that are associated with the feature are the following:
— Retainability KPI
— Cell throughput KPI
— Mobility KPI
If the share of resources assigned to one partition is not enough to sufficiently
serve the current number of UEs in that partition, retainability can be lowered.
Mobility KPI can degrade when the response to a scheduling request for
measurement reports from UE is delayed.
Counters
The following counters are associated with this feature:
— pmPrbUlUtilDistrPartitionN
— pmPrbDlUtilDistrPartitionN
— pmPrbUlUtilGbrDistrPartition
— pmPrbDlUtilGbrDistrPartition
Two new ENIQ PM counters are added for each partition (N), for each resource
type (PRB DL or UL) showing percentage use of the total available resources. For
these new ENIQ PM counters, an ENIQ_events server is required in addition to an
ENIQ_statistics server.
The number of created counters depends on the number of partitions configured
in the eNodeB and the N in the counter name corresponds to the value of
ResourcePartition.partitionId configured in the MO.
It is possible to observe the gains and benefits of the feature by examining the
counters and comparing them to the configured share. This method is only
possible in a controlled scenario (full buffer traffic in each partition) where it is
known that the partitions are fully utilized.
20 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

Events
The following events are related to this feature:
Table 4 Events
Event Event Parameter Description
INTERNAL_PER_PARTITI
ON_REPORT
— EVENT_PARAM_PARTI
TION_ID
— EVENT_PARAM_MEASU
REMENT_PERIOD
TION_PRB_DL_MAX
TION_PRB_DL_MIN
TION_PRB_DL_SUM
TION_PRB_UL_MAX
TION_PRB_UL_MIN
TION_PRB_UL_SUM
— EVENT_PARAM_AVAIL
_PRB_UL_RESOURCES
_PRB_DL_RESOURCES
— EVENT_PARAM_PRB_U
L_UTILIZATION
— EVENT_PARAM_PRB_D
L_UTILIZATION
— EVENT_PARAM_GBR_U
L_UTILIZATION
— EVENT_PARAM_GBR_D
L_UTILIZATION
It reports the use for
each resource type for a
given partition. This
event results in PM
counter pegging.
INTERNAL_PER_UETR_PA
RTITION_REPORT
TION_ID
It reports the use for
each resource type for a
given partition.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 21

— EVENT_PARAM_MEASU
REMENT_PERIOD
TION_PRB_DL_MAX
TION_PRB_DL_MIN
TION_PRB_DL_SUM
TION_PRB_UL_MAX
TION_PRB_UL_MIN
TION_PRB_UL_SUM
_PRB_UL_RESOURCES
_PRB_DL_RESOURCES
— EVENT_PARAM_PRB_U
L_UTILIZATION
— EVENT_PARAM_PRB_D
L_UTILIZATION
— EVENT_PARAM_GBR_U
L_UTILIZATION
— EVENT_PARAM_GBR_D
L_UTILIZATION
INTERNAL_EVENT_PARTI
TION_CONFIG_MISSING
EVENT_PARAM_PARTITIO
N_CONFIG_FAULT_BITMA
P
The event alerts a
potential
misconfiguration of
resource partition
configuration. It uses a
bitmap to specify
configuration problems.
The event is sent when
there are fewer than two
resource partitions
defined in the cell at cell
unlock. If a PLMN exists
22 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

in the Shared RAN
additional PLMN list, but
it does not appear in any
partition currently
configured in the cell,
(both at cell unlock and
upon addition of a new
PLMN to the additional
PLMN list) an event is
sent.
For each cell, the aggregation of the sum, minimum, and maximum values per
active partition for the interval are stored for each type of resource (PRB UL or
PRB DL) and sent in a new event for each partition. There are two new events,
one at UE trace level and one at cell trace level.
For a full list with detailed information about PM events, see the list files in the
List Files library folder.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 23

7 Activate Radio Resource Partitioning
To use the feature, it must be activated following the usual feature
activation procedure.
Prerequisites
The license key is installed in the node.
Continuous Cell Trace Recording (CCTR) is activated since at least one week. This
ensures there is troubleshooting data available if something goes wrong.
Steps
1. Set the attribute featureState to ACTIVATED in the applicable MO
instance, depending on node type:
Node Type License Control MO
DU Radio Node OptionalFeatureLicense=RadioResourcePart
itioning
Baseband Radio Node FeatureState=CXC4012019
After This Task
Let the CCTR be active for one week, for continued collection of troubleshooting
data.
24 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

8 Deactivate Radio Resource Partitioning
If the feature is no longer needed, it can be deactivated following the usual
feature deactivation procedure. It must also be deactivated before the
activation of any conflicting feature.
Prerequisites
Continuous Cell Trace Recording (CCTR) is activated since at least one week. This
ensures there is troubleshooting data available if something goes wrong.
Steps
1. Set the attribute featureState to DEACTIVATED in the applicable MO
instance, depending on node type:
Node Type License Control MO
DU Radio Node OptionalFeatureLicense=RadioResourcePart
itioning
Baseband Radio Node FeatureState=CXC4012019
After This Task
Let the CCTR be active for one week, for continued collection of troubleshooting
data.
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 25

9 Feature Change History
This section lists changes that affected this feature and the impact it had on
the network.
9.1 20.Q2: Static Resource Sharing
This enhancement introduces static resource sharing in shared network
deployments.
Access Type: LTE
Feature Name: Radio Resource Partitioning
Node Type: Baseband Radio Node, DU Radio Node
This enhancement allows the operator to control if a cell uses static or dynamic
(default) resource sharing in Radio Resource Partitioning. In case of static
resource sharing, the non-GBR traffic is strictly limited even if free resources are
available in another partition of the cell. As a result, preconfigured shares for
PLMN-based or SPID-based partitions can be applied both in resource
contention and other configuration types.
Benefits
Static resource partitioning does not allow non-GBR traffic to exceed the
configured share, even if unused capacity is available in the cell. In this way, the
use of unlimited resources can be restricted in shared LTE RAN deployments.
The resource limitation for each partition can lower capacity utilization in each
cell. Lower capacity can lead to throughput degradation.
Operation
The enhancement introduces the
ResourcePartitioningGroup.resourceSharingType attribute to control if the
functionality is enabled for a specific cell.
26 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

Interfaces
No impact.
Hardware
No special hardware requirements.
ENM version 19.4 or later is required for this enhancement.
9.2 20.Q2: GBR Partitioning
This feature enhancement enables the partitioning of GBR bearer, as well as
IMS and mission-critical (MC) signaling bearers. It also enables to override
partition settings for priority access bearers to prevent partitioning them.
Access Type: LTE
Feature Name: Radio Resource Partitioning
Node Type: Baseband Radio Node, DU Radio Node
This enhancement can be used only with Dynamic Resource Sharing. To secure
the priority access traffic in case of emergency, the partition override
configuration for priority access bearers is introduced as well.
Benefits
With this enhancement, the operator can decide if GBR, IMS and MC signaling
bearers are partitioned in the same way as the non-GBR data bearer.
If the cell is overloaded and there is uneven share of GBR bearer in each
partition, GBR QoS degradation can be expected. For example, when in one
partition the GBR load is high, and in the other partition, the GBR load is low.
Operation
This enhancement introduces the following MOM attributes:
238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20 27

— ResourcePartitions.gbrPartitioning
— QciProfilePredefined.paPartitionOverride
— QciProfileOperatorDefined.paPartitionOverride
Benefits of this enhancement can be observed in GBR or non-GBR bearer
scenarios with the following existing PM counters:
— pmPrbDlUtilDistrPartition
— pmPrbUlUtilDistrPartition
The enhancement introduces the following PM counters to check the GBR use for
each partition:
— pmPrbDlUtilGbrDistrPartition
— pmPrbUlUtilGbrDistrPartition
Interfaces
No impact.
Hardware
No special hardware requirements.
ENM version 20.1 or later is required for this enhancement.
28 238/221 04-LZA 701 6014/1 Uen BH13B | 2020-11-20

Radio Resource Partitioning.pdf

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Radio Resource Partitioning.pdf

Similar to Radio Resource Partitioning.pdf (20)

Recently uploaded

Recently uploaded (20)

Radio Resource Partitioning.pdf