Abstract
Numerous Internet of Things (IoT) devices are being connected to the net-works to offer services. To cope with a large diversity and number of IoT ser-vices, operators must meet those needs with a more flexible and efficient net-work architecture. Network slicing in 5G promises a feasible solution for this issue with network virtualization and programmability enabled by NFV (Net-work Functions Virtualization). In this research, we use virtualized IoT plat-forms as the Virtual Network Functions (VNFs) and customize network slices enabled by NFV with different QoS to support various kinds of IoT services for their best performance. We construct three different slicing systems including: 1) a single slice system, 2) a multiple customized slices system and 3) a single but scalable network slice system to support IoT services. Our objective is to compare and evaluate these three systems in terms of their throughput, aver-age response time and CPU utilization in order to identify the best system de-sign. Validated with our experiments, the performance of the multiple slicing system is better than those of the single slice systems whether it is equipped with scalability or not.
Highlights
The Field Domain consists of Application Dedicated Node (ADN), Application Service Node (ASN) and Middle Node (MN) while Infrastructure Node (IN) is located in the Infrastructure Domain
For the single slice system, we send the traffic to the OM2M IoT platform directly
For the multiple slicing system, each type of IoT traffic will be sent to the Virtualized Network Functions (VNFs) on the corresponding network slice
Summary
Such support doesn’t exist in the currently deployed 4G networks [3]. It provides common service functions and uniform APIs via a common framework to support the development of IoT applications and services. There are 4 different kinds of nodes in the oneM2M network: Application Dedicated Node (ADN), Application Service Node (ASN), Middle Node (MN) and Infrastructure Node (IN). OM2M provides RESTful APIs for creating and managing M2M resources It offers Common Services Entities (CSEs) to implement horizontal M2M servers, gateways, and devices. We deploy OM2M IN CSEs as VNFs and use these VNFs to construct network slices in NFV to conduct our experiments with three different slicing systems
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
