@article{Xian1803:Reducing,

title = {Reducing Latency in Virtual Machines Enabling Tactile Internet for Human Machine Co-working},

author = {Zuo {Xiang} and Frank {Gabriel} and Elena {Urbano} and Giang T. {Nguyen} and Martin {Reisslein} and Frank H. P. {Fitzek}},

doi = {10.1109/JSAC.2019.2906788},

issn = {0733-8716},

year  = {2019},

date = {2019-05-01},

journal = {IEEE Journal on Selected Areas in Communications},

volume = {37},

number = {5},

pages = {1098-1116},

address = {, USA},

abstract = {Software Defined Networking (SDN) and Network Function Virtualization (NFV) processed in Multi-access Edge Computing (MEC) cloud systems have been proposed as critical paradigms for achieving the low latency requirements of the tactile Internet. While virtual network functions (VNFs) allow greater flexibility compared to hardware based solutions, the VNF abstraction also introduces additional packet processing delays. In this paper, we investigate the practical feasibility of NFV with respect to the tactile Internet latency requirements. We develop, implement, and evaluate Chain bAsed Low latency VNF ImplemeNtation (CALVIN), a low-latency management framework for distributed Service Function Chains (SFCs). CALVIN classifies VNFs into elementary, basic, and advanced VNFs. CALVIN implements elementary and basic VNFs in the kernel space, while advanced VNFs are implemented in the user space. Throughout, CALVIN employs a distributed mapping with one VNF per Virtual Machine (VM) in a MEC system. Moreover, CALVIN avoids the metadata structure processing and batch processing of packets in the conventional Linux networking stack so as to achieve short per-packet latencies. Our rigorous measurements on off-the-shelf conventional networking and computing hardware demonstrate that CALVIN achieves round-trip times from a MEC ingress point via an elementary forwarding VNF and a MEC server to a MEC egress point on the order of 0.32~ms. Our measurements also indicate that MEC network coding and encryption are feasible for small 256 byte packets with an MEC latency budget of .35~ms; whereas, large 1400 byte packets can complete the network coding, but not the encryption within the 0.35~ms.},

keywords = {},

pubstate = {published},

tppubtype = {article}

}