Language: 英語 | 日本語 || Login: ログイン | Help: ヘルプ |

1 件の該当がありました. : このページのURL : HTML

P. U-chupala, K. Ichikawa, P. Uthayopas, S. Date, and H. Abe, "Bandwidth and Latency Aware Routing Using Openflow," PRAGMA 26 Workshop, Poster, April 2014.
ID 249
分類 研究会・全国大会等
タグ aware bandwidth latency openflow routing
表題 (title) Bandwidth and Latency Aware Routing Using Openflow
表題 (英文) Bandwidth and Latency Aware Routing Using Openflow
著者名 (author) Pongsakorn U-chupala,Kohei Ichikawa,Putchong Uthayopas,Susumu Date,Hirotake Abe
英文著者名 (author) Pongsakorn U-chupala,Kohei Ichikawa,Putchong Uthayopas,Susumu Date,Hirotake Abe
キー (key) Pongsakorn U-chupala,Kohei Ichikawa,Putchong Uthayopas,Susumu Date,Hirotake Abe
刊行月 (month) 4
出版年 (year) 2014
刊行形式 (howpublished) PRAGMA 26 Workshop, Poster
URL
付加情報 (note)
注釈 (annote)
内容梗概 (abstract) Each application running on a network infrastructure may have different requirements. For example, the secure shell protocol requires as little latency as possible, while the file transfer protocol requires more bandwidth for faster file transfer. To achieve the best performance, the underlying network infrastructure should be able to take the requirements of each application into account and optimize its services accordingly. As network usually have multiple path from one point to the other, each performs differently. One path may provide higher bandwidth while the other may provide smaller latency.
With Software-defined Networking (SDN) [1], it is possible to dynamically control routes (flows) in the network. Using an SDN implementation such as OpenFlow [2], it is now possible to implement application-aware networking without being limited by traditional paradigm of network analysis, which relied on line-rate packet analysis. [3]
Overseer is our proposed solution to take advantage of the aforementioned property of network using SDN. It is a bandwidth and latency aware OpenFlow controller. It exposes API to let network monitoring tool such as Overlord [4] reports current status of the network and let application define flow preference for each connection. Overseer then use these informations to determine route for each connection accordingly.
Overseer optimizes network utilization by matching connections in the network with connection preferences requested by application through API. For general connections that do not match any specific preference, Overseer behaves like a normal switch and choose the route with smallest hop count. If connections match specific requirement such as prefer high bandwidth or prefer low latency, Overseer calculates a route to meet the requirement using information provided by monitoring tool. The route will be updated periodically as information feeded by monitoring tool changes to best reflect current status of the network.

[1] https://www.opennetworking.org/sdn-resources/sdn-definition
[2] N. McKeown and T. Anderson, “OpenFlow: enabling innovation in campus networks,” ACM SIGCOMM Comput. Commun. Rev., vol. 38, no. 2, pp. 69–74, 2008.
[3] B. Koldehofe and F. Dürr, “The power of software-defined networking: line-rate content-based routing using OpenFlow,” in MW4NG ’12 Proceedings of the 7th Workshop on Middleware for Next Generation Internet Computing, 2012, pp. 1–6.
[4] https://github.com/mekpro/overlord
論文電子ファイル 利用できません.
BiBTeXエントリ
@misc{id249,
         title = {Bandwidth and Latency Aware Routing using OpenFlow},
        author = {Pongsakorn U-chupala and Kohei Ichikawa and Putchong Uthayopas and Susumu Date and Hirotake Abe},
         month = {4},
          year = {2014},
    howpublished = {PRAGMA 26 Workshop, Poster},
}