LTE - PCI IP Mapping for ANR

[nron3]

Hi All,

Do any1 can explain for me why and how to do PCI IP Mapping for ANR.
Many thank ya.

[JCarlos21]

Hi mate,

Using which one?

LTE492: ANR or LTE782: ANR - UE based is activated ?

Br,

[nron3]

Hi Mate,
It is LTE492.
Do u have any power point talk about ANR?

[JCarlos21]

Gotta check and see if I can find something for you.

Let you know if anything comes up.

Regards,

[nron3]

Thank a lot... If it is P&C, hope u may PM me or send to ghee148@gmail.com
highly appreciate for your sharing.

[qarmates]

Hi,

LTE492

Automated neighbor relation (ANR) LTE492 requires X2 connectivity to learn the neighbor cell configuration. The learned configuration data are stored persistent in LNADJ and LNADJL. This supports in case of X2 outage mobility via S1 HO

[qarmates]

Prerequisite

• geo-locations and
  
• antenna direction have to be configured for all cells

In LTE networks the UE mobility relies on information given by neighbor cell relations and neighbor cell configurations. An automatic mechanism is implemented to discover and integrate unknown cells. It supports and allows the automated configuration and update of neighbor cell information without the need of an off-line planning update of the neighbor cell configurations.
The neighbor cell configuration via X2 is initiated by UE-measurements of a camping UE. The eNB considers only PCI values of A3 and A5 UE measurements that are used for an HO attempt for creation of a persistent neighbor relation (LNREL).
The UE reports all detected/strongest cells above a given threshold. Therefore it may report strong cells whose PCI are currently not yet known to the Flexi Multiradio BTS. The eNB checks in the A3/A5 measurement when there are more PCI reported, if the unknown PCI is the only target to be selected. In this case, the Flexi Multiradio BTS looks up the C-plane IP-connectivity information (IP address) of the relevant neighbor eNB, hosting the unknown cell.
If the Flexi Multiradio BTS successfully looks-up the IP-connectivity information and if there is not yet a X2 interface already established to this neighbor site the X2 signalling connectivity is set-up and an IPsec tunnel that is used for S1 traffic is also used for the X2 traffic as configured, if network domain security is applied. The X2 UP interface (X2_U) is set up during the first handover event between a pair of eNBs, including IPsec tunnel over S1 interface, if network domain security is applied. A new neighbor relation (instance of LNREL) is created for that neighbor cell, if an HO attempt is initiated to this neighbor cell.

ANR supports IPsec star topology configurations where an IPsec tunnel that is used for S1 traffic is also used for X2 traffic as configured. IPsec meshed topology configurations are not supported.

The resolution of PCI to IP-connectivity information is done by means of a PCI/RF/IPaddress look up table stored at the eNB, provided by O&M-configuration (NetAct Optimizer, NetAct Configurator).
The PCI/RF/IPaddress look-up table provides a mapping of PCI assigned to a neighbor cell. The table includes information about related C-plane IP-address used by a cell on a certain RF-carrier and C-plane IPaddress of the Flexi Multiradio BTS serving the cell.
The generation of the PCI/RF/IPaddress look-up table is part of the auto-connection/auto-configuration procedure. The operator can as well execute this functionality manually for a selected set of operational eNBs.



BR

[nron3]

Dear Mate,
Do u have any guide line about how to do PCI IP mapping in Netact.
many thank.

[qarmates]

NetAct Optimizer: Neighbor evaluation procedure
Triggered during the auto-configuration procedure for a new deployed eNB, the NetAct Optimizer calculates the distance to other cells and creates a list of found neighbor cell relations. Then eNB selects for the closest cells the eNB and adds all its cells into the list. The result is given to NetAct Configurator to complete the configuration plan file for the new eNB. These are not “found neighbor cell relations” but simply “a larger list of geo-graphic closest neighbor sites as look-up table for the eNB”. With the intention, that the eNB can establish an X2 link, only to those, that are actually visible and reported by connected UEs. Therefore, the look-up table has much more entries than X2 links can establish in a single center frequency deployment. In a two center frequency deployment and/or even one with un-equal cell sizes, this is still sufficient with the current limit of 200 entries.

Additional setting to control the generation of the PCI/RF/IP address table
NetAct Optimizer supports the creation of the PCI/RF/IP address table. The contained cells in the PCI/RF/IP address table are controlled by the operator with additional settings, that are supported in the following use cases:

• Auto configuration of LTE492: ANR (global preference settings)
  
• Manual trigger of LTE492: ANR (user-specific preference settings)

The operator can configure the execution of the neighbor finding algorithm during the LTE492: ANR work-flow:

• Maximum allowed number of neighbor cells
  
  
  • Maximum allowed number of total neighbor cells irrespective of carrier OR
    
  • ONE maximum allowed number of neighbor cells per carrier configured in any served cells inside eNB and
    
  • ONE maximum allowed number of neighbor cells per carrier not configured in any cell inside eNB
  
  
  
• Additionally, not more than 200 neighbor cell candidates are allowed to add.
  
• Maximum allowed distance from any served cell to a neighbor cell.

Those cells beyond the limits are excluded. From one neighbor eNB only the suitable cells are put to the list. With respect to the distance, each served cell of a distributed site configuration can have a different distance to a neighbor cell. A cell is excluded only, if the distance to all served cells is beyond the maximum allowed distance. The cells of the served eNB are not added at all.
NetAct Optimizer prevents to add additional far away cells with equal PCI/RF values to the PCI/RF/IP address table. In case of equal PCI/RF among neighbor cells, NetAct Optimizer adds only the closest (highest prioritized) neighbor candidate cell to the PCI/RF/IP address table. Neighbor cells with equal PCI/RF to any served cell are not added at all.
Benefit
The operator can limit the entries in the PCI/RF/IP address table for each carrier to ensure fair share for each carrier. In addition the operator can distinguish carriers for those a not served cell is configured and that would require intra- or inter-frequency ANR and HO. This allows the operator to fill the PCI/RF/IP address table with inter-frequency candidates to not served cell's frequencies only, by setting the served cell preference value to “0”.
The operator can prohibit adding entries into the PCI/RF/IP address table with respect to the distance between served cell towards neighbor cell. This prevents to have far away neighbor cells on certain carriers considered.


NetAct Configurator: Automated neighbor site IP connectivity configuration completion
As soon as NetAct Optimizer has completed the neighbor evaluation, it hands over the result to NetAct Configurator which starts to look into the configuration files of the neighbor eNB.
For each found, the Configurator opens the configuration plan file and copies all found IP-address connectivity information relevant for X2 establishment and the relevant PCIs/RFs. If needed, the Configurator will automatically run a “Plan Prepare” before download of the plan, to enhance the plan to update the mapping table information of all affected eNB in the neighborhood of a newly installed eNB. Optionally, Configurator runs a plan prepare to align the mapping tables to modified PCI values, too. Both are regular behavior in 2G and 3G that is used to align adjacent-cell objects in the neighborhood of the modified cells.
The updated configuration plan file (including the PCI/RF/IPaddress look-up table) is now ready to be downloaded automatically as part of the auto-configuration process.
After the new neighbor sites are successfully included into the local configuration data, the Flexi Multiradio BTS sends a configuration change notification to the Network Management System (NetAct) to synchronize the local configuration changes.
As soon as a self-learned X2 connection has been successfully established, its IP address becomes part of the normal configuration data and thereby this X2 connection becomes persistent (for example does not need to be detected by UE measurements anymore, BTS-restart safe).
If an operator has not licensed or does not want to utilize the ANR-feature he is able to pre-configure X2-connectivity information (IP-addresses) by O&M-configuration (plan file).

Operator hint The feature LTE492: ANR works in coverage limited network deployments very similar as the feature LTE782: ANR - UE based in passive ANR mode. In addition it is required to have up-to-date PCI/IP address tables in all eNBs, for any change of a PCI value. This is automatically done by NetAct. It is possible to run LTE492: ANR when LTE782: ANR - UE based is activated, for example to use PCI/IP address tables for inter-frequency HO support. In case of configuration plans with PCI updates, for example LTE468: Self-healing, Itf-N configuration or manual operator action, NetAct keeps the known own and neighbor eNB's LTE492: ANR PCI/IP address table up-to-date. In capacity limited network deployments LTE492: ANR and LTE782: ANR - UE based in passive ANR mode work quite similar as well. Similar operator shall watch the NR from a performance point of view. The operator can influence the amount of resolved neighbor cells with the LNCEL parameter anrThresNbCell. The default value 40 (= -100dBm) does ignore PCI values reported with RSRP less than -100dBm as a neighbor. In urban deployments this value is recommended to be increased to 50..60 (= -90..-80dBm). The eNB does establish a new LNREL only, if an HO attempt is initiated to the resolved neighbor cells. If for an eNB, too many LNREL are created, then those can be deleted with the help of NetAct. NetAct supports filter mechanism to list LNREL to a plan and apply delete operation on this list entries, in the manner of a mass configuration. By setting of an higher threshold, less neighbor relation are resolved. During the upgrade, the operator should have changed all the existing IP addresses to run in eNB controlled mode by setting the LNADJ - parameter cPlaneIpAddrCtrl = “enbControlled (1)”.

[kentck86]

Hi,

Can you share any document presentation related to this would be much appreciated.

thank you

NetAct Optimizer: Neighbor evaluation procedure
Triggered during the auto-configuration procedure for a new deployed eNB, the NetAct Optimizer calculates the distance to other cells and creates a list of found neighbor cell relations. Then eNB selects for the closest cells the eNB and adds all its cells into the list. The result is given to NetAct Configurator to complete the configuration plan file for the new eNB. These are not “found neighbor cell relations” but simply “a larger list of geo-graphic closest neighbor sites as look-up table for the eNB”. With the intention, that the eNB can establish an X2 link, only to those, that are actually visible and reported by connected UEs. Therefore, the look-up table has much more entries than X2 links can establish in a single center frequency deployment. In a two center frequency deployment and/or even one with un-equal cell sizes, this is still sufficient with the current limit of 200 entries.

Additional setting to control the generation of the PCI/RF/IP address table
NetAct Optimizer supports the creation of the PCI/RF/IP address table. The contained cells in the PCI/RF/IP address table are controlled by the operator with additional settings, that are supported in the following use cases:

• Auto configuration of LTE492: ANR (global preference settings)
• Manual trigger of LTE492: ANR (user-specific preference settings)

The operator can configure the execution of the neighbor finding algorithm during the LTE492: ANR work-flow:

• Maximum allowed number of neighbor cells
  
  • Maximum allowed number of total neighbor cells irrespective of carrier OR
  • ONE maximum allowed number of neighbor cells per carrier configured in any served cells inside eNB and
  • ONE maximum allowed number of neighbor cells per carrier not configured in any cell inside eNB
  
  
• Additionally, not more than 200 neighbor cell candidates are allowed to add.
• Maximum allowed distance from any served cell to a neighbor cell.

Those cells beyond the limits are excluded. From one neighbor eNB only the suitable cells are put to the list. With respect to the distance, each served cell of a distributed site configuration can have a different distance to a neighbor cell. A cell is excluded only, if the distance to all served cells is beyond the maximum allowed distance. The cells of the served eNB are not added at all.
NetAct Optimizer prevents to add additional far away cells with equal PCI/RF values to the PCI/RF/IP address table. In case of equal PCI/RF among neighbor cells, NetAct Optimizer adds only the closest (highest prioritized) neighbor candidate cell to the PCI/RF/IP address table. Neighbor cells with equal PCI/RF to any served cell are not added at all.
Benefit
The operator can limit the entries in the PCI/RF/IP address table for each carrier to ensure fair share for each carrier. In addition the operator can distinguish carriers for those a not served cell is configured and that would require intra- or inter-frequency ANR and HO. This allows the operator to fill the PCI/RF/IP address table with inter-frequency candidates to not served cell's frequencies only, by setting the served cell preference value to “0”.
The operator can prohibit adding entries into the PCI/RF/IP address table with respect to the distance between served cell towards neighbor cell. This prevents to have far away neighbor cells on certain carriers considered.


NetAct Configurator: Automated neighbor site IP connectivity configuration completion
As soon as NetAct Optimizer has completed the neighbor evaluation, it hands over the result to NetAct Configurator which starts to look into the configuration files of the neighbor eNB.
For each found, the Configurator opens the configuration plan file and copies all found IP-address connectivity information relevant for X2 establishment and the relevant PCIs/RFs. If needed, the Configurator will automatically run a “Plan Prepare” before download of the plan, to enhance the plan to update the mapping table information of all affected eNB in the neighborhood of a newly installed eNB. Optionally, Configurator runs a plan prepare to align the mapping tables to modified PCI values, too. Both are regular behavior in 2G and 3G that is used to align adjacent-cell objects in the neighborhood of the modified cells.
The updated configuration plan file (including the PCI/RF/IPaddress look-up table) is now ready to be downloaded automatically as part of the auto-configuration process.
After the new neighbor sites are successfully included into the local configuration data, the Flexi Multiradio BTS sends a configuration change notification to the Network Management System (NetAct) to synchronize the local configuration changes.
As soon as a self-learned X2 connection has been successfully established, its IP address becomes part of the normal configuration data and thereby this X2 connection becomes persistent (for example does not need to be detected by UE measurements anymore, BTS-restart safe).
If an operator has not licensed or does not want to utilize the ANR-feature he is able to pre-configure X2-connectivity information (IP-addresses) by O&M-configuration (plan file).

Operator hint The feature LTE492: ANR works in coverage limited network deployments very similar as the feature LTE782: ANR - UE based in passive ANR mode. In addition it is required to have up-to-date PCI/IP address tables in all eNBs, for any change of a PCI value. This is automatically done by NetAct. It is possible to run LTE492: ANR when LTE782: ANR - UE based is activated, for example to use PCI/IP address tables for inter-frequency HO support. In case of configuration plans with PCI updates, for example LTE468: Self-healing, Itf-N configuration or manual operator action, NetAct keeps the known own and neighbor eNB's LTE492: ANR PCI/IP address table up-to-date. In capacity limited network deployments LTE492: ANR and LTE782: ANR - UE based in passive ANR mode work quite similar as well. Similar operator shall watch the NR from a performance point of view. The operator can influence the amount of resolved neighbor cells with the LNCEL parameter anrThresNbCell. The default value 40 (= -100dBm) does ignore PCI values reported with RSRP less than -100dBm as a neighbor. In urban deployments this value is recommended to be increased to 50..60 (= -90..-80dBm). The eNB does establish a new LNREL only, if an HO attempt is initiated to the resolved neighbor cells. If for an eNB, too many LNREL are created, then those can be deleted with the help of NetAct. NetAct supports filter mechanism to list LNREL to a plan and apply delete operation on this list entries, in the manner of a mass configuration. By setting of an higher threshold, less neighbor relation are resolved. During the upgrade, the operator should have changed all the existing IP addresses to run in eNB controlled mode by setting the LNADJ - parameter cPlaneIpAddrCtrl = “enbControlled (1)”.