Cell Outage Management in LTE Networks M. Amirijoo (Ericsson), L. - PDF document

FP7 ICT-SOCRATES Cell Outage Management in LTE Networks M. Amirijoo (Ericsson), L. Jorguseski (TNO ICT), T. Kürner (TU Braunschweig), R. Litjens (TNO ICT), M. Neuland (TU Braunschweig), L. C. Schmelz (Nokia Siemens Networks), U. Türke (Atesio) Abstract Cell outage management is a functionality aiming at automatically detecting and mitigating outages that occur in radio networks due to unexpected failures. The FP7 EU-funded project SOCRATES (Self-Optimisation and self-ConfiguRATion in wirelEss networkS) is heavily engaged in developing a framework and solutions for cell outage management, where appropriate measurements, control parameters, policies, assessment methodologies, and algorithms are being developed. Our vision is that radio networks autonomously detect an outage based on measurements, from e.g., user equipment and base stations, and alter the configuration of radio base stations such that coverage and service quality requirements during an outage, as specified by the operator, are satisfied. In this presentation we give an introduction in the area of cell outage management and present an overview of the results achieved so far as well as the next steps that will be pursued. 1 1

Outline � Introduction � Components in cell outage management � Operator policy � Measurement � Control parameters � Scenarios � Assessment criteria � Simulator � Future work WWW.FP7-SOCRATES.EU 2/20 2/20 2

Introduction � One aspect that benefits from self-organization is cell outage management (COM), which consists of: – Cell outage detection – Cell outage compensation � Reasons for outages, e.g.: – hardware and software failures, – external failures such as power supply or network connectivity � Outages – may not be detected for hours or even days – may require manual analysis and unplanned site visit – SOCRATES COM concentrates on those cases where an eNodeB reset does not help � Outage detection function must timely inform the operator about the occurrence and the cause of an outage � Automatic compensation actions are triggered to alleviate performance degradation WWW.FP7-SOCRATES.EU 3/20 3/20 There are multiple reasons for a cell outage, e.g., hardware and software failures (radio board failure, channel processing implementation error etc), external failures such as power supply or network connectivity failures, or even erroneous configuration. While some cell outage cases are detected by Operations Support System (OSS) functions through performance counters and/or alarms, some may not be detected for hours or even days. It is often through long term performance analysis and subscriber complaints that these outages are detected. Currently, discovery and identification of some errors involves sometimes manual analysis and may require unplanned site visits, which makes cell outage detection a costly task. It is the task of the cell outage detection function to timely inform the operator about the occurrence of an outage and the cause of the outage. In the event of a cell outage detection, appropriate compensation methods are triggered to alleviate the degraded performance due to the resulting coverage gap and loss in throughput by appropriately adjusting radio parameters in surrounding sites. In general, human involvement shall only be triggered when absolutely necessary, e.g., when manual repairs are needed. 3 3

Components of Cell Outage Management Control parameters Operator policy: Coverage, QoS Compensation -70 2000 -80 1500 -90 1000 -100 500 -110 0 -120 Measurements -130 Detection -500 -140 -1000 -150 -1500 Cov. map -160 -2000 -170 -2000 -1500 -1000 -500 0 500 1000 1500 2000 2500 estimation Simulation tools Scenarios Assessment criteria WWW.FP7-SOCRATES.EU 4/20 4/20 Various measurements are gathered from the user equipments (UEs) and the base stations (called eNodeBs in LTE). The measurements are then fed into the cell outage detection function, which detects whether at the current time an outage has occurred and triggers the cell outage compensation function to take appropriate actions. The goal of cell outage compensation is to minimise the network performance degradation when a cell is in outage. This is done by automatic adjustment of network parameters in order to meet the operator’s performance requirements based on coverage and other quality indicators, e.g., throughput. It is realized that performance requirements may not be achieved during an outage and, as such, the goal of the compensation function is to meet performance requirements to the largest possible extent. Cell outage compensation algorithms may for example alter the antenna tilt and azimuth, or the cell transmit power, in order to cover the area that is in outage. Altering the radio parameter of the neighbouring cells means that some of the UEs served by neighbouring cells may be affected. For example, if the coverage of a neighbouring cell increases then this implies that more UEs will be served and, consequently, the UE throughput may decrease. This should be taken into account and an appropriate balance between coverage and other quality indicators (e.g. throughput) should be achieved. This balance is indicated by means of an operator policy that governs the actions taken by the cell outage compensation function. In order to monitor and evaluate the actions taken by the cell outage compensation algorithm, there is a need to estimate the coverage around the vicinity of the outage area. This is provided by the coverage map estimation function, which continuously monitors the network coverage by means of measurements and possibly prediction data. There are also other activities being pursued along this work, namely, the development of simulation tools, scenarios that capture different outage cases, and methods and criteria for assessing the impact and performance of cell outage detection and compensation algorithms. 4 4

Measurements � Continuous and event-triggered measurements required for cell eNodeB2 outage management aGW UE2 � Measurement Sources and Types: – Affected eNodeB: Counters and KPIs, Timers, Alarms, Reports – Neighbour eNodeB: Counters and KPIs, Timers, Alarms, Reports UE1 – User Equipment: Measurements, eNodeB4 eNodeB1 Reports – Access Gateway: Alarms, Timers, Counters – OSS System: Statistics eNodeB3 WWW.FP7-SOCRATES.EU 5/20 5/20 The following example nodes may be used when collecting the measurements. eNodeB1 denotes the eNodeB that encounters a cell/sector outage or a complete node outage (marked by a flash). UE1 is served by eNodeB1 (shown by solid line). UE1 furthermore receives signal from neighbouring eNodeBs 2 and 3 (shown by dotted line) and reports measurements to eNodeB1. eNodeB2 – eNodeB4 are neighbouring eNodeBs of eNodeB1. The X2 interface between affected eNodeB1 and neighbouring eNodeBs is shown by a dashed line. UE2 is served by eNodeB2. Furthermore, UE2 receives signal from eNodeB1 (shown by dotted line) and reports measurements to its serving eNodeB2. Access Gateway (aGW) where affected eNodeB1 is connected to via S1 interface is shown by a dashed line. 5 5