A. Basta, W. Kellerer, M. Hoffmann, K. Hoffmann, E. Schmidt
{"title":"A Virtual SDN-Enabled LTE EPC Architecture: A Case Study for S-/P-Gateways Functions","authors":"A. Basta, W. Kellerer, M. Hoffmann, K. Hoffmann, E. Schmidt","doi":"10.1109/SDN4FNS.2013.6702532","DOIUrl":null,"url":null,"abstract":"The recent initiative of Network Functions Virtualization (NFV) aims to deliver any data- plane processing or control-plane function in high volume data centers or network elements to decrease operational cost and increase deployment flexibility. In order to dynamically direct traffic flows between respective network elements, Software Defined Networking (SDN) can be seen as one enabler. In this paper, we focus on mobile core network nodes such as the MME, HSS, S- and P- Gateway as standardized for the LTE Evolved Packet Core (EPC). One straightforward solution for a virtualized EPC architecture would be to move all EPC network nodes completely into a data center and handle the data traffic via SDN-enabled switches. However, this solution would keep the conventional monolithic architecture unchanged. A possible split in the EPC functionality between a centralized data center and operator's transport network elements could be needed to provide the desired flexibility, performance and TCO reduction. Therefore, we have analyzed the EPC nodes and classified their functions according to their impact on data-plane and control-plane processing. We propose a mapping for these functions on four alternative deployment frameworks based on SDN and OpenFlow (OF). In addition, we investigate the current OF implementation's capability to realize basic core operations such as QoS, data classification, tunneling and charging. Our analysis shows that functions, which involve high data packet processing such as tunneling, have more potential to be kept on the data-plane network element, i.e. realized by an OpenFlow Switch. We argue for an enhanced OF network element NE+, which contains additional network functions next to the basic OpenFlow protocol.","PeriodicalId":6455,"journal":{"name":"2013 IEEE SDN for Future Networks and Services (SDN4FNS)","volume":"16 1","pages":"1-7"},"PeriodicalIF":0.0000,"publicationDate":"2013-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"159","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2013 IEEE SDN for Future Networks and Services (SDN4FNS)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SDN4FNS.2013.6702532","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 159
Abstract
The recent initiative of Network Functions Virtualization (NFV) aims to deliver any data- plane processing or control-plane function in high volume data centers or network elements to decrease operational cost and increase deployment flexibility. In order to dynamically direct traffic flows between respective network elements, Software Defined Networking (SDN) can be seen as one enabler. In this paper, we focus on mobile core network nodes such as the MME, HSS, S- and P- Gateway as standardized for the LTE Evolved Packet Core (EPC). One straightforward solution for a virtualized EPC architecture would be to move all EPC network nodes completely into a data center and handle the data traffic via SDN-enabled switches. However, this solution would keep the conventional monolithic architecture unchanged. A possible split in the EPC functionality between a centralized data center and operator's transport network elements could be needed to provide the desired flexibility, performance and TCO reduction. Therefore, we have analyzed the EPC nodes and classified their functions according to their impact on data-plane and control-plane processing. We propose a mapping for these functions on four alternative deployment frameworks based on SDN and OpenFlow (OF). In addition, we investigate the current OF implementation's capability to realize basic core operations such as QoS, data classification, tunneling and charging. Our analysis shows that functions, which involve high data packet processing such as tunneling, have more potential to be kept on the data-plane network element, i.e. realized by an OpenFlow Switch. We argue for an enhanced OF network element NE+, which contains additional network functions next to the basic OpenFlow protocol.