ds are being already developed, for example, by the oneM2M Partnership Project (oneM2M), to overcome these issues. OneM2M-based technology allows among other things a proper scheduling of IoT application data transmissions, to allow a battery-efficient communication. That avoids adverse effects on the cellular networks (oneM2M Technical Specification TS-0001). However, until oneM2M-developed (or similar) technologies gain sufficient market penetration, there will be always a risk of unintentional denial of service (DoS) from IoT applications, which may have been developed without taking the specifics of cellular connectivity into account. 7.3.2.2 Compute Resources for Edge Computing Services Edge computing is expected to play a major role in 5G deployments; for example, to ensure end-to-end low latency. For more details about edge in general and MEC in particular, refer to Section 6.4. NR radio interface can provide an extremely low one-way latency of 0.5 ms. However, besides latency introduced by the air interface on the mile," latency introduced owing to data transmission over the backhaul links (as also discussed in Section 6.4) and through the core network to the other peer communication partner (e.g. an application running in a data center) contributes considerably to the end-to-end delay/latency budget. The simple back-of-the-envelope calculation provided below illustrates the issue. Using the simple formula S = C t,where: C represents the speed of light C = 299 792 t represents the time. If 1 ms round-trip end-to-end latency is required (which is often assumed in 5G URLLC applications), that is t=1 ms, then this translates to a distance of: S = 299 792 458 x 10 - = 299 792 458 m = 299.8 km 22 300 km In other words, once a round-trip delay of less than 1 ms is required, the distance between both communication partners must be less than Smax = 300/2 = 150 km, to allow ping times of 1 ms. Assuming base stations are connected via fiber, an additional media delay should be taken into account. That is, just ~67%