etainability KPIs are RRC abnormal release rate, E-RAB abnormal release rate, E-RAB release success rate, UE context release success rate, and average E-RAB number per active user. CHAPTER 1 NETWORK PLANNING In order to test retainability KPI cases, for instance, the UE context release success rate, these considerations will be required: Multiple UEs needs to initiate the attach procedure followed by a constant UL/DL data transfer procedure. For a fraction of these RRC_CONNECTED UEs, eNodeB should trigger the UE context release procedure due to user inactivity. For another fraction of the RRC_CONNECTED UEs, MME should initiate UE context release for various reasons (i.e., successful handover completion, handover cancellation completion, release of old UE-associated S1 connection, etc.). In order to maintain a steady number of attached users or sectors, new attached procedures must be maintained within the cell at the same rate at which UE context release requests or completions are maintained. Integrity of KPI Testing Examples for integrity KPIs are UL peak user throughput, DL peak user throughput, DL Internet provider (IP) latency, DL transport BLER, UL transport BLER, roundtrip time (RTT) latency, RTT packet loss (ping), among others. In order to test integrity KPI cases, for instance, DL peak user throughput, these considerations will be required: A single UE should perform the attachment and should have at least one digital radio broadcasting (DRB) for non-guaranteed bit rate (GBR) data and one DRB for GBR data in the DL as well as UL direction for throughput tests. The aggregate maximum bit rate (AMBR) and the GBR values of the UE RABs should be sufficiently high (equal to or more than the cell throughput) and the application server that is connected to the evolved packet core (EPC) should be able to pump data for these RABs with a steady flow, wherein there is sufficient data scheduled for both of these RABs. The UE reported CQI should be maintained very high (around 15) to measure the peak throughput in DL