. On the context of OpenFlow networks, the FlowVisor has emerged as a tool to enable the network virtualization, creating an environment for running multiple concurrent and independent experiments. However, this solution still has some limitations, such as the definition of mechanisms to allocate resources to different virtual networks. Although newer versions of the tool allow the queue assignment network slice, to provide resource control among them, device configurations are on the dependency of external tools. Therefore, this article aims to propose a solution to extend the FlowVisor functionality, creating a structure to allow traffic control configuration parameters in the network device, to ensure resource isolation and interference mitigation between the different virtual networks.

Packet scheduling is essential to properly support applications on Software-Defined Networking (SDN) model. However, on OpenFlow/SDN, QoS is only performed with bandwidth guarantees and by a well-known FIFO scheduling. Facing this limitation, this paper presents the QoSFlow proposal, which controls multiple packet schedulers of Linux kernel and improve the flexibility of QoS control. The paper assesses QoSFlow performance, by analysing response time of packet scheduler operations running on datapath level, maximum bandwidth capacity, hardware resource utilization rate, bandwidth isolation and QoE. Our outcomes show an increase more than 48% on PSNR value of QoE by using SFQ scheduling.

The increase in complexity of computer networks and their services have boosted the development of standardizations, models, and solutions for network management over the years. Lately, the Distributed Management Task Force (DMTF) defined the Common Information Model (CIM) for describing computational entities and businesses on the Internet. This paper proposes an extension of the CIM for Software-Defined Networking (SDN) by adding new elements (Controllers, Apps, Slices and others) to improve the system management performance. Furthermore, we define a metamodel to help the process of creating and understanding the proposed model. The proposal was validated by creating a script that generates the FlowVisor configuration file using the network model as input and using Object Constraint Language (OCL) to find inconsistencies in the network.

Currently, there is a philosophical problem that arises between the real need for current support to OpenFlow and legacy network infrastructure. Among them, the legacy networking has not been compatible with OpenFlow network, and for that, it needs to be replaced or a few cases upgraded, as a consequence there are additional spending with new equipment OpenFlow-based. This paper introduces a proposal of hybrid SDN solution based on OpenFlow protocol and called of LegacyFlow, which is able to control Legacy equipment (non-OpenFlow) through OpenFlow protocol 1.0. Results show that it is possible used the LegacyFlow together with OpenFlow switches keeping a good performance time with OpenFlow application.

The OpenFlow technology enables the creation of a programmable layer over the control-plane of a network, in this way dictating the data-plane forwarding behaviour through the use of applications plugged to a network controller. Dynamic Circuit Network is an architecture that permits the scheduling of network resources on virtual circuits, such as bandwidth, over multiple domains with heterogeneous technologies. Recently, researches were conducted in order to integrate both technologies so that dynamic circuits can be dynamically provisioned over OpenFlow domains. The objective of this work is to propose an architecture that enables such provision, maintaining the QoS requisites of a DCN architecture.