User Guide 23/1553-LZA 701 6017/1 Uen SN34F

Ericsson Spectrum Sharing All-In-One User Guide

Contents

ESS Overview
What Is ESS?
Why ESS?
When to Use ESS?
ESS Features
ESS Prerequisites
ESS Impact on LTE Performance
FAJ 121 5147: LTE-NR FDD Spectrum Sharing Enabler
FAJ 121 5228: LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth
FAJ 121 5257: LTE-NR FDD Spectrum Sharing with NR Standalone
FAJ 121 5309: LTE-NR FDD Spectrum Sharing with Policy-based Biasing
FAJ 121 5333: LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
FAJ 121 5301: LTE-NR FDD Spectrum Sharing with Category M
FAJ 121 5306: LTE-NR FDD Spectrum Sharing with NB-IoT
FAJ 121 5382: LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation
FAJ 121 5378: LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH
FAJ 121 5406: LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
FAJ 121 5473: LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation
FAJ 121 5474: LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols
FAJ 121 5607: LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
FAJ 121 5660: LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation
ESS Operational Flow
Deploy
Optimize
Monitor
Decommission
Appendix
ESS Deployment Examples
1 ESS Overview
Learn about the basics of ESS, including the concept, the operating principles, and the application. If you are new to ESS, this part of the
guide is a good starting point.

What do you want to know?

– What is ESS?

– Why use ESS?

– When to use ESS?

1.1 What Is ESS?

Ericsson Spectrum Sharing is a unique inter-RAT solution consisting of specific features. It enables the introduction of NR in the existing LTE
infrastructure thanks to the use of intelligent scheduler algorithms and smart coordination of NR and LTE signaling. With ESS, you can
dynamically share spectrum between the technologies on the same band.

ESS enables the introduction of NR in a spectrum used by LTE FDD. Instead of having to assign spectrum resources manually to LTE and NR at
a fixed ratio, ESS assigns these resources dynamically based on traffic load, with the intention of boosting performance and end-user
experience in any location. With an existing LTE FDD radio spectrum refarmed, you can build continuous 5G coverage and decrease mid-band
resource consumption, with fewer new sites, in less time and in a cost-efficient way.

Baseline Introduce 5G +5G Coverage +Capacity Ultimate

Dual connectivity NR carrier aggregation Introduce high-bands NR as mainstream
Spectrum sharing

High-bands

Mid-bands (new)

Mid-bands (existing)

Low-bands

Legend

2G and 3G

4G
5G

4G and 5G

Carrier aggregation

Dual connectivity

L0003737A

Figure 1 Network Evolution with ESS

1.2 Why ESS?

Fast introduction, increased NR coverage, and better load balancing between NR and LTE are just a few advantages of the ESS.

ESS provides a number of benefits:

– Enables a faster introduction of NR on the already utilized LTE FDD spectrum

– Eliminates the need for spectrum refarming across NR and LTE

 – Improves resource pooling with the intent to maintain peak throughput for both NR and LTE UEs

– Balances the load between NR and LTE resources

– Increases coverage with additional low-band NR spectra

– Extends NR mid-band coverage with low-band carrier aggregation

– Improves NR TDD round trip time in FDD-TDD Carrier Aggregation compared with TDD only carrier aggregation

– Provides a shared spectrum and ensures bandwidth when LTE is declining, without the need to dedicate a large spectrum to it

1.3 When to Use ESS?

ESS is the fastest option to enable nationwide NR coverage, but it can also be used as a step towards a standalone NR deployment, or a
throughput and coverage booster for the existing NR.

The introduction of ESS is recommended in the following scenarios:

– Transition from LTE to NR EN-DC by refarming the existing LTE spectrum

– Moving from NR EN-DC to NR standalone

– Rapid rollout of nationwide NR coverage

EPC 5G EPC

Option 1 Option 1 Option 2

Legend

NR
LTE

L0003738A

Figure 2 ESS Scenario to Migrate from LTE to NR EN-DC

Dual-mode core

5G EPC 5G EPC 5GC

Option 1 Option 2 Option 1 Option 2 Option 3

Legend

NR
LTE

L0003739B

Figure 3 ESS Scenario to Migrate from NR EN-DC to NR Standalone

 EPC 5G EPC 5GC

Option 1 Option 1 Option 2

Legend

NR
LTE

L0003740A

Figure 4 ESS Scenario to Migrate from LTE to NR Standalone

See ESS Deployment Examples for aspects, such as hardware reuse and hardware expansion, and ESS Solution Guideline for various possible
deployment scenarios and various configuration aspects.
2 ESS Features
ESS is a unique inter-RAT solution that requires specific features, depending on the implemented ESS migration scenario.

Learn about which ESS features are required for a successful ESS deployment depending on the ESS migration scenario. Find out which Value
Packages contain the features you need.

Table 1 ESS Features

ESS Migration Scenario Required Features Recommended Features Additional Features

From LTE to EN-DC–ESS FAJ 121 5147: LTE-NR FDD
Spectrum Sharing Enabler – FAJ 121 5228: LTE-NR FDD – FAJ 121 5309: LTE-NR FDD
Spectrum Sharing with Spectrum Sharing with
Flexible Channel Bandwidth Policy-based Biasing
Note: This feature is not
– FAJ 121 5333: LTE-NR FDD
needed if standard
Spectrum Sharing with
bandwidth
Downlink Data and DMRS
configurations are
Multiplexing
used.
– FAJ 121 5378: LTE-NR FDD
– FAJ 121 5242: NR UE Spectrum Sharing with Rate
Throughput Booster Matching around LTE
– FAJ 121 5306: LTE-NR FDD Synchronization Signal and
Spectrum Sharing with NB- PBCH
IoT – FAJ 121 5382: LTE-NR FDD
– FAJ 121 5607: LTE-NR FDD Spectrum Sharing with Dual
Spectrum Sharing with Micro Outer Loop Link Adaptation
Sleep Tx – FAJ 121 5406: LTE-NR FDD
From EN-DC–ESS to SA–ESS FAJ 121 5257: LTE-NR FDD N/A Spectrum Sharing with
Spectrum Sharing with NR Tunable NR Subframes
Standalone
– FAJ 121 5473: LTE-NR FDD
From LTE to SA–ESS Spectrum Sharing with QoS-
– FAJ 121 5147: LTE-NR FDD – FAJ 121 5306: LTE-NR FDD
Spectrum Sharing Enabler Spectrum Sharing with NB- Aware Relative Resource
IoT Allocation
– FAJ 121 5257: LTE-NR FDD
Spectrum Sharing with NR – FAJ 121 5228: LTE-NR FDD – FAJ 121 5660: LTE-NR FDD
Standalone Spectrum Sharing with Spectrum Sharing with
Flexible Channel Bandwidth Dynamic Slot Aggregation(1)

– FAJ 121 5607: LTE-NR FDD

Spectrum Sharing with Micro
Sleep Tx
(1) The LTE-NR Spectrum Sharing with Dynamic Slot Aggregation feature is not supported in the LTE to EN-DC-ESS migration scenario.

Table 2 ESS Value Packages

Value Package Name Value Package Introduced in Benefits Included Features

Identity

– FAJ 121 5147: LTE-NR

FDD Spectrum Sharing
Enabler
Provides support for the UE with NR
– FAJ 121 5257: LTE-NR
LTE-NR FDD Ericsson L20.Q1 capabilities to access an existing LTE
FAJ 801 4012 FDD Spectrum Sharing
Spectrum Sharing N20.Q1 FDD spectrum that is shared with NR
Low-Band. with NR Standalone

– FAJ 121 5607: LTE-NR

FDD Spectrum Sharing
with Micro Sleep Tx
LTE-NR FDD ESS Multi-RAT FAJ 801 4018 L20.Q4 Allows ESS to coexist with other RATs
Coexistence N20.Q4 that use the same FDD spectrum, and – FAJ 121 5228: LTE-NR
thus maximize the FDD spectrum use FDD Spectrum Sharing
 Value Package Name Value Package Introduced in Benefits Included Features
Identity
and minimize interference between with Flexible Channel
RATs. Bandwidth

– FAJ 121 5301: LTE-NR

FDD Spectrum Sharing
with Category M

– FAJ 121 5306: LTE-NR

FDD Spectrum Sharing
with NB-IoT

– FAJ 121 5309: LTE-NR

FDD Spectrum Sharing
with Policy-based
Biasing

– FAJ 121 5333: LTE-NR

FDD Spectrum Sharing
with Downlink Data
and DMRS
Multiplexing

– FAJ 121 5378: LTE-NR

FDD Spectrum Sharing
with Rate Matching
around LTE
Synchronization Signal
and PBCH
Enables improved ESS performance
LTE-NR FDD Ericsson
L21.Q1 with increased NR efficiency for peak – FAJ 121 5382: LTE-NR
Spectrum Sharing FAJ 801 4020
N21.Q1 rate and throughput by the means of FDD Spectrum Sharing
Performance Boost
maximizing resource element usage. with Dual Outer Loop
Link Adaptation

– FAJ 121 5406: LTE-NR

FDD Spectrum Sharing
with Tunable NR
Subframes

– FAJ 121 5473: LTE-NR

FDD Spectrum Sharing
with QoS-Aware
Relative Resource
Allocation

– FAJ 121 5660: LTE-NR

FDD Spectrum Sharing
with Dynamic Slot
Aggregation

2.1 ESS Prerequisites

Prerequisites for the ESS migration scenarios, such as the required bandwidth, software, hardware, UE support, and features.

Prerequisites for ESS Migration Scenarios

The following migration scenarios exist in ESS:

– LTE to EN-DC-ESS

– EN-DC-ESS to NR SA-ESS

– LTE to NR SA-ESS

For general prerequisites, see the following tables:

– Bandwidth Prerequisites
 – Capacity Prerequisites

– Core Network Prerequisites

– Hardware Prerequisites

– Software Prerequisites

– Synchronization Prerequisites

– UE Support Prerequisites
For feature-specific prerequisites, see Table 10.

Table 3 Bandwidth Prerequisites

Category Consideration for Software References

For more information on the required capacity
licenses, see:
The capacity licenses of the NR 5+5 MHz
On the gNodeB:
Sector Carrier (FAJ 121 4930) and the 5+5
NR 5+5 MHz Sector Carrier (FAJ 121 4930)
MHz Sector Carrier (FAJ 121 3071) features
On the eNodeB:
Bandwidth Prerequisites and Support are required to be activated.
5+5 MHz Sector Carrier (FAJ 121 3071)
The supported bandwidths for the allowed
For more information on the allowed number
number of ESS cell pairs are 10 MHz, 15 MHz,
of ESS cell pairs, see: Supported Capacity and
and 20 MHz.
Configurations for LTE-NR FDD Spectrum
Sharing
To enable additional channel bandwidth
ranges in cells, the FAK 101 0157 license is
needed.
For more information on LTE FDD Channel
The Configured FDD channel bandwidth is
LTE FDD Channel Bandwidth 5 MHz Bandwidth 5 MHz (FAK 101 0157), see:
calculated based on the uplink and downlink
Hardware-Related Capabilities
bandwidth specified in the
NRSectorCarrier MO configured for the
NRCellDU.
To enable additional channel bandwidth
ranges in cells, the FAK 101 0153 license is
needed.
For more information on NR FDD Channel
The configured FDD Channel Bandwidth for
NR FDD Channel Bandwidth 5 MHz Bandwidth 5 MHz (FAK 101 0153), see:
the NR Cell is the sum of the
Hardware-Related Capabilities
[Link] and
[Link]
attributes.

Note: The number of required capacity license units for each ESS-configured cell is calculated using the following calculation: Number of
required capacity license units= Ceiling ((Configured FDD channel bandwidth) / (10 MHz))

Table 4 Capacity Prerequisites

Category Consideration for Software References

ESS requires Baseband units with the
capability to run LTE FDD and NR FDD within
For ESS capacity figures, see Supported
the same unit.
ESS Capacity Capacity and Configurations for LTE-NR FDD
Maximum capacity depends on both the LTE
Spectrum Sharing
and NR cell configuration and the features
activated.
The general support (for example, the number
For general information on DU and Baseband
of RI ports) has to be considered because it
DU and Baseband capacity support per standard, see DU and Baseband
might have impact on the capacity (for
Configurations and Capacity.
example, the number of sectors) of carriers.

Table 5 Core Network Prerequisites

Category Consideration for Software References

Connectivity The Baseband Radio Node with Mixed Mode For information on Mixed Mode configuration,
configuration has the following connections: see Mixed Mode All-In-One User Guide.

– S1 to an EPC

–
Category Consideration for Software References
NG to a 5GC (Not applicable for
migration from LTE to EN-DC-ESS)

Table 6 Hardware Prerequisites

Category Consideration for Hardware References

The introduction of Mixed Mode Baseband for
For more information on LTE-NR Mixed Mode
ESS migration causes an increased load on
Baseband Baseband units, see DU and Baseband
the existing LTE Baseband units. Adding new
Configurations and Capacity.
nodes might be required.
For the supported list of IRUs and Radio Dot
LTE-NR Mixed Mode Radio Units certified for
Radio Unit variants for both LTE and NR, see Supported
ESS are required.
Radio Capabilities.

Table 7 Software Prerequisites

Category Consideration for Software References

N20.Q1 and L20.Q1 or later is required.
Release For the anchor LTE carrier, L19.Q4 or later is N/A
required but L20.Q1 is recommended.
ENM version ENM version 19.4 or later is required. N/A

Table 8 Synchronization Prerequisites

Category Consideration for Software References

Time synchronization is recommended for an
NR system in addition to frequency
synchronization.
For FDD-based networks, NGS can be used for For more information, see Network
Time Synchronization
tight time alignment, which is required Synchronization Guidelines.
between the ESS-capable Baseband units
when running Carrier Aggregation or uplink
CoMP over Elastic RAN.

Table 9 UE Support Prerequisites

Category Consideration for Software References

UEs must be compliant with the 3GPP 15.6.0
standard and reporting their ESS capabiliy to
the eNodeB.
UEs must be capable to access an ESS cell,
that is, must support the following:
– Rate matching around LTE CRS
For information on UE handling if its ESS
UE requirements – Moved DMRS symbol not to collide with capabilities are insufficient, see Basic
LTE CRS Intelligent Connectivity.
– Periodic rate matching pattern to avoid
allocation colliding with LTE
Synchronization Signal, PBCH, and CSI-
RS
(1)

(1) Checked only if relevant functionality is used in the network side.

Table 10 Feature-Specific Prerequisites

ESS Migration Scenario

Feature LTE to EN-DC– EN-DC–ESS to LTE to NR SA–
ESS NR SA–ESS ESS
LTE-NR FDD Spectrum Sharing Enabler See LTE-NR FDD N/A See LTE-NR FDD
Spectrum Spectrum
Sharing Enabler Sharing Enabler
 ESS Migration Scenario
Feature LTE to EN-DC– EN-DC–ESS to LTE to NR SA–
ESS NR SA–ESS ESS
interaction with interaction with
other features other features
See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum
Sharing with NR Sharing with NR
LTE-NR FDD Spectrum Sharing with NR Standalone N/A
Standalone Standalone
interaction with interaction with
other features other features
See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum
Sharing with Sharing with
LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth Flexible Channel N/A Flexible Channel
Bandwidth Bandwidth
interaction with interaction with
other features other features
See LTE-NR FDD See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum Spectrum
Sharing with Sharing with Sharing with
LTE-NR FDD Spectrum Sharing with Policy-based Biasing Policy-based Policy-based Policy-based
Biasing Biasing Biasing
interaction with interaction with interaction with
other features other features other features
See LTE-NR FDD See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum Spectrum
Sharing with Sharing with Sharing with
Downlink Data Downlink Data Downlink Data
LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
and DMRS and DMRS and DMRS
Multiplexing Multiplexing Multiplexing
interaction with interaction with interaction with
other features other features other features
See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum
Sharing with NB- Sharing with NB-
LTE-NR FDD Spectrum Sharing with NB-IoT N/A
IoT interaction IoT interaction
with other with other
features features
See LTE-NR FDD See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum Spectrum
Sharing with Sharing with Sharing with
LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation Dual Outer Loop Dual Outer Loop Dual Outer Loop
Link Adaptation Link Adaptation Link Adaptation
interaction with interaction with interaction with
other features other features other features
See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum
Sharing with Sharing with
LTE-NR FDD Spectrum Sharing with Category M N/A
Category M Category M
interaction with interaction with
other features other features
See LTE-NR FDD See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum Spectrum
Sharing with Sharing with Sharing with
Rate Matching Rate Matching Rate Matching
LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization
around LTE around LTE around LTE
Signal and PBCH
Synchronization Synchronization Synchronization
Signal and PBCH Signal and PBCH Signal and PBCH
interaction with interaction with interaction with
other features other features other features
LTE-NR FDD Spectrum Sharing with Tunable NR Subframes See LTE-NR FDD See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum Spectrum
Sharing with Sharing with Sharing with
Tunable NR Tunable NR Tunable NR
Subframes Subframes Subframes
 ESS Migration Scenario
Feature LTE to EN-DC– EN-DC–ESS to LTE to NR SA–
ESS NR SA–ESS ESS
interaction with interaction with interaction with
other features other features other features
See LTE-NR FDD See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum Spectrum
Sharing with Sharing with Sharing with
LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation Tunable NR Tunable NR Tunable NR
Subframes Subframes Subframes
interaction with interaction with interaction with
other features other features other features
See LTE-NR FDD See LTE-NR FDD
Spectrum Spectrum
Sharing with Sharing with
LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation N/A Dynamic Slot Dynamic Slot
Aggregation Aggregation
interaction with interaction with
other features other features

ESS Limitations

– Only FDD operation are supported.

– Only cells with a single sector carrier are supported.

– Line Rate Limitation

The maximum supported RI link line rate is 10.1 Gbps if ESS is used in configuration with RAN Compute units in the following RAN
Compute groups:

• RAN Compute group 5a

• RAN Compute group 5c

For more information on RAN Compute groups, see DU and Baseband Configurations and Capacity.
If the connected radio unit and SFP modules enable a higher RI link line rate than 10.1 Gbps, the line rate must be lowered manually for
ESS compatibility.
The [Link] attribute can be used to set the maximum allowed RI link line rate to 10.1 for each
applicable port.
Note: The RI link line rate must be configured manually only if all of the following conditions apply:

• ESS is used in configuration with RAN Compute units in RAN Compute groups 5a or 5c

• The connected radio unit and SFP modules enable a higher RI link line rate than 10.1 Gbps

In every other case, the system automatically sets the appropriate RI link line rate.

– An EN-DC UE cannot use the same spectrum shared in an ESS cell pair as its PCell and PScell.

– Mobility between NR cells are only supported through:

• Intra-frequency and inter-frequency handovers between NR cells used in ESS cell pairs

• Intra-frequency handover between an NR cell used in an ESS cell pair and an NR cell not used in LTE-NR FDD Spectrum Sharing
Enabler if the recommended NR SSB configuration is applied

– LTE Observability
NR PUCCH has no IpN measurement. So, if the NR PUCCH is located within the LTE spectrum, the
[Link] PM counter for these resource blocks are pegged to a static default value. The
value of conversion from the static default value to dBm is -113.0.

– Interference minimization strategies

Since ESS divides the spectrum based on demands between NR and LTE, the freedom to select spectrum is limited to the spectrum given
by ESS. Spectrum assigned to LTE but not allocated to UEs is reassigned to NR for possible allocation by the shorter latency used in NR.
LTE and NR allocations follow the supported configured allocation strategies. It can result in allocations from the lowest available PRB
index compared to ESS disabled, and thus higher values on those PRBs in pmRadioRecInterferencePwrPrb.

– NR service is lost if all relevant S1 links are broken, or if the corresponding MME nodes are down.
2.2 ESS Impact on LTE Performance
Get familiar with the impact that ESS has on various aspects of the network.

Activation of ESS on an existing LTE carrier can have an impact on LTE Integrity KPIs, including potential reductions in the following:

– Peak downlink and uplink throughput, since adding additional resource elements can be required

To avoid possible collisions between LTE and NR reference signals and traffic scheduling, the highest possible throughput in either the
LTE-ESS or the NR-ESS cell does not reach the same level as in a non-ESS LTE or NR cell. For LTE cell of the ESS cell pair, the peak
throughput of the LTE UE can experience a small decrease compared to a pure LTE network. When the EN-DC-capable UE enters the
coverage of the NR cell of the ESS cell pair, the peak throughput depends on the assigned MCG and SCG resources. By using the FAJ 121
4912: LTE-NR Downlink Aggregation and FAJ 121 5091: LTE-NR Uplink Aggregation features, the peak uplink and downlink throughput
of ESS-capable UEs are much higher than in pure NR networks.

When using the FAJ 121 4856: Elastic RAN Uplink Coordinated Multi-Point Reception feature, the gain can only be observed when the
cell load is low. When ESS is activated, the load in cooperating cells can be increased by traffic from NR UEs, which might interfere with
the cooperating signals.

– Capacity, as a result of reduction in peak rates and NR traffic

– Latency

The extent of the impact depends on both the LTE and NR cell configuration and the features activated.

When ESS is deployed, no degradation in LTE accessibility, retainability, and mobility is expected.

2.3 FAJ 121 5147: LTE-NR FDD Spectrum Sharing Enabler

2.3.1 LTE-NR FDD Spectrum Sharing Enabler Overview

The LTE-NR FDD Spectrum Sharing Enabler capacity enables the shared use of the same spectrum by an LTE cell and an NR cell based on
traffic load.

Feature Name LTE-NR FDD Spectrum Sharing Enabler

Feature Identity: FAJ 121 5147
Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing
Value Package Identity: FAJ 801 4012
Node Type: Baseband Radio Node
Access Type: NR, LTE
Licensing: License-controlled capacity.

The LTE-NR FDD Spectrum Sharing Enabler capacity enables the introduction of NR in the existing spectrum utilized by LTE FDD. The capacity
offers better spectrum use by assigning LTE and NR resources in the following way:

– On shorter time scales

– Based on traffic load

 NR

Frequency
LTE

Time (1 ms)

LTE NR

ESS Coverage

L0003741A

Figure 5 Overview of LTE-NR FDD Spectrum Sharing Enabler

Instant spectrum sharing maximizes spectrum usage by tailoring PRB allocation for LTE and NR UEs based on buffer load, every Transmission
Time Interval (TTI). Frequency domain allocation is fully dynamic, varying between 100% LTE and 100% NR without any preset levels.

The LTE and NR cells use the same PRBs and TTIs through a shared carrier. The placement of reference symbols and control channels in this
shared carrier is orchestrated by a combined scheduler for both RATs. When the combined scheduler determines how to split resources
between LTE and NR, it weighs the type of traffic and considers higher priority traffic first. It evaluates the traffic load of the connected LTE
and NR UEs during each TTI, calculates the number of PRBs needed for the UEs of each RAT, and allocates resources with the highest
granularity in the frequency domain. The combined scheduler also weighs the resource division between the RATs.

Each sector carrier shared with the LTE-NR FDD Spectrum Sharing Enabler capacity has its own optional, but recommended, node unique
identifier. It is configured through the [Link] attribute for LTE and the [Link]
attribute for NR. If set, they appear in observability attributes and can also serve as a basis for generation of the required essScPairId.

The sector carriers are grouped into sector carrier pairs. These sector carrier pairs are identified through the [Link]
and [Link] attributes for LTE and NR, respectively. This attribute value must be unique within the node and
identical for each sector carrier pair. If either of these parameters is set to 0 or omitted, it means that the sector carrier does not have a pair, and
it is not selected for spectrum sharing.

The capacity can include NR PDSCH outer loop adjustment in the PDCCH SINR estimation. This results in the following benefits:

– Enhanced PDCCH performance, as the PDCCH SINR estimation can become more accurate.

– Increased robustness of NR PDCCH when LTE interference is strong.

– Lowered NR PDCCH resource usage through tuning the [Link] attribute.

Note: Tuning the [Link] attribute to reduce PDCCH resource use can have an impact on PDCCH
performance, even when the [Link] attribute is set to the default setting of No_OLA. Setting the
[Link] attribute to PDSCH_OLA mitigates the negative impact.

2.3.2 Dependencies of LTE-NR FDD Spectrum Sharing Enabler

The LTE-NR FDD Spectrum Sharing Enabler capacity requires EN-DC and mixed mode configuration features to operate. If activated, it has
an impact on multiple LTE features.

Feature dependencies and limitations of Ericsson Spectrum Sharing are only described in the Ericsson Spectrum Sharing All-In-One User Guide
and not in the individual Feature Descriptions in the LTE RAN and NR RAN libraries.
For the status of individual features, see LTE RAN Feature Status and NR RAN Feature Status.
Table 11 Feature Dependencies
Feature Impact Description
Feature Name Standard Relationship
Identity Area
FAJ 121 This feature is required for the LTE-NR FDD Spectrum Sharing Enabler
Basic Intelligent Connectivity LTE Prerequisite Connectivity
4843 capacity.
FAJ 121 This feature is required for the LTE-NR FDD Spectrum Sharing Enabler
LTE-NR Dual Connectivity NR Prerequisite Connectivity
4908 capacity.
FAJ 121 Mixed Mode This feature is required for the LTE-NR FDD Spectrum Sharing Enabler
Mixed Mode Baseband LTE Prerequisite
4565 Solutions capacity.
FAJ 121 Mixed Mode This feature is required for the LTE-NR FDD Spectrum Sharing Enabler
Mixed Mode Baseband NR Prerequisite
5021 Solutions capacity.
FAJ 121 Mixed Mode This feature is required for the LTE-NR FDD Spectrum Sharing Enabler
Mixed Mode Radio LTE Prerequisite
0906 Solutions capacity.
FAJ 121 Mixed Mode This feature is required for the LTE-NR FDD Spectrum Sharing Enabler
Mixed Mode Radio NR Prerequisite
4945 Solutions capacity.
When the Adjustable CRS Power feature is used in ESS, boosting CRS
power up to 3 dB is supported. Boosting CRS power to 4.77 dB or 6 dB is not
FAJ 121 supported in the LTE cell when the Adjustable CRS Power feature is
Adjustable CRS Power LTE Related Scheduling
3049 activated in the cell.
With ESS, it is not recommended to increase CRS power to avoid
interference to NR.
The Admission-Triggered Offload feature can offload GBR traffic load to
another LTE or WCDMA frequency based on GBR MSR thresholds.
When this feature is used together with ESS and there is NR traffic in the
FAJ 121 LTE Load NR part of the ESS cell pair, the feature operation is triggered earlier than
Admission-Triggered Offload LTE Related
3100 Management without ESS. This is because the MSR calculation takes NR traffic into
account, and due to the NR traffic, MSR thresholds are reached earlier.
When there is no NR traffic, the LTE MSR is not affected by ESS.
Increased non-GBR traffic does not affect this feature.
The AI Powered DL Link Adaptation feature supports LTE on ESS carriers
with NR interference handling. For LTE deployed on ESS carriers, the
interference created by both the LTE and NR neighbor cells is considered
when setting the dynamic BLER target.
In ESS neighbor cells, the interference rank of the LTE cell in the ESS cell
LTE pair also applies to the NR cell. If an LTE neighbor cell in the ESS
Scheduling deployment is configured to report scheduling activity, the aggregated
FAJ 121 PDSCH PRB use statistics for the ESS cell pair is included in the report. The
AI Powered DL Link Adaptation LTE Related and
5247 dynamic BLER target is selected based on this report.
Interference
Management Neighbor cell reporting configuration for ESS neighbor cells is based on the
LTE-to-LTE configuration. The same X2 procedures and X2 messages are
used for neighbor cell activity reporting regardless of deployment mode.
Note: In ESS deployments where pure NR cells exist,
interference from those NR cells is not considered.
If the LTE-NR FDD Spectrum Sharing Enabler capacity and the Automated
Load
Cell Capacity Estimation feature are activated, the capacity estimation
Automated Cell Capacity FAJ 121 Balancing, Cell
LTE Related algorithm is adjusted for the Automated Cell Capacity Estimation to apply
Estimation 3031 Capacity and
the shared NR resource impact. This way, NR resources are also considered
Throughput
in load balancing. For example, the NR load of SRB and MBB traffic.
The Automated Neighbor Relations feature uses NR neighbor information
on NR cells in ESS cell pairs to build LTE-to-NR cell relations for the NR cells.
FAJ 121 This is possible even if these NR cells do not broadcast SIB1. If the
Automated Neighbor Relations LTE Related LTE Mobility
0497 frequency of an NR cell changes, and it is part of an ESS cell pair, any
preexisting neighbor relation on any Master Node cannot be automatically
updated.
When ESS is used in LTE carrier aggregation, the downlink throughput of
each component carrier that is an ESS cell is decreased. The downlink
throughput decrease depends on the downlink and uplink NR traffic in the
ESS cell, or the type of carrier aggregation used, for example Inter-eNodeB,
FAJ 121 LTE Carrier
Carrier Aggregation LTE Related E-RAN.
3046 Aggregation
The use of NR resources and no LTE downlink traffic in MBSFN reduces the
downlink throughput in each component carrier that is an ESS cell. In
addition, the maximum allowed LTE latency is increased. The configuration
of more MBSFN subframes increases the effect on the network.
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
Carrier Aggregation-Aware IFLB LTE Related
3075 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
The LTE-NR FDD Spectrum Sharing Enabler feature provides full NR service
when the Cell Sleep Mode feature is active.
FAJ 121 Energy
Cell Sleep Mode LTE Related Some Radio 8843 B2 B66A units might restart when the Cell Sleep Mode
4390 Efficiency
feature is enabled. In this event, to prevent performance degradation, the
Cell Sleep Mode feature must be disabled.
FAJ 121 LTE Carrier When ESS is used together with the Configurable SCell Priority feature,
Configurable SCell Priority LTE Related
4701 Aggregation effective bandwidth computation does not take NR into account.
Coverage-Adapted Load FAJ 121 LTE Related Load If the LTE-NR FDD Spectrum Sharing Enabler capacity and the Coverage-
Management 3077 Balancing, Cell Adapted Load Management feature are activated, the load estimation
algorithm is adjusted for Coverage-Adapted Load Management to apply the
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
Capacity and shared NR resource impact. This way, NR resources are also considered in
Throughput load management.
The Data-Aware Carrier Management feature dynamically activates and
FAJ 121 NR Carrier
Data-Aware Carrier Management NR Related deactivates the SCells based downlink RLC buffer size in FR1 carrier
5410 Aggregation
aggregation.
LTE
When the Delay-Based Scheduling and Grant Estimation feature is used
Scheduling
Delay-Based Scheduling and Grant FAJ 121 together with ESS and there is NR SRB traffic, LTE throughput is decreased
LTE Related and
Estimation 1789 more than the general ESS impact. NR MBB traffic does not affect the
Interference
general ESS impact.
Management
The feature only affects an LTE UE that is scheduled in the same slot as an
Downlink Frequency-Selective FAJ 121 NR UE, and only if the NR PRBs match the optimal frequency selective LTE
LTE Related Scheduling
Scheduling 2053 PRBs. The feature has little impact on ESS, especially when NR usage is
low, with bursty traffic.
The Dynamic GBR Admission Control feature can limit the amount of GBR
bearers by rejecting GBR bearer setup requests on LTE based on GBR MSR
thresholds.
When this feature is used together with ESS and there is NR traffic in the
FAJ 121 LTE Admission
Dynamic GBR Admission Control LTE Related NR part of the ESS cell pair, the feature operation is triggered earlier than
4301 Control
without ESS. This is because the MSR calculation takes NR traffic into
account, and due to the NR traffic, MSR thresholds are reached earlier.
When there is no NR traffic, the LTE MSR is not affected by ESS.
Increased non-GBR traffic does not affect this feature.
When the Dynamic Load Control feature is used together with ESS and
FAJ 121 LTE Load there is NR traffic in the NR part of the ESS cell pair, the feature operation is
Dynamic Load Control LTE Related
3083 Management triggered earlier than without ESS. This is because LTE RRC procedure
latency and the number of RRC connection rejects are increased.
LTE
Scheduling When ESS is used together with Dynamic PUCCH, in few occasions
FAJ 121
Dynamic PUCCH LTE Related and attachment can fail as new PUCCH Scheduling Request resources cannot be
4377
Interference allocated. This can happen due to hard spectrum fragmentation.
Management
The Dynamic UE Admission Control can limit the amount of resources used
by rejecting UE setup requests on LTE based on MSR thresholds.
When this feature is used together with ESS and there is NR traffic in the
FAJ 121 LTE Admission
Dynamic UE Admission Control Related NR part of the ESS cell pair, the feature operation is triggered earlier than
4301 Control
without ESS. This is because the MSR calculation takes NR traffic into
account, and due to the NR traffic, MSR thresholds are reached earlier.
When there is no NR traffic, the LTE MSR is not affected by ESS.
When ESS is used together with the Efficient DRX/DTX for Connected UE
feature, there are fewer DRX scheduling occasions because of MBSFN
Efficient DRX/DTX for Connected FAJ 121 subframes.
LTE Related LTE DRX
UE 0801 Note: The value of the [Link] attribute
must be larger than PSF3.
When ESS is used with Elastic RAN Uplink Coordinated Multipoint
Reception, the uplink throughput of each ESS cell contributing in the uplink
Elastic RAN Uplink Coordinated FAJ 121 LTE Uplink
LTE Related CoMP group is decreased more than the general ESS impact. The uplink
Multi-Point Reception 4856 CoMP
throughput decrease depends on the downlink and uplink NR traffic in the
ESS cell.
FAJ 121 Emergency If ESS is used, prioritization of emergency calls in LTE can be affected by
Emergency Call Prioritization LTE Related
1039 Calls random access messages in NR.
If the LTE-NR FDD Spectrum Sharing Enabler capacity and the Evolved
Load
Load-Based Distribution at Release feature are activated, the load
Evolved Load-Based Distribution at FAJ 121 Balancing, Cell
LTE Related estimation algorithm is adjusted for Evolved Load-Based Distribution at
Release 5128 Capacity and
Release to apply the shared NR resource impact. This way, NR resources are
Throughput
also considered in load distribution.
The feature only affects an LTE UE that is scheduled in the same slot as an
Evolved Uplink Frequency- FAJ 121 NR UE, and only if the NR PRBs match the optimal frequency selective LTE
LTE Related Scheduling
Selective Scheduling 4966 PRBs. The feature has little impact on ESS, especially when NR usage is
low, with bursty traffic.
If the eNodeB has both FDD and TDD cells and uses FDD only or the FDD
FAJ 121 Number of
FDD and TDD on Same eNodeB LTE Related and TDD on Same eNodeB feature, the maximum number of cells is 12, of
4274 LTE Cells
which four cells can be part of ESS cell pairs.
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
IFLB Activation Threshold LTE Related
3058 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
Inter-Frequency Load Balancing LTE Related
440 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
Inter-Frequency Offload LTE Related
3058 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
When these LTE features are activated and used in ESS, subframe positions
allocated for LTE PRS and MBSFN might collide.
It is recommended that LTE PRS is reconfigured to avoid collision between
MBSFN subframes and PRS subframes in ESS. To do this, the following
attribute values need to be adjusted for the LTE cell that uses PRS in an ESS
LTE cell pair:
FAJ 121 Positioning
Inter-Frequency OTDOA LTE Related
3090 Reference – [Link]
System
– [Link]
If the LTE PRS configuration results in a collision between PRS subframes
and MBSFN subframes in ESS, the ESS Inconsistent Configuration alarm is
raised at unlocking the LTE cell in the ESS cell pair.
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
Inter-RAT Offload to WCDMA LTE Related
3048 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
If CFI override is enabled by
FAJ 121
Intra-LTE Handover LTE Related Handover [Link], latency can increase
0489
slightly due to postponed CFI override.
If CFI override is enabled by
FAJ 121
Intra-LTE Inter-Mode Handover LTE Related Handover [Link], latency can increase
3042
slightly due to postponed CFI override.
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
Limited Uplink-Aware IFLB LTE Related
440 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
Load
FAJ 121 Balancing, Cell To benefit from these features in ESS, each feature must be activated with
Load Based Distribution at Release LTE Related
4338 Capacity and the Automated Cell Capacity Estimation feature.
Throughput
When these LTE features are activated and used in ESS, subframe positions
allocated for LTE PRS and MBSFN might collide.
It is recommended that LTE PRS is reconfigured to avoid collision between
MBSFN subframes and PRS subframes in ESS. To do this, the following
attribute values need to be adjusted for the LTE cell that uses PRS in an ESS
LTE cell pair:
FAJ 121 Positioning
LPPa-based OTDOA Support LTE Related
3050 Reference – [Link]
System
– [Link]
If the LTE PRS configuration results in a collision between PRS subframes
and MBSFN subframes in ESS, the ESS Inconsistent Configuration alarm is
raised at unlocking the LTE cell in the ESS cell pair.
In ESS, if one of the partner cells is unavailable, the LTE Intelligent
LTE Intelligent Temperature FAJ 121
LTE Related Scheduling Temperature Handling feature is disabled on Low-Band Remote radio units
Handling 5445
with external antenna.
LTE Modulation-Aware Power FAJ 121 Dynamic power backoff is supported in ESS configurations to improve EVM
LTE Related Scheduling
Control 5577 for radios operating at full power.
With the LTE-NR Downlink Aggregation feature, if the NR cell is used in EN-
Uplink and DC in the ESS cell pair, further NR PDCP resources can be aggregated in
FAJ 121 downlink.
LTE-NR Downlink Aggregation NR Related Downlink
4912
Aggregation Note: Not applicable when migrating from LTE to SA–ESS.
When dual outer loop is configured, through configuring
[Link], the gNodeB uses the following
separate PDSCH outer loop adjustments:

– For NR slots that correspond to LTE MBSFN subframes, the MBSFN

outer loop is used to adjust PDSCH SINR.
LTE-NR FDD Spectrum Sharing
FAJ 121 Interference – For NR slots that correspond to LTE non-MBSFN subframes, the
with Dual Outer Loop Link NR, LTE Related
5382 Management
Adaptation non-MBSFN outer loop is used to adjust the PDSCH SINR.
If PDCCH link adaptation adjustment is configured with the
[Link] attribute to use PDSCH outer loop
adjustment, the individual adjustments are applied to PDCCH SINR the
same way.
If dual outer loop is configured on the SCells including external SCell, the
same adjustments are made on the SCell.
With the LTE-NR Uplink Aggregation feature, if the NR cell is used in EN-DC
Uplink and in the ESS cell pair, further NR PDCP resources can be aggregated in uplink.
FAJ 121
LTE-NR Uplink Aggregation NR Related Downlink
5091 Note:
Aggregation Not applicable when migrating from LTE to SA–ESS.
Minimum Inter-Cell Interference FAJ 121 NR Related Resource Since ESS is dividing the spectrum based on demands between NR and LTE,
Scheduling 5079 Allocation the freedom to select spectrum is limited to the spectrum given by ESS.
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
Note: RANDOM_START_WITHIN_BAND is not supported for
[Link] and
[Link].
If the value of the [Link] or the
[Link] attribute is set to
START_LOWER_EDGE or START_HIGHER_EDGE, the randomization of PRB
allocation is disabled. This might cause inter-cell interference and KPI
degradation.
LTE
Scheduling When the Minimum Rate Proportional Fair Scheduling feature is used
Minimum Rate Proportional Fair FAJ 121
LTE Related and together with ESS and there is NR SRB traffic, LTE throughput is decreased
Scheduling 0920
Interference more than the general ESS impact.
Management
LTE Mission When the Mission-Critical Push-to-Talk feature is used together with ESS
FAJ 121
Mission-Critical Push-to-Talk LTE Related Critical and there is increased NR SRB traffic, PTT user capacity is reduced
4929
Services significantly for QCI = 66 and 70.
FAJ 121 Dynamic power backoff is supported in ESS configurations to improve EVM
Modulation-Aware Power Control NR Related Scheduling
5423 for radios operating at full power.
LTE When ESS is used together with the Multi-Clustered PUSCH feature, the LTE
Scheduling throughput degradation increases with the increase in the number of NR
FAJ 121
Multi-Clustered PUSCH Related and users because NR does not have multi-clustered PUSCH. The throughput
4468
Interference degradation mostly affects LTE retransmissions, where NR cannot use the
Management clustered PUSCH between LTE transmission and retransmission.
FAJ 121 NR Carrier
NR 3CC DL Carrier Aggregation NR Related The NR 3CC DL Carrier Aggregation feature can use ESS cells as FDD SCells.
5426 Aggregation
FAJ 121 NR Carrier The NR 4CC DL Carrier Aggregation feature can use ESS cells as FDD PCells
NR 4CC DL Carrier Aggregation NR Related
5518 Aggregation and SCells.
FAJ 121 NR Carrier The NR 5CC DL Carrier Aggregation feature can use ESS cells as FDD PCells
NR 5CC DL Carrier Aggregation NR Related
5639 Aggregation and SCells.
FAJ 121 NR Carrier The NR 6CC DL Carrier Aggregation feature can use ESS cells as FDD PCells
NR 6CC DL Carrier Aggregation NR Related
5753 Aggregation and SCells.
FAJ 121 A- CSI
NR Aperiodic CSI Trigger Handling NR Related The NR Aperiodic CSI Trigger Handling feature can be used in ESS cells.
5758 Scheduling
The NR Automated Neighbor Relations feature checks the NR cell relations
FAJ 121 with the LTE-NR FDD Spectrum Sharing Enabler capacity. The NR
NR Automated Neighbor Relations NR Related NR Mobility
5218 Automated Neighbor Relations feature does not remove the cell relations if
the [Link] attribute is set to TRUE.
FAJ 121 NR Carrier The NR DL Carrier Aggregation feature can use ESS cells as SCells in EN-DC
NR DL Carrier Aggregation NR Related
5201 Aggregation deployments in Low-Band and Mid-Band.
NR DL Carrier Aggregation for FAJ 121 NR Carrier The NR DL Carrier Aggregation for Coverage Extension feature can use ESS
NR Related
Coverage Extension 5202 Aggregation cells as PCells.
NR Dynamic Slot Aggregation for FAJ 121
NR Related Voice over NR This feature is not supported in LTE to EN-DC-ESS migration scenarios.
VoNR 5471
In ESS, if one of the partner cells is unavailable, the NR Intelligent
NR Intelligent Temperature FAJ 121
NR Related Scheduling Temperature Handling feature is disabled on Low-Band Remote radio units
Handling 5444
with external antenna.
When the NR Radio Resource Partitioning feature is enabled for ESS cells
and the values of the
[Link] and the
[Link] attributes are set to
GENERAL_COMPENSATION, the RRP is adjusted on a slot basis for the
FAJ 121
NR Radio Resource Partitioning NR Related Scheduling available spectrum resources that the ESS provides for NR.
5337
When the [Link] and the
[Link] attributes are set to
ABSOLUTE, the spectrum shares must be configured based on the
information received from traffic dimensioning of the number of resources
that ESS is expected to provide for the NR cell over time.
When resource starvation prevention is configured in ESS cells, the channel
FAJ 121 capacity estimation does not take into account the limit on the spectrum
NR Rate-Controlled Scheduling NR Related Scheduling
5481 resources that is dynamically set by ESS for NR traffic. Because of this, the
maximum channel capacity might be overestimated.
NR Service-Adaptive SR Periodicity FAJ 121 NR Related Resource When the NR Service-Adaptive SR Periodicity feature is used together with
5595 Allocation ESS, the following LTE counters are impacted because more PUCCH
resources are allocated to NR:

– [Link]

– [Link]

– [Link]

– [Link]
Note: The
[Link]
PM counter exists for each possible PRB, where
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
X is the number of the PRB. For example, the
EUtranCellFDD.pmRadioRecInterferencePwrPrb1
PM counter is related to the first PRB.
NR PUCCH has no IpN measurement. So if the NR PUCCH is
located within the LTE spectrum, the
[Link]
PM counters for these resource blocks are pegged to a static
default value. The value of conversion from the static default
value to dBm is -113.0.

NR Switched Uplink for Throughput FAJ 121 NR Carrier The NR Switched Uplink for Throughput Boost feature can use ESS cells as
NR Related
Boost 5772 Aggregation FDD SCells.
The Bandwidth-Triggered Inter-System Handover function treats an ESS
FAJ 121
NR Traffic Steering NR Related Handover carrier completely as a pure NR carrier. The bandwidth calculations are
5458
always based on the total bandwidth of the NR cell.
FAJ 121 NR Carrier The NR Uplink Carrier Aggregation feature can use ESS cells as FDD PCells
NR Uplink Carrier Aggregation NR Related
5583 Aggregation and SCells.
When these LTE features are activated and used in ESS, subframe positions
allocated for LTE PRS and MBSFN might collide.
It is recommended that LTE PRS is reconfigured to avoid collision between
MBSFN subframes and PRS subframes in ESS. To do this, the following
attribute values need to be adjusted for the LTE cell that uses PRS in an ESS
LTE cell pair:
OTDOA Control Plane Location FAJ 121 Positioning
LTE Related
Support 1793 Reference – [Link]
System
– [Link]
If the LTE PRS configuration results in a collision between PRS subframes
and MBSFN subframes in ESS, the ESS Inconsistent Configuration alarm is
raised at unlocking the LTE cell in the ESS cell pair.
When these LTE features are activated and used in ESS, subframe positions
allocated for LTE PRS and MBSFN might collide.
It is recommended that LTE PRS is reconfigured to avoid collision between
MBSFN subframes and PRS subframes in ESS. To do this, the following
attribute values need to be adjusted for the LTE cell that uses PRS in an ESS
LTE cell pair:
FAJ 121 Positioning
OTDOA PRS Management LTE Related
3086 Reference – [Link]
System
– [Link]
If the LTE PRS configuration results in a collision between PRS subframes
and MBSFN subframes in ESS, the ESS Inconsistent Configuration alarm is
raised at unlocking the LTE cell in the ESS cell pair.
When these LTE features are activated and used in ESS, subframe positions
allocated for LTE PRS and MBSFN might collide.
It is recommended that LTE PRS is reconfigured to avoid collision between
MBSFN subframes and PRS subframes in ESS. To do this, the following
attribute values need to be adjusted for the LTE cell that uses PRS in an ESS
LTE cell pair:
OTDOA User Plane Location FAJ 121 Positioning
LTE Related
Support 0862 Reference – [Link]
System
– [Link]
If the LTE PRS configuration results in a collision between PRS subframes
and MBSFN subframes in ESS, the ESS Inconsistent Configuration alarm is
raised at unlocking the LTE cell in the ESS cell pair.
LTE
When ESS is used together with the PDCCH Coverage Extension feature,
Scheduling
FAJ 121 and the maximum LTE CFI = 3, the number of available CCEs decreases in
PDCCH Coverage Extension LTE Related and
4629 all subframes where NR PDCCH is scheduled. With lower maximum CFI,
Interference
there is no impact.
Management
LTE
Scheduling When ESS is used together with the PDCCH Power Boost feature, the
FAJ 121
PDCCH Power Boost LTE Related and number of available CCEs decreases slightly in all subframes where NR
3057
Interference PDCCH is scheduled. The decrease depends on the used maximum LTE CFI.
Management
LTE
Scheduling When the Prescheduling feature is used together with ESS and there is full-
FAJ 121
Prescheduling LTE Related and buffer NR UE in the NR part of the ESS cell pair, Prescheduling provides no
3057
Interference benefit. This is the same as with full-buffer LTE UEs.
Management
LTE
Scheduling When the Prioritized SR Scheduling feature is used together with ESS and
FAJ 121
Prioritized SR Scheduling LTE Related and there is high NR SRB traffic, the benefits of the Prioritized SR Scheduling
4300
Interference feature are reduced.
Management
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
Priority-Controlled Scheduling feature affects the scheduling of DRBs as
follows:

– If the [Link] attribute is

set to a value between 1 and 16, a decrease in LTE traffic volume is
to be expected. The reason for this is that when this value is set
between 1 and 16, the NR DRBs are prioritized over LTE in the
FAJ 121 shared ESS cell.
Priority-Controlled Scheduling NR Related Scheduling
5192
– When the [Link]
or the [Link] attribute is
set to HI_PRIO_OVERRIDE, LTE DRBs have absolute priority over
any initial NR DRB transmission. This is applicable also for LTE
DRBs configured with delay-based scheduling or minimum
guaranteed bit rate.

LTE
Scheduling
FAJ 121 When ESS is used together with PUCCH Overdimensioning, NR PUCCH and
PUCCH Overdimensioning LTE Related and
0883 PUSCH PRBs are handled correctly.
Interference
Management
When the QoS-Aware Scheduler feature is used together with ESS, absolute
priority for DRBs must be applied conservatively. Only QCI1 (Voice over IP)
LTE
and QCI5 (IMS signaling) are recommended for prioritization. Non-GBR
Scheduling
FAJ 121 traffic is not recommended for prioritization, unless it corresponds to
QoS-Aware Scheduler LTE Related and
0859 infrequent and low-intensity traffic similar to signaling. Any use of absolute
Interference
priority scheduling for bearers with high-intensity traffic leads to dropping
Management
UEs with less prioritized bearers. UEs are dropped due to PDUs with
undelivered RLC AM status.
FAJ 121 The Radio Dot System feature enables NR operation on Radio Dot System
Radio Dot System NR NR Related RDS Support
5022 including the support for ESS solution.
The resource utilization of an LTE cell partition is underestimated as the NR
FAJ 121
Radio resource partitioning LTE Related RAN Slicing PRB usage is not accounted for. This results in a higher priority partition
4571
occupying the resources longer if the threshold is not set properly.
LTE
Scheduling When the Relative Priority Scheduling feature is used together with ESS
FAJ 121
Relative Priority Scheduling LTE Related and and there is NR traffic in the NR part of the ESS cell pair, LTE prioritizes UEs
2037
Interference over NR depending on the minimum rate.
Management
This feature is only beneficial if the Baseband is highly loaded, or there is
Resource-Optimized Uplink FAJ 121
LTE Related Scheduling uneven LTE traffic distribution across all cells on the same Baseband. It has
Scheduling 4888
little impact on ESS, especially when NR usage is low, with bursty traffic.
Similarly to the VSWR Antenna Supervision feature, the Return Loss
Antenna Supervision feature makes measurements on the reflected power
to detect breaks in the RF feeder. It can also detect other RF-related defects
FAJ 121 LTE Load in the antenna system path connected to the radio unit. An alarm is raised if
Return Loss Antenna Supervision LTE, NR Related
4578 Management return loss is below the configured VSWR sensitivity value. The Return Loss
Antenna Supervision feature enables return loss antenna supervision of the
feeder cables for AIR and micro radio. The main benefit of using the Return
Loss Antenna Supervision feature is to detect faults in the antenna system.
When the [Link] attribute is set to
CFI_STATIC_3 in ESS, the following behavior is observed:

– Resource allocation in the subframe uses CFI=3 if the subframe has

no NR traffic.
FAJ 121
Scheduler LTE Related Scheduling
4756 – Resource allocation in the subframe uses CFI=2 if the subframe has
NR traffic or if it is an MBSFN subframe.
When the [Link] attribute is set to
CFI_AUTO_MAXIMUM_3 in ESS, resource allocation in the subframe uses up
to CFI=3 depending on the actual NR traffic load.
If CFI override is enabled by
Service or Priority-Triggered Inter- FAJ 121
LTE Related Handover [Link], latency can increase
Frequency Handover 3087
slightly due to postponed CFI override.
When ESS is used together with the Service Specific DRX feature, there are
fewer DRX scheduling occasions for short DRX on-durations, because of
FAJ 121 MBSFN subframes.
Service Specific DRX LTE Related LTE DRX
3011 Note: The value of the [Link] attribute
must be larger than PSF3.
If CFI override is enabled by
FAJ 121
Service Specific Load Management LTE Related Handover [Link], latency can increase
3047
slightly due to postponed CFI override.
Service Triggered Mobility FAJ 121 LTE Related Handover If CFI override is enabled by
1747 [Link], latency can increase
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
slightly due to postponed CFI override.
If CFI override is enabled by
FAJ 121
SGW Relocation at X2 Handover LTE Related Handover [Link], latency can increase
1819
slightly due to postponed CFI override.
LTE
Scheduling
FAJ 121
Shared LTE RAN LTE Related and Shared LTE RAN is supported for LTE cells that are part of an ESS cell pair.
0860
Interference
Management
For ESS to be configured properly, the
[Link] attribute must be populated
correctly on the eNodeB if the following conditions are true:

FAJ 121 – The Shared NR RAN feature is activated on the gNodeB.

Shared NR RAN NR Related Configuration
5211
– The gNodeB is configured for the MORAN sharing case.
This means that the [Link] attribute
cannot be empty for MORAN cells.
The [Link] and the
FAJ 121
Scheduler Low-Band NR Related Scheduling [Link] PM
5038
counters are not supported in ESS cells.
The program group restart on LTE has impact on NR for users with ESS
Software Upgrade with System FAJ 121 System
LTE, NR Related configuration. The feature has similar behavior during LTE upgrade, that is,
Adaptive Restart 5310 Restart
the NR cells are affected for ESS configuration.
TDD PCell Support for DL Carrier FAJ 121 NR Carrier The TDD PCell Support for DL Carrier Aggregation Low/Mid-Band feature
NR Related
Aggregation Low/Mid-Band 5363 Aggregation can use ESS cells as SCells.
To benefit from the UE Throughput-Aware IFLB feature in ESS, it is
recommended to activate the Automated Cell Capacity Estimation and the
Load
Limited Uplink-Aware IFLB features. If the Limited Uplink-Aware IFLB
FAJ 121 Balancing, Cell
UE Throughput-Aware IFLB LTE Related feature is activated with the UE Throughput-Aware IFLB feature, the
4219 Capacity and
[Link] attribute needs to be
Throughput
adjusted to the expected or observed average percentage of split PRBs
between LTE and NR.
The feature only affects an LTE UE that is scheduled in the same slot as an
Uplink Frequency-Selective FAJ 121 NR UE, and only if the NR PRBs match the optimal frequency selective LTE
LTE Related Scheduling
Scheduling 1799 PRBs. The feature has little impact on ESS, especially when NR usage is
low, with bursty traffic.
When ESS is used with LTE Uplink Coordinated Multipoint Reception, the
uplink throughput of each ESS cell contributing in the UL CoMP group is
Uplink Coordinated Multi-Point FAJ 121 LTE Uplink
LTE Related decreased more than the general ESS impact. The uplink throughput
Reception 3043 CoMP
decrease depends on the downlink and uplink NR traffic in the ESS cell. The
degradation can be higher if NR occupies inband PRBs for PUCCH.
The feature makes measurements on the reflected power to detect breaks in
the RF feeder. It can also detect other RF-related defects in the antenna
FAJ 121 LTE Load system path connected to the radio unit. An alarm is raised if return loss is
VSWR Antenna Supervision NR Related below the configured VSWR sensitivity value.
0706 Management
Note: VSWR measurements fail when LTE is disabled.
FAJ 121
Combined Cell LTE Conflicting Cell Coverage This feature cannot be used in ESS cells.
3025
The LTE-NR FDD Spectrum Sharing Enabler capacity and the downlink
interference management function of the ICIC - Autonomous Resource
Allocation feature cannot be used together.
Note: When using ESS, only the uplink interference
ICIC - Autonomous Resource FAJ 121 Resource management function of the ICIC - Autonomous
LTE Conflicting Resource Allocation feature is supported, with Flexible
Allocation 1074 Allocation
Channel Bandwidth disabled. Since the spectrum is
divided by ESS based on demands between NR and
LTE, the freedom to select spectrum is limited to the
spectrum given by ESS.
FAJ 121 Streaming
Internal MCE LTE Conflicting This feature cannot be used in ESS cells.
3059 Services
FAJ 121 Energy
LTE AI Powered MIMO Sleep Mode LTE Conflicting The LTE AI Powered MIMO Sleep Mode feature cannot be used in ESS cells.
5296 Efficiency
FAJ 121 Streaming
LTE Broadcast LTE Conflicting This feature cannot be used in ESS cells.
3021 Services
FAJ 121 PIM The LTE-NR FDD Spectrum Sharing Enabler capacity has a significant
LTE PIM Avoidance LTE Conflicting
5448 Avoidance impact on downlink load which is unaccounted for in PIM evaluation.
When the Air Interface Load Generator feature on ESS is activated, the
FAJ 121 downlink load generated by the Air Interface Load Generator feature is not
LTE PIM Detection LTE Conflicting PIM Detection
5436 considered during PIM detection, which might result in incorrect PIM
detection results.
 Feature Impact Description
Feature Name Standard Relationship
Identity Area
Maximum Cell Range beyond 100 FAJ 121 The Maximum Cell Range beyond 100 km feature cannot be used in ESS
LTE Conflicting Scheduling
km 5124 cells.
FAJ 121 Energy
MIMO Sleep Mode LTE Conflicting The MIMO Sleep Mode feature cannot be used in ESS cells.
3094 Efficiency
The Minimum Interference Scheduling feature does not operate by default if
the PUCCH Overdimensioning feature is activated.
For more information on the relationship with this feature, see
Interoperability with Other Features in Special Cases in Minimum
Interference Scheduling.
FAJ 121 Note:
Minimum Interference Scheduling
5222
LTE Conflicting Scheduling Since the spectrum is divided by ESS based on
demands between NR and LTE, the freedom to select
spectrum is limited to the spectrum given by
[Link] Configured Grant for URLLC Dedicated
RAN
FAJ 121 Energy
NR Booster Carrier Sleep NR Conflicting The NR Booster Carrier Sleep feature is not supported in ESS cells.
5625 Efficiency
Load
NR Downlink Data and PDCCH FAJ 121 Balancing, Cell
NR Conflicting This feature cannot be used in ESS cells.
Multiplexing 5594 Capacity and
Throughput
FAJ 121
NR Combined Cell NR Conflicting Cell Coverage This feature cannot be used in ESS cells.
5554
NR Flexible Downlink Resource FAJ 121 Resource
NR Conflicting This feature cannot be used in ESS cells.
Allocation Type Low/Mid-Band 5743 Allocation
NR Large Bandwidth Support Low- FAJ 121
NR Conflicting Connectivity This feature is not supported in ESS cells.
Band 5588
FAJ 121 PIM The LTE-NR FDD Spectrum Sharing Enabler capacity has a significant
NR PIM Avoidance NR Conflicting
5502 Avoidance impact on downlink load which is unaccounted for in PIM evaluation.
When ESS is deployed, there is a significant impact on downlink load. This
FAJ 121
NR PIM Detection NR Conflicting PIM Detection added load is not considered during NR PIM detection, which means that
5501
the PIM detection result can be incorrect.
NR Reduced UE Bandwidth FAJ 121
NR Conflicting Connectivity This feature is not supported in ESS cells.
Support 5442
If the [Link] attribute is set to a value
FAJ 121 LTE Carrier
Uplink Carrier Aggregation LTE Related between 0 and 12 it enables the Optimized Power Splitting for Uplink
4425 Aggregation
Carrier Aggregation feature enhancement in ESS deployed cells.
Uplink Configured Grant for URLLC FAJ 121
NR Conflicting Scheduling This feature cannot be used in ESS cells.
Public RAN 5407
Uplink Configured Grant for URLLC FAJ 121
NR Conflicting Scheduling This feature cannot be used in ESS cells.
Dedicated RAN 5408
Uplink Configured Grant for URLLC
FAJ 121 LTE Carrier
DedicatedSupplemental Downlink LTE Conflicting The ESS cell cannot be a supplemental downlink cell. (1)
3068 Aggregation
for Carrier Aggregation
The
PmUlInterferenceReport.pmRadioRecInterferencePwrBrPrb1–
PmUlInterferenceReport.pmRadioRecInterferencePwrBrPrb100
PM counters do not observe accumulated noise and interference power for
the corresponding PRB on the antenna branch given by the
FAJ 121 RAN Data rfBranchRxRef attribute, except LTE PUCCH. The PM counters
Uplink Interference Reporting LTE Conflicting
4157 Collection corresponding to LTE PUCCH PRB show if a particular antenna branch
given by rfBranchRxRef attribute is operational.
The EUtranCellFDD.pmRadioRecInterferencePwrPrb1–
EUtranCellFDD.pmRadioRecInterferencePwrPrb100 PM counters
can observe accumulated interference power for a PRB over all
rfBranchRxRef attributes.
If the Secondary Node is included in the gNodeB blocklist, the existing X2
X2 Configuration EN-DC LTE Related Connectivity connections of the Secondary Node are removed. All UEs connected to the
ESS cell through the Master Node or the Secondary Node are released.
LTE
Scheduling
FAJ 121 The Zero Interference VoLTE Operation feature and the LTE-NR FDD
Zero Interference VoLTE Operation LTE Conflicting and
5235 Spectrum Sharing Enabler capacity cannot be enabled in the same cell.
Interference
Management
(1) Other non-ESS cells can be supplemental downlink cells.

Limitations
In ESS, the increase of CRS power can cause interference to NR.

2.3.3 Network Impact of LTE-NR FDD Spectrum Sharing Enabler

The LTE-NR FDD Spectrum Sharing Enabler capacity has an impact on capacity and performance.
 Capacity and Performance
The LTE-NR FDD Spectrum Sharing Enabler capacity has lower downlink and uplink throughput than an individual LTE or NR network
deployment with dedicated spectrum. However, if we compare this with a network deployment, where LTE and NR use a split spectrum,
downlink and uplink throughput increases significantly.
For example, a carrier is split into two 10-MHz carriers for LTE and NR, and 90 percent of UEs use LTE. This means a drop in performance, as
the 10-MHz LTE carrier is overloaded with traffic that was previously served on 20 MHz. Compared to that, a 20-MHz carrier with LTE-NR FDD
Spectrum Sharing Enabler performs almost identically to the original 20-MHz LTE cell. Furthermore, the per-device throughput improves with
an increase in share of NR devices. It can even exceed the baseline performance on the dedicated LTE carrier, as NR devices use the carrier
more efficiently than traditional LTE devices.
Scheduling of PRBs for NR and LTE UEs with the highest granularity in the frequency domain optimizes the performance of LTE and NR in ESS,
as resources are shared fully dynamically depending on traffic load, and the QoS is considered in scheduling.

Interfaces
No impact.

Other Network Elements

No impact.
Related Information
Optimize

2.3.4 O&M Aspects of LTE-NR FDD Spectrum Sharing Enabler

Configuration management, fault management, and performance management aspects of the LTE-NR FDD Spectrum Sharing Enabler
capacity.

Activation The LTE-NR FDD Spectrum Sharing Enabler capacity requires installing LKFs and activating Software Package in the
Software Upgrade Job, to be performed during Phase 2: Software Installation, which is a common task for the ESS
migration scenarios. The instance of the capacity is modeled as CapacityState=CXC4012411 MO.

Initial For the required configuration steps, see the relevant ESS migration scenario in the ESS Operational Flow.
Configuration
Optimization LTE PDCCH symbol allocation can be optimized by configuring the [Link] attribute. For the
recommended configuration, see Configuration of Symbol Allocation for the LTE PDCCH. The recommended configuration
allows the best LTE throughput, however, an alternative configuration can be used to mitigate PDCCH reception failure
because of interference from neighbor cells.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.

Related reference
MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing Enabler

2.3.5 Feature Change History of LTE-NR FDD Spectrum Sharing Enabler

Changes that affect the LTE-NR FDD Spectrum Sharing Enabler capacity and the impact that the capacity has on the network.

Table 12 Feature Change History

Enhancement Name Description

20.Q2: Instant Spectrum Sharing The resource splitting between LTE and NR UEs made more flexible.
20.Q3: Observability Improvement for LTE-NR
Introduced PM counters and KPIs for ESS to observe throughput and latency.
Dynamic Spectrum Sharing
20.Q4: Improved NR Random Access Handling Improved prioritization of NR signaling with an increase in the Accessibility KPIs for EN-
with LTE-NR Dynamic Spectrum Sharing DC-capable UEs.
20.Q4: PM Counter Impact when Upgrading to Provided observability when upgrading to the Instant Spectrum Sharing enhancement of
Instant Spectrum Sharing the LTE-NR FDD Spectrum Sharing Enabler feature.
Changed the name of the feature associated with FAJ 121 5147 to LTE-NR FDD Spectrum
21.Q2: Feature Name Change for FAJ 121 5147
Sharing Enabler.
22.Q2: PDSCH ACK/NACK-aware PDCCH Link This enhancement allows for configuring the PDSCH outer loop adjustment to be included
Adaptation in the PDCCH SINR estimation.
 Enhancement Name Description
22.Q2: Higher CFI Value Support for LTE PDCCH in The feature enhancement allows a configuration that can enforce the allocation of more
LTE-NR FDD Spectrum Sharing symbols for the LTE PDCCH in ESS to mitigate interference from neighbor cells.
Observability for Improved PDSCH Resource Improved accuracy of PDSCH resource estimation might cause the PDCCH blocking PM
Estimation counter to increase or decrease depending on the traffic model.
23.Q2: Counters for NR MCS Distribution in The introduced PM counters improve the observability of NR MCS distribution in MBSFN
MBSFN Subframes subframes.
The feature enhancement enables the use of the Cell Sleep Mode feature in an ESS cell
Cell Sleep Mode for ESS Cells
pair.
The feature enhancement allows ESS cell pairs to use the Cell Sleep Mode feature with the
ESS Cell Sleep Mode with PUSCH Repetition
LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation feature enabled.

2.4 FAJ 121 5228: LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth

2.4.1 LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth Overview
The LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature introduces uplink and downlink flexible channel bandwidth
for NR when used in ESS. It is possible to blank PRBs and CRBs at either one or both edges of the cell bandwidth for 10 MHz, 15 MHz, or 20
MHz EN-DC–ESS cells, and 15 MHz or 20 MHz NR SA–ESS cells.

Feature Identity: FAJ 121 5228

Value Package Name: LTE-NR FDD ESS Multi-RAT Coexistence
Value Package Identity: FAJ 801 4018
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license is required for each node.

The LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature eliminates the possibility of interference between NR and other
RATs when NR is used in a shared LTE spectrum, by allowing the user to block a customizable portion of the edge of the cell spectrum. For 10
MHz, 15 MHz, and 20 MHz cells, the blocked portion can be on either side of the cell spectrum, or on both sides.

PRB blanking ensures that other RATs fit in the LTE spectrum that is shared with NR and other RATs. Therefore, it is possible for other RATs to
occupy the blanked region by reducing the number of PRBs on the LTE side, and the number of CRBs on the NR side.

The Control Channels and Reference Signals Muting in PRBs feature enhancement for Flexible Channel Bandwidth can be used to block LTE
control channels and LTE reference signals in the blanked region. For more information about this enhancement, see Flexible Channel
Bandwidth.

LTE/NR Carrier
Frequency (MHz)

LTE/NR Carrier CDMA

Frequency (MHz)

LTE/NR Carrier
Frequency (MHz)

Legend

Available RBs

Blanked RBs

L0002862A

Figure 6 Resource Block Blanking for LTE and NR

The behavior of LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature at:
 – SSB Allocation

The feature allows automatic and manual NR SSB allocation. SSB is allocated within the frequency band, in the lowest available NR-
GSCN in the bandwidth. With automatic SSB configuration, the SSB is automatically allocated within the available downlink frequency
range. With manual SSB configuration, the SSB must be placed inside the resource blocks that are available for NR in the shared
spectrum. If the SSB allocation is configured in the blanked region, the cell setup fails.

– Reference Signal Allocation

TRS is transmitted according to configuration, see Configure Flexible Channel Bandwidth for ESS. For more information about the 3GPP
technical specification, see 3GPP TS 38.214. The CSI-RS is transmitted within the available frequency range. CSI reporting is adjusted
according to the CSI-RS frequency transmission configuration.

– Control Channel and Shared Channel Allocation

• Uplink PRACH and PUCCH are allocated within the available uplink frequency range. PUSCH is allocated within the resource blocks
that are available for NR in the shared spectrum.

• PDCCH is allocated within the available CCEs. PDSCH allocation associated with USS is within the available RBGs.

[Link] Resource Block Blanking Options for LTE and NR

Resource Block Blanking configuration options and limitations for LTE and NR.

Example1 and Example 2 detail resource block blanking with LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth for LTE and NR
in a 10-MHz ESS cell pair. Table 13 shows the limitations that apply when blanking resource blocks on one or both sides of the spectrum.

Example 1 Possible Resource Block Blanking Configurations for LTE

Occupied bandwidth with

ESS Support for NR Flexible Channel Bandwidth

13 RBs
blanked

Frequency (MHz)

LTE Carrier Other RATs

L0002819C

Occupied bandwidth with

ESS Support for NR Flexible Channel Bandwidth

13 RBs
blanked

Frequency (MHz)

Other RATs LTE Carrier

L0002858B

Occupied bandwidth with

ESS Support for NR Flexible Channel Bandwidth

6 RBs blanked 5 RBs blanked

Frequency (MHz)

Other RAT LTE Carrier Other RAT

L0002860B

Example 2 Possible Resource Block Blanking Configurations for NR

 Occupied bandwidth with
ESS Support for NR Flexible Channel Bandwidth

14 RBs
blanked

Frequency (MHz)

NR Carrier Other RATs

L0002820C

Occupied bandwidth with

ESS Support for NR Flexible Channel Bandwidth

14 RBs
blanked

Frequency (MHz)

Other RATs NR Carrier

L0002859B

Occupied bandwidth with

ESS Support for NR Flexible Channel Bandwidth

7 RBs blanked 6 RBs blanked

Frequency (MHz)

Other RAT NR Carrier Other RAT

L0002861B

Table 13 Limitations for Blanking PRBs

Bandwidth Transmission Limitations

Downlink No more than the floor function of 50% of the number of PRBs can be blanked.
Maximum number of resource blocks at the top or bottom is 20 minus the number of PUCCH resource blocks
10 MHz (PRACH format F0 and format F1).
Uplink
Maximum number of resource blocks at the top or bottom is 17 minus the number of PUCCH resource blocks
(PRACH preamble format B4).
Minimum number of available PRBs is 52, 53, 54, or 55 if [Link] = 0, 3, 2, or 1 modulo 4,
15 MHz Downlink
respectively.
and 20
MHz Minimum number of available PRBs is 52.
Uplink
No more than the floor function of 25% of the number of PRBs can be blanked on either side.

The reduced chance of achieving maximum aggregation level for PDCCH can affect the DTX rate for coverage limited cases, especially for a
smaller, for example 10 MHz, bandwidth. The impact of this must be considered for downlink blanking.

[Link] Resource Block Blanking Configuration Consistency Check for the ESS Cell

The LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature allows the configuration of blanked resource blocks on the
LTE and NR side, and simultaneously checks the consistency of the configuration between LTE and NR in the ESS cell pair.

The following blanking scenarios exist:

– If the resource blocks on the LTE side are not blanked, the NR side CRBs outside of the LTE frequency range can be blanked.

– If the resource blocks on the LTE side are blanked at the top, bottom, or both sides of the cell spectrum, the NR side resource blocks must
be blanked in a compatible way. This means that if PRBs are blanked on the LTE side, CRBs are blanked on the NR side starting at the
same resource block. On the NR resource grid, the blanking considers the same resource blocks as on the LTE side and also those
resource blocks that are only available in the NR resource grid at the top or bottom of the grid.
 RB Blanking in a 10-MHz Cell
Available PRBs (39) Blanked RBs (11)
in LTE in LTE

EUtranCellFDD:
dlFrequencyAllocationProportion +
ulFrequencyAllocationProportion
NRCellDU:
dlAvailableCrbs +
ulAvailableCrbs Frequency (MHz)

Available CRBs (40) Blanked RBs (12)

in NR in NR

L0002883A

Figure 7 Position of Blanked Resource Blocks for LTE and NR in a 10-MHz Cell with Resource Blocks Blanked at the Top of the
Spectrum

RB Blanking in a 15-MHz Cell

Blanked RBs (3) Blanked RBs (4)
in LTE Available PRBs (68) in LTE in LTE

EUtranCellFDD:
dlFrequencyAllocationProportion +
ulFrequencyAllocationProportion
NRCellDU:
dlAvailableCrbs +
ulAvailableCrbs Frequency (MHz)

Blanked RBs (5) Available CRBs (68) in NR Blanked RBs (6)

in NR in NR

L0002884A

Figure 8 Position of Blanked Resource Blocks for LTE and NR in a 15-MHz Cell with Resource Blocks Blanked on Both Sides of the
Spectrum

RB Blanking in a 15-MHz Cell

Available PRBs (75) in LTE

EUtranCellFDD:
dlFrequencyAllocationProportion +
ulFrequencyAllocationProportion
NRCellDU:
dlAvailableCrbs +
ulAvailableCrbs Frequency (MHz)

Blanked RBs (2) Available CRBs (75) in NR Blanked RBs (2)

in NR in NR

L0002886A

Figure 9 Position of Blanked Resource Blocks for LTE and NR in a 15-MHz Cell with No Blanking for LTE and Resource Blocks Blanked
on Both Sides of the Spectrum for NR

RB Blanking in a 20-MHz Cell

Blanked RBs (5)
in LTE Available PRBs (95) in LTE

EUtranCellFDD:
dlFrequencyAllocationProportion +
ulFrequencyAllocationProportion
NRCellDU:
dlAvailableCrbs +
ulAvailableCrbs Frequency (MHz)

Blanked RBs (8) Available CRBs (98) in NR

in NR

L0002885A

Figure 10 Position of Blanked Resource Blocks for LTE and NR in a 20-MHz Cell with Resource Blocks Blanked at the Bottom of the
Spectrum
 The feature raises an alarm if the PRB blanking configuration on the LTE side is inconsistent with the blanking configuration on the NR side.
For more information about the alarms raised by the feature, see ESS Inconsistent Configuration.

It is recommended that the number of blocked PRBs be a multiple of the LTE RBG size.

2.4.2 Dependencies of LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth
The feature requires the LTE-NR FDD Spectrum Sharing Enabler and Flexible Channel Bandwidth features to be activated. In addition, if
activated, it has impact on LTE features.

Feature Dependencies

Table 14 Feature Dependencies

Feature Access Relationship Relationship Description

Feature Name
Identity Type Scope

LTE-NR FDD The LTE-NR FDD Spectrum Sharing Enabler feature must be
FAJ 121
Spectrum Sharing NR Prerequisite activated for the LTE-NR FDD Spectrum Sharing with Flexible
5147
Enabler Channel Bandwidth feature to be operational.
The Flexible Channel Bandwidth LTE feature must be activated
for the LTE-NR FDD Spectrum Sharing with Flexible Channel
Flexible Channel FAJ 121
LTE Prerequisite Bandwidth feature to be operational.
Bandwidth 4756
Both of the features must be configured for ESS to blank the same
resource blocks.
The PUCCH Overdimensioning feature must be activated for the
PUCCH FAJ 121
LTE Prerequisite LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth
Overdimensioning 0883
feature to be operational.
The LTE-NR FDD Spectrum Sharing with NR Standalone feature
LTE-NR FDD
FAJ 121 must be activated for the LTE-NR FDD Spectrum Sharing with
Spectrum Sharing NR Related
5257 Flexible Channel Bandwidth feature to be operational in NR SA–
with NR Standalone
ESS configuration.
The LTE-NR FDD Spectrum Sharing with NB-IoT feature can
coexist with the LTE-NR FDD Spectrum Sharing with Flexible
LTE-NR FDD
FAJ 121 Channel Bandwidth feature if the
Spectrum Sharing NR Related
5306 [Link] attribute is set to true. The
with NB-IoT
position of the NB-IoT resource blocks must be set in a way that
they do not collide with the position of blanked PRBs.
The LTE-NR FDD Spectrum Sharing with Flexible Channel
FAJ 121
TTI Bundling LTE Related Bandwidth feature reduces the frequency range that can be used
2051
by the TTI Bundling feature.
The LTE-NR FDD Spectrum Sharing with Flexible Channel
VoLTE Frequency FAJ 121
LTE Related Bandwidth feature reduces the frequency range that can be used
Hopping 4224
by the VoLTE Frequency Hopping feature.
Before reconfiguring a non-ESS cell to an ESS-cell, it must be
NR Flexible Channel FAJ 121
NR Related ensured that the blanking configuration is aligned with ESS rules.
Bandwidth 5264
Otherwise, configuring ESS cells might be blocked.
The LTE-NR FDD Spectrum Sharing with Flexible Channel
Bandwidth and the ICIC - Autonomous Resource Allocation
features cannot be used together. To use the LTE-NR FDD
Spectrum Sharing with Flexible Channel Bandwidth feature,
ICIC - Autonomous FAJ 121 disable the ICIC - Autonomous Resource Allocation feature by
LTE Conflicting
Resource Allocation 1074 setting the following attributes to FALSE:
– [Link]

– [Link]
LTE Service-Specific
The LTE Service-Specific Uplink Scheduling for Flexible Channel
Uplink Scheduling FAJ 121 Cell-level
LTE Conflicting Bandwidth feature does not work if the LTE-NR FDD Spectrum
for Flexible Channel 5848 conflict
Sharing with Flexible Channel Bandwidth feature is enabled.
Bandwidth
NR Air Interface Load Generator cannot be enabled with the LTE-
NR Air Interface FAJ 121
NR Conflicting NR FDD Spectrum Sharing with Flexible Channel Bandwidth
Load Generator 5191
feature.
2.4.3 Network Impact of LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth
The LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth has impact on network capacity and performance.

Capacity and Performance

The feature reduces the LTE-NR shared spectrum for uplink and downlink channels. Therefore, the user peak throughput and cell capacity are
reduced proportionally to the CRBs that are blanked.
The feature reduces the maximum PDCCH aggregation level for all bandwidths, which negatively impacts the coverage of the PDCCH for USS.
The following counters are impacted:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

All other throughput-related counters on the LTE and NR side are impacted by the feature.

Interfaces
No impact.

Other Network Elements

No impact.

2.4.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth
Configuration management, fault management and performance management aspects of the LTE-NR FDD Spectrum Sharing with Flexible
Channel Bandwidth feature.

Activation The feature LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth requires activation, performed during the ESS
deployment activities, see Activate Features in the Migration Scenario from LTE to EN-DC–ESS.
The feature is activated by setting the [Link] attribute to ACTIVATED in the
FeatureState=CXC4012528 MO instance.

Optimization Flexible channel bandwidth must be configured for the feature to function properly, see Configure Flexible Channel
Bandwidth for ESS.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.

2.4.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth
Changes that affect the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature and the impact that the feature has on
the network.

Table 15 Feature Change History

Enhancement Name Description

21.Q3: LTE-NR FDD Spectrum Sharing with GSM coexistence can be allowed in the LTE spectrum that is shared with NR by using
Flexible Channel Bandwidth for GSM Coexistence flexible channel bandwidth.
21.Q3: Flexible Channel Bandwidth Support for
Flexible channel bandwidth is supported for 15 MHz and 20 MHz NR SA–ESS cells.
NR SA–ESS Configuration

2.5 FAJ 121 5257: LTE-NR FDD Spectrum Sharing with NR Standalone

2.5.1 LTE-NR FDD Spectrum Sharing with NR Standalone Overview

 The feature allows the dynamic resource sharing of the same spectrum for load adaptation between an LTE cell and an NR cell deployed in
an NR standalone configuration. This allows the simultaneous deployment of LTE and NR standalone services in the same geographical
area.

Feature Name: LTE-NR FDD Spectrum Sharing with NR Standalone

Feature Identity: FAJ 121 5257
Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing
Value Package Identity: FAJ 801 4012
Node Type: Baseband Radio Node
Access Type: NR, LTE
Licensing: Licensed feature. One license is required for each node.

The LTE-NR FDD Spectrum Sharing with NR standalone feature enables sharing an LTE cell with an NR cell deployed in an NR standalone
configuration on the same spectrum. The feature ensures idle and connected mode access to the shared NR standalone cell for NR standalone
capable UEs that support ESS.

The LTE and NR cells use the same PRBs and TTIs through a shared carrier. The placement of reference symbols and control channels in this
shared carrier is orchestrated by a combined scheduler for both RATs. For more information on the combined scheduling, see LTE-NR FDD
Spectrum Sharing Enabler Overview.

The feature also allows MBSFN subframe configuration to align NR signals and prevent from interference with LTE. For more information, see
MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing with NR Standalone.

For a UE to be able to use the NR cell in the ESS cell pair, the LTE CRS rate matching capabilities must be verified in a UE capability check.

LTE CRS is transmitted in predefined symbols around which rate matching on PDSCH is applied. This is based on the UE rate matching
capability reported to the network. If the UE is in an ESS cell pair in which the NR cell is deployed in an NR standalone configuration, LTE CRS
might collide with certain messages on PDSCH. This can happen before the LTE CRS rate matching capabilities of the UE are known in the
network. The following messages can be affected:

– NR Random Access Msg2

– NR Random Access Msg4

– NR Paging message

– RRC SecurityModeCommand

– RRC UECapabilityEnquiry

– RRC RRCReconfiguration

The collision results in minor performance degradation of NR messages in downlink.

When the network receives the RRC UECapabilityInformation message from the UE that supports ESS, a UE capability check is
performed. This process is used to evaluate the UE capabilities, including LTE CRS rate matching capabilities, to consider them in RRC
reconfiguration. The network reconfigures the UE according to the reported capabilities by sending the RRCReconfiguration message to
the UE. When the UE is reconfigured for RRC connection, LTE CRS rate matching is applied on PDSCH after the RRCReconfiguration
message.

If an NR standalone capable UE does not support ESS and fails the UE capability check, it is released and redirected blindly to an LTE
frequency. Configuring the NR Coverage-Triggered NR Session Continuity feature prevents from redirecting the UE back and forth between
LTE and NR frequencies.

The PDSCH ACK/NACK-aware PDCCH Link Adaptation enhancement allows for NR PDSCH outer loop adjustment to be included in the PDCCH
SINR estimation for ESS cells using configuration.

The feature can include NR PDSCH outer loop adjustment in the PDCCH SINR estimation. This results in the following benefits:

– Enhanced PDCCH performance as the PDCCH SINR estimation can become more accurate.

– Increased robustness of NR PDCCH when LTE interference is strong.

– NR PDCCH resource use can be lowered through tuning the [Link] attribute.

Note: Tuning the [Link] attribute to reduce PDCCH resource use can have an impact on PDCCH
performance, even when the [Link] attribute is set to the default setting of No_OLA. Setting the
[Link] attribute to PDSCH_OLA mitigates the negative impact.
2.5.2 Dependencies of LTE-NR FDD Spectrum Sharing with NR Standalone
The LTE-NR FDD Spectrum Sharing with NR Standalone feature requires and is related to several LTE and NR features.

Table 16 Feature Dependencies

Feature Name Feature Identity Standard Relationship Description
The LTE-NR FDD Spectrum Sharing Enabler feature must be
activated and the ESS cell pair must be configured before activating
FAJ 121 5147: LTE-NR FDD Spectrum
FAJ 121 5147 NR Prerequisite the LTE-NR FDD Spectrum Sharing with NR Standalone feature.
Sharing Enabler
The feature relationships of this prerequisite feature also apply to the
LTE-NR FDD Spectrum Sharing with NR Standalone feature.
The shared cells in the cell relation must be deployed on a Baseband
Mixed Mode Baseband FAJ 121 4565 LTE Prerequisite
Radio Node used in LTE + NR Mixed Mode configuration.
The shared cells in the cell relation must be deployed on a Baseband
Mixed Mode Baseband FAJ 121 5021 NR Prerequisite
Radio Node used in LTE + NR Mixed Mode configuration.
Mixed Mode Radio FAJ 121 0906 LTE Prerequisite The radio unit must be used in LTE + NR Mixed Mode configuration
Mixed Mode Radio FAJ 121 4945 NR Prerequisite to support ESS-type carriers.
The UE capability check is performed as part of the Connection
Establishment process to determine if the NR standalone capable UE
supports ESS or not. UEs that fail the capability check are released
and blindly redirected to an LTE frequency.
The UE capability check determines if the standalone capable UE
that supports ESS can perform LTE CRS rate matching. The Random
Access, Security Mode, and UE Capability Enquiry procedures
between the Baseband Radio Node with Mixed Mode configuration
and the UE might show performance degradation because the
messages of the procedures collide with LTE CRS. Once the LTE CRS
rate matching capabilities of the UE are known, LTE CRS rate
matching is applied on PDSCH with UE RRC reconfiguration.
NR Standalone FAJ 121 5060 NR Prerequisite In ESS, NR paging messages are not transmitted in MBSFN
subframes that carry the following signals:

– SSB

– System Information

– TRS

– CSI-RS
Therefore, when the LTE-NR FDD Spectrum Sharing with NR
Standalone feature is used, NR paging capacity is reduced as
compared to NR standalone without ESS.
If EN-DC–NR standalone coexistence is required in the NR cell in the
ESS cell pair, the Basic Intelligent Connectivity feature must be
activated on the Baseband Radio Node with Mixed Mode
Basic Intelligent Connectivity FAJ 121 4843 LTE Prerequisite
configuration.
If the NR cell in the ESS cell pair is used only in NR standalone, the
Basic Intelligent Connectivity feature is not a prerequisite.
If EN-DC–NR standalone coexistence is required in the NR cell in the
ESS cell pair, the LTE-NR Dual Connectivity feature must be
activated on the Baseband Radio Node with Mixed Mode
LTE-NR Dual Connectivity FAJ 121 4908 NR Prerequisite
configuration.
If the NR cell in the ESS cell pair is used only in NR standalone, the
LTE-NR Dual Connectivity feature is not a prerequisite.
RedCap UEs can access and perform mobility to NR Low-Band cells
Ericsson Reduced Capability Enabler FAJ 121 5661 NR Related
that are part of an ESS cell pair.
If an NR standalone capable UE that does not support ESS fails the
UE capability check, it is released and redirected blindly to an LTE
frequency. If the NR Coverage-Triggered NR Session Continuity (FAJ
121 4983) feature is activated on the Baseband Radio Node with
NR Coverage-Triggered NR Session
FAJ 121 4983 LTE Related Mixed Mode configuration, the UE can immediately be transferred
Continuity
back to an NR frequency based on a B1 measurement report. To
avoid redirecting the UE back and forth between LTE and NR
frequencies, the configuration of NR Coverage-Triggered NR Session
Continuity feature must to be adjusted.
When these LTE features are activated and used in ESS, subframe
positions allocated for LTE PRS and MBSFN might collide.
Inter-Frequency OTDOA FAJ 121 3090 LTE Related It is recommended that LTE PRS is reconfigured to avoid collision
between MBSFN subframes and PRS subframes in ESS. To do this,
the following attribute values need to be adjusted for the LTE cell
that uses PRS in an ESS cell pair:

LPPa-based OTDOA Support FAJ 121 3050 LTE Related – [Link]

– [Link]
OTDOA Control Plane Location Support FAJ 121 1793 LTE Related If the LTE PRS configuration results in a collision between PRS
subframes and MBSFN subframes in ESS, the ESS Inconsistent
 Feature Name Feature Identity Standard Relationship Description
Configuration alarm is raised at unlocking the LTE cell in the ESS
cell pair.
Note: The values of the [Link]
attribute must be set to prevent subframe collision in the
OTDOA PRS Management FAJ 121 3086 LTE Related
following cases:

– When the LTE-NR FDD Spectrum Sharing with NR

standalone is activated.
OTDOA User Plane location Support FAJ 121 0862 LTE Related
– When the MBSFN subframe allocation for the NR
standalone cell in the ESS cell pair must be changed.
When dual outer loop is configured through configuring the
[Link] attribute, the gNodeB
uses the following separate PDSCH outer loop adjustments:

– For NR slots that correspond to LTE MBSFN subframes, the

MBSFN outer loop is used to adjust PDSCH SINR.

LTE-NR FDD Spectrum Sharing with Dual – For NR slots that correspond to LTE non-MBSFN subframes,
FAJ 121 5382 NR, LTE Related
Outer Loop Link Adaptation the non-MBSFN outer loop is used to adjust the PDSCH
SINR.
If PDCCH link adaptation adjustment is configured with the
[Link]
If dual outer loop is configured on the SCells including external SCell,
the same adjustments are made on the SCell. attribute to use PDSCH
outer loop adjustment, the individual adjustments are applied to
PDCCH SINR the same way.
The LTE-NR FDD Spectrum Sharing with NR Standalone feature has
NR PIM Avoidance FAJ 121 5502 NR Conflicting a significant impact on downlink load which is unaccounted for in
PIM evaluation.
If the Secondary Node is included in the gNodeB blocklist, the
existing X2 connections of the Secondary Node are removed. All UEs
X2 Configuration EN-DC LTE Related
connected to the ESS cell through the Master Node or the Secondary
Node are released.

Limitations
The feature allows automatic NR SSB allocation or manual configuration of SSBs in the lowest available NR-GSCN in the bandwidth.

2.5.3 Network Impact of LTE-NR FDD Spectrum Sharing with NR Standalone

The activation of the LTE-NR FDD Spectrum Sharing with NR Standalone feature has an impact on LTE throughput, and on NR standalone
performance.

Capacity and Performance

The activation of the LTE-NR FDD Spectrum Sharing with NR Standalone feature reduces LTE throughput in downlink. This is caused by
MBSFN subframe configuration to allocate subframes for the following NR resources specific to NR cells in an NR standalone deployment:

– NR SIB1

– NR Other System Information

By using the LTE-NR FDD Spectrum Sharing with NR Standalone feature, LTE CRS might collide with NR messages on PDSCH. This might lead
to performance degradation of the following NR messages specific to NR cells in an NR standalone deployment:

– NR Random Access Msg4

– NR Paging message

– RRC SecurityModeCommand

– RRC UECapabilityEnquiry

– RRC RRCReconfiguration

The performance degradation persists until the UE is reconfigured over RRC according to its LTE CRS rate matching capabilities.

Interfaces
No impact.

Other Network Elements

No impact.
2.5.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with NR Standalone
Configuration management, fault management and performance management aspects of the LTE-NR FDD Spectrum Sharing with NR
Standalone feature.

Activation The LTE-NR FDD Spectrum Sharing with NR Standalone feature requires activation, performed during the ESS
deployment activities, see Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS or Activate Features
in the Migration Scenario from LTE to SA–ESS, depending on the ESS migration scenario.
The feature is activated by setting the [Link] attribute to ACTIVATED in the
FeatureState=CXC4012507 MO instance. The feature deactivation is performed by setting the same attribute to
DEACTIVATED.

Initial The feature requires adjusting certain parameters to work properly. Recommended settings are included in the respective
Configuration migration scenario of the Initial Cell Configuration phase. Additional parameter settings are required when migrating from
EN-DC–ESS to SA–ESS, see Set Parameters to Recommended Values.
The NR Coverage-Triggered NR Session Continuity feature which prevents from redirecting the UE between LTE and NR
frequencies, is also configured during the cell configuration phase in both deployment paths from EN-DC–ESS to SA–ESS
or from LTE to SA–ESS.

Optimization The MBSFN subframe configuration is to optimize NR signaling and is performed in two scenarios: when migrating from
EN-DC–ESS to SA–ESS or from LTE to SA–ESS. For more information, see MBSFN Subframe Configuration for LTE-NR
FDD Spectrum Sharing with NR Standalone.
LTE PDCCH symbol allocation can be optimized by configuring the [Link] attribute. For the
recommended configuration, see Configuration of Symbol Allocation for the LTE PDCCH. The recommended configuration
allows the best LTE throughput, however, an alternative configuration can be used to mitigate PDCCH reception failure
due to interference from neighbor cells.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.

Related concepts
MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing with NR Standalone

2.5.5 Feature Change History of LTE-NR FDD Spectrum Sharing with NR Standalone
Changes that affect the LTE-NR FDD Spectrum Sharing with NR Standalone feature and the impact that the feature has on the network.

Table 17 Feature Change History

Enhancement Name Description

20.Q3: UE Capability Check for NR Standalone Introduced handling of NR SA-capable UEs not supporting ESS, based on the UE
with Non-Compliant UE Handling capability check.
20.Q4: Improved NR Random Access and Paging
Improved prioritization of NR signaling with an increase in the Accessibility KPIs for NR
Handling with Instant Spectrum Sharing Support
SA-capable UEs.
for NR Standalone
Changed the name of the feature associated with FAJ 121 5257 to LTE-NR FDD
21.Q2: Feature Name Change for FAJ 121 5257
Spectrum Sharing with NR Standalone.
22.Q2: PDSCH ACK/NACK-aware PDCCH Link This enhancement allows for PDSCH outer loop adjustment to be included in the PDCCH
Adaptation SINR estimation using configuration.
22.Q2: Higher CFI Value Support for LTE PDCCH in The feature enhancement allows a configuration that can enforce the allocation of more
LTE-NR FDD Spectrum Sharing symbols for the LTE PDCCH in ESS to mitigate interference from neighbor cells.
Observability for Improved PDSCH Resource Improved accuracy of PDSCH resource estimation might cause the PDCCH
Estimation blocking PM counter to increase or decrease depending on the traffic model.
23.Q2: Counters for NR MCS Distribution in MBSFN The introduced PM counters improve the observability of NR MCS distribution in MBSFN
Subframes subframes.

2.6 FAJ 121 5309: LTE-NR FDD Spectrum Sharing with Policy-based Biasing

2.6.1 LTE-NR FDD Spectrum Sharing with Policy-based Biasing Overview

The feature prioritizes non-GBR traffic between LTE and NR based on operator configuration.
 Feature Name: LTE-NR FDD Spectrum Sharing with Policy-based Biasing
Feature Identity: FAJ 121 5309
Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity: FAJ 801 4020
Node Type: Baseband Radio Node
Access Type NR, LTE
Licensing: Licensed feature. One license is required for each node.

In ESS, NR users compete against LTE users for spectrum resources. LTE users are the dominant traffic in current networks. Because of this, the
scheduling opportunity for NR users is reduced. The feature makes it possible to prioritize NR best effort traffic to overcome the competition
against LTE best effort traffic.

Note: In some cases, it might be desirable to prioritize LTE best effort traffic over NR best effort traffic instead of treating them fairly.

The feature provides option to prioritize non-GBR traffic of one RAT over the other in spectrum sharing configuration. The non-GBR
prioritization happens in time domain when traffic data in buffer exists.

Note: If the prioritized RAT does not need all of the resources, the remaining resources can be assigned to the non-prioritized RAT.

The feature uses the [Link] attribute that enables the function of favoring LTE non-GBR traffic by setting it to
LTE_BIASED. In this case, when only NR and LTE non-GBR traffic is present, more slots are used for LTE non-GBR traffic. The
[Link] attribute also enables the function of favoring NR non-GBR traffic by setting it to NR_BIASED. In this case,
when only NR and LTE non-GBR traffic is present, more slots are used for NR non-GBR traffic.

Non-GBR traffic between LTE and NR is prioritized based on operator configuration.

Note: The configuration of the [Link] attribute is effective only if the EUtranCellFDD and the NRCellDU MO
classes are locked before the configuration of the parameter and are unlocked after the configuration is done.
The possible configurations of the [Link] attribute are the following:

– FAIR

– LTE_BIASED

– NR_BIASED

Note: Without the feature, it is not possible to configure the parameter, and it is always set to the default FAIR configuration.

When the [Link] attribute is set to LTE_BIASED, the ratio between the number of TTIs in which LTE non-GBR is
prioritized over NR non-GBR is 2:1 in downlink, and 3:1 in uplink. In a TTI, when there is no demand from either RAT, 75% resources are given
to LTE and 25% resources are given to NR.

When the [Link] attribute is set to NR_BIASED, the ratio between the number of TTIs in which NR non-GBR is
prioritized over LTE non-GBR is about 3:1 both in downlink and uplink. In a TTI, when there is no demand from either RAT, 75% resources are
given to NR and 25% resources are given to LTE.

When the [Link] attribute is set to the default FAIR, the RATs are handled with equal priority. In a TTI, when there is
no demand from either RAT, 50% resources are given to each RAT.

For any configuration of the [Link] attribute, if there is no demand from LTE in uplink, all uplink resources are given
to NR.

Note: LTE GBR traffic is always prioritized over non-GBR of either RAT.
The feature offers the following benefit:

– Depending on the favored RAT, the non-GBR traffic throughput for either NR or LTE can be improved in the event of resource contention
between LTE and NR on a shared channel.
Note: Without the feature, NR and LTE non-GBR traffic are treated equally.

2.6.2 Dependencies of LTE-NR FDD Spectrum Sharing with Policy-based Biasing

The feature requires the LTE-NR FDD Spectrum Sharing Enabler feature to be installed on the node.

Table 18 Feature Dependencies

 Feature Name Feature Identity Standard Relationship Description
This feature enables the shared
FAJ 121 5147: LTE-NR FDD use of the same spectrum by an
FAJ 121 5147 NR Prerequisite
Spectrum Sharing Enabler LTE cell and an NR cell based on
traffic load.
When the LTE-NR FDD Spectrum
Sharing with Tunable NR
FAJ 121 5406: LTE-NR FDD
Subframes feature is active, the
Spectrum Sharing with Tunable FAJ 121 5406 NR Related
scheduling policy must be aligned
NR Subframes
with the configuration of the
MBSFN subframes.
In ESS deployments, the blanking
policy of the NR Intelligent
Temperature Handling feature
allows UEs to stop monitoring
NR Intelligent Temperature
FAJ 121 5444 NR Related PDCCH for a period of time to
Handling
save UE battery. This could lead to
latency for NR UEs. These effects
apply to both idle and connected
mode.

Limitations

– The feature is applicable only on ESS cells.

– The feature trades throughput of unbiased RAT for biased RAT.

2.6.3 Network Impact of LTE-NR FDD Spectrum Sharing with Policy-based Biasing
The feature affects a configuration parameter, and the capacity and performance of the network.

Parameters

Table 19 Parameters

Parameter Type Description

See MOM parameter.
The values LTE_BIASED and NR_BIASED are
[Link] Affected
added to the [Link]
parameter.

Capacity and Performance

When the [Link] attribute is set to LTE_BIASED, LTE throughput might be increased. This occurs because more
resources might be allocated to LTE. NR cell throughput is reduced in this case.
When the [Link] attribute is set to NR_BIASED, NR throughput might be increased. This occurs because more
resources might be allocated to NR. LTE cell throughput is reduced in this case.
After feature activation, the values of the following groups of NR PM counters can change:

– pmMacRbSymAvailUl

– pmMacRbSymAvailDl

The extent of these changes is highly dependent on the traffic conditions.

Interfaces
No impact.

Other Network Elements

No impact.

2.6.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Policy-based Biasing
Configuration management, fault management and performance management aspects of the LTE-NR FDD Spectrum Sharing with Policy-
based Biasing feature.

Activation The LTE-NR FDD Spectrum Sharing with Policy-based Biasing feature requires activation, performed during the ESS
deployment activities, see Activate Features in the Migration Scenario from LTE to EN-DC–ESS, Activate Features in the
 Migration Scenario from EN-DC–ESS to SA–ESS or Activate Features in the Migration Scenario from LTE to SA–ESS,
depending on the ESS migration scenario.
The feature is activated by setting the FeatureState attribute to ACTIVATED in the FeatureState=CXC4012543 MO
instance.
The feature deactivation is performed by setting the FeatureState attribute to DEACTIVATED in the
FeatureState=CXC4012543 MO.
Optimization The prioritization of non-GBR traffic between LTE and NR is configured with the [Link] attribute,
see Configure Policy-Based Biasing.
In the case of feature deactivation, the [Link] attribute must be set to FAIR.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.

Related concepts
Optimization of MBSFN Subframe Configuration for LTE and NR Downlink PRB Utilization

2.7 FAJ 121 5333: LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS
Multiplexing

2.7.1 LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing Overview
The feature provides a means of transmitting downlink data in unused resource elements in symbols carrying NR PDSCH DMRS. This
creates the opportunity for increased NR downlink data throughput on a cell level.

Feature Identity: FAJ 121 5333

Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity: FAJ 801 4020
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license is required for each node.

The feature allows NR downlink data to be transmitted in symbols carrying DMRS. This is achieved by multiplexing PDSCH with DMRS, so that
PDSCH replaces unused resource elements in symbols carrying DMRS. This applies to every resource block that is allocated for PDSCH.

The feature realizes the following benefits:

– Increased efficiency in NR resource element use

– Increased NR downlink throughput

As 3GPP states, DMRS power boosting is not possible when PDSCH is multiplexed with DMRS. This means that a trade-off exists between
DMRS power and gaining additional resource elements for downlink data. This can have an impact on the ability of the UE to decode PDSCH
and on the overall channel estimation. However, when the gNodeB does not multiplex PDSCH with DMRS, power boost is retained. In this case,
the unused DMRS resource elements are power-boosted, which improves DMRS reception. Consequently, the ability of the UE to decode
PDSCH also improves, especially at low SINR.
 No Multiplexing of PDSCH and DMRS Multiplexing of PDSCH and DMRS

Reserved for LTE and NR control channels Reserved for LTE and NR control channels

PDSCH PDSCH

DMRS (power boost) DMRS (zero boost)

Unused resource element

L0003033C

Figure 11 Resource Element Usage without and with PDSCH and DMRS Multiplexing
The [Link] attribute is used to manually enable or disable the multiplexing of PDSCH and DMRS in
individual NR cells in ESS cell pairs. The attribute can be enabled when the following criteria are met:

– The cell is configured to be in an ESS cell pair.

– The LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature is activated on the gNodeB.

The configured attribute value is checked together with the LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
feature license. If the attribute is set to true and the feature license is not installed, not activated, or expired (the
[Link] attribute is set to INOPERABLE), the NR cell of the ESS cell pair has the following attribute values
when unlocked:

• [Link] is set to FAILED.

• [Link] is set to DISABLED.

• [Link] is set to OUT_OF_SERVICE.

In addition, the following alarms are raised on the NR cell:

• The MO Configuration Requires Key Install and Feature Activation alarm is raised when the feature license is not
installed.

• The Configuration Requires Feature Activation alarm is raised when the feature is not activated or expired.

Throughput gains with the feature are expected when the PDSCH is multiplexed with DMRS for a given PDSCH transmission to a given UE in
good SINR conditions. To prevent downlink throughput degradation for the UE in the cell where such multiplexing is enabled, the following
means are provided:

– The gNodeB does not multiplex PDSCH with DMRS for a given PDSCH transmission when the gNodeB-estimated SINR in the cell is
below a configured threshold. This threshold can be tuned through using the [Link] attribute. The
attribute value applies to the individual cell. The gNodeB uses this threshold value to decide whether or not to multiplex PDSCH with
DMRS for a given PDSCH transmission.

– If activating the feature degrades throughput, and the SINR threshold cannot be tuned properly, the operator can manually disable the
multiplexing of PDSCH and DMRS in that given cell by setting the [Link] attribute to false.

Related concepts
SINR Threshold Configuration to Avoid Throughput Degradation
Related tasks
Enable or Disable the Multiplexing of PDSCH and DMRS Manually
Related Information
3GPP TS 38.212; NR; Multiplexing and channel coding
3GPP TS 38.214; NR; Physical layer procedures for data
MO Configuration Requires Key Install and Feature Activation
Configuration Requires Feature Activation
2.7.2 Dependencies of LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
The feature is related to NR features used for different cell configurations and mobility. Feature applicability is limited by cell configuration
and the number of transmission layers.

Table 20 Feature Dependencies

Feature Name Feature Identity Standard Relationship Description
The LTE-NR FDD Spectrum
Sharing Enabler must be operable
FAJ 121 5147: LTE-NR FDD before the LTE-NR FDD Spectrum
FAJ 121 5147 NR Prerequisite
Spectrum Sharing Enabler Sharing with Downlink Data and
DMRS Multiplexing feature can be
used.
The LTE-NR FDD Spectrum
Sharing with NR Standalone
feature must be activated if the
FAJ 121 5257: LTE-NR FDD
LTE-NR FDD Spectrum Sharing
Spectrum Sharing with NR FAJ 121 5257 NR Related
with Downlink Data and DMRS
Standalone
Multiplexing feature is used in NR
cells configured for NR standalone
in the ESS cell pair.
The source and the target cell can
have independent feature licenses
and configurations. At handover,
NR Mobility FAJ 121 5041 NR Related
the UE applies the DMRS
multiplexing configuration that is
available in the target cell.
The LTE-NR FDD Spectrum
Sharing with Downlink Data and
DMRS Multiplexing feature can be
applied to the local PCell and local
NR DL Carrier Aggregation FAJ 121 5201 NR Related
SCells.
Serving cells can have different
DMRS multiplexing
configurations.
The LTE-NR FDD Spectrum
Sharing with Downlink Data and
Advanced RAN Coordination FAJ 121 5271 NR Related
DMRS Multiplexing feature cannot
be used with external SCells.
When the LTE-NR FDD Spectrum
Sharing with Downlink Data and
DMRS Multiplexing feature is
active, only one additional DMRS
High Speed UE Low/Mid-Band FAJ 121 5268 NR Related
symbol can be configured for the
PDSCH.
This way, performance
degradation can be avoided.

Limitations

– Multiplexing of PDSCH and DMRS can only be applied to 1-layer or 2-layer downlink transmissions. According to 3GPP, if the gNodeB
and the UE support 3-layer or 4-layer transmissions, and the UE is in good radio conditions, 3-layer or 4-layer transmissions are used
without the multiplexing of PDSCH with DMRS.

– The feature can only be enabled in the cell if the [Link] attribute value is equal to or less than UP_TO_100KMPH.

2.7.3 Network Impact of LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
Data throughput gain can be achieved with the feature. This can be monitored by using NR KPIs and PM counters.

Capacity and Performance

When PDSCH is multiplexed with DMRS, the number of resource elements available for data increases, as shown in Table 21. 12 in the
numerator stands for two PDSCH symbols with DMRS multiplied by six PDSCH subcarriers. The denominator has nine PDSCH symbols with no
DMRS multiplied by 12 subcarriers, and the number (6, 12, 16) of resource elements used for CRS subtracted.
Table 21 Calculating the Percentage Increase of Possible PDSCH Resource Elements
Antenna Configuration Formula to Calculate Percentage Increase of Possible PDSCH Resource Elements
1TX/1RX 12 / (9 × 12 − 6)
2TX/2RX 12 / (9 × 12 − 12)
4TX/4RX 12 / (9 × 12 − 16)
The increase in the number of PDSCH resource elements, however, does not represent the same increase in NR downlink throughput.
Both the increased number of PDSCH resource elements and the actual NR downlink throughput gain are expected to vary mainly because of
the following conditions:

– Low SINR or the UE is located close to the cell edge.

– The number of downlink transmission layers used in the network. According to 3GPP, multiplexing of PDSCH with DMRS is only possible
when 1-layer or 2-layer transmissions are used. No gains can be expected where the majority of UEs use three or four layers for downlink
transmission.

As 3GPP states, DMRS power boosting is not possible when PDSCH is multiplexed with DMRS. This means that a trade-off exists between
DMRS power and gaining additional resource elements for downlink data. This can have an impact on the ability of the UE to decode PDSCH
and on the overall channel estimation.
The benefit provided by the feature can be observed when using NR KPIs representing data throughput. The NR KPI recommended to monitor
the throughput increase with the feature is Normalized Average DL MAC Cell Throughput Considering Traffic NR KPI. This NR KPI captures the
data volume increase in downlink for the served UE in the cell. For sustained traffic, this KPI shows an increase because of the increased
amount of data in downlink transmission. For traffic occurring in bursts, the KPI might show an increase because of the increased amount of
data and the decreased time for PDSCH scheduling. However, in cells with low volume of NR traffic, the KPI might not show any increase at all.
The following NR KPIs can also be observed to monitor the gain with the feature:

– Average DL MAC Cell Throughput – Fixed Time Normalized

– Normalized DL MAC Cell Throughput Considering Actual PDSCH Slot Only

– Average DL MAC DRB Throughput

– DL MAC DRB Throughput per QoS

Note: The following KPIs can be observed to monitor the gain with the feature in the LTE to EN-DC–ESS migration scenario:

– Differentiated Average DL PDCP UE Throughput Captured in eNodeB

– Differentiated Average DL PDCP UE Throughput for LTE Leg Using Carrier Aggregation, Captured in eNodeB

– Differentiated Average DL PDCP UE DRB Throughput Captured in eNodeB

The [Link] PM counter is introduced to directly observe the extent of using the NR efficiency features
in ESS. The PM counter shows the number of PDSCH resource elements that are allocated in DMRS symbols divided by the number of
subcarriers in one symbol.
After feature activation, the values of the following groups of NR PM counters might change as described below:

– The following PM counters increase by the amount of additional MAC volume that can be transmitted because of the feature:

• [Link]

• [Link]

• [Link]

• [Link]

The amount these PM counters are increased is highly dependent on traffic conditions.
Note: The [Link] PM counter can be used to monitor the increased number of PDSCH resource
elements in the LTE to EN-DC–ESS migration scenario.

– The following PM counters decrease in value proportional to the amount with which the feature is able to shorten the time required to
complete the transmission of a downlink data burst:

• [Link]

• [Link]

• [Link]

• [Link]

The amount these PM counters are decreased, if at all, is highly dependent on traffic conditions.

Interfaces
No impact.

Other Network Elements

 No impact.

2.7.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
Configuration management, fault management, and performance management aspects of the LTE-NR FDD Spectrum Sharing with
Downlink Data and DMRS Multiplexing feature.

Activation The LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature requires feature activation,
performed during the ESS deployment activities. Depending on the ESS migration scenario, see the following
information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

The LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature is activated by setting the
[Link] attribute to ACTIVATED in the FeatureState=CXC4012554 MO instance.
To deactivate the LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature, the following
steps must be taken:

1. The multiplexing of PDSCH and DMRS has to be disabled in all the cells of the gNodeB by setting the
[Link] attribute to false in all cell MO instances.

2. The attribute [Link] must be set to DEACTIVATED in the FeatureState=CXC4012554

MO instance.

Initial The [Link] attribute is used to manually enable or disable the multiplexing of PDSCH
Configuration and DMRS in individual cells.
For details on the attribute configuration, see LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS
Multiplexing Overview.

Optimization For information on when to consider tuning the configurable SINR threshold using the
[Link] attribute, see SINR Threshold Configuration to Avoid Throughput Degradation.
For information on manually enabling and disabling the multiplexing of PDSCH and DMRS when the LTE-NR FDD
Spectrum Sharing with Downlink Data and DMRS Multiplexing feature is activated, see Enable or Disable the
Multiplexing of PDSCH and DMRS Manually.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.
For NR KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with Downlink
Data and DMRS Multiplexing feature, see Network Impact of LTE-NR FDD Spectrum Sharing with Downlink Data and
DMRS Multiplexing.

2.7.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing
Changes that affect the LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature and the impact that the
feature has on the network.

Table 22 Feature Change History

Enhancement Name Description

A new attribute to configure the SINR threshold on cell level and a PM
21.Q3: NR Efficiency Enhancement for LTE-NR FDD Spectrum Sharing counter to monitor NR efficiency are introduced to the LTE-NR FDD
with Downlink Data and DMRS Multiplexing Spectrum Sharing with Downlink Data and DMRS Multiplexing
feature.

2.8 FAJ 121 5301: LTE-NR FDD Spectrum Sharing with Category M

2.8.1 LTE-NR FDD Spectrum Sharing with Category M Overview

The LTE-NR FDD Spectrum Sharing with Category M feature enables the shared use of the same spectrum by LTE UEs, NR UEs, and
Category M1 UEs.
 Feature
FAJ 121 5301
Identity:
Value
Package LTE-NR FDD ESS Multi-RAT Coexistence
Name:
Value
Package FAJ 801 4018
Identity:
Node
Baseband Radio Node
Type:
Licensing: Licensed feature. One license is required for each node.

The feature enables dynamic time and frequency resource sharing between NR, LTE, and Category M. With the support from this feature, the
Category M Access feature can be enabled on an LTE cell in an ESS cell pair. As a result, low-complexity Category M1 UEs can use an ESS
configuration.

The feature operates in a way that ensures Category M service in its dedicated part of the carrier. By default, Category M is prioritized over LTE
and NR for the same service type. For example, Category M data transmission is prioritized over LTE and NR data transmission.

The feature supports both NR standalone and EN-DC deployments, and the following ESS bandwidths:

– 10 MHz

– 15 MHz

– 20 MHz

Category M PRBs
NR PRBs
Frequency

LTE PRBs

Time (1 ms)

LTE Category M1 NR

ESS Coverage

L0003078A

Figure 12 Dynamic Spectrum Sharing between the RATs

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M
Related reference
Network Impact of LTE-NR FDD Spectrum Sharing with Category M

[Link] LTE-NR FDD Spectrum Sharing with Category M Resource Sharing

In an ESS cell pair, LTE, NR, and Category M share the same resources. The feature is optimized to ensure that the effect of Category M on
the other RATs is minimized.
General Characteristics
In general, Category M competes for radio resources with LTE and it uses static PRBs. The LTE-NR FDD Spectrum Sharing with Category M
feature is optimized to avoid conflict between the RATs. When this feature is activated, LTE, NR and Category M can be used together.
Category M uses static PRBs for the following transmission types:

– Broadcast messages

– PRACH resources

– PUCCH resources

Broadcast transmission provides static load from Category M in the downlink, while PUCCH transmission provides static load in the uplink.
Category M PRACH transmissions do not have additional impact on NR, because Category M and LTE use the same PRACH resources in an
ESS configuration.

Downlink Resource Sharing Characteristics

The scheduler arranges the downlink Category M, LTE, and NR resources to avoid direct interference between the RATs. The feature minimizes
the effect of misalignment between LTE and NR RBGs, and the Category M downlink narrowband location. As a result, LTE and NR UEs can be
scheduled in the same slot around the Category M resources.
The Category M downlink narrowband location within ESS does not follow all the guidelines described in Category M Guideline.
Note: The feature requires a specific configuration to ensure Category M and NR standalone service when both RATs have high load at the
same time. Invalid Category M subframes must be configured to prioritize the CORESET#0 transmission of NR standalone in the time
domain.
This configuration is controlled with the [Link] attribute, which must be set to at least
value 1 in an NR standalone deployment.
Frequency

Time (1 ms)

Legend

Category M PRBs

NR CRBs

LTE PRBs
L0003242A

Figure 13 Category M, LTE and NR Downlink Resources Scheduled in the Same Slots

For more information on the effects of RBG misalignment, see Category M Guideline.
For more information about CORESET#0 transmission, see Manage Radio Network.
For more information about CORESET#0 in ESS scheduling, see LTE-NR FDD Spectrum Sharing with NR Standalone Impact on EN-DC–NR SA
Coexistence in the Same Cell.

Uplink Resource Sharing Characteristics

In the uplink, the RATs either have dedicated resources for a given channel, or they share the channel resources with other RATs.

Table 23 Category M, LTE and NR Uplink Resource Sharing Characteristics

Uplink Channel Resource Sharing Characteristic

Dedicated resources for NR. Shared resources between Category M
PRACH
and LTE.
Dedicated resources for each RAT.

PUCCH Note: The Category M PUCCH uses resources in the lower and upper
part of the spectrum, which affects the LTE and NR resource
share.
 Uplink Channel Resource Sharing Characteristic
Shared between the RATs.
PUSCH For Category M, this means that uplink narrowbands are placed in the
shared PUSCH area.
It is recommended to configure the Category M PUSCH resources on the opposite side of the spectrum as the Category M PRACH resources.
This ensures that the LTE and the NR PUSCH transmissions have as many contiguous PRBs as possible in non-PRACH subframes. When there
are no PRACH transmissions, the LTE and NR PUSCH can use these PRBs if they are allocated contiguously.
The PRACH frequency sharing between Category M and LTE is a mandatory setting in an ESS configuration. The common PRACH resources
are configured as follows:

– The [Link] attribute must be set to true.

– The [Link] attribute must be set to 44 to decrease the number of LTE preambles to 44. This is the
recommended setting if the number of Category M preambles is not changed.

NR PUCCH

Category M PUCCH

LTE PUCCH

Category M PUSCH

LTE and
NR PUSCH
Configured on
opposite sides
NR PRACH

Category M and
LTE PRACH

LTE PUCCH

Category M PUCCH

NR PUCCH

Legend
Category M resources
LTE resources
NR resources
Channel sizes are not to scale.
L0003243A

Figure 14 Category M, LTE and NR Uplink Channel Resource Allocation

For more information about PRACH frequency sharing, see the Category M Flexible Preamble Selection Feature Description and Category M
Guideline.

[Link] Category M Resource Sharing Guidelines

The LTE-NR FDD Spectrum Sharing with Category M feature supports configuration options to adjust the resource share of Category M.
This can reduce the effect of Category M on LTE and NR traffic.

At high LTE or NR load, Category M traffic can affect LTE or NR traffic negatively. The negative effect occurs because Category M is prioritized
over LTE and NR for the same service type in the Category M-dedicated narrowband. For example, Category M voice is prioritized over LTE and
NR voice, or Category M data is prioritized over LTE and NR data.

This negative effect can be reduced by limiting the number of Category M narrowbands. However, reducing the number of Category M
narrowbands limits Category M resource share also in situations when such limitation is not needed, for example, when the LTE and NR load is
not high. Also, at least one narrowband is necessary to have Category M service.

As an alternative, the LTE-NR FDD Spectrum Sharing with Category M feature supports resource control through MO attributes, which can be
seen in Table 24. Through these resource control attributes, the Category M PRB share can be limited specifically at high LTE or NR load, while
supporting multiple narrowbands to handle high Category M peaks. This solution is supported for both EN-DC and NR standalone
deployments.
The limitation on Category M PRB share is only applied when the LTE or NR resources are fully utilized, meaning that the load is considered
high. The feature checks if there is a resource conflict for each specific subframe. If there is no resource conflict, then Category M resource share
is not limited. If there is a resource conflict, then the limitation is applied.

The [Link] PM counter is pegged when the LTE or NR resources are fully utilized.

For example, during daytime, users are more active, and the LTE and NR data traffic is high. During the day, Category M traffic is limited to a
certain resource share to avoid a negative effect on LTE and NR service. At night, users are less active, and LTE and NR traffic is normal or low.
The limitation of Category M traffic is lifted, and Category M UEs might be served with high data rates.

The resource control attributes are recommended to be set based on the relative priority of Category M traffic in the ESS cell pair. For example,
a high value corresponds to high resource share, and therefore high priority.

In the context of this feature, the priority is not a specific setting, but the general importance of Category M in a network. The following priority
levels can be defined:
High Category M Category M priority is high when Category M is considered important also at high LTE or NR load. The negative effect
Priority on LTE and NR is acceptable in this case.

Moderate Category Category M priority is moderate when reduced Category M service is acceptable in the cell at high LTE or NR load, but
M Priority Category M service is still important.

Low Category M Category M priority is low when Category M service is not important in the cell at high LTE or NR load. Category M
Priority service might be delayed at this importance level, for example, Category M requests might be delayed until the night.

For specific parameter value recommendations for each priority, see Parameter Recommendations for LTE-NR FDD Spectrum Sharing with
Category M.

Table 24 Category M Resource Sharing Configuration Attributes

MO Attribute Use Case Description

This attribute is the primary tool for Category
M resource control. This is because the
negative effect of Category M traffic at high
LTE or NR load is most common in downlink
traffic.
The value of this MO attribute affects both the
downlink and the uplink service, because
uplink service is granted in downlink.
[Link] Downlink and uplink PRB share
During bidirectional Category M traffic, the
Category M uplink service is impacted more
compared to the case when Category M traffic
is uplink only.
Category M uplink service can be severely
impacted if the
[Link]
attribute is set to the lowest possible value.
This attribute is a secondary tool for Category
M resource control.
Uplink is typically not congested for LTE and
NR. Generally, it is not necessary to limit the
Category M uplink PRB share. This attribute is
only recommended to be used when Category
M traffic affects the LTE or NR uplink traffic,
[Link] Uplink PRB share only
but the effect on downlink is small.
Note: Limiting only the Category M uplink
resource share might increase the
negative effect on LTE and NR
downlink throughput, and it is not
recommended.

This attribute is a secondary tool for Category

M resource control.
Category M traffic might affect LTE and NR
PRB share of Category M RRC establishments when many Category M UEs try to connect to
EUtranCellFDD.dlCatmEssShareSrb0
only the cell close in time. For this rare use case,
this attribute is used to limit the number of
downlink PRBs available for Category M RRC
establishment.
 These resource control MO attributes limit the number of Category M PRBs. The parameter values directly correspond to the number of PRBs,
for example, value 100 equals 10 PRBs.

Setting the [Link] attribute value to 20 (2 PRBs) can reduce the Category M resource share to about one third
of the normal Category M cell service with one downlink narrowband.
Related tasks
Optimize Category M Resource Share
Related reference
Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

2.8.2 Dependencies of LTE-NR FDD Spectrum Sharing with Category M

Table 25 Feature Dependencies

Feature Feature Standard Relationship Relationship Description

Name Identity Scope

FAJ 121 5147:

The LTE-NR FDD Spectrum Sharing Enabler feature
LTE-NR FDD Node-level
FAJ 121 5147 NR Prerequisite must be activated for the LTE-NR FDD Spectrum
Spectrum prerequisite
Sharing with Category M feature to be operational.
Sharing Enabler
The LTE-NR FDD Spectrum Sharing with NR
Standalone feature must be operable before the LTE-
FAJ 121 5257: NR FDD Spectrum Sharing with Category M feature can
LTE-NR FDD be used with NR standalone deployment.
Spectrum FAJ 121 5257 NR Related The
Sharing with NR [Link]
Standalone attribute must be set to a minimum value of 1 to enable
the coexistence of NR standalone and Category M in a
high load scenario.
The Category M Access feature must be activated for
Category M Node-level
FAJ 121 4658 MI Prerequisite the LTE-NR FDD Spectrum Sharing with Category M
Access prerequisite
feature to be operational.
Category M
It is recommended to activate the LTE-NR FDD
Flexible Uplink
FAJ 121 4979 MI Related Spectrum Sharing with Category M feature with the
Channel
Category M Flexible Uplink Channel Allocation feature.
Allocation
If the LTE-NR FDD Spectrum Sharing with Category M
Category M
and the Category M Connected Mode Mobility features
Connected Mode FAJ 121 4784 MI Related
are both activated, latency can increase for UEs that
Mobility
require a measurement gap.
The Category M Dynamic Resource Sharing with LTE
feature can be used together with the resource control
MO attributes of the LTE-NR FDD Spectrum Sharing
with Category M feature, but they have different levels
Category M of prioritization. The Category M Dynamic Resource
Dynamic Sharing with LTE feature prioritizes on the service level,
FAJ 121 5052 MI Related
Resource while the resource control MO attributes prioritize
Sharing with LTE based on the PRB utilization level and they do not
consider service type. If the resource control MO
attributes are used with the lowest values, the Category
M Dynamic Resource Sharing with LTE feature has little
additional effect.
If the LTE-NR FDD Spectrum Sharing with Category M
and the Category M Basic VoLTE features are both
Category M activated, coverage can decrease. There is also a
FAJ 121 4766 MI Related
Basic VoLTE negative impact on the possible number of Category M
UEs in the cell that use VoLTE, since a portion of the
subframes is reserved for NR.
Category M If the LTE-NR FDD Spectrum Sharing with Category M
Dynamic HARQ- FAJ 121 4982 MI Related and the Category M Dynamic HARQ-ACK Delay
ACK Delay features are both activated, throughput can decrease.
Category M If the LTE-NR FDD Spectrum Sharing with Category M
HARQ-ACK FAJ 121 4981 MI Related and the Category M HARQ-ACK Bundling features are
Bundling both activated, throughput can decrease.
Feature Feature Standard Relationship Relationship Description
Name Identity Scope

Category M
The Category M Multiple Narrowband Support feature
Multiple
FAJ 121 5188 MI Related enables the use of more narrowbands for Category M
Narrowband
traffic.
Support
If the LTE-NR FDD Spectrum Sharing with Category M
Inter-eNodeB
and the Inter-eNodeB Carrier Aggregation features are
Carrier FAJ 121 4469 LTE Related
both activated, the UE has less chance to perform
Aggregation
carrier aggregation.
The Contention Free Random Access feature can be
Contention Free
FAJ 121 2055 LTE Related used with the LTE-NR FDD Spectrum Sharing with
Random Access
Category M feature to optimize random access.
If the LTE-NR FDD Spectrum Sharing with Category M
Dynamic PUCCH FAJ 121 4377 LTE Related and the Dynamic PUCCH features are both activated,
UE peak rate can decrease in LTE and NR cells.
If the LTE-NR FDD Spectrum Sharing with Category M
Dynamic GBR
and the Dynamic GBR Admission Control features are
Admission FAJ 121 1748 LTE Related
both activated, it is recommended to adjust the
Control
thresholds.
If the LTE-NR FDD Spectrum Sharing with Category M
Dynamic Load
FAJ 121 3083 LTE Related and the Dynamic Load Control features are both
Control
activated, it is recommended to adjust the thresholds.
FAJ 121 5228:
LTE-NR FDD
If the LTE-NR FDD Spectrum Sharing with Category M
Spectrum
FAJ 121 5228 NR Conflicting Cell-level conflict feature is activated, downlink blanking inside the LTE
Sharing with
spectrum is not possible.
Flexible Channel
Bandwidth
The LTE-NR FDD Spectrum Sharing with Category M
feature cannot be used when the
[Link] attribute is
set to NSA_SA_55_PERCENT.
With the LTE-NR FDD Spectrum Sharing with Tunable
FAJ 121 5406: NR Subframes feature, the Category M performance
LTE-NR FDD can decrease because of the limited Category M PDCCH
Spectrum and Category M PDSCH. The uplink and downlink cell
FAJ 121 5406 NR Related
Sharing with peak throughput and the UE peak throughput can
Tunable NR decrease.
Subframes When the percentage of the MBSFN subframe values is
set to 25% or higher, the
[Link]
attribute is recommended to be set to 0. A higher
MBSFN ratio also affects the evaluation of the
Category M System Information window length.
If the LTE-NR FDD Spectrum Sharing with Category M
Load Based CA and the Load Based CA SCell Handling features are
FAJ 121 4939 LTE Related
SCell Handling both activated, it is recommended to adjust the
thresholds.
If the LTE-NR FDD Spectrum Sharing with Category M
and the Minimum Rate Proportional Fair Scheduler
Minimum Rate
features are both activated, the relative throughput
Proportional Fair FAJ 121 0920 LTE Related
and latency impact can require adjustment. This is
Scheduler
particularly applicable if the Category M Dynamic
Resource Sharing with LTE feature is also activated.
If the LTE-NR FDD Spectrum Sharing with Category M
feature is activated with the NR Mobility and the
Category M Multiple Narrowband Support features, the
NR Mobility FAJ 121 5041 NR Related
number of failed handovers can increase during high
load in 10 MHz LTE cells with the Category M Access
feature enabled.
NR Radio The NR Radio Resource Partitioning feature and the
Node-level
Resource FAJ 121 5337 NR Conflicting LTE-NR FDD Spectrum Sharing with Category M
conflict
Partitioning feature cannot be operational at the same time.
 Feature Feature Standard Relationship Relationship Description
Name Identity Scope

The Radio Resource Partitioning feature and the LTE-

Radio Resource Node-level
FAJ 121 4571 LTE Conflicting NR FDD Spectrum Sharing with Category M feature
Partitioning conflict
cannot be operational at the same time.
If this feature is activated in the ESS cell, the
Inter-Frequency recommended value for the
FAJ 121 3090 LTE Related
OTDOA [Link]
attribute is 0.
If this feature is activated in the ESS cell, the
LPPa-based recommended value for the
FAJ 121 3050 LTE Related
OTDOA Support [Link]
attribute is 0.
If this feature is activated in the ESS cell, the
OTDOA Control
recommended value for the
Plane Location FAJ 121 1793 LTE Related
[Link]
Support
attribute is 0.
If this feature is activated in the ESS cell, the
OTDOA PRS recommended value for the
FAJ 121 3086 LTE Related
Management [Link]
attribute is 0.
If this feature is activated in the ESS cell, the
OTDOA User
recommended value for the
Plane Location FAJ 121 0862 LTE Related
[Link]
Support
attribute is 0.
Category M If both, the Category M Flexible Narrowband Support
Flexible feature and the LTE-NR FDD Spectrum Sharing with
FAJ 121 5590 MI Conflicting
Narrowband Category M feature are activated, the Category M
Support Flexible Narrowband Support feature cannot work.
The Shared LTE RAN and the LTE-NR FDD Spectrum
Sharing with Category M features cannot be used
Shared LTE RAN FAJ 121 0860 LTE Conflicting
together if the eNodeB uses MORAN on single
Baseband configuration.

2.8.3 Network Impact of LTE-NR FDD Spectrum Sharing with Category M

Capacity and Performance

The LTE-NR FDD Spectrum Sharing with Category M feature can affect Category M throughput in the following ways:

– Cell throughput for Category M can decrease.

– Peak rate for Category M can decrease.

The LTE-NR FDD Spectrum Sharing with Category M feature can affect LTE and NR cells in the following ways:

– Network overhead can occur in the NR cell because of the larger RBG size compared to LTE and subcarrier misalignment from the center
frequency.

– Network overhead for LTE and NR slightly increases due to Category M broadcast messages.

– Peak rate can decrease in the ESS cell pair.

– Recurring and traffic-dependent transmissions can be delayed, because Category M traffic is prioritized.

The following LTE and ESS KPIs might decrease at heavy load because Category M PRBs and Category M traffic are included in the KPI
calculation:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

– Average UL PRB Utilization in ESS

 – Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

Interfaces
No impact.

Other Network Elements

No impact.

2.8.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M

Category M can be introduced into an ESS configuration as part of the regular ESS deployment, or it can be introduced into an existing ESS
configuration. After the LTE-NR FDD Spectrum Sharing with Category M feature is enabled, it can be optimized to reduce the impact of
Category M on LTE and NR.

Activation The LTE-NR FDD Spectrum Sharing with Category M feature requires feature activation, performed during the ESS
deployment activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

The LTE-NR FDD Spectrum Sharing with Category M feature is activated by setting the [Link]
attribute to ACTIVATED in the FeatureState=CXC4012537 MO instance.
The LTE-NR FDD Spectrum Sharing with Category M feature is deactivated by setting the
[Link] attribute to DEACTIVATED in the FeatureState=CXC4012537 MO instance.

Initial After the feature license is activated, the feature can be enabled through different procedures. Based on the initial network
Configuration environment, see the following information:

– Activate ESS Configuration in a Category M Access-Enabled Cell

– Activate Category M Access in an ESS Configuration

The LTE and NR cells must remain locked for the entire procedure, from before the feature is enabled until all the MO
attributes are set to the recommended values.

Optimization After initial configuration, the effect of Category M on LTE and NR can be reduced with the following optimization options:

– Reduce the Dynamic Effect of Category M

– Reduce the Static Effect of Category M

– Optimize Category M Resource Share

– Finetune Category M Resource Share

– Finetune Category M Uplink Resource Share

– Finetune the Resource Share of Category M RRC Establishments

Alarms The feature can raise an alarm in the following cases:

– The feature license is not activated.

– A prerequisite feature license is not activated.

– If the [Link] attribute is set to false while the feature is enabled, the ESS
Inconsistent Configuration alarm is raised.
The alarm is raised, because Category M must use common PRACH with LTE in an ESS configuration.

– If the total number of invalid subframes configured in the system is too high, the Inconsitent Configuration
alarm is raised.
For ESS with NR standalone deployment, the feature requires invalid subframes in the time domain. Invalid
subframes are configured for this feature through the [Link]
attribute. The alarm is not raised when the attribute value is set to other values.
However, the system uses invalid subframes from different sources, not only from this attribute. The invalid
subframes from different sources are added together. The alarm is only raised if the total number of invalid
subframes is too high.
 For the ESS alarm information, see Detect and Resolve.
KPIs The impact of Category M on LTE and NR at heavy load can be observed through the following KPIs:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

– Average UL PRB Utilization in ESS

– Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

The dynamic effect of Category M on LTE and NR throughput can be observed through the Average UL MAC UE
Throughput KPI.
The following counters help to observe Category M traffic and decide when to limit Category M PRB use:

– EUtranCellFDD.pmCellCatmEssShareDlSrb0Max

– [Link]

– [Link]

The following counters help to observe how Category M traffic is affected by LTE and NR traffic:

– EUtranCellFDD.pmMacTimeDlCatmEssShareSrb0Enforced

– [Link]

– [Link]

The [Link] PM counter helps to observe when LTE and NR are fully
utilized.
The following PM counters introduced by the Category M Access feature can be used to observe the number of PRBs used
by Category M:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

These PM counters help to observe how Category M PRB use affects ESS.
For the ESS-related KPI and counter information, see Manage Performance.

Related concepts
LTE-NR FDD Spectrum Sharing with Category M Overview
Category M Resource Sharing Guidelines
Related tasks
Activate Category M Access in an ESS Configuration
 Activate ESS Configuration in a Category M Access-Enabled Cell
Reduce the Dynamic Effect of Category M
Reduce the Static Effect of Category M
Optimize Category M Resource Share
Finetune Category M Resource Share
Finetune Category M Uplink Resource Share
Finetune the Resource Share of Category M RRC Establishments

[Link] Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

Table 26 Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

MO Attribute Value
[Link] true
[Link] 44
The opposite side of the
[Link] attribute, as
[Link] follows:
[Link] = 1-
[Link]
The opposite side of the
[Link] attribute, as
EUtranCellFDD.msg3FrequencyAllocationBr follows:
EUtranCellFDD.msg3FrequencyAllocationBr = 1-
[Link]
For ESS with NR standalone configuration:
1
[Link]
For ESS with EN-DC configuration:
0
NORMAL for cells if deep indoor, and large coverage is not needed for
EUtranCellFDD.siSib1RepetitionBr
Category M.
High priority:
1000
Moderate priority:
[Link]
30
Low priority:
1
High priority:
1000
Moderate priority:
[Link]
60
Low priority:
2
High priority:
1000
Moderate priority:
EUtranCellFDD.dlCatmEssShareSrb0
10
Low priority:
1

2.8.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Category M
Changes that affect the LTE-NR FDD Spectrum Sharing with Category M feature and the impact that the feature has on the network.

Table 27 Feature Change History

Enhancement Name Description

22.Q1: Enhanced Resource Control for LTE-NR
Resource sharing optimization options are introduced for the feature.
FDD Spectrum Sharing with Category M

2.9 FAJ 121 5306: LTE-NR FDD Spectrum Sharing with NB-IoT
2.9.1 LTE-NR FDD Spectrum Sharing with NB-IoT Overview
This feature introduces support for the coexistence of one LTE-NR ESS cell pair with one NB-IoT cell that is deployed in the guard band of
the host LTE cell.

Feature Identity: FAJ 121 5306

Value Package Name: LTE-NR FDD ESS Multi-RAT Coexistence
Value Package Identity: FAJ 801 4018
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license is required for each node.

This feature enables the deployment of the following cells in the same spectrum:

– One LTE cell

– One NB-IoT cell

– One NR cell

Either NB-IoT can be introduced into an existing LTE-NR ESS configuration, or NR can be introduced into an existing LTE network that is
deployed with NB-IoT. On the same node, both LTE cells and LTE cells in ESS cell pairs can serve as the hosts for NB-IoT cells. The
[Link] attribute must be set to true in each NR cell, for each NB-IoT cell that shares spectrum with the ESS cell
pair.

The NB-IoT cell can use either one anchor carrier, or both one anchor and one non-anchor carrier configuration. The anchor and non-anchor
carriers can be deployed on both sides, or on the same side of an ESS carrier. As a result, NB-IoT PRBs can be deployed flexibly to avoid
collision with blanked PRBs configured with the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature. If the LTE-NR FDD
Spectrum Sharing with Flexible Channel Bandwidth feature supports only EN-DC mode, the configuration of NB-IoT coexistence with blanked
PRBs can be supported only in EN-DC mode. In other cases, the NB-IoT coexistence with blanked PRBs can be supported in EN-DC mode or
NR standalone mode. The NB-IoT PRBs must be within the valid PRB range and must not collide with blanked PRBs.

Compared to an NB-IoT cell deployed with an LTE cell, this feature extends the available PRB range where a guard band NB-IoT cell can be
deployed. For this reason, the supported range of the following attributes is extended:

– [Link]

– [Link]

– [Link]

– [Link]

If a guard band NB-IoT cell is deployed, it is in-band for the NR cell. This means that the NB-IoT cell occupies a part of the frequency range of
the NR cell. To enable the coexistence of NB-IoT and NR in the same spectrum, NR resource blocks are blocked if they are overlapped by NB-
IoT PRBs.
 -3 -2 -1 0 1 98 99 100 101 102

0 1 2 3 4 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003065A

Figure 15 Overlapping NB-IoT and NR Resource Blocks

The subcarriers of some NB-IoT PRBs can spill over at the end of the outmost NR resource block for each bandwidth. This means that one or
more subcarriers of the guard band NB-IoT PRB can exceed the PRB subcarrier range of the ESS NR cell. The spillover value represents how
many subcarriers the radio can handle that exceeds the outmost subcarrier of NR.

For 15 MHz and 20 MHz bandwidths, if subcarrier spillover is supported, the number of NR resource blocks that need to be reserved for NB-IoT
is reduced. This results in more NR resource blocks that can be used for NR, which can improve the downlink cell throughput.

The gNodeB considers the following factors when it allocates cell radio resources:

– Blanked PRBs if the FAJ 121 5228: LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature is activated

– For NR standalone, the position of CORESET#0

– NB-IoT PRBs

Note: The position of NB-IoT PRBs must be set in a way that they do not collide with the position of CORESET#0 or with blanked
PRBs.
For more information about CORESET#0, see Manage Radio Network.
For more information about PRB blanking, see LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth.

Related concepts
Configure LTE-NR FDD Spectrum Sharing with NB-IoT
Related Information
NB-IoT Guideline

2.9.2 Dependencies of LTE-NR FDD Spectrum Sharing with NB-IoT

 The feature has different prerequisites based on whether it is enabled in an EN-DC or an NR standalone deployment. The feature is related
to other features that affect the scheduling of resource blocks.

Table 28 Feature Dependencies

Feature Name Feature Identity Standard Relationship Description

The LTE-NR FDD Spectrum Sharing Enabler
FAJ 121 5147: LTE-NR
feature must be operable before the LTE-NR
FDD Spectrum Sharing FAJ 121 5147 NR Prerequisite
FDD Spectrum Sharing with NB-IoT feature
Enabler
can be used.
The NB-IoT Access feature must be operable
NB-IoT Access FAJ 121 4657 MI Prerequisite before the LTE-NR FDD Spectrum Sharing with
NB-IoT feature can be used.
The LTE-NR FDD Spectrum Sharing with NR
FAJ 121 5257: LTE-NR
Standalone feature must be operable before
FDD Spectrum Sharing FAJ 121 5257 NR Related
the LTE-NR FDD Spectrum Sharing with NB-
with NR Standalone
IoT feature can be used with NR standalone.
The NB-IoT Non-Anchor Carrier Support
NB-IoT Non-Anchor feature must be operable before the LTE-NR
FAJ 121 4893 MI Related
Carrier Support FDD Spectrum Sharing with NB-IoT feature
can be used with a non-anchor carrier.
If the LTE-NR Spectrum Sharing with Flexible
FAJ 121 5228: LTE-NR
Channel Bandwidth feature is activated, the
FDD Spectrum Sharing
FAJ 121 5228 NR Related position of NB-IoT resource blocks must be set
with Flexible Channel
in a way that they do not collide with the
Bandwidth
position of blanked PRBs.
If the PUCCH Overdimensioning feature and
the LTE-NR FDD Spectrum Sharing with NB-
PUCCH
FAJ 121 0883 LTE Related IoT feature are active at the same time, the
Overdimensioning
[Link]
attribute must be set to 0.
If the Shared LTE RAN feature is activated, NB-
IoT UEs can connect to a selected frequency in
a shared LTE RAN environment.
Shared LTE RAN FAJ 121 0860 LTE Related
The NB-IoT Access feature is not supported for
eNodeBs configured with the MORAN on single
Baseband configuration.

Limitations
Baseband units and radios that support NB-IoT are required for this feature.
Depending on the ARFCN of the NR cell and radio performance, guard band NB-IoT cannot be supported for NR standalone 10 MHz in the
following cases:

– The first resource block of CORESET#0 is on the NR resource block #0.

– The last resource block of CORESET#0 is on the NR resource block #51.

Network Requirements
No specific network requirements.

2.9.3 Network Impact of LTE-NR FDD Spectrum Sharing with NB-IoT

If the load is heavy in the ESS cell pair, the feature has a negative effect on throughput and PRB use.

Capacity and Performance

If the feature is activated, NR throughput decreases, because NB-IoT and NR use the same spectrum. The following counters are decreased if
NB-IoT is deployed:

– [Link]

– [Link]

– [Link]

Throughput and PRB use decrease in the downlink, and slightly decrease in the uplink if the following conditions apply:
 – An NB-IoT cell is configured.

– Traffic load in the LTE-NR ESS cell pair is heavy.

– Up to two NB-IoT PRBs can be allocated to uplink or downlink respectively.

The downlink cell throughput can improve by supporting non-zero spillover, because more NR PRBs can be used for NR.
If the value of the [Link] attribute is greater than 3, it might have a negative impact on radio performance and uplink
cell throughput.
Decreased throughput and PRB use can be observed with the following KPIs:
Table 29 Affected KPIs

Affected KPI Description of Change in Heavy Load

If an NB-IoT cell is deployed in the same spectrum as an NR cell, the
Normalized Average DL MAC Cell Throughput in ESS number of resource blocks available to NR decreases. As a result, NR
throughput is decreased.
If an NB-IoT cell is deployed in the same spectrum as an NR cell, the
Normalized Average UL MAC Cell Throughput in ESS number of resource blocks available to NR decreases. As a result, NR
throughput is decreased.
These KPIs are calculated as a ratio of schedulable PRBs and
Average DL PRB Utilization in ESS (based on the
available PRBs. NB-IoT uses some of the schedulable and available
[Link] PM counter)
PRBs and because of this, the value of these KPIs decreases.
These KPIs are calculated as a ratio of schedulable PRBs and
Average UL PRB Utilization in ESS (based on the
available PRBs. NB-IoT uses some of the schedulable and available
[Link] PM counter)
PRBs and because of this, the value of these KPIs decreases.

Interfaces
No impact.

Other Network Elements

No impact.

2.9.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with NB-IoT

The feature depends on other features related to ESS and NB-IoT access, and the optimization of resource blocks among NB-IoT and NR.

Activation The LTE-NR FDD Spectrum Sharing with NB-IoT feature requires feature activation, performed during the ESS deployment
activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

In addition, the following features related to NB-IoT must be activated before the LTE-NR FDD Spectrum Sharing with NB-
IoT feature can be activated:

– NB-IoT Access

– NB-IoT Non-Anchor Carrier Support

The NB-IoT Non-Anchor Carrier Support feature is only required if non-anchor carriers are used.

The LTE-NR FDD Spectrum Sharing with NB-IoT feature is activated by setting the [Link]
attribute to ACTIVATED in the FeatureState=CXC4012540 MO instance.
The LTE-NR FDD Spectrum Sharing with NB-IoT feature is deactivated by setting the [Link]
attribute to DEACTIVATED in the FeatureState=CXC4012540 MO instance.

Initial The [Link] attribute is used to enable or disable the LTE-NR FDD Spectrum Sharing with NB-
Configuration IoT feature manually in each NR cell.
Optimization The LTE-NR FDD Spectrum Sharing with NB-IoT feature must be configured in a way that NB-IoT PRBs do not interfere
with NR resource blocks and blanked PRBs. If the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature
supports only EN-DC mode, the configuration of NB-IoT coexistence with blanked PRBs can be supported only in EN-DC
mode. In other cases, the NB-IoT coexistence with blanked PRBs can be supported in EN-DC mode or NR standalone
mode. If no PRBs are available or an invalid combination of PRBs are used, the ESS Inconsistent Configuration
alarm is raised.
In an anchor and non-anchor configuration, the following options are supported for uplink carriers:

– The uplink carriers must be placed next to each other on one side of the bandwidth.
 – The uplink carriers must be placed on both sides of the bandwidth symmetrically.
The feature supports the following PRB indexes:
Table 30 Supported NB-IoT PRB Indexes

Related Attribute Bandwidth Supported PRB Indexes

10 MHz -1, 50, 255
[Link]
(1) 15 MHz -1, 75, 255
20 MHz -2, -1, 100, 101, 255
10 MHz -1, 50, 255
[Link] 15 MHz -2(2), -1, 75, 76(2), 255
20 MHz -3(2), -2, -1, 100, 101, 102(2), 255
10 MHz -1, 50
[Link] 15 MHz -2(3), -1, 75, 76(4)
20 MHz -3(5), -2, -1, 100, 101, 102(6)
10 MHz -1, 50
[Link] 15 MHz -2(2), -1, 75, 76(2)
20 MHz -3(2),-2,-1, 100, 101, 102(2)
(1) When downlink PRB indexes are configured, it is recommended to place the anchor PRBs nearer to the center of the bandwidth than non-anchor
PRBs.
(2) The value of the [Link] attribute can be up to 3 for this PRB. This PRB index can be configured even if the value of the
[Link] attribute is 0.
(3) -2 can only be configured when the value of the [Link] attribute is at least 3.
(4) 76 can only be configured when the value of the [Link] attribute is at least 4.
(5) -3 can only be configured when the value of the [Link] attribute is at least 1.
(6) 102 can only be configured when the value of the [Link] attribute is at least 2.

The attributes listed in Table 31 affect radio resource allocation. If these attributes are set to a value that is not supported
by the LTE-NR FDD Spectrum Sharing with NB-IoT feature, the ESS Inconsistent Configuration alarm is raised.
Table 31 ESS Parameter Checklist for the LTE-NR FDD Spectrum Sharing with NB-IoT Feature

MO Attribute Valid Value

[Link] 0
The PRBs used by the LTE-NR FDD Spectrum Sharing with
[Link] NB-IoT feature must be set in a way that they do not
interfere with blanked PRBs.
The PRBs used by the LTE-NR FDD Spectrum Sharing with
[Link] NB-IoT feature must be set in a way that they do not
interfere with blanked PRBs.
The PRBs used by the LTE-NR FDD Spectrum Sharing with
[Link] NB-IoT feature must be set in a way that they do not
interfere with blanked PRBs.
The PRBs used by the LTE-NR FDD Spectrum Sharing with
[Link] NB-IoT feature must be set in a way that they do not
interfere with blanked PRBs.
[Link] This feature supports specific PRB indexes.
[Link] This feature supports specific PRB indexes.
[Link] This feature supports specific PRB indexes.
[Link] This feature supports specific PRB indexes.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.
For NR KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with NB-IoT feature,
see Network Impact of LTE-NR FDD Spectrum Sharing with NB-IoT.

Related tasks
Activate NB-IoT Access in an ESS Configuration
Activate ESS Configuration in an LTE Cell that Hosts an NB-IoT Cell
 Related reference
NB-IoT PRB Configuration Examples
NB-IoT PRB Configuration Examples with Blanked PRBs

2.9.5 Feature Change History LTE-NR FDD Spectrum Sharing with NB-IoT
Changes that affect the LTE-NR FDD Spectrum Sharing with NB-IoT feature and the impact that the feature has on the network.

Table 32 Feature Change History

Enhancement Name Description

Non-Zero Spillover for LTE-NR FDD Spectrum
Non-zero spillover for NB-IoT PRBs is supported.
Sharing with NB-IoT

2.10 FAJ 121 5382: LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation

2.10.1 LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation Overview
The feature introduces two independent outer loops for NR interference slots and LTE-NR mixed interference slots.

Feature Identity: FAJ 121 5382

Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity: FAJ 801 4020
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license is required for each node.

The feature introduces two outer loops for NR PDSCH link adaptation:

– One loop for slots affected by NR interference

– Another loop for slots impacted by mixed interference of LTE and NR

The feature uses HARQ feedback received for PDSCH transmission to update the outer loops, on one loop with NR interference, on the other
loop with mixed interference. Link adaptation for PDSCH transmission is based on the HARQ feedback received on the individual loops.

The two loops can converge into a more stable outer loop adjustment value than what only one loop provides.

The feature provides the following benefits:

– More accurate link adaptation

– More responsive MCS to interference

– Increased NR data throughput

The [Link] attribute is used to enable or disable dual outer loop link adaptation. The attribute
configuration only takes effect if the LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation feature is operable and the NR cell
is part of an ESS cell pair. By setting the [Link] attribute to false, the system returns to single outer loop
link adaptation.

The feature can include NR PDSCH outer loop adjustment in the PDCCH SINR estimation. This results in the following benefits:

– Enhanced PDCCH performance as the PDCCH SINR estimation can become more accurate.

– Increased robustness of NR PDCCH when LTE interference is strong.

– NR PDCCH resource use can be lowered, through tuning the [Link] attribute.

Note: Tuning the [Link] attribute to reduce PDCCH resource use can have an impact on PDCCH
performance, even when the [Link] attribute is set to the default value of No_OLA. Setting the
[Link] attribute to PDSCH_OLA mitigates the negative impact.

2.10.2 Dependencies of LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation
 The feature requires the LTE-NR FDD Spectrum Sharing Enabler feature to be activated. In addition, if activated, it has impact on carrier
aggregation features.

Table 33 Feature Dependencies

Feature Name Feature Identity Standard Relationship Description
When dual outer loop is configured through the
[Link]
attribute, the gNodeB uses the following separate
PDSCH outer loop adjustments:

– For NR slots that correspond to LTE

MBSFN subframes, the MBSFN outer loop
is used to adjust PDSCH SINR.

FAJ 121 5147: LTE-NR FDD – For NR slots that correspond to LTE non-
FAJ 121 5147 NR Prerequisite
Spectrum Sharing Enabler MBSFN subframes, the non-MBSFN outer
loop is used to adjust the PDSCH SINR.
If PDCCH link adaptation adjustment is configured
with the [Link]
attribute to use PDSCH outer loop adjustment, the
individual adjustments are applied to PDCCH SINR
the same way.
If dual outer loop is configured on the SCells
including external SCells, the same adjustments
are made on the SCell.
The LTE-NR FDD Spectrum Sharing with NR
Standalone feature must be activated if the LTE-
NR FDD Spectrum Sharing with Dual Outer Loop
Link Adaptation feature is used in ESS cells where
NR is configured for NR standalone.
With an active PDCCH Link Adaptation Adjustment
in ESS Cells feature, when dual outer loop is
configured, non-MBSFN open loop adjustment is
used in non-MBSFN subframes and MBSFN open
FAJ 121 5257: LTE-NR FDD
loop adjustment is used in MBSFN subframes to be
Spectrum Sharing with NR FAJ 121 5257 NR Related
included in the PDCCH SINR estimation.
Standalone
When PDCCH Link adaptation adjustment is
possible with ESS external SCells with support for
dual outer loops, the OLA value included in PDCCH
SINR estimation can show two, one or no outer
loops. This value depends on the configuration of
the [Link]
attribute, configured for both the PCell and the
external SCell, and the
[Link] attributes.
Feature gain degradation is expected when
different MBSFN configurations are applied in a
cell cluster. Using the same MBSFN configuration is
recommended in all cells of the same cluster
(serving cells and neighbor cells).
Link adaptation is done for the slots that are
impacted by mixed interference, which can impact
the performance, when the following conditions
apply:
FAJ 121 5406: LTE-NR FDD
Spectrum Sharing with Tunable FAJ 121 5406 NR Related – The
NR Subframes [Link]
is set to NSA_SA_55_PERCENT.

– Dual outer loop link adaptation is

performed in the PCell.

– Single outer loop link adaptation is

performed in the ESCell.

Advanced RAN Coordination FAJ 121 5271 NR Related Dual outer loop link adaptation in inter-node
carrier aggregation is supported only if the
following conditions apply:

– The LTE-NR FDD Spectrum Sharing with

Dual Outer Loop Link Adaptation feature is
activated on the node hosting the ESCell.

– Dual outer loop link adaptation is enabled

on the node hosting the ESCell
If the PCell is not capable of dual outer loop link
adaptation, the PCell can still be used in inter-
 Feature Name Feature Identity Standard Relationship Description
gNodeB carrier aggregation, but only single outer
loop link adaptation can be applied.
The information to configure dual outer loops and
to apply dual outer loop adjustment in inter-node
carrier aggregation for the ESCells is transferred
between the PCell and the ESCells. The ESCell
configuration is transferred to the PCell. However,
when the configuration changes on the ESCell, the
ESCell must be locked and unlocked to synchronize
the configuration between the PCell and the
ESCell. Dual outer loop adjustment is calculated in
the PCell and transferred to the ESCell.
If FDD-FDD carrier aggregation is used, only the
NR DL Carrier Aggregation FAJ 121 5201 NR Related outer loop adjustment from the mixed interference
loop is considered for PCell and SCell buffer split.
If the NR Slot-Specific Downlink Link Adaptation
feature is activated, SINR backoff and the
disabling of outer-loop adjustment target the NR
inter-cell interference, not the LTE CRS
NR Slot-Specific Downlink Link interference.
FAJ 121 5475 NR Related
Adaptation Too many slots must not be configured to disable
outer-loop adjustment. For example, all MBSFN
slots must not be configured to disable outer-loop
adjustment, as MBSFN outer-loop stops working
as a result of such configuration.
With the Link Adaptation for Low Target BLER for
Link Adaptation for Low Target
Public RAN feature activated, down step size
BLER for Dedicated RAN (FAJ 121 FAJ 121 5667 NR Related
configuration for achieving the low target BLER is
5667)
possible for dual outer loop link adaptation.
With the Link Adaptation for Low Target BLER for
Link Adaptation for Low Target
Dedicated RAN feature activated, down step size
BLER for Public RAN (FAJ 121 FAJ 121 5666 NR Related
configuration for achieving the low target BLER is
5666)
possible for dual outer loop link adaptation.

2.10.3 Network Impact of LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation
Data throughput gain and BLER decrease can be achieved with the feature.

Capacity and Performance

The feature can increase NR data throughput, and it can decrease NR BLER if the BLER is higher than the target value. The following NR KPIs
and PIs can be observed to monitor the throughput gain and the BLER decrease:

– Normalized Average DL MAC Cell Throughput in ESS

– DL HARQ Rate Total

As BLER converges more accurately to the target, the DL HARQ Rate Total PI is expected to increase compared to legacy single loop in ESS.

Interfaces
No impact.

Other Network Elements

No impact.

Related reference
ESS KPIs

2.10.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation
Configuration management, fault management, and performance management aspects of the LTE-NR FDD Spectrum Sharing with Dual
Outer Loop Link Adaptation feature.

Activation The LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation feature requires feature activation, performed
during the ESS deployment activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

 The LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation feature is activated by setting the
[Link] attribute to ACTIVATED in the FeatureState=CXC4012583 MO instance.
To deactivate the LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation feature, the following steps need
to be taken:

1. The dual outer loop link adaptation must be disabled in all the cells of the gNodeB by setting the
[Link] attribute to false in all cell MO instances.

2. The attribute [Link] must be set to DEACTIVATED in the FeatureState=CXC4012583

MO instance.

Initial The [Link] attribute is used to manually enable or disable dual outer loop link
Configuration adaptation in individual cells. The attribute configuration only takes effect if the LTE-NR FDD Spectrum Sharing with Dual
Outer Loop Link Adaptation feature is activated.

Optimization For the recommended attribute values and the configuration, see Configuration of Outer Loop Link Adaptation.

KPIs For the ESS-related KPI and counter information, see Manage Performance.
For NR KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with Dual Outer
Loop Link Adaptation feature, see Network Impact of LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link
Adaptation.

Alarms When the configuration of the ESCell changes and the changes are not synchronized between the PCell and the ESCell,
the MO Configuration Pending Action alarm is raised to notify the operator about the inconsistency in the
configuration.
When a capability mismatch exists between the nodes hosting the PCell and the external SCell, the Inter Node
Carrier Aggregation Service Degraded alarm is raised. For more information, see Detect and Resolve.

Related concepts
Configuration of Outer Loop Link Adaptation

2.10.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation
Changes that affect the LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation feature and the impact that the feature has
on the network.

Table 34 Feature Change History

Enhancement Name Description

The feature enhancement introduces the support of dual outer loops
Planned: LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link
in inter-node carrier aggregation used in ESS. As a result, the NR
Adaptation on External SCells
downlink data throughput can increase.

2.11 FAJ 121 5378: LTE-NR FDD Spectrum Sharing with Rate Matching around LTE
Synchronization Signal and PBCH

2.11.1 LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH
Overview
The purpose of this feature is to increase NR downlink throughput by applying rate matching to the NR PDSCH around the LTE
synchronization signals and the LTE PBCH.

Feature Identity: FAJ 121 5378

Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity: FAJ 801 4020
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license is required for each node.

Rate matching around the LTE synchronization signals and the LTE PBCH is applied for capable UEs when the following options apply:

– The feature is activated on the node.

– The ESS cell pair is unlocked.

 The feature provides the following benefits:

– The NR downlink data throughput can increase.

– Previously unavailable NR resource elements can be used.

The number of resource elements that carry NR downlink data can increase. The additional resource elements used by NR are unavailable for
LTE.

The feature only provides benefits to UEs that support the semi-static rate matching capability. Non-capable UEs are scheduled without NR
downlink data around the LTE synchronization signals and the LTE PBCH.

When rate matching around the LTE synchronization signals and the LTE PBCH is applied, unused resources become available for NR downlink
data. However, some of the resources remain unused for the PDSCH due to misalignment of the LTE and NR resource blocks in the upper half
spectrum.

No Rate Matching Rate Matching

around the LTE Synchronization Signals around the LTE Synchronization Signals
and the LTE PBCH and the LTE PBCH
Cell Bandwidth

Cell Bandwidth

1 Slot 1 Slot

Reserved for LTE and NR control channels

PDSCH

DMRS

LTE Sync Signal and LTE PBCH

LTE CRS (4-port)

Unused resources

L0003135A

Figure 16 Downlink Data Transmission with and without Rate Matching around the LTE Synchronization Signals and the LTE PBCH

2.11.2 Dependencies of LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal
and PBCH
The feature is related to NR features used for different cell configurations. The benefits of the feature are only available for UEs with semi-
static rate matching capability.

Table 35 Feature Dependencies

Feature Name Feature Identity Standard Relationship Description

The LTE-NR FDD Spectrum
Sharing Enabler feature
must be activated for the
FAJ 121 5147: LTE-NR LTE-NR FDD Spectrum
FDD Spectrum Sharing FAJ 121 5147 NR Prerequisite Sharing with Rate
Enabler Matching around LTE
Synchronization Signal and
PBCH feature to be
operational.
FAJ 121 5257: LTE-NR FAJ 121 5257 NR Related The LTE-NR FDD Spectrum
FDD Spectrum Sharing Sharing with NR
with NR Standalone Standalone feature must
 Feature Name Feature Identity Standard Relationship Description
be activated if the LTE-NR
FDD Spectrum Sharing
with Rate Matching around
LTE Synchronization Signal
and PBCH feature is used
in NR cells configured for
NR standalone in the ESS
cell pair.
A semi-static rate matching
activation indication is
forwarded to each UE.
When configured, the
Advanced RAN
FAJ 121 5271 NR Related external SCell can perform
Coordination
rate matching around the
LTE synchronization signal
and the LTE PBCH for
capable UEs.

Limitations
No known limitations.

Network Requirements
The feature requires that the UE supports the semi-static rate matching capability.

2.11.3 Network Impact of LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization
Signal and PBCH
Data throughput gain can be achieved with the feature. Impact on the network capacity and performance can be monitored by using KPIs
and PM counters.

Capacity and Performance

When the feature is enabled, the number of resource elements available for NR downlink data increases by 2–4%. The amount of this increase
depends on cell bandwidth and configuration. However, the feature gains can be lower, in terms of used resource elements and throughput.
Especially, the feature gains can be lower when one or both of the following conditions apply:

– The NR load is low.

– The NR UEs have mainly short data bursts.

The increase of resource elements that carry NR downlink data can be monitored with the Average DL PRB Utilization in ESS KPI. The
additional resource elements used by NR are unavailable for LTE.
The throughput gain can be monitored with the Normalized Average DL MAC Cell Throughput considering traffic NR KPI.
The following NR KPIs can increase:

– Average DL MAC Cell Throughput - fixed time normalized

– Average DL MAC DRB Throughput

– DL MAC DRB Throughput per QoS

– Normalized Average DL MAC Cell Throughput considering traffic

– Normalized DL MAC Cell Throughput considering actual PDSCH slot only

Note: The following NR KPIs can increase in the LTE to EN-DC–ESS migration scenario:

– Differentiated Average DL PDCP UE DRB Throughput Captured in eNodeB

– Differentiated Average DL PDCP UE Throughput Captured in eNodeB

– Differentiated Average DL PDCP UE Throughput for LTE Leg using Carrier Aggregation Captured in eNodeB

The following NR KPIs can decrease:

– Average DL MAC DRB Latency per QoS covering DRX In-sync

– Average DL MAC DRB Latency per QoS covering non-DRX In-sync

 – Average Overall DL Latency
The following LTE KPIs can increase:

– Average DL UE Latency

– Average DL UE PDCP DRB Latency per QCI

– DL Scheduled Entities per TTI

The following LTE KPIs can decrease:

– Average DL MAC Cell Throughput

– Average DL PDCP Cell Throughput

– Average DL PDCP UE DRB Throughput per QCI

– Average DL PDCP UE Throughput

– Average DL PDCP UE Throughput for Carrier Aggregation

– DL PDCP UE Throughput Distribution

– Filtered MBB UE DL PDCP Throughput

– Total DL PDCP UE Throughput

The performance of the feature can be observed through the following PM counters:

– [Link]

– [Link]

– [Link]

Note: The [Link] PM counter can be used to observe the performance of the feature in the LTE to EN-DC–
ESS migration scenario.
When the LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH on External SCells feature is
activated, the following KPIs can be used to monitor the improved throughput gain on external SCells:

– Average DL MAC Cell Throughput - Fixed Time Normalized

– Normalized Average DL MAC Cell Throughput considering traffic

– Normalized DL MAC Cell Throughput considering actual PDSCH slot only

– Average DL MAC DRB Throughput

– DL MAC DRB Throughput per QoS

Interfaces
No impact.

Other Network Elements

No impact.
Related reference
ESS KPIs

2.11.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal
and PBCH
Configuration management, fault management, and performance management aspects of the LTE-NR FDD Spectrum Sharing with Rate
Matching around LTE Synchronization Signal and PBCH feature.

Activation The LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH feature requires
feature activation, performed during the ESS deployment activities. Depending on the ESS migration scenario, see the
following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

 – Activate Features in the Migration Scenario from LTE to SA–ESS
The LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH feature is
activated by setting the [Link] attribute to ACTIVATED in the FeatureState=CXC4012581
MO instance.
The LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH feature is
deactivated by setting the [Link] attribute to DEACTIVATED in the
FeatureState=CXC4012581 MO instance.

Initial The LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH feature cannot be
Configuration enabled or disabled manually. If the feature is activated on the node, rate matching around the LTE synchronization
signals and the LTE PBCH is applied for capable UEs when the ESS cell pair is unlocked.

Alarms For the ESS alarm information, see Detect and Resolve.

KPIs For the ESS-related KPI and counter information, see Manage Performance.
For KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with Rate Matching
around LTE Synchronization Signal and PBCH feature, see Network Impact of LTE-NR FDD Spectrum Sharing with Rate
Matching around LTE Synchronization Signal and PBCH.

2.11.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Rate Matching around LTE
Synchronization Signal and PBCH
Changes that affect the LTE-NR FDD Spectrum Sharing with Rate Matching around LTE Synchronization Signal and PBCH feature and the
impact that the feature has on the network.

Table 36 Feature Change History

Enhancement Name Description

This feature enhancement can increase NR downlink throughput by
22.Q2: LTE-NR FDD Spectrum Sharing with Rate Matching around
rate matching the NR PDSCH around the LTE synchronization signals
LTE Synchronization Signal and PBCH on External SCells
and the LTE PBCH on external SCells.

2.12 FAJ 121 5406: LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

2.12.1 LTE-NR FDD Spectrum Sharing with Tunable NR Subframes Overview

This feature can increase the NR downlink throughput by enabling the configuration of additional MBSFN subframes available for NR
downlink data.

Feature Identity: FAJ 121 5406

Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity: FAJ 801 4020
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license is required for each node.

By activating this feature on the gNodeB, additional MBSFN subframes can be configured as dedicated resources for NR traffic. In addition,
LTE CRS interference from neighbor cells can be reduced.

The feature provides increased NR downlink throughput and increased NR spectral efficiency when most of the NR traffic is sent in MBSFN
subframes.

The [Link] attribute is deprecated and replaced by the [Link]

attribute. The feature introduces support for the following configuration options regarding the percentage of the MBSFN subframes in a 40-
subframe pattern:

– 25%

– 35%

– 45%

– 55%
 The [Link] attribute is introduced to provide information about the exact position of the configured
MBSFN subframes.
Related concepts
MBSFN Subframe Configuration

2.12.2 Dependencies of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

The feature has dependencies with other features affected by MBSFN subframe configuration.

Table 37 Feature Dependencies

Feature Name Feature Identity Standard Relationship Description

The LTE-NR FDD Spectrum Sharing Enabler feature
FAJ 121 5147: LTE-
must be activated for the LTE-NR FDD Spectrum
NR FDD Spectrum FAJ 121 5147 NR Prerequisite
Sharing with Tunable NR Subframes feature to be
Sharing Enabler
operational.
With additional MBSFN subframes configured, the LTE
cell capacity decreases for LTE load balancing. UE
Automated Cell
FAJ 121 3031 LTE Related distribution to other cells can start earlier. Therefore,
Capacity Estimation
observation of a decrease in LTE connected users is
possible with more MBSFN subframes configured.
The [Link] and
[Link] attributes are
recommended to be set to a value larger than PSF4 if
the following conditions apply:
Efficient DRX/DTX
FAJ 121 0801 LTE Related – The LTE-NR FDD Spectrum Sharing with Tunable
for Connected UE
NR Subframes feature is used.

– The [Link] attribute is

set to 18 in ESS.
The [Link] and
[Link] attributes are
recommended to be set to a value larger than PSF4 if
the following conditions apply:
Service Specific DRX FAJ 121 3011 LTE Related – The LTE-NR FDD Spectrum Sharing with Tunable
NR Subframes feature is used.

– The [Link] attribute is

set to 18 in ESS.
The LTE-NR FDD Spectrum Sharing with NR
FAJ 121 5257: LTE-
Standalone feature must be activated if the LTE-NR
NR FDD Spectrum
FAJ 121 5257 NR Related FDD Spectrum Sharing with Tunable NR Subframes
Sharing with NR
feature is used in NR cells configured for NR SA in the
Standalone
ESS cell pair.
The LTE-NR FDD Spectrum Sharing with Category M
feature cannot be used when the
[Link] attribute is
set to NSA_SA_55_PERCENT.
With the LTE-NR FDD Spectrum Sharing with Tunable
NR Subframes feature, the Category M performance
FAJ 121 5301: LTE- can decrease because of the limited Category M PDCCH
NR FDD Spectrum and Category M PDSCH. The uplink and downlink cell
FAJ 121 5301 NR Related
Sharing with peak throughput and the UE peak throughput can
Category M decrease.
When the percentage of the MBSFN subframe values is
set to 25% or higher, the
[Link]
attribute is recommended to be set to 0. A higher
MBSFN ratio also affects the evaluation of the
Category M System Information window length.
FAJ 121 5309: LTE- When the LTE-NR FDD Spectrum Sharing with Policy-
NR FDD Spectrum based Biasing feature is active, the configuration of
FAJ 121 5309 NR Related
Sharing with Policy- MBSFN subframes must be aligned with the scheduling
based Biasing policy.
 Feature Name Feature Identity Standard Relationship Description
FAJ 121 5382: LTE- Feature gain degradation is expected when different
NR FDD Spectrum MBSFN configurations are applied in a cell cluster.
Sharing with Dual FAJ 121 5382 NR Related Using the same MBSFN configuration is recommended
Outer Loop Link in all cells of the same cluster (serving cells and
Adaptation neighbor cells).
The LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
FAJ 121 5607: LTE-
feature supports the varying configuration of downlink
NR FDD Spectrum
FAJ 121 5607 NR Related MBSFN subframes. The extent of power savings can
Sharing with Micro
vary depending on the downlink MBSFN subframe
Sleep Tx
configuration.
All MBSFN subframe configurations are supported if
the [Link] attribute is
Inter-Frequency
FAJ 121 3090 LTE Related set to 11 and the
OTDOA
[Link]
attribute is set to SF1.
All MBSFN subframe configurations are supported if
the [Link] attribute is
LPPa-based OTDOA
FAJ 121 3050 LTE Related set to 11 and the
Support
[Link]
attribute is set to SF1.
All MBSFN subframe configurations are supported if
OTDOA Control the [Link] attribute is
Plane Location FAJ 121 1793 LTE Related set to 11 and the
Support [Link]
attribute is set to SF1.
All MBSFN subframe configurations are supported if
the [Link] attribute is
OTDOA PRS
FAJ 121 3086 LTE Related set to 11 and the
Management
[Link]
attribute is set to SF1.
All MBSFN subframe configurations are supported if
the [Link] attribute is
OTDOA User Plane
FAJ 121 0862 LTE Related set to 11 and the
Location Support
[Link]
attribute is set to SF1.
When the feature is activated, the PCell and the ESCell
can be expected to have different MBSFN
configurations more often.
FAJ 121 5147: LTE-
If the PCell and the external SCell have different
NR FDD Spectrum FAJ 121 5147 NR Related
MBSFN configurations, the PDCCH SINR estimation
Sharing Enabler
includes both non-MBSFN open loop adjustment, used
in non-MBSFN subframes, and MBSFN open loop
adjustment, used in MBSFN subframes.

Limitations
The [Link] attribute must not be set to TRANSMISSION_MODE_9 when additional MBSFN subframes are
configured with the feature.

Network Requirements
No specific network requirements.
Related reference
Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

2.12.3 Network Impact of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
NR downlink throughput gain can be achieved with the feature. Impact on the network capacity and performance can be observed through
using KPIs and PM counters.

Capacity and Performance

The increased number of MBSFN subframes can affect the capacity and performance in the following ways:

– The LTE downlink throughput can decrease.

 – The NR uplink throughput for a single UE can decrease because of aperiodic CSI blocking.
Note: A UE with aperiodic CSI demand skips uplink subframes that have no aperiodic CSI occasions.

– The number of supported VoLTE calls can decrease, and VoLTE-related performance can degrade.

– The LTE cell capacity can decrease for LTE load balancing, and UE distribution to other cells can start earlier. Therefore, observation of a
decrease in LTE connected users is possible with more MBSFN subframes configured.

– The downlink interference from neighboring cells can decrease for NR and increase for LTE. As NR traffic increases, the NR and LTE
downlink interference impact decreases, which might affect LTE cell estimation and impact cell selection. As a result, uplink and
downlink BLER might increase, due to UE attaching to cell with worse channel quality.
The following NR KPIs can increase:

– Average DL MAC Cell Throughput - fixed time normalized

– Average DL MAC DRB Throughput

– DL MAC DRB Throughput per QoS

– Normalized Average DL MAC Cell Throughput considering traffic

– Normalized DL MAC Cell Throughput considering actual PDSCH slot only

The following NR KPIs can increase in the LTE to EN-DC–ESS migration scenario:

– Differentiated Average DL PDCP UE DRB Throughput Captured in eNodeB

– Differentiated Average DL PDCP UE Throughput Captured in eNodeB

– Differentiated Average DL PDCP UE Throughput for LTE Leg using Carrier Aggregation Captured in eNodeB

The DL HARQ BLER NR KPI can decrease.

The following LTE KPIs can increase:

– Average DL UE Latency

– Average DL UE PDCP DRB Latency per QCI

– Average PDCCH Aggregation Level

– DL HARQ BLER %

– DL PDCCH Error Rate

The following LTE KPIs can decrease:

– Average DL MAC Cell Throughput

– Average DL PDCP Cell Throughput

– Average DL PDCP UE DRB Throughput per QCI

– Average DL PDCP UE Throughput

– Average DL PDCP UE Throughput for Carrier Aggregation

– DL PDCP UE Throughput Distribution

– Filtered MBB UE DL PDCP Throughput

– Total DL PDCP UE Throughput

– VoIP Cell Integrity

The following Category M KPIs can decrease:

– Average DL Latency per QCI for Category M1 UEs

– Average DL PDCP UE Throughput for Category M1 UEs

– Average DL UE Latency for Category M1 UEs

– Average UL PDCP Cell Throughput for Category M1 UEs

– Average UL PDCP UE Throughput for Category M1 UEs

– Cell Mobility Success Rate for Category M1 UEs

 The use of the same MBSFN configuration is recommended in all ESS cells of the same cluster (serving cells and neighbor cells). Therefore, the
[Link] attribute is recommended to be set to SAME_MBSFN_SUBFRAMES. However, with the
introduction of additional MBSFN subframes that can be configured, the [Link] attribute must be set to
DIFF_MBSFN_SUBFRAMES more often, especially when ESS and non-ESS LTE cells have frequency relations.
The feature introduces the following PM counters to provide observability on PRB utilization on NR PDSCH in MBSFN subframes:

– [Link]

– [Link]

Because of the increased number of MBSFN subframes, the coverage for Category M1 UEs can decrease. This change can be observed with the
following PM counters:

– [Link]

– [Link]

– [Link]

When most of the NR traffic is sent in MBSFN subframes, the NR spectral efficiency increases and can be calculated with the following
formula: 8 × ([Link] / [Link]).
LTE random access success rate can decrease due to fewer LTE Msg2 opportunities with more MBSFN subframes. Therefore, Msg2 can be
congested in case of high LTE random access load.

Interfaces
No impact.

Other Network Elements

No impact.
Related concepts
Optimization of MBSFN Subframe Configuration for LTE and NR Downlink PRB Utilization
Related reference
MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

2.12.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
Configuration management, fault management, and performance management aspects of the LTE-NR FDD Spectrum Sharing with
Tunable NR Subframes feature.

Activation The LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature requires feature activation, performed during the
ESS deployment activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

The activation or deactivation of the LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature can only be done
when the ESS cell pair is locked.
The LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature is activated by setting the
[Link] attribute to ACTIVATED in the FeatureState=CXC4012595 MO instance.
The LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature is deactivated by setting the
[Link] attribute to DEACTIVATED in the FeatureState=CXC4012595 MO instance.

Initial When the feature is activated on the node, the [Link] attribute can be set to a
Configuration feature-specific value in the NR cell of the ESS cell pair. However, for the configuration to take effect, the ESS cell pair
must be first locked and then unlocked. This must be done every time the setting of the attribute is changed.
The [Link] attribute is introduced to provide information about the exact
position of the configured MBSFN subframes.

Alarms If the [Link] attribute is configured with feature-specific subframe values, and the
feature license is not installed or not activated, the following alarms can be raised on the NR cell in the ESS cell pair:

– MO Configuration Requires Key Install and Feature Activation

– Configuration Requires Feature Activation

 The [Link] attribute must not be set to NSA_SA_45_PERCENT or
NSA_SA_55_PERCENT when the [Link] attribute is set to LTE_BIASED. This configuration
raises the ESS Inconsistent Configuration alarm.
For the ESS alarm information, see Detect and Resolve.
KPIs For the ESS-related KPI and counter information, see Manage Performance.
For KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with Tunable NR
Subframes feature, see Network Impact of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes.

Related concepts
Optimization of MBSFN Subframe Configuration for LTE and NR Downlink PRB Utilization
Related reference
MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
Related Information
MO Configuration Requires Key Install and Feature Activation
Configuration Requires Feature Activation

2.12.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
Changes that affect the LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature and the impact that the feature has on the
network.

Table 38 Feature Change History

Enhancement Name Description

The introduced PM counters improve the observability of NR MCS
23.Q2: Counters for NR MCS Distribution in MBSFN Subframes
distribution in MBSFN subframes.

2.13 FAJ 121 5473: LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource
Allocation

2.13.1 LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation Overview
The feature enables inter-RAT resource allocation based on the relative priorities, resource needs, and number of the LTE and NR DRBs.

Feature Identity FAJ 121 5473

Value Package Name LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity FAJ 801 4020
Node Type Baseband Radio Node
Licensing Licensed feature. One license is required for each node.

The feature provides the following benefits if the competition from higher priority traffic is minimal:

– Flexibility to favor one RAT over another dynamically based on the resource needs and relative priorities of the DRBs.

– Inter-RAT resource allocation that is proportional to the number of users in each RAT when the relative priorities and resource needs of
the DRBs in the RATs are similar.

– Inter-RAT resource allocation that is proportional to the relative priority of the DRBs in each RAT when the resource needs and the
number of users are similar.

– Number of possible inter-RAT resource allocation ratios is increased.

The resource needs are determined based on the following characteristics:

– Number of DRBs with data in buffer

– Radio conditions of the users of the DRB

– Data in buffer for each DRB

• In downlink, data in RLC buffer is used.

• In uplink, data indication from BSR at the MAC layer is used.

The feature creates a relationship between a DRB of one RAT with one or multiple DRBs of the other RAT in the following ways:

– DRBs configured with the [Link],

[Link], or the [Link]
attribute set to DEMAND_WEIGHTED_RP establish inter-RAT relationships, making them related in terms of their relative priorities.

– DRBs configured with the [Link],

[Link], or [Link]
attribute set to DEMAND_WEIGHTED_RP get absolute priority over the DRBs of the other RAT configured with the attribute set to
SCHED_POLICY.

The feature introduces configuration management for both NR and LTE to govern ESS relative resource allocation between the two RATs.

Note: The [Link] or the [Link] attribute and

the [Link] attribute must be aligned across the DRBs of LTE and NR to ensure the proper
operation of the feature.

Inter-RAT Resource Allocation

The resource distribution between the RATs is based on the resource needs and relative priorities of all qualified DRBs in each RAT, in both
uplink and downlink, with the following principles:

– Relative priority-based fairness: If an LTE and an NR DRB have the same resource need, the DRB with higher relative priority is favored
in inter-RAT resource allocation. The ratio of the allocated inter-RAT resources is determined according to the ratio of the relative
priorities.

– Resource demand-based fairness: If an LTE and an NR DRB have the same relative priority, the DRB with higher resource need is
favored in inter-RAT resource allocation. The ratio of the allocated inter-RAT resources is determined according to the ratio of the
resource needs.

– UE or DRB-based fairness: If all DRBs in both RATs have the same relative priority and resource needs, the ratio of the allocated inter-
RAT resources is determined according to the ratio of the number of DRBs of the RATs.

– The resources of a RAT are allocated in proportion to the accumulated DRB allocation of all its DRBs and relative priorities.

Figure 17 shows the distribution of the relative priority weighted demands of NR and LTE going from the maximum value to the minimum
value above the resource limit.
Weighted
Resource Demand

Weighted
Resource Demand

Legend

NR Weighted Resource Demand

LTE Weighted Resource Demand
Resource Limit
L0003517A

Figure 17 Distribution of Relative Priority Weighted Resource Demands of NR and LTE

Figure 18 shows the distribution of the allocated resources between the RATs, and how it follows the relative priority weighted demands of the
RATs shown in Figure 17.
 Allocated
Resource

Allocated
Resource
Non-
MBSFN
Limit

Legend

NR Share
LTE Share
Resource Limit
L0003528B

Figure 18 Distribution of Resource Allocation between NR and LTE

Qualified DRBs
An LTE DRB is qualified if the following conditions apply:

– It is configured with the [Link] or the

[Link] attribute set to DEMAND_WEIGHTED_RP.

– The QCI profile is not configured with the [Link] or the

[Link] attribute set to HI_PRIO_OVERRIDE.

– The QCI profile is not configured with the [Link] or the

[Link] attribute set to DELAY_BASED.

– In uplink, if the DRB belongs to an LCG with multiple DRBs, the DRB with the lowest [Link] or the
[Link] attribute value in the LCG has the
[Link] or the
[Link] attribute set to DEMAND_WEIGHTED_RP.

An NR DRB is qualified if the following conditions apply:

– It is configured with the [Link] attribute set to DEMAND_WEIGHTED_RP.

– The value of the [Link] attribute is greater than 16.

– In uplink, if the DRB belongs to an LCG with multiple DRBs, the DRB with the lowest [Link]
attribute value in the LCG has the [Link] attribute set to DEMAND_WEIGHTED_RP.

Example 3 Prioritization of Different DRBs

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation

2.13.2 Dependencies of LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation
The feature has dependencies with other features related to scheduling.

Table 40 Feature Dependencies

Feature Name Feature Standard Relationship Relationship Description

Identity Scope

FAJ 121 5147:

LTE-NR FDD The LTE-NR FDD Spectrum Sharing Enabler feature must be activated for
FAJ 121 Node-level
Spectrum NR Prerequisite the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource
5147 prerequisite
Sharing Allocation feature to be operational.
Enabler
Feature Name Feature Standard Relationship Relationship Description
Identity Scope

Relative The Relative Priority Scheduling feature must be activated for the LTE-NR
FAJ 121 Node-level
Priority LTE Prerequisite FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation
2037 prerequisite
Scheduling feature to be operational.
NR Relative The NR Relative Priority Scheduling feature must be activated for the LTE-
FAJ 121 Node-level
Priority NR Prerequisite NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation
5293 prerequisite
Scheduling feature to be operational.
FAJ 121 5257:
LTE-NR FDD The LTE-NR FDD Spectrum Sharing with NR Standalone feature must be
Spectrum FAJ 121 Cell-level activated if the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative
NR Prerequisite
Sharing with 5257 prerequisite Resource Allocation feature is used in ESS cells where NR is configured for
NR NR standalone.
Standalone
Advanced
The Advanced Differentiation for Resource Fair Scheduling feature must be
Differentiation
FAJ 121 activated if the [Link] or
for Resource LTE Related
4415 the [Link] attribute
Fair
is set to RESOURCE_FAIR.
Scheduling
If the [Link] or the
QoS-Aware FAJ 121 [Link] attribute is used
LTE Related
Scheduler 0859 for the absolute priority override of different QCIs, these QCIs have
absolute priority, and do not participate in this feature.
Minimum Rate
FAJ 121 QCIs configured with minimum bit rate are treated with higher priority
Proportional LTE Related
0920 when the minimum bit rate is not maintained.
Fair Scheduler
Delay-Based
Scheduling FAJ 121 QCIs configured for delay-based scheduling do not participate in this
LTE Related
and Grant 1789 feature.
Estimation
FAJ 121 5301: Category M traffic gets high absolute priority if LTE or NR has no resource
LTE-NR FDD congestion. If either LTE or NR has resource congestion, Category M traffic
FAJ 121
Spectrum NR Related gets low absolute priority. This depends on the configuration of the
5301
Sharing with Category M resource sharing attributes. If the attributes are not configured,
Category M Category M traffic gets absolute priority over LTE and NR.
Prioritized SR FAJ 121 This LTE feature enables QCIs to be configured with relative priority so they
LTE Related
Scheduling 4300 get a higher priority.
5QIs that are configured with a priority domain value less than 17 have
absolute priority in ESS over priority domains with a value greater than 16.
Priority-
FAJ 121 This means that configuring the
Controlled NR Related
5192 [Link] attribute does
Scheduling
not take effect for 5QIs that are configured to be in a priority domain with a
value that is smaller than 17.
FAJ 121 5406: The resolution in downlink resource allocation between LTE and NR is
LTE-NR FDD constrained by the MBSFN subframe configuration that limits the shared
Spectrum FAJ 121 subframes between LTE and NR. When the LTE-NR FDD Spectrum Sharing
NR Related
Sharing with 5406 with Tunable NR Subframes feature is used, the shared resource allocator
Tunable NR takes the configured MBSFN subframes into consideration during resource
Subframes allocation between LTE and NR.
FAJ 121 5309: 5QIs configured with the
LTE-NR FDD [Link] attribute set to
Spectrum FAJ 121 SCHED_POLICY are handled by the LTE-NR FDD Spectrum Sharing with
NR Related
Sharing with 5309 Policy-based Biasing feature. These 5QIs have a lower absolute priority
Policy-based than 5QIs associated with the DEMAND_WEIGHTED_RP value of the
Biasing [Link] attribute.
The UE wake-up time during the opportunity for DRX might get delayed for
the RAT that is not prioritized in ESS resource allocation.
Connected FAJ 121 If the DRB of one RAT has longer DRX awake setting than the DRB of the
NR Related
Mode DRX 4963 other RAT, the resource share can differ from the relative priority settings.
The RAT with longer DRX awake setting gets more opportunities to
schedule and more resource.
Efficient FAJ 121 LTE Related The UE wake-up time during the opportunity for DRX might get delayed for
DRX/DTX for 0801 the RAT that is not prioritized in ESS resource allocation.
Connected UE
 Feature Name Feature Standard Relationship Relationship Description
Identity Scope

If the DRB of one RAT has longer DRX awake setting than the DRB of the
other RAT, the resource share can differ from the relative priority settings.
The RAT with longer DRX awake setting gets more opportunities to
schedule and more resources.
NR Radio
FAJ 121 The change in relative priority changes the overall resource allocation share
Resource NR Related
5337 of NR, but not necessarily the share of the individual partition.
Partitioning
LTE-NR When the two features are used together, dual connectivity DRBs are given
FAJ 121
Downlink NR Related a higher priority for resource allocation than their resource needs if they
4912
Aggregation have data buffered at PDCP.
DRBs served in an ESS cell pair configured with one of the following
attributes set to DEMAND_WEIGHTED_RP are treated with absolute priority
over the external traffic of the other RAT:
Carrier FAJ 121
LTE Related – [Link]
Aggregation 3046
– [Link]

– [Link]
DRBs served in an ESS cell pair configured with one of the following
attributes set to DEMAND_WEIGHTED_RP are treated with absolute priority
over the external traffic of the other RAT:
NR DL Carrier FAJ 121
NR Related – [Link]
Aggregation 5201
– [Link]

– [Link]
QoS information is not transferred between Advanced RAN Coordination
partners on a DRB basis when using the NR QoS-Aware Downlink Carrier
Aggregation feature.
NR QoS- If the DRBs in the external SCell are configured with one of the following
Aware attributes set to DEMAND_WEIGHTED_RP, the local DRBs have absolute
FAJ 121 priority over the external traffic forwarded from the SpCell:
Downlink NR Related
5571
Carrier
– [Link]
Aggregation
– [Link]

– [Link]
NR Soft FAJ 121 The soft admission function can be configured in an ESS cell with the
NR Related
Admission 5832 [Link] attribute.

Limitations
No known limitations.

Network Requirements
No specific network requirements.

2.13.3 Network Impact of LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation
Throughput can be affected based on the relative priority, which can be observed through using KPIs and PM counters.

Capacity and Performance

The resource prioritization is based on DRBs instead of RATs.
The throughput can be affected on the RAT depending on the configured relative priority for QCIs and 5QIs, and the number of DRBs in each
RAT.
If the ESS cell pair operates under high resource congestion with a very high number of VoLTE and VoNR users, then increasing the value of the
[Link] attribute for voice DRBs might be beneficial for performance.
The following LTE Integrity KPIs can be used to monitor the throughput impact of the feature:

– Average DL PDCP UE Throughput

 – Average UL PDCP UE Throughput

– Average MAC UE UL Throughput

– Average DL PDCP UE DRB Throughput per QCI

– Average UL UE Throughput per LCG

– Average DL PDCP Cell Throughput

– Average UL PDCP Cell Throughput

– Average DL MAC Cell Throughput

– Average UL MAC Cell Throughput

The following NR Integrity KPIs can be used to monitor the throughput impact of the feature:

– Average DL MAC Cell Throughput - fixed time normalized

– Normalized Average DL MAC Cell Throughput considering traffic

– Average UL MAC Cell Throughput - fixed time normalized

– Normalized Average UL MAC Cell Throughput considering successful PUSCH slot only

– Average DL MAC DRB Throughput

– DL MAC DRB Throughput per QoS

– Average UL MAC UE Throughput

The following counters can be used to observe the resource distribution between the RATs in ESS:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

Interfaces
No impact.

Other Network Elements

No impact.

2.13.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation
Configuration management aspects of the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation feature.

Activation The LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation feature requires feature activation,
performed during the ESS deployment activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

The following features must be activated before activating the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative
Resource Allocation feature:

– Relative Priority Scheduling

– NR Relative Priority Scheduling

 The feature state of the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation feature can only be
changed when the ESS cell pair is locked.
The LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation feature is activated by setting the
[Link] attribute to ACTIVATED in the FeatureState=CXC4012617 MO instance.
When the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation feature is active, the following
attributes can be set to DEMAND_WEIGHTED_RP to enable relative priority-based inter-RAT resource allocation in ESS:

– [Link]

– [Link]

– [Link]

If the attributes are set to DEMAND_WEIGHTED_RP but the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative
Resource Allocation feature or any one of its prerequisite features is not activated, inter-RAT resource allocation in ESS is
performed as when they are set to SCHED_POLICY.
The LTE-NR FDD Spectrum Sharing with QoS-Aware Relative Resource Allocation feature is deactivated by setting the
[Link] attribute to DEACTIVATED in the FeatureState=CXC4012617 MO instance.
Initial The QCIs of those LTE DRBs that are configured with the [Link] or
Configuration the [Link] attribute set to DEMAND_WEIGHTED_RP are
prioritized in the resource allocation order over those that use the SCHED_POLICY setting.
The 5QIs of those NR DRBs that are configured with the [Link]
attribute set to DEMAND_WEIGHTED_RP are prioritized in the resource allocation order over those that use the
SCHED_POLICY setting.
If the [Link] attribute is set to DEMAND_WEIGHTED_RP, the
[Link] attribute uses RP_ONLY setting regardless of the actual attribute
setting.
By using the settings of the [Link] attribute, 5QIs in higher priority domains are
allocated according to their absolute priority even if the [Link]
attribute is set to DEMAND_WEIGHTED_RP for these 5QIs.
If the NR Soft Admission feature is activated in an ESS cell, the LTE-NR FDD Spectrum Sharing with QoS-Aware Relative
Resource Allocation feature can be enabled for a specific QoS flow even if the
[Link] attribute is set to a value of less than 17.

KPIs For the ESS-related KPI and counter information, see Manage Performance.
For KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with QoS-Aware
Relative Resource Allocation feature, see Network Impact of LTE-NR FDD Spectrum Sharing with QoS-Aware Relative
Resource Allocation.

2.14 FAJ 121 5474: LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols

2.14.1 LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols Overview
The feature provides means to dynamically adapt the number of symbols used for NR PDCCH in ESS as the current traffic demand requires
it in the cell.

Feature Identity: FAJ 121 5474

Value Package Name: LTE-NR FDD Ericsson Spectrum Sharing
Value Package Identity: FAJ 801 4012
Node Type: Baseband Radio Node
Licensing: Non-license-controlled feature. No license is required.

With increasing NR traffic demand in ESS cells, more resources need to be allocated for the NR PDCCH to prevent the formation of a
bottleneck. The feature enables the system to dynamically choose for the NR PDCCH to occupy one or two symbols based on the traffic
demand. NR PDSCH mapping type B is used for scheduling data when two symbols are allocated for the NR PDCCH. The feature optimizes the
impact on NR PDSCH by using only one symbol for the NR PDCCH if two symbols are not required, balancing the resources between the control
channel and the shared channel.

To gain the benefits of the feature, the UEs must be capable of supporting NR PDCCH in symbol three and NR PDSCH mapping type B. NR
PDSCH mapping type B starts in symbol four with a length of 10 symbols, and is used in the following cases:

– When symbol three is used for NR PDCCH and three symbols are used for the LTE control region.

– When symbols two and three are used for NR PDCCH and two symbols are used for the LTE control region.
 NR PDSCH DMRS positions are shifted by one symbol to avoid the collision with LTE CRS in symbol four and 11. The shifting is done for all
PDSCH mapping type B transmissions. For more information, see 3GPP TS 38.211; NR; Physical Channels and Modulation, Release 16.
The feature has the following benefits:

– The NR PDCCH capacity is improved in NR ESS cell pairs when two PDCCH symbols are used.

– Using two PDCCH symbols when PDCCH load is high can increase the downlink and uplink NR cell throughput and reduce latency.

– Dynamic adaptation and optimization of the NR PDCCH capacity and overhead in ESS cells improve the efficiency in order to meet the
traffic demands.

– The added PDCCH capacity enables the scheduling of more available PDSCH or PUSCH resources, which might otherwise be blocked by
PDCCH capacity shortage.

– Slots with three symbols used for LTE control region can be used by NR.

UEs not supporting the required capabilities are scheduled with NR PDCCH in symbol two and with NR PDSCH mapping type A.

[Link] UE Classification and RRC Reconfiguration

UEs are reconfigured to use the feature based on their capabilities.

To gain the benefits of the feature, the UEs must be capable of supporting a combination of capabilities, based on which the UEs are classified:

– PDSCH mapping type B scheduling with 9 or 10 symbol length and DMRS shift for 10 symbol length

– At least one of the following additional capabilities must also be supported:

• PDCCH monitoring with a span of three symbols

• PDCCH monitoring with a span of three symbols within the first four symbols
 UE configuration needed

Is the feature No
enabled in ESS cell pair?

Yes

RRC setup or reconfiguration

What is the reason without UE capabilities
for UE configuration?

RRC reconfiguration
with UE capabilities

Does UE support No UE scheduled as UEs not

PDSCH Type B allocation? supporting required capabilities

Yes

No

Does UE support No Does UE support

additional capability A? additional capability B?

Yes Yes

UE scheduled as UEs
supporting required capabilities

L0003506A

Figure 19 Classification of UE Capability Support

Note: In Figure 19 additional capability A capability refers to PDCCH monitoring with a span of three symbols. Additional capability B refers
to PDCCH monitoring with a span of three symbols within the first four symbols.
When the feature is enabled in an ESS cell pair, the UEs can be classified based on the supported capabilities in the following way:

– UEs not supporting the capabilities required for the feature

UEs fall into this category if they support only either the mandatory or one of the PDCCH monitoring additional capabilities.

– UEs supporting the capabilities required for the feature

When the network does not know the UE capabilities, all ESS UEs are configured as those that do not support capabilities required for the
feature. Once UE capability information is available, UEs that support the required capabilities are reconfigured with PDCCH and PDSCH
configuration options to use in each slot depending on the traffic demand in the ESS cell pair.

At Secondary Node Addition, the UE capabilities are known. Therefore, UEs that support the required capabilities are reconfigured with PDCCH
and PDSCH configuration options to use in each slot depending on the traffic demand in the ESS cell pair.

[Link] Downlink Channel Configuration Based on UE Classification

The feature configures the UEs with downlink channels differently based on the UE capabilities.

If the feature is enabled in an ESS cell pair, UEs are scheduled according to their capabilities and to the required NR PDCCH capacity.
UEs supporting the required capabilities at low or normal NR PDCCH load are typically configured with the following downlink channel
resources in one slot:

– NR PDCCH is allocated in symbol two

– NR PDSCH mapping type A allocation starting in symbol three

UEs supporting the required capabilities at high NR PDCCH load are typically configured with the following downlink channel resources in one
slot:

– NR PDCCH can be allocated in either symbol two or symbol three

– NR PDSCH mapping type B allocation starting in symbol four with DMRS position shifted by one symbol

UEs lacking the required capabilities at any NR PDCCH load are configured with the following downlink channel resources in one slot:

– NR PDCCH is allocated in symbol two

– NR PDSCH Type A allocation starting in symbol three

Note: UEs involved in the following procedures are also treated as UEs that lack the required capabilities:

– UEs involved in system information, paging and random access signaling

– UEs before the UE capabilities are known

– UEs that have an ongoing RRC Reconfiguration procedure

– UEs that have ongoing DTX retransmissions

The duration of the LTE control region is not affected by the scheduling of the UEs.

UE lacking the required capabilities UE with the required capabilities

Type B

1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14

Type A Type A

1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14

Legend
Type B
NR PDSCH NR DMRS

LTE PDSCH
1 2 3 4 5 6 7 8 9 10 11 12 13 14

LTE CRS (example)

Reserved for LTE and NR control channels

L0003507B

Figure 20 UE Scheduling
If the LTE control region is configured to take up three symbols, the UEs are scheduled the following way:

– UEs that lack the required capabilities are not scheduled.

– UEs with the required capabilities are scheduled with NR PDCCH in symbol three, and NR PDSCH Type B with 10-symbol length.

If the LTE control region is configured to take up two symbols, the UEs are scheduled the following way:

– UEs that lack the required capabilities are scheduled with NR PDCCH in symbol two, and NR PDSCH mapping type A.
 – UEs with the required capabilities are scheduled with NR PDCCH in either symbol two or symbol three and NR PDSCH mapping type A or
type B with 10-symbol length.

Note: DMRS positions are shifted by one symbol to avoid the collision with LTE CRS. This means that the DMRS positions are moved from
symbol four to five and from symbol 11 to 12.

[Link] CORESET and Search Space Configuration

The possibility of using a single NR PDCCH symbol in slots where it is sufficient for the NR PDCCH capacity requires an additional search
space.

The CORESET and UE-specific search space configuration that is supported with up to two NR PDCCH symbols is different depending on the
UE capabilities:

– For UEs that lack the required capabilities, one-symbol CORESET is applied with one UE-specific search space in symbol two.

– For UEs with the required capabilities, one-symbol CORESET is applied with two UE-specific search spaces associated with the same
CORESET. One search space is in symbol two, and the other is in symbol three. Each search space has fewer PDCCH candidates than in
the case of one UE-specific search space. The actual PDCCH candidates vary for every UE in every slot; while their number is constant.

2.14.2 Dependencies of LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols

Table 41 Feature Dependencies

Feature Identity Standard Relationship Relationship Scope Description

Feature Name

To avoid performance
degradation when the
High Speed UE
Low/Mid-Band
feature is active, the
High Speed UE
FAJ 121 5268 NR Conflicting Cell-level conflict number of configured
Low/Mid-Band
DMRS symbols must
be limited to one
mandatory and one
additional DMRS
symbol.
With CRB blanking,
the number of CCEs
for a CORESET is
reduced for cells with
FAJ 121 5228: LTE-
10 MHz bandwidth. In
NR FDD Spectrum
FAJ 121 5228 NR Related this case, the number
Sharing with Flexible
of NR PDCCH
Channel Bandwidth
candidates increases
for two UE-specific
search spaces at low
aggregation levels.
FAJ 121 5301: LTE- FAJ 121 5301 NR Related The LTE-NR FDD
NR FDD Spectrum Spectrum Sharing
Sharing with Category with Category M
M feature can reduce NR
PDCCH capacity when
Category M
transmission is used
and the third symbol is
occupied with
additional NR PDCCH.
An increase can occur
in PDCCH blocking
because of the
Category M
narrowband
placement in the
transmission
bandwidth.
 Feature Identity Standard Relationship Relationship Scope Description
Feature Name

If the LTE control

region is configured to
take up two symbols,
and two-symbol NR
PDCCH is used, fewer
resources are
available in the
additional symbol for
NR PDCCH.
If the LTE control
region is configured to
take up three symbols,
resources can be
assigned to Category
M. This reduces the NR
PDCCH capacity and
causes NR resources
to be wasted,
especially at high
Category M traffic.
Rate matching is not
applied for UEs
FAJ 121 5378: LTE-
scheduled with NR
NR FDD Spectrum
PDSCH Type B in slots
Sharing with Rate
FAJ 121 5378 NR Related where the DMRS
Matching around LTE
collides with the
Synchronization
region around which
Signal and PBCH
the PDSCH is to be
rate-matched.
When the LTE-NR
FDD Spectrum
Sharing with Multiple
NR PDCCH Symbols
feature is enabled and
symbol three is used
for NR PDCCH,
resource allocation for
the NR Air Interface
Load Generator
feature starts from
symbol four. If symbol
three is not required
for NR PDCCH,
resource allocation for
the NR Air Interface
NR Air Interface Load Load Generator
FAJ 121 5191 NR Related
Generator feature can
dynamically start in
symbol three. With the
LTE-NR FDD
Spectrum Sharing
with Multiple NR
PDCCH Symbols
feature, both NR
PDSCH Type A and
Type B can be used in
the cell for some UEs.
The NR PDSCH
allocation type might
change slot by slot.
These changes are
expected to improve
performance.

Limitations
The combination of three or more standards is supported. A combination of the following standards is supported:
 – ESS

– GSM

– LTE

– NB-IoT

– NR

Network Requirements
This feature requires the following network elements:
ENM It is recommended to use ENM version 22.4 or later to support the MOM changes introduced by this feature. If the Release
Independence Manager application is used, the MOM changes are supported on earlier ENM versions also.

UE The UE must be compliant with the RRC protocol version 16.9.0 or later. For more information, see 3GPP TS 38.331; NR; Radio
Resource Control (RRC); Protocol specification.
The UEs must be capable of supporting a combination of capabilities required by this feature:

– PDSCH Type B scheduling with 9-symbol or 10-symbol length and DMRS shift for 10-symbol length

– At least one of the following additional capabilities must also be supported:

• PDCCH monitoring with a span of three symbols

• PDCCH monitoring with a span of three symbols within the first four symbols

2.14.3 Network Impact of LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols
The NR PDCCH capacity in an ESS cell pair can be increased with the feature. Impact on resource allocation for the NR PDCCH, NR PDSCH,
and NR throughput can be monitored.

Capacity and Performance

With the dynamic adaptation and optimization of the NR PDCCH resources, the feature increases the NR PDCCH capacity for all bandwidths in
ESS. Increased NR PDCCH capacity is most beneficial in cells with narrower bandwidths.
With the introduction of NR PDSCH Type B, the available resources for NR traffic can be better utilized even when the LTE and NR PDCCH take
up four symbols in total. The resource allocation can be monitored with the following PM counters:

– [Link]

– [Link]

– [Link]

Depending on the traffic demand, the feature enables the use of up to two symbols for NR PDCCH. When NR PDCCH uses two symbols, the NR
PDSCH has one fewer symbols than when the PDCCH uses one. The resource use between the control channel and the shared channel
improves. With a low number of large allocations, one PDCCH symbol allows higher PDSCH throughput, while a higher number of small PDSCH
and PUSCH allocations might require two PDCCH symbols to avoid control channel bottlenecks.
The gains with the feature can be lower if Category M traffic is ongoing in the ESS cell pair.
During high NR PDCCH load in the ESS cell pair, the added NR PDCCH capacity of using two symbols for NR PDCCH transmission allows the
scheduling of more of the available PDSCH or PUSCH resources. Without the feature, such resources are blocked by the NR PDCCH capacity
shortage of using only one symbol. This results in the following network impact:

– More users can be scheduled in each slot.

– Latency can be reduced.

– NR PDCCH blocking rate can be reduced.

This means that the occasions when downlink or uplink resources are not fully utilized because of NR PDCCH resource shortage are reduced.
These occasions can be monitored through the following PM counters:

– [Link]
The available resources can be monitored through the [Link] and the
[Link] PM counter.

– [Link]

For NR throughput increase, the following resource indicators can be monitored:

 – Average DL Throughput per NRCellDU

– Average UL Throughput per NRCellDU

The following PM counters show the increase in the scheduling entities in each slot:

– [Link]

– [Link]

Interfaces
This feature affects the Uu interface. The RRCReconfiguration RRC message is updated with the following information:

– NR PDSCH mapping Type B configuration

– Additional DMRS positions for NR PDSCH

– Search space configuration

Other Network Elements

No impact.

[Link] Update of the Blockage on LTE due to NR PDCCH Reserved PRB KPI

The Blockage on LTE due to NR PDCCH Reserved PRB KPI is updated to consider PRBs that cannot be assigned to the NR PDSCH or
PDCCH on symbol three.

The LTE-NR FDD Spectrum Sharing with Category M feature can reduce NR PDCCH capacity when Category M transmission is used and the
third symbol is occupied with additional NR PDCCH. An increase can occur in PDCCH blocking because of the Category M narrowband
placement in the transmission bandwidth.

Therefore, the formula of the Blockage on LTE due to NR PDCCH Reserved PRBs KPI is updated the following way:

[Link] - [Link] - [Link]

The difference between the [Link] and the [Link] PM counters represents
the number of PRBs blocked for the LTE PDSCH. This KPI calculation is updated with [Link], the ESS PM counter
that counts the number of PRBs assigned to Category M in the NR region. The Blockage on LTE due to NR PDCCH Reserved PRB KPI also
includes PRBs that cannot be assigned to the NR PDSCH or NR PDCCH on symbol three because of the Category M narrowband placement in
the transmission bandwidth.
PRB

KPI: LTE blocked

by NR PDCCH

pmPrbCatmNr

pmPrbUsedPdcchPdschNr

pmPrbUsedPdschNr

Time
Legend

LTE PRB NR PRB

Cat-M PRB Blocked PRB

L0003508A
 Figure 21 Components of the Blockage on LTE due to NR PDCCH Reserved PRB KPI

2.14.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols
Configuration management, fault management, and performance management aspects of the LTE-NR FDD Spectrum Sharing with
Multiple NR PDCCH Symbols feature.

Activation The LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols feature is available as long as ESS is deployed. The
feature does not have an associated software license key. This means that the feature does not have an entry in the LKF
that is installed on the node.

Initial The feature is enabled by setting the [Link] attribute to ADAPT_MAX_2. By configuring this
Configuration value, the gNodeB dynamically adapts the number of symbols, up to two, allocated in a slot for the NR PDCCH. This
depends on the actual traffic demand in an ESS cell pair. The feature can be configured on the cell level. For the
configuration changes to take effect, the ESS cell pair must be locked and unlocked.

KPIs For ESS-related KPI and counter information, see Manage Performance.
For KPIs and PM counters used to monitor the performance of the LTE-NR FDD Spectrum Sharing with Multiple NR
PDCCH Symbols feature, see Network Impact of LTE-NR FDD Spectrum Sharing with Multiple NR PDCCH Symbols.

2.15 FAJ 121 5607: LTE-NR FDD Spectrum Sharing with Micro Sleep Tx

2.15.1 LTE-NR FDD Spectrum Sharing with Micro Sleep Tx Overview

The feature decreases power consumption in radio units used in ESS.

Feature Identity FAJ 121 5607

Value Package Name LTE-NR FDD Ericsson Spectrum Sharing
Value Package Identity FAJ 801 4012
Node Type Baseband Radio Node
Licensing Non-license-controlled feature. No license is required.

The feature decreases power consumption in radio units. Power amplifiers are automatically turned off in the radio unit on TX branches for
each downlink symbol that is not used for transmission.

When a partner cell is locked or deactivated, the feature continues to operate in the following cases:

– If the EUtranCellFDD MO instance is locked or deactivated, the feature continues to operate for the NR cell with traffic disturbance.

– If the NRCellDU MO instance is locked or deactivated, the feature continues to operate for the LTE cell.

2.15.2 Dependencies of LTE-NR FDD Spectrum Sharing with Micro Sleep Tx

The feature requires the LTE-NR FDD Spectrum Sharing Enabler feature to be activated.

Table 42 Feature Dependencies

Feature Name Feature Identity Standard Relationship Relationship Description

Scope

The LTE-NR FDD Spectrum Sharing

Enabler feature must be activated for
FAJ 121 5147: LTE-NR FDD Node-level
FAJ 121 5147 NR Prerequisite the LTE-NR FDD Spectrum Sharing
Spectrum Sharing Enabler prerequisite
with Micro Sleep Tx feature to be
operational.
The LTE-NR FDD Spectrum Sharing
with NR Standalone feature must be
FAJ 121 5257: LTE-NR FDD
activated for the LTE-NR FDD
Spectrum Sharing with NR FAJ 121 5257 NR Related
Spectrum Sharing with Micro Sleep Tx
Standalone
feature to be operational in NR
standalone configuration.
Feature Name Feature Identity Standard Relationship Relationship Description
Scope

The LTE-NR FDD Spectrum Sharing

with Micro Sleep Tx feature supports
FAJ 121 5406: LTE-NR FDD the varying configuration of downlink
Spectrum Sharing with FAJ 121 5406 NR Related MBSFN subframes. The extent of
Tunable NR Subframes power savings can vary depending on
the downlink MBSFN subframe
configuration.
The LTE-NR FDD Spectrum Sharing
FAJ 121 3089: Micro Sleep with Micro Sleep Tx feature replaces
FAJ 121 3089 LTE Related
Tx the Micro Sleep Tx feature in ESS
deployment.
The LTE-NR FDD Spectrum Sharing
with Micro Sleep Tx feature might not
FAJ 121 0860: Shared LTE operate correctly when the Shared LTE
FAJ 121 0860 LTE Conflicting Partially impaired
RAN RAN feature activates or deactivates a
sector carrier without locking or
unlocking it.

Hardware
The feature has the following hardware limitations:

– Indoor radio units are not supported.

– Some Radio 8843 B2 B66A radio units might restart, when the feature is enabled.
Note: In this event, to prevent performance degradation, the feature must be disabled.

The SSB-based VSWR measurements function is supported on the following radio units:

– Radio 2212

– Radio 2238

– Radio 2260

– Radio 2262

– Radio 2279

– Radio 2460

– Radio 2479

– Radio 4020

– Radio 4415

– Radio 4417

– Radio 4419

– Radio 4426

– Radio 4428

– Radio 4429

– Radio 4432

– Radio 4471HP

– Radio 4456

– Radio 4460

– Radio 4466 44B1 44B3 44B7 C

– Radio 4466 44B1 44B3 44B40 C

– Radio 4478

– Radio 4480
 – Radio 4481

– Radio 4490

– Radio 4490HP

– Radio 4499

– Radio 4890HP

– Radio 6626

– Radio 6646

2.15.3 Network Impact of LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
The feature saves power in symbols that do not transmit downlink data.

Capacity and Performance

The feature decreases power consumption in radio units with no negative impact on capacity or performance.
The following PM counters measure potential power-saving time:

– [Link]

– [Link]

The feature measures power-saving time in each sector carrier, which might be different from the power-saving time in the radio unit.

Table 43 Applicable Counter Depending on Partner Cell States

Unlocked or Activated Partner Cell Applicable Counter

Both [Link]
Only LTE [Link]
Only NR [Link]

The SSB-based VSWR measurements function decreases power consumption by replacing injected messages with SSB transmissions for
VSWR measurements. This function also provides additional power savings by allowing the LTE-NR FDD Spectrum Sharing with Micro Sleep
Tx feature to activate more often as fewer downlink symbols are used for transmission.
The following PM counters monitor the total time and ratio Tx branches are switched off in radio units capable of reporting it, regardless of
radio node configurations and activated sleep features:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

Interfaces
No impact.

Other Network Elements

No impact.

2.15.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
The LTE-NR FDD Spectrum Sharing with Micro Sleep Tx feature is a non-license-controlled feature. It is activated by default and does not
have configuration options.

Activation The feature is a non-license-controlled feature, it does not require activation.

The feature is enabled by default, and can be disabled by setting the [Link] attribute to
false.
 Note: If any of the sector carriers are locked while the feature is enabled, the value of the
[Link] attribute remains true. This value indicates that the feature is
operational.
For the feature to operate, the relevant SectorCarrier and NRSectorCarrier MO instances must have ESS enabled.
The [Link] attribute affects only the LTE cell of an ESS cell pair. The LTE-NR FDD
Spectrum Sharing with Micro Sleep Tx feature is active in the NR cell if the LTE cell is locked or uses the Cell Sleep Mode feature.
KPIs For ESS-related KPI and counter information, see Manage Performance.

2.15.5 Feature Change History of LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
Changes that affect the LTE-NR FDD Spectrum Sharing with Micro Sleep Tx feature and the impact that the feature has on the network.

Table 44 Feature Change History

Enhancement Name Description

This feature enhancement allows the LTE-NR FDD Spectrum Sharing
23.Q3: Locked Partner Cell Support for LTE-NR FDD Spectrum Sharing
with Micro Sleep Tx feature to operate when an ESS partner cell is
with Micro Sleep Tx
locked.
This feature enhancement increases the observability of power-saving
23.Q3: Observability Enhancement for LTE-NR FDD Spectrum Sharing
time with the LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
with Micro Sleep Tx
feature.
This feature enhancement introduces SSB-based VSWR
23.Q4: SSB-Based VSWR Measurements for ESS
measurements for ESS.
This feature enhancement provides observability on multiple MO
24.Q1.0: Enhanced Observability of Switched-off Tx Branches for LTE-
levels of the total time a Tx branch is switched off in radio units
NR FDD Spectrum Sharing with Micro Sleep Tx
capable of reporting it.
24.Q1.0: Enhanced Observability of Switched-off Tx Branches for LTE- This feature enhancement extends the observability of the total time a
NR FDD Spectrum Sharing with Micro Sleep Tx for Radio Group 6 Tx branch is switched off to additional radio units in radio group 6.
This feature enhancement enables the LTE-NR FDD Spectrum Sharing
24.Q2.0: Radio Gateway and LC-05 9x CPRI Line Card in Conversion
with Micro Sleep Tx feature in Radio Gateway and LC-05 9xCPRI line
Mode Support for LTE-NR FDD Spectrum Sharing with Micro Sleep Tx
card configurations.
24.Q2.0: Extended Hardware Support for Observability of Switched
This feature enhancement extends the observability of the time a Tx
off Tx Branches for LTE-NR FDD Spectrum Sharing with Micro Sleep
branch is switched off for additional radio units in radio group 6.
Tx

2.16 FAJ 121 5660: LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation

2.16.1 LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation Overview
This feature enables the use of dynamic slot aggregation in ESS.

Feature Identity FAJ 121 5660

Value Package Name LTE-NR FDD Ericsson Spectrum Sharing Performance Boost
Value Package Identity FAJ 801 4020
Node Type Baseband Radio Node
Licensing Licensed feature. One license is required for each node.

This feature enables the use of Dynamic Slot Aggregation for VoNR traffic using PUSCH Repetition Type A in ESS cells.

This provides the following benefits:

– Improved coverage for UEs in poor channel conditions

– Improved PDCCH channel utilization

The feature is not supported in the LTE to EN-DC-ESS migration scenario.

2.16.2 Dependencies of LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation
The feature requires the activation of multiple prerequisite features.
 Table 45 Feature Dependencies

Feature Name Feature Identity Standard Relationship Relationship Description

Scope

The LTE-NR FDD Spectrum Sharing

Enabler feature must be activated for
LTE-NR FDD Spectrum Node-level
FAJ 121 5147 NR Prerequisite the LTE-NR FDD Spectrum Sharing
Sharing Enabler prerequisite
with Dynamic Slot Aggregation feature
to be operational.
The LTE-NR FDD Spectrum Sharing
with NR Standalone feature must be
LTE-NR FDD Spectrum activated for the LTE-NR FDD
FAJ 121 5257 NR Prerequisite
Sharing with NR Standalone Spectrum Sharing with Dynamic Slot
Aggregation feature to be operational
in NR standalone configurations.
The NR Dynamic Slot Aggregation for
VoNR feature must be activated for the
NR Dynamic Slot
FAJ 121 5471 NR Prerequisite LTE-NR FDD Spectrum Sharing with
Aggregation for VoNR
Dynamic Slot Aggregation feature to be
operational.
The Cell Sleep Mode feature and the
LTE-NR FDD Spectrum Sharing with
Cell Sleep Mode FAJ 121 4390 NR Related
Dynamic Slot Aggregation feature can
be used together in ESS cell pairs.

Hardware
The UE must support PUSCH Repetition Type A.

2.16.3 Network Impact of LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation
The feature impacts network capacity.

Capacity and Performance

Enabling PUSCH Repetition in an ESS cell might have an impact on the amount of resources available for LTE, depending on the amount of
VoNR traffic.

Interfaces
No impact.

Other Network Elements

No impact.

2.16.4 O&M Aspects of LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation
Configuration management and performance management aspects of the LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
feature.

Activation The LTE-NR FDD Spectrum Sharing with Dynamic Slot Aggregation feature requires feature activation, performed during the
ESS deployment activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

KPIs For the ESS-related KPI and counter information, see Manage Performance.
3 ESS Operational Flow
Select a use case of interest to navigate to specific how-to articles.

Start

Deploy
Preparation ESS Deployment Examples

Software Installation Rollback

Initial Configuration

ESS
Scenario

Migration from LTE Migration from EN-DC-ESS Migration from LTE

to EN-DC-ESS to SA-ESS to SA-ESS

Monitor Optimize

Detect and Resolve Set Optimization Parameters

Manage Performance

Prevent

Decommissioning

L0002943A

Figure 22 ESS Operational Flow

3.1 Deploy
ESS deployment consists of a set of site readiness, software activation, and initial configuration activities.

The phases of the ESS deployment:

Phase 1: Preparation

Phase 2: Software Installation

Phase 3: Initial Cell Configuration

– Migration from LTE to EN-DC–ESS

– Migration from EN-DC–ESS to SA–ESS

– Migration from LTE to SA–ESS

3.1.1 Phase 1: Preparation

Ensure the site is ready for ESS.

This phase consists of the following tasks:

 1. Analyze Prerequisites

2. Conduct Site Survey

3. Create Network Design

4. Prepare Site

5. Define KPI Baseline

Back to ESS Operational Flow.

[Link] Analyze Prerequisites

Consider all prerequisites for ESS migration to ensure that the site meets the necessary conditions.

Begin with the preparation phase by analyzing the ESS requirements, the current status and evolution plan of the network, including available
bands and coverage needs, and select the spectrum to use for ESS.

Related concepts
ESS Impact on LTE Performance
Related reference
ESS Prerequisites

[Link] Conduct Site Survey

ESS reuses NR-capable hardware. A review of site inventory helps to establish whether the installed base can be used for spectrum sharing
or whether the site needs to be reconfigured or modernized.

Collect the following site information:

– HW equipment type

– Synchronization status

– Transport network status

– Cabling

– Power

– Dimensions

– Configuration data

Use the checklist to determine site readiness and plan relevant site preparation actions.

Table 46 ESS Site Readiness Checklist

Area Subarea Site readiness check Action if not ready

Upgrade to one of the ESS-ready Baseband Radio
ESS-compliant hardware ESS-compliant hardware deployed?
Nodes.
More than 12 LTE cells served by current LTE
LTE cells supported Add a Baseband node.
Baseband?
Baseband Restructure site, for example, introduce second
RI ports Mixed Mode RI port limitation hit?
Baseband, cascading Baseband, re-parenting.
LTE and NR IP addresses, VLAN ID & EN-DC
IP design Perform IP design.
connection in place?
Synchronization method Synchronization for NR FDD and E-RAN in place? Choose synchronization option and implement.
Mixed Mode Radio for NR FDD Low-Band (600
ESS-compliant hardware Check the Radio Units certified for ESS.
MHz–2600 MHz), 2TX or 4TX available?
Radio
LTE antenna system
LTE antenna system can be reused for ESS? Implement new antenna systems.
reuse
Fronthaul CPRI interface status The availability after Mixed Mode Baseband Update the connection topology, for example, to a
migration, physical connection topology update cascading configuration, and introduce Baseband
required or not? R503 to expand the number of CPRI ports. Radio
Gateway R608 is introduced for conversion from
 Area Subarea Site readiness check Action if not ready
eCPRI to CPRI to support CPRI radio units. Line card
LC-05 9xCPRI is a hardware variant of Radio
Gateway R608.
Reconnection or recabling engineering work not
Perform reconnection or recabling.
needed? Check RI ports limitations.
New physical connections required, for example
Physical connectivity Update physical connections.
new Baseband introduced?
Logical connectivity updated, for example
Backhaul Logical connectivity parameter settings for NR traffic?
Update logical connections.

New IP/VLAN for NR added? Update IP design.

IP design
New routing configuration required? Update routing configurations in the affected nodes.
Core
5G EPC Network NSA compliant 5G EPC network available? Upgrade to NSA compliant 5G EPC network.
Network
ESS compliant ENM software to support Mixed
ENM ENM software version Upgrade ENM release: minimum ENM 20.3.
Mode Baseband and ESS CM/FM/PM available?

[Link] Create Network Design

Plan the implementation of the necessary activities to make a selected site ready to deploy ESS.

When creating the network design consider the following:

– Traffic management

– Synchronization

– Coverage and anchor selection

– Throughput and capacity

– Transport network

– Equipment

For more information, see ESS Solution Guideline.

[Link] Prepare Site

To make the site ESS-capable, ensure it has the required hardware, connectivity, capacity, and synchronization.

The site preparation for ESS focuses on four areas:

Hardware
Only ESS-compliant hardware can be upgraded with ESS software. Consult the results of the site survey and follow the directives of the
network design.
The introduction of Mixed Mode Baseband for ESS migration causes an increased load on the existing LTE Baseband units, adding new nodes
can be required.
LTE-NR Mixed Mode Baseband units:

– Baseband 6631

– Baseband 6641

– Baseband 6648

– RAN Processor 6647

– RAN Processor 6651

– RAN Processor 6672

– Radio Processor 6337

– Radio Processor 6339

– Radio Processor 6353

– Radio Processor 6347

 – Radio Processor 6507
For the supported list of LTE-NR mixed mode radio units, see Supported Radio Capabilities and Radio Configurations for ESS.
For the supported list of IRUs and Radio Dot variants for LTE-NR mixed mode, see Supported Radio Capabilities.

Connectivity
Using a RAN Compute unit in LTE-NR mixed mode configuration results in a reduced number of Radio Interface (RI) ports for NR and ESS on
some RAN Compute units. Therefore, when NR or ESS is used on these RAN Compute units, radio units must be connected to a subset of RI
ports that are active when the RAN Compute unit uses LTE-NR mixed mode configuration. Transport network connections must be upgraded
as well in fronthaul and backhaul.
For the supported number of RI ports on RAN Compute units supporting ESS, see DU and Baseband Configurations and Capacity.
For information on how to expand the number of RI ports for CPRI, see ESS Solution Guideline.

Capacity
An ESS cell pair is implemented on a RAN Compute unit with LTE-NR mixed mode configuration as one LTE and one NR cell. The maximum
number of supported LTE and NR cells depends on the RAN Compute unit. For the supported number of LTE and NR cells in ESS, see DU and
Baseband Configurations and Capacity.
The cells must be split evenly between LTE and NR when configuring an ESS cell pair.
The cells can be split several ways, including the following examples:

– 4 ESS cells (4 LTE+ 4 NR) + 8 non-ESS cells

– 6 ESS cells (6 LTE + 6 NR) + 6 non-ESS cells

If more capacity is needed, the following options can be considered:

– Rearranging capacity between the RATs on existing Baseband units

– Adding a new Baseband unit

For more information, see Capacity Prerequisites.

Synchronization
NR synchronization on FDD bands can be achieved through one of the following methods:

– Partial time support with reduced accuracy limit synchronization

– Node group synchronization

– Time synchronization, either GPS or PTP G.8275.1

Note: In a configuration where LTE and NR share the same Baseband, the synchronization functionality is also shared.

[Link] Define KPI Baseline

Perform a KPI analysis on a specified Node Element (NE) collection.

Steps

1. Freeze the specified collection of nodes, for example, by limiting the daily operations affecting the nodes in the FFI cluster to a minimum.

2. Monitor the Network KPIs in the specified NE collection and take alarm and KPI baselines. See View KPIs on how to create a KPI monitor
using ENM.
When establishing the KPI baseline, ensure that the set of KPIs selected for monitoring includes the potentially affected throughput KPIs.

Table 47 Throughput KPIs

RAT KPI Description

([Link] -
LTE LTE UE Throughput (Mbps) [Link]
)/([Link])/1000000
EUTRANCELLFDD. pmRadioThpVolDl )/(EUTRANCELLFDD.
LTE LTE Cell Throughput (Mbps)
pmSchedActivityCellDl)/1000000
NR NR Cell Throughput (Mbps) (0.064*[Link]/[Link])
NR NR UE Throughput (Mbps) (0.064*[Link]/NRCellDU. pmMacTimeDlDrb)

3. Analyze the results of the measurement to decide whether the cluster is stable enough to analyze the performance.
 4. Conclude the KPI measurement.

3.1.2 Phase 2: Software Installation

Install, activate and verify the new software for ESS.

These are typical tasks performed at software change. For details and best practices, see Upgrade RAN Software Using Automation Flow in
ENM and Upgrade RAN Software Manually in ENM.

1. Install software.

a. Request license key file.

b. Import software package.

c. Create network element collection.

d. Import license key file.

e. Perform health check.

f. Create backup.

g. Create software upgrade job.

2. Activate software.

a. Perform health check.

b. Disable alarm supervision.

c. Install license key file.

d. Export active alarms.

e. Execute software upgrade job.

f. Verify PM information.

g. Perform health check.

h. Enable alarm supervision.

i. Create backup.

3. Verify installation.

a. Check the node heartbeat.

b. View alarms and KPIs.

Use the same KPIs that were defined when establishing the KPI baseline in the preparation phase.

4. Rollback node in ENM.

Back to ESS Operational Flow.

3.1.3 Phase 3: Initial Cell Configuration

[Link] Migration from LTE to EN-DC–ESS

 Initial Configuration
Migration from
LTE to EN-DC-ESS

Lock LTE and NR Cells

Active Features

Enable Spectrum Sharing in LTE FDD Cell

Enable Spectrum Sharing in NR Cell

Create Unique ESS Sector Carrier Pair ID

Unlock ESS Cell Pair

Verify ESS Cell Configuration

L0002940A

Figure 23 Initial Configuration Flow when Migrating from LTE to EN-DC–ESS

Back to ESS Operational Flow.

[Link].1 Lock LTE and NR Cells

Lock both the LTE and the NR cell to suspend traffic and configure the general LTE and NR attributes for the ESS cell pair.

Prerequisites

– MO instances for LTE and NR cells exist:

• EUtranCellFDD MO for the LTE cell

• NRCellDU for the NR cell

Steps

1. Set the [Link] attribute to LOCKED.

Result: The value of the [Link] attribute changes to OFF_LINE.

2. Lock the EUtranCellFDD MO.

Result: The value of the [Link] attribute changes to OFF_LINE.

3. Optional: Lock the NRSectorCarrier MO, if needed.

4. Optional: Lock the TermPointToGNB MO, if needed.

Back to the Initial Configuration flow.

[Link].1.1 ESS Cell Pair Example

To complete the deployment, LTE and NR cells must be locked and configured to form ESS cell pairs.

An example ESS cell pair shown in the figure gives a high-level view of the MO instances and highlights the relation between attribute values.
 ESS eNodeB ESS gNodeB

X2
EUtranCellFDD NRCellCU
Cellid=646 Cellid=344

F1
GUtranCellRelation EUtranCellRelation
essEnabled=True essEnabled=True

ExternalGUtranCell ExternalEUtranCell NRCellDU

localCellId=344 cellLocalId=646

SectorCarrier NRSectorCarrier
essScPairID=39 essScPairID=39

L0003006B

Figure 24 Example Cell Pair

[Link].1.2 ESS Cell Pair with NB-IoT Cell Example

To complete the deployment, LTE cells that host an NB-IoT cell and NR cells must be locked and configured to form ESS cell pairs.

The example ESS cell pair shown in Figure 25 gives a high-level view of the MO instances and the relation between attribute values.

ESS eNodeB ESS gNodeB

X2
EUtranCellFDD NRCellCU
Cellid=646 Cellid=344

NbIotCell

F1
GUtranCellRelation EUtranCellRelation
essEnabled=True essEnabled=True

ExternalGUtranCell ExternalEUtranCell NRCellDU

localCellId=344 cellLocalId=646

SectorCarrier NRSectorCarrier
essScPairID=39 essScPairID=39

L0003064A

Figure 25 Example Cell Pair with NB-IoT Cell

[Link].2 Activate Features in the Migration Scenario from LTE to EN-DC–ESS

Features to be activated when migrating from LTE to EN-DC–ESS. The features are activated following the usual feature activation
procedure.

Prerequisites

– The license key is installed in the node.

– All prerequisite features are operable and configured on the Baseband unit that supports both LTE and NR in a mixed mode
configuration.

– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

Steps

1. Set the attribute featureState to ACTIVATED in the applicable MO instance.

Feature Name License Control MO

FAJ 121 5228: LTE-NR FDD Spectrum FeatureState=CXC4012528

Sharing with Flexible Channel Bandwidth

FAJ 121 5242: NR UE Throughput Booster FeatureState=CXC4012503

FAJ 121 5309: LTE-NR FDD Spectrum FeatureState=CXC4012543

Sharing with Policy-based Biasing

FAJ 121 5333: LTE-NR FDD Spectrum FeatureState=CXC4012554

Sharing with Downlink Data and DMRS
Multiplexing

FAJ 121 5301: LTE-NR FDD Spectrum FeatureState=CXC4012537

Sharing with Category M

FAJ 121 5306: LTE-NR FDD Spectrum FeatureState=CXC4012540

Sharing with NB-IoT

FAJ 121 5382: LTE-NR FDD Spectrum FeatureState=CXC4012583

Sharing with Dual Outer Loop Link
Adaptation

FAJ 121 5378: LTE-NR FDD Spectrum FeatureState=CXC4012581

Sharing with Rate Matching around LTE
Synchronization Signal and PBCH

FAJ 121 5406: LTE-NR FDD Spectrum FeatureState=CXC4012595

Sharing with Tunable NR Subframes
FAJ 121 5473: LTE-NR FDD Spectrum FeatureState=CXC4012617
Sharing with QoS-Aware Relative Resource
Allocation

After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.
Back to the Initial Configuration flow.
[Link].3 Enable Spectrum Sharing in LTE FDD Cell

Enable spectrum sharing by configuring the LTE cell and setting up a corresponding NR cell relation.

Prerequisites

– The EUtranCellFDD MO instance to be used for spectrum sharing is locked.

– The NRCellDU MO instance to be paired with the LTE cell is identified.

– An ExternalGNodeBFunction MO instance representing the gNodeB with the partner NR cell, and a corresponding
TermPointToGNB MO instance exist.

– A GUtranFreqRelation MO instance exists.

Steps

1. Create an ExternalGUtranCell MO instance and configure the following attributes to match the configuration of the partner NR cell:

– [Link]

– [Link]

– [Link]

2. Create a GUtranCellRelation MO instance and configure it as follows:

Table 48 Configuration Values of GUtranCellRelation for Spectrum Sharing

Attribute Value
[Link] true
[Link] false
A reference to the ExternalGUtranCell instance created
[Link]
in Step 1

3. Create a SectorCarrier MO instance and configure it as follows:

Table 49 Configuration Values of SectorCarrier for Spectrum Sharing

Attribute Value
A unique, non-zero value that is the same as the
[Link]
corresponding [Link]
[Link] A unique value identifying the eNodeB sector carrier

4. Add the SectorCarrier MO instance created in Step 2 to the [Link] attribute as reference.

After This Task

Check the parameter values against the checklist for LTE Cells.
Back to the Initial Configuration flow.

Related reference
ESS Parameter Checklist for LTE Cells

[Link].3.1 ESS Parameter Checklist for LTE Cells

The list of valid parameter values is used to check the compliance of LTE cells with ESS requirements.

For parameter recommendations, see LTE RAN Parameter Recommendations Lists.

Table 50 Valid LTE Parameter Settings for LTE-NR FDD Spectrum Sharing Enabler

MO Attribute Valid Value

[Link] Larger than PSF3(1)
[Link] true
[Link] Supported PRACH formats in ESS are configured by using the
following values:
–
MO Attribute Valid Value
For Format 0, the attribute value must be less than 15 with the
[Link] attribute set
to false.

– For Format 1, attribute value must be greater than 15 with the

[Link] attribute set
to false. This configuration is only applicable if the Maximum
Cell Range (FAJ 121 0869) is activated for the LTE cell.
[Link] false(2)
[Link] 0 or 1(3)
[Link] 0
One of the following values:
– 10000
[Link]
– 15000

– 20000
[Link] 0
[Link] true(4)
[Link] 11(6)(5)
[Link] SF1(6)
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised.
If the value is empty, the RF branches are selected by the system.
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised.
If the value is empty, the RF branches are selected by the system.
One of the following values:
– 10000
[Link]
– 15000

– 20000
[Link] 0
[Link] Any value in the range of 0–29
[Link] false
One of the following values:
– TRANSMISSION_MODE_3

– TRANSMISSION_MODE_4
[Link]
– TRANSMISSION_MODE_9
Note: If the value of TRANSMISSION_MODE_9 is used, the
[Link] attribute must
be set to NZP_ZP_CSIRS.

[Link] false
[Link] false
[Link] SAME_MBSFN_SUBFRAMES(7)
GUtranFreqRelation.endcB1MeasPriority -1(8)
[Link] The value set for the [Link] attribute
must be the same as the value set for the
 MO Attribute Valid Value
[Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
Values greater than 4 are not supported in ESS.
The value set for the [Link] attribute
must be the same as the value set for the
[Link]
[Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
When the LTE-NR FDD Spectrum Sharing with Policy-based Biasing
[Link] feature (FAJ 121 5309) is activated, all values are possible to
configure, depending on prioritized RAT preference.
(1) When set, the value must apply to all QCIs. For this reason, the [Link]=18 DRX profile is used for bearer-level QCI configuration.
(2) The attribute is used in the [Link] attribute to configure PRACH format in the LTE cell.
(3) If PRACH success rate on the NR side shows degradation, the value of the attribute can be changed to 0. This way, the neighbor cell interference between PRACH and Random
Access Msg3 can be minimized.
(4) This is needed to enable PRS consistency check on ESS EutranCellFDD MO.
(5) If another than the recommended value needs to be used in ESS, the configuration must consider MBSFN subframe positions. These are 1, 2, and 21 in a 40-subframe pattern.
(6) The recommended parameter value ensures that the subframe positions allocated for LTE PRS do not collide with the MBSFN subframes in ESS.
(7) The attribute value indicates that the handover source and target LTE cells must have the same MBSFN subframe allocation if both cells are used in ESS.
SAME_MBSFN_SUBFRAMES can generally be used if most LTE cells are ESS cells.
(8) EN-DC is not considered for the NR cell on the same frequency with the LTE cell when used in ESS. This is needed only in the GUtranFreqRelation MO between LTE ESS
and NR ESS of the same ESS pair.
If the values of the following attribute partners do not match, the Inconsistent Configuration alarm is raised:

Table 51 ESS Attribute Partners

LTE NR
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]

Related tasks
Enable Spectrum Sharing in LTE FDD Cell

[Link].4 Enable Spectrum Sharing in NR Cell

Enable spectrum sharing by configuring the NR cell and setting up a corresponding LTE cell relation.

Prerequisites

– An ExternalENodeBFunction MO instance representing the eNodeB with the partner E-UTRAN cell exists.

Steps

1. Create an ExternalEUtranCell MO instance and configure the [Link] attribute to match the
configuration of the partner LTE cell.

2. Create an EUtranCellRelation MO instance and configure it as follows:

Table 52 Configuration Values of EUtranCellRelation for Spectrum Sharing

Attribute Value
[Link] true
A reference to the ExternalEUtranCell instance created
[Link]
in Step 1
 3. Create an NRSectorCarrier MO instance and configure it as follows:

Table 53 Configuration values of NRSectorCarrier for Spectrum Sharing

Attribute Value
A unique, non-zero value that is the same as the
[Link]
corresponding [Link]
[Link] A unique value identifying the gNodeB sector carrier

4. Add the NRSectorCarrier MO instance created in Step 2 to the [Link] attribute as reference.

After This Task

Check the parameter values against the checklist for NR Cells.
Back to the Initial Configuration flow.
Related reference
ESS Parameter Checklist for NR Cells

[Link].4.1 ESS Parameter Checklist for NR Cells

The list of valid parameter values can be used to check the compliance of NR cells with ESS requirements.

For parameter recommendations, see NR RAN Parameter Recommendations Lists.

Table 54 ESS Parameter Settings for NR Cells

MO Attribute Valid Value

[Link] 40
[Link] 0
[Link] DEACTIVATED
One of the following values:
– START_LOWER_EDGE
[Link]
– START_HIGHER_EDGE

– RANDOM_START_LOWER_OR_HIGHER
[Link] Equal to or greater than ONDURATIONTIMER_6MS.
[Link] 0(1)
[Link] 20
[Link] 15
[Link] 15
The parameter must be left empty so that the system can choose the
[Link]
best value.(2)
The SSB in EN-DC only configuration can be manually configured to
be at the top or the bottom resource blocks. Configuring the SSB at the
[Link]
top resource blocks is preferred in EN-DC only configuration to
improve PDCCH capacity on SSB slots.(3)
[Link] true
One of the following values:
– 10
[Link]
– 15

– 20
One of the following values:
– 10
[Link]
– 15

– 20
[Link] The value set for the [Link]
attribute must be the same as the value set for the
 MO Attribute Valid Value
[Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
Values greater than 4 are not supported in ESS.
The value set for the [Link]
attribute must be the same as the value set for the
[Link]
[Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised
If the value is empty, the RF branches are selected by the system.
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised.
If the value is empty, the RF branches are selected by the system.
(1) The configuration allows for intra-frequency and inter-frequency handovers between an NR cell used in an ESS cell pair and an NR cell not used in ESS. An alternative is to
update the [Link] attribute or the [Link] attribute, and the [Link]
attribute or the [Link] attribute so that the resulting SMTC window covers the SSB of both types of NR cells.
(2) The configuration allows for intra-frequency and inter-frequency handovers between an NR cell used in an ESS cell pair and an NR cell not used in ESS. An alternative is to
update the [Link] attribute or the [Link] attribute, and the [Link]
attribute or the [Link] attribute so that the resulting SMTC window covers the SSB of both types of NR cells.
(3) If the value of the [Link] attribute is set to 0 and the NR cell bandwidth changes, the ESS cell setup might fail. The NR cell bandwidth can change, for
example, because of the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth or the LTE-NR FDD Spectrum Sharing with NB-IoT features.
If the values of the following attribute partners do not match, the Inconsistent Configuration alarm is raised:

Table 55 ESS Attribute Partners

NR LTE
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]

Related tasks
Enable Spectrum Sharing in NR Cell

[Link].5 Create Unique ESS Sector Carrier Pair ID

Each ESS cell pair requires a unique carrier pair ID.

The ESS sector carrier pair ID is used by the following MOM attributes:

– [Link]

– [Link]

Prerequisites

– Unique local IDs exist for the sector carriers on both nodes.
 Steps

1. Multiply the value of the [Link] attribute by 1010.

2. Add the value of the [Link] attribute to the product from Step 1.
Back to the Initial Configuration flow.

Related tasks
Enable Spectrum Sharing in LTE FDD Cell
Enable Spectrum Sharing in NR Cell

[Link].5.1 ESS Sector Carrier Pair ID Calculation Example

Example 4 Calculating an ESS Sector Carrier Pair ID

[Link] = 42398
[Link] = 78623

42398 × 1010 = 423980000000000

423980000000000 + 78623 = 423980000078623

Value of the ESS sector carrier pair ID: 423980000078623

[Link].6 Configure ESS Counters and KPIs

ESS-specific counters are under the SharingGroup MO class. The SharingGroup MO must be configured for the counters to create
performance information in the ESS cell pair.

Prerequisites

– The LTE-NR FDD Spectrum Sharing Enabler license key is installed.

Steps

1. Create an instance of the SpectrumSharingFunction MO under the ENodeBFunction MO.

2. Create an instance of the SharingGroup MO under the SpectrumSharingFunction MO.

The number of SharingGroup MO instances created under the SpectrumSharingFunction MO must match the number of the ESS cell
pairs. In each ESS cell pair, the configuration of each SharingGroup MO instance must contain the references to both the LTE-to-NR cell
relation and the LTE cell.

3. Set a reference in the [Link] attribute to the EUtranCellFDD MO in the ESS cell pair.

4. Set a reference in the [Link] attribute to the GUtranCellRelation MO containing a reference to

the ExternalGUtranCell MO in the ESS cell pair.
The ExternalGUtranCell MO represents the frequency of NR cell in the ESS cell pair based on the settings of the
[Link] attribute.
The GUtranCellRelation MO references the ExternalGUtranCell MO if the [Link] attribute
is configured.

5. Set the [Link] attribute to a value that is the combined names of the LTE and NR cells used in the ESS cell pair.
In this case, KPI post-processing has easier access to the counters used for KPI calculations.

Results
After unlocking both the LTE and the NR cell in the ESS cell pair that is associated with an instance of the SharingGroup MO, the counters are
ready to use in KPIs for monitoring ESS performance.

Related reference
ESS KPIs
Related Information
Back to the Initial Configuration flow.

[Link].7 Unlock ESS Cell Pair

 Unlock both the LTE and the NR cell to resume traffic and update the configuration changes.

Steps

1. Optional: Unlock the TermPointToGNB MO instance, if needed.

2. Unlock the EUtranCellFDD MO instance. The LTE cell becomes enabled after the NR cell is unlocked.

3. Optional: Unlock the NRSectorCarrier MO instance, if any changes are made to the related attribute configurations.

4. Unlock the NRCellDU MO instance.

Note: The order of the steps is only relevant when attributes are changed after initial cell setup.

Results
The values of the [Link] and the [Link] attributes change to
DEPENDENCY_LOCKED during configuration exchange. They change to DEGRADED when traffic resumes. When both cells become operational,
the values are cleared.
Note: If there is a problem with the LTE/NR ESS carrier during the unlock, when the cells already are enabled, the following values are set:

– The NR Cell and Sector Carrier becomes DISABLED/DEPENDENCY_FAILED.

– The LTE Cell (no ESS) becomes DISABLED/DEPENDENCY_FAILED.

– The LTE ESS Cell becomes DISABLED/FAILED.

– The LTE ESS Sector Carrier becomes DISABLED/OFF_LINE.

Back to the Initial Configuration flow.

[Link].8 Verify ESS Cell Configuration

Verification includes viewing alarms and KPIs related to the installed elements.

Detect possible installation faults in the following steps:

Steps

1. Check alarms. See Manage Faults for guidance on how to view alarms.

2. Lock the NR cell.

3. Check KPIs. See View KPIs on how to create a KPI monitor using ENM.

Note: In certain areas, KPI degradation can be expected due to overhead and contention, for example, throughput.
To monitor the extent of degradation, compare KPIs that are gathered when verifying software installation.

4. Unlock the NR Cell.

5. Check the same set of KPIs as in step 3.

Back to the Initial Configuration flow.

[Link] Migration from EN-DC–ESS to SA–ESS

 Initial Configuration
Migration from
EN-DC-ESS to
SA-ESS

Lock LTE and NR Cells

Activate Features

Set parameters to Recommended Values

Unlock ESS Cell Pair

Configure NR Coverage-Triggered Session Continuity

L0002941B

Figure 26 Initial Configuration Flow when Migrating from EN-DC–ESS to SA–ESS

Back to ESS Operational Flow.

[Link].1 Lock LTE and NR Cells

Lock both the LTE and the NR cell to suspend traffic and configure the general LTE and NR attributes for the ESS cell pair.

Prerequisites

– MO instances for LTE and NR cells exist:

• EUtranCellFDD MO for the LTE cell

• NRCellDU for the NR cell

Steps

1. Set the [Link] attribute to LOCKED.

Result: The value of the [Link] attribute changes to OFF_LINE.

2. Lock the EUtranCellFDD MO.

Result: The value of the [Link] attribute changes to OFF_LINE.

3. Optional: Lock the NRSectorCarrier MO, if needed.

4. Optional: Lock the TermPointToGNB MO, if needed.

Back to the Initial Configuration flow.

[Link].2 Activate Features in the Migration Scenario from EN-DC–ESS to SA–ESS

Features to be activated when migrating from EN-DC–ESS to SA–ESS. The features are activated following the usual feature activation
procedure.

Prerequisites

– The license key is installed in the node.

– All prerequisite features are operable and configured on the Baseband unit that supports both LTE and NR in a Mixed Mode
configuration.

– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

Steps

1. Set the attribute featureState to ACTIVATED in the applicable MO instance.

 Feature Name License Control MO
FeatureState=CXC4012507
FAJ 121 5257: LTE-NR FDD Spectrum
Sharing with NR Standalone

FAJ 121 5309: LTE-NR FDD Spectrum FeatureState=CXC4012543

Sharing with Policy-based Biasing

FAJ 121 5333: LTE-NR FDD Spectrum FeatureState=CXC4012554

Sharing with Downlink Data and DMRS
Multiplexing

FAJ 121 5382: LTE-NR FDD Spectrum FeatureState=CXC4012583

Sharing with Dual Outer Loop Link
Adaptation

FAJ 121 5378: LTE-NR FDD Spectrum FeatureState=CXC4012581

Sharing with Rate Matching around LTE
Synchronization Signal and PBCH

FAJ 121 5406: LTE-NR FDD Spectrum FeatureState=CXC4012595

Sharing with Tunable NR Subframes
FAJ 121 5473: LTE-NR FDD Spectrum FeatureState=CXC4012617
Sharing with QoS-Aware Relative Resource
Allocation
FAJ 121 5660: LTE-NR FDD Spectrum FeatureState=CXC4012693
Sharing with Dynamic Slot Aggregation

After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.
Back to the Initial Configuration flow.

[Link].3 Set Parameters to Recommended Values

When the LTE-NR FDD Spectrum Sharing with NR Standalone feature is used, certain parameter recommendations must be followed.

In the migration scenario from EN-DC–ESS to SA–ESS, it is recommended to adjust relevant parameters for correct functioning of the LTE-NR
FDD Spectrum Sharing with NR Standalone feature, as well as other functions, such as EN-DC–NR SA Coexistence in the Same Cell and LTE
Positioning Reference System used together with this feature.

Back to the Initial Configuration flow.

Related reference
LTE-NR FDD Spectrum Sharing with NR Standalone Impact on EN-DC–NR SA Coexistence in the Same Cell
Recommended Parameter Settings for LTE Positioning Reference System When Used with LTE-NR FDD Spectrum Sharing with NR Standalone
Recommended Parameter Settings for LTE-NR FDD Spectrum Sharing with NR Standalone

[Link].3.1 LTE-NR FDD Spectrum Sharing with NR Standalone Impact on EN-DC–NR SA Coexistence in the Same Cell

NR Cell with EN-DC–NR SA Coexistence Used in ESS

If the [Link] attribute is set to false for the NR cell in the ESS cell pair, the NR cell can serve both EN-DC-capable
and NR standalone-capable UEs that support ESS. This way, an EN-DC-capable UE is anchored in the LTE network, and can connect to NR
after Secondary Node Addition. In addition, the NR standalone-capable UE can perform registration in the same NR cell. However, in ESS,
when the feature is used, scheduling must consider the difference in NR resources between the deployment options of the same NR cell.

Table 56 Transmission in an NR Cell in Different Configuration Options Used for ESS

 NR Cell Configured for EN-DC Used in ESS NR Cell Configured for NR Standalone Used
in ESS
SSB/PBCH Yes Yes
SIB1 No Yes
Other System Information No Yes
Random Access Msg2 Yes Yes
Random Access Msg4 No Yes
Paging No Yes
SRB No Yes

CORESET#0 in ESS Scheduling

CORESET#0 is used in NR random access both for EN-DC-capable and NR standalone-capable UEs. The placement of CORESET#0 is
predefined and occupies particular resources that scheduling must consider in an NR standalone cell or in an NR cell with EN-DC–NR SA
coexistence used in an ESS cell pair.
The NR standalone-capable UE receives the following information transmitted in CORESET#0:

– SIB1, scheduled by PDCCH, is used only by NR standalone-capable UEs to acquire access information on the NR cell.

– Other system information that the NR standalone-capable UEs use for idle mode mobility.

– Random Access Msg2 is the Random Access Response message the Baseband Radio Node with mixed mode configuration sends to the
UE on PDSCH.

– Random Access Msg4 is the Contention Resolution message to complete the random access procedure. It carries the RRCSetup
message the Baseband Radio Node with mixed mode configuration uses to establish RRC connection with the NR standalone-capable
UE. The message involves UE configuration for SRB1 establishment.

– Paging messages are required for the NR standalone-capable UE to establish NAS signaling and user plane resources.

For more information on CORESET#0, SIB1, and other system information used in an NR standalone cell, see Manage Radio Network NR.
For more information on random access, paging, and SRBs in NR standalone, see NR Standalone.

MBSFN Subframe Configuration for NR Standalone Signaling

The MBSFN subframe settings that are required in the NR cell configured for NR standalone also apply if the same cell is used for EN-DC.
When used for NR standalone, the specific MBSFN subframe settings specific to NR standalone for the cell must not be changed.

[Link].3.2 Recommended Parameter Settings for LTE Positioning Reference System When Used with LTE-NR FDD Spectrum Sharing
with NR Standalone

Certain parameters must be adjusted for an LTE cell in an ESS cell pair that has the LTE Positioning Reference System features activated
and the recommended MBSFN configuration applied for NR standalone resources.

Recommended LTE PRS Configuration for ESS

MO Attribute Value Description
The recommended parameter values ensure
that the subframe positions allocated for LTE
[Link] 11 PRS do not collide with MBSFN subframes
configured for the NR standalone cell used in
an ESS cell pair.
If the LTE PRS configuration results in a
collision between PRS subframes and
[Link] SF1 MBSFN subframes, the ESS Inconsistent
Configuration alarm is raised when the
LTE cell used in the ESS cell pair is unlocked.

MBSFN Subframes to Consider When Configuring LTE PRS Subframes

[Link] Subframes Used for MBSFN in a 40- Description
Subframe Pattern
The [Link]
SA_BASIC 1, 6, 21, 22, 26
attribute has a recommended value. If another
value needs to be used in ESS, it must be
SA_SIB_ROBUST_15_PERCENT 1, 6, 21, 22, 23, 26 configured to avoid collision with the MBSFN
subframe position set in the
NSA_BASIC(1) 1, 2, 21
 [Link] Subframes Used for MBSFN in a 40- Description
Subframe Pattern
[Link]
(1) This MBSFN configuration is only used when the NR cell in the ESS cell pair is used in EN-DC configuration.
attribute.

[Link].3.3 Recommended Parameter Settings for LTE-NR FDD Spectrum Sharing with NR Standalone

Certain parameters must be set to the recommended values for an NR cell when used in ESS with the LTE-NR FDD Spectrum Sharing with
NR Standalone feature activated.

MO Attribute Value Description

The attribute is required to be set to 20 if the NR cell is used in
[Link] 20
an ESS cell pair.
Five MBSFN subframes are allocated to LTE for NR signaling to
[Link] SA_BASIC ensure that SIB1 and other system information are scheduled in
MBSFN subframes.
If the attribute is set to false, the NR cell starts broadcasting
SIB1 and other system information.
The configured value is checked together with the LTE-NR FDD
Spectrum Sharing with NR Standalone feature license. If the
attribute is set to false and the feature license is not installed,
not activated, or expired (the [Link]
attribute is set to INOPERABLE), the NR cell in the ESS cell pair
has the following attribute values when unlocked:
– The [Link] attribute is set
to FAILED.

– The [Link] attribute is set to

[Link] false DISABLED.

– The [Link] attribute is set to

OUT_OF_SERVICE.
In addition, the following alarms are raised on the NR cell:
– The MO Configuration Requires Key Install
and Feature Activation alarm is raised when the
feature license is not installed.

– The Configuration Requires Feature

Activation alarm is raised when the feature is not
activated or expired.

The siPeriodicity member of the 64 for the following

following attributes: parameters:

– NRCellDU.sibType2 – NRCellDU.sibType2

– NRCellDU.sibType4 – NRCellDU.sibType4 The configuration value ensures that the appropriate number of

– NRCellDU.sibType5 – NRCellDU.sibType5 radio frames is set for the periodicity of the other system
information.
– NRCellDU.sibType6 – NRCellDU.sibType7 SIB9 can be transmitted with other SIBs if the siPeriodicity
member has the same value.
– NRCellDU.sibType7 – NRCellDU.sibType8

– NRCellDU.sibType8 – NRCellDU.sibType9
32 for
– NRCellDU.sibType9
NRCellDU.sibType6
The configuration value ensures that the scheduling window is
[Link] 80
appropriate for transmitting the other system information.
The SSB in NR standalone configuration must be configured to
be at the bottom resource blocks to improve the following:

[Link] Other than 0 – PDCCH capacity on SSB slots

– Resource sharing between LTE and NR in non-SSB slots

(1)

The only acceptable configuration values for the number of

[Link] 1 or 2 paging occasions in a paging frame when the LTE-NR FDD
Spectrum Sharing with NR Standalone feature activated.
 (1) If the value of the [Link] attribute is set to 0 and the NR cell bandwidth changes, the ESS cell setup might fail. The NR cell bandwidth can change, for
example, because of the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth or the LTE-NR FDD Spectrum Sharing with NB-IoT features.

[Link].4 Unlock ESS Cell Pair

Unlock both the LTE and the NR cell to resume traffic and update the configuration changes.

Steps

1. Optional: Unlock the TermPointToGNB MO instance, if needed.

2. Unlock the EUtranCellFDD MO instance. The LTE cell becomes enabled after the NR cell is unlocked.

3. Optional: Unlock the NRSectorCarrier MO instance, if any changes are made to the related attribute configurations.

4. Unlock the NRCellDU MO instance.

Note: The order of the steps is only relevant when attributes are changed after initial cell setup.

Results
The values of the [Link] and the [Link] attributes change to
DEPENDENCY_LOCKED during configuration exchange. They change to DEGRADED when traffic resumes. When both cells become operational,
the values are cleared.
Note: If there is a problem with the LTE/NR ESS carrier during the unlock, when the cells already are enabled, the following values are set:

– The NR Cell and Sector Carrier becomes DISABLED/DEPENDENCY_FAILED.

– The LTE Cell (no ESS) becomes DISABLED/DEPENDENCY_FAILED.

– The LTE ESS Cell becomes DISABLED/FAILED.

– The LTE ESS Sector Carrier becomes DISABLED/OFF_LINE.

Back to the Initial Configuration flow.

[Link].5 Configure NR Coverage-Triggered Session Continuity

If an NR standalone capable UE that does not support ESS fails the UE capability check, it is released and redirected blindly to an LTE
frequency. If the NR Coverage-Triggered NR Session Continuity is activated on the Baseband Radio Node with Mixed Mode configuration, the
UE can immediately be transferred back to an NR frequency based on a B1 measurement report.

Steps

To avoid redirecting the UE back and forth between LTE and NR frequencies, configure the NR Coverage-Triggered NR Session Continuity
feature:

1. Set the following attributes to a lower value than they are set for an external NR cell not used in ESS:

– [Link]

– [Link]

2. Set the following attributes to a higher value than they are set for an external NR cell not used in ESS:

– ReportConfigB1NR.b1ThresholdRsrp

– ReportConfigB1NR.b1ThresholdRsrq

3. Increase the value of the [Link] attribute. This delays the B1 measurement that triggers the
immediate transfer of the UE back to an NR frequency.
Back to the Initial Configuration flow.

[Link] Migration from LTE to SA–ESS

 Initial Configuration
Migration from
LTE to SA-ESS

Lock LTE and NR Cells

Activate Features

Enable Spectrum Sharing in LTE FDD Cell

Enable Spectrum Sharing in NR Cell

Create Unique ESS Sector Carrier Pair ID

Unlock ESS Cell Pair

Configure NR Coverage-Triggered Session Continuity

Verify ESS Cell Configuration

L0002942A

Figure 27 Initial Configuration Flow when Migrating from LTE to SA–ESS

Back to ESS Operational Flow.

[Link].1 Lock LTE and NR Cells

Lock both the LTE and the NR cell to suspend traffic and configure the general LTE and NR attributes for the ESS cell pair.

Prerequisites

– MO instances for LTE and NR cells exist:

• EUtranCellFDD MO for the LTE cell

• NRCellDU for the NR cell

Steps

1. Set the [Link] attribute to LOCKED.

Result: The value of the [Link] attribute changes to OFF_LINE.

2. Lock the EUtranCellFDD MO.

Result: The value of the [Link] attribute changes to OFF_LINE.

3. Optional: Lock the NRSectorCarrier MO, if needed.

4. Optional: Lock the TermPointToGNB MO, if needed.

Back to the Initial Configuration flow.

[Link].2 Activate Features in the Migration Scenario from LTE to SA–ESS

Features to be activated when migrating from LTE to SA–ESS. The features are activated following the usual feature activation procedure.

Prerequisites

– The license key is installed in the node.

–
 All the prerequisite features are operable and configured on the Baseband unit that supports both LTE and NR in a Mixed Mode
configuration.

– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

Steps

1. Set the attribute featureState to ACTIVATED in the applicable MO instance.

Feature Name License Control MO

FeatureState=CXC4012507
FAJ 121 5257: LTE-NR FDD Spectrum
Sharing with NR Standalone

FAJ 121 5309: LTE-NR FDD Spectrum FeatureState=CXC4012543

Sharing with Policy-based Biasing

FAJ 121 5333: LTE-NR FDD Spectrum FeatureState=CXC4012554

Sharing with Downlink Data and DMRS
Multiplexing

FAJ 121 5306: LTE-NR FDD Spectrum FeatureState=CXC4012540

Sharing with NB-IoT

FAJ 121 5228: LTE-NR FDD Spectrum FeatureState=CXC4012528

Sharing with Flexible Channel Bandwidth

FAJ 121 5382: LTE-NR FDD Spectrum FeatureState=CXC4012583

Sharing with Dual Outer Loop Link
Adaptation

FAJ 121 5301: LTE-NR FDD Spectrum FeatureState=CXC4012537

Sharing with Category M

FAJ 121 5378: LTE-NR FDD Spectrum FeatureState=CXC4012581

Sharing with Rate Matching around LTE
Synchronization Signal and PBCH

FAJ 121 5406: LTE-NR FDD Spectrum FeatureState=CXC4012595

Sharing with Tunable NR Subframes
FAJ 121 5473: LTE-NR FDD Spectrum FeatureState=CXC4012617
Sharing with QoS-Aware Relative Resource
Allocation
FAJ 121 5660: LTE-NR FDD Spectrum FeatureState=CXC4012693
Sharing with Dynamic Slot Aggregation

After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.
Back to the Initial Configuration flow.

[Link].3 Enable Spectrum Sharing in LTE FDD Cell

Enable spectrum sharing by configuring the LTE cell and setting up a corresponding NR cell relation.

Prerequisites
 – The EUtranCellFDD MO instance to be used for spectrum sharing is locked.

– The NRCellDU MO instance to be paired with the LTE cell is identified.

– An ExternalGNodeBFunction MO instance that represents the gNodeB with the partner NR cell, and a corresponding
TermPointToGNB MO instance exist.

– A GUtranFreqRelation MO instance exists.

Steps

1. Create an ExternalGUtranCell MO instance and configure the following attributes to match the configuration of the partner NR cell:

– [Link]

– [Link]

– [Link]

2. Create a GUtranCellRelation MO instance and configure it as follows:

Table 57 Configuration Values of GUtranCellRelation for Spectrum Sharing

Attribute Value
[Link] true
[Link] false
A reference to the ExternalGUtranCell instance created
[Link]
in Step 1

3. Create a SectorCarrier MO instance and configure it as follows:

Table 58 Configuration Values of SectorCarrier for Spectrum Sharing

Attribute Value
A unique, non-zero value that is the same as the value of the
[Link]
corresponding [Link]
[Link] A unique value identifying the eNodeB sector carrier

4. Add the SectorCarrier MO instance created in Step 2 to the [Link] attribute as reference.

After This Task

Check the parameter values against the checklist for LTE cells.
Back to the Initial Configuration flow.
Related reference
ESS Parameter Checklist for LTE Cells

[Link].3.1 ESS Parameter Checklist for LTE Cells

The list of valid parameter values is used to check the compliance of LTE cells with ESS requirements.

For parameter recommendations, see LTE RAN Parameter Recommendations Lists.

Table 59 Valid LTE Parameter Settings for LTE-NR FDD Spectrum Sharing Enabler

MO Attribute Valid Value

[Link] Larger than PSF3(1)
[Link] true
MO Attribute Valid Value
Supported PRACH formats in ESS are configured by using the
following values:
– For Format 0, the attribute value must be less than 15 with the
[Link] attribute set
[Link] to false.

– For Format 1, attribute value must be greater than 15 with the

[Link] attribute set
to false. This configuration is only applicable if the Maximum
Cell Range is activated for the LTE cell.

[Link] false(2)
[Link] 0 or 1(3)
[Link] 0
One of the following values:
– 10000
[Link]
– 15000

– 20000
[Link] 0
[Link] true(4)
[Link] 11(6)(5)
[Link] SF1(6)
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised.
If the value is empty, the RF branches are selected by the system.
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised.
If the value is empty, the RF branches are selected by the system.
One of the following values:
– 10000
[Link]
– 15000

– 20000
[Link] 0
[Link] Any value in the range of 0–29
[Link] false
One of the following values:
– TRANSMISSION_MODE_3

– TRANSMISSION_MODE_4
[Link]
– TRANSMISSION_MODE_9
Note: If the value of TRANSMISSION_MODE_9 is used, the
[Link] attribute must
be set to NZP_ZP_CSIRS.

[Link] false
[Link] false
[Link] SAME_MBSFN_SUBFRAMES(7)
 MO Attribute Valid Value
GUtranFreqRelation.endcB1MeasPriority -1(8)
The value set for the [Link] attribute
must be the same as the value set for the
[Link] [Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
Values greater than 4 are not supported in ESS.
The value set for the [Link] attribute
must be the same as the value set for
[Link]
[Link].
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
When the LTE-NR FDD Spectrum Sharing with Policy-based Biasing
[Link] feature (FAJ 121 5309) is activated, all values are possible to
configure, depending on prioritized RAT preference.
(1) When set, the value must apply to all QCIs. For this reason, the [Link]=18 DRX profile is used for bearer-level QCI configuration.
(2) The attribute is used with the [Link] attribute to configure PRACH format in the LTE cell.
(3) If PRACH success rate on the NR side shows degradation, the value of the attribute can be changed to 0. This way, the neighbor cell interference between PRACH and Random
Access Msg3 can be minimized.
(4) This is needed to enable PRS consistency check on ESS EutranCellFDD MO.
(5) If another than the recommended value needs to be used in ESS, the configuration must consider MBSFN subframe positions. These are 1, 2, and 21 in a 40-subframe pattern.
(6) The recommended parameter value ensures that the subframe positions allocated for LTE PRS do not collide with the MBSFN subframes in ESS.
(7) The attribute value indicates that the handover source and target LTE cells must have the same MBSFN subframe allocation if both cells are used in ESS.
SAME_MBSFN_SUBFRAMES can generally be used if most of the LTE cells are ESS cells.
(8) EN-DC is not considered for the NR cell on the same frequency with the LTE cell when used in ESS. This is needed only in the GUtranFreqRelation MO between LTE ESS
and NR ESS of the same ESS pair.
If the values of the following attribute partners do not match, the Inconsistent Configuration alarm is raised:

Table 60 ESS Attribute Partners

LTE NR
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]

[Link].4 Enable Spectrum Sharing in NR Cell

Enable spectrum sharing by configuring the NR cell and setting up a corresponding LTE cell relation.

Prerequisites

– An ExternalENodeBFunction MO instance representing the eNodeB with the partner E-UTRAN cell exists.

Steps

1. Create an ExternalEUtranCell MO instance and configure the [Link] attribute to match the
configuration of the partner LTE cell.

2. Create an EUtranCellRelation MO instance and configure it as follows:

Table 61 Configuration Values of EUtranCellRelation for Spectrum Sharing

Attribute Value
[Link] true
A reference to the ExternalEUtranCell instance created
[Link]
in Step 1
 3. Create an NRSectorCarrier MO instance and configure it as follows:

Table 62 Configuration values of NRSectorCarrier for Spectrum Sharing

Attribute Value
A unique, non-zero value that is the same as the
[Link]
corresponding [Link]
[Link] A unique value identifying the gNodeB sector carrier

4. Add the NRSectorCarrier MO instance created in Step 2 to the [Link] attribute as reference.

After This Task

Check the parameter values against the checklist for NR cells.
Back to the Initial Configuration flow.
Related reference
ESS Parameter Checklist for NR Cells

[Link].4.1 ESS Parameter Checklist for NR Cells

The list of valid parameter values can be used to check the compliance of NR cells with ESS requirements.

For parameter recommendations, see NR RAN Parameter Recommendations Lists.

Table 63 ESS Parameter Settings for NR Cells

MO attribute Valid value

[Link] 40
[Link] 0
[Link] DEACTIVATED
One of the following values:
– START_LOWER_EDGE
[Link]
– START_HIGHER_EDGE

– RANDOM_START_LOWER_OR_HIGHER
[Link] Equal to or greater than ONDURATIONTIMER_6MS.
[Link] 0(1)
[Link] 20
[Link] 15
[Link] 15
The parameter must be left empty so that the system can choose the
[Link]
best value.(2)
The SSB in NR standalone configuration must be configured to be at
the bottom resource blocks to improve the following:

[Link] – PDCCH capacity on SSB slots

– Resource sharing between LTE and NR in non-SSB slots

(3)

[Link] false
One of the following values:
– 10
[Link]
– 15

– 20
One of the following values:
– 10
[Link]
– 15

– 20
 MO attribute Valid value
The value set for the [Link]
attribute must be the same as the value set for the
[Link] [Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
Values greater than 4 are not supported in ESS.
The value set for the [Link]
attribute must be the same as the value set for the
[Link]
[Link] attribute.
If the values do not match, the cells and sector carriers are realized by
the lowest configuration, and might be degraded with alarms.
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised
If the value is empty, the RF branches are selected by the system.
References to the RfBranch MO instances for triggering deterministic
carrier allocation.
The [Link] attribute must have the
[Link] same value as the [Link] attribute. If
the values do not match, the cell and sector carrier are disabled and
alarms are raised.
If the value is empty, the RF branches are selected by the system.
(1) The configuration allows for intra-frequency and inter-frequency handovers between an NR cell used in an ESS cell pair and an NR cell not used in ESS. An alternative is to
update the [Link] attribute or the [Link] attribute, and the of the
[Link] attribute or the [Link] attribute so that the resulting SMTC window covers the SSB of both types of
NR cells.
(2) The configuration allows for intra-frequency and inter-frequency handovers between an NR cell used in an ESS cell pair and an NR cell not used in ESS. An alternative is to
update the [Link] attribute or the [Link] attribute, and the of the
[Link] attribute or the [Link] attribute so that the resulting SMTC window covers the SSB of both types of
NR cells.
(3) If the value of the [Link] attribute is set to 0 and the NR cell bandwidth changes, the ESS cell setup might fail. The NR cell bandwidth can change, for
example, because of the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth or the LTE-NR FDD Spectrum Sharing with NB-IoT features.
If the values of the following attribute partners do not match, the Inconsistent Configuration alarm is raised:

Table 64 ESS Attribute Partners

NR LTE
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]
[Link] [Link]

[Link].5 Create Unique ESS Sector Carrier Pair ID

Each ESS cell pair requires a unique carrier pair ID.

The ESS sector carrier pair ID is used by the following MO attributes:

– [Link]

– [Link]

Prerequisites

– Unique local IDs exist for the sector carriers on both nodes.
 Steps

1. Multiply the value of the [Link] attribute by 1010.

2. Add the value of the [Link] attribute to the product from Step 1
Back to the Initial Configuration flow.

Related tasks
Enable Spectrum Sharing in LTE FDD Cell
Enable Spectrum Sharing in NR Cell

[Link].5.1 ESS Sector Carrier Pair ID Calculation Example

Example 5 Calculating an ESS Sector Carrier Pair ID

[Link] = 42398
[Link] = 78623

42398 × 1010 = 423980000000000

423980000000000 + 78623 = 423980000078623

Value of the ESS sector carrier pair ID: 423980000078623

[Link].6 Configure ESS Counters and KPIs

ESS-specific counters are under the SharingGroup MO class. The SharingGroup MO must be configured for the counters to create
performance information in the ESS cell pair.

Prerequisites

– The LTE-NR FDD Spectrum Sharing Enabler license key is installed.

Steps

1. Create an instance of the SpectrumSharingFunction MO under the ENodeBFunction MO.

2. Create an instance of the SharingGroup MO under the SpectrumSharingFunction MO.

The number of SharingGroup MO instances created under the SpectrumSharingFunction MO must match the number of the ESS cell
pairs. In each ESS cell pair, the configuration of each SharingGroup MO instance must contain the references to both the LTE-to-NR cell
relation and the LTE cell.

3. Set a reference in the [Link] attribute to the EUtranCellFDD MO in the ESS cell pair.

4. Set a reference in the [Link] attribute to the GUtranCellRelation MO containing a reference to

the ExternalGUtranCell MO in the ESS cell pair.
The ExternalGUtranCell MO represents the frequency of NR cell in the ESS cell pair based on the settings of the
[Link] attribute.
The GUtranCellRelation MO references the ExternalGUtranCell MO if the [Link] attribute
is configured.

5. Set the [Link] attribute to a value that is the combined names of the LTE and NR cells used in the ESS cell pair.
In this case, KPI post-processing has easier access to the counters used for KPI calculations.

Results
After unlocking both the LTE and the NR cell in the ESS cell pair that is associated with an instance of the SharingGroup MO, the counters are
ready to use in KPIs for monitoring ESS performance.

Related reference
ESS KPIs
Related Information
Back to the Initial Configuration flow.

[Link].7 Unlock ESS Cell Pair

 Unlock both the LTE and the NR cell to resume traffic and update the configuration changes.

Steps

1. Optional: Unlock the TermPointToGNB MO instance, if needed.

2. Unlock the EUtranCellFDD MO instance. The LTE cell becomes enabled after the NR cell is unlocked.

3. Optional: Unlock the NRSectorCarrier MO instance, if any changes are made to the related attribute configurations.

4. Unlock the NRCellDU MO instance.

Note: The order of the steps is only relevant when attributes are changed after initial cell setup.

Results
The values of the [Link] and the [Link] attributes change to
DEPENDENCY_LOCKED during configuration exchange. They change to DEGRADED when traffic resumes. When both cells become operational,
the values are cleared.
Note: If there is a problem with the LTE/NR ESS carrier during the unlock, when the cells already are enabled, the following values are set:

– The NR Cell and Sector Carrier becomes DISABLED/DEPENDENCY_FAILED.

– The LTE Cell (no ESS) becomes DISABLED/DEPENDENCY_FAILED.

– The LTE ESS Cell becomes DISABLED/FAILED.

– The LTE ESS Sector Carrier becomes DISABLED/OFF_LINE.

Back to the Initial Configuration flow.

[Link].8 Configure NR Coverage-Triggered Session Continuity

If an NR standalone capable UE that does not support ESS fails the UE capability check, it is released and redirected blindly to an LTE
frequency. If the NR Coverage-Triggered NR Session Continuity is activated on the Baseband Radio Node with Mixed Mode configuration, the
UE can immediately be transferred back to an NR frequency based on a B1 measurement report.

Steps

To avoid redirecting the UE back and forth between LTE and NR frequencies, configure the NR Coverage-Triggered NR Session Continuity
feature:

1. Set set the following attributes to a lower value than they are set for an external NR cell not used in ESS:

– [Link]

– [Link]

2. Set the following attributes to a higher value than they are set for an external NR cell not used in ESS:

– ReportConfigB1NR.b1ThresholdRsrp

– ReportConfigB1NR.b1ThresholdRsrq

3. Increase the value of the [Link] attribute. This delays the B1 measurement that triggers the
immediate transfer of the UE back to an NR frequency.
Back to the Initial Configuration flow.

[Link].9 Verify ESS Cell Configuration

Verification includes viewing alarms and KPIs related to the installed elements.

Detect possible installation faults in the following steps::

Steps

1. Check alarms. See Manage Faults for guidance on how to view alarms.

2. Lock NR cell.

3. Check KPIs. See View KPIs on how to create a KPI monitor using ENM.
 Note: In certain areas, KPI degradation can be expected due to overhead and contention, for example throughput.
To monitor the extent of degradation, compare KPIs that were gathered when verifying software installation.

4. Unlock the NR cell.

5. Check the same set of KPIs as in step 3.

Back to the Initial Configuration flow.

3.2 Optimize
Optimization part of the ESS migration involves setting feature-specific parameters to recommended values to enable their proper
functioning and coexistence after the initial configuration phase.

Perform the relevant procedure to optimize the functioning of ESS-specific and related features depending on the chosen migration scenario
for ESS.

Back to ESS Operational Flow.

If load balancing is needed due to resource shortage on the links, follow the instructions in the following documents:

– Basic Load Management

– Manage Mobility

– Preferential Traffic Management Guidelines

Related concepts
SINR Threshold Configuration to Avoid Throughput Degradation
O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M
Configure LTE-NR FDD Spectrum Sharing with NB-IoT
Related tasks
Configure Flexible Channel Bandwidth for ESS
Configure MBSFN Subframes for LTE-NR FDD Spectrum Sharing with NR Standalone
Configure Policy-Based Biasing
Enable or Disable the Multiplexing of PDSCH and DMRS Manually

3.2.1 Configure Flexible Channel Bandwidth for ESS

LTE and NR must be configured to block the same frequency range to enable the LTE-NR FDD Spectrum Sharing with Flexible Channel
Bandwidth feature.

Prerequisites
The NR PDCCH Link Adaptation functionality is needed for configuring NR common resource block blanking. For more information, see
Physical Layer Mid-Band.

Steps

1. Check the LTE Flexible Channel Bandwidth configuration. The same frequency range must be blocked on both LTE and NR to enable the
LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature.

Note: For more information about configuring LTE Flexible Channel Bandwidth, see Flexible Channel Bandwidth.

2. Set the [Link] attribute to LOCKED.

3. Set the [Link] attribute to LOCKED.

4. Set the value of the following attributes to configure ESS-compatible common resource block blanking for LTE:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]
 – [Link]

Note: If uplink blanking is applied, the [Link] attribute might not reflect the actual position of
the LTE PUCCH.

5. Set the value of the following attributes to configure ESS-compatible common resource block blanking for NR:

– [Link]

– [Link]

– [Link]

– [Link]

In the 10 MHz configuration, LTE has 50 resource blocks, and NR has 52 resource blocks. Because of this, one extra blanked resource block
is available for NR, either on the top or the bottom blanking configuration, compared to LTE.
In the 15 MHz configuration, LTE has 75 resource blocks, and NR has 79 resource blocks. Because of this, two extra blanked resource blocks
are available for NR, either on the top or the bottom blanking configuration, compared to LTE.
In the 20 MHz configuration, LTE has 100 resource blocks, and NR has 106 resource blocks. Because of this, three extra blanked resource
blocks are available for NR, either on the top or the bottom blanking configuration, compared to LTE.
For examples of the blanking configurations, see Blanking Configuration Examples for LTE-NR FDD Spectrum Sharing with Flexible
Channel Bandwidth.

Note: If the [Link] and the [Link] attributes are configured and the feature license is
not installed, not activated, or expired (the [Link] attribute is set to INOPERABLE), the NR cell in the ESS
cell pair has the following attribute values when unlocked:

– [Link] is set to FAILED.

– [Link] is set to DISABLED.

– [Link] is set to OUT_OF_SERVICE.

In addition, the alarms are raised on the following NR cell:

– MO Configuration Requires Key Install and Feature Activation

– Configuration Requires Feature Activation

6. Set the value of the [Link] attribute to configure TRS bandwidth.

7. Set the [Link] to UNLOCKED.

8. Set the [Link] to UNLOCKED.

[Link] Blanking Configuration Examples for LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth

The configuration of the PRB blanking on LTE side, and the CRB blanking on the NR side must be compatible for ESS cells.

Example 6 Blanking Configuration for LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth for 11 LTE PRBs

PRBs Blanked Recommended Configuration

11 LTE PRBs at top of 10-MHz spectrum
– [Link]=0

– [Link]=78

– [Link]=false

– [Link]=11

– [Link]=0

– [Link]=78

– [Link]=false

– [Link]=40

– [Link]=0

– [Link]=40
PRBs Blanked Recommended Configuration
– [Link]=0

Example 7 Blanking Configuration for LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth for 15 LTE PRBs

PRBs Blanked Configuration

– [Link]=31

– [Link]=70

– [Link]=false

– [Link]=15

– [Link]=31

– [Link]=70

– [Link]=false

15 LTE PRBs at bottom of 10-MHz spectrum – [Link]=36

– [Link]=16

– [Link]=0
Note: Setting the [Link] attribute to
0 is necessary because of the large size of the blanked
region in this example.
The [Link] attribute must be
set to 0 or 1 when using this configuration.

– [Link]=36

– [Link]=16

Example 8 Blanking Configuration for LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth for 7 LTE PRBs

PRBs Blanked Configuration

– [Link]=6

– [Link]=91

– [Link]=false

– [Link]=4

– [Link]=6
3 LTE PRBs at the top and 4 LTE PRBs at the bottom of a 15-MHz
spectrum – [Link]=91

– [Link]=false

– [Link]=68

– [Link]=5

– [Link]=68

– [Link]=5

Example 9 Blanking Configuration for LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth for 4 LTE PRBs

PRBs Blanked Configuration

4 LTE PRBs at the bottom of a 20-MHz spectrum
– [Link]=4

– [Link]=96
 PRBs Blanked Configuration
– [Link]=false

– [Link]=5

– [Link]=5

– [Link]=96

– [Link]=false

– [Link]=100

– [Link]=6

– [Link]=100

– [Link]=6

Example 10 Blanking Configuration for LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth for 2 NR CRBs at the Top and 2 NR
CRBs at the Bottom, without LTE PRB Blanking

PRBs Blanked Configuration

– [Link]=0

– [Link]=100

– [Link]=false

– [Link]=0

– [Link]=0
2 NR CRBs at the top and 2 NR CRBs at the bottom of a 15-MHz
spectrum – [Link]=100

– [Link]=false

– [Link]=75

– [Link]=2

– [Link]=75

– [Link]=2

3.2.2 MBSFN Subframe Configuration

MBSFN subframes can be configured to align the NR signals and mitigate LTE interference in an ESS cell pair.

No LTE resources are scheduled in downlink in the configured MBSFN subframes. This allows the NR-specific signals deployed in an NR
standalone configuration (SIB1 and other system information) to occupy those subframes. These specific NR resources are not present if the
NR cell in the ESS cell pair is used in EN-DC. However, the configured proportion of MBSFN subframes can be set to be specific to EN-DC, NR
standalone, or cover both types of NR cell configurations.

Additional MBSFN subframes can be configured as dedicated resources for NR traffic to increase the NR downlink throughput. In addition, LTE
CRS interference from neighbor cells can be reduced.

The [Link] attribute can be set to a feature-specific value in the NR cell of the ESS cell pair. However, for
the configuration to take effect, the ESS cell pair must be first locked and then unlocked. This must be done every time the setting of the
attribute is changed.

The [Link] attribute is introduced to provide information about the exact position of the configured
MBSFN subframes.

The supported configuration options consider MBSFN subframes in a 40-subframe pattern.

The following MBSFN subframe configurations are recommended:

– The MBSFN percentage is set to a smaller value than the average NR PRB utilization to not waste PRBs in MBSFN subframes, for
example, to 10%.
 – The MSBFN percentage is set to a value smaller than 55% if Category M1 UEs must be supported.

– The [Link] attribute is set to FAIR if unbiased resource assignation is required for the following reasons:

• If the [Link] attribute is set to LTE_BIASED, the number of NR-prioritized subframes decreases. In specific
MBSFN configuration cases, the MBSFN percentage is higher within NR prioritized subframes, therefore, more NR traffic is scheduled
in MBSFN. The setting limits NR throughput if LTE traffic load is high.

• If the [Link] attribute is set to NR_BIASED, the number of NR prioritized subframes increases. In specific
MBSFN configuration cases, the MBSFN percentage is lower within the NR prioritized subframes, therefore, MBSFN subframes might
be underutilized.

MBSFN percentage configuration must be determined based on NR and LTE downlink traffic types and load.

For the calculation of PRB utilization in ESS cells, see ESS KPIs.
Note: The PRB utilization calculations refer to the average PRB utilization in a ROP period.

The NR PRB utilization distribution in MBSFN subframes can be obtained from the [Link] PM
counter. The counter can be used to calculate the percentage of the MBSFN subframes in which the NR PRB utilization is below or above a
specific value. The calculation is designated as UNRDist. The percentage of MBSFN subframes in which the NR PRB utilization is below or
exceeds a certain value can be expressed as P(UNRDist < A) and P(UNRDist > A), where A is the chosen specific value.

Calculating the PRB utilization with the [Link] attribute can give inaccurate results, as the
attribute counts the subframes that contain a certain number of RBGs used by NR. However, the last RBG might contain fewer resource blocks
than other RBGs.

Example 11 Miscalculation of PRB Utilization

If the nominal RBG size is eight for a 20-MHz bandwidth, all RBGs contain eight resource blocks, except for the last RBG, which has only two
resource blocks. If three RBGs are used, the number of resource blocks used can be 18 or 24.

Related concepts
FAJ 121 5147: LTE-NR FDD Spectrum Sharing Enabler
FAJ 121 5257: LTE-NR FDD Spectrum Sharing with NR Standalone
FAJ 121 5406: LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

[Link] MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing Enabler

MBSFN subframes can be configured for the LTE-NR FDD Spectrum Sharing Enabler feature to align the NR signals and mitigate LTE
interference in an ESS cell pair.

Table 65 Supported MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing Enabler

NR Cell [Link] [Link] Description Subframes Used

Configuration Value Value for MBSFN in a
Option 40-Subframe
Pattern
Three MBSFN
subframes are
EN-DC only true NSA_BASIC 1, 2, 21
allocated to NR
resources.

Related concepts
FAJ 121 5147: LTE-NR FDD Spectrum Sharing Enabler
O&M Aspects of LTE-NR FDD Spectrum Sharing Enabler

[Link] MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing with NR Standalone

MBSFN subframes can be configured for the LTE-NR FDD Spectrum Sharing with NR Standalone feature to align the NR signals and
mitigate LTE interference in an ESS cell pair.

Table 66 Supported MBSFN Subframe Configurations for LTE-NR FDD Spectrum Sharing with NR Standalone
 NR Cell [Link] [Link] Description Subframes Used
Configuration Value Value for MBSFN in a
Option 40-Subframe
Pattern
Recommended
configuration for
LTE to consider NR
standalone
resources in the NR
cell.
Five MBSFN
NR standalone only, subframes are
and NR standalone false SA_BASIC allocated to NR 1, 6, 21, 22, 26
EN-DC coexistence resources. Ensures
that SIB1 and other
system information,
transmitted only in
an NR standalone
cell, are scheduled
in MBSFN
subframes.
Possible alternative
configuration for
LTE to consider NR
standalone
resources in the NR
cell.
Six MBSFN
NR standalone only, subframes are
and NR standalone false SA_SIB_ROBUST_15_PERCENT allocated to NR 1, 6, 21, 22, 23, 26
EN-DC coexistence resources. Ensures
that SIB1 and Other
System Information,
transmitted only in
an NR standalone
cell, are scheduled
in MBSFN
subframes.

With the recommended MBSFN subframe configuration set for NR standalone, that is, SA_BASIC, SIB1 can show performance degradation.
With the alternative MBSFN subframe configuration, that is, SA_SIB_ROBUST_15_PERCENT, no such degradation is expected. However, the
larger number of MBSFN subframes for NR standalone requires additional resources unavailable to LTE. Therefore, such a configuration results
in slightly reduced LTE throughput in downlink.
Related concepts
FAJ 121 5257: LTE-NR FDD Spectrum Sharing with NR Standalone
O&M Aspects of LTE-NR FDD Spectrum Sharing with NR Standalone

[Link].1 Configure MBSFN Subframes for LTE-NR FDD Spectrum Sharing with NR Standalone

The procedure only applies when migrating from EN-DC–ESS to SA–ESS and from LTE to SA–ESS.
If the feature is used, specific MBSFN subframe allocation has to be configured. This is necessary to align the scheduling of LTE resources with
NR resources in an NR cell that is deployed in an NR SA configuration.

Prerequisites

– LTE-NR cell pairs are configured in cell relations for ESS.

– The LTE-NR FDD Spectrum Sharing with NR Standalone feature is activated on the gNodeB.

– The NRCellDU MO instances used in ESS cell pairs have the following settings:

• The [Link] attribute is set to LOCKED.

• The [Link] attribute is set to false.

Steps

1. Set the [Link] attribute to SA_BASIC.

 2. Set the [Link] attribute to 80.

3. Set the siPeriodicity member of the following attributes to 64:

– NRCellDU.sibType2

– NRCellDU.sibType4

– NRCellDU.sibType5

4. Set the [Link] attribute to UNLOCKED.

Result: Five MBSFN subframes are allocated in LTE for NR resources specific to NR SA.

If the NR signaling shows performance degradation in the ESS cell pair with the configured value, use the following alternative MBSFB
subframe allocation setting:

5. Set the [Link] attribute to LOCKED.

6. Set the [Link] attribute to SA_SIB_ROBUST_15_PERCENT.

7. Set the [Link] attribute to UNLOCKED.

Result: Six MBSFN subframes are allocated in LTE for NR resources specific to NR SA.

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with NR Standalone

[Link] MBSFN Subframe Configuration for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

MBSFN subframes can be configured for the LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature to align the NR signals
and mitigate LTE interference in an ESS cell pair.

Table 67 Supported MBSFN Subframe Configurations for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

NR Cell [Link] [Link] Description Subframes Used

Configuration Value Value for MBSFN in a
Option 40-Subframe
Pattern
10 MBSFN
subframes are 1, 2, 6, 12, 21, 22,
EN-DC only true NSA_25_PERCENT
allocated to NR 28, 31, 36, 38
resources.
10 MBSFN
NR standalone only,
subframes are 1, 6, 12, 21, 22, 23,
and NR standalone false SA_25_PERCENT
allocated to NR 26, 28, 36, 38
EN-DC coexistence
resources.
EN-DC, NR 14 MBSFN
1, 2, 6, 8, 12, 18,
standalone, and NR subframes are
true or false NSA_SA_35_PERCENT 21, 22, 23, 26, 28,
standalone EN-DC allocated to NR
31, 36, 38
coexistence resources.
EN-DC, NR 18 MBSFN 1, 2, 6, 8, 12, 16,
standalone, and NR subframes are 18, 21, 22, 23, 26,
true or false NSA_SA_45_PERCENT
standalone EN-DC allocated to NR 27, 28, 31, 32, 36,
coexistence resources. 37, 38
EN-DC, NR 22 MBSFN 1, 2, 3, 6, 8, 12, 13,
standalone, and NR subframes are 16, 17, 18, 21, 22,
true or false NSA_SA_55_PERCENT
standalone EN-DC allocated to NR 23, 26, 27, 28, 31,
coexistence resources. 32, 33, 36, 37, 38

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

[Link].1 Optimization of MBSFN Subframe Configuration for LTE and NR Downlink PRB Utilization

If the LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature is activated, the scheduling policy must be aligned with the
configuration of the MBSFN subframes.

Table 68 MBSFN Subframe Configurations with LTE-NR FDD Spectrum Sharing with Policy-based Biasing Feature Activated
[Link] [Link] Number of Number of Number of Ratio of Ratio of
Value Value Non-MBSFN LTE-Usable NR- the the
Subframes Non-MBSFN Dedicated Number of Number of
with LTE- Subframes MBSFN LTE- LTE-
Prioritization with NR Subframes Prioritized Prioritized
in Downlink Prioritization in and NR- and NR-
in Downlink Downlink Prioritized Prioritized
Subframes Subframes
in in Uplink
Downlink
LTE_BIASED 27 10 3 27:13 3:1
NSA_BASIC FAIR 18 19 3 18:22 1:1
NR_BIASED 10 27 3 10:30 1:3
LTE_BIASED 27 8 5 27:13 3:1
SA_BASIC FAIR 18 17 5 18:22 1:1
NR_BIASED 10 25 5 10:30 1:3
LTE_BIASED 26 8 6 26:14 3:1
SA_SIB_ROBUST_15_PERCENT FAIR 17 17 6 17:23 1:1
NR_BIASED 10 24 6 10:30 1:3
LTE_BIASED 26 4 10 26:14 3:1
NSA_25_PERCENT or SA_25_PERCENT FAIR 17 13 10 17:23 1:1
NR_BIASED 10 20 10 1:3 1:3
LTE_BIASED 22 4 14 22:18 3:1
NSA_SA_35_PERCENT FAIR 17 9 14 17:23 1:1
NR_BIASED 10 16 14 1:3 1:3
LTE_BIASED N/A N/A N/A N/A N/A
NSA_SA_45_PERCENT FAIR 17 5 18 17:23 1:1
NR_BIASED 10 12 18 1:3 1:3
LTE_BIASED N/A N/A N/A N/A N/A
NSA_SA_55_PERCENT FAIR 14 4 22 14:26 1:1
NR_BIASED 10 8 22 1:3 1:3

LTE-prioritized subframes are located in non-MBSFN subframes. In such subframes, LTE DRBs with QoS parameters of lower scheduling
priority are prioritized over the NR DRB traffic with equivalent QoS parameters.

NR SRBs or DRBs with high QoS parameters of higher scheduling priority, for example, voice traffic, have a higher priority when using non-
MBSFN subframes.

If no LTE traffic is present, other types of NR traffic can use the non-MBSFN subframes.

NR-prioritized subframes can be located in either non-MBSFN or MBSFN subframes.

In case of non-MBSFN subframes, the NR-prioritized subframes prioritize the NR QoS traffic over LTE DRBs with QoS parameters of lower
scheduling priority.

If no NR traffic is present, LTE traffic can use the non-MBSFN subframes. MBSFN subframes are dedicated resources for NR with no LTE
downlink traffic.

Configuring a higher percentage of MBSFN subframes aim for cases of high NR traffic volume.

In case of low NR traffic volume and high LTE traffic volume, if the [Link] attribute is set to
NSA_SA_55_PERCENT, LTE cannot utilize 55% of the subframes. LTE KPIs degrade significantly as a result.

Table 69 shows nominal LTE and NR downlink PRB utilization derivation under traffic contention. The shown cases use specific MBSFN
configuration and scheduling policy settings, with NR using all NR-prioritized subframes and LTE using all LTE-prioritized subframes.
Table 69 Derivation of Nominal LTE and NR Downlink PRB Utilization

[Link] [Link] LTE to NR LTE Nominal PRB NR Nominal PRB

Value Value Subframe Ratio Utilization Utilization
NSA_BASIC
LTE_BIASED 27:13 68% 32%
SA_BASIC
NSA_BASIC
FAIR 18:22 45% 55%
SA_BASIC
[Link] [Link] LTE to NR LTE Nominal PRB NR Nominal PRB
Value Value Subframe Ratio Utilization Utilization
SA_SIB_ROBUST_15_PERCENT
LTE_BIASED 26:14 65% 35%
SA_25_PERCENT
NSA_SA_35_PERCENT LTE_BIASED 22:18 55% 45%
SA_SIB_ROBUST_15_PERCENT
SA_25_PERCENT
NSA_25_PERCENT FAIR 17:23 43% 57%
NSA_SA_35_PERCENT
NSA_SA_45_PERCENT
NSA_SA_55_PERCENT FAIR 14:26 35% 65%
NSA_BASIC
NR_BIASED 10:30 25% 75%
NSA_SA_55_PERCENT
If the MBSFN percentage configuration is not appropriate, the following cases can apply:

– The MBSFN percentage is too low and causes either low NR or LTE throughput, or both, which can be indicated by the following
occurrences:

• The average total of PRB utilization is high.

• Average NR PRB utilization exceeds the configured MBSFN percentage.

• The percentage of the MBSFN subframes in which the NR PRB utilization is above the configured value exceeds 50%.

– The MBSFN percentage is too high and decreases the LTE throughput, which can be indicated by the following occurrences:

• Average NR PRB utilization is below the configured MBSFN percentage.

• Average LTE PRB utilization is close to the nominal LTE PRB utilization under traffic contention.

• The percentage of the MBSFN subframes in which the NR PRB utilization is below the configured MBSFN exceeds 50%.

Table 70 Determination of Recommended MBSFN Percentage

Condition Recommended [Link] Value

(Average DL PRB Utilization in ESS, NR impact only (%) ≤ T1) or NSA_BASIC
(P(UNRDist ≤ T2) ≥ T3) SA_BASIC
(Average DL PRB Utilization in ESS, NR impact only (%) ≤ T4) or
(P(UNRDist ≤ T5) ≥ T3) and (Average DL PRB Utilization in ESS, NR SA_25_PERCENT
impact only (%) + Average DL PRB Utilization in ESS, LTE impact only NSA_25_PERCENT
(%) ≥ T6)
(Average DL PRB Utilization in ESS, NR impact only (%) ≤ T7) or
(P(UNRDist ≤ T8) ≥ T3) and (Average DL PRB Utilization in ESS, NR
NSA_SA_35_PERCENT
impact only (%) + Average DL PRB Utilization in ESS, LTE impact only
(%) ≥ T6)
(Average DL PRB Utilization in ESS, NR impact only (%) ≤T9) or
(P(UNRDist ≤ T10) ≥ T3) and (Average DL PRB Utilization in ESS, NR
NSA_SA_45_PERCENT
impact only (%) + Average DL PRB Utilization in ESS, LTE impact only
(%) ≥ T6)
Other conditions not satisfied and Category M support not required NSA_SA_55_PERCENT

For NR PRB utilization, the value of the Average DL PRB Utilization in ESS, NR impact only KPI can be used if traffic load is high. If the same
MBSFN percentage configuration is required in a cluster, the KPI must be averaged over the whole cluster. The KPI distribution over a cluster
and over a period of high traffic load can also be obtained, and a percentile value can be used in the algorithm.

The purpose of the condition involving the total PRB utilization (Average DL PRB Utilization in ESS, NR impact only + Average
DL PRB Utilization in ESS, LTE impact only) is to minimize the MBSFN percentage configuration change. The condition can be
removed if the goal is to improve NR performance and configuration change effort is not a concern,

The threshold values, from T1 to T10, are determined by the preference of the operator to improve NR or LTE performance, or to balance out
the NR and the LTE performance.
Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
O&M Aspects of LTE-NR FDD Spectrum Sharing with Policy-based Biasing
FAJ 121 5406: LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
 FAJ 121 5257: LTE-NR FDD Spectrum Sharing with NR Standalone
FAJ 121 5147: LTE-NR FDD Spectrum Sharing Enabler
Related reference
Network Impact of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

[Link].2 Optimization of MBSFN Subframe Configuration for LTE and NR Interference Reduction

The LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature can be used to mitigate interference on NR that is generated by
LTE.

In case of LTE interference, the distribution of NR MCS in MBSFN subframes can be more than three bins higher than in non-MBSFN
subframes.

Interference on NR that is generated by LTE can decrease if the number of MBSFN subframes are increased.

Interference generated by LTE CRS symbols can be mitigated by using non-shifted CRS configurations in the cell.

However, mitigation actions might degrade LTE service. Monitoring the NR MCS distribution of non-MBSFN subframes when MBSFN
subframes are increased to ensure an acceptable level of NR MCS distribution. It is also recommended to use non-shifted CRS configurations
only for neighboring LTE cells that are in the same node.

Related concepts
FAJ 121 5406: LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

[Link] LTE Downlink Throughput Degradation

If the configured MBSFN percentage is too high, LTE downlink throughput degradation can occur.

Table 71 shows the predicted impact on LTE downlink throughput if the MBSFN percentage changes.

Table 71 Impact of MBSFN Percentage Change on LTE Downlink Throughput

PRB Utilization of LTE Cell During Previous LTE Downlink Throughput Impact Calculation
MBSFN Configuration
LTE_PRB_utilization_previous ≤ (1 -
Degradation is not expected. Not applicable
MBSFN%) / 100(1)(2)
(LTE_PRB_utilization_previous(1) - (1 -
LTE_PRB_utilization_previous > (1 -
Degradation is expected. MBSFN%(2)) / 100) /
MBSFN%) / 100(1)(2)
LTE_PRB_utilization_previous(1)
(1) The LTE_PRB_utilization_previous is the PRB utilization of the LTE cell with the previous MBSFN percentage configuration.
(2) The MBSFN% is the current MBSFN percentage.

Example 12 LTE Downlink Throughput Degradation Prediction

Table 72 predicts LTE downlink throughput degradation if MBSFN percentage changes from 12.5% to 55%.
Table 72 MBSFN Percentage Change from 12.5% to 55%

LTE Cell PRB Utilization with 12.5% MBSFN LTE Downlink Throughput Impact with 55% Calculation
MBSFN
PRB_utilization_12.5 ≤ (1 - 55%) Degradation is not expected. Not applicable.
A degradation between 0% and 49% is ((1 - 12.5%) - (1 - 55%)) / (1 -
PRB_utilization_12.5 > (1 - 55%)
expected. 12.5%) = 49%

Table 73 predicts LTE downlink throughput degradation if MBSFN percentage changes from 25% to 55%.
Table 73 MBSFN Percentage Change from 25% to 55%

LTE Cell PRB Utilization with 25% MBSFN LTE Downlink Throughput Impact with 55% Calculation
MBSFN
PRB_utilization_25 ≤ (1 - 55%) Degradation is not expected. Not applicable.
A degradation between 0% and 40% is ((1 - 25%) - (1 - 55%)) / (1 - 25%)
PRB_utilization_25 > (1 - 55%)
expected. = 40%
3.2.3 Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes
When additional MBSFN subframes are configured with the LTE-NR FDD Spectrum Sharing with Tunable NR Subframes feature, attributes
for related activated features can be set to recommended values.

Table 74 Recommended Parameter Settings for LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

MO Attribute Recommended Value

[Link] Larger than PSF4
[Link] Larger than PSF4
[Link] 0
[Link] SF1
[Link] 11
One of the following values:
– TRANSMISSION_MODE_2
[Link]
– TRANSMISSION_MODE_3

– TRANSMISSION_MODE_4

Related reference
Dependencies of LTE-NR FDD Spectrum Sharing with Tunable NR Subframes

3.2.4 Configure Policy-Based Biasing

Prioritize non-GBR traffic between LTE and NR.

The procedure is applicable regardless of the ESS migration scenario.

Steps

1. Set the [Link] attribute to LTE_BIASED to favor LTE non-GBR traffic, or to NR_BIASED to favor NR non-GBR
traffic.

3.2.5 SINR Threshold Configuration to Avoid Throughput Degradation

When tuning the SINR threshold for the LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature, radio
conditions in the cell must be considered.

When the LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature is activated on the gNodeB and enabled in
individual NR cells in ESS cell pairs, downlink throughput gains depend on channel conditions. The CQI counters, for example, can be used to
monitor the channel conditions. The gNodeB evaluates the channel conditions by SINR estimation and compares this estimated SINR to a
threshold value that can be configured on cell level. If the estimated SINR is below this configured threshold, the gNodeB does not multiplex
PDSCH with DMRS for a given PDSCH transmission to avoid throughput degradation.

The threshold value can be set and tuned by using the [Link] attribute. The attribute value applies to the
individual cell.

The optimal SINR threshold value depends on factors that can be different for each cell. For example, channel conditions, traffic
characteristics, and the distribution of the UEs within the cell.

When the feature is enabled in a cell with the default threshold value set in the [Link] attribute, the NR KPIs
representing data throughput need to be monitored. If no performance gain can be observed in the cell with the default threshold value, the
attribute must be tuned until the data throughput KPIs show performance gain.

Throughput gain reduction might also occur at high SINR when the feature is activated and enabled in a cell. This is because SINR is reduced
in the cell for users scheduled with higher modulation schemes (64QAM, 256QAM) with power back-off. In this case, the SINR threshold might
need to be tuned to mitigate the reduction in throughput gain.

Related concepts
LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing Overview
Optimize
3.2.6 Enable or Disable the Multiplexing of PDSCH and DMRS Manually
The operator can manually enable or disable the multiplexing of PDSCH and DMRS on a cell level when the LTE-NR FDD Spectrum Sharing
with Downlink Data and DMRS Multiplexing feature is activated.

The [Link] attribute is used to enable or disable the multiplexing of PDSCH and DMRS manually in
individual cells.
The configuration can be used regardless of the ESS migration scenario.

Prerequisites
The LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing feature is activated.

Steps

1. Set the [Link] attribute to true in the NR cell of the ESS cell pair in which the multiplexing of PDSCH and
DMRS is to be enabled.

If activating the feature leads to throughput degradation in a cell, the multiplexing of PDSCH and DMRS can be disabled manually. To prevent
downlink throughput degradation in a given cell:

2. Set the [Link] attribute to false in the NR cell of the ESS cell pair.
Result: The multiplexing of PDSCH and DMRS is not applied in the cell.

Related concepts
LTE-NR FDD Spectrum Sharing with Downlink Data and DMRS Multiplexing Overview

3.2.7 O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M

Category M can be introduced into an ESS configuration as part of the regular ESS deployment, or it can be introduced into an existing ESS
configuration. After the LTE-NR FDD Spectrum Sharing with Category M feature is enabled, it can be optimized to reduce the impact of
Category M on LTE and NR.

Activation The LTE-NR FDD Spectrum Sharing with Category M feature requires feature activation, performed during the ESS
deployment activities. Depending on the ESS migration scenario, see the following information:

– Activate Features in the Migration Scenario from LTE to EN-DC–ESS

– Activate Features in the Migration Scenario from LTE to SA–ESS

The LTE-NR FDD Spectrum Sharing with Category M feature is activated by setting the [Link]
attribute to ACTIVATED in the FeatureState=CXC4012537 MO instance.
The LTE-NR FDD Spectrum Sharing with Category M feature is deactivated by setting the
[Link] attribute to DEACTIVATED in the FeatureState=CXC4012537 MO instance.

Initial After the feature license is activated, the feature can be enabled through different procedures. Based on the initial network
Configuration environment, see the following information:

– Activate ESS Configuration in a Category M Access-Enabled Cell

– Activate Category M Access in an ESS Configuration

The LTE and NR cells must remain locked for the entire procedure, from before the feature is enabled until all the MO
attributes are set to the recommended values.

Optimization After initial configuration, the effect of Category M on LTE and NR can be reduced with the following optimization options:

– Reduce the Dynamic Effect of Category M

– Reduce the Static Effect of Category M

– Optimize Category M Resource Share

– Finetune Category M Resource Share

– Finetune Category M Uplink Resource Share

– Finetune the Resource Share of Category M RRC Establishments

Alarms The feature can raise an alarm in the following cases:

– The feature license is not activated.

– A prerequisite feature license is not activated.

– If the [Link] attribute is set to false while the feature is enabled, the ESS
Inconsistent Configuration alarm is raised.
The alarm is raised, because Category M must use common PRACH with LTE in an ESS configuration.

– If the total number of invalid subframes configured in the system is too high, the Inconsitent Configuration
alarm is raised.
For ESS with NR standalone deployment, the feature requires invalid subframes in the time domain. Invalid
subframes are configured for this feature through the [Link]
attribute. The alarm is not raised when the attribute value is set to other values.
However, the system uses invalid subframes from different sources, not only from this attribute. The invalid
subframes from different sources are added together. The alarm is only raised if the total number of invalid
subframes is too high.

For the ESS alarm information, see Detect and Resolve.

KPIs The impact of Category M on LTE and NR at heavy load can be observed through the following KPIs:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

– Average UL PRB Utilization in ESS

– Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

The dynamic effect of Category M on LTE and NR throughput can be observed through the Average UL MAC UE
Throughput KPI.
The following counters help to observe Category M traffic and decide when to limit Category M PRB use:

– EUtranCellFDD.pmCellCatmEssShareDlSrb0Max

– [Link]

– [Link]

The following counters help to observe how Category M traffic is affected by LTE and NR traffic:

– EUtranCellFDD.pmMacTimeDlCatmEssShareSrb0Enforced

– [Link]

– [Link]

The [Link] PM counter helps to observe when LTE and NR are fully
utilized.
The following PM counters introduced by the Category M Access feature can be used to observe the number of PRBs used
by Category M:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]
 – [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

These PM counters help to observe how Category M PRB use affects ESS.
For the ESS-related KPI and counter information, see Manage Performance.

[Link] Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

Table 75 Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

MO Attribute Value
[Link] true
[Link] 44
The opposite side of the
[Link] attribute, as
[Link] follows:
[Link] = 1-
[Link]
The opposite side of the
[Link] attribute, as
EUtranCellFDD.msg3FrequencyAllocationBr follows:
EUtranCellFDD.msg3FrequencyAllocationBr = 1-
[Link]
For ESS with NR standalone configuration:
1
[Link]
For ESS with EN-DC configuration:
0
NORMAL for cells if deep indoor, and large coverage is not needed for
EUtranCellFDD.siSib1RepetitionBr
Category M.
High priority:
1000
Moderate priority:
[Link]
30
Low priority:
1
High priority:
1000
Moderate priority:
[Link]
60
Low priority:
2
High priority:
1000
Moderate priority:
EUtranCellFDD.dlCatmEssShareSrb0
10
Low priority:
1

[Link] Activate ESS Configuration in a Category M Access-Enabled Cell

NR is introduced into an existing Category M-enabled LTE cell through ESS.

Prerequisites
 – Category M Access feature license is activated, and Category M is enabled in the LTE cell.

– The LTE-NR FDD Spectrum Sharing Enabler feature license is activated.

– The LTE-NR FDD Spectrum Sharing with Category M feature license is activated.

– For ESS with NR standalone configuration, the LTE-NR FDD Spectrum Sharing with NR Standalone feature is activated on the gNodeB.

Steps

1. Lock each cell in the following order where access for Category M must be configured:
a. Set the [Link] attribute to LOCKED if it is not already locked.

b. Set the [Link] attribute to LOCKED if it is not already locked.

2. Set the [Link] attribute to true.

3. Set the [Link] attribute to 44.

4. Configure the initial settings for ESS, but do not unlock the LTE and the NR cells.

5. For ESS with NR standalone configuration, set the [Link] attribute to the recommended
value of 1.

Note: If the total number of invalid subframes configured in the system is too high, the Inconsistent Configuration alarm might be raised
with the Configured total number of invalid downlink subframes exceeds internal system limit.
additional text.

6. Optimize the effect of Category M on LTE and NR with the following optimization options:

– Reduce the Dynamic Effect of Category M

– Reduce the Static Effect of Category M

7. Set the [Link] attribute to UNLOCKED if no other changes are planned that require a locked cell.

Results
The initial settings for ESS are configured. The LTE-NR FDD Spectrum Sharing with Category M feature is enabled and ready for further
optimization.

After This Task

After initial configuration, the effect of Category M on LTE and NR can be reduced with the following optimization options:

– Reduce the Dynamic Effect of Category M

– Reduce the Static Effect of Category M

– Optimize Category M Resource Share

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M
Related tasks
Reduce the Dynamic Effect of Category M
Reduce the Static Effect of Category M
Related reference
Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

[Link] Activate Category M Access in an ESS Configuration

Category M is introduced into an existing ESS cell pair.

Prerequisites

– The Category M Access feature license is activated.

– The LTE-NR FDD Spectrum Sharing with Category M feature license is activated.

– The LTE-NR FDD Spectrum Sharing Enabler feature license is activated and the initial settings for ESS are configured.

– For ESS with NR standalone configuration, the LTE-NR FDD Spectrum Sharing with NR Standalone feature is activated on the gNodeB.

Steps
 1. Lock each cell in the following order where access for Category M must be configured:
a. Set the [Link] attribute to LOCKED if it is not already locked.

b. Set the [Link] attribute to LOCKED if it is not already locked.

2. Set the [Link] attribute to true.

3. Set the [Link] attribute to 44.

4. Configure the initial settings for the Category M Access feature, but do not unlock the LTE cell.

5. For ESS with NR standalone configuration, set the [Link] attribute to the recommended
value of 1.

Note: If the total number of invalid subframes configured in the system is too high, the Inconsistent Configuration alarm might be raised
with the Configured total number of invalid downlink subframes exceeds internal system limit.
additional text.

6. Optimize the effect of Category M on LTE and NR with the following optimization options:

– Reduce the Dynamic Effect of Category M

– Reduce the Static Effect of Category M

7. Set the [Link] attribute to UNLOCKED if no other changes are planned that require a locked cell.
Results
The initial settings for ESS are configured. The LTE-NR FDD Spectrum Sharing with Category M feature is enabled and ready for further
optimization.

After This Task

After initial configuration, the effect of Category M on LTE and NR can be reduced with the following optimization options:

– Reduce the Dynamic Effect of Category M

– Reduce the Static Effect of Category M

– Optimize Category M Resource Share

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M
Related tasks
Reduce the Dynamic Effect of Category M
Reduce the Static Effect of Category M
Related reference
Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

[Link] Reduce the Dynamic Effect of Category M

To reduce the dynamic effect of Category M, configure the Category M PUSCH and Msg3 on the opposite side of the PRACH.

This procedure can be performed separately, or at the same time when Category M is first deployed together with ESS. In the latter case,
special attention is needed when locking or unlocking the cells.
Note: The entire process from deploying ESS together with Category M until the end of the initial configuration of the LTE-NR FDD Spectrum
Sharing with Category M feature requires a locked cell.

Prerequisites

– The Category M Access feature license is activated.

– The Category M Flexible Uplink Channel Allocation feature license is activated.

Steps

1. Set the [Link] attribute to LOCKED if it is not already locked.

2. Set the [Link] attribute to place the Category M PUSCH on the opposite side from PRACH.
Use the following formula:
[Link] = [Link]
If the [Link] attribute value equals 1, then the
[Link] attribute value equals 0.
 3. Set the EUtranCellFDD.msg3FrequencyAllocationBr attribute to place the Msg3 on the opposite side from PRACH. Use the
following formula:
EUtranCellFDD.msg3FrequencyAllocationBr = [Link]
If the EUtranCellFDD.msg3FrequencyAllocationBr attribute value equals 1, then the
[Link] attribute value equals 0.

4. Set the [Link] attribute to UNLOCKED if no other changes are planned that require a locked cell.
Results
This setting might increase the value of the Average UL MAC UE Throughput KPI. The amount of increase depends on the uplink LTE service
type.

[Link] Reduce the Static Effect of Category M

The static effect of Category M1 UEs on LTE and NR can be reduced if deep indoor, and large coverage is not needed for Category M.

This procedure can be performed separately, or at the same time when Category M is first deployed together with ESS. In the latter case,
special attention is needed when locking or unlocking the cells.
Note: The entire process from deploying ESS together with Category M until the end of the initial configuration of the LTE-NR FDD Spectrum
Sharing with Category M feature requires a locked cell.

Prerequisites

– The Category M Access feature license is activated.

– Deep indoor, or large coverage is not needed for Category M.

Steps

1. Set the [Link] attribute to LOCKED if it is not already locked.

2. Set the EUtranCellFDD.siSib1RepetitionBr attribute to NORMAL.

For more information, see Category M System Information Messages in the Category M Guideline.

3. Set the [Link] attribute to UNLOCKED if no other changes are planned that require a locked cell.

Results
Category M does not have deep indoor coverage, but the static effect of Category M1 UEs on LTE and NR is reduced.

After This Task

Observe the [Link] PM counter. If it is significantly reduced with this setting, then there are UEs in deep indoor
coverage or that are far from the radio node.
To serve these UEs, a MEDIUM or LARGE value is required for the EUtranCellFDD.siSib1RepetitionBr attribute.

Related concepts
O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M
Related tasks
Activate ESS Configuration in a Category M Access-Enabled Cell
Activate Category M Access in an ESS Configuration
Reduce the Dynamic Effect of Category M
Related reference
Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

[Link] Optimize Category M Resource Share

The Category M resource share optimization is based on the observed traffic and the wanted priority of Category M in the ESS cell pair.

The values of the resource control MO attributes are recommended to be set based on the following factors:

– Observed Category M, LTE, and NR traffic

– The wanted priority of Category M service in the cell pair

In the context of the LTE-NR FDD Spectrum Sharing with Category M feature, priority is not a specific setting, but the general importance of
Category M in a network.
 Maximum
High
resource share

Observe

Decide Category M Moderate

priority

Adjust
resource share

Minimum
Low
resource share

L0003292A

Figure 28 Category M Resource Share Optimization Workflow

Prerequisites
The initial configuration of the LTE-NR FDD Spectrum Sharing with Category M feature is completed.

Steps

1. Observe the effect of Category M on LTE and NR.

The following KPIs are recommended for consideration when the Category M resource share is optimized:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

– Average UL PRB Utilization in ESS

– Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

– E-RAB Retainability for Category M1 UEs - Session Time Normalized Loss Rate

– E-RAB Retainability for Category M1 UEs - Percentage Lost

The [Link] PM counter helps to understand the effect of Category M on LTE and NR.

2. Decide the priority of Category M service in the network.

3. Set the [Link] attribute to LOCKED.

4. Set the [Link] attribute based on the Category M priority:

Priority Recommended Value

High 1000

Moderate 30

Low 1
 5. Set the [Link] attribute based on the Category M priority:

Priority Recommended Value

High 1000

Moderate 60

Low 2

6. Set the EUtranCellFDD.dlCatmEssShareSrb0 attribute based on the Category M priority:

Priority Recommended Value

High 1000

Moderate 10

Low 1

7. Set the [Link] attribute to UNLOCKED.

Results
Category M PRB share is handled according to its priority level at high LTE or NR load.

After This Task

Continue to observe the effect of Category M on LTE and NR. Change the attribute values if the priority of Category M service changes or if
further tuning is needed.
Related concepts
Category M Resource Sharing Guidelines
O&M Aspects of LTE-NR FDD Spectrum Sharing with Category M
Related tasks
Finetune Category M Resource Share
Finetune Category M Uplink Resource Share
Finetune the Resource Share of Category M RRC Establishments
Related reference
Parameter Recommendations for LTE-NR FDD Spectrum Sharing with Category M

[Link] Finetune Category M Resource Share

Category M resource share of moderate priority is recommended to be tuned based on the observed Category M, LTE, and NR traffic.

The [Link] attribute can be used to reduce the effect of Category M on the LTE and the NR downlink and uplink
at the same time, because uplink service is granted in downlink.
This task is about balancing the LTE and NR service against the Category M service. If LTE and NR service is favored, the Category M drop rate
might increase. If Category M is favored, the effect of Category M on LTE and NR at high load is greater.
To achieve the required balance, it is recommended to perform and repeat this task over time, while monitoring the following KPIs:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

 – Average UL PRB Utilization in ESS

– Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

– E-RAB Retainability for Category M1 UEs - Session Time Normalized Loss Rate

– E-RAB Retainability for Category M1 UEs - Percentage Lost

The following PM counters also help understand the effect of Category M on LTE and NR:

– [Link]

– [Link]

– [Link]

Steps

1. Monitor the KPIs and counters in the nodes where Category M traffic is high.

2. Set the [Link] attribute to LOCKED.

3. Adjust the value of the [Link] attribute in increments of 10, based on the value observed with the
[Link] counter.
If the Category M resource share is to be decreased, set the value of the [Link] attribute lower than the
value observed with the counter.
If the Category M resource share is to be increased, set the value of the [Link] attribute higher than the
value observed with the counter.

4. Set the [Link] attribute to UNLOCKED.

Results
The effect of Category M on LTE and NR traffic at high LTE or NR load is optimized.

After This Task

Continue to observe the KPIs and counters in the affected nodes and repeat this task if necessary.

[Link] Finetune Category M Uplink Resource Share

Category M uplink resource share can be tuned when Category M traffic affects the LTE or NR uplink traffic, but the effect on downlink is
small.

The [Link] attribute can be used to reduce the effect of Category M on the LTE and the NR downlink and uplink
at the same time, because uplink service is granted in downlink.
However, if Category M traffic affects the uplink traffic, but the effect on downlink is small, the uplink resource share can be tuned separately.
This task is about balancing the LTE and NR service against the Category M service. If LTE and NR service is favored, the Category M drop rate
might increase. If Category M is favored, the effect of Category M on LTE and NR at high load is greater.
To achieve the required balance, it is recommended to perform and repeat this task over time, while monitoring the following KPIs:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

– Average UL PRB Utilization in ESS

– Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

– E-RAB Retainability for Category M1 UEs - Session Time Normalized Loss Rate

– E-RAB Retainability for Category M1 UEs - Percentage Lost

The following counters also help understand the effect of Category M on LTE and NR:

– [Link]

– [Link]

Steps
 1. Monitor the KPIs and counters in the nodes where Category M traffic is high.

2. Set the [Link] attribute to LOCKED.

3. Adjust the value of the [Link] attribute in increments of 10, based on the value observed through the
[Link] PM counter.
If the Category M resource share is to be decreased, set the value of the [Link] attribute lower than the
value observed through the PM counter.
If the Category M resource share is to be increased, set the value of the [Link] attribute higher than the
value observed through the PM counter.

4. Set the [Link] attribute to UNLOCKED.

Results
Category M has reduced effect on uplink LTE and NR traffic at high LTE or NR load.

After This Task

Continue to observe the KPIs and counters in the affected nodes and repeat this task if necessary.

[Link] Finetune the Resource Share of Category M RRC Establishments

Category M traffic might affect LTE and NR when many Category M UEs try to connect to the cell at the same time. For this rare use case,
the number of downlink PRBs available for Category M RRC establishment can be reduced.

This task is about balancing the LTE and NR service against the Category M service. If LTE and NR service is favored, the Category M drop rate
might increase. If Category M is favored, the effect of Category M on LTE and NR at high load is greater.
To achieve the required balance, it is recommended to perform and repeat this task over time, while monitoring the following KPIs:

– Average DL PRB Utilization

– Average UL PRB Utilization

– Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only in ESS (expressed in Mbps)

– Average DL PRB Utilization in ESS

– Average UL PRB Utilization in ESS

– Normalized Average UL MAC Cell Throughput in ESS (expressed in Mbps)

– E-RAB Retainability for Category M1 UEs - Session Time Normalized Loss Rate

– E-RAB Retainability for Category M1 UEs - Percentage Lost

The following counters also help understand the effect of Category M on LTE and NR:

– EUtranCellFDD.pmCellCatmEssShareDlSrb0Max

– EUtranCellFDD.pmMacTimeDlCatmEssShareSrb0Enforced

Steps

1. Monitor the KPIs and counters in the nodes where Category M traffic is high.

2. Set the [Link] attribute to LOCKED.

3. Set the EUtranCellFDD.dlCatmEssShareSrb0 attribute to the value observed through the

EUtranCellFDD.pmCellCatmEssShareDlSrb0Max PM counter, or lower.

4. Set the [Link] attribute to UNLOCKED.

Results
Category M RRC establishments have reduced effect on downlink LTE and NR traffic at high LTE or NR load.

After This Task

Continue to observe the KPIs and counters in the affected nodes and repeat this task if necessary.

3.2.8 Configure LTE-NR FDD Spectrum Sharing with NB-IoT

 The LTE-NR FDD Spectrum Sharing with NB-IoT feature must be configured in a way that NB-IoT PRBs do not interfere with NR resource
blocks and blanked PRBs.

If the LTE-NR FDD Spectrum Sharing with Flexible Channel Bandwidth feature supports only EN-DC mode, the configuration of NB-IoT
coexistence with blanked PRBs can be supported only in EN-DC mode. In other cases, the NB-IoT coexistence with blanked PRBs can be
supported in EN-DC mode or NR standalone mode. The NB-IoT PRBs must be within the valid PRB range and must not collide with blanked
PRBs.

Related concepts
LTE-NR FDD Spectrum Sharing with NB-IoT Overview

[Link] Activate NB-IoT Access in an ESS Configuration

Either NB-IoT can be introduced into an existing LTE-NR ESS configuration, or NR can be introduced into an existing LTE network that is
deployed with NB-IoT.

An ESS service is already set up and NB-IoT needs to be configured.

Prerequisites

– Activate the LTE-NR FDD Spectrum Sharing Enabler feature license.

– For ESS with NR SA, activate the LTE-NR FDD Spectrum Sharing with NR Standalone feature for ESS.

– If non-anchor carrier support is required, activate the NB-IoT Non-Anchor Carrier Support feature license.

Steps

1. Lock each cell where NB-IoT needs to be configured.

a. Lock the NR cell.

b. Lock the LTE cell.

2. Activate the NB-IoT Access feature license.

3. Set the initial settings for the NB-IoT Access feature.

4. Activate the LTE-NR FDD Spectrum Sharing with NB-IoT feature license.
The LTE-NR FDD Spectrum Sharing with NB-IoT feature is activated by setting the [Link] attribute to
ACTIVATED in the FeatureState=CXC4012540 MO instance.

5. Set the [Link] attribute to the EUtranCellFDD MO instance.

6. Set the [Link] attribute to 0 if the value is not 0.

7. Set the [Link] attribute to true.

To optimize the LTE-NR FDD Spectrum Sharing with NB-IoT feature:

8. Configure the PRB indexes with the following attributes:

Table 76 Supported NB-IoT PRB Indexes

Related Attribute Bandwidth Supported PRB Indexes

10 MHz -1, 50, 255
[Link]
(1)
15 MHz -1, 75, 255
20 MHz -2, -1, 100, 101, 255
10 MHz -1, 50, 255

[Link] 15 MHz -2(2), -1, 75, 76(2), 255

20 MHz -3(2), -2, -1, 100, 101, 102(2), 255
10 MHz -1, 50

[Link] 15 MHz -2(3), -1, 75, 76(4)

20 MHz -3(5), -2, -1, 100, 101, 102(6)
[Link] 10 MHz -1, 50
15 MHz -2(2), -1, 75, 76(2)
 Related Attribute Bandwidth Supported PRB Indexes
20 MHz -3(2),-2,-1, 100, 101, 102(2)
(1) When downlink PRB indexes are configured, it is recommended to place the anchor PRBs nearer to the center of the bandwidth than non-anchor PRBs.
(2) The value of the [Link] attribute can be up to 3 for this PRB. This PRB index can be configured even if the value of the
[Link] attribute is 0.
(3) -2 can only be configured when the value of the [Link] attribute is at least 3.
(4) 76 can only be configured when the value of the [Link] attribute is at least 4.
(5) -3 can only be configured when the value of the [Link] attribute is at least 1.
(6) 102 can only be configured when the value of the [Link] attribute is at least 2.

9. Unlock the LTE cell.

10. Unlock the NR cell.

[Link] Activate ESS Configuration in an LTE Cell that Hosts an NB-IoT Cell

Either NB-IoT can be introduced into an existing LTE-NR ESS configuration, or NR can be introduced into an existing LTE network that is
deployed with NB-IoT.

An LTE cell that hosts an NB-IoT cell is already set up and ESS needs to be configured.

Prerequisites

– Activate the LTE-NR FDD Spectrum Sharing Enabler feature license.

– Activate the LTE-NR FDD Spectrum Sharing with NB-IoT feature license.

– Activate the NB-IoT Access feature license.

– For ESS with NR standalone configuration, activate the LTE-NR FDD Spectrum Sharing with NR Standalone feature for ESS.

– If non-anchor carrier support is required, activate the NB-IoT Non-Anchor Carrier Support feature license.

Steps

1. Lock each cell where ESS needs to be configured.

a. Lock the NR cell.

b. Lock the LTE cell.

2. Set the initial settings for ESS. For information, see Migration from LTE to EN-DC–ESS or Migration from LTE to SA–ESS.

3. Set the [Link] attribute to 0 if the value is not 0.

4. Set the [Link] attribute to true.

To optimize the LTE-NR FDD Spectrum Sharing with NB-IoT feature:

5. Configure the PRB indexes with the following attributes:

Table 77 Supported NB-IoT PRB Indexes

Related Attribute Bandwidth Supported PRB Indexes

10 MHz -1, 50, 255
[Link]
(1) 15 MHz -1, 75, 255
20 MHz -2, -1, 100, 101, 255
10 MHz -1, 50, 255
[Link] 15 MHz -2(2), -1, 75, 76(2), 255
20 MHz -3(2), -2, -1, 100, 101, 102(2), 255
10 MHz -1, 50

[Link] 15 MHz -2(3), -1, 75, 76(4)

20 MHz -3(5), -2, -1, 100, 101, 102(6)
10 MHz -1, 50

[Link] 15 MHz -2(2), -1, 75, 76(2)

20 MHz -3(2),-2,-1, 100, 101, 102(2)
 (1) When downlink PRB indexes are configured, it is recommended to place the anchor PRBs nearer to the center of the bandwidth than non-anchor PRBs.
(2) The value of the [Link] attribute can be up to 3 for this PRB. This PRB index can be configured even if the value of the
[Link] attribute is 0.
(3) -2 can only be configured when the value of the [Link] attribute is at least 3.
(4) 76 can only be configured when the value of the [Link] attribute is at least 4.
(5) -3 can only be configured when the value of the [Link] attribute is at least 1.
(6) 102 can only be configured when the value of the [Link] attribute is at least 2.

6. Unlock the LTE cell.

7. Unlock the NR cell.

[Link] NB-IoT PRB Configuration Examples

Default anchor and non-anchor PRB configuration examples without PRB blanking.

Example 13 Default Anchor and Non-Anchor PRB Configuration for 10 MHz

Attribute Example Value

[Link] 50
[Link] 50
[Link] -1
[Link] -1

Example 14 Default Anchor and Non-Anchor PRB Configuration for 15 MHz

Attribute Example Value

[Link] 75
[Link] 76
[Link] -1
[Link] -2

Example 15 Default Anchor and Non-Anchor PRB Configuration for 20 MHz

Attribute Example Value

[Link] -1
[Link] 102
[Link] -2
[Link] -3

[Link] NB-IoT PRB Configuration Examples with Blanked PRBs

It is recommended to secure as many guard band PRBs as possible when NB-IoT PRBs are allocated.

Example 16 20 MHz Guard Band NB-IoT Configuration 1

With the configuration in Table 78, NR resource blocks 0, 1, and 2 are blanked, and the following resource blocks can be allocated to NB-IoT:
 -3 -2 -1 0 1 98 99 100 101 102

0 1 2 3 4 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003065A

Figure 29 Resource Block Allocation 1

Table 78 MO Configuration 1

MO Attribute Value
[Link] 0
[Link] 100
[Link] 101
[Link] 3

Example 17 20 MHz Guard Band NB-IoT Configuration 2

With the configuration in Table 79, NR resource blocks 104 and 105 are blanked, and the following resource blocks can be allocated to NB-IoT:
 -3 -2 -1 0 1 98 99 100 101 102

0 1 2 3 4 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003066A

Figure 30 Resource Block Allocation 2

Table 79 MO Configuration 2

MO Attribute Value
[Link] 0
[Link] 100
[Link] 101
[Link] 3

Example 18 20 MHz Guard Band NB-IoT Configuration 3

With the configuration in Table 80, NR resource blocks 0 and 105 are blanked, and the following resource blocks can be allocated to NB-IoT:
 -3 -2 -1 0 1 98 99 100 101 102

0 1 2 3 4 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003067A

Figure 31 Resource Block Allocation 3

Table 80 MO Configuration 3

MO Attribute Value
[Link] 0
[Link] 100
[Link] 100
[Link] 3

Example 19 20 MHz Guard Band NB-IoT Configuration 4

With the configuration in Table 81, NR resource blocks 0, 1, 2, 3, 4, 5, and 6 are blanked, and the following resource blocks can be allocated to
NB-IoT:
 -3 -2 -1 0 1 2 3 4 98 99 100 101 102

0 1 2 3 4 5 6 7 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003068A

Figure 32 Resource Block Allocation 4

Table 81 MO Configuration 4

MO Attribute Value
[Link] 4
[Link] 96
[Link] 96
[Link] 7

[Link] NB-IoT PRB Configuration for Guard Band Cells Interacting with ESS

If ESS coexists with NB-IoT, the MOs of anchor and non-anchor PRBs are recommended to be set to specific values based based on the
used bandwidth. Applying the recommended settings prevents LTE throughput degradation and increases the efficiency of the NR
frequency.

Table 82 Recommended Anchor and Non-Anchor PRB Configuration

Bandwidth Non-Anchor PRB Number Non-Anchor PRB Index(1) Anchor PRB Index(2)
10 MHz 0 255 50
75
0 255
76
15 MHz
75 76
1
76 75
 Bandwidth Non-Anchor PRB Number Non-Anchor PRB Index(1) Anchor PRB Index(2)
-3
-2
-1
0 255
100
101
102
20 MHz
-3 -3
-2 -2
-1 -1
1
100 100
101 101
102 102
(1) Cannot be the same as anchor PRB index.
(2) Cannot be the same as non-anchor PRB index.

Considerations
For 10 MHz bandwidth, GB 1+0 is recommended to be deployed, and the NB-IoT PRB is recommended to be allocated to the highest PRB
index. This can be done by setting the [Link] attribute, it is recommended to set the attribute to 50. Otherwise, LTE
throughput can degrade when NR traffic is increased.
For 15 and 20 MHz bandwidth, both the downlink anchor and non-anchor NB-IoT PRBs are recommended to be set to the same edge by
manually configuring the [Link] and the [Link] attributes. Otherwise, the NR
frequency can be less efficient and LTE throughput can degrade for the 15 MHz bandwidth.

[Link] NB-IoT Spillover Example

One or more subcarriers of the guard band NB-IoT PRB can exceed the PRB subcarrier range of the ESS NR cell. If non-zero spillover is
supported, the number of NR CRBs that need to be reserved for NB-IoT is reduced. The supported spillover value is represented by the
[Link] and the [Link] attributes.

Example 20 20 MHz Bandwidth with Spillover of Two Subcarriers in Downlink

In Figure 33, the NB-IoT PRBs spill over the last subcarrier of NR CRB 105 by two subcarriers.

.. .. .. 101
SC9
101
SC10
101
SC11
102
SC0
102
SC1 .. .. .. 102
SC8
102
SC9
102
SC10
102
SC11

.. .. .. 104
SC11
105
SC0
105
SC1
105
SC2
105
SC3 .. .. .. 105
SC10
105
SC11

NB-IoT PRB subcarrier

NR CRB subcarrier

Spillover

L0003392A

Figure 33 Spillover of Two Subcarriers in Downlink

If the supported spillover is at least two, NB-IoT PRB 101 and 102 can be used. In this case, only NR CRB 104 and 105 is reserved for NB-IoT,
and NR CRB 103 can be used for NR.
 -3 -2 -1 0 1 .. .. .. 98 99 100 101 102

0 1 2 3 4 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003391A

Figure 34 Resource Block Allocation with Spillover Support

However, if the supported spillover is less than two, NB-IoT PRB 102 cannot be used, so NB-IoT PRB 100 and 101 must be used. NB-IoT PRB
101 overlaps with NR CRB 104 and 105, so both NR CRBs must be reserved for NB-IoT. This results in fewer resource blocks that can be used
for NR.

-3 -2 -1 0 1 .. .. .. 98 99 100 101 102

0 1 2 3 4 .. .. .. 101 102 103 104 105

NB-IoT PRB

NR RB

LTE PRB

Blanked RB

Unused RB

L0003390A

Figure 35 Resource Block Allocation without Sufficient Spillover Support

Example 21 15 MHz Bandwidth with Spillover of Two Subcarriers in Uplink

In Figure 36, the NB-IoT PRBs spill over the first subcarrier of NR CRB 0 and the last subcarrier of NR CRB 78 by two subcarriers. Even if the
supported spillover value is 0, the -2 and 76 PRB indexes can be configured for NB-IoT. However, a larger supported spillover value can reduce
the interference from NB-IoT.
 -2 SC3 -1 SC0 0 SC0 75 SC0 76 SC0
-2 -2 -2 76 76 76
- - - - -
SC0 SC1 SC2 SC9 SC10 SC11
-2 SC11 -1 SC11 74 SC11 75 SC11 76 SC8

0 SC1 1 SC0 2 SC0 77 SC0 78 SC2

0 0 0 78 78 78
- - - - -
SC0 SC10 SC11 SC0 SC1 SC11
0 SC9 1 SC11 76 SC11 77 SC11 78 SC10

NB-IoT PRB subcarrier

NR CRB subcarrier

LTE PRB subcarrier

Unused PRB subcarrier

Spillover

Gap

L0003393A

Figure 36 Spillover of Two Subcarriers in Uplink

3.2.9 Configuration of Outer Loop Link Adaptation

Dual loop link adaptation is used if the [Link] attribute is set to true. If the
[Link] attribute is set to false, single outer loop link adaptation is used.

Note: The [Link] attribute can only be set to true if the LTE-NR FDD Spectrum Sharing with Dual Outer
Loop Link Adaptation feature is operable and the NR cell is part of an ESS cell pair.
The following attributes can be adjusted for correct functioning, depending whether single or dual outer loop link adaptation is used:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

The MO Configuration Pending Action alarm is raised as a notification about the inconsistency in the configuration of any attributes
on the PCell and the ESCells. If the ESCell configuration changes when inter-node carrier aggregation is used in ESS, the ESCell must be locked
and unlocked to clear the alarm. The changes are synchronized between the PCell and the ESCell through this action.
Note: The configuration change is immediately synchronized to the PCell and the internal SCell. The operator must consider that the remedy
action to synchronize the PCell and the ESCell can negatively impact the NRCellDU MO. If the impact on the PCell and the internal
SCell is determined to be too great, the operator can decide not to lock and unlock the ESCell.

At inconsistent configuration, when the [Link] attribute is set from true to false, single outer loop link
adaptation is applied in the ESCell and dual outer loop adjustment is applied in the PCell. ESCell uses the outer loop adjustment value for slots
impacted by mixed LTE and NR interference until the alarm is cleared. When the [Link] attribute is set
from false to true, the PCell calculates the single outer loop adjustment value and transfers the value to the ESCell.

Slot-Specific Downlink Link Adaptation

SINR backoff and the disabling of outer-loop adjustment target NR inter-cell interference, not LTE CRS interference.
Too many slots must not be configured to disable outer-loop adjustment. For example, all MBSFN slots must not be configured to disable
outer-loop adjustment, as MBSFN outer-loop stops working as a result of such configuration.
Slot-specific downlink link adaptation is not supported in High-Band cells.
The SINR backoff configuration and the disabling of the outer-loop adjustment are not applied to the link adaptation in ESCells. PM events
and PM counters are not stepped with HARQ feedback in cells used as ESCells.

Related concepts
LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation Overview
O&M Aspects of LTE-NR FDD Spectrum Sharing with Dual Outer Loop Link Adaptation
3.2.10 Configuration of Symbol Allocation for the LTE PDCCH
Using higher CFI results in the allocation of more symbols for the LTE PDCCH in a subframe, which can mitigate the interference from
neighbor cells.

Setting the [Link] attribute to CFI_AUTO_MAXIMUM_3 is recommended. With this setting, the CFI mode is
adjusted dynamically depending on the NR and LTE traffic load, allocating up to three symbols for the LTE PDCCH in a subframe.

An alternative setting is available that enforces the use of more PDCCH symbols. Setting the [Link] attribute to
CFI_STATIC_3 can mitigate reception failure due to interference from neighbor cells.

3.2.11 PDCCH Link Adaptation Adjustment

Setting the [Link] attribute enables a more accurate CQI report for UEs, both in higher and lower LTE
interference conditions.

Configuration Possibilities
For a given UE, the performance impact depends on the level of LTE interference from neighbor cells.
UE with Low The CQI error rate is expected to be low, but the default [Link] attribute value might be too
LTE conservative for the radio conditions. When the [Link] attribute is set to NO_OLA, the
Interference estimated PDCCH SINR for the UE tends to be too conservative. This leads to higher CCE aggregation level and more
PDCCH resource utilization. However, since the estimated PDCCH SINR for the UE is too conservative, the PDCCH error
rate for the UE can be low compared to the target error rate.
When the [Link] attribute is set to PDSCH_OLA, a less negative value for the
[Link] can be configured. The result is that the PDCCH SINR for the UE becomes less
conservative. This leads to lower CCE aggregation level and lower PDCCH resource utilization and an increase in PDCCH
error rate for the UE, resulting in an error rate closer to the target.

UE with Strong The reported CQI can be too optimistic, and it is not possible to sufficiently correct for it even with a more negative value
LTE for the [Link] attribute. When the [Link] attribute is set to
Interference NO_OLA, the estimated PDCCH SINR for the UE can still be too aggressive. This leads to lower CCE aggregation level and
lower PDCCH resource utilization. However, since the estimated PDCCH SINR for the UE is too aggressive, the PDCCH
error rate for the UE can be well above the target error rate of 1%.
When the [Link] attribute is set to PDSCH_OLA, a less negative value for the
[Link] attribute can be configured. The strong LTE interference results in a large negative
PDSCH outer loop adjustment. Since the PDSCH outer loop adjustment is included in the estimated PDCCH SINR, the
estimation is more accurate, or not as aggressive, as without the PDCCH link adaptation adjustment. This leads to higher
CCE aggregation level and higher PDCCH resource utilization. However, the PDCCH error rate for the UE drops, becoming
closer to the target error rate.

External SCell Behavior in ESS

Setting the [Link] attribute enables adjustment of the PDCCH SINR on the external SCell.

Performance and Observability

The impact on PDCCH error rate can be monitored through the following PM counters:

– [Link]

– NRCellDU.pmMacHarqDlAck16Qam

– NRCellDU.pmMacHarqDlAck64Qam

– NRCellDU.pmMacHarqDlAck256Qam

– [Link]

– NRCellDU.pmMacHarqDlNack16Qam

– NRCellDU.pmMacHarqDlNack64Qam

– NRCellDU.pmMacHarqDlNack256Qam

– [Link]

– NRCellDU.pmMacHarqDlDtx16Qam

– NRCellDU.pmMacHarqDlDtx64Qam

– NRCellDU.pmMacHarqDlDtx256Qam
 – [Link]

– NRCellDU.pmMacHarqUlAck16Qam

– NRCellDU.pmMacHarqUlAck64Qam

– NRCellDU.pmMacHarqUlAck256Qam

– [Link]

– NRCellDU.pmMacHarqUlNack16Qam

– NRCellDU.pmMacHarqUlNack64Qam

– NRCellDU.pmMacHarqUlNack256Qam

– [Link]

– NRCellDU.pmMacHarqUlDtx16Qam

– NRCellDU.pmMacHarqUlDtx64Qam

– NRCellDU.pmMacHarqUlDtx256Qam

The PDCCH blocking can be monitored through the following PM counters:

– [Link]

– [Link]

The PDCCH resource utilization can be monitored through the following PM counters:

– [Link]

– NRCellDU.pmMacRBSymUsedPdcchTypeAAggrLvl1

– NRCellDU.pmMacRBSymUsedPdcchTypeAAggrLvl2

– NRCellDU.pmMacRBSymUsedPdcchTypeAAggrLvl4

– NRCellDU.pmMacRBSymUsedPdcchTypeAAggrLvl8

– NRCellDU.pmMacRBSymUsedPdcchTypeAAggrLvl16

3.3 Monitor
Observe the network behavior and node status to be able to detect and resolve potential problems.

Monitor the ESS-dedicated and related alarms and KPIs, and perform regular health checks to keep control of the network condition.

Back to ESS Operational Flow.

3.3.1 Detect and Resolve

Troubleshoot and clear alarms with the help of the alarm instructions.

Note: In fault handling/propagation for LTE ESS cells, the dependency on a successful parameter exchange between LTE and NR takes
precedence over dependencies to local FRU resources.

Table 83 ESS-specific Alarms

RAT Alarm OPI MO Class

EUtranCellFDD
LTE/NR ESS Inconsistent Configuration NRCellDU
SectorCarrier
EUtranCellFDD
LTE/NR ESS Service Degraded
NRCellDU
EUtranCellFDD
LTE/NR ESS Service Unavailable
NRCellDU

Table 84 ESS-related Alarms

 RAT Alarm OPI MO Class
NR Configuration Requires Feature Activation NRCellDU
EUtranCellFDD
LTE/NR Inter-Node Feature Incompatibility
NRCellDU
MO Configuration Not Consistent With Installed
LTE SectorCarrier
Equipment
MO Configuration Requires Key Install and Feature
NR NRCellDU
Activation
NR MO Configuration Exceeds Resources Enabled by the Key NRCellDU
EUtranCellFDD
LTE/NR SW Error SectorCarrier
NRSectorCarrier
NRCellDU
NR MO Configuration Pending Action
NRSectorCarrier
NR Inter-Node Carrier Aggregation Service Degraded ExtGNBDUPartnerFunction

Back to ESS Operational Flow.

[Link] View Alarms

View alarm details for a node or a node collection using the ENM Alarm Monitor.

Required Tools and Equipment

ENM

Prerequisites
ENM User Role: FM_Administrator or FM_Operator

Steps

1. Launch Alarm Monitor.

2. Add or select the required nodes from the Network Elements list.

3. Click Apply. The Alarms table is updated with all the alarms related to the applied Network Elements.
Select View Summary or View OPI for further details.

3.3.2 Manage Performance

Monitor the performance of the network to decide on optimization in the network evolution plan. The ESS-dedicated KPIs as well as the
aggregated PM data of the individual RATs enable observing the spectrum sharing group.

The ESS KPIs include generic KPI set applicable to all ESS scenarios, and additional SA-dedicated KPIs.

Back to ESS Operational Flow.

[Link] ESS KPIs

The ESS-generic KPIs and counters applicable regardless of the ESS migration scenario.

The [Link] attribute can be set to a value that is the combined names of the LTE and NR cells used in the ESS cell pair.
In this case, KPI post-processing has easier access to the counters used for KPI calculations.

Table 85 ESS Key Performance Indicators

KPI RAT Formula

Normalized Average DL MAC Cell Throughput in ESS [Link] / maximum value of
(expressed in Mbps) either [Link] or
LTE
[Link], depending on
which value is higher
NR (0.008 × [Link]) / maximum value of either
[Link] or
KPI RAT Formula
[Link], depending on
which value is higher
([Link] + 0.008 ×
[Link]) / maximum value of either
ESS [Link] or
[Link], depending on
which value is higher
(0.008 × [Link]) /
NR
[Link]
Normalized Average UL MAC Cell Throughput in ESS
(expressed in Mbps) ([Link] + 0.008 ×
ESS [Link]) /
[Link]
[Link] / Normalized Average UL
MAC Cell Throughput Considering Successful PUSCH Slot Only
LTE
in ESS (expressed in
Mbps)[Link]
[Link] /
LTE
[Link]
Average Overall DL Latency (expressed in ms) (([Link] +
[Link]) / 8) /
NR
([Link] +
[Link])
100 × ([Link] +
[Link] +
Average DL PRB Utilization LTE [Link] +
[Link]) /
[Link]
Calculated based on the following PIs related to PRB
NR utilization: 100 × [Link] /
[Link]
Calculated based on the following PIs related to PRB
Average DL PRB Utilization in ESS utilization: 100 × ([Link] +
[Link] +
ESS [Link] +
[Link] +
[Link]) /
[Link]
100 × [Link] /
Average UL PRB Utilization LTE
[Link]
Calculated based on the following PIs related to PRB
NR utilization: 100 × [Link] /
[Link]
Average UL PRB Utilization in ESS Calculated based on the following PIs related to PRB
utilization: 100 × ([Link] +
ESS
[Link]) /
[Link]
[Link] -
Blockage on LTE due to NR PDCCH Reserved PRBs NR [Link] -
[Link]

Table 86 ESS Performance Indicators

PI RAT Formula
DL HARQ Rate Total NR 100 × ([Link] +
NRCellDU.pmMacHarqDlAck16Qam +
NRCellDU.pmMacHarqDlAck64Qam +
NRCellDU.pmMacHarqDlAck256Qam) /
([Link] +
[Link] +
[Link] +
NRCellDU.pmMacHarqDlAck16Qam +
NRCellDU.pmMacHarqDlNack16Qam +
NRCellDU.pmMacHarqDlDtx16Qam +
NRCellDU.pmMacHarqDlAck64Qam +
NRCellDU.pmMacHarqDlNack64Qam +
PI RAT Formula
NRCellDU.pmMacHarqDlDtx64Qam +
NRCellDU.pmMacHarqDlAck256Qam +
NRCellDU.pmMacHarqDlNack256Qam +
NRCellDU.pmMacHarqDlDtx256Qam)

ESS Counters
The following PM counters related to throughput and PRB utilization are associated with this feature:

– [Link]

– [Link]

– [Link]

– NRCellDU.pmMacRBSymUsedPdcchTypeBAggrLvl1

– NRCellDU.pmMacRBSymUsedPdcchTypeBAggrLvl2

– NRCellDU.pmMacRBSymUsedPdcchTypeBAggrLvl4

– Normalized Average UL MAC Cell Throughput Considering Successful

NRCellDU.pmMacRBSymUsedPdcchTypeBAggrLvl8

– NRCellDU.pmMacRBSymUsedPdcchTypeBAggrLvl16

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

Note: In ESS cells, LTE and NR PM counters related to resource utilization do not reflect the actual utilization of LTE and NR.
The following PM counters provide observability on throughput performance in an ESS cell pair:

– [Link]

– [Link]

The following NR PM counters provide observability on EN-DC – NR standalone coexistence in the same NR cell:

– [Link]

– [Link]

– [Link]

– [Link]
 – [Link]

– [Link]
The following PM counters provide observability on PRB utilization on the NR PDSCH in MBSFN subframes:

– [Link]

– [Link]

The average number of used PRBs in all slots can be calculated with the following formula: [Link] / (15 × 60
× 1000)
The average number of used PRBs in MBSFN subframes can be calculated with the following formula:
[Link] / (15 × 60 × 1000 × percentage of MBSFN subframes)
The average number of used PRBs in non-MBSFN subframes can be calculated with the following formula:
([Link] - [Link]) / (15 × 60 × 1000 × (1- percentage of MBSFN
subframes))
The following PM counters help with tuning the number of MBSFN subframes by improving the observability of NR MCS distribution:

– NRCellDU.pmRadioPdschTable1MbsfnMcsDistr

– NRCellDU.pmRadioPdschTable2MbsfnMcsDistr

Note: The NR MCS distribution for non-MBSFN subframes can be calculated using these PM counters together with the
NRCellDU.pmRadioPdschTable1McsDistr and the NRCellDU.pmRadioPdschTable2McsDistr PM counters.
Due to additional overhead in the NR cell in non-MBSFN subframes, the distribution of NR MCS in non-MBSFN subframes is expected to be
three bins lower than in MBSFN subframes. However, if the difference is more than three bins, expectation is not fulfilled because of
interference from LTE cells, see Optimization of MBSFN Subframe Configuration for LTE and NR Interference Reduction.
The following PM counters continue to increase even when the LTE cell is in power saving mode with the Cell Sleep Mode feature active:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

Related reference
ESS KPIs for NR SA

[Link].1 ESS KPIs for NR SA

Additional KPIs, PIs and Counters dedicated to NR SA only.

Table 87 Key Performance Indicators for NR SA Random Access and RRC Establishment Success Rate Performance Observability

KPI RAT Description

100 × (NRCellDU.pmRadioRaCbSuccMsg3 /
CBRA Success Rate NR
[Link])
100 × ([Link] /
RRC Establishment Success Rate NR
[Link])
100 × ([Link] /
RRC Establishment Success Rate MOS NR ([Link] -
[Link]))

Table 88 Key Performance Indicators for NR SA Data Transfer Performance Observability

KPI RAT Description

DRB Accessibility Success Rate for Mapped 5QI NR (([Link] -
[Link]) /
([Link] -
([Link] +
[Link]))) ×
(([Link] -
[Link]) /
KPI RAT Description
([Link] -
[Link])) ×
(NRCellCU.pmDrbEstabSucc5qi /
NRCellCU.pmDrbEstabAtt5qi) × 100
(NRCellCU.pmDrbRelAbnormalGnbAct5qi +
NRCellCU.pmDrbRelAbnormalAmfAct5qi /
DRB Retainability Percentage Lost per Mapped 5QI NR (NRCellCU.pmDrbRelNormal5qi +
NRCellCU.pmDrbRelAbnormalGnbAct5qi +
NRCellCU.pmDrbRelAbnormalAmfAct5qi)) × 100
(NRCellCU.pmDrbRelAbnormalGnbAct5qi /
DRB Retainability Percentage Lost per Mapped 5QI (gNodeB (NRCellCU.pmDrbRelNormal5qi +
NR
triggered only) NRCellCU.pmDrbRelAbnormalGnbAct5qi +
NRCellCU.pmDrbRelAbnormalAmfAct5qi)) × 100

PIs

Table 89 Performance Indicators for NR Paging Discard Rate Observability

PI RAT Description
[Link] /
Paging Discard Rate on gNodeB-CU NR
[Link] × 100
GNBDUFunction.pmPagF1Discarded /
Paging Discard Rate on gNodeB-DU NR
GNBDUFunction.pmPagF1Received × 100
[Link] /
Paging Discard Rate on Cell Level NR
[Link] × 100

Table 90 Performance Indicators for Resource Monitoring of Average and Maximum Number of Users in NR

PI RAT Description
Depending on whether the information is generated on cell
level or node level, the following formulas apply:
– Cell level:
Average Number of RRC Connected Users, EN-DC UE [Link] /
NR
Connections [Link]

– Node level:
[Link] /
[Link]

Depending on whether the information is generated on cell

level or node level, the following formulas apply:
– Cell level:
Average Number of RRC Connected Users (for NR SA UE [Link] /
NR
connections) [Link]

– Node level:
[Link] /
[Link]

The following counters give information on this PI:

Max Number of RRC Connected Users, EN-DC UE
NR – [Link]
Connections
– [Link]

The following counters give information on this PI:

Max Number of RRC Connected Users (for NR SA UE
NR – [Link]
connections)
– [Link]

Counters
The following NR latency counters can be aggregated with LTE latency counters to produce ESS performance data:

– [Link]
 – [Link]

– [Link]

– [Link]
The following NR counters provide paging performance observability:

– [Link]

– [Link]

– GNBDUFunction.pmPagF1Received

– GNBDUFunction.pmPagF1Discarded

– [Link]

– [Link]

The following NR counters provide observability on EN-DC – NR standalone coexistence in the same NR cell:

– [Link]

– [Link]

– [Link]

– [Link]

Related reference
ESS KPIs

[Link] View KPIs

Create a KPI monitor on a specified NE collection using the ENM Node Monitor.

Required Tools and Equipment

ENM

Prerequisites
ENM User Role: NHM_Administrator or NHM_Operator

Steps

1. Launch the ENM Node Monitor application.

2. Select the relevant NE collection in the Network pane.

3. Create a KPI viewer widget using the Add a Widget button in the top menu.

4. Use the Settings icon to add KPIs to be monitored by the KPI Viewer.

Results
The selected KPIs can now be observed for the NE collection.

3.3.3 Prevent
Prevention activities allow early identification of potential problems in the ESS-enabled network.

Run regular health checks of the ESS-enabled nodes and collect data to support effective troubleshooting.

Back to ESS Operational Flow.

[Link] Perform Health Check

Check the state of a Network Element for general troubleshooting and maintenance purposes, using the ENM Node Health Check wizard.

Required Tools and Equipment

– ENM
 Prerequisites
Required roles and access rights:

– ENM User Role: nhc_Administrator

– Node access rights: Target Based Access Control rights

Other prerequisites:

– A separate collection is available for the node with the domain and type set to System Local.

– CmNodeHeartbeatSupervision is ON for the required nodes.

– CM Synchronization Status: SYNCHRONIZED

Steps

1. Launch the Node Health Check application and click Setup & Run Report.

2. Define the report in Report Details.

3. Select the node for the health check in Node Selection.

4. For the health check configuration, select TROUBLESHOOT from the drop-down menu.

5. Define the schedule for the report: set the Start value to Execute immediately.

6. Review the report configuration in the Summary and click Finish.

Results
The Node Health Check report is displayed in the Reports table. The report execution starts immediately after creation. When ready, the status
changes to COMPLETED.

After This Task

For status other than HEALTHY, analyze the health check result. The report can be exported to a CSV file. Clear all the alarms and issues listed
before proceeding.
Use the Report Comparison page to compare different reports.

[Link] Collect DCG Package

Collect troubleshooting data that is to be enclosed in a Customer Service Request (CSR) in case of an installation failure.

Perform all data collection as soon as possible, before any recovery is attempted, as the recovery procedure results in some logs and statistics
being overwritten. Collecting Data Collection Guideline (DCG) package is the preferred data collection method. If that is not possible, the
Ericsson Support Information (ESI) package is also acceptable.

Steps

1. Fetch the DCG package, using command dcgm in Element Management Command Line Interface (EMCLI).

2. Save the file produced by the dcgm command, to be able to attach it to the CSR if the installation is not successful.
If it is not possible to log on to the node, perform data collection by the Emergency Access, see Data Collection Guideline for details.

3.4 Decommission
Activities performed in the end of ESS support phase.

3.4.1 Deconfigure ESS

The procedure includes example steps to return from ESS to non-ESS mixed mode configuration.

Consider changing the setting of any other attributes configured for ESS, depending on the network-specific conditions.

Steps

1. Set the [Link] and the [Link] attributes to LOCKED.

2. Set the [Link] attribute to LOCKED.

 3. Set the [Link] attribute to LOCKED in the ESS cell pair.

4. Set the [Link] attribute to LOCKED in the ESS cell pair.

5. Delete the EUtranCellRelation MO under the NRCellCU MO.

6. Delete the ExternalEUtranCell=LTE-ESS MO class.

7. Set the following attributes to the appropriate value:

– [Link] to false

– [Link] to false

– [Link] to 0

– [Link] to 0

– [Link] to empty

8. Set the following attributes to the appropriate value at the same time:

– [Link] to empty

– [Link] to 0

9. Set the [Link] attribute to false.

10. Set the [Link] attribute to false if the Downlink Data and DMRS Multiplexing (FAJ 121 5336) feature is
not activated.

If only one standard is needed, do the following:

11. Remove the standard that is not needed.

For more information, see Remove Standard from Mixed Mode Baseband in Mixed Mode All-In-One User Guide.

If both NR and LTE are needed, do the following:

12. Use the [Link] action.

Note: The frequency for the NR cell and the LTE cell must differ if ESS is not enabled.

13. Set the following attributes according to the network design:

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

If the NR SSB frequency changes, do the following:

14. Recreate the following MOs according to handover and carrier aggregation configurations:

– NRFrequency

– NRFreqRelation

– NRCellRelation

15. Set the [Link] attribute to UNLOCKED.

16. Set the [Link] attribute to UNLOCKED.

17. Set the [Link] attribute to UNLOCKED.

18. Set the following retuning attributes to the desired value:

 – [Link]

– [Link]

19. Create the GUtranFreqRelation and the GUtranCellRelation MOs for the anchor nodes.
See ESS Solution Guidelines for more information on selecting the LTE anchor carrier nodes.

20. Optional: Remove the old GUtranFreqRelation MO.

21. Update the GUtranFreqRelation.endcB1MeasPriority attribute with the new SSB frequency.

22. Delete all the intra- and inter-gNodeB neighbor relations and recreate them with the updated SSB frequency.

23. Optional: If NR standalone is used, define the cell reselection mobility priorities with the new SSB frequency.

24. Optional: Delete the old EUtranFreqRelation MO if no longer needed.

25. Set the [Link] and the [Link] attributes to UNLOCKED.

4 Appendix
4.1 ESS Deployment Examples
Many ESS deployment scenarios are possible, depending on the overall network evolution plan and the specific network design created for
a site.

4.1.1 Hardware Reuse in a Legacy RAN Site

In this example, ESS is introduced in an existing RAN setup. The site is rearranged, NR-capable Baseband units are upgraded and
configured to handle ESS cell pairs, and the remaining legacy traffic is delegated to the other Baseband nodes.

Legacy Setup
The example site consists of:

– One LTE Baseband unit with two LTE radio units

– One Mixed Mode Baseband unit with two LTE radio units and one WCDMA radio unit

– One LTE Baseband unit with 15 LTE radio units

The setup is illustrated in Figure 37.

LTE
I LTE
Radio
2 CPR Radio
LTE
Baseband

LTE
LTE
Radio
Radio
WCDMA
Radio

I
PR
3C
Fronthaul

Site Mixed Mode

Router Baseband
LTE
LTE
Radio
Radio
LTE
Radio
RI
CP
15

LTE
Baseband

LTE
LTE
Radio
Radio
LTE
Radio
Legend
LTE
WCDMA
L0003742B

Figure 37 Example RAN Site Before ESS Introduction

Rearranging the Site to Prepare for ESS

 To fully utilize the available hardware and prepare for ESS, the following strategy should be applied:

– Baseband units designated to handle mixed LTE and NR traffic must be ESS-compliant and the software needs to be upgraded to a
version, which supports Mixed Mode Baseband, that is 20.Q1 or later.

– If a Baseband, which does not support ESS, is available, it can be introduced to handle the existing WCDMA or LTE capacity.

– Maximum cell capacity and RI port capacity limits must be considered for the installed Baseband units after the rearrangement. If the
limits are exceeded, a new Baseband must be introduced to the setup.

– Transport Network must be reconfigured for Mixed Mode Baseband IP connectivity.

– Time synchronization must be prepared on the site.

For more information, see ESS Solution Guideline.

LTE
Radio
LTE
RI Radio
5 CP

LTE
Baseband

LTE
LTE
Radio
Radio
LTE
Radio
Fronthaul

5 CPRI

Mixed Mode LTE

Site Baseband LTE
Radio
LTE
Router Radio
WCDMA
Radio
LTE
Radio
Radio

LTE
LTE
Radio
RI Radio
LTE
9 CP
Radio
Mixed Mode
Baseband

Legend
LTE LTE
NR LTE
Radio
WCDMA Mixed Mode
Radio
ESS Enabled Radio

L0003743B

Figure 38 Example RAN Site After ESS Introduction

Radios in ESS
ESS enables NR and LTE within the same spectrum by using the Mixed Mode Radio feature. The Mixed Mode Radio feature is required for both
LTE (FAJ 121 0906) and NR (FAJ 121 4945). The following strategies can be applied:

– The bands can be modernized and the existing LTE spectrum can be proposed as the spectrum for ESS.

– The already deployed NR-capable radio units can be reused for the ESS with software and HWAC upgrade.

4.1.2 Hardware Expansion in a High Capacity RAN Site

In this example, ESS is introduced in an existing site. The site is expanded with additional radio units and new Baseband units.
In this example configuration, the site consists of a single Baseband unit with LTE traffic and 15 LTE radio units. To enable the introduction of
ESS in this site, the capacity of the site must be increased. With an extra Baseband unit, the site can support more than 12 cells in Mixed Mode
configuration, including the cells allocated to ESS. Furthermore, the addition of the second Baseband unit enables the option of inter-
Baseband carrier aggregation. These Baseband units can be connected through a Router 6000 unit in an E-RAN configuration. If the site
configuration requires additional RI ports to meet the capacity requirements, a Baseband R503 can be used to expand the CPRI ports.

LTE
LTE
Radio
Radio
LTE
Radio

LTE
LTE
Radio
Radio
LTE
Radio
I
R
CP
15

Fronthaul

LTE
LTE LTE
Site Radio
Baseband
Router Radio
LTE
Radio

LTE
LTE
Radio
Radio
LTE
Radio

LTE
LTE
Radio
Legend Radio
LTE
LTE
Radio

L0002990B

Figure 39 Site Configuration before Expansion to ESS

The next step before introducing ESS is to plan cell allocation for the ESS carriers. Some of the legacy LTE radio units need to be replaced, or
upgraded to ESS-capable units. In this example, three radios are replaced with units that support Mixed Mode Radio.
 LTE
LTE
Radio
Radio
LTE
Radio

LTE
LTE
Radio
Radio
LTE
Radio

RI
CP
9

Fronthaul
LTE
Mixed Mode LTE
Site Radio
Baseband
Router 3C Radio
LTE
PR Radio
I

LTE
LTE
Radio ESS
LTE & NR
Radio
Mixed Mode
Radio

3 CPRI
Legend LTE
LTE LTE
LTE Radio
Baseband
NR Radio
LTE
ESS Enabled Radio

L0002991B

Figure 40 Site Configuration after Expansion to ESS

After the expansion, the Baseband units and the radios support Mixed Mode configurations for LTE and NR, and ESS can be enabled.

4.1.3 Radio Gateway

The Master Node, which is the LTE anchor carrier, and the Secondary Node, which is the ESS NR carrier, are deployed in the same LTE + NR
Mixed Mode Baseband unit with the support of Radio Gateway R608. Between the Mixed Mode Baseband unit and the Radio Gateway R608
unit, a minimum of one and a maximum of four eCPRI links are supported, depending on capacity. Massive IoT is supported on carriers of
dedicated radios and also on the ESS carrier of the Mixed Mode Radio. For more information, see Category M Guideline, NB-IoT Guideline in
the Massive IoT CPI library.
 Master Node

LTE
Radio

EN-DC

1 eCPRI 3 CPRI
Mixed Mode
Baseband
Radio Gateway LTE
R608 Secondary Node
ESS enabled Mixed Mode
Radio
Radio
ESS enabled

LTE
Legend Radio
NR
Radio
LTE
NR
ESS Enabled

L0003465C

Figure 41 Master Node and Secondary Node in the Same Baseband with Radio Gateway R608 - Star Topology

4.1.4 LC-05 9xCPRI in Conversion Mode with Router 6673

The Master Node, which is the LTE anchor carrier, and the Secondary Node, which is the ESS NR carrier, are deployed in the same LTE + NR
Mixed Mode Baseband unit with the support of Fronthaul Router 6673 with LC-05 9xCPRI in Conversion mode. Between the Mixed Mode
Baseband unit and the Router 6673, a minimum of one and, considering capacity, a maximum of four eCPRI links are supported per LC-05
9xCPRI card. Massive IoT is supported on carriers of dedicated radios and also on the ESS carrier of the Mixed Mode Radio. For more
information, see Category M Guideline, NB-IoT Guideline in the Massive IoT CPI library.

Master Node

LTE
Radio

EN-DC
Packet Fronthaul

1 eCPRI 3 CPRI
Mixed Mode
Baseband
Radio Gateway LTE
R608
ESS enabled Mixed Mode Secondary Node
Radio
Radio
ESS enabled

LTE
Radio
LTE
Radio
Legend
LTE
NR
ESS Enabled
L0003541B

Figure 42 Master Node and Secondary Node in the Same Baseband with Fronthaul Router 6673 and LC-05 9xCPRI - Star Topology
 Legal | © Ericsson AB 2020–2025
Copyright © Ericsson AB 2020–2025. 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.

Trademarks All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark
Information.