## 4 Proposed Orchestrator
### Description of the Architecture
#### 4.1.1 Multi-Provider Service Leader Plane  
It performs service orchestration and management across federated resources from successfully admitted slice requests. In this article, we propose a set of functional blocks that integrate the physical and logical infrastructure of mobile operators and SPs, aligned with a horizontal orchestration service. To that end, network functions have been proposed that implement 5G network slicing using Fog/Edge and cloud computing (Figure 4). In general, integration with the orchestra \begin{table}
\begin{tabular}{l l} \hline \hline
**Proposed Orchestrator Architecture** & **Conceptual Model** \\ \hline Intelligent Service Leader & Application Requirements \\ Mobility Manager & Application Requirements \\ Multi-Provider Network Slice Functions & Infrastructure Layer, Network Function Layer \\ Multi-Provider Network Slice Selector & Application Requirements \\ Multi-Provider Slice Manager & Application Requirements, Network Slice Definition, \\ Multi-Tenants & Services \\ Physical Resources & Infrastructure Layer \\ Service Manager & Network Slice Definition, Network Slice Negotiation \\ Slice Life-Cycle Manager & Network Slice Definition, Network Slice Negotiation \\ Specific-Provider Connectivity Control & Network Slice Definition, Network Slice Negotiation \\ Specific-Provider NFV-MANO & Network Slice Definition, Network Slice Negotiation \\ Virtual Resources & Network Function Layer \\ Virtualization Layer & Network Function Layer \\ United Connectivity Resource Manager & Network Slice Definition \\ United Distributed Cloud Mediator & Network Slice Negotiation \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Mapping between components and modules from the Orchestrator architecture to the conceptual model. Figure 4: Proposed Multi-Provider Orchestrator architecture. tion service takes place based on the perception, definition, selection, or creation of the best slice in a given coverage area. In this case, the slice selection service using computational intelligence techniques and, using SDN-based traffic management, selects the slice that has the best requirements (QoS parameters) to meet a given user. Alternatively, from the negotiation of an SLA, it defines the necessary metrics for the slice, serving as input to the _Mobility Manager_ module. The _Mobility Manager_, in turn, makes use of traffic prediction techniques and consults a database of available network services (_BD Services/Network_ module), which act as a kind of catalog that shows the health of the network in real-time, using monitoring tools (e.g., Prometheus ecosystem ([[https://prometheus.io/docs/introduction/overview/](https://prometheus.io/docs/introduction/overview/)]([https://prometheus.io/docs/introduction/overview/](https://prometheus.io/docs/introduction/overview/)) (accessed on 7 December 2021)). It then checks the network panorama and executes the mobile operator's handover to satisfy the requested requirements. However, for the handover decision to take place efficiently, the prediction and heuristics information provided by the _Intelligent Service Leader_ module is used, which contains a set of data analytics algorithms and techniques to make traffic prediction, that is, to ensure that the user has the SLA met while avoiding the _ping-pong_ effect, in which the user is switched between the slices available in short periods, thus reducing their QoE [96]. The signaling performed by the _Mobility Manager_ module is then received by the _Multi-Provider Slice Manager_ module, which sends the resource allocation model, verifying the connectivity services and computational resource capacity that should be made available. This request (e.g., TOSCA or YAML template) is then sent for provisioning in the _E2E Network Slice Orchestration Plane_ block, which will be detailed later. It is important to note that unlike the 5G NORMA project [64], our slice selection service is shared between the edge and the cloud.