Professional Documents
Culture Documents
Eden Net Prach 5g Guide
Eden Net Prach 5g Guide
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.
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.
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.
5G PRACH Optimization Guide DN1000008654 1-4 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
1 Summary of changes
• Dependencies
Updated sections:
New sections:
• Unlocking cells
• Locking cells
Added section:
EdenNet 19 FP 1905 Parameter name is changed from Plan PRACH Frequency Offset
(PRFO) to Plan PRACH Frequency Start (PRFO).
Added section:
EdenNet 18 SP1 1812 This is a new document that describes how to assign conflict-free PRACH
parameters for the New Radio (NR) cells which are being considered for op-
timization.
RACH is a basic procedure that is used to establish uplink synchronization and start the uplink trans-
mission.
This module assigns conflict-free PRACH parameters for the New Radio (NR) cells which are being
considered for optimization.
• Fresh Allocation: assigns conflict-free PRACH parameters for all the selected NR Cells.
• Conflict Resolution: identifies and resolves PRACH conflicts for the NR cells with respect to other
scope cells and neighboring cells.
• Inconsistency Resolution: identifies the inconsistencies between the PRACH parameters of the
own cell and resolves the inconsistency by assigning the conflict-free PRACH parameters.
Note:
The 5G PRACH Optimization module supports only internal cells. If external cells arrive (as
neighbors), they are ignored by the module.
PRACH 5G is agnostic to RAN deployment. It works for both SA (stand-alone) and NSA (non-stand-
alone) sites.
Table 2: 5G PRACH Optimization supported vendors and technologies lists the supported vendors and
technologies for the 5G PRACH Optimization module.
Vendor Technology
Nokia 5G
Ericsson 5G
• Dependencies
2.1.1 Dependencies
The 5G PRACH Optimization module requires the expected cell range information for each of the
cells.
The cell range must be provided either as CM parameters or in the cell plan file:
• If the RAN vendor provides the cell range as CM parameters, the 5G PRACH Optimization module
reads the same.
• If the RAN vendor does not provide the range information or the range information in the CM data
is incorrect, the correct cell range must be populated in the cell plan file.
For TDD-FR1 cells, Ericsson supports the following maximum cell ranges based on the preamble for-
mat:
• 5 kms
• 10 kms
Note:
• update the cell_plan.csv with the correct expected cell range value.
Or
• fill the cellRange CM parameter for each cell.
If this value is not filled for the source or neighbor FDD cell, all the cells are skipped and module exe-
cution is terminated.
• Root Sequence Index (RSI) - Root Sequence Index together with Zero Correlation Zone
Config (ZCZC) represents the code domain
• PRACH Frequency Start (PRFO) - Represents the frequency domain
• PRACH Configuration Index (PRCI) - Represents the time domain
• Zero Correlation Zone Config (ZCZC) - Zero Correlation Zone Config together with RSI
represents the code domain
Any 2 New Radio (NR) cells are considered as PRACH conflict-free, if the PRACH resources used by
them do not overlap in any of the three domains (frequency, time and code domain).
All Ericsson cells are considered to be frequency and time domain overlapping. Hence, only code do-
main differentiation is performed.
Conflict-free PRACH parameter allocation ensures better network KPIs by reducing the call setup de-
lay, handover delay, and data resuming delays.
• Open loop
• Closed loop
• 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 EdenNet User and
Administration Guide.
• When a plan is scheduled, the provision status is changed to Scheduled.
The 5G PRACH Optimization module generates a plan file for the proposed changes to PRACH pa-
rameters which need to be sent to the OSS. In addition, an exhaustive report with information about
scope cells, summary of execution, warnings or errors (if any), and so on is generated. It also lists the
recommended changes to improve the network performance. This module only runs during the main-
tenance window.
Nokia recommends that you do not execute closed loop operations of the 5G PRACH Optimization
module simultaneously for overlapping clusters or for clusters which share first or second level neigh-
bors.
If the 5G 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.
The 5G PRACH Optimization parameters are offline parameters, which means that the cells need to
be taken down before the parameter values can be changed. Currently, the Ericsson gNodeB does not
have the capability of gracefully locking down the cells. Therefore, the PCE module is required to per-
form the following operations:
• Locking cells
• Unlocking cells
1. Log in to the EdenNet application. See Accessing 5G PRACH Optimization module for more
information.
3. Select PCEmodule.
6. Click Import.
8. Click Choose File and navigate to the location of the Table 3: Ericsson NR unlocking configuration
file (Excel file) on your local system.
SON
SON SON SON
SON Region-
En- SON Market Allow-
MW al
MO SON Level
Parameter force Enforce- able
Class Node Audit Enforce- Level
Name this ment En- Enforce-
Name Rule ment
En- force- ment
Para- Rule
Only force- ment
meter Values
ment
10. Execute the PCE module in closed loop with default values (on the list of cells where the 5G
PRACH Optimization module has proposed changes and changes are pushed to the network in
Cell Locked status).
11. Import and activate the PCE5G_unlockingcells.xlsx file.(Use the same excel
created in Locking cells. Change the excel name from PCE5G_lockingcells.xlsx to
PCE5G_unlockingcells.xlsx).
Expected outcome
The administrative state of the cells can be verified using the AC lite CM Editor or the Ericsson Net-
work Manager Moshell.
1. Log in to the EdenNet application. See Accessing 5G PRACH Optimization module for more
information.
3. Select PCEmodule.
6. Click Import.
8. Click Choose File and navigate to the location of the Ericsson NR locking configuration file (Excel
file) on your local system.
SON
SON SON SON
SON Region-
En- SON Market Allow-
MW al
MO SON Level
Parameter force Enforce- able
Class Node Audit Enforce- Level
Name this ment En- Enforce-
Name Rule ment
En- force- ment
Para- Rule
Only force- ment
meter Values
ment
10. Execute the PRACH 5G module in open loop mode to identify the cells that need to be changed.
See Configuring and executing 5G PRACH Optimization module for more information.
11. Create an excel (PCE5G_lockingcells.xlsx) with a list of all the cells for which the change set
is detected.
12. Execute the PCE module in closed loop with default values (on the list of cells where the change
set is detected).
Expected outcome
The administrative state of the cells can be verified using the AC lite CM Editor or the Ericsson Net-
work Manager Moshell.
To execute the RSI changes, execute the 5G PRACH Optimization module and provision the plan.
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 5G
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 5G 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 5G PRACH Optimization module detects conflict and
optimizes the RSI and PRCI (code and time domain parameters).
• Fresh allocation
• Conflict resolution
• Inconsistency resolution
• it is hard to fix conflicts, and the expected reuse distances for 5G cells cannot be achieved.
• suitable PRACH values for the upcoming new 5G cell cannot be found.
• the success rate KPIs are poor for a group of cells or neighborhood RACH.
• the cell range is changed for cells in the network.
In this use case, the 5G PRACH Optimization module assigns conflict free PRACH parameters for all
the scope cells.
a. Assign the appropriate PRACH frequency start. The number of PRBs needed for 5G PRACH
varies based on the SCS of PRACH. If the Use position of PRACH in frequency
domain as differentiation parameter is set as No, the 5G PRACH Optimization module
retains the old value for PRFO.
b. Assign the appropriate PRACH configuration index.
For TDD, assign the first configuration index, as time domain differentiation is not yet support-
ed. For FDD, time domain differentiation is supported. Therefore, assign the configuration in-
dex supported by the gNB.
c. Assign the appropriate zero correlation zone configuration, depending on the cell range.
d. Calculate the number of consecutive root sequence indexes that are required, depending on
the cell range. Check for a non-conflicting range of root sequence index availability and assign
the starting root sequence index to the PRACH root sequence index parameter.
e. If the module fails to assign the conflict-free PRACH root sequence index, ignore the lowest
ranked undefined neighbors and proceed with 4.a. If the module fails even after ignoring all
the undefined neighbors, the module will log the warning and mark FAILURE for the cell in the
report.
Note: 4.a, 4.b, and 4.c are skipped for the Ericsson vendor.
1. Conflict detection: The 5G PRACH Optimization module detects conflicts for the scope cell with
respect to its neighboring cells. It performs the below steps for each scope cell:
If the source and neighbor cells overlap in frequency, time, and code domain resources,
then these 2 cells are said to be conflicting. The 5G PRACH module checks for frequency
domain separation if the Use position of PRACH in frequency domain as
differentiation parameter is set to Yes. Else, all the cells are considered to be
overlapping in the frequency domain.
Mark each conflicting scope cell for the conflict resolution phase.
2. Conflict resolution: For the conflicting scope cells, the 5G PRACH Optimization module resolves
conflicts by assigning conflict-free PRACH parameters. The 5G PRACH Optimization module
performs the below steps for each scope cell which is identified as conflicting based on the radio
frequency range type (FR1 or FR2), SCS, and channel bandwidth:
a. Assign the appropriate PRACH frequency start. The number of PRBs required for 5G PRACH
varies based on the SCS of PRACH. If the Use position of PRACH in frequency
domain as differentiation parameter is set to No, the 5G PRACH Optimization module
retains the old value for PRFO.
b. Assign the appropriate PRACH configuration index. For TDD, assign the first configuration
index, as time domain differentiation is not yet supported. For FDD, time domain differentiation
is supported. Therefore, assign the configuration index supported by the gNB.
c. Depending on the cell range, assign the appropriate zero correlation zone configuration.
d. Depending on the cell range, calculate the number of consecutive root sequence indexes that
are required. Check for a non-conflicting range of root sequence index availability and assign
the starting root sequence index to the PRACH root sequence index parameter.
e. If the 5G PRACH Optimization module fails to assign the conflict-free PRACH root sequence
index, ignore the lowest ranked undefined neighbors and proceed with 2.a. If the 5G PRACH
Optimization module fails even after ignoring all the undefined neighbors, then the module logs
the warning and marks FAILURE for the cell in the report.
Note: 2.a, 2.b, and 2.c are skipped for the Ericsson vendor.
1. Inconsistency detection:
The module marks the cell as inconsistent for the below cases:
• Cell is assigned with forbidden RSIs: Only this section is applicable to Ericsson.
• ZCZC is not in accordance with the cell range
• PRCI is not in accordance with the cell range
• Cell is assigned with forbidden Preamble format
• Incorrect value for PRFO
2. The 5G PRACH Optimization module marks the cell as inconsistent if it uses the forbidden values
for PRACH parameters. It performs the below steps for each scope cell:
1. Assign the appropriate PRACH frequency start. The number of PRBs required for 5G
PRACH varies based on the SCS of PRACH. If the Use position of PRACH in fre-
report.
Note: 3.c.i, 3.c.ii, and 3.c.iii are skipped for the Ericsson vendor.
• License
• CM data
• Cell plan and OSS data
5.1.1 License
The 5G PRACH Optimization license is listed in Table 5: EdenNet Licenses.
5.1.2 CM data
For details about the CM data of the 5G PRACH Optimization module, see the EdenNet module spe-
cific Data for Nokia document.
At present, the 5G PRACH Optimization module does not consider 5G PM counters or KPIs for net-
work optimization and only relies on the CM data. Support for PM KPIs to be used for network opti-
mization is planned in future releases.
The 5G PRACH Optimization module requires accurate 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 longi-
tude 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 con-
figurable distance, for example, 50 meters).
Note: Nokia recommends that you run the latitude and longitude auditing module before the
5G PRACH Optimization module is enabled in the operator network.
The below details must be available for each cell from the cell plan:
Prerequisites
a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, and cross-
OSS):
• 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.
Expected outcome
The selected module is accessed and the Configure Targets page appears.
Prerequisites
EdenNet restricts the module to making changes only to those cells selected by the user.
For more information about configuring the targets, see the Define the topology section in the Eden-
Net User and Administration Guide.
1. Select the 5G cells for configuration by clicking Filters to perform the following tasks:
• filter specific cells on the map based on Topology Filter or Center Frequency Filter and then
select target cells from the map
Or
• filter specific cells on the map based on Topology Filter or Center Frequency Filter and then
select all filtered items by clicking
Or
The selected cells appear in the Selections pane. For more information about selecting cells, see
the Selecting cells section in the EdenNet User and Administration Guide.
Note: A module may retrieve configuration and performance information for other cells
in the network that are not on the target list. For many modules, this information may
be required by the module's core algorithms. Multiple instances of the module, each
with its own target cell list are permitted and are necessary for large OMCs or OSS
configurations.
2. Click Next.
Expected outcome
The target cells are selected and the Configure Parameters page appears.
Prerequisites
1. Define the configuration parameter values. For the list of 5G PRACH Optimization parameters, see
5G PRACH Optimization GUI parameters.
Note:
• You can retain the default values or select the values from the drop-down list.
• To revert to the default parameter value, click the Default Value icon.
2. Click Next.
Expected outcome
The parameters are configured and the Select Configuration File page appears.
3. Continue with Selecting the configuration file for 5G PRACH Optimization module.
Prerequisites
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.
Expected outcome
The configuration file is selected and the Execution Type page appears.
3. Continue with Selecting the execution type for 5G PRACH Optimization module.
Prerequisites
• Successful completion of Selecting the configuration file for 5G PRACH Optimization module.
For more information about scheduling the execution, see the Configuring execution type section
in the EdenNet User and Administration Guide.
2. Click Next.
Expected outcome
The module is scheduled for execution and the Confirm Execution page appears.
Prerequisites
• Successful completion of Selecting the execution type for 5G PRACH Optimization module.
Procedure
Note: You can monitor the activities, status, and events of the 5G PRACH Optimization
module. For more information, see Monitoring 5G PRACH Optimization.
Expected outcome
The 5G PRACH Optimization module is executed based on the configured parameters and as per the
defined schedule.
Start hour of mainte- This parameter indicates the start 0 to 23 hours N/A 2
nance window time for executing the module in
closed loop. Changes will not be
provisioned before this time.
End hour of mainte- This parameter indicates the end 0 to 23 hours N/A 6
nance window time for provisioning the changes
to network when the module is run
in closed loop. Changes will not be
provisioned after this time.
Email address (Op- Email addresses to which the link N/A N/A N/A
tional) for module reports need to be sent.
Separate the email addresses with
a semi-colon or comma.
Use case selection It allows the user to run one of the Fresh allocation, N/A Conflict res-
PRACH use cases from: Conflict resolu- olution
tion, Inconsis-
• Fresh allocation (erases and
tency resolution
allocates new PRACH values)
• Conflict resolution (detects and
resolves conflicts)
Or
• Inconsistency resolution (de-
tects and resolves inconsisten-
cies) for target (scope) cells
Search distance Neighbor cells which are located 0.001 kms to 0.001 6 kms
(Coverage overlap within the defined search distance 200 kms km
strategy) from the target cell location will be
compared for coverage area over-
lap with the target cell.
Plan PRACH Con- If yes, the PRCI parameter will be Yes, No N/A No
figuration Index planned if it is supported in the tar-
(PRCI) get (scope) cell. The Expected Cell
Range is the mandatory input to
modify PRCI.
Plan Zero Corre- If yes, the ZCZC parameter will be Yes, No N/A No
lation Zone Config planned if it is supported in the tar-
(ZCZC) get (scope) cell. Cell Range is a
mandatory input to modify ZCZC.
Additionally, the PRCI must be
planned along with ZCZC.
To fix inconsisten- It defines whether to modify only Modify neces- N/A Modify nec-
cies, modify neces- those parameters which are nec- sary parameters, essary para-
sary parameters or essary or to modify from those pa- meters
as manually select-
Skip target (scope) It defines whether to skip the tar- Skip target N/A Skip target
or neighbor cell get (scope) cell or neighbor cell in (scope) cell, (scope) cell
in case of invalid case a neighbor cell is found to be Skip neighbor
neighbor invalid. cell
For example:
SON operation Set to Open loop to run the module Open loop, N/A Open loop
mode in open loop mode. Set to Closed Closed loop
loop to run the module in closed
loop mode. In open loop mode, the
module does not push parameter
changes to network elements.
Plan Name Tag Text that will be added to the Sequence which N/A Empty
names of all the plans that will be contains any
generated by this module. If the combinations of:
target of the module is a whole
• Uppercase
specific cluster (and the name
and lower-
of this cluster also matches the
case letters:
Range), then the cluster name will
[A-Za-z]
also be added to the plan name.
• Numbers:
[0-9]
• Underscore:
_
The maximum
length is 20
characters.
Schedule plan provi- If this parameter is set to True, the True, False N/A False
sion in maintenance changes are scheduled to be pro-
window visioned 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.
Note:
• This parameter is
applicable only when
AC is integrated. If
AC is not integrated,
then the plan will be
provisioned only if
it is generated with-
in the maintenance
window.
• When the plan is
scheduled to be pro-
visioned, the pro-
visioning will be at-
tempted at the start
of the maintenance
window. However,
if there are many
plans to be provi-
sioned, the plan will
be provisioned lat-
er in the mainte-
nance window. If the
plan cannot be pro-
visioned within the
maintenance window
because of a high
number of plans,
then provisioning will
not be re-attempt-
ed. You can manual-
ly provision the plan
from the Provision-
ing Logs tab.
• If the schedule is
manually deleted in
the Provisioning
Logs tab, the user
has to manually stop
the module in the
Active SON Mod-
ules window.
Root Sequence In- One or more RSIs from 0 to 137 0 to 137 N/A N/A
dex (for Preamble can be defined as forbidden for a
Format A1, A2, A3, cell which uses preamble format
B1, B2, B3, B4, C0, A1, A2, A3, B1, B2, B3, B4, C0, C2
C2 for FR1) for FR1. Enter comma separated
values. A range of values is also
allowed, for example: 56-66.
Root Sequence In- One or more RSIs from 0 to 137 0 to 137 N/A N/A
dex (for Preamble can be defined as forbidden for a
Format A1, A2, A3, cell which uses preamble format
B1, B2, B3, B4, C0, A1, A2, A3, B1, B2, B3, B4, C0, C2
C2 for FR2) for FR2. Enter comma separated
Root Sequence In- One or more RSIs from 0 to 837 0 to 837 N/A N/A
dex (for Preamble can be defined as forbidden for a
Format 0 to 3) cell which uses preamble format 0
to 3. Enter comma separated val-
ues. A range of values is also al-
lowed, for example: 1-3.
Preamble format(A1, One or more preamble formats can A1, A2, A3, B1, N/A N/A
A2, A3, B1, B2, B3, be defined forbidden for FR1. Pre- B2,
B4, C0, C2, 1, 0 for amble format A2 cannot be forbid-
B3, B4, C0, C2,
FR1) den.
1
Preamble format(A1, One or more preamble formats can A1, A2, A3, B1, N/A N/A
A2, A3, B1, B2, B3, be defined forbidden for FR2. Pre- B2,
B4, C0, C2 for FR2) amble format A2 cannot be forbid-
B3, B4, C0, C2
den.
Note:
Table 8: Supported Preamble Format for vendors lists the Preamble Formats supported.
Note: Forbidding Preamble Format B4 is not supported for Ericsson for TDD FR1 for the fol-
lowing option:
Preamble format(A1, A2, A3, B1, B2, B3, B4, C0, C2, 1, 0 for FR1)
Note: The format of each section and the parameter details are provided as part of the below
sample file.
[Global]
# Support Preamble Format 0+ when set to "Yes". Default is "No".
Accepted values are "Yes" and "No".
Support Preamble Format 0+ = No
# Generates events when set to "Yes". Default is "No". Accepted values
are "Yes" and "No"
Generate_events = No
# Indicates the initial BandWidth Part (BWP) allocation for SA and
SA+NSA configurations. When this parameter is set to 1, the coreset0
allocation is considered for the initial BWP for SA and SA+NSA
configurations.
BandWidth Profile Setting = 0
#################################################################
[Forbidden:Global]
# One or more RSI from 0 to 837 can be defined forbidden for a cell
which uses preamble format 0, Enter comma separated values. Range of
values are also allowed, for example: 4, 78-85, 90, Default: Nothing
forbidden
Root sequence index (for preamble format 0 to 3) =
# One or more RSI from 0 to 137 can be defined forbidden for a cell
which uses preamble format A1, A2, A3, B1, B2, B3, B4, C0, C2 for FR1.
Enter comma separated values. Range of values are also allowed, for
example: 6, 7-75, 90 Default: Nothing forbidden
Root sequence index (for Preamble Format A1, A2, A3, B1, B2, B3, B4, C0,
C2 for FR1) = 1,2,3-100,19,49,70,91
# One or more RSI from 0 to 137 can be defined forbidden for a cell
which uses preamble format A1, A2, A3, B1, B2, B3, B4, C0, C2 for FR2.
Enter comma separated values. Range of values are also allowed, for
example: 6, 7-75, 90 Default: Nothing forbidden
Root sequence index (for Preamble Format A1, A2, A3, B1, B2, B3, B4, C0,
C2 for FR2) = 1,2,3-100,119
Preamble format(A1, A2, A3, B1, B2, B3, B4, C0, C2, 1, 0 for FR1) =
Preamble format(A1, A2, A3, B1, B2, B3, B4, C0, C2 for FR2) =
#################################################################
[AchievedReuseDistanceSettings]
Report achieved reuse distance = No
Increment_Fix_Distance = 1
Maximum_Fix_Reuse_Distance = 12
#################################################################
[Region.Forbidden:<region_name>]
Root sequence index (for preamble format 0 to 3) =
Root sequence index (for Preamble Format A1, A2, A3, B1, B2, B3, B4, C0,
C2 for FR1) = 1,2,3-100,19,49,70,91
Root sequence index (for Preamble Format A1, A2, A3, B1, B2, B3, B4, C0,
C2 for FR2) = 1,2,3-100,119,126,129-136
Preamble format(A1, A2, A3, B1, B2, B3, B4, C0, C2, 1, 0 for FR1) =
Preamble format(A1, A2, A3, B1, B2, B3, B4, C0, C2 for FR2) =
#################################################################
# 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.
#################################################################
Prerequisites
Only users with admin privileges have permissions to modify the parameters.
• 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.
The user should have admin or SON manager access permissions to perform the Delete oper-
ation. INI files can be deleted only if they are not used by other modules.
• Activate: to activate the selected file from the list.
A file can be deactivated only when it is not used by other module instances listed under Ac-
tive SON Modules and 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: to save the new version of the configuration after editing the parameter values in the
selected INI file.
• Save As: to save the configuration with a different name.
For more details, see the Configuring a module section in the EdenNet User and Administration
Guide.
For the INI file parameters, see 5G PRACH Optimization INI parameters.
Expected outcome
The Active SON Modules and Module History appear in the left pane, and Execution Status
appears in the right pane.
3. In the left pane, select a module either from Active SON Modules or Module History.
Active SON Modules – All active SON module instances are listed in this section. An active SON
module instance is one which is in a state other than stopped, completed, or failed.
Module History - It displays SON modules in various states of inactivity such as recently stopped,
completed, or failed.
The log contains messages which provide information on the progress of the module run as well as
any warnings and errors that were encountered.
The Directory Listing For dialog box with a list of files and module names appears.
A set of excel files is listed in the Directory Listing For dialog box.
Expected outcome
Table 9: Use case settings report describes the columns in the Use case settings report tab.
Parameters planned along with PRACH root sequence index (provided they are PRACH Frequency
supported in the cells) Start and PRACH
configuration index
and Zero Correla-
tion Zone Config
Forbidden preamble format (A1, A3, B1, B2, B3, B4, C0, C2 for FR1) for region []
<region name>
Forbidden preamble format (A1, A3, B1, B2, B3, B4, C0, C2 for FR2) for region []
<region name>
Root sequence index (for preamble format 0 to 3) for region <region name> []
Root sequence index (for preamble format A1, A2, A3, B1, B2, B3, B4, C0, C2 []
for FR1) for region <region name>
Root sequence index (for preamble format A1, A2, A3, B1, B2, B3, B4, C0, C2 []
for FR2) for region <region name>
Summary
Target cells skipped from configuration since one or more basic parameters 2
(NR-ARFCNs, channel bandwidths, Locations) are missing
Target cells skipped from configuration since one or more of its neighbors has 0
basic parameters [NR-ARFCNs, channel bandwidth(s), Location(s), TDD sub-
frame configuration] missing
Target cells skipped from configuration since one or more of its neighbors have 0
missing or invalid mandatory PRACH input values [PRFO, PRCI, ZCZC, RSI or
Expected cell range]
Target cells skipped from configuration due to missing or invalid SS Block Sub- 10
carrier Spacing
Table 11: PRACH validation warnings describes the columns in the PRACH validation warnings tab.
Warning Example
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCELL-4
Algorithm behavior NR cell skipped from PRACH configuration due to missing or invalid chan-
nel bandwidth
Table 12: Coverage overlap warnings describes the columns in the Coverage overlap warnings tab.
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCELL-4
Results
Preamble Format 0
Push Status
Table 14: Push Status is applicable only for closed loop execution.
Status SUCCESS
Table 15: Achieved Reuse Distance Report describes the columns in the Achieved Reuse Distance
Report tab.
• 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 16: Use case settings report describes the columns in the Results tab.
Parameters planned along with PRACH root sequence index (provided they are None
supported in the cells)
Forbidden preamble format (A1, A3, B1, B2, B3, B4, C0, C2 for FR1) for region None
<region name>
Forbidden preamble format (A1, A3, B1, B2, B3, B4, C0, C2 for FR2) for region None
<region name>
Root sequence index (for preamble format 0 to 3) for region <region name> []
Root sequence index (for preamble format A1, A2, A3, B1, B2, B3, B4, C0, C2 []
for FR1) for region <region name>
Root sequence index (for preamble format A1, A2, A3, B1, B2, B3, B4, C0, C2 []
for FR2) for region <region name>
Summary
Target cells skipped from configuration since one or more basic parameters 0
(NR-ARFCNs, channel bandwidths, Locations) are missing
Target cells skipped from configuration since one or more of its neighbors has 2
basic parameters (NR-ARFCNs, channel bandwidths, Locations, TDD subframe
configuration) missing
Target cells skipped from configuration since one or more of its neighbors have 0
missing or invalid mandatory PRACH input values (PRFO, PRCI, ZCZC, 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 successful configuration and new changes proposed to push 2
into network
Target cells skipped from configuration due to missing or invalid SS Block Sub- 10
carrier Spacing
Table 18: PRACH validation warnings describes the columns in the PRACH validation warnings tab.
Warning Example
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCELL-1
Algorithm behavior NR cell skipped from PRACH configuration due to missing or invalid chan-
nel bandwidth
Table 19: Coverage overlap warnings describes the columns in the Coverage overlap warnings tab.
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCELL-4
Conflicts
Results
Preamble Format 0
Push Status
Table 22: Push Status is applicable only for closed loop execution.
Status SUCCESS
Table 23: Achieved Reuse Distance Report describes the columns in the Achieved Reuse Distance
Report tab.
• 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 24: Use case settings report describes the columns in the Use case settings report tab.
Parameters planned along with PRACH root sequence index (provided they are PRACH Frequency
supported in the cells) Start and PRACH
configuration index
and Zero Correla-
tion Zone Config
To fix inconsistencies, modify necessary parameters or as manually selected in Use manual selec-
UI (Inconsistency) tion
Forbidden Preamble format (A1, A3, B1, B2, B3, B4, C0, C2 for FR2) for region []
<region name>
Forbidden Preamble format (A1, A3, B1, B2, B3, B4, C0, C2 for FR1) for region []
<region name>
Forbidden Root Sequence Index (for Preamble Format 0 to 3) for region <re- []
gion name>
Forbidden Root Sequence Index (for Preamble Format A1, A2, A3, B1, B2, B3, []
B4, C0, C2 for FR1) for region <region name>
Forbidden Root Sequence Index (for Preamble Format A1, A2, A3, B1, B2, B3, []
B4, C0, C2 for FR2) for region <region name>
Summary
Target cells skipped from configuration since one or more basic parameters 0
(NR-ARFCNs, channel bandwidths, Locations) are missing
Target cells skipped from configuration since one or more of its neighbors has 0
basic parameters (NR-ARFCNs, channel bandwidths, Locations, TDD subframe
configuration) missing
Target cells skipped from configuration since one or more of its neighbors have 0
missing or invalid mandatory PRACH input values (PRFO, PRCI, ZCZC, 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 successful configuration and new changes proposed to push 23
into network
Target cells skipped from configuration due to missing or invalid SS Block Sub- 10
carrier Spacing
Table 26: PRACH validation warnings describes the columns in the PRACH validation warnings tab.
Warning Example
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCEL-4
Algorithm behavior NR cell skipped from PRACH configuration due to missing or invalid chan-
nel bandwidth
Table 27: Coverage overlap warnings describes the columns in the Coverage overlap warnings tab.
Cell DN PLMN-PLMN/MRBTS-1/NRBTS-1/NRCELL-4
Inconsistencies
Results
Preamble Format 0
Push Status
Table 30: Push Status is applicable only for closed loop execution.
Status SUCCESS
Table 31: Achieved Reuse Distance Report describes the columns in the Achieved Reuse Distance
Report tab.
• 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.
3. From the Module/Service filter, click the required PRACH instance to view the event logs.
The event logs can also be viewed using the following filters:
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.
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.
Expected outcome
Category: PRACH_Optimization_5G
• Fresh allocation
• Conflict resolution
• Inconsistency resolution
PRACH_Skipped_cell warning Indicates the target cells and neighbor cells (if any)
which are skipped from PRACH optimization for the fol-
lowing use cases:
• Fresh allocation
• Conflict resolution
• Inconsistency resolution
PRACH_Unresolved_con- warning Indicates which target cells and neighbor cells have un-
flicts resolved conflicts. It also indicates the reason for not
resolving the conflict.
For more information, see the Configure and monitor SON modules section in the EdenNet User and
Administration Guide document.