0134 14delta

BSS Telecom Parameters
Delta between edition 14 released and edition 13 released
Sub-System
BSC MFS OMC
nb of modified parameters
11 27 1
Delta for the BSS Telecom Parameters Catalogue
Sub-system:
Logical name HMI name
BSC
B10 Oui B9
Oui
BCCH_FREQUENCY
BCCH_FREQUENCY
Definition Indicates the frequency used as BCCH. Sub-system BSC Category Site (CAE) Instance cell OMC-R access Virtual changeable Type Number Min value 0 Coded Min 0 Unit None Max value 1023 Coded Max 1023 Application domain GSM Def value None Coded Def Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Handover Preparation ---- 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. --
Rec reference
None
Modif date Modif description

04/03/2008 Ed14 rlsd: mandatory rule removed, CR 226280
Page 2 of 33
BCCH_FREQUENCY(n)
BCCH_ARFCN
B10 Oui
B9
Oui
Definition Indicates the frequency used as BCCH. Sub-system BSC Category Site (CAE) Instance cell OMC-R access Changeable Type Number Min value 0 Unit None Max value 1023 Application domain GSM Def value None Spec reference Coding rules Mandatory rules
Handover Preparation --
Coded Min 0 Coded Max 1023 Coded Def Rec reference

None
- BCCH_FREQUENCY(n) = BCCH_ARFCN(n) 1) for Non Evolium serving cell : The cell neighborhood for reselection is controlled by EN_2G_TO_3G_CELL_RESELECTION value and FDD_ARFCN_LIST content. The cell neighborhood for handover is controlled by EN_3G_HO and FDD_ARFCN values. - if the neighborhood of the serving cell for reselection is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. - if the neighborhood of the serving cell for reselection is mixed 2G/3G, and if all 2G frequencies can be encoded in the SI2 or SI2bis message, and if the SI2ter message is used to encode only 3G frequencies, then there shall be no more than 31 different BCCH 2G frequencies for the set of all the target cells. - since the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells 2) For Evolium serving cell : The cell neighborhood for reselection is controlled by EN_2G_TO_3G_CELL_RESELECTION value and FDD_ARFCN_LIST content. The cell neighborhood for handover is controlled by EN_3G_HO and FDD_ARFCN values. - if the neighborhood of the serving cell for reselection is 2G only, or mixed 2G/3G, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. - if the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. -- 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. - in case of Non Evolium serving cell, if neighborhood for reselection is mixed 2G/3G then no more than 31 frequencies (the OMC cannot performed the described mandatory --
Recommended rules Internal Comment
External Comment

05/03/2008 04/03/2008 Ed14 rlsd: new mandatory rules : CR 227496v3 Ed14 rlsd: one mandatory rule removed: CR 226280
Page 3 of 33
DL_DTX_AMR_WB_GMSK
DL_DTX_AMR_WB_GMSK
B10 Oui
B9
Non
Definition This flag enables / disables the use of downlink DTX for AMR-WB GMSK speech calls. Sub-system BSC Category Site (CAE) Instance BSC OMC-R access Changeable Type Flag Min value 0 Coded Min 0 Unit None Max value 1 Coded Max 1 Application domain GSM Def value 0 Coded Def 0 Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
DTX functional specification 0 : DL DTX for AMR-WB GMSK disabled, 1 : DL DTX for AMR-WB GMSK enabled -The value 1 is recommended when EN_TFO_AMR_WB =1 B10 MR2 parameter. This parameter is used to set the value of the DTX field in cell Options IE in SYSTEM INFORMATION TYPE 6 in some cases. --
Rec reference
None

09/01/2008 Ed13: instance is BSC: correct the FR 229412 (CR 211031 was not taken completely)
Page 4 of 33
Logical name HMI name Definition
DUMMY_ARFCN_FOR_SI2TER
DUMMY_ARFCN_FOR_SI2TER
B10 Oui
B9
Oui
Dummy ARFCN used to describe one dummy 2G frequency in the SI2ter message when there is no additional 2G frequency to encode in the Extended BCCH Frequency List IE of the SI2ter message and the SI2ter message has to be present to describe 3G frequencies.
Sub-system BSC Instance BSC Type Number Unit None Application domain GSM Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Category System (CST) OMC-R access None (DLS) Min value 0 Max value 1023 Def value 252
Coded Min 0 Coded Max 1023 Coded Def 252 Rec reference
None
System information management ----
In case of Non Evolium serving cell, if neighborhood for reselection is mixed 2G/3G then no more than 31 frequencies (the OMC cannot performed the described mandatory check, but still present to give the really concerned case). For a Non Evolium serving cell, if its neighborhood for reselection is mixed 2G/3G, and if all 2G frequencies can be encoded in the SI2 or SI2bis message, and if the SI2ter message is used to encode only 3G frequencies, then there shall be no more than 31 different BCCH 2G frequencies for the set of all the target cells. Since the total number of ARFCNs described in the BA list shall not exceed 32 in the serving cell, the total number of useful ARFCN (excluding the dummy ARFCN) is limited to 32 1 = 31 (1 stands for the dummy ARFCN)

05/03/2008 Ed14rlsd: int and ext comments changed: CR 227496v3
Page 5 of 33
EGSM_RR_ALLOC_STRATEGY
EGSM_RR_ALLOC_STRATEGY
B10 Oui
B9
Oui
Definition Defines if the G1 non-capable MS is supported or not in the network. Sub-system BSC Category Network (CDE) Instance BSS OMC-R access Displayed Type Number Min value 0 Coded Min 0 Unit None Max value 1 Coded Max 1 Application domain GSM Def value 0 Coded Def 0 Spec reference Coding rules
Resource allocation and management
Rec reference
None
Mandatory rules
0: G1 non-capable MS-s are only supported in the cells where the BCCH is not configured on the G1 band (i.e. BCCH is configured on PGSM band or on DCS1800 band) . 1: G1 non-capable MS-s are not supported in any cell that contains at least one G1 TRX When EGSM_RR_ALLOC_STRATEGY is set to 0, if the BCCH is not configured on the G1 band (i.e. BCCH is configured on PGSM band or on DCS1800 band), then: 1) the OMC-R does not allow the operator to define the CCCH, SDCCH and CBCH on a G1 TRX. 2) TRX_PREF_MARK must be <> 0 for a hopping G1 TRX . ----
Recommended rules Internal Comment External Comment

04/03/2008 Ed14 rlsd: CR 226280
Page 6 of 33
EN_2G_TO_3G_CELL_RESELECTION
EN_2G_TO_3G_CELL_RESELECTION
B10 Oui
B9
Oui
Sub-system Instance cell Type Number Unit None Application domain 2G-3G Spec reference Coding rules
Enables/Disables the GSM to UTRAN FDD cell reselections and defines the 3G search activation mode for MS in GMM Ready state. BSC Category Site (CAE)
OMC-R access Changeable Min value 0 Max value 3 Def value 0

None
System information management
Mandatory rules
0: Disabled 1: Enabled with 3G search activated while the UE/MS is in GMM ready state, 2: Enabled with 3G search deactivated while the UE/MS is in GMM ready state. 3: Enabled with 3G search activated while the UE/MS is in GMM ready state, even if Network_Control_Order > 1 if EN_2G_TO_3G_CELL_RESELECTION <> 0 and if EN_2G_TO_3GTDD_CELL_RESELECTION <> 0, then EN_2G_TO_3G_CELL_RESELECTION = EN_2G_TO_3GTDD_CELL_RESELECTION 1) for Non Evolium serving cell : The cell neighborhood for reselection is controlled by EN_2G_TO_3G_CELL_RESELECTION value and FDD_ARFCN_LIST content. - if the neighborhood of the serving cell for reselection is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. - if the neighborhood of the serving cell for reselection is mixed 2G/3G, and if all 2G frequencies can be encoded in the SI2 or SI2bis message, and if the SI2ter message is used to encode only 3G frequencies, then there shall be no more than 31 different BCCH 2G frequencies for the set of all the target cells. 2) For Evolium serving cell : The cell neighborhood for reselection is controlled by EN_2G_TO_3G_CELL_RESELECTION value and FDD_ARFCN_LIST content. - if the neighborhood of the serving cell for reselection is 2G only, or mixed 2G/3G, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells.
Recommended rules
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 frequencies within the same band. Value 3 should be used only in case of good 3G FDD coverage. 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. This parameter is available in the MFS through the BSCGP interface. - in case of Non Evolium serving cell, if neighborhood for reselection is mixed 2G/3G then no more than 31 frequencies (the OMC cannot performed the described mandatory check, but still present to give the really concerned case)
Internal Comment
External Comment
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 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]

05/03/2008 05/03/2008 Ed14 rlsd: ext comment changed: CR 233377 Ed14 rlsd: new mandatory rule: CR 227496v3
Page 7 of 33
EN_3G_HO
EN_3G_HO
B10 Oui
B9
Oui
Definition This flag enables/disables the 2G-3G handover Sub-system BSC Category Site (CAE) Instance cell OMC-R access Changeable Type Flag Min value 0 Unit None Max value 1 Application domain 2G-3G Def value 0 Spec reference Coding rules Mandatory rules
Handover Preparation 0: disabled, 1: enabled

None
1) For Non Evolium serving cell: The cell neighborhood for handover is controlled by EN_3G_HO and FDD_ARFCN values. - since the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells 2) For Evolium serving cell : The cell neighborhood for handover is controlled by EN_3G_HO and FDD_ARFCN values. - if the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. --2G-3G Handover will be disabled by the BSS in cells mapped to non Evolium BTSs

05/03/2008 Ed14 rlsd: new mandatory rule: CR 227496v3
Page 8 of 33
EN_TFO_MATCH
EN_TFO_MATCH
B10 Oui
B9
Oui
Sub-system Instance cell Type Flag Unit None Application domain Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
This flag enables/disables TFO codec mismatch resolution function (for FR, EFR, AMR-WB and HR codecs). BSC Category Site (CAE)
GSM

None
TFO Functional specification 0: disabled; 1: enabled
may be set to 1 only if EN_TFO=1or if EN_TFO_AMR_WB=1 May be set to 0 only if EN_TFO_OPT = 0 ----

07/03/2008 Ed14 rlsd: CR 211031v4 was not taken completely in previous edition
Page 9 of 33
FREQUENCY_RANGE
FREQUENCY_RANGE
B10 Oui
B9
Oui
Definition This parameter indicates the frequency range of the cell. Sub-system BSC Category Site (CAE) Instance cell OMC-R access Changeable Type Number Min value 0 Unit None Max value 6 Application domain GSM Def value 0 Spec reference Coding rules Mandatory rules
Normal assignment

None
0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850, 7..255: for future use. The parameter shall be coded over 8 bits as a provision for future frequency bands support. - if FREQUENCY_RANGE = "GSM-DCS" then CELL_PARTITION_TYPE must be equal to "Concentric" . - The micro concentric, mini concentric and indoor concentric cells must be multiband (the allowed FREQUENCY_RANGE is PGSM-DCS1800 or EGSMDCS1800). This restriction does not apply to the external cells. - The frequency range of an extended inner cell has to be the same as the frequency range of the corresponding extended outer cell, where PGSM (0) and EGSM (2) are here considered as belonging to the same frequency range. 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".
-Values 4 and "5" are for Multiband cells. Transmitted to the BTS in the BTS_CONF_DATA message. --

04/03/2008 Ed14 rlsd: one mandatory rule removed: CR 226280
Page 10 of 33
MAX_GPRS_CS
MAX_GPRS_CS
B10 Oui
B9
Oui
Definition Maximum coding scheme used for GPRS traffic in the cell. Sub-system BSC Category Site (CAE) Instance cell OMC-R access Changeable Type Number Min value 2 Unit None Max value 4 Application domain GPRS Def value 2 Spec reference Coding rules Mandatory rules
GPRS MFS-BSC interface - BSCGP layer 1 : CS-2; 2 : CS-3; 3 : CS-4 MAX_GPRS_CS >= TBF_DL_INIT_CS MAX_GPRS_CS >= TBF_UL_INIT_CS

None
If Max_PDCH = 0 then MAX_GPRS_CS = CS-2. The aim of this last rule is to prevent the BSC to trigger uselessly the algorithms of adjust ranking and transmission pool set up (lead time and outage) for CS3 and CS4, in case Max_PDCH = 0 (i.e. GPRS is not allowed)
Recommended rules
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 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. For consistency reasons, MAX_GPRS_CS_SHORT_DATA_DL and MAX_GPRS_CS_SHORT_DATA_UL shall NOT be higher than any of the MAX_GPRS_CS values defined in the cells of the MFS. 1) 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. 2) This parameter can be set to CS-3 or CS-4 only if the CS-3/CS-4 feature has been bought by the Customer. CS-3 and CS-4 are supported on Evolium BTS only.
Internal Comment
External Comment

14/03/2008 05/03/2008 Ed14 rlsd: change in recommended rule: CR 235553 Ed14 rlsd: ext comments; CR 227496v3
Page 11 of 33
TRX_PREF_MARK
Preference Mark
B10 Oui
B9
Oui
Definition Preference mark assigned to a given TRX. Sub-system BSC Category Site (CAE) Instance TRX OMC-R access Changeable Type Number Min value 0 Unit None Max value 7 Application domain GSM Def value 1 Spec reference Coding rules
Resource allocation & management

None
0: PS/CS TRX: This TRX can carry PS and CS traffic and has the lowest preference in the TCH sub-channel selection process used to serve a CS call. 1: CS TRX with preference mark 1: This TRX can carry only CS traffic and has the preference mark 1 in the TCH sub-channel selection process used to serve a CS call. 7: CS TRX with preference mark 7: This TRX can carry only CS traffic and has the highest preference in the TCH sub-channel selection process used to served a CS call. It means that this TRX has the highest priority for CS traffic. 1) For a TRX in the inner zone of a monoband or multiband concentric cell, the parameter TRX_PREF_MARK shall be set to a non-null value. 2) For a hopping G1 TRX, if EGSM_RR_ALLOC_STRATEGY = 0 and BCCH/CCCH are configured on PGSM TRX then TRX_PREF_MARK <> 0 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. 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. -Note: It may happen that a TRX for which TRX_PREF_MARK <> 0 can carry also CS/PS signalling traffic (if it is the BCCH TRX and if there is an MPDCH on this TRX), see also the rules for the parameter NB_TS_MPDCH. 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 8PSK, 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).
Mandatory rules

04/03/2008 Ed14 rlsd: mandatory rule change, CR 226280
Page 12 of 33
Sub-system:
MFS
B10 Oui B9
Non
Ater_Usage_Threshold_Short_Data
Ater_Usage_Threshold_Short_Data
Sub-system Instance MFS Type Number Unit % Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules
Threshold (percentage of used Ater nibbles, in a GPU) above which the Ater usage is optimized for short data MS transfers. MFS Category Network (CDE)
OMC-R access None (DLS) Min value 0 Max value 100 Def value 100
FBS GPRS - Radio interface - RRM sublayer (PRH) ---
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 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.
Internal Comment External 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).
Page 13 of 33
BCCH_ARFCN(n)
BCCH_ARFCN
B10 Oui
B9
Oui
Definition Absolute Radio Frequency Channel Number of the BCCH of the adjacent cell. Sub-system MFS Category Site (CAE) Instance adj OMC-R access Changeable Type Number Min value 0 Coded Min 0 Unit None Max value 1023 Coded Max 1023 Application domain GSM Def value None Coded Def Spec reference Coding rules Mandatory rules
FBS GPRS - Radio interface - RRM sublayer (PRH) -- BCCH_FREQUENCY(n) = BCCH_ARFCN(n) 1) for Non Evolium serving cell : The cell neighborhood for reselection is controlled by EN_2G_TO_3G_CELL_RESELECTION value and FDD_ARFCN_LIST content. The cell neighborhood for handover is controlled by EN_3G_HO and FDD_ARFCN values. - if the neighborhood of the serving cell for reselection is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. - if the neighborhood of the serving cell for reselection is mixed 2G/3G, and if all 2G frequencies can be encoded in the SI2 or SI2bis message, and if the SI2ter message is used to encode only 3G frequencies, then there shall be no more than 31 different BCCH 2G frequencies for the set of all the target cells. - since the neighborhood of the serving cell for handover is 2G only, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. 2) For Evolium serving cell : The cell neighborhood for reselection is controlled by EN_2G_TO_3G_CELL_RESELECTION value and FDD_ARFCN_LIST content. The cell neighborhood for handover is controlled by EN_3G_HO and FDD_ARFCN values. - if the neighborhood of the serving cell for reselection is 2G only, or mixed 2G/3G, then there can be up to 32 different BCCH 2G frequencies for the set of all the target cells. There shall be no more than 32 different BCCH frequencies for the set of all target cells. - if the neighborhood of the serving cell for handover is 2G only, then there can be up -- Needed for MPDCH feature. 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. The OMC-R access is defined accordingly (changeable). The BCCH frequency of an adjacent internal cell is virtual changeable. - in case of Non Evolium serving cell, if neighborhood for reselection is mixed 2G/3G then no more than 31 frequencies (the OMC cannot performed the described mandatory check, but still present to give the really concerned case) --
Rec reference
None
Recommended rules Internal Comment
External Comment

05/03/2008 04/03/2008 Ed14 rlsd: new mandatory rule: CR 227496v3 Ed14 rlsd: one mandatory rule removed: CR 226280
Page 14 of 33
CHANNEL_REQ_PERIOD
CHANNEL_REQ_PERIOD
B10 Oui
B9
Non
Period value of the limitation mechanism of the MFS. During each period, the MFS could limit the number of CHANNEL REQUEST messages received from the BSC on the BSCGP interface. Over a given threshold, the new coming CHANNEL REQUEST messages are simply discarded until the end of the current period.
Sub-system MFS Instance MFS Type Number Unit ms Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
BSCGP ---
Category System (CST) OMC-R access None (not in DLS) Min value 0 Coded Min 0 Max value 5000 Coded Max 5000 Def value 800 Coded Def 800 Rec reference
None
Avoid multiple and divisor of 1 sec, because of the MS retry periodicity (the range is depending on Tx_integer and CCCH_CONF) ---

03/03/2008 Ed14: creation (CR 216748v2)
CHANNEL_REQ_THRES_GP
CHANNEL_REQ_THRES_GP
B10 Oui
B9
Non
Maximum number of CHANNEL REQUEST messages per second received from the BSC on the BSCGP interface, that will be accepted/processed by the MFS. Over that threshold, the new coming CHANNEL REQUEST messages are simply discarded until the end of the current period.
Sub-system MFS Instance MFS Type Threshold Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
BSCGP --
None
could not be greater than MAX_CTXT_MS_GP ----

03/03/2008 Ed14 creation (CR 216748v2)
Page 15 of 33
CHANNEL_REQ_THRES_GPU
CHANNEL_REQ_THRES_GPU
B10 Oui
B9
Non
Maximum number of CHANNEL REQUEST messages per second received from the BSC on the BSCGP interface, that will be accepted/processed by the MFS. Over that threshold, the new coming CHANNEL REQUEST messages are simply discarded until the end of the current period.
Sub-system MFS Instance MFS Type Threshold Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
BSCGP --
None
could not be greater than MAX_CTXT_MS_GPU ----

03/03/2008 Ed14: creation (CR 216748v2)
Page 16 of 33
FREQUENCY_RANGE(n)(MFS)
FREQUENCY_RANGE
B10 Oui
B9
Oui
Definition This parameter indicates the frequency range of the adjacent cell (GAN cell excluded). Sub-system MFS Category Site (CAE) Instance adj OMC-R access Changeable Type Number Min value 0 Coded Min 0 Unit None Max value 6 Coded Max 6 Application domain GSM Def value 0 Coded Def 0 Spec reference Coding rules Mandatory rules
Normal assignment
Rec reference
None
0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850, 7..255: for future use. The parameter shall be coded over 8 bits as a provision for future frequency bands support. - If FREQUENCY_RANGE(n) = "GSM-DCS" then CELL_PARTITION_TYPE(n) must be equal to "Concentric". - The micro concentric, mini concentric and indoor concentric cells must be multiband (the allowed FREQUENCY_RANGE(n) is PGSM-DCS1800 or EGSMDCS1800). This restriction does not apply to the external cells. - The frequency range of an extended inner cell has to be the same as the frequency range of the corresponding extended outer cell, where PGSM (0) and EGSM (2) are here considered as belonging to the same frequency range. -Values 4 and "5" are for Multiband cells. Within the same PLMN, the FREQUENCY_RANGE parameter of a given cell shall be selected among one of the following values: - PGSM (GSM900) or EGSM (GSM900) or DCS1800 or PGSM-DCS1800 or EGSMDCS1800 if the PLMN_FREQUENCY_BANDS is set to "GSM900 and DCS1800 bands", - GSM850 or DCS1800 if the PLMN_FREQUENCY_BANDS is set to "GSM850 and DCS1800 bands", - GSM850 or DCS1900 if the PLMN_FREQUENCY_BANDS is set to "GSM850 and

Page 17 of 33
MAX_EGPRS_MCS
MAX_EGPRS_MCS
B10 Oui
B9
Oui
Definition Maximum Modulation and Coding Scheme used for EGPRS traffic in the cell. Sub-system MFS Category Site (CAE) Instance cell OMC-R access Changeable Type Number Min value 1 Coded Min 0 Unit None Max value 9 Coded Max 8 Application domain GPRS Def value 9 Coded Def 8 Spec reference Coding rules
Not linked to a document 0: MCS-1; 1: MCS-2; 2: MCS-3; 3: MCS-4; 4: MCS-5; 5: MCS-6; 6: MCS-7; 7: MCS-8; 8: MCS-9; MAX_EGPRS_MCS >= TBF_DL_INIT_MCS MAX_EGPRS_MCS >= TBF_UL_INIT_MCS When cell_type = extended outer, then MAX_EGPRS_MCS <= MCS-4 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 => 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. For consistency reasons, MAX_EGPRS_MCS_SHORT_DATA_DL and MAX_EGPRS_MCS_SHORT_DATA_UL shall NOT be higher than any of the MAX_EGPRS_MCS values defined in the cells of the MFS. ---
Rec reference
None
Mandatory rules
Recommended rules

14/03/2008 Ed14 rlsd: change in recommended rule: CR 235553
Page 18 of 33
MAX_EGPRS_MCS_SHORT_DATA_DL
MAX_EGPRS_MCS_SHORT_DATA_DL
B10 Oui
B9
Non
Sub-system Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules
Maximum Modulation and Coding Scheme used for the DL EGPRS TBFs associated to a short data MS transfer. MFS Category Network (CDE)
FBS GPRS - Radio interface - RRM sublayer (PRH) 0: MCS-1; 1: MCS-2; 2: MCS-3; 3: MCS-4; 4: MCS-5; 5: MCS-6; 6: MCS-7; 7: MCS-8; 8: MCS-9. --
Mandatory rules Recommended rules Internal Comment External Comment
For consistency reasons, MAX_EGPRS_MCS_SHORT_DATA_DL shall NOT be higher than any of the MAX_EGPRS_MCS values defined in the cells of the MFS. A cell instantiation shall be used internally in the MFS, in prevision of a potential future evolution of the instance of this parameter (e.g. in future BSS releases). 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).

Page 19 of 33
MAX_EGPRS_MCS_SHORT_DATA_UL
MAX_EGPRS_MCS_SHORT_DATA_UL
B10 Oui
B9
Non
Sub-system Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules
Maximum Modulation and Coding Scheme used for the UL EGPRS TBFs associated to a short data MS transfer. MFS Category Network (CDE)
FBS GPRS - Radio interface - RRM sublayer (PRH) 0: MCS-1; 1: MCS-2; 2: MCS-3; 3: MCS-4; 4: MCS-5; 5: MCS-6; 6: MCS-7; 7: MCS-8; 8: MCS-9. --
For consistency reasons, MAX_EGPRS_MCS_SHORT_DATA_UL shall NOT be higher than any of the MAX_EGPRS_MCS values defined in the cells of the MFS. A cell instantiation shall be used internally in the MFS, in prevision of a potential future evolution of the instance of this parameter (e.g. in future BSS releases). --

14/03/2008 Ed14 rlsd: change in the recommended rule : CR 235553
Page 20 of 33
MAX_GPRS_CS_SHORT_DATA_DL
MAX_GPRS_CS_SHORT_DATA_DL
B10 Oui
B9
Non
Definition Maximum coding scheme used for the DL GPRS TBFs associated to a short data MS transfer. Sub-system MFS Category Network (CDE) Instance MFS OMC-R access None (DLS) Type Number Min value 1 Coded Min 0 Unit None Max value 4 Coded Max 3 Application domain GPRS Def value 1 Coded Def 0 Spec reference Coding rules
FBS GPRS - Radio interface - RRM sublayer (PRH) 0 : CS-1; 1 : CS-2; 2 : CS-3; 3 : CS-4. -For consistency reasons, MAX_GPRS_CS_SHORT_DATA_DL shall NOT be higher than any of the MAX_GPRS_CS values defined in the cells of the MFS. A cell instantiation shall be used internally in the MFS, in prevision of a potential future evolution of the instance of this parameter (e.g. in future BSS releases). 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).
Rec reference

Page 21 of 33
MAX_GPRS_CS_SHORT_DATA_UL
MAX_GPRS_CS_SHORT_DATA_UL
B10 Oui
B9
Non
Definition Maximum coding scheme used for the UL GPRS TBFs associated to a short data MS transfer. Sub-system MFS Category Network (CDE) Instance MFS OMC-R access None (DLS) Type Number Min value 1 Coded Min 0 Unit None Max value 4 Coded Max 3 Application domain GPRS Def value 2 Coded Def 1 Spec reference Coding rules
FBS GPRS - Radio interface - RRM sublayer (PRH) 0 : CS-1; 1 : CS-2; 2 : CS-3; 3 : CS-4. -For consistency reasons, MAX_GPRS_CS_SHORT_DATA_UL shall NOT be higher than any of the MAX_GPRS_CS values defined in the cells of the MFS. A cell instantiation shall be used internally in the MFS, in prevision of a potential future evolution of the instance of this parameter (e.g. in future BSS releases). --
Rec reference

Maximum_Credit
Maximum_Credit
B10 Oui
B9
Non
Sub-system Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
When a TBF credit reaches this maximum value, then the TBF can still be scheduled but its credit is no more increased. MFS Category System (CST)
OMC-R access None (not in DLS) Min value 20 Coded Min 20 Max value 20 Coded Max 20 Def value 20 Coded Def 20 Rec reference
None
GPRS radio interface - MAC sublayer step size = 1 --This constant is hardcoded in MAC. --

13/03/2008 Ed14 rlsd: spec reference added: CR 235069
Page 22 of 33
Maximum_Weight
Maximum_Weight When a TBF weight reaches this maximum value, then the TBF can still be scheduled but its weight is no more increased. MFS Category System (CST)
B10 Oui
B9
Non
Sub-system Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
OMC-R access None (not in DLS) Min value 45 Coded Min 45 Max value 45 Coded Max 45 Def value 45 Coded Def 45 Rec reference
GPRS radio interface - MAC sublayer step size = 1 --This constant is hardcoded in MAC --

Minimum_Credit_Weight
Minimum_Credit_Weight
B10 Oui
B9
Non
When a TBF credit or weight reaches this minimum value, then the TBF can still be scheduled (in the extra scheduling phase) but its credit/weight is no more decreased. This value can be negative. This value applies to both RT and NRT TBFs.
Sub-system MFS Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Category System (CST) OMC-R access None (not in DLS) Min value -10 Coded Min -10 Max value -10 Coded Max -10 Def value -10 Coded Def -10 Rec reference
None
GPRS radio interface - MAC sublayer step size = 1 --This constant is hardcoded in MAC --

13/03/2008 09/01/2008 Ed14 rlsd: spec reference added: CR 235069 Ed13: coded values added (missing)
Page 23 of 33
N_MAX_PERIODIC_REALLOC_ATTEMPT_T3
B10 Oui
B9
Oui
Defines the total number of (unsuccessful) T3 radio resource reallocation attempts that are allowed to be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer. As soon as N_MAX_PERIODIC_REALLOC_SUCCESS_T3 T3 radio resource reallocation attempts succeed, no other attempt is performed (even if less than N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 attempts have been performed so far). The UL-biased MSs and the DL-biased MSs are considered regardless of each other. As a result, in a given cell, up to 2 x N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 T3 radio resource reallocation attempts will be performed upon expiry of the timer.
Sub-system MFS Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment
Category System (CST) OMC-R access None (DLS) Min value 1 Max value 500 Def value 20

None
FBS GPRS - Radio interface - RRM sublayer (PRH) ----
External Comment
This parameter, with the parameter T_CANDIDATE_TBF_REALLOC, allows to : - control the reactivity of the BSS with regards to T3 TBF reallocations - and to control the extra CPU load generated by the T3 TBF reallocation attempts (the highest the value of N_MAX_PERIODIC_REALLOC_ATTEMPT_T3, the highest the generated CPU load). --

04/03/2008 Ed14 rlsd: EDA clarification: CR 229787v2
Page 24 of 33
B10 Oui
B9
Oui
Sub-system Instance MFS Type Number Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment
Defines the total number of T4 radio resource reallocation attempts (successful or not) that are performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer. MFS Category System (CST)

None
FBS GPRS - Radio interface - RRM sublayer (PRH) ----
External 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 --

04/03/2008 Ed14 rlsd: EDA clarification, CR 229787v2
N_UL_BIAS_FOR_EDA
N_UL_BIAS_FOR_EDA
B10 Oui
B9
Non
Sub-system Instance BSS Type Number Unit None Application domain E-GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Minimum number of significantly consecutive uplink biases observed during a transfer to allow a mobile station to use Extended Dynamic Allocation. MFS Category Site (CAE)

None
FBS GPRS - Radio interface - RRM sublayer (PCC) ----
B10 MR2 parameter A significantly-uplink bias is a bias with a traffic ratio superior to the BIAS_LIMIT_EDA parameter. This parameter can allow using EDA only in case of big UL transfers

04/03/2008 Ed14 rlsd, clarifications for EDA, CR 229787v2
Page 25 of 33
NETWORK_CONTROL_ORDER
NETWORK_CONTROL_ORDER
B10 Oui
B9
Oui
Definition This parameter defines whether the MS or the BSS controls the cell reselections. Sub-system MFS Category Site (CAE) Instance cell OMC-R access Changeable Type Number Min value 0 Coded Min 0 Unit None Max value 4 Coded Max 4 Application domain GPRS Def value 0 Coded Def 0 Spec reference Coding rules
FBS GPRS - Radio interface - RRM sublayer (PRH)
Rec reference
3GPP TS 44.060
0: NC0 mode of operation for all MS. All MS controls their cell reselections an no MS reports packet measurements to the BSS. 1: NC1 mode of operation for all MS. All MS controls their cell reselections but all the MS reports packet measurements to the BSS. (Not supported) 2: NC2 mode of operation for R99 onwards MS. The BSS controls the cell reselections of R99 onwards MS when in packet transfer mode or of R99 onwards MS when in GMM Ready state (depending on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS. 3: NC2 mode of operation for all MS. The BSS controls the cell reselections of all MS when in packet transfer mode or of all MS when in GMM Ready state (depending on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS. 4: NC2 mode of operation for Rel.4 onwards MS. The BSS controls the cell reselections of Rel.4 onwards MS when in packet transfer mode or of Rel.4 onwards MS when in GMM Ready state (depending on the selected NC2 deactivation mode). While the NC2 mode is activated for the concerned MS, the MS reports packet measurements to the BSS. - 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 --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 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.)
Mandatory rules

05/03/2008 Ed14 rlsd: ext comments changed: CR 233377
Page 26 of 33
OAM_VLAN_ID
OAM_VLAN_ID
B10 Oui
B9
Non
Definition Virtual LAN identifier used to tag the MxMFS internal O&M traffic Sub-system MFS Category System (CST) Instance MFS OMC-R access None (not in DLS) Type Number Min value 2 Coded Min 2 Unit None Max value 4094 Coded Max 4094 Application domain IP Def value 5 Coded Def 5 Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
GPRS Functional O&M Architecture' Coded on 12 bits. -In case the same subnet is used for Telecom and OAM traffic, the same VLAN_ID shall be used for Telecom and OAM VLAN_Ids. IP demo parameter. --
Rec reference
IEEE 802.1 Q 9.6

PD_UL_TBF_VOLUME_THR_1
PD_UL_TBF_VOLUME_THR_1
B10 Oui
B9
Oui
Sub-system Instance BSS Type Number Unit byte Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Upper limit of the 1st band, lower limit of the 2nd band for LLC volume carried by an UL TBF distribution MFS Category Site (CAE)
None
MFS counters catalogue step size = 1 byte
PD_UL_TBF_VOLUME_THR_1 < PD_UL_TBF_VOLUME_THR_2 -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)" --

05/03/2008 Ed14 rlsd: new int comment: CR 232329
Page 27 of 33
PMU_CPU_overload_step_H
PMU_CPU_overload_step_H
B10 Oui
B9
Oui
Sub-system Instance GPU Type Number Unit None Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Number of steps to increment the internal PMU variable used in the PMU CPU overload control algorithm, when the PMU is in CPU overload state. MFS Category System (CST)

None
Overload Control and CPU power budget management ----
The current default value is chosen so that reaction to overload is faster than return to normal behaviour. --

03/03/2008 Ed14: default value = 4 : CR 216661
SGSN_IP_Address
IP_Address
B10 Oui
B9
Non
Definition IP address of the SGSN IP endpoint used for Gb over IP Sub-system MFS Category Site (CAE) Instance SGSN-IPEndPoint OMC-R access Set by Create Type Number Min value 0 Unit None Max value 4294967295 Application domain GPRS Def value 0 Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
GPRS Gb interface - Network service control sub-layer

None
coded on 32 bits OMC must display the value of each octet following the format:www.xxx.yyy.zzz default value is 0.0.0.0 Each SGSN IP EndPoint (SGSN_IP_Address, SGSN_UDP_Port) must be unique per -B10 MR2 parameter --

14/03/2008 Ed14 rlsd: new HMI name: CR 234799v2
Page 28 of 33
SGSN_UDP_Port
Port_Number
B10 Oui
B9
Non
Definition UDP port number of the SGSN IP endpoint used for Gb over IP. Sub-system MFS Category Site (CAE) Instance SGSN-IPEndPoint OMC-R access Set by Create Type Number Min value 49152 Coded Min 49152 Unit None Max value 65535 Coded Max 65535 Application domain GPRS Def value 49152 Coded Def 49152 Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
GPRS Gb interface - Network service control sub-layer -Each SGSN IP EndPoint (SGSN_IP_Address, SGSN_UDP_Port) must be unique per -B10 MR2 parameter --
Rec reference
None

14/03/2008 Ed14 rlsd: new HMI name: CR 234799v2
Page 29 of 33
T_CANDIDATE_TBF_REALLOC
T_CANDIDATE_TBF_REALLOC
B10 Oui
B9
Oui
Timer value controlling the time duration between successive resource reallocation attempts for candidate MSs (triggers T3 and T4). In a given cell, at each expiry of the T_CANDIDATE_TBF_REALLOC timer : - up to N_MAX_PERIODIC_REALLOC_ATTEMPT_T4 T4 TBF reallocation attempts are performed, - up to N_MAX_PERIODIC_REALLOC_ATTEMPT_T4 T4 reallocations are performed, - up to 2 x N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 T3 TBF reallocation attempts are performed
Sub-system MFS Instance MFS Type Timer Unit sec Application domain Spec reference Coding rules Mandatory rules Recommended rules
GPRS
Category Network (CDE) OMC-R access None (DLS) Min value 1 Coded Min 1 Max value 20 Coded Max 20 Def value 1 Coded Def 1 Rec reference
None
FBS GPRS - Radio interface - RRM sublayer (PRH)
step size = 1 sec; value 1 means 1 sec; value 2 means 2 sec, and so on -T_GCH_INACTIVITY > T_CANDIDATE_TBF_REALLOC in all the cells of the BSS. This constraints avoids as much as possible that some GCHs are released and reestablished again some moments later. This way, the T3 and T4 TBF reallocations can benefit from the GCHs which are currently unused, but still established. -This parameter, together with the parameters N_MAX_PERIODIC_REALLOC_ATTEMPT_T3, N_MAX_PERIODIC_REALLOC_SUCCESS_T3 and N_MAX_PERIODIC_REALLOC_ATTEMPT_T4, allows to : - to control the reactivity of the BSS with regards to T3 and T4 TBF reallocations, - and to control the extra CPU load generated by T3 and T4 TBF reallocation attempts (the lowest the value of T_CANDIDATE_TBF_REALLOC, the highest the generated CPU

04/03/2008 Ed14 rlsd: EDA clarifications CR 229787v2
Page 30 of 33
Telecom_VLAN_ID
Telecom_VLAN_ID
B10 Oui
B9
Non
Definition Virtual LAN identifier used to tag the MFS internal telecom traffic Sub-system MFS Category System (CST) Instance MFS OMC-R access None (not in DLS) Type Number Min value 2 Coded Min 2 Unit None Max value 4094 Coded Max 4094 Application domain GPRS Def value 5 Coded Def 5 Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
GPRS Functional O&M Architecture' Coded on 12 bits. -In case the same subnet is used for Telecom and OAM traffic, the same VLAN_ID shall be used for Telecom and OAM VLAN_Ids. B10 MR2 parameter. It is needed for GboverIP and also for the IP transport (final --
Rec reference
IEEE 802.1 Q 9.6

13/03/2008 Ed14 rlsd: spec ref added + CST/not in DLS: CR 235069
WI_PR
Wait Indication for Packet Access Reject
B10 Oui
B9
Oui
Sub-system Instance cell Type Number Unit sec Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment
Wait indication used in IMMEDIATE ASSIGNMENT REJECT or PACKET ACCESS REJECT, when not in PMU CPU overload situation. MFS Category Site (CAE)

None
FBS GPRS - Radio interface - RRM sublayer (PCC) -WI_PR <= WI_PR_CPU_OVERLOAD. --
External Comment
SW change from B10 MRn (n not supporting the WI_PR_CPU_OVERLOAD parameter): Due to the fact that the MFS goes to MRm (with 1 <= n < m, m supporting the WI_PR_CPU_OVERLOAD parameter) before the BSC, it is needed that the OMC plays the WI_PRnm migration rule when going to MRm. As a consequence, it is needed to play a GPRS resynchro at OMCMFS SW change time from MRn to MRm. --

04/03/2008 Ed14 rlsd: CR 217276v6
Page 31 of 33
WI_PR_CPU_OVERLOAD
Wait Indication for Packet Access Reject when CPU overload
B10 Oui
B9
Non
Sub-system Instance cell Type Number Unit sec Application domain GPRS Spec reference Coding rules Mandatory rules Recommended rules Internal Comment External Comment
Wait indication used in IMMEDIATE ASSIGNMENT REJECT or PACKET ACCESS REJECT, when in PMU CPU overload situation. MFS Category Site (CAE)
GPU Overload Control and CPU power budget management -WI_PR <= WI_PR_CPU_OVERLOAD. ----

04/03/2008 Ed14 rlsd: creation, CR 217276v6
Page 32 of 33
Sub-system:
OMC
B10 Oui B9
Oui
FREQUENCY_RANGE(n)(OMC)
FREQUENCY_RANGE
Definition This parameter indicates the frequency range of the adjacent cell (internal or external to the OMC). Sub-system OMC Category Site (CAE) Instance cell OMC-R access Changeable Type Number Min value 0 Coded Min 0 Unit None Max value 7 Coded Max 7 Application domain GSM Def value 0 Coded Def 0 Spec reference Coding rules Mandatory rules
Normal assignment
Rec reference
0: PGSM (GSM 900), 1: DCS 1800, 2: EGSM, 3: DCS 1900, 4: PGSM-DCS1800, 5: EGSM-DCS1800, 6: GSM 850, 7: GAN, 8..255: for future use. The parameter shall be coded over 8 bits as a provision for future frequency bands support. - if FREQUENCY_RANGE = "GSM-DCS" then CELL_PARTITION_TYPE must be equal to "Concentric" . - if FREQUENCY_RANGE = GAN then CELL_RANGE must be equal to GAN - the value GAN is only allowed for the OMC external cells - The micro concentric, mini concentric and indoor concentric cells must be multiband (the allowed FREQUENCY_RANGE is PGSM-DCS1800 or EGSMDCS1800). This restriction does not apply to the external cells. - The frequency range of an extended inner cell has to be the same as the frequency range of the corresponding extended outer cell, where PGSM (0) and EGSM (2) are here considered as belonging to the same frequency range. 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".
Values 4 and "5" are for Multiband cells. Value "7" exists only starting from MR2.

Page 33 of 33

0134 14delta

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

0134 14delta

Uploaded by

Copyright:

Available Formats

BSS Telecom Parameters

Delta between edition 14 released and edition 13 released

Delta for the BSS Telecom Parameters Catalogue

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Coded Min 0 Coded Max 1023 Coded Def Rec reference

Recommended rules Internal Comment

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name Definition

System information management ----

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Recommended rules Internal Comment External Comment

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name Definition

OMC-R access Changeable Min value 0 Max value 3 Def value 0

Coded Min 0 Coded Max 3 Coded Def 0 Rec reference

System information management

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Coded Min 0 Coded Max 1 Coded Def 0 Rec reference

Recommended rules Internal Comment External Comment

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name Definition

OMC-R access Changeable Min value 0 Max value 1 Def value 0

Coded Min 0 Coded Max 1 Coded Def 0 Rec reference

TFO Functional specification 0: disabled; 1: enabled

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Coded Min 0 Coded Max 6 Coded Def 0 Rec reference

Recommended rules Internal Comment External Comment

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Coded Min 1 Coded Max 3 Coded Def 1 Rec reference

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Coded Min 0 Coded Max 7 Coded Def 1 Rec reference

Recommended rules Internal Comment External Comment

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

FBS GPRS - Radio interface - RRM sublayer (PRH) ---

Internal Comment External Comment

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name

Recommended rules Internal Comment

Modif date Modif description

Delta for the BSS Telecom Parameters Catalogue

Logical name HMI name Definition

Modif date Modif description

Logical name HMI name Definition