Scribd
Upload
98 views2 pages

MFBI Parameters

The document outlines the addition of MFBIPR objects for each E-UTRA carrier frequency at neighboring sites, necessitating specific parameters for implementation. It emphasizes the importance of activating feature LTE2754 across all nodes to prevent handover failures, particularly for AWS-1 cells, and highlights the benefits for IoT device compatibility. The implementation must be completed by March 30, 2018, using a SON Custom Module to ensure proper configuration and activation.

Uploaded by

surma12
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
98 views2 pages

MFBI Parameters

The document outlines the addition of MFBIPR objects for each E-UTRA carrier frequency at neighboring sites, necessitating specific parameters for implementation. It emphasizes the importance of activating feature LTE2754 across all nodes to prevent handover failures, particularly for AWS-1 cells, and highlights the benefits for IoT device compatibility. The implementation must be completed by March 30, 2018, using a SON Custom Module to ensure proper configuration and activation.

Uploaded by

surma12
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

 A new object: MFBIPR have to be added for each E-UTRA carrier frequency of neighboring

sites.

 This means, X number of eutraCarrierFreq = X MFBIPRs to be added (each with specific


values for MFBIPR id and E-UTRA carrier freq).

Technolo Object Parameter Current Recommend


gy Value ed Value
LTE LNBTS actMFBI FALSE TRUE
LTE LNBTS/ mfbiPrId N/A Please see the
MFBIPR note below
LTE LNBTS/ addFreqBandInd N/A 66
MFBIPR
LTE LNBTS/ addSpectrEmiss N/A 3
MFBIPR Req
LTE LNBTS/ eutraCarrierFreq N/A Please see the
MFBIPR note below RELATED PARAMETERS
LTE LNBTS/ freqBandIndPrio N/A broadcasted
MFBIPR - eutraCarrierFreq
shall be derived from the eARFCN of ALL Band4 cells (LNCEL/ earfcnDL) hosted on the eNB, and
neighboring eNBs based on (LNADJL/fDlEarfcn) or (LNHOIF/eutraCarrierInfo). Band 4 eARFCN
ranges 1950-2399
- More than one LNBTS/ MFBIPR may be created, and each LNBTS/ MFBIPR contains a unique
combination of mfbiPrId and eutraCarrierFreq
- LNBTS is the object name used in FL16A and this object name will be LNBTS_FDD in FL17

BENEFITS

- LTE2754 will be applied to AWS-1 cells to indicate additional band of B66, so that UEs
supporting B66 will be considered to use B66 instead of B4 in AWS-1 cells in order to make
B66+B66, or B66+B66+x Carrier Aggregation possible
- Upcoming IoT devices will only support B66, which makes LTE2754 a prerequisite to support
those IoT devices

PERFORMANCE IMPACT
This feature needs to be activated in all the nodes in the market (existing and planned) to avoid
possible HO failures.

- Once an eNB has LTE2754 enabled, all its neighboring eNBs must have LTE2754 enabled as
well to avoid HO failures towards the AWS-1 cells because the source eNB needs to have the
correct understanding of the target AWS-1 cell’s eARFCN, e.g. B66 vs. B4
- LTE2754 must be enabled on ALL eNBs which host AWS-1 cells, and ALL eNBs which have
neighboring AWS-1 cells.
- A SON Custom Module was developed to activate the feature and set the corresponding “E-UTRA
carrier frequency” by looking for AWS-1 cells on the eNB, and also by checking LNADJ for any AWS-
1 neighboring cells.
- Any identified AWS-1 cells from LNCEL or LNADJ will need to be added to MFBIPR objects

MFBI was tested in Austin for months and was deployed in whole Austin market last September 2017.
MFBI functionality was also tested in micro and pico in the same market.

OPERATIONAL IMPACT
This is an online change , it will take effect immediately with no need for object locking.

IMPLEMENTATION

1. Activate feature LTE2754 using the SON module which has the correct parameter settings in all
nodes. This same Custom Module can be used for macro, micro & pico.

2. All markets need to activate this feature before March 30, 2018 to avoid HO failure issues that
can occur at market borders.

Link to SON Custom Module : http://son.t-mobile.com/modules.php?


guiname=tmo_4GN_LTE2754_ActivateMFBI

You might also like