Professional Documents
Culture Documents
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.
Contents
Contents 3
List of tables 5
List of figures 6
Summary of changes 7
List of tables
List of figures
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
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
Editorial changes.
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
.
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
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
With this parameter you define the maximum number of preferred cell identifiers
that the BSC sends to the MSC in the handover required message.
With this parameter you define the macrocell 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 5 dBm, the
division of cells into macrocells and microcells is not in use.
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.
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.
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.
MS distance behaviour
With this parameter you define the executions allowed after the timing advance
has exceeded the threshold.
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.
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.
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:
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:
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:
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:
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.
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.
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.
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.
With this parameter you define the BSC ISDN call number. The values range
from 0000 to 999999999999999 (from four to 15 digits).
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.
Note
If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.
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.
Note
If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.
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).
Note
If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.
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:
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:
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:
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.
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.
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.
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.
Note
If a cell level parameter has some other value than N, it replaces the
corresponding BSC-level parameter.
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:
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:
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.
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.
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.
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.
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.
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.
With this parameter you define how the GPRS territory is seen when calculating
FR resources.
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:
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:
With this parameter you define the measurement reporting period for the MSs in
the RR Packet Idle mode. The values are:
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.
With this parameter you define the measurement reporting period for the MSs in
the RR Packet Transfer mode. The values are:
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.
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.
With this parameter you define the penalty time for a neighbor cell after a failed
NCCR to that cell.
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:
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.
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;
Additional When the system has created a BSC object, the general base station controller
information parameters have the following default values:
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).
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.
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:
In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.
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
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 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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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 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.
With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.
The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.
With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.
The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.
With this parameter you define the length of the measurement period. The alarms
are printed out only at the end of the measurement period.
The values range from 5 to 1440 minutes (=24 hours). To deactivate supervision,
set the measurement period to zero.
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.
With this parameter you define the maximum time in percent that a TCH may be
on high interference levels during a measurement period.
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.
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.
With this parameter you define the time of day when the BTS supervision starts.
The starting moment is given in hours and minutes.
The starting moment for BTS supervision must be earlier than the ending
moment.
With this parameter you define the time of day when the BTS supervision ends.
The ending moment is given in hours and minutes.
The ending moment for BTS supervision must be later than the starting moment.
With this parameter you set the timer value which must elapse between two
subsequent territory updates.
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:
COMMAND EXECUTED
Semantic error
messages
The ending moment cannot be earlier than or the same as the starting moment.
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.
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
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.
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.
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.
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.
With this parameter you define the alarm limit for available full rate traffic
channels. The parameter is used by radio network recovery.
With this parameter you define the alarm limit for available half rate traffic
channels. The parameter is used by radio network recovery.
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.
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:
disable external DR
With this parameter you disable or enable the external directed retry handovers.
The parameter may receive the following values:
RX level balance
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.
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.
With this parameter you define how many successive remote transcoder failures
the BSC may receive before it releases the call.
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:
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.
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.
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:
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.
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.
With this parameter you can indicate whether the pre-emption is applied or not in
a case of handover. The values are:
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.
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.
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.
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.
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.
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.
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.
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.
With this parameter you define the minimum acceptable carrier/noise ratio for
half rate speech connections.
With this parameter you define the minimum acceptable carrier/noise ratio for
circuit switched data connections of 14.4 kbit/s.
With this parameter you define the minimum acceptable carrier/noise ratio for full
rate AMR speech connections.
With this parameter you define the minimum acceptable carrier/noise ratio for
half rate AMR speech connections.
With this parameter you define whether TCH access is based on downlink RX
level.
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.
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
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.
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:
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.
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
UBL1 = <PFC unack BLER limit for SDU error ratio 1> |
ABL1 = <PFC ack BLER limit for transfer delay 1> |) ... ;
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.
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.
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.
UL priority 1 SSS
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.
UL priority 2 SSS
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.
UL priority 3 SSS
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.
UL priority 4 SSS
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.
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.
Note
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.
Note
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.
Note
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.
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.
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.
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.
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.
The values range from 0 to 250. The unit is parts per thousand.
Note
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.
Note
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:
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.
Syntax
EET: [ PR = <priority level> ... ,
ST = <subscriber type> ] ... ; <option>
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.
ZEET:PR=2&3,ST=1;
2. Attach priority levels from 1 to 6 to subscriber type 2.
ZEET:PR=1&&6,ST=2;
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.
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;
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 parameter value must be equal to or greater than soft blocking C/I FR.
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.
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.
With this parameter you define the target C/I value for half rate speech
connections.
The parameter value must be equal to or greater than the soft blocking C/I HR.
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.
The parameter value must be equal to or smaller than the C/I target HR.
With this parameter you define the target C/I value for circuit switched data
connections of 14.4 kbit/s.
The parameter value must be equal to or greater than the soft blocking C/I 14.4.
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.
With this parameter you define the target C/I value for full rate AMR speech
connections.
The parameter value must be equal to or greater than the soft blocking C/I AMR
FR.
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.
The parameter value must be equal to or smaller than the C/I target AMR FR.
With this parameter you define the target C/I value for half rate AMR speech
connections.
The parameter value must be equal to or greater than the soft blocking C/I AMR
HR.
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.
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.
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.
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.
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.
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.
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:
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.
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.
ZEEH:CIF=9,SCIO=3;
Additional When the system has created a BSC object, base station controller parameters
information have the following default values:
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.
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.
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.
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.
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.
In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.
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>
|
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> ) :
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
With this parameter you define the criteria used to the (E)GPRS inactivity.
With this parameter you define the number of TBF allocation attempts required
per hour for (E)GPRS inactivity alarm.
With this parameter you define the length of the supervision period for (E)GPRS
inactivity alarm in minutes.
With this parameter you define the maximum time accepted for a Packet Flow
Timer (PFT) during a DTM allocation.
Note
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.
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;
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.
Syntax EER;
ZEER;
Additional Before the command is executed, the program asks for confirmation:
information
The ways that the state of background data may change in the preparation for
downloading are:
COMMAND EXECUTED
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.
Parameters operation;
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.
ZEEG;
Additional The different alternatives how the state of the background data may change while
information controlling the activation of the background data are:
Changing the background data is denied during the activation and also if the
activation is interrupted but not cancelled.
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?
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.
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:
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.
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.
Activation method
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.
connection type
With this parameter you define which type of connection is used between BSC
and NetAct for file transfer. The parameter is obligatory.
OK cases to feedback
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.
progress info
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).
compress threshold
With this parameter you define the feedback file size in kilobytes above which
compression is used when the file is sent.
remote directory
With this parameter you define the directory path in NetAct for plan and feedback
files. The remote directory's last character must be ' / '.
With this parameter you define short timer interval for file transfer connection
check in ftp/ftam connection.
With this parameter you define long timer interval for file transfer connection
check in ftp/ftam connection.
With this parameter you define short timer count for file transfer connection
check in ftp/ftam connection.
With this parameter you define long timer count for file transfer connection check
in ftp/ftam connection.
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.
port number
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.
With this parameter you define the FTAM application entity name. Ftam
application entity name is possible to give if connection type is FTAM.
user name
With this parameter you give the username of the FTP connection.
user ID
With this parameter you give the user ID of the FTAM connection.
password
With this parameter you give password of the FTP or FTAM server where to read
plan file and where to sent the feedback files.
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.
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.
Parameters BCF identification, BTS identification, SEG identification, YES TRXs to output;
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
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
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
With this parameter you define if TRX information is printed out or not. The
default value is Y.
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:;
BCF-0001 ACTIVATED WO
BTS-0001 ACTIVATED WO
TRX-001 ACTIVATED BL_USR
TRX-002 ACTIVATED WO
BCF-0004 PLANNED WO
BTS-0004 PLANNED BL_USR
TRX-001 PLANNED BL_USR
TRX-002 PLANNED BL_USR
COMMAND EXECUTED
BCF-0001 ACTIVATED WO
BTS-0001 ACTIVATED WO
BCF-0004 PLANNED WO
BTS-0004 PLANNED BL_USR
COMMAND EXECUTED
BTS-0001 ACTIVATED WO
TRX-001 ACTIVATED WO
TRX-002 ACTIVATED BL_USR
TRX-003 ACTIVATED WO
BTS-0004 PLANNED WO
TRX-001 PLANNED BL_USR
TRX-002 PLANNED BL_USR
TRX-003 PLANNED BL_USR
COMMAND EXECUTED
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
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
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.
ZEEO;
2. Output radio network supervision parameters of the BSC.
ZEEO:SUP;
3. Output all BSC parameters.
ZEEO:ALL;
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.
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 ] :
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.
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.
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.
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
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
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:
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.
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;).
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;
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.
COMMAND EXECUTED
COMMAND EXECUTED
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.
Syntax
EEL: [ <operational state> ] :
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
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
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
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.
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).
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
COMMAND EXECUTED
COMMAND EXECUTED
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.
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.
In addition, the general execution error messages of the MML commands are
used. For more information, see General Error Messages of System.
Syntax
EEP: [ [ BCF = <BCF identification> ... |
BTS = <BTS identification> ... |
NAME = <BTS name> ... ] | <all> def ] ;
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
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
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.
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;
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.
Parameters mapping entry index, location area code : signaling point code;
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.
With this parameter you define the location area code which will be mapped with
a signaling point code.
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;
COMMAND EXECUTED
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.
In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.
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.
If you give this parameter, you cannot give the parameter LAC.
With this parameter you define the location area code which will be mapped with
a signaling point code.
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;
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.
In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.
Parameters mapping entry index, location are code: identification of function: signaling point
code, new location area code;
<identification of function> :
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.
If you give this parameter, you cannot give the parameter LAC.
With this parameter you define the location area code which will be mapped with
a signaling point code.
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.
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.
With this parameter you define the new location area code.
The parameter is allowed only when you modify a location area code, and in that
case the parameter is obligatory.
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;
COMMAND EXECUTED
COMMAND EXECUTED
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.
In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.
Syntax
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.
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.
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;
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.
In addition, the general execution error messages of MML commands are used.
For more information, see General Error Messages of System.