| Literature DB >> 32512902 |
Thi-Thuy-Lien Nguyen1,2, Tuan-Minh Pham3,4.
Abstract
The Internet of Things (IoT) is increasingly creating new market possibilities in several industries' sectors such as smart homes, smart manufacturing, and smart cities, to link the digital and physical worlds. A key challenge in an IoT system is to ensure network performance and cost-efficiency when a plethora of data is generated and proliferated. The adoption of Network Function Virtualization (NFV) technologies within an IoT environment enables a new approach of providing services in a more agile and cost-efficient way. We address the problem of traffic engineering with multiple paths for an NFV enabled IoT system (vIoT), taking into account the fluctuation of traffic volume in various time periods. We first formulate the problem as a mixed linear integer programming model for finding the optimal solution of link-weight configuration and traffic engineering. We then develop heuristic algorithms for a vIoT system with a large number of devices. Our solution enables a controller to adjust a link weight system and update a flow table at an NFV switch for directing IoT traffic through a service function chain in a vIoT system. The evaluation results under both synthetic and real-world datasets of network traffic and topologies show that our approach to traffic engineering with multiple paths remarkably improves several performance metrics for a vIoT system.Entities:
Keywords: internet of things; network functions virtualization; optimization; traffic engineering; vIoT
Year: 2020 PMID: 32512902 PMCID: PMC7308828 DOI: 10.3390/s20113198
Source DB: PubMed Journal: Sensors (Basel) ISSN: 1424-8220 Impact factor: 3.576
Figure 1An NFV enabled IoT framework (vIoT).
Figure 2Service chain provisioning in vIoT.
Summary of notations.
|
| |
|
| Service demands |
|
| Service demands require that the system fully satisfies their traffic volumes |
|
| Service demands allow a system to serve with its best efforts |
|
| Links on the vIoT system |
|
| Nodes on the vIoT system |
|
| VNFs available on the vIoT system |
|
| Possible paths on the vIoT system |
|
| Possible paths for demand |
|
| Time periods |
|
| |
|
| The traffic volume of |
|
| The starting node of demand |
|
| The terminating node of demand |
|
| The SFC requested by demand |
|
| Node |
|
| Bandwidth capacity of link |
|
| Network routing cost of link |
|
| Computing capacity of node |
|
| The largest link capacity of all links |
|
| The weight of accepted demands |
|
| The weight of total satisfied traffic |
|
| The weight of total network routing cost |
|
| |
|
| A binary variable represents that link |
|
| A binary variable represents that link |
|
| |
|
| The traffic rate on link |
|
| The smallest length of the paths from node |
|
| Total of traffic through link |
|
| Total traffic volume assigned to outgoing links of node |
|
| Percentage of accepted demands at time period |
|
| Percentage of total satisfied traffic at time period |
|
| Percentage of total network routing cost at time period |
|
| |
|
| Number of accepted demands at time period |
|
| |
|
| The minimum ratio of accepted demands over all time periods |
|
| The minimum of total satisfied traffic over all time periods |
|
| The maximum of total network routing cost over all time periods |
|
| |
| w | The metric of links on the vIoT system, |
| x | A traffic splitting vector |
Figure 3Flowchart of the proposed algorithm.
Scenarios.
| Scenarios | Number of Virtual Nodes | Number of Virtual Links | Number of VNFs | Number of Time Periods | Min Number of Demand | Max Number of Demand |
|---|---|---|---|---|---|---|
| Internet2 | 12 | 30 | 4 | 3 | 20 | 120 |
| Geant | 22 | 72 | 4 | 4 | 50 | 200 |
| Two-tier | 60 | 282 | 4 | 3 | 10 | 40 |
| Bcube | 176 | 1464 | 4 | 3 | 50 | 200 |
Figure 4Efficient traffic engineering solution considering differentiated demands with the Internet2 dataset.
Figure 5Efficient traffic engineering solution considering differentiated demands with the Bcube dataset.
Figure 6Efficient traffic engineering solution considering differentiated demands with the GEANT dataset.
Figure 7Efficient traffic engineering solution considering differentiated demands with the Two-tier dataset.
Figure 8Efficient traffic engineering solution considering multiple time periods with the Internet2 dataset.
Figure 9Efficient traffic engineering solution considering multiple time periods with the Bcube dataset.
Figure 10Efficient traffic engineering solution considering multiple time periods with the GEANT dataset.
Figure 11Efficient traffic engineering solution considering multiple time periods with the Two-tier dataset.
Figure 12Efficient traffic engineering solution considering the combination of differentiated demands and multiple time periods with the Internet2 dataset.
Figure 13Efficient traffic engineering solution considering the combination of differentiated demands and multiple time periods with the Bcube dataset.
Figure 14Efficient traffic engineering solution considering the combination of differentiated demands and multiple time periods with the GEANT dataset.
Figure 15Efficient traffic engineering solution considering the combination of differentiated demands and multiple time periods with the Two-tier dataset.