 Others including voice over Internet protocol (VoIP) Total UE simulation will be triggered using a performance simulation tool and channel conditions along with UE speed. Distribution can also be done using either the performance simulation tool or a channel emulator tool. The eNodeB will be connected to the element management system (EMS) where the KPIs can be observed over the course of testing. Overload and Capacity Testing Overload and capacity testing can broadly be classified into two categories: Control plane overload and capacity testing. User plane overload and capacity testing. Control Plane Overload and Capacity Testing Control plane capacity and overload testing deal mainly with determining the signaling capacity of the eNodeB and estimating the signaling load. Control plane overload and capacity testing will involve tests like: Maximum number of RRC connected UEs that can be supported by a sector without compromising the KPIs. Maximum number of RRC connected UEs that can be supported by an eNodeB without compromising on the KPIs. Maximum number of E-RABs (default plus dedicated) that can be supported by a sector without compromising the KPIs. Maximum number of E-RABs (default plus dedicated) that can be supported by an eNodeB without compromising the KPIs. Number of simultaneous attaches procedures (number of attach requests per second) that can be supported by the sector without compromising the KPI requirements. Number of incoming handovers that can be supported by the sector without compromising the KPIs. CHAPTER 1 NETWORK PLANNING For control plane capacity testing, a test setup similar to test setup 2 is essential. For example, to test the maximum number of attached UEs per sector, the following steps will be required: For the sector running on a no-load condition, perform a steady rate of UE attaches in steps of 32 attaches, 64 attaches, 96 attaches, 128 attaches, 156 attaches, 200 attaches, and SO forth. Observe the success rate for KPIs and monitor the drop in success rate. Continue performi