 for the user under ideal conditions. UE can be moved to the cell center, cell edge, and SO forth, and throughputs can be measured accordingly for each of these conditions. The steps can be repeated for different propagation models (pedestrian fading, vehicular speed, etc.). Availability of KPI Testing For testing availability of the eNodeB, various tests can be run on the eNodeB continuously and the average downtime of eNodeB should be noted using the following equation: Total testing time - eNodeB down time = eNodeB available time. No special testing is specified to verify the availability KPI, instead the eNodeB downtime should be noted while performing all other performance testing and the KPI value should be derived. CHAPTER 1 NETWORK PLANNING Mobility of KPI Testing Mobility KPI testing targets to verify the system performance during various handovers. Examples for mobility KPIs are intra-eNodeB handover success rate, intrafrequency handover success rate, interfrequency handover success rate, X2 handover success rate, S1 handover success rate, among others. In most deployments, the handover is triggered based on the A3 event reported by the UE incase of intra- or interfrequency handover and B1 or B2 event reported by UE in case of interradio technology transfer (RAT) handover. Events A3 and B1 are most often used to refer to a condition where the neighbor cell signal strength measurement is offset better than the serving cell signal strength. In order to test mobility KPI cases, for instance, the intra-eNodeB handover success rate, these considerations will be required: Multiple UEs for multiple sectors are required to perform UE's attach procedure followed by a constant UL/DL data transfer procedure for each of these UEs. UE mobility should be enabled with different speeds so that the event A3/B1 is triggered for the UEs and handovers to the neighboring sectors are initiated. For a given sector under test, it is required to maintain a steady rate of outgoing handovers and an equal rate of incoming handover