ng UE attaches until the success rate drops below an acceptable KPI threshold. In order to ensure that the attached UEs are not disconnected from the sector because of inactivity, maintain a steady UL/DL data rate for each of these attached UEs. Note the number of attached UEs after which the attach success rate starts to drop below an acceptable limit. This would be used as the maximum number of attached UEs per sector. Try attaches with different rates (30 attaches/second, 50 attaches/second) and also under different channel fading models such as the EPA, EVA, and ETU models. User Plane Overload and Capacity Testing User plane overload and capacity testing will deal mainly with data throughput capacity of the eNodeB. User plane overload testing will involve tests like: Maximum throughput that can be supported by a sector for MIMO users under ideal radio conditions. Maximum throughput that can be supported by an eNodeB for MIMO users under ideal radio conditions. Number of users that can be scheduled by a cell for each transmission time interval (TTI). Tests to verify the GBR share/sector. Tests to verify the n-GBR share/sector. Apart from these tests, the following tests also need to be performed under overload and capacity testing category: Memory consumption tests for different loads (no UE attaches, 32 UE attaches, 64 UE attaches, etc.). Computer processing unit (CPU) load consumption tests. Configuration of thresholds 1, 2, 3, and 4. Tests to load the eNodeB or sector to exceed threshold 1 and verify the actions that are triggered by eNodeB/sector to bring the CPU load below the threshold. Tests to load the eNodeB/sector to exceed threshold 2 and verify the actions that are triggered by eNodeB/sector to bring the CPU load below the threshold. Tests to load the eNodeB/sector to exceed threshold 3 and verify the actions that are triggered by eNodeB/sector to bring the CPU load below the threshold. Tests to load the eNodeB/sector to exceed threshold 4 and verify the actions that are triggered by eNodeB/sector 