AirScale BSC, Release FP21B,

Operating Documentation,
Issue 02

AirScale BSC Parameters

DN227435928
Issue 02
Approved on 2021-06-04

© 2021 Nokia. Nokia Confidential Information.

Use subject to agreed restrictions on disclosure and use.
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and
consulting with standards bodies to ensure that terminology is inclusive and aligned with the industry. Our future
customer documentation will be updated accordingly.
 

This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.

This document is intended for use by Nokia’s customers (“You”/ “Your”) in connection with a product purchased or
licensed from any company within Nokia Group of Companies. Use this document as agreed. You agree to notify
Nokia of any errors you may find in this document; however, should you elect to use this document for any
purpose(s) for which it is not intended, You understand and warrant that any determinations You may make or
actions You may take will be based upon Your independent judgment and analysis of the content of this document.

Nokia reserves the right to make changes to this document without notice. At all times, the controlling version is
the one available on Nokia’s site.

No part of this document may be modified.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS
DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA
THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE
OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names mentioned
in this document may be trademarks of their respective owners.

© 2021 Nokia.
documentation and
e industry. Our future

stributed or disclosed

product purchased or
d. You agree to notify
cument for any
You may make or
ontent of this document.

controlling version is

LIMITED TO ANY
MERCHANTABILITY
NT OF THIS
BUT NOT LIMITED TO
UCH AS BUT NOT
PORTUNITY OR DATA
EVEN IN THE CASE

uct names mentioned

1. Introduction
The purpose of this document is to assist users in finding parameters, their meanings, specifications, and default values. Th
managed objects and parameters are listed in alphabetical order.

2. How to read this excel report

The excel report provides a full information on the parameter dictionary. It shows the full set of parameter attributes includin
the change information.

2.1 Parameter List

This section shows the full parameter information including the following:
- abbreviated names
- managed objects
- parent/child parameter relationships
- default values
- range and step
- field descriptions
- change information

2.2 Field descriptions

Field descriptions are provided in the second row of Parameter List section. Use fold (-) and unfold (+) buttons on the left
panel to respectively hide and show the field descriptions.
cations, and default values. The

of parameter attributes including

unfold (+) buttons on the left

Managed Object Class Tree

BSC
ANE
BAL
BCF
BSTE
BTS
ADCE
ADJL
ADJW
GPC
HOC
POC
TRX
DMR
TRE
CAPLIM
DMR
DN2
ETP
MAL
MALD
MBAL
MFL
NSE
NSVL
OPERTR
OPPOOL
PCU
RA
SG
SMLC
LCSE
LMUA
SPC
TCSM
TID
TRE
TRKT
VNF
BSCSERV
DATSYNC
PEERVNF
Managed Object Class Name
Note :
BSC radio network parameter values can be empty in NetAct actual configuration when the corresponding feature license
not set in the BSC.
corresponding feature license is
Note:
See "How to Read This Report" tab for instructions
on the usage of Parameter List.

Changes between issues 01 and 02

 The Managed Object Class in
Abbreviated Name which the parameter is
MO Class
defined.

diversityUsed BSC/BCF/BTS
The user interface name for the For a parameter within a structure, this
parameter.
Full Name field
Parentgives the abbreviated name of the
Structure
structure. For standalone parameters,
this field is empty.

RX Diversity
For a structure, this field lists the The parameter datatype. Describes how
abbreviated names of all child
Child Parameters Data Type many instances of
Multiplicity
parameters. For standalone the parameter can
parameters, this field is empty. be included in the
managed object.

Enumeration 1
The parameter name used in 3GPP Describes in detail the purpose of the parameter and includes
specifications.
3GPP Name extra information on the parameter.
Description

With this parameter you define whether RX diversity is used in

the BTS.

NOTE: This parameter is allowed only for MetroSite, UltraSite,

Flexi EDGE, Flexi Multiradio, Flexi Multiradio 10, Flexi Compact
and BTSplus BTSs but with BTSplus BTS, this parameter has
no influence on RX diversity function as RX diversity will be
enabled during the hardware configuration locally in the
BTSplus.

4-way diversity is available for UltraSite, Flexi EDGE, BTSplus,

Flexi Multiradio, Flexi Multiradio 10, Flexi Compact and Horizon
site types only.

If Double Power (DPTRX) TRXs or Intelligent Downlink

Diversity (IDD) TRXs are used in Flexi EDGE BTS, the value of
this parameter must be Y.
Includes an extra information on the parameter.
Additional Information
There are two parameter categories: Basic and Advanced. The value range for the
Parameter Category parameter
Range andand stepthe value by
In Netact CM Editor there are predefined Parameter Views called which this parameter value
Basic parameters or Advanced parameters that group parameters increases or decreases
according to the Category. within the range, including
the unit in which this
Basic parameter category includes: parameter is given or shown
•- parameters
Basic parameters
which should be considered during cell deployment and 0: RX user
in the diversity is not used
interface.
must be adjusted to a particular scenario (N)
- configuration parameters (like IDs of the network elements, IP 1: RX diversity is used (Y)
addresses etc.),
- planning parameters (like neighbor definitions, frequency plan,
scrambling code plan, PCI plan, RA preamble plan etc.),
- parameters related to the dimensioning and parameters defining
operators' strategy (e.g. traffic steering, thresholds for power control,
handovers, cell reselections, high level parameters defining feature
behavior etc.)

Advanced parameter category includes network optimization and fine

tuning parameters (including those related to advanced or complex
features). The advanced parameters can be effectively moved out of
the primary focus during a regular network operation.
The formula for calculating the system The parameter value
internal
Formulavalue (for example,
for Getting ASN.1
Internal value)
Value the system
Default will use if
Value
which is used between the system there is no other value
components, for example, in provisioned or given.
uploaded files.

RX diversity is not used

(N) (0)
Additional information (if any) on the A parameter value with a Describes whether the
default
Defaultvalue.
Value Notes special
Specialfunction
Value or meaning. parameter is mandatory
Required on Creation or not.
This parameter value is outside
the normal value range. It can, Note: Mandatory parameters
for example, indicate "not with no default value defined
defined" or "don't use". must be filled in.
Optional
Describes whether the Describes where and Other parameters that affect the parameter or upon
parameter can be
Modification when the parameter is
Modified which thisParameters
Related parameter impacts.
modified in the network modified.
element and what impact
the modification has or
conditions to fulfil.
On-line BTS - limForTriggeringOscDhrMultiplexing: BSC shall
allow disabling of Rx diversity in a BTS object only if
OSC is not in use in the BTS (parameter Limit for
Triggering OSC DHR Multiplexing = 0).
TRX - dualTrxUsage: The value of this parameter
must be Y if Dual TRX Usage parameter is used in
Flexi EDGE BTS.
Dependencies between the parameter and the Informs what options or licences operator needs to
related parameters.
Parameter Relationships use to activate
Related Optionsfuctionality.

#N/A
Feature or license required to modify and take The management interfaces over
advantage of this parameter. If the system does not
Related Features which this parameter is
Interfaces
have the necessary licenses, it ignores that transferred.
parameter.

• RACApp <-> RAC

• Planner <-> RAC
• RAC <-> BSC
References (if any) to 3GPP specifications.
References
The parameter full name used in MML programs.
BSC - MML Full Name

RX diversity
The parameter abbreviated name used in MML
programs.
BSC - MML Abbreviated Name

RDIV
The parameter name used in MML commands. Informs if the parameter is supported via File Base
BSC - MML Commands Provisioning feature.
File Based Provisioning

EQM, EQO #N/A

The BTS types supported by a parameter.
Supported BTS Types

ALL