Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 1
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 2
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 4
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 5
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 6
Self Optimizing Networks – SON Procedure

NOTES:

• Antenna bearing parameter needs to be defined in plan before Optimizer

is able to process eNB cells.
• Antenna geographical location – non nw plannable ANTL parameters that
can be used by Optimizer if antennas are at different place than site
• Recommendation to user to add/merge all new BTS configurations into
same plan since then Optimizer is able to see all planned BTS, however it
is up to user if he so makes, with several separate plans the limitation is
that no “awareness” across plans at Optimizer allocation

RA41129EN08GLA0 7
Self Optimizing Networks – SON Procedure

In addition to the MRBTS and LNBTS managed objects that are unique
identifiers for sites the following parameters within these MOs are related
site ids:

PLMN-PLMN/MRBTS-<y>/LNBTS-<y>  siteID
PLMN-PLMN/MRBTS-<y>/LNBTS-<y>  enbName
PLMN-PLMN/MRBTS-<y>/LNBTS-<y>/BTSSC-1  btsId
PLMN-PLMN/MRBTS-<y>/LNBTS-<y>/BTSSC-1  btsName
PLMN-PLMN/MRBTS-<y>/LNBTS-<y>/FTM-1  systemTitle
PLMN-PLMN/MRBTS-<y>/LNBTS-<y>/FTM-1  userLabel
PLMN-PLMN/MRBTS-<y>/LNBTS-<y>/FTM-1/IPNO-1  btsId
SITE  all parameters (id, name, address, coordinates)

RA41129EN08GLA0 8
Self Optimizing Networks – SON Procedure

If parameter values are “internal” you will see number indices for the
parameter values:
<p name="amRlcPBTab1dlPollByte">0</p>
If the “UI” parameter values are used it will show more descriptive values and
possibly lists:
<list name="amRlcPBTab1">
<item>
<p name="dlPollByte">25kB</p>
<p name="ueCategory">1</p>
<p name="ulPollByte">50kB</p>
</item>
NOTE:
It is possible to create the plan input file by taking a BTS configuration file
from BTS Site Manager by replacing all occurrences of the MRBTS managed
object with PLMN-PLMN/MRBTS.
Once plan input file is imported and a plan is created, changes can be made
to the plan via CM Editor.
SITE Object will be created in CM Editor along with MRBTS object when the
plan is created via Workflow Engine. If SITE Object is not included, it can be
created within CM Editor and assigned to the MRBTS manually.

RA41129EN08GLA0 9
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 10
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 11
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 12
Self Optimizing Networks – SON Procedure

These global settings determine:

• Auto planning for PCI and eNB adjacencies
• GPS based auto identification, and the allowable tolerance of the SITE
object vs. actual GPS coordinates sent from BTS.
• Handling of temporary and auto configuration plans, if the system
automatically deletes them, or not (e.g. for troubleshooting).
• Behavior of one button planning feature (RL20)

RA41129EN08GLA0 13
Self Optimizing Networks – SON Procedure

New RL20 feature – plan file that is imported must be accurate and complete
since you will not be able to modify the plan.

RA41129EN08GLA0 14
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 15
Self Optimizing Networks – SON Procedure

NOTE:

The MRBTS objects included in the plan input file are created as ACTUAL
objects. They are management objects that are used by the Workflow Engine
during auto connection and auto configuration.

The MRBTS/LNBTS object is not an actual object until auto configuration is

successful and the eNB is able to connect and upload the LNBTS parameters
to NetAct.

The following parameters are set and updated by the system, they should
not be set manually via plan provisioning:
- Auto configuration mode
- Auto configuration plan name
- Auto configuration plan ready
- Auto configuration status

RA41129EN08GLA0 16
Self Optimizing Networks – SON Procedure

NOTE:

The Site Template name is NOT used for finding a match. The auto configuration plan needs to have
something in the Site Template Description field that matches a Site Template Description defined in
NetAct.

Site templates with empty Site Template Description parameter field will not be matched at all.

During plan creation or editing managed objects parameters of existing one, you can enter a wildcard or
regular expression as a value of “Site Template Description” parameter of a MRBTS managed object.
Such a wildcard/regular expression matching of site template description is used during ‘Site Template
Search and Select’ feature in the CM Operations Manager Workflow Engine UI.

Value of Site Template Description parameter can be inputted in one of the following formats:
- Java 1.4 regular expression format: To treat value of Site Template Description parameter as a Java
regular expression, you must start the string with / character. In this case the remaining part of the
string is going to be interpreted as a Java regular expression.
- Wildcard string format: Site Template Description parameter value is matched as a wildcard string, if it
has no / character at the beginning. The value should contain number of *,? or ** characters within. The
asterisk character * covers any content with any length. The question mark ? covers any one character.
The double asterisk character ** covers all not empty string of characters.
- Exact string: If you type the exact string, it’s being treated as an equal match.

RA41129EN08GLA0 17
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 18
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 19
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 20
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 21
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 22
Self Optimizing Networks – SON Procedure

NOTE:

The MRBTS parameter “auto configuration plan file ready” must be TRUE
before auto configuration can begin. This means no errors are found during
validation.

RA41129EN08GLA0 23
Self Optimizing Networks – SON Procedure

NOTE:

PREBTS parameter values are taken from auto configuration plan -> user does not need to define
GOMS PREBTS object separately, it is done “dynamically” by the workflow operation
• PREBTS instance ID value to be same as planned MRBTS ID
• BTS ID parameter value to be same as planned MRBTS ID
• HW ID value from MRBTS non-nw parameter AutoConnHWID (if that has planned value)
• Site ID value from MRBTS non-nw parameter AutoConnSiteID (if that has planned value)
• Coordinate values taken from BTS assigned Site object latitude, longitude, height, AutoConnGPSTolerance
parameter defined in “settings UI”
• Final iOMS IP@ copied from MRBTS/FTM/IPNO:Transport network IP address of the O&M system
• Technology information parameter automatically set to value ‘LTE’
• Version value copied from MRBTS obj. version

RA41129EN08GLA0 24
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 25
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 26
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 27
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 28
Self Optimizing Networks – SON Procedure

NOTE:

Auto configuration is enabled by default.

If no configuration is present the BTS will send a DCHP Discover try and get IP
information on how to connect to the iOMS, CMP server, and VPN GW.

RA41129EN08GLA0 29
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 30
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 31
Self Optimizing Networks – SON Procedure

RA41129EN08GLA0 32