Seongbok Baik, Younggil Lim, Jongwoo Kim, Youngwoo Lee
{"title":"SDN架构中的自适应流量监控","authors":"Seongbok Baik, Younggil Lim, Jongwoo Kim, Youngwoo Lee","doi":"10.1109/APNOMS.2015.7275368","DOIUrl":null,"url":null,"abstract":"The SDN controllers maintain the flow tables to manage all the data flows passing through the SDN switches. In some cases, monitoring activities are required for the specific flows to detect the special events. Current de facto standard of SDN architecture enforces SDN switch to stay awake all the time from the time it receives the event monitoring request from SDN controller to catch the target event on the corresponding flow. This mechanism might disturb the fundamental SDN philosophy, which recommends the SDN switch to focus on the data forwarding, resulting in the degrading the performance of the whole SDN network. In order to tackle this problem in the real world domain, this paper focuses on the flow monitoring procedure described in OpenFlow specification version 1.4[1]. Starting from pointing out the problem of the current procedure in OpenFlow specification 1.4, we propose the detailed brand-new procedure, improved message format, and the system configuration to resolve the corresponding problem. The proposed idea can help the network service provider to build and operate their networks more efficiently and effectively.","PeriodicalId":269263,"journal":{"name":"2015 17th Asia-Pacific Network Operations and Management Symposium (APNOMS)","volume":"70 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2015-09-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"11","resultStr":"{\"title\":\"Adaptive flow monitoring in SDN architecture\",\"authors\":\"Seongbok Baik, Younggil Lim, Jongwoo Kim, Youngwoo Lee\",\"doi\":\"10.1109/APNOMS.2015.7275368\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The SDN controllers maintain the flow tables to manage all the data flows passing through the SDN switches. In some cases, monitoring activities are required for the specific flows to detect the special events. Current de facto standard of SDN architecture enforces SDN switch to stay awake all the time from the time it receives the event monitoring request from SDN controller to catch the target event on the corresponding flow. This mechanism might disturb the fundamental SDN philosophy, which recommends the SDN switch to focus on the data forwarding, resulting in the degrading the performance of the whole SDN network. In order to tackle this problem in the real world domain, this paper focuses on the flow monitoring procedure described in OpenFlow specification version 1.4[1]. Starting from pointing out the problem of the current procedure in OpenFlow specification 1.4, we propose the detailed brand-new procedure, improved message format, and the system configuration to resolve the corresponding problem. The proposed idea can help the network service provider to build and operate their networks more efficiently and effectively.\",\"PeriodicalId\":269263,\"journal\":{\"name\":\"2015 17th Asia-Pacific Network Operations and Management Symposium (APNOMS)\",\"volume\":\"70 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2015-09-28\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"11\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2015 17th Asia-Pacific Network Operations and Management Symposium (APNOMS)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/APNOMS.2015.7275368\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2015 17th Asia-Pacific Network Operations and Management Symposium (APNOMS)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/APNOMS.2015.7275368","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The SDN controllers maintain the flow tables to manage all the data flows passing through the SDN switches. In some cases, monitoring activities are required for the specific flows to detect the special events. Current de facto standard of SDN architecture enforces SDN switch to stay awake all the time from the time it receives the event monitoring request from SDN controller to catch the target event on the corresponding flow. This mechanism might disturb the fundamental SDN philosophy, which recommends the SDN switch to focus on the data forwarding, resulting in the degrading the performance of the whole SDN network. In order to tackle this problem in the real world domain, this paper focuses on the flow monitoring procedure described in OpenFlow specification version 1.4[1]. Starting from pointing out the problem of the current procedure in OpenFlow specification 1.4, we propose the detailed brand-new procedure, improved message format, and the system configuration to resolve the corresponding problem. The proposed idea can help the network service provider to build and operate their networks more efficiently and effectively.