ality. Production data is not allowed to go out of the industrial premises for data protection reasons. This removes the option of (remote) cloud processing and reliance on public networks. Latency. Public RAN latency is an order of magnitude higher than private network latency if public networks are optimized toward eMBB deployment and centralized compute. Even in an optimal (lightly loaded) environment, public network RAN latency alone is order of magnitude (10 ms). RAN performance. When relying on a public network, it is difficult to accommodate for guaranteed operational Quality of Service in every location. Operator owned small cells could be used to improve RAN performance but are intrusive on the IT infrastructure in the industrial environment. Cost and (small) scale targets of industrial deployment are achieved by implementing SDN for control plane and core network functions. This removes the need to rely on high- end networking equipment that is designed for use by the mobile network operators. The 5G RAN itself can be physically implemented/partitioned in different ways. For example: Integrated small cells where RF, Physical Layer, and 3GPP Medium Access Control (MAC)/Radio Link Control (RLC) layers are colocated into a single (small-cell) unit, connecting over sub-1 Gbps links to the centralized unit that takes care of 3GPP protocol termination, cell site routing, and connectivity to edge compute/core network. Distributed small cells where RF and lower Physical Layer are separated from the upper Physical layer and MAC/RLC functionality. In this case, connectivity between the two is provided by higher capacity Ethernet, typically dedicated 10/25GbE. There are tradeoffs in cost, power, programmability/flexibility, and other factors between these two implementation options. Specific URLLC protocol level features can be more easily implemented in an integrated small-cell environment (smaller slot times, low HARQ turnaround times) or in a distributed small cell (CoMP, interference management). The choice be