No abstract

In recent years, significant work has been completed on traffic engineering enhancements to the generalized multiprotocol label switching protocol suite [1][2][3]. As a next step, reproducing the current trend of switching layers' integration happening in the data plane, network control is foreseen to go beyond the traditional per layer approach and tend toward an integrated model [4,5]. In these multilayer environments, a single GMPLS control plane drives various distinct switching layers at the same time and as a coherent whole, taking benefit from the "common" property of GMPLS. Beyond this application of supporting network control across different technologies, in this article we catalog the unified traffic engineering paradigms, discuss their applicability, and present their enforcement techniques. Furthermore, we show that the common GMPLS concept has the advantage of low operational complexity, and enables unified TE capabilities such as efficient network resource usage and rapid service provisioning.

In an increasingly interconnected world, new opportunities for telecom-based services are emerging. Innovative applications profit from cloud versatility and scalability, but require a platform to combine the optimized 5G network fabric with the advancements in the domain of cloud computing, Software Defined Networking (SDN) and Network Function Virtualization (NFV). In this multi-domain context, we find that available service platforms are lagging, because they tend to be tightly coupled to a constrained set of technologies. In practice, we need the flexibility to deploy different microservices over a heterogeneous range of infrastructure types, aggregating various virtualization, orchestration and control mechanisms. Moreover, the integration of the service requires collaboration among a wide mix of actors (e.g. developers, operators, hardware/software vendors, infrastructure/service providers or vertical integrators). We propose a next-generation Platform-asa-Service (NGPaaS), devised as a modular framework for the development and operation of network services, while targeting a high degree of both customization and automation. The presented architecture is built around a workflow-based orchestrator which coordinates custom-built tasks across a tailored group of specialized infrastructure or platforms. We also explain how NGPaaS enhances DevOps-principles, to achieve a more efficient integration process across the many isolated administrative domains in the modern telco landscape. Keywords-NFV; SDN; 5G; PaaS Architecture; DevOps; Devfor-Operationshigh modularity/microservice based high level of virtualization implementation characteristics Capex + Lock-in (vendor, technology) Time-to-market testing, communication overhead cost (dev, deployment, opex)optimal PaaS configuration default PaaS features monolithic, hardware-based Fig. 1. The PaaS architecture is microservice-based, where the right design achieves the optimal trade-off.

No abstract

No abstract