iFUSION: Standards-based SDN Architecture for Carrier Transport Network

Contreras, Luis M.; González, O.R.; López, Vı́ctor; Fernández-Palacios, J.P.; Folgueira, Jesús

doi:10.1109/cscn.2019.8931386

Cited by 16 publications

(8 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The preferred architecture option is shown in Figure 17 . Originally proposed by Telefónica with the iFUSION brand [ 82 ], this architecture follows a hierarchical model, with specific domain controllers per technology domain (IP/MPLS, optical/DWDM and microwave/backhaul) and an overarching Software-Defined Transport Network controller (SDTN controller). This two-layer control architecture has become the reference framework for operators worldwide, as echoed in the white paper published by Telecom Infra Project’s Open Optical and Packet Transport (OOPT) project group [ 83 ].…”

Section: Tn Domainmentioning

confidence: 99%

On the Rollout of Network Slicing in Carrier Networks: A Technology Radar

Ordoñez-Lucena

Ameigeiras

Contreras

et al. 2021

Sensors

View full text Add to dashboard Cite

Network slicing is a powerful paradigm for network operators to support use cases with widely diverse requirements atop a common infrastructure. As 5G standards are completed, and commercial solutions mature, operators need to start thinking about how to integrate network slicing capabilities in their assets, so that customer-facing solutions can be made available in their portfolio. This integration is, however, not an easy task, due to the heterogeneity of assets that typically exist in carrier networks. In this regard, 5G commercial networks may consist of a number of domains, each with a different technological pace, and built out of products from multiple vendors, including legacy network devices and functions. These multi-technology, multi-vendor and brownfield features constitute a challenge for the operator, which is required to deploy and operate slices across all these domains in order to satisfy the end-to-end nature of the services hosted by these slices. In this context, the only realistic option for operators is to introduce slicing capabilities progressively, following a phased approach in their roll-out. The purpose of this paper is to precisely help designing this kind of plan, by means of a technology radar. The radar identifies a set of solutions enabling network slicing on the individual domains, and classifies these solutions into four rings, each corresponding to a different timeline: (i) as-is ring, covering today’s slicing solutions; (ii) deploy ring, corresponding to solutions available in the short term; (iii) test ring, considering medium-term solutions; and (iv) explore ring, with solutions expected in the long run. This classification is done based on the technical availability of the solutions, together with the foreseen market demands. The value of this radar lies in its ability to provide a complete view of the slicing landscape with one single snapshot, by linking solutions to information that operators may use for decision making in their individual go-to-market strategies.

show abstract

Section: Tn Domainmentioning

confidence: 99%

On the Rollout of Network Slicing in Carrier Networks: A Technology Radar

Ordoñez-Lucena

Ameigeiras

Contreras

et al. 2021

Sensors

View full text Add to dashboard Cite

show abstract

“…The idea leverages on the concept of Wide-area Infrastructure Manager (WIM) as defined by the ETSI NFV architecture as the element devoted to manage virtualize capabilities in the WAN [17]. When referring to slices, such an entity could be associated to a Transport Slice Controller, as defined in [18] either complementing or being part of an overarching SDN transport network control environment as in [19,20].…”

Section: Programmable Control Of Transport Connectivitymentioning

confidence: 99%

Architecture for integrating vertical customer’s programmability control of network functions and connectivity in a slice-as-a-service schema

Contreras

Barguil

Vilalta

et al. 2021

J Wireless Com Network

View full text Add to dashboard Cite

Network slicing will permit offering to vertical customers tailored end-to-end logical networks in an on-demand fashion, on top of a common telecom infrastructure, achieving a Slices-as-a-Service (SlaaS) business model. This is possible due to the progressive introduction of network softwarization techniques, such as programmability and virtualization, into existing operational networks, enabling dynamic and flexible provision of slices. Those vertical customers could require the control not only of the network functions composing the end-to-end service, but also of the connectivity among them, e.g., for influencing the paths for steering traffic among function instances. However, this can be problematic since decisions from one vertical customer can collide with decisions from others. One aspect not yet sufficiently investigated is how to permit vertical customers to jointly control the service functions and the underlay connectivity, in such a way that could operate the allocated slice as if it was actually a dedicated network entirely for them. This paper explores some architectural proposition in this respect illustrated with some potential use cases and it provides an example of the provision of SlaaS for a vertical customer.

show abstract

“…The Network Slice Controller (NSC) realizes a transport network slice in the underlying transport infrastructure, maintains and monitors the state of its resources. The NSC will delegate on SDN Domain controllers [6] to configure the network resources. The NSC receives a transport network slice request from the Operation Support System and Business Support System (OSS/BSS).…”

Section: Introductionmentioning

confidence: 99%