Search

Although there is consensus that software defined networking and network functions virtualization overhaul service provisioning and deployment, the community still lacks a definite answer on how carrier-grade operations praxis needs to evolve. This article presents what lies beyond the first evolutionary steps in network management, identifies the challenges in service verification, observability, and troubleshooting, and explains how to address them using our Service Provider DevOps (SP-DevOps) framework. We compendiously cover the entire process from design goals to tool realization and employ an elastic version of an industry-standard use case to show how on-the-fly verification, software-defined monitoring, and automated troubleshooting of services reduce the cost of fault management actions. We assess SP-DevOps with respect to key attributes of software-defined telecommunication infrastructures both qualitatively and quantitatively, and demonstrate that SP-DevOps paves the way toward carrier-grade operations and management in the network virtualization era., Comment: Pre-print of article published in IEEE Communications Magazine, vol. 55, no. 1, pp. 204-211, January 2017

This report presents the results of the UNIFY Service Provider DevOps activities. First, we present the final definition and assessment of the concept. SP-DevOps is realized by a combination of various functional components facilitating integrated service verification, efficient and programmable observability, and automated troubleshooting processes. Our assessment shows that SP-DevOps can help providers to reach a medium level of DevOps maturity and allows significant reduction in OPEX. Second, we focus on the evaluation of the proposed SP-DevOps components. The set of tools proposed supports ops and devs across all stages, with a focus on the deployment, operation and debugging phases, and allows to activate automated processes for operating NFV environments. Finally, we present use-cases and our demonstrators for selected process implementions, which allowed the functional validation of SP-DevOps., Comment: This is the public deliverable D4.3 of the EU FP7 UNIFY project (ICT-619609) - "Updated concept and evaluation results for SP-DevOps". Original Deliverable published at https://www.fp7-unify.eu/index.php/results.html#Deliverables

This report provides an understanding of how the UNIFY Service Provider (SP)-DevOps concept can be applied and integrated with a combined cloud and transport network NFV architecture. Specifically, the report contains technical descriptions of a set of novel SP-DevOps tools and support functions that facilitate observability, troubleshooting, verification, and VNF development processes. The tools and support functions are described in detail together with their architectural mapping, giving a wider understanding of the SP-DevOps concept as a whole, and how SP-DevOps tools can be used for supporting orchestration and programmability in the UNIFY NFV framework. The concept is further exemplified in a case study for deployment and scaling of an Elastic Firewall., Comment: This is the public deliverable D4.2 of the EU FP7 UNIFY project (ICT-619609) - "Proposal for SP-DevOps network capabilities and tools". Original Deliverable published at https://www.fp7-unify.eu/files/fp7-unify-eu-docs/UNIFY-WP4-D4.2%20Proposal%20for%20SP-DevOps%20network%20capabilities%20and%20tools.pdf

Network Service Chaining (NSC) is a service deployment concept that promises increased flexibility and cost efficiency for future carrier networks. NSC has received considerable attention in the standardization and research communities lately. However, NSC is largely undefined in the peer-reviewed literature. In fact, a literature review reveals that the role of NSC enabling technologies is up for discussion, and so are the key research challenges lying ahead. This paper addresses these topics by motivating our research interest towards advanced dynamic NSC and detailing the main aspects to be considered in the context of carrier-grade telecommunication networks. We present design considerations and system requirements alongside use cases that illustrate the advantages of adopting NSC. We detail prominent research challenges during the typical lifecycle of a network service chain in an operational telecommunications network, including service chain description, programming, deployment, and debugging, and summarize our security considerations. We conclude this paper with an outlook on future work in this area., Comment: Presented at the 2013 "Software Defined Networking for Future Networks and Services" (SDN4FNS) conference in Trento, Italy (http://sites.ieee.org/sdn4fns/). Will be published in the SDN4FNS proceedings at IEEE

Segment retransmissions are an essential tool in assuring reliable end-to-end communication in the Internet. Their crucial role in TCP design and operation has been studied extensively, in particular with respect to identifying non-conformant, buggy, or underperforming behaviour. However, TCP segment retransmissions are often overlooked when examining and analyzing large traffic traces. In fact, some have come to believe that retransmissions are a rare oddity, characteristically associated with faulty network paths, which, typically, tend to disappear as networking technology advances and link capacities grow. We find that this may be far from the reality experienced by TCP flows. We quantify aggregate TCP segment retransmission rates using publicly available network traces from six passive monitoring points attached to the egress gateways at large sites. In virtually half of the traces examined we observed aggregate TCP retransmission rates exceeding 1%, and of these, about half again had retransmission rates exceeding 2%. Even for sites with low utilization and high capacity gateway links, retransmission rates of 1%, and sometimes higher, were not uncommon. Our results complement, extend and bring up to date partial and incomplete results in previous work, and show that TCP retransmissions continue to constitute a non-negligible percentage of the overall traffic, despite significant advances across the board in telecommunications technologies and network protocols. The results presented are pertinent to end-to-end protocol designers and evaluators as they provide a range of "realistic" scenarios under which, and a "marker" against which, simulation studies can be configured and calibrated, and future protocols evaluated.

Forthcoming wireless communications will be characterized by the ubiquity of multiaccess. Despite the inherently increased complexity, end-users should be able to take advantage of the most suitable access network. Thus, access selection in an environment with different overlapping radio technologies is of central interest and an architecture is needed that performs equally well on single- and multi-operator scenarios, considers several parameters, and respects the principle of layering. In this paper, we introduce the Ambient Networks heterogeneous access selection architecture explaining how it meets such requirements. We present the essential architectural components and explain their interactions. We illustrate how the proposed architecture works in practice and discuss recent results form our prototype-based validation., Comment: Proc. First Ambient Networks Workshop on Mobility, Multiaccess, and Network Management (M2NM), Sydney, Australia, October 2007, pp. 49-54

Solutions for mobility management in wireless networks have been investigated and proposed in various research projects and standardization bodies. With the continuing deployment of different access networks, the wider range of applications tailored for a mobile environment, and a larger diversity of wireless end systems, it emerged that a single mobility protocol (such as Mobile IP) is not sufficient to handle the different requirements adequately. Thus a solution is needed to manage multiple mobility protocols in end systems and network nodes, to detect and select the required protocols, versions and optional features, and enable control on running daemons. For this purpose a mobility toolbox has been developed as part of the EU funded Ambient Networks project. This paper describes this modular management approach and illustrates the additional benefits a mobility protocol can gain by using state transfer as an example., Comment: Proc. First Ambient Networks Workshop on Mobility, Multiaccess, and Network Management (M2NM), Sydney, Australia, October 2007, pp. 73-78

In recent years several wireless communication standards have been developed and more are expected, each with different scope in terms of spatial coverage, radio access capabilities, and mobility support. Heterogeneous networks combine multiple of these radio interfaces both in network infrastructure and in user equipment which requires a new multi-radio framework, enabling mobility and handover management for multiple RATs. The use of heterogeneous networks can capitalize on the overlapping coverage and allow user devices to take advantage of the fact that there are multiple radio interfaces. This paper presents the functional architecture for such a framework and proposes a generic signaling exchange applicable to a range of different handover management protocols that enables seamless mobility. The interworking of radio resource management, access selection and mobility management is defined in a generic and modular way, which is extensible for future protocols and standards., Comment: Proc. First Ambient Networks Workshop on Mobility, Multiaccess, and Network Management (M2NM), Sydney, Australia, October 2007, pp. 31-36