Scalable Network Architecture for Flow-Based Traffic Control

Abstract

Many control schemes have been proposed for flow‐level traffic control. However, flow‐level traffic control is implemented only in limited areas such as traffic monitoring and traffic control at edge nodes. No clear solution for end‐to‐end architecture has been proposed. Scalability and the lack of a business model are major problems for deploying end‐to‐end flow‐level control architecture. This paper introduces an end‐to‐end transport architecture and a scalable control mechanism to support the various flow‐level QoS requests from applications.

An architecture for internet inter-domain interconnections and bandwidth trading towards effective NGN deployment

“…For example, [16] demonstrates so-called "Exact Bandwidth Distribution Scheme (X-BDS)" for a dynamic and fair distribution of available bandwidth among individual flows. One can find different solution approaches to flow management by utilizing the market-based models; for example, refer to [44] and [45].…”

Evaluation of OpenFlow's Enhancements

“…Grouping sequence of packets into flows is very reasonable, since that different services (applications) on the Internet have different characteristics and require different levels of support by the network, and thus flows can be used to group communications according to the type of service they belong to and then apply some rules for each group. As an example flows are used in [9] to assure different levels of Quality of Service (QoS) for different types of applications depending on the application's needs, while in [10] flows are used as a mean to apply security policies.…”