Eden Net Lte Prach Guide

EdenNet 21
LTE Physical Random Access Channel

(PRACH) Optimization Guide
DN09230579
Issue: 1-0
LTE Physical Random Access Channel DN09230579 1-0 Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.
This document is intended for use by Nokia' customers (“You”) only, and it may not be used except for the purposes defined in the agreement
between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced,
modified or transmitted in any form or means without the prior written permission of Nokia. If you have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using
it. Nokia welcome Your comments as part of the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity,
fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves
the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of
this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. But,
Nokia' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of
the software in the Product will be uninterrupted or error-free.
N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY
OR F IT NE SS FO R A PA RT ICU LAR PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T.
IN NO EVEN T WI L L NOK IA B E LI ABLE F OR AN Y DA M A G E S , I N C L U D I N G B U T N O T L I M I T E D TO S P E C I A L ,
D IRE CT, IN D IRECT, I NCI DE NTAL OR C ON SEQ UE N T IA L OR A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D TO LO SS
OF PRO F IT, REVE NU E, B US IN ESS IN T ER RU PT I ON , B U S I NE S S O P P O RT U N I T Y O R D ATA T H AT M AY A R I S E
FRO M T HE USE O F TH IS DO CU M EN T O R T HE IN F OR M AT IO N I N I T, E V E N I N T H E C A S E O F E R R O R S I N O R
OM IS SI O NS FRO M T HI S DOC UM EN T O R IT S CO NT E N T.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the
prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © 2021 Nokia. All rights reserved.
Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the
safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this
document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for
any additional information.
LTE Physical Random Access Channel DN09230579 1-0 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
2 Overview of LTE PRACH Optimization module..........................................................................................11

2.1 LTE PRACH Optimization dependencies and interactions..................................................................... 11
2.1.1 Dependencies................................................................................................................................. 11
2.1.2 Interactions......................................................................................................................................12
3 LTE PRACH Optimization functional description and guidelines............................................................ 13

3.1 Operational modes of LTE PRACH Optimization................................................................................... 13
3.1.1 Open loop....................................................................................................................................... 13
3.1.2 Closed loop..................................................................................................................................... 14
3.2 Dynamic Spectrum Sharing (DSS) Supports..........................................................................................14
4 LTE PRACH Optimization algorithm............................................................................................................16

4.1 Fresh allocation....................................................................................................................................... 16
4.2 Conflict resolution....................................................................................................................................16
4.3 Inconsistency resolution.......................................................................................................................... 17
4.4 Common settings.................................................................................................................................... 18
4.4.1 Neighbor finding strategy................................................................................................................18
4.4.2 Parameter planning.........................................................................................................................19
4.4.3 Differentiation strategy.................................................................................................................... 21
4.5 PRACH planning support for running eNB auto planning...................................................................... 21
4.6 PRACH optimization in Heterogeneous Network (HetNet).....................................................................22
5 Planning requirements for LTE PRACH Optimization............................................................................... 25
6 Configuring and executing LTE PRACH Optimization module.................................................................26

6.1 LTE PRACH Optimization prerequisites................................................................................................. 26
6.1.1 License details................................................................................................................................ 27
6.1.2 CM data.......................................................................................................................................... 27
6.2 Accessing LTE PRACH Optimization......................................................................................................28
6.3 Configuring targets for LTE PRACH Optimization.................................................................................. 28
6.4 Configuring parameters for LTE PRACH Optimization........................................................................... 29
6.5 Selecting the configuration file for LTE PRACH Optimization................................................................ 30
6.6 Selecting execution type for LTE PRACH Optimization......................................................................... 30
6.7 Confirming execution for LTE PRACH Optimization...............................................................................31
7 LTE PRACH Optimization configuration parameters.................................................................................32

7.1 LTE PRACH Optimization GUI parameters............................................................................................ 32
7.2 LTE PRACH Optimization INI parameters.............................................................................................. 44
7.2.1 Example of LTE PRACH Optimization configuration file................................................................ 50
7.3 Configuring INI parameters.....................................................................................................................53
EdenNet 21 © 2021 Nokia 3

LTE Physical Random Access Channel DN09230579 1-0 Table of Contents
8 Viewing LTE PRACH Optimization reports................................................................................................. 55

8.1 Fresh report.............................................................................................................................................56
8.2 Conflict report.......................................................................................................................................... 63
8.3 Inconsistency report................................................................................................................................ 71
9 Viewing LTE PRACH Optimization events.................................................................................................. 78

9.1 LTE PRACH Optimization events........................................................................................................... 79
10 Monitoring LTE PRACH Optimization........................................................................................................80
11 Appendix: Summary messages................................................................................................................. 81

LTE Physical Random Access Channel DN09230579 1-0 Summary of changes
1 Summary of changes
Release Change description
EdenNet 21 Updated section:
• Overview of LTE PRACH Optimization module: A note is

added about the deprecation of direct CM integration.
EdenNet 20 FP 2011 Updated section:
• LTE PRACH Optimization GUI parameters: The description of

the Plan PRACH Frequency Start (PRFO) parameter is
updated.
Added section:
• Dynamic Spectrum Sharing (DSS) Supports
EdenNet 20 FP 2010 No change.
EdenNet 20 FP 2008 Updated sections:
• LTE PRACH Optimization INI parameters: A new parameter

(Wraparound_RSI_Allocation) is added.
• Example of LTE PRACH Optimization configuration file
EdenNet 20 FP 2007 Updated section:
• LTE PRACH Optimization GUI parameters: The description of

the Neighbor cell finding strategy GUI parameter is
modified.
EdenNet 20 Updated sections:
• LTE PRACH Optimization INI parameters: The following para-

meters are added:
– Report achieved reuse distance

– Maximum_fix_reuse_distance
– Increment_Fix_Distance
• Example of LTE PRACH Optimization configuration file
• Fresh report: The Achieved Reuse Distance Report table is
added.
• Conflict report: The Achieved Reuse Distance Report table is
added.

• Inconsistency report: The Achieved Reuse Distance Report ta-

ble is added.
• Closed loop: MORAN information is updated.
EdenNet 19A FP 2004 No change.
EdenNet 19A FP 2001 Updated sections:
• Parameter planning: A note is added for the Huawei vendor.

• LTE PRACH Optimization GUI parameters: The parameter de-
scription for the Target cell's Highspeed flag para-
meter (applicable only for Fresh allocation)
parameter is modified.
• Example of LTE PRACH Optimization configuration file: The
example is modified.
• Appendix: Summary messages: A message is added.
EdenNet 19A FP 1911 Updated sections:
• Overview of LTE PRACH Optimization module

• LTE PRACH Optimization functional description and guide-
lines
• PRACH optimization in Heterogeneous Network (HetNet)
• CM data
EdenNet 19A No change.
EdenNet 19 FP 1904 All instances of Custom modules are changed to Adapted mod-
ules in the following sections:
• Accessing LTE PRACH Optimization

• Configuring INI parameters
EdenNet 19 • A new parameter Schedule plan provision in main-

tenance window is added to the LTE PRACH Optimization
GUI parameters section.

• The following sections are updated:
– Conflict report
– Fresh report
– Inconsistency report
– LTE PRACH Optimization events
– Example of LTE PRACH Optimization configuration file
– LTE PRACH Optimization INI parameters
EdenNet 18 SP1 1901 • A new parameter eNBwise RSI allocation per fre-
quency level is added to the LTE PRACH Optimization INI
parameters section.
• Changes are made to the eNBwise RSI allocation content in
the LTE PRACH Optimization GUI parameters section.
• Changes are made to the Summary and Use case settings re-
ports of the following sections:
– Conflict report
– Fresh report
• The Appendix: Summary messages section is updated.
EdenNet 18 SP1 1812 No updates.
EdenNet 18 SP1 1811 A note is added to the Summary table in the Conflict report sec-
tion.
EdenNet 18 SP1 • The description of the Email addresses (Optional) pa-

rameter is modified.
• A note about inband NB-IoT cells is added to the Fresh alloca-
tion section.
• A note about inband NB-IoT cells is added to the Conflict reso-
lution section.
• Information about PRACH regions is updated and a note is
added in the Inconsistency resolution section.
EdenNet 18 The following sections are modified:
• LTE PRACH Optimization GUI parameters

• LTE PRACH Optimization INI parameters
EdenNet 17 SP1 FP1 The parameter KPI based relational neighbor

filtering is added to the section LTE PRACH Optimization GUI
parameters.

The below parameters are added to the section LTE PRACH Opti-
mization INI parameters:
• KPI_monitor_period
• Intra_LTE_HO_attempts
• Intra_LTE_HO_success_rate
The LTE PRACH Optimization prerequisites section is updated.
The LTE PRACH Optimization GUI parameters section is updated.
The Dependencies section is updated.
The PRACH optimization in Heterogeneous Network (HetNet) sec-

tion is updated.
The Conflict report section is updated.
Appendix: Summary messages section is added.
EdenNet 17 SP1 The document is restructured.
The following sections are added:
• Viewing LTE PRACH Optimization events

• LTE PRACH Optimization events
The following sections are updated:
• In the LTE PRACH Optimization GUI parameters section, the

following parameters are added:
– Plan Name Tag

– RSI allocation strategy
– Email Addresses (optional)
• In the LTE PRACH Optimization INI parameters section:
– Generate_events parameter is added.

– a note related to the Preamble format (PF) is added.
EdenNet 17 FP1 The following sections are added:
• Selecting the configuration file for LTE PRACH Optimization
The following sections are updated:
• LTE PRACH Optimization GUI parameters section > A note

is added related to support for Open loop execution with plan
creation
EdenNet 17 • LTE PRACH Optimization INI parameters section is updated

with the region forbidden value information.

• Overview of LTE PRACH Optimization module section is up-

dated.
EdenNet 16 SP4 LTE PRACH Optimization prerequisites section is updated with a

note related to Expected Reuse Distance.
EdenNet 16 SP3 • A note is added below the Configurable parameters of LTE

PRACH Optimization module table.
• LTE PRACH optimization output report table > Conflicting
cells report row is updated.
EdenNet 16 SP2 • Parameter planning section is updated.

• PRACH optimization in Heterogeneous Network (HetNet) sec-
tion is updated.
• Configurable parameters of LTE PRACH Optimization module
table is updated.
EdenNet 16 SP1 • Overview of LTE PRACH Optimization module section is up-

dated.
• PRACH module input and output parameters table is added.
• LTE PRACH Optimization INI parameters section is newly
added.
• Neighbor finding strategy section is updated.
• Parameter planning section is updated.
• Differentiation strategy section is updated.
• PRACH planning support for running eNB auto planning sec-
tion is newly added.
• PRACH optimization in Heterogeneous Network (HetNet) sec-
tion is newly added.
• LTE PRACH Optimization GUI parameters section is updated.
• Administering tasks section is removed, since this section is
common and is available in the Administering EdenNet docu-
ment.
EdenNet 16 • Inconsistency resolution section is updated.

• Neighbor finding strategy section is updated.
• Configurable parameters of LTE PRACH Optimization module
table is updated.
EdenNet 15 SP4 This is a new document that provides information on how to plan,
configure, and execute the LTE PRACH Optimization module.

Table 1: Summary of changes

LTE Physical Random Access Channel DN09230579 1-0 Overview of LTE PRACH Optimization
(PRACH) Optimization Guide module
2 Overview of LTE PRACH Optimization module

Physical Random Access Channel (PRACH) is the LTE uplink (UL) control channel, which the UE us-
es to initiate the Random Access (RACH) procedure.
RACH is a basic LTE procedure used to establish uplink synchronization and start the uplink transmis-
sion. PRACH is used when UE needs to send new UL data or control information or needs to receive
new downlink (DL) data or UE handing over from the current serving cell to a target cell or UE transit-
ing from RRC_IDLE to RRC Connected state.
PRACH configuration parameters are a combination of the following LTE cell parameters:
1. Root Sequence Index (RSI) - Root Sequence Index together with PRCS represents the code do-
main
2. PRACH Frequency Offset (PRFO) - Represents frequency domain
3. PRACH Configuration Index (PRCI) - Represents time domain
4. PRACH Cyclic Shift (PRCS) - PRACH Cyclic Shift together with RSI represents code domain
Note: One or more parameters from the above combination are not supported for some ven-
dors.
Supported vendor Technology
Nokia LTE
Ericsson LTE
Huawei LTE
ZTE LTE
Table 2: Supported vendors and technologies
Note:
Nokia only supports the use of AC based integration for Nokia, Ericsson, and Huawei ven-
dors as direct CM integration is deprecated from EdenNet 21 release onwards for these ven-
dors.
2.1 LTE PRACH Optimization dependencies and interactions

• Dependencies
• Interactions

LTE Physical Random Access Channel DN09230579 1-0 Overview of LTE PRACH Optimization
(PRACH) Optimization Guide module
2.1.1 Dependencies
If the cell plan data has the expected cell range, the module will use it. Otherwise, it will look for the
same information in the CM data. Ensure that the expected cell range is either present in the cell plan
or the CM data.
2.1.2 Interactions
The module uses the HetNet algorithm when the Coverage Overlap Strategy is selected as the
neighbor finding strategy. Ensure that all the mandatory parameters required for the HetNet algorithm
are available.

LTE Physical Random Access Channel DN09230579 1-0 LTE PRACH Optimization functional
(PRACH) Optimization Guide description and guidelines
3 LTE PRACH Optimization functional description and

guidelines
The EdenNet LTE PRACH Parameter Optimization module automatically reduces RACH setup failure,
call setup failure, and handover failure rates in the LTE networks by optimizing LTE PRACH parame-
ters. The module verifies the entire network operational cells (in actual state) to determine and resolve:
• PRACH parameters conflicts between neighbor cells

• PRACH inconsistency between own cell parameters (occurred due to incorrect configuration)
Or
• To perform fresh allocation for each of the target cells
The PRACH module provides recommendations and implements the changes to resolve, PRACH
conflicts between immediate neighbor cells and PRACH inconsistency between own cell parameters.
When the coverage overlap strategy is selected as the neighbor finding strategy, the LTE PRACH Op-
timization module considers each network cells differently as per the cell type, such as:
• macro
• micro
• pico
• femto
COp strategy determines the cell type based on pMax, dlCellPwrRed of the cell, in the Nokia vendor.
In Ericsson, Huawei, and ZTE vendors, the power parameter configured in the cell is used for neighbor
prioritization in Expected Cell Range substrategy of Coverage Overlap strategy.
3.1 Operational modes of LTE PRACH Optimization

The LTE PRACH optimization module can work in two different modes:
• Open loop
• Closed loop
3.1.1 Open loop

LTE PRACH Optimization supports open loop with deferred provisioning (only for NADC integration).
When the LTE PRACH Optimization module runs in open loop, the plan is visible under SON Modules
→ Status → Provisioning Logs.
• When the module run is successful, an entry appears in the provisioning logs area. The provision-
ing status is set as waiting till the plan is provisioned or till it expires.

• If the cells in the plan are a part of the SON module exclusion list, or if they are not a part of the
user’s geofence, the plan is not provisioned. In such cases, the status remains as waiting and
even the scheduled plans are moved to waiting status.
• The validity of the plan is for a period of 24 hours. The plan validity period can be configured. The
plan expires after the validity period and the user is not allowed to provision the plan.
For more details, see the Editing plan lifetime validity for open loop section in the EdenNet User
and Administration Guide.
• When a plan is scheduled, the provision status is changed to Scheduled. For direct OSS integra-
tion, open loop does not generate a plan.
• The user can reschedule and cancel schedules.
3.1.2 Closed loop

It is recommended not to execute closed-loop operations of the LTE PRACH Optimization module si-
multaneously for overlapping clusters or for clusters which share first or second level neighbors.
A user with closed loop permission for the LTE PRACH Optimization module can provision the plan im-
mediately, or schedule it to be provisioned later.
If the LTE PRACH Optimization module running in closed loop proposes changes for the cells from
both OSSs (enabled/connected OSS and disabled/disconnected OSS), then the module is overrid-
den to open loop. The reason for the override is to prevent changes from getting pushed (from the en-
abled/connected OSS) to the network to avoid inconsistencies. This scenario is applicable only for
MORAN (Multi Operator Radio Access Network).
For more information on disabling OSS access, see the Disabling OSS access for a disconnected
OSS section in the EdenNet User and Administration Guide document.
3.2 Dynamic Spectrum Sharing (DSS) Supports

In non-DSS deployments, PRACH is placed in any part of the bandwidth, preferably after PUCCH.
In DSS configurations, the NR spectrum is allocated to one edge of the shared spectrum. As a result,
PRACH is at one end of the shared spectrum. LTE takes up the remaining part of the shared spec-
trum, and follows the standard procedure of first allocating PUCCH resources within the LTE share of
the spectrum and then allocating PRACH.
Based on the differences in frequency domain allocation of PRACH in DSS enabled cells, the LTE
PRACH Optimization module requires changes to adapt to DSS specific frequency domain allocation.
Nokia recommends that you separate the scope between DSS enabled sites and non-DSS sites, thus
enabling PRFO usage for non-DSS sites.
Nokia DSS Phase1 and 2: The LTE PRACH Optimization module will be able to continue optimizing
LTE and PRACH cells in the following way: :

• Operators must plan the frequency domain position of PRACH in accordance with recommenda-
tions from LTE and NR DSS features.
• While running the PRACH module for DSS enabled cells, set the Plan PRACH Frequency
Start (PRFO) parameter to No for LTE and NR cells.
Thus, the PRFO position is not modified by the PRACH algorithm, and the network retains the op-
erator configured settings. As a result, the LTE PRACH Optimization module detects conflict and
optimizes the RSI and PRCI (code and time domain parameters).

LTE Physical Random Access Channel DN09230579 1-0 LTE PRACH Optimization algorithm
4 LTE PRACH Optimization algorithm

This section explains LTE PRACH optimization use cases and functionality.
• To support optimum planning and optimization of PRACH parameters

• To withstand the designed cell range and RACH density requirements of the target cell
Optimum PRACH parameters help to improve the decoding success rate of RACH requests and also
to minimize UL interference for RACH attempts, thereby enhancing the user experience.
4.1 Fresh allocation

In fresh allocation, the existing PRACH values for target cells are erased and a fresh allocation is done
for all the target LTE cells.
You have the flexibility to choose the plan from PRFO, PRCI and PRCS along with RSI (RSI will al-
ways be planned). The selected parameter has to be supported in the vendor’s BTS in order to get the
selected parameter planned, else that parameter will not be planned.
Fresh allocation use case is preferred when the network’s cell PRACH parameter values are too old,
due to which:
• it is hard to fix conflicts, and not able to achieve expected reuse distances for LTE cells
• unable to find suitable PRACH values for upcoming new LTE cell
• if a group of cells/neighborhood RACH success rate KPIs is poor
• if the cell range is changed for cells in the network
Note:
• All the target cells have their values freshly allocated, which results in a restart of cells.
• Inband NB-IoT cell occupies 1 PRB of the LTE cell. While allocating the PRFO for the
LTE cell, the module ensures that:
– PRACH PRBs do not overlap with Inband NB-IoT PRB.

– PRACH PRBs are either adjacent to PUCCH or NB-IoT PRB to minimize the frag-
mentation of PUSCH resources.
– This is supported only for Nokia vendor.
4.2 Conflict resolution

In conflict resolution, all the LTE cells in the target are verified for conflicts. LTE PRACH Optimization
module is capable of detecting the following issues for each cell in the LTE network:
• Sibling cells having same PRACH parameter configuration and are located within or out of reuse
distance (in case of, distributed site/antenna configuration).

• Two cells within a reuse distance having the same PRACH parameter configuration, such as same
or overlapping code, space and time values. For example, cell A and cell B both having same or
overlapping RSI, PRFO, PRCI and PRCS values.
• Two neighboring cells connected by LNREL/X2 (incoming or outgoing intra LTE neighbor relations)
and located within or out of reuse distance and using same or overlapping PRACH parameter con-
figuration.
Overall, between two TDD LTE cells (say cell A and cell B with same operating frequency) matching
any one of the above criteria, if the PRACH configuration is not differentiated either in code, space or
time, then a conflict is reported.
Between two FDD LTE cell (say cell A and cell B with same operating frequency) matching any one of
the above criteria if the PRACH configuration is not differentiated either in code, space or time (provid-
ed all FDD LTE cells in network are time synchronized) or at least in code or space (if FDD LTE cells in
network are not time synchronized), then a conflict is reported.
The conflicting cell pair is then tried for resolving conflicts by modifying one of the cell’s PRACH values
from the cell pair. During re-allocation, if the PRACH algorithm is unable to resolve detected conflicts
for a LTE cell, then the existing PRACH values for that LTE cell is retained.
Conflict resolution use case is preferred when new cell is planned and the X2s gets created one af-
ter another. Initially the new cell might have 10 X2s and later it can increase to 100 X2s, which might
cause establishment of X2s between cells using same PRACH configuration values.
Note: Inband NB-IoT cell occupies 1 PRB of the LTE cell. While allocating the PRFO for the
LTE cell, the module ensures that:
• PRACH PRBs do not overlap with Inband NB-IoT PRB.

• PRACH PRBs are either adjacent to PUCCH or NB-IoT PRB to minimize the fragmenta-
tion of PUSCH resources.
• This is supported only for Nokia vendor.
4.3 Inconsistency resolution

In inconsistency resolution, all the LTE cells in the target are checked for inconsistencies. Inconsis-
tencies are reported if existing PRACH configuration parameter values of a target LTE cell are not in
line or inconsistent when compared to other PRACH input parameters (see Configuring parameters for
LTE PRACH Optimization section) of the same cell.
When inconsistency resolution runs, then a target LTE cell is evaluated based on the following scenar-
ios and the cell is considered as inconsistent if the cell is:
• using global or OSS level forbidden values of preamble format PF, PRFO, PRCI or RSI
• using unsupported PRACH values or out of range PRACH values
• having PRACH region overlapping with PUCCH area
• having PRACH region not adjacent to PUCCH area
• having PRACH region overlapping with masked PUSCH area

• having PRFO not in line with total number of uplink PRB and so on
• having PRCI not in line with PRCS
• having PRCI not in line with RSI
• having PRCI not in line with tddSpecSubfConf
• having PF/PRCI not in line with tddFrameConf
• having PRACH region overlapping with NB-IoT PRB
• having PRACH region not adjacent to NB-IoT PRB
Note:
If the LTE cell has inband NB-IoT deployment, then the cell is considered only if the PRACH
region is neither adjacent to PUCCH nor to the inband NB-IoT PRB.
Inconsistent cells are sent for PRACH re-allocation. During re-allocation the PRACH algorithm tries to
resolve all the detected inconsistencies. If the detected inconsistencies cannot be resolved for a LTE
cell, then existing PRACH values for that LTE cell is retained.
Inconsistency resolution use case is preferred, if LTE cell does not have any PRACH conflicts but the
cell RACH success rate KPI is poor. The cell must be checked for PRACH inconsistency resolution
use case.
4.4 Common settings

The PRACH module provides the below common settings (RACH policies) for all the use cases. The
use cases are:
1. Neighbor finding strategy

2. Parameters Planning
3. Differentiation Strategy settings
4.4.1 Neighbor finding strategy

While running any one of the use cases, the PRACH allocation for target cell must have unique
PRACH parameters combinations between target and neighbor cells. The neighbor cells have to be
considered suitably from a limited geographical area, such that PRACH allocation must be possible for
target cell from within the available resources.
For example, RSI range is 0-837, considering many neighbors leads to unavailability of PRACH re-
sources, while considering too less neighbors might lead to PRACH interference.
Apart from sibling cells and X2 based neighbor cells, user can define a geographical boundary, such
that all the LTE cells are located within that geographical boundary. It can also be considered as neigh-
bors for target cell and an optimum PRACH resource allocation must be done for the target cell, while
maintaining uniqueness with all those neighbor cells. Location of a cell is determined by a cell’s anten-
na latitude and longitude.

Multiple Antenna support in PRACH module: Target and neighbor cells having multiple antennas
are handled by forming combinations with each antenna of target and neighbor cells, which will be
used for calculating the inter-cell distances. The shortest distance in the antennas combinations are
considered as the inter-cell distance, which then is used in the neighbor finding strategy to decide the
suitable neighbors for finding the PRACH conflicts.
You can choose a suitable neighbor finding strategy, such as:
1. Fixed Reuse distance: This strategy is preferred for urban area or when few X2 based neighbors
are available for target cell.
2. Relative Reuse distance: This strategy is preferred for rural area or area which has more X2
based neighbors. Settings definition is available in GUI parameter description, see Configuring pa-
rameters for LTE PRACH Optimization.
3. Coverage Overlap based neighborhood identification strategy: In this strategy, the neighbor-
hood of a LTE cell is determined based on HetNet algorithm. The PRACH optimization module au-
tomatically determines the neighbor cells based on cell’s Cell Type, Deployment Type, expected
cell range and Cost Hata based Propagation path loss models.
Note: User is recommended to use the above settings based on their network knowledge, as
the above recommendations might not be suitable for all the scenarios.
4.4.2 Parameter planning

While resolving the detected problems, for example, conflicts, inconsistencies or if user has chosen
to freshly allocate PRACH values, then the user can further specify the parameters PRACH algorithm
can modify as part of the use case.
• Planning RSI as part of all of the use case is always enabled.

• Additionally, the user can choose to modify PRFO along with RSI:
– If recent changes occurred in the cell’s PUCCH parameters

– If the user doubts the inconsistencies between PUCCH and PRFO settings, because of PRFO
is not adjacent to PUCCH area and so on.
– If the user understands that RSIs might not be available, and hence PRFO can be shifted. For
example, from the Lower Edge to the Upper Edge or from the Upper Edge to the Lower Edge
to differentiate PRACH in space/frequency domain. The available options are:
• use the edge as set in the forbidden/available list
Or
• use as per Mod2(PCI) value
• User can choose to modify PRCI along with RSI:
– If the recent changes (increase or decrease) happened in cell’s cell range/PRCS, which
changes the PF value internally and as a result PRCI has to be adjusted
– If the recent changes happened in cell’s RACH density due to increase or decrease of RACH
traffic (which changes the PRACH repetition in the radio frame), then PRCI must be adjusted

– If a user doubts inconsistencies between the PRCI and PRCS settings.

– If a user understands that RSIs might not be available. Hence, PRACH transmission can be
shifted by assigning different PRCIs to shift PRACH from Subframe 1 to Subframe 3 or the
other way around to differentiate PRACH in the time domain.
Note:
– When modifying only PRCI, PRACH algorithm has to calculate the Preamble Format
and with the Rach Density input, it arrives at a particular PRCI. Thus, it is mandatory
to provide ECR value as an input.
– Additionally, because the PRCS remains unmodified and cell radius is unchanged,
the Preamble Format internally also remains the same. As a result, new values of
PRCI can be allocated in a way which will be inline with the Preamble Format.
– To shift PRACH from Subframe x to Subframe y and to maintain differentiation with
the neighbor, the time domain differentiation has to be enabled.
– For the Huawei vendor, the HighSpeedFlag parameter of the target cell cannot be
set to True or False.
• Users can choose to modify PRCS along with RSI:
– If recent changes occurred in the cell’s PRCI due to changes in cell ranges
– If recent changes occurred in the cell’s PRCI due to RACH density
– If a user wants to increase or decrease cell’s coverage radius (cell radius)
– If a user doubts inconsistencies between the PRCS and PRCI settings.
Note:
– To change PRCS, which means changing cell radius, user has to decide how much
cell radius to change. Thus, it is mandatory to provide ECR value as an input.
– Once PRCS changes are done, it might lead to increase or decrease of the cell ra-
dius, which might lead to supporting of different Preamble Format and in turn, this
leads to change in PRCI. Thus, PRCI must also be planned and must be aligned
with new PRCS.
• Supported Combinations: As part of the combination validation, if any of the below combinations
are not supported, then the operation will be skipped.
– In case of non-COp strategy, the valid combinations are:
• Only RSI (RSI, by default planned)

• RSI and PRFO
• RSI and PRFO and PRCI
• RSI and PRFO and PRCI and PRCS
• RSI and PRCI
• RSI and PRCI and PRCS
– In case of COp strategy, the valid combinations are:


In case the Target cell's High speed flag parameter is set to True or False the valid combinations
are:

4.4.3 Differentiation strategy

PRACH module tries its best to achieve uniqueness of PRACH configuration parameters values be-
tween target cell and its neighboring cells. It provides two additional differentiation strategies, that is,
differentiation in space or frequency domain and time domain apart from code domain.
• Frequency domain differentiation: This strategy is always active and the user has to select from
the available options of positioning the PRACH towards the edge as set in forbidden/available list
or towards the edge obtained as per Mod2 (PCI) value. Accordingly, the PRFO value is updated to
be the one at lower edge or upper edge.
Note: This is applicable only if PRFO is selected for modification.
• Time domain differentiation: When this strategy is selected the target cell’s PRACH is positioned
in different sub frames than its neighbors. This is recommended only for time synchronized net-
works. The change is indicated with target cell’s PRCI having different values than neighbor cells
PRCI. The change in PRCI is done only if no more RSIs are available for allocation to target cell.
Note: This is applicable only if PRCI is selected for modification.
Differentiation in Frequency domain or Differentiation in Time domain leads to overlapping of PRACH

and PUSCH region and might lead to PRACH to PUSCH and PUSCH to PRACH interference.
Note: These interferences are not completely avoidable in LTE network, as the network can
still have PRACH to PRACH and PUSCH to PUSCH interference.
Additionally, if all LTE cells in the network do not have identical PUCCH configuration, then the net-
work will have at least partially PRACH to PUSCH, PRACH to PUCCH, and the other way around in-
terference. Therefore, if there are not enough root sequences available, then there is no way to avoid
the time or frequency domain differentiation. However, as long as enough root sequences are avail-
able, there is no need to use the time and frequency differentiation. Thus, it is up to the user's discre-
tion to choose the best strategy for their network.

4.5 PRACH planning support for running eNB auto planning

Fresh allocation algorithm is called from the eNodeB Auto Planning module to configure the LTE net-
work PRACH parameters for the new LTE cells, satisfying the distance or neighbor criteria defined
commonly as part of the eNodeB Auto Planning module. All the four PRACH parameters, such as RSI,
PRFO, PRCI, and PRCS are planned. For more details about the PRACH settings used as part of the
eNodeB Auto Planning module, see the eNodeB autoplanning section in the Automated Site Creation
Guide.
4.6 PRACH optimization in Heterogeneous Network (HetNet)

You can plan and optimize the PRACH parameters for LTE cells in the Heterogeneous Network (Het-
Net). You can:
• perform PRACH Fresh allocation in the HetNet scenarios
Note: With this enhancement, the same PRACH fresh allocation is also available as part
of eNodeB Auto configuration process to configure the PRACH parameters in the HetNet
scenarios. All the four PRACH parameters such as RSI, PRFO, PRCI, and PRCS (pro-
vided those parameters are supported by the cell) are planned, and the calculated ECR
value based on the Coverage Overlap (COp) strategy will be written back to the cell.
• perform PRACH Conflict resolution in the HetNet scenarios

• perform PRACH Inconsistency resolution in the HetNet scenarios
Additionally, the HetNet algorithm supports the following enhancements:
1. ECR of the cell being configured as part of PRACH optimization or as part of LTE eNB Auto-con-
figuration is determined by HetNet algorithm and this ECR value is used for all further PRACH pro-
cessing (such as, for PF, PRCS, and RSI planning)
a. If By Expected Cell Range strategy is selected, then the HetNet algorithm uses the ECR val-
ue stored in the EdenNet database (DB). The user can provide the ECR value through (import-
ing) a CSV plan file, which can populate the respective EdenNet DB tables, and the values are
stored for further use. Otherwise, the ECR value is read from the CM attributes.
• Upload a cell plan file.

• The PRACH operation cannot be continued if the ECR value is missing for one of the tar-
get or neighbor LTE cells.
• In case this strategy is selected, the Skip target or neighbor cell in case of invalid
neighbor setting is not applicable.
b. If By Fixed Cell Range strategy is selected, then the UI input values are considered.
c. If By Propagation Path Loss strategy is selected, then cell range for each target cell is calcu-
lated based on the COST Hata Model using the UI inputs.
2. PRACH optimization module also provides additional alternatives to find neighbors for each of its
use cases. For example, user can perform PRACH Conflict resolution, whereas neighbors can be

determined based on the Coverage Overlap (COp) strategy, apart from the existing Reuse Dis-
tance based strategies. Apart from the two sub strategies under the Reuse Distance strategy, there
are three more sub strategies under the COp strategy, such as:
a. If By Expected Cell Range strategy strategy is selected, then the cell range value available in
the EdenNet DB for each of the target and neighbor cells are considered as an ECR input.
b. If By Fixed Cell Range strategy strategy is selected, then the cell range value for each of the
target and neighbor cell is considered according to the value defined by user in UI, against the
respective Cell Type and Deployment Type.
c. If By Propagation Path Loss strategy is selected, then the cell range for each of the target
and neighbor cell is calculated using the values defined by user in UI using the COST Hata
model.
3. Neighbor cells are located within the user defined search distance, considering the target cell as
the center. The target cell is compared with it’s coverage area overlap along with the found neigh-
bor cells. The coverage area is calculated considering the previously calculated cell range as ra-
dius. If coverage area of target cell and neighbor cell overlaps, then such neighbor cells are further
used for processing, else the neighbor cell will be rejected. The overlapping neighbors are then
arranged in a list in a descending order of priority, whereas the priority is calculated considering the
cell’s antenna bearing and percentage of neighbor cell coverage area overlaps with the target cell.
After obtaining the neighbors, the PRACH algorithm proceeds naturally according to its existing be-
havior and tries to allocate a unique RSI to the target cell.
In case a unique PRACH allocation is not achieved after the first iteration (considering the com-
plete neighbor cell list), subsequent iterations run with a pared down neighbor cell list until a valid
PRACH configuration is obtained for the target LTE cell or until no more neighbors are remaining
to be pared.
Only non-LNREL and non-sibling cells are pared.
As part of the neighbor paring setting, users can define how many neighbors are to be pared down
after each unsuccessful iteration (for example, trim the prioritized neighbor list by n after every iter-
ation).
After the allocation is successfully completed, the behavior of the module (for example, generation
of reports, logs, and plans) remains the same and the PRACH parameters which were selected by
the user for modification are sent or pushed for provisioning into the EMS.
Note:
• All substrategies of Coverage Overlap strategy are supported only for Nokia.
Only Expected Cell Range substrategy of Coverage Overlap strategy is supported for
Ericsson, ZTE, and the homogeneous network of Huawei.
• Antenna information should be stored in the EdenNet database. The user has to pro-
vide the antenna information (latitude and longitude) by (importing) a CSV plan file
which can populate the respective EdenNet DB, and the values are stored for further

use. Cells (both target and neighbor) that do not have the antenna information are
not considered for PRACH optimization.

LTE Physical Random Access Channel DN09230579 1-0 Planning requirements for LTE PRACH
(PRACH) Optimization Guide Optimization
5 Planning requirements for LTE PRACH Optimization

This section provides a brief overview of LTE PRACH optimization planning requirements.
User equipment (UE) must not receive simultaneously multiple PRACH from immediate neighbors
when planning LTE PRACH that has either one of the following:
• Overlapping RSIs while PRACH being transmitted in same time and frequency
• Transmitted in overlapping time while similar code and frequency is used
• Transmitted in overlapping frequency while similar code and time is used
• The four PRACH configuration parameters must not be inconsistent with one another
If the four PRACH parameter combinations as a whole is the same in between two neighboring cells
and if the operating frequency is also same, then the cell’s PRACH will interfere with each other. This
results in RACH failures, decrease RACH detection probability and limits the coverage.
During PRACH planning and optimization, the key principle is that the PRACH configuration must not
be identical in the neighborhood of a target LTE cell. The target of the neighborhood is determined
based on the UI inputs provided by user.

LTE Physical Random Access Channel DN09230579 1-0 Configuring and executing LTE PRACH
(PRACH) Optimization Guide Optimization module
6 Configuring and executing LTE PRACH Optimization

module
To configure and execute a module, you must access LTE PRACH Optimization from EdenNet and configure few parameters.
Configure and execute the LTE PRACH Optimization module in the following order:
1. Accessing LTE PRACH Optimization
2. Configuring targets for LTE PRACH Optimization
3. Configuring parameters for LTE PRACH Optimization
4. Selecting the configuration file for LTE PRACH Optimization
5. Selecting execution type for LTE PRACH Optimization
6. Confirming execution for LTE PRACH Optimization
Expected outcome
LTE PRACH Optimization is executed based on the configuration parameters and as per the
defined schedule.
6.1 LTE PRACH Optimization prerequisites

Before running the LTE PRACH optimization module, perform the following checks:
• PRACH module is installed, activated and integrated with the respective EMS/NMS. For example:
NetAct, in case of Nokia vendor.
• LTE cell object must be available in CM with up-to-date information about PRACH parameter con-
figuration (Perform an MO upload or refresh if required).
• Up-to-date cell location information is available through antenna objects for each LTE cell in the
EdenNet database (Upload a cell plan file, if required).
• Choose a target on which the PRACH module can operate (for example, the target can contain a
valid group of LTE cells or a single LTE cell which are targeted for PRACH optimization).
• Select LTE cells in the target which have degradation in one or more of the following KPIs:
– LTE_INTRA_HO_ATT
– LTE_INTRA_HO_SUCCESS
– LTE_RACH_Attempts
– LTE_RACH_Setup_Completes_Rate
– LTE_RRC_Setup_Completes_Rate
• Alternatively, you can also select such cells as target, where there is a probability of PRACH con-
flict due to the recent roll-out of new eNBs in the surrounding area.

• – Expected cell range: LTE PRACH module uses the expected cell range stored in the Eden-
Net database for allocating the PRACH parameters. If the user has provided the expected cell
range from the cell plan (CSV), the module uses the same cell range. Else, it looks for CM pa-
rameters. If both are not available, the module:
• skips either the target cell or neighbor cell based on the GUI setting for Reuse distance
strategy.
• aborts the operation for COp strategy.
6.1.1 License details

The Table 3: LTE PRACH Optimization License license must be installed to activate the LTE PRACH
Optimization module.
Licensed feature com- Licensed feature

LK item code LK item object name
ponent code component name
ENSW6161CLK LTE PRACH Optimization 0000029017 LTE PRACH Optimiza-

CLK tion
Table 3: LTE PRACH Optimization License
6.1.2 CM data
LTE PRACH optimization module requires accurate LTE cell location data for all cells in the network.
This data is typically read from a planning tool output file.
EdenNet incorporates a latitude and longitude auditing capability for network engineers to check that
the cells are within a bounded area and that the co-sector cells (as identified by cell name) have the
same latitude and longitude (within a configurable distance, for example, 50 meters).
Note: It is recommended to run the latitude and longitude auditing module before LTE reuse
optimization module is enabled in the operator network.
The PRACH optimization module requires the neighbor list configuration for each of the target cells in
the network as well as the complete set of PRACH values assigned to each cell in the network. This
data can be read through the OSS interfaces.
Note: The neighbors can be any vendor (for example, Nokia, Huawei or Ericson) main LTE
cells, or external LTE cells (for example, EXEUCE, which represents the external LTE cells of
any vendor for the Nokia vendor target cell).
See the below documents for the complete list of parameters read and modified by the module:
• EdenNet module specific Data for Nokia

• EdenNet module specific Data for Huawei
• EdenNet module specific Data for Ericsson

• EdenNet module specific Data for ZTE
6.2 Accessing LTE PRACH Optimization

Log in to the EdenNet application and access the LTE PRACH Optimization module to perform any action on the module.
Prerequisites
• Prerequisites mentioned in the LTE PRACH Optimization prerequisites section must be met.
1. Log in to the EdenNet application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, and Cross-
OSS):
https://<EdenNet GUI_SERVERS IP>
where <EdenNet GUI_SERVERS IP> is the IP address of the GUI server provided during the
installation of EdenNet.
The EdenNet login page appears.

b) In the Username field, type the username.
c) In the Password field, type the password.
d) Click Log In.
The SON Activity page appears.
2. Click the Configure tab.
The following module categories appear in the left pane:
• EdenNet modules: The modules that Nokia provides are available in this category.
• Adapted modules: The modules that users develop are available in this category.
• Helper modules: These modules are mainly used for troubleshooting by Nokia support teams.
They are not categorized as Generally Available. General Availability implies that the release is
available to all customers.
3. Select the PRACH_Optimization_LTE module.
Expected outcome
The Configure Targets page appears.
4. Proceed with Configuring targets for LTE PRACH Optimization.

6.3 Configuring targets for LTE PRACH Optimization

In EdenNet, a module can only be configured and executed on a scope of cells. In Configure Targets page, you can select
cells on the map.
Prerequisites
• Successful completion of Accessing LTE PRACH Optimization.
1. Select the cells for configuration by:
• filtering specific cells on map based on Topology Filter or Center Frequency Filter and then
select target cells from the map
Or
• filtering specific cells on map based on Topology Filter or Center Frequency Filter and then
select all filtered items by clicking icon.
Or
• cell ID search selection tools from the map toolbar

Or
• selecting existing clusters
Target cells are selected and shown in the Selections pane. For more information about selecting
cells, see the Selecting cells section in the EdenNet User and Administrator guide.
2. Click Next.
Expected outcome
The Configure Parameters page appears.
3. Proceed with Configuring parameters for LTE PRACH Optimization.
6.4 Configuring parameters for LTE PRACH Optimization

To execute a module, you must configure a set of parameters. In the Configuration Parameter page, a list of parameters,
along with the descriptions and default values are displayed.
Prerequisites
• Successful completion of Configuring targets for LTE PRACH Optimization.
You can retain the default values or else select the values from the drop-down list.
1. Define the configuration parameters values. For the list of parameters, see LTE PRACH
Optimization GUI parameters values.
2. Click Next to schedule the operation.

Expected outcome
The Execution type page appears.
3. Proceed with Selecting the configuration file for LTE PRACH Optimization.
6.5 Selecting the configuration file for LTE PRACH Optimization

You can select configuration files from the list of available active configurations.
Prerequisites
• Successful completion of Configuring parameters for LTE PRACH Optimization.

• Ensure that the required configuration files are activated. For more details, see Configuring INI pa-
rameters.
1. Select the required configuration file from the available categories. If configuration files are not
available, proceed to the next step.
Note: You can select only one configuration file from each category.
2. Click Next.
Expected outcome
The Execution Type page appears.
3. Continue with Selecting execution type for LTE PRACH Optimization.
6.6 Selecting execution type for LTE PRACH Optimization

In the Execution type page you can schedule when the module must be executed. Depending on the type of execution such
as, immediately, later or during a specific date and time, the module is scheduled and executed.
Prerequisites
• Successful completion of Selecting the configuration file for LTE PRACH Optimization.
1. To schedule the module execution, select one of the following options:
• Execute Now - to activate the module immediately.

• Execute Later - to activate the module at a later time.

• Schedule Execution - to schedule the module for execution during a certain date and time.
2. Click Next.
Proceed with Confirming execution for LTE PRACH Optimization.
For more information about scheduling the execution, see the Configuring execution type section in
the EdenNet User and Administrator guide.
6.7 Confirming execution for LTE PRACH Optimization

In the Confirm Execution page, you can view the summary of the operation setup and start the operation. The operation is
executed as per the defined schedule.
Prerequisites
• Successful completion of Selecting execution type for LTE PRACH Optimization.
Procedure
• After verifying the configuration summary, click Finish.
Expected outcome
The LTE PRACH Optimization module starts execution as per the defined schedule.
You can monitor the operation. For more information, see Monitoring LTE PRACH Optimization

LTE Physical Random Access Channel DN09230579 1-0 LTE PRACH Optimization configuration
(PRACH) Optimization Guide parameters
7 LTE PRACH Optimization configuration parameters

A set of parameters are required to run a module. Module parameters are configured through:
• LTE PRACH Optimization GUI parameters

• LTE PRACH Optimization INI parameters
7.1 LTE PRACH Optimization GUI parameters

Table 4: GUI parameters of LTE PRACH Optimization module describes the GUI parameters of the
LTE PRACH Optimization module.
Default
Parameter name Parameter description Range (min, max) Step
value
Start hour of Indicates the start time for pro- 0 - 23 hours N/A 22
maintenance win- visioning the changes to the
dow network when the module is
run in the closed-loop mode.
Changes are not provisioned
before this time.
End hour of Indicates the end time for pro- 0 - 23 hours N/A 0
maintenance win- visioning the changes to the
dow network when the module is
run in the closed-loop mode.
Changes are not provisioned
after this time.
Note: End time

should be config-
ured later than the
start time.
Email addresses Email addresses to which a NA N/A NA

(Optional) link to download the report
should be sent. Separate
email addresses with a se-
mi-colon or comma.
Use case selec- Select one of the following • Fresh allocation N/A Conflict
tion PRACH use cases to run the • Conflict resolution resolution
module:

Default
value
• Fresh allocation: This op- • Inconsistency res-

tion erases and allocates olution
new PRACH values.
• Conflict resolution: This
option detects and re-
solves the conflicts.
• Inconsistency resolu-
tion: This option detects
and resolves the inconsis-
tencies for target cells.
RSI allocation There are two strategies to al- • Cell wise RSI allo- N/A Cell wise
strategy locate RSI. If set to Cell wise cation RSI alloca-
RSI allocation, then code do- • eNB wise RSI allo- tion
main differentiation is applied cation
first and is performed at cell
level. If set to eNB wise RSI
allocation, then time domain
differentiation is applied first
between intra-eNB cells and
neighbors followed by code
domain differentiation if need-
ed.
Neighbor cell The following strategies are • Coverage overlap N/A Reuse dis-
finding strategy used to obtain neighbor cells: strategy tance strat-
• Reuse distance egy

• Coverage overlap strat-
egy: considers the sur- strategy
rounding cells as neigh-

bor cells only if the cover-
age area calculated based
on the cell range overlaps
with the target cell cover-
age area.
The sub strategies are:
– Propagation path
loss and Fixed cell
range:
Valid combinations are

{RSI & PRCI & PRCS}

Default
value
OR {RSI & PRFO &

PRCI & PRCS}.
– Expected cell range:
Valid combinations are

{Only RSI} OR {RSI
& PRFO} OR {RSI &
PRFO & PRCI} OR
{RSI & PRFO & PRCI
& PRCS} OR {RSI
& PRCI} OR {RSI &
PRCI & PRCS}.
• Reuse distance strat-

egy: Considers the sur-
rounding cells located
within a defined reuse dis-
tance as neighbor cells.
The valid combinations
are {Only RSI} OR {RSI &
PRFO} OR {RSI & PRFO
& PRCI} OR {RSI & PRFO
& PRCI & PRCS} OR {RSI
& PRCI} OR {RSI & PRCI
& PRCS}.
Coverage over- Select one of the following • By expected cell N/A Expected
lap strategy coverage overlap option based range cell range
on the cell range calculation • By fixed cell range
strategy:
• By propagation
• By expected cell range: path loss
This option uses the cell's
expected cell range val-
ues.
• By fixed cell range: This
option uses the cell range
defined for each cell type
in the configuration file.
• By propagation path
loss: This option calcu-

Default
value
lates the cell range per

cell based on the COST
Hata model, that uses the
input provided by the user
in the .ini configuration file.
Cell range is used to check the

coverage overlap between the
target and neighbor cells.
Search distance Neighbor cells which are locat- 0.001 km - 200 km 0.001km 6 km
(Coverage over- ed within the defined search
lap strategy) distance from the target cell
location, will be compared for
the coverage area overlap with
the target cell. Note: To find
the conflicts based on rela-
tional neighbor(s) only, config-
ure the search distance as 0.
001km.
Neighbor reduc- If unique RSI allocation is not 1 to 50 1 1

tion count (Cov- found, then reduce the num-
erage overlap ber of non-relational intra-LTE
strategy) neighbors by the defined
neighbor reduction count.
Reuse distance It allows user to select a reuse • Fixed reuse dis- N/A Fixed reuse
Strategy Type distance strategy which deter- tance distance
mines the neighboring cells lo- • Relative reuse dis-
cated in a reuse distance and tance
the PRACH values that must
not be allocated to the target
cells while running the PRACH
use cases.
Maximum ex- It defines the maximum ex- 0.001 km - 100 km 0.001km 10km
pected PRACH pected PRACH reuse distance
reuse distance which the PRACH algorithm
(Fixed reuse dis- should try to achieve for each
tance) target cell.
It is recommended to select
realistic reuse distance values,

Default
value
as unnecessary higher values

evaluates too many neighbors
which might lead to increase in
time consumption.
Note: To find con-

flicts only based on
the relational neigh-
bor, give input as 0.
001km.
Reuse distance It defines the reduction size by From 0.001 km to the 0.001 km 1km
reduction size which the maximum expect- defined maximum ex-
(Fixed reuse dis- ed PRACH reuse distance val- pected PRACH reuse
tance) ue reduces each time, if maxi- distance
mum expected PRACH reuse
distance cannot be achieved
for a target cell.
Minimum expect- It defines the stopping thresh- From 0.001 km to the 0.001 km 2km
ed PRACH reuse old which acts as a minimum defined maximum ex-
distance (Fixed expected PRACH reuse dis- pected PRACH reuse
reuse distance) tance. Achieved reuse dis- distance
tance for a target cell can be
greater than or equal to this
value or else allocation not
possible for the target cell.
Reuse distance It defines the multiplier value 0.1 to 100 0.01 5

multiplier (Rel- which will be multiplied with
ative reuse dis- the calculated average dis-
tance) tance of X closest inter-eNB
cell level relational neighbors
to obtain the maximum expect-
ed PRACH reuse distance.
Number of clos- It defines the number of clos- 1 to 1000 1 10

est inter-eNB cell est inter-eNB cell level rela-
level relational tional neighbors X, whose dis-
neighbors (Rel- tance from the target cell is av-
ative reuse dis- eraged and multiplied by mul-
tance) tiplier value to obtain the maxi-

Default
value
mum expected PRACH reuse

distance.
Default starting It defines the average distance 0.001 km - 100 km 0.001 km 2km
average distance to be considered and multi-
(Relative reuse plied with multiplier to obtain
distance) maximum expected PRACH
reuse distance, in case the
obtained number of closest
inter-eNB cell level relation-
al neighbor is less than the
defined number of closest in-
ter-eNB cell level relational
neighbors X.
Multiplier reduc- It defines the reduction From 0.001 to the de- 0.001 0.5
tion amount (Rel- amount by which the reuse fined multiplier value
ative reuse dis- distance multiplier value re-
tance) duces each time, if maximum
expected PRACH reuse dis-
tance cannot be achieved for a
target cell.
Minimum multipli- It defines the stopping thresh- From 0.001 to the de- 0.001 1
er value (Relative old and represents the min- fined multiplier value
reuse distance) imum value a multiplier can
be allowed after successive
reduction from original value.
Achieved reuse distance for a
target cell should be achieved
with the multiplier value either
greater than or equal to this
value or else allocation not
possible for the target cell.
KPI based rela- If set to Yes, the relational • Yes N/A No

tional neighbor neighbors obtained from any • No
filtering neighbor finding strategy will
be filtered based on the HO
KPI thresholds. If set to No,
conflicts will be resolved re-
gardless of the HO KPIs.

Default
value
Note:
When the module

is unable to assign
conflict-free PRACH
parameters for a
scope cell, along
with first reduction
of reuse distance or
neighbor count, the
module also tries to
skip the relational
neighbors which are
beyond the maxi-
mum reuse distance
and do not meet HO
KPI criteria.
Plan PRACH If you select Yes, then PRFO • Yes N/A No

Frequency Offset parameter is planned, if it is • No
(PRFO) supported in the target cell.
If the scope contains DSS

enabled sites, this parameter
must be set to No.
Plan PRACH If you select Yes, then the • Yes N/A No

Configuration In- PRCI parameter is planned, • No
dex (PRCI) if it is supported in the target
cell.
Plan PRACH If you select Yes, then the • Yes N/A No

Cyclic Shift PRCS parameter is planned, • No
(PRCS) if it is supported in the target
cell.
Target cell's High To enable the target cells to • No change in Hs- N/A No change
speed flag para- serve either high speed or low Flag in HsFlag
meter (applicable speed users, modify the High • True
only for Fresh al- speed flag (HsFlag) parameter
• False
location) of the target cells.
If the parameter is set to True

option, the target cells are

Default
value
enabled to serve high speed

users.
If the parameter is set to False

option, the target cells are en-
abled to serve the low speed
users.
If the parameter is set to No

change in HsFlag option, the
high speed flag parameter's
actual defined value is used.
If the parameter is set to True

or False option, the valid com-
binations are:
OR
• RSI and PRFO and PRCI
and PRCS
Note:
This parameter can-

not be configured for
the Huawei vendor.
While detecting Frequency division duplex • Yes N/A No

conflicts, consid- (FDD) cells might or might not • No
er FDD LTE cells be time synchronized. Con-
as time synchro- flict detection is an automatic
nized (Conflict process which considers TDD
resolution) cells as time synchronized. It
asks for inputs from the user
- whether FDD cells are also
time synchronized. This helps
in accurate conflict detection.
Note: Intra-eNB
FDD cells are al-
ways considered as
time synchronized.

Default
value
To fix inconsis- It defines whether to modify • Modify necessary N/A Modify nec-
tencies, modify only the parameters which are parameters essary pa-
necessary pa- necessary or to modify from • Use manual selec- rameters
rameters or as those parameters which are tion
manually select- manually selected by user to
ed in UI (Incon- fix inconsistencies, after incon-
sistency) sistencies detection is done for
target cells.
Position of It considers the edge which • Mod2(PCI) value N/A Use PRFO
PRACH in fre- is not forbidden in PRFO for- • Use PRFO forbid- forbidden
quency domain bidden list or as per mod2 of den list list
PCI value where, if the result
is odd, then assign the lower
edge and if the result is even,
then assign the upper edge
value to PRFO of target cell
to achieve frequency domain
differentiation between target
and neighbor cells.
Use position of You can define to use PRCI • Yes N/A No

PRACH in time value of target cell for time do- • No
domain as differ- main differentiation between
entiation target and neighbor cells. It
is applicable for cells which
support PRCI parameter and
whose value does not change
automatically by eNB.
Skip target or It defines whether to skip tar- • Skip target cell N/A Skip target
neighbor cell in get cell or neighbor cell, in • Skip neighbor cell cell
case of invalid case a neighbor cell is found
neighbor invalid (that is, mismatching
or wrong band, bandwidths,
EARFCNs or null PCI, in case
Mod2(PCI) option is enabled).
SON Operation Set to Open Loop to run mod- • Open Loop N/A Open Loop
Mode ule in open loop mode. Set to • Closed Loop
Closed Loop to run module
in closed loop mode. In closed
loop mode, changes are au-

Default
value
tomatically pushed to the net-

work without user interven-
tion. In open loop mode, the
module do not automatically
push parameter changes to
network. User has to manual-
ly provision the plans to push
changes to the network.
Plan Name Tag Text that will be added to the Sequence which con- N/A N/A
names of all plans that will tains any combinations
be generated by this mod- of:
ule. If the target of the mod-
• Uppercase and
ule is a whole specific cluster
lowercase letters:
(and name of this cluster also
[A-Za-z]
matches requirements spec-
• Numbers: [0-9]
ified in Range column), then
• Underscore: _
the cluster name will also be
added to the plan name. Maximum length: 20
characters
Schedule plan If this parameter is set to True, True, False N/A False
provision in main- the changes are scheduled
tenance window to be provisioned during the
maintenance window (if the
plan is generated outside the
maintenance window). If the
plan is generated within the
maintenance window, the plan
is provisioned immediately.
If this parameter is set to

False, the plan is provisioned
only if it is generated within the
maintenance window.
Note:
• This parame-
ter is applicable
only when AC
is integrated. If
AC is not inte-

Default
value
grated, then the

plan will be pro-
visioned only if
it is generated
within the main-
tenance win-
dow.
• When the plan
is scheduled to
be provisioned,
the provisioning
will be attempt-
ed at the start
of the main-
tenance win-
dow. Howev-
er, if there are
many plans to
be provisioned,
the plan will be
provisioned lat-
er in the main-
tenance win-
dow. If the plan
cannot be pro-
visioned with-
in the mainte-
nance window
because of a
high number of
plans, then pro-
visioning will not
be re-attempted.
You can man-
ually provision
the plan from
the Provision-
ing Logs tab.
• If the sched-
ule is manu-
ally deleted in

Default
value
the Provision-
ing Logs tab,
the user has to
manually stop
the module in
the Active SON
Modules win-
dow.
Table 4: GUI parameters of LTE PRACH Optimization module
Note:
• The default values might not yield the desired optimized results in all customer net-
works. In case of dense networks, the parameter values must be tuned to avoid the LTE
PRACH Optimization module encountering out of memory exceptions.
• Supported combinations for planning PRACH parameters for reuse distance strategy
and expected cell range substrategy of coverage overlap strategy are:
– Only RSI
– RSI & PRFO
– RSI & PRCI
– RSI & PRFO & PRCI
– RSI & PRCI & PRCS
– RSI & PRFO & PRCI & PRCS
Supported combinations for planning PRACH parameters for fixed cell range substrategy
and propagation path loss substrategy are :

Supported combinations if the use case is Fresh allocation and Target cell's High
speed flag parameter value is set to a value other than 'No change in HsFlag' are :

• For the vendors supporting PRCI, if the module fails to assign conflict-free RSI for the
target cell, then the module behavior is as below:
– The module first assigns a different possible PRCI and tries to get conflict-free RSI, if
the below conditions are satisfied:
1. Plan PRACH Configuration Index is set to Yes.

2. Use position of PRACH in time domain as differentiation is set

to Yes.
Even with a different PRCI, if the module fails to get the conflict-free RSI, then the mod-
ule proceeds with reduction of non-relational neighbors.
Note: The module uses the combination of reducing the non-relational neigh-
bors and different PRCIs for the target cell.
If either Plan PRACH Configuration Index or Use position of PRACH in

time domain as differentiation is set to False, then the module proceeds with
the reduction of non-relational neighbors and tries to assign conflict-free RSI.
• RSI allocation strategy:
When the eNB wise RSI allocation strategy option is selected:
– Inconsistency resolution behaves like cell wise RSI allocation.

– The PRACH configuration index parameter is always planned along with RSI.
– The parameter Use position of PRACH in time domain as differenti-
ation should be set to Yes.
Table 5: Use cases for eNBwise RSI allocation per frequency level describes certain use
cases when the eNBwise RSI allocation per frequency level parameter is
set to Yes or No or if the value is absent.
eNBwise RSI allocation per frequency Either eNBwise RSI allocation per fre-
level = Yes quency level is absent or set as No
The LTE PRACH Optimization module The LTE PRACH Optimization module
extends the scope to contain all the in- extends the scope to contain all the in-
tra-eNB and intra-frequency cells of the tra-eNB cells of the original scope cell.
original scope cell.
If the LTE PRACH Optimization module If the LTE PRACH Optimization module
fails to allocate PRACH parameters for fails to allocate PRACH parameters for
any intra-eNB or intra-frequency cells, all any intra-eNB cells, all the intra-eNB cells
the intra-eNB and intra-frequency cells are are marked as failed and the module will
marked as failed and the LTE PRACH Op- not propose any parameters for these
timization module will not propose any pa- cells.
rameters for these cells.
Table 5: Use cases for eNBwise RSI allocation per frequency level

7.2 LTE PRACH Optimization INI parameters

Table 6: INI parameters of LTE PRACH Optimization module describes the INI parameters of the LTE
PRACH Optimization module.
Range Default
Parameter name Parameter description Step
(min, max) value
Preamble Format One or more preamble formats 1 to 4 4 1

from 1 to 4 can be defined for-
bidden. Preamble format 0 can
never be forbidden. Enter com-
ma separated values. A range
of values is also allowed, for
example: 1-3.
Root Sequence Index (for One or more RSI from 0 to 837 0 to 837 N/A 1
Preamble Format 0 to 3) can be defined forbidden for a
cell which uses preamble for-
mat 0 to 3. Enter comma sep-
arated values. A range of val-
ues is also allowed, for exam-
ple: 15-30.
Root Sequence Index (for One or more RSI from 0 to 137 0 to 137 N/A 1
Preamble Format 4) can be defined forbidden for a
cell which uses preamble for-
mat 4 . Enter comma separat-
ed values. A range of values
is also allowed, for example:
52-62.
PRACH Configuration In- One or more configuration in- 0 to 2 and 6 N/A 1

dex dex from 0 to 63 can be de- to 63
fined forbidden except 3,4,5 for (3,4,5 not
a cell. Enter comma separated allowed)
values. A range of values is al-
so allowed, for example: 8-16.
PRACH Frequency Offset PRACH frequency offset points • Upper Upper N/A
to either upper edge or lower Edge Edge
edge of PUSCH (Physical Up- • Lower
link Shared Channel) area. Ei- Edge
ther Upper edge or Lower edge
can be defined forbidden.

Range Default
(min, max) value
Macro_Urban Cell range for Macro Urban 0 to 500 km 2 N/A
Macro_SubUrban Cell range for Macro Suburban 0 to 500 km 4 N/A
Macro_Rural Cell range for Macro Rural 0 to 500 km 8 N/A
Micro_Urban Cell range for Micro Urban 0 to 20 km 1 N/A
Micro_SubUrban Cell range for Micro Suburban 0 to 20 km 2 N/A
Micro_Rural Cell range for Micro Rural 0 to 20 km 4 N/A
Pico_Urban Cell range for Pico Urban 0 to 5 km 0.5 N/A
Pico_SubUrban Cell range for Pico Suburban 0 to 5 km 1 N/A
Pico_Rural Cell range for Pico Rural 0 to 5 km 2 N/A
Femto_Urban Cell range for Femto Urban 0 to 1 km 0.1 N/A
Femto_SubUrban Cell range for Femto Suburban 0 to 1 km 0.2 N/A
Femto_Rural Cell range for Femto Rural 0 to 1 km 0.4 N/A
desiredCellEdgeRSRP Desired Cell Edge RSRP -120dBm to -100 N/A

0dBm
UEAntennaHeight UE Antenna Height 1m to 100m 1.5 N/A
macroCellRangeExten- Macro Cell Range Extension -0.5 to 0.5 0 N/A

sionFactorModifier Factor Modifier
Cell-
microCellRangeExten- Micro Cell Range Extension -0.5 to 0.5 0 N/A

cro-
picoCellRangeExten- Pico Cell Range Extension -0.5 to 0.5 0 N/A

o-
femtoCellRangeExten- Femto Cell Range Extension -0.5 to 0.5 0 N/A

to-
Generate_events This is an optional parameter. • Yes No N/A

If this is set to Yes, then events • No
will be generated.
KPI_monitor_period The number of completed days 1 to 10 days 1 day 1

for which daily aggregated
KPIs have to be considered.

Range Default
(min, max) value
For example:
Configure KPI_monitor_
period = 3 to view the result
for 4 days of KPI data.
Intra_LTE_HO_attempts The neighbor relations with 10 to 1000 100 10

handover attempts equal to
or greater than the defined
threshold will be considered for
conflict resolution.
Intra_LTE_HO_success_ The neighbor relations with 1 to 100% 50 1

rate handover success rate less
than or equal to the defined
threshold will be considered for
conflict resolution.
eNBwise RSI allocation per This parameter is valid only if Yes, No No N/A
frequency level the RSI allocation strategy is
set as eNB wise RSI allocation.
Based on this parameter, the
LTE PRACH Optimization mod-
ule extends the scope cells to
include all the intra-eNB cells
or intra-eNB cells within the
same frequency layer:
• If the parameter is set as

Yes, the LTE PRACH Op-
timization module extends
the scope to include all the
intra-eNB cells within the
same frequency layer.
• If the parameter is ab-
sent or set as No, the LTE
PRACH Optimization mod-
ule extends the scope to
include all the intra-eNB
cells.
Report achieved reuse dis- This parameter enables the Yes, No No N/A
tance LTE PRACH Optimization mod-
ule to calculate and report the

Range Default
(min, max) value
achieved reuse distance post
optimization.
Note: Enabling this

parameter has an
impact on the per-
formance of the LTE
PRACH Optimization
module.
Maximum_fix_reuse_dis- The LTE PRACH Optimization 1 to 50 20 N/A

tance module considers only the dis-
tance neighbor cells (relation-
al neighbors are not included)
within the configured value of
this parameter. This parame-
ter is valid only if the Report
achieved reuse distance
INI parameter is set to Yes.
The unit is kilometers.
Increment_Fix_Distance This parameter indicates the fix N/A 1 N/A

distance increment until the cell
conflict is identified or Maxi-
mum_fix_reuse_distance
is reached. This parameter
is valid only if the Report
achieved reuse distance
INI parameter is set to Yes.
The unit is kilometers.
Wraparound_RSI_Alloca- This parameter enables or dis- Yes, No No N/A

tion ables the wraparound Root Se-
quence Index (RSI) allocation.
The wraparound RSI alloca-

tion is supported only when the
available RSI range for a cell
is:
• 0 to 837
Or

Range Default
(min, max) value
• 0 to 137
Table 6: INI parameters of LTE PRACH Optimization module
Note: N/A indicates that the field can be left blank for that parameter in the INI file.
• Forbidden or reserved PRACH configuration values: This parameter allows reserved PRACH
configuration to be defined within the module. The module must not use any values from the re-
served PRACH configuration groups for recommending new PRACH configuration. When the
module encounters cells that use values from the reserved PRACH configuration values groups,
the module will throw a warning and might not retune the PRACH configuration for those cells or
as set by user. The reserved PRACH values groups can be specified in comma separated values
and in a range of values, for example, 1,2,3 or 1-3, 2-3.
• In the forbidden profile the following parameters are marked as forbidden at global and region lev-
el:
– PF - one or more or all from the Preamble format (from 1 to 4) can be defined as forbidden
Note: If Cat-M feature is activated in any of the scope cells, then the restriction on
Preamble format will be applicable for the entire scope cells as per eNodeB capabili-
ty. User should forbid the unsupported Preamble formats in the .ini file.
– RSI (for PF 0 to 3) - one or more or all from RSI (from 0 to 837) can be defined forbidden for a
cell, where user assumes PF 0-3 is used
– RSI (for PF 4) - one or more or all from RSI (from 0 to 137) can be defined forbidden for a cell,
where user assumes PF 4 is used
Note:
– If region wise forbidden values are provided, then the module considers the region
forbidden values. Otherwise, it considers the global forbidden values.
– In this ini file section [Region.Forbidden:<region_name>], replace the
<region_name> with region (managing OSS) connected to the lab. If multiple re-
gions are connected, then one section for each region must be created to forbid the
region specific values.
• If the COp is selected as neighbor finding strategy (Coverage overlap strategy (COp strategy)),
then the input for the Fixed cell range and Propagation path loss sub-strategy type can be provid-
ed from the INI file. To import the settings for Fixed cell range and Propagation path loss sub-strat-
egy, a template or file can be constructed in INI format and imported according to the capability
available in EdenNet.
– Fixed cell range settings values to be defined in the INI file are:

• Macro_Urban (0 to 500)
• Macro_SubUrban (0 to 500)
• Macro_Rural (0 to 500)
• Micro_Urban (0 to 20)
• Micro_SubUrban (0 to 20)
• Micro_Rural (0 to 20)
• Pico_Urban (0 to 5)
• Pico_SubUrban (0 to 5)
• Pico_Rural (0 to 5)
• Femto_Urban (0 to 1)
• Femto_SubUrban (0 to 1)
• Femto_Rural (0 to 1)
Note: If value defined against any setting is null, then the HetNet algorithm will use
the default value for them and continue.
– Propagation path loss settings values to be defined in the INI file are:
• desiredCellEdgeRSRP (-120dBm to 0dBm)

• UEAntennaHeight (1m to 100m)
• macroCellRangeExtensionFactorModifier (-0.5 to 0.5)
• microCellRangeExtensionFactorModifier (-0.5 to 0.5)
• picoCellRangeExtensionFactorModifier (-0.5 to 0.5)
• femtoCellRangeExtensionFactorModifier (-0.5 to 0.5)
Note: If the value defined against any setting is null, the HetNet algorithm uses the
default value for such settings.
• Generate_events - This is an optional parameter. Only if the user wants to generate events, then
this parameter can be added to the configuration file.
The configuration file is uploaded to the EdenNet application. For more information on how to up-
load the file, see the Configuring a module section in the EdenNet User and Administrator guide
document.
• When KPI based relational neighbor filtering is set to Yes, and if the module fails to
allocate conflict-free PRACH parameters in the first iteration, it skips the relational neighbors which
are beyond the reuse distance. For these relational neighbors:
– HO attempts are below Intra_LTE_HO_attempts

– HO success rate is below Intra_LTE_HO_success_rate

7.2.1 Example of LTE PRACH Optimization configuration file

The following code snippet is an example configuration file (INI file) for the LTE PRACH Optimization
module.
Note: The format of each section and the parameter details are provided as part of the below
sample file.
[Global]
# Generates events when set to "Yes". Default is "No". Accepted values
are "Yes" and "No"
Generate_events = No
# The number of days of KPI to be considered. Default is 1. Ranges
between 1 to 10 days.
KPI_monitor_period = 1
# The neighbor relations with handover attempts equal to or greater than
the defined threshold will be considered for conflict resolution. Ranges
from 10 to 1000 with step size of 10. Default 100.
Intra_LTE_HO_attempts = 100
# The neighbor relations with handover success rate less than or equal
to the defined threshold will be considered for conflict resolution.
Ranges from 1 to 100%. Default 50%.
Intra_LTE_HO_success_rate = 50
# This parameter is valid only if the RSI allocation strategy is set as
eNB wise RSI allocation. Based on this parameter, the module extends
the scope cells to include all the intra-eNB cells or intra-eNB cells
within the same frequency layer. If the parameter is set as Yes, then
the module extends the scope to include all the intra-eNB cells within
the same frequency layer. If the parameter is absent or set as No, then
the module extends the scope to include all the intra-eNB cells.
eNBwise RSI allocation per frequency level = No
Wraparound_RSI_Allocation = No
#################################################################
[Forbidden:Global]
Preamble Format = 1,2-3,4
Root Sequence Index (for Preamble Format 0 to 3) = 0-800
Root Sequence Index (for Preamble Format 4) = 1,2,3-100,119,126,129-136
PRACH Configuration Index = 0,1,2,20-29,60,63
PRACH Frequency Offset = Upper Edge
#################################################################
[AchievedReuseDistanceSettings]
Report achieved reuse distance = No
Increment_Fix_Distance = 1
Maximum_Fix_Reuse_Distance = 20
#################################################################
[Region.Forbidden:<region_name>]
Preamble Format = 1,2-3,4
Root Sequence Index (for Preamble Format 0 to 3) = 0-100

Root Sequence Index (for Preamble Format 4) = 1,2,3-100,119,126,129-136

PRACH Configuration Index = 0,1,2,20-29,60,63
PRACH Frequency Offset = Upper Edge
#################################################################
# Note for [Region.Forbidden:<region_name>]. Replace <region_name>
with region(managing OSS)connected to the lab. If multiple regions are
connected, then one section for each region must be created to forbid
the region specific values.
# Note for [Forbidden:Global] or [Region.Forbidden:<region_name>]:
# Allowed Range for PF which can be defined forbidden are: 1 to 4;
Default: PF 4 forbidden, so make sure to put 4 as forbidden unless want
to really make use of PF 4.
# Allowed Range for RSI (for PF 0 to 3) which can be defined forbidden
are: 0 to 837; Default: Nothing forbidden
# Allowed Range for RSI (for PF 4) which can be defined forbidden are: 0
to 137; Default: Nothing forbidden
# Allowed Range for PRCI which can be defined forbidden are: 0 to 2 & 6
to 63 (3,4,5 not allowed except for Huawei vendor. For Huawei, 3,4,and 5
can be forbidden); Default: Nothing forbidden
# Allowed Range for Frequency Offset which can be defined forbidden are
either Upper Edge OR Lower Edge; Default = Upper Edge
# If no value defined against a parameter i.e., the value is left blank
e.g., "Preamble Format = " then corresponding Default value will be
considered.
# If a parameter row is not present then corresponding Default value
will be considered.
# Make sure to define forbidden values, if any after a single space
after '=' sign & don't leave any space in between the defined values e.g.
, "Preamble Format = 1,2,3,4" is correct while, "Preamble Format =1,2, 3,
4" is incorrect.
# Values can be defined with comma separated e.g., Preamble Format = 1,2,
3
# Range can be defined with <starting value><hyphen><ending value> e.g.,
Preamble Format = 1-4
# Note: In case user inputs such values which are not allowed or in
unspecified format, module output will be incorrect.
#################################################################
[FixedCellRange]
#cellType_deploymentType (Range in km) = Value (km)
Macro_Urban (0 to 500) = 2
Macro_SubUrban (0 to 500) = 4
Macro_Rural (0 to 500) = 8
Micro_Urban (0 to 20) = 1
Micro_SubUrban (0 to 20) = 2
Micro_Rural (0 to 20) = 4
Pico_Urban (0 to 5) = 0.5
Pico_SubUrban (0 to 5) = 1
Pico_Rural (0 to 5) = 2
Femto_Urban (0 to 1) = 0.1
Femto_SubUrban (0 to 1) = 0.2

Femto_Rural (0 to 1) = 0.4
#################################################################
[PropagationPathLoss]
#propagationPathLossSetting (Ranges) = Value
desiredCellEdgeRSRP (-120dBm to 0dBm) = -100
UEAntennaHeight (1m to 100m) = 1.5
macroCellRangeExtensionFactorModifier (-0.5 to 0.5) = 0
microCellRangeExtensionFactorModifier (-0.5 to 0.5) = 0
picoCellRangeExtensionFactorModifier (-0.5 to 0.5) = 0
femtoCellRangeExtensionFactorModifier (-0.5 to 0.5) = 0
#################################################################
7.3 Configuring INI parameters

INI parameters can be modified to change the default settings of a LTE PRACH Optimization module. You can also import,
export, delete, activate, and deactivate configuration files..
Only users with administrator privileges have permission to modify the parameters.

OSS):

d) Click Log In.
2. Click Administration → Modules.
The following module categories appear in the left pane:
• EdenNet modules: The modules that Nokia provides are available in this category.
• Adapted modules: The modules that users develop are available in this category.
• Helper modules: These modules are mainly used for troubleshooting by Nokia support teams.
They are not categorized as Generally Available. General Availability implies that the release is
available to all customers.
3. Select the PRACH_Optimization_LTE module.
4. Click Configure → Module Configuration.

The PRACH_Optimization_LTE Configuration Manager dialog box appears.
5. Click Module Global Configuration.
A list of configuration files appears.
You can click:
• Import And Activate: to import a file and activate it immediately.

• Import: to import a file.
• Export: to export the selected file to your system.
• Delete: to delete the selected file from the list.
Note: Users with Administrator or SON Module Manager permissions can delete
the configuration files. The configuration files can be deleted only if it is not used by
other modules.
• Activate: to activate the selected file from the list.
Note: Multiple configurations can be activated.
• Deactivate: to deactivate the activated file.
Note: A file can be deactivated only when it is not used by other modules listed
under Active SON Modules or Module History.
• Set As Default: to set the selected file as the default configuration.

• Reset: to reset the edited parameter values in the selected INI file.
• Save As: to save the configuration with a different name.
• Save: to save the new version of the configuration after editing the parameter values in the
selected INI file.
Note: For more details, see the Configuring a module section in EdenNet User and
Administrator guide.
For the INI file parameters, see LTE PRACH Optimization INI parameters.

LTE Physical Random Access Channel DN09230579 1-0 Viewing LTE PRACH Optimization reports
8 Viewing LTE PRACH Optimization reports

For every execution, each LTE PRACH Optimization module produces an output file in Microsoft Excel format, such as,
(instance_number).xlsx and produces multiple output files.

OSS):

d) Click Log In.
2. Click SON Modules → Status.
Active SON Modules and Module History appears in the left pane, and Execution Status
appears in the right pane.
3. In the left pane, click a module either from Active SON Modules or Module History.
The module execution status appears in the right pane.
Active SON Modules – All active SON module instances are listed in this section.
The Active SON Modules table displays all the active SON module instances. An active SON
module instance is one which is in a state other than stopped, completed, or failed.
Module History - SON Module iterations are listed in the Module History section.
The Module History table displays the recently stopped, completed, or failed SON module in-
stances.
The Module History area of the Status tab displays SON modules in various states of inactivity.
4. In the right pane, click Logs.
5. Click the user name next to User Outputs.
Directory Listing For dialog box with a list of files and module names appears.
6. Select the required module file name.

A set of Excel files is listed in the Directory Listing For dialog box.
7. Select a file and open or save it.
The LTE PRACH Optimization module produces an output file in Microsoft Excel format, for
example, <instance_number.xlsx> and produces multiple output files.
8.1 Fresh report

Table 7: Fresh report describes the tabs available in the Fresh report.
Tab Description
Use case settings report This tab lists the UI parameters and the INI parameters that are used
for the LTE PRACH Optimization module run.
Summary This tab provides a summary of the LTE PRACH Optimization mod-
ule run. It provides the following statistics:
Applicable for all use cases:
• Total scope cells

• Skipped scope cells due to various reasons
• Number of target cells with missing optional parameters
• Number of scope cells for which the PRACH configuration is pro-
posed to the network
Applicable for conflict resolution:
• Extended scope cells

• Number of scope cells having PRACH conflicts
• Number of scope cells with successful conflict resolution
• Number of scope cells whose conflicts could not be resolved
• Number of scope cells with successful configurations that have
retained the previous values
• Number of scope cells whose conflicts were resolved by reduc-
ing the reuse distance or skipping the undefined neighbors
Applicable for fresh allocation:

• Number of scope cells with successful PRACH configurations
• Number of scope cells whose PRACH parameters could not be
configured

Tab Description
• Number of scope cells whose PRACH parameters were config-
ured by reducing the reuse distance or skipping the undefined
neighbors
Applicable for inconsistency resolution:
• Number of scope cells having inconsistent PRACH configura-

tions
• Number of scope cells with successful inconsistency resolution
• Number of scope cells whose inconsistencies could not be re-
solved
• Number of scope cells whose PRACH parameters were config-
ured by reducing the reuse distance or skipping the undefined
neighbors
PRACH validation warnings This tab lists the warnings and errors encountered by the LTE
PRACH Optimization module either during validation of the data or
during the execution of the algorithm. This tab provides the following
details:
• Cell information
• Problem details
• Algorithm behavior
Coverage overlap warnings This tab provides details about the error or warning encountered by
the coverage overlap neighbor finding strategy and the default value
for any missing parameters.
Results This tab provides the following information after the execution of the
use case:
• Modified scope cell information

• Existing and proposed root sequence index
• Existing and proposed PRACH frequency offset
• Existing and proposed PRACH configuration index
• Existing and proposed PRACH cyclic shift
• Expected and achieved reuse distance
• Expected and achieved overlapped neighbors
For LTE:
• 4G-NBIoT inband PRB index

• Existing and proposed APUCCH PRACH region

Tab Description
Achieved Reuse Distance Re- The LTE PRACH Optimization module:

port
• can be configured to report the Achieved Reuse Distance by en-
abling the Report achieved reuse distance INI parame-
ter. It does not report the Achieved Reuse Distance by default.
• checks for PRACH conflicts only within the configured Maxi-
mum_fix_reuse_distance.
• checks for PRACH conflicts only for distance based neighbors,
some of which could be defined neighbors as well.
Table 7: Fresh report
Table 8: Use case settings report describes the columns in the Use case settings report.
• PRACH preference option Value
Start hour of maintenance window 8
End hour of maintenance window 9
Email addresses (Optional) xyz@nokia.com
Use case selection Fresh allocation
RSI allocation strategy eNB wise RSI allocation
eNBwise RSI allocation per frequency level Yes
Neighbor cell finding strategy Reuse distance strategy
Target cell's High speed flag parameter (applicable only for Fresh allo- No change in HsFlag
cation)
Reuse distance Strategy Type Fixed reuse distance
Maximum expected PRACH reuse distance 10.0 km
Reuse distance reduction size 1.0 km
Minimum expected PRACH reuse distance 2.0 km
KPI based relational neighbor filtering Yes
KPI monitor period 1 day
Intra LTE HO attempts threshold 100
Intra LTE HO success rate threshold 50 %
Parameters planned along with PRACH root sequence index (provided None
they are supported in the cells)
Position of PRACH in frequency domain Use PRFO forbidden list

PRACH preference option Value
Use position of PRACH in time domain as differentiation No
Forbidden PRACH configuration index for region global []
Forbidden preamble format for region global []
Forbidden RACH root sequence (Preamble format 0-3) for region glob- [ ]
al
Forbidden RACH root sequence (Preamble format 4) for region global []
Forbidden frequency offset edge for region global Upper Edge
Forbidden PRACH configuration index for region sross []
Forbidden preamble format for region sross []
Forbidden RACH root sequence (Preamble format 0-3) for region []

sross
Forbidden RACH root sequence (Preamble format 4) for region sross []
Forbidden frequency offset edge for region sross Upper Edge
Action to take in case of invalid neighbor Skip neighbor cell
Plan provisioning type Open Loop
Table 8: Use case settings report
• Table 9: Summary describes the columns in Summary.
PRACH operation summary Value
Total number of target cells 3
Extended scope for eNodeB wise allocation 21
Total number of scope cells for Fresh allocation 9
Target cells skipped from configuration since one or more basic parameters 0
[EARFCN(s), channel bandwidth(s), Location(s)] are missing
Target cells skipped from configuration as PRACH control parameter set to 0

manual or Activate supplemental downlink carrier is set to True
Target cells skipped from configuration as PUSCH masking settings are invalid 0
Target cells skipped from PRACH configuration due to missing PCI while Fre- 0
quency offset selection is chosen to be based on PCI modulo2
Target cells skipped from configuration due to missing or invalid mandatory 0

PRACH input values [PRFO, PRCI, PRCS, RSI or Expected cell range]

Target cells skipped from configuration since one or more of its neighbors has 0
basic parameters [EARFCN(s), channel bandwidth(s), Location(s), TDD sub-
frame configuration, High Speed Flag] missing or invalid
Target cells skipped from configuration since one or more of its neighbors have 0
missing or invalid mandatory PRACH input values [PRFO, PRCI, PRCS, RSI
or Expected cell range]
Target cells skipped due to indeterminable expected cell range or mismatch 0

between proposed preamble format and (cyclic shift or configuration index)
Target cells having one or more missing input parameters 5
Target cells with configuration not possible 0
Target cells with successful configuration 3
Target cells with successful configuration but previous values retained 3
Target cells with configuration obtained by reducing reuse distance or by trim- 0

ming neighbors
Target cells with successful configuration and new changes proposed to push 3
into network
Table 9: Summary
• Table 10: PRACH validation warnings describes the columns in PRACH validation warnings.
Column name Value
Cell DN PLMN-PLMN/EXCENBF-1/EXENBF-3863/EXEUCE-2
Cell name 310-260-73579-21
Cell region t5oss
Cell vendor nsn
Problem Target cell has one or more missing input parameters
Algorithm behavior Default values will be used for missing input parame-
ters:{'phichRes': 0.1667, 'rachDensity': 1.0, 'deltaPucchShift': 2}
Table 10: PRACH validation warnings
• Table 11: Coverage overlap warnings describes the columns in Coverage overlap warnings.

Column name Value
Cell name 1-1-1-1
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCELL-4
Cell vendor vendor_1
Cell region region_1
Problem Invalid/Missing antenna horizontal beamwidth
Defaulting to 65 (Large Cells) or 360
Table 11: Coverage overlap warnings
• Table 12: Results describes the columns in Results.
Column name Value
Modified target cell DN PLMN-PLMN/MRBTS-73660/

LNBTS-73660/LNCEL-11
Modified target cell name 244-8-1725-3
Modified target cell region t5oss
Modified target cell vendor nsn
Root sequence index existing 24
Root sequence range existing 24 - 27
Root sequence index proposed 24
Root sequence range proposed 24 - 27
PRACH frequency offset existing 4
PRACH frequency offset proposed 4
4G-NBIoT inband PRB index Not Applicable
APUCCH PRACH region existing Not Applicable
APUCCH PRACH region proposed Not Applicable
PRACH configuration index existing 19
PRACH configuration index proposed 19
PRACH cyclic shift existing 0
PRACH cyclic shift proposed 0
Expected reuse distance (km) 10

Column name Value
Neighbor finding rule status Expected reuse distance fulfilled
Achieved reuse distance (km) 10
Expected overlapped neighbors (count) 3
Note: This column will be present in the report

only when the GUI parameter Neighbor cell
finding strategy = Coverage overlap
strategy.
Achieved overlapped neighbors (count) 3
Note: This column will be present in the report

only when the GUI parameter Neighbor cell
finding strategy = Coverage overlap
strategy.
Table 12: Results
Table 13: Achieved Reuse Distance Report describes the columns in the Achieved Reuse Distance
Report tab.
Column name Example
Target Cell DN PLMN-S2OSS0302/MRBTS-152613/LNBTS-152613/

LNCEL-24
Target Cell name DDA02752A41
Target Cell region S2OSS0302
Target Cell vendor vendor_1
Nearest neighbor cell DN causing PRACH N/A

conflict
Nearest neighbor cell name causing PRACH N/A

conflict
Region of nearest neighbor cell causing N/A

PRACH conflict
Vendor of nearest neighbor cell causing N/A

PRACH conflict
Achieved Reuse Distance (km) 20

Table 13: Achieved Reuse Distance Report
8.2 Conflict report

Table 14: Conflict report describes the tabs available in the Conflict report.
Tab Description
Use case settings report This tab lists the UI parameters and the INI parameters that are used for
the LTE PRACH Optimization module run.
Summary This tab provides a summary of the LTE PRACH Optimization module run.
It provides the following statistics:

• Number of scope cells for which the PRACH configuration is proposed
to the network

• Number of scope cells with successful configurations that have re-
tained the previous values
• Number of scope cells whose conflicts were resolved by reducing the
reuse distance or skipping the undefined neighbors

• Number of scope cells whose PRACH parameters could not be con-
figured
• Number of scope cells whose PRACH parameters were configured by
reducing the reuse distance or skipping the undefined neighbors

Tab Description
• Number of scope cells having inconsistent PRACH configurations
• Number of scope cells whose inconsistencies could not be resolved
• Number of scope cells whose PRACH parameters were configured by
reducing the reuse distance or skipping the undefined neighbors
PRACH validation warn- This tab lists the warnings and errors encountered by the LTE PRACH Op-
ings timization module either during validation of the data or during the execu-
tion of the algorithm. This tab provides the following details:
• Problem details
Conflicts This tab provides details about the conflicts for each source cell:
• Source cell information

• Information about the nearest conflicting cell
• Expected reuse distance and achieved reuse distance
• Expected overlapping neighbors and achieved overlapping neighbors
• Conflict resolution status
Coverage overlap warn- This tab provides details about the error or warning encountered by the
ings coverage overlap neighbor finding strategy and the default value for any
missing parameters.
Results This tab provides the following information after the execution of the use
case:

For LTE:


Tab Description
Achieved Reuse Dis- The LTE PRACH Optimization module:

tance Report
• can be configured to report the Achieved Reuse Distance by enabling
the Report achieved reuse distance INI parameter. It does
not report the Achieved Reuse Distance by default.
• checks for PRACH conflicts only within the configured Maximum_
fix_reuse_distance.
• checks for PRACH conflicts only for distance based neighbors, some
of which could be defined neighbors as well.
Table 14: Conflict report
Email addresses (Optional) xyz@nokia.com
Use case selection Conflict resolution
RSI allocation strategy eNB wise RSI allocation
eNBwise RSI allocation per frequency level Yes
Target cell's High speed flag parameter (applicable only for Fresh al- No change in HsFlag
location)
KPI based relational neighbor filtering Yes
While detecting conflicts, consider FDD LTE cells as time synchro- No

nized
Parameters planned along with PRACH root sequence index (provid- PRACH frequency offset
ed they are supported in the cells) and PRACH configuration
index and PRACH cyclic
shift

Use position of PRACH in time domain as differentiation No
Forbidden PRACH configuration index for region global []
Forbidden preamble format for region global []

global
Forbidden RACH root sequence (Preamble format 4) for region glob- [ ]

al
Forbidden frequency offset edge for region global Upper Edge
Forbidden PRACH configuration index for region sross []
Forbidden preamble format for region sross []

sross
Forbidden RACH root sequence (Preamble format 4) for region sross [ ]
Forbidden frequency offset edge for region sross Upper Edge
• Table 16: Summary describes the columns in Summary.
Target cells having conflicts 2
Extended scope for eNodeB wise allocation 21
Total number of scope cells for Conflict resolution 6

Target cells skipped from configuration as PUSCH masking settings are in- 0
valid

Target cells skipped from PRACH configuration due to missing PCI while 0
Frequency offset selection is chosen to be based on PCI modulo2

Target cells skipped from configuration since one or more of its neighbors 0
has basic parameters [EARFCN(s), channel bandwidth(s), Location(s), TDD
subframe configuration, High Speed Flag] missing or invalid
Target cells skipped from configuration since one or more of its neighbors 0
have missing or invalid mandatory PRACH input values [PRFO, PRCI,
PRCS, RSI or Expected cell range]
Target cells skipped due to indeterminable expected cell range or mismatch 0

between proposed preamble format and (cyclic shift or configuration index)
Target cells having one or more missing input parameters 3
Target cells with resolution not possible 0
Target cells with successful resolution 6
Target cells with configuration obtained by reducing reuse distance or by 0

trimming neighbors
Target cells with successful configuration and new changes proposed to 6

push into network
Table 16: Summary
Column name Value
Cell DN PLMN-PLMN/MRBTS-150909/LNBTS-150909/LNCEL-4
Cell name 310-260-10062-11
Cell region t5oss
Cell vendor nsn
Problem "FDD or TDD division" parameter empty for EXEUCE cell
Algorithm behavior Considering it as FDD cell, based on downlink earfcn

• Table 18: Conflicts describes the columns in Conflicts.
Column name Value
Conflicting target cell DN PLMN-PLMN/MRBTS-65519/LNBTS-65519/LN-

CEL-1
Conflicting target cell name L9BH1475A11
Conflicting target cell region t5oss
Conflicting target cell vendor nsn
Nearest neighbor cell DN causing PRACH PLMN-PLMN/MRBTS-65541/LNBTS-65541/LN-

conflict CEL-3
Nearest neighbor cell name causing PRACH L9C00144A31

conflict
Region of nearest neighbor cell causing t5oss

PRACH conflict
Vendor of nearest neighbor cell causing nsn

PRACH conflict
Nearest conflicting neighbor cell distance (km) 8.484
Conflict resolution status SUCCESS
Note: This column will be present in

the report only when the GUI para-
meter Neighbor cell finding
strategy = Coverage over-
lap strategy.
Note: This column will be present in

the report only when the GUI para-
meter Neighbor cell finding

Column name Value
strategy = Coverage over-

lap strategy.
Table 18: Conflicts
Column name Value
Cell name 1-1-1-1
Column name Value
Modified target cell DN PLMN-PLMN/MRBTS-65519/

LNBTS-65519/LNCEL-1
Modified target cell name L9BH1475A11
Modified target cell region t5oss
Root sequence range existing 48 - 53
Root sequence range proposed 144 - 153
4G-NBIoT inband PRB index Not Applicable
APUCCH PRACH region existing Not Applicable

Column name Value
APUCCH PRACH region proposed Not Applicable
PRACH cyclic shift existing 10
PRACH cyclic shift proposed 12
Note: This column will be present in the re-

port only when the GUI parameter Neigh-
bor cell finding strategy = Cov-
erage overlap strategy.
Note: This column will be present in the re-

port only when the GUI parameter Neigh-
bor cell finding strategy = Cov-
erage overlap strategy.
Table 20: Results
Report tab.
Column name Example

LNCEL-24

conflict

Column name Example

conflict

PRACH conflict

PRACH conflict
8.3 Inconsistency report

Table 22: Inconsistency report describes the tabs available in the Inconsistency report.
Tab Description
Use case settings report This tab lists the UI parameters and the INI parameters that are used for
the LTE PRACH Optimization module run.
Summary This tab provides a summary of the LTE PRACH Optimization module
run. It provides the following statistics:

• Number of scope cells for which the PRACH configuration is pro-
posed to the network

• Number of scope cells whose conflicts were resolved by reducing
the reuse distance or skipping the undefined neighbors

Tab Description

• Number of scope cells whose PRACH parameters could not be con-
figured
• Number of scope cells whose PRACH parameters were configured
by reducing the reuse distance or skipping the undefined neighbors
• Number of scope cells having inconsistent PRACH configurations

• Number of scope cells whose inconsistencies could not be resolved
• Number of scope cells whose PRACH parameters were configured
by reducing the reuse distance or skipping the undefined neighbors
PRACH validation warn- This tab lists the warnings and errors encountered by the LTE PRACH
ings Optimization module either during validation of the data or during the ex-
ecution of the algorithm. This tab provides the following details:
• Problem details
Coverage overlap warn- This tab provides details about the error or warning encountered by the
ings coverage overlap neighbor finding strategy and the default value for any
missing parameters.
Inconsistencies This tab provides information about the scope cell which has an inconsis-
tent PRACH configuration:
• Scope cell information

• Violated inconsistency rule
• Inconsistency resolution status
Results This tab provides the following information after the execution of the use
case:


Tab Description

For LTE:

Achieved Reuse Distance The LTE PRACH Optimization module:

Report
• can be configured to report the Achieved Reuse Distance by en-
abling the Report achieved reuse distance INI parameter. It
does not report the Achieved Reuse Distance by default.
• checks for PRACH conflicts only within the configured Maximum_
fix_reuse_distance.
• checks for PRACH conflicts only for distance based neighbors, some
of which could be defined neighbors as well.
Table 22: Inconsistency report
Use case selection Inconsistency resolution
Target cell's High speed flag parameter (applicable only for Fresh No change in HsFlag
allocation)
Parameters planned along with PRACH root sequence index PRACH frequency offset and
(provided they are supported in the cells) PRACH configuration index
and PRACH cyclic shift
To fix inconsistencies, modify necessary parameters or as manu- Modify necessary parame-

ally selected in UI (Inconsistency) ters

Global forbidden PRACH configuration index []
Global forbidden preamble format []
Global forbidden RACH root sequence (Preamble format 0-3) [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10,
11, 12, 13, 14, 15, 16, 17,
18, 19, 20, 21, 22, 23, 24,
25, 26, 27, 28, 29, 30, 31,
32, 33, 34, 35, 36, 37, 38,
39, 40, 41, 42, 43, 44, 45,
46, 47, 48, 49, 50]
Global forbidden RACH root sequence (Preamble format 4) []
Global forbidden frequency offset edge Upper Edge
• Table 24: Summary describes the columns in the Summary.
Target cells having inconsistencies 2

Target cells skipped from configuration as PUSCH masking settings are invalid 0
Target cells skipped from PRACH configuration due to missing PCI while Fre- 0
quency offset selection is chosen to be based on PCI modulo2

Target cells skipped from configuration since one or more of its neighbors has 0
basic parameters [EARFCN(s), channel bandwidth(s), Location(s), TDD sub-
frame configuration, High Speed Flag] missing or invalid

Target cells skipped from configuration since one or more of its neighbors have 0
missing or invalid mandatory PRACH input values [PRFO, PRCI, PRCS, RSI or
Expected cell range]
Target cells skipped due to indeterminable expected cell range or mismatch be- 0
tween proposed preamble format and (cyclic shift or configuration index)
Target cells with resolution not possible 0
Target cells with successful resolution 2
Target cells with configuration obtained by reducing reuse distance or by trim- 0

ming neighbors
Target cells with successful configuration and new changes proposed to push 2
into network
Table 24: Summary
Column name Value
Cell DN PLMN-vsp0081_offline/MRBTS-100/LNBTS-1/LNCEL-1
Cell name 214-3-306051-12
Cell region vsp0081_offline
Cell vendor nsn
Problem "FDD or TDD division" parameter empty for EXEUCE cell
Algorithm behavior Considering it as FDD cell, based on downlink earfcn
Column name Value
Cell name 1-1-1-1

Column name Value
• Table 27: Inconsistencies describes the columns in Inconsistencies.
Column name Value
Inconsistent target cell DN PLMN-vsp0081_offline/MRBTS-100/LNBTS-1/LNCEL-1
Inconsistent target cell name CANX6110N1A
Inconsistent target cell re- vsp0081_offline

gion
Inconsistent target cell ven- nsn

dor
Violated rules The PRACH PRBs are not adjacent to the PUCCH or masked
PUSCH area.
Inconsistency resolution sta- Successful

tus
Table 27: Inconsistencies
Column name Value
Modified target cell DN PLMN-vsp0081_offline/MRBTS-100/LNBTS-1/

LNCEL-1
Modified target cell name CANX6110N1A
Modified target cell region vsp0081_offline
Root sequence range existing 364-371
Root sequence range proposed 364-371
4G-NBIoT inband PRB index Not applicable

Column name Value
APUCCH PRACH region existing Not applicable
APUCCH PRACH region proposed Not applicable
PRACH cyclic shift existing Not supported
PRACH cyclic shift proposed Not supported
Table 28: Results
Report tab.
Column name Example

LNCEL-24

conflict

conflict

PRACH conflict

PRACH conflict

LTE Physical Random Access Channel DN09230579 1-0 Viewing LTE PRACH Optimization events
9 Viewing LTE PRACH Optimization events

You can view events which are specific to the module.

OSS):

d) Click Log In.
2. Click the Events tab.
A list of filters appears in the left pane.
3. From the Module/Service filter, click the required LTE PRACH instance to view the event logs.
The event logs can also be viewed using the following filters:
• Name: indicates the name of the event.

• Category: indicates the category of the event.
• Level: indicates the level of the event.
• Source Type: indicates from where the event originates.
• Target Type: indicates to where the event is targeted.
• Target: indicates the target of the event (cell name can be selected).
Note: The common event levels are information and warning. By default, the warning
and error level filters are selected. To view all levels of events, remove the warning and
error level filter.
4. In the Time Range area, set the required time range.
5. Under Saved Filters, enter a name for the event filter or for the combination of filters, and save it
using the Save As New Filter option.
6. Click Filter to apply the filter.
The event log appears.

LTE Physical Random Access Channel DN09230579 1-0 Viewing LTE PRACH Optimization events
9.1 LTE PRACH Optimization events

The LTE PRACH Optimization module specific events are described in Table 30: LTE PRACH Opti-
mization events.
Category: PRACH_Optimization_LTE
Name Level Description
PRACH_Default_para- info Indicates:

meter_used
• Target Cell
• Use case: Fresh allocation/Conflict resolution/Inconsis-
tency resolution
• Parameter (multiple instances)
• Default value (multiple instances)
PRACH_Proposed_pa- info Indicates the parameters which are proposed for PRACH
rameters optimization for the following use cases:
• Fresh allocation
• Conflict resolution
• Inconsistency resolution
Note: The Proposed value can be the same as

the Old value.
PRACH_Skipped_cell warning Indicates the target cells and neighbor cells (if any) which
are skipped from PRACH optimization for the following use
cases:
• Fresh allocation
• Conflict resolution
• Inconsistency resolution
It also indicates the reasons for skipping.
PRACH_Unresolved_ warning Indicates which target cells and neighbor cells have unre-
conflicts solved conflicts. It also indicates the reason for not resolving
the conflict.
Table 30: LTE PRACH Optimization events

LTE Physical Random Access Channel DN09230579 1-0 Monitoring LTE PRACH Optimization
10 Monitoring LTE PRACH Optimization

You can monitor the LTE PRACH Optimization module's:
• activities
• status
• events
For more information, see the Configure and monitor SON modules section in the EdenNet User and
Administration guide.

LTE Physical Random Access Channel DN09230579 1-0 Appendix: Summary messages
11 Appendix: Summary messages

Table 31: Summary messages describes the summary messages.
Summary message Description
Total number of target cells Total number of selected target cells.
Extended scope for eNodeB wise Total number of target cells when eNB wise RSI allocation is se-
allocation lected as RSI allocation strategy. With eNB wise RSI al-
location strategy, the module considers all the sibling cells of an
eNB for optimization, though the user does not select some sib-
ling cells in the scope.
Target cells skipped from config- Total number of skipped target cells either because the user
uration as PRACH control para- does not want the module to optimize the target cell (by setting
meter is set to manual or Activate PRACH control as manual), or the supplemental downlink carrier
supplemental downlink carrier is is activated for the target cell.
set to True
Target cells skipped since one or Total number of skipped target cells as one or more neighbors
more of its neighbors have miss- have missing or invalid mandatory PRACH input values, and
ing or invalid mandatory PRACH Skip target or neighbor cell in case of invalid
input values neighbor is set as Skip target cell.
Target cells skipped from config- Total number of skipped target cells as the target cell does not
uration since one or more basic have EARFCN, channel bandwidth or location.
parameters[EARFCN(s), chan-
nel bandwidth(s), Location(s)] are
missing
Target cells skipped from config- Total number of skipped target cells as the target cell does not
uration due to missing or invalid have the expected cell range or PRACH parameters (PRFO,
mandatory PRACH input values PRCI, PRCS, RSI)
[PRFO, PRCI, PRCS, RSI or Ex-
pected cell range]
Target cells skipped from PRACH Total number of skipped target cells as the target cell does not
configuration due to missing PCI have a PCI, and Position of PRACH in frequency do-
while Frequency offset selection is main is set as Mod2(PCI) value
chosen to be based on PCI modu-
lo2
Target cells having inconsisten- Total number of target cells which have inconsistencies among
cies the PRACH parameters.

Target cells with successful reso- Total number of target cells for which the module has successful-
lution ly resolved PRACH conflicts for the Conflict resolution use-case.
Target cells with resolution not Total number of target cells for which the module is unable to re-
possible solve the PRACH conflicts in Conflict resolution use-case.
Target cells with successful con- Total number of target cells which are successfully configured
figuration with PRACH parameters in Fresh allocation use-case.
Target cells with configuration not Total number of target cells for which the module is unable to
possible configure the PRACH parameter in Fresh allocation use-case.
Target cells having conflicts Total number of target cells which have conflicts either with other
target cells or neighbors in Conflict resolution use-case.
Target cells skipped due to inde- Total number of skipped target cells, as the module is unable to
terminable expected cell range or determine the expected cell range from preamble format, PRCS,
mismatch between proposed pre- and PRCI.
amble format and (cyclic shift or
configuration index)
Target cells skipped from con- Total number of skipped target cells as one or more neighbors
figuration since one or more have a missing or invalid EARFCN, channel bandwidth, location,
of its neighbors has basic TDD subframe configuration, or High Speed Flag and Skip
parameters[EARFCN(s), chan- target or neighbor cell in case of invalid
nel bandwidth(s), Location(s), neighbor is set as the Skip target cell.
TDD subframe configuration, High
Speed Flag] missing or invalid
Target cells with new changes Total number of target cells for which the module has proposed
proposed to push into network changes. This could be less than Total cells with successful con-
figuration or Target cells with successful resolution as resolving
the conflict of one cell might resolve the conflict of another target
cell.
Target cells with configuration ob- Total number of target cells for which the module is able to suc-
tained by reducing reuse distance cessfully configure the PRACH parameters after reducing the
or by trimming neighbors reuse distance (in Reuse distance strategy) or by reducing the
lowest ranked, coverage overlapping neighbors. This means that
the module is unable to configure the non-conflicting PRACH pa-
rameters for these target cells by considering all the neighbors
as per the configuration parameters.
Target cells with successful con- Total number of target cells for which the module need not pro-
figuration but previous values re- pose any new PRACH parameters and thus retain the existing
tained PRACH parameters. This means that the module had identi-

fied the conflict for this target cell A was due to the conflicting
PRACH parameter with another target cell B. When the module
assigned the target cell B with non-conflicting PRACH parame-
ters, it in turn resolves the conflict which target cell A had and
hence there is no need to propose any new PRACH parameters
to target cell A.
Target cells with resolution ob- Total number of target cells whose PRACH conflicts have been
tained by reducing reuse distance resolved by the module and the newly achieved reuse distance
and with a value equal to or high- is equal to or higher than the distance to the previous nearest
er than previous reuse distance conflicting cell.
Target cells with resolution ob- Total number of target cells whose PRACH conflicts have been
tained by reducing reuse distance resolved by the module and the newly achieved reuse distance
and with a value lower than previ- is smaller than the distance to the previous nearest conflicting
ous reuse distance cell.
Target cells skipped from config- Total number of skipped target cells as one or more neighbors
uration since one or more of its have missing or invalid expected cell range or PRACH parame-
neighbors have missing or invalid ters (PRFO, PRCI, PRCS, RSI) and Skip target or neigh-
mandatory PRACH input values bor cell in case of invalid neighbor is set as Skip
[PRFO, PRCI, PRCS, RSI or Ex- target cell.
pected cell range]
Target cells skipped from config- Total number of skipped target cells due to the invalid PUSCH
uration as PUSCH masking set- mask setting for the target cell.
tings are invalid
Target cells skipped from config- Total number of skipped target cells either because Automatic
uration as parameter "Selection PUCCH configuration is not activated or Select PRACH region is
of PRACH region in automatic not configured.
PUCCH allocation" value is not
available
Target cells skipped from config- Total number of skipped target cells which have either missing or
uration due to missing or invalid invalid TDD subframe configurations.
TDD subframe configuration
Target cells with missing expected Total number of target cells which do not have the expected cell
cell range in the cell plan range.
Target cells skipped from configu- Total number of skipped target cells due to missing antenna in-
ration due to missing antenna formation.
Target cells having one or more Total number of target cells which have a few missing input para-
missing input parameters meters for which the module uses the default value.

Skipped relational neighbors as If the module is unable to allocate the conflict-free PRACH para-
they are beyond reuse distance meters with all the neighbors in consideration and if KPI based
and do not meet KPI threshold relational neighbor filtering is set as Yes, the mod-
ule drops the relational neighbors from the use case if:
• the relational neighbor is beyond the reuse distance, and

• the handover KPI between the target cell and this relational
neighbor is below the defined threshold
This field provides a count of all relational neighbors which are

skipped by the module.
Total number of scope cells for The number of valid cells (including sibling cells) sent for fresh
fresh allocation allocation when eNB wise RSI allocation is selected as the RSI
allocation strategy.
Total number of scope cells for The number of valid cells (including sibling cells) sent for conflict
Conflict resolution resolution when eNB wise RSI allocation is selected as the RSI
allocation strategy.
Target cells skipped from config- The total number of target cells skipped because of unsupported
uration due to unsupported or in- or invalid HighSpeed flag value (applicable for Huawei vendor,
valid HighSpeed flag value where the HighSpeed flag is set to extra high speed).
Table 31: Summary messages

Eden Net Lte Prach Guide

Uploaded by

Copyright:

Available Formats

You might also like

Eden Net Lte Prach Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eden Net Lte Prach Guide

Uploaded by

Copyright:

Available Formats

EdenNet 21

LTE Physical Random Access Channel

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

Copyright © 2021 Nokia. All rights reserved.

Important Notice on Product Safety

2 Overview of LTE PRACH Optimization module..........................................................................................11

3 LTE PRACH Optimization functional description and guidelines............................................................ 13

4 LTE PRACH Optimization algorithm............................................................................................................16

5 Planning requirements for LTE PRACH Optimization............................................................................... 25

6 Configuring and executing LTE PRACH Optimization module.................................................................26

7 LTE PRACH Optimization configuration parameters.................................................................................32

EdenNet 21 © 2021 Nokia 3

8 Viewing LTE PRACH Optimization reports................................................................................................. 55

9 Viewing LTE PRACH Optimization events.................................................................................................. 78

10 Monitoring LTE PRACH Optimization........................................................................................................80

11 Appendix: Summary messages................................................................................................................. 81

EdenNet 21 © 2021 Nokia 4

Release Change description

EdenNet 21 Updated section:

• Overview of LTE PRACH Optimization module: A note is

EdenNet 20 FP 2011 Updated section:

• LTE PRACH Optimization GUI parameters: The description of

• Dynamic Spectrum Sharing (DSS) Supports

EdenNet 20 FP 2010 No change.

EdenNet 20 FP 2009 No change.

EdenNet 20 FP 2008 Updated sections:

• LTE PRACH Optimization INI parameters: A new parameter

EdenNet 20 FP 2007 Updated section:

• LTE PRACH Optimization GUI parameters: The description of

EdenNet 20 Updated sections:

• LTE PRACH Optimization INI parameters: The following para-

– Report achieved reuse distance

EdenNet 21 © 2021 Nokia 5

Release Change description

• Inconsistency report: The Achieved Reuse Distance Report ta-

EdenNet 19A FP 2004 No change.

EdenNet 19A FP 2003 No change.

EdenNet 19A FP 2002 No change.

EdenNet 19A FP 2001 Updated sections:

• Parameter planning: A note is added for the Huawei vendor.

EdenNet 19A FP 1912 No change.

EdenNet 19A FP 1911 Updated sections:

• Overview of LTE PRACH Optimization module

EdenNet 19A No change.

EdenNet 19 FP 1907 No change.

EdenNet 19 FP 1906 No change.

EdenNet 19 FP 1905 No change.

• Accessing LTE PRACH Optimization

EdenNet 19 • A new parameter Schedule plan provision in main-

EdenNet 21 © 2021 Nokia 6

Release Change description

• The following sections are updated:

EdenNet 18 SP1 1812 No updates.

EdenNet 18 SP1 • The description of the Email addresses (Optional) pa-

EdenNet 18 The following sections are modified:

• LTE PRACH Optimization GUI parameters

EdenNet 17 SP1 FP1 The parameter KPI based relational neighbor

EdenNet 21 © 2021 Nokia 7

Release Change description