WRAN 21Q4 Network Impact Report

Network Impact Report
WCDMA
18/109 48-HSD 101 02/1 Uen LJ

Copyright
© Ericsson AB 2017-2021. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Contents
Contents
1 Introduction 1
1.1 Related Information 2
2 Released Functions 4
2.1 New Features 4
2.2 Mandatory Impact at Upgrade 14
2.3 Optional Impact at Upgrade 123
3 Planned Functions 174

3.1 New Features 174
3.2 Mandatory Impact at Upgrade 176
3.3 Optional Impact at Upgrade 185
4 Parameters 191
4.1 RNC RN Parameters 20.Q2 191
4.2 RNC TN Parameters 20.Q2 192
4.3 DU RN Parameters 20.Q2 192
4.15 DU TN Parameters 21.Q3 205
5 Counters 207
5.1 RNC Counters 20.Q2 207
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

5.3 DU Counters 20.Q4 212

6 Alarms 217
6.1 RNC Alarms 20.Q2 217
6.2 RNC Alarms 21.Q2 217
7 KPIs 219
8 GPEH 220
8.1 GPEH 20.Q2 220
8.2 GPEH 21.Q1 220
8.3 GPEH 21.Q4 221
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Introduction
1 Introduction
The Network Impact Report (NIR) describes the new and enhanced
features and how they affect the operator's network. This document
presents the changes introduced in W20.Q1 and later releases.
Content of the Network Impact Report (NIR) is a subject to change. New features
and additional information are added as more details are available.
The Network Impact Report includes delta information for parameters, counters,
alarms, KPIs and General Performance Event Handling (GPEH).
How to Read This Document

The purpose of the NIR is to provide information to support the introduction of
new features and upgrades to the network.
The NIR is split into the following two main sections:
— Under Released Functions, all globally released and unrestricted features

and changes are described.
— Under Planned Functions, unreleased features are described to provide early

information.
Each main section is further divided into the following three subsections, where
every new feature and upgrade has its own separate section:
— The New Features section includes a brief description of all the newly
introduced features. For more information about a specific feature, refer to
the Feature Description.
— The Mandatory Impact at Upgrade section includes all changes that are
automatically enabled in the network after the software upgrade. These
include the description of the change, as well as the impact on capacity,
counters, KPIs, alarms, parameters and other operational aspects.
— The Optional Impact at Upgrade section includes all changes that the
operator can manually enable after the software upgrade. These include the
description of the change, as well as the impact on capacity, counters, KPIs,
alarms, parameters and other operational aspects.
Delta information for parameters, counters, alarms, KPIs and General

Performance Event Handling (GPEH) can be found in the separate chapters at
the end of this document.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 1

1.1 Related Information

Sources of information regarding licensing, compliance to 3GPP interfaces,
compatibility with external nodes, Key Performance Indicators and delta.
License and Hardware Activation Codes

Information about License and Hardware Activations for Ericsson Software
Model can be found in the following documents:
Table 1 Licenses and Hardware Activation Codes

Document Number Description
Licenses and Hardware Activation Codes 251/1553-HSD 101 02/1 Uen Ericsson Software Model
in Ericsson Software Model
Ericsson Software Model Base and Value 250/1553-HSD 101 02/1 Uen Lists the included features in each Base
Packages and Value Package
Compliance and Compatibility

Information about compliance to 3GPP interfaces and compatibility with
external nodes can be found in the following documents:
Table 2 Compliance and Compatibility

Compliance and Compatibility 140/1551-HSD 101 02/1 Uen Describes the compliance to 3GPP
interfaces and compatibility with external
nodes.
Basic Features 218/1553-HSD 101 02/1 Uen A table included in the document shows
which features are supported on RNC, DU
Radio Node and Baseband Radio Node.
Optional Features 219/1553-HSD 101 02/1 Uen A table included in the document shows
which features are supported on RNC, DU
Radio Node and Baseband Radio Node.
Key Performance Indicators

KPIs that are referenced to in this document can be found in the following
document:
Table 3 Key Performance Indicators

Radio Network KPI 120/1553-HSD 101 02 Uen Contains defined KPIs for Ericsson
WCDMA RAN.
2 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Introduction
Delta Information
Table 4 Delta Information

Lists and Delta Lists Baseband 189/006 51-LZA 701 6014 This document is included in
Baseband Radio Node library
only.
1.1.1 Software Support for RBS3000 with DUW
W17.Q4 is the last software release to support RBS3000 with DUW.
For W18.Q1 or later software release, RBS3000 with DUW is not supported.
Note: — Unexpected failures may occur if RBS3000 with DUW is upgraded

to W18.Q1 or later software release.
— Potential problems may exist if RBS3000 with DUW runs with a

software version of W18.Q1 or later software release.
1.1.2 Software Support for RNC 3820
W19.Q2 is the latest software release where RNC 3820 is supported.
For W19.Q3 or later software releases, RNC 3820 is not supported and any
attempt to upgrade RNC 3820 with that software fails.
Customers wishing to continue to use RNC 3820 can operate on W19.Q2

software as long as it is under maintenance.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 3

2 Released Functions
2.1 New Features

Overview information about the globally released and unrestricted new features.
For more information about the features, see the feature description documents.
2.1.1 EvoC RNC Geo-Redundancy Overview
The EvoC RNC Geo-Redundancy feature provides an emergency

redundancy solution for two or more RNCs, without a need to deploy
additional hardware. The operator can configure unlimited number of RNCs
with this feature.
Access Type: WCDMA

Feature Identity: FAJ 121 5182 R3
Value Package Name: EvoC RNC Geo-Redundancy
Value Package Identity: FAJ 801 1342 R3
Node Type: RNC
Licensing: Licensed feature. One license for each node.
Summary
The EvoC RNC Geo-Redundancy feature provides fast traffic recovery if an EvoC
RNC fails. The restoration of traffic is based on the manual Iub switchover
operation.
Geo-redundancy can be configured in two ways:

— Using MO actions directly on an RNC node (recommended)
— Using the gr command in AMOS
The feature has the following benefits:
— Provides fast recovery of traffic.
— Minimizes the service interruption time.
— Redundancy support for unlimited number of RNCs in the network.
The feature supports the following configurations:
4 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— EvoC 8300 and EvoC 8300
— EvoC 8300 and EvoC 8200/RNC
— EvoC 8200/RNC and EvoC 8200/RNC
Additional Information
For more information, see Configure Geo-Redundancy.
2.1.2 Call Re-establishment for PS Overview
The Call re-establishment for PS feature enables re-establishment of a PS

connection.
Access Type WCDMA

Feature Identity: FAJ 121 5151
Value Package Name: Enhanced Voice Retainability
Value Package Identity: FAJ 801 0307
Node Type: RNC
Licensing: License required
Summary
This feature improves the experience of the end-user and PS drop rate KPI, by
preventing PS connections from being released.
The Call Re-establishment for PS feature decreases the call drop by using
automatic re-establishment of Packet Switch (PS) Radio Access Bearer (RAB). It
reduces the PS drop rate when the User Equipment (UE) loses the radio
connection.
This feature enables the UE to request re-establishment of a PS connection when

loss of DL synchronization or an unrecoverable Radio Link Control (RLC) error is
detected.
The connection can also be re-established for:

— Ongoing procedure of PS RAB establishment from standalone SRB and on
top of one or more existing RABs
— Standalone SRB (no ongoing procedure exists)
DL NAS message can also be retransmitted to UE after successful CRE if it did not
reach UE because of poor radio conditions.
Feature Benefits
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 5

— Improves PS-retainability and accessibility.
— Expands CRE supported RAB combinations.
Feature introduces support for the following RAB combinations:
— n x PS RAB
— CS + n x PS RAB
2.1.3 Garbled Speech Elimination Overview
Validation of UL AMR frames enables detection and correction of garbled

speech occurrences.
Access Type WCDMA

Value Package Name: HD Voice
Node Type: RNC
Licensing: Licensed feature.
Summary
The Garbled Speech Elimination feature introduces validation of active UL AMR
speech frames, so it is possible to detect an occurrence of garbled speech and
apply correcting measures.
Garbled speech means incomprehensible voice that is caused by encryption or

decryption parameters mismatch between RNC and UE. This behavior can be
caused by for example poor radio conditions and have severe impact on the
quality of speech.
This feature improves observability in speech quality area by introducing PM

counters and UE-specific traces which can help troubleshooters to find root-
cause of the problems in speech area.
2.1.4 User Profile Based Mobility Overview
This feature controls UE mobility to LTE based on UeMobilityProfile MO

instances created on RNC. Mobility to LTE, both in idle mode and in
connected mode, can be prioritized or blocked.
Access Type WCDMA
6 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Value Package Name: Traffic Management Advanced WCDMA-LTE
Node Type: RNC
Licensing: Licensed feature. One license is required for each
node.
Summary
The User Profile Based Mobility feature is capable of steering groups of UEs by
allowing, preventing, or prioritizing the mobility to LTE. As a result, the feature
offers the following benefits:
— Flexible configuration of mobility to LTE.
— Reduced unnecessary signaling.
— Improved speech accessibility by reducing the number of paging outages

caused by futile attempts to access the LTE network.
— Improved packet switch retainability by reducing the interruption of data

transmissions.
The User Profile Based Mobility feature allows the operator to:
— Grant exclusive E-UTRAN frequency access for a selected group of users
based on the IMSI number or Core Network operator.
— Provide better performance for UEs with WCDMA-only subscription. The

WCDMA-only subscribers must belong to the same IMSI series.
— Keep roaming users in WCDMA. Roaming users might not be allowed to

access E-UTRAN according to roaming agreement.
— Control mobility of UE groups toward LTE networks in order to meet the

subscriber mobility strategy of the operator.
— Block the sending of RRC UTRAN MOBILITY INFORMATION messages for

certain UE groups.
2.1.5 Preferred Mobility at CS Fallback Return to LTE Overview
The feature provides the ability to set the preferred method of redirection or
handover of CS Fallback users to LTE.
Feature Name: Preferred Mobility at CS Fallback Return to LTE

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 7


Node Type: RNC
Licensing: Licensed feature. One license per RNC.
Access Type WCDMA
Summary
The feature introduces a more flexible handling method for CS fallback return to
LTE by omitting unwanted mobility features. This feature is only triggered when
the UE is about to be redirected from WCDMA to LTE using the
csFallbackCsRelease trigger. The behavior of other triggers remains
unchanged.
Instead of starting evaluation from the most prioritized mobility to LTE feature,
operator has an option to select a startable feature from the mobility process.
Depending on chosen startable feature, WCDMA to LTE mobility can be speed up.
2.1.6 Site Diagnostics Overview
Site Diagnostics is an O&M solution, combined of a number of features and

applications. The main purpose of the Site Diagnostics is to support users in
diagnostics activities that are performed on-site and off-site.

Value Package Name: WRAN Base Package
Node Type: Baseband Radio Node
Licensing: Basic feature. No license is required.
Access Type: NR, LTE, WCDMA, GSM
Summary
The Site Diagnostics aims to support various aspects of the deployment and
maintenance activities. Depending on the use case, tasks such as validation,
troubleshooting, or KPI and alarm handling, are made more effective and easier
to handle by the introduced software features and user interaction
improvements.
8 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.1.7 UE-Selective Relocation to LTE Overview
The feature enables the RNC to recognize the UEs having trouble
connecting to LTE RAN, for example because of lack of LTE subscription.
Access Type: WCDMA

Node Type: RNC
Licensing: Licensed feature. One license is required for each
node.
Summary
The feature limits mobility to LTE for UEs that reconnect to the WCDMA RAN
within a configurable time period, after attempting mobility to LTE.
Reconnections to the WCDMA RAN within a configurable interval might mean
that these UEs have no LTE subscription. Mobility to LTE for these UEs becomes
restricted for a configurable interval. The feature does not affect the LTE Mobility
process for any of those UEs, that return from the LTE RAN to the WCDMA RAN
by SRVCC voice and data, CSFB through idle mode, or CSFB based on PSHO from
LTE.
This feature ensures the following benefits:
— Provides better performance for UEs with a WCDMA subscription only.
— Keeps roaming users in WCDMA RAN, if the roaming agreement forbids

roaming users to access E-UTRAN.
— Temporarily blocks subsequent mobility attempts to LTE for UEs that appear
unable to attach to the LTE network.
— Increases the general success rate for mobility to LTE process for the network
with UEs without LTE subscription.
— Detects UEs without LTE subscription without CN support.
— Reduces unnecessary signaling.
— Reduces interruption of data transmissions, that improves PS retainability.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 9

2.1.8 Multiple IP Addresses on the Same VLAN
This feature introduces the configuration of up to four IPv4 addresses on

the same VLAN.
Access Type: LTE, NR, WCDMA, GSM

Value Package Name: WCDMA Base Package
Benefits
The feature allows the node to support up to four IPv4 addresses on the same
VLAN.
Capacity and Performance

No impact.
Operation
A maximum of four AddressIPv4 MOs can be created under the same
InterfaceIPv4 MO. The addresses must belong to different, non-overlapping
subnets. The AddressIPv4.configuartionMode attribute must be set to MANUAL
for each AddressIPv4 MO.
One IPv4 address must be set as the primary address for cases when the system
must use a single address. This is done by setting the
AddressIPv4.primaryAddress attribute to true.
Note:
The InterfaceIPv4.encapsulation attribute must refer to the EthernetPort,
VlanPort, LagPort, or Bridge MO. In other cases, maximum one AddressIPv4
MO can be configured under the corresponding InterfaceIPv4 MO.
Interfaces
No impact.
Hardware
No special hardware requirements.
10 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Other Network Elements

ENM version 21.1 or later is required for this feature.
RELATED INFORMATION
Multiple IP Addresses on the Same VLAN
2.1.9 Efficient Fault Management
The feature supports users in efficient fault management and problem

troubleshooting.
Access Type: LTE, NR, WCDMA

Licensing Basic feature. No license is required.
Benefits
The feature allows minimizing the time and effort needed to identify and
troubleshoot a problem.
Less competence and intervention effort can be involved thanks to accurate and
relevant fault indication.

Improved performance achieved thanks to effective fault management and
faster system recovery.
Operation
Efficient Fault Management provides mechanisms to enhance the monitoring
capabilities.
If the node is not able to recover a service, the user is provided with accurate
information assuring that the fault is reported once and pinpointing the root
cause.
The observability of system recoverable faults is improved through notifications

which give insights into self-healing activities.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 11

In addition, the feature allows configuring the network supervision according to

the operator's preferences.
Interfaces
No impact.
Hardware

No impact.
Related Information
Efficient Fault Management
2.1.10 In-Service Performance Excellence
The In-Service Performance Excellence feature supports achieving a

constantly available and fully capable network in terms of both capacity
and end-user service experience.
Access Type: LTE, NR, WCDMA

Licensing Basic feature. No license is required.
Benefits
The feature allows achieving high service availability with minimized human
involvement.

Improved robustness by reducing service downtime and minimizing performance
degradation.
Operation
The In-Service Performance Excellence feature improves robustness through
several functions.
12 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
The aim of the feature is to reduce service downtime with focus on the following
mechanisms:
— System restarts
The function enables optimized restart sequences and good control of the
restart domains, for example individual Radio Access Technology, to reach
service availability as fast as possible.
— Automatic recoveries
Whenever a fault occurs, the system is trying to recover the failed resource
unless it is evaluated as a non-recoverable problem that requires operator
intervention.
— Automatic mitigation of problems
System is trying to keep the service operational with as minimal degradation

as possible by using alternative resources or network capabilities. At the
same time the system is clearly indicating a fault to the operator so they can
plan and execute corrective actions.
Interfaces
No impact.
Hardware

No impact.
Related Information
In-Service Performance Excellence
2.1.11 4TX Support for One WCDMA Carrier
4TX is supported for WCDMA in both single mode and mixed mode radio
configuration. With this feature activated, one sector can only support one
WCDMA carrier.

Value Package Name: Mobile Broadband
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 13


Access Type: WCDMA
Licensing: No Licensed Required
Summary and Benefits

This feature provides the following benefits:
— The CAPEX and OPEX are reduced because of flexible network deployment.
— In W+L mixed mode radio configuration, the network performance of LTE or

WCDMA can be improved as more available power can be allocated.
For more information, see 4TX Support for One WCDMA Carrier.
2.2 Mandatory Impact at Upgrade

Overview information about the globally released and unrestricted changes to
the network performance and operation. The changes take effect automatically
at upgrade.
2.2.1 20.Q2: Activation of Improved Selection of EUL/HS Serving Cell
Feature Name: System Improvements in W19.Q2

Node Type: RNC
Access Type: WCDMA
Benefits
Improved handling of selecting best cell in Active Set is introduced with the
feature. Until now, best cell was chosen when the Soft Handover procedure had
been executed at the RL Removal. Result of that was that the Network and UE
had different view of the best cell. With the new behavior, what is considered as
the best cell is independent on the mobility direction. The selection of best cell is
based on event 1d-HS measurements report.
For more information, see Handover.

Features that are dependent on the best cell indication, for example Load
Sharing, ANR Mobility, and Release with Redirect to LTE, benefit from this
improvement.
The following KPIs are affected:
14 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— PintHS_R_D
— PintHS_R_MD
— PintEUL_R_MD
— SRBonlyHS_R_D
— SRBonlyEUL_R_D
— Drop_Source
For more information, see Radio Network KPI.
Operation
The system improvement is enabled by default.
Interfaces
No impact.

No impact.
2.2.2 20.Q2: Configurable External Alarm Filter for Each Port
The improvement provides the possibility to configure external alarm port

filters on AlarmPort MO instances

Benefits
This improvement provides the possibility to configure external alarm port filters
on AlarmPort MO instances. The filter can be configured in case of toggling
alarm notifications to reduce the number of reported events from sensors
connected to the ports.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 15

The main benefit of this improvement is that once the filters are configured, they
decrease the number of alarm notifications reported.

No impact
Operation
The external alarm port filters can be configured by setting the new attributes on
AlarmPort MO instances. These attributes are intended to decrease the number
of alarm notifications sent for AlarmPort MO instances. It is possible to filter out
short events completely, and also filter low frequency toggling alarms, where
time between the alarms is higher than 60 seconds.
Table 5 Introduced Attributes

MO Attribute Description
AlarmPort.filterAlgorithm This attribute can be configured with
the following values:
— None: The current system
behavior is applied when this
value is set.
— Fixed: It is possible to manually

configure the
AlarmPort.filterTime and
AlarmPort.filterDelay
attributes when this value is set.
— Auto: It is possible to manually

configure the
AlarmPort.filterTime attribute,
and to automatically configure the
AlarmPort.filterDelay
attribute when this value is set.
This option can be applied if the
toggling frequency for the
equipment connected to the
external alarm port input is not
known at the time of
configuration.
AlarmPort.filterTime Only the events that are longer than
the time defined (in seconds) by this
attribute are reported. The default
value of this attribute is 0 second.
AlarmPort.filterDelay This attribute is responsible for
decreasing the number of alarm
notifications toggling with low
16 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
MO Attribute Description
frequency. The default value of this
attribute is 60 seconds, which is
updated by the system when the
AlarmPort.filterAlgorithm is set
to Auto.
Interfaces
No impact.
Hardware

This enhancement requires ENM version 20.04 or later to be used.
2.2.3 20.Q2: LTE Measurements Enhancement: Accepted Signal Strength Margin

Relative to the Best LTE Cell
This enhancement introduces a mechanism of checking signal strength of

the chosen candidate LTE cell.
Feature Name: PS Handover to LTE based on Measurements in LTE

Node Type: RNC
Access Type: WCDMA
Benefits
In case the best reported LTE cell is not defined as a neighbor cell, a handover is
not to be performed if the difference in signal strength between chosen candidate
reported LTE cell and best reported LTE cell in the same frequency is not within a
margin.

In case many LTE neighbor relation configurations are missing, value of counters
related to PSHO based on LTE Measurements can change.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 17

Operation
No impact.
Interfaces
No impact.
Hardware

To fully benefit from the change, the node requires support from the following
network elements:
— UE:
— Release 8 and support PSHO to LTE
— LTE RAN:
— L17A
— Coverage-Triggered WCDMA IRAT Handover (FAJ 121 0897)
— Coverage-Triggered WCDMA Session Continuity (FAJ 121 0493)
2.2.4 20.Q2: Improvement of Additional Information for Power Disturbance

Alarm
This system improvement adds detail to the Power Disturbance alarm,

and helps speed up on-site work.

Benefits
The Additional Information field of the Power Disturbance alarm is redefined to
remove a step from unit identification on site, and speed up the alarm resolution
process. For more information, see Power Disturbance.
18 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
Operation
The new value pair UNITS is added to the Additional Information field of the
Power Disturbance alarm. Its value is an array of strings that list
<fieldReplaceableUnitId>,<serialNo> pairs. The
<fieldReplaceableUnitId> is the value component of the RDN,
<serialNumber> refers to the serial number of the field replaceable unit.
Example 1 Value Pair UNITS for Two Radio Units
Check outcome of alarm list for UNITS = [{“RU-1-1,D167826134“}, →

{“RU-1-2,D167826135“}]
Interfaces
No impact.
Hardware

No impact.
2.2.5 20.Q2: Recovery Initiation and Recovery Success Alerts
This improvement introduces two alerts to notify the operator that service is
unavailable (cell disabled) when automatic system recovery is initiated, and
the service is available (cell enabled) again when the automatic system
recovery is finished successfully.

Access Type: WCDMA
The automatic system recovery is initiated when any of the following faults
occur:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 19

— Baseband unit hardware fault
— CPRI link related fault
— Radio unit related fault
The following two alerts are introduced:

— Cell Service Unavailable Auto Recovery Initiated Alert: Indicates the
automatic system recovery is initiated and service is unavailable during the
system recovery.
— Cell Service Available Auto Recovery Successful Alert: Indicates the

automatic system recovery is finished successfully and service is available
again.

No impact.
Operation
The two alerts do not require manual intervention.
A new value DEPENCENCY_RECOVERY is introduced to the attributes listed in

Table 6.
Table 6 Attribute Changes

Attribute Description
SectorCarrier::availabilityStat The new value
us DEPENDENCY_RECOVERY indicates
the automatic system recovery is
NodeBLocalCell::availabilitySta
initiated and the cell is disabled.
tus
NodeBLocalCellGroup::availabili The new value
tyStatus DEPENDENCY_RECOVERY indicates
the automatic system recovery is
initiated and all cells within the cell
group are disabled.
Interfaces
No impact.
Hardware
20 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.6 20.Q2: Multiple SPC Support for RANAP Protocol
This system improvement enables the operator to use two different

originating Signaling Point Codes (SPC) with different Network Indicator
(NI) settings for RANAP.
Feature Name: System Improvements in 20.Q2

Node Type: RNC
Access Type: WCDMA
Benefits
Enabling two different SPCs with different NI for RANAP increases the
configuration flexibility of the RNC. As a result of the improvement, the operator
can also configure the CS or the PS domain using signaling separation, if such a
configuration is needed.

No impact.
Operation
The default configuration allows the use of the same Originating Point Code
(OPC) and the same NI, as shown in Figure 1. CS and PS domains reference the
same SccpApLocal MO, which has a parent-child relation to the SccpScrc MO
and to the SccpSp MO.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 21

Mtp3bSpItu=1
SPC 2551
NI=1
SccpSp=1 Mtp3bAp=1 Mtp3bSrs=1 M3uAssociation
Mtp3bSr
SccpScrc=1 Mtp3bAp=2 Mtp3bSrs=2 M3uAssociation
Mtp3bSr
SccpApRemote=2
SccpApRemote=1
1 2 Reference
SccpApLocal=1 IuLink=1 IuLink=2
C P Parent-child relation
<MO name> Single instance
Ranap=CS Ranap=PS <MO name> Multiple instances

RncLmRanap
Figure 1 Example of the PS/CS Domain Configuration Using One SPC. No

Signaling Separation.
With the improvement, the RANAP application can be attached to two different
local SCCP Access Points. Figure 2 presents a network configuration using two
different OPCs and referencing two different Network Indicator settings.
Different SccpApLocal MOs are used for the CS and the PS domain. CS and PS
domain signaling separation is achieved in this configuration.
22 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Mtp3bSpItu=1 Mtp3bSpItu=2
SccpSp=1 SPC 2551 SccpSp=2 SPC 2351
NI=1 NI=2
Mtp3bAp=1 Mtp3bSrs=1 Mt3uAssociation Mtp3bAp=2 Mtp3bSrs=2 Mt3uAssociation
Mtp3bSr Mtp3bSr
SccpScrc=1 SccpScrc=2
SccpApLocal=1 SccpApRemote=1 SccpApLocal=2 SccpApRemote=2
IuLink=1 IuLink=2
Ranap=CS Ranap=PS
RncLmRanap
C P Parent-child relation 1 2 Reference <MO name> Single instance <MO name> Multiple instances
Figure 2 Example of the PS/CS Domain Configuration Using Two Different

SPCs. Signaling Separation is Enabled.
The improvement introduces the following configuration possibilities:
— Same OPC and different NIs
— Different OPCs and the same NI
— Different OPCs and different NIs
To enable the new solution in the network, the following MO instances are
required:
— IuLink
— Ranap
— SCCP MOs:
• SccpApLocal
• SccpApRemote
• SccpScrc
• SccpSp
— Transport Network MOs:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 23

• Mtp3bAp
• Mtp3bSpItu
• Mtp3bSrs
• Mtp3bSr
• M3uAssociation
Interfaces
No impact.
Hardware
Applicable for Evo Controller 8200/RNC and EvoC 8300.

No impact.
2.2.7 20.Q2: t315 Default Value and Dependency Change
The default and recommended value of the Rrc::t315 is changed, as well

as it's feature dependency.
Feature Name: Call re-establishment for PS

ANR Inter Frequency
FAJ 121 4564
Value Package Name: Enhanced Voice retainability
ANR
FAJ 801 0327 R7
Node Type: RNC
Access Type: WCDMA
As a result of introduction of feature Call re-establishment for PS (FAJ 121 5151):
— The default and recommended value of the timer Rrc::t315 is changed from
0 s to 10 s. When Call Re-establishment for PS is deactivated, t315 is hard-
coded to 0, regardless of the MOM parameter value.
24 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— The dependency to ANR Inter-Frequency (FAJ 121 4564) and Call Re-
establishment (FAJ 121 1374) is replaced with dependency to Call re-
establishment for PS (FAJ 121 5151).

With the new default and recommended value when the feature Call re-
establishment for PS is active, PS retainability can be improved.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.2.8 20.Q2: HSDPA Capacity Increase for Baseband
The maximum number of HSDPA users on each HS core is increased from

128 to 160.

Access Type: WCDMA
Benefits
When multiple cells are allocated to the same HS core, this system improvement
brings the following benefits for high-loaded cells:
— The HS accessibility is improved because more HSDPA users are supported.
— The blocked HS RAB establishment attempt can be reduced due to the

increased HSDPA core capacity
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 25

Note: The number of blocked HS RAB establishment attempt can be

observed through the two PM counters,
UtranCell::pmNoRabEstBlockNodePsIntHsBest and
UtranCell::pmNoRabEstBlockNodePsStrHsBest.
For more information about cell allocation to a HS core, refer to Manage Radio
Network.

The maximum number of HSDPA users on node level increases up to 25%.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.2.9 20.Q2: Encrypted Target Monitor Streaming
Encrypted target monitor streaming ensures confidentiality and integrity

protection of the personal data in transit by cryptographic means. This
functionality prevents possible privacy breaches or manipulation with the
data.
Feature Name: Security Management

Node Type: RNC
Access Type: WCDMA
No visible change is expected after system upgrade. Default setting for target
monitor is secure mode, where streaming is disabled.
26 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
New encrypted mode is introduced for target monitor functionality. In encrypted

mode, the streaming between host and node is encrypted ensuring
confidentiality and integrity protection of the personal data. Streams are
encrypted with ciphers negotiated by TLS.
For more information about the target monitor, see Security for O&M Node
Access.

No impact.
Operation
The updated command secmode -m allows the operator to change the target
monitor mode (secure, unsecure, and encrypted).
The new attribute Security::targetMonitorPort indicates the current target

monitor setting.
Target monitor is configured using tm command. In encrypted mode client IP

address must be configured by authorized user.
For more information on how to change the target monitor setting, see Security
for O&M Node Access.
Prerequisite to enable encrypted target monitor mode is to have node credentials

installed.
Interfaces
No impact.
Hardware

ENM/AMOS is not supporting encrypted target monitor streaming.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 27

2.2.10 20.Q2: LTE Measurements Enhancement: Combining Coverage Check and

LTE Measurement as Triggers for PSHO to LTE
This enhancement allows to perform PSHO to LTE based on Coverage

Check also when feature PS Handover to LTE based on Measurements in
LTE is activated.
Feature Name: PS Handover to LTE Based on Measurements in LTE

Node Type: RNC
Access Type: WCDMA
Benefits
This enhancement allows to perform PSHO to LTE based on Coverage Check also
when feature PS Handover to LTE based on Measurements in LTE is activated. If
both features are enabled and event 2f-RwR is received before event 3c, then 2f-
RwR is no longer ignored but used as a trigger for PSHO to LTE based on
Coverage Check.
The enhancement removes also the dependency of PS Handover to LTE Based on

Measurements in LTE feature on PSHO to LTE based on Coverage Check. For the
enhancement to be active both features must be enabled.

Introduction of the enhancement decreases Compressed Mode usage in networks
with coverage of co-sited LTE cells resulting in less frequent LTE measurement
starts and therefore less frequent Compressed Mode starts.
Detailed information on new counters, KPI formulas to observe and expected

behavior of existing counters can be found in PS Handover to LTE Based on
Measurements in LTE.
Operation
Feature introduces mechanism to keep legacy behavior after removing license
dependency of feature PS Handover to LTE based on Measurements in LTE (FAJ
121 3519) on license for Packet Switched Handover to LTE (FAJ 121 4721). It
works by altering UtranCell::psHoToLteEnabled and
UtranCell::lteMeasEnabled parameters during RNC upgrade. For details,
please see PS Handover to LTE based on Measurements in LTE.
28 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Interfaces
No impact.
Hardware

No impact.
2.2.11 20.Q2: Enhanced CPRI Diagnostics and Observability, Improved AMOS

Commands Timing
This system improvement enhances SFP-related CPRI diagnostics by

providing faster execution time of inv and sdi AMOS commands. The
improvement also enhances CPRI observability by increasing history log
storage.
Feature Name: System Improvements in W20

Benefits
The improvement offers the following benefits:
— Enhanced SFP-related CPRI diagnostics
— Enhanced CPRI observability

The improvement shortens the execution time of inv and sdi AMOS commands
by executing CLI commands only on the Baseband unit, instead of executing
them also on the Radio or Baseband R503.
The improvement also enhances history log storage by increasing the internal
memory.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 29

Operation
This improvement enables the following PM counters by default:
— RiLink.pmLinkDelayHigh
— RiLink.pmLinkDelayLow
— RiLink.pmLinkRestart
— RiLink.pmLinkStabilityError
— RiPort.pmBitError
— RiPort.pmLossOfFrame
— RiPort.pmLossOfSignal
— SfpModule.pmSfpTemperature
— SfpModule.pmSfpVoltage
— SfpChannel.pmChannelRxPower
— SfpChannel.pmChannelTxPower
— SfpChannel.pmChannelTxBias
Interfaces
No impact.
Hardware

Upgrade to ENM version 20.1 is required.
2.2.12 20.Q2: Improved Visibility of SSH Public Keys
SSH public keys are visible and presented by a new system-created MO

ServerKey.

30 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Benefits
This enhancement improves the security for SSH-based server-client connection.

No impact.
Operation
SSH public keys are generated during software initial rollout and after every
successful upgrade, and the keys can be renewed by the new action
ServerKey::renewKey.
Note: The established SSH sessions are terminated during the key renewing.
The customer can read the information of SSH public keys by the following new
attributes:
— ServerKey::fingerprint
— ServerKey::keyType
— ServerKey::publicKey
— ServerKey::publicKeyFormat
— ServerKey::serverKeyId
— ServerKey::userLabel
For more information about security management, refer to Manage Security.
Interfaces
No impact.
Hardware

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 31

2.2.13 20.Q2: IPsec DPD Message Optimization
This enhancement improves the IPsec DPD mechanism by sending DPD

messages from the baseband unit to the SEG if incoming ESP traffic stops in
the IPsec VPN connection.
Feature Name: IPsec

Value Package Name: IPsec
Access Type: WCDMA
The enhancement limits the amount of DPD traffic between the baseband unit
and the SEG. The existence of incoming ESP traffic in the IPsec VPN connection
proves that the IPsec VPN connection is working.
Benefits
The enhancement offers the following benefits:
— Less processing load on the SEG
— Enabling the SEG to support more IPsec VPN connections

The enhancement reduces processing load on the SEG by limiting the amount of
DPD traffic in the IPsec VPN connection.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
32 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.14 20.Q2: EvoC8300: Brute Force Protection, Disabling Telnet and FTP Server
Access
The enhancement introduces brute force protection for the Evo 8300 node.

Node Type: RNC
Access Type: WCDMA
The enhancement prevents the possibility to gain access to the node through a
user account using brute force attack. The protection mechanism also introduces
both user logon delay and user account lockout.
Support for Telnet and FTP servers on the node is removed.
Dormant User accounts in basic mode of user authentication and authorization

are disabled on the 365th day. The Inactive Node User Account is sent to
ENM to indicate dormant accounts at regular intervals.
All CLI based idle sessions are terminated after idle session timeout.
Operation and maintenance traffic with IP options and ICMP redirect enabled
traffic are not processed by the node. For more information, see Security for O&M
Node Access.

No impact.
Operation
If the passwords are not changed every 90 days for the existing node user
accounts, the following message is displayed after the enhancement is enabled:
The password could be compromised. Please, change the password.
Note: When going back to a software version older than 20.Q2, node users are
reset on the node. The users must be created by logging in with the
initadmin user.
Operators are recommended to use SSH and SFTP when connecting to the node.
It is recommended for the operators to update their passwords every 90 days
after the enabling the enhancement. The userconfig command is enhanced to
unlock a locked user and enabled a disabled dormant user.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 33

The Security.unlockUser action is introduced for the Evo 8300 node to unlock
a locked LAA user.
Interfaces
No impact.
Hardware
The enhancement supports EvoC 8300 only.

No impact.
2.2.15 20.Q2: Displaying Node Autointegration Status in ENM
The ENM Integration Engineer can supervise and troubleshoot the early
stages of RBS autointegration process using the ENM Auto Provisioning
service.
Feature Name: Zero Touch Zero Touch N/A

Integration Integration
Feature Identity: FAJ 121 0999 FAJ 121 0999 R2 N/A
Value Package LTE Base Package WCDMA Base GSM RAN Base
Name: Package
Package
Value Package FAJ 801 0400 FAJ 801 0359 R18 FAJ 801 0386
Identity:
Node Type: Baseband Radio Baseband Radio Baseband Radio
Node Node Node
Access Type: LTE WCDMA GSM
Benefits
— Better supervision of the early stages of autointegration.
— Faster troubleshooting in case of errors during the process.
The improvement is applicable for greenfield integrations of nodes using Zero

Touch or LMT Integration.

No impact.
34 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
During early stages of Auto Integration node provides integration status to ENM
Auto Provisioning.
In case of a fault during the integration, the node provides the fault description.
The description enables the ENM Integration Engineer to troubleshoot.
Interfaces
Autointegration status is provided using standardized interface between the
node and ENM AIWS service.
Hardware

ENM version 20.2 or later is required.
2.2.16 20.Q2: Removal of License Check for Multi-Sector Per Radio
With this system improvement, the Multi-Sector Per Radio feature requires
no license in Baseband Radio Node.
Feature Name: System Improvements in 20.Q2

Access Type: WCDMA
Benefits
The Multi-Sector Per Radio feature in Baseband Radio Node can be used directly.
For more information about Multi-Sector Per Radio, refer to Multi-Sector Per
Radio.

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 35

Operation
Operators do not need to order license.
Interfaces
No impact.
Hardware

No impact.
2.2.17 20.Q2: Baseband Power Savings
This improvement allows the baseband unit to save power by using only
half of the baseband processing resources. It is applicable for single-
standard nodes only.

Access Type: WCDMA
Benefits
The power consumption of a baseband unit is reduced up to 22% without impact
to capacity or performance.
The system improvement replaces the function of Energy Efficient Baseband

Configuration.

No Impact.
Operation
The system improvement is by default enabled after the upgrade. It can be
disabled by setting PowerSaving::bbPowerSavingsEnabled to FALSE.
36 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Note: If the SW is upgraded from 20.Q1, users need to manually enable this
system improvement by setting
PowerSaving::bbPowerSavingsEnabled to TRUE.
If the power saving is enabled and all the requirements in Table 7 are fulfilled,
the node runs in power saving mode, which is indicated by
PowerSaving::bbPowerSavingStatus with the value ACTIVATED.
Table 7 Baseband Power Saving Configurations

Baseband Unit Number of Number of Number of
Unlocked Cells(1) Configured Licensed HWAC
RX/TX Branches CE DL/UL
Baseband 5216 1-12 1-24 1-576
Baseband 6630
Baseband 6318
IDU 5209 1-6 1-12 N/A
(1) A cell with maximum 2TX and 4RX is internally treated as two cells with maximum 2TX and
2RX. The unlocked cell with maximum 2TX and 4RX reserves the baseband resources of two
cells with maximum 2TX and 2RX.
Any change in the attribute value of PowerSaving::bbPowerSavingsEnabled

needs a node restart to enable or disable power saving mode. If the power saving
mode is enabled, changes in the configuration that go against or meet the
requirements in Table 7 can deactivate or activate power saving mode with a
node restart. For more information, refer to Manage Hardware Equipment
The amount of saved power can be calculated by comparing either of the counter
values, when power saving mode is activated or deactivated:
— EnergyMeter::pmConsumedEnergy
— EnergyMeter::pmPowerConsumption
— EnergyMeasurement::pmEnergyConsumption
— EnergyMeasurement::pmPowerConsumption
The MO, attributes, and alarm introduced with this system improvement are
shown in the following table.
Items Name Description

MO PowerSaving -
Attribute PowerSaving::powerSa -
vingId
PowerSaving::bbPower -
SavingsEnabled
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 37

Items Name Description

PowerSaving::bbPower PowerSaving::bbPower
SavingStatus SavingStatus
replaces
NodeBLocalCellGroup:
:bbPowerSavingMode
.
Alarm Power Saving Capacity When the node runs in
Limit Exceeded power saving mode, if
the capacity supported
by power saving mode is
exceeded as more cells
are added and unlocked,
Power Saving Capacity
Limit Exceeded is raised.
To cease the alarm, refer
to Power Saving
Capacity Limit
Exceeded.
Interfaces
No impact.
Hardware
This improvement applies to the following hardware:
— Baseband 5216, Baseband 6630, Baseband 6318
— IDU 5209

No impact.
2.2.18 20.Q3: Detect Wrongly Connected CPRI Cable Case in Baseband Radio
Node
This system improvement introduces a detection method to find wrongly

connected CPRI cables between the radio, the Baseband Radio Node and
the XMU.
Feature Name: System Improvements in WCDMA RAN

38 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Access Type: GSM, WCDMA, LTE, NR
When the faulty case occurs, an alarm MO Configuration Not Consistent

with Installed Equipment is generated on the RiLink MO.
The detection method covers the following misconnection error cases:

— In a multiple radio configuration, not all cables from the radios are connected
to the same FRU physically.
— In a single radio configuration, each cable is configured for one FRU in MOM,
but more cables are connected physically to the same hardware.
The improvement updates the MO Configuration Not Consistent with

Installed Equipment alarm.
The alarm also improves legacy behavior by covering the use case where a radio
cable is connected to a wrong data port.
Benefits
Customer is notified by the alarm MO Configuration Not Consistent with
Installed Equipment to find wrongly connected cable problem quickly.

No impact.
Operation
Inconsistent Configuration alarm on RiPort is updated to ensure that
wrongly connected cable problems are not raised on RiPort, but on RiLink MO
with the alarm MO Configuration Not Consistent with Installed
Equipment. When the alarm is raised, the RiLink MO is kept enabled for traffic.
Interfaces
No impact.
Hardware

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 39

2.2.19 20.Q3: Password Change Enforcement Message
This system improvement introduces a warning message for the user about
the need for a password change.

Node Type: RNC
Access Type: WCDMA
The benefit of this system improvement is informing the user about the need for a
password change.
If a node password is not changed in the last 90 days, after login to the node the
following warning appears:
WARNING: The password could be compromised. Please change the password.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
This system improvement is applicable for EvoC 8200.

No impact.
40 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.20 20.Q3: Enforce Replacement of Passwords - EvoC 8200
Node behavior is changed to prevent unauthorized access and

configuration management in case node password is not set.

Value Package Identity: FAJ 801 0359 R19B
Node Type: RNC
Access Type: WCDMA
This feature enhancement is activated by default after system upgrade and there
is no option to deactivate it.

No impact.
Operation
When User Authentication and Authorization is in basic mode and node
password is not configured, the user is not able to:
— Execute COLI commands
— Establish FTP and SFTP connections
Node password is configured over SSH, Telnet or Serial connection by using

command passwd. For more information about the target monitor, see Security
for O&M Node Access.
Interfaces
No impact.
Hardware
This feature enhancement is applicable for EvoC 8200 RNC node.

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 41

2.2.21 20.Q3: Enforce Replacement of Passwords - EvoC 8300

Value Package Identity: FAJ 801 0359 R19B
Node Type: RNC
Access Type: WCDMA
This feature enhancement enforces changing the password of the user created by
an O&M administrator at first logon of the user to the node. The default O&M
Admin passwords for users are removed from CPI. Operators are advised to
create operator own usernames and passwords.
The enforce replacement of passwords feature enhancement is activated by

default after System Upgrade. There is no option to deactivate it.

No impact.
Operation
The O&M user newly created by the O&M adminstrator when the User
Authentication and Authorization is in basic mode has to take the following
steps:
1. Logon to the node over SSH or serial port with the adminstrator provided
password.
2. Change the password on first logon.
3. Logon to the node with the new password.
SFTP is disallowed until the users change password over SSH or Serial port.
For more information, see Security for O&M Node Access.
Interfaces
No impact.
Hardware
This feature enhancement is applicable for EvoC 8300 RNC node.

No impact.
42 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.22 20.Q3: Improved Static Route State Retrieval
The improvement introduces a logic to retrieve the static route state

information.
Feature Name: System Improvements in WCDMA RAN W20

Node Type: RNC
Access Type: WCDMA
The improvement introduces a logic behind the retrieval of the active attribute
from the hardware to expose it on CPP MO level. It is along with raising an event
if a route becomes active.

The improvement introduces the STATIC_ROUTE_ACTIVITY_CHANGE_IND event.
This event is raised in case a static route becomes active to improve the
troubleshooting of traffic handling issues.
Operation
The layout of the Ipv4StaticRoute MO is changed to indicate if the route is
selected for traffic routing towards the destination set in the parent
Ipv4DestNetwork MO or not.
Interfaces
No impact.
Hardware
Applicable only for EvoC 8200 and EvoC 8300.

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 43

2.2.23 20.Q3: Robust Call Retention during O&M Disturbances
This improvement enables Circuit Switch (CS) and Packet Switch (PS)
retainability during O&M planned or unplanned disturbances such as
transmission issues, power outages, RBS restarts, cell lock.

Node Type: RNC
Access Type: WCDMA
In case planned or unplanned disturbance occurs, if there is any working radio

link left in the active set, the RNC, instead of releasing the call, removes faulty
radio link and updates the active set accordingly. In case of HS connections, RNC
can change the HS serving cell if there is appropriate candidate in the AS, located
in the other RBS.
If all radio links in the active set are considered to be down, RNC postpones
releasing of the connection and waits for call reestablishment request from the
UE. The following Call Re-establishment features are assumed to be enabled,
otherwise, the connection is dropped:
— Call Re-establishment (FAJ 121 1374)
— Call Re-establishment for PS (FAJ 121 5151)
— Call Re-establishment over Iur (FAJ 121 3273)

The improvement affects the UtranCell.pmNoTimesRlDelFrActSet PM counter.
The improvement affects the following KPIs:
Table 8 Key Performance Indicators

KPI Description
Speech_R Retainability formula measuring CS
speech drop rate.
PacketintHs_R Retainability formula measuring HS
interactive drop rate.
The improvement affects other retainability formulas as well.
The improvement affects the following event:
44 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Table 9 Events
Event Event Parameter Description
INTERNAL_SYSTEM_RE CAUSE_VALUE Cell Lock Indication
LEASE
EVENT_PARAM_UTINT 113 (O&M Intervention)
ERNAL_SYSTEM_RELEA
SERAN RANAP_CAUSE
EVENT_PARAM_RAN Four combinations
DISCONNECTION_COD (cause name: O&M,
E trigger: Cell lock
indication)
EVENT_PARAM_RAN One combination (cause
DISCONNECTION_SUBC name: O&M, trigger: Cell
ODE lock indication)
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.2.24 20.Q3: Automatic Narrowband Interference Rejection Handling
With the introduction of automatic Narrowband Interference Rejection

(NBIR) handling, the optimal NBIR algorithm is selected automatically.
Feature Name: Narrowband Interference Rejection

Value Package Name: Narrowband Interference Rejection
Access Type: WCDMA
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 45

Benefits
This enhancement brings the following benefits:
— The operation for NBIR algorithm selection is simplified.
— The optimal NBIR algorithm is selected automatically. It can lead to the

following improvements:
— Increases cell coverage and uplink cell throughput
— Decreases call drop rate
For more information, refer to Narrowband Interference Rejection.

With automatic NBIR handling, NBIR is enhanced to further decrease the
received total power, which is observed by the counter
NodeBSectorCarrier::pmAverageRssiHigh.
The lower received total power increases cell coverage, uplink cell throughput
and decreases call drop rate. These performance improvements can be observed
by the following KPIs respectively:
— Increased uplink cell throughput:
— PINTEUL_I_ULTP_L1
— PintEUL_I_ULTP_Glim_L1
— Decreased call drop rate:

— Speech_R
— PacketintHs_R
Operation
The automatic NBIR handling can be enabled when the attribute
NodeBSectorCarrier::nbirAlgorithm is set to any of the following values:
— AUTO_GENERIC_ADAPTIVE_NBIR
— AUTO_GENERIC_ADAPTIVE_OFF_NBIR
If the attribute NodeBSectorCarrier::nbirAlgorithm is set to GENERIC_NBIR

before upgrade, the value of the attribute is automatically converted to
AUTO_GENERIC_ADAPTIVE_NBIR when the node is upgraded to the SW
release supporting automatic NBIR handling for the first time.
To activate the Narrowband Interference Rejection feature, refer to Narrowband

Interference Rejection.
46 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
The automatic NBIR handling is disabled by setting the attribute

NodeBSectorCarrier::nbirAlgorithm to any of the following values:
— GENERIC_NBIR
— ADAPTIVE_NOTCH_NBIR
— FIXED_NOTCH_NBIR
The attribute changes for the enhancement are listed in Table 10.

NodeBSectorCarrier::nbirAlgorit The following values are introduced to
hm enable the automatic NBIR handling:
— AUTO_GENERIC_ADAPTIVE_NBI
R: In the case of no interference,
the generic NBIR algorithm is
performed.
— AUTO_GENERIC_ADAPTIVE_OFF
_NBIR: In the case of no
interference, no NBIR algorithm is
performed.
NodeBSectorCarrier::nbirAutoCur New read-only attribute, which
rentAlgorithm indicates the current NBIR algorithm
being performed when the automatic
NBIR handling is enabled. The value
NOT_APPLICABLE indicates the
automatic NBIR handling is disabled.
Interfaces
No impact.
Hardware

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 47

2.2.25 20.Q3: Support for Showing Alarm History in EMGUI
Alarms history is introduced in EMGUI to make troubleshooting process

easier.

Access Type: WCDMA
Benefits
— Observability of alarm history provides help with troubleshooting
— Site technician can see if alarm is toggling
— No need to know EMCLI commands to see alarm history
— The following filtering options are available:
• Alarms from given dates range
• Only active alarms
• Only historical alarms
For more information, see Manage EMGUI.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
48 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.26 20.Q3: Improved behavior of port LEDs on SMXB

Node Type: RNC
Access Type: WCDMA
This system improvement aligns the LED behavior on SMX board with the
Ericsson design rules.
Table 11 shows the connection between the LED statuses and the link states:
Table 11 Connection between LED Statuses and Link States

LED Status Definition Meaning
OFF The port is DISABLED. The port is disabled and
there is no link.
Steady ON The port is ENABLED. The port is enabled
without traffic on the
link.
Flash Traffic on the link. The port is enabled with
traffic on the link.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
Applicable for EvoC 8300.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 49


No impact.
2.2.27 20.Q3: RNC Process for Rehoming with EvoC 8300 and ENM
The RNC Process for Rehoming with EvoC 8300 and ENM feature provides
an emergency procedure for fast traffic recovery to a spare RNC.
Feature Name: The RNC Process for Rehoming with EvoC 8300 and
ENM
Feature Identity: N/A
Value Package Name: N/A
Value Package Identity: N/A
Access Type: WCDMA
Node Type: RNC
The RNC Process for Rehoming with EvoC 8300 and ENM feature enables radio
configuration recovery from a live RNC to the spare RNC. The use of this
procedure is limited to emergency situations that caused RNC failure, for example
natural disasters. The procedure lets the operator to restore the traffic on the
spare RNC by using the automated script available in AMOS.
For more information, refer to Rehome Radio Configuration with EvoC 8300 and
ENM.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
Applicable to EvoC 8300.
At least one spare EvoC 8300 is required.
50 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

AMOS version 20.0k or later is required.
2.2.28 20.Q3: SHA-2 Support for License Key Files
SHA-2 hash algorithms are supported for LKFs.
Feature Name: License Control of Functionality

Node Type: RNC, DU Radio Node, M-MGw
Access Type: WCDMA
Benefits
This feature enhancement extends the security aspects of the existing license
control. The LKFs are secured with SHA-2 certificates using modern
cryptographic functions based on SHA-2 algorithms.

No impact.
Operation
The SHA-2 LKFs with certificates and cryptographic functions are automatically
generated in the ELIS.
The SHA-2 LKFs are supported from the W18.Q3 release.
Up to the W20.Q2 release, LKFs are generated in the ELIS with SHA-1
certificates and cryptographic functions.
From the W20.Q3 release, LKFs are generated in the ELIS with SHA-2 certificates
and cryptographic functions.
Interfaces
No impact.
Hardware
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 51


No impact.
2.2.29 20.Q3: Increased Retransmission Period at Longer IPsec DPD Time
With this enhancement, the number of retransmissions for IPsec Dead Peer
Detection (DPD) can be set with the attribute dpdTime.
Feature Name: IPsec

Value Package Name: IPSec
Access Type: WCDMA
Benefits
This enhancement improves the compatibility between Ericsson Baseband Radio
Nodes and SEG nodes from other vendors. It can be achieved by changing the
number of retransmissions. The number of retransmissions depends on the value
of Ikev2PolicyProfile::dpdTime.
For detailed information, refer to IPsec and Manage IPsec.

No impact.
Operation
The number of retransmissions can be changed by setting
Ikev2PolicyProfile::dpdTime.
For details about how the configuration defines the number of retransmissions,
the retransmission period and the interval, refer to Manage IPsec.
Interfaces
No impact.
Hardware
52 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.30 20.Q3: Call Re-Establishment Enhancement in Access Phase
Call Re-establishment Enhancement in Access Phase reduces the number of

connection drops during call setup phase. Improvement is visible in cells or
areas where radio condition issues occur.
Feature Name: Call Re-Establishment (prerequisite)

Call Re-Establishment for PS (related)
Feature Identity: FAJ 121 1374 R3 (prerequisite)
FAJ 121 5151 R2 (related)
Value Package Name: Enhanced voice retainability
Node Type: WCDMA
Access Type: RNC
This enhancement enables a call re-establishment (CRE) functionality at:

— RAB establishment
— From standalone SRB
— On top of existing RABs
— DL NAS Signaling
CRE at RAB Establishment:
With this enhancement, Cell Update with cause RL Failure or RLC Unrecoverable
Error received from UE during RAB Establishment procedure is handled by RNC.
RNC attempts to restore the connection by performing a call re-establishment in
case the UE experiences radio connection issues during establishment of CS RAB.
If Call Re-establishment for PS (FAJ 121 5151) is active, it is possible to re-
establish PS RABs also.
CRE at NAS Signaling:
With poor radio conditions, NAS message sent to UE may not reach the UE which
can lead to connection release initiated by the core network. With this
enhancement, NAS message is “cached” in RNC and call re-establishment is
attempted. After a successful CRE, the NAS message is re-transmitted to the UE
and removed from cache. This solution is applicable for CU with cause RL Failure.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 53


This enhancement improves accessibility at connection setup phase. It also
reduces connection drops during RAB establishment on top of another RAB,
which means that existing connection is saved.
The observability is ensured with the following:

— Basic retainability and accessibility KPIs
— Counters related to PS/CS call re-establishment
— Counters related to SRB system releases
— As well as the following, newly introduced counters:

— For the number of executions of CRE that is requested/attempted/
successful for standalone SRB established towards CS/PS domain:
• pmCallReestFromSrbReqPs
• pmCallReestFromSrbReqCs
• pmCallReestFromSrbAttPs
• pmCallReestFromSrbAttCs
• pmCallReestFromSrbSuccPs
• pmCallReestFromSrbSuccCs
— For the number of executions of CRE that is requested/attempted/

successful during ongoing RAB Establishment procedure:
• pmCallReestAtRabEstReqPs
• pmCallReestAtRabEstReqCs
• pmCallReestAtRabEstAttPs
• pmCallReestAtRabEstAttCs
• pmCallReestAtRabEstSuccPs
• pmCallReestAtRabEstSuccCs
— For the number of retransmissions of CS/PS DL NAS Message after

successful CRE:
• pmNoRetransNasReestSuccPs
• pmNoRetransNasReestSuccCs
54 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
This enhancement introduces two operator parameters:
— Rrc::callReestRabEstEnabled controls activation of support for CRE
during addition of RABs.
— Rrc::callReestDlNasSignEnabled controls activation of support for DL

NAS message retransmission after CRE.
If Call Re-Establishment (FAJ 121 1374) or Call Re-establishment for PS (FAJ

121 5151) is enabled, this enhancement is enabled by default.
If Call Re-establishment for PS (FAJ 121 5151) is active, it is possible to re-

establish PS RABs also.
Interfaces
No impact.
Hardware

The enhancement requires at least R6 compliant UEs. For UEs release less than
6, the connection is released.
It is possible to extend RAB Assignment supervision timer in CN to increase the

probability of saving the new RAB when CRE happens at RAB handling
procedure.
2.2.31 20.Q3: Read-only MOM Attributes - Consistent Behavior without

Notification
A noNotification flag was added to a number of read-only MOM attributes.

As a result, these attributes changed from persisted to non-persisted
(delegate) in ENM database. The attributes are related to Network
Synchronization functionality.

Release
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 55

Access Type: WCDMA
Benefits
The attributes behave as other non-persisted attributes. They are updated in
ENM CLI, and in CM Export if using User-Defined Filter File. They are not
included in normal CM Export.
Previous behavior without noNotification flag was inconsistent: Attributes were

not updated in ENM CLI. They were included but not updated in normal CM
export.
The fact that the attributes are now not included in normal CM Export is a non-
backward compatible change. The choice of noNotification was made mainly
with respect to the risk of high notification load.

No impact.
Operation
Functionality for non-persisted (delegate) attributes is limited compared to
persisted attributes:
— ENM accesses the attributes from the Baseband Radio Node. This requires
that node is synchronized to ENM.
— The attributes can be read but not queried by ENM CLI.
— The attributes are not included in normal CM export but can be included
using a User-Defined Filter File. CM export with User-Defined Filter File with
non-persisted attributes requires that Baseband Radio Node and ENM are
synchronized. CM export can be configured with disabled export of non-
synchronized nodes.
— The attributes are not monitored in CM Events.
— Affected attributes are listed in the table below. These attributes are in the
Transport Model.
Table 12 Affected Attributes

MO Class Attribute
FrequencySyncIO availabilityStatus
operationalState
GnssInfo gnssRecControlPath
gnssReceiverControl
56 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
MO Class Attribute
gnssReceiverProductData
multipleGnssActual
multipleGnssStatus
NtpFrequencySync availabilityStatus
cachedIpAddress
ingressUdpPort
ntpFrequencySyncStatus
operationalState
BoundaryOrdinaryClock clockStatus
PtpBcOcPort availabilityStatus
cachedIpAddress
operationalState
ptpPortStatus
AssistingReference assistedReferenceStatus
availabilityStatus
operationalState
receivedQualityLevel
RadioEquipmentClock timeSyncAssistanceState
RadioEquipmentClockReference availabilityStatus
operationalState
receivedQualityLevel
referenceStatus
syncRefType
SyncEthInput availabilityStatus
operationalState
receivedSsmCode
syncEthPhysical
syncEthStatus
SyncPort availabilityStatus
operationalState
TimeSyncIO timeSyncIOStatus
Interfaces
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 57

Hardware

The MOM change is supported from ENM version 20.3. It means the attributes
are non-persisted (delegate) in the ENM database. With earlier versions of ENM
the behavior does not change for these attributes - they are persisted but not
updated live after the initial node synchronization.
2.2.32 20.Q3: Automatic Narrowband Interference Rejection Handling on DU

Radio Node

Node Type: DU Radio Node
Access Type: WCDMA
Benefits
This enhancement brings the following benefits:
— The operation for NBIR algorithm selection is simplified.
— The optimal NBIR algorithm is selected automatically. It can lead to the

following improvements:
— Increases cell coverage and uplink cell throughput
— Decreases call drop rate

With automatic NBIR handling, NBIR is enhanced to further decrease the
received total power, which is observed by the counter
Carrier::pmAverageRssiHigh.
The lower received total power increases cell coverage, uplink cell throughput
and decreases call drop rate. These performance improvements can be observed
by the following KPIs respectively:
— Increased uplink cell throughput:
— PINTEUL_I_ULTP_L1
58 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— PintEUL_I_ULTP_Glim_L1
— Decreased call drop rate:

— Speech_R
— PacketintHs_R
Operation
The automatic NBIR handling is enabled when the attribute
Carrier::nbirAlgorithm is set to any of the following values:
— AUTO_GENERIC_ADAPTIVE_NBIR
— AUTO_GENERIC_ADAPTIVE_OFF_NBIR
If the attribute Carrier::nbirAlgorithm is set to GENERIC_NBIR before

upgrade, the value of the attribute is automatically converted to
AUTO_GENERIC_ADAPTIVE_NBIR when the node is upgraded to the SW
release supporting automatic NBIR handling for the first time.
To activate the Narrowband Interference Rejection feature, refer to Narrowband

Interference Rejection.
The automatic NBIR handling is disabled by setting the attribute

Carrier::nbirAlgorithm to any of the following values:
— GENERIC_NBIR
— ADAPTIVE_NOTCH_NBIR
— FIXED_NOTCH_NBIR
The attribute changes for the enhancement are listed in Table 13.

Carrier::nbirAlgorithm The following values are introduced to
enable the automatic NBIR handling:
— AUTO_GENERIC_ADAPTIVE_NBI
R: In the case of no interference,
the generic NBIR algorithm is
performed.
— AUTO_GENERIC_ADAPTIVE_OFF
_NBIR: In the case of no
interference, no NBIR algorithm is
performed.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 59

Carrier::nbirAutoCurrentAlgorit New read-only attribute, which
hm indicates the current NBIR algorithm
being performed when the automatic
NBIR handling is enabled. The value
NOT_APPLICABLE indicates the
automatic NBIR handling is disabled.
Interfaces
No impact.
Hardware

No impact.
2.2.33 20.Q3: Support for AISG RET antenna
The feature enhancement supports using AISG3.0-compatible antenna

near units.
Feature Name: Support for AISG RET antenna

Benefits
The AISG3.0 standard enables the operator to inspect the antenna near unit logs
and diagnose faults without on-site actions.
Legacy operations of AISG2.0 are supported, and the enhancement allows the
operator to dynamically switch between different AISG versions. AISG2.0 and
AISG3.0 devices are compatible with each other and can be used together.

No impact.
60 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
The enhancement introduces the following attributes for inspecting and
configuring antenna near units:
— AntennaNearUnit.aldState
— AntennaNearUnit.connectionState
— AntennaNearUnit.downloadState
— AntennaNearUnit.configuredAisgVersion
— AntennaNearUnit.supportedAisgVersion
The AntennaNearUnit.configuredAISGVersion attribute can be used to switch

between the supported AISG versions that are shown by the
AntennaNearUnit.supportedAISGVersion attribute.
The following actions are introduced:

— AntennaNearUnit.clearActiveAlarms
— AntennaNearUnit.generateTestAlarm
— RetSubUnit.resetAllPorts
— RetSubUnit.resetAld
— RetSubUnit.clearConfig
— TmaSubUnit.resetAld
— TmaSubUnit.resetAllPorts
Interfaces
No impact.
Hardware
The enhancement requires AISG3.0-compatible antenna near units.
The enhancement is supported on RET and TMA.
Antennas must support ADB-type 3PP antenna near units.

ENM version 20.2 or later is required for this feature enhancement.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 61

2.2.34 20.Q4: Improved Supervision of Synchronization References
This system improvement introduces supervision for phase jump events on

time-capable network synchronization references.

This improvement is applicable to existing features that enable time-capable

synchronization. It introduces supervision for phase jump events on time-capable
network synchronization references. Such events are recorded through the new
phaseJump PM counter.
Benefits
Observability for baseband unit is improved by giving additional information
about the time-capable synchronization reference behavior. Troubleshooting of
synchronization issues, like interference or traffic disturbances, is improved. It is
achieved by making it easier to pinpoint which baseband unit can be the root
cause of the problem.

No impact.
Operation
The new phaseJump PM counter is introduced under the PtpBcOcPort and the
TimeSyncIO MO classes. This PM counter is used for time-capable
synchronization reference, and it is stepped when the phase jump of the
corresponding size occurs.
Interfaces
No impact.
Hardware
62 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.35 20.Q4: Support for AISG RAE version 2.2.0
This feature enhancement adds support for AISG RAE version 2.2.0, and
introduces the ASD and GLS subunits.
Feature Name: Support for AISG RAE

Access Type: WCDMA
Functions for geographic location information and antenna observability are

extended to the ASD and GLS subunits.
The ASD and GLS subunits provide geographic location information of the ALD
and allow for benchmarking the following parameters:
— Altitude
— Latitude
— Longitude
— Downtilt
— Azimuth
— Roll
Benefits
The feature enhancement has the following benefits:
— Enhanced engineering parameters monitoring
— Introduces RAE version 2.2.0 and ASD and GLS devices support.

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 63

Operation
The ASD and GLS subunits must be configured manually before on-site
deployment. The configuration file must be uploaded to the ALD.
The enhancement introduces the following MO classes:

— AsdSubUnit
— GlsSubUnit
The enhancement modifies the following MO classes:

— AntennaNearUnit
— AntennaUnit
— RaeSubUnit
The enhancement introduces the following alarms:

— ASD Fault
— GLS Fault
— ASD Autoset Failed
— ASD Not Calibrated
Interfaces
No impact.
Hardware
The enhancement is not applicable to AAS-capable radio units.

network elements:
— ECT
— EMGUI
ENM version 20.14 or later is required for the enhancement.
64 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.36 20.Q4: TMA Uplink Gain Handling Improvement
With the system improvement, the uplink gain from TMA in the configured
sector is updated dynamically.

Access Type: WCDMA
Benefits
The system improvement brings the following benefits:
— Shorten node startup time up to 14 seconds
— Improve the measurement of RSSI and power spectrum

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 65


Notification

(delegate) in ENM database. The attributes are related to Cabinet Power
Distribution and External Alarms.


Previous behavior without noNotification flag was inconsistent: attributes were

export.

No impact.
Operation
synchronized nodes.
66 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— Affected attributes are listed in the table below.
• MO Classes BatteryBackup and PowerDistribution are in the

EquipmentSupportFunction model.
• MO Class Alarm Port are in the Equipment model.

MO Class Attribute
BatteryBackup estimatedRemainingBackupTime
PowerDistribution systemVoltage
AlarmPort activeExternalAlarm
Interfaces
No impact.
Hardware

The MOM change is supported from ENM version 20.4. It means the attributes
are non-persisted (delegate) in the ENM database. With earlier versions of ENM
the behavior does not change for these attributes - they are persisted but not
updated live after the initial node synchronization.
2.2.38 20.Q4: 4096-Bit RSA Key Support for Node O&M Certificates
This feature enhancement enables the enrollment of certificates with 4096-

bit size RSA key.

Node Type: RNC
Access Type: WCDMA
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 67

Benefits
Node certificates with 4096-bit size RSA key strengthens the security of TLS
communications.

No impact.
Operation
The EnrollmentData struct for the Security.initCertEnrollment MO action
is updated with the following new default values:
— The enrollmentMode member default value is changed from SCEP to
CMPV2_INITIAL.
— The keyLength member default value is changed from KEY_1024 to

KEY_2048. The option KEY_1024 is deprecated.
The keyLength member of the EnrollmentData struct can be set to KEY_4096 to

enroll node certificates using the Security.initCertEnrollment MO action.
For more information on the enrollment process, see Security for O&M Node
Access.
Interfaces
No impact.
Hardware

This feature enhancement requires 4096-bit RSA key enrollment support from
ENM.
2.2.39 20.Q4: User-defined Filtering of Alarm Notifications
Fault Management supports suppressing specific alarm notifications.

68 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

This feature introduces Fault Management support in the node to suppress or

send alarm and alert notifications over FM NBI to ENM, depending on the
configuration of related alarm types set by the operator.
The MOM is modified by adding new isNotified attribute to FmAlarmType, and

FmAlarm MOs. FmAlarmType:isNotified attribute enables the operator to
suppress or send the alarm and alert notification for this FmAlarmtype on the
node. FmAlarm:isNotified attribute indicates if an alarm or alert notification
corresponding to the FmAlarm MO instance was sent or suppressed. Suppressed
alarm and alert notifications are instantiated as FmAlarm MO instances in the
node MIB in the same way as the sent notifications and are stored on the node in
the legacy Alarm log, or Alert log, and presented in the nodes in Active Alarm List.
For more information, see Fault Management.
Note: Alarm notifications with perceived or configured severity set to “Critical”

cannot be suppressed.
Benefits
— Operators are able to focus on alarms which are more relevant to them and
their specific network deployment.
— Less time is required for the operator to spend on alarm notification handling
and fault management, as they are not notified about alarms not relevant to
them.
— Less personnel is needed in operator's NOC to monitor and process alarm

notifications.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 69


No impact.
2.2.40 20.Q4: Improved Observation of Narrowband Interference Rejection

Algorithm
The observability of narrowband interference rejection algorithm has

improved.

Baseband Radio Node
Access Type: WCDMA
Benefits
This enhancement introduces the following counters to observe the NBIR
algorithm and track algorithm history:
— pmNbirRunningAlgorithm: the NBIR algorithm in use
— pmNbirSuggestAlgorithm: the recommended NBIR algorithm based on the

measured narrowband interference
With this enhancement, the operator can achieve the following benefits:
— Improved observability of NBIR algorithm
— Better view of narrowband interference status
— Clear NBIR algorithm suggestion for cells with narrowband interference

No impact.
Operation
No impact.
70 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Interfaces
No impact.
Hardware

No impact.
2.2.41 20.Q4: Node Health Validator
The Node Health Validator is introduced to simplify the use of the available
node health checks.
Feature Name: Site Diagnostics

Benefits
— The field technician can run health check to validate the on-site activity
before handing over to NOC.
— The field technician can run health check to get the initial status, as starting
point when troubleshooting is needed.

No impact.
Operation
The Node Health Validator is accessible as a web tool on the Baseband node. It is
mainly targeted towards site technicians for performing site diagnostics and
health checks without requiring knowledge about MOM and software
configuration.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 71

Interfaces
No impact.
Hardware

No impact.
2.2.42 20.Q4: On-site Indication of Alarms in EMGUI
This enhancement introduces on-site indication for alarms in EMGUI,

intended to support site technicians.

Benefits
— The field technician can run health check to validate the on-site activity
before handing over to NOC.
— The field technician can run health check to get the initial status, as starting
point when troubleshooting is needed.

No impact.
Operation
The Node Health Validator is accessible as a web tool on the Baseband node. It is
mainly targeted towards site technicians for performing site diagnostics and
health checks without requiring knowledge about MOM and software
configuration.
72 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Interfaces
No impact.
Hardware

No impact.
2.2.43 20.Q4: Change value range for required intervals of BfdProfile MO
This improvement offers greater configuration flexibility by lowering the

range limit of two attributes under the BfdProfile MO class.

Node Type: RNC
Access Type: WCDMA
This improvement lowers the limit range from 200ms to 100ms for the
desiredMinTxInterval and requiredMinRxInterval attributes under the
BfdProfile MO class.
These attributes configure the BFD Detection Time, which is used for link
supervision between SMXB routers and external routers in both receiving and
transmitting directions.
The new interval ranges introduce greater configuration flexibility and allows
quicker link failure detection.

No impact.
Operation
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 73

Interfaces
No impact.
Hardware
This improvement is only applicable for EvoC 8300.

No impact.
2.2.44 20.Q4: Increase System Limits of External Cells and Iub Links
The system improvement increases the system limits for the number of
external UTRAN cells, external GSM cells, and Iub links in EvoC 8300 and
Evo Controller 8200/RNC.

Node Type: RNC
Access Type: WCDMA
Benefits
This system improvement provides the following benefits:
— Ability to merge older RNC 3820 nodes saturated with ExternalUtranCell

and ExternalGsmCell into smaller number of Evo RNC nodes.
— Ability to handle the configurations with three UTRAN cells for each
IubLink.
— Wider geographical area coverage with one node.
— Allows the EvoC RNC Geo-Redundancy (FAJ 121 5182) feature to handle
larger RNC configurations.

No impact.
74 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
The system improvement increases the cardinality for the following MOs:
Table 15 MOs Affected by the Improvement

Name Old Value New Value
ExternalUtranCell 5301 10602
ExternalGsmCell 7680 15360
IubLink 1767 2346
RSite 1767 2346
Interfaces
No impact.
Hardware
Applicable for Evo Controller 8200/RNC and EvoC 8300.

ENM version 21.1 or later is required for this improvement.
2.2.45 21.Q1: Detection of Transmitted Power
The system improvement introduces detection of transmitted power,

automatic recovery, and an alarm for failed recovery.
Feature Name: In-Service Performance Excellence

Access Type: WCDMA
Benefits
Transmitted power for each downlink carrier branch is continuously checked. If
any downlink carrier branch of a cell has no transmitted power, cell re-setup is
automatically performed to recover the cell. If the recovery fails, Downlink TX
No Power Detected alarm is raised for the affected cell.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 75


No impact.
Operation
To cease the alarm, follow the instructions in Downlink TX No Power Detected.
Interfaces
No impact.
Hardware
The system improvement is applicable to the radios that support VSWR
measurements.

No impact.
2.2.46 21.Q1: Detect a Replacement during Power Off
The hardware replacement that happens during node power off can be
recorded.

Benefits
When hardware units are replaced during node power off, the information of the
new hardware unit is recorded in the Hardware Inventory History Log after node
power on.
With the log, operators can easily track the history of hardware replacement.

No impact.
76 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
No impact.
Interfaces
No impact.
Hardware
The following hardware replacements can be recorded in the log:
— Field Replaceable Units except baseband units
— Hardware units with a product number or serial number, but do not belong to
the FRU category
Note: The replacement information of battery unit is not recorded in the

log.

No impact.
2.2.47 21.Q1: Anonymized Event Data Activated by Default
The Anonymized Event Data feature is now activated by default after

network upgrade. Additional actions are recommended for users that have
not activated the feature before.
Feature Name: Anonymized Event Data

Node Type: RNC
Access Type: WCDMA
When Anonymized Event Data is active, it is recommended to set the same

encryption key for all nodes. This allows data from different RNCs to be
correlated. If no key is defined by the user, a random key is generated, which may
affect network supervision realized with GPEH, CTR, UETR, and UERTT
functions.
If encryption is not to be used in the network, the feature must be deactivated.

For instructions, see Anonymized Event Data.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 77


When the feature is active, MC Load is increased by up to 1,5% for Evo Controller
8200/RNC.
Operation
The encryption key is set using the setCryptoPassword MO action. For more
information on the encryption key and feature operation, see Anonymized Event
Data.
Interfaces
No impact.
Hardware

No impact.
2.2.48 21.Q1: Increased EvoC 8300 Security through Restricted Access to OS
The enhancement introduces restricted access to OS sensitive commands

and file paths for Local Authentication and Authorization (LAA) users on
EvoC 8300 node.

Node Type: RNC
Access Type: WCDMA
Benefits
This enhancement improves the LAA function on the node by protecting
operating system files from being accessed by LAA users. LAA users on the node
are only authorized to perform CLI operations and file transfers specified in their
authorized task profiles.
The enhancement has no impact for node users in basic mode.
78 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
Operation
Unauthorized file system, operating system, and CLI access are restricted for LAA
users.
Interfaces
No impact.
Hardware

MoShell version 20.0p or later is mandatory to be able to connect through AMOS
shell to RNC node with enhanced LAA mode for LAA users. This includes FM
Advanced and Ericsson Support task profile users.
ENM 21.1 is equipped with valid MoShell version. For older ENM releases,
manual MoShell update is required.
2.2.49 21.Q1: Non-Backwards Compatible Change in LKF Handling for RNC

Nodes
This feature enhancement extends the security aspects of the existing

license control.

Release
Node Type: RNC
Access Type: WCDMA
Benefits
Enhanced LKF protection mechanism is introduced to provide new LKF file
secured with certificates using modern cryptographic functions.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 79


No impact.
Operation
New LKF file has to be ordered and installed before upgrading to W21.Q1
software or later. Existing LKFs on the node ordered before W20.Q3 release are
no longer valid.
If the upgrade to W21.Q1 is performed with incompatible LKF, License Key

File Fault and License Mismatch alarms are raised. The License Mismatch
alarm activates a safety buffer period of 7 days (previously 36 hours). During this
time, all licensing features enabled on the node continue to work. Once safety
buffer is expired, all the existing licensing features are disabled, leading to traffic
service disruption.
Interfaces
No impact.
Hardware
EvoC 8200 and EvoC 8300 are impacted.

No impact.
2.2.50 21.Q1: Enhanced LKF Protection Mechanism
This feature enhancement extends the security aspects of the existing

license control.

W21 Release
80 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Benefits
An enhanced LKF protection mechanism is introduced to provide a new LKF file
secured with certificates using modern cryptographic functions.

No impact.
Operation
A new LKF file has to be ordered and installed before upgrading to 21.Q1
software or later. Existing LKFs on the node, ordered before 20.Q3 release, are no
longer valid.
If the upgrade to 21.Q1 is performed with an incompatible LKF, the License Key
File Fault and Autonomous Mode Activated alarms are raised. The
Autonomous Mode Activated alarm activates a grace period of 7 days
(previously 36 hours). During this time, all licensing features enabled on the node
continue to work. Once the grace period expires, all the existing licensing features
are disabled, leading to traffic service disruption.
Interfaces
No impact.
Hardware

No impact.
2.2.51 21.Q1: Improved Hardware Fault Management for Radio Units
Automatic recovery is introduced when the connection with the antenna

near units is lost.

Release
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 81

Access Type: WCDMA
Benefits
When the connection with antenna near units is lost, automatic recovery is
triggered before generating an alarm. If the recovery fails, the alarm No
Connection is raised on the AntennaNearUnit MO.
The system improvement can reduce the number of alarms if the fault can be
automatic recovered.

No impact.
Operation
The automatic recovery is enabled by default. It can be disabled by setting the
new attribute RfPort::automaticAnuRecovery to FALSE.
To cease the alarm raised by failed recovery, refer to No Connection.
Interfaces
No impact.
Hardware
The improvement is not supported on IRU.

No impact.
2.2.52 21.Q1: TLS 1.3 Support for Baseband Radio Node
The improvement introduces TLS 1.3 support for all management and
control plane traffic on the Baseband Radio Node where TLS 1.2 is
supported.
Feature Name: System Improvements in WCDMA

RAN W21 Release
82 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Access Type: NR, LTE, WCDMA
The improvement enables TLS 1.3 on all interfaces where TLS 1.2 is supported on
the Baseband Radio Node.
The selection of ciphers is simplified as TLS 1.3 cipher suite definitions do not
include key exchange and signature algorithms.

Using TLS 1.3 ensures greater network security and improved performance
compared to previous TLS versions.
Operation
TLS 1.3 can be configured with the Tls MO.
Interfaces
No impact.
Hardware

The use of the enhancement depends on whether the other connected network
element supports TLS 1.3.
2.2.53 21.Q1: Node Group Synchronization: Alarm Handling in Unsupported

Configurations

W21 Release
Access Type: WCDMA
This is a system improvement introducing the Sync Inconsistent

Configuration alarm to Baseband Radio Nodes used in Mixed Mode Radio and
Multi-Operator RAN (MORAN) configurations with CPRI shared equipment.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 83

The alarm is raised when Managed Elements in Mixed Mode Radio and MORAN
configurations with CPRI shared equipment use an unsupported synchronization
solution. In this case, Node Group Synchronization is the recommended solution,
assuring tight synchronization between Managed Elements.
Benefits
This system improvement has the following benefits:
— Improves observability of the Baseband Radio Node by indicating that an

unsupported synchronization solution is configured.
— Draws the attention of the operator to configure and use the supported NGS
solution and avoid potential traffic degradation.

No impact.
Operation
This system improvement introduces the Sync Inconsistent Configuration
alarm. The alarm is raised on the RadioEquipmentClock MO.
The alarm is raised when the

FieldReplaceableUnit.isSharedWithExternalMe attribute is set to true and
the NodeGroupSyncMember MO is not created or locked.
Interfaces
No impact.
Hardware
— ENM release 20.1 or later is required for this improvement.
2.2.54 21.Q1: Node Performance Monitor
Node Performance Monitor is a tool from EMGUI family, introduced to

provide easy access to basic hardware-related performance indicators.

84 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Benefits
— User has possibility to see selected hardware performance indicator values

on the web page opened from the node.
— User can see measurements in better granularity than standard 15 minutes

ROP period.
— User can go to EMGUI Equipment View to see where given unit is connected.
For more details, see Manage EMGUI.

No impact.
Operation
Node Performance Monitor tool can be used in on-site and remote
troubleshooting to see HW performance measurements.
Interfaces
No impact.
Hardware

No impact.
2.2.55 21.Q1: LTE Measurements Enhancement: LteMeasCmDchProlongTimer

Default Value Change
Default value of timer prolonging DCH state to complete LTE measurements

is changed.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 85

Release with Redirect to LTE Based on

Measurements in LTE
FAJ 121 4277 R2
Node Type: RNC
Access Type: WCDMA
The recommended and default value of the

UeMeasControl.lteMeasCmDchProlongTimer attribute is changed from 0 to 25.
This corresponds to 2.5 seconds.
In consequence, this enhancement is automatically activated when one or more

of the following features are activated on the RNC:
— PS Handover to LTE Based on Measurements in LTE (FAJ 121 3519)
— Release with Redirect to LTE Based on Measurements in LTE (FAJ 121 4277)
For more information, see LTE Measurements.

If the enhancement is active by default, some KPIs and counters related to
mobility to LTE can be affected.
Impact on observability is highly dependent on the network and the

configuration and might not always be as described.
The following counters and counter ratios can be affected:

— LTE_measurement_success_rate = 100 *
(UtranCell.pmLteMeasReportEval / UtranCell.pmLteMeasCmStart) -
expected to increase
— LTE_measurement_stop_rate = 100 * (UtranCell.pmLteMeasStop /

UtranCell.pmLteMeasCmStart) - expected to decrease
— LTE_measurement_timeout_rate = 100 * (UtranCell.pmLteMeasTimeout /

UtranCell.pmLteMeasCmStart) - could be increased
— UtranCell.pmOutPsHoEutraReq - expected to increase
— UtranCell.pmOutPsHoLteMeasReq - expected to increase
Because of the increased number of PS Handover attempts

(UtranCell.pmOutPsHoEutraAtt), the following KPIs can be slightly improved:
— Pint_M_IRATHO_LTE
86 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— Pint_M_IRATHO_LTE_Tot
For the full list of affected counters, see 20.Q4: LTE Measurements Enhancement:
Prolong DCH State to Complete Measurements.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.2.56 21.Q1: User Profile Based Mobility Enhancement
This enhancement adds Packet Switched Handover to LTE features as new

mobility type supported by UE mobility profiles and therefore extends the
flexibility of controlling mobility to LTE. Furthermore, support for additional
Shared Network and standalone (non-shared) configuration is also
provided by the enhancement.
Feature Name: User Profile Based Mobility

Node Type: RNC
Access Type: WCDMA
This enhancement enables the User Profile Based Mobility feature to be

activated together with the following features:
— Shared Network Support (FAJ 121 246)
— One PLMN-ID per Frequency (FAJ 121 1301)
It is not mandatory to use the Shared RAN (MOCN) multiple PLMN support (FAJ
121 2530) feature with this function of the User Profile Based Mobility feature.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 87

The feature enhancement can now support handover type of mobility to LTE, so
the filtering algorithm of target LTE frequencies is affected for the following
features:
— Packet Switched Handover to LTE (FAJ 121 4721)
— PS Handover to LTE based on Measurements in LTE (FAJ 121 3519)
Benefits
— Functionality to control relocation toward LTE using an assigned profile
— Support for shared network configurations for both the One PLMN-ID per
Frequency and the Shared Network Support features
— Support for standalone, that is non-shared RNC configuration

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.2.57 21.Q1: Automatic Truncation of Iur Neighbor List

Release
Node Type: RNC
Access Type: WCDMA
88 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
This system improvement checks the RNSAP RADIO LINK SETUP RESPONSE and
RNSAP RADIO LINK ADDITION RESPONSE message size and removes cell
relations until the message size is below the limit imposed by the SCCP. If the
limit cannot be reached, an RNSAP RADIO LINK SETUP FAILURE or RNSAP RADIO
LINK ADDITION FAILURE message is sent instead.
Figure 3 Automatic Truncation of Iur Neighbor List Operational Process
Start of the Flow
Encode ASN.1 message
No
Send encoded
Truncate message Is message size too big?
RNSAP message
Yes
Yes
Can the message
be truncated?
No
- Discard message
- Peg respective PM counter
- Produce short RNSAP RL
Setup/Addition Failure message
End of the Flow
C0002579A
Neighbor cells are truncated in the following order:
1. GSM cell truncation

2. E-UTRA cell truncation
3. IEF cell truncation
— GSM Cell Truncation
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 89

If several external GSM networks are configured in the RNC, the minimum
number of GSM relations is equally divided among those GSM networks to
which relations exist from the source UTRAN cell. The minimum number of
GSM relations is defined in the IurCellRelTrunCfg.minGsmCellRelations
MO attribute.
GSM relations are put in descending order. The order corresponds to the
GsmRelation.selectionPriority MO attribute.
Truncation of the GSM neighboring cells is performed until the number of

cells in every GSM network group equals to the minimum level for the group.
Truncation of the GSM relations is performed in a round-robin manner,

meaning that in the next iteration, relation belonging to the next GSM
network is selected for truncation.
If the number of relations in all GSM network groups reaches the minimum
level, relations of another access type are truncated next.
— E-UTRA Cell Truncation
In case of LTE cells that belong to multiple LTE frequencies of one E-UTRA
Network operator, neighboring list in RNSAP message is limited to the cells
which belong to up to two LTE frequencies, with the lowest EARFCN.
Considering the RNSAP-related limitation, if the total number of LTE

frequencies (ensured for the LTE cells that are adjacent to the source UTRAN
cell) is greater than one, then the minimum number of LTE neighboring cells
is equally divided among those frequencies. This way of operation ensures
fairness when truncating the cells on different LTE frequencies. The operator
defines the minimum number of LTE neighboring cells in the
IurCellRelTrunCfg.minEutraCellRelations MO attribute.
Truncation of LTE neighboring cells is performed in a round-robin manner,

meaning that in the next iteration, LTE neighboring cell belonging to the next
LTE frequency is selected for truncation.
Truncation of LTE neighboring cells is performed until the number of cells for
each LTE frequency equals to the minimum level for the LTE frequency. If the
number of LTE relations in all LTE frequency groups reaches the minimum
level, relations of another access type are truncated in the next iteration.
— IEF Cell Truncation
If more than two WCDMA frequencies are accessible for the UEs handled by
a given PLMN operator, then the number of WCDMA frequencies to which
UEs of certain operator can be handed over from the source cell are limited to
two (with the lowest UARCFN).
If several WCDMA frequencies are accessible from the source cell

(considering the WCDMA frequency limitation), the minimum IEF relation
level is equally divided among those remaining WCDMA frequencies. The
90 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
operator defines the minimum IEF relation level in the

IurCellRelTrunCfg.minIefCellRelations MO attribute.
IEF cells (for a given WCDMA frequency) are put in descending order based
on the UtranRelation.selectionPriority MO attribute (truncation of
least important first). If IEF ANCL is enabled, hit divided by usage rate for all
IEF relations is used instead (truncation of least used first).
Truncation of IEF relations is performed in a round-robin manner, meaning

that in the next iteration, relation belonging to the next WCDMA frequency is
selected for truncation.
Truncation of IEF relations is performed until the number of relations in every

WCDMA frequency group is equal.
IAF neighbor cells are not truncated.
When truncation of other relation type cells does not help to sufficiently reduce
the size of the RNSAP response message, the RNSAP RADIO LINK SETUP
FAILURE or RNSAP RADIO LINK ADDITION FAILURE message is sent.

The following counter is affected by this enhancement:
pmNoIurCellRelTruncFailure - Stepped when the size of the RNSAP RADIO

LINK SETUP RESPONSE or RNSAP RADIO LINK ADDITION RESPONSE
message exceeds the maximum size of SCCP message in CPP layer and cannot
be sent.
With the Automatic Truncation of Iur Neighbor List system improvement, the
counter is pegged for the same reason but only if the truncation of neighbor list
has reached the configured minimums and the RNSAP message size is still above
SCCP message limit.
Operation
The minimum numbers of relations are defined for each UTRAN cell in structure
UtranCell.iurCellRelTrunCfg:
— IurCellRelTrunCfg.minGsmCellRelations - minimum number of GSM cell

relations that must remain in RNSAP message after truncation (the default
value is 8)
— IurCellRelTrunCfg.minIefCellRelations - minimum number of IEF

UMTS cell relations that must remain in RNSAP message after truncation
(the default value is 20)
— IurCellRelTrunCfg.minEutraCellRelations - minimum number of E-

UTRA cell relations that must remain in RNSAP message after truncation
(the default value is 16)
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 91

Interfaces
No impact.
Hardware

No impact.
2.2.58 21.Q1: Anonymized Trace & Error and COLI Commands in RNC
The Anonymized Event Data feature is enhanced, to protect sensitive end

user information in troubleshooting data.

Node Type: RNC
Access Type: WCDMA
Benefits
With the enhancement, the feature encrypts the sensitive identifiers in the logs,
when using Trace & Error and COLI commands.

No impact.
Operation
For Information on feature operation, see Anonymized Event Data.
Interfaces
No impact.
Hardware
92 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.59 21.Q2: Configurable Password Aging for RNC Nodes
Node password aging can be configured.

Node Type: RNC
Access Type: WCDMA
Benefits
With this system improvement, the operator can configure the password aging
according to the organization security policies.
A warning message is issued when the password age is beyond the configured
password aging threshold limit. For more information on password aging, see
Security for O&M Node Access.

No impact.
Operation
The password age is set with the attribute Security.passwordAgingThreshold.
The default password aging limit is 90 days. Changing passwords is required
when the password age is beyond the password aging limit.
On upgrade, the existing password age is continued and the warning is issued
according to the configured password aging threshold limit.
Note: — The warning message can be disabled by extending the password

aging threshold.
— The password aging function is not applicable to Local User AA

Database (LAAD) users.
Interfaces
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 93

Hardware
This system improvement is applicable for EvoC 8200/RNC and EvoC 8300.

No impact.
2.2.60 21.Q2: Other Changed Behaviors in RNC: DCH Resource Optimization in

Case of Channel Switching to URA Procedure Failure
This improvement changes logic for handling asynchronous signals during

ongoing Channel Switch procedure.
Feature Name: System Improvements in WCDMA RAN W21 Release

Node Type: RNC
Access Type: WCDMA
When UE loses DCH connection and tries to connect again while old resources
are still allocated, UE ID collision indication is raised. With this change, such
indication signal aborts ongoing Channel Switch procedure to speed up overall
release of DCH resources.
Additionally, if RANAP Iu Release Command with normal release is received

during Channel Switch to URA, the channel switch procedure is also terminated.
Benefits
With the previously mentioned conditions, this improvement has the following
benefits:
— Faster release of old, unused DCH resources can be achieved.
— Increased reliability of Packet Switched release counters and Pint_R_D KPI.

The values of UtranCell::pmNoSystemRabReleasePacket counter can increase.
The values of UtranCell::pmNoNormalRabReleasePacket counter can
decrease. As a result, the value of Pint_R_D KPI can increase.
The values of UtranCell::pmChSwitchAttemptHsUra and

UtranCell::pmChSwitchAttemptDchUra counters can decrease. As a result, the
Success Rate for Channel Switch from DCH or HS to URA can increase.
94 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.2.61 21.Q2: Remove Support for RNC in Pool
W21.Q1 is the last software release that supports RNC in Pool.
Feature Name: RNC in Pool

Value Package Name: RNC in Pool
Node Type: WCDMA
Access Type: RNC
From W21.Q2 RNC in Pool is no longer supported. Iub redundancy can be

ensured with FAJ 121 5182 R3: EvoC RNC Geo-Redundancy. For more
information, see EvoC RNC Geo-Configuration.

No impact.
Operation
It is not possible to upgrade to W21.Q2 or higher software, if any instances of the
following MOs are present on the RNC:
— RemoteUtranCell
— RncClusterMember
— ClusterMember
— NodeClusterCommunication
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 95

For a successful upgrade, remove RNC in Pool configuration as described in RNC

in Pool in WCDMA RAN 21.Q1 CPI library or earlier.
Interfaces
No impact.
Hardware

No impact.

Notification

(delegate) in ENM database. The attributes are related to Transport
Network functionality.

W21 Release
Benefits
Previous behavior without noNotification flag was inconsistent: Attributes were

export.
96 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
Operation
synchronized nodes.
— Affected attributes are listed in the table below. These attributes are in the
Transport Model.

MO Class Attribute
InterfaceIPv4 availabilityStatus
operationalState
InterfaceIPv6 availabilityStatus
operationalState
Interfaces
No impact.
Hardware

The MOM change is supported from ENM version 21.05. It means that the
attributes are non-persisted (delegate) in the ENM database. With earlier
versions of ENM, the behavior does not change for these attributes - they are
persisted but not updated live after the initial node synchronization.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 97

2.2.63 21.Q2: Visibility and Assurance of Real-Time Security Event Logging
This feature enhancement improves the quality and visibility of the syslog
message format for security events and audit trail events in the Baseband
Radio Node.
Feature Name: Real-Time Security Event Logging

Value Package Name: Secure OAM and security logging
Benefits
The feature enhancement provides more information by unifying event format.
The following information is updated:
— Event descriptions
— Event areas
— Facility
— Functional area
— MSGIDs
— Severity levels
The enhancement provides easier troubleshooting and better observability.
For more information, see Security Logging.

No impact.
Operation
Outgoing syslog messages are affected by the detailed and unified AuditTrailLog
and SecurityLog contents. There is a minor increase in Real-Time Security Event
Logging event frequency because of the added events.
98 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Hardware
No impact.
Interfaces
No impact.

No impact.
2.2.64 21.Q2: 4096-Bit RSA Keys Support for RBS Node O&M Certificates

Access Type: WCDMA
This system improvement gives the possibility to enroll node O&M certificates
with 4096-bit RSA key lengths on RBS DU radio node.
Benefits
Node certificates with 4096-bit size RSA key strengthen the security of TLS
communications.

No impact.
Operation
The keyLength member of the EnrollmentData struct has to be set to KEY_4096
to enroll node certificates using the Security::initCertEnrollment() MO
action and to enroll IPsec certificates using the ipsec::initCertEnrollment()
MO action.
For more information on the enrollment process, see Security for O&M Node
Access.
Interfaces
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 99

Hardware

This feature enhancement requires 4096-bit RSA key enrollment support from
ENM.
2.2.65 21.Q2: Detect Hardware Reconfiguration
The HwInvHistoryLog is enhanced to distinguish hardware reconfiguration

from hardware replacement.

Benefits
The Hardware Inventory History Log records hardware replacements and
reconfigurations.

No impact.
Operation
The HwInvHistoryLog operator log contains an additional text that indicates if a
hardware unit is replaced or reconfigured. Reconfiguration is detected only for
Hardware units with a serial number.
Interfaces
No impact.
Hardware
100 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.66 21.Q2: AISG 3.0 Feature Support - Device Scan Functionality
The enhancement extends the support for AISG Device Scan procedure
from AISG 2.0 standard version to AISG 3.0.
Feature Name: Support for AISG RET Antenna

Benefits
The enhancement extends the support for AISG device scan procedure to AISG
3.0. This allows scanning new hardware based on this version. AISG 2.0 device
scan functionality is not affected.
After the upgrade, the scan results show devices that support AISG 3.0 in
addition to devices supporting earlier versions.
For more information on AISG 3.0, see Manage Hardware Equipment.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 101

2.2.67 21.Q2: Enhancement in Multiple IP Addresses on the Same VLAN
This enhancement introduces the configuration of up to four IPv4 addresses

on the same VLAN with identical subnets.
Feature Name: Multiple IP Addresses on the Same VLAN

Benefits
The enhancement allows the node to support up to four, manually configured
IPv4 addresses on the same VLAN, belonging to identical subnets.

No impact.
Operation
A maximum of four AddressIPv4 MOs can be created under the same
InterfaceIPv4 MO. The addresses can belong to different, non-overlapping
subnets or identical subnets. The AddressIPv4.configurationMode attribute
must be set to MANUAL for each AddressIPv4 MO.
One IPv4 address must be set as the primary address for cases when the system
must use a single address. This is done by setting the
AddressIPv4.primaryAddress attribute to true.
Interfaces
No impact.
Hardware

ENM version 21.1 or later is required for this feature.
102 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.68 21.Q2: Support for Schematron Rules Validation in EMGUI

Access Type: WCDMA
Benefits
Dependency rules specified in the MOM are now validated during edit, create,
and delete operations in EMGUI. An operation that does not conform to those
rules is rejected. With this validation, it is possible to edit, create, or delete a
number of MOs which were previously treated as ReadOnly by EMGUI.
For more information, see Manage EMGUI.

No impact.
Operation
User can now use EMGUI for a wider range of MOs in the MIB which were
previously treated as ReadOnly by EMGUI.
Interfaces
No impact.
Hardware

No impact.
2.2.69 21.Q2: System Restart Alert
The enhancement introduces a node restart notification for Baseband Radio

Node.
Feature Name: In-Service Performance Excellence
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 103


Access Type: WCDMA
Benefits
The observability of the radio node restart is improved. The user is notified about
the restart with a System Restart alert, with the following additional
information provided:
— Restart time
— Restart category
— Restart type
The restart notification is visible through ENM Alarm Monitor application or ENM
FM NBI.

No impact.
Operation
The function is activated by default.
The alert does not require any user intervention. More information on the restart
is collected in the availability log. If an unexpected restart or high rate restarts on
node or network level is seen, Ericsson Support must be contacted (a Customer
Service Request including data collection, see Data Collection Guideline).
Interfaces
No impact.
Hardware

No impact.
104 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.70 21.Q2: Improved Method for Creating Configuration Files Manually
Integration CPI is updated to include instructions for how to create

configuration files manually.
Feature Name: Zero Touch Integration

Benefits
A customized integration project can be created from scratch, or by manually
modifying a profile generated by ECT. This allows the profile to be extended
beyond ECT capabilities.

No impact.
Operation
The process for manual creation and adaptation of ECT profile is described in
Integrate Baseband Radio Node.
Interfaces
No impact.
Hardware

2.2.71 21.Q2: Manage the Security Gateway Address Manually Using Ericsson Site
Assistant Application

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 105


This functionality introduces support for a user to manually submit the security
gateway address in the Ericsson Site Assistant application. This is done to
establish a connection between the Baseband unit and the security gateway,
instead of using the EGIS server.

No impact.
Operation
Possible to perform Zero Touch integration of a Baseband unit connected over
internet without the need for EGIS.
Interfaces
No impact.
Hardware

No impact.
2.2.72 21.Q2: Improved MC Load Distribution in EvoC 8300
The improvement provides to the Module Controller (MC) load distribution

algorithm the use of the real load measurements of each MC instead of
average load taken from processing units assigned to MCs working on the
same processor.

Node Type: RNC
Access Type: WCDMA
106 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Benefits
With this improvement, MC load distribution can be optimized on EvoC 8300.

As a result of better utilization of resources within the same processor, the thread
load of RncLmUe processes is better balanced thus thread overload on particular
RncLmUe becomes more difficult to reach. On system level, this results in RNC
being more robust to RRC signaling rejections caused by thread load under heavy
traffic.
Operation
The following counters are introduced for measuring the load of each RncLmUe
thread:
— RncModule::pmLmUeMcThreadLoad
— RncModule::pmSamplesLmUeMcThreadLoad
— RncModule::pmSumLmUeMcThreadLoad
— RncModule::pmSumSqrLmUeMcThreadLoad
The following counters are introduced for measuring the load of each LmCell
thread:
— RncModule::pmLmCellMcThreadLoad
— RncModule::pmSamplesLmCellMcThreadLoad
— RncModule::pmSumLmCellMcThreadLoad
— RncModule::pmSumSqrLmCellMcThreadLoad
After upgrade, the values of the following counters are evaluated by using the
RncLmUe thread load value:
— RncModule::pmMeasuredLoad
— RncModule::pmSumMeasuredLoad
— RncModule::pmSumSqrMeasuredLoad
The average load taken from processing units assigned to MCs working on the
same processor is no longer taken into consideration in the evaluation. As a
result, rapid change can be observed in the values reported by these counters and
the related formulas. For more details, see Processor Load Management.
Interfaces
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 107

Hardware
The improvement is applicable only for EvoC 8300.

ENM version 21.2 or later is required for this improvement.
2.2.73 21.Q3: AISG 3.0 Support - Antenna Near Unit Functionalities
This feature enhancement introduces functionalities from the AISG 3.0

standard.

Benefits
The feature enhancement introduces the following functionalities from the AISG
3.0 standard:
— Support for version selection for RET and TMA subunits
— Improved download function on Antenna Line Devices (ALDs)
— New upload function on ALDs
— Functionality to collect new operational and diagnostic information
— Update for device scan to gather the following information:
• Configuration checksum
• DC power information
• Subunit capabilities
• Subunit standard versions

No impact.
108 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
The feature enhancement introduces the following new alarms:
— Antenna Communication Problem
— ALD Failure
The feature enhancement introduces read-only MO attributes and MO actions.
Table 17 Introduced MO attributes

MO Attributes Description
AntennaNearUnit.uploadState Displays the progress of the upload
procedure.
AntennaNearUnit.configurationCh Displays the checksum of the currently
ecksum used ALD configuration.
AntennaNearUnit.powerMode Indicates the current power mode of
the antenna near unit.
AntennaNearUnit.powerModeValues Displays the ALD power consumption
of all possible power modes.
AntennaNearUnit.lastReset Displays information about the last
ALD reset.
RetSubUnit.configuredAisgRetVer Displays the configured AISG version
sion for the RET subunit.
RetSubUnit.supportedAisgRetVers Lists the AISG versions supported by
ion the RET subunit.
TmaSubUnit.configuredAisgTmaVer Displays the configured AISG version
sion for the TMA subunit.
TmaSubUnit.supportedAisgTmaVers Lists the AISG versions supported by
ion the TMA subunit.
Table 18 Introduced MO Actions

MO Actions Description
AntennaNearUnit.setAisgVersionF Sets the AISG standard version for the
orSubunitType specified subunit type.
AntennaNearUnit.sendInformation Sends an information file to an ALD.
File
AntennaNearUnit.sendConfigurati Sends a configuration file to an ALD.
onFile
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 109

MO Actions Description
AntennaNearUnit.receiveLogFile Downloads a log file from an ALD, and
stores it at an external SFTP location.
The received file contains the logs for
the ALD.
AntennaNearUnit.receiveInformat Downloads an information file from an
ionFile ALD, and stores it at an external SFTP
location. The received file contains
data with no operational impact.
RetSubUnit.receiveLogFile Downloads a log file from an ALD, and
the specific subunit only.
TmaSubUnit.receiveLogFile Downloads a log file from an ALD, and
the specific subunit only.
Interfaces
No impact.
Hardware
The enhancement has the following hardware limitations:
— The enhancement works only with AISG 3.0 compatible near ALDs.
— Only RET and TMA subunits are supported.

No impact.
2.2.74 21.Q3: Collection of Troubleshooting Data Prior to Operator-initiated

Restart
Troubleshooting data is collected immediately before operator-initiated

Radio Node restart.
Feature Name System Improvements in WCDMA RAN

W21.Q3
110 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions


ESI/DCG data package now contains troubleshooting data collected prior to the
latest operator-initiated restart. Such restart will be postponed by up to 10
seconds in order to collect preselected volatile data considered most useful for
troubleshooting. This data will increase the chances of successful troubleshooting
of pre-restart faults.

Operator-initiated restart is postponed by up to 10 seconds. In-Service
Performance is not affected as restart duration is not changed.
Operation
— New MO AutoEsiM is introduced under MO NodeSupport to represent

functionality related to automated ESI operations. This MO is created by the
system.
— New MO PreRestartEsi is introduced under MO AutoEsiM for configuration

of pre-restart collection of troubleshooting data (part of ESI data). This MO is
created by the system.
— The new MO attribute volatileDataCollection (in MO class

PreRestartEsi) controls activation of the new functionality.
— Data collection will be activated by default. Operator can deactivate and

reactivate it.
For more information, see Data Collection Guideline.
Interfaces
No impact.
Hardware

network elements: ENM version 21.3 or newer.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 111

RELATED INFORMATION
Data Collection Guideline
2.2.75 21.Q3: Detect Baseband Replacement
Baseband unit replacement is recorded in the HwInvHistoryLog operator

log.

Benefits
The Hardware Inventory History Log records Baseband unit replacements.

No impact.
Operation
Information about a new Baseband unit is added to the Hardware Inventory
History Log.
The Hardware Inventory History Log can be exported from the RBS in the
following ways:
— With the introduced action HWInventoryHistorylog::export
— With the lghr | grep HWHI COLI command
— With the ESI package
Interfaces
No impact.
112 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Hardware

No impact.
2.2.76 21.Q3: Improved CPI for Setting Up Integration Infrastructure and Planning
for Integration
Integration CPI is enhanced with a new document describing the

integration infrastructure requirements and choices to consider, when
planning an integration of a Baseband Radio Node.


The document can aid the user preparing for integration by providing information
and guidance in the following aspects:
— Choice of the integration method and its implications, including hardware

binding and the use of a client on site.
— Integration infrastructure, consisting of the Transport Network, an instance

of the Ericsson Network Manager (ENM), and associated services.
The document is available in the Baseband Radio Node CPI collection, under the
following link: Integration Planning and Infrastructure Guidelines.

No impact.
Operation
No impact.
Interfaces
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 113

Hardware

No impact.
2.2.77 21.Q3: Node Health Validator Customization of Input Parameters
This Node Health Validator enhancement introduces possibility to edit input

parameters for health checks.

Access Type: WCDMA
Benefits
This enhancement allows user of Node Health Validator to specify health check
input parameters, for example threshold for executed checks, to fit configuration
and diagnostics conditions better.
The user is provided with an easy-to-use graphical interface for both laptop and
mobile device, at site and remotely, to execute and customize thresholds for all
applicable health checks available on the node.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
114 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.2.78 21.Q3: Random Delay Solution for User Enumeration

This system improvement introduces a method to synchronize login failure delay

across different user types to increase account security.
The synchronization of the login failure delay is achieved by the introduction of

an attribute to ensure a random login failure delay across maintenance, LDAP
and fake users.
Benefits
This system improvement increases the account security by giving the option to
have a synchronized delay for all users.

No impact.
Operation
This improvement introduces the
MaintenanceUserSecurity.loginDelayPolicy attribute for maintenance users
with the RANDOM default value.
The MaintenanceUserSecurity.loginDelay attribute becomes valid only when

the MaintenanceUserSecurity.loginDelayPolicy attribute is set to FIXED.
Interfaces
No impact.
Hardware
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 115


ENM version 21.10 or later is recommended for this improvement.
2.2.79 21.Q3: Summary View for Baseband Cells in EMGUI
This EMGUI enhancement introduces possibility to display cells configured

on a Baseband Radio Node.

Access Type: WCDMA, GSM, LTE, NR
Benefits
This enhancement introduces the ability to view the status and relation to the
hardware of cells configured on the Node from the EMGUI tool.
With this function, the user is able check what are the configured cells, what is
their status. It is also possible to check the equipment to which the cell is
assigned. That helps during on site activities like maintaining the node, hardware
replacement, fault finding.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
116 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.2.80 21.Q3: WCDMA Baseband Reset on Baseband 6621/Baseband 6631
WCDMA baseband reset behavior on Baseband 6621/Baseband 6631 is

different from other Baseband units.

Release
Access Type: WCDMA

GSM baseband restart caused by software fault leads to WCDMA baseband
restart in the following configurations:
— W+G on Baseband 6621
— L+W+G on Baseband 6631
On other Baseband units, GSM baseband restart in this case does not impact
WCDMA.

WCDMA traffic is lost temporally at the restart.
Operation
No impact.
Interfaces
No impact.
Hardware
It applies to the following Baseband units:
— Baseband 6621
— Baseband 6631
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 117


No impact.
2.2.81 21.Q4: Configurable Observability for Long Alignment Process between CC

or DC Devices and C1 Board
This system improvement introduces configurable observability for the long

alignment process of RNC Frame Number counter synchronization between
CC or DC devices and the C1 board.

Release
Node Type: RNC
Access Type: WCDMA

This system improvement raises FM events at the start and the end of a long
alignment process between the CC or DC devices and the C1 board.
Loss of synchronization between CC or DC devices and the C1 board can cause

Accessibility and Retainability KPI degradation. To synchronize CC or DC devices
and the C1 board, the alignment process is triggered automatically, and can take
maximum up to 30 minutes.
The configurable limits for the following factors determine whether the
alignment process is treated as a long alignment process:
— The time that is needed for the CC or DC devices to align to the C1 board.
— The number of the CC or DC devices that are out of synchronization.
This system improvement ensures the following benefits:
— Visibility of the long time alignment process between the CC or DC devices

and the C1 board.
— Ability to estimate how long the alignment takes.
— Information on whether the experienced KPI degradation is related to loss of

synchronization between CC or DC devices and the C1 board.
118 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
The system improvement introduces the following attributes:
— TimDevice::longAlignmentDevicesThresh
— TimDevice::longAlignmentTimeThresh
The system improvement introduces the following FM events:
— TimDevice_LongAlignmentIndication
— TimDevice_LongAlignmentFinished
The TimDevice_LongAlignmentIndication FM event indicates that a long

alignment process has started. The event is raised if all the following conditions
are met:
— The time that is needed for CC and DC devices to align to the C1 board is
higher than the value of the TimDevice::longAlignmentTimeThresh
attribute.
— The number of these CC and DC devices is equal to or higher than the value
of the TimDevice::longAlignmentDevicesThresh attribute.
By configuring these attributes, the time and the CC or DC device amount

thresholds for raising the TimDevice_LongAlignmentIndication FM event are
determined. Setting the value of the
TimDevice::longAlignmentDevicesThresh attribute to 0 disables raising the
FM events.
The TimDevice_LongAlignmentIndication FM event provides an estimated

time that is needed for performing the alignment. This event is triggered again if
the CC or DC devices imply longer time alignment process, than indicated before.
The TimDevice_LongAlignmentFinished FM event indicates that the long

alignment process is finished.
The introduced spsync timealignment COLI subcommand provides the

following information:
— The number of devices that are out of synchronization
— The time needed for finishing the synchronization
— The list of the devices that are out of synchronization

No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 119

Interfaces
No impact.
Hardware

No impact.
2.2.82 21.Q4: MAU Ethernet Connectivity Down Alarm in EvoC 8200
This system improvement introduces the MAU Ethernet Connectivity

Down alarm in EvoC 8200 RNC node. This alarm is raised, if the physical
connection is broken between a Medium Access Unit (MAU) and an external
device.

Node Type: RNC
Access Type: WCDMA

This system improvement detects and reports physical link failures to the
operator by raising the MAU Ethernet Connectivity Down alarm. The alarm is
raised for both active and stand-by MAUs.
The Operation and Maintenance (OAM) loss because of physical connection loss
can be prevented by the early detection of physical link failures.

No impact.
Operation
The operator can enable or disable the MAU Ethernet Connectivity Down
alarm by configuring the MediumAccessUnit::ecdReporting attribute. The
alarm is enabled by default.
120 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
It is recommended to keep this alarm enabled to fix cable connectivity failures for
a MAU.
After upgrading the node with the software version that contains this system
improvement, the MAU Ethernet Connectivity Down alarm is raised, if
physical link failure occurs to the MAU.
Interfaces
No impact.
Hardware
This system improvement is applicable for the EvoC 8200 RNC node.

No impact.
2.2.83 21.Q4: Security Event Logging for Anonymized Event Data
Anonymized Event Data is enhanced with the ability to record security

events.

Node Type: RNC
Access Type: WCDMA

Anonymized Event Data encrypts sensitive identifiers but does not block the
tracing functions, which are used in various diagnostic and troubleshooting
cases. The feature is enhanced with security event logging, to prevent
unauthorized and unsupervised use of tracing functions.

No impact.
Operation
A security Event is recorded when one of the following conditions occur:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 121

— The Anonymized Event Data feature is activated, deactivated, the activation

fails, or the encryption key is changed.
— The ueidtrace, UETR, UERTT, GPEH, CTR, or RDT function is enabled or

disabled.
Events are collected in the node security log and streamed as Real Time Security
Events to an external SysLog server. The log can be accessed with the lgy AMOS
command.
The enhancement introduces the following events:
— RNC_ANONYMIZATION_ACTIVATED
— RNC_ANONYMIZATION_DEACTIVATED
— RNC_ANONYMIZATION_FAILURE
— RNC_ANONYMIZATION_KEY_CHANGED
— RNC_USER_DATA_INTERNAL_TRACE_ACTIVATED
— RNC_USER_DATA_INTERNAL_TRACE_DEACTIVATED
— RNC_USER_DATA_TRACE_ACTIVATED
— RNC_USER_DATA_TRACE_DEACTIVATED
— RNC_USER_DATA_PROTECTION_ENABLED
— RNC_USER_DATA_PROTECTION_DISABLED
For details, see External Security Syslog Events.
Interfaces
No impact.
Hardware

No impact.
122 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.3 Optional Impact at Upgrade

Overview information about the globally released and unrestricted changes to
the network performance and operation. The changes take effect only when
manually activated.
2.3.1 20.Q1: Assisted Time Holdover for PTP over Ethernet
This enhancement introduces SyncE as an assisting reference when PTP

over Ethernet is applied as a primary reference.
Feature Name: Assisted Time Holdover

Value Package Name: Time and Phase Synchronization
Access Type: LTE, WCDMA, GSM, NR
Benefits
This feature enhancement enables SyncE support for the Assisted Time Holdover
feature when PTP over Ethernet with G.8275.1 profile (Full Timing Support) is
applied as primary reference.
The main benefits of this enhancement are the following:
— The longer time holdover periods allow the TDD and the FDD to run for a
longer time during a temporary time synchronization reference outage.
— The longer time holdover periods allow more flexible planning of repair
actions.

No impact.
Operation
The SyncE support for the Assisted Time Holdover feature when the feature is
using PTP over Ethernet as primary reference can be observed by reading the
RadioEquipmentClock.timeAssistedHoldoverSec counter.
The time holdover duration provided by SyncE assisting reference depends on the
SyncE source quality.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 123

Interfaces
No impact.
Hardware

This enhancement requires ENM version 19.4 or later to be used.
2.3.2 20.Q1: Cell Broadcast Support for EvoC 8300
This enhancement introduces Cell Broadcast Service for EvoC 8300 nodes.
Feature Name: Cell Broadcast Service

Value Package Name: Public Warning
Node Type: RNC
Access Type: WCDMA
This enhancement enables the operator to send CBS messages on EvoC 8300
nodes.
In the countries where public warning is mandatory functionality, EvoC 8300 can
be offered as fully complementary to regulatory requirements.

No impact
Operation
This enhancement introduces the following changes:
— New InconsistentConfiguration alarm raising when IuBcLink MO
configuration with O&M IP Host is used (IuBcLink::administrativeState
attribute is set to UNLOCKED and IuBcLink::ipTerminationRef attribute
is set to EMPTY).
Interfaces
Iu-BC transport is available on EvoC 8300 nodes.
124 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Only configuration with separate IP host, dedicated to communication with CBC,

is possible on EvoC 8300 nodes.
Hardware

No impact.
2.3.3 20.Q1: Health Check-Based Site Acceptance Improvement
Health check for site verification and acceptance is improved.

Access Type: WCDMA
Benefits
With this improvement, all health check rules are customizable on health check
job level.
Table 19 shows the changes of health check rules and categories that are
applicable for WCDMA.
Table 19 Changes of Health Check Rules and Categories

Category Description
SITE_ACCEPTANCE Existing category, which includes the
following health check rules before:
— Check Hardware Status
— Check Sector Status
— Check VSWR Status
— Check RET Status
— Check TMA Status
— Check RAE Status
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 125

Category Description
The following health check rules are
added to this category:
— Check WCDMA Traffic
— Check Node B Local Cell Status
— Check Synchronization Clock
— Check Synchronization Reference
— Check CPRI Link Status

ALL New category, which includes all
health check rules.
OTHER This category is removed.
For more information, refer to Manage Node Health Check.

No impact.
Operation
To perform health check, refer to Manage Node Health Check.
Interfaces
No impact.
Hardware

ENM 20.1 is required to perform health check for site verification and acceptance.
2.3.4 20.Q1: PM Counter Filtering Improvement
A dedicated MOM attribute is introduced for each in-use PM counter to

improve handling PM information.
Feature Name: N/A

Feature Identity: N/A
126 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Value Package Name: N/A

Value Package Identity: N/A
Node Type: RNC
Access Type: LTE, WCDMA
Benefits
The PM counter filtering functionality introduced in 19.Q4 is now enhanced with
a dedicated MOM attribute pmCounterCategory. The tag contains classification
details, such as type, area, and scenario, used as a basis for filtering PM counters
in the MOM included in the CPI library. With the new tag, it is now possible to
introduce customized WoW improvements for handling PM information.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

Support for the tag available in ENM 19.1 and newer.
2.3.5 20.Q1: Signature Validation Service for Evo Controller 8200/RNC
The improvement ensures integrity of the software that is loaded into the
node and prevents unwanted modifications, by using digital software
certificate validation.
Feature Name: Signed Software

Node Type: RNC
Access Type: WCDMA
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 127

Benefits
Each software module to be loaded into the node is now digitally signed by
Ericsson. Modified and unsigned software is rejected during the validation.
Validation is performed during node upgrade, or during the manual installation of

Load Modules (LM).

Signature validation increases the node restart time by up to 30%. The increase
depends on the number of EPB with the EPB_BLADE_A allocation, installed in
the node and may be higher in large configurations.
Operation
The improvement introduces the svs COLI command to the RNC. The command is
used to activate the Signature Validation Service (SVS).
SVS is activated using svs [-enable], followed by a node restart, see Enabling
Signature Validation Service.
Interfaces
No impact.
Hardware
Applicable for Evo Controller 8200/RNC.

No impact.
2.3.6 20.Q1: Additional Text Improvements for Resource-Based Alarms
Feature Name: System Improvement

Baseband Radio Node
Access Type: GSM, WCDMA, LTE
The benefit of this System Improvement is that it is easier and quicker to find the
correct remedy actions thanks to the additional text alignment in the code, alarm
128 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
list, and CPI. The improved additional texts provide better understanding of the
fault.
The following alarms are impacted:

— Inconsistent Configuration
— MO Configuration Exceeds Resources Enabled by the Key

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.3.7 20.Q1: Automatic Enabling of Local Authentication and Authorization
With Local Authentication and Authorization (LAA) Database files installed,

LAA is automatically enabled on RNC and DU Radio nodes.
Feature Name: System Improvements in W20

Node Type: RNC
DU Radio Node
Benefits
LAAis automatically enabled on RNC and DU Radio Nodes when LAA Database
files are installed. L AA Database files manage the different levels of
authentication and authorization for different users.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 129

Telnet, FTP, UDP link handler and Debug server are disabled when LAA is
enabled. Password files handled by these protocols are deleted.

No impact.
Operation
The automatic enabling of LAA must be confirmed with a semcode command by
a Security Manager user.
Interfaces
No impact.
Hardware

network elements:
— ENM version 19.06 or later
2.3.8 20.Q1: Automated Software Upgrade Enhancement
This feature enhancement improves the end-to-end automation flow for

Baseband Radio Nodes and DU Radio Nodes.

DU Radio Node
Benefits
The enhancement introduces the following changes to improve the Automated
Software Upgrade procedure:
130 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— Support for a mixed batch of DU Radio Nodes and Baseband Radio Nodes in
one flow instance
— Support for soft upgrade option on Baseband Radio Nodes in ENM
— The following new building blocks in the setup phase of Automated Software
Upgrade:
— Post-install backup in the software preparation phase
— Clean-up script at the end of the software activation phase
— License validation in the software preparation and activation phases
— Email notification in the software preparation and activation phases

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

2.3.9 20.Q1: SAI Based Positioning Enhancement
The enhancement introduces support for direct SAI reporting.
Feature Name: SAI Based Positioning

Node Type: RNC
Access Type: WCDMA
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 131

Benefits
The enhancement introduces support for direct SAI reporting, that is the support
for message LOCATION REPORTING CONTROL. Table 20 presents the
configuration of Information Element (IE) Request Type.
Table 20 Information Element Request Type

Information Element Request Type Preferred Setting
Event Direct
Stop Direct
Report Area Service Area

In networks with URA_PCH used, SAI Based Positioning enhancement can
increase number of users in CELL_FACH state.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.3.10 20.Q1: Hardware Sensitive Install for Auto-Integration
Hardware sensitive install (HSI) is introduced for auto-integration.

Access Type: WCDMA
132 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Benefits
With the improvement, only the unzipped software applicable for the installed
hardware is downloaded to the node at auto-integration. For more information
about HSI, refer to Hardware Sensitive Install.
Note: Before software downloading, the installed hardware, Baseband and

ENM is connected through transport network.

Auto-integration duration is shortened.
Operation
No impact.
Interfaces
No impact.
Hardware
This improvement applies to the following hardware:
— Baseband Unit, including Baseband R503
— Radio unit

No impact.
2.3.11 20.Q2: Zero Touch Integration Simplified Late Binding
This enhancement introduces the possibility to assign static IP addresses

from DHCP based on the node logical name instead of the node serial
number. This functionality is applicable for Zero Touch Integration process.

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 133

Benefits
If a logical name is assigned to the node, it can be specified as the client identifier
during the DHCP request. This enhancement makes static IP address assignment
easier because the operator does not need to obtain the node serial number.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.3.12 20.Q2: CPRI Diagnostics Health Checks Enhancement
This improvement introduces health checks related to SFP compatibility.

Access Type: WCDMA
Benefits
The main benefit of this improvement is that it facilitates automation and
reduces the lead time of verification processes.
The improvement introduces the following health check rules to test if the SFP
module used in the hardware configuration follows the recommendations of SFP
Module Selector Guide:
134 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— Check enabled SFP module validation info on RI Port
— Check SFP and board compatibility on RiLink
For more information, see Manage Node Health Check.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.3.13 20.Q2: ANR Mobility for IAF CELL_DCH
This enhancement enables the ANR Mobility feature to use the Automatic
Neighbor Cell List (ANCL) for maintaining Intra-Frequency (IAF) neighbors.
When a neighbor is found, it is marked as CANDIDATE_FOUND in CRS. The
marked neighbor is copied to the ANCL.
Feature Name: ANR Mobility

Value Package Name: ANR
Node Type: RNC
Access Type: WCDMA
Each cell has one ANCL which contains both operator-defined and ANR-
discovered IAF neighbors. The ANCL is sorted periodically according to the
dynamically calculated priorities of the neighbors.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 135

The RNC can keep up to 128 IAF neighbors per UtranCell MO instance in ANCL,
instead of 31 IAF relations defined in MOM.
The operator can activate automatic removal of UtranRelation MOs to delete

the neighbors that are not used for a long time.
The enhancement includes the Persistent Storage handling.
When the IAF ANCL is active, the neighbor marked as CANDIDATE_FOUND in

CRS table is copied to ANCL table. Therefore, after the deactivation, restart or
upgrade of the IAF ANCL, the RNC candidates found by ANR are not lost.
The legacy Persistent Storage functionality which saves CRS entries restores a
full list of neighbors. It also protects the system against KPI degradation because
of missing neighbors.

Turning on IAF ANCL can slightly increase load on MP processor.
Operation
To activate ANR Mobility for IAF CELL_DCH, the value of
AnrIafUtran.anrAnclEnabled attribute must be set to ON on the RNC level.
This enhancement introduces the following parameters:

— AnrIafUtran.anrAnclEnabled
— AnrIafUtran.anrRemoveRelationEnabled
— ExternalUtranCell.antennaPosition
— RemoteUtranCell.antennaPosition
— The following parameters in structure anrIafUtrancellConfig in the

UtranCell MO class:
• relationRemoveEnabled
• sib11IafAnclEnabled
Interfaces
The ANR-discovered neighbors are sent from DRNC to SRNC in RNSAP messages
containing neighbor cell list.
Hardware
136 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
2.3.14 20.Q3: Automated Configuration of AISG Devices
AISG devices can be configured automatically depending on the AISG

device scan results.
Feature Name: System Improvement in W20.Q3

Access Type: WCDMA
Benefits
With this improvement, the operator does not need to manually input the
hardware specific data for the device configuration.
The improvement brings the following benefits:

— The procedure for integrating AISG devices is simplified.
— The effort and time for site configuration is reduced.

No impact.
Operation
The automated configuration can be enabled by setting the new attribute
EquipmentDiscovery::autoCreateAisgUnits to TRUE. After AISG device scan
is completed, the automated configuration is performed automatically.
Note: If the device in AISG device scan results is configured already, the device
is excluded during the automated configuration.
The status of the AISG device scan and automated configuration is monitored by
the new attribute EquipmentDiscovery::equipmentDiscoveryStatus,
replaced the attribute EquipmentDiscovery::antennaDeviceScanStatus.
For more information about automated configuration, refer to Manage Hardware

Equipment.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 137

Interfaces
No impact.
Hardware
This improvement is applicable for the following AISG devices:
— AISG 2.0 Device:
— Single-antenna RET
— Multi-antenna RET
— TMA
— TMF
— AISG 2.1.0 Device:

— RAE

No impact.
2.3.15 20.Q3: Soft Lock during Upgrade for WCDMA
The system improvement introduces soft upgrade for Baseband Radio

Nodes.

Access Type: WCDMA
Benefits
With the soft upgrade, traffic can be redirected to overlapping cells served in
adjacent nodes. This avoids service interruptions caused by upgrade restart.
Note: Without overlapping coverage, service interruptions cannot be avoided

even if the soft upgrade is selected.
138 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

The soft upgrade takes a longer time to complete than the hard upgrade.
Operation
In the activation phase of the software upgrade procedure, operators can choose
HARD or SOFT upgrade mode.
For the detailed upgrade procedure, refer to Manage Software.
Interfaces
No impact.
Hardware

No impact.
2.3.16 20.Q3: VSWR Antenna System Validation
This improvement introduces a new MO class to perform VSWR check at

installation, extending the Antenna Return Loss Frequency Sweep.
Feature Name: System Improvements

Access Type: WCDMA
Benefits
The improvement provides early detection and fast restoration of installation
problems in antenna systems. A basic test validates antenna system
malfunctions by measuring return loss. This solution provides the following main
benefits:
— Simplified evaluation of test results
— Improved VSWR measurement accuracy
— Support in validation of the raised VSWR supervision alarms
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 139


No impact.
Operation
To perform the VSWR check, the backhaul connection must be available. The
cells have to be enabled for radio or RF ports for which the test results are
required.
The check can be initiated by the manually created RfVswrInstallationCheck

MO class. When the RfVswrInstallationCheck.performCheck action is
triggered, return loss is measured for all RF ports involved in the sequence based
on the input parameters.
The test result is calculated on the basis of the values of

RfVswrInstallationCheck.thresholdLow and
RfVswrInstallationCheck.thresholdHigh attributes. The attribute values can
be either default or user-defined. Test results are displayed for each band on each
tested RF ports.
The antenna system validation VSWR test is supported on the following levels:
— Rf port
— Radio
— Node
Note: The VSWR check result of an RF port can be inconsistent with the VSWR
supervision alarm status, because the measurement methods and
applied thresholds can be different.
Interfaces
No impact.
Hardware
Valid only for radios supporting Antenna Return Loss Frequency Sweep.
Check the relevant Radio Description to determine if the radio supports Antenna
Loss Frequency Sweep.

This improvement requires MOShell version 20.0g. If MOShell is configured to use
CLI only NODE of check is supported.
If CLI is used to start check on RF Port or Radio level, only one LDN is supported
in the action parameter specifying LDNs to test.
140 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.3.17 20.Q3: IKEv2 Fragmentation
This feature enhancement enables the fragmentation of large IKEv2

messages by IKEv2 itself. Thus, fragmentation of IKEv2 message at IP level
is not needed and network issues caused by IP fragments can be avoided.
Feature Name: IPsec

Value Package Name: IPsec
Benefits
The enhancement has the following benefits:
— IKEv2 messages can traverse network devices that do not allow IP
fragments to pass through.
— With IKEv2 fragmentation, IKE messages are less likely to be subject for
Denial-of-Service attacks than large IKEv2 messages that require IP
fragmentation.
Note: — The enhancement cannot be used when establishing the first

temporary IPsec VPN connection for Zero Touch Integration.
— IKEv2 fragmentation is only applicable if both peers enable

fragmentation.

No impact.
Operation
To configure the feature enhancement, the
Ikev2PolicyProfile.ikev2Fragmentation attribute is introduced. The
enhancement is disabled by default.
For more information on enabling IKEv2 fragmentation see Manage IPsec.
Interfaces
No impact.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 141

Hardware

ENM version 20.12 or later is required for this enhancement.
2.3.18 20.Q3: Introduction of Trace Streaming in Ramdisk Mode for EvoC 8300
This system improvement introduces trace streaming in ramdisk mode for

EvoC 8300.

Node Type: RNC
Access Type: WCDMA
Trace streaming in ramdisk mode is used to store traces from early startup of the
node as it does not require IP stack. This mode of trace streaming configures
more number of sub-buffers than trace and error log to accommodate more
number of traces. This feature uses 50MB of ramdisk memory at any point in time
as a circular buffer.
Snapshots recorded in ramdisk mode are in CTF format. To view the traces, the
user needs to copy the archived snapshots to the host machine and use babel
trace viewer to read the traces.

No impact.
Operation
The ramdisk session can be enabled by using the COLI command. The following
commands are introduced with this feature:
ts ramdisk activate
This command starts the ramdisk session.
ts ramdisk save Records the current snapshot file. Renames and zip the
file, and saves the file in ramdisk log directory path.
142 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
ts ramdisk ls Lists and displays the files present in the ramdisk log
directory.
Interfaces
No impact.
Hardware
This improvement is applied only for EvoC 8300.

No impact.
2.3.19 20.Q4: Hardware Inventory History Log
When hardware units are replaced during operation, a record is stored in the
Inventory History Log.

Access Type: WCDMA
Benefits
When hardware replacement is made during operation, the information of the
new hardware unit is recorded in the Hardware Inventory History Log.
With the log, operators can easily track the history of hardware replacement.

No impact.
Operation
The HWInvHistoryLog MO is introduced.
The operator can access the Hardware Inventory History Log by one of the
following ways:
— New action HWInvHistoryLog::export
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 143

— COLI command lghr | grep HWHI
— ESI package
For detailed log information in ESI package, refer to Manage Hardware

Equipment.
Interfaces
No impact.
Hardware
The following hardware replacements can be recorded in the log:
— Field Replaceable Units except baseband units
— Hardware units with a product number or serial number, but do not belong to
the FRU category
Note: The replacement information of battery unit is not recorded in the

log.

No impact.
2.3.20 20.Q4: Observability for Robust Call Retention during O&M Disturbances
This improvement introduces PM counters for observing the Robust Call

Retention during O&M Disturbances system improvement.

Node Type: RNC
Access Type: WCDMA
Benefits
PM counters are introduced to measure the success rate of the Robust Call
Retention during O&M Disturbances system improvement. The improvement also
allows to observe the level of use of the Call Re-establishment and the Call Re-
establishment for PS features, which are used to save the connection during O&M
disturbances in case all radio links from the active set are lost.
144 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

No impact.
Operation
The following PM counters are introduced on Handover level:
— Handover.pmNoCallRetentionCandidates
— Handover.pmNoCallRetentionRLReleaseTriggered
— Handover.pmNoCallRetentionRLReleaseSuccess
The following PM counters are introduced on UTRAN cell level:

— UtranCell.pmNoCallRetentionCallReestReq
— UtranCell.pmNoCallRetentionCallReestAtt
— UtranCell.pmNoCallRetentionCallReestSucc
The introduced counters are not included in any predefined scanner and can be
activated manually.
Interfaces
No impact.
Hardware

No impact.
2.3.21 20.Q4: PM Counter Categorization for Observability Use Cases
Feature Name: System Improvements in WCDMA

RAN W20
Access Type: LTE, WCDMA, GSM
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 145

Each in-use node PM counter and EBS counter is classified into a PM category
which includes type, area and scenario. The operator can use the provided
categorization to narrow down the list of counters to a subset applicable to a
particular observability use case. The categorization of each PM counter into
type, area and scenario, is listed in their MOM description in the CPI MOM as well
as in the Lists and Delta Lists document.
The Managed Object Model (MOM) PM Counters folder in the CPI library has a
filtering function to narrow down the list of node PM counters to a subset
applicable to a particular observability use case. For more information, see
section Counter Categories and Filtering in Manage Performance.
Benefits
The improvement will extend the current information for PM counters. The
description of the PM counters is unified and described in a common way.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
2.3.22 20.Q4: Assisted Time Holdover, PTP G.8275.1 Assisting GNSS

Access Type: LTE, WCDMA, GSM, NR
146 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
The feature enhancement introduces PTP over Ethernet according to ITU-T

G.8275.1 as an assisting reference, when GNSS is used as primary reference.
With this enhancement, the Assisted Time Holdover feature provides longer time
holdover periods by using PTP over Ethernet G.8275.1 reference.
Benefits
The main benefits of this enhancement are the following:
— The longer time holdover periods allow the TDD and the FDD to run for a
longer time during a temporary time synchronization reference outage.
— The longer time holdover periods allow more flexible planning of repair
actions.

No impact.
Operation
The time holdover duration provided by PTP over Ethernet G.8275.1 assisting
reference depends on the PTP source quality.
The support for the Assisted Time Holdover feature can be observed by reading
the RadioEquipmentClock.timeAssistedHoldoverSec counter.
Table 21 shows the parameter changes introduced by this enhancement.
Table 21 Parameter Changes

Affected Parameter Description
AssistingReference.encapsulatio The parameter refers to the
n BoundaryOrdinaryClock.ptpProfil
e parameter set to G_8275_1.
Interfaces
No impact.
Hardware

ENM 20.3 or later is required for this feature enhancement.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 147

2.3.23 20.Q4: Support for Multiple RNCs with EvoC RNC Geo-Redundancy
This enhancement provides an emergency recovery solution for three or

more RNCs by introducing the circular redundancy configuration.
Feature Name: EvoC RNC Geo-Redundancy

Node Type: RNC
Access Type: WCDMA
Benefits
This enhancement provides the following benefits:
— Emergency redundancy solution for three or more RNCs, without a need to
deploy additional hardware
— Support cell relation modification in DRNCs towards redundant RNCs

No impact.
Operation
Three or more RNCs can be configured with circular redundancy. Each Iub link
selected for redundancy must be configured in two RNCs, one primary and one
redundant RNC. Each RNC must have redundant Iub links only from one other
RNC.
The configuration cannot exceed system limits for the number of cells, cell
relations, and Iub links.
For more information, see EvoC RNC Geo-Redundancy and Configure Geo-
Redundancy.
Interfaces
No impact.
Hardware
148 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Reconfiguration in the core network might be needed to include the RNCs with
redundant Iub links in the same location area and Routing Area. During the Iub
switchover and Iub rollback actions, cell relations in neighboring Ericsson and
non-Ericsson RNCs, LTE, and GSM networks must be reconfigured.
Updates in the core network might be required because Iub links are handled by
a different RNC if the primary RNC is down.
AMOS version 20.0n or higher is required for this enhancement.
2.3.24 20.Q4: LTE Measurements Enhancement: Prolong DCH State to Complete

Measurements
This enhancement introduces a mechanism for prolonging the duration of

CELL_DCH state to finish ongoing LTE measurements.

Measurements in LTE
FAJ 121 4277 R2
Node Type: RNC
Access Type: WCDMA
This enhancement introduces the following operator configurable timer:

— lteMeasCmDchProlongTimer
The timer is started along with the start of compressed mode for LTE
measurements. Triggers to perform channel switch because of inactivity are
ignored while the timer is running. After the expiration of the timer, no changes
are expected in the handling of triggers. If no 3c measurement report is received
and data transmission is resumed before the expiration of the
lteMeasCmDchProlongTimer, downswitch is not performed.
The enhancement increases the probability of receiving 3c measurement report

after the start of LTE measurements. This leads to the following benefits:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 149

— Higher success rate of LTE measurements
— Lower stop rate of LTE measurements
— Reduced number of LTE measurements with compressed mode
— Better utilization of compressed mode resources
— Increased number of PS handover attempts or Release with Redirection

actions

For more information about how to measure success rate, see LTE
Measurements.
The following PM counters are introduced to observe the effects of the

enhancement:
— UtranCell.pmLteMeasCmDchProlong
— UtranCell.pmLteMeasCmDchProlongWithE3c
The following counters are affected by the enhancement:

— UtranCell.pmCmTriggLteMeas
— IurLink.pmCmTriggLteMeas
— UtranCell.pmLteMeasCmStart
— IurLink.pmLteMeasCmStart
— UtranCell.pmLteMeasReportEval
— IurLink.pmLteMeasReportEval
— UtranCell.pmLteMeasStop
— IurLink.pmLteMeasStop
— UtranCell.pmLteMeasTimeout
— IurLink.pmLteMeasTimeout
— UtranCell.pmNoRwrEutraBasedMeasReport3c
— IurLink.pmNoRwrEutraBasedMeasReport3c
— UtranCell.pmOutPsHoLteMeasReq
— IurLink.pmOutPsHoLteMeasReq
150 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— UtranCell.pmOutPsHoLteMeasAtt
— IurLink.pmOutPsHoLteMeasAtt
— UtranCell.pmPsIntDchToFachAtt
— UtranCell.pmPsIntDchToFachSucc
— UtranCell.pmPsIntHsToFachAtt
— UtranCell.pmPsIntHsToFachSucc
— UtranCell.pmOutPsHoEutraReq
— IurLink.pmOutPsHoEutraReq
— UtranCell.pmOutPsHoEutraAtt
— IurLink.pmOutPsHoEutraAtt
— UtranCell.pmRedirectAttemptsEutra – Impacted only if dchToFach or

csFallbackDchToFach triggers are enabled for RwR.
— IurLink.pmRedirectAttemptsEutra – Impacted only if dchToFach or

csFallbackDchToFach triggers are enabled for RwR.
Operation
This enhancement introduces the following attribute:
— UeMeasControl.lteMeasCmDchProlongTimer
The attribute determines the time while the ongoing LTE measurements cannot
be stopped because of the downswitch caused by inactivity.
Setting the attribute to 0 disables the enhancement.
This enhancement is not active by default.
Interfaces
No impact.
Hardware

network elements:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 151

— UE:
— Release 8 and support E-UTRAN Measurement
— LTE RAN:
— L17A
— Coverage-Triggered WCDMA IRAT Handover (FAJ 121 0897)
— Coverage-Triggered WCDMA Session Continuity (FAJ 121 0493)
2.3.25 21.Q1: Improvement of Security and Audit Trail Logs for EvoC 8300
The improvement introduces Real-Time Security Event Logging support for

EvoC 8300.
Feature Name: Real Time Security Event Logging

Value Package Name: Secure OAM and Security Logging
Node Type: RNC
Access Type: WCDMA
The improvement extends the functionality of the Real-Time Security Event

Logging feature, to support the logging of security events from both CPP and
RNC applications to an external Syslog server. UDP and TLS over TCP modes are
supported for transporting the events to an external Syslog server.
The feature is protected with certificate-based TLS tunnels in TLS over TCP
mode. TLS 1.0 and TLS 1.2 protocols are supported for TLS communication.
Using this feature, applicable events from External Security Syslog Events are
logged on to an external Syslog server.
For more information about the Real-Time Security Event Logging feature,
configuration and supported TLS cipher suites, see Security for O&M Node
Access.

No impact.
152 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Operation
This is a licensed feature. Before feature activation, a valid feature license must
be installed on the Node. The feature can be activated by setting the
RealTimeSecLog.featureState attribute to ACTIVATED.
The Real Time Security Event Log Fault indicates a problem with the Real-
Time Security Event Logging feature.
Interfaces
Real-Time Security Event Logging is over the Mur interface and is protected with
TLS in TLS over TCP mode.
Hardware
With this improvement, the Real-Time Security Event Logging feature is
supported on all RNC types.

The feature requires the node to be connected to an external Syslog server to log
the security events.
2.3.26 21.Q1: Baseband Unit Replacement With Node Serial Number Used for
IPsec Node Certificate
This feature enhancement introduces a solution for automatic node

hardware replacement for cases when the operator configures the IPsec
node credentials based on the hardware serial number.

Access Type: NR, LTE, WDCMA, GSM
The solution is applicable for nodes in public IP networks that use IPsec node
credentials based on the hardware serial number. Hardware replacement
scenarios using Zero Touch and LMT are supported.
The easy hardware replacement solution introduced with this feature reduces the
number of on-site manual activities during the replacement process.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 153


No impact.
Operation
If the hardware serial number is used as part of the IPsec node credentials
(subjectAltName and optionally subjectName), and the ENM Integration
Engineer initiates the hardware replacement using an ENM Auto Provisioning
project, the IPsec node credentials are updated automatically.
Interfaces
No impact.
Hardware
No impact.

2.3.27 21.Q1: Health Check Management Improvements
The improved health check management provides more accurate and

detailed results.

Access Type: WCDMA
Benefits
The improvements are as following:
— A list of categories supported on the node is provided for reference in the

attribute HealthCheckM::supportedCategories.
— It is now possible to delete jobs to keep the number of health check jobs no
more than 30. Operators can change the attribute HcJob::deletionPolicy
to define whether the job is deleted automatically or manually.
154 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— Health check rules are classified with the attribute HcRule::ruleType. The
attribute defines types of checking areas, such as traffic, link, cell, hardware,
and so on. This allows for the health check job status to be grouped and
checked by each type and subtype, through the attribute
HcJob::typeStatus and HcJob::subTypeStatus.
— Health check results are classified into success rules, locked rules, failed rules
respectively with the MO HcRuleSuccess, HcRuleLocked, and
HcRuleFailed. The detailed information for each entity checked by a success
or failed rule is provided with the MO SuccessHcRuleEntity and
FailedHcRuleEntity respectively.
Note: For the NodeBFunction rules, only the failed entities report results.
— The health check rules have the following changes:
• The rule Check Disk Space is split into two rules:
— Check Number of UPs: checking number of UPs on the node
— Check Disk Space: checking used disk space
• The rule Check VSWR Status has the following updates:
— The VSWR value is provided for each RfPort on entity level.
— The acceptance criteria change.
• The rule Check BER and Power Loss for Optical Link is assigned
to category SITE_ACCEPTANCE.
• Recommended action for all rules is more detailed.
For the detailed improvements, see Manage Node Health Check.

No impact.
Operation
The following MOs are introduced:
— HcRuleFailed
— HcRuleLocked
— HcRuleSuccess
— FailedHcRuleEntity
— SuccessHcRuleEntity
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 155

The following attributes are introduced:
— HealthCheckM::supportedCategories
— HcJob::deletionPolicy
— HcJob::subTypeStatus
— HcJob::typeStatus
— HcRule::outputParameters
— HcRule::ruleType
The attribute HcJob::failedRules is replaced by MO HcRuleFailed and

FailedHcRuleEntity.
Interfaces
No impact.
Hardware

To fully benefit from the health check improvements, the node requires ENM
version 21.3 or later. Before ENM support is in place, the improvements can only
be executed from the node.
2.3.28 21.Q1: Flexible PM Statistics
Flexible PM Statistics provides the possibility to define PM statistics ROP

(Recording Output Period) to 5-minute or 60-minute operator-controlled
granularity periods for RNC counters. The feature requires ENM 21.1 or
later.
Feature Name: Flexible PM Statistics

Value Package Name: WCDMA Base Package Features
Node Type: RNC
Access Type: WCDMA
156 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
In addition to the default 15-minute PM counter granularity period, an operator

can define less important counters with a longer 60-minute granularity period,
while more important counters, used in crucial KPI reports, with 5-minute
granularity period. The operator can use a combination of any two available
granularity periods. A counter can only be activated in one granularity period at a
time.
Benefits
Counter activation on 60-minute granularity period has the following benefits:
— Lower PM handling costs.
— Reduced hard disk usage for storing PM statistics data since data volume is
significantly lower which allows operators to increase the number of active
PM counters.
— Reduced module MP load because of less file writing.
— Reduced Mur bandwidth because of less frequent file fetching.
— Less frequent PM data collection on the ENM side, number of files from
nodes are reduced to one-fourth.
— Aggregation of PM files to one-hour report by ENIQ is no longer needed.
— Less frequent KPI report creation.
Counter activation on 5-minute granularity period has the following benefits:

— Enhanced detection of immediate network performance degradation
because of more frequent observation of crucial KPIs.
— Optimal network performance monitoring at all times.
— The combination of 5-minute and 60-minute granularity periods lowers PM

cost when less important KPI counters are moved to 60-minute scanners.
Data volume is reduced and more frequent observability for crucial KPIs is
still provided.

A short counter reporting period, for example a 5-minute period, demands more
ENM and RNC resources, involving CPU load, Mur bandwidth requirements, data
storage, and data processing. To minimize the CPU load impact, the 5-minute
granularity period ROP option is limited to the maximum of 10% of all active
counters defined by PmService.maxNoOfCounters.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 157

Operation
A single counter can be activated in PM scanners defined with only one
granularity period. Also, a maximum of two different granularity periods can be
applied for all defined PM scanners. The supported options are the following:
— 5-minute and 15-minute periods
To obtain proper results from a KPI formula, all counters used in this formula
must be defined with the same granularity period. It is recommended to check if
a given counter is used in a different formula that contains counters defined with
a different granularity period.
The Flexible PM Statistics feature is only supported for Standard Statistical

Subscriptions. For more information, refer to section Flexible ROP for Standard
Statistical Subscriptions in ENM Summary of External Interfaces, 2/15519-AOM
901 151, (available from Ericsson Network Manager, ENM, AOM 901 151 R1EF
library).
Interfaces
No impact.
Hardware
No specific hardware requirements.

2.3.29 21.Q2: Automatic Detection for Feeder Cable Problems
With the enhancement, the legacy feature solution is obsolete, and a new
feature solution is adopted to improve the usability.
Feature Name: Optimized Antenna Selection

Access Type: WCDMA
158 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Benefits
The new solution supports the following configurations:
— Up to six sectors.
— Dual band configuration. The Optimized Antenna Selection feature can run
on one of the bands.
The enhancement enables operators to discover feeder cable problems easily.
For more information, see Optimized Antenna Selection.

No impact.
Operation
This enhancement introduces the following changes:
— New attribute NodeBFunction::featCtrlOptmAntennaSelection is

introduced to control the feature.
— The unit of PM counter

NodeBSectorCarrier::pmOasDeltaRscpMeasurement is changed from 1
dB to 0.1 dB.
— The following two alarms can be raised when faulty antenna branches are
detected:
• RX Branch Imbalance Fault
• RX Diversity Lost
Interfaces
No impact.
Hardware
This feature supports radio units that connect to antenna units through feeder
cables.

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 159

2.3.30 21.Q2: Baseband Network Loader to Support All Update Paths

Benefits
It is possible for operators to upgrade Network Loader software successfully even
if the board has limited storage capabilities (Baseband 5216, Baseband 5212),
which enables the use of Zero Touch Integration.

No impact.
Operation
System improvement introduces stepwise upgrade procedure for Network Loader
on Baseband 5212/5216 boards specified in the Hardware section, where
customers need to run Zero Touch Integration with the latest Network Loader
version.
For detailed procedure, see Upgrade Network Loader document.
Interfaces
No impact.
Hardware
System improvement is applicable for the following boards and Network Loader
Type 2 versions:
— Baseband 5212: KDU 137 925/41 < R5A (Network Loader type 2 < R7U)
— Baseband 5216: KDU 137 925/31 < R5A (Network Loader type 2 < R7U)

No impact.
160 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.3.31 21.Q2: Optical Indication to Locate Physical Position of Radio Units
The enhancement introduces the "Here I Am" indication to help locate the
physical position of a radio.

Benefits
The function introduces a distinctive maintenance LED blinking pattern that
allows:
— identifying the correct Radio Unit to troubleshoot in case the cabling is

incorrectly marked.
— identifying the physical Radio Unit represented by a given MO without

affecting its availability and without relying on hardware labels.
— isolating the Radio Unit at the far end of the node fiber, which is helpful
during site installation, site modernization, HW replacement, and
troubleshooting.
— checking the correctness of fronthaul wiring.
It can be used by both Ericsson or non-Ericsson personnel working on-site.

No impact
Operation
The HereIAmIndication MO class is introduced with the MO actions:
startHereIAmIndication to activate and stopHereIAmIndication to
deactivate the "Here I Am" indication for Radio Unit.
To be able to locate the equipment, the "Here I Am" indication must be active on
a hardware unit represented by the parent of the HereIAmIndication MO.
Activation cannot happen during state transition.
The hereIAmIndicationState attribute on the HereIAmIndication MO has

two values:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 161

— ACTIVE: Indication is active, radio maintenance indicator is Double Flashing

and ON/OFF.
— INACTIVE: Indication is inactive.
The indication stops on the following conditions:

— after 6 hours
— after a restart
— if the maintenance button is pressed
— if the administrativeState attribute of the parent MO

FieldReplaceableUnit changes
— if stopped with the stopHereIAmIndication action
Hardware
The function supports radio groups: 3a (except Radio Dot), 3b, 4a (except third
party products), and 8.
See Radio Capabilities for detailed product numbers.
Interfaces
No impact.

No impact.
RELATED INFORMATION
Site Diagnostics
2.3.32 21.Q2: Automatic Health Check Execution for Greenfield Integration
Health checks for an integration project can be executed automatically.

162 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
Benefits
Node health checks can be triggered automatically by the ENM Auto Provisioning
tool as a part of the Zero Touch Integration process. For more details and a list of
applicable health check rules, see Integrate Baseband Radio Node.
For general information on the health checks, see Manage Node Health Check

No impact.
Operation
The name of the health check profile created in the ENM Node Health Check
application is referenced in the configuration files. The reference is added when
creating configurations.
Interfaces
No impact.
Hardware
Applicable for Baseband Radio Nodes.

2.3.33 21.Q2: EvoC RNC Geo-Redundancy: Reduced Time for Iub Switchover and
Iub Rollback
The enhancement introduces actions on the GeoRedundancy MO that are

performed directly on the RNC to set up the redundancy for two or more
RNCs on the customer network.
Feature Name: EvoC RNC Geo-Redundancy

Node Type: RNC
Access Type: WCDMA
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 163

This enhancement introduces actions on the GeoRedundancy MO in addition to

the existing gr command-based solution. The enhancement allows actions to be
performed directly on the RNC node.
Benefits
The enhancement provides the following benefits:
— The time needed to perform Iub switchover and Iub rollback is reduced.
— It is now possible to perform actions during maintenance window.
— Configuring redundancy requires less effort from the user, compared to the
existing solution.
— A new log is added to provide observability for troubleshooting purpose, and

it is visible with the lg8 AMOS command.
— It is now possible to perform actions when AMOS connection is not available

(using ncli over telnet/ssh).

After an Iub switchover action, the following results are expected:
— The restoration time of traffic and mobility takes several minutes.
— RNC restart time increases because additional MOs are configured on the
node and therefore it takes longer for the node to restart.
— RNC overload period depending on the RNC size because the increased
number of Iub links is handled by the same RNC.
Calling actions on the GeoRedundancy MO increases C1 load for the duration of

the action.
Operation
This enhancement introduces the GeoRedundancy MO.
The following actions are introduced under the GeoRedundancy MO:

— GeoRedundancy.checkIub
— GeoRedundancy.deleteIub
— GeoRedundancy.readAndUpdateConfiguration
— GeoRedundancy.rollbackDriftRnc
— GeoRedundancy.rollbackIub
— GeoRedundancy.storeConfiguration
164 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
— GeoRedundancy.switchoverDriftRnc
— GeoRedundancy.switchoverIub
The following attributes are introduced under the GeoRedundancy MO:

— GeoRedundancy.actionResult
— GeoRedundancy.currentGeoConfiguration
— GeoRedundancy.functionState
— GeoRedundancy.isGeoEnabled
— GeoRedundancy.sourceConfigurationFilePath
— GeoRedundancy.sourceDriftRncsConfigurationFilePath
— GeoRedundancy.switchedOverDriftRncs
The GeoRedundancy.isGeoEnabled attribute activates the enhancement.
When a configuration problem occurs, the Inconsistent Configuration alarm is

raised. For possible causes and how to clear them, see InconsistentConfiguration.
If the redundancy is configured by using the gr command-based solution and

migration to the MO actions-based solution is demanded, the grd command
must be performed first. After that, redundancy must be configured by using the
dedicated MO actions. For more information, see Configure Geo-Redundancy.
Interfaces
No impact.
Hardware

Reconfiguration might be needed in the Core Network for the following reasons:
— Iub links are handled by a different RNC, with a separate rncId.
— Both the primary and redundant RNCs must be included in the same
Location Area and Routing Area.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 165

This enhancement requires the following network elements:

— ENM version 21.2 or higher, or AMOS to configure the geo-redundancy.
— AMOS version 21.0d or higher, to use polg and lg8 commands.
2.3.34 21.Q3: Configurable Alarm Sync Inconsistent Configuration
The system improvement provides the possibility to disable the Sync

Inconsistent Configuration alarm.

Release
Benefits
Setting the RadioEquipmentClock.syncInconsistentConfigAlarmEnabled
attribute to false can stop the new raise of the Sync Inconsistent
Configuration alarm, and cease the already raised alarm immediately.

No impact.
Operation
The system improvement introduces the
RadioEquipmentClock.syncInconsistentConfigAlarmEnabled attribute.
When the value of this attribute is set to false, the Sync Inconsistent
Configuration alarm is disabled.
Interfaces
No impact.
Hardware
166 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

ENM 21.3 or later is required for this system improvement.
2.3.35 21.Q3: Random Time Delay at Login
This system improvement enhances brute force protection mechanism. The

mechanism is enhanced with support for randomized login delay on a failed
user login attempt along with existing fixed and incremental delay
configurations. Random delay configuration protects the node from user
enumeration attacks.


With this enhancement, the node provides increased protection against user
enumeration and password attacks.

No impact.
Operation
The Security.loginDelay attribute can be configured to randomized login
delay by setting the attribute value to -2.
For new installations, the default login delay is randomized login delay. The login
delay can be configured to one of the following login delay options by setting
Security.loginDelay:
— randomized
— incremental
— fixed
For more information on configuration of brute force protection, see Security for
O&M Node Access.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 167

At upgrade, the login delay remains unchanged. Changing the login delay to
randomized delay is recommended for enhanced brute force protection.
Interfaces
No impact.
Hardware
This feature enhancement is applicable to DU radio nodes.

To fully benefit from the change, ENM version 20.3 or later is required and release
independence function must be executed.
2.3.36 21.Q3: HWAC for Baseband 6621 and Baseband 6631
HWACs with the utility modules Throughput and ABW are introduced for
Baseband 6621 and Baseband 6631.

Release

The system improvement introduces the following Baseband HWACs with the
utility modules Throughput and ABW:
— For Baseband 6621
• FAK 101 0232: Initial HWAC Baseband 6621 Utility Module - CXC 401
2471
• FAK 101 0233: Initial HWAC Baseband 6621 Utility Module ABW - CXC
401 2472
— For Baseband 6631
• FAK 101 0234: Initial HWAC Baseband 6631 Utility Module - CXC 401
2471
168 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
• FAK 101 0235: Initial HWAC Baseband 6631 Utility Module ABW - CXC
401 2472
Note: The initial packages (IPs) enable full capacity for WCDMA in 21.Q3.
Refined enforcement in accordance with commercial agreements is
planned for later release. With the complete enforcement, expansion
packages (EPs) are needed for configurations where capacity provided
by the IP is not enough.

No impact.
Operation
When no initial package is installed on the node, the alarm Resource Allocation
Failure raises.
Alarm Name MO Additional Text

Resource Allocation NodeBLocalCell Unable to allocate
Failure baseband HW resources
due to insufficient
baseband HWAC for this
RAT.
Interfaces
No impact.
Hardware
This improvement applies to the following Baseband units:
— Baseband 6621
— Baseband 6631

No impact.
2.3.37 21.Q4: Extended Support of Optical Indication to Locate Physical Position

of Radio Unit
Possibility to invoke the new HereIAmIndication MO actions for user-

selected instance of FieldReplaceableUnit MO is introduced in the
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 169

EMGUI. The list of Radio Unit products with the "Here I Am" optical
indication function available is extended.

Access Type: GSM, LTE, NR, WCDMA,

With this function, the user is able easily and reliably locate the physical Radio
Unit that is graphically represented in the schematic graph provided by EMGUI.
In case of several active units, all of them are highlighted on the graph.
Activated function causes the maintenance LED to flash with a dedicated

pattern.
The "Here I Am" optical indication is made available for the majority of Radio
Unit types.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
The function supports all radio groups except group 1, 2, 5, 7a, Radio Dot and
third party products.
See Radio Capabilities for detailed product numbers.

No impact.
170 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions
2.3.38 21.Q4: Protection of Target Monitor Streaming Events
Security configuration for target monitor and protection of target monitor

streaming events ensures confidentiality and integrity protection of the
personal data in transit by using SSH tunneling.

Node Type: RNC
Access Type: WCDMA
With this enhancement the trace and error logs, which can contain sensitive and
personal data, can be protected in encrypted mode while streaming from target
monitor to a remote host using SSH tunneling. Streams are encrypted with
ciphers negotiated by SSH.
For more information about the target monitor protection, see Security for O&M
Node Access.
Benefits
With this enhancement the trace and error logs can be protected in encrypted
mode while streaming between target monitor and remote host using SSH
Tunneling. This functionality prevents possible privacy breaches or manipulation
of the data to occur over the transport network.

No impact on capacity.
The CPU load in security configuration is expected to increase 4% to 5% on O&M

CoreMP board compared with insecurity configuration when streaming from
target monitor to remote host.
Operation
command secmode -m allows the operator to change the target monitor mode
(secure, unsecure, and encrypted).
The attribute Security::targetMonitorPort indicates the current target

monitor setting.
Target monitor is configured using ts command. New ts ips command is

introduced to start trace streaming session in encrypted mode.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 171

The mon command is updated to support encrypted trace streaming using SSH
tunneling. When the target monitor is in encrypted mode, the mon command
executes the ts ips command to start the trace streaming sessions.
The monk command is updated to destroy SSH tunnel in encrypted mode.
After upgrade, default setting for the target monitor is secure mode, where
streaming is disabled. Operator should use the encrypted configuration to enable
target monitor streaming. For more information on how to change the target
monitor setting, see Security for O&M Node Access.
Prerequisite to enable encrypted target monitor mode is to have remote host

supporting SSH tunneling and host side LTTNG trace streaming configuration.
For LAA user, when the user authentication and authorization mode is moved
from Basic to Enhanced, the security configuration of target monitor is changed
to secure.
Interfaces
No impact.
Hardware
This improvement is applicable for EvoC 8300.

network elements:
— ENM uses AMOS to support secure Target Monitor.
— ENM version 21.3 or later is required.
2.3.39 21.Q4: Random Time Delay at Login
This system improvement enhances brute force protection mechanism. The

mechanism is enhanced with support for randomized login delay on a failed
user login attempt along with existing fixed and incremental delay
configurations. Random delay configuration protects the node from user
enumeration attacks.

172 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Released Functions

Node Type: RNC EvoC 8200
Access Type: WCDMA

With this enhancement, the node provides increased protection against user
enumeration and password attacks.

No impact.
Operation
The Security.loginDelay attribute can be configured to randomized login
delay by setting the attribute value to -2.
For new installations, the default login delay is randomized login delay. The login
delay can be configured to one of the following login delay options by setting
Security.loginDelay:
— randomized
— incremental
— fixed
For more information on configuration of brute force protection, see Security for
O&M Node Access.
At upgrade, the login delay remains unchanged. Changing the login delay to
randomized delay is recommended for enhanced brute force protection.
Interfaces
No impact.
Hardware
This feature enhancement is applicable to RNC EvoC 8200.

To fully benefit from the change, ENM version 20.3 or later is required and release
independence function must be executed.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 173

3 Planned Functions
3.1 New Features

Overview information about the new features that are planned to be released in
upcoming releases.
For more information about the features, see the feature description documents.
3.1.1 Support for AISG ADB
The feature introduces support for ADB subunit function and transmission
of certain subunit-related data.


The Support for AISG ADB feature adds function support for the ADB subunit
and enables the integration of the unit into the network. The ADB subunit allows
data collection related to antenna arrays.

No impact.
Operation
The feature introduces the AdbSubUnit MO Class to represent the ADB subunit.
The feature introduces the following attributes for the AntennaUnit MO Class:
— AntennaUnit.antennaDataProvenance
— AntennaUnit.antennaModelNumber
— AntennaUnit.antennaSerialNumber
174 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions
— AntennaUnit.numberOfLogicalArrays
— AntennaUnit.mechanicalAntennaBearing
— AntennaUnit.positionWithinSector
— AntennaUnit.sectorLabel
— AntennaNearUnit.antennaUnitRef
The attribute AntennaNearUnit.antennaUnitRef replaces the following

attributes:
— AntennaUnit.glsSubUnitRef
— AntennaUnit.asdSubUnitRef
— AntennaUnit.raeSubUnitRef
The feature introduces the ADB Failure alarm, and updates the Antenna
Communication Problem alarm and the Inconsistent Configuration alarm with
additional text.
The ADB allows data collection by performing the following actions:

— Setting the AntennaNearUnit.antennaUnitRef attribute to update
antenna-related data on AntennaUnit MO
— Executing the AdbSubUnit.getLogicalAntennaArraysData action to

collect logical antenna array-related data
— Running an AIGS device scan to collect ADB subunit-related data into an

XML file
Interfaces
No impact.
Hardware
The feature is only applicable to near Antenna Line Devices (ALDs) compatible
with AISG 3.0.
To use any ADB function, the ALD must include an ADB subunit.

ECT and EMGUI tools are updated to support AISG 3.0.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 175

3.2 Mandatory Impact at Upgrade

Overview information about the changes to the network performance and
operation that are planned to be released in upcoming releases. The changes
take effect automatically at upgrade.
3.2.1 NETCONF-Based Baseband Migration Support Using AMOS for WCDMA

and GSM
The feature is now extended with the support for WCDMA and GSM
migration of Baseband units.
Table 22
Access Type: WCDMA, GSM
Benefits
The enhancement brings the following benefits:
— The migration from a legacy Baseband unit to a new Baseband is now
supported for WCDMA and GSM, in addition to LTE and NR.
— The Baseband migration is supported to the following Baseband unit types:

6621/6631. The radio technology support at migration depends on the
Baseband types involved in the migration, see Migrate Baseband Unit Using
NETCONF-Based Procedure and DU and Baseband Configurations and
Capacity.
— The migration is also supported for a node running mixed mode RAT
combinations (NR, LTE, WCDMA, GSM).
— The support for Instantaneous Licensing at migration is added.

No impact.
176 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions
Operation
No impact.
Interfaces
No impact.
Hardware

The required ENM version is 21.3.
3.2.2 Cold Baseband Restart Improvements
With this feature enhancement, the number of shared unit restarts caused
by a Baseband restart due to upgrade or a cold manual restart is reduced.
When upgrading to an older shared unit software, or when performing a
manual cold restart when the shared unit running software is newer, the
number of restarts is zero. A shared unit is a Field Replaceable Unit (FRU)
that is connected to more than one external MEs.
Feature Name: Mixed Mode Radio Mixed Mode Baseband R

WCDMA
Feature Identity: FAJ 121 1553 FAJ 121 4776
Value Package Name: Mixed Mode Radio Node WCDMA Base Package
WCDMA
Value Package Identity: FAJ 801 0337 FAJ 801 0359
Node Type: Baseband Radio Node Baseband Radio Node
Access Type: NR, LTE, WCDMA, GSM NR, LTE, WCDMA, GSM

The cold Baseband restart improvement is applicable in the following cases:
— Integrating a Baseband unit with an FRU that is already integrated with
another Baseband unit.
— Upgrading an ME with an older software version that includes software for

shared FRU.
— Performing a manual cold restart of a Baseband unit.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 177

The enhancement has the following benefits:

— The time to enable a cell is reduced on the ME, resulting in less time with
traffic loss.
— The external MEs do not experience traffic loss, since no shared FRU restart
occurs.
— The external MEs take reduced time to enable a cell when a shared FRU
restarts.
The benefits are more significant when the shared FRU is an AAS-capable radio
unit, because this type has longer startup time.

The feature enhancement improves the cell availability KPI.
Operation
No impact.
Interfaces
No impact.
Hardware

No impact.
3.2.3 Monitoring of SyncE as Assisting Reference Based on Network Information
This feature enhancement introduces monitoring of SyncE as an assisting

reference based on network information to provide a more accurate
calculation of the time error while in assisted mode.

178 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions

The feature enhancement provides the following benefits:
— The calculation of the time error is more accurate while in assisted mode.
Thus the interference situations can be prevented when the node tracks a
SyncE input whose quality is poor.
— Operators can remap the SyncE reference to a better QL for assisting when
the received QL is not worse than PRC and the actual QL is better than the
received QL.

No impact.
Operation
The enhancement introduces the following attributes:
— AssistingReference.assistingQLFrom
— AssistingReference.remappedQualityLevel
— SyncEthInput.adminCascadedEec
— SyncEthInput.adminCascadedEnhancedEec
— SyncEthInput.useNumberEecFrom
The default value for AssistingReference.assistingQLFrom attribute is

RECEIVED_QL.
When the received QL is not wrose than PRC and the actual QL is better than the
received QL, operators can remap the received QL to a better QL. This can be
achieved by setting AssistingReference.assistingQLFrom attribute to
REMAPPED_QL and AssistingReference.remappedQualityLevel attribute to a
better QL.
Interfaces
No impact.
Hardware
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 179


ENM 21.16 or later is required for this feature enhancement.
3.2.4 Handling Fault Cases with Unknown Cause
This system improvement introduces the FRU General Problem alarm.

W21 Release
Access Type: WCDMA, LTE, NR, GSM

This system improvement introduces the FRU General Problem alarm to handle
fault cases where the cause cannot be determined. The cause of the fault can be
any of the following:
— Software error
— Undetected hardware fault
— Configuration fault
Separating the fault cases helps to avoid incorrect alarm handling.

No impact.
Operation
The system improvement introduces the FRU General Problem alarm. The FRU
General Problem alarm is raised on the FieldReplaceableUnit MO.
Hardware
Interfaces
No impact.
180 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions

No impact.
3.2.5 Other Changed Behaviors in DU Radio Node: More Auto-Created MOs in

RruDeviceGroup MO
More MOs in RruDeviceGroup MO are automatically created.

Access Type: WCDMA

The number of the following MOs are increased, which are automatically created
under the RruDeviceGroup MO:
— TpaDevice and AiDevice MOs are increased from 4 to 6
— DpclDevice and TrDevice MOs are increased from 24 to 36
For unused device MOs, availabilityStatus is automatically set to

NOT_INSTALLED and operationalState to DISABLED.

No impact.
Operation
No impact.
Interfaces
No impact.
Hardware
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 181


No impact.
3.2.6 Multi Sector Per Radio Enhancement: Support of Three Sectors Per Radio
The Multi-Sector Per Radio feature is enhanced to support three sectors on

a 6TX/6RX radio unit or a radio group of two 6TX/6RX radio units.
Feature Name: Multi-Sector Per Radio

Access Type: WCDMA

With the enhancement, the following configurations are supported:
— Three sectors in one 6TX/6RX radio, for example Radio 6626. Each sector
has one or more sector carriers with two antenna branches.
— Three sectors in a radio group of two 6TX/6RX radios, for example Radio
6626 + Radio 6626. Each sector has one or more sector carriers with four
antenna branches.
The enhancement brings the following benefits:

— Improved coverage by enabling the configuration of multiple sectors for one
radio unit.
— Decreased power consumption as fewer radio units are required to provide

an improved coverage.
— Decreased site lease costs as fewer radio units need to be installed.
— Easier site installation and hardware transportation.
For more information, see Multi-Sector Per Radio.

No impact.
Operation
No impact.
182 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions
Interfaces
No impact.
Hardware

No impact.
3.2.7 RETv3 Subunit Functionality Support
This feature enhancement improves the use of AISG 3.0 devices and RET
functionality.

Access Type: WCDMA
This feature enhancement enables the collection of data related to physical

antenna units and antenna arrays.
Benefits
This feature enhancement provides the following benefits:
— Improved AISG 3.0 support for RET subunit.
— Up to 12 RET subunits are supported on one Antenna Line Device.

No impact.
Operation
This feature enhancement introduces the value 64 that represents SALD for the
attribute AntennaNearUnit.iuantDeviceType for AISG 3.0 devices.
ECT and EMGUI are updated to support AISG 3.0 improvement.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 183

Interfaces
No impact.
Hardware
Near antenna line devices that are compatible with AISG 3.0 are required.

No impact.
3.2.8 Time Discontinuity Handling
With this system improvement, the GPS week number can be properly
calculated after the GNSS receiver week number rollover which is performed
1024 weeks after firmware build date.

Release
Value Package Name: WCDMA Base package

This system improvement ensures that the correct GPS week number is used for
synchronization. Therefore, no performance or traffic degradations are observed
after the GNSS receiver week number rollover.

No impact.
Operation
No impact.
Interfaces
No impact.
184 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions
Hardware

No impact.
3.3 Optional Impact at Upgrade

Overview information about changes to the network performance and operation
that are planned to be released in upcoming releases. The changes take effect
only when manually activated.
3.3.1 Periodic Trigger for Start of LTE Measurements
This enhancement introduces new periodic trigger for LTE Measurements

and the controllability for the common LTE Measurements triggers.
Feature Name: PS Handover to LTE based on Measurements in LTE

Measurements in LTE
FAJ 121 4277
Access Type: WCDMA
Node Type: RNC

An operator configurable periodic timer is introduced to determine how long after
the last unsuccessful LTE Measurements a new periodic trigger starts. The timer
is started in the following cases:
— After the guard timer UeMeasControl::eutranMeasGuardTime expiration
— After good connection quality indication (for example, event 2f or event

6b) reception if previously LTE Measurements has been stopped by bad
connection quality indication (for example, event 2d or event 6d)
— After downswitch to FACH or URA causing LTE Measurements termination
— After unsuccessful PS Handover procedure
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 185

— Release of CS signaling connection when PS session is active in case of the

RAB combination of Speech + 0/0
If the timer time-out has occurred on the CELL_DCH connection state, then LTE
Measurements starts (if the conditions to start are met).
If the timer time-out has occurred on CELL_FACH or CELL_URA connection state,

then LTE Measurements starts after the first upswitch to CELL_DCH (if the
conditions to start are met).
The timer is cancelled when any other trigger for start of LTE Measurements
occurred or a CS call is established.
The enhancement provides the following benefits:

— Less loaded WCDMA network due to users being moved to LTE
— Better user experience (LTE offers high-speed data transfers)
The enhancement also introduces new structure attribute on IurLink and

UeMeasControl which contain switches for triggers to start LTE Measurements.
New switches allows Operator for a flexible controllability of LTE Measurements.

For information how to measure success rate, see LTE Measurements.
Enabling the new trigger can increase the number of compressed mode starts.
The following PDF counters are introduced to observe LTE Measurements starts
and evaluations for each trigger:
— UtranCell::pmLteMeasTriggCsRabRelease
— UtranCell::pmLteMeasTriggPsHoFromLte
— UtranCell::pmLteMeasTriggBestCellChange
— UtranCell::pmLteMeasTriggEmergencyTimerExp
— UtranCell::pmLteMeasTriggLteOffloadTimerExp
— UtranCell::pmLteMeasTriggEutraCapReception
— UtranCell::pmLteMeasTriggPeriodicTimerExp
The following counters are affected by the enhancement:

— UtranCell::pmCmTriggLteMeas
— IurLink::pmCmTriggLteMeas
— UtranCell::pmLteMeasCmStart
186 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions
— IurLink::pmLteMeasCmStart
— UtranCell::pmLteMeasReportEval
— IurLink::pmLteMeasReportEval
— UtranCell::pmLteMeasStop
— IurLink::pmLteMeasStop
— UtranCell::pmLteMeasTimeout
— IurLink::pmLteMeasTimeout
— UtranCell::pmNoRwrEutraBasedMeasReport3c
— IurLink::pmNoRwrEutraBasedMeasReport3c
— UtranCell::pmOutPsHoLteMeasReq
— IurLink::pmOutPsHoLteMeasReq
Operation
The UeMeasControl::eutranMeasPeriodicTime parameter with the default
value of 20s is introduced to determine how long after the last unsuccessful LTE
Measurements a new periodic trigger starts.
Table 23 shows new structure attribute that allows to switch ON and OFF specific
LTE Measurement triggers:
Table 23 Introduced Structures

Structure Trigger Name Description
UeMeasControl::lteMe eutranMeasPeriodicTr Enables periodic trigger
asTriggers iggEnabled for start of LTE
Measurements on RNC.
eutraCapReceptionTri Enables UE E-UTRA
ggEnabled Capability reception
trigger for start of LTE
bestCellChangeTriggE Enables best cell change
nabled trigger for start of LTE
csRabReleasePsActive Enables release of CS
TriggEnabled signaling connection
when PS session is
active (excluding the
RAB combination of
Speech + 0/0) trigger for
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 187

Structure Trigger Name Description

start of LTE
pshoFromLteTriggEnab Enables release of CS
led signaling connection due
to LAU after Packet
Switch Handover from
LTE trigger for start of
LTE Measurements on
RNC.
IurLink::lteMeasTrig eutranMeasPeriodicTr Enables periodic trigger
gers iggEnabled for start of LTE
Measurements on
IurLink.
eutraCapReceptionTri Enables UE E-UTRA
ggEnabled Capability reception
trigger for start of LTE
Measurements on
IurLink.
bestCellChangeTriggE Enables best cell change
nabled trigger for start of LTE
Measurements on
IurLink.
csRabReleasePsActive Enables release of CS
TriggEnabled signaling connection
when PS session is
active (excluding the
RAB combination of
Speech + 0/0) trigger for
start of LTE
Measurements on
IurLink.
pshoFromLteTriggEnabl Enables release of CS
ed signaling connection due
to LAU after Packet
Switch Handover from
LTE trigger for start of
LTE Measurements on
IurLink.
Interfaces
No impact.
Hardware
188 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Planned Functions

network elements:
— UE
Release 8 and support E-UTRAN Measurement
— LTE RAN
Coverage-Triggered WCDMA IRAT Handover (FAJ 121 0897)
Coverage-Triggered WCDMA Session Continuity (FAJ 121 0493)
3.3.2 PS and CS Traffic Separation and Multihomed SCTP Association

Configuration
The improvement enables the operator to increase the number of SCTP

Front Ends on RNC EvoC 8300. It allows CS and PS control plane traffic
separation while keeping all redundancy options.

Node Type: RNC
Access Type: WCDMA

This improvement introduces the ability to create four SCTP Front Ends on RNC
EvoC 8300 similar to the capability of EvoC 8200/RNC. With this improvement,
the operator can separate signaling at the SCTP Front End level. For example, it
is possible to configure separate SCTP Front End to handle exclusively only the
CS or the PS domain signals.
A new type of Software Allocation, the EPB_BLADE_B role is introduced, which

can be used to configure additional SCTP Front Ends. This Software Allocation
can be used instead of the existing EPB_BLADE_A role on operating EPB2 blade
or it can be installed on a newly added EPB2 blade.
The EPB_BLADE_B Software Allocation can be selected during the board adding
procedure in the Hardware Configuration Tool through the Element Manager
Application.
For more information, see the following documents:
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 189

— Remove a BoardEvoC 8300 (steps needed for removing existing

EPB_BLADE_A Software Allocation from operating EPB2 blade)
— Add EPB2 EvoC8300 (steps needed for introducing newly created

EPB_BLADE_B Software Allocation for chosen EPB2 blade)

The introduced EPB_BLADE_B Software Allocation provides a half of the traffic
handling capacity of the previously used EPB_BLADE_A Software Allocation as
one of the two EPB board processors is solely dedicated for the newly created
SCTP Front End. Therefore, it is recommended to use the Utilize C1 Blades for
Traffic feature to mitigate capacity reduction.
Operation
No impact.
Interfaces
The improvement allows configuration of two additional SCTP Front Ends, up to
a maximum number of four.
Hardware

No impact.
190 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters
4 Parameters
This section provides an overview of the parameters introduced in the

different releases.
4.1 RNC RN Parameters 20.Q2
Table 24 RNC RN Parameters 20.Q2

New, Removed, or Parameter name MO Class Comments
Changed
Changed garbledSpeechCor RncFunction Description
rectionEnabled change.
Changed spareA RncFunction Release of index
0.
Index 4
description
change.
Changed spareB RncFunction Description
change.
Release of index
2.
Changed t315 Rrc Description and
default value
change.
Changed localSccpApRef Ranap Description
change.
Changed poolRedundancy IubLink Description
change.
Changed poolRedundancy UtranCell Description
change.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 191

4.2 RNC TN Parameters 20.Q2
Table 25 RNC TN Parameters 20.Q2

Changed
Changed icmpRedirect Ip Description
change.
Changed RealTimeSecLog Class description
update
New targetMonitorPort Security New attribute.
Changed targetMonitorPort Security Description and
Active default value
change.
4.3 DU RN Parameters 20.Q2
Table 26 DU RN Parameters 20.Q2

New, Removed, or Parameter Name MO Class Comments
Changed
Changed nbirAlgorithm Carrier Description
change.
New nbirAutoCurrentAl Carrier
gorithm

Changed
New prefMobilityToLte EutraNetwork
CsfbEnabled
New callReestDlNasSig Rrc
nEnabled
New callReestRabEstE Rrc
nabled
New prefMobilityToLte UtranCell
CsfbHandling
192 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
Changed redirectionOrder EutranFreqRelati Description
on update.
Changed spareA Rncfunction Index [4] released
New MO Class UeMobilityProfile

Changed
Changed icmpRedirect Ip Default value
change.
Changed nodeIpv6Interfac Ip Dependencies
eName change.
Changed ipv6Addresses EthernetLink Description
update.
New pmIpIfStatsInAdd EthernetLink
rErrors
New pmIpIfStatsInDis EthernetLink
cards
New pmIpIfStatsInHdr EthernetLink
Errors
New pmIpIfStatsInOct EthernetLink
ets
New pmIpIfStatsInRec EthernetLink
eives
New pmIpIfStatsInUnk EthernetLink
nownProtos
New pmIpIfStatsOutDi EthernetLink
scards
New pmIpIfStatsOutFr EthernetLink
agCreates
New pmIpIfStatsOutO EthernetLink
ctets
New pmIpIfStatsOutTr EthernetLink
ansmits
New pmIpIfStatsReas EthernetLink
mFails
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 193


Changed
New pmIpIfStatsReas EthernetLink
mReqds
New active Ipv4StaticRoute

Changed
Changed desiredMinTxInter BfdProfile Range extended,
val description
update.
Changed requiredMinRxInt BfdProfile Range extended,
erval description
update.
Changed ClusterMember Class deprecated
Changed NodeClusterCom Class deprecated
munication
Changed administrativeSta ClusterMember Marked as
te deprecated
Changed ClusterMemberId ClusterMember Marked as
deprecated
Changed ipAddress ClusterMember Marked as
deprecated
Changed memberIdentity ClusterMember Marked as
deprecated
Changed operationalState ClusterMember Marked as
deprecated
Changed userLabel ClusterMember Marked as
deprecated
Changed moOwner M3uAssociation Marked as
deprecated
Changed moOwner Mtp3bAp Marked as
deprecated
Changed moOwner Mtp3bSpAnsi Marked as
deprecated
Changed moOwner Mtp3bSpChina Marked as
deprecated
194 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
Changed moOwner Mtp3bSpItu Marked as
deprecated
Changed moOwner Mtp3bSpTtc Marked as
deprecated
Changed moOwner Mtp3bSr Marked as
deprecated
Changed moOwner Mtp3bSrs Marked as
deprecated
Changed administrativeSta NodeClusterCom Marked as
te munication deprecated
Changed clusterIdentity NodeClusterCom Marked as
munication deprecated
Changed dscp NodeClusterCom Marked as
Changed firstMainServerAd NodeClusterCom Marked as
dresses munication deprecated
Changed ipAccessList NodeClusterCom Marked as
Changed memberIdentity NodeClusterCom Marked as
Changed NodeClusterCom NodeClusterCom Marked as
municationId munication deprecated
Changed reservedBy NodeClusterCom Marked as
Changed secondMainServe NodeClusterCom Marked as
rAddresses munication deprecated
Changed userLabel NodeClusterCom Marked as
Changed moOwner SccpApLocal Marked as
deprecated
Changed moOwner SccpApRemote Marked as
deprecated
Changed moOwner SccpScrc Marked as
deprecated
Changed moOwner SccpSp Marked as
deprecated
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 195


Changed
Changed nbirAlgorithm Carrier Default value
change

Changed
Changed ExternalUtranCell Description
change
Changed blockRwrEutraTi Handover Description
me change
New noEutraSubExpec Handover
tedReturnTime
New spare IuBcLink Index [0] is
currently in use
Not supported in
this release"
Changed resetResourceMsg Ranap Deprecated
Interval
Changed RemoteUtranCell Class deprecated
Changed agpsEnabled RemoteUtranCell Deprecated
Changed antennaPosition RemoteUtranCell Deprecated
Changed cId RemoteUtranCell Deprecated
Changed creationTime RemoteUtranCell Deprecated
Changed individualOffset RemoteUtranCell Deprecated
Changed maxTxPowerUl RemoteUtranCell Deprecated
Changed primaryCpichPow RemoteUtranCell Deprecated
er
Changed primaryScramblin RemoteUtranCell Deprecated
gCode
Changed qQualMin RemoteUtranCell Deprecated
196 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
Changed qRxLevMin RemoteUtranCell Deprecated
Changed RemoteUtranCellI RemoteUtranCell Deprecated
d
Changed reportingRange1a RemoteUtranCell Deprecated
Changed reportingRange1b RemoteUtranCell Deprecated
Changed reservedBy RemoteUtranCell Deprecated
Changed timeToTrigger1a RemoteUtranCell Deprecated
Changed timeToTrigger1b RemoteUtranCell Deprecated
Changed transmissionSche RemoteUtranCell Deprecated
me
Changed uarfcnDl RemoteUtranCell Deprecated
Changed uarfcnUl RemoteUtranCell Deprecated
Changed userLabel RemoteUtranCell Deprecated
Changed RncClusterMembe Class deprecated
r
Changed ipAccessHostPool RncClusterMembe Deprecated
Ref r
Changed redundancySwitc RncClusterMembe Deprecated
hoverWaitTime r
Changed RncClusterMembe RncClusterMembe Deprecated
rId r
Changed eutranFilterCoeffi UeMeasControl Description
cient3c change
Changed eutranHysteresis3 UeMeasControl Description
cRsrp change
Changed eutranHysteresis3 UeMeasControl Description
cRsrq change
Changed eutranMeasGuard UeMeasControl Description
Time change
Changed eutranMeasQuant UeMeasControl Description
ity3c change
Changed eutranThresh3cRs UeMeasControl Description
rp change
Changed eutranThresh3cRs UeMeasControl Description
rq change
Changed timeToTrigger3c UeMeasControl Description
change
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 197


Changed
New lteMeasCmDchPr UeMeasControl
olongTimer

Changed
Changed noEutraSubExpec Handover Description
tedReturnTime changed
Changed sourceIpAddressV IuBcLink Description
alidation changed
Changed selHoSupImplicitL RncFunction Description
teFiltering changed
Changed lteMeasCmDchPr UeMeasControl Description
olongTimer changed
Default value
change
New iurCellRelTrunCfg UtranCell Description
changed

Changed
Changed RealTimeSecLog Class description
changed
198 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
New GeoRedundancy
New GeoRedundancyI GeoRedundancy
d
Changed actionResult GeoRedundancy
New isGeoEnabled GeoRedundancy
New sourceConfigurati GeoRedundancy
onFilePath
New currentGeoConfig GeoRedundancy
uration
New switchedOverDrift GeoRedundancy
Rncs
New functionState GeoRedundancy
New sourceDriftRncsC GeoRedundancy
onfigurationFileP
ath
Changed resetResourceMsg Ranap Marked as
Interval Obsolete.
Changed RemoteUtranCell MO class marked
as obsolete.
Changed agpsEnabled RemoteUtranCell Marked as
Obsolete.
Changed antennaPosition RemoteUtranCell Marked as
Obsolete.
Changed cId RemoteUtranCell Marked as
Obsolete.
Changed creationTime RemoteUtranCell Marked as
Obsolete.
Changed individualOffset RemoteUtranCell Marked as
Obsolete.
Changed maxTxPowerUl RemoteUtranCell Marked as
Obsolete.
Changed primaryCpichPow RemoteUtranCell Marked as
er Obsolete.
Changed primaryScramblin RemoteUtranCell Marked as
gCode Obsolete.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 199


Changed
Changed qQualMin RemoteUtranCell Marked as
Obsolete.
Changed qRxLevMin RemoteUtranCell Marked as
Obsolete.
Changed RemoteUtranCellI RemoteUtranCell Marked as
d Obsolete.
Changed reportingRange1a RemoteUtranCell Marked as
Obsolete.
Changed reportingRange1b RemoteUtranCell Marked as
Obsolete.
Changed reservedBy RemoteUtranCell Marked as
Obsolete.
Changed timeToTrigger1a RemoteUtranCell Marked as
Obsolete.
Changed timeToTrigger1b RemoteUtranCell Marked as
Obsolete.
Changed transmissionSche RemoteUtranCell Marked as
me Obsolete.
Changed uarfcnDl RemoteUtranCell Marked as
Obsolete.
Changed uarfcnUl RemoteUtranCell Marked as
Obsolete.
Changed userLabel RemoteUtranCell Marked as
Obsolete.
Changed RncClusterMembe Marked as
r Obsolete.
Changed ipAccessHostPool RncClusterMembe Marked as
Ref r Obsolete.
Changed redundancySwitc RncClusterMembe Marked as
hoverWaitTime r Obsolete.
Changed RncClusterMembe RncClusterMembe Marked as
rId r Obsolete.
Changed RncFunction MO class
description
changed.
Changed spareB RncFunction Index [3]
description
changed.
Changed poolRedundancy IubLink Description
changed.
200 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
Changed rbsId IubLink Description
changed.
Changed eutranFrequency UeMobilityProfile Description
ConfList changed.
Changed useForMobilityTo UeMobilityProfile Description
Lte changed.
Changed poolRedundancy UtranCell Description
changed.
New additionalPlmnId UtranNetwork
entities
Changed UtranRelation MO class
description
changed.
Changed utranCellRef UtranRelation Description
changed.
Changed TimDevice Class description
updated with FM
events, not
supported in this
release.
New longAlignmentDe TimDevice Not supported in
vicesThresh this release.
New longAlignmentTi TimDevice Not supported in
meThresh this release.

Changed
Changed ClusterMember MO class marked
as Obsolete.
Changed administrativeSta ClusterMember Marked as
te Obsolete.
Changed ClusterMemberId ClusterMember Marked as
Obsolete.
Changed ipAddress ClusterMember Marked as
Obsolete.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 201


Changed
Changed memberIdentity ClusterMember Marked as
Obsolete.
Changed operationalState ClusterMember Marked as
Obsolete.
Changed userLabel ClusterMember Marked as
Obsolete.
Changed M3uAssociation MO class
description
changed.
Changed moOwner M3uAssociation Marked as
Obsolete.
Changed sctpAssociationRe M3uAssociation Description
f changed.
Changed sctpId M3uAssociation Description
changed.
Changed Mtp3bAp MO class
description
changed.
Changed moOwner Mtp3bAp Marked as
Obsolete.
Changed Mtp3bSpAnsi MO class
description
changed.
Changed moOwner Mtp3bSpAnsi Marked as
Obsolete.
Changed Mtp3bSpChina MO class
description
changed.
Changed moOwner Mtp3bSpChina Marked as
Obsolete.
Changed Mtp3bSpItu MO class
description
changed.
Changed moOwner Mtp3bSpItu Marked as
Obsolete.
Changed Mtp3bSpTtc MO class
description
changed.
Changed moOwner Mtp3bSpTtc Marked as
Obsolete.
202 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
Changed Mtp3bSr MO class
description
changed.
Changed moOwner Mtp3bSr Marked as
Obsolete.
Changed usageState Mtp3bSr Description
changed.
Changed Mtp3bSrs MO class
description
changed.
Changed moOwner Mtp3bSrs Marked as
Obsolete.
Changed NodeClusterCom MO class marked
munication as Obsolete.
Changed administrativeSta NodeClusterCom Marked as
te munication Obsolete.
Changed clusterIdentity NodeClusterCom Marked as
munication Obsolete.
Changed dscp NodeClusterCom Marked as
Changed firstMainServerAd NodeClusterCom Marked as
dresses munication Obsolete.
Changed ipAccessList NodeClusterCom Marked as
Changed memberIdentity NodeClusterCom Marked as
Changed NodeClusterCom NodeClusterCom Marked as
municationId munication Obsolete.
Changed reservedBy NodeClusterCom Marked as
Changed secondMainServe NodeClusterCom Marked as
rAddresses munication Obsolete.
Changed userLabel NodeClusterCom Marked as
Changed SccpApLocal MO class
description
changed.
Changed moOwner SccpApLocal Marked as
Obsolete.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 203


Changed
Changed SccpApRemote MO class
description
changed.
Changed moOwner SccpApRemote Marked as
Obsolete.
Changed SccpSp MO class
description
changed.
Changed moOwner SccpSp Marked as
Obsolete.
New passwordAgingTh Security
reshold

Changed
Changed AiDevice MO class
description
changed.
Changed DpclDevice MO class
description
changed.
Changed TpaDevice MO class
description
changed.
Changed TrDevice MO class
description
changed.
204 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Parameters

Changed
Changed objectAConnect AntFeederCable Update the
or description due to
decreasing the
device number for
MR9002 Radio
6626 on WCDMA
G1.
4.15 DU TN Parameters 21.Q3

Changed
Changed loginDelay Security The change is
from CPP MOM,
Functional
change,
MR9204-1 SP1:
Random time
delay at login for
RBS, Evo8200
and MGW.

Changed
New eutranMeasPeri UeMeasControl
odicTime
New lteMeasTrigger UeMeasControl
s
New lteMeasTrigger IurLink
s
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 205


Changed
Changed spare RncFunction Index[2] is
temporarily
reserved for FAJ
121 4747 A-BLER
for Voice
enhancement
prototype testing.
Do not change
value without
request or
permission from
Ericsson
Personnel.
Changed spareB RncFunction Index [7], [8], [9]
reserved
Changed TimDevice "Not supported in
this release"
removed from
class description
for FM events
Changed longAlignmentD TimDevice "Not supported in
evicesThresh this release"
removed
Changed longAlignmentT TimDevice "Not supported in
imeThresh this release"
removed

Changed
Changed dscp Ip Description
changed
Changed loginDelay Security Description, range
and default value
changed
Changed targetMonitorP Security Description
ort changed
Changed ecdReporting MediumAccessUn Description
it changed
206 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Counters
5 Counters
This section provides an overview of the counters introduced in the different

releases.
5.1 RNC Counters 20.Q2

Changed
New pmNoGsReceived IurLink New counter.
Cre
New pmNoGsSuccessC IurLink New counter.
re
New pmNoGsTriggered IurLink New counter.
NwInitCre
Changed pmNoCorrectedG RncFunction Description
arbledCallNbUl change.
Changed pmNoCorrectedG RncFunction Description
arbledCallWbUl change.
Changed pmNoGarbledCall RncFunction Description
NbUl change.
Changed pmNoGarbledCall RncFunction Description
WbUl change.
Changed pmCallReestAttPs UtranCell Description
change.
Changed pmCallReestReqP UtranCell Description
s change.
Changed pmCallReestSucc UtranCell Description
Ps change.
New pmNoCorrectedG UtranCell New counter.
arbledSpeechNb
New pmNoCorrectedG UtranCell New counter.
arbledSpeechWb
New pmNoDetectedGa UtranCell New counter.
rbledSpeechNb
New pmNoDetectedGa UtranCell New counter.
rbledSpeechWb
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 207


Changed
New pmNoGsReceived UtranCell New counter.
Cre
New pmNoGsSuccessC UtranCell New counter.
re
New pmNoGsTriggered UtranCell New counter.
NwInitCre
New pmOutPsHoLteM IurLink New counter.
easAtt
easReq
easReqFail
easRetNotPhyCh
Fail
easSucc
easUeRej
New pmOutPsHoLteM UtranCell New counter.
easAtt
easAtt
easReq
easReqFail
easAtt
easReqFailNoRes
ource
easRetNotPhyCh
Fail
easRetPhyChFail
easSucc
208 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Counters

Changed
easUeRej
Table 42 RNC Counters 20.Q3

New, Changed, or Counter Name MO Class Comment
Removed
Changed pmBwErrBlocks Aal0TpVccTp Description
update
Changed pmBwLostCells Aal0TpVccTp Description
update
Changed pmBwMissinsCell Aal0TpVccTp Description
s update
Changed pmFwErrBlocks Aal0TpVccTp Description
update
Changed pmFwLostCells Aal0TpVccTp Description
update
Changed pmFwMissinsCells Aal0TpVccTp Description
update
Changed pmLostBrCells Aal0TpVccTp Description
update
Changed pmLostFpmCells Aal0TpVccTp Description
update
update
update
s update
update
update
update
update
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 209


Removed
update
update
update
s update
update
update
update
update
update
Changed pmBwErrBlocks Aal2PathVccTp Description
update
Changed pmBwLostCells Aal2PathVccTp Description
update
Changed pmBwMissinsCell Aal2PathVccTp Description
s update
Changed pmDiscardedEgre Aal2PathVccTp Description
ssCpsPackets update
Changed pmEgressCpsPack Aal2PathVccTp Description
ets update
Changed pmFwErrBlocks Aal2PathVccTp Description
update
Changed pmFwLostCells Aal2PathVccTp Description
update
Changed pmFwMissinsCells Aal2PathVccTp Description
update
Changed pmIngressCpsPac Aal2PathVccTp Description
kets update
Changed pmLostBrCells Aal2PathVccTp Description
update
Changed pmLostFpmCells Aal2PathVccTp Description
update
210 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Counters

Removed
update
update
s update
update
update
update
update
update
Changed pmCallReestReqP UtranCell Condition update
s
Changed pmMatchUeProfil UtranCell Condition update
e
Changed pmNoPagingAtte UtranCell Condition update
mptUtranRejected
Changed pmNoTimesRlDel UtranCell Condition update
FrActSet
New pmBlockDedicPrio UtranCell
EutraUeProfile
New pmCallReestAtRa UtranCell
bEstAttCs
bEstAttPs
bEstReqCs
bEstReqPs
bEstSuccCs
bEstSuccPs
New pmCallReestFrom UtranCell
SrbAttCs
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 211


Removed
SrbAttPs
SrbReqCs
SrbReqPs
SrbSuccCs
SrbSuccPs
New pmNoRetransNas UtranCell
ReestSuccCs
New pmNoRetransNas UtranCell
ReestSuccPs
New pmRedirectAttem UtranCell
ptsEutraUeProfile
New pmTriggDedicPrio UtranCell
EutraUeProfile
New pmRefusedReque LoadControl
stsThread
5.3 DU Counters 20.Q4
Table 43 DU Counters 20.Q4

New, Changed or Counter Name MO Class Comment
Removed
New pmNbirRunningAl Carrier New observability
gorithm for NBIR
algorithm history
and suggestion.
New pmNbirSuggestAl Carrier New observability
gorithm for NBIR
algorithm history
and suggestion.
212 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Counters

Removed
Changed pmInCnhhoAttCs UtranCell Description
Speech change
New pmNoCallRetent Handover New counter
ionCandidates
ionRLReleaseTr
iggered
ionRLReleaseSu
ccess
New pmNoCallRetent UtranCell New counter
ionCallReestRe
q
ionCallReestAt
t
ionCallReestSu
cc
New pmLteMeasCmDch UtranCell
Prolong
New pmLteMeasCmDch UtranCell
ProlongWithE3c
New pmSamplesAnrIa UtranCell Description
fRelation changed
New pmSumAnrIafRel UtranCell Description
ation changed
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 213


Removed
New pmOutPsHoEutra IurLink
AttUeProfile
ReqFailUeProfi
le
ReqUeProfile
StopUeProfile
SuccUeProfile
New pmRedirectAtte IurLink
mptsEutraUePro
file
New pmNoIurCellRel UtranCell
TruncFailure
New pmOutPsHoEutra UtranCell
AttUeProfile
ReqFailUeProfi
le
ReqUeProfile
StopUeProfile
SuccUeProfile
214 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Counters

Removed
New pmLmCellMcThre RncModule
adLoad
New pmLmUeMcThread RncModule
Load
New pmSamplesLmCel RncModule
lMcThreadLoad
New pmSamplesLmUeM RncModule
cThreadLoad
New pmSumLmCellMcT RncModule
hreadLoad
New pmSumLmUeMcThr RncModule
eadLoad
New pmSumSqrLmCell RncModule
McThreadLoad
New pmSumSqrLmUeMc RncModule
ThreadLoad
Changed pmDownSwitchSu UtranCell Description
ccess changed.
Changed pmMeasuredLoad RncModule Description
changed.
Changed pmSumMeasuredL RncModule Description
oad changed.

Removed
New pmLteMeasTriggB UtranCell
estCellChange
New pmLteMeasTriggC UtranCell
sRabRelease
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 215


Removed
New pmLteMeasTriggE UtranCell
mergencyTimerEx
p
New pmLteMeasTriggE UtranCell
utraCapReception
New pmLteMeasTriggL UtranCell
teOffloadTimerEx
p
New pmLteMeasTriggP UtranCell
eriodicTimerExp
New pmLteMeasTriggP UtranCell
sHoFromLte
Changed pmMeasuredLoad RncModule Description
changed
Changed pmSumMeasuredL RncModule Description
oad changed
216 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Alarms
6 Alarms
This section provides an overview of the alarms introduced in the different

releases.
6.1 RNC Alarms 20.Q2
Table 48 RNC Alarms 20.Q2

New, Removed or Specific Problem MO Class Comment
Changed
New Inactive Node Security AdditionalInfo:
User account Present.
AdditionalText:
Present.
EvoC8300 only.
6.2 RNC Alarms 21.Q2
Table 49 RNC Alarms 21.Q2

Changed
New InconsistentConfi GeoRedundancy
guration
Removed Cluster Member ClusterMember Change related to
Unavailable removal of RNC in
Pool.
Removed Member Identity NodeClusterCom Change related to
Not Unique munication removal of RNC in
Pool.
Removed SS7 Cluster Mtp3bSpAnsi Change related to
Configuration removal of RNC in
Duplicated Pool.
Removed SS7 Cluster Mtp3bSpChina Change related to
Duplicated Pool.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 217


Changed
Removed SS7 Cluster Mtp3bSpItu Change related to
Duplicated Pool.
Removed SS7 Cluster Mtp3bSpTtc Change related to
Duplicated Pool.
Removed SS7 Cluster Mtp3bSpAnsi Change related to
Inconsistent Pool.
Removed SS7 Cluster Mtp3bSpChina Change related to
Inconsistent Pool.
Removed SS7 Cluster Mtp3bSpItu Change related to
Inconsistent Pool.
Removed SS7 Cluster Mtp3bSpTtc Change related to
Inconsistent Pool.
218 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

KPIs
7 KPIs
This section provides an overview of the KPIs introduced in the different

releases.
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 219

8 GPEH
This section provides an overview of the Events introduced in the different

releases.
8.1 GPEH 20.Q2
Table 50 Events 20.Q2

Change Type Name Comments
Updated Internal Event INTERNAL_GARBLED_CALL_DET Added new parameter(s):
ECTED EVENT_PARAM_GARBLED_SPEE
CH_DETECTION_TIME
EVENT_PARAM_GARBLED_SPEE
CH_CORRECTION_ACTION_TYPE
EVENT_PARAM_GARBLED_SPEE
CH_DETECTION_HFN_DELTA
Table 51 Event Parameters 20.Q2

New EVENT_PARAM_GARBLED_SPEE
CH_CORRECTION_ACTION_TYPE
CH_DETECTION_HFN_DELTA
CH_DETECTION_TIME
Chnaged EVENT_PARAM_EXTENDED_CAU Logical value(s) added:
SE_VALUE EVENT_VALUE_UE_CAPABILITY
_INFORMATION_TIMEOUT_NOT
_USED
Changed EVENT_PARAM_NWINIT_CALLR Logical value(s) added:
EEST_TRIGGER EVENT_VALUE_GARBLED_SPEE
CH_CORRECTION
8.2 GPEH 21.Q1

Updated Internal Event INTERNAL_CALL_REESTABLISH Added new parameter(s):
MENT EVENT_PARAM_CREAP_E1A_DE
LAYED
220 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

GPEH

New EVENT_PARAM_CREAP_E1A_DE
LAYED
Changed EVENT_PARAM_LTE_MEAS_DET Logical value(s) added:
AILED_REASON EVENT_VALUE_PS_RELEASE
8.3 GPEH 21.Q4

Updated Internal Event INTERNAL_LTE_MEASUREMENT Added new parameter(s):
_HANDLING EVENT_PARAM_LTE_MEAS_FAIL
ED_REATTEMPT

New EVENT_PARAM_LTE_MEAS_FAIL
ED_REATTEMPT
Changed EVENT_PARAM_LTE_MEAS_DET Logical value(s) added:
AILED_REASON EVENT_VALUE_LAU_AFTER_PS
HO_FROM_LTE
EVENT_VALUE_PERIODIC_TIME
R_EXPIRATION
Changed EVENT_PARAM_REQ_RNC_MOD Updated parameter description.
ULE_ID
18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 221

WRAN 21Q4 Network Impact Report

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WRAN 21Q4 Network Impact Report

Uploaded by

Copyright:

Available Formats

Network Impact Report

Network Impact Report

18/109 48-HSD 101 02/1 Uen LJ

© Ericsson AB 2017-2021. All rights reserved. No part of this document may be

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

3 Planned Functions 174

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

5.3 DU Counters 20.Q4 212

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

How to Read This Document

The NIR is split into the following two main sections:

— Under Released Functions, all globally released and unrestricted features

— Under Planned Functions, unreleased features are described to provide early

Delta information for parameters, counters, alarms, KPIs and General

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 1

1.1 Related Information

License and Hardware Activation Codes

Table 1 Licenses and Hardware Activation Codes

Compliance and Compatibility

Table 2 Compliance and Compatibility

Key Performance Indicators

Table 3 Key Performance Indicators

2 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

Table 4 Delta Information

Document Number Description

1.1.1 Software Support for RBS3000 with DUW

W17.Q4 is the last software release to support RBS3000 with DUW.

Note: — Unexpected failures may occur if RBS3000 with DUW is upgraded

— Potential problems may exist if RBS3000 with DUW runs with a

1.1.2 Software Support for RNC 3820

W19.Q2 is the latest software release where RNC 3820 is supported.

Customers wishing to continue to use RNC 3820 can operate on W19.Q2

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 3

2.1 New Features

2.1.1 EvoC RNC Geo-Redundancy Overview

The EvoC RNC Geo-Redundancy feature provides an emergency

Access Type: WCDMA

Geo-redundancy can be configured in two ways:

— Using the gr command in AMOS

The feature has the following benefits:

— Provides fast recovery of traffic.

— Minimizes the service interruption time.

— Redundancy support for unlimited number of RNCs in the network.

The feature supports the following configurations:

4 18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12

— EvoC 8300 and EvoC 8300

— EvoC 8300 and EvoC 8200/RNC

— EvoC 8200/RNC and EvoC 8200/RNC

2.1.2 Call Re-establishment for PS Overview

The Call re-establishment for PS feature enables re-establishment of a PS

Access Type WCDMA

This feature enables the UE to request re-establishment of a PS connection when

The connection can also be re-established for:

— Standalone SRB (no ongoing procedure exists)

18/109 48-HSD 101 02/1 Uen LJ | 2021-10-12 5

— Improves PS-retainability and accessibility.

— Expands CRE supported RAB combinations.

Feature introduces support for the following RAB combinations:

2.1.3 Garbled Speech Elimination Overview

Validation of UL AMR frames enables detection and correction of garbled

Access Type WCDMA

Garbled speech means incomprehensible voice that is caused by encryption or

This feature improves observability in speech quality area by introducing PM

2.1.4 User Profile Based Mobility Overview