B12 TelecomParam BTP Ed1.5

vendredi 26 juillet 2013
BSS Telecom Parameters Catalogue:
Release B12
Edition : 11 Released BSS Telecom parameters 3BK 11203 0250 DSZZA

BSC parameters
Logical A_ECNO_HO B11 Yes B12 Yes
name TRX nb No
HMI A_ECNO_HO Sub-syste BSC Cell Type Yes
name Instance cell RMS No
Definition Window size for Ec/No level averages for 2G to 3G handover
Category Site (CAE) OMC-R access Changeable Type Number Unit Samfr
Rec ref. None Domai 2G-3G Min value 1 Coded Min 1
n Max value 31 Coded Max 31
Spec ref. Radio measurements data processing Coded Max 31
Def value 8 Coded Def 8
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
CT: Depends on Cell Type and BTS Type
Edition : 11 Released BSS Telecom parameters 3BK 11203 0250 DSZZA Page 2
Logical A_LEV_HO B11 Yes B12 Yes
name TRX nb No
HMI A_LEV_HO Sub-syste BSC Cell Type Yes
Definition Window size for level averages for handover.
Rec ref. None Domai GSM Min value 1 Coded Min 1
Coding rules --
Mandatory rules A_LEV_HO + W_LEV_HO < 32
Recommended A_LEV_HO = 2 x A_LEV_PC. A_PBGT_HO = 2 x A_LEV_HO

rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Logical A_LEV_MCHO B11 Yes B12 Yes
name TRX nb No
HMI A_LEV_MCHO Sub-syste BSC Cell Type Yes
Definition Window size for level averages for microcell handover.
Coding rules --
Mandatory rules A_LEV_MCHO + W_LEV_MCHO < 16
Recommended --
rules
External --
comment
Internal comment Meaningful only for cells where: Cell_type = Microcell
Logical A_LEV_PC B11 Yes B12 Yes
name TRX nb No
HMI A_LEV_PC Sub-syste BSC Cell Type No
Definition Window size for level averages for power control. For uplink, it is applicable to both VAMOS and non-VAMOS mode; for downlink, to non-VAMOS mode only.
Coding rules --
Mandatory rules A_LEV_PC + W_LEV_PC < 32
Recommended A_LEV_HO = 2 x A_LEV_PC

rules
External --
comment
Internal comment --
Logical A_LEV_PC_VAMOS B11 No B12 Yes
name TRX nb No
HMI A_LEV_PC_VAMOS Sub-syste BSC Cell Type No
Definition Window size for level averages for power control in VAMOS mode (only for downlink).
Coding rules --
Mandatory rules - A_LEV_PC_VAMOS + W_LEV_PC_VAMOS <= 32
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied on new VAMOS calls (after modification).
Internal comment --
Logical A_LEV_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI A_LEV_VAMOS_PAIRING Sub-syste BSC Cell Type No
Definition Window size for level averages for VAMOS pairing (only for downlink measurements).
Coding rules --
Mandatory rules - A_LEV_VAMOS_PAIRING + W_LEV_VAMOS_PAIRING < 32
Recommended --
rules
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Logical A_LEV_VAMOS_UNPAIRING B11 No B12 Yes
name TRX nb No
HMI A_LEV_VAMOS_UNPAIRING Sub-syste BSC Cell Type No
Definition Window size for level averages for VAMOS unpairing (only for downlink measurements).
Coding rules --
Mandatory rules - A_LEV_VAMOS_UNPAIRING + W_LEV_VAMOS_UNPAIRING < 32
Recommended --
rules
Internal comment --
Logical A_PBGT_DR B11 Yes B12 Yes
name TRX nb No
HMI A_PBGT_DR Sub-syste BSC Cell Type No
Definition Window size for neighbour cell level averages for forced directed retry.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical A_PBGT_HO B11 Yes B12 Yes
name TRX nb No
HMI A_PBGT_HO Sub-syste BSC Cell Type Yes
Definition Window size for averaging neighbour cell levels and averaging current cell levels for power budget calculation.
Coding rules --
Mandatory rules A_PBGT_HO + W_PBGT_HO < 32
Recommended A_PBGT_HO = 2 x A_LEV_HO

rules
External should be set to 6 in suburban area, to 8 in urban area and to 12 in rural area
comment
Logical A_QUAL_CA_FR_HR B11 Yes B12 Yes
name TRX nb No
HMI A_QUAL_CA_FR_HR Sub-syste BSC Cell Type No
Definition Quality averaging window size for AMR-NB FR-to-HR channel adaptation (handover Cause 27).
Coding rules step size = 1 Samfr
Mandatory rules A_QUAL_CA_FR_HR >= A_QUAL_CA_HR_FR
Recommended --
rules
External --
comment
Internal comment --
Logical A_QUAL_CA_HR_FR B11 Yes B12 Yes
name TRX nb No
HMI A_QUAL_CA_HR_FR Sub-syste BSC Cell Type No
Definition Quality averaging window size for AMR-NB HR-to-FR channel adaptation.
Mandatory rules A_QUAL_CA_FR_HR >= A_QUAL_CA_HR_FR
Recommended --
rules
External --
comment
Internal comment --
Logical A_QUAL_HO B11 Yes B12 Yes
name TRX nb No
HMI A_QUAL_HO Sub-syste BSC Cell Type Yes
Definition Window size for quality averages for handover.
Coding rules --
Mandatory rules A_QUAL_HO + W_QUAL_HO < 32
Recommended A_QUAL_HO = 2 x A_QUAL_PC

rules
External --
comment
Logical A_QUAL_PC B11 Yes B12 Yes
name TRX nb No
HMI A_QUAL_PC Sub-syste BSC Cell Type No
Definition Window size for quality averages for power control. For uplink, it is applicable to both VAMOS and non-VAMOS mode; for downlink, to non-VAMOS mode only.
Coding rules --
Mandatory rules A_QUAL_PC + W_QUAL_PC < 32
Recommended A_QUAL_HO = 2 x A_QUAL_PC

rules
External --
comment
Internal comment --
Logical A_QUAL_PC_VAMOS B11 No B12 Yes
name TRX nb No
HMI A_QUAL_PC_VAMOS Sub-syste BSC Cell Type No
Definition Window size for quality averages for power control in VAMOS mode (only for downlink).
Coding rules --
Mandatory rules - A_QUAL_PC_VAMOS + W_QUAL_PC_VAMOS <= 32
Recommended --
rules
Internal comment --
Logical A_QUAL_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI A_QUAL_VAMOS_PAIRING Sub-syste BSC Cell Type No
Definition Window size for quality averages for VAMOS pairing (only for downlink measurements).
Coding rules --
Mandatory rules - A_QUAL_VAMOS_PAIRING + W_QUAL_VAMOS_PAIRING < 32
Recommended --
rules
Internal comment --
Logical A_QUAL_VAMOS_UNPAIRING B11 No B12 Yes
name TRX nb No
HMI A_QUAL_VAMOS_UNPAIRING Sub-syste BSC Cell Type No
Definition Window size for quality averages for VAMOS unpairing (only for downlink measurements).
Coding rules --
Mandatory rules - A_QUAL_VAMOS_UNPAIRING + W_QUAL_VAMOS_UNPAIRING < 32
Recommended --
rules
Internal comment --
Logical A_RANGE_HO B11 Yes B12 Yes
name TRX nb No
HMI A_RANGE_HO Sub-syste BSC Cell Type No
Definition Window size for distance averages.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical A_TRAFFIC_LOAD B11 Yes B12 Yes
name TRX nb Yes
HMI A_TRAFFIC_LOAD Sub-syste BSC Cell Type No
Definition Window size for load averages.
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Spec ref. Resource Allocation and Management Coded Max 16
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Logical ABIS_BANDWIDTH B11 Yes B12 Yes
name TRX nb No
HMI ABIS_BANDWIDTH Sub-syste BSC Cell Type No
name Instance A-bis link RMS No
Definition Total Abis bandwidth available (for the Abis BTS group if Abis-Transport-Mode = "IP Ethernet", or for one E1 link if Abis-Transport-Mode = "IP framed" or "IP unframed").
Category Site (CAE) OMC-R access Changeable Type Number Unit kbit/s
Rec ref. None Domai IP Min value 1 Coded Min 1
Def value None Coded Def 0
Coding rules Step size = 1.
The coded default value is for implementation purposes only; this dummy value indicates that the operator does not provide any Abis bandwidth yet.
Mandatory rules The Abis bandwidth can be defined / negotiated with a transport network operator through SLA (Service Level Agreement). Such a SLA should define the needed
bandwidth per QoS level (i.e. P0/CS, P1/SIG, P2/GBR, P3/BE). Thus, the ABIS_BANDWIDTH parameter shall be positioned to the minimum value between the SLA
values (e.g. CIR (Committed Information Rate) and/or EIR (Excess Information Rate) values) and other inputs or calculation results. The value of the
TCH_TS_ACTIVITY_FACTOR parameter may also be constrained by SLA.
Recommended In case of variable Abis bandwidth (e.g. micro-wave), the ABIS_BANDWIDTH parameter shall be positioned to the minimum guaranteed bandwidth.
rules
External If Abis-Transport-Mode = "IP framed", the ABIS_BANDWIDTH parameter is CAE/Virtual changeable" and shall be computed according to the Usable_TSs parameter
comment value (so no input is needed from the operator in this case).
In the case of a BTS linked to the BSC through N E1 links, then the total bandwidth is N * ABIS_BANDWIDTH value.
If Abis-Transport-Mode = "IP Ethernet", the ABIS_BANDWIDTH parameter shall be mandatorily set by the operator (the default value (=None) is indeed not relevant
because out of the range of possible values). To be noted that the Abis should be the bottleneck of the transmission bandwidth in a well-engineered BSS IP transport
network (the available transmission bandwidth on the Abis last mile is considered to be the bottleneck with respect to the radio bandwidth between RRM and
RLC/MAC).
Bandwidth used by OML is neglected.
Internal comment --
Logical AC_0 B11 Yes B12 Yes
name TRX nb No
HMI AC 0 Sub-syste BSC Cell Type No
Definition Indicates if Access Class 0 is barred.
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. GSM TS 04.08 Domai GSM Min value 0 Coded Min 0
Spec ref. Overload control Coded Max 1
Coding rules 0: not barred, 1: barred
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical AC_PRIORITY_LIST(priority=1) B11 Yes B12 Yes
name TRX nb No
HMI High Priority Access Class Ordering P1 Sub-syste BSC Cell Type No
name Instance BSC RMS No
Definition List of access classes 11..15 and EC (=10) in their priority order.
Coding rules Priority 1 is the highest priority, Priority 6 is the lowest priority, 10 (EC) is coded as 5, 11 (access class 11) is coded as 0, 12 (access class 12) is coded as 1, 13
(access class 13) is coded as 2, 14 (access class 14) is coded as 3, 15 (access class 15) is coded as 4.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules Priority 1 is the highest priority, Priority 6 is the lowest priority
10 (EC) is coded as 5, 11 (access class 11) is coded as 0, 12 (access class 12) is coded as 1, 13 (access class 13) is coded as 2, 14 (access class 14) is coded as
3, 15 (access class 15) is coded as 4.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ADD_HR_IN_TFO_LIST B11 Yes B12 Yes
name TRX nb No
HMI ADD_HR_IN_TFO_LIST Sub-syste BSC Cell Type No
Definition Enables/disables the addition of the legacy HR codec type in the list of supported codec type provided to the TFO remote partner for a given AMR-NB call, when that call
is currently established in Half Rate for cell load reason and when TFO is possible for that call (TFO on AMR-NB supported by the TC and configured in the cell).
Coding rules 0: HR SV1 is never provided in the list of supported codec types.
1: HR SV1 may be provided (if supported by the MS and configured in the cell) in the list of supported codec types, in addition to HR SV3.
Mandatory rules --
Recommended --
rules
External - Significant if EN_TFO_AMR_NB is enabled
comment - TFO on AMR-NB function is available on BSC Evolution only.
- Parameter change: No impact on the telecom service, on going calls are not disrupted. Change applied only on new AMR-NB call allocated in Half Rate after
modification
Internal comment --
Logical ADDITIONAL_RESELECT_PARAM B11 Yes B12 Yes
name TRX nb No
HMI ADDITIONAL_RESELECT_PARAM Sub-syste BSC Cell Type No
Definition Indicates if C2 cell selection parameters are present in SYS_INFO_7&8 or SYS_INFO_4.
Category Site (CAE) OMC-R access Displayed Type Flag Unit None
Spec ref. System information management Coded Max 1
Coding rules 1bit; 0= the SI 4 rest octets, if present, are used to derive the value of PI and possibly C2 parameters.
1= the value of PI and possibly C2 parameters in a SYS INFO TYPE or message 8 are used
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment always set to 0 as SYS_INFO 7&8 are not used
Logical ADDR_MON B11 Yes B12 Yes
name TRX nb No
HMI ADDR_MON Sub-syste BSC Cell Type No
Definition Time it takes to ADDR_TR to be reached to report an alarm. On timeout, the address error counter is reset.
Category Network (CDE) OMC-R access None (DLS) Type Timer Unit sec
n Max value 6553.5 Coded Max 65535
Spec ref. LAPD management Coded Max 65535
Coding rules step size = 0.1sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ADDR_TR B11 Yes B12 Yes
name TRX nb No
HMI ADDR_TR Sub-syste BSC Cell Type No
Definition Address error threshold for alarm detection.
Category Network (CDE) OMC-R access None (DLS) Type Threshold Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Internal BSS alarm, not OMC-R visualisation
Logical AG_PREMPT_PCH B11 Yes B12 Yes
name TRX nb No
HMI AG_PREMPT_PCH Sub-syste BSC Cell Type No
Definition Flag to enable pre-emption of Paging sub-channels for Access Grant messages when there is one remaining free AGCH block.
Spec ref. Paging and Access Grant control Coded Max 1
Coding rules 0 = disabled, 1 = enabled
Mandatory rules Lets define the free AGCH blocks as the number of blocks remaining for the AGCH messages when the BCCH extended block and NCH blocks have been excluded.
- If there is no free AGCH block then the flag is not used (pre-emption mandatory, default
value 0 is not used by BTS )
- If there is only one free AGCH block then AG_PREMPT_PCH =1 or 0 (pre-emption allowed)
- If there is more than one free AGCH then AG_PREMPT_PCH = 0 (pre-emption forbidden).
Recommended --
rules
External --
comment
Internal comment When EN_VGCS is disabled :
Free AGCH = BS_AG_BLKS_RES - BCCH_EXT
When EN_VGCS is enabled:

Free AGCH = BS_AG_BLKS_RES - NUMBER_NCH_BLOCKS - BCCH_EXT
Logical ALLOC_ANYWAY B11 Yes B12 Yes
name TRX nb No
HMI ALLOC_ANYWAY Sub-syste BSC Cell Type No
Definition Controls whether a queued request can be allocated on free resource at expiry of its queuing timer independently of the threshold NUM_TCH_EGNCY_HO.
Coding rules --
Mandatory rules --
Recommended --
rules
External only relevant when NUM_TCH_EGNCY_HO > 0
comment
Internal comment --
Logical ALPHA (BSC) B11 Yes B12 Yes
name TRX nb No
HMI ALPHA Sub-syste BSC Cell Type No
Definition Alpha power control parameter.
Rec ref. GSM TS 04.08 Domai GPRS Min value 0 Coded Min 0
Coding rules Possible values are : 0.0 to 1.0 with step of 0.1respectively binary coded : 0000, 0001, 0010 1010
Mandatory rules Equal to ALPHA (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical AMR_FR_HYST B11 Yes B12 Yes
name TRX nb No
HMI AMR_FR_HYST Sub-syste BSC Cell Type No
Definition Hysteresis for AMR-NB FR codec mode adaptation.
Category Site (CAE) OMC-R access Changeable Type Number Unit dB
Spec ref. Codec Adaptation Coded Max 15
Coding rules step size=0.5 dB; 0 = 0.0 dB, 1 = 0.5 dB, , 15 = 7.5 dB
Mandatory rules --
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rule is highly recommended : AMR_FR_HYST + AMR_FR_THR_i <= 16dB (with i = 13).
rules The recommended value for the preferred AMR FR configurations given in 3GPP TS 28.062 and selected via the PREF_CONFIG_FR_AMR_NB parameter is:
AMR configuration 1, 8, 9, 10, 12 and 14: 2 dB.
External Default value corresponds to the optimal default codec subset (12.2kbit/s, 7.95kbit/s, 5.9kbit/s).
comment Significant only if EN_AMR_FR is set to TRUE.
Internal comment PREF_CONFIG_FR_AMR_NB parameter is defined in the BOP
Logical AMR_FR_SUBSET B11 Yes B12 Yes
name TRX nb No
HMI AMR_FR_SUBSET Sub-syste BSC Cell Type No
name Instance BSS RMS No
Definition Bitmap (8 bits) defining the codec subset that shall be used for AMR-NB FR calls (up to 4 codecs selected by the operator or codecs associated to the selected preferred
AMR configuration).
Rec ref. 3GPP TS 26.071 Domai GSM Min value 1 Coded Min 1
Coding rules bit 8 (most significant)=1: 12,2 kbit/s is part of the subset;
bit 7=1: 10,2 kbit/s is part of the subset;
bit 1 (least significant)=1: 4,75 kbit/s is part of the subset.
AMR configuration 0 is composed of the codec: 4.75 Kbit/sec

AMR configuration 1 is composed of the codec: 12.20, 7.40, 5.90 and 4.75 Kbit/sec
AMR configuration 8 is composed of the codec: 5.90 and 4.75 Kbit/sec
AMR configuration 9 is composed of the codec: 6.70, 5.90 and 4.75 Kbit/sec
(The list of all the 16 standardized AMR-NB FR configurations are given in 3GPP TS 28.062)
Mandatory rules - In one subset a maximum of 4 codec modes can be chosen (a maximum of 4 bits can be set to 1).
- EN_AUP_OVER_IP can be enabled only if:
AMR_FR_SUBSET = {1, 4, 5, 8, 13, 16, 29, 32, 64, 77, 128, 149, 165} when EN_AMR_FR is enabled in at least one cell of the BSS
And
Recommended - The AMR configuration 1 is especially recommended for calls between GERAN and UMTS, because it leads in all call cases to TFO/TrFO compatible connections with
m
rules optimal voice quality.
- The AMR configuration 1 is especially recommended when EN_AUP_OVER_IP is enabled template
External - Default value corresponds to an optimal codec subset:12.2kbit/s, 7.95kbit/s, 5.9kbit/s
comment - The AMR-NB FR configurations 11, 13 and 15 (allowing the optimization mode) are not supported by the Alcatel-Lucent BSS.
Internal comment - The translation from the AMR preferred configuration number to codecs subset is done by the OMC (usage of standardized AMR NB configuration enhanced TFO
interoperability, but TFO doesnt require their usage, and they can be used without TFO enabled).
- The codec 12.20 Kbit/sec of config 1 is applicable to FR only
- The selection of the preferred AMR configuration is done via PREF_CONFIG_FR_AMR_NB (defined in the BOP).
Logical AMR_FR_THR_1 B11 Yes B12 Yes

name TRX nb No
HMI AMR_FR_THR_1 Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Threshold for AMR-NB FR codec mode adaptation between lowest codec mode and second lowest codec mode.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit dB
Def value 6.5 Coded Def 13
Mandatory rules AMR_FR_THR_1 <= AMR_FR_THR_2
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rule is highly recommended : AMR_FR_HYST + AMR_FR_THR_1 <= 16dB.
rules The recommended value for the preferred AMR FR configurations given in 3GPP TS 28.062 and selected via the PREF_CONFIG_FR_AMR_NB parameter is:
AMR configuration 1, 8, 9, 10, 12 and 14: 4 dB.
External Default value corresponds to the optimal default codec subset (12.2kbit/s, 7.95kbit/s, 5.9kbit/s). AMR_FR_THR_1 is not used if less than 2 codecs are in the AMR FR
comment subset.
Significant only if EN_AMR_FR is set to TRUE.
Internal comment AMR_HR_SUBSET = {1, 4, 5, 8, 13, 21, 29} when EN_AMR_HR is enabled in at least one cell of the BSS. --
name TRX nb No
BSC Cell Type No
name Instance
cell RMS No
Definition Threshold for AMR-NB FR codec mode adaptation between second lowest codec mode and third lowest codec mode.
Mandatory rules AMR_FR_THR_3 >= AMR_FR_THR_2 >= AMR_FR_THR_1
rules The recommended values for the preferred AMR FR configurations given in 3GPP TS 28.062 and selected via the PREF_CONFIG_FR_AMR_NB parameter are:
AMR configuration 1 and 14: 6.5 dB;
AMR configuration 9, 10 and 12: 5.5 dB.
comment subset.
Internal comment --
name TRX nb No
BSC Cell Type No
name Instance
cell RMS No
Definition Threshold for AMR-NB FR codec mode adaptation between third lowest codec mode and fourth lowest codec mode.
Mandatory rules AMR_FR_THR_3 >= AMR_FR_THR_2
rules The recommended values for the preferred AMR FR configurations given in 3GPP TS 28.062 and selected via the PREF_CONFIG_FR_AMR_NB parameter are:
AMR configuration 1 and 14: 11.5 dB;
AMR configuration 10: 6.5 dB;
AMR configuration 12: 8 dB.
comment subset.
Internal comment --
Logical AMR_HR_HYST B11 Yes B12 Yes
name TRX nb No
HMI AMR_HR_HYST Sub-syste BSC Cell Type No
Definition Hysteresis for AMR-NB HR codec mode adaptation.
Mandatory rules --
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rule is highly recommended : AMR_HR_HYST + AMR_HR_THR_i <= 16dB (with i = 13).
rules The recommended value for the preferred AMR HR configurations given in 3GPP TS 28.062 and selected via the PREF_CONFIG_HR_AMR_NB parameter is:
AMR configuration 1, 8, 9, 10: 2 dB.
External Default value corresponds to the optimal default codec subset (7.4kbit/s, 5.9kbit/s, 5.15kbit/s).
comment Significant only if EN_AMR_HR is set to TRUE.
Internal comment PREF_CONFIG_HR_AMR_NB parameter is defined in the BOP
Logical AMR_HR_SUBSET B11 Yes B12 Yes
name TRX nb No
HMI AMR_HR_SUBSET Sub-syste BSC Cell Type No
Definition Bitmap (6 bits) defining the codec subset that shall be used for AMR-NB HR calls (up to 4 codecs selected by the operator or codecs associated to the selected preferred
AMR configuration).
Coding rules Coded on 1 byte.
bit 8 (most significant) = 0
bit 7 = 0;
bit 6 =1: 7,95 kbit/s is part of the subset;
bit 1 (least significant)=1: 4,75 kbit/s is part of the subset;

AMR configuration 8 is composed of the codec: 5.90 and 4.75 Kbit/sec
(The list of all the 9 standardized AMR-NB HR configurations are given in 3GPP TS 28.062)
Mandatory rules - In one subset a maximum of 4 codec modes can be chosen (a maximum of 4 bits can be set to 1).
- The subset shall not contain only 7.4 kbit/s codec mode. As consequence, the AMR configuration 4 is forbidden too.
And
AMR_HR_SUBSET = {1, 4, 5, 8, 13, 21, 29} when EN_AMR_HR is enabled in at least one cell of the BSS.
Recommended - The AMR configuration 1 is especially recommended for calls between GERAN and UMTS, because it leads in all call cases to TFO/TrFO compatible connections with
rules optimal voice quality.
External - Default value corresponds to the optimal default codec subset (7.4kbit/s, 5.9kbit/s, 5.15kbit/s).
comment - The codec mode 7.95 kbit/s (and AMR configuration 5, as consequence) is not supported by the Alcatel-Lucent BSS. m
Internal comment - The translation from the AMR preferred configuration number to codecs subset is done by the OMC (usage of standardized AMR NB configuration enhanced TFO
template
interoperability, but TFO doesnt require their usage, and they can be used without TFO enabled). template
- The limitation about the codec 7.4Kbit/sec is a 3GPP limitation due to the synchronization between TC and BTS.
- The selection of the preferred AMR configuration is done via PREF_CONFIG_HR_AMR_NB (defined in the BOP).
Logical AMR_HR_THR_1 B11 Yes B12 Yes

name TRX nb No
HMI AMR_HR_THR_1 Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Threshold for AMR-NB HR codec mode adaptation between lowest codec mode and second lowest codec mode.
Mandatory rules AMR_HR_THR_1 <= AMR_HR_THR_2
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rule is highly recommended : AMR_HR_HYST + AMR_HR_THR_1 <= 16dB.
rules The recommended values for the preferred AMR HR configurations given in 3GPP TS 28.062 and selected via the PREF_CONFIG_HR_AMR_NB parameter are:
AMR configuration 1, 9 and 10: 10.5 dB;
External Default value corresponds to the optimal default codec subset (7.4kbit/s, 5.9kbit/s, 5.15kbit/s). AMR_HR_THR_1 is not used if less than 2 codecs are in the AMR HR
comment subset.
Significant only if EN_AMR_HR is set to TRUE.
Internal comment --
- The AMR configuration 1 is especially recommended when EN_AUP_OVER_IP is enabled
name TRX nb No
BSC Cell Type No
name Instance
cell RMS No
Definition Threshold for AMR-NB HR codec mode adaptation between second lowest codec mode and third lowest codec mode.
Mandatory rules AMR_HR_THR_3 >= AMR_HR_THR_2 >= AMR_HR_THR_1
AMR configuration 1, 9 and 10: 12 dB.
comment subset.
Internal comment --
name TRX nb No
BSC Cell Type No
name Instance
cell RMS No
Definition Threshold for AMR-NB HR codec mode adaptation between third lowest codec mode and fourth lowest codec mode.
Mandatory rules AMR_HR_THR_3 >= AMR_HR_THR_2
comment subset.
Internal comment --
Logical AMR_START_MODE_FR B11 Yes B12 Yes
name TRX nb No
HMI AMR_START_MODE_FR Sub-syste BSC Cell Type No
Definition Indicates the codec used at the beginning of a AMR-NB FR call, until codec mode adaptation is started by the BTS.
Category Site (CAE) OMC-R access Changeable Type Reference Unit None
Coding rules 0: implicit rule is used for initial codec mode; 1: lowest codec mode of the subset; 2: second lowest codec mode (used if the subset contains more than one codec
mode); 3: third lowest codec mode (used if the subset contains more than two codec modes); 4: highest codec mode (used if the subset contains four codec modes)
Mandatory rules --
Recommended --
rules
External When the TFO function is enabled in case of AMR narrow band codec (EN_TFO_AMR_NB) in the cell, the Alcatel-Lucent BSS always considers the implicit rule is
comment used for the initial codec mode.
Internal comment --
Logical AMR_START_MODE_HR B11 Yes B12 Yes
name TRX nb No
HMI AMR_START_MODE_HR Sub-syste BSC Cell Type No
Definition Indicates the codec used at the beginning of a AMR-NB HR call, until codec mode adaptation is started by the BTS.
Coding rules 0: implicit rule is used for initial codec mode; 1: lowest codec mode of the subset; 2: second lowest codec mode (used if the subset contains more than one codec
mode); 3: third lowest codec mode (used if the subset contains more than two codec modes); 4: highest codec mode (used if the subset contains four codec modes)
Mandatory rules If AMR_START_MODE_HR is explicit (I.e. not equal to 0), the chosen codec mode shall not correspond to 7.40 kbit/s.
Recommended Use codec mode 6.7 kbit/s as start mode for AMR-NB HR should be avoided.
rules
External When the TFO function is enabled in case of AMR narrow band codec (EN_TFO_AMR_NB) in the cell, the Alcatel-Lucent BSS always considers the implicit rule is
comment used for the initial codec mode.
Internal comment --
Logical AMR_WB_GMSK_HYST_1 B11 Yes B12 Yes
name TRX nb No
HMI AMR_WB_GMSK_HYST_1 Sub-syste BSC Cell Type No
Definition Hysteresis for AMR-WB GMSK codec mode adaptation, for transition between lowest codec mode and second lowest codec mode.
Mandatory rules AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1<=AMR_WB_GMSK_THR_2+AMR_WB_GMSK_HYST_2
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rules is highly recommended : AMR_WB_GMSK_HYST_1 + AMR_WB_GMSK_THR_1 <=
rules 16dB
External --
comment
Internal comment --
Logical AMR_WB_GMSK_HYST_2 B11 Yes B12 Yes
name TRX nb No
HMI AMR_WB_GMSK_HYST_2 Sub-syste BSC Cell Type No
Definition Hysteresis for AMR-WB GMSK codec mode adaptation, for transition between highest codec mode and second lowest codec mode
Mandatory rules AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1<=AMR_WB_GMSK_THR_2+AMR_WB_GMSK_HYST_2
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rules is highly recommended : AMR_WB_GMSK_HYST_2 + AMR_WB_GMSK_THR_2 <=
rules 16dB
External --
comment
Internal comment --
Logical AMR_WB_GMSK_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI AMR_WB_GMSK_THR_1 Sub-syste BSC Cell Type No
Definition Threshold for AMR-WB GMSK codec mode adaptation between lowest codec mode and second
lowest codec mode.
Mandatory rules - AMR_WB_GMSK_THR_1 < AMR_WB_GMSK_THR_2

- AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1
<= AMR_WB_GMSK_THR_2+AMR_WB_GMSK_HYST_2
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rule is highly recommended : AMR_WB_GMSK_HYST_1 + AMR_WB_GMSK_THR_1 <= 16dB
rules
External --
comment
Internal comment --
Logical AMR_WB_GMSK_THR_2 B11 Yes B12 Yes
name TRX nb No
HMI AMR_WB_GMSK_THR_2 Sub-syste BSC Cell Type No
Definition Threshold for AMR-WB GMSK codec mode adaptation between second lowest codec mode and highest codec mode
Mandatory rules - AMR_WB_GMSK_THR_1 < AMR_WB_GMSK_THR_2

- AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1
<= AMR_WB_GMSK_THR_2+AMR_WB_GMSK_HYST_2
Recommended As the BTS is not able to compute C/I values higher than 16 dB, following rule is highly recommended : AMR_WB_GMSK_HYST_2 + AMR_WB_GMSK_THR_2 <= 16dB
rules
External --
comment
Internal comment --
Logical ARFCN_3G(FDD) B11 Yes B12 Yes
name TRX nb No
HMI UARFCN Sub-syste
BSC Cell Type No
name Instance
3G cell RMS No
Definition Downlink FDD UTRAN Absolute Radio Frequency Channel Number (UARFCN) of an external 3G FDD cell.
Category Site (CAE) OMC-R access Set Create & Changeable Type Number Unit None
Rec ref. 3GPP TS 25.101 Domai 2G-3G Min value 0 Coded Min 0
Def value None Coded Def
Coding rules --
Mandatory rules - Only the following downlink FDD UARFCN ranges are standardized:
I) 10562-10838 and
II) 9662-9938 and
III) 1162-1513 and
IV) 1537-1738 and
V) 4357-4458 and
VI) 4387-4413 and
VII) 2237- 2563 and
VIII) 2937-3088 and
IX) 9237-9387
X) 3112-3388
XI) 3712-3787
XII) 3842- 3903
XIII) 4017-4043
XIV) 4117-4143
- For a given 2G cell, there shall be no more than 3 distinct ARFCN_3G (FDD) among all the neighbour 3G FDD cells target for handover (or both).
- For a given 2G cell, there shall be no more than 8 distinct ARFCN_3G (FDD) among all the neighbour 3G FDD cells target for reselection (or both).
- For a given 2G cell, the couple (ARFCN_3G (FDD), SCRAMBLING_CODE_3G_FDD) shall be unique among all the neighbour 3G FDD cells target for handover (or
both).
- FDD_ARFCN_LIST and ARFCN_3G (FDD) are exclusive: for a given BSS, we cannot have at the same time a valid FDD_ARFCN_LIST and, at least, one 2G cell where
EN_2G_TO_3G_CELL_RESELECTION is not disabled, and having, at least, one neighbour 3G FDD cell target for reselection (or both).
Recommended --
rules
External - Significant if RAT_3G is FDD
comment - The FDD UARFCNs are used on the Air interface.
- The FDD UARFCNs of the 3G neighbour cells configured for reselection (or both) are broadcast on BCCH.
Internal comment - A coded default value is not needed since the operator cannot create a 3G FDD cell without configuring its UARFCN (no dummy value needed). m
- If, for a serving 2G cell where EN_2G_TO_3G_CELL_RESELECTION is not disabled, two neighbour 3G cells are target for reselection and configured with the same
ARFCN_3G (FDD), then BSC broadcasts the ARFCN_3G only once. template
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Logical ARFCN_3G(TDD) B11 Yes B12 Yes
name TRX nb No
HMI UARFCN Sub-syste
BSC Cell Type No
name Instance
3G cell RMS No
Definition Downlink TDD UTRAN Absolute Radio Frequency Channel Number (UARFCN) of an external 3G TDD cell.
Coding rules --
Mandatory rules - Only the following downlink UARFCN ranges are standardized:
a) 9504-9596 and 10054-10121
b) 9254- 9546 and 9654-9946
c) 9554-9646
d) 12854-13096
e) 11504-11996
f) 9404-9596
- For a given 2G cell, there shall be no more than 8 distinct ARFCN_3G (TDD) among all the neighbour 3G TDD cells target for reselection.
- TDD_ARFCN_LIST and ARFCN_3G (TDD) are exclusive: for a given BSS, we cannot have at the same time a valid TDD_ARFCN_LIST and, at least, one 2G cell where
EN_2G_TO_3GTDD_CELL_RESELECTION is not disabled, and having, at least, one neighbour 3G TDD cell target for reselection.
Recommended --
rules
External - Significant if RAT_3G is TDD
comment - The TDD UARFCNs are used on the Air interface.
- The TDD UARFCns of the 3G neighbour cells (configured for reselection) are broadcast on BCCH
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Internal comment - The standardized values are those of 1.28 Mcps TDD option.
- A coded default value is not needed since the operator cannot create a 3G TDD cell without configuring its UARFCN (no dummy value needed).
- If, for a serving 2G cell where EN_2G_TO_3GTDD_CELL_RESELECTION is not disabled, two neighbour 3G cells are target for reslection and configured with the
same ARFCN_3G (TDD), then BSC broadcasts the ARFCN_3G only once.
Logical ARFCN_LTE(FDD) B11 Yes B12 Yes
name TRX nb No
HMI EUARFCN Sub-syste
BSC Cell Type No
name Instance
LTE cell RMS No
Definition Downlink FDD E-UTRAN Absolute Radio Frequency Channel Number (EUARFCN) of an external LTE FDD cell.
Rec ref. 3GPP TS 36.101 Domai 2G-LTE Min value 0 Coded Min 0
Coding rules --
Mandatory rules Only the following downlink EUARFCN ranges are standardized for FDD:
1) 0 599 and
2) 600 1199 and
3) 1200 1949 and
4) 1950 2399 and
5) 2400 2649 and
6) 2650 - 2749 is forbidden (as not applicable in 3GPP)
7) 2750 - 3449 and
8) 3450 - 3799 and
9) 3800 4149 and
10) 4150 4749 and
11) 4750 4949 and
12) 5010 5179 and
13) 5180 5279 and
14) 5280 5379 and
17) 5730 - 5849 and
18) 58505999 and
19) 60006149 and
20) 61506449 and
21) 64506599
- For a given 2G cell, there shall be no more than 8 distinct ARFCN_LTE(FDD) among all the neighbour LTE FDD cells target for reselection.
Recommended --
rules
External - Significant if RAT_LTE is FDD
comment - The FDD EUARFCNs are used on the Air interface.
- The FDD EUARFCNs of the LTE neighbour cells configured for reselection are broadcast on BCCH.
- Parameter available on BSC Evolution only. m
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. But any modification impacts System Information Broadcasting. Change applied
immediately after modification, in broadcasted SI2quater messages and in dedicated Channel Release and Packet Measurement Order messages of the current calls.
template
Internal comment - A coded default value is not needed since the operator cannot create a LTE FDD cell without configuring its EUARFCN (no dummy value needed).
- If, for a serving 2G cell where EN_2G_TO_LTEFDD_CELL_RESELECTION is not disabled, two neighbour LTE cells are target for reselection and configured with the
same ARFCN_LTE (FDD), then BSC broadcasts the ARFCN_LTE only once.
Logical ARFCN_LTE(TDD) B11 Yes B12 Yes
name TRX nb No
HMI EUARFCN Sub-syste BSC Cell Type No
name Instance LTE cell RMS No
Definition Downlink TDD E-UTRAN Absolute Radio Frequency Channel Number (EUARFCN) of an external
LTE TDD cell.
Coding rules --
Mandatory rules - Only the following downlink EUARFCN ranges are standardized for TDD:
33) 36000 36199 and
34) 36200 36349 and
35) 36350 36949 and
36) 36950 37549 and
37) 37550 37749 and
38) 37750 - 38249 and
39) 38250 - 38649 and
40) 38650 - 39649
- For a given 2G cell, there shall be no more than 8 distinct ARFCN_LTE(TDD) among all the neighbour LTE TDD cells target for reselection.
- For a given 2G cell, where both EN_2G_TO_3GTDD_CELL_RESELECTION and
EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, if FAKE_FDD_MANAGEMENT = 1 then
there shall be no more than 3 distinct ARFCN_LTE(TDD) among all the neighbour LTE TDD cells target for reselection.
Recommended --
rules
External - Significant if RAT_LTE is TDD
comment - The TDD EUARFCNs are used on the Air interface.
- The TDD EUARFCNs of the LTE neighbour cells configured for reselection are broadcast on BCCH.
- Parameter available on BSC Evolution only.
Internal comment - A coded default value is not needed since the operator cannot create a LTE TDD cell without configuring its EUARFCN (no dummy value needed).
- If, for a serving 2G cell where EN_2G_TO_LTETDD_CELL_RESELECTION is not disabled,
Logical ASIG_IP_SUBNET_MASK_2_BSC m B11 No B12 Yes
name TRX nb No
HMI Asig Subnet Mask 2 Sub-syste BSC template Cell Type No
Definition Mask of the second subnet for the feature A signalling over IP.
It is used when the SCTP end to end redundancy applied on BSC side.
Category Site (CAE) OMC-R access Displayed Type IP address Unit None
Rec ref. None Domai IP Min value None Coded Min
n Max value None Coded Max
Spec ref. TMN Administration services Coded Max
Coding rules coded on 15 characters string
Mandatory rules --
Recommended - 255.255.255.255 and 0.0.0.0 are both forbidden

rules
External Parameter change: Changing the IP configuration (e.g. subnet mask, and so routing table) of any IP equipment of the network (BSC included) may impact the ongoing
comment traffic. Usually, the change is also to be done accordingly in the gateway(s). As consequence, Alcatel-Lucent recommends to shut down the traffic before any
change.
Internal comment - The coded default value implemented on BSC-> OMC is 15 blanks string; that dummy value indicates that the operator does not provide any IP address yet. It is not
displayed.
- The IP address is coded on 32 bits in the DLS.
two neighbour LTE cells are target for reselection and configured with the same ARFCN_LTE (TDD), then BSC broadcasts the ARFCN_LTE only once.
Logical ASIG_IP_SUBNET_MASK_BSC B11 Yes B12 Yes
name TRX nb No
HMI Asig Subnet Mask Sub-syste BSC Cell Type No
Definition Mask of the subnet where is allocated the range of BSC addresses used for telecom protocols for the feature A signalling over IP
Mandatory rules --

rules
change.
displayed.
Logical ASIG_OVER_IP_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI ASIG_OVER_IP_PRIORITY Sub-syste BSC Cell Type No
Definition BSS internal priority used for the Asig over IP flow (M3UA/SCTP signalling between BSC and MSC, on A interface).
Category System (CST) OMC-R access None (DLS) Type Number Unit None
Spec ref. Not linked to a document Coded Max 3
Coding rules 0: higher priority
3: lower priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ASIG_SCTP_ENDPOINT_IP_Address_1 B11 Yes B12 Yes
name TRX nb No
HMI ASIG_SCTP_ENDPOINT_IP_Address_1 Sub-syste BSC Cell Type No
name Instance SCTP EndPoint RMS No
Definition Primary IP address of a SCTP endpoint (used by M3UA protocol) on the MSC side.
Category Site (CAE) OMC-R access Changeable Type IP address Unit None
Spec ref. xxxx Coded Max
Mandatory rules - ASIG_SCTP_ENDPOINT_IP_Address_1 and ASIG_SCTP_ENDPOINT_PORT shall together be unique inside one MSC
- 255.255.255.255 and 0.0.0.0 are both forbidden
Recommended --
rules
External Parameter change: before any modification, the operator must lock the associated A Signalling Link (ASL).
comment
Internal comment 2 coded default values are implemented (15 blanks string on BSC-> OMC, and empty string on OMC-> BSC); those dummy values indicate that the operator does not
provide any IP address yet. They are not displayed.
The IP address is coded on 32 bits in the DLS.
Logical ASIG_SCTP_ENDPOINT_IP_Address_2 B11 Yes B12 Yes
name TRX nb No
HMI ASIG_SCTP_ENDPOINT_IP_Address_2 Sub-syste BSC Cell Type No
Definition Secondary IP address of a SCTP endpoint (used by M3UA protocol) on the MSC side.
It is an optional address used in case of SCTP multihoming in MSC side.
Mandatory rules - ASIG_SCTP_ENDPOINT_IP_Address_2 and ASIG_SCTP_ENDPOINT_PORT shall togetherbe unique inside one MSC
Recommended --
rules
comment
Internal comment 2 coded default values are implemented (15 blanks string on BSC-> OMC, and empty string on OMC-> BSC); those dummy values indicate that the operator does not
Logical ASIG_SCTP_ENDPOINT_LIST B11 Yes B12 Yes
name TRX nb No
HMI ASIG_SCTP_ENDPOINT_LIST Sub-syste BSC Cell Type No
name Instance MSC RMS No
Definition List of the SCTP endpoints (used by M3UA protocol) on the MSC side.
Up to 4 endpoints can be defined in that list.
Category Site (CAE) OMC-R access Set Create & Changeable Type List of numbers Unit None
Coding rules coded as an array of 4 entries
Each entry is an SCTP endpoint, composed of ASIG_SCTP_ENDPOINT_IP_Address_1, ASIG_SCTP_ENDPOINT_PORT and ASIG_SCTP_ENDPOINT_IP_Address_2
Mandatory rules When the MSC TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the ASIG_SCTP_ENDPOINT_LIST must be equal or greater than
MIN_NB_ACTIVE_
Recommended --
rules
External Parameter change: before any modification, the operator must lock the associated A Signalling Link(s) (ASL).
comment
Internal comment - MAX_NB_ASIG_SCTP_ENDPOINT = 4
- A coded default value is not needed since the operator cannot create a MSC without configuring its list of SCTP endpoints (no dummy value needed).
Logical ASIG_SCTP_ENDPOINT_PORT B11 Yes B12 Yes
name TRX nb No
HMI ASIG_SCTP_ENDPOINT_PORT Sub-syste BSC Cell Type No
Definition Port of a SCTP endpoint (used by M3UA protocol) on the MSC side.
Spec ref. xxxx Coded Max 65535
Coding rules Step size = 1
Mandatory rules ASIG_SCTP_ENDPOINT_IP_Address_1 and ASIG_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one MSC
Recommended --
rules
comment
Internal comment A coded default value is not needed since the operator cannot create a MSC SCTP endpoint without configuring its port number (no dummy value needed).
Logical ATT (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IMSI Attach/Detach Sub-syste BSC Cell Type No
Definition This flag indicates to the MS if IMSI Attach/detach procedure is allowed in the cell.
Coding rules 0: not allowed, 1: allowed
Mandatory rules Equal to ATT (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical AUP_IP_SUBNET_MASK_BSC B11 No B12 Yes
name TRX nb No
HMI AUP_IP_SUBNET_MASK_BSC Sub-syste BSC Cell Type No
Definition Mask of the subnet where is allocated the range of BSC addresses used for telecom protocols for the feature A user plane over IP
Mandatory rules --

rules
change.
displayed.
- minimum 3 addresses.
Logical AUP_OVER_IP_CODEC_SUP B11 No B12 Yes
name TRX nb No
HMI AUP_OVER_IP_CODEC_SUP Sub-syste BSC Cell Type No
Definition Bitmap (8 bits) defining the codec types supported for the A Interface user plane over IP.
The bit set to 1 indicates that the BSS supports the use of IP interface for the given codec type, with the transcoder (TC) located in the media gateway (MGW).
Category Site (CAE) OMC-R access Changeable Type Bitmap Unit None
Spec ref. Normal assignment Coded Max 127
Coding rules bit 8 (most significant)=0: (reserved);
bit 7=1: CS data (dummy codec) is supported over IP;
bit 6=1: FR AMR-WB is supported over IP;
bit 5=1: HR AMR-NB is supported over IP;
bit 4=1: FR AMR-NB is supported over IP;
bit 3=1: EFR is supported over IP;
bit 2=1: HR is supported over IP;
bit 1 (least significant)=1: FR is supported over IP.
Mandatory rules - AUP_OVER_IP_CODEC_SUP and AUP_OVER_TDM_CODEC_SUP cannot be set to zero at the same time.
- The bit1 of AUP_OVER_IP_CODEC_SUP and AUP_OVER_TDM_CODEC_SUP cannot be set to zero at the same time.
- the parameter value is updated only if the other requirements of the external comment are fulfilled.
Recommended --
rules
External - If a codec type is supported on both A user plane interface, IP and TDM, the IP interface will be preferred.
comment - Significant only if EN_AUP_OVER_IP is enabled
- Parameter change: the BSS-TEL is to be previously locked. This procedure leads the BSC to stop telecom activity and reject any new calls and wait for some
minutes (Wait Traffic Clear) before shutting down the on going calls. After modification, a BSC reset is triggered and the BSS-TEL is unlocked to reopen the telecom
service.
Internal comment --
Logical AUP_OVER_TDM_CODEC_SUP B11 No B12 Yes
name TRX nb No
HMI AUP_OVER_TDM_CODEC_SUP Sub-syste BSC Cell Type No
Definition Bitmap (8 bits) defining the codec types supported for the A Interface user plane over TDM.
The bit set to 1 indicates that the BSS supports the use of TDM interface for the given codec type, with the transcoder (TC) located in the BSS.
In case of "Mixed IP/TDM A interface" architecture, AUP_OVER_TDM_CODEC_SUP <> 0.
In case of "Full AUPoIP" architecture, AUP_OVER_TDM_CODEC_SUP = 0.
Coding rules bit 8 (most significant)=0: (reserved);
bit 7=1: CS data (dummy codec) is supported over TDM;
bit 6=1: FR AMR-WB is supported over TDM;
bit 5=1: HR AMR-NB is supported over TDM;
bit 4=1: FR AMR-NB is supported over TDM;
bit 3=1: EFR is supported over TDM;
bit 2=1: HR is supported over TDM;
bit 1 (least significant)=1: FR is supported over TDM.
Mandatory rules - AUP_OVER_IP_CODEC_SUP and AUP_OVER_TDM_CODEC_SUP cannot be set to zero at the same time.
- The bit1 of AUP_OVER_IP_CODEC_SUP and AUP_OVER_TDM_CODEC_SUP cannot be set to zero at the same time.
- The "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0) can be supported only if the Atermuxes linked to the MFS are GPRS-dedicated.
- The "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0) is not compatible with TFO (EN_TFO and EN_TFO_AMR_NB and EN_TFO_AMR_WB shall be
disabled in all the cells).
- When the Abis/Ater flexibility is used, then EN_AUP_OVER_IP is enabled in "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0)
Recommended --
rules
External - If a codec type is supported on both A user plane interface, IP and TDM, the IP interface will be preferred.
comment - Significant only if EN_AUP_OVER_IP is enabled
- Parameter change: the BSS-TEL is to be previously locked. This procedure leads the BSC to stop telecom activity and reject any new calls and wait for some
service.
Internal comment --
Logical AUT_BAR B11 Yes B12 Yes
name TRX nb No
HMI AUTO_BAR_CELL m Sub-syste BSC Cell Type No
name Instance BSC template RMS No
Definition This flag enables/inhibits automatic barring of cell.
Coding rules 0: disabled, 1: enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical AUTO_DSC B11 Yes B12 Yes
name TRX nb No
HMI AUTO_DSC Sub-syste BSC Cell Type No
Definition This flag enables/disables auto disconnection of LAPD links.
Category System (CST) OMC-R access None (DLS) Type Flag Unit None
Coding rules 0: disabled 1: enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical B_NUM B11 Yes B12 Yes
name TRX nb No
HMI B_NUM Sub-syste BSC Cell Type No
Definition Number of BLOCK/UNBLOCK messages sent in one burst.
Spec ref. Reset circuit and blocking and unequipped circuit Coded Max 35
Coding rules --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type.
comment
Internal comment --
Logical BANDWIDTH_PER_SIG_LINK B11 Yes B12 Yes
name TRX nb No
HMI BANDWIDTH_PER_SIG_LINK Sub-syste BSC Cell Type No
Definition Bandwidth consumed by the RSL signalling link associated to a TRX on Abis interface. The bandwidth, used by the OML link associated to a BTS, is also included in that
bandwidth (as the global OML bandwidth is assumed very low or very sporadic).
Mandatory rules In case of a BTS with several Abis/E1 links, BANDWIDTH_PER_SIG_LINK shall take the same value on each link.
Recommended --
rules
External --
comment
Internal comment - The present parameter is multiplied by the number of configured TRX mapped onto the Abis link in order to compute the bandwidth at Abis link level (even if the TRX
are not already mapped onto TRE in the BTS)
Logical BANDWIDTH_PER_TCH_TS B11 Yes B12 Yes
name TRX nb No
HMI BANDWIDTH_PER_TCH_TS Sub-syste BSC Cell Type No
Definition Abis bandwidth consumed by a RTS supporting some TCH(s) (one FR TCH or two HR TCHs).
The RTSs supporting only one HR TCH are supposed to consume half this bandwidth.
The statistical bandwidth gain brought by DTX (when DTX is activated) shall be taken into account in this value.
Mandatory rules In case of a BTS with several Abis/E1 links, BANDWIDTH_PER_TCH_TS shall take the same value on each link.
Recommended --
rules
External --
comment
Internal comment - Only values equal and below 16 kbit/s are allowed. Greater values are necessary for 8PSK AMR-WB.
Logical BCC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BCC Sub-syste BSC Cell Type No
Definition BTS colour code of the cell.
Coding rules coded over 3 bits
Mandatory rules Equal to BCC (MFS)
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Logical BCCH_ARFCN B11 Yes B12 Yes
name TRX nb No
HMI BCCH_ARFCN Sub-syste BSC Cell Type No
Definition Indicates the Absolute Radio Frequency Channel Number of the frequency used as BCCH.
Category Site (CAE) OMC-R access Virtual changeable Type Number Unit None
Spec ref. Handover Preparation Coded Max 1023
Def value None Coded Def -1
Coding rules The coded default value of -1 is for implementation purposes only; this dummy value indicates that the operator does not provide any radio TS description yet.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - The ARFCN of the G1 band are in the range {975, 976, , 1023, 0}.
- For an own cell, the BCCH frequency is deduced from the radio TS description.
Logical BCCH_ARFCN(n)(BSC) B11 Yes B12 Yes
name TRX nb No
HMI BCCH_ARFCN Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Indicates the Absolute Radio Frequency Channel Number of the frequency used as BCCH in the adjacent cell.
Coding rules The coded default value of -1 is for implementation purposes only; this dummy value indicates that the operator does not provide any BCCH yet.
Mandatory rules - BCCH_ARFCN(n)(BSC) = BCCH_ARFCN(n)(MFS)
For Evolium serving cell:

- there can be up to 32 different BCCH 2G frequencies for the set of all the target cells for reselection (no matter the 2G/3G neighborhood of the serving cell for
reselection) .
- if the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells for
handover.
- if the neighborhood of the serving cell for handover is mixed 2G/3G, then there shall be no more than 31 different BCCH 2G frequencies for the set of all the target
cells for handover.
Recommended --
rules
External --
comment
Internal comment - The ARFCN of the G1 band are in the range {975, 976, , 1023, 0}.
- The BCCH frequency of an adjacent external cell is directly editable in the HMI. To be consistent with the MFS related parameter, the OMC-R access is defined
according to this case (changeable). The BCCH frequency of an adjacent internal cell is virtual changeable.
Logical BCCH_EXT B11 Yes B12 Yes
name TRX nb No
HMI BCCH_EXT Sub-syste BSC Cell Type No
Definition This flag enables / disables the use of extended BCCH.
Coding rules 0: false, 1:true
Mandatory rules -When EN_SOLSA is enabled, the BCCH_EXT shall be set to true.
-When EN_VGCS is disabled :
. if BCCH_EXT = true, then BS_AG_BLKS_RES >= 1
-When EN_VGCS is enabled :
. if BCCH_EXT = false, BS_AG_BLKS_RES >= NUMBER_NCH_BLOCKS
. if BCCH_EXT = true, then BS_AG_BLKS_RES > NUMBER_NCH_BLOCKS
Recommended The support of extended BCCH (parameter BCCH_EXT) is HIGHLY recommended in cells having adjacent cells in several frequency bands and at least 18 adjacent
rules BCCH within the same band.
External --
comment
Internal comment The recommended rule is linked to the fact that when the SI2bis message is sent, it is recommended to activate the extended BCCH
i) for 2G to 2G cell reselection to reduce the cell reselection duration
ii) for 2G to 3G cell reselection to reduce the acquisition of the system information on 3G cells.
Logical BF_HI_RX B11 Yes B12 Yes
name TRX nb No
HMI BF_HI_RX Sub-syste BSC Cell Type No
Definition Threshold on LAPD RX buffers occupancy for transition from normal to busy condition.
Category Network (CDE) OMC-R access None (DLS) Type Threshold Unit %
Coding rules --
Mandatory rules --
Recommended BF_HI_RX > BF_LO_RX

rules
External --
comment
Internal comment --
Logical BF_HI_TX B11 Yes B12 Yes
name TRX nb No
HMI BF_HI_TX Sub-syste BSC Cell Type No
Definition Threshold on LAPD TX buffers occupancy for transition from normal to busy condition.
Coding rules --
Mandatory rules --
Recommended BF_HI_TX > BF_LO_TX

rules
External --
comment
Internal comment --
Logical BF_LO_RX B11 Yes B12 Yes
name TRX nb No
HMI BF_LO_RX Sub-syste BSC Cell Type No
Definition Threshold on LAPD RX buffers occupancy for transition from busy to normal condition.
Coding rules --
Mandatory rules --
Recommended BF_LO_RX < BF_HI_RX

rules
External --
comment
Internal comment --
Logical BF_LO_TX B11 Yes B12 Yes
name TRX nb No
HMI BF_LO_TX Sub-syste BSC Cell Type No
Definition Threshold on LAPD TX buffers occupancy for transition from busy to normal condition.
Coding rules --
Mandatory rules --
Recommended BF_LO_TX < BF_HI_TX

rules
External --
comment
Internal comment --
Logical BS_AG_BLKS_RES (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BS_AG_BLKS_RES Sub-syste BSC Cell Type No
Definition Number of CCCH blocks reserved for the access grant channel (AGCH).
Coding rules coded on 3 bits (000 : 0, ...111 : 7)
When CCCH_CONF = 1, def value = 1.
Mandatory rules -BS_AG_BLKS_RES (MFS) = BS_AG_BLKS_RES (BSC) for a given cell.
- when CCCH_CONF <> 1 and CBCH is configured in the cell, BS_AG_BLKS_RES must be > 0
- if CCCH_CONF= 1, then max value = 2, else max value = 7
- When EN_VGCS is disabled :
. if BCCH_EXT = true, then BS_AG_BLKS_RES >= 1
- When EN_VGCS is enabled :
. if BCCH_EXT = false, then BS_AG_BLKS_RES >= NUMBER_NCH_BLOCKS
. if BCCH_EXT = true, then BS_AG_BLKS_RES > NUMBER_NCH_BLOCKS
Recommended --
rules
External - Parameter change:
comment no impact on the telecom service, on going traffic is not disrupted. But any modification impacts Paging (paging queues are reset and paging is suspended until the
reconfiguration is completed).
Internal comment At OMC, CBCH configured in the cell corresponds to channelCombination = CBH or SDH in the TRX attribute listOfRadioChannel.
Logical BS_CV_MAX (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BS_CV_MAX Sub-syste BSC Cell Type No
Definition Number of remaining RLC data blocks sent (per assigned PDCH) by the MS, below which the Count Down procedure is entered.
One third of the number of RLC data blocks per assigned PDCH before the MS checks if the resolution contention has failed.
Rec ref. 3GPP TS 04.60 Domai GPRS Min value 1 Coded Min 1
Coding rules Coded on 4 bits (1==0001, 2 == 0010 .. 15 == 1111).
Mandatory rules Equal to BS_CV_MAX (MFS)
Recommended BS_CV_MAX should be set to a value equal to the "minimum" round trip delay to optimise the uplink re-transmission of non-acknowledged blocks and minimise
rules window-stalled situations.
If BS_CV_MAX is set greater than round-trip-delay, uplink retransmissions of unacknowledged blocks may be delayed.
It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Abis or Ater satellite links:
- BS_CV_MAX = 9 if GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell,
- BS_CV_MAX = 15 if GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell.
External Used by the MS to start the countdown value process (release of UL TBF) or to consider acknowledgement messages as valid for a given RLC data block. Lower
comment values avoid too many TBF releases and reestablishments.
Internal comment --
Logical BS_P_CON_ACK B11 Yes B12 Yes
name TRX nb No
HMI BS_P_CON_ACK Sub-syste BSC Cell Type Yes
Definition Supervision of the BS Power Control procedure (used also by the VAMOS DL power control).
Category Site (CAE) OMC-R access Changeable Type Timer Unit 2 x Samfr
Spec ref. Power control and radio link supervision Coded Max 31
Coding rules step size=1 (2 x Samfr)
Mandatory rules --
Recommended --
rules
External --
comment
Logical BS_P_CON_INT B11 Yes B12 Yes
name TRX nb No
HMI BS_P_CON_INT Sub-syste BSC Cell Type Yes
Definition Minimum delay between two consecutive BS power commands (used also by the VAMOS DL power control).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical BS_PA_MFRMS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BS_PA_MFRMS Sub-syste BSC Cell Type No
Definition Number of 51 frame multiframes between consecutive occurrences of a Paging Group.
Coding rules coded on 3 bits (000 : 2, ... 111: 9)
Mandatory rules BS_PA_MFRMS (BSC) = BS_PA_MFRMS (MFS) for a given cell
Recommended --
rules
External The bigger this parameter is, the lesser the MS power consumption is.
comment
Internal comment --
Logical BS_TXPWR_ATTENUATION B11 Yes B12 Yes
name TRX nb No
HMI BS_TXPWR_ATTENUATION Sub-syste BSC Cell Type No
Definition This parameter defines the power reduction, expressed in 0.1dB, applied on the output power (after leveling). In a concentric or multi-band cell, this attenuation applies on
the output power of the TRX(s) of the outer zone.
Coding rules step size = 0.1dB.
Mandatory rules - when EN_BS_PC_PS is enabled, then BS_TXPWR_ATTENUATION + POW_RED_P0 + MAX_POW_RED_DYN <= 32
- when EN_BS_PC_PS is enabled, then BS_TXPWR_ATTENUATION + POW_RED_P0_PDDCB <= 34
Recommended --
rules
External --
comment
Internal comment - Not sent to the MFS, because the power received from BTS (via MEGCH) is already attenuated and finely defined (in 0.1 dB)
- This parameter is sent to the BTS via OML.
- On G3, G4 and G5 TREs, if BS_TXPWR_ATTENUATION BS_TXPWR_MIN > 32dB, then an attenuation of 32 dB is applied by the BTS.
Logical BS_TXPWR_ATTENUATION_INNER B11 Yes B12 Yes
name TRX nb No
HMI BS_TXPWR_ATTENUATION_INNER Sub-syste BSC Cell Type Yes
Definition This parameter defines the power reduction, expressed in 0.1dB, applied on the output power of the TRX(s) of the inner zone in a concentric or multi-band cell (after
leveling).
Coding rules step size = 0.1dB.
Mandatory rules --
Recommended --
rules
External The parameter value depends on configuration. The default value indicated here is for implementation purposes
comment
Internal comment - Not sent to the MFS, because PS is not supported in the inner zone of a concentric (multiband or monoband) cell
- This parameter is sent to the BTS via OML.
- Meaningful only in cells where: CELL_PARTITION_TYPE = concentric.
- On G3, G4 and G5 TREs, if BS_TXPWR_ATTENUATION_INNER BS_TXPWR_MIN > 32dB, then an attenuation of 32 dB is applied by the BTS.
Logical BS_TXPWR_MAX (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BS_TXPWR_MAX Sub-syste BSC Cell Type No
Definition This parameter defines the power reduction relative to the attenuated maximum GMSK output power of the BTS.
It is always set to 0 by the OMC.
A finer power attenuation, BS_TXPWR_ATTENUATION defined in step of 0.1dB, is managed instead.
Category Site (CAE) OMC-R access Virtual (DLS) Type Number Unit dB
Rec ref. 3GPP TS 05.08 Domai GSM Min value -30 Coded Min 15
Coding rules step size = 2dB. 0: 0 dB, 1: -2dB, ..., 15: -30dB
Mandatory rules Equal to BS_TXPWR_MAX (MFS)
Recommended --
rules
External The BTS maximum allowed transmit power is defined relatively to the sector maximum RF transmit power in GMSK (due to hardware limitation).
comment
Internal comment - With the RFD252615, fine BTS power level from the OMC, this parameter is not directly managed by the operator anymore (greyed on the HMI).
- This parameter is sent to the BTS via RSL.
- it is kept in order to avoid impact on the telecom power reduction algorithms.
Logical BS_TXPWR_MAX_INNER (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BS_TXPWR_MAX_INNER Sub-syste BSC Cell Type Yes
Definition This parameter defines the power reduction relative to the attenuated maximum GMSK output power of the TRX of the inner zone in a concentric or multi-band cell.
A finer power attenuation, BS_TXPWR_ATTENUATION_INNER defined in step of 0.1dB, is managed instead.
Rec ref. None Domai GSM Min value -30 Coded Min 15
Mandatory rules --
Recommended --
rules
comment
The parameter value depends on configuration. The default value indicated here is for implementation purposes.
Internal comment - Meaningful only in cells where: CELL_PARTITION_TYPE = concentric.
- With the RFD252615, fine BTS power level from the OMC, this parameter is not directly managed by the operator anymore (greyed on the HMI).
- This parameter is sent to the BTS via RSL
Logical BS_TXPWR_MIN B11 Yes B12 Yes
name TRX nb No
HMI BS_TXPWR_MIN Sub-syste BSC Cell Type No
Definition This parameter defines the maximum value of the power attenuation (so the minimum allowed transmission power) relative to the attenuated maximum GMSK output
power of the BTS.
Def value -24 Coded Def 12
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter is not sent to the BTS
- it is kept with a step of 2dB in order to avoid impact on the telecom power reduction algorithms..
- On G3, G4 and G5 TREs, if BS_TXPWR_ATTENUATION BS_TXPWR_MIN > 32dB, then an attenuation of 32 dB is applied by the BTS.
Logical BSC_EN_RF_RES_IND B11 Yes B12 Yes
name TRX nb No
HMI BSC_EN_RF_RES_IND Sub-syste BSC Cell Type No
Definition Enables/disables the RF RESOURCE INDICATION processing by the BSC.
Category Site (CAE) OMC-R access None (DLS) Type Flag Unit None
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical BSC_RSL_TID B11 Yes B12 Yes
name TRX nb No
HMI BSC_RSL_TID Sub-syste BSC Cell Type No
name Instance RSL RMS No
Definition RSL termination identifier on BSC side.
Category Site (CAE) OMC-R access None (DLS) Type Number Unit None
Spec ref. O&M Abis interface Coded Max 65535
Mandatory rules Inside a BCS, each BSC_RSL_TID is unique.
Recommended --
rules
External --
comment
Internal comment --
Logical BSC_SSRC B11 No B12 Yes
name TRX nb No
HMI BSC_SSRC Sub-syste BSC Cell Type No
Definition Fixed SSRC value used by the BSC when sending RTP/RTCP packets.
Spec ref. AUPoIP: BSS-MGW interface Coded Max 4294967295
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment = FADE1958 hexa
Logical BSC_X25_primary_address_i [1] B11 Yes B12 Yes
name TRX nb No
HMI BSC Primary X25 Address [1] Sub-syste BSC Cell Type No
Definition First character of BSC X25 primary address.
Spec ref. Short message service cell broadcast Coded Max 255
Coding rules 1character of a string. default = blank character
Mandatory rules changeable if SMSCB_STATE=disabled
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
name TRX nb No
Definition Tenth character of BSC X25 primary address.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Eleventh character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Twelfth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Thirteenth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fourteenth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fifteenth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Second character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Third character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fourth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fifth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Sixth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Seventh character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Eighth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Ninth character of BSC X25 primary address.
Recommended --
rules
comment
Internal comment --
Logical BSC_X25_secondary_address_i [1] B11 Yes B12 Yes
name TRX nb No
HMI BSC Secondary X25 Address [1] Sub-syste BSC Cell Type No
Definition First character of BSC X25 secondary address.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Tenth character of BSC X25 secondary address.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Eleventh character of BSC X25 secondary address.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Twelfth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Thirteenth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fourteenth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fifteenth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Second character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Third character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fourth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Fifth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Sixth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Seventh character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Eighth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Ninth character of BSC X25 secondary address.
Recommended --
rules
comment
Internal comment --
Logical BSIC (GSM) B11 Yes B12 Yes
name TRX nb No
HMI BSIC Sub-syste BSC Cell Type No
Definition Concatenation of the NCC and the BCC.
Category Site (CAE) OMC-R access Changeable Type Abstract Unit None
Rec ref. GSM TS 04.08 Domai GSM Min value # Coded Min
n Max value # Coded Max
Spec ref. Radio measurements data processing Coded Max
Def value # Coded Def
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment See BCC (BSC) and NCC (BSC)
Logical BSS_DL_MUXTRAUP_UDP_PORT B11 No B12 Yes
name TRX nb No
HMI BSS_DL_MUXTRAUP_UDP_PORT Sub-syste BSC Cell Type No
Definition UDP port of TPIP/MUXTRAUP function of the BSC, used by the TC for Downlink traffic.
Spec ref. TMN Administration services Coded Max 65535
Coding rules --
Mandatory rules The parameter shall be outside the range (54528-54551)
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is enabled in "Mixed IP/TDM A interface" architecture (AUP_OVER_TDM_CODEC_SUP <> 0).
comment - Parameter change: the BSS-TEL is to be previously locked in order to stop the BSC telecom activity from TC-NEM or OMC reset the active TCIF board.
Internal comment - default = D4FEx
- This parameter is configurable from the BSC terminal.
- the forbidden range is the one of IPTCH_UDP_PORT_TC_MUX (in case MUXTRAUP_IP_ADDRESS_BSC = TC_TRAUP_IP_ADDRESS)
Logical BSS_IP_SUBNET_MASK_BSC B11 Yes B12 Yes
name TRX nb No
HMI Bss Subnet Mask Sub-syste BSC Cell Type No
Definition Mask of the subnet where is allocated the range of BSC addresses used for telecom protocols for the feature Ip transport in the BSS.
Mandatory rules --

rules
change.
displayed.
Logical BSS_MAX_PAG_RATE B11 Yes B12 Yes
name TRX nb No
HMI BSS_MAX_PAG_RATE Sub-syste BSC Cell Type No
Definition This parameter defines the maximum paging rate on A interface allowed for a given BSC site.
Category Site (CAE) OMC-R access None (DLS) Type Enumerated Unit None
Coding rules 145 : Maximum paging rate accepted by the BSC on A interface is 145/s
245 : Maximum paging rate accepted by the BSC on A interface is 245/s
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Parameter change: No impact on the telecom service, on-going traffic is not disrupted
Internal comment - The value 145 and 245 correspond to the maximum committed values in ALU BSS CS Traffic Model plus a 20% margin, respectively 121+20% and 204 + 20%
- The default value allows configurations of CCCH_CONF up to 6 (ie 4 CCCHs slots)
Logical BSS_SEND_CM_ENQUIRY B11 Yes B12 Yes
name TRX nb No
HMI Send_CM_Enquiry Sub-syste BSC Cell Type No
Definition Controls the trigger of Classmark Enquiry procedure during Location Updating procedure.
Spec ref. Classmark handling Coded Max 2
Coding rules 0: the classmark enquiry is never initiated by the BSC during Location Updating procedure;
1: on reception of a LOCATION UPDATING REQUEST message with ES IND flag set to 0, the BSC will always initiate a classmark enquiry;
2: on reception of a LOCATION UPDATING REQUEST message with ES IND flag set to 0, the BSC will initiate the classmark enquiry if algorithm A5/1 is not available
(information available in MS classmark 1 IE sent in the LOCATION UPDATING REQUEST).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical BSS_TRANSPORT_MODE (BSC) B11 Yes B12 Yes
name TRX nb No
HMI BSS_TRANSPORT_MODE Sub-syste BSC Cell Type No
Definition IP Transport mode for Ater level signalling links (GSL, Qmux/TCSL, N7, knowing only GSL applies to the MFS): TDM or IP
Spec ref. IP routing and addressing Coded Max 1
Coding rules 0 : TDM, 1 :IP
Mandatory rules - Can be set to IP if all the atermuxes, connected to the MFS, are pure PS atermuxes (AterMux-GPRS-Usage=dedicated and GPRS-capacity=100) and if all the
atermuxes, connected to the TC, are pure CS atermuxes (AterMux-GPRS-Usage=mixed and GPRS-capacity=0).
- Can be set to IP if at least one TCSL link (on TC side) has been configured in the BSC.
- When set to IP on BSC side, then can be set to IP on MFS side for the BSS.
- Can be set to 'TDM', if all the Abis-Transport-Mode are set to 'TDM'
Recommended --
rules
External - IP transport in BSS is available on BSC Evolution only.
comment - Parameter change: a BSC reset procedure is needed, after modification. This BSC reset leads to a total outage of several minutes. No telecom service is provided
during this procedure.
Internal comment - when BSS_TRANSPORT_MODE is TDM, Abis-Transport-Mode (BOP) is TDM and BTS-TransMode (BOP) is TDM.
Logical BSS_UL_MUXTRAUP_UDP_PORT B11 No B12 Yes
name TRX nb No
HMI BSS_UL_MUXTRAUP_UDP_PORT Sub-syste BSC Cell Type No
Definition UDP port of TPIP/MUXTRAUP function of the BSC, used by the BTS for Uplink traffic.
Coding rules --
Mandatory rules --
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is enabled.
comment - Parameter change: the BSS-TEL is to be previously locked in order to stop the BSC telecom activity.
Internal comment - default = D500x
- if EN_AUP_OVER_IP is enabled, the BTS uses instead IPTCH_UDP_PORT_TC_MUX for Uplink traffic to reach TC.
Logical BTS_IP_Address B11 Yes B12 Yes
name TRX nb No
HMI BTS_IP_Address Sub-syste BSC Cell Type No
name Instance BTS RMS No
Definition IP address of the BTS, used by all protocols (IPTCH, IPGCH, RSL, OML,).
Category Site (CAE) OMC-R access Set Create & Changeable Type IP address Unit None
Spec ref. IP routing and addressing Coded Max
Mandatory rules - 255.255.255.255 and 0.0.0.0 are both forbidden
Recommended --
rules
External Meaningful only for BTS in IP transport mode (in both A user plane over TDM or IP).
comment
Internal comment - When the IP BTS is created in the BSC, it is created with its IP@. The BTS gets its IP@ from the DHCP request. The BTS IP address is sent to the MFS via BSCGP:
state change message.
- 2 coded default values are implemented (15 blanks string on BSC-> OMC, and empty string on OMC-> BSC); those dummy values indicate that the operator does not
Logical BTS_Q_LENGTH B11 Yes B12 Yes
name TRX nb Yes
HMI BTS_Queue_Length Sub-syste BSC Cell Type No
Definition Maximum number of Assignment Requests and Handover Requests that can be queued simultaneously.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical BTS_RSL_TID B11 Yes B12 Yes
name TRX nb No
HMI BTS_RSL_TID Sub-syste BSC Cell Type No
Definition RSL termination identifier of one TRX (inside a TRE HW module) on BTS side
Mandatory rules - Inside a TRE HW module, each BTS_RSL_TID is unique
Recommended --
rules
External --
comment
Internal comment - up to 6 TRXs per TRE HW module (with MC module)
- sent to the BSC via OML in the HW capabilities report
Logical Call_user_data_sel B11 Yes B12 Yes
name TRX nb No
HMI Call_User_Data_Selector Sub-syste BSC Cell Type No
Definition Identifies the higher protocol selector for an outgoing connection.
Coding rules 0 to 16 bytes string
Mandatory rules Can be changed only when SMSCB_State is disabled
Recommended --
rules
comment Each byte of the string can get a value in the range [0..255].
Internal comment OMC sends a string of a fixed length of 16bytes.
The default string is an empty string.
The right side of the string might be filled by zeros until 16 bytes are reached.
Logical CAPTURE_TRAFFIC_CONDITION B11 Yes B12 Yes
name TRX nb No
HMI CAPTURE_TRAFFIC_CONDITION Sub-syste BSC Cell Type No
Definition This parameter determines the condition on traffic load in the serving cell to trigger a general capture handover.
Spec ref. Handover preparation Coded Max 2
Coding rules 0: Any load, 1: Not low, 2: High
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CBC_window B11 Yes B12 Yes
name TRX nb No
HMI CBC_Window Sub-syste BSC Cell Type No
Definition Maximum number of outstanding primitives on the BSC/CBC interface for both incoming and outgoing primitives.
Coding rules --

shall be set to "1" when SMSCB_FEATURE_SET="FS1"
Recommended --
rules
External Default value corresponds to SMSCB_FEATURE_SET = FS1.
comment If SMSCB_FEATURE_SET = FS2, CBC_Window should be set to 3.
Internal comment --
Logical CBC_X25_primary_address B11 Yes B12 Yes
name TRX nb No
HMI CBC Primary X25 Address Sub-syste BSC Cell Type No
Definition CBC X25 primary address.
Coding rules 0 to 15 characters string. *: default = empty string
Recommended --
rules
comment
Internal comment --
Logical CBC_X25_secondary_address B11 Yes B12 Yes
name TRX nb No
HMI CBC Secondary X25 Address Sub-syste BSC Cell Type No
Definition CBC X25 secondary address.
Recommended --
rules
comment
Internal comment --
Logical CCCH_CONF (BSC) B11 Yes B12 Yes
name TRX nb No
HMI CCCH_CONF Sub-syste BSC Cell Type No
Definition Configuration of the CCCH.
Category Site (CAE) OMC-R access Virtual changeable Type Enumerated Unit None
Coding rules Coded over 3 bits
0: one CCCH not combined (TS0),
1: one CCCH combined (TS0)
2: two CCCH not combined (TS0+2)
4: three CCCH not combined (TS0+2+4)
6: four CCCH not combined (TS0+2+4+6)
Mandatory rules 1) CCCH_CONF (BSC) = CCCH_CONF (MFS) for a given cell
2)The following conditions are verified by the OMC-R in order to check the upper limit of MAX_PDCH:
i) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 1 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 1
ii) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 2 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 0
iii) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX.
iv) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 3 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 2
v) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 4 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 4 or 6
Recommended - Alcatel-Lucent recommends to set TRX_PREF_MARK > 0 (ie no PS traffic) on the BCCH TRX of the cell where CCCH_CONF = 6, otherwise only one timeslot is
rules reserved for PS traffic on that TRX.
- When CCCH_CONF >= 4, Alcatel-Lucent recommends to apply the 64Kbit/s statistic multiplexing rule and the high signalling load mode in the sector, to prevent from
the risk of RSL congestion.
- Alcatel-Lucent recommends avoiding multiple CCCH (ie values 2 and 4 and 6) in the extended cell.
- It should be noted that if some cells do not have the CCCH capacity sufficient to transfer on the radio interface all the Paging messages received from the MSC, some
paging messages may be discarded by the BTS.
External - The feature up to 4 CCCHs/cell (ie values 4 and 6) is available on BSC Evolution only, when all the TRE of the cell are G4 onwards.
comment - The PS traffic cannot be carried between two timeslots configured with CCCH (in case of value 2 or 4).
Internal comment - The support of two CCCH, and (three or four) CCCH are optional features (TRX quantity controlled)
- parameter value is computed by the OMC, based on the TRX radio configuration set by the operator.
- Mux-Rule and Abis-Signalling-Load (sector) (of the recommended rule) are defined in the BOP
Logical CELL_BAR_ACCESS m B11 Yes B12 Yes
name TRX nb No
HMI Administrative cell Barring Sub-syste BSC template Cell Type No
Definition This parameter identifies if the cell is barred by the operator for MS initial access.
Category Site (CAE) OMC-R access Virtual changeable Type Flag Unit None
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is changeable via bar-cell and debar-cell operator commands.
Logical CELL_BAR_QUALIFY B11 Yes B12 Yes
name TRX nb No
HMI CELL_BAR_QUALIFY Sub-syste BSC Cell Type No
Definition Indicates the priority of the cell for cell selection.
Coding rules 0: normal priority, 1: low priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
Logical CELL_CAPACITY_CLASS B11 Yes B12 Yes
name TRX nb No
HMI Cell Capacity Class Sub-syste BSC Cell Type No
Definition Capacity class of the cell, measured on a linear scale, ranging from 1 to 100.
Category Site (CAE) OMC-R access Changeable Type Number Unit %
Spec ref. External channel changes Coded Max 100
Coding rules binary value on 8 bits
Mandatory rules --
Recommended the Cell Capacity Class shall follow the recommended rule: In order to fulfill the 3GPP requirement of having a linear scale in the capacity class, ranging from 1 to 100:
rules
Cell Capacity Class is a linear function of the Cell capacity: value 1 shall indicate the minimum capacity class, and 100 shall indicate the maximum capacity class.
Capacity class should be measured on a linear scale.
The default value of Cell Capacity Class should depend on the number of available TCHs in the cell and since there may be up to 126 TCH channels in one GSM cell:
Cell_Capacity_Class = int{[(99/125) x (NTCH - 1)] + 1}
where NTCH is the number of all TCH channels in the Cell.
External --
comment
Internal comment --
Logical CELL_CAPACITY_CLASS_SOURCE B11 Yes B12 Yes
name TRX nb No
HMI CELL_CAPACITY_CLASS_SOURCE Sub-syste BSC Cell Type No
Definition Indicates the method used by the BSC for reporting the cell capacity to the RNC, on the Iur-g interface.
Category Network (CDE) OMC-R access None (DLS) Type Enumerated Unit None
Coding rules 1: the BSC reports the number of equipped TRXs, configured in the cell
2: the BSC reports the value of the CELL_CAPACITY_CLASS parameter
Mandatory rules --
Recommended --
rules
External Significant if EN_IURG is enabled
comment
Internal comment --
Logical CELL_CIPH_SET B11 Yes B12 Yes
name TRX nb No
HMI CELL_CIPH_SET Sub-syste BSC Cell Type No
Definition List of flag indicating what are the ciphering algorithms allowed by the operator (each bit represents an A5 algorithm).
When several algorithms can be selected (depending on network configuration, MS capabilities and operator choice), the one with the highest A5 number is used.
Spec ref. Ciphering procedure Coded Max 255
Coding rules Coded as a 8 bits bitmap. Each bit indicates if corresponding encryption algorithm is permitted.
Bit x='0' : algorithm A5/x not permitted
Bit x='1' : algorithm A5/x permitted
bit 0 : A5/0 (no ciphering)

bit 1 : A5/1.
bit 2 : A5/2
bit 3 : A5/3
bit 4 : A5/4

bit 7 : A5/7.
Mandatory rules The possible values are :

- A5/0
- A5/0 + A5/1
- A5/0 + A5/1 +A5/3
- The value A5/0 + A5/3 is not allowed because today not all mobiles support A5/3.
- If CELL_CIPH_SET does not allow the A5/3 usage in the cell, then EN_A53_PREF_ALLOC_STRATEGY cannot be enabled.
Recommended --
rules
External A5/2 is not supported by the BSS.
comment In cells where EN_DTM = enabled, the algorithm A5/3 is not used for MS, DTM capable but not supporting ciphering changes in DTM mode.
Internal comment - Bits 4 to 7 shall not be displayed at the OMC
- The support of A5/3 is an optional feature
Logical CELL_DIMENSION_TYPE B11 Yes B12 Yes
name TRX nb No
HMI Cell Dimension Sub-syste BSC Cell Type Yes
Definition Determines if the cell is processed as a macrocell or a microcell.
Coding rules 0: Macrocell, 1: Microcell
Mandatory rules Shall be consistent with CELL_TYPE.
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. The CELL_DIMENSION_TYPE parameter is not displayed as such to the O&M user.
Logical CELL_DIMENSION_TYPE(n) B11 Yes B12 Yes
name TRX nb No
HMI Cell Dimension Sub-syste BSC Cell Type Yes
Definition Determines if the adjacent cell is processed as a macrocell or a microcell
Coding rules 0: Macrocell, 1: Microcell
Mandatory rules Shall be consistent with CELL_TYPE(n).
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. The CELL_DIMENSION_TYPE parameter is not displayed as such to the O&M user
Logical CELL_EV B11 Yes B12 Yes
name TRX nb No
HMI CELL_EVALUATION Sub-syste BSC Cell Type Yes
Definition Handover cell evaluation process applied in the cell.
Coding rules 0: Order, 1: Grade
Mandatory rules --
Recommended --
rules
External --
comment
Logical CELL_LAYER_TYPE B11 Yes B12 Yes
name TRX nb No
HMI Cell Layer Sub-syste BSC Cell Type Yes
Definition Determines if the cell is processed as single cell, upper layer cell, lower layer or indoor layer cell.
Coding rules 0: Single cell, 1: Upper layer, 2: Lower layer, 3 : Indoor layer
Recommended The allowed layer configurations are: 1) Only single layer cells, 2) Upper layer cells + Indoor layer cells, 3) Upper layer cells + Lower layer cells, 4) Upper layer cells +
rules Lower layer cells + Indoor layer cells
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. The CELL_LAYER_TYPE parameter is not displayed as such to the O&M user.
Logical CELL_LAYER_TYPE(n) B11 Yes B12 Yes
name TRX nb No
HMI Cell Layer Sub-syste BSC Cell Type Yes
Definition Determines if the adjacent cell is processed as single cell, upper layer cell, lower layer or indoor
layer cell.
Coding rules 0: Single cell, 1: Upper layer, 2: Lower layer, 3 : Indoor layer
Recommended The allowed layer configurations are: 1) Only single layer cells, 2) Upper layer cells + Indoor layer cells, 3) Upper layer cells + Lower layer cells, 4) Upper layer cells +
rules Lower layer cells + Indoor layer cells
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. The CELL_LAYER_TYPE parameter is not displayed as such to the O&M user.
Logical CELL_PARAMETER_3G_TDD B11 Yes B12 Yes
name TRX nb No
HMI CELL_PARAMETER_3G_TDD Sub-syste BSC Cell Type No
name Instance 3G cell RMS No
Definition Cell information related to an external 3G TDD cell.
Coding rules Coded on 7 bits
Mandatory rules --
Recommended --
rules
comment - Parameter change: to be completed
Internal comment - This parameter is not used by BSS SW. It is defined as a provision for the MIB (following B11 RFD 250745 enhanced 2G to 3G TDD/FDD reselection).
- A coded default value is not needed since the operator cannot create a 3G TDD cell without configuring its cell parameter (no dummy value needed).
- Neither 2G to 3G TDD handover, nor The 3G TDD cell reselection with cell info is supported. So this parameter is currently not used.
Logical CELL_PARTITION_TYPE B11 Yes B12 Yes
name TRX nb No
HMI Cell Partition Sub-syste BSC Cell Type Yes
Definition Determines if the cell is concentric.
Coding rules 0: No partition, 1: Concentric

Must be equal to "Concentric" when FREQUENCY_RANGE = "EGSM-DCS1800" or "PGSM-DCS1800".
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. The CELL_PARTITION_TYPE parameter is not displayed as such to the O&M user.
Logical CELL_PARTITION_TYPE(n) B11 Yes B12 Yes
name TRX nb No
HMI Cell Partition Sub-syste BSC Cell Type Yes
Definition Determines if the adjacent cell is concentric.
Coding rules 0: No partition, 1: Concentric

Must be equal to "Concentric" when FREQUENCY_RANGE = "EGSM-DCS1800" or "PGSM-DCS1800".
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. The CELL_PARTITION_TYPE parameter is not displayed as such to the O&M user.
Logical CELL_RANGE (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Cell Range Sub-syste BSC Cell Type Yes
Definition Determines if the cell belongs to an extended cell.
Coding rules 0: Normal cell, 1: Outer cell, 2: Inner cell
Mandatory rules CELL_RANGE(BSC) = CELL_RANGE(MFS)

Shall be consistent with CELL_TYPE.
A couple of mate cells (Extended inner + extended outer) shall have the same LAC (respectively RAC when they are PS capable).
Recommended --
rules
External --
comment
Internal comment The CELL_RANGE parameter is not displayed as such to the O&M user.
Logical CELL_RANGE(n) (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Cell Range Sub-syste BSC Cell Type Yes
Definition Determines if the adjacent cell belongs to an extended cell, or is a GAN cell.
Coding rules 0: Normal cell, 1: Outer cell, 2: Inner cell, 3: GAN cell
Mandatory rules CELL_RANGE(BSC) = CELL_RANGE(MFS)

Shall be consistent with CELL_TYPE(n).
Recommended --
rules
External The CELL_RANGE parameter is not displayed as such to the O&M user.
comment
Internal comment --
Logical CELL_RESELECT_HYSTERESIS B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_HYSTERESIS Sub-syste BSC Cell Type No
Definition Level hysteresis for cell reselection applied when the new cell is in a different location area or, for a GPRS MS, in a different routing area, or when a GPRS MS is in GMM
ready state.
Coding rules step size = 2dB; coded on 3 bits (000 : 0 dB, 111 : 14 dB)
Mandatory rules --
Recommended --
rules
External If the VGCS is licensed, the parameter is modifiable only via the provisioning context of the OMC.
comment
Internal comment --
Logical CELL_RESELECT_HYSTERESIS(n) B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_HYSTERESIS(n) Sub-syste BSC Cell Type No
Definition Level hysteresis for cell reselection applied when the new cell is in a different location area.
Rec ref. None Domai VGCS Min value 0 Coded Min 0
Coding rules step size = 2dB; coded on 3 bits (000 : 0 dB, 111 : 14 dB)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CELL_RESELECT_OFFSET (BSC) B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_OFFSET Sub-syste BSC Cell Type No
Definition Permanent offset to C2 criterion.
Coding rules step size = 2dB; coded on 6 bits (000000:0 dB, 111111 : 126 dB)
Mandatory rules CELL_RESELECT_OFFSET (MFS) = CELL_RESELECT_OFFSET (BSC)
Recommended --
rules
External --
comment
Logical CELL_RESELECT_OFFSET(n)(BSC) B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_OFFSET Sub-syste BSC Cell Type No
Mandatory rules CELL_RESELECT_OFFSET(n)(MFS) = CELL_RESELECT_OFFSET (n)(BSC)
Recommended --
rules
External --
comment
Logical CELL_RESELECT_PARAM_IND B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_PARAM_IND Sub-syste BSC Cell Type No
Definition Indicates to the MS if parameters for C2 reselection criterion are broadcast.
Coding rules 0: not present, 1: present
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS. This parameter was explicitly defined in GSM 05.08 up to version V8.3.1 of Release 99 (replaced by sentences in
subsequent versions)
Logical CGI_3G_REQD B11 Yes B12 Yes
name TRX nb No
HMI CGI_3G_REQUIRED Sub-syste BSC Cell Type No
Definition Controls the format of an external 3G cell identification, sent to the MSC on the A interface for 2G to 3G handover.
Category Network (CDE) OMC-R access Displayed Type Flag Unit None
Coding rules 0: CGI not used, 1: CGI used
Mandatory rules --
Recommended Alcatel-Lucent recommend to set the CGI_3G_REQD parameter to 1 provided that the MSC supports the CGI format. The CGI_3G_REQD parameter shall be set to 1 if
rules the operator wants to allow inter-PLMN 2G to 3G handovers. If this parameter needs to be changed, it is recommended to change it during a migration phase to avoid
any additional Telecom outage.
External Depends on MSC Type. The value indicated here is for implementation purposes.
comment
Internal comment - If CGI_3G_REQD = 1 then a 3G cell will be identified on A interface with MCC_3G + MNC_3G + LAC_3G + RNC_ID_3G
Else with LAC_3G + RNC_ID_3G
- Only the 2G to 3G FDD handover is supported
Logical CGI_REQD B11 Yes B12 Yes
name TRX nb No
HMI CGI_REQUIRED Sub-syste BSC Cell Type No
Definition Controls format of cell identifications sent to the MSC.
Category Network (CDE) OMC-R access Displayed Type Flag Unit None
Coding rules 0: CGI not used, 1: CGI used
Mandatory rules --
Recommended Alcatel recommend to set the CGI_REQD parameter to 1 provided that the MSC supports the CGI format. The CGI_REQD parameter shall be set to 1 if the operator
rules wants to allow inter-PLMN 2G to 2G handovers. If this parameter needs to be changed, it is recommended to change it during a migration phase to avoid any additional
Telecom outage.
External Depends on MSC Type. The value indicated here is for implementation purposes.
comment
Internal comment --
Logical CI (BSC) B11 Yes B12 Yes
name TRX nb No
HMI CI Sub-syste BSC Cell Type No
Definition Cell Identity.
Coding rules --
Mandatory rules LAC and CI can not be equal to 65535 at the same time
Equal to CI (MFS)
Recommended --
rules
comment
Internal comment --
Logical CI(n) (BSC) B11 Yes B12 Yes
name TRX nb No
HMI CI Sub-syste BSC Cell Type No
Definition Cell Identity of adjacent cell.
Coding rules --
Equal to CI(n)(MFS)
Recommended --
rules
comment
Internal comment --
Logical CI_3G B11 Yes B12 Yes
name TRX nb No
HMI CI_3G Sub-syste BSC Cell Type No
Definition This parameter indicates the Cell Identifier of an external 3G (FDD or TDD) cell as defined in 3GPP TS 25.401.
Spec ref. Handover Management Coded Max 65535
Coding rules Binary value on 16 bits
Mandatory rules (MCC_3G, MNC_3G, RNC_ID_3G and CI_3G) shall together uniquely identify a 3G cell
Recommended --
rules
External Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
comment
Internal comment - A coded default value is not needed since the operator cannot create a 3G cell without configuring its CellId (no dummy value needed).
Logical CI_LTE B11 Yes B12 Yes
name TRX nb No
HMI CI_LTE Sub-syste BSC Cell Type No
Definition This parameter indicates the Cell Identifier of an external LTE (FDD or TDD) cell as defined in 3GPP TS 36.300.
Category Site (CAE) OMC-R access Set by Create Type Number Unit None
Coding rules Binary value on 28 bits is expanded to 32 bits (with the four Most Significant Bits set to 1).
Mandatory rules (MCC_LTE, MNC_LTE and CI_LTE) shall together uniquely identify a LTE cell inside the OMC
Recommended --
rules
External - The CI_LTE is equivalent to the long/standard eNode-B Id.
comment - Parameter available on BSC Evolution only.
Internal comment - A coded default value is not needed since the operator cannot create a LTE cell without configuring its CellId (no dummy value needed).
Logical CI_SI B11 Yes B12 Yes
name TRX nb No
HMI CI_SI Sub-syste BSC Cell Type No
Definition Specific Cell Identity to be broadcasted in the SI3 and SI6 messages instead of the value of the other O&M parameter CI.
Coding rules When set to 0, it indicates that the feature is de-activated, i.e the existing CI is sent in SI3 and SI6 messages
Mandatory rules --
Recommended --
rules
External Parameter change: no impact on the telecom service, on going traffic is not disrupted. But any modification impacts System Information Broadcasting. Change applied
comment immediately after modification, in broadcasted SI3 messages and in dedicated SI6 messages of the current calls.
Internal comment --
Logical CIC B11 Yes B12 Yes
name TRX nb No
HMI Circuit Identity Code Sub-syste BSC Cell Type No
name Instance A ch RMS No
Definition Circuit Identity Code of an A interface circuit.
Category Site (CAE) OMC-R access Displayed Type Reference Unit None
Coding rules Coded over 16 bits: top 11 bits = pcm number, remaining 5 bits = TS number
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical COUNT_DECR B11 Yes B12 Yes
name TRX nb No
HMI COUNT_DECR Sub-syste BSC Cell Type No
Definition Stepsize by which the leaky bucket counter used during the reaction to TCU overload is decremented upon T_COUNT_I expiry.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical COUNT_I_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI COUNT_I_THRESHOLD Sub-syste BSC Cell Type No
Definition Leaky bucket counter threshold used to trigger defense actions upon TCU overload.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical COUNT_INCR_1 B11 Yes B12 Yes
name TRX nb No
HMI COUNT_INCR_1 Sub-syste BSC Cell Type No
Definition Stepsize by which the leaky bucket counter used during the reaction to TCU overload is incremented upon TCU overload level 1.
Coding rules --
Mandatory rules --
Recommended COUNT_INCR_1 <= COUNT_INCR_2

rules
External --
comment
Internal comment --
Logical COUNT_INCR_2 B11 Yes B12 Yes
name TRX nb No
HMI COUNT_INCR_2 Sub-syste BSC Cell Type No
Definition Stepsize by which the leaky bucket counter used during the reaction to TCU overload is incremented upon TCU overload level 2.
Coding rules --
Mandatory rules --
Recommended COUNT_INCR_2 >= COUNT_INCR_1

rules
External --
comment
Internal comment --
Logical CRC_MON B11 Yes B12 Yes
name TRX nb No
HMI CRC_MON Sub-syste BSC Cell Type No
Definition Time in which CRC_TR is to be reached to report an alarm. On timeout, the CRC error counter is reset.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CRC_TR B11 Yes B12 Yes
name TRX nb No
HMI CRC_TR Sub-syste BSC Cell Type No
Definition CRC error threshold for alarm detection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical DEFAULT_PRIORITY_3G B11 Yes B12 Yes
name TRX nb No
HMI DEFAULT_PRIORITY_3G Sub-syste BSC Cell Type No
Definition Default priority associated to any UARFCN not explicitely broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Coding rules step size = 1
0 is the lowest priority,
7 the highest
Mandatory rules The DEFAULT_PRIORITY_3G of a given BSS shall be different from any priority (GERAN_PRIORITY) of its related 2G cells (which has at least one neighbour 3G or LTE
cell for reselection), and different from any priority (PRIORITY_3G and PRIORITY_LTE) of all those target neighbour 3G and LTE cells for reselection.
Recommended --
rules
External - Parameter available on BSC Evolution only.
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. But any modification impacts System Information Broadcasting. Change applied
immediately after modification, in broadcasted SI2quater messages and in dedicated Packet Measurement Order messages of the current calls.
Internal comment --
Logical DEFAULT_QRXLEVMIN_3G B11 Yes B12 Yes
name TRX nb No
HMI DEFAULT_QRXLEVMIN_3G Sub-syste BSC Cell Type No
Definition Default minimum received level associated to any UARFCN not explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Category Site (CAE) OMC-R access Changeable Type Number Unit dBm
Rec ref. 3GPP TS 45.008 Domai 2G-LTE Min value -119 Coded Min 0
n Max value -57 Coded Max 31
Coding rules Coded_value = (dBm + 119) / 2, step size = 2 dBm
Mandatory rules --
Recommended --
rules
Internal comment --
Logical DEFAULT_THRESH_3G B11 Yes B12 Yes
name TRX nb No
HMI DEFAULT_THRESH_3G Sub-syste BSC Cell Type No
Definition Default threshold associated to any UARFCN not explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Coding rules Coded_value = dB / 2, step size = 2 dB
Mandatory rules --
Recommended --
rules
Internal comment --
Logical DELTA_DEC_HO_margin B11 Yes B12 Yes
name TRX nb No
HMI DELTA_DEC_HO_MARGIN Sub-syste BSC Cell Type Yes
Definition Correction factor favouring handover cause Power budget when traffic is high in the serving cell and low in neighbour cell(s).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical DELTA_INC_HO_margin B11 Yes B12 Yes
name TRX nb No
HMI DELTA_INC_HO_MARGIN Sub-syste BSC Cell Type Yes
Definition Correction factor penalizing handover cause Power budget when traffic is low in the serving cell and high in neighbour cell(s).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical DELTA_SCPIR_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI DELTA_SCPIR_VAMOS_PAIRING Sub-syste BSC Cell Type No
Definition This parameter represents the maximum deviation of the difference between the average receive DL level of two MSs allowing them to be VAMOS paired together on the
same TCH channel (with respect to the minimum and maximum values of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for both
MSs).
Coding rules Step size = 2 dB
0: -10dB; 1: -8dB; 2: -6dB; 3: -4dB; 4: -2dB; 5: 0dB; 6: +2dB; 7: +4dB; 8: +6dB; 9: +8dB; 10: +10dB
Mandatory rules --
Recommended - A positive value means that the pairing algorithm allows the pairing of 2 MSs in VAMOS mode, when the difference of their respective DL RXLEV is higher than the
rules maximum SCPIR (SCPIRhigh), or lower than the minimum SCPIR (SCPIRlow). The initial SCPIR is forced anyway to fulfil the SCPIRlow/high conditions.
- A negative value means that the 2 MSs shall only be in optimal radio conditions to be paired together in VAMOS mode. The initial SCPIR will always be lower than
SCPIRhigh and higher than SCPIRlow.

Internal comment --
Logical DL_DTX_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI DL_DTX_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition This flag enables / disables the use of downlink DTX for AMR-WB GMSK speech calls.
Spec ref. DTX functional specification Coded Max 1
Coding rules 0 : DL DTX for AMR-WB GMSK disabled,
1 : DL DTX for AMR-WB GMSK enabled
Mandatory rules --
Recommended - The value 1 is recommended when EN_TFO_AMR_WB =1

rules - If there are some MC modules handled by the BSC for which dynamic power allocation is applied (cf. BOP), then it is recommended to enable the use of downlink
DTX, so as to limit the potential degradations during the downlink transmissions on the TSs of the MC modules.
- When EN_AUP_OVER_IP is enabled and the operator wants the Downlink DTX to be managed through the Core Network, then DL_DTX_AMR_WB_GMSK shall be
enabled.
External --
comment
Internal comment This parameter is used to set the value of the DTX field in cell Options IE in SYSTEM INFORMATION TYPE 6 in some cases
Logical DOWNLINK_DTX_ENABLE B11 Yes B12 Yes
name TRX nb No
HMI Downlink DTX Sub-syste BSC Cell Type No
Definition This flag defines if downlink DTX is allowed for FR and EFR calls.
Coding rules 0: DTX not allowed, 1: DTX allowed
Mandatory rules --
Recommended - should be enabled when EN_TFO = 1

- When EN_AUP_OVER_IP is enabled and the operator wants the Downlink DTX to be managed through the Core Network, then DOWNLINK_DTX_ENABLE shall be
enabled.
External --
comment
Internal comment --
Logical Downlink_DTX_enable_AMR_FR B11 Yes B12 Yes
name TRX nb No
HMI DOWNLINK_DTX_AMR_FR Sub-syste BSC Cell Type No
Definition This flag enables / disables the use of downlink DTX for AMR-NB FR speech calls.
Coding rules 0 : DL DTX for AMR FR disabled, 1 : DL DTX for AMR FR enabled
Mandatory rules --
Recommended - The value 1 is recommended when EN_TFO_AMR_NB =1

- When EN_AUP_OVER_IP is enabled and the operator wants the Downlink DTX to be managed through the Core Network, then Downlink_DTX_enable_AMR_FR shall
be enabled.
External --
comment
Internal comment --
Logical Downlink_DTX_enable_AMR_HR B11 Yes B12 Yes
name TRX nb No
HMI DOWNLINK_DTX_AMR_HR Sub-syste BSC Cell Type No
Definition This flag enables / disables the use of downlink DTX for AMR-NB HR speech calls.
Coding rules 0 : DL DTX for AMR HR disabled, 1 : DL DTX for AMR HR enabled
Mandatory rules --
Recommended - The value 1 is recommended when EN_TFO_AMR_NB =1

- When EN_AUP_OVER_IP is enabled and the operator wants the Downlink DTX to be managed through the Core Network, then Downlink_DTX_enable_AMR_HR shall
be enabled.
External --
comment
Internal comment --
Logical Downlink_DTX_enable_HR B11 Yes B12 Yes
name TRX nb No
HMI DOWNLINK_DTX_HR Sub-syste BSC Cell Type No
Definition This flag enables / disables the use of downlink DTX for HR speech calls.
Coding rules 0 : DL DTX for HR disabled, 1 : DL DTX for HR enabled
Mandatory rules --
Recommended - should be enabled when EN_TFO = 1

- When EN_AUP_OVER_IP is enabled and the operator wants the Downlink DTX to be managed through the Core Network, then Downlink_DTX_enable_HR shall be
enabled.
External --
comment
Internal comment --
Logical DPC B11 Yes B12 Yes
name TRX nb No
HMI MSC Signalling Point Code Sub-syste BSC Cell Type No
Definition Signalling Point Code of the MSC.
Rec ref. ITU-T Q.704 Domai GSM Min value 0 Coded Min 0
Spec ref. (SS7 parameter) Coded Max 16383
Mandatory rules --
Recommended --
rules
External - Default value depends on configuration. The value indicated here is for implementation purposes.
comment - Significant only if EN_ASIG_OVER_IP is set to FALSE.
Internal comment - Must be equal to OPC and SSF used by MSC.
- With the A Signalling Over IP feature (and Aflex anticipation), DPC has been replaced by MSC_SPC
Logical DRX_TIMER_MAX (BSC) B11 Yes B12 Yes
name TRX nb No
HMI DRX_TIMER_MAX Sub-syste BSC Cell Type No
Definition Maximum value allowed for the MS to request for non-DRX mode after packet transfer mode.
Category Site (CAE) OMC-R access Changeable Type Number Unit sec
Coding rules Radio coding :Possible values : 0, 1, 2, 4, 8, 16, 32, 64 respectively binary coded as 000, 001, , 111
ONLY THE VALUES 0, 1, 2 AND 4 ARE POSSIBLE in ALCATEL BSS.
Mandatory rules Equal to DRX_TIMER_MAX (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical DTX_INDICATOR (BSC) B11 Yes B12 Yes
name TRX nb No
HMI (Not applicable) Sub-syste BSC Cell Type No
Definition Controls uplink DTX usage for GSM phase 1 MS.
Coding rules coded over 2 bits. 0: MS may use uplink DTX, 1: MS shall use uplink DTX, 2: MS shall not use uplink DTX
Mandatory rules Equal to DTX_INDICATOR (MFS)
Recommended --
rules
External DTX_INDICATOR calculated from DTX_INDICATOR_FR
comment
Internal comment This parameter is used to set the value of the DTX field in cell Options (BCCH) IE in SYSTEM INFORMATION TYPE 3 and in cell Options (SACCH) IE in SYSTEM
INFORMATION TYPE 6 in some cases. The DTX_INDICATOR (BSC) parameter is not displayed as such to the O&M user.
Logical DTX_INDICATOR_SACCH B11 Yes B12 Yes
name TRX nb No
HMI (Not applicable) Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Controls uplink DTX usage for GSM phase 2 MS. Applies for all codec types except AMR-NB and AMR-WB.
Coding rules coded over 3 bits. The meaning of this parameter depends on the allocated channel rate
for TCH/F 0=may, 1=shall, 2=shall not, 3=shall, 4=may, 5=shall, 6=shall not, 7=may
for TCH/H 0=shall not, 1=shall not, 2=shall not, 3=may, 4=may, 5=shall, 6=shall, 7= shall
Mandatory rules --
Recommended --
rules
External DTX_INDICATOR_SACCH calculated from DTX_INDICATOR_FR and DTX_INDICATOR_HR (see coding rules).
comment
Internal comment This parameter is used to set the value of the DTX field in cell Options IE in SYSTEM INFORMATION TYPE 6 in some cases. The DTX_INDICATOR_SACCH
parameter
is not displayed as such to the O&M user.
Logical DTX_INDICATOR_SACCH_AMR B11 Yes B12 Yes
name TRX nb No
HMI (Not applicable) Sub-syste BSC Cell Type No
Definition Controls uplink DTX usage for GSM phase 2 MS. Applies only to AMR-NB FR and AMR-NB HR.
Coding rules coded over 3 bits. The meaning of this parameter depends on the allocated channel rate
for TCH/F (AMR FR) 0=may, 1=shall, 2=shall not, 3=shall, 4=may, 5=shall, 6=shall not, 7=may
for TCH/H (AMR HR) 0=shall not, 1=shall not, 2=shall not, 3=may, 4=may, 5=shall, 6=shall, 7= shall
Mandatory rules --
Recommended --
rules
External DTX_INDICATOR_SACCH_AMR is calculated from DTX_INDICATOR_FR_AMR and DTX_INDICATOR_HR_AMR (see coding rules).
comment
Internal comment This parameter is used to set the value of the DTX field in cell Options IE in SYSTEM INFORMATION TYPE 6 in some cases. The DTX_INDICATOR_SACCH_AMR
parameter is not displayed as such to the O&M user.
Logical DTX_INDICATOR_SACCH_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI DTX_INDICATOR_SACCH_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition Controls uplink DTX usage for GSM phase 2 MS. Applies only to AMR-WB GMSK.
Category Site (CAE) OMC-R access Changeable Type Enumerated Unit None
Coding rules 0= the MS may use UL DTX for AMR-WB GMSK,
1= the MS shall use UL DTX for AMR-WB GMSK,
2=the MS shall not use UL DTX for AMR-WB GMSK
Mandatory rules --
Recommended The value 1 is recommended when EN_TFO_AMR_WB =1

rules
External --
comment
Internal comment This parameter is used to set the value of the DTX field in cell Options IE in SYSTEM INFORMATION TYPE 6 in some cases.
Logical DWELL_TIME_STEP B11 Yes B12 Yes
name TRX nb No
HMI DWELL_TIME_STEP Sub-syste BSC Cell Type No
Definition Step value for the modification (increasing or decreasing) of MIN_DWELL_TIME.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical E1_MTU B11 Yes B12 Yes
name TRX nb No
HMI E1_MTU Sub-syste BSC Cell Type No
Definition MTU used in DL by the TP board of the BSC and in UL by the BTS (SUM) for IPoverE1 link.
Category Site (CAE) OMC-R access Changeable Type Number Unit byte
Coding rules Step size = 100 bytes
Mandatory rules E1_MTU >= IPGCH_PACKET_SIZE
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML.
- In DL, if the TP receives an IP packet (with priority 1..3) for which the size (including IP header) is > E1_MTU, this packet is redirected to the OBC to be fragmented
by the IP stack of the TP. Same kind of mechanism is performed in UL by the SUM. Packets with priority 0 (speech) are not fragmented.
Logical EC B11 Yes B12 Yes
name TRX nb No
HMI EMERGENCY_CALL Sub-syste BSC Cell Type No
Definition Indicates if Emergency calls are allowed for all access classes or only for access classes 11 to 15.
Coding rules 0: all access classes, 1: access classes 11 to 15 only
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in SYSTEM INFORMATION messages
Logical EC_BAR B11 Yes B12 Yes
name TRX nb No
HMI AUTO_BAR_EC Sub-syste BSC Cell Type No
Definition This flag enables/disables automatic barring of Emergency Class.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ECSC B11 Yes B12 Yes
name TRX nb No
HMI ECSC Sub-syste BSC Cell Type No
Definition Indicates to the MS whether or not early sending of CLASSMARK CHANGE is allowed.
Coding rules 0: early sending not allowed, 1: early sending allowed
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in SYSTEM INFORMATION messages. Coded in the software.
Logical EDR_ASSIGN_FAIL_CAUSE B11 Yes B12 Yes
name TRX nb No
HMI EDR_ASSIGN_FAIL_CAUSE Sub-syste BSC Cell Type No
Definition This parameter determines the cause filled in ASSIGNMENT FAILURE sent in case of External Directed Retry.
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment This parameter is meaningful only if EDR_SEND_ASSIGN_FAIL = 1.
Logical EDR_MSG_ORDER B11 Yes B12 Yes
name TRX nb No
HMI EDR_MSG_ORDER Sub-syste
BSC Cell Type No
name InstanceBSC RMS No
Definition This parameter determines the order of transmission of ASSIGNMENT FAILURE and HANDOVER REQUIRED on the A interface in case of an External Directed Retry.
Coding rules 0: Ass Failure before HO Reqd, 1: Ass Failure after HO Reqd
Mandatory rules --
Recommended --
rules
comment
Internal comment This parameter is meaningful only if EDR_SEND_ASSIGN_FAIL = 1.
Logical EDR_QUEUING_MAINTAINED B11 Yes B12 Yes
name TRX nb No
HMI EDR_QUEUING_MAINTAINED Sub-syste BSC Cell Type No
Definition This flag indicates whether or not Assignment Request is maintained in queue during External Directed Retry attempt.
Coding rules 0: Request not maintained in queue, 1: Request maintained in queue
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical EDR_SEND_ASSIGN_FAIL B11 Yes B12 Yes
name TRX nb No
HMI EDR_SEND_ASSIGN_FAIL Sub-syste BSC Cell Type No
Definition This flag indicates whether ASSIGNMENT FAILURE is sent to the MSC in case of External Directed Retry.
Coding rules 0: Assignment Failure not sent, 1: Assignment Failure sent
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical EFR_ENABLED B11 Yes B12 Yes
name TRX nb No
HMI EFR_ENABLED Sub-syste BSC Cell Type No
Definition This flag indicates whether the operation of enhanced full rate (EFR) is allowed in the cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EGSM_RR_ALLOC_STRATEGY B11 Yes B12 Yes
name TRX nb No
HMI EGSM_RR_ALLOC_STRATEGY Sub-syste BSC Cell Type No
Definition Defines if the G1 non-capable MS is supported or not in the network
Category Network (CDE) OMC-R access Displayed Type Number Unit None
Coding rules 0: G1 non-capable MS-s are only supported in the cells where the BCCH is not configured on the G1 band (i.e. BCCH is configured on PGSM band or on DCS1800
band).
1: G1 non-capable MS-s are not supported in any cell that contains at least one G1 TRX of the network (Note these MS-s are still supported in other cells).
Mandatory rules When EGSM_RR_ALLOC_STRATEGY is set to 0, if the BCCH is not configured on the G1 band (i.e. BCCH is configured on PGSM band or on DCS1800 band), then:
1) the OMC-R does not allow the operator to define the CCCH, SDCCH and CBCH on a G1 TRX.
2) TRX_PREF_MARK must be <> 0 for a hopping G1 TRX.
Recommended --
rules
External --
comment
Internal comment --
Logical EN_2G_3G_HO_NO_SERVICE_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_2G_3G_HO_NO_SERVICE_HO Sub-syste BSC Cell Type No
Definition Allows handovers towards 3G cells for a given MS when I.E. Service Handover is missing and the load in the serving cell is high (see THR_CELL_LOAD_3G_REQ)
Coding rules 0 : disable, 1 : enable
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_2G_TO_3G_CELL_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_2G_TO_3G_CELL_RESELECTION Sub-syste BSC Cell Type No
Definition Enables/Disables the GSM to UTRAN FDD cell reselections and defines the 3G search activation mode for MS in GMM Ready state. The adjacent UARFCNs can be
configured either at BSS level (FDD_ARFCN_LIST), or, exclusively, at 3G cell level (ARFCN_3G).
Those UARFCNs are used in the blind search method.
Coding rules 0: Disabled
1: Enabled with 3G search activated while the UE/MS is in GMM ready state,
2: Enabled with 3G search deactivated while the UE/MS is in GMM ready state.
3: Enabled with 3G search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1.
4: Enabled with 3G search activated with flexible priority while the UE/MS is in GMM ready state.
Mandatory rules - EN_2G_TO_3G_CELL_RESELECTION and EN_2G_TO_3GTDD_CELL_RESELECTION shall not be <> disabled at the same time.
- Configuration of FDD_ARFCN_LIST and 2G/LTE inter-working are exclusive: for a given BSS, we cannot have at the same time a valid FDD_ARFCN_LIST and, at
least, one 2G cell for which (EN_2G_TO_3G_CELL_RESELECTION <> 0) and (EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0 or
EN_2G_TO_LTETDD_CELL_RESELECTION <> 0).
- if both EN_2G_TO_3G_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, then they shall have the same value.
- It is not allowed to have EN_FAST_3G_RESELECTION = 1 and EN_2G_TO_3G_CELL_ RESELECTION = 0 and EN_2G_TO_3GTDD_CELL_ RESELECTION = 0.
- It is allowed to have EN_FAST_3G_RESELECTION = 3 only if (EN_2G_TO_3G_CELL_RESELECTION <> 0 and EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0) or
(EN_2G_TO_3G_CELL_RESELECTION <> 0 and
EN_2G_TO_LTETDD_CELL_RESELECTION <> 0) or (EN_2G_TO_3GTDD_CELL_RESELECTION <> 0 and
EN_2G_TO_LTETDD_CELL_RESELECTION <> 0)
- if both EN_2G_TO_3G_CELL_RESELECTION and EN_2G_TO_LTEFDD_CELL_RESELECTION are <> disabled, then they shall have the same value.
Recommended Value 3 and 4 should be used only in case of good 3G FDD coverage.
rules
External - If the NETWORK_CONTROL_ORDER is set to NC2 mode of operation for R99 onwards MS or NC2 mode of operation for all MS, then the 3G search is
comment systematically deactivated when activating the NC2 mode through the Packet Measurement Order [NC2] message.
- If EN_2G_TO_3G_CELL_RESELECTION = "Enabled with 3G search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1", then the
3G search is activated even when activating the NC2 mode (the Packet Measurement Order [NC2] message will not be sent).
m
Internal comment - This parameter is available in the MFS through the BSCGP interface.
- The 3G FDD cell reselection based on the UARFCN (also called blind reselection) is supported. template
- The 3G FDD cell reselection based on the UARFCN+cell information is not supported.
- 3G TDD and LTE FDD are mutually exclusive.
Logical EN_2G_TO_3GTDD_CELL_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_2G_TO_3GTDD_CELL_RESELECTION Sub-syste BSC Cell Type No
Definition Enables/Disables the GSM to UTRAN TD-SCDMA cell reselections and defines the 3G search
activation mode for MS in GMM Ready state. The adjacent UARFCNs can be configured
either at BSS level (TDD_ARFCN_LIST), or, exclusively, at 3G cell level (ARFCN_3G).
Those UARFCNs are used in the blind search method.
Coding rules 0: Disabled
1: Enabled with 3G search activated while the UE/MS is in GMM ready state,
2: Enabled with 3G search deactivated while the UE/MS is in GMM ready state.
3: Enabled with 3G search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1.
4: Enabled with 3G search activated with flexible priority while the UE/MS is in GMM ready state.
Mandatory rules - EN_2G_3G_CELL_RESELECTION and EN_2G_3GTDD_CELL_RESELECTION shall not be <>disabled at the same time
- EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTEFDD_CELL_RESELECTION shall not be <> disabled at the same time.
- Configuration of TDD_ARFCN_LIST and 2G/LTE inter-working are exclusive: for a given BSS, we cannot have at the same time a valid TDD_ARFCN_LIST and, at
least, one 2G cell where both EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled.
- if both EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, then they shall have the same value.
- It is not allowed to have EN_FAST_3G_RESELECTION = 1 and EN_2G_TO_3G_CELL_ RESELECTION = 0 and EN_2G_TO_3GTDD_CELL_ RESELECTION = 0.
- It is allowed to have EN_FAST_3G_RESELECTION = 3 only if (EN_2G_TO_3G_CELL_RESELECTION <> 0 and
EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0) or (EN_2G_TO_3G_CELL_RESELECTION <> 0 and
- For a given 2G cell, where both EN_2G_TO_3GTDD_CELL_RESELECTION and
EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, if FAKE_FDD_MANAGEMENT = 1 then there shall be no more than 8 distinct ARFCN_3G (TDD) among
all the
neighbour 3G TDD cells target for reselection and there shall be no more than 3 distinct ARFCN_LTE(TDD) among all the neighbour LTE TDD cells target for
reselection.
Recommended Value 3 and 4 should be used only in case of good 3G TDD coverage.
rules
External - If EN_2G_TO_3GTDD_CELL_RESELECTION < 3, and If the NETWORK_CONTROL_ORDER is set to NC2 mode of operation for R99 onwards MS or NC2 mode of
comment operation for Rel4 onwards MS or NC2 mode of operation for all MS, the 3G search is systematically deactivated when activating the NC2 mode through the Packet
Measurement Order [NC2] message. This 3G search deactivation is then performed independently of the value of the EN_2G_TO_3GTDD_CELL_RESELECTION
parameter. m
template
- The 3G TDD cell reselection based on the UARFCN (also called blind reselection) is supported.
- The 3G TDD cell reselection based on the UARFCN+cell information is not supported.
- 3G TDD and LTE FDD are mutually exclusive.
Logical EN_2G_TO_LTEFDD_CELL_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_2G_TO_LTEFDD_CELL_RESELECTION Sub-syste BSC Cell Type No
Definition Enables/Disables the GSM to E-UTRAN FDD cell reselection and defines the LTE search activation mode for MS in GMM Ready state. The adjacent EUARFCNs can be
configured at LTE cell level only (ARFCN_LTE).
Those EUARFCNs are used in the blind search method.
Rec ref. None Domai 2G-LTE Min value 0 Coded Min 0
Coding rules 0: Disabled,
1: Enabled with LTE search activated while the UE/MS is in GMM ready state,
2: Enabled with LTE search deactivated while the UE/MS is in GMM ready state,
3: Enabled with LTE search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1,
4: Enabled with LTE search activated with flexible priority while the UE/MS is in GMM ready state.
Mandatory rules - Configuration of FDD_ARFCN_LIST and 2G/LTE inter-working are exclusive: for a given BSS, we cannot have at the same time a valid FDD_ARFCN_LIST and, at
- EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTEFDD_CELL_RESELECTION shall not be <> disabled at the same time.
- EN_2G_TO_LTEFDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION shall not be <> disabled at the same time.
- It is not allowed to have EN_FAST_3G_RESELECTION = 2 and EN_2G_TO_LTEFDD_CELL_ RESELECTION = 0 and EN_2G_TO_LTETDD_CELL_RESELECTION =
0.
- It is allowed to have EN_FAST_3G_RESELECTION = 3 only if (EN_2G_TO_3G_CELL_RESELECTION <> 0 and
EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0) or (EN_2G_TO_3G_CELL_RESELECTION <> 0 and
- It is not allowed to have EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0 if the cell is owned by a BSC connected to a legacy MFS.
- if both EN_2G_TO_3G_CELL_RESELECTION and EN_2G_TO_LTEFDD_CELL_RESELECTION are <> disabled, then they shall have the same value.
Recommended Value 3 should be used only in case of good LTE FDD coverage.
rules
External - If EN_2G_TO_LTEFDD_CELL_RESELECTION < 3, and If the NETWORK_CONTROL_ORDER is set to NC2 mode of operation for R99 onwards MS or NC2 mode of
comment operation for Rel4 onwards MS or NC2 mode of operation for all MS, the LTE search is systematically deactivated when activating the NC2 mode through the Packet
Measurement Order [NC2] message. This LTE search deactivation is then performed independently of the value of the EN_2G_TO_LTEFDD_CELL_RESELECTION
parameter.
m
- The LTE FDD cell reselection based on the EUARFCN (also called blind reselection) is supported. template
- The LTE FDD cell reselection based on the EUARFCN+cell information is not supported.
- The second mandatory rule ensures that LTE FDD and 3G TDD are mutually exclusive.
Logical EN_2G_TO_LTETDD_CELL_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_2G_TO_LTETDD_CELL_RESELECTION Sub-syste BSC Cell Type No
Definition Enables/Disables the GSM to E-UTRAN TDD cell reselection and defines the LTE search activation mode for MS in GMM Ready state. The adjacent EUARFCNs can be
configured at LTE cell level only (ARFCN_LTE).
Those EUARFCNs are used in the blind search method.
Coding rules 0: Disabled,
1: Enabled with LTE search activated while the UE/MS is in GMM ready state,
2: Enabled with LTE search deactivated while the UE/MS is in GMM ready state,
3: Enabled with LTE search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1,
4: Enabled with LTE search activated with flexible priority while the UE/MS is in GMM ready state.
Mandatory rules - Configuration of FDD_ARFCN_LIST and 2G/LTE inter-working are exclusive: for a given BSS, we cannot have at the same time a valid FDD_ARFCN_LIST and, at
- EN_2G_TO_LTEFDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION shall not be <> disabled
at the same time.
- if both EN_2G_TO_3G_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, then they shall have the same value.
- if both EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, then they shall have the same value.
- It is not allowed to have EN_FAST_3G_RESELECTION = 2 and EN_2G_TO_LTEFDD_CELL_RESELECTION = 0 and EN_2G_TO_LTETDD_CELL_RESELECTION =
0.
- It is allowed to have EN_FAST_3G_RESELECTION = 3 only if (EN_2G_TO_3G_CELL_RESELECTION <> 0 and EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0) or
(EN_2G_TO_3G_CELL_RESELECTION <> 0 and EN_2G_TO_LTETDD_CELL_RESELECTION <> 0) or (EN_2G_TO_3GTDD_CELL_RESELECTION <> 0 and
- It is not allowed to have EN_2G_TO_LTETDD_CELL_RESELECTION <> 0 if the cell is owned by a BSC connected to a legacy MFS.
- For a given 2G cell, where both EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, if
FAKE_FDD_MANAGEMENT = 1 then there shall be no more than 8 distinct ARFCN_3G (TDD) among all the neighbour 3G TDD cells target for reselection and there
shall
be no more than 3 distinct ARFCN_LTE(TDD) among all the neighbour LTE TDD cells target for reselection.
Recommended Value 3 should be used only in case of good LTE TDD coverage.
rules
External - If EN_2G_TO_LTEFDD_CELL_RESELECTION < 3, and If the NETWORK_CONTROL_ORDER is set to NC2 mode of operation for R99 onwards MS or NC2 mode of
comment operation for Rel4 onwards MS or NC2 mode of operation for all MS, the LTE search is systematically deactivated when activating the NC2 mode through the Packet
Measurement Order [NC2] message. This LTE search deactivation is then performed independently of the value of the EN_2G_TO_LTEFDD_CELL_RESELECTION
parameter. m
template
- The LTE TDD cell reselection based on the EUARFCN (also called blind reselection) is supported.
- The LTE TDD cell reselection based on the EUARFCN+cell information is not supported.
Logical EN_3G_DIVERSITY(FDD) B11 Yes B12 Yes

name TRX nb No
HMI EN_3G_DIVERSITY Sub-syste BSC Cell Type No
Definition This parameter indicates if diversity is applied for an external 3G FDD cell.
Coding rules 1 bit:
0 diversity is not applied,
1 diversity is applied
Mandatory rules --
Recommended --
rules
External - Significant only if RAT_3G is FDD.
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Internal comment --
Logical EN_3G_DIVERSITY(TDD) B11 Yes B12 Yes
name TRX nb No
HMI EN_3G_DIVERSITY Sub-syste BSC Cell Type No
Definition This parameter indicates if the Space Code Transmit Diversity (diversity TDD bit) is applied in an external 3G TDD cell.
Coding rules 1 bit:
0 diversity is not applied,
1 diversity is applied
Mandatory rules --
Recommended --
rules
Logical EN_3G_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_3G_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the 2G to 3G FDD handover.
Mandatory rules For Evolium serving cell :

cells for handover.
Recommended --
rules
comment
Internal comment --
Logical EN_4_DR_TRE_PER_TCU B11 Yes B12 Yes
name TRX nb No
HMI EN_4_DR_TRE_PER_TCU Sub-syste BSC Cell Type No
Definition Defines if the limitation of TRE is static or dynamic.
For static limitation only Nb FR TRE + 2 x DR TRE < 200 is allowed.
For dynamic limitation only Nb TRE < 200 is allowed.
Coding rules 0: static
1:dynamic
Mandatory rules --
Recommended - Alcatel-Lucent recommends setting this parameter consistently with the RSL configuration. Once dynamic, the operator shall not set it to static again, with more than
rules 100 RSLs configured in Dual Rate per CCP; otherwise the CCP may appear as overloaded.
External - Parameter change: after each parameter change, it is advised to remap-bts-on-ccp.
comment
Internal comment feature "Removal of HR impact"
in B9, TCU can serve 4 FR TREs or 2 DR TREs
in B10, dynamic, TCU serves 4 TREs (FR or HR)
Logical EN_A_FLEX B11 Yes B12 Yes
name TRX nb No
HMI EN_A_FLEX Sub-syste BSC Cell Type No
Definition Enables/disables the support of the "Aflex" feature (for signaling traffic). The Aflex feature allows a BSS to be connected to more than one MSC.
Mandatory rules EN_A_FLEX is enabled only if EN_ASIG_OVER_IP is enabled

When EN_A_FLEX is enabled, up to 16 MSCs can be connected to one BSC.
When EN_A_FLEX is disabled, only one MSC can be connected to one BSC.
Recommended --
rules
External - Aflex function is available on BSC Evolution only.
comment - Support of A-Flex by the MSC server is mandatory.
- Support of Virtual MGW feature by the Media Gateway is mandatory.
Parameter change: Before disabling the feature from the BSC side, the operator must delete all the excessive MSCs (except one, ie no more than one MSC connected
to the BSC).
Before enabling the feature, the operator must have configured the NULL_NRI and NRI_LENGTH parameters. Then the Aflex feature deals with the unlocked MSC(s).
Internal comment - it is an optional feature

- up to MAX_NB_MSC (BOP) = 16 MSC can be connected to one BSC
Logical EN_A53_PREF_ALLOC_STRATEGY B11 Yes B12 Yes
name TRX nb No
HMI EN_A53_PREF_ALLOC_STRATEGY Sub-syste BSC Cell Type No
Definition Enables/disables the support of the "A5/3 enhanced radio resource allocation" feature, which tends to favor the selection of a free and pure CS timeslot, on a TRX
supporting the A5/3 ciphering encryption algorithm, during the resource allocation processing for an A5/3 capable MS (and inversely on a TRX non supporting A5/3, when
the MS is not A5/3 capable). This feature applies to new CS call establishments and to incoming (internal or external) handovers.
Coding rules 0: disabled,
1: enabled
Mandatory rules - EN_A53_PREF_ALLOC_STRATEGY can be enabled, only if CELL_CIPH_SET allows the A5/3 usage in the cell.
- When EN_A53_PREF_ALLOC_STRATEGY is disabled, then EN_A53_PREF_ALLOC_STRATEGY_PS cannot be enabled.
Recommended --
rules
External - The present feature is automatically inhibited by the BSC when the concerned MS is G1 capable.
comment
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately on new CS call establishment requested after
modification
Internal comment - The A5/3 encryption is not supported by G3 TREs.
Logical EN_A53_PREF_ALLOC_STRATEGY_PS B11 Yes B12 Yes
name TRX nb No
HMI EN_A53_PREF_ALLOC_STRATEGY_PS Sub-syste BSC Cell Type No
Definition Enables/disables the support of the "A5/3 enhanced radio resource allocation" feature, which tends to favor the selection of a free and PS capable timeslot, on a TRX
supporting the A5/3 ciphering encryption algorithm, during the resource allocation processing for an A5/3 capable MS (and inversely on a TRX non supporting A5/3, when
the MS is not A5/3 capable). This feature applies to new CS call establishments and to incoming (internal or external) handovers.
Mandatory rules EN_A53_PREF_ALLOC_STRATEGY_PS can be enabled only if EN_A53_PREF_ALLOC_STRATEGY is already enabled.
Recommended --
rules
External - The present feature is automatically inhibited by the BSC when the concerned MS is G1 capable.
comment
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately on new CS call establishment requested after
modification
Internal comment - The A5/3 encryption is not supported by G3 TREs.
Logical EN_AMR_CA_FR_HR B11 Yes B12 Yes
name TRX nb No
HMI EN_AMR_CA_FR_HR Sub-syste BSC Cell Type No
Definition This flag enables/disables intracell HO for AMR-NB FR-to-HR channel adaptation (Handover Cause 27). According to the load of the serving cell (high or normal), the
handover is triggered with different thresholds values.
Mandatory rules EN_AMR_CA_FR_HR can be enabled only if {EN_AMR_FR=1 AND EN_AMR_HR=1}
Recommended --
rules
External - Significant if HO_INTRACELL_ALLOWED is enabled.
comment - When EN_TFO_AMR_NB is enabled in the cell, the cause 27 triggering will be automatically inhibited for the AMR-NB ongoing call with TFO (and uninhibited if TFO is
given up for any reason).
- When EN_AMR_CA_FR_HR_ONLY_WHEN_LOADED is enabled, then the cause 27 triggering under normal load is automatically inhibited.
- When MAX_TCH_HALF_RATE is reached, then the cause 27 triggering is inhibited in any cell of the BSS.
Internal comment --
Logical EN_AMR_CA_FR_HR_ONLY_WHEN_LOADED B11 Yes B12 Yes
name TRX nb No
HMI EN_AMR_CA_FR_HR_ONLY_WHEN_LOADED Sub-syste BSC Cell Type No
Definition This flag enables/disables intracell HO for AMR-NB FR-to-HR channel adaptation (Handover Cause 27) under high load only.
Coding rules 0: disabled
1: enabled
Mandatory rules EN_AMR_CA_FR_HR_ONLY_WHEN_LOADED can be enabled only if EN_AMR_CA_FR_HR =1
Recommended --
rules
External - When EN_AMR_CA_FR_HR_ONLY_WHEN_LOADED is enabled, then the cause 27 triggering under normal load is automatically inhibited (even if
comment EN_AMR_CA_FR_HR is enabled).
- When MAX_TCH_HALF_RATE is reached, then the cause 27 triggering is inhibited in any cell of the BSS.
Internal comment --
Logical EN_AMR_CA_HR_FR B11 Yes B12 Yes
name TRX nb No
HMI EN_AMR_CA_HR_FR Sub-syste BSC Cell Type No
Definition This flag enables/disables intracell HO for AMR-NB channel adaptation (Handover Cause 26).
Mandatory rules EN_AMR_CA_HR_FR can be enabled only if {EN_AMR_FR=1 AND EN_AMR_HR=1}
Recommended --
rules
External - Significant if HO_INTRACELL_ALLOWED is enabled.
comment - When EN_TFO_AMR_NB is enabled in the cell, the cause 26 triggering will be automatically inhibited for the AMR-NB ongoing call with TFO (and uninhibited if TFO is
given up for any reason).
Internal comment --
Logical EN_AMR_FR B11 Yes B12 Yes
name TRX nb No
HMI EN_AMR_FR Sub-syste BSC Cell Type No
Definition This flag controls whether or not AMR-NB full rate is allowed in the cell.
Coding rules 0: disabled; 1: enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_AMR_HR B11 Yes B12 Yes
name TRX nb No
HMI EN_AMR_HR Sub-syste BSC Cell Type No
Definition This flag controls whether or not AMR-NB half rate is allowed in the cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI EN_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition This flag controls whether or not AMR-WB GMSK is allowed in the cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment it is an optional feature
Logical EN_ASIG_OVER_IP B11 Yes B12 Yes
name TRX nb No
HMI EN_ASIG_OVER_IP Sub-syste BSC Cell Type No
Definition Enables/disables the support of "A signalling over IP"
Mandatory rules - EN_A_FLEX is enabled only if EN_ASIG_OVER_IP is enabled.

- EN_ASIG_OVER_IP can be enabled if, at least, one MSC SCTP endpoint has been configured.
- EN_AUP_OVER_IP can be enabled only if EN_ASIG_OVER_IP is enabled.
Recommended --
rules
comment
- Parameter change: A BSC reset procedure is needed, after modification, to resynchronize all the channels of the A interface. This BSC reset leads to a total outage
of several minutes. No telecom service is provided during this procedure.
Logical EN_ASSIGN_FAIL_CIC_USED_NO_ACTION B11 Yes B12 Yes
name TRX nb No
HMI EN_ASSIGN_FAIL_CIC_USED_NO_ACTION Sub-syste BSC Cell Type No
Definition In case of ASSIGNMENT FAILURE cause terrestrial circuit already allocated sent to the MSC, this flag indicates whether the BSC takes no action on the radio interface in
order to recover resource consistency with the MSC.
Spec ref. Call release Coded Max 1
Mandatory rules --
Recommended --
rules
External - Default value depends on MSC type
comment
- Parameter change: No impact on the telecom service, on going calls are not disrupted. Change applied immediately after modification
Internal comment - value 1 is compliant with 3GPP TS 48.008 = no action (ie. the call currently allocated is not released by the BSC).
Logical EN_AUP_OVER_IP B11 No B12 Yes
name TRX nb No
HMI EN_AUP_OVER_IP Sub-syste BSC Cell Type No
Definition Enables/disables the support of "A user plane over IP" in "Full AUPoIP" architecture, or in "Mixed IP/TDM A interface" architecture.
Mandatory rules - EN_AUP_OVER_IP can be enabled only if EN_ASIG_OVER_IP is enabled.

- EN_AUP_OVER_IP can be enabled only if EXT_HO_FORCED is disabled for all cells of the BSS.
And
AMR_HR_SUBSET = {1, 4, 5, 8, 13, 21, 29} when EN_AMR_HR is enabled in at least one cell of the BSS.
- EN_AUP_OVER_IP can be enabled in "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0) only if the Atermuxes linked to the MFS are GPRS-dedicated.
- EN_AUP_OVER_IP can be enabled in "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0) only without TFO (EN_TFO and EN_TFO_AMR_NB and
EN_TFO_AMR_WB shall be disabled)
- When the Abis/Ater flexibility is used, then EN_AUP_OVER_IP is enabled in "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0)
Recommended - Before enabling A user plane over IP, the operator must ensure that the BSS is connected to a NGN (MSC server and MGW) Core Network.
rules - When EN_AUP_OVER_IP is enabled and the operator wants the Downlink DTX to be managed through the Core Network, the following flags shall be enabled:
DL_DTX_AMR_WB_GMSK, DOWNLINK_DTX_ENABLE, Downlink_DTX_enable_AMR_FR, Downlink_DTX_enable_AMR_HR and Downlink_DTX_enable_HR.
External - Function available on BSC Evolution (with 2 TPGSM boards at least TPV3i3) only.
comment - Parameter change: the BSS-TEL is to be previously locked. This procedure leads the BSC to stop telecom activity and reject any new calls and wait for some
service.
Internal comment - it is an optional feature (TRX quantity controlled).
- DL DTX flag, sent by the MSC, remains unmanaged by the BSC, although the MGW managed it on AUPoIP.
Logical EN_BALANCED_CI B11 Yes B12 Yes
name TRX nb No
HMI EN_BALANCED_CI Sub-syste BSC Cell Type No
name Instance BSC RMS Yes
Definition This flag enables/disables to balance the C/I measure.
Spec ref. Radio Measurements Coded Max 1
Coding rules 0:disable, 1: enable
Mandatory rules --
Recommended --
rules
External Up to 16 instances of this parameter with different values can be defined. This allows to define "RMS templates" (see parameter RMS_template).
comment
Internal comment --
Logical EN_BETTER_ZONE_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_BETTER_ZONE_HO Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the detection of too high level in outer zone handover cause (cause 13).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where: CELL_PARTITION_TYPE = concentric. CT: Depends on Cell Type and BTS Type
Logical EN_BI-BAND_MS(n) B11 Yes B12 Yes
name TRX nb No
HMI EN_BI-BAND_MS(n) Sub-syste BSC Cell Type No
Definition This flag enables/disables the incoming handovers of bi-band MSs from the preferred band.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_BS_PC B11 Yes B12 Yes
name TRX nb No
HMI EN_BS_PC Sub-syste BSC Cell Type No
Definition This flag enables/disables BS Power Control.
1: enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_BSS_OVRL_CLASS_BAR B11 Yes B12 Yes
name TRX nb No
HMI AUTO_BAR_BSS_OVERLOAD Sub-syste BSC Cell Type No
Definition This flag enables/disables access class automatic barring upon BTS/BSC overload.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_BSS_PAGING_COORDINATION (BSC) B11 Yes B12 Yes
name TRX nb No
HMI EN_BSS_PAGING_COORDINATION Sub-syste BSC Cell Type No
Definition Enables/disables the CS paging coordination managed in the BSS for MS in Packet Transfer Mode.
Rec ref. None Domai GPRS Min value 0 Coded Min 0
Coding rules 0 : disabled, 1 : enabled
Mandatory rules - EN_BSS_PAGING_COORDINATION (BSC) = EN_BSS_PAGING_COORDINATION (MFS)

- can be enabled only if (network_operation_mode <> NMO I) and (round_trip_delay < 500 msec for all the cells of the BSS)
Recommended - if EN_BSS_PAGING_COORDINATION is set to enabled, it is highly recommended to set EN_RA_CAP_UPDATE to enabled.

rules - if EN_DTM is Enabled for at least one cell within the BSS it is highly recommended to activate CS Paging Coordination for the BSS, either through the Gs Interface
(network_operation_mode = NMO I) or by setting EN_BSS_PAGING_COORDINATION to Enabled (network_operation_mode <> NMO I).
- if a BSC is connected to a MFS but GPRS is disabled (EN_GPRS = false) for any cells of the BSS, it is recommended to set EN_BSS_PAGING_COORDINATION to
disabled for that BSS.
External The support of paging coordination in the BSS is not compatible with the "GPRS through satellite connection on Abis or Ater interface" feature.
comment
Logical EN_CIRCUIT_GROUP B11 Yes B12 Yes
name TRX nb No
HMI EN_CIRCUIT_GROUP Sub-syste BSC Cell Type No
Definition This flag enables/disables the sending of Circuit group messages.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_COMPRESSED_INTER_RAT_INFO B11 Yes B12 Yes
name TRX nb No
HMI EN_COMPRESSED_INTER_RAT_INFO Sub-syste BSC Cell Type No
Definition Allows sending by the MS of Compressed Inter-RAT HO information
Spec ref. Radio and link establishment Coded Max 1
Coding rules 0 : disable, 1 : enable
Mandatory rules --
Recommended --
rules
External Shall be set to 1 only if all RNCs neighbour to this BSS support the feature.
comment
Internal comment --
Logical EN_CPICH_2G_3G_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_CPICH_2G_3G_RESELECTION Sub-syste BSC Cell Type No
Definition Defines the CPICH measurements used in the 2G to 3G cell reselection
Coding rules 0: Only 1 CPICH measurement is used
1: CPICH Ec/No and RSCP measurements must be used
Mandatory rules This parameter can be set on 1 only if EN_2G_TO_3G_CELL_ RESELECTION <>0
Recommended --
rules
External --
comment
Internal comment --
Logical EN_DATA_144 B11 Yes B12 Yes
name TRX nb No
HMI Data 14.4 kbit/s Sub-syste BSC Cell Type No
Definition This flag indicates if 14.4 kbit/s operation is allowed.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter has not been removed in order not to impact the implementation of the BSC.
Logical EN_DIST_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_DIST_HO Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the detection of distance handover cause (cause 6).
Mandatory rules --
Recommended --
rules
External --
comment
Logical EN_DPVA B11 No B12 Yes
name TRX nb No
HMI EN_DPVA Sub-syste BSC Cell Type No
Definition Enables Dynamic Power Voltage Adjustment on all the MC modules in the cell, reducing their power consumption in low load situations.
Coding rules 0: the power voltage adjustement is disabled,
1: the power voltage adjustement is enabled.
Mandatory rules --
Recommended --
rules
External If EN_DPVA is set to enabled, the dynamic power voltage adjustment feature addresses only the MC modules, equipped with a unique power amplifier for all the
comment TRXs.
- a switchable power supply is required within the HW MC module (TRX, RRH, TRDU).
Logical EN_DR B11 Yes B12 Yes
name TRX nb No
HMI Directed_Retry Sub-syste BSC Cell Type No
Definition This flag enables/disables the execution of Directed Retry.
Spec ref. Handover management Coded Max 1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_DTM B11 Yes B12 Yes
name TRX nb No
HMI EN_DTM Sub-syste BSC Cell Type No
Definition Enables/disables the support of dual transfer mode
Rec ref. None Domai DTM Min value 0 Coded Min 0
Spec ref. DTM Functional specification Coded Max 1
Mandatory rules EN_DTM may be set to 1 only if :

-CELL_RANGE = 0
-MAX_PDCH_HIGH_LOAD > 1
Recommended If EN_DTM is Enabled for at least one cell within the BSS it is highly recommended to activate CS Paging Coordination for the BSS, either through the Gs Interface
rules (network_operation_mode = NMO I) or by setting EN_BSS_PAGING_COORDINATION to Enabled (network_operation_mode <> NMO I).
External ((E)GPRS is mandatory for DTM operation, and at least 2 PDCHs are required in the PS zone for allocation of DTM resources to (at least) one DTM call, therefore,
comment MAX_PDCH_HIGH_LOAD shall at least be equal to 2.
Logical EN_EGPRS B11 Yes B12 Yes
name TRX nb No
HMI EN_EGPRS Sub-syste BSC Cell Type No
Definition Enables/Disables EGPRS traffic in the cell.
Coding rules 0: Disable, 1: Enable
Mandatory rules EN_EGPRS = enable only if MAX_PDCH > 0.
Recommended If EN_EGPRS is set to enable, Alcatel recommend to set the parameter PS_PREF_BCCH_TRX to 0.
rules In case of extended cell, Alcatel recommend to set the same value in both, inner and outer, cells.
External From system point of view, when EN_EGPRS = Enable, the highest MCS allowed on the TRX is defined by the current size of the M-EGCH link of the TRX and by the
comment MAX_EGPRS_MCS value.
Internal comment 1) From system point of view, if EN_EGPRS = Enable, the highest MCS, i.e. the less robust, that can be used on each TRX of the cell is determined as a function of
the HW TRX capability, of the current size of the M-EGCH link of the TRX, and of the MAX_EGPRS_MCS value.
2) This parameter can be set to enable only if the EGPRS feature has been bought by the Customer.
Logical EN_EXT_DR B11 Yes B12 Yes
name TRX nb No
HMI EN_EDR Sub-syste BSC Cell Type No
Definition This flag enables/disables the Outgoing External Directed Retry procedure.
Mandatory rules --
Recommended EN_EXT_DR should be set to enable when EN_TCH_PREEMPT is set to enable.

rules
External - For external directed retries, the serving BSC does not know whether or not the external target cells (towards which the directed retry is triggered) are congested.
comment Therefore, Alcatel recommend to set RESP_REQ to 1 if EN_EDR is enabled in order to get a Handover Reject message from the MSC in case all target cells are
congested and thus to attempt other procedures.
- Significant when EN_DR is enabled
Internal comment MSC: Depends on MSC Type
Logical EN_EXT_MEAS_REP B11 Yes B12 Yes
name TRX nb No
HMI EN_EXT_MEAS_REP Sub-syste BSC Cell Type No
Definition This flag enables/disables the extended measurement reporting for Mobile Assisted Frequency Allocation.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_FAST_3G_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_FAST_3G_RESELECTION Sub-syste BSC Cell Type No
Definition Enables a fast 3G/LTE (FDD or TDD) cell reselection at 2G CS call release.
Coding rules 0:fast 3G/LTE cell reselection at 2G CS call release is not used.
1:only fast 3G cell reselection at 2G CS call release is used.
2:only fast LTE cell reselection at 2G CS call release is used.
3:fast LTE cell reselection at 2G CS call release is used, 3G otherwise.
Mandatory rules - It is not allowed to have EN_FAST_3G_RESELECTION = 1 and EN_2G_TO_3G_CELL_ RESELECTION = 0 and EN_2G_TO_3GTDD_CELL_ RESELECTION = 0.
- It is not allowed to have EN_FAST_3G_RESELECTION = 2 and EN_2G_TO_LTEFDD_CELL_ RESELECTION = 0 and EN_2G_TO_LTETDD_CELL_RESELECTION =
0.
It is allowed to have EN_FAST_3G_RESELECTION = 3 only if (EN_2G_TO_3G_CELL_RESELECTION <> 0 and EN_2G_TO_LTEFDD_CELL_RESELECTION <> 0) or
(EN_2G_TO_3G_CELL_RESELECTION <> 0 and EN_2G_TO_LTETDD_CELL_RESELECTION <> 0) or (EN_2G_TO_3GTDD_CELL_RESELECTION <> 0 and
Recommended --
rules
External - Parameter change: no impact on the telecom service, on going traffic is not disrupted. But any modification impacts System Information Broadcasting. Change applied
comment immediately after modification in dedicated Channel Release messages of the current calls.
Internal comment 3G TDD and LTE FDD are mutually exclusive.
Logical EN_FAST_TRAFFIC_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_FAST_TRAFFIC_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the use of Fast traffic handovers.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_FORCED_DR B11 Yes B12 Yes
name TRX nb No
HMI EN_FORCED_DR Sub-syste BSC Cell Type No
Definition This flag enables/disables the Forced Directed Retry handover cause (cause 20) detection.
Mandatory rules - EN_FORCED_DR and EN_PREFERRED_BAND_FORCED_DR are exclusive: both cannot be enabled at the same time.
Recommended --
rules
External --
comment
Internal comment --
Logical EN_FR_IF_HR_PREF B11 Yes B12 Yes
name TRX nb No
HMI EN_FR_IF_HR_PREF Sub-syste BSC Cell Type No
Definition When set, this flag allows, when bugged MS asking for a dual rate, half-rate preferred, to allocate a full rate channel.
Category Network (CDE) OMC-R access None (DLS) Type Flag Unit None
Coding rules 0 : function disabled, 1 : function enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This flag shall be set to 1 only in Cegetel NW
Logical EN_GAN_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_GAN_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the handover to GAN
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_GENERAL_CAPTURE_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_GENERAL_CAPTURE_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of general capture handover cause (cause 24).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_GPRS B11 Yes B12 Yes
name TRX nb No
HMI Enable GPRS Sub-syste BSC Cell Type No
Definition This flag enables / disables the GPRS traffic within the cell.
Mandatory rules if MAX_PDCH = 0 then EN_GPRS is set to disable

if MAX_PDCH > 0 then EN_GPRS is set to enable
Recommended If a BSC is connected to a MFS but GPRS is disabled (EN_GPRS = false) for any cells of the BSS, it is recommended to set EN_BSS_PAGING_COORDINATION to
rules disabled for that BSS.
External --
comment
Internal comment The EN_GPRS parameter is not displayed as such to the O&M user.
Logical EN_HR_FOR_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI EN_HR_FOR_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition Enables/disables, when the cell is loaded, the support of the Half Rate allocation (at new call establishment and during inter-cell handover) for possible AMR-WB calls.
This feature deals with the possible AMR-WB calls, ie calls for which AMR-WB is supported by the MS, and supported by the TC, and allowed by the MSC, and allowed in
the cell.
1: enabled
Mandatory rules --
Recommended --
rules
External - Significant if EN_AMR_WB_GMSK is enabled
comment - Parameter change: No impact on the telecom service, calls on going in the cell are not disrupted. Change applied only on new calls (establishment or handover)
allocated in the cell after modification.
Internal comment --
Logical EN_HSL B11 Yes B12 Yes
name TRX nb No
HMI EN_HSL Sub-syste BSC Cell Type No
Definition Enables SS7 HSL (High speed Signalling Link).
Coding rules 0: HSL disabled
1: HSL enabled
Mandatory rules --
Recommended --
rules
External Changeable on the BSC terminal.
comment if EN_HSL = 1 the following new Q703 parameters:
Q703_N1_HSL, Q_703_N2_HSL, Q703_T1_HSL, Q703_T4E_HSL and Q703_T4N_HSL
replaces the old ones:
Q703_N1, Q_703_N2, Q703_T1, Q703_T4E and Q703_T4N.
Internal comment --
Logical EN_IC_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_INCOMING_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables incoming handovers in the cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_IM_ASS_REJ B11 Yes B12 Yes
name TRX nb No
HMI EN_IMM_ASS_REJ Sub-syste BSC Cell Type No
Definition This flag indicates if the Immediate Assignment Reject procedure is enabled.
Mandatory rules --
Recommended --
rules
External This parameter is only valid for circuit switched traffic. For packet traffic (GPRS or EGPRS) sending of IMMEDIATE ASSIGNMENT REJECT messages cannot be
comment disabled.
Internal comment --
Logical EN_INBAND_NOTIF B11 Yes B12 Yes
name TRX nb No
HMI EN_INBAND_NOTIF Sub-syste BSC Cell Type No
Definition Flag to disable/enable the in-band notification
Coding rules 0: disabled, 1:enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment If EN_INBAND_NOTIF is set to enabled, in addition to sending initial Notification messages on the NCH for the voice group call, If the priority level of the new call is
equal or higher than the priority level defined by the parameter Notif_FACCH_PTP_call_THR, the BSS sends initial notification messages (i.e. the three first notification
messages) on FACCH of all on-going standard point-to-point calls in the cell informing mobile stations partaking in these calls of new voice group calls that are being
set-up in the cell.
Logical EN_INBAND_PAGING B11 Yes B12 Yes
name TRX nb No
HMI EN_INBAND_PAGING Sub-syste BSC Cell Type No
Definition Flag to disable/enable the in-band paging
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_INT_HO_INITIATED_BY_MSC B11 No B12 Yes
name TRX nb No
HMI EN_INT_HO_INITIATED_BY_MSC Sub-syste BSC Cell Type No
Definition Enables/disables the processing of the internal handover initiated by the MSC.
Spec ref. Internal Channel Change Coded Max 1
Mandatory rules --
Recommended --
rules
External - Significant only if EN_AUP_OVER_IP is enabled
comment - Parameter change: No impact on the telecom service, on going calls are not disrupted. Change applied on the new calls established after modification.
Internal comment --
Logical EN_INTERBAND_NEIGH B11 Yes B12 Yes
name TRX nb No
HMI EN_INTERBAND_HO Sub-syste BSC Cell Type No
Definition This flag enables / disables the multiband operation by filtering the sending of SYSTEM INFORMATION TYPE 2ter/5ter.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_INTFBD_PM B11 No B12 Yes
name TRX nb No
HMI EN_INTFBD_PM Sub-syste BSC Cell Type No
Definition Enables/disables the management of the interference distribution on all the idle channels (TCH, PDCH and SDCCH).
Mandatory rules --
Recommended --
rules
External - Parameter Change: No impact on the telecom service, on going calls are not disrupted. Change applied immediately after modification
comment
- Transmitted to the BTS in the BTS_CONF_DATA message
Logical EN_INTRA_DL B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRA_DL Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of intracell downlink handover cause (cause 16) for non AMR calls (neither AMR-NB nor AMR-WB).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_INTRA_DL_AMR B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRA_DL_AMR Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of intracell downlink handover cause (cause 16) for AMR-NB calls.
Coding rules 0: disable, 1: enable
Mandatory rules --
Recommended It is recommended to disable this intracell downlink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Logical EN_INTRA_DL_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRA_DL_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of intracell downlink handover cause (cause 16) for AMR-WB GMSK calls.
Mandatory rules --
Recommended It is recommended to disable this intracell downlink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Logical EN_INTRA_UL B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRA_UL Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of intracell uplink handover cause (cause 15) for non AMR calls (neither AMR-NB nor AMR-WB).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_INTRA_UL_AMR B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRA_UL_AMR Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of intracell uplink handover cause (cause 15) for AMR-NB calls.
Mandatory rules --
Recommended It is recommended to disable this intracell uplink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Logical EN_INTRA_UL_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRA_UL_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of intracell uplink handover cause (cause 15) for AMR-WB GMSK calls
Mandatory rules --
Recommended It is recommended to disable this intracell uplink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Logical EN_INTRACELL_REPEATED B11 Yes B12 Yes
name TRX nb No
HMI EN_INTRACELL_REPEATED Sub-syste BSC Cell Type No
Definition This flag enables/disables the repetition of intracell handover attempts.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_IP_CONGESTION_1ST_LEVEL B11 Yes B12 Yes
name TRX nb No
HMI EN_IP_CONGESTION_1ST_LEVEL Sub-syste BSC Cell Type No
Definition Enables/disables the defence mechanism related to CS IP congestion situation on the Abis interface.
When a CS IP congestion is detected by a given BTS, then no new call can be established on any TRX linked to that BTS as long as IP_CONGESTION_TIMER is running
(the on going CS calls are kept established).
This first level of detection, also called preventive congestion detection, is based on the UL and DL transmission delays measured to transfer IP packets between the BTS
and the TC. It aims at avoiding that the congestion situation gets worse.
Coding rules 0: 1st level of CS IP congestion is disabled
1: 1st level of CS IP congestion is enabled
Mandatory rules --
Recommended --
rules
External Parameter change: No impact on the telecom service, on going traffic is not disrupted. This flag is taken into account immediately by the BSC: if a congestion situation
comment is already detected by the BTS when this flag is activated (indeed, the detection in the BTS is always active), then the first level of defence applies immediately in the
BSC.
If this flag is disabled when the first level of defence applies in the BSC then all new calls are immediately accepted by the BSC.
Internal comment --
Logical EN_IPE_PREF_CODEC_TYPE B11 Yes B12 Yes
name TRX nb No
HMI EN_IPE_PREF_CODEC_TYPE Sub-syste BSC Cell Type No
Definition This Flag enables/disables the support of the "preferred codec" algorithm for TFO.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment As TFO_REQ_P messages no more exist in 3GPP, this functional option becomes a BSC constant always set to disable (change introduced with TFO for AMR-NB).
The T_TFO_PREF information remains in the BSC-BTS interface for compatibility reason with old TC configuration e.g. DT 16
Logical EN_IURG B11 Yes B12 Yes
name TRX nb No
HMI EN_IURG Sub-syste BSC Cell Type No
Definition Enables/disables the support of the Iur-g+ (Iur-g with enhanced control plane) interface.
This interface allows a BSS to be connected to one or several RNCs.
The enhanced RNSAP control plane is carried over SCCP/M3UA/SCTP/IP.
Mandatory rules - Up to 16 RNCs can be connected to one BSC.

- EN_IURG can be enabled if, at least, one RNC SCTP endpoint has been configured.
- EN_IURG can be disabled if all the Iur-g signalling links of all the RNCs have been locked.
Recommended --
rules
comment - Parameter change:No impact on the telecom service, on going traffic is not disrupted. This flag is taken into account
immediately by the BSC.
Internal comment - it is an optional feature, but CMCC proprietary and specific.
- up to MAX_NB_RNC (BOP) = 16 RNC can be connected to one BSC
Logical EN_LB B11 Yes B12 Yes
name TRX nb No
HMI EN_LB Sub-syste BSC Cell Type No
Definition Enables/disables the support of the Lb interface (in the CS domain) in the BSC.
This interface allows a BSS to be connected to a single external SMLC.
When enabled, the Timing Advance positioning method (also called CellId + TA) is used.
The Lb interface is natively carried over SIGTRAN (SCCP/M3UA/SCTP/IP).
Rec ref. None Domai LCS Min value 0 Coded Min 0
Spec ref. LCS Functional Specification Coded Max 1
Mandatory rules - Only one SMLC can be connected to one BSC

- EN_LB and EN_LCS shall not be both enabled at the same time
- When EN_LB is disabled, then EN_LB_NMR cannot be enabled.
- EN_LB can be enabled if, at least, one SCTP endpoint has been configured in the associated SMLC.
- EN_LB can be disabled if all the Lb signalling links of the associated SMLC have been locked.
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
comment - Parameter change: No impact on the telecom service, on going traffic is not disrupted. This flag is taken into account immediately by the BSC.
- GPS-oriented, E-OTD and U-TDOA methods are not supported by ALU BSS
Logical EN_LB_NMR B11 Yes B12 Yes
name TRX nb No
HMI EN_LB_NMR Sub-syste BSC Cell Type No
Definition When the Lb interface (in the CS domain) is supported by the BSC, this flag allow to use the TA positioning + NMR method (with radio measurements report of neighbour
cells), instead of the default (CellId + TA) positioning method.
Mandatory rules - EN_LB_NMR can be enabled only if EN_LB is already enabled
Recommended --
rules
comment - Significant if EN_LB is enabled
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. This flag is taken into account immediately by the BSC.
- GPS-oriented, E-OTD and U-TDOA methods are not supported by ALU BSS
Logical EN_LCS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI EN_LCS Sub-syste BSC Cell Type No
Definition Enables/Disables the Location Services (LCS) in the BSS.
Coding rules 0 = disabled; 1 = enabled
Mandatory rules - Equal to EN_LCS (MFS)

- EN_LCS = disabled on BSC G2
Recommended --
rules
comment - Only the value 0 is supported on G2 BSC.
Logical EN_LNK_M B11 Yes B12 Yes
name TRX nb No
HMI EN_LNK_M Sub-syste BSC Cell Type No
Definition This flag enables/disables datalink monitoring.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_LOAD_BALANCE B11 Yes B12 Yes
name TRX nb No
HMI EN_LOAD_BALANCE Sub-syste BSC Cell Type Yes
Definition Flag to enable/disable the balancing of load between the inner and outer zone of a multiband cell.
Mandatory rules --
Recommended EN_LOAD_BALANCE & EN_LOAD_OUTER should not be both "Enabled".

rules
External EN_LOAD_BALANCE significant only if EN_BETTER_ZONE_HO is enabled
comment
Internal comment --
Logical EN_LOAD_MNGT B11 Yes B12 Yes
name TRX nb No
HMI Automatic AC barring on TCH load Sub-syste BSC Cell Type No
Definition This flag enables/disables automatic barring of access classes on TCH load criterion.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_LOAD_ORDER B11 Yes B12 Yes
name TRX nb No
HMI EN_LOAD_ORDER Sub-syste BSC Cell Type No
Definition This flag indicates whether or not traffic load has to be taken into account when setting up the list of target cells.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_LOAD_OUTER B11 Yes B12 Yes
name TRX nb No
HMI Load computation in outer zone Sub-syste BSC Cell Type No
Definition Flag to enable/disable the load computation on the outer zone of a Concentric/multiband cell instead of the load computation on the whole cell.
Mandatory rules --
Recommended When enabled, the values of the parameters FREElevel_1 to FREElevel_4 need to be updated to number of TRX considered in the load computation.
rules EN_LOAD_BALANCE & EN_LOAD_OUTER should not be both "Enabled".
External significant only for concentric and multiband cells.
comment
Internal comment --
Logical EN_MA_SELECTION B11 Yes B12 Yes
name TRX nb No
HMI EN_MA_SELECTION Sub-syste BSC Cell Type No
Definition This flag enables/disables channel selection according to Mobile Allocation criterion.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_MCHO_H_DL B11 Yes B12 Yes
name TRX nb No
HMI EN_MCHO_H_DL Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the detection of level downlink micro-cell handover cause (cause 18).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_DIMENSION_TYPE = Micro. CT: Depends on Cell Type and BTS Type
Logical EN_MCHO_H_UL B11 Yes B12 Yes
name TRX nb No
HMI EN_MCHO_H_UL Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the detection of level uplink mirco-cell handover cause (cause 17).
Coding rules 0: disabled1: enabled
Mandatory rules --
Recommended --
rules
External --
comment
Logical EN_MCHO_NCELL B11 Yes B12 Yes
name TRX nb No
HMI EN_MCHO_NCELL Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the detection of high level in neighbour lower or indoor cell handover cause (cause 14).
Mandatory rules --
Recommended In a lower layer cell, the flag shall be disabled if there is no indoor layer.
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer or lower layer.
Logical EN_MCHO_RESCUE B11 Yes B12 Yes
name TRX nb No
HMI EN_MCHO_RESCUE Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the detection of consecutive bad SACCH frames handover cause (cause 7).
Mandatory rules --
Recommended --
rules
External --
comment
Logical EN_MORE_RMS_BCCH_BSIC B11 Yes B12 Yes
name TRX nb No
HMI EN_MORE_RMS_BCCH_BSIC Sub-syste BSC Cell Type No
Definition Enables/disables the RMS improvement feature, which allows reporting more than 42 neighbour frequencies per TRX in the 2G radio link measurements performed by
the MS.
When enabled, the parameter RMS_BCCH_BSIC_NB gives the maximum number of frequencies reported by the BTS.
When disabled, that maximum is not configurable (42, per default).
Mandatory rules --
Recommended --
rules
External -Parameter available on BSC Evolution only.
comment -Parameter change: No impact on the telecom service, on going calls are not disrupted. But the RMS jobs, ongoing on the BTSs, are restarted (all data already
collected are discarded).
Logical EN_MS_PC B11 Yes B12 Yes
name TRX nb No
HMI EN_MS_PC Sub-syste BSC Cell Type No
Definition This flag enables/disables MS Power Control.
Coding rules 0: disabled1: enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_MULTIBAND_PBGT_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_MULTIBAND_PBGT_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the power budget handovers Cause 12 and the traffic handovers Cause 23 between cells belonging to different frequency bands.
Coding rules 0 : function disabled, 1 : function enabled
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_PAIRING_NON_SAIC_VAMOS1 B11 No B12 Yes
name TRX nb No
HMI Non SAIC / VAMOS-1 Sub-syste BSC Cell Type No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of a legacy non SAIC capable terminal with a VAMOS1
capable terminal, on the same TCH sub-channel (in FR or HR).
Mandatory rules - EN_PAIRING_NON_SAIC_VAMOS1 can be set to enabled only if SCPIR_LOW_MS_ALLOC_NON_SAIC + SCPIR_LOW_MS_ALLOC_VAMOS1 <= 0
Recommended --
rules
Internal comment - A SAIC capable MS is also called DARP phase 1 MS
- A VAMOS aware MS corresponds to a VAMOS level 1 or a VAMOS level 2 MS.
- With the default value (8-4>0), ALU recommends to forbid pairing of VAMOS1 with NON-SAIC.
Logical EN_PAIRING_NON_SAIC_VAMOS2 B11 No B12 Yes
name TRX nb No
HMI Non SAIC / VAMOS-2 Sub-syste BSC Cell Type No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of a legacy non SAIC capable terminal with a VAMOS2
capable terminal, on the same TCH sub-channel (in FR or HR).
Mandatory rules - EN_PAIRING_NON_SAIC_VAMOS2 can be set to enabled only if SCPIR_LOW_MS_ALLOC_NON_SAIC + SCPIR_LOW_MS_ALLOC_VAMOS2 <= 0
Recommended --
rules
- A VAMOS aware MS corresponds to a VAMOS level 1 or a VAMOS level 2 MS
Logical EN_PAIRING_SAIC_SAIC B11 No B12 Yes
name TRX nb No
HMI SAIC / SAIC Sub-syste BSC Cell Type No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of two legacy SAIC capable terminals, on the same TCH
sub-channel (in FR or HR).
Mandatory rules - EN_PAIRING_SAIC_SAIC can be set to enabled only if SCPIR_LOW_MS_ALLOC_SAIC <= 0
Recommended --
rules
Logical EN_PAIRING_SAIC_VAMOS1 B11 No B12 Yes
name TRX nb No
HMI SAIC / VAMOS-1 Sub-syste BSC Cell Type No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of a legacy SAIC capable terminal with a VAMOS1 capable
terminal, on the same TCH sub-channel (in FR or HR).
Mandatory rules - EN_PAIRING_SAIC_VAMOS1 can be set to enabled only if SCPIR_LOW_MS_ALLOC_SAIC + SCPIR_LOW_MS_ALLOC_VAMOS1 <= 0
Recommended --
rules
Logical EN_PAIRING_SAIC_VAMOS2 B11 No B12 Yes
name TRX nb No
HMI SAIC / VAMOS-2 Sub-syste BSC Cell Type No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of a legacy SAIC capable terminal with a VAMOS2 capable
Mandatory rules - EN_PAIRING_SAIC_VAMOS2 can be set to enabled only if SCPIR_LOW_MS_ALLOC_SAIC + SCPIR_LOW_MS_ALLOC_VAMOS2 <= 0
Recommended --
rules
Logical EN_PAIRING_VAMOS1_VAMOS1 B11 No B12 Yes
name TRX nb No
HMI VAMOS-1 / VAMOS-1 Sub-syste BSC Cell Type No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of two VAMOS1 capable terminals, on the same TCH
Mandatory rules - EN_PAIRING_VAMOS1_VAMOS1 can be set to enabled only if SCPIR_LOW_MS_ALLOC_VAMOS1 <= 0
Recommended --
rules
name TRX nb No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of a VAMOS1 capable terminal with a VAMOS2 capable
Mandatory rules - EN_PAIRING_VAMOS1_VAMOS2 can be set to enabled only if SCPIR_LOW_MS_ALLOC_VAMOS1 + SCPIR_LOW_MS_ALLOC_VAMOS2 <= 0
Recommended --
rules
name TRX nb No
Definition Enables/disables the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of two VAMOS2 capable terminals, on the same TCH
Mandatory rules - EN_PAIRING_VAMOS2_VAMOS2 can be set to enabled only if SCPIR_LOW_MS_ALLOC_VAMOS2 <= 0
Recommended --
rules
Logical EN_PBGT_FILTERING B11 Yes B12 Yes
name TRX nb No
HMI EN_PBGT_FILTERING Sub-syste BSC Cell Type Yes
Definition This flag enables/disables filtering of candidate neighbour cells on HO_MARGIN_DIST/LEV/QUAL criterion.
Mandatory rules --
Recommended This parameter must be set to disabled in case of extended cell

rules
External --
comment
Internal comment --
Logical EN_PBGT_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_PBGT_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of power budget handover cause (cause 12).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_PCR B11 Yes B12 Yes
name TRX nb No
HMI Preventive cyclic retransmission flag Sub-syste BSC Cell Type No
Definition This flag enables preventive cyclic retransmission.
Mandatory rules --
Recommended --
rules
External This parameter is set to 1 by the BSC in case the Ater links of a BSS are configured as satellite links.
comment
Internal comment --
Logical EN_POWER_SAVING B11 Yes B12 Yes
name TRX nb No
HMI EN_POWER_SAVING Sub-syste BSC Cell Type No
Definition Enables power saving on all TRXs in the cell.
Coding rules 0: the power saving is disabled,
1: the power saving is enabled.
Mandatory rules --
Recommended --
rules
External If EN_POWER_SAVING is set to enabled, the TRX dynamic power saving feature will be applied on all the TRXs in the cell belonging to G3, G4 or G5 TREs. The
comment feature will however not be applied on the TRXs in the cell belonging to MC modules, due to the specific architecture of MC modules (unique power amplifier for all the
TRXs).
- it is an optional feature
Logical EN_PREFERRED_BAND_FORCED_DR B11 No B12 Yes
name TRX nb No
HMI EN_PREFERRED_BAND_FORCED_DR Sub-syste BSC Cell Type No
Definition This flag enables/disables the Preferred Band Forced Directed Retry handover cause (cause 36) detection.
Mandatory rules - EN_FORCED_DR and EN_PREFERRED_BAND_FORCED_DR are exclusive: both cannot be enabled at the same time.
Recommended - when enabled in at least one cell of the BSS, Alcatel-Lucent recommends to enable QUEUE_ANYWAY, otherwise the feature will work only when queuing is
rules allowed by the MSC.
comment - Significant when EN_DR is enabled
Logical EN_PREFERRED_BAND_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_PREFERRED_BAND_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of handover cause 21 (high level in neighbour cell in the preferred band).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_PRIORITY_ORDERING B11 Yes B12 Yes
name TRX nb No
HMI EN_PRIORITY_ORDERING Sub-syste BSC Cell Type No
Definition This flag enables/disables the use of the parameter PRIORITY(0,n) in the candidate cell evaluation process.
Coding rules 0: Priority(0,n) not taken into account, 1: Priority(0,n) taken into account
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_RANDOMISE_FBL2 B11 Yes B12 Yes
name TRX nb No
HMI EN_RANDOMISE_FBL2 Sub-syste BSC Cell Type No
Definition Enables/disables the support of the randomisation of fill bits in L2 message feature on the DL Air interface of the cell. That feature brings more protection to voice calls
using A5/1 encryption algorithm.
Spec ref. LAPDM functional specification Coded Max 1
Coding rules 0: the DL randomisation is disabled,
1: the DL randomisation is enabled.
Mandatory rules --
Recommended Since a MS may move from one cell to another cell, the activation of the feature on few cells makes no sense. Alcatel-Lucent recommends on a large set of cells, like
rules the BSS level.
- For more protection, Alcatel-Lucent recommends configuring EN_RANDOMISE_FBL2 and EN_RANDOMISE_FBSI6 in a consistent way.
External Parameter change:
comment No impact on the telecom service, on going calls are not disrupted. Change applied only on new CS calls established after modification.
- it is an optional feature, supported from G3 onwards TRE (including MC module).
Logical EN_REP_DL_FACCH B11 Yes B12 Yes
name TRX nb No
HMI EN_REP_DL_FACCH Sub-syste BSC Cell Type No
Definition Enables/Disables repeated downlink FACCH for AMR-NB or AMR-WB GMSK calls.
1: enabled for LAPDm command frames
2: enabled for LAPDm command frames, and also for LAPDm response frames (valid only for the MS having indicated the support of the feature by Repeated ACCH
Capability bit=1).
Mandatory rules --
Recommended --
rules
External Function available on BSC Evolution only.
comment Parameter change : no impact on the telecom service. Change applied on new calls (after modification).
Internal comment Transmitted (indirectly : used to set other fields) to the BTS via RSL
Logical EN_REP_SACCH B11 Yes B12 Yes
name TRX nb No
HMI EN_REP_SACCH Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Enables/Disables repeated SACCH for SAPI 0 frames in case of AMR-NB or AMR-WB GMSK calls (for mobile station having indicated the support of the feature).
Mandatory rules --
Recommended --
rules
External Function available on BSC Evolution only.
comment Parameter change : no impact on the telecom service. Change applied on new calls (after modification).
Logical EN_RESCUE_UM B11 Yes B12 Yes
name TRX nb No
HMI EN_RESCUE_UMBRELLA Sub-syste BSC Cell Type Yes
Definition This flag determines if emergency handovers are directed preferentially to umbrella cells.
Coding rules 0: disabled, 1: enabled, 2: indefinite
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Lower layer. Used to prevent indoor MS going to umbrella. CT: Depends on Cell Type and BTS Type
Logical EN_RESET_LB B11 Yes B12 Yes
name TRX nb No
HMI EN_RESET_LB Sub-syste BSC Cell Type No
name Instance SMLC RMS No
Definition Enables/disables the handling of the RESET procedure, initiated by the BSC towards the SMLC, on the Lb interface. During this procedure, all the on-going LCS
procedures related to the BSC are cancelled.
Mandatory rules --
Recommended --
rules
Internal comment - the reset procedure, triggered by the SMLC, is independent of the present parameter.
- Optional procedure in 3GPP TS 49.031
Logical EN_RETURN_CS_ZONE_HO B11 Yes B12 Yes
name TRX nb No
HMI EN_RETURN_CS_ZONE_HO Sub-syste BSC Cell Type No
Definition Flag enabling the intracell handovers allowing to move TCH from the PS zone to the CS zone of PDCH/TCH allocation (intracell handover cause 30).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_RL_RECOV B11 Yes B12 Yes
name TRX nb No
HMI EN_RADIOLINK_RECOVERY Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the Radio Link Recovery procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message.
Logical EN_RMS_IMPROVED B11 Yes B12 Yes
name TRX nb No
HMI EN_RMSI Sub-syste BSC Cell Type No
Definition Enables/disables the RMS improvement feature, processing by the BSC.
Mandatory rules --
Recommended --
rules
comment - Parameter Change: No impact on the telecom service, on going calls are not disrupted. Change applied immediately after modification.
Internal comment - Feature specific for CMCC
- it is an optional feature (TRX quantity controlled)
Logical EN_RXLEV_DL B11 Yes B12 Yes
name TRX nb No
HMI EN_RXLEV_DL Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of level downlink handover cause (cause 5).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_RXLEV_UL B11 Yes B12 Yes
name TRX nb No
HMI EN_RXLEV_UL Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of level uplink handover cause (cause 3).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_RXQUAL_DL B11 Yes B12 Yes
name TRX nb No
HMI EN_RXQUAL_DL Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of quality downlink handover cause (cause 4).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_RXQUAL_UL B11 Yes B12 Yes
name TRX nb No
HMI EN_RXQUAL_UL Sub-syste BSC Cell Type No
Definition This flag enables/disables the detection of quality uplink handover cause (cause 2).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_SAIC_SCPIR_MODIF B11 No B12 Yes
name TRX nb No
HMI EN_SAIC_SCPIR_MODIF Sub-syste BSC Cell Type No
Definition When the pairing in VAMOS (Voice services over Adaptive Multi-user channels on One Slot) mode, of two legacy SAIC capable terminals, is enabled in the cell, this
parameter enables/disables values of SCPIR (Sub-Channel Power Imbalance Ratio) different from 0dB for the VAMOS pair composed of two legacy SAIC capable
terminals.
Mandatory rules --
Recommended - Alcatel-Lucent highly recommends enabling this parameter, especially in case of positive SCPIR_LOW_MS_ALLOC_SAIC or SCPIR_LOW_MS_ALLOC_SUB_SAIC
rules value.
comment - Significant if EN_PAIRING_SAIC_SAIC is enabled.
Internal comment When disabled, the DL SCPIR value is fixed to 0dB and only the total BS_TXPWR value can be modified (ie. SCPIRlow_PC = SCPIRhigh_PC = 0dB in the VAMOS BS
Power Control algorithm).
Logical EN_SEND_CM3 B11 Yes B12 Yes
name TRX nb No
HMI Forward_CM_3 Sub-syste BSC Cell Type No
Definition This flag enables/disables sending of Classmark 3 IE to the MSC.
Coding rules 0: Disabled, 1: Enabled
Mandatory rules EN_SEND_CM3 and STRIP_O5_CM2 shall not be both set to 1 at the same time.
Recommended --
rules
External The value of this parameter depends on whether the MSC supports the MS classmark 3 IE or not: if the MSC supports the MS classmark 3 IE then the parameter shall
comment be set to 1, otherwise the parameter shall be set to 0.
Internal comment --
Logical EN_SEND_OLD_CHAN_MODE B11 Yes B12 Yes
name TRX nb No
HMI EN_SEND_OLD_CHAN_MODE Sub-syste BSC Cell Type No
Definition This flag controls Current channel OIE inclusion in HANDOVER REQUIRED.
Coding rules 0: IE is not included, 1: IE is included
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical EN_SEND_SPEECH_VER B11 Yes B12 Yes
name TRX nb No
HMI EN_SEND_SPEECH_VER Sub-syste BSC Cell Type No
Definition This flag controls Speech version (used) OIE inclusion in HANDOVER REQUIRED.
Coding rules 0: IE is not included, 1: IE is included
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical EN_SPECIFIC_PM B11 No B12 Yes
name TRX nb No
HMI EN_SPECIFIC_PM Sub-syste BSC Cell Type No
Definition Enables/disables the specific counters management.
Spec ref. OMC/BSC PM file format Coded Max 1
Mandatory rules --
Recommended --
rules
comment - Parameter Change: No impact on the telecom service, on going calls are not disrupted. Change applied immediately after modification.
Logical EN_SPEED_DISC B11 Yes B12 Yes
name TRX nb No
HMI EN_SPEED_DISCRIMINATION Sub-syste BSC Cell Type Yes
Definition This flag enables/disables the speed discrimination process.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Lower layer or CELL_LAYER_TYPE = Upper layer. CT: Depends on Cell Type and BTS Type
Logical EN_SYNCHRONISED_HO B11 Yes B12 Yes
name TRX nb No
HMI SYNCHRONISED_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables synchronous handovers between synchronized cells.
Mandatory rules EN_SYNCHRONISED_HO shall be set to disabled when CELL_TYPE is equal to Extended inner or Extended outer.
Recommended --
rules
External --
comment
Internal comment CELL_TYPE = extended inner at OMC-R HMI corresponds to CELL_RANGE = inner cell in the BSC. CELL_TYPE = extended outer at OMC-R HMI corresponds to
CELL_RANGE = outer cell in the BSC.
Logical EN_TCH_PREEMPT B11 Yes B12 Yes
name TRX nb No
HMI EN_TCH_PREEMPT Sub-syste BSC Cell Type No
Definition This flag enables/disables the TCH/VGCH pre-emption feature. If enabled, a point-to-point or voice group call with the pvi (pre-emption vulnerability indication) bit set might
be pre-empted for a point-to-point or voice group call that has the pci (pre-emption capability indication) bit set if the concerned cell is in congestion state.
Coding rules 0:disabled, 1:enabled
Mandatory rules --
Recommended - EN_EXT_DR should be set to enable when EN_TCH_PREEMPT is set to enable.

rules - If EN_VGCS = enabled , then Alcatel recommends to set EN_TCH_PREEMPT to enabled, otherwise to set the value of MIN_VGCS_TS to a value greater or equal to 2.
External In case one or more TCHs have been reserved for emergency handovers (NUM_TCH_EGNCY_HO > 0) in the concerned cell, the BSC will first try to use one of these
comment resources before actually releasing an ongoing call with lower priority and the pvi bit set.
In case the cell is congested, if EN_TCH_PREEMPT is enabled and the MSC does not allow the queing, the BSC will queue an incoming point-to-point request with
pre-emption capability indicator set during at most T11_forced seconds for a normal assignment or during at most T_qho seconds for an handover request. For the
voice group call request, the BSC will follow the MSC indicator.
Internal comment --
Logical EN_TEST_FOR_NON_SAIC B11 No B12 Yes
name TRX nb No
HMI EN_TEST_FOR_NON_SAIC Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter enables/disables the transmission of AQPSK test
bursts for the legacy non SAIC capable MSs before allocating them in VAMOS mode (to know if they are legacy SAIC capable instead).
Mandatory rules --
Recommended --
rules
Internal comment When enabled, the MSs, with VAMOS level = 00 and Downlink Advanced Receiver Performance = 00 in MS Classmark3, are ToBeTested before considering them as
legacy non SAIC, or legacy SAIC. When disabled, they are legacy non SAIC. For testing such MS, on reception of the TEST MS message, the BTS sends AQPSK test
bursts with SCPIR = 0dB.
Logical EN_TFO B11 Yes B12 Yes
name TRX nb No
HMI EN_TFO Sub-syste BSC Cell Type No
Definition Flag to enable/ disable the use of the TFO function for FR, EFR and HR codec types.
Spec ref. TFO Functional specification Coded Max 1
Mandatory rules - EN_AUP_OVER_IP can be enabled in "Full AUPoIP" architecture (AUP_OVER_TDM_CODEC_SUP = 0) only without TFO (EN_TFO and EN_TFO_AMR_NB and
EN_TFO_AMR_WB shall be disabled in all the cells)
Recommended --
rules
External --
comment
Logical EN_TFO_AMR_NB B11 Yes B12 Yes
name TRX nb No
HMI EN_TFO_AMR_NB Sub-syste BSC Cell Type No
Definition Flag to enable/ disable the use of the TFO function in case of AMR-NB codec.
Recommended --
rules
External Function available on BSC Evolution only
comment
Internal comment it is an optional feature.
Logical EN_TFO_AMR_WB B11 Yes B12 Yes
name TRX nb No
HMI EN_TFO_AMR_WB Sub-syste BSC Cell Type No
Definition Flag to enable/ disable the use of the TFO function in case of AMR-WB GMSK codec.
Recommended --
rules
External --
comment
Internal comment Non optional feature (present with AMR-WB), kind of safety flag.
Logical EN_TFO_MATCH B11 Yes B12 Yes
name TRX nb No
HMI EN_TFO_MATCH Sub-syste BSC Cell Type No
Definition This flag enables/disables TFO codec mismatch resolution function (for FR, EFR, HR, AMR-NB and AMR-WB codecs).
Mandatory rules - may be set to 1 only if EN_TFO=1

or if EN_TFO_AMR_WB=1 or if EN_TFO_AMR_NB=1
- May be set to 0 only if EN_TFO_OPT = 0
Recommended --
rules
External --
comment
Internal comment --
Logical EN_TFO_OPT B11 Yes B12 Yes
name TRX nb No
HMI EN_TFO_OPT Sub-syste BSC Cell Type No
Definition This flag enables/disables TFO codec optimisation function.
Mandatory rules may be set to 1 only if EN_TFO_MATCH=1
Recommended --
rules
External --
comment
Internal comment --
Logical EN_TRAFFIC_HO(0,n) B11 Yes B12 Yes
name TRX nb No
HMI EN_TRAFFIC_HO Sub-syste BSC Cell Type No
name Instance adj RMS No
Definition This flag enables/disables the detection of traffic handover cause (cause 23).
Mandatory rules --
Recommended --
rules
External As the traffic load of cells external to the BSC is unknown, no HO cause 23 will be triggered towards these cells, even if EN_TRAFFIC_HO = 1.
comment
Internal comment --
Logical EN_UNEQUIPPED_CIRCUIT B11 Yes B12 Yes
name TRX nb No
HMI EN_UNEQUIPPED_CIRCUIT Sub-syste BSC Cell Type No
Definition This flag enables/disables the sending of UNEQUIPPED CIRCUIT message.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical EN_UPLINK_REPLY B11 Yes B12 Yes
name TRX nb No
HMI EN_UPLINK_REPLY Sub-syste BSC Cell Type No
Definition Flag to disable/enable the uplink reply procedure
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_VAMOS B11 No B12 Yes
name TRX nb No
HMI EN_VAMOS Sub-syste BSC Cell Type No
Definition Enables/disables VAMOS (Voice services over Adaptive Multi-user channels on One Slot) in the cell.
This service allows assigning a single radio timeslot either up to 2 Full Rate MS or up to 4 Half Rate MS.
Mandatory rules - EN_VAMOS can be enabled only if the BTS-TransMode (of the concerned BTS(s)) is not in TDM mode.
Recommended - Alcatel-Lucent recommends to enable the DL DTX, the Repeated xACCH and the BS Power Control with VAMOS.
rules - For continuity purpose, before activating VAMOS, Alcatel-Lucent recommends to initialize TSC_1 with the current TSC value.
- For VAMOS, base station hardware requires antenna diversity to receive two users who are transmitting at the same time, otherwise the BTS will not be able to
decode the UL signals in VAMOS mode and the VAMOS calls will be unpaired immediately after the VAMOS pairing. Moreover, according to the 3GPP TS 45.005, a
BTS supporting VAMOS shall fulfill RX performance requirements with RX diversity with two antennas
comment - Function supported from G5 onwards TRE.
- VAMOS will not apply to MS allocated in DTM mode.
- Parameter change: when the parameter is changed, the TRX/RSL mapping may need to be ajusted. For that, all the impacted TRXs of the cell have the preserve calls
flag set to TRUE, before shutting down their on going calls (Wait Traffic Clear). Change applied only on new resource allocation requests received after the
modification.
Internal comment - BTS-TransMode is a BOP parameter
- VAMOS is not supported by G3 or G4 TREs.
- it is an optional feature (TRX quantity controlled).
- Due to DSP limitation, VAMOS is not supported on all the TRXs of a MC module/G6 TRE.
- VAMOS requires a MSC Release 9 (for updated Classmark 3).
Logical EN_VAMOS_NASS B11 No B12 Yes
name TRX nb No
HMI EN_VAMOS_NASS Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter enables/disables VAMOS pairing on normal
assignment.
Mandatory rules --
Recommended --
rules
Internal comment --
Logical EN_VAMOS_NON_AMR B11 No B12 Yes
name TRX nb No
HMI EN_VAMOS_NON_AMR Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter enables/disables VAMOS pairing of non AMR calls
(neither AMR-NB nor AMR-WB).
Mandatory rules --
Recommended --
rules
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification, in the radio resource allocation.
Internal comment --
Logical EN_VAMOS_PAIRING_CA B11 No B12 Yes
name TRX nb No
HMI EN_VAMOS_PAIRING_CA Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this flag enables/disables intracell HO for VAMOS pairing channel
adaptation (Handover Cause 35), due to high signal level and high load.
Mandatory rules --
Recommended --
rules
- Significant if HO_INTRACELL_ALLOWED is enabled.
Internal comment --
Logical EN_VAMOS_SUB_SAIC_BLACKLIST B11 No B12 Yes
name TRX nb No
HMI EN_VAMOS_SUB_SAIC_BLACKLIST Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter enables/disables the management of the black list of
the substandard Legacy SAIC capable MS. When paired in VAMOS mode, the performance of these SAIC MS is lower than expected.
1: enabled
Mandatory rules --
Recommended --
rules
Internal comment --
Logical EN_VAMOS_UNPAIRING_CA B11 No B12 Yes
name TRX nb No
HMI EN_VAMOS_UNPAIRING_CA Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this flag enables/disables intracell HO for VAMOS unpairing channel
adaptation (Handover Cause 34), due to bad radio quality or to low signal level.
Mandatory rules --
Recommended --
rules
- Significant if HO_INTRACELL_ALLOWED is enabled.
Internal comment --
Logical EN_VGCS B11 Yes B12 Yes
name TRX nb No
HMI EN_VGCS Sub-syste BSC Cell Type No
Definition Flag to disable/enable the VGCS in the cell
Mandatory rules --
Recommended When the VGCS feature (EN_VGCS) is activated, it is recommended to

rules - include the Response Request in the HANDOVER REQUIRED message (RESP_REQ).
- to configure, at least, one TRX with TRX_PREF_MARK <> 0 in the cell.
- to set EN_TCH_PREEMPT to enabled, otherwise to set the value of MIN_VGCS_TS to a value greater or equal to 2
External --
comment
Internal comment --
Logical ENH_UL_INTERF_MEAS B11 No B12 Yes
name TRX nb No
HMI ENH_UL_INTERF_MEAS Sub-systeBSC Cell Type No
Definition Defines the algorithm number, used in the BTS, by the enhanced reported UL interference measurement management.
Category Site (CAE) OMC-R access None (DLS & Restricted) Type Enumerated Unit None
Coding rules 0: average computing over INTAVE,
1: minimum computing over INTAVE,
2: minimum computing over T_INTRF_L3
Mandatory rules ENH_UL_UNTERF_MEAS <> 0 if and only if EN_INTFBD_PM is enabled
Recommended --
rules
External - Function supported on the G4 onwards TREs of the cell.
comment - Parameter change: No impact on the telecom service, on going traffic is not disrupted
Internal comment - this parameter is configurable (by ALU team) from the BSC terminal (from lab version)
- Transmitted to the BTS in the BTS_CONF_DATA message
- the feature is not supported by G3 TRE
Logical EXT_HO_FORCED B11 Yes B12 Yes
name TRX nb No
HMI EXT_HO_FORCED Sub-syste BSC Cell Type No
Definition This flag, when set, forces internal intercell handovers to be executed as external HO.
Coding rules 0: BSC performs internal HO, 1: MSC performs internal HO
Mandatory rules - EN_AUP_OVER_IP can be enabled only if EXT_HO_FORCED is disabled for all cells of the BSS.
Recommended --
rules
External --
comment
Internal comment - Valid for both TCH and SDCCH
- The forced external HO mecanism is NOT applied to the VGC talker, i.e., during the inter-cell internal channel change, i.e., the BSC shall ignore the value of
EXT_HO_FORCED parameter.
Logical FAKE_FDD_MANAGEMENT B11 Yes B12 Yes
name TRX nb No
HMI FAKE_FDD_MANAGEMENT Sub-syste
BSC Cell Type No
name InstanceBSS RMS No
Definition This parameter defines the way fake 3G FDD UARFCNs are managed in the SI2Quater message content, in order to cope with faulty MS within networks where the
GSM to UTRAN TD-SCDMA cell reselection is enabled.
Category Network (CDE) OMC-R access Displayed Type Enumerated Unit None
Coding rules 0: Not managed
1: Managed in every SI2Q instance
2: Managed only in SI2Q instances containing legacy 3G IEs.
Mandatory rules - For a given 2G cell, where both EN_2G_TO_3GTDD_CELL_RESELECTION and EN_2G_TO_LTETDD_CELL_RESELECTION are <> disabled, if
FAKE_FDD_MANAGEMENT = 1 then there shall be no more than 8 distinct ARFCN_3G (TDD) among all the neighbour 3G TDD cells target for reselection and there
shall
be no more than 3 distinct ARFCN_LTE(TDD) among all the neighbour LTE TDD cells target for reselection.
Recommended --
rules
External - This parameter is relevant only in 2G cells where EN_2G_TO_3GTDD_CELL_RESELECTION is <> disabled, ie when at least one neighbour 3G TDD UARFCN has to
be
comment broadcasted in SI2Quater.
Internal comment - Dimensional constraint of the ALU BSS is no more than 8 SI2Quater instances.
- Parameter is relevant only within CMCC networks
Logical FDD_ARFCN_LIST B11 Yes B12 Yes
name TRX nb No
HMI FDD_ARFCN_LIST Sub-syste BSC Cell Type No
Definition List of neighbour Downlink FDD UTRAN Absolute Radio Frequency Channel Numbers (UARFCNs) of any 3G FDD neighbor cell, adjacent to the BSS.
Up to 3 FDD UARFCNs can be defined in the list. This list is used for 2G to 3G cell reselection (blind search method).
Category Site (CAE) OMC-R access Changeable Type List of numbers Unit None
Coding rules The value of -1 is for implementation purpose only; this dummy value indicates that the operator does not provide any UARFCN.
Mandatory rules - The UARFCNs defined in the list (i.e. not set to -1) shall be different from each other.
- Only the following downlink FDD UARFCN ranges are standardized:
I) 10562-10838 and
II) 9662-9938 and
III) 1162-1513 and
IV) 1537-1738 and
V) 4357-4458 and
VI) 4387-4413 and
VII) 2237- 2563 and
VIII) 2937-3088 and
IX) 9237-9387 and
X) 3112-3388 and
XI) 3712-3787 and
XII) 3842- 3903 and
XIII) 4017-4043 and
XIV) 4117-4143
- Configuration of FDD_ARFCN_LIST and 2G/LTE inter-working are exclusive: for a given BSS, we cannot have at the same time a valid FDD_ARFCN_LIST and, at
Recommended --
rules
External - The FDD UARFCNs are used on the Air interface.
comment - The FDD UARFCNs of the 3G neighbour cells are broadcast on BCCH.
m
template
Internal comment The 3 UARFCNs form a table with the 3 following values FDD_ARFCN_LIST[I] for I = 1,,3.
The OMC always sends to the BSC precisely 3 values for this list, including the dummy ones, if any, at the end of the list.
Logical FDD_MULTIRAT_REPORTING B11 Yes B12 Yes

name TRX nb No
HMI FDD_MULTIRAT_REPORTING Sub-syste BSC Cell Type No
Definition Number of the strongest 3G cells to be reported by the MS in the measurement report message
Coding rules --
Mandatory rules --
Recommended --
rules
External This parameter is meaningful only if EN_3G_HO is set to enabled. If disabled, this parameter is considered as equal to zero (the MS shall report only 2G cells).
comment This parameter is broadcast on SACCH.
Internal comment --
- Significant only if EN_2G_TO_3G_CELL_RESELECTION is not disabled

Logical FDD_Qmin(BSC) B11 Yes B12 Yes
name TRX nb No
HMI FDD_Qmin Sub-syste BSC Cell Type No
Definition Minimum threshold for Ec/Io for UTRAN FDD cell re-selection.
Rec ref. 3GPP TS 05.08 Domai 2G-3G Min value -20 Coded Min 0
Coding rules 0 = -20 dB
1 = -6 dB
2 = -18 dB
3 = -8dB
4 = -16dB
5 = -10dB
6 = -14dB
7 = -12dB
Mandatory rules Equal to FDD_Qmin(MFS)
Recommended --
rules
External This parameter is broadcast on BCCH and on PBCCH if there is a PBCCH allocated in the serving cell.
comment
Internal comment --
Logical FDD_Qmin_Offset B11 Yes B12 Yes
name TRX nb No
HMI FDD_Qmin_Offset Sub-syste BSC Cell Type No
Definition Applies an offset to FDD_Qmin value
Coding rules coded on 3 bits:
0 = 0 dB,
1 = 2 dB,
2 = 4 dB,
3 = 6 dB,
4 = 8 dB,
5 = 10 dB,
6 = 12 dB,
7 = 14 dB.
Mandatory rules --
Recommended --
rules
External Available only if EN_CPICH_2G_3G_Reselection = 1
comment
Internal comment --
Logical FDD_Qoffset (BSC) B11 Yes B12 Yes
name TRX nb No
HMI FDD_Qoffset Sub-syste BSC Cell Type No
Definition Offset added to the received level average of the serving cell and of the neighbour GSM cells for UTRAN FDD cell re-selection.
Rec ref. GSM TS 05.08 Domai 2G-3G Min value -32 Coded Min 0
Coding rules Coded value (binary): Value (dB): Text displayed at the OMC
0: -32: Always select a 3G cell if possible
1: -28: -28 dB
2: -24: -24 dB
3: -20: -20 dB
4: -16: -16 dB
5: -12: -12 dB
6: -8: -8 dB
7: -4: -4 dB
8: 0: 0 dB
9: 4: 4 dB
10: 8: 8 dB
11: 12: 12 dB
12: 16: 16 dB
13: 20: 20 dB
14: 24: 24 dB
15: 28: 28 dB
Mandatory rules Equal to FDD_Qoffset(MFS)
Recommended --
rules
External This parameter is broadcast on BCCH and on PBCCH if there is a PBCCH allocated in the serving cell.
comment
Internal comment The OMC shall not display on the OMC screen the value of 32, but the corresponding text always select a 3G cell if possible
Logical FDD_REP_QUANT B11 Yes B12 Yes
name TRX nb No
HMI FDD_REP_QUANT Sub-syste BSC Cell Type No
Definition This parameter defines the measured quantity to be reported by the MS for the 3G cell.
Category System (CST) OMC-R access None (not in DLS) Type Number Unit None
Coding rules 0 : RSCP; 1 :Ec/No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The value 0 is not supported
Logical FDD_REPORTING_OFFSET B11 Yes B12 Yes
name TRX nb No
HMI FDD_REPORTING_OFFSET Sub-syste BSC Cell Type No
Definition Offset that the MS shall apply to measurements before reporting
(0 : 0, 1 : 6, 7 : 42)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment It is linked to the feature ENHANCED MEASUREMENT REPORT which is not supported in the ALU BSS.
Logical FDD_REPORTING_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI FDD_REPORTING_THRESHOLD Sub-syste BSC Cell Type No
Definition Threshold above which the MS shall report the measurements
Category System (CST) OMC-R access None (DLS) Type Threshold Unit dB
Coding rules step size = 6dB
Coded value (binary) : Value (dB)
0 : 0 : Always report the 3G neighbor cells
1 : 6 : 6 dB
2 : 12 : 12 dB
3 : 18 : 18 dB
4 : 24 : 24 dB
5 : 30 : 30 dB
6 : 36 : 36 dB
7 : 42 : Never report the 3G neighbor cells
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment It is linked to the feature ENHANCED MEASUREMENT REPORT which is not supported in the ALU BSS.
Logical FDD_RSCPmin B11 Yes B12 Yes
name TRX nb No
HMI FDD_RSCPmin Sub-syste BSC Cell Type No
Definition Minimum threshold of RSCP for UTRAN FDD cell re-selection.
Coding rules coded on 4bits:
0 = -114 dBm,
1 = -112 dBm,
2 = -110 dBm,
3 = -108 dBm,
4 = -106 dBm,
5 = -104 dBm,
6 = -102 dBm,
7 = -100 dBm,
8 = -98 dBm,
9 = -96 dBm,
10 = -94 dBm,
11 = -92 dBm,
12 = -90 dBm,
13 = -88 dBm,
14 = -86 dBm,
15 = -84 dBm.
Mandatory rules --
Recommended --
rules
External Available only if EN_CPICH_2G_3G_Reselection=1
comment
Internal comment --
Logical Filter_Suspend_Cause B11 Yes B12 Yes
name TRX nb No
HMI Filter_Suspend_Cause Sub-syste BSC Cell Type No
Definition This filter allows not to undertake a suspend procedure, for some specific causes.
Spec ref. GPRS MFS-BSC interface - BSCGP layer Coded Max 255
Coding rules bitmap : one bit per cause which can be filtered : (0000 0000): no filtering (0000 0001): LA update filtering (0000 0010): SMS filetring (0000 0011): LA update and
SMS filering (1111 1111): Suspend procedure inhibited whatever the cause may be.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical FORBID_AMR_NS B11 Yes B12 Yes
name TRX nb No
HMI FORBID_AMR_NS Sub-syste BSC Cell Type No
Definition Flag to forbid / allow AMR-NB or AMR-WB noise suppressor in the MS.
Rec ref. GSM 04.18 Domai GSM Min value 0 Coded Min 0
Coding rules 0: the MS can use AMR NS, 1: the MS shall not use AMR NS.
Mandatory rules --
Recommended --
rules
External Significant only if EN_AMR_FR, EN_AMR_HR or EN_AMR_WB_GMSK is set to TRUE.
comment
Internal comment --
Logical FORBID_DTXD_NH_BCCH_F B11 Yes B12 Yes
name TRX nb No
HMI FORBID_DTXD_NH_BCCH_F Sub-syste BSC Cell Type No
Definition Forbid use of downlink DTX on non hopping TCH of the BCCH TRX.
Coding rules 0 : DTX DL on non-hopping BCCH TRX is allowed; 1 : DTX DL on non-hopping BCCH TRX is forbidden
Mandatory rules --
Recommended If there are some MC modules handled by the BSC for which dynamic power allocation is applied (cf. BOP), then it is recommended to enable the use of downlink
rules DTX, so as to limit the potential degradations during the downlink transmissions on the TSs of the MC modules.
External --
comment
Internal comment --
Logical FORCE_TFO_HR_WHEN_LOADED B11 Yes B12 Yes
name TRX nb No
HMI TFO HR when loaded Sub-syste BSC Cell Type No
Definition Flag to control the establishment of TFO in Half Rate, when the cell is loaded and the call is currently allocated with an Half Rate codec type (HR or AMR-NB HR) for load
reason.
Coding rules 0 : TFO with Half Rate codec not forced,
if for load reasons the call is established with an Half Rate codec, the BSC will propose to establish TFO with all the supported codec types, including the Full Rate
ones (except the FR AMR-WB codec).
1 : TFO with Half Rate codec only,
if for load reasons the call is established with an Half Rate codec, it will stay in Half Rate even in case of TFO mismatch situation (if TFO is not possible in Half Rate on
remote side, TFO is not established).
2 : TFO with Half Rate codec preferred,
if for load reasons the call is established with an Half Rate codec, the BSC will propose in a first step to establish TFO providing only the supported Half Rate codecs
only. If TFO is not possible in Half Rate on remote side, the BSC will try to establish TFO with all the supported codec types, including the Full Rate ones (except the FR
AMR-WB codec), provided that EN_TFO_MATCH=1.
Mandatory rules --
Recommended If FORCE_TFO_HR_WHEN_LOADED=2, EN_TFO_MATCH should be set to 1

rules
External When the call is currently allocated with AMR-NB HR for load reason and when TFO is possible for that call (TFO on AMR-NB supported by the TC and configured in
comment the cell), then the BSC automatically behaviors as TFO with Half Rate codec only, and set the list of the supported codec types according to the
ADD_HR_IN_TFO_LIST parameter.
Internal comment --
Logical FORCE_TFO_VS_AMR B11 Yes B12 Yes
name TRX nb No
HMI Force TFO versus AMR Sub-syste BSC Cell Type No
Definition Flag to enable/disable the basic functions of Tandem Free Operation (TFO) for GSM FR SV1, FR SV2 and HR SV1 codec types when the current codec is AMR-NB FR or
AMR-NB HR and when TFO is not possible for the current call (TFO on AMR-NB not supported by the TC or not configured in the cell).
no TFO negotiation if AMR-NB, FR or HR, is currently used;
1: enabled,
TFO negotiation will start even if AMR-NB, FR or HR, is currently used
Mandatory rules FORCE_TFO_VS_AMR = 1 only if EN_TFO=1
Recommended --
rules
External FORCE_TFO_VS_AMR relevant only if (EN_AMR_FR = 1 or EN_AMR_HR = 1) AND (EN_TFO = 1) AND (EN_TFO_AMR_NB = 0 or not supported by the BSS)
comment
Internal comment This parameter is relevant only for legacy behavior (before support of TFO on AMR-NB), ie when EN_TFO = 1 and EN_TFO_AMR_WB = 0 and EN_TFO_AMR_NB = 0
Logical Freefactor_1 B11 Yes B12 Yes
name TRX nb No
HMI Free_Factor_1 Sub-syste BSC Cell Type No
Definition Correction factor used in the cell evaluation process to take into account the number of free TCHs in the candidate cell.
Coding rules --
Mandatory rules Freefactor_1 <= Freefactor_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules Freefactor_1 <= Freefactor_2 <= Freefactor_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules Freefactor_5 >= Freefactor_4
Recommended --
rules
External --
comment
Internal comment --
Logical Freelevel_1 B11 Yes B12 Yes
name TRX nb Yes
HMI Free_Level_1 Sub-syste BSC Cell Type No
Definition Boundary on free TCH number for determination of Freefactor of the cell.
Coding rules --
Mandatory rules Freelevel_1 < Freelevel_2
Recommended --
rules
External --
comment
name TRX nb Yes
Coding rules --
Mandatory rules Freelevel_3 > Freelevel_2 > Freelevel_1
Recommended --
rules
External --
comment
name TRX nb Yes
Coding rules --
Mandatory rules Freelevel_4 > Freelevel_3 > Freelevel_2
Recommended --
rules
External --
comment
name TRX nb Yes
Coding rules --
Mandatory rules Freelevel_4 > Freelevel_3
Recommended --
rules
External --
comment
Logical Freelevel_DR(n) B11 Yes B12 Yes
name TRX nb Yes
HMI Free_Level_DR Sub-syste BSC Cell Type Yes
Definition Minimum number of free TCHs in neighbour cell n to allow forced directed retry to cell n.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit None
Coding rules --
Mandatory rules --
Recommended Freelevel_DR > N_TCH_HO

rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type. TRXnb: Depends on TRX number
Logical FREQ_SYNC_GRAD_CONV_EDGE B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_GRAD_CONV_EDGE Sub-syste BSC Cell Type No
Definition Edge value of mean gradient to speed up OCXO correction in the BTS when mean gradient is large.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit ppb
Spec ref. BSS IP Transport: protocol & configuration Coded Max 50
Coding rules --
Mandatory rules --
Recommended --
rules
External The BTS will use the Max (FREQ_SYNC_GRAD_CONV_THRES, FREQ_SYNC_GRAD_CONV _THRES * mean gradient/ FREQ_SYNC_GRAD_CONV _EDGE) as
comment threshold value.
Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM.
Logical FREQ_SYNC_GRAD_CONV_THRES B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_GRAD_CONV_THRES Sub-syste BSC Cell Type No
Definition Threshold of mean gradient delta to trigger an OCXO correction in the BTS. This threshold is needed to be sure there is a convergence in the frequency synchro
evaluations: if the delta is smaller than this threshold and this is true 4 times one after another, then an OCXO tuning will be done.
Notes:
- The mean gradient is the calculated frequency offset.
- The mean gradient delta is the difference between the mean gradient of the current and the mean gradient of the last frequency synchro evaluation.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit ppb
Rec ref. None Domai IP Min value 0.1 Coded Min 1
Coding rules step size = 0.1
Mandatory rules --
Recommended --
rules
External The BTS will use the Max (FREQ_SYNC_GRAD_CONV_THRES, FREQ_SYNC_GRAD_CONV _THRES * mean gradient/ FREQ_SYNC_GRAD_CONV _EDGE) as
comment threshold value.
Logical FREQ_SYNC_MAX_INITIAL_EVAL B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_MAX_INITIAL_EVAL Sub-syste BSC Cell Type No
Definition Maximum number of initial frequency synchro evaluations performed by the BTS. After this number of evaluations, the BTS goes to sustained phase (even if no OCXO
correction has been triggered).
Mandatory rules --
Recommended --
rules
External --
comment
Logical FREQ_SYNC_MIN_NBR_EVAL B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_MIN_NBR_EVAL Sub-syste BSC Cell Type No
Definition Minimum number of successful frequency synchro evaluations performed by the BTS before allowing an OCXO correction. It is used during initial and sustained phases.
Successful evaluation means that FREQ_SYNC_SUCCESS_RATIO is fulfilled and no outlier is detected.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical FREQ_SYNC_POLL_PER_EVAL B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_POLL_PER_EVAL Sub-syste
BSC Cell Type No
name InstanceBTS RMS No
Definition Number of times the frequency synchro polling is performed by the BTS for measuring the minimum clock difference between the BTS and the frequency synchro time
server. It is used during initial and sustained phases.
Coding rules --
Mandatory rules --
Recommended --
rules
External With the default values of FREQ_SYNC_POLL_PER_EVAL and FREQ_SYNC_POLLING_TIME_SUSTAINED, the evaluation task (in sustained phase) will be started
once
comment time per day (96x900sec = 24h): This allows typically to get one low-traffic period on the IP network (with low delays to the time server) during one evaluation period
Note: Significant change should be obtained with modifications multiple of 10.

Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM
Logical FREQ_SYNC_POLLING_TIME_INITIAL B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_POLLING_TIME_INITIAL Sub-syste BSC Cell Type No
Definition Time between two pollings performed by the BTS to the frequency synchro time server. This timer is used during the initial phase, i.e. until the frequency synchro
algorithm triggers the first OCXO correction or until FREQ_SYNC_MAX_INITIAL_EVAL initial frequency synchro evaluations.
Coding rules step size = 10 sec
Mandatory rules --
Recommended Alcatel-Lucent recommends to set a value large enough to avoid the overload of the frequency synchro time server.
rules FREQ_SYNC_POLLING_TIME_INITIAL should not be larger than FREQ_SYNC_POLLING_TIME_SUSTAINED.
Anyway, the BTS will use the Min(FREQ_SYNC_POLLING_TIME_INITIAL, FREQ_SYNC_POLLING_TIME_SUSTAINED) value.
External --
comment
Logical FREQ_SYNC_POLLING_TIME_SUSTAINED B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_POLLING_TIME_SUSTAINED Sub-syste BSC Cell Type No
Definition Time between two pollings performed by the BTS to the frequency synchro time server. This timer is used during the sustained phase, i.e. after the first OCXO correction
in the BTS or after FREQ_SYNC_MAX_INITIAL_EVAL initial frequency synchro evaluations.
Mandatory rules --
Recommended Alcatel-Lucent recommends to set a value large enough to avoid the overload of the frequency synchro time server.
rules
External With the default values of FREQ_SYNC_POLL_PER_EVAL and FREQ_SYNC_POLLING_TIME_SUSTAINED, the evaluation task (in sustained phase) will be started
once
comment time per day (96x900sec = 24h): This allows typically to get one low-traffic period on the IP network (with low delays to the time server) during one evaluation
period.
Logical FREQ_SYNC_SUCCESS_RATIO B11 Yes B12 Yes
name TRX nb No
HMI FREQ_SYNC_SUCCESS_RATIO Sub-syste BSC Cell Type No
Definition Ratio of successful pollings performed by the BTS to the frequency synchro time server before accepting an evaluation.
Remark: Successful means that there is a response from the frequency synchro time server and the response is usable by the BTS.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit %
Mandatory rules --
Recommended --
rules
External --
comment
Logical FREQUENCY_RANGE B11 Yes B12 Yes
name TRX nb No
HMI FREQUENCY_RANGE Sub-syste BSC Cell Type No
Definition This parameter indicates the frequency range of the cell.
Coding rules 0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850, 7..255: for future use. The parameter shall be coded
over 8 bits as a provision for future frequency bands support.
Mandatory rules - if FREQUENCY_RANGE = "GSM-DCS" then CELL_PARTITION_TYPE must be equal to "Concentric" .
- The micro concentric, mini concentric and indoor concentric cells must be multiband (the allowed FREQUENCY_RANGE is PGSM-DCS1800 or
EGSM-DCS1800). This restriction does not apply to the external cells.
- The frequency range of an extended inner cell has to be the same as the frequency range of the corresponding extended outer cell, where PGSM (0) and EGSM (2)
are here considered as belonging to the same frequency range.
- When FREQUENCY_RANGE is PGSM-DCS1800 or EGSM-DCS1800 (case of multiband cell) then the supporting sector cannot work in coverage mode (ie.
COVERAGE_MODE = not activated).
The OMC-R checks the consistency between the setting of FREQUENCY_RANGE and PLMN_FREQUENCY_BANDS parameters:
- At cell creation
- When the value of FREQUENCY_RANGE parameter is modified.
However, no check is performed when the PLMN_FREQUENCY_BANDS is modified.
Only the following values of the FREQUENCY_RANGE parameter are allowed depending on the value of the PLMN_FREQUENCY_BANDS parameter:
- FREQUENCY_RANGE = PGSM (GSM900) or EGSM (GSM900) or DCS1800 or PGSM-DCS1800 or EGSM-DCS1800 if the PLMN_FREQUENCY_BANDS is set
to
"GSM900 and DCS1800 bands",
- FREQUENCY_RANGE = GSM850 or DCS1800 if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1800 bands",
- FREQUENCY_RANGE = PGSM (GSM900) or EGSM (GSM900) or DCS1900 if the PLMN_FREQUENCY_BANDS is set to "GSM900 and DCS1900 bands".
Recommended --
rules
External When the frequency range is changed from EGSM (resp. EGSM-DCS) to PGSM (resp. PGSM-DCS) or from PGSM (resp. PGSM-DCS) to EGSM (resp. EGSM-DCS),
comment then all TRXs of the cell have the preserve call flag set to FALSE
Internal comment Values 4 and "5" are for Multiband cells. Transmitted to the BTS in the BTS_CONF_DATA message.
Logical FTP_PRIORITY (BSC) m B11 Yes B12 Yes

name TRX nb No
HMI FTP_PRIORITY (BSC) Sub-syste BSC template Cell Type No
Definition BSS internal priority used by the BSC for FTP flow in IP network towards the BTS.
Spec ref. GPRS telecom presentation Coded Max 3
3: lower priority
Mandatory rules shall be equal to FTP_PRIORITY(BTS).
Recommended --
rules
External --
comment
Internal comment --
Logical GERAN_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI GERAN_PRIORITY Sub-syste BSC Cell Type No
Definition Gives the priority for the serving cell. Used for cell reselection by a LTE-capable MS/UE.
Coding rules step size = 1,
0 is the lowest priority, 7 the highest
Mandatory rules When a given serving 2G cell has at least one neighbour 3G or LTE cell for reselection, then GERAN_PRIORITY shall be different from any priority (PRIORITY_3G and
PRIORITY_LTE) of its neighbour 3G and LTE cells for reselection, and different from the DEFAULT_PRIORITY_3G of its BSS.
Recommended --
rules
Internal comment --
Logical GSL_PRIORITY (BSC) B11 Yes B12 Yes
name TRX nb No
HMI GSL_PRIORITY (BSC) Sub-syste BSC Cell Type No
Definition BSS internal priority used by the GSL flow in IP network
3: lower priority
Mandatory rules Shall be equal to GSL_PRIORITY (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical GSM_PHASE B11 Yes B12 Yes
name TRX nb No
HMI GSM_PHASE Sub-syste BSC Cell Type No
Definition This flag indicates the GSM Phase used by the BSC to format messages towards the MSC.
Coding rules 0: GSM Phase 1, 1: GSM Phase 2
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type.The value indicated here is for implementation purposes.
comment
Internal comment --
Logical H_LOAD_OBJ B11 Yes B12 Yes
name TRX nb Yes
HMI H_LOAD_OBJ Sub-syste BSC Cell Type Yes
Definition High threshold on busy TCH timeslots percentage to reduce MIN_DWELL_TIME variable.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit %
Coding rules step size = 10%
Mandatory rules H_LOAD_OBJ >= L_LOAD_OBJ
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer. TRXnb: Depends on TRX number
Logical H_MIN_DWELL_TIME B11 Yes B12 Yes
name TRX nb No
HMI H_MIN_DWELL_TIME Sub-syste BSC Cell Type No
Definition Maximum allowed value for MIN_DWELL_TIME variable.
Coding rules --
Mandatory rules H_MIN_DWELL_TIME >= L_MIN_DWELL_TIME
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer.
Logical H_PRIO B11 Yes B12 Yes
name TRX nb No
HMI H_PRIO Sub-syste BSC Cell Type No
Definition Hysteresis used in the priority reselection algorithm by a LTE-capable MS/UE.
Coded value (decimal): Value (dB): Text displayed at the OMC
0: 6: Rule disabled
1: 5: 5 dB
2: 4: 4 dB
3: 3: 3 dB
Mandatory rules --
Recommended --
rules
Internal comment --
Logical HIGH_TRAFFIC_LOAD B11 Yes B12 Yes
name TRX nb Yes
HMI HIGH_TRAFFIC_LOAD Sub-syste BSC Cell Type No
Definition Load threshold used to determine when traffic load is high for circuit switched calls.
Coding rules --
Mandatory rules - HIGH_TRAFFIC_LOAD >= LOW_TRAFFIC_LOAD

- HIGH_TRAFFIC_LOAD >= THR_CELL_LOAD_3G_REJECT (when THR_CELL_LOAD_3G_REJECT <> 100%).
- HIGH_TRAFFIC_LOAD >= THR_CELL_LOAD_LTE_REJECT (when THR_CELL_LOAD_LTE_REJECT <> 100%).
Recommended --
rules
External Default value depends on the number of TRX in the cell (see TRXnb default value). The value indicated here is for implementation purposes.
comment
Internal comment --
Logical HIGH_TRAFFIC_LOAD_GPRS B11 Yes B12 Yes
name TRX nb Yes
HMI HIGH_TRAFFIC_LOAD_GPRS Sub-syste BSC Cell Type No
Definition Load threshold used to determine a certain margin of radio timeslots reserved for CS traffic between two sending of the BSCGP RR Allocation Indication messages. The
threshold is expressed in percentage of the radio timeslots available in the cell.
Coding rules --
Mandatory rules --
Recommended --
rules
External The margin of radio timeslots reserved for CS traffic can be computed as follows:
comment
(100 - HIGH_TRAFFIC_LOAD_GPRS)/100*NB_TS
where NB_TS is the number of radio timeslots available in the cell.

Internal comment --
Logical HO_INTERCELL_ALLOWED B11 Yes B12 Yes
name TRX nb No
HMI INTERCELL_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the execution of all outgoing intercell handovers.
It does not applied to the internal handover initiated by the MSC.
Mandatory rules --
Recommended --
rules
External Valid for both TCH and SDCCH. This parameter has no influence on Directed Retry
comment
Internal comment --
Logical HO_INTRACELL_ALLOWED B11 Yes B12 Yes
name TRX nb No
HMI INTRACELL_HO Sub-syste BSC Cell Type No
Definition This flag enables/disables the execution of intracell handovers.
It does not apply to the internal handover initiated by the MSC.
Mandatory rules --
Recommended --
rules
External Valid for both TCH and SDCCH.
comment The flags specific to the TFO feature, I.e. EN_TFO, EN_TFO_MATCH, EN_TFO_OPT,
EN_IPE_PREF_CODEC_TYPE, are set independently of the flag HO_INTRACELL_ALLOWED.
Additionally, the flag related to handover cause 30, EN_RETURN_CS_ZONE_HO is set
independently of the flag HO_INTRACELL_ALLOWED.
The handovers for TFO reasons (cause 29) and RAE4 reasons (cause 30) can therefore
be performed even if HO_INTRACELL_ALLOWED = disabled.
Internal comment --
Logical HO_MARGIN_DIST(0,n) B11 Yes B12 Yes
name TRX nb No
HMI HO_MARGIN_DIST Sub-syste BSC Cell Type Yes
Definition Criterion for candidate neighbour cell filtering on distance handover causes.
Rec ref. None Domai GSM Min value -127 Coded Min -127
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical HO_MARGIN_LEV(0,n) B11 Yes B12 Yes
name TRX nb No
HMI HO_MARGIN_LEV Sub-syste BSC Cell Type Yes
Definition Criterion for candidate neighbour cell filtering on level handover causes.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical HO_MARGIN_QUAL(0,n) B11 Yes B12 Yes
name TRX nb No
HMI HO_MARGIN_QUAL Sub-syste BSC Cell Type Yes
Definition Criterion for candidate neighbour cell filtering on quality handover causes
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical HO_SDCCH_INHIBIT B11 Yes B12 Yes
name TRX nb No
HMI SDCCH_HO Sub-syste BSC Cell Type Yes
Definition The flag inhibits/enables the execution of SDCCH handovers.
Coding rules 0: SDCCH HO enabled1: SDCCH HO disabled
Mandatory rules --
Recommended --
rules
External This parameter has no influence on Directed Retry
comment
Internal comment CT: Depends on Cell Type
Logical HOmargin (0,n) B11 Yes B12 Yes
name TRX nb No
HMI HO_MARGIN Sub-syste BSC Cell Type Yes
Definition Difference in power budget (PBGT) between cell(0) and cell(n) which is required for a power budget HO.
Rec ref. GSM TS 05.08 Domai GSM Min value -127 Coded Min -127
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical HR_ENABLED B11 Yes B12 Yes
name TRX nb No
HMI HR_ENABLED Sub-syste BSC Cell Type No
Definition This flag controls if Half Rate TCH is enabled.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical I_TX_LAPD B11 Yes B12 Yes
name TRX nb No
HMI I_TX_LAPD Sub-syste BSC Cell Type No
Definition Maximum LAPD transmission queue length.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IGNORE_2MBIT_FAIL B11 Yes B12 Yes
name TRX nb No
HMI IGNORE_2Mbit_FAILURE Sub-syste BSC Cell Type No
Definition This flag indicates whether or not a transmission alarm triggers the telecom defence activities (call release, blocking messages towards MSC). Note that the O&M
activities are not dependent on this flag.
Coding rules 0: transmission alarms are not ignored and the telecom defence activities (call release, blocking messages towards MSC) are triggered;
1: transmission alarms are ignored and telecom defence activities (call release, blocking messages towards MSC) are not triggered;
Mandatory rules --
Recommended If BSS_TRANSPORT_MODE = IP, should be set to FALSE. Due to TDM switching on TC side, there is no more interaction between Atermux and ATR failures.
rules
External --
comment
Internal comment --
Logical INBAND_PAGING_THR B11 Yes B12 Yes
name TRX nb No
HMI INBAND_PAGING_THR Sub-syste BSC Cell Type No
Definition If the eMLPP priority included in the Paging message from the MSC is higher than or equal to this parameter, then the BSS shall trigger in-band paging within cells, that are
identified to be paged from the PAGING message, and that have existing VGC active.
000 : deactivation of inband paging
001 : call priority level 4 (lowest priority)
010 : call priority level 3
110 : call priority level B
111 : call priority level A (highest priority)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IND_TRAFFIC_LOAD B11 Yes B12 Yes
name TRX nb Yes
HMI IND_TRAFFIC_LOAD Sub-syste BSC Cell Type No
Definition Load threshold used to determine when traffic load is indefinite for circuit switched calls.
Coding rules --
Mandatory rules --
Recommended IND_TRAFFIC_LOAD = 0 OR LOW_TRAFFIC_LOAD <= IND_TRAFFIC_LOAD <= HIGH_TRAFFIC_LOAD

rules
External --
comment
Logical INTAVE B11 Yes B12 Yes
name TRX nb No
HMI INTAVE Sub-syste BSC Cell Type No
Definition Averaging period for interference measurements on idle channels.
Category Site (CAE) OMC-R access Changeable Type Timer Unit Samfr
Coding rules step size=1 Samfr
Mandatory rules INTAVE < T_INTRF_L3
Recommended --
rules
External --
comment
Internal comment - Transmitted to the BTS in the BTS_CONF_DATA message
- If EN_INTFBD_PM = 0, idle TCH are considered, else idle TCH, SDCCH and PDCH
Logical INTFBD1 B11 Yes B12 Yes
name TRX nb No
HMI Interference bands 1-2 limit Sub-syste BSC Cell Type No
Definition Limit between interference band 1 and interference band 2.
Rec ref. GSM TS 08.58 Domai GSM Min value -110 Coded Min 0
Coding rules Coded over 6 bits: 0: -110 dBm, 1: -109 dBm...63: -47 dBm
Mandatory rules INTFBD1 < INTFBD2
Recommended --
rules
External --
comment
name TRX nb No
Mandatory rules INTFBD3 > INTFBD2 > INTFBD1
Recommended --
rules
External --
comment
name TRX nb No
Recommended --
rules
External --
comment
name TRX nb No
Recommended --
rules
External --
comment
name TRX nb No
HMI Interference band 5 upper limit Sub-syste BSC Cell Type No
Definition Upper limit of interference band 5.
Category System (CST) OMC-R access Displayed Type Number Unit dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical IP_CONGESTION_FILTER_WS B11 Yes B12 Yes
name TRX nb No
HMI IP_CONGESTION_FILTER_WS Sub-syste BSC Cell Type No
Definition This parameter is used by the detection mechanism of CS IP congestion situation on the Abis interface, which relies on the BTS to measure the UL and DL delays of the IP
packets sent to/received from the TC. This parameter corresponds to the duration of the observation, during which the BTS will count the excessive jitter events (ie the
number of UL or DL packets for which the delay is IP_CONGESTION_JITTER_THRESHOLD higher than the overall measured minimum delay).
If during that duration, the number of excessive jitter events measured in one direction is greater than IP_CONGESTION_PREVENTIVE_THRESHOLD, then a first level of
CS IP congestion case is detected by the BTS.
Only one case of CS IP congestion can be notified per IP_CONGESTION_FILTER_WS seconds.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit sec
Spec ref. TC/BTS Interface Coded Max 100
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML
Logical IP_CONGESTION_JITTER_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IP_CONGESTION_JITTER_THRESHOLD Sub-syste BSC Cell Type No
packets sent to/received from the TC. This parameter corresponds to the excessive jitter event criteria, ie such event is identified and counted when the UL or DL delay
of the current packet is greater than IP_CONGESTION_JITTER_THRESHOLD milliseconds from the overall measured minimum delay.
If during IP_CONGESTION_FILTER_WS, the number of excessive jitter events measured in one direction is greater than IP_CONGESTION_PREVENTIVE_THRESHOLD,
then a first level of CS IP congestion case is detected by the BTS
Category Network (CDE) OMC-R access None (DLS) Type Threshold Unit ms
Mandatory rules --
Recommended --
rules
External --
comment
- No jitter is assumed to exist on a satellite links / no jitter higher than 40 ms (current max value of the parameter) would anyway be acceptable wrt voice quality
degradations
Logical IP_CONGESTION_PREVENTIVE_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IP_CONGESTION_PREVENTIVE_THRESHOLD Sub-syste BSC Cell Type No
packets sent to/received from the TC. This parameter corresponds to the minimum number of UL or DL IP packets, which have an excessive jitter.
If during IP_CONGESTION_FILTER_WS, the number of excessive jitter events measured in one direction is greater than this minimum threshold, then a first level of CS IP
congestion case is detected by the BTS.
Mandatory rules --
Recommended --
rules
External --
comment
Logical IP_CONGESTION_TIMER B11 Yes B12 Yes
name TRX nb No
HMI IP_CONGESTION_TIMER Sub-syste BSC Cell Type No
Definition Duration during which the BSC considers the Abis interface suffers from CS IP congestion situation. After the reception of the message IP_Congestion_Indication from a
given BTS, the BSC refuses any new TCH establishments on any TRX linked to that BTS, as long as IP_CONGESTION_TIMER is running. At timer expiry, the BSC
considers that the BTS has left IP congestion state.
Mandatory rules --
Recommended --
rules
External This timer is not relevant when EN_IP_CONGESTION_1ST_LEVEL is disabled.
comment
Internal comment --
Logical IPGCH_PACKET_SIZE B11 Yes B12 Yes
name TRX nb No
HMI IPGCH_PACKET_SIZE Sub-syste BSC Cell Type No
name Instance Abis group RMS No
Definition Maximum IPGCH packet size (including TCP/UDP/IP headers) used by IPGCHC and IPGCHU.
Spec ref. GPRS MFS-BTS interface - IPGCH stack Coded Max 15
Coding rules Step size =100
Mandatory rules IPGCH_PACKET_SIZE <= E1_MTU in case of IPoE1
Recommended - IPGCH sending window size (ie 112 on G3 TRE / 496 on higher TRE) x IPGCH_PACKET_SIZE / round trip delay between MFS and BTS >= maximum theoretical
rules throughput possible on the TRE (ex: CS-4 throughput on 8 PDCHs = 160 kbps / MCS-9 throughput on 16 PDCHs = 947 kbps). If that recommendation were not followed
(typically in case of BTS to MFS transport over satellite (round_trip_delay >= 500ms)), the PS throughput would be degraded due to stalled IPGCH sending window.
- The operator must ensure that the MTU in its network is greater than IPGCH_PACKET_SIZE. If it is not the case, IPGCH does not work.
External The value of this parameter is only indicative: it is not applied directly because some TRE hardware constraints have to be taken into account when computing the TCP
comment MSS (Maximum Segment Size) and the IPGCHU MISS (Maximum IPGCHU Segment Size) values.
This parameter shall be set like a Network MTU (Maximum Transmission Unit), i.e. by taking into account the size of the TCP/IP headers (for the TCP MSS) and the size
of the UDP/IP/IPGCH headers (for the IPGCHU MISS).
Change on this parameter applies only after a TCP connection reestablishment.
This parameter impacts the jitter experienced by the CS traffic.
Internal comment - Sent by BSC to MFS via BSCGP (Abis group object unknown by MFS O&M).
- Sent by BSC to BTS via OML.
- 112=IPGCHU_UDP_MAX_WINDOW_SIZE_G3.
-2000 =IPGCHU_UDP_MAX_WINDOW_SIZE_G4_G5 =IPGCHU_UDP_MAX_WINDOW_SIZE_GP =IPGCHU_UDP_MAX_WINDOW_SIZE_MC
Logical IPGCHC_TCP_PORT_BTS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHC_TCP_PORT_BTS Sub-syste BSC Cell Type No
name Instance TRX RMS No
Definition Value of the TCP port used on BTS side by one TRE for the IPGCHC protocol and sent to the MFS by the BSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Value is received from the BTS (see IPGCHC_TCP_PORT_BTS (BTS) and the DLS is updated accordingly. The default value is used to initialise the DLS but shall be
updated by the right value coming from the BTS.
- Sent by the BSC to the MFS via BSCGP: state_change.
- Min = hD100, Max = hD4FF
- Alignement of the BTP on BSC DLS content.
Logical IPGCHU_DELAY_HIGH_THRES_DL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_DELAY_HIGH_THRES_DL Sub-syste BSC Cell Type No
Definition For IPGCHU, threshold on measured differential delay in downlink for a given Abis group (second congestion threshold).
When the measured differential delay exceeds this threshold, a very pessimistic BE shaping is applied in downlink (cf. the IPGCHU_BW_MIN_CONG_DL parameter).
Category Site (CAE) OMC-R access Changeable Type Threshold Unit ms

Mandatory rules IPGCHU_DELAY_HIGH_THRES_DL >= IPGCHU_DELAY_LOW_THRES_DL
Recommended 6 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL => IPGCHU_DELAY_HIGH_THRES_DL (because there are 6 IPGCH polling request contexts for
rules each PTU at MFS side).
External --
comment
Internal comment - Sent by the BSC to MFS via BSCGP.
Logical IPGCHU_DELAY_HIGH_THRES_UL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_DELAY_HIGH_THRES_UL Sub-syste BSC Cell Type No
Definition For IPGCHU, threshold on measured differential delay in uplink for a given Abis group (second congestion threshold).
When the measured differential delay exceeds this threshold, a very pessimistic BE shaping is applied in uplink on the concerned TRE(s) (cf. the
IPGCHU_BW_MIN_CONG_UL parameter.
Mandatory rules IPGCHU_DELAY_HIGH_THRES_UL >= IPGCHU_DELAY_LOW_THRES_UL
Recommended 6 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL => IPGCHU_DELAY_HIGH_THRES_UL (because there are 6 IPGCH polling request contexts for
rules each TRE at BTS side).
External --
comment
Internal comment -Sent by the BSC to MFS via BSCGP.
- Provided by MFS to BTS.
Logical IPGCHU_DELAY_LOW_THRES_DL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_DELAY_LOW_THRES_DL Sub-syste BSC Cell Type No
Definition For IPGCHU, threshold on measured differential delay in downlink for a given Abis group (first congestion threshold).
Below this threshold, the system is in nominal mode without any regulation (no BE shaping in downlink).
Mandatory rules IPGCHU_DELAY_HIGH_THRES_DL >= IPGCHU_DELAY_LOW_THRES_DL
Recommended --
rules
External --
comment
Logical IPGCHU_DELAY_LOW_THRES_UL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_DELAY_LOW_THRES_UL Sub-syste BSC Cell Type No
Definition For IPGCHU, threshold on measured differential delay in uplink for a given Abis group (first congestion threshold).
Below this threshold, the system is in nominal mode without any regulation (no BE shaping in uplink on the concerned TRE(s))
Mandatory rules IPGCHU_DELAY_HIGH_THRES_UL >= IPGCHU_DELAY_LOW_THRES_UL
Recommended --
rules
External --
comment
- Provided by MFS to BTS.
Logical IPGSL_IP_Address_BSCside (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_IP_Address_BSCside Sub-syste BSC Cell Type No
name Instance IP-GSL RMS No
Definition IP address of the IPGSL link on BSC side
Spec ref. GPRS MFS-BSC interface - BSCGP layer Coded Max
Recommended --
rules
External Parameter change: After the change of this parameter (via the START_BSS_IP_ADDRESS_BSC) by the operator from the BSC terminal, the MFS will perform an
comment automatic reset of all the GPs connected to this BSS (PS traffic is interrupted in the BSS).
Internal comment - The OMC stay aware of the parameter value on BSC side for displaying, and also for synchronization (when the value changed on BSC side, the OMC realigns the
value on MFS side).
- the coded default value implemented on BSC-> OMC is 15 blanks string; that dummy value indicates that the operator does not provide any IP address yet. It is not
displayed.
- This IP address is computed by the BSC (per CCP board) from the START_BSS_IP_ADDRESS_BSC.
Logical IPGSL_IP_Address_MFSside (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_IP_Address_MFSside Sub-syste BSC Cell Type No
Definition IP address of the IPGSL link on MFS side.
Category Site (CAE) OMC-R access Virtual changeable Type IP address Unit None
Spec ref. GPRS MFS-BSC interface - BSCGP layer Coded Max
Mandatory rules - Equal to IPGSL_IP_Address_MFSside (MFS)

Recommended --
rules
External --
comment
Internal comment - Provided by the OMC to the BSC.
- The OMC stay aware of the parameter value on MFS side for displaying, and also for synchronization (when the value changed on MFS side, the OMC realigns the
value on BSC side).
- 2 coded default values are implemented (15 blanks string on BSC-> OMC, and empty string on OMC-> BSC); those dummy values indicate that the operator does not
Logical IPGSL_MSS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_MSS (BSC) Sub-syste BSC Cell Type No
Definition MSS (Maximum Segment Size) value used by the TCP stack for IPGSL protocol in the BSC
Category System (CST) OMC-R access None (not in DLS) Type Number Unit byte
Mandatory rules --
Recommended IPGSL_MSS (BSC) = IPGSL_MSS (MFS)

rules IPGSL_MSS >= 264 (max size of one BSCGP message)
External To avoid TCP segmentation, the TCP MSS shall be > max size of BSCGP messages (264).
comment
Internal comment - Used to configure the TCP stacks
Logical IPGSL_TCP_PORT_BSCside (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_TCP_PORT_BSCside Sub-syste BSC Cell Type No
Definition TCP port number used by each CCP board of the BSC for IPGSL interface.
Category Site (CAE) OMC-R access Displayed Type Number Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - The OMC stay aware of the parameter value on BSC side for displaying, and also for synchronization (in case the value is changed on BSC side, the OMC realigns
the value on MFS side; however this will not happen because only one value is possible).
- Only one port value is used: indeed, TCP uses (Server IP address + Server TCP Port + Client IP Address + Client TCP Port) to distinguish the different connections.
Note: in order to distinguish easily each side of the protocol, different value at BSC side and MFS side could be used, but, by default, the same value is used by BSC
and MFS.
- Min=hCD90, Max=hCD91
Logical IPGSL_TCP_PORT_MFSside (BSC) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_TCP_PORT_MFSside Sub-syste BSC Cell Type No
Definition TCP port number for the MFS side of the IPGSL link, used by the BSC.
Coding rules --
Mandatory rules equal to IPGSL_TCP_PORT_MFSside (MFS)
Recommended --
rules
External --
comment
Internal comment - The OMC stay aware of the parameter value on MFS side for displaying, and also for synchronization (in case the value is changed on MFS side, the OMC realigns
the value on BSC side, however this will not happen because only one value is possible).
- one value is used: h'CD90
Logical IURG_IP_SUBNET_MASK_BSC B11 Yes B12 Yes
name TRX nb No
HMI ADD_FUNC_IP_SUBNET_MASK_BSC Sub-syste BSC Cell Type No
Definition Mask of the subnet where is allocated the range of BSC addresses used for telecom protocols for the feature support of the Iur-g+ interface.
Mandatory rules --

rules
change.
displayed.
Logical IURG_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI IURG_PRIORITY Sub-syste BSC Cell Type No
Definition BSS internal priority used for the Iurg signaling over IP flow (M3UA/SCTP signalling between BSC and RNC, on Iurg interface).
3: lower priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IURG_SCTP_ENDPOINT_IP_ADDRESS_1 B11 Yes B12 Yes
name TRX nb No
HMI IURG_SCTP_ENDPOINT_IP_ADDRESS_1 Sub-syste BSC Cell Type No
Definition Primary IP address of a SCTP endpoint (used by M3UA protocol) on the RNC side.
Mandatory rules - IURG_SCTP_ENDPOINT_IP_ADDRESS_1 and IURG_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one RNC.
Recommended --
rules
External Parameter change: before any modification, the operator must lock the associated Iur-g Signalling Link
comment
Internal comment - 2 coded default values are implemented (15 blanks string on BSC-> OMC, and empty string on OMC-> BSC); those dummy values indicate that the operator does not
Logical IURG_SCTP_ENDPOINT_IP_ADDRESS_2 B11 Yes B12 Yes
name TRX nb No
HMI IURG_SCTP_ENDPOINT_IP_ADDRESS_2 Sub-syste BSC Cell Type No
Definition Secondary IP address of a SCTP endpoint (used by M3UA protocol) on the RNC side.
It is an optional address used in case of SCTP multihoming in RNC side.
Recommended --
rules
comment
-The IP address is coded on 32 bits in the DLS.
Logical IURG_SCTP_ENDPOINT_LIST B11 Yes B12 Yes
name TRX nb No
HMI IURG_SCTP_ENDPOINT_LIST Sub-syste BSC Cell Type No
name Instance RNC RMS No
Definition List of the SCTP endpoints (used by M3UA protocol) on the RNC side.
Coding rules coded as an array of 4 entries
Each entry is an SCTP endpoint, composed of IURG_SCTP_ENDPOINT_IP_ADDRESS_1, IURG_SCTP_ENDPOINT_PORT and
IURG_SCTP_ENDPOINT_IP_ADDRESS_2
Mandatory rules When the RNC_TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the IURG_SCTP_ENDPOINT_LIST must be equal or greater than
RNC_MIN_NB_ACTIVE_IPSP
Recommended --
rules
External Parameter change: before any modification, the operator must lock all the Iur-g Signalling Links of the modified RNC
comment
Internal comment - MAX_NB_IURG_SCTP_ENDPOINT = 4
- A coded default value is not needed since the operator cannot create a RNC without configuring its list of SCTP endpoints (no dummy value needed)
Logical IURG_SCTP_ENDPOINT_PORT B11 Yes B12 Yes
name TRX nb No
HMI IURG_SCTP_ENDPOINT_PORT Sub-syste BSC Cell Type No
Definition Port of a SCTP endpoint (used by M3UA protocol) on the RNC side.
Coding rules --
Mandatory rules IURG_SCTP_ENDPOINT_IP_ADDRESS_1 and IURG_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one RNC
Recommended --
rules
comment
Internal comment - A coded default value is not needed since the operator cannot create a RNC SCTP endpoint without configuring its port number (no dummy value needed).
Logical K_GSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI K_GSL (BSC) Sub-syste BSC Cell Type No
Definition Maximum number of outstanding I frames on a GSL link.
Spec ref. GPRS MFS-BSC interface - GSL stack Coded Max 16
Coding rules --
Mandatory rules --
Recommended It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Ater satellite links:
rules - K_GSL = 7 if GPRS traffic is carried through Ater terrestrial links in all BSC of the MFS.
- K_GSL = 16 if GPRS traffic is carried through Ater satellite links in at least one BSC of the MFS.
External --
comment
Internal comment --
Logical K_VAL_OML_16K_satellite B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_OML_16K_satellite Sub-syste BSC Cell Type No
Definition LAPD window size on OML in the BSC for 16Kbit/s link and satellite connection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is not applicable to the uplink. The BTS (OMU) value is hardcoded.
Logical K_VAL_OML_16K_terrestrial B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_OML_16K_terrestrial Sub-syste BSC Cell Type No
Definition LAPD window size on OML in the BSC for 16Kbit/s link and terrestrial connection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical K_VAL_OML_64K_satellite B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_OML_64K_satellite Sub-syste BSC Cell Type No
Definition LAPD window size on OML in the BSC for 64Kbit/s link and satellite connection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical K_VAL_OML_64K_terrestrial B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_OML_64K_terrestrial Sub-syste BSC Cell Type No
Definition LAPD window size on OML in the BSC for 64Kbit/s link and terrestrial connection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical K_VAL_RSL_16K_satellite B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_RSL_16K_satellite Sub-syste BSC Cell Type No
Definition LAPD window size on 16 Kbit/s RSL for satellite connections.
Coding rules --
Mandatory rules --
Recommended Only values strictly lower than 16 are compatible with G2 BTS, hence 15 is chosen as default value. There is a small loss of throughput on the RSL when going from
rules 16 to 15.
The setting to 15 was due in B7 to migration in presence of FUMO, we could envisage to use 16 in B11 (only BTS Evolium). But as
this would lead to a small increase of the bandwidth and would require qualifying again the satellite connection in load situation, this has not been retained (as not
retained in all the previous releases).
External --
comment
Internal comment This value is copied to the BTS parameter K_VAL_RSL, when the RSL is carried by a 16 kbit/s channel on a satellite connection.
With 540 ms round trip time and an average LAPD frame = 33 bytes, the RSL average throughput is 8.1 kbitps with K_VAL_RSL_16K_satellite = 16 (maximum), and
7.6 kbitps with K_VAL_RSL_16K_satellite = 15 (default).
Logical K_VAL_RSL_16K_terrestrial B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_RSL_16K_terrestrial Sub-syste BSC Cell Type No
Definition LAPD window size on 16 Kbit/s RSL for terrestrial connections.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This value is copied to the BTS parameter K_VAL_RSL, when the RSL is carried by a 16 Kbit/s channel on a terrestrial connection.
Logical K_VAL_RSL_64K_satellite B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_RSL_64K_satellite Sub-syste BSC Cell Type No
Definition LAPD window size on 64 Kbit/s RSL for satellite connections.
Coding rules --
Mandatory rules --
Recommended Only values strictly lower than 16 are compatible with G2 BTS, hence 15 is chosen as default value. There is a small loss of throughput on the RSL when going from
rules 16 to 15.
The setting to 15 was due in B7 to migration in presence of FUMO, we could envisage to use 16 in B11 (only BTS Evolium). But as
this would lead to a small increase of the bandwidth and would require qualifying again the satellite connection in load situation, this has not been retained (as not
retained in all the previous releases).
External --
comment
Internal comment This value is copied to the BTS parameter K_VAL_RSL, when the RSL is carried by a 64 kbit/s channel on a satellite connection.
With 540ms round trip time and an average LAPD frame = 33 bytes, the RSL average throughput is 8.1 kbitps with K_VAL_RSL_64K_satellite = 16 (maximum), and 7.6
kbitps with K_VAL_RSL_64K_satellite = 15 (default).
Logical K_VAL_RSL_64K_terrestrial B11 Yes B12 Yes
name TRX nb No
HMI K_VAL_RSL_64K_terrestrial Sub-syste BSC Cell Type No
Definition LAPD window size on 64 Kbit/s RSL for terrestrial connections.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This value is copied to the BTS parameter K_VAL_RSL, when the RSL is carried by a 64 Kbit/s channel on a terrestrial connection.
Logical KEEP_CODEC_HO B11 Yes B12 Yes
name TRX nb No
HMI Keep codec on handover Sub-syste BSC Cell Type No
Definition Indicates if the BSC tries to keep the same codec for internal incoming handovers.
Coding rules 0:free choice of the codec ; 1:try to maintain codec for TFO calls only; 2: try to maintain codec for all calls
Mandatory rules --
Recommended --
rules
External - significant only if EN_AUP_OVER_IP is disabled
comment
Internal comment --
Logical L_LOAD_OBJ B11 Yes B12 Yes
name TRX nb Yes
HMI L_LOAD_OBJ Sub-syste BSC Cell Type Yes
Definition Low threshold on busy TCH timeslots percentage to increase MIN_DWELL_TIME variable.
Mandatory rules L_LOAD_OBJ <= H_LOAD_OBJ
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer. TRXnb: Depends on TRX number
Logical L_MIN_DWELL_TIME B11 Yes B12 Yes
name TRX nb No
HMI L_MIN_DWELL_TIME Sub-syste BSC Cell Type No
Definition Minimum allowed value for MIN_DWELL_TIME variable.
Coding rules --
Mandatory rules L_MIN_DWELL_TIME <= H_MIN_DWELL_TIME
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer
Logical L_RXLEV_CPT_HO(0,n) B11 Yes B12 Yes
name TRX nb No
HMI L_RXLEV_CPT_HO Sub-syste BSC Cell Type No
Definition Minimum received downlink level from cell n for umbrella to neighbour lower layer cell n handover or from classical band to preferred band cell n handover.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit dBm
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical L_RXLEV_DL_H B11 Yes B12 Yes
name TRX nb No
HMI L_RXLEV_DL_H Sub-syste BSC Cell Type Yes
Definition Downlink level threshold for handover.
Mandatory rules L_RXLEV_DL_H < U_RXLEV_DL_P.

L_RXLEV_DL_H < RXLEV_DL_IH
Recommended L_RXLEV_D_H < L_RXLEV_DL_P

rules If CELL_PARTITION_TYPE = Concentric AND FREQUENCY_RANGE = PGSM or DCS1800 or EGSM or DCS 1900:
RXLEV_DL_ZONE >= L_RXLEV_DL_H (This rule only applies to concentric and monoband cell.)
External --
comment
Logical L_RXLEV_DL_P B11 Yes B12 Yes
name TRX nb No
HMI L_RXLEV_DL_P Sub-syste BSC Cell Type No
Definition Lower downlink level threshold for power control.
Mandatory rules L_RXLEV_DL_P < U_RXLEV_DL_P
Recommended --
rules
External --
comment
Internal comment --
Logical L_RXLEV_DL_P_VAMOS B11 No B12 Yes
name TRX nb No
HMI L_RXLEV_DL_P_VAMOS Sub-syste BSC Cell Type No
Definition Lower downlink level threshold for VAMOS BS power control.
Mandatory rules - L_RXLEV_DL_P_VAMOS < U_RXLEV_DL_P_VAMOS
Recommended - L_RXLEV_DL_P_VAMOS + 10 dB <= U_RXLEV_DL_P_VAMOS

rules
Internal comment --
Logical L_RXLEV_MULTIBAND_FORCED_DR(0,n) B11 No B12 Yes
name TRX nb No
HMI L_RXLEV_MULTIBAND_FORCED_DR Sub-syste BSC Cell Type No
Definition Minimum received downlink level from cell n for towards to preferred band cell n directed retry.
Mandatory rules --
Recommended --
rules
comment - Significant when EN_PREFERRED_BAND_FORCED_DR is enabled
Internal comment --
Logical L_RXLEV_NCELL_DR(n) B11 Yes B12 Yes
name TRX nb No
HMI L_RXLEV_NCELL_DR Sub-syste BSC Cell Type Yes
Definition Minimum level received from neighbour cell n to allow forced directed retry to cell n.
Coding rules Coded over 6 bits :0: -110 dBm, 1: -109 dBm...63: -47 dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical L_RXLEV_UL_H B11 Yes B12 Yes
name TRX nb No
HMI L_RXLEV_UL_H Sub-syste BSC Cell Type Yes
Definition Uplink level threshold for handover.
Mandatory rules L_RXLEV_UL_H < U_RXLEV_UL_P

L_RXLEV_UL_H < RXLEV_UL_IH
Recommended L_RXLEV_UL_H < L_RXLEV_UL_P

rules If CELL_PARTITION_TYPE = Concentric AND FREQUENCY_RANGE = PGSM or DCS1800 or EGSM or DCS 1900:
RXLEV_UL_ZONE >= L_RXLEV_UL_H (This rule only applies to concentric and monoband cell.)
External --
comment
Logical L_RXLEV_UL_P B11 Yes B12 Yes
name TRX nb No
HMI L_RXLEV_UL_P Sub-syste BSC Cell Type Yes
Definition Lower uplink level threshold for power control.
Mandatory rules L_RXLEV_UL_P < U_RXLEV_UL_P
Recommended --
rules
External --
comment
Logical L_RXLEV_UL_P_VAMOS B11 No B12 Yes
name TRX nb No
HMI L_RXLEV_UL_P_VAMOS Sub-syste BSC Cell Type Yes
Definition Lower downlink level threshold for VAMOS MS power control.
Mandatory rules L_RXLEV_UL_P_VAMOS < U_RXLEV_UL_P_VAMOS
Recommended --
rules
The UL RXLEV measured for each one of the two VAMOS sub-channels is the total received signal (sub-channel#1 + sub-channel#2) measured on the antenna
connector, so higher than the values measured in non-VAMOS mode
Logical L_RXQUAL_DL_H B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_H Sub-syste BSC Cell Type No
Definition Downlink quality threshold for handover for non AMR calls (neither AMR-NB nor AMR-WB).
Coding rules step size = 0.1, (1==0.1 70==7)
Mandatory rules --
Recommended L_RXQUAL_DL_H >= L_RXQUAL_DL_P

rules
External Higher value is the worst quality
comment
Internal comment --
Logical L_RXQUAL_DL_H_AMR B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_H_AMR Sub-syste BSC Cell Type No
Definition Downlink quality threshold for handovers (cause 16) on AMR-NB calls.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical L_RXQUAL_DL_H_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_H_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition Downlink quality threshold for handovers (cause 16) on AMR-WB GMSK calls.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical L_RXQUAL_DL_P B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_P Sub-syste BSC Cell Type No
Definition Lower downlink quality threshold for power control of any calls, except the AMR-NB or AMR-WB GMSK calls.
Coding rules step size = 0.1 (1==0.1 70==7)
Mandatory rules L_RXQUAL_DL_P > U_RXQUAL_DL_P
Recommended --
rules
External Highest value is the worst quality.
comment
Internal comment --
Logical L_RXQUAL_DL_P_AMR B11 No B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_P_AMR Sub-systeBSC Cell Type No
Definition Lower downlink quality threshold for power control of AMR-NB or AMR-WB GMSK calls where either Repeated DL FACCH (for LAPDm command and response frames)
or Repeated SACCH is not activated.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_DL_P_AMR < L_RXQUAL_DL_P_AMR
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting L_RXQUAL_DL_P_AMR = L_RXQUAL_DL_P
rules
comment - Highest value is the worst quality.
- Parameter change: no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
Logical L_RXQUAL_DL_P_AMR_RXACCH B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_P_AMR_RXACCH Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Lower downlink quality threshold for power control of AMR-NB or AMR-WB GMSK calls where Repeated DL FACCH (for LAPDm command and response frames) and
Repeated SACCH are activated.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_DL_P_AMR < L_RXQUAL_DL_P_AMR_RXACCH
Recommended To take benefit from the feature repeated ACCH, Alcatel-Lucent recommends :
rules L_RXQUAL_DL_P_AMR_RXACCH >= L_RXQUAL_DL_P_AMR
- Parameter change : no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
Logical L_RXQUAL_DL_P_AMR_RXACCH_VAMOS B11 No B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_P_AMR_RXACCH_VAMOS Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Lower downlink quality threshold for VAMOS power control of AMR-NB or AMR-WB VAMOS calls where Repeated DL FACCH (for LAPDm command and response
frames) and Repeated SACCH are activated.
Mandatory rules - U_RXQUAL_DL_P_AMR_VAMOS < L_RXQUAL_DL_P_AMR_RXACCH_VAMOS
Recommended - To take benefit from the feature repeated ACCH, Alcatel-Lucent recommends:
rules L_RXQUAL_DL_P_AMR_VAMOS <= L_RXQUAL_DL_P_AMR_RXACCH_VAMOS
- Highest value is the worst quality.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied on new VAMOS calls (after modification)
Internal comment --
Logical L_RXQUAL_DL_P_AMR_VAMOS B11 No B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_P_AMR_VAMOS Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Lower downlink quality threshold for VAMOS power control of AMR-NB or AMR-WB VAMOS calls where either Repeated DL FACCH (for LAPDm command and
response frames) or Repeated SACCH is not activated.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_DL_P_AMR_VAMOS < L_RXQUAL_DL_P_AMR_VAMOS
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting L_RXQUAL_DL_P_AMR_VAMOS = L_RXQUAL_DL_P_VAMOS.
rules
Internal comment --
Logical L_RXQUAL_DL_P_VAMOS B11 No B12 Yes
name TRX nb No
HMI L_RXQUAL_DL_P_VAMOS Sub-syste BSC Cell Type No
Definition Lower downlink quality threshold for VAMOS power control of any VAMOS calls, except the AMR-NB or AMR-WB ones.
Mandatory rules - U_RXQUAL_DL_P_VAMOS < L_RXQUAL_DL_P_VAMOS
Recommended --
rules
Internal comment --
Logical L_RXQUAL_UL_H B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_UL_H Sub-syste BSC Cell Type No
Definition Uplink quality threshold for handover for non AMR calls (nether AMR-NB nor AMR-WB).
Mandatory rules --
Recommended L_RXQUAL_UL_H >= L_RXQUAL_UL_P

rules
External Higher value is the worst quality
comment
Internal comment --
Logical L_RXQUAL_UL_H_AMR B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_UL_H_AMR Sub-syste BSC Cell Type No
Definition Uplink quality threshold for handovers (cause 15) on AMR-NB calls.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical L_RXQUAL_UL_H_AMR_WB_GMSK B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_UL_H_AMR_WB_GMSK Sub-syste BSC Cell Type No
Definition Uplink quality threshold for handovers (cause 15) on AMR-WB GMSK calls.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical L_RXQUAL_UL_P B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_UL_P Sub-syste BSC Cell Type No
Definition Lower uplink quality threshold for power control of any calls, except the AMR-NB or AMR-WB GMSK calls.
Mandatory rules L_RXQUAL_UL_P > U_RXQUAL_UL_P
Recommended --
rules
External Highest value is the worst quality.
comment
Internal comment --
Logical L_RXQUAL_UL_P_AMR B11 No B12 Yes
name TRX nb No
HMI L_RXQUAL_UL_P_AMR Sub-systeBSC Cell Type No
Definition Lower uplink quality threshold for power control of AMR-NB or AMR-WB GMSK calls where either Repeated DL FACCH (for LAPDm command and response frames) or
Repeated SACCH is not activated.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_UL_P_AMR < L_RXQUAL_UL_P_AMR
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting L_RXQUAL_UL_P_AMR = L_RXQUAL_UL_P
rules
Internal comment --
Logical L_RXQUAL_UL_P_AMR_RXACCH B11 Yes B12 Yes
name TRX nb No
HMI L_RXQUAL_UL_P_AMR_RXACCH Sub-syste
BSC Cell Type No
name Instancecell RMS No
Definition Lower uplink quality threshold for power control of AMR-NB or AMR-WB GMSK calls where Repeated DL FACCH (for LAPDm command and response frames) and
Repeated SACCH are activated.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_UL_P_AMR < L_RXQUAL_UL_P_AMR_RXACCH
Recommended To take benefit from the feature repeated ACCH, Alcatel recommends :
rules L_RXQUAL_UL_P_AMR_RXACCH >= L_RXQUAL_UL_P_AMR
Internal comment --
Logical L_TIME_ADVANCE B11 Yes B12 Yes
name TRX nb No
HMI LOWER_TIMING_ADVANCE Sub-syste BSC Cell Type Yes
Definition Low threshold to trigger handover cause too short distance in outer cell.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit bper
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where: CELL_RANGE = Outer cell. CT: Depends on Cell Type and BTS Type
Logical LAC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI LAC Sub-syste BSC Cell Type No
Definition Location Area Code.
Coding rules --
Equal to LAC (MFS)
A couple of mate extended cells (Extended inner + extended outer) shall have the same LAC.
Recommended --
rules
comment
Internal comment --
Logical LAC(n) (BSC) B11 Yes B12 Yes
name TRX nb No
HMI LAC Sub-syste BSC Cell Type No
Definition Location Area Code of adjacent cell.
Coding rules --
Mandatory rules LAC and CI can not be equal to 65535 at the same time.
Equal to LAC(n)(MFS).
A couple of mate extended cells (Extended inner + extended outer) shall have the same.
Recommended --
rules
comment
Internal comment --
Logical LAC_3G B11 Yes B12 Yes
name TRX nb No
HMI LAC_3G Sub-syste BSC Cell Type No
Definition This parameter indicates the Location Area Code of an external 3G (FDD or TDD) cell, as defined in 3GPP TS 24.008 (in the HANDOVER COMMAND message on A
interface).
Mandatory rules --
Recommended --
rules
comment
Internal comment - A coded default value is not needed since the operator cannot create a 3G cell without configuring its LAC (no dummy value needed).
Logical LB_DECR B11 Yes B12 Yes
name TRX nb No
HMI LB_DECR Sub-syste BSC Cell Type No
Definition Stepsize by which a leaky bucket overload counter in the BSC is decremented on T_LB_OV expiry.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Not used in case of OVERLOAD received from FU supporting the BCCH
Logical LB_INCR B11 Yes B12 Yes
name TRX nb No
HMI LB_INCR Sub-syste BSC Cell Type No
Definition Stepsize by which a leaky bucket overload counter in the BSC is incremented each time an OVERLOAD is received from the FU.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical LB_IP_SUBNET_MASK_BSC B11 Yes B12 Yes
name TRX nb No
HMI ADD_FUNC_IP_SUBNET_MASK_BSC Sub-syste BSC Cell Type No
Definition Mask of the subnet where is allocated the range of BSC addresses used for telecom protocols for the feature support of the Lb interface.
Mandatory rules --

rules
change.
displayed.
Logical LB_MIN_NB_ACTIVE_IPSP B11 Yes B12 Yes
name TRX nb No
HMI LB_MIN_NB_ACTIVE_IPSP Sub-syste BSC Cell Type No
Definition The minimum number of active IP server processes (IPSP) in the SMLC server, required to handle the signalling traffic with that SMLC.
Coding rules --
Mandatory rules When the SMLC_TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the LB_SCTP_ENDPOINT_LIST must be equal or greater than
LB_MIN_NB_ACTIVE_IPSP
Recommended --
rules
External - This parameter is significant when the SMLC_TRAFFIC_MODE of the SMLC is load sharing mode.
comment - Parameter change: before any modification, the operator must lock all the Lb Signalling Links of the modified SMLC.
Internal comment --
Logical LB_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI LB_PRIORITY Sub-syste BSC Cell Type No
Definition BSS internal priority used for the Lb signaling over IP flow (M3UA/SCTP signalling between BSC and SMLC, on Lb interface).
3: lower priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical LB_SCTP_ENDPOINT_IP_ADDRESS_1 B11 Yes B12 Yes
name TRX nb No
HMI LB_SCTP_ENDPOINT_IP_ADDRESS_1 Sub-syste BSC Cell Type No
Definition Primary IP address of a SCTP endpoint (used by M3UA protocol) on the SMLC side.
Mandatory rules - LB_SCTP_ENDPOINT_IP_ADDRESS_1 and LB_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one SMLC.
Recommended --
rules
External Parameter change: before any modification, the operator must lock the associated Lb Signalling Link
comment
Internal comment - 2 coded default values are implemented (15 blanks string on BSC->OMC, and empty string on OMC-> BSC); those dummy values indicate that the operator does not
Logical LB_SCTP_ENDPOINT_IP_ADDRESS_2 B11 Yes B12 Yes
name TRX nb No
HMI LB_SCTP_ENDPOINT_IP_ADDRESS_2 Sub-syste BSC Cell Type No
Definition Secondary IP address of a SCTP endpoint (used by M3UA protocol) on the SMLC side.
It is an optional address used in case of SCTP multihoming in SMLC side.
Recommended --
rules
comment
Logical LB_SCTP_ENDPOINT_LIST B11 Yes B12 Yes
name TRX nb No
HMI LB_SCTP_ENDPOINT_LIST Sub-syste BSC Cell Type No
Definition List of the SCTP endpoints (used by M3UA protocol) on the SMLC side.
Coding rules coded as an array of 4 entries.
Each entry is an SCTP endpoint, composed of LB_SCTP_ENDPOINT_IP_ADDRESS_1, LB_SCTP_ENDPOINT_PORT and LB_SCTP_ENDPOINT_IP_ADDRESS_2
Mandatory rules When the SMLC_TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the LB_SCTP_ENDPOINT_LIST must be equal or greater than
Recommended --
rules
External Parameter change: before any modification, the operator must lock all the Lb Signalling Links of the modified SMLC
comment
Internal comment - MAX_NB_LB_SCTP_ENDPOINT = 4
- A coded default value is not needed since the operator cannot create a SMLC without configuring its list of SCTP endpoints (no dummy value needed)
Logical LB_SCTP_ENDPOINT_PORT B11 Yes B12 Yes
name TRX nb No
HMI LB_SCTP_ENDPOINT_PORT Sub-syste BSC Cell Type No
Definition Port of a SCTP endpoint (used by M3UA protocol) on the SMLC side.
Coding rules --
Mandatory rules LB_SCTP_ENDPOINT_IP_ADDRESS_1 and LB_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one SMLC.
Recommended --
rules
comment
Internal comment - A coded default value is not needed since the operator cannot create a SMLC SCTP endpoint without configuring its port number (no dummy value needed).
Logical Linkfactor (0,n) B11 Yes B12 Yes
name TRX nb No
HMI Link_factor Sub-syste BSC Cell Type No
Definition Correction factor used in cell evaluation process to handicap or favour cell n.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical LOAD_EV_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI LOAD_EV_PERIOD Sub-syste BSC Cell Type No
Definition Number of load samples (received every TCH_INFO_PERIOD) for load averaging.
Category Site (CAE) OMC-R access Changeable Type Timer Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical LOAD_EV_PERIOD_GPRS B11 Yes B12 Yes
name TRX nb No
HMI LOAD_EV_PERIOD_GPRS Sub-syste BSC Cell Type No
Definition Number of load samples (calculated every TCH_INFO_PERIOD seconds) used to compute the maximum number of slave PDCHs that the BSC can allocate to the MFS.
Category Site (CAE) OMC-R access Changeable Type Timer Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Loadfactor_1 B11 Yes B12 Yes
name TRX nb No
HMI Load_Factor_1 Sub-syste BSC Cell Type No
Definition Correction factor used in cell evaluation process to take into account the TCH load in the candidate cell.
Coding rules --
Mandatory rules Loadfactor_1 >= Loadfactor_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
HMI Load_Factor_2 Sub-syste BSC Cell Type Yes
Coding rules --
Mandatory rules Loadfactor_1 >= Loadfactor_2 >= Loadfactor_3
Recommended --
rules
External --
comment
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
name TRX nb No
Coding rules --
Mandatory rules Loadfactor_5 <= Loadfactor_4
Recommended --
rules
External --
comment
Logical Loadlevel_1 B11 Yes B12 Yes
name TRX nb No
HMI Load_Level_1 Sub-syste BSC Cell Type No
Definition Boundary on cell load for determination of Loadfactor of the cell.
Coding rules --
Mandatory rules Loadlevel_1 < Loadlevel_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules Loadlevel_1 < Loadlevel_2 < Loadlevel_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules Loadlevel_2 < Loadlevel_3 < Loadlevel_4
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules Loadlevel_4 > Loadlevel_3
Recommended --
rules
External --
comment
Internal comment --
Logical LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 B11 Yes B12 Yes
name TRX nb No
HMI LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 Sub-syste BSC Cell Type No
Definition Local primary IP adress of a SCTP endpoint (used by M3UA protocol) on the BSC side.
Mandatory rules - LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 and LOCAL_ASIG_SCTP_ENDPOINT_PORT shall together be unique inside the BSC.
Recommended 255.255.255.255 and 0.0.0.0 are both forbidden

rules
External --
comment
Internal comment - In the BSC, there is one SCTP endpoint per MSC, connected to the BSC.
- The present address is computed by the BSC, according to START_ASIG_IP_ADDRESS_BSC.
displayed.
Logical LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_2 B11 No B12 Yes
name TRX nb No
HMI LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_2 Sub-syste BSC Cell Type No
Definition Local secondary IP address of a SCTP endpoint (used by M3UA protocol) on the BSC side.
It is an optional address used in case of SCTP multihoming, for M3UA load sharing and SCTP end to end redundancy, on BSC side.
Mandatory rules - LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_2 (when configured) and LOCAL_ASIG_SCTP_ENDPOINT_PORT shall together be unique inside the BSC.

rules
External --
comment
- The present address is computed by the BSC, according to START_ASIG_IP_ADDRESS_2_BSC.
displayed.
Logical LOCAL_ASIG_SCTP_ENDPOINT_PORT B11 Yes B12 Yes
name TRX nb No
HMI LOCAL_ASIG_SCTP_ENDPOINT_PORT Sub-syste BSC Cell Type No
Definition Local port of a SCTP endpoint (used by M3UA protocol) on the BSC side.
The default value corresponds to the first Asig port value set by the BSC.
Mandatory rules - LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 and LOCAL_ASIG_SCTP_ENDPOINT_PORT shall together be unique inside the BSC.
- LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_2 (when configured) and LOCAL_ASIG_SCTP_ENDPOINT_PORT shall together be unique inside the BSC.
- LOCAL_ASIG_SCTP_ENDPOINT_PORT shall be defined in the range 61953 61999.
Recommended - It is recommended to change these values only in case of IOT issue with the MSC. In this case it is recommended:
rules - to avoid the values already used by other BSS protocols using IP,
- and especially to not use the ports used by the IP_BSSAsig protocol (to avoid conflicts during the transition from Asig over TDM to Asig over IP).
External Parameter change: Before any modification of the Local_Asig_SCTP_Endpoint_Port, If the Aflex feature is enabled, Alcatel-Lucent recommends to firstly set the
comment concerned MSC into the "off loaded" state in order to redirect the new traffic towards other MSCs. Then, the operator must lock all the A Signalling Links (ASL) of the
modified MSC. Under some circumstances (e.g. that MSC is the only MSC still operational, ie in IT or FIT, state among all the MSCs connected to a BSC), the BSS-TEL is
to be previously locked too. This procedure leads the BSC to reject any new calls and wait for some minutes (Wait Traffic Clear) before shutting down the on going
calls. After modification of the Local_Asig_SCTP_Endpoint_Port, the locked objects must be
unlocked and be "on loaded" again to reopen the telecom service.
- BSC Firewall configuration : as it is not possible to modify dynamically the range of SCTP ports used by the BSC firewall, the BSC firewall shall be configured to
accept all possible SCTP ports (ie no SCTP port firewalling).
- The LOCAL_ASIG_SCTP_ENDPOINT_PORT values are computed by the BSC in the range 61953 61999 at the SCTP endpoint creation.
Logical LOCAL_IURG_SCTP_ENDPOINT_IP_ADDRESS_1 B11 Yes B12 Yes
name TRX nb No
HMI LOCAL_IURG_SCTP_ENDPOINT_IP_ADDRESS_1 Sub-syste BSC Cell Type No
Definition Local primary IP address of a SCTP endpoint (used by M3UA protocol) on the BSC side.
Mandatory rules - LOCAL_IURG_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_IURG_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside the BSC

rules
External --
comment
Internal comment - In the BSC, there is one SCTP endpoint (managed by one IPSP) per RNC, connected to the BSC.
- The present address is computed by the BSC, according to START_IURG_IP_ADDRESS_BSC.
displayed.
Logical LOCAL_IURG_SCTP_ENDPOINT_PORT B11 Yes B12 Yes
name TRX nb No
HMI LOCAL_IURG_SCTP_ENDPOINT_PORT Sub-syste BSC Cell Type No
Coding rules --
Mandatory rules LOCAL_IURG_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_IURG_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside the BSC
Recommended --
rules
External The LOCAL_IURG_SCTP_ENDPOINT_PORT values are computed by the BSC in the range 62000-62015.
comment
Internal comment - In the BSC, there is one SCTP endpoint (managed by one IPSP) per RNC, connected to the BSC.
- There is no default value since the port value is set by the BSC in this range at the SCTP endpoint creation (no dummy value needed).
Logical LOCAL_LB_SCTP_ENDPOINT_IP_ADDRESS_1 B11 Yes B12 Yes
name TRX nb No
HMI LOCAL_LB_SCTP_ENDPOINT_IP_ADDRESS_1 Sub-syste BSC Cell Type No
Definition Local primary IP address of a SCTP endpoint (used by M3UA protocol) on the BSC side.
Mandatory rules - LOCAL_LB_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_LB_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside the BSC

rules
External --
comment
Internal comment -In the BSC, there is one SCTP endpoint (managed by one IPSP) associated to the single SMLC, connected to the BSC.
- The present address is computed by the BSC, according to START_LB_IP_ADDRESS_BSC.
displayed.
Logical LOCAL_LB_SCTP_ENDPOINT_PORT B11 Yes B12 Yes
name TRX nb No
HMI LOCAL_LB_SCTP_ENDPOINT_PORT Sub-syste BSC Cell Type No
Coding rules --
Mandatory rules LOCAL_LB_SCTP_ENDPOINT_IP_ADDRESS_1 and LOCAL_LB_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside the BSC
Recommended --
rules
External - The LOCAL_LB_SCTP_ENDPOINT_PORT value is set by the BSC
comment
Internal comment - In the BSC, there is one SCTP endpoint (managed by one IPSP) associated to the single SMLC, connected to the BSC.
- There is no default value since the port value is set by the BSC at the SCTP endpoint creation (no dummy value needed).
Logical LOW_TRAFFIC_LOAD B11 Yes B12 Yes
name TRX nb Yes
HMI LOW_TRAFFIC_LOAD Sub-syste BSC Cell Type No
Definition Load threshold used to determine when traffic load is low for circuit switched calls.
Coding rules --
Mandatory rules LOW_TRAFFIC_LOAD <= HIGH_TRAFFIC_LOAD
Recommended --
rules
External If LOW_TRAFFIC_LOAD is set to 0 in a given cell n, then no Handover Cause 23 (i.e. Traffic Handovers) can be triggered towards that cell n.
comment
Logical LSA_ID_array (BSC) B11 Yes B12 Yes
name TRX nb No
HMI LSA_ID_I Sub-syste BSC Cell Type No
Definition List of authorised LSAs on a cell (up to 5).
Coding rules coded on 3 bytes max
Mandatory rules Equal to LSA_ID_array (MFS)
Recommended The LSA_ID may either be a Universal LSA identity (in case of odd number) or a PLMN significant LSA identity (in case of even number), as defined in GSM 03.03.
rules
External The default value depends on the configuration. The value given here is for implementation purposes only.
comment
Internal comment The limitation to 5 LSA_Ids is due to data storage limitation in the BSC.
The maximum 0xFFFFFF is reserved as invalid value for implementation purpose.
Logical LSA_OFFSET B11 Yes B12 Yes
name TRX nb No
HMI LSA_OFFSET Sub-syste BSC Cell Type No
Definition Offset to be used for LSA cell reselection between cells with the same LSA priorities.
Coding rules coded from 0 to 7, where 0 = 0 dB, 1 = 4 dB, 2 = 8 dB, 3 = 16 dB, 4 = 24 dB, 5 = 32 dB, 6 = 48 dB, 7 = 64 dB.
Mandatory rules --
Recommended --
rules
External The default value corresponds to an unused parameter for the MS.
comment
Internal comment --
Logical M_PEND_A (G2 BSC) B11 Yes B12 Yes
name TRX nb No
HMI M_PEND_A (G2 BSC) Sub-syste
BSC Cell Type No
name Instance
BSC RMS No
Definition Maximum number of I-frames received on RSL and GSL by a G2 BSC before sending an acknowledgement.
Mandatory rules The value of this parameter shall be lower than K_LAPD_RSL and K_GSL (BSC)
Recommended --
rules
External This parameter is used with the G2 BSC for both terrestrial and satellite links
comment
Internal comment --
Logical M_PEND_A (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI M_PEND_A (MX BSC) Sub-syste
BSC Cell Type No
name Instance
BSC RMS No
Definition Maximum number of I-frames received on RSL and GSL by a MX BSC before sending an acknowledgement.
Mandatory rules The value of this parameter shall be lower than K_LAPD_RSL and K_GSL (BSC)
Recommended --
rules
External This parameter is used only with Mx BSC for both terrestrial and satellite links.
comment
Internal comment --
Logical M1 B11 Yes B12 Yes
name TRX nb No
HMI Nbr. AC 11-15 barred in one step Sub-syste BSC Cell Type No
Definition Number of high priority access classes (11..15) are barred in one step.
Coding rules Value 0 inhibits the automatic barring of high priority access classes
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical M2 B11 Yes B12 Yes
name TRX nb No
HMI Nbr AC 11-15 unbarred in one step Sub-syste BSC Cell Type No
Definition Number of high priority access classes (11..15) are unbarred in one step.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical M2UA_SCTP_PORT_BSC B11 Yes B12 Yes
name TRX nb No
HMI M2UA_SCTP_PORT_BSC Sub-syste BSC Cell Type No
Definition STCP port used for IP_BSSAsig flow (M2UA/SCTP signalisation between BSC and TC and going to/coming from A interface), on BSC side.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Min = hCD70, Max = h'CD87
Logical M2UA_SCTP_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI M2UA_SCTP_PRIORITY Sub-syste BSC Cell Type No
Definition BSS internal priority used for the IP_BSSAsig flow (M2UA/SCTP signalling between BSC and TC and coming from/going to A interface).
3: lower priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to TC via TCSL
Logical MATE_CI (BSC) B11 Yes B12 Yes
name TRX nb No
HMI MATE_CI Sub-syste BSC Cell Type No
Definition Cell Identity of the Mate cell
Coding rules --
Mandatory rules MATE_CI (BSC) = MATE_CI (MFS)

If one mate cell is configured with GPRS (MAX_PDCH > 0) then the other mate cell shall also be configured with GPRS (MAX_PDCH > 0)
For an extended cell, MATE_LAC and MATE_CI can not be equal to 65535 at the same time
Recommended --
rules
comment (MATE_LAC + MATE_CI) is relevant for extended cells only
Internal comment --
Logical MATE_LAC B11 Yes B12 Yes
name TRX nb No
HMI MATE_LAC Sub-syste BSC Cell Type No
Definition Location Area Code of the Mate cell.
Mandatory rules For an extended cell, MATE_LAC and MATE_CI can not be equal to 65535 at the same time
A couple of mate extended cells (Extended inner + extended outer) shall have the same LAC
Recommended --
rules
comment (MATE_LAC + MATE_CI) is relevant for extended cells only
Internal comment --
Logical MAX_GPRS_CS B11 Yes B12 Yes
name TRX nb No
HMI MAX_GPRS_CS Sub-syste BSC Cell Type No
Definition Maximum coding scheme used for GPRS traffic in the cell.
Coding rules 1 : CS-2;
2 : CS-3;
3 : CS-4
Mandatory rules MAX_GPRS_CS >= TBF_DL_INIT_CS
MAX_GPRS_CS >= TBF_UL_INIT_CS
If Max_PDCH = 0 then MAX_GPRS_CS = CS-2.

The aim of this last rule is to prevent the BSC to trigger uselessly the algorithms of adjust ranking and transmission pool set up (lead time and outage) for CS3 and CS4,
in case Max_PDCH = 0 (i.e. GPRS is not allowed)
Recommended R_AVERAGE_GPRS shall not be set to a bitrate higher than the useful bitrate corresponding to MAX_GPRS_CS (e.g. if MAX_GPRS_CS = CS2 => R_AVERAGE_GPRS
rules shall not be higher than 12kbps)
R_MIN_GPRS shall not be set to a bitrate higher than the useful bitrate corresponding to Max_GPRS_CS. If the above recommended rule is not fulfilled, then some RT
PFCs can be accepted by the BSS whereas it will not be possible to handle their associated GBR. This may result in RT PFC downgrades to Best Effort.
External - This parameter can be set to CS-3 or CS-4 only if the related feature has been bought and controlled per quantity.
comment - Parameter change: In case of value increasing, there is no impact on the telecom service, on going TBF are not disrupted. But in case of value decreasing, the
established TBF will continue transferring with the previous limit, so it may happen that some TBF are disrupted due to the possible minimum number of GCH
decreasing
Internal comment This parameter is defined at cell level so that CS-3 and CS-4 can be used only in cells where the radio link quality is sufficiently good.
Logical MAX_IMSI_SAVED B11 Yes B12 Yes
name TRX nb No
HMI MAX_IMSI_SAVED Sub-syste BSC Cell Type No
Definition Maximum number of [IMSI, MSC identity] entries that can be saved per cell. These couples are temporarily stored by the BSC during a paging procedure without TMSI. The
identity of a MSC, connected to the BSC (Aflex feature), is either the MSC signalling point code, or the Global CN-id.
Coding rules --
Mandatory rules --
Recommended --
rules
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
- The duration for the BSC to save the [IMSI, MSC identity] is not specified by 3GPP. That duration is to be correlated with the paging repetition timer T3113, defined at
the core network side.
Internal comment - The maximum number of IMSIs that can be saved for each cell is:
MAX_IMSI_SAVED = T3113*(maximum paging rate of the cell)*(ratio of IMSI paging), where the value of T3113 and ratio of IMSI paging are network dependent.
255 corresponds to T3113 = 15sec, and ratio of IMSI paging = 10%, and a BSC of 6300 Erlang (170 max paging/cell)
2550 corresponds to T3113 = 15sec, and ratio of IMSI paging = 100% (VLR restart), and a BSC of 6300 Erlang (170 max paging/cell).
Logical MAX_LAPDM B11 Yes B12 Yes
name TRX nb No
HMI MAX_LAPDM Sub-syste BSC Cell Type No
Definition Maximum number of LAPDm frames on which a layer 3 can be segmented into and be sent on the main DCCH.
Rec ref. 3GPP TS 44.018 Domai DTM Min value 5 Coded Min 0
Coding rules Coded on 3 bits:
000 : 5
001 : 6
.
111 : 12
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_LAPS B11 Yes B12 Yes
name TRX nb No
HMI MAX_LAPS Sub-syste BSC Cell Type No
Definition Maximum number of logical data links on one physical link.
Coding rules Only value "1" is possible, that means point-to-point connection.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_NB_ASIG_SCTP_ENDPOINT B11 Yes B12 Yes
name TRX nb No
HMI MAX_NB_ASIG_SCTP_ENDPOINT Sub-syste BSC Cell Type No
Definition Maximum number of SCTP endpoints defined in the MSC server that handle the traffic with the BSS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_NB_IURG_SCTP_ENDPOINT B11 Yes B12 Yes
name TRX nb No
HMI MAX_NB_IURG_SCTP_ENDPOINT Sub-syste BSC Cell Type No
Definition Maximum number of SCTP endpoints defined in the RNC.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_NB_LB_SCTP_ENDPOINT B11 Yes B12 Yes
name TRX nb No
HMI MAX_NB_LB_SCTP_ENDPOINT Sub-syste BSC Cell Type No
Definition Maximum number of SCTP endpoints defined in the SMLC.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_PDCH (G2 BSC) B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH Sub-syste BSC Cell Type No
Definition Maximum number of slave and master PDCHs that can be allocated to the MFS in the cell.
Category Site (CAE) OMC-R access None (not in DLS) Type Number Unit None
Coding rules --
Mandatory rules Max_PDCH >= MAX_PDCH_HIGH_LOAD;

If MAX_PDCH > 0 then EN_GPRS = TRUE ;
If MAX_PDCH = 0 then EN_GPRS = FALSE;
If MAX_PDCH = 0 then EN_EGPRS = FALSE;
If EN_VGCS= enabled, then (MAX_VGCS_TS + MAX_PDCH) < Total number of TCHs of the cell

The aim of this rule is to prevent the BSC to trigger uselessly the algorithms of adjust ranking and transmission pool set up (lead time and outage) for CS3 and CS4, in
case Max_PDCH = 0 (i.e. GPRS is not allowed)
MAX_PDCH shall be set so that at least one slave PDCH can be allocated to the MFS to serve DL or UL TBFs. This means that MAX_PDCH > NB_TS_MPDCH if
EN_GPRS = TRUE.
When Max_PDCH > 0 and cell_type = extended inner or extended outer, then MAX_PDCH shall be an even number.
The following conditions are verified by the OMC-R in order to check the upper limit of MAX_PDCH:
i) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 1 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 1: CCCH combined
ii) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 2 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 0: CCCH not combined
iii) MAX_PDCH <= NB_TS_MPDCH + 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX
iv) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK=0) - 3 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 2
Recommended In a micro cell, the operator may be interested to force the MS to reselect a macro cell by a correct setting of the cell reselection parameters broadcast on PBCCH
rules (without using NC cell reselections, i.e. when EN_OUTGOING_GPRS_REDIR is set to 0 and NETWORK_CONTROL_ORDER is set to NC0 in the micro cell). In this
case,
the following configuration is recommended: NB_TS_MPDCH = 1, MAX_PDCH = 2, MAX_PDCH_HIGH_LOAD = 1, MIN_PDCH = 1.
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment
To support LCS in a cell, it is mandatory to have Max_PDCH > 0
m
Internal comment - The MPDCHs (primary and secondary) are also taken into account in this parameter.
- The cell is not created into the MFS, if Max_PDCH = 0 template
- The conditions to check the upper limit of MAX_PDCH are not fully optimized here. Indeed, ideally they should be performed taking into account the number of slave
PDCHs defined in the cell. However, implementing checks on a timeslot basis would degrade O&M performance. The proposed checks are therefore seen as a good
tradeoff between the O&M performance and optimized checks.
- The parameter value is stored in the memory (not in DLS file on disk), based on BSCGP received information
Logical MAX_PDCH (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH Sub-syste BSC Cell Type No
Definition Maximum number of slave and master PDCHs that can be allocated to the MFS in the cell
Coding rules --
Mandatory rules Shall be equal to MAX_PDCH (MFS)

Max_PDCH >= MAX_PDCH_HIGH_LOAD;

MAX_PDCH shall be set so that at least one slave PDCH can be allocated to the MFS to serve DL or UL TBFs. This means that MAX_PDCH > 0 if EN_GPRS = TRUE.
iii) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX
case,
the following configuration is recommended: MAX_PDCH = 2, MAX_PDCH_HIGH_LOAD = 1, MIN_PDCH = 1.
comment m
Internal comment - The MPDCHs (primary and secondary) are also taken into account in this parameter. template
- The cell is not created into the MFS, if Max_PDCH = 0
- The conditions to check the upper limit of MAX_PDCH are not fully optimized here. Indeed, ideally they should be performed taking into account the number of slave
- MX BSC received two values (one from the OMC, and one from MFS via BSCGP); last one is ignored.
Logical MAX_PDCH_HIGH_LOAD (G2 BSC) B11 Yes B12 Yes

name TRX nb No
HMI MAX_PDCH_HIGH_LOAD Sub-syste BSC Cell Type No
Definition Maximum number of slave and master PDCHs that can be allocated to the MFS when the CS traffic is high.
Coding rules --
Mandatory rules - MAX_PDCH >= MAX_PDCH_HIGH_LOAD

- MAX_PDCH_HIGH_LOAD >= MIN_PDCH
- If EN_DTM = 1 then MAX_PDCH_HIGH_LOAD > 1
Recommended --
rules
External 127 is a theoretical value: 16 TRX * 8 PDCH - BCCH.
comment
Logical MAX_PDCH_HIGH_LOAD (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH_HIGH_LOAD Sub-syste BSC Cell Type No
Coding rules --
Mandatory rules Shall be equal to MAX_PDCH_HIGH_LOAD (MFS)

- MAX_PDCH >= MAX_PDCH_HIGH_LOAD
Recommended --
rules
comment
Internal comment 1) MX BSC received two values (one from the OMC, and one from MFS via BSCGP); last one is ignored.
2) The MPDCHs (primary and secondary) are also taken into account in this parameter.
Logical MAX_POW_INC B11 Yes B12 Yes
name TRX nb No
HMI MAX_POW_INC Sub-syste BSC Cell Type No
Definition Maximum Power increase in one power command.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_POW_INC_VAMOS B11 No B12 Yes
name TRX nb No
HMI MAX_POW_INC_VAMOS Sub-syste BSC Cell Type No
Definition Maximum Power increase of a VAMOS sub-channel in one power command.
Mandatory rules --
Recommended --
rules
Internal comment --
Logical MAX_POW_RED B11 Yes B12 Yes
name TRX nb No
HMI MAX_POW_RED Sub-syste BSC Cell Type No
Definition Maximum Power reduction in one power command.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_POW_RED_VAMOS B11 No B12 Yes
name TRX nb No
HMI MAX_POW_RED_VAMOS Sub-syste BSC Cell Type No
Definition Maximum Power reduction of a VAMOS sub-channel in one power command.
Mandatory rules --
Recommended --
rules
Internal comment --
Logical Max_retrans (BSC) B11 Yes B12 Yes
name TRX nb No
HMI MAX_RETRANS Sub-syste BSC Cell Type No
Definition Maximum number of CHANNEL REQUEST retransmissions by the MS on the RACH.
Coding rules Possible values are:1, 2 ,4 and 7 respectively binary coded:00, 01, 10 and 11
Mandatory rules Max_retrans (BSC) = Max_retrans (MFS) for a given cell
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_TCH_HALF_RATE B11 No B12 Yes
name TRX nb No
HMI MAX_TCH_HALF_RATE Sub-syste BSC Cell Type No
Definition Maximum number of CS calls established with a half rate codec (HR or AMR-NB HR) in the BSS.
This value is expressed as a percentage over all the CS calls established in the BSS.
Coding rules 100% means that the mechanism is disabled
Mandatory rules --
Recommended - In order to use the whole BSS capacity, Alcatel-Lucent recommends setting this parameter to 100%
rules
comment - Significant when either HR_ENABLED or EN_AMR_HR is enabled (in at least one cell of the BSS)
- Parameter change: No impact on the telecom service, on going traffic is not disrupted (in case of value decreasing, the BSC will let the extra ongoing half rate calls
ending normally). Change applied on new calls (after modification).
Internal comment --
Logical MAX_TCH_PER_CCP_900E B11 Yes B12 Yes
name TRX nb No
HMI MAX_TCH_PER_CCP_900E Sub-syste BSC Cell Type No
Definition Maximum number of active TCHs per CCP board to reach 900 Erlang per CCP with a blocking probability of 0.1% and a margin of 3% (call mix with 3HO/call).
Spec ref. BSS telecom performance, traffic modele and capacity Coded Max 1000
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_TRC_NUMBER B11 Yes B12 Yes
name TRX nb No
HMI MAX_TRC_NUMBER Sub-syste BSC Cell Type No
Definition Maximum number of simultaneous trace jobs in the BSC.
Spec ref. GPRS Radio interface - RRM sublayer Coded Max 20
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_VGCS_TS B11 Yes B12 Yes
name TRX nb No
HMI MAX_VGCS_TS Sub-syste BSC Cell Type No
Definition Maximum number of radio timeslots that can be used by the VGCS calls in the cell.
Coding rules --
Mandatory rules MIN_VGCS_TS <= MAX_VGCS_TS

If EN_VGCS= enabled, then (MAX_VGCS_TS + MAX_PDCH) < Total number of TCHs of the cell.
If EN_VGCS= disabled, then MAX_VGCS_TS = 0
Recommended --
rules
comment To support VGCS in a cell, it is mandatory to have Max_VGCS_TS > 0
Internal comment --
Logical MCC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Country Code (MCC) Sub-syste BSC Cell Type No
Definition Mobile Country Code of the own PLMN.
Category Site (CAE) OMC-R access Set by Create Type Reference Unit None
Coding rules 3 digits BCD
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- MCC (BSC) = MCC (MFS).
- The cells belonging to the same BSC shall have the same (MCC,MNC) couple.
- The (MCC,MNC) couple of cells internal to the OMC-R shall be selected from the set of own PLMNs.
- The (MCC,MNC) couple of cells external to the OMC-R can be selected from the set of own or foreign PLMNs.
Recommended --
rules
External The value depends on the configuration. The default value indicated here is for implementation purposes.
comment
Internal comment The value sent by the OMC-R corresponds to the value of a OwnMCC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom catalogue document. The
OwnMCC[x] parameter defines one MCC of the own PLMN set.
Logical MCC(n) (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Country Code (MCC) Sub-syste BSC Cell Type No
Definition Mobile Country Code of the own or of a foreign PLMN.
Category Site (CAE) OMC-R access Virtual changeable Type Reference Unit None
- MCC(n) (BSC) = MCC(n) (MFS)
- If the target and serving cells belong to the same BSC, the OMC-R shall ensure that the cells have the same (MCC,MNC) couple.
- If the target and serving cells belong to the same OMC-R, both (MCC,MNC) couples shall be selected in the set of own PLMNs (but they do not have necessarily the
same own PLMN).
- If the target cell is external to the OMC-R, the MCC is computed by the OMC-R as a function of the PLMN id selected by the operator. In this case, the (MCC,MNC)
couple of the target cell can be selected in the set of own or foreign PLMNs.
Recommended --
rules
External --
comment
Internal comment The value sent by the OMC-R corresponds to the value of a OwnMCC[x] or ForeignMCC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom
catalogue document. The OwnMCC[x] parameter defines a MCC of the own PLMN set. The ForeignMCC[x] parameter defines a MCC of the foreign PLMN set.
Logical MCC_3G B11 Yes B12 Yes
name TRX nb No
HMI Mobile Country Code (MCC) for 3G cell Sub-syste BSC Cell Type No
Definition Mobile Country Code of a neighbour external 3G cell (FDD or TDD) of the own or of a foreign PLMN.
Mandatory rules - The MCC_3G is computed by the OMC-R as a function of the PLMN id selected by the operator.
- (MCC_3G, MNC_3G, Local-3G-Cell-Identity) shall together uniquely identify a 3G cell inside the OMC.
- (MCC_3G, MNC_3G, RNC_ID_3G and CI_3G) shall together uniquely identify a 3G cell.
Recommended --
rules
External --
comment
Internal comment - The value sent by the OMC-R corresponds to the value of a OwnMCC[x] or ForeignMCC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom
catalogue document. The OwnMCC[x] parameter defines a MCC of the own PLMN set. The ForeignMCC[x] parameter defines a MCC of the foreign PLMN set.
- A coded default value is not needed since the operator cannot create a 3G cell without configuring its MCC (no dummy value needed).
Logical MCC_LTE B11 Yes B12 Yes
name TRX nb No
HMI Mobile Country Code (MCC) for LTE cell Sub-syste BSC Cell Type No
Definition Mobile Country Code of a neighbour external LTE (FDD or TDD) cell of the own or of a foreign PLMN.
Mandatory rules - The MCC_LTE is computed by the OMC-R as a function of the PLMN id selected by the operator in the set of own or foreign PLMNs
- (MCC_LTE, MNC_LTE, CI_LTE) shall together uniquely identify a LTE cell inside the OMC
Recommended --
rules
External - Parameter available on BSC Evolution only
comment
Internal comment - The value sent by the OMC-R corresponds to the value of a OwnMCC[x] or ForeignMCC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom
catalogue document. The OwnMCC[x] parameter defines a MCC of the own PLMN set.
The ForeignMCC[x] parameter defines a MCC of the foreign PLMN set.
- A coded default value is not needed since the operator cannot create a LTE cell without configuring its MCC (no dummy value needed).
Logical MEAS_RES_DISCARDED_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_RES_DISCARDED_i [1] Sub-syste BSC Cell Type No
Definition Percentage of MEASUREMENT RESULT messages discarded by the TCU at step I.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MEAS_STAT_BFI_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_STAT_BFI_1 Sub-syste BSC Cell Type No
Definition Threshold on successive Bad Frame Indication to define bands used for Radio Measurements Statistics.
Mandatory rules MEAS_STAT_BFI2 > MEAS_STAT_BFI1
Recommended --
rules
comment
Internal comment --
name TRX nb No
HMI MEAS_STAT_BFI_2 Sub-systeBSC Cell Type No
Mandatory rules MEAS_STAT_BFI3 > MEAS_STAT_BFI2 > MEAS_STAT_BFI1
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_BFI9 > MEAS_STAT_BFI8
Recommended --
rules
comment
Internal comment --
Logical MEAS_STAT_C_I_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_STAT_C_I_1 Sub-syste BSC Cell Type No
Definition Threshold on radio C/I (Carrier/Interference) measurements to define bands used for Radio Measurements Statistics.
Coding rules coded from 1 to +125, step size = 1dB ( 1= -62 db, , 125 = +62 dB)
Mandatory rules MEAS_STAT_CI1 < MEAS_STAT_CI2
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_CI1 < MEAS_STAT_CI2 < MEAS_STAT_CI3
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_CI8 < MEAS_STAT_CI9
Recommended --
rules
comment
Internal comment --
Logical MEAS_STAT_LEV_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_STAT_LEV_1 Sub-syste BSC Cell Type No
Definition Threshold on radio level to define bands used for Radio Measurements Statistics.
Coding rules coded 1 to 62, 1 = -109 dBm, . . . 62 = -48 dBm, step = 1dBm
Mandatory rules MEAS_STAT_LEV_1 > MEAS_STAT_LEV_2
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_LEV_1 > MEAS_STAT_LEV_2 > MEAS_STAT_LEV_3
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_LEV_8 > MEAS_STAT_LEV_9
Recommended --
rules
comment
Internal comment --
Logical MEAS_STAT_PATH_BAL_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_STAT_PATH_BAL_1 Sub-syste BSC Cell Type No
Definition Threshold on path balance to define bands used for Radio Measurements Statistics.
Coding rules coded from 1 to +219, step size = 1dB (1 = -109 dB, 219 = +109 dB)
Mandatory rules MEAS_STAT_PATH_BAL1 < MEAS_STAT_PATH_BAL2
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_PATH_BAL3 > MEAS_STAT_PATH_BAL2 > MEAS_STAT_PATH_BAL1
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_PATH_BAL9 > MEAS_STAT_PATH_BAL8
Recommended --
rules
comment
Internal comment --
Logical MEAS_STAT_S_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_STAT_S_1 Sub-syste BSC Cell Type No
Definition Threshold on radio link counter to define bands used for Radio Measurements Statistics.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit Samfr
Mandatory rules MEAS_STAT_S1 < MEAS_STAT_S2
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_S3 > MEAS_STAT_S2 > MEAS_STAT_S1
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Recommended --
rules
comment
Internal comment --
name TRX nb No
Mandatory rules MEAS_STAT_S9 > MEAS_STAT_S8
Recommended --
rules
comment
Internal comment --
Logical MEAS_STAT_TA_i [1] B11 Yes B12 Yes
name TRX nb No
HMI MEAS_STAT_TA_1 Sub-syste BSC Cell Type No
name Instance BSS RMS Yes
Definition Upper limit of the first TA band, lower limit of the second TA band (for the RMS TA measurements)
Category Site (CAE) OMC-R access Changeable Type Number Unit bper
Coding rules --
Mandatory rules 0 < MEAS_STAT_TA_1 < MEAS_STAT_TA_2
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd TA band, lower limit of the 3rd TA band (for the RMS TA measurements)
Coding rules --
Mandatory rules MEAS_STAT_TA_1 < MEAS_STAT_TA_2 < MEAS_STAT_TA_3
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd TA band, lower limit of the 4th TA band (for the RMS TA measurements)
Coding rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th TA band, lower limit of the 5th TA band (for the RMS TA measurements)
Coding rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules MEAS_STAT_TA_8 < MEAS_STAT_TA_9 < 63
Recommended --
rules
comment
Internal comment --
Logical MEASUREMENT_BANDWIDTH B11 Yes B12 Yes
name TRX nb No
HMI MEASUREMENT_BANDWIDTH Sub-syste BSC Cell Type No
Definition Number of resources blocks (NRB) over which an MS/UE LTE-capable could measure.
Coding rules 0 (coded) = 6
1 (coded) = 15
2 (coded) = 25
3 (coded) = 50
4 (coded) = 75
5 (coded) = 100
Mandatory rules All LTE cells managed by the OMC having the same ARFCN_LTE shall be given the same MEASUREMENT_BANDWIDTH value (to be checked on a per RAT basis).
Recommended --
rules
Internal comment --
Logical MIN_CONNECT_TIME B11 Yes B12 Yes
name TRX nb No
HMI MIN_CONNECT_TIME Sub-syste BSC Cell Type Yes
Definition Maximum connection time after a handover in an overlaid cell to declare the MS fast when leaving the cell with a handover.
Category Site (CAE) OMC-R access Changeable Type Timer Unit sec
Coding rules step size=1sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Lower layer. CT: Depends on Cell Type and BTS Type
Logical MIN_NB_ACTIVE_IPSP B11 Yes B12 Yes
name TRX nb No
HMI MIN_NB_ACTIVE_IPSP Sub-syste BSC Cell Type No
Definition The minimum number of active IP server processes (IPSP) in the MSC server required to handle the traffic with that MSC.
Coding rules --
Mandatory rules When the MSC TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the ASIG_SCTP_ENDPOINT_LIST must be equal or greater than
MIN_NB_ACTIVE_IPSP
Recommended --
rules
External - This parameter is significant when the TRAFFIC_MODE of the MSC is load sharing mode.
comment - Parameter change: before any modification of the MIN_NB_ACTIVE_IPSP, If the Aflex feature is
enabled, Alcatel-Lucent recommends to firstly set the concerned MSC into the "off loaded" state in order to redirect the new traffic towards other MSCs. Then, the
operator must lock all the A Signalling Links (ASL) of the modified MSC. Under some circumstances (e.g. that MSC is the only MSC still operational, ie in IT or FIT, state
among all the MSCs connected to a BSC), the BSS-TEL is to be previously locked too. This procedure leads the BSC to reject any new calls and wait for some minutes
(Wait Traffic Clear) before shutting down the on going calls. After modification of the MIN_NB_ACTIVE_IPSP, the locked objects must be unlocked and be "on loaded"
again to reopen the telecom service.
Internal comment --
Logical MIN_PDCH (G2 BSC) B11 Yes B12 Yes
name TRX nb No
HMI MIN_PDCH Sub-syste BSC Cell Type No
Definition Minimum number of master and slave PDCHs that are always allocated to the MFS.
Coding rules --
Mandatory rules -MAX_PDCH_HIGH_LOAD >= MIN_PDCH;

-MIN_PDCH > NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = enabled;
-MIN_PDCH >= NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = disabled.
-When MIN_PDCH > 0 and cell_type = extended inner or extended outer, then MIN_PDCH shall be an even number
Recommended It is recommended to set this parameter to a value smaller than the maximum number of PDCHs that may be allocated in the cell, in order to avoid congestion on the
rules MFS-BSC interface.
comment
Logical MIN_PDCH (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI MIN_PDCH Sub-syste BSC Cell Type No
Coding rules --
Mandatory rules - Shall be equal to MIN_PDCH (MFS)

-MAX_PDCH_HIGH_LOAD >= MIN_PDCH;
-MIN_PDCH > 0 if EN_FAST_INITIAL_GPRS_ACCESS = enabled;
-MIN_PDCH >= 0 if EN_FAST_INITIAL_GPRS_ACCESS = disabled.
comment
- MX BSC received two values (one from the OMC, and one from MFS via BSCGP); last one is ignored.
Logical MIN_TIME_BTW_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI MIN_TIME_BTW_VAMOS_PAIRING Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition This parameter represents the minimum delay between the VAMOS unpairing and subsequent VAMOS pairing for a given MS. It I used to prevent a MS from an immediate
re-pairing; and from ping-pong between non-VAMOS and VAMOS allocation.
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment --
Logical MIN_VGCS_TS B11 Yes B12 Yes
name TRX nb No
HMI MIN_VGCS_TS Sub-syste BSC Cell Type No
Definition Minimum number of radio timeslots that are reserved for the VGCS calls in the cell in normal situation (point-to-point CS call can NOT use these timeslots).
Coding rules --
Mandatory rules MIN_VGCS_TS <= MAX_VGCS_TS
Recommended - The following rules about the upper limit are recommended :
rules i) MIN_VGCS_TS <= 8*(nb of TRXs with TRX_PREF_MARK <> 0) - 2 if TRX_PREF_MARK <> 0 on BCCH TRX and CCCH_CONF = 1: CCCH combined
ii) MIN_VGCS_TS <= 8*(nb of TRXs with TRX_PREF_MARK <> 0) - 3 if TRX_PREF_MARK <> 0 on BCCH TRX and CCCH_CONF = 0: CCCH not combined
iii) MIN_VGCS_TS <= 8*(nb of TRXs with TRX_PREF_MARK <> 0) - 1 if TRX_PREF_MARK = 0 on BCCH TRX.
- If EN_VGCS = enabled , then Alcatel recommends to set EN_TCH_PREEMPT to enabled, otherwise to set the value of MIN_VGCS_TS to a value greater or equal to 2

comment
Internal comment --
Logical MNC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Network Code (MNC) Sub-syste BSC Cell Type No
Definition Mobile Network Code of the own PLMN.
- MNC (BSC) = MNC (MFS).
Recommended --
rules
External The value depends on configuration. The default value indicated here is for implementation purposes.
comment The operator is allowed to enter 2 or 3 digits MNC in the CDE table.
MNC such as yz or Fyz correspond to a 2 digits MNC (y, z = 0..9). (F binary coded 1111)
MNC such as xyz correspond to a 3 digits MNC (x = 0..9).
Internal comment The value sent by the OMC-R corresponds to the value of a OwnMNC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom catalogue document. The
OwnMNC[x] parameter defines a MNC of the own PLMN set.
Logical MNC(n) (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Network Code (MNC) Sub-syste BSC Cell Type No
Definition Mobile Network Code of the own PLMN or of a foreign PLMN.
- MNC(n) (BSC) = MNC(n) (MFS)
- If the target and serving cells belong to the same OMC-R, both (MCC,MNC) couples shall be selected in the set of own PLMNs (they do not have necessarily the same
own PLMN).
Recommended --
rules
External --
comment
Internal comment The value sent by the OMC-R corresponds to the value of a OwnMNC[x] or ForeignMNC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom
catalogue document. The OwnMNC[x] parameter defines a MNC of the own PLMN set. The ForeignMNC[x] parameter defines a MNC of the foreign PLMN set.
Logical MNC_3G B11 Yes B12 Yes
name TRX nb No
HMI Mobile Network Code (MNC) for 3G cell Sub-syste BSC Cell Type No
Definition Mobile Network Code of a neighbour external 3G cell (FDD or TDD) of the own PLMN or of a foreign PLMN.
Mandatory rules - The MNC_3G is computed by the OMC-R as a function of the PLMN id selected by the operator.
- (MCC_3G, MNC_3G, Local-3G-Cell-Identity) shall together uniquely identify a 3G cell inside the OMC.
- (MCC_3G, MNC_3G, RNC_ID_3G and CI_3G) shall together uniquely identify a 3G cell.
Recommended --
rules
External The operator is allowed to enter 2 or 3 digits MNC in the CDE table.
comment MNC such as yz or Fyz correspond to a 2 digits MNC (y, z = 0..9). (F binary coded 1111)
Internal comment - The value sent by the OMC-R corresponds to the value of a OwnMNC[x] or ForeignMNC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom
catalogue document. The OwnMNC[x] parameter defines a MNC of the own PLMN set. The ForeignMNC[x] parameter defines a MNC of the foreign PLMN set.
- A coded default value is not needed since the operator cannot create a 3G cell without configuring its MNC (no dummy value needed).
Logical MNC_LTE B11 Yes B12 Yes
name TRX nb No
HMI Mobile Network Code (MNC) for LTE cell Sub-syste BSC Cell Type No
Definition Mobile Network Code of a neighbour external LTE (FDD or TDD) cell of the own PLMN or of a foreign PLMN.
Mandatory rules - The MNC_LTE is computed by the OMC-R as a function of the PLMN id selected by the operator in the set of own or foreign PLMNs.
- (MCC_LTE, MNC_LTE, CI_LTE) shall together uniquely identify a LTE cell inside the OMC
Recommended --
rules
External - Parameter available on BSC Evolution only
comment - The operator is allowed to enter 2 or 3 digits MNC in the CDE table.
Internal comment - The value sent by the OMC-R corresponds to the value of a OwnMNC[x] or ForeignMNC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom
catalogue document. The OwnMNC[x] parameter defines a MNC of the own PLMN set.
The ForeignMNC[x] parameter defines a MNC of the foreign PLMN set.
- A coded default value is not needed since the operator cannot create a LTE cell without configuring its MNC (no dummy value needed).
Logical MS_P_CON_ACK B11 Yes B12 Yes
name TRX nb No
HMI MS_P_CON_ACK Sub-syste BSC Cell Type Yes
Definition Supervision of the MS Power Control procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Logical MS_P_CON_INT B11 Yes B12 Yes
name TRX nb No
HMI MS_P_CON_INT Sub-syste BSC Cell Type Yes
Definition Minimum delay between two consecutive MS power commands.
Mandatory rules --
Recommended --
rules
External --
comment
Logical MS_TXPWR_MAX B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX Sub-syste BSC Cell Type No
Definition MS maximum allowed transmission power.
Coding rules P-GSM/G1 coding: step size = 2 dBm; 0: 43 dBm,...., 19: 5 dBm.
GSM 850 coding: step size = 2 dBm; 0: 39 dBm, 1: 39 dBm, 2: 39 dBm, 3: 37 dBm, 4: 35 dBm,..., 19: 5 dBm.
DCS 1800 coding:step size = 2 dBm; 0: 30 dBm,..., 15: 0 dBm.
DCS 1900 coding: range 0 to 15, 30, 31; 0: 30 dBm, 1: 28 dBm, ..., 15: 0 dBm, 30: 33 dBm, 31: 32 dBm.
Mandatory rules MS_TXPWR_MAX >= MS_TXPWR_MIN
Recommended --
rules
External According to the 3GPP TS 05.05, if the BCCH frequency band is P-GSM/G1, depending on the version of MS (Phase 1 MS or Phase 2/onwards MS), the coded value
comment 0, 1 and 2 are interpreted differently:
- Coded value 0: (interpreted as 43 dBm by the Phase 1 MS; interpreted as 39 dBm by the Phase 2/onwards MS);
- Coded value 2: (interpreted as 39 dBm by both the Phase 1 MS and the Phase 2/onwards MS).
Internal comment 1) Exceptionally the CAE templates in the BTP will always contain the coded_default value (coded as 0) instead of the real default value expressed in dBm (i.e., 43,
39, 30, 30, depending on the BCCH frequency band). By convention, the minimum, maximum, and default values in the main window of the parameter are given
for the P-GSM/G1 frequency band.
2) In the GSM850 band, the value of 39 dBm is only displayed once at the OMC-R screen and corresponds to the value coded as 0. However, the value coded as 1
or 2 may be used if the data are retrieved from the ACIE interface.
Logical MS_TXPWR_MAX(n) B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX Sub-syste BSC Cell Type No
Definition MS maximum allowed transmission power.
Coding rules P-GSM/G1 coding: step size = 2 dBm; 0: 43 dBm, ..., 19: 5 dBm.
DCS 1800 coding:step size = 2 dBm; 0: 30 dBm, ..., 15: 0 dBm.
Mandatory rules MS_TXPWR_MAX >= MS_TXPWR_MIN
Recommended --
rules
-Coded value 2: (interpreted as 39 dBm by both the Phase 1 MS and the Phase 2/onwards MS).
Logical MS_TXPWR_MAX_CCH (BSC) B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX_CCH Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Maximum transmission power an MS is allowed to use when accessing the cell until otherwise commanded.
Mandatory rules --
Recommended --
rules
Logical MS_TXPWR_MAX_CCH(n)(BSC) B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX_CCH Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Maximum transmission power an MS is allowed to use when accessing the cell until otherwise commanded, broadcast on PBCCH for CS service establishment.
DCS 1900 coding: range 0 to 15, 30, 31; 30: 33 dBm, 31: 32 dBm, 0: 30 dBm, 1: 28 dBm, ..., 15: 0 dBm.
Mandatory rules --
Recommended --
rules
Logical MS_TXPWR_MAX_INNER B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX_INNER Sub-syste BSC Cell Type Yes
Definition MS maximum allowed transmission power in the inner zone of a concentric or multiband cell.
Mandatory rules MS_TXPWR_MAX_INNER >= MS_TXPWR_MIN
Recommended --
rules
Meaninful only in cells where: CELL_PARTITION_TYPE = concentric.

Internal comment 1) The coding rules of MS_TXPWR_MAX_INNER depend on the inner zone frequency band. Therefore, in a multiband concentric cell, the coding rules defined for
MS_TXPWR_MAX_INNER are different from the coding rules defined for MS_TXPWR_MAX and MS_TXPWR_MIN, which both apply to the outer zone frequency
band.
2) Exceptionally the CAE templates in the BTP will always contain the coded_default value (coded as 0) instead of the real default value expressed in dBm (i.e., 43,
Logical MS_TXPWR_MIN B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MIN Sub-syste BSC Cell Type No
Definition MS minimum allowed transmission power.
Coding rules P-GSM/G1 coding: step size = 2 dBm; 0: 43 dBm, ...,13: 17 dBm,, 19: 5 dBm.
GSM 850 coding: step size = 2 dBm; 0: 39 dBm, 1: 39 dBm, 2: 39 dBm, 3: 37 dBm, 4: 35 dBm,..., 13: 17 dBm,, 19: 5 dBm.
DCS 1800 coding:step size = 2 dBm; 0: 30 dBm, ..., 13: 4 dBm,, 15: 0 dBm.
DCS 1900 coding: range 0 to 15, 30, 31; 0: 30 dBm, 1: 28 dBm, ..., 13: 4 dBm,, 15: 0 dBm, 30: 33 dBm, 31: 32 dBm.
Mandatory rules MS_TXPWR_MIN <= MS_TXPWR_MAX and MS_TXPWR_MAX_INNER >= MS_TXPWR_MIN
Recommended --
rules
External The default value depends on the BCCH frequency band:
comment Default value for P-GSM/G1: 17 dBm
Default value for GSM850: 17 dBm
Default value for DCS1800: 4 dBm
Internal comment 1) Exceptionally the CAE templates in the BTP will always contain the coded_default value (coded as 13) instead of the real default value expressed in dBm (i.e.,
17, 17, 4, 4, depending on the BCCH frequency band). By convention, the minimum, maximum, and default values in the main window of the parameter are
given for the P-GSM/G1 frequency band.
Logical MSC_CN_ID B11 Yes B12 Yes
name TRX nb No
HMI MSC_CN_ID Sub-syste BSC Cell Type No
Definition This parameter indicates, within a given PLMN, the Core Network Identifier.
It is part of the Global Core Network Identifier, defined in 3GPP TS 23.003 as (PLMN-id + CN-id), which uniquely identifies a MSC for the Aflex feature.
Rec ref. 3GPP TS 23.003 Domai IP Min value 0 Coded Min 0
Coding rules coded on 2 bytes
The coded default value is for implementation purposes only; this dummy value indicates that the operator does not provide any MSC identifier yet.
Mandatory rules - All the MSCs, connected to one BSC, must have different MSC_CN_ID.
Recommended - The operator must control that, in a PLMN, 2 MSCs must have 2 different MSC_CN_ID.
rules
- The operator must control that the BSC and all the MSCs connected to that BSC via Aflex feature must belong to the same PLMN.
- Parameter change: No impact on the telecom service, on going calls are not disrupted (still established with the same MSC). Change applied immediately on the new
calls established after modification.
Internal comment --
Logical MSC_MCC B11 Yes B12 Yes
name TRX nb No
HMI MSC_MCC Sub-syste BSC Cell Type No
Definition Mobile Country Code of the MSC, connected to the BSC. It is part of the Global Core Network Identifier, defined in 3GPP TS 23.003 as (PLMN-id + CN-id), which uniquely
identifies a MSC for the Aflex feature.
The coded default value is for implementation purposes only; this dummy value indicates that the operator does not provide any MCC yet.
Mandatory rules The OMC-R initializes the parameter with the MCC field of the BSC-OwnPLMN. It is not changeable on the HMI.
Recommended --
rules
Internal comment - According to the multi-PLMN feature, the OMC manages several ownPLMNs, but each BSC remains mono PLMN. The present PLMN is ready in the MIB to be
changeable. If necessary in the future it could become easily changeable at the OMC HMI level (one among the own+foreign PLMNs or one free operator choice).
Logical MSC_MNC B11 Yes B12 Yes
name TRX nb No
HMI MSC_MNC Sub-syste BSC Cell Type No
Definition Mobile Network Code of the MSC, connected to the BSC. It is part of the Global Core Network Identifier, defined in 3GPP TS 23.003 as (PLMN-id + CN-id), which uniquely
identifies a MSC for the Aflex feature.
The coded default value is for implementation purposes only; this dummy value indicates that the operator does not provide any MNC yet.
Mandatory rules The OMC-R initializes the parameter with the MNC field of the BSC-OwnPLMN. It is not changeable on the HMI.
Recommended --
rules
Internal comment - According to the multi-PLMN feature, the OMC manages several ownPLMNs, but each BSC remains mono PLMN. The present PLMN is ready in the MIB to be
changeable. If necessary in the future it could become easily changeable at the OMC HMI level (one among the own+foreign PLMNs or one free operator choice).
Logical MSC_OFFLOAD_STATE B11 Yes B12 Yes
name TRX nb No
HMI --- Sub-syste BSC Cell Type No
Definition State assigned to a given MSC, connected to the BSC (Aflex feature), for the load redistribution function. That function removes the off loaded MSC from the list of
candidate MSCs on BSS side.
Coding rules 0: off loaded
1: on loaded
Mandatory rules --
Recommended --
rules
External - Significant only if EN_A_FLEX is enabled.
- If a MSC server is in high load situation, the operator can avoid the MSC to enter the overload situation through the update of that parameter to off loaded for the
concerned MSC.
Parameter change: on going traffic is not disrupted. Change applied immediately after modification. The complete redistribution of the MS requires the same change
done on Core Network side too.
Internal comment - HMI name = the name of the button value, ie ONLOADED or OFFLOADED
Logical MSC_SPC B11 Yes B12 Yes
name TRX nb No
HMI MSC_SPC Sub-syste BSC Cell Type No
Definition Signalling Point Code of a given MSC, connected to the BSC.
Rec ref. ITU-T Q.704 Domai IP Min value 0 Coded Min 0
Mandatory rules All the MSCs connected to one BSC must have different MSC_SPC.
Recommended --
rules
External - Significant only if EN_ASIG_OVER_IP is set to TRUE
comment - "A signalling over IP" function is available on BSC Evolution only.
- Parameter change: Before any modification of the MSC_SPC, If the Aflex feature is enabled, Alcatel-Lucent recommends to firstly set the concerned MSC into the
"off loaded" state in order to redirect the new traffic towards other MSCs. Then, the operator must lock all the A Signalling Links (ASL) of the modified MSC. Under
some circumstances (e.g. that MSC is the only MSC still operational, ie in IT or FIT, state among all the MSCs connected to a BSC), the BSS-TEL is to be previously
locked too. This procedure leads the BSC to reject any new calls and wait for some minutes (Wait Traffic Clear) before shutting down the on going calls. After
modification of the MSC_SPC, the locked objects must be unlocked and be "on loaded" again to reopen the telecom service.
Internal comment A coded default value is not needed since the operator cannot create a MSC without configuring its signaling point code (no dummy value needed).
Logical MSC_WEIGHT B11 Yes B12 Yes
name TRX nb No
HMI MSC_WEIGHT Sub-syste BSC Cell Type No
Definition Weight assigned to a MSC, connected to the BSC (Aflex feature), for the load balancing function. A high value is to be associated to a high capacity MSC.
Coding rules --
Mandatory rules --
Recommended It is recommended to set a weight value consistent with the number of A-trunks connected to that MSC.
rules
Internal comment --
Logical MSCR (G2 BSC) B11 No B12 Yes
name TRX nb No
HMI MSCR Sub-syste BSC Cell Type No
Definition Year corresponding to the version of ETSI/3GPP recommendations used to implement MSC software.
Coding rules 0 = MSC is release '98 or older; 1 = MSC is release '99 onwards
Mandatory rules MSCR (BSC) = MSCR (MFS)
Recommended --
rules
comment
Internal comment The BSS does not use this field but shall provide it to the MS (MSC Release is broadcast in SI/PSI message) for upper layer protocol between the MS and the
MSC.Towards a MSC Release 99 (and newer), the MS is allowed to send several unacknowledge layer3 MM or CC messages to the MSC, transparently to the BSS
(defined in GSM TS24.007, TS24.008 and 04.18).
Logical MSCR (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI MSCR Sub-syste BSC Cell Type No
Recommended --
rules
comment
Logical MTP_Sequence_Number_Format B11 Yes B12 Yes
name TRX nb No
HMI MTP_Sequence_Number_Format Sub-syste BSC Cell Type No
Definition Defines the format to be used for the sequence number of MTP2.
Coding rules 0: Normal
1: Extended
Mandatory rules --
Recommended --
rules
External Value "Extended" is refused by the BSC if EN_HSL=0
comment
Internal comment MTP_SN_Format is managed by the Mx-BSC only.
In IP mode, sent to the TC via TCSL
Logical MTP3_WB_INTERWORKING B11 Yes B12 Yes
name TRX nb No
HMI WHITE_BOOK_INTERWORKING Sub-syste
BSC Cell Type No
Definition This flag indicates if the BSC sends a Q.704 TRA message upon first reception of SLTA from the MSC.
Coding rules 0 : TRA not sent upon first SLTA reception, 1 : TRA sent upon first SLTA reception
Mandatory rules --
Recommended --
rules
External - This flag is set to 1 for interworking with a "White Book" MSC. It is set to 0 for interworking with a "Blue Book" MSC.
comment - Parameter change: after modification, a BSC restart procedure is needed. On going calls are not disrupted (as long as no new signalling exchange is needed) but
the new traffic is not accepted during that procedure.
Internal comment --
Logical MULTIBAND_FORCED_DR_TRAFFIC_CONDITION B11 No B12 Yes
name TRX nb Yes
HMI MULTIBAND_FORCED_DR_TRAFFIC_CONDITION Sub-syste BSC Cell Type No
Definition This parameter determines the traffic load threshold in the serving cell to trigger a preferred band forced directed retry handover (cause 36).
Coding rules Default value depends on the number of TRX in the cell.
The value indicated here is for implementation purposes.
Mandatory rules --
Recommended --
rules
comment - Significant when EN_PREFERRED_BAND_FORCED_DR is enabled
Internal comment - TRXnb: Depends on TRX number
Logical MULTIBAND_REPORTING (BSC) B11 Yes B12 Yes
name TRX nb No
HMI MULTIBAND_REPORTING Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Minimum number of cells of each supported frequency band to be included in MEASUREMENT REPORT by the MS.
Coding rules Coded over 2 bits:
00: normal reporting of the six strongest cells, with known and allowed NCC part of BSIC, irrespective of the band used;
01: the MS shall report the strongest cell, with known and allowed NCC part of BSIC, in each of the frequency bands in the BA list, excluding the frequency band of
the serving cell;
10: the MS shall report the two strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the BA list, excluding the frequency band
of the serving cell;
11: the MS shall report the three strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the BA list, excluding the frequency
band of the serving cell.
Mandatory rules Equal to MULTIBAND_REPORTING (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical MULTIBAND_TRAFFIC_CONDITION B11 Yes B12 Yes
name TRX nb No
HMI MULTIBAND_TRAFFIC_CONDITION Sub-syste BSC Cell Type No
Definition This parameter determines the condition on traffic load in the serving cell to trigger a multiband handover (cause 21).
Coding rules 0: Any load, 1: Not low, 2: High
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MUXRTP_SIZE B11 No B12 Yes
name TRX nb No
HMI MUXRTP_SIZE Sub-syste BSC Cell Type No
Definition Threshold used to trigger the sending of a MUXRTP packet (MRLT). It is the minimum size above which a MUXRTP packet is sent. The size includes IP header, UDP header,
RTP header and payload.
A MUXRTP packet may be sent either its size is above the size threshold or the timer
T_MAX_HOLD_MUXRTP has expired
Category Site (CAE) OMC-R access Changeable Type Threshold Unit byte
Coding rules Step size = 100 bytes.
Mandatory rules --
Recommended --
rules
External Parameter change: Change apply immediately and to all established calls.
comment
Internal comment --
Logical MUXRTP_UDP_PORT_MASK B11 No B12 Yes
name TRX nb No
HMI MUXRTP_UDP_PORT_MASK Sub-syste BSC Cell Type No
Definition Mask defining the number of UDP ports allocated in the BSC, for A user plane over IP.
The present port mask and the associated port base (MUXRTP_UDP_PORT_START) define the UDP ports range, used for the MUXRTP protocol.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - This parameter is computed by the BSC.
Internal comment - default = FFF0x
- RTCP streams are not muxed
- the defined default range size is 000Fx= 16 values (but only 8 even UDP ports are used from the first configured)
Logical MUXRTP_UDP_PORT_START B11 No B12 Yes
name TRX nb No
HMI MUXRTP_UDP_PORT_START Sub-syste BSC Cell Type No
Definition Base of the UDP ports allocated in the BSC, for A user plane over IP.
The present port base and the associated port mask (MUXRTP_UDP_PORT_MASK) define the UDP ports range, used for the MUXRTP protocol.
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment - RTCP streams are not muxed
- default = 7FF0x
Logical MUXTRAUP_IP_ADDRESS_BSC B11 No B12 Yes
name TRX nb No
HMI MUXTRAUP_IP_ADDRESS_BSC Sub-syste BSC Cell Type No
Definition IP address of the TPIP/MUXTRAUP function in the BSC
Category Site (CAE) OMC-R access None (DLS) Type IP address Unit None
Mandatory rules --
Recommended --
rules
External - Parameter change: This parameter is changed via the START_BSS_IP_ADDRESS_BSC change by the operator from the BSC terminal.
comment - Significant if EN_AUP_OVER_IP is enabled.
Internal comment - function is hosted by the active TPGSM
- computed by the BSC = START_BSS_IP_ADDRESS_BSC + 2
Logical MUXTRAUP_SIZE B11 Yes B12 Yes
name TRX nb No
HMI MUXTRAUP_SIZE Sub-systeBSC Cell Type No
Definition Threshold used to trigger the sending of a MUXTRAUP packet. It is the minimum size above which a MUXTRAUP packet is sent. The size includes IP header, UDP header,
COM-H field and payload.
A MUXTRAUP packet may be sent either its size is above the size threshold or the timer
T_MAX_HOLD_MUXTRAUP has expired
Category Site (CAE) OMC-R access Changeable Type Threshold Unit byte
Coding rules Step size = 100 bytes.
Mandatory rules --
Recommended - The operator must ensure that the MTU in its network is greater than MUXTRAUP_SIZE + 80. If it is not the case, IPTCH does not work.
rules
External The value results on a compromise between BW efficiency and jitter. 500 is the highest value with which it works properly under extreme conditions....... (heavy load,
comment BTS chains etc.)
Change apply immediately and to all established calls.
Internal comment - The maximum MUXTRAUP packet size is equal to MUXTRAUP_SIZE + the max size of the last TRAUP frame, which depends on the codec used and type of call (HR,
FR,).
- Sent to the BTS via OML and to the TC via TCSL.
- This parameter can be > E1_MTU because the IP fragmentation in the TP (for DL) and in the SUM (for UL) doesnt apply to P0 traffic (speech).
Logical N_AVG_I (BSC) B11 Yes B12 Yes
name TRX nb No
HMI N_AVG_I (BSC) Sub-syste BSC Cell Type No
Definition N_AVG_I (BSC) value is broadcast to the (E)GPRS MS in the SI13. The (E)GPRS MS uses it for filtering the interference signal level measurements that it shall perform
during the packet transfer mode. These measurements are used by the (E)GPRS MS for output power control, but also reported to the network and used for performing
downlink link adaptation.
Coding rules coded on 4 bits
Mandatory rules Equal to N_AVG_I (MFS)
Recommended --
rules
External --
comment
Internal comment The Default value 6 has been used by the simulations performed by R&I, see report UTR/C/03/0011/V1 for detail.
Logical N_BAD_SACCH B11 Yes B12 Yes
name TRX nb No
HMI N_BAD_SACCH Sub-syste BSC Cell Type Yes
Definition Number of consecutive bad SACCH frames to trigger a rescue handover.
Coding rules --
Mandatory rules --
Recommended 1) N_BAD_SACCH = RADIOLINK_TIMEOUT_BS - N_BSTXPWR_M + 1

rules
2) In micro cells, it is recommended to set N_BAD_SACCH so that T_AUTOCLEANING_MEAS_REP > N_BAD_SACCH * 480ms + 30 seconds if
T_AUTOCLEANING_MEAS_REP <> 0.
External --
comment
Internal comment Meaningful only in cells where: Cell_type = Microcell
Logical N_BSTXPWR_M B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_RECOVERY_THRES Sub-syste BSC Cell Type Yes
Definition Counter threshold to trigger a radio link recovery.
Coding rules --
Mandatory rules N_BSTXPWR_M < RADIOLINK_TIMEOUT_BS
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message. CT: Depends on Cell Type and BTS Type
Logical N_CLR_REQ B11 Yes B12 Yes
name TRX nb No
HMI NB_CLR_REQ Sub-syste BSC Cell Type No
Definition Maximum number of CLEAR REQUEST message transmission.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_DELAYED_HO_CAUSE30 B11 Yes B12 Yes
name TRX nb No
HMI N_DELAYED_HO_CAUSE30 Sub-syste BSC Cell Type No
Definition Number of TCH usage information update periods to be waited by the BSC before moving the TCH of a DTM capable MS from the PS zone to the CS zone (intracell
handover cause 30).
"zero" means that the feature "avoid ping-pong between CS and PS zones for DTM MS" is not activated.
Coding rules --
Mandatory rules --
Recommended --
rules
External - Parameter change : no impact on the telecom service. Change applied on the handovers cause 30 detected after the modification (didn't apply on running timers).
comment - Function available on BSC Evolution only.
- the delay applied by the BSC is between N_DELAYED_HO_CAUSE30 * TCH_INFO_PERIOD and (N_DELAYED_HO_CAUSE30 + 1) * TCH_INFO_PERIOD
Internal comment The delay cannot be armed by the BSC while EN_RETURN_CS_ZONE_HO is disabled in the cell.
Logical N_PREF_CELLS B11 Yes B12 Yes
name TRX nb No
HMI NB_PREF_CELLS Sub-syste BSC Cell Type No
Definition Maximum number of candidate cells sent in one HANDOVER REQUIRED.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N_TCH_HO B11 Yes B12 Yes
name TRX nb No
HMI N_TCH_HO Sub-syste BSC Cell Type No
Definition Number of less interfered Full Rate TCH reserved for handover.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_threshold B11 Yes B12 Yes
name TRX nb No
HMI TCH load threshold for Auto AC Sub-syste BSC Cell Type No
Definition Threshold on busy TCH timeslots percentage for automatic barring of access classes.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_TRAFFIC_LOAD B11 Yes B12 Yes
name TRX nb Yes
HMI N_TRAFFIC_LOAD Sub-syste BSC Cell Type No
Definition Number of consecutive load averages used in traffic load evaluation process.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N1 B11 Yes B12 Yes
name TRX nb No
HMI Nbr. AC 0-9 barred in one step Sub-syste BSC Cell Type No
Definition Number of low priority access classes (0..9) are barred in one step.
Coding rules Value 0 inhibits the automatic barring of low priority access classes.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
HMI Nbr. AC 0-9 unbarred in one step Sub-syste BSC Cell Type No
Definition Number of low priority access classes (0..9) are unbarred in one step.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N200_GSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI N200_GSL (BSC) Sub-syste BSC Cell Type No
Definition Maximum number of re-transmissions on a GSL link.
Coding rules --
Mandatory rules Equal to N200_GSL (MFS)
Recommended T_GSL_Ack (BSC) > T200 (GSL) * (1 + N200 (GSL))

rules
External --
comment
Internal comment --
Logical N200_OML (BSC) B11 Yes B12 Yes
name TRX nb No
HMI N200_OML (BSC) Sub-syste BSC Cell Type No
Definition Maximum number of re-transmissions of a LAPD frame on an OML.
Coding rules --
Mandatory rules --
Recommended The recommended value for Abis via satellite is 5.

rules
External The value of this parameter is driven by the associated Abis connection type
comment The default value 12 corresponds to Abis terrestrial link.
Internal comment --
Logical N200_RSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI N200_RSL (BSC) Sub-syste BSC Cell Type No
Definition Maximum number of retransmissions of a LAPD frame on a RSL.
Coding rules --
Mandatory rules --
Recommended N200_RSL (BSC) = N200_RSL (BTS) + 2

rules The recommended value for Abis via satellite is 5.
External The value of this parameter is driven by the associated Abis connection type
Internal comment --
Logical N201 (BSC) B11 Yes B12 Yes
name TRX nb No
HMI N201 (BSC) Sub-syste BSC Cell Type No
Definition Maximum number of bytes in Information part of an I frame sent by the BSC.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N201_GSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI N201_GSL (BSC) Sub-syste BSC Cell Type No
Definition Maximum number of bytes in Information part of an I frame sent by the BSC on the GSL link.
Coding rules --
Mandatory rules Equal to N201_GSL (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical N2X4 B11 Yes B12 Yes
name TRX nb No
HMI N2X4 Sub-syste BSC Cell Type No
Definition Maximum number of polling in case of peer entity busy condition.
Coding rules 0: the polling continues forever until the status of the peer entity becomes non-busy again, <> 0: after polling N2X4 times, LAPD re-establishment is forced
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NB_MAX_ACTIVE_TCH_TS B11 Yes B12 Yes
name TRX nb No
HMI NB_MAX_ACTIVE_TCH_TS Sub-syste
BSC Cell Type No
name Instance
Abis group RMS No
Definition Maximum number of RTSs supporting some TCH(s) at the same time (one FR TCH or two HR TCHs) in one Abis BTS group.
The RTSs supporting only one HR TCH are counted as half a RTS.
Mandatory rules --
Recommended --
rules
External This limit of 8000 TCH TSs is a simple theoretical limit based on 8TS*1000TRX (because at most 1000 TRXs per MX-BSC). Due to the presence of signalling channels,
comment this upper limit will never be reached. Additionally, because the MFS will map all cells of a same Abis group on a same GP/GPU, operator shall take care not to build too
large Abis group to take benefit of all equipped GPs/GPUs.
This parameter is calculated by both OMC and BSC, based on the channel configuration of the TRXs mapped on the BTS of this Abis group, and on the TCH
occupancy factor.
Internal comment - Shall be displayed at OMC-R.
Logical NB_MAX_MSG_MULTIPLE_PAGING_CMD B11 Yes B12 Yes
name TRX nb No
HMI NB_MAX_MSG_MULTIPLE_PAGING_CMD Sub-syste
BSC Cell Type No
name Instance
BSC RMS No
Definition Number of paging messages that shall be included in the Abis message MULTIPLE PAGING COMMAND before sending it to the BTS (except if
T_SEND_MULTIPLE_PAGING_CMD expires before this limit is reached).
This is also the number of paging messages that shall be included in the BSCGP message PAGING COORDINATION REQUEST before sending it to the MFS (except if
T_SEND_MULTIPLE_PAGING_CMD expires before this limit is reached).
Mandatory rules --
Recommended --
rules
External Value 1 disables the function (i.e. Paging Command message is used on Abis).
comment When EN_BSS_PAGING_COORDINATION is disabled, the multiple paging on BSCGP is disabled too.
Internal comment In order to test it in the BSC, in front of a BTS simulator, the default value shall manually be changed in the BSC DLS to 5.
Logical NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC B11 Yes B12 Yes
name TRX nb No
HMI NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC Sub-syste BSC Cell Type No
Definition In a G2 BSC, Xoff threshold (in terms of number of BSCGP messages queued in the GSL output buffer) above which channel requests are no longer allowed to be sent
on this GSL link.
The interest of those Xon/Xoff thresholds is to avoid GSL output buffer overflow.
Coding rules --
Mandatory rules NB_MSG_GSL_OUTPUT_BUFFER_XON_G2_BSC < NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC
Recommended --
rules
External Applicable only to TDM mode.
comment
Internal comment - In case of GSL output buffer overflow, all outstanding BSCGP messages are discarded and the GSL link is re-established by the BSC.
- A high value will tend to decrease the efficiency of the BSC defence to avoid GSL output buffer overflow.
- A low value can lead to discard too many PS channel requests (QoS degradation).
- The default value is the results of load tests performed on G2 BSC in B10, which brought DTC stability (no reset)
Logical NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC B11 Yes B12 Yes
name TRX nb No
HMI NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC Sub-syste BSC Cell Type No
Definition In an Evolution BSC, Xoff threshold (in terms of number of BSCGP messages queued in the GSL output buffer) above which channel requests are no longer allowed to
be sent on this GSL link.
Coding rules --
Mandatory rules NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC < NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC
Recommended --
rules
comment
- A high value will tend to decrease the efficiency of the BSC defence to avoid GSL output buffer overflow.
- A low value can lead to discard too many PS channel requests (QoS degradation).
Logical NB_MSG_GSL_OUTPUT_BUFFER_XON_G2_BSC B11 Yes B12 Yes
name TRX nb No
HMI NB_MSG_GSL_OUTPUT_BUFFER_XON_G2_BSC Sub-systeBSC Cell Type No
Definition In a G2 BSC, Xon hysteresis threshold (in terms of number of BSCGP messages queued in the GSL output buffer) below which channel requests can again be sent on
this GSL link.
Coding rules --
Mandatory rules NB_MSG_GSL_OUTPUT_BUFFER_XON_G2_BSC < NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC
Recommended --
rules
comment
- The default value is the results of load tests performed on G2 BSC in B10, which brought DTC stability (no reset)
Logical NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC B11 Yes B12 Yes
name TRX nb No
HMI NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC Sub-syste BSC Cell Type No
Definition In an Evolution BSC, Xon hysteresis threshold (in terms of number of BSCGP messages queued in the GSL output buffer) below which channel requests can again be
sent on this GSL link.
Coding rules --
Mandatory rules NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC < NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC
Recommended --
rules
External Applicable only to TDM mode
comment
Internal comment In case of GSL output buffer overflow, all outstanding BSCGP messages are discarded and the GSL link is re-established by the BSC.
Logical Nb_of_reserved_slots_for_basic_CBCH B11 Yes B12 Yes
name TRX nb No
HMI Reserved Slots Number for Basic CBCH Sub-syste BSC Cell Type No
Definition This parameter indicates the number of slots reserved for high priority messages within the schedule period for basic CBCH.
Coding rules --
Mandatory rules shall be set to "0" when SMSCB_FEATURE_SET="FS1"
Recommended --
rules
External --
comment
Internal comment --
Logical Nb_of_reserved_slots_for_extended_CBCH B11 Yes B12 Yes
name TRX nb No
HMI Reserved Slots Number for Extended CBCH Sub-syste BSC Cell Type No
Definition This parameter indicates the number of slots reserved for high priority messages within the schedule period for extended CBCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NB_TS_MPDCH (BSC) B11 Yes B12 Yes
name TRX nb No
HMI NB_TS_MPDCH Sub-syste BSC Cell Type No
Definition Number of radio timeslots reserved for the primary and secondary master PDCHs defined in the cell.
Coding rules --
Mandatory rules 0) NB_TS_MPDCH = 0
1) MIN_PDCH > NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = enabled; MIN_PDCH >= NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = disabled.
2) if the network_operation_mode (BSC) parameter is set to 2 (NMO II) then all cells of the BSS must have NB_TS_MPDCH = 0
iii) MAX_PDCH <= NB_TS_MPDCH + 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX.
4) When cell_type = extended inner or extended outer, then NB_TS_MPDCH = 0
Recommended --
rules
External - Only the value 0 is supported
comment - The Master PDCH requires the establishment of a GCH (Abis and Ater) which does not carry traffic. In case of Abis or Ater through satellite link, the usage of the
MPDCH must consider the following criteria:
* higher cost of transmission resources through the satellite link;
* limited throughput of the RSL in case of Abis through satellite to about 6 kbit/s (because of round trip delay effect on acknowledged protocol with limited LAP-D
window size). In case of important CS signalling load, the RSL may not be able to transport the additional signalling load due toTBF establishments when no MPDCH is
established.
Hence the recommendation in the GPRS through satellite case is:
* for a cell connected with Abis through satellite and with non negligible signalling load (CS+PS), MPDCH is recommended;
* for a cell connected with Ater through satellite, MPDCH is not recommended.
Internal comment 0: MPDCH is not configured in the cell;
1: only one static primary MPDCH is configured in the cell;
2: one static primary MPDCH and one static secondary MPDCH are configured in the cell;
3: one static primary MPDCH and two static secondary MPDCH are configured in the cell; m
4: one static primary MPDCH and three static secondary MPDCH are configured in the cell.
template
Logical NB_WAIT_SMLC_RESET_ACK B11 Yes B12 Yes
name TRX nb No
HMI NB_WAIT_SMLC_RESET_ACK Sub-syste BSC Cell Type No
Definition Maximum number of consecutive attempts for the RESET procedure on the Lb interface (for sending the TS 49.031 RESET message to the SMLC).
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Significant if EN_RESET_LB is enabled
Internal comment --
Logical NBLK B11 Yes B12 Yes
name TRX nb No
HMI NBLK Sub-syste BSC Cell Type No
Definition Maximum number of BLOCK messages that can be sent if the ACK from the MSC is not received.
Coding rules 255: infinite transmission
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NBR_RESET_CIC_REP B11 Yes B12 Yes
name TRX nb No
HMI NBR_RESET_CIC_REP Sub-syste BSC Cell Type No
Definition Maximum number of RESET CIRCUIT message repetitions when not acknowledged by the MSC.
Coding rules 255: RESET CIRCUIT message is indefinitely repeated
Mandatory rules --
Recommended --
rules
External --
comment
Logical NBR_RESET_IP_REP B11 No B12 Yes
name TRX nb No
HMI NBR_RESET_IP_REP Sub-syste
BSC Cell Type No
name Instance
BSC RMS No
Definition Maximum number of RESET IP RESOURCE message repetitions when not acknowledged by the MSC
Spec ref. Reset Circuit/IP resource & Blocking Coded Max 255
Coding rules 255: message is indefinitely repeated
Mandatory rules --
Recommended --
rules
External - Parameter change: No impact on the telecom service, on going calls are not disrupted.
comment
Logical NBR_RESET_REP B11 Yes B12 Yes
name TRX nb No
HMI NBR_RESET_REP Sub-syste BSC Cell Type No
Definition Number of times the RESET message is sent without being acknowledged by the MSC before an alarm is reported.
Spec ref. BSS global reset Coded Max 127
Coding rules If NBR_RESET_REP = 0, RESET message is not sent
Mandatory rules --
Recommended --
rules
External --
comment
Logical NBR_STEPS_OVRL_1 B11 Yes B12 Yes
name TRX nb No
HMI NBR_STEPS_OVRL_1 Sub-syste BSC Cell Type No
Definition Number of steps needed to reduce the load upon TCU overload level 1.
Coding rules --
Mandatory rules --
Recommended NBR_STEPS_OVRL_1 <= NBR_STEPS_OVRL_2

rules
External --
comment
Internal comment --
Logical NBR_STEPS_OVRL_2 B11 Yes B12 Yes
name TRX nb No
HMI NBR_STEPS_OVRL_2 Sub-syste BSC Cell Type No
Definition Number of steps to reduce the load upon TCU overload level 2.
Coding rules --
Mandatory rules --
Recommended NBR_STEPS_OVRL_2 >= NBR_STEPS_OVRL_1

rules
External --
comment
Internal comment --
Logical NCC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI NCC Sub-syste BSC Cell Type No
Definition Network Colour code of the cell.
Coding rules Coded over 3 bits.
Mandatory rules - Equal to NCC (MFS)

- NCC (BSC) shall be included in NCC_permited
Recommended --
rules
comment
Logical NCC_permitted B11 Yes B12 Yes
name TRX nb No
HMI NCC permitted Sub-syste BSC Cell Type No
Definition Indicates which NCC values the MS considers as belonging to the network.
Coding rules Coded over 8 bits. each bit corresponds to a NCC value: MSB corresponds to NCC = 7, LSB corresponds to NCC = 0. For each bit:0= NCC not permitted, 1= NCC
permitted
Mandatory rules NCC of the serving cell and of its neighbor cells shall be included in NCC_permited
Recommended --
rules
comment
Internal comment This parameter was previously named: PLMN_permitted.
Logical NCI B11 Yes B12 Yes
name TRX nb No
HMI NCI Sub-syste BSC Cell Type No
Definition This flag indicates to the MS if it reports a HANDOVER FAILURE in case of out of range timing advance.
Coding rules 0: Out of range timing advance is ignored, 1: Out of range timing advance triggers a Handover Failure procedure
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NECI (BSC) B11 Yes B12 Yes
name TRX nb No
HMI NECI (BSC) Sub-syste BSC Cell Type No
Definition New Establishment Causes Indicator. Indicates to the MS if the network supports the new GSM Phase 2 establishment causes in CHANNEL REQUEST.
Coding rules 0: not supported, 1: supported
Mandatory rules Equal to NECI (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical NEIGHBOUR_RXLEV(0,n) B11 Yes B12 Yes
name TRX nb No
HMI NEIGHBOUR_RXLEV Sub-syste BSC Cell Type Yes
Definition Threshold of maximum received level from the neighbour cells for cause 13.
Coding rules coded over 6 bits: 0: -110 dBm, 1: -109 dBm...63: -47 dBm
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical network_operation_mode (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Network_mode_of_operation Sub-syste BSC Cell Type No
Definition This parameter defines the CS-PS co-ordination for paging.
Coding rules 3 possible values : 1, 2, 3; 1 == Network operation mode I ; 2 == Network operation mode II ; 3 == Network operation mode III.
Mandatory rules Equal to network_operation_mode (MFS).
External Any change will trigger a data reset of the GPUs. Stop and restart of (E)GPRS traffic in all the cells of the BSS.
comment NMO I requires a Gs interface.
Internal comment Corresponds to NMO in Sys info 13.
Coding at radio interface is different, i.e. 0 == Network operation mode I; 1 == Network operation mode II; 2 == Network operation mode III.
Logical NO_CLEAR_REQUEST_AFTER_DISC_RATIO B11 Yes B12 Yes
name TRX nb No
HMI NO_CLEAR_REQUEST_AFTER_DISC_RATIO BSC Sub-syste Cell Type No
name BSC Instance RMS No
Definition Ratio of CLEAR REQUEST not sent to MSC when the timer T_CLEAR_REQUEST_AFTER_DISC runs.
Category Site (CAE) OMC-R access None (DLS & Restricted) Type Number Unit %
Mandatory rules --
Recommended --
rules
- this parameter is configurable (by ALU team) from the BSC terminal (from lab version)
Logical NOTIF_FACCH_OTHER_VGCS_CALL_THR B11 Yes B12 Yes
name TRX nb No
HMI NOTIF_FACCH_OTHER_VGCS_CALL_THR Sub-syste BSC Cell Type No
Definition If the eMLPP priority is higher than or equal to this parameter, the Notifications message shall be sent on FACCH of all other on-going VGCS call.
000 : deactivation of notification on FACCH of other on-going VGCS calls
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NOTIF_FACCH_PTP_CALL_THR B11 Yes B12 Yes
name TRX nb No
HMI NOTIF_FACCH_PTP_CALL_THR Sub-syste BSC Cell Type No
Definition If the eMLPP priority is higher than or equal to this parameter, the Notifications message shall be sent on FACCH of all on-going point to point call whose MS is VGCS
capable.
000 : deactivation of notification on FACCH of all on going point to point calls in the cell
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NOTIF_PCH_THR B11 Yes B12 Yes
name TRX nb No
HMI NOTIF_PCH_THR Sub-syste BSC Cell Type No
Definition The priority threshold for notification over PCH.
The BSS shall consider, for Notification/PCH, only VGCS-Calls which have a priority (eMLPP priority) not below this parameter. If more than one is selected, all these voice
group calls shall be notified on PCH and all with the same frequency of occurrence.
000 : deactivation of notification on PCH in the cell
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NRI_LENGTH B11 Yes B12 Yes
name TRX nb No
HMI NRI_LENGTH Sub-syste BSC Cell Type No
Definition This parameter defined the configurable length of a NRI (Network Resource Identification), expressed as a number of bits It is used by the BSC to derive the NRI value
from the received temporary identity TMSI, and to identify the serving MSC, connected to the BSC (Aflex feature). The NRI is coded starting from the bit 23 (the most
significant bit of the NRI) of the TMSI, regardless of the NRI length.
Coding rules The coded default value is for implementation purposes only; this dummy value indicates that the operator does not provide any length value yet.
Mandatory rules - Each NRI of the list <= 2^NRI_LENGTH - 1

- NULL_NRI <= 2^NRI_LENGTH 1
Recommended - The operator must control that the same NRI_LENGTH is configured in all the BSSs belonging to a same pool area.
rules - A larger length allows to define/connect more MSCs per CS pool area, but reduce the number of available TMSI for a given time period, since the NRI is part of the
TMSI.
Parameter change: No impact on the telecom service, on going calls are not disrupted (still established with the same MSC). Change applied immediately on the new
Internal comment - The value (5) allows to define up to 2^5-1 = 31 NRI, so 31 MSC. A length of 4 allows only 15 MSC. Up to 16 MSC have been committed.
- According to TS23.236, the length of the NRI shall be the same in all nodes of a domain in a pool area.
Logical NRI_LIST B11 Yes B12 Yes
name TRX nb No
HMI NRI_LIST Sub-syste BSC Cell Type No
Definition List of the Network Resource Identifiers, associated to a given MSC, connected to the BSC (Aflex feature). Up to 8 NRIs can be defined per MSC.
The NRI is part of the temporary identity TMSI, which is assigned by the serving MSC to the MS. The BSC derives the NRI from any Initial layer 3 message, in order to
identify the serving MSC.
Coding rules Coded on 2 bytes
The empty list (length = 0) value 1024 is for implementation purpose only; this dummy list indicates that the operator does not provide any NRI yet.
Mandatory rules - 2 different MSCs, connected to the BSC, must have 2 different NRI_LIST.
- A NRI shall be unique among all the NRI_LIST of all the MSCs connected to the BSC (and especially when the BSC is in the overlapping zone of 2 CS pool areas).
- Each NRI of the list <= 2^NRI_LENGTH 1
- The NULL_NRI shall not be included in any NRI_LIST of any MSCs connected to the BSC
- When EN_A_FLEX is enabled, the NRI_LIST must contain at least one NRI
Recommended - The operator must control that one NRI shall be unique among all the NRI_LIST of all the MSCs, which serve in parallel a given CS pool area.
rules - When several BSCs, belonging to the same CS pool area, are connected to the same MSC, the operator must control that the NRI_LIST of that MSC is configured with
the same value in each BSC of the CS pool area.
Internal comment - According to 3GPP TS 23.236, more than one NRI may be assigned to a CN node.
Logical NRT_GUARANTEED_BANDWIDTH_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI NRT_GUARANTEED_BANDWIDTH_FACTOR Sub-syste BSC Cell Type No
Definition Percentage of reserved PS bandwidth (Abis bandwidth) which is not considered as usable for GBR PS traffic by the MFS.
This parameter enables to guarantee, in each Abis BTS group supported by the BSC:
- a minimum bandwidth for Best Effort PS traffic,
- the necessary bandwidth for PS related control traffic (PMU-PTU and IPGCH control traffic),
- the necessary bandwidth for the transmission of all the IP/UDP/IPGCH headers (for Best Effort + GBR PS traffic), provided the reserved PS bandwidth is not null (or
very low) for the Abis BTS group.
Coding rules Step size = 1%.
Mandatory rules In case of a BTS with several Abis/E1 links, NRT_GUARANTEED_BANDWIDTH_FACTOR shall take the same value on each link.
Recommended --
rules
External Depending on the IPGCHU segment size, the necessary bandwidth for the transmission of all the IP/UDP/IPGCH headers (for Best Effort + GBR PS traffic) may not be
comment negligible. Example: IP header (20 bytes) + UDP header (8 bytes) + IPGCH header (a few bytes) will represent around 10% of the total Abis bandwidth consumption if
the IPGCHU segment size is 300 bytes.
Internal comment --
Logical NUBLK B11 Yes B12 Yes
name TRX nb No
HMI NUBLK Sub-syste BSC Cell Type No
Definition Maximum number of UNBLOCK messages that are sent if the ACK from the MSC is not received.
Coding rules 255: infinite transmission
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NULL_NRI B11 Yes B12 Yes
name TRX nb No
HMI NULL_NRI Sub-systeBSC Cell Type No
Definition Upon reception of a message with that dummy/reserved NRI included, the BSC uses the load balancing algorithm for selecting one MSC, among the on loaded MSC
connected to the BSC (Aflex feature), and for re-routing the received message to that MSC.
The coded default value is for implementation purposes only; this dummy value indicates that the operator does not provide any null NRI yet.
Mandatory rules - NULL_NRI <= 2^NRI_LENGTH - 1
- The NULL_NRI shall not be included in any NRI_LIST of any MSCs connected to the BSC.
Recommended The operator must control that the NULL_NRI is common inside all the BSSs of one PLMN.
rules
Parameter change: No impact on the telecom service, on going calls are not disrupted (still established with the same MSC). Change applied immediately on the new
Internal comment - According to TS23.236, there is one unique null NRI in a PLMN.
Logical NUM_TCH_EGNCY_HO B11 Yes B12 Yes
name TRX nb No
HMI NUM_TCH_EMERGENCY_HO Sub-syste BSC Cell Type No
Definition Number of full rate TCH reserved for incoming emergency handovers (plus Cause 12 and Cause 27 handovers).
Mandatory rules --
Recommended --
rules
External The Pre-emption procedure (in case EN_TCH_PREEMPT = enabled) might use these reserved TCHs in order to avoid releasing an on-going call unnecessarily.
comment
Internal comment --
Logical NUMBER_NCH_BLOCKS B11 Yes B12 Yes
name TRX nb No
HMI NUMBER_NCH_BLOCKS Sub-syste BSC Cell Type No
Definition This parameter defines the maximum number of blocks usable for NCH.
Rec ref. 3GPP TS 44.018 Domai VGCS Min value 1 Coded Min 1
Coding rules --
Mandatory rules if EN_VGCS is enabled :

- BS_AG_BLKS_RES >= NUMBER_NCH_BLOCKS
- if BCCH_EXT = true, then BS_AG_BLKS_RES > NUMBER_NCH_BLOCKS
Recommended --
rules
External The parameter is significant when EN_VGCS is enabled
comment
Internal comment --
Logical NY1 B11 Yes B12 Yes
name TRX nb No
HMI NY_1 Sub-syste BSC Cell Type No
Definition Maximum number of repetitions of PHYSICAL INFORMATION.
Coding rules --
Mandatory rules For rules, see T3105_D and T3105_F_FR, T3105_F_HR.
Recommended For rules, see T3105_D and T3105_F_FR, T3105_F_HR.

rules
External --
comment
Logical NY2 B11 Yes B12 Yes
name TRX nb No
HMI NY2 Sub-syste BSC Cell Type No
Definition Maximum number of repetitions for the VGCS UPLINK GRANT message during an uplink access procedure
Rec ref. 3GPP TS 44.018 Domai VGCS Min value 1 Coded Min 1
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment It is a CDM parameter
Logical OandM_PRIORITY (BSC) B11 Yes B12 Yes
name TRX nb No
HMI OandM_PRIORITY (BSC) Sub-syste BSC Cell Type No
Definition BSS internal priority used by the O&M flows in IP network
3: lower priority
Mandatory rules Equal to OandM_PRIORITY (MFS)
Recommended --
rules
External --
comment
Internal comment - Sent to the TC via TCSL.
Logical OFFSET_CA_HIGH B11 Yes B12 Yes
name TRX nb No
HMI OFFSET_CA_HIGH Sub-syste BSC Cell Type No
Definition Offset for AMR-NB HR-to-FR channel adaptation hysteresis under high load (Handover Cause 26).
Coding rules step size = 0.1 (0 coded as 0, 0.1 coded as 1 7 coded as 70)
Mandatory rules OFFSET_CA_HIGH >= OFFSET_CA_NORMAL
Recommended --
rules
External --
comment
Internal comment --
Logical OFFSET_CA_NORMAL B11 Yes B12 Yes
name TRX nb No
HMI OFFSET_CA_NORMAL Sub-syste BSC Cell Type No
Definition Offset for AMR-NB HR-to-FR channel adaptation hysteresis under normal load (Handover Cause 26).
Mandatory rules OFFSET_CA_HIGH >= OFFSET_CA_NORMAL
Recommended --
rules
External --
comment
Internal comment --
Logical OFFSET_HO_MARGIN_INNER B11 Yes B12 Yes
name TRX nb No
HMI OFFSET_HO_MARGIN_INNER Sub-syste BSC Cell Type No
Definition Offset which allows to take into account the radio differences between the inner and the outer zone (especially in multiband cells).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Offset_Hopping_HO B11 Yes B12 Yes
name TRX nb No
HMI OFFSET_HOPPING_HO Sub-syste BSC Cell Type No
Definition Offset applied in the handover quality causes for radio hopping channels.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Relative value added to L_RXQUAL_UL_H and L_RXQUAL_DL_H
Logical Offset_Hopping_PC B11 Yes B12 Yes
name TRX nb No
HMI OFFSET_HOPPING_PC Sub-syste BSC Cell Type No
Definition Offset applied in the power control quality causes for hopping radio channels.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Relative value added to L_RXQUAL_UL_P and L_RXQUAL_DL_P
Logical OPC B11 Yes B12 Yes
name TRX nb No
HMI Own SPC Sub-syste BSC Cell Type No
Definition Signalling Point Code of the BSC.
Mandatory rules --
Recommended --
rules
External - Must be equal to DPC and SSF used by the MSC and RNC and SMLC for adressing the BSC.
comment - Default value depends on configuration. The value indicated here is for implementation purposes.
- Parameter change: Before any modification of the OPC, the BSS-TEL is to be previously locked. This procedure leads the BSC to reject any new calls and wait for
some minutes (Wait Traffic Clear) before shutting down the on going calls.
After modification of the OPC, the operator shall trigger a BSC restart. The locked objects must be unlocked again to reopen the telecom service.
Internal comment --
Logical Operator B11 Yes B12 Yes
name TRX nb No
HMI CBC_Operator Sub-syste BSC Cell Type No
Definition Identifies the CBC operator.
Coding rules 0 to 20 characters string (default = empty string) are sent by the OMC on the OMC/BSC interface . BSC performs the padding of OMC string with space characters
on the right side of the string until 20 bytes are reached. At Upload, OMC RNL removes padded space characters from the retrieved BSC value.
Recommended --
rules
comment
Internal comment --
Logical OUTDOOR_UMB_LEV(0,n) B11 Yes B12 Yes
name TRX nb No
HMI OUTDOOR_UMB_LEV Sub-syste BSC Cell Type Yes
Definition Minimum received level from umbrella cell n to allow handover cause level uplink micro-cell or level downlink micro-cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Lower layer.
Used to prevent indoor MS going to umbrella.
Logical P0_LAYER2_MAPPING_BSC B11 Yes B12 Yes
name TRX nb No
HMI P0_LAYER2_MAPPING_CS Sub-syste BSC Cell Type No
Definition Defines, for BSC CS applications, BTS and TC, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P0 internal priority (the highest).
Mandatory rules P0_LAYER2_MAPPING_BSC >= P1_LAYER2_MAPPING_BSC
Recommended The operator shall ensure that it is equal to P0_LAYER2_MAPPING_MFS

rules
External Each internal priority can be mapped to a L2 priority using the parameter Px_layer2_mapping and mapped to a L3 priority using the parameter Px_layer3_mapping.
comment
Internal comment - Sent to the BTS via OML and to the TC via TCSL.
name TRX nb No
Definition Defines the Diffserv DSCP value used on the IP network by BSC CS applications, BTS or TC flows having the P0 internal BSS priority (P0 is the highest priority).
Rec ref. RFC 2474/2475, 2598 Domai IP Min value 0 Coded Min 0
Only a subset of the possible values are defined in the standard:
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
Logical P0_TP_QUEUE_MAPPING B11 Yes B12 Yes
name TRX nb No
HMI P0_TP_QUEUE_MAPPING Sub-syste BSC Cell Type No
Definition Defines which queue is used in the TP board by the flows having the P0 internal priority (the highest priority).
Rec ref. IEEE 802.1 Q Domai IP Min value 0 Coded Min 0
Coding rules step size = 1; queue 3 is the highest priority queue
Mandatory rules --
Recommended Queue 3 (highest priority queue) shall not be used (it is reserved to NE1oE traffic)
rules
External --
comment
Internal comment - Due to the fact that the queue 3 is reserved to the NE1oE internal Mx-BSC traffic, the flows having P1 and P2 internal priorities are mapped to the same queue.
name TRX nb No
Definition Defines, for BSC CS applications, BTS and TC, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P1 internal priority.
Mandatory rules P0_LAYER2_MAPPING_BSC >= P1_LAYER2_MAPPING_BSC >= P2_LAYER2_MAPPING_BSC

rules
comment
name TRX nb No
Definition Defines the Diffserv DSCP value used on the IP network by BSC CS applications, BTS or TC flows having the P1 internal BSS priority (P3 is the lowest priority).
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
name TRX nb No
Definition Defines which queue is used in the TP board by the flows having the P1 internal priority.
Mandatory rules --
rules
External --
comment
name TRX nb No
Definition Defines, for BSC CS applications, BTS and TC, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P2 internal priority.

rules
comment
name TRX nb No
Definition Defines the Diffserv DSCP value used on the IP network by BSC CS applications, BTS or TC flows having the P2 internal BSS priority (P3 is the lowest priority).
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
name TRX nb No
Definition Defines which queue is used in the TP board by the flows having the P2 internal priority.
Mandatory rules --
rules
External --
comment
name TRX nb No
Definition Defines, for BSC CS applications, BTS and TC, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P3 internal priority (the lowest).
Coding rules step size = 1.

rules
comment
name TRX nb No
Definition Defines Diffserv DSCP value used on the IP network by BSC CS applications, BTS or TC flows having the P3 internal BSS priority (P3 is the lowest priority).
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
name TRX nb No
Definition Defines which queue is used in the TP board by the flows having the P3 internal priority (the lowest priority).
Mandatory rules --
rules
External --
comment
Logical PAG_BAR B11 Yes B12 Yes
name TRX nb No
HMI PAGING Sub-syste BSC Cell Type No
Definition This flag indicates if transmission of Pagings is allowed in the cell.
Coding rules 0: Pagings are not barred, 1: Pagings are barred
Mandatory rules --
Recommended --
rules
External this flag can be used by an operator to temporarily prevent phones from ringing in specific cells
comment
Internal comment --
Logical PAIRING_PRIORITIES_NON_SAIC B11 No B12 Yes
name TRX nb No
HMI PAIRING_PRIORITIES_NON_SAIC Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter configures the VAMOS pairing priorities for a legacy
non SAIC capable MS. The digit having the lowest value represents the most prefered pairing.
Category Network (CDE) OMC-R access None (DLS) Type List of numbers Unit None
Coding rules Coded on 6 digits BCD, as follows:
digit 6 (most left):priority value for pairing with legacy non SAIC MS
digit 5: priority value for pairing with legacy SAIC MS
digit 4: priority value for pairing with VAMOS1 MS (using TSC Set1)
digit 1 (most right): priority value for pairing with VAMOS2 MS (using TSC Set2)
Mandatory rules digit 6 is ignored

digit 5 is ignored
digit 4 is ignored
digit 3 is ignored when EN_PAIRING_NON_SAIC_VAMOS1 = 0
digit 2 is ignored
digit 1 is ignored when EN_PAIRING_NON_SAIC_VAMOS2 = 0
Each digit shall be in the range 1,,6
Recommended --
rules
Internal comment - digit 6 and digit 5 are ignored because NON SAIC can be paired only with VAMOS1 or VAMOS2
- digit 4 and digit 2 are ignored because NON SAIC uses TSC Set1 only.
Logical PAIRING_PRIORITIES_SAIC B11 No B12 Yes
name TRX nb No
HMI PAIRING_PRIORITIES_SAIC Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter configures the VAMOS pairing priorities for a legacy
SAIC capable MS.
The digit having the lowest value represents the most prefered pairing.
Mandatory rules digit 6 is ignored

digit 5 is ignored when EN_PAIRING_SAIC_SAIC = 0
digit 4 is ignored
digit 3 is ignored when EN_PAIRING_SAIC_VAMOS1 = 0
digit 2 is ignored
Recommended --
rules
Internal comment - digit 6 is ignored because SAIC can be paired only with SAIC or VAMOS1 or VAMOS2
- digit 4 and digit 2 are ignored because SAIC uses TSC Set1 only.
Logical PAIRING_PRIORITIES_VAMOS1 B11 No B12 Yes
name TRX nb No
HMI PAIRING_PRIORITIES_VAMOS1 Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter configures the VAMOS pairing priorities for a
VAMOS1 capable MS.
Mandatory rules digit 6 is ignored when EN_PAIRING_NON_SAIC_VAMOS1 = 0

digit 4 is ignored when EN_PAIRING_VAMOS1_VAMOS1 = 0
Recommended --
rules
Internal comment --
Logical PAIRING_PRIORITIES_VAMOS2 B11 No B12 Yes
name TRX nb No
HMI PAIRING_PRIORITIES_VAMOS2 Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter configures the VAMOS pairing priorities for a
VAMOS2 capable MS.
Mandatory rules digit 6 is ignored when EN_PAIRING_NON_SAIC_VAMOS2 = 0

Recommended --
rules
Internal comment --
Logical PAN_DEC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI PAN_DEC Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Value decremented from MS N3102 counter when PACKET UL ACK/NACK is not received before MS timer T3182.
Coding rules Binary coded on 3 bits
Mandatory rules Equal to PAN_DEC (MFS)
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection
Logical PAN_INC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI PAN_INC Sub-syste BSC Cell Type No
Definition Value incremented to MS N3102 counter when PACKET UL ACK/NACK is received by MS.
Mandatory rules Equal to PAN_INC (MFS)
Recommended --
rules
External --
comment
Logical PAN_MAX (BSC) B11 Yes B12 Yes
name TRX nb No
HMI PAN_MAX Sub-syste BSC Cell Type No
Definition Maximum value for counter N3102. cell reselection is done by MS when N3102 <= 0.
Coding rules Possible values : 4, 8, 12., 32 respectively binary coded 000, 001, , 111
Mandatory rules Equal to PAN_MAX (MFS)
Recommended --
rules
External --
comment
Logical Password B11 Yes B12 Yes
name TRX nb No
HMI CBC_Password Sub-syste BSC Cell Type No
Definition CBC password.
Coding rules 0 to 20 characters string (default = empty string) are sent by the OMC on the OMC/BSC interface. BSC performs the padding of OMC string with space characters on
the right side of the string until 20 bytes are reached. At Upload, OMC RNL removes padded space characters from the retrieved BSC value.
Recommended --
rules
comment
Internal comment --
Logical PC_MEAS_CHAN (BSC) B11 Yes B12 Yes
name TRX nb No
HMI PC_MEAS_CHAN Sub-syste BSC Cell Type No
Definition This parameter determines on which channel the MS shall measure the received power level on the downlink for the purpose of the uplink power control.
Coding rules 0 : downlink measurements for power control shall be made on BCCH
1 : downlink measurements for power control shall be made on PDCH
Mandatory rules - Equal to PC_MEAS_CHAN (MFS).
- EN_RED_PDDCB (packet downlink power control) can be enabled only if PC_MEAS_CHAN = 0
- EN_BS_PC_PS (packet downlink power control) can be enabled only if PC_MEAS_CHAN = 0
Recommended --
rules
External --
comment
Internal comment --
Logical PENALTY_TIME(BSC) B11 Yes B12 Yes
name TRX nb No
HMI PENALTY_TIME Sub-syste BSC Cell Type Yes
Definition Time during which MS shall apply TEMPORARY_OFFSET to C2 criterion.
Coding rules step size = 20s. 0: 20s, 1: 40s, ..., 30: 620s, 31: TEMPORARY OFFSET ignored and cell_RESELECT_OFFSET has a negative value
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS. CT: Depends on Cell Type and BTS Type.
The Max value (620 seconds) is coded as 30. Nevertheless the coded value 31 is allowed by the 3GPP TS 05.08 (meaning: TEMPORARY OFFSET ignored and
cell_RESELECT_OFFSET has a negative value). As consequence the range [0,31] (encoded with a step size of 1) shall be used in the CAE template.
Logical PENALTY_TIME(n)(BSC) B11 Yes B12 Yes
name TRX nb No
HMI PENALTY_TIME Sub-syste BSC Cell Type Yes
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS. CT: Depends on Cell Type and BTS Type.
The Max value (620 seconds) is coded as 30. Nevertheless the coded value 31 is allowed by the 3GPP TS 05.08 (meaning: TEMPORARY OFFSET ignored and
cell_RESELECT_OFFSET has a negative value). As consequence the range [0,31] (encoded with a step size of 1) shall be used in the CAE template.
Logical PING_PONG_HCP B11 Yes B12 Yes
name TRX nb No
HMI PING_PONG_HANDICAP Sub-syste BSC Cell Type No
Definition A transient handicap is applied to power budget of previous cell to avoid a ping-pong effect.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PLMN_FREQUENCY_BANDS(BSC) B11 Yes B12 Yes
name TRX nb No
HMI PLMN_FREQUENCY_BANDS Sub-syste BSC Cell Type No
Definition Frequency bands used in the whole PLMN.
Coding rules 0: GSM900 and DCS1800 bands
1: GSM850 and DCS1800 bands
4,...,255: for future use
This parameter shall be coded over 8 bits as a provision for future frequency band combinations.
Mandatory rules PLMN_FREQUENCY_BANDS(BSC) = PLMN_FREQUENCY_BANDS(MFS)
- At cell creation
to
Recommended --
rules
External --
comment
Internal comment The value sent by the OMC-R to the BSC corresponds to the value of the OMC-R changeable parameter, defined in the BSS O&M Telecom catalogue document
Logical POW_INC_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI POW_INC_FACTOR Sub-syste BSC Cell Type No
Definition Weighting factor for power increase.
Mandatory rules --
Recommended POW_INC_FACTOR >= POW_RED_FACTOR

rules
External --
comment
Internal comment --
Logical POW_INC_FACTOR_VAMOS B11 No B12 Yes
name TRX nb No
HMI POW_INC_FACTOR_VAMOS Sub-syste BSC Cell Type No
Definition VAMOS weighting factor for power increase.
Mandatory rules --
Recommended - POW_RED_FACTOR_VAMOS <= POW_INC_FACTOR_VAMOS

rules
Internal comment --
Logical POW_INC_STEP_SIZE B11 Yes B12 Yes
name TRX nb No
HMI POW_INC_STEP_SIZE Sub-syste BSC Cell Type No
Definition Power increase step size in case of power command triggered on quality criterion.
Coding rules step size = 2dB. 1: 2dB, 2: 4dB, ..., 7: 14 dB
Mandatory rules --
Recommended POW_INC_STEP_SIZE > POW_RED_STEP_SIZE

rules
External --
comment
Internal comment --
Logical POW_INC_STEP_SIZE_VAMOS B11 No B12 Yes
name TRX nb No
HMI POW_INC_STEP_SIZE_VAMOS Sub-syste BSC Cell Type No
Definition Power increase step size of a VAMOS sub-channel in case of power command triggered on quality criterion.
Coding rules step size = 2dB.
1: 2dB,
2: 4dB,
...,
7: 14 dB
Mandatory rules --
Recommended - POW_RED_STEP_SIZE_VAMOS < POW_INC_STEP_SIZE_VAMOS

rules
Internal comment --
Logical POW_RED_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI POW_RED_FACTOR Sub-syste BSC Cell Type No
Definition Weighting factor for power reduction.
Mandatory rules --
Recommended POW_RED_FACTOR <= POW_INC_FACTOR

rules
External --
comment
Internal comment --
Logical POW_RED_FACTOR_VAMOS B11 No B12 Yes
name TRX nb No
HMI POW_RED_FACTOR_VAMOS Sub-syste BSC Cell Type No
Definition VAMOS weighting factor for power reduction.
Mandatory rules --
Recommended - POW_RED_FACTOR_VAMOS <= POW_INC_FACTOR_VAMOS

rules
Internal comment --
Logical POW_RED_STEP_SIZE B11 Yes B12 Yes
name TRX nb No
HMI POW_RED_STEP_SIZE Sub-syste BSC Cell Type No
Definition Power reduction step size in case of power command triggered on quality criterion.
Coding rules step size = 2dB. 1: 2dB, 2: 4dB
Mandatory rules --
Recommended POW_RED_STEP_SIZE < POW_INC_STEP_SIZE

rules
External --
comment
Internal comment --
Logical POW_RED_STEP_SIZE_VAMOS B11 No B12 Yes
name TRX nb No
HMI POW_RED_STEP_SIZE_VAMOS Sub-syste BSC Cell Type No
Definition Power reduction step size of a VAMOS sub-channel in case of power command triggered on quality criterion.
Coding rules step size = 2dB.
1: 2dB, 2: 4dB
Mandatory rules --
Recommended - POW_RED_STEP_SIZE_VAMOS < POW_INC_STEP_SIZE_VAMOS

rules
Internal comment --
Logical POWER_OFFSET_IND B11 Yes B12 Yes
name TRX nb No
HMI POWER_OFFSET_IND Sub-syste BSC Cell Type No
Definition This parameter indicates to the MS whether or not POWER_OFFSET parameter is present in System Information.
Coding rules 0: POWER_OFFSET not present, 1: POWER_OFFSET present
Mandatory rules --
Recommended --
rules
External This parameter relates to support of DCS-1800 4W MS.
comment
Internal comment --
Logical PREFERRED_BAND B11 Yes B12 Yes
name TRX nb No
HMI PREFERRED_BAND Sub-syste BSC Cell Type No
Definition Frequency band to which the multiband MS are preferentially directed.
Coding rules 0: none, 1: GSM, 2: DCS
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical PRIO_THR B11 Yes B12 Yes
name TRX nb No
HMI LSA_PRIO_THR Sub-syste BSC Cell Type No
Definition Signal threshold for applying LSA cell reselection.
Coding rules coded from 0 to 7; step size = 6 dB (i.e. 0 = 0 dB, 1 = 6 dB, 2 = 12 dB, 3 = 18 dB, 4 = 24 dB, 5 = 30 dB, 6 = 36 dB, 7 = infinite = 42 dB).
Mandatory rules --
Recommended --
rules
External The default value corresponds to an unused parameter for the MS.
comment The maximum and default values correspond to an infinite threshold.
Internal comment At the OMC, do not display 42dB as maximum value, but infinity.
Logical PRIORITY(0,n) B11 Yes B12 Yes
name TRX nb No
HMI Candidate cell priority Sub-syste BSC Cell Type No
Definition Priority of the cell n in the HO candidate cell evaluation process.
Coding rules 0: highest priority, 5: lowest priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PRIORITY_3G B11 Yes B12 Yes
name TRX nb No
HMI PRIORITY_3G Sub-syste BSC Cell Type No
Definition Priority associated to a given UARFCN explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
0 is the lowest priority, 7 the highest.
Mandatory rules - All 3G cells managed by the OMC (and neighbour to a BSC Evolution) having the same ARFCN_3G shall be given the same PRIORITY_3G value (to be checked on a
per RAT basis).
- The PRIORITY_3G of a given 3G cell, neighbour for reselection to one/several 2G serving cell(s) S, shall be different from any priority (GERAN_PRIORITY) of the
cell(s) S, and different from any priority (DEFAULT_PRIORITY_3G) of the BSS(s) owning the cell(s) S, and different from any priority (PRIORITY_LTE) of the LTE
cell(s) (if any) neighbour for reselection to the cell(s) S.
Recommended --
rules
Internal comment - The mandatory rule has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
Logical PRIORITY_ACCESS_THRESHOLD (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Allowed priority classes Sub-syste BSC Cell Type No
Definition This parameter indicates whether or not a MS of a certain priority class is allowed to do Packet access.
Coding rules Coded over 3 bits . 000: packet access not allowed in the cell; 011:packet access allowed for priority level 1; 100: packet access allowed for priority level 1 to 2; 101:
packet access allowed for priority level 1 to 3; 110: packet access allowed for priority level 1 to 4
Mandatory rules Equal to PRIORITY_ACCESS_THRESHOLD (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical PRIORITY_LTE B11 Yes B12 Yes
name TRX nb No
HMI PRIORITY_LTE Sub-syste BSC Cell Type No
Definition Priority associated to a given EUARFCN explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
0 is the lowest priority, 7 the highest.
Mandatory rules - All LTE cells managed by the OMC having the same ARFCN_LTE shall be given the same PRIORITY_LTE value (to be checked on a per RAT basis).
- The PRIORITY_LTE of a given LTE cell, neighbour for reselection to one/several 2G serving cell(s) S, shall be different from any priority (GERAN_PRIORITY) of the
cell(s) S, and different from any priority (DEFAULT_PRIORITY_3G) of the BSS(s) owning the cell(s) S, and different from any priority (PRIORITY_3G) of the 3G cell(s)
(if any) neighbour for reselection to the cell(s) S.
Recommended --
rules
Internal comment --
Logical PROT_MON B11 Yes B12 Yes
name TRX nb No
HMI PROT_MON Sub-syste BSC Cell Type No
Definition Time in which PROT_TH is to be reached to report an alarm. On timeout, the protocol error counter is reset.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PROT_TH B11 Yes B12 Yes
name TRX nb No
HMI PROT_TH Sub-syste BSC Cell Type No
Definition Protocol error threshold for alarm detection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical PS_PREF_BCCH_TRX B11 Yes B12 Yes
name TRX nb No
HMI PS_PREF_BCCH_TRX Sub-syste BSC Cell Type No
Definition Indicates whether or not the PS requests shall be preferentially served with PDCH(s) of the BCCH TRX
Coding rules 0: No preference. The TRX ranking algorithm handles the BCCH TRX as a non-BCCH TRX.
1: PS requests preferentially served on BCCH TRX. The TRX ranking algorithm ensures that the BCCH TRX has the highest preference to carry PS traffic (provided that
the BCCH TRX can carry PS traffic, i.e. TRX_PREF_MARK = 0 on that TRX).
2 : PS requests served on BCCH TRX with lowest priority. The TRX ranking algorithm ensures that the BCCH TRX has the lowest preference to carry PS traffic
(provided that the BCCH TRX can carry PS traffic, i.e. TRX_PREF_MARK = 0 on that TRX).
Mandatory rules --
Recommended - If EGPRS is activated in a non-hopping or a non-hopping / radio-hopping cell, Alcatel recommend to set this parameter to 0 in order to reduce the likelihood of having
rules to reduce the GMSK output power (see external comment).
- If EGPRS is activated in a base-band hopping cell, setting this parameter to 0 does not reduce the likelihood of having to reduce the GMSK output power since PS
capable TRXs will hop on the BCCH carrier.
- if CCCH_CONF = 6 and the BCCH TRX can carry PS traffic (TRX_PREF_MARK = 0 on that TRX), Alcatel-Lucent recommends to set this parameter to 2.
External When set to 1 or '2', this parameter is only relevant if the BCCH TRX supports PS traffic (i.e. if TRX_PREF_MARK = 0 on the BCCH TRX).
comment If EGPRS is activated in a non-hopping or a non-hopping / radio-hopping cell, if the BCCH TRX can carry PS traffic and if the BCCH TRX is associated to a TRE
hardware allowing the usage of 8-PSK, the operator shall ensure that the difference in the mean output powers between GSMK and 8-PSK signals is less than 2 dB
in order to be compliant with 3GPP TS 45.005 and 3GPP TS 45.008 requirements (or 4 dB if an SDCCH timeslot is defined on timeslot number 7 of the BCCH TRX).
If EGPRS is activated in a base-band hopping cell, the operator shall ensure that the difference in the mean output powers between GMSK and 8-PSK signals is less
than 2 dB in order to be compliant with 3GPP TS 45.005 and 3GPP TS 45.008 requirements (or 4 dB if timeslot number 7 is not part of the PDCH groups).
Internal comment --
Logical PWRC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI PWRC Sub-syste BSC Cell Type No
Definition This flag indicates to the MS if it includes measurements made on BCCH frequency in case of frequency hopping channel.
Coding rules 0: measurements made on BCCH frequency are included, 1: measurements made on BCCH frequency are not included.
Mandatory rules Equal to PWRC (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical Q703_N1 B11 Yes B12 Yes
name TRX nb No
HMI Q703_N1 Sub-syste BSC Cell Type No
Definition Maximum number of MSU available for retransmission.
Coding rules --
Mandatory rules --
Recommended --
rules
External not used if EN_HSL = 1
comment
Internal comment In IP mode, NOT sent to the TC via TCSL
Logical Q703_N1_HSL B11 Yes B12 Yes
name TRX nb No
HMI Q703_N1_HSL Sub-syste BSC Cell Type No
Definition Maximum number of MSU available for retransmission (if HSL is used).
Coding rules step size 1
Mandatory rules --
Recommended --
rules
External used if EN_HSL = 1
comment
Internal comment In IP mode, NOT sent to the TC via TCSL
Logical Q703_N2 B11 Yes B12 Yes
name TRX nb No
HMI Q703_N2 Sub-syste BSC Cell Type No
Definition Maximum number of MSU octets which are available for retransmission.
Category Site (CAE) OMC-R access None (DLS) Type Number Unit bytes
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment In IP mode, sent to the TC via TCSL
Logical Q703_N2_HSL B11 Yes B12 Yes
name TRX nb No
HMI Q703_N2_HSL Sub-syste BSC Cell Type No
Definition Maximum number of MSU octets which are available for retransmission (if HSL is used).
Category Site (CAE) OMC-R access None (DLS) Type Number Unit bytes
Mandatory rules --
Recommended --
rules
comment
Internal comment In IP mode, sent to the TC via TCSL
Logical Q703_T1 B11 Yes B12 Yes
name TRX nb No
HMI Q703_T1 Sub-syste BSC Cell Type No
Definition MTP2 timer alignment ready.
Category Site (CAE) OMC-R access None (DLS) Type Timer Unit 1/10 sec
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment In IP mode, the coded value is sent to the TC via TCSL.
In LSL (Low Speed Link) mode, the step size is 0.1 sec, whereas in HSL (High Speed Link) mode the step size is 1 sec.
Logical Q703_T1_HSL B11 Yes B12 Yes
name TRX nb No
HMI Q703_T1_HSL Sub-syste BSC Cell Type No
Definition MTP2 timer alignment ready for 2Mbit/s (if HSL is used).
Category Site (CAE) OMC-R access None (DLS) Type Timer Unit sec
Mandatory rules --
Recommended --
rules
comment
Internal comment In IP mode, , the coded value is sent to the TC via TCSL.
In LSL (Low Speed Link) mode, the step size is 0.1 sec, whereas in HSL (High Speed Link) mode the step size is 1 sec.
name TRX nb No
Definition MTP2 timer not aligned.
Category Site (CAE) OMC-R access None (DLS) Type Timer Unit 1/10 sec
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment In IP mode, , the coded value is sent to the TC via TCSL
name TRX nb No
Definition MTP2 timer aligned.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - In IP mode, the coded value issent to the TC via TCSL
Logical Q703_T4E B11 Yes B12 Yes
name TRX nb No
HMI Q703_T4E Sub-syste BSC Cell Type No
Definition MTP2 Emergency proving period.
Rec ref. ITU-T Q.703 Domai GSM Min value 0.4 Coded Min 4
Mandatory rules --
Recommended --
rules
External Applicable to LSL and HSL.
comment
Internal comment In IP mode, the coded value is sent to the TC via TCSL
Logical Q703_T4N B11 Yes B12 Yes
name TRX nb No
HMI Q703_T4N Sub-syste BSC Cell Type No
Definition MTP2 Normal proving period.
Mandatory rules --
Recommended --
rules
comment
In LSL (Low Speed Link) mode, the step size is 0.1 sec, whereas in HSL (High Speed Link) mode the step size is 1 sec
Logical Q703_T4N_HSL B11 Yes B12 Yes
name TRX nb No
HMI Q703_T4N_HSL Sub-syste BSC Cell Type No
Definition MTP2 Normal proving period for 2Mbit/s (if HSL is used).
Coding rules step size = 1sec
Mandatory rules --
Recommended --
rules
comment
In LSL (Low Speed Link) mode, the step size is 0.1 sec, whereas in HSL (High Speed Link) mode the step size is 1 sec
name TRX nb No
Definition MTP2 timer sending SIB.
Category Site (CAE) OMC-R access None (DLS) Type Timer Unit ms
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - In IP mode, the coded value is sent to the TC via TCSL
name TRX nb No
Definition MTP2 timer remote congestion.
Mandatory rules Q707_T1 >= Q703_T6
Recommended --
rules
External --
comment
Internal comment In IP mode, the coded value is sent to the TC via TCSL
name TRX nb No
Definition MTP2 timer excessive delay of acknowledgement.
Mandatory rules --
Recommended --
rules
External In case of a Ater satellite connection, this parameter is set to 2 seconds by the BSC.
comment
Internal comment - In IP mode, the coded value is sent to the TC via TCSL
name TRX nb No
Definition MTP3 timer supervising the reception of changeover acknowledgement.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition MTP3 timer supervising the reception of changeback acknowledgement (first attempt).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition MTP3 timer supervising the reception of changeback acknowledgement (second attempt).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition MTP3 timer supervising the reception of signalling link test acknowledgement.
Mandatory rules Q707_T1 >= Q703_T6
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition MTP3 delay between transmission of consecutive signalling link test message.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical QRXLEVMIN_3G B11 Yes B12 Yes
name TRX nb No
HMI QRXLEVMIN_3G Sub-syste BSC Cell Type No
Definition Minimum received level required for a given UARFCN broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Mandatory rules All 3G cells managed by the OMC (and neighbour to a BSC Evolution) having the same ARFCN_3G shall be given the same QRXLEVMIN_3G value (to be checked on a
per RAT basis).
Recommended --
rules
Internal comment - The mandatory rule has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
Logical QRXLEVMIN_LTE B11 Yes B12 Yes
name TRX nb No
HMI QRXLEVMIN_LTE Sub-syste BSC Cell Type No
Definition Minimum received level required for a given EUARFCN broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Mandatory rules All LTE cells managed by the OMC having the same ARFCN_LTE shall be given the same QRXLEVMIN_LTE value (to be checked on a per RAT basis).
Recommended --
rules
Internal comment --
Logical Qsearch_C B11 Yes B12 Yes
name TRX nb No
HMI Qsearch_C Sub-syste BSC Cell Type No
Definition Threshold for searching for 3G cells in dedicated mode depending whether the received signal level of the serving cell is below or above the threshold.
Coding rules Coded value (binary): Value (dBm): Text displayed at the OMC
0: -98: -98 dBm (below)
1: -94: -94 dBm (below)
2: -90: -90dBm (below)
3: -86: -86dBm (below)
4: -82: -82 dBm (below)
5: -78: -78 dBm (below)
6: -74: -74 dBm (below)
7: -70: Always search for 3G neighbour cells
8: -78: -78 dBm (above)
9: -74: -74 dBm (above)
10: -70: -70 dBm (above)
11: -66: -66 dBm (above)
12: -62: -62 dBm (above)
13: -58: -58 dBm (above)
14: -54: -54 dBm (above)
15: -50: Never search for 3G neighbour cells
Mandatory rules --
Recommended In a cell where at least one 2G to 3G adjacency has been defined, Qsearch_C =-70, i.e. always search for 3G neighbour cells
rules
External This threshold is used to search for 3G cells if the received signal level is below (-98 dBm to always search for 3G neighbour cells) or above (-78 dBm to never
comment search for neighbour cells) the threshold.
This parameter is broadcast on SACCH
Internal comment The OMC shall not display on the OMC screen the value of 70 (resp. 50), but the corresponding text always search for 3G neighbour cells (resp. never search
for 3G
neighbour cells).
m
template
Logical Qsearch_C_LTE_INITIAL B11 Yes B12 Yes
name TRX nb No
HMI Qsearch_C_LTE_INITIAL Sub-syste BSC Cell Type No
Definition Indicates the Qsearch value to be used in dedicated / dual transfer mode before Qsearch_C_LTE is received. Used for CS handover by a LTE-capable MS/UE.
0: -98: -98 dBm (below)
1: -94: -94 dBm (below)
2: -90: -90dBm (below)
3: -86: -86dBm (below)
4: -82: -82 dBm (below)
5: -78: -78 dBm (below)
6: -74: -74 dBm (below)
7: -70: Always search for LTE neighbour cells
8: -78: -78 dBm (above)
9: -74: -74 dBm (above)
10: -70: -70 dBm (above)
11: -66: -66 dBm (above)
12: -62: -62 dBm (above)
13: -58: -58 dBm (above)
14: -54: -54 dBm (above)
15: -50: Never search for LTE neighbour cells
Mandatory rules --
Recommended --
rules
comment - This threshold is used to search for LTE cells if the received signal level is below (-98 dBm to always search for LTE neighbour cells) or above (-78 dBm to never
search for LTE neighbour cells) the threshold.
Internal comment - This parameter is not used by BSS SW. It is defined as a provision for the MIB (following B11 RFD 234264).
Logical Qsearch_I B11 Yes B12 Yes
name TRX nb No
HMI Qsearch_I Sub-syste BSC Cell Type No
Definition Threshold for searching for 3G cells depending whether the received level average of the
serving cell is below or above the threshold.
0: -98: -98 dBm (below)
1: -94: -94 dBm (below)
2: -90: -90dBm (below)
3: -86: -86dBm (below)
4: -82: -82 dBm (below)
5: -78: -78 dBm (below)
6: -74: -74 dBm (below)
8: -78: -78 dBm (above)
9: -74: -74 dBm (above)
10: -70: -70 dBm (above)
11: -66: -66 dBm (above)
12: -62: -62 dBm (above)
13: -58: -58 dBm (above)
14: -54: -54 dBm (above)
Mandatory rules --
Recommended In a cell with FDD_ARFCN_list not empty, Qsearch_I =-70, i.e. always search for 3G neighbour cells
rules
comment search for neighbour cells) the threshold.
This parameter is broadcast on BCCH
Internal comment --
Logical Qsearch_P B11 Yes B12 Yes
name TRX nb No
HMI Qsearch_P Sub-syste BSC Cell Type No
Definition Threshold for searching for 3G cells in GPRS depending whether the received level average of the serving cell is below or above the threshold
0: -98: -98 dBm (below)
1: -94: -94 dBm (below)
2: -90: -90dBm (below)
3: -86: -86dBm (below)
4: -82: -82 dBm (below)
5: -78: -78 dBm (below)
6: -74: -74 dBm (below)
8: -78: -78 dBm (above)
9: -74: -74 dBm (above)
10: -70: -70 dBm (above)
11: -66: -66 dBm (above)
12: -62: -62 dBm (above)
13: -58: -58 dBm (above)
14: -54: -54 dBm (above)
Mandatory rules --
Recommended In a cell with FDD_ARFCN_list not empty, Qsearch_P =-70, i.e. always search for 3G neighbour cells
rules
comment search for neighbour cells) the threshold in GPRS.
This parameter is broadcast on BCCH and on PBCCH if there is a PBCCH allocated in the serving cell.
for 3G neighbour cells).
Logical Qsearch_P_LTE B11 Yes B12 Yes
name TRX nb No
HMI Qsearch_P_LTE Sub-syste BSC Cell Type No
Definition Threshold for searching for LTE cells in GPRS depending whether the received level average of the serving cell is below or above the threshold.
Used for cell reselection by a LTE-capable MS/UE.
0: -98: -98 dBm (below)
1: -94: -94 dBm (below)
2: -90: -90dBm (below)
3: -86: -86dBm (below)
4: -82: -82 dBm (below)
5: -78: -78 dBm (below)
6: -74: -74 dBm (below)
7: -70: Always search for LTE neighbour cells
8: -78: -78 dBm (above)
9: -74: -74 dBm (above)
10: -70: -70 dBm (above)
11: -66: -66 dBm (above)
12: -62: -62 dBm (above)
13: -58: -58 dBm (above)
14: -54: -54 dBm (above)
15: -50: Never search for LTE neighbour cells
Mandatory rules --
Recommended --
rules
Internal comment --
Logical QUEUE_ANYWAY m B11 Yes B12 Yes

name TRX nb No
HMI Forced_Queuing Sub-syste BSC template Cell Type No
Definition This flag enables/disables forced queuing for Assignment requests when queuing is not allowed by the MSC.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment If Queue_Anyway = disabled and the queuing is not allowed by the MSC neither, calls with pre-emption capability might be queued nevertheless if EN_TCH_PREEMPT
= enabled.
Logical RA_CODE (BSC) B11 Yes B12 Yes
name TRX nb No
HMI Routing Area Code for GPRS Sub-syste BSC Cell Type No
Definition Routing Area Code for GPRS.
Rec ref. 3GPP TS 04.18 Domai GPRS Min value -1 Coded Min 0
Coding rules The initial special value -1 means that the RA code has still not been set by the operator.
Mandatory rules - Equal to RA_CODE (MFS)

- A couple of mate extended cells (Extended inner + extended outer) shall have the same RA_CODE when they are PS capable
Recommended --
rules
comment
Internal comment Note that, for a cell which does not support GPRS, the OMC may initially set the value -1.
-1" value of RA_CODE or RA_COLOUR is never downloaded to the BSC. It is filtered by OMC-R since "-1" is out of the parameters range (see BSS MIB).
Logical RA_COLOUR B11 Yes B12 Yes
name TRX nb No
HMI Routing Area Colour for GPRS Sub-syste BSC Cell Type No
Definition Routing Area Colour for GPRS.
Coding rules Coded over 3 bits. the initial special value -1 means that the RA codecolour has not yet been valued by the network provider.
Mandatory rules --
Recommended --
rules
External Default value depends on the configuration. The value indicated here is for implementation purposes.
comment
Internal comment - Transported in 04.18 SYSTEM INFORMATION TYPE 3/4 messages.
- Note that, for a cell which does not support GPRS, the OMC may initially set the value -1.
- "-1" value of RA_CODE or RA_COLOUR is never downloaded to the BSC. It is filtered
Logical RACH_BUSY_THRES B11 Yes B12 Yes
name TRX nb No
HMI RACH_BUSY_THRES Sub-syste BSC Cell Type No
Definition Received level above which a RACH TS is deemed busy.
Category Site (CAE) OMC-R access Displayed Type Threshold Unit dBm
Coding rules This parameter is encoded with a step size of 4 dB as follows:
1: -110 dBm
5: -106 dBm
9: -102 dBm
13: -98 dBm
17: -94 dBm
21: -90 dBm
25: -86 dBm
29: -82 dBm
33: -78 dBm
37: -74 dBm
41: -70 dBm
45: -66 dBm
49: -62 dBm
53: -58 dBm
57: -54 dBm
61: -50 dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical RACH_LOAD_MEAS_PER B11 Yes B12 Yes
name TRX nb No
HMI CCCH_LOAD_MEAS_PERIOD Sub-syste BSC Cell Type No
Definition Period over which CCCH load measurements are made.
Category Site (CAE) OMC-R access Displayed Type Timer Unit 51mfr
Coding rules step size=1
Mandatory rules --
Recommended RACH_LOAD_MEAS_PER < RACHRT

rules
External --
comment
Logical RACH_TA_FILTER (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RACH/PRACH_TA_FILTER Sub-syste BSC Cell Type No
Definition Timing Advance threshold for CHANNEL REQUIRED and PACKET CHANNEL REQUEST filtering.
Coding rules 64: no filtering
Mandatory rules Equal to RACH_TA_FILTER (MFS).
Recommended Disable the filtering for extended cells.

rules
External One unit corresponds to a distance of about 550m. CHANNEL REQUIRED or PACKET CHANNEL REQUEST messages with Timing Advance greater or equal to
comment RACH_TA_FILTER are discarded.
Internal comment --
Logical RACHRT B11 Yes B12 Yes
name TRX nb No
HMI CCCH_LOAD_IND_PERIOD Sub-syste BSC Cell Type No
Definition Minimum delay between two consecutive sendings of CCCH LOAD INDICATION messages.
Category Site (CAE) OMC-R access Displayed Type Timer Unit 51mfr
Coding rules step size=1 (51mfr)
Mandatory rules --
Recommended RACHRT > RACH_LOAD_MEAS_PER

rules
External --
comment
Logical RADIOLINK_REP_DL_SACCH B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_REP_DL_SACCH Sub-syste BSC Cell Type No
Definition Repeated DL SACCH activation threshold for UL RLT (Radio Link Timer) counter.
Dynamic activation is triggered in the BTS when the UL RLT counter is inferior or equal to that threshold.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - The setting of this value is a trade-off between "triggering REP_DL_SACCH soon enough to take benefit from it before drop" and "triggering REP_DL_SACCH not too
soon to let time to the recovery mechanism to increase the output power of the BTS to its max level before".
Internal comment - CDM parameter (sent by BSC to BTS on the OML)
- The default value equals to RADIOLINK_RECOVERY_THRES (= N_BSTXPWR_M) - 3) to let time to the BSS to set the power output of the BTS and MS to its maximum
value (recovery mechanism). It is applicable to all cell types, even in micro cells.
Logical RADIOLINK_TIMEOUT (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_TIMEOUT Sub-syste BSC Cell Type No
Definition Initial value of MS counter for radio link supervision.
This applies to non AMR calls or to AMR (NB or WB) calls for which Repeated SACCH and Repeated DL FACCH are activated.
Coding rules step size = 4 Samfr, coded from 0 to 15 (0 == 4 Samfr, 1 == 8 Samfr ... 15 == 64 Samfr
Mandatory rules Equal to RADIOLINK_TIMEOUT (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical RADIOLINK_TIMEOUT_AMR B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_TIMEOUT_AMR Sub-syste BSC Cell Type No
Definition Initial value of MS counter for radio link supervision, for a call using an AMR codec (NB or WB) and for which Repeated SACCH and/or Repeated DL FACCH are not
activated.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RADIOLINK_TIMEOUT_BS B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_FAILURE_THRES Sub-syste BSC Cell Type No
Definition Counter threshold to detect a radio link failure on the uplink path, for non AMR calls, or for AMR calls (NB or WB) for which Repeated SACCH and Repeated DL FACCH
are activated.
Coding rules --
Mandatory rules RADIOLINK_TIMEOUT_BS > N_BSTXPWR_M
Recommended Values higher than 128 are not recommended by Alcatel-Lucent (very far to the 3GPP values):
rules It will significantly increase the delay for retransmission of a message. For instance, if a HANDOVER COMMAND is sent to a given MS, but not received, the MS will
have to wait longer to get the repeated HO CMD, which may lead to call drop in the meantime.
Moreover, it can increase congestion in the BSS, as the call duration is artificially increased.
External --
comment
Logical RADIOLINK_TIMEOUT_BS_AMR B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_FAILURE_THRES_AMR Sub-syste BSC Cell Type No
Definition Counter threshold to detect a radio link failure on the uplink path for calls using an AMR codec (NB or WB) and for which Repeated SACCH and/or Repeated DL FACCH
are not activated.
Coding rules --
Mandatory rules RADIOLINK_TIMEOUT_BS_AMR > N_BSTXPWR_M
Recommended Values higher than 128 are not recommended by Alcatel-Lucent (very far to the 3GPP values):
External --
comment
Logical RANGEi_HIGHER (1<=i<=13) B11 Yes B12 Yes
name TRX nb No
HMI Highest BA range ARFCNs Sub-syste BSC Cell Type No
Definition Highest ARFCN of range i indicated in BA Range Information Element.
Rec ref. 3GPP TS 04.08 Domai GSM Min value -1 Coded Min -1
Def value -1 Coded Def -1
Coding rules --
Mandatory rules RANGEi_HIGHER >= RANGEi_LOWER
Recommended --
rules
External RANGEi_HIGHER = -1 means that it shall not be included in BA Range IE.
comment Moreover, all BA RANGE following this one will be considered as not significant by the OMC and not send to the BSC. (i.e. -1 = indicator of end of BA Range)
Internal comment --
Logical RANGEi_LOWER (1<=i<=13) B11 Yes B12 Yes
name TRX nb No
HMI Lowest BA range ARFCNs Sub-syste BSC Cell Type No
Definition Lowest ARFCN of range i indicated in BA Range Information Element.
Rec ref. 3GPP TS 04.08 Domai GSM Min value -1 Coded Min -1
Coding rules Coded on 16 bits.
Mandatory rules RANGEi_HIGHER >= RANGEi_LOWER
Recommended --
rules
External RANGEi_LOWER = -1 means that it shall not be included in BA Range IE
comment Moreover, all BA RANGE following this one will be considered as not significant by the OMC and not send to the BSC. (i.e. -1 = indicator of end of BA Range)
Internal comment --
Logical RAT_3G B11 Yes B12 Yes
name TRX nb No
HMI RAT_3G Sub-syste BSC Cell Type No
Definition This parameter defines UMTS radio access technology of an external 3G cell.
Category Site (CAE) OMC-R access Set by Create Type Enumerated Unit None
Coding rules 0: FDD
1: TDD
Mandatory rules A 3G TDD cell can be configured for (blind) cell reselection only.
Recommended --
rules
External --
comment
Internal comment - A coded default value is not needed since the operator cannot create a 3G cell without configuring its radio access technology (no dummy value needed).
- From a given 2G serving cell, a neighbour 3G FDD cell could be target, either for handover or for (blind) cell reselection or for both.
- From a given 2G serving cell, a neighbour 3G TDD cell could be target for (blind) cell reselection only.
Logical RAT_LTE B11 Yes B12 Yes
name TRX nb No
HMI RAT_LTE Sub-syste BSC Cell Type No
Definition This parameter defines the radio access technology of an external LTE cell.
Category Site (CAE) OMC-R access Set by Create Type Enumerated Unit None
Coding rules 0: FDD
1: TDD
Mandatory rules --
Recommended --
rules
External Parameter available on BSC Evolution only.
comment
Internal comment --
Logical RE B11 Yes B12 Yes
name TRX nb No
HMI CALL_RE_ESTABLISHMENT Sub-syste BSC Cell Type No
Definition This flag indicates to the MS if call reestablishment is allowed in the cell.
Coding rules 0: allowed, 1: not allowed
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical REP_DL_FACCH_LEGACY_SUPPORT B11 Yes B12 Yes
name TRX nb No
HMI REP_DL_FACCH_LEGACY_SUPPORT Sub-syste BSC Cell Type No
Definition Legacy support for repeated downlink FACCH for AMR-NB or AMR-WB GMSK calls.
This parameter concerns only the LAPDm command frames.
Coding rules 0: repeated DL FACCH enabled only for the AMR mobile stations having indicated the support of the feature by repeated ACCH Capability bit = 1
1: repeated DL FACCH enabled for all AMR mobile stations
Mandatory rules --
Recommended --
rules
External - This parameter is relevant only if repeated downlink FACCH (EN_REP_DL_FACCH) is enabled.
comment - Function available on BSC Evolution only.
- The value 1 is used to tackle early implementations, ie for MS with repeated ACCH Capability bit=0 or MS without Repeated ACCH Capability bit (legacy MS).
Logical REP_DL_FACCH_THRES_AMR_FR B11 Yes B12 Yes
name TRX nb No
HMI REP_DL_FACCH_THRES_AMR_FR Sub-syste BSC Cell Type No
Definition Repeated DL FACCH activation threshold for AMR-NB FR calls.
Dynamic activation is done as long as the codec mode request (CMR value) is inferior or equal to that threshold.
Coding rules 0: off
1: 4,75 kbit/s
2: 5,15 kbit/s
3: 5,90 kbit/s
4: 6,70 kbit/s
5: 7,40 kbit/s
6: 7,95 kbit/s
7: 10,2 kbit/s
8: 12,2 kbit/s
Mandatory rules --
Recommended --
rules
comment - When setting the threshold to the max value, the repeated DL FACCH is always activated for AMR-NB FR codec (if allowed for the call).
-Parameter change : no impact on the telecom service. Change applied on new calls (after modification).
Internal comment CDM parameter (sent by BSC to BTS on the OML)
Logical REP_DL_FACCH_THRES_AMR_HR B11 Yes B12 Yes
name TRX nb No
HMI REP_DL_FACCH_THRES_AMR_HR Sub-syste BSC Cell Type No
Definition Repeated DL FACCH activation threshold for AMR-NB HR calls.
Coding rules 0: off
1: 4,75 kbit/s
2: 5,15 kbit/s
3: 5,90 kbit/s
4: 6,70 kbit/s
5: 7,40 kbit/s
Mandatory rules --
Recommended --
rules
comment - When setting the threshold to the max value, the repeated DL FACCH is always activated for AMR-NB HR codec (if allowed for the call).
Logical REP_DL_FACCH_THRES_AMR_WB B11 Yes B12 Yes
name TRX nb No
HMI REP_DL_FACCH_THRES_AMR_WB Sub-syste BSC Cell Type No
Definition Repeated DL FACCH activation threshold for AMR-WB GMSK calls.
Coding rules 0: off
1: 6,60 kbit/s
2: 8,85 kbit/s
3: 12,65 kbit/s
Mandatory rules --
Recommended --
rules
comment - When setting the threshold to the max value, the repeated DL FACCH is always activated for AMR-WB GMSK codec (if allowed for the call).
Logical REP_DL_SACCH_THRES B11 Yes B12 Yes
name TRX nb No
HMI REP_DL_SACCH_THRES Sub-syste BSC Cell Type No
Definition Repeated DL SACCH threshold.
RDSACCH is activated if at least REP_DL_SACCH_THRES SRR bits set to 1 have been received (after possible combining) in a window whose size is equal to
REP_DL_SACCH_WS successive UL SACCH periods.
Inversely RDSACCH is deactivated if less than REP_DL_SACCH_THRES SRR bits set to 1 have been received in the window.
Category System (CST) OMC-R access None (DLS) Type Threshold Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
comment - The REP_DL_SACCH_THRES and WS defaults values trigger RDSACCH as soon as the legacy SER becomes superior or equal to 30%. These values allow having a
relatively fast reaction mechanism without triggering spurious RDSACCH (this is all the more true that the SRR bit can be repeated if RUSACCH is also used at this
moment).
Logical REP_DL_SACCH_WS B11 Yes B12 Yes
name TRX nb No
HMI REP_DL_SACCH_WS Sub-syste BSC Cell Type No
Definition Repeated DL SACCH window size.
RDSACCH is activated if at least REP_DL_SACCH_THRES SRR bits set to 1 have been received (after possible combining) in a window whose size is equal to
REP_DL_SACCH_WS successive UL SACCH periods.
Inversely RDSACCH is deactivated if less than REP_DL_SACCH_THRES SRR bits set to 1 have been received in the window.
Category System (CST) OMC-R access None (DLS) Type Number Unit Samfr
Coding rules --
Mandatory rules --
Recommended --
rules
comment - The REP_DL_SACCH_THRES and WS defaults values trigger RDSACCH as soon as the legacy SER becomes superior or equal to 30%. These values allow having a
relatively fast reaction mechanism without triggering spurious RDSACCH (this is all the more true that the SRR bit can be repeated if RUSACCH is also used at this
moment).
Logical REP_UL_SACCH_THRES B11 Yes B12 Yes
name TRX nb No
HMI REP_UL_SACCH_THRES Sub-syste BSC Cell Type No
Definition Repeated UL SACCH threshold.
RUSACCH is activated if at least REP_UL_SACCH_THRES UL SACCH messages have been correctly received before combining in a window whose size is equal to
REP_UL_SACCH_WS successive UL SACCH periods.
Inversely RUSACCH is deactivated if less than REP_UL_SACCH_THRES UL legacy SACCH messages have not been correctly received before combining in the window.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - The REP_UL_SACCH_THRES and WS defaults values trigger RUSACCH as soon as the legacy SER becomes superior or equal to 30%.
Logical REP_UL_SACCH_WS B11 Yes B12 Yes
name TRX nb No
HMI REP_UL_SACCH_WS Sub-syste BSC Cell Type No
Definition Repeated UL SACCH window size.
RUSACCH is activated if at least REP_UL_SACCH_THRES UL SACCH messages have been correctly received before combining in a window whose size is equal to
REP_UL_SACCH_WS successive UL SACCH periods.
Inversely RUSACCH is deactivated if less than REP_UL_SACCH_THRES UL legacy SACCH messages have not been correctly received before combining in the window.
Category System (CST) OMC-R access None (DLS) Type Number Unit Samfr
Coding rules --
Mandatory rules --
Recommended --
rules
comment - The REP_UL_SACCH_THRES and WS defaults values trigger RUSACCH as soon as the legacy SER becomes superior or equal to 30%.
Logical RESET_INDEFINITE B11 Yes B12 Yes
name TRX nb No
HMI RESET_INDEFINITE Sub-syste BSC Cell Type No
Definition This flag determines whether or not the RESET message shall be sent indefinitely (as long as it is not acknowledged).
Coding rules 0: RESET message is sent a maximum of NBR_RESET_REP times, 1: The Reset procedure is repeated until a RESET or RESET ACK message is received.
Mandatory rules --
Recommended --
rules
comment
Internal comment Used only when NBR_RESET_REP <> 0.
Logical RESP_REQ B11 Yes B12 Yes
name TRX nb No
HMI RESP_REQ Sub-syste BSC Cell Type No
Definition This flag controls Response request OIE inclusion in HANDOVER REQUIRED.
Coding rules 0: IE not included, 1: IE included
Mandatory rules --
Recommended When the VGCS feature (EN_VGCS) is activated, it is recommended to include the Response Request in the HANDOVER REQUIRED message (RESP_REQ).
rules
comment For external directed retries, the serving BSC does not know whether or not the external target cells (towards which the directed retry is triggered) are congested.
Therefore, Alcatel recommend to set RESP_REQ to 1 if EN_EXT_DR is set to enabled in order to get a Handover Reject message from the MSC in case all target cells
are congested and thus to attempt other procedures.
Internal comment --
Logical RMS_BCCH_BSIC_NB B11 Yes B12 Yes
name TRX nb No
HMI RMS_BCCH_BSIC_NB Sub-syste BSC Cell Type No
Definition Maximum number of measured neighbour frequencies, reported by the BTS to the BSC in the Radio Measurements. The actual number, reported by a TRE, depends on its
generation. One frequency, identified by one (BCCH frequency/BSIC) couple, is reported into one CI vector.
Coding rules --
Mandatory rules --
Recommended Configuring a multiple of 14 as value allows optimizing the block usage in the RMS measurements returned to OMC in the performance counters.
rules
comment - Significant only if EN_MORE_RMS_BCCH_BSIC is enabled.
- A G3 TRE supports up to 84 (BCCH frequency/BSIC) couples; others up to 154 couples.
Internal comment This parameter (or 42, in case EN_MORE_RMS_BCCH_BSIC is disabled) is sent to the BTS via RSL
Logical RMS_TEMPLATE_INDEX B11 Yes B12 Yes
name TRX nb No
HMI RMS_TEMPLATE Sub-syste
BSC Cell Type No
name Instance
cell RMS No
Definition Template of values of RMS parameters to be applied to the concerned cell (concerns the parameters MEAS_STAT_C_Ix, MEAS_STAT_BFIx, MEAS_STAT_LEVx,
MEAS_STAT_PATH_BALx, MEAS_STAT_Sx, EN_BALANCED_CI, VQ_AVERAGE, VQ_BAD_RXFER, VQ_FER_THRESHOLD, VQ_GOOD_RXFER,
VQ_INTF_THRESHOLD,
VQ_RXLEV, VQ_RXQUAL, VQ_RXQUAL_VS_RXFER).
Coding rules coded from 1 to 16
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The parameter is a CELL attribute, it is the reference to one of the 16 RMS templates at the beginning of the definition field.
Logical RNC_ID_3G B11 Yes B12 Yes
name TRX nb No
HMI RNC_ID Sub-syste BSC Cell Type No
Definition This parameter indicates the RNC Identifier or the Extended RNC Identifier of an external 3G (FDD or TDD) cell, as defined in 3GPP TS 25.401 (in HO Required message
sent to the MSC on A interface).
Coding rules Binary value on 16 bits.
Mandatory rules (MCC_3G, MNC_3G, RNC_ID_3G and CI_3G) shall together uniquely identify a 3G cel.
Recommended --
rules
comment
Internal comment - A coded default value is not needed since the operator cannot create a 3G cell without configuring its RNCId (no dummy value needed).
Logical RNC_MIN_NB_ACTIVE_IPSP B11 Yes B12 Yes
name TRX nb No
HMI RNC_MIN_NB_ACTIVE_IPSP Sub-syste BSC Cell Type No
Definition The minimum number of active IP server processes (IPSP) in the RNC server required to handle the signalling traffic with that RNC.
Coding rules --
Mandatory rules When the RNC_TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the IURG_SCTP_ENDPOINT_LIST must be equal or greater than
RNC_MIN_NB_ACTIVE_
Recommended --
rules
External - This parameter is significant when the RNC_TRAFFIC_MODE of the RNC is load sharing mode.
comment - Parameter change: before any modification, the operator must lock all the Iur-g Signalling Links of the modified RNC.
Internal comment --
Logical RNC_SPC B11 Yes B12 Yes
name TRX nb No
HMI RNC_SPC Sub-syste BSC Cell Type No
Definition Signalling Point Code of a given RNC, connected to the BSC.
Mandatory rules All the RNCs connected to one BSC must have different RNC_SPC.
Recommended --
rules
External - Significant only if EN_IURG is set to TRUE
comment - "Iur-g+ interface" is available on BSC Evolution only.
- Parameter change: before any modification, the operator must lock all the Iur-g Signalling Links of the modified RNC.
Internal comment - A coded default value is not needed since the operator cannot create a RNC without configuring its signaling point code (no dummy value needed).
Logical RNC_TRAFFIC_MODE B11 Yes B12 Yes
name TRX nb No
HMI RNC_TRAFFIC_MODE Sub-syste BSC Cell Type No
Definition Traffic mode of the M3UA signalling link set with the RNC.
Rec ref. RFC 4666 Domai IP Min value 0 Coded Min 0
Coding rules 0: load sharing mode (ie the traffic is distributed over all the active IPSPs)
1 :override mode (ie only one of the IPSPs handle the traffic)
2: broadcast mode (ie all the active IPSPs receive the same messages)
Mandatory rules - The value "broadcast mode" is not allowed.
- When the RNC_TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the IURG_SCTP_ENDPOINT_LIST must be equal or greater than
RNC_MIN_NB_ACTIVE_IPSP
Recommended --
rules
comment - The broadcast mode is not supported by the BSS on the Iur-g interface.
- Parameter change: before any modification, the operator must lock all the Iur-g Signalling Links of the modified RNC.
Internal comment --
Logical ROT B11 Yes B12 Yes
name TRX nb No
HMI ROT Sub-syste BSC Cell Type No
Definition Indicates to the MS whether or not it shall include Time Difference IE in HANDOVER COMPLETE.
Coding rules 0: "Mobile Time Difference" IE is NOT included in HANDOVER COMPLETE,
1: "Mobile Time Difference" IE is included in HANDOVER COMPLETE
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RR_ACK_TIMER (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI RR_ACK_TIMER (MX BSC) Sub-syste BSC Cell Type No
Definition Maximum delay for sending a RR acknowledgement frame on RSL and GSL
Category System (CST) OMC-R access None (DLS) Type Timer Unit ms
Coding rules step size = 100ms
Mandatory rules The value of this parameter shall be lower than T200 (BSC)
Recommended --
rules
External This parameter is used only with Mx BSC for both terrestrial and satellite links.
comment
Internal comment --
Logical RR_ALLOC_PERIOD (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RR_ALLOC_PERIOD (BSC) Sub-syste BSC Cell Type No
Definition This parameter allows to tune the time between two sendings of the BSCGP RR Allocation Indication messages.
Coding rules --
Mandatory rules Equal to RR_ALLOC_PERIOD (MFS)
Recommended --
rules
External --
comment
Internal comment The time between two sendings of the RR Allocation Indication messages is TCH_INFO_PERIOD * RR_ALLOC_PERIOD seconds.
Logical RSL_I_PRIORITY (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RSL_I_PRIORITY (BSC) Sub-syste BSC Cell Type No
Definition BSS internal priority used by the BSC for the RSL-I flow in IP network
3: lower priority
Mandatory rules shall be equal to RSL_I_PRIORITY(BTS)
Recommended --
rules
External --
comment
Internal comment --
Logical RSL_RATE (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RSL_RATE (BSC) Sub-syste BSC Cell Type No
Definition Rate used on all RSL links towards a BTS.
Coding rules 0: 16 kbit/s, 1: 64 kbit/s
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Deduced from O&M parameter: BSI-Link-Type
Logical RSL_UDP_PORT_BSC B11 Yes B12 Yes
name TRX nb No
HMI RSL_UDP_PORT_BSC Sub-syste BSC Cell Type No
Definition UDP port number used for RSL on BSC side.
Mandatory rules --
Recommended --
rules
External --
comment
- Min = hCF00, Max = hCFFF
Logical RSL_UI_PRIORITY (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RSL_UI_PRIORITY (BSC) Sub-syste BSC Cell Type No
Definition BSS internal priority used by the RSL-UI flow in IP network
3: lower priority
Mandatory rules - shall be equal to RSL_UI_PRIORITY (BTS)
Recommended --
rules
External --
comment
Internal comment --
Logical RTCP_N_NEGO B11 No B12 Yes
name TRX nb No
HMI RTCP_N_NEGO Sub-syste BSC Cell Type No
Definition Number of times an APP RTCP packet is sent to the MGW before ending the RTP muliplexing negotiation.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RTCP_PERIOD B11 No B12 Yes
name TRX nb No
HMI RTCP_PERIOD Sub-syste BSC Cell Type No
Definition Period of sending APP RTCP packets to the MGW during the RTP mulitplexing negotiation.
Category System (CST) OMC-R access None (DLS) Type Timer Unit sec
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RTP_IP_ADDRESS_BSC B11 No B12 Yes
name TRX nb No
HMI RTP_IP_ADDRESS_BSC Sub-syste BSC Cell Type No
Definition IP address of the TPIP/RTP function in the BSC.
Mandatory rules --
Recommended --
rules
External - Parameter change: This parameter is changed via the START_AUP_IP_ADDRESS_BSC change by the operator from the BSC terminal.
Internal comment - function is hosted by the active TPGSM
- computed by the BSC = START_AUP_IP_ADDRESS_BSC + 2
Logical RTP_UDP_PORT_MASK B11 No B12 Yes
name TRX nb No
HMI RTP_UDP_PORT_MASK Sub-syste BSC Cell Type No
Definition Mask defining the number of UDP ports allocated in the BSC, for A user plane over IP.
The present port mask and the associated port base (RTP_UDP_PORT_START) define the UDP ports range, used for the RTP/RTCP protocol.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - This parameter is computed by the BSC.
Internal comment - default = C000x
- the defined default range size is 3FFFx= 16384 values = 8192 couples of (RTP, RTCP) port numbers. RTP port is even, RTCP port is odd.
-The range size is higher than the maximum number of calls (depending on BSC configuration) x 2 (one for RTP, another one for RTCP).
Logical RTP_UDP_PORT_START B11 No B12 Yes
name TRX nb No
HMI RTP_UDP_PORT_START Sub-syste BSC Cell Type No
Definition Base of the UDP ports allocated in the BSC, for A user plane over IP.
The present port base and the associated port mask (RTP_UDP_PORT_MASK) define the UDP ports range, used for the RTP/RTCP protocol.
Coding rules RTP ports are the even ports, and RTCP ports are the odd ports
Mandatory rules --
Recommended --
rules
Internal comment - default = 8000x
Logical RXLEV_ACCESS_MIN (BSC) B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_ACCESS_MIN Sub-syste BSC Cell Type No
Definition Minimum received level at the MS required for initial access to the cell.
Coding rules Coded on 6 bits, 0=-110 dBm, 63=-47 dBm, step size=1dBm.
Mandatory rules RXLEV_ACCESS_MIN (MFS) = RXLEV_ACCESS_MIN (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical RXLEV_ACCESS_MIN(n)(BSC) B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_ACCESS_MIN Sub-syste BSC Cell Type No
Rec ref. None Domai VGCS Min value -110 Coded Min 0
Mandatory rules RXLEV_ACCESS_MIN(n)(MFS) = RXLEV_ACCESS_MIN(n)(BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical RXLEV_DL_IH B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_DL_IH Sub-syste BSC Cell Type Yes
Definition Downlink level threshold for decision between intracell and intercell handover in case of bad downlink quality.
Coding rules Coded over 6 bits: 0: -110 dBm, 1: -109 dBm...63: -47 dBm.
Mandatory rules RXLEV_DL_IH > L_RXLEV_DL_H
Recommended --
rules
External --
comment
Internal comment --
Logical RXLEV_DL_MAX_VAMOS_UNPAIRING B11 No B12 Yes
name TRX nb No
HMI RXLEV_DL_MAX_VAMOS_UNPAIRING Sub-systeBSC Cell Type No
Definition Maximum received downlink level threshold for allowing a MS to be VAMOS-unpaired from its paired MS.
Mandatory rules - RXLEV_DL_MAX_VAMOS_UNPAIRING < RXLEV_DL_MIN_VAMOS_PAIRING
Recommended --
rules
Internal comment --
Logical RXLEV_DL_MIN_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI RXLEV_DL_MIN_VAMOS_PAIRING Sub-syste BSC Cell Type No
Definition Minimum received downlink level from a MS allowing this MS to be VAMOS-paired with another MS.
0: -110 dBm, 1: -109 dBm...63: -47 dBm93: -17 dBm
Mandatory rules - RXLEV_DL_MAX_VAMOS_UNPAIRING < RXLEV_DL_MIN_VAMOS_PAIRING
Recommended --
rules
Internal comment --
Logical RXLEV_DL_ZONE B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_DL_ZONE Sub-syste BSC Cell Type Yes
Definition Downlink level threshold for inner to outer zone handover.
Mandatory rules --
Recommended If CELL_PARTITION_TYPE = Concentric AND FREQUENCY_RANGE = PGSM or DCS1800 or EGSM or DCS 1900:
rules RXLEV_DL_ZONE >= L_RXLEV_DL_H (This rule only applies to concentric and monoband cell.)
External --
comment
Internal comment Meaningful only in cells where CELL_PARTITION_TYPE = Concentric. CT: Depends on Cell Type and BTS Type
Logical RxLev_HO_to_GAN B11 Yes B12 Yes
name TRX nb No
HMI RxLev_HO_to_GAN Sub-syste BSC Cell Type No
Definition This flag allows to take into account faulty measurement results on GAN cells
Category System (CST) OMC-R access None (not in DLS) Type Flag Unit None
Coding rules 0: measurement results RxLev <> 63 are discarded, 1: measurement results RxLev <> 63 are taken into account (the value kept is 63)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RXLEV_LIMIT_PBGT_HO B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_LIMIT_PBGT_HO Sub-syste BSC Cell Type Yes
Definition Threshold on the downlink received level above which it is not necessary to trigger a handover on power budget (cause 12).
Coding rules Coded over 6 bits:0: -110 dBm, 1: -109 dBm...63: -47 dBm.
Mandatory rules --
Recommended --
rules
External --
comment
Logical RXLEV_UL_IH B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_UL_IH Sub-syste BSC Cell Type Yes
Definition Uplink level threshold for decision between intracell and intercell handover in case of bad uplink quality.
Mandatory rules RXLEV_UL_IH > L_RXLEV_UL_H
Recommended --
rules
External --
comment
Internal comment --
Logical RXLEV_UL_ZONE B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_UL_ZONE Sub-syste BSC Cell Type Yes
Definition Uplink level threshold for inner to outer zone handover.
Mandatory rules --
Recommended If CELL_PARTITION_TYPE = Concentric AND FREQUENCY_RANGE = PGSM or DCS1800 or EGSM or DCS 1900:
rules RXLEV_UL_ZONE >= L_RXLEV_UL_H (This rule only applies to concentric and monoband cell.)
External --
comment
Internal comment Meaningful only in cells where CELL_PARTITION_TYPE = Concentric. CT: Depends on Cell Type and BTS Type
Logical RXLEVmin(n) B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_MIN_n Sub-syste BSC Cell Type Yes
Definition Minimum level received from cell n to allow reception of handover.
Mandatory rules --
Recommended --
rules
External --
comment
Logical RXQUAL_DL_MAX_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI RXQUAL_DL_MAX_VAMOS_PAIRING Sub-syste
BSC Cell Type No
Definition Minimum downlink quality threshold (ie maximum value) for allowing a MS to be VAMOS-paired with another MS.
Coding rules Step size = 0.1
Mandatory rules - RXQUAL_DL_MAX_VAMOS_PAIRING < RXQUAL_DL_MIN_VAMOS_UNPAIRING
Recommended --
rules
Internal comment --
Logical RXQUAL_DL_MIN_VAMOS_UNPAIRING B11 No B12 Yes
name TRX nb No
HMI RXQUAL_DL_MIN_VAMOS_UNPAIRING Sub-syste
BSC Cell Type No
Definition Maximum downlink quality threshold (ie minimum value) for allowing a MS to be VAMOS-unpaired from its paired MS.
Mandatory rules - RXQUAL_DL_MAX_VAMOS_PAIRING < RXQUAL_DL_MIN_VAMOS_UNPAIRING
Recommended --
rules
Internal comment --
Logical SAI_LTE B11 No B12 Yes
name TRX nb No
HMI SAI_LTE Sub-syste BSC Cell Type No
Definition This parameter defines the Serving Area Identity, used in E-UTRAN.
This value allows the BSC to discriminate 3G from LTE, as the serving RAT in the Cell Identifier (serving) IE of the incoming HANDOVER REQUEST messages (even in
case of several MSC servers connected to the BSC with the Aflex feature).
Category Network (CDE) OMC-R access None (DLS) Type Abstract Unit None
Rec ref. 3GPP TS 25.413 Domai 2G-LTE Min value None Coded Min
Spec ref. External channel changes Coded Max
Coding rules Coded on 7 octets string (according to section 9.2.3.9 of 3GPP TS 25.413)
3 octets for the PLMN identity
2 octets for the LAC
2 octets for the SAC
Mandatory rules --
Recommended --
rules
comment - According to 3GPP TS 23.216, this parameter must match the value configured in the MSC for E-UTRAN. To ensure correct statistics in the target BSS, this default
SAI should be different from the SAIs used in UTRAN.
Internal comment - The feature is not optional
- if no value is configured by the operator, the handover requests are assumed coming from 3G.
Logical Schedule_period_for_basic_CBCH B11 Yes B12 Yes
name TRX nb No
HMI Schedule Period for Basic CBCH Sub-syste BSC Cell Type No
Definition Length of the DRX schedule period for the basic CBCH.
Category Site (CAE) OMC-R access Changeable Type Number Unit CBper
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Schedule_period_for_extended_CBCH B11 Yes B12 Yes
name TRX nb No
HMI Schedule period for Extended CBCH Sub-syste BSC Cell Type No
Definition Length of the DRX schedule period for the extended CBCH.
Category Site (CAE) OMC-R access Changeable Type Number Unit CBper
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SCPIR_LOW_MS_ALLOC_NON_SAIC B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_ALLOC_NON_SAIC Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a Legacy Non SAIC capable
MS, allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2). It is used by the resource
allocation algorithm.
Mandatory rules - SCPIR_LOW_MS_PC_NON_SAIC <= SCPIR_LOW_MS_ALLOC_NON_SAIC
- if 0 < SCPIR_LOW_MS_ALLOC_NON_SAIC + SCPIR_LOW_MS_ALLOC_VAMOS1 then EN_PAIRING_NON_SAIC_VAMOS1 is disabled
Recommended - A negative value means that the MS is able to correctly decode its VAMOS signal even when the other paired MS (on the VAMOS sub-channel#2) is transmitted
rules with a higher power. As consequence, the more negative the value is, the more easily the corresponding MS type could be paired, under good radio condition.
-

- if (SCPIR_LOW_MS_ALLOC of MS type1 + SCPIR_LOW_MS_ALLOC of MS type2) > 0 then MS type1 and MS type2 could not be paired together on the same radio
timeslot.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied immediately after the modification.
Internal comment With the default value (9-4>0), ALU recommends to forbid pairing of VAMOS1 with NON-SAIC.
Logical SCPIR_LOW_MS_ALLOC_SAIC B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_ALLOC_SAIC Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a Legacy SAIC capable MS,
allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2). It is used by the resource allocation
algorithm.
Mandatory rules - SCPIR_LOW_MS_PC_SAIC <= SCPIR_LOW_MS_ALLOC_SAIC
- if 0 < SCPIR_LOW_MS_ALLOC_SAIC then EN_PAIRING_SAIC_SAIC is disabled
- if 0 < SCPIR_LOW_MS_ALLOC_SAIC + SCPIR_LOW_MS_ALLOC_VAMOS1 then EN_PAIRING_SAIC_VAMOS1 is disabled
- When EN_VAMOS_SUB_SAIC_BLACKLIST is enabled, then SCPIR_LOW_MS_ALLOC_SAIC <= SCPIR_LOW_MS_ALLOC_SUB_SAIC

timeslot.
- When EN_VAMOS_SUB_SAIC_BLACKLIST is enabled, the parameter applies only to the standard Legacy SAIC capable MS (ie the Legacy SAIC capable MS not
present in the SUB_SAIC_BLACKLIST).
Internal comment --
Logical SCPIR_LOW_MS_ALLOC_SUB_SAIC B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_ALLOC_SUB_SAIC Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a substandard Legacy SAIC
capable MS, allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2).
It is used by the resource allocation algorithm.
5: 0dB;
6: +2dB;
7: +4dB;
8: +6dB;
9: +8dB;
10: +10dB
Mandatory rules - SCPIR_LOW_MS_PC_SUB_SAIC <= SCPIR_LOW_MS_ALLOC_SUB_SAIC

- SCPIR_LOW_MS_ALLOC_SAIC <= SCPIR_LOW_MS_ALLOC_SUB_SAIC
Recommended --
rules
comment - Significant if EN_VAMOS_SUB_SAIC_BLACKLIST is enabled.
Internal comment - The positive value makes the pairing of a substandard SAIC with another MS more difficult than for a standard SAIC.
Logical SCPIR_LOW_MS_ALLOC_VAMOS1 B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_ALLOC_VAMOS1 Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a VAMOS1 capable MS,
algorithm.
Mandatory rules - SCPIR_LOW_MS_PC_VAMOS1 <= SCPIR_LOW_MS_ALLOC_VAMOS1
- if 0 < SCPIR_LOW_MS_ALLOC_VAMOS1 then EN_PAIRING_VAMOS1_VAMOS1 is disabled
- if 0 < SCPIR_LOW_MS_ALLOC_VAMOS1 + SCPIR_LOW_MS_ALLOC_VAMOS2 then EN_PAIRING_VAMOS1_VAMOS2 is disabled
- Alcatel-Lucent recommends - SCPIR_LOW_MS_ALLOC_VAMOS1 < SCPIR_LOW_MS_ALLOC_NON_SAIC to forbid (non SAIC, VAMOS1) MS pairing.

timeslot.
Internal comment With the default value (9-4>0), ALU recommends to forbid pairing of VAMOS1 with NON-SAIC.
Logical SCPIR_LOW_MS_ALLOC_VAMOS2 B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_ALLOC_VAMOS2 Sub-syste BSC Cell Type No
algorithm.
- if 0 < SCPIR_LOW_MS_ALLOC_VAMOS1 + SCPIR_LOW_MS_ALLOC_VAMOS2 then EN_PAIRING_VAMOS1_VAMOS2 is disabled
- if 0 < SCPIR_LOW_MS_ALLOC_VAMOS2 then EN_PAIRING_VAMOS2_VAMOS2 is disabled

timeslot.
Internal comment --
Logical SCPIR_LOW_MS_PC_NON_SAIC B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_PC_NON_SAIC Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a Legacy Non SAIC capable
MS, allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2). It is used by the power control
algorithm.
Mandatory rules - SCPIR_LOW_MS_PC_NON_SAIC <= SCPIR_LOW_MS_ALLOC_NON_SAIC
rules with a higher power. As consequence, the more negative the value is, the longer the corresponding MS type is able to stay paired with the same companion.
- Alcatel-Lucent recommends - SCPIR_LOW_MS_ALLOC_VAMOS1 < SCPIR_LOW_MS_ALLOC_NON_SAIC to forbid (non SAIC, VAMOS1) MS pairing.

Internal comment --
Logical SCPIR_LOW_MS_PC_SAIC B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_PC_SAIC Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a Legacy SAIC capable MS,
allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2). It is used by the power control
algorithm.
Mandatory rules - SCPIR_LOW_MS_PC_SAIC <= SCPIR_LOW_MS_ALLOC_SAIC
- When EN_VAMOS_SUB_SAIC_BLACKLIST is enabled, then SCPIR_LOW_MS_PC_SAIC <= SCPIR_LOW_MS_PC_SUB_SAIC

- When EN_VAMOS_SUB_SAIC_BLACKLIST is enabled, the parameter applies only to the standard Legacy SAIC capable MS (ie the Legacy SAIC capable MS not
present in the SUB_SAIC_BLACKLIST).
Internal comment --
Logical SCPIR_LOW_MS_PC_SUB_SAIC B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_PC_SUB_SAIC Sub-syste BSC Cell Type No
Definition This parameter represents the minimum value of SCPIR (Sub-Channel Power Imbalance Ratio) allowing a correct decoding of the signal for a substandard Legacy SAIC
capable MS, allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2).
It is used by the power control algorithm.
5: 0dB;
6: +2dB;
7: +4dB;
8: +6dB;
9: +8dB;
10: +10dB
Mandatory rules - SCPIR_LOW_MS_PC_SUB_SAIC <= SCPIR_LOW_MS_ALLOC_SUB_SAIC

- SCPIR_LOW_MS_PC_SAIC <= SCPIR_LOW_MS_PC_SUB_SAIC
Recommended --
rules
comment - Significant if EN_VAMOS_SUB_SAIC_BLACKLIST is enabled..
Internal comment --
Logical SCPIR_LOW_MS_PC_VAMOS1 B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_PC_VAMOS1 Sub-syste BSC Cell Type No
allocated to the VAMOS sub-channel #1 (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2). It is used by the power control
algorithm.

Internal comment --
Logical SCPIR_LOW_MS_PC_VAMOS2 B11 No B12 Yes
name TRX nb No
HMI SCPIR_LOW_MS_PC_VAMOS2 Sub-syste BSC Cell Type No
allocated to the VAMOS sub-channel # (independently of the MS capabilities of the MS allocated into the VAMOS sub-channel #2)1. It is used by the power control
algorithm.

Internal comment --
Logical SCPIR_MODIF_STEP_SIZE B11 No B12 Yes
name TRX nb No
HMI SCPIR_MODIF_STEP_SIZE Sub-syste BSC Cell Type No
Definition Step size applied to a VAMOS pair during increasing or reduction of the SCPIR (Sub-Channel Power Imbalance Ratio).
0: 0dB; 1: 2dB; 2: 4dB; 3: 6dB; 4: 8dB; 5: 10dB; 6: 12dB; 7: 14dB; 8: 16dB; 9: 18dB; 10: 20dB
Mandatory rules --
Recommended --
rules
Internal comment - SCPIR valid range is -10,+10 (length = 20)
Logical SCPIR_MODIF_VAMOS_CCCH B11 No B12 Yes
name TRX nb No
HMI SCPIR_MODIF_VAMOS_CCCH Sub-syste BSC Cell Type No
Definition This parameter represents the SCPIR (Sub-Channel Power Imbalance Ratio) modification, applied by the BTS in downlink, to favour FACCH and SACCH frames when
such a frame is multiplexed with a TCH frame on an AQPSK burst of a VAMOS pair.
Mandatory rules --
Recommended --
rules
Internal comment - This parameter is sent to the BTS via OML
Logical SCPIR_NON_SAIC_VAMOS1_THR_1 B11 No B12 Yes
name TRX nb No
HMI SCPIR_NON_SAIC_VAMOS1_THR_1 Sub-syste BSC Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving a legacy non SAIC capable MS on the sub-channel#1 and a
VAMOS1 capable MS on the sub-channel#2.
Spec ref. BSS counter catalogue Coded Max 10
Mandatory rules SCPIR_NON_SAIC_VAMOS1_THR_1 <= SCPIR_NON_SAIC_VAMOS1_THR_2
Recommended --
rules
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS1 are enabled.
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving a legacy non SAIC capable MS on the sub-channel#1 and a
Mandatory rules - SCPIR_NON_SAIC_VAMOS1_THR_1 <= SCPIR_NON_SAIC_VAMOS1_THR_2
- SCPIR_NON_SAIC_VAMOS1_THR_2 <= SCPIR_NON_SAIC_VAMOS1_THR_3
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving a legacy non SAIC capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving a legacy non SAIC capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving a legacy non SAIC capable MS on the sub-channel#1 and a
Mandatory rules - SCPIR_NON_SAIC_VAMOS2_THR_1 <= SCPIR_NON_SAIC_VAMOS2_THR_2
- SCPIR_NON_SAIC_VAMOS2_THR_2 <= SCPIR_NON_SAIC_VAMOS2_THR_3
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving a legacy non SAIC capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
Logical SCPIR_SAIC_SAIC_THR_1 B11 No B12 Yes
name TRX nb No
HMI SCPIR_SAIC_SAIC_THR_1 Sub-syste BSC Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving two legacy SAIC capable MSs.
Mandatory rules SCPIR_SAIC_SAIC_THR_1 <= SCPIR_SAIC_SAIC_THR_2
Recommended --
rules
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_SAIC are enabled.
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving two legacy SAIC capable MSs.
Mandatory rules - SCPIR_SAIC_SAIC_THR_1 <= SCPIR_SAIC_SAIC_THR_2
- SCPIR_SAIC_SAIC_THR_2 <= SCPIR_SAIC_SAIC_THR_3
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving two legacy SAIC capable MSs.
Mandatory rules SCPIR_SAIC_SAIC_THR_2 <= SCPIR_SAIC_SAIC_THR_3
Recommended --
rules
Internal comment --
Logical SCPIR_SAIC_VAMOS1_THR_1 B11 No B12 Yes
name TRX nb No
HMI SCPIR_SAIC_VAMOS1_THR_1 Sub-syste BSC Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving a legacy SAIC capable MS on the sub-channel#1 and a
Mandatory rules SCPIR_SAIC_VAMOS1_THR_1 <= SCPIR_SAIC_VAMOS1_THR_2
Recommended --
rules
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS1 are enabled.
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving a legacy SAIC capable MS on the sub-channel#1 and a
Mandatory rules - SCPIR_SAIC_VAMOS1_THR_1 <= SCPIR_SAIC_VAMOS1_THR_2
- SCPIR_SAIC_VAMOS1_THR_2 <= SCPIR_SAIC_VAMOS1_THR_3
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving a legacy SAIC capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 1st band, lower limit of the 2nd band forSCPIR values distribution of a VAMOS pair involving a legacy SAIC capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving a legacy SAIC capable MS on the sub-channel#1 and a
Mandatory rules - SCPIR_SAIC_VAMOS2_THR_1 <= SCPIR_SAIC_VAMOS2_THR_2
- SCPIR_SAIC_VAMOS2_THR_2 <= SCPIR_SAIC_VAMOS2_THR_3
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving a legacy SAIC capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
Logical SCPIR_VAMOS1_VAMOS1_THR_1 B11 No B12 Yes
name TRX nb No
HMI SCPIR_VAMOS1_VAMOS1_THR_1 Sub-syste BSC Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving two VAMOS1 capable MSs.
Mandatory rules SCPIR_VAMOS1_VAMOS1_THR_1 <= SCPIR_VAMOS1_VAMOS1_THR_2
Recommended --
rules
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS1 are enabled.
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving two VAMOS1 capable MSs.
Mandatory rules - SCPIR_VAMOS1_VAMOS1_THR_1 <= SCPIR_VAMOS1_VAMOS1_THR_2
- SCPIR_VAMOS1_VAMOS1_THR_2 <= SCPIR_VAMOS1_VAMOS1_THR_3
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving two VAMOS1 capable MSs.
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 1st band, lower limit of the 2nd band forSCPIR values distribution of a VAMOS pair involving a VAMOS1 capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving a VAMOS1 capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving a VAMOS1 capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving a VAMOS2 capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving a VAMOS2 capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving a VAMOS2 capable MS on the sub-channel#1 and a
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 1st band, lower limit of the 2nd band for SCPIR values distribution of a VAMOS pair involving two VAMOS2 capable MSs.
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for SCPIR values distribution of a VAMOS pair involving two VAMOS2 capable MSs.
Recommended --
rules
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for SCPIR values distribution of a VAMOS pair involving two VAMOS2 capable MSs.
Recommended --
rules
Internal comment --
Logical SCRAMBLING_CODE_3G_FDD B11 Yes B12 Yes
name TRX nb No
HMI SCRAMBLING_CODE_3G Sub-syste BSC Cell Type No
Definition This parameter indicates the Primary Scrambling Code of an external 3G FDD cell, as defined in 3GPP TS 25.213.
Coding rules Binary value on 9 bits.
Mandatory rules - For a given 2G cell, the couple (ARFCN_3G (FDD), SCRAMBLING_CODE_3G_FDD) shall be unique among all the neighbour 3G FDD cells target for handover (or
both).
Recommended --
rules
External - Significant if RAT_3G is FDD
Internal comment - A coded default value is not needed since the operator cannot create a 3G FDD cell without configuring its scrambling code, even if configured for reselection only
(no dummy value needed). The value 1 has been kept in the MIB to avoid additional MIB impact and delay, but CC shall not use it.
Logical SDCCH_AVG_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI SDCCH_AVG_PERIOD Sub-syste BSC Cell Type No
Definition Period used to average the processor occupancy measurements.
Coding rules 8 bits, step size=1sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SDCCH_COUNTER B11 Yes B12 Yes
name TRX nb No
HMI SDCCH_COUNTER Sub-syste BSC Cell Type No
Definition Time during which SDCCH handovers are forbidden after completion of the Immediate Assignment procedure.
Mandatory rules --
Recommended SDCCH_COUNTER <= T_SDCCH_PC

rules
External 0 means that SDCCH handover is immediately allowed after completion of the Immediate Assignment procedure.
comment
Internal comment --
Logical SDCCH_HIGH_DELAY B11 Yes B12 Yes
name TRX nb No
HMI SDCCH_HIGH_DELAY Sub-syste BSC Cell Type No
Definition Delay added to SDCCH internal release when TCU processor load is high.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SDCCH_LOW_DELAY B11 Yes B12 Yes
name TRX nb No
HMI SDCCH_LOW_DELAY Sub-syste BSC Cell Type No
Definition Delay added to SDCCH internal release when TCU processor load is low.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SGW_INTERWORKING_LB B11 Yes B12 Yes
name TRX nb No
HMI SGW_INTERWORKING_LB Sub-syste BSC Cell Type No
Definition To configure the M3UA protocol, used on Lb interface towards the SMLC: either a Signalling GateWay is used to address SMLC over TDM, or no gateway is needed (for
SMLC over IP)
Coding rules 0: no SGW is used (M3UA works in IPSP mode)
1: a SGW is used (M3UA works in MGC mode)
Mandatory rules can be switched to 0 or 1, only while EN_LB is disabled
Recommended --
rules
comment - Parameter change: before any modification, the operator must lock all the Lb Signalling Link(s) (LBSL) of the associated SMLC. After modification, unlock the objects
and reopen the Location service for CS domain.
Internal comment --
Logical SLC B11 Yes B12 Yes
name TRX nb No
HMI Signalling Link Code Sub-syste BSC Cell Type No
name Instance N7 ch RMS No
Definition Signalling Link Code.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical SMLC_SPC B11 Yes B12 Yes
name TRX nb No
HMI SMLC_SPC Sub-syste BSC Cell Type No
Definition Signalling Point Code of the SMLC connected to the BSC.
Mandatory rules --
Recommended --
rules
External - Significant only if EN_LB is set to TRUE
comment - Lb interface is available on BSC Evolution only.
- Parameter change: before any modification, the operator must lock all the Lb Signalling Links of the modified SMLC.
Internal comment - A coded default value is not needed since the operator cannot create a SMLC without configuring its signalling point code (no dummy value needed).
Logical SMLC_TRAFFIC_MODE B11 Yes B12 Yes
name TRX nb No
HMI SMLC_TRAFFIC_MODE Sub-syste BSC Cell Type No
Definition Traffic mode of the M3UA signalling link set with the SMLC.
- When the SMLC_TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the LB_SCTP_ENDPOINT_LIST must be equal or greater than
Recommended --
rules
comment - The broadcast mode is not supported by the BSS on the Lb interface.
- Parameter change: before any modification, the operator must lock all the Lb Signalling Links of the modified SMLC.
Internal comment --
Logical SMS_INHIBIT B11 Yes B12 Yes
name TRX nb No
HMI SMS_INHIBIT Sub-syste BSC Cell Type No
Definition This flag enables/disables SMS support.
Spec ref. Short message service point to point Coded Max 1
Coding rules 0: SMS permitted, 1: SMS inhibited
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SMSCB_Features_set B11 Yes B12 Yes
name TRX nb No
HMI SMSCB_Features_Set Sub-syste BSC Cell Type No
Definition This parameter indicates which features are usable with the SMSCB product.
Coding rules 1: Features set 1, 2: Features set 2
Mandatory rules Can be changed only when SMSCB_STATE = "inactive".

If SMSCB_Features_set = FS1, then CBC_Window shall be equal to "1"- If SMSCB_Features_set = FS1, then SMSCB_Recovery shall be set to "No"- If
SMSCB_Features_set = FS1, then for all the BSC cells Use_of_Extended_CBCH shall be set to "No"- If SMSCB_Features_set = FS1, then for all the BSC cells
Nb_of_reserved_slots_for_basic_CBCH shall be set to "0"
Recommended --
rules
External When migrating from FS1 to FS2,
comment USE_OF_EXTENDED_CBCH shall be set to "Yes",
CBC_WINDOW shall be set to 4.
Internal comment --
Logical SMSCB_Mode B11 Yes B12 Yes
name TRX nb No
HMI SMSCB_Mode Sub-syste BSC Cell Type No
Definition This parameter enables to select the mode of operation, either OMC-R or CBC.
Category System (CST) OMC-R access Displayed Type Flag Unit None
Coding rules 0: OMC-R, 1: CBC
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Can be changed only when SMSCB_State is disabled
Logical SMSCB_Phase B11 Yes B12 Yes
name TRX nb No
HMI SMSCB_Phase Sub-syste BSC Cell Type No
Definition This parameter indicates whether the feature operates in GSM Phase2 or Phase 2+ mode.
Coding rules 0: Phase 2, 1: Phase 2+
Mandatory rules If SMSCB_FEATURES_SET="FS1", SMSCB_PHASE shall be set to "phase2"

'If SMSCB_FEATURES_SET="FS2", SMSCB_PHASE shall be set to "phase2+"
SMSCB_Phase can be changed only when SMSCB_STATE="inactive"
Recommended --
rules
External --
comment
Internal comment --
Logical SMSCB_Recovery B11 Yes B12 Yes
name TRX nb No
HMI SMSCB_Recovery Sub-syste BSC Cell Type No
Definition This parameter indicates if the CBC accepts the recovery-indication in Restart-Indication message.
Coding rules 0: No, 1: Yes
Mandatory rules shall be set to "No" when SMSCB_FEATURE_SET="FS1"

can be changed only when SMSCB_STATE="inactive"
Recommended --
rules
External --
comment
Internal comment --
Logical SMSCB_State B11 Yes B12 Yes
name TRX nb No
HMI SMSCB_State Sub-syste BSC Cell Type No
Definition This flag indicates if the feature is activated or deactivated.
Coding rules 0: activated, 1: deactivated
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SNMP_PRIORITY (BSC) B11 Yes B12 Yes
name TRX nb No
HMI SNMP_PRIORITY (BSC) Sub-syste BSC Cell Type No
Definition BSS internal priority used by the BSC for the SNMP flow in IP network
3: lower priority
Mandatory rules shall be equal to SNMP_PRIORITY(BTS)
Recommended --
rules
External --
comment
Internal comment - Used for OML establishment.
Logical SPGC_CCCH_SUP (BSC) B11 Yes B12 Yes
name TRX nb No
HMI SPGC_CCCH_SUP (BSC) Sub-syste BSC Cell Type No
Definition This flag indicates the support of split pg cycle on CCCH by the network.
Coding rules 0: split pg cycle on CCCH not supported in the cell
1: split pg cycle on CCCH supported in the cell
Mandatory rules Equal to SPGC_CCCH_SUP (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical SSF B11 Yes B12 Yes
name TRX nb No
HMI SSF Sub-syste BSC Cell Type No
Definition This parameter inditifies the numbering plan of the Signalling Point Code.
Coding rules coded over 4 bits.only values 0, 4, 8 and 12 are defined : Value = 0, international network; Value = 4, Spare, reserved for international use; Value = 8, National
network; Value = 12 , Reserved for national use
Mandatory rules --
Recommended --
rules
External SSF (Sub-Service Field) is composed of 4 bits: 2bits for Network Indicator and 2 spare bits.
comment
Internal comment --
Logical START_ASIG_IP_ADDRESS_2_BSC B11 No B12 Yes
name TRX nb No
HMI Start Asig IP Address 2 Sub-syste BSC Cell Type No
Definition Second IP address for the range of telecom addresses shown to the external world for the feature A signalling over IP. When this address is configured (not dummy),
the SCTP end to end redundancy is used on BSC side.
The BSC deduces every secondary telecom address of its associated endpoints from this base address.
Mandatory rules --

rules
External Parameter change: when EN_ASIG_OVER_IP is enabled and this parameter is changed from the BSC operator terminal, the BSC resets autonomously.
comment
displayed.
- the range size is 2 (2 IP addresses are reserved from the first configured)
Logical START_ASIG_IP_ADDRESS_BSC B11 Yes B12 Yes
name TRX nb No
HMI Start Asig IP Address Sub-syste BSC Cell Type No
Definition First IP address for the range of telecom addresses shown to the external world for the feature A signalling over IP. The BSC deduces every telecom address of its
associated endpoints from this base address.
Mandatory rules --

rules
External Parameter change: when EN_ASIG_OVER_IP is enabled and this parameter is changed from the BSC operator terminal, the BSC resets autonomously.
comment
displayed.
Logical START_AUP_IP_ADDRESS_BSC B11 No B12 Yes
name TRX nb No
HMI START_AUP_IP_ADDRESS_BSC Sub-syste BSC Cell Type No
Definition First IP address for the range of telecom addresses shown to the external world for the feature A user plane over IP. The BSC deduces every telecom address of its
associated endpoints (OMCP, TPGSM and CCP) from this base address.
Mandatory rules --

rules
External Parameter change: when EN_AUP_OVER_IP is enabled and this parameter is changed from the BSC operator terminal, the BSC resets autonomously.
comment
displayed.
Logical START_BSS_IP_ADDRESS_BSC B11 Yes B12 Yes
name TRX nb No
HMI Start Bss IP Address Sub-syste BSC Cell Type No
Definition First IP address for the range of telecom addresses shown to the external world for the feature Ip transport in the BSS. The BSC deduces every telecom address of its
associated endpoints (OMCP, TPGSM and CCP) from this base address.
Mandatory rules --

rules
External Parameter change: when BSS_TRANSPORT_MODE is IP and this parameter is changed from the BSC operator terminal, the BSC resets autonomously and the MFS
comment resets automatically of all the GPs connected to this BSS (PS traffic is interrupted in the BSS)..
displayed.
Logical START_IURG_IP_ADDRESS_BSC B11 Yes B12 Yes
name TRX nb No
HMI START_ADD_FUNC_IP_ADDRESS_BSC Sub-syste BSC Cell Type No
Definition First IP address for the range of telecom addresses shown to the external world for the feature support of the Iur-g+ interface. The BSC deduces every telecom
address of its associated endpoints (OMCP) from this base address.
Mandatory rules --

rules
External Parameter change: when EN_IURG is enabled and this parameter is changed from the BSC operator terminal, the BSC resets autonomously.
comment
displayed.
Logical START_LB_IP_ADDRESS_BSC B11 Yes B12 Yes
name TRX nb No
HMI START_ADD_FUNC_IP_ADDRESS_BSC Sub-syste BSC Cell Type No
Definition First IP address for the range of telecom addresses shown to the external world for the feature support of the Lb interface. The BSC deduces every telecom address
of its associated endpoints (OMCP) from this base address.
Mandatory rules --

rules
External Parameter change: when EN_LB is enabled and this parameter is changed from the BSC operator terminal, the BSC resets autonomously.
comment
displayed.
Logical START_UPLINK_REPLY B11 Yes B12 Yes
name TRX nb No
HMI START_UPLINK_REPLY Sub-syste BSC Cell Type No
Definition Maximum number of repetitions for the UPLINK FREE message (with the Uplink Access Request bit set to L) during the initial part of the uplink access procedure (i.e.
before sending the first UPLINK FREE message with the Uplink Access Request bit set to H)
Coding rules --
Mandatory rules --
Recommended --
rules
External The parameter is significant only if EN_UPLINK_REPLY is set to true.
comment
Logical STRIP_O5_CM2 B11 Yes B12 Yes
name TRX nb No
HMI Strip_Octet_5_In_CM2 Sub-syste BSC Cell Type No
Definition This flag controls the format of the Classmark 2 IE sent to the MSC.
Coding rules 0: no modification on Classmark2 IE, 1: octet 5 of Classmark2 IE is stripped out
Mandatory rules EN_SEND_CM3 and STRIP_O5_CM2 shall not be both set to 1 at the same time.
Recommended --
rules
External Default value depends on MSC type.The value indicated here is for implementation purposes.
comment
Internal comment --
Logical SUB_SAIC_BLACKLIST B11 No B12 Yes
name TRX nb No
HMI SUB_SAIC_BLACKLIST Sub-syste BSC Cell Type No
Definition List of the Legacy SAIC capable MS, considered as substandard Legacy SAIC, due to their poor performance in VAMOS mode, even in good radio conditions.
Each terminal is identified by its TAC (Type Allocation Code) value.
Coding rules One TAC is composed of 8 digits, coded over 4 octets (2 digits per octet) - ex: the decimal '246789 is coded as h'00246789.
The coded default value of -1 is for implementation purposes only; this dummy value indicates that the operator does not provide any TAC yet.
Mandatory rules all the items of the list are different
Recommended --
rules
comment - Significant if EN_VAMOS_SUB_SAIC_BLACKLIST is enabled.
Internal comment - TAC is extracted from the IMEISV of the Ciphering Mode Complete message sent by the MS to the MSC.
Logical T(conn est) B11 Yes B12 Yes
name TRX nb No
HMI T(conn est) Sub-syste BSC Cell Type No
Definition SCCP timer supervising the reception of Connection Confirm message.
Mandatory rules T(conn est) < T9105
Recommended --
rules
External --
comment
Internal comment --
Logical T(iar) B11 Yes B12 Yes
name TRX nb No
HMI T(iar) Sub-syste BSC Cell Type No
Definition SCCP timer supervising the activity on SCCP connection.
Mandatory rules --
Recommended Must be greater than T(ias) used by the MSC

rules It is recommended to configure T(iar) > (2 x T(ias) used by the MSC) + 1 min
External --
comment
Internal comment Internally, the OMC uses values in the range 402000..1530000, (ie in msec)
Logical T(ias) B11 Yes B12 Yes
name TRX nb No
HMI T(ias) Sub-syste BSC Cell Type No
Definition SCCP timer supervising the sending of Inactivity Test message.
Mandatory rules --
Recommended Must be less than T(iar) used by the MSC

rules It is recommended to configure T(ias) < (T(iar) used by the MSC - 1 min) / 2
External --
comment
Internal comment --
Logical T(rel) B11 Yes B12 Yes
name TRX nb No
HMI T(rel) Sub-syste BSC Cell Type No
Definition SCCP timer supervising the reception of Release Complete message.
Coding rules step size = 0.5sec, coded from 16 to 255, 16 == 8 sec, 255 == 127.5 sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T(sst) (G2 BSC) B11 Yes B12 Yes
name TRX nb No
HMI T(sst) Sub-syste BSC Cell Type No
Definition SCCP delay between sending of consecutive Subsystem Status Test messages.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T(sst) (MX BSC) B11 Yes B12 Yes
name TRX nb No
HMI T(sst) Sub-syste BSC Cell Type No
Definition SCCP delay between sending of consecutive Subsystem Status Test messages.
Mandatory rules --
Recommended ALU highly recommends setting this timer to 6 seconds to improve the BSC robustness.
rules
External --
comment
Internal comment --
Logical T_ALLOC_BTS B11 Yes B12 Yes
name TRX nb No
HMI T_ALLOC_BTS Sub-syste BSC Cell Type No
Definition Timer controlling the allocation/deallocation of GCHs in the BTS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_ATER_CONN B11 Yes B12 Yes
name TRX nb No
HMI T_ATER_CONN Sub-syste BSC Cell Type No
Definition Supervision of BTS-TC speech path connection / disconnection in the case of a TDM BTS connected to an IP BSC.
Spec ref. Normal Assignment Coded Max 20
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_AUTOCLEANING_MEAS_REP B11 Yes B12 Yes
name TRX nb No
HMI Autocleaning_Timer Sub-syste BSC Cell Type No
Definition Guard time for detection of SDCCH/TCH autocleaning procedure.
Category Network (CDE) OMC-R access Displayed Type Timer Unit sec
Mandatory rules --
Recommended - In micro cells, it is recommended to set N_BAD_SACCH so that T_AUTOCLEANING_MEAS_REP > N_BAD_SACCH * 480ms + 30 seconds if
rules T_AUTOCLEANING_MEAS_REP <> 0.
- Alcatel-Lucent recommends to configure the present BSS guard timer strictly greater than Max(RADIOLINK_TIMEOUT_BS, RADIOLINK_TIMEOUT_BS_AMR) x 0.480
sec of any cells of the BSS in order to let the radio link failure defence mechanism ended before internal cleanup.
External T_AUTOCLEANING_MEAS_REP = 0 inhibits the autocleaning procedure.
comment
Internal comment --
Logical T_AVG_T (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_AVG_T Sub-syste BSC Cell Type No
Definition Signal strength filter period for power control in packet transfer mode.
Coding rules binary coded on 5 bits
Mandatory rules Equal to T_AVG_T (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical T_AVG_W (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_AVG_W Sub-syste BSC Cell Type No
Definition Signal strength filter period for power control in packet idle mode.
Mandatory rules Equal to T_AVG_W (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical T_BIND_CNF B11 Yes B12 Yes
name TRX nb No
HMI T_BIND_CNF Sub-syste BSC Cell Type No
Definition Maximum waiting time to get a response to a CBSE-BIND primitive.
Recommended --
rules
External --
comment
Internal comment --
Logical T_BTS_EST_CNF B11 Yes B12 Yes
name TRX nb No
HMI T_BTS_EST_CNF Sub-syste BSC Cell Type No
Definition Supervision of the SAPI 3 Establishment procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_BTS_RLS_CNF B11 Yes B12 Yes
name TRX nb No
HMI T_BTS_RLS_CNF Sub-syste BSC Cell Type No
Definition Supervision of the SAPI 3 Release procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_BURST B11 Yes B12 Yes
name TRX nb No
HMI T_BURST Sub-syste BSC Cell Type No
Definition Delay between consecutive bursts of BLOCK or UNBLOCK messages.
Rec ref. None Domai GSM Min value 0.1 Coded Min 1
Coding rules step size =0.1 sec
Mandatory rules --
Recommended (31 x T_BURST) / B_NUM < T1_short

rules
comment
Internal comment --
Logical T_CBC_READY B11 Yes B12 Yes
name TRX nb No
HMI T_CBC_READY Sub-syste BSC Cell Type No
Definition Defines the maximum period during which the BSC tries to connect to the CBC before issueing an alarm or returning CMD-MODE Resp.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit sec
Coding rules step size: 1 sec
Mandatory rules --
Recommended T_CBC_READY > 8 * T_CONNECT

rules
External --
comment
Internal comment --
Logical T_CLEAR_REQUEST_AFTER_DISC B11 Yes B12 Yes
name TRX nb No
HMI T_CLEAR_REQUEST_AFTER_DISC Sub-syste BSC Cell Type No
Definition This timer manages the sending of CLEAR REQUEST towards the MSC, on the reception of ERROR INDICATION with cause T200 expired (N200+1) times or
CONNECTION FAILURE INDICATION (radio link failure) from BTS and after reception of DTAP DISCONNECT (With progress indicator IE not present or different from #8)
from MSC. When the timer runs, the CLEAR REQUEST messages are sent or not according to the ratio NO_CLEAR_REQUEST_AFTER_DISC_RATIO.
The BSC waits for the timer expiry before sending systematically the CLEAR REQUEST message to the MSC.
When the mechanism is not activated in the BSC, no delay/filtering is introduced and the message is always sent to the MSC.
Category Site (CAE) OMC-R access None (DLS & Restricted) Type Timer Unit sec
Coding rules 0 = the mechanism is not activated in the BSC
Mandatory rules --
Recommended --
rules
- If T_CLEAR_REQUEST_AFTER_DISC in BSC > (T305 + 2* T308) in MSC, then the MSC sends Clear Command first
- this parameter is configurable (by ALU team only) from the BSC terminal (from lab version) and not visible by customer
Logical T_CONNECT B11 Yes B12 Yes
name TRX nb No
HMI T_CONNECT Sub-syste BSC Cell Type No
Definition Defines the value of TIMER_T_CONNECT which is used by L4E_CONV during outgoing X.25 call setup association setup towards the CBC to protect against absence of
CECNF from the Network layer.
Category System (CST) OMC-R access None (DLS) Type Number Unit sec
Coding rules step size: 1 sec
Mandatory rules --
Recommended T_CBC_READY > 8 * T_CONNECT

rules
External --
comment
Internal comment This parameter is described in document 3BK 11202 0329 DSZZA.
Logical T_COUNT_I B11 Yes B12 Yes
name TRX nb No
HMI T_COUNT_I Sub-syste BSC Cell Type No
Definition Supervision of the leaky bucket counter used during the reaction to TCU overload.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_DELAY B11 Yes B12 Yes
name TRX nb No
HMI T_DELAY Sub-syste BSC Cell Type No
Definition Delays the reestablishment of RSL link by the BSC in order that FU restart can finish.
Coding rules --
Mandatory rules --
Recommended T_DELAY >= T203 + 2x (N200+1)xT200 (T_DELAY must be greater than the time needed for the FU to detect the Abis link failure)
rules
External --
comment
Internal comment --
Logical T_DELAY_GSL B11 Yes B12 Yes
name TRX nb No
HMI T_DELAY_GSL Sub-syste BSC Cell Type No
Definition Timer for LAPD re-establishment after a LAPD failure. This timer gives the delay between two LAPD establishment attempts.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_DELAY_HO_COMMAND B11 No B12 Yes
name TRX nb No
HMI T_DELAY_HO_COMMAND Sub-syste
BSC Cell Type No
Definition This parameter allows delaying handover/assignment command for AMR-NB calls with TrFO active, in order to perform a codec mode adaptation procedure before
triggering the handover execution.
Coding rules step size = 50 ms
A zero value disables the delay.
Mandatory rules --
Recommended --
rules
- Parameter change: No impact on the telecom service, on going traffic is not disrupted.
Internal comment - This parameter is configurable from the BSC terminal.
- It applies to intra BSC compatible handovers from AMR-NB (FR or HR) to AMR-NB HR, and to outgoing (inter BSC) handovers from AMR-NB (FR or HR).
Logical T_DYN_SDCCH_HOLD B11 Yes B12 Yes
name TRX nb No
HMI T_DYN_SDCCH_HOLD Sub-syste BSC Cell Type No
Definition Timer to define the delay before an dynamic SDCCH/8 timeslot will be de-allocated once all of its SDCCH sub-channels are in the free state.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_FILTER B11 Yes B12 Yes
name TRX nb No
HMI HO_ALARM_PERSISTENCE Sub-syste BSC Cell Type No
Definition Maximum time a handover alarm is maintained while no more alarm condition is detected.
Coding rules step size = 2 x SACCH frames = 0.96s. Coded over 5 bits:0: 0s, 1: 0.96s, , 31: 29.76s
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_GPRS_Resume B11 Yes B12 Yes
name TRX nb No
HMI T_GPRS_Resume Sub-syste
BSC Cell Type No
name Instance
BSC RMS No
Definition Timer used by BSC, to wait for Resume acknowledgement from SGSN before releasing the CS channel.
Rec ref. 3GPP TS 24.008 Domai GPRS Min value 0.2 Coded Min 2
Coding rules step size = 0.1 sec, coded from 2 to 50
Mandatory rules T_GPRS_Resume < T3240 (10s)
Recommended T_GPRS_Resume > (BSSGP_T4 * (Resume_retries+1))

rules
It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Ater satellite links:
- T_GPRS_RESUME = 1 s if GPRS traffic is carried through Ater terrestrial links in all the cells of the MFS,
- T_GPRS_RESUME = 1.5 s if GPRS traffic is carried through Ater satellite links in at least one cell of the MFS.
External T3240 is a MS timer see 3GPP TS 24.008
comment
Internal comment --
Logical T_GSL_ACK (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_GSL_ACK_BSC Sub-syste BSC Cell Type No
Definition Supervision of MFS acknowledgements on BSCGP.
Coding rules step size = 0.1 sec
Mandatory rules --
Recommended - T_GSL_Ack(BSC) > T200 (GSL) * (1 + N200 (GSL))

rules - T_GSL_ACK (BSC) > TCP abort interval, configured by TCP_MAX_RETRANS(BSC)
External The purpose of the 2nd recommended rule is to ensure that failure at TCP level will be detected before failure at IPGSL level
comment
Internal comment --
Logical T_HCP B11 Yes B12 Yes
name TRX nb No
HMI T_HCP Sub-syste BSC Cell Type No
Definition Time during which PING_PONG_HCP is applied after handover.
Coding rules step size= 1sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_HO_REQD_LOST B11 Yes B12 Yes
name TRX nb No
HMI T_HO_REQD_LOST Sub-syste BSC Cell Type No
Definition Supervision of the MSC response after sending of HANDOVER REQUIRED.
Mandatory rules T_HO_REQD_LOST > T7
Recommended T_HO_REQD_LOST value shall be greater than the maximum time for external handover execution
rules
External Depends on MSC type
comment
Internal comment --
Logical T_i B11 Yes B12 Yes
name TRX nb No
HMI T_i Sub-syste BSC Cell Type No
Definition Duration of SSP or SPI condition that triggers an Internal Reset procedure.
Mandatory rules --
Recommended --
rules
External Some slow MSC (e.g. legacy MSC) may take more than one minute to reply the BSC request (e.g. the SST message sent by the BSC). If the BSC is connected to
comment such kind of slow MSC, increasing the T_i value up to 120 seconds may be necessary. Otherwise after T_i expiry, the BSC triggers an unexpected Internal Reset
procedure. This leads to telecom outage for several minutes.
Internal comment - This timer is an optional timer specified by 3GPP TS 48.008 Sub-clause 3.1.15 (General SCCP Abnormal Conditions.
- The default value is applicable for both G2 BSC and BSC Evolution.
Logical T_i_LB B11 Yes B12 Yes
name TRX nb No
HMI T_i_LB Sub-syste BSC Cell Type No
Definition Duration of SMLC unreachability condition that triggers an internal LCS Reset procedure on the Lb interface.
When unreachable, the location service requests, received from the MSC, are rejected with a system failure cause.
Mandatory rules --
Recommended --
rules
- Some slow SMLC (e.g. legacy SMLC) may take time to reply the BSC request (e.g. the SST message sent by the BSC). If the BSC is connected to such kind of
slow SMLC, increasing the T_i_LB value may be necessary.
Internal comment - It is applied independently of SGW_INTERWORKING_LB value
Logical T_IA B11 Yes B12 Yes
name TRX nb No
HMI T_IA Sub-syste BSC Cell Type No
Definition Indicates the maximum time a CS IMMEDIATE ASSIGNMENT message remains in the AGCH queue.
Mandatory rules T_IA<T3101
Recommended --
rules
External --
comment
Internal comment --
Logical T_INHIBIT_CPT B11 Yes B12 Yes
name TRX nb No
HMI T_INHIBIT_CPT Sub-syste BSC Cell Type No
Definition Time during which the HO Causes 14, 21, 24 and 36 are inhibited.
Mandatory rules --
Recommended --
rules
External T_INHIBIT_CPT = 0 inhibits the anti ping-pong function.
comment
Internal comment --
Logical T_INTRF_L3 B11 Yes B12 Yes
name TRX nb No
HMI RF_RES_IND_PERIOD Sub-syste BSC Cell Type No
Definition Delay between two consecutive RF RESOURCE INDICATION.
Mandatory rules T_INTRF_L3 > Max (T11, T_qho, T11_FORCED) & T_INTRF_L3 > INTAVE
Recommended --
rules
External --
comment
Logical T_LB_OV B11 Yes B12 Yes
name TRX nb No
HMI T_LB_OV Sub-syste BSC Cell Type No
Definition Supervision of the leaky bucket counter used during the reaction to FU overload.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_LCS_RESTART (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_LCS_RESTART_BSC Sub-syste BSC Cell Type No
Definition BSC timer to guard the response from the SMLC in case of LCS Restart procedure (i.e. initialisation procedure).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_Loc_abort B11 Yes B12 Yes
name TRX nb No
HMI T_Loc_abort Sub-syste BSC Cell Type No
Definition BSC timer supervising the response from the SMLC in case of Location Abort.
Mandatory rules --
Recommended T_Loc_abort < T_Location

rules
External The timer is meaningful in the BSC when EN_LCS=1.
comment
Internal comment The BSC cancels T_Location and starts T_Loc_abort in case of LCS abort procedure towards the SMLC.
Logical T_Loc_abort_LB B11 Yes B12 Yes
name TRX nb No
HMI T_Loc_abort_LB Sub-syste BSC Cell Type No
Definition BSC timer, on a per call basis, supervising athe response from the SMLC in case of Location Abort on Lb interface
Mandatory rules --
Recommended --
rules
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied on new locations procedures initiated after modification.
Internal comment --
Logical T_Location B11 Yes B12 Yes
name TRX nb No
HMI T_Location Sub-syste BSC Cell Type No
Definition BSC timer, on a per call basis, supervising the response from the SMLC in case of Location request, when no RRLP exchange is triggered with the MS.
Mandatory rules T_Location + T_Location_Longer > T_LCS_Delay_Tolerant >= T_LCS_Low_Delay
Recommended -
rules
External The timer is meaningful in the BSC when EN_LCS=1.
comment
Internal comment The BSC cancels T_Location and starts T_Location_Longer in case of RRLP message flow between the SMLC and the MS.
Logical T_Location_LB B11 Yes B12 Yes
name TRX nb No
HMI T_Location_LB Sub-syste BSC Cell Type No
Definition BSC timer, on a per call basis, supervising any response from the SMLC on Lb interface.
Rec ref. RFC 2474/2475, 2598 Domai LCS Min value 1 Coded Min 2
Mandatory rules --
Recommended --
rules
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied on new locations procedures initiated after modification.
Internal comment --
Logical T_Location_Longer B11 Yes B12 Yes
name TRX nb No
HMI T_Location_Longer Sub-syste BSC Cell Type No
Definition BSC timer, on a per call basis, supervising the response from the SMLC in case of Location request, when a RRLP exchange is triggered with the MS.
Recommended T_Location_Longer > T_Location

rules
External The timer is meaningful in the BSC when EN_LCS=1, and replaces T_Location timer in case of Conventional GPS, MS Assisted A-GPS and MS Based A-GPS
comment positioning methods.
Internal comment The BSC cancels T_Location and starts T_Location_Longer in case of RRLP message flow between the SMLC and the MS.
Logical T_MAX_HOLD_MUXRTP B11 No B12 Yes
name TRX nb No
HMI T_MAX_HOLD_MUXRTP Sub-syste BSC Cell Type No
Definition Maximum holding time in BSC before sending a MUXRTP packet.
A MUXRTP packet may be sent either its size is above the size threshold MUXRTP_SIZE or the timer has expired.
Coding rules step size = 0,5 ms
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_MAX_HOLD_MUXTRAUP B11 Yes B12 Yes
name TRX nb No
HMI T_MAX_HOLD_MUXTRAUP Sub-syste BSC Cell Type No
Definition Maximum holding time in BTS and TC before sending a MUXTRAUP packet.
A MUXTRAUP packet may be sent either its size is above the size threshold MUXTRAUP_SIZE or the timer has expired.
Mandatory rules --
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is disabled
comment
- When EN_AUP_OVER_IP is enabled, the BSC uses T_MAX_HOLD_MUXTRAUP_TPIP instead.
Logical T_MAX_HOLD_MUXTRAUP_TPIP B11 No B12 Yes
name TRX nb No
HMI T_MAX_HOLD_MUXTRAUP_TPIP Sub-syste
BSC Cell Type No
Definition Maximum holding time in BSC before sending a DL MUXTRAUP packet to the BTS, when A user plane over IP is enabled.
A MUXTRAUP packet may be sent either its size is above the size threshold MUXTRAUP_SIZE or the timer has expired.
Coding rules step size = 0,625 msec
Mandatory rules --
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is enabled
comment
Internal comment - the BTS and the TC still use T_MAX_HOLD_MUXTRAUP.
- the step size is derived from the internal clock frequency of the TPIP board
Logical T_MPDCH_EST_PROC (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_MPDCH_EST_PROC (BSC) Sub-syste BSC Cell Type No
Definition Duration of the MPDCH establishment procedure.
Category System (CST) OMC-R access None (not in DLS) Type Timer Unit sec
Coding rules --
Mandatory rules Equal to T_MPDCH_EST_PROC (MFS)
Recommended This covers the maximum time taken by MS to become aware of a new cell configuration
rules
External --
comment
Internal comment Needed for MPDCH feature
Logical T_MS_CELL_REJ B11 Yes B12 Yes
name TRX nb No
HMI T_MS_CELL_REJ Sub-syste BSC Cell Type No
Definition Delay where the cells the MS failed to handover, cannot be selected as targets in subsequent handover attempts.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_NOTIF_RESPONSE_DELAY B11 Yes B12 Yes
name TRX nb No
HMI T_NOTIF_RESPONSE_DELAY Sub-syste BSC Cell Type No
Definition This Timer is used to delay the Multiple SACCH Info Modify and the VGCS_ADD_INFO in order to give the MS a chance to receive the immediately transmitted
VGCS_ADD_INFO/FACCH and SI6 messages
Category Site (CAE) OMC-R access Changeable Type Timer Unit ms
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_OVL_MSC B11 Yes B12 Yes
name TRX nb No
HMI T_OVL_MSC Sub-syste BSC Cell Type No
Definition Minimum delay between two consecutive OVERLOAD messages sent to the MSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_PAG_CS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_PAG_CS Sub-syste BSC Cell Type No
Definition This timer indicates the maximum time a CS PAGING message can remain in a Paging Group Queue. It includes the round-trip delay on A and A-bis or Gs/Gb and A-bis
interface.
Mandatory rules Equal to T_PAG_CS (MFS)
Recommended T_PAG_CS<T3113 (MSC timer)

rules
External --
comment
Internal comment round trip delay between MSC and BTS
Logical T_PAG_PS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_PAG_PS Sub-syste BSC Cell Type No
Definition This timer indicates the maximum time a PS PAGING message can remain in a Paging Group Queue. It includes the round-trip delay on Gb and A-bis interface.
Mandatory rules Equal to T_PAG_PS (MFS)
Recommended T_PAG_PS < T3313 (SGSN timer)

rules
External --
comment
Internal comment round trip delay between SGSN and BTS
Logical T_PDA B11 Yes B12 Yes
name TRX nb No
HMI T_PDA Sub-syste BSC Cell Type No
Definition Indicates the maximum time an Immediate Assignment message for a DL TBF establishment on PCH remains in the PCH queue.
Category Site (CAE) OMC-R access Virtual changeable Type Timer Unit sec
Mandatory rules The T_PDA parameter is computed by the OMC as follows:

T_PDA = T_GPRS_assign_pch, or equivalently,
T_PDA = 1200 ms if BS_PA_MFRMS=2

T_PDA = 2400 ms if BS_PA_MFRMS=9.
Recommended --
rules
External --
comment
Internal comment The T_PDA parameter is computed automatically by the OMC as a function of the BS_PA_MFRMS parameter.The T_PDA parameter is not displayed to the O&M user.
Logical T_PUA B11 Yes B12 Yes
name TRX nb No
HMI T_PUA Sub-syste BSC Cell Type No
Definition Indicates the maximum time an Immediate Assignment message for a UL or DL TBF establishment on AGCH remains in the AGCH queue.
Mandatory rules The T_PUA parameter is computed by the OMC as follows:

T_PUA = T_ul_assign_ccch = T_GPRS_assign_agch (See the table below)
AG_PREMPT_PCH/BCCH_EXT/CCCH_CONF/BS_AG_BLKS_RES/T_GPRS_agch_queuing_max (ms)/Comments
Disabled/False/CCCH not combined/0/600/
Disabled/False/CCCH combined/0/1000/
Disabled/True/CCCH not combined/0/x/Not allowed
Disabled/True/CCCH not combined/1/2000/
Disabled/True/CCCH combined/0/x/Not allowed
Disabled/True/CCCH combined/1/2000/
Disabled/True/CCCH combined/2/1000/
Enabled/False/CCCH not combined/0/600/
m
template

Recommended Enabled/False/CCCH combined/0/1000/ --
rules Enabled/False/CCCH combined/1/1000/
External Enabled/False/CCCH combined/2/1000/ --
comment Enabled/True/CCCH not combined/0/x/Not allowed
Internal comment Enabled/True/CCCH not combined/1/600/ The T_PUA parameter is computed automatically by the OMC as a function of the AG_PREEMPT_TCH, BCCH_EXT,
CCCH_CONF and BS_AG_BLKS_RES parameters.
Enabled/True/CCCH not combined/2/600/ The T_PUA parameter is not displayed to the O&M user.
Logical T_qho B11 Yes B12 Yes
name TRX nb No
HMI T_QHO Sub-syste BSC Cell Type No
Definition Maximum queuing time for Handover Requests.
Mandatory rules T_INTRF_L3 > Max (T11, T_qho, T11_FORCED)
Recommended --
rules
External --
comment
Logical T_RCR_ACK B11 Yes B12 Yes
name TRX nb No
HMI T_RCR_ACK Sub-syste BSC Cell Type No
Definition Supervision of the RF Channel Release procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RECOVERY B11 Yes B12 Yes
name TRX nb No
HMI T_RECOVERY Sub-syste BSC Cell Type No
name Instance OMC RMS No
Definition Delay between two consecutive audits on trace file transfer status when a file transfer failure occurs.
Category System (CST) OMC-R access None (DLS) Type Timer Unit mn
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted by the OMC-R to the BSC at init with the OCD_admin tool
Logical T_REPETITION_CHANNEL_RELEASE B11 Yes B12 Yes
name TRX nb No
HMI T_REPETITION_CHANNEL_RELEASE Sub-syste BSC Cell Type No
Definition This parameter defines the repetition period of CHANNEL RELEASE message sent on FACCH
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_REPETITION_UPLINK_FREE B11 Yes B12 Yes
name TRX nb No
HMI T_REPETITION_UPLINK_FREE Sub-syste BSC Cell Type No
Definition Delay between consecutive repetitions of the UPLINK FREE message, sent to the mobile station. The UPLINK FREE messages shall be repeated as long as no uplink is
granted to a mobile station.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - It is a CDM parameter
- The minimum value is 20 ms, since the UPLINK FREE message is sent on FACCH of VGCS channel and the periodicity of FACCH is 20 ms.
The maximum value is extracted from 3GPP TS 44.018.
Logical T_RESELECTION B11 Yes B12 Yes
name TRX nb No
HMI T_RESELECTION Sub-syste BSC Cell Type No
Definition Period during which the cell reselection criteria of the priority algorithm must be verified to allow the cell reselection; used by a LTE-capable MS/UE.
Coding rules Coded_value = (sec / 5) - 1, step size = 5
Mandatory rules --
Recommended --
rules
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted
Internal comment --
Logical T_RMS_BSC B11 Yes B12 Yes
name TRX nb No
HMI T_RMS_BSC Sub-syste BSC Cell Type No
Definition General supervision of RMS in the BSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RMS_BSC_RECONF B11 Yes B12 Yes
name TRX nb No
HMI T_RMS_BSC_RECONF Sub-syste BSC Cell Type No
Definition Delay to restart RMS job after reconfiguration.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RMS_BSC_RESTART B11 Yes B12 Yes
name TRX nb No
HMI T_RMS_BSC_RESTART Sub-syste BSC Cell Type No
Definition Delay to restart RMS job after TRE restart.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RMS_BTS B11 Yes B12 Yes
name TRX nb No
HMI T_RMS_BTS Sub-syste BSC Cell Type No
Definition Time interval between BTS transfer of 2 successive RMS blocks of measurements.
Mandatory rules T_RMS_BTS < T_RMS_BSC
Recommended T_RMS_BSC > 2* T_RMS_BTS

rules
External --
comment
Internal comment --
Logical T_RTP_PNRT B11 No B12 Yes
name TRX nb No
HMI RTP Packet Not received Time Sub-syste BSC Cell Type No
Definition Maximum time during which the BSC did not received any RTP packet from the MGW, before triggering any action.
Mandatory rules --
Recommended 180ms should be set only if MGW generates SID frames every 160ms (recommended by 3GPP). If MGW generates SID frames every 480ms (allowed by 3GPP),
rules 500ms is the minimum value to be used.
comment
Internal comment - This parameter is configurable from the BSC terminal.
Logical T_SCON B11 Yes B12 Yes
name TRX nb No
HMI T_SCON Sub-syste BSC Cell Type No
Definition Timer for supervising the congestion duration in the network. During the signalling congestion, notified by the SMLC on the Lb interface, the location requests received
from the MSC are not processed anymore. At this timer expiry, they will be again.
Coding rules --
Mandatory rules --
Recommended --
rules
External - Significant if EN_LB is enabled
comment
Internal comment --
Logical T_SDCCH_PC B11 Yes B12 Yes
name TRX nb No
HMI T_SDCCH_PC Sub-syste BSC Cell Type No
Definition Time during which power control on SDCCH is inhibited after completion of the Immediate Assignment procedure.
Coding rules step size = 1 (2 x Samfr)
Mandatory rules --
Recommended T_SDCCH_PC >= SDCCH_COUNTER

rules
External --
comment
Internal comment --
Logical T_SEND_MULTIPLE_PAGING_CMD B11 Yes B12 Yes
name TRX nb No
HMI T_SEND_MULTIPLE_PAGING_CMD Sub-syste BSC Cell Type No
Definition Maximum time during which Paging Requests are buffered by the BSC before sending MULTIPLE PAGING COMMAND on Abis and before sending PAGING
COORDINATION REQUEST on BSCGP.
Coding rules Step size = 50 msec.
Mandatory rules --
Recommended --
rules
External This mechanism does not apply to G2 BSC.
comment When EN_BSS_PAGING_COORDINATION is disabled, the multiple paging on BSCGP is disabled too.
Internal comment --
Logical T_SHARED_DTM_INFO (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T_SHARED_DTM_INFO (BSC) Sub-syste BSC Cell Type No
Definition Timer monitoring the reception of BSCGP BSC Shared DTM Info Indication (periodic or not) on BSC side.
Spec ref. Dual Transfer Mode Functional Specification Coded Max 100
Coding rules Step size = 1 sec
Mandatory rules shall be at max equal to T_SHARED_DTM_INFO (MFS) / 2
Recommended --
rules
External --
comment
Internal comment Due to BSC implementation constraints, with a default value of 8 sec, the observed value on BSCGP interface will be in the range [8;9.6] sec. This has no system
impact.
Logical T_SMSCB_RESP B11 Yes B12 Yes
name TRX nb No
HMI T_SMSCB_RESP Sub-syste BSC Cell Type No
Definition Maximum waiting time to get a response from the BTS to a primitive.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_START_MUXRTP B11 No B12 Yes
name TRX nb No
HMI T_START_MUXRTP Sub-syste BSC Cell Type No
Definition Minimum duration between the AUP over IP establishment and the sending of the first muliplexed RTP packet (with header compression) sent by the BSC for a given RTP
session.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_TC_BTS_LINK_POLLING B11 Yes B12 Yes
name TRX nb No
HMI T_TC_BTS_LINK_POLLING Sub-syste BSC Cell Type No
Definition The timer used by the BTS to send periodically to the TC a message in order that the TC keeps alive the BTS context, even in case of no traffic.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_TFO B11 Yes B12 Yes
name TRX nb No
HMI T_TFO Sub-syste BSC Cell Type No
Definition Timer for sending and acknowledgement of No_speech frames in case of TFO.
Coding rules coded on 8 bits, step size = 20 ms
Mandatory rules --
Recommended --
rules
External This parameter is set to 620ms by the BSC in case of Abis/Ater via satellite.
comment
Internal comment --
Logical T_TRAU_ACK_WAIT B11 Yes B12 Yes
name TRX nb No
HMI T_TRAU_ACK_WAIT Sub-syste BSC Cell Type No
Definition Supervision of the correct receipt of Commands between CCU and TRAU, in case of IP transport.
Coding rules step size = 20 msec
Mandatory rules --
Recommended --
rules
External Default value in case of Abis/Ater per satellite : 640 msec.
comment
Internal comment - Sent to the BTS via OML and the TC via TCSL.
Logical T_WAIT_SMLC_RESET_ACK B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_SMLC_RESET_ACK Sub-syste
BSC Cell Type No
name Instance
SMLC RMS No
Definition Timer monitoring the receipt of the TS 49.031 RESET ACKNOWLEDGE message from the SMLC during the RESET procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Significant if EN_RESET_LB is enabled
Internal comment --
Logical T_WAIT_UPLINK_ACCESS B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_UPLINK_ACCESS Sub-syste BSC Cell Type No
Definition Guard timer to wait for an Uplink Access. If no such bursts are received at this timer expiry, the BSC releases the voice group call channel in that cell and provide
notifications containing no channel description.
Mandatory rules --
Recommended T_Wait_Uplink_Access >= [START_UPLINK_REPLY + (10 * WAIT_UPLINK_ACCESS)] * T_REPETITION_UPLINK_FREE

rules
External The parameter is significant only if EN_UPLINK_REPLY is set to true
comment
Internal comment --
Logical T_WAIT_UPLINK_REQUEST_ACK B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_UPLINK_REQUEST_ACK Sub-syste BSC Cell Type No
Definition Guard timer to wait for UPLINK REQUEST ACK or UPLINK REQUEST REJECT message from the MSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T1_0858 B11 Yes B12 Yes
name TRX nb No
HMI T1_0858 Sub-syste BSC Cell Type No
Definition Delay during which, after reception of an OVERLOAD from the BTS, a new OVERLOAD is ignored.
Mandatory rules T1_0858 < T2_0858
Recommended --
rules
External --
comment
Internal comment --
Logical T1_long B11 Yes B12 Yes
name TRX nb No
HMI T1_long Sub-syste BSC Cell Type No
Definition Hold off time before attempting another Block/Unblock procedure.
Coding rules --
Mandatory rules --
Recommended T1_long >= T1_short

rules
comment
Internal comment --
Logical T1_short B11 Yes B12 Yes
name TRX nb No
HMI T1 Sub-syste BSC Cell Type No
Definition Supervision of the Blocking/Unblocking procedure.
Mandatory rules --
Recommended T1_short > (31 x T_BURST) / B_NUM

rules
comment
Internal comment --
Logical T11 B11 Yes B12 Yes
name TRX nb No
Definition Maximum queuing time for Assignment Requests.
Coding rules step size = 1 s
Recommended --
rules
comment
Internal comment --
Logical T11_FORCED B11 Yes B12 Yes
name TRX nb No
HMI T11_FORCED Sub-syste BSC Cell Type No
Definition Maximum queuing time for Assignment Requests where queuing is not allowed by the MSC.
Recommended --
rules
comment
Internal comment Must be < assignment timer in the MSC (trr1).
Provision in MIB B5
name TRX nb No
Definition Delay for acknowledgement of RESET received from MSC.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Maximum queuing time for the VGCS Assignment Requests
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Period of time where a new OVERLOAD that is received from the MSC, is not processed after reception of a processed OVERLOAD.
Coding rules step size: 0.1 sec
Mandatory rules T17 < T18_overload
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Delay between consecutive debarring actions after a BSS outage.
Coding rules Step size: 0.1 sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T18_Overload B11 Yes B12 Yes
name TRX nb No
HMI T18_OVERLOAD Sub-syste BSC Cell Type No
Definition Delay between the latest MSC OVERLOAD message or DTC internal overload detection and debarring action. Also delay between consecutive debarring actions for
overload procedure and Telecom global reset procedure.
Coding rules step size: 0.1 sec
Mandatory rules T18_OVERLOAD > T17
Recommended --
rules
External --
comment
Internal comment Comes from the split of T18 into two timers: T18 and T18_OVERLOAD
name TRX nb No
Definition Supervision of the Reset Circuit procedure.
Rec ref. GSM TS 05.08 Domai GSM Min value 0.1 Coded Min 1
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical T2_0858 B11 Yes B12 Yes
name TRX nb No
HMI T2_0858 Sub-syste BSC Cell Type No
Definition Minimum delay between debarring of an access class, in the case where the BTS stops sending OVERLOAD.
Mandatory rules T2_0858 > T1_0858
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of Circuit Group Blocking procedure.
Coding rules step size=0.1 sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T200 (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T200 (BSC) Sub-syste BSC Cell Type No
Definition Supervision of acknowledgements.
Coding rules step size: 100ms; (1: 100ms, 2: 200ms, 3: 300ms, 4: 400ms, .. . , 10: 1000ms
Mandatory rules --
Recommended The recommended value for Abis via satellite is 1000 ms.
rules
External The value of T200 (BSC) is driven by the associated Abis connection type.
comment It can be changed indirectly from the OMC (through the change of Abis connection type)
The default value 300 ms corresponds to Abis terrestrial link.
Internal comment --
Logical T200_GSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T200_GSL (BSC) Sub-syste BSC Cell Type No
Definition Supervision of acknowledgements on the GSL link.
Coding rules --
Mandatory rules --
Recommended T_GSL_Ack (BSC) > T200_GSL (BSC) * (1 + N200_GSL (BSC))

rules
External --
comment
Internal comment --
Logical T200_TF B11 Yes B12 Yes
name TRX nb No
HMI T200_TF Sub-syste BSC Cell Type No
Definition Supervision of acknowledgements for FACCH (TCH FR associated) SAPI 0.
Spec ref. LAPDm functional specification Coded Max 255
Coding rules Step size = 20 msec
Mandatory rules --
Recommended Values higher than 1000ms are not recommended by Alcatel-Lucent (very far to the 3GPP values):
External Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately on new CS calls established after modification.
comment
When Repeated DL FACCH is used, 40msec are automatically added by the BTS.
Internal comment Sent to the BTS via OML. Default value shall be used to ensure normal behaviour of LAPDm layer.
Logical T200_TH B11 Yes B12 Yes
name TRX nb No
HMI T200_TH Sub-syste BSC Cell Type No
Definition Supervision of acknowledgements for FACCH (TCH HR associated) SAPI 0.
Coding rules step size = 20 msec.
Mandatory rules --
Recommended Values higher than 1000ms are not recommended by Alcatel-Lucent (very far to the 3GPP values):
External Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately on new CS calls established after modification.
comment
When Repeated DL FACCH is used, 40msec are automatically added by the BTS.
Internal comment Sent to the BTS via OML. Default value shall be used to ensure normal behaviour of LAPDm layer.
name TRX nb No
HMI T203 (BSC) Sub-syste BSC Cell Type No
Definition Link supervision timer.
Coding rules --
Mandatory rules Equal to T203 (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical T203_GSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T203_GSL (BSC) Sub-syste BSC Cell Type No
Definition Link supervision timer on the GSL link.
Coding rules --
Mandatory rules Equal to T203_GSL (MFS)
Recommended --
rules
External --
comment
Internal comment --
Logical T25 B11 No B12 Yes
name TRX nb No
Definition Supervision of the INTERNAL HANDOVER REQUIRED message, sent to the MSC.
Rec ref. 3GPP TS 48.008 Domai IP Min value 0.5 Coded Min 5
Mandatory rules --
Recommended --
rules
External - Parameter change: No impact on the telecom service, on going calls are not disrupted. Change applied on timers started after modification
comment
Internal comment --
name TRX nb No
Definition Supervision of the Immediate Assignment procedure.
Mandatory rules --
Recommended T3101 > 2s

rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the Internal Handover procedure.
Mandatory rules T3103 > Ny1 x T3105_D.

T3103 > Ny1 x T3105_F_FR.
T3103 > Ny1 x T3105_F_HR.
T3103 > T3106_D.
T3103 > T3106_F
Recommended --
rules
External --
comment
Internal comment --
Logical T3105_D B11 Yes B12 Yes
name TRX nb No
HMI T3105D Sub-syste BSC Cell Type No
Definition Delay between consecutive repetitions of PHYSICAL INFORMATION on SDCCH.
Coding rules --
Mandatory rules T3105_D x Ny1 < T3103

T3105_D x Ny1 < T9113
Recommended T3105_D x Ny1 > T3124

rules T3105_D << T3124 (T3124 = 675 ms on SDCCH)
External --
comment
Logical T3105_D_STOP B11 Yes B12 Yes
name TRX nb No
HMI T3105D_STOP Sub-syste BSC Cell Type No
Definition Criterion to stop T3105_D timer.
Coding rules 0: stopped on reception of SABM frame, 1: stopped on reception of any correct L2 signalling frame
Mandatory rules --
Recommended --
rules
External --
comment
Logical T3105_F_FR B11 Yes B12 Yes
name TRX nb No
HMI T3105F_FR Sub-syste BSC Cell Type No
Definition Delay between consecutive repetitions of PHYSICAL INFORMATION on FACCH for FR channels.
Coding rules --
Mandatory rules T3105_F_FR x Ny1 < T3103

T3105_F_FR x Ny1 < T9113
Recommended T3105_F_FR x Ny1 > T3124

rules T3105_F_FR << T3124 (T3124 = 320 ms on TCH)
External --
comment
Logical T3105_F_HR B11 Yes B12 Yes
name TRX nb No
HMI T3105F_HR Sub-syste BSC Cell Type No
Definition Delay between consecutive repetitions of PHYSICAL INFORMATION on FACCH for HR channels.
Coding rules --
Mandatory rules T3105_F_HR x Ny1 < T3103

T3105_F_HR x Ny1 < T9113
Recommended T3105_F_HR x Ny1 > T3124

rules T3105_F_HR << T3124 (T3124 = 320 ms on TCH)
External --
comment
Logical T3105_F_STOP B11 Yes B12 Yes
name TRX nb No
HMI T3105F_STOP Sub-syste BSC Cell Type No
Definition Criterion to stop T3105_F timer.
Coding rules 0: stopped on reception of SABM frame, 1: stopped on reception of any correct L2 signalling frame or of a correct traffic frame
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
HMI T3106D Sub-syste BSC Cell Type No
Definition Supervision of the reception of valid frame from the MS on the target cell in case of SDCCH synchronous handover.
Coding rules --
Mandatory rules T3106_D < T3103

T3106_D < T9113
Recommended --
rules
External --
comment
Logical T3106_D_STOP B11 Yes B12 Yes
name TRX nb No
HMI T3106D_STOP Sub-syste BSC Cell Type No
Definition Criterion to stop T3106_D timer.
Coding rules 0: stopped on reception of SABM frame, 1: stopped on reception of any correct L2 signalling frame
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T3106_F B11 Yes B12 Yes
name TRX nb No
HMI T3106F Sub-syste BSC Cell Type No
Definition Supervision of the reception of valid frame from the MS on the target cell in case of TCH synchronous handover.
Coding rules --
Mandatory rules T3106_F < T3103

T3106_F < T9113
Recommended --
rules
External --
comment
Logical T3106_F_STOP B11 Yes B12 Yes
name TRX nb No
HMI T3106F_STOP Sub-syste BSC Cell Type No
Definition Criterion to stop T3106_F timer.
Coding rules 0: stopped on reception of SABM frame, 1: stopped on reception of any correct L2 signalling frame or of a correct traffic frame
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the Assignment procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the Channel Release procedure.
Mandatory rules --
Recommended T3109 > RADIOLINK_TIMEOUT + 1s

rules
External --
comment
Internal comment --
name TRX nb No
Definition Delay of the RF Channel Release procedure.
Mandatory rules --
Recommended T3111 > 2 x T200_D. T3111 > 2 x T200_TH. T3111 = T3110 (MS)
rules
External --
comment
Internal comment --
name TRX nb No
Definition This timer is used for the repetition of the VGCS UPLINK GRANT message during the uplink access procedure. If the timer expires before the reception of a correctly
decoded frame from MS, the BTS repeats the VGCS UPLINK GRANT message to the requesting MS
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
Definition This timer is started by sending an INTER SYSTEM TO UTRAN HANDOVER message to the MS and is normally stopped when the MS has correctly seized the UTRAN
channel(s). Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Timer controlling the period sending of SYSTEM INFORMATION messages to the BTS to avoid sleeping cell problems.
Category System (CST) OMC-R access None (DLS) Type Timer Unit mn
Coding rules Step size = 1 min
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T3148n (BSC) B11 Yes B12 Yes
name TRX nb No
HMI T3148n (BSC) Sub-syste BSC Cell Type No
Definition Timer controlling on BSC side the uplink DTM assignment. It is started at reception of DTM Request, and stopped at reception of DTM Assignment Command or DTM Reject
from MFS.
Def value 3,8 Coded Def 38
Mandatory rules Shall be equal to T3148n (MFS)
Recommended --
rules
External --
comment
Internal comment Corresponds to T3148 (on MS side) - Round Trip Delay
name TRX nb No
Definition This timer defines the maximum time the MS waits for a packet UL assignment, after sending a Packet Resource Request (case of two-phase UL TBF establishment) or
after including a Channel Request Description Information Element in a Packet Downlink Ack/Nack (case of UL TBF establishment on a concurrent DL TBF). Broadcast in
SI13 within the GPRS Cell Options IE.
Coding rules Coded on 3 bits as follows:
001: 1000 ms
010: 1500 ms
011: 2000 ms
100: 2500 ms
101: 3000 ms
110: 3500 ms
111: 4000 ms.
Recommended It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Abis or Ater satellite links:
rules - T3168 = 1 s if GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell,
- T3168 = 1.5 s if GPRS traffic is carried through Abis or Ater satellite links (round_trip_delay >= 500ms) in the serving cell and Abis_transport_mode(MFS) = 0 (TDM).
- T3168 = 2 s if GPRS traffic between the corresponding BTS and the MFS is carried through satellite link (round_trip_delay >= 500ms), and
Abis_transport_mode(MFS) = 1 (IP) for this BTS.
External The setting of T3168 should leave sufficient time to the MFS for granting PDCHs for serving the UL TBF request, plus also cover the round trip time and the possible
comment queuing delay within the MFS before the Packet Uplink Assignment can be sent to the Mobile Station. Therefore a value of 500 ms is not allowed in this release of the
Alcatel BSS.
Internal comment The following rules that cannot be checked by the OMC must be fulfilled nevertheless:
1. T3168 < T_ACK_WAIT - MAX_UL_TBF_SPDCH*20 - 60 (ms)
2. T3168 > T_MFS_Processing + T_Queuing_PACCH + round_trip_delay.
T_MFS_Processing corresponds to the processing time that can be expected at worse in the MFS for answering an uplink TBF request. Because the MFS may have
to request additional PDCHs to the BSC (which can take about 400 msec), a value of 500 msec should be considered for this parameter.
T_Queuing_PACCH corresponds to the maximum queuing time expected on PACCH and a value of about 200 msec should be considered.
m
template
Note that the chosen default values shall ensure that those rules are met.
name TRX nb No
Definition Wait for release of the downlink TBF on MS side after reception of the final block by the MS.
0 0 0: 500 msec
0 0 1: 1000 msec
0 1 0: 1500 msec
1 1 1: 200 msec
T3192 + T_MAX_EXTENDED_UL + round_trip_delay < 5 sec
Recommended T3192>MS-BSS roundtrip delay + RRBP maximum duration (60 ms)

rules It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Abis or Ater satellite links:
==> Case GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell:
i) T3192 = 1000 ms if the non-DRX mode is not activated and the delayed DL TBF release mode is not activated in the cell (i.e. if DRX_TIMER_MAX = 0 and
EN_DELAYED_DL_TBF_REL = 0)
ii) T3192 = 500 ms if the non-DRX mode is activated or the delayed DL TBF release mode is activated in the cell (i.e. if DRX_TIMER_MAX > 0 or
iii) however, if T3192 is finally set to 200 msec, then :
- some abnormal DL TBF release may occur during the delayed phase, and
- the MS may not receive the NC2 deactivation order from the BSS, which may lead the MS to send useless PMR before leaving its ready state.
==> Case GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell:
External The following values ofT3192 defined in the 3GPP TS 04.60 are not supported in this release of the Alcatel BSS:
comment 0 1 1: 0 msec
1 0 0: 80 msec
Internal comment -- m
B11 Yes B12 Yes template
name TRX nb No
Definition This timer indicates to the MS the delay between two consecutive Periodic Location Update procedures.
Category Site (CAE) OMC-R access Changeable Type Number Unit 6 mn
Coding rules 0: no periodic location update
Recommended --
rules
External --
comment
Internal comment --
1 0 1: 120 msec
1 1 0: 160 msec
name TRX nb No
Definition Supervision of RESET message sent to the MSC.
Mandatory rules --
Recommended --
rules
External T4 shall be set greater than T2 (timer in MSC).
comment
Internal comment Used only when NBR_RESET_REP <> 0.
name TRX nb No
Definition Timer controlling the repetition of HANDOVER REQUIRED.
Mandatory rules T7 < T_HO_REQD_LOST
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Supervision of the External Handover procedure in the serving BSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the SCCP connection release procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the Channel Activation procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the call clearing procedure when triggered by the BSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the SCCP Connection procedure.
n Max value 6553,5 Coded Max 65535
Mandatory rules T9105 > T(conn est)
Recommended T9105 > max T3210. T9105 > max T3220. T9105 > max T3230
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the Physical Context procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Guards the response of the MSC when no resources are allocated to the SCCP connection (started on the reception of CONN_IND(SCCP_CON_REQ) not carrying a
HANDOVER REQUEST message and stopped when a HANDOVER REQUEST message is received on the same SCCP connection as the SCCP_CON_REQ message).
Guards also the response of the MSC when a HANDOVER FAILURE or ASSIGNMENT FAILURE message has been sent (stopped when a HANDOVER REQUEST or
CLEAR COMMAND message is received).
Mandatory rules --
Recommended T9110 << max [T(ias), T(iar)].

rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the channel modification in the MS.
Spec ref. Channel modification Coded Max 65535
Mandatory rules --
Recommended T9112 >= 15s. T9112 <= T9114. T9112 is inferior to the MSC timer supervising the Modify procedure.
rules
External --
comment
Internal comment --
name TRX nb No
Definition Supervision of the External Handover procedure in the target BSC.
Mandatory rules T9113 > T3105_D x Ny1. T9113 > T3105_F x Ny1. T9113 > T3106_D. T9113 > T3106_F
Recommended --
rules
External --
comment
Internal comment --
Logical TA_STAT B11 Yes B12 Yes
name TRX nb No
HMI TA_STAT Sub-syste BSC Cell Type No
Definition Threshold on timing advance to define the cell limit used for Radio Measurements Statistics.
Coding rules --
Mandatory rules --
Recommended --
rules
External 1 bper corresponds to about 550m
comment
Internal comment --
Logical TCH_INFO_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI TCH_INFO_PERIOD Sub-syste BSC Cell Type No
Definition Periodicity of TCH usage information update in the BSC.
Coding rules stepsize = 0.1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TCH_TS_ACTIVITY_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI TCH_TS_ACTIVITY_FACTOR Sub-syste
BSC Cell Type No
name Instance
Abis segment RMS No
Definition Maximum percentage of RTSs supporting some TCH(s) at the same time (one FR TCH or two HR TCHs), among all the RTSs configured as TCH or configured as dynamic
SDCCH.
The RTSs supporting only one HR TCH are counted as half a RTS.
Allows to perform a radio over-dimensioning in case < 100%.
Coding rules Step size = 1%
Mandatory rules In case of a BTS with several Abis/E1 links, TCH_TS_ACTIVITY_FACTOR shall take the same value on each link.
Recommended Shall be set to a value high enough to ensure that CS traffic will (nearly) never be limited because of this constraint. The ABIS_BANDWIDTH shall be dimensioned in
rules proportion.
In addition, if GPRS is activated in some cells of the Abis BTS group, it is highly recommended to avoid configurations where the reserved PS bandwidth is very low
or null. This can indeed imply risks of PS traffic blocking situation in the Abis BTS group due to lack of Abis bandwidth, or risks of PMU-PTU interface traffic
congestion, or risks of IPGCH control traffic congestion.
External --
comment
Internal comment --
Logical TCP_KEEP_ALIVE_CNT (BSC) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_CNT Sub-syste BSC Cell Type No
Definition Number of TCP keep-alive messages sent by the IPGSL (or TCSL) and not acknowledged by the peer before triggering a TCP disconnection
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_CNT (MFS) and TCP_ KEEP_ALIVE_CNT (TC)

rules
External --
comment
Internal comment - TCP_KEEP_ALIVE_CNT (TC) is defined in BOP
- applied to OMCP and CCP boards
Logical TCP_KEEP_ALIVE_IDLE (BSC) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_IDLE Sub-syste BSC Cell Type No
Definition IPGSL (and TCSL) link supervision: Time to wait before sending the first TCP keep alive message.
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_IDLE (BSC) and TCP_KEEP_ALIVE_IDLE (TC)

rules
External --
comment
Internal comment - TCP_KEEP_ALIVE_IDLE (TC) is defined in BOP
Logical TCP_KEEP_ALIVE_INTVL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_INTVL Sub-syste BSC Cell Type No
Definition Time between the sending of two TCP keep-alive messages by IPGSL and TCSL.
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_INTVL (MFS) and TCP_KEEP_ALIVE_INTVL (TC)

rules
External --
comment
Internal comment - TCP_KEEP_ALIVE_INTVL (TC) is defined in BOP
Logical TCP_MAX_RETRANS (BSC) B11 Yes B12 Yes
name TRX nb No
HMI TCP_MAX_RETRANS Sub-syste
BSC Cell Type No
name Instance
BSC RMS No
Definition Maximum number of times a TCP segment (used by IPGSL or TCSL) is resent by the BSC before to raise a TCP time-out error.
0 means no retransmission
Mandatory rules --
Recommended 1) TCP_MAX_RETRANS(BSC) should be set to a value in order that TCP reset (Abort interval) will apply before T_GSL_ACK (BSC) expiry. If this is not the case,
rules BSCGP layer will resend unnecessarily to TCP layer too many not acknowledged messages.
2) TCP_MAX_RETRANS(BSC) should be set to a value in order that TCP reset (Abort interval) will apply before T_TCSL_ACK (BSC) (defined in BOP) expiry. If this is
not the case, TCSL layer will resend unnecessarily to TCP layer too many not acknowledged messages.
3) TCP_MAX_RETRANS (BSC) should be set to a value in order that TCP reset (Abort interval) is shorter than the GP recovery time (34sec).
External The purpose of the 1st and 2nd recommended rule is to ensure that failure at TCP level will be detected before failure at BSCGP or TCSL level. For example, if a global
comment failure happens during a TCP transfer in which the failed connection side was the data receiver, the sending TCP will try to retransmit the non-acknowledged data
segments, but TCP will limit the number of retransmissions by means of this parameter. On expiry, TCP resets the connection (RST segment).
The purpose of the 3rd rule is to ensure that the CCP will be able to reopen the TCP connection at the end of the GP restart.
Internal comment - Exponential back off applied by the TCP stack of the BSC (used by IPGSL and TCSL) before each resend of TCP segment.
- The same parameter value is used by CCP for IPGSL and by OMCP for TCSL.
Logical TCP_MSL (BSC) B11 Yes B12 Yes
name TRX nb No
HMI TCP_MSL (BSC) Sub-syste BSC Cell Type No
Definition TCP message segment lifetime, used by IPGSL (and TCSL).
Mandatory rules --
Recommended TCP_MSL (BSC) = TCP_MSL (MFS)

rules
External --
comment
Internal comment - hardcoded in the kernel
- TCP-MSL (TC) is defined in BOP
Logical TDD_ARFCN_LIST B11 Yes B12 Yes
name TRX nb No
HMI TDD_ARFCN_LIST Sub-syste BSC Cell Type No
Definition List of neighbour Downlink TDD UTRAN Absolute Radio Frequency Channel Numbers (UARFCNs) of any 3G TDD neighbor cell (TD-SCDMA), adjacent to the BSS.
Up to 3 TDD UARFCNs can be defined in the list. This list is used for 2G to 3G cell reselection (blind search method).
Coding rules The value of -1 is for implementation purpose only; this dummy value indicates that the operator does not provide any UARFCN.
Mandatory rules - The UARFCNs defined in the list (i.e. not set to 1) shall be different from each other.
- Only following downlink TDD UARFCN ranges are standardised :
a) 9504-9596 and 10054-10121
b) 9254-9546 and 9654-9946
c) 9554-9646
d) 12854-13096
e) 11504-11996
f) 9404-9596
Recommended --
rules
External - The TDD UARFCNs are used on the Air interface.
comment - The TDD UARFCNs of the 3G neighbour cells are broadcast on BCCH.
- Significant only if EN_2G_TO_3GTDD_CELL_RESELECTION is not disabled
Internal comment The 3 UARFCNs form a table with the 3 following values TDD_ARFCN[I] for I = 1,,3.
The OMC always sends to the BSC precisely 3 values for this list, including the dummy ones, if any, at the end of the list.
Logical TDD_Qoffset B11 Yes B12 Yes
name TRX nb No
HMI TDD_Qoffset Sub-syste BSC Cell Type No
Definition Offset added to the received level average of the serving cell and of the neighbour GSM
cells for UTRAN TDD cell re-selection.
1: -28: -28 dB
2: -24: -24 dB
3: -20: -20 dB
4: -16: -16 dB
5: -12: -12 dB
6: -8: -8 dB
7: -4: -4 dB
8: 0: 0 dB
9: 4: 4 dB
10: 8: 8 dB
11: 12: 12 dB
12: 16: 16 dB
13: 20: 20 dB
14: 24: 24 dB
15: 28: 28 dB
Mandatory rules --
Recommended --
rules
External This parameter is broadcast on BCCH.
comment
Logical TEMPORARY_OFFSET B11 Yes B12 Yes
name TRX nb No
HMI TEMPORARY_OFFSET Sub-syste BSC Cell Type Yes
Definition Offset applied to C2 criterion for the duration of PENALTY_TIME.
n Max value infinity Coded Max 7
Coding rules step size = 10dB. 0: 0dB, 1:10dB, 6: 60dB, 7: infinity
Mandatory rules --
Recommended --
rules
External If the VGCS is licensed, the parameter is modifiable only via the provisioning context of the OMC.
comment
Logical TEMPORARY_OFFSET(n) B11 Yes B12 Yes
name TRX nb No
HMI TEMPORARY_OFFSET Sub-syste BSC Cell Type Yes
Definition Offset applied to C2 criterion for the duration of PENALTY_TIME.
Coding rules step size = 10dB. 0: 0dB, 1:10dB, 6: 60dB, 7: infinity
Mandatory rules --
Recommended --
rules
External --
comment
Logical THR_CCCH_LOAD B11 Yes B12 Yes
name TRX nb No
HMI THR_CCCH_LOAD Sub-syste BSC Cell Type No
Definition Threshold triggering the sending of CCCH LOAD INDICATION message.
Category Site (CAE) OMC-R access Displayed Type Threshold Unit %
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Percentage of busy to successful accesses. Transmitted to the BTS in the BTS_CONF_DATA message
Logical THR_CELL_LOAD_3G_REJECT B11 Yes B12 Yes
name TRX nb No
HMI THR_CELL_LOAD_3G_REJECT Sub-syste BSC Cell Type No
Definition Load threshold determining whether a 3G to 2G handover request shall be rejected in load situation; the feature is deactivated by setting THR_CELL_LOAD_3G_REJECT
to its maximum value 100%.
Mandatory rules THR_CELL_LOAD_3G_REJECT shall be lower than the 2G load thresholds HIGH_TRAFFIC_LOAD or equal to 100%.
Recommended --
rules
External --
comment
Internal comment --
Logical THR_CELL_LOAD_3G_REQ B11 Yes B12 Yes
name TRX nb No
HMI THR_CELL_LOAD_3G_REQ Sub-syste BSC Cell Type No
Definition Load threshold on the serving cell below which handovers towards 3G cells are forbidden when I.E. Service Handover is missing (whatever
EN_2G_3G_HO_NO_SERVICE_HO value)
Mandatory rules --
Recommended --
rules
External Value 0 disables the feature.
comment
Internal comment --
Logical THR_CELL_LOAD_LTE_REJECT B11 No B12 Yes
name TRX nb No
HMI THR_CELL_LOAD_LTE_REJECT Sub-syste BSC Cell Type No
Definition Load threshold determining whether a LTE to 2G handover request shall be rejected in load situation; the feature is deactivated by setting THR_CELL_LOAD_LTE_REJECT
to its maximum value 100%.
Mandatory rules THR_CELL_LOAD_LTE_REJECT shall be lower than the 2G load thresholds HIGH_TRAFFIC_LOAD or equal to 100%.
Recommended --
rules
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied on new handovers procedures initiated after modification.
Internal comment - to activate the feature, SAI_LTE shall also be configured
Logical THR_ECNO_HO B11 Yes B12 Yes
name TRX nb No
HMI THR_ECNO_HO Sub-syste BSC Cell Type No
Definition Ec/No threshold above which a handover to UTRAN may be triggered
Rec ref. None Domai 2G-3G Min value -24.5 Coded Min 0
Coding rules step size = 0.5 dB, coded over 6 bits
0: HO to 3G attempted whatever the Ec/No,
1: -24.0,
2: -23.5,
3: -23,
...,
48: -0.5,
49: 0.0
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical THR_FR_LOAD_L_SV1 B11 Yes B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_L_SV1 Sub-syste BSC Cell Type No
Definition Lower load threshold for allocation policy with HR or AMR-NB HR codec type in a dual rate cell.
Mandatory rules - THR_FR_LOAD_L_SV1 <= THR_FR_LOAD_U_SV1

- THR_FR_LOAD_L_SV3 <= THR_FR_LOAD_L_SV1
Recommended When choosing the THR_FR_LOAD_L_SV1 value, it is recommended to check that the number of DR TCH in the cell is greater than (100 - THR_FR_LOAD_L_SV1)
rules /100*total number of TCH in the cell.
External --
comment
Internal comment --
Logical THR_FR_LOAD_L_SV3 B11 Yes B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_L_SV3 Sub-syste BSC Cell Type No
Definition Lower load threshold for allocation policy with AMR-NB HR codec type and for AMR-NB channel adaptation handover (Cause 26 and Cause 27) in a dual rate cell.

- THR_FR_LOAD_L_SV3 <= THR_FR_LOAD_L_SV1
- THR_FR_LOAD_L_SV3 <= THR_FR_LOAD_L_VAMOS_HR
Recommended When choosing the THR_FR_LOAD_L_SV3 value, it is recommended to check that the number of DR TCH in the cell is greater than (100 - THR_FR_LOAD_L_SV3)
External --
comment
Internal comment --
Logical THR_FR_LOAD_L_VAMOS_FR B11 No B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_L_VAMOS_FR Sub-syste
BSC Cell Type No
Definition Lower load threshold for allocation policy with a VAMOS Full Rate sub-channel (FR, EFR, AMR-NB FR or AMR-WB FR codec type).
Mandatory rules - THR_FR_LOAD_L_VAMOS_FR <= THR_FR_LOAD_U_VAMOS_FR

- THR_FR_LOAD_L_VAMOS_FR <= THR_FR_LOAD_L_VAMOS_HR
Recommended --
rules
Internal comment --
Logical THR_FR_LOAD_L_VAMOS_HR B11 No B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_L_VAMOS_HR Sub-syste
BSC Cell Type No
Definition Lower load threshold for allocation policy with a VAMOS Half Rate sub-channel (HR or AMR-NB HR codec type) in a dual rate cell.
Mandatory rules - THR_FR_LOAD_L_VAMOS_HR <= THR_FR_LOAD_U_VAMOS_HR

- THR_FR_LOAD_L_VAMOS_FR <= THR_FR_LOAD_L_VAMOS_HR
- THR_FR_LOAD_L_SV3 <= THR_FR_LOAD_L_VAMOS_HR
Recommended --
rules
Internal comment --
Logical THR_FR_LOAD_U_SV1 B11 Yes B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_U_SV1 Sub-syste BSC Cell Type No
Definition Higher load threshold for allocation policy with HR or AMR-NB HR codec type in a dual rate cell.

- THR_FR_LOAD_U_SV3 <= THR_FR_LOAD_U_SV1
Recommended When choosing the THR_FR_LOAD_U_SV1 value, it is recommended to check that the number of DR TCH in the cell is greater than (100 - THR_FR_LOAD_U_SV1)
External --
comment
Internal comment --
Logical THR_FR_LOAD_U_SV3 B11 Yes B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_U_SV3 Sub-syste BSC Cell Type No
Definition Higher load threshold for allocation policy with AMR-NB HR codec type and for AMR-NB channel adaptation handover (Cause 26 and Cause 27) in a dual rate cell.

- THR_FR_LOAD_U_SV3 <= THR_FR_LOAD_U_SV1
- THR_FR_LOAD_U_SV3 <= THR_FR_LOAD_U_VAMOS_HR
Recommended When choosing the THR_FR_LOAD_U_SV3 value, it is recommended to check that the number of DR TCH in the cell is greater than (100 - THR_FR_LOAD_U_SV3)
External --
comment
Internal comment --
Logical THR_FR_LOAD_U_VAMOS_FR B11 No B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_U_VAMOS_FR Sub-systeBSC Cell Type No
Definition Higher load threshold for allocation policy with a VAMOS Full Rate sub-channel (FR, EFR, AMR-NB FR or AMR-WB FR codec type).
Mandatory rules - THR_FR_LOAD_L_VAMOS_FR <= THR_FR_LOAD_U_VAMOS_FR

- THR_FR_LOAD_U_VAMOS_FR <= THR_FR_LOAD_U_VAMOS_HR
Recommended --
rules
Internal comment --
Logical THR_FR_LOAD_U_VAMOS_HR B11 No B12 Yes
name TRX nb Yes
HMI THR_FR_LOAD_U_VAMOS_HR Sub-syste
BSC Cell Type No
Definition Higher load threshold for allocation policy with a VAMOS Half Rate sub-channel (HR or AMR-NB HR codec type) in a dual rate cell.
Mandatory rules - THR_FR_LOAD_L_VAMOS_HR <= THR_FR_LOAD_U_VAMOS_HR

- THR_FR_LOAD_U_VAMOS_FR <= THR_FR_LOAD_U_VAMOS_HR
- THR_FR_LOAD_U_SV3 <= THR_FR_LOAD_U_VAMOS_HR
Recommended --
rules
Internal comment --
Logical THR_LB_OV B11 Yes B12 Yes
name TRX nb No
HMI THR_LB_OV Sub-syste BSC Cell Type No
Definition Counter threshold for triggering global defence actions in the BSC upon FU overload.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical THR_MARGIN_PRIO_PS B11 Yes B12 Yes
name TRX nb No
HMI THR_MARGIN_PRIO_PS Sub-syste BSC Cell Type No
Definition Margin of radio timeslots reserved for PS traffic between two sendings of the BSCGP RR Allocation Indication messages. The threshold is expressed in percentage of
radio timeslots.
This margin only applies in case of high CS load and low PS load.
Category System (CST) OMC-R access None (DLS) Type Number Unit %
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical THR_RXQUAL_CA_HIGH B11 Yes B12 Yes
name TRX nb No
HMI THR_RXQUAL_CA_HIGH Sub-syste BSC Cell Type No
Definition Threshold for AMR-NB channel adaptation handover under high load (Cause 26 and Cause 27).
Mandatory rules THR_RXQUAL_CA_HIGH >= THR_RXQUAL_CA_NORMAL
Recommended --
rules
External --
comment
Internal comment --
Logical THR_RXQUAL_CA_NORMAL B11 Yes B12 Yes
name TRX nb No
HMI THR_RXQUAL_CA_NORMAL Sub-syste BSC Cell Type No
Definition Threshold for AMR-NB channel adaptation handover under normal load (Cause 26 and Cause 27).
Mandatory rules THR_RXQUAL_CA_HIGH >= THR_RXQUAL_CA_NORMAL
Recommended --
rules
External --
comment
Internal comment --
Logical THRESH_2G_LOW B11 Yes B12 Yes
name TRX nb No
HMI THRESH_2G_LOW Sub-syste BSC Cell Type No
Definition Gives the threshold of the GSM serving cell (and all measured GSM cells). Used in the priority algorithm for cell reselection by a LTE-capable MS/UE.
Coding rules step size = 2 dB
Coded value (decimal): Value (dB): Text displayed at the OMC
0: 0: 0 dB
1: 2: 2 dB
2: 4: 4 dB
3: 6: 6 dB
4: 8: 8 dB
5: 10: 10 dB
6: 12: 12 dB
7: 14: 14 dB
8: 16: 16 dB
9: 18: 18 dB
10: 20: 20 dB
11: 22: 22 dB
12: 24: 24 dB
13: 26: 26 dB
14: 28: 28 dB
15: 30: always select a LTE cell is possible
Mandatory rules --
Recommended --
rules
Internal comment --
Logical THRESH_3G_HIGH m B11 Yes B12 Yes

name TRX nb No
HMI THRESH_3G_HIGH Sub-syste BSC template Cell Type No
Definition Threshold (high) associated to a given UARFCN explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Coding rules Coded_value = dB / 2, step size = 2
Mandatory rules - All 3G cells managed by the OMC (and neighbour to a BSC Evolution) having the same ARFCN_3G shall be given the same THRESH_3G_HIGH value (to be checked
on a per RAT basis).
- THRESH_3G_LOW <= THRESH_3G_HIGH
Recommended --
rules
Internal comment - The first mandatory rule has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
Logical THRESH_3G_LOW B11 Yes B12 Yes
name TRX nb No
HMI THRESH_3G_LOW Sub-syste BSC Cell Type No
Definition Threshold (low) associated to a given UARFCN explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Coding rules Coded_value = dB / 2, step size = 2
Mandatory rules - All 3G cells managed by the OMC (and neighbour to a BSC Evolution) having the same ARFCN_3G shall be given the same THRESH_3G_LOW value (to be checked at
Network level and on a per RAT basis).
- THRESH_3G_LOW <= THRESH_3G_HIGH
Recommended --
rules
Internal comment - The first mandatory rule has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
Logical THRESH_LTE_HIGH B11 Yes B12 Yes
name TRX nb No
HMI THRESH_LTE_HIGH Sub-syste BSC Cell Type No
Definition Threshold (high) associated to a given EUARFCN explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Mandatory rules - All LTE cells managed by the OMC having the same ARFCN_LTE shall be given the same THRESH_LTE_HIGH value (to be checked on a per RAT basis).
- THRESH_LTE_LOW <= THRESH_LTE_HIGH
Recommended --
rules
Internal comment --
Logical THRESH_LTE_LOW B11 Yes B12 Yes
name TRX nb No
HMI THRESH_LTE_LOW Sub-syste BSC Cell Type No
Definition Threshold (low) associated to a given EUARFCN explicitly broadcasted by the BSS. Used for cell reselection by a LTE-capable MS/UE.
Mandatory rules - All LTE cells managed by the OMC having the same ARFCN_LTE shall be given the same THRESH_LTE_LOW value (to be checked on a per RAT basis).
- THRESH_LTE_LOW <= THRESH_LTE_HIGH
Recommended --
rules
Internal comment --
Logical THRESH_PRIORITY_SEARCH B11 Yes B12 Yes
name TRX nb No
HMI THRESH_PRIORITY_SEARCH Sub-syste BSC Cell Type No
Definition Threshold for the serving cell that controls inter-RAT measurements. Used for cell reselection by a LTE-capable MS/UE.
Coding rules step size = 3 dBm
Coded value (decimal): Value (dBm): Text displayed at the OMC
0: -98: -98 dBm
1: -95: -95 dBm
2: -92: -92 dBm
3: -89: -89 dBm
4: -86: -86 dBm
5: -83: -83 dBm
6: -80: -80 dBm
7: -77: -77 dBm
8: -74: -74 dBm
9: -71: -71 dBm
10: -68: -68 dBm
11: -65: -65 dBm
12: -62: -62 dBm
13: -59: -59 dBm
14: -56: -56 dBm
15: -53: Always
Mandatory rules --
Recommended --
rules
Internal comment --
Logical THRESHOLD_1_0 m B11 Yes B12 Yes

name TRX nb No
HMI THRESHOLD_1_0 Sub-syste BSC template Cell Type No
Definition Free buffer thresholds separating no overload condition and overload level 1 condition when pointer P points at position 0.
Coding rules --
Mandatory rules THRESHOLD_1_0 >= THRESHOLD_2_0
Recommended --
rules
External --
comment
Internal comment --
Logical THRESHOLD_1_1 B11 Yes B12 Yes
name TRX nb No
HMI THRESHOLD_1_1 Sub-syste BSC Cell Type No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Free buffer thresholds separating overload level 1 condition and overload level 2 condition when pointer P points at position 0.
Coding rules --
Mandatory rules THRESHOLD_2_0 <= THRESHOLD_1_0
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TL_TCUA B11 Yes B12 Yes
name TRX nb No
HMI TL_TCUA Sub-syste BSC Cell Type No
Definition Minimum delay between two consecutive TCU load increaseby the local overload controller.
Mandatory rules TL_TCUA >TS_TCUA
Recommended --
rules
External --
comment
Internal comment --
Logical TL0 B11 Yes B12 Yes
name TRX nb No
HMI TL0 Sub-syste BSC Cell Type No
Definition Threshold on TCU Processor Occupancy Level. The TCU is in "Low Overload" state if its Processor Occupancy Level is higher or equal to TL0 and less than TL3." The
TCU is in "No Overload" state if its Processor Occupancy Level is less than TL0.
Spec ref. Overload Control Coded Max 100
Coding rules --
Mandatory rules TL0 < TL3 < TL4
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition BSC processor occupancy threshold used to decrement pointer P on buffer occupancy thresholds.
Coding rules --
Mandatory rules TL1 < TL2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition BSC processor occupancy threshold used to increment pointer P on buffer occupancy thresholds.
Coding rules --
Mandatory rules TL3 > TL4
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Threshold on TCU Processor Occupancy Level:
1) In upward direction, the TCU Overload State is in High Overload state if TL3 <= TCU Processor Occupancy Level < TL4;
2) In downward direction, the TCU Overload State is still in Very High Overload State if TL3 <= TCU Processor Occupancy Level < TL4;
3) In downward direction, the TCU Overload State is in Low Overload state if TL0 <= TCU Processor Occupancy Level < TL3.
Coding rules --
Mandatory rules T0 < TL3 < TL4
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Threshold on TCU Processor Occupancy Level. The TCU is in Very High Overload state if its Processor Occupancy Level is higher or equal to TL4.
Coding rules --
Mandatory rules TL4 > TL3 > TL0
Recommended --
rules
External --
comment
Internal comment --
Logical TP_QUEUE0_WEIGHT B11 Yes B12 Yes
name TRX nb No
HMI TP_QUEUE0_WEIGHT Sub-syste BSC Cell Type No
Definition Weight used by the weighted round robin algorithm to handle the TP queue 0.
Mandatory rules --
Recommended --
rules
External The weight gives the number of packets that are sent from this queue every round over the queue before next queue is scheduled. This is the lowest priority queue.
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External The weight gives the number of packets that are sent from this queue every round over the queue before next queue is scheduled.
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External The weight gives the number of packets that are sent from this queue every round over the queue before next queue is scheduled.
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External Queue 3 is the highest priority queue. It handles only the NE1oE internal traffic (strong time synchronization constraints linked to the NE1oE protocol). The weight gives
comment the number of packets that are sent from this queue every round over the queue before next queue is scheduled.
Internal comment --
Logical TRAFFIC_MODE B11 Yes B12 Yes
name TRX nb No
HMI TRAFFIC_MODE Sub-syste BSC Cell Type No
Definition Traffic mode of the MSC server.
- When the MSC TRAFFIC_MODE is in load sharing, the number of SCTP endpoints configured in the ASIG_SCTP_ENDPOINT_LIST must be equal or greater than
MIN_NB_ACTIVE_IPSP
Recommended --
rules
comment - The broadcast mode is not supported by the BSS.
- Parameter change: Before any modification of the TRAFFIC_MODE, If the Aflex feature is enabled, Alcatel-Lucent recommends to firstly set the concerned MSC into
the "off loaded" state in order to redirect the new traffic towards other MSCs. Then, the operator must lock all the A Signalling Links (ASL) of the modified MSC. Under
some circumstances (e.g. that MSC is the only MSC still operational, ie in IT or FIT, state among all the MSCs connected to a BSC), the BSS-TEL is to be previously
locked too. This procedure leads the BSC to reject any new calls and wait for some minutes (Wait Traffic Clear) before shutting down the on going calls. After
modification of the TRAFFIC_MODE, an OMCP takeover must be performed by reset of the active board, the locked objects must be unlocked and be "on loaded" again
to reopen the telecom service.
Internal comment --
Logical TRAU_CONNECTION_TIMEOUT B11 Yes B12 Yes
name TRX nb No
HMI TRAU_CONNECTION_TIMEOUT Sub-syste BSC Cell Type No
Definition Waiting time to detect loss of synchronisation between BTS and TC in case of IP transport.
Mandatory rules --
Recommended --
rules
External --
comment
- Range ensures that TRAU_Activity_Timer <= TRAU_Connection_Timeout. when TRAU_Connection_Timeout = TRAU_Activity_Timer; only the mechanism linked to
TRAU_Connection_Timeout is used
Logical TRBSS B11 No B12 Yes
name TRX nb No
HMI TRBSS Sub-syste BSC Cell Type No
Definition Supervision of the RESET IP RESOURCE procedure, initiated at the BSC.
When no response is received from the MSC, the RESET IP RESOURCE message is repeated.
Spec ref. Reset Circuit/IP resource & Blocking Coded Max 255
Mandatory rules --
Recommended --
rules
External - Parameter change: No impact on the telecom service, on going calls are not disrupted.
comment
Internal comment --
Logical Treassembly B11 Yes B12 Yes
name TRX nb No
HMI Treassembly Sub-syste BSC Cell Type No
Definition Timer controlling the reception of subsequent segments after reception of the first segment of a segmented layer 3 message.
Rec ref. Q714 Domai GSM Min value 10 Coded Min 100
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Treassembly < T9110 (the rule is checked neither by BSC nor by the OMC.)
Logical TRG_SDCCH B11 Yes B12 Yes
name TRX nb No
HMI TRG_SDCCH Sub-syste BSC Cell Type No
name Instance BSC proc RMS No
Definition Controls if local overload controller is triggered upon SDCCH overload.
Coding rules 1 for TCU, 0 for others
Mandatory rules --
Recommended --
rules
External This parameter is set by default to 1 for TCUs. It shall be set to 0 for other BSC processors
comment
Internal comment --
Logical TRX_CIPH_CAP B11 Yes B12 Yes
name TRX nb No
HMI TRX_CIPH_CAP Sub-syste BSC Cell Type No
Definition Indicates the ciphering algorithms supported by the TRX in TDM mode and in IP mode.
Category Site (CAE) OMC-R access Virtual displayed Type Bitmap Unit None
Coding rules The first byte indicates the ciphering capability in TDM mode.
The second byte indicates the ciphering capability in IP mode.
Each byte is coded as a 8 bits bitmap. Each bit indicates if corresponding encryption algorithm is permitted.
Bit x='0' : encryption algorithm not supported

Bit x='1' : encryption algorithm supported
bit 0 : A5/0 (no ciphering)

bit 1 : A5/1.
bit 2 : A5/2
bit 3 : A5/3
bit 4 : A5/4

bit 7 : A5/7.
Mandatory rules The possible values for each byte are :

- A5/0 + A5/1
- A5/0 + A5/1 +A5/3
Recommended --
rules
External A5/2 is not supported by the BSS.
comment Default value depends on configuration. The value indicated here (A5/0 + A5/1 for both mode) is for implementation purposes.
Internal comment Bits 4 to 7 shall not be displayed at the OMC.
A5/3 is not supported by G3 TRE.
The value is retrieved from the TRE_CIPH_CAP parameter, defined in BOP
Logical TRX_DATA_TIMER B11 Yes B12 Yes
name TRX nb No
HMI TRX_DATA_TIMER Sub-syste BSC Cell Type No
Definition Timer supervision the reception by the BSC of the TRX_COUNTER_REPORT message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TRX_PREF_MARK B11 Yes B12 Yes
name TRX nb No
HMI Preference Mark Sub-syste BSC Cell Type No
Definition Preference mark assigned to a given TRX.
Coding rules 0: PS/CS TRX: This TRX can carry PS and CS traffic and has the lowest preference in the TCH sub-channel selection process used to serve a CS call.
1: CS TRX with preference mark 1: This TRX can carry only CS traffic and has the preference mark 1 in the TCH sub-channel selection process used to serve a CS
call.

7: CS TRX with preference mark 7: This TRX can carry only CS traffic and has the highest preference in the TCH sub-channel selection process used to served a CS
call. It means that this TRX has the highest priority for CS traffic.
Mandatory rules 1) For a TRX in the inner zone of a monoband or multiband concentric cell, the parameter TRX_PREF_MARK shall be set to a non-null value.
2) For a hopping G1 TRX, if EGSM_RR_ALLOC_STRATEGY = 0 and BCCH/CCCH are configured on PGSM TRX, then TRX_PREF_MARK <> 0
iii) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX.
iv) MAX_PDCH <= 8*(nb of TRXs with TRX_PREF_MARK = 0) - 3 if TRX_PREF_MARK = 0 on BCCH TRX and CCCH_CONF = 2
4) In case of cell shared over 2 BTSs, the GPRS TRXs of the cell (ie TRX_PREF_MARK=0) can be either on the main sector or on the secondary, but not on both.
5) the maximum number of PS capable TRX (ie TRX_PREF_MARK = 0) defined in one cell is 16.
Recommended - Alcatel-Lucent recommends to set TRX_PREF_MARK > 0 (ie no PS traffic) on the BCCH TRX of the cell where CCCH_CONF = 6, otherwise only one timeslot is
rules reserved for PS traffic on that TRX.
External If EGPRS is activated in the cell, TRX_PREF_MARK (BCCH TRX) = 0 and the BCCH TRX is associated to a TRE hardware and a transmission pool allowing the usage of
comment 8-PSK, the operator shall ensure that the difference in the mean output powers between GSMK and 8-PSK signals is less than 2 dB in order to be compliant with
3GPP TS 05.05 and 3GPP TS 05.08 requirements (or 4 dB if an SDCCH timeslot is defined in timeslot number 7 of the BCCH TRX).
Internal comment --
Logical TS_TCUA m B11 Yes B12 Yes

name TRX nb No
HMI TS_TCUA Sub-syste BSC template Cell Type No
Definition Minimum delay between two consecutive TCU load reduction by the local overload controller.
Mandatory rules TS_TCUA < TL_TCUA
Recommended --
rules
External --
comment
Internal comment --
Logical TSC B11 Yes B12 Yes
name TRX nb No
HMI TSC Sub-syste BSC Cell Type No
Definition Training Sequence Code for:
- any packet channel (when EN_VAMOS enabled or not in the cell), and
- any circuit channel (when EN_VAMOS disabled in the cell)
- except for common control channels (BCCH, CCCH and CBCH).
Mandatory rules --
Recommended --
rules
comment - Several training sequence codes (TSCO) are used in Alcatel-Lucent BSS:
*) TSCO for BCCH, CCCH and CBCH: the BSS sets the O&M parameter BCC. This behaviour is compliant to 3GPP TS 05.02 which states that for BCCH and CCCH, the
TSCO must be equal to the BCC. In Alcatel-Lucent BSS, for CBCH, the TSCO is also set to BCC.
**) TSCO for any packet channel: the BSS sets the O&M parameter TSC.
***) TSCO for any circuit channel: when EN_VAMOS is enabled, the BSS uses either TSC_1 or TSC_2 of the O&M parameter TSC_1_2; when disabled, the BSS sets
the O&M paramtere TSC.
Internal comment When EN_VAMOS is enabled, TSC_1 and TSC_2 of TSC_1_2 are used instead for circuit channel.
Logical TSC_1_2 B11 No B12 Yes
name TRX nb No
HMI TSC_1_2 Sub-syste BSC Cell Type No
Definition When VAMOS (Voice services over Adaptive Multi-user channels on One Slot) is enabled in the cell, this parameter represents the two Training Sequence Codes, TSC_1
and TSC_2, allowed in the cell for any circuit channel established in VAMOS mode; TSC_1 being used when established in Non-VAMOS mode..
Coding rules The allowed (TSC_1, TSC_2) values are coded as following:
0: (0, 2)
1: (1, 3)
2: (2, 1)
3: (3, 0)
4: (4, 3)
5: (5, 0)
6: (6, 3)
7: (7, 0)
8 to 15: reserved
Mandatory rules --
Recommended For a legacy behavior on circuit channel established in Non-VAMOS mode, in cell where EN_VAMOS has been activated, Alcatel-Lucent recommends initializing
rules TSC_1_2 with a value where TSC_1 equals the current TSC value.
Internal comment TSC_1 can be either from the legacy TSC Set 1 or from the new TSC Set 2.
On VAMOS sub-channel#2: TSC_2 from TSC Set1 is used only in case of (legacy SAIC, legacy SAIC) VAMOS pair, else TSC_1 or TSC_2 belonging to TSC Set2 is
used.
On VAMOS sub-channel#1:TSC_1 or TSC_2 belonging to TSC Set1 is used.
Logical TSTD_3G_TDD B11 Yes B12 Yes
name TRX nb No
HMI TSTD_3G_TDD Sub-syste BSC Cell Type No
Definition The parameter indicates if the Time Switched Transmit Diversity (TSTD bit) is applied in an external 3G TDD cell.
Coding rules 1 bit:
0 TSTD is not applied,
1 TSTD is applied
Mandatory rules --
Recommended --
rules
Logical Tx_integer (BSC) B11 Yes B12 Yes
name TRX nb No
HMI TX_INTEGER Sub-syste BSC Cell Type No
Definition Number of RACH timeslots that spread transmission of CHANNEL REQUEST.
Coding rules Possible values are:3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 25, 32, 50 respectively binary coded from 0000 to 1111
Mandatory rules Equal to Tx_integer (MFS)
Recommended When the GPRS is supported through Abis or Ater terrestrial links, it is recommended to set:
rules TX_INTEGER = 32 if the CCCH is not combined, i.e. CCCH_CONF <> 1
TX_INTEGER = 12 if the CCCH is combined, i.e. CCCH_CONF = 1.
When the GPRS is supported through Abis or Ater satellite links, it is recommended to set:
TX_INTEGER = 32 whatever the configuration of the CCCH.
The number of slots belonging to the MSs RACH between 2 successive Channel Request messages is a random value drawn randomly for each new retransmission
with uniform distribution in the set (S, S+1, ...,S+T-1). With T = Tx_Integer and S depending on the CCCH configuration as shown below:
1) for non combined CCCH:

- Tx_Integer = 3, 8, 14, 50 --> S = 55 RACH frames (i.e. 253.8 ms)
- Tx_Integer = 4, 9, 16 --> S = 76 RACH frames (i.e. 349.6 ms)
Tx_Integer = 7, 12, 32 --> S = 217 RACH frames (i.e. 998.2 ms)
2) for combined CCCH:

Note:
m
External When EN_GPRS=1, it is recommended to set: template
comment TX_INTEGER = 32 if the CCCH is not combined, i.e. CCCH_CONF <> 1
TX_INTEGER = 12 if the CCCH is combined, i.e. CCCH_CONF = 1
Internal comment For more details on the setting of this parameter, refer to the memo MND/TD/SYT/EBR/0497.2001.
Logical U_RXLEV_DL_MCHO B11 Yes B12 Yes

name TRX nb No
HMI U_RXLEV_DL_MCHO Sub-syste BSC Cell Type Yes
Definition Downlink level threshold for Microcell to Macrocell handover.
Rec ref. None - In the non-combined CCCH configuration, there are 51 RACH frames per 51-multiframe Domai GSM Min value -110
Coded Min 0
Rec ref. None - In the combined CCCH configuration, there are 27 RACH frames per 51-multiframe. Domai GSM Min value -110
Coded Min 0
Coding rules coded over 6 bits :0: -110 dBm, 1: -109 dBm...63: -47 dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical U_RXLEV_DL_P B11 Yes B12 Yes
name TRX nb No
HMI U_RXLEV_DL_P Sub-syste BSC Cell Type No
Definition Upper downlink level threshold for power control.
Mandatory rules U_RXLEV_DL_P > L_RXLEV_DL_P
Recommended U_RXLEV_DL_P >= L_RXLEV_DL_P + 10 dB

rules
External --
comment
Internal comment --
Logical U_RXLEV_DL_P_VAMOS B11 No B12 Yes
name TRX nb No
HMI U_RXLEV_DL_P_VAMOS Sub-syste BSC Cell Type No
Definition Upper downlink level threshold for VAMOS BS power control.
Mandatory rules - L_RXLEV_DL_P_VAMOS < U_RXLEV_DL_P_VAMOS
Recommended - L_RXLEV_DL_P_VAMOS + 10 dB <= U_RXLEV_DL_P_VAMOS

rules
Internal comment --
Logical U_RXLEV_UL_MCHO B11 Yes B12 Yes
name TRX nb No
HMI U_RXLEV_UL_MCHO Sub-syste BSC Cell Type Yes
Definition Uplink level threshold for Microcell to Macrocell handover.
Mandatory rules --
Recommended --
rules
External --
comment
Logical U_RXLEV_UL_P B11 Yes B12 Yes
name TRX nb No
HMI U_RXLEV_UL_P Sub-syste BSC Cell Type Yes
Definition Upper uplink level threshold for power control.
Coding rules coded over 6 bits :0: -110 dBm, 1: -109 dBm...63: -47 dBm
Mandatory rules U_RXLEV_UL_P > L_RXLEV_UL_P
Recommended U_RXLEV_UL_P >= L_RXLEV_UL_P + 10 dB

rules
External --
comment
Logical U_RXLEV_UL_P_VAMOS B11 No B12 Yes
name TRX nb No
HMI U_RXLEV_UL_P_VAMOS Sub-syste BSC Cell Type Yes
Definition Upper downlink level threshold for VAMOS MS power control.
Mandatory rules L_RXLEV_UL_P_VAMOS < U_RXLEV_UL_P_VAMOS
Recommended U_RXLEV_UL_P_VAMOS >= L_RXLEV_UL_P_VAMOS + 10

rules
The UL RXLEV measured for each one of the two VAMOS sub-channels is the total received signal (sub-channel#1 + sub-channel#2) measured on the antenna
connector, so higher than the values measured in non-VAMOS mode
Logical U_RXQUAL_DL_P B11 Yes B12 Yes
name TRX nb No
HMI U_RXQUAL_DL_P Sub-syste BSC Cell Type No
Definition Upper downlink quality threshold for power control of any calls, except the AMR-NB or AMR-WB GMSK calls.
Mandatory rules U_RXQUAL_DL_P < L_RXQUAL_DL_P
Recommended --
rules
External Highest value is the worst quality
comment
Internal comment --
Logical U_RXQUAL_DL_P_AMR B11 No B12 Yes
name TRX nb No
HMI U_RXQUAL_DL_P_AMR Sub-syste BSC Cell Type No
Definition Upper downlink quality threshold for power control of AMR-NB or AMR-WB GMSK calls.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_DL_P_AMR < L_RXQUAL_DL_P_AMR
- U_RXQUAL_DL_P_AMR < L_RXQUAL_DL_P_AMR_RXACCH
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting U_RXQUAL_DL_P_AMR = U_RXQUAL_DL_P.
rules
Internal comment --
Logical U_RXQUAL_DL_P_AMR_VAMOS B11 No B12 Yes
name TRX nb No
HMI U_RXQUAL_DL_P_AMR_VAMOS Sub-syste BSC Cell Type No
Definition Upper downlink quality threshold for VAMOS power control of AMR-NB or AMR-WB VAMOS calls.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_DL_P_AMR_VAMOS < L_RXQUAL_DL_P_AMR_VAMOS
- U_RXQUAL_DL_P_AMR_VAMOS < L_RXQUAL_DL_P_AMR_RXACCH_VAMOS
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting U_RXQUAL_DL_P_AMR_VAMOS = U_RXQUAL_DL_P_VAMOS
rules
Internal comment --
Logical U_RXQUAL_DL_P_VAMOS B11 No B12 Yes
name TRX nb No
HMI U_RXQUAL_DL_P_VAMOS Sub-syste BSC Cell Type No
Definition Upper downlink quality threshold for VAMOS power control of any VAMOS calls, except the AMR-NB or AMR-WB ones.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_DL_P_VAMOS < L_RXQUAL_DL_P_VAMOS
Recommended --
rules
Internal comment --
Logical U_RXQUAL_UL_P B11 Yes B12 Yes
name TRX nb No
HMI U_RXQUAL_UL_P Sub-syste BSC Cell Type No
Definition Upper uplink quality threshold for power control of any calls, except the AMR-NB or AMR-WB GMSK calls.
Mandatory rules U_RXQUAL_UL_P < L_RXQUAL_UL_P
Recommended --
rules
External Highest value is the worst quality
comment
Internal comment --
Logical U_RXQUAL_UL_P_AMR B11 No B12 Yes
name TRX nb No
HMI U_RXQUAL_UL_P_AMR Sub-syste BSC Cell Type No
Definition Upper uplink quality threshold for power control of AMR-NB or AMR-WB GMSK calls.
(1==0.1 70==7)
Mandatory rules - U_RXQUAL_UL_P_AMR < L_RXQUAL_UL_P_AMR
- U_RXQUAL_UL_P_AMR < L_RXQUAL_UL_P_AMR_RXACCH
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting U_RXQUAL_UL_P_AMR = U_RXQUAL_UL_P
rules
Internal comment --
Logical U_TIME_ADVANCE B11 Yes B12 Yes
name TRX nb No
HMI UPPER_TIMING_ADVANCE Sub-syste BSC Cell Type Yes
Definition Timing Advance threshold for distance handover.
Coding rules --
Mandatory rules --
Recommended --
rules
External One unit corresponds to a distance of about 550m
comment
Internal comment CT: Depends on Cell type
Logical UL_VAMOS_PC_CORRECTION_FACTOR B11 No B12 Yes
name TRX nb No
HMI UL_VAMOS_PC_CORRECTION_FACTOR Sub-syste BSC Cell Type No
Definition This parameter represents the correction factor used to determine the transmitted powers of the VAMOS paired MSs.
Mandatory rules --
Recommended The choice of the UL_VAMOS_PC_CORRECTION_FACTOR value shall be a tradeoff between allowing a certain flexibility in the MS Power Control algorithm and
rules reducing the risks of interference in the network.
Internal comment --
Logical Use_of_Extended_CBCH B11 Yes B12 Yes
name TRX nb No
HMI Extended CBCH Sub-syste BSC Cell Type No
Definition This flag indicates if the extended CBCH is used.
Coding rules 0: not used, 1: used
Mandatory rules shall be set to "No" when SMSCB_FEATURE_SET="FS1"

can be changed only when SMSCB_STATE="inactive"
Recommended --
rules
External Default value correspond to SMSCB_FEATURE_SET = FS1.
comment If SMSCB_FEATURE_SET = FS2, Use_of_Extended_CBCH should be set to "Yes".
Internal comment --
Logical VARIOUS_IP_PRIORITY (BSC) B11 Yes B12 Yes
name TRX nb No
HMI VARIOUS_IP_PRIORITY (BSC) Sub-syste BSC Cell Type No
Definition BSS internal priority used by the BSC for the DHCP, ICMP and ARP protocols in the IP network
3: lower priority
Mandatory rules --
Recommended Should be consistent with the priorities used by others Nes

rules
External - Each internal priority can be mapped to a L2 priority using the parameter Px_layer2_mapping and also mapped to a L3 priority (DSCP) using the parameter
comment Py_layer3_mapping.
- For ARP messages, only the L2 priority is configurable (DSCP does not exist)
Internal comment - In case of specific configurations using RIP or OSPF inside the BSC, this parameter also gives the internal priority used by the routing protocol.
Logical VGCS_FIX_AMR_FR_CODEC B11 Yes B12 Yes
name TRX nb No
HMI VGCS_FIX_AMR_FR_CODEC Sub-syste BSC Cell Type No
Definition This parameter defines the type of FR AMR codec used in the network.
Coding rules 0 : AMR Full Rate Codec 12,2 kbit/s;
1 : AMR Full Rate Codec 10,2 kbit/s;
7 : AMR Full Rate Codec 4,75 kbit/st;
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical VGCS_FIX_AMR_HR_CODEC B11 Yes B12 Yes
name TRX nb No
HMI VGCS_FIX_AMR_HR_CODEC Sub-syste BSC Cell Type No
Definition This parameter defines the type of HR AMR codec used in the network.
Coding rules 0 : AMR Half Rate Codec 7,95 kbit/s;
1 : AMR Half Rate Codec 7,40 kbit/s;
Mandatory rules --
Recommended --
rules
External AMR Half Rate codec mode 7,95 kb/s is not supported by Alcatel BSS.
comment AMR Half Rate codec mode 7,4kb/s is not supported as a "stand-alone" codec
Internal comment --
Logical VQ_AVERAGE B11 Yes B12 Yes
name TRX nb No
HMI VQ_AVERAGE Sub-syste BSC Cell Type No
Definition Average window size on measurements to obtain samples for Voice Quality statistics.
Mandatory rules --
Recommended --
rules
External Up to 16 instances of this parameter with different values can be defined. This allows to define "RMS tempates" (see parameter RMS_template).
comment
Internal comment --
Logical VQ_BAD_RXFER B11 Yes B12 Yes
name TRX nb No
HMI VQ_BAD_RXFER Sub-syste BSC Cell Type No
Definition Radio bad FER threshold to specify bad quality samples for Voice Quality statistics.
Coding rules coded 0 to 200, step size=0.1% (0= 0%, 1 = 0.1 %, , 200 = 20%)
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical VQ_FER_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI VQ_FER_THRESHOLD Sub-syste BSC Cell Type No
Definition Radio FER threshold to detect calls with bad speech quality for Voice Quality statistics.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical VQ_GOOD_RXFER B11 Yes B12 Yes
name TRX nb No
HMI VQ_GOOD_RXFER Sub-syste BSC Cell Type No
Definition Radio good FER threshold to specify bad quality samples for Voice Quality statistics.
Coding rules coded 0 to 200, step size=0.1% (0= 0%, 1 = 0.1 %, , 200 = 20%)
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical VQ_INTF_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI VQ_INTF_THRESHOLD Sub-syste BSC Cell Type No
Definition Radio interference threshold to detect noisy calls for Voice Quality statistics.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical VQ_RXLEV B11 Yes B12 Yes
name TRX nb No
HMI VQ_RXLEV Sub-syste BSC Cell Type No
Definition Radio level threshold to specify bad quality samples for Voice Quality statistics.
Coding rules 0 = -110 dBm, 1 = -109 dBm, 62 = -48 dBm, 63 = -47 dBm, step = 1dBm
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical VQ_RXQUAL B11 Yes B12 Yes
name TRX nb No
HMI VQ_RXQUAL Sub-syste BSC Cell Type No
Definition Radio quality threshold to specify bad quality samples for Voice Quality statistics.
Coding rules step size=0.1 (1==0.1 70==7)
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical VQ_RXQUAL_VS_RXFER B11 Yes B12 Yes
name TRX nb No
HMI VQ_RXQUAL_VS_RXFER Sub-syste BSC Cell Type No
Definition Radio quality threshold to specify correlation between quality samples for Voice Quality statistics.
Coding rules step size=0.1 (1==0.1 70==7)
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical W_LEV_HO B11 Yes B12 Yes
name TRX nb No
HMI W_LEV_HO Sub-syste BSC Cell Type No
Definition Weight applicable to level samples for handover either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules A_LEV_HO + W_LEV_HO < 32
Recommended --
rules
External --
comment
Internal comment --
Logical W_LEV_MCHO B11 Yes B12 Yes
name TRX nb No
HMI W_LEV_MCHO Sub-syste BSC Cell Type Yes
Definition Weight applicable to level samples for microcell handover either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules A_LEV_MCHO + W_LEV_MCHO < 16
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where: Cell_type = Microcell
Logical W_LEV_PC B11 Yes B12 Yes
name TRX nb No
HMI W_LEV_PC Sub-syste BSC Cell Type No
Definition Weight applicable to level samples for power control either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe. For uplink, it
is applicable to both VAMOS and non-VAMOS mode; for downlink, to non-VAMOS mode only.
Coding rules --
Mandatory rules A_LEV_PC + W_LEV_PC < 32
Recommended --
rules
External --
comment
Internal comment --
Logical W_LEV_PC_VAMOS B11 No B12 Yes
name TRX nb No
HMI W_LEV_PC_VAMOS Sub-syste BSC Cell Type No
Definition Weight applicable to level samples for power control in VAMOS mode (only for downlink) either when DTX is disabled, or when DTX is enabled and no silence period is
present in the multiframe.
Coding rules --
Mandatory rules - A_LEV_PC_VAMOS + W_LEV_PC_VAMOS <= 32
Recommended --
rules
Internal comment --
Logical W_LEV_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI W_LEV_VAMOS_PAIRING Sub-syste BSC Cell Type No
Definition Weight applicable to level samples for VAMOS pairing, either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules - A_LEV_VAMOS_PAIRING + W_LEV_VAMOS_PAIRING < 32
Recommended --
rules
Internal comment --
Logical W_LEV_VAMOS_UNPAIRING B11 No B12 Yes
name TRX nb No
HMI W_LEV_VAMOS_UNPAIRING Sub-syste BSC Cell Type No
Definition Weight applicable to level samples for VAMOS unpairing, either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules - A_LEV_VAMOS_UNPAIRING + W_LEV_VAMOS_UNPAIRING < 32
Recommended --
rules
Internal comment --
Logical W_PBGT_HO B11 Yes B12 Yes
name TRX nb No
HMI W_PBGT_HO Sub-syste BSC Cell Type No
Definition Weight applicable to level samples for power budget either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules A_PBGT_HO + W_PBGT_HO < 32
Recommended --
rules
External --
comment
Internal comment --
Logical W_QUAL_CA B11 Yes B12 Yes
name TRX nb No
HMI W_QUAL_CA Sub-syste BSC Cell Type No
Definition Averaging weight applicable for full quality (Channel adaptation).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical W_QUAL_HO B11 Yes B12 Yes
name TRX nb No
HMI W_QUAL_HO Sub-syste BSC Cell Type No
Definition Weight applicable to quality samples for handover either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules A_QUAL_HO + W_QUAL_HO < 32
Recommended --
rules
External --
comment
Internal comment --
Logical W_QUAL_PC B11 Yes B12 Yes
name TRX nb No
HMI W_QUAL_PC Sub-syste BSC Cell Type No
Definition Weight applicable to quality samples for power control either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe. For uplink,
it is applicable to both VAMOS and non-VAMOS mode; for downlink, to non-VAMOS mode only.
Coding rules --
Mandatory rules A_QUAL_PC + W_QUAL_PC < 32
Recommended --
rules
External --
comment
Internal comment --
Logical W_QUAL_PC_VAMOS B11 No B12 Yes
name TRX nb No
HMI W_QUAL_PC_VAMOS Sub-syste BSC Cell Type No
Definition Weight applicable to quality samples for power control in VAMOS mode (only for downlink) either when DTX is disabled, or when DTX is enabled and no silence period is
present in the multiframe.
Coding rules --
Mandatory rules - A_QUAL_PC_VAMOS + W_QUAL_PC_VAMOS <= 32
Recommended --
rules
Internal comment --
Logical W_QUAL_VAMOS_PAIRING B11 No B12 Yes
name TRX nb No
HMI W_QUAL_VAMOS_PAIRING Sub-syste BSC Cell Type No
Definition Weight applicable to quality samples for VAMOS pairing, either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules - A_QUAL_VAMOS_PAIRING + W_QUAL_VAMOS_PAIRING < 32
Recommended --
rules
Internal comment --
Logical W_QUAL_VAMOS_UNPAIRING B11 No B12 Yes
name TRX nb No
HMI W_QUAL_VAMOS_UNPAIRING Sub-syste BSC Cell Type No
Definition Weight applicable to quality samples for VAMOS unpairing, either when DTX is disabled, or when DTX is enabled and no silence period is present in the multiframe.
Coding rules --
Mandatory rules - A_QUAL_VAMOS_UNPAIRING + W_QUAL_VAMOS_UNPAIRING < 32
Recommended --
rules
Internal comment --
Logical WAIT_UPLINK_ACCESS B11 Yes B12 Yes
name TRX nb No
HMI WAIT_UPLINK_ACCESS Sub-syste BSC Cell Type No
Definition Maximum number of repetitions for the UPLINK FREE message (with the Uplink Access Request bit set to L) per cycle, during the non-initial part of the uplink access
procedure (i.e. after sending the first UPLINK FREE message with the Uplink Access Request bit set to H).
Each time the value of this counter becomes zero, the BTS send one UPLINK FREE message with the Uplink Access Request bit set to H.
Coding rules --
Mandatory rules --
Recommended --
rules
External The parameter is significant only if EN_UPLINK_REPLY is set to true.
comment
Logical WI_CR B11 Yes B12 Yes
name TRX nb No
HMI WI_CR Sub-syste BSC Cell Type No
Definition Value of Wait Indication for Establishment cause = Call Re-establishment.
Coding rules 0: 0s, 1: 1s, ..., 254: 254s, 255: no IMMEDIATE ASSIGNMENT REJECT message is sent.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical WI_EC B11 Yes B12 Yes
name TRX nb No
HMI WI_EC Sub-syste BSC Cell Type No
Definition Value of Wait Indication for Establishment cause = Emergency call.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical WI_OC B11 Yes B12 Yes
name TRX nb No
HMI WI_OC Sub-syste BSC Cell Type No
Definition Value of Wait Indication for Establishment cause = Originating call.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical WI_OP B11 Yes B12 Yes
name TRX nb No
HMI WI_OP Sub-syste BSC Cell Type No
Definition Value of Wait Indication for Establishment cause = Location updating or Other procedures which can be completed with an SDCCH.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ZONE_HO_HYST_DL B11 Yes B12 Yes
name TRX nb No
HMI ZONE_HO_HYST_DL Sub-syste BSC Cell Type No
Definition Hysteresis applied to RXLEV_DL_ZONE for outer to inner zone handover.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ZONE_HO_HYST_UL B11 Yes B12 Yes
name TRX nb No
HMI ZONE_HO_HYST_UL Sub-syste BSC Cell Type No
Definition Hysteresis applied to RXLEV_UL_ZONE for outer to inner zone handover.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ZONE_TYPE B11 Yes B12 Yes
name TRX nb No
HMI TRX zone Sub-syste BSC Cell Type Yes
Definition Determines which TRX(s) belong to the inner zone and which TRX(s) belong to the outer zone of a concentric cell.
Coding rules Coded as a 16 bits bitmap. Each bit specifies the zone the corresponding TRX (if declared) belongs to. 0: Outer zone, 1: Inner zone.
Mandatory rules --
Recommended --
rules
comment
Internal comment This parameter is meaningful only in cells with: cell_PARTITION_TYPE = Concentric cell
BTS parameters
Logical ABORT_FRAME B11 Yes B12 Yes
name TRX nb No
HMI ABORT_FRAME Sub-syste BTS Cell Type No
Definition Abort frame threshold for alarm detection.
Category System (CST) OMC-R access None (not in DLS) Type Threshold Unit None
n Max value 2E+16 Coded Max 0
Def value 2E+16 Coded Def 0
Coding rules 2E+16 coded as 0
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Logical AG_FULL B11 Yes B12 Yes
name TRX nb No
HMI AG_FULL Sub-syste BTS Cell Type No
Definition Maximum number of Access Grant messages that can be buffered for one CCCH slot.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware
Logical BCCH_CUT_TIMER B11 Yes B12 Yes
name TRX nb No
HMI BCCH_CUT_TIMER Sub-syste BTS Cell Type No
Definition Timeout for cut of BCCH on loss of LAPD connection.
Mandatory rules --
Recommended --
rules
External --
comment
Logical BFD_IP_ADDRESS_BTS B11 Yes B12 Yes
name TRX nb No
HMI BFD_IP_ADDRESS_BTS Sub-syste BTS Cell Type No
Definition This parameter is the specific IP address used in the BTS for the BFD protocol (Bidirectional Forwarding Detection).
Spec ref. BSS IP Transport: protocol & configuration Coded Max
Coding rules Coded on 4 octets string
The coded default value 0.0.0.0 means BFD is not activated on this BFD IP address; that dummy value indicates that the operator does not provide any IP address yet.
It is not displayed on the OMC.
Mandatory rules --
Recommended - 255.255.255.255 is forbidden

rules - The gateway address (see BTS_ROUTING_SUBGROUP defined in the BOP) shall be different to the BFD_IP_ADDRESS_BTS.
External - Meaningful only for BTS in IP transport mode
comment - This parameter is configurable from the BTS terminal (BTS-NEM)
- Note: BFD is always active on the BTS_IP_Address. There is no need to configure BFD_IP_ADDRESS_BTS (different of BTS_IP address) if in the router a host route
to the BTS_IP_address is defined, which is bound to a BFD session. It is needed to configure BFD_IP_ADDRESS_BTS if a network route is defined in the router (the
BFD_IP_ADDRESS_BTS is next hop for the BTS_IP_address).
Internal comment - This parameter is retrieved from the BTS by the OMC through SNMP.
Logical BTS_EN_RF_RES_IND B11 Yes B12 Yes
name TRX nb No
HMI BTS_EN_RF_RES_IND Sub-syste BTS Cell Type No
Definition Enables/disables sending of RF RESOURCE INDICATION by the BTS.
Category Site (CAE) OMC-R access None (not in DLS) Type Flag Unit None
Mandatory rules --
Recommended --
rules
External --
comment
Logical BTS_VLAN_ID B11 Yes B12 Yes
name TRX nb No
HMI BTS_VLAN_ID Sub-syste BTS Cell Type No
Definition Virtual LAN identifier used to tag the BTS traffic.
Rec ref. IEEE 802.1 Q 9.6 Domai IP Min value 0 Coded Min 0
0 means there is no VLAN_ID (only priority tagging: Cf 802.1Q).
Mandatory rules --
Recommended The VLAN_ID value shall be consistent in all the VLAN-aware switches of the IP network.
rules
External - This parameter is configurable from the BTS terminal (BTS-NEM).
comment - Meaningful only for BTS in IP transport mode.
- Parameter change: Change of the VLAN_ID used by the BTS will impact the traffic of the BTS. As consequence, Alcatel-Lucent recommends to shut down the
traffic before any change.
Internal comment - Sent from BTS to OMC by SNMP.
Logical CRC_ERR B11 Yes B12 Yes
name TRX nb No
HMI CRC_ERR Sub-syste BTS Cell Type No
Definition CRC error threshold for alarm detection.
Mandatory rules --
Recommended --
rules
External --
comment
Logical DMA_OVERRUN B11 Yes B12 Yes
name TRX nb No
HMI DMA_OVERRUN Sub-syste BTS Cell Type No
Definition DMA overrun threshold for alarm detection (the chip has not enough time for DMA access in reception).
Mandatory rules --
Recommended --
rules
External --
comment
Logical DMA_UNDERRUN B11 Yes B12 Yes
name TRX nb No
HMI DMA_UNDERRUN Sub-syste BTS Cell Type No
Definition DMA underrun threshold for alarm detection (the chip has not enough time for DMA access in transmission).
Mandatory rules --
Recommended --
rules
External --
comment
Logical FRAME_DISCARD B11 Yes B12 Yes
name TRX nb No
HMI FRAME_DISCARD Sub-syste BTS Cell Type No
Definition Frame discard (due to lack of buffer) threshold for alarm detection.
Mandatory rules --
Recommended --
rules
External --
comment
Logical FTP_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI FTP_PRIORITY (BTS) Sub-syste BTS Cell Type No
Definition BSS internal priority used by the BTS for FTP flow in IP network towards the BSC.
3: lower priority
Mandatory rules shall be equal to FTP_PRIORITY (BSC).
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
Logical I_LAPD_MAX_RX B11 Yes B12 Yes
name TRX nb No
HMI I_LAPD_MAX_RX Sub-syste BTS Cell Type No
Definition Maximum number of I frames allowed in the reception buffer of the RSL in BTS.
Coding rules --
Mandatory rules --
Recommended > LAPD window size +3

rules
External --
comment
Logical I_LAPD_MAX_TX B11 Yes B12 Yes
name TRX nb No
HMI I_LAPD_MAX_TX Sub-syste BTS Cell Type No
Definition Maximum number of I frames allowed in the transmission buffer of the RSL in BTS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical INACT_DLCI B11 Yes B12 Yes
name TRX nb No
HMI INACT_DLCI Sub-syste BTS Cell Type No
Definition Inactive DLCI threshold for alarm detection.
Coding rules 2**16 coded as 0
Mandatory rules --
Recommended --
rules
External --
comment
Logical INVALID_ADR B11 Yes B12 Yes
name TRX nb No
HMI INVALID_ADR Sub-syste BTS Cell Type No
Definition Invalid address threshold for alarm detection (fixed format error when CRC is correct).
0 : 20000000000000000
1: 1
2: 2
.
1999999999999999: 1999999999999999
Mandatory rules --
Recommended --
rules
External --
comment
Logical IPGCHC_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHC_PRIORITY Sub-syste BTS Cell Type No
Definition BSS internal priority used by the IPGCH Control flow in IP network
3: lower priority
Mandatory rules Equal to IPGCHC_PRIORITY (MFS)
Recommended --
rules
External --
comment
Logical IPGCHC_TCP_PORT_BTS (BTS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHC_TCP_PORT_BTS Sub-syste BTS Cell Type No
Definition Defines the range allowed for all the TCP ports used by the IPGCHC protocol on BTS side by all its TREs.
Mandatory rules --
Recommended SUM shall take care that with the value of this parameter, all TCP ports values computed for each TRE belong to the range specified
rules
External --
comment
Internal comment - Hardcoded inside the SUM SW.
- Values for each TRE are taken by the BTS(SUM) in the range specified and then distributed to each TRE. These values are sent by the BTS to the BSC via OML
HW_capability_report and then, sent by the BSC to the MFS (see IPGCHC_TCP_PORT_BTS (BSC)).
- Min = hD100, Max = hD4FF
Logical IPGCHU_BE_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BE_PRIORITY Sub-syste BTS Cell Type No
Definition BSS internal priority used by the IPGCH Best Effort flow in IP network
3: lower priority
Mandatory rules Equal to IPGCHU_BE_PRIORITY (MFS)
Recommended --
rules
External --
comment
Logical IPGCHU_GBR_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_GBR_PRIORITY Sub-syste BTS Cell Type No
Definition BSS internal priority used by the IPGCH GBR flow in IP network
3: lower priority
Mandatory rules Equal to IPGCHU_GBR_PRIORITY (MFS)
Recommended --
rules
External --
comment
Logical IPGCHU_UDP_MAX_WINDOW_SIZE_G3 B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_UDP_MAX_WINDOW_SIZE_G3 Sub-syste BTS Cell Type No
Definition Maximum UDP window size for IPGCH usable for a G3 TRE.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the BTS
Logical IPGCHU_UDP_MAX_WINDOW_SIZE_G4_G5 B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_UDP_MAX_WINDOW_SIZE_G4_G5 Sub-syste BTS Cell Type No
Definition Maximum UDP window size for IPGCH usable for a G4 or a G5 TRE.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the BTS
Logical IPGCHU_UDP_MAX_WINDOW_SIZE_MC B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_UDP_MAX_WINDOW_SIZE_MC Sub-syste BTS Cell Type No
Definition Maximum UDP window size for IPGCH usable for a MC module.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the BTS.
The value 2000 stems from the product requirement to support:
- 1,92 Mbps per MC module when using Abis and Ater terrestrial links (i.e. Edge traffic in MCS-9 on 8 PDCHs on 4 TRXs),
- 960 kbps per MC module when using Abis or Ater satellite links (i.e. Edge traffic in MCS-9 on 8 PDCHs on 2 TRXs).
Logical IPGCHU_UDP_PORT_BTS B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_UDP_PORT_BTS Sub-syste BTS Cell Type No
Definition Defines the range allowed for UDP ports used by the BTS (SUM) to configure the IPGCHU protocol on BTS side for each TRE.
Coding rules --
Mandatory rules --
Recommended SUM shall take care that with the value of this parameter, all UPD ports values computed for each TRE belong to the range specified.
rules
External BTS uses one source UDP port (IPGCHU_UDP_PORT_BTS) to send UL traffic towards the destination IPGCHU_UDP_PORT_MFS port of the MFS.
comment
Internal comment - Hardcoded inside the SUM SW. Values for each TRE are taken by the BTS(SUM) in the range specified Values for each TRE are sent by each TRE to the MFS in the
IPGCH_init_cnf message . Min = hD000, Max = hD0FF
Logical IPTCH_UDP_PORT_BTS B11 Yes B12 Yes
name TRX nb No
HMI IPTCH_UDP_PORT_BTS Sub-syste BTS Cell Type No
Definition UDP port of IPTCH protocol used on BTS side (by the SUM, for MUXTRAUP).
Mandatory rules --
Recommended --
rules
External Meaningful in both A user plane over TDM or IP.
comment
Internal comment - one port is used: h'D500
- Hardcoded inside the SUM SW.
Logical K_LAPD_OML B11 Yes B12 Yes
name TRX nb No
HMI K_LAPD_OML Sub-syste BTS Cell Type No
Definition Maximum number of outstanding frames (OML).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical K_LAPD_RSL B11 Yes B12 Yes
name TRX nb No
HMI K_LAPD_RSL Sub-syste BTS Cell Type No
Definition Maximum number of outstanding frames (OML).
Category Network (CDE) OMC-R access None (not in DLS) Type Number Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Recommended values:4 for 16 kbit/s RSL, 7 for 64 kbit/s RSL
Logical K_LAPDm B11 Yes B12 Yes
name TRX nb No
HMI K_LAPDm Sub-syste BTS Cell Type No
Definition Maximum number of outstanding I frames.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical M_PEND_A (BTS) B11 Yes B12 Yes
name TRX nb No
HMI M_PEND_A (BTS) Sub-syste BTS Cell Type No
Definition Maximum number of I-frames received on RSL by an Evolium BTS before sending an acknowledgement.
Mandatory rules The value of this parameter shall be lower than (K_LAPD_RSL minus 2)
Recommended --
rules
External The same value is used for terrestrial and satellite links.
comment
Internal comment --
Logical N_DECR B11 Yes B12 Yes
name TRX nb No
HMI N_DECR Sub-syste BTS Cell Type No
Definition Stepsize by which a leaky bucket overload counter in the FU is decremented on T_SUP expiry.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N_INCR B11 Yes B12 Yes
name TRX nb No
HMI N_INCR Sub-syste BTS Cell Type No
Definition Stepsize by which a leaky bucket overload counter in the FU is incremented each time an overload is reported.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N_TA_IP B11 Yes B12 Yes
name TRX nb No
HMI N_TA_IP Sub-syste BTS Cell Type No
Definition Minimum number TRAUP packet between the sending by CCU of the last Time Alignment request and the sending of next TA request.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via FU.CPF
Logical N_WAIT B11 Yes B12 Yes
name TRX nb No
HMI N_WAIT Sub-syste BTS Cell Type No
Definition Spacing between two consecutive DL_DATA_CONGESTION_IND sent to BTS Layer 3.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_LE B11 Yes B12 Yes
name TRX nb No
HMI N200_LE Sub-syste BTS Cell Type No
Definition Maximum number of retransmission of a frame (that requires acknowledgement) before detecting radio failure in Link Establishment state.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_LR B11 Yes B12 Yes
name TRX nb No
HMI N200_LR Sub-syste BTS Cell Type No
Definition Maximum number of retransmission of a frame (that requires acknowledgement) before detecting radio failure in Link Release state.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_OML (BTS) B11 Yes B12 Yes
name TRX nb No
HMI N200_OML (BTS) Sub-syste BTS Cell Type No
Definition Maximum number of retries for sending I frame by the BTS (OML).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_RSL (BTS) B11 Yes B12 Yes
name TRX nb No
HMI N200_RSL (BTS) Sub-syste BTS Cell Type No
Definition Maximum number of retries for sending I frame by the BTS (RSL).
Coding rules --
Mandatory rules --
Recommended The recommended value for Abis via satellite is 5.

rules
External The value of N200_RSL (BTS) is driven by the associated Abis connection type.
Logical N200_TD B11 Yes B12 Yes
name TRX nb No
HMI N200_TD Sub-syste BTS Cell Type No
Definition Maximum number of retransmission of a frame (that requires acknowledgement) before detecting radio failure in Timer Recovery state on SDCCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_TS B11 Yes B12 Yes
name TRX nb No
HMI N200_TS Sub-syste BTS Cell Type No
Definition Maximum number of retransmission of a frame (that requires acknowledgement) before detecting radio failure in Timer Recovery state on SACCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_TTF B11 Yes B12 Yes
name TRX nb No
HMI N200_TTF Sub-syste BTS Cell Type No
Definition Maximum number of retransmission of a frame (that requires acknowledgement) before detecting radio failure in Timer Recovery state on FACCH (TCH/FR associated).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N200_TTH B11 Yes B12 Yes
name TRX nb No
HMI N200_TTH Sub-syste BTS Cell Type No
Definition Maximum number of retransmission of a frame (that requires acknowledgement) before detecting radio failure in Timer Recovery state on FACCH (TCH/HR associated).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N201 (BTS) B11 Yes B12 Yes
name TRX nb No
HMI N201 (BTS) Sub-syste BTS Cell Type No
Definition Maximum length of user data in an I frame.
Category System (CST) OMC-R access None (not in DLS) Type Number Unit bytes
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N201_BTER_D B11 Yes B12 Yes
name TRX nb No
HMI N201_BTER_D Sub-syste BTS Cell Type No
Definition Length of information field on FACCH (Format Bter).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N201_BTER_S B11 Yes B12 Yes
name TRX nb No
HMI N201_BTER_S Sub-syste BTS Cell Type No
Definition Length of information field on SACCH (Format Bter).
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N201_D B11 Yes B12 Yes
name TRX nb No
HMI N201_D Sub-syste BTS Cell Type No
Definition Length of information field on SDCCH and FACCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical N201_S B11 Yes B12 Yes
name TRX nb No
HMI N201_S Sub-syste BTS Cell Type No
Definition Length of information field on SACCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical PDA_FULL B11 Yes B12 Yes
name TRX nb No
HMI PDA_FULL Sub-syste BTS Cell Type No
Definition Maximum number of PACKET DL ASSIGNMENT messages that can be stored for one CCCH group.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware.
Logical PG_FULL B11 Yes B12 Yes
name TRX nb No
HMI PG_FULL Sub-syste BTS Cell Type No
Definition Maximum number of PAGING REQUEST messages that can be stored for one CCCH group.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical RR_ACK_TIMER (BTS) B11 Yes B12 Yes
name TRX nb No
HMI RR_ACK_TIMER (BTS) Sub-syste BTS Cell Type No
Definition Maximum delay for sending a RR acknowledgement frame on RSL and GSL
Category System (CST) OMC-R access None (not in DLS) Type Timer Unit ms
Mandatory rules The value of this parameter shall be lower than (T200 TRE minus 50ms
Recommended --
rules
External The same value is used for terrestrial and satellite links.
comment
Internal comment --
Logical RSL_I_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI RSL_I_PRIORITY (BTS) Sub-syste BTS Cell Type No
Definition BSS internal priority used by the BTS for the RSL-I flow in IP network
3: lower priority
Mandatory rules shall be equal to RSL_I_PRIORITY(BSC)
Recommended --
rules
External --
comment
Logical RSL_RATE (BTS) B11 Yes B12 Yes
name TRX nb No
HMI RSL_RATE (BTS) Sub-syste BTS Cell Type No
Definition Rate used on all RSL links of the BTS.
Category Site (CAE) OMC-R access None (not in DLS) Type Flag Unit None
Coding rules 0: 16 kbit/s, 1: 64 kbit/s.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message. Should be the same as the BSC value
Logical RSL_UDP_PORT_TRE B11 Yes B12 Yes
name TRX nb No
HMI RSL_UDP_PORT_TRE Sub-syste BTS Cell Type No
Definition UDP port number of one TRE (HW module) used for RSL on BTS side.
Mandatory rules --
Recommended --
rules
External --
comment
- Min = hCF00, Max = hCFFF.
- Values for each TRX are taken by the BTS (SUM) in the range specified and distributed to each TRX.
- the UDP port of each TRE HW module (Twin-TRA or MC module) is computed by the BTS (SUM) in the specified range, and distributed to every TRXs inside the
related TRE HW module.
Logical RSL_UI_PRIORITY (BTS) B11 No B12 Yes
name TRX nb No
HMI RSL_UI_PRIORITY (BTS) Sub-syste BTS Cell Type No
Definition BSS internal priority used by the BTS for the RSL-UI flow in IP network
3: lower priority
Mandatory rules - shall be equal to RSL_UI_PRIORITY (BSC)
Recommended --
rules
External --
comment
Logical SHORT_FRM B11 Yes B12 Yes
name TRX nb No
HMI SHORT_FRM Sub-syste BTS Cell Type No
Definition Short frame threshold for alarm detection.
Mandatory rules --
Recommended --
rules
External --
comment
Logical SIDMO_TCP_PORT_TRE B11 Yes B12 Yes
name TRX nb No
HMI SIDMO_TCP_PORT_TRE Sub-syste BTS Cell Type No
Definition Defines the range allowed for all the TCP ports used by the SIDMO protocol (SCP IP Debug Monitor) on BTS side by all its TREs. SIDMO is used for debug purposes to
send messages on IP network related for example to RLC/MAC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Values for each TRE are computed by the BTS in the range specified.
- Min = hD700 Max = hD7FF
Logical SNMP_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI SNMP_PRIORITY (BTS) Sub-syste BTS Cell Type No
Definition BSS internal priority used by the BTS for the SNMP flow in IP network
3: lower priority
Mandatory rules shall be equal to SNMP_PRIORITY(BSC)
Recommended --
rules
External --
comment
Logical T_CFI_TR B11 Yes B12 Yes
name TRX nb No
HMI T_CFI_TR Sub-syste BTS Cell Type No
Definition Timer used in the BTS for filtering transcoder alarms after the sending of the 08.58 ESTABLISH INDICATION message at the beginning of the TCH assignment.
Category Network (CDE) OMC-R access None (not in DLS) Type Timer Unit sec
Coding rules --
Mandatory rules T_CFI_TR > T_SYNC
Recommended --
rules
External --
comment
Internal comment Sent to the FU at initialisation via FU_CPF.
Logical T_CONFIRM_ABIS B11 Yes B12 Yes
name TRX nb No
HMI T_CONFIRM_ABIS Sub-syste BTS Cell Type No
Definition Timer controlling the periodic sending by the BTS to the BSC of the message CONFIRM ABIS NIBBLES, containing the list of Abis nibbles allocated to the concerned TRE of
the BTS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RESET_COUNTER B11 Yes B12 Yes
name TRX nb No
HMI T_RESET_COUNTER Sub-syste BTS Cell Type No
Definition Used to reset LAPD error counters.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_SMSCB_READY B11 Yes B12 Yes
name TRX nb No
HMI T_SMSCB_READY Sub-syste BTS Cell Type No
Definition Maximum waiting time before repetition of response from the BTS.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_SUP B11 Yes B12 Yes
name TRX nb No
HMI T_SUP Sub-syste BTS Cell Type No
Definition Delay between latest increment and decrement and between two consecutive decrement of FU load counter.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_SYNC B11 Yes B12 Yes
name TRX nb No
HMI Tsync Sub-syste BTS Cell Type No
name Instance TRAU RMS No
Definition Timer used in the BTS to detect a loss of synchronisation between BTS and transcoder
Spec ref. TRCU/BTS interface Coded Max 15
Coding rules step size = 1s
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the software. Configured via the FU.CPF file
Logical T_SYNCd B11 Yes B12 Yes
name TRX nb No
HMI TsyncD Sub-syste BTS Cell Type No
Definition Time for detection of loss of synchronisation on downlink from transcoder to BTS for enhanced full rate and half rate channels.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_SYNCu B11 Yes B12 Yes
name TRX nb No
HMI TsyncU Sub-syste BTS Cell Type No
Definition Time for detection of uplink framing errors for enhanced full rate and half rate channels.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_ta B11 Yes B12 Yes
name TRX nb No
HMI Tta Sub-syste BTS Cell Type No
Definition Minimum delay between two consecutive time alignment changes.
Mandatory rules --
Recommended --
rules
External Values equal to or higher than 500 ms disable time alignment for FR and EFR in BTS-TC interface and link adaptation for AMR
comment
Logical T_TA_ Margin B11 Yes B12 Yes
name TRX nb No
HMI T_TA_ Margin Sub-syste BTS Cell Type No
Definition Margin between TA-target-value and TA-On-Time
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Configured via FU.CPF
Logical T_TA_delta_min B11 Yes B12 Yes
name TRX nb No
HMI T_TA_delta_min Sub-syste BTS Cell Type No
Definition Minimum absolute TA-target-value, which allows to send a new TA command.
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
HMI T200_D Sub-syste BTS Cell Type No
Definition Supervision of acknowledgements for SDCCH SAPI 0.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical T200_D3 B11 Yes B12 Yes
name TRX nb No
HMI T200_D3 Sub-syste BTS Cell Type No
Definition Supervision of acknowledgements for SDCCH SAPI 3.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical T200_OMU B11 Yes B12 Yes
name TRX nb No
HMI T200_TRE Sub-syste BTS Cell Type No
Definition Supervision of acknowledgements on RSL for OMU SW.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment hardcoded in OMU PROM.
Logical T200_S3 B11 Yes B12 Yes
name TRX nb No
HMI T200_S3 Sub-syste BTS Cell Type No
Definition Supervision of acknowledgements for SACCH (TCH associated) SAPI 3.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical T200_TRE B11 Yes B12 Yes
name TRX nb No
HMI T200_TRE Sub-syste BTS Cell Type No
Definition Supervision of acknowledgements on RSL for TRE SW.
Category Site (CAE) OMC-R access None (not in DLS) Type Timer Unit ms
Coding rules step size 10 ms
Mandatory rules --
Recommended The recommended value for Abis via satellite is 1000 ms.
rules
External The value of T200_TRE is driven by the associated Abis connection type,
comment It can be changed indirectly from the OMC (through the change of Abis connection type).
The default value 270 ms corresponds to Abis terrestrial link.
Internal comment --
Logical T203 (BTS) B11 Yes B12 Yes
name TRX nb No
HMI T203 (BTS) Sub-syste BTS Cell Type No
Definition RSL Link supervision timer.
Coding rules --
Mandatory rules T203 (BTS) > T_SYNC
Recommended --
rules
External --
comment
Logical TCP_KEEP_ALIVE_CNT (BTS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_CNT Sub-syste BTS Cell Type No
Definition Number of TCP keep-alive messages sent by the IPGCH-C and not acknowledged by the peer before triggering a TCP disconnection
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_CNT (MFS)

rules
External --
comment
Logical TCP_KEEP_ALIVE_IDLE (BTS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_IDLE Sub-syste BTS Cell Type No
Definition IPGCH-C link supervision: Time to wait before sending the first TCP keep alive message.
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_IDLE (MFS)

rules
External --
comment
Logical TCP_KEEP_ALIVE_INTVL (BTS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_INTVL Sub-syste BTS Cell Type No
Definition Time between the sending of two TCP keep-alive messages by IPGCH-C
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_INTVL (MFS)

rules
External --
comment
Logical TCP_MAX_RETRANS (BTS) B11 Yes B12 Yes
name TRX nb No
BTS Cell Type No
name Instance
BTS RMS No
Definition Maximum number of times a TCP segment (used by IPGCHC) is resent by the BTS before to raise a time-out error.
Mandatory rules --
Recommended TCP_MAX_RETRANS (BTS) should be set to a value in order that TCP reset (Abort interval) is shorter than the GP recovery time.
rules
External For example, if a global failure happens during a TCP transfer in which the failed connection side was the data receiver, the sending TCP will try to retransmit the
comment non-acknowledged data segments, but TCP will limit the number of retransmissions by
means of this parameter. On abort interval expiry, TCP resets the connection (RST segment). It is a constant hardcoded.
- Exponential back off applied by the TCP stack of the MFS (used by IPGSL and IPGCHC) before each resend of TCP segment.
Note: the max time between two resends is 1 minute
Logical TCP_MSL (BTS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_MSL (BTS) Sub-syste BTS Cell Type No
Definition TCP message segment lifetime, used by IPGCH-C.
Mandatory rules --
Recommended TCP_MSL (BTS) = TCP_MSL (MFS)

rules
External --
comment
Logical THR_ACT_1 B11 Yes B12 Yes
name TRX nb No
HMI THR_ACT_1 Sub-syste BTS Cell Type No
Definition Threshold for triggering local overload defence actions in the FU.
Category Network (CDE) OMC-R access None (not in DLS) Type Threshold Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical THR_ACT_2 B11 Yes B12 Yes
name TRX nb No
HMI THR_ACT_2 Sub-syste BTS Cell Type No
Definition Threshold for triggering global overload defence actions in the FU.
Category Network (CDE) OMC-R access None (not in DLS) Type Threshold Unit None
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical THR_BUFFER B11 Yes B12 Yes
name TRX nb No
HMI THR_BUFFER Sub-syste BTS Cell Type No
Definition Free buffers threshold in Frame Unit.
Category Network (CDE) OMC-R access None (not in DLS) Type Threshold Unit %
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical THR_IDLE B11 Yes B12 Yes
name TRX nb No
HMI THR_IDLE Sub-syste BTS Cell Type No
Definition Processor idle time threshold in Frame Unit.
Category Network (CDE) OMC-R access None (not in DLS) Type Threshold Unit %
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical THRES_HIGH_TX B11 Yes B12 Yes
name TRX nb No
HMI THRES_HIGH_TX Sub-syste BTS Cell Type No
Definition Congestion onset threshold for transmission buffer of the RSL in BTS.
Category System (CST) OMC-R access None (not in DLS) Type Threshold Unit %
Coding rules --
Mandatory rules --
Recommended THRES_HIGH_TX > THRES_LOW_TX

rules
External --
comment
Logical THRES_LOW_TX B11 Yes B12 Yes
name TRX nb No
HMI THRES_LOW_TX Sub-syste BTS Cell Type No
Definition Congestion clear threshold for transmission buffer of the RSL in BTS.
Category System (CST) OMC-R access None (not in DLS) Type Threshold Unit %
Coding rules --
Mandatory rules --
Recommended THRES_LOW_TX < THRES_HIGH_TX

rules
External --
comment
Logical TLC_CONFIG_T B11 Yes B12 Yes
name TRX nb No
HMI TLC_CONFIG_T Sub-syste BTS Cell Type No
Definition Supervision of the initialisation of the FU via the RSL.
Spec ref. BSS initialisation of the telecom part Coded Max 65535
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured in the BTS via the FU.CPF file
Logical TRAU_ACTIVITY_TIMER B11 Yes B12 Yes
name TRX nb No
HMI TRAU_ACTIVITY_TIMER Sub-syste BTS Cell Type No
Definition Timer to supervise the TRAU activity.
Mandatory rules --
Recommended --
rules
External --
comment
- Range ensures that TRAU_Activity_Timer <= TRAU_Connection_Timeout. when TRAU_Connection_Timeout = TRAU_Activity_Timer; only the mechanism linked to
TRAU_Connection_Timeout is used
Logical TRE_CONTAINER_MAX_NB_UDP_G3 B11 Yes B12 Yes
name TRX nb No
HMI TRE_CONTAINER_MAX_NB_UDP_G3 Sub-syste
BTS Cell Type No
name InstanceBTS RMS No
Definition Maximum number of UDP containers to consider when computing the maximum IPGCHU segment size (called IPGCHU MISS value) in a G3 TRE.
Mandatory rules
Recommended
rules
External
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
For a G3 TRE, limiting the number of UDP containers to the TRE_CONTAINER_MAX_NB_UDP_G3 parameter value has for goal to avoid the allocation of too much TRE
memory for the IPGCHU segment retransmission buffers. This is not really seen as a problem from G4 onwards TREs, including MC modules, which have much more
memory available than G3 TREs.
Logical TRE_CONTAINER_SIZE_TCP_G3 B11 Yes B12 Yes
name TRX nb No
HMI TRE_CONTAINER_SIZE_TCP_G3 Sub-syste BTS Cell Type No
Definition Size of a TCP container in a G3 TRE.
This size is used in the computing of the TCP maximum segment size in DL (TCP DL MSS for the IPGCHC TCP connections).
Mandatory rules --
Recommended --
rules
External --
comment
The default value of 768 bytes is not optimal. As the TCP NO DELAY option is used and as the size of the IPGCH control messages is generally quite low (far below
768 bytes), setting this parameter to 768 bytes is inefficient and can lead to a waste of memory in the TRE. For the moment, it will stay at this high default value to
minimize efforts. The intent is to play around with this value when the load tests start and to decide afterwards.
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Logical TRE_CONTAINER_SIZE_TCP_MC B11 Yes B12 Yes
name TRX nb No
HMI TRE_CONTAINER_SIZE_TCP_MC Sub-syste BTS Cell Type No
Definition Size of a TCP container in a MC module.
Mandatory rules --
Recommended --
rules
External --
comment
Logical TRE_CONTAINER_SIZE_UDP_G3 B11 Yes B12 Yes
name TRX nb No
HMI TRE_CONTAINER_SIZE_UDP_G3 Sub-syste BTS Cell Type No
Definition Size of an UDP container in a G3 TRE.
This size is used in the computing of the maximum IPGCHU segment size (called IPGCHU MISS value).
Coding rules Step size = 1 byte
Mandatory rules --
Recommended --
rules
External --
comment
The following rules should be verified by this parameter:
- its value should not be too low in order to avoid CPU consumption in the TRE (memory buffer allocations when sending LLC data are indeed CPU-consuming),
- its value should not be higher than IPGCH_PACKET_SIZE 34, otherwise it will fragment and waste IPGCH memory / increase risks of IPGCH memory congestion in
the TRE, which can especially be a problem for G3 TREs (this rule is not really seen as a problem from G4 onwards TREs, including MC modules, which have much
more memory available than G3 TREs).
For the moment, this parameter will stay with a default value of 150 bytes: the intent is to play around with this value when the load tests start and to decide
afterwards.
To be noted that, as IPGCH_PACKET_SIZE is a changeable parameter, it will anyway be impossible to set this parameter value in an optimal way in all situations.
In particular, GMM traffic (which uses very short LLC PDUs) could put some problems if this parameter value is too high.
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
afterwards.
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
afterwards.
Logical TRE_CONTAINER_SIZE_UDP_MC B11 Yes B12 Yes
name TRX nb No
HMI TRE_CONTAINER_SIZE_UDP_MC Sub-syste BTS Cell Type No
Definition Size of an UDP container in a MC module.
Mandatory rules --
Recommended --
rules
External --
comment
afterwards.
Logical UI_LAPD_MAX_TX B11 Yes B12 Yes
name TRX nb No
HMI UI_LAPD_MAX_TX Sub-syste BTS Cell Type No
Definition Maximum number of UI frames allowed in the transmission buffer of the RSL in BTS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical VARIOUS_IP_PRIORITY (BTS) B11 Yes B12 Yes
name TRX nb No
HMI VARIOUS_IP_PRIORITY (BTS) Sub-syste BTS Cell Type No
Definition BSS internal priority used by the BTS for the DHCP, ICMP and ARP protocols in the IP network
3: lower priority
Mandatory rules --
Recommended Should be consistent with the priorities used by others Nes

rules
comment Py_layer3_mapping
Internal comment - In case of specific configurations using RIP or OSPF inside the TC, this parameter also gives the internal priority used by the routing protocol.
- Harcoded in the BTS
MFS parameters
Logical 3G_TDD_PMO_CODING B11 No B12 Yes
name TRX nb No
HMI 3G_TDD_PMO_CODING Sub-systeMFS Cell Type No
name Instance MFS RMS No
Definition Flag to allow variants of Packet Measurement Order message coding for GSM to UTRAN TD-SCDMA cell reselection.
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 2
Coding rules - 0 PMO encoding is with order of the TDD_indic0 field and TDD-ARFCN field reverse compared with 3GPP TS 44.060
- 1: PMO encoding is compliant with 3GPP
- 2 : Reserved for future use
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution and further generation
comment
Internal comment - This flag is specific for CMCC.
- The default value 0 corresponds to same behaviour as B11 (PMO encoding for bugged MS).
Logical ACCESS_BURST_TYPE B11 Yes B12 Yes
name TRX nb No
HMI ACCESS_BURST_TYPE Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Format of the access burst used by (E)GPRS MSs when sending a PACKET CHANNEL REQUEST, a PACKET CONTROL ACKNOWLEDGEMENT or a PTCCH/U
message.
Spec ref. GPRS radio interface - RRM sublayer Coded Max 1
Coding rules 0 : 8 bits access bursts, 1 : 11 bits access bursts
Mandatory rules A couple of mate cells (Extended inner + extended outer) shall have the same ACCESS_BURST_TYPE when they are PS capable.
Recommended --
rules
External --
comment
Internal comment --
Logical ACCESS_RATE_BC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Capacity Sub-syste MFS Cell Type No
name Instance BC RMS No
Definition Physical access rate of the Frame Relay bearer channel.
Category Site (CAE) OMC-R access None (not in DLS) Type Number Unit kbit/s
Spec ref. GPRS Gb interface - Sub-network service sub-layer Coded Max 1984
Coding rules
Mandatory rules Not changeable after MFS system initialization.
CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC (MFS)
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment - This parameter is computed by the MFS, as follow: 64 x [nb of bit set to 1 in the BOP parameter BEARER_CHANNEL_CAPACITY]
Logical ALLOW_DTM_EDA_COMBINATION B11 Yes B12 Yes
name TRX nb No
HMI ALLOW_DTM_EDA_COMBINATION Sub-syste MFS Cell Type No
Definition Allows EDA operations for mobile stations in DTM mode.
Rec ref. None Domai E-GPRS Min value 0 Coded Min 0
Coding rules 0: the usage of EDA for mobile stations in DTM mode is not allowed,
1: the usage of EDA for mobile stations in DTM mode is allowed.
Mandatory rules --
Recommended --
rules
External This flag is relevant only if DTM and EDA are both activated.
comment
Internal comment - This flag provides a mean to disable the usage of EDA in case of DTM operations. Indeed some mobile stations might not correctly support the combination of these
two features.
- None of the combination of the EN_EDA, EN_DTM, EDA_MS_ACTIVATION_LEVEL and ALLOW_DTM_EDA_COMBINATION parameters allows activating EDA only in
case of DTM operations.
Logical ALPHA (MFS) B11 Yes B12 Yes
name TRX nb No
HMI ALPHA Sub-syste MFS Cell Type No
Definition Alpha power control parameter.
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 10
Coding rules Possible values are : 0.0 to 1.0 with step of 0.1respectively binary coded : 0000, 0001, 0010 1010
Mandatory rules Equal to ALPHA (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical ARC_SIZE_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI ARC_SIZE_FACTOR Sub-syste MFS Cell Type No
Definition Factor used in the computation of the width in degree of the ellipsoid arc returned by the MFS when computing location estimate based on TA positionning method.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical ATER_GCH_EQUITY_MARGIN B11 No B12 Yes
name TRX nb No
HMI ATER_GCH_EQUITY_MARGIN Sub-syste MFS Cell Type No
Definition Margin used for selecting the lowest TRXs of the GP.
If (GCH/TBF) on a TRX < averaged (GCH/TBF) on all TRXs of the GP x (1 margin) then that TRX is considered as a lowest TRX.
In case of many candidates, only the ATER_GCH_EQUITY_NB_LOWEST_TRX lowest ones are selected.
When set to 100%, there is no lowest TRX on the GP.
Coding rules --
Mandatory rules --
Recommended --
rules
External -Function available on MFS Evolution only
comment - Significant if ATER_GCH_EQUITY_TIMER is enabled
- Applicable only to TDM mode.
Internal comment --
Logical ATER_GCH_EQUITY_NB_LOWEST_TRX B11 No B12 Yes
name TRX nb No
HMI ATER_GCH_EQUITY_NB_LOWEST_TRX Sub-syste MFS Cell Type No
Definition Maximum number of lowest TRXs of the GP that can be selected during the Ater GCH equity process.
Those lowest TRXs belong to a not overloaded DSP and are facing a lack of GCH, compared to the number of TBFs currently used on that TRX.
Their selection depends also on the ATER_GCH_EQUITY_MARGIN value.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Significant if ATER_GCH_EQUITY_TIMER is enabled
- Applicable only to TDM mode.
Internal comment --
Logical ATER_GCH_EQUITY_TIMER B11 No B12 Yes
name TRX nb No
HMI ATER_GCH_EQUITY_TIMER Sub-syste MFS Cell Type No
Definition This parameter enables/disables the Ater GCH equity mechanism in the GP(s) associated to the BSS.
When enabled, this timer gives the triggering periodicity.
Coding rules step size=1sec,
0 means that the Ater GCH equity mechanism is disabled (never triggered)
Mandatory rules --
Recommended --
rules
comment - Applicable only to TDM mode.
Internal comment --
Logical Ater_Usage_Threshold B11 Yes B12 Yes
name TRX nb No
HMI Ater_Usage_Threshold Sub-syste MFS Cell Type No
Definition Threshold (percentage of used Ater nibbles, in a GPU) above which the Ater usage is said high.
Coding rules --
Mandatory rules --
Recommended A low value of GCH_RED_Factor_High_Ater_Usage can be coherent with a high value of Ater_Usage_Threshold (it will avoid reaching the saturation point of 100%
rules of the Ater resources used at the same moment in the GPU).
Reciprocally, a high value of GCH_RED_Factor_High_Ater_Usage can be coherent with a low value of Ater_Usage_Threshold (it will limit the risks of wasting, i.e. of
not using, Ater resources in the GPU).
For all the Ater_Usage_Threshold values being defined for the BSSs handled by the MFS, Ater_Usage_Threshold_Short_Data <= Ater_Usage_Threshold 30%.
Indeed, for consistency reasons, short data MS transfer optimizations should come prior to high Ater usage optimizations.
External - Applicable only to TDM mode.
comment - When the Ater usage is high, the GCH_RED_FACTOR_High_Ater_Usage is applied, whereas when the Ater usage is normal (i.e. percentage of used Ater nibbles
is below the threshold), no GCH reduction factor is applied.
Parameter change: No impact on the telecom service, on going TBF are not disrupted. Change applied only on new TBF established after modification.
Internal comment --
Logical Ater_Usage_Threshold_Short_Data B11 Yes B12 Yes
name TRX nb No
HMI Ater_Usage_Threshold_Short_Data Sub-syste MFS Cell Type No
Definition Threshold (percentage of used Ater nibbles, in a GPU) above which the Ater usage is optimized for short data MS transfers.
Coding rules --
Mandatory rules --
Recommended If Ater_Usage_Threshold_Short_Data is not set to 100% (100% meaning that there is no Ater usage optimization for short data MS transfers), then it is
rules recommended to set it to 30%, except if the drawbacks of another value (as explained in the external comments) are deemed acceptable.
For all the Ater_Usage_Threshold values being defined for the BSSs handled by the MFS, Ater_Usage_Threshold_Short_Data <= Ater_Usage_Threshold 30%.
Indeed, for consistency reasons, short data MS transfer optimizations should come prior to high Ater usage optimizations.
If it is seen as an important goal to save Ater resources in the GPU, a value of Ater_Usage_Threshold_Short_Data < 100% is coherent with a low value of the
T_GCH_INACTIVITY and T_GCH_INACTIVITY_LAST timers.
comment - Setting Ater_Usage_Threshold_Short_Data to 100% means that there is no Ater usage optimization for short data MS transfers.
If Ater_Usage_Threshold_Short_Data is not set to 100%:
- the higher the Ater_Usage_Threshold_Short_Data value, the fewer ping time degradations and data transfer delays will be experienced,
- the lower the Ater_Usage_Threshold_Short_Data value, the more accurate the Ater consumption in the GPU will be (i.e. potential wastes of Ater resources will be
minimized in the GPU).
Parameter change: No impact on the telecom service, on going TBF are not disrupted. Change applied only on new TBF established after modification.
Internal comment --
Logical ATT (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IMSI Attach/Detach Sub-syste MFS Cell Type No
Definition This flag indicates to the MS whether IMSI Attach/detach procedure is allowed in the cell.
Coding rules 0: not allowed, 1: allowed
Mandatory rules Equal to ATT (BSC)
Recommended --
rules
External --
comment
Logical Basic_Scheduling_Limit B11 Yes B12 Yes
name TRX nb No
HMI Basic_Scheduling_Limit Sub-syste MFS Cell Type No
Definition Limit of Credit/weight below which a TBF cannot be scheduled during the basic scheduling phase.
This limit applies to both RT and NRT TBFs (i.e to both credit and weight).
Spec ref. GPRS radio interface - MAC sublayer Coded Max 1
Coding rules step size = 0,5
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Hardcoded in MAC layer
Logical BCC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI BCC Sub-syste MFS Cell Type No
Definition BTS colour code of the cell.
Mandatory rules Equal to BCC (BSC)
Recommended --
rules
comment
Logical BCC (n) B11 Yes B12 Yes
name TRX nb No
HMI BCC Sub-syste MFS Cell Type No
Definition BTS colour code of the adjacent cell.
Mandatory rules --
Recommended --
rules
comment
Logical BCCH_ARFCN(n)(MFS) B11 Yes B12 Yes
name TRX nb No
HMI BCCH_ARFCN Sub-syste
MFS Cell Type No
name Instance
adj RMS No
Definition Indicates the Absolute Radio Frequency Channel Number of the frequency used as BCCH in the adjacent cell.
Coding rules --
Mandatory rules - BCCH_ARFCN(n)(BSC) = BCCH_ARFCN(n)(MFS)
For Evolium serving cell:

- there can be up to 32 different BCCH 2G frequencies for the set of all the target cells for reselection (no matter the 2G/3G neighborhood of the serving cell for
reselection) .
- if the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells for
handover.
cells for handover.
Recommended --
rules
External --
comment
Internal comment - Needed for MPDCH feature. The ARFCN of the G1 band are in the range {975, 976, , 1023, 0}.
- The BCCH ARFCN of an adjacent external cell is directly editable in the HMI. The OMC-R access is defined accordingly (changeable). The BCCH ARFCN of an
adjacent internal cell is virtual changeable.
- The cell neighborhood for 3G handover is controlled by EN_3G_HO and FDD_ARFCN(n) values.
Logical BEP_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI BEP_PERIOD Sub-syste MFS Cell Type No
Definition Filter constant for EGPRS channel quality measurements.
Rec ref. 3GPP TS 05.08 Domai E-GPRS Min value 1 Coded Min 0
Coding rules coded on 4 bits as follows:
0: 1
1: 2
2: 3
3: 4
4: 5
5: 7
6: 10
7: 12
8: 15
9: 20
10: 25
11: Reserved for future use
Mandatory rules --
Recommended --
rules
External The BEP_PERIOD parameter defines the forgetting factor used in the MEAN_BEP and CV_BEP averaging at the MS side.
comment In case of cell without frequency hopping and without fast mobiles (i.e. not motorway or TGV coverage), it is advised to set a higher value (e.g. 25) in order to avoid
spurious MCS changes causing higher BLER and throughput loss.
Internal comment Only the values from 1 to 25 are displayed at the OMC-R.
Logical BEST_EFFORT_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI BEST_EFFORT_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for the pre-defined Best Effort Packet Flow Context, and for all MS traffic without PFC
Coding rules --
Mandatory rules --
Recommended --
rules
External Default value corresponds to the priority for interactive THP3.
comment The minimum value (the highest priority) corresponds to one priority level below the streaming class.
Internal comment --
Logical BIAS_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI BIAS_LIMIT Sub-syste MFS Cell Type No
Definition Transfer ratio above which the bias of the transfer is deemed as uplink (otherwise downlink).
Mandatory rules BIAS_LIMIT <= BIAS_LIMIT_EDA
Recommended --
rules
External --
comment
Internal comment Default value computed based on default values of N_BIAS_DETERMINATION and WEIGHT_BIAS_DETERMINATION to use uplink-biased configurations during ping
series (in case EUTM is used).
Logical BIAS_LIMIT_EDA B11 Yes B12 Yes
name TRX nb No
HMI BIAS_LIMIT_EDA Sub-syste MFS Cell Type No
Definition Minimum transfer ratio observed to allow a mobile station to use Extended Dynamic Allocation.
Mandatory rules BIAS_LIMIT_EDA >= BIAS_LIMIT
Recommended --
rules
External This parameter allows using EDA only when the bias of the transfer is significantly uplink.
comment
Internal comment BIAS_LIMIT_EDA shall be set to a value high enough to avoid triggering EDA in ping scenarios. BIAS_LIMIT_EDA shall be tuned versus BIAS_DETERMINATION and
WEIGHT_BIAS_DETERMINATION (the current default value of 2 has been tuned considering BIAS_DETERMINATION=3Kbytes,
WEIGHT_BIAS_DETERMINATION=70%
and max ping size around 1500 bytes). If BIAS_LIMIT_EDA is set to 1, this means the transfer ratio is not taken into account to allow EDA (only the bias is considered).
Logical BS_AG_BLKS_RES (MFS) B11 Yes B12 Yes
name TRX nb No
HMI BS_AG_BLKS_RES Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Number of CCCH blocks reserved for the access grant channel (AGCH), broadcast on the PBCCH for CS service establishment.
Coding rules coded on 3 bits (000 : 0, ...111 : 7)
Mandatory rules same as BS_AG_BLKS_RES (BSC)
Recommended --
rules
External - Parameter change:
comment no impact on the telecom service, on going traffic is not disrupted. But any modification impacts Paging (paging queues are reset and paging is suspended until the
reconfiguration is completed).
Internal comment Needed for MPDCH feature.
Logical BS_CV_MAX (MFS) B11 Yes B12 Yes
name TRX nb No
HMI BS_CV_MAX Sub-syste MFS Cell Type No
Definition Number of remaining RLC data blocks sent (per assigned PDCH) by the MS, below which the Count Down procedure is entered.
One third of the number of RLC data blocks per assigned PDCH before the MS checks if the resolution contention has failed.
Coding rules Coded on 4 bits (1==0001, 2 == 0010 .. 15 == 1111).
Mandatory rules Equal to BS_CV_MAX (BSC)
Recommended BS_CV_MAX should be set to a value equal to the "minimum" round trip delay to optimise the uplink re-transmission of non-acknowledged blocks and minimise
rules window-stalled situations.
If BS_CV_MAX is set greater than round-trip-delay, uplink retransmissions of unacknowledged blocks may be delayed.
- BS_CV_MAX = 9 if GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell,
- BS_CV_MAX = 15 if GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell.
External Used by the MS to start the countdown value process (release of UL TBF) or to consider acknowledgement messages as valid for a given RLC data block. Lower
comment values avoid too many TBF releases and reestablishments.
Internal comment --
Logical BS_PA_MFRMS (MFS) B11 Yes B12 Yes
name TRX nb No
HMI BS_PA_MFRMS Sub-syste MFS Cell Type No
Definition Number of 51 frame multiframes between consecutive occurrences of a Paging Group, broadcast on the PBCCH for the CS service establishment.
Coding rules coded on 3 bits (000 : 2, ... 111: 9)
Mandatory rules BS_PA_MFRMS (BSC) = BS_PA_MFRMS (MFS) for a given cell
Recommended --
rules
comment
Logical BS_PAG_BLKS_RES B11 Yes B12 Yes
name TRX nb No
HMI BS_PAG_BLKS_RES Sub-syste MFS Cell Type No
Definition Number of blocks allocated to the PAGCH or PDTCH or PACCH per 52 multiframe.
Coding rules coded on 4 bits (0001: 1, ..., 1010: 10)
The codepoints 0000: 0, 1011: 11 and 1100: 12 are not supported by the ALCATEL BSS.
Mandatory rules BS_PAG_BLKS_RES < 12 BS_PBCCH_BLKS
Recommended --
rules
External According to 3GPP TS 05.02, the number of paging blocks available on one PCCCH =
comment (12 - BS_PAG_BLKS_RES - BS_PBCCH_BLKS) * 64. In order for the network to be able to page GPRS-attached Mobile Stations when PCCCH is present in the cell,
there shall be at least one radio block where paging can occur. This requires (12 - BS_PAG_BLKS_RES - BS_PBCCH_BLKS) to be strictly greater than 0.
Logical BS_PBCCH_BLKS B11 Yes B12 Yes
name TRX nb No
HMI BS_PBCCH_BLKS Sub-syste MFS Cell Type No
Definition Number of blocks allocated to the PBCCH per 52 multiframe.
Coding rules coded on 2 bits : 00=Block B0 used for PBCCH, 01=Block B0, B6 used for PBCCH, 10=Block B0, B6, B3 used for PBCCH, 11=Block B0, B6, B3, B9 used for PBCCH
Mandatory rules BS_PBCCH_BLKS < 12 - BS_PAG_BLKS_RES
Recommended --
rules
External --
comment
Logical BS_PRACH_BLKS B11 Yes B12 Yes
name TRX nb No
HMI BS_PRACH_BLKS_MIN Sub-syste MFS Cell Type No
Definition Number of blocks statically allocated to the PRACH per 52 multiframe on each MPDCH.
Coding rules coded on 4 bits (0001: 1, .., 1000: 8)
Mandatory rules --
Recommended --
rules
External --
comment
Logical BS_PRR_BLKS B11 Yes B12 Yes
name TRX nb No
HMI BS_PRR_BLKS_SPDCH Sub-syste MFS Cell Type No
Definition Maximum number of radio blocks that may be allocated to Packet Resource Request message for two-phase access UL TBF establishment, Packet Measurement Report
message, or Packet Cell Change Failure message. This maximum number is defined per 52-multiframe on each uplink slave PDCH.
Category System (CST) OMC-R access None (DLS) Type Number Unit radio blocks
Spec ref. GPRS Radio interface - MAC sublayer Coded Max 12
Coding rules 6 possible values (1;2;3;4;6;12)
Mandatory rules BS_PRR_BLKS_MPDCH <= BS_PRR_BLKS
Recommended --
rules
External --
comment
Internal comment This parameter only applies to cells where there is no PCCCH.
Logical BS_PRR_BLKS_MPDCH B11 Yes B12 Yes
name TRX nb No
HMI BS_PRR_BLKS_MPDCH Sub-systeMFS Cell Type No
Definition Maximum number of radio blocks that may be allocated to Packet Resource Request message for two-phase access UL TBF establishment, Packet Measurement Report
message, or Packet Cell Change Failure message. This maximum number is defined per 52-multiframe on each uplink master PDCH.
Category System (CST) OMC-R access None (DLS) Type Number Unit radio blocks
Coding rules 6 possible values (1;2;3;4;6;12)
Mandatory rules BS_PRR_BLKS_MPDCH <= BS_PRR_BLKS
Recommended --
rules
External --
comment
Internal comment number blocks per multiframe which are available for a Packet Resource Request.
Needed for MPDCH feature.
This parameter only applies to cells where there is at least one PCCCH.
Logical BS_TXPWR_MAX (MFS) B11 Yes B12 Yes
name TRX nb No
HMI BS_TXPWR_MAX Sub-syste MFS Cell Type No
Definition This parameter defines the power reduction relative to the attenuated maximum GMSK output power of the BTS.
A finer power attenuation, BS_TXPWR_ATTENUATION defined in step of 0.1dB, is managed instead.
0 0 0 0 = 0 dB,
0 0 0 1 = -2 dB,
0 0 1 0 = -4 dB,
..., 1 1 1 1 = -30 dB
Mandatory rules Equal to BS_TXPWR_MAX (BSC)
Recommended --
rules
comment
Internal comment - With the RFD252615, fine BTS power level from the OMC, this parameter is not directly managed by the operator anymore (greyed on the HMI).
Logical BSC_ID(n) B11 Yes B12 Yes
name TRX nb No
HMI BSC_ID Sub-syste MFS Cell Type No
Definition BSC identifier of an adjacent cell.
Coding rules Only values [1..255] are significant.
Value 0 means that the cell is external to the OMC.
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical BSS_TRANSPORT_MODE (MFS) B11 Yes B12 Yes
name TRX nb No
HMI BSS_TRANSPORT_MODE Sub-systeMFS Cell Type No
Definition IP Transport mode for Ater level signalling links (GSL, Qmux/TCSL, N7, knowing only GSL applies to the MFS): TDM or IP
Coding rules 0 : TDM, 1 :IP
Mandatory rules - Can be set to IP on MFS side for the BSS, only if, before, it has been set to IP on BSC side.
Recommended --
rules
External - IP transport in BSS is available on MFS Evolution only.
comment - Parameter change: Any modification of the parameter leads the MFS to reset autonomously all the GPs connected to this BSS.
Internal comment --
Logical bssgp_T1 B11 Yes B12 Yes
name TRX nb No
HMI T1 Sub-syste MFS Cell Type No
Definition Guards the (un)blocking procedures.
Spec ref. GPRS Gb interface - BSSGP layer Coded Max 30
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Guards the reset procedure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
HMI BSSGP_T3 Sub-syste MFS Cell Type No
Definition Timer used by PCU to wait for Suspend acknowledgement from SGSN.
Rec ref. GSM TS 08.18 Domai GPRS Min value 0.1 Coded Min 1
Coding rules 1:0,1 ; 2: 0,2 ; ; 10: 1 ; ; 100: 10
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
HMI BSSGP_T4 Sub-syste MFS Cell Type No
Definition Timer used by PCU to wait for Resume acknowledgement from SGSN.
Coding rules 1:0,1 ; 2: 0,2 ; ; 10: 1 ; ; 100: 10
Mandatory rules --
Recommended BSSGP_T4 < T_GPRS_Resume/ (Resume_retries+1))

rules
External --
comment
Internal comment --
Logical BTS_LOAD_FORGETTING_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI BTS_LOAD_FORGETTING_FACTOR Sub-syste MFS Cell Type No
Definition Forgetting factor of the filter used to compute the CPU load of an SCP (for a given TRE module) over the last 20 ms periods.
Spec ref. Overload control (CPU and memory) Coded Max 128
Coding rules --
Mandatory rules --
Recommended --
rules
External Applicable only to IP transport.
comment
Internal comment - The highest the BTS_LOAD_FORGETTING_FACTOR value, the highest the likelihood for an SCP CPU load peak (i.e. a load increase followed by a load decrease in a
short period of time) to be notified to RRM. And such a notification wil result in some TBF traffic blocking in RRM during the entire next
T_BTS_LOAD_REPORT_WITH_TRANSITION period.
- The lowest the BTS_LOAD_FORGETTING_FACTOR value, the less reactive RRM will be in case of SCP CPU load increase (potential risk for a TRE module to reach
an SCP CPU load close to 100% before RRM begins to react by blocking some TBF traffic).
- The value of the forgetting factor in percent is BTS_LOAD_FORGETTING_FACTOR / 128 * 100%.
Logical BVC_BLOCK_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI BVC BLOCK RETRIES Sub-syste MFS Cell Type No
name Instance NSE RMS No
Definition Number of retries of the BVC Blocking procedure.
Spec ref. GPRS Gb interface - BSSGP Layer Coded Max 3
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical BVC_RESET_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI BVC RESET RETRIES Sub-syste MFS Cell Type No
Definition Number of retries of theBVC RESET procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical BVC_UNBLOCK_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI BVC_UNBLOCK_RETRIES Sub-syste MFS Cell Type No
Definition Number of retries of the BVC Unblocking procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical C31_HYST B11 Yes B12 Yes
name TRX nb No
HMI C31_HYST Sub-syste MFS Cell Type No
Definition Determines whether an additional cell hysteresis shall be applied to the C31 criterion. The hysteresis is GPRS_CELL_RESELECT_HYSTERESIS (for NC0 mode).
Coding rules 0 : no, 1 : yes
Mandatory rules --
Recommended --
rules
External --
comment
Logical C32_QUAL B11 Yes B12 Yes
name TRX nb No
HMI C32_QUAL Sub-syste MFS Cell Type No
Definition Flag indicating an exception rule for GPRS_RESELECT_OFFSET in NC0 mode.
Coding rules 0=NO, 1=YES
Mandatory rules --
Recommended --
rules
External --
comment
Logical CBS B11 Yes B12 Yes
name TRX nb No
HMI Commited Burst Size Sub-syste MFS Cell Type No
name Instance PVC RMS No
Definition Commited Burst Size.
Category Site (CAE) OMC-R access Changeable Type Number Unit kbyte
Coding rules --
Mandatory rules CIR=0 <=> CBS=0 => EBS > 0

CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC
Recommended --
rules
comment
Internal comment --
Logical CCCH_CONF (MFS) B11 Yes B12 Yes
name TRX nb No
HMI CCCH_CONF Sub-syste MFS Cell Type No
Definition Configuration of the CCCH, broadcast on the PBCCH for CS service establishment.
Spec ref. Packet system information management Coded Max 6
0: one CCCH not combined (TS0),
1: one CCCH combined (TS0)
2: two CCCH not combined (TS0+2)
4: three CCCH not combined (TS0+2+4)
6: four CCCH not combined (TS0+2+4+6)
Mandatory rules same as CCCH_CONF (BSC)
Recommended same as CCCH_CONF (BSC)

rules
External --
comment
Logical CELL_RANGE (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Cell Range Sub-syste MFS Cell Type Yes
Definition Determines if the cell belongs to an extended cell.
Coding rules 0: Normal cell, 1: Outer cell, 2: Inner cell
Mandatory rules CELL-RANGE(MFS) = CELL_RANGE(BSC)

Shall be consistent with CELL_TYPE.
A couple of mate cells (Extended inner + extended outer) shall have the same LAC (respectively RAC when they are PS capable)
Recommended --
rules
External --
comment
Internal comment The CELL_RANGE parameter is not displayed as such to the O&M user.
Logical CELL_RESELECT_OFFSET (MFS) B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_OFFSET Sub-syste MFS Cell Type No
Mandatory rules CELL_RESELECT_OFFSET (MFS) = CELL_RESELECT_OFFSET (BSC)
Recommended --
rules
External --
comment
Logical CELL_RESELECT_OFFSET(n)(MFS) B11 Yes B12 Yes
name TRX nb No
HMI CELL_RESELECT_OFFSET Sub-syste MFS Cell Type No
Mandatory rules CELL_RESELECT_OFFSET(n)(MFS) = CELL_RESELECT_OFFSET (n)(BSC)
Recommended --
rules
External --
comment
Logical CHANNEL_REQ_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI CHANNEL_REQ_PERIOD Sub-syste MFS Cell Type No
Definition Period value of the limitation mechanism of the PCU. During each period, the PCU could limit the number of CHANNEL REQUEST messages received from the BSC on the
BSCGP interface. Over a given threshold, the new coming CHANNEL REQUEST messages are simply discarded until the end of the current period.
Category System (CST) OMC-R access None (not in DLS) Type Number Unit ms
Coding rules --
Mandatory rules --
Recommended Avoid multiple and divisor of 1 sec, because of the MS retry periodicity (the range is depending on Tx_integer and CCCH_CONF)
rules
External --
comment
Internal comment --
Logical CHANNEL_REQ_THRES_GP2 B11 Yes B12 Yes
name TRX nb No
HMI CHANNEL_REQ_THRES_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of CHANNEL REQUEST messages per second received from the BSC on the BSCGP interface, that will be accepted/processed by the GP board of the
Mx-MFS. Over that threshold, the new coming CHANNEL REQUEST messages are simply discarded until the end of the current period.
Coding rules --
Mandatory rules could not be greater than MAX_CTXT_MS_GP2
Recommended --
rules
External Applicable to GP2 board
comment
Internal comment --
Logical CHANNEL_REQ_THRES_GP3 B11 No B12 Yes
name TRX nb No
HMI CHANNEL_REQ_THRES_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of CHANNEL REQUEST messages per second received from the BSC on the BSCGP interface, that will be accepted/processed by the GP board of the
Mx-MFS. Over that threshold, the new coming CHANNEL REQUEST messages are simply discarded until the end of the current period.
Coding rules --
Mandatory rules could not be greater than MAX_CTXT_MS_GP3
Recommended --
rules
comment
Internal comment --
Logical CI (MFS) B11 Yes B12 Yes
name TRX nb No
HMI CI Sub-syste MFS Cell Type No
Definition Cell Identity.
Coding rules --
Equal to CI (BSC)
Recommended --
rules
comment
Internal comment --
Logical CI(n) (MFS) B11 Yes B12 Yes
name TRX nb No
HMI CI Sub-syste MFS Cell Type No
Definition Cell Identity of adjacent cell.
Coding rules Values 0..65535 correspond to the standard CI-value.
Equal to CI(n)(BSC).
Recommended --
rules
comment
Internal comment --
Logical CIR B11 Yes B12 Yes
name TRX nb No
HMI Committed Information Rate Sub-syste MFS Cell Type No
Definition Committed Information Rate.
Coding rules --
Mandatory rules CIR=0 when direct access is used, CIR=0 <=> CBS=0 => EBS > 0
Recommended --
rules
comment
Internal comment --
Logical CN_ID_PS B11 Yes B12 Yes
name TRX nb No
HMI SGSN_ID Sub-syste MFS Cell Type No
Definition This parameter uniquely identifies one SGSN inside one BSS for the Gbflex feature.
For that, the operator has the possibility to use the Core Network Identifier, which is part of the Global Core Network Identifier, defined in 3GPP TS 23.003 as (PLMN-id +
CN-id). But in such case, the same identifier can identify 2 different SGSN, belonging to 2 different PLMN.
Mandatory rules - All the NSEs of one GP/GPU must have different CN_ID_PS.
Recommended - The operator must control that, in a BSS, 2 SGSNs must have 2 different CN_ID_PS.
rules - For a BSS in multi-GP/GPU configuration, for a consistent behaviour of the Gbflex feature, the operator must connect all the GP/GPU(s) to the same SGSN(s) and
define the same CN_ID_PS on all the NSEs, connected to one SGSN.
- It is highly recommended to extend that rule (same CN_ID_PS value for all the NSEs connected to one SGSN) in all the BSSs managed by the MFS; and even more, in
the whole managed network.
External - Significant only if EN_GB_FLEX is enabled
comment - The default value depends on the configuration. The value given here is for implementation purposes only.
- The operator must control that the BSS and all the SGSNs connected to that BSS via Gbflex feature must belong to the same PLMN.
Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Internal comment - The highly recommended rule is for PM aggregation concern at SGSN level (whichever the connected MFS and BSS).
Logical CONFIDENCE_ORIGIN B11 Yes B12 Yes
name TRX nb No
HMI CONFIDENCE_ORIGIN Sub-syste MFS Cell Type No
Definition Confidence origin used in the 3D linear regression of the confidence of the ellipsoid arc returned by the MFS when providing the reference location to the A-GPS server.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CONFIDENCE_VS_ARC_FACTOR_SLOPE B11 Yes B12 Yes
name TRX nb No
HMI CONFIDENCE_VS_ARC_FACTOR_SLOPE Sub-syste MFS Cell Type No
Definition Slope ratio between the confidence and the arc factor used in the 3D linear regression of the confidence of the ellipsoid arc returned by the MFS when providing the
reference location to the A-GPS server.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CONFIDENCE_VS_RADIUS_SLOPE B11 Yes B12 Yes
name TRX nb No
HMI CONFIDENCE_VS_RADIUS_SLOPE Sub-syste MFS Cell Type No
Definition Slope ratio between the confidence and the sum of minimum radius factor and maximum radius factor used in the 3D linear regression of the confidence of the ellipsoid
arc returned by the MFS when providing the reference location to the A-GPS server.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_AVG_PERIOD_LT B11 Yes B12 Yes
name TRX nb No
HMI CS_AVG_PERIOD_LT Sub-syste MFS Cell Type No
Definition "Forgetting time in the long term averaging of channel quality measurements in the GPRS link Adaptation: measurements which are older than CS_AVG_PERIOD_LT are
negligible in the average of channel quality measurements.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit sec
Rec ref. None Domai GPRS Min value 0.02 Coded Min 1
Spec ref. GPRS radio interface - RLC sublayer Coded Max 250
Mandatory rules --
Recommended --
rules
External Parameter change: any modification impacts the telecom PS service. The on-going PS traffic of the BSS is broken and no new traffic is accepted until the related
comment PMU(s) restarted.
Internal comment see also CS_AVG_PERIOD_LT_DEF_VALUE (CS_AVG_PERIOD_LT is assumed rarely modified on the fields)
Logical CS_AVG_PERIOD_LT_DEF_VALUE B11 Yes B12 Yes
name TRX nb No
HMI CS_AVG_PERIOD_LT_DEF_VALUE Sub-syste MFS Cell Type No
Definition Default value of the "Forgetting time in the long term averaging of channel quality measurements in the GPRS link Adaptation.
This default value is used in IP transmission mode as an input for the Link Adaptation computation process following a TRE starting.
Category System (CST) OMC-R access None (not in DLS) Type Threshold Unit sec
Spec ref. PMU-PTU interface Coded Max 100
Mandatory rules shall be equal to the default value of CS_AVG_PERIOD_LT
Recommended --
rules
External --
comment
Internal comment this parameter is hard-coded in the BTS.
Logical CS_AVG_PERIOD_ST B11 Yes B12 Yes
name TRX nb No
HMI CS_AVG_PERIOD_ST Sub-syste MFS Cell Type No
Definition "Forgetting time" in the short term averaging of channel quality measurements in the GPRS link adaptation: measurements which are older than CS_AVG_PERIOD_ST are
negligible in the average of channel quality measurements.
Category Site (CAE) OMC-R access Changeable Type Threshold Unit sec
Mandatory rules --
Recommended --
rules
Internal comment see also CS_AVG_PERIOD_ST_DEF_VALUE (CS_AVG_PERIOD_ST is assumed rarely modified on the fields)
Logical CS_AVG_PERIOD_ST_DEF_VALUE B11 Yes B12 Yes
name TRX nb No
HMI CS_AVG_PERIOD_ST_DEF_VALUE Sub-syste MFS Cell Type No
Definition Default value of the "Forgetting time" in the short term averaging of channel quality measurements in the GPRS link adaptation.
Category System (CST) OMC-R access None (not in DLS) Type Threshold Unit sec
Mandatory rules shall be equal to the default value of CS_AVG_PERIOD_ST
Recommended --
rules
External --
comment
Logical CS_BLER_DL_3_4 B11 Yes B12 Yes
name TRX nb No
HMI CS_BLER_DL_3_4 Sub-syste MFS Cell Type No
Definition CS3 BLER threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the SIR measurements are not
reported by the MS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_BLER_DL_4_3 B11 Yes B12 Yes
name TRX nb No
HMI CS_BLER_DL_4_3 Sub-syste MFS Cell Type No
Definition CS4 BLER threshold used in the link adaptation algorithms to change the Coding Scheme from CS4 to CS3 in the downlink direction when the SIR measurements are not
reported by the MS.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_HST_DL_LT B11 Yes B12 Yes
name TRX nb No
HMI CS_HST_DL_LT Sub-syste MFS Cell Type No
Definition Hysteresis value for AV_RXQUAL_LT thresholds used in the downlink radio link supervision to change the TBF coding scheme.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_HST_DL_ST B11 Yes B12 Yes
name TRX nb No
HMI CS_HST_DL_ST Sub-syste MFS Cell Type No
Definition Hysteresis value for AV_RXQUAL_ST thresholds used in the downlink radio link supervision to change the TBF coding scheme.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_HST_UL_LT B11 Yes B12 Yes
name TRX nb No
HMI CS_HST_UL_LT Sub-syste MFS Cell Type No
Definition Hysteresis value for AV_RXQUAL_LT thresholds used in the uplink radio link supervision to change the TBF coding scheme.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_HST_UL_ST B11 Yes B12 Yes
name TRX nb No
HMI CS_HST_UL_ST Sub-syste MFS Cell Type No
Definition Hysteresis value for AV_RXQUAL_ST thresholds used in the uplink radio link supervision to change the TBF coding scheme.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_MAX_IDLE_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI CS_MAX_IDLE_PERIOD Sub-syste MFS Cell Type No
Definition Maximum transfer inactivity time to reuse the previous (Modulation and) Coding Scheme. This applies in case of transfer resumption during inactive TBF phase (delayed
downlink TBF mode / extended uplink TBF mode) and in case of uplink TBF establishment on PACCH while extended uplink TBF mode is not used (with some additional
restrictions).
Mandatory rules --
Recommended --
rules
External This parameter applies to both GPRS and EGPRS TBFs.
comment
Internal comment --
Logical CS_QUAL_DL_1_2_FH_ACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_DL_1_2_FH_ACK Sub-syste MFS Cell Type No
Definition RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the downlink direction when the RLC mode is acknowledged
and the TBF is established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_QUAL_DL_1_2_FH_NACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_DL_1_2_FH_NACK Sub-syste MFS Cell Type No
Definition RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the downlink direction when the RLC mode is unacknowledged
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_QUAL_DL_1_2_NFH_ACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_DL_1_2_NFH_ACK Sub-syste MFS Cell Type No
and the TBF is established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_QUAL_DL_1_2_NFH_NACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_DL_1_2_NFH_NACK Sub-syste MFS Cell Type No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_QUAL_UL_1_2_FH_ACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_UL_1_2_FH_ACK Sub-syste MFS Cell Type No
Definition RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is acknowledged and
the TBF is established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Min value = (Coded Min - 30) / 10;
Def value = (Coded_default - 30) / 10;
Max value = (Coded Max - 30) / 10.
Logical CS_QUAL_UL_1_2_FH_NACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_UL_1_2_FH_NACK Sub-syste MFS Cell Type No
Definition RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is unacknowledged
Mandatory rules --
Recommended --
rules
External --
comment
Logical CS_QUAL_UL_1_2_NFH_ACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_UL_1_2_NFH_ACK Sub-syste MFS Cell Type No
Definition RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is acknowledged and
the TBF is established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Logical CS_QUAL_UL_1_2_NFH_NACK B11 Yes B12 Yes
name TRX nb No
HMI CS_QUAL_UL_1_2_NFH_NACK Sub-syste MFS Cell Type No
Definition RXQUAL threshold used in the link adaptation algorithms to change the Coding Scheme from CS1 to CS2 in the uplink direction when the RLC mode is unacknowledged
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
Definition Threshold used in the link adaptation algorithms to change the Coding Scheme from CS2 to CS3 in the uplink direction when the RLC mode is acknowledged and the TBF is
established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Threshold used in the link adaptation algorithms to change the Coding Scheme from CS2 to CS3 in the uplink direction when the RLC mode is unacknowledged and the TBF
is established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
is established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
is established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
is established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_SIR_DL_3_4_FH_ACK B11 Yes B12 Yes
name TRX nb No
HMI CS_SIR_DL_3_4_FH_ACK Sub-syste MFS Cell Type No
Definition Signal to Interference Ratio threshold used in the link adaptation algorithms to change the Coding Scheme from CS3 to CS4 in the downlink direction when the RLC mode is
acknowledged and the TBF is established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_SIR_DL_3_4_FH_NACK B11 Yes B12 Yes
name TRX nb No
HMI CS_SIR_DL_3_4_FH_NACK Sub-syste MFS Cell Type No
unacknowledged and the TBF is established on a hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_SIR_DL_3_4_NFH_ACK B11 Yes B12 Yes
name TRX nb No
HMI CS_SIR_DL_3_4_NFH_ACK Sub-syste MFS Cell Type No
acknowledged and the TBF is established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_SIR_DL_3_4_NFH_NACK B11 Yes B12 Yes
name TRX nb No
HMI CS_SIR_DL_3_4_NFH_NACK Sub-syste MFS Cell Type No
unacknowledged and the TBF is established on a non-hopping TRX.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical CS_SIR_HST_DL B11 Yes B12 Yes
name TRX nb No
HMI CS_SIR_HST_DL Sub-syste MFS Cell Type No
Definition Signal to Interference Ratio hysteresis used in the link adaptation algorithms to change the Coding Scheme from CS4 to CS3 in the downlink direction.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Def_value_T_Flow_Ctrl_Cell B11 Yes B12 Yes
name TRX nb No
HMI Def_value_T_Flow_Ctrl_Cell Sub-syste MFS Cell Type No
Definition Timer used for calculation of BVC bucket size when T_Flow_Ctrl_Cell = 0.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Def_value_T_Flow_Ctrl_MS B11 Yes B12 Yes
name TRX nb No
HMI Def_value_T_Flow_Ctrl_MS Sub-syste MFS Cell Type No
Definition Timer used for calculation of Bmax_default_MS when T_Flow_Ctrl_MS = 0.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical DELAY_FORCED_LOAD_REPORT B11 Yes B12 Yes
name TRX nb No
HMI DELAY_FORCED_LOAD_REPORT Sub-syste MFS Cell Type No
Definition Number of 20ms periods before the DSP reports its CPU load to PMU once the DSP load reaches 100% (i.e no load measurement in a such ms period because the
corresponding DSP task cannot run).
Coding rules --
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment
Internal comment --
Logical DL_POLL_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI DL_DATA_CREDIT Sub-syste MFS Cell Type No
Definition This parameter defines the slope in credit computation for the downlink cyclic polling algorithm.
Coding rules --
Mandatory rules --
Recommended --
rules
External The max number of downlink TBFs assigned per PDCH shall be such that the periodicity of polling needed for Channel Quality reports is respected (taking into account
comment needed bandwidth for PACCH en downlink).
Internal comment --
Logical DLCI B11 Yes B12 Yes
name TRX nb No
HMI Data Link Connection Identifier Sub-syste MFS Cell Type No
Definition Data Link Connection Identifier, corresponds to a PVC identifier, see Q.922 Annex A, Table 1.
Rec ref. ITU-T Q.922 Domai GPRS Min value 16 Coded Min 16
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical DRX_TIMER_MAX (MFS) B11 Yes B12 Yes
name TRX nb No
HMI DRX_TIMER_MAX Sub-syste MFS Cell Type No
Definition Maximum value allowed for the MS to request for non-DRX mode after packet transfer mode.
Coding rules Radio coding :Possible values : 0, 1, 2, 4, 8, 16, 32, 64 respectively binary coded as 000, 001, , 111
ONLY THE VALUES 0, 1, 2 AND 4 ARE POSSIBLE in ALCATEL BSS.
Mandatory rules Equal to DRX_TIMER_MAX (BSC)
Recommended --
rules
External --
comment
Sent on PSI 13 on PACCH when no MPDCH
Logical DSP_LOAD_FORGETTING_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI DSP_LOAD_FORGETTING_FACTOR Sub-syste MFS Cell Type No
Definition Forgetting factor of the filter used to compute the CPU load of a DSP over the last 20 ms periods.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment - The highest the DSP_LOAD_FORGETTING_FACTOR value, the highest the likelihood for a DSP CPU load peak (i.e. a load increase followed by a load decrease in a
short period of time) to be notified to RRM. And such a notification wil result in some TBF traffic blocking in RRM during the entire next T_DSP_LOAD_REPORT period.
- The lowest the DSP_LOAD_FORGETTING_FACTOR value, the less reactive RRM will be in case of DSP CPU load increase (potential risk for a DSP to reach a CPU
load close to 100% before RRM begins to react by blocking some TBF traffic).
- The value of the forgetting factor in percent is DSP_LOAD_FORGETTING_FACTOR / 128 * 100%
Logical DSP_LOAD_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI DSP_LOAD_THR_1 Sub-syste MFS Cell Type No
Definition Threshold beyond which a given DSP is considered as "loaded" in terms of CPU load by RRM.
Category System (CST) OMC-R access None (DLS) Type Threshold Unit %
Mandatory rules DSP_LOAD_THR_1 < DSP_LOAD_THR_2
Recommended --
rules
External Applicable to TDM only.
comment
Internal comment --
Logical DSP_LOAD_THR_2 B11 Yes B12 Yes
name TRX nb No
HMI DSP_LOAD_THR_2 Sub-syste MFS Cell Type No
Definition Threshold beyond which a given DSP is considered as "overloaded" in terms of CPU load by RRM.
Coding rules step size = 1 %
Mandatory rules DSP_LOAD_THR_1 < DSP_LOAD_THR_2
Recommended --
rules
External Applicable to TDM only.
comment
Internal comment --
Logical DTX_INDICATOR (MFS) B11 Yes B12 Yes
name TRX nb No
HMI (Not applicable) Sub-syste MFS Cell Type No
Definition Controls uplink DTX usage for GSM phase 1 MS.
Coding rules coded over 2 bits. 0: MS may use uplink DTX, 1: MS shall use uplink DTX, 2: MS shall not use uplink DTX
Mandatory rules Equal to DTX_INDICATOR (BSC)
Recommended --
rules
External DTX_INDICATOR calculated from DTX_INDICATOR_FR
comment
Internal comment this parameter is used to set the value of the DTX field in cell Options (BCCH) IE in SYSTEM INFORMATION TYPE 3 and in cell Options (SACCH) IE in SYSTEM
INFORMATION TYPE 6 in some cases
Needed for MPDCH feature.
The DTX_INDICATOR (MFS) parameter is not displayed as such to the O&M user.
Logical E_TX_EFFICIENCY_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI E_TX_EFFICIENCY_PERIOD Sub-syste MFS Cell Type No
Definition Number of received radio blocks for an EGPRS TBF after which E_TX_EFFICIENCY is computed.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EBS B11 Yes B12 Yes
name TRX nb No
HMI Excess Burst Size Sub-syste MFS Cell Type No
Definition Excess Burst Size.
Category Site (CAE) OMC-R access Changeable Type Number Unit kbyte
Coding rules --
Mandatory rules CIR=0 <=> CBS=0 => EBS > 0

Recommended EBS=FR_CAPACITY(expressed in kbit/s) / 8, if CIR=0

rules
comment
Internal comment --
Logical EDA_MS_ACTIVATION_LEVEL B11 Yes B12 Yes
name TRX nb No
HMI EDA_MS_ACTIVATION_LEVEL Sub-syste MFS Cell Type No
Definition Activation level of Extended Dynamic Allocation (EDA).
Coding rules 0: EDA activated for all mobile stations (supporting the feature),
1: EDA activated for R99-onwards mobile stations (supporting the feature),
2: EDA activated for Rel-4-onwards mobile stations (supporting the feature).
Mandatory rules --
Recommended --
rules
External -This parameter is relevant only if EDA is activated (EN_EDA parameter).
comment -The activation level may provide an artificial mean to limit the inter-operability risks due to mobile stations with uncorrected EDA implementation (EDA is a R97 feature
but has been completely clarified in Rel-6).
- R99 is detected through the Revision Level Indicator.
- A mobile station is considered as Rel4-onwards compliant if it indicates the field "GERAN Feature Package 1" in its MS Radio Access Capability.
Internal comment - Further releases have not been considered since there is no same mean to detect if a mobile station is compliant with them.
Logical EGPRS_DL_Ack_Factor B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_DL_Ack_Factor Sub-syste MFS Cell Type No
Definition If the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the ratio between the number of transmitted RLC data blocks
necessary to request for a EGPRS Packet Downlink Ack Nack in acknowledged mode, and the RLC window size
Coding rules step size =0.01
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EGPRS_DL_ACK_factor_Satellite B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_DL_ACK_factor_Satellite Sub-syste MFS Cell Type No
Definition If the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the downlink EGPRS ARQ period factor: Acknowledgement period over
window size ratio.
Coding rules step size: 0.01
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is used by the MFS only if round_trip_delay >= 500 ms and shall be tuned according to the simulation result.
Logical EGPRS_LLC_THROUGHPUT_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_LLC_THROUGHPUT_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the 1st class, lower limit of the 2nd class for EGPRS LLC THROUGHTPUT distribution
Category System (CST) OMC-R access None (DLS) Type Number Unit kbit/s
Spec ref. MFS counters catalogue Coded Max 10
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Lower limit of the 10th class for EGPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th class for EGPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 2st class, lower limit of the 3rd class for EGPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd class, lower limit of the 4th class for EGPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th class, lower limit of the 5th class for EGPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EGPRS_N3105_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_N3105_LIMIT Sub-syste MFS Cell Type No
Definition For a DL EGPRS TBF, if the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the maximum number of expected Packet
Downlink ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF. This
parameter is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.
Spec ref. GPRS Radio interface - RLC sublayer Coded Max 32
Coding rules --
Mandatory rules --
Recommended --
rules
External If EGPRS_N3105_LIMIT < TBF_MCS_DL then the loss of consecutive packet DL ACK/NACK will not trigger link adaptation but TBF release. EGPRS_N3105_Limit has to
comment be set in order not to release a DL TBF in case of transient bad radio conditions.The polling frequency depends on Ack_factor, T_DL_EGPRS_MeasReport, MS
multislot class and on the number of TBFs per PDCH.
Internal comment --
Logical EGPRS_N3105_LIMIT_SATELLITE B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_N3105_LIMIT_SATELLITE Sub-syste MFS Cell Type No
Definition For a DL EGPRS TBF, if the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the maximum number of expected Packet
Coding rules --
Mandatory rules --
Recommended --
rules
External If EGPRS_N3105_LIMIT_SATELLITE < TBF_MCS_DL then the loss of consecutive packet DL ACK/NACK will not trigger link adaptation but TBF release.
comment EGPRS_N3105_Limit_Satellite has to be set in order not to release a DL TBF in case of transient bad radio conditions.The polling frequency depends on Ack_factor,
T_DL_EGPRS_MeasReport, MS multislot class and on the number of TBFs per PDCH.
Logical EGPRS_UL_Ack_Factor B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_UL_Ack_Factor Sub-syste MFS Cell Type No
Definition If the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the ratio between the number of received RLC data blocks
necessary to send a Packet Uplink Ack/Nack in acknowledged mode, and the RLC window size.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EGPRS_UL_Ack_Factor_Satellite B11 Yes B12 Yes
name TRX nb No
HMI EGPRS_UL_Ack_Factor_Satellite Sub-syste MFS Cell Type No
Definition If the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the ratio between the number of received RLC data blocks necessary
to send a Packet Uplink Ack/Nack in acknowledged mode, and the RLC window size.
Mandatory rules --
Recommended --
rules
External --
comment
Logical EN_AUTONOMOUS_REROUTING B11 Yes B12 Yes
name TRX nb No
HMI EN_AUTONOMOUS_REROUTING Sub-syste MFS Cell Type No
Definition This flag enables / disables autonomous rerouting of DL LLC PDUs.
Mandatory rules --
Recommended It is recommended not to activate simultaneously extended UL TBF feature (EN_EXTENDED_UL_TBF) and the DL PDU rerouting feature
rules (EN_AUTONOMOUS_REROUTING)
External --
comment
Internal comment This flag enables the BSS to autonomously reroute pending DL LLC PDUs from the old cell to the new cell (in the same RA) in case there is a NSE change and the
SGSN does not support the inter-NSE rerouting optional R4 feature.
Logical EN_BS_PC_PS B11 No B12 Yes
name TRX nb No
HMI EN_BS_PC_PS Sub-syste MFS Cell Type No
Definition Flag to enable/disable the handling of packet downlink power control in a cell.
This power control applies to timeslots with PS in service.
It is composed of a static part (POW_RED_P0), independent of radio conditions, and of a dynamic part, which depends on the radio link conditions reported by the MS.
1: enabled
Mandatory rules - EN_BS_PC_PS can be enabled only if PC_MEAS_CHAN = 0 (downlink measurements for power control shall be made on BCCH)
Recommended - The packet downlink power control should be disabled in extended cell, due to the large radius of these cells.
rules
External - Function available on MFS Evolution, and supported on the G4 onwards TREs of the cell.
comment - In case of multiband cells, the packet downlink power control is handled only in the outer zone that carries the BCCH, ie where the PS service is established.
- In a cell, where the BCCH TRX is non-hopping or non-hopping/radio-hopping, the packet downlink power control is inefficient for the TBFs established on that TRX.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Logical EN_BSS_PAGING_COORDINATION (MFS) B11 Yes B12 Yes
name TRX nb No
HMI EN_BSS_PAGING_COORDINATION Sub-syste MFS Cell Type No
Definition Enables/disables the CS paging coordination managed in the BSS for MS in Packet Transfer Mode.
Mandatory rules - EN_BSS_PAGING_COORDINATION (MFS) = EN_BSS_PAGING_COORDINATION (BSC)

- can be enabled only if (network_operation_mode <> NMO I) and (round_trip_delay < 500 msec for all the cells of the BSS)
Recommended - if EN_BSS_PAGING_COORDINATION is set to enabled, it is highly recommended to set EN_RA_CAP_UPDATE to enabled.

rules - if EN_DTM is Enabled for at least one cell within the BSS it is highly recommended to activate CS Paging Coordination for the BSS, either through the Gs Interface
(network_operation_mode = NMO I) or by setting EN_BSS_PAGING_COORDINATION to Enabled (network_operation_mode <> NMO I).
- if a BSC is connected to a MFS but GPRS is disabled (EN_GPRS = false) for any cells of the BSS, it is recommended to set EN_BSS_PAGING_COORDINATION to
disabled for that BSS.
External The support of paging coordination in the BSS is not compatible with the "GPRS through satellite connection on Abis or Ater interface" feature.
comment
Logical EN_CBL B11 Yes B12 Yes
name TRX nb No
HMI EN_CBL Sub-syste MFS Cell Type No
Definition This flag enables / disables CBL feature (Leaky Bucket Synchronisation)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical EN_CONV_GPS B11 Yes B12 Yes
name TRX nb No
HMI EN_CONV_GPS Sub-syste MFS Cell Type No
Definition Flag to enable or disable the positioning method Conventional GPS.
Mandatory rules EN_CONV_GPS = 0
Recommended --
rules
External - The activation of this positioning method is meaningful when EN_LCS=1.
comment - Only the value 0 is supported
Internal comment --
Logical EN_CS_ADAPTATION_ACK B11 Yes B12 Yes
name TRX nb No
HMI EN_CS_ADAPTATION_ACK Sub-syste MFS Cell Type No
Definition Enables / disables the link adaptation in RLC acknowledged mode.
Coding rules 0: Disable; 1: Enable
Mandatory rules --
Recommended If EN_STREAMING = 1 then it is recommended to set EN_CS_ADAPTATION_ACK to TRUE in order to activate the link adaptation mechanism so that the (M)CS can
rules reach a suitable level regarding the level of the configured Rmin_(E)GPRS. Otherwise, the streaming PFCs can be downgraded to the Default Best Effort ABQP
because the negotiated GBR cannot be reached on the radio interface.
comment
Internal comment --
Logical EN_CS_ADAPTATION_NACK B11 Yes B12 Yes
name TRX nb No
HMI EN_CS_ADAPTATION_NACK Sub-syste MFS Cell Type No
Definition Enables / disables the link adaptation in RLC unacknowledged
Coding rules 0: Disable; 1: Enable
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical EN_DL_LLC_PDU_REROUTING B11 Yes B12 Yes
name TRX nb No
HMI EN_DL_LLC_PDU_REROUTING Sub-syste MFS Cell Type No
Definition This flag enables / disables rerouting of DL LLC PDUs.
Mandatory rules --
Recommended --
rules
External This parameter locks only the rerouting part of the feature. It has no effect on the securisation part.
comment This parameter applies to both, intra-NSE and inter-NSE cell change.
Internal comment --
Logical EN_DL_RETRANS_BTS B11 Yes B12 Yes
name TRX nb No
HMI EN_DL_RETRANS_BTS Sub-syste MFS Cell Type No
Definition This flag enables / disables downlink retransmission in the BTS.
Mandatory rules --
Recommended --
rules
External DL retransmission in the BTS will be disabled by the MFS in the cells having an Abis or an Ater satellite link (whatever the TRE type). In a cell with terrestrial Abis and
comment Ater links, this feature is disabled for G3 TREs only.
Internal comment The feature shall be disabled by the MFS :
- on a TRX when the hardware capability is set to CS-1 up to CS-4 (I.e. a TRX mapped onto a G3 TRE in the BTS)
- in a cell when the cell round_trip_delay parameter indicates an Abis or Ater satellite link
Logical EN_EDA B11 Yes B12 Yes
name TRX nb No
HMI EN_EDA Sub-syste MFS Cell Type No
Definition Enables Extended Dynamic Allocation (EDA).
Coding rules 0: EDA not activated,
1: EDA activated
Mandatory rules EN_EDA = 0 in case of extended cell
Recommended --
rules
External When EDA is activated, its activation domain is given by the EDA_MS_ACTIVATION_LEVEL and ALLOW_DTM_EDA_COMBINATION parameters.
comment
Internal comment --
Logical EN_EXTENDED_UL_TBF B11 Yes B12 Yes
name TRX nb No
HMI EN_EXTENDED_UL_TBF Sub-syste MFS Cell Type No
Definition Flag to disable/enable the extended TBF mode feature on the uplink (without or with allowing the MS not to answer to a USF received while in Extended UL TBF mode).
Coding rules 0: Extended UL TBF mode (EUTM) is not used
1: EUTM is used
2: I-EUTM is used (improved EUTM mode)
Mandatory rules --
Recommended -It is recommended not to activate simultaneously extended UL TBF feature (EN_EXTENDED_UL_TBF) and the DL PDU rerouting feature
rules (EN_AUTONOMOUS_REROUTING)
- if EN_EXTENDED_UL_TBF is enabled and if RA capability update is supported by SGSN, then the parameter EN_RA_CAP_UPDATE must be enabled.
The Extended UL TBF mode feature is completely effective only if the parameter EN_RA_CAP_UPDATE is set to enabled.
External I-EUTM (improved EUTM) allow MS in EUTM mode to not answer to a USF.
comment In I-EUTM mode, N_POLLING_EUTM_LIMIT and IEUTM_MAX_IDLE_PERIOD parameters can be used to tune the radio link monitoring.
Internal comment --
Logical EN_FACTOR_DELAYED_DL_TBF B11 No B12 Yes
name TRX nb No
HMI EN_FACTOR_DELAYED_DL_TBF Sub-syste MFS Cell Type No
Definition This flag indicates whether or not the weight of DL TBF in delayed mode is managed differently from the weight of those in transfer mode when counting
established/active TBF in the RR allocation algorithm.
1: enabled
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the downlink TBF established after modification.
Logical EN_FAST_INITIAL_GPRS_ACCESS B11 Yes B12 Yes
name TRX nb No
HMI EN_FAST_INITIAL_GPRS_ACCESS Sub-syste MFS Cell Type No
Definition This flag indicates whether or not one Slave PDCH is available for (E)GPRS traffic in the cell (fast initial PS access feature).
In an Evolium BTS, that corresponds to a PDCH being able to support incoming (E)GPRS traffic, that PDCH being located on an established TRX (i.e. the TRX owns an
M-EGCH link or an IPGCH TCP connection is established)
1: enabled
Mandatory rules - MIN_PDCH > 0 if EN_FAST_INITIAL_GPRS_ACCESS = enabled;
- MIN_PDCH >= 0 if EN_FAST_INITIAL_GPRS_ACCESS = disabled.
- If GPRS traffic is carried between BTS and PCU through satellite links (round_trip_delay >= 500ms), and Abis_transport_mode = 1 (IP) for the corresponding BTS,
then EN_FAST_INITIAL_GPRS_ACCESS must be equal to enabled.
Recommended --
rules
External Better performances for service access time will be obtained when this parameter is set to enabled, but one PDCH will always be established in the cell. A
comment compromise has to be made by the operator between performance gain and the cost of radio and terrestrial resources. This compromise becomes of higher
importance in case of a cell connected through a satellite link due to the higher GPRS access time with satellite links, but also the higher cost of transmission links.
Internal comment - If this flag is enabled, it guarantees that the concerned cell is able to convey GPRS traffic and that an UL TBF might be established without further delay.
- In case of Abis_transport_mode(MFS) modification (see BOP), the OMC cannot check the related mandatory rule at modification time; only a non blocking warning is
raised.
Logical EN_FAST_USF_UL_EXTENDED B11 Yes B12 Yes
name TRX nb No
HMI EN_FAST_USF_UL_EXTENDED Sub-syste MFS Cell Type No
Definition Flag to disable/enable the normal fast scheduling mode for the uplink TBFs in extended mode
Mandatory rules --
Recommended --
rules
External The parameter is significant only if EN_EXTENDED_UL_TBF is enabled.
comment
Internal comment The normal fast scheduling policy is controlled by the T_EXTENDED_UL_TBF_FAST_POL parameter.
Logical EN_FULL_FAST_USF_UL_EXTENDED B11 Yes B12 Yes
name TRX nb No
HMI EN_FULL_FAST_USF_UL_EXTENDED Sub-syste MFS Cell Type No
Definition Flag to enable/disable the full fast scheduling mode for uplink TBFs in EUTM.
Mandatory rules --
Recommended --
rules
External - The full fast USF scheduling can be enabled /disabled independently on the normal fast USF scheduling (EN_FAST_USF_UL_EXTENDED parameter)
comment - The parameter is relevant only if EN_EXTENDED_UL_TBF is enabled
Internal comment The full fast USF scheduling policy is controlled by the FULL_FAST_USF_UL_EXTENDED parameter.
Logical EN_FULL_IR_DL_per_cell B11 Yes B12 Yes
name TRX nb No
HMI EN_FULL_IR_DL Sub-syste MFS Cell Type No
Definition Enables/Disables the resegmentation for the downlink TBF in the cell.
Coding rules 0: Disable the "full" IR, so : Incremental Redundancy with resegmentation allowed in DL,
1: Enable the "full" IR, so, Incremental Redundancy without resegmentation in DL
Mandatory rules --
Recommended To allow the best throughput in DL, it is strongly recommended to set this parameter to 0 i.e. to not forbid the resegmentation.
rules
External --
comment
Internal comment This parameter was previously named "EN_IR" wich lead to misunderstanding. In fact, IR is always activated (it is a mandatory feature for the MS). When this
parameter is set to 1, the RLC resegmentation is not allowed, meaning that, in case of degradation of the radio conditions, the IR would permit to continue the transfer
on a high MCS. In fact, with the IR implementation of the MS, it appeared that this hypothesis was not true and the best throughput is obtained if the resegmentation is
allowed (so, the possibility to decrease the MCS).
Logical EN_GB_FLEX B11 Yes B12 Yes
name TRX nb No
HMI EN_GB_FLEX Sub-syste MFS Cell Type No
Definition Enables/disables the support of the "Gbflex" feature (for data and signaling traffic). The GbFlex feature allows a BSS to be connected to more than one SGSN.
Mandatory rules - EN_GB_FLEX is enabled only if Gb_Transport_Mode is IP

- If Gb_Transport_Mode is FR then EN_GB_FLEX must be disabled
- EN_GB_FLEX is enabled only if SGSNR = 1
- When EN_GB_FLEX is disabled, only one SGSN can be connected to one BSS.
Recommended --
rules
External Support of Gb-Flex by the SGSN is mandatory.
comment
Parameter change: no impact on the on going telecom service. Before disabling the feature, the operator shall delete all the excessive NSEs (no more than one NSE
per PMU, ie no more than one SGSN connected to the BSS).
- up to MAX_NB_SGSN (BOP) = 16 SGSN can be connected to one BSS
Logical EN_INSTANT_MSG_SERVICE_QOS B11 Yes B12 Yes
name TRX nb No
HMI EN_INSTANT_MSG_SERVICE_QOS Sub-syste MFS Cell Type No
Definition Flag to activate/deactivate the support of the specific Instant message service QoS (also called QoS feature without PFC) in a cell.
1: enabled
Mandatory rules --
Recommended For an improved behaviour of the specific Instant Message service, Alcatel-Lucent recommends to activate along with the present feature, also the reduced PDCH
rules allocation (GPRS_MULTISLOT_CLASS_CONG_IM) and the reduced delayed DL TBF (T_NETWORK_RESPONSE_TIME_IM).
External - Function available on MFS Evolution or LRC only
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to Downlink PDU received after modification.
- it is an optional feature (TRX quantity controlled).
Logical EN_IR_UL_per_cell B11 Yes B12 Yes
name TRX nb No
HMI EN_IR_UL Sub-syste MFS Cell Type No
Definition Enables/Disables Incremental redundancy for the uplink TBF in the BSS.
Coding rules 0: Disable, 1: Enable
Mandatory rules --
Recommended Among the features Incremental Redundancy in uplink (EN_IR_UL) and RLC resegmentation in uplink (EN_RESEGMENTATION_UL_per_cell), Alcatel recommends to
rules enable first the Incremental Redundancy in Uplink. The activation of both at the same time may reduce the gain of the Incremental Redundancy
External The Incremental Redundancy for the uplink TBF feature is supported only from G4 onwards BTSs.
comment
Internal comment --
Logical EN_LCS (MFS) B11 Yes B12 Yes
name TRX nb No
HMI EN_LCS Sub-syste MFS Cell Type No
Definition Enables/Disables the Location Services (LCS) in the BSS.
Mandatory rules - Equal to EN_LCS (BSC)

- EN_LCS = disabled on BSC G2
Recommended --
rules
comment - Only the value 0 is supported on G2 BSC.
Logical EN_LONG_TBF_WEIGHT(MFS) B11 No B12 Yes
name TRX nb No
HMI EN_LONG_TBF_WEIGHT Sub-syste MFS Cell Type No
Definition This flag indicates whether, or not , the long TBFs are scheduled with a higher weight than the other TBFs, the number of allocated radio timeslot is based on packet size
threshold detection.
1: enabled
Mandatory rules --
Recommended --
rules
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the TBF established after modification.
- EN_LONG_TBF_WEIGHT(MFS) control depending on EN_PFC_FEATURE,
- EN_LONG_TBF_WEIGHT(OMC), EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) combination:
with:
EN_RTS_ALLOC_ON_PACKET_SIZE(OMC)= [1] EN_LONG_TBF_WEIGHT(OMC)=[2];
EN_PFC_FEATURE= [3];
EN_LONG_TBF_WEIGHT(MFS)= [4]
we have:
[1] [2] [3] [4] :
0 0 0 0
1 0 0 forbidden
0 1 0 forbidden
1 1 0 1
0 0 1 0
1 0 1 1
0 1 1 forbidden
1 1 1 forbidden
Logical EN_MCS_ADAPTATION_CONFIGURATION B11 No B12 Yes
name TRX nb No
HMI EN_MCS_ADAPTATION_CONFIGURATION Sub-syste MFS Cell Type No
Definition This flag enables / disables configuring link adaptation tables for EGPRS in RLC acknowledged mode.
1: enabled
Mandatory rules --
Recommended --
rules
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the TBF established.
Logical EN_MCS1_in_CRP B11 Yes B12 Yes
name TRX nb No
HMI EN_MCS1_in_CRP Sub-syste MFS Cell Type No
Definition Enables the forced usage of MCS-1 for uplink EGPRS TBF in contention resolution phase at one-phase access to make this phase more robust.
Coding rules 0: the BSS does not force uplink EGPRS TBF to use MCS-1 during the contention resolution phase at one-phase access.
1: the BSS forces uplink EGPRS TBF to use MCS-1 during the contention resolution phase at one-phase access.
Mandatory rules --
Recommended --
rules
External The forced usage of MCS-1 for uplink EGPRS TBF in contention resolution phase at one-phase access corresponds to the behaviour in B9.
comment
Internal comment --
Logical EN_MS_ASSISTED_AGPS B11 Yes B12 Yes
name TRX nb No
HMI EN_MS_ASSISTED_AGPS Sub-syste MFS Cell Type No
Definition Flag to enable or disable the positioning method MS Assisted A-GPS.
Mandatory rules - EN_MS_ASSISTED_AGPS = 0.
Recommended --
rules
comment - Only the value 0 is supported.
Internal comment --
Logical EN_MS_BASED_AGPS B11 Yes B12 Yes
name TRX nb No
HMI EN_MS_BASED_AGPS Sub-syste MFS Cell Type No
Definition Flag to enable or disable the positioning method MS Based A-GPS.
Mandatory rules - EN_MS_BASED_AGPS = 0
Recommended --
rules
comment - Only the value 0 is supported
Internal comment --
Logical EN_MULTISLOT_CLASS_30_33 B11 Yes B12 Yes
name TRX nb No
HMI EN_MULTISLOT_CLASS_30_33 Sub-syste MFS Cell Type No
Definition Enables the support of (E)GPRS multislot class 30-33.
Mandatory rules --
Recommended --
rules
External Support of DTM (E)GPRS multislot classes 31 to 33 is possible only if EN_DTM = 1 and EN_MULTISLOT_CLASS_30_33 = 1. Support of configurations requiring EDA is
comment possible only if EN_EDA = 1 (and ALLOW_DTM_EDA_COMBINATION = 1 in case of DTM).
Logical EN_NACC B11 Yes B12 Yes
name TRX nb No
HMI EN_NACC Sub-syste MFS Cell Type No
Definition Enables the Network Assisted Cell Change feature.
Coding rules 0: disabled; 1:enabled
Mandatory rules Can be enabled only if round_trip_delay < 500 msec

When cell_type = extended inner or extended outer, then EN_NACC = 0
Recommended --
rules
External --
comment
Internal comment --
Logical EN_OUTGOING_GPRS_REDIR B11 Yes B12 Yes
name TRX nb No
HMI EN_OUTGOING_GPRS_REDIR Sub-syste MFS Cell Type No
Definition Indicates whether or not outgoing GPRS redirections are systematically triggered from the serving cell.
Coding rules 0: Outgoing GPRS redirections are not triggered
1: Outgoing GPRS redirections are systematically triggered
Mandatory rules --
Recommended In cells where outgoing GPRS redirections are systematically triggered (i.e. EN_OUTGOING_GPRS_REDIR = Enable), it is up to the operator to ensure that at least one
rules NC cell reselection cause is always triggered upon receipt of the first Packet Measurement Report message. For instance, NC cell reselection Cause PT1 can be
always activated by setting NC_DL_RXLEV_THR to -47 dBm (Always).
External An outgoing GPRS redirection is a NC cell reselection which is triggered when the MS enters the packet transfer mode in the serving cell even if the radio link is good.
comment The intention of GPRS redirections is to redirect the MS towards a target cell more appropriate to carry PS traffic (for instance a macro cell).
Internal comment This parameter shall also be valid for external cells.
Logical EN_OUTGOING_GPRS_REDIR(n) B11 Yes B12 Yes
name TRX nb No
HMI EN_OUTGOING_GPRS_REDIR(n) Sub-syste MFS Cell Type No
Definition Indicates whether or not outgoing GPRS redirections are systematically triggered from the serving cell.
Coding rules 0: Disable Outgoing GPRS redirections are not triggered
1: Enable Outgoing GPRS redirections are systematically triggered
Mandatory rules --
Recommended In cells where outgoing GPRS redirections are systematically triggered (i.e. EN_OUTGOING_GPRS_REDIR = Enable), it is up to the operator to ensure that at least one
rules NC cell reselection cause is always triggered upon receipt of the first Packet Measurement Report message. For instance, NC cell reselection Cause PT1 can be
always activated by setting NC_DL_RXLEV_THR to -47 dBm (Always).
External An outgoing GPRS redirection is a NC cell reselection which is triggered when the MS enters the packet transfer mode in the serving cell even if the radio link is good.
comment The intention of GPRS redirections is to redirect the MS towards a target cell more appropriate to carry PS traffic (for instance a macro cell).
Logical EN_PFC_FEATURE B11 Yes B12 Yes
name TRX nb No
HMI EN_PFC_FEATURE Sub-syste MFS Cell Type No
Definition Enables/disables the support of the PFC negotiation feature.
Coding rules 1 => PFC feature is supported,
0 => PFC feature is not supported
Mandatory rules - EN_PFC_FEATURE and EN_LONG_TBF_WEIGHT are exclusive: they shall not be both enabled at the same time in any cell of the BSS.
- EN_LONG_TBF_WEIGHT(OMC) cannot be enabled if EN_PFC_FEATURE=enabled,
- When EN_PFC_FEATURE = disabled, EN_LONG_TBF_WEIGHT(OMC) and EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) must have the same value.
Recommended --
rules
External Parametre change: Any modification of the parameter leads to reset autonomously all the PMUs connected to this BSS.
comment
Internal comment --
Logical EN_PSI_STATUS B11 Yes B12 Yes
name TRX nb No
HMI EN_PSI_STATUS Sub-syste MFS Cell Type No
Definition Enables the Packet SI Status feature in cells w/o PBCCH or the Packet PSI Status feature in cells with a PBCCH.
Coding rules 0: disabled; 1:enabled
Mandatory rules Can be enabled only if round_trip_delay < 500 msec

When cell_type = extended inner or extended outer, then EN_PSI_STATUS = 0
Recommended --
rules
External --
comment
Internal comment --
Logical EN_PSI3_Coding2 B11 Yes B12 Yes
name TRX nb No
HMI EN_PSI3_Coding2 Sub-syste MFS Cell Type No
Definition This flag enables the use of the optional neighbour cell parameters 2 structure in the coding of PSI3bis messages
Mandatory rules --
Recommended --
rules
External --
comment
The neighbour cell parameters 2 provides a shorter coding of neighbour cells parameters which improves the cell reselection duration.
Logical EN_RA_CAP_UPDATE B11 Yes B12 Yes
name TRX nb No
HMI EN_RA_CAP_UPDATE Sub-syste MFS Cell Type No
Definition Flag to enable/disable the Radio Acces Capability update on Gb
Mandatory rules --
Recommended This parameter must be enabled if RA capability update is supported by SGSN and if it exists, at least, one cell where EN_EXTENDED_UL_TBF is enabled.
rules The Extended UL TBF mode feature is completely effective only if the parameter EN_RA_CAP_UPDATE is set to enabled.
If EN_STREAMING is set to 1 then EN_RA_CAP_UPDATE must also be set to 1 (enabled). Otherwise the BSS will not be able to handle streaming flow. If this rule is not
respected then all PFC creation requests related to a streaming flow will be downgraded to the default best effort flow by the BSS.
External --
comment
Internal comment --
Logical EN_RED_PDDCB B11 No B12 Yes
name TRX nb No
HMI EN_RED_PDDCB Sub-syste MFS Cell Type No
Definition Flag to activate/deactivate the reduction of unnecessary PDDCB (Packet DL Dummy Control Block) in a cell
1: enabled
Mandatory rules - EN_RED_PDDCB can be enabled only if PC_MEAS_CHAN = 0 (downlink measurements for power control shall be made on BCCH)
Recommended --
rules
External - Function available on MFS Evolution and supported on the G4 onwards TREs of the cell.
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to any ongoing Downlink TBFs
- the feature is not supported by G3 TRE.
Logical EN_RESEGMENTATION_UL_per_cell B11 Yes B12 Yes
name TRX nb No
HMI EN_RESEGMENTATION_UL Sub-syste MFS Cell Type No
Definition Enables/Disables the resegmentation for the uplink TBF in the cell, in case of RLC in acknowledged mode.
Coding rules 0: Disabled, 1: Enabled
Mandatory rules --
Recommended Among the features Incremental Redundancy in uplink (EN_IR_UL) and RLC resegmentation in uplink (EN_RESEGMENTATION_UL), Alcatel recommends to enable first
rules the Incremental Redundancy in Uplink. The activation of both at the same time may reduce the gain of the Incremental Redundancy
External --
comment
Internal comment --
Logical EN_RIM_NACC B11 Yes B12 Yes
name TRX nb No
HMI EN_RIM_NACC Sub-syste MFS Cell Type No
Definition Flag to disable/enable the Inter-BSS and Inter-RAT NACC features (inter-RAT = inter-3G or inter-LTE).
It covers both controlling and serving aspects : for controlling part, this is the ability to request and receive System Information messages from the Gb interface and to
broadcast them to MS through the PACCH.
For serving part, this is the ability to provide System Information messages when requested by another BSS/RNC.
Coding rules 0: Inter-BSS and Inter-RAT NACC are disabled
1: Inter-BSS NACC only is enabled
2 Inter-3G NACC only is enabled
3 Inter-BSS and Inter-3G NACC are enabled
4 Inter-LTE NACC only is enabled
5 Inter-BSS and Inter-LTE NACC are enabled
6 Inter-3G and Inter-LTE NACC are enabled
7 Inter-BSS and Inter-RAT NACC are enabled
Mandatory rules --
Recommended --
rules
External - For a BSS working as a controlling BSS, the Inter-BSS NACC feature can be effective for a serving cell, if EN_NACC feature is enabled in that cell. For a BSS
comment working as a serving BSS, there is no interaction with the EN_NACC feature.
- Parameter change:
When enabling (setting from 0 to <>0), a reset of all the BVC SIG is automatically performed (leading to stop and restart PS traffic in the BSS).
In case of disabling (setting from <>0 to 0), the reset is automatically done only on the NSEs of the BSS, connected to a SGSN supporting the RIM feature (leading to
stop and restart PS traffic on these SGSN(s)).
In any other case of modification, there is no impact on the PS traffic; on going TBFs are not disrupted.
Internal comment Both features are managed as a single optional feature
At controlling BSS side, 0=2=4=6 and 1=3=5=7, since inter-RAT NACC is only managed by a serving BSS.
Logical EN_SAGI B11 Yes B12 Yes
name TRX nb No
HMI EN_SAGI Sub-syste MFS Cell Type No
Definition Flag indicating whether SAGI (interface with the A-GPS server) is configured or not for this BSS.
Mandatory rules - EN_SAGI = 0
Recommended --
rules
External - Only the value 0 is supported.
comment
Internal comment --
Logical EN_SOLSA B11 Yes B12 Yes
name TRX nb No
HMI EN_SOLSA Sub-syste MFS Cell Type No
Definition This flag enables / disables SoLSA feature.
Mandatory rules May be set to Enabled only if BCCH_EXT=TRUE.
Recommended --
rules
External --
comment
Internal comment Used to determine O&M parameter SOLSA_FUNCT_LEVEL.
Logical EN_SOLSA(n) B11 Yes B12 Yes
name TRX nb No
HMI EN_SOLSA Sub-syste MFS Cell Type No
Definition This flag enables / disables SoLSA feature.
Mandatory rules --
Recommended --
rules
External This parameter is for every cell. The operator needs only to configure the value of that parameter for OMC external cells ; the parameter is autonomously filled by the
comment OMC in case the adjacent cell is an OMC internal cell.
Internal comment --
Logical EN_STREAMING B11 Yes B12 Yes
name TRX nb No
HMI EN_STREAMING Sub-syste MFS Cell Type No
Definition Enables/disables the support of the STREAMING flows.
Coding rules 1 => the cell supports the streaming flows in addition to the non real time flows (best effort, interactive, background) if EN_PFC_FEATURE = 1 and if the PFC feature
negotiation with the SGSN is successful
0 => the cell supports the non real time flows (best effort, interactive, background) if EN_PFC_FEATURE = 1 and if the PFC feature negotiation with the SGSN is
successful
Mandatory rules - If EN_STREAMING = 1 then MAX_PDCH_HIGH_LOAD > 0
- When cell_type = extended inner or extended outer, then EN_STREAMING = 0
Recommended 1) If this parameter is set to 1 then the parameter EN_RA_CAP_UPDATE must also be set to 1 (enabled). Otherwise the BSS will not be able to handle streaming flow.
rules If this rule is not respected then all PFC creation requests related to a streaming flow will be downgraded to the default best effort flow by the BSS.
2) the parameter EN_CS_ADAPTATION_ACK must also set to TRUE in order to activate the link adaptation mechanism so that the (M)CS can reach a suitable level
regarding the level of the configured Rmin_(E)GPRS. Otherwise, the streaming PFCs can be downgraded to the Default Best Effort ABQP because the negotiated GBR
cannot be reached on the radio interface.
External --
comment
Internal comment --
Logical EN_UL_CONGESTION B11 Yes B12 Yes
name TRX nb No
HMI EN_UL_CONGESTION Sub-syste MFS Cell Type No
Definition Flag to enable or disable the UL congestion process in case of UL NS congestion.
Coding rules 0: disabled; 1:enable
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Estimated_Speed_CS_FAMILY_0 B11 Yes B12 Yes
name TRX nb No
HMI Estimated_Speed_CS_FAMILY_0 Sub-syste MFS Cell Type No
Definition Factor used for coding (resp. decoding) of the RLC buffer size on IPGCH interface, according to the estimated speed indication.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit kbit/s
Mandatory rules --
Recommended --
rules
External Values of Estimated_Speed_CS_FAMILY_i parameters have been determined to keep a trend as close as possible as the one of (M)CS raw bitrates.
comment The default value corresponds to the factor used for CS1, CS2, MCS1 and MCS2 bitrates.
Internal comment - An indication of ESS = 0 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_0.
name TRX nb No
Mandatory rules --
Recommended --
rules
comment The default value corresponds to the factor used for CS3 and MCS3 bitrates.
name TRX nb No
Mandatory rules --
Recommended --
rules
comment The default value corresponds to the factor used for CS4 and MCS4 bitrates.
name TRX nb No
Mandatory rules --
Recommended --
rules
comment The default value corresponds to the factor used for MCS5 bitrate.
name TRX nb No
Mandatory rules --
Recommended --
rules
name TRX nb No
Mandatory rules --
Recommended --
rules
name TRX nb No
Mandatory rules --
Recommended --
rules
name TRX nb No
Mandatory rules --
Recommended --
rules
Logical FACTOR_DELAYED_DL_TBF B11 No B12 Yes
name TRX nb No
HMI FACTOR_DELAYED_DL_TBF Sub-syste MFS Cell Type No
Definition Percentage of radio bandwidth consumed by a DL TBF in delayed mode, compared with a TBF in active state. The lower the value of FACTOR_DELAYED_DL_TBF, the
higher the number of DL TBFs multiplexed per PDCH.
When set to 100% both TBFs, currently established in delayed and in active mode, have the same weight in the bandwidth evaluation of the DL TBF radio allocation
algorithm.
When set to 0%, the DL TBFs in delayed mode are totally ignored.
Mandatory rules --
Recommended --
rules
comment - Significant if EN_ FACTOR_DELAYED_DL_TBF is enabled.
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the downlink TBF established after modification.
Logical FDD_GPRS_Qoffset B11 Yes B12 Yes
name TRX nb No
HMI FDD_GPRS_Qoffset Sub-syste MFS Cell Type No
Definition Offset added to the received level average of the serving cell and of the neighbour GSM cells
for UTRAN FDD cell re-selection in GPRS
Rec ref. GSM TS 05.08 Domai 2G-3G Min value -32 Coded Min 0
Spec ref. Packet system information management Coded Max 15
1: -28: -28 dB
2: -24: -24 dB
3: -20: -20 dB
4: -16: -16 dB
5: -12: -12 dB
6: -8: -8 dB
7: -4: -4 dB
8: 0: 0 dB
9: 4: 4 dB
10: 8: 8 dB
11: 12: 12 dB
12: 16: 16 dB
13: 20: 20 dB
14: 24: 24 dB
15: 28: 28 dB
Mandatory rules --
Recommended --
rules
External This parameter is broadcast on PBCCH if there is a PBCCH allocated in the serving cell.
comment
Logical FLOW_DIM_Safety_BVC B11 Yes B12 Yes
name TRX nb No
HMI FLOW_DIM_Safety_BVC Sub-syste MFS Cell Type No
Definition Safety factor to size BVC_Bucket_Size parameter, for downlink flow control, on Gb interface.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical FLOW_DIM_Safety_MS B11 Yes B12 Yes
name TRX nb No
HMI FLOW_DIM_Safety_MS Sub-syste MFS Cell Type No
Definition Safety factor to size default MS_Bucket_Size parameter, for downlink flow control, on Gb interface.
Mandatory rules --
Recommended FLOW_DIM_Safety_MS should be set to a value corresponding to the maximum multi-slot class of the MS present on the network
rules
External --
comment
Internal comment --
Logical FR_INFO_SIZE B11 Yes B12 Yes
name TRX nb No
HMI Info Frame size Sub-syste MFS Cell Type No
Definition Maximum frame relay information frame size.
Category System (CST) OMC-R access None (DLS) Type Number Unit byte
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical FREQUENCY_RANGE(n) (MFS) B11 Yes B12 Yes
name TRX nb No
HMI FREQUENCY_RANGE Sub-syste MFS Cell Type No
Definition This parameter indicates the frequency range of the adjacent cell (GAN cell excluded).
Coding rules 0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850, 7..255: for future use. The parameter shall be coded
over 8 bits as a provision for future frequency bands support.
Mandatory rules - If FREQUENCY_RANGE(n) = "GSM-DCS" then CELL_PARTITION_TYPE(n) must be equal to "Concentric".
- The micro concentric, mini concentric and indoor concentric cells must be multiband (the allowed FREQUENCY_RANGE(n) is PGSM-DCS1800 or
Recommended --
rules
External Within the same PLMN, the FREQUENCY_RANGE parameter of a given cell shall be selected among one of the following values:
comment - PGSM (GSM900) or EGSM (GSM900) or DCS1800 or PGSM-DCS1800 or EGSM-DCS1800 if the PLMN_FREQUENCY_BANDS is set to "GSM900 and DCS1800
bands",
- GSM850 or DCS1800 if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1800 bands",

- GSM850 or DCS1900 if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1900 bands.
Internal comment Values 4 and "5" are for Multiband cells.
Logical FULL_FAST_USF_UL_EXTENDED B11 Yes B12 Yes
name TRX nb No
HMI FULL_FAST_USF_UL_EXTENDED Sub-syste MFS Cell Type No
Definition Duration of the full fast USF scheduling phase for an UL TBF in EUTM, during which the UL TBF in EUTM may be scheduled on all its PDCHs (instead of on only one).
It is expressed in number of successive block periods (20 ms).
Category System (CST) OMC-R access None (DLS) Type Number Unit block period
Coding rules --
Mandatory rules --
Recommended --
rules
External The parameter is relevant only if EN_FULL_FAST_USF_UL_EXTENDED is enabled.
comment
Internal comment Trade-off MS battery lifetime / MS reaction time +Round trip delay.
Simultaneously activating full fast USF scheduling and increasing T_EXTENDED_UL_FAST_POL may allow in some cases saving resources during the EUTM phases
without strong performance degradations
Logical GAMMA_TNx B11 Yes B12 Yes
name TRX nb No
HMI GAMMA_TNx Sub-syste MFS Cell Type No
Definition Binary representation of the gamma ch for MS output power control.
Coding rules Coded on 5 bits, step size=2dB, with 00000 == 0 dB, 00001 == 2 dB, ... 11111 == 62 dB.
Mandatory rules --
Recommended --
rules
External - In the context of a concentric cell, the parameter applies to the outer zone.
comment - Default value depends on configuration. The value indicated here is for implementation purposes.
Internal comment --
Logical Gb_Configuration_Type B11 Yes B12 Yes
name TRX nb No
HMI Gb_Configuration_Type Sub-syste MFS Cell Type No
Definition Configuration type used with Gb over IP.
In case of static configuration, the SGSN IP endpoint(s) are given by O&M.
In case of dynamic configuration, the SGSN IP endpoint(s) are sent dynamically by the SGSN. For that exchange, at least one pre-configured SGSN IP endpoint is
previously given by O&M.
Spec ref. GPRS Gb interface - Network service control sub-layer Coded Max 1
Coding rules 0 : Static configuration
1: Dynamic configuration
Mandatory rules In a BSS in multi-GP/GPUs configuration where Gb_Transport_Mode is IP, all the NSEs connected to the same SGSN, having children SGSN IP endpoint(s), must have
the same Gb_Configuration_Type.
Recommended --
rules
External Gb_Configuration type is significant only when Gb_Transport mode is IP.
comment Parameter change: before any parameter modification, the operator has to delete the children SGSN IP endpoint(s).
Internal comment The configuration type is checked per BSS, in order to let the ability for a SGSN to use different configuration type per connected BSS.
Logical Gb_Data_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI Gb_Data_PRIORITY Sub-syste MFS Cell Type No
Definition BSS internal priority used by the PCU for the Gb over IP data flow
Coding rules step size = 1, O: highest priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Gb_Signalling_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI Gb_Signalling_PRIORITY Sub-syste MFS Cell Type No
Definition BSS internal priority used by the PCU for the Gb over IP signalling flow
Coding rules Step size = 1. 0: highest priority
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Gb_Transport_Mode B11 Yes B12 Yes
name TRX nb No
HMI Gb_Transport_Mode Sub-syste MFS Cell Type No
Definition Mode of the transport for Gb interface: FR or IP.
Coding rules 0: FR mode
1: IP mode
Mandatory rules - EN_GB_FLEX is enabled only if Gb_Transport_Mode is IP.
- If Gb_Transport_Mode is FR then EN_GB_FLEX must be disabled.
Recommended --
rules
External - When the NSE is not associated to a BSS, the Gb_Transport_Mode_perNSE defines the transport mode of the NSE.
comment When the NSE is associated to a BSS, the transport mode of the BSS defines the transport mode of all NSEs of the BSS (the Gb_Transport_Mode - of the BSS -
overrides the transport mode defined in the NSE instance).
- Parameter change: before to set to transport mode to FR, the operator has to delete all the excessive NSEs (no more than one NSE per GPU, ie no more than one
SGSN connected to the BSS). Any modification of the parameter leads the MFS to reset autonomously all the GP/GPUs connected to this BSS.
Internal comment Gb over IP is an optional feature.
Logical Gb_Transport_Mode_per_NSE B11 Yes B12 Yes
name TRX nb No
HMI Gb_Transport_Mode_per_NSE Sub-syste MFS Cell Type No
Definition Mode of the transport for Gb interface (per NSE): FR or IP.
Coding rules 0: FR mode
1: IP mode
Mandatory rules --
Recommended --
rules
External - When the NSE is not associated to a BSS, the Gb_Transport_Mode_perNSE defines the transport mode of the NSE.
comment When the NSE is associated to a BSS, the transport mode of the BSS defines the transport mode of all NSEs of the BSS (the Gb_Transport_Mode - of the BSS -
overrides the transport mode defined in the NSE instance).
- Parameter change: Any modification of the parameter leads the MFS to reset autonomously the associated GP/GPU.
Internal comment Gb over IP is an optional feature
Logical GCH_RED_FACTOR_High_Ater_Usage B11 Yes B12 Yes
name TRX nb No
HMI GCH_RED_FACTOR_HiAter Sub-syste MFS Cell Type No
Definition Reduction factor of the number of GCHs targeted per PDCH, when the Ater usage is high.
Mandatory rules --
Recommended A low value of GCH_RED_Factor_High_Ater_Usage can be coherent with a high value of Ater_Usage_Threshold (it will avoid reaching the saturation point of 100%
rules of the Ater resources used at the same moment in the GPU).
Reciprocally, a high value of GCH_RED_Factor_High_Ater_Usage can be coherent with a low value of Ater_Usage_Threshold (it will limit the risks of wasting, i.e. of
not using, Ater resources in the GPU).
comment - The GCH reduction factor applies to the new PDCHs which are used when the Ater usage is high (see the Ater_Usage_Threshold parameter). This parameter can
be reduced in order to avoid Ater shortage situations.
Internal comment --
Logical GEOGRAPHICAL_COORDINATES_FLAG B11 Yes B12 Yes
name TRX nb No
HMI Geographical Coordinates Sub-syste MFS Cell Type No
Definition Indicates whether latitude and longitude are significant or not.
Coding rules 0: not significant, 1: significant
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter allows the SMLC to know whether the geographical coordinates sent by the OMC-R are significant or not.
Logical GPRS_CELL_RESELECT_HYSTERESIS B11 Yes B12 Yes
name TRX nb No
HMI GPRS_CELL_RESELECT_HYSTERESIS Sub-syste MFS Cell Type No
Definition Additional hysteresis which applies in Ready state for cells in same RA.
Coding rules step size = 2dB; coded on 3 bits. 000=0 dB, 001= 2 dB, 111=14 dB
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_DL_Ack_period B11 Yes B12 Yes
name TRX nb No
HMI GPRS_DL_Ack_period Sub-syste MFS Cell Type No
Definition If the GPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the number of transmitted radio blocks necessary to request a
Packet Downlink Ack/Nack in acknowledged mode.
Mandatory rules --
Recommended --
rules
External The value of this parameter is linked with N3105_Limit.
comment
Internal comment It is recommended to set GPRS_DL_Ack_period = 12 if the MSs used in the network are able to manage two polling requests at a given instant. Otherwise, it is
recommended to set GPRS_DL_Ack_period = 16.
The value of GPRS_DL_Ack_period = 12 allows not blocking the RLC transmission window in case of Packet DL Ack/Nack message is lost on the radio interface or is
replaced by a Packet Measurement Report message (if NC2 is activated).
The value of GPRS_DL_Ack_period = 16 ensures that in most of the cases the MSs only manage one polling request at a given instant.
Logical GPRS_DL_Ack_period_Satellite B11 Yes B12 Yes
name TRX nb No
HMI GPRS_DL_Ack_period_Satellite Sub-syste MFS Cell Type No
Definition If the GPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the number of transmitted radio blocks necessary to request a Packet
Downlink Ack/Nack in acknowledged mode.
Mandatory rules --
Recommended --
rules
External The value of this parameter is linked with N3105_Limit_Satellite.
comment
It is recommended to set GPRS_DL_Ack_period_Satellite = 12 if the MSs used in the network are able to manage two polling requests at a given instant. Otherwise, it
is recommended to set GPRS_DL_Ack_period_Satellite = 16.
The value of GPRS_DL_Ack_period_Satellite = 12 allows not blocking the RLC transmission window in case of Packet DL Ack/Nack message is lost on the radio
interface or is replaced by a Packet Measurement Report message (if NC2 is activated).
The value of GPRS_DL_Ack_period_Satellite = 16 ensures that in most of the cases the MSs only manage one polling request at a given instant.
Logical GPRS_HCS_THR B11 Yes B12 Yes
name TRX nb No
HMI HCS_THR Sub-syste MFS Cell Type No
Definition HCS signal strength.
Rec ref. GSM TS 05.08 Domai GPRS Min value -110 Coded Min 0
Coding rules Coded on 5 bits. 00000=-110 dBm, 00001=-108 dBm, 11111=-48 dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_HCS_THR(n) B11 Yes B12 Yes
name TRX nb No
HMI HCS_THR Sub-syste MFS Cell Type No
Definition HCS signal strength.
Coding rules Coded on 5 bits. 00000=-110 dBm, 00001=-108 dBm, 11111=-48 dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_LLC_THROUGHPUT_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI GPRS_LLC_THROUGHPUT_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the 1st class, lower limit of the 2nd class for GPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th class for GPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd class, lower limit of the 3rd class for GPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd class, lower limit of the 4th class for GPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th class, lower limit of the 5th class for GPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Lower limit of the 9th class for GPRS LLC THROUGHTPUT distribution
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical GPRS_MS_TXPWR_MAX_CCH B11 Yes B12 Yes
name TRX nb No
HMI GPRS_MS_TXPWR_MAX_CCH Sub-syste MFS Cell Type No
Definition Maximum TX power level an MS may use when accessing the system.
Coding rules Coded on 5 bits from 0 to 31
The coding depends on the BCCH frequency band:
P-GSM/G1 coding: step size = 2 dBm; 0: 43 dBm, ..., 19: 5 dBm.
Mandatory rules --
Recommended --
rules
Internal comment 1) This parameter is needed when a PBCCH is established in the serving cell.
2) The default value depends on the BCCH frequency band, but the same default coded value is always used, i.e. default coded value = 0.
By convention, the minimum, maximum, and default values in the main window of the parameter are given for the P-GSM/G1 frequency band.
Logical GPRS_MS_TXPWR_MAX_CCH(n) B11 Yes B12 Yes
name TRX nb No
HMI GPRS_MS_TXPWR_MAX_CCH Sub-syste MFS Cell Type No
Definition Maximum TX power level an MS may use when accessing the system.
Coding rules Coded on 5 bits from 0 to 31
The coding depends on the BCCH frequency band:
P-GSM/G1 coding: step size = 2 dBm; 0: 43 dBm, ..., 19: 5 dBm.
GSM 850 coding: step size = 2 dBm; 0: 39 dBm, 1: 39 dBm, 2: 39 dBm, 3: 37 dBm, 4: 35 dBm, 19: 5 dBm.
Mandatory rules --
Recommended --
rules
Internal comment 1)This parameter is needed when a PBCCH is established in the serving cell.
Logical GPRS_MULTISLOT_CLASS_CONG_IM B11 Yes B12 Yes
name TRX nb No
HMI GPRS_MULTISLOT_CLASS_CONG_IM Sub-syste MFS Cell Type No
Definition Maximum (E)GPRS multislot class used to establish a DL specific Instant Message TBF, when the cell is PS radio congested. If the multislot class, received on Gb
interface, is greater than this parameter, then this parameter value is used by the best candidate TBF allocation computation, in order to reduce the DL PDCH allocation.
Coding rules 0: the reduced PDCH allocation in DL for specific Instant Message is disabled
1: GPRS multislot class 1 (1+1 MS);
2: GPRS multislot class 2 (2+1 MS)
Mandatory rules - GPRS_MULTISLOT_CLASS_CONG_IM <= GPRS_MULTISLOT_CLASS_DEF_VALUE
Recommended --
rules
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the downlink TBF established after modification.
Internal comment - the transfer is to be downlink biased by PCC (e.g. case of one phase access UL TBF establishment, the most access used in CMCC network)
- Feature specific for CMCC
Logical GPRS_MULTISLOT_CLASS_DEF_VALUE B11 Yes B12 Yes
name TRX nb No
HMI GPRS_MULTISLOT_CLASS_DEF_VALUE Sub-syste MFS Cell Type No
Definition Default value of the (E)GPRS multislot class assumed at TBF establishment when the actual MS (E)GPRS multislot class is unknown.
The default MS class is used as an input of the best candidate TBF allocation computation process when the MS class is not known on UL TBF establishment.
Coding rules Only the following GPRS multislot class defined in 3GPP TS 05.02 annex B are allowed:
30: GPRS multislot class 30 (5+1 MS).
Mandatory rules - The max GPRS_MULTISLOT_CLASS_CONG_IM of all the cells of the BSS <= GPRS_MULTISLOT_CLASS_DEF_VALUE
Recommended The recommendations to set this parameter are the following:

rules 1) In case the PS traffic is mainly signalling (e.g. there is a great proportion of RA Updates among the UL TBF establishment requests),
GPRS_MULTISLOT_CLASS_DEF_VALUE shall be set to 1 (optimization of the number of T2 TBF reallocations and of CPU).
2) In case the PS traffic is mainly data (high proportion of UL TBF establishment requests for data traffic), GPRS_MULTISLOT_CLASS_DEF_VALUE should be set to
the most common multislot class which can be found among the mobile stations within the BSS (in order to limit the number of T2 TBF reallocations and of CPU,
triggered with the establishment of the concurrent DL TBF). In case of multislot class 30, this additionally requires that the multislot class 30-33 feature is widely
activated in the BSS.
External The entered value is assumed by default at uplink TBF establishment when the actual MS multislot class is unknown (e.g. RACH one phase access on CCCH) .
comment Otherwise, the multislot class received in the request for uplink TBF establishment is taken into account.
Internal comment --
Logical GPRS_PENALTY_TIME(n) B11 Yes B12 Yes
name TRX nb No
HMI GPRS_PENALTY_TIME Sub-syste MFS Cell Type No
Definition Time during which GPRS_TEMPORARY_OFFSET is active in neighbour cells.
Coding rules step size = 10 sec, coded on 5 bits (00000 = 10 sec, 11111 = 320 sec)
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_PRIORITY_CLASS B11 Yes B12 Yes
name TRX nb No
HMI PRIORITY_CLASS Sub-syste MFS Cell Type No
Definition HCS priority of the cell, used in NC0.
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_PRIORITY_CLASS(n) B11 Yes B12 Yes
name TRX nb No
HMI PRIORITY_CLASS Sub-syste MFS Cell Type No
Definition HCS priority of the adjacent cell, used in NC0.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_RESELECTION_OFFSET(n) B11 Yes B12 Yes
name TRX nb No
HMI GPRS_RESELECTION_OFFSET Sub-syste MFS Cell Type No
Definition Permanent offset for GPRS cell reselection in neighbour cells.
Coding rules coded on 5 bits (00000 = -52 dB, 11111 = 48 dB)
00000= -52; 00001= -48; 00010= -44; 00011= -40; 00100= -36; 00101= -32; 00110= -28; 00111= -24; 01000= -20; 01001= -16; 01010= -12; 01011= -10; 01100= -
8; 01101= - 6; 01110= - 4; 01111= - 2; 10000= 0; 10001= 2; 10010= 4; 10011= 6; 10100= 8; 10101=10; 10110= 12; 10111= 16; 11000= 20; 11001= 24; 11010=
28; 11011= 32; 11100= 36; 11101= 40; 11110= 44; 11111= 48
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_RXLEV_ACCESS_MIN B11 Yes B12 Yes
name TRX nb No
HMI GPRS_RXLEV_ACCESS_MIN Sub-syste MFS Cell Type No
Definition Minimum received level at the MS required for access to the system.
Coding rules step size = 1 dBm, coded on 6 bits (000000 = -110 dBm, 111111 = -47 dBm)
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_RXLEV_ACCESS_MIN(n) B11 Yes B12 Yes
name TRX nb No
HMI GPRS_RXLEV_ACCESS_MIN Sub-syste MFS Cell Type No
Definition Minimum received level at the MS required for access to the system in neighbour cells.
Coding rules coded on 6 bits, 0=-110 dBm, 63=-47 dBm, step size=1dBm
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_TEMPORARY_OFFSET(n) B11 Yes B12 Yes
name TRX nb No
HMI GPRS_TEMPORARY_OFFSET Sub-syste MFS Cell Type No
Definition Negative offset used for MS cell reselection process in neighbour cells.
Coding rules Possible values : 0, 10, 20, 30, 40, 50, 60, infinity respectively binary coded as 000, 001, , 111
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPRS_UL_Ack_period B11 Yes B12 Yes
name TRX nb No
HMI GPRS_UL_Ack_period Sub-syste MFS Cell Type No
Definition If the GPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the number of received radio blocks necessary to send a Packet
Uplink Ack/Nack in acknowledged mode.
Coding rules step size =1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical GPRS_UL_Ack_period_Satellite B11 Yes B12 Yes
name TRX nb No
HMI GPRS_UL_Ack_period_Satellite Sub-syste MFS Cell Type No
Definition If the GPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the number of received radio blocks necessary to send a Packet Uplink
Ack/Nack in acknowledged mode.
Mandatory rules --
Recommended --
rules
External --
comment
Logical GPU_BUFFER_CONGESTION_THR_1_XOFF B11 Yes B12 Yes
name TRX nb No
HMI PMU_BUFFER_CONGESTION_THR_1_XOFF Sub-syste MFS Cell Type No
Definition Threshold to enter the first level of buffer congestion in a given PMU (buffers used for LLC PDU storage and the BSCGP signalling message storage).
Coding rules --
Mandatory rules GPU_BUFFER_CONGESTION_THR_2 > GPU_BUFFER_CONGESTION_THR_1_XOFF > GPU_BUFFER_CONGESTION_THR_1_XON
Recommended --
rules
External --
comment
Internal comment Used by RRM (for Gb interface protection)
Logical GPU_BUFFER_CONGESTION_THR_1_XON B11 Yes B12 Yes
name TRX nb No
HMI PMU_BUFFER_CONGESTION_THR_1_XON Sub-syste MFS Cell Type No
Definition Threshold to exit the first level of buffer congestion in a given PMU (buffers used for LLC PDU storage and the BSCGP signalling message storage).
Coding rules --
Recommended --
rules
External --
comment
Internal comment Used by RRM (for Gb interface protection)
Logical GPU_BUFFER_CONGESTION_THR_2 B11 Yes B12 Yes
name TRX nb No
HMI PMU_BUFFER_CONGESTION_THR_2 Sub-syste MFS Cell Type No
Definition Threshold defining the second level of buffer congestion in a given PMU (buffers used for LLC PDU storage and the BSCGP signalling message storage).
Coding rules --
Recommended --
rules
External --
comment
Internal comment Used by RRM (for Gb interface protection) and BSCGP (for BSCGP interface protection)
Logical GPU_Gb_Base_IP B11 Yes B12 Yes
name TRX nb No
HMI GPU_Gb_Base_IP Sub-syste MFS Cell Type No
Definition Base address of the IP address of the local Gb IP endpoint, used to define the GPU_Gb_IP_Address of each GPU board (for Gb over IP interface).
The last group is set to 000 (base address)
Mandatory rules --
Recommended --
rules
External Parameter change: if Gb_transport_Mode is already in IP mode, a change of this parameter must be followed by a manual reset of the associated GP/GPU (during the
comment IP settings preparation phase, no manual reset is needed since the reset is automatically performed by the MFS at the feature activation time).
Internal comment changeable from the local operator terminal (IMT)
Logical GPU_Gb_Base_UDP B11 Yes B12 Yes
name TRX nb No
HMI GPU_Gb_Base_UDP Sub-syste MFS Cell Type No
Definition Base port number of the UDP port number of the local Gb IP endpoint, used to define the GPU_Gb_UDP_port of each GPU board (for Gb over IP interface).
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment Min = hF800, Max = hFC00
changeable from the local operator terminal (IMT)
Logical GPU_Gb_IP_Address B11 Yes B12 Yes
name TRX nb No
HMI GPU_Gb_IP_Address Sub-syste MFS Cell Type No
name Instance GPU RMS No
Definition Allows to display the IP address of the local Gb IP endpoint, used by a GPU board in a NSE instance (for Gb over IP interface)
coded default value is for implementation purposes only
Mandatory rules --
Recommended --
rules
External Calculated by the MFS from the GPU_Gb_Base_IP value.
comment
Internal comment --
Logical GPU_Gb_UDP_Port B11 Yes B12 Yes
name TRX nb No
HMI GPU_Gb_UDP_Port Sub-syste MFS Cell Type No
Definition Allows to display the UDP port number of the local Gb IP endpoint, used by a GPU board in a NSE instance (for Gb over IP interface).
Coding rules --
Mandatory rules --
Recommended --
rules
External equal to GPU_Gb_base_UDP.
comment
Internal comment Min = hF800, Max = hFC00
The same port is used on all the GPU boards
Logical GSL_LOSS_RESET_DATA B11 No B12 Yes
name TRX nb No
HMI GSL_LOSS_RESET_DATA Sub-syste MFS Cell Type No
Definition Defines the GP reset strategy in case of loss of all the GSL links of a given GP.
Coding rules 0: all the GPs, connected to the same impacted BSC, perform a reset
1:only the impacted GP performs a reset
Mandatory rules --
Recommended Alcatel-Lucent recommends setting this parameter to 1 in order to reduce PS outage in case of loss of all the GSL links of a given GP
rules
External - Available on MFS Evolution only
Internal comment 0: B11 behaviour
1: new behaviour
Logical GSL_PRIORITY (MFS) B11 Yes B12 Yes
name TRX nb No
HMI GSL_PRIORITY (MFS) Sub-syste MFS Cell Type No
Definition BSS internal priority used by the GSL flow in IP network
3: lower priority
Mandatory rules Shall be equal to GSL_PRIORITY (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical HALFPWR_BEAM_WIDTH B11 Yes B12 Yes
name TRX nb No
HMI HALFPWR_BEAM_WIDTH Sub-syste MFS Cell Type No
Definition Antenna half power beam for the sector supporting the cell (used by the MFS to compute location estimate based on TA positionning method).
Coding rules 0: half power beam width unknown, 1: 1 degree,, 360: 360 degree (omnidirectional cell)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical HIGH_PRECEDENCE_BACKGROUND_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI HIGH_PRECEDENCE_BACKGROUND_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for Background Packet Flow Context, with precedence parameter set to 'high'
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical HIGH_PRECEDENCE_INSTANT_MSG_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI HIGH_PRECEDENCE_INSTANT_MSG_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the TBF relative priority used for Instant message service DL PDU, with precedence parameter set to 'high'.
Coding rules 4 : highest priority
15: lowest priority
Mandatory rules HIGH_PRECEDENCE_INSTANT_MSG_ PRIORITY
= NORMAL_PRECEDENCE_INSTANT_MSG_ PRIORITY
= LOW_PRECEDENCE_INSTANT_MSG_ PRIORITY
Recommended --
rules
External - Significant only if EN_INSTANT_MSG_SERVICE is enabled
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied after modification
Internal comment - CMCC requires to set to a priority lower than BEST_EFFORT_PRIORITY
Logical HIGH_PRECEDENCE_THP1_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI HIGH_PRECEDENCE_THP1_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for Interactive THP1 Packet Flow Context, with precedence parameter set to 'high'
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IEUTM_MAX_IDLE_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI IEUTM_MAX_IDLE_PERIOD Sub-systeMFS Cell Type No
Definition Maximum duration of UL TBF inactivity before MS is polled in EUTM mode when EN_EXTENDED_UL_TBF is set ot 2 (IEUTM enabled).
Mandatory rules --
Recommended --
rules
External Change of parameter value is taken into account also for on-going UL TBFs
comment
Internal comment The value of the parameter should be greater than Round Trip Delay and greater than T_EXTENDED_UL_TBF_POL.
The precision of the idle period may vary as it is linked to the MAC scheduling.
Logical INIT_PDCH_SHORT_DATA_EGPRS B11 Yes B12 Yes
name TRX nb No
HMI INIT_PDCH_SHORT_DATA_EGPRS MFS Sub-syste Cell Type No
name cell Instance RMS No
Definition Number of PDCHs on which MAX_EGPRS_MCS_SHORT_DATA_DL and MAX_EGPRS_MCS_SHORT_DATA_UL are targeted when establishing GCHs for an EGPRS TBF
associated to a short data MS transfer.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Parameter change: No impact on the telecom service, on going TBF are not disrupted. Change applied on current TBF and new TBF established after modification
Internal comment --
Logical INIT_PDCH_SHORT_DATA_GPRS B11 Yes B12 Yes
name TRX nb No
HMI INIT_PDCH_SHORT_DATA_GPRS MFS Sub-syste Cell Type No
Definition Number of PDCHs on which MAX_GPRS_CS_SHORT_DATA_DL and MAX_GPRS_CS_SHORT_DATA_UL are targeted when establishing GCHs for a GPRS TBF
associated to a short data MS transfer.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Parameter change: No impact on the telecom service, on going TBF are not disrupted. Change applied on current TBF and new TBF established after modification.
Internal comment --
Logical IP_BTS_LOAD_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI IP_BTS_LOAD_THR_1 Sub-syste MFS Cell Type No
Definition Threshold beyond which a given TRE module is considered as "loaded" in terms of SCP CPU load by RRM (IP BTS)
Mandatory rules IP_BTS_LOAD_THR_1 < IP_BTS_LOAD_THR_2
Recommended
rules
External --
comment
Internal comment --
Logical IP_BTS_LOAD_THR_2 B11 Yes B12 Yes
name TRX nb No
HMI IP_BTS_LOAD_THR_2 Sub-syste MFS Cell Type No
Definition Threshold beyond which a given TRE module is considered as "overloaded" in terms of SCP CPU load by RRM (IP BTS).
Mandatory rules IP_BTS_LOAD_THR_1 < IP_BTS_LOAD_THR_2
Recommended
rules
External --
comment
Internal comment --
Logical IP_PFC_PRIORITY_MAPPING B11 Yes B12 Yes
name TRX nb No
HMI IP_PFC_PRIORITY_MAPPING Sub-syste MFS Cell Type No
Definition Mapping between PFC priorities (0 to 15) and IP priorities used in the BSS for GPRS (GBR, BE)
Category System (CST) OMC-R access None (DLS) Type Reference Unit None
Rec ref. None Domai IP 0 Coded Min 0
Spec ref. GPRS radio interface - RLC sublayer 1 Coded Max 65535
1
Coding rules Bitmap. Each bit indicates for a given PFC priority whether it shall be mapped on GBR priority (0) or BE priority (1).
Bit 0 (the most right) represents priority 0 (low level mechanisms)
Bit 1 represents priority 1 (SIGNALLING_PRIORITY)
Bit 2 represents priority 2 (conversational)
Bit 3 represents priority 3 (STREAMING_PRIORITY
Bit 4 represents priority 4
.
Bit 15 (the most left) represents priority 15
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPBSS_SUBNET_MASK_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPBSS_SUBNET_MASK_MFS Sub-syste MFS Cell Type No
Definition Mask of the subnet where is allocated the range of MFS addresses used for
IPGCH / IPGSL protocol
Mandatory rules --
Recommended --
rules
External Parameter change: if BSS_TRANSPORT_MODE is already in IP mode, a change of this parameter must be followed by a manual reset of all the GPs connected to the IP
comment BSS (during the IP settings preparation phase, no manual reset is needed since the reset is automatically performed by the MFS at the feature activation time).
Internal comment - changeable from the local operator terminal (IMT)
Logical IPGB_SUBNET_MASK_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGB_SUBNET_MASK_MFS Sub-syste MFS Cell Type No
Definition Mask of the subnet where is allocated the range of MFS addresses used for
Gb telecom protocols
Mandatory rules --
Recommended --
rules
Internal comment changeable from the local operator terminal (IMT)
Logical IPGCH_Base_Address_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGCH_Base_Address_MFS Sub-syste MFS Cell Type No
Definition Base address of the local IP address used by the MFS to define the IP address used by the IPGCH protocol on each GP board
Mandatory rules --
Recommended --
rules
External - Operator must take care that a MFS will reserve 30 GP address max from this base.
comment - Parameter change: if BSS_TRANSPORT_MODE is already in IP mode, a change of this parameter must be followed by a manual reset of the GPs connected to the IP
BSS (during the IP settings preparation phase, no manual reset is needed since the reset is automatically performed by the MFS at the feature activation time).
Logical IPGCH_DL_BW_CONTROL_REPEAT_RATE B11 Yes B12 Yes
name TRX nb No
HMI IPGCH_DL_BW_CONTROL_REPEAT_RATE Sub-syste MFS Cell Type No
Definition Parameter to control the repetition rate of the delay measurements performed in DL by IPGCH.
Mandatory rules The operator must control that 6 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL > round trip delay between PCU and BTS. If that rule is not
respected (typically in case of BTS to PCU transport over satellite (round_trip_delay >= 500ms)), the PS traffic can be totally blocked.
Recommended - 6 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL >= IPGCHU_DELAY_HIGH_THRES_DL (because there are 6 polling request contexts per PTU
for
rules IPGCHU at PCU side).
- 3 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL >= round trip delay between PCU and BTS (because there are 3 polling request contexts per
PTU
for IPGCHC at PCU side). If that recommendation were not followed (typically in case of BTS to PCU transport over satellite (round_trip_delay >= 500ms)), the IPGCHC
shaping would be less efficient.
External Delay measurement will be done every IPGCH_DL_BW_CONTROL_REPEAT_RATE * T_IPGCH_ACK_UL
comment Measurements are done on an Abis basis.
Internal comment --
Logical IPGCH_IP_Address_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGCH_IP_Address_MFS Sub-syste MFS Cell Type No
Definition Allow to display the IP address of the IPGCH link used by IPGCH component on the PCU side.
Mandatory rules --
Recommended --
rules
External Calculated by the PCU from IPGCH_Base_Address_MFS
comment
Internal comment --
Logical IPGCH_UL_BW_CONTROL_REPEAT_RATE B11 Yes B12 Yes
name TRX nb No
HMI IPGCH_UL_BW_CONTROL_REPEAT_RATE Sub-syste MFS Cell Type No
Definition Parameter to control the repetition rate of the delay measurements in UL for IPGCH.
Mandatory rules The operator must control that 6 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL > round trip delay between PCU and BTS. If that rule is not
Recommended - 6 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL >= IPGCHU_DELAY_HIGH_THRES_UL (because there are 6 polling request contexts per TRE
for
rules IPGCHU at BTS side).
- 3 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL >= round trip delay between PCU and BTS (because there are 3 polling request contexts per
TRE
for IPGCHC at BTS side). If that recommendation were not followed (typically in case of BTS to PCU transport over satellite (round_trip_delay >= 500ms)), the IPGCHC
External Delay measurement will be done every IPGCH_UL_BW_CONTROL_REPEAT_RATE * T_IPGCH_ACK_UL. Measurements are done on a TRE basis.
comment
Internal comment - Sent to the BTS via IPGCH.
Logical IPGCHC_Base_TCP_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGCHC_Base_TCP_MFS Sub-syste MFS Cell Type No
Definition Base for the TCP port number used by the PCU for IPGCHC protocol. This base is used to define the TCP ports for each PTU access. The same base is used by each PMU
(they have different IP addresses to be distinguished).
Coding rules --
Mandatory rules --
Recommended --
rules
External - Parameter change: if BSS_TRANSPORT_MODE is already in IP mode, a change of this parameter must be followed by a manual reset of the PMUs connected to the
comment IP BSS (during the IP settings preparation phase, no manual reset is needed since the reset is automatically performed by the BSS at the feature activation time).
Internal comment - At MFS side, it has been chosen to use the same allowed range as at the BTS side (IPGCHC_TCP_PORT_BTS (BTS)=[53504-54527]). Since a MFS can reserve up to
MAX_TRX_GP (=960) TCP ports from this base, the max value of the base has been reduced accordingly.
Logical IPGCHC_PRIORITY (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHC_PRIORITY Sub-syste MFS Cell Type No
Definition BSS internal priority used by the IPGCH Control flow in IP network
3: lower priority
Mandatory rules Equal to IPGCHC_PRIORITY (BTS)
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_ACK_SEND_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_ACK_SEND_THRESHOLD Sub-systeMFS Cell Type No
Definition Threshold on the IPGCHU BE/GBR receive window size above which an uplink acknowledgement for IPGCHU uplink data is sent by the PCU to the BTS / a downlink
acknowledgement for IPGCHU downlink data is sent by the BTS to the PCU.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent by the MFS to the BTS via IPGCH.
- This parameter allows to speed up the acknowledgements (if there is too much traffic in regard to the value of the timers T_IPGCH_ACK_DL or T_IPGCH_ACK_UL).
If IPGCHU_ACK_SEND_THRESHOLD is set to 100%, then the receive-window-size-based event for acknowledgement sending is turned off.
Logical IPGCHU_Base_UDP_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_Base_UDP_MFS Sub-syste MFS Cell Type No
Definition Base for the UDP port number used by each GP board of the MFS for IPGCHU protocol.
Coding rules --
Mandatory rules --
Recommended --
rules
External Parameter change: if BSS_TRANSPORT_MODE is already in IP mode, a change of this parameter must be followed by a manual reset of the GPs connected to the IP

- IPGCHU_UDP_PORT_MFS = IPGCHU_Base_UDP_MFS
Logical IPGCHU_BE_PRIORITY (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BE_PRIORITY Sub-syste MFS Cell Type No
Definition BSS internal priority used by the IPGCH Best Effort flow in IP network
3: lower priority
Mandatory rules Equal to IPGCHU_BE_PRIORITY (BTS)
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_BE_UL_THRES B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BE_UL_THRES Sub-syste MFS Cell Type No
Definition Threshold on the size of the IPGCH BE queue of a TRE, which is used by MAC (in the USF scheduling algorithms) in order to avoid the overflow of this queue. This
parameter only concerns the UL traffic.
Coding rules Step size = 1 IPGCH container
Mandatory rules IPGCHU_ExtraGBR_UL_THRES < IPGCHU_BE_UL_THRES
Recommended --
rules
External --
comment
Internal comment - Configured via PMU-PTU interface.
Logical IPGCHU_BW_MAX_CONG_DL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BW_MAX_CONG_DL Sub-syste MFS Cell Type No
Definition Percentage of the total Abis bandwidth (cf. the ABIS_BANDWIDTH parameter) indicating the maximum Abis bandwidth usable by the Best-Effort IPGCHU in downlink
when in congested operation, for a given Abis BTS group.
Mandatory rules IPGCHU_Nominal_Abis_BW_Factor >= IPGCHU_BW_MAX_CONG_DL

IPGCHU_BW_MIN_CONG_DL <= IPGCHU_BW_MAX_CONG_DL
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_BW_MAX_CONG_UL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BW_MAX_CONG_UL Sub-syste MFS Cell Type No
Definition Maximum Abis bandwidth usable by the Best-Effort IPGCHU in uplink when in congested operation, for a given TRE with 8 active PDCHs.
Coding rules Step size = 10 kbit/s
Mandatory rules IPGCHU_BW_MIN_CONG_UL <= IPGCHU_BW_MAX_CONG_UL
Recommended --
rules
External --
comment
Internal comment - The coded value is sent by the MFS to the BTS via IPGCH.
- The maximum value of 1Mbps corresponds to a hardware limit per TRE inside the BTS.
Logical IPGCHU_BW_MIN_CONG_DL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BW_MIN_CONG_DL Sub-syste MFS Cell Type No
Definition Percentage of the total Abis bandwidth (cf. the ABIS_BANDWIDTH parameter) indicating the minimum Abis bandwidth usable by the Best-Effort IPGCHU in downlink when
in congested operation, for a given Abis BTS group.
Mandatory rules IPGCHU_BW_MIN_CONG_DL <= IPGCHU_BW_MAX_CONG_DL
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_BW_MIN_CONG_UL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_BW_MIN_CONG_UL Sub-syste MFS Cell Type No
Definition Minimum Abis bandwidth usable by the Best-Effort IPGCHU in uplink when in congested operation, for a given TRE with 8 active PDCHs.
Coding rules Step size = 10 kbit/s
Mandatory rules IPGCHU_BW_MIN_CONG_UL <= IPGCHU_BW_MAX_CONG_UL
Recommended --
rules
External --
comment
- The maximum value of 1Mbps corresponds to a hardware limit per TRE inside the BTS.
Logical IPGCHU_ExtraGBR_UL_THRES B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_ExtraGBR_UL_THRES Sub-syste MFS Cell Type No
Definition Threshold on the size of the internal IPGCH extra GBR queue of a TRE, which is used by MAC (in the USF scheduling algorithms) in order to avoid the overflow of this
queue. This parameter only concerns the UL traffic.
Mandatory rules IPGCHU_ExtraGBR_UL_THRES < IPGCHU_BE_UL_THRES
Recommended --
rules
External --
comment
Logical IPGCHU_GBR_PRIORITY (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_GBR_PRIORITY Sub-syste MFS Cell Type No
Definition BSS internal priority used by the IPGCH GBR flow in IP network
3: lower priority
Mandatory rules Equal to IPGCHU_GBR_PRIORITY (BTS)
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_GBR_UL_THRES B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_GBR_UL_THRES Sub-syste MFS Cell Type No
Definition Threshold on the size of the IPGCH GBR queue of a TRE, which is used by MAC (in the USF scheduling algorithms) in order to avoid the overflow of this queue. This
parameter only concerns the UL traffic.
Mandatory rules --
Recommended --
rules
External --
comment
Logical IPGCHU_MAX_PATTERN_MEAS_THROUGHPUT_DL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_MAX_PATTERN_MEAS_THROUGHPUT_DL Sub-syste MFS Cell Type No
Definition Maximum number of patterns used to compute the current Abis BE throughput used by IPGCHU in DL.
Coding rules step size = 1 pattern
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_Nominal_Abis_BW_Factor B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_Nominal_Abis_BW_Factor Sub-syste MFS Cell Type No
Definition Percentage of the total Abis bandwidth (cf. the ABIS_BANDWIDTH parameter) indicating the maximum Abis bandwidth usable by the Best-Effort IPGCHU in downlink, for a
given Abis BTS group.
Mandatory rules IPGCHU_Nominal_Abis_BW_Factor >= IPGCHU_BW_MAX_CONG_DL
Recommended
rules
External --
comment
Internal comment - In case of variable Abis bandwidth (e.g. micro-wave), the ABIS_BANDWIDTH parameter should be positioned to the minimum guaranteed bandwidth. Thus, in such a
case, setting the IPGCHU_Nominal_Abis_BW_Factor parameter to a value higher than 100% may make sense.
Logical IPGCHU_PATTERN_LIFETIME_DL B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_PATTERN_LIFETIME_DL Sub-syste MFS Cell Type No
Definition Lifetime of a pattern (i.e. time to switch from one pattern to the next one) used to compute the current Abis BE throughput used by IPGCHU in DL.
Category Network (CDE) OMC-R access None (DLS) Type Timer Unit ms
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_UDP_MAX_WINDOW_SIZE_GP B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_UDP_MAX_WINDOW_SIZE_GP Sub-syste MFS Cell Type No
Definition Maximum UDP window size for IPGCH usable in the MFS.
Coding rules --
Mandatory rules --
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment - The value 2000 stems from the product requirement to support:
- 1,92 Mbps per MC module when using Abis and Ater terrestrial links (i.e. Edge traffic in MCS-9 on 8 PDCHs on 4 TRXs),
- 960 kbps per MC module when using Abis or Ater satellite links (i.e. Edge traffic in MCS-9 on 8 PDCHs on 2 TRXs).
Logical IPGCHU_UDP_PORT_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_UDP_PORT_MFS Sub-syste MFS Cell Type No
Definition UDP port used by the IPGCHU protocol on MFS side by each GP board. The same UDP port is used by each GP board (they have different IP addresses to be
distinguished)
Mandatory rules --
Recommended --
rules
External MFS can use 2 source UDP ports (IPGCHU_UDP_PORT_MFS and IPGCHU_UDP_PORT_MFS + 1) to send DL traffic towards the destination
IPGCHU_UDP_PORT_BTS
comment port of the BTS.
Internal comment - Min = hD000, Max = hD0FF. At migration from B10 to B11, no IP EndPoint exists at OMC (neither at MFS). Sent by the MFS to the BTS in IPGCH_init_req message.
- IPGCHU_UDP_PORT_MFS = IPGCHU_Base_UDP_MFS
Logical IPGCHU_XOFF_BE_FIFO_DL_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_XOFF_BE_FIFO_DL_THRESHOLD Sub-syste MFS Cell Type No
Definition Threshold on the BE queue filling level to trigger an Xoff state for the BE DL flow of a given PTU (back pressure mechanism between RRM-PCC and IPGCH for the BE DL
flow).
Coding rules Step size = 1 LLC PDU
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_XOFF_GBR_FIFO_DL_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_XOFF_GBR_FIFO_DL_THRESHOLD Sub-syste MFS Cell Type No
Definition Threshold on the GBR queue filling level to trigger an Xoff state for the GBR DL flow of a given PTU (back pressure mechanism between RRM-PCC and IPGCH for the
strict GBR DL flow).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_XON_BE_FIFO_DL_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_XON_BE_FIFO_DL_THRESHOLD Sub-syste MFS Cell Type No
Definition Threshold on the BE queue filling level to trigger an Xon state for the BE DL flow of a given PTU (back pressure mechanism between RRM-PCC and IPGCH for the BE DL
flow).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPGCHU_XON_GBR_FIFO_DL_THRESHOLD B11 Yes B12 Yes
name TRX nb No
HMI IPGCHU_XON_GBR_FIFO_DL_THRESHOLD Sub-syste MFS Cell Type No
Definition Threshold on the GBR queue filling level to trigger an Xon state for the GBR DL flow of a given PTU (back pressure mechanism between RRM-PCC and IPGCH for the
strict GBR DL flow).
Coding rules Step size = 1 LLC PDU.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical IPGSL_Base_Address_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_Base_Address_MFS Sub-syste MFS Cell Type No
Definition Base address of the local IP address used to define the IP address used by the IPGSL on each GP board.
Mandatory rules --
Recommended --
rules
External - Operator must take care that a MFS will reserve 30 GP address max from this base.
comment - Parameter change: if BSS_TRANSPORT_MODE is already in IP mode, a change of this parameter must be followed by a manual reset of the GPs connected to the IP
BSS (during the IP settings preparation phase, no manual reset is needed since the reset is automatically performed by the MFS at the feature activation time).
Logical IPGSL_BASE_TCP_MFS B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_BASE_TCP_MFS Sub-syste MFS Cell Type No
Definition TCP port number used to configure the TCP port number of each GP board of the MFS for IPGSL interface.
Coding rules --
Mandatory rules --
Recommended --
rules
External Parameter change: if BSS_TRANSPORT_MODE is already in IP mode, a change of this parameter must be followed by a manual reset of the GPs connected to the IP
Internal comment - IPGSL_TCP_PORT_MFSside (MFS) = IPGSL_BASE_TCP_MFS

IPGSL_BASE_TCP_MFS is needed because it is configured by the IMT (at MFS level) and IPGSL_TCP_PORT_MFSside (MFS) is per GP.
- value = h'CD90
Logical IPGSL_IP_Address_BSCside (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_IP_Address_BSCside Sub-syste MFS Cell Type No
Definition IP address of the IPGSL link on BSC side.
Category Site (CAE) OMC-R access Virtual changeable Type IP address Unit None
Mandatory rules Equal to IPGSL_IP_Address_BSCside (BSC)
Recommended --
rules
External - Parameter change: After the change of this parameter on BSC side, the MFS will perform an automatic reset of all the GPs connected to this BSS (PS traffic is
comment interrupted in the BSS).
Internal comment - The OMC stay aware of the parameter value on BSC side for displaying, and also for synchronization (when the value changed on BSC side, the OMC realigns the
value on MFS side)
Logical IPGSL_IP_Address_MFSside (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_IP_Address_MFSside Sub-syste MFS Cell Type No
Definition IP address of the IPGSL link on MFS side.
The value is calculated by the MFS from IPGSL_Base_Address_MFS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - The OMC stay aware of the parameter value on MFS side for displaying, and also for synchronization (when the value changed on MFS side, the OMC realigns the
value on BSC side)
Logical IPGSL_MSS (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_MSS (MFS) Sub-syste MFS Cell Type No
Definition MSS (Maximum Segment Size) value used by the TCP stack for IPGSL protocol in the MFS.
Mandatory rules --
Recommended IPGSL_MSS (BSC) = IPGSL_MSS (MFS)

rules IPGSL_MSS >= 264 (max size of one BSCGP message)
External To avoid TCP segmentation, the TCP MSS shall be > max size of BSCGP messages (264).
comment
Internal comment - Used to configure the TCP stacks
Logical IPGSL_TCP_PORT_BSCside (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_TCP_PORT_BSCside Sub-syste MFS Cell Type No
Definition TCP port number for the BSC side of the IPGSL link, used by the MFS .
Coding rules --
Mandatory rules equal to IPGSL_TCP_PORT_BSCside (BSC)
Recommended --
rules
External --
comment
Internal comment - The OMC stay aware of the parameter value on BSC side for displaying, and also for synchronization (in case the value is changed on BSC side, the OMC realigns
the value on MFS side; however this will not happen because only one value is possible)
- Only one port value is used: indeed, TCP uses (Server IP address + Server TCP Port + Client IP Address + Client TCP Port) to distinguish the different connections.
Note: in order to distinguish easily each side of the protocol, different value at BSC side and MFS side could be used but by default, the same value is used by BSC
and MFS.
- Min=hCD90, Max=hCD91
Logical IPGSL_TCP_PORT_MFSside (MFS) B11 Yes B12 Yes
name TRX nb No
HMI IPGSL_TCP_PORT_MFSside Sub-syste MFS Cell Type No
Definition TCP port number used by each GP board of the MFS for IPGSL interface.
Coding rules --
Mandatory rules --
Recommended --
rules
External Each GP board uses the same TCP port number (they can be distinguished by their IP address).
comment
Internal comment - The OMC stay aware of the parameter value on MFS side for displaying, and also for synchronization (in case the value is changed on MFS side, the OMC realigns
the value on BSC side, however this will not happen because only one value is possible).
- one value is used: h'CD90
- IPGSL_TCP_PORT_MFSside (MFS) = IPGSL_BASE_TCP_MFS
Logical K_GSL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI K_GSL (MFS) Sub-syste MFS Cell Type No
Definition Maximum number of outstanding I frames on a GSL link.
Coding rules --
Mandatory rules --
Recommended It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Ater satellite links:
rules - K_GSL = 7 if GPRS traffic is carried through Ater terrestrial links in all BSC of the MFS.
- K_GSL = 16 if GPRS traffic is carried through Ater satellite links in at least one BSC of the MFS.
External --
comment
Internal comment --
Logical LAC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI LAC Sub-syste MFS Cell Type No
Coding rules --
Equal to LAC (BSC)
A couple of mate extended cells (Extended inner + extended outer) shall have the same LAC
Recommended --
rules
comment
Internal comment --
Logical LAC(n) (MFS) B11 Yes B12 Yes
name TRX nb No
HMI LAC Sub-syste MFS Cell Type No
Coding rules --
Equal to LAC(n)(BSC)
Recommended --
rules
comment
Internal comment --
Logical LCS_AZIMUTH B11 Yes B12 Yes
name TRX nb No
HMI AZIMUTH Sub-syste MFS Cell Type No
Definition Antenna direction orientation for the sector supporting the cell (used by the MFS to compute location estimate based on TA positionning method).
Coding rules 0: 0 degree,, 359: 359 degree, 360: omnidirectional cell
Mandatory rules --
Recommended --
rules
External 0 corresponds to the North orientation and is coun ted clockwise.
comment
Internal comment This parameter is considered as being significant as soon as the geographical coordinates are significant.
Logical LCS_LATITUDE B11 Yes B12 Yes
name TRX nb No
HMI LATITUDE Sub-syste MFS Cell Type No
Definition Latitude of the BTS supporting the cell (used by the MFS to compute location estimate based on TA positionning method).
Rec ref. None Domai LCS Min value 0,0,0,false Coded Min
n Max value 90,59,9999,true Coded Max
Spec ref. LCS Functional Specification Coded Max
Coding rules Sequence of:
- number of degrees (from 0 to 90)
- number of minutes (from 0 to 59)
- number of fractional minutes (from 0 to 9999)
- direction (boolean, true for South and false for North)
Mandatory rules --
Recommended --
rules
External 1) 0 latitude corresponds to the Equator;
comment 2) The coding for OMC-R HMI is described in the "BSS O&M Parameters" document, parameter "LCS-Latitude".
Internal comment 1) This parameter is significant only when GEOGRAPHICAL_COORDINATES_FLAG is set to true;
2) the coding rules are only valid for MFS-OMC interface. The coding for OMC-R HMI is different due to the REAL numbers management constraint.
Logical LCS_LONGITUDE B11 Yes B12 Yes
name TRX nb No
HMI LONGITUDE Sub-syste MFS Cell Type No
Definition Longitude of the BTS supporting the cell (used by the MFS to compute location estimate based on TA positionning method).
Rec ref. None Domai LCS Min value 0,0,0,false Coded Min
n Max value 180,59,9999,true Coded Max
Spec ref. LCS Functional Specification Coded Max
Coding rules Sequence of:
- number of degrees (from 0 to 180)
- number of minutes (from 0 to 59)
- number of fractional minutes (from 0 to 9999)
- direction (boolean, true for West and false for East)
Mandatory rules --
Recommended --
rules
External 1) 0 longitude corresponds to the Greenwich Meridi an;
comment 2) The coding for OMC-R HMI is described in the "BSS O&M Parameters" document, parameter "LCS-Longitude".
Internal comment 1) This parameter is significant only when GEOGRAPHICAL_COORDINATES_FLAG is set to true;
2) the coding rules are only valid for MFS-OMC interface. The coding for OMC-R HMI is different due to the REAL numbers management constraint.
Logical Length_On_Going_Requests_ListA_HIGH_CAP B11 Yes B12 Yes
name TRX nb No
HMI Length_On_Going_Requests_ListA_HIGH_CAP Sub-syste MFS Cell Type No
Definition Maximum number of on-going requests in list A when the MFS is connected to a BSC high capacity (ie BSC Evolution). List A is used for on-going requests towards the
BSC on the BSCGP interface for the following messages: Detach Request, GIC Group State Request, Transmission Allocation Request, Transmission Deallocation
Command.
Coding rules --
Mandatory rules In case of multi-GP/GPU configuration, the value to be used by each GP/GPU is the above parameter divided by the number of configured GP/GPU boards connected to
the same BSC
Recommended --
rules
External --
comment
Internal comment --
Logical Length_On_Going_Requests_ListA_LOW_CAP B11 Yes B12 Yes
name TRX nb No
HMI Length_On_Going_Requests_ListA_LOW_CAP Sub-syste MFS Cell Type No
Definition Maximum number of on-going requests in list A when the GP/GPU is connected to a BSC low capacity (ie BSC G2). List A is used for on-going requests towards the BSC
on the BSCGP interface for the following messages: Detach Request, GIC Group State Request, Transmission Allocation Request, Transmission Deallocation Command.
Coding rules --
the same BSC.
Recommended --
rules
External --
comment
Internal comment --
Logical Length_On_Going_Requests_ListB_HIGH_CAP B11 Yes B12 Yes
name TRX nb No
HMI Length_On_Going_Requests_ListB_HIGH_CAP Sub-syste MFS Cell Type No
Definition Maximum number of on-going requests in list B when the MFS is connected to a BSC high capacity (ie BSC Evolution). List B is used for on-going requests towards the
BSC on the BSCGP interface for the following messages: Ater Reset, BSC Reset, BSS Traffic Control Request, Cell Reset, Start GPRS, Cell State Request, BSC State
Request, Stop GPRS, Update GPRS Parameters Request, Extra ABIS Pool Configuration Request.
Coding rules --
the same BSC.
Recommended --
rules
External --
comment
Internal comment --
Logical Length_On_Going_Requests_ListB_LOW_CAP B11 Yes B12 Yes
name TRX nb No
HMI Length_On_Going_Requests_ListB_LOW_CAP Sub-syste MFS Cell Type No
Definition Maximum number of on-going requests in list B when the GP/GPU is connected to a BSC low capacity (ie BSC G2). List B is used for on-going requests towards the BSC
on the BSCGP interface for the following messages: Ater Reset, BSC Reset, BSS Traffic Control Request, Cell Reset, Start GPRS, Cell State Request, BSC State Request,
Stop GPRS, Update GPRS Parameters Request, Extra ABIS Pool Configuration Request.
Coding rules --
the same BSC.
Recommended --
rules
External --
comment
Internal comment --
Logical Length_Suspended_Requests_QueueA_GP B11 Yes B12 Yes
name TRX nb No
HMI Length_Suspended_Requests_QueueA_GP Sub-syste MFS Cell Type No
Definition Maximum number of suspended requests in queue A on a GP board. Queue A is used for suspended requests towards the BSC on the BSCGP interface for the following
messages: Detach Request, GIC Group State Request, Transmission Allocation Request, Transmission Deallocation Command.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment 500 corresponds to the maximum number of cells per BSS.
Logical Length_Suspended_Requests_QueueB_GP B11 Yes B12 Yes
name TRX nb No
HMI Length_Suspended_Requests_QueueB_GP Sub-syste MFS Cell Type No
Definition Maximum number of suspended requests in queue B on a GP board. Queue B is used for suspended requests towards the BSC on the BSCGP interface for the following
messages: Ater Reset, BSC Reset, BSS Traffic Control Request, Cell Reset, Start GPRS, Cell State Request, BSC State Request, Stop GPRS, Update GPRS Parameters
Request, Extra ABIS Pool Configuration Request.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment 500 corresponds to the maximum number of cells per BSS
Logical LONG_TBF_SIZE B11 No B12 Yes
name TRX nb No
HMI LONG_TBF_SIZE_PACKET_SIZE_THR Sub-syste MFS Cell Type No
Definition This parameter has a double purpose, covering 2 independant features :
- It is the threshold used to check the Number of transmitted bytes of a TBF: above this threshold a TBF is considered as Long TBF
- It is also the threshold used to check the packet size in a TBF, below this threshold a TBF is considered as Small Packet Size TBF. The packet size detection
threshold is used to control the number of allocated radio timeslots.
Coding rules step size = 10 bytes
Mandatory rules --
Recommended --
rules
comment - Significant if EN_ LONG_TBF_WEIGHT(MFS) is enabled.
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the TBF established after modification.
Logical LONG_TBF_WEIGHT B11 No B12 Yes
name TRX nb No
HMI LONG_TBF_WEIGHT Sub-syste MFS Cell Type No
Definition Defines the relative weight used for the long TBF (without PFC)
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Significant if EN_LONG_TBF_WEIGHT is enabled.
- 45 = Maximum_Weight (> max(Weight_Px = 15)
- def = 15 > 4 (=def of Weight_P12 and def of BEST_EFFORT_PRIORITY = 12)
Logical LOW_PRECEDENCE_BACKGROUND_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI LOW_PRECEDENCE_BACKGROUND_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for Background Packet Flow Context, with precedence parameter set to 'low'
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical LOW_PRECEDENCE_INSTANT_MSG_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI LOW_PRECEDENCE_INSTANT_MSG_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the TBF relative priority used for Instant message service DL PDU, with precedence parameter set to 'Low'.
15: lowest priority
Recommended --
rules
Logical LOW_PRECEDENCE_THP1_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI LOW_PRECEDENCE_THP1_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for Interactive THP1 Packet Flow Context, with precedence parameter set to 'low'
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical LSA_ID_array (MFS) B11 Yes B12 Yes
name TRX nb No
HMI LSA_ID_I Sub-syste MFS Cell Type No
Definition List of authorised LSAs on a cell (up to 5).
Mandatory rules Equal to LSA_ID_array (BSC)
Recommended The LSA_ID may either be a Universal LSA identity (in case of odd number) or a PLMN significant LSA identity (in case of even number), as defined in GSM 03.03.
rules
External The default value depends on the configuration. The value given here is for implementation purposes only.
comment
Internal comment The limitation to 5 LSA_Ids is due to data storage limitation in the BSC.
The maximum 0xFFFFFF is reserved as unvalid value for implementation purpose.
Logical LSA_ID_array (n) B11 Yes B12 Yes
name TRX nb No
HMI LSA_ID_I(n) Sub-syste MFS Cell Type No
Definition List of authorised LSAs on a neighbour cell (up to 5).
Mandatory rules --
Recommended --
rules
External This parameter is for every cell. The operator needs only to configure the value of that parameter for OMC external cells ; the parameter is autonomously filled by the
comment OMC in case the adjacent cell is an OMC internal cell.
Internal comment The maximum 0xFFFFFF is reserved as unvalid value for implementation purpose.
Logical MATE_CI (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MATE_CI Sub-syste MFS Cell Type No
Definition Cell Identity of the Mate cell
Coding rules --
Mandatory rules MATE_CI (MFS) = MATE_CI (BSC)

If one mate cell is configured with GPRS (MAX_PDCH > 0) then the other mate cell shall also be configured with GPRS (MAX_PDCH > 0).
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes
comment MATE_CI is relevant for extended cells only
Internal comment a cleanup is performed before the migration of the OMC to .an OMC version supporting PS in extended cell in order to have extended cell with relevant mate in any
case .
The value 1 is sent by the OMC for the normal cells
Logical MAX_ADJ_CELL B11 Yes B12 Yes
name TRX nb No
HMI MAX_ADJ_CELL Sub-syste MFS Cell Type No
Definition Maximum number of adjacent cells for 1 cell.
Spec ref. GPRS Radio interface - RRM sublayer Coded Max 64
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_AGCH_QUEUING_DELAY B11 Yes B12 Yes
name TRX nb No
HMI MAX_AGCH_QUEUING_DELAY Sub-syste MFS Cell Type No
Definition AGCH queuing time.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_BLER B11 Yes B12 Yes
name TRX nb No
HMI MAX_BLER Sub-syste MFS Cell Type No
Definition Maximum mean BLER value that a TBF can possibly reach
Mandatory rules --
Recommended --
rules
External The MAX_BLER value is used by RRM to evaluate the minimum number of GCHs necessary to support RT traffic on a TRX.
comment
Internal comment --
Logical MAX_CELLS_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_CELLS_GP Sub-syste MFS Cell Type No
Definition Maximum number of cells configured by GP board (Mx-MFS)
Spec ref. GPRS traffic model and performances Coded Max 500
Coding rules --
Mandatory rules MAX_CELLS_GP <= MAX_CTXT_CELLS_GP
Recommended --
rules
comment
Internal comment --
Logical MAX_CTXT_CELLS_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_CTXT_CELLS_GP Sub-syste MFS Cell Type No
Definition Maximum number of cells supported per GP board (Mx-MFS)
Coding rules --
Mandatory rules MAX_CELLS_GP <= MAX_CTXT_CELLS_GP
Recommended --
rules
comment
Internal comment --
Logical MAX_CTXT_MS_GP2 B11 Yes B12 Yes
name TRX nb No
HMI MAX_CTXT_MS_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of MS context supported by GP board (Mx-MFS).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical MAX_CTXT_MS_GP3 B11 No B12 Yes
name TRX nb No
HMI MAX_CTXT_MS_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of MS context supported by GP board (Mx-MFS).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical MAX_CTXT_TBF_GP2 B11 Yes B12 Yes
name TRX nb No
HMI MAX_CTXT_TBF_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of TBF context supported by GP board (Mx-MFS) (in each direction).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment 2880 in UL + 2880 in DL = 5760.
Logical MAX_CTXT_TBF_GP3 B11 No B12 Yes
name TRX nb No
HMI MAX_CTXT_TBF_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of TBF context supported by GP board (Mx-MFS) (in each direction).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment 11520 in UL + 11520 in DL = 23040.
Logical MAX_CTXT_TRX_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_CTXT_TRX_GP Sub-syste MFS Cell Type No
Definition Maximum number of TRX contexts supported by GP board (Mx-MFS).
Coding rules --
Mandatory rules MAX_TRX_GP <= MAX_CTXT_TRX_GP
Recommended --
rules
comment
Internal comment --
Logical MAX_DL_TBF_SPDCH B11 Yes B12 Yes
name TRX nb No
HMI MAX_DL_TBF_SPDCH Sub-syste MFS Cell Type No
Definition Indicative value of the maximum number of DownLink (E)GPRS TBFs per Slave PDCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External - When allocating a DL GPRS TBF: MAX_DL_TBF_SPDCH is the maximum number of GPRS + EGPRS TBFs allowed in DL on each Slave PDCH.
comment - When allocating a DL EGPRS TBF: MAX_DL_TBF_SPDCH is the maximum number of EGPRS TBFs allowed in DL on each Slave PDCH (regardless of the current
number of DL GPRS TBFs).
- When EN_FACTOR_DELAYED_DL_TBF is enabled and FACTOR_DELAYED_DL_TBF set to a value strictly lower than 100%, then more DL TBFs than
MAX_DL_TBF_SPDCH can be multiplexed per Slave PDCH.
Internal comment Within PTU SW, a limit is hardcoded corresponding to the maximum number of DL (E)GPRS TBF resources which can be possibly reached per Slave PDCH (taking into
account TBF allocations and a margin for TBF reallocations). This hardcoded value is set to 16 (cf. MAC specification).
Logical MAX_EGPRS_MCS B11 Yes B12 Yes
name TRX nb No
HMI MAX_EGPRS_MCS Sub-syste MFS Cell Type No
Definition Maximum Modulation and Coding Scheme used for EGPRS traffic in the cell.
Coding rules 0: MCS-1;
1: MCS-2;
2: MCS-3;
3: MCS-4;
4: MCS-5;
5: MCS-6;
6: MCS-7;
7: MCS-8;
8: MCS-9;
Mandatory rules - MAX_EGPRS_MCS >= TBF_DL_INIT_MCS

- MAX_EGPRS_MCS >= TBF_UL_INIT_MCS
- When cell_type = extended outer, then MAX_EGPRS_MCS <= MCS-4
- When EN_BS_PC_PS is enabled and MAX_POW_RED_DYN <> 0, then TARGET_MCS_PR <= MAX_EGPRS_MCS
Recommended R_AVERAGE_EGPRS shall not be set to a bitrate higher than the useful bitrate corresponding to MAX_EGPRS_MCS (e.g. if MAX_EGPRS_MCS = MCS9 =>
rules R_AVERAGE_EGPRS shall not be higher than 59,2kbps).
R_MIN_EGPRS shall not be set to a bitrate higher than the useful bitrate corresponding to Max_EGPRS_MCS. If the above recommended rule is not fulfilled, then some
RT PFCs can be accepted by the BSS whereas it will not be possible to handle their associated GBR. This may result in RT PFC downgrades to Best Effort.
It is advised to set MAX_EGPRS_MCS to a value different from MCS-2 to cope with MEGCH control message granularity in an optimal way.
External Parameter change: In case of value increasing, there is no impact on the telecom service, on going TBF are not disrupted. But in case of value decreasing, the
comment established TBF will continue transferring with the previous limit, so it may happen that some TBF are disrupted due to the possible minimum number of GCH
decreasing.
Internal comment --
Logical MAX_EGPRS_MCS_SHORT_DATA_DL B11 Yes B12 Yes
name TRX nb No
HMI MAX_EGPRS_MCS_SHORT_DATA_DL Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Maximum Modulation and Coding Scheme used for the DL EGPRS TBFs associated to a short data MS transfer.
Coding rules 1: MCS-1 coded as 0
2: MCS-2 coded as 1
3: MCS-3 coded as 2
4: MCS-4 coded as 3
5: MCS-5 coded as 4
6: MCS-6 coded as 5
7: MCS-7 coded as 6
8: MCS-8 coded as 7
9: MCS-9 coded as 8
Mandatory rules --
Recommended In order to avoid establishing too many GCHs during the short data MS transfer phases, it is recommended that MAX [MAX_EGPRS_MCS_SHORT_DATA_DL,
rules MAX_EGPRS_MCS_SHORT_DATA_UL] <= MIN [TBF_DL_INIT_MCS, TBF_UL_INIT_MCS].
This rule also tends to reduce the TBF blocking rate in the cell (by recommending low values for MAX_EGPRS_MCS_SHORT_DATA_DL/UL) and to simplify the cell
configuration.
comment - Setting this parameter to MCS-2 might introduce some problems (because a MCS-2 block consumes exactly 1.00 GCH and might therefore block some of the
MFS-BTS signalling messages to be sent in the M-EGCH link in DL).
- If MAX_EGPRS_MCS_SHORT_DATA_DL is strictly higher than MAX_EGPRS_MCS, then MAX_EGPRS_MCS is used instead.
- Parameter change: In case of value increasing, there is no impact on the telecom service, on going TBF are not disrupted. But in case of value decreasing, the
decreasing.
Internal comment --
Logical MAX_EGPRS_MCS_SHORT_DATA_UL B11 Yes B12 Yes
name TRX nb No
HMI MAX_EGPRS_MCS_SHORT_DATA_UL Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Maximum Modulation and Coding Scheme used for the UL EGPRS TBFs associated to a short data MS transfer.
Coding rules 1: MCS-1 coded as 0
2: MCS-2 coded as 1
3: MCS-3 coded as 2
4: MCS-4 coded as 3
5: MCS-5 coded as 4
6: MCS-6 coded as 5
7: MCS-7 coded as 6
8: MCS-8 coded as 7
9: MCS-9 coded as 8
Mandatory rules --
configuration.
comment - If MAX_EGPRS_MCS_SHORT_DATA_UL is strictly higher than MAX_EGPRS_MCS, then MAX_EGPRS_MCS is used instead.
decreasing.
Internal comment --
Logical MAX_GCH_DSP_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_GCH_DSP_GP Sub-syste MFS Cell Type No
Definition Maximum number of GCH 16 kbit/s handled by a DSP (Mx-MFS).
Coding rules --
Mandatory rules --
Recommended --
rules
comment Applicable to GP2 and GP3 boards
Internal comment This parameter corresponds to a constant hard-coded in the MFS
Logical MAX_GP_PER_BSS B11 Yes B12 Yes
name TRX nb No
HMI MAX_GP_PER_BSS Sub-syste MFS Cell Type No
Definition Value of the committed maximum number of GP boards per BSS for Mx-MFS
Spec ref. Packet service feature list Coded Max 21
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - applicable to stand alone configuration
- Def value = Max value = 9 is applicable to rack shared configuration
Logical Max_GPRS_assign_agch_retrans B11 Yes B12 Yes
name TRX nb No
HMI Max_GPRS_assign_AGCH_retrans Sub-syste MFS Cell Type No
Definition Maximum number of Packet DL Assignment messages retransmitted on PACCH, after which the complete DL TBF establishment procedure may be restarted. This
parameter is applicable only if the Immediate Assignment message has already been sent on AGCH for a MS in non-DRX mode.
Coding rules possible values: 0 to 7 (0: no retransmission)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The retransmission period of the Packet DL Assignment messages on PACCH is computed by the MFS as follows: T_ul_assign_ccch /
(Max_GPRS_assign_agch_retrans + 1)
A period lower than 200 ms may lead to the sending of two Packet DL Assignment messages although the first assignment is correctly acknowledged by the MS. This
behaviour has no consequence, the DL TBF begins after the reception of the first Packet Control Ack messages.
The Max_GPRS_assign_AGCH_retrans parameter is not displayed to the O&M user.
Logical Max_GPRS_assign_pch_retrans B11 Yes B12 Yes
name TRX nb No
HMI Max_GPRS_assign_PCH_retrans Sub-syste MFS Cell Type No
Definition Maximum number of Packet DL Assignment messages retransmitted on PACCH after which the complete DL TBF establishment procedure may be restarted. This
parameter is applicable only if the Immediate Assignment message has already been sent on PCH for a MS in DRX mode.
Coding rules possible values: 0 to 7 (0: no retransmission)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The retransmission period of the Packet DL Assignment messages on PACCH is computed by the MFS as follows:
T_GPRS_assign_pch / (Max_GPRS_assign_pch_retrans + 1) >= 300 ms.
The Max_GPRS_assign_PCH_retrans parameter is not displayed to the O&M user.
Logical MAX_GPRS_CS_SHORT_DATA_DL B11 Yes B12 Yes
name TRX nb No
HMI MAX_GPRS_CS_SHORT_DATA_DL Sub-syste MFS Cell Type No
Definition Maximum coding scheme used for the DL GPRS TBFs associated to a short data MS transfer.
Coding rules 1: CS-1 coded as 0
2: CS-2 coded as 1
3: CS-3 coded as 2
4: CS-4 coded as 3
Mandatory rules --
Recommended In order to avoid establishing too many GCHs during the short data MS transfer phases, it is recommended that MAX [MAX_GPRS_CS_SHORT_DATA_DL,
rules MAX_GPRS_CS_SHORT_DATA_UL] <= MIN [TBF_DL_INIT_CS, TBF_UL_INIT_CS].
This rule also tends to reduce the TBF blocking rate in the cell (by recommending low values for MAX_GPRS_CS_SHORT_DATA_DL/UL) and to simplify the cell
configuration.
comment - Setting this parameter to CS-2 might introduce some problems (because a CS-2 block consumes exactly 1.00 GCH and might therefore block some of the MFS-BTS
signalling messages to be sent in the M-EGCH link in DL).
- If MAX_GPRS_CS_SHORT_DATA_DL is strictly higher than MAX_GPRS_CS, then MAX_GPRS_CS is used instead.
decreasing.
Internal comment --
Logical MAX_GPRS_CS_SHORT_DATA_UL B11 Yes B12 Yes
name TRX nb No
HMI MAX_GPRS_CS_SHORT_DATA_UL Sub-syste MFS Cell Type No
Definition Maximum coding scheme used for the UL GPRS TBFs associated to a short data MS transfer.
Coding rules 1: CS-1 coded as 0
2: CS-2 coded as 1
3: CS-3 coded as 2
4: CS-4 coded as 3
Mandatory rules --
configuration.
comment - If MAX_GPRS_CS_SHORT_DATA_UL is strictly higher than MAX_GPRS_CS, then MAX_GPRS_CS is used instead.
decreasing.
Internal comment --
Logical MAX_LLC_PDU_Lifetime B11 Yes B12 Yes
name TRX nb No
HMI MAX_LLC_PDU_Lifetime Sub-syste MFS Cell Type No
Definition Indicates the maximum time a LLC PDU may remain in queue in the BSS (PCU) even if "infinity" as been indicated by the SGSN.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_MPDCH_DSP_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_MPDCH_DSP_GP Sub-syste MFS Cell Type No
Definition Maximum number of master PDCH which can be handled by a DSP (Mx-MFS).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
This parameter corresponds to a constant hard-coded in the PTU SW.
Logical MAX_MPDCH_PTU_IP B11 Yes B12 Yes
name TRX nb No
HMI MAX_MPDCH_PTU_IP Sub-syste MFS Cell Type No
Definition Maximum number of master PDCH which can be handled by a BTS (PTU)
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Needed for MPDCH feature.
- This parameter corresponds to a constant hard-coded in the PTU SW.
Logical Max_Nb_Tcorr_Start B11 Yes B12 Yes
name TRX nb No
HMI Max_Nb_Tcorr_Start Sub-syste MFS Cell Type No
Definition Maximum number of consecutive times the timer Tcorr can be started for the same (ME)GCH link.
Spec ref. GPRS MFS-BTS interface - MEGCH stack Coded Max 3
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical MAX_PAGING_QUEUE B11 Yes B12 Yes
name TRX nb No
HMI MAX_PAGING_QUEUE Sub-syste MFS Cell Type No
Definition Maximum number of CS+PS paging messages stored in PMU.
Coding rules --
Mandatory rules --
Recommended Paging Rate = 100 paging/s AND Queueing Time = 5s

rules
External --
comment
Internal comment --
Logical MAX_PDCH (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH Sub-syste MFS Cell Type No
Definition Maximum number of slave and master PDCHs that can be allocated to the MFS in the cell.
Coding rules --
Mandatory rules Shall be equal to MAX_PDCH (MX BSC)

Max_PDCH >= MAX_PDCH_HIGH_LOAD;

MAX_PDCH shall be set so that at least one slave PDCH can be allocated to the MFS to serve DL or UL TBFs. This means that MAX_PDCH > NB_TS_MPDCH if
EN_GPRS = TRUE.
iii) MAX_PDCH <= NB_TS_MPDCH + 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX
case,
the following configuration is recommended: NB_TS_MPDCH = 1, MAX_PDCH = 2, MAX_PDCH_HIGH_LOAD = 1, MIN_PDCH = 1.
comment m
Internal comment 1) this parameter is available in the G2 BSC through the BSCGP interface template
2) the MPDCHs (primary and secondary) are also taken into account in this parameter.
3) The cell is not created into the MFS, if Max_PDCH = 0
4) The conditions to check the upper limit of MAX_PDCH are not fully optimized here. Indeed, ideally they should be performed taking into account the number of slave
Logical MAX_PDCH_HIGH_LOAD (MFS) B11 Yes B12 Yes

name TRX nb No
HMI MAX_PDCH_HIGH_LOAD Sub-syste MFS Cell Type No
Coding rules --
Mandatory rules Shall be equal to MAX_PDCH_HIGH_LOAD (MX BSC)

- MAX_PDCH >= MAX_PDCH_HIGH_LOAD
Recommended --
rules
comment
Internal comment 1) This parameter is available in the G2 BSC through the BSCGP interface
2) The MPDCHs (primary and secondary) are also taken into account in this parameter.
Logical MAX_PDCH_PER_TBF B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH_PER_TBF Sub-syste MFS Cell Type No
Definition Maximum number of PDCHs allocated to a single (E)GPRS connection.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_PDCH_PTU_GP2 B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH_PTU_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of PDCHs handled by a DSP (Mx-MFS)
Coding rules --
Mandatory rules --
Recommended --
rules
comment Applicable to GP2 board
Logical MAX_PDCH_PTU_GP3 B11 No B12 Yes
name TRX nb No
HMI MAX_PDCH_PTU_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of PDCHs handled by a PTU instance (Mx-MFS)
Coding rules --
Mandatory rules --
Recommended --
rules
Logical MAX_PDCH_PTU_IP_G3_G4 B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH_PTU_IP_G3_G4 Sub-syste MFS Cell Type No
Definition Maximum number of PDCHs handled by a PTU in IP mode (within a G3 or G4 TRE)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
Logical MAX_PDCH_PTU_IP_G5 B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH_PTU_IP_G5 Sub-syste MFS Cell Type No
Definition Maximum number of PDCHs handled by a PTU in IP mode (within a G5 TRE)
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_PDCH_PTU_IP_MC B11 Yes B12 Yes
name TRX nb No
HMI MAX_PDCH_PTU_IP_MC Sub-syste MFS Cell Type No
Definition Maximum number of PDCHs handled by a PTU in IP mode (within a MC module)
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_PFC_NUMBER_GP2 B11 Yes B12 Yes
name TRX nb No
HMI MAX_PFC_NUMBER_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of PFC per GP board (Mx-MFS)
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical MAX_PFC_NUMBER_GP3 B11 No B12 Yes
name TRX nb No
HMI MAX_PFC_NUMBER_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of PFC per GP board (Mx-MFS)
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical MAX_POW_RED_DYN B11 No B12 Yes
name TRX nb No
HMI MAX_POW_RED_DYN Sub-syste MFS Cell Type No
Definition Maximum power reduction relative to the POW_RED_P0 for Packet Service.
It represents the dynamic part of the packet downlink power control reduction, applicable to the TBFs in EGPRS mode.
Mandatory rules - BS_TXPWR_ATTENUATION + POW_RED_P0 + MAX_POW_RED_DYN <= 32
Recommended --
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled.
- The dynamic part of the packet downlink power control does not apply to DL TBF established for a MS in DTM mode.
- In case of TBF in RLC unacknowledged mode, MAX_POW_RED_DYN is considered as 0.
Internal comment - it is applicable to GMSK and 8PSK modulations used in EGPRS
Logical MAX_POW_RED_USF_8PSK B11 No B12 Yes
name TRX nb No
HMI MAX_POW_RED_USF_8PSK Sub-systeMFS Cell Type No
Definition Maximum packet downlink power reduction of a RLC/MAC radio block that carries an USF using 8PSK modulation.
Mandatory rules --
Recommended - MAX_POW_RED_USF_8PSK <= MAX_POW_RED_DYN for a better decoding of the USF by the MS.
rules
comment - Significant if EN_BS_PC_PS is enabled and MAX_POW_RED_DYN <> 0.
Internal comment --
Logical MAX_POW_RED_USF_GMSK B11 No B12 Yes
name TRX nb No
HMI MAX_POW_RED_USF_GMSK Sub-systeMFS Cell Type No
Definition Maximum packet downlink power reduction of a RLC/MAC radio block that carries an USF using GMSK modulation.
Mandatory rules --
Recommended - MAX_POW_RED_USF_GMSK <= MAX_POW_RED_DYN for a better decoding of the USF by the MS.
rules
Internal comment --
Logical Max_PPCH_DRX_Occurrences B11 Yes B12 Yes
name TRX nb No
HMI Max_PPCH_DRX_Occurrences Sub-syste MFS Cell Type No
Definition Maximum number of paging occurrences tested for the sending of a paging or a Packet Downlink Assignment when the addressed MS is in DRX mode.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Max_PPCH_Non_DRX_Lifetime B11 Yes B12 Yes
name TRX nb No
HMI Max_PPCH_Non_DRX_Lifetime Sub-syste MFS Cell Type No
Definition Time limit for the sending of a paging or a Packet Downlink Assignment when the addressed MS is in non DRX mode.
Coding rules step size: 100 ms
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_PPCH_QUEUING_DELAY B11 Yes B12 Yes
name TRX nb No
HMI MAX_PPCH_QUEUING_DELAY Sub-syste MFS Cell Type No
Definition PPCH queuing time.
Mandatory rules --
Recommended --
rules
External Used to evaluate the MS DRX mode
comment
Internal comment --
Logical MAX_RADIUS_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI MAX_RADIUS_FACTOR Sub-syste MFS Cell Type No
Definition Factor used in the computation of the maximum radius of the ellipsoid arc returned by the MFS when computing location estimate based on TA positionning method.
Rec ref. None Domai LCS Min value 0.5 Coded Min 10
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Max_Rate_Safety B11 Yes B12 Yes
name TRX nb No
HMI Max_Rate_Safety Sub-syste
MFS Cell Type No
name Instance
MFS RMS No
Definition Safety factor to compensate the Max_Rate_PDCH in the calculation of BVC_Bucket_Size and MS_Bucket_Size, for downlink flow control, on Gb interface.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment In case of perfect radio condition and there is only one MS on each allocated PDCH, this parameter is used to artificially decrease the radio efficiency in order to avoid
the underflow situation of BVC buffer and MS buffer.
Logical Max_Resel_Duration B11 Yes B12 Yes
name TRX nb No
HMI Max_Resel_Duration Sub-syste MFS Cell Type No
Definition Defines targeted maximum duration of a cell reselection. Corresponds to the scheduling period of Low Rate PSI messages.
0: Low Rate PSI period = High Rate PSI period
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Max_retrans (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MAX_RETRANS Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Maximum number of CHANNEL REQUEST retransmissions by the MS on the RACH, broadcast on the PBCCH for CS service establishment.
Coding rules Possible values are:1, 2 ,4 and 7 respectively binary coded:00, 01, 10 and 11
Mandatory rules Max_retrans (BSC) = Max_retrans (MFS) for a given cell
Recommended --
rules
comment
Logical MAX_RETRANS_1 B11 Yes B12 Yes
name TRX nb No
HMI MAX_RETRANS_1 Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Maximum number of PACKET CHANNEL REQUEST retransmissions by the MS on the PRACH with priority level 1.
Coding rules Possible values are : 1, 2, 4, 7 respectively binary coded : 00, 01, 10, 11
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
MFS Cell Type No
name Instance
cell RMS No
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
MFS Cell Type No
name Instance
cell RMS No
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
MFS Cell Type No
name Instance
cell RMS No
Mandatory rules --
Recommended --
rules
External --
comment
Logical Max_retrans_DL B11 Yes B12 Yes
name TRX nb No
HMI Max_retrans_DL Sub-syste MFS Cell Type No
Definition Maximum number of DL TBF establishment retries
(max_Retrans_Dl is decremented each time the DL TBF establishment procedure is started from the beginning).
Coding rules Possible values: 0 to 7.
Mandatory rules --
Recommended N3103_Limit: maximum number of retransmissions to release an UL TBF

rules Max_Retrans_DL:maximum number of retransmissions to establish a DL TBF
In case of simultaneous UL TBF Release and DL TBF establishment with loss of the Packet Control Ack which acknowledges the final Packet UL Ack/Nack, the UL TBF
has to be released, at least before the last attempt to establish the DL TBF, in order to avoid the emission of a Radio Status.
Consequently the following rule has to be followed:
(N3103_Limit + 1) x (RTD + 60) < Max_Retrans_DL x (RTD + 60)
N3103_Limit + 1:total number of attempts to send the final Packet UL Ack/Nack
RTD: Round Trip Delay
60 (msec): for the Packet UL Ack/Nack acknowledgement: RRBP + 3 is used
Max_Retrans_DL:total number of attempts minus one to send the Packet DL Assignment
60 (msec): for the Packet DL Assignment acknowledgement: RRBP + 3 is used
--> Max_Retrans_DL > (N3103_Limit + 1) x (RTD + 60) / (RTD + 60)
--> Max_Retrans_DL > (N3103_Limit + 1)
External --
comment
Internal comment --
Logical MAX_RETRANS_PAGING_EXT B11 Yes B12 Yes
name TRX nb No
HMI MAX_RETRANS_PAGING_EXT Sub-syste MFS Cell Type No
Definition Maximum number of Paging Request sent to the MS in an extended cell. This parameter
is used only when the MS didnt answer to any Packet DL Assignment message.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The first Paging request sending is counted in the parameter value.
0 means no Paging Request.
Logical MAX_Retrans_SIG B11 Yes B12 Yes
name TRX nb No
HMI MAX_Retrans_SIG Sub-syste MFS Cell Type No
Definition Maximum number of retransmissions of a Packet TBF Release message, of a Packet Measurement Order message with a 3G search deactivation command, or of a
Packet Cell Change Order message following a non-reception of the Packet Control Acknowledgement message. This parameter is also used to define the maximum
number of retransmissions of a Packet Measurement Order message with a NC2 activation command following the non-reception of a Packet Measurement Report
message.
Coding rules step size: 1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MAX_RLC_blks_PTU_G3_IP B11 Yes B12 Yes
name TRX nb No
HMI MAX_RLC_blks_PTU_G3_IP Sub-syste MFS Cell Type No
Definition Maximum number of RLC/MAC data blocks stocked in PTU for a G3 BTS in IP mode, used for all coding schemes.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PTU SW.
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_RLC_BLKS_PTU_GP2 B11 Yes B12 Yes
name TRX nb No
HMI MAX_RLC_BLKS_PTU_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of RLC/MAC data blocks stocked in a DSP, used for all coding schemes.
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW.
Logical MAX_RLC_BLKS_PTU_GP3 B11 No B12 Yes
name TRX nb No
HMI MAX_RLC_BLKS_PTU_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of RLC/MAC data blocks stocked in a PTU instance, used for all coding schemes.
Coding rules --
Mandatory rules --
Recommended --
rules
Logical MAX_RLC_blks_PTU_MC_IP B11 Yes B12 Yes
name TRX nb No
HMI MAX_RLC_blks_PTU_MC_IP Sub-syste MFS Cell Type No
Definition Maximum number of RLC/MAC data blocks stocked in PTU for a MC module in IP mode, used for all coding schemes.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Its value corresponds to 4 x MAX_RLC_blks_PTU_G4_IP (4 x to consider 4 PS-loaded TRXs per MC module, so per PTU in IP mode).
Logical MAX_TBF_CELL_DL B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_CELL_DL Sub-syste MFS Cell Type No
Definition Maximum number of DL TBFs which can be simultaneously established in a cell.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU SW
Logical MAX_TBF_CELL_UL B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_CELL_UL Sub-syste MFS Cell Type No
Definition Maximum number of UL TBFs which can be simultaneously established in a cell.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU SW.
Logical MAX_TBF_PTU_G3_IP B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_PTU_G3_IP Sub-syste MFS Cell Type No
Definition Maximum number of DL + UL TBFs handled by a G3 PTU in an IP BTS
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PTU SW. It gives the maximum number of TBF for both directions which can be simultaneously
established in the PTU in a G3 BTS.
name TRX nb No
Definition Maximum number of DL + UL TBFs handled by a G4 PTU in an IP BTS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
Definition Maximum number of DL + UL TBFs handled by a G5 PTU in an IP BTS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_TBF_PTU_GP2 B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_PTU_GP2 Sub-syste MFS Cell Type No
Definition Maximum number of (E)GPRS connections handled by a DSP (Mx-MFS)
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW. It gives the maximum number of TBF for both directions which can be simultaneously
established in the DSP.
Logical MAX_TBF_PTU_GP3 B11 No B12 Yes
name TRX nb No
HMI MAX_TBF_PTU_GP3 Sub-syste MFS Cell Type No
Definition Maximum number of (E)GPRS connections handled by a PTU instance (Mx-MFS)
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW. It gives the maximum number of TBF for both directions which can be simultaneously
established in the PTU instance.
Logical MAX_TBF_PTU_MC_IP B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_PTU_MC_IP Sub-syste MFS Cell Type No
Definition Maximum number of DL + UL TBFs handled by the PTU of a MC module in an IP BTS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
established in the PTU of a MC module.
The value 336 comes from 6 x MAX_TBF_PTU_G4_IP, as there can be up to 6 TRXs per MC module.
Logical MAX_TBF_TRX_DL_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_TRX_DL_GP Sub-syste MFS Cell Type No
Definition Maximum number of (E)GPRS DL TBFs which can be simultaneously established on a TRX (in case of Mx-MFS).
Mandatory rules --
Recommended --
rules
comment
Internal comment This parameter fixes the maximum number of (E)GPRS DL TBFs which can be simultaneously established on a TRX regardless, in TDM mode, of the number of GCHs
in the M-EGCH link of this TRX. Other parameters exist to limit the number of TBFs in function of the number of GCHs (cf. RRM-PRH).
Within PTU SW, a limit of 80 is hardcoded (corresponding to the maximum value of this parameter).
Logical MAX_TBF_TRX_UL_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_TBF_TRX_UL_GP Sub-syste MFS Cell Type No
Definition Maximum number of (E)GPRS UL TBFs which can be simultaneously established on a TRX (in case of Mx-MFS).
Mandatory rules --
Recommended --
rules
comment
Internal comment This parameter fixes the maximum number of (E)GPRS UL TBFs which can be simultaneously established on a TRX regardless, in TDM mode, of the number of GCHs
in the M-EGCH link of this TRX. Other parameters exist to limit the number of TBFs in function of the number of GCHs (cf. RRM-PRH).
Within PTU SW, a limit of 48 is hardcoded (corresponding to the maximum value of this parameter).
Logical MAX_TRX_DSP_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_TRX_DSP_GP Sub-syste MFS Cell Type No
Definition Maximum number of TRX handled by a DSP (Mx-MFS).
Coding rules --
Mandatory rules --
Recommended --
rules
comment Applicable to GP2 and GP3 boards
Logical MAX_TRX_GP B11 Yes B12 Yes
name TRX nb No
HMI MAX_TRX_GP Sub-syste MFS Cell Type No
Definition Maximum number of TRX configured supported by GP board (Mx-MFS)
Coding rules --
Mandatory rules MAX_TRX_GP <= MAX_CTXT_TRX_GP
Recommended --
rules
comment
Internal comment --
Logical MAX_TRX_PTU_IP_G3_G4 B11 Yes B12 Yes
name TRX nb No
HMI MAX_TRX_PTU_IP_G3_G4 Sub-syste MFS Cell Type No
Definition Maximum number of TRX handled by a PTU in IP (within a G3 or a G4 TRE).
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_TRX_PTU_IP_G5 B11 Yes B12 Yes
name TRX nb No
HMI MAX_TRX_PTU_IP_G5 Sub-syste MFS Cell Type No
Definition Maximum number of TRX handled by a PTU in IP (within a G5 TRE).
Coding rules 1 : for G5 TRE configured as High Power; 2 : for G5 TRE configured as Twin
Mandatory rules --
Recommended --
rules
External --
comment
Logical MAX_TRX_PTU_IP_MC B11 Yes B12 Yes
name TRX nb No
HMI MAX_TRX_PTU_IP_MC Sub-syste MFS Cell Type No
Definition Maximum number of TRXs handled by the PTU of a MC module in IP mode.
Coding rules --
Mandatory rules - MC_MODULE_NB_TRE (BTS parameter in BOP) <= MAX_TRX_PTU_IP_MC.
Recommended --
rules
External --
comment
Logical MAX_UL_TBF_SPDCH B11 Yes B12 Yes
name TRX nb No
HMI MAX_UL_TBF_SPDCH Sub-syste MFS Cell Type No
Definition Indicative value of maximum number of UpLink (E)GPRS TBFs per slave PDCH.
Coding rules --
Mandatory rules --
Recommended --
rules
External When allocating an UL GPRS TBF: MAX_UL_TBF_SPDCH is the maximum number of GPRS + EGPRS TBFs allowed in UL on each Slave PDCH.
comment When allocating an UL EGPRS TBF: MAX_UL_TBF_SPDCH is the maximum number of EGPRS TBFs allowed in UL on each Slave PDCH (regardless of the current
number of UL GPRS TBFs).
Internal comment Within PTU SW, a limit is hardcoded corresponding to the maximum number of UL (E)GPRS TBF resources which can be possibly reached per Slave PDCH (taking into
account TBF allocations and a margin for TBF reallocations). This hardcoded value is set to 7 (cf. MAC specification)
Logical Maximum_Credit B11 Yes B12 Yes
name TRX nb No
HMI Maximum_Credit Sub-syste MFS Cell Type No
Definition When a TBF credit reaches this maximum value, then the TBF can still be scheduled but its credit is no more increased.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This constant is hardcoded in MAC.
Logical Maximum_Weight B11 Yes B12 Yes
name TRX nb No
HMI Maximum_Weight Sub-syste MFS Cell Type No
Definition When a TBF weight reaches this maximum value, then the TBF can still be scheduled but its weight is no more increased.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This constant is hardcoded in MAC
Logical MCC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Country Code (MCC) Sub-syste MFS Cell Type No
Definition Mobile Country Code of the own PLMN.
- MCC (BSC) = MCC (MFS).
Recommended --
rules
External The value depends on the configuration. The default value indicated here is for implementation purposes.
comment
Internal comment The value sent by the OMC-R corresponds to the value of a OwnMCC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom catalogue document. The
OwnMCC[x] parameter defines a MCC of the own PLMN set.
Logical MCC(n) (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Country Code (MCC) Sub-syste MFS Cell Type No
Definition Mobile Country Code of the own or of a foreign PLMN.
- MCC(n) (BSC) = MCC(n) (MFS)
own PLMN).
Recommended --
rules
External --
comment
Internal comment --
Logical MCS_ADAPTATION_SET_SELECTION B11 No B12 Yes
name TRX nb No
HMI MCS_ADAPTATION_SET_SELECTION Sub-syste MFS Cell Type No
Definition Defines the set number of link adaptation table to be used for EGPRS link adaptation in RLC acknowledged mode.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Significant if EN_MCS_ADAPTATION_CONFIGURATION is enabled.
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the TBF established.
Logical MCS_AVG_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI MCS_AVG_PERIOD Sub-syste MFS Cell Type No
Definition Filtering period used for calculation of the forgetting factor applied to the current UL MEAN_BEP and CV_BEP samples in the averaging Modulation and Coding Scheme
adaptation filter
Category Site (CAE) OMC-R access Changeable Type Reference Unit sec
Rec ref. None Domai E-GPRS Min value 0.02 Coded Min 1
Mandatory rules --
Recommended --
rules
Internal comment see also MCS_AVG_PERIOD_DEF_VALUE (MCS_AVG_PERIOD is assumed rarely modified on the fields)
Logical MCS_AVG_PERIOD_DEF_VALUE B11 Yes B12 Yes
name TRX nb No
HMI MCS_AVG_PERIOD_DEF_VALUE Sub-syste MFS Cell Type No
Definition Default value of the filtering period used for calculation of the forgetting factor applied to the current UL MEAN_BEP and CV_BEP samples in the averaging Modulation and
Coding Scheme adaptation filter.
Category System (CST) OMC-R access None (not in DLS) Type Reference Unit sec
Mandatory rules shall be equal to the default value of MCS_AVG_PERIOD
Recommended --
rules
External --
comment
Logical MIN_PDCH (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MIN_PDCH Sub-syste MFS Cell Type No
Coding rules --
Mandatory rules - Shall be equal to MIN_PDCH (MX BSC)

-MAX_PDCH_HIGH_LOAD >= MIN_PDCH;
-MIN_PDCH > NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = enabled;
-MIN_PDCH >= NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = disabled.
comment
- This parameter is available in the G2 BSC through the BSCGP interface
Logical MIN_RADIUS_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI MIN_RADIUS_FACTOR Sub-syste MFS Cell Type No
Definition Factor used in the computation of the minimum radius of the ellipsoid arc returned by the MFS when computing location estimate based on TA positionning method.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MIN_RLF_TIME_DL B11 Yes B12 Yes
name TRX nb No
HMI MIN_RLF_TIME_DL Sub-syste MFS Cell Type No
Definition Minimum time before detecting a radio link failure of a DL TBF, triggered by N3105 or NstagnatingWindowDL.
Mandatory rules --
Recommended It is recommended to set a value close to the time of temporary very bad radio conditions that the operator would like to support during a DL TBF. Typically, a few
rules seconds.
External --
comment
Internal comment The main goal of this mechanism is to avoid spurious abnormal DL TBF releases due to temporary bad radio conditions, e.g. fading holes for slow channel profiles
without frequency hopping or shadowing effects for fast.
Logical MIN_THROUGHPUT_GAIN B11 Yes B12 Yes
name TRX nb No
HMI MIN_THROUGHPUT_GAIN Sub-systeMFS Cell Type No
Definition Minimum throughput gain required to be provided to the MS when performing a T2 or T3 TBF reallocation.
Rec ref. None Domai E-GPRS Min value 0.1 Coded Min 1
Mandatory rules --
Recommended --
rules
External Increasing the value of this parameter above 0,3 might block some reallocations for mobiles having a high multislot class (multislot class >= 30).
comment
Internal comment --
Logical Minimum_Credit_Weight B11 Yes B12 Yes
name TRX nb No
HMI Minimum_Credit_Weight Sub-syste MFS Cell Type No
Definition When a TBF credit or weight reaches this minimum value, then the TBF can still be scheduled (in the extra scheduling phase) but its credit/weight is no more decreased.
This value can be negative.

This value applies to both RT and NRT TBFs.
Rec ref. None Domai GPRS Min value -10 Coded Min -10
n Max value -10 Coded Max -10
Spec ref. GPRS radio interface - MAC sublayer Coded Max -10
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This constant is hardcoded in MAC
Logical MNC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Network Code (MNC) Sub-syste MFS Cell Type No
Definition Mobile Network Code of the own PLMN.
- MNC (BSC) = MNC (MFS).
Recommended --
rules
comment The operator is allowed to enter 2 or 3 digits MNC.
Internal comment The value sent by the OMC-R corresponds to the value of a OwnMNC[x] parameter (where x = 1, 2, 3 or 4) defined in the BSS O&M Telecom catalogue document. The
OwnMNC[x] parameter defines a MNC of the own PLMN set.
Logical MNC(n) (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Mobile Network Code (MNC) Sub-syste MFS Cell Type No
Definition Mobile Network Code of the own or of a foreign PLMN.
- MNC(n) (BSC) = MNC(n) (MFS)
own PLMN).
Recommended --
rules
External --
comment
Internal comment --
Logical MPDCH_LOAD_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI MPDCH_LOAD_PERIOD Sub-syste MFS Cell Type No
Definition Duration of the sliding window, used to estimate the average load on MPDCH channels.
Coding rules --
Mandatory rules --
Recommended MPDCH_LOAD_PERIOD and NB_MPDCH_LOAD_SAMPLE are used to determine signalling load samples period (Sig_Load_Period = MPDCH_LOAD_PERIOD /
rules NB_MPDCH_LOAD_SAMPLE)
For example, default values, give the following Sig_Load_Period: 30 / 6 = 5s.
External --
comment
Internal comment Needed for MPDCH load counters.
Logical MS_BASED_AGPS_ASSIST_DATA_LIST B11 Yes B12 Yes
name TRX nb No
HMI MS_BASED_AGPS_ASSIST_DATA_LIST Sub-syste
MFS Cell Type No
name InstanceMFS RMS No
Definition Bitmap (8 bits) defining the types of optional assistance data to be retrieved from the A-GPS server when using the MS based A-GPS positioning method. The following
optional assistance data type are considered: Almanac, UTC model, DGPS corrections, reference time, acquisition assistance, real-time integrity.
Category Network (CDE) OMC-R access None (DLS) Type Reference Unit None
Coding rules bit 8 (most significant) and bit 7 are not used (i.e. always set to 0); bit 6=1: real-time integrity is retrieived; bit 5=1: acquisition assistance is retrieived; bit 4=1: reference
time is retrieived; bit 3=1: DGPS corrections is retrieived; bit 2=1: UTC model is retrieived; bit 1 (least significant)=1: Almanac is retrieived.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical MS_TIME_TO_SWITCH_TO_NEW_PDCH B11 Yes B12 Yes
name TRX nb No
HMI MS_TIME_TO_SWITCH_TO_NEW_PDCH Sub-syste MFS Cell Type No
Definition Time that a Mobile Station is expected to need for switching to the assigned PDCHs after acknowledging a (re)assignment message (PACKET DOWNLINK ASSIGNMENT,
PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE).
Mandatory rules --
Recommended --
rules
External The 3GPP standard mandates the MS to switch to the new resources in 40 msec but some MSs may take longer.
comment
Internal comment --
Logical MS_TXPWR_MAX_CCH (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX_CCH Sub-syste MFS Cell Type No
Mandatory rules --
Recommended --
rules
Internal comment 1)This parameter is needed when a PBCCH is established in the serving cell.
Logical MS_TXPWR_MAX_CCH(n)(MFS) B11 Yes B12 Yes
name TRX nb No
HMI MS_TXPWR_MAX_CCH Sub-syste MFS Cell Type No
Mandatory rules --
Recommended --
rules
Internal comment 1)This parameter is needed when a PBCCH is established in the serving cell
Logical MSCR (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MSCR Sub-systeMFS Cell Type No
Recommended --
rules
comment
Logical MULTIBAND_REPORTING (MFS) B11 Yes B12 Yes
name TRX nb No
HMI MULTIBAND_REPORTING Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Minimum number of cells of each supported frequency band to be included in MEASUREMENT REPORT by the MS.
00: normal reporting of the six strongest cells, with known and allowed NCC part of BSIC, irrespective of the band used;
01: the MS shall report the strongest cell, with known and allowed NCC part of BSIC, in each of the frequency bands in the BA list, excluding the frequency band of
the serving cell;
10: the MS shall report the two strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the BA list, excluding the frequency band
of the serving cell;
11: the MS shall report the three strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the BA list, excluding the frequency
band of the serving cell.
Mandatory rules Equal to MULTIBAND_REPORTING (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical N_ATER_TS_MARGIN_GPU B11 Yes B12 Yes
name TRX nb No
HMI N_ATER_TS_MARGIN_GPU Sub-syste MFS Cell Type No
Definition Number of free 64k Ater TSs that are kept in reserve in order to be able to serve some prioritary requests in cells managed by the GP(U). The prioritary requests are the
GCH establishment requests launched when the first TBF has to be established in a cell (useful to guarantee that MM traffic will be supported in any cell at any time).
In case N_ATER_TS_MARGIN_GPU = 0, then no Ater margin is managed.

In case N_ATER_TS_MARGIN_GPU > 0, RRM will ensure that N_ATER_TS_MARGIN_GPU 64k Ater TSs are always free (i.e. not used by a GCH in the GP(U)). From then
on, only prioritary requests will be allowed to establish some GCHs with those Ater resources.
Coding rules --
Mandatory rules --
Recommended --
rules
comment - Increasing the value of N_ATER_TS_MARGIN_GPU will make the average number of unused Ater nibbles in the GP(U) increase. That corresponds to a loss of Ater
resources on the field, as the on-going TBF traffic will never benefit from the margin of Ater resources. But, on the other hand, the likelihood of not serving a
prioritary request in the GP(U) will be become very low.
- Decreasing the value of N_ATER_TS_MARGIN_GPU (to a non null value) will make it possible that prioritary requests cannot be served in case several such
requests have to be served in a short period of time (i.e. before having had the time to fill the Ater margin up again), especially if the requests have to be served on
several different DSPs (one 64k Ater TS will be consumed by each DSP).
- Setting N_ATER_TS_MARGIN_GPU to 0 will make it possible the cases where prioritary requests cannot be served at all.
Internal comment Applicable to GPU and GP2 and GP3 boards
Logical N_AVG_I (MFS) B11 Yes B12 Yes
name TRX nb No
HMI N_AVG_I (MFS) Sub-systeMFS Cell Type No
Definition N_AVG_I (MFS) value is broadcast to the (E)GPRS MS in the PSI 13 and PSI1. The (E)GPRS MS uses it for filtering the interference signal level measurements that it shall
perform during the packet transfer mode. These measurements are used by the (E)GPRS MS for output power control, but also reported to the network and used for
performing downlink link adaptation.
Mandatory rules Equal to N_AVG_I (BSC)
Recommended --
rules
External --
comment
Internal comment The Default value 6 has been used by the simulations performed by R&I, see report UTR/C/03/0011/V1 for detail.
Logical N_BIAS_DETERMINATION B11 Yes B12 Yes
name TRX nb No
HMI N_BIAS_DETERMINATION Sub-syste MFS Cell Type No
Definition Number of kbytes which must be transferred on a TBF before the bias of the on-going user application is determined.
Category System (CST) OMC-R access None (DLS) Type Number Unit kbyte
Coding rules step size = 1 kbyte
Mandatory rules --
Recommended --
rules
External This parameter is used to tune the algorithm, which assesses the bias of the on-going application for a given MS. Each time N_BIAS_DETERMINATION bytes have
comment been transferred in one direction or the other, the PCU compares the number of bytes transferred in both directions; the direction in which more bytes have been
transferred gives the bias of the on-going transfer. The resource reallocation algorithm attempts to offer the best possible throughput in the direction of the bias
depending on the available resources.
The value 0 disables the function (the bias of the on-going application is never assessed and therefore the application is always deemed downlink biased, except in
case the MS context is created upon an UL 2 phase access in which case the bias is uplink).
Internal comment --
Logical N_CANDIDATE_FOR_REALLOC B11 Yes B12 Yes
name TRX nb No
HMI N_CANDIDATE_FOR_REALLOC Sub-syste
MFS Cell Type No
name Instance
MFS RMS No
Definition Number of bytes which must be transferred on a TBF before the corresponding MS becomes candidate for resource reallocation.
Coding rules Step size = 100 bytes
Mandatory rules --
Recommended --
rules
External This parameter shall be big enough to avoid reallocating the resources of MSs that are used only to transfer signalling LLC PDUs or very short transfers. On the other
comment hand, it shall not delay unnecessarily the reallocation for other kinds of traffic. When the parameter is set to 0, an MS with a TBF in the direction of the bias shall
become candidate for resource reallocation as soon as the TBF is established.
Internal comment --
Logical N_DATA_BYTES_MAX_TRANS B11 Yes B12 Yes
name TRX nb No
HMI N_DATA_BYTES_MAX_TRANS Sub-syste MFS Cell Type No
Definition Number of bytes below which an MS transfer is considered to be short data.
Coding rules step size = 1 byte
Mandatory rules --
Recommended N_DATA_BYTES_MAX_TRANS <= N_DATA_BYTES_MAX_TRANS_PERIODIC

rules
comment - An MS transfer is considered to be short data as long as less than N_DATA_BYTES_MAX_TRANS bytes have been transferred in both directions (since the TBF
establishment(s)). Else, if more than N_DATA_BYTES_MAX_TRANS bytes have been transferred in at least one direction, the MS transfer is considered to be long
data.
Note: in DL, the bytes of the DL LLC PDUs currently queued for the MS (but not yet sent to the MS) are also counted.
Decreasing (respectively increasing) the value of N_DATA_BYTES_MAX_TRANS will tend:
- to make the Ater resource optimization worse (respectively better) when the Ater usage of the GPU is above Ater_Usage_Threshold_Short_Data,
- to reduce (respectively make higher) the PS throughput degradations at the beginning of MS traffics when the Ater usage of the GPU is above
Ater_Usage_Threshold_Short_Data,
- to make the MFS and BSC CPU loads higher (respectively lower).
- Parameter change: No impact on the telecom service, on going TBF are not disrupted. Change applied immediately on current TBF and on new TBF, established after
modification.
Internal comment --
Logical N_DATA_BYTES_MAX_TRANS_PERIODIC B11 Yes B12 Yes
name TRX nb No
HMI N_DATA_BYTES_MAX_TRANS_PERIODIC Sub-syste MFS Cell Type No
Definition Number of bytes above which a transition from short data to long data MS transfer shall be periodically reattempted (only useful in the rare cases where such a
transition previously failed).
Category Network (CDE) OMC-R access None (DLS) Type Number Unit byte
Coding rules step size = 100 bytes
Mandatory rules --
Recommended N_DATA_BYTES_MAX_TRANS <= N_DATA_BYTES_MAX_TRANS_PERIODIC

rules
comment - A transition from short data to long data MS transfer can only fail in the rare cases where there is a too high number of TBFs on the TRX / in some very specific
reallocation failure scenarios.
A low value of N_DATA_BYTES_MAX_TRANS_PERIODIC should be avoided because it will tend to increase the CPU load of the MFS for a defence case which
should be rare (if TRX and Abis/Ater transmission resources are properly dimensioned).
Internal comment --
Logical N_GCH_FAST_PS_ACCESS B11 Yes B12 Yes
name TRX nb No
HMI N_GCH_FAST_PS_ACCESS Sub-syste MFS Cell Type No
Definition Two definitions are possible :
- If EN_FAST_INITIAL_GPRS_ACCESS = enabled : number of GCHs required to be established due to the Fast Initial PS Access feature,
- If EN_FAST_INITIAL_GPRS_ACCESS = "disabled : number of GCHs to keep established when there is no more (E)GPRS traffic in a cell (while the
T_GCH_INACTIVITY_LAST timer is running). Those GCHs will be useful in case of (E)GPRS traffic resumption in the cell.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 B11 Yes B12 Yes
name TRX nb No
HMI N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 Sub-syste MFS Cell Type No
Definition Defines the total number of (unsuccessful) T3 radio resource reallocation attempts that are allowed to be performed upon expiry of the T_CANDIDATE_TBF_REALLOC
timer. As soon as N_MAX_PERIODIC_REALLOC_SUCCESS_T3 T3 radio resource reallocation attempts succeed, no other attempt is performed (even if less than
N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 attempts have been performed so far).
The UL-biased MSs and the DL-biased MSs are considered regardless of each other.
As a result, in a given cell, up to 2 x N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 T3 radio resource reallocation attempts will be performed upon expiry of the timer.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter, with the parameters T_CANDIDATE_TBF_REALLOCREALLOC and N_MAX_PERIODIC_REALLOC_SUCCESS_T3, allows to :
- control the reactivity of the BSS with regards to T3 reallocations
- and to control the extra CPU load generated by the T3 reallocation attempts (the highest the value of N_MAX_PERIODIC_REALLOC_ATTEMPT_T3, the highest the
generated CPU load).
Logical N_MAX_PERIODIC_REALLOC_ATTEMPT_T4 B11 Yes B12 Yes
name TRX nb No
HMI N_MAX_PERIODIC_REALLOC_ATTEMPT_T4 Sub-syste MFS Cell Type No
Definition Defines the total number of T4 radio resource reallocation attempts (successful or not) that are performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter, with the parameter T_CANDIDATE_TBF_REALLOC, allows to :
- control the reactivity of the BSS with regards to T4 reallocations
- and to control the extra CPU load generated by the T4 reallocation attempts (the highest the value of N_MAX_PERIODIC_REALLOC_T4, the highest the generated CPU
load).
Logical N_MAX_PERIODIC_REALLOC_SUCCESS_T3 B11 Yes B12 Yes
name TRX nb No
HMI N_MAX_PERIODIC_REALLOC_SUCCESS_T3 Sub-syste MFS Cell Type No
Definition Maximum number of successful T3 radio resource reallocation attempts that can be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer.
Coding rules --
Mandatory rules N_MAX_PERIODIC_REALLOC_SUCCESS_T3 <= N_MAX_PERIODIC_REALLOC_ATTEMPT_T3
Recommended --
rules
External The maximum number of successful T3 radio resource reallocation attempts that can be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer is limited
comment by the Round Trip Delay.
Internal comment -This parameter is linked to the N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 parameter.
-A default value of 1 leads to B9 behaviour.
-A default value of 2 allows performing more rapidly the non-muliplexed-EDA strategy in some scenarios.
Logical N_PDCH_Release B11 Yes B12 Yes
name TRX nb No
HMI N_PDCH_Release Sub-syste MFS Cell Type No
Definition Number of repetitions of a Packet PDCH Release message.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_POLLING_EUTM_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI N_POLLING_EUTM_LIMIT Sub-syste MFS Cell Type No
Definition Maximum number of consecutive polling requests that can be sent to a MS in EUTM state (when EN_EXTENDED_UL_TBF is set ot 2 (IEUTM enabled)) without receiving a
polling response in a PCA.
Mandatory rules --
Recommended The value of the parameter should be set to a value high enough to avoid any spurious abnormal UL TBF releases.
rules
External A change of parameter value is taken into account also for on-going UL TBFs.
comment
Internal comment --
Logical N_RIM_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI N_RIM_RETRIES Sub-syste MFS Cell Type No
Definition Number of times a RAN procedure is retried (after first attempt) before giving up (in case of no answer is received)
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_SIG_REPEAT B11 Yes B12 Yes
name TRX nb No
HMI N_SIG_REPEAT Sub-syste MFS Cell Type No
Definition Number of repetitions of Packet Measurement Order messages with a Reset command, of Packet Uplink Assignment messages, or of Packet Power Control Timing
Advance messages. These repetitions are handled by the MAC layer.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_stagnating_Window_DL_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI NstagnatingWindowDL_LIMIT Sub-syste MFS Cell Type No
Definition This parameter defines the maximum number of consecutive Packet Downlink ACK/NACK or EGPRS Packet Downlink ACK/NACK messages reporting the failure of
progress of the RLC window during the active phase of a downlink TBF, before triggering an abnormal release of the DL TBF. This parameter is used in conjunction with
the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_stagnating_Window_UL_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI NstagnatingWindowUL_LIMIT Sub-syste MFS Cell Type No
Definition NstagnatingWindow limit above which a mono-slot uplink TBF alone on its PDCH shall be released: the counter is incremented each time a Packet UL Ack/Nack fails in
making the RLC window progress. For a multi-slot TBF or a TBF which shares its PDCH, the limit is proportional to the allocated bandwidth at the TBF establishment.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical N_UL_BIAS_FOR_EDA B11 Yes B12 Yes
name TRX nb No
HMI N_UL_BIAS_FOR_EDA Sub-syste MFS Cell Type No
Definition Minimum number of consecutive significantly-uplink biases observed during a transfer to allow a mobile station to use Extended Dynamic Allocation.
Coding rules --
Mandatory rules --
Recommended --
rules
External This parameter can allow using EDA only in case of big UL transfers
comment
Internal comment A significantly-uplink bias is a bias with a traffic ratio superior to the BIAS_LIMIT_EDA parameter.
Logical N_UL_Dummy_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI N_UL_Dummy_LIMIT Sub-syste MFS Cell Type No
Definition N_UL_Dummy threshold limit above which a uplink TBF shall be released: the counter is incremented each time the BSS receives a dummy block.
Coding rules --
Mandatory rules --
Recommended N_ul_dummy_limit > round trip delay / 20ms

rules
External For a multislot TBF, the actual limit is value * n_allocated_TS
comment
Internal comment --
Logical N_UL_Errors_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI N_UL_Errors_LIMIT Sub-syste MFS Cell Type No
Definition Number of received erroneous UL RLC blocks above which the uplink TBF is released by the BSS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The counter N_UL_Errors is incremented each time the RLC layer receives an erroneous UL RLC block (for instance when an UL RLC block is received with a wrong
UL TFI).
Logical N200_GSL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI N200_GSL (MFS) Sub-syste MFS Cell Type No
Definition Maximum number of re-transmissions on a GSL link.
Coding rules --
Mandatory rules Equal to N200_GSL (BSC)
Recommended T_GSL_Ack (BSC) > T200 (GSL) * (1 + N200 (GSL))

rules
External --
comment
Internal comment --
Logical N201_GSL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI N201_GSL (MFS) Sub-syste MFS Cell Type No
Definition Maximum number of bytes in Information part of an I frame sent by the BSC on the GSL link.
Coding rules --
Mandatory rules Equal to N201_GSL (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical N3101_LIMIT B11 Yes B12 Yes
name TRX nb No
HMI N3101_LIMIT Sub-syste MFS Cell Type No
Definition In an UL TBF tranfer procedure, maximum of consecutive times (before releasing abnormally the UL TBF) when the network receives no valid UL RLC data block or
nothing from the MS on its allocated PDCH.
To note that the counter N3101 can be incremented more than one time per block period.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition In an UL TBF releasing procedure, maximum of consecutive times (before releasing abnormally the UL TBF) when the network does not receive a Packet Control
Acknowledgement from the MS in response of its Packet UL ACK/NACK which specifies the end of the TBF.
Coding rules --
Mandatory rules --
Recommended N3103_Limit: maximum number of retransmissions to release an UL TBF

rules Max_Retrans_DL: maximum number of retransmissions to establish a DL TBF
In case of simultaneous UL TBF Release and DL TBF establishment with loss of the Packet Control Ack which acknowledges the final Packet UL Ack/Nack, the UL TBF
has to be released, at least before the last attempt to establish the DL TBF, in order to avoid the emission of a Radio Status.
Consequently the following rule has to be followed:
(N3103_Limit + 1) x (RTD + 60) < Max_Retrans_DL x (RTD + 60)
N3103_Limit + 1: total number of attempts to send the final Packet UL Ack/Nack
RTD: Round Trip Delay
60 (msec): for the Packet UL Ack/Nack acknowledgement: RRBP + 3 is used
Max_Retrans_DL: total number of attempts minus one to send the Packet DL Assignment
60 (msec): for the Packet DL Assignment acknowledgement: RRBP + 3 is used
N3103_Limit < (Max_Retrans_DL x (RTD + 60) / (RTD + 60)) - 1
N3103_Limit < [Max_Retrans_DL] - 1
Example:
With Max_Retrans_DL = 3: N3103_Limit < 2 that is N3103_Limit = 1
External --
comment
Internal comment --
name TRX nb No
Definition For a DL GPRS TBF, if the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, this parameter defines the maximum number of expected Packet
Coding rules --
Mandatory rules --
Recommended --
rules
External If N3105_LIMIT < TBF_CS_DL then the loss of consecutive packet DL ACK/NACK will not trigger link adaptation but TBF release. N3105_Limit has to be set in order not
comment to release a DL TBF in case of transient bad radio conditions. The polling frequency depends on GPRS_DL_Ack_Period, T_DL_GPRS_MeasReport, MS multislot class
and on the number of TBFs per PDCH.
Internal comment --
Logical N3105_LIMIT_SATELLITE B11 Yes B12 Yes
name TRX nb No
HMI N3105_LIMIT_SATELLITE Sub-syste MFS Cell Type No
Definition For a DL GPRS TBF, if the EGPRS traffic is carried through Abis satellite link or Ater satellite link, this parameter defines the maximum number of expected Packet Downlink
ACK/NACK or Packet Control Acknowledgement messages consecutively lost on the radio interface, before triggering an abnormal release of the DL TBF. This parameter
is used in conjunction with the MIN_RLF_TIME_DL delay to decide if the DL TBF shall be released.
Coding rules --
Mandatory rules --
Recommended --
rules
External If N3105_LIMIT_SATELLITE < TBF_CS_DL then the loss of consecutive packet DL ACK/NACK will not trigger link adaptation but TBF release. N3105_LIMIT_SATELLITE
comment has to be set in order not to release a DL TBF in case of transient bad radio conditions. The polling frequency depends on GPRS_DL_Ack_Period_Satellite,
T_DL_GPRS_MeasReport, MS multislot class and on the number of TBFs per PDCH.
name TRX nb No
HMI N391 Sub-syste MFS Cell Type No
Definition Number of polling cycles before Frame Relay " full status enquiry" (see ITU Q.933 Annex A, A.7).
Rec ref. ITU Q.933 Annex A, A.7 Domai GPRS Min value 1 Coded Min 1
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
name TRX nb No
Definition Error threshold (Frame Relay, see Q.933, Annex A).
Rec ref. ITU Q.933, Annex A Domai GPRS Min value 1 Coded Min 1
Coding rules --
Mandatory rules --
Recommended N392*T391 is the value of the link failure detection time

rules
comment
Internal comment --
name TRX nb No
Definition Monitored error counts (Frame Relay, see ITU Q.933 Annex A, A.7).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NB_MAX_BC_PER_PHYSICAL_LINE B11 Yes B12 Yes
name TRX nb No
HMI NB_MAX_BC_PER_PHYSICAL_LINE Sub-syste MFS Cell Type No
Definition Maximum number of bearer channels per physical line.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NB_MAX_BEARER_CHANNELS_PER_GPU B11 Yes B12 Yes
name TRX nb No
HMI NB MAX BEARER CHANNELS PER GPU Sub-syste MFS Cell Type No
Definition Maximum number of Frame Relay bearer channels per GP/GPU board.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment is linked to the maximum number of HDLC formatters per GPU
Applicable to GPU and GP2 and GP3 boards
Logical NB_MAX_GB_PHYSICAL_LINES B11 Yes B12 Yes
name TRX nb No
HMI NB_MAX_GB_PHYSICAL_LINES Sub-syste MFS Cell Type No
Definition Maximum number of PCM per GPU for Gb interface.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NB_MAX_PVC_PER_BEARER_CHANNEL B11 Yes B12 Yes
name TRX nb No
HMI NB MAX PVC PER BEARER CHANNEL Sub-syste MFS Cell Type No
Definition Maximum number of PVC per Frame Relay bearer channel.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NB_MPDCH_LOAD_SAMPLE B11 Yes B12 Yes
name TRX nb No
HMI NB_MPDCH_LOAD_SAMPLE Sub-syste MFS Cell Type No
Definition Number of signalling load samples used to estimate the average load on MPDCH channels.
Coding rules --
Mandatory rules --
Recommended MPDCH_LOAD_PERIOD and NB_MPDCH_LOAD_SAMPLE are used to determine signalling load samples period (Sig_Load_Period = MPDCH_LOAD_PERIOD /
rules NB_MPDCH_LOAD_SAMPLE)
For example, default values, give the following Sig_Load_Period: 30 / 6 = 5s.
External --
comment
Internal comment Needed for MPDCH load counters.
Logical NB_TS_MPDCH (MFS) B11 Yes B12 Yes
name TRX nb No
HMI NB_TS_MPDCH Sub-syste MFS Cell Type No
Definition Number of radio timeslots reserved for the primary and secondary master PDCHs defined in the cell.
Spec ref. MFS INITIALISATION OF TELECOM PART Coded Max 4
Coding rules --
Mandatory rules 0) NB_TS_MPDCH = 0
1) MIN_PDCH > NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = enabled;MIN_PDCH >= NB_TS_MPDCH if EN_FAST_INITIAL_GPRS_ACCESS = disabled.
2) if the network_operation_mode (MFS) parameter is set to 2 (NMO II) then all cells of the BSS must have NB_TS_MPDCH = 0.
iii) MAX_PDCH <= NB_TS_MPDCH + 8*(nb of TRXs with TRX_PREF_MARK = 0) if TRX_PREF_MARK <> 0 on BCCH TRX.
4) When cell_type = extended inner or extended outer, then NB_TS_MPDCH = 0
Recommended --
rules
External - Only the value 0 is supported
comment - The Master PDCH requires the establishment of a GCH (Abis and Ater) which does not carry traffic. In case of Abis or Ater through satellite link, the usage of the
MPDCH must consider the following criteria:
* higher cost of transmission resources through the satellite link;
* limited throughput of the RSL in case of Abis through satellite to about 6 kbit/s (because of round trip delay effect on acknowledged protocol with limited LAP-D
window size). In case of important CS signalling load, the RSL may not be able to transport the additional signalling load due toTBF establishments when no MPDCH is
established.
Hence the recommendation in the GPRS through satellite case is:
* for a cell connected with Abis through satellite and with non negligible signalling load (CS+PS), MPDCH is recommended;
* for a cell connected with Ater through satellite, MPDCH is not recommended.
Internal comment 1) This parameter is used for the cell/GPU mapping purpose by MFS;
2) The signification of coded value is as follows:

0: MPDCH is not configured in the cell; m
1: only one static primary MPDCH is configured in the cell;
2: one static primary MPDCH and one static secondary MPDCH are configured in the cell; template
3: one static primary MPDCH and two static secondary MPDCH are configured in the cell;
4: one static primary MPDCH and three static secondary MPDCH are configured in the cell.
Logical NC_DL_RXLEV_LIMIT_THR B11 Yes B12 Yes

name TRX nb No
HMI NC_DL_RXLEV_LIMIT_THR Sub-systeMFS Cell Type No
Definition Threshold below which a NC cell reselection Cause PT2 can be triggered due to the detection of a better neighbour cell.
Coding rules 0: -110 dBm (Never), 1: -109 dBm, ...,63: -47 dBm (Always) (step size = 1 dB)
Mandatory rules --
Recommended In cells where outgoing GPRS redirections are systematically triggered (i.e. EN_OUTGOING_GPRS_REDIR = Enable), it is recommended to deactivate NC cell
rules reselection Cause PT2 (i.e. set NC_DL_RXLEV_LIMIT_THR to -110 dBm (Never). The aim of this recommended rule is to limit the conditions triggering a GPRS
redirection.
External 1) The specific value of -110 dBm (Never) deactivates the NC cell reselections Cause PT2.
comment 2) The specific value of -47 dBm (Always) systematically allows the triggering of NC cell reselections Cause PT2
Internal comment --
Logical NC_DL_RXLEV_THR B11 Yes B12 Yes
name TRX nb No
HMI NC_DL_RXLEV_THR Sub-syste MFS Cell Type No
Definition Threshold below which a NC cell reselection Cause PT1 is triggered due to a too bad RXLEV in the downlink direction (while the MS is in packet transfer mode).
Coding rules 0: -110 dBm (Never), 1: -109 dBm, ...,63: -47 dBm (step size = 1 dB)
Mandatory rules --
Recommended In cells where outgoing GPRS redirections are systematically triggered (i.e. EN_OUTGOING_GPRS_REDIR = Enable), it is recommended to activate NC cell reselection
rules Cause PT1 (i.e. set NC_DL_RXLEV_THR to -47 dBm (Always).
External The specific value of -110 dBm (Never) deactivates the NC cell reselection Cause PT1.
comment
Internal comment --
Logical NC_DL_RXQUAL_THR B11 Yes B12 Yes
name TRX nb No
HMI NC_DL_RXQUAL_THR Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Threshold above which a NC cell reselection Cause PT3 is triggered due to a too bad RXQUAL in downlink direction (while the MS is in packet transfer mode).
Coding rules step size = 0.1. At the OMC-R, the following values are displayed: 0, 0.1, 0.2, , 6.9, 7 (Never).
Mandatory rules --
rules reselection Cause PT3 (i.e. set NC_UL_RXQUAL_THR to 7 (Never). The aim of this recommended rule is to limit the conditions triggering a GPRS redirection.
External The specific value of 7 (Never) deactivates the NC cell reselection Cause PT3.
comment
Internal comment --
Logical NC_NON_DRX_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI NC_NON_DRX_PERIOD Sub-syste MFS Cell Type No
Definition Maximum non-DRX period applied by a MS after the sending of a NC measurement report.
Coding rules 000:0 ; 001:0,24 ; 010: 0,48; 011: 0,72; 100: 0,96; 101: 1,20; 110: 1,44; 111: 1,92
Mandatory rules --
Recommended Shall be >= round_trip_delay + MAX_AGCH_QUEUING_DELAY + time for PCU to react to a Packet Measurement Report plus a Packet Cell Change Failure message.
rules
External --
comment
Internal comment --
Logical NC_PING_PONG_OFFSET B11 Yes B12 Yes
name TRX nb No
HMI NC_PING_PONG_OFFSET Sub-syste MFS Cell Type No
Definition NC ping-pong offset which is applied to the C2 or C32 criterion to disfavour the neighbour cells during T_NC_PING_PONG_OFFSET.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NC_REPORTING_PERIOD_I B11 Yes B12 Yes
name TRX nb No
HMI NC_REPORTING_PERIOD_I Sub-syste MFS Cell Type No
Definition Reporting period of NC measurements reported by the MS while in packet idle mode.
Coding rules coded from 0 to 7 (0 0 0 : 0.48 sec , 0 0 1: 0.96 sec , 0 1 0 : 1.92 sec , 0 1 1: 3.84 sec, 1 0 0 : 7.68 sec , 1 0 1 : 15.36 sec , 1 1 0: 30.72 sec , 1 1 1: 61.44 sec) .
Mandatory rules --
Recommended In order to avoid overloading the (P)CCCH with Packet Measurement Report messages reported by MS in packet idle mode, it is recommended that the
rules NC_REPORTING_PERIOD is higher that the GMM Ready timer.
External --
comment
Internal comment --
Logical NC_REPORTING_PERIOD_T B11 Yes B12 Yes
name TRX nb No
HMI NC_REPORTING_PERIOD_T Sub-syste MFS Cell Type No
Definition Reporting period of NC measurements reported by the MS while in packet transfer mode.
Mandatory rules --
Recommended --
rules
External --
comment
Logical NC_REPORTING_PERIOD_T(n) B11 Yes B12 Yes
name TRX nb No
HMI NC_REPORTING_PERIOD_T(n) Sub-syste MFS Cell Type No
Definition Reporting period of NC measurements reported by the MS while in packet transfer mode.
Mandatory rules --
Recommended --
rules
External --
comment
Logical NC_RESELECT_HYSTERESIS(0,n) B11 Yes B12 Yes
name TRX nb No
HMI NC_RESELECT_HYSTERESIS Sub-syste MFS Cell Type No
Definition NC cell reselection offset used for triggering power budget causes.
Rec ref. None Domai GPRS Min value -127 Coded Min 0
Coding rules 0: -127 dB (Always), 1: -126 dB, , 254: 127 dB, 255: 128 dB (Never)
(step size = 1 dB)
Mandatory rules --
Recommended --
rules
External 1) The specific value of 128 dB (Never) deactivates the NC cell reselection Cause PT2 towards the target cell n.
comment 2) The specific value of -127 dB (Always) systematically triggers the NC cell reselection Cause PT2 towards the target cell n.
Internal comment The short name of this parameter displayed in the OMC-R in the Existent Adjacencies table is: NcHyst.
Logical NC_RXLEV_FORGETTING_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI NC_RXLEV_FORGETTING_FACTOR Sub-syste MFS Cell Type No
Definition Forgetting factor of the filter used to average the NC measurements reported in the Packet Measurement Report messages.
Mandatory rules --
Recommended --
rules
External This parameter applies to the serving cell and the neighbour cells.
comment
Internal comment The default value is recommended for NC_REPORTING_PERIOD_T = 0.96 s. It has been obtained so that the coefficient of the filter is twice lower than the forgetting
factor after an averaging period of 5 * NC_REPORTING_PERIOD_T = 4.8 s. This value is determined as follows: NC_RXLEV_FORGETTING_FACTOR = 1 (1/2)5
Logical NC_RXQUAL_AVG_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI NC_RXQUAL_AVG_PERIOD Sub-syste MFS Cell Type No
Definition Period after which a weight of 0.9 s is applied to the current UL or DL RXQUAL samples in the averaging filter.
Category Site (CAE) OMC-R access Changeable Type Number Unit ms
Mandatory rules --
Recommended --
rules
External This parameter applies to the serving cell.
comment
Internal comment --
Logical NC_RXQUAL_HYSTERESIS B11 Yes B12 Yes
name TRX nb No
HMI NC_RXQUAL_HYSTERESIS Sub-syste MFS Cell Type No
Definition Hysteresis to avoid frequent NC cell reselection alarms on the PMU-PTU interface
Coding rules step size: 0.1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The purpose of this parameter is to avoid frequent exchanges on the PMU-PTU interface to signal that an NC cell reselection alarm has been raised or has
disappeared.
Logical NC_UL_RXQUAL_THR B11 Yes B12 Yes
name TRX nb No
HMI NC_UL_RXQUAL_THR Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Threshold above which a NC cell reselection Cause PT4 is triggered due to a too bad RXQUAL in uplink direction (while the MS is in packet transfer mode).
Coding rules step size = 0.1. At the OMC-R, the following values are displayed: 0, 0.1, 0.2, , 6.9, 7 (Never)
Mandatory rules --
rules reselection Cause PT4 (i.e. set NC_UL_RXQUAL_THR to 7 (Never). The aim of this recommended rule is to limit the conditions triggering a GPRS redirection.
External The specific value of 7 (Never) deactivates the NC cell reselection Cause PT4.
comment
Internal comment --
Logical NC2_DEACTIVATION_MODE B11 Yes B12 Yes
name TRX nb No
HMI NC2_DEACTIVATION_MODE Sub-systeMFS Cell Type No
Definition NC2 deactivation mode. This parameter defines whether or not the Packet Measurement Order message with a Reset Command is sent at the end of a packet transfer.
Coding rules 0: "NC2 deactivation at the end of the packet transfer". A Packet Measurement Order message is sent to deactivate the NC2 mode at the end of the packet transfer.
1: "NC2 deactivation at the expiry of the GMM Ready timer". No Packet Measurement Order message is sent to deactivate the NC2 mode.
Mandatory rules --
Recommended In cells where outgoing GPRS redirections are not triggered systematically (i.e. EN_OUTGOING_GPRS_REDIR = Disable), the presence of the PBCCH is not
rules mandatory. However, the following recommendations apply, depending on the presence of the PBCCH:
- If PBCCH is present, the NC2_DEACTIVATION_MODE can be set to any value (at the end of the packet transfer mode or at the expiry of the GMM Ready timer) if the
setting of the C32 parameters ensures that GPRS mobile stations do not camp in cells where outgoing GPRS redirections are systematically triggered.
- If PBCCH is not present or PBCCH is present but C32 parameters are not correctly set, the NC2_DEACTIVATION_MODE should be set to "at the expiry of the GMM
Ready timer" to prevent the GPRS mobile stations from reselecting a cell where outgoing GPRS redirections are triggered systematically (at least while the MS is in
packet idle mode and the GMM Ready timer is running).
External --
comment
Internal comment --
Logical NC2_LOAD_EV_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI NC2_LOAD_EV_PERIOD Sub-syste MFS Cell Type No
Definition Number of NC2 load samples used to compute the NC2 load average
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NCC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI NCC Sub-syste MFS Cell Type No
Definition Network Colour code of the cell.
Mandatory rules - Equal to NCC (BSC)

- NCC (MFS) shall be included in NCC_permited
Recommended --
rules
comment
Logical NCC(n) B11 Yes B12 Yes
name TRX nb No
HMI NCC Sub-syste MFS Cell Type No
Definition Network Colour code of the neighbour cell.
Mandatory rules NCC(n) shall be included in NCC_permited of the serving cell
Recommended --
rules
comment This parameter is for every cell (OMC external cells and OMC internal cells). The operator needs to configure the value of that parameter for every cell.
Logical NECI (MFS) B11 Yes B12 Yes
name TRX nb No
HMI New Establishment Causes Indicator Sub-syste MFS Cell Type No
Definition New Establishment Causes Indicator. Indicates to the MS if the network supports the new GSM Phase 2 establishment causes in CHANNEL REQUEST.
Coding rules 0: not supported, 1: supported
Mandatory rules Equal to NECI (BSC)
Recommended --
rules
External --
comment
Logical NETWORK_CONTROL_ORDER B11 Yes B12 Yes
name TRX nb No
HMI NETWORK_CONTROL_ORDER Sub-syste MFS Cell Type No
Definition This parameter defines whether the MS or the BSS controls the cell reselections.
Coding rules 0: NC0 mode of operation for all MS. All MS controls their cell reselections and no MS reports packet measurements to the BSS.
1: NC1 mode of operation for all MS. All MS controls their cell reselections but all the MS reports packet measurements to the BSS. (Not supported)
2: NC2 mode of operation for R99 onwards MS. The BSS controls the cell reselections of R99 onwards MS when in packet transfer mode or of R99 onwards MS
when in GMM Ready state (depending on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet
measurements to the BSS.
3: NC2 mode of operation for all MS. The BSS controls the cell reselections of all MS when in packet transfer mode or of all MS when in GMM Ready state (depending
on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS.
4: NC2 mode of operation for Rel.4 onwards MS. The BSS controls the cell reselections of Rel.4 onwards MS when in packet transfer mode or of Rel.4 onwards MS
Mandatory rules - The OMC-R only shows the values 0, 2, 3 and 4 to the operator.
- When cell_type = extended inner or extended outer, then NETWORK_CONTROL_ORDER = NC0 mode of operation for all MS
Recommended --
rules
External If the NETWORK_CONTROL_ORDER is set to NC2 mode of operation for R99 onwards MS or NC2 mode of operation for all MS" or NC2 mode of operation for Rel.4
comment onwards MS, then the 3G search is systematically deactivated when activating the NC2 mode (activation performed through the Packet Measurement Order [NC2]
message).
If EN_2G_TO_3G_CELL_RESELECTION = "Enabled with 3G search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1", then the 3G
search is activated even when activating the NC2 mode (the Packet Measurement Order [NC2] message will not be sent).
Internal comment --
Logical NETWORK_CONTROL_ORDER(n) B11 Yes B12 Yes
name TRX nb No
HMI NETWORK_CONTROL_ORDER Sub-syste MFS Cell Type No
Definition This parameter defines whether the MS or the BSS controls the cell reselections.
Coding rules 0: NC0 mode of operation for all MS. All MS controls their cell reselections an no MS reports packet measurements to the BSS.
1: NC1 mode of operation for all MS. All MS controls their cell reselections but all the MS reports packet measurements to the BSS. (Not supported)
2: NC2 mode of operation for R99 onwards MS. The BSS controls the cell reselections of R99 onwards MS when in packet transfer mode or of R99 onwards MS
3: NC2 mode of operation for all MS. The BSS controls the cell reselections of all MS when in packet transfer mode or of all MS when in GMM Ready state (depending
on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS.
4: NC2 mode of operation for Rel.4 onwards MS. The BSS controls the cell reselections of Rel.4 onwards MS when in packet transfer mode or of Rel.4 onwards MS
Mandatory rules - The OMC-R only shows the values 0, 2, 3 and 4 to the operator.
- When cell_type = extended inner or extended outer, then NETWORK_CONTROL_ORDER = NC0 mode of operation for all MS
Recommended --
rules
External If the NETWORK_CONTROL_ORDER is set to NC2 mode of operation for R99 onwards MS or NC2 mode of operation for all MS" or NC2 mode of operation for Rel.4
comment onwards MS, the 3G search is systematically deactivated when activating the NC2 mode (activation performed through the Packet Measurement Order [NC2]
message). This 3G search deactivation is then performed independently of the value of the EN_2G_TO_3G_CELL_RESELECTION parameter.
Internal comment --
Logical network_operation_mode (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Network_mode_of_operation Sub-syste MFS Cell Type No
Definition This parameter defines the CS-PS co-ordination for paging.
Coding rules 3 possible values : 1, 2, 3; 1 == Network operation mode I ; 2 == Network operation mode II ; 3 == Network operation mode III
Mandatory rules If the network_operation_mode (MFS) parameter is set to NMO II then all cells of the BSS must have NB_TS_MPDCH = 0.
Equal to network_operation_mode (BSC).
External Any change will trigger a data reset of the GPUs. Stop and restart of (E)GPRS traffic in all the cells of the BSS.
comment NMO I requires a Gs interface.
Internal comment Coding at radio interface is different, i.e. 0 == Network operation mode I ; 1 == Network operation mode II ; 2 == Network operation mode III.
Logical NIR B11 Yes B12 Yes
name TRX nb No
HMI Normal Information Rate Sub-syste MFS Cell Type No
Definition Normal Information Rate.
Coding rules --
Mandatory rules CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC
Recommended NIR=0 when direct access is used

rules
comment
Internal comment --
Logical NORMAL_PRECEDENCE_BACKGROUND_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI NORMAL_PRECEDENCE_BACKGROUND_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for Background Packet Flow Context, with precedence parameter set to 'normal'
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NORMAL_PRECEDENCE_INSTANT_MSG_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI NORMAL_PRECEDENCE_INSTANT_MSG_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the TBF relative priority used for Instant message service DL PDU, with precedence parameter set to 'Normal'.
15: lowest priority
Recommended --
rules
Logical NORMAL_PRECEDENCE_THP1_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI NORMAL_PRECEDENCE_THP1_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for Interactive THP1 Packet Flow Context, with precedence parameter set to 'normal'
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NRI_LENGTH_PS B11 Yes B12 Yes
name TRX nb No
HMI NRI_LENGTH_PS Sub-syste MFS Cell Type No
Definition This parameter defined the configurable length of a NRI (Network Resource Identification), expressed as a number of bits It is used to derive the NRI value from the
received TLLI, and to identify the serving SGSN, connected to the BSS (Gbflex feature). The NRI is coded starting from the bit 23 (the most significant bit of the NRI) of the
TLLI, regardless of the NRI length.
Coding rules --
Mandatory rules - Each NRI of the list <= 2^NRI_LENGTH_PS 1

- NULL_NRI_PS <= 2^NRI_LENGTH_PS 1
Recommended The operator must control that the same NRI_LENGTH_PS is configured in all the BSSs belonging to a same pool area.
rules
External Significant only if EN_GB_FLEX is enabled.
comment
Internal comment - The value (5) allows to define up to 2^5-1 = 31 NRI, so 31 SGSN.
- According to TS23.236, the length of the NRI shall be the same in all nodes of a domain in a pool area.
Logical NRI_LIST_PS B11 Yes B12 Yes
name TRX nb No
HMI NRI_LIST_PS Sub-systeMFS Cell Type No
Definition List of the Network Resource Identifiers, associated to a given SGSN, connected to the MFS (Gbflex feature). Up to 8 NRIs can be defined per SGSN (and at least one).
The NRI is part of the temporary identity P-TMSI, which is assigned by the serving SGSN to the MS. The MFS derives the NRI from the TLLI received from the MS, in order
to identify the serving SGSN.
The value 1024 is only defined for implementation purpose (it is not a valid value).
Mandatory rules - In a BSS, 2 different SGSNs must have 2 different NRI_LIST_PS.
- A NRI shall be unique among all the NRI_LIST_PS of all the NSEs of one GP/GPU.
- Each NRI of the list <= 2^NRI_LENGTH_PS 1
- For a BSS, the NULL_NRI_PS shall not be included in any NRI_LIST_PS of any NSE connected to that BSS.
Recommended - For all the BSSs belonging to a same pool area, the NSEs connected to one SGSN must all have the same NRI_LIST_PS, in order for a MS to be served by that
rules dedicated SGSN inside the whole pool area (area belonging or not to the same MFS)
- In a BSS in multi-GP/GPU configuration, for a consistent behaviour of the Gbflex feature, all the NSEs, connected to one SGSN, must have the same NRI_LIST_PS.
External Significant only if EN_GB_FLEX is enabled

comment
Internal comment - According to 3GPP TS 23.236, more than one NRI may be assigned to a CN node.
Logical NRT_GUARANTEED_MARGIN B11 Yes B12 Yes
name TRX nb No
HMI NRT_GUARANTEED_MARGIN Sub-syste MFS Cell Type No
Definition For a PDCH, percentage of channel capacity (in terms of radio block scheduling) which is exclusively reserved to NRT TBFs. That capacity is not allowed to be allocated
to a streaming TBF (RT PFC).
Mandatory rules --
Recommended --
rules
External In each direction (DL or UL), the minimum number of NRT TBFs which are possible (in all cases) to be established on a PDCH is equal to
comment ((NRT_GUARANTEED_MARGIN/100) * (T_MAX_FOR_TBF_SCHEDULING/20ms)) rounded down to the closest integer value. This minimum number of NRT TBFs is
guaranteed even in case of RT PFC allocation on the PDCH.
The higher the value of NRT_GUARANTEED_MARGIN, the higher the risks of rejecting RT PFC creation requests.
The lower the value of NRT_GUARANTEED_MARGIN, the higher the risks of rejecting NRT TBF establishment requests (signalling or data traffic).
Internal comment --
Logical NS_alive_IP_retries B11 Yes B12 Yes
name TRX nb No
HMI NS_alive_IP_retries Sub-syste MFS Cell Type No
Definition Maximum number of attempts for NS_VC test procedure in case of Gb over IP.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical NS_ALIVE_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI NsAliveRetries Sub-syste MFS Cell Type No
Definition Maximum number of attempts to test.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NS_BLOCK_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI NsBlockRetries Sub-syste MFS Cell Type No
Definition maximum number of attempts to block a NS-VC.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NS_Priority B11 Yes B12 Yes
name TRX nb No
HMI NS Priority Sub-syste MFS Cell Type No
name Instance NSVC RMS No
Definition Priority of the NSVC, is used by the load sharing (used for Gb over Frame Relay interface).
Coding rules 1: lowest priority, 255:highest priority
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NS_RESET_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI NsResetRetries Sub-syste MFS Cell Type No
Definition Maximum number of attempts to reset.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NS_UNBLOCK_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI NsUnblockRetries Sub-syste MFS Cell Type No
Definition Maximum number of attempts to unblock a NS-VC.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical NSEI B11 Yes B12 Yes
name TRX nb No
HMI NSEI Sub-syste MFS Cell Type No
Definition NSE Identifier.
Coding rules --
Mandatory rules The NSEI shall be unique per PCU.
Recommended --
rules
External --
comment
Internal comment mandatory forbids more than needed, but is simple. In fact, the NSEI shall be unique per SGSN (to avoid erasing the previous NSE created with the same NSEI).
Logical NSEMAX B11 Yes B12 Yes
name TRX nb No
HMI NSE MAX Sub-syste MFS Cell Type No
Definition Maximum number of NSE per PMU.
Coding rules --
Mandatory rules --
Recommended --
rules
External significant only if EN_GB_FLEX = disabled or not supported,
comment (else MAX_NB_SGSN (BOP))
Internal comment --
Logical NSVCI B11 Yes B12 Yes
name TRX nb No
HMI NSVC Identifier Sub-syste MFS Cell Type No
name Instance NSVC RMS No
Definition NSVC identifier (used for Gb over Frame Relay interface).
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment SGSN IP endpoints are used for Gb over IP interface.
Logical NSVCMAX B11 Yes B12 Yes
name TRX nb No
HMI NSVC MAX Sub-syste MFS Cell Type No
Definition Maximum number of NSVC per GPU.
Coding rules --
Recommended --
rules
comment
Internal comment --
Logical NULL_NRI_PS B11 Yes B12 Yes
name TRX nb No
HMI NULL_NRI_PS Sub-syste MFS Cell Type No
Definition In UL cases, upon TLLI reception with that dummy/reserved NRI included, while a SGSN is not already selected for a mobile, the load balancing algorithm allows selecting
one SGSN among the on loaded SGSN connected to the BSS (Gbflex feature).
Mandatory rules - NULL_NRI_PS <= 2^NRI_LENGTH_PS 1

- For a BSS, the NULL_NRI_PS shall not be included in any NRI_LIST_PS of any NSE connected to that BSS.
- For a BSS, the NULL_NRI_PS shall not be included in any NRI_LIST_PS_LRC of any SGSN connected to that BSS.
Recommended The operator must control that the NULL_NRI_PS is common inside all the BSSs of one PLMN
rules
comment
Internal comment - According to TS23.236, there is one unique null NRI in a PLMN.
Logical OandM_PRIORITY (MFS) B11 Yes B12 Yes
name TRX nb No
HMI OandM_PRIORITY (MFS) Sub-syste MFS Cell Type No
Definition BSS internal priority used by the O&M flows in IP network
3: lower priority
Mandatory rules Equal to OandM_PRIORITY (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical P0_LAYER2_MAPPING_MFS B11 Yes B12 Yes
name TRX nb No
HMI P0_LAYER2_MAPPING_PS Sub-syste MFS Cell Type No
Definition Defines, for the PCU, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P0 internal priority (the highest).
Mandatory rules P0_LAYER2_MAPPING_MFS >= P1_LAYER2_MAPPING_MFS
Recommended The operator shall ensure that it is equal to P0_LAYER2_MAPPING_BSC

rules
comment
Internal comment --
name TRX nb No
HMI P0_LAYER3_MAPPING_PS Sub-systeMFS Cell Type No
Definition Defines the Diffserv DSCP value used on the IP network by the PCU flows having the P0 internal BSS priority (P0 is the highest priority).
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
Internal comment - Note this priority is not used (EF class is not used by the flows handled by the MFS).
name TRX nb No
Definition Defines, for the PCU, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P1 internal priority.
Mandatory rules P0_LAYER2_MAPPING_MFS >= P1_LAYER2_MAPPING_MFS >= P2_LAYER2_MAPPING_MFS

rules
comment
Internal comment --
name TRX nb No
Definition Defines the Diffserv DSCP value used on the IP network by the PCU flows having the P1 internal BSS priority (P3 is the lowest priority).
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
Internal comment --
name TRX nb No
Definition Defines, for the PCU, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P2 internal priority.

rules
comment
Internal comment --
name TRX nb No
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
Internal comment --
name TRX nb No
Definition Defines, for the PCU, the priority indicated in L2 protocol (e.g. ethernet), corresponding to the flows having the P3 internal priority (the lowest).

rules
comment
Internal comment --
name TRX nb No
00 for BE,
10,12,14 for AF1;
18,20,22 for AF2;
26, 28,30 for AF3;
34, 36, 38 for AF4
and 46 for EF.

rules
comment
Internal comment --
Logical PACKET_LOAD_BROADCAST_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI PACKET_LOAD_BROADCAST_PERIOD Sub-syste MFS Cell Type No
Definition RRM reporting period to update the information (per cell) necessary for the Multi-GP(U) feature.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Applicable to GPU and GP2 and GP3 boards
Logical PAN_DEC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI PAN_DEC Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Value decremented from MS N3102 counter when PACKET UL ACK/NACK is not received before MS timer T3182.
Mandatory rules Equal to PAN_DEC (BSC)
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection.
Logical PAN_INC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI PAN_INC Sub-syste MFS Cell Type No
Definition Value incremented to MS N3102 counter when PACKET UL ACK/NACK is received by MS.
Mandatory rules Equal to PAN_INC (BSC)
Recommended --
rules
External --
comment
Logical PAN_MAX (MFS) B11 Yes B12 Yes
name TRX nb No
HMI PAN_MAX Sub-syste MFS Cell Type No
Definition Maximum value for counter N3102. cell reselection is done by MS when N3102 <= 0.
Coding rules Possible values : 4, 8, 12,.., 32 respectively binary coded 000, 001,.. , 111
Mandatory rules Equal to PAN_MAX (BSC)
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile staion shall perform an abnormal release with cell re-selection
Logical Pb B11 Yes B12 Yes
name TRX nb No
HMI Pb Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition Power reduction value used by the BTS on PBCCH blocks, relative to the output power used on BCCH.
Category System (CST) OMC-R access None (DLS) Type Number Unit dB
Coding rules Possible values : 0, -2, -4, .., -30 dB respectively binary coded as 0000, 0001, .., 1111
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH.
Logical PC_MEAS_CHAN (MFS) B11 Yes B12 Yes
name TRX nb No
HMI PC_MEAS_CHAN Sub-syste MFS Cell Type No
Definition This parameter determines on which channel the MS shall measure the received power level on the downlink for the purpose of the uplink power control.
Coding rules 0 : downlink measurements for power control shall be made on BCCH,
1 : downlink measurements for power control shall be made on PDCH
Mandatory rules See PC_MEAS_CHAN (BSC).
Recommended --
rules
External --
comment
Internal comment --
Logical PCC_n_RT_THROUGHPUT B11 Yes B12 Yes
name TRX nb No
HMI PCC_n_RT_THROUGHPUT Sub-syste MFS Cell Type No
Definition Trigger for the RT computation in PCC (for the TDM & IP mode), expressed in number of times of PCC_T_LEAKY_BUCKET timer.
Mandatory rules --
Recommended --
rules
External The RT_THROUGHPUT computation is triggered after PCC_n_RT_THROUGHPUT times PCC_T_LEAKY_BUCKET.
comment
Internal comment As in IP mode the arrival time of a TRN-DL-ACK.ind for an extra-scheduled PDU can be seriously delayed (or not coming at all) due to the possible congestion on Abis,
it is decided to not trigger the RT_THROUGHPUT computation by the receiving of a TRN-DL-ACK.ind message from RLC
Logical PCC_T_LEAKY_BUCKET B11 Yes B12 Yes
name TRX nb No
HMI PCC_T_LEAKY_BUCKET Sub-syste MFS Cell Type No
Definition Timer controlling the activation of the DL flow control per TBF on IP mode (leaky bucket algorithm) for all TBFs on a cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PCC_T_MAX_UL_BUFFERING B11 Yes B12 Yes
name TRX nb No
HMI PCC_T_MAX_UL_BUFFERING Sub-syste
MFS Cell Type No
name InstanceMFS RMS No
Definition Maximum UL buffering capability in PCC, expressed as a duration : Time which multiplied by (TBF_nbr_PDCH * (M)CS throughput) defines a buffer level above which the
UL transfer is considered as failed.
Coding rules Step size = 1sec.
Mandatory rules --
Recommended When a PDU is not received in the correct order (this case can occur in IP mode, after a pfc priority change or after a reallocation), the PDUs are kept in a buffer. This
rules parameter allows to define the size of this buffer.
External --
comment
Internal comment --
Logical PCC_UL_TBF_GUARD_TIMER B11 Yes B12 Yes
name TRX nb No
HMI PCC_UL_TBF_GUARD_TIMER Sub-syste MFS Cell Type No
Definition Guard timer of an UL TBF used in IP mode to supervise the reception of UL LLC PDUs. At expiration, the UL TBF is released.
Mandatory rules In IP mode: PCC_UL_TBF_GUARD_TIMER < T_IPGCHU_TIMEOUT, because T_IPGCHU_TIMEOUT offers a defense at a higher level (IPGCH flow level) than
PCC_UL_TBF_GUARD_TIMER (TBF level).
Recommended --
rules
External --
comment
Internal comment --
Logical PD_DL_PDCH_UNIT_ALLOC_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI PD_DL_PDCH_UNIT_ALLOC_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for DL PDCH unit allocation distribution
Coding rules step size = 0.1 PDCH
Mandatory rules PD_DL_PDCH_UNIT_ALLOC_THR_1< PD_DL_PDCH_UNIT_ALLOC_THR_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th band for DL PDCH unit allocation distribution
Mandatory rules --
Recommended --
rules
External PD_DL_PDCH_UNIT_ALLOC_THR_9 < PD_DL_PDCH_UNIT_ALLOC_THR_10
comment
Internal comment - Coded value of 50 (instead of 5) is introduced for consistency with other PD_DL_PDCH_UNIT_ALLOC_THR_i parameters
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for DL PDCH unit allocation distribution
Mandatory rules PD_DL_PDCH_UNIT_ALLOC_THR_1 < PD_DL_PDCH_UNIT_ALLOC_THR_2< PD_DL_PDCH_UNIT_ALLOC_THR_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for DL PDCH unit allocation distribution
Mandatory rules PD_DL_PDCH_UNIT_ALLOC_THR_2 < PD_DL_PDCH_UNIT_ALLOC_THR_3 < PD_DL_PDCH_UNIT_ALLOC_THR_4
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th band, lower limit of the 5th band for DL PDCH unit allocation distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules PD_DL_PDCH_UNIT_ALLOC_THR_8 < PD_DL_PDCH_UNIT_ALLOC_THR_9
Recommended --
rules
External --
comment
Internal comment --
Logical PD_DL_TBF_DURATION_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI PD_DL_TBF_DURATION_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the first band, lower limit of the second band for DL TBF duration distribution.
Mandatory rules PD_DL_TBF_DURATION_THR_1 < PD_DL_TBF_DURATION_THR_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th band for DL TBF duration distribution
Mandatory rules --
Recommended --
rules
External PD_DL_TBF_DURATION_THR_9 < PD_DL_TBF_DURATION_THR_10
comment
Internal comment - Coded value of 32768 (instead of 16384) is introduced for consistency with other PD_DL_TBF_DURATION_THR_i parameters
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for DL TBF duration distribution
Mandatory rules PD_DL_TBF_DURATION_THR_1 < PD_DL_TBF_DURATION_THR_2 < PD_DL_TBF_DURATION_THR_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for DL TBF duration distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th band, lower limit of the 5th band for DL TBF duration distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules PD_DL_TBF_DURATION_THR_8 < PD_DL_TBF_DURATION_THR_9
Recommended --
rules
External --
comment
Internal comment --
Logical PD_DL_TBF_VOLUME_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI PD_DL_TBF_VOLUME_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for LLC volume carried by an DL TBF distribution
Mandatory rules PD_DL_TBF_VOLUME_THR_1 < PD_DL_TBF_VOLUME_THR_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th band for LLC volume carried by an DL TBF distribution
Mandatory rules --
Recommended --
rules
External PD_DL_TBF_VOLUME_THR_9 < PD_DL_TBF_VOLUME_THR_10
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for LLC volume carried by an DL TBF distribution
Mandatory rules PD_DL_TBF_VOLUME_THR_1 < PD_DL_TBF_VOLUME_THR_2 < PD_DL_TBF_VOLUME_THR_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for LLC volume carried by an DL TBF distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th band, lower limit of the 5th band for LLC volume carried by an DL TBF distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules PD_DL_TBF_VOLUME_THR_8 < PD_DL_TBF_VOLUME_THR_9
Recommended --
rules
External --
comment
Internal comment --
Logical PD_UL_PDCH_UNIT_ALLOC_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI PD_UL_PDCH_UNIT_ALLOC_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for UL PDCH unit allocation distribution
Mandatory rules PD_UL_PDCH_UNIT_ALLOC_THR_1< PD_UL_PDCH_UNIT_ALLOC_THR_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th band for UL PDCH unit allocation distribution
Mandatory rules --
Recommended --
rules
External PD_UL_PDCH_UNIT_ALLOC_THR_9 < PD_UL_PDCH_UNIT_ALLOC_THR_10
comment
Internal comment - Coded value of 50 (instead of 5) is introduced for consistency with other PD_UL_PDCH_UNIT_ALLOC_THR_i parameters
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for UL PDCH unit allocation distribution
Mandatory rules PD_UL_PDCH_UNIT_ALLOC_THR_1 < PD_UL_PDCH_UNIT_ALLOC_THR_2< PD_UL_PDCH_UNIT_ALLOC_THR_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for UL PDCH unit allocation distribution
Mandatory rules PD_UL_PDCH_UNIT_ALLOC_THR_2 < PD_UL_PDCH_UNIT_ALLOC_THR_3 < PD_UL_PDCH_UNIT_ALLOC_THR_4
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th band, lower limit of the 5th band for UL PDCH unit allocation distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules PD_UL_PDCH_UNIT_ALLOC_THR_8 < PD_UL_PDCH_UNIT_ALLOC_THR_9
Recommended --
rules
External --
comment
Internal comment --
Logical PD_UL_TBF_DURATION_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI PD_UL_TBF_DURATION_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the first band, lower limit of the second band for UL TBF duration distribution.
Mandatory rules PD_UL_TBF_DURATION_THR_1 < PD_UL_TBF_DURATION_THR_2
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 10th band for UL TBF duration distribution
Mandatory rules --
Recommended --
rules
External PD_UL_TBF_DURATION_THR_9 < PD_UL_TBF_DURATION_THR_10
comment
Internal comment - Coded value of 32768 (instead of 16384) is introduced for consistency with other PD_UL_TBF_DURATION_THR_i parameters
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for UL TBF duration distribution
Mandatory rules PD_UL_TBF_DURATION_THR_1 < PD_UL_TBF_DURATION_THR_2 < PD_UL_TBF_DURATION_THR_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for UL TBF duration distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th band, lower limit of the 5th band for UL TBF duration distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules PD_UL_TBF_DURATION_THR_8 < PD_UL_TBF_DURATION_THR_9
Recommended --
rules
External --
comment
Internal comment --
Logical PD_UL_TBF_VOLUME_THR_1 B11 Yes B12 Yes
name TRX nb No
HMI PD_UL_TBF_VOLUME_THR_1 Sub-syste MFS Cell Type No
Definition Upper limit of the 1st band, lower limit of the 2nd band for LLC volume carried by an UL TBF distribution
Mandatory rules PD_UL_TBF_VOLUME_THR_1 < PD_UL_TBF_VOLUME_THR_2
Recommended --
rules
External --
comment
Internal comment An odd value activates the collect of the debug counters used for the detection of "PS quality on TS based" on TRX Edge capable (EGPRS-Capability >= 3).
name TRX nb No
Definition Upper limit of the 10th band for LLC volume carried by an UL TBF distribution
Mandatory rules --
Recommended --
rules
External PD_UL_TBF_VOLUME_THR_9 < PD_UL_TBF_VOLUME_THR_10
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 2nd band, lower limit of the 3rd band for LLC volume carried by an UL TBF distribution
Mandatory rules PD_UL_TBF_VOLUME_THR_1 < PD_UL_TBF_VOLUME_THR_2 < PD_UL_TBF_VOLUME_THR_3
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 3rd band, lower limit of the 4th band for LLC volume carried by an UL TBF distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Upper limit of the 4th band, lower limit of the 5th band for LLC volume carried by an UL TBF distribution
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules PD_UL_TBF_VOLUME_THR_8 < PD_UL_TBF_VOLUME_THR_9
Recommended --
rules
External --
comment
Internal comment --
Logical PDCH_BUFFERING_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI PDCH_BUFFERING_FACTOR Sub-syste MFS Cell Type No
Definition The buffering delay factor associated to one PDCH that is shared between TBF accordingly to the TBF throughput.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment The given default value is a testing value and must be reconsidered acccording to the global flowcontrol between the MS and the SGSN (Gb interface, RRM and
RLC/MAC buffering).
Logical PDCH_MIN_BUFFERING_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI PDCH_MIN_BUFFERING_FACTOR Sub-syste MFS Cell Type No
Definition The minimum buffering delay between XON and XOFF thresholds that should be used according to the TBF throughput.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment The given default value is a testing value and must be reconsidered acccording to the global flowcontrol between the MS and the SGSN (Gb interface, RRM and
RLC/MAC buffering).
Logical PDCH_TBF_XON_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI PDCH_TBF_XON_FACTOR Sub-syste MFS Cell Type No
Definition Anticipation number of radio blocks considering the throughput of one PDCH.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment The given default value is a testing value and must be reconsidered acccording to the global flow control between the MS and the SGSN (Gb interface, RRM and
RLC/MAC buffering).
Logical PDU_LIFETIME_ORDER B11 Yes B12 Yes
name TRX nb No
HMI PDU_LIFETIME_ORDER Sub-syste MFS Cell Type No
Definition Authorize or inhibit DL LLC PDU ordering according to the remaining PDU lifetime.
Coding rules 0: ordering disabled, 1 : ordering enabled
Mandatory rules --
Recommended Should be set to ordering disabled, when the BSS interfaces with an Ericsson SGSN or any SGSN modifying the PDU Lifetime value during data flows addressed to
rules the same MS on the same LLC SAPI in a non-acceptable manner, otherwise should be set to ordering enabled.
External --
comment
Internal comment --
Logical PDU_REORDER_INHIBIT_THRES_GP B11 Yes B12 Yes
name TRX nb No
HMI PDU_REORDER_INHIBIT_THRES Sub-syste MFS Cell Type No
Definition Thresholds (expressed in number of DL LLC PDUs stored in the PCU buffers) above which
the DL PDU reordering algorithm is inhibited and replaced by another speeder algorithm.
This algorithm discards the unacknowledged DL PDUs of a TBF and resend the other ones stored for that TBF.
Zero means that the normal reordering algorithm (based on the remaining PDU lifetime) applied.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Normal behaviour depends on PDU_LIFETIME_ORDER value.
- The nb of PDUs stored in the MFS queues (PFC + PTU) = PDU not sent + PDU sent but not ack
- Max value is SW memory dependent, and is based on B11 MFS dev inputs
Logical Peer_NSE_Data_Weight B11 Yes B12 Yes
name TRX nb No
HMI Peer_NSE_Data_Weight Sub-syste MFS Cell Type No
name Instance SGSN-IPEndPoint RMS No
Definition Indicates the data weight assigned to the peer NSE, in case of static configuration of the Gb over IP interface.
Mandatory rules --
Recommended --
rules
External Declared by the operator in case of static configuration.
comment If Peer_NSE_Data_Weight=0, the SGSN IP endpoint will not be selected as a data endpoint by the load sharing function.
Internal comment --
Logical Peer_NSE_Signalling_Weight B11 Yes B12 Yes
name TRX nb No
HMI Peer_NSE_Signalling_Weight Sub-syste MFS Cell Type No
Definition Indicates the signalling weight assigned to the peer NSE, in case of static configuration of the Gb over IP interface.
Mandatory rules --
Recommended --
rules
External Declared by the operator in case of static configuration.
comment If Peer_NSE_Signalling_Weight=0, the SGSN IP endpoint will not be selected as a signalling endpoint.
Internal comment --
Logical PENALTY_TIME(MFS) B11 Yes B12 Yes
name TRX nb No
HMI PENALTY_TIME Sub-syste MFS Cell Type No
Coding rules step size = 20s. 0: 20s, 1: 40s, ..., 30: 620s, 31: TEMPORARY OFFSET ignored and cell_RESELECT_OFFSET has a negative value.
Mandatory rules PENALTY_TIME(MFS) = PENALTY_TIME(BSC)
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS. CT: Depends on Cell Type and BTS Type
Logical PENALTY_TIME(n)(MFS) B11 Yes B12 Yes
name TRX nb No
HMI PENALTY_TIME Sub-syste MFS Cell Type No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PERSISTENCE_LEVEL_1 B11 Yes B12 Yes
name TRX nb No
HMI PERSISTENCE_LEVEL_1 Sub-syste MFS Cell Type No
Definition This parameter indicates the values of the access persistence level for radio priority 1.
Coding rules Values : 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 16 coded on 4 bits
0 0 0 0 : persistence level 0, 0 0 0 1: persistence level 1, 0 0 1 0:persistence level 2, 0 0 1 1: persistence level 3, 0 1.0.0 : persistence level 4
. . . . 1 1 1 0 : persistence level 14, 1 1 1 1: persistence level 16
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningless parameter if the Radio Priority 1 is not allowed. Value 16 indicates that access is forbidden.
Needed for MPDCH feature
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Meaningless parameter if the Radio Priority 2 is not allowed Value 16 indicates that access is forbidden.
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Logical PFC_NB_RETRY_DOWNLD B11 Yes B12 Yes
name TRX nb No
HMI PFC_NB_RETRY_DOWNLD Sub-syste MFS Cell Type No
Definition Number of Download_BSS_PFC attempts
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PFC_NB_RETRY_MODIFY B11 Yes B12 Yes
name TRX nb No
HMI PFC_NB_RETRY_MODIFY Sub-syste MFS Cell Type No
Definition Number of Modify_BSS_PFC attempts
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PFC_T6 B11 Yes B12 Yes
name TRX nb No
HMI PFC_T6 Sub-syste MFS Cell Type No
Definition Timer guarding the Download-BSS-PFC procedure
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PFC_T8 B11 Yes B12 Yes
name TRX nb No
HMI PFC_T8 Sub-syste MFS Cell Type No
Definition Timer guarding the Modify-BSS-PFC procedure
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PLMN_FREQUENCY_BANDS(MFS) B11 Yes B12 Yes
name TRX nb No
HMI PLMN_FREQUENCY_BANDS Sub-syste MFS Cell Type No
Definition Frequency bands used in the whole PLMN.
Coding rules 0: GSM900 and DCS1800 bands
4,...,255: for future use
This parameter shall be coded over 8 bits as a provision for future frequency band combinations.
Mandatory rules PLMN_FREQUENCY_BANDS(BSC) = PLMN_FREQUENCY_BANDS(MFS)
- At cell creation
to
Recommended --
rules
External --
comment
Internal comment The value sent by the OMC-R to the MFS corresponds to the value of the OMC-R changeable parameter defined in the BSS O&M Telecom catalogue document
Logical PMU_CPU_OVERLOAD_GP2 B11 Yes B12 Yes
name TRX nb No
HMI PMU_CPU_OVERLOAD_GP2 Sub-syste MFS Cell Type No
Definition Threshold above which a PMU enters the CPU overload state.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical PMU_CPU_OVERLOAD_GP3 B11 No B12 Yes
name TRX nb No
HMI PMU_CPU_OVERLOAD_GP3 Sub-syste MFS Cell Type No
Definition Threshold above which a PMU enters the CPU overload state.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical PMU_CPU_overload_step_H B11 Yes B12 Yes
name TRX nb No
HMI PMU_CPU_overload_step_H Sub-systeMFS Cell Type No
Definition Number of steps to increment the internal PMU variable used in the PMU CPU overload control algorithm, when the PMU is in CPU overload state.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The current default value is chosen so that reaction to overload is faster than return to normal behaviour.
Logical PMU_CPU_overload_step_N B11 Yes B12 Yes
name TRX nb No
HMI PMU_CPU_overload_step_N Sub-syste
MFS Cell Type No
name InstanceGPU RMS No
Definition Number of steps to decrement the internal PMU variable used in the PMU CPU overload control algorithm, when the PMU is in CPU normal load state.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The current default value is chosen so that reaction to overload is faster than return to normal behaviour.
Logical PMU_CPU_sampling_period B11 Yes B12 Yes
name TRX nb No
HMI PMU_CPU_sampling_period Sub-syste MFS Cell Type No
Definition Periodicity at which the PMU CPU load is evaluated for the PMU overload control algorithm.
Category System (CST) OMC-R access None (not in DLS) Type Number Unit sec
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical POW_RED_DEC_STEP_SIZE_PS B11 No B12 Yes
name TRX nb No
HMI POW_INC_STEP_SIZE_PS Sub-syste MFS Cell Type No
Definition Power reduction decrease step size for packet downlink power control.
Mandatory rules --
Recommended - POW_RED_INC_STEP_SIZE_PS <= POW_RED_DEC_STEP_SIZE_PS

rules
Internal comment --
Logical POW_RED_INC_STEP_SIZE_PS B11 No B12 Yes
name TRX nb No
HMI POW_RED_STEP_SIZE_PS Sub-syste MFS Cell Type No
Definition Power reduction increase step size for packet downlink power control.
Mandatory rules --
Recommended - POW_RED_INC_STEP_SIZE_PS <= POW_RED_DEC_STEP_SIZE_PS

rules
Internal comment --
Logical POW_RED_P0 B11 No B12 Yes
name TRX nb No
HMI POW_RED_P0 Sub-syste MFS Cell Type No
Definition Power reduction relative to the BCCH power for Packet Service.
It represents the static part of the packet downlink power control reduction, applicable to the TBFs in either GPRS or EGPRS mode.
Mandatory rules - BS_TXPWR_ATTENUATION + POW_RED_P0 + MAX_POW_RED_DYN <= 32
Recommended - Alcatel-Lucent recommends POW_RED_P0 <= POW_RED_P0_PDDCB for a better efficiency of the power control.
rules
Internal comment - it is applicable to GMSK and 8PSK modulations
Logical POW_RED_P0_PDDCB B11 No B12 Yes
name TRX nb No
HMI POW_RED_P0_PDDCB Sub-syste MFS Cell Type No
Definition Power reduction relative to the BCCH power for the unnecessary PDDCB (Packet DL Dummy Control Block), which are not used for MS synchronisation, nor USF
transport.
It represents the static part of the packet downlink power control reduction, applicable to those PDDCB.
Mandatory rules - BS_TXPWR_ATTENUATION + POW_RED_P0_PDDCB <= 34
Recommended - Alcatel-Lucent recommends POW_RED_P0 <= POW_RED_P0_PDDCB for a better efficiency of the power control.
rules
Internal comment - POWER_RED_P0 is applicable to the other PDDCB that are used for MS synchronisation.
Logical PRACH_BUSY_THRES B11 Yes B12 Yes
name TRX nb No
HMI PRACH_BUSY_THRES Sub-syste MFS Cell Type No
Definition Received level above which a PRACH block is deemed busy.
Rec ref. None Domai GPRS Min value -110 Coded Min 0
Coding rules This parameter is encoded with a step size of 4 dB as follows:
0: -110 dBm
1: -106 dBm
2: -102 dBm
3: -98 dBm
4: -94 dBm
5: -90 dBm
6: -86 dBm
7: -82 dBm
8: -78 dBm
9: -74 dBm
10: -70 dBm
11: -66 dBm
12: -62 dBm
13: -58 dBm
14: -54 dBm
15: -50 dBm
Mandatory rules --
Recommended --
rules
External Parameter used in dynamic allocation of secondary MasterPDCH algorithm.
comment
Internal comment --
Logical PREF_GPS_LIST_Priority_1 B11 Yes B12 Yes
name TRX nb No
HMI PREF_GPS_LIST_Priority_1 Sub-syste MFS Cell Type No
Definition The most preferred GPS positioning method.
Coding rules It contains a reference to a GPS method: 1 for MS Assisted A-GPS, 2 for MS Based A-GPS, 3 for Conventional GPS.
Mandatory rules --
Recommended The same GPS methods reference should not be used for different priorities
rules
External --
comment
Internal comment --
name TRX nb No
Definition The second preferred GPS positioning method.
Mandatory rules --
Recommended The same GPS methods reference should not be used for different priorities.
rules
External --
comment
Internal comment --
name TRX nb No
Definition The third preferred GPS positioning method.
Mandatory rules --
Recommended The same GPS methods reference should not be used for different priorities.
rules
External --
comment
Internal comment --
Logical PRIORITY_ACCESS_THRESHOLD (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Allowed priority classes Sub-syste MFS Cell Type No
Definition This parameter indicates whether or not a MS of a certain priority class is allowed to do a Packet access.
Coding rules Coded over 3 bits . 000: packet access is not allowed in the cell; 011:packet access is allowed for priority level 1; 100: packet access is allowed for priority level 1 to
2; 101: packet access is allowed for priority level 1 to 3; 110: packet access allowed for priority level 1 to 4
Mandatory rules Equal to PRIORITY_ACCESS_THRESHOLD (BSC)
Recommended --
rules
External Persistence level parameter for priority (i) is meaningless if the Radio Priority (i) is not allowed
comment
Internal comment --
Logical PS_RADIO_CONG_RATIO B11 Yes B12 Yes
name TRX nb No
HMI PS_RADIO_CONG_RATIO Sub-syste MFS Cell Type No
Definition Threshold used to determine if a cell is considered as PS radio congested or not. It is expressed as a ratio between the averaged TBF multiplexing level, measured in the
cell, and the maximum TBF multiplexing, allowed in the cell. Same ratio applied to UL and DL TBF multiplexing.
Coding rules 0: the cell is always considered as PS radio congested
Mandatory rules --
Recommended --
rules
comment - The parameter is significant in cell where the reduced PDCH allocation in DL for Instant Message is activated (GPRS_MULTISLOT_CLASS_CONG_IM) or where the
reduced delayed TBF timer is used (T_NETWORK_RESPONSE_TIME_CONG or T_NETWORK_RESPONSE_TIME_IM_CONG).
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied in the evaluation of the PS radio congestion status of the cell,
triggered after modification
- max TBF multiplexing is defined by MAX_UL_TBF_SPDCH and MAX_DL_TBF_SPDCH.
Logical PTM_BVCI B11 Yes B12 Yes
name TRX nb No
HMI PTM BVCI Sub-syste MFS Cell Type No
Definition PTM BVCI value.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical PTP_BVCI B11 Yes B12 Yes
name TRX nb No
HMI BVCI Sub-syste MFS Cell Type No
Definition PTP BVCI value.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The value is set by the MFS.
Logical PVC_Level1_down B11 Yes B12 Yes
name TRX nb No
HMI Level 1 down Sub-syste MFS Cell Type No
Definition This parameter gives the low level of threshold for congestion.
Category Site (CAE) OMC-R access Set by Create Type Number Unit %
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical PVC_Level1_Factor B11 Yes B12 Yes
name TRX nb No
HMI Level 1 Factor Sub-syste MFS Cell Type No
Definition This parameter is used to calculate the amount of data used for buffering.
Mandatory rules --
Recommended amount of memory needed : PVC_Level1_factor * 10 * (CBS+EBS) for a PVC

rules
comment
Internal comment --
Logical PVC_Level1_up B11 Yes B12 Yes
name TRX nb No
HMI Level 1 up Sub-syste MFS Cell Type No
Definition This parameter gives the high level of threshold for congestion.
Category Site (CAE) OMC-R access Set by Create Type Number Unit %
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical PWRC (MFS) B11 Yes B12 Yes
name TRX nb No
HMI PWRC Sub-syste MFS Cell Type No
Definition This flag indicates to the MS whether or not it shall include measurements made on BCCH frequency in case of frequency hopping channel.
Coding rules 0: measurements made on BCCH frequency shall be included, 1: measurements made on BCCH frequency shall not be included
Mandatory rules Equal to PWRC (BSC)
Recommended --
rules
External --
comment
Logical QOS_SAFETY_MARGIN B11 Yes B12 Yes
name TRX nb No
HMI QOS_SAFETY_MARGIN Sub-syste MFS Cell Type No
Definition Additional capacity (in terms of radio bandwidth and in terms of transmission resources) which is reserved for a streaming TBF (RT PFC) to correctly fulfil its AGBR
contract and to possibly convey other multiplexed NRT PFC(s) of the same TBF. The part of this margin that is not used by the streaming TBF may be used by other
TBF(s).
Mandatory rules --
Recommended Setting QOS_SAFETY_MARGIN to 0% is not recommended (the GBR of some RT PFCs may turn out to be impossible to guarantee in this case).
rules
External In case of IP transport in the BSS, UDP/IP headers are taken into account in the bandwidth computation
comment
Internal comment --
Logical Qsearch_P_PTM B11 Yes B12 Yes
name TRX nb No
HMI Qsearch_P_PTM Sub-syste MFS Cell Type No
Definition Threshold for searching for 3G cells in GPRS packet transfer mode depending whether the received level average of the serving cell is below or above the threshold
0: -98: -98 dBm (below)
1: -94: -94 dBm (below)
2: -90: -90dBm (below)
3: -86: -86dBm (below)
4: -82: -82 dBm (below)
5: -78: -78 dBm (below)
6: -74: -74 dBm (below)
8: -78: -78 dBm (above)
9: -74: -74 dBm (above)
10: -70: -70 dBm (above)
11: -66: -66 dBm (above)
12: -62: -62 dBm (above)
13: -58: -58 dBm (above)
14: -54: -54 dBm (above)
Mandatory rules --
Recommended --
rules
comment search for neighbour cells) the threshold in GPRS packet transfer mode.
This parameter is sent in Packet Measurement Order on PACCH.
for 3G neighbour cells).
Logical R_AVERAGE_EGPRS B11 Yes B12 Yes
name TRX nb No
HMI R_AVERAGE_EGPRS m Sub-syste MFS Cell Type No
name Instance cell template RMS No
Definition Average bitrate per PDCH for Edge capable terminals in this cell
Category Site (CAE) OMC-R access Changeable Type Number Unit bit/s
Coding rules --
Mandatory rules RMIN_EGPRS <= R_AVERAGE_EGPRS
Recommended R_AVERAGE_EGPRS shall not be set to a bitrate higher than the useful bitrate corresponding to MAX_EGPRS_MCS (e.g. if MAX_EGPRS_MCS = MCS9 =>
rules R_AVERAGE_EGPRS shall not be higher than 59,2kbps).
External This parameter represents the average bit rate that is targeted, per PDCH, in the cell with respect to the cell radio planning. It is recommended not to set this bit rate
comment higher than the average measured bit rate in the cell.
The default value corresponds to MCS-6.
The max value corresponds to MCS-9.
Internal comment --
Logical R_AVERAGE_GPRS B11 Yes B12 Yes
name TRX nb No
HMI R_AVERAGE_GPRS Sub-syste MFS Cell Type No
Definition Average bitrate per PDCH for non-Edge capable terminals in this cell
Coding rules --
Mandatory rules RMIN_GPRS <= R_AVERAGE_GPRS
Recommended R_AVERAGE_GPRS shall not be set to a bitrate higher than the useful bitrate corresponding to MAX_GPRS_CS (e.g. if MAX_GPRS_CS = CS2 => R_AVERAGE_GPRS
rules shall not be higher than 12kbps).
External This parameter represents the average bit rate that is targeted, per PDCH, in the cell with respect to the cell radio planning. It is recommended not to set this bit rate
comment higher than the average measured bit rate in the cell.
The default value corresponds to CS-2.
The max value corresponds to CS-4.
Internal comment --
Logical RA_CAPABILITY_UPDATE_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI RA_CAPABILITY_UPDATE_RETRIES Sub-syste MFS Cell Type No
Definition Maximum number of repetition of Radio Access capability in case of no answer from SGSN at T5 expiry.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RA_CODE (MFS) B11 Yes B12 Yes
name TRX nb No
HMI Routing Area Code for GPRS Sub-syste MFS Cell Type No
Definition Routing Area Code.
Rec ref. 3GPP TS 04.60 Domai GPRS Min value -1 Coded Min -1
Coding rules 0...255 (significant value: 3GPP TS 04.60)
other values: external or unknown cell
Mandatory rules - Equal to RA_CODE (BSC)
- A couple of mate extended cells (Extended inner + extended outer) shall have the same RA_CODE when they are PS capable
Recommended --
rules
comment
Internal comment The special value of "-1" means that the RA code has still not been valued by the network provider or that the MFS shall set the SAME_RA_AS_SERVING_CELL field
to 0.
Logical RA_CODE(n) B11 Yes B12 Yes
name TRX nb No
HMI Routing Area Code for GPRS Sub-syste MFS Cell Type No
Definition Routing Area Code of neighbour cells.
Rec ref. 3GPP TS 04.60 Domai GPRS Min value -1 Coded Min -1
Coding rules 0...255 (significant value: 3GPP TS 04.60);
other values: external or unknown cell.
The special value of -1 means that the RA code has still not been valued by the network provider or that the MFS shall set the SAME_RA_AS_SERVING_CELL field to
0.
Mandatory rules --
Recommended If i) the target and serving cells belong to different PLMNs and ii) the RAC and LAC of the target cell are equal to the RAC and LAC of the serving cell, and iii) there is a
rules PBCCH established in the serving cell, and iv) a cell reselection adjacency link is defined between the serving cell and the target cell, then it is recommended to set
the RA_CODE to -1. Otherwise, the MFS considers that the serving cell and the target cell belong to the same routing area when setting the
SAME_RA_AS_SERVING_CELL field in the 04.60 PACKET SYSTEM INFORMATION TYPE 3/3bis messages.
External The special value of -1 means that the RA code has still not been valued by the operator or that the routing area of the serving cell is different from the routing area of
comment the target cell.
Internal comment This parameter is used when there is a PBCCH in the serving cell.
Logical RA_RESELECT_HYSTERESIS B11 Yes B12 Yes
name TRX nb No
HMI RA_RESELECT_HYSTERESIS Sub-syste MFS Cell Type No
Definition This parameter indicates in both STANDBY and READY state the additional hysteresis which applies when selecting a cell in a new Routing Area.
Coding rules step size = 2 dB, Coded on 3 bits. 000=0 dB, 001=2 dB, ...111=14 dB
Mandatory rules --
Recommended --
rules
External --
comment
Logical RACH_TA_FILTER (MFS) B11 Yes B12 Yes
name TRX nb No
HMI RACH/PRACH_TA_FILTER Sub-syste MFS Cell Type No
Definition Timing Advance threshold for CHANNEL REQUIRED and PACKET CHANNEL REQUEST filtering.
Coding rules 64: no filtering
Mandatory rules Equal to RACH_TA_FILTER (BSC)
Recommended Disable the filtering for extended cells.

rules
External One unit corresponds to a distance of about 550m. CHANNEL REQUIRED or PACKET CHANNEL REQUEST messages with Timing Advance greater or equal to
comment RACH_TA_FILTER are discarded.
Internal comment --
Logical RADIOLINK_TIMEOUT (MFS) B11 Yes B12 Yes
name TRX nb No
HMI RADIOLINK_TIMEOUT Sub-syste MFS Cell Type No
Definition Initial value of MS counter for radio link supervision.
This applies to non AMR calls or to AMR (NB or WB) calls for which Repeated SACCH and Repeated DL FACCH are activated.
Mandatory rules Equal to RADIOLINK_TIMEOUT (BSC)
Recommended --
rules
External --
comment
Logical RATE_RED B11 Yes B12 Yes
name TRX nb No
HMI rateRed Sub-syste MFS Cell Type No
Definition Rate reduction of the bvc leak rate (DL flow control with the SGSN) to apply when the first level of PMU buffer congestion is reached in a given PMU (buffers used for
LLC PDU storage, cf. the GPU_BUFFER_CONGESTION_THR_1_XOFF parameter).
Category System (CST) OMC-R access None (not in DLS) Type Number Unit %
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Hardcoded in RRM
Logical RAW_BITRATE_CS1 B11 Yes B12 Yes
name TRX nb No
HMI RAW_BITRATE_CS1 Sub-syste MFS Cell Type No
Definition Raw bit rate corresponding to CS1, used for FC1 flow control algorithm in RLC (IP mode only).
Category System (CST) OMC-R access None (not in DLS) Type Number Unit kbit/s
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical RAW_BITRATE_MCS1 B11 Yes B12 Yes
name TRX nb No
HMI RAW_BITRATE_MCS1 Sub-syste MFS Cell Type No
Definition Raw bit rate corresponding to MCS1, used for FC1 flow control algorithm in RLC (IP mode only).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Resume_retries B11 Yes B12 Yes
name TRX nb No
HMI Resume_retries Sub-syste MFS Cell Type No
Definition Maximum number of retries to send a Resume message to the SGSN.
Coding rules --
Mandatory rules --
Recommended BSSGP_T4 < T_GPRS_Resume/ (Resume_retries+1)

rules
External --
comment
Internal comment --
Logical RLC_FC1_BUFFER_SEND_THRES B11 Yes B12 Yes
name TRX nb No
HMI RLC_FC1_BUFFER_SEND_THRES Sub-syste MFS Cell Type No
Definition Threshold in RLC to request IPGCH to send DL FC1 flow control message to PCC, in case of low level of the RLC buffer. It is expressed as a number of 20 msec periods.
Coding rules Step size = 1, coded on 1 byte.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via IPGCH.
Logical RLC_FC1_THROUGHPUT_CHANGE_THRES B11 Yes B12 Yes
name TRX nb No
HMI RLC_FC1_THROUGHPUT_CHANGE_THRES Sub-syste MFS Cell Type No
Definition Threshold in RLC to request IPGCH to send downlink FC1 flow control message to PCC, in case of important change of the expected throughput (through an increase or
decrease of ther (M)CS and/or number of allocated PDCHs)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS.
Logical RLC_TARGET_BUFFER B11 Yes B12 Yes
name TRX nb No
HMI RLC_TARGET_BUFFER Sub-syste MFS Cell Type No
Definition Target filling level of the RLC buffer associated to each DL TBF. This parameter is used by the FC1 downlink flow control mechanism between RRM-PCC and RLC layers.
This parameter is expressed as a number of 20 msec periods.

Category Network (CDE) OMC-R access None (DLS) Type Number Unit block period
Mandatory rules --
Recommended - T_IPGCH_ACK_DL/20 <= 31 - RLC_TARGET_BUFFER (linked to the max. value of 31 for the Buffer Filling Level IEs on IPGCH interface).
rules - RLC_TARGET_BUFFER <= 27
External Corresponds to number of time-periods (20 ms) worth of data.
comment
Internal comment - IPGCH simulations did not show the need to a different value of RLC_TARGET_BUFFER, even when the round trip delay between the MFS and the BTS is high
(typically in case of BTS to MFS transport over satellite (round_trip_delay >= 500ms)).
Logical RMIN_EGPRS B11 Yes B12 Yes
name TRX nb No
HMI RMIN_EGPRS Sub-syste MFS Cell Type No
Definition Minimal bitrate per PDCH for Edge capable terminals in this cell (at 95 % or 90% confidence level or less %, depending on tolerable risk)
Coding rules --
Mandatory rules RMIN_EGPRS <= R_AVERAGE_EGPRS
Recommended If EN_STREAMING = 1 and EN_CS_ADAPTATION_ACK = False then the following condition must be respected: RMIN_EGPRS <= useful bitrate corresponding to min
rules (TBF_UL_INIT_MCS, TBF_DL_INIT_MCS). Otherwise the streaming PFC can be downgraded to the Defaut Best Effort ABQP.
R_MIN_EGPRS shall not be set to a bitrate higher than the useful bitrate corresponding to Max_EGPRS_MCS. If the above recommended rule is not fulfilled, then some
RT PFCs can be accepted by the BSS whereas it will not be possible to handle their associated GBR. This may result in RT PFC downgrades to Best Effort.
External This parameter is used to provide a guaranted Bit rate of streaming PFC for Edge capable MS, in the worst case radio condition. It should be set appropriately with
comment respect to the cell radio planning.
The default value corresponds to a bitrate between MCS-4 and MCS-5.
The max value corresponds to MCS-9.
Internal comment The default value corresponds to the minimum bitrate to accept a GBR 64Kb/s with the following conditions : MS multislot class = 4+1, MAX_PDCH_HIGH_LOAD =4
Logical RMIN_GPRS B11 Yes B12 Yes
name TRX nb No
HMI RMIN_GPRS Sub-syste MFS Cell Type No
Definition Minimal bitrate per PDCH for non-Edge capable terminals in this cell cell (at 95 % or 90% confidence level or less, depending on tolerable risk)
Coding rules --
Mandatory rules RMIN_GPRS <= R_AVERAGE_GPRS
Recommended If EN_STREAMING = 1 and EN_CS_ADAPTATION_ACK = False then the following condition must be respected: RMIN_GPRS <= useful bitrate corresponding to min
rules (TBF_UL_INIT_CS, TBF_DL_INIT_CS). Otherwise the streaming PFC can be downgraded to the Defaut Best Effort ABQP.
R_MIN_GPRS shall not be set to a bitrate higher than the useful bitrate corresponding to Max_GPRS_CS. If the above recommended rule is not fulfilled, then some RT
PFCs can be accepted by the BSS whereas it will not be possible to handle their associated GBR. This may result in RT PFC downgrades to Best Effort.
External This parameter is used to provide a guaranted Bit rate of streaming PFC for Non Edge capable MS, in the worst case radio condition. It should be set appropriately
comment with respect to the cell radio planning.
The default value corresponds to CS-1.
The max value corresponds to CS-4.
Internal comment --
Logical round_trip_delay B11 Yes B12 Yes
name TRX nb No
HMI Round trip delay PMU-MS Sub-syste MFS Cell Type No
Definition Round trip delay between the PMU and a MS, in TDM and IP mode.
Coding rules step size=10 ms
Mandatory rules - T3192 + T_MAX_EXTENDED_UL + round_trip_delay < 5 sec

- If GPRS traffic is carried between BTS and PMU through satellite links (round_trip_delay >= 500ms), and Abis_transport_mode = 1 (IP) for the corresponding BT, then
EN_FAST_INITIAL_GPRS_ACCESS must be equal to enabled
Recommended --
rules
External The round-trip delay is used by the RRM layers. The OMC-R and the PCU also use this parameter to determine whether or not GPRS traffic is carried through Abis or
comment Ater satellite links as follows:
- If round_trip_delay < 500 ms, the OMC-R and the PMU consider that GPRS traffic is carried through Abis and Ater terrestrial links,
- If round_trip_delay >= 500 ms, the OMC-R and the PMU consider that GPRS traffic is carried through one satellite link: either through Abis satellite links or Ater
satellite links in case Abis_transport_mode = 0 (TDM); or through a satellite link between BTS and PMU in case Abis_transport_mode = 1 (IP).
When the GPRS traffic is carried through Abis or Ater satellite links in the serving cell, it is recommended to set the round_trip_delay parameter to [Delay due to
satellite (540 ms) + Delay due to PMU-MS link (160 ms)] = 700 ms.
Internal comment - ONLY used in the construction of other timers, the considered round trip delay is : output of RRM layer - MS - input of RRM layer. It shall take into account Abis
transmission delay (TDM transmission mode) or IPGCH transmission delay (IP transmission mode). The round trip delay shall not take into account RRBP delay at (MAC)
level.
In TDM mode, also used by RLC for several algorithms.
In TDM transmission mode, RRM provides RLC with the round_trip_delay MFS-MS parameter value.
- In case of Abis_transport_mode(MFS) modification (see BOP), the OMC cannot check the related mandatory rule at modification time; only a non blocking warning is
raised.
Logical round_trip_delay_bts_ms B11 Yes B12 Yes
name TRX nb No
HMI Round trip delay BTS-MS Sub-syste MFS Cell Type No
Definition Round trip delay between the PTU and a MS, in IP mode.
Coding rules step size=10 ms
Mandatory rules --
Recommended In IP mode, the operator shall ensure that T3192 + T_MAX_EXTENDED_UL + round_trip_delay_bts_ms < 5 sec.
rules
External --
comment
Internal comment In IP mode, used by RLC for several algorithms.
In IP transmission mode, RRM provides RLC with the round_trip_delay BTS-MS parameter value.
The round trip delay BTS-MS shall not take into account RRBP delay at (MAC) level.
Logical RR_ALLOC_PERIOD (MFS) B11 Yes B12 Yes
name TRX nb No
HMI RR_ALLOC_PERIOD (MFS) Sub-syste MFS Cell Type No
Definition This parameter allows to tune the time between two sendings of the BSCGP RR Allocation Indication messages.
Coding rules --
Mandatory rules Equal to RR_ALLOC_PERIOD (BSC)
Recommended --
rules
External --
comment
Internal comment This parameter is used by MFS in the defensive mechanism for radio resource management to increment internal variables.
Logical RXLEV_ACCESS_MIN (MFS) B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_ACCESS_MIN Sub-syste MFS Cell Type No
Mandatory rules RXLEV_ACCESS_MIN (MFS) = RXLEV_ACCESS_MIN (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical RXLEV_ACCESS_MIN(n)(MFS) B11 Yes B12 Yes
name TRX nb No
HMI RXLEV_ACCESS_MIN Sub-syste MFS Cell Type No
Mandatory rules RXLEV_ACCESS_MIN(n)(MFS) = RXLEV_ACCESS_MIN(n)(BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical S B11 Yes B12 Yes
name TRX nb No
HMI S Sub-syste MFS Cell Type No
Definition Number of slots between 2 successive PACKET CHANNEL REQUEST.
Coding rules Possible values are : 12, 15, 20, 30, 41, 55, 76, 109, 163, 217 respectively binary coded : 0000, 0001, 0010,... ,1001
Mandatory rules --
Recommended When the GPRS traffic is carried through Abis or Ater terrestrial links, it is recommended to set S so that the time between two successive Packet Channel Request
rules messages is longer than 900 ms.
When the GPRS traffic is carried through Abis or Ater satellite links, it is recommended to set S so that the time between two successive Packet Channel Request
messages is longer than 1400 ms.
The number of slots belonging to the MSs PRACH between 2 successive Packet Channel Request messages is a random value drawn randomly for each new
retransmission with uniform distribution in the set (S, S+1, ...,S+T-1) with T = Tx_INT. The time in seconds between two Packet Channel Request messages is
determined as a function of S, TX_INT and of the BS_PRACH_BLKS parameter. BS_PRACH_BLKS defines the number of blocks statically allocated to the PRACH per
52 multiframe on each PCCCH.
External --
comment
Internal comment Needed when there is a PBCCH in the cell.
Logical S_BECN B11 Yes B12 Yes
name TRX nb No
HMI S_BECN Sub-syste MFS Cell Type No
Definition Number of consecutive frames with BECN bit before congestion is stated.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical SAGI_GATEWAY_IP_ADDRESS_1 B11 Yes B12 Yes
name TRX nb No
HMI SAGI_GATEWAY_IP_ADDRESS_1 Sub-syste MFS Cell Type No
Definition IP address (on sub-network 1 in the MFS) of the external router used as gateway towards the GPS server.
Category System (CST) OMC-R access None (DLS) Type IP address Unit None
Coding rules Coded on 32 bits (IP v4).
RuleTo convert the IP address into decimal: Each sub number of the IP addresse is coded on a byte (8 bits). then the 4 sub numbers are concatenated
default: value corresponding to IP address 1.1.1.10
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Following addresses are already used within MFS sub-network 1 and can not set as IP address of the external router in sub-network 1: 1.1.1.x, with x = 1, 2, 30-31,
50-65, 150-165, 100, 20
Logical SAGI_GATEWAY_IP_ADDRESS_2 B11 Yes B12 Yes
name TRX nb No
HMI SAGI_GATEWAY_IP_ADDRESS_2 Sub-syste MFS Cell Type No
Definition IP address (on sub-network 2 in the MFS) of the external router used as gateway towards the GPS server.
RuleTo convert the IP address into decimal: Each sub number of the IP addresse is coded on a byte (8 bits). then the 4 sub numbers are concatenated
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Following addresses are already used within MFS sub-network 2 and can not set as IP address of the external router in sub-network 2: 2.2.2.x, with x = 1, 2, 30-31,
50-65, 150-165, 100, 200
Logical SAGI_GPS_SERVER_LOCAL_IP_ADDRESS B11 Yes B12 Yes
name TRX nb No
HMI SAGI_GPS_SERVER_LOCAL_IP_ADDRESS Sub-syste MFS Cell Type No
Definition Local IP address (within MFS sub-networks) of the GPS server.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The local IP address of the server must not belong to the addresses used within MFS sub-networks 1 and 2, i.e. it must be different from 1.1.1.x or 2.2.2.x.
Logical SAGI_TCP_DATA_TIMEOUT B11 Yes B12 Yes
name TRX nb No
HMI SAGI_TCP_DATA_TIMEOUT Sub-syste MFS Cell Type No
Definition Parameter used in the context of supervision of SAGI based on TCP keep alive mechanism. This timer controls the retransmission timeout for the sending of the individual
data segments.
Coding rules step size = 1 second
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SAGI_TCP_KEEP_ALIVE_INTERVAL B11 Yes B12 Yes
name TRX nb No
HMI SAGI_TCP_KEEP_ALIVE_INTERVAL Sub-syste MFS Cell Type No
Definition Parameter used in the context of supervision of SAGI based on TCP keep alive mechanism. This timer determines the interval separating keep alive retransmissions until a
response is received. Once a response is received, the delay until the next keep alive transmission is again controlled by the value of this timer. The connection will be
aborted after the number of retransmissions specified by SAGI_TCP_MAX_DATA_RETRANS have gone unanswered.
Coding rules step size = 1 second
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SAGI_TCP_MAX_DATA_RETRANS B11 Yes B12 Yes
name TRX nb No
HMI SAGI_TCP_MAX_DATA_RETRANS Sub-syste MFS Cell Type No
Definition Parameter used in the context of supervision of SAGI based on TCP keep alive mechanism. This parameter controls the number of times TCP will retransmit an individual
data segment before aborting the connection. The retransmission timeout is given by the parameter SAGI_TCP_DATA_TIMEOUT.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SAGI_TCP_PORT_NB B11 Yes B12 Yes
name TRX nb No
HMI SAGI_TCP_PORT_NB Sub-syste MFS Cell Type No
Definition The TCP port number used for opening and closing of a SAGI TCP connection.
Spec ref. SMLC / A-GPS Server Interface Coded Max 65535
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SCHEDULING_PRIORITY_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI SCHEDULING_PRIORITY_FACTOR Sub-syste MFS Cell Type No
Definition When computing the best candidate timeslot allocation for an NRT TBF, this factor enables to give a higher weight (PDCH capacity) to the already-established NRT TBFs
having a higher scheduling priority (combination of THP and of Precedence) than the TBF to be established or reallocated.
This factor will tend to avoid piling up several TBFs with different scheduling priorities on the same PDCHs, which would degrade the throughput of the low-priority TBFs.
Coding rules --
Mandatory rules --
Recommended --
rules
External The higher the value of T_MAX_FOR_TBF_SCHEDULING is, the higher the value of SCHEDULING_PRIORITY_FACTOR shall be, in order to avoid degrading the
comment throughput of the low-priority TBFs in a significant manner (if it is possible according to the available PDCHs in the cell).
Internal comment --
Logical SERVICE_CLASS_INDICATOR_IE B11 Yes B12 Yes
name TRX nb No
HMI SERVICE_CLASS_INDICATOR_IE Sub-syste MFS Cell Type No
Definition Provides the coded value used on Gb interface to indicate Instant message service PDU.
Coding rules - The value provided to the PMU is a decimal number.
- 153 is decimal = 99 hexadecimal
- The translation into hexadecimal will be preformed by the PMU software for Gb needs.
Mandatory rules --
Recommended --
rules
comment
Internal comment - 3GPP reserved value, provided by CMCC
Logical SGSN_IP_Address B11 Yes B12 Yes
name TRX nb No
HMI IP_Address Sub-syste MFS Cell Type No
Definition IP address of a SGSN IP endpoint, used in case of static configuration of Gb over IP interface.
IP address of a pre-configured SGSN IP endpoint, used in case of dynamic configuration of Gb over IP interface.
Category Site (CAE) OMC-R access Set by Create Type IP address Unit None
Mandatory rules - Each SGSN IP EndPoint (SGSN_IP_Address, SGSN_UDP_Port) must be unique per NSE.
- in case of static configuration, up to 16 SGSN IP endpoints can be defined per NSE.
- In case of dynamic configuration, only a single pre-configured SGSN IP endpoint can be defined per NSE.
Recommended The operator shall ensure that all the SGSN IP EndPoints (SGSN_IP_Address, SGSN_UDP_Port) of one NSE belong to the same SGSN. He shall also ensure that the
rules SGSN IP EndPoints (SGSN_IP_Address, SGSN_UDP_Port) of two different NSEs of the same GP/GPU belong to two different SGSNs.
External The BSS controls that each SGSN IP Endpoint (SGSN_IP_Address, SGSN_UDP_Port) is unique among all the ones of all the NSEs of one GP/GPU (relevant when
comment EN_GB_FLEX is enabled).
Internal comment In case of dynamic configuration, the single pre-configured SGSN IP endpoint is a MFS limitation
Logical SGSN_IP_ENDPOINT_MAX B11 Yes B12 Yes
name TRX nb No
HMI SGSN_IP_ENDPOINT_MAX Sub-syste MFS Cell Type No
Definition Maximum number of SGSN IP Endpoint per NSE (applicable to both static and dynamic configuration of the Gb over IP interface)
Coding rules --
Mandatory rules Not changeable after PCU system initialization.
Recommended --
rules
External --
comment
Internal comment --
Logical SGSN_OFFLOAD_STATE B11 Yes B12 Yes
name TRX nb No
HMI --- Sub-syste MFS Cell Type No
Definition State assigned to a given SGSN, connected to the MFS (Gbflex feature), for the load redistribution function. That function removes the off loaded SGSN from the list of
candidate SGSNs on BSS side.
Coding rules 0: off loaded
1: on loaded
Mandatory rules --
Recommended In a BSS in multi-GP/GPUs configuration, for a consistent behaviour of the Gbflex feature, all the NSEs, connected to the same SGSN, must have the same
rules SGSN_OFFLOAD_STATE.
External - Significant only if EN_GB_FLEX is enabled.
comment - If a SGSN server is in high load situation, the operator can avoid the SGSN to enter the overload situation through the update of that parameter to off loaded for all
the NSEs of all the BSSs connected to the concerned SGSN.
Parameter change: on going traffic is not disrupted. Change applied immediately after modification. The complete redistribution of the MS requires the same change
done on Core Network side too.
Internal comment - HMI name = the name of the button value, ie ONLOADED or OFFLOADED
Logical SGSN_UDP_Port B11 Yes B12 Yes
name TRX nb No
HMI Port_Number Sub-syste MFS Cell Type No
Definition UDP port number of a SGSN IP endpoint, used in case of static configuration of Gb over IP interface.
UDP port number of a pre-configured SGSN IP endpoint, used in case of dynamic configuration of Gb over IP interface.
Coding rules --
Mandatory rules - Each SGSN IP EndPoint (SGSN_IP_Address, SGSN_UDP_Port) must be unique per NSE.
- in case of static configuration, up to 16 SGSN IP endpoints can be defined per NSE.
- In case of dynamic configuration, only a single pre-configured SGSN IP endpoint can be defined per NSE.
Recommended The operator shall ensure that all the SGSN IP EndPoints (SGSN_IP_Address, SGSN_UDP_Port) of one NSE belong to the same SGSN. He shall also ensure that the
rules SGSN IP EndPoints (SGSN_IP_Address, SGSN_UDP_Port) of two different NSEs of the same GP/GPU belong to two different SGSNs.
External - Following IANA.org: Registered Ports are in the range 1024-49151 and Dynamic and/or Private Ports are those from 49152 through 65535 (ALU BSS ports are
comment taken in the private range, however SGSN ports taken in the registered ports are accepted by the ALU BSS).
- The MFS controls that each SGSN IP Endpoint (SGSN_IP_Address, SGSN_UDP_Port) is unique among all the ones of all the NSEs of one GP/GPU (relevant when
EN_GB_FLEX is enabled).
Internal comment In case of dynamic configuration, the single pre-configured SGSN IP endpoint is a MFS limitation
Logical SGSN_WEIGHT B11 Yes B12 Yes
name TRX nb No
HMI SGSN_WEIGHT Sub-syste MFS Cell Type No
Definition Weight assigned to a SGSN, connected to the MFS (Gbflex feature), for the load balancing function. A high value is to be associated to a high capacity SGSN, because it
will be chosen more often than a SGSN with a lower weight (e.g. a SGSN with weight = 10 will be chosen twice as often as a SGSN with weight = 5).
Coding rules --
Mandatory rules --
Recommended In a BSS in multi-GP/GPUs configuration, for a consistent behaviour of the Gbflex feature, all the NSEs, connected to the same SGSN, must have the same
rules SGSN_WEIGHT. Same rule is to be extended to all the NSEs of all the BSSs belonging to a same pool area, and connected to the same SGSN.
External - Significant only if EN_GB_FLEX is enabled
Internal comment --
Logical SGSNR B11 Yes B12 Yes
name TRX nb No
HMI SGSNR Sub-syste
MFS Cell Type No
name InstanceBSS RMS No
Definition Year corresponding to the version of ETSI/3GPP recommendations used to implement SGSN software.
Rec ref. GSM 04.18 Domai GPRS Min value 0 Coded Min 0
Coding rules 0 = SGSN is release '98 or older; 1 = SGSN is release '99 onwards
Mandatory rules EN_GB_FLEX is enabled only if SGSNR = 1.
Recommended --
rules
External - Any modification of the parameter leads to reset autonomously all the PMUs connected to this BSS.
comment - Default value depends on SGSN type
Internal comment --
Logical SIG_BVCI B11 Yes B12 Yes
name TRX nb No
HMI SIG BVCI Sub-syste MFS Cell Type No
Definition Signalling BVCI value.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SIGNALLING_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI SIGNALLING_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for the pre-defined Signalling PFC.
Coding rules --
Mandatory rules The priority set for signalling should always be higher than for data traffic
Recommended --
rules
External Signalling is, by default, handled as top priority. The default value of the parametercorresponds to the highest priority.
comment
Internal comment --
Logical SLOW_MOVING_FACTOR B11 Yes B12 Yes
name TRX nb No
HMI SLOW_MOVING_FACTOR Sub-syste MFS Cell Type No
Definition Number of times one SGSN is used, once selected by the Node Selection Function.
Coding rules ---
Mandatory rules --
Recommended There is no advantage to define different values for different BSSs.

rules
comment
Internal comment - The MFS instance is not supported for this kind of MFS parameter (BSS is the biggest possible one)
Logical SMS_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI SMS_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for the pre-defined SMS PFC.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SNS_CONFIG_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI SNS_CONFIG_RETRIES Sub-syste MFS Cell Type No
Definition Number of retry for the SNS-Config message
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SNS_SIZE_RETRIES B11 Yes B12 Yes
name TRX nb No
HMI SNS_SIZE_RETRIES Sub-syste MFS Cell Type No
Definition Number of retry for the SNS-Size message
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical SPGC_CCCH_SUP (MFS) B11 Yes B12 Yes
name TRX nb No
HMI SPGC_CCCH_SUP (MFS) Sub-syste MFS Cell Type No
Definition This flag indicates the support of split pg cycle on CCCH by the network.
Coding rules 0: split pg cycle on CCCH not supported in the cell
1: split pg cycle on CCCH supported in the cell
Mandatory rules Equal to SPGC_CCCH_SUP (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical STREAMING_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI STREAMING_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for the Streaming PFC
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Suspend_retries B11 Yes B12 Yes
name TRX nb No
HMI Suspend_retries Sub-syste MFS Cell Type No
Definition Maximum number of retries to send a Suspend message to the SGSN.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_ACK_WAIT B11 Yes B12 Yes
name TRX nb No
HMI T_ACK_WAIT Sub-syste MFS Cell Type No
Definition Timer defining the maximum time to wait for an MS answer (i.e. Packet Control Ack or beginning of an UL TBF) to a network solicitation sent on PACCH/DL when the MS is
in PTM, or on PPCH when the MS is in PIM and non-DRX mode, or on main DCCH when the MS is in dedicated mode.
Mandatory rules --
rules - T_ack_wait = 1200 ms if GPRS traffic is carried through Abis and Ater terrestrial links in all the cells of the PCU.
- T_ack_wait = 1700 ms if GPRS traffic is carried either through Abis satellite links or Ater satellite links in at least one cell of the PCU and Abis_transport_mode = 0
(TDM).
- T_ack_wait = 2300 ms if GPRS traffic between BTS and PCU is carried through satellite link (round_trip_delay >= 500ms) in at least one cell of the PCU and
Abis_transport_mode = 1 (IP) for all the corresponding BTS.
External --
comment
Internal comment T_ACK_WAIT <= T_ACK_WAIT_DRX_PCCCH
As T_ACK_WAIT is not shown to the operator, the OMC is not able to verify the following rules. Despite of this fact, these rules (expressed in ms) are essential and
shall be verified when setting the default values:
1. T_ACK_WAIT > T3168 + MAX_UL_TBF_SPDCH*20 + 60
2. T_ACK_WAIT > T_queuing_PACCH + round_trip_delay + MAX_UL_TBF_SPDCH*20 + 60 (for UL two-phase access and UL access on concurrent DL TBF)
3. T_ACK_WAIT > T_queuing_PAGCH + round_trip_delay + MAX_UL_TBF_SPDCH*20 + 60 (for UL one-phase access on PCCCH)
4. T_ACK_WAIT > T_queuing_PPCH_non_DRX + round_trip_delay + 120 (for DL TBF establishment on PCCCH in non-DRX mode)
5. T_ACK_WAIT > T_queuing_PACCH + round_trip_delay + 120 (for DL TBF establishment on concurrent UL TBF or for fast DL TBF re-establishment).
The following parameters are used in the above formulae:
- T_queuing_PACCH: maximum queuing time expected on PACCH (~200 msec)
- T_queuing_PAGCH: maximum queuing time expected on PAGCH (<200 msec)
- T_queuing_PPCH_non_DRX: maximum queuing time expected on PPCH in non-DRX mode (<200 msec)
Logical T_ACK_WAIT_DRX_PCCCH B11 Yes B12 Yes
name TRX nb No
HMI T_ACK_WAIT_DRX_PCCCH Sub-syste MFS Cell Type No
Definition Timer defining the maximum time to wait for a MS answer (i.e. Packet Control Ack) to a network sollicitation sent on PPCH when the MS is in PIM and DRX mode.
Coding rules step size = 0.1 sec ; 0 = 0; 1 = 0.1;... ;100 = 10
Mandatory rules --
rules - T_ACK_WAIT_DRX_PCCCH = 2.5 s if GPRS traffic is carried through Abis and Ater terrestrial links in all the cells of the MFS,
- T_ACK_WAIT_DRX_PCCCH = 3 s if GPRS traffic is carried either through Abis satellite links or Ater satellite links in at least one cell of the MFS.
External --
comment
Internal comment T_ACK_WAIT <= T_ACK_WAIT_DRX_PCCCH
Logical T_AVG_T (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_AVG_T Sub-syste MFS Cell Type No
Definition Signal strength filter period for power control in packet transfer mode.
Mandatory rules Equal to T_AVG_T (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical T_AVG_W (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_AVG_W Sub-syste MFS Cell Type No
Definition Signal strength filter period for power control in packet idle mode.
Mandatory rules Equal to T_AVG_W (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical T_BA_CHANGE B11 Yes B12 Yes
name TRX nb No
HMI T_BA_CHANGE Sub-syste MFS Cell Type No
Definition Time during which no NC cell reselection can be triggered further to a change of the BCCH allocation.
Coding rules step size = 1s
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_BTS_LOAD_REPORT_WITH_TRANSITION B11 Yes B12 Yes
name TRX nb No
HMI T_BTS_LOAD_REPORT_WITH_TRANSITION Sub-syste MFS Cell Type No
Definition Period with which a given TRE module reports its SCP CPU load to RRM, in case a transition of CPU load state (from a higher to a lower congestion state) took place since
the last reporting.
Mandatory rules T_BTS_LOAD_REPORT_WITH_TRANSITION < T_BTS_LOAD_REPORT_WITHOUT_TRANSITION
Recommended --
rules
External --
comment
Internal comment - The highest the T_BTS_LOAD_REPORT_WITH_TRANSITION value, the longest the phases during which RRM might block some TBF traffic on the TRXs in case of
high SCP CPU load. In particular, those phases (during which some TBF traffic is blocked by RRM) can happen after an SCP CPU load peak (i.e. a load increase
followed by a load decrease in a short period of time, see the BTS_LOAD_FORGETTING_FACTOR parameter to tune the likelihood for an SCP CPU load peak to be
notified to RRM).
- The lowest the T_BTS_LOAD_REPORT_WITH_TRANSITION value, the highest the PMU-PTU interface load (see also the
T_BTS_LOAD_REPORT_WITHOUT_TRANSITION parameter).
Logical T_BTS_LOAD_REPORT_WITHOUT_TRANSITION B11 Yes B12 Yes
name TRX nb No
HMI T_BTS_LOAD_REPORT_WITHOUT_TRANSITION Sub-syste MFS Cell Type No
Definition Period with which a given TRE module reports its SCP CPU load to RRM, in case no transition of CPU load state took place since the last reporting.
Mandatory rules T_BTS_LOAD_REPORT_WITH_TRANSITION < T_BTS_LOAD_REPORT_WITHOUT_TRANSITION
Recommended --
rules
External --
comment
Internal comment - The highest the T_BTS_LOAD_REPORT_ WITHOUT_TRANSITION value, the fewer the notications sent to RRM (which could be useful for debug).
- The lowest the T_BTS_LOAD_REPORT_ WITHOUT_TRANSITION value, the highest the PMU-PTU interface load.
Logical T_CANDIDATE_TBF_REALLOC B11 Yes B12 Yes
name TRX nb No
HMI T_CANDIDATE_TBF_REALLOC Sub-syste MFS Cell Type No
Definition Timer value controlling the time duration between successive resource reallocation attempts for candidate MSs (triggers T3 and T4).
In a given cell, at each expiry of the T_CANDIDATE_TBF_REALLOC timer :
- up to N_MAX_PERIODIC_REALLOC_ATTEMPT_T4 T4 reallocation attempts are performed,
- up to N_MAX_PERIODIC_REALLOC_ATTEMPT_T4 T4 reallocations are performed,
- up to 2 x N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 T3 reallocation attempts are performed,
- up to 2 x N_MAX_PERIODIC_REALLOC_SUCCESS_T3 T3 reallocations are performed.
This timer controls also the periodic evaluation of the PS radio congestion status of a cell, where GPRS_MULTISLOT_CLASS_CONG_IM is enabled.
Coding rules step size = 1 sec; value 1 means 1 sec; value 2 means 2 sec, and so on
Mandatory rules --
Recommended T_GCH_INACTIVITY > T_CANDIDATE_TBF_REALLOC in all the cells of the BSS.

rules This constraints avoids as much as possible that some GCHs are released and reestablished again some moments later. This way, the T3 and T4 reallocations can
benefit from the GCHs which are currently unused, but still established.
External This parameter, together with the parameters N_MAX_PERIODIC_REALLOC_ATTEMPT_T3, N_MAX_PERIODIC_REALLOC_SUCCESS_T3 and
comment N_MAX_PERIODIC_REALLOC_ATTEMPT_T4, allows to :
- to control the reactivity of the BSS with regards to T3 and T4 reallocations,
- and to control the extra CPU load generated by T3 and T4 reallocation attempts (the lowest the value of T_CANDIDATE_TBF_REALLOC, the highest the generated
CPU load).
Internal comment --
Logical T_CHANGE_RLC_MODE B11 Yes B12 Yes
name TRX nb No
HMI T_CHANGE_RLC_MODE Sub-systeMFS Cell Type No
Definition Timeout value for RLC mode modification procedure on downlink path when DL LLC PDUs with different RLC (acknowledged and unacknowledged) are simultaneously
received by the PCU.
Coding rules Step size : 100 ms
Mandatory rules --
Recommended --
rules
External A value of 0 is required in order to guarantee no de-sequencing of LLC PDUs within the same LLC SAPI. A value different from 0 will lead to possible de-sequencing
comment at LLC level; however, the SNDCP layer within the MS should de-multiplex the data flows operating in different RLC modes towards different NSAPIs. It should
therefore not impact the behaviour of layers above RLC/MAC when the value is different from 0; it is however recommended in order to minimise the risks.
Internal comment --
Logical T_CONFIG_TBF B11 Yes B12 Yes
name TRX nb No
HMI T_CONFIG_TBF Sub-syste MFS Cell Type No
Definition Supervision timer for TBF context configuration in a TRX
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This value of timer shall be used when the traffic is carried through Abis or Ater terrestrial links. When the traffic is carried through Abis or Ater satellite links, RLC
shall add 420 ms to this value of timer.
Logical T_delay_gch B11 Yes B12 Yes
name TRX nb No
HMI T_delay_gch Sub-syste MFS Cell Type No
Definition Delay for GCH re-establishment after a GCH establishment failure.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Gives the delay between 2 GCH establishment attempts.
Logical T_DELAY_PAGING_EXT B11 Yes B12 Yes
name TRX nb No
HMI T_DELAY_PAGING_EXT Sub-syste MFS Cell Type No
Definition Time to delay the specific paging procedure when the MS didnt answer to any Packet DL Assignment message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Lets define : A = (T_ul_assign_ccch or T_dl_assign_ccch, depending on the Air channel, AGCH or PCH, used to send the Immediate Assignment message) *
(Max_retrans_DL+1).
The T_DELAY_PAGING_EXT value should be configured to last, at least, the time up to the T3190 expiry on the MS side plus an additional margin (around 2.5sec
according to the MS Paging Group) to give the time to the MS to switch on the CCCH and receive the Paging Request message, Illustration with T3190n = 5sec and
T_dl_assign_ccch = 1.4sec :
Ex1 : Max_retrans_DL = 2
A=(2+1)*1.4=4.2sec, then T_DELAY_PAGING_EXT >= 5-4.2+2.5>=3.3
A=(3+1)*1.4=5.6sec, then T_DELAY_PAGING_EXT >= 0+2.5>=4.1
A=(4+1)*1.4=7.0sec, then T_DELAY_PAGING_EXT >= (5-1.4)+2.5>=7.1
The default value 5.5 sec is an average value.
Logical T_DELAYED_DL_TBF_POL B11 Yes B12 Yes
name TRX nb No
HMI T_DELAYED_DL_TBF_POL Sub-syste MFS Cell Type No
Definition This timer controls the polling period on the downlink when a TBF is in delayed release mode. When NC2 is activated for an MS, the actual polling period depends also on
NC_REPORTING_PERIOD_T.
Coding rules step size = 20msec
Mandatory rules --
Recommended --
rules
External It controls the occurrence of polling requests sent to a Mobile Station, the downlink TBF of which is in delayed release mode. Its value shall ensure that the Mobile
comment Station is granted PACCH/U often enough to be able to request establishment of an uplink TBF, without loading too much the uplink PDCH. Queuing time on the PDCH to
send the polling request (contained in an RLC data block filled with LLC Dummy UI Commands) shall also be considered.
Internal comment The Min value of 60 ms is needed to ensure that T_DELAYED_DL_TBF_POL >= T_MIN_POLL.
Logical T_DELAYED_DL_TBF_POL_INITIAL B11 Yes B12 Yes
name TRX nb No
HMI T_DELAYED_DL_TBF_POL_INITIAL Sub-syste MFS Cell Type No
Definition Time that the PCU shall wait before sending the first RLC data block containing only LLC Dummy UI command(s) after the last DL RLC data block has been sent, that
contains useful data.
Mandatory rules --
Recommended --
rules
External Because the last DL RLC data block is now sent with a polling request preferably 60 msec after the MS has received it, the MS may not have the time in 60 msec to
comment get the response from the upper layers. Then the MS will not include a channel request description for requesting uplink TBF establishment. Now, if the DL TBF enters
delayed release state, the next time the MS will have an opportunity for requesting such an uplink TBF establishment will be after T_DELAYED_DL_TBF_POL. Because
that time is quite long (200 msec by default), a specific timer is introduced for the first polling request.
Internal comment The Min value of 60 ms is needed to ensure that T_DELAYED_DL_TBF_POL_INITIAL >= T_MIN_POLL.
Logical T_Delayed_DL_TBF_Pol_UL B11 Yes B12 Yes
name TRX nb No
HMI T_Delayed_DL_TBF_Pol_UL Sub-syste MFS Cell Type No
Definition This timer defines the period of sending 'Dummy UI commands' in the delayed DL TBF release state, when there is an on-going UL TBF.
Coding rules step size = 0.1s
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_DELAYED_FINAL_PUAN B11 Yes B12 Yes
name TRX nb No
HMI T_DELAYED_FINAL_PUAN Sub-syste MFS Cell Type No
Definition This timer defines the duration of the delay introduced by the BSS to send the final Packet UL Ack/Nack message when releasing an UL TBF.
Coding rules step size : 100 ms ; 0 = 0 msec, 1 = 100 msec, 2 = 200 msec, etc
Mandatory rules --
Recommended --
rules
External - The feature delayed emission of the final Packet UL Ack/Nack can be inhibited by setting the value 0 to the parameter T_DELAYED_FINAL_PUAN. When the feature
comment is enabled, the timer duration should be long enough to let the server send its response to the uplink PDUs received from the MS, while remaining short enough in
order not to jeopardise the sending of further uplink PDUs by the MS.
- If GPRS traffic between one BTS and the PMU is carried through satellite link (round_trip_delay >= 500ms), and Abis_transport_mode = 1 (IP) for the concerned BTS,
and if T_delayed_Final_PUAN < 540ms then the MS will wait for a delay equal to Max (540ms, T_delayed_Final_PUAN). This is due to the delayed PMU-PTU
interworking when in IP mode (PMU side, PTU at BTS side).
Note: 540ms is the RTD with a satellite link.
Internal comment Coded value 0 is used in the MFS during the migration phase until completion of BSS radio re-synchronisation step. The feature delayed final Packet UL Ack/Nack is
therefore inhibited during this period; this behaviour is acceptable considering that it only leads to a degradation of QoS during this period.
For more details on the setting of this parameter, refer to the memo Abis or Ater interface over IP over satellite (B11) ref 208123 v5
Logical T_dl_assign_ccch B11 Yes B12 Yes
name TRX nb No
HMI T_GPRS_assign_PCH Sub-syste MFS Cell Type No
Definition Maximum emission duration of an Immediate Assignment message on PCH aimed at establishing a downlink TBF.
Coding rules step size : 0.1sec
Mandatory rules T_GPRS_assign_pch parameters is computed by the OMC as follows:
BS_PA_MFRMS / T_GPRS_assign_pch (ms) if round_trip_delay < 500 ms / T_GPRS_assign_pch (ms) if round_trip_delay >= 500 ms
2/1200/1600
3/1200/1600
4/1200/1600
5/1400/2000
6/1600/2200
7/2000/2600
8/2200/2800
9/2400/3000
Recommended --
rules
External --
comment
Internal comment The retransmission period of the Packet DL Assignment messages on PACCH is computed by the MFS as follows:
T_GPRS_assign_pch / (Max_GPRS_assign_pch_retrans + 1).
As the timer accuracy in the MFS is 50 ms, it is recommended to set T_GPRS_assign_pch so that the period of retransmission of the Packet Downlink Assignment
messages on PACCH, i.e. T_GPRS_assign_pch / (Max_GPRS_assign_pch_retrans + 1), is a multiple of 50 ms.
In order not to unnecessary load the PCH queue, it is recommended to set T_PDA = T_GPRS_assign_pch.
The T_GPRS_assign_PCH parameter is not displayed to the O&M user.
Logical T_DL_EGPRS_MeasReport B11 Yes B12 Yes
name TRX nb No
HMI T_DL_EGPRS_MeasReport Sub-syste MFS Cell Type No
Definition Time period to request for an EGPRS Packet Downlink Ack/Nack with measurements.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_DL_GPRS_MeasReport B11 Yes B12 Yes
name TRX nb No
HMI T_DL_GPRS_MeasReport Sub-syste MFS Cell Type No
Definition Time period to request for a Packet Downlink Ack/Nack with measurements.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_DSP_LOAD_REPORT B11 Yes B12 Yes
name TRX nb No
HMI T_DSP_LOAD_REPORT Sub-syste MFS Cell Type No
Definition Period with which a given DSP reports its CPU load to RRM
Rec ref. None Domai GPRS Min value 0,1 Coded Min 1
Mandatory rules --
Recommended --
rules
comment
Internal comment - The highest the T_DSP_LOAD_REPORT value, the longest the phases during which RRM blocks some TBF traffic (on the TRXs mapped onto the concerned DSP) will
be in case of high DSP CPU load. In particular, those phases (during which some TBF traffic is blocked by RRM) can happen after a DSP CPU load peak (i.e. a load
increase followed by a load decrease in a short period of time) has occurred (cf. The DSP_LOAD_FORGETTING_FACTOR parameter to tune the likelihood for a DSP
CPU load peak to be notified to RRM).
- the lowest the T_DSP_LOAD_REPORT value, the highest the PMU-PTU interface load.
Logical T_DTM_ASSIGN B11 Yes B12 Yes
name TRX nb No
HMI T_DTM_ASSIGN Sub-syste MFS Cell Type No
Definition Timer monitoring the establishment of an UL or a DL TBF on main DCCH for Dual Transfer Mode.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_EXTENDED_UL_TBF_FAST_POL B11 Yes B12 Yes
name TRX nb No
HMI T_EXTENDED_UL_TBF_FAST_POL Sub-syste MFS Cell Type No
Definition Scheduling period for an uplink TBF which is in extended TBF mode and in normal fast scheduling conditions.
Mandatory rules --
Recommended T_EXTENDED_UL_TBF_FAST_POL should be set to a value strictly inferior to T_EXTENDED_UL_TBF_POL so as to take benefit from the normal fast scheduling mode.
rules
External - This parameter is relevant only if EN_EXTENDED_UL_TBF and EN_FAST_USF_UL_EXTENDED are both enabled.
comment - The scheduling scheme can be changed during full fast USF scheduling phases (see EN_FULL_FAST_USF_UL_EXTENDED).
Internal comment --
Logical T_EXTENDED_UL_TBF_POL B11 Yes B12 Yes
name TRX nb No
HMI T_EXTENDED_UL_TBF_POL Sub-syste MFS Cell Type No
Definition Scheduling period for an uplink TBF which is in extended TBF mode not in normal/full fast scheduling conditions.
Spec ref. GPRS radio interface - RRM sublayer Coded Max 25
Mandatory rules --
Recommended --
rules
External - This parameter is significant only if EN_EXTENDED_UL_TBF is enabled.
comment - If EN_FAST_USF_UL_EXTENDED is enabled, T_EXTENDED_UL_TBF_FAST_POL should be set to a value strictly inferior to T_EXTENDED_UL_TBF_POL so as to
take
benefit from the normal fast scheduling mode.
- The scheduling scheme can be changed during full fast USF scheduling phases (see EN_FULL_FAST_USF_UL_EXTENDED)
Internal comment TMO has customized this constant timer(probably starting from B10) with 120msec!!!
Logical T_FAST_DL_margin B11 Yes B12 Yes
name TRX nb No
HMI T_FAST_DL_margin Sub-syste MFS Cell Type No
Definition Value defining two times the transmission delay between RRM sub-layer and GCH layer.
Category System (CST) OMC-R access None (DLS) Type Number Unit ms
Coding rules step size: 5ms
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment ONLY used in the construction of other timers.
Logical T_flow_ctrl_cell B11 Yes B12 Yes
name TRX nb No
HMI T_FLOW_CTRL_CELL Sub-syste MFS Cell Type No
Definition Periodicity of emission of NM- FLOW-CONTROL-BVC message to SGSN.
Coding rules step size=1sec, 0 means infinite timer
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment T_flow_Ctr_cell >= C, defined in GSM 08.18. T_Mobil requires :"C configurable in a range 1-10 secondes, with step size 1 second"
Logical T_flow_ctrl_ms B11 Yes B12 Yes
name TRX nb No
HMI T_FLOW_CTRL_MS Sub-syste
MFS Cell Type No
name Instance
BSS RMS No
Definition Periodicity of emission of NM- FLOW-CONTROL-MS message towards the SGSN for GPRS and EGPRS Mobile Stations.
Coding rules step size=1sec, 0 means infinite timer
Mandatory rules --
Recommended --
rules
External 1) if T_Flow_Ctrl_MS is set to 0, then the MS flow control mechanism is inhibited;
comment 2) if T_Flow_Ctrl_MS has a non-null value, then "C< T_flow_ctrl_ms < Th". The parameters C and Th are defined in the 3GPP TS 08.18.
Internal comment If T_Flow_Ctrl_MS has a non-null value, then "C< T_flow_ctrl_ms < Th". The parameters C and Th are defined in the 3GPP TS 08.18. According to a T_Mobile
Requirement, the range of Th is 5 - 250 seconds with a step size of 1s.
Logical T_GCH_INACTIVITY B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_INACTIVITY Sub-syste MFS Cell Type No
Definition Timer to postpone the release of the "unused" transmission resources:
- in TDM mode: the GCHs of the M-EGCH link of a TRX (the condition for some GCHs of the M-EGCH link of a TRX to become "unused" is that some TBFs established on
that TRX were released); or
- in IP mode: the IPGCH TCP connection of a PTU (a TCP connection become "unused" when no other TRX mapped on that PTU needs it)
Mandatory rules --
Recommended T_GCH_INACTIVITY > T_CANDIDATE_TBF_REALLOC in all the cells of the BSS.

rules This constraints avoids as much as possible that some GCHs/TCP connection are released and reestablished again some moments later. This way, the T3 and T4 TBF
reallocations can benefit from the transmission resources which are currently unused, but still established.
If it is seen as an important goal to save Ater resources, a value of Ater_Usage_Threshold_Short_Data < 100% is coherent with a low value of the
T_GCH_INACTIVITY and T_GCH_INACTIVITY_LAST timers.
External In TDM mode, the setting of the T_GCH_INACTIVITY timer comes to make a trade-off between the GCH resource usage and the Telecom performance:
comment - The higher is the T_GCH_INACTIVITY timer, the higher is the GCH resource usage on the Ater interface.
- The higher is the T_GCH_INACTIVITY timer, the lower is the average duration of TBF establishments on (P)CCCH, especially if the GPRS traffic is carried through
satellite.
Internal comment - Evolium BTS :
A high value of T_GCH_INACTIVITY will block Ater nibbles for "unused" GCHs for a long time, which may induce Ater congestion situations (even if the intra-cell and
inter-cell GCH redistributions will tend to limit the effects of an Ater congestion). When an UL TBF is established, as no GCH is established by anticipation for the
subsequent concurrent DL TBF, the T_GCH_INACTIVITY value is not important. Thanks to the M-EGCH Statistical Multiplexing feature, it will be possible to establish the
subsequent concurrent DL TBF with all the timeslots allowed by its multislot class, and the DL TBF will use the GCHs of the M-EGCH link previously established for the
UL TBF.
Logical T_GCH_INACTIVITY_LAST B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_INACTIVITY_LAST Sub-syste MFS Cell Type No
Definition Timer to postpone the release of the last N_GCH_FAST_PS_ACCESS GCHs established (in TDM mode) or of the last TCP connection (in IP mode) in a cell, when the last
TBF has been released in the cell. There is no more (E)GPRS traffic in the cell, but keeping some transmission resources (GCHs or IPGCHs) established will be useful in
case of (E)GPRS traffic resumption in the cell (e.g. WAP, WEB).
Mandatory rules --
Recommended If it is seen as an important goal to save Ater resources, a value of Ater_Usage_Threshold_Short_Data < 100% is coherent with a low value of the
rules T_GCH_INACTIVITY and T_GCH_INACTIVITY_LAST timers.
External That timer is relevant only if EN_FAST_INITIAL_GPRS_ACCESS is disabled.
comment This parameter may also be used to ensure that the BSS reserves at least one transmission resource in the serving cell while the MS is engaged in a Web browsing
session.
In TDM mode, the setting of the T_GCH_INACTIVITY_LAST timer comes to make a trade-off between the transmission resource usage and the Telecom performance:
- The higher is the T_GCH_INACTIVITY_LAST timer, the higher is the resource usage on the Ater interface.
- The higher is the T_GCH_INACTIVITY_LAST timer, the lower is the average duration of TBF establishments on (P)CCCH, especially if the GPRS traffic is carried
through satellite links.
Internal comment --
Logical T_GSL_ACK (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_GSL_ACK_MFS Sub-syste MFS Cell Type No
Definition Supervision of MFS acknowledgements on BSCGP.
Mandatory rules --
Recommended T_GSL_ACK (MFS) > Abort interval in the MFS (set by TCP_MAX_RETRANS (MFS)
rules
External - The actual default value depends on the maximum number of GPUs that can be connected to one BSC:T_GSL_ACK = 1 second x MAX_GPU_PER_BSS.
comment - The purpose of the recommended rule is to ensure that failure at TCP level will be detected before failure at IPGSL level
Internal comment The actual default value (see external comment) is calculated by GOM (MFS control station) before being downloaded to a GPU.
Logical T_INITIAL_PDCH B11 Yes B12 Yes
name TRX nb No
HMI T_INITIAL_PDCH Sub-syste MFS Cell Type No
Definition Timer used to trigger the execution of a DL TBF request queued in the L4 list.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_IPGCH_ACK_DL B11 Yes B12 Yes
name TRX nb No
HMI T_IPGCH_ACK_DL Sub-syste MFS Cell Type No
Definition Timer controlling in the BTS the sending of acknowledgements on IPGCH interface (sending of DL acknowledgement messages from the BTS to the PCU).
Mandatory rules The operator must control that 6 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL > round trip delay between PCU and BTS. If that rule is not
Recommended - 6 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL >= IPGCHU_DELAY_HIGH_THRES_UL (because there are 6 polling request contexts per TRE
for
rules IPGCHU at BTS side).
- 3 x IPGCH_UL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_DL >= round trip delay between PCU and BTS (because there are 3 polling request contexts per
TRE
for IPGCHC at BTS side). If that recommendation were not followed (typically in case of BTS to PCU transport over satellite (round_trip_delay >= 500ms)), the IPGCHC
- T_IPGCH_ACK_DL/20 <= 31 - RLC_TARGET_BUFFER (linked to the max. value of 31 for the Buffer Filling Level IEs on IPGCH interface).
External --
comment
Logical T_IPGCH_ACK_UL B11 Yes B12 Yes
name TRX nb No
HMI T_IPGCH_ACK_UL Sub-syste MFS Cell Type No
Definition Timer controlling in the PCU the sending of acknowledgements on IPGCH interface (sending of UL acknowledgement messages from the PCU to the BTS).
Mandatory rules The operator must control that 6 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL > round trip delay between PCU and BTS. If that rule is not
Recommended - 6 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL => IPGCHU_DELAY_HIGH_THRES_DL (because there are 6 polling request contexts per PTU
for
rules IPGCHU at PCU side).
- 3 x IPGCH_DL_BW_CONTROL_REPEAT_RATE x T_IPGCH_ACK_UL >= round trip delay between PCU and BTS (because there are 3 polling request contexts per
PTU
for IPGCHC at PCU side). If that recommendation were not followed (typically in case of BTS to PCU transport over satellite (round_trip_delay >= 500ms)), the IPGCHC
External --
comment
Internal comment --
Logical T_IPGCHU_TIMEOUT B11 Yes B12 Yes
name TRX nb No
HMI T_IPGCHU_TIMEOUT Sub-syste
MFS Cell Type No
name Instance
MFS RMS No
Definition Timer after which the IPGCH connection is released in case of IPGCHU BE/GBR sending window blocked for a long time.
Mandatory rules In IP mode: PCC_UL_TBF_GUARD_TIMER < T_IPGCHU_TIMEOUT, because T_IPGCHU_TIMEOUT offers a defence at a higher level (IPGCH flow level) than
PCC_UL_TBF_GUARD_TIMER (TBF level).
Recommended T_IPGCHU_TIMEOUT > Abort interval in the PCU (set by TCP_MAX_RETRANS

rules
External The purpose of the recommended rule is to ensure that failure at TCP level will be detected before failure at IPGCH level.
comment
Internal comment - This timer is used to monitor the case where the oldest IPGCHU segment waiting to be acknowledged in the BE or GBR sending window has not changed for a long
time.
- This parameter is sent to the BTS via the IPGCH Init Req message.
Logical T_LCS_Delay_Tolerant B11 Yes B12 Yes
name TRX nb No
HMI T_LCS_Delay_Tolerant Sub-syste MFS Cell Type No
Definition SMLC timer to guard the calculation of the MS position (including the RRLP message exchange with the target MS) in case of a Delay Tolerant Location Request.
Recommended --
rules
External The timer is meaningful in the MFS when EN_LCS=1.
comment
Internal comment --
Logical T_LCS_Low_Delay B11 Yes B12 Yes
name TRX nb No
HMI T_LCS_Low_Delay Sub-syste MFS Cell Type No
Definition SMLC timer to guard the calculation of the MS position (including the RRLP message exchange with the target MS) in case of a Low Delay Location Request.
Recommended --
rules
comment
Internal comment --
Logical T_LCS_RESTART (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_LCS_RESTART_MFS Sub-syste MFS Cell Type No
Definition MFS timer to guard the response from the BSC in case of LCS Restart procedure (i.e. initialisation procedure).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_MAX_EXTENDED_UL B11 Yes B12 Yes
name TRX nb No
HMI T_MAX_EXTENDED_UL Sub-syste MFS Cell Type No
Definition Maximum duration of the extended uplink TBF phase
Mandatory rules T3192 + T_MAX_EXTENDED_UL + round_trip_delay < 5 sec
rules - between 1 sec and 2 sec if GPRS traffic is carried through Abis and Ater terrestrial links,
- between 1.5 sec and 2.5 sec if GPRS traffic is carried either through Abis satellite links or Ater satellite links.
If Abis_transport_mode = 1 (IP) for the concerned BTS, the operator shall ensure that T3192 + T_MAX_EXTENDED_UL + round_trip_delay_bts_ms < 5 sec.
External If GPRS traffic between BTS and PMU is carried through satellite link (round_trip_delay >= 500ms), and Abis_transport_mode = 1 (IP) for the corresponding BTS, the
comment duration of the extended UL phase in the MS is equal to this timer + 540ms. This is due to the delayed PMU-PTU interworking when in IP mode (PMU side, PTU at BTS
side).
Note: 540ms is the RTD with a satellite link.
Internal comment - The rate of abnormal UL TBF release due to N_POLLING_EUTM_LIMIT could increase when the value of T_MAX_EXTENDED_UL is increased
- For more details on the setting of this parameter, refer to the memo Abis or Ater interface over IP over satellite (B11) ref 208123 v5.
Logical T_MAX_FOR_MS_SYNCHRO B11 Yes B12 Yes
name TRX nb No
HMI T_MAX_FOR_MS_SYNCHRO Sub-systeMFS Cell Type No
Definition Timer per PDCH used to monitor the maximum time between the sending of two DL blocks which could be decoded by all the active mobiles having their PACCH supported
on the PDCH.
Mandatory rules - TRTS_PS > T_MAX_FOR_MS_SYNCHRO
Recommended - we can assume that a difference of 80ms between the two timers is sufficient to cope with possible delay on the MEGCH interface (in TDM mode)
rules
External --
comment
Internal comment The timer is started for a PDCH supporting the PACCH of at least one enabled DL or UL TBF, or an extended UL TBF. At the timer expiry, MAC is forced to send a DL
block in a (M)CS that could be decoded by all the MS allocated on this PDCH.
Logical T_MAX_FOR_TBF_SCHEDULING B11 Yes B12 Yes
name TRX nb No
HMI T_MAX_FOR_TBF_SCHEDULING Sub-syste MFS Cell Type No
Definition Maximum time between two scheduling of a given NRT TBF (either between two DL block requests for a NRT DL TBF, or between two UL blocks received for a given
NRT UL TBF).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Within PTU SW, some limits are hardcoded corresponding to the maximum numbers of DL or UL (E)GPRS TBF resources which can be possibly reached per Slave
PDCH (taking into account TBF allocations and a margin for TBF reallocations). Those hardcoded values are set to 16 in DL and 7 in UL (cf. MAC specification) and are
compatible with a max value of 300ms for the T_MAX_FOR_TBF_SCHEDULING parameter.
Logical T_MAX_RETRANS_DL B11 Yes B12 Yes
name TRX nb No
HMI T_MAX_RETRANS_DL Sub-syste MFS Cell Type No
Definition Duration between two retries of DL TBF establishment.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_MAX_STREAMING_BUFFERING B11 Yes B12 Yes
name TRX nb No
HMI T_MAX_STREAMING_BUFFERING Sub-syste MFS Cell Type No
Definition Time which multiplied by the GBR defines a buffer level above which we may consider the BSS failed to provide the GBR
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_MIN_POLL B11 Yes B12 Yes
name TRX nb No
HMI T_MIN_POLL Sub-syste MFS Cell Type No
Definition Minimum time between two consecutive polling requests.
Mandatory rules --
Recommended --
rules
External --
comment
Logical T_MS_CONTEXT_FLUSH_PERSISTENCE B11 Yes B12 Yes
name TRX nb No
HMI T_MS_CONTEXT_FLUSH_PERSISTENCE Sub-syste MFS Cell Type No
Definition This timer controls the duration during which a MS context is kept after receipt of a FLUSH-LL.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment All DL PDUs received for that MS while the timer is running are rerouted to the new cell if it is known. It also avoids trying to reestablish a DL TBF for a MS that has
just moved to a neighbour cell if data still arrive after the FLUSH.
Logical T_MS_Context_Lifetime B11 Yes B12 Yes
name TRX nb No
HMI T_MS_Context_Lifetime Sub-syste MFS Cell Type No
Definition This timer defines the maximum time during which an MS context is kept in the PCU for a Mobile Station in Packet Idle Mode.
Coding rules 0: the MS context is not maintained;
1..9999: the MS context is maintained 1..9999 seconds
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The MS context is kept during max(DRX_TIMER_MAX, T_MS_Context_Lifetime)
Logical T_NC_PING_PONG B11 Yes B12 Yes
name TRX nb No
HMI T_NC_PING_PONG Sub-syste MFS Cell Type No
Definition Time during which the ping-pong offset is applied.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_NC_REJ_CELL B11 Yes B12 Yes
name TRX nb No
HMI T_NC_REJ_CELL Sub-syste MFS Cell Type No
Definition Time during which a NC cell reselection is inhibited towards that cell due to a previous NC cell reselection failure on that cell.
Mandatory rules --
Recommended --
rules
External -
comment
Internal comment --
Logical T_NC_RXQUAL_VALID B11 Yes B12 Yes
name TRX nb No
HMI T_NC_RXQUAL_VALID Sub-syste MFS Cell Type No
Definition Timer used to control the validity of the NC RXQUAL averages at the beginning of a TBF.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment In the downlink direction, the timer is started on receipt of the first Packet Downlink Ack/Nack message of the DL TBF. While the timer is running, NC cell reselection
Cause PT3 cannot be triggered. At the expiry of the timer, Cause PT3 can be triggered.
In the uplink direction, the timer is started upon receipt of the first correctly decoded UL data block. While the timer is running, NC cell reselection Cause PT4 cannot be
triggered. At the expiry of the timer, Cause PT4 can be triggered.
Logical T_NC2_LOAD_RANKING B11 Yes B12 Yes
name TRX nb No
HMI T_NC2_LOAD_RANKING Sub-syste MFS Cell Type No
Definition Period of the cell load evaluation for the NC2 cell ranking process
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_NETWORK_RESPONSE_TIME B11 Yes B12 Yes
name TRX nb No
HMI T_NETWORK_RESPONSE_TIME Sub-syste MFS Cell Type No
Definition Maximum expected response time of a network server as seen from the PCU.
This timer is used in cells which are considered as not PS radio congested.
Mandatory rules - The max T_NETWORK_RESPONSE_TIME_IM of all the cells of the BSS <= T_NETWORK_RESPONSE_TIME
- The max T_NETWORK_RESPONSE_TIME_IM_CONG of all the cells of the BSS <= T_NETWORK_RESPONSE_TIME
- The max T_NETWORK_RESPONSE_TIME_CONG of all the cells of the BSS <= T_NETWORK_RESPONSE_TIME
Recommended --
rules
External 1) The response time corresponds to T1 T2 where T2 corresponds to the time at which a command is sent to the SGSN and T1 the time at which the response is
comment received on the PCU side. This command / response is e.g. the LLC PDU containing an FTP GET and the first LLC PDU starting the file transfer. It can also be the LLC
PDU containing an HTTP GET and the first LLC PDU starting the page download.
2) The value of this timer defines the duration of the Delayed DL TBF Release procedure. In case the servers to which the GGSN serving the PCU is connected are
not located at the same place, then the maximum server response time should be entered. However, note that the higher this timer is, the longer TBF releases will be
delayed and therefore the more resources are used up.
Internal comment This parameter can also be used for the extended UL TBF mode feature in a future release.
Logical T_NETWORK_RESPONSE_TIME_CONG B11 No B12 Yes
name TRX nb No
HMI T_NETWORK_RESPONSE_TIME_CONG Sub-syste MFS Cell Type No
Definition Maximum expected response time of a network server as seen from the PCU.
This timer is used in cells which are considered as PS radio congested.
0: the reduced delayed DL TBF in case of PS congested cell is disabled
Mandatory rules - T_NETWORK_RESPONSE_TIME_CONG <= T_NETWORK_RESPONSE_TIME
Recommended - When the concerned timers are strictly positive, Alcatel-Lucent recommends T_NETWORK_RESPONSE_TIME_CONG_IM <=
T_NETWORK_RESPONSE_TIME_CONG
rules
Logical T_NETWORK_RESPONSE_TIME_IM B11 Yes B12 Yes
name TRX nb No
HMI T_NETWORK_RESPONSE_TIME_IM Sub-syste MFS Cell Type No
Definition Maximum expected response time of a network server as seen from the PCU, ie delay before releasing a DL specific Instant Message TBF.
This timer is used in cells which are considered as not PS radio congested.
0: the reduced delayed DL TBF for specific Instant Message is disabled
Mandatory rules - T_NETWORK_RESPONSE_TIME_IM<= T_NETWORK_RESPONSE_TIME
Recommended - When the concerned timers are strictly positive, Alcatel-Lucent recommends T_NETWORK_RESPONSE_TIME_CONG_IM <= T_NETWORK_RESPONSE_TIME_IM.
rules
comment - Significant if EN_INSTANT_MSG_SERVICE_QOS is enabled.
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the DL TBF established after modification
Logical T_NETWORK_RESPONSE_TIME_IM_CONG B11 No B12 Yes
name TRX nb No
HMI T_NETWORK_RESPONSE_TIME_IM_CONG Sub-syste MFS Cell Type No
Definition Maximum expected response time of a network server as seen from the PCU, ie delay before releasing a DL specific Instant Message TBF.
This timer is used in cells which are considered as PS radio congested.
0: the reduced delayed DL TBF for specific Instant Message in case of PS congested cell is disabled
Mandatory rules - T_NETWORK_RESPONSE_TIME_IM_CONG <= T_NETWORK_RESPONSE_TIME
Recommended - When the concerned timers are strictly positive, Alcatel-Lucent recommends T_NETWORK_RESPONSE_TIME_IM_CONG <= T_NETWORK_RESPONSE_TIME_IM
and
rules T_NETWORK_RESPONSE_TIME_IM_CONG <= T_NETWORK_RESPONSE_TIME_CONG
comment - Significant if EN_INSTANT_MSG_SERVICE_QOS is enabled
Logical T_One_Block B11 Yes B12 Yes
name TRX nb No
HMI T_ul_2_ph_access Sub-syste
MFS Cell Type No
name Instance
MFS RMS No
Definition Timer to postpone the release of the M-EGCH link (in TDM mode) or of the TCP connection (in IP mode) of a TRX when the TRX does not support any (E)GPRS traffic, but a
one uplink block has been allocated to a MS for a 2 phase access TBF establishment on one of the RTSs of the TRX
Mandatory rules --
rules - T_one_block = 4 s if GPRS traffic is carried through Abis and Ater terrestrial links in all the cells of the PCU,
- T_one_block = 5 s if GPRS traffic is carried either through Abis satellite links or Ater satellite links in at least one cell of the PCU (round_trip_delay >= 500ms), and
Abis_transport_mode = 0 (TDM).
- T_one_block = 6 s if GPRS traffic between BTS and PCU is carried through satellite link (round_trip_delay >= 500ms) in at least one cell of the PCU and and
Abis_transport_mode = 1 (IP) for all the corresponding BTS.
External --
comment
Internal comment 3 sec is not recommended, because the implemented timer may end before.
T_one_block >= max of T_UL_ASSIGN_CCCH + 1/2 max of round_trip_delay
Logical T_PAG_CS (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_PAG_CS Sub-syste MFS Cell Type No
Definition This timer indicates the maximum time a CS PAGING message can remain in a Paging Group Queue. It includes the round-trip delay on A and A-bis or Gs/Gb and A-bis
interface.
Mandatory rules Equal to T_PAG_CS (BSC)
Recommended T_PAG_CS<T3113 (MSC timer)

rules
External --
comment
Internal comment round trip delay between MSC and BTS
Logical T_PAG_PS (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_PAG_PS Sub-syste MFS Cell Type No
Definition This timer indicates the maximum time a PS PAGING message can remain in a Paging Group Queue. It includes the round-trip delay on Gb and A-bis interface.
Mandatory rules Equal to T_PAG_PS (BSC)
Recommended T_PAG_PS < T3313 (SGSN timer)

rules
External --
comment
Internal comment round trip delay between SGSN and BTS
Logical T_PAGING_EXT B11 Yes B12 Yes
name TRX nb No
HMI T_PAGING_EXT Sub-syste MFS Cell Type No
Definition Maximum time between two specific paging request in an extended cell.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Lets define : A = (T_ul_assign_ccch or T_dl_assign_ccch, depending on the Air channel, AGCH or PCH, used to send the Immediate Assignment message) *
(Max_retrans_DL+1).
The T_DELAY_PAGING_EXT value should be configured to last, at least, the time up to the T3190 expiry on the MS side plus an additional margin (around 2.5sec
according to the MS Paging Group) to give the time to the MS to switch on the CCCH and receive the Paging Request message, Illustration with T3190n = 5sec and
T_dl_assign_ccch = 1.4sec :
A=(2+1)*1.4=4.2sec, then T_DELAY_PAGING_EXT >= 5-4.2+2.5>=3.3
A=(3+1)*1.4=5.6sec, then T_DELAY_PAGING_EXT >= 0+2.5>=4.1
The default value 5.5 sec is an average value.
Logical T_PAGING_REORG B11 Yes B12 Yes
name TRX nb No
HMI T_PAGING_REORG Sub-syste MFS Cell Type No
Definition Duration of the paging reorganization procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_PSCD_SCHEDULE_ACK B11 Yes B12 Yes
name TRX nb No
HMI T_PSCD_SCHEDULE_ACK Sub-syste MFS Cell Type No
Definition Timer guarding on network side the sending of Packet Serving Cell Data or PSI messages for Packet (P)SI Status feature. It is started at reception of Packet PSI Status /
Packet SI Status message, and stopped when all PSCDs / PSIs have been sent to the mobile (as indicated by RLC layer to RRM layer).
Mandatory rules --
Recommended --
rules
External Two timers are used on MS side. The first one equals 1 sec (for first sending of Packet (P)SI Status), the second one equals 2 sec (for subsequent sending of Packet
comment (P)SI Status). The timer on network side will be set to 1 sec - RTD = 840 msec
Internal comment --
Logical T_PSI_PACCH B11 Yes B12 Yes
name TRX nb No
HMI T_PSI_PACCH Sub-syste MFS Cell Type No
Definition Scheduling period of PSI1, PSI13 or PSI14 on PACCH.
Coding rules step size =1sec,
00000 == Deactivated PSI scheduling on PACCH,
00001 == 1s,

11110 == T_PSI_PACCH = 30 sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_REROUTING_REQUEST_GUARD B11 Yes B12 Yes
name TRX nb No
HMI T_REROUTING_REQUEST_GUARD Sub-syste MFS Cell Type No
Definition This timer controls the maximum time during which a PMU waits for the response to a rerouting request.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This timer prevents system lock in case of loss of the request or the response on the Ethernet bus or loss of the FLUSH-LL on Gb . It must be chosen large enough to
cover a Round trip time to the SGSN on Gb.
Logical T_RESEL B11 Yes B12 Yes
name TRX nb No
HMI T_RESEL Sub-syste MFS Cell Type No
Definition Timer whose expiry allows a MS, which has performed an abnormal release with cell reselection, to reselect the previous cell.
Coding rules coded on 3 bits, 000= 5 sec, 001= 10 sec, 010 = 15 sec, 011 = 20 sec, 100= 30 sec, 101 = 60 sec, 110 = 120 sec, 111 = 300 sec
Mandatory rules --
Recommended --
rules
External --
comment
MSs only apply this timer if another cell is available.
Logical T_RIM_DISABILITY B11 Yes B12 Yes
name TRX nb No
HMI T_RIM_DISABILITY Sub-syste MFS Cell Type No
Definition Timer supervising the disability of the adjacent target cell. When no RAN information has been received (no answer at the end of the retries or unknown destination), this
parameter corresponds to the duration it is not possible to use the RIM NACC procedure for this target cell.
Category Site (CAE) OMC-R access Changeable Type Timer Unit mn
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RIM_MULTIPLE_REPORT B11 Yes B12 Yes
name TRX nb No
HMI T_RIM_MULTIPLE_REPORT Sub-syste MFS Cell Type No
Definition Timer supervising reception of the following RAN Information with multiple report. It allows to resynchronize the System Information messages with the remote entity in
case of restart of the remote entity.
Category Site (CAE) OMC-R access Changeable Type Timer Unit mn
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RIM_RI B11 Yes B12 Yes
name TRX nb No
HMI T_RIM_RI Sub-syste MFS Cell Type No
Definition Timer supervising reception of RAN Information ACK
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RIM_RIR B11 Yes B12 Yes
name TRX nb No
HMI T_RIM_RIR Sub-syste MFS Cell Type No
Definition Timer supervising reception of RAN Information
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_RRLP_Delay_Tolerant B11 Yes B12 Yes
name TRX nb No
HMI T_RRLP_Delay_Tolerant Sub-syste MFS Cell Type No
Definition SMLC timer to guard the RRLP message exchange between the SMLC and the target MS, in case of a Delay Tolerant Location Request.
Mandatory rules T_LCS_Delay_Tolerant > T_RRLP_Delay_Tolerant

T_RRLP_Delay_Tolerant >= T_RRLP_Low_Delay
Recommended --
rules
comment
Internal comment --
Logical T_RRLP_Low_Delay B11 Yes B12 Yes
name TRX nb No
HMI T_RRLP_Low_Delay Sub-syste MFS Cell Type No
Definition SMLC timer to guard the RRLP message exchange between the SMLC and the target MS, in case of a Low Delay Location Request.
Mandatory rules T_Low_Delay > T_RRLP_Low_Delay

T_RRLP_Delay_Tolerant >= T_RRLP_Low_Delay
Recommended --
rules
comment
Internal comment --
Logical T_SAGI_GUARD B11 Yes B12 Yes
name TRX nb No
HMI T_SAGI_GUARD Sub-syste MFS Cell Type No
Definition Timer to guard the response from the A-GPS server (on SAGI: interface with A-GPS server).
Mandatory rules --
Recommended --
rules
External The timer is meaningful in the MFS when EN_SAGI=1.
comment
Internal comment --
Logical T_SHARED_DTM_INFO (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T_SHARED_DTM_INFO (MFS) Sub-syste MFS Cell Type No
Definition Timer monitoring the reception of BSCGP BSC Shared DTM Info Indication (periodic or not) on PCU side.
Mandatory rules shall be at least equal to T_SHARED_DTM_INFO (BSC) x 2
Recommended --
rules
External --
comment
Internal comment --
Logical T_STOP_FR_EMISSION B11 Yes B12 Yes
name TRX nb No
HMI T stop frame relay emission Sub-syste MFS Cell Type No
Definition Timer used to trigger restart of emission on a PVC (Frame Relay).
Category Site (CAE) OMC-R access Set by Create Type Timer Unit ms
Recommended --
rules
comment
Internal comment --
Logical T_TBF_ACTIV B11 Yes B12 Yes
name TRX nb No
HMI T_TBF_ACTIV Sub-syste MFS Cell Type No
Definition Waiting time during which RLC layer is waiting for the first downlink LLC PDU. This timer is started on TBF activation in RLC layer. It is stopped on receipt of the first LLC
PDU from RRM layer. On its expiry, the relevant TBF is released.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_TBF_BCK_REL B11 Yes B12 Yes
name TRX nb No
HMI T_TBF_BCK_REL Sub-syste MFS Cell Type No
Definition Guard timer against blocking situations where a RLC/MAC control block is expected from the MS.
Triggering condition:
End of UL TBF (an expected Packet Control Ack is not received),
End of DL TBF (an expected Packet Downlink Ack/Nack with FINAL indicator set to 1 is not received for acknowledged mode and Packet Control Acknowledgement for
unacknowledged mode),
Tx window of DL TBF stalled (an expected Packet Downlink Ack/Nack is not received).
Reseting condition:
Receipt of a RLC/MAC control block.
Action on expiry;
Release of a TBF
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The value of T_TBF_BCK_REL should be set accordingly to the round trip delay and the counters N3105 as followed:
T_TBF_BCK_REL = (N3105*(round_trip_delay output of RLC sublayer - MS - input of RLC sublayer)) + "margin of 250ms"
Logical T_ul_access_max B11 Yes B12 Yes
name TRX nb No
HMI T_ul_access_max Sub-syste MFS Cell Type No
Definition Timer to limit the duration of an UL TBF establishment.
Coding rules step size = 50 ms, 0 = 0 ms, 1 = 50 ms,... , 100 = 5000 ms
Mandatory rules --
Recommended The two following rules are recommended:

rules i) The Time T_ul_access_max shall be longer than the duration of a radio allocation requested towards the BSC.
ii) A too long value of T_ul_access_max may lead to reserve unnecessarily radio resources. It is recommended to set T_ul_access_max = T_repeat + 240 ms
Round_Trip_Delay, where the T_Repeat is the maximum time between two successive packet channel requests, 240 ms is a given margin. The value of T_Repeat
depends on the parameters S, TX_INT, and TX_INTEGER.
It is recommended to set this parameter as follows depending on whether or not GPRS traffic is carried between BTS and PCU through satellite links (round_trip_delay
>= 500ms):
- T_ul_access_max = 1400 ms if GPRS traffic is carried through Abis and Ater terrestrial links in at least one cell of the PCU (and this is irrespective of the BSS
transport mode: Abis_transport_mode = TDM or IP or mixed mode),
- T_ul_access_max = 1000 ms if GPRS traffic is carried through Abis or Ater satellite links in all the cells of the PCU (and this is irrespective of the BSS transport
mode: Abis_transport_mode = TDM or IP or mixed mode).
External --
comment
Internal comment For more details on the setting of this parameter, refer to the memo MND/TD/SYT/EBR/0497.2001 and MoAD/GSM Radio/R&D/SYT/GCO/208123/Ed5.
Logical T_ul_assign_ccch B11 Yes B12 Yes
name TRX nb No
HMI T_GPRS_assign_AGCH Sub-systeMFS Cell Type No
Definition Maximum emission duration of an Immediate Assignment message on AGCH aimed at establishing an uplink or a downlink TBF (when the mobile station is non-DRX mode),
or at allocating one uplink block.
Mandatory rules The T_ul_assign_ccch parameters is computed by the OMC as indicated in the table below:
AG_PREMPT_PCH / BCCH_EXT / CCCH_CONF / BS_AG_BLKS_RES / T_ul_assign_ccch (ms) if round_trip_delay < 500 ms / T_ul_assign_ccch (ms) if
round_trip_delay
>= 500 ms / Comments
Disabled/False/CCCH not combined/0/600/1200/

Disabled/False/CCCH combined/0/1000/1600/
Disabled/True/CCCH not combined/0/x/x/Not allowed

Disabled/True/CCCH not combined/1/2000/2500/
Disabled/True/CCCH combined/0/x/x/Not allowed
m
template
Disabled/True/CCCH combined/1/2000/2500/
Disabled/True/CCCH combined/2/1000/1600/
Enabled/False/CCCH not combined/0/600/1200/

Enabled/False/CCCH not combined/1/600/1200/
Enabled/False/CCCH not combined/2/600/1200/Not allowed
Recommended Enabled/False/CCCH combined/0/1000/1600/ --
rules Enabled/False/CCCH combined/1/1000/1600/
External Enabled/False/CCCH combined/2/1000/1600/ --
comment
Internal comment Enabled/True/CCCH not combined/0/x/x/Not allowed The retransmission period of the Packet DL Assignment messages on PACCH is computed by the MFS as follows:
Enabled/True/CCCH not combined/1/600/1200/
Enabled/True/CCCH not combined/2/600/1200/ T_ul_assign_ccch / (Max_GPRS_assign_agch_retrans + 1)
Enabled/True/CCCH not combined/4/600/1200/ A period lower than the round trip delay plus the RRBP duration may lead to the sending of two Packet DL
Assignment messages although the first assignment is
Enabled/True/CCCH not combined/5/600/1200/ correctly acknowledged by the MS. This behaviour has no consequence, the DL TBF begins after the reception of
the first Packet Control Ack messages.
Enabled/True/CCCH not combined/7/600/1200/ As the timer accuracy in the MFS is 50 ms, it is recommended to set T_GPRS_assign_agch so that the period of
retransmission of the Packet Downlink Assignment
Enabled/True/CCCH combined/0/x/x/Not allowed messages on PACCH, i.e. T_ul_assign_ccch / (Max_GPRS_assign_agch_retrans + 1), is a multiple of 50 ms.
Enabled/True/CCCH combined/1/1000/1600/
Enabled/True/CCCH combined/2/1000/1600/ In order not to unnecessary load the AGCH queue, it is recommended to set T_PUA = T_ul_assign_ccch.
Edition : 11 Released The T_ul_assign_ccch parameter is not displayed to the O&M user. BSS Telecom
parameters3BK 11203 0250 DSZZA Page 1969
The T_ul_assign_ccch parameter is computed automatically by the OMC as a function of the AG_PREEMPT_TCH, BCCH_EXT, CCCH_CONF and BS_AG_BLKS_RES
parameters. In addition, in an OMC, the T_ul_assign_ccch parameter is displayed to the O&M user after the OMC computation.
More details on the setting of T_ul_assign_ccch=T_GPRS_assign_agch parameter can be found in the memo MND/TD/SYT/EBR/0342.2001.
Logical T_ul_assign_pccch B11 Yes B12 Yes
name TRX nb No
HMI T_ul_assign_PCCCH Sub-syste
MFS Cell Type No
name Instance
cell RMS No
Definition The duration between the reception of the (EGPRS) Packet Channel Request message and one uplink radio block allocated to the MS.
Mandatory rules --
rules - T_ul_asssign_pccch = 0.4 s if GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell,
- T_ul_assign_pccch = 0.7 s if GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell.
External --
comment
The following rule that cannot be checked by the OMC must be fulfilled nevertheless:
t_ul_assign_pccch + round_trip_delay/2 + 6*20ms < T_ACK_WAIT.
Logical T_UL_CONGESTION B11 Yes B12 Yes
name TRX nb No
HMI T_UL_CONGESTION Sub-syste MFS Cell Type No
Definition Timer giving the periodicity of PDCH release in all cells of the BSS, in the UL congestion process.
Coding rules --
Mandatory rules --
Recommended --
rules
External Used only when EN_UL_CONGESTION is enabled
comment
Internal comment --
Logical T_USF_Scheduling_AGCH B11 Yes B12 Yes
name TRX nb No
HMI T_USF_Scheduling_AGCH Sub-syste MFS Cell Type No
Definition Time to elapse between the transmission of the Immediate assignment message by the PMU and the scheduling of the first USF for a UL TBF establishment on CCCH.
Coding rules step size = 50ms.
If T_USF_Scheduling = 0, then the USF are scheduled by the PMU immediately after sending the Immediate assignment message.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Too high value: useless delay of UL TBF establishment, when performed on CCCH,
Too low value: a few USF will be scheduled when the MS is not yet capable to use them.
Logical T_WAIT_CS_PROC B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_CS_PROC Sub-syste MFS Cell Type No
Definition Timer controlling on PMU side the repetition of BSCGP DTM ASSIGNMENT COMMAND / BSCGP PACKET NOTIFICATION / BSCGP GPRS INFORMATION DL after
reception of
BSCGP DTM ASSIGNMENT FAILURE (cause "BSC is in handover or assignment procedure") / PACKET NOTIFICATION ACK (cause "BSC is in handover or assignment
procedure") / BSCGP GPRS INFORMATION DL ACK (cause "BSC is in handover or assignment procedure").
Rec ref. None Domai DTM Min value 0.1 Coded Min 1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_WAIT_DTM B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_DTM Sub-syste MFS Cell Type No
Definition Timer supervising in the PCU the response of the BSC following a BSCGP Packet Notification (containing a PS paging) in dedicated mode, or a BSCGP GPRS
INFORMATION DL (also in dedicated mode).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T_WAIT_DTM_TCH_REL B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_DTM_TCH_REL Sub-syste MFS Cell Type No
Definition This timer defines the time that, upon reception of a BSCGP BSC Shared DTM Information Indication message indicating that the TCH resource allocated to a DTM capable
MS is being released at the CS application side, the PS application shall wait before releasing the TCH resource in its turn.
Mandatory rules --
Recommended --
rules
External The value 0 indicates that, upon reception of a BSCGP BSC Shared DTM Information Indication message, the PCU shall release immediately the related TCH resource.
comment
Internal comment This timer is used to avoid the misalignment between BSC and MFS (i.e. a TCH resource release is still on going at the BSC side, whereas the MFS considers that the
TCH resource release has already been finished by the BSC).
Upon reception of a BSCGP BSC Shared DTM Information Indication message indicating that the TCH resource allocated to a DTM capable MS is being released at the
BSC side, the MFS shall wait T_WAIT_DTM_TCH_REL seconds before releasing the TCH resource in his turn.
Logical T_WAIT_FLUSH B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_FLUSH Sub-syste MFS Cell Type No
Definition Timer monitoring the receipt of a Flush message or a GPRS suspend message further to the release of the on-going TBF(s)
Coding rules Step size : 0.5 sec
1 coded 1; 1,5 coded 2; 2 coded 3; 2,5 coded 4; .
15,5 coded 30 and 16 coded 31
Mandatory rules --
Recommended The timer T_WAIT_FLUSH shall be set to the maximum cell reselection duration plus the time for the MS to switch back to the old cell and send a Packet Cell Change
rules Failure message.
External --
comment
Internal comment The timer shall cover the time needed to receive a FLUSH message from SGSN from the point in time the MS switchs in a new cell.
Logical T_WAIT_PMR_MARGIN B11 Yes B12 Yes
name TRX nb No
HMI T_WAIT_PMR_MARGIN Sub-syste MFS Cell Type No
Definition Time margin used in the computation of the T_WAIT_PMR timer.
Mandatory rules --
Recommended --
rules
External -
comment
Internal comment --
Logical T200_GSL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T200_GSL (MFS) Sub-syste MFS Cell Type No
Definition Supervision of acknowledgements on the GSL link.
Coding rules --
Mandatory rules --
Recommended T_GSL_Ack (MFS) > T200_GSL (MFS) * (1 + N200_GSL (MFS))

rules It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Ater satellite links:
- T200_GSL(MFS) = 1 if GPRS traffic is carried through Ater terrestrial links in all BSC of the MFS.
- T200_GSL(MFS) = 2 if GPRS traffic is carried through Ater satellite links in at least one BSC of the MFS.
External --
comment
Internal comment The recommended value of 2 in case of satellite workaround a MFS bug which prevent to use the full K_GSL(MFS) window size at LAPD level.
Logical T203_GSL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T203_GSL (MFS) Sub-syste MFS Cell Type No
Definition Link supervision timer on the GSL link.
Coding rules --
Mandatory rules Equal to T203_GSL (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical T3148n (MFS) B11 Yes B12 Yes
name TRX nb No
HMI T3148n (MFS) Sub-syste MFS Cell Type No
Definition Timer controlling on MFS side the uplink DTM assignment. It is started at reception of BSCGP DTM Request, and stopped when sending BSCGP DTM Assignment
Command
or BSCGP DTM Reject to BSC.
Mandatory rules shall be equal to T3148n (BSC)
Recommended --
rules
External --
comment
Internal comment --
Logical T3166n B11 Yes B12 Yes
name TRX nb No
HMI T3166n Sub-syste MFS Cell Type No
Definition Maximum time a MS is waiting for a Packet UplinkAck/Nack with TLLI for contention resolution.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical T3168 (MFS) B11 Yes B12 Yes
name TRX nb No
Definition This timer defines the maximum time the MS waits for a packet UL assignment, after sending a Packet Resource Request (case of two-phase UL TBF establishment) or
after including a Channel Request Description Information Element in a Packet Downlink Ack/Nack (case of UL TBF establishment on a concurrent DL TBF). Broadcast in
PSI1 within the GPRS Cell Options IE.
001: 1000 ms
010: 1500 ms
011: 2000 ms
100: 2500 ms
101: 3000 ms
110: 3500 ms
111: 4000 ms.
Mandatory rules Equal to T3168 (BSC)
rules - T3168 = 1 s if GPRS traffic is carried through Abis and Ater terrestrial links,
- T3168 = 1.5 s if GPRS traffic is carried through Abis or Ater satellite links (round_trip_delay >= 500ms), and Abis_transport_mode(MFS) = 0 (TDM).
- T3168 = 2 s if GPRS traffic between the corresponding BTS and the MFS is carried through satellite link (round_trip_delay >= 500ms), and
Abis_transport_mode(MFS) = 1 (IP) for this BTS.
External The setting of T3168 should leave sufficient time to the MFS for granting PDCHs for serving the UL TBF request, plus also cover the round trip time and the possible
comment queuing delay within the MFS before the Packet Uplink Assignment can be sent to the Mobile Station. Therefore a value of 500 ms is not allowed in this release of the
Alcatel BSS.
Internal comment The following rules that cannot be checked by the OMC must be fulfilled nevertheless:
1. T3168 < T_ACK_WAIT - MAX_UL_TBF_SPDCH*20 - 60 (ms)
2. T3168 > T_MFS_Processing + T_Queuing_PACCH + round_trip_delay.
T_MFS_Processing corresponds to the processing time that can be expected at worse in the MFS for answering an uplink TBF request. Because the MFS may have
to request additional PDCHs to the BSC (which can take about 400 msec), a value of 500 msec should be considered for this parameter.
T_Queuing_PACCH corresponds to the maximum queuing time expected on PACCH and a value of about 200 msec should be considered.
Note that the chosen default values shall ensure that those rules are met.
Logical T3169 m B11 Yes B12 Yes
name TRX nb No
HMI T3169 Sub-syste MFS template Cell Type No
Definition Timer used in the procedure UL TBF abnormal release : when the UL TBF is cut due to the radio link quality or loss of the MS, the TFI, USF(s) and TAI cannot be
reallocated during T3169.
Mandatory rules T3169 = T3180
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition This timer is used on the mobile station side to define when to stop waiting for the USF determining the assigned portion of the uplink channel after the pervious RLC/MAC
block is sent. In multislot operation, it is enough that the assigned USF is noted on one of the uplink PDCHs. If expired, the mobile station repeats the procedure for random
access. This timer does not apply to fixed allocation transfers
Coding rules step size=0.1sec
Mandatory rules T3169 = T3180
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Timer used in the procedure UL TBF abnormal release : when the UL TBF is cut due to continuous MS stalled TBF, the TFI, USF(s) and TAI cannot be reallocated during
T3182n.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Timer used in the procedure DL TBF abnormal release : when the DL TBF is cut due to the radio link quality or loss of the MS, the TFI and TAI cannot be reallocated
during T3190n.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Timer used in the procedure DL TBF abnormal release : the timer is used on the network side to define when the current assignment is surely invalid on the MS side so
that the TFI and TAI can be reused.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
name TRX nb No
Definition Wait for release of the downlink TBF on MS side after reception of the final block by the MS.
0 0 0: 500 msec
0 0 1: 1000 msec
0 1 0: 1500 msec
1 1 1: 200 msec
T3192 + T_MAX_EXTENDED_UL + round_trip_delay < 5 sec
Recommended T3192>MS-BSS roundtrip delay + RRBP maximum duration (60 ms)

rules It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Abis or Ater satellite links:
==> Case GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell:
iii) however, if T3192 is finally set to 200 msec, then :
- some abnormal DL TBF release may occur during the delayed phase, and
- the MS may not receive the NC2 deactivation order from the BSS, which may lead the MS to send useless PMR before leaving its ready state.
==> Case GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell:
EN_DELAYED_DL_TBF_REL = 1).
In IP mode, the operator shall ensure that T3192 + T_MAX_EXTENDED_UL + round_trip_delay_bts_ms < 5 sec.
External The following values ofT3192 defined in the 3GPP TS 04.60 are not supported in this release of the Alcatel BSS:
comment 0 1 1: 0 msec
1 0 0: 80 msec
1 0 1: 120 msec m
1 1 0: 160 msec
template
Internal comment Broadcast in PSI

name TRX nb No
Definition Timer guarding on network side the sending of Packet Neighbour Cell Data messages for NACC feature. It is started at reception of Packet Cell Change Notification
message, and stopped when all PNCDs have been sent to the mobile (as indicated by RLC layer to RRM layer).
Mandatory rules --
Recommended --
rules
External This timer corresponds to T3208 on MS side. T3208n = T3208 - RTD = 960 ms - 160 ms
comment
Internal comment --
name TRX nb No
Definition This timer indicates to the MS the delay between two consecutive Periodic Location Update procedures.
Category Site (CAE) OMC-R access Changeable Type Number Unit 6 mn
Coding rules 0: no periodic location update, coded on 8 bits
Recommended --
rules
External --
comment
Internal comment Needed for feature MPDCH
name TRX nb No
Definition Link integrity verification polling timer (Frame Relay, see ITU Q.933, Annex A, A.7).
Coding rules --
Mandatory rules --
Recommended N392*T391 is the value of the link failure detection time

rules
comment
Internal comment --
Logical T5_RA_CAP_UPDATE B11 Yes B12 Yes
name TRX nb No
HMI T5_RA_CAP_UPDATE Sub-syste MFS Cell Type No
Definition Timer to supervise the reception of the MSs current Radio Access capability from the SGSN on Gb.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TARGET_MCS_BEP_OFFSET B11 No B12 Yes
name TRX nb No
HMI TARGET_MCS_BEP_OFFSET Sub-syste MFS Cell Type No
Definition Offset reduction applied to the MEAN_BEP reported by the MS.
It represents the stability of the current Modulation and Coding Scheme used for a DL EGPRS TBF, above TARGET_MCS_PR; the stability required before applying the
packet downlink power control to that TBF.
Coding rules --
Mandatory rules --
Recommended --
rules
Internal comment --
Logical TARGET_MCS_PR B11 No B12 Yes
name TRX nb No
HMI TARGET_MCS_PR Sub-syste MFS Cell Type No
Definition Target Modulation and Coding Scheme to reach before activating the dynamic packet downlink power control for TBFs in EGPRS mode.
Coding rules 4: MCS-5;
5: MCS-6;
6: MCS-7;
7: MCS-8;
8: MCS-9;
Mandatory rules - TARGET_MCS_PR <= MAX_EGPRS_MCS
Recommended --
rules
Internal comment --
Logical TBF_CS_DL B11 Yes B12 Yes
name TRX nb No
HMI TBF_CS_DL Sub-syste
MFS Cell Type No
name Instance
BSS RMS No
Definition Threshold defining the number of consecutive PACKET DOWNLINK ACK/NACK not received above which the Coding Scheme of a DL acknowledged or unacknowledged
DL TBF is changed to CS-1.
Mandatory rules --
Recommended --
rules
External If the GPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, in case where N3105_LIMIT < TBF_CS_DL then the loss of consecutive packet DL
comment ACK/NACK will not trigger link adaptation but TBF release.
If the GPRS traffic is carried through Abis satellitel link or Ater satellite link, in case where N3105_LIMIT_SATELLITE < TBF_CS_DL then the loss of consecutive packet
DL ACK/NACK will not trigger link adaptation but TBF release.
Internal comment --
Logical TBF_CS_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI TBF_CS_PERIOD Sub-syste MFS Cell Type No
Definition Number of RLC data blocks after which the CS adaption decision may be made, in GPRS.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter replaces TBF_CS_PERIOD1.
Logical TBF_CS_UL B11 Yes B12 Yes
name TRX nb No
HMI TBF_CS_UL Sub-syste MFS Cell Type No
Definition Threshold defining the maximum number of consecutive times the network receives an invalid UL RLC data block or nothing from the MS having a monoslot GPRS TBF
before changing the coding scheme to CS1. For a multislot GPRS TBF, TBF_CS_UL_limit := TBF_CS_UL x n_allocated
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TBF_CS3_BLER_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI TBF_CS3_BLER_PERIOD Sub-syste MFS Cell Type No
Definition Defines the window size required to estimate the CS3 BLER. The window size is expressed as a number of DL RLC data blocks.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TBF_CS4_BLER_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI TBF_CS4_BLER_PERIOD Sub-syste MFS Cell Type No
Definition Defines the window size required to estimate the CS4 BLER. The window size is expressed as a number of DL RLC data blocks.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TBF_DL_INIT_CS B11 Yes B12 Yes
name TRX nb No
HMI TBF_DL_INIT_CS Sub-syste MFS Cell Type No
Definition Value of the downlink coding scheme when the link adaptation algorithm is disabled or initial value (e.g. at TBF start or in case of TBF resumption with
CS_MAX_IDLE_PERIOD expiry) of the downlink coding scheme when the link adaptation algorithm is enabled.
Coding rules 0 : CS1, 1 : CS2, 2 : CS3, 3 : CS4
Mandatory rules TBF_DL_INIT_CS <= MAX_GPRS_CS
configuration.
External --
comment
Internal comment --
Logical TBF_DL_INIT_MCS B11 Yes B12 Yes
name TRX nb No
HMI TBF_DL_INIT_MCS Sub-syste MFS Cell Type No
Definition Value of the downlink modulation and coding scheme when the link adaptation algorithm is disabled or initial value (e.g. at TBF start or in case of TBF resumption with
CS_MAX_IDLE_PERIOD expiry) of the downlink modulation and coding scheme when the link adaptation algorithm is enabled.
Coding rules 0 : MCS-1
1 : MCS-2
2 : MCS-3
3 : MCS-4
4 : MCS-5
5 : MCS-6
6 : MCS-7
7 : MCS-8
8 : MCS-9
Mandatory rules TBF_DL_INIT_MCS <= MAX_EGPRS_MCS
configuration.
External The parameter is significant only if EN_EGPRS is enabled
comment
Internal comment --
Logical TBF_GCH_RATIO_DL B11 Yes B12 Yes
name TRX nb No
HMI TBF_GCH_RATIO_DL Sub-syste MFS Cell Type No
Definition Multiplication factor used in the computation of the maximum number of DL TBFs allowed to be established on a TRX for a given number of GCHs on this TRX (i.e. in the
M-EGCH link of this TRX).
Mandatory rules --
Recommended --
rules
comment - If there is a great amount of short data TBFs in the network (delayed DL or extended UL phases are longer than actual TBF traffic phases), the existing TBF
limitations (in number of TBFs established on a TRX for a given number of GCHs on this TRX) may be too restrictive and lead to some TBF establishment failures. The
TBF_GCH_RATIO_DL and TBF_GCH_RATIO_UL parameters allow to increase this limit, so to be more flexible.
Another justification for the TBF_GCH_RATIO_DL and TBF_GCH_RATIO_UL parameters is that the limits for DL and UL TBF numbers may be different.
The TBF_GCH_RATIO_DL and TBF_GCH_RATIO_UL parameters are used in the formulae to compute Min_Nb_GCH_Best_Effort_XL (RRM-PRH). An increase of their
value should be validated by load tests (in order to check, among others, that the DSP can support the induced extra CPU load).
Internal comment --
Logical TBF_GCH_RATIO_UL B11 Yes B12 Yes
name TRX nb No
HMI TBF_GCH_RATIO_UL Sub-syste MFS Cell Type No
Definition Multiplication factor used in the computation of the maximum number of UL TBFs allowed to be established on a TRX for a given number of GCHs on this TRX (i.e. in the
M-EGCH link of this TRX).
Mandatory rules --
Recommended --
rules
comment - If there is a great amount of short data TBFs in the network (delayed DL or extended UL phases are longer than actual TBF traffic phases), the existing TBF
limitations (in number of TBFs established on a TRX for a given number of GCHs on this TRX) may be too restrictive and lead to some TBF establishment failures. The
TBF_GCH_RATIO_DL and TBF_GCH_RATIO_UL parameters allow to increase this limit, so to be more flexible.
Another justification for the TBF_GCH_RATIO_DL and TBF_GCH_RATIO_UL parameters is that the limits for DL and UL TBF numbers may be different.
The TBF_GCH_RATIO_DL and TBF_GCH_RATIO_UL parameters are used in the formulae to compute Min_Nb_GCH_Best_Effort_XL (RRM-PRH). An increase of their
value should be validated by load tests (in order to check, among others, that the DSP can support the induced extra CPU load).
Internal comment --
Logical TBF_MCS_DL B11 Yes B12 Yes
name TRX nb No
HMI TBF_MCS_DL Sub-syste
MFS Cell Type No
name Instance
BSS RMS No
Definition Threshold defining the number of consecutive EGPRS PACKET DOWNLINK ACK/NACK not received above which the MCS of a DL acknowledged or unacknowledged DL
TBF is changed to MCS-1.
Mandatory rules --
Recommended --
rules
External If the EGPRS traffic is carried through Abis terrestrial link and Ater terrestrial link, in case where EGPRS_N3105_LIMIT < TBF_MCS_DL then the loss of consecutive
comment EGPRS Packet DL ACK/NACK will not trigger link adaptation but TBF release.
If the EGPRS traffic is carried through Abis satellitel link or Ater satellite link, in case where EGPRS_N3105_LIMIT_SATELLITE < TBF_MCS_DL then the loss of
consecutive EGPRS Packet DL ACK/NACK will not trigger link adaptation but TBF release.
Internal comment --
Logical TBF_MCS_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI TBF_MCS_PERIOD Sub-syste MFS Cell Type No
Definition Minimum number of transmitted (resp. received) radio blocks after which the DL (resp. UL) MCS adaptation decision may be made in EGPRS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The default value of 12 is equal to the value of EGPRS_LQC_WINDOW_SIZE (hard-coded RLC parameter) to optimize especially the time of the first MCS adaptation
decision in case of an UL EGPRS TBF alone on its radio resources.
Logical TBF_MCS_UL B11 Yes B12 Yes
name TRX nb No
HMI TBF_MCS_UL Sub-syste MFS Cell Type No
Definition Threshold defining the maximum number of consecutive times the network receives an invalid UL RLC data block or nothing from the MS having a monoslot EGPRS TBF
before changing the coding scheme to MCS1. For a multislot EGPRS TBF, TBF_MCS_UL_limit := TBF_MCS_UL x n_allocated_timeslots.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TBF_UL_INIT_CS B11 Yes B12 Yes
name TRX nb No
HMI TBF_UL_INIT_CS Sub-syste MFS Cell Type No
Definition Value of the uplink coding scheme when the link adaptation algorithm is disabled or initial value (e.g. at TBF start or in case of TBF resumption with
CS_MAX_IDLE_PERIOD expiry) of the uplink coding scheme when the link adaptation algorithm is enabled.
Coding rules 0 : CS1, 1 : CS2, 2 : CS3, 3 : CS4
Mandatory rules TBF_UL_INIT_CS <= MAX_GPRS_CS
configuration.
External Exception cases apply for uplink TBF establishment on PACCH when link adaptation is enabled.
comment
Internal comment --
Logical TBF_UL_INIT_MCS B11 Yes B12 Yes
name TRX nb No
HMI TBF_UL_INIT_MCS Sub-syste MFS Cell Type No
Definition Value of the uplink modulation and coding scheme when the link adaptation algorithm is disabled or initial value (e.g. at TBF start or in case of TBF resumption with
CS_MAX_IDLE_PERIOD expiry) of the uplink modulation and coding scheme when the link adaptation algorithm is enabled.
Coding rules 0 : MCS-1
1 : MCS-2
2 : MCS-3
3 : MCS-4
4 : MCS-5
5 : MCS-6
6 : MCS-7
7 : MCS-8
8 : MCS-9
Mandatory rules TBF_UL_INIT_MCS <= MAX_EGPRS_MCS
configuration.
External The parameter is significant only if EN_EGPRS is enabled. Exception cases apply for uplink TBF establishment on PACCH when link adaptation is enabled.
comment
Internal comment --
Logical Tcorr B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_CORR Sub-syste MFS Cell Type No
Definition Timer to supervise clock drift correction loop for 16k channel.
Coding rules step size=100ms
Mandatory rules --
Recommended Tcorr > Trelease+240ms and Tcorr > Testab+240ms

rules where 240 ms represents the maximum delay in MAC layer between the notification for a DBN correction and the application of this DBN correction.
- Tcorr = 0.8 s if GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell,
- Tcorr = 1.4 s if GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell.
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Tcorr.
Internal comment --
Logical TCP_KEEP_ALIVE_CNT (MFS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_CNT Sub-syste MFS Cell Type No
Definition Number of TCP keep-alive messages sent by the IPGCH-C / IPGSL and not acnowledged by the peer before triggering a TCP disconnection
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_CNT (BTS) and TCP_KEEP_ALIVE_CNT (BSC)

rules
External --
comment
Internal comment --
Logical TCP_KEEP_ALIVE_IDLE (MFS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_IDLE Sub-syste MFS Cell Type No
Definition IPGCH-C / IPGSL link supervision: Time to wait before sending the first TCP keep alive message.
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_IDLE (BTS), TCP_KEEP_ALIVE_IDLE (BSC)

rules
External --
comment
Internal comment --
Logical TCP_KEEP_ALIVE_INTVL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_KEEP_ALIVE_INTVL Sub-syste MFS Cell Type No
Definition Time between the sending of two TCP keep-alive messages by IPGCH-C or IPGSL.
Mandatory rules --
Recommended Equal to TCP_KEEP_ALIVE_INTVL (BTS) and TCP_KEEP_ALIVE_INTVL (BSC)

rules
External --
comment
Internal comment --
Logical TCP_MAX_RETRANS (MFS) B11 Yes B12 Yes
name TRX nb No
MFS Cell Type No
name Instance
MFS RMS No
Definition Maximum number of times a TCP segment (used by IPGSL or IPGCHC) is resent by the MFS before to raise a TCP time-out error.
Mandatory rules --
Recommended 1) To be set to a value in order that a TCP reset is triggered before repetitions of not acknowledged message triggered at BSCGP level (due to T_GSL_ACK(MFS)
rules expiry), so, < T_GSL_ACK(MFS) x MAX_GPU_PER_BSC. If this is not the case, BSCGP layer will resend unnecessarily to TCP layer too many not acknowledged
messages.
2) TCP_MAX_RETRANS (MFS) should be set to a value in order that TCP reset (Abort interval) is bigger than the TRE PS recovery time.
3) TCP_MAX_RETRANS (MFS) should be set to a value in order that TCP reset (Abort interval) is lower than T_IPGCHU_TIMEOUT
External The purpose of the 1st recommended rule is to ensure that failure at TCP level will be detected before failure at BSCGP level.
comment For example, if a global failure happens during a TCP transfer in which the failed connection side was the data receiver, the sending TCP will try to retransmit the
non-acknowledged data segments, but TCP will limit the number of retransmissions by
means of this parameter. On expiry, TCP resets the connection (RST segment).
The purpose of the 2nd rule is to ensure that the GP will be able to reopen the TCP connection in case of TRE or traffic restart.
It is a constant hardcoded.
The purpose of the 3rd recommended rule is to avoid an abortion by the IPGCHU connection in case some acknowledgements (sent by IPGCHC so by TCP) are not
successful.
Internal comment - Exponential back off applied by the TCP stack of the MFS (used by IPGSL and IPGCHC) before each resend of TCP segment.
Note: the max time between two resends is 1 minute
Logical TCP_MSL (MFS) B11 Yes B12 Yes
name TRX nb No
HMI TCP_MSL (MFS) Sub-syste MFS Cell Type No
Definition TCP message segment lifetime, used by IPGCH-C and IPGSL.
Mandatory rules --
Recommended TCP_MSL (MFS) = TCP_MSL (BSC)

rules TCP_MSL (MFS) = TCP_MSL (BTS)
External --
comment
Internal comment - hardcoded in the kernel
Logical Tdsl B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_dsl Sub-syste MFS Cell Type No
Definition Supervision of loss of downlink synchronisation for 16k channels.
Mandatory rules Tdsl < Trelease
Recommended --
rules
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Tdsl.
Internal comment There is potential Interactions between Dynamic Abis allocation and CS traffic (CS call drop increase) when value is high. No clear interaction test cases are
identified today (neither during GCH establishment failure, nor during abnormal GCH release at MFS side).And potential border effect of value decreasing (ex:200) are
unknown.
Logical Testab B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_ESTAB Sub-syste MFS Cell Type No
Definition Supervision of loss of GCH link establishment for 16k channels.
Coding rules step size= 100 ms
Mandatory rules Treq_pending > Testab
rules - Testab = 0.4 s if GPRS traffic is carried through Abis and Ater terrestrial links in the serving cell,
- Testab = 1 s if GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell.
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Testab.
Internal comment --
Logical THR_NC2_LOAD_RANKING B11 Yes B12 Yes
name TRX nb No
HMI THR_NC2_LOAD_RANKING Sub-syste MFS Cell Type No
Definition Threshold above which the load of the serving cell is considered in a high load situation in the NC2 cell ranking process
Coding rules Step size of 10%
0 : 0%; 1: 10%; . 10 : 100%
Mandatory rules --
Recommended --
rules
External This parameter is only relevant if the parameter NETWORK_CONTROL_ORDER is set to 2: NC2 mode of operation for R99 onwards MS or "3: NC2 mode of operation
comment for all MS".
The serving cell is considered in a low load situation when THR_NC2_LOAD_RANKING = 0 %. The value of 0 % deactivates the load evaluation in the serving cell.
The load situation of external cells is unknown in the serving cell. The BSS then computes the NC2 load of those cells as follows:
- If the threshold THR_NC2_LOAD_RANKING is set to a value lower than 100 %, then the cell is considered in a low load situation.
- If the threshold THR_NC2_LOAD_RANKING is set to 100 %, then the cell is considered in an high load situation
Internal comment --
Logical THR_RR_ALLOC_DEFENSE_HIGH B11 Yes B12 Yes
name TRX nb No
HMI THR_RR_ALLOC_DEFENSE_HIGH Sub-syste MFS Cell Type No
Definition This threshold defines the minimal duration before triggering the PMU defensive mechanism for radio resource management, according to the most important criteria (C1
and C3).
Category System (CST) OMC-R access None (DLS) Type Threshold Unit mn
Coding rules Step size = 10 min.
Mandatory rules The duration must be strictly greater than 10 min, which is the time used for other existing defensive mechanism in RRM (and because of other case of
TCH_INFO_PERIOD restart)
Recommended --
rules
External --
comment
Internal comment --
Logical THR_RR_ALLOC_DEFENSE_LOW B11 Yes B12 Yes
name TRX nb No
HMI THR_RR_ALLOC_DEFENSE_LOW Sub-syste MFS Cell Type No
Definition This threshold defines the minimal duration before triggering the PMU defensive mechanism for radio resource management, according to the less important criteria (C2).
Category System (CST) OMC-R access None (DLS) Type Threshold Unit mn
Coding rules Step size = 10 min.
Mandatory rules The duration must be strictly greater than 10 min, which is the time used for other existing defensive mechanism in RRM (and because of other case of
TCH_INFO_PERIOD restart)
Recommended --
rules
External --
comment
Internal comment --
Logical THRES_DSP_XOFF B11 Yes B12 Yes
name TRX nb No
HMI THRES_DSP_XOFF Sub-syste MFS Cell Type No
Definition Threshold used for the management of DSP memory congestion (RLC resources).
Threshold above which downlink LLC PDUs are no more sent by RRM to RLC.
Coding rules step size=0.1% (0 == 0%, 1000 == 100%)
Mandatory rules THRES_G_MAX_HIGH > THRES_G_MAX_LOW > THRES_DSP_XOFF > THRES_DSP_XON > THRES_LOW_DSP_XOFF > THRES_LOW_DSP_XON
Recommended --
rules
comment
Internal comment --
Logical THRES_DSP_XON B11 Yes B12 Yes
name TRX nb No
HMI THRES_DSP_XON Sub-syste MFS Cell Type No
Definition Threshold used for the management of DSP memory congestion (RLC resources). Threshold under which downlink LLC PDU are sent again by RRM to RLC,
after having previously encountered a DSP memory congestion situation (due to the THRES_DSP_XOFF threshold).
.
Recommended --
rules
comment
Internal comment --
Logical THRES_G_MAX_HIGH B11 Yes B12 Yes
name TRX nb No
HMI THRES_G_MAX_HIGH Sub-syste MFS Cell Type No
Threshold used to handle the transition between the G_XOFF and G_MAX
congestion states. In the G_MAX congestion state, some TBFs will be released, in order to free some DSP memory.
Coding rules step size = 0.1 %
Recommended --
rules
comment
Internal comment The THRES_G_MAX_HIGH value is limited to a maximum defined for each software generation.
A maximum value is defined in BSS telecom parameters to prevent the DSP from refusing the configuration.
Note that any value depend on the DSP implementation (free DSP memory size) and needs to be tuned.
The default value is the initial one.
Logical THRES_G_MAX_HIGH_IP B11 Yes B12 Yes
name TRX nb No
HMI THRES_G_MAX_HIGH_IP Sub-syste MFS Cell Type No
Definition Threshold used for the management of RLC and IPGCH SCP memory congestion in IP mode (G_XOFF -> G_MAX transition).
Mandatory rules THRES_G_MAX_HIGH_IP > THRES_G_MAX_LOW_IP > THRES_SCP_XOFF_IP > THRES_SCP_XON_IP > THRES_LOW_SCP_XOFF_IP >
THRES_LOW_SCP_XON_IP
Recommended --
rules
comment
Internal comment --
Logical THRES_G_MAX_LOW B11 Yes B12 Yes
name TRX nb No
HMI THRES_G_MAX_LOW Sub-syste MFS Cell Type No
Threshold used to handle the transition between the G_MAX and G_XOFF congestion states.
Recommended --
rules
comment
Internal comment --
Logical THRES_G_MAX_LOW_IP B11 Yes B12 Yes
name TRX nb No
HMI THRES_G_MAX_LOW_IP Sub-syste MFS Cell Type No
Definition Threshold used for the management of RLC and IPGCH SCP memory congestion in IP mode (G_MAX -> G_XOFF transition).
Recommended --
rules
comment
Internal comment --
Logical THRES_LOW_DSP_XOFF B11 Yes B12 Yes
name TRX nb No
HMI THRES_LOW_DSP_XOFF Sub-syste MFS Cell Type No
Threshold above which TBF establishment is not possible.
Coding rules step size = 0.1% (0% == 0, 100% = 1000)
Recommended --
rules
comment
Internal comment --
Logical THRES_LOW_DSP_XON B11 Yes B12 Yes
name TRX nb No
HMI THRES_LOW_DSP_XON Sub-syste MFS Cell Type No
Threshold under which TBF establishment becomes possible again after having previously encountered a DSP memory congestion situation (due to the
THRES_LOW_DSP_XOFF threshold).
Recommended --
rules
comment
Internal comment --
Logical THRES_LOW_SCP_XOFF_IP B11 Yes B12 Yes
name TRX nb No
HMI THRES_LOW_SCP_XOFF_IP Sub-syste MFS Cell Type No
Definition Threshold used for the management of RLC and IPGCH SCP memory congestion in IP mode (NO_CONGESTION -> G_LOW_XOFF transition).
Recommended --
rules
External Applicable only to IP transport
comment
Internal comment --
Logical THRES_LOW_SCP_XON_IP B11 Yes B12 Yes
name TRX nb No
HMI THRES_LOW_SCP_XON_IP Sub-syste MFS Cell Type No
Definition Threshold used for the management of RLC and IPGCH SCP memory congestion in IP mode (G_LOW_XOFF -> NO_CONGESTION transition).
Recommended --
rules
External Applicable only to IP transport
comment
Internal comment --
Logical THRES_SCP_XOFF_IP B11 Yes B12 Yes
name TRX nb No
HMI THRES_SCP_XOFF_IP Sub-syste MFS Cell Type No
Definition Threshold used for the management of RLC and IPGCH SCP memory congestion in IP mode (G_LOW_XOFF -> G_XOFF transition).
Recommended --
rules
comment
Internal comment --
Logical THRES_SCP_XON_IP B11 Yes B12 Yes
name TRX nb No
HMI THRES_SCP_XON_IP Sub-syste MFS Cell Type No
Definition Threshold used for the management of RLC and IPGCH SCP memory congestion in IP mode (G_XOFF -> G_LOW_XOFF transition).
Recommended --
rules
comment
Internal comment --
Logical Tns_alive B11 Yes B12 Yes
name TRX nb No
HMI TnsAlive Sub-syste MFS Cell Type No
Definition Time-out to trigger the test procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical Tns_alive_IP B11 Yes B12 Yes
name TRX nb No
HMI Tns_alive_IP Sub-syste MFS Cell Type No
Definition Guard the NS-VC test procedure in case of Gb over IP.
Mandatory rules --
Recommended --
rules
External In the standard, this parameter is set to 3sec, not changeable with TDM or IP sub-network.
comment
Internal comment --
Logical Tns_block B11 Yes B12 Yes
name TRX nb No
HMI TnsBlock Sub-syste MFS Cell Type No
Definition Time-out to trigger the block/unblock procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical Tns_reset B11 Yes B12 Yes
name TRX nb No
HMI TnsReset Sub-syste MFS Cell Type No
Definition Time-out for reset procedure.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical Tns_test B11 Yes B12 Yes
name TRX nb No
HMI TnsTest Sub-syste MFS Cell Type No
Definition Overall time-out to test an NS-VC.
Coding rules --
Mandatory rules --
Recommended --
rules
comment
Internal comment --
Logical Tns_test_IP B11 Yes B12 Yes
name TRX nb No
HMI Tns_test_IP Sub-syste MFS Cell Type No
Definition Periodicity of the NS-VC test procedure in case of Gb over IP.
Mandatory rules --
Recommended --
rules
External In the standard, this parameter is the same with TDM or IP sub-network.
comment
Internal comment --
Logical TOM8_PRIORITY B11 Yes B12 Yes
name TRX nb No
HMI TOM8_PRIORITY Sub-syste MFS Cell Type No
Definition Defines the relative priority used for the pre-defined TOM8 Packet Flow Context
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Trelease B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_release Sub-syste MFS Cell Type No
Definition Supervision of GCH link release for 16k channel.
Mandatory rules Trelease > Tdsl

Treq_pending > Trelease
rules - Trelease = 500 ms if GPRS traffic is carried through Abis and Ater terrestrial links in all the cells of the MFS,
- Trelease = 1000 ms if GPRS traffic is carried either through Abis satellite links or Ater satellite links in at least one cell of the MFS.
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Trelease.
Internal comment --
Logical Treq_pending B11 Yes B12 Yes
name TRX nb No
HMI Treq_pending Sub-syste MFS Cell Type No
Definition Maximum time during which a GCH establishment or release request from PMU can be delayed in MEGCH layer.
Mandatory rules Treq_pending > Trelease+Tcorr
Recommended Treq_pending > Testab+Tcorr

rules
comment
Internal comment At the timer expiry, PTU is forced to provide an answer to the PMU request.
Logical TRTS_PS B11 Yes B12 Yes
name TRX nb No
HMI TRTS_PS Sub-syste MFS Cell Type No
Definition This timer is used in the BTS to supervise the state of a RTS used as a PDCH. This timer is started when the BTS does not receive in a 20 ms period a valid DL frame on
the RTS and is stopped when it receives one DL valid frame.
Mandatory rules - TRTS_PS > T_MAX_FOR_MS_SYNCHRO
Recommended - we can assume that a difference of 80ms between the two timers is sufficient to cope with possible delay on the MEGCH interface (in TDM mode)
rules
External --
comment
Internal comment --
Logical Tsns_config B11 Yes B12 Yes
name TRX nb No
HMI Tsns_config Sub-syste MFS Cell Type No
Definition Guard the SNS config procedure from the SGSN
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Tsns_prov B11 Yes B12 Yes
name TRX nb No
HMI Tsns_prov Sub-syste MFS Cell Type No
Definition Guard the SNS procedures
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Tsns_restart B11 Yes B12 Yes
name TRX nb No
HMI Tsns_restart Sub-syste MFS Cell Type No
Definition Timer to prevent the use of a SGSN IP endpoint after a failure.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical Tusl B11 Yes B12 Yes
name TRX nb No
HMI T_GCH_usl Sub-syste MFS Cell Type No
Definition Supervision of loss of uplink synchronisation for 16k channels.
Mandatory rules Tusl < (20 x 48) = 960 ms
Recommended --
rules
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Tusl.
Internal comment --
Logical TX_EFFICIENCY_ACK_THR B11 Yes B12 Yes
name TRX nb No
HMI TX_EFFICIENCY_ACK_THR Sub-syste MFS Cell Type No
Definition Threshold below which the TBF is released because of a bad transmission efficiency in acknowledged mode.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TX_EFFICIENCY_NACK_THR B11 Yes B12 Yes
name TRX nb No
HMI TX_EFFICIENCY_NACK_THR Sub-syste MFS Cell Type No
Definition Threshold below which the TBF is released because of a bad transmission efficiency in unacknowledged mode.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TX_EFFICIENCY_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI TX_EFFICIENCY_PERIOD Sub-syste MFS Cell Type No
Definition Number of received RLC data blocks for GPRS TBF after which TX_EFFICIENCY is computed.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical TX_INT B11 Yes B12 Yes
name TRX nb No
HMI TX_INT Sub-syste MFS Cell Type No
Definition Number of PRACH timeslots to spread transmission of PACKET CHANNEL REQUEST.
Coding rules Possible values are : 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 16, 20, 25, 32, 50, coded from 0000 to 1111
Mandatory rules --
Recommended It is recommended to set TX_INT so that the corresponding spreading time is about 240 ms.
rules
External --
comment
Logical Tx_integer (MFS) B11 Yes B12 Yes
name TRX nb No
HMI TX_INTEGER Sub-syste MFS Cell Type No
Definition Number of RACH timeslots that spread transmission of CHANNEL REQUEST.
Coding rules Possible values are:3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 25, 32, 50 respectively binary coded from 0000 to 1111
Mandatory rules Equal to Tx_Integer (BSC)
Recommended When the GPRS is supported through Abis or Ater terrestrial links, it is recommended to set:
rules TX_INTEGER = 32 if the CCCH is not combined, i.e. CCCH_CONF <> 1
TX_INTEGER = 12 if the CCCH is combined, i.e. CCCH_CONF = 1.
When the GPRS is supported through Abis or Ater satellite links, it is recommended to set:
TX_INTEGER = 32 whatever the configuration of the CCCH.
The number of slots belonging to the MSs RACH between 2 successive Channel Request messages is a random value drawn randomly for each new retransmission
with uniform distribution in the set (S, S+1, ...,S+T-1). With T = Tx_Integer and S depending on the CCCH configuration as shown below:
1) for non combined CCCH:

Tx_Integer = 7, 12, 32 --> S = 217 RACH frames (i.e. 998.2 ms)
2) for combined CCCH:

Note:
m
External When EN_GPRS=1, it is recommended to set: template
comment TX_INTEGER = 32 if the CCCH is not combined, i.e. CCCH_CONF <> 1
TX_INTEGER = 12 if the CCCH is combined, i.e. CCCH_CONF = 1
Internal comment Needed for feature MPDCH.
For more details on the setting of this parameter, refer to the memo MND/TD/SYT/EBR/0497.2001.
Logical UL_POLL_FACTOR B11 Yes B12 Yes

name TRX nb No
HMI UL_DATA_CREDIT Sub-syste MFS Cell Type No
Definition This parameter defines the slope in credit computation for the uplink cyclic polling algorithm.
Category System (CST) - In the non-combined CCCH configuration, there are 51 RACH frames per 51-multiframe OMC-R access None (DLS)
Type Number Unit None
Rec ref. None - In the combined CCCH configuration, there are 27 RACH frames per 51-multiframe. Domai GPRS Min value 1
Coded Min 1
Coding rules --
Mandatory rules --
Recommended --
rules
External The max number of uplink TBFs assigned per PDCH shall be such that the TBF scheduling periodicity needed for BTS measurements is respected (taking into account
comment needed bandwidth for PACCH en uplink).
Internal comment --
Logical USF_NE B11 Yes B12 Yes
name TRX nb No
HMI usfNe Sub-syste MFS Cell Type No
Definition USF "No emission" used to schedule UL signalling of TBF without USF.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical VARIOUS_IP_PRIORITY (MFS) B11 Yes B12 Yes
name TRX nb No
HMI VARIOUS_IP_PRIORITY (MFS) Sub-syste MFS Cell Type No
Definition BSS internal priority used by the PCU for the DHCP, ICMP and ARP protocols in the IP network
3: lower priority
Mandatory rules --
Recommended Should be consistent with the priorities used by others NEs.

rules
Internal comment - In case of specific configurations using RIP or OSPF inside the MFS, this parameter also gives the internal priority used by the routing protocol.
Logical WEIGHT_BIAS_DETERMINATION B11 Yes B12 Yes
name TRX nb No
HMI WEIGHT_BIAS_DETERMINATION Sub-syste MFS Cell Type No
Definition Weighting factor used in the transfer bias determination in order to mitigate resource reallocations due to changing bias.
Mandatory rules --
Recommended --
rules
External This parameter allows to avoid changing the bias of the on-going transfer too often. The number of bytes transferred in each direction is actually a weighted average
comment taking into account WEIGHT_BIAS_DETERMINATION * the weighted average as of the previous assessment.
Internal comment --
Logical Weight_P10 B11 Yes B12 Yes
name TRX nb No
HMI Weight_P10 Sub-syste MFS Cell Type No
Definition Weight to be used for a TBF/PFC of priority 10
Mandatory rules --
Recommended weight_Px >= weight_Py if x<y

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
name TRX nb No
Mandatory rules --

rules
External --
comment
Internal comment --
Logical WI_DTM B11 Yes B12 Yes
name TRX nb No
HMI WI_DTM Sub-syste MFS Cell Type No
Definition Value of Wait Indication for DTM requets
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical WI_PR B11 Yes B12 Yes
name TRX nb No
HMI WI_PR Sub-syste MFS Cell Type No
Definition Wait indication used in IMMEDIATE ASSIGNMENT REJECT or PACKET ACCESS REJECT in the nominal case (see the WI_PR_CPU_OVERLOAD parameter for the
particular
cases).
Coding rules --
Mandatory rules WI_PR <= WI_PR_CPU_OVERLOAD
Recommended --
rules
External --
comment
Internal comment --
Logical WI_PR_CPU_OVERLOAD B11 Yes B12 Yes
name TRX nb No
HMI WI_PR_CPU_OVERLOAD Sub-syste MFS Cell Type No
Definition Wait indication used in IMMEDIATE ASSIGNMENT REJECT or PACKET ACCESS REJECT in case of PMU CPU or memory overload.
Coding rules --
Mandatory rules WI_PR <= WI_PR_CPU_OVERLOAD
Recommended --
rules
External --
comment
Internal comment --
OMC parameters
Logical ACCESS_RATE_BC (OMC) B11 Yes B12 Yes
name TRX nb No
HMI Capacity Sub-syste OMC Cell Type No
Definition Physical access rate of the Frame Relay bearer channel.
Category Site (CAE) OMC-R access Virtual displayed Type Number Unit kbit/s
Coding rules --
Mandatory rules CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC (OMC)
Recommended --
rules
comment
Internal comment This parameter is computed by the OMC, using the same formula as the MFS.
Logical BSC_X25_primary_address B11 Yes B12 Yes
name TRX nb No
HMI BSC Primary X25 Address Sub-syste OMC Cell Type No
Definition BSC X25 primary address.
Def value * Coded Def
Recommended --
rules
comment
Internal comment In the DLS, this parameter is presented as an array of 15 characters, see BSC_X25_Primary_Address_i [n], n=1..15
Logical BSC_X25_secondary_address B11 Yes B12 Yes
name TRX nb No
HMI BSC Secondary X25 Address Sub-syste OMC Cell Type No
Definition BSC X25 secondary address.
Def value * Coded Def
Recommended --
rules
comment
Internal comment In the DLS, this parameter is presented as an array of 15 characters, see BSC_X25_Primary_Address_i [n], n=1..15
Logical Cell_Type B11 Yes B12 Yes
name TRX nb No
HMI Cell Type OMC Sub-syste Cell Type No
Definition Combination of CELL_DIMENSION_TYPE, CELL_LAYER_TYPE, CELL_PARTITION_TYPE, CELL_RANGE for an OMC own cell. Used for cell default parameter template.
Rec ref. None Domai GSM Min value * Coded Min
n Max value * Coded Max
Spec ref. Handover preparation Coded Max
Coding rules Single (0), Concentric (1), Umbrella (2), Micro (3), Umbrella Concentric (4), Mini (5), Extended Inner (6), Extended Outer (7), Mini Concentric (8), Micro Concentric (9),
Indoor (10), Indoor Concentric(11)
Mandatory rules - EN_SYNCHRONISED_HO shall be set to disabled when CELL_TYPE is equal to Extended inner or Extended outer.
Recommended --
rules
External *: possible values are:
comment - Single
- Umbrella
- Umbrella Concentric
- Micro
- Mini
- Micro Concentric
- Mini Concentric
- Indoor
- Indoor Concentric (labelled "Indoor Multiband" on the HMI)
- Extended Inner
- Extended Outer
Internal comment Value computed according to CELL_DIMENSION_TYPE, CELL_LAYER_TYPE, CELL_PARTITION_TYPE and CELL_RANGE.
Logical Cell_Type(n) B11 Yes B12 Yes
name TRX nb No
HMI Cell Type Sub-syste OMC Cell Type No
Definition Combination of CELL_DIMENSION_TYPE, CELL_LAYER_TYPE,
CELL_PARTITION_TYPE, CELL_RANGE for an adjacent cell (OMC own cell or OMC external cell).
Rec ref. None Domai GSM Min value * Coded Min
n Max value * Coded Max
Spec ref. Handover Preparation Coded Max
Coding rules Single (0), Concentric (1), Umbrella (2), Micro (3), Umbrella Concentric (4), Mini (5), Extended Inner (6), Extended Outer (7), Mini Concentric (8), Micro Concentric (9),
Indoor (10), Indoor Concentric(11), GAN(12)
Mandatory rules - EN_SYNCHRONISED_HO shall be set to disabled when CELL_TYPE is equal to Extended inner or Extended outer.
- The GAN value is allowed only for external cells
Recommended --
rules
External *: possible values are:
comment - Single
- Umbrella
- Umbrella Concentric
- Micro
- Mini
- Micro Concentric
- Mini Concentric
- Indoor
- Indoor Concentric (labelled "Indoor Multiband" on the HMI)
- Extended Inner
- Extended Outer
- GAN
Internal comment Value computed according to CELL_DIMENSION_TYPE(n), CELL_LAYER_TYPE(n), CELL_PARTITION_TYPE(n) and CELL_RANGE(n).
For the GAN cells the OMC handles the cell type depending parameters similarly as for the single cells
Logical DTX_INDICATOR_FR B11 Yes B12 Yes
name TRX nb No
HMI DTX_FR_INDICATOR Sub-syste OMC Cell Type No
Definition Controls uplink DTX usage for GSM Phase 1 and 2 for FR. Applies for all codec types except AMR-NB and AMR-WB.
Coding rules 0: MS May Use DTX for FR
1: MS Shall Use DTX for FR,
2: MS shall not use DTX for FR
Mandatory rules The following combinations between DTX_INDICATOR_FR / DTX_INDICATOR_HR are possible (FR/HR):
may/shall, may/shall not, may/may, shall/shall, shall/shall not, shall/may, shall not/shall and shall not/shall not.
The only combination that is NOT allowed is: DTX_INDICATOR_FR = shall not and DTX_INDICATOR_HR = may, I.e. shall not/may.
Recommended --
rules
External --
comment
Internal comment --
Logical DTX_INDICATOR_FR_AMR B11 Yes B12 Yes
name TRX nb No
HMI DTX_FR_INDICATOR_AMR Sub-syste OMC Cell Type No
Definition Controls uplink DTX usage for GSM phase 2 MS. Applies only for AMR-NB FR.
Coding rules 0: MS may use DTX for AMR-NB FR,
1: MS shall use DTX for AMR-NB FR,
2: MS shall not use DTX for AMR-NB FR
Mandatory rules The following combinations between DTX_INDICATOR_FR_AMR / DTX_INDICATOR_HR_AMR are possible (FR_AMR / HR_AMR):
The only combination that is NOT allowed is: DTX_INDICATOR_FR_AMR = shall not and DTX_INDICATOR_HR_AMR = may, I.e. shall not/may.
Recommended The value 1 is recommended when EN_TFO_AMR_NB =1

rules
External --
comment
Internal comment --
Logical DTX_INDICATOR_HR B11 Yes B12 Yes
name TRX nb No
HMI DTX_HR_INDICATOR Sub-syste OMC Cell Type No
Definition Controls uplink DTX usage for GSM phase 2 for HR. Applies for all codec types except AMR-NB and AMR-WB.
Coding rules 0: MS May Use DTX for HR
1: MS Shall Use DTX for HR,
2: MS shall not use DTX for HR
Mandatory rules The following combinations between DTX_INDICATOR_FR / DTX_INDICATOR_HR are possible (FR/HR):
The only combination that is NOT allowed is: DTX_INDICATOR_FR = shall not and DTX_INDICATOR_HR = may, I.e. shall not/may.
Recommended --
rules
External --
comment
Internal comment --
Logical DTX_INDICATOR_HR_AMR B11 Yes B12 Yes
name TRX nb No
HMI DTX_HR_INDICATOR_AMR Sub-syste OMC Cell Type No
Definition Controls uplink DTX usage for GSM phase 2 MS. Applies only for AMR-NB HR.
Coding rules 0: MS may use DTX for AMR-NB HR,
1: MS shall use DTX for AMR-NB HR,
2: MS shall not use DTX for AMR-NB HR
Mandatory rules The following combinations between DTX_INDICATOR_FR_AMR / DTX_INDICATOR_HR_AMR are possible (FR_AMR / HR_AMR):
The only combination that is NOT allowed is: DTX_INDICATOR_FR_AMR = shall not and DTX_INDICATOR_HR_AMR = may, I.e. shall not/may.
Recommended The value 1 is recommended when EN_TFO_AMR_NB =1

rules
External --
comment
Internal comment --
Logical EN_LONG_TBF_WEIGHT(OMC) B11 No B12 Yes
name TRX nb No
HMI EN_LONG_TBF_WEIGHT Sub-syste OMC Cell Type No
Definition This flag indicates whether, or not, the long TBFs are scheduled with a higher weight than the
other TBFs.
Coding rules : disabled,
1: enabled
Mandatory rules - EN_LONG_TBF_WEIGHT(OMC) can not be enabled if EN_PFC_FEATURE = enabled,
- When EN_PFC_FEATURE = disabled, EN_LONG_TBF_WEIGHT(OMC) and EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) must have the same value.
Recommended --
rules
Logical EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) B11 No B12 Yes
name TRX nb No
HMI EN_RTS_ALLOC_ON_PACKET_SIZE Sub-syste OMC Cell Type No
Definition This flag indicates whether, or not, the number of allocated radio timeslot is based on packet size detection.
1: enabled
Mandatory rules - When EN_PFC_FEATURE = disabled, EN_LONG_TBF_WEIGHT(OMC) and EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) must have the same value.
Recommended --
rules
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the TBF established after modification
Logical FREQUENCY_RANGE(n) (OMC) B11 Yes B12 Yes
name TRX nb No
HMI FREQUENCY_RANGE Sub-syste OMC Cell Type No
Definition This parameter indicates the frequency range of the adjacent cell (internal or external to the OMC).
Spec ref. Normal Assignment Coded Max 7
Coding rules 0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850, 7: GAN, 8..255: for future use. The parameter shall be
coded over 8 bits as a provision for future frequency bands support.
Mandatory rules - if FREQUENCY_RANGE = "GSM-DCS" then CELL_PARTITION_TYPE must be equal to "Concentric" .
- if FREQUENCY_RANGE = GAN then CELL_RANGE must be equal to GAN.
- the value GAN is only allowed for the OMC external cells
- At cell creation
to
Recommended --
rules
External --
comment
Internal comment Values 4 and "5" are for Multiband cells.
m
Logical TRAFFIC_EV_PERIOD B11 Yes B12 Yes template
name TRX nb No
HMI TRAFFIC_EV_PERIOD Sub-syste OMC Cell Type No
Definition Periodicity of traffic load update in resource allocation algorithms = N_TRAFFIC_LOAD x A_TRAFFIC_LOAD x TCH_INFO_PERIOD.
Category Site (CAE) OMC-R access OMC local display Type Timer Unit sec
Coding rules --
Mandatory rules --
Recommended --
rules
External The given default value corresponds to the value calculated by the OMC, based on the values of N_TRAFFIC_LOAD (which depends on the nb of TRX in the cell, not
comment reflected by DLS default value), A_TRAFFIC_LOAD (which depends on the nb of TRX in the cell, not reflected by DLS default value), TCH_INFO_PERIOD.
Internal comment The parameter is displayed in minutes and seconds
TC parameters
Logical IPTCH_UDP_PORT_TC_MUX B11 Yes B12 Yes
name TRX nb No
HMI IPTCH_UDP_PORT_TC_MUX Sub-syste TC Cell Type No
name Instance TC RMS No
Definition UDP ports of IPTCH link used on TC side (for MUXTRAUP and TRAUP protocols).
Coding rules --
Mandatory rules --
Recommended The operator must ensure that the same UDP port must be declared for same BSC at different TC and that different UDP ports must be declared for different BSC at
rules same TC. Otherwise IPTCH does not work in a multi-TC environment.
External --
comment
Internal comment - Min = hD500, Max = hD517
- the BTS uses IPTCH_UDP_PORT_TC_MUX for Uplink traffic if EN_AUP_OVER_IP is disabled, and BSC uses it when EN_AUP_OVER_IP is enabled in "Mixed IP/TDM
A
interface" architecture (AUP_OVER_TDM_CODEC_SUP <> 0) to reach TC.
- min-max used in BSS_DL_MUXTRAUP_UDP_PORT.
Logical IPTCH_UDP_PORT_TC_NONMUX B11 Yes B12 Yes
name TRX nb No
HMI IPTCH_UDP_PORT_TC_NONMUX Sub-syste TC Cell Type No
Definition UDP ports used for TC-TC (eTRAUP) flow in UL.
Coding rules --
Mandatory rules Shall be an even number.

Shall be different from IPTCH_UDP_PORT_TC_MUX.
Recommended --
rules
External - IPTCH_UDP_PORT_TC_NONMUX for downlink flow = IPTCH_UDP_PORT_TC_NONMUX + 1.
comment - Meaningful in both A user plane over TDM or IP.
Internal comment - Min = hCD00, Max = hCD2E
Logical M2UA_SCTP_PORT_TC B11 Yes B12 Yes
name TRX nb No
HMI M2UA_SCTP_PORT_TC Sub-syste TC Cell Type No
Definition SCTP port used for IP_BSSAsig flow (M2UA/SCTP signalisation between BSC and TC and going to/coming from A interface), on TC side.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Min = hCD70, Max = hCD87.
Logical M2UA_SCTP_SG B11 Yes B12 Yes
name TRX nb No
HMI M2UA_SCTP_SG Sub-syste TC Cell Type No
Definition Defines on which processor (also called Signalling Gateway) in the TCIF board the IP_BSSAsig flow related to a dedicated BSC is handled.
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical M2UA_TC_IP_ADDRESS_SG1 B11 Yes B12 Yes
name TRX nb No
HMI M2UA_TC_IP_ADDRESS_SG1 Sub-syste TC Cell Type No
Definition IP address of the TC on the processor SG1, used for IP_BSSAsig flow (M2UA/SCTP signalling between BSC and TC and coming from/going to A interface)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Two addresses can be used because there are two M2UA/SCTP stacks on the TCIF board, this allows to manage the load sharing of the A signalling traffic towards
several BSCs.
Logical M2UA_TC_IP_ADDRESS_SG2 B11 Yes B12 Yes
name TRX nb No
HMI M2UA_TC_IP_ADDRESS_SG2 Sub-syste TC Cell Type No
Definition IP address of the TC on the processor SG2, used for IP_BSSAsig flow (M2UA/SCTP signalling between BSC and TC and coming from/going to A interface)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Two addresses can be used because there are two M2UA/SCTP stacks on the TCIF board, this allows to manage the load sharing of the A signalling traffic towards
several BSCs.
Logical SNMP_PRIORITY (TC) B11 Yes B12 Yes
name TRX nb No
HMI SNMP_PRIORITY (TC) Sub-syste TC Cell Type No
Definition BSS internal priority used by the TC for the SNMP flow in IP network
3: lower priority
Mandatory rules shall be consistent with the priority used by the OMC.
Recommended --
rules
External --
comment
Internal comment - Used to communicate with OMC.
Logical T_release B11 Yes B12 Yes
name TRX nb No
HMI T_release Sub-syste TC Cell Type No
Definition Maximum time after loss of synchronisation before TRAU returns to idle mode.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the software
Logical T_TC_IPTCHM_REPORTING_PERIOD B11 Yes B12 Yes
name TRX nb No
HMI T_TC_IPTCHM_REPORTING_PERIOD Sub-syste TC Cell Type No
Definition Reporting period of the IPTCHM by TCIF
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - hardcoded in TC-IF
Logical TC_TRAUP_IP_Address B11 Yes B12 Yes
name TRX nb No
HMI TC_TRAUP_IP_Address Sub-syste TC Cell Type No
Definition IP address of the TC, used for IPTCH flow (MUXTRAUP) and for TC-TC flow (eTRAUP).
Mandatory rules --
Recommended --
rules
External Meaningful in both A user plane over TDM or IP.
comment
Internal comment --
Logical TELECOM_IP_SUBNET_MASK_TC B11 Yes B12 Yes
name TRX nb No
HMI TELECOM_IP_SUBNET_MASK_TC Sub-syste TC Cell Type No
Definition Mask of the subnet where is allocated the range of TC addresses used for
telecom protocols
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical UL_TA_Late_Margin B11 Yes B12 Yes
name TRX nb No
HMI UL_TA_Late_Margin Sub-syste TC Cell Type No
Definition Minimum margin between TRAU Decoding Time and Late Arrival Limit
Coding rules step size = 0,250 msec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Logical VARIOUS_IP_PRIORITY (TC) B11 Yes B12 Yes
name TRX nb No
HMI VARIOUS_IP_PRIORITY (TC) Sub-syste TC Cell Type No
Definition BSS internal priority used by the TC for the DHCP, ICMP and ARP protocols in the IP network
3: lower priority
Mandatory rules --
Recommended Should be consistent with the priorities used by others NEs.

rules
Internal comment - In case of specific configurations using RIP or OSPF inside the TC, this parameter also gives the internal priority used by the routing protocol.
Default values for RMS templates
Template number
Logical name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
EN_BALANCED_CI 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
MEAS_STAT_BFI_i [1] 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
MEAS_STAT_BFI_i [2] 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MEAS_STAT_BFI_i [3] 4 4 4 4 4 4 4 4 4 4 4 4 4 6 4 4
MEAS_STAT_BFI_i [4] 6 6 6 6 6 6 6 6 6 6 6 6 6 10 6 6
MEAS_STAT_BFI_i [5] 8 8 8 8 8 8 8 8 8 8 8 8 8 14 8 8
MEAS_STAT_BFI_i [6] 10 10 10 10 10 10 10 10 10 10 10 10 10 18 10 10
MEAS_STAT_BFI_i [7] 14 14 14 14 14 14 14 14 14 14 14 14 14 20 14 14
MEAS_STAT_BFI_i [8] 18 18 18 18 18 18 18 18 18 18 18 18 18 22 18 18
MEAS_STAT_BFI_i [9] 22 22 22 22 22 22 22 22 22 22 22 22 22 24 22 22
MEAS_STAT_C_I_i [1] -12 0 -16 -12 0 -16 -12 0 -16 -12 0 -16 -12 -12 -12 -12
MEAS_STAT_C_I_i [2] -9 2 -14 -9 2 -14 -9 2 -14 -9 2 -14 -9 -9 -9 -9
MEAS_STAT_C_I_i [3] -6 4 -12 -6 4 -12 -6 4 -12 -6 4 -12 -6 -6 -6 -6
MEAS_STAT_C_I_i [4] -3 6 -10 -3 6 -10 -3 6 -10 -3 6 -10 -3 -3 -3 -3
MEAS_STAT_C_I_i [5] 0 8 -8 0 8 -8 0 8 -8 0 8 -8 0 0 0 0
MEAS_STAT_C_I_i [6] 3 10 -6 3 10 -6 3 10 -6 3 10 -6 3 3 3 3
MEAS_STAT_C_I_i [7] 6 12 -4 6 12 -4 6 12 -4 6 12 -4 6 6 6 6
MEAS_STAT_C_I_i [8] 9 14 -2 9 14 -2 9 14 -2 9 14 -2 9 9 9 9
MEAS_STAT_C_I_i [9] 12 16 0 12 16 0 12 16 0 12 16 0 12 12 12 12
MEAS_STAT_LEV_i [1] -53 -53 -53 -51 -51 -51 -60 -60 -60 -74 -74 -74 -53 -53 -53 -53
MEAS_STAT_LEV_i [2] -60 -60 -60 -55 -55 -55 -65 -65 -65 -78 -78 -78 -60 -60 -60 -60
MEAS_STAT_LEV_i [3] -66 -66 -66 -59 -59 -59 -70 -70 -70 -82 -82 -82 -66 -66 -66 -66
MEAS_STAT_LEV_i [4] -72 -72 -72 -63 -63 -63 -75 -75 -75 -86 -86 -86 -72 -72 -72 -72
MEAS_STAT_LEV_i [5] -79 -79 -79 -67 -67 -67 -80 -80 -80 -90 -90 -90 -79 -79 -79 -79
MEAS_STAT_LEV_i [6] -85 -85 -85 -71 -71 -71 -85 -85 -85 -94 -94 -94 -85 -85 -85 -85
MEAS_STAT_LEV_i [7] -91 -91 -91 -75 -75 -75 -90 -90 -90 -98 -98 -98 -91 -91 -91 -91
MEAS_STAT_LEV_i [8] -97 -97 -97 -79 -79 -79 -95 -95 -95 -102 -102 -102 -97 -97 -97 -97
MEAS_STAT_LEV_i [9] -104 -104 -104 -83 -83 -83 -100 -100 -100 -106 -106 -106 -104 -104 -104 -104
MEAS_STAT_PATH_BAL_i [1] -50 -50 -50 -50 -50 -50 -50 -50 -50 -50 -50 -50 -50 -50 -50 -20
MEAS_STAT_PATH_BAL_i [5] 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MEAS_STAT_S_i [1] 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
MEAS_STAT_S_i [2] 4 4 4 4 4 4 4 4 4 4 4 4 4 4 2 4
MEAS_STAT_S_i [3] 8 8 8 8 8 8 8 8 8 8 8 8 8 8 4 8
MEAS_STAT_S_i [4] 12 12 12 12 12 12 12 12 12 12 12 12 12 12 6 12
MEAS_STAT_S_i [5] 14 14 14 14 14 14 14 14 14 14 14 14 14 14 8 14
MEAS_STAT_S_i [6] 16 16 16 16 16 16 16 16 16 16 16 16 16 16 10 16
MEAS_STAT_S_i [7] 18 18 18 18 18 18 18 18 18 18 18 18 18 18 14 18
MEAS_STAT_S_i [8] 20 20 20 20 20 20 20 20 20 20 20 20 20 20 18 20
MEAS_STAT_S_i [9] 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22
MEAS_STAT_TA_i [1] 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
MEAS_STAT_TA_i [2] 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13
MEAS_STAT_TA_i [3] 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19
MEAS_STAT_TA_i [4] 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25
MEAS_STAT_TA_i [5] 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31
MEAS_STAT_TA_i [6] 37 37 37 37 37 37 37 37 37 37 37 37 37 37 37 37
MEAS_STAT_TA_i [7] 43 43 43 43 43 43 43 43 43 43 43 43 43 43 43 43
MEAS_STAT_TA_i [8] 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49
MEAS_STAT_TA_i [9] 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55
VQ_AVERAGE 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
VQ_BAD_RXFER 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
VQ_FER_THRESHOLD 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
VQ_GOOD_RXFER 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
VQ_INTF_THRESHOLD 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
VQ_RXLEV -95 -95 -95 -95 -95 -95 -95 -95 -95 -95 -95 -95 -95 -95 -95 -95
VQ_RXQUAL 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
VQ_RXQUAL_VS_RXFER 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
Default parameter values according to number of TRX in the cell
This table gives the default values according to the number of TRX in the cell for all parameters with "TRXnb" indicated in "Def value" column.
Parameter Name 1TRX 2TRX 3TRX 4TRX 5TRX 6TRX 7TRX 8TRX 9TRX 10TRX 11TRX 12TRX 13TRX 14TRX 15TRX 16TRX Comment
s
A_TRAFFIC_LOAD 4 4 8 8 12 12 12 12 12 12 12 12 12 12 12 12 Following
rule is
applied :
A_TRAFFIC
_LOAD x
N_TRAFFIC
_LOAD =
24
BTS_Q_LENGTH 4 4 6 6 10 10 10 10 10 10 10 10 10 10 10 10
Freelevel_1 1 2 3 3 4 5 5 6 7 7 8 8 9 9 10 10
Freelevel_2 2 3 5 6 7 9 10 12 13 14 16 17 19 20 22 21
Freelevel_3 4 7 10 12 14 17 20 23 26 28 31 34 37 40 44 47
Freelevel_4 6 9 12 15 21 26 30 34 38 42 47 51 56 61 67 74
Freelevel_DR(n) 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
H_LOAD_OBJ 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
HIGH_TRAFFIC_LOAD 70 70 80 80 80 80 80 80 80 80 80 80 80 80 80 80
HIGH_TRAFFIC_LOAD_GPR 70 70 70 80 80 80 80 80 80 80 80 80 80 80 80 80
S
IND_TRAFFIC_LOAD 45 45 60 60 60 60 60 60 60 60 60 60 60 60 60 60
L_LOAD_OBJ 0 10 20 40 40 40 40 40 40 40 40 40 40 40 40 40
LOW_TRAFFIC_LOAD 20 20 50 50 50 50 50 50 50 50 50 50 50 50 50 50
MULTIBAND_FORCED_DR_T 20 20 50 50 50 50 50 50 50 50 50 50 50 50 50 50
RAFFIC_CONDITION
N_TRAFFIC_LOAD 6 6 3 3 2 2 2 2 2 2 2 2 2 2 2 2
THR_FR_LOAD_L_SV1 0 20 30 40 40 40 40 40 40 40 40 40 40 40 40 40
THR_FR_LOAD_L_SV3 0 20 30 40 40 40 40 40 40 40 40 40 40 40 40 40
THR_FR_LOAD_L_VAMOS_ 0 20 30 40 40 40 40 40 40 40 40 40 40 40 40 40
FR
THR_FR_LOAD_L_VAMOS_ 0 20 30 40 40 40 40 40 40 40 40 40 40 40 40 40
HR
THR_FR_LOAD_U_SV1 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
THR_FR_LOAD_U_SV3 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
THR_FR_LOAD_U_VAMOS 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
_FR
THR_FR_LOAD_U_VAMOS 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70 70
_HR
Default parameter values according to the cell type
This table gives the default values according to Cell Type for all parameters with "CT" indicated in "Def value" column.
The default parameter values are all based on the Evolium product.
An asterix (*) means that the value of the parameter is not changeable.
Parameter Single Umbrella Concentric Concentric Concentric Concentric Microcell Minicell Extended Extended Indoor Concentric
Umbrella Microcell Minicell inner cell outer Microcell indoor
Microcell
A_ECNO_HO 8 8 8 8 4 8 4 8 8 8 4 4
A_LEV_HO 8 8 8 8 4 8 4 8 8 8 4 4
A_LEV_MCHO N/A N/A N/A N/A 2 N/A 2 N/A N/A N/A 2 2
A_PBGT_HO 12 12 12 12 6 12 6 12 12 12 6 6
A_QUAL_HO 8 8 8 8 4 8 4 8 8 8 4 4
BS_P_CON_ACK 3 3 3 3 2 3 2 3 3 3 2 2
BS_P_CON_INT 1 1 1 1 0 1 0 1 1 1 0 0
BS_TXPWR_ATTENUATION_IN N/A N/A # # # # N/A N/A N/A N/A N/A #

NER
BS_TXPWR_MAX_INNER (BSC) N/A N/A # # # # N/A N/A N/A N/A N/A #
CELL_DIMENSION_TYPE macro (0) * macro (0) * macro (0) * macro (0) * micro (1) * macro (0) * micro (1) * macro (0) * macro (0) * macro (0) * micro (1) * micro (1)*
CELL_DIMENSION_TYPE(n) macro (0) * macro (0) * macro (0) * macro (0) * micro (1) * macro (0) * micro (1) * macro (0) * macro (0) * macro (0) * micro (1) * micro (1)*
CELL_EV grade (1) grade (1) grade (1) grade (1) order (0) grade (1) order (0) grade (1) grade (1) grade (1) order (0) order (0)
CELL_LAYER_TYPE single (0) * upper (1) * single (0) * upper (1) * lower (2) * lower (2) * lower (2) * lower (2) * single (0) * single (0) * indoor (3) * indoor (3) *
Microcell
CELL_LAYER_TYPE(n) single (0) * upper (1) * single (0) * upper (1) * lower (2) * lower (2) * lower (2) * lower (2) * single (0) * single (0) * indoor (3) * indoor (3) *
CELL_PARTITION_TYPE normal (0) * normal (0) * concentric (1) concentric (1) * concentric concentric normal (0) * normal (0) * normal (0) * normal (0) * normal (0) concentric
* (1) * (1) *
CELL_PARTITION_TYPE(n) normal (0) * normal (0) * concentric (1) concentric (1) * concentric concentric normal (0) * normal (0) * normal (0) * normal (0) * normal (0) concentric
* (1) * (1) *
CELL_RANGE (BSC) normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * extended extended normal (0) * normal (0) *
inner (2) * outer (1) *
CELL_RANGE(n) (BSC) normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * normal (0) * extended extended normal (0) * normal (0) *
inner (2) * outer (1) *
DELTA_DEC_HO_margin 5 dB (5) 5 dB (5) 5 dB (5) 5 dB (5) 4 dB (4) 5 dB (5) 4 dB (4) 5 dB (5) 5 dB (5) 5 dB (5) 4 dB (4) 4 dB (4)
DELTA_INC_HO_margin 5 dB (5) 5 dB (5) 5 dB (5) 5 dB (5) 4 dB (4) 5 dB (5) 4 dB (4) 5 dB (5) 5 dB (5) 5 dB (5) 4 dB (4) 4 dB (4)
EN_BETTER_ZONE_HO N/A N/A enable (1) enable (1) enable (1) enable (1) N/A N/A N/A N/A N/A enable (1)
EN_DIST_HO enable (1) enable (1) enable (1) enable (1) disable (0) enable (1) disable (0) enable (1) enable (1) enable (1) disable (0) disable (0)
EN_LOAD_BALANCE N/A N/A disable (0) disable (0) disable (0) disable (0) N/A N/A N/A N/A N/A disable (0)
EN_MCHO_H_DL disable (0) disable (0) * disable (0) * disable (0) * enable (1) disable (0) * enable (1) disable (0) * disable (0) * disable (0) * enable (1) enable (1)
*
EN_MCHO_H_UL disable (0) disable (0) * disable (0) * disable (0) * enable (1) disable (0) * enable (1) disable (0) * disable (0) * disable (0) * enable (1) enable (1)
*
EN_MCHO_NCELL disable (0) enable (1) disable (0) * enable (1) disable (0) disable (0) disable (0) disable (0) disable (0) * disable (0) * disable (0) * disable (0)*
*
Microcell
EN_MCHO_RESCUE disable (0) disable (0) * disable (0) * disable (0) * enable (1) disable (0) * enable (1) disable (0) * disable (0) * disable (0) * enable (1) enable (1)
*
EN_PBGT_FILTERING enable (1) enable (1) enable (1) enable (1) disable (0) enable (1) disable (0) enable (1) disable (0) disable (0) disable (0) disable (0)
EN_RESCUE_UM N/A N/A N/A N/A enable (1) disable (0) enable (1) disable (0) N/A N/A enable (1) enable (1)
EN_RL_RECOV enable (1) enable (1) enable (1) enable (1) enable (1) enable (1) enable (1) enable (1) enable (1) enable (1) enable (1) enable (1)
EN_SPEED_DISC disable (0) disable (0) disable (0) * disable (0) disable (0) disable (0) disable (0) disable (0) disable (0) * disable (0) * disable (0) disable (0)
*
Freelevel_DR(n) See TRXnb See TRXnb See TRXnb See TRXnb See TRXnb See TRXnb See TRXnb See TRXnb 255 * 255 * See TRXnb See TRXnb
H_LOAD_OBJ N/A See TRXnb N/A See TRXnb N/A N/A N/A N/A N/A N/A N/A N/A
HO_MARGIN_DIST(0,n) 2 dB 2 dB 2 dB 2 dB 5 dB 2 dB 5 dB 2 dB -29 dB 5 dB 5 dB 5 dB
HO_MARGIN_LEV(0,n) 2 dB 2 dB 0 dB 0 dB 5 dB 0 dB 5 dB 0 dB -29 dB 5 dB 5 dB 5 dB
HO_MARGIN_QUAL(0,n) 1 dB 1 dB 1 dB 1 dB 5 dB 1 dB 5 dB 1 dB -29 dB 5 dB 5 dB 5 dB
HO_SDCCH_INHIBIT enable (0) enable (0) enable (0) enable (0) enable (0) enable (0) enable (0) enable (0) disabled (1) * disabled (1) enable (0) enable (0)
*
HOmargin (0,n) 5 dB 5 dB 5 dB 5 dB 4 dB 5 dB 4 dB 5 dB 5 dB 5 dB 4 dB 5 dB
L_LOAD_OBJ N/A See TRXnb N/A See TRXnb N/A N/A N/A N/A N/A N/A N/A N/A
L_RXLEV_DL_H -91 dBm -91 dBm (19) -91 dBm (19) -91 dBm (19) -96 dBm -91 dBm -96 dBm -91 dBm -96 dBm (14) -98 dBm -96 dBm -96 dBm
(19) (14) (19) (14) (19) (12) (14)
Microcell
L_RXLEV_NCELL_DR(n) -85 dBm -85 dBm (25) -85 dBm (25) -85 dBm (25) -70 dBm -85 dBm -70 dBm -85 dBm N/A N/A -70 dBm -70 dBm
(25) (40) (25) (40) (25) (40)
L_RXLEV_UL_H -100 dBm -100 dBm -100 dBm (10) -100 dBm (10) -100 dBm -100 dBm -100 dBm -100 dBm -100 dBm -100 dBm -100 dBm -100 dBm
(10) (10) (10) (10) (10) (10) (10) (10) (10)
L_RXLEV_UL_P -95 dBm -95 dBm (15) -95 dBm (15) -95 dBm (15) -85 dBm -95 dBm -85 dBm -95 dBm -95 dBm (15) -95 dBm -85 dBm -85 dBm
(15) (25) (15) (25) (15) (15) (25)
L_RXLEV_UL_P_VAMOS -92 dBm -92 dBm (18) -92 dBm (18) -92 dBm (18) -82 dBm -92 dBm -82 dBm -92 dBm -92 dBm (18) -92 dBm -82 dBm -82 dBm
(18) (28) (18) (28) (18) (18) (28)
L_TIME_ADVANCE N/A N/A N/A N/A N/A N/A N/A N/A N/A 0 N/A N/A
Loadfactor_2 -2 -2 -2 -2 -2 -2 -2 -2 0 0 -2 -2
Loadfactor_3 -5 -5 -5 -5 -4 -5 -4 -5 0 0 -4 -4
Loadfactor_4 -7 -7 -7 -7 -6 -7 -6 -7 0 0 -6 -6
Loadfactor_5 -10 -10 -10 -10 -8 -10 -8 -10 0 0 -8 -8
MIN_CONNECT_TIME N/A N/A N/A N/A 20 s 40 s 20 s 40 s N/A N/A 10 s 10 s
MS_P_CON_ACK 3s 3s 3s 3s 2s 3s 2s 3s 3s 3s 2s 2s
MS_P_CON_INT 1s 1s 1s 1s 0s 1s 0s 1s 1s 1s 0s 0s
MS_TXPWR_MAX_INNER N/A N/A # # # # N/A N/A N/A N/A N/A #
N_BAD_SACCH N/A N/A N/A N/A 4 N/A 4 N/A N/A N/A 4 4
N_BSTXPWR_M 13 13 13 13 15 13 15 13 13 13 15 15
Microcell
NEIGHBOUR_RXLEV(0,n) N/A N/A -47 dBm (63) -47 dBm (63) -47 dBm -47 dBm N/A N/A N/A N/A N/A -47 dBm
(63) (63)
OUTDOOR_UMB_LEV(0,n) N/A N/A N/A N/A -88 dBm -88 dBm -88 dBm -88 dBm N/A N/A -88 dBm -88 dBm
(22) (22) (22) (22) (22)
PENALTY_TIME(BSC) inhibited inhibited (31) inhibited (31) inhibited (31) 20 s (0) 20 s (0) 20 s (0) 20 s (0) inhibited (31) inhibited 20 s (0) 20 s (0)
(31) (31)
PENALTY_TIME(n)(BSC) inhibited inhibited (31) inhibited (31) inhibited (31) 20 s (0) 20 s (0) 20 s (0) 20 s (0) inhibited (31) inhibited 20 s (0) 20 s (0)
(31) (31)
RXLEV_DL_IH -65 dBm -65 dBm (45) -65 dBm (45) -65 dBm (45) -65 dBm -65 dBm -65 dBm -65 dBm -70 dBm (40) -60 dBm -65 dBm -65 dBm
(45) (45) (45) (45) (45) (50) (45)
RXLEV_DL_ZONE N/A N/A -71 dBm (39) -71 dBm (39) -71 dBm -71 dBm N/A N/A N/A N/A N/A -71 dBm
(39) (39)
RXLEV_LIMIT_PBGT_HO -65 dBm -65 dBm (45) -65 dBm (45) -65 dBm (45) -65 dBm -65 dBm -65 dBm -65 dBm -70 dBm (40) -60 dBm -65 dBm -65 dBm
(45) (45) (45) (45) (45) (50) (45)
RXLEV_UL_IH -75 dBm -75 dBm (35) -75 dBm (35) -75 dBm (35) -65 dBm -70 dBm -65 dBm -70 dBm -75 dBm (35) -75 dBm -65 dBm -65 dBm
(35) (45) (40) (45) (40) (35) (45)
RXLEV_UL_ZONE N/A N/A -78 dBm (32) -78 dBm (32) -78 dBm -78 dBm N/A N/A N/A N/A N/A -78 dBm
(32) (32)
RXLEVmin(n) -100 dBm -100 dBm -100 dBm (10) -100 dBm (10) -100 dBm -100 dBm -100 dBm -100 dBm -100 dBm -102 dBm -100 dBm -100 dBm
(10) (10) (10) (10) (10) (10) (10) (8) (10)
TEMPORARY_OFFSET 0 dB (0) 0 dB (0) 0 dB (0) 0 dB (0) infinity (7) infinity (7) infinity (7) infinity (7) 0 dB (0) 0 dB (0) infinity (7) infinity (7)
TEMPORARY_OFFSET(n) 0 dB (0) 0 dB (0) 0 dB (0) 0 dB (0) infinity (7) infinity (7) infinity (7) infinity (7) 0 dB (0) 0 dB (0) infinity (7) infinity (7)
Microcell
U_RXLEV_DL_MCHO N/A N/A N/A N/A -91 dBm N/A -91 dBm N/A N/A N/A -91 dBm -91 dBm
(19) (19) (19)
U_RXLEV_UL_MCHO N/A N/A N/A N/A -98 dBm N/A -98 dBm N/A N/A N/A -98 dBm -98 dBm
(12) (12) (12)
U_RXLEV_UL_P -85 dBm -85 dBm (25) -85 dBm (25) -85 dBm (25) -75 dBm -85 dBm -75 dBm -85 dBm -85 dBm (25) -85 dBm -75 dBm -75 dBm
(25) (35) (25) (35) (25) (25) (35)
U_RXLEV_UL_P_VAMOS -82 dBm -82 dBm (28) -82 dBm (28) -82 dBm (28) -72 dBm -82 dBm -72 dBm -82 dBm -82 dBm (28) -82 dBm -72 dBm -72 dBm
(28) (38) (28) (38) (28) (28) (38)
U_TIME_ADVANCE 35 km (63) 35 km (63) 35 km (63) 35 km (63) 1 km (2) 35 km (63) 1 km (2) 35 km (63) 34.5 km (62) 35 km (63) 500 m (1) 500 m (1)
W_LEV_MCHO N/A N/A N/A N/A 1 N/A 1 N/A N/A N/A 1 1
ZONE_TYPE N/A N/A # # # # N/A N/A N/A N/A N/A #
Alphabetic X-reference of table
All parameters given in this document are listed hereafter, by alphabetical order. The sub-system in which they are used is also provided.
Note: The table must be read from left to right, and then up to down.
3G_TDD_PMO_CODING MFS A_ECNO_HO BSC A_LEV_HO BSC
A_LEV_MCHO BSC A_LEV_PC BSC A_LEV_PC_VAMOS BSC
A_LEV_VAMOS_PAIRING BSC A_LEV_VAMOS_UNPAIRING BSC A_PBGT_DR BSC
A_PBGT_HO BSC A_QUAL_CA_FR_HR BSC A_QUAL_CA_HR_FR BSC
A_QUAL_HO BSC A_QUAL_PC BSC A_QUAL_PC_VAMOS BSC
A_QUAL_VAMOS_PAIRING BSC A_QUAL_VAMOS_UNPAIRING BSC A_RANGE_HO BSC
A_TRAFFIC_LOAD BSC ABIS_BANDWIDTH BSC ABORT_FRAME BTS
AC_0 BSC AC_1 BSC AC_11 BSC
AC_PRIORITY_LIST(priority=1) BSC AC_PRIORITY_LIST(priority=2) BSC AC_PRIORITY_LIST(priority=3) BSC
AC_PRIORITY_LIST(priority=4) BSC AC_PRIORITY_LIST(priority=5) BSC AC_PRIORITY_LIST(priority=6) BSC
ACCESS_BURST_TYPE MFS ACCESS_RATE_BC (MFS) MFS ACCESS_RATE_BC (OMC) OMC
ADD_HR_IN_TFO_LIST BSC ADDITIONAL_RESELECT_PARAM BSC ADDR_MON BSC
ADDR_TR BSC AG_FULL BTS AG_PREMPT_PCH BSC
ALLOC_ANYWAY BSC ALLOW_DTM_EDA_COMBINATION MFS ALPHA (BSC) BSC
ALPHA (MFS) MFS AMR_FR_HYST BSC AMR_FR_SUBSET BSC
AMR_FR_THR_1 BSC AMR_FR_THR_2 BSC AMR_FR_THR_3 BSC
AMR_HR_HYST BSC AMR_HR_SUBSET BSC AMR_HR_THR_1 BSC
AMR_HR_THR_2 BSC AMR_HR_THR_3 BSC AMR_START_MODE_FR BSC
AMR_START_MODE_HR BSC AMR_WB_GMSK_HYST_1 BSC AMR_WB_GMSK_HYST_2 BSC
AMR_WB_GMSK_THR_1 BSC AMR_WB_GMSK_THR_2 BSC ARC_SIZE_FACTOR MFS
ARFCN_3G(FDD) BSC ARFCN_3G(TDD) BSC ARFCN_LTE(FDD) BSC
ARFCN_LTE(TDD) BSC ASIG_IP_SUBNET_MASK_2_BSC BSC ASIG_IP_SUBNET_MASK_BSC BSC
ASIG_OVER_IP_PRIORITY BSC ASIG_SCTP_ENDPOINT_IP_Address_1 BSC ASIG_SCTP_ENDPOINT_IP_Address_2 BSC
ASIG_SCTP_ENDPOINT_LIST BSC ASIG_SCTP_ENDPOINT_PORT BSC ATER_GCH_EQUITY_MARGIN MFS
ATER_GCH_EQUITY_NB_LOWEST_TR MFS ATER_GCH_EQUITY_TIMER MFS Ater_Usage_Threshold MFS

X
Ater_Usage_Threshold_Short_Data MFS ATT (BSC) BSC ATT (MFS) MFS
AUP_IP_SUBNET_MASK_BSC BSC AUP_OVER_IP_CODEC_SUP BSC AUP_OVER_TDM_CODEC_SUP BSC
AUT_BAR BSC AUTO_DSC BSC B_NUM BSC
BANDWIDTH_PER_SIG_LINK BSC BANDWIDTH_PER_TCH_TS BSC Basic_Scheduling_Limit MFS
BCC (BSC) BSC BCC (MFS) MFS BCC (n) MFS
BCCH_ARFCN BSC BCCH_ARFCN(n)(BSC) BSC BCCH_ARFCN(n)(MFS) MFS
BCCH_CUT_TIMER BTS BCCH_EXT BSC BEP_PERIOD MFS
BEST_EFFORT_PRIORITY MFS BF_HI_RX BSC BF_HI_TX BSC
BF_LO_RX BSC BF_LO_TX BSC BFD_IP_ADDRESS_BTS BTS
BIAS_LIMIT MFS BIAS_LIMIT_EDA MFS BS_AG_BLKS_RES (BSC) BSC
BS_AG_BLKS_RES (MFS) MFS BS_CV_MAX (BSC) BSC BS_CV_MAX (MFS) MFS
BS_P_CON_ACK BSC BS_P_CON_INT BSC BS_PA_MFRMS (BSC) BSC
BS_PA_MFRMS (MFS) MFS BS_PAG_BLKS_RES MFS BS_PBCCH_BLKS MFS
BS_PRACH_BLKS MFS BS_PRR_BLKS MFS BS_PRR_BLKS_MPDCH MFS
BS_TXPWR_ATTENUATION BSC BS_TXPWR_ATTENUATION_INNER BSC BS_TXPWR_MAX (BSC) BSC
BS_TXPWR_MAX (MFS) MFS BS_TXPWR_MAX_INNER (BSC) BSC BS_TXPWR_MIN BSC
BSC_EN_RF_RES_IND BSC BSC_ID(n) MFS BSC_RSL_TID BSC
BSC_SSRC BSC BSC_X25_primary_address OMC BSC_X25_primary_address_i [1] BSC
BSC_X25_primary_address_i [10] BSC BSC_X25_primary_address_i [11] BSC BSC_X25_primary_address_i [12] BSC
BSC_X25_primary_address_i [8] BSC BSC_X25_primary_address_i [9] BSC BSC_X25_secondary_address OMC
BSC_X25_secondary_address_i [1] BSC BSC_X25_secondary_address_i [10] BSC BSC_X25_secondary_address_i [11] BSC
BSIC (GSM) BSC BSS_DL_MUXTRAUP_UDP_PORT BSC BSS_IP_SUBNET_MASK_BSC BSC
BSS_MAX_PAG_RATE BSC BSS_SEND_CM_ENQUIRY BSC BSS_TRANSPORT_MODE (BSC) BSC
BSS_TRANSPORT_MODE (MFS) MFS BSS_UL_MUXTRAUP_UDP_PORT BSC bssgp_T1 MFS
bssgp_T2 MFS bssgp_T3 MFS bssgp_T4 MFS
BTS_EN_RF_RES_IND BTS BTS_IP_Address BSC BTS_LOAD_FORGETTING_FACTOR MFS
BTS_Q_LENGTH BSC BTS_RSL_TID BSC BTS_VLAN_ID BTS
BVC_BLOCK_RETRIES MFS BVC_RESET_RETRIES MFS BVC_UNBLOCK_RETRIES MFS
C31_HYST MFS C32_QUAL MFS Call_user_data_sel BSC
CAPTURE_TRAFFIC_CONDITION BSC CBC_window BSC CBC_X25_primary_address BSC
CBC_X25_secondary_address BSC CBS MFS CCCH_CONF (BSC) BSC
CCCH_CONF (MFS) MFS CELL_BAR_ACCESS BSC CELL_BAR_QUALIFY BSC
CELL_CAPACITY_CLASS BSC CELL_CAPACITY_CLASS_SOURCE BSC CELL_CIPH_SET BSC
CELL_DIMENSION_TYPE BSC CELL_DIMENSION_TYPE(n) BSC CELL_EV BSC
CELL_LAYER_TYPE BSC CELL_LAYER_TYPE(n) BSC CELL_PARAMETER_3G_TDD BSC
CELL_PARTITION_TYPE BSC CELL_PARTITION_TYPE(n) BSC CELL_RANGE (BSC) BSC
CELL_RANGE (MFS) MFS CELL_RANGE(n) (BSC) BSC CELL_RESELECT_HYSTERESIS BSC
CELL_RESELECT_HYSTERESIS(n) BSC CELL_RESELECT_OFFSET (BSC) BSC CELL_RESELECT_OFFSET (MFS) MFS
CELL_RESELECT_OFFSET(n)(BSC) BSC CELL_RESELECT_OFFSET(n)(MFS) MFS CELL_RESELECT_PARAM_IND BSC
Cell_Type OMC Cell_Type(n) OMC CGI_3G_REQD BSC
CGI_REQD BSC CHANNEL_REQ_PERIOD MFS CHANNEL_REQ_THRES_GP2 MFS
CHANNEL_REQ_THRES_GP3 MFS CI (BSC) BSC CI (MFS) MFS
CI(n) (BSC) BSC CI(n) (MFS) MFS CI_3G BSC
CI_LTE BSC CI_SI BSC CIC BSC
CIR MFS CN_ID_PS MFS CONFIDENCE_ORIGIN MFS
CONFIDENCE_VS_ARC_FACTOR_SLO MFS CONFIDENCE_VS_RADIUS_SLOPE MFS COUNT_DECR BSC

PE
COUNT_I_THRESHOLD BSC COUNT_INCR_1 BSC COUNT_INCR_2 BSC
CRC_ERR BTS CRC_MON BSC CRC_TR BSC
CS_AVG_PERIOD_LT MFS CS_AVG_PERIOD_LT_DEF_VALUE MFS CS_AVG_PERIOD_ST MFS
CS_AVG_PERIOD_ST_DEF_VALUE MFS CS_BLER_DL_3_4 MFS CS_BLER_DL_4_3 MFS
CS_HST_DL_LT MFS CS_HST_DL_ST MFS CS_HST_UL_LT MFS
CS_HST_UL_ST MFS CS_MAX_IDLE_PERIOD MFS CS_QUAL_DL_1_2_FH_ACK MFS
CS_QUAL_DL_1_2_FH_NACK MFS CS_QUAL_DL_1_2_NFH_ACK MFS CS_QUAL_DL_1_2_NFH_NACK MFS
CS_QUAL_DL_2_3_FH_ACK MFS CS_QUAL_DL_2_3_FH_NACK MFS CS_QUAL_DL_2_3_NFH_ACK MFS
CS_QUAL_DL_2_3_NFH_NACK MFS CS_QUAL_DL_3_4_FH_ACK MFS CS_QUAL_DL_3_4_FH_NACK MFS
CS_QUAL_DL_3_4_NFH_ACK MFS CS_QUAL_DL_3_4_NFH_NACK MFS CS_QUAL_UL_1_2_FH_ACK MFS
CS_QUAL_UL_1_2_FH_NACK MFS CS_QUAL_UL_1_2_NFH_ACK MFS CS_QUAL_UL_1_2_NFH_NACK MFS
CS_QUAL_UL_2_3_FH_ACK MFS CS_QUAL_UL_2_3_FH_NACK MFS CS_QUAL_UL_2_3_NFH_ACK MFS
CS_QUAL_UL_2_3_NFH_NACK MFS CS_QUAL_UL_3_4_FH_ACK MFS CS_QUAL_UL_3_4_FH_NACK MFS
CS_QUAL_UL_3_4_NFH_ACK MFS CS_QUAL_UL_3_4_NFH_NACK MFS CS_SIR_DL_3_4_FH_ACK MFS
CS_SIR_DL_3_4_FH_NACK MFS CS_SIR_DL_3_4_NFH_ACK MFS CS_SIR_DL_3_4_NFH_NACK MFS
CS_SIR_HST_DL MFS Def_value_T_Flow_Ctrl_Cell MFS Def_value_T_Flow_Ctrl_MS MFS
DEFAULT_PRIORITY_3G BSC DEFAULT_QRXLEVMIN_3G BSC DEFAULT_THRESH_3G BSC
DELAY_FORCED_LOAD_REPORT MFS DELTA_DEC_HO_margin BSC DELTA_INC_HO_margin BSC
DELTA_SCPIR_VAMOS_PAIRING BSC DL_DTX_AMR_WB_GMSK BSC DL_POLL_FACTOR MFS
DLCI MFS DMA_OVERRUN BTS DMA_UNDERRUN BTS
DOWNLINK_DTX_ENABLE BSC Downlink_DTX_enable_AMR_FR BSC Downlink_DTX_enable_AMR_HR BSC
Downlink_DTX_enable_HR BSC DPC BSC DRX_TIMER_MAX (BSC) BSC
DRX_TIMER_MAX (MFS) MFS DSP_LOAD_FORGETTING_FACTOR MFS DSP_LOAD_THR_1 MFS
DSP_LOAD_THR_2 MFS DTX_INDICATOR (BSC) BSC DTX_INDICATOR (MFS) MFS
DTX_INDICATOR_FR OMC DTX_INDICATOR_FR_AMR OMC DTX_INDICATOR_HR OMC
DTX_INDICATOR_HR_AMR OMC DTX_INDICATOR_SACCH BSC DTX_INDICATOR_SACCH_AMR BSC
DTX_INDICATOR_SACCH_AMR_WB_G BSC DWELL_TIME_STEP BSC E_TX_EFFICIENCY_PERIOD MFS

MSK
E1_MTU BSC EBS MFS EC BSC
EC_BAR BSC ECSC BSC EDA_MS_ACTIVATION_LEVEL MFS
EDR_ASSIGN_FAIL_CAUSE BSC EDR_MSG_ORDER BSC EDR_QUEUING_MAINTAINED BSC
EDR_SEND_ASSIGN_FAIL BSC EFR_ENABLED BSC EGPRS_DL_Ack_Factor MFS
EGPRS_DL_ACK_factor_Satellite MFS EGPRS_LLC_THROUGHPUT_THR_1 MFS EGPRS_LLC_THROUGHPUT_THR_10 MFS
EGPRS_LLC_THROUGHPUT_THR_11 MFS EGPRS_LLC_THROUGHPUT_THR_2 MFS EGPRS_LLC_THROUGHPUT_THR_3 MFS
EGPRS_N3105_LIMIT MFS EGPRS_N3105_LIMIT_SATELLITE MFS EGPRS_UL_Ack_Factor MFS
EGPRS_UL_Ack_Factor_Satellite MFS EGSM_RR_ALLOC_STRATEGY BSC EN_2G_3G_HO_NO_SERVICE_HO BSC
EN_2G_TO_3G_CELL_RESELECTION BSC EN_2G_TO_3GTDD_CELL_RESELECTI BSC EN_2G_TO_LTEFDD_CELL_RESELECTI BSC

ON ON
EN_2G_TO_LTETDD_CELL_RESELECTI BSC EN_3G_DIVERSITY(FDD) BSC EN_3G_DIVERSITY(TDD) BSC

ON
EN_3G_HO BSC EN_4_DR_TRE_PER_TCU BSC EN_A_FLEX BSC
EN_A53_PREF_ALLOC_STRATEGY BSC EN_A53_PREF_ALLOC_STRATEGY_P BSC EN_AMR_CA_FR_HR BSC

S
EN_AMR_CA_FR_HR_ONLY_WHEN_L BSC EN_AMR_CA_HR_FR BSC EN_AMR_FR BSC

OADED
EN_AMR_HR BSC EN_AMR_WB_GMSK BSC EN_ASIG_OVER_IP BSC
EN_ASSIGN_FAIL_CIC_USED_NO_AC BSC EN_AUP_OVER_IP BSC EN_AUTONOMOUS_REROUTING MFS

TION
EN_BALANCED_CI BSC EN_BETTER_ZONE_HO BSC EN_BI-BAND_MS(n) BSC
EN_BS_PC BSC EN_BS_PC_PS MFS EN_BSS_OVRL_CLASS_BAR BSC
EN_BSS_PAGING_COORDINATION BSC EN_BSS_PAGING_COORDINATION MFS EN_CBL MFS
(BSC) (MFS)
EN_CIRCUIT_GROUP BSC EN_COMPRESSED_INTER_RAT_INFO BSC EN_CONV_GPS MFS
EN_CPICH_2G_3G_RESELECTION BSC EN_CS_ADAPTATION_ACK MFS EN_CS_ADAPTATION_NACK MFS
EN_DATA_144 BSC EN_DIST_HO BSC EN_DL_LLC_PDU_REROUTING MFS
EN_DL_RETRANS_BTS MFS EN_DPVA BSC EN_DR BSC
EN_DTM BSC EN_EDA MFS EN_EGPRS BSC
EN_EXT_DR BSC EN_EXT_MEAS_REP BSC EN_EXTENDED_UL_TBF MFS
EN_FACTOR_DELAYED_DL_TBF MFS EN_FAST_3G_RESELECTION BSC EN_FAST_INITIAL_GPRS_ACCESS MFS
EN_FAST_TRAFFIC_HO BSC EN_FAST_USF_UL_EXTENDED MFS EN_FORCED_DR BSC
EN_FR_IF_HR_PREF BSC EN_FULL_FAST_USF_UL_EXTENDED MFS EN_FULL_IR_DL_per_cell MFS
EN_GAN_HO BSC EN_GB_FLEX MFS EN_GENERAL_CAPTURE_HO BSC
EN_GPRS BSC EN_HR_FOR_AMR_WB_GMSK BSC EN_HSL BSC
EN_IC_HO BSC EN_IM_ASS_REJ BSC EN_INBAND_NOTIF BSC
EN_INBAND_PAGING BSC EN_INSTANT_MSG_SERVICE_QOS MFS EN_INT_HO_INITIATED_BY_MSC BSC
EN_INTERBAND_NEIGH BSC EN_INTFBD_PM BSC EN_INTRA_DL BSC
EN_INTRA_DL_AMR BSC EN_INTRA_DL_AMR_WB_GMSK BSC EN_INTRA_UL BSC
EN_INTRA_UL_AMR BSC EN_INTRA_UL_AMR_WB_GMSK BSC EN_INTRACELL_REPEATED BSC
EN_IP_CONGESTION_1ST_LEVEL BSC EN_IPE_PREF_CODEC_TYPE BSC EN_IR_UL_per_cell MFS
EN_IURG BSC EN_LB BSC EN_LB_NMR BSC
EN_LCS (BSC) BSC EN_LCS (MFS) MFS EN_LNK_M BSC
EN_LOAD_BALANCE BSC EN_LOAD_MNGT BSC EN_LOAD_ORDER BSC
EN_LOAD_OUTER BSC EN_LONG_TBF_WEIGHT(MFS) MFS EN_LONG_TBF_WEIGHT(OMC) OMC
EN_MA_SELECTION BSC EN_MCHO_H_DL BSC EN_MCHO_H_UL BSC
EN_MCHO_NCELL BSC EN_MCHO_RESCUE BSC EN_MCS_ADAPTATION_CONFIGURATI MFS

ON
EN_MCS1_in_CRP MFS EN_MORE_RMS_BCCH_BSIC BSC EN_MS_ASSISTED_AGPS MFS
EN_MS_BASED_AGPS MFS EN_MS_PC BSC EN_MULTIBAND_PBGT_HO BSC
EN_MULTISLOT_CLASS_30_33 MFS EN_NACC MFS EN_OUTGOING_GPRS_REDIR MFS
EN_OUTGOING_GPRS_REDIR(n) MFS EN_PAIRING_NON_SAIC_VAMOS1 BSC EN_PAIRING_NON_SAIC_VAMOS2 BSC
EN_PAIRING_SAIC_SAIC BSC EN_PAIRING_SAIC_VAMOS1 BSC EN_PAIRING_SAIC_VAMOS2 BSC
EN_PAIRING_VAMOS1_VAMOS1 BSC EN_PAIRING_VAMOS1_VAMOS2 BSC EN_PAIRING_VAMOS2_VAMOS2 BSC
EN_PBGT_FILTERING BSC EN_PBGT_HO BSC EN_PCR BSC
EN_PFC_FEATURE MFS EN_POWER_SAVING BSC EN_PREFERRED_BAND_FORCED_DR BSC
EN_PREFERRED_BAND_HO BSC EN_PRIORITY_ORDERING BSC EN_PSI_STATUS MFS
EN_PSI3_Coding2 MFS EN_RA_CAP_UPDATE MFS EN_RANDOMISE_FBL2 BSC
EN_RED_PDDCB MFS EN_REP_DL_FACCH BSC EN_REP_SACCH BSC
EN_RESCUE_UM BSC EN_RESEGMENTATION_UL_per_cell MFS EN_RESET_LB BSC
EN_RETURN_CS_ZONE_HO BSC EN_RIM_NACC MFS EN_RL_RECOV BSC
EN_RMS_IMPROVED BSC EN_RTS_ALLOC_ON_PACKET_SIZE(O OMC EN_RXLEV_DL BSC
MC)
EN_RXLEV_UL BSC EN_RXQUAL_DL BSC EN_RXQUAL_UL BSC
EN_SAGI MFS EN_SAIC_SCPIR_MODIF BSC EN_SEND_CM3 BSC
EN_SEND_OLD_CHAN_MODE BSC EN_SEND_SPEECH_VER BSC EN_SOLSA MFS
EN_SOLSA(n) MFS EN_SPECIFIC_PM BSC EN_SPEED_DISC BSC
EN_STREAMING MFS EN_SYNCHRONISED_HO BSC EN_TCH_PREEMPT BSC
EN_TEST_FOR_NON_SAIC BSC EN_TFO BSC EN_TFO_AMR_NB BSC
EN_TFO_AMR_WB BSC EN_TFO_MATCH BSC EN_TFO_OPT BSC
EN_TRAFFIC_HO(0,n) BSC EN_UL_CONGESTION MFS EN_UNEQUIPPED_CIRCUIT BSC
EN_UPLINK_REPLY BSC EN_VAMOS BSC EN_VAMOS_NASS BSC
EN_VAMOS_NON_AMR BSC EN_VAMOS_PAIRING_CA BSC EN_VAMOS_SUB_SAIC_BLACKLIST BSC
EN_VAMOS_UNPAIRING_CA BSC EN_VGCS BSC ENH_UL_INTERF_MEAS BSC
Estimated_Speed_CS_FAMILY_0 MFS Estimated_Speed_CS_FAMILY_1 MFS Estimated_Speed_CS_FAMILY_2 MFS
Estimated_Speed_CS_FAMILY_3 MFS Estimated_Speed_CS_FAMILY_4 MFS Estimated_Speed_CS_FAMILY_5 MFS
Estimated_Speed_CS_FAMILY_6 MFS Estimated_Speed_CS_FAMILY_7 MFS EXT_HO_FORCED BSC
FACTOR_DELAYED_DL_TBF MFS FAKE_FDD_MANAGEMENT BSC FDD_ARFCN_LIST BSC
FDD_GPRS_Qoffset MFS FDD_MULTIRAT_REPORTING BSC FDD_Qmin(BSC) BSC
FDD_Qmin_Offset BSC FDD_Qoffset (BSC) BSC FDD_REP_QUANT BSC
FDD_REPORTING_OFFSET BSC FDD_REPORTING_THRESHOLD BSC FDD_RSCPmin BSC
Filter_Suspend_Cause BSC FLOW_DIM_Safety_BVC MFS FLOW_DIM_Safety_MS MFS
FORBID_AMR_NS BSC FORBID_DTXD_NH_BCCH_F BSC FORCE_TFO_HR_WHEN_LOADED BSC
FORCE_TFO_VS_AMR BSC FR_INFO_SIZE MFS FRAME_DISCARD BTS
Freefactor_1 BSC Freefactor_2 BSC Freefactor_3 BSC
Freefactor_4 BSC Freefactor_5 BSC Freelevel_1 BSC
Freelevel_2 BSC Freelevel_3 BSC Freelevel_4 BSC
Freelevel_DR(n) BSC FREQ_SYNC_GRAD_CONV_EDGE BSC FREQ_SYNC_GRAD_CONV_THRES BSC
FREQ_SYNC_MAX_INITIAL_EVAL BSC FREQ_SYNC_MIN_NBR_EVAL BSC FREQ_SYNC_POLL_PER_EVAL BSC
FREQ_SYNC_POLLING_TIME_INITIAL BSC FREQ_SYNC_POLLING_TIME_SUSTAI BSC FREQ_SYNC_SUCCESS_RATIO BSC

NED
FREQUENCY_RANGE BSC FREQUENCY_RANGE(n) (MFS) MFS FREQUENCY_RANGE(n) (OMC) OMC
FTP_PRIORITY (BSC) BSC FTP_PRIORITY (BTS) BTS FULL_FAST_USF_UL_EXTENDED MFS
GAMMA_TNx MFS Gb_Configuration_Type MFS Gb_Data_PRIORITY MFS
Gb_Signalling_PRIORITY MFS Gb_Transport_Mode MFS Gb_Transport_Mode_per_NSE MFS
GCH_RED_FACTOR_High_Ater_Usage MFS GEOGRAPHICAL_COORDINATES_FLA MFS GERAN_PRIORITY BSC

G
GPRS_CELL_RESELECT_HYSTERESIS MFS GPRS_DL_Ack_period MFS GPRS_DL_Ack_period_Satellite MFS
GPRS_HCS_THR MFS GPRS_HCS_THR(n) MFS GPRS_LLC_THROUGHPUT_THR_1 MFS
GPRS_LLC_THROUGHPUT_THR_10 MFS GPRS_LLC_THROUGHPUT_THR_2 MFS GPRS_LLC_THROUGHPUT_THR_3 MFS
GPRS_MS_TXPWR_MAX_CCH MFS GPRS_MS_TXPWR_MAX_CCH(n) MFS GPRS_MULTISLOT_CLASS_CONG_IM MFS
GPRS_MULTISLOT_CLASS_DEF_VAL MFS GPRS_PENALTY_TIME(n) MFS GPRS_PRIORITY_CLASS MFS

UE
GPRS_PRIORITY_CLASS(n) MFS GPRS_RESELECTION_OFFSET(n) MFS GPRS_RXLEV_ACCESS_MIN MFS
GPRS_RXLEV_ACCESS_MIN(n) MFS GPRS_TEMPORARY_OFFSET(n) MFS GPRS_UL_Ack_period MFS
GPRS_UL_Ack_period_Satellite MFS GPU_BUFFER_CONGESTION_THR_1_ MFS GPU_BUFFER_CONGESTION_THR_1_ MFS

XOFF XON
GPU_BUFFER_CONGESTION_THR_2 MFS GPU_Gb_Base_IP MFS GPU_Gb_Base_UDP MFS
GPU_Gb_IP_Address MFS GPU_Gb_UDP_Port MFS GSL_LOSS_RESET_DATA MFS
GSL_PRIORITY (BSC) BSC GSL_PRIORITY (MFS) MFS GSM_PHASE BSC
H_LOAD_OBJ BSC H_MIN_DWELL_TIME BSC H_PRIO BSC
HALFPWR_BEAM_WIDTH MFS HIGH_PRECEDENCE_BACKGROUND_P MFS HIGH_PRECEDENCE_INSTANT_MSG_P MFS

RIORITY RIORITY
HIGH_PRECEDENCE_THP1_PRIORITY MFS HIGH_PRECEDENCE_THP2_PRIORITY MFS HIGH_PRECEDENCE_THP3_PRIORITY MFS
HIGH_TRAFFIC_LOAD BSC HIGH_TRAFFIC_LOAD_GPRS BSC HO_INTERCELL_ALLOWED BSC
HO_INTRACELL_ALLOWED BSC HO_MARGIN_DIST(0,n) BSC HO_MARGIN_LEV(0,n) BSC
HO_MARGIN_QUAL(0,n) BSC HO_SDCCH_INHIBIT BSC HOmargin (0,n) BSC
HR_ENABLED BSC I_LAPD_MAX_RX BTS I_LAPD_MAX_TX BTS
I_TX_LAPD BSC IEUTM_MAX_IDLE_PERIOD MFS IGNORE_2MBIT_FAIL BSC
INACT_DLCI BTS INBAND_PAGING_THR BSC IND_TRAFFIC_LOAD BSC
INIT_PDCH_SHORT_DATA_EGPRS MFS INIT_PDCH_SHORT_DATA_GPRS MFS INTAVE BSC
INTFBD1 BSC INTFBD2 BSC INTFBD3 BSC
INTFBD4 BSC INTFBD5 BSC INVALID_ADR BTS
IP_BTS_LOAD_THR_1 MFS IP_BTS_LOAD_THR_2 MFS IP_CONGESTION_FILTER_WS BSC
IP_CONGESTION_JITTER_THRESHOLD BSC IP_CONGESTION_PREVENTIVE_THRES BSC IP_CONGESTION_TIMER BSC

HOLD
IP_PFC_PRIORITY_MAPPING MFS IPBSS_SUBNET_MASK_MFS MFS IPGB_SUBNET_MASK_MFS MFS
IPGCH_Base_Address_MFS MFS IPGCH_DL_BW_CONTROL_REPEAT_R MFS IPGCH_IP_Address_MFS MFS

ATE
IPGCH_PACKET_SIZE BSC IPGCH_UL_BW_CONTROL_REPEAT_R MFS IPGCHC_Base_TCP_MFS MFS

ATE
IPGCHC_PRIORITY (BTS) BTS IPGCHC_PRIORITY (MFS) MFS IPGCHC_TCP_PORT_BTS (BSC) BSC
IPGCHC_TCP_PORT_BTS (BTS) BTS IPGCHU_ACK_SEND_THRESHOLD MFS IPGCHU_Base_UDP_MFS MFS
IPGCHU_BE_PRIORITY (BTS) BTS IPGCHU_BE_PRIORITY (MFS) MFS IPGCHU_BE_UL_THRES MFS
IPGCHU_BW_MAX_CONG_DL MFS IPGCHU_BW_MAX_CONG_UL MFS IPGCHU_BW_MIN_CONG_DL MFS
IPGCHU_BW_MIN_CONG_UL MFS IPGCHU_DELAY_HIGH_THRES_DL BSC IPGCHU_DELAY_HIGH_THRES_UL BSC
IPGCHU_DELAY_LOW_THRES_DL BSC IPGCHU_DELAY_LOW_THRES_UL BSC IPGCHU_ExtraGBR_UL_THRES MFS
IPGCHU_GBR_PRIORITY (BTS) BTS IPGCHU_GBR_PRIORITY (MFS) MFS IPGCHU_GBR_UL_THRES MFS
IPGCHU_MAX_PATTERN_MEAS_THRO MFS IPGCHU_Nominal_Abis_BW_Factor MFS IPGCHU_PATTERN_LIFETIME_DL MFS

UGHPUT_DL
IPGCHU_UDP_MAX_WINDOW_SIZE_G BTS IPGCHU_UDP_MAX_WINDOW_SIZE_G BTS IPGCHU_UDP_MAX_WINDOW_SIZE_G MFS

34_G5 P
IPGCHU_UDP_MAX_WINDOW_SIZE_M BTS IPGCHU_UDP_PORT_BTS BTS IPGCHU_UDP_PORT_MFS MFS

C
IPGCHU_XOFF_BE_FIFO_DL_THRESH MFS IPGCHU_XOFF_GBR_FIFO_DL_THRES MFS IPGCHU_XON_BE_FIFO_DL_THRESHO MFS
OLD HOLD LD
IPGCHU_XON_GBR_FIFO_DL_THRESH MFS IPGSL_Base_Address_MFS MFS IPGSL_BASE_TCP_MFS MFS

OLD
IPGSL_IP_Address_BSCside (BSC) BSC IPGSL_IP_Address_BSCside (MFS) MFS IPGSL_IP_Address_MFSside (BSC) BSC
IPGSL_IP_Address_MFSside (MFS) MFS IPGSL_MSS (BSC) BSC IPGSL_MSS (MFS) MFS
IPGSL_TCP_PORT_BSCside (BSC) BSC IPGSL_TCP_PORT_BSCside (MFS) MFS IPGSL_TCP_PORT_MFSside (BSC) BSC
IPGSL_TCP_PORT_MFSside (MFS) MFS IPTCH_UDP_PORT_BTS BTS IPTCH_UDP_PORT_TC_MUX TC
IPTCH_UDP_PORT_TC_NONMUX TC IURG_IP_SUBNET_MASK_BSC BSC IURG_PRIORITY BSC
IURG_SCTP_ENDPOINT_IP_ADDRESS_ BSC IURG_SCTP_ENDPOINT_IP_ADDRESS_ BSC IURG_SCTP_ENDPOINT_LIST BSC

12
IURG_SCTP_ENDPOINT_PORT BSC K_GSL (BSC) BSC K_GSL (MFS) MFS
K_LAPD_OML BTS K_LAPD_RSL BTS K_LAPDm BTS
K_VAL_OML_16K_satellite BSC K_VAL_OML_16K_terrestrial BSC K_VAL_OML_64K_satellite BSC
K_VAL_OML_64K_terrestrial BSC K_VAL_RSL_16K_satellite BSC K_VAL_RSL_16K_terrestrial BSC
K_VAL_RSL_64K_satellite BSC K_VAL_RSL_64K_terrestrial BSC KEEP_CODEC_HO BSC
L_LOAD_OBJ BSC L_MIN_DWELL_TIME BSC L_RXLEV_CPT_HO(0,n) BSC
L_RXLEV_DL_H BSC L_RXLEV_DL_P BSC L_RXLEV_DL_P_VAMOS BSC
L_RXLEV_MULTIBAND_FORCED_DR(0 BSC L_RXLEV_NCELL_DR(n) BSC L_RXLEV_UL_H BSC

,n)
L_RXLEV_UL_P BSC L_RXLEV_UL_P_VAMOS BSC L_RXQUAL_DL_H BSC
L_RXQUAL_DL_H_AMR BSC L_RXQUAL_DL_H_AMR_WB_GMSK BSC L_RXQUAL_DL_P BSC
L_RXQUAL_DL_P_AMR BSC L_RXQUAL_DL_P_AMR_RXACCH BSC L_RXQUAL_DL_P_AMR_RXACCH_VA BSC
MOS
L_RXQUAL_DL_P_AMR_VAMOS BSC L_RXQUAL_DL_P_VAMOS BSC L_RXQUAL_UL_H BSC
L_RXQUAL_UL_H_AMR BSC L_RXQUAL_UL_H_AMR_WB_GMSK BSC L_RXQUAL_UL_P BSC
L_RXQUAL_UL_P_AMR BSC L_RXQUAL_UL_P_AMR_RXACCH BSC L_TIME_ADVANCE BSC
LAC (BSC) BSC LAC (MFS) MFS LAC(n) (BSC) BSC
LAC(n) (MFS) MFS LAC_3G BSC LB_DECR BSC
LB_INCR BSC LB_IP_SUBNET_MASK_BSC BSC LB_MIN_NB_ACTIVE_IPSP BSC
LB_PRIORITY BSC LB_SCTP_ENDPOINT_IP_ADDRESS_1 BSC LB_SCTP_ENDPOINT_IP_ADDRESS_2 BSC
LB_SCTP_ENDPOINT_LIST BSC LB_SCTP_ENDPOINT_PORT BSC LCS_AZIMUTH MFS
LCS_LATITUDE MFS LCS_LONGITUDE MFS Length_On_Going_Requests_ListA_HI MFS

GH_CAP
Length_On_Going_Requests_ListA_L MFS Length_On_Going_Requests_ListB_HI MFS Length_On_Going_Requests_ListB_L MFS

OW_CAP GH_CAP OW_CAP
Length_Suspended_Requests_Queue MFS Length_Suspended_Requests_Queue MFS Linkfactor (0,n) BSC

A_GP B_GP
LOAD_EV_PERIOD BSC LOAD_EV_PERIOD_GPRS BSC Loadfactor_1 BSC
Loadfactor_2 BSC Loadfactor_3 BSC Loadfactor_4 BSC
Loadfactor_5 BSC Loadlevel_1 BSC Loadlevel_2 BSC
Loadlevel_3 BSC Loadlevel_4 BSC LOCAL_ASIG_SCTP_ENDPOINT_IP_Ad BSC

dress_1
LOCAL_ASIG_SCTP_ENDPOINT_IP_AD BSC LOCAL_ASIG_SCTP_ENDPOINT_PORT BSC LOCAL_IURG_SCTP_ENDPOINT_IP_AD BSC

DRESS_2 DRESS_1
LOCAL_IURG_SCTP_ENDPOINT_PORT BSC LOCAL_LB_SCTP_ENDPOINT_IP_ADD BSC LOCAL_LB_SCTP_ENDPOINT_PORT BSC
RESS_1
LONG_TBF_SIZE MFS LONG_TBF_WEIGHT MFS LOW_PRECEDENCE_BACKGROUND_P MFS

RIORITY
LOW_PRECEDENCE_INSTANT_MSG_P MFS LOW_PRECEDENCE_THP1_PRIORITY MFS LOW_PRECEDENCE_THP2_PRIORITY MFS

RIORITY
LOW_PRECEDENCE_THP3_PRIORITY MFS LOW_TRAFFIC_LOAD BSC LSA_ID_array (BSC) BSC
LSA_ID_array (MFS) MFS LSA_ID_array (n) MFS LSA_OFFSET BSC
M_PEND_A (BTS) BTS M_PEND_A (G2 BSC) BSC M_PEND_A (MX BSC) BSC
M1 BSC M2 BSC M2UA_SCTP_PORT_BSC BSC
M2UA_SCTP_PORT_TC TC M2UA_SCTP_PRIORITY BSC M2UA_SCTP_SG TC
M2UA_TC_IP_ADDRESS_SG1 TC M2UA_TC_IP_ADDRESS_SG2 TC MATE_CI (BSC) BSC
MATE_CI (MFS) MFS MATE_LAC BSC MAX_ADJ_CELL MFS
MAX_AGCH_QUEUING_DELAY MFS MAX_BLER MFS MAX_CELLS_GP MFS
MAX_CTXT_CELLS_GP MFS MAX_CTXT_MS_GP2 MFS MAX_CTXT_MS_GP3 MFS
MAX_CTXT_TBF_GP2 MFS MAX_CTXT_TBF_GP3 MFS MAX_CTXT_TRX_GP MFS
MAX_DL_TBF_SPDCH MFS MAX_EGPRS_MCS MFS MAX_EGPRS_MCS_SHORT_DATA_DL MFS
MAX_EGPRS_MCS_SHORT_DATA_UL MFS MAX_GCH_DSP_GP MFS MAX_GP_PER_BSS MFS
Max_GPRS_assign_agch_retrans MFS Max_GPRS_assign_pch_retrans MFS MAX_GPRS_CS BSC
MAX_GPRS_CS_SHORT_DATA_DL MFS MAX_GPRS_CS_SHORT_DATA_UL MFS MAX_IMSI_SAVED BSC
MAX_LAPDM BSC MAX_LAPS BSC MAX_LLC_PDU_Lifetime MFS
MAX_MPDCH_DSP_GP MFS MAX_MPDCH_PTU_IP MFS MAX_NB_ASIG_SCTP_ENDPOINT BSC
MAX_NB_IURG_SCTP_ENDPOINT BSC MAX_NB_LB_SCTP_ENDPOINT BSC Max_Nb_Tcorr_Start MFS
MAX_PAGING_QUEUE MFS MAX_PDCH (G2 BSC) BSC MAX_PDCH (MFS) MFS
MAX_PDCH (MX BSC) BSC MAX_PDCH_HIGH_LOAD (G2 BSC) BSC MAX_PDCH_HIGH_LOAD (MFS) MFS
MAX_PDCH_HIGH_LOAD (MX BSC) BSC MAX_PDCH_PER_TBF MFS MAX_PDCH_PTU_GP2 MFS
MAX_PDCH_PTU_GP3 MFS MAX_PDCH_PTU_IP_G3_G4 MFS MAX_PDCH_PTU_IP_G5 MFS
MAX_PDCH_PTU_IP_MC MFS MAX_PFC_NUMBER_GP2 MFS MAX_PFC_NUMBER_GP3 MFS
MAX_POW_INC BSC MAX_POW_INC_VAMOS BSC MAX_POW_RED BSC
MAX_POW_RED_DYN MFS MAX_POW_RED_USF_8PSK MFS MAX_POW_RED_USF_GMSK MFS
MAX_POW_RED_VAMOS BSC Max_PPCH_DRX_Occurrences MFS Max_PPCH_Non_DRX_Lifetime MFS
MAX_PPCH_QUEUING_DELAY MFS MAX_RADIUS_FACTOR MFS Max_Rate_Safety MFS
Max_Resel_Duration MFS Max_retrans (BSC) BSC Max_retrans (MFS) MFS
MAX_RETRANS_1 MFS MAX_RETRANS_2 MFS MAX_RETRANS_3 MFS
MAX_RETRANS_4 MFS Max_retrans_DL MFS MAX_RETRANS_PAGING_EXT MFS
MAX_Retrans_SIG MFS MAX_RLC_blks_PTU_G3_IP MFS MAX_RLC_blks_PTU_G4_IP MFS
MAX_RLC_blks_PTU_G5_IP MFS MAX_RLC_BLKS_PTU_GP2 MFS MAX_RLC_BLKS_PTU_GP3 MFS
MAX_RLC_blks_PTU_MC_IP MFS MAX_TBF_CELL_DL MFS MAX_TBF_CELL_UL MFS
MAX_TBF_PTU_G3_IP MFS MAX_TBF_PTU_G4_IP MFS MAX_TBF_PTU_G5_IP MFS
MAX_TBF_PTU_GP2 MFS MAX_TBF_PTU_GP3 MFS MAX_TBF_PTU_MC_IP MFS
MAX_TBF_TRX_DL_GP MFS MAX_TBF_TRX_UL_GP MFS MAX_TCH_HALF_RATE BSC
MAX_TCH_PER_CCP_900E BSC MAX_TRC_NUMBER BSC MAX_TRX_DSP_GP MFS
MAX_TRX_GP MFS MAX_TRX_PTU_IP_G3_G4 MFS MAX_TRX_PTU_IP_G5 MFS
MAX_TRX_PTU_IP_MC MFS MAX_UL_TBF_SPDCH MFS MAX_VGCS_TS BSC
Maximum_Credit MFS Maximum_Weight MFS MCC (BSC) BSC
MCC (MFS) MFS MCC(n) (BSC) BSC MCC(n) (MFS) MFS
MCC_3G BSC MCC_LTE BSC MCS_ADAPTATION_SET_SELECTION MFS
MCS_AVG_PERIOD MFS MCS_AVG_PERIOD_DEF_VALUE MFS MEAS_RES_DISCARDED_i [1] BSC
MEAS_RES_DISCARDED_i [10] BSC MEAS_RES_DISCARDED_i [2] BSC MEAS_RES_DISCARDED_i [3] BSC
MEAS_STAT_BFI_i [1] BSC MEAS_STAT_BFI_i [2] BSC MEAS_STAT_BFI_i [3] BSC
MEAS_STAT_C_I_i [1] BSC MEAS_STAT_C_I_i [2] BSC MEAS_STAT_C_I_i [3] BSC
MEAS_STAT_LEV_i [1] BSC MEAS_STAT_LEV_i [2] BSC MEAS_STAT_LEV_i [3] BSC
MEAS_STAT_PATH_BAL_i [1] BSC MEAS_STAT_PATH_BAL_i [2] BSC MEAS_STAT_PATH_BAL_i [3] BSC
MEAS_STAT_S_i [1] BSC MEAS_STAT_S_i [2] BSC MEAS_STAT_S_i [3] BSC
MEAS_STAT_TA_i [1] BSC MEAS_STAT_TA_i [2] BSC MEAS_STAT_TA_i [3] BSC
MEASUREMENT_BANDWIDTH BSC MIN_CONNECT_TIME BSC MIN_NB_ACTIVE_IPSP BSC
MIN_PDCH (G2 BSC) BSC MIN_PDCH (MFS) MFS MIN_PDCH (MX BSC) BSC
MIN_RADIUS_FACTOR MFS MIN_RLF_TIME_DL MFS MIN_THROUGHPUT_GAIN MFS
MIN_TIME_BTW_VAMOS_PAIRING BSC MIN_VGCS_TS BSC Minimum_Credit_Weight MFS
MNC (BSC) BSC MNC (MFS) MFS MNC(n) (BSC) BSC
MNC(n) (MFS) MFS MNC_3G BSC MNC_LTE BSC
MPDCH_LOAD_PERIOD MFS MS_BASED_AGPS_ASSIST_DATA_LI MFS MS_P_CON_ACK BSC

ST
MS_P_CON_INT BSC MS_TIME_TO_SWITCH_TO_NEW_PDC MFS MS_TXPWR_MAX BSC

H
MS_TXPWR_MAX(n) BSC MS_TXPWR_MAX_CCH (BSC) BSC MS_TXPWR_MAX_CCH (MFS) MFS
MS_TXPWR_MAX_CCH(n)(BSC) BSC MS_TXPWR_MAX_CCH(n)(MFS) MFS MS_TXPWR_MAX_INNER BSC
MS_TXPWR_MIN BSC MSC_CN_ID BSC MSC_MCC BSC
MSC_MNC BSC MSC_OFFLOAD_STATE BSC MSC_SPC BSC
MSC_WEIGHT BSC MSCR (G2 BSC) BSC MSCR (MFS) MFS
MSCR (MX BSC) BSC MTP_Sequence_Number_Format BSC MTP3_WB_INTERWORKING BSC
MULTIBAND_FORCED_DR_TRAFFIC_C BSC MULTIBAND_REPORTING (BSC) BSC MULTIBAND_REPORTING (MFS) MFS

ONDITION
MULTIBAND_TRAFFIC_CONDITION BSC MUXRTP_SIZE BSC MUXRTP_UDP_PORT_MASK BSC
MUXRTP_UDP_PORT_START BSC MUXTRAUP_IP_ADDRESS_BSC BSC MUXTRAUP_SIZE BSC
N_ATER_TS_MARGIN_GPU MFS N_AVG_I (BSC) BSC N_AVG_I (MFS) MFS
N_BAD_SACCH BSC N_BIAS_DETERMINATION MFS N_BSTXPWR_M BSC
N_CANDIDATE_FOR_REALLOC MFS N_CLR_REQ BSC N_DATA_BYTES_MAX_TRANS MFS
N_DATA_BYTES_MAX_TRANS_PERIO MFS N_DECR BTS N_DELAYED_HO_CAUSE30 BSC

DIC
N_GCH_FAST_PS_ACCESS MFS N_INCR BTS N_MAX_PERIODIC_REALLOC_ATTEMP MFS

T_T3
N_MAX_PERIODIC_REALLOC_ATTEMP MFS N_MAX_PERIODIC_REALLOC_SUCCES MFS N_PDCH_Release MFS

T_T4 S_T3
N_POLLING_EUTM_LIMIT MFS N_PREF_CELLS BSC N_RIM_RETRIES MFS
N_SIG_REPEAT MFS N_stagnating_Window_DL_LIMIT MFS N_stagnating_Window_UL_LIMIT MFS
N_TA_IP BTS N_TCH_HO BSC N_threshold BSC
N_TRAFFIC_LOAD BSC N_UL_BIAS_FOR_EDA MFS N_UL_Dummy_LIMIT MFS
N_UL_Errors_LIMIT MFS N_WAIT BTS N1 BSC
N2 BSC N200_GSL (BSC) BSC N200_GSL (MFS) MFS
N200_LE BTS N200_LR BTS N200_OML (BSC) BSC
N200_OML (BTS) BTS N200_RSL (BSC) BSC N200_RSL (BTS) BTS
N200_TD BTS N200_TS BTS N200_TTF BTS
N200_TTH BTS N201 (BSC) BSC N201 (BTS) BTS
N201_BTER_D BTS N201_BTER_S BTS N201_D BTS
N201_GSL (BSC) BSC N201_GSL (MFS) MFS N201_S BTS
N2X4 BSC N3101_LIMIT MFS N3103_LIMIT MFS
N3105_LIMIT MFS N3105_LIMIT_SATELLITE MFS N391 MFS
N392 MFS N393 MFS NB_MAX_ACTIVE_TCH_TS BSC
NB_MAX_BC_PER_PHYSICAL_LINE MFS NB_MAX_BEARER_CHANNELS_PER_ MFS NB_MAX_GB_PHYSICAL_LINES MFS

GPU
NB_MAX_MSG_MULTIPLE_PAGING_C BSC NB_MAX_PVC_PER_BEARER_CHANN MFS NB_MPDCH_LOAD_SAMPLE MFS

MD EL
NB_MSG_GSL_OUTPUT_BUFFER_XOF BSC NB_MSG_GSL_OUTPUT_BUFFER_XOF BSC NB_MSG_GSL_OUTPUT_BUFFER_XO BSC

F_G2_BSC F_MX_BSC N_G2_BSC
NB_MSG_GSL_OUTPUT_BUFFER_XO BSC Nb_of_reserved_slots_for_basic_CBC BSC Nb_of_reserved_slots_for_extended_ BSC

N_MX_BSC H CBCH
NB_TS_MPDCH (BSC) BSC NB_TS_MPDCH (MFS) MFS NB_WAIT_SMLC_RESET_ACK BSC
NBLK BSC NBR_RESET_CIC_REP BSC NBR_RESET_IP_REP BSC
NBR_RESET_REP BSC NBR_STEPS_OVRL_1 BSC NBR_STEPS_OVRL_2 BSC
NC_DL_RXLEV_LIMIT_THR MFS NC_DL_RXLEV_THR MFS NC_DL_RXQUAL_THR MFS
NC_NON_DRX_PERIOD MFS NC_PING_PONG_OFFSET MFS NC_REPORTING_PERIOD_I MFS
NC_REPORTING_PERIOD_T MFS NC_REPORTING_PERIOD_T(n) MFS NC_RESELECT_HYSTERESIS(0,n) MFS
NC_RXLEV_FORGETTING_FACTOR MFS NC_RXQUAL_AVG_PERIOD MFS NC_RXQUAL_HYSTERESIS MFS
NC_UL_RXQUAL_THR MFS NC2_DEACTIVATION_MODE MFS NC2_LOAD_EV_PERIOD MFS
NCC (BSC) BSC NCC (MFS) MFS NCC(n) MFS
NCC_permitted BSC NCI BSC NECI (BSC) BSC
NECI (MFS) MFS NEIGHBOUR_RXLEV(0,n) BSC NETWORK_CONTROL_ORDER MFS
NETWORK_CONTROL_ORDER(n) MFS network_operation_mode (BSC) BSC network_operation_mode (MFS) MFS
NIR MFS NO_CLEAR_REQUEST_AFTER_DISC_ BSC NORMAL_PRECEDENCE_BACKGROUN MFS

RATIO D_PRIORITY
NORMAL_PRECEDENCE_INSTANT_MS MFS NORMAL_PRECEDENCE_THP1_PRIORI MFS NORMAL_PRECEDENCE_THP2_PRIORI MFS

G_PRIORITY TY TY
NORMAL_PRECEDENCE_THP3_PRIORI MFS NOTIF_FACCH_OTHER_VGCS_CALL_ BSC NOTIF_FACCH_PTP_CALL_THR BSC

TY THR
NOTIF_PCH_THR BSC NRI_LENGTH BSC NRI_LENGTH_PS MFS
NRI_LIST BSC NRI_LIST_PS MFS NRT_GUARANTEED_BANDWIDTH_FA BSC

CTOR
NRT_GUARANTEED_MARGIN MFS NS_alive_IP_retries MFS NS_ALIVE_RETRIES MFS
NS_BLOCK_RETRIES MFS NS_Priority MFS NS_RESET_RETRIES MFS
NS_UNBLOCK_RETRIES MFS NSEI MFS NSEMAX MFS
NSVCI MFS NSVCMAX MFS NUBLK BSC
NULL_NRI BSC NULL_NRI_PS MFS NUM_TCH_EGNCY_HO BSC
NUMBER_NCH_BLOCKS BSC NY1 BSC NY2 BSC
OandM_PRIORITY (BSC) BSC OandM_PRIORITY (MFS) MFS OFFSET_CA_HIGH BSC
OFFSET_CA_NORMAL BSC OFFSET_HO_MARGIN_INNER BSC Offset_Hopping_HO BSC
Offset_Hopping_PC BSC OPC BSC Operator BSC
OUTDOOR_UMB_LEV(0,n) BSC P0_LAYER2_MAPPING_BSC BSC P0_LAYER2_MAPPING_MFS MFS
P0_LAYER3_MAPPING_BSC BSC P0_LAYER3_MAPPING_MFS MFS P0_TP_QUEUE_MAPPING BSC
P1_LAYER2_MAPPING_BSC BSC P1_LAYER2_MAPPING_MFS MFS P1_LAYER3_MAPPING_BSC BSC
P1_LAYER3_MAPPING_MFS MFS P1_TP_QUEUE_MAPPING BSC P2_LAYER2_MAPPING_BSC BSC
P2_LAYER2_MAPPING_MFS MFS P2_LAYER3_MAPPING_BSC BSC P2_LAYER3_MAPPING_MFS MFS
P2_TP_QUEUE_MAPPING BSC P3_LAYER2_MAPPING_BSC BSC P3_LAYER2_MAPPING_MFS MFS
P3_LAYER3_MAPPING_BSC BSC P3_LAYER3_MAPPING_MFS MFS P3_TP_QUEUE_MAPPING BSC
PACKET_LOAD_BROADCAST_PERIOD MFS PAG_BAR BSC PAIRING_PRIORITIES_NON_SAIC BSC
PAIRING_PRIORITIES_SAIC BSC PAIRING_PRIORITIES_VAMOS1 BSC PAIRING_PRIORITIES_VAMOS2 BSC
PAN_DEC (BSC) BSC PAN_DEC (MFS) MFS PAN_INC (BSC) BSC
PAN_INC (MFS) MFS PAN_MAX (BSC) BSC PAN_MAX (MFS) MFS
Password BSC Pb MFS PC_MEAS_CHAN (BSC) BSC
PC_MEAS_CHAN (MFS) MFS PCC_n_RT_THROUGHPUT MFS PCC_T_LEAKY_BUCKET MFS
PCC_T_MAX_UL_BUFFERING MFS PCC_UL_TBF_GUARD_TIMER MFS PD_DL_PDCH_UNIT_ALLOC_THR_1 MFS
PD_DL_PDCH_UNIT_ALLOC_THR_10 MFS PD_DL_PDCH_UNIT_ALLOC_THR_2 MFS PD_DL_PDCH_UNIT_ALLOC_THR_3 MFS
PD_DL_TBF_DURATION_THR_1 MFS PD_DL_TBF_DURATION_THR_10 MFS PD_DL_TBF_DURATION_THR_2 MFS
PD_DL_TBF_DURATION_THR_9 MFS PD_DL_TBF_VOLUME_THR_1 MFS PD_DL_TBF_VOLUME_THR_10 MFS
PD_DL_TBF_VOLUME_THR_2 MFS PD_DL_TBF_VOLUME_THR_3 MFS PD_DL_TBF_VOLUME_THR_4 MFS
PD_DL_TBF_VOLUME_THR_5 MFS PD_DL_TBF_VOLUME_THR_6 MFS PD_DL_TBF_VOLUME_THR_7 MFS
PD_DL_TBF_VOLUME_THR_8 MFS PD_DL_TBF_VOLUME_THR_9 MFS PD_UL_PDCH_UNIT_ALLOC_THR_1 MFS
PD_UL_PDCH_UNIT_ALLOC_THR_10 MFS PD_UL_PDCH_UNIT_ALLOC_THR_2 MFS PD_UL_PDCH_UNIT_ALLOC_THR_3 MFS
PD_UL_TBF_DURATION_THR_1 MFS PD_UL_TBF_DURATION_THR_10 MFS PD_UL_TBF_DURATION_THR_2 MFS
PD_UL_TBF_DURATION_THR_9 MFS PD_UL_TBF_VOLUME_THR_1 MFS PD_UL_TBF_VOLUME_THR_10 MFS
PD_UL_TBF_VOLUME_THR_2 MFS PD_UL_TBF_VOLUME_THR_3 MFS PD_UL_TBF_VOLUME_THR_4 MFS
PD_UL_TBF_VOLUME_THR_5 MFS PD_UL_TBF_VOLUME_THR_6 MFS PD_UL_TBF_VOLUME_THR_7 MFS
PD_UL_TBF_VOLUME_THR_8 MFS PD_UL_TBF_VOLUME_THR_9 MFS PDA_FULL BTS
PDCH_BUFFERING_FACTOR MFS PDCH_MIN_BUFFERING_FACTOR MFS PDCH_TBF_XON_FACTOR MFS
PDU_LIFETIME_ORDER MFS PDU_REORDER_INHIBIT_THRES_GP MFS Peer_NSE_Data_Weight MFS
Peer_NSE_Signalling_Weight MFS PENALTY_TIME(BSC) BSC PENALTY_TIME(MFS) MFS
PENALTY_TIME(n)(BSC) BSC PENALTY_TIME(n)(MFS) MFS PERSISTENCE_LEVEL_1 MFS
PERSISTENCE_LEVEL_2 MFS PERSISTENCE_LEVEL_3 MFS PERSISTENCE_LEVEL_4 MFS
PFC_NB_RETRY_DOWNLD MFS PFC_NB_RETRY_MODIFY MFS PFC_T6 MFS
PFC_T8 MFS PG_FULL BTS PING_PONG_HCP BSC
PLMN_FREQUENCY_BANDS(BSC) BSC PLMN_FREQUENCY_BANDS(MFS) MFS PMU_CPU_OVERLOAD_GP2 MFS
PMU_CPU_OVERLOAD_GP3 MFS PMU_CPU_overload_step_H MFS PMU_CPU_overload_step_N MFS
PMU_CPU_sampling_period MFS POW_INC_FACTOR BSC POW_INC_FACTOR_VAMOS BSC
POW_INC_STEP_SIZE BSC POW_INC_STEP_SIZE_VAMOS BSC POW_RED_DEC_STEP_SIZE_PS MFS
POW_RED_FACTOR BSC POW_RED_FACTOR_VAMOS BSC POW_RED_INC_STEP_SIZE_PS MFS
POW_RED_P0 MFS POW_RED_P0_PDDCB MFS POW_RED_STEP_SIZE BSC
POW_RED_STEP_SIZE_VAMOS BSC POWER_OFFSET_IND BSC PRACH_BUSY_THRES MFS
PREF_GPS_LIST_Priority_1 MFS PREF_GPS_LIST_Priority_2 MFS PREF_GPS_LIST_Priority_3 MFS
PREFERRED_BAND BSC PRIO_THR BSC PRIORITY(0,n) BSC
PRIORITY_3G BSC PRIORITY_ACCESS_THRESHOLD BSC PRIORITY_ACCESS_THRESHOLD MFS

(BSC) (MFS)
PRIORITY_LTE BSC PROT_MON BSC PROT_TH BSC
PS_PREF_BCCH_TRX BSC PS_RADIO_CONG_RATIO MFS PTM_BVCI MFS
PTP_BVCI MFS PVC_Level1_down MFS PVC_Level1_Factor MFS
PVC_Level1_up MFS PWRC (BSC) BSC PWRC (MFS) MFS
Q703_N1 BSC Q703_N1_HSL BSC Q703_N2 BSC
Q703_N2_HSL BSC Q703_T1 BSC Q703_T1_HSL BSC
Q703_T2 BSC Q703_T3 BSC Q703_T4E BSC
Q703_T4N BSC Q703_T4N_HSL BSC Q703_T5 BSC
Q703_T6 BSC Q703_T7 BSC Q704_T2 BSC
Q704_T4 BSC Q704_T5 BSC Q707_T1 BSC
Q707_T2 BSC QOS_SAFETY_MARGIN MFS QRXLEVMIN_3G BSC
QRXLEVMIN_LTE BSC Qsearch_C BSC Qsearch_C_LTE_INITIAL BSC
Qsearch_I BSC Qsearch_P BSC Qsearch_P_LTE BSC
Qsearch_P_PTM MFS QUEUE_ANYWAY BSC R_AVERAGE_EGPRS MFS
R_AVERAGE_GPRS MFS RA_CAPABILITY_UPDATE_RETRIES MFS RA_CODE (BSC) BSC
RA_CODE (MFS) MFS RA_CODE(n) MFS RA_COLOUR BSC
RA_RESELECT_HYSTERESIS MFS RACH_BUSY_THRES BSC RACH_LOAD_MEAS_PER BSC
RACH_TA_FILTER (BSC) BSC RACH_TA_FILTER (MFS) MFS RACHRT BSC
RADIOLINK_REP_DL_SACCH BSC RADIOLINK_TIMEOUT (BSC) BSC RADIOLINK_TIMEOUT (MFS) MFS
RADIOLINK_TIMEOUT_AMR BSC RADIOLINK_TIMEOUT_BS BSC RADIOLINK_TIMEOUT_BS_AMR BSC
RANGEi_HIGHER (1<=i<=13) BSC RANGEi_LOWER (1<=i<=13) BSC RAT_3G BSC
RAT_LTE BSC RATE_RED MFS RAW_BITRATE_CS1 MFS
RAW_BITRATE_CS2 MFS RAW_BITRATE_CS3 MFS RAW_BITRATE_CS4 MFS
RAW_BITRATE_MCS1 MFS RAW_BITRATE_MCS2 MFS RAW_BITRATE_MCS3 MFS
RE BSC REP_DL_FACCH_LEGACY_SUPPORT BSC REP_DL_FACCH_THRES_AMR_FR BSC
REP_DL_FACCH_THRES_AMR_HR BSC REP_DL_FACCH_THRES_AMR_WB BSC REP_DL_SACCH_THRES BSC
REP_DL_SACCH_WS BSC REP_UL_SACCH_THRES BSC REP_UL_SACCH_WS BSC
RESET_INDEFINITE BSC RESP_REQ BSC Resume_retries MFS
RLC_FC1_BUFFER_SEND_THRES MFS RLC_FC1_THROUGHPUT_CHANGE_TH MFS RLC_TARGET_BUFFER MFS

RES
RMIN_EGPRS MFS RMIN_GPRS MFS RMS_BCCH_BSIC_NB BSC
RMS_TEMPLATE_INDEX BSC RNC_ID_3G BSC RNC_MIN_NB_ACTIVE_IPSP BSC
RNC_SPC BSC RNC_TRAFFIC_MODE BSC ROT BSC
round_trip_delay MFS round_trip_delay_bts_ms MFS RR_ACK_TIMER (BTS) BTS
RR_ACK_TIMER (MX BSC) BSC RR_ALLOC_PERIOD (BSC) BSC RR_ALLOC_PERIOD (MFS) MFS
RSL_I_PRIORITY (BSC) BSC RSL_I_PRIORITY (BTS) BTS RSL_RATE (BSC) BSC
RSL_RATE (BTS) BTS RSL_UDP_PORT_BSC BSC RSL_UDP_PORT_TRE BTS
RSL_UI_PRIORITY (BSC) BSC RSL_UI_PRIORITY (BTS) BTS RTCP_N_NEGO BSC
RTCP_PERIOD BSC RTP_IP_ADDRESS_BSC BSC RTP_UDP_PORT_MASK BSC
RTP_UDP_PORT_START BSC RXLEV_ACCESS_MIN (BSC) BSC RXLEV_ACCESS_MIN (MFS) MFS
RXLEV_ACCESS_MIN(n)(BSC) BSC RXLEV_ACCESS_MIN(n)(MFS) MFS RXLEV_DL_IH BSC
RXLEV_DL_MAX_VAMOS_UNPAIRING BSC RXLEV_DL_MIN_VAMOS_PAIRING BSC RXLEV_DL_ZONE BSC
RxLev_HO_to_GAN BSC RXLEV_LIMIT_PBGT_HO BSC RXLEV_UL_IH BSC
RXLEV_UL_ZONE BSC RXLEVmin(n) BSC RXQUAL_DL_MAX_VAMOS_PAIRING BSC
RXQUAL_DL_MIN_VAMOS_UNPAIRIN BSC S MFS S_BECN MFS

G
SAGI_GATEWAY_IP_ADDRESS_1 MFS SAGI_GATEWAY_IP_ADDRESS_2 MFS SAGI_GPS_SERVER_LOCAL_IP_ADD MFS

RESS
SAGI_TCP_DATA_TIMEOUT MFS SAGI_TCP_KEEP_ALIVE_INTERVAL MFS SAGI_TCP_MAX_DATA_RETRANS MFS
SAGI_TCP_PORT_NB MFS SAI_LTE BSC Schedule_period_for_basic_CBCH BSC
Schedule_period_for_extended_CBCH BSC SCHEDULING_PRIORITY_FACTOR MFS SCPIR_LOW_MS_ALLOC_NON_SAIC BSC
SCPIR_LOW_MS_ALLOC_SAIC BSC SCPIR_LOW_MS_ALLOC_SUB_SAIC BSC SCPIR_LOW_MS_ALLOC_VAMOS1 BSC
SCPIR_LOW_MS_ALLOC_VAMOS2 BSC SCPIR_LOW_MS_PC_NON_SAIC BSC SCPIR_LOW_MS_PC_SAIC BSC
SCPIR_LOW_MS_PC_SUB_SAIC BSC SCPIR_LOW_MS_PC_VAMOS1 BSC SCPIR_LOW_MS_PC_VAMOS2 BSC
SCPIR_MODIF_STEP_SIZE BSC SCPIR_MODIF_VAMOS_CCCH BSC SCPIR_NON_SAIC_VAMOS1_THR_1 BSC
SCPIR_NON_SAIC_VAMOS1_THR_2 BSC SCPIR_NON_SAIC_VAMOS1_THR_3 BSC SCPIR_NON_SAIC_VAMOS2_THR_1 BSC
SCPIR_NON_SAIC_VAMOS2_THR_2 BSC SCPIR_NON_SAIC_VAMOS2_THR_3 BSC SCPIR_SAIC_SAIC_THR_1 BSC
SCPIR_SAIC_SAIC_THR_2 BSC SCPIR_SAIC_SAIC_THR_3 BSC SCPIR_SAIC_VAMOS1_THR_1 BSC
SCPIR_SAIC_VAMOS1_THR_2 BSC SCPIR_SAIC_VAMOS1_THR_3 BSC SCPIR_SAIC_VAMOS2_THR_1 BSC
SCPIR_SAIC_VAMOS2_THR_2 BSC SCPIR_SAIC_VAMOS2_THR_3 BSC SCPIR_VAMOS1_VAMOS1_THR_1 BSC
SCPIR_VAMOS1_VAMOS1_THR_2 BSC SCPIR_VAMOS1_VAMOS1_THR_3 BSC SCPIR_VAMOS1_VAMOS2_THR_1 BSC
SCPIR_VAMOS2_VAMOS2_THR_2 BSC SCPIR_VAMOS2_VAMOS2_THR_3 BSC SCRAMBLING_CODE_3G_FDD BSC
SDCCH_AVG_PERIOD BSC SDCCH_COUNTER BSC SDCCH_HIGH_DELAY BSC
SDCCH_LOW_DELAY BSC SERVICE_CLASS_INDICATOR_IE MFS SGSN_IP_Address MFS
SGSN_IP_ENDPOINT_MAX MFS SGSN_OFFLOAD_STATE MFS SGSN_UDP_Port MFS
SGSN_WEIGHT MFS SGSNR MFS SGW_INTERWORKING_LB BSC
SHORT_FRM BTS SIDMO_TCP_PORT_TRE BTS SIG_BVCI MFS
SIGNALLING_PRIORITY MFS SLC BSC SLOW_MOVING_FACTOR MFS
SMLC_SPC BSC SMLC_TRAFFIC_MODE BSC SMS_INHIBIT BSC
SMS_PRIORITY MFS SMSCB_Features_set BSC SMSCB_Mode BSC
SMSCB_Phase BSC SMSCB_Recovery BSC SMSCB_State BSC
SNMP_PRIORITY (BSC) BSC SNMP_PRIORITY (BTS) BTS SNMP_PRIORITY (TC) TC
SNS_CONFIG_RETRIES MFS SNS_SIZE_RETRIES MFS SPGC_CCCH_SUP (BSC) BSC
SPGC_CCCH_SUP (MFS) MFS SSF BSC START_ASIG_IP_ADDRESS_2_BSC BSC
START_ASIG_IP_ADDRESS_BSC BSC START_AUP_IP_ADDRESS_BSC BSC START_BSS_IP_ADDRESS_BSC BSC
START_IURG_IP_ADDRESS_BSC BSC START_LB_IP_ADDRESS_BSC BSC START_UPLINK_REPLY BSC
STREAMING_PRIORITY MFS STRIP_O5_CM2 BSC SUB_SAIC_BLACKLIST BSC
Suspend_retries MFS T(conn est) BSC T(iar) BSC
T(ias) BSC T(rel) BSC T(sst) (G2 BSC) BSC
T(sst) (MX BSC) BSC T_ACK_WAIT MFS T_ACK_WAIT_DRX_PCCCH MFS
T_ALLOC_BTS BSC T_ATER_CONN BSC T_AUTOCLEANING_MEAS_REP BSC
T_AVG_T (BSC) BSC T_AVG_T (MFS) MFS T_AVG_W (BSC) BSC
T_AVG_W (MFS) MFS T_BA_CHANGE MFS T_BIND_CNF BSC
T_BTS_EST_CNF BSC T_BTS_LOAD_REPORT_WITH_TRANSI MFS T_BTS_LOAD_REPORT_WITHOUT_TR MFS

TION ANSITION
T_BTS_RLS_CNF BSC T_BURST BSC T_CANDIDATE_TBF_REALLOC MFS
T_CBC_READY BSC T_CFI_TR BTS T_CHANGE_RLC_MODE MFS
T_CLEAR_REQUEST_AFTER_DISC BSC T_CONFIG_TBF MFS T_CONFIRM_ABIS BTS
T_CONNECT BSC T_COUNT_I BSC T_DELAY BSC
T_delay_gch MFS T_DELAY_GSL BSC T_DELAY_HO_COMMAND BSC
T_DELAY_PAGING_EXT MFS T_DELAYED_DL_TBF_POL MFS T_DELAYED_DL_TBF_POL_INITIAL MFS
T_Delayed_DL_TBF_Pol_UL MFS T_DELAYED_FINAL_PUAN MFS T_dl_assign_ccch MFS
T_DL_EGPRS_MeasReport MFS T_DL_GPRS_MeasReport MFS T_DSP_LOAD_REPORT MFS
T_DTM_ASSIGN MFS T_DYN_SDCCH_HOLD BSC T_EXTENDED_UL_TBF_FAST_POL MFS
T_EXTENDED_UL_TBF_POL MFS T_FAST_DL_margin MFS T_FILTER BSC
T_flow_ctrl_cell MFS T_flow_ctrl_ms MFS T_GCH_INACTIVITY MFS
T_GCH_INACTIVITY_LAST MFS T_GPRS_Resume BSC T_GSL_ACK (BSC) BSC
T_GSL_ACK (MFS) MFS T_HCP BSC T_HO_REQD_LOST BSC
T_i BSC T_i_LB BSC T_IA BSC
T_INHIBIT_CPT BSC T_INITIAL_PDCH MFS T_INTRF_L3 BSC
T_IPGCH_ACK_DL MFS T_IPGCH_ACK_UL MFS T_IPGCHU_TIMEOUT MFS
T_LB_OV BSC T_LCS_Delay_Tolerant MFS T_LCS_Low_Delay MFS
T_LCS_RESTART (BSC) BSC T_LCS_RESTART (MFS) MFS T_Loc_abort BSC
T_Loc_abort_LB BSC T_Location BSC T_Location_LB BSC
T_Location_Longer BSC T_MAX_EXTENDED_UL MFS T_MAX_FOR_MS_SYNCHRO MFS
T_MAX_FOR_TBF_SCHEDULING MFS T_MAX_HOLD_MUXRTP BSC T_MAX_HOLD_MUXTRAUP BSC
T_MAX_HOLD_MUXTRAUP_TPIP BSC T_MAX_RETRANS_DL MFS T_MAX_STREAMING_BUFFERING MFS
T_MIN_POLL MFS T_MPDCH_EST_PROC (BSC) BSC T_MS_CELL_REJ BSC
T_MS_CONTEXT_FLUSH_PERSISTENC MFS T_MS_Context_Lifetime MFS T_NC_PING_PONG MFS

E
T_NC_REJ_CELL MFS T_NC_RXQUAL_VALID MFS T_NC2_LOAD_RANKING MFS
T_NETWORK_RESPONSE_TIME MFS T_NETWORK_RESPONSE_TIME_CONG MFS T_NETWORK_RESPONSE_TIME_IM MFS
T_NETWORK_RESPONSE_TIME_IM_CO MFS T_NOTIF_RESPONSE_DELAY BSC T_One_Block MFS
NG
T_OVL_MSC BSC T_PAG_CS (BSC) BSC T_PAG_CS (MFS) MFS
T_PAG_PS (BSC) BSC T_PAG_PS (MFS) MFS T_PAGING_EXT MFS
T_PAGING_REORG MFS T_PDA BSC T_PSCD_SCHEDULE_ACK MFS
T_PSI_PACCH MFS T_PUA BSC T_qho BSC
T_RCR_ACK BSC T_RECOVERY BSC T_release TC
T_REPETITION_CHANNEL_RELEASE BSC T_REPETITION_UPLINK_FREE BSC T_REROUTING_REQUEST_GUARD MFS
T_RESEL MFS T_RESELECTION BSC T_RESET_COUNTER BTS
T_RIM_DISABILITY MFS T_RIM_MULTIPLE_REPORT MFS T_RIM_RI MFS
T_RIM_RIR MFS T_RMS_BSC BSC T_RMS_BSC_RECONF BSC
T_RMS_BSC_RESTART BSC T_RMS_BTS BSC T_RRLP_Delay_Tolerant MFS
T_RRLP_Low_Delay MFS T_RTP_PNRT BSC T_SAGI_GUARD MFS
T_SCON BSC T_SDCCH_PC BSC T_SEND_MULTIPLE_PAGING_CMD BSC
T_SHARED_DTM_INFO (BSC) BSC T_SHARED_DTM_INFO (MFS) MFS T_SMSCB_READY BTS
T_SMSCB_RESP BSC T_START_MUXRTP BSC T_STOP_FR_EMISSION MFS
T_SUP BTS T_SYNC BTS T_SYNCd BTS
T_SYNCu BTS T_ta BTS T_TA_ Margin BTS
T_TA_delta_min BTS T_TBF_ACTIV MFS T_TBF_BCK_REL MFS
T_TC_BTS_LINK_POLLING BSC
T_TC_IPTCHM_REPORTING_PERIOD TC T_TFO BSC T_TRAU_ACK_WAIT BSC
T_ul_access_max MFS T_ul_assign_ccch MFS T_ul_assign_pccch MFS
T_UL_CONGESTION MFS T_USF_Scheduling_AGCH MFS T_WAIT_CS_PROC MFS
T_WAIT_DTM MFS T_WAIT_DTM_TCH_REL MFS T_WAIT_FLUSH MFS
T_WAIT_PMR_MARGIN MFS T_WAIT_SMLC_RESET_ACK BSC T_WAIT_UPLINK_ACCESS BSC
T_WAIT_UPLINK_REQUEST_ACK BSC T1_0858 BSC T1_long BSC
T1_short BSC T11 BSC T11_FORCED BSC
T13 BSC T14 BSC T17 BSC
T18 BSC T18_Overload BSC T19 BSC
T2_0858 BSC T20 BSC T200 (BSC) BSC
T200_D BTS T200_D3 BTS T200_GSL (BSC) BSC
T200_GSL (MFS) MFS T200_OMU BTS T200_S3 BTS
T200_TF BSC T200_TH BSC T200_TRE BTS
T203 (BSC) BSC T203 (BTS) BTS T203_GSL (BSC) BSC
T203_GSL (MFS) MFS T25 BSC T3101 BSC
T3103 BSC T3105_D BSC T3105_D_STOP BSC
T3105_F_FR BSC T3105_F_HR BSC T3105_F_STOP BSC
T3106_D BSC T3106_D_STOP BSC T3106_F BSC
T3106_F_STOP BSC T3107 BSC T3109 BSC
T3122 BSC T3148n (BSC) BSC T3148n (MFS) MFS
T3166n MFS T3168 (BSC) BSC T3168 (MFS) MFS
T3169 MFS T3180 MFS T3182n MFS
T3190n MFS T3191 MFS T3192 (BSC) BSC
T3192 (MFS) MFS T3208n MFS T3212 (BSC) BSC
T3212 (MFS) MFS T391 MFS T4 BSC
T5_RA_CAP_UPDATE MFS T7 BSC T8 BSC
T9112 BSC T9113 BSC TA_STAT BSC
TARGET_MCS_BEP_OFFSET MFS TARGET_MCS_PR MFS TBF_CS_DL MFS
TBF_CS_PERIOD MFS TBF_CS_UL MFS TBF_CS3_BLER_PERIOD MFS
TBF_CS4_BLER_PERIOD MFS TBF_DL_INIT_CS MFS TBF_DL_INIT_MCS MFS
TBF_GCH_RATIO_DL MFS TBF_GCH_RATIO_UL MFS TBF_MCS_DL MFS
TBF_MCS_PERIOD MFS TBF_MCS_UL MFS TBF_UL_INIT_CS MFS
TBF_UL_INIT_MCS MFS TC_TRAUP_IP_Address TC TCH_INFO_PERIOD BSC
TCH_TS_ACTIVITY_FACTOR BSC Tcorr MFS TCP_KEEP_ALIVE_CNT (BSC) BSC
TCP_KEEP_ALIVE_CNT (BTS) BTS TCP_KEEP_ALIVE_CNT (MFS) MFS TCP_KEEP_ALIVE_IDLE (BTS) BTS
TCP_KEEP_ALIVE_IDLE (BSC) BSC TCP_KEEP_ALIVE_IDLE (MFS) MFS TCP_KEEP_ALIVE_INTVL (BSC) BSC
TCP_KEEP_ALIVE_INTVL (BTS) BTS TCP_KEEP_ALIVE_INTVL (MFS) MFS TCP_MAX_RETRANS (BSC) BSC
TCP_MAX_RETRANS (BTS) BTS TCP_MAX_RETRANS (MFS) MFS TCP_MSL (BSC) BSC
TCP_MSL (BTS) BTS TCP_MSL (MFS) MFS TDD_ARFCN_LIST BSC
TDD_Qoffset BSC Tdsl MFS TELECOM_IP_SUBNET_MASK_TC TC
TEMPORARY_OFFSET BSC TEMPORARY_OFFSET(n) BSC Testab MFS
THR_ACT_1 BTS THR_ACT_2 BTS THR_BUFFER BTS
THR_CCCH_LOAD BSC THR_CELL_LOAD_3G_REJECT BSC THR_CELL_LOAD_3G_REQ BSC
THR_CELL_LOAD_LTE_REJECT BSC THR_ECNO_HO BSC THR_FR_LOAD_L_SV1 BSC
THR_FR_LOAD_L_SV3 BSC THR_FR_LOAD_L_VAMOS_FR BSC THR_FR_LOAD_L_VAMOS_HR BSC
THR_FR_LOAD_U_SV1 BSC THR_FR_LOAD_U_SV3 BSC THR_FR_LOAD_U_VAMOS_FR BSC
THR_FR_LOAD_U_VAMOS_HR BSC THR_IDLE BTS THR_LB_OV BSC
THR_MARGIN_PRIO_PS BSC THR_NC2_LOAD_RANKING MFS THR_RR_ALLOC_DEFENSE_HIGH MFS
THR_RR_ALLOC_DEFENSE_LOW MFS THR_RXQUAL_CA_HIGH BSC THR_RXQUAL_CA_NORMAL BSC
THRES_DSP_XOFF MFS THRES_DSP_XON MFS THRES_G_MAX_HIGH MFS
THRES_G_MAX_HIGH_IP MFS THRES_G_MAX_LOW MFS THRES_G_MAX_LOW_IP MFS
THRES_HIGH_TX BTS THRES_LOW_DSP_XOFF MFS THRES_LOW_DSP_XON MFS
THRES_LOW_SCP_XOFF_IP MFS THRES_LOW_SCP_XON_IP MFS THRES_LOW_TX BTS
THRES_SCP_XOFF_IP MFS THRES_SCP_XON_IP MFS THRESH_2G_LOW BSC
THRESH_3G_HIGH BSC THRESH_3G_LOW BSC THRESH_LTE_HIGH BSC
THRESH_LTE_LOW BSC THRESH_PRIORITY_SEARCH BSC THRESHOLD_1_0 BSC
THRESHOLD_1_1 BSC THRESHOLD_1_10 BSC THRESHOLD_1_2 BSC
TL_TCUA BSC TL0 BSC TL1 BSC
TL2 BSC TL3 BSC TL4 BSC
TLC_CONFIG_T BTS Tns_alive MFS Tns_alive_IP MFS
Tns_block MFS Tns_reset MFS Tns_test MFS
Tns_test_IP MFS TOM8_PRIORITY MFS TP_QUEUE0_WEIGHT BSC
TP_QUEUE1_WEIGHT BSC TP_QUEUE2_WEIGHT BSC TP_QUEUE3_WEIGHT BSC
TRAFFIC_EV_PERIOD OMC TRAFFIC_MODE BSC TRAU_ACTIVITY_TIMER BTS
TRAU_CONNECTION_TIMEOUT BSC TRBSS BSC TRE_CONTAINER_MAX_NB_UDP_G3 BTS
TRE_CONTAINER_SIZE_TCP_G3 BTS TRE_CONTAINER_SIZE_TCP_G4 BTS TRE_CONTAINER_SIZE_TCP_G5 BTS
TRE_CONTAINER_SIZE_TCP_MC BTS TRE_CONTAINER_SIZE_UDP_G3 BTS TRE_CONTAINER_SIZE_UDP_G4 BTS
TRE_CONTAINER_SIZE_UDP_G5 BTS TRE_CONTAINER_SIZE_UDP_MC BTS Treassembly BSC
Trelease MFS Treq_pending MFS TRG_SDCCH BSC
TRTS_PS MFS TRX_CIPH_CAP BSC TRX_DATA_TIMER BSC
TRX_PREF_MARK BSC TS_TCUA BSC TSC BSC
TSC_1_2 BSC Tsns_config MFS Tsns_prov MFS
Tsns_restart MFS TSTD_3G_TDD BSC Tusl MFS
TX_EFFICIENCY_ACK_THR MFS TX_EFFICIENCY_NACK_THR MFS TX_EFFICIENCY_PERIOD MFS
TX_INT MFS Tx_integer (BSC) BSC Tx_integer (MFS) MFS
U_RXLEV_DL_MCHO BSC U_RXLEV_DL_P BSC U_RXLEV_DL_P_VAMOS BSC
U_RXLEV_UL_MCHO BSC U_RXLEV_UL_P BSC U_RXLEV_UL_P_VAMOS BSC
U_RXQUAL_DL_P BSC U_RXQUAL_DL_P_AMR BSC U_RXQUAL_DL_P_AMR_VAMOS BSC
U_RXQUAL_DL_P_VAMOS BSC U_RXQUAL_UL_P BSC U_RXQUAL_UL_P_AMR BSC
U_TIME_ADVANCE BSC UI_LAPD_MAX_TX BTS UL_POLL_FACTOR MFS
UL_TA_Late_Margin TC UL_VAMOS_PC_CORRECTION_FACT BSC Use_of_Extended_CBCH BSC

OR
USF_NE MFS VARIOUS_IP_PRIORITY (BSC) BSC VARIOUS_IP_PRIORITY (BTS) BTS
VARIOUS_IP_PRIORITY (MFS) MFS VARIOUS_IP_PRIORITY (TC) TC VGCS_FIX_AMR_FR_CODEC BSC
VGCS_FIX_AMR_HR_CODEC BSC VQ_AVERAGE BSC VQ_BAD_RXFER BSC
VQ_FER_THRESHOLD BSC VQ_GOOD_RXFER BSC VQ_INTF_THRESHOLD BSC
VQ_RXLEV BSC VQ_RXQUAL BSC VQ_RXQUAL_VS_RXFER BSC
W_LEV_HO BSC W_LEV_MCHO BSC W_LEV_PC BSC
W_LEV_PC_VAMOS BSC W_LEV_VAMOS_PAIRING BSC W_LEV_VAMOS_UNPAIRING BSC
W_PBGT_HO BSC W_QUAL_CA BSC W_QUAL_HO BSC
W_QUAL_PC BSC W_QUAL_PC_VAMOS BSC W_QUAL_VAMOS_PAIRING BSC
W_QUAL_VAMOS_UNPAIRING BSC WAIT_UPLINK_ACCESS BSC WEIGHT_BIAS_DETERMINATION MFS
Weight_P10 MFS Weight_P11 MFS Weight_P12 MFS
WI_CR BSC WI_DTM MFS WI_EC BSC
WI_OC BSC WI_OP BSC WI_PR MFS
WI_PR_CPU_OVERLOAD MFS ZONE_HO_HYST_DL BSC ZONE_HO_HYST_UL BSC
ZONE_TYPE BSC
End of document

B12 TelecomParam BTP Ed1.5

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

B12 TelecomParam BTP Ed1.5

Caricato da

Copyright:

Formati disponibili

vendredi 26 juillet 2013

BSS Telecom Parameters Catalogue:

Edition : 11 Released BSS Telecom parameters 3BK 11203 0250 DSZZA

Mandatory rules A_LEV_HO + W_LEV_HO < 32

Recommended A_LEV_HO = 2 x A_LEV_PC. A_PBGT_HO = 2 x A_LEV_HO

Mandatory rules A_LEV_MCHO + W_LEV_MCHO < 16

Mandatory rules A_LEV_PC + W_LEV_PC < 32

Recommended A_LEV_HO = 2 x A_LEV_PC

Mandatory rules - A_LEV_PC_VAMOS + W_LEV_PC_VAMOS <= 32

Mandatory rules - A_LEV_VAMOS_PAIRING + W_LEV_VAMOS_PAIRING < 32

Mandatory rules - A_LEV_VAMOS_UNPAIRING + W_LEV_VAMOS_UNPAIRING < 32

Mandatory rules A_PBGT_HO + W_PBGT_HO < 32

Recommended A_PBGT_HO = 2 x A_LEV_HO

Mandatory rules A_QUAL_CA_FR_HR >= A_QUAL_CA_HR_FR

Mandatory rules A_QUAL_CA_FR_HR >= A_QUAL_CA_HR_FR

Mandatory rules A_QUAL_HO + W_QUAL_HO < 32

Recommended A_QUAL_HO = 2 x A_QUAL_PC

Mandatory rules A_QUAL_PC + W_QUAL_PC < 32

Recommended A_QUAL_HO = 2 x A_QUAL_PC

Mandatory rules - A_QUAL_PC_VAMOS + W_QUAL_PC_VAMOS <= 32

Mandatory rules - A_QUAL_VAMOS_PAIRING + W_QUAL_VAMOS_PAIRING < 32

Mandatory rules - A_QUAL_VAMOS_UNPAIRING + W_QUAL_VAMOS_UNPAIRING < 32

When EN_VGCS is enabled:

Mandatory rules Equal to ALPHA (MFS)

AMR configuration 0 is composed of the codec: 4.75 Kbit/sec

Logical AMR_FR_THR_1 B11 Yes B12 Yes

Mandatory rules AMR_FR_THR_1 <= AMR_FR_THR_2

Mandatory rules AMR_FR_THR_3 >= AMR_FR_THR_2 >= AMR_FR_THR_1

Mandatory rules AMR_FR_THR_3 >= AMR_FR_THR_2

AMR configuration 0 is composed of the codec: 4.75 Kbit/sec

Logical AMR_HR_THR_1 B11 Yes B12 Yes

Mandatory rules AMR_HR_THR_1 <= AMR_HR_THR_2

- The AMR configuration 1 is especially recommended when EN_AUP_OVER_IP is enabled

Mandatory rules AMR_HR_THR_3 >= AMR_HR_THR_2 >= AMR_HR_THR_1

Mandatory rules AMR_HR_THR_3 >= AMR_HR_THR_2

Mandatory rules AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1<=AMR_WB_GMSK_THR_2+AMR_WB_GMSK_HYST_2

Mandatory rules AMR_WB_GMSK_THR_1+AMR_WB_GMSK_HYST_1<=AMR_WB_GMSK_THR_2+AMR_WB_GMSK_HYST_2

Mandatory rules - AMR_WB_GMSK_THR_1 < AMR_WB_GMSK_THR_2

Mandatory rules - AMR_WB_GMSK_THR_1 < AMR_WB_GMSK_THR_2

Recommended - 255.255.255.255 and 0.0.0.0 are both forbidden

Recommended - 255.255.255.255 and 0.0.0.0 are both forbidden

Mandatory rules Equal to ATT (MFS)

Recommended - 255.255.255.255 and 0.0.0.0 are both forbidden

Mandatory rules Equal to BCC (MFS)

Mandatory rules - BCCH_ARFCN(n)(BSC) = BCCH_ARFCN(n)(MFS)

For Evolium serving cell:

Recommended BF_HI_RX > BF_LO_RX

Recommended BF_HI_TX > BF_LO_TX

Recommended BF_LO_RX < BF_HI_RX

Recommended BF_LO_TX < BF_HI_TX

Mandatory rules Equal to BS_CV_MAX (MFS)

Mandatory rules BS_PA_MFRMS (BSC) = BS_PA_MFRMS (MFS) for a given cell

Mandatory rules Equal to BS_TXPWR_MAX (MFS)

Mandatory rules Inside a BCS, each BSC_RSL_TID is unique.

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled

Mandatory rules changeable if SMSCB_STATE=disabled