You are on page 1of 138

BSC3119

Nokia BSC/TCSM, Rel. S12, Product


Documentation, v.1

EE - Base Station Controller


Parameter Handling in BSC

DN9813184 # Nokia Corporation 1 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the use
of Nokia's customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without the
prior written permission of Nokia. The document has been prepared to be used by professional
and properly trained personnel, and the customer assumes full responsibility when using it.
Nokia welcomes customer comments as part of the process of continuous development and
improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding but
shall be defined in the agreement made between Nokia and the customer. However, Nokia has
made all reasonable efforts to ensure that the instructions contained in the document are
adequate and free of material errors and omissions. Nokia will, if necessary, explain issues
which may not be covered by the document.
Nokia's liability for any errors in the document is limited to the documentary correction of errors.
NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT
OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY
LOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according to
the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright © Nokia Corporation 2007. All rights reserved.

2 (138) # Nokia Corporation DN9813184


Issue 19-1 en
Contents

Contents

Contents 3

List of tables 5

List of figures 6

Summary of changes 7

EE - BASE STATION CONTROLLER PARAMETER HANDLING IN


BSC 13

EEM MODIFY GENERAL BASE STATION CONTROLLER


PARAMETERS 15

EEN MODIFY RADIO NETWORK SUPERVISION PARAMETERS 35

EEQ MODIFY MISCELLANEOUS PARAMETERS 45

EEV MODIFY QUALITY OF SERVICE PARAMETERS <option> 57

EET MODIFY PRIORITY LEVEL TO SUBSCRIBER TYPE RELATION


<option> 65

EEH MODIFY DFCA PARAMETERS <option> 67

EEJ MODIFY GPRS PARAMETERS <option> 75

EER PREPARE DATABASE FOR DOWNLOADING OF BACKGROUND


DATA 83

EEG CONTROL ACTIVATION OF BACKGROUND DATA 85

EEE CONTROL ACTIVATION OF RNW PLAN 89

EEK OUTPUT RNW PLAN DATA ACTIVATION STATES 97

EEO OUTPUT BASE STATION CONTROLLER PARAMETERS 103

EEI OUTPUT RADIO NETWORK CONFIGURATION 109

EEL OUTPUT TRX RADIO TIME SLOTS 117

EEP OUTPUT BACKGROUND DATA ACTIVATION STATES 123

EEC CREATE LAC TO SPC MAPPING INFO <option> 127

EED DELETE LAC TO SPC MAPPING INFO <option> 131

DN9813184 # Nokia Corporation 3 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

EEF MODIFY LAC TO SPC MAPPING INFO <option> 133

EES OUTPUT LAC TO SPC MAPPING INFO <option> 137

4 (138) # Nokia Corporation DN9813184


Issue 19-1 en
List of tables

List of tables

DN9813184 # Nokia Corporation 5 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

List of figures

6 (138) # Nokia Corporation DN9813184


Issue 19-1 en
Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.

Changes made between issues 19–1 and 19


EEE CONTROL ACTIVATION OF RNW PLAN
A new state has been added to the execution printout
abbreviations.
EEK OUTPUT RNW PLAN DATA ACTIVATION STATES
A new state has been added to the execution printout
abbreviations.

Changes made between issues 19 and 18–1

Editorial changes.
EEQ MODIFY MISCELLANEOUS PARAMETERS
New parameters internal HO to external allowed, TCH
transaction count and max TCH transaction rate have been
added.
Parameters soft blocking C/N HR, soft blocking C/N 14.4,
soft blocking C/N AMR FR, and soft blocking C/N AMR
HR have been made optional.
The execution printout has been updated.
EEU MODIFY DYNAMIC HOTSPOT PARAMETERS
<option>
Command has been removed
EEV References to GPRS NS Layer Handling have been
changed into references to Gb Interface Handling.
Information on EQoS removed because the feature is not
supported in S12.
EEH MODIFY DFCA PARAMETERS

DN9813184 # Nokia Corporation 7 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

A new parameter SAIC DL C/I offset has been added.


The execution printout has been updated.
EEJ MODIFY GPRS PARAMETERS
A new command.
EEG CONTROL ACTIVATION OF BACKGROUND DATA
Additional information about user confirmation has been
added.
EEE CONTROL ACTIVATION OF RNW PLAN
A new command.
EEK OUTPUT RNW PLAN DATA ACTIVATION STATES
A new command.
EEO OUTPUT BASE STATION CONTROLLER
PARAMETERS
The execution printout has been updated.
Information on EQoS removed because the feature is not
supported in S12.
EEI OUTPUT RADIO NETWORK CONFIGURATION
The execution printouts have been updated.

Changes made between issues 18–1 and 18

Editorial changes.

Changes made between issues 18 and 17

The BCF, BTS and SEG ID fields in all printouts have been extended from three
digits to four digits.
EEM MODIFY GENERAL BASE STATION CONTROLLER
PARAMETERS
New parameters NACC enabled,NCCR control mode,
NCCR idle mode reporting period,NCCR transfer mode
reporting period,NCCR return to old cell time,NCCR
target cell penalty time,NCCR neighbor cell penalty,
WCDMA FDD NCCR enabled and WCDMA FDD
NCCR preferred have been added.
EEQ MODIFY MISCELLANEOUS PARAMETERS

8 (138) # Nokia Corporation DN9813184


Issue 19-1 en
Summary of changes

New parameters RX level based TCH access,IMSI based


handover GSM cells anonymous MS,IMSI based
handover WCDMA cells anonymous MS,delay of HO and
PC for emergency calls,Internal HO to external allowed,
TCH transaction count and max TCH transaction rate have
been added. Parameters soft blocking C/N FR,soft
blocking C/N HR,soft blocking C/N AMR FR,soft
blocking C/N AMR HR and soft blocking C/N 14.4 have
been moved from command EEH to EEQ.
EEV MODIFY QUALITY OF SERVICE PARAMETERS
<OPTION>
The following new parameters have been added: streaming
traffic class scheduling weight for ARP 1,streaming traffic
class scheduling weight for ARP 2,streaming traffic class
scheduling weight for ARP 3,interactive 1 traffic class
scheduling weight for ARP 1,interactive 1 traffic class
scheduling weight for ARP 2,interactive 1 traffic class
scheduling weight for ARP 3,interactive 2 traffic class
scheduling weight for ARP 1,interactive 2 traffic class
scheduling weight for ARP 2,interactive 2 traffic class
scheduling weight for ARP 3,interactive 3 traffic class
scheduling weight for ARP 1,interactive 3 traffic class
scheduling weight for ARP 2,interactive 3 traffic class
scheduling weight for ARP 3,background traffic class
scheduling weight for ARP 1,background traffic class
scheduling weight for ARP 2,background traffic class
scheduling weight for ARP 3,interactive 1 traffic class
PFC NRT nominal bitrate for ARP 1 <option>,interactive
1 traffic class PFC NRT nominal bitrate for ARP 2
<option>,interactive 1 traffic class PFC NRT nominal
bitrate for ARP 3 <option>,interactive 2 traffic class PFC
NRT nominal bitrate for ARP 1 <option>,interactive 2
traffic class PFC NRT nominal bitrate for ARP 2
<option>,interactive 2 traffic class PFC NRT nominal
bitrate for ARP 3 <option>,interactive 3 traffic class PFC
NRT nominal bitrate for ARP 1 <option>,interactive 3
traffic class PFC NRT nominal bitrate for ARP 2
<option>,interactive 3 traffic class PFC NRT nominal
bitrate for ARP 3 <option>,background traffic class PFC
NRT nominal bitrate for ARP 1 <option>,background
traffic class PFC NRT nominal bitrate for ARP 2
<option>,background traffic class PFC NRT nominal
bitrate for ARP 3 <option>,best effort ARP 1 PFC
predefined nominal bitrate <option>,best effort ARP 2
PFC predefined nominal bitrate <option>,best effort ARP
3 PFC predefined nominal bitrate <option>,signalling PFC
predefined nominal bitrate <option>,SMS PFC predefined

DN9813184 # Nokia Corporation 9 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

nominal bitrate <option>,streaming traffic class


scheduling theta for ARP 1 <option>,streaming traffic
class scheduling theta for ARP 2 <option>,streaming
traffic class scheduling theta for ARP 3 <option>,
interactive 1 traffic class scheduling theta for ARP 1
<option>,interactive 1 traffic class scheduling theta for
ARP 2 <option>,interactive 1 traffic class scheduling theta
for ARP 3 <option>,interactive 2 traffic class scheduling
theta for ARP 1 <option>,interactive 2 traffic class
scheduling theta for ARP 2 <option>,interactive 2 traffic
class scheduling theta for ARP 3 <option>,interactive 3
traffic class scheduling theta for ARP 1 <option>,
interactive 3 traffic class scheduling theta for ARP 2
<option>,interactive 3 traffic class scheduling theta for
ARP 3 <option>,background traffic class scheduling theta
for ARP 1 <option>,background traffic class scheduling
theta for ARP 2 <option>,background traffic class
scheduling theta for ARP 3 <option>,QC reallocation
action trigger threshold,QC NCCR action trigger
threshold,QC QoS renegotiation action trigger threshold,
QC drop action trigger threshold,PFC predefined traffic
class for best effort ARP 1 <option>,PFC predefined
traffic class for best effort ARP 2 <option>,PFC
predefined traffic class for best effort ARP 3 <option>,
PFC predefined traffic class for signaling <option>,PFC
predefined traffic class for SMS <option>,PFC unack
BLER limit for SDU error ratio 1,PFC unack BLER limit
for SDU error ratio 2,PFC unack BLER limit for SDU
error ratio 3,PFC unack BLER limit for SDU error ratio 4,
PFC unack BLER limit for SDU error ratio 5,PFC unack
BLER limit for SDU error ratio 6,PFC ack BLER limit for
transfer delay 1,PFC ack BLER limit for transfer delay 2,
PFC ack BLER limit for transfer delay 3,PFC ack BLER
limit for transfer delay 4 and PFC ack BLER limit for
transfer delay 5.
EEH MODIFY DFCA PARAMETERS
Parameter expected BSC-BSC interface delay has been
added. The value ranges of the following parameters have
changed: soft blocking C/I FR,soft blocking C/I HR,soft
blocking C/I 14.4,soft blocking C/I AMR FR and soft
blocking C/I AMR HR.
EEO OUTPUT BASE STATION CONTROLLER
PARAMETERS
New parameters have been added to execution printouts.
EEC CREATE LAC TO SPC MAPPING INFO

10 (138) # Nokia Corporation DN9813184


Issue 19-1 en
Summary of changes

The description of parameter signaling point code has


been modified. The execution printout has been updated.
EEF MODIFY LAC TO SPC MAPPING INFO
The description of parameter signaling point code has
been modified. The execution printout has been updated.
EES OUTPUT LAC TO SPC MAPPING INFO
The execution printout has been updated.

DN9813184 # Nokia Corporation 11 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

12 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EE - BASE STATION CONTROLLER PARAMETER HANDLING IN BSC

EE - BASE STATION CONTROLLER


PARAMETER HANDLING IN BSC
The commands of the command group are used for

.
outputting and changing the BSC object's parameters
. outputting the radio network configuration
. outputting the TRX's radio time slots in a given operational state
. handling and outputting the background data state
. creating , deleting, changing and outputting the LAC to SPC mapping info

in the BSDATA (BSS Radio Network Configuration Database).

Menu of the command group:

BASE STATION CONTROLLER PARAMETER HANDLING COMMANDS


? ..... DISPLAY MENU
M: ..... MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS
N: ..... MODIFY RADIO NETWORK SUPERVISION PARAMETERS
Q: ..... MODIFY MISCELLANEOUS PARAMETERS
V: ..... MODIFY QUALITY OF SERVICE PARAMETERS <option>
T: ..... MODIFY PRIORITY LEVEL TO SUBSCRIBER TYPE RELATION <option>
H: ..... MODIFY DFCA PARAMETERS <option>
J: ..... MODIFY GPRS PARAMETERS <option>
R: ..... PREPARE DATABASE FOR DOWNLOADING OF BACKGROUND DATA
G: ..... CONTROL ACTIVATION OF BACKGROUND DATA
E: ..... CONTROL ACTIVATION OF RNW PLAN
K: ..... OUTPUT RNW PLAN DATA ACTIVATION STATES
O: ..... OUTPUT BASE STATION CONTROLLER PARAMETERS
I: ..... OUTPUT RADIO NETWORK CONFIGURATION
L: ..... OUTPUT TRX RADIO TIME SLOTS
P: ..... OUTPUT BACKGROUND DATA ACTIVATION STATES
C: ..... CREATE LAC TO SPC MAPPING INFO <option>
D: ..... DELETE LAC TO SPC MAPPING INFO <option>
F: ..... MODIFY LAC TO SPC MAPPING INFO <option>
S: ..... OUTPUT LAC TO SPC MAPPING INFO <option>
Z; ..... RETURN TO MAIN LEVEL

DN9813184 # Nokia Corporation 13 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The commands in this command group are:


EEM MODIFY GENERAL BASE STATION CONTROLLER
PARAMETERS
EEN MODIFY RADIO NETWORK SUPERVISION
PARAMETERS
EEQ MODIFY MISCELLANEOUS PARAMETERS
EEV MODIFY QUALITY OF SERVICE PARAMETERS
<option>
EET MODIFY PRIORITY LEVEL TO SUBSCRIBER TYPE
RELATION <option>
EEH MODIFY DFCA PARAMETERS <option>
EEJ MODIFY GPRS PARAMETERS <option>
EER PREPARE DATABASE FOR DOWNLOADING OF
BACKGROUND DATA
EEG CONTROL ACTIVATION OF BACKGROUND DATA
EEE CONTROL ACTIVATION OF RNW PLAN
EEK OUTPUT RNW PLAN DATA ACTIVATION STATES
EEO OUTPUT BASE STATION CONTROLLER
PARAMETERS
EEI OUTPUT RADIO NETWORK CONFIGURATION
EEL OUTPUT TRX RADIO TIME SLOTS
EEP OUTPUT BACKGROUND DATA ACTIVATION
STATES
EEC CREATE LAC TO SPC MAPPING INFO <option>
EED DELETE LAC TO SPC MAPPING INFO <option>
EEF MODIFY LAC TO SPC MAPPING INFO <option>
EES OUTPUT LAC TO SPC MAPPING INFO <option>

14 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

EEM MODIFY GENERAL BASE STATION


CONTROLLER PARAMETERS
Function With the EEM command you modify a BSC object's general parameters in the
BSDATA.

Parameters number of preferred cells, GSM macrocell threshold, GSM microcell threshold,
DCS macrocell threshold, DCS microcell threshold, MS distance behaviour, BTS
site battery backup forced HO timer <option>, enable emergency call on FACCH,
enable answer to paging call on FACCH <option>, enable ordinary calls on
FACCH <option>, enable call re-establishment on FACCH <option>, TCH in
handover <option>, lower limit for FR TCH resources <option>, upper limit for
FR TCH resources <option>, BSC call number <option>, AMH upper load
threshold <option>, AMH lower load threshold <option>, AMH max load of
target cell <option>, AMR configuration in handovers <option>, initial AMR
channel rate <option>, slow AMR LA enabled <option>, AMR set grades
enabled <option>, free TSL for CS downgrade <option>, free TSL for CS
upgrade <option>, TRHO guard time, HO preference order interference DL, HO
preference order interference UL, load rate for channel search, triggering
threshold for service area penalty <option>, penalty trigger measurement period
<option>, service area penalty time <option>, CS TCH allocate RTSL0 <option>,
CS TCH allocation calculation <option>, NACC enabled <option>: NCCR
control mode <option>, NCCR idle mode reporting period <option>, NCCR
transfer mode reporting period <option>, NCCR return to old cell time <option>,
NCCR target cell penalty time <option>, NCCR neighbor cell penalty <option>,
WCDMA FDD NCCR enabled <option>, WCDMA FDD NCCR preferred
<option>;

Syntax

EEM: ( NPC = <number of preferred cells> |


GMAC = <GSM macrocell threshold> |
GMIC = <GSM microcell threshold> |
DMAC = <DCS macrocell threshold> |
DMIC = <DCS microcell threshold> |
DISB = <MS distance behaviour> |
TIM = <BTS site battery backup forced HO timer> <option> |

DN9813184 # Nokia Corporation 15 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

EEF = <enable emergency call on FACCH> |


EPF = <enable answer to paging call on FACCH> <option> |
EOF = <enable ordinary calls on FACCH> <option> |
ERF = <enable call re-establishment on FACCH> <option> |
HRI = <TCH in handover> <option> |
HRL = <lower limit for FR TCH resources> <option> |
HRU = <upper limit for FR TCH resources> <option> |
BCN = <BSC call number> <option> |
AUT = <AMH upper load threshold> <option> |
ALT = <AMH lower load threshold> <option> |
AML = <AMH max load target cell> <option> |
ACH = <AMR configuration in handovers> <option> |
IAC = <initial AMR channel rate> <option> |
SAL = <slow AMR LA enabled> <option> |
ASG = <AMR set grades enabled> <option> |
CSD = <free TSL for CS downgrade> <option> |
CSU = <free TSL for CS upgrade> <option> |
TGT = <TRHO guard time> |
HDL = <HO preference order interference DL> |
HUL = <HO preference order interference UL> |
CLR = <load rate for channel search> |
TTSAP = <triggering threshold for service area penalty> <option> |
PTMP = <penalty trigger measurement period> <option> |
SAPT = <service area penalty time> <option> |
CTR = <CS TCH allocate RTSL0> <option> |
CTC = <CS TCH allocation calculation> <option> |
NACC = <NACC enabled> <option> :

NCM = <NCCR control mode> <option> |


NIRP = <NCCR idle mode reporting period> <option> |
NTRP = <NCCR transfer mode reporting period> <option> |
NOCT = <NCCR return to old cell time> <option> |
NTPT = <NCCR target cell penalty time> <option> |
NNCP = <NCCR neighbor cell penalty> <option> |
WFNE = <WCDMA FDD NCCR enabled> <option> |
WFNP = <WCDMA FDD NCCR preferred> <option> ) ... ;

Parameter number of preferred cells


explanations
NPC = decimal number

With this parameter you define the maximum number of preferred cell identifiers
that the BSC sends to the MSC in the handover required message.

The values range from 1 to 16 preferred cell identifiers.

GSM macrocell threshold

GMAC = decimal number in steps of two

With this parameter you define the macrocell size by means of the maximum
transmission power of the MS in a GSM cell.

16 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

The values range from 5 to 39 dBm. If you set the parameter value at 5 dBm, the
division of cells into macrocells and microcells is not in use.

GSM microcell threshold

GMIC = decimal number in steps of two

With this parameter you define the microcell size by means of the maximum
transmission power of the MS in a GSM cell.

The values range from 5 to 39 dBm. If you set the parameter value at 39 dBm, the
division of cells into macrocells and microcells is not in use.

DCS macrocell threshold

DMAC = decimal number

With this parameter you define the macrocell size by means of the maximum
transmission power of the MS in a GSM 1800 or a GSM 1900 cell. If you set the
parameter value at 0 dBm, the division of cells into macrocells and microcells is
not in use.

The values are


for GSM 1800: 0...36 dBm with 2 dBm step
for GSM 1900: 0...32 dBm with 2 dBm step and 33 dBm with 1 dBm

DCS microcell threshold

DMIC = decimal number

With this parameter you define the microcell size by means of the maximum
transmission power of the MS in a GSM 1800 or a GSM 1900 cell. If you set the
parameter value at 36 dBm in GSM 1800 or 33 dBm in GSM 1900, the division
of cells into macrocells and microcells is not in use.

The values are


for GSM 1800: 0...36 dBm with 2 dBm step
for GSM 1900: 0...32 dBm with 2 dBm step and 33 dBm with 1 dBm

MS distance behaviour

With this parameter you define the executions allowed after the timing advance
has exceeded the threshold.

DN9813184 # Nokia Corporation 17 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The value range is 0...60 and 255.

Parameter Value Explanation


DISB = 0 Release immediately.
1 1 second time to try handover, release if handover is unsuccessful.
2 2 seconds time to try handover, release if handover is unsuccessful.
...
60 60 seconds time to try handover, release if handover is
unsuccessful.
255 No release, only handover attempts.

BTS site battery backup forced HO timer <option>

TIM = decimal number

With this parameter you define the maximum time period during which handover
is attempted in TRXs if a mains power failure is detected in the BTS and the spare
power supply is being taken into use. After the defined period has elapsed,
remaining calls are force-released. This is done in order to make the battery last
longer during power cuts.

The values range from 1 to 500 seconds.

enable emergency call on FACCH

With this parameter you enable or disable the emergency call setup on FACCH.
The emergency call setup on FACCH is possible only in those cells in which the
emergency call is not restricted (BTS level parameter EC). The FACCH call setup
is only possible when SDCCH congestion occurs.

The values are:

Parameter Value Explanation


EEF = Y Enable emergency call setup on FACCH.
N Disable emergency call setup on FACCH.

enable answer to paging call on FACCH <option>

With this parameter you enable or disable an answer to the paging call setup on
FACCH. The FACCH call setup is only possible when SDCCH congestion
occurs. The values are:

18 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

Parameter Value Explanation


EPF = Y Enable answer to paging call setup on FACCH.
N Disable answer to paging call setup on FACCH.

enable ordinary calls on FACCH <option>

With this parameter you enable or disable the ordinary call setup on FACCH. The
FACCH call setup is only possible when SDCCH congestion occurs. The values
are:

Parameter Value Explanation


EOF = Y Enable ordinary calls setup on FACCH.
N Disable ordinary calls setup on FACCH.

enable call re-establishment on FACCH <option>

With this parameter you enable or disable the call re-establishment setup on
FACCH. The call re-establishment setup on FACCH is possible only in those
cells in which the call re-establishment (BTS level parameter RE) is allowed. The
FACCH call setup is only possible when SDCCH congestion occurs. The values
are:

Parameter Value Explanation


ERF = Y Enable call re-establishment setup on FACCH.
N Disable call re-establishment setup on FACCH.

TCH in handover <option>

HRI = decimal number

With this parameter you define the traffic channel allocation during BSS internal
or external handovers. The parameter controls the target cell selection and the
TCH channel rate and speech codec determination in traffic channel allocation.
The values are:

Parameter Value Explanation


HRI = 1 The call serving type of TCH has to be allocated primarily. The call
serving type of speech codec inside the call serving type of TCH can
change.

DN9813184 # Nokia Corporation 19 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Parameter Value Explanation


2 Primary allocation is preferred for the call serving type of TCH and the
call serving type of speech codec during the speech connection. The
channel rate change is possible during data connection, if necessary,
and if the radio interface data rate allows it.
3 The channel rate and speech codec changes are denied totally.
4 The preferred channel rate of TCH and preferred speech codec have
to be primarily allocated.
5 TCH has to be allocated primarily from the best BTS of the handover
candidate list.

lower limit for FR TCH resources <option>

HRL = decimal number

With this parameter you define the lower limit for the percentage of free full rate
resources. Full rate TCHs are allocated until the number of free full rate resources
is reduced below the value of the parameter. The half rate resources are then
allocated.

The parameter controls the TCH channel rate determination on the BSC level
according to the cell load in traffic channel allocation.

The values range from 0 to 100 %.

Parameters HRL and HRU can have the same values and effects as the BTS
object parameters FRL and FRU. When the BTS level parameters FRL and FRU
have reasonable values (FRL is equal to or smaller than FRU), the BSC level
parameters are not significant in TCH allocation. Otherwise the control of the
BSC object parameters will be followed. The cell load control will be applied
only if the preferred TCH channel rate is given by MSC.

During optional Half Rate, the parameter controls the TCH channel rate
determination on BSC level according to the cell load in traffic channel
allocation. Full rate TCHs are allocated until the number of free full rate resources
is reduced below the value of the parameter. After that half rate resources are
allocated. During optional Adaptive Multi Rate (AMR) Speech Codec the
parameter controls the packing of FR AMR calls to HR calls on BSC level
according to the cell load. Packing is done via an intra-cell handover. Packing is
active when the number of free full rate resources is reduced below the value of
the parameter and is actually triggered by a new channel allocation for BSC. The
principle in packing is that the number of free full rate resources increases by one
compared to the situation before the new channel allocation.

upper limit for FR TCH resources <option>

20 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

HRU = decimal number

With this parameter you define the upper limit for the percentage of free full rate
resources. Full rate TCHs are allocated when the number of free full rate
resources exceeds the value of the parameter.

The parameter controls the TCH channel rate determination on the BSC level
according to the cell load in traffic channel allocation.

The values range from 0 to 100 %.

Parameters HRL and HRU can have the same values and effects as the BTS
object parameters FRL and FRU. When the BTS level parameters FRL and FRU
have reasonable values (FRL is equal to or smaller than FRU), the BSC level
parameters are not significant in TCH allocation. Otherwise the control of the
BSC object parameters will be followed. The cell load control will be applied
only if the preferred TCH channel rate is given by MSC.

During optional Half Rate, the parameter controls the TCH channel rate
determination on BSC level according to the cell load in traffic channel
allocation. Full rate TCHs are allocated when the number of free full rate
resources increases above the value of the parameter. During optional AMR the
parameter controls the packing of FR AMR calls to HR calls on BSC level
according to the cell load. Packing becomes inactive when the number of free full
rate resources increases above the value of the parameter.

BSC call number <option>

BCN = decimal number

With this parameter you define the BSC ISDN call number. The values range
from 0000 to 999999999999999 (from four to 15 digits).

AMH upper load threshold <option>

AUT = decimal number

With this advanced multilayer handling parameter you define the upper threshold
for the load of the base station. The parameter is used to trigger BSC-controlled
traffic reason handovers.

The values range from 0 to 100 %.

DN9813184 # Nokia Corporation 21 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Note

If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.

AMH lower load threshold <option>

ALT = decimal number

With this parameter you define the lower threshold for the load of the base
station. The parameter is used to trigger advanced multilayer handling
functionality with IUO and/or Dual Band/microcell SW products.

The values range from 0 to 100 %.

Note

If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.

AMH max load of target cell <option>

AML = decimal number

With this advanced multilayer handling parameter you define the maximum
traffic load in the adjacent cell allowed for a target cell of traffic reason handover
(TRHO).

The values range from 0 to 100 %.

Note

If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.

AMR configuration in handovers <option>

With this parameter you define the preference between the currently used
multirate configuration and the one defined for the target BTS during internal and
external handovers. The values are:

22 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

Parameter Value Explanation


ACH = 1 The currently used multirate configuration is preferred in further
channel allocations.
2 The multirate configuration of the target BTS is preferred in further
channel allocations.

initial AMR channel rate <option>

With this parameter you define the initial channel in call setup, internal inter–cell
handover (HO) and external HO for an Adaptive Multi Rate (AMR) call. The
values are:

Parameter Value Explanation


IAC = 1 Any Rate, there are not any extra requirements for the parameter
and the chosen channel rate is defined by taking into account the
currently used information for channel allocation.
2 AMR FR is allocated despite of the values of the currently used
information for channel allocation.

slow AMR LA enabled <option>

With this parameter you define the AMR link adaptation (LA) mode within the
BSS. Alternatives are fast LA or slow LA. During the fast LA mode the BTS
allows the inband codec mode changes on every other TCH frame whereas during
the slow LA mode the BTS allows inband codec mode changes only on SACCH
frame interval. The values are:

Parameter Value Explanation


SAL = Y Enable slow AMR LA mode
N Fast LA mode is used

AMR set grades enabled <option>

With this parameter you define whether the codec mode set downgrades are
applied or not during internal HOs and whether upgrades are applied or not after
internal HOs. The source side downgrade is used to align the source side codec
set with the one chosen for the target side in order to utilize the uni-directional
downlink connection for the target side. The utilization of the uni-directional
downlink connection decreases the amount of muting experienced in the speech
path connection during the internal HO. The target side upgrade is done to utilize
that original AMR codec set of the target BTS which was not chosen for the
target side because of the target side alignment with the source side during
internal HO. The reason for this alignment is the same as in the downgrade case.

DN9813184 # Nokia Corporation 23 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Parameter Value Explanation


ASG = Y Downgrades and upgrades are applied
N Downgrades and upgrades are not applied

free TSL for CS downgrade <option>

CSD = decimal number

With this parameter you define a safety margin for the circuit switched traffic. If
the number of free TSL(s) in a BTS becomes less than the margin defined by the
parameter then a GPRS downgrade is started.

The values range from 0 to 100 %. Value 0 % means that no GPRS downgrade is
done to maintain a safety margin.

free TSL for CS upgrade <option>

CSU = decimal number

With this parameter you define a safety margin for the circuit switched traffic.
This margin is examined when deciding if a GPRS upgrade is allowed in a BTS.
A GPRS upgrade may be done if the number of free TSLs in a BTS will still be at
least the margin defined by the parameter after the upgrade. Actually the
parameter states how many seconds after an upgrade the probability for a GPRS
downgrade should be no more than 5 %. The BSC defines the number of TSLs
for the safety margin according to the given time and the number of TRXs in the
BTS.

The values range from 0 to 10 s. Value 0 means that no margin is maintained in


GPRS upgrade.

TRHO guard time

TGT = decimal number

With this parameter you define the guard time after a BSC-controlled or an MSC-
controlled TRHO, during which a handover back to the original cell is not
allowed.

The values range from 0 to 120 s.

24 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

Note

If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.

HO preference order interference DL

With this parameter you define the order of preference between intra-cell and
inter-cell handovers when the cause of the handover is downlink interference.
The values are:

Parameter Value Explanation


HDL = INTER The inter-cell handover has greater priority.
INTRA The intra-cell handover has greater priority.

HO preference order interference UL

With this parameter you define the order of preference between intra-cell and
inter-cell handovers when the cause of the handover is uplink interference. The
values are:

Parameter Value Explanation


HUL = INTER The inter-cell handover has greater priority.
INTRA The intra-cell handover has greater priority.

load rate for channel search

CLR = decimal number

With this parameter you define the general load limit for traffic channels in a cell
under the BSC. If the TCH load in a cell is below the limit, the traffic channels for
speech and single slot data calls are allocated using rotation between TRXs in a
cell and between TSLs of a TRX. If the load limit has been reached or exceeded,
the TCH allocation is performed trying to save larger spaces of idle FR resources
for the possible multislot HSCSD calls by preferring small gaps of free resources
and ends of a TRX for single slot calls.

The values range from 0 to 100 %.

If the BTS-specific parameter cell load for channel search has been set (the value
is not 0) in a BTS, this will override the effect of the BSC level parameter in that
BTS.

DN9813184 # Nokia Corporation 25 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

triggering threshold for service area penalty <option>

TTSAP = decimal number

With this parameter you define the triggering level for a Service Area penalty.
The Service Area-specific penalty timer is triggered if the number of incoming
Inter-System handovers occurring from a certain Service Area exceed the penalty
triggering level during a measurement period. While the Service Area penalty
timer is on, the BSC is not allowed to initiate an Inter-System handover attempt
towards WCDMA RAN cells which belong to the Service Area.

The values range from 0 to 255.

penalty trigger measurement period <option>

PTMP = decimal number

With this parameter you define the length of the period during which the latest
Inter-System handover counters are used, if the WCDMA RAN Service Area and
neighbour WCDMA RAN cell penalty triggering are used. According to the
value of this parameter, the BSC calculates the number of successful incoming
Inter-System handovers per each Service Area and the number of unsuccessful
outgoing Inter-System handover attempts per each neighbour WCDMA RAN cell
during the latest measurement period. The values are N, and 2...254 with 2 s
steps. The value N means that WCDMA RAN Service Area and neighbour
WCDMA RAN cell penalty triggering is disabled in the BSC.

service area penalty time <option>

SAPT = decimal number

With this parameter you define the duration of the handover penalty timer which
has been triggered for a Service Area. While the Service Area penalty timer is on,
the BSC is not allowed to initiate an Inter-System handover attempt towards
WCDMA RAN cells that belong to the Service Area.

The values range from 0 to 255 s.

CS TCH allocate RTSL0 <option>

CTR = decimal number

With this parameter you define the priority order between GPRS and RTSL-0
allocation. With the parameter you can define the RTSL-0s to be allocated before
allocating a TCH from GPRS territory.

26 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

The values are:

Parameter Value Explanation


CTR = N The GPRS territory is allocated
first. If no free resources are
available then the RTSL-0 hopping
group is searched.
Y The RTSL-0 hopping group is
allocated first. If no free resources
are available then the GPRS
territory is searched.

CS TCH allocation calculation <option>

CTC = decimal number

With this parameter you define how the GPRS territory is seen when calculating
FR resources.

The values are:

Parameter Value Explanation


CTC = 0 Only circuit switched RTSLs are noticed when calculating resources.
1 Circuit switched and packet switched RTSLs are noticed. Packet
switched RTSLs are seen as occupied resource when calculating
resources.
2 Circuit switched and packet switched RTSLs are noticed. Packet
switched RTSLs are seen as idle resource when calculating resources.

NACC enabled <option>

With this parameter you enable or disable the usage of Network Assisted Cell
Change (NACC) in BSC. An MS in the NC0 or NC2 mode may receive
neighbour cell system information messages in Packet Transfer Mode in the
serving cell before cell reselection is executed. When enabled PACKET SI
STATUS is also supported in BSC. The values are:

Parameter Value Explanation


NACC= Y NACC is enabled in BSC.
N NACC is disabled in BSC.

NCCR control mode <option>

DN9813184 # Nokia Corporation 27 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

NCM = decimal number

With this parameter you define how the cell re–selection is performed. In NC0
mode the MS will make an autonomous cell reselection. In NC2 mode the MS
sends neighbour cell measurements to the network and the network commands
the MS to perform cell reselection. The values are:

Parameter Value Explanation


NCM= 0 NCCR is disabled for all mobile
stations (NC0 broadcast).
1 NCCR is enabled for release 97
mobile stations and onwards (NC0
broadcast).
2 NCCR is enabled for release 99
mobile stations and onwards (NC0
broadcast).
3 NCCR is enabled for release 4
mobile stations and onwards (NC0
broadcast).
4 NCCR is enabled for all mobile
stations (NC2 broadcast).

NCCR idle mode reporting period <option>

NIRP = decimal number

With this parameter you define the measurement reporting period for the MSs in
the RR Packet Idle mode. The values are:

Parameter Value Explanation


NIRP= 0 0.48 s
1 0.96 s
2 1.92 s
3 3.84 s
4 7.68 s
5 15.36 s
6 30.72 s
7 61.44 s

If the value of this parameter is greater than MM Ready timer value in SGSN,
there will be no measurement reports in the RR Packet Idle mode.

28 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

NCCR transfer mode reporting period <option>

NTRP = decimal number

With this parameter you define the measurement reporting period for the MSs in
the RR Packet Transfer mode. The values are:

Parameter Value Explanation


NTRP= 0 0.48 s
1 0.96 s
2 1.92 s
3 3.84 s
4 7.68 s
5 15.36 s
6 30.72 s
7 61.44 s

NCCR return to old cell time <option>

NOCT = decimal number

With this parameter you define the start value for a timer that together with timer
NCCR target cell penalty time counteracts the 'Ping-Pong' effect.

The values range from 5 to 20 s.

NCCR target cell penalty time <option>

NTPT = decimal number

With this parameter you define the time during which the NCCR is not allowed
for a mobile station that has been ordered to select another cell and has returned
from that cell to the original cell.

The values range from 5 to 60 s.

NCCR neighbor cell penalty <option>

NNCP= decimal number

With this parameter you define the penalty time for a neighbor cell after a failed
NCCR to that cell.

DN9813184 # Nokia Corporation 29 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The values range from 1 to 60 s.

WCDMA FDD NCCR enabled <option>

With this parameter you switch on or off the inter–system network–controlled cell
re–selection (IS–NCCR) to WCDMA FDD cells. Due to MS autonomous cell
reselection operation, WCMDA FDD neighbour cells are broadcast on PBCCH,
even if the value of this parameter is set to value N. The values are:

Parameter Value Explanation


WFNE= Y ISNCCR is enabled to WCDMA
FDD cells.
N ISNCCR is disabled to WCDMA
FDD cells.

WCDMA FDD NCCR preferred <option>

With this parameter you define if the coverage reason inter–system network–
controlled cell reselection is triggered as soon as an appropriate WCDMA FDD
cell is available, or if it is triggered only in case there is not an appropriate GSM/
EDGE cell available and an appropriate WCDMA FDD cell is available.

The values are:

Parameter Value Explanation


WFNP= Y ISNCCR is triggered as soon as an
appropriate WCDMA cell is
available.
N ISNCCR is triggered only in case
there is not an appropriate GSM/
EDGE cell available and an
appropriate WCDMA cell is
available.

If the value of this parameter is set to Y, Service UTRAN CCO IE value is


ignored.

Examples 1. Modify the number of target cells to 5.

ZEEM:NPC=5;
2. Modify the GSM macrocell threshold to 37 dBm, the DCS microcell
threshold to 10 dBm, and the MS distance behaviour to 3.
ZEEM:GMAC=37,DMIC=10,DISB=3;

30 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

3. Modify the inter-cell handover caused by uplink interference to have


greater priority.
ZEEM:HUL=INTER;

Additional When the system has created a BSC object, the general base station controller
information parameters have the following default values:

number of preferred cells (NPC) 3


GSM macrocell threshold (GMAC) 35 dBm
GSM microcell threshold (GMIC) 33 dBm
DCS macrocell threshold (DMAC) 26 dBm
DCS microcell threshold (DMIC) 24 dBm
MS distance behaviour (DISB) 255
(no release, only handover attempts)
bts site battery backup forced ho timer (TIM) 30 s
emergency call on FACCH (EEF) N
answer to paging call on FACCH (EPF) N
ordinary calls on FACCH (EOF) N
re establishment on FACCH (ERF) N
TCH in handover (HRI) 1
(call serving type of TCH has to be allocated primarily)
lower limit for FR TCH resources (HRL) 40 %
upper limit for FR TCH resources (HRU) 60 %
bsc call number (BCN) 0000
AMH upper load threshold (AUT) 80 %
AMH lower load threshold (ALT) 20 %
AMH max load of target cell (AML) 70 %
AMR configuration in handovers (ACH) 1
initial AMR channel rate (IAC) 1
slow AMR LA enabled (SAL) N
AMR set grades enabled (ASG) N
free TSL for CS downgrade (CSD) 95 %
free TSL for CS upgrade (CSU) 4 s
TRHO guard time (TGT) 30 s
priority ho interference dl (HDL) INTER
priority ho interference ul (HUL) INTER
load rate for channel search (CLR) 100 %
triggering threshold for service area penalty (TTSAP) 127
penalty trigger measurement period (PTMP) 128 s
service area penalty time (SAPT) 127 s
CS TCH allocate RTSL0 (CTR) N
CS TCH allocation calculation (CTC) 0
NACC enabled (NACC) N
NCCR control mode (NCM) 0
(NCCR is disabled for all mobile stations)
NCCR idle mode reporting period (NIRP) 15.36 s
NCCR transfer mode reporting period (NTRP) 0.48 s
NCCR return to old cell time (NOCT) 10 s
NCCR target cell penalty time (NTPT) 10 s
NCCR neighbor cell penalty (NNCP) 6 s
WCDMA FDD NCCR enabled (WFNE) N
WCDMA FDD NCCR Preferred (WFNP) Y

DN9813184 # Nokia Corporation 31 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

If the SW product (FACCH call setup) is deactivated from the General Parameter
File (PRFILE) by the operator with the command WOF:10-15:0; the warning
text NOT ACTIVE IN PRFILE is printed out. The warning text is printed out
only if the following parameters are used: enable answer to paging call on
FACCH (EPF), enable ordinary calls on FACCH (EOF) and enable call re-
establishment on FACCH (ERF).

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-06-06 11:11:32

BASE STATION CONTROLLER MODIFICATION COMPLETED

NUMBER OF PREFERRED CELLS ........................ (NPC).... 5


GSM MACROCELL THRESHOLD .......................... (GMAC)... 35 dBm
GSM MICROCELL THRESHOLD .......................... (GMIC)... 33 dBm
DCS MACROCELL THRESHOLD .......................... (DMAC)... 26 dBm
DCS MICROCELL THRESHOLD .......................... (DMIC)... 24 dBm
MS DISTANCE BEHAVIOUR ............................ (DISB)... 255
(NO RELEASE, ONLY HANDOVER ATTEMPTS)
BTS SITE BATTERY BACKUP FORCED HO TIMER .......... (TIM).... 30 s
EMERGENCY CALL ON FACCH .......................... (EEF).... Y
ANSWER TO PAGING CALL ON FACCH ................... (EPF).... Y *)
ORDINARY CALLS ON FACCH .......................... (EOF).... Y *)
RE-ESTABLISHMENT ON FACCH ........................ (ERF).... Y *)
TCH IN HANDOVER .................................. (HRI).... 1
(CALL SERVING TYPE OF TCH HAS TO BE ALLOCATED PRIMARILY)
LOWER LIMIT FOR FR TCH RESOURCES ................. (HRL).... 18 %
UPPER LIMIT FOR FR TCH RESOURCES ................. (HRU).... 68 %
BSC CALL NUMBER .................................. (BCN).... 0000
AMH UPPER LOAD THRESHOLD ......................... (AUT).... 80 %
AMH LOWER LOAD THRESHOLD ......................... (ALT).... 20 %
AMH MAX LOAD OF TARGET CELL ...................... (AML).... 70 %
AMR CONFIGURATION IN HANDOVERS ................... (ACH).... 1
INITIAL AMR CHANNEL RATE ......................... (IAC).... 1
SLOW AMR LA ENABLED .............................. (SAL).... N
AMR SET GRADES ENABLED ........................... (ASG).... N
FREE TSL FOR CS DOWNGRADE ........................ (CSD).... 95 %
FREE TSL FOR CS UPGRADE .......................... (CSU).... 4 s
TRHO GUARD TIME .................................. (TGT).... 30 s
PRIORITY HO INTERFERENCE DL ...................... (HDL).... INTER
PRIORITY HO INTERFERENCE UL ...................... (HUL).... INTER
LOAD RATE FOR CHANNEL SEARCH ..................... (CLR).... 100 %
TRIGGERING THRESHOLD FOR SERVICE AREA PENALTY .... (TTSAP).. 127
PENALTY TRIGGER MEASUREMENT PERIOD ............... (PTMP)... 128 s
SERVICE AREA PENALTY TIME ........................ (SAPT)... 127 s
CS TCH ALLOCATE RTSL0 ............................ (CTR)... N
CS TCH ALLOCATION CALCULATION .................... (CTC)... 0
NACC ENABLED ..................................... (NACC)... N
NCCR CONTROL MODE ................................ (NCM).... 0
(NCCR IS DISABLED FOR ALL MOBILE STATIONS)
NCCR IDLE MODE REPORTING PERIOD .................. (NIRP)... 3.84 s
NCCR TRANSFER MODE REPORTING PERIOD .............. (NTRP)... 0.48 s
NCCR RETURN TO OLD CELL TIME ..................... (NOCT)... 10 s

32 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEM MODIFY GENERAL BASE STATION CONTROLLER PARAMETERS

NCCR TARGET CELL PENALTY TIME .................... (NTPT)... 10 s


NCCR NEIGHBOR CELL PENALTY ....................... (NNCP)... 6 s
WCDMA FDD NCCR ENABLED ........................... (WFNE)... N
WCDMA FDD NCCR PREFERRED ......................... (WFNP)... Y

*) NOT ACTIVE IN PRFILE

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error /*** BCSU UPDATE ERROR ***/


messages

The modification was successful but the updating of all BCSUs did not succeed.

After the printout, a list of failed BCSU updates follows, for instance in the
following form:

/*** BCSU-05 NOT UPDATED ***/


/*** BCSU-07 NOT UPDATED ***/

For more information, see Radio Network Administration.

In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.

DN9813184 # Nokia Corporation 33 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

34 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEN MODIFY RADIO NETWORK SUPERVISION PARAMETERS

EEN MODIFY RADIO NETWORK SUPERVISION


PARAMETERS
Function With the EEN command you modify the radio network supervision parameters in
the BSDATA.

Parameters minimum mean holding time for TCHs, maximum mean holding time for TCHs,
maximum mean holding time for SDCCHs, alarm threshold for TCH failure rate,
alarm threshold for SDCCH failure rate, alarm threshold for TCH congestion,
alarm threshold for SDCCH congestion, alarm threshold for number of channel
seizures, alarm threshold for number of channel seizure requests, measurement
period for TCH mean holding time supervision, measurement period for SDCCH
mean holding time supervision, measurement period for supervision of channel
failure rate, measurement period for supervision of congestion in BTS, threshold
for high TCH interference level, alarm threshold for the share of high TCH
interference, measurement period for high TCH interference supervision,
measurement period for supervision of BTS with no transactions, starting
moment for supervision of BTS, ending moment for supervision of BTS, GPRS
territory update guard time <option>;

Syntax

EEN: ( MINHTT = <minimum mean holding time for TCHs> |


MAXHTT = <maximum mean holding time for TCHs> |
MAXHTS = <maximum mean holding time for SDCCHs> |
TCHFR = <alarm threshold for TCH failure rate> |
SCHFR = <alarm threshold for SDCCH failure rate> |
CNGT = <alarm threshold for TCH congestion> |
CNGS = <alarm threshold for SDCCH congestion> |
CS = <alarm threshold for number of channel seizures> |
CSR = <alarm threshold for number of channel seizure requests> |
PRDMHT = <measurement period for TCH mean holding time supervision> |
PRDMHS = <measurement period for SDCCH mean holding time supervision> |
PRDCFR = <measurement period for supervision of channel failure rate> |
PRDCNG = <measurement period for supervision of congestion in BTS> |
HIFLVL = <threshold for high TCH interference level> |
HIFSHR = <alarm threshold for the share of high TCH interference> |
PRDHIF = <measurement period for high TCH interference supervision> |
PRDBNT = <measurement period for supervision of BTS with no transactions> |

DN9813184 # Nokia Corporation 35 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

SMBNT = <starting moment for supervision of BTS> |


EMBNT = <ending moment for supervision of BTS> |
GTUGT = <GPRS territory update guard time> <option> ) ... ;

Parameter minimum mean holding time for TCHs


explanations
MINHTT = decimal number

With this parameter you define the minimum mean holding time for traffic
channels. If the mean holding time is below the minimum mean holding time and
there have been enough calls during the measurement period (the number of
seizures is greater than or equals to the operator-defined threshold value), the
alarm system prints out an alarm.

The values range from 0 to 65535 seconds.

The value has to be lower than the value of the parameter maximum mean
holding time for TCHs.

Note

The value range of minimum mean holding time for TCHs is in seconds and
the value range of maximum mean holding time for TCHs is in minutes.

maximum mean holding time for TCHs

MAXHTT = decimal number

With this parameter you define the maximum mean holding time for traffic
channels. If the mean holding time during a measurement period is greater than or
equal to the maximum mean holding time, the alarm system prints out an alarm.

The values range from 0 to 1440 minutes (=24 hours).

The value has to be higher than the value of the parameter minimum mean
holding time for TCHs.

Note

The value range of minimum mean holding time for TCHs is in seconds and
the value range of maximum mean holding time for TCHs is in minutes.

maximum mean holding time for SDCCHs

36 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEN MODIFY RADIO NETWORK SUPERVISION PARAMETERS

MAXHTS = decimal number

With this parameter you define the maximum mean holding time for signalling
channels. If the mean holding time during a measurement period is greater than or
equal to the maximum mean holding time, the alarm system prints out an alarm.

The values range from 0 to 1440 minutes (=24 hours).

alarm threshold for TCH failure rate

TCHFR = decimal number

With this parameter you define an alarm threshold for traffic channel failure rate.
Whenever a channel is released with a release cause other than a normal one, the
counter of channel failures for the released channel is incremented. If the
percentage of channel failures equals to or exceeds the threshold and there have
been enough calls during the measurement period (the number of seizures is
greater than or equal to the operator-defined threshold value), the alarm system
prints out an alarm.

The values range from 1 to 100 %.

alarm threshold for SDCCH failure rate

SCHFR = decimal number

With this parameter you define an alarm threshold for the SDCCH failure rate. If
the number of SDCCH failures equals to or exceeds the threshold, the alarm
system prints out an alarm.

The values range from 1 to 100 %.

alarm threshold for TCH congestion

CNGT = decimal number

With this parameter you define an alarm threshold for traffic channel congestion.
The parameter supervises the traffic level of traffic channels in a BTS. If the
percentage of TCH seizure requests refused due to congestion equals to or
exceeds the threshold and there have been enough call attempts during the
measurement period (the number of seizure requests is greater than or equal to the
operator-defined threshold value), the alarm system prints out an alarm.

The values range from 1 to 100 %.

alarm threshold for SDCCH congestion

DN9813184 # Nokia Corporation 37 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

CNGS = decimal number

With this parameter you define an alarm threshold for SDCCH congestion. This
parameter supervises the traffic level of signalling channels in a BTS. If the
percentage of SDCCH seizure requests refused due to congestion equals to or
exceeds the threshold and there have been enough call attempts during the
measurement period (the number of seizure requests is greater than or equal to the
operator-defined threshold value), the alarm system prints out an alarm.

The values range from 1 to 100 %.

alarm threshold for number of channel seizures

CS = decimal number

With this parameter you define an alarm threshold for the number of channel
seizures. Only when the number of channel seizures during the measurement
period equals to or exceeds this threshold, the alarm threshold values for
minimum mean holding time for TCHs and alarm threshold for TCH failure rate
are taken into account.

This parameter supervises lost calls and a too short mean holding time in the
traffic channels.

The values range from 1 to 65535.

alarm threshold for number of channel seizure requests

CSR = decimal number

This parameter supervises SDCCH and TCH congestions.

With this parameter you define an alarm threshold for the number of channel
seizure requests. Only when the number of channel seizure requests during the
measurement period equals to or exceeds this threshold, the values for alarm
threshold for TCH congestion and alarm threshold for SDCCH congestion are
taken into account.

The values range from 1 to 65535.

measurement period for TCH mean holding time supervision

PRDMHT = decimal number

With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.

38 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEN MODIFY RADIO NETWORK SUPERVISION PARAMETERS

This parameter supervises too short and too long mean holding times in traffic
channels.

The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.

measurement period for SDCCH mean holding time supervision

PRDMHS = decimal number

With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.

This parameter supervises too long mean holding times in SDCCHs.

The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.

measurement period for supervision of channel failure rate

PRDCFR = decimal number

With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.

This parameter supervises channel failures both in traffic channels and in


SDCCHs.

The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.

measurement period for supervision of congestion in BTS

PRDCNG = decimal number

With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.

This parameter supervises SDCCH and TCH congestion in a BTS.

The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.

threshold for high TCH interference level

HIFLVL = decimal number

DN9813184 # Nokia Corporation 39 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you define the interference level which is regarded as high in
traffic channel interference supervision.

The values range from 0 to 4. Value zero is the lowest interference level or the
best channel quality.

alarm threshold for the share of high TCH interference

HIFSHR = decimal number

With this parameter you define the maximum time in percent that a TCH may be
on high interference levels during a measurement period.

The values range from 1 to 100 %.

measurement period for high TCH interference supervision

PRDHIF = decimal number

With this parameter you define the measurement period for the high TCH
interference supervision.

The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.

measurement period for supervision of BTS with no transactions

PRDBNT = decimal number

With this parameter you define the measurement period for the supervision of
BTSs with no transactions.

The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.

starting moment for supervision of BTS

SMBNT = decimal number

With this parameter you define the time of day when the BTS supervision starts.
The starting moment is given in hours and minutes.

The values range from 00-00 to 23-59.

The starting moment for BTS supervision must be earlier than the ending
moment.

40 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEN MODIFY RADIO NETWORK SUPERVISION PARAMETERS

ending moment for supervision of BTS

EMBNT = decimal number

With this parameter you define the time of day when the BTS supervision ends.
The ending moment is given in hours and minutes.

The values range from 00-00 to 23-59.

The ending moment for BTS supervision must be later than the starting moment.

GPRS territory update guard time <option>

GTUGT = decimal number

With this parameter you set the timer value which must elapse between two
subsequent territory updates.

The values range from 1 to 255 seconds.

Examples 1. Change the parameter value of the alarm threshold for TCH failure rate to
10 %, and the value of the alarm threshold for number of channel seizures
to 20.

ZEEN:TCHFR=10,CS=20;
2. Deactivate the measurement period for TCH mean holding time
supervision.
ZEEN:PRDMHT=0;
3. Set the starting moment for supervision of BTSs to 11:30.
ZEEN:SMBNT=11-30;

Additional When the system has created a BSC object, the radio network supervision
information parameters have the following default values:

minimum mean holding time for TCHs (MINHTT) 10 s


maximum mean holding time for TCHs (MAXHTT) 120 min
maximum mean holding time for SDCCHs (MAXHTS) 30 min
alarm threshold for TCH failure rate (TCHFR) 20 %
alarm threshold for SDCCH failure rate (SCHFR) 80 %
alarm threshold for TCH congestion (CNGT) 20 %
alarm threshold for SDCCH congestion (CNGS) 20 %
alarm threshold for number of channel seizures (CS) 10
alarm threshold for number of ch seizure requests (CSR) 100
meas prd for TCH mean holding time supervision (PRDMHT) 240 min
meas prd for SDCCH mean holding time supervision (PRDMHS) 60 min

DN9813184 # Nokia Corporation 41 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

meas prd for supervision of channel failure rate (PRDCFR) 60 min


meas prd for supervision of congestion in BTS (PRDCNG) 120 min
threshold for high TCH interference level (HIFLVL) 4
alarm threshold for share of high TCH interference (HIFSHR) 50 %
meas prd for high TCH interference supervision (PRDHIF) 120 min
meas prd for supervision of BTS with no transactions (PRDBNT) 120 min
starting moment for supervision of BTS (SMBNT) 08-00
ending moment for supervision of BTS (EMBNT) 18-00
GPRS territory update guard time (GTUGT) 5 s

Execution printouts 1. The execution printout of the command ZEEN:MINHTT=65535; is:

BSC BSC-LAB 2004-01-19 10:11:32

RADIO NETWORK SUPERVISION PARAMETERS MODIFICATION COMPLETED

MINIMUM MEAN HOLDING TIME FOR TCHS ............... (MINHTT). 65535 s


MAXIMUM MEAN HOLDING TIME FOR TCHS ............... (MAXHTT). 1440 min
MAXIMUM MEAN HOLDING TIME FOR SDCCHS ............. (MAXHTS). 30 min
ALARM THRESHOLD FOR TCH FAILURE RATE ............. (TCHFR).. 20 %
ALARM THRESHOLD FOR SDCCH FAILURE RATE ........... (SCHFR).. 80 %
ALARM THRESHOLD FOR TCH CONGESTION ............... (CNGT)... 20 %
ALARM THRESHOLD FOR SDCCH CONGESTION ............. (CNGS)... 20 %
ALARM THRESHOLD FOR NUMBER OF CHANNEL SEIZURES ... (CS)..... 10
ALARM THRESHOLD FOR NUMBER OF CH SEIZURE REQUESTS (CSR).... 100
MEAS PRD FOR TCH MEAN HOLDING TIME SUPERVISION ... (PRDMHT). 240 min
MEAS PRD FOR SDCCH MEAN HOLDING TIME SUPERVISION . (PRDMHS). 60 min
MEAS PRD FOR SUPERVISION OF CHANNEL FAILURE RATE . (PRDCFR). 240 min
MEAS PRD FOR SUPERVISION OF CONGESTION IN BTS .... (PRDCNG). 120 min
THRESHOLD FOR HIGH TCH INTERFERENCE LEVEL ........ (HIFLVL). 4
ALARM THRESHOLD FOR SHARE OF HIGH TCH INTERFERENCE (HIFSHR). 50 %
MEAS PRD FOR HIGH TCH INTERFERENCE SUPERVISION ... (PRDHIF). 0 min
DEACTIVATED
MEAS PRD FOR SUPERVISION OF BTS WITH NO TRANSACT . (PRDBNT). 0 min
DEACTIVATED
STARTING MOMENT FOR SUPERVISION OF BTS ........... (SMBNT).. 08-00
ENDING MOMENT FOR SUPERVISION OF BTS ............. (EMBNT).. 18-00
GPRS TERRITORY UPDATE GUARD TIME ................. (GTUGT).. 5 s

COMMAND EXECUTED

Semantic error
messages

/*** STARTING MOMENT FOR SUPERVISION OF BTS (SMBNT) HAS TO BE EARLIER


THAN ENDING MOMENT FOR SUPERVISION OF BTS (EMBNT) ***/

The ending moment cannot be earlier than or the same as the starting moment.

/*** MINHTT VALUE HAS TO BE LOWER THAN MAXHTT VALUE


NOTE: MINHTT VALUE RANGE IS IN SECONDS AND MAXHTT IN MINUTES ***/

42 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEN MODIFY RADIO NETWORK SUPERVISION PARAMETERS

The value of parameter minimum mean holding time for TCHs has to be lower
than the value of parameter maximum mean holding time for TCHs.

In addition, the general semantic error messages of the MML commands are
output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

DN9813184 # Nokia Corporation 43 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

44 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEQ MODIFY MISCELLANEOUS PARAMETERS

EEQ MODIFY MISCELLANEOUS PARAMETERS


Function With the EEQ command you modify the miscellaneous BSC parameters in the
BSDATA.

Parameters BCSU load threshold, LAPD load threshold, upper limit of MS speed class 1,
upper limit of MS speed class 2, alarm limit for full rate TCH availability, alarm
limit for half rate TCH availability, alarm limit for SDCCH availability, disable
internal HO, disable external DR, RX level balance, RX antenna supervision
period, number of ignored transcoder failures, variable DL step size, maximum
number of DL TBF <option>, maximum number of UL TBF <option>, FEP in
PC HO use <option>, intra segment SDCCH HO guard <option>, pre-emption
usage in handover <option>, WPS priority capacity <option>, WPS preference
capacity <option>, public served count <option>, time limit WPS <option>, time
limit WPS handover <option>, IMSI based handover GSM cells anonymous MS
<option>, IMSI based handover WCDMA cells anonymous MS <option>, soft
blocking C/N FR, soft blocking C/N HR, soft blocking C/N 14.4, soft blocking
C/N AMR FR, soft blocking C/N AMR HR, RX level based TCH access, delay
of HO and PC for emergency calls, internal HO to external allowed, TCH
transaction count, max TCH transaction rate;

Syntax

EEQ: ( BCSUL = <BCSU load threshold> |


LAPDL = <LAPD load threshold> |
MSSCF = <upper limit of MS speed class 1> |
MSSCS = <upper limit of MS speed class 2> |
ALFRT = <alarm limit for full rate TCH availability> |
ALHRT = <alarm limit for half rate TCH availability> |
ALSDC = <alarm limit for SDCCH availability> |
DINHO = <disable internal HO> |
DEXDR = <disable external DR> |
RXBAL = <RX level balance> |
RXANT = <RX antenna supervision period> |
ITCF = <number of ignored transcoder failures> |
VDLS = <variable DL step size> |
MNDL = <maximum number of DL TBF> <option> |
MNUL = <maximum number of UL TBF> <option> |
FPHO = <FEP in PC HO use> <option> |
ISS = <intra segment SDCCH HO guard> <option> |
PRE = <pre-emption usage in handover> <option> |

DN9813184 # Nokia Corporation 45 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

WPIC = <WPS priority capacity> <option> |


WPEC = <WPS preference capacity> <option> |
PSC = <public served count> <option> |
TLW = <time limit WPS> <option> |
TLWH = <time limit WPS handover> <option> |
IBGA = <IMSI based handover GSM cells anonymous MS> <option> |
IBWA = <IMSI based handover WCDMA cells anonymous MS> <option> |
SBCNF = <soft blocking C/N FR> |
SBCNH = <soft blocking C/N HR> <option> |
SBCN = <soft blocking C/N 14.4> <option> |
SBCNAF = <soft blocking C/N AMR FR> <option> |
SBCNAH = <soft blocking C/N AMR HR> <option> |
RXTA = <RX level based TCH access> |
DEC = <delay of HO and PC for emergency calls> |
IHTA = <internal HO to external allowed> |
TTRC = <TCH transaction count> |
MTTR = <max TCH transaction rate> ) ... ;

Parameter BCSU load threshold


explanations
BCSUL = decimal number

With this parameter you define the threshold for the proportion of rejected
measurement results in all measurement results. An overload in the BCSU unit
causes the rejections. If the threshold is exceeded, the BCSU unit is regarded as
overloaded, and the BSC generates a relevant alarm.

The values range from 0 to 10 000 (equals to 0..100 %).

LAPD load threshold

LAPDL = decimal number

With this parameter you define the threshold for the proportion of rejected
measurement results in all measurement results. An overload in the telecom Abis
LAPD link causes the rejections. If the threshold is exceeded, the LAPD link is
regarded as overloaded, and the BSC generates a relevant alarm.

The values range from 0 to 10 000 (equals to 0..100 %).

upper limit of MS speed class 1

MSSCF = decimal number

With this parameter you define the upper limit of the MS speed for the first class
in MS speed measurement.

The values range from 0 to 255. One parameter step equals to the speed of 2 km/
h. The default is 10.

46 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEQ MODIFY MISCELLANEOUS PARAMETERS

upper limit of MS speed class 2

MSSCS = decimal number

With this parameter you define the upper limit of MS speed for the second class
in MS speed measurement.

The values range from 0 to 255. One parameter step equals to the speed of 2 km/
h. The default is 30.

alarm limit for full rate TCH availability

ALFRT = decimal number

With this parameter you define the alarm limit for available full rate traffic
channels. The parameter is used by radio network recovery.

The values range from 0 to 100 %.

alarm limit for half rate TCH availability

ALHRT = decimal number

With this parameter you define the alarm limit for available half rate traffic
channels. The parameter is used by radio network recovery.

The values range from 1 to 100 %.

alarm limit for SDCCH availability

ALSDC = decimal number

With this parameter you define the alarm limit for available SDCCHs. The limit is
the ratio of working SDCCHs to working TCHs in percent. The parameter is used
by radio network recovery.

The values range from 0 to 100 %.

disable internal HO

With this parameter you define whether all handovers are controlled by the MSC
or not. The parameter may receive the following values:

Parameter Value Explanation


DINHO = Y All handovers are controlled by the MSC.

DN9813184 # Nokia Corporation 47 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Parameter Value Explanation


N All handovers are not controlled by the MSC.

disable external DR

With this parameter you disable or enable the external directed retry handovers.
The parameter may receive the following values:

Parameter Value Explanation


DEXDR = Y Disable external directed retry handovers.
N Enable external directed retry handovers.

RX level balance

RXBAL = decimal number

With this parameter you define the balance between the downlink signal level and
the uplink signal level within the BSC coverage area. Value 5 dB means that the
downlink signal is 5 dB stronger than the uplink signal.

The values range from 0 to 20 dB.

RX antenna supervision period

RXANT = decimal number

With this parameter you define the time (in minutes) that the BTS uses for the
internal RX antenna supervision.

The values range from 15 to 65535 minutes. If the supervision period is set to
65535, the internal supervision is not performed in the BTSs.

number of ignored transcoder failures

ITCF = decimal number

With this parameter you define how many successive remote transcoder failures
the BSC may receive before it releases the call.

The values range from 0 to 5.

variable DL step size

48 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEQ MODIFY MISCELLANEOUS PARAMETERS

With this parameter you define whether the variable step size is used in the power
control algorithm when the downlink transmission power is decreased. The
values are:

Parameter Value Explanation


VDLS = Y The variable downlink step size is used.
N The variable downlink step size is not used.

maximum number of DL TBF <option>

MNDL = decimal number

With this parameter you define the maximum number of TBFs that a radio time
slot can have in average in a GPRS territory, in the downlink direction.

The values range from 1 to 9.

maximum number of UL TBF <option>

MNUL = decimal number

With this parameter you define the maximum number of TBFs that a radio time
slot can have in average in a GPRS territory, in the uplink direction.

The values range from 1 to 7.

FEP in PC HO use <option>

With this parameter you indicate whether the Frame Error Probability based
Power Control (PC) and Handover (HO) decision-making is used in the Power
Control and Handover algorithm. The values are:

Parameter Value Explanation


FPHO = Y The Power Control and Handover decision-making is used.
N The Power Control and Handover decision-making is not used.

intra segment SDCCH HO guard <option>

ISS = decimal number

With this parameter you define the guard time for attempting an SDCCH
handover from the BCCH BTS resource layer to another resource layer in a
segment.

DN9813184 # Nokia Corporation 49 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The values range from 0 to 255 seconds. Value 0 means that no time limit is set
for starting an SDCCH handover attempt from the BCCH BTS resource layer,
and the attempt can be made as soon as possible. Values 1..254 define the time
after which an SDCCH handover from the BCCH BTS resource layer is
attempted. Value 255 means no SDCCH handover from the BCCH BTS resource
layer is attempted based on the SDCCH reservation duration.

pre-emption usage in handover <option>

With this parameter you can indicate whether the pre-emption is applied or not in
a case of handover. The values are:

Parameter Value Explanation


PRE = Y The pre-emption is applied in a case of handover.
N The pre-emption is not applied in a case of handover.

WPS priority capacity <option>

WPIC = decimal number

With this parameter you define the portion of cells' total traffic capacity to which
the WPS users are given priority. This parameter is also applied in the Directed
Retry handover target cell evaluation together with the parameter WPS preference
capacity.

The values range from 0 to 100 %.

WPS preference capacity <option>

WPEC = decimal number

With this parameter you define how much of the rest of the cell's resources (100 -
WPS priority capacity) can be allocated to WPS users without any restriction.
This parameter is also applied in the Directed Retry handover target cell
evaluation together with the parameter WPS priority capacity.

The values range from 0 to 100 %.

public served count <option>

PSC = decimal number

50 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEQ MODIFY MISCELLANEOUS PARAMETERS

With this parameter you define how many public users must be served before a
WPS user can be served. This parameter is applied in traffic channel allocation
when the WPS users already have the WPS priority capacity in use and more than
WPS preference capacity of the rest of the cell's resources is in use. Value 0
means that all the idle resources of a cell can be allocated to successive WPS calls
without any restrictions.

The values range from 0 to 10.

time limit WPS <option>

TLW = decimal number

With this parameter you define the maximum queuing time in seconds for WPS
call setup attempts.

The values range from 0 to 30 s. Value 0 means that the queuing is not allowed
for WPS call setups.

time limit WPS handover <option>

TLWH = decimal number

With this parameter you define the maximum queuing time in seconds for WPS
handover attempts.

The values range from 0 to 30 s. Value 0 means that the queuing is not allowed
for WPS handovers.

IMSI based handover GSM cells anonymous MS <option>

IBGA = decimal number or ALL

With this parameter you define in case of intra-GSM handover whether one of the
existing Authorised Networks groups is used for the target cell selection or if all
neighbour GSM cells are permitted. This parameter is used in a serving GSM cell
when a mobile subscriber is anonymous and IMSI based handovers are enabled
in the serving GSM cell. If the status of IMSI based HO to GSM cell is deactive,
then all neighbour GSM cells are permitted for all mobile subscribers.

The values are:

Parameter Value Explanation


IBGA= ALL All neighbour GSM cells are
permitted for all mobile subscribers

DN9813184 # Nokia Corporation 51 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Parameter Value Explanation


1...10 Identifier of Authorised Networks
group

IMSI based handover WCDMA cells anonymous MS <option>

IBWA = decimal number or ALL

With this parameter you define in case of inter-system handover from GSM to
WCDMA whether one of the existing Authorised Networks groups is used for the
target cell selection or if all neighbour WCDMA RAN cells are permitted. This
parameter is used in a serving GSM cell when the mobile subscriber is
anonymous and IMSI based handovers are enabled in the serving GSM cell. If the
status of IMSI based handover to GSM cell is active but the
ISHO_SUPPORT_IN_BSC option is deactive, then all neighbour WCDMA
RAN cells are permitted for all mobile subscribers.

The values are:

Parameter Value Explanation


IBWA= ALL All neighbour WCDMA RAN cells
are permitted for all mobile
subscribers
1...10 Identifier of Authorised Networks
group

soft blocking C/N FR

SBCNF = decimal number

With this parameter you define the minimum acceptable carrier/noise ratio for full
rate and EFR speech connections as well as for circuit switched data connections
of up to 9.6 kbit/s.

The values range from 0 to 63 dB.

soft blocking C/N HR <option>

SBCNH = decimal number

With this parameter you define the minimum acceptable carrier/noise ratio for
half rate speech connections.

The values range from 0 to 63 dB.

52 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEQ MODIFY MISCELLANEOUS PARAMETERS

soft blocking C/N 14.4 <option>

SBCN = decimal number

With this parameter you define the minimum acceptable carrier/noise ratio for
circuit switched data connections of 14.4 kbit/s.

The values range from 0 to 63 dB.

soft blocking C/N AMR FR <option>

SBCNAF = decimal number

With this parameter you define the minimum acceptable carrier/noise ratio for full
rate AMR speech connections.

The values range from 0 to 63 dB.

soft blocking C/N AMR HR <option>

SBCNAH = decimal number

With this parameter you define the minimum acceptable carrier/noise ratio for
half rate AMR speech connections.

The values range from 0 to 63 dB.

RX level based TCH access

RXTA = decimal number

With this parameter you define whether TCH access is based on downlink RX
level.

The values are:

Parameter Value Explanation


RXTA= 0 RX level based TCH access is not
used.
1 RX level based TCH access is
used in call setup.
2 RX level based TCH access is
used in call setup and in
handovers.

DN9813184 # Nokia Corporation 53 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

delay of HO and PC for emergency calls

DEC = decimal number

With this parameter you temporarily disable mobile power control and handovers
in TCH for emergency calls. This enhances the U-TDOA positioning accuracy.
The values range from 0 to 10 seconds.

internal HO to external allowed

With this parameter you define whether it is allowed to change internal handover,
where speech codec or channel rate is changed, to MSC controlled in order to
avoid DL muting.

Note

If the MSC does not support uni-directional handover, DL muting cannot be


avoided by changing handover to external. In that case it is advisable to leave
the parameter to the default value.

Parameter Value Explanation


IHTA= 0 Changing is not allowed.
1 Changing is allowed for AMR
packing/unpacking handovers only.
2 Changing is allowed for other
internal handovers than AMR
packing/unpacking handovers.
3 Changing is allowed for all internal
handovers.

TCH transaction count

TTRC = decimal number

With this parameter you define how many incoming TCH transactions (incoming
MSC controlled TCH handovers or assignments) are taken into account when
determining average TCH transaction rate.

The values range from 0 to 100. Value 0 means that averaging is not used.

max TCH transaction rate

54 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEQ MODIFY MISCELLANEOUS PARAMETERS

MTTR = decimal number

With this parameter you define the maximum incoming (from MSC to BSC)
TCH ransaction rate (transactions per second). In this context TCH transaction
means an MSC controlled TCH handover or TCH assignment. The parameter is
used to determine whether internal handover is allowed to be changed to external.

The values range from 0 to 1000. Value 0 means that changing internal handover
to external is not allowed.

Examples 1. Set BCSU load threshold to 300 and LAPD load threshold to 450.

ZEEQ:BCSUL=300,LAPDL=450;

Additional When the system has created a BSC object, the miscellaneous base station
information controller parameters have the following default values:

BCSU load threshold (BCSUL) 1.50 %


LAPD load threshold (LAPDL) 1.50 %
upper limit of MS speed class 1 (MSSCF) 10 (20 km/h)
upper limit of MS speed class 2 (MSSCS) 30 (60 km/h)
alarm limit for full rate TCH availability (ALFRT) 30 %
alarm limit for half rate TCH availability (ALHRT) 30 %
alarm limit for SDCCH availability (ALSDC) 30 %
disable internal HO (DINHO) N
disable external DR (DEXDR) N
RX level balance (RXBAL) 5 dB
RX antenna supervision period (RXANT) 65535 min
(RX antenna supervision is not performed)
number of ignored transcoder failures (ITCF) 0
variable DL step size (VDLS) N
maximum number of DL TBF (MNDL) 9
maximum number of UL TBF (MNUL) 7
FEP in PC HO use (FPHO) N
intra segment SDCCH HO guard (ISS) 255 s
pre-emption usage in handover (PRE) Y
WPS priority capacity (WPIC) 25 %
WPS preference capacity (WPEC) 97 %
public served count (PSC) 3
time limit WPS (TLW) 28 s
time limit WPS handover (TLWH) 5 s
IMSI based handover GSM cells anonymous MS (IBGA) ALL
IMSI based handover WCDMA cells anonymous MS (IBWA) ALL
soft blocking C/N FR (SBCNF) 12 dB
soft blocking C/N HR (SBCNH) 14 dB
soft blocking C/N 14.4 (SBCN) 14 dB
soft blocking C/N AMR FR (SBCNAF) 7 dB
soft blocking C/N AMR HR (SBCNAH) 12 dB
RX level based TCH access (RXTA) 0
(RX level based TCH access is not used)
delay of HO and PC for emergency calls (DEC) 5 s
internal HO to external allowed (IHTA) 0
TCH transaction count (TTRC) 10

DN9813184 # Nokia Corporation 55 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

max TCH transaction rate (MTTR) 50

Execution printouts 1. The execution printout of the command ZEEQ:RXANT=65535; is:

BSC BSC-LAB 2006-10-15 14:11:32

MISCELLANEOUS PARAMETERS MODIFICATION COMPLETED

BCSU LOAD THRESHOLD .............................. (BCSUL).. 48.00 %


LAPD LOAD THRESHOLD .............................. (LAPDL).. 8.40 %
UPPER LIMIT OF MS SPEED CLASS 1 .................. (MSSCF).. 10 ( 20 km/h)
UPPER LIMIT OF MS SPEED CLASS 2 .................. (MSSCS).. 30 ( 60 km/h)
ALARM LIMIT FOR FULL RATE TCH AVAILABILITY ....... (ALFRT).. 30 %
ALARM LIMIT FOR HALF RATE TCH AVAILABILITY ....... (ALHRT).. 30 %
ALARM LIMIT FOR SDCCH AVAILABILITY ............... (ALSDC).. 30 %
DISABLE INTERNAL HO .............................. (DINHO).. N
DISABLE EXTERNAL DR .............................. (DEXDR).. Y
RX LEVEL BALANCE ................................. (RXBAL).. 5 dB
RX ANTENNA SUPERVISION PERIOD .................... (RXANT).. 65535 min
(RX ANTENNA SUPERVISION IS NOT PERFORMED)
NUMBER OF IGNORED TRANSCODER FAILURES ............ (ITCF)... 0
VARIABLE DL STEP SIZE ............................ (VDLS)... N
MAXIMUM NUMBER OF DL TBF ......................... (MNDL)... 9
MAXIMUM NUMBER OF UL TBF ......................... (MNUL)... 7
FEP IN PC HO USE ................................. (FPHO)... N
INTRA SEGMENT SDCCH HO GUARD ..................... (ISS).... 255 s
PRE-EMPTION USAGE IN HANDOVER .................... (PRE).... Y
WPS PRIORITY CAPACITY ............................ (WPIC)... 25 %
WPS PREFERENCE CAPACITY .......................... (WPEC)... 97 %
PUBLIC SERVED COUNT .............................. (PSC).... 3
TIME LIMIT WPS ................................... (TLW).... 28 s
TIME LIMIT WPS HANDOVER .......................... (TLWH)... 5 s
IMSI BASED HANDOVER GSM CELLS ANONYMOUS MS ....... (IBGA)... ALL
IMSI BASED HANDOVER WCDMA CELLS ANONYMOUS MS ..... (IBWA)... ALL
SOFT BLOCKING C/N FR ............................. (SBCNF).. 12 dB
SOFT BLOCKING C/N HR ............................. (SBCNH).. 14 dB
SOFT BLOCKING C/N 14.4 ........................... (SBCN)... 14 dB
SOFT BLOCKING C/N AMR FR ......................... (SBCNAF). 7 dB
SOFT BLOCKING C/N AMR HR ......................... (SBCNAH). 12 dB
RX LEVEL BASED TCH ACCESS ........................ (RXTA)... 0
(RX LEVEL BASED TCH ACCESS IS NOT USED)
DELAY OF HO AND PC FOR EMERGENCY CALLS ........... (DEC).... 5 s
INTERNAL HO TO EXTERNAL ALLOWED .................. (IHTA)... 0
TCH TRANSACTION COUNT ............................ (TTRC)... 10
MAX TCH TRANSACTION RATE ......................... (MTTR)... 50

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

56 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEV MODIFY QUALITY OF SERVICE PARAMETERS <option>

EEV MODIFY QUALITY OF SERVICE


PARAMETERS <option>
Function With the EEV command you modify the priority based scheduling and enhanced
quality of service (EQoS) parameters in the BSDATA. The command is optional.

Parameters DL high priority SSS, DL normal priority SSS, DL low priority SSS, UL priority
1 SSS, UL priority 2 SSS, UL priority 3 SSS, UL priority 4 SSS: background
traffic class scheduling weight for ARP 1, background traffic class scheduling
weight for ARP 2, background traffic class scheduling weight for ARP 3:::: QC
reallocation action trigger threshold, QC NCCR action trigger threshold, QC QoS
renegotiation action trigger threshold, QC drop action trigger threshold:: PFC
unack BLER limit for SDU error ratio 1, PFC ack BLER limit for transfer delay
1;

Syntax

EEV: ( DHP = <DL high priority SSS> |


DNP = <DL normal priority SSS> |
DLP = <DL low priority SSS> |
UP1 = <UL priority 1 SSS> |
UP2 = <UL priority 2 SSS> |
UP3 = <UL priority 3 SSS> |
UP4 = <UL priority 4 SSS> :
BGSW1 = <background traffic class scheduling weight for ARP 1> |
BGSW2 = <background traffic class scheduling weight for ARP 2> |
BGSW3 = <background traffic class scheduling weight for ARP 3> :::: |

QCATR = <QC reallocation action trigger threshold> |


QCATN = <QC NCCR action trigger threshold > |
QCATQ = <QC QoS renegotiation action trigger threshold > |
QCATD = <QC drop action trigger threshold> :: |

UBL1 = <PFC unack BLER limit for SDU error ratio 1> |
ABL1 = <PFC ack BLER limit for transfer delay 1> |) ... ;

Parameter DL high priority SSS


explanations
DHP = decimal number

DN9813184 # Nokia Corporation 57 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you define the scheduling step size (SSS) for the high priority
level in the downlink direction. The value of this parameter must be lower than or
equal to the value of the parameter dl normal priority sss (DNP). This parameter
is replaced by the Scheduling weight parameters in the PCU supporting EQoS.

The values range from 1 to 12.

DL normal priority SSS

DNP = decimal number

With this parameter you define the scheduling step size (SSS) for the normal
priority level in the downlink direction. The value of this parameter must be
lower than or equal to the value of the parameter dl low priority sss (DLP) and
higher than or equal to the value of the parameter dl high priority sss (DHP). This
parameter is replaced by the Scheduling weight parameters in the PCU supporting
EQoS.

The values range from 1 to 12.

DL low priority SSS

DLP = decimal number

With this parameter you define the scheduling step size (SSS) for the low priority
level in the downlink direction. The value of this parameter must be higher than
or equal to the value of the parameter dl normal priority sss (DNP). This
parameter is replaced by the Scheduling weight parameters in the PCU supporting
EQoS.

The values range from 1 to 12.

UL priority 1 SSS

UP1 = decimal number

With this parameter you define the scheduling step size (SSS) for the priority
level 1 (highest) in the uplink direction. The value of this parameter must be
lower than or equal to the value of the parameter ul priority 2 sss (UP2). This
parameter is replaced by the Scheduling weight parameters in the PCU supporting
EQoS.

The values range from 1 to 12.

UL priority 2 SSS

58 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEV MODIFY QUALITY OF SERVICE PARAMETERS <option>

UP2 = decimal number

With this parameter you define the scheduling step size (SSS) for the priority
level 2 in the uplink direction. The value of this parameter must be lower than or
equal to the value of the parameter ul priority 3 sss (UP3) and higher than or
equal to the value of the parameter ul priority 1 sss (UP1). This parameter is
replaced by the Scheduling weight parameters in the PCU supporting EQoS.

The values range from 1 to 12.

UL priority 3 SSS

UP3 = decimal number

With this parameter you define the scheduling step size (SSS) for the priority
level 3 in the uplink direction. The value of this parameter must be lower than or
equal to the value of the parameter ul priority 4 sss (UP4) and higher than or
equal to the value of the parameter ul priority 2 sss (UP2). This parameter is
replaced by the Scheduling weight parameters in the PCU supporting EQoS.

The values range from 1 to 12.

UL priority 4 SSS

UP4 = decimal number

With this parameter you define the scheduling step size (SSS) for the priority
level 4 (lowest) in the uplink direction. The value of this parameter must be
higher than or equal to the value of the parameter ul priority 3 sss (UP3). This
parameter is replaced by the Scheduling weight parameters in the PCU supporting
EQoS.

The values range from 1 to 12.

background traffic class scheduling weight for ARP 1

BGSW1 = decimal number

With this parameter you define the scheduling weight for the allocation and
retention priority value 1 for background traffic class. The scheduling weight
defines the proportion of residual bandwidth allocation between PFCs.
Scheduling weight parameters replace uplink and downlink scheduling step size
parameters in a PCU where EQoS is supported.

The values range from 1 to 100.

DN9813184 # Nokia Corporation 59 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Note

This parameter is only valid for a PCU that supports EQoS.

background traffic class scheduling weight for ARP 2

BGSW2 = decimal number

With this parameter you define the scheduling weight for the allocation and
retention priority value 2 for background traffic class. The scheduling weight
defines the proportion of residual bandwidth allocation between PFCs.
Scheduling weight parameters replace uplink and downlink scheduling step size
parameters in a PCU where EQoS is supported.

The values range from 1 to 100.

Note

This parameter is only valid for a PCU that supports EQoS.

background traffic class scheduling weight for ARP 3

BGSW3 = decimal number

With this parameter you define the scheduling weight for the allocation and
retention priority value 3 for background traffic class. The scheduling weight
defines the proportion of residual bandwidth allocation between PFCs.
Scheduling weight parameters replace uplink and downlink scheduling step size
parameters in a PCU where EQoS is supported.

The values range from 1 to 100.

Note

This parameter is only valid for a PCU that supports EQoS.

QC reallocation action trigger threshold

QCATR = decimal number

60 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEV MODIFY QUALITY OF SERVICE PARAMETERS <option>

With this parameter you define the Quality Control reallocation action trigger
threshold. Quality Control reallocation action is triggered whenever the quality
degradation has lasted for the number of block periods defined by this parameter.
The reallocation action can always be triggered.

The values range from 0 to 1000 block periods. One block period equals the time
of 20 ms. The value 0 means that the action is disabled.

QC NCCR action trigger threshold

QCATN = decimal number

With this parameter you define the Quality Control NCCR action trigger
threshold. Quality Control NCCR action is triggered whenever the quality
degradation has lasted for the number of block periods defined by this parameter.

The values range from 0 to 1000 block periods. One block period equals the time
of 20 ms. The value 0 means that action is disabled.

QC QoS renegotiation action trigger threshold

QCATQ = decimal number

With this parameter you define the Quality Control QoS renegotiation action
trigger threshold. Quality Control QoS renegotiation action is triggered whenever
the quality degradation has lasted for the number of block periods defined by this
parameter.

The values range from 0 to 1000 block periods. One block period equals the time
of 20 ms. The value 0 means that the action is disabled.

QC drop action trigger threshold

QCATD = decimal number

With this parameter you define the Quality Control drop action trigger threshold.
The Quality Control drop action is triggered whenever the quality degradation
has lasted for the number of block periods defined by this parameter.

The values range from 0 to 1000 block periods. One block period equals the time
of 20 ms. The value 0 means that the action is disabled.

PFC unack BLER limit for SDU error ratio 1

UBL1 = decimal number

DN9813184 # Nokia Corporation 61 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you define the maximum block error rate for the PFCs for
which the SDU Error Ratio is not available. This parameter defines the maximum
block error rate for radio link control in the unacknowledged mode used with link
adaptation and block error rate monitoring algorithm in quality control.

If the value of the PFC Mode parameter of Gb Interface Handling is FALSE, only
the value defined by this parameter is used from PFC unack BLER Limit
parameters. If the value of the PFC Mode parameter is TRUE, the value defined
by this parameter is used from PFC unack BLER Limit parameters when no
aggregate BSS QoS profile is available for the PFC.

PFC unack BLER Limit parameters replace the maximum BLER in


unacknowledgement mode (BLU) parameter in a PCU where EQoS is supported.

The values range from 0 to 250. The unit is parts per thousand.

Note

This parameter is only valid for a PCU that supports EQoS.

PFC ack BLER limit for transfer delay 1

ABL1 = decimal number

With this parameter you define the maximum block error rate for the PFCs for
which the transfer delay is not available. This parameter defines the maximum
block error rate for radio link control in the acknowledged mode used with link
adaptation and block error rate monitoring algorithm in quality control.

If the value of the PFC mode parameter of Gb Interface Handling is FALSE, only
the value defined by this parameter is used from PFC ack BLER limit for transfer
delay parameters. If the value of the PFC mode parameter is TRUE, the value
defined by this parameter is used from PFC ack BLER limit for transfer delay
parameters when no aggregate BSS QoS profile is available for the PFC.

The values range from 0 to 100 %.

Note

This parameter is only valid for a PCU that supports EQoS.

62 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEV MODIFY QUALITY OF SERVICE PARAMETERS <option>

Examples 1. Modify the downlink high priority scheduling step size to 6 for the PCUs
not supporting EQoS.

ZEEV:DHP=6;
2. Modify the downlink normal priority scheduling step size to 4 and the
downlink low priority scheduling step size to 5 for the PCUs not
supporting EQoS.
ZEEV:DNP=4,DLP=5;
3. Modify the uplink priority level 1 SSS to 2, priority level 2 SSS to 4,
priority level 3 SSS to 6 and priority level 4 SSS to 8 for the PCUs not
supporting EQoS.
ZEEV:UP1=2,UP2=4,UP3=6,UP4=8;
4. Modify the background traffic class scheduling weight for ARP 3 to 10 for
the PCUs supporting EQoS.
ZEEV::BGSW3=10:;

Additional When the system has created a BSC object, the quality of service parameters have
information the following default values:

DL high priority SSS (DHP) 3


DL normal priority SSS (DNP) 6
DL low priority SSS (DLP) 12
UL priority 1 SSS (UP1) 3
UL priority 2 SSS (UP2) 6
UL priority 3 SSS (UP3) 9
UL priority 4 SSS (UP4) 12
background traffic class scheduling weight for ARP 1 (BGSW1) 20
background traffic class scheduling weight for ARP 2 (BGSW2) 10
background traffic class scheduling weight for ARP 3 (BGSW3) 5
QC reallocation action trigger threshold (QCATR) 25 (500 ms)
QC NCCR action trigger threshold (QCATN) 100 (2000 ms)
QC renegotiation action trigger threshold QoS (QCATQ) 200 (4000 ms)
QC drop action trigger threshold (QCATD) 400 (8000 ms)
PFC unack BLER limit for SDU error ratio 1 (UBL1) 10
PFC ack BLER limit for transfer delay 1 (ABL1) 70

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-06-09 15:11:32

QUALITY OF SERVICE PARAMETER MODIFICATION COMPLETED

DL HIGH PRIORITY SSS ............................. (DHP).... 6


DL NORMAL PRIORITY SSS ........................... (DNP).... 6
DL LOW PRIORITY SSS .............................. (DLP).... 12
UL PRIORITY 1 SSS ................................ (UP1)... 3
UL PRIORITY 2 SSS ................................ (UP2)... 6
UL PRIORITY 3 SSS ................................ (UP3)... 9

DN9813184 # Nokia Corporation 63 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

UL PRIORITY 4 SSS ................................ (UP4)... 12


BACKGROUND TC SCHEDULING WEIGHT FOR ARP 1 ........ (BGSW1).. 20
BACKGROUND TC SCHEDULING WEIGHT FOR ARP 2 ........ (BGSW2).. 10
BACKGROUND TC SCHEDULING WEIGHT FOR ARP 3 ........ (BGSW3).. 5
QC REALLOCATION ACTION TRIGGER THRESHOLD ......... (QCATR).. 25 BLOCK PERIODS
QC NCCR ACTION TRIGGER THRESHOLD ................. (QCATN).. 100 BLOCK PERIODS
QC QOS RENEGOTIATION ACTION TRIGGER THRESHOLD .... (QCATQ).. 200 BLOCK PERIODS
QC DROP ACTION TRIGGER THRESHOLD ................. (QCATD).. 400 BLOCK PERIODS
PFC UNACK BLER LIMIT FOR SDU ERROR RATIO 1 ....... (UBL1)... 10
PFC ACK BLER LIMIT FOR TRANSFER DELAY 1 .......... (ABL1)... 70 %
COMMAND EXECUTED

Semantic error
messages

/*** SCHEDULING STEP SIZE (SSS) PARAMETERS FOR THE PRIORITY LEVELS
IN THE DOWNLINK DIRECTION HAVE THE FOLLOWING DEPENDENCE:
DHP <= DNP <= DLP ***/

Some of the scheduling step size parameters DHP, DNP and DLP do not follow
the dependence above.

/*** SCHEDULING STEP SIZE (SSS) PARAMETERS FOR THE PRIORITY LEVELS
IN THE UPLINK DIRECTION HAVE THE FOLLOWING DEPENDENCE:
UP1 <= UP2 <= UP3 <= UP4 ***/

Some of the scheduling step size parameters UP1, UP2, UP3 and UP4 do not
follow the dependence above.

In addition, the general semantic error messages of the MML commands are
output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

64 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EET MODIFY PRIORITY LEVEL TO SUBSCRIBER TYPE RELATION <option>

EET MODIFY PRIORITY LEVEL TO SUBSCRIBER


TYPE RELATION <option>
Function With the EET command you define the relation between a subscriber type and the
priority level in the PIE (Priority Information Element) of assignment/handover
requests. The relation is used in defining the traffic types of different requests.
The command is optional.

Parameters priority level, subscriber type;

Syntax
EET: [ PR = <priority level> ... ,
ST = <subscriber type> ] ... ; <option>

Parameter priority level


explanations
PR = decimal number

With this parameter you define the priority level to which a certain subscriber
type is to be attached. The values range from 1 to 14. Multiple priority levels can
be attached to one subscriber type by using the characters & and &&. If you enter
this parameter, you must also enter the subscriber type parameter.

subscriber type

ST = decimal number

With this parameter you define the subscriber type that is to be attached to a
certain priority level or levels.

The values are:

Parameter Value Explanation


ST = 0 GSM subscriber
1 MCN subscriber

DN9813184 # Nokia Corporation 65 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Parameter Value Explanation


2 Priority subscriber

Examples 1. Attach priority levels 2 and 3 to subscriber type 1.

ZEET:PR=2&3,ST=1;
2. Attach priority levels from 1 to 6 to subscriber type 2.
ZEET:PR=1&&6,ST=2;

Execution printouts The execution printout of the command ZEET:PR=1&&4,ST=0:PR=5&&9,


ST=1:PR=10&12,ST=2:PR=11&13&14,ST=0; is:

BSC BSC-LAB 2004-03-27 13:54:32

BASE STATION CONTROLLER MODIFICATION COMPLETED

PRIORITY LEVEL SUBSCRIBER TYPE

1 0 (GSM SUBSCRIBER)
2 0 (GSM SUBSCRIBER)
3 0 (GSM SUBSCRIBER)
4 0 (GSM SUBSCRIBER)
5 1 (MCN SUBSCRIBER)
6 1 (MCN SUBSCRIBER)
7 1 (MCN SUBSCRIBER)
8 1 (MCN SUBSCRIBER)
9 1 (MCN SUBSCRIBER)
10 2 (PRIORITY SUBSCRIBER)
11 0 (GSM SUBSCRIBER)
12 2 (PRIORITY SUBSCRIBER)
13 0 (GSM SUBSCRIBER)
14 0 (GSM SUBSCRIBER)

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

66 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEH MODIFY DFCA PARAMETERS <option>

EEH MODIFY DFCA PARAMETERS <option>


Function With the EEH command you modify DFCA (Dynamic Frequency and Channel
Allocation) parameters in the BSDATA. The command is optional.

Parameters C/I target FR, soft blocking C/I FR, C/I target UL offset, C/I target HR <option>,
soft blocking C/I HR <option>, C/I target 14.4 <option>, soft blocking C/I 14.4
<option>, C/I target AMR FR <option>, soft blocking C/I AMR FR <option>, C/
I target AMR HR <option>, soft blocking C/I AMR HR <option>, SAIC DL C/I
offset <option>, BIM confidence probability, BIM interference threshold, BIM
update period, BIM update scaling factor, BIM update guard time, DFCA channel
allocation method, expected BSC-BSC interface delay;

Syntax EEH: ( CIF = <C/I target FR> |


SBF = <soft blocking C/I FR> |
CIUL = <C/I target UL offset> |
CIH = <C/I target HR> <option> |
SBH = <soft blocking C/I HR> <option> |
CIT = <C/I target 14.4> <option> |
SBCI = <soft blocking C/I 14.4> <option> |
CIAF = <C/I target AMR FR> <option> |
SBAF = <soft blocking C/I AMR FR> <option> |
CIAH = <C/I target AMR HR> <option> |
SBAH = <soft blocking C/I AMR HR> <option> |
SCIO = <SAIC DL C/I offset> <option> |
BCP = <BIM confidence probability> |
BIT = <BIM interference threshold> |
BUP = <BIM update period> |
BUSF = <BIM update scaling factor> |
BUGT = <BIM update guard time> |
DCAM = <DFCA channel allocation method> |
EBID = <expected BSC-BSC interface delay> ) ... ; <option>

Parameter C/I target FR


explanations
CIF = decimal number

With this parameter you define the target C/I value for full rate and EFR speech
connections as well as for circuit switched data connections of up to 9.6 kbit/s.

The values range from 0 to 63 dB.

DN9813184 # Nokia Corporation 67 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The parameter value must be equal to or greater than soft blocking C/I FR.

soft blocking C/I FR

SBF = decimal number

With this parameter you define the minimum acceptable C/I value for full rate and
EFR speech connections as well as for circuit switched data connections of up to
9.6 kbit/s.

The values range from –20 to 43 dB. Value –20 dB means that soft blocking is
disabled.

The parameter value must be equal to or smaller than C/I target FR.

C/I target UL offset

CIUL = decimal number

With this parameter you define an offset that is added to the C/I targets and soft
blocking C/I limits of all connection types when uplink interference checks are
performed.

The value range is from –31 to 31 dB.

C/I target HR <option>

CIH = decimal number

With this parameter you define the target C/I value for half rate speech
connections.

The values range from 0 to 63 dB.

The parameter value must be equal to or greater than the soft blocking C/I HR.

soft blocking C/I HR <option>

SBH = decimal number

With this parameter you define the minimum acceptable C/I value for half rate
speech connections.

The values range from -20 to 43 dB. Value –20 dB means that soft blocking is
disabled.

68 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEH MODIFY DFCA PARAMETERS <option>

The parameter value must be equal to or smaller than the C/I target HR.

C/I target 14.4 <option>

CIT = decimal number

With this parameter you define the target C/I value for circuit switched data
connections of 14.4 kbit/s.

The values range from 0 to 63 dB.

The parameter value must be equal to or greater than the soft blocking C/I 14.4.

soft blocking C/I 14.4 <option>

SBCI = decimal number

With this parameter you define the minimum acceptable C/I value for circuit
switched data connections of 14.4 kbit/s.

The values range from -20 to 43 dB. Value –20 dB means that soft blocking is
disabled.

The parameter value must be equal to or smaller than the C/I target 14.4.

C/I target AMR FR <option>

CIAF = decimal number

With this parameter you define the target C/I value for full rate AMR speech
connections.

The values range from 0 to 63 dB.

The parameter value must be equal to or greater than the soft blocking C/I AMR
FR.

soft blocking C/I AMR FR <option>

SBAF = decimal number

With this parameter you define the minimum acceptable C/I value for full rate
AMR speech connections.

The values range from -20 to 43 dB. Value –20 dB means that soft blocking is
disabled.

DN9813184 # Nokia Corporation 69 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The parameter value must be equal to or smaller than the C/I target AMR FR.

C/I target AMR HR <option>

CIAH = decimal number

With this parameter you define the target C/I value for half rate AMR speech
connections.

The values range from 0 to 63 dB.

The parameter value must be equal to or greater than the soft blocking C/I AMR
HR.

soft blocking C/I AMR HR <option>

SBAH = decimal number

With this parameter you define the minimum acceptable C/I value for half rate
AMR speech connections.

The values range from -20 to 43 dB. Value –20 dB means that soft blocking is
disabled.

The parameter value must be equal to or smaller than the C/I target AMR HR.

BIM confidence probability

BCP = decimal number

With this parameter you define the level of confidence for the estimation used to
build a background interference matrix. It gives the share of users experiencing a
C/I equal to or greater than the C/I contained in the matrix.

The values range from 50 to 95 %.

BIM interference threshold

BIT = decimal number

With this parameter you define an upper limit for the C/I values which are
considered relevant for the interference estimations. C/I values above the
interference threshold can be discarded during the BIM update procedure.

The values range from 0 to 35 dB.

70 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEH MODIFY DFCA PARAMETERS <option>

BIM update period

BUP = decimal number

With this parameter you define the period between successive background
interference matrix updates. Therefore, it is the length of the data collecting
period for a single BIM update.

The values are:

from 10 to 60 min with 10 min steps

from 120 to 360 min with 60 min steps

720 and 1440 min

Value 0 means that no BIM updates are performed.

BIM update scaling factor

BUSF = decimal number

With this parameter you define the weighting factor for the C/I value defined
during the latest BIM update period when this is combined with the long term C/I
statistics.

The values range from 0.0 to 1.0 with 0.1 step

BIM update guard time

BUGT = decimal number

With this parameter you define the number of BIM update periods that the DFCA
algorithm allows without removing a neighbour cell from the BIM table of a
DFCA cell. The neighbour cell is not removed even it is not included in the BIM
updates made during that time.

The values range from 0 to 63 BIM update periods. Value 63 means that a
neighbour is not removed from the BIM even if the neighbour is not included in
any new BIM update.

DFCA channel allocation method

DCAM = decimal number

DN9813184 # Nokia Corporation 71 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you define if DCFA assignments are made primarily to
channels having the connection specific C/I target level or to channels having the
highest positive C/I difference from the target level. The values are:

Parameter Value Explanation


DCAM = 0 The primary target of a DFCA assignment is an MA, MAIO and tsl
combination with the highest C/I difference from the target level.
1 The primary target of a DFCA assignment is an MA, MAIO and tsl
combination on the connection specific target C/I level.

expected BSC-BSC interface delay

EBID = decimal number

With this parameter you define the expected BSC-BSC interface delay. This
parameter is used in the Radio Resource Manager for the channel assignment
control to prevent simultaneous channel allocations in neigbouring BSCs.

The values range from 0 to 2000 ms with 10 ms steps.

SAIC DL C/I offset

SCIO = decimal number

With this parameter you define how much lower downlink C/I values can be used
for SAIC calls than for non-SAIC calls in DFCA TCH allocation.

The values range from 0 to 63 dB with 1 dB step.

Examples 1. Set the C/I target FR to 9 and SAIC DL C/I offset to 3.

ZEEH:CIF=9,SCIO=3;

Additional When the system has created a BSC object, base station controller parameters
information have the following default values:

C/I target FR (CIF) 14 dB


soft blocking C/I FR (SBF) -20 dB
C/I target UL offset (CIUL) 0 dB
C/I target HR (CIH) 14 dB
soft blocking C/I HR (SBH) -20 dB
C/I target 14.4 (CIT) 16 dB
soft blocking C/I 14.4 (SBCI) -20 dB
C/I target AMR FR (CIAF) 8 dB
soft blocking C/I AMR FR (SBAF) -20 dB
C/I target AMR HR (CIAH) 12 dB
soft blocking C/I AMR HR (SBAH) -20 dB

72 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEH MODIFY DFCA PARAMETERS <option>

SAIC DL C/I offset (SCIO) 2 dB


BIM confidence probability (BCP) 90 %
BIM interference threshold (BIT) 30 dB
BIM update period (BUP) 60 min
BIM update scaling factor (BUSF) 0.5
BIM update guard time (BUGT) 10
DFCA channel allocation method (DCAM) 0
expected BSC-BSC interface delay (EBID) 50 ms

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2006-10-06 11:11:32

DFCA PARAMETERS MODIFICATION COMPLETED

C/I TARGET FR .................................... (CIF).... 9 dB


SOFT BLOCKING C/I FR ............................. (SBF).... 0 dB
C/I TARGET UL OFFSET ............................. (CIUL)... 0 dB
C/I TARGET HR .................................... (CIH).... 14 dB
SOFT BLOCKING C/I HR ............................. (SBH).... 0 dB
C/I TARGET 14.4 .................................. (CIT).... 16 dB
SOFT BLOCKING C/I 14.4 ........................... (SBCI)... 0 dB
C/I TARGET AMR FR ................................ (CIAF)... 8 dB
SOFT BLOCKING C/I AMR FR ......................... (SBAF)... 0 dB
C/I TARGET AMR HR ................................ (CIAH)... 12 dB
SOFT BLOCKING C/I AMR HR ......................... (SBAH)... 0 dB
SAIC DL C/I OFFSET ............................... (SCIO)... 3 dB
BIM CONFIDENCE PROBABILITY ....................... (BCP).... 90 %
BIM INTERFERENCE THRESHOLD ....................... (BIT).... 30 dB
BIM UPDATE PERIOD ................................ (BUP).... 60 min
BIM UPDATE SCALING FACTOR ........................ (BUSF)... 0.5
BIM UPDATE GUARD TIME ............................ (BUGT)... 10
DFCA CHANNEL ALLOCATION METHOD ................... (DCAM)... 0
EXPECTED BSC-BSC INTERFACE DELAY ................. (EBID)... 50 ms

COMMAND EXECUTED

Semantic error /*** CIF MUST BE EQUAL TO OR GREATER THAN SBF ***/
messages

The value of the C/I target FR parameter must be greater than or equal to the
value of the soft blocking C/I FR parameter.

/*** CIH MUST BE EQUAL TO OR GREATER THAN SBH ***/

The value of the C/I target HR parameter must be greater than or equal to the
value of the soft blocking C/I HR parameter.

/*** CIT MUST BE EQUAL TO OR GREATER THAN SBCI ***/

The value of the C/I target 14.4 parameter must be greater than or equal to the
value of the soft blocking C/I 14.4 parameter.

DN9813184 # Nokia Corporation 73 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

/*** CIAF MUST BE EQUAL TO OR GREATER THAN SBAF ***/

The value of the C/I target AMR FR parameter must be greater than or equal to
the value of the soft blocking C/I AMR FR parameter.

/*** CIAH MUST BE EQUAL TO OR GREATER THAN SBAH ***/

The value of the C/I target AMR HR parameter must be greater than or equal to
the value of the soft blocking C/I AMR HR parameter.

In addition, the general semantic error printouts of MML commands are output.
For more information, see General Notice Messages of MML Session.

Execution error For more information, see Radio Network Administration.


messages

In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.

74 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEJ MODIFY GPRS PARAMETERS <option>

EEJ MODIFY GPRS PARAMETERS <option>


Function With the EEJ command you modify the GPRS parameters in the BSDATA. The
command is optional.

Parameters mean BEP limit for MS multislot power profile 0 with 2 UL TSL <option>, mean
BEP limit for MS multislot power profile 0 with 3 UL TSL <option>, mean BEP
limit for MS multislot power profile 0 with 4 UL TSL <option>, mean BEP limit
for MS multislot power profile 1 with 2 UL TSL <option>, mean BEP limit for
MS multislot power profile 1 with 3 UL TSL <option>, mean BEP limit for MS
multislot power profile 1 with 4 UL TSL <option>, mean BEP limit for MS
multislot power profile 2 with 3 UL TSL <option>, mean BEP limit for MS
multislot power profile 2 with 4 UL TSL <option>, RX quality limit for MS
multislot power profile 0 with 2 UL TSL <option>, RX quality limit for MS
multislot power profile 0 with 3 UL TSL <option>, RX quality limit for MS
multislot power profile 0 with 4 UL TSL <option>, RX quality limit for MS
multislot power profile 1 with 2 UL TSL <option>, RX quality limit for MS
multislot power profile 1 with 3 UL TSL <option>, RX quality limit for MS
multislot power profile 1 with 4 UL TSL <option>, RX quality limit for MS
multislot power profile 2 with 3 UL TSL <option>, RX quality limit for MS
multislot power profile 2 with 4 UL TSL <option>, EGPRS inactivity criteria
<option>, events per hour for EGPRS inactivity alarm <option>, supervision
period length for EGPRS inactivity alarm <option>: DTM PFC packet flow timer
<option>, DTM fragmentation penalty <option>, ISHO preferred for non-DTM
MS <option>;

Syntax

EEJ: ( BL02 = <mean BEP limit for MS multislot power profile 0 with 2 UL TSL> <option>
|
BL03 = <mean BEP limit for MS multislot power profile 0 with 3 UL TSL> <option>
|
BL04 = <mean BEP limit for MS multislot power profile 0 with 4 UL TSL> <option>
|
BL12 = <mean BEP limit for MS multislot power profile 1 with 2 UL TSL> <option>
|
BL13 = <mean BEP limit for MS multislot power profile 1 with 3 UL TSL> <option>
|
BL14 = <mean BEP limit for MS multislot power profile 1 with 4 UL TSL> <option>
|

DN9813184 # Nokia Corporation 75 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

BL23 = <mean BEP limit for MS multislot power profile 2 with 3 UL TSL> <option>
|
BL24 = <mean BEP limit for MS multislot power profile 2 with 4 UL TSL> <option>
|
RL02 = <RX quality limit for MS multislot power profile 0 with 2 UL TSL>
<option> |
RL03 = <RX quality limit for MS multislot power profile 0 with 3 UL TSL>
<option> |
RL04 = <RX quality limit for MS multislot power profile 0 with 4 UL TSL>
<option> |
RL12 = <RX quality limit for MS multislot power profile 1 with 2 UL TSL>
<option> |
RL13 = <RX quality limit for MS multislot power profile 1 with 3 UL TSL>
<option> |
RL14 = <RX quality limit for MS multislot power profile 1 with 4 UL TSL>
<option> |
RL23 = <RX quality limit for MS multislot power profile 2 with 3 UL TSL>
<option> |
RL24 = <RX quality limit for MS multislot power profile 2 with 4 UL TSL>
<option> |
EGIC = <EGPRS inactivity criteria> <option> |
IEPH = <Events per hour for EGPRS inactivity alarm> <option> |
SPL = <Supervision period length for EGPRS inanctivity alarm> <option> ) :

( DPPFT = <DTM PFC packet flow timer> <option> |


DFP = <DTM fragmentation penalty> <option> |
IPND = <ISHO preferred for non-DTM MS> <option> )... ;

Parameter Mean BEP limit for MS multislot power profile 0 with 2 UL TSL
explanations
BL02 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

Mean BEP limit for MS multislot power profile 0 with 3 UL TSL

BL03 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

76 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEJ MODIFY GPRS PARAMETERS <option>

Mean BEP limit for MS multislot power profile 0 with 4 UL TSL

BL04 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

Mean BEP limit for MS multislot power profile 1 with 2 UL TSL

BL12 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

Mean BEP limit for MS multislot power profile 1 with 3 UL TSL

BL13 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

Mean BEP limit for MS multislot power profile 1 with 4 UL TSL

BL14 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

DN9813184 # Nokia Corporation 77 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The values range from 0 to 8 dB with 1 dB step.

Mean BEP limit for MS multislot power profile 2 with 3 UL TSL

BL23 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

Mean BEP limit for MS multislot power profile 2 with 4 UL TSL

BL24 = decimal number

With this parameter you indicate the mean BEP limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured mean BEP
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the mean BEP limit is set low, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 0 with 2 UL TSL

RL02 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 0 with 3 UL TSL

RL03 = decimal number

78 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEJ MODIFY GPRS PARAMETERS <option>

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 0 with 4 UL TSL

RL04 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 1 with 2 UL TSL

RL12 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 1 with 3 UL TSL

RL13 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 1 with 4 UL TSL

DN9813184 # Nokia Corporation 79 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

RL14 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 2 with 3 UL TSL

RL23 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

RX quality limit for MS multislot power profile 2 with 4 UL TSL

RL24 = decimal number

With this parameter you indicate the RX quality limit for different MS multislot
power profiles when allocating more than 1 UL TSL. The measured RX quality
value is compared to the value of this parameter when defining how many UL
TSLs can be allocated. If the RX quality limit is set high, power reduction is not
taken into account so strictly in channel allocation.

The values range from 0 to 8 dB with 1 dB step.

EGPRS inactivity criteria

EGIC = decimal number

With this parameter you define the criteria used to the (E)GPRS inactivity.

The values range from 0 to 3 with 1 step.

events per hour for EGPRS inactivity alarm

IEPH = decimal number

80 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEJ MODIFY GPRS PARAMETERS <option>

With this parameter you define the number of TBF allocation attempts required
per hour for (E)GPRS inactivity alarm.

The values range from 0 to 255 with 1 step.

supervision period length for EGPRS inactivity alarm

SPL = decimal number

With this parameter you define the length of the supervision period for (E)GPRS
inactivity alarm in minutes.

The values range from 15 to 1440 min with 1 min step.

DTM PFC Packet Flow Timer

DPPFT = decimal number

With this parameter you define the maximum time accepted for a Packet Flow
Timer (PFT) during a DTM allocation.

The values range from 1 to 600 s with 1 s step.

Note

A DTM allocation is released when the last PFC context of a DTM MS is


deleted by the PCU. Therefore, the PFC lifetime determines how long the CS
connection of a DTM MS is kept in the PS territory after the data traffic has
ceased for the MS.

DTM fragmentation penalty

DFP = decimal number

With this parameter you define the value of the fragmentation penalty that is used
in the DTM channel allocation algorithm if there is a need to search for a
configuration giving the highest capacity for the DTM MS.

The values range from 0 to 1 with 0.1 step.

ISHO preferred for non-DTM MS

DN9813184 # Nokia Corporation 81 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you determine whether an inter-system handover is to be


triggered for an MS that is DTM incapable but WCDMA capable as soon as an
appropriate WCDMA target cell is available.

Parameter Value Explanation


IPND = Y ISHO is triggered
N ISHO is not triggered

Examples 1. Set the mean BEP limit for MS multislot power profile 1 with 2 UL TSL to
4, RX quality limit for MS multislot power profile 0 with 3 UL TSL to 5
and ISHO preferred for non-DTM MS to N.

ZEEJ:BL12=4,RL03=5:IPND=N;

Execution printouts The execution printout of command example 1 is:

BSC DX220-LAB 2006-10-06 12:14:52

GPRS PARAMETERS MODIFICATION COMPLETED

MEAN BEP LIMIT MS MULTISLOT PWR PROF 0 WITH 2 UL TSL .. (BL02).. 6 dB


MEAN BEP LIMIT MS MULTISLOT PWR PROF 0 WITH 3 UL TSL .. (BL03).. 6 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 0 WITH 4 UL TSL .. (BL04).. 7 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 1 WITH 2 UL TSL .. (BL12).. 4 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 1 WITH 3 UL TSL .. (BL13).. 5 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 1 WITH 4 UL TSL .. (BL14).. 6 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 2 WITH 3 UL TSL .. (BL23).. 6 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 2 WITH 4 UL TSL .. (BL24).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 0 WITH 2 UL TSL ... (RL02).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 0 WITH 3 UL TSL ... (RL03).. 5 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 0 WITH 4 UL TSL ... (RL04).. 6 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 1 WITH 2 UL TSL ... (RL12).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 1 WITH 3 UL TSL ... (RL13).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 1 WITH 4 UL TSL ... (RL14).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 2 WITH 3 UL TSL ... (RL23).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 2 WITH 4 UL TSL ... (RL24).. 6 dB
EGPRS INACTIVITY CRITERIA ............................. (EGIC).. 0
EVENTS PER HOUR FOR EGPRS INACTIVITY ALARM ............ (IEPH).. 10
SUPERVISION PERIOD LENGTH FOR EGPRS INACTIVITY ALARM ... (SPL).. 60
DTM PFC PACKET FLOW TIMER ............................ (DPPFT).. 4 s
DTM FRAGMENTATION PENALTY .............................. (DFP).. 0.3
ISHO PREFERRED FOR NON-DTM MS.......................... (IPND).. N

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

82 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EER PREPARE DATABASE FOR DOWNLOADING OF BACKGROUND DATA

EER PREPARE DATABASE FOR


DOWNLOADING OF BACKGROUND DATA
Function With the EER command you prepare the database for background downloading.

Parameters The command has no parameters.

Syntax EER;

Examples 1. Prepare database for the downloading of background data.

ZEER;

Additional Before the command is executed, the program asks for confirmation:
information

CONFIRM COMMAND EXECUTION: Y/N ?

The ways that the state of background data may change in the preparation for
downloading are:

1. You modify radio network background parameters: the background data


state changes to NEW.
2. You clear the background in the BSDATA.
3. You clear the background in the BSDATA.

For more information, see Radio Network Configuration Management.

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-02-28 11:11:32

RADIO NETWORK BACKGROUND DATA PREPARATION STARTED

COMMAND EXECUTED

DN9813184 # Nokia Corporation 83 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

84 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEG CONTROL ACTIVATION OF BACKGROUND DATA

EEG CONTROL ACTIVATION OF BACKGROUND


DATA
Function With the EEG command you control the background data activation procedures
by:

. activating a new frequency plan


.
performing a cross-check between background and active data
. interrupting an ongoing activation
.
cancelling an interrupted activation.

Parameters operation;

Syntax EEG: [ <operation> | <ACT> def ] ;

Parameter operation
explanations
With this parameter you define the operation as:
ACT The activation operation starts the activation of the
frequency plan, that is, a switchover between the
background data and active data.
CHK The cross-check operation cross-checks the background
data. The checking is carried out to the whole database to
ensure that the database content after the background data
activation is correct.
CNL The cancelling operation cancels the interrupted
activation.
INT The interruption operation interrupts the ongoing
activation of the frequency plan.

Examples 1. Start the activation of the background data.

ZEEG;

DN9813184 # Nokia Corporation 85 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

2. Run a cross-check between the background and the active data.


ZEEG:CHK;
3. Interrupt an ongoing activation.
ZEEG:INT;
4. Cancel an interrupted activation.
ZEEG:CNL;

Additional The different alternatives how the state of the background data may change while
information controlling the activation of the background data are:

1. The user enters the activation command. The system automatically


executes a semantic cross-check.
2. The activation is completed.
3. The user modifies the backup data.
4. The user restores the original frequency plan. The system automatically
executes a semantic cross-check.
5. The user interrupts an ongoing activation or it is spontaneously interrupted
by a BSC reset. The user can continue the activation by re-entering the
activation command. The system does not execute semantic cross-check.
6. The user cancels the interrupted activation.

Changing the background data is denied during the activation and also if the
activation is interrupted but not cancelled.

For more information, see Radio Network Configuration Management.

When the command EEG; is executed and if the Radio Network (RNW) Plan
Database state is one of the specific states (DOWNLOADING,
DOWNLOADED, VALIDATING or VALIDATED) a confirmation to proceed is
asked from the user:

RNW PLAN CONFIGURATION IS DOWNLOADED AND THIS COMMAND CANCELS THE PLAN, ARE YOU SURE
YOU WANT TO DO THIS COMMAND?

CONFIRM COMMAND EXECUTION: Y/N ?

Answering Y executes the command normally, and answering N aborts the


command. If the RNW Plan Database is in some other state, confirmation is not
asked and command is executed normally.

86 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEG CONTROL ACTIVATION OF BACKGROUND DATA

For more information on File Based Plan Provisioning, and RNW Plan Database
and its states, see File Based Plan Provisioning in GSM/EDGE BSS
documentation.

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-03-27 13:54:32

RADIO NETWORK BACKGROUND DATA ACTIVATION STARTED

BACKGROUND DATA STATE .............................. ACTIVATING

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

If an error occurs in the background data cross-checks, also the conflict point is
output. The printout depends on the error. Execution error message of the
command ZEEG:ACT; can be:

BSC BSC-LAB 2004-03-27 13:54:32

RADIO NETWORK BACKGROUND DATA ACTIVATION STARTED

/*** DX ERROR: 11084 ***/


/*** BSIC VALUE OF ADJACENT CELL DIFFERS FROM CORRESPONDING OWN BTS VALUE ***/

BTS-0001 CENTRUM1 HAS ADJACENT CELL :


BTS-0002 CENTRUM2 MCC = 123 MNC = 234 LAC = 00001 CI = 00002

COMMAND EXECUTION ABORTED

For more information, see Radio Network Administration.

DN9813184 # Nokia Corporation 87 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

88 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEE CONTROL ACTIVATION OF RNW PLAN

EEE CONTROL ACTIVATION OF RNW PLAN


Function With the EEE command you operate the RNW plan database. Parameter
operation type defines the operation of the command.

Parameters configuration identification, operation type: activation method, connection type:


ok cases to feedback, progress info, compress threshold, remote directory path,
short timer interval, long timer interval, short timer count, long timer count, ip
address, port number, ftam application entity name, user name, user id, password;

Syntax EEE: ( ID = <configuration identification> |


OPE = <operation type> ) :

( METHOD = <activation method> |


CONNTYPE = <connection type> ) :

( OKFEB = <ok cases to feedback> |


PROGINFO = <progress info> |
COMPTRH = <compress threshold> |
REMOTEDIR = <remote directory path> |
STIMER = <short timer interval> |
LTIMER = <long timer interval> |
STIMERCOUNT = <short timer count> |
LTIMERCOUNT = <long timer count> |
IP = <ip address> |
PORT = <port number> |
FTAMAEN = <ftam application entity name> |
USERNAME = <user name> |
USERID = <user id> |
PASSWORD = <password> ) ... ;

Parameter configuration identification


explanations
ID = decimal number

With this parameter you define the right plan for operation. The ID is saved into
BSC database and it is used to check if the ID in the command coincides with the
ID in the BSC database. The parameter is obligatory.

The values range from 1 to 2147483647.

DN9813184 # Nokia Corporation 89 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

operation type

With this parameter you define whether the commands activate RNW plan,
interrupt RNW plan activation, or activate the fallback. The parameter is
obligatory.

Parameter Value Explanation


OPE = ACT Activate RNW plan with fallback.
ACTWF Activate RNW plan without fallback.
INT Interrupt RNW plan.
ACTFALL Activate fallback.

Activation method

METHOD = decimal number

With this parameter you define how many objects are activated simultaneously.
This is a percentage value of BCF amount in the plan. The value that indicates
how many simultaneous objects are handled is received from NetAct. If the value
is 0, the fastest possible is used (150 objects) without handovers. If the value is
other than 0, the handovers are used. It is possible to give this parameter if the
value of parameter operation type is ACT or ACTWF.

The values range from 0 to 20 % with 1 % step.

connection type

With this parameter you define which type of connection is used between BSC
and NetAct for file transfer. The parameter is obligatory.

Parameter Value Explanation


CONNTYPE = FTP FTP connection between BSC and
NetAct for file transfer.
FTAM FTAM connection between BSC
and NetAct for file transfer.
NOCONN No Connection between BSC and
NetAct for file transfer.

OK cases to feedback

90 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEE CONTROL ACTIVATION OF RNW PLAN

With this parameter you define if a feedback message of the objects with
successful handling in download, validation or activation phase is written to
feedback file.

Parameter Value Explanation


OKFEB = Y Successful cases are written to the
feedback file.
N Error cases are written to the
feedback file.

progress info

PROGINFO = decimal number

With this parameter you define how many feedback messages are included in one
feedback file. The amount is in steps of 100. The default value is 1 (= 100
feedback messages to one field).

The values range from 0 to 65534 with 1 step.

compress threshold

COMPTRH = decimal number

With this parameter you define the feedback file size in kilobytes above which
compression is used when the file is sent.

The values range from 0 to 4294967295 with 1 step.

remote directory

REMOTEDIR = text string

With this parameter you define the directory path in NetAct for plan and feedback
files. The remote directory's last character must be ' / '.

The values range from 1 to 27 characters.

short timer interval

STIMER = decimal number

With this parameter you define short timer interval for file transfer connection
check in ftp/ftam connection.

DN9813184 # Nokia Corporation 91 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

The values range from 1 to 5 s with 1 s step.

long timer interval

LTIMER = decimal number

With this parameter you define long timer interval for file transfer connection
check in ftp/ftam connection.

The values range from 2 to 10 min with 1 min step.

short timer count

STIMERCOUNT = decimal number

With this parameter you define short timer count for file transfer connection
check in ftp/ftam connection.

The values range from 1 to 3 with 1 step.

long timer count

LTIMERCOUNT = decimal number

With this parameter you define long timer count for file transfer connection check
in ftp/ftam connection.

The values range from 1 to 20 with 1 step.

IP address

IP = decimal number

With this parameter you give the IP address of the FTP server where to read plan
file and where to sent the feedback files. IP address can be given if the connection
type is FTP.

The values are given A.B.C.D where A, B, C and D values range from 0 to 255.

This parameter is obligatory.

port number

PORT = decimal number

92 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEE CONTROL ACTIVATION OF RNW PLAN

With this parameter you give the port number of the FTP server where to read
plan file and where to sent the feedback files. Port number is possible to give if
connection type is FTP.

The values range from 0 to 65535 with 1 step.

ftam application entity name

FTAMAEN = text string

With this parameter you define the FTAM application entity name. Ftam
application entity name is possible to give if connection type is FTAM.

The values range from 1 to 16 characters.

This parameter is obligatory.

user name

USERNAME = text string

With this parameter you give the username of the FTP connection.

The values range from 1 to 15 characters.

user ID

USERID = text string

With this parameter you give the user ID of the FTAM connection.

The values range from 1 to 6 characters.

password

PASSWORD = text string

With this parameter you give password of the FTP or FTAM server where to read
plan file and where to sent the feedback files.

The values range from 1 to 15 characters.

DN9813184 # Nokia Corporation 93 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Examples 1. Set the configuration identification to 1, operation type to ACT, activation


method to 20, connection type to FTP, ok cases to feedback to N, remote
directory to MAIN/, short timer interval to 3, long timer interval to 10,
short timer count to 2, long timer count to 10, ip address to 193.200.12.1,
port number to 6763, user name to ROOT and password to 12345.

EEE:ID=1,OPE=ACT:METHOD=20,CONNTYPE=FTP:OKFEB=N,
REMOTEDIR=MAIN/,STIMER=3,LTIMER=10,STIMERCOUNT=2,
LTIMERCOUNT=10,IP=193.200.12.1,PORT=6763,
USERNAME=ROOT,PASSWORD=12345;
2. Set the configuration identification to 1, operation type to ACT, activation
method to 20 and connection type to NOCONN.
EEE:ID=1,OPE=ACT:METHOD=20,CONNTYPE=NOCONN;
3. Set the configuration identification to 1, operation type to ACTFALL and
connection type to NOCONN.
EEE:ID=1,OPE=ACTFALL:CONNTYPE=NOCONN;
4. Set the configuration identification to 1 and operation type to INT.
EEE:ID=1,OPE=INT;

Additional When the command is executed and if the operation type is ACTFALL, a
information confirmation to proceed is asked from the user:

SYSTEM RESTART IS EXECUTED AFTER FALLBACK FILES COPY. FILE COPY MAY
TAKE SOME MINUTES.

CONFIRM COMMAND EXECUTION: Y/N ?

Answering Y executes the command normally, and answering N aborts the


command.

Execution printouts The abbreviations used in the execution printout:

CLEAR RNW plan does not exist


DOWNLOAD_INIT
Initialisation of RNW Plan database is ongoing.
DOWNLOADING Download is ongoing
DOWNLOADED RNW plan is downloaded; database is initialized and the
changes in the plan are made into the database
VALIDATING Validation of the plan database is ongoing
VALIDATING_NO_INT
Validation of the plan database is ongoing, BSC Radio
Network configuration changes are denied

94 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEE CONTROL ACTIVATION OF RNW PLAN

VALIDATED Validation is done; RNW plan database is ready to be


activated
ACT_INIT Fallback copy is dumped to disk
ACTIVATING Activation of the plan database is ongoing
ACTIVATED RNW plan is activated
FALLBACK_ACT Fallback activation is ongoing
FALLBACK_INIT Fallback copy is loaded to memory
INTERRUPTED Activation is interrupted
INTERRUPTED_BY_SYSTEM
Activation is interrupted by the system; only fallback
activation is allowed in this state

The execution printout of command example 1 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE ACTIVATION STARTED

RNW PLAN DATABASE STATE ..................... ACTIVATING


COMMAND EXECUTED

The execution printout of command example 2 is:

BSC DX220-LAB 2006-10-08 15:17:10

RADIO NETWORK PLAN DATABASE ACTIVATION STARTED

RNW PLAN DATABASE STATE ..................... ACTIVATING


COMMAND EXECUTED

The execution printout of command example 3 is:

BSC DX220-LAB 2006-10-08 15:17:10

RADIO NETWORK FALLBACK ACTIVATION STARTED

RNW PLAN DATABASE STATE ..................... ACT_INIT


COMMAND EXECUTED

The execution printout of command example 4 is:

BSC DX220-LAB 2006-10-08 15:17:12

RADIO NETWORK PLAN DATABASE ACTIVATION INTERRUPTION STARTED

RNW PLAN DATABASE STATE .................... INTERRUPTED

DN9813184 # Nokia Corporation 95 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

96 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEK OUTPUT RNW PLAN DATA ACTIVATION STATES

EEK OUTPUT RNW PLAN DATA ACTIVATION


STATES
Function With the EEK command you output the activation state of RNW object and RNW
plan state.

Parameters BCF identification, BTS identification, SEG identification, YES TRXs to output;

Syntax EEK: ( BCF = <BCF identification> |


BTS = <BTS identification> |
SEG = <SEG identification> | ) :

( TRXINFO = <TRXs to output> | def = Y |


<RNW plan database state def> ) ... ;

Parameter BCF identification


explanations
BCF = desimal number

With this parameter you identify the base control function. The value range
depends on the BSC hardware configuration and the corresponding options. You
can enter multiple BCFs by using characters & and &&. You can enter only one
of the parameters BCF, BTS and SEG in the same command.

BTS identification

BTS = desimal number

With this parameter you identify the BTS. The value range depends on the BSC
hardware configuration and the corresponding options. You can enter multiple
BTSs by using characters & and &&. You can enter only one of the parameters
BCF, BTS and SEG in the same command.

SEG identification

SEG = desimal number

DN9813184 # Nokia Corporation 97 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you identify the segment. You can enter several values at the
same time by using characters & or &&. You can enter only one of the parameters
BCF, BTS and SEG in the same command.

TRXs to output

TRXINFO = text string

With this parameter you define if TRX information is printed out or not. The
default value is Y.

Parameter Value Explanation


TRXINFO = Y TRXs are printed out.
N TRXs are not printed out.

Examples 1. Output the RNW plan data activation states under BCF 1 to 5.

EEK:BCF=1&&5;
2. Output the RNW plan data activation states under BCF 1 to 5 and
TRXINFO=N.
EEK:BCF=1&&5:TRXINFO=N;
3. Output the RNW plan data activation states under BTS 1 to 5.
EEK:BTS=1&&5;
4. Output the RNW plan data activation states under SEG 1 and 2.
EEK:SEG=1&2;
5. Output the RNW plan data activation states under SEG 1 to 2 and
TRXINFO=N.
EEK:SEG=1&2:TRXINFO=N;
6. Output the RNW plan data activation states.
EEK:;

Execution printouts The abbreviations used in the execution printouts:

BCF Base Control Function


SEG Segment
BTS Base Transceiver Station
TRXINFO Transceiver info
NO PLAN There is no plan for the object

98 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEK OUTPUT RNW PLAN DATA ACTIVATION STATES

PLANNED Object has changes in plan


ACTIVATED Planned change is activated for the object
CLEAR RNW plan does not exist
DOWNLOAD_INIT
Initialisation of RNW Plan database is ongoing
DOWNLOADING Download is ongoing
DOWNLOADED The RNW plan is downloaded; the database is initialised
and changes in the plan are made into the database
VALIDATING Validation of the plan database is ongoing
VALIDATING_NO_INT
Validation of the plan database is ongoing, BSC Radio
Network configuration changes are denied
VALIDATED Validation is done; RNW plan database is ready to be
activated
ACT_INIT Fallback copy is dumped to disk
ACTIVATING Activation of the plan database is ongoing
ACTIVATED RNW plan is activated
FALLBACK_ACT Fallback activation is ongoing
FALLBACK_INIT Fallback copy is loaded to memory
INTERRUPTED Activation is interrupted
INTERRUPTED_BY_SYSTEM
Activation is interrupted by the system; only fallback
activation is allowed in this state
WO The object is in the normal function state
BL_USR The operator has blocked the object out of use

The execution printout of command example 1 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE STATES IN BSC:

RNW PLAN DATABASE STATE ..................... ACTIVATING


RNW CONFIGURATION ID......................... 0
RNW PLAN CONFIGURATION ID.................... 1
RNW FALLBACK CONFIGURATION ID................ 0

BCF BTS TRX ACTIVATION STATE OP STATE


======== ========= ======== ================= ======

BCF-0001 ACTIVATED WO
BTS-0001 ACTIVATED WO
TRX-001 ACTIVATED BL_USR
TRX-002 ACTIVATED WO

DN9813184 # Nokia Corporation 99 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

BCF-0004 PLANNED WO
BTS-0004 PLANNED BL_USR
TRX-001 PLANNED BL_USR
TRX-002 PLANNED BL_USR

BCF-0005 PLANNED BL_USR

COMMAND EXECUTED

The execution printout of command example 2 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE STATES IN BSC:

RNW PLAN DATABASE STATE ..................... ACTIVATING


RNW DATABASE CONFIGURATION ID................ 0
RNW PLAN DATABASE CONFIGURATION ID........... 1
RNW FALLBACK CONFIGURATION ID................ 0

BCF BTS TRX ACTIVATION STATE OP STATE


======== ========= ======== ================= ======

BCF-0001 ACTIVATED WO
BTS-0001 ACTIVATED WO
BCF-0004 PLANNED WO
BTS-0004 PLANNED BL_USR

BCF-0005 PLANNED BL_USR

COMMAND EXECUTED

The execution printout of command example 3 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE STATES IN BSC:

RNW PLAN DATABASE STATE ..................... ACTIVATING


RNW CONFIGURATION ID......................... 1
RNW PLAN CONFIGURATION ID....... ............ 1
RNW FALLBACK CONFIGURATION ID................ 1

BTS TRX ACTIVATION STATE OP STATE


========= ======== ================= ======

BTS-0001 ACTIVATED WO
TRX-001 ACTIVATED WO
TRX-002 ACTIVATED BL_USR
TRX-003 ACTIVATED WO

100 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEK OUTPUT RNW PLAN DATA ACTIVATION STATES

BTS-0004 PLANNED WO
TRX-001 PLANNED BL_USR
TRX-002 PLANNED BL_USR
TRX-003 PLANNED BL_USR

BTS-0005 PLANNED BL_USR

COMMAND EXECUTED

The execution printout of command example 4 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE STATES IN BSC:

RNW PLAN DATABASE STATE ..................... ACTIVATING


RNW CONFIGURATION ID......................... 1
RNW PLAN CONFIGURATION ID.................... 1
RNW FALLBACK CONFIGURATION ID................ 1

SEG BTS TRX ACTIVATION STATE OP STATE


======== ======== ======= ================= ======

SEG-0001
BTS-0001 ACTIVATED WO
BTS-0004 ACTIVATED WO
BTS-0005 ACTIVATED WO
TRX-001 ACTIVATED WO
TRX-002 ACTIVATED WO
TRX-003 ACTIVATED WO

SEG-0002
BTS-0002 ACTIVATED WO
BTS-0006 ACTIVATED WO
BTS-0007 PLANNED WO

COMMAND EXECUTED

The execution printout of command example 5 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE STATES IN BSC:

RNW PLAN DATABASE STATE ..................... ACTIVATING


RNW DATABASE CONFIGURATION ID................ 1
RNW PLAN DATABASE CONFIGURATION ID........... 1
RNW FALLBACK CONFIGURATION ID................ 1

DN9813184 # Nokia Corporation 101 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

SEG BTS TRX ACTIVATION STATE OP STATE


======== ======== ======= ================= ======

SEG-0001
BTS-0001 ACTIVATED WO
BTS-0004 ACTIVATED WO
BTS-0005 ACTIVATED WO

SEG-0002
BTS-0002 ACTIVATED WO
BTS-0006 ACTIVATED WO
BTS-0007 PLANNED WO

COMMAND EXECUTED

The execution printout of command example 6 is:

BSC DX220-LAB 2006-10-08 15:17:09

RADIO NETWORK PLAN DATABASE STATES IN BSC:

RNW PLAN DATABASE STATE ..................... DOWNLOADED


RNW CONFIGURATION ID......................... 1
RNW PLAN CONFIGURATION ID.................... 1
RNW FALLBACK CONFIGURATION ID................ 1

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

102 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEO OUTPUT BASE STATION CONTROLLER PARAMETERS

EEO OUTPUT BASE STATION CONTROLLER


PARAMETERS
Function With the EEO command you output the parameters of a BSC object in the BSS
Radio Network Configuration Database (BSDATA).

Parameters parameter group;

Syntax EEO: [ <parameter group> | <GEN> def ] ;

Parameter parameter group


explanations
With this parameter you define the name of the base station controller parameter
group that is output:
GEN general base station controller parameters
SUP radio network supervision parameters
MIS miscellaneous parameters
QOS quality of service parameters <option>
DFCA dynamic frequency and channel allocation parameters
<option>
PRI priority level to subscriber types <option>
GPRS GPRS parameters <option>
ALL all parameters

The default is the GEN parameter group.

Examples 1. Output the general base station controller parameters group.

ZEEO;
2. Output radio network supervision parameters of the BSC.
ZEEO:SUP;
3. Output all BSC parameters.

DN9813184 # Nokia Corporation 103 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

ZEEO:ALL;

Execution printouts 1. The execution printout of command example 3 is:

BSC BSC-LAB 2006-10-11 09:51:32

BASE STATION CONTROLLER DATA

BACKGROUND DATA STATE .............................. CLEAR

NUMBER OF PREFERRED CELLS ........................ (NPC).... 1


GSM MACROCELL THRESHOLD .......................... (GMAC)... 35 dBm
GSM MICROCELL THRESHOLD .......................... (GMIC)... 33 dBm
DCS MACROCELL THRESHOLD .......................... (DMAC)... 26 dBm
DCS MICROCELL THRESHOLD .......................... (DMIC)... 24 dBm
MS DISTANCE BEHAVIOUR ............................ (DISB)... 3 s
(RELEASE AFTER TIME IF HANDOVER IS UNSUCCESFUL)
BTS SITE BATTERY BACKUP FORCED HO TIMER .......... (TIM).... 30 s
EMERGENCY CALL ON FACCH .......................... (EEF).... Y
ANSWER TO PAGING CALL ON FACCH ................... (EPF).... Y *)
ORDINARY CALLS ON FACCH .......................... (EOF).... Y *)
RE-ESTABLISHMENT ON FACCH ........................ (ERF).... Y *)
TCH IN HANDOVER .................................. (HRI).... 3
(CHANNEL RATE AND SPEECH CODEC CHANGES ARE DENIED TOTALLY)
LOWER LIMIT FOR FR TCH RESOURCES ................. (HRL).... 18 %
UPPER LIMIT FOR FR TCH RESOURCES ................. (HRU).... 68 %
BSC CALL NUMBER .................................. (BCN).... 0000
AMH UPPER LOAD THRESHOLD ......................... (AUT).... 80 %
AMH LOWER LOAD THRESHOLD ......................... (ALT).... 20 %
AMH MAX LOAD OF TARGET CELL ...................... (AML).... 70 %
AMR CONFIGURATION IN HANDOVERS ................... (ACH).... 1
INITIAL AMR CHANNEL RATE ......................... (IAC).... 1
SLOW AMR LA ENABLED .............................. (SAL).... N
AMR SET GRADES ENABLED ........................... (ASG).... N
FREE TSL FOR CS DOWNGRADE ........................ (CSD).... 95 %
FREE TSL FOR CS UPGRADE .......................... (CSU).... 4 s
TRHO GUARD TIME .................................. (TGT).... 30 s
PRIORITY HO INTERFERENCE DL ...................... (HDL).... INTER
PRIORITY HO INTERFERENCE UL ...................... (HUL).... INTER
LOAD RATE FOR CHANNEL SEARCH ..................... (CLR).... 100 %
TRIGGERING THRESHOLD FOR SERVICE AREA PENALTY..... (TTSAP).. 127
PENALTY TRIGGER MEASUREMENT PERIOD ............... (PTMP)... 128 s
SERVICE AREA PENALTY TIME ........................ (SAPT)... 127 s
CS TCH ALLOCATE RTSL0 ............................ (CTR).... N
CS TCH ALLOCATION CALCULATION .................... (CTC).... 0
NACC ENABLED ..................................... (NACC)... N
NCCR CONTROL MODE ................................ (NCM).... 0
(NCCR IS DISABLED FOR ALL MOBILE STATIONS)
NCCR IDLE MODE REPORTING PERIOD .................. (NIRP)... 3.84 s
NCCR TRANSFER MODE REPORTING PERIOD .............. (NTRP)... 0.48 s
NCCR RETURN TO OLD CELL TIME ..................... (NOCT)... 10 s
NCCR TARGET CELL PENALTY TIME .................... (NTPT)... 10 s
NCCR NEIGHBOR CELL PENALTY ....................... (NNCP)... 6 s
WCDMA FDD NCCR ENABLED ........................... (WFNE)... N

104 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEO OUTPUT BASE STATION CONTROLLER PARAMETERS

WCDMA FDD NCCR PREFERRED ......................... (WFNP)... Y

MINIMUM MEAN HOLDING TIME FOR TCHS ............... (MINHTT). 65535 s


MAXIMUM MEAN HOLDING TIME FOR TCHS ............... (MAXHTT). 1440 min
MAXIMUM MEAN HOLDING TIME FOR SDCCHS ............. (MAXHTS). 30 min
ALARM THRESHOLD FOR TCH FAILURE RATE ............. (TCHFR).. 20 %
ALARM THRESHOLD FOR SDCCH FAILURE RATE ........... (SCHFR).. 80 %
ALARM THRESHOLD FOR TCH CONGESTION ............... (CNGT)... 20 %
ALARM THRESHOLD FOR SDCCH CONGESTION ............. (CNGS)... 20 %
ALARM THRESHOLD FOR NUMBER OF CHANNEL SEIZURES ... (CS)..... 10
ALARM THRESHOLD FOR NUMBER OF CH SEIZURE REQUESTS (CSR).... 100
MEAS PRD FOR TCH MEAN HOLDING TIME SUPERVISION ... (PRDMHT). 240 min
MEAS PRD FOR SDCCH MEAN HOLDING TIME SUPERVISION . (PRDMHS). 0 min
DEACTIVATED
MEAS PRD FOR SUPERVISION OF CHANNEL FAILURE RATE . (PRDCFR). 240 min
MEAS PRD FOR SUPERVISION OF CONGESTION IN BTS .... (PRDCNG). 120 min
THRESHOLD FOR HIGH TCH INTERFERENCE LEVEL ........ (HIFLVL). 4
ALARM THRESHOLD FOR SHARE OF HIGH TCH INTERFERENCE (HIFSHR). 50 %
MEAS PRD FOR HIGH TCH INTERFERENCE SUPERVISION ... (PRDHIF). 120 min
MEAS PRD FOR SUPERVISION OF BTS WITH NO TRANSACT . (PRDBNT). 120 min
STARTING MOMENT FOR SUPERVISION OF BTS ........... (SMBNT).. 08-00
ENDING MOMENT FOR SUPERVISION OF BTS ............. (EMBNT).. 18-00
GPRS TERRITORY UPDATE GUARD TIME ................. (GTUGT)... 5 s

BCSU LOAD THRESHOLD .............................. (BCSUL).. 48.00 %


LAPD LOAD THRESHOLD .............................. (LAPDL).. 8.40 %
UPPER LIMIT OF MS SPEED CLASS 1 .................. (MSSCF).. 10 ( 20 km/h)
UPPER LIMIT OF MS SPEED CLASS 2 .................. (MSSCS).. 105 (210 km/h)
ALARM LIMIT FOR FULL RATE TCH AVAILABILITY ....... (ALFRT).. 30 %
ALARM LIMIT FOR HALF RATE TCH AVAILABILITY ....... (ALHRT).. 30 %
ALARM LIMIT FOR SDCCH AVAILABILITY ............... (ALSDC).. 30 %
DISABLE INTERNAL HO .............................. (DINHO).. N
DISABLE EXTERNAL DR .............................. (DEXDR).. N
RX LEVEL BALANCE ................................. (RXBAL).. 5 dB
RX ANTENNA SUPERVISION PERIOD .................... (RXANT).. 65535 min
(RX ANTENNA SUPERVISION IS NOT PERFORMED)
NUMBER OF IGNORED TRANSCODER FAILURES ............ (ITCF)... 0
VARIABLE DL STEP SIZE ............................ (VDLS)... N
MAXIMUM NUMBER OF DL TBF ......................... (MNDL)... 9
MAXIMUM NUMBER OF UL TBF ......................... (MNUL)... 7
FEP IN PC HO USE ................................. (FPHO)... N
INTRA SEGMENT SDCCH HO GUARD ..................... (ISS).... 255 s
PRE-EMPTION USAGE IN HANDOVER .................... (PRE).... Y
WPS PRIORITY CAPACITY ............................ (WPIC)... 25 %
WPS PREFERENCE CAPACITY .......................... (WPEC)... 50 %
PUBLIC SERVED COUNT .............................. (PSC).... 2
TIME LIMIT WPS ................................... (TLW).... 28 s
TIME LIMIT WPS HANDOVER .......................... (TLWH)... 5 s
IMSI BASED HANDOVER GSM CELLS ANONYMOUS MS ....... (IBGA)... ALL
IMSI BASED HANDOVER WCDMA CELLS ANONYMOUS MS ..... (IBWA)... ALL
SOFT BLOCKING C/N FR ............................. (SBCNF).. 12 dB
SOFT BLOCKING C/N HR ............................. (SBCNH).. 0 dB
SOFT BLOCKING C/N 14.4 ........................... (SBCN)... 14 dB
SOFT BLOCKING C/N AMR FR ......................... (SBCNAF). 7 dB
SOFT BLOCKING C/N AMR HR ......................... (SBCNAH). 12 dB
RX LEVEL BASED TCH ACCESS ........................ (RXTA)... 0

DN9813184 # Nokia Corporation 105 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

(RX LEVEL BASED TCH ACCESS IS NOT USED)


DELAY OF HO AND PC FOR EMERGENCY CALLS ........... (DEC).... 5 s
INTERNAL HANDOVER TO EXTERNAL .................... (IHTA)... 0
TCH TRANSACTION COUNT ............................ (TTRC)... 10
MAXIMUM TCH TRANSACTION RATE ..................... (MTTR)... 50

DL HIGH PRIORITY SSS ............................. (DHP).... 6


DL NORMAL PRIORITY SSS ........................... (DNP).... 6
DL LOW PRIORITY SSS .............................. (DLP).... 12
UL PRIORITY 1 SSS ................................ (UP1)... 3
UL PRIORITY 2 SSS ................................ (UP2)... 6
UL PRIORITY 3 SSS ................................ (UP3)... 9
UL PRIORITY 4 SSS ................................ (UP4)... 12
BACKGROUND TC SCHEDULING WEIGHT FOR ARP 1 ........ (BGSW1).. 20
BACKGROUND TC SCHEDULING WEIGHT FOR ARP 2 ........ (BGSW2).. 10
BACKGROUND TC SCHEDULING WEIGHT FOR ARP 3 ........ (BGSW3).. 5
QC REALLOCATION ACTION TRIGGER THRESHOLD ......... (QCATR).. 25 BLOCK PERIODS
QC NCCR ACTION TRIGGER THRESHOLD ................. (QCATN).. 100 BLOCK PERIODS
QC QOS RENEGOTIATION ACTION TRIGGER THRESHOLD .... (QCATQ).. 200 BLOCK PERIODS
QC DROP ACTION TRIGGER THRESHOLD ................. (QCATD).. 400 BLOCK PERIODS
PFC UNACK BLER LIMIT FOR SDU ERROR RATIO 1 ....... (UBL1)... 10
PFC ACK BLER LIMIT FOR TRANSFER DELAY 1 .......... (ABL1)... 70 %
MEAN BEP LIMIT MS MULTISLOT PWR PROF 0 WITH 2 UL TSL .. (BL02).. 6 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 0 WITH 3 UL TSL .. (BL03).. 7 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 0 WITH 4 UL TSL .. (BL04).. 7 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 1 WITH 2 UL TSL .. (BL12).. 4 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 1 WITH 3 UL TSL .. (BL13).. 5 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 1 WITH 4 UL TSL .. (BL14).. 6 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 2 WITH 3 UL TSL .. (BL23).. 6 dB
MEAN BEP LIMIT MS MULTISLOT PWR PROF 2 WITH 4 UL TSL .. (BL24).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 0 WITH 2 UL TSL ... (RL02).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 0 WITH 3 UL TSL ... (RL03).. 5 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 0 WITH 4 UL TSL ... (RL04).. 6 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 1 WITH 2 UL TSL ... (RL12).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 1 WITH 3 UL TSL ... (RL13).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 1 WITH 4 UL TSL ... (RL14).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 2 WITH 3 UL TSL ... (RL23).. 7 dB
RX QUAL LIMIT MS MULTISLOT PWR PROF 2 WITH 4 UL TSL ... (RL24).. 6 dB
EGPRS INACTIVITY CRITERIA ............................. (EGIC).. 0
EVENTS PER HOUR FOR EGPRS INACTIVITY ALARM ............ (IEPH).. 10
SUPERVISION PERIOD LENGTH FOR EGPRS INACTIVITY ALARM ... (SPL).. 60 min
DTM PFC PACKET FLOW TIMER ............................ (DPPFT).. 4 s
DTM FRAGMENTATION PENALTY .............................. (DFP).. 0.3
ISHO PREFERRED FOR NON-DTM MS.......................... (IPND).. N

C/I TARGET FR .................................... (CIF).... 9 dB


SOFT BLOCKING C/I FR ............................. (SBF).... 0 dB
C/I TARGET UL OFFSET ............................. (CIUL)... 0 dB
C/I TARGET HR .................................... (CIH).... 14 dB
SOFT BLOCKING C/I HR ............................. (SBH).... 0 dB
C/I TARGET 14.4 .................................. (CIT).... 16 dB
SOFT BLOCKING C/I 14.4 ........................... (SBCI)... 0 dB
C/I TARGET AMR FR ................................ (CIAF)... 8 dB
SOFT BLOCKING C/I AMR FR ......................... (SBAF)... 0 dB
C/I TARGET AMR HR ................................ (CIAH)... 12 dB
SOFT BLOCKING C/I AMR HR ......................... (SBAH)... 0 dB

106 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEO OUTPUT BASE STATION CONTROLLER PARAMETERS

BIM CONFIDENCE PROBABILITY ....................... (BCP).... 90 %


BIM INTERFERENCE THRESHOLD ....................... (BIT).... 30 dB
BIM UPDATE PERIOD ................................ (BUP).... 60 min
BIM UPDATE SCALING FACTOR ........................ (BUSF)... 0.5
BIM UPDATE GUARD TIME ............................ (BUGT)... 10
DFCA CHANNEL ALLOCATION METHOD ................... (DCAM)... 0
EXPECTED BSC-BSC INTERFACE DELAY ................. (EBID)... 50 ms
SAIC DL C/I OFFSET ............................... (SCIO)... 3 dB

PRIORITY LEVEL SUBSCRIBER TYPE

1 0 (GSM SUBSCRIBER)
2 0 (GSM SUBSCRIBER)
3 0 (GSM SUBSCRIBER)
4 0 (GSM SUBSCRIBER)
5 1 (MCN SUBSCRIBER)
6 1 (MCN SUBSCRIBER)
7 1 (MCN SUBSCRIBER)
8 1 (MCN SUBSCRIBER)
9 1 (MCN SUBSCRIBER)
10 2 (PRIORITY SUBSCRIBER)
11 0 (GSM SUBSCRIBER)
12 2 (PRIORITY SUBSCRIBER)
13 0 (GSM SUBSCRIBER)
14 0 (GSM SUBSCRIBER)

*) NOT ACTIVE IN PRFILE

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

DN9813184 # Nokia Corporation 107 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

108 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEI OUTPUT RADIO NETWORK CONFIGURATION

EEI OUTPUT RADIO NETWORK


CONFIGURATION
Function With the EEI command you interrogate the radio network in the BSDATA. The
program outputs the whole radio network configuration or the configuration
under given BCFs, SEGs or BTSs.

Parameters BCF identification, SEG identification <option>, SEG name <option>, BTS
identification, BTS name: output type;

Syntax
EEI: [ [ BCF = <BCF identification> ... |
SEG = <SEG identification> ... <option> |
SEGNAME = <SEG name> ... <option> |
BTS = <BTS identification> ... |
NAME = <BTS name> ... ] | <all> def ] :

[ <output type> | <NORM> def ] ;

Parameter BCF identification


explanations
BCF = decimal number

With this parameter you identify the base control function. The value range
depends on the BSC hardware configuration and the corresponding options. You
can enter multiple BCFs by using characters & and &&. You can enter only one
of the parameters BCF, SEG, SEGNAME, BTS or NAME in the same command.

SEG identification <option>

SEG = decimal number or ALL

With this parameter you identify the segment. The value range is the same as the
BTS identification value range. With ALL you can output all segments under a
BSC.

DN9813184 # Nokia Corporation 109 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

You can enter several values at the same time by using characters & or &&. You
can enter only one of the parameters BCF, SEG, SEGNAME, BTS or NAME in
the same command.

SEG name <option>

SEGNAME = text string

With this parameter you identify the segment by its name. The name can contain
1 to 15 characters.

You can enter several names at the same time by using character &. You can enter
only one of the parameters BCF, SEG, SEGNAME, BTS or NAME in the same
command.

BTS identification

BTS = decimal number

With this parameter you identify the BTS with a decimal number. The value
range depends on the BSC hardware configuration and the corresponding
options. You can enter multiple BTSs by using characters & and &&. You can
enter only one of the parameters BCF, SEG, SEGNAME, BTS or NAME in the
same command.

BTS name

NAME = text string

With this parameter you identify the BTS by name. The name can contain 1...15
characters. You can enter multiple BTS names by using the character &. You can
enter only one of the parameters BCF, SEG, SEGNAME, BTS or NAME in the
same command.

output type

With this parameter you define the output type. The output type can be:
NORM for the normal radio network configuration output
BCSU for the following information:

. the number of created TRXs and D-channel links under BCSUs


. the number of real TCHs in the BCSUs

110 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEI OUTPUT RADIO NETWORK CONFIGURATION

. the maximum TRX capacity in the BSC supported by hardware


. the maximum TRX capacity in the BSC supported by hardware and
software.

When calculating these numbers, all BCSUs in the WO (working) state are
included.

The number of real TCHs is defined so that one full rate supporting resource
corresponds to one TCH resource and one half rate or dual rate supporting
resource corresponds to two TCH resources.

If you enter the command with this parameter only (ZEEI::BCSU;), the normal
radio network configuration output is not shown.

The default value is NORM.

You may find it useful to output the number of TRXs under BCSUs when you are
creating a new BTS site.

Note

The number of TRXs under all BCSUs is shown even if you only output the
radio network under certain BCFs or BTSs (ZEEI:BCF=1:BCSU;).

Examples 1. Output the network.

ZEEI;
2. Output the network under BCFs 1, 10, 11 and 12.
ZEEI:BCF=1&10&&12;
3. Output the network under BTS 4.
ZEEI:BTS=4;
4. Output the network under BTS CITY1.
ZEEI:NAME=CITY1;
5. Output the number of TRXs and links under BCSUs.
ZEEI::BCSU;
6. Output the network under all segments.
ZEEI:SEG=ALL;

DN9813184 # Nokia Corporation 111 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Additional The TRX's EDGE information is not valid if the TRX hardware has been changed
information and the TRX has not been unlocked after that.

Execution printouts The abbreviations used in the execution printout:

BCF= Base Control Function


SEG= Segment
BCSU= BSC signalling unit
BL= Blocked
BL-BCF= The object is blocked out of use due to a fatal BTS-site-
wide failure.
BL-BTS= The object is blocked out of use due to a fatal sector-wide
failure on the BTS site.
BL-CF= The object is blocked out of use due to both a fatal Frame
Unit (FU) and a fatal Carrier Unit (CU) failure on the BTS
site.
BL-CLK= The object is blocked out of use due to a clock
synchronisation failure on the BTS site.
BL-CU= The object is blocked out of use due to a fatal Carrier Unit
(CU) failure on the BTS site.
BL-DGN= The object is blocked temporarily out of use due to base
station diagnostic activities.
BL-FLO= The logical TRX is blocked out of use on the sector
because the physical TRX is switched to another sector of
the BTS in order to replace a faulty TRX.
BL-FU= The object is blocked out of use due to a fatal Frame Unit
(FU) failure on the BTS site.
BL-PWR= The object is blocked out of use due to a mains power
failure on the BTS site.
BL-RSL= The object is blocked out of use due to a telecom Abis D-
channel link disconnection.
BL-RST= The logical radio network object is blocked out of use due
to the reset of the corresponding physical radio network
equipment.
BL-SHD= The object will be blocked out of use within a time limit.
New call attempts are prohibited via an object in the BL-
SHD state and forced handovers are executed for ongoing
calls via the object.
BL-SU= The object is blocked out of use due to a BCSU unit reset
on the BSC.
BL-SWO= The object is blocked out of use due to an ongoing
background data switchover.

112 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEI OUTPUT RADIO NETWORK CONFIGURATION

BL-SYS= The radio network management function class of the BSC


has blocked the logical object out of use due to ongoing
radio network recovery actions which are triggered
because of fatal faults in the BSS radio network.
BL-TRX= The object is blocked out of use due to a fatal TRX-wide
failure on the BTS site.
BL-TST= The object is blocked temporarily out of use due to radio
network testing activities.
BL-USR= The operator has blocked the object out of use. The
administrative state of the object is LOCKED or the
related higher-level object is LOCKED.
BL-WAC= The object is blocked out of use, because it is waiting for
the Autoconfiguration or the Automatic Picocell Planning.
BTS= Base Transceiver Station
CBCH= Cell broadcast channel
DFCA = Dynamic frequency and channel allocation
EDGE = Enhanced data rates for global evolution
ERACH= Extended random access channel
ET-PCM= PCM number of Abis circuit
ETRX= E-TRX type
FR= Full rate
FREQ= Absolute radio frequency number to the TRX
FRT= TRX frequency type
FTRX= A floating TRX, that is, a transceiver unit which can be
dynamically switched to operate in any of the BTS's
sectors. The floating TRX automatically replaces a faulty
BCCH TRX.
GP= Busy GPRS
HR= Half rate
L= The object is LOCKED and is not in the active radio
network of the BSS. It is blocked out of use from the
viewpoint of the BSS call control functions.
MBCCB= Combined broadcast control channel with cell broadcast
channel
MBCCH= Broadcast control channel
MBCCHC= Combined broadcast control channel
MPBCCH= Packet control channel
PREF= Preferred BCCH TRX
SD= Shutting down
SP= Spare
TRX= Transceiver

DN9813184 # Nokia Corporation 113 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

*TRX= A BCCH TRX which is replaced by the floating TRX.


U= The object is in the active radio network of the BSS. From
the viewpoint of the call control functions, the
UNLOCKED radio network resource is available if the
related higher-level objects are also UNLOCKED.
UA= Unavailable
WO= The object is in the normal function state. From the
viewpoint of the BSS call control functions, the
WORKING radio network resource is available for call
control use.

The printout of the command ZEEI:BCF=1&13; is:

BSC BSC-LAB 2006-10-26 10:11:32

RADIO NETWORK CONFIGURATION IN BSC:


E P B
F T R C D-CHANNEL BUSY
AD OP R ET- BCCH/CBCH/ R E S O&M LINK HR FR
LAC CI HOP ST STATE FREQ T PCM ERACH X F U NAME ST /GP
===================== == ====== ==== == ==== =========== = = == ===== == === ===
BCF-0001 FLEXI EDGE U WO 1 OM1 WO
00001 00001 BTS-0001 U WO 2 4
CENTRUM1 RF/– 3
TRX-001 U WO 124 0 18 MBCCH+CBCH P 1
TRX-002 L BL-USR 20 0 18 1
TRX-003 L BL-USR 22 0 18 1
TRX-006 U WO 24 0 18 1
BTS-0002 U WO 6
CENTRUM2 RF/– 5
TRX-004 U WO 30 0 18 MBCCH P 1
TRX-005 U WO 32 0 18 ERACH E 1
TRX-007 U WO 34 0 18 E 1

BCF-0013 TALK-FAMILY U WO 2 OM13 WO


00001 00003 BTS-0011 U WO 1 5
COUNTRYSIDE1 BB/ –
*TRX-001 U WO 100 0 19 MBCCH+CBCH 2
00001 00004 BTS-0021 U WO 4
COUNTRYSIDE2 –/–
TRX-005 U WO 118 0 19 MBCCHC P 2
FTRX-007 U BL-FLO 122 0 19 2

COMMAND EXECUTED

The printout of command example 5 is:

BSC BSC-LAB 2006-10-18 08:19:12

NUMBER OF CREATED TRXS, LINKS AND REAL TCHS UNDER BCSUS:

114 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEI OUTPUT RADIO NETWORK CONFIGURATION

D-CHANNEL D-CHANNEL REAL


UNIT TRXS TELECOM LINKS O&M LINKS TCHS
======== ====== ============= ========= ======
BCSU-1 40 40 8 310
BCSU-2 40 40 8 310
BCSU-3 40 40 8 310
BCSU-4 40 40 8 310
BCSU-5 40 40 8 310
BCSU-6 40 40 8 310
BCSU-7 40 40 8 310
BCSU-8 40 40 8 310
======== ====== ======
TOTAL 320 2480

HARDWARE SUPPORTED MAXIMUM TRX CAPACITY : 384


HW AND SW SUPPORTED MAXIMUM TRX CAPACITY: 384

COMMAND EXECUTED

The printout of command example 6 is:

BSC BSC-LAB 2006-10-26 10:11:32

RADIO NETWORK CONFIGURATION IN BSC:


E P B
F T R C D-CHANNEL BUSY
AD OP R ET- BCCH/CBCH/ R E S O&M LINK HR FR
LAC CI HOP ST STATE FREQ T PCM ERACH X F U NAME ST /GP
===================== == ====== ==== == ==== =========== = = == ===== == === ===
00001 00001 SEG-0001 BIG_CENTRUM
BCF-0001 TALK-FAMILY U WO 1 OM1 WO
BTS-0001 U WO 2 4
CENTRUM1 RF/– 3
TRX-001 U WO 124 0 33 MBCCHC P 1
TRX-002 L BL-USR 20 0 33 1
TRX-003 L BL-USR 22 0 34 1
TRX-006 U WO 24 0 36 8
BCF-0005 ULTRASITE U WO 4 OM85 WO
BTS-0002 U WO 6
CENTRUM2 –/RF 5
EDGE TRX-004 U WO 30 0 44 P 4
EDGE TRX-005 U WO 32 0 44 4
EDGE TRX-007 U WO 34 0 44 4

00001 00003 SEG-0013 BIG_COYNTRY13


BCF-0013 TALK-FAMILY U WO 2 OM120 WO
BTS-0011 U WO 1 5
COUNTRYSIDE1 BB/–
TRX-001 U WO 100 0 72 MBCCHC 0

00001 00004 SEG-0015 BIG_COYNTRY15

DN9813184 # Nokia Corporation 115 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

BCF-0015 ULTRASITE U WO 2 OM125 WO


BTS-0015 U WO 1 5
COUNTRYSIDE15 RF/DF
TRX-001 U WO 101 0 73 MBCCHC 0
DFCA TRX-002 U WO 103 0 73 0
DFCA TRX-003 U WO 105 0 73 0

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

116 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEL OUTPUT TRX RADIO TIME SLOTS

EEL OUTPUT TRX RADIO TIME SLOTS


Function With the EEL command you output the TRX's radio time slots that are in a given
operational state.

Parameters operational state: BCF identification, BTS identification, BTS name;

Syntax
EEL: [ <operational state> ] :

[ [ BCF = <BCF identification> ... |


BTS = <BTS identification> ... |
NAME = <BTS name> ... ] | <all> def ] ;

Parameter operational state


explanations
With this parameter you define the radio time slot's operational state. The inquiry
from the BSDATA is based on this state.

The state values are:


BL= blocked
BL-BCF= blocked-bcf_fault
BL-BTS= blocked-bts_fault
BL-CF= blocked-cu/fu_fault
BL-CLK= blocked-clock_fault
BL-CU= blocked-cu_fault
BL-DGN= blocked-diagnostic
BL-FLO= blocked-floating
BL-FTY= blocked-faulty
BL-FU= blocked-fu_fault
BL-PWR= blocked-mains_power_fault
BL-RSL= blocked-rsl_fault
BL-RST= blocked-reset
BL-SHD= blocked-shutting_down
BL-SU= blocked-bcsu_reset

DN9813184 # Nokia Corporation 117 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

BL-SWO= blocked-background_data_switchover
BL-SYS= blocked-system
BL-TRX= blocked-trx_fault
BL-TSL= blocked-timeslot_fault
BL-TST= blocked-testing
BL-USR= blocked-user
BL-WAC= blocked-waiting for autoconfiguration

If you give the BL parameter value, the program outputs all radio time slots of the
TRX that are in the BL state or its substate. If you give the BL-FTY parameter
value, the program outputs the same information except for the TRX's radio time
slots that are in BL-USR or BL-TST state.

If you do not give this parameter, the program outputs only the number of the
idle, busy and blocked radio time slots and GPRS radio time slots.

BCF identification

BCF = decimal number

With this parameter you identify the base control function. The value range
depends on the BSC hardware configuration and the corresponding options. You
can give multiple BCFs by using the characters & and &&. You can only give
one of the parameters BCF, BTS and NAME in the same command.

BTS identification

BTS = decimal number

With this parameter you identify the BTS with a decimal number. The value
range depends on the BSC hardware configuration and the corresponding
options. You can give multiple BTSs by using the characters & and &&. You can
only give one of the parameters BCF, BTS and NAME in the same command.

BTS name

NAME = the name of the BTS

With this parameter you identify the BTS by name. The name can contain 1...15
characters. You can give multiple BTS names by using the character &. You can
only give one of the parameters BCF, BTS and NAME in the same command.

118 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEL OUTPUT TRX RADIO TIME SLOTS

Examples 1. Output the TRX's radio time slots that are in a BL state and under BTSs 3
and 7.

ZEEL:BL:BTS=3&7;
2. Output the TRX's radio time slots that are in a BL state and under BTSs
CITY1 and CITY2.
ZEEL:BL:NAME=CITY1&CITY2;
3. Output the TRX's radio time slots that are in a BL-USR state.
ZEEL:BL-USR;
4. Output BSC network information.
ZEEL;
5. Output the radio time slot status information of BCFs 1 and 2.
ZEEL::BCF=1&3;

Additional If you specify the BCFs and/or BTSs in the EEL command (see examples 1, 2
information and 5), the MML program displays the radio time slot information under the
specified area. If you give the command without parameters, the MML program
displays the radio time slot information under the whole BSC (see execution
printouts).

Execution printouts The abbreviations used in the execution printout:

BCF= Base Control Function


BTS= Base Transceiver Station
CH0= RTSL (radio time slot)
GPRS= General Packet Radio Service
L= The object is LOCKED and is not in the active radio
network of the BSS. It is blocked out of use from the
viewpoint of the BSS call control functions.
SD= Shutting down
TRX= Transceiver
U= The object is in the active radio network of the BSS. From
the viewpoint of the call control functions, the
UNLOCKED radio network resource is available if the
related higher-level objects are also UNLOCKED.
WO= The object is in the normal function state. From the
viewpoint of the BSS call control functions, the
WORKING radio network resource is available for call
control use.

The printout of the command ZEEL:BL:BCF=1&11&12; is:

DN9813184 # Nokia Corporation 119 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

BSC BSC-LAB 2004-11-25 10:11:32

ADM OP
STATE STATE CH0 CH1 CH2 CH3 CH4 CH5 CH6 CH7
===== ====== ====== ====== ====== ====== ====== ====== ====== ======
BCF-0001 U WO
CENTRUM1
BTS-0001 U WO
TRX-001 U BL-RES BL-RES BL-RES BL-RES BL-RES BL-RES BL-RES BL-RES BL-RES
TRX-003 U WO BL-USR
TRX-005 U WO BL-TST
CENTRUM2
BTS-0002 U BL-USR
TRX-007 U BL-USR BL-USR BL-USR BL-USR BL-USR BL-USR BL-USR BL-USR BL-USR

ADM OP
STATE STATE CH0 CH1 CH2 CH3 CH4 CH5 CH6 CH7
===== ====== ====== ====== ====== ====== ====== ====== ====== ======
BCF-0011 U WO
COUNTRY1
BTS-0010 U WO
TRX-001 U BL-SYS BL-SYS BL-SYS BL-SYS BL-SYS BL-SYS BL-SYS BL-SYS BL-SYS
TRX-003 U BL-CU BL-CU BL-CU BL-CU BL-CU BL-CU BL-CU BL-CU BL-CU
TRX-005 U WO BL-TST

BUSY FULL RATE .............. 36


BUSY HALF RATE .............. 12
BUSY SDCCH .................. 16
IDLE FULL RATE .............. 42
IDLE HALF RATE .............. 24
IDLE SDCCH .................. 40
BLOCKED RADIO TIME SLOTS .... 35
GPRS TIME SLOTS ............. 10

COMMAND EXECUTED

The printout of the command example 4 is:

BSC BSC-LAB 2004-08-15 10:13:46

BSC NETWORK INFORMATION:

BUSY FULL RATE .............. 36


BUSY HALF RATE .............. 12
BUSY SDCCH .................. 16
IDLE FULL RATE .............. 42
IDLE HALF RATE .............. 24
IDLE SDCCH .................. 40
BLOCKED RADIO TIME SLOTS .... 35
GPRS TIME SLOTS ............. 10

COMMAND EXECUTED

120 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEL OUTPUT TRX RADIO TIME SLOTS

Semantic error If and error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error /*** ERROR IN RRMPRB COMMUNICATION ***/


messages

The output was successful, but the count information of the radio time slots
cannot be output due to a communication error with the program block.

For more information, see Radio Network Administration.

In addition, the general execution error messages of the MML commands are
used. For more information, see General Error Messages of System.

DN9813184 # Nokia Corporation 121 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

122 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEP OUTPUT BACKGROUND DATA ACTIVATION STATES

EEP OUTPUT BACKGROUND DATA


ACTIVATION STATES
Function With the EEP command you output the background data state and the BTS-
specific background data states in the BSDATA.

Parameters BCF identification, BTS identification, BTS name;

Syntax
EEP: [ [ BCF = <BCF identification> ... |
BTS = <BTS identification> ... |
NAME = <BTS name> ... ] | <all> def ] ;

Parameter BCF identification


explanations
BCF = decimal number

With this parameter you identify the base control function. The value range
depends on the BSC hardware configuration and the corresponding options. You
can give multiple BCFs by using characters & and &&. You can only give one of
the parameters BCF, BTS and NAME in the same command.

BTS identification

BTS = decimal number

With this parameter you identify the BTS with a decimal number. The value
range depends on the BSC hardware configuration and the corresponding
options. You can give multiple BTSs by using characters & and &&. You can
only give one of the parameters BCF, BTS and NAME in the same command.

BTS name

NAME = the name of the BTS

DN9813184 # Nokia Corporation 123 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you identify the BTS by name. The name can contain 1...15
characters. You can give multiple BTSs by using the character &. You can only
give one of the parameters BCF, BTS and NAME in the same command.

Examples 1. Output the background data states.

ZEEP;
2. Output the background data states under BCFs 1, 10, 11 and 12.
ZEEP:BCF=1&10&&12;
3. Output the background data states under BTS 4.
ZEEP:BTS=4;
4. Output the background data states under BTS CITY1.
ZEEP:NAME=CITY1;

Execution printouts The abbreviations used in the execution printout:

ACTIVATING This background data activation state indicates that the


swapping of parameter values between the background
and the active data is going on.
ACTIVATING-INTERRUPTED
This background data activation state indicates that the
ongoing swapping of parameter values has been
interrupted with a command or by a system restart.
BACK-UP This background data activation state indicates that the old
active data is on the background.
CLEAR This background data activation state indicates that the
database contains new background data or that the
interrupted activation is cancelled.
NEW This background data activation state indicates that the
activation of a switchover can be initiated.
NOT DEFINED The background data under the BTS is not defined.
DEFINED The background data under the BTS is changed. The
background and the active data will be swapped in
activation.
SWAPPING This background data state under the BTS indicates that
the swapping between the background and the active data
is going on.
SWAPPED This background data state under the BTS indicates that
the parameter values between the background and the
active data have been swapped.

The printout of the command ZEEP:BCF=1&13; is:

124 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEP OUTPUT BACKGROUND DATA ACTIVATION STATES

BSC BSC-LAB 2004-11-19 10:11:32

RADIO NETWORK BACKGROUND DATA STATES IN BSC:

BACKGROUND DATA STATE............................... ACTIVATING

BTS BACKGROUND
BCF BTS-ID BTS NAME DATA STATE
======== ======== ========= ===============

BCF-0001
BTS-0001 CENTRUM1 SWAPPED
BTS-0002 CENTRUM2 SWAPPED
BCF-0013
BTS-0011 CITY1 SWAPPING
BTS-0021 DEFINED

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error If an error occurs, the general execution error messages of the MML commands
messages are output. For more information, see General Error Messages of System.

DN9813184 # Nokia Corporation 125 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

126 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEC CREATE LAC TO SPC MAPPING INFO <option>

EEC CREATE LAC TO SPC MAPPING INFO


<option>
Function With the EEC command you create LAC to SPC mapping info in the BSDATA.
The command is optional.

Parameters mapping entry index, location area code : signaling point code;

Syntax EEC: MEI = <mapping entry index>,


LAC = <location area code> :
[ SPC = <signaling point code> ... ] ; <option>

Parameter mapping entry index


explanations
MEI = decimal number

With this parameter you define the mapping entry index which is an indication for
a mapping relation between the location area code and the signaling point code in
the LAC to SPC mapping info.

The values range from 1 to 64. If you do not give this parameter, the smallest free
mapping entry index value is searched and used.

location area code

LAC = decimal number

With this parameter you define the location area code which will be mapped with
a signaling point code.

The values range from 1 to 65533.

The parameter is obligatory.

signaling point code

SPC = hexadecimal number or decimal number

DN9813184 # Nokia Corporation 127 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

With this parameter you define the signaling point code which will be mapped
with a location area code.

You can give values either as hexadecimal numbers or decimal numbers. The
values range from 1 to FFFFFF as hexadecimal numbers or from 1 to 16777215
as decimal numbers. If you give a decimal number, you must type characters D'
before the parameter value.

The maximum amount of signaling point codes in one LAC to SPC mapping info
is 6. You can give multiple signaling point codes by using the wild card character
&. You can give the same signaling point code only once. If DFCA is used under
the LAC, give the SPC address of that BSC.

Examples 1. Create LAC to SPC mapping info. The location area code number is 9 and
signaling point codes are 2345, 123455 and 345678. The signaling point
codes are given as decimal numbers.

ZEEC:LAC=9:SPC=D'2345&D'123455&D'345678;
2. Create LAC to SPC mapping info where the mapping entry index is 2,
location area code is 10 and signaling point codes are 1FF, 10FF, 100FF
and 1000FF. The signaling point codes are given as hexadecimal numbers.
ZEEC:MEI=2,LAC=10:SPC=1FF&10FF&100FF&1000FF;

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-09-09 11:11:32

LAC TO SPC MAPPING INFO CREATED

MAPPING ENTRY INDEX ............................ (MEI).... 1


LOCATION AREA CODE ............................. (LAC).... 9
SIGNALING POINT CODES (H/D): 000929/00002345 01E23F/00123455
05464E/00345678

COMMAND EXECUTED

The execution printout of command example 2 is:

BSC BSC-LAB 2004-09-09 11:11:32

LAC TO SPC MAPPING INFO CREATED

MAPPING ENTRY INDEX ............................ (MEI).... 2


LOCATION AREA CODE ............................. (LAC).... 10
SIGNALING POINT CODES (H/D): 0001FF/00000511 0010FF/00004351
0100FF/00065791 1000FF/01048831

COMMAND EXECUTED

128 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEC CREATE LAC TO SPC MAPPING INFO <option>

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error For more information, see Radio Network Administration.


messages

In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.

DN9813184 # Nokia Corporation 129 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

130 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EED DELETE LAC TO SPC MAPPING INFO <option>

EED DELETE LAC TO SPC MAPPING INFO


<option>
Function With the EED command you delete the LAC to SPC mapping info from the
BSDATA. The command is optional.

Parameters mapping entry index, location area code;

Syntax EED: ( MEI = <mapping entry index> |


LAC = <location area code>) ; <option>

Parameter mapping entry index


explanations
MEI = decimal number

With this parameter you define the mapping entry index which indicates a
mapping relation between the location area code and the signaling point code in
the LAC to SPC mapping info.

The values range from 1 to 64.

If you give this parameter, you cannot give the parameter LAC.

location area code

LAC = decimal number

With this parameter you define the location area code which will be mapped with
a signaling point code.

The values range from 1 to 65533.

If you give this parameter, you cannot give the parameter MEI.

Examples 1. Delete the LAC to SPC mapping info whose location area code is 17899.

ZEED:LAC=17899;

DN9813184 # Nokia Corporation 131 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2002-09-09 11:11:32

LAC TO SPC MAPPING INFO DELETED

MAPPING ENTRY INDEX ............................ (MEI).... 1


LOCATION AREA CODE ............................. (LAC).... 17899

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error For more information, see Radio Network Administration.


messages

In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.

132 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEF MODIFY LAC TO SPC MAPPING INFO <option>

EEF MODIFY LAC TO SPC MAPPING INFO


<option>
Function With the EEF command you add and remove signaling point codes to and from
the LAC to SPC mapping info in the BSDATA. You can also modify the location
area codes of the signaling point codes with this command.

Parameters mapping entry index, location are code: identification of function: signaling point
code, new location area code;

Syntax EEF: (( MEI = <mapping entry index> |


LAC = <location area code>) :

<identification of function> :

( SPC = <signaling point code> ... |


NEWLAC = <new location area code> )) ; <option>

Parameter mapping entry index


explanations
MEI = decimal number

With this parameter you define the mapping entry index which is an indication for
a mapping relation between the location area code and the signaling point code in
the LAC to SPC mapping info.

The values range from 1 to 64.

If you give this parameter, you cannot give the parameter LAC.

location area code

LAC = decimal number

With this parameter you define the location area code which will be mapped with
a signaling point code.

The values range from 1 to 65533.

DN9813184 # Nokia Corporation 133 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

If you give this parameter, you cannot give the parameter MEI.

identification of function

With this parameter you identify whether the command adds a signaling point
code to the LAC to SPC mapping info, removes a signaling point code from it or
modifies location area code to LAC to SPC mapping info. The values are:
A Add signaling point codes
R Remove signaling point codes
M Modify location area code.

The parameter is obligatory.

signaling point code

SPC = hexadecimal number or decimal number

With this parameter you define the signaling point code to be added to the LAC to
SPC mapping info or removed from it.

You can give values either as hexadecimal numbers or decimal numbers. The
values range from 1 to FFFFFF as hexadecimal numbers or from 1 to 16777215
as decimal numbers. If you give a decimal number you must type the characters
D' before you give the parameter value.

The maximum number of signaling point codes in one LAC to SPC mapping info
is 6. You can give multiple signaling point codes by using the character &. You
can give the same signaling point code only once.

The parameter is allowed only when you add or remove signaling point codes,
and in that case the parameter is obligatory.

new location area code

NEWLAC = decimal number

With this parameter you define the new location area code.

The values range from 1 to 65533.

The parameter is allowed only when you modify a location area code, and in that
case the parameter is obligatory.

134 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EEF MODIFY LAC TO SPC MAPPING INFO <option>

Examples 1. Add signaling point codes FFFFFF, FFFFFE, FFFFFD, FFFFFC, FFFFFB,
and FFFFFA to the LAC to SPC mapping info whose location area code is
2.

ZEEF:LAC=2:A:
SPC=FFFFFF&FFFFFE&FFFFFD&FFFFFC&FFFFFB&FFFFFA;
2. Remove signaling point code FFFFFE from the LAC to SPC mapping info
whose location area code is 2.
ZEEF:LAC=2:R:SPC=FFFFFE;
3. Add signaling point codes 11 and 2111 to the LAC to SPC mapping info
whose mapping entry index is 3.
ZEEF:MEI=3:A:SPC=D'11&D'2111;
4. Modify location area code from 2 to 3.
ZEEF:LAC=2:M:NEWLAC=3;

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-08-08 11:11:32

LAC TO SPC MAPPING INFO MODIFIED

MAPPING ENTRY INDEX ............................ (MEI).... 1


LOCATION AREA CODE ............................. (LAC).... 2
SIGNALING POINT CODES (H/D): FFFFFF/16777215 FFFFFE/16777214
FFFFFD/16777213 FFFFFC/16777212
FFFFFB/16777211 FFFFFA/16777210

COMMAND EXECUTED

The execution printout of command example 2 is:

BSC BSC-LAB 2004-08-08 11:11:32

LAC TO SPC MAPPING INFO MODIFIED

MAPPING ENTRY INDEX ............................ (MEI).... 1


LOCATION AREA CODE ............................. (LAC).... 2
SIGNALING POINT CODES (H/D): FFFFFF/16777215 FFFFFD/16777213
FFFFFC/16777212 FFFFFB/16777211
FFFFFA/16777210

COMMAND EXECUTED

The execution printout of command example 4 is:

BSC BSC-LAB 2004-08-08 11:11:32

DN9813184 # Nokia Corporation 135 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

LAC TO SPC MAPPING INFO MODIFIED

MAPPING ENTRY INDEX ............................ (MEI).... 1


LOCATION AREA CODE ............................. (LAC).... 3
SIGNALING POINT CODES (H/D): FFFFFF/16777215 FFFFFD/16777213
FFFFFC/16777212 FFFFFB/16777211
FFFFFA/16777210

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error For more information, see Radio Network Administration.


messages

In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.

136 (138) # Nokia Corporation DN9813184


Issue 19-1 en
EES OUTPUT LAC TO SPC MAPPING INFO <option>

EES OUTPUT LAC TO SPC MAPPING INFO


<option>
Function With the EES command you output the LAC to SPC mapping info in the
BSDATA. The command is optional.

Parameters mapping entry index, location area code;

Syntax

EES: [[ MEI = <mapping entry index> ... |


LAC = <location area code> ... ] | <all> def ] ; <option>

Parameter mapping entry index


explanations
MEI = decimal number

With this parameter you define the mapping entry index which is an indication for
a mapping relation between the location area code and the signaling point code in
the LAC to SPC mapping info.

The values range from 1 to 64. You can give multiple mapping entry indexes by
using the characters & and &&. The default value is 'all'.

If you give this parameter, you cannot give the parameter LAC.

location area code

LAC = decimal number

With this parameter you define the location area code which will be mapped with
a signaling point code.

The values range from 1 to 65533. You can give multiple location area codes by
using the characters & and &&. The default value is 'all'.

If you give this parameter, you cannot give the parameter MEI.

DN9813184 # Nokia Corporation 137 (138)


Issue 19-1 en
EE - Base Station Controller Parameter Handling in BSC

Examples 1. Output the LAC to SPC mapping info whose location area codes are 999
and 1000.

ZEES:LAC=999&1000;
2. Output the LAC to SPC mapping info whose mapping entry index is 2.
ZEES:MEI=2;
3. Output all LAC to SPC mapping info.
ZEES;

Execution printouts The execution printout of command example 1 is:

BSC BSC-LAB 2004-09-09 11:11:32

LAC TO SPC MAPPING INFO DATA

MAPPING ENTRY INDEX ............................ (MEI).... 1


LOCATION AREA CODE ............................. (LAC).... 999
SIGNALING POINT CODES (H/D): FFFFFF/16777215 FFFFFE/16777214
FFFFFD/16777213 FFFFFC/16777212
FFFFFB/16777211 FFFFFA/16777210

MAPPING ENTRY INDEX ............................ (MEI).... 2


LOCATION AREA CODE ............................. (LAC).... 1000
SIGNALING POINT CODES (H/D): 0001FF/00000511 0010FF/00004351
0100FF/00065791 1000FF/01048831

COMMAND EXECUTED

Semantic error If an error occurs, the general semantic error messages of the MML commands
messages are output. For more information, see General Notice Messages of MML Session.

Execution error For more information, see Radio Network Administration.


messages

In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.

138 (138) # Nokia Corporation DN9813184


Issue 19-1 en

You might also like