You are on page 1of 17

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

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

e. 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. which consists of: – Cell outage detection – Cell outage compensation  Reasons for outages. In general. some may not be detected for hours or even days. human involvement shall only be triggered when absolutely necessary. channel processing implementation error etc). external failures such as power supply or network connectivity failures. It is often through long term performance analysis and subscriber complaints that these outages are detected.g.. e.EU 3/20 There are multiple reasons for a cell outage.: – hardware and software failures.FP7-SOCRATES. 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.g. when manual repairs are needed. hardware and software failures (radio board failure. or even erroneous configuration.g. discovery and identification of some errors involves sometimes manual analysis and may require unplanned site visits. 3 3 . Currently. which makes cell outage detection a costly task. In the event of a cell outage detection.. While some cell outage cases are detected by Operations Support System (OSS) functions through performance counters and/or alarms. – 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. Introduction  One aspect that benefits from self-organization is cell outage management (COM). e.

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

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

Error Indication. On the other hand. RSRP includes measurements of serving and neighbouring cells but is reported only to the serving eNodeB •Channel Quality Indicator (CQI): the CQI is a measurement about the radio channel quality of the serving eNodeB which is taken by the UE. X2 Setup Failure. and reported only to the serving eNodeB. this is still a topic FFS •Reference Signal Received Power (RSRP): sudden decrease in received power level of serving or neighbour cells may indicate a cell outage. Relevant cause values for cell outage management are: “Cell not Available”. eNodeB Configuration Update Failure. These alarms could be used for cell outage detection and cause analysis 6 6 . These historic could be provided to the new serving eNodeB after cell re-selection for failure cause analysis (FFS in standardisation) •Blocked / dropped calls: the number of blocked or dropped calls is counted by the eNodeB and by default sent to the OAM system – a sudden increase may indicate cell outage •Alarms from eNodeB / aGW: eNodeB and aGW send alarms to the OAM system in case of connection failures. Handover Request. Handover Preparation Failure.g. •Cell Capacity: zero capacity or sudden decrease of capacity may indicate an outage •Radio Link Failure (RLF) counter: sudden increase may indicate a cell outage •Internal handover failure rate: high failure rate of internal handovers (between sectors / cells of one eNodeB) may indicate the outage of a sector / cell •Incoming / outgoing handover failure rate: high inter-eNodeB handover failure rate towards dedicated eNodeB may indicate outage of a sector of this eNodeB or the whole eNodeB •Relative load indicator: message is exchanged between neighbouring eNodeBs via X2 interface to transfer load and interference coordination information.g. in standardisation. These reports can also be used for cell outage detection or cause analysis •Historic measurements: the UE provides measurements such as RSRP. Measurements . and the resource request could also be used to confirm potential outages that have been indicated by other measurements •Cause Information Element: multiple X2 messages include the (mandatory) information element (IE) "Cause". due to a cell outage) the latest measurements are usually lost. handover failures etc. A sudden decrease of the CQI level may indicate an upcoming cell outage of the serving eNodeB. “Hardware Failure”. It is to be further investigated to see which of the measurements that are needed by the cell outage management functions. e. speech which is for further study (FFS).Details  Measurements from eNodeB: – Cell capacity – Radio Link Failure (RLF) counter – Internal / External Handover failure rate – Relative Load Indicator – Resource status reporting – Cause information element – Interference – Buffer information (send / receive)  Measurements from UE: – Reference Signal Received Power (RSRP) / Channel Quality Identifier (CQI) – Failure reports. e. and Resource Status Failure. e. after failed handover – Buffer information  Measurements form aGW / OSS System: – Blocked / dropped calls counters – Alarms from eNodeBs / aGW WWW.g. The indication of sudden interference level decrease reported through load indicator messages may indicate a cell outage at the sending eNodeB •Resource status reporting: an eNodeB may request resource status from neighbouring eNodeBs via X2 interface. Handover Cancel. This information exchanged via X2 interface can be used for cell outage detection and cause analysis •Interference measurements: sudden changes (reduction) in interference measurements taken by eNodeB or UE may indicate outage of neighbour eNodeB.g.EU 6/20 The following measurements may be useful when detecting and compensating an outage. “Transport resource unavailable”. a suddenly increasing CQI may indicate the outage of a neighbouring eNodeB which may cause a decrease in channel interference •Failure reports: failure reports are generated by the UE after connection or handover failures and sent to eNodeB / OAM system for cause analysis. Different measurements can be requested. Suddenly changing values of measurements may indicate cell outages. CQI and others to the serving eNodeB during connection – in case of a connection failure to the serving eNodeB (e.. such as cell load or prioritised bit rates.FP7-SOCRATES.

by lowering the cell power the cell area is reduced and as a consequence load and interference caused by the cell can also be reduced. 7 7 . As part of cell outage management. This is the basis for an on- line control of the antenna characteristics and thus provides the option to modify the characteristics according to the needs of self-organisation. The consideration of Home-eNodeB for outage compensation is for further study. Second aspect. remote electrical tilt. The feasibility of this approach depends on whether it is possible to open Home- eNodeBs for access by UEs.cause UL interference to the macro-layer. these changes may be controlled as to optimize network coverage and load balancing among the remaining cells. Two aspects are currently foreseen as possible options.. these may take over some macro-layer traffic.g. Control Parameters  Physical channel parameters – Power settings (e. Steer beam pattern to coverage hole  Home-eNodeB related parameters (FFS) – Improve coverage by temporarily carrying macro layer traffic by Home-eNodeBs – Reduce interference caused by Home-eNodeBs to improve coverage of macro layer WWW. resulting in a high distance between UE and a functioning eNodeB. remote electrical tilt – RET) – Control of the coverage/capacity trade-off – Multi antenna techniques – E. “downlink reference signal”) – Control of the coverage/capacity trade-off (increase/decrease cell sizes)  Antenna parameters – Tilt. is that Home-eNodeB users – if operating in the same spectrum . if there are sufficient Home-eNodeBs in the outage area. One the one hand. azimuth (only if adjustable remotely.. During an outage. e. Modern antenna design allows influencing the antenna pattern and the orientation of the main lobe by electrical means (e. First.g.g. because the implementation details of Home-eNodeBs are not yet completely fixed. by increasing the physical channel power the coverage area of a cell can be increased (in order to compensate for outage). On the other hand.FP7-SOCRATES.EU 7/20 The power allocated to physical channels dictates the cell size. once a macro-level sector/eNodeB has failed.g. the coverage might be significantly reduced by the UEs connected to Home-eNodeBs. the footprint of the surrounding cells change as one or more cells "disappear". The changes in the footprints are coincidental. A possible approach is to turn Home eNodeBs off whenever there is an outage or at least decrease the transmission power of UE served by Home eNodeBs.. In case of a cell outage. beam forming) .

g. and (iii) whether cell outage detection and/or cell outage compensation methods are/should be developed. e.EU 8/20 The objective is to formulate a number of scenarios that are considered in the development and assessment of cell outage management methods. failing sites/cells or failing transport network links. In category (i) different subcases can be distinguished offering different potential for (primarily) cell outage detection solutions. In category (iii). (ii) whole site/sector failure (where failure is reported to OSS). Scenarios  The developed cell outage management algorithms are assessed for different scenarios. traffic and environment aspects for which useful deployment of cell outage management solutions is anticipated. which affects capacity and/or coverage. in case all S1 links to an eNodeB fail. sleeping sites/cells. broadcast information. handovers (HOs) may endure additional delays as they will be handled via S1 links. 8 8 . These scenario descriptions comprise three key elements (i) the considered outage scenario.g.FP7-SOCRATES. paging channel or user plane transmission. and (iv) other types of malfunctions. depending on the actual physical channel that fails.g. the site is entirely unfunctional (as in category (ii)). e. The type of control/signalling channel that fails influence e. whereas if an X2 link fails. the synchronisation channel. A distinction is made between four categories of outage scenarios: (i) physical channel failures causing sleeping sites/sectors. comprising – Outage scenarios: type and extent of failure – Evaluation scenarios: considered network.g. (ii) assumptions regarding network. e. (iii) transport network link failures.g. e. traffic and environment scenarios – COM mechanism: detection (COD) vs compensation (COC)  Key outage scenarios – Sleeping site/sector due to physical channel failure – COD: methods depend on failing channel – COC: similar methods as below – Whole site/sector failure – COD: no foreseen need of algorithm – COC: compensation using control parameters – Transport network link failure – COD: no foreseen need of algorithm X2 X2 – COC: X2 failure may affect HO performance and the effectiveness of ICIC WWW. reference signal. which in turn affects the possibilities for developing cell outage detection methods. reduced performance due to hardware aging. whether network/mobile-originating calls or handovers can be supported. and inter-cell interference coordination (ICIC) algorithms could no longer function. a distinction is made regarding the type of transport network link that fails.

since it may still be able to attach to a more distant cell even without compensation measures.EU 9/20 The following evaluation scenarios have been formulated for the development of cell outage compensation methods. such traffic is typically relatively far away from neighbouring sites and hence the compensation potential is limited. Priority: low. Priority: medium. Priority: medium. In a dense. e. little potential exists for compensating outage-induced coverage/capacity loss. coverage-driven network layout. •Impact of outage location: if cell outages occur at the edge of an ‘LTE island’ fewer neighbours exist to help compensate. a higher shadowing variation (also primarily depending on the propagation environment) may allow more distant cells to serve calls in an outage area. If traffic is concentrated ‘in between’ sites. •Impact of propagation aspects: the higher the path loss exponent (higher frequency bands. •Impact of user mobility: if mobility is low (high). Furthermore. the potential is larger. The perceived outage impact depends on the delay-tolerance and elasticity of the service. capacity- driven network layout.FP7-SOCRATES.g. The potential for cell outage compensation is higher. this potential is higher. For instance. •Impact of service type: the distinct elasticity and quality of service requirements of different services affect the compensation potential. the more difficult it may be to cover such users with relatively remote compensation cells in case of an outage. VoIP telephony  Impact of outage location More COC potential if a cell/site outage occurs at the inner part of an LTE island  Also study impact of: user mobility spatial traffic distribution propagation aspects UE terminal class WWW. Priority: high. 9 9 . Scenarios Evaluation scenarios  Impact of eNodeB density and load More COC potential in a dense capacity-driven network layout  Impact of service type More COC potential in an area with predominantly low-bandwidth service. few (many) users spend a relatively long (short) time in an outage area. •Impact of UE terminal class: the higher a UE’s maximum uplink transmit power (class- dependent) the lower the need for outage compensation. the priority of the evaluation scenarios is given. For outages in the core of such an ‘LTE island’. the compensation potential is larger. •Impact of eNodeB density and traffic load: in a sparse. particularly when traffic loads are low. compensation actions may be able to alleviate local outage effects to handle only low bandwidth services. more urbanised environments). Priority: high. since retuned surrounding cells may be more able to serve such a user. Priority: medium. •Impact of spatial traffic distribution: if traffic is concentrated around sites. Priority: low. Furthermore.

The execution time of a particular algorithm typically depends on the size n of the input data. between eNodeB and MME (S1).g.. processing overhead.EU 10/20 A so-called failure duration interval is associated with each failure.g.. or even exponential (an). severity indication accuracy Detection Delay True Detection False Detection Missed Detection F D D F Tfail Tdetect time F Failure occurrence D Failure detection Failure duration WWW. reduction in QoS.g.. number of measurements.g. and coverage. Let Ldetector denote the severity indication level estimated by the detection algorithm and Ltrue be the true severity indication level. the level classified if true network conditions are known. This is measured using the number of resource blocks / time unit / eNodeB scheduled for cell outage detection specific communication. 10 10 . A true detection is a detection which is reported by the cell outage detection mechanism during the failure duration interval. where each severity is characterized by multiple factors.. Processing overhead refers to the amount of processing needed to detect the outage.Ltrue|.. polynomial (na). between eNodeBs (X2). Assume that there are nL levels of severity. In contrast a false detection is reported outside the failure duration interval. i.. and can be asymptotically logarithmic (log n)..FP7-SOCRATES. e.g. An analysis of asymptotic execution time gives an insight in the processing demand of an algorithm. e. AL = |Ldetector . The following abbreviations are used: Tfail is the time instant when the failure occurred Tdetect is the time instant when the failure is detected Ndetect is the number of detections within the failure duration interval (true detection) Nfail is number of failures observed during the simulation Nfalse is the number of detections outside the failure duration interval (false detection) Signalling Overhead can be divided into two parts: •Transport network signalling overhead captures all data that is transmitted over the transport network.g. Assessment Criteria – Cell Outage Detection  Detection delay = Tdetect . and eNodeB and OSS (Itf-S) measured in either number of messages sent / time unit / eNodeB or bytes sent / time unit / eNodeB. AL = (Ldetector . Non-linear variations of AL may also be considered.e. e. e. which starts with the occurrence of a failure and ends with the elimination of the failure (e. The level estimation accuracy AL is a function of Ldetector . by repairing the error involved). e.Ltrue.Tfail  Detection probability = Ndetect/Nfail  False detection probability = Nfalse/(Nfalse + Ndetect)  Other: signalling overhead. capacity.Ltrue)2. •Radio interface signalling overhead captures the communication needed between a UE and an eNodeB in order to facilitate outage detection.

coverage and throughput performance metrics are chosen for illustration. •Throughput is the rate of successful data delivery measured in bits per second or data packets per second. and calculated as the number of bits (or packets) that are successfully delivered in a certain time period. the ratio of the number of dropped calls to the number of calls that are accepted by the network.EU 11/20 The following definitions are used: •Call blocking ratio is the ratio of the number of blocked calls to the number of calls that attempt to access the network •Call dropping ratio is the probability that an existing call is dropped before it is finished i. The margins (Margin 1 and 2) presented in the figure are used to set some allowed deviation to the final state of performance. TSS2 is set to the earliest time after which coverage is within margin 1. The convergence time of coverage is obtained by TSS2 . Different network performance metrics can be considered here. ±1%.Ti for one cell (similar definition is used for. pixels having average SINR or data rate lower than a pre-defined threshold •Ti is the outage detection time •TSS1 is the time instant of steady state for the cell throughput •TSS2 is the time instant of steady state for the cell coverage The convergence time is defined as the difference between the time the outage compensation algorithm reaches a steady state on the network performance and the time outage is detected. etc. e. Assessment Criteria – Cell Outage Compensation  Call blocking ratio. meaning that coverage can oscillate between the steady state plus or minus 1%. Throughput. The convergence time in the area under consideration is obtained as the maximum of convergence times of all the cells involved in the cell outage compensation. Call Dropping ratio. •Nbin is the number of pixels within the cell •Nbin_outage is the number of pixels in outage. Throughput) Margin 1 Coverage Margin 2 Throughput TSS1 Ti me Ti TSS2 Convergence Ti me WWW. divided by the length of that time period. i. throughput). In the figure above.e.g.  Coverage [%] = (Nbin – Nbin_outage)/Nbin  Other metrics such as convergence time per cell Network Performance (Coverage. 11 11 .e. Margin 1 can be considered e. This is measure of how fast the compensation algorithm reconfigures the network.FP7-SOCRATES.g.

EU 12/20 Every operator has its own policy for the network performance. all these goals cannot be fulfilled at the same time. coverage oriented operator vs.  All these goals cannot be fulfilled at the same time – the targets have to be weighted and/or ranked in order to provide quantitative input to an optimisation procedure. 12 12 . •providing the highest accessibility. In a cell outage situation an operator may still target at the ideal goal of •achieving the best coverage possible. For example. For cell outage management the operator wants to implement its policy into the network.g. In most cases. one operator wants to maximize its income also during the cell outage. – providing the highest accessibility. Operator Policy  In a cell outage situation an operator may still target at the ideal goal of – achieving the best coverage possible. For this. the policy definition should be modular/flexible enough to capture different operator strategies. optimisation goals and a cost function have to be defined.  The optimisation goal itself may vary depending on the operator’s policy – coverage orientation – quality orientation – capacity orientation WWW. capacity oriented operator.FP7-SOCRATES. The optimisation goal itself may vary depending on the operator’s policy. Hence. e. which is often worse for the reputation compared to a higher blocking rate.. In the first case an operator may target a high capacity sacrificing coverage in a large area yielding a low perceived coverage. and – delivering the best possible quality in the cell outage area and all surrounding cells. and •delivering the best possible quality in the cell outage area and all surrounding cells. As a consequence the targets have to be weighted and/or ranked in order to provide quantitative input to an optimisation procedure. whereas another operator may have also the long-term user satisfaction in mind.

For example. As a consequence the optimisation goals have to be defined on a cell-basis. in cells covering large areas coverage should be kept high. so that different priorities are assigned to the cells. and the normalisation procedure have still to be defined. and all cells that are not actively tuned by the COM algorithms but influenced by the network changes at all other cells. Optimisation goals may vary for different cells. The main challenge here is how to accurately estimate the position of the UE.EU 13/20 When defining the cost function it has to be decided which cells have to be taken into account. and quality. 13 13 . ) – focus on quality ( . whereas in high-capacity cells located in the same region the focus will be more on accessibility and/or quality. The second ring (outer ring) are all cells that are not actively tuned but are influenced by the network changes at all other cells. )  The cost function has to take all these different foci into account WWW. In addition to the different optimisation goals cells may have different importance. three groups of cells have to be distinguished: the cell in outage. Accessibility and quality can be assessed by key performance indicators (KPI) retrieved from counters available in the network. Normalised values are used in the cost function because it is easier to weight the normalised and dimensionless values of the different criteria against each other. geographic coordinates of the mobile position or at least an estimation of these coordinates have to be assigned to the obtained measurement reports. The coverage can be estimated based on measurement reports. The first ring are all cells that are actively tuned by the COM algorithms. into account. The cell in the centre is the cell in outage. such as coverage. too.FP7-SOCRATES. Operator Policy  Three groups of cells have to be distinguished: – the cell in outage ( ) – all cells that are actively tuned by the COM algorithm ( ) – all cells that are not actively tuned but influenced by the network changes at all other cells ( )  Cells may have different optimisation goals and different priorities – focus on coverage ( . ) – focus on accessibility ( . It has to be investigated to which degree coverage can be estimated based on measurement reports. The reference value to which the criteria are normalized. Therefore. all cells that are actively tuned by the COM algorithms. The cost function has to take all important effects. This is shown in the upper figure. This concept is shown in the lower figure in which the different layouts of the cells represent different foci. accessibility. Therefore.

e. speech. e. FTP.FP7-SOCRATES.g.EU 14 . potential to use counters from MME.g.) – IP throughput (uplink / downlink) according to the requested QCI – Direct measurement of IP traffic in eNodeB and UE. HTTP etc. through measurements from UE  Accessibility (GBR traffic. VoIP. COC Observability study  Goal of the study is to define and evaluate specific KPIs for the evaluation of cell outage compensation success  Coverage: – Describe the percentage of the area of the failed cell that is covered by modified other cells after compensation  identification of coverage gaps – For Simulator the area can be subdivided into “pixels” by an overlay grid. it is to be evaluated how far in a real system counters are available with the required frequency  Quality / Throughput (non-GBR traffic. e. and the expected downlink and uplink coverage can be calculated  open question how this can be achieved in a real system without requiring drive tests. IPTV etc. and comparison of the results with requested QCI will be difficult to be performed locally  approaches to use information about buffer sizes at eNodeB and UE currently under evaluation WWW.) – Calculation of the Session Set-up Success Rate (simple approach) – Calculation of the Establishment Success Rate that includes the requested QoS Class Identifier (QCI) – If possible using measurements / counters (session blocking ratio) available from eNodeB.g.

diversity between downlink and uplink coverage etc.)  How effective will COM be? – An important factor is the percentage of of the outage cases that can be detected and compensated automatically by a COM system – here currently no resilient data is available – Cost savings through COM can be calculated through the unnecessary site visits and drive tests in case of automated compensation.FP7-SOCRATES. especially regarding an effective outage detection and the observation of the compensation quality in real systems (for example: identification of coverage holes. balanced again the implementation efforts WWW. and the reduced network down time. minimisation of interference. Efficiency of cell outage management  Will COM actually work? – Yes – at least simulations show that with automated outage compensation. it is possible to re-establish coverage in the failure area – not necessarily with the same service quality but at least with the ability for the UE to establish connection – But: there are still several open questions.EU 15 .

conferences.EU 16/20 Next steps involve modelling various aspects of LTE and implementing simulators for cell outage compensation and coverage map estimation. The controllability study is planned to be finished by July 2009. a study will be carried out to understand the impact of antenna tilt on coverage and quality. A controllability study will be carried out in order to see to what degree an outage can be compensated (by manual means) as well as to understand the relation between control parameters and overall goal and assessment criteria of cell outage compensation. The simulator implementation is planned to be finished by July 2009.2A (finished by Oct 2009) – Algorithm development and evaluation (starting Sep 2009)  Publications and reports WWW. The questions that will be addressed in the observability study deal mostly with to what degree measurements. 16 16 . and journals. Future Work  Socrates will continue the work on cell outage detection and compensation  Next steps involve: – Simulator implementation (finished by July 2009) – Controllability studies (finished by July 2009) – Observability studies (finished by July 2009) – Intermediate report D4. Algorithms for cell outage detection and compensation will be developed using the knowledge obtained in the controllability and observability study. There will be an intermediate report finalized by Oct 2009.FP7-SOCRATES. and •estimating the coverage in the network The observability study is planned to be finished by July 2009. counters etc from the network can aid in •detecting an outage. The algorithm development and evaluation is planned to be finished by beginning 2010. Socrates will publish results in project deliverables. For example. •estimating the impact of compensation measures and the performance of the compensation function.

de R.nl M. Schmelz (Nokia Siemens Networks). Jorguseski (TNO ICT).com U.jorguseski@tno.litjens@tno. tuerke@atesio. Türke (Atesio). Neuland (TU Braunschweig).nl T. Litjens (TNO ICT). m.EU 17/20 17 . C.neuland@tu-bs.de L. Contact M. ljupco. lars.schmelz@nsn. Amirijoo (Ericsson). remco. Kürner (TU Braunschweig).FP7-SOCRATES. t. mehdi.amirijoo@ericsson.de WWW.com L.kuerner@tu-bs.