Feature Description Guide

Software Features Description
User Documentation
240-00-0049
Issue 3
Copyright © 2016 Altiostar Networks, Inc.

All rights reserved.
Copyright © 2016 Altiostar Networks, Inc.
All rights reserved.
DOCUMENT NOTICE: The information contained in this manual is the property of Altiostar and is subject to change
without notice. Altiostar reserves the right to make changes in the design of its products or components as progress
in engineering and manufacturing may warrant. It is the responsibility of the customer to satisfy itself as to whether
the information contained herein is adequate and sufficient for particular use of a user. It is the further responsibility
of each user to ensure that all applications of Altiostar products are appropriate and safe based on conditions
anticipated or encountered during use. This document does not create any additional obligation for Altiostar and
does not constitute additional warranties and representations.
The Altiostar logo is a trademark and a service mark of Altiostar.
Questions: Please call Altiostar General Information at +1-855-709-0701.
Issue 3 Altiostar Software Features Description

240-00-0049
Preface
Preface
P.1 About the document

This document describes the software features available in the Altiostar software
releases.
P.2 Intended users

This document is intended for all personnel involved in the engineering, operation and
maintenance of the Altiostar system.
P.3 Licenses
For information on licenses for the software features, contact your local Altiostar
representative.
Software Features Description Altiostar Issue 3

240-00-0049 P-i
Preface Licenses

P-ii 240-00-0049
Contents
Contents
Preface ................................................................................................................ P-i
P.1 About the document .................................................................................. P-i
P.2 Intended users .......................................................................................... P-i
P.3 Licenses .................................................................................................... P-i
Chapter 1 What’s new ......................................................................................... 1-1
1.1 What’s new in Issue 3 .............................................................................. 1-1
1.2 What’s new in Issue 2 .............................................................................. 1-1
Chapter 2 Introduction........................................................................................ 2-1
Chapter 3 v2.0 Software Features Description .................................................... 3-1
3.1 UL CoMP ................................................................................................... 3-1
3.1.1 Feature Information ................................................................................ 3-1
3.1.2 Description ............................................................................................ 3-1
3.1.3 Benefits ................................................................................................ 3-2
3.1.4 Dependencies ........................................................................................ 3-2
3.1.5 Grouping under major function ................................................................. 3-2
3.1.6 Functional Diagrams/Flowcharts ............................................................... 3-2
3.1.7 Activation procedure ............................................................................... 3-2
3.1.8 Deactivation procedure............................................................................ 3-3
3.1.9 Parameters related to the feature ............................................................. 3-3
3.1.10 Affected existing parameters .................................................................. 3-3
3.1.11 Counters related to the feature ............................................................... 3-4
3.1.12 KPIs related to the feature ..................................................................... 3-4
3.2 Inter-Site CA ............................................................................................ 3-5
3.2.2 Description ............................................................................................ 3-5
3.2.3 Benefits ................................................................................................ 3-5
3.2.4 Dependencies ........................................................................................ 3-6
3.3 SSAC Barring for MMTEL Voice and Video ................................................. 3-9
3.3.2 Description ............................................................................................ 3-9
3.3.3 Benefits ................................................................................................ 3-9
3.3.4 Dependencies ........................................................................................ 3-9

240-00-0049 i
Contents
3.3.6 Functional Diagrams/Flowcharts ............................................................. 3-10

3.3.7 Activation procedure ............................................................................. 3-10
3.3.8 Deactivation procedure.......................................................................... 3-10
3.3.9 Parameters related to the feature ........................................................... 3-10
3.3.10 Affected existing parameters ................................................................ 3-10
3.3.11 Counters related to the feature ............................................................. 3-10
3.3.12 KPIs related to the feature ................................................................... 3-10
3.4 EM-SON .................................................................................................. 3-11
3.4.1 Feature Information .............................................................................. 3-11
3.4.2 Description .......................................................................................... 3-11
3.4.3 Benefits .............................................................................................. 3-11
3.4.4 Dependencies ...................................................................................... 3-11
3.4.5 Grouping under major function ............................................................... 3-11
3.5 VNF Manager - Phase 1........................................................................... 3-13
3.5.2 Description .......................................................................................... 3-13
3.5.3 Benefits .............................................................................................. 3-14
3.5.4 Dependencies ...................................................................................... 3-14
Chapter 4 v1.5 Software Features Description .................................................... 4-1
4.1 GPS - 1588 Failover .................................................................................. 4-1
4.1.2 Description ............................................................................................ 4-2
4.1.3 Benefits ................................................................................................ 4-2
4.1.4 Dependencies ........................................................................................ 4-2

ii 240-00-0049
Contents

4.2 Inter-Frequency HO Based on Coverage ................................................... 4-3
4.2.2 Description ............................................................................................ 4-3
4.2.3 Benefits ................................................................................................ 4-4
4.2.4 Dependencies ........................................................................................ 4-4
4.3 Features related to CSFB to GERAN .......................................................... 4-9
4.3.2 Description .......................................................................................... 4-10
4.3.3 Benefits .............................................................................................. 4-10
4.3.4 Dependencies ...................................................................................... 4-10
4.4 Features related to CSFB to UTRAN ........................................................ 4-18
4.4.2 Description .......................................................................................... 4-18
4.4.3 Benefits .............................................................................................. 4-18
4.4.4 Dependencies ...................................................................................... 4-18

240-00-0049 iii
Contents
4.5 Features related to IRAT and SR-VCC ..................................................... 4-24

4.5.2 Description .......................................................................................... 4-24
4.5.3 Benefits .............................................................................................. 4-24
4.5.4 Dependencies ...................................................................................... 4-24
4.5.9 Common Parameters related to the feature .............................................. 4-26
4.5.10 Parameters related to the feature ......................................................... 4-26
4.6 Features related to IRC PUSCH and Receiver.......................................... 4-33
4.6.2 Description .......................................................................................... 4-33
4.6.3 Benefits .............................................................................................. 4-34
4.6.4 Dependencies ...................................................................................... 4-34
4.6.5 Performance Curves.............................................................................. 4-34
4.7 UL FSS .................................................................................................... 4-38
4.7.2 Description .......................................................................................... 4-38
4.7.3 Benefits .............................................................................................. 4-38
4.7.4 Dependencies ...................................................................................... 4-38
4.8 Features related to RoHC, TTI and Scheduling........................................ 4-40

iv 240-00-0049
Contents
4.8.2 Description .......................................................................................... 4-40

4.8.3 Benefits .............................................................................................. 4-40
4.8.4 Dependencies ...................................................................................... 4-41
4.9 Features related to SR-VCC LTE .............................................................. 4-42
4.9.2 Description .......................................................................................... 4-42
4.9.3 Benefits .............................................................................................. 4-43
4.9.4 Dependencies ...................................................................................... 4-43
4.10 Features related to IPsec ..................................................................... 4-44
4.10.1 Feature Information ............................................................................ 4-44
4.10.2 Description ........................................................................................ 4-44
4.10.3 Benefits............................................................................................. 4-44
4.10.4 Dependencies..................................................................................... 4-44
4.10.5 Grouping under major function ............................................................. 4-44
4.10.6 Functional Diagrams/Flowcharts............................................................ 4-45
4.10.7 Activation procedure ........................................................................... 4-45
4.10.8 Deactivation procedure ........................................................................ 4-45
4.10.10 Affected existing parameters .............................................................. 4-50
4.10.11 Counters related to the feature ........................................................... 4-50
4.10.12 KPIs related to the feature ................................................................. 4-50
4.11 Default Bearer Differentiated Flow Treatment ...................................... 4-50
4.11.2 Description ........................................................................................ 4-50
4.11.3 Benefits............................................................................................. 4-51
4.11.4 Dependencies..................................................................................... 4-51

240-00-0049 v
Contents

4.12 Video Pacing for MP4/FLV decoder....................................................... 4-52
4.12.2 Description ........................................................................................ 4-52
4.12.3 Benefits............................................................................................. 4-52
4.12.4 Dependencies..................................................................................... 4-52
4.13 Automatic Neighbor Relations .............................................................. 4-53
4.13.2 Description ........................................................................................ 4-53
4.13.3 Benefits............................................................................................. 4-54
4.13.4 Dependencies..................................................................................... 4-54
4.13.13 Licensing requirement: ...................................................................... 4-56
4.14 Physical Cell Identity conflict detection ................................................ 4-56
4.14.2 Description ........................................................................................ 4-56
4.14.2.1 Enabling HO in case of PCID confusion .............................................. 4-56
4.14.3 Benefits............................................................................................. 4-56
4.14.4 Dependencies..................................................................................... 4-56

vi 240-00-0049
Contents

4.14.13 Licensing requirement ....................................................................... 4-58
4.15 Mobility Robustness Optimization ........................................................ 4-58
4.15.2 Description ........................................................................................ 4-59
4.15.3 Benefits............................................................................................. 4-59
4.15.4 Dependencies..................................................................................... 4-59
4.15.13 Licensing requirement ....................................................................... 4-62

240-00-0049 vii
Contents

viii 240-00-0049
List of figures
List of figures
Figure 3-1 CA Functional Flow ................................................................................ 3-6

Figure 3-2 EM-SON Functional Diagram ................................................................. 3-12
Figure 3-3 NFV-MANO Solution Architecture ........................................................... 3-15
Figure 4-1 GPS – 1588 Failover ............................................................................... 4-2
Figure 4-2 Ordered channel quality report for each user across resource blocks............ 4-39
Figure 4-3 Maximizes spectral efficiency ................................................................ 4-39
Figure 4-4 Backhaul IP Security ............................................................................ 4-45
Figure 4-5 Fronthaul IP Security ............................................................................ 4-45

240-00-0049 ix
List of figures

x 240-00-0049
List of tables
List of tables
Table 1-1 What’s new in Issue 3 .............................................................................. 1-1

Table 1-2 What’s new in Issue 2 .............................................................................. 1-1
Table 3-1 Feature Information - UL CoMP.................................................................. 3-1
Table 3-2 Feature Information - Inter-Site CA............................................................ 3-5
Table 3-3 Feature Information - SSAC Barring for MMTEL Voice and Video..................... 3-9
Table 3-4 Feature Information - EM-SON ................................................................ 3-11
Table 3-5 Feature Information - VNF Manager - Phase 1 ........................................... 3-13
Table 4-1 Feature Information - GPS 1588 Failover .................................................... 4-1
Table 4-2 Feature Information - Inter-Frequency HO Based on Coverage....................... 4-3
Table 4-3 Feature Information- CSFB to GERAN ......................................................... 4-9
Table 4-4 Feature Information - CSFB to UTRAN ...................................................... 4-18
Table 4-5 Feature Information - IRAT and SR-VCC ................................................... 4-24
Table 4-6 Feature Information - IRC PUSCH and Receiver ......................................... 4-33
Table 4-7 4Rx Performance Scenario for EPA5 ......................................................... 4-34
Table 4-8 4Rx Performance Scenario for EVA5 ......................................................... 4-35
Table 4-9 4Rx Performance Scenario for ETU70 ....................................................... 4-35
Table 4-10 2Rx Performance Scenario .................................................................... 4-36
Table 4-11 Feature Information- UL FSS ................................................................. 4-38
Table 4-12 Feature Information - RoHC, TTI and Scheduling...................................... 4-40
Table 4-13 Feature Information - SR-VCC LTE ......................................................... 4-42
Table 4-14 Feature information - IPsec ................................................................... 4-44
Table 4-15 Parameters defined for IPsec ................................................................. 4-46
Table 4-16 Feature Information - Default Bearer Differentiated Flow Treatment ........... 4-50
Table 4-17 Feature Information - Video Pacing for MP4/FLV decoder........................... 4-52
Table 4-18 Feature Information - Automatic Neighbor Relations ................................. 4-53
Table 4-19 Parameters Information - Automatic Neighbor Relations............................ 4-55
Table 4-20 Feature Information - Physical Cell Identity conflict detection..................... 4-56
Table 4-21 Parameters Information - PCI Conflict Detection....................................... 4-57
Table 4-22 Feature Information - Mobility Robustness Optimization ............................ 4-58
Table 4-23 Parameters Information - Mobility Robustness Optimization ....................... 4-60

240-00-0049 xi
List of tables

xii 240-00-0049
What’s new
Chapter 1
What’s new
This chapter lists the new features and enhancements added to the Altiostar Software
Features Description document.
1.1 What’s new in Issue 3

Table 1-1 What’s new in Issue 3 on page 1-1 lists the new information added to Issue
3 of the Altiostar Software Features Description document.
Table 1-1 What’s new in Issue 3
Feature/enhancement Description Refer to
v2.0 Software Added information about v2.0 Chapter 3 - v2.0 Software

Features software features. Features Description on
page 3-1.
1.2 What’s new in Issue 2

Table 1-2 What’s new in Issue 2 on page 1-1 lists the new information added to Issue
2 of the Altiostar Software Features Description document.
Table 1-2 What’s new in Issue 2
Feature/enhancement Description Refer to
v1.5 Software Added information about v1.5 Chapter 4 - v1.5 Software

Features software features. Features Description on
page 4-1.

240-00-0049 1-1
What’s new What’s new in Issue 2

1-2 240-00-0049
Introduction
Chapter 2
Introduction
This document provides information about Altiostar software features. For more
information, refer to the following chapters:
• Chapter 3 - v2.0 Software Features Description on page 3-1.
• Chapter 4 - v1.5 Software Features Description on page 4-1.
An eNodeB is a logical entity comprising of vBBU and an iRRH or a set of

iRRHs that represents a physical location of a radiating entity.
NOTE

240-00-0049 2-1
Introduction

2-2 240-00-0049
v2.0 Software Features Description
Chapter 3

This chapter provides information on the following v2.0 software features:
• UL CoMP on page 3-1.
• Inter-Site CA on page 3-5.
• SSAC Barring for MMTEL Voice and Video on page 3-9.
• EM-SON on page 3-11.
• VNF Manager - Phase 1 on page 3-13.
3.1 UL CoMP
3.1.1 Feature Information

For the feature information, refer to Table 3-1 Feature Information - UL CoMP on
page 3-1.
Table 3-1 Feature Information - UL CoMP
Feature ID Feature Name
P-0150 UL CoMP
3.1.2 Description
The UL-CoMP feature provides joint reception and interference mitigation for uplink
signals received by neighboring sectors. These neighboring sectors can be located
at the same deployment site or at different sites. The results of this feature are
seen as better UL throughput for cell edge users. There are multiple deployment
scenarios for which UL-CoMP reception can show significant benefits.
Numerous performance studies in the literature have shown that UL-CoMP provides
significant gains in the cell-edge spectral efficiency by performing joint reception
(JR) of the cell-edge users in the overlapping coverage areas. However, some of
the main challenges of implementing JR are the higher CoMP-specific feedback rate
requirement, along with lower latency, from participating CoMP nodes to the
master CoMP node where the joint decoding takes place. Because of this, JR
appears to be more suitable to a centralized RAN solution in which RRHs are
connected with the central vBBU via dedicated fiber links. Altiostar has developed
an alternative UL CoMP method that is more tolerant to transport delays with
comparable performance to the highly processing intensive JR algorithm.

240-00-0049 3-1
v2.0 Software Features Description UL CoMP
Macro deployments, dense deployments (such as in stadiums) and deployments

with significant Uplink (UL) traffic can be limited in coverage and performance due
to poor uplink reception. The UL-CoMP feature provides improved decoding of
uplink data with support from multiple eNodeBs which results in higher uplink
throughputs and better user experiences.
Assistance is provided by the supporting nodes to the principal node in the form of
equalized frequency domain symbols and other information required by the
principal node to combine with its own received signal through an auxiliary
communication channel between the radios. The combining of feedback with its
own signal helps achieve better Signal to Interference plus Noise Ratio (SINR)
thereby improving the throughput of the UE.
3.1.3 Benefits
UL CoMP provides increased throughput to UEs by making use of the signal
received at alternate eNodeBs. UL CoMP in combination with the Altiostar
proprietary UL Power Control (UL-PC) algorithm, helps reduce the UEs transmit
power in some cases, by providing additional combining gain since it mimics the
presence of more antennas than there are at the eNodeB.
3.1.4 Dependencies
Communication between the radios using the Altiostar Radio (AR) interface is
required.
3.1.5 Grouping under major function

None
3.1.6 Functional Diagrams/Flowcharts

None
3.1.7 Activation procedure

UL CoMP is activated for a UE, if one of the following conditions is valid:
• If the estimated UL SINR of the UE falls below a predetermined threshold. The
threshold is set using the configuration parameter, ULSINR Threshold.
• If the downlink RSRQ falls below a predetermined threshold. The threshold is
set using the configuration parameter, A2 Threshold under the event, A2
Intra ULCOMP.
Upon satisfying the valid condition, the system performs the following steps for
activation:
a. eNodeB configures A3-event for the UE as a result of which the UE reports a
list of neighboring nodes.

3-2 240-00-0049
UL CoMP v2.0 Software Features Description
b. The eNodeB checks for feasibility of AR link between the neighbors reported by
the UE with the help of a list of cooperating nodes maintained by EMS. The list
is pushed to the vBBU upon initialization.
c. Upon identification of such a node (supporting node), if the link is not already
setup, the principal node sets up the AR link between itself and the identified
node.
d. Once the AR link setup completes successfully, the primary node starts
requesting support from the supporting node. The supporting node responds
with feedback data based on availability of processing capability.
3.1.8 Deactivation procedure

UL CoMP is deactivated for a UE, if one of the following options is encountered:
• UE stops sending A3 reports for a period of time.
• The following conditions are valid:
• UL SINR goes above the threshold for activation, allowing for a hysteresis.
• Downlink RSRQ goes above the threshold for activation, allowing for a
hysteresis.
3.1.9 Parameters related to the feature

In the EMS GUI, the following parameters are related to this feature:
• EMS > Configuration > Configuration Explorer > BBU > Sector > ULCOMP >
ULCOMP Primary Enable.
Max Support Nodes.
ULSINR Threshold.
• EMS > Configuration > Configuration Explorer > BBU > Profiles > Handover >
Event A2 Intra ULCOMP : A2 Threshold.
Event A1 Intra ULCOMP : A1 Threshold.
Event A3 Intra ULCOMP
• A3 Offset
• Report Amount
• Report Interval
3.1.10 Affected existing parameters

None

240-00-0049 3-3
v2.0 Software Features Description UL CoMP
3.1.11 Counters related to the feature

The following Counters are related to this feature:
• ULCOMP.UeSmplsSum - The cumulative value of number of UL CoMP UEs,
samples of number of UL CoMP UEs taken every 5 seconds.
• ULCOMP.UeSmplsNbr - The cumulative value of number of samples
incremented by 1 every 5 seconds.
• ULCOMP.PrbPrvdedNbr - Number of PRB provided for UL CoMP UE.
• ULCOMP.PrbPrvdedSmplsNbr - Number of PRB samples.
• ULCOMP.ActvUeSmplsSum - Average number of UEs actively getting support
from at least 1 supporting node, samples are collected at 10 second.
• ULCOMP.ActvUeSmplsNbr - Number of active UE samples, which are collected
every 10 second.
• ULCOMP.SuppNodeReqUeNbr - Number of UEs requested support from the
supporting node.
• ULCOMP.SuppNodeReqRbNbr - Number of RBs requested support from the
supporting node.
• ULCOMP.PrimNodeAccptRbNbr - Number of accepted RBs by primary node.
• ULCOMP.PrimNodeLateArrRbNbr - Number of RBs that arrived late at primary
node.
• ULCOMP.PrimNodeRejetRbNbr - Number of rejected RBs by primary node.
• ULCOMP.SuppNodeReqRejRbNbr - Number of UL CoMP RB requests from the
primary node that were rejected.
• ULCOMP.SinrUeNbr.Gain - An alpha-averaged histogram of the number of UEs
that fall into a specific UL CoMP SINR gain bucket, per 10 second interval.
SINR Gain: ENUMERATED {db-5(-5), db-4(-4),…,db15(15)})
• ULCOMP.SinrRbNbr.Gain - An alpha-averaged histogram of the number of RBs
that fall into a specific UL CoMP SINR gain bucket, per 10 second interval. This
is an array, with elements representing the following:
SINR range: [-5dB to 15dB], in resolution of 0.5dB. 
SINR Gain: ENUMERATED {db-5(-5), db-4(-4),…,db15(15)})
3.1.12 KPIs related to the feature

The following KPIs are related to this feature:
• ULCOMP.AvgUeNbr - Number of UL CoMP UEs.
• ULCOMP.TotRbNbr - Total number of UL CoMP RBs.
• ULCOMP.AvgActvUeNbr - The number of UEs actively getting support from at
least one support node (while the previous stat represents all UEs which are
enabled for UL CoMP [hit the trigger], not necessarily receiving support) - A3
Event triggered and L1 Confirms AR Status to L2.
• ULCOMP.RBAccepByPrim - Percentage of RBs accepted by primary.

3-4 240-00-0049
Inter-Site CA v2.0 Software Features Description
• ULCOMP.RBArrivLateAtPrim - Percentage of RBs that arrived late at primary

node.
• ULCOMP.RBRejecByPrim - Percentage of RBs rejected by primary node for
other reasons.
• ULCOMP.RBRejecBySupp - Percentage of RBs rejected by supporting node.
3.2 Inter-Site CA

For the feature information, refer to Table 3-2 Feature Information - Inter-Site CA
on page 3-5.
Table 3-2 Feature Information - Inter-Site CA
P-0161 Inter-Site CA
3.2.2 Description
With Carrier Aggregation (CA) feature in Long-Term Evolution (LTE) Release 10,
load- balancing is part of the scheduler and can be executed in the timescale of
sub- frames. CA enables scalable expansion of bandwidth as the user can receive
transmissions from multiple component carriers simultaneously. In Inter-Site CA,
geographically non co-located cells can be used to aggregate BW and increase
overall throughput.
Operators deploying LTE in the Frequency-Division Duplex (FDD) mode can flexibly
utilize unequal bandwidths for downlink and uplink. In the Altiostar solution for
v2.0 release, two downlink carriers are aggregated, corresponding to a single
uplink carrier.
3GPP Release-10 carrier aggregation requirements were framed such that layers
above MAC are agnostic to the CA feature and each cell will utilize independent
HARQ operation. But this is not well-suited for operators with non-ideal front-haul,
neither does it extend well to multi-site scenarios. While operators and vendors
have enabled support in Release 12/13 time-frame, the Altiostar solution uses
simple, proprietary mechanisms to enable carrier aggregation for Release 10/11
users.
3.2.3 Benefits
The benefits of the feature are as follows:
• Peak UE throughput will scale linearly with the aggregated bandwidth.
• Traffic split through multiple transmission points, that is, increased load-
balancing benefits.

240-00-0049 3-5
v2.0 Software Features Description Inter-Site CA
• Robust mobility management as multiple SCells can be configured and rapidly

switched on/off based on proximity.
3.2.4 Dependencies
None

Capacity enhancement.

For information on the functional diagram/flowchart, refer to Figure 3-1 CA
Functional Flow on page 3-6.
Figure 3-1 CA Functional Flow

Activation procedure involves the following step:
In the EMS GUI, EMS > Configuration > Configuration Explorer > BBU > Sector >
CA Enabled to enabled.

Deactivation procedure involves the following step:
CA Enabled to disabled.

• EMS > Configuration > Configuration Explorer > BBU > Sector > CA Enabled.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Scell
Deactivation Timer.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Scell PCI
List.

3-6 240-00-0049
Inter-Site CA v2.0 Software Features Description
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > MAX CA
Users per cell.
Deactivate SINR Threshold.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Trigger
Period.
Acqi Enabled.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Datarate
High Threshold.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Datarate
Low Threshold.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Queue
Low Threshold.
• EMS > Configuration > Configuration Explorer > BBU > Sector > CA > Queue
High Threshold.

None

The following Counters are related to this feature:
• CA.CAUeSmplsSum - Sum of DL CA capable UEs in the current cell, which
serves as PCell for these UEs. 
A UE is considered to be "CA capable" if its UE-EUTRA-Capability indicates the
support of the band combination, that is configured for Carrier Aggregation in
eNB - accessStratumRelease Release greater than or equal Release 10.
• CA.CAUeSmplsNbr - Number of samples of CAUeSmplsSum.
• CA.ScellCnfgdSmplsSum - Sum of UEs in the current cell, which have a
configured SCell.
• CA.ScellCnfgdSmplsNbr - Number of samples of ScellCnfgdSmplsSum.
• CA.ScellActdSmplsSum - Sum of UEs in the current cell, which have an
activated SCell.
• CA.ScellActdSmplsNbr - Number of samples of ScellActdSmplsSum.
• CA.ScellCnfgAtt - Number of SCell configuration attempts.
Transmission of an RRC:RRCConnectionReconfiguration message, which
includes a "SCellToAddModList-r10" parameter
• CA.ScellCnfgSucc - Reception of an
RRC:RRCConnectionReconfigurationComplete message related to a preceding
RRC:RRCConnectionReconfiguration message, which includes a
"SCellToAddModList-r10" parameter and addressed to the same UE.

240-00-0049 3-7
v2.0 Software Features Description Inter-Site CA
• CA.ScellCnfgNbr.[Scell] - Number of successful CA configurations per Scell.

• CA.ScellActvNbr.[Scell] - Number of successful CA activations per Scell.
• CA.PdcpVolViaScell - Aggregated DL volume in Pcell which is transmitted
through all the Scells PHY.
• CA.ThpVolScell - Throughput volume when the Cell is acting as Scell & CA is
active.
• CA.ThpVolPcell - Throughput volume when the Cell is acting as Pcell & CA is
active.
• CA.ThpTimeScell - Throughput time (TTIs) when the Cell is acting as Scell &
CA is active.
• CA.ThpTimePcell - Throughput time (TTIs) when the Cell is acting as Pcell &
CA is active.
• CA.SessionTime [Pcell][Scell] - Active session time of CA activated UEs per
Scell.
• CA.PcellPrbDtchAllocNbr - PRB allocated for DTCH in Pcell when CA is active in
DL.
• CA.ScellPrbDtchAllocNbr - PRB allocated for DTCH in Scell when CA is active in
DL.

The following KPIs are related to this feature:
• CA.AvgCaCapableUeNbr - Average number of DL CA capable UEs in the
current cell, which serves as PCell for the UEs.
• CA.AvgScellConfigUeNbr - Average number of UEs in the current cell, which
have a configured SCell.
• CA.AvgScellActivUeNbr - Average number of UEs in the current cell, which
have an activated SCell.
• CA.CaCapableUeRatio - Ratio of the averaged number of the CA capable UEs
to average number of UEs in RRC_CONNECTED state.
• CA.ScellConfigUeRatio - Ratio of the average number of the UEs with a Scell
configured to the average number of UEs in RRC_CONNECTED state.
• CA.ScellActivUeRatio - Ratio of the average number of the UEs with Scell
activated to the average number of UEs in RRC_CONNECTED state.
• CA.ScellTrafficRatio - The PDCP volume per cell (in this cell with PCell role) in
downlink direction which is transmitted via SCell.
• CA.DlPcellSecThroughput - Downlink Pcell sector throughput.
• CA.DlScellSecThroughput - Downlink Scell sector throughput.
• CA.ScellConfigSuccRatio - Ratio of the successful and attempted SCell
configurations.

3-8 240-00-0049
SSAC Barring for MMTEL Voice and Video v2.0 Software Features Description
• CA.DlPcellPrbUtilization - Percentage of PRB Utilization at Pcell.

• CA.DlScellPrbUtilization - Ratio of traffic offloaded to SCell.
3.3 SSAC Barring for MMTEL Voice and Video

For the feature information, refer to Table 3-3 Feature Information - SSAC Barring
for MMTEL Voice and Video on page 3-9.
Table 3-3 Feature Information - SSAC Barring for MMTEL Voice and Video
S-0060 SSAC Barring for MMTEL Voice and Video
3.3.2 Description
In a disaster situation many users will try to access the network and create a
network overload condition which will affect network performance and the ability of
certain users (for example, emergency personnel) to access the network. The
service specific access control (SSAC) is a mechanism introduced to LTE for the
purpose of prioritizing access to certain types of users and restricting access of
other types for MMTEL (voice and video) services.
In order to facilitate access barring and control the EPS shall provide a capability to
assign a service probability factor for each of MMTEL voice and MMTEL video
services:
• assign a barring rate (percentage) commonly applicable for Access Classes 0-9;
• assign a flag barring status (barred /unbarred) for each Access Class in the
range 11-15.
• SSAC shall not apply to Access Class 10.
3.3.3 Benefits
SSAC provides the network operator the capability to limit access to the network
for LTE MMTEL services during periods of high congestion.
3.3.4 Dependencies
None

Services

240-00-0049 3-9
v2.0 Software Features Description SSAC Barring for MMTEL Voice and Video

None

SSAC Barring Enable to enabled.

SSAC Barring Enable to disabled.

• EMS > Configuration > Configuration Explorer > BBU > Sector > SSAC Barring
Enable.
• EMS > Configuration > Configuration Explorer > BBU > Sector > SIB2 > SSAC
Barring for MMTEL Voice > AC Barring Time.
Barring for MMTEL Voice > AC Barring Factor.
Barring for MMTEL Voice > AC Barring For Special AC.
Barring for MMTEL Video > AC Barring Time.
Barring for MMTEL Video > AC Barring Factor.
Barring for MMTEL Video > AC Barring For Special AC.

None

None

None

3-10 240-00-0049
EM-SON v2.0 Software Features Description
3.4 EM-SON

For the feature information, refer to Table 3-4 Feature Information - EM-SON on
page 3-11.
Table 3-4 Feature Information - EM-SON
O-0021 EM-SON
3.4.2 Description
The EM-SON function comprises the centralized portion of Altiostar's SON
framework and is co-resident with the Altiostar EMS. EM-SON provides the
management and orchestration functionality for the SON algorithms. This allows
for highly efficient inter-site and inter-RAT optimizations. EM-SON also provides
northbound IRP interfaces to the NM layer for integration with NMS systems and
third party SON systems. There are other IRP interfaces which are east-westbound
in order to integrate with other vendors EMS systems to allow for inter-vendor LTE
and inter-RAT optimizations.
The major functions performed by EM-SON include:
• SON policy control
• Monitoring of SON functions
• Coordination
• Parameter control
• History for rollback
• SON algorithms
3.4.3 Benefits
EM-SON provides centralized self-optimizing-network functionality.
3.4.4 Dependencies
EM-SON is dependent on EMS and its services.

SON

240-00-0049 3-11
v2.0 Software Features Description EM-SON

For information on the functional diagram/flowchart, refer to Figure 3-2 EM-SON
Functional Diagram on page 3-12.
Figure 3-2 EM-SON Functional Diagram

EM-SON becomes automatically active when license is available.

EM-SON will not be active when license is not available or if license is disabled.

In the EMS GUI, EMSON > Rule Configuration.

None

None

None

3-12 240-00-0049
VNF Manager - Phase 1 v2.0 Software Features Description
3.5 VNF Manager - Phase 1

For the feature information, refer to Table 3-5 Feature Information - VNF Manager
- Phase 1 on page 3-13.
Table 3-5 Feature Information - VNF Manager - Phase 1
O-0070 VNF Manager - Phase 1
3.5.2 Description
In order to manage Virtual Network Functions (VNF), the ETSI NFV-MANO
architecture expects a Virtual Network Function Manager (VNFM). The VNF Manager is
responsible for the lifecycle management of VNF instances. Each VNF instance is
assumed to have an associated VNF Manager. A VNF manager is responsible for the
management of multiple VNF instances of the same type or of different types.
Most of the VNF Manager functions are assumed to be generic common functions
applicable to any type of VNF. However, the NFV-MANO architectural framework needs
to also support cases where VNF instances need specific functionality for their lifecycle
management, and such functionality may be specified in the VNF Package.
The Altiostar VNFM supports the following functions:
• vBBU instantiation, including vBBU configuration as required by the deployment
template (e.g. vBBU initial configuration with IP addresses before completion of
the instantiation operation).
• vBBU instantiation feasibility checking, if required.
• vBBU instance software upgrade.
• vBBU instance modification.
• vBBU instance scaling up/down.
• vBBU instance assisted or automated healing.
• vBBU instance termination.
• vBBU lifecycle management change notification.
• Management of VNF package.
The Altiostar VNFM also implements a pseudo orchestrator module to support the
following NFVO actions that are required to support the VNFM functions:
• VIM infrastructure resource view (availability of compute resources such as
compute nodes, vCPU, memory and storage).
• Policy management
• Energy saving policies for the VIM.

240-00-0049 3-13
v2.0 Software Features Description VNF Manager - Phase 1
3.5.3 Benefits
The VNFM function provides the functionality for creating and managing the
Altiostar vBBU virtual network functions (VNFs).
3.5.4 Dependencies
The following prerequisites and dependencies need to be addressed for VNFM to
execute the functions:
a. Cluster setup with WindRiver Titanium Server (version 15.12).
b. Networks are planned and configured on WindRiver cluster.
c. Required tenants are configured on WindRiver cluster.
d. User with admin privilege created on Windriver cluster, can perform the
following operations:
• Flavor CRUD operations.
• Server (VNF) CRUD, all actions supported by OpenStack (including scaling
and live migration).
• Network read operations.
• Image CRUD operations.

OAM

The functional diagram provides various blocks of NFV-MANO solution architecture
and highlighted are the blocks that are implemented as part of Altiostar VNFM is

3-14 240-00-0049
VNF Manager - Phase 1 v2.0 Software Features Description
hosted on Altiostar EMS platform. For information on the functional diagram/

flowchart, refer to Figure 3-3 NFV-MANO Solution Architecture on page 3-15.
Figure 3-3 NFV-MANO Solution Architecture

Altiostar VNFM is bundled and installed with Altiostar EMS product. Follow the EMS
deployment procedure. For more information, refer to the Altiostar EMS v2.0
Installation Guide.

Altiostar VNFM is bundled and installed with Altiostar EMS product. Follow the EMS
uninstallation procedure. For more information, refer to the Altiostar EMS v2.0
Installation Guide.

None

None

None

240-00-0049 3-15
v2.0 Software Features Description VNF Manager - Phase 1

None

3-16 240-00-0049
Chapter 4

This chapter provides information on the following v1.5 software features:
• GPS - 1588 Failover on page 4-1.
• Inter-Frequency HO Based on Coverage on page 4-3.
• Features related to CSFB to GERAN on page 4-9.
• Features related to CSFB to UTRAN on page 4-18.
• Features related to IRAT and SR-VCC on page 4-24.
• Features related to IRC PUSCH and Receiver on page 4-33.
• UL FSS on page 4-38.
• Features related to RoHC, TTI and Scheduling on page 4-40.
• Features related to SR-VCC LTE on page 4-42.
• Features related to IPsec on page 4-44.
• Default Bearer Differentiated Flow Treatment on page 4-50.
• Video Pacing for MP4/FLV decoder on page 4-52.
• Automatic Neighbor Relations on page 4-53.
• Physical Cell Identity conflict detection on page 4-56.
• Mobility Robustness Optimization on page 4-58.
4.1 GPS - 1588 Failover

For the feature information, refer to Table 4-1 Feature Information - GPS 1588
Failover on page 4-1.
Table 4-1 Feature Information - GPS 1588 Failover
G-0190 GPS - 1588 Failover

240-00-0049 4-1
v1.5 Software Features Description GPS - 1588 Failover
4.1.2 Description
This feature enables failover mechanism between primary and secondary timing
sources. The primary/preferred timing source is GPS whereas the secondary being
IEEE1588v2 (PTP). This feature allows seamless transition across timing sources in
a redundant manner, such that loss of timing synchronization with the preferred
source will not impact the functionality of the iRRH.
4.1.3 Benefits
This feature allows redundancy of timing sources which allows seamless failover
from one source to the other, in case of a failure scenario (timing synchronization
loss).
4.1.4 Dependencies
None

This feature is grouped under the Timing function.

For information on the functional diagrams/flowchart, refer to Figure 4-1 GPS –
1588 Failover on page 4-2.
Figure 4-1 GPS – 1588 Failover


4-2 240-00-0049
Inter-Frequency HO Based on Coverage v1.5 Software Features Description
• Select timing source from EMS

None

The parameters related to this feature are listed below:
• ConfigTiming
• ConfigGPS
• ConfigIEEE1588

None

None

None
4.2 Inter-Frequency HO Based on Coverage

For the feature information, refer to Table 4-2 Feature Information - Inter-
Frequency HO Based on Coverage on page 4-3.
Table 4-2 Feature Information - Inter-Frequency HO Based on Coverage
M-0030 Inter-Frequency HO Based on Coverage
4.2.2 Description
This feature allows a UE to handover from one frequency to another depending on
the thresholds set for the handover.

240-00-0049 4-3
v1.5 Software Features Description Inter-Frequency HO Based on Coverage
4.2.3 Benefits
This feature allows mobility of the UE in a multi-frequency network with the help of
handovers. It is especially beneficial in deployments where the operator may
require support for more than one band in their network.
4.2.4 Dependencies
None

This feature is grouped under the Mobility function.

For information on the functional diagrams/flowchart, refer to the following figures
from the 3GPP TS 23.401 version 9.16.0 Release 9 document:
• Figure 5.5.1.1.2-1: X2-based handover without Serving GW relocation.
• Figure 5.5.1.1.3-1: X2-based handover with Serving GW relocation.
• Figure 5.5.1.2.2-1: S1-based handover.

Activation procedure involves the following steps:
a. Configure required inter-frequency.
b. Set A2-inter and A1-inter threshold values according to the deployment plan.
c. Procedure will be activated once UE reports A2-inter event. A2-inter event will
lead to A3-inter and A1-inter event configuration.
d. UE reporting A3-inter event will result in handover.

Procedure will be deactivated once UE reports A1-inter event. A1-inter event will
result in A2-inter event configuration.

a. BBU > Sector > Neighbor > EUTRAN
• Sector ID
• Carrier Frequency
• Measurement-Object-Allowed Meas Bandwidth
• Measurement-Object-Presence Antenna Port1

4-4 240-00-0049
• Measurement-Object-Neighbor Cell Configuration

• Measurement-Object-Offset Frequency
• Handover-Profile-Info-Event Intra Frequency ID – This is necessary if Carrier
frequency is serving frequency for setting A2-inter threshold value.
• Handover-Profile-Info-Event Inter Frequency ID – This is necessary when
Carrier Frequency is inter-frequency.
b. BBU > Sector > Neighbor > EUTRAN > NBR Cell Item
• Sector ID
• Carrier Freq
• PLMN Identity
• Cell Identity
• NBR ENB ID
• TAI-PLMN_Identity
• TAI-TAC
• PHY Cell ID
• Cell Individual Offset
• HO Allowed
• NR Status
c. BBU > Profiles > Handover Profile > Profile Event Inter Frequency > Event A2
inter
• Trigger Quantity
• Report Quantity
• Max Report Cells
• Report Interval
• Report Amount
• Trigger Type – Should be set to Event
d. BBU > Profiles > Handover Profile > Profile Event Inter Frequency > Event A2
inter > Event
• Hysteresis
• Time To Trigger
• Event ID – Should be set to Event A2
e. BBU > Profiles > Handover Profile > Profile Event Inter Frequency > Event A2
inter > Event > Event-A2
• A2-threshold
f. BBU > Profiles > Handover Profile > Profile Event Inter Frequency > Event A3
inter

240-00-0049 4-5
• Report Quantity
• Report Interval
• Report Amount
• Trigger Type – Should be set to Event
g. BBU > Profiles > Handover Profile > Profile Event Inter Frequency > Event A3
inter > Event
• Hysteresis
• Time To Trigger
• Event ID – Should be set to Event A3
h. BBU > Profiles > Handover Profile > Profile Event Inter Frequency > Event A3
inter > Event > Event-A3
• A3 Offset
• Report on leave

None

The counters related to this feature are listed below:
• HOOUT.InterFreqMeasGapAttNbr - Attempted UE outgoing inter-frequency
handovers when meas gaps are used.
• HOOUT.InterFreqMeasGapSuccNbr - Successful UE outgoing inter-frequency
handovers when meas gaps are used.
• HOOUT.InterFreqNoMeasGapAttNbr - Attempted UE outgoing inter-
frequency handovers when meas gaps are not used.
• HOOUT.InterFreqNoMeasGapSuccNbr - Successful UE outgoing inter-
frequency handovers when meas gaps are not used.
• HOOUT.InterFreqIntraEnbPrepAttNbr - Inter frequency Intra eNodeB HO
Prep attempts, that is, before receiving HO ACK.
• HOOUT.InterFreqIntraEnbPrepSuccNbr - Inter frequency Intra eNodeB HO
Prep success, that is, before receiving HO ACK.
• HOOUT.InterFreqIntraEnbPrepCnclNbr - Inter frequency Intra eNodeB HO
cancel in Prep Phase, that is, before receiving HO ACK.
• HOOUT.InterFreqIntraEnbExecAttNbr - Inter frequency Intra eNodeB HO
attempts in Exec Phase, that is, after sending Reconfiguration to UE.

4-6 240-00-0049
• HOOUT.InterFreqIntraEnbExecSuccNbr - Inter frequency Intra eNodeB HO

success in Exec Phase, that is, after sending Reconfig to UE.
• HOOUT.InterFreqIntraEnbExecCnclNbr - Inter frequency Intra eNodeB HO
cancel in Exec Phase, that is, after receiving HO ACK. A1 event, UE Ctxt Rel.
• HOOUT.InterFreqIntraEnbOthrCnclNbr - Inter frequency Intra eNodeB HO
cancel due to faulty situation. For example, internal fail, Re-Estab and so on.
• HOOUT.InterFreqS1PrepAttNbr - Inter frequency S1 HO Prep attempts, that
is, before receiving HO ACK.
• HOOUT.InterFreqS1PrepSuccNbr - Inter frequency S1 HO Prep success, that
• HOOUT.InterFreqS1PrepCnclNbr - Inter frequency S1 HO cancel in Prep
Phase, that is, before receiving HO ACK.
• HOOUT.InterFreqS1ExecAttNbr - Inter frequency S1 HO attempts in Exec
Phase, that is, after sending Reconfig to UE.
• HOOUT.InterFreqS1ExecSuccNbr - Inter frequency S1 HO success in Exec
• HOOUT.InterFreqS1ExecCnclNbr - Inter frequency S1 HO cancel in Exec
Phase, that is, after receiving HO ACK. A1 event, UE Ctxt Rel.
• HOOUT.InterFreqS1OthrCnclNbr - Inter frequency S1 HO cancel due to faulty
situation. For example, internal fail, Re-Estab and so on.
• HOOUT.InterFreqX2PrepAttNbr - Inter frequency X2 HO Prep attempts, that
• HOOUT.InterFreqX2PrepSuccNbr - Inter frequency X2 HO Prep success, that
• HOOUT.InterFreqX2PrepCnclNbr - Inter frequency X2 HO cancel in Prep
Phase, that is, before receiving HO ACK.
• HOOUT.InterFreqX2ExecAttNbr - Inter frequency X2 HO attempts in Exec
• HOOUT.InterFreqX2ExecSuccNbr - Inter frequency X2 HO success in Exec
• HOOUT.InterFreqX2ExecCnclNbr - Inter frequency X2 HO cancel in Exec
Phase, that is, after receiving HO ACK. A1 event, UE Ctxt Rel.
• HOOUT.InterFreqX2OthrCnclNbr - Inter frequency X2 HO cancel due to faulty
situation. For example, internal fail, Re-Estab and so on.
• HOINC.InterFreqIntraEnbPrepAttNbr - Inter frequency Intra eNodeB HO Prep
attempts, that is, before sending HO ACK.
• HOINC.InterFreqIntraEnbPrepSuccNbr - Inter frequency Intra eNodeB HO
Prep success, that is, before sending HO ACK.
• HOINC.InterFreqIntraEnbPrepCnclNbr - Inter frequency Intra eNodeB HO
cancel in Prep Phase, that is, before sending HO ACK.

240-00-0049 4-7
• HOINC.InterFreqIntraEnbExecAttNbr - Inter frequency Intra eNodeB HO

attempts in Exec Phase, that is, after sending HO Ack.
• HOINC.InterFreqIntraEnbExecSuccNbr - Inter frequency Intra eNodeB HO
success in Exec Phase, that is, after sending HO Ack.
• HOINC.InterFreqIntraEnbExecCnclNbr - Inter frequency Intra eNodeB HO
cancel in Exec Phase, that is, after sending HO Ack.
• HOINC.InterFreqS1PrepAttNbr - Inter frequency S1 HO Prep attempts, that
is, before sending HO ACK.
• HOINC.InterFreqS1PrepSuccNbr - Inter frequency S1 HO Prep success, that
• HOINC.InterFreqS1PrepCnclNbr - Inter frequency S1 HO cancel in Prep
Phase, that is, before sending HO ACK.
• HOINC.InterFreqS1ExecAttNbr - Inter frequency S1 HO attempts in Exec
Phase, that is, after sending HO Ack.
• HOINC.InterFreqS1ExecSuccNbr - Inter frequency S1 HO success in Exec
• HOINC.InterFreqS1ExecCnclNbr - Inter frequency S1 HO cancel in Exec
• HOINC.InterFreqX2PrepAttNbr - Inter frequency X2 HO Prep attempts, that
• HOINC.InterFreqX2PrepSuccNbr - Inter frequency X2 HO Prep success, that
• HOINC.InterFreqX2PrepCnclNbr - Inter frequency X2 HO cancel in Prep
Phase, that is, before sending HO ACK.
• HOINC.InterFreqX2ExecAttNbr - Inter frequency X2 HO attempts in Exec
• HOINC.InterFreqX2ExecSuccNbr - Inter frequency X2 HO success in Exec
• HOINC.InterFreqX2ExecCnclNbr - Inter frequency X2 HO cancel in Exec

The KPIs related to this feature are listed below:
• HoOutInterFreqGapSuccRate - The percentage of inter-frequency outgoing
handovers with gap-assisted measurements that are completed successfully.
• HoOutInterFreqNonGapSuccRate - The percentage of inter-frequency
outgoing handovers without gap-assisted measurements that are completed
successfully.
• HoOutInterFreqIntraEnbPrepSuccRate - Outgoing HO Inter frequency Intra
eNodeB- Preparation Success Rate.

4-8 240-00-0049
Features related to CSFB to GERAN v1.5 Software Features Description
• HoOutInterFreqIntraEnbExecSuccRate - Outgoing HO Inter frequency Intra

eNodeB- Execution Success Rate.
• HoOutInterFreqInterEnbS1PrepSuccRate - Outgoing HO Inter frequency
Inter eNodeB over S1- Preparation Success Rate.
• HoOutInterFreqInterEnbS1ExecSuccRate - Outgoing HO Inter frequency
Inter eNodeB over S1- Execution Success Rate.
• HoOutInterFreqInterEnbX2PrepSuccRate - Outgoing HO Inter frequency
Inter eNodeB over X2- Preparation Success Rate.
• HoOutInterFreqInterEnbX2ExecSuccRate - Outgoing HO Inter frequency
Inter eNodeB over X2- Execution Success Rate.
• HoIncInterFreqIntraEnbPrepSuccRate - Incoming HO Inter frequency Intra
eNodeB- Preparation Success Rate.
• HoIncInterFreqIntraEnbExecSuccRate - Incoming HO Inter frequency Intra
eNodeB- Execution Success Rate.
• HoIncInterFreqInterEnbS1PrepSuccRate - Incoming HO Inter frequency
Inter eNodeB over S1- Preparation Success Rate.
• HoIncInterFreqInterEnbS1ExecSuccRate - Incoming HO Inter frequency
Inter eNodeB over S1- Execution Success Rate.
• HoIncInterFreqInterEnbX2PrepSuccRate - Incoming HO Inter frequency
Inter eNodeB over X2- Preparation Success Rate.
• HoIncInterFreqInterEnbX2ExecSuccRate - Incoming HO Inter frequency
Inter eNodeB over X2- Execution Success Rate.
• HoOutInterFreq - Outgoing HO Inter frequency handover.
• HoIncInterFreq - Incoming HO Inter frequency handover.
4.3 Features related to CSFB to GERAN

For the feature information, refer to Table 4-3 Feature Information- CSFB to
GERAN on page 4-9.
Table 4-3 Feature Information- CSFB to GERAN
M-0050 CSFB to GERAN – Redirection
M-0060 CSFB to GERAN – eRedirection
M-0061 CSFB to GERAN via CCO without NACC
M-0062 CSFB to GERAN via CCO with NACC

240-00-0049 4-9
v1.5 Software Features Description Features related to CSFB to GERAN
4.3.2 Description
This feature allows the UE to switch to a Circuit Based switch in GERAN/GSM
networks in order to make a voice call. 3GPP 36.300 Clause 10.2.5 allows for CS
Fallback to GSM using the RRC Connection Release with Redirection procedure.
4.3.3 Benefits
This feature allows operators to provide voice functionality to users by utilizing
their legacy GSM network.
4.3.4 Dependencies
Interaction with M-0120:
When IRAT 2G HO is enabled along with any of the CSFB features M-0050/M-0060/
M-0061/M-0062, eNodeB always tries to do CS Fallback with IRAT PSHO. If CS
Fallback with IRAT PSHO is not possible, configured CSFB option is used.

These features are grouped under the Mobility function.

For information on the functional diagrams/flowchart, refer to the 3GPP TS
23.401 version 9.16.0 Release 9 document.

M-0050
a. Load balancing: Set Configuration > Configuration Explorer > BBU > Sector >
IRAT > GERAN > CSFB to redirection.
b. Measurement: Set Configuration > Configuration Explorer > BBU > Sector >
IRAT > GERAN > CSFB to redirection-meas.
M-0060
IRAT > GERAN > CSFB to eredirection.
IRAT > GERAN > CSFB to eredirection-meas.
M-0061
CCO without NACC: Set Configuration > Configuration Explorer > BBU > Sector >
IRAT > GERAN > CSFB to cco.
M-0062

4-10 240-00-0049
IRAT > GERAN > CSFB to cco-nacc.

Deactivation procedure involves the following steps:
M-0050
IRAT > GERAN > CSFB to disabled.
M-0060
M-0061
M-0062

M-0050
Load balancing:
a. Configuration > Configuration Explorer > BBU > Sector > IRAT > CSFB
Common > IRAT Pref CSFB.
b. Configuration > Configuration Explorer > BBU > Sector > IRAT > GERAN >
CSFB Pref ARFCN.
c. Configuration > Configuration Explorer > BBU > Sector > IRAT > CSFB
Common > IRAT Pref Emergency Call.
d. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN:
• Sector ID
• ARFCN
• Band
• CSFB Load Factor
• Following ARFCNs

240-00-0049 4-11
e. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN
> Neighbor Cell Item:
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID
• ARFCN
• RAC
• Physical Cell ID - Network Color Code
• Physical Cell ID - Base Station Color Code
Measurement:
CSFB Pref ARFCN.
d. Configuration > Configuration Explorer > BBU > Sector > IRAT > CSFB
Common > CSFB Meas Timeout.
e. Configuration > BBU > Sector > Neighbor > GERAN
• Sector ID
• ARFCN
• Band
• NCC Permitted
• Offset Frequency
f. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID

4-12 240-00-0049
• ARFCN
• RAC
M-0060
Load balancing:
CSFB Pref ARFCN.
d. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN:
• Sector ID
• ARFCN
• Band
e. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID
• ARFCN
• RAC
Measurement:
CSFB Pref ARFCN.

240-00-0049 4-13
e. Configuration > BBU > Sector > Neighbor > GERAN
• Sector ID
• ARFCN
• Band
• NCC Permitted
f. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID
• ARFCN
• RAC
M-0061
CCO without NACC:
CSFB Pref ARFCN.
c. Configuration > Configuration Explorer > BBU > Sector > IRAT > GERAN >
CCO T304 Timer
e. Configuration > Configuration Explorer > BBU > Sector > IRAT > CSFB
f. Configuration > BBU > Sector > Neighbor > GERAN
• Sector ID

4-14 240-00-0049
• ARFCN
• Band
• NCC Permitted
g. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID
• ARFCN
• RAC
M-0062
CCO with NACC:
CSFB Pref ARFCN.
c. Configuration > Configuration Explorer > BBU > Sector > IRAT > GERAN >
CCO T304 Timer
e. Configuration > Configuration Explorer > BBU > Sector > IRAT > CSFB
f. Configuration > BBU > Sector > Neighbor > GERAN
• Sector ID
• ARFCN
• Band
• NCC Permitted

240-00-0049 4-15
g. Configuration > Configuration Explorer > BBU > Sector > Neighbor > GERAN
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID
• ARFCN
• RAC

None

The counters related to the feature are listed below:
Common Counters:
• CSFB.TotAttNbr
• CSFB.GeranReqIdleModeNbr
• CSFB.GeranReqConnctdModeNbr
• CSFB.MeasRprtTimeoutGeranNbr
M-0050:
• CSFB.RelRdrctnToGeranNbr
• CSFB.TimeTknRdrctnToGeran
• CSFB.EmrgncyRdrctnToGeranNbr
• CSFB.RelEmrgncyRdrctnToGeranNbr
• CSFB.RelRdrctnMeasToGeranNbr
• CSFB.TimeTknRdrctnMeasToGeran
• CSFB.RelRdrctnPerGeranCarrierNbr
M-0060:
• CSFB.RelERdrctnToGeranNbr
• CSFB.TimeTknErdrctnToGeran
• CSFB.RelERdrctnMeasToGeranNbr

4-16 240-00-0049
• CSFB.TimeTknERdrctnMeasToGeran
• CSFB.RelERdrctnPerGeranCarrierNbr
• S1APNodalMsg.ENBDirectInfTransferGeran
• S1APNodalMsg.MMEDirectInfTransferGeran
M-0061:
• CSFB.CcoAttNbr
• CSFB.CcoSuccNbr
M0062:
• CSFB.CcoNaccAttNbr
• CSFB.CcoNaccSuccNbr
M-0050/ M-0060/M-0061/M-0062 with M-0120:
• HOOUT.CsfbPshoGeranPrepAttNbr
• HOOUT.CsfbPshoGeranPrepSuccNbr
• HOOUT.CsfbPshoGeranPrepCnclNbr
• HOOUT.CsfbPshoGeranExecAttNbr
• HOOUT.CsfbPshoGeranExecSuccNbr
• HOOUT.CsfbPshoGeranExecCnclNbr
• HOOUT.CsfbPshoGeranExecOthrCnclNbr
• HOOUT.CsfbPshoGeranPrepCnclNbr.Cause
• HOOUT.CsfbPshoGeranExecCnclNbr.Cause

The KPIs related to the feature are listed below:
M-0050: CsfbGeranRdrctnSuccRatio
M-0060: CsfbGeranERdrctnSuccRatio
M-0061 and M-0062: CcoSuccRatio

240-00-0049 4-17
v1.5 Software Features Description Features related to CSFB to UTRAN
4.4 Features related to CSFB to UTRAN

For the feature information, refer to Table 4-4 Feature Information - CSFB to
UTRAN on page 4-18.
Table 4-4 Feature Information - CSFB to UTRAN
M-0090 CSFB to UTRAN – Redirection
M-0100 CSFB to UTRAN – eRedirection
4.4.2 Description
This feature allows the UE to switch to a Circuit Based switch in UTRAN/UMTS
networks in order to make a voice call. 3GPP 36.300 Clause 10.2.5 allows for CS
Fallback to UMTS using the RRC Connection Release with Redirection procedure.
4.4.3 Benefits
This feature allows operators to provide voice functionality to users by utilizing
their legacy UMTS network.
4.4.4 Dependencies
Interaction with M-0121:
When IRAT 3G HO is enabled along with any of the CSFB features M-0090/M-0100,
eNodeB always tries to do CS Fallback with IRAT PSHO (measurement based). If
CS Fallback with IRAT PSHO is not possible, configured CSFB option will be used.

These features are grouped under the Mobility function.

For information on the functional diagrams/flowchart, refer to the 3GPP TS
23.401 version 9.16.0 Release 9 document.

M-0090
IRAT > UTRAN > CSFB to redirection.

4-18 240-00-0049
Features related to CSFB to UTRAN v1.5 Software Features Description
IRAT > UTRAN > CSFB to redirection-meas.
M-0100
IRAT > UTRAN > CSFB to eredirection.
IRAT > UTRAN > CSFB to eredirection-meas.

M-0090
IRAT > UTRAN > CSFB to disabled.
M-0100

M-0090
Load balancing:
b. Configuration > Configuration Explorer > BBU > Sector > IRAT > UTRAN >
CSFB Pref ARFCN.
d. Configuration > Configuration Explorer > BBU > Sector > Neighbor > UTRAN:
• Sector ID
• ARFCN
• Duplex Mode
• Band
e. Configuration > Configuration Explorer > BBU > Sector > Neighbor > UTRAN

240-00-0049 4-19
• Sector ID
• ARFCN
• Duplex Mode
• Band
• PLMN Identity
• RNC ID
• Cell ID
• LAC
• RAC
• Physical Cell ID
Measurement:
CSFB Pref ARFCN.
e. Configuration > BBU > Sector > Neighbor > UTRAN:
• Sector ID
• ARFCN
• Duplex Mode
• Band
f. Configuration > Configuration Explorer > BBU > Sector > Neighbor > UTRAN
• Sector ID
• ARFCN
• Duplex Mode
• Band
• PLMN Identity
• RNC ID
• Cell ID
• LAC

4-20 240-00-0049
• RAC
M-0100
Load balancing:
CSFB Pref ARFCN.
d. Configuration > Configuration Explorer > BBU > Sector > Neighbor > UTRAN:
• Sector ID
• ARFCN
• Duplex Mode
• Band
e. Configuration > Configuration Explorer > BBU > Sector > Neighbor > UTRAN
• Sector ID
• ARFCN
• Duplex Mode
• Band
• PLMN Identity
• RNC ID
• Cell ID
• LAC
• RAC
Measurement:
CSFB Pref ARFCN.

240-00-0049 4-21
e. Configuration > BBU > Sector > Neighbor > UTRAN:

• Sector ID
• ARFCN
• Duplex Mode
• Band
f. Configuration > Configuration Explorer > BBU > Sector > Neighbor > UTRAN
• Sector ID
• ARFCN
• Duplex Mode
• Band
• PLMN Identity
• RNC ID
• Cell ID
• LAC
• RAC

None

Common Counters:
• CSFB.TotAttNbr
• CSFB.UtranReqIdleModeNbr
• CSFB.UtranReqConnctdModeNbr
• CSFB.MeasRprtTimeoutUtranNbr
M-0090:
• CSFB.RelRdrctnToUtranNbr
• CSFB.TimeTknRdrctnToUtran
• CSFB.EmrgncyRdrctnToUtranNbr
• CSFB.RelEmrgncyRdrctnToUtranNbr

4-22 240-00-0049
• CSFB.RelRdrctnMeasToUtranNbr
• CSFB.TimeTknRdrctnMeasToUtran
• CSFB.RelRdrctnPerUtranCarrierNbr
M-0100:
• CSFB.RelERdrctnToUtranNbr
• CSFB.TimeTknErdrctnToUtran
• CSFB.RelERdrctnMeasToUtranNbr
• CSFB.TimeTknERdrctnMeasToUtran
• CSFB.RelERdrctnPerUtranCarrierNbr
• S1APNodalMsg.ENBDirectInfTransferUtran
• S1APNodalMsg.MMEDirectInfTransferUtran
M-0090/M-0100 with M-0121:
• HOOUT.CsfbPshoUtranPrepAttNbr
• HOOUT.CsfbPshoUtranPrepSuccNbr
• HOOUT.CsfbPshoUtranPrepCnclNbr
• HOOUT.CsfbPshoUtranExecAttNbr
• HOOUT.CsfbPshoUtranExecSuccNbr
• HOOUT.CsfbPshoUtranExecCnclNbr
• HOOUT.CsfbPshoUtranExecOthrCnclNbr
• HOOUT.CsfbPshoUtranPrepCnclNbr.Cause
• HOOUT.CsfbPshoUtranExecCnclNbr.Cause

M-0050: CsfbUtranRdrctnSuccRatio
M-0060: CsfbUtranERdrctnSuccRatio

240-00-0049 4-23
v1.5 Software Features Description Features related to IRAT and SR-VCC
4.5 Features related to IRAT and SR-VCC

For the feature information, refer to Table 4-5 Feature Information - IRAT and SR-
VCC on page 4-24.
Table 4-5 Feature Information - IRAT and SR-VCC
M-0110 I-RAT Idle mode mobility to GERAN
M-0111 I-RAT Idle mode mobility to UTRAN
M-0120 IRAT 2G HO
M-0121 IRAT 3G HO
S-0110 SR-VCC LTE – GERAN
S-0111 SR-VCC LTE – UTRAN
4.5.2 Description
This feature allows seamless handover from LTE to legacy networks of GERAN/GSM
or UTRAN/UMTS. Mobility to legacy networks from LTE network can be achieved in
idle mode or in active mode. Furthermore the SR-VCC feature allows for seamless
voice continuity during the mobility from LTE to the legacy networks.
4.5.3 Benefits
This feature provides an operator to continue using the legacy networks for
coverage where LTE networks are not deployed. Furthermore adding SRVCC for
voice connectivity allows for handover of a voice call to a legacy network without a
break in connection.
4.5.4 Dependencies
None

These features are grouped under the following major functions:
• Mobility
• Services

4-24 240-00-0049
Features related to IRAT and SR-VCC v1.5 Software Features Description

For information on the functional diagrams/flowchart, refer to the following figures:
• Inter RAT Handover to UTRAN/GERAN call flow diagrams under 3GPP TS 23.401
version 9.16.0 Release 9 Section 5.5.2.
• SRVCC from EUTRAN call flow diagrams under 3GPP TS 23.216 version 9.9.0
Release 9.

M-0120
Inter RAT Handover to GERAN feature is activated by setting Configuration > BBU
> Sector > IRAT > GERAN > HandOver-PSHO value to enabled.
M-0121
Inter RAT Handover to UTRAN feature is activated by setting Configuration > BBU
> Sector > IRAT > UTRAN > HandOver-PSHO value to enabled.
M-0110
SRVCC from EUTRAN to GERAN feature is activated by setting Configuration > BBU
> Sector > IRAT > GERAN > HandOver-SRVCC value to enabled.
M-0111
SRVCC from EUTRAN to UTRAN feature is activated by setting Configuration > BBU
> Sector > IRAT > UTRAN > HandOver-SRVCC value to enabled.

M-0120
Inter RAT Handover to GERAN feature is deactivated by setting Configuration >
BBU > Sector > IRAT > GERAN > HandOver-PSHO value to disabled.
M-0121
Inter RAT Handover to UTRAN feature is deactivated by setting Configuration >
BBU > Sector > IRAT > UTRAN > HandOver-PSHO value to disabled.
M-0110
SRVCC from EUTRAN to GERAN feature is deactivated by setting Configuration >
BBU > Sector > IRAT > GERAN > HandOver-SRVCC value to disabled.
M-0111
a. SRVCC from EUTRAN to UTRAN feature is deactivated by setting Configuration
> BBU > Sector > IRAT > UTRAN > HandOver-SRVCC value to disabled.

240-00-0049 4-25
4.5.9 Common Parameters related to the feature

M-0050
Configure Default Event Inter RAT ID
Configuration > BBU > Sector > Default Handover profile > Event Inter RAT ID.
Configure HO Profile:
Configure Event A1 Inter RAT under Serving frequency HO profile
Configuration > BBU > Profiles > HO > Profile Event Intra Frequency > Event.
A1 Inter RAT
• Report Quantity
• Report Interval
• Report Amount
• Trigger Type
• Hysteresis
• Time To Trigger
• Event A1
• A1 Threshold (RSRP or RSRQ)
Configure Event A2 Inter RAT Under Serving frequency HO profile
Configuration > BBU > Profiles > HO > Profile Event Intra Frequency > Event.
A2 Inter RAT
• Report Quantity
• Report Interval
• Report Amount
• Trigger Type
• Hysteresis
• Time To Trigger
• Event A2
• A2 Threshold (RSRP or RSRQ)

M-0110

4-26 240-00-0049
GERAN frequencies relevant for cell re-selection.

Configuration > BBU > Sector > SIB > SIB7 > General:
• Sector ID
• Period
• Period Scaling Medium
• Period Scaling High
Configuration > BBU > Sector > SIB > SIB7 > GeranCellReselectionParams:
• Sector ID
• NCC Permitted
• Reselection Min Rx
• Max TX Power UL
• Rx Threshold High
• Rx Threshold Low
• Cell Reselection Priority
• Starting ARFCN
• Band Indicator
M-0111
UTRA frequencies and UTRA neighboring cells relevant for cell re-selection.
Configuration > BBU > Sector > SIB > SIB6 > General:
• Sector ID
• Period
• Period Scaling Medium
• Period Scaling High
Configuration > BBU > Sector > SIB > SIB6 > UtranCellReselectionParams:
• Sector ID
• Duplex Mode
• Threshold High
• Threshold Low
• PMax UL Transmission
• Q Receive Level Minimum
• Q Quality Minimum

240-00-0049 4-27
• Cell Reselection Priority

Configuration > BBU > Sector > SIB > SIB6 > UTRAN Cell Reselection Threshold
Params:
• Sector ID
• Threshold High Qr9
• Threshold Low Qr9
M-0120 and S-0110
Configure GERAN Neighbor Table.
Configuration > BBU > Sector > Neighbor > General:
• Sector ID
• ARFCN
• Band
• NCC Permitted
• Event Inter Rat ID
Configure GERAN Neighbor Cell Item.
Configuration > BBU > Sector > Neighbor > GERAN > Neighbor Cell Item:
• Sector ID
• Starting ARFCN
• Band
• PLMN Identity
• LAC
• Cell ID
• ARFCN
• DTM HO Capable
• VOIP Capable
• DTM Capable
Configure Event B2 GERAN HO Profile
Configuration > BBU > Profiles > HO > Profile Event Inter RAT > Event B2
GERAN:

4-28 240-00-0049
• Report Interval
• Report Amount
• Trigger Type
• Hysteresis
• Time To Trigger
• Event B2
• B2 Threshold1 (RSRP or RSRQ)
• B2 Threshold2 GERAN
QuantityConfigGERAN
Configuration > BBU > Sector > L3 Common Meas Configuration > L3 Quantity
GERAN:
• Sector ID
• Quantity-GERAN-MEAS Quantity GERAN
• Quantity-GERAN-Filter Coefficient
M-0121 and S-0111
Configure UTRAN Neighbor Table.
Configuration > BBU > Sector > Neighbor > UTRAN:
• Sector ID
• ARFCN
• Duplex Mode
• Band
• Event Inter Rat ID
Configure UTRAN Neighbor Cell Item.
Configuration > BBU > Sector > Neighbor > UTRAN > Neighbor Cell Item:
• Sector ID
• ARFCN
• Duplex Mode
• Band
• PLMN Identity
• RNC ID
• Cell ID
• LAC
• RAC

240-00-0049 4-29
• PS HO Capable
• VOIP Capable
Configure Event B2 UTRAN HO Profile
Configuration > BBU > Profiles > HO > Profile Event Inter RAT > Event B2
UTRAN:
• Report Interval
• Report Amount
• Trigger Type
• Hysteresis
• Time To Trigger
• Event B2
• B2 Threshold1 (RSRP or RSRQ)
• B2 Threshold2 (RSCP or ECN0)
QuantityConfigUTRA
Configuration > BBU > Sector > L3 Common Meas Configuration > L3 Quantity
UTRAN:
• Sector ID
• Quantity-UTRA-MEAS Quantity UTRA FDD
• Quantity-UTRA-MEAS Quantity UTRA TDD
• Quantity-UTRA-Filter Coefficient

None

M-0120:
Outgoing IRAT Handover to GERAN:
• HOOUT.IratGeranPrepAttNbr
• HOOUT.IratGeranPrepSuccNbr
• HOOUT.IratGeranPrepCnclNbr
• HOOUT.IratGeranExecAttNbr
• HOOUT.IratGeranExecSuccNbr

4-30 240-00-0049
• HOOUT.IratGeranExecCnclNbr
• HOOUT.IratGeranExecOthrCnclNbr
• HOOUT.IratGeranPrepCnclNbr.Cause
• HOOUT.IratGeranExecCnclNbr.Cause
Incoming IRAT Handover from GERAN:
• HOINC.GeranEutranAttNbr
• HOINC.GeranEutranSuccNbr
IRAT HO to GERAN Per Target Stats:
• HOOUT.IratGeranPrepAttNbr
• HOOUT.IratGeranPrepSuccNbr
• HOOUT.IratGeranExecAttNbr
• HOOUT.IratGeranExecSuccNbr
S-0110:
SRVCC to GERAN counters:
• HOOUT.SrvccGeranPrepAttNbr
• HOOUT.SrvccGeranPrepSuccNbr
• HOOUT.SrvccGeranPrepCnclNbr
• HOOUT.SrvccGeranExecAttNbr
• HOOUT.SrvccGeranExecSuccNbr
• HOOUT.SrvccGeranExecCnclNbr
• HOOUT.SrvccGeranExecOthrCnclNbr
• HOOUT.SrvccGeranPrepCnclNbr.Cause
• HOOUT.SrvccGeranExecCnclNbr.Cause
SRVCC to GERAN Per Target Stats:
• HOOUT.SrvccGeranPrepAttNbr
• HOOUT.SrvccGeranPrepSuccNbr
• HOOUT.SrvccGeranExecAttNbr
• HOOUT.SrvccGeranExecSuccNbr
M-0121:
Outgoing IRAT Handover to UTRAN:
• HOOUT.IratUtranPrepAttNbr
• HOOUT.IratUtranPrepSuccNbr
• HOOUT.IratUtranPrepCnclNbr
• HOOUT.IratUtranExecAttNbr

240-00-0049 4-31
• HOOUT.IratUtranExecSuccNbr
• HOOUT.IratUtranExecCnclNbr
• HOOUT.IratUtranExecOthrCnclNbr
• HOOUT.IratUtranPrepCnclNbr.Cause
• HOOUT.IratUtranExecCnclNbr.Cause
Incoming IRAT Handover from UTRAN:
• HOINC.UtranEutranAttNbr
• HOINC.UtranEutranSuccNbr
IRAT HO to UTRAN Per Target Stats:
• HOOUT.IratUtranPrepAttNbr
• HOOUT.IratUtranPrepSuccNbr
• HOOUT.IratUtranExecAttNbr
• HOOUT.IratUtranExecSuccNbr
S-0111:
SRVCC to UTRAN counters:
• HOOUT.SrvccUtranPrepSuccNbr
• HOOUT.SrvccUtranPrepCnclNbr
• HOOUT.SrvccUtranExecAttNbr
• HOOUT.SrvccUtranExecSuccNbr
• HOOUT.SrvccUtranExecCnclNbr
• HOOUT.SrvccUtranExecOthrCnclNbr
• HOOUT.SrvccUtranPrepCnclNbr.Cause
• HOOUT.SrvccUtranExecCnclNbr.Cause
SRVCC to UTRAN Per Target Stats:
• HOOUT.SrvccUtranExecAttNbr
• HOOUT.SrvccUtranExecSuccNbr

M-0120: IRAT Handover to GERAN KPI
• HoOutIratGeranPrepSuccRatio

4-32 240-00-0049
Features related to IRC PUSCH and Receiver v1.5 Software Features Description
• HoOutIratGeranExecSuccRatio
• HoOutIratGeranTotalSuccRatio
S-0110: SRVCC to GERAN KPI
• HoOutSrvccGeranPrepSuccRatio
• HoOutSrvccGeranExecSuccRatio
• HoOutSrvccGeranTotalSuccRatio
M-0121: IRAT Handover to UTRAN KPI
• HoOutIratUtranPrepSuccRatio
• HoOutIratUtranExecSuccRatio
• HoOutIratUtranTotalSuccRatio
S-0111: SRVCC to UTRAN KPI
• HoOutSrvccUtranPrepSuccRatio
• HoOutSrvccUtranExecSuccRatio
• HoOutSrvccUtranTotalSuccRatio
4.6 Features related to IRC PUSCH and Receiver

For the feature information, refer to Table 4-6 Feature Information - IRC PUSCH
and Receiver on page 4-33.
Table 4-6 Feature Information - IRC PUSCH and Receiver
P-0110 Dynamic or Advance Receiver
P-0075 2-way IRC PUSCH
P-0071 4-way IRC PUSCH
4.6.2 Description
Interference Rejection and Cancellation (IRC) uses MIMO techniques to remove
interference from the Uplink signal. This results in improved SINR and better
PUSCH reception. Since interference can be due to complete and partial overlap in
the frequency domain, our advanced receiver is sensitive to this and applies IRC in
a frequency selective manner for optimal throughput in both interference and noise
limited scenarios.

240-00-0049 4-33
v1.5 Software Features Description Features related to IRC PUSCH and Receiver
4.6.3 Benefits
IRC allows increased uplink throughput with lower transmit power at the UE for cell
edge users. The Advanced Receiver design leverages multiple receiver types to
give optimum Uplink throughput under a variety of channel conditions.
4.6.4 Dependencies
None
4.6.5 Performance Curves

For information on the performance curves, refer to the following sections:
The results in Table 4-7 4Rx Performance Scenario for EPA5 on page 4-34
through Table 4-10 2Rx Performance Scenario on page 4-36 are the system
NOTE performance on 20 MHz and 6 PUCCH PRBs, with SRS disabled.
4Rx Performance
For scenarios on 4Rx Performance, refer to the following tables:
• Table 4-7 4Rx Performance Scenario for EPA5 on page 4-34
• Table 4-8 4Rx Performance Scenario for EVA5 on page 4-35
• Table 4-9 4Rx Performance Scenario for ETU70 on page 4-35
Scenario: Interference: 18dBm/tone; Fading model: EPA5
Table 4-7 4Rx Performance Scenario for EPA5
IRC_Disabled (UL Throughput in IRC_Enabled (UL Throughput in

EPA5
Mbps) Mbps)
With Without With With

RSRP (dBm)
Interferenc Interference Interference Interference
-102 2.25 37.5 18.5 37
-105 0.85 30.9 10.5 31
-108 0.45 24 7.5 24.5
-111 0.2 17 3.8 16.5
-114 0.15 10.5 1.8 10.2
-117 0.08 6 0.6 5.5
-120 0.02 3.3 0.22 3.42

4-34 240-00-0049
Table 4-7 4Rx Performance Scenario for EPA5

EPA5
Mbps) Mbps)

RSRP (dBm)
-123 NO data 1.5 NO data 1.75
-126 NO data 1 NO data 0.9
Scenario: Interference: 18 dBm/tone; Fading model: EVA5
Table 4-8 4Rx Performance Scenario for EVA5

EVA5
Mbps) Mbps)

RSRP (dBm)
-102 1.7 36.8 13.1 36.9
-105 0.8 30.3 7.8 28.5
-108 0.25 20.4 4.8 19.7
-111 0.16 14 3.2 12.8
-114 0.09 4.5 1 7.6
-117 0.035 4.5 0.2 4.2
-120 0.011 2.8 0.16 2.4
-123 No data 1.5 0.12 1.2
-126 No data 0.45 No Data 0.4
Scenario: Interference: 18 dBm/tone; Fading Model: ETU70
Table 4-9 4Rx Performance Scenario for ETU70

ETU70
Mbps) Mbps)

RSRP (dBm)
-102 1.63 35.5 5 33.3

240-00-0049 4-35
v1.5 Software Features Description Features related to IRC PUSCH and Receiver
Table 4-9 4Rx Performance Scenario for ETU70

ETU70
Mbps) Mbps)

RSRP (dBm)
-105 0.8 28.5 2.5 26.1
-108 0.36 16 1.1 16.5
-111 0.13 8.2 0.56 10.1
-114 0.085 5.4 0.2 5.4
-117 0.03 2.9 0.08 2.8
-120 No data 1.3 0.045 1.3
-123 No data 0.69 0.03 0.68
-126 No data 0.25 No data 0.3
2Rx Performance
For scenario on 2Rx Performance, refer to Table 4-10 2Rx Performance Scenario on
page 4-36.
Table 4-10 2Rx Performance Scenario
IRC_Disabled IRC_Enabled
UL
Interfere UE TX Power UL Throughput
Throughput UE TX Power (dBm)
nce(dBm (dBm) (Mbps)
(Mbps)
-20 13.5 17 14.3 17
-15 13 17 13.5 17
-10 12 17 12.5 17
5 8.6 18 12 17
0 5.2 20 8.5 17
5 2.8 20 6.3 17
10 0.7 20 5.3 17
15 0.4 21 3.8 17

4-36 240-00-0049
Table 4-10 2Rx Performance Scenario
IRC_Disabled IRC_Enabled
UL
Interfere UE TX Power UL Throughput
Throughput UE TX Power (dBm)
nce(dBm (dBm) (Mbps)
(Mbps)
20 0.1 21 1.5 17

These features are grouped under the Performance function.

None

By default IRC is enabled in config.xml through advanced-receiver-support
parameter.

To disable IRC, advanced-receiver-support has to be disabled in config.xml.

Advanced-receiver-support is used to enable/disable this feature.

None

None

Improved uplink throughput and lower transmit power at the UE for cell edge
users.

240-00-0049 4-37
v1.5 Software Features Description UL FSS
4.7 UL FSS

For the feature information, refer to Table 4-11 Feature Information- UL FSS on
page 4-38.
Table 4-11 Feature Information- UL FSS
P-0250 UL FSS
4.7.2 Description
In LTE Uplink, cell-edge users are power-limited. Total transmission power of the
user needs to be spread across their entire resource allocation. In case of heavy
path-loss, only few resource blocks is allocated for reliable communication during
each scheduling instance. Therefore, it is very important to schedule cell-edge
users on the best possible resources of the user.
Single Carrier-Frequency Division Multiple Access mandates that resources
allocated are contiguous. In other words, finding the best resource blocks for each
user is NP-hard problem. Altiostar’s Frequency Selective Scheduling solution
provides low-complexity resource allocation in the Uplink.
4.7.3 Benefits
The Altiostar algorithm is invariant to the number of scheduling-eligible users. As a
result, there are no concerns with solution’s scalability. The algorithm exploits the
principle of multi-user diversity. As the number of users in the system increase,
performance will be near-optimal spectral efficiency.
4.7.4 Dependencies
Sounding Reference Signal (SRS) feature needs to be turned on.

This feature is grouped under the following major functions:
• Performance
• Uplink scheduler enhancements

4-38 240-00-0049
UL FSS v1.5 Software Features Description

For information on the functional diagrams/flowchart, refer to Figure 4-2 Ordered
channel quality report for each user across resource blocks on page 4-39 and
Figure 4-3 Maximizes spectral efficiency on page 4-39.
Figure 4-2 Ordered channel quality report for each user across resource
blocks
Resource Allocation with preference order of individual UEs
Figure 4-3 Maximizes spectral efficiency

UL FSS is activated by licensing the feature and then configuring it in EMS. This
assumes the dependent feature (SRS) is licensed and activated.

Can be deactivated from EMS.

None. Only the feature flag which can be turned on/off from EMS.

None

None

None

240-00-0049 4-39
v1.5 Software Features Description Features related to RoHC, TTI and
4.8 Features related to RoHC, TTI and Scheduling

For the feature information, refer to Table 4-12 Feature Information - RoHC, TTI
and Scheduling on page 4-40.
Table 4-12 Feature Information - RoHC, TTI and Scheduling
S-0080 RoHC for VoIP
S-0090 TTI Bundling
P-0080 Semi-Persistent Scheduling
4.8.2 Description
These three features are applicable for VoIP and are interrelated.
• Robust Header Compression (ROHC): 3GPP has included ROHC in PDCP
functionality in order to reduce this overhead. ROHC transmitter compresses
the RTP/UDP/IP header such that the fields which are unchanging are not
transmitted. ROHC receiver decompresses the packet to its original state.
Compressor starts with Initialization and Refresh (IR) state and as the
compression increases, it moves to First Order (FO) and Second Order (SO)
states.
• TTI Bundling: This UL feature is useful when the system is UL power limited.
For example, in a Macro eNodeB deployment. In TTI bundling, eNodeB assigns
four consecutive PUSCH transmissions for the same transport block. HARQ
benefits of the four transmissions increases the UL coverage for the cell edge
UEs. We use this feature only for UEs with QCI-1 bearer.
• Semi-persistent Scheduling (SPS): SPS is used only for UEs with QCI-1
bearers. In this feature, UEs is assigned a fixed DL or UL assignment with a
fixed period. This feature is useful for VoIP calls where packets are generated
periodically by the codec.
4.8.3 Benefits
The benefits for the three features are as follows:
• ROHC: This feature reduces the VoIP packet size significantly by compressing
the UDP/IP (or TCP/IP) headers. This means that a much smaller transport
block is needed to transmit the packet. This can result in higher VoIP capacity
and higher VoIP coverage.
• TTI Bundling: This feature can improve the VoIP coverage. Typical HARQ
gains seen by the cell edge UEs are 3-4 dB with 6 dB being the theoretical limit.

4-40 240-00-0049
Features related to RoHC, TTI and v1.5 Software Features Description
• SPS: This feature reduces the PDCCH utilization since a fixed PRB allocation is
assigned to the UE. This can significantly increase the VoIP capacity in the
system since a typical VoLTE deployment is PDCCH limited.
4.8.4 Dependencies
There are no dependencies on other features; however these features are used
only for QCI-1 bearer.

The three features are grouped under the following major functions:
• VoLTE
• Performance
• Services

None

ROHC and SPS can be activated by licensing the feature and then configuring it in
EMS. While TTI bundling requires licensing the feature, configuring it in EMS and is
activated if a UE’s UL channel condition is too poor to sustain a VoIP call.

All the features can be deactivated from EMS.

The parameters related to the feature are listed below:
• DB: SpsDefaultTbs
• DB: SpsCceAggregationLevel
• DB: SpsdlSinrMargin
• DB: SpsPrbPartition
• DB: SpsModificationPerMultiplication
• DB: semiPersistSchedIntervalDL
• DB: semiPersistSchedIntervalUL
• DB: SpsModIncThresh
• DB: SpsModDecThresh
• DB: SpsulSinrMargin

240-00-0049 4-41
v1.5 Software Features Description Features related to SR-VCC LTE
• DB: SpsEnable
• DB: SpsMissedThresh
• DB: SpsDefaultMcsIndex
• DB: numberOfConfSPS-Processes
• DB: implicitReleaseAfter
• DB: p0-NominalPUSCH-Persistent
• DB: p0-UE-PUSCH-Persistent
• DB:TtiBundlingThresh
• DB:TtiBundlingEnable
• DB:TtiBundlingTimeHyst
• DB:TtiBundlingPRB

None

None

None
4.9 Features related to SR-VCC LTE

For the feature information, refer to Table 4-13 Feature Information - SR-VCC LTE
on page 4-42.
Table 4-13 Feature Information - SR-VCC LTE
S-0110 SR-VCC LTE – GERAN
S-0111 SR-VCC LTE – UTRAN
4.9.2 Description
The SR-VCC feature allows a VoLTE call, that is in the packet domain to be handed
over to a legacy network like GERAN/UTRAN that is in a circuit switch domain
seamlessly.

4-42 240-00-0049
Features related to SR-VCC LTE v1.5 Software Features Description
4.9.3 Benefits
This feature allows the seamless mobility by utilizing legacy networks such as
GERAN/UTRAN. This ensures voice call continuity in areas where VoLTE capabilities
are not available.
4.9.4 Dependencies
None

The features are grouped under the Services function.

None

None

None

None

None

None

None

240-00-0049 4-43
v1.5 Software Features Description Features related to IPsec
4.10 Features related to IPsec

For the feature information, refer to Table 4-14 Feature information - IPsec on
page 4-44.
Table 4-14 Feature information - IPsec
T-0040 IPsec for S1
T-0041 IPsec for X2
T-0042 IPsec for FH
4.10.2 Description
IPsec for S1, X2 and Fronthaul provide secure channel for transferring Backhaul
and Fronthaul traffic. IPsec provides security at network layer with transport or
tunnel mode facilities. The tunnel mode configuration is used for securing the
traffic. Along with security, the IPsec authenticates its peer using pre-shared key.
4.10.3 Benefits
The benefits of the features are as follows:
• Allows traffic originated towards BH, X2 and Fronthaul interfaces are secured
using standard protocols.
• Authenticates peers using Pre-Shared key
4.10.4 Dependencies
None

The features are grouped under the Transport - Security function.

4-44 240-00-0049
Features related to IPsec v1.5 Software Features Description

For information on the functional diagrams/flowchart, refer to Figure 4-4 Backhaul
IP Security on page 4-45 and Figure 4-5 Fronthaul IP Security on page 4-45.
Figure 4-4 Backhaul IP Security
Figure 4-5 Fronthaul IP Security

• IPsec for S1 and X2 can be activated using the bh-ipsec flag present in the
config.xml or from EMS.
• IPsec for Fronthaul can be activated using the fh-ipsec flag present in the

• IPsec for S1 and X2 can be deactivated using the bh-ipsec flag present in the
• IPsec for Fronthaul can be deactivated using the fh-ipsec flag present in the

240-00-0049 4-45

The new parameters defined for configuring IPsec are listed in the table below.
Refer to Table 4-15 Parameters defined for IPsec on page 4-46.
Table 4-15 Parameters defined for IPsec
Mandatory
Parameter (M)/ Type Description Allowed values
Optional (O)
bh–ipsec O (default: Enumeration Flag to (disabled, enabled)

disabled) enable/
disable
Backhaul
IPsec
x2-ipsec O (default: Enumeration Flag to (disabled, enabled)

disabled) enable/
disable X2
IPsec
fh-ipsec O (default: Enumeration Flag to (disabled, enabled)

disabled) enable/
disable
Fronthaul
IPsec
IkeName M String Name Max length of 255 characters

describing Ike
connection
local_addrs M String Describes the IPv4/IPv6 addresses, DNS

local (source) names, CIDR subnets or IP
outer IPs address ranges
remote_add M IP Address or Describes the IPv4/IPv6 addresses, DNS

rs List of IP remote names, CIDR subnets or IP
addresses (destination) address ranges
outer IPs
auth_type O (default: Enumeration Describes (psk, pubkey)

psk) authentication
type

4-46 240-00-0049
Mandatory
Optional (O)
authId M String Describes the Possible values are:

identity to be
• IP address
used for
IKEv2 • Or O=Altiostar,
CN=vBBU
• Or vbbu.altiostar.com
Can be an IP address, a
fully-qualified domain name,
an email address or a
Distinguished Name for
which the ID type is
determined automatically.
Certs O String Describes the Max length of 255 characters

certificate file
(absolute path or relative
name
paths from swanctl directory
should be allowed)
Version O (default: Enumeration Describes the (unknown, ikev1, ikev2)

ikev2) Ike protocol
version
Reauth time O (default: Range of Describes the Xu = > X is INTGER(1.59)

uses third values Re
u is unit (s or m or h)
party authentication
software time. Possible values are:
provided
• 10m = > 10 minutes
values)
• 10h = > 10 hour
• 10s = > 10 seconds
IKE rekey O (default: Range of Describes the Xu = > X is INTGER(1.59)

time uses third values IKE rekey
party time.
software Possible values are:
provided
values)
• 10h = > 10 hour

240-00-0049 4-47
Mandatory
Optional (O)
IKE M Combination Describes the ENC-INT-DG =>

proposals of lists encryption,
ENC is (null , aes_cbc , 3des)
authentication
and DH group INT is (hmac_sha1,
for IKE SA aes_xcbc, md5)
DG is (1024, 2048)
The list mentioned above
may get updated if any
additional algorithm needs to
be supported.
dpdaction O (default: Enumeration Describes the (none, clear, hold, restart)

uses third action to be
party taken after
software peer is
provided detected as
values) dead
dpddelay O (default: Range of Describes the Xu = > X is INTGER(1.59)

uses third Values dpd period
party time interval
software to exchange Possible values are:
provided keep alive
values) messages
• 10h = > 10 hour
dpdtimeout O (default: Range of Describes the Xu = > X is INTGER(1.59)

uses third Values timeout
party interval after
software which all Possible values are:
provided connections
values) to peer are
deleted in • 10h = > 10 hour
case of • 10s = > 10 seconds
inactivity
Child name M String Name Max length of 255 characters

describing the
child

4-48 240-00-0049
Mandatory
Optional (O)
local_ts and M String Comma Each selector is a IP4/IPv6/

remote_ts separated list CIDR subnet definition,
of local traffic followed by an optional
selectors to proto/port selector.
include in
For example:
CHILD_SA.
• 10.0.0.1[tcp/http],
10.0.0.2[6/80]
• fec1::1[udp],10.0.0.0/
16[/53]
• fec1::1[udp/
%any],10.0.0.0/
16[%any/53]
• %any
Child rekey O (default: Range of Describes Xu = > X is INTGER(1.59)

time uses third Values child SA rekey
party time
software Possible values are:
provided
values)
• 10h = > 10 hour
ESP M if ESP is Combination Describes ENC-INT-DG =>

proposals selected as of lists child SA
ENC is (null, aes_cbc, 3des)
IPsec proposals
protocol using ESP INT is (hmac_sha1,
protocol aes_xcbc, md5)
DG is (1024, 2048)
be supported.

240-00-0049 4-49
v1.5 Software Features Description Default Bearer Differentiated Flow Treatment
Mandatory
Optional (O)
ah proposals M if AH is Combination Describes ENC-INT-DG =>

selected as of lists child SA
ENC is (null, aes_cbc, 3des)
IPsec proposals
protocol using AH INT is (hmac_sha1,
protocol aes_xcbc, md5)
DG is (1024, 2048)
be supported.

None

None

None
4.11 Default Bearer Differentiated Flow Treatment

For the feature information, refer to Table 4-16 Feature Information - Default
Bearer Differentiated Flow Treatment on page 4-50.
Table 4-16 Feature Information - Default Bearer Differentiated Flow

Treatment
V-0110 Default Bearer Differentiated Flow Treatment –

More Reliable Delivery
4.11.2 Description
AI module will be tagging PDUs which is sent fail safe in a given logical channel.
L2 is required to send these PDUs with an assertive scheduling MCS, to improve

4-50 240-00-0049
Default Bearer Differentiated Flow Treatment v1.5 Software Features Description
the chances of these PDUs being decoded by UE, thereby ensuring a more reliable
delivery.
4.11.3 Benefits
A more reliable delivery of the tagged PDUs is ensured, thereby increasing the
quality of experience for the end user.
4.11.4 Dependencies
None

The feature is grouped under the AI function.

None

Through configuration.

Through configuration.

Existing Parameters:
• Rule Category of type bearer-opt-tcp, and action schedule-assertive.
• ConfigAppint::DiffUserGroupAI::bearer-opt-tcp-rule-name.
New Parameters:
• ConfENB::l2::assertive-scheduling-mcs: This is the MCS at which all
assertive tagged PDUs will be transmitted.
• ConfENB::l2::assertive-scheduling-agg: This is the CCE aggregation level of
all DCIs carrying information about Assertive Scheduled PDUs.

None

None

240-00-0049 4-51
v1.5 Software Features Description Video Pacing for MP4/FLV decoder

None
4.12 Video Pacing for MP4/FLV decoder

For the feature information, refer to Table 4-17 Feature Information - Video
Pacing for MP4/FLV decoder on page 4-52.
Table 4-17 Feature Information - Video Pacing for MP4/FLV decoder
V-0140 Video Pacing for MP4/FLV decoder
4.12.2 Description
This feature calculates the required bandwidth for a video, and then throttles or
prioritizes a flow based on traffic conditions on that bearer to provide the required
bandwidth to MP4 and FLV videos.
4.12.3 Benefits
If more bandwidth is available for the flow, the flow is throttled to save radio
resources without affecting the user experience.
If less bandwidth is available for the flow, other flows will be throttled to prioritize
this flow, thus preventing video stalls and improving the user experience.
4.12.4 Dependencies
Refer to the following dependencies:
• The DPI Enable flag needs to be enabled in the DUG configuration.
• TCP RWND Adaption needs to be enabled.
• Default Bearer Differentiated Flow Treatment needs to be enabled.

The feature is grouped under the AI function.

None

4-52 240-00-0049
Automatic Neighbor Relations v1.5 Software Features Description

In the EMS GUI, enable BBU > App Int > Diff User Group > Video Bandwidth
Detection Enable.

In the EMS GUI, disable BBU > App Int > Diff User Group > Video Bandwidth
Detection Enable.

The parameter related to this feature is BBU > App Int > Diff User Group > Video
Bandwidth Detection Enable.

None

None

None
4.13 Automatic Neighbor Relations

For the feature information, refer to Table 4-18 Feature Information - Automatic
Neighbor Relations on page 4-53.
Table 4-18 Feature Information - Automatic Neighbor Relations
O-0020 Automatic Neighbor Relations
4.13.2 Description
The ANR function residing in the eNodeB manages the Neighbor Relation Table
(NRT). The neighbor detection function located within ANR, discovers new
neighbors and X2 relations and adds them to NRT through X2 messages and UE
measurement reports received in the eNodeB. The neighbor removal function
deletes unused/idle neighbor relations.

240-00-0049 4-53
v1.5 Software Features Description Automatic Neighbor Relations
4.13.3 Benefits
• Reduces operator intervention in maintaining neighbor relations.
• eNodeB automatically configures and maintains its neighbor relations.
• Aging allows to remove unused or idle neighbors. The idle time is
configurable based on user requirement.
4.13.4 Dependencies
ANR has dependencies on the following features:
• Long DRX support to read the E-UTRAN Cell Global Identifier (ECGI) of the
neighbor.
• X2 support to detect new neighbor through X2 messages.

This feature is grouped under eNodeB SON functionality.

For information on the functional diagrams/flowchart, refer to the following
figures from the 3GPP TS 36.300 version 9.9.0 Release 9 document:
• Figure 22.3.2a-1: Interaction between eNB and O&M due to ANR.
• Figure 22.3.3-1: Automatic Neighbor Relation Function.

ANR is activated by licensing the feature and then configuring it in EMS.
• Static ANR: Set Configuration > Configuration Explorer > BBU > Sector >
SON > ANR > Enable State to enabled.
• Dynamic ANR: Set Configuration > Configuration Explorer > BBU > Sector >
SON > ANR > Dynamic ANR to enabled.
• Ageing: Set Configuration > Configuration Explorer > BBU > Sector > SON
> ANR > Aging Timeout to any non-zero value between 1 to 21600 minutes.

• Static ANR: Set Configuration > Configuration Explorer > BBU > Sector >
SON > ANR > Enable State to disabled.
• Dynamic ANR: Set Configuration > Configuration Explorer > BBU > Sector >
SON > ANR > Dynamic ANR to disabled.

4-54 240-00-0049
Automatic Neighbor Relations v1.5 Software Features Description
• Ageing: Set Configuration > Configuration Explorer > BBU > Sector > SON
> ANR > Aging Timeout to 0.

For details on parameters defined for configuring SON ANR, refer to Table 4-19
Parameters Information - Automatic Neighbor Relations on page 4-55.
Table 4-19 Parameters Information - Automatic Neighbor Relations
Mandatory
Optional (O)
enable-state M Enumerated Flag to enable/disable disabled,

Static ANR.
(default: enabled
disabled)
dynamic-anr M Enumerated Flag to enable/disable disabled,

Dynamic ANR.
(default: enabled
disabled)
aging- M UInteger16 Aging timeout value in 0 to 21600

timeout minutes.
(default: 0)

None

The following counters are maintained per frequency at SON ANR:
• ANR.nbr-added-count - Number of neighbors added by ANR.
• ANR.no-of-nbr-reported - Number of neighbors detected by UE reports.
• ANR.no-of-nbr-resolved - Number of neighbors resolved from UE reports.
• ANR.no-of-nbr-accept-pending - Number of detected neighbors accept
pending from OAM.
• ANR.nbr-deleted-count - Number of neighbors deleted by ANR Aging.

None

240-00-0049 4-55
v1.5 Software Features Description Physical Cell Identity conflict detection
4.13.13 Licensing requirement:

ANR is activated by enabling the feature in the license.
4.14 Physical Cell Identity conflict detection

For the feature information, refer to Table 4-20 Feature Information - Physical
Cell Identity conflict detection on page 4-56.
Table 4-20 Feature Information - Physical Cell Identity conflict detection
O-0031 Physical Cell Identity conflict detection
4.14.2 Description
PCID conflicts are identified from X2 messages and UE measurement reports and
then reported to EMS. EMS can use such PCID conflict notifications to change the
PCID of one of those sites to avoid handover (HO) failures. Changing of PCID
values has to be done manually as of now.
4.14.2.1 Enabling HO in case of PCID confusion

In case of PCID confusion being present in the neighbor relation table for a
PCID (either configured or discovered), and if a HO is triggered to that PCID,
this feature helps in choosing the correct target by resolving the PCID and
getting the correct ECGI, just before the HO is triggered.
4.14.3 Benefits
• Detection and reporting of PCID Conflicts helps in taking action to avoid HO
failures.
• Helps UE in choosing the correct target if a PCID confusion is present in the
neighbor relation table.
4.14.4 Dependencies
PCID conflicts detection has dependencies on the following features:
• Long DRX support to read the E-UTRAN Cell Global Identifier (ECGI) of the
neighbor.
• X2 support to get adjacent neighbor information.

4-56 240-00-0049
Physical Cell Identity conflict detection v1.5 Software Features Description


None

PCI Conflict Detection is activated by licensing the feature and then configuring it
in EMS.
PCI Conflict Detection: Set Configuration > Configuration Explorer > BBU >
Sector > SON > PCI > Enable State to enabled.

PCI Conflict Detection: Set Configuration > Configuration Explorer > BBU >
Sector > SON > PCI > Enable State to disabled.

For details on parameters defined for configuring SON PCI Conflict Detection,
refer to Table 4-21 Parameters Information - PCI Conflict Detection on
page 4-57.
Table 4-21 Parameters Information - PCI Conflict Detection
Mandatory
Optional (O)
enable-state M Enumerated Flag to enable/disable PCI disabled,

conflict detection.
(default: enabled
disabled)
periodicityForP M UInteger32 Periodicity for resolving 60 to 1296000

CIDResolution neighbors to detect PCI
(default:
conflicts.
3600)
maxPCIDResolu M UInteger8 Max no of resolutions done 1 to10

tionsPerNbr for each neighbor in a
(default: 3)
resolution period.

240-00-0049 4-57
v1.5 Software Features Description Mobility Robustness Optimization

None

The following counters are maintained per sector at SON PCI periodically.
• PCI.totalConflicts - Total number of conflicts found in a resolution period.
• PCI.last-seen-new-conflict - Time of last seen new conflict.
• PCI.totalNoOfConflictingReports - Total number of conflicting ECGI reports
received in a resolution period.
• PCI.totalNoOfReportsRecd - Total number of UE reports forwarded to SON
PCI.
• PCI.totalRequestsMadeForCGI - Total number of times ECGI is requested to
UEs by SON PCI in a resolution period.
• PCI.noOfNbrsShortOfRequiredUEs - Count of neighbors that did not get
enough UE reports to resolve themselves.
• PCI.avgUEsShortPerNbr - Average number of UE reports that each of the
neighbor was short of for resolving.
The following counters are maintained per each conflicted neighbor at SON PCI.
• NBRCONFLICT.totalConflicts - Total Number of Conflicts found for the
neighbor.
• NBRCONFLICT.last-seen - Last seen conflict time for the neighbor.

None
4.14.13 Licensing requirement

PCID Conflict detection is activated by enabling the feature in the license.
4.15 Mobility Robustness Optimization

For the feature information, refer to Table 4-22 Feature Information - Mobility
Robustness Optimization on page 4-58.
Table 4-22 Feature Information - Mobility Robustness Optimization
O-0040 Mobility Robustness Optimization

4-58 240-00-0049
Mobility Robustness Optimization v1.5 Software Features Description
4.15.2 Description
Mobility robustness optimization (MRO) evaluates HO failures, identifies the root
cause, and makes corrections automatically. MRO algorithms run on individual
eNodeBs using data gathered from neighbor nodes. The EMS monitors and
reports on the statistics generated.
MRO is a solution for automatic detection and correction of errors in the mobility
parameters configuration. The focus is on errors which cause Radio link failures
(RLF) due to:
• Too late handover
• Too early handover
• Handover to an incorrect cell.
In the case of a too late handover, the handover procedure in the source cell is
initialized too late, since the UE is moving faster than the Handover (HO)
parameter settings allow. Hence when the RRC HO command from the serving
cell is transmitted the signal strength is too weak to reach the UE, which is now
located in the target cell, so the connection is lost. The UE attempts a connection
re-establishment, containing the PCID and C-RNTI belonging to the source cell,
but received by the target cell. The target eNB will then inform the source cell
about RLF to adjust Handover parameters.
To detect a too early handover is complicated. The UE has successfully been
handed over from the source cell to the target cell, but since it was triggered too
early the connection will drop almost immediately due to poor radio conditions in
the target cell. The UE will then try to re-establish the connection, which will now
take place in the original source cell, cell, since this cell is the strongest one. The
UE will use the PCID and RNTI from the target cell and the source cell will then
consider this as a Radio Link Failure due to too late handover and send an
indication to the target cell. But the target cell will now recognize the parameters
in the indication, as given to a mobile that had just completed a handover to the
target cell from the source cell now indicating failure. The target cell will send
back a report about too early Handover to adjust Handover parameters, to the
source cell.
4.15.3 Benefits
• Self-optimization of HO parameters by eNodeB.
• Improve HO operations within the network.
• Provides an enhanced end-user experience and improved network capacity.
4.15.4 Dependencies
None

240-00-0049 4-59


None

MRO is activated by licensing the feature and then configuring it in EMS.
SON MRO: Set Configuration > Configuration Explorer > BBU > Sector > SON >
MRO > Enable State to enabled.

SON MRO: Set Configuration > Configuration Explorer > BBU > Sector > SON >
MRO > Enable State to disabled.

For details on parameters defined for configuring Mobility Robustness
Optimization, refer to Table 4-23 Parameters Information - Mobility Robustness
Optimization on page 4-60.
Table 4-23 Parameters Information - Mobility Robustness Optimization
Mandatory (M)/
Parameter Type Description Allowed values
Optional (O)
enable-state M Enumerated Flag to enable/disable disabled,

SON MRO. enabled
(default: disabled)
ho-fail- M UInteger8 HO failure + Pingpong 1 to 100

pingpong- HO rate threshold.
(default: 10)
thresh
ho-fail- M UInteger16 Minimum count of (HO 1 to1000

pingpong- failures + Pingpong
(default: 10)
sample- HOs) in a monitoring
threshold period to be considered
for action.
ho-rlf-fail- M Real Weightage to be 0 to 1.0

weigth considered for HO RLF
(default: 0.5)
failures.

4-60 240-00-0049
Mobility Robustness Optimization v1.5 Software Features Description
Table 4-23 Parameters Information - Mobility Robustness Optimization (continued)
Mandatory (M)/
Parameter Type Description Allowed values
Optional (O)
ho-pingpong- M Real Weightage to be 0 to 1.0

weigth considered for Pingpong
(default: 0.5)
handovers.
data-coll-period M UInteger16 Monitoring period for 60 to 3600

collecting HO failures.
(default: 120)
corr-action- M UInteger8 MRO action is taken 1 to 100

period- after 'corr-action-
(default: 4)
multiplier period-multiplier'
monitoring periods.
min-cio- M Q-OffsetRange The minimum CIO value dB-24 to dB24

allowed-mro below which MRO is not
(default: dB-6)
allowed to change the
CIO value.
max-cio- M Q-OffsetRange The maximum CIO dB-24 to dB24

allowed-mro value up to which MRO
(default: dB6)
is allowed to change the
CIO value.
mro-ping- M UInteger16 The minimum total 1 to 600

pong-period amount of time the UE
(default: 15)
should spend in serving
and target cells
combined to be
considered as Pingpong
HO.
mro-ue- M UInteger16 The amount of time 1 to 1200

connected- beyond which any RLF
(default: 60)
period report from the UE will
be ignored immediately
after the re-
establishment
procedure.

The following parameter is modified during MRO Action, if required, to improve
HO success rate:
Configuration Explorer > BBU > Sector > Neighbor > EUTRAN > NBR Cell Item
> Cell Individual Offset

240-00-0049 4-61

The following counters are maintained per neighbor at SON MRO:
• MRONBR.tot-ho-attempts - Total number of Handover attempts towards the
neighbor.
• MRONBR.tot-ho-fails - Total number of Handover failures towards the
neighbor.
• MRONBR.ho-fail-too-early - Total number of Too Early Handover failures
towards the neighbor.
• MRONBR.ho-fail-too-late - Total number of Too Late Handover failures
towards the neighbor.
• MRONBR.ho-fail-wcell-wtarget- Total number of WrongCell Wrong Target
Handover failures towards the neighbor.
• MRONBR.ho-fail-wcell-ctarget- Total number of WrongCell Correct Target
Handover failures towards the neighbor.
• MRONBR.ho-ping-pong- Total number of Pingpong Handovers towards the
neighbor.

None
4.15.13 Licensing requirement

MRO is activated by enabling the feature in the license.

4-62 240-00-0049
Software Features Description
Issue 3
240-00-0049
Copyright © 2016 Altiostar Networks, Inc.

Feature Description Guide

Uploaded by

Document Information

Original Title

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

Feature Description Guide

Uploaded by

Copyright:

Available Formats

Software Features Description

Copyright © 2016 Altiostar Networks, Inc.

The Altiostar logo is a trademark and a service mark of Altiostar.

Questions: Please call Altiostar General Information at +1-855-709-0701.

Issue 3 Altiostar Software Features Description

P.1 About the document

P.2 Intended users

Software Features Description Altiostar Issue 3

Issue 3 Altiostar Software Features Description

Software Features Description Altiostar Issue 3

3.3.6 Functional Diagrams/Flowcharts ............................................................. 3-10

Issue 3 Altiostar Software Features Description

4.1.9 Parameters related to the feature ............................................................. 4-3

Software Features Description Altiostar Issue 3

4.5 Features related to IRAT and SR-VCC ..................................................... 4-24

Issue 3 Altiostar Software Features Description

4.8.2 Description .......................................................................................... 4-40

Software Features Description Altiostar Issue 3

4.11.6 Functional Diagrams/Flowcharts............................................................ 4-51

Issue 3 Altiostar Software Features Description

4.14.8 Deactivation procedure ........................................................................ 4-57

Software Features Description Altiostar Issue 3

Issue 3 Altiostar Software Features Description

Figure 3-1 CA Functional Flow ................................................................................ 3-6

Software Features Description Altiostar Issue 3

Issue 3 Altiostar Software Features Description

Table 1-1 What’s new in Issue 3 .............................................................................. 1-1

Software Features Description Altiostar Issue 3

Issue 3 Altiostar Software Features Description

1.1 What’s new in Issue 3

Table 1-1 What’s new in Issue 3

Feature/enhancement Description Refer to

v2.0 Software Added information about v2.0 Chapter 3 - v2.0 Software

1.2 What’s new in Issue 2

Table 1-2 What’s new in Issue 2

Feature/enhancement Description Refer to

v1.5 Software Added information about v1.5 Chapter 4 - v1.5 Software

Software Features Description Altiostar Issue 3

Issue 3 Altiostar Software Features Description

An eNodeB is a logical entity comprising of vBBU and an iRRH or a set of

Software Features Description Altiostar Issue 3

Issue 3 Altiostar Software Features Description

v2.0 Software Features Description

3.1.1 Feature Information

Table 3-1 Feature Information - UL CoMP

Feature ID Feature Name

Software Features Description Altiostar Issue 3

Macro deployments, dense deployments (such as in stadiums) and deployments

3.1.5 Grouping under major function

3.1.6 Functional Diagrams/Flowcharts

3.1.7 Activation procedure

Issue 3 Altiostar Software Features Description

3.1.8 Deactivation procedure

3.1.9 Parameters related to the feature

3.1.10 Affected existing parameters

Software Features Description Altiostar Issue 3

3.1.11 Counters related to the feature

3.1.12 KPIs related to the feature

Issue 3 Altiostar Software Features Description

• ULCOMP.RBArrivLateAtPrim - Percentage of RBs that arrived late at primary

3.2.1 Feature Information

Table 3-2 Feature Information - Inter-Site CA

Feature ID Feature Name