## 3 Integration of 5G NPN Deployment Options and Edge Computing Scenarios
### Standardone NPN with Private, On-Premises Edge  
As shown in Figure 2, in this scenario, all of the user plane and control plane functions required to operate the NPN are physically located on factory premises. The edge deployment that hosts the latency-critical industry applications (e.g., cloud-based mobile robot control) is also on-premises, and dedicated infrastructure is used for the edge. Due to the totally separated infrastructure for the edge and SNPN domains, this scenario ensures the highest isolation for the industry applications running at the edge.  
\begin{table}
\begin{tabular}{c c} \hline \hline
**NPN Deployment Options** & **Possible Edge Computing Deployment** \\ \hline Standalone NPN & On-premises—Standalone edge \\ Standalone NPN & On-premises—Federated edge \\ Standalone NPN & On-premises—Integrated edge and central \\ Standalone NPN & cloud premises \\ Shared NPN infrastructure & On-premises edge \\ PNI-NPN with shared RAN and core & On-premises edge \\ control plane & Telco/3 rd party edge \\ PNI-NPN hosted by the public network & On-premises edge \\ \hline \hline \end{tabular}
\end{table}
Table 1: Overview of the NPN deployment options and edge computing setups.  
Figure 2: Standalone NPN with factory premises edge.  
The industrial network domain, which comprises the SNPN and wired network segments, connects the industrial end devices to the edge computing domain. The on-premises edge enables a wide range of deployment alternatives:  
* A single, standalone data center could be deployed in the factory premises;
* Several edge (standalone) data centers could be deployed in different factory buildings, realizing a distributed edge infrastructure for improved robustness, and each data center is managed as a separate edge computing cluster;
* Another operation mode is to handle the multiple clusters in a federated way;
* Beside the on-premises edge data center(s), a central (public or private) cloud premises is also used for hosting industry applications/application functions with relaxed requirements (e.g., latency).  
The private, on-premises edge deployment enables lots of flexibility for the edge owner (typically the industrial party in this scenario or a third-party integrator); however, the edge owner is responsible for the handling of the full cloud stack, including:  
* The infrastructure layer (e.g., compute and storage resources, as well as cloud networking) has to provide low latency (e.g., near-real-time) and high availability capabilities (support the redundant deployment of application instances)
* Maintenance of the virtualization platform, such as container runtime environment (e.g., Docker [28]) or virtual machine (VM)-based ecosystem;
* Maintenance of the cloud orchestration system, e.g., proper installation and management of Kubernetes components (e.g., provide the redundancy of the Kubernetes control plane, Kubernetes cluster configuration, etc.)  
Depending on the stakeholder roles, the above tasks could be handled by the industrial party (self-managed deployment), a third-party integrator, or even the MNO. In the two latter cases, the industrial party should only perform the application deployment and life-cycle management, while in the first case, the industrial party is responsible for the proper operation of the full cloud stack. The on-premises edge scenario enables numerous deployment options; the most specific ones are discussed in the next part of the section.