<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CSSE</journal-id>
<journal-id journal-id-type="nlm-ta">CSSE</journal-id>
<journal-id journal-id-type="publisher-id">CSSE</journal-id>
<journal-title-group>
<journal-title>Computer Systems Science &#x0026; Engineering</journal-title>
</journal-title-group>
<issn pub-type="ppub">0267-6192</issn>
<publisher>
<publisher-name>Tech Science Press</publisher-name>
<publisher-loc>USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">20534</article-id>
<article-id pub-id-type="doi">10.32604/csse.2022.020534</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Mobile Fog Computing by Using SDN/NFV on 5G Edge Nodes</article-title><alt-title alt-title-type="left-running-head">Mobile Fog Computing by Using SDN/NFV on 5G Edge Nodes</alt-title><alt-title alt-title-type="right-running-head">Mobile Fog Computing by Using SDN/NFV on 5G Edge Nodes</alt-title>
</title-group>
<contrib-group content-type="authors">
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western"><surname>Sreekanth</surname><given-names>G. R.</given-names></name>
<xref ref-type="aff" rid="aff-1">1</xref><email>grsreekanth1@yahoo.com</email>
</contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western"><surname>Ahmed</surname><given-names>S. Ahmed Najat</given-names></name>
<xref ref-type="aff" rid="aff-2">2</xref>
</contrib>
<contrib id="author-3" contrib-type="author">
<name name-style="western"><surname>Sarac</surname><given-names>Marko</given-names></name>
<xref ref-type="aff" rid="aff-3">3</xref>
</contrib>
<contrib id="author-4" contrib-type="author">
<name name-style="western"><surname>Strumberger</surname><given-names>Ivana</given-names></name>
<xref ref-type="aff" rid="aff-3">3</xref>
</contrib>
<contrib id="author-5" contrib-type="author">
<name name-style="western"><surname>Bacanin</surname><given-names>Nebojsa</given-names></name>
<xref ref-type="aff" rid="aff-3">3</xref>
</contrib>
<contrib id="author-6" contrib-type="author">
<name name-style="western"><surname>Zivkovic</surname><given-names>Miodrag</given-names></name>
<xref ref-type="aff" rid="aff-3">3</xref>
</contrib>
<aff id="aff-1"><label>1</label><institution>Department of Computer Science and Engineering, Kongu Engineering College</institution>, <addr-line>Erode, 638060</addr-line>, <country>India</country></aff>
<aff id="aff-2"><label>2</label><institution>Department of Computer Engineering, Lebanese French University</institution>, <addr-line>Erbil, 44001</addr-line>, <country>Iraq</country></aff>
<aff id="aff-3"><label>3</label><institution>Singidunum University</institution>, <addr-line>Belgrade, 11000</addr-line>, <country>Serbia</country></aff>
</contrib-group><author-notes><corresp id="cor1"><label>&#x002A;</label>Corresponding Author: G. R. Sreekanth. Email: <email>grsreekanth1@yahoo.com</email></corresp></author-notes>
<pub-date pub-type="epub" date-type="pub" iso-8601-date="2021-10-4"><day>4</day>
<month>10</month>
<year>2021</year></pub-date>
<volume>41</volume>
<issue>2</issue>
<fpage>751</fpage>
<lpage>765</lpage>
<history>
<date date-type="received"><day>28</day><month>5</month><year>2021</year></date>
<date date-type="accepted"><day>19</day><month>7</month><year>2021</year></date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2022 Sreekanth et al.</copyright-statement>
<copyright-year>2022</copyright-year>
<copyright-holder>Sreekanth et al.</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This work is licensed under a <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="TSP_CSSE_20534.pdf"></self-uri>
<abstract>
<p>Fog computing provides quality of service for cloud infrastructure. As the data computation intensifies, edge computing becomes difficult. Therefore, mobile fog computing is used for reducing traffic and the time for data computation in the network. In previous studies, software-defined networking (SDN) and network functions virtualization (NFV) were used separately in edge computing. Current industrial and academic research is tackling to integrate SDN and NFV in different environments to address the challenges in performance, reliability, and scalability. SDN/NFV is still in development. The traditional Internet of things (IoT) data analysis system is only based on a linear and time-variant system that needs an IoT data system with a high-precision model. This paper proposes a combined architecture of SDN and NFV on an edge node server for IoT devices to reduce the computational complexity in cloud-based fog computing. SDN provides a generalization structure of the forwarding plane, which is separated from the control plane. Meanwhile, NFV concentrates on virtualization by combining the forwarding model with virtual network functions (VNFs) as a single or chain of VNFs, which leads to interoperability and consistency. The orchestrator layer in the proposed software-defined NFV is responsible for handling real-time tasks by using an edge node server through the SDN controller via four actions: task creation, modification, operation, and completion. Our proposed architecture is simulated on the EstiNet simulator, and total time delay, reliability, and satisfaction are used as evaluation parameters. The simulation results are compared with the results of existing architectures, such as software-defined unified virtual monitoring function and ASTP, to analyze the performance of the proposed architecture. The analysis results indicate that our proposed architecture achieves better performance in terms of total time delay (1800&#x2005;s for 200 IoT devices), reliability (90&#x0025;), and satisfaction (90&#x0025;).</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>Mobile fog computing</kwd>
<kwd>edge computing</kwd>
<kwd>edge node</kwd>
<kwd>IoT</kwd>
<kwd>software-defined networking</kwd>
<kwd>network functions virtualization</kwd>
<kwd>orchestrator</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>In recent years, cloud computing has been the main storage platform for many applications. A high demand for storage space has also been noted due to high-level information processing and digital motivation. Edge devices are preferred to help in cloud servers&#x2019; traffic. However, future edge devices alone cannot process the cloud storage. Therefore, mobile fog computing (MFC) has been introduced by researchers. The quality of service (QoS) of smart devices is guaranteed in fog and cloud computing. They are considered promising technologies for enhancing the quality of devices. In advancement techniques, such as the Internet of things (IoT), considerable data are generated and transferred over the network at a particular time. This condition leads to the importance and need for fog computing on edge nodes for storage and computation of data in the network to reduce the traffic constantly. Hence, the edge devices in the network seem close to users, and the latency for transmitting data from the cloud data center to users is reduced, which leads to rapid computation. MFC is a next assured technology to reduce the latency of transmission, and services in a timely manner will save energy and increase scalability. To make MFC reliable and time efficient, software-defined networking (SDN) and network functions virtualization (NFV) are used.</p>
<p>SDN separates data and control planes in networking switches. The entire network is controlled using centralized software logical programs. This methodology manages networks with new configuration. The main difference between SDN and NFV is as follows: SDN separates the control function from the forwarding function in networks, whereas NFV removes forwarding and other functions from the hardware machine it computes. Both systems mainly rely on the virtualization concept that enables network infrastructure design to separate hardware and software.</p>
<p>SDN and NFV compute together by transferring network data and execute a router control function in a virtual machine. This process is used in cloud computing-based MFC to reduce the computational complexity in the network. The basic function in the network is provided by NFV, while SDN focuses on specific uses. SDN separates hardware in networks, while NFV concentrates on the virtualization of physical hardware during traffic. The traditional IoT data analysis system is only based on a linear and time-variant system that needs an IoT data system with a high-precision model (EstiNet). This limitation leads to the concept of big data management-based SDN to determine the network bandwidth and storage units. This concept will extend research interests to the next level. Instead of connecting IoT devices to the cloud server directly, mobile edge computing (MEC) connects them to the edge server.</p>
<sec id="s1_1">
<label>1.1</label>
<title>Scope of This Work</title>
<p><list list-type="bullet"><list-item>
<p>SDN provides a unified model of the forwarding plane that is separated from the control plane. Meanwhile, NFV concentrates on visualization.</p></list-item><list-item>
<p>The combination of a forwarding model with virtual network functions (VNFs) leads to interoperability and homogeneity.</p></list-item><list-item>
<p>One protocol is adequate for control, management, and orchestration.</p></list-item><list-item>
<p>The main advantage of using this concept is that it makes dynamic and flexible network infrastructure.</p></list-item></list></p>
</sec>
<sec id="s1_2">
<label>1.2</label>
<title>Objective of This Work</title>
<p><list list-type="bullet"><list-item>
<p>The use of SDN/NFV on edge nodes leads to reduced latency and increased scalability.</p></list-item><list-item>
<p>The application of SDN/NFV in edge computing results in a dynamic, quick, and reliable computing environment.</p></list-item><list-item>
<p>The scaling capabilities of this combined architecture use the network resources in an optimal way.</p></list-item><list-item>
<p>Data may be transferred to edge nodes for fast transmission to users, which will increase the execution time of each task.</p></list-item></list></p>
<p>The rest of this paper is organized as follows. Section 2 presents a detailed literature review. Section 3 explains the proposed architecture and indicates its simulation. Section 4 discusses the simulation result and comparative analysis with existing architectures. Section 5 concludes this work.</p>
</sec>
</sec>
<sec id="s2">
<label>2</label>
<title>Related Work</title>
<p>Current industrial and academic studies are tackling to integrate SDN and NFV in different environments to address the challenges in performance, reliability, and scalability. SDN/NFV is still in development. Reference [<xref ref-type="bibr" rid="ref-1">1</xref>] provided a detailed review of an integrated SDN/NFV architecture by synthesizing its architectural design and stated the areas for improvement.</p>
<p>NFV solves many issues by transferring network functions and hardware utilization to commercial off-the-shelf (COTS) software systems in virtual functions [<xref ref-type="bibr" rid="ref-2">2</xref>]. In current networks, the Internet protocol layer combines data and control planes vertically into network devices. On the contrary, SDN separates the control plane from the data plane in the network.</p>
<p>The traditional IoT data analysis system is only based on a linear and time-variant system that needs an IoT data system with a high-precision model [<xref ref-type="bibr" rid="ref-3">3</xref>], which leads to the concept of big data management-based SDN to determine the network bandwidth and storage units. MEC is a recent research topic that combines computing resources in the contiguity of IoT devices [<xref ref-type="bibr" rid="ref-4">4</xref>]. This topic will extend research interests to the next level. Instead of connecting IoT devices to the cloud server directly, MEC connects them to the edge server. Current research on this topic [<xref ref-type="bibr" rid="ref-5">5</xref>] estimates that approximately 29 billion IoT smart devices will be connected to the Internet by 2022.</p>
<p>A distributed deep learning-driven task off-loading (DDTO) method has been proposed to identify the edge and cloud differences in choosing off-loading devices. It generates a near-optimal off-loading decision in mobile, edge, and cloud-centralized servers. The proposed DDTO in [<xref ref-type="bibr" rid="ref-6">6</xref>] presented high accuracy, which generated decisions on off-loading data effectively and efficiently in edge and cloud servers. Reference [<xref ref-type="bibr" rid="ref-7">7</xref>] discussed NFV and its relationship with SDN and cloud computing. The authors surveyed the clear functions of NFV and identified the promising future research guidelines. They also outlined the key NFV projects and used cases.</p>
<p>The next-generation computing migration outlines for networks were discussed in [<xref ref-type="bibr" rid="ref-8">8</xref>]. The paper discussed MEC with SDN and NFV technologies. It also considered decision making on multiattribute and migrant computing for solving MEC based on SDN and NFV.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-9">9</xref>] proposed Computing Mode Selection (CMS) and priority-based execution sequences for tasks (ASTP) in the architecture of a smart factory based on IIoT and SDN. The SDN controller has the design of the CMS module in it. The mode of optimal computing is obtained by each service while operating in the CMS algorithm. Then, on the basis of task performance in real time and calculated amount, the priorities of tasks are calculated. To complete the transmission of tasks, the SDN controller sends the flow table to the switch in accordance with the task priority values.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-10">10</xref>] discussed the off-loading tasks in MEC. It showed the trade-off between latency and reliability in off-loading. In the proposed architecture, the user equipment divides a task into many subtasks, then they are off-loaded in order of multiple edges. To reduce the latency and off-loading probability, the authors formulated optimization problems, which are nonconvex. They proposed three algorithms based on heuristic approach, linear reformulation, and half defined relaxation. The formulated problems were solved through optimizing edge node candidates&#x2019; selection, off-loading order, and task allocation.</p>
<p>The architectures of adaptive transmission for SDN and fog computing for IIoT were proposed in [<xref ref-type="bibr" rid="ref-11">11</xref>]. In this work, data streams were divided into two groups, and two strategies were proposed for low and high deadlines. The proposed method performed better than existing methods. The architectures of MEC ecosystem and orchestration were developed in [<xref ref-type="bibr" rid="ref-12">12</xref>]. The orchestrator and external elements functioned in a module to indicate the QoS with the concentration on the channel state of information along with the life cycle of MEC services.</p>
<p>To address network scalability, single process, distributed monitoring of virtual functions, network flexibility, and acceptance of virtual life cycle problems were managed in [<xref ref-type="bibr" rid="ref-13">13</xref>]. The proposed software-defined unified virtual monitoring function called (SuVMF) based on SDN for large networks was used.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-14">14</xref>] stated that SDN and NFV provide a complete structure of network devices. Such a structure needs a common model on abstraction for forwarding model and network functions. Interoperability and homogeneity are ensured in this model.</p>
<p>The utilization of SDN in network access, core network, and WAN between edge nodes and clouds has been reviewed in detail. The issues and future challenges have also been addressed. Reference [<xref ref-type="bibr" rid="ref-15">15</xref>] made significant contributions, ranging from SDN and NFV through ecosystem to orchestration with SDN-NFV, by considering the issues of optimization, network control, and security.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-16">16</xref>] introduced a novel method called autonomic network management and optimization architecture. This work combined SDN and software-defined radio to improve the flexibility, performance, and available resource usage in SDN with a cognitive radio network system. An efficient VNF that works effectively at edges was proposed in [<xref ref-type="bibr" rid="ref-17">17</xref>] for enhancing network services in IoT applications.</p>
<p>To simplify the distribution of service-chained VNFs, the authors proposed an approach that extends the network cloud infrastructure with MEC for permitting delay-sensitive network traffic. To make 5G networks heterogeneous, [<xref ref-type="bibr" rid="ref-18">18</xref>] designed a model using the SDN architecture. In terms of the security issues in the centralization of SDN, the authors proposed an error-free security architecture for 5G networks. Reference [<xref ref-type="bibr" rid="ref-19">19</xref>] exploited the flexibility of using SDN technology. It proposed an architecture called SDN-based MEC for solving the problem of choosing MEC and end user off-load data. The proposed architecture utilizes a reinforcement learning method and game theory techniques.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-20">20</xref>] designed an NFV orchestration that is scalable with clouds. To implement the data plane, segment routing was used. The proposed architecture exhibited minimal complexity in accordance with the number of orchestrations. Reference [<xref ref-type="bibr" rid="ref-21">21</xref>] reviewed SDN technologies and services with tools. It also presented an overview of tactical, ad hoc, military, and coalition networks. Reference [<xref ref-type="bibr" rid="ref-22">22</xref>] presented the challenges related to the adaptation of 5G technologies. The authors proposed a workflow for PaaS in multicloud based on modularity, microservices, and shape order.</p>
<p>Reference [<xref ref-type="bibr" rid="ref-23">23</xref>] presented the uses of combining SDN with MEC on IoT with detailed reviews. References [<xref ref-type="bibr" rid="ref-24">24</xref>,<xref ref-type="bibr" rid="ref-25">25</xref>] focused mainly on IoT research and applications.</p>
</sec>
<sec id="s3">
<label>3</label>
<title>Proposed 5G SDN/NFV Concept for Fog Computing</title>
<sec id="s3_1">
<label>3.1</label>
<title>Problem Description</title>
<p>With the advancement in IoT, large volumes of data are produced from IoT devices, such as smart home appliances, tablets, smartphones, routers, smart traffic systems, smart energy meters, cellular base stations, connected vehicles, and smart building controllers. Cloud computing efficiently processes considerable data in networks. With the rapid growth of the kind of IoT devices, excessive amounts of data must be transferred continuously over the network within a particular time. These data must be processed and responded as early as possible. As a result, the edge devices in the network are near to users, and the latency for transmitting data from the cloud data center to users is reduced, which leads to fast computation. We redevelop different communication methods with fog computing, such as SDN, NFV, content distribution network, the concept of 5G technology, and Long-Reach Passive Optical Network.</p>
</sec>
<sec id="s3_2">
<label>3.2</label>
<title>Architectural Overview</title>
<p>An overview of the proposed work is presented in <xref ref-type="fig" rid="fig-1">Fig. 1</xref>. Cloud services are stored at the top of the layer called tier 3, which consists of the cloud server with large capacity. Tier 2 consists of an edge node, which is connected to all other networks and comprises all network devices, such as routers and gateways. The proposed SDN/NFV architecture is applied on the edge node. Tier 3 consists of IoT devices, such as cameras, smartphones, sensors, and computers.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>Overview of the proposed SDN/NFV on edge nodes</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-1.png"/>
</fig>
<p><xref ref-type="fig" rid="fig-2">Fig. 2</xref> shows a detailed overview of our proposed architecture. It consists of three layers: application, control, and infrastructure. The first layer is responsible for network services at the cloud data center. These services communicate to the control plane of SDN&#x0027;s second layer called control layer through the open SDN orchestrator. In this proposed work, an SDN controller called Ryu is used. Ryu is an open-source structure created by NTT and written in Python. It supports OpenFlow, OF-Cong, and NETCONF. SDN&#x0027;s control plane is in charge of the traffic control in the application layer. The edge nodes directly communicate with the end devices. They communicate with the application layer through the SDN controller. Accordingly, the latency will be reduced, and data processing will be increased. SDN&#x0027;s main feature is the division of the control and forwarding planes.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>Architecture of the proposed SDNFV on edge nodes</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-2.png"/>
</fig>
<p>In <xref ref-type="fig" rid="fig-3">Fig. 3</xref>, in SDN&#x0027;s control plane, software called SDN controller is installed, which is responsible for handling the network traffic. It will run on COTS systems. The data plane is responsible for transferring data based on rules. The SDN controller combined with NFV VNFs at the edge is responsible for managing the rules through API. It does not have direct access to API. Consequently, the scalability and data processing accelerate. This work mainly focuses on traffic control by monitoring the data transferred to IoT devices from clouds and vice versa.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>Orchestrator layer in the proposed SDNFV on edge nodes</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-3.png"/>
</fig>
<p>The transferred data must be related to the query created by the end user, which means data processing is improved in terms of time. The task of transferring the correct data to the user is based on three indexes: i) higher, ii) lower, and iii) neutral. If the importance of a real-time task is high and the computational necessity is low, then the task belongs to the higher index. By contrast, when the importance of a real-time task is low and the computational necessity is high, then the task belongs to the lower index. That is, the smaller the calculation amounts are, the lower the complexity of the task will be.</p>
</sec>
<sec id="s3_3">
<label>3.3</label>
<title>Algorithm 1: Proposed Software-Defined NFV (SDNFV) on Edge Nodes</title>
<p>&#x2002;&#x2002;&#x2002;1. Data transmission in the industrial layer consists of IoT devices. A set of <italic>N(d)</italic> devices called <italic>N</italic>(<italic>d</italic>)&#x2009;&#x003D;&#x2009;&#x007B;1, 2, &#x2026;<italic>N</italic>&#x007D; exists, and each device has a task to be completed in a certain limit.</p>
<p>&#x2002;&#x2002;&#x2002;2. The orchestrator layer in the proposed SDNFV is responsible for handling real-time tasks by using an edge node server through the SDN controller via four actions: task creation, modification, operation, and completion.</p>
<p>&#x2002;&#x2002;&#x2002;If request &#x003D;&#x003D; valid then</p>
<p>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;If task &#x003D;&#x003D; exists then</p>
<p>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;Executed from the catalogue of the network system</p>
<p>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;Else</p>
<p>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;Call the service-chained module of SDNFV</p>
<p>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;Update the task</p>
<p>&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;&#x2002;end</p>
<p>&#x2002;&#x2002;&#x2002;3. Once the task is created, activated, and completed, the computational complexity is calculated as<disp-formula id="eqn-1"><label>(1)</label>
<mml:math id="mml-eqn-1" display="block"><mml:msub><mml:mi>T</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>C</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>L</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mo>,</mml:mo><mml:mi>m</mml:mi><mml:mi>a</mml:mi><mml:mi>x</mml:mi></mml:mrow></mml:msub><mml:mo fence="false" stretchy="false">}</mml:mo><mml:mi>n</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mi>N</mml:mi></mml:math>
</disp-formula>where</p>
<p><italic>T</italic><sub><italic>n</italic></sub>&#x2009;&#x2212;&#x2009;<italic>task</italic> <italic>for</italic> <italic>a</italic> <italic>particular</italic> <italic>device</italic></p>
<p><italic>C</italic><sub><italic>n</italic></sub>&#x2009;&#x2212;&#x2009;<italic>calculation</italic> <italic>of</italic> <italic>the</italic> <italic>CPU</italic> <italic>cycle</italic> <italic>amount</italic> <italic>needed</italic> <italic>to</italic> <italic>complete</italic> <italic>the</italic> <italic>task</italic></p>
<p><italic>L</italic><sub><italic>n</italic>,<italic>max</italic></sub>&#x2009;&#x2212;&#x2009;<italic>maximum</italic> <italic>latency</italic> <italic>of</italic> <italic>device</italic> <italic>n</italic> (<italic>in</italic> <italic>s</italic>)</p>
<p>&#x2002;&#x2002;&#x2002;4. After all input <italic>D</italic><sub><italic>n</italic></sub> is received, the task is performed on the fog node. Thus, on the edge node, the execution time of task <italic>J</italic><sub><italic>n</italic></sub> consists of two sectors: transmission and computing time. <italic>f</italic><sub><italic>n</italic>,<italic>E</italic></sub> denotes the computational resource of the edge server.<disp-formula id="eqn-2"><label>(2)</label>
<mml:math id="mml-eqn-2" display="block"><mml:msub><mml:mi>J</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mo>,</mml:mo><mml:mi>E</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mfrac><mml:mrow><mml:msub><mml:mi>D</mml:mi><mml:mi>n</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mo>,</mml:mo><mml:mi>E</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow><mml:mo>+</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mfrac><mml:mrow><mml:msub><mml:mi>C</mml:mi><mml:mi>n</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:msub><mml:mi>f</mml:mi><mml:mrow><mml:msup><mml:mrow><mml:mi>n</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup><mml:msup><mml:mrow><mml:mi>E</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msub></mml:mrow></mml:mfrac></mml:mrow></mml:mstyle></mml:mstyle></mml:math>
</disp-formula></p>
<p>&#x2002;&#x2002;&#x2002;5. The application layer performs the computation task based on the five indexes indicated in <xref ref-type="disp-formula" rid="eqn-3">Eqs. (3)</xref>&#x2013;<xref ref-type="disp-formula" rid="eqn-7">(7)</xref> to analyze the cost, time, and computation.</p>
</sec>
<sec id="s3_4">
<label>3.4</label>
<title>Workflow of the Proposed Architecture</title>
<p>The orchestrator layer in the proposed SDNFV is responsible for handling real-time tasks by using an edge node server through the SDN controller via four actions: task creation, modification, operation, and task completion. The workflow of the proposed architecture is depicted in <xref ref-type="fig" rid="fig-4">Fig. 4</xref>.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>Workflow of the proposed SDNFV on edge nodes</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-4.png"/>
</fig>
<p>From <xref ref-type="fig" rid="fig-4">Fig. 4</xref>, the workflow of the proposed architecture is elucidated as follows:<list list-type="roman-lower"><list-item><label>i)</label>
<p><bold>Task Request:</bold> An IoT device (user) sends the task request to the cloud processor. It is described using predefined templates.</p></list-item><list-item><label>ii)</label>
<p><bold>Task Checking:</bold> Once the request is received by the orchestrator in the proposed architecture via the edge node, it performs a security check to determine whether the request is authorized. If it is authorized, then it will be processed. Otherwise, the task request will be terminated.</p></list-item><list-item><label>iii)</label>
<p><bold>Task Registration:</bold> If the service of the task requested is already available, then the required resources will be reserved. If the requested service is not already available in the network system, then the task is created using the service-chained module of the proposed architecture&#x0027;s orchestrator. A single or chain of VNFs with the forwarding plane of SDN is responsible for it. To activate the initiated request, the proposed layer interacts with VNF for granting the task resources.</p></list-item><list-item><label>iv)</label>
<p><bold>Task Update</bold>: Task update is requested by the user. Again, a security check is performed on the modification request. Once the task that needs modification is verified, the update is performed through the service-scaling module of the proposed layer. The SDN controller of the proposed layer is responsible for monitoring the service in terms of the lifetime performance of the proposed architecture.</p></list-item><list-item><label>v)</label>
<p><bold>Task Termination:</bold> Once the device user sends a request to terminate the service, then the service manager of the orchestrator layer will terminate the request by completing the task.</p></list-item></list></p>
</sec>
<sec id="s3_5">
<label>3.5</label>
<title>Mathematical Computation</title>
<p>The proposed SDNFV model considers five indexes: cost, time, bandwidth, energy consumption, and energy calculation.<list list-type="roman-lower"><list-item><label>i)</label>
<p>Cost Index</p></list-item></list></p>
<p>The cost can be calculated using <xref ref-type="disp-formula" rid="eqn-3">Eq. (3)</xref>. The cost of the distance from source to destination is calculated by multiplying <italic>W</italic><sub><italic>c</italic></sub> as the unit of communication cost with the distance. The lower the cost is, the better the architecture will be.<disp-formula id="eqn-3"><label>(3)</label>
<mml:math id="mml-eqn-3" display="block"><mml:mi>C</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mi>S</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>D</mml:mi><mml:mi>j</mml:mi></mml:msub></mml:mrow><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:msub><mml:mi>W</mml:mi><mml:mi>c</mml:mi></mml:msub><mml:mo>&#x00D7;</mml:mo><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>d</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math>
</disp-formula><list list-type="simple"><list-item>
<p>ii) Time Index</p></list-item></list></p>
<p>It is the time the user needs from sending data to receiving data from the cloud center. Minimum time leads to a better model. It is calculated by adding transmission and computational delays as<disp-formula id="eqn-4"><label>(4)</label>
<mml:math id="mml-eqn-4" display="block"><mml:mi>T</mml:mi><mml:mo>=</mml:mo><mml:msub><mml:mi>T</mml:mi><mml:mi>p</mml:mi></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>T</mml:mi><mml:mi>c</mml:mi></mml:msub></mml:math>
</disp-formula><list list-type="simple"><list-item>
<p>iii) Bandwidth Index</p></list-item></list></p>
<p><italic>m</italic> virtual machines exist at the cloud center to serve <italic>m</italic> users at a time, then the total bandwidth is fixed, as shown as follows [<xref ref-type="bibr" rid="ref-1">1</xref>]:<disp-formula id="eqn-5"><label>(5)</label>
<mml:math id="mml-eqn-5" display="block"><mml:mi>B</mml:mi><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mtable rowspacing="4pt" columnspacing="1em"><mml:mtr><mml:mtd columnalign="left"><mml:msub><mml:mi>B</mml:mi><mml:mrow><mml:mo movablelimits="true" form="prefix">max</mml:mo></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>m</mml:mi><mml:mo>&#x003C;</mml:mo><mml:msub><mml:mi>T</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd columnalign="left"><mml:mi>W</mml:mi><mml:mrow><mml:mo>/</mml:mo></mml:mrow><mml:mi>m</mml:mi><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>T</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>&#x2264;</mml:mo><mml:mi>m</mml:mi><mml:mo>&#x2264;</mml:mo><mml:msub><mml:mi>T</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd columnalign="left"><mml:msub><mml:mi>B</mml:mi><mml:mrow><mml:mi>m</mml:mi><mml:mi>m</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>n</mml:mi><mml:mo>&#x003E;</mml:mo><mml:msub><mml:mi>T</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:mtd></mml:mtr></mml:mtable><mml:mo fence="true" stretchy="true" symmetric="true"></mml:mo></mml:mrow></mml:math>
</disp-formula>where <italic>B</italic> is the amount of bandwidth, and <italic>T</italic><sub>1</sub><italic>and</italic> <italic>T</italic><sub>2</sub> are the numbers of users at the cloud center.<list list-type="simple"><list-item>
<p>iv) Energy Consumption</p></list-item></list></p>
<p>Energy consumption is the energy spent when the cloud center offers a service to device users. This is also called cost index, which means lower energy leads to a better model.</p>
<p><disp-formula id="eqn-6"><label>(6)</label>
<mml:math id="mml-eqn-6" display="block"><mml:msub><mml:mi>E</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mi>E</mml:mi><mml:mi>b</mml:mi></mml:msub><mml:mo>+</mml:mo><mml:mi>m</mml:mi><mml:mo>&#x2217;</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>v</mml:mi><mml:mi>m</mml:mi></mml:mrow></mml:msub></mml:math>
</disp-formula>where <italic>E</italic><sub><italic>ai</italic></sub> is the total energy consumed, <italic>E</italic><sub><italic>b</italic></sub> is the total standby power consumption, and <italic>c</italic><sub><italic>vm</italic></sub> represents the unit of energy consumption.<list list-type="simple"><list-item><label>v)</label>
<p>v) Capacity of the Machines at the Cloud Center</p></list-item></list></p>
<p>The capacity is calculated as<disp-formula id="eqn-7"><label>(7)</label>
<mml:math id="mml-eqn-7" display="block"><mml:mrow><mml:mi mathvariant="normal">E</mml:mi><mml:mi mathvariant="normal">n</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">g</mml:mi><mml:mi mathvariant="normal">y</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">p</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">y</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mo>=</mml:mo><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">o</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">l</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">n</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">g</mml:mi><mml:mi mathvariant="normal">y</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">p</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">y</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">o</mml:mi><mml:mi mathvariant="normal">f</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">t</mml:mi><mml:mi mathvariant="normal">h</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">m</mml:mi><mml:mi mathvariant="normal">a</mml:mi><mml:mi mathvariant="normal">c</mml:mi><mml:mi mathvariant="normal">h</mml:mi><mml:mi mathvariant="normal">i</mml:mi><mml:mi mathvariant="normal">n</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mrow><mml:mo>/</mml:mo></mml:mrow><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">n</mml:mi><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">m</mml:mi><mml:mi mathvariant="normal">b</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">o</mml:mi><mml:mi mathvariant="normal">f</mml:mi><mml:mtext>&#xA0;</mml:mtext><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">s</mml:mi><mml:mi mathvariant="normal">e</mml:mi><mml:mi mathvariant="normal">r</mml:mi><mml:mi mathvariant="normal">s</mml:mi></mml:mrow></mml:math>
</disp-formula></p>
<p>To evaluate the performance of the proposed architecture of SDNFV on edge nodes, the simulation results are analyzed and compared with the results of existing architectures. The effective performance of the proposed architecture is shown in <xref ref-type="fig" rid="fig-5">Fig. 5</xref>. Our proposed SDNFV architecture on edge nodes is the middle architecture between the IoT devices and cloud data center. While using the proposed architecture on edge nodes for data processing, the response accelerates and the throughput is reduced because the configuration and processing of data are performed on the edge server.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Effective performance of the proposed architecture</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-5.png"/>
</fig>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Experimental Evaluation</title>
<sec id="s4_1">
<label>4.1</label>
<title>Mathematical Computation</title>
<p>MATLAB is used to develop the simulation environment for algorithm execution. A system of IIoT with SDN is established on edge devices. The EstiNet simulator is used for the simulation. In SDN, OpenFlow is processed between a controller and a switch. The simulated OpenFlow with SDN controller enables an Ethernet switch to support control panels as in-band or out-of-band by using multiple controllers. To control the simulated OpenFlow switches, open-source controller software can be used in the simulated SDN. The SDN Wi-Fi infrastructure can be simulated using OpenFlow-enabled access and switch devices. This simulation platform is best suitable for researchers in SDN.</p>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Simulation Result of the Proposed Architecture and Simulation Parameters</title>
<p>The proposed architecture lies on edge nodes near IoT devices. The response from the cloud center for a task request is processed with high execution time and low time delay, and the request is validated before processing. Hence, the user will obtain a response with low computational power and high performance. While the device count increases the time, the complexity throughput is also increased gradually. The simulation result is shown in <xref ref-type="table" rid="table-1">Tab. 1</xref>. <xref ref-type="fig" rid="fig-6 fig-7 fig-8">Figs. 6&#x2013;8</xref> show the simulation result of the proposed SDNFV architecture in terms of the number of IoT device requests, such as 50, 80, 100, 150, and 200. Our proposed architecture presents computational complexity of 1500&#x2005;J, cost of 240, execution time of 230&#x2005;s, and throughput of 2200 kbps for 200 devices. To analyze the performance of the proposed architecture further, it is compared with existing architectures, such as ASTP and SuVMF.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Computational complexity of the proposed architecture</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-6.png"/>
</fig>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>Execution time of the proposed architecture</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-7.png"/>
</fig>
<fig id="fig-8">
<label>Figure 8</label>
<caption>
<title>Throughput of the proposed architecture</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-8.png"/>
</fig>
<table-wrap id="table-1"><label>Table 1</label>
<caption>
<title>Simulation result of the proposed architecture</title></caption>
<table frame="hsides"><colgroup><col align="left"/><col align="left"/><col align="left"/><col align="left"/><col align="left"/>
</colgroup>
<thead>
<tr>
<th align="left">No. of devices</th>
<th align="left">Time complexity</th>
<th align="left">Cost</th>
<th align="left">Time</th>
<th align="left">Throughput</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">50</td>
<td align="left">750</td>
<td align="left">140</td>
<td align="left">80</td>
<td align="left">50</td>
</tr>
<tr>
<td align="left">80</td>
<td align="left">850</td>
<td align="left">180</td>
<td align="left">100</td>
<td align="left">1000</td>
</tr>
<tr>
<td align="left">100</td>
<td align="left">1100</td>
<td align="left">200</td>
<td align="left">130</td>
<td align="left">1400</td>
</tr>
<tr>
<td align="left">150</td>
<td align="left">1300</td>
<td align="left">220</td>
<td align="left">180</td>
<td align="left">1800</td>
</tr>
<tr>
<td align="left">200</td>
<td align="left">1500</td>
<td align="left">240</td>
<td align="left">230</td>
<td align="left">2200</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4_3">
<label>4.3</label>
<title>Results and Discussion</title>
<p><bold>Total Time Delay:</bold> The total time delay of the architectures is shown in <xref ref-type="fig" rid="fig-9">Fig. 9</xref>. As the device amount increases, the delay time is also increased for all the architectures. However, our proposed SDNFV has less total time delay compared with the other existing architectures because it selects each device task through the edge node of the framework via NFV. For the requests of 200 IoT devices, the time delay of the proposed architecture is 1800&#x2005;s only, that of ASTP is 2500&#x2005;s, and that of SuVMF is 3000&#x2005;s.</p>
<fig id="fig-9">
<label>Figure 9</label>
<caption>
<title>Performance analysis in terms of total time delay</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-9.png"/>
</fig>
<p><bold>Reliability</bold>. This is an important index for evaluating the success of any architecture in task processing. When the failure rate to complete a task is low, it means the reliability of the architecture is high. From <xref ref-type="fig" rid="fig-10">Fig. 10</xref>. with the increase in the device number, the reliability of all architectures decreases. With the concept of SDN with NFV on edge nodes, the device requests are validated, and response is performed through VNF&#x0027;s forwarding plane in the orchestrator layer. The reliability of the proposed architecture is higher than that of the other existing architectures. The proposed architecture achieves 90&#x0025; reliability on 200 devices, which is higher than that of the two other architectures (85&#x0025; for ASTP and 70&#x0025; for SuVMF).</p>
<fig id="fig-10">
<label>Figure 10</label>
<caption>
<title>Performance analysis in terms of reliability</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-10.png"/>
</fig>
<p><bold>Satisfaction</bold>. It is a comprehensive index for real-time systems. The best architecture must rapidly respond to requests and achieve user satisfaction. When the number of device requests is increased, the tasks must be processed rapidly; if the system is not able to respond on time, the satisfaction will be low. <xref ref-type="fig" rid="fig-11">Fig. 11</xref>. shows the analysis of the architectures in terms of user satisfaction.</p>
<fig id="fig-11">
<label>Figure 11</label>
<caption>
<title>Performance analysis in terms of satisfaction</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_20534-fig-11.png"/>
</fig>
<p>The proposed SDNFV on edge nodes has the highest satisfaction among the architectures. The proposed architecture lies on the edge nodes near the IoT devices. The response from the cloud center for a task request is processed with high execution time and low time delay, and the request is validated before processing. Hence, the user will receive the response as early as possible with full satisfaction. Our proposed architecture achieves 90&#x0025; satisfaction compared with ASTP at 82&#x0025; and SuVMF at 68&#x0025;. In sum, our proposed SDN with NFV on edge nodes performs better in terms of total time delay, reliability, and satisfaction.</p>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Conclusions</title>
<p>The MFC architecture uses SDN/NFV on edge nodes to reduce the complexity of data computation. Every hardware is separated and controlled using software virtualization concepts. It produces high reliability with low time delay. This architecture improves the QoS among edge computing devices in cloud computing infrastructure. The SDN controller combined with NFV VNFs on edge nodes is responsible for managing rules through API. Considerable data can be computed with minimal complexity when using SDNFV in fog devices. Information growth can be a competitor for every growing technology. This architecture can help reduce the computational complexity. The simulation results prove that our proposed architecture obtains better throughput, execution time, cost, reliability, and satisfaction compared with existing architectures. The proposed SDNFV obtains high satisfaction of 90&#x0025; compared with the others. In the future, we can focus on security in this architecture and add multiple SDNFV nodes to the orchestration architecture at different locations. The multiple nodes will help further increase the efficiency of this architecture.</p>
</sec>
</body>
<back><fn-group>
<fn fn-type="other">
<p><bold>Funding Statement:</bold> The authors received no specific funding for this study.</p>
</fn>
<fn fn-type="conflict">
<p><bold>Conflicts of Interest:</bold> The authors declare that they have no conflicts of interest to report regarding the present study.</p>
</fn>
</fn-group>
<ref-list content-type="authoryear">
<title>References</title>
<ref id="ref-1"><label>[1]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J. O.</given-names> <surname>Fajardo</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Liberal</surname></string-name>, <string-name><given-names>I.</given-names> <surname>Giannoulakis</surname></string-name>, <string-name><given-names>E.</given-names> <surname>Kafetzakis</surname></string-name>, <string-name><given-names>V.</given-names> <surname>Pii</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Introducing mobile edge computing capabilities through distributed 5G cloud enabled small cells</article-title>,&#x201D; <source>Mobile Networks and Applications</source>, vol. <volume>21</volume>, no. <issue>4</issue>, pp. <fpage>564</fpage>&#x2013;<lpage>574</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-2"><label>[2]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>N.</given-names> <surname>ISG</surname></string-name></person-group>, &#x201C;<article-title>Network functions virtualisation (nfv)-network operator perspectives on industry progress</article-title>,&#x201D; <source>ETSI, Tech</source>, no. 1, <year>2013</year>.</mixed-citation></ref>
<ref id="ref-3"><label>[3]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>R.</given-names> <surname>Chaudhary</surname></string-name>, <string-name><given-names>G. S.</given-names> <surname>Aujla</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Kumar</surname></string-name> and <string-name><given-names>J. J.</given-names> <surname>Rodrigues</surname></string-name></person-group>, &#x201C;<article-title>Optimized big data management across multi-cloud data centers: Software-defined-network-based analysis</article-title>,&#x201D; <source>IEEE Communications Magazine</source>, vol. <volume>56</volume>, no. <issue>2</issue>, pp. <fpage>118</fpage>&#x2013;<lpage>126</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-4"><label>[4]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>R.</given-names> <surname>Mahmud</surname></string-name>, <string-name><given-names>R.</given-names> <surname>Kotagiri</surname></string-name> and <string-name><given-names>R.</given-names> <surname>Buyya</surname></string-name></person-group>, &#x201C;<article-title>Fog computing: A taxonomy, survey and future directions</article-title>,&#x201D; in <source>Internet of Everything</source>, <edition>1st edition</edition>, <publisher-name>Springer</publisher-name>, <publisher-loc>Cham</publisher-loc>, pp. <fpage>103</fpage>&#x2013;<lpage>130</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-5"><label>[5]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>B.</given-names> <surname>Varghese</surname></string-name> and <string-name><given-names>R.</given-names> <surname>Buyya</surname></string-name></person-group>, &#x201C;<article-title>Next generation cloud computing: New trends and research directions</article-title>,&#x201D; <source>Future Generation Computer Systems</source>, vol. <volume>79</volume>, pp. <fpage>849</fpage>&#x2013;<lpage>861</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-6"><label>[6]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>H.</given-names> <surname>Wu</surname></string-name>, <string-name><given-names>Z.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Guan</surname></string-name>, <string-name><given-names>K.</given-names> <surname>Wolter</surname></string-name> and <string-name><given-names>M.</given-names> <surname>Xu</surname></string-name></person-group>, &#x201C;<article-title>Collaborate edge and cloud computing with distributed deep learning for smart city internet of things</article-title>,&#x201D; <source>IEEE Internet of Things Journal</source>, vol. <volume>7</volume>, no. <issue>9</issue>, pp. <fpage>8099</fpage>&#x2013;<lpage>8110</lpage>, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-7"><label>[7]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>R.</given-names> <surname>Mijumbi</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Serrat</surname></string-name>, <string-name><given-names>J. L.</given-names> <surname>Gorricho</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Bouten</surname></string-name>, <string-name><given-names>F.</given-names> <surname>De turck</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Network function virtualization: State-of-the-art and research challenges</article-title>,&#x201D; <source>IEEE Communications Surveys &#x0026; Tutorials</source>, vol. <volume>18</volume>, no. <issue>1</issue>, pp. <fpage>236</fpage>&#x2013;<lpage>262</lpage>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-8"><label>[8]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Z.</given-names> <surname>Lv</surname></string-name> and <string-name><given-names>W.</given-names> <surname>Xiu</surname></string-name></person-group>, &#x201C;<article-title>Interaction of edge-cloud computing based on SDN and NFV for next generation IoT</article-title>,&#x201D; <source>IEEE Internet of Things Journal</source>, vol. <volume>7</volume>, no. <issue>7</issue>, pp. <fpage>5706</fpage>&#x2013;<lpage>5712</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-9"><label>[9]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Wang</surname></string-name> and <string-name><given-names>D.</given-names> <surname>Li</surname></string-name></person-group>, &#x201C;<article-title>Adaptive computing optimization in software-defined network-based industrial internet of things with fog computing</article-title>,&#x201D; <source>Sensors</source>, vol. <volume>18</volume>, no. <issue>8</issue>, pp. 1&#x2013;14, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-10"><label>[10]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Liu</surname></string-name> and <string-name><given-names>Q.</given-names> <surname>Zhang</surname></string-name></person-group>, &#x201C;<article-title>Offloading schemes in mobile edge computing for ultra-reliable low latency communications</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>6</volume>, pp. <fpage>12825</fpage>&#x2013;<lpage>12837</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-11"><label>[11]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A. C.</given-names> <surname>Baktir</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Ozgovde</surname></string-name> and <string-name><given-names>C.</given-names> <surname>Ersoy</surname></string-name></person-group>, &#x201C;<article-title>How can edge computing benefit from software-defined networking: A survey, use cases, and future directions</article-title>,&#x201D; <source>IEEE Communications Surveys &#x0026; Tutorials</source>, vol. <volume>19</volume>, no. <issue>4</issue>, pp. <fpage>2359</fpage>&#x2013;<lpage>2391</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-12"><label>[12]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Peng</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Fajardo</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Sayyad Khodashenas</surname></string-name>, <string-name><given-names>B.</given-names> <surname>Blanco</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Liberal</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Qoe-oriented mobile edge service management leveraging SDN and NFV</article-title>,&#x201D; <source>Mobile Information Systems</source>, vol. <volume>2017</volume>, pp. 1&#x2013;14, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-13"><label>[13]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>T.</given-names> <surname>Choi</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Kang</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Yoon</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Yang</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Song</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>SuVMF: Software-defined unified virtual monitoring function for SDN-based large-scale networks</article-title>,&#x201D; in <conf-name>Proc. CFI, ACM</conf-name>, <conf-loc>Tokyo</conf-loc>, <conf-loc>Japan</conf-loc>, pp. <fpage>1</fpage>&#x2013;<lpage>6</lpage>, <year>2014</year>.</mixed-citation></ref>
<ref id="ref-14"><label>[14]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>E.</given-names> <surname>Haleplidis</surname></string-name>, <string-name><given-names>J. H.</given-names> <surname>Salim</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Denazis</surname></string-name> and <string-name><given-names>O.</given-names> <surname>Koufopavlou</surname></string-name></person-group>, &#x201C;<article-title>Towards a network abstraction model for SDN</article-title>,&#x201D; <source>Journal of Network and Systems Management</source>, vol. <volume>23</volume>, no. <issue>2</issue>, pp. <fpage>309</fpage>&#x2013;<lpage>327</lpage>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-15"><label>[15]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Papavassiliou</surname></string-name></person-group>, &#x201C;<source>Software Defined Networking (SDN) and Network Function Virtualization (NFV)</source>,&#x201D; <publisher-name>Multidisciplinary Digital Publishing Institute</publisher-name>, vol. <volume>12</volume>, no. <issue>1</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>3</lpage>, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-16"><label>[16]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Stamou</surname></string-name>, <string-name><given-names>G.</given-names> <surname>Kakkavas</surname></string-name>, <string-name><given-names>K.</given-names> <surname>Tsitseklis</surname></string-name>, <string-name><given-names>V.</given-names> <surname>Karyotis</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Papavassiliou</surname></string-name></person-group>, &#x201C;<article-title>Autonomic network management and cross-layer optimization in software defined radio environments</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>11</volume>, no. <issue>2</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>18</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-17"><label>[17]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Leivadeas</surname></string-name>, <string-name><given-names>G.</given-names> <surname>Kesidis</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Ibnkahla</surname></string-name> and <string-name><given-names>I.</given-names> <surname>Lambadaris</surname></string-name></person-group>, &#x201C;<article-title>VNF placement optimization at the edge and cloud</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>11</volume>, no. <issue>3</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>13</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-18"><label>[18]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Yao</surname></string-name>, <string-name><given-names>Z.</given-names> <surname>Han</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Sohail</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Wang</surname></string-name></person-group>, &#x201C;<article-title>A robust security architecture for SDN-based 5G networks</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>11</volume>, no. <issue>4</issue>, pp. <fpage>85</fpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-19"><label>[19]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>G.</given-names> <surname>Mitsis</surname></string-name>, <string-name><given-names>P. A.</given-names> <surname>Apostolopoulos</surname></string-name>, <string-name><given-names>E. E.</given-names> <surname>Tsiropoulou</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Papavassiliou</surname></string-name></person-group>, &#x201C;<article-title>Intelligent dynamic data offloading in a competitive mobile edge computing market</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>11</volume>, no. <issue>5</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>19</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-20"><label>[20]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>V.</given-names> <surname>Eramo</surname></string-name>, <string-name><given-names>F. G.</given-names> <surname>Lavacca</surname></string-name>, <string-name><given-names>T.</given-names> <surname>Catena</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Polverini</surname></string-name> and <string-name><given-names>A.</given-names> <surname>Cianfrani</surname></string-name></person-group>, &#x201C;<article-title>Effectiveness of segment routing technology in reducing the bandwidth and cloud resources provisioning times in network function virtualization architectures</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>11</volume>, no. <issue>3</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>20</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-21"><label>[21]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>V.</given-names> <surname>Gkioulos</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Gunleifsen</surname></string-name> and <string-name><given-names>G. K.</given-names> <surname>Weldehawaryat</surname></string-name></person-group>, &#x201C;<article-title>A systematic literature review on military software defined networks</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>10</volume>, no. <issue>9</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>39</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-22"><label>[22]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Mimidis Kentis</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Soler</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Veitch</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Broadbent</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Mobilio</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>The next generation platform as a service: Composition and deployment of platforms and services</article-title>,&#x201D; <source>Future Internet</source>, vol. <volume>11</volume>, no. <issue>5</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>20</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-23"><label>[23]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>P.</given-names> <surname>Porambage</surname></string-name>, <string-name><given-names>J. O.</given-names> <surname>Kwuibe</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Liyanage</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Ylianttila</surname></string-name> and <string-name><given-names>T.</given-names> <surname>Taleb</surname></string-name></person-group>, &#x201C;<article-title>Survey on multi-access edge computing for internet of things realization</article-title>,&#x201D; <source>IEEE Communications Surveys &#x0026; Tutorials</source>, vol. <volume>20</volume>, no. <issue>4</issue>, pp. <fpage>2961</fpage>&#x2013;<lpage>2991</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-24"><label>[24]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Lin</surname></string-name>, <string-name><given-names>W.</given-names> <surname>Yu</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Yang</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Zhang</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>A survey on internet of things: Architecture, enabling technologies, security and privacy, and applications</article-title>,&#x201D; <source>IEEE Internet of Things Journal</source>, vol. <volume>4</volume>, no. <issue>5</issue>, pp. <fpage>1125</fpage>&#x2013;<lpage>1142</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-25"><label>[25]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>D.</given-names> <surname>Miorandi</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Sicari</surname></string-name>, <string-name><given-names>F.</given-names> <surname>De Pellegrini</surname></string-name> and <string-name><given-names>I.</given-names> <surname>Chlamtac</surname></string-name></person-group>, &#x201C;<article-title>Internet of things: Vision, applications and research challenges</article-title>,&#x201D; <source>Ad hoc Networks</source>, vol. <volume>10</volume>, no. <issue>7</issue>, pp. <fpage>1497</fpage>&#x2013;<lpage>1516</lpage>, <year>2012</year>.</mixed-citation></ref>
</ref-list>
</back>
</article>