ocessing time. Two device capa- bilities are defined, capability 1 and capability 2. The former corresponds to a baseline mode for the capability of the minimum PDSCH/PUSCH processing time, while the latter is an aggressive mode which requires a tighter processing schedule. All UEs are required to fulfill at least the baseline mode. A UE may also report that it is capable of a more aggressive processing timeline. The impact of the more aggressive processing capability is similar to the impact of a shorter slot duration. The design involves a balance among the clock rate, the power consumption, the parallel processing capability, the chip area/cost, and SO on. Either a higher energy demand, or a higher device cost for components of hardware, memory, and processors is needed, or more sophisticated software programming is needed to handle the scheduling of concurrent jobs. 13.3.1.5 Preemption Indication Assume, under high traffic load, that all downlink time-frequency resources are occupied as a result of which the network is unable to accommodate an incoming time-critical service. NR supports the functionality of re-allocating the resource originally scheduled to a first UE1 to another UE2 with a tight latency requirement. To do so, a preemption indication is sent to UE1 notifying some of its resources have been preempted and used for other purposes. In this way, for UE2, the latency due to scheduling delay can be saved. The network and UE1 should take further action to compensate for the resource pre- emption. In the example above, UE1 has to perform some soft buffer handling. For instance, the part of the soft buffer which corresponds to the preempted resource should be flushed because the data intended to UE2 carried in the preempted resource have corrupted the information stored in the soft buffer. This soft buffer handling should be completed before the arrival of the associated retransmission of the preemption indica- tion; otherwise, the retransmission is wasted. For PDSCH with tight HARQ timing, this is dif