e and with a certain suc- cess probability can be guaranteed. This requirement was defined for the purpose of evalua- tion in the mMTC use case. More specifically, the connection density represents the total number of terminals that can achieve a target QoS per unit geographical area, where the tar- get QoS is to ensure that the system packet drop rate remains less than 1% at a given packet inter-arrival time and payload size. Connection density is proportional to the connection efficiency, the channel bandwidth and TRP density. Let W denote the channel bandwidth liv Introduction and Background and dTRP the TRP density (i.e., number of TRPs per square kilometer). Then connection density dconnection can be expressed as follows: dconnection adTRPW The connection efficiency a is evaluated with a small packet model. Considering the num- ber of users/devices N in the coverage area with average inter-packet time interval Tpacket> the average number of packets arrival in 1 second denoted as Npacket N/T packet. The system must guarantee that the percentage of packets in outage is less than 1%, where a packet is defined to have experienced outage, if the packet fails to be delivered to the destination within a permissible packet delay bound of 4 milliseconds. The packet delay is measured from the time when a packet arrives at the transmitter buffer to the time when it is success- fully decoded at the receiver. According to the IMT-2020 evaluation methodology [10], in order to compute the connec- tion efficiency, one must run system-level simulations by assuming certain number of devices N, packet arrival rate Npacket> number of TRPs NTRP and system bandwidth W. One then generates user traffic packets according to the small packet model specified in refer- ence [10] with packet arrival rate Npacket The system-level simulations are run again to obtain the packet outage rate. The number of devices will be iterated until the number of devices satisfying the packet outage rate of 1% is reached, which is denoted as Ncapacity: T