tep RACH 2-step RACH Figure 15.10 Regular RACH and 2-step RACH operation. 15 5G Phase 2 and Beyond The Release 16 looked at the power saving aspects while taking into account the resulting impact on latency and 5G network performance in general. The findings from the study are reflected in [12]. The methods agreed to be specified in Release 16, include triggering a MAC entity to "wake up" to monitor PDCCH when receiving power saving signal/channel. 15.2.10 Lightweight Mobile Broadband with NR-Light The work in Release 15 did not address 5G-based IoT operation other than the URLLC use case, which was then extended in Release 16 to more demanding URLLC use cases. The Release 16 step (as discussed in Chapter 5) was to enable connecting NB-IoT and eMTC (LTE-M) to 5G Core, which, from the radio perspective can be operated side by side with 5G operation as the subcarrier spacings are compatible (in-band operation with 5G), this being in place from 5G Release 15 already. Legacy devices, however, can- not connect to 5G Core (unless they are upgraded to support 5G access signaling), and thus the practical deployments are foreseen to stay with EPC core for several years to come with NB-IoT and eMTC. The next step is to address the use of 5G for IoT purposes other than IIoT, which has not yet been formally included as part of the 3GPP work program. The general view agreed upon in 3GPP is that there is no intention at the moment to define a very-low-cost 5G IoT modem that would be optimized for exactly the same use cases as NB-IoT and eMTC, like the metering applications. It has been suggested, however, that a beginning can be made by initiating the definition of a more capable 5G modem (than NB-IoT or eMTC) UE type which would deliver data rates on the order of 10-100 of Mbps and would have reduced capabilities compared to full-blown 5G modems with a capabil- ity of up to 2 Gbps. One of the example use cases raised in 3GPP is the surveillance camera [13], which would not need the 100 MHz RF bandwidth capability but could be