Professional Documents
Culture Documents
2.A SDN or NFV Based IoT Network Slicing
2.A SDN or NFV Based IoT Network Slicing
net/publication/328327848
CITATIONS READS
6 142
6 authors, including:
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Meng Wang on 09 April 2020.
Application Layer
Multi-Flow Transmission
Datacenter Slice
VIM
Core Layer
QoS requirements especially in IoT system because there are VIM Cloud Data Center
plenty of IoT sensors in IoT system. In this paper, we propose VNF VNF VNF
Bandwidth:Text>Image>Video
Transport Layer
Transport Slice
SDN Controller
Bandwidth:Video>Image>Text
easily-operating service creation environment and a service Priority:Text>Image>Video
Access Slice
VIM
adding subservices and QoS policies into a business process
Access Layer
CCS CONCEPTS
1 INTRODUCTION
• Networks → Network design principles; Network manage-
ment; Mobile networks; With the development of Internet of Things (IoT) technolo-
gies, there have been plenty of IoT applications [1] such as
KEYWORDS smart cities, smart home, internet of vehicles and smart grid,
as the Figure 1(a) shows. In this situation, network is facing
Network slices; 5G; IoT; SDN; NFV
a rapid change by embracing Software Defined Networking
ACM Reference Format: (SDN) and Network Function Virtualization (NFV). This prob-
Meng Wang, Bo Cheng, Xuan Liu, Yi Yue, Biyi Li, Junliang Chen. lem is particularly difficult in the IoT environment because
2018. Poster:A SDN/NFV-Based IoT Network Slicing Creation Sys- there are so many sensors in the IoT environment. The fifth
tem. In The 24th Annual International Conference on Mobile Com- generation (5G) mobile network slicing with SDN/NFV [2]
puting and Networking (MobiCom ’18), October 29-November 2, 2018,
is expected to support a multitude of IoT applications. Using
New Delhi, India. ACM, New York, NY, USA, 3 pages. https://doi.
org/10.1145/3241539.3267745
SDN at the transport layer makes it easier to centralize the
network intelligence in the SDN controller. Cloud and edge
Bo Cheng is the corresponding author. datacenter use NFV to decouple the network functionalities
from the hardware. As shown in Figure 1(b), IoT network
Permission to make digital or hard copies of part or all of this work for
personal or classroom use is granted without fee provided that copies are slicing based on SDN/NFV provides flexibility and support
not made or distributed for profit or commercial advantage and that copies for various requirements of IoT applications.
bear this notice and the full citation on the first page. Copyrights for third- However, there are some existing problems still remain to
party components of this work must be honored. For all other uses, contact solve. Firstly, most of the current IoT system are specific and
the owner/author(s).
therefore the slices are difficult to reuse. Secondly, although
MobiCom ’18, October 29-November 2, 2018, New Delhi, India
there are many NFV management systems such as [3] [4], we
© 2018 Copyright held by the owner/author(s).
ACM ISBN 978-1-4503-5903-0/18/10. want a management system that can manage IoT network
https://doi.org/10.1145/3241539.3267745 slices, VNFs and IoT sensors in a unified way. Thirdly, as the
666
Poster Presentation MobiCom’18, October 29–November 2, 2018, New Delhi, India
slice_template:
Workspace
Design Plane
yaml_templates:
VNF1:
properties:
Service 2
Service 1 flavor: m1.small
slice1:
Service 3 Extended-YAML properties:
name: smart_home
Service 5 Service 6 business_process:
Service 4 properties:
s5-s1, s6-s2,
VNF Domain
Control Plane
PNF PNF
Data Plane
S-PNF S-PNF
PNF PNF S-PNF S-PNF
Common PNFs IoT Sensor-PNFs
667
Poster Presentation MobiCom’18, October 29–November 2, 2018, New Delhi, India
3 IMPLEMENTATION
2.5K We have developed three S-VNFs to implement the IoT sce-
nario described in Figure 1(c). The instance contains three
Number of packets per second
2K
data sources: video, image and text. The text contains some
1.5K
important commands. We just drag and drop subservices
1K related to three data sources in the design plane.
500
At the beginning, the order of bandwidths is video, image
and text. We want to receive commands quickly and video
0 20 80 time(s) 140 quality is less important to us. So the order of priorities is
Figure 3: Number of packets per second of video text, image and video. We can define priority-based QoS poli-
cies to guarantee the bandwidth of high priority service in
200
the design plane.
We judge the change of bandwidth by observing the number
Number of packets per second
668