Professional Documents
Culture Documents
Parameter B12 2G
Parameter B12 2G
Release B12
Edition :02.02 Released (aka Ed13 in 3BK version) BSS Telecom parameters GSM/SYS/DD/037396
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
Recommended --
rules
External --
comment
Internal comment Meaningful only for cells where: Cell_type = Microcell
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 --
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 after the modification.
Internal comment --
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 after the modification.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 after the modification.
Internal comment --
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 after the modification.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Category Site (CAE) OMC-R access Changeable Type Number Unit kbit/s
Rec ref. None Domai IP Min value 1 Coded Min 1
n Max value 65535 Coded Max 65535
Spec ref. Resource Allocation and Management Coded Max 65535
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. None Domai GSM Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. Resource Allocation and Management Coded Max 1
Def value 0 Coded Def 0
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 --
Recommended --
rules
External --
comment
Internal comment always set to 0 as SYS_INFO 7&8 are not used
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Internal BSS alarm, not OMC-R visualisation
Mandatory rules Let’s 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
Mandatory rules --
Recommended --
rules
External only relevant when NUM_TCH_EGNCY_HO > 0
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 = 1…3).
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
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
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 50
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 doesn’t 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).
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. --
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_2 <= 16dB.
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.
External Default value corresponds to the optimal default codec subset (12.2kbit/s, 7.95kbit/s, 5.9kbit/s). AMR_FR_THR_2 is not used if less than 3 codecs are in the AMR FR
comment subset.
Significant only if EN_AMR_FR is set to TRUE.
Internal comment --
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_3 <= 16dB.
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.
External Default value corresponds to the optimal default codec subset (12.2kbit/s, 7.95kbit/s, 5.9kbit/s). AMR_FR_THR_3 is not used if less than 4 codecs are in the AMR FR
comment subset.
Significant only if EN_AMR_FR is set to TRUE.
Internal comment --
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 = 1…3).
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
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.
- 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
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.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 55
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 doesn’t 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).
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;
AMR configuration 8: 11 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 --
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_2 <= 16dB.
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, 9 and 10: 12 dB.
External Default value corresponds to the optimal default codec subset (7.4kbit/s, 5.9kbit/s, 5.15kbit/s). AMR_HR_THR_2 is not used if less than 3 codecs are in the AMR HR
comment subset.
Significant only if EN_AMR_HR is set to TRUE.
Internal comment --
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_3 <= 16dB.
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 10: 13 dB.
External Default value corresponds to the optimal default codec subset (7.4kbit/s, 5.9kbit/s, 5.15kbit/s). AMR_HR_THR_3 is not used if less than 4 codecs are in the AMR HR
comment subset.
Significant only if EN_AMR_HR is set to TRUE.
Internal comment --
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 --
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 --
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 --
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 --
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 --
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 --
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.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 65
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.
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.
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) 5850–5999 and
19) 6000–6149 and
20) 6150–6449 and
21) 6450–6599
- 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
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.
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.
- 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.
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,
Mandatory rules --
two neighbour LTE cells are target for reselection and configured with the same ARFCN_LTE (TDD), then BSC broadcasts the ARFCN_LTE only once.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules - ASIG_SCTP_ENDPOINT_IP_Address_2 and ASIG_SCTP_ENDPOINT_PORT shall togetherbe 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.
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).
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
External Parameter change: before any modification, the operator must lock the associated A Signalling Link (ASL).
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).
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
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 --
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)
- 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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type.
comment
Internal comment --
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)
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.
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
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.
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.
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.
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
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.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External The bigger this parameter is, the lesser the MS power consumption is.
comment
Internal comment --
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.
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.
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.
Category Site (CAE) OMC-R access Virtual (DLS) Type Number Unit dB
Rec ref. None Domai GSM Min value -30 Coded Min 15
n Max value 0 Coded Max 0
Spec ref. Power control and radio link supervision Coded Max 0
Def value 0 Coded Def 0
Coding rules step size = 2dB. 0: 0 dB, 1: -2dB, ..., 15: -30dB
Mandatory rules --
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
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
- it is kept in order to avoid impact on the telecom power reduction algorithms.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment = FADE1958 hexa
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment See BCC (BSC) and NCC (BSC)
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)
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%
- This parameter is configurable from the BSC terminal.
- The default value allows configurations of CCCH_CONF up to 6 (ie 4 CCCHs slots)
Recommended --
rules
External --
comment
Internal comment --
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.
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
- This parameter is configurable from the BSC terminal.
- if EN_AUP_OVER_IP is enabled, the BTS uses instead IPTCH_UDP_PORT_TC_MUX for Uplink traffic to reach TC.
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
provide any IP address yet. They are not displayed.
The IP address is coded on 32 bits in the DLS.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
comment
Internal comment --
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
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 153
Logical CELL_BAR_ACCESS m B11 Yes B12 Yes
name TRX nb No
HMI Administrative cell Barring Sub-syste BSC template Cell Type No
name Instance cell RMS 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
Rec ref. 3GPP TS 05.08 Domai GSM Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. Overload control Coded Max 1
Def value 0 Coded Def 0
Coding rules 0: not barred, 1: barred
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is changeable via “bar-cell” and “debar-cell” operator commands.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
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:
External --
comment
Internal comment --
Recommended --
rules
External Significant if EN_IURG is enabled
comment
Internal comment --
- 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
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.
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
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.
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.
Mandatory rules --
Recommended --
rules
External - Significant if RAT_3G is TDD
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.
Recommended Alcatel-Lucent recommends to have CELL_PARTITION_TYPE = 0 in case of one logical cell (OLC).
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.
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.
Recommended --
rules
External --
comment
Internal comment The CELL_RANGE parameter is not displayed as such to the O&M user.
Recommended --
rules
External The CELL_RANGE parameter is not displayed as such to the O&M user.
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
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)
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
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 --
Mandatory rules LAC and CI can not be equal to 65535 at the same time
Equal to CI (MFS)
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Mandatory rules LAC and CI can not be equal to 65535 at the same time
Equal to CI(n)(MFS)
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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).
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).
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 --
Mandatory rules --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Internal BSS alarm, not OMC-R visualisation
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 --
Mandatory rules --
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 --
Mandatory rules --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
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.
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
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
Recommended --
rules
External --
comment
Internal comment --
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.
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules IPGCH_PACKET_SIZE <= E1_MTU for all IPoE1 Abis links of the aim BSC.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in SYSTEM INFORMATION messages
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in SYSTEM INFORMATION messages. Coded in the software.
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.
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. None Domai GSM Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. External channel changes Coded Max 1
Def value 0 Coded Def 0
Coding rules 0: Ass Failure before HO Reqd, 1: Ass Failure after HO Reqd
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.
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. None Domai 2G-3G Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. Handover preparation Coded Max 1
Def value 0 Coded Def 0
Coding rules 0 : disable, 1 : enable
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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).
- 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.
Recommended Value 3 and 4 should be used only in case of good 3G TDD coverage.
rules
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 219
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
- 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 - This parameter is available in the MFS through the BSCGP interface.
- 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.
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.
- Parameter available on BSC Evolution only.
- 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.
Recommended Value 3 should be used only in case of good LTE TDD coverage.
rules
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 223
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
- Parameter available on BSC Evolution only.
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. But any modification impacts System Information Broadcasting. Change applied
template
immediately after modification, in broadcasted SI2quater messages and in dedicated Channel Release and Packet Measurement Order messages of the current calls.
Internal comment - This parameter is available in the MFS through the BSCGP interface.
- 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.
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 --
Recommended --
rules
External - Significant if RAT_3G is TDD
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).
- Neither 2G to 3G TDD handover, nor The 3G TDD cell reselection with cell info is supported. So this parameter is currently not used.
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 --
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)
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).
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.
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.
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 --
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 --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment it is an optional feature
Recommended --
rules
External - Function available on BSC Evolution only.
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.
Internal comment it is an optional feature
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).
- This parameter is configurable from the BSC terminal.
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
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 - 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.
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 --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Shall be set to 1 only if all RNCs neighbour to this BSS support the feature.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter has not been removed in order not to impact the implementation of the BSC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
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.
Internal comment - Sent to the BTS via OML.
- a switchable power supply is required within the HW MC module (TRX, RRH, TRDU).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Internal comment it is an optional feature
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.
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This flag shall be set to 1 only in Cegetel NW
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. None Domai GSM Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. Resource Allocation and Management Coded Max 1
Def value 0 Coded Def 0
Coding rules 0: disabled,
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 --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Internal comment - it is an optional feature (TRX quantity controlled).
- Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended It is recommended to disable this intracell downlink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended It is recommended to disable this intracell downlink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended It is recommended to disable this intracell uplink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended It is recommended to disable this intracell uplink handover when frequency hopping is applied
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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
Recommended --
rules
External - Function 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.
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
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.
Internal comment - it is an optional feature (TRX quantity controlled).
- GPS-oriented, E-OTD and U-TDOA methods are not supported by ALU BSS
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
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.
Internal comment - it is an optional feature (TRX quantity controlled).
- GPS-oriented, E-OTD and U-TDOA methods are not supported by ALU BSS
Recommended --
rules
External - Parameter available on BSC Evolution only.
comment - Only the value 0 is supported on G2 BSC.
Internal comment - it is an optional feature (TRX quantity controlled).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
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
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.
CT: Depends on Cell Type and BTS Type
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
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).
Internal comment - it is an optional feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended Alcatel-Lucent recommends to enable the RTP multiplexing in order to optimise the BW usage on A interface over IP.
rules
External - Function available on BSC Evolution (with 2 TPGSM boards at least TPV3i3) only.
comment - Parameter change: No impact on the telecom service, on going calls are not disrupted. Change applied immediately after modification
Internal comment --
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
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 - 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.
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
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 - 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
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 - A SAIC capable MS is also called DARP phase 1 MS
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
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 - 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
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
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 - 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
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 - 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
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
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 - 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
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 - 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
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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).
Internal comment - Sent to the BTS via OML.
- it is an optional feature
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.
External - Function available on BSC Evolution only.
comment - Significant when EN_DR is enabled
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment - it is an optional feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Internal comment - Sent to the BTS via OML.
- it is an optional feature, supported from G3 onwards TRE (including MC module).
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
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
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
Mandatory rules --
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
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.
Internal comment - the reset procedure, triggered by the SMLC, is independent of the present parameter.
- Optional procedure in 3GPP TS 49.031
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message.
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only
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)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
External - Function available on BSC Evolution only.
comment - Significant if EN_PAIRING_SAIC_SAIC 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 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).
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 --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only
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)
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
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.
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. None Domai GSM Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. Normal assignment Coded Max 1
Def value 0 Coded Def 0
Coding rules 0:disabled, 1:enabled
Mandatory rules --
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 --
Mandatory rules --
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 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.
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
Internal comment it is an optional feature
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 Function available on BSC Evolution only
comment
Internal comment it is an optional feature.
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
Internal comment Non optional feature (present with AMR-WB), kind of safety flag.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules - EN_VAMOS can be enabled only if the BTS-TransMode (of the concerned BTS(s)) is not in TDM mode.
- If COVERAGE_MODE is set to 1 (case of one logical cell (OLC)) then EN_VAMOS shall be disabled.
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
External - Function available on BSC Evolution only.
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).
Mandatory rules --
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 after the modification.
Internal comment --
Mandatory rules --
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 after the modification, in the radio resource allocation.
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- Significant if HO_INTRACELL_ALLOWED is enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
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 after the modification.
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- Significant if HO_INTRACELL_ALLOWED is enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Mandatory rules --
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
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.
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.
- Parameter available on BSC Evolution only.
Internal comment - Dimensional constraint of the ALU BSS is no more than 8 SI2Quater instances.
- Parameter is relevant only within CMCC networks
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
- 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).
- 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).
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.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 354
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.
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 --
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 --
Mandatory rules --
Recommended --
rules
External Available only if EN_CPICH_2G_3G_Reselection = 1
comment
Internal comment --
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”
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The value 0 is not supported
Recommended --
rules
External --
comment
Internal comment It is linked to the feature “ENHANCED MEASUREMENT REPORT” which is not supported in the ALU BSS.
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.
Mandatory rules --
Recommended --
rules
External Available only if EN_CPICH_2G_3G_Reselection=1
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 --
Mandatory rules --
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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Mandatory 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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai IP Min value 5 Coded Min 5
n Max value 100 Coded Max 100
Spec ref. BSS IP Transport: protocol & configuration Coded Max 100
Def value 7 Coded Def 7
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM.
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
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
Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM.
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.
Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter is sent by the BSC to the BTS via OML, and displayed on BTS-NEM.
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 = “GSM850” or “DCS1900” if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1900 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
Recommended --
rules
External --
comment
Internal comment --
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 --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type.The value indicated here is for implementation purposes.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer. TRXnb: Depends on TRX number
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer.
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 --
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 --
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
Mandatory rules --
Recommended --
rules
External Valid for both TCH and SDCCH. This parameter has no influence on Directed Retry
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External This parameter has no influence on Directed Retry
comment
Internal comment CT: Depends on Cell Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
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
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Category Network (CDE) OMC-R access None (DLS) Type Number Unit sec
Rec ref. None Domai IP Min value 1 Coded Min 1
n Max value 100 Coded Max 100
Spec ref. TC/BTS Interface Coded Max 100
Def value 10 Coded Def 10
Coding rules Step size = 1.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML
- 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
Category Network (CDE) OMC-R access None (DLS) Type Threshold Unit None
Rec ref. None Domai IP Min value 1 Coded Min 1
n Max value 100 Coded Max 100
Spec ref. TC/BTS Interface Coded Max 100
Def value 5 Coded Def 5
Coding rules Step size = 1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML.
Mandatory rules --
Recommended --
rules
External This timer is not relevant when EN_IP_CONGESTION_1ST_LEVEL is disabled.
comment
Internal comment --
Mandatory rules IPGCH_PACKET_SIZE <= E1_MTU for all IPoE1 Abis links of the aim BSC.
Recommended - IPGCH sending window size (i.e. 496 on G5/G6 TRE) x IPGCH_PACKET_SIZE / round trip delay between MFS and BTS >= maximum theoretical throughput possible
rules 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. In particular, in case of low BW last mile (ex: DSL line), it could be necessary to reduce the
IPGCH_PACKET_SIZE to 300 in order to improve the voice quality.
Internal comment - Sent by BSC to MFS via BSCGP (Abis group object unknown by MFS O&M).
- Sent by BSC to BTS via OML.
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 = h’D100, Max = h’D4FF
- Alignement of the BTP on BSC DLS content.
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.
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.
Recommended --
rules
External --
comment
Internal comment - Sent by the BSC to MFS via BSCGP.
Recommended --
rules
External --
comment
Internal comment - Sent by the BSC to MFS via BSCGP.
- Provided by MFS to BTS.
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.
The IP address is coded on 32 bits in the DLS.
- This IP address is computed by the BSC (per CCP board) from the START_BSS_IP_ADDRESS_BSC.
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
provide any IP address yet. They are not displayed.
The IP address is coded on 32 bits in the DLS.
Mandatory 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=h’CD90, Max=h’CD91
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules - IURG_SCTP_ENDPOINT_IP_ADDRESS_1 and IURG_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one RNC.
- 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 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
provide any IP address yet. They are not displayed.
- The IP address is coded on 32 bits in the DLS.
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
provide any IP address yet. They are not displayed.
-The IP address is coded on 32 bits in the DLS.
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)
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 - 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).
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is not applicable to the uplink. The BTS (OMU) value is hardcoded.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is not applicable to the uplink. The BTS (OMU) value is hardcoded.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is not applicable to the uplink. The BTS (OMU) value is hardcoded.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter is not applicable to the uplink. The BTS (OMU) value is hardcoded.
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).
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.
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).
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.
Mandatory rules --
Recommended --
rules
External - significant only if EN_AUP_OVER_IP is disabled
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer. TRXnb: Depends on TRX number
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where CELL_LAYER_TYPE = Upper layer
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant when EN_PREFERRED_BAND_FORCED_DR is enabled
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
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 CT: Depends on Cell Type and BTS Type
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
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External Highest value is the worst quality.
comment
Internal comment --
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting L_RXQUAL_DL_P_AMR = L_RXQUAL_DL_P
rules
External - Function available on BSC Evolution only.
comment - Highest value is the worst quality.
- Parameter change: no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
Recommended To take benefit from the feature repeated ACCH, Alcatel-Lucent recommends :
rules L_RXQUAL_DL_P_AMR_RXACCH >= L_RXQUAL_DL_P_AMR
External - Function available on BSC Evolution only.
comment - Highest value is the worst quality.
- Parameter change : no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
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
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- 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 --
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting L_RXQUAL_DL_P_AMR_VAMOS = L_RXQUAL_DL_P_VAMOS.
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- 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 --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- 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 --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External Highest value is the worst quality.
comment
Internal comment --
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting L_RXQUAL_UL_P_AMR = L_RXQUAL_UL_P
rules
External - Function available on BSC Evolution only.
comment - Highest value is the worst quality.
- Parameter change: no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
Recommended To take benefit from the feature repeated ACCH, Alcatel recommends :
rules L_RXQUAL_UL_P_AMR_RXACCH >= L_RXQUAL_UL_P_AMR
External - Function available on BSC Evolution only.
comment - Highest value is the worst quality.
- Parameter change : no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
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
Mandatory rules LAC and CI can not be equal to 65535 at the same time
Equal to LAC (MFS)
A couple of mate extended cells (Extended inner + extended outer) shall have the same LAC.
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Mandatory rules --
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 LAC (no dummy value needed).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Not used in case of OVERLOAD received from FU supporting the BCCH
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Not used in case of OVERLOAD received from FU supporting the BCCH
Mandatory 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 --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules - LB_SCTP_ENDPOINT_IP_ADDRESS_1 and LB_SCTP_ENDPOINT_PORT shall together uniquely identify a SCTP endpoint inside one SMLC.
- 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 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
provide any IP address yet. They are not displayed.
The IP address is coded on 32 bits in the DLS.
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
provide any IP address yet. They are not displayed.
The IP address is coded on 32 bits in the DLS.
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 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)
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 - 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).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Timer Unit None
Rec ref. None Domai GPRS Min value 3 Coded Min 3
n Max value 30 Coded Max 30
Spec ref. Resource Allocation and Management Coded Max 30
Def value 3 Coded Def 3
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules - LOCAL_ASIG_SCTP_ENDPOINT_IP_Address_1 and LOCAL_ASIG_SCTP_ENDPOINT_PORT shall together be unique inside the BSC.
Mandatory rules - LOCAL_ASIG_SCTP_ENDPOINT_IP_ADDRESS_2 (when configured) and LOCAL_ASIG_SCTP_ENDPOINT_PORT shall together be unique inside the BSC.
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.
Internal comment - In the BSC, there is one SCTP endpoint per MSC, connected to the BSC.
- 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.
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
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).
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
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).
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
Internal comment TRXnb: Depends on TRX number
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.
Mandatory rules --
Recommended --
rules
External The default value corresponds to an unused parameter for the MS.
comment
Internal comment --
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 --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Min = h’CD70, Max = h'CD87
Recommended --
rules
External --
comment
Internal comment - Sent to TC via TCSL
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment (MATE_LAC + MATE_CI) is relevant for extended cells only
Internal comment --
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
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment (MATE_LAC + MATE_CI) is relevant for extended cells only
Internal comment --
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.
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).
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
If EN_VGCS= enabled, then “(MAX_VGCS_TS + MAX_PDCH) < Total number of TCHs of the cell”
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.
If EN_VGCS= enabled, then “(MAX_VGCS_TS + MAX_PDCH) < Total number of TCHs of the cell”
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.
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
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 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: MAX_PDCH = 2, MAX_PDCH_HIGH_LOAD = 1, MIN_PDCH = 1.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 523
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment m
To support LCS in a cell, it is mandatory to have Max_PDCH > 0
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
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.
- MX BSC received two values (one from the OMC, and one from MFS via BSCGP); last one is ignored.
Recommended --
rules
External 127 is a theoretical value: 16 TRX * 8 PDCH - BCCH.
comment
Internal comment - The MPDCHs (primary and secondary) are also taken into account in this parameter.
- The parameter value is stored in the memory (not in DLS file on disk), based on BSCGP received information
Recommended --
rules
External 127 is a theoretical value: 16 TRX * 8 PDCH - BCCH.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
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 --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended - In order to use the whole BSS capacity, Alcatel-Lucent recommends setting this parameter to 100%
rules
External - Function available on BSC Evolution only.
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 --
Mandatory rules --
Recommended In order to use the whole cell capacity, Alcatel-Lucent recommends setting this parameter to 100%.
rules
External - Function available on BSC Evolution only.
comment - Significant when either HR_ENABLED or EN_AMR_HR is enabled in the cell.
- 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 MAX_TCH_HALF_RATE_PER_CELL parameter can be set independently of the parameter MAX_TCH_HALF_RATE.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment To support VGCS in a cell, it is mandatory to have Max_VGCS_TS > 0
Internal comment --
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.
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- 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.
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).
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).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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
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 --
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.
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment
Internal comment - The MPDCHs (primary and secondary) are also taken into account in this parameter.
- The parameter value is stored in the memory (not in DLS file on disk), based on BSCGP received information
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.
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment
Internal comment - The MPDCHs (primary and secondary) are also taken into account in this parameter.
- MX BSC received two values (one from the OMC, and one from MFS via BSCGP); last one is ignored.
Mandatory rules --
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 after the modification.
Internal comment --
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
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- MNC (BSC) = MNC (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 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.
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- MNC(n) (BSC) = MNC(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 (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 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.
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)
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] 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).
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.
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] 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).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
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 “1”: (interpreted as 41 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.
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 “1”: (interpreted as 41 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.
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 “1”: (interpreted as 41 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.
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 “1”: (interpreted as 41 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.
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 “1”: (interpreted as 41 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).
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”,
“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.
3) 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.
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
Default value for DCS1900: 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.
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.
Recommended - The operator must control that, in a PLMN, 2 MSCs must have 2 different MSC_CN_ID.
rules
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
- 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 --
Recommended --
rules
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
- The operator must control that the BSC and all the MSCs connected to that BSC via Aflex feature must belong to the same PLMN.
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).
Recommended --
rules
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
- The operator must control that the BSC and all the MSCs connected to that BSC via Aflex feature must belong to the same PLMN.
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).
Recommended --
rules
External - Significant only if EN_A_FLEX is enabled.
comment - Aflex function is available on BSC Evolution only.
- 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
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).
Mandatory rules --
Recommended It is recommended to set a weight value consistent with the number of A-trunks connected to that MSC.
rules
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
- 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 --
Recommended --
rules
External Default value depends on MSC type
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).
Recommended --
rules
External Default value depends on MSC type
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).
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
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 --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant when EN_PREFERRED_BAND_FORCED_DR is enabled
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment - TRXnb: Depends on TRX number
Recommended --
rules
External The different choices are:
comment - 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.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Parameter change: Change apply immediately and to all established calls.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is enabled.
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)
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 - RTCP streams are not muxed
- default = 7FF0x
- This parameter is configurable from the BSC terminal.
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
- The IP address is coded on 32 bits in the DLS.
- computed by the BSC = START_BSS_IP_ADDRESS_BSC + 2
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) doesn’t apply to P0 traffic (speech).
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message. CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment MSC: Depends on MSC Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment TRXnb: Depends on TRX number
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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.
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)
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).
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.
- The default value is the results of load tests performed on G2 BSC in B10, which brought DTC stability (no reset)
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.
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
3)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.
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.
Mandatory rules --
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
comment - Significant if EN_RESET_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.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment MSC: Depends on MSC Type
Mandatory rules --
Recommended --
rules
External - Parameter change: No impact on the telecom service, on going calls are not disrupted.
comment
Internal comment MSC: Depends on MSC Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment MSC: Depends on MSC Type
Mandatory rules --
Mandatory rules --
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
Recommended --
rules
External The value depends on configuration. The default value indicated here is for implementation purposes.
comment
Internal comment This parameter was previously named: “PLMN_permitted”.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 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.
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 - Feature specific for CMCC
- this parameter is configurable (by ALU team) from the BSC terminal (from lab version)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
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 - 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.
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.
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
- 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 - According to 3GPP TS 23.236, more than one NRI may be assigned to a CN node.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended The operator must control that the NULL_NRI is common inside all the BSSs of one PLMN.
rules
External - Significant only if EN_A_FLEX is enabled
comment - Aflex function is available on BSC Evolution only.
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 - According to TS23.236, there is one unique null NRI in a PLMN.
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 --
Recommended --
rules
External The parameter is significant when EN_VGCS is enabled
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment It is a CDM parameter
Recommended --
rules
External --
comment
Internal comment - Sent to the TC via TCSL.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Relative value added to L_RXQUAL_UL_H and L_RXQUAL_DL_H
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Relative value added to L_RXQUAL_UL_P and L_RXQUAL_DL_P
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 --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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
Category Network (CDE) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai IP Min value 0 Coded Min 0
n Max value 7 Coded Max 7
Spec ref. BSS IP Transport: protocol & configuration Coded Max 7
Def value 5 Coded Def 5
Coding rules step size = 1
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.
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.
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.
Category Network (CDE) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai IP Min value 0 Coded Min 0
n Max value 7 Coded Max 7
Spec ref. BSS IP Transport: protocol & configuration Coded Max 7
Def value 0 Coded Def 0
Coding rules step size = 1.
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.
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 --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
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.
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
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.
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
Internal comment --
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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“.
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“.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 = “GSM850” or “DCS1900” if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1900 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 --
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
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External This parameter relates to support of DCS-1800 4W MS.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 - The “mandatory rule” has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Internal BSS alarm, not OMC-R visualisation
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 --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External not used if EN_HSL = 1
comment
Internal comment In IP mode, NOT sent to the TC via TCSL
Mandatory rules --
Recommended --
rules
External used if EN_HSL = 1
comment
Internal comment In IP mode, NOT sent to the TC via TCSL
Mandatory rules --
Recommended --
rules
External not used if EN_HSL = 1
comment
Internal comment In IP mode, sent to the TC via TCSL
Mandatory rules --
Recommended --
rules
External used if EN_HSL = 1
comment
Internal comment In IP mode, sent to the TC via TCSL
Mandatory rules --
Recommended --
rules
External not used if EN_HSL = 1
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.
Mandatory rules --
Recommended --
rules
External used if EN_HSL = 1
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment In IP mode, , the coded value is sent to the TC via TCSL
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - In IP mode, the coded value issent to the TC via TCSL
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
Mandatory rules --
Recommended --
rules
External not used if EN_HSL = 1
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
Mandatory rules --
Recommended --
rules
External used if EN_HSL = 1
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - In IP mode, the coded value is sent to the TC via TCSL
Recommended --
rules
External --
comment
Internal comment In IP mode, the coded value is sent to the TC via TCSL
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
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 - The “mandatory rule” has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
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
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 --
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”).
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 768
m
template
Mandatory rules --
Recommended --
rules
External - Parameter available on BSC Evolution only.
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).
Mandatory rules --
Recommended In a cell with FDD_ARFCN_list not empty, Qsearch_I =-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 BCCH
Internal comment --
Mandatory rules --
Recommended In a cell with FDD_ARFCN_list not empty, Qsearch_P =-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 in GPRS.
This parameter is broadcast on BCCH and on PBCCH if there is a PBCCH allocated in the serving cell.
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”).
Mandatory rules --
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.
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.
Recommended --
rules
External The value depends on configuration. The default value indicated here is for implementation purposes.
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).
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only
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".
- 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)
- 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.
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message.
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
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message.
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 --
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 --
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.
Recommended --
rules
External Parameter available on BSC Evolution only.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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).
- 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
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
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)
Recommended --
rules
External - Function available on BSC Evolution only.
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).
- 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)
Recommended --
rules
External - Function available on BSC Evolution only.
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).
- 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)
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
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).
Internal comment CDM parameter (sent by BSC to BTS on the OML)
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
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).
Internal comment CDM parameter (sent by BSC to BTS on the OML)
Category System (CST) OMC-R access None (DLS) Type Threshold Unit None
Rec ref. None Domai GSM Min value 0 Coded Min 0
n Max value 100 Coded Max 100
Spec ref. LAPDM functional specification Coded Max 100
Def value 3 Coded Def 3
Coding rules --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - The REP_UL_SACCH_THRES and WS defaults values trigger RUSACCH as soon as the legacy SER becomes superior or equal to 30%.
Internal comment CDM parameter (sent by BSC to BTS on the OML)
Category System (CST) OMC-R access None (DLS) Type Number Unit Samfr
Rec ref. None Domai GSM Min value 1 Coded Min 1
n Max value 100 Coded Max 100
Spec ref. LAPDM functional specification Coded Max 100
Def value 10 Coded Def 10
Coding rules --
Mandatory rules --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - The REP_UL_SACCH_THRES and WS defaults values trigger RUSACCH as soon as the legacy SER becomes superior or equal to 30%.
Internal comment CDM parameter (sent by BSC to BTS on the OML)
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment Used only when NBR_RESET_REP <> 0.
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
External Default value depends on MSC type
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 --
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
External - Parameter available on BSC Evolution only.
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
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.
Mandatory rules (MCC_3G, MNC_3G, RNC_ID_3G and CI_3G) shall together uniquely identify a 3G cel.
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 RNCId (no dummy value needed).
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 --
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).
Recommended --
rules
External - Default value depends on configuration. The value indicated here is for implementation purposes.
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 --
Recommended --
rules
External --
comment
Internal comment --
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 --
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.
Mandatory rules --
Recommended --
rules
External Significant if one logical cell is active (COVERAGE_MODE = 1).
comment Function available on BSC Evolution only.
Internal comment In case of inactive one logical cell (COVERAGE_MODE <> 1), RACH_TA_FILTER is applicable.
Mandatory rules --
Recommended --
rules
External Significant if one logical cell is active (COVERAGE_MODE = 1).
comment Function available on BSC Evolution only.
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Deduced from O&M parameter: BSI-Link-Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML.
- Min = h’CF00, Max = h’CFFF
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
comment - Significant if EN_AUP_OVER_IP is enabled.
Internal comment - function is hosted by the active TPGSM
- The IP address is coded on 32 bits in the DLS.
- computed by the BSC = START_AUP_IP_ADDRESS_BSC + 2
Mandatory rules --
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is enabled.
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).
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 = 8000x
- This parameter is configurable from the BSC terminal.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 after the modification, in the radio resource allocation.
Internal comment --
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 after the modification, in the radio resource allocation.
Internal comment --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External --
comment
Internal comment --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment CT: Depends on Cell Type and BTS Type
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- Highest value is the worst quality.
- 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 --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- Highest value is the worst quality.
- 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 --
Recommended --
rules
External - Function available on BSC Evolution only.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
-
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.
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS_SUB_SAIC_BLACKLIST is enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied immediately after the modification.
Internal comment - The positive value makes the pairing of a substandard SAIC with another MS more difficult than for a standard SAIC.
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.
- Alcatel-Lucent recommends - SCPIR_LOW_MS_ALLOC_VAMOS1 < SCPIR_LOW_MS_ALLOC_NON_SAIC to forbid (non SAIC, VAMOS1) MS pairing.
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.
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 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.
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 longer the corresponding MS type is able to stay paired with the same companion.
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS_SUB_SAIC_BLACKLIST 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 --
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 longer the corresponding MS type is able to stay paired with the same companion.
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 longer the corresponding MS type is able to stay paired with the same companion.
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 immediately after the modification.
Internal comment - SCPIR valid range is -10,+10 (length = 20)
Mandatory rules --
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 - This parameter is sent to the BTS via OML
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_NON_SAIC_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_SAIC are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_SAIC are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_SAIC are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_SAIC_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS1 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS1_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS2_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS2_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only
comment - Significant if EN_VAMOS and EN_PAIRING_VAMOS2_VAMOS2 are enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment --
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
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External - Default value depends on configuration. The value indicated here is for implementation purposes.
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 --
Mandatory rules --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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).
Recommended --
rules
External - Default value depends on configuration. The value indicated here is for implementation purposes.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Can be changed only when SMSCB_State is disabled
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment - Used for OML establishment.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External SSF (Sub-Service Field) is composed of 4 bits: 2bits for Network Indicator and 2 spare bits.
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External The parameter is significant only if EN_UPLINK_REPLY is set to true.
comment
Internal comment It is a CDM parameter
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 --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS_SUB_SAIC_BLACKLIST is enabled.
- Parameter change: No impact on the telecom service, on going traffic is not disrupted. Change applied after the modification.
Internal comment - TAC is extracted from the IMEISV of the Ciphering Mode Complete message sent by the MS to the MSC.
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended ALU highly recommends setting this timer to 6 seconds to improve the BSC robustness.
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
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 - Feature specific for CMCC
- 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
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_AUP_OVER_IP is enabled.
- 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).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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.
Mandatory rules --
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
comment - Significant if EN_LB is enabled
- 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
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External T_INHIBIT_CPT = 0 inhibits the anti ping-pong function.
comment
Internal comment --
Mandatory rules T_INTRF_L3 > Max (T11, T_qho, T11_FORCED) & T_INTRF_L3 > INTAVE
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Not used in case of OVERLOAD received from FU supporting the BCCH
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
comment - Significant if EN_LB is enabled
- 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 --
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.
Mandatory rules --
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
comment - Significant if EN_LB is enabled
- 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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Significant if EN_AUP_OVER_IP is disabled
comment
Internal comment - Sent to the BTS via OML and to the TC via TCSL.
- When EN_AUP_OVER_IP is enabled, the BSC uses T_MAX_HOLD_MUXTRAUP_TPIP instead.
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
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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 not combined/1/1000/
Disabled/False/CCCH not combined/2/1000/
Disabled/False/CCCH not combined/3/1000/
Disabled/False/CCCH not combined/4/800/
Disabled/False/CCCH not combined/5/600/
Disabled/False/CCCH not combined/6/600/
Disabled/False/CCCH not combined/7/600/
Disabled/False/CCCH combined/0/1000/
Disabled/False/CCCH combined/1/1000/
Disabled/False/CCCH combined/2/1000/
Disabled/True/CCCH not combined/0/x/Not allowed
Disabled/True/CCCH not combined/1/2000/
Disabled/True/CCCH not combined/2/1000/
Disabled/True/CCCH not combined/3/1000/
Disabled/True/CCCH not combined/4/1000/
Disabled/True/CCCH not combined/5/800/
Disabled/True/CCCH not combined/6/600/
Disabled/True/CCCH not combined/7/600/
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/
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 953
m
template
Recommended --
rules
External --
comment
Internal comment MSC: Depends on MSC Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted by the OMC-R to the BSC at init with the OCD_admin tool
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment It is a CDM parameter
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.
Mandatory rules --
Recommended --
rules
External - Parameter available on BSC Evolution only.
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
External - Significant if EN_AUP_OVER_IP is enabled.
comment
Internal comment - This parameter is configurable from the BSC terminal.
Mandatory rules --
Recommended --
rules
External - Significant if EN_LB is enabled
comment
Internal comment --
Mandatory rules --
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML.
Mandatory rules --
Recommended --
rules
External This parameter is set to 620ms by the BSC in case of Abis/Ater via satellite.
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External - Lb interface is available on BSC Evolution only.
comment - Significant if EN_RESET_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.
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment Must be < assignment timer in the MSC (trr1).
Provision in MIB B5
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Comes from the split of T18 into two timers: T18 and T18_OVERLOAD
Mandatory rules --
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Mandatory rules --
Recommended Values higher than 1000ms 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 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.
Mandatory rules --
Recommended Values higher than 1000ms 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 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.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Transmitted to the BTS in the BTS_CONF_DATA message
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended T3111 > 2 x T200_D. T3111 > 2 x T200_TH. T3111 = T3110 (MS)
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment It is a CDM parameter
Category Site (CAE) OMC-R access Changeable Type Timer Unit sec
Rec ref. 3GPP TS 44.018 Domai 2G-3G Min value 0 Coded Min 0
n Max value 25.5 Coded Max 255
Spec ref. Not linked to a document Coded Max 255
Def value 14 Coded Def 140
Coding rules step size = 0.1 sec
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Corresponds to T3148 (on MS side) - Round Trip Delay
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.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 1016
m
template
Note that the chosen default values shall ensure that those rules are met.
==> Case GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell:
i) T3192 = 1500 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 = 1000 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
EN_DELAYED_DL_TBF_REL = 1)
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
Recommended --
rules
External --
comment
Internal comment --
1 0 1: 120 msec
1 1 0: 160 msec
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.
Recommended --
rules
External Default value depends on MSC type
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended T9105 > max T3210. T9105 > max T3220. T9105 > max T3230
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended T9112 >= 15s. T9112 <= T9114. T9112 is inferior to the MSC timer supervising the Modify procedure.
rules
External --
comment
Internal comment --
Mandatory rules T9113 > T3105_D x Ny1. T9113 > T3105_F x Ny1. T9113 > T3106_D. T9113 > T3106_F
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External 1 bper corresponds to about 550m
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Mandatory rules --
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.
Mandatory rules --
Category Site (CAE) OMC-R access Changeable Type List of numbers Unit None
Rec ref. 3GPP TS 25.102 Domai 2G-3G Min value 0 Coded Min 0
n Max value 16383 Coded Max 16383
Spec ref. System information management Coded Max 16383
Def value None Coded Def -1
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
- 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.
- 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.
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
- 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.
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.
Mandatory rules --
Recommended --
rules
External This parameter is broadcast on BCCH.
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”
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 Cannot be understood by GSM Phase 1 MS.
CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Percentage of busy to successful accesses. Transmitted to the BTS in the BTS_CONF_DATA message
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 --
Mandatory rules --
Recommended --
rules
External Value 0 disables the feature.
comment
Internal comment --
Mandatory rules THR_CELL_LOAD_LTE_REJECT shall be lower than the 2G load thresholds HIGH_TRAFFIC_LOAD or equal to 100%.
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied on new handovers procedures initiated after modification.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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)
rules /100*total number of TCH in the cell.
External --
comment
Internal comment --
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 after the modification, in the radio resource allocation.
Internal comment --
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 after the modification, in the radio resource allocation.
Internal comment --
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)
rules /100*total number of TCH in the cell.
External --
comment
Internal comment --
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)
rules /100*total number of TCH in the cell.
External --
comment
Internal comment --
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 after the modification, in the radio resource allocation.
Internal comment --
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 after the modification, in the radio resource allocation.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Not used in case of OVERLOAD received from FU supporting the BCCH
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
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.
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
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 - The first “mandatory rule” has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
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
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 - The first “mandatory rule” has to be checked on a per RAT basis (FDD/TDD) for cases where FDD/TDD UARFCN ranges overlap.
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
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 --
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
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 --
Mandatory rules --
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.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 --
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 --
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 --
Recommended --
rules
External - Default value depends on configuration. The value indicated here is for implementation purposes.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML and to the TC via TCSL.
- 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
Mandatory rules --
Recommended --
rules
External - Parameter change: No impact on the telecom service, on going calls are not disrupted.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Treassembly < T9110 (the rule is checked neither by BSC nor by the OMC.)
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 --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
3)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
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).
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Default value depends on configuration. The value indicated here is for implementation purposes.
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.
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.
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 after the modification.
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.
Recommended --
rules
External - Significant if RAT_3G is TDD
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).
- Neither 2G to 3G TDD handover, nor The 3G TDD cell reselection with cell info is supported. So this parameter is currently not used.
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 MS’s 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:
Note:
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 1110
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.
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
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
Recommended --
rules
External Highest value is the worst quality
comment
Internal comment --
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting U_RXQUAL_DL_P_AMR = U_RXQUAL_DL_P.
rules
External - Function available on BSC Evolution only.
comment - Highest value is the worst quality.
- Parameter change: no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting U_RXQUAL_DL_P_AMR_VAMOS = U_RXQUAL_DL_P_VAMOS
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- 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 --
Recommended --
rules
External - Function available on BSC Evolution only.
comment - Significant if EN_VAMOS is enabled.
- 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 --
Recommended --
rules
External Highest value is the worst quality
comment
Internal comment --
Recommended To avoid the risk of call drops, Alcatel-Lucent recommends setting U_RXQUAL_UL_P_AMR = U_RXQUAL_UL_P
rules
External - Function available on BSC Evolution only.
comment - Highest value is the worst quality.
- Parameter change: no impact on the telecom service. Change applied on new calls (after modification).
Internal comment --
Mandatory rules --
Recommended --
rules
External One unit corresponds to a distance of about 550m
comment
Internal comment CT: Depends on Cell type
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.
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 after the modification.
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
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 --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Meaningful only in cells where: Cell_type = Microcell
Recommended --
rules
External --
comment
Internal comment --
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 --
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 after the modification.
Internal comment --
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 after the modification.
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 after the modification.
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai GSM Min value 1 Coded Min 1
n Max value 3 Coded Max 3
Spec ref. Radio measurements data processing Coded Max 3
Def value 1 Coded Def 1
Coding rules --
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 after the modification.
Internal comment --
Mandatory rules --
Recommended --
rules
External The parameter is significant only if EN_UPLINK_REPLY is set to true.
comment
Internal comment It is a CDM parameter
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment This parameter is meaningful only in cells with: cell_PARTITION_TYPE = Concentric cell
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
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 = h’D100, Max = h’D4FF
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the BTS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the BTS
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).
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 = h’D000, Max = h’D0FF
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Recommended values:4 for 16 kbit/s RSL, 7 for 64 kbit/s RSL
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via FU.CPF
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Category System (CST) OMC-R access None (not in DLS) Type Number Unit None
Rec ref. GSM TS 04.06 Domai GSM Min value 34 Coded Min 34
n Max value 34 Coded Max 34
Spec ref. LAPDm functional specification Coded Max 34
Def value 34 Coded Def 34
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Category System (CST) OMC-R access None (not in DLS) Type Number Unit None
Rec ref. GSM TS 04.06 Domai GSM Min value 29 Coded Min 29
n Max value 29 Coded Max 29
Spec ref. LAPDm functional specification Coded Max 29
Def value 29 Coded Def 29
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the firmware
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 --
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via OML
- Min = h’CF00, Max = h’CFFF.
- 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.
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Values for each TRE are computed by the BTS in the range specified.
- Min = h’D700 Max = h’D7FF
Recommended --
rules
External --
comment
Internal comment - Harcoded in the BTS
Recommended --
rules
External --
comment
Internal comment Sent to the FU at initialisation via FU_CPF.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the software. Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the software. Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the software. Configured via the FU.CPF file
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
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Configured via FU.CPF
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Configured via FU.CPF
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment hardcoded in OMU PROM.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
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 --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Mandatory rules --
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.
Internal comment - Configured via FU.CPF
- 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
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured in the BTS via the FU.CPF file
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Configured via FU.CPF
- 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
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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 600 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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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 600 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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the TRE SW.
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 600 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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Configured via the FU.CPF file
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).
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. 3GPP TS 04.60 Domai GPRS Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. GPRS radio interface - RRM sublayer Coded Max 1
Def value 0 Coded Def 0
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 --
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]
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.
Recommended --
rules
External --
comment
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai LCS Min value 1 Coded Min 10
n Max value 1.5 Coded Max 15
Spec ref. LCS Functional Specification Coded Max 15
Def value 1.2 Coded Def 12
Coding rules step size = 0.1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution
comment - Only significant when EN_PFC_FEATURE = 2
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution
comment - Only significant when EN_PFC_FEATURE = 2
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution
comment - Only significant when EN_PFC_FEATURE = 2
Internal comment --
Mandatory rules --
Recommended --
rules
External -Function available on MFS Evolution only
comment - Significant if EN_ATER_GCH_EQUITY is enabled
- Applicable only to TDM mode.
Internal comment --
Mandatory rules --
Recommended --
rules
External -Function available on MFS Evolution only
comment - Significant if EN_ATER_GCH_EQUITY is enabled
- Applicable only to TDM mode.
Internal comment --
Mandatory rules --
Recommended --
rules
External -Function available on MFS Evolution only
comment - Applicable only to TDM mode.
- Significant if EN_ATER_GCH_EQUITY is enabled.
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Applicable only to TDM mode.
- Significant if EN_ATER_GCH_EQUITY is enabled
Internal comment --
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 --
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.
External - Applicable only to TDM mode.
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 --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Hardcoded in MAC layer
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment Needed for MPDCH feature
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.
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.
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 --
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).
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).
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.
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 --
Recommended --
rules
External The bigger this parameter is, the lesser the MS power consumption is.
comment
Internal comment Needed for MPDCH feature
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.
Recommended --
rules
External --
comment
Internal comment - Needed for MPDCH feature.
- The displayed values are 1..4/ For instance, the coded value 00 should be displayed as "1 (block B0 used)”
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Recommended --
rules
External --
comment
Internal comment This parameter only applies to cells where there is no PCCCH.
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.
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).
- it is kept in order to avoid impact on the telecom power reduction algorithms.
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory 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%.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External Applicable to GP2 board.
comment Parameter change: No impact on the telecom service, on going traffic is not disrupted.
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP3 board.
comment Parameter change: No impact on the telecom service, on going traffic is not disrupted.
Internal comment --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment The CELL_RANGE parameter is not displayed as such to the O&M user.
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS.
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 --
Recommended --
rules
External Applicable to GP2 board
comment
Internal comment --
Recommended --
rules
External Applicable to GP3 board
comment
Internal comment --
Mandatory rules LAC and CI can not be equal to 65535 at the same time
Equal to CI (BSC)
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Mandatory rules LAC and CI can not be equal to 65535 at the same time.
Equal to CI(n)(BSC).
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Mandatory rules CIR=0 when “direct access” is used, CIR=0 <=> CBS=0 => EBS > 0
CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
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).
Category Network (CDE) OMC-R access None (DLS) Type Number Unit %
Rec ref. None Domai LCS Min value 0 Coded Min 0
n Max value 100 Coded Max 1000
Spec ref. LCS Functional Specification Coded Max 1000
Def value 50.7 Coded Def 507
Coding rules step size = 0.1
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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)
Recommended --
rules
External --
comment
Internal comment this parameter is hard-coded in the BTS.
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_ST_DEF_VALUE (CS_AVG_PERIOD_ST is assumed rarely modified on the fields)
Recommended --
rules
External --
comment
Internal comment this parameter is hard-coded in the BTS.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External This parameter applies to both GPRS and EGPRS TBFs.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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.
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Sent on PSI 13 on PACCH when no MPDCH
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
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%
Recommended --
rules
External Applicable to TDM only.
comment
Internal comment --
Recommended --
rules
External Applicable to TDM only.
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 R’97 feature
but has been completely clarified in Rel-6).
- R’99 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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Recommended --
rules
External - Function available on MFS Evolution only
comment - Applicable only to TDM mode.
Internal comment --
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 PDU’s 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.
Category Site (CAE) OMC-R access Changeable Type Flag Unit None
Rec ref. None Domai GPRS Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 1
Def value 0 Coded Def 0
Coding rules 0: disabled
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 - Alcatel Lucent recommends disabling the packet downlink power control in one logical cell (OLC) because RRHs may have different output power that may involves
possible inconsistencies at MS side related to the P0 and PR field in DL RLC/MAC radio blocks provided to the MS.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External - The activation of this positioning method is meaningful when EN_LCS=1.
comment - Only the value 0 is supported
Internal comment --
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.
External This parameter applies to both GPRS and EGPRS TBFs.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External This parameter applies to both GPRS and EGPRS TBFs.
comment
Internal comment --
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 --
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
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 --
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai GPRS Min value 0 Coded Min 0
n Max value 2 Coded Max 2
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 2
Def value 0 Coded Def 0
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 --
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.
Internal comment - Feature specific for CMCC
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.
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.
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.
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).
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).
Internal comment - it is an optional feature
- up to MAX_NB_SGSN (BOP) = 16 SGSN can be connected to one BSS
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.
Internal comment - Feature specific for CMCC
- it is an optional feature (TRX quantity controlled).
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 --
Recommended --
rules
External - Parameter available on BSC Evolution only.
comment - Only the value 0 is supported on G2 BSC.
Internal comment - it is an optional feature (TRX quantity controlled).
Recommended --
rules
External - Function available on MFS Evolution only
comment - This parameter is not displayed by the OMC (only EN_ LONG_TBF_WEIGHT (OMC) is displayed.
- 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
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 TBF established.
Internal comment - Feature specific for CMCC
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 --
Recommended --
rules
External - The activation of this positioning method is meaningful when EN_LCS=1.
comment - Only the value 0 is supported.
Internal comment --
Recommended --
rules
External - The activation of this positioning method is meaningful when EN_LCS=1.
comment - Only the value 0 is supported
Internal comment --
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).
Internal comment it is an optional feature
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Function available on MFS Evolution
comment For a PDCH where an instant message TBF is allocated, OCCUPANCY_RATE_TBF_INSTANT_MESSAGE
sets the occupancy rate of that TBF on the PDCH for RRM-PRH radio resources allocation.
Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Internal comment it is an optional feature
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.
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.
Recommended --
rules
External Parametre change: Any modification of the parameter leads to reset autonomously all the PMUs connected to this BSS.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature.
The neighbour cell parameters 2 provides a shorter coding of neighbour cells parameters which improves the cell reselection duration.
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 --
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
Internal comment - it is an optional feature (TRX quantity controlled).
- the feature is not supported by G3 TRE.
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 --
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.
Recommended --
rules
External - Only the value 0 is supported.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Used to determine O&M parameter SOLSA_FUNCT_LEVEL.
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 --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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 CS3 and MCS3 bitrates.
Internal comment - An indication of ESS = 1 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_1.
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 CS4 and MCS4 bitrates.
Internal comment - An indication of ESS = 2 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_2.
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 MCS5 bitrate.
Internal comment - An indication of ESS = 3 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_3.
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 MCS6 bitrate.
Internal comment - An indication of ESS = 4 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_4.
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 MCS7 bitrate.
Internal comment - An indication of ESS = 5 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_5.
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 MCS8 bitrate.
Internal comment - An indication of ESS = 6 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_6.
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 MCS9 bitrate.
Internal comment - An indication of ESS = 7 on IPGCH interface will be interpreated by PCC as TBF estimated speed = nb allocated PDCH * Estimated_Speed_CS_FAMILY_7.
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution only
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.
Internal comment - Feature specific for CMCC
Mandatory rules --
Recommended --
rules
External This parameter is broadcast 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”
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
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",
Category System (CST) OMC-R access None (DLS) Type Number Unit block period
Rec ref. None Domai GPRS Min value 1 Coded Min 1
n Max value 50 Coded Max 50
Spec ref. GPRS radio interface - MAC sublayer Coded Max 50
Def value 7 Coded Def 7
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
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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
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).
External - Applicable only to TDM mode.
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
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.
Mandatory rules --
Recommended --
rules
External The value of this parameter is linked with N3105_Limit_Satellite.
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External The default value depends on the BCCH frequency band:
comment Default value for P-GSM/G1: 43 dBm
Default value for GSM850: 39 dBm
Default value for DCS1800: 30 dBm
Default value for DCS1900: 30 dBm
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.
3) 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.
Recommended --
rules
External The default value depends on the BCCH frequency band:
comment Default value for P-GSM/G1: 43 dBm
Default value for GSM850: 39 dBm
Default value for DCS1800: 30 dBm
Default value for DCS1900: 30 dBm
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.
3) 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.
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai GPRS Min value 0 Coded Min 0
n Max value 2 Coded Max 2
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 2
Def value 0 Coded Def 0
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
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 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
- it is an optional feature (TRX quantity controlled)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Recommended --
rules
External --
comment
Internal comment Used by RRM (for Gb interface protection)
Recommended --
rules
External --
comment
Internal comment Used by RRM (for Gb interface protection)
Recommended --
rules
External --
comment
Internal comment Used by RRM (for Gb interface protection) and BSCGP (for BSCGP interface protection)
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)
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 Min = h’F800, Max = h’FC00
changeable from the local operator terminal (IMT)
Recommended --
rules
External Calculated by the MFS from the GPU_Gb_Base_IP value.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External equal to GPU_Gb_base_UDP.
comment
Internal comment Min = h’F800, Max = h’FC00
The same port is used on all the GPU boards
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
comment - Applicable only to TDM mode.
Internal comment 0: B11 behaviour
1: new behaviour
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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 --
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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 --
Mandatory rules --
Recommended --
rules
External Applicable to GP2 board.
comment Parameter change: No impact on the telecom service, on going traffic is not disrupted.
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP3 board.
comment Parameter change: No impact on the telecom service, on going traffic is not disrupted.
Internal comment --
Recommended
rules
External --
comment
Internal comment --
Recommended
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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).
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)
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).
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 --
Recommended --
rules
External Calculated by the PCU from IPGCH_Base_Address_MFS
comment
Internal comment --
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
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_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
shaping would be less efficient.
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.
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.
Recommended --
rules
External --
comment
Internal comment --
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”.
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
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).
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment - Configured via PMU-PTU interface.
Recommended --
rules
External --
comment
Internal comment --
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.
Recommended --
rules
External --
comment
Internal comment --
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.
Recommended --
rules
External --
comment
Internal comment - Configured via PMU-PTU interface.
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Configured via PMU-PTU interface.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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).
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 = h’D000, Max = h’D0FF. 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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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).
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
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).
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)
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)
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=h’CD90, Max=h’CD91
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
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 --
Mandatory rules LAC and CI can not be equal to 65535 at the same time
Equal to LAC (BSC)
A couple of mate extended cells (Extended inner + extended outer) shall have the same LAC
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
Mandatory rules LAC and CI can not be equal to 65535 at the same time.
Equal to LAC(n)(BSC)
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment --
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.
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.
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.
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 --
Category System (CST) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai GPRS Min value 1 Coded Min 1
n Max value 50 Coded Max 50
Spec ref. GPRS MFS-BSC interface - BSCGP layer Coded Max 50
Def value 10 Coded Def 10
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 --
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 --
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 --
Mandatory rules --
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment 500 corresponds to the maximum number of cells per BSS.
Mandatory rules --
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment 500 corresponds to the maximum number of cells per BSS
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution only
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.
Internal comment - Feature specific for CMCC
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_LONG_TBF_WEIGHT is enabled.
- Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied to the TBF established after modification.
Internal comment - Feature specific for CMCC
- 45 = Maximum_Weight (> max(Weight_Px = 15)
- def = 15 > 4 (=def of Weight_P12 and def of BEST_EFFORT_PRIORITY = 12)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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.
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment --
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP2 board
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP3 board
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP2 board
comment
Internal comment 2880 in UL + 2880 in DL = 5760.
Mandatory rules --
Recommended --
rules
External Applicable to GP3 board
comment
Internal comment 11520 in UL + 11520 in DL = 23040.
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment --
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).
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 --
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.
External - Applicable only to TDM mode.
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
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 --
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.
External - Applicable only to TDM mode.
comment - If MAX_EGPRS_MCS_SHORT_DATA_UL 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
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 --
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment Applicable to GP2 and GP3 boards
Internal comment This parameter corresponds to a constant hard-coded in the MFS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - applicable to stand alone configuration
- Def value = Max value = 9 is applicable to rack shared configuration
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.
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.
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.
External - Applicable only to TDM mode.
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.
- 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 --
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.
External - Applicable only to TDM mode.
comment - If MAX_GPRS_CS_SHORT_DATA_UL is strictly higher than MAX_GPRS_CS, then MAX_GPRS_CS 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
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment
Internal comment Needed for MPDCH feature.
This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Needed for MPDCH feature.
- This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
comment
Internal comment --
Mandatory rules --
If EN_VGCS= enabled, then “(MAX_VGCS_TS + MAX_PDCH) < Total number of TCHs of the cell”
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
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 <= 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
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 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.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 1586
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment m
To support LCS in a cell, it is mandatory to have Max_PDCH > 0
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
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.
Recommended --
rules
External 127 is a theoretical value: 16 TRX * 8 PDCH - BCCH.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable only to TDM mode.
comment Applicable to GP2 board
Internal comment This parameter corresponds to a constant hard-coded in the MFS
Mandatory rules --
Recommended --
rules
External Applicable only to TDM mode.
comment Applicable to GP3 board
Internal comment This parameter corresponds to a constant hard-coded in the MFS
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
Mandatory rules --
Recommended --
rules
External Applicable to GP2 board
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP3 board
comment
Internal comment --
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.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Mandatory rules --
Recommended - MAX_POW_RED_USF_8PSK <= MAX_POW_RED_DYN for a better decoding of the USF by the MS.
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled and MAX_POW_RED_DYN <> 0.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Internal comment --
Mandatory rules --
Recommended - MAX_POW_RED_USF_GMSK <= MAX_POW_RED_DYN for a better decoding of the USF by the MS.
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled and MAX_POW_RED_DYN <> 0.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Used to evaluate the MS DRX mode
comment
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai LCS Min value 0.5 Coded Min 10
n Max value 1 Coded Max 20
Spec ref. LCS Functional Specification Coded Max 20
Def value 0.6 Coded Def 12
Coding rules step size = 0.05
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External The bigger this parameter is, the lesser the MS power consumption is.
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The first Paging request sending is counted in the parameter value.
0 means no Paging Request.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External Applicable only to TDM mode.
comment Applicable to GP2 board
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External Applicable only to TDM mode.
comment Applicable to GP3 board
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PTU SW.
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).
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU SW
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU SW.
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.
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 G4 BTS.
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 G5 BTS.
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment Applicable to GP2 board
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.
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment Applicable to GP3 board
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.
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 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.
Mandatory rules --
Recommended --
rules
External Applicable to GP2 and GP3 boards
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).
Mandatory rules --
Recommended --
rules
External Applicable to GP2 and GP3 boards
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).
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
comment Applicable to GP2 and GP3 boards
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW.
Recommended --
rules
External Applicable to GP2 and GP3 boards
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
Recommended --
rules
External --
comment
Internal comment - This parameter corresponds to a constant hard-coded in the PMU, PTU and SCP SW.
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)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This constant is hardcoded in MAC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This constant is hardcoded in MAC
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 a MCC of the own PLMN set.
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- 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 (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 --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution only
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.
Internal comment - Feature specific for CMCC
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 MCS_AVG_PERIOD_DEF_VALUE (MCS_AVG_PERIOD is assumed rarely modified on the fields)
Recommended --
rules
External --
comment
Internal comment this parameter is hard-coded in the BTS.
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.
External 127 is a theoretical value : 16 TRX * 8 PDCH - BCCH.
comment
Internal comment - The MPDCHs (primary and secondary) are also taken into account in this parameter.
- This parameter is available in the G2 BSC through the BSCGP interface
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai LCS Min value 0.5 Coded Min 10
n Max value 1 Coded Max 20
Spec ref. LCS Functional Specification Coded Max 20
Def value 0.85 Coded Def 17
Coding rules step size = 0.05
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This constant is hardcoded in MAC
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- MNC (BSC) = MNC (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 configuration. The default value indicated here is for implementation purposes.
comment The operator is allowed to enter 2 or 3 digits MNC.
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.
Mandatory rules The OMC-R shall ensure that the following rules are always fulfilled:
- MNC(n) (BSC) = MNC(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 (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 --
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.
Recommended --
rules
External --
comment
Internal comment --
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 --
Recommended --
rules
External The default value depends on the BCCH frequency band:
comment Default value for P-GSM/G1: 43 dBm
Default value for GSM850: 39 dBm
Default value for DCS1800: 30 dBm
Default value for DCS1900: 30 dBm
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.
3) 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.
Recommended --
rules
External The default value depends on the BCCH frequency band:
comment Default value for P-GSM/G1: 43 dBm
Default value for GSM850: 39 dBm
Default value for DCS1800: 30 dBm
Default value for DCS1900: 30 dBm
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.
3) 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.
Recommended --
rules
External Default value depends on MSC type
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).
Recommended --
rules
External The different choices are:
comment - 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.
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. None Domai E-GPRS Min value 0 Coded Min 0
n Max value 10 Coded Max 10
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 10
Def value 2 Coded Def 2
Coding rules --
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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
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.
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 --
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 --
Mandatory rules --
- 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 --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Category System (CST) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai GPRS Min value 1 Coded Min 1
n Max value 500 Coded Max 500
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 500
Def value 20 Coded Def 20
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).
Category System (CST) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai GPRS Min value 1 Coded Min 1
n Max value 500 Coded Max 500
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 500
Def value 5 Coded Def 5
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).
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Category Site (CAE) OMC-R access Changeable Type Threshold Unit None
Rec ref. None Domai GPRS Min value 1 Coded Min 1
n Max value 256 Coded Max 256
Spec ref. GPRS radio interface - RLC sublayer Coded Max 256
Def value 10 Coded Def 10
Coding rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory 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).
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
External --
comment
Internal comment --
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 --
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.
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.
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment is linked to the maximum number of HDLC formatters per GPU
Applicable to GPU and GP2 and GP3 boards
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
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.
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.
3)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.
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.
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 --
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 --
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 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 --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter shall also be valid for external cells.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter shall also be valid for external cells.
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”.
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
Mandatory rules --
Recommended --
rules
External This parameter applies to the serving cell.
comment
Internal comment --
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.
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 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 --
Category Site (CAE) OMC-R access Changeable Type Number Unit None
Rec ref. GSM TS 04.60 Domai GPRS Min value 0 Coded Min 0
n Max value 1 Coded Max 1
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 1
Def value 0 Coded Def 0
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
comment
Internal comment Needed for MPDCH feature
Recommended --
rules
External Default value depends on configuration. The value indicated here is for implementation purposes.
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.
Internal comment Needed for MPDCH feature
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
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 --
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 --
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.
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 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.
Mandatory rules CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
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.
Category Site (CAE) OMC-R access Changeable Type List of numbers Unit None
Rec ref. 3GPP TS 23.236 Domai IP Min value 0 Coded Min 0
n Max value 1024 Coded Max 1024
Spec ref. xxxx Coded Max 1024
Def value None Coded Def 1024
Coding rules coded on 2 bytes
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.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
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).
Mandatory rules --
Recommended --
rules
External significant only if EN_GB_FLEX = disabled or not supported,
comment (else MAX_NB_SGSN (BOP))
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment SGSN IP endpoints are used for Gb over IP interface.
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Recommended The operator must control that the NULL_NRI_PS is common inside all the BSSs of one PLMN
rules
External Significant only if EN_GB_FLEX is enabled
comment
Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Internal comment - According to TS23.236, there is one unique null NRI in a PLMN.
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution
comment - Significant if EN_OPTIM_TBF_ALLOC_FOR_IM is enabled
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Applicable to GPU and GP2 and GP3 boards
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_RTS_ALLOC_ON_PACKET_SIZE is enabled
Internal comment --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_RTS_ALLOC_ON_PACKET_SIZE is enabled
Internal comment --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_RTS_ALLOC_ON_PACKET_SIZE is enabled
Internal comment --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_RTS_ALLOC_ON_PACKET_SIZE is enabled
Internal comment --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_RTS_ALLOC_ON_PACKET_SIZE is enabled
Internal comment --
Recommended --
rules
External - Function available on MFS Evolution only
comment - Significant if EN_RTS_ALLOC_ON_PACKET_SIZE is enabled
Internal comment --
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection.
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile station shall perform an abnormal release with cell re-selection
Recommended --
rules
External --
comment
Internal comment When N3102<=0 is reached, the mobile staion shall perform an abnormal release with cell re-selection
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH.
Recommended --
rules
External --
comment
Internal comment --
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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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 --
Recommended --
rules
External --
comment
Internal comment --
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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External PD_DL_TBF_VOLUME_THR_9 < PD_DL_TBF_VOLUME_THR_10
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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).
Mandatory rules --
Recommended --
rules
External PD_UL_TBF_VOLUME_THR_9 < PD_UL_TBF_VOLUME_THR_10
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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).
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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).
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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).
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 --
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
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 --
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 --
Recommended --
rules
External --
comment
Internal comment Cannot be understood by GSM Phase 1 MS. CT: Depends on Cell Type and BTS Type
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
Recommended --
rules
External --
comment
Internal comment Meaningless parameter if the Radio Priority 2 is not allowed Value 16 indicates that access is forbidden.
Needed for MPDCH feature
Recommended --
rules
External --
comment
Internal comment Meaningless parameter if the Radio Priority 3 is not allowed Value 16 indicates that access is forbidden.
Needed for MPDCH feature
Recommended --
rules
External --
comment
Internal comment Meaningless parameter if the Radio Priority 4 is not allowed Value 16 indicates that access is forbidden.
Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 = “GSM850” or “DCS1900” if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1900 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 --
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
Mandatory rules --
Recommended --
rules
External Applicable to GP2 board
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable to GP3 board
comment
Internal comment --
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Internal comment --
Mandatory rules --
Internal comment --
Recommended - Alcatel-Lucent recommends POW_RED_P0 <= POW_RED_P0_PDDCB for a better efficiency of the power control.
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Recommended - Alcatel-Lucent recommends POW_RED_P0 <= POW_RED_P0_PDDCB for a better efficiency of the power control.
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Internal comment - POWER_RED_P0 is applicable to the other PDDCB that are used for MS synchronisation.
Mandatory rules --
Recommended --
rules
External Parameter used in dynamic allocation of secondary MasterPDCH algorithm.
comment
Internal comment --
Mandatory rules --
Recommended The same GPS methods reference should not be used for different priorities
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended The same GPS methods reference should not be used for different priorities.
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended The same GPS methods reference should not be used for different priorities.
rules
External --
comment
Internal comment --
Recommended --
rules
External Persistence level parameter for priority (i) is meaningless if the Radio Priority (i) is not allowed
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution or LRC only
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
Internal comment - Feature specific for CMCC
- max TBF multiplexing is defined by MAX_UL_TBF_SPDCH and MAX_DL_TBF_SPDCH.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment The parameter is not persisted in the OMC-R. The value of this parameter is set by the MFS and is required by OMC-R each time the operator triggers its displaying..
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
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 --
Category Site (CAE) OMC-R access Changeable Type Number Unit dBm
Rec ref. 3GPP TS 05.08 Domai 2G-3G Min value -98 Coded Min 0
n Max value -50 Coded Max 15
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 15
Def value -50 Coded Def 15
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 --
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 in GPRS packet transfer mode.
This parameter is sent in Packet Measurement Order on PACCH.
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”).
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 --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External The value depends on configuration. The default value indicated here is for implementation purposes.
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Hardcoded in RRM
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Category Network (CDE) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai IP Min value 0 Coded Min 0
n Max value 30 Coded Max 30
Spec ref. GPRS radio interface - RLC sublayer Coded Max 30
Def value 4 Coded Def 4
Coding rules Step size = 1, coded on 1 byte.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS via IPGCH.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Sent to the BTS.
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)).
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
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 --
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.
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.
Recommended --
rules
External --
comment
Internal comment This parameter is used by MFS in the defensive mechanism for radio resource management to increment internal variables.
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 MS’s 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.
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
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
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
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Category Network (CDE) OMC-R access None (DLS) Type Number Unit None
Rec ref. None Domai GPRS Min value 1 Coded Min 1
n Max value 10 Coded Max 10
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 10
Def value 2 Coded Def 2
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 --
Recommended --
rules
External - Significant only if EN_INSTANT_MSG_SERVICE is enabled
comment
Internal comment - 3GPP reserved value, provided by CMCC
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
Recommended --
rules
External --
comment
Internal comment --
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
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
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
comment - Parameter change: no impact on the telecom service, on going traffic is not disrupted. Change applied immediately after modification.
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
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 - 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)
Mandatory rules --
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 - 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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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).
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.
Mandatory rules --
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Gives the delay between 2 GCH establishment attempts.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Let’s 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
Ex2 : Max_retrans_DL = 3
A=(3+1)*1.4=5.6sec, then T_DELAY_PAGING_EXT >= 0+2.5>=4.1
Ex3 : Max_retrans_DL = 4
A=(4+1)*1.4=7.0sec, then T_DELAY_PAGING_EXT >= (5-1.4)+2.5>=7.1
Ex3 : Max_retrans_DL = 5
A=(5+1)*1.4=8.4sec, then T_DELAY_PAGING_EXT >= (5-2.8)+2.5>=4.7
The default value 5.5 sec is an average value.
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External Applicable only to TDM transport.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
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!!!
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment ONLY used in the construction of other timers.
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"
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.
Mandatory rules --
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.
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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
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_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
shaping would be less efficient.
- 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
Internal comment - The coded value is sent by the MFS to the BTS via 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 --
comment
Internal comment --
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 --
rules
External The timer is meaningful in the MFS when EN_LCS=1.
comment
Internal comment --
Recommended --
rules
External The timer is meaningful in the MFS when EN_LCS=1.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 - 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.
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.
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter corresponds to a constant hard-coded in the PTU SW.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment All DL PDU’s 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.
Recommended --
rules
External --
comment
Internal comment The MS context is kept during max(DRX_TIMER_MAX, T_MS_Context_Lifetime)
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External -
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
Recommended - When the concerned timers are strictly positive, Alcatel-Lucent recommends T_NETWORK_RESPONSE_TIME_CONG_IM <=
T_NETWORK_RESPONSE_TIME_CONG
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 TBF established after modification.
Internal comment - Feature specific for CMCC
Recommended - When the concerned timers are strictly positive, Alcatel-Lucent recommends T_NETWORK_RESPONSE_TIME_CONG_IM <= T_NETWORK_RESPONSE_TIME_IM.
rules
External - Function available on MFS Evolution or LRC only
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
Internal comment - Feature specific for CMCC
- it is an optional feature (TRX quantity controlled)
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
External - Function available on MFS Evolution only
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 TBF established after modification.
Internal comment - Feature specific for CMCC
Mandatory rules --
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 - 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
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Let’s 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
Ex2 : Max_retrans_DL = 3
A=(3+1)*1.4=5.6sec, then T_DELAY_PAGING_EXT >= 0+2.5>=4.1
Ex3 : Max_retrans_DL = 4
A=(4+1)*1.4=7.0sec, then T_DELAY_PAGING_EXT >= (5-1.4)+2.5>=7.1
Ex3 : Max_retrans_DL = 5
A=(5+1)*1.4=8.4sec, then T_DELAY_PAGING_EXT >= (5-2.8)+2.5>=4.7
The default value 5.5 sec is an average value.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Recommended --
rules
External --
comment
Internal comment --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Needed for MPDCH feature.
MSs only apply this timer if another cell is available.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External The timer is meaningful in the MFS when EN_LCS=1.
comment
Internal comment --
Recommended --
rules
External The timer is meaningful in the MFS when EN_LCS=1.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External The timer is meaningful in the MFS when EN_SAGI=1.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Reseting condition:
Receipt of a RLC/MAC control block.
Action on expiry;
Release of a TBF
Category System (CST) OMC-R access None (DLS) Type Timer Unit sec
Rec ref. None Domai GPRS Min value 1.5 Coded Min 15
n Max value 10 Coded Max 100
Spec ref. GPRS radio interface - RLC sublayer Coded Max 100
Def value 3 Coded Def 30
Coding rules step size=0.1 sec
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"
Mandatory rules --
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.
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/True/CCCH combined/1/2000/2500/
Disabled/True/CCCH combined/2/1000/1600/
Edition : 13 Released The T_ul_assign_ccch parameter is not displayed to the O&M user. BSS Telecom
parametersGSM/SYS/DD/037396 Page 1991
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.
Category Site (CAE) OMC-R access Changeable Type Timer Unit sec
Rec ref. None Domai GPRS Min value 0.1 Coded Min 1
n Max value 0.7 Coded Max 7
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 7
Def value 0.4 Coded Def 4
Coding rules step size = 0.1 sec
Mandatory rules --
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 - 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
Internal comment Needed when there is a PBCCH in the cell.
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.
Mandatory rules --
Recommended --
rules
External Used only when EN_UL_CONGESTION is enabled
comment
Internal comment --
Category System (CST) OMC-R access None (DLS) Type Timer Unit ms
Rec ref. None Domai GPRS Min value 0 Coded Min 0
n Max value 300 Coded Max 6
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 6
Def value 0 Coded Def 0
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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.
Mandatory rules --
Recommended --
rules
External -
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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,
- 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.
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 2004
Logical T3169 m B11 Yes B12 Yes
name TRX nb No
HMI T3169 Sub-syste MFS template Cell Type No
name Instance MFS RMS 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.
Category System (CST) OMC-R access None (DLS) Type Timer Unit sec
Rec ref. GSM TS 04.60 Domai GPRS Min value 0 Coded Min 0
n Max value 15 Coded Max 15
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PCC) Coded Max 15
Def value 5 Coded Def 5
Coding rules step size=1sec
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
==> Case GPRS traffic is carried either through Abis satellite links or Ater satellite links in the serving cell:
i) T3192 = 1500 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 = 1000 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
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.
Mandatory rules --
Recommended --
rules
External This timer corresponds to T3208 on MS side. T3208n = T3208 - RTD = 960 ms - 160 ms
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment Needed for feature MPDCH
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled and MAX_POW_RED_DYN <> 0.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Internal comment --
Recommended --
rules
External - Function available on MFS Evolution
comment - Significant if EN_BS_PC_PS is enabled and MAX_POW_RED_DYN <> 0.
- Parameter change: no impact on the telecom service, on going TBFs are not disrupted. Change applied to the new downlink TBF established after modification.
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment This parameter replaces TBF_CS_PERIOD1.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
External --
comment
Internal comment --
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.
External The parameter is significant only if EN_EGPRS is enabled
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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 --
Mandatory rules --
Recommended --
rules
External - Applicable only to TDM mode.
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 --
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 --
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.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
External Exception cases apply for uplink TBF establishment on PACCH when link adaptation is enabled.
comment
Internal comment --
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.
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 --
Mandatory rules --
It is recommended to set this parameter as follows depending whether or not GPRS traffic is carried through Abis or Ater satellite links:
- 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.
comment - Applicable only to TDM mode.
Internal comment --
Mandatory rules --
Mandatory rules --
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
Mandatory rules --
Recommended --
rules
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Tdsl.
comment - Applicable only to TDM mode.
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.
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 - 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.
comment - Applicable only to TDM mode.
Internal comment --
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 --
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 --
Category System (CST) OMC-R access None (DLS) Type Threshold Unit mn
Rec ref. None Domai GPRS Min value 20 Coded Min 2
n Max value 600 Coded Max 60
Spec ref. FBS GPRS - Radio interface - RRM sublayer (PRH) Coded Max 60
Def value 180 Coded Def 18
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 --
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
External Applicable only to TDM mode.
comment
Internal comment --
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
External Applicable only to TDM mode.
comment
Internal comment --
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
External - Applicable only to TDM mode.
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.
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
External Applicable only to IP transport.
comment
Internal comment --
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
External - Applicable only to TDM mode.
comment
Internal comment --
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
External Applicable only to IP transport.
comment
Internal comment --
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
External Applicable only to TDM transport.
comment
Internal comment --
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
External Applicable only to TDM transport.
comment
Internal comment --
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
External Applicable only to IP transport
comment
Internal comment --
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
External Applicable only to IP transport
comment
Internal comment --
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
External Applicable only to IP transport.
comment
Internal comment --
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
External Applicable only to IP transport.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External In the standard, this parameter is the same with TDM or IP sub-network.
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 - 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.
comment - Applicable only to TDM mode.
Internal comment --
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External - HMI name changed to precise that this timer is valid for GCH channels. Former HMI name Tusl.
comment - Applicable only to TDM mode.
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended It is recommended to set TX_INT so that the corresponding spreading time is about 240 ms.
rules
External --
comment
Internal comment Needed when there is a PBCCH in the cell.
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 MS’s 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:
Note:
Edition : 13 Released BSS Telecom parameters GSM/SYS/DD/037396 Page 2072
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.
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 --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules CIR <= NIR <= CIR x (1 + EBS/CBS) <= ACCESS_RATE_BC (OMC)
Recommended --
rules
External - applicable to Gb over FR only
comment
Internal comment This parameter is computed by the OMC, using the same formula as the MFS.
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
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
Recommended --
rules
External The minimum, maximum and default values indicated are only for implementation purposes.
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
Category Site (CAE) OMC-R access Changeable Type Abstract Unit None
Rec ref. None Domai GSM Min value * Coded Min
n Max value * Coded Max
Spec ref. Handover preparation Coded Max
Def value # Coded Def
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”.
A couple of mate cells (Extended inner + extended outer) shall have the same LAC (respectively RAC when they are PS capable).
- 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.
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.
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
Recommended --
rules
External --
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
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 TBF established after modification.
Internal comment - Feature specific for CMCC.
The relation with EN_LONG_TBF_WEIGHT(MFS) is:
-if (the aim BSC does support simplified SPD) AND (the aim MFS does NOT support the full SPD) then EN_LONG_TBF_WEIGHT(MFS) is computed based on the table
currently provided in the external comment of EN_LONG_TBF_WEIGHT(MFS).
- elseif (the aim MFS does support the full SPD) then EN_LONG_TBF_WEIGHT(MFS) is set on the same values as EN_LONG_TBF_WEIGHT(OMC).
Conversely, during the cell view opening, EN_LONG_TBF_WEIGHT(OMC) is valued according to the rule:
-if (the aim BSC does support simplified SPD) AND (the aim MFS does NOT support the full SPD) then EN_LONG_TBF_WEIGHT(OMC) is computed based on the table
currently provided in the external comment of EN_LONG_TBF_WEIGHT(MFS).
- elseif (the aim MFS does support the full SPD) then EN_LONG_TBF_WEIGHT(OMC) is set on the same values as EN_LONG_TBF_WEIGHT(MFS).
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 TBF established after modification
Internal comment - Feature specific for CMCC.
The relation with EN_RTS_ALLOC_ON_PACKET_SIZE(MFS) is:
- if (the aim BSC does support simplified SPD) AND (the aim MFS does NOT support the full SPD) then EN_RTS_ALLOC_ON_PACKET_SIZE(MFS) is computed based
on the table currently provided in the external comment of EN_LONG_TBF_WEIGHT(MFS).
- elseif (the aim MFS does support the full SPD) then EN_RTS_ALLOC_ON_PACKET_SIZE(MFS) is set on the same values as
EN_RTS_ALLOC_ON_PACKET_SIZE(OMC).
Conversely, during the cell view opening, EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) is valued according to the rule:
-if (the aim BSC does support simplified SPD) AND (the aim MFS does NOT support the full SPD) then EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) is computed based
on
the table currently provided in the external comment of EN_LONG_TBF_WEIGHT(MFS).
- elseif (the aim MFS does support the full SPD) then EN_RTS_ALLOC_ON_PACKET_SIZE(OMC) is set on the same values as
EN_RTS_ALLOC_ON_PACKET_SIZE(MFS).
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 = “GSM850” or “DCS1900” if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1900 bands",
- FREQUENCY_RANGE = “PGSM (GSM900)” or “EGSM (GSM900)” or “DCS1900” if the PLMN_FREQUENCY_BANDS is set to "GSM900 and DCS1900 bands".
Recommended --
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.
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 = h’D500, Max = h’D517
- 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.
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 = h’CD00, Max = h’CD2E
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - Min = h’CD70, Max = h’CD87.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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.
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.
Recommended --
rules
External --
comment
Internal comment - Used to communicate with OMC.
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment Coded in the software
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment - hardcoded in TC-IF
Recommended --
rules
External Meaningful in both A user plane over TDM or IP.
comment
Internal comment --
Recommended --
rules
External --
comment
Internal comment --
Mandatory rules --
Recommended --
rules
External --
comment
Internal comment --
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 [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 [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 [2] -30 -30 -30 -30 -30 -30 -30 -30 -30 -30 -30 -30 -30 -30 -30 -10
MEAS_STAT_PATH_BAL_i [3] -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -6
MEAS_STAT_PATH_BAL_i [4] -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -3
MEAS_STAT_PATH_BAL_i [5] 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MEAS_STAT_PATH_BAL_i [6] 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 3
MEAS_STAT_PATH_BAL_i [7] 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 6
MEAS_STAT_PATH_BAL_i [8] 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 10
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_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
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
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
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_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
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) *
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)*
*
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)
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
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
N_BSTXPWR_M 13 13 13 13 15 13 15 13 13 13 15 15
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)
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)
INTAVE BSC INTERNAL TARGET PDCH GP2 MFS INTERNAL TARGET PDCH GP3 MFS
M_PEND_A (BTS) BTS M_PEND_A (G2 BSC) BSC M_PEND_A (MX BSC) BSC
MAX_PDCH (MFS) MFS MAX_PDCH (MX BSC) BSC MAX_PDCH_HIGH_LOAD (G2 BSC) BSC
MSCR (G2 BSC) BSC MSCR (MFS) MFS MSCR (MX BSC) BSC
RLC_FC1_BUFFER_SEND_THRES MFS
T(sst) (G2 BSC) BSC T(sst) (MX BSC) BSC T_ACK_WAIT MFS
End of document