Preferential Traffic Management

Guidelines

Operational Guidelines

3/154 43-LZA 701 6014/1 Uen BD13B

Copyright

© Ericsson AB 2017-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.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Contents

Contents

1 Preferential Traffic Management Overview 1

2 Concepts of Preferential Traffic Management 2

2.1 UE and Band Types in Preferential Traffic Management 2
2.2 Traffic Load State 2
2.3 Load Balancing Cycle 4
2.4 Load Balancing Relation 5
2.5 Subscription Ratio 5
2.6 GBR Traffic Load 6
2.7 Non-GBR Traffic Load 6
2.8 Monitored System Resources 7
2.9 Subscriber Profile ID for RAT/Frequency Priority 8

3 Features Used in Preferential Traffic Management 9

3.1 Admission-Triggered Offload Overview 11
3.2 Best Neighbor Relations for Intra-LTE Load Management
Overview 13
3.3 Inter-Frequency Load Balancing Overview 14
3.4 Inter-Frequency Offload Overview 17
3.5 Shared LTE RAN Overview 18
3.6 Subscriber Triggered Mobility Overview 20

4 Implementation of Preferential Traffic Management 22

4.1 Configuration Parameters for Preferential Traffic Management 22
4.2 Cell Profile Configurations for Preferential Traffic Management 25
4.3 Enable Preferential Traffic Management 26
4.4 Suspend Preferential Traffic Management 28
4.5 Disable Preferential Traffic Management 29
4.6 Set PLMN-related Thresholds for Subscription Ratio 31
4.7 Set PLMN-related Thresholds for GBR MSR Usage 31
4.8 Configure Cells for Preferential Traffic Management 32
4.9 Configure SPID-Based Parameters for Preferential Traffic
Management 33

5 Operation of Preferential Traffic Management 35

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

Preferential Traffic Management Guidelines

5.1 Normal Traffic Load Level Operation of Preferential Traffic

Management 35
5.1.1 Restricting Inter-Frequency Load Balancing for a UE Category 36
5.2 High Traffic Load Operation of Preferential Traffic
Management 37
5.2.1 Stopping Inter-Frequency Load Balancing to Priority Cells at
High Subscription Ratio 37
5.3 Very High Traffic Load Operation of Preferential Traffic
Management 39
5.3.1 Allowing the Same Cell as Target Cell for both Inter-Frequency
Load Balancing and Inter-Frequency Offload 41
5.3.2 Inhibiting Idle Mode Prioritization 45
5.3.3 Blocking a Cell for Idle Mode Camping and Incoming
Handover for Non-Priority UEs 48
5.3.3.1 PLMN IDs Reserved Due to Subscription Ratio or MSR Usage 49
5.3.3.2 Blocked Handover to Cells Reserved for Operator Use 51
5.3.4 Subscriber Group-based UE Selection for Offload 53
5.3.5 Enabling or Disabling Admission-Triggered Offload Per Cell for
UEs 53

6 Optimization of Preferential Traffic Management 55

6.1 Optimization of Cell Relations for Preferential Traffic
Management 55
6.2 Optimization of Thresholds for Preferential Traffic
Management 56
6.3 Optimization of PLMN Thresholds for Preferential Traffic
Management 57
6.4 Optimization of Inhibit Timer for Idle Mode Prioritization 60
6.5 Optimization of Admission Triggered Offload 60

7 Performance Management of Preferential Traffic Management 61

8 Maintenance and Troubleshooting Preferential Traffic

Management 63
8.1 UEs of the Wrong Type Are Grouped on Priority Cells 63
8.2 Non-Priority Cells Are Performing Load Balancing Handovers
to Heavily Loaded Priority Cells 64
8.3 Non-Priority Cells Are Not Inhibiting Idle Mode Prioritization
of Priority UEs to Heavily Loaded Priority Cells 66
8.4 Improper Time for Idle Mode Prioritization for Priority UEs 68

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Preferential Traffic Management Overview

1 Preferential Traffic Management Overview

The Preferential Traffic Management solution offers the operator the possibility
to efficiently use an LTE network, deployed on several frequency bands, with one
frequency band used primarily for priority users. The solution enables the
following:

— To use the priority band for both priority and non-priority users as long as co-
existence rules allow it

— To use the priority band exclusively for priority users in intended traffic
situations

— To use the non-priority bands for both non-priority and priority users, both as
coverage bands and bands to offload priority traffic when the priority band is
overloaded

The load management policies used depend on the current traffic load level.
Traffic load states in the solution are defined by configurable load threshold
parameters.

The solution is developed for existing commercial RAN infrastructure with a

designated band used as priority band, using an MOCN architecture. The solution
is achieved by a collection of extensions in existing licensed features, configured
to work together.

RELATED INFORMATION

2.1 UE and Band Types in Preferential Traffic Management on page 2

3. Features Used in Preferential Traffic Management on page 9

2.2 Traffic Load State on page 2

5.1 Normal Traffic Load Level Operation of Preferential Traffic Management on

page 35

5.2 High Traffic Load Operation of Preferential Traffic Management on page

37

5.3 Very High Traffic Load Operation of Preferential Traffic Management on

page 39

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 1

 Preferential Traffic Management Guidelines

2 Concepts of Preferential Traffic Management

2.1 UE and Band Types in Preferential Traffic Management

UE Categories
A UE category is a group of UEs that are identified with the same value or values
of SPID and PLMN.

Priority UE UEs priority to have access to the network and transfer

data even in situations of congested traffic.

For example, if Preferential Traffic Management is used

for public safety purposes, priority UEs are of first
responder type staff, such as police or firefighters.

Non-priority UE UEs of non-priority subscribers.

Frequency Band Types

Priority Band Band primarily used by priority UEs.

Non-Priority Band
Band primarily used by non-priority UEs. Any band other
than the priority band.

2.2 Traffic Load State

A traffic load state is defined by a threshold and a set of actions that a source or a
target cell, or both, perform in that state. The thresholds for traffic load states are
defined using GBR MSRs and subscription ratio.

2 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Concepts of Preferential Traffic Management

Non-prioritized traffic load traffic load state = “Inhibit idle mode prioritiza
Prioritized traffic load traffic load state = “Stop incoming IFLB” (+ implicitly “Stop incoming IFLB”)

lbEUtranTriggerOffloadThreshold
(legacy)

stopIncomingIflbThreshold
(new)

Note:
The measured cell traffic load is the sum of non-prioritized and prioritized load.
L

Figure 1 Traffic Load States and Thresholds

The Preferential Traffic Management solution defines two traffic load states:

Stop incoming IFLB

The state is instated when the subscription ratio in a cell
is above the threshold
PtmIflbConfig.stopIncomingIflbThreshold.

The state is exited when the subscription ratio in the cell

falls below or equal to threshold
PtmIflbConfig.stopIncomingIflbThreshold.

The priority cell in this traffic load state does not let
neighbor non-priority cells initiate load balancing
handover to itself. This function needs to be enabled.

Inhibit idle mode prioritization

The state is instated when the subscription ratio in a cell
is above the legacy offload threshold
EUtranCellFDD.lbEUtranTriggerOffloadThreshold
or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold,
or a GBR MSR usage exceeds
AdmissionControl.lbAtoThresholdLevel1 .

The state is exited when the cell subscription ratio is

below or equal to
EUtranCellFDD.lbEUtranTriggerOffloadThreshold
or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold,

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 3

 Preferential Traffic Management Guidelines

and a GBR MSR usage is below

AdmissionControl.lbAtoThresholdLevel1.

The priority cell in this traffic load state forces

neighboring non-priority cells to inhibit idle mode
prioritization for preconfigured SPID values.

Reaching this traffic load state implies that the

neighboring cells consider this cell like being both in
traffic load states "Stop incoming IFLB" and "Inhibit idle
mode prioritization".

2.3 Load Balancing Cycle

The load balancing cycle is the time interval between two successive
evaluations of traffic load balancing status. It is the time frame for the
actions attempting to restore the traffic load balance.

Load balancing between cells is done repeatedly in successive load balancing

cycles of 15 seconds.

Load measurement

Load information exchange

15 seconds

Load balancing action magnitude

UE selection for load balancing action

L0001854B

Figure 2 Load Balancing Cycle

Load Measurement
The load of each cell is estimated.

4 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Concepts of Preferential Traffic Management

Load Information Exchange

Load information is exchanged between source and
target cells.

For inter-eNodeB load exchange, X2 messages are used.

Load Balancing Action Magnitude

The amount of offloading required to manage load
between cells is determined.

Higher loaded cells select some UEs as candidates for

load balancing. The selected UEs are configured for event
A5 inter-frequency measurement.

UE Selection for Load Balancing Action

The UEs suitable for offload are selected. The suitable
UEs are those that reported to the source cell that they
detected sufficient coverage in a target cell.

Some suitable UEs are moved to detected target cells by

inter-frequency handover.

2.4 Load Balancing Relation

The load balancing relation is the logical relation between a load balancing
source and a target cell. Load balancing relations are controlled with the
EUtranCellRelation.loadBalancing attribute.

For load balancing features to steer traffic from one source cell to a target cell, a
relation must be defined in the source cell. This relation is defined to the target
cell using the EUtranCellRelation MO. The
EUtranCellRelation.loadBalancing attribute controls whether load
balancing, or offload, or both are allowed.

Note: Each defined load balancing relation is unidirectional.

2.5 Subscription Ratio

Subscription ratio is a relative traffic load measure. It is the ratio between
the total QCI subscription quanta of all E-RAB instances currently
configured in a cell and the cell subscription capacity of the cell.

It takes a value between zero and one for an under-subscribed cell. Values
greater than one indicate an over-subscribed cell.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 5

 Preferential Traffic Management Guidelines

∑
=

Figure 3 Subscription Ratio

The configuration of the following values has to obtain the required load
balancing behavior:
— qciSubscriptionQuanta (in MOs QciProfilePredefined or
QciProfileOperatorDefined)

— cellSubscriptionCapacity (in MOs EUtranCellFDD or EUtranCellTDD)

This enables load balancing between cells with different UE groups, and cells
with different traffic capacities.

Configuration of the assessment model offers control of the load balancing

objectives in LTE RAN and opportunity for further changes.

The subscription ratio can be used to monitor the traffic load in a cell.

2.6 GBR Traffic Load

GBR traffic is characterized by a relatively persistent E-RAB that generates a
steady data stream. For example, an E-RAB for a voice call typically lasts for one
or a few minutes. During the voice call, a stream of voice packets is transferred at
a nearly constant rate.

Therefore, the number of E-RABs for GBR traffic present in a cell is a good basis
for the assessment of the GBR traffic load.

2.7 Non-GBR Traffic Load

Non-GBR traffic is typically characterized by short but frequent data
transactions. The individual data transactions can range from a few data packets
to the transfer of large files. Many data transactions are completed within a short
time, often less than a few seconds.

Non-GBR traffic has the following pattern:

1. The UE enters connected mode.

2. The E-RABs are established.

6 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Concepts of Preferential Traffic Management

3. The data transaction, or a sequence of data transactions proceeds.

4. The UE is released after a period of inactivity.

This pattern is repeated, but each RRC connection and each E-RAB for the node
is unique. The node is unable to correlate the different RRC connections
generated by a UE.

Non-GBR traffic patterns are difficult to predict because they change often and
quickly. The activity of an individual UE or E-RAB does not necessarily give much
information about the activity a few seconds ahead. The number of E-RABs
presented by the UEs to the LTE RAN can be used to assess the non-GBR traffic
load generated by the UE groups. This applies for a UE group camped in a cell.

2.8 Monitored System Resources

RBS considers its MSRs to decide if it can admit a request or not, see Figure 4.
Each MSR represents the utilization of a system resource that potentially is a
bottleneck in the RBS. Moreover, the MSR represents the accumulated resource
utilization from all admitted requests.

Resource
Request Admit/Reject

Admission Request/Response
Control

MSRs

L0000674A

Figure 4 Admission Control Checks the MSRs

The MSRs can be either static or dynamic, see Figure 5. Requests can be
admitted (indicated as up) and released (indicated as down). The resource
consumption to a static MSR because of an admitted request does not vary
during the time the request is served by the RBS. The resource consumption
changes if a specific modification request, for example an E-RAB Modify Request
on S1AP, is issued. The resource consumption to a dynamic MSR because of an
admitted request can vary during the time the request is served by the RBS. The
variations depend on the scheduler, radio conditions, or mobility.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 7

 Preferential Traffic Management Guidelines

Consideration of dynamic MSRs for GBR traffic is part of the Dynamic GBR
Admission Control feature and protects QoS of already admitted E-RABs.

Note: If the Enhanced PTT Admission Control feature is activated, the

downlink PTT dynamic MSR reservations are considered when checking
the admission-triggered offload thresholds.

MSR Static MSR

utilization

Time
MSR Dynamic MSR
utilization

Time

L0000677A

Figure 5 Static versus Dynamic MSRs

2.9 Subscriber Profile ID for RAT/Frequency Priority

The SPID parameter received by the node through the S1 interface is an index
referring to user information for mobility profile and service use profile. The
information is UE-specific and applies to all its radio bearers. This index is
mapped by the node to locally defined configuration to apply specific RRM
strategies. The strategies include defining RRC_IDLE mode priorities and control
IRAT, intra-frequency, or inter-frequency handover in RRC_CONNECTED mode.

8 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

3 Features Used in Preferential Traffic

Management

Features
The Preferential Traffic Management solution can only work if all of the
prerequisite features are activated on each node in the network. This is crucial if a
node includes cells using frequencies that belong to both the priority band and
non-priority bands.

The recommended features need not be active for the solution to work properly.
Using these features is recommended to avoid manual configuration of cell
relations for offload and load balancing.

Note: It is not recommended to use Preferential Traffic Management together

with Radio Resource Partitioning feature.

Table 1 Features Used in Preferential Traffic Management

Feature Relationship Description
Admission-Triggered Offload (FAJ 121 Prerequisite Admission-Triggered Offload can be
3100) enabled per cell in a node to given target
frequencies for UEs configured with a
specific SPID.
When Admission-Triggered Offload is
triggered, the priority cell enters "Inhibit
idle mode prioritization" traffic load state.
Depending on the priority order in
Preferential Traffic Management, UEs at
the bottom of the offload list are offloaded
first, while UEs at the top of the offload list
are offloaded last.
The GBR MSR usage of cells—used for
determining the operation of Admission-
Triggered Offload—is measured to decide
if configured PLMNs are "reserved", and
incoming handover of UEs with matching
SPID is blocked.
Inter-Frequency Load Balancing(1) (FAJ Prerequisite Inter-Frequency Load Balancing is used to
121 3009) move UEs to frequency bands intended as
their primary usage.
Inter-frequency load balancing can be
stopped for some cells—to priority cells
with high traffic load from non-priority
cells. This allows the priority band to be
used primarily to serve priority users, and
ensures access for priority UEs in high
traffic load situations.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 9

 Preferential Traffic Management Guidelines

Feature Relationship Description

Inter-Frequency Offload(1) (FAJ 121 Prerequisite Inter-Frequency Offload is used to move

3061) UEs to frequency bands intended as their
primary usage.
Depending on the priority order in
Preferential Traffic Management, UEs at
the bottom of the offload list are offloaded
first, while UEs at the top of the offload list
are offloaded last.
Inter-Frequency Offload threshold—
EUtranCellFDD.lbEUtranTriggerOffload
Threshold or
EUtranCellTDD.lbEUtranTriggerOffload
Threshold—is used to determine when a
cell enters "Inhibit idle mode prioritization"
traffic load state.
Shared LTE RAN (FAJ 121 0860) Prerequisite The Shared LTE RAN feature allows to
configure multiple PLMN on one node.
This allows to configure the function of
reserving PLMN IDs, which is required for
Preferential Traffic Management.
Subscriber Triggered Mobility (FAJ 121 Prerequisite When the traffic load is not very high, the
1788), RFPM function RFPM function of Subscriber Triggered
Mobility ensures idle mode prioritization of
priority UEs to priority bands, and non-
priority UEs to non-priority bands. This
makes sure that the correct users end up
on the bands intended as their primary
usage.
Idle mode prioritization can be inhibited
between some cells—to priority cells with
very high traffic load from non-priority
cells. This ensures that priority cells are not
overloaded, so priority UEs have access in
very high load traffic situations.
Automated Neighbor Relations (FAJ 121 Recommended The Automated Neighbor Relations
0497) feature can be used to automatically
create neighbor cell relations based on
measurement from the UEs.
Best Neighbor Relations for Intra-LTE Recommended The feature, Best Neighbor Relations for
Load Management (FAJ 121 3028) Intra-LTE Load Management can be used
to automatically configure neighbor cell
relations.
For automatic configuration of neighbor
cells for both Inter-Frequency Load
Balancing and Inter-Frequency Offload,
attribute
EUtranFreqRelation.lbBnrPolicy must
be set to IFO_AND_IFLB.

(1) Automatic access class barring—the Load-Based Access Barring, Progressive Access Barring, PLMN-Specific Access
Barring, and the Progressive Barring for Special Access Classes feature—does not affect the operation of Preferential
Traffic Management at high load in priority cells.
If the Preferential Traffic Management solution is enabled, by setting the PtmFunction.ptmEnabled attribute to TRUE, and the cell is
configured as priority cell, triggering of the access class barring calculation mechanism does not disable the following events:

— Subscription ratio evaluation

— Inter-Frequency Load Balancing

— Inter-Frequency Offload

A cell is configured as priority cell if the following is true:

— PtmCellProfile.cellType is set to PRIORITY.

— The EUtranCellFDD.ptmCellProfileRef or the EUtranCellTDD.ptmCellProfileRef reference to a cell profile is set as

priority.

10 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

RELATED INFORMATION

1. Preferential Traffic Management Overview on page 1

5.1 Normal Traffic Load Level Operation of Preferential Traffic Management on

page 35

5.2 High Traffic Load Operation of Preferential Traffic Management on page

37

5.3 Very High Traffic Load Operation of Preferential Traffic Management on

page 39

3.1 Admission-Triggered Offload Overview

The feature monitors GBR load, based on MSR, also used for admission
control. If the load is above a threshold, new UEs in connected mode are
moved to another LTE frequency or to WCDMA frequency.

Access Type: LTE

Feature Identity: FAJ 121 3100
Value Package Name: Service-Based Mobility
Value Package Identity: FAJ 801 0433
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license for each
node.

Summary
The Admission-Triggered Offload feature helps to control the load created by
GBR bearers in LTE cells. The feature offloads the UEs to other LTE frequency or
RAT when the GBR usage of the source cell exceeds some ATO threshold. This
ensures efficient utilization of resources in the LTE and available IRAT resources.

The offload of UEs with GBR bearers is triggered before admission rejection or
service degradation starts to occur. The underlying trigger mechanism uses MSR
to signal exceeded resource usage.

Admission-Triggered Offload offers the following benefits:

— Enables more efficient GBR overload handling.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 11

 Preferential Traffic Management Guidelines

— Enables better service quality during degradation for GBR bearers already
set up in the system.

— Minimizes the rate of rejections for services requiring GBR bearers and
thereby contributes to a good end-user experience.

— Provides better utilization of resources in the LTE as well as the involved

WCDMA cells.

Additional Information
More information about the Admission-Triggered Offload and related topics can
be found in the following documentation:

— 3GPP TS 36.331, Radio Resource Control (RRC)

— 3GPP TS 36.413, S1 Application Protocol (S1AP)

— 3GPP TS 36.423, X2 Application Protocol (X2AP)

— Best Neighbor Relations for WCDMA IRAT Offload

— Best Neighbor Relations for Intra-LTE Load Management

— Carrier Aggregation-Aware IFLB

— Coverage-Triggered WCDMA IRAT Handover

— Coverage-Triggered Inter-Frequency Handover

— Differentiated UE Handling

— Inter-Frequency Load Balancing

— Inter-Frequency Offload

— Inter-RAT Offload to WCDMA

— Preferential Traffic Management Guidelines

— Service Specific Load Management

— Service or Priority-Triggered Inter-Frequency Handover

— SRVCC Handover to UTRAN

— Subscriber Triggered Mobility

— UE Throughput-Aware IFLB

12 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

3.2 Best Neighbor Relations for Intra-LTE Load

Management Overview
Best Neighbor Relations for Intra-LTE Load Management feature provides
automatic configuration of load management relations.

Access Type: LTE

Feature Identity: FAJ 121 3028
Value Package Name: Multi-Carrier Load Management
Value Package Identity: FAJ 801 0427
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license per
radio.

Summary
The purpose of the Best Neighbor Relations for Intra-LTE Load Management
feature is to evaluate whether inter-frequency neighbor cells are suitable for
inter-frequency load balancing or inter-frequency offload. Suitable inter-
frequency neighbor cells are automatically and dynamically configured as load
balancing relations. It reduces the need for manual configuration of load
management relations.

The benefits of Best Neighbor Relations for Intra-LTE Load Management are the
following:

— This automatic configuration is crucial in network deployments with several

frequency layers and different cell grids. Manual configuration is difficult in
such network deployments.

— Dynamic configuration of load management relations improves load

management efficiency and reduces the workload of manual configuration.

— By considering suitable targets and removing unsuitable targets, load

balancing is optimized and used to determine the amount of traffic load that
is handed over to each target cell. Additional unsuitable target cells in the list
reduce the chance of utilizing suitable targets and can also increase the
number of unnecessary UE measurements.

Additional Information
For information on the preferred state and parameter settings of this feature, see
RAN Parameter Recommendations Lists.

More information about this feature and related topics can be found in the
following documentation:

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 13

 Preferential Traffic Management Guidelines

— 3GPP TS 36.300, Overall description; Stage 2

— The benefits of Best Neighbor3GPP TS 36.331, Radio Resource Control

(RRC); Protocol Specification

— 3GPP TS 36.423, X2 Application Protocol (X2AP)

3.3 Inter-Frequency Load Balancing Overview

Access Type: LTE
Feature Identity: FAJ 121 3009
Value Package Name: Multi-Carrier Load Management
Value Package Identity: FAJ 801 0427
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license required
per node.

Summary
The purpose of inter-frequency load balancing is to manage uneven distribution
of traffic load between different carrier frequencies. It enables efficient use of
network resources on multiple carrier frequencies, and achieves similar user
experience independent of the carrier in use. Load balancing is achieved by User
Equipment (UE) in connected mode is relocated to carriers that are underused in
comparison with the carrier in use.

The feature introduces a method to assess traffic load. The method is based on
the presence of E-RABs in the cell and the QoS class to which they belong.

The Inter-Frequency Load Balancing feature is realized as a network feature.

Neighboring nodes cooperate and perform the traffic load adjustments, without a
central node controlling those efforts.

The Inter-Frequency Load Balancing feature can be inter-mode (FDD and TDD) if
the Intra-LTE Inter-Mode Handover feature is activated.

The Inter-Frequency Load Balancing feature supports the following:

— An arbitrary grade of coverage overlap between cells

— An arbitrary number of target cells on the same inter-frequency

— An arbitrary number of frequencies and frequency bands

— Load balancing between cells that are co-located and not co-located

— Load balancing between cells in the same and in separate nodes

14 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

Frequency

Distance
L0000565A

Figure 6 Traffic Moving Between Inter-Frequency Cells Covering a Common

Geographical Area Due to Load Balancing

To support load balancing between cells in separate nodes, the feature requires
an Ericsson node in both ends.

The feature provides the following benefits:

— Distributes radio traffic load between inter-frequency cells with overlapping

coverage.

For example, lower carrier frequencies can have better coverage and
propagation characteristics and attract more traffic than higher frequencies.
This can result in the underuse of high frequency carriers. The Inter-
Frequency Load Balancing feature distributes radio use evenly over all
carriers, which maximizes the availability of radio resources.

— Helps enhance the non-GBR end user experience.

— Reduces the risk of blocking and allows more UEs in an area where multiple
carrier frequencies are used.

— Allows the average user throughput to increase linearly when adding new
carrier frequencies or increasing the RF spectrum by other means.

— Enhances observability of the traffic load in network on a per cell basis, using
subscription ratio.

Additional Information
For information on the preferred state and parameter settings of this feature, see
RAN Parameter Recommendations Lists.

More information about this feature and related topics can be found in the
following documentation:

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 15

 Preferential Traffic Management Guidelines

— 3GPP TS 36.300, Overall description; Stage 2

— 3GPP TS 36.331, Radio Resource Control (RRC); Protocol Specification

— 3GPP TS 36.423, X2 Application Protocol (X2AP)

— Admission-Triggered Offload

— Automated Cell Capacity Estimation

— Best Neighbor Relations for Intra-LTE Load Management

— Best Neighbor Relations for WCDMA IRAT Offload

— Coverage-Adapted Load Management

— Coverage-Triggered Inter-Frequency Handover

— Coverage-Triggered Inter-Frequency Session Continuity

— Dynamic GBR Admission Control

— Idle Mode Support

— Inter-Frequency Offload

— Inter-RAT Offload to WCDMA

— Limited-Uplink-Aware IFLB

— Overlaid Cell Detection

— Preferential Traffic Management Guidelines

— Radio Bearer Service

— Service Specific Load Management

— Service Triggered Mobility

— Shared LTE RAN

— Subscriber Triggered Mobility

— UE Throughput-Aware IFLB

16 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

3.4 Inter-Frequency Offload Overview

The feature is part of load management. It is used to offload traffic to the E-
UTRAN network if the traffic load in the E-UTRAN cells exceeds a
configured level.

Access Type: LTE

Feature Identity: FAJ 121 3061
Value Package Name: Inter-Vendor Load Management
Value Package Identity: FAJ 801 0416
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license required
for each node.

Summary
The Inter-Frequency Offload feature is part of the Load Management features.
Load balancing relations are configured between two E-UTRAN cells. The Inter-
Frequency Offload feature is used to offload traffic to the E-UTRAN network
(Ericsson or non-Ericsson E-UTRAN FDD or TDD cells) if the traffic load in the E-
UTRAN cells exceeds a configured level.

The feature uses the function introduced by the Inter-Frequency Load Balancing
feature for the assessment of traffic load based on the presence of E-RABs in the
cell and the QoS class to which they belong.

This feature is an alternative feature of Inter-Frequency Load Balancing. The

main difference is there is no load information exchange between the cells in the
Inter-Frequency Offload feature.

The Inter-Frequency Offload feature provides the following benefits:

— Certain operators can use the spectrum and equipment in a more efficient
way by pushing traffic between the carriers. This applies to operators that
have agreements with other operators with overlaying carriers, and
operators that have overlaying carriers operated by nodes of different
vendors.

— It reduces the risk for a UE to be trapped in an overused E-UTRAN cell

providing poor performance.

— It enhances the usage of all frequencies within a network.

— Inter-frequency offload can be applied in different network topologies where

a large number of small inter-frequency cells exists, that are not feasible for
load balancing. For example, heterogeneous network or small cell
deployments.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 17

 Preferential Traffic Management Guidelines

Additional Information
More information about this feature and related topics can be found in the
following documentation:
— 3GPP TS 36.413; E UTRAN S1 Application Protocol (S1AP)

— 3GPP TS 36.423, X2 Application Protocol (X2AP)

3.5 Shared LTE RAN Overview

The feature supports sharing of LTE RAN between operators up to six
operators. The 3GPP defined configurations Multi Operator Core Network
(MOCN) and Gateway Core Network (GWCN) are supported.

Access Type: LTE

Feature Identity: FAJ 121 0860
Value Package Name: Shared Networks
Value Package Identity: FAJ 801 0434
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license for each
radio node.

Summary
The Shared LTE RAN feature supports the following configurations:
GWCN Both the eNodeB and the MME are shared by two or more
operators. All the cells and frequencies are shared. The
Shared LTE RAN feature enables up to six operators with
up to six PLMNs to share an LTE RAN. Without the
feature, a PLMN consists of a RAN and a core network,
through which one operator provides services to its
subscribers, while subscribers of other operators can only
receive services as national or international roamers.

GWCN as MORAN
Both the eNodeB and the MME are shared by two or more
operators, but by network configuration non-shared cells
can be enabled (dedicated frequency for each operator).

MOCN Two or more operators share one eNodeB while the core
network is dedicated for each operator.

MORAN Two DUs or Baseband units that belong to different

operators can share radio units and the support system.

18 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

Operators have their own carriers and individual

configuration of all parameters. For more details, see
Multi-Operator RANThe Shared LTE RAN feature enables
up to six operators with up to six PLMNs to share feature
description.

MOCN as MORAN
Two or more operators share eNodeB but by network
configuration non-shared cells can be enabled (dedicated
frequency for each operator).

These configurations are standardized scenarios for network sharing as in 3GPP

TS23.251.

Non-Shared Spectrum Shared Spectrum

1. 2. 3. 4. 5. 6. 7. 8. 9.
Site MOCN MOCN GWCN MORAN Geographical GWCN GWCN MOCN
Sharing as MORAN as MORAN as MORAN with Split (Scenario 1) (Scenario 2)
(separate (shared two DUs or Networks
RUs) RUs) Basebands (National
Roaming)

PDN GW, HSS

and applications

SGW

MME

eNodeB
(DU or BB and RU)

Cell

Shared Baseband MORAN Defined in 3GPP

enabling mechanisms not
in 3GPP specified in
3GPP
Nodes or resources of Operator A

Nodes or resources of Operator B

Shared nodes or resources
Control plane and user plane
User plane only

L0002569

Figure 7 Shared LTE RAN Configurations

The Shared LTE RAN feature allows the operators to share a common RAN. This
provides substantial cost reductions and a reduced environmental footprint.

Additional Information
More information about this feature and related topics can be found in the
following documentation:

— 3GPP TS 36.413, S1 Application Protocol (S1AP)

— 3GPP TS 36.423, X2 Application Protocol (X2AP)

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 19

 Preferential Traffic Management Guidelines

— 3GPP TS 36.331, Radio Resource Control (RRC); Protocol Specification

— 3GPP TS 23.251, Network Sharing; Architecture and Functional Description

— 3GPP TS 36.300, Evolved Universal Terrestrial Radio Access (E-UTRA) and

Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall
description; Stage 2

— 3GPP TS 23.122, Non-Access-Stratum (NAS) functions related to Mobile

Station (MS) in idle mode

3.6 Subscriber Triggered Mobility Overview

The Subscriber Triggered Mobility feature enables individual control of
mobility characteristics for a UE based on SPID.

Access Type: LTE

Feature Identity: FAJ 121 1788
Value Package Name: LTE Base Package
Value Package Identity: FAJ 801 0400
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license for
each radio.

Summary
The use of SPID makes it possible to create and sell differentiated subscription
types. For example, a high-rate subscription can offer the highest possible
throughput for the end-user, whereas a low rate subscription offers lower
throughput for the end-user. If not used, the node cannot differentiate the UE
based on its subscription profile, so the node gives every user priority and
throughput based on the default criteria.

Telephone-only subscribers or low data-rate subscriptions can be directed to

move to a RAN that offers lower data-rate networks than E-UTRAN.

With the RFPM function of this feature, the operator can configure new
frequencies and priorities that only affect a given SPID value. This enables the
operator to define "test-UE" subscriptions as the only UEs that are affected by the
new frequency and priorities. Once tested and proven, the configuration can be
applied for all UEs. This reduces or removes the need to temporarily disable part
of the RAN to try out new configurations.

The ORC function of this feature uses SPID to determine if a UE is allowed to

perform incoming handover to cells that are in mode "reserved for operator use".

20 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Features Used in Preferential Traffic Management

Only UEs with specific SPID values are allowed access. This enables the operator
to define a "test-UE" that is allowed access, but all others are blocked. The "test-
UE" is then used for testing the ORC.

Additional Information
More information about the Subscriber Triggered Mobility feature and related
topics can be found in the following documentation:

— 3GPP TS 36.413 S1 Application Protocol (S1AP)

— 3GPP TS 36.423 X2 Application Protocol (X2AP)

— 3GPP TS 36.300 Overall description; Stage 2

— 3GPP TS 36.304 User Equipment (UE) procedures in idle mode

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 21

 Preferential Traffic Management Guidelines

4 Implementation of Preferential Traffic

Management

4.1 Configuration Parameters for Preferential Traffic

Management

Table 2 Feature Parameters

Parameter Type Description
EUtranCellFDD.ptmCel Introduced See MOM description.
lProfileRef
EUtranCellTDD.ptmCel
lProfileRef
PtmAtoConfig.minSucc
RateThreshold
PtmAtoConfig.ptmSubs
criberGroupRef
PtmCellProfile.cellT
ype
PtmFunction.ptmEnabl
ed
PtmIflbConfig.stopIn
comingIflbThreshold
PtmIflbConfig.stopOu
tgoingIflbEnabled
PtmIfoConfig.ptmSubs
criberGroupRef
PtmResOpUseConfig.pt
mSubscriberGroupRef
PtmResOpUseConfig.re
sMsrUsageThreshold
PtmResOpUseConfig.re
sSRatioThreshold
PtmResOpUseConfig.un
resMsrUsageThreshold
PtmResOpUseConfig.un
resSRatioThreshold

22 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Implementation of Preferential Traffic Management

Parameter Type Description

PtmStmConfig.inhibit
ImpInterval
PtmStmConfig.ptmSubs
criberGroupRef
PtmSubscriberGroup.s
pidList
PtmSubscriberGroup.p Introduced See MOM description.
lmn
The attribute references
the struct
PlmnIdentity. The
struct has the following
members:
— mcc

— mnc

— mncLength
offloadAllowed Introduced See MOM description.
Member of struct
FreqPrioEUTRA. The
parameter references
from the RATFreqPrio
MO.
EUtranFreqRelation.l Affected New value,
bBnrPolicy IFO_AND_IFLB is
introduced to allow
automatic configuration
for the cell on the given
frequency relation for
offload and load
balancing actions.
Note:
The IFO_AND_IFLB value
can only be used if
Preferential Traffic
Management is enabled
and configured.
EUtranCellRelation.l Affected New value
oadBalancing IFO_AND_IFLB is
introduced for the
attribute to allow Inter-
Frequency Offload and
Inter-Frequency Load
Balancing for the cell.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 23

 Preferential Traffic Management Guidelines

Parameter Type Description

Note:
The IFO_AND_IFLB value
can only be used if
Preferential Traffic
Management is enabled
and configured.

The
EUtranCellRelation.l
oadBalancing attribute
controls if Inter-
Frequency Load
Balancing or Inter-
Frequency Offload is
allowed between cells.
RATFreqPrio.freqPrio Affected The attribute references
ListEUTRA the FreqPrioEUTRA
struct.
Offloading behavior can
be controlled by
offloadAllowed struct
member if
loadBalancingAllowed
struct member is set to
FALSE.
Note:
The parameter requires
that Preferential Traffic
Management is enabled.

Priority UEs, defined

with SPID, are not
allowed for Inter-
Frequency Load
Balancing. This can be
set using attribute
loadBalancingAllowed.
EUtranCellFDD.lbEUtr Affecting The
anTriggerOffloadThre EUtranCellFDD.lbEUtr
shold anTriggerOffloadThre
shold and the
EUtranCellTDD.lbEUtr
EUtranCellTDD.lbEUtr
anTriggerOffloadThre
anTriggerOffloadThre
shold
shold attributes are
used to define traffic
load state "Inhibit idle
mode prioritization".

24 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Implementation of Preferential Traffic Management

Parameter Type Description

When a cell is configured
for both Inter-Frequency
Load Balancing and
Inter-Frequency Offload,
EUtranCellFDD.lbEUtr
anTriggerOffloadThre
shold or
EUtranCellTDD.lbEUtr
anTriggerOffloadThre
shold is used to decide if
offload-like or load
balancing-like actions
are performed when the
traffic load is very high.

4.2 Cell Profile Configurations for Preferential Traffic

Management
The PtmCellProfile.cellType attribute can be set to PRIORITY in profiles
for priority cells, and to NON_PRIORITY in profiles for non-priority cells.

Table 3 Configurations for Cell Profiles

Parameter PtmCellProfile.cellT PtmCellProfile.cellT
ype is set to PRIORITY ype is set to
NON_PRIORITY
PtmAtoConfig.minSucc The attribute is set to 50. N/A
RateThreshold
PtmAtoConfig.ptmSubs The attribute references N/A
criberGroupRef instances of
PtmSubscriberGroup,
and defines the offload
order.
PtmIflbConfig.stopOu N/A Attribute is set to true.
tgoingIflbEnabled
PtmIflbConfig.stopIn The attribute is set to 60. N/A
(1)
comingIflbThreshold
PtmIfoConfig.ptmSubs The attribute references N/A
criberGroupRef instances of
PtmSubscriberGroup,
and defines the offload
order.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 25

 Preferential Traffic Management Guidelines

Parameter PtmCellProfile.cellT PtmCellProfile.cellT

ype is set to PRIORITY ype is set to
NON_PRIORITY
PtmResOpUseConfig.pt The attribute references N/A
mSubscriberGroupRef instances of
PtmSubscriberGroup,
and defines which UEs
are not allowed by the
cell when the reserved
for operator use
functionality is triggered.
PtmStmConfig.inhibit N/A The attribute is set to 60.
ImpInterval
PtmStmConfig.ptmSubs N/A The attribute references
criberGroupRef instances of
PtmSubscriberGroup.
(1) The default threshold parameters are recommended. The thresholds can be changed to achieve
the desired behavior, provided that the required relationships between them are preserved.

4.3 Enable Preferential Traffic Management

Prerequisites
On the nodes used in the Preferential Traffic Management solution the following
features are activated and enabled in the used cells:

— Admission-Triggered Offload (FAJ 121 3100)

— Inter-Frequency Load Balancing (FAJ 121 3009)

— Inter-Frequency Offload (FAJ 121 3061)

— Shared LTE RAN (FAJ 121 0860)

— Subscriber Triggered Mobility (FAJ 121 1788), the RFPM function

Steps

1. Configure subscriber groups to create a Preferential Traffic Management

group.

a. Create an instance on PtmSubscriberGroup.

b. Set PtmSubscriberGroup.plmn.

c. Set PtmSubscriberGroup.spidList.

26 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Implementation of Preferential Traffic Management

2. Create the required PtmCellProfile instances.

3. Configure load balancing relations to allow load balancing from any cells,
and allow offload from priority cells to non-priority cells.

a. From priority cells to non-priority cells, set attribute

EUtranCellRelation.loadBalancing to IFO_AND_IFLB.

b. From non-priority cells to priority cells, set attribute

EUtranCellRelation.loadBalancing to ALLOWED.

Note: Enabling Automated Neighbor Relations and Best Neighbor

Relations for Intra-LTE Load Management features is
recommended to allow automatic configuration of cell relations.

4. Set PtmIflbConfig.stopIncomingIflbThreshold for each priority cell

profile so the value is equal to or lower than the value of
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

5. Enable IFO, ATO, and reserved for operator use function on priority cells.

a. Set the offload order for IFO by using

PtmIfoConfig.ptmSubscriberGroupRef. Groups referenced first
are offloaded first.
b. Set the offload order for ATO by using
PtmAtoConfig.ptmSubscriberGroupRef. Groups that are
referenced first have a higher chance of being offloaded first.
c. Set PtmAtoConfig.minSuccRateThreshold.

Note: Setting this MO to a high value increases the amount of

UEs offloaded, but this can cause the priority groups set
higher to be offloaded earlier.
d. Set PtmResOpUseConfig.ptmSubscriberGroupRef to reference
non-priority user groups that are blocked from entering the cell
during high network congestion. PLMNs that are broadcasted as
reserved are rejected during handovers.
e. Set the value of PtmResOpUseConfig.unresMsrUsageThreshold
lower than the value of
PtmResOpUseConfig.resMsrUsageThreshold.

f. Set the value of PtmResOpUseConfig.unresSRatioThreshold

lower than the value of
PtmResOpUseConfig.resSRatioThreshold.

6. Enable STM enhancements on non-priority cells.

a. Set PtmStmConfig.ptmSubscriberGroupRef to reference priority

subscriber groups that are to be blocked from redirecting towards
priority cells when changing their state to Idle Mode.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 27

 Preferential Traffic Management Guidelines

7. Reference a PtmCellProfile using the

EUtranCellFDD.ptmCellProfileRef or
EUtranCellTDD.ptmCellProfileRef in each cell used in the Preferential
Traffic Management solution, depending on the required configuration.
Priority cells reference cell profiles where PtmCellProfile.cellType =
PRIORITY, while non-priority cells reference cell profiles where
PtmCellProfile.cellType = NON_PRIORITY.

8. Set the parameters in FreqPrioEUTRA struct for priority SPIDs. These

parameters are associated with the target carrier frequencies in
RATFreqPrio.freqPrioListEUTRA.

a. Set loadBalancingAllowed to FALSE.

b. Set offloadAllowed to TRUE.

c. Set the value of cellReselectionPriority.

9. Enable the Preferential Traffic Management function on eNodeB level by

setting PtmFunction.ptmEnabled to TRUE.

RELATED INFORMATION

2.1 UE and Band Types in Preferential Traffic Management on page 2

2.2 Traffic Load State on page 2

4.8 Configure Cells for Preferential Traffic Management on page 32

4.9 Configure SPID-Based Parameters for Preferential Traffic Management on

page 33

4.4 Suspend Preferential Traffic Management

If the Preferential Traffic Management solution is still needed, but it must be
turned off temporarily, it can be done by performing this task.

The configuration of Preferential Traffic Management affects the configuration of

the used features. Hence, when turning the solution off, legacy configurations
must be reset.

Steps

1. Set PtmFunction.ptmEnabled to the default value, FALSE.

28 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Implementation of Preferential Traffic Management

Result: The functions of the Preferential Traffic Management are no longer

operating.

2. Set the EUtranFreqRelation.lbBnrPolicy attribute to the default value to

disallow automatic setting of load balancing relations for both Inter-
Frequency Offload and Inter-Frequency Load Balancing.

3. Set EUtranCellRelation.loadBalancing to ALLOWED or OFFLOAD—if the

attribute was previously set to IFO_AND_IFLB— depending on desired
behavior for all load balancing relations that allow both Inter-Frequency
Offload and Inter-Frequency Load Balancing.

4. Revise configurations in FreqPrioEUTRA struct for attribute

RATFreqPrio.freqPrioListEUTRA, as follows:

a. Set offloadAllowed to FALSE.

b. Review attribute loadBalancingAllowed and set it according to

legacy.
c. Review attribute atoAllowed and set it according to legacy.

d. Review attribute cellReselectionPriority and set it according to

legacy.

5. Set EUtranCellFDD.lbEUtranAcceptOffloadThreshold or
EUtranCellTDD.lbEUtranAcceptOffloadThreshold to legacy
recommended value.

4.5 Disable Preferential Traffic Management

If the Preferential Traffic Management solution is no longer needed, it can
be disabled permanently by performing this task.

The configuration of Preferential Traffic Management affects the configuration of

the used features. Hence, when turning the solution off, legacy configurations
must be reset.

Steps

1. Set PtmFunction.ptmEnabled to the default value, FALSE.

Result: The functions of the Preferential Traffic Management are no longer

operating.

2. Set the EUtranFreqRelation.lbBnrPolicy attribute to the default value to

disallow automatic setting of load balancing relations for both Inter-
Frequency Offload and Inter-Frequency Load Balancing.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 29

 Preferential Traffic Management Guidelines

3. Set EUtranCellRelation.loadBalancing to ALLOWED or OFFLOAD—if the

attribute was previously set to IFO_AND_IFLB— depending on desired
behavior for all load balancing relations that allow both Inter-Frequency
Offload and Inter-Frequency Load Balancing.

4. Revise configurations in FreqPrioEUTRA struct for attribute

RATFreqPrio.freqPrioListEUTRA, as follows:

a. Set offloadAllowed to FALSE.

b. Review attribute loadBalancingAllowed and set it according to

legacy.
c. Review attribute atoAllowed and set it according to legacy.

d. Review attribute cellReselectionPriority and set it according to

legacy.

5. Set EUtranCellFDD.lbEUtranAcceptOffloadThreshold or
EUtranCellTDD.lbEUtranAcceptOffloadThreshold to legacy
recommended value.

6. Delete EUtranCellFDD.ptmCellProfileRef and

EUtranCellTDD.ptmCellProfileRef attributes.

7. Delete all PtmSubscriberGroup MO references from the following MOs:

— PtmAtoConfig

— PtmIfoConfig

— PtmResOpUseConfig

— PtmStmConfig

8. Delete all the following MOs:

— PtmAtoConfig

— PtmIflbConfig

— PtmIfoConfig

— PtmResOpUseConfig

— PtmStmConfig

9. Delete all PtmCellProfile MOs.

10. Delete all PtmSubscriberGroup MOs.

30 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Implementation of Preferential Traffic Management

4.6 Set PLMN-related Thresholds for Subscription Ratio

To ensure that Preferential Traffic Management functions properly, and the
relevant thresholds related to subscription ratio that define the behavior of load
management features are appropriately set, do the following:

Prerequisites

— Inter-Frequency Load Balancing is activated and enabled in the cell.

— Inter-Frequency Offload is activated and enabled in the cell.

Steps
Set the thresholds related to cell subscription ratio in priority cells so that the
following relations hold between them:

PtmIflbConfig.stopIncomingIflbThreshold ≤
PtmResOpUseConfig.unresSRatioThreshold <
PtmResOpUseConfig.resSRatioThreshold ≤
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold (depending on which cell
the cell profile references from)

RELATED INFORMATION

2.5 Subscription Ratio on page 5

4.8 Configure Cells for Preferential Traffic Management on page 32

5.3.3.1 PLMN IDs Reserved Due to Subscription Ratio or MSR Usage on page
49

6.3 Optimization of PLMN Thresholds for Preferential Traffic Management on

page 57

4.7 Set PLMN-related Thresholds for GBR MSR Usage

To ensure that Preferential Traffic Management functions properly, and the
relevant PLMN-related thresholds for GBR MSR usage, which define the behavior
of Admission-Triggerred Offload, are appropriate, do the following:

Prerequisites

— Admission-Triggerred Offload is activated and enabled in the cell.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 31

 Preferential Traffic Management Guidelines

Steps
Set the thresholds related to GBR MSR usage so that the following relations hold
between them:

PtmResOpUseConfig.unresMsrUsageThreshold <
AdmissionControl.lbAtoThresholdLevel1 ≤
AdmissionControl.lbAtoThresholdLevel2 ≤
PtmResOpUseConfig.resMsrUsageThreshold

RELATED INFORMATION

2.8 Monitored System Resources on page 7

4.8 Configure Cells for Preferential Traffic Management on page 32

5.3.3.1 PLMN IDs Reserved Due to Subscription Ratio or MSR Usage on page
49

6.3 Optimization of PLMN Thresholds for Preferential Traffic Management on

page 57

4.8 Configure Cells for Preferential Traffic Management

To differentiate priority cells from non-priority cells, different load management
configuration is required for them.

Steps
Configure the cell level parameters depending on the type of the cell.

Table 4 Recommended Cell Configuration Parameters for Preferential Traffic Management

MO Instance Non-priority Cells Priority Cells
Parameter
EUtranCellFDD.lbEUtranAcceptOffloadThreshold 90 N/A
EUtranCellTDD.lbEUtranAcceptOffloadThreshold
EUtranCellFDD.lbEUtranTriggerOffloadThreshold N/A 80
EUtranCellTDD.lbEUtranTriggerOffloadThreshold
EUtranCellFDD.ptmCellProfileRef References to References to
PtmCellProfile. PtmCellProfile.
EUtranCellTDD.ptmCellProfileRef

RELATED INFORMATION

6.2 Optimization of Thresholds for Preferential Traffic Management on page

56

32 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Implementation of Preferential Traffic Management

6.3 Optimization of PLMN Thresholds for Preferential Traffic Management on

page 57

6.4 Optimization of Inhibit Timer for Idle Mode Prioritization on page 60

5.1 Normal Traffic Load Level Operation of Preferential Traffic Management on

page 35

5.2 High Traffic Load Operation of Preferential Traffic Management on page

37

5.3 Very High Traffic Load Operation of Preferential Traffic Management on

page 39

4.9 Configure SPID-Based Parameters for Preferential

Traffic Management
To ensure that load management is differentiated based on the type of UEs, cells,
and frequency bands, configure the relevant SPID-based parameters as follows:

Prerequisites

— The RFPM function of Subscriber Triggered Mobility is activated and enabled

in the cell.

Steps

1. Create RATFreqPrio MO instances for priority UEs and for non-priority UEs.

a. Configure the SPIDs associated with priority UEs in the spidList

parameter in the RATFreqPrio MO instances for priority UEs.

b. Configure the SPIDs associated with non-priority UEs in the

spidList parameter in the RATFreqPrio MO instances for non-
priority UEs.

2. Configure parameter freqPrioListEUTRA and corresponding

FreqPrioEUTRA structs in RATFreqPrio MO instances for priority UEs in the
following way:

Table 5 Recommended Configurations for FreqPrioEUTRA Structs for Priority UEs

Parameter Priority Frequency Non-priority Frequencies
atoAllowed TRUE TRUE

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 33

 Preferential Traffic Management Guidelines

Parameter Priority Frequency Non-priority Frequencies

cellReselectionPriority 7 5
loadBalancingAllowed FALSE FALSE
offloadAllowed FALSE TRUE

Note: The attribute cellReselectionPriority must be set to a higher

value for priority frequencies than for non-priority frequencies. This
ensures that priority bands are priority in idle mode prioritization for
priority UEs.

3. Configure parameter freqPrioListEUTRA and corresponding

FreqPrioEUTRA structs in RATFreqPrio MO instances for non-priority UEs in
the following way:

Table 6 Recommended Configurations for FreqPrioEUTRA Structs for Non-priority UEs

Parameter Priority Frequency Non-priority Frequencies
atoAllowed FALSE FALSE
cellReselectionPriority 5 6
connectedModeMobilityPrio 0 N/A
loadBalancingAllowed TRUE TRUE
offloadAllowed FALSE FALSE

RELATED INFORMATION

4.3 Enable Preferential Traffic Management on page 26

2.9 Subscriber Profile ID for RAT/Frequency Priority on page 8

3.6 Subscriber Triggered Mobility Overview on page 20

5.1 Normal Traffic Load Level Operation of Preferential Traffic Management on

page 35

5.3 Very High Traffic Load Operation of Preferential Traffic Management on

page 39

8.1 UEs of the Wrong Type Are Grouped on Priority Cells on page 63

34 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

5 Operation of Preferential Traffic

Management

5.1 Normal Traffic Load Level Operation of Preferential

Traffic Management
Preferential Traffic Management functions on normal load operation when
the load is below threshold PtmIflbConfig.stopIncomingIflbThreshold.
This occurs when all bands—including the priority band—have relatively
low load, and no special congested traffic situation is ongoing.

Non-priority traffic load

Priority traffic load

lbEUtranTriggerOffloadThreshold
(legacy)

stopIncomingIflbThreshold
(new)

Idle mode (SPID based) redirection

Non-priority bands Priority band

Note:
The measured cell traffic load is the sum of non-priority and priority load.
L0001795E

Figure 8 Normal Load Operation of Preferential Traffic Management

Given that the Inter-Frequency Load Balancing feature is enabled, the system
moves non-priority UEs between the different frequency layers and bands as
legacy function.

Besides the load balancing behavior, the RFPM function of Subscriber Triggered
Mobility ensures idle mode prioritization of priority UEs to priority bands, and
non-priority UEs to non-priority bands. This makes sure that correct users end up
on the bands intended as their primary usage.

The solution requires that only a certain UE category is allowed in Inter-

Frequency Load Balancing.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 35

 Preferential Traffic Management Guidelines

RELATED INFORMATION

2.2 Traffic Load State on page 2

3.3 Inter-Frequency Load Balancing Overview on page 14

3.6 Subscriber Triggered Mobility Overview on page 20

2.1 UE and Band Types in Preferential Traffic Management on page 2

2.9 Subscriber Profile ID for RAT/Frequency Priority on page 8

5.1.1 Restricting Inter-Frequency Load Balancing for a UE Category

The Preferential Traffic Management solution introduces a new parameter—
offloadAllowed in struct FreqPrioEUTRA—to allow a configuration where a UE
with a certain SPID is not allowed to be moved by Inter-Frequency Load
Balancing, but allowed to move to the same frequency when load increases and
Inter-Frequency Offload is triggered.

The new parameter offloadAllowed has any effect only in the following case:
— For load balancing relations allowing both inter-frequency load balancing
and inter-frequency offload, EUtranCellRelation.loadBalancing set to
IFO_AND_IFLB

— Parameter loadBalancingAllowed in struct FreqPrioEUTRA is set to FALSE.

In that case a target frequency is allowed for a UE with the considered SPID only
if offloadAllowed is TRUE and the subscription ratio in the current cell is above
the offload threshold EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

The default value of parameter offloadAllowed is FALSE for any frequency and
SPID. To use the Preferential Traffic Management solution, the parameter must
be set to TRUE in FreqPrioEUTRA structs corresponding to non-priority
frequencies for priority UEs.

RELATED INFORMATION

4.3 Enable Preferential Traffic Management on page 26

4.9 Configure SPID-Based Parameters for Preferential Traffic Management on

page 33

36 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

5.2 High Traffic Load Operation of Preferential Traffic

Management
Preferential Traffic Management functions on high load operation when a
relatively high load has been built up on the priority band, but no special
congested traffic situation is ongoing.

Non-priority traffic load

Priority traffic load

lbEUtranTriggerOffloadThreshold
(legacy)

stopIncomingIflbThreshold
(new)

Inter-Frequency Load Balancing

Non-priority bands Priority band

Note:
The measured cell traffic load is the sum of non-priority and priority load.
L0001796D

Figure 9 High Load Operation of Preferential Traffic Management

When the total subscription ratio in some cell on the priority band is above
threshold PtmIflbConfig.stopIncomingIflbThreshold, the system ensures
that further incoming Inter-Frequency Load Balancing actions, to the affected
cell or cells, are stopped.

RELATED INFORMATION

2.2 Traffic Load State on page 2

3.3 Inter-Frequency Load Balancing Overview on page 14

5.2.1 Stopping Inter-Frequency Load Balancing to Priority Cells at High

Subscription Ratio
Preferential Traffic Management stops Inter-Frequency Load Balancing to a
target cell on the priority band with high traffic load using the following
procedure.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 37

 Preferential Traffic Management Guidelines

Operation Sequence Diagram

Target Cell Source Cell

Compute
subscription ratio

Subscription ratio > no

stopIncomingIfIbThreshold Normal traffic load operation

yes

Traffic load state signaled Load report Receiving report

as “Stop Incoming IFLB” on traffic load state

Report from another cell no

contains traffic load
state “Stop Incoming IFLB”

yes

no
stopOutgoingIflbEnabled
is TRUE

yes

Remove cell from valid Normal load

load balancing target list balancing operation

L0001806D

Figure 10 Stopping Inter-Frequency Load Balancing to Priority Cells

Process Steps

1. In the load assessment step, the computed subscription ratio of the priority
cell is compared with threshold
PtmIflbConfig.stopIncomingIflbThreshold.

2. If the subscription ratio is lower than or equal to threshold

PtmIflbConfig.stopIncomingIflbThreshold, the normal traffic load
operation remains effective.

If the subscription ratio is higher than threshold

PtmIflbConfig.stopIncomingIflbThreshold, during load information
exchange the traffic load state of the priority cell is signaled as set to "Stop
incoming IFLB".

3. A non-priority cell receives a load report indicating the traffic load state of a
potential target cell, and checks the traffic load state.

38 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

Note: Between cells in different nodes, the load report is sent in X2 cell
resource status report messages.

4. If the traffic load state of the reported cell is "Stop incoming IFLB" and the
cell is enabled to consider this traffic load state, load balancing is not allowed
towards the reported cell.

A non-priority cell can be enabled to consider traffic load state "Stop

incoming IFLB" by setting attribute
PtmIflbConfig.stopOutgoingIflbEnabled to TRUE.

Otherwise the normal load balancing operation remains effective.

RELATED INFORMATION

6.2 Optimization of Thresholds for Preferential Traffic Management on page

56

4.3 Enable Preferential Traffic Management on page 26

4.8 Configure Cells for Preferential Traffic Management on page 32

8.2 Non-Priority Cells Are Performing Load Balancing Handovers to Heavily

Loaded Priority Cells on page 64

5.3 Very High Traffic Load Operation of Preferential Traffic

Management
Preferential Traffic Management functions on very high load operation
when the priority cell has reached very high load from non-priority and
priority UEs, after Inter-Frequency Load Balancing actions to the affected

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 39

 Preferential Traffic Management Guidelines

cells have been stopped. This corresponds to a case when a special

congested traffic situation is ongoing.

Non-priority traffic load

Priority traffic load

lbEUtranTriggerOffloadThreshold
(legacy)

stopIncomingIflbThreshold
(new)

Idle mode (SPID based) redirection

Non-priority bands Priority band

Note:
The measured cell traffic load is the sum of non-priority and priority load.
L0001797E

Figure 11 Very High Load Operation of Preferential Traffic Management

Given that the Admission Triggered Offload and the Inter-Frequency Offload
features are enabled, the system offloads traffic to cells with lower load, as
legacy functionality.

The solution requires the following additional functions:

— Non-priority cells are allowed to be used as target cell for both Inter-
Frequency Load Balancing and Inter-Frequency Offload.

— Idle mode prioritization of priority UEs (characterizing normal and high

traffic load level operation) is stopped.

— When the total subscription ratio or the total MSR usage for GBR has
reached very high level in a cell, the respective priority cell is blocked for
camping for the non-priority users.

— In priority cells, non-priority UEs are offloaded first and priority UEs last.

— Admission-Triggered Offload can be enabled per cell on a node to given

target frequencies for UEs configured with a SPID. This function is required,
because one node can have both priority and non-priority cells. Without this
function, Admission-Triggered Offload can be configured either as
differentiated based on SPID and the same for each cell on the node, or as
differentiated per cell when no SPID differentiation applies.

40 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

RELATED INFORMATION

2.2 Traffic Load State on page 2

2.5 Subscription Ratio on page 5

3.1 Admission-Triggered Offload Overview on page 11

3.3 Inter-Frequency Load Balancing Overview on page 14

3.4 Inter-Frequency Offload Overview on page 17

3.5 Shared LTE RAN Overview on page 18

3.6 Subscriber Triggered Mobility Overview on page 20

2.5 Subscription Ratio on page 5

2.6 GBR Traffic Load on page 6

2.7 Non-GBR Traffic Load on page 6

2.8 Monitored System Resources on page 7

2.9 Subscriber Profile ID for RAT/Frequency Priority on page 8

5.3.1 Allowing the Same Cell as Target Cell for both Inter-Frequency Load
Balancing and Inter-Frequency Offload

Preferential Traffic Management handles target cells that are configured to

be usable for both Inter-Frequency Load Balancing and Inter-Frequency
Offload combined with UE permissions per SPID to perform inter-frequency
load balancing or inter-frequency offload.

The node can configure neighbor cells for both Inter-Frequency Load Balancing
and Inter-Frequency Offload automatically with the following features:

— Automated Neighbor Relations

— Best Neighbor Relations for Intra-LTE Load Management

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 41

 Preferential Traffic Management Guidelines

Note: For automatic configuration of neighbor cells for both Inter-Frequency

Load Balancing and Inter-Frequency Offload, attribute
EUtranFreqRelation.lbBnrPolicy must be set to IFO_AND_IFLB.

The following process is done in every load balancing cycle, and iterated for every
neighboring target cell.

Operation Sequence Diagram

Subscription ratio of the source

cell is computed

yes Target cell is no

configured for offload

Subscription ratio > no

no Target cell is configured
lbEUtranTriggerOffloadThreshold for IFO_AND_IFLB

yes Target cell is configured yes

Traffic load to be for load balancing
handed over = 0
yes yes Subscription ratio > no
lbEUtranTriggerOffloadThreshold no

Nothing is done

yes Load-sum > no

lbEUtranTriggerOffloadThreshold

yes Load-sum > no

stopIncomingIflbThreshold
Traffic load to be handed over is
computed as the subscription
ratio-lbEUtranTriggerOffloadThreshold

Traffic load to be handed over is Traffic load to be handed over is

computed as the subscription based on the subscription ratio
ratio-stopIncomingIflbThreshold of the source cell and the
load-sum of target cell

Load-sum = the sum of the subscription ratio received

for target cell and the rate offset for target cell
L0001967C

Figure 12 Inter-Frequency Load Balancing and Inter-Frequency Offload Operation Depending on

EUtranCellRelation.loadBalancing

Process Steps

1. In load measurement step, the computed subscription ratio of the cell is

compared with offload threshold
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

42 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

2. In load balancing action magnitude step, if the cell is configured for both
Inter-Frequency Load Balancing and Inter-Frequency Offload, by setting
attribute EUtranCellRelation.loadBalancing to IFO_AND_IFLB, the
amount of traffic load to be handed over to each target cell is determined
based on the following:

• The traffic load level in the source cell

• Whether the source cell can move more subscription quanta to the target
cell by load balancing or offload action

Note: If the cell is configured using

EUtranCellRelation.loadBalancing for Inter-Frequency Load
Balancing or Inter-Frequency Offload only, the amount of traffic
load to be handed over to each target cell is determined by the
respective feature.

Table 7 Load Balancing Action when EUtranCellRelation.loadBalancing is

IFO_AND_IFLB
Traffic Load Level Threshold Assessment Traffic Load Handed Over
Threshold Load-sum(1) > Offload-like action.
EUtranCellFDD.lbEUtranTriggerOff lbEUtranTriggerOffloadThreshold The load to be moved to the
loadThreshold or neighboring cell is computed as the
EUtranCellTDD.lbEUtranTriggerOff subscription ratio of the source cell –
loadThreshold is exceeded. lbEUtranTriggerOffloadThreshold.

Load-sum(1) ≤ Load balancing-like action.

lbEUtranTriggerOffloadThreshold The load to be moved to the
neighboring cell is based on the
difference between the subscription
ratio of the source cell and the load-
sum(1) of the target cell.
Threshold Load-sum(1) > Offload-like action.
PtmIflbConfig.stopIncomingIflbTh PtmIflbConfig.stopIncomingIflbTh The load to be moved to the
reshold is exceeded. reshold neighboring cell is computed as the
subscription ratio of the source cell –
PtmIflbConfig.stopIncomingIflbTh
reshold.

Load-sum(1) ≤ Load balancing-like action.

PtmIflbConfig.stopIncomingIflbTh The load to be moved to the
reshold neighboring cell is based on the
difference between the subscription
ratio of the source cell and the load-
sum(1) of the target cell.
(1) Load-sum is the sum of the subscription ratio received for target cell and the rate offset for target cell.

Note: Cells configured for both Inter-Frequency Load Balancing and Inter-
Frequency Offload can be used as target cell for CATR function of
the Carrier Aggregation-Aware IFLB feature.

3. In UE selection for load balancing action step, the procedure depends on the
SPID of the UE.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 43

 Preferential Traffic Management Guidelines

If the UE has no allocated SPID value, or its SPID value is not configured in
any RATFreqPrio MO instance, the UE selection for load balancing action is
performed like in legacy, using inter-frequency Event A5 measurement
reporting.

If the SPID value of the UE is configured in some RATFreqPrio MO instance,

the frequency is chosen as a candidate for the UE to start measurements
only if either of the following applies—besides legacy criteria:

• Attribute loadBalancingAllowed in the corresponding FreqPrioEUTRA

struct is set to TRUE.

• Attribute offloadAllowed in the corresponding FreqPrioEUTRA struct is

set to TRUE and the subscription ratio of the source cell is higher than
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

Otherwise, the frequency is excluded from measurements.

Incoming measurement reports are handled as legacy.

4. The cause value of an outgoing handover to a target cell allowed for both
Inter-Frequency Load Balancing and Inter-Frequency Offload is set as the
cause value of an outgoing Inter-Frequency Load Balancing handover.

RELATED INFORMATION

3.2 Best Neighbor Relations for Intra-LTE Load Management Overview on

page 13

6.1 Optimization of Cell Relations for Preferential Traffic Management on page

55

4.8 Configure Cells for Preferential Traffic Management on page 32

4.9 Configure SPID-Based Parameters for Preferential Traffic Management on

page 33

8.1 UEs of the Wrong Type Are Grouped on Priority Cells on page 63

8.2 Non-Priority Cells Are Performing Load Balancing Handovers to Heavily

Loaded Priority Cells on page 64

44 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

5.3.2 Inhibiting Idle Mode Prioritization

Preferential Traffic Management in non-priority cells inhibits idle mode
prioritization for priority UEs on priority bands with very high traffic load, using
the following procedure.

Activation of Inhibit Idle Mode Prioritization Functionality

The inhibit idle mode prioritization function can be triggered in a cell by receiving
load report message indicating traffic load state "Inhibit idle mode prioritization"

Target Cell

Subscription ratio Normal traffic

is computed load operation

no

Subscription ratio > no Subscription ratio >

IbEUtranTriggerOffloadThreshold stopIncomingIflbThreshold

yes
yes

High traffic
sendInhibitIM-
PriorizationEnabled
load operation Source Cell
is TRUE

yes
Incoming handover
Load report Receiving report from Admission-
Traffic load state signaled as
“Inhibit idle mode priorization” on traffic load state Triggered Offload

Report from another cell no The report contains no

contains traffic load traffic load state “Stop
state “Inhibit idle mode
priorization” incoming IFLB”

yes yes

High traffic
load operation
no
InhibitIMPrioritizationEnabled
is TRUE
Normal load
balancing operation
yes
Nothing is done

Inhibit timer is started

for the time set by
inhibitIMPrioritizationInterval

L0001867E

1. In load measurement step, the computed subscription ratio of the cell is

compared with offload threshold
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 45

 Preferential Traffic Management Guidelines

2. If the subscription ratio is lower than threshold

EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold, the
PtmIflbConfig.stopIncomingIflbThreshold is checked to decide if
normal or high traffic load operation is effective.

If the subscription ratio is higher than threshold

EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold, during load
information exchange the traffic load state of the cell is signaled set to
"Inhibit idle mode prioritization".

The information is sent only if the cell is enabled to do so, by setting

parameter PtmCellProfile.cellType to PRIORITY.

3. Another cell receives a load report indicating the traffic load state of a
potential target cell, and checks the traffic load state.

Note: Between cells in different nodes, the load report is sent in X2 cell
resource status report messages.

4. If the traffic load state of the reported cell is not "Inhibit idle mode
prioritization", it is decided if normal or high traffic load operation is
effective.

5. If the traffic load state of the reported cell is "Inhibit idle mode prioritization",
the inhibit idle mode prioritization function can be started. Go to .

Since traffic load state "Inhibit idle mode prioritization" in a cell implies that
"Stop incoming IFLB" traffic load state is also instated in that cell, the
behavior for traffic load state "Stop incoming IFLB" is also applied for the
potential target cell.

6. An incoming Admission-Triggered Offload or Inter-Frequency Offload

handover is detected in a cell.

7. The inhibit idle mode prioritization functionality is started for the time set by
parameter PtmStmConfig.inhibitImpInterval, measured by an inhibit
timer.

The inhibit timer is started, or restarted if it is already active.

The function and the timer is started only if at least one of the Preferential
Traffic Management subscriber group is referenced from
PtmStmConfig.ptmSubscriberGroupRef.

Inhibit Timer Timeout

When the time set by PtmStmConfig.inhibitImpInterval has elapsed, the
inhibit idle mode prioritization function is stopped in the cell.

46 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

Note: If the inhibiting idle mode prioritization function is triggered while it is

already running in the cell, the inhibit timer is restarted. Thus, the
function is stopped only when the time set by
PtmStmConfig.inhibitImpInterval has elapsed since the last trigger
for activating the function.

Inhibiting Idle Mode Prioritization at UE Release

UE release procedure is started

No SPID of the UE is
configured with idle mode
prioritization

Yes

No
Inhibit timer is active

Yes

Yes SPID of the UE is No

included in ptmSubscriberGroupRef

No idle mode SPID is included with

prioritization information idle mode redirection
is sent to the UE information in UE
release request message

L0001866D

In UE release, idle mode prioritization is inhibited for the UE, if the following
conditions are met:

— The SPID of the UE is included in at least one of the subscriber groups that
referenced from PtmStmConfig.ptmSubscriberGroupRef.

— The inhibit timer is not timed out.

RELATED INFORMATION

4.3 Enable Preferential Traffic Management on page 26

4.8 Configure Cells for Preferential Traffic Management on page 32

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 47

 Preferential Traffic Management Guidelines

4.9 Configure SPID-Based Parameters for Preferential Traffic Management on

page 33

6.4 Optimization of Inhibit Timer for Idle Mode Prioritization on page 60

8.1 UEs of the Wrong Type Are Grouped on Priority Cells on page 63

8.3 Non-Priority Cells Are Not Inhibiting Idle Mode Prioritization of Priority UEs
to Heavily Loaded Priority Cells on page 66

8.4 Improper Time for Idle Mode Prioritization for Priority UEs on page 68

5.3.3 Blocking a Cell for Idle Mode Camping and Incoming Handover for Non-
Priority UEs

Preferential Traffic Management blocks a priority cell for idle mode camping
by broadcasting the cell as "reserved for operator use." It also blocks
incoming handover for non-priority UEs in very high load situations.

This is achieved with the following functions:

— The PLMNs for non-priority UEs are broadcast in SIB1 system messages as
Reserved, because of subscription ratio or MSR usage.

— Incoming handover to cells "reserved for operator use" for SPIDs of UEs is
blocked if at least one of the instances of PtmSubscriberGroup MO is
referenced from PtmResOpUseConfig.ptmSubscriberGroupRef.

Handover is also blocked if the target cell signals its reservation status as
Reserved. Such cell is removed from the list of valid cells for handover.

Cell reservation state is propagated between nodes over X2 in the Cell

Resource Status Report message. The message is sent periodically so cells
can update reservation state of neighboring cells. A cell is considered
Unreserved in the following cases:

— If the cell does not receive the Cell Resource Status Report message
from a previously reserved cell.

— If the Cell Resource Status Report message does not contain the Cell
Reservation State IE.

48 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

Note: The ORC part of the Subscriber Triggered Mobility feature works
independently of this function.

When both functions are used, the traffic is affected. Manual setting of
cells to "reserved for operator use"—by ORC—cannot be changed using
this function.

Note: If the Enhanced PTT Admission Control feature is activated, the

downlink PTT dynamic MSR reservations are considered when checking
the admission-triggered offload thresholds.

RELATED INFORMATION

4.6 Set PLMN-related Thresholds for Subscription Ratio on page 31

4.7 Set PLMN-related Thresholds for GBR MSR Usage on page 31

4.8 Configure Cells for Preferential Traffic Management on page 32

6.3 Optimization of PLMN Thresholds for Preferential Traffic Management on

page 57

8.2 Non-Priority Cells Are Performing Load Balancing Handovers to Heavily

Loaded Priority Cells on page 64

8.3 Non-Priority Cells Are Not Inhibiting Idle Mode Prioritization of Priority UEs
to Heavily Loaded Priority Cells on page 66

5.3.3.1 PLMN IDs Reserved Due to Subscription Ratio or MSR Usage

Preferential Traffic Management broadcasts configured PLMNs for non-priority

UEs as "reserved" in the following cases:
— When the subscription ratio of the cell exceeds threshold
PtmResOpUseConfig.resSRatioThreshold.

— When the MSR usage in the cell, for either uplink or downlink exceeds
threshold PtmResOpUseConfig.resMsrUsageThreshold.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 49

 Preferential Traffic Management Guidelines

Operation Sequence Diagram

Subscription ratio MSR usage

is computed is computed

Subscription ratio > no

plmnResOpUseSRatioThreshold
MSR usage >
no
plmnResOpUseMsrUsageThreshold

yes yes

The PLMN IDs configured in

plmnsToReserveAtHighLoad
are broadcast as "reserved"
Subscription ratio <
plmnUnresOpUseSRatioThreshold and yes
MSR usage <
plmnUnresOpUseMsrUsageThreshold and

no
The PLMN IDs configured in
plmnsToReserveAtHighLoad
Nothing is are broadcast as "unreserved"
done

L0001960A

Figure 15 PLMN IDs Reserved Due to Subscription Ratio or MSR Usage

Process Steps

1. In load measurement step, the computed subscription ratio of the cell is

compared with threshold PtmResOpUseConfig.resSRatioThreshold.

If the subscription ratio is higher than threshold

PtmResOpUseConfig.resSRatioThreshold, the PLMN IDs configured in
PtmResOpUseConfig.ptmSubscriberGroupRef are broadcast as "reserved".

Note: The PLMN IDs used in PtmSubscriberGroup must also be present

in either ENodeFunction.eNodeBPlmnId,
EUtranCellFDD.additionalPlmnList, or
EUtranCellTDD.additionalPlmnList.

2. In MSR usage measurement step, the computed MSR usage for any GBR
MSR is compared with threshold
PtmResOpUseConfig.resMsrUsageThreshold.

50 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

If the MSR usage, for either uplink or downlink is higher than

PtmResOpUseConfig.resMsrUsageThreshold, the PLMN IDs configured in
PtmResOpUseConfig.ptmSubscriberGroupRef are broadcast as "reserved".

3. The cell leaves the "reserved" state, and the PLMN IDs used in
PtmSubscriberGroup are broadcast as "unreserved" if the following
conditions are met:
— The cell subscription ratio is lower than threshold
PtmResOpUseConfig.unresSRatioThreshold.

— The MSR Usage for downlink is lower than

PtmResOpUseConfig.unresMsrUsageThreshold.

Note: The downlink MSR usage is made up not only of the load
created by the bearers established for the UEs in the cell, but a
constant MSR load is created by control channel messages sent
by the cell. The messages are sent even when no UE attaches to
the cell.

— The MSR Usage for uplink is lower than

PtmResOpUseConfig.unresMsrUsageThreshold.

Note: The ORC part of the Subscriber Triggered Mobility feature works
independently of this function.

When both functions are used, the traffic is affected. Manual setting
of cells to "reserved for operator use"—by ORC—cannot be changed
using this function.

5.3.3.2 Blocked Handover to Cells Reserved for Operator Use

UEs with certain PLMN IDs cannot camp in cells "reserved for operator use".
Incoming handover to such cells is blocked.

Note: The ORC part of the Subscriber Triggered Mobility feature works
independently of this function.

When both functions are used, the traffic is affected. Manual setting of
cells to "reserved for operator use"—by ORC—cannot be changed using
this function.

MOM attribute PtmResOpUseConfig.ptmSubscriberGroupRef is used to

configure the SPIDs whose handover is blocked for the time the cell has one or
more PLMN IDs "reserved".

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 51

 Preferential Traffic Management Guidelines

Operation Sequence Diagram

Incoming handover

Cell is in state no
"reserved for operator use"

Nothing is done
yes

SPID of UE is listed no
in spidBlacklistHo

The handover
yes is executed

The UE has no SPID no

and spidBlacklistHo
contains value -1

yes

The handover
is rejected

L0001942A

Figure 16 Blocking Handover to Cells Reserved for Operator Use

Process Steps

1. The handover is rejected with a cause code Radio resources not

available in the following cases:

• The UE has a SPID and the SPID is listed in one of the subscriber groups
referenced from PtmResOpUseConfig.ptmSubscriberGroupRef.

• The UE has no SPID and at least one of the PtmSubscriberGroup

instances referenced from
PtmResOpUseConfig.ptmSubscriberGroupRef contains -1 as one of
the SPID values.

Otherwise, the handover is continued.

If all other legacy condition is met, the handover is executed.

52 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Operation of Preferential Traffic Management

5.3.4 Subscriber Group-based UE Selection for Offload

When the Preferential Traffic Management solution is enabled, and the

traffic load is very high, from priority cells offload of non-priority UEs is
started before offload of priority UEs.

UE selection for offload—Inter-Frequency Offload and Admission-Triggered

Offload—is based on subscriber group priority as follows.

UEs are selected for offload based on the priority of their subscriber group. Up to
12 subscriber groups can be defined. Offload candidate selection works only on
cells that reference PRIORITY Preferential Traffic Management cell profiles.

The order of the subscriber group offload is defined by the order of the subscriber
group references in PtmAtoConfig.ptmSubscriberGroupRef. Groups from the
top of the PtmAtoConfig.ptmSubscriverGroupRef list have lower priority and
are offloaded earlier. For high priority groups, a special threshold is introduced to
control the timing of the Preferential Traffic Management initiated offload.

Offload is not stopped due to lack of UEs with low priority SPIDs or which cannot
be moved for other reasons, for example emergency call or bad coverage in the
target cell. When the Admission-Triggered Offload throughput is evaluated, it is
then decided whether the amount of offloaded UEs fulfills the threshold
requirements. If not, the next group of UEs are offloaded.

Note: Enabling subscriber group-based UE selection for offload requires the

following configuration:
— Priority cells reference cell profiles where
PtmCellProfile.cellType is set to PRIORITY.

— PtmFunction.ptmEnabled is set to TRUE.

UE selection for offload is based on the following configurations:

— For Inter-Frequency Offload, moveable non-priority UEs are selected first,

and priority UEs are selected last.

— For Admission-Triggered Offload, selection of priority UEs can start before all
moveable non-priority UEs are offloaded.

5.3.5 Enabling or Disabling Admission-Triggered Offload Per Cell for UEs

Preferential Traffic Management allows that Admission-Triggered Offload is

enabled or disabled per cell for UEs .

This behavior is achieved by setting PtmCellProfile.cellType to PRIORITY

and referencing this profile from the desired non-priority cells. UE selection for

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 53

 Preferential Traffic Management Guidelines

Admission-Triggered Offload is configured by using

PtmAtoConfig.ptmSubscriberGroupRef.

Without using the PtmCellProfile.cellType attribute, SPID-differentiated

behavior of Admission-Triggered Offload can only be set the same in all cells on a
node. This is possible using attribute atoAllowed in FreqPrioEUTRA structs of
associated RATFreqPrio.freqPrioListEUTRA attributes.

Without using attribute PtmCellProfile.cellType, Admission-Triggered

Offload can be set per cell, but without differentiating based on SPID. This is
possible using EUtranFreqRelation.atoAllowed.

If PtmCellProfile.cellType is set to NON_PRIORITY Preferential Traffic

Management has no effect on Admission-Triggered Offload.

RELATED INFORMATION

4.7 Set PLMN-related Thresholds for GBR MSR Usage on page 31

4.8 Configure Cells for Preferential Traffic Management on page 32

4.9 Configure SPID-Based Parameters for Preferential Traffic Management on

page 33

54 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Optimization of Preferential Traffic Management

6 Optimization of Preferential Traffic

Management

6.1 Optimization of Cell Relations for Preferential Traffic

Management
Enabling Automated Neighbor Relations and Best Neighbor Relations for Intra-
LTE Load Management features is recommended to allow automatic
configuration of cell relations.

To achieve optimal operation of Preferential Traffic Management, cell relations

are recommended to be configured as follows:

Table 8 Recommended Load Balancing Relations for Preferential Traffic Management

Cell Relation Recommendation Setting of Setting of
EUtranCellRelation.loadBal EUtranFreqRelation.lbBnrPo
ancing licy
From priority cell to non- Required IFO_AND_IFLB IFO_AND_IFLB
priority cell
Among priority cells Recommended ALLOWED(1) AUTO
From non-priority cell to Required ALLOWED AUTO
priority cell
Among non-priority cells Recommended ALLOWED AUTO

(1) If some cell relations between priority cells is configured to allow inter-frequency offload—attribute
EUtranCellRelation.loadBalancing is set to OFFLOAD or IFO_AND_IFLB—and priority UEs are served on multiple
frequencies, it is important to set EUtranCellFDD.lbEUtranAcceptOffloadThreshold or
EUtranCellTDD.lbEUtranAcceptOffloadThreshold in priority cells equal to
PtmIflbConfig.stopIncomingIflbThreshold. This allows that priority cells offload to neighboring priority cells, and
non-priority UEs are not allowed to move to priority cells when the thresholds are exceeded.

RELATED INFORMATION

2.4 Load Balancing Relation on page 5

4.3 Enable Preferential Traffic Management on page 26

4.8 Configure Cells for Preferential Traffic Management on page 32

8.2 Non-Priority Cells Are Performing Load Balancing Handovers to Heavily

Loaded Priority Cells on page 64

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 55

 Preferential Traffic Management Guidelines

8.3 Non-Priority Cells Are Not Inhibiting Idle Mode Prioritization of Priority UEs
to Heavily Loaded Priority Cells on page 66

3.2 Best Neighbor Relations for Intra-LTE Load Management Overview on

page 13

3.3 Inter-Frequency Load Balancing Overview on page 14

3.4 Inter-Frequency Offload Overview on page 17

6.2 Optimization of Thresholds for Preferential Traffic

Management
To achieve optimal behavior of the Preferential Traffic Management solution,
both legacy and new thresholds have to be considered.

lbEUtranTriggerOffloadThreshold and lbEUtranAcceptOffloadThreshold

The following attributes control offload in source and target E-UTRAN cells:

— EUtranCellFDD.lbEUtranAcceptOffloadThreshold

— EUtranCellFDD.lbEUtranTriggerOffloadThreshold

— EUtranCellTDD.lbEUtranAcceptOffloadThreshold

— EUtranCellTDD.lbEUtranTriggerOffloadThreshold

It is important to have EUtranCellFDD.lbEUtranTriggerOffloadThreshold

and EUtranCellTDD.lbEUtranTriggerOffloadThreshold in priority cells set to
a value lower than EUtranCellFDD.lbEUtranAcceptOffloadThreshold and
EUtranCellTDD.lbEUtranAcceptOffloadThreshold in non-priority cells.
Otherwise, offload from priority to non-priority cells cannot work properly.

In non-priority cells, EUtranCellFDD.lbEUtranAcceptOffloadThreshold and

EUtranCellTDD.lbEUtranAcceptOffloadThreshold are recommended to be
set to 90, or another very high value. This ensures that offload from priority to
non-priority cells is accepted as long as the non-priority cell can accept it.

stopIncomingIflbThreshold
Modifying threshold PtmIflbConfig.stopIncomingIflbThreshold influences
the balance between priority and non-priority UEs in cells. Above this threshold,
load balancing moves non-priority UEs only from priority cells. Non-priority UEs
can be in priority cells only for the following reasons:

56 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Optimization of Preferential Traffic Management

— Coverage-triggered handover

— Connection establishment

— Connection re-establishment

The PtmIflbConfig.stopIncomingIflbThreshold attribute is recommended to

be set high enough to allow load balancing when the load on the network is
relatively small. This ensures that the load is kept as equal as possible,
considering that priority UEs do not take part in inter-frequency load balancing.

Attribute PtmIflbConfig.stopIncomingIflbThreshold should not be set too

high, so that non-priority users start to be removed from the priority band during
increased load.

RELATED INFORMATION

2.1 UE and Band Types in Preferential Traffic Management on page 2

2.2 Traffic Load State on page 2

3.3 Inter-Frequency Load Balancing Overview on page 14

3.4 Inter-Frequency Offload Overview on page 17

4.3 Enable Preferential Traffic Management on page 26

4.8 Configure Cells for Preferential Traffic Management on page 32

8.2 Non-Priority Cells Are Performing Load Balancing Handovers to Heavily

Loaded Priority Cells on page 64

8.3 Non-Priority Cells Are Not Inhibiting Idle Mode Prioritization of Priority UEs
to Heavily Loaded Priority Cells on page 66

6.3 Optimization of PLMN Thresholds for Preferential Traffic

Management
In Preferential Traffic Management, the following thresholds are used for PLMN-
differentiated load management:
— PtmResOpUseConfig.resSRatioThreshold

— PtmResOpUseConfig.unresSRatioThreshold

— PtmResOpUseConfig.resMsrUsageThreshold

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 57

 Preferential Traffic Management Guidelines

— PtmResOpUseConfig.unresMsrUsageThreshold

The two thresholds for subscription ratio includes both GBR and non-GBR
bearers.

The two thresholds for MSR usage considers only GBR bearers.

It is important to set PtmResOpUseConfig.resSRatioThreshold with a higher

value than PtmResOpUseConfig.unresSRatioThreshold, and
PtmResOpUseConfig.resMsrUsageThreshold with a higher value than
PtmResOpUseConfig.unresMsrUsageThreshold. This creates hysteresis, so that
the cell does not change 'reserved' and 'unreserved' states continuously. However,
if the related attributes are set too far apart, the cell changes 'reserved' and
'unreserved' states too late. This keeps the cell in a state with high reservations
even after the traffic load has already dropped to an acceptable level.

Table 9 Recommended Relations for PLMN-related Thresholds

Measured Load Quantity Recommended Configuration
Subscription ratio PtmIflbConfig.stopIncomingIflbT
hreshold ≤
PtmResOpUseConfig.unresSRatioTh
reshold <
PtmResOpUseConfig.resSRatioThre
shold ≤
lbEUtranTriggerOffloadThreshold
(in MOs EUtranCellFDD or
EUtranCellTDD)
MSR usage PtmResOpUseConfig.unresMsrUsage
Threshold <
AdmissionControl.lbAtoThreshold
Level1 ≤
AdmissionControl.lbAtoThreshold
Level2 ≤
PtmResOpUseConfig.resMsrUsageTh
reshold

To ensure that non-priority UEs start to be removed from priority cells before
offloading priority UEs has started, the recommended relations between PLMN-
related thresholds can be contravened in the following respects:
— Attribute PtmResOpUseConfig.resSRatioThreshold should be set slightly
lower than the threshold for inter-frequency offload:
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

— Attribute PtmResOpUseConfig.resMsrUsageThreshold should be set

slightly lower than the thresholds for admission-triggered offload:
AdmissionControl.lbAtoThresholdLevel1 and
AdmissionControl.lbAtoThresholdLevel2.

58 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Optimization of Preferential Traffic Management

Note: If the Enhanced PTT Admission Control feature is activated, the

downlink PTT dynamic MSR reservations are considered when checking
the admission-triggered offload thresholds.

When configuring the MSR-related thresholds for downlink—

PtmResOpUseConfig.resMsrUsageThreshold and
PtmResOpUseConfig.unresMsrUsageThreshold—it is important to consider the
following: The downlink MSR usage is made up not only of the load created by
the bearers established for the UEs in the cell, but a constant MSR load is created
by control channel messages sent by the cell. The messages are sent even when
no UE attaches to the cell.

Hence threshold PtmResOpUseConfig.unresMsrUsageThreshold for downlink

must be set to a value higher than the constant MSR load created by control
channel messages.

RELATED INFORMATION

2.5 Subscription Ratio on page 5

2.8 Monitored System Resources on page 7

2.6 GBR Traffic Load on page 6

2.7 Non-GBR Traffic Load on page 6

3.1 Admission-Triggered Offload Overview on page 11

3.3 Inter-Frequency Load Balancing Overview on page 14

3.4 Inter-Frequency Offload Overview on page 17

4.6 Set PLMN-related Thresholds for Subscription Ratio on page 31

4.7 Set PLMN-related Thresholds for GBR MSR Usage on page 31

4.8 Configure Cells for Preferential Traffic Management on page 32

5.3.3 Blocking a Cell for Idle Mode Camping and Incoming Handover for Non-
Priority UEs on page 48

5.3.3.1 PLMN IDs Reserved Due to Subscription Ratio or MSR Usage on page
49

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 59

 Preferential Traffic Management Guidelines

6.4 Optimization of Inhibit Timer for Idle Mode Prioritization

Preferential Traffic Management introduces a timer for functioning when the
traffic load is very high. It is started in a non-priority cell after receiving
information from a priority cell that the load in the priority cell is above offload
threshold EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold. The higher the value of
parameter PtmStmConfig.inhibitImpInterval, the higher the risk that a non-
priority cell stays in a more restrictive state even long after its load has dropped
significantly.

Note: The maximum delay of returning to a less restrictive state for a cell can
be up to an hour.

The PtmStmConfig.inhibitImpInterval attribute is recommended to be set to

larger values only if the load is constantly fluctuating, and it is desirable to
prevent it from going back and forth between traffic load states.

RELATED INFORMATION

2.2 Traffic Load State on page 2

5.3.2 Inhibiting Idle Mode Prioritization on page 45

8.4 Improper Time for Idle Mode Prioritization for Priority UEs on page 68

6.5 Optimization of Admission Triggered Offload

In Preferential Traffic Management, the
PtmAtoConfig.minSuccRateThreshold attribute is used to decide when to
increase the number of subscriber groups that can be offloaded.

If PtmAtoConfig.minSuccRateThreshold parameter is set to a low value, the

number of subscriber groups that are allowed for offload can slow down and the
ATO throughput can be degraded. With this setting, higher priority users are
offloaded only when non-priority users are already removed.

If PtmAtoConfig.minSuccRateThreshold parameter is set to a high value, the

number of subscriber groups that are allowed for offload is increased faster.
Higher priority users are considered for earlier offload, and priority users can be
offloaded before non-priority users. With this setting, ATO throughput is not
degraded.

60 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Performance Management of Preferential Traffic Management

7 Performance Management of Preferential

Traffic Management

Performance of the Preferential Traffic Management can be observed using

legacy and newly introduced counters and events.

Counters

— pmHoPrepRejInPtm

— pmLbSubRatioSamp

— pmLbSubRatioSum

— pmPtmAtoMeasuredUeDistr

— pmPtmCellReservedMsr

— pmPtmCellReservedSubRatio

— pmPtmHoBlocked

— pmPtmIfoMeasuredUeDistr

— pmPtmInhibitImp

— pmPtmStopIncomingIflb

— pmPtmSubRatioSumDistr

The pmLbSubRatioSum and pmLbSubRatioSamp PM counters can be used to track

when priority cells enter the "Stop incoming IFLB" or "Inhibit idle mode
prioritization" traffic load state. This is because the average subscription ratio of
a cell can be determined as pmLbSubRatioSum / pmLbSubRatioSamp * 0.1.

Events
Preferential Traffic Management introduces the following events:

Table 10 Preferential Traffic Management Events

Event Description
INTERNAL_EVENT_PTM_CELL_RESERVE Indicates the total time a cell is
D reserved for operator use. This can
happen because of the subscription

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 61

 Preferential Traffic Management Guidelines

Event Description
ratio and the MSR during the last load
balancing cycle.
INTERNAL_EVENT_PTM_CELL_TRAFFIC Indicates the traffic load state in the
_LOAD_STATE current cell depending on the relation
between the subscription ratio and the
thresholds related to the given traffic
load state.
The following traffic load states are
considered:
— Stop the incoming IFLB

— Inhibit idle mode prioritization

INTERNAL Indicates if the UE is chosen for
_EVENT_PTM_OFFLOAD_MEASURED_UE offload by Inter-Frequency Offload or
Admission-Triggered Offload.
Indicates the subscriber group to
which the UE belongs.
INTERNAL Indicates if handover is blocked
_EVENT_PTM_UE_HO_BLOCKED because of Preferential Traffic
Management cell reservation.

The solution also introduces the EVENT_PARAM_TRAFFIC_LOAD_STATE event

parameter for the INTERNAL_EVENT_LB_SUB_RATIO PM event. The parameter
captures current traffic load state by monitoring load report.

Note: Between cells in different nodes, the load report is sent in X2 cell
resource status report messages.

The RRC_SYSTEM_INFORMATION_BLOCK_TYPE_1 PM event can be used to track

when a priority cell enters and leaves the "reserved for operator use" state. In this
case, the incoming handovers of non-priority UEs are blocked. This is possible
because the RRC_SYSTEM_INFORMATION_BLOCK_TYPE_1 PM event can be used to
detect changes in SIB1 messages, and PLMN-related information—including the
status of cells as "reserved for operator use"—is broadcast in SIB1 messages.

Note: A cell can also enter or leave the "reserved for operator use" state
because of the ORC function of Subscriber Triggered Mobility.

62 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Maintenance and Troubleshooting Preferential Traffic Management

8 Maintenance and Troubleshooting

Preferential Traffic Management

The following can lead to improper operation of Preferential Traffic

Management:

— The prerequisite features are not activated or enabled.

— The recommended features are not activated or enabled.

— X2 connections between neighbor nodes are missing.

— The solution is not enabled by attribute PtmFunction.ptmEnabled.

8.1 UEs of the Wrong Type Are Grouped on Priority Cells

Non-priority UEs are grouped, or priority UEs are not grouped on priority
cells. This can occur if SPIDs are configured incorrectly.

Priority UEs attach to non-priority cells and stay there, even if a priority cell is
available in their reach.

Since priority UEs are not grouped on priority cells, appropriate access to radio
resources cannot be assured for them.

If this affects priority cells without neighboring non-priority cells, or in non-

priority cells without neighboring priority cells, this should not be treated as an
error. Without appropriate neighbor cells, there is no opportunity to move the UE
to the correct type of cell.

Cause
Idle mode prioritization of UEs is handled by the RFPM function of the Subscriber
Triggered Mobility feature. It is done using SPIDs to define groups of UEs. With
invalid SPID prioritization setting in FreqPrioEUTRA structs corresponding to
RATFreqPrio.freqPrioListEUTRA attributes for the priority frequencies, UEs of
the unintended type can end up in priority cells.

Solution

1. Check if valid priority SPIDs are configured in attribute

cellReselectionPriority in FreqPrioEUTRA structs corresponding to
attribute RATFreqPrio.freqPrioListEUTRA for priority bands.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 63

 Preferential Traffic Management Guidelines

Solution

1. Look for invalid priority SPIDs in attribute cellReselectionPriority in

FreqPrioEUTRA structs corresponding to attribute
RATFreqPrio.freqPrioListEUTRA.

2. Configure valid priority SPIDs in attribute cellReselectionPriority in

FreqPrioEUTRA structs corresponding to attribute
RATFreqPrio.freqPrioListEUTRA.

RELATED INFORMATION

4.9 Configure SPID-Based Parameters for Preferential Traffic Management on

page 33

3.6 Subscriber Triggered Mobility Overview on page 20

2.1 UE and Band Types in Preferential Traffic Management on page 2

8.2 Non-Priority Cells Are Performing Load Balancing

Handovers to Heavily Loaded Priority Cells
This can occur in the following cases:

— Non-priority cells do not react to the received traffic load state information
"Stop incoming IFLB".

— Priority cells do not propagate traffic load state information "Stop incoming
IFLB".

Choose Remedy

1. For heavily loaded priority cells, check the

EVENT_PARAM_TRAFFIC_LOAD_STATE event parameter for the
INTERNAL_EVENT_LB_SUB_RATIO PM event.

This provides information on current traffic load state of cells signaled in

load reports.

Note: Between cells in different nodes, the load report is sent in X2 cell
resource status report messages.

2. If the traffic load state of the heavily loaded cells is signaled as "Stop
incoming IFLB", go to Non-priority Cells Do Not React to Received Traffic
Load State.

64 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Maintenance and Troubleshooting Preferential Traffic Management

3. Otherwise, go to Cause 2: Priority Cells Do Not Propagate Traffic Load State

Information on page 65.

Cause 1: Non-Priority Cells Do Not React to Received Traffic Load State

Information

Solution

1. Check if the PtmIflbConfig.stopOutgoingIflbEnabled attribute is set to

true in non-priority cells to ensure that non-priority cells are enabled to react
to traffic load state "Stop incoming IFLB".

Cause 2: Priority Cells Do Not Propagate Traffic Load State Information

This can happen in the following cases:

— Incorrect configuration for cell relations

— Missing X2 connections

— Priority cells disabled to send traffic load state information

— Incorrect configuration of thresholds defining traffic load states

Solution

1. Check if cell relations are configured correctly.

2. Check if the license for Best Neighbor Relations for Intra-LTE Load
Management feature is activated, the feature is enabled and configured
correctly.

3. Check if X2 connections between neighboring eNodeBs exist.

4. Check if the PtmCellProfile.cellType attribute is set to PRIORITY.

5. Check if the thresholds—defining the traffic load states—on the priority

bands are correctly configured.
PtmIflbConfig.stopIncomingIflbThreshold must be lower than
EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 65

 Preferential Traffic Management Guidelines

RELATED INFORMATION

4.3 Enable Preferential Traffic Management on page 26

4.8 Configure Cells for Preferential Traffic Management on page 32

3.2 Best Neighbor Relations for Intra-LTE Load Management Overview on

page 13

5.2.1 Stopping Inter-Frequency Load Balancing to Priority Cells at High

Subscription Ratio on page 37

6.1 Optimization of Cell Relations for Preferential Traffic Management on page

55

6.2 Optimization of Thresholds for Preferential Traffic Management on page 56

7. Performance Management of Preferential Traffic Management on page 61

8.3 Non-Priority Cells Are Not Inhibiting Idle Mode

Prioritization of Priority UEs to Heavily Loaded Priority
Cells
When the network reaches a state of heavy load, but idle mode prioritization is
not inhibited in non-priority cells, priority UEs are still moved from non-priority to
priority cells. This overloads the priority cells that are likely already overloaded.

Cause 1: Priority Cells Do Not Propagate Traffic Load State Information

Solution

1. Check if the license for Best Neighbor Relations for Intra-LTE Load
Management feature is activated, the feature is enabled, and configured
correctly.

2. Check if the license for feature Admission-Triggered Offload is activated, and

the feature is enabled.

3. Check if X2 connections between neighboring eNodeBs exist.

4. Check if the thresholds—defining the traffic load states—on the priority

bands are correctly configured.

66 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11

 Maintenance and Troubleshooting Preferential Traffic Management

PtmIflbConfig.stopIncomingIflbThreshold must be lower than

EUtranCellFDD.lbEUtranTriggerOffloadThreshold or
EUtranCellTDD.lbEUtranTriggerOffloadThreshold.

5. Check if the PtmCellProfile.cellType attribute is set to PRIORITY.

Cause 2: Priority Cells Are Performing Admission-Triggered Offload Handovers to

Non-Priority Cells

Solution

1. Check if the license for Best Neighbor Relations for Intra-LTE Load
Management feature is activated, the feature is enabled and configured
correctly.

2. Check if the license for feature Admission-Triggered Offload is activated.

3. Check if X2 connections between neighboring cells exist.

Cause 3: Non-Priority Cells Are Not Reacting to Traffic Load State Information

Solution

1. Check the EVENT_PARAM_TRAFFIC_LOAD_STATE event parameter for the

INTERNAL_EVENT_LB_SUB_RATIO PM event to see if load reports are being
sent between eNodeBs.

Note: Between cells in different nodes, the load report is sent in X2 cell
resource status report messages.

2. Check if the PtmCellProfile.cellType attribute is set to NON_PRIORITY.

RELATED INFORMATION

4.3 Enable Preferential Traffic Management on page 26

4.8 Configure Cells for Preferential Traffic Management on page 32

5.3.2 Inhibiting Idle Mode Prioritization on page 45

3.1 Admission-Triggered Offload Overview on page 11

3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11 67

 Preferential Traffic Management Guidelines

3.2 Best Neighbor Relations for Intra-LTE Load Management Overview on

page 13

6.2 Optimization of Thresholds for Preferential Traffic Management on page 56

7. Performance Management of Preferential Traffic Management on page 61

8.4 Improper Time for Idle Mode Prioritization for Priority

UEs

Cause
The time idle mode prioritization can be inhibited for priority UEs is measured by
the inhibit timer, and set by attribute PtmStmConfig.inhibitImpInterval.

Note: The PtmStmConfig.inhibitImpInterval attribute is measured in

seconds.

The inhibit timer is stopped in the following cases:

— Node restart

— Setting the PtmFunction.ptmEnabled attribute to false

— Deleting the PtmStmConfig MO

Solution

1. Check the configuration of the PtmStmConfig.inhibitImpInterval

attribute.

RELATED INFORMATION

4.3 Enable Preferential Traffic Management on page 26

6.4 Optimization of Inhibit Timer for Idle Mode Prioritization on page 60

5.3.2 Inhibiting Idle Mode Prioritization on page 45

68 3/154 43-LZA 701 6014/1 Uen BD13B | 2020-11-11