<?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" xml:lang="en" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CMC</journal-id>
<journal-id journal-id-type="nlm-ta">CMC</journal-id>
<journal-id journal-id-type="publisher-id">CMC</journal-id>
<journal-title-group>
<journal-title>Computers, Materials &#x0026; Continua</journal-title>
</journal-title-group>
<issn pub-type="epub">1546-2226</issn>
<issn pub-type="ppub">1546-2218</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">59616</article-id>
<article-id pub-id-type="doi">10.32604/cmc.2024.059616</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>An Asynchronous Data Transmission Policy for Task Offloading in Edge-Computing Enabled Ultra-Dense IoT</article-title>
<alt-title alt-title-type="left-running-head">An Asynchronous Data Transmission Policy for Task Offloading in Edge-Computing Enabled Ultra-Dense IoT</alt-title>
<alt-title alt-title-type="right-running-head">An Asynchronous Data Transmission Policy for Task Offloading in Edge-Computing Enabled Ultra-Dense IoT</alt-title>
</title-group>
<contrib-group>
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western"><surname>Wang</surname><given-names>Dayong</given-names></name><xref ref-type="aff" rid="aff-1">1</xref><email>wangdayong@graduate.utm.my</email></contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western"><surname>Bakar</surname><given-names>Kamalrulnizam Bin Abu</given-names></name><xref ref-type="aff" rid="aff-1">1</xref></contrib>
<contrib id="author-3" contrib-type="author">
<name name-style="western"><surname>Isyaku</surname><given-names>Babangida</given-names></name><xref ref-type="aff" rid="aff-2">2</xref></contrib>
<contrib id="author-4" contrib-type="author">
<name name-style="western"><surname>Lei</surname><given-names>Liping</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, Faculty of Computing, Universiti Teknologi Malaysia</institution>, <addr-line>Johor Bahru, 81310, Johor</addr-line>, <country>Malaysia</country></aff>
<aff id="aff-2"><label>2</label><institution>Department of Computer Science, Faculty of Information Communication Technology, Sule Lamido University</institution>, <addr-line>Kafin Hausa, 741103, Jigawa</addr-line>, <country>Nigeria</country></aff>
<aff id="aff-3"><label>3</label><institution>School of Political Science and Public Administration, East China University of Political Science and Law</institution>, <addr-line>Shanghai, 201620</addr-line>, <country>China</country></aff>
</contrib-group>
<author-notes>
<corresp id="cor1"><label>&#x002A;</label>Corresponding Author: Dayong Wang. Email: <email>wangdayong@graduate.utm.my</email></corresp>
</author-notes>
<pub-date date-type="collection" publication-format="electronic">
<year>2024</year>
</pub-date>
<pub-date date-type="pub" publication-format="electronic">
<day>19</day><month>12</month><year>2024</year>
</pub-date>
<volume>81</volume>
<issue>3</issue>
<fpage>4465</fpage>
<lpage>4483</lpage>
<history>
<date date-type="received">
<day>13</day>
<month>10</month>
<year>2024</year>
</date>
<date date-type="accepted">
<day>14</day>
<month>11</month>
<year>2024</year>
</date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2024 The Authors.</copyright-statement>
<copyright-year>2024</copyright-year>
<copyright-holder>Published by Tech Science Press.</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_CMC_59616.pdf"></self-uri>
<abstract>
<p>In recent years, task offloading and its scheduling optimization have emerged as widely discussed and significant topics. The multi-objective optimization problems inherent in this domain, particularly those related to resource allocation, have been extensively investigated. However, existing studies predominantly focus on matching suitable computational resources for task offloading requests, often overlooking the optimization of the task data transmission process. This inefficiency in data transmission leads to delays in the arrival of task data at computational nodes within the edge network, resulting in increased service times due to elevated network transmission latencies and idle computational resources. To address this gap, we propose an Asynchronous Data Transmission Policy (ADTP) for optimizing data transmission for task offloading in edge-computing enabled ultra-dense IoT. ADTP dynamically generates data transmission scheduling strategies by jointly considering task offloading decisions and the fluctuating operational states of edge computing-enabled IoT networks. In contrast to existing methods, the Deep Deterministic Policy Gradient (DDPG) based task data transmission scheduling module works asynchronously with the Deep Q-Network (DQN) based Virtual Machine (VM) selection module in ADTP. This significantly reduces the computational space required for the scheduling algorithm. The continuous dynamic adjustment of data transmission bandwidth ensures timely delivery of task data and optimal utilization of network bandwidth resources. This reduces the task completion time and minimizes the failure rate caused by timeouts. Moreover, the VM selection module only performs the next inference step when a new task arrives or when a task finishes its computation. As a result, the wastage of computational resources is further reduced. The simulation results indicate that the proposed ADTP reduced average data transmission delay and service time by 7.11% and 8.09%, respectively. Furthermore, the task failure rate due to network congestion decreased by 68.73%.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>Bandwidth allocation</kwd>
<kwd>edge computing</kwd>
<kwd>internet of things</kwd>
<kwd>task offloading</kwd>
<kwd>reinforcement learning</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>The rapid development of the Internet of Things (IoT) and the continuous complexity of application scenarios have indeed led to a significant increase in the computational load on terminal devices (TDs) [<xref ref-type="bibr" rid="ref-1">1</xref>,<xref ref-type="bibr" rid="ref-2">2</xref>]. This led to the issue of slow response times for application services becoming particularly pronounced due to the insufficient computational capacity of TDs [<xref ref-type="bibr" rid="ref-3">3</xref>]. Task offloading technology allows TDs to submit computational tasks to edge-computing networks or cloud platforms, reducing the computational load on the TDs [<xref ref-type="bibr" rid="ref-4">4</xref>,<xref ref-type="bibr" rid="ref-5">5</xref>].</p>
<p>The most commonly applied task offloading paradigm involves TDs offloading computation-intensive tasks to cloud platforms or edge-computing networks [<xref ref-type="bibr" rid="ref-6">6</xref>]. TDs submit task offloading requests to nearby computing networks via wireless access networks and upload the data associated with the computational tasks [<xref ref-type="bibr" rid="ref-7">7</xref>]. As the number of terminal devices continues to rise, numerous computation-intensive jobs have begun to compete for resources in the edge network [<xref ref-type="bibr" rid="ref-8">8</xref>]. This trend has placed immense pressure on the network services at the wireless access layer, leading to network congestion [<xref ref-type="bibr" rid="ref-9">9</xref>]. Compared to cloud computing, edge-computing systems have relatively limited bandwidth resources. The coexistence of numerous devices poses challenges for bandwidth allocation. Additionally, reducing data processing latency is also a pressing issue that needs to be addressed [<xref ref-type="bibr" rid="ref-10">10</xref>].</p>
<p>Indeed, both computational and transmission delays play a critical role in influencing the overall efficacy of task offloading [<xref ref-type="bibr" rid="ref-11">11</xref>]. However, existing research has focused extensively on optimizing computational resource allocation, while considerations for transmission optimization remain relatively limited. Concurrent data uploads can lead to severe wireless network congestion, particularly in densely populated networks [<xref ref-type="bibr" rid="ref-12">12</xref>]. Therefore, the completion time of tasks increases due to the failure of task data to arrive at the corresponding virtual machine (VM) promptly. Thus, it is essential to optimize the data transmission process for task scheduling based on effective network bandwidth allocation strategies. However, such problems have been proven NP-hard due to their complex optimization requirements and dynamic environments [<xref ref-type="bibr" rid="ref-13">13</xref>]. This means that it is challenging to find an algorithm that can guarantee an optimal solution within polynomial time.</p>
<p>The common bandwidth allocation mechanism involves assigning different priorities to the data streams of tasks [<xref ref-type="bibr" rid="ref-14">14</xref>,<xref ref-type="bibr" rid="ref-15">15</xref>]. However, this can result in low-priority data experiencing significant transmission delays [<xref ref-type="bibr" rid="ref-16">16</xref>]. Some studies [<xref ref-type="bibr" rid="ref-17">17</xref>,<xref ref-type="bibr" rid="ref-18">18</xref>] utilize M/M/1 queues to model task processing. However, this requires ensuring that the computing nodes have sufficient resources to handle incoming data at all times. This is challenging to guarantee in edge-computing networks. Additionally, heuristic bandwidth allocation methods, while providing near-optimal solutions, often lack scalability.</p>
<p>AI-based network resource scheduling methods can effectively handle more complex transmission demands and environmental constraints, thereby optimizing overall network performance [<xref ref-type="bibr" rid="ref-19">19</xref>,<xref ref-type="bibr" rid="ref-20">20</xref>]. However, existing research in this area primarily focuses on optimizing IoT data transmission and abstract data communication scheduling. Some AI-based resource scheduling methods aimed at task offloading take into account the varying transmission demands of task data and the constraints of available bandwidth. Nonetheless, they all lack efficient mechanisms for scheduling the network transmission of task data to align with the dynamic allocation of VM resources. To address the aforementioned issues, we propose an asynchronous data transmission policy for task offloading in edge-computing-enabled IoT. This policy takes into full account the delay associated with the arrival of task data at the target VM, thereby reducing resource wastage by dynamically allocating the limited available network bandwidth. Specifically, our main contributions are listed as follows:
<list list-type="bullet">
<list-item>
<p>Deconstructed the factors influencing task offloading efficiency and focused on the optimization of task data transmission in high-density task offloading scenarios. Subsequently, this NP-hard mixed integer nonlinear programming (MINLP) optimization problem was transformed into a Markov decision process (MDP) that can be solved using reinforcement learning techniques. Furthermore, the discrete nature of VM allocation was differentiated from the continuous characteristics of network bandwidth allocation to adapt to various reinforcement learning neural networks.</p></list-item>
<list-item>
<p>Proposed an Asynchronous Data Transmission Policy (ADTP) that jointly considers the matching of tasks with computational resources and network resource constraints to dynamically allocate network bandwidth. Additionally, ADTP incorporates Quality of Experience (QoE) feedback to refine the bandwidth allocation strategy. Consequently, task data can be uploaded promptly to the corresponding VMs for processing, while simultaneously reducing the computational cost of the scheduling algorithm.</p></list-item>
<list-item>
<p>Established a simulation environment and conducted extensive comparative experiments. The simulation results demonstrate that the proposed Asynchronous Data Transmission Policy (ADTP) utilizes limited network resources more effectively. Both the success rate of task execution and response time were enhanced due to the timely upload of task data to the corresponding virtual computing nodes.</p></list-item>
</list></p>
<p>The rest of this paper is organized as follows. <xref ref-type="sec" rid="s2">Section 2</xref> explained the relevant prior works. <xref ref-type="sec" rid="s3">Section 3</xref> describes the system model and formulates the optimization problem of task data transmission. <xref ref-type="sec" rid="s4">Section 4</xref> presents the proposed data transmission policy for IoT task offloading. The performance evaluation of the proposed policy is presented in <xref ref-type="sec" rid="s5">Section 5</xref>. Finally, we provide conclusions and future research works in <xref ref-type="sec" rid="s6">Section 6</xref>.</p>
</sec>
<sec id="s2">
<label>2</label>
<title>Related Work</title>
<p>Data transmission optimization based on network resource allocation has been investigated across various levels in tandem with the advancement of IoT and task offloading technologies. However, the majority of existing research fails to adequately address the optimization of data transmission within the context of task offloading scenarios.</p>
<p>In [<xref ref-type="bibr" rid="ref-21">21</xref>], channel resources are allocated based on the size of the task data to avoid transmission conflicts among IoT nodes. However, data size alone does not fully represent the multidimensional requirements for data transmission. In [<xref ref-type="bibr" rid="ref-22">22</xref>], the proposed transmission optimization method prioritizes data based on task deadlines; however, this prioritized transmission approach does not support parallel data transfers. In [<xref ref-type="bibr" rid="ref-23">23</xref>], a weighted fair queuing (WFQ) mechanism with delay constraints is employed to reduce overall latency. Nonetheless, fairness is not the requisite mode for task offloading data transmission. If resources for either communication or computation are insufficient, tasks must wait in the queue. Each upstream queue can only process upload tasks sequentially.</p>
<p>Compared to the aforementioned simple data transmission optimization schemes, heuristic and meta-heuristic algorithms can handle relatively complex data transmission constraints. In [<xref ref-type="bibr" rid="ref-24">24</xref>], an Index-Based Transmission Scheduling (IBTS) approach is employed to optimize the transmission of task data after offloading decisions. However, this scheme only considers data size and transmission rate, neglecting the timing constraints for task data arrival at the server. In [<xref ref-type="bibr" rid="ref-25">25</xref>], the proposed Grey Wolf Optimization (GWO) meta-heuristic method is utilized to optimize data transmission and reduce wireless communication energy consumption for terminal devices. Nonetheless, this method suffers from slow convergence and a tendency to get trapped in local optima.</p>
<p>AI-based data transmission schemes can manage a vast array of environmental parameters and task constraints, demonstrating robust capabilities for optimizing task data transmission in complex scenarios. In [<xref ref-type="bibr" rid="ref-26">26</xref>], an improved K-means algorithm is proposed for the automatic clustering of NB-IoT terminals, followed by the generation of a prioritized transmission sequence for task data. However, this method overlooks the impact of the delay in task data arrival at the edge server on task completion time. In [<xref ref-type="bibr" rid="ref-27">27</xref>], the proposed approach utilizes deep neural networks (DNN) to learn data transmission characteristics for each time slot and dynamically adjust the allocation of wireless communication resources. However, this method primarily focuses on optimizing network throughput, latency, and the conflict rate of data transmissions.</p>
<p>The advancement of deep reinforcement learning (DRL) techniques offers improved solutions for optimizing task data transmission due to their ability to automatically adapt to dynamic changes in the network environment. In [<xref ref-type="bibr" rid="ref-28">28</xref>], multiple Deep Q-Learning Networks (DQN) are employed for the dynamic scheduling of network transmission states and data transmission requirements, optimizing channel allocation and throughput. Similarly, DDQN has also been applied to dynamically allocate time slot resources across multiple channels [<xref ref-type="bibr" rid="ref-29">29</xref>]. However, these approaches primarily optimize at the packet transmission level and lack awareness of the overall structure of task data.</p>
<p>To address such independent optimization challenges, hybrid solutions that integrate multiple techniques have been proposed. However, existing methods struggle to flexibly coordinate the discrete nature of the VM selection problem with the continuous nature of the bandwidth allocation issue [<xref ref-type="bibr" rid="ref-30">30</xref>&#x2013;<xref ref-type="bibr" rid="ref-32">32</xref>]. Moreover, the expansion of network scale and the proliferation of numerous application tasks impose constraints on reinforcement learning agents in tackling high-dimensional problems, as this may give rise to the curse of dimensionality. In [<xref ref-type="bibr" rid="ref-33">33</xref>], a hierarchical DDPG (HDDPG) framework was proposed, which first optimizes the data communication process and subsequently addresses the computational resource allocation problem. However, the use of two synchronously operating DDPG neural networks introduces relatively high computational costs.</p>
<p>To address these challenges, we propose an Asynchronous Data Transmission Policy (ADTP) for task offloading in edge-computing enabled ultra-dense IoT environment.</p>
</sec>
<sec id="s3">
<label>3</label>
<title>System Model and Problem Formulation</title>
<p>In this section, an edge-computing enabled IoT task-offloading network architecture is presented. Additionally, we describe the system model including the task computing model and the data communication model for IoT task offloading. Subsequently, the problem of minimizing task completion time is formulated as a Markov Decision Process (MDP).</p>
<p>We consider a typical edge-computing enabled IoT network architecture as shown in <xref ref-type="fig" rid="fig-1">Fig. 1</xref>. Similar scenario designs are widely adopted [<xref ref-type="bibr" rid="ref-34">34</xref>]. There is a set of TDs communicating with the edge-computing network via bandwidth-limited wireless connections. The communication between the edge-computing network and the cloud platform utilizes Wide Area Network (WAN) connections. Within the edge-computing network, multiple data centers are interconnected through high-speed networks. The orchestrator in the edge-computing network is responsible for allocating virtual machine resources and wireless bandwidth to tasks from TDs based on task offloading requests and the operational state of the network. Consequently, the completion time of a task is equal to the transmission time of the task data plus the execution time of the task on the virtual machine. Each Access Point (AP) has the same total available bandwidth. The ADTP dynamically adjusts the bandwidth allocated for the transmission of each task data in each time slot. <xref ref-type="fig" rid="fig-1">Fig. 1</xref> illustrates the system architecture of task offloading in Multi-access Edge Computing (MEC).</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>The system architecture of task offloading in MEC</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-1.tif"/>
</fig>
<p>To describe the problem under investigation, let the system&#x2019;s operating time be <inline-formula id="ieqn-1"><mml:math id="mml-ieqn-1"><mml:mi>T</mml:mi></mml:math></inline-formula> with time slots <inline-formula id="ieqn-2"><mml:math id="mml-ieqn-2"><mml:mi>t</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mn>2</mml:mn><mml:mo>,</mml:mo><mml:mo>&#x2026;</mml:mo><mml:mo>,</mml:mo><mml:mi>T</mml:mi><mml:mo>}</mml:mo></mml:mrow></mml:math></inline-formula>, where each time slot has a duration of <inline-formula id="ieqn-3"><mml:math id="mml-ieqn-3"><mml:mi mathvariant="normal">&#x0394;</mml:mi><mml:mi>t</mml:mi></mml:math></inline-formula>. The total number of tasks and virtual machines are denoted as <inline-formula id="ieqn-4"><mml:math id="mml-ieqn-4"><mml:mi>I</mml:mi><mml:mo>&#x2208;</mml:mo><mml:msup><mml:mrow><mml:mrow><mml:mi mathvariant="double-struck">Z</mml:mi></mml:mrow></mml:mrow><mml:mrow><mml:mo>+</mml:mo></mml:mrow></mml:msup></mml:math></inline-formula> and <inline-formula id="ieqn-5"><mml:math id="mml-ieqn-5"><mml:mi>J</mml:mi><mml:mo>&#x2208;</mml:mo><mml:msup><mml:mrow><mml:mrow><mml:mi mathvariant="double-struck">Z</mml:mi></mml:mrow></mml:mrow><mml:mrow><mml:mo>+</mml:mo></mml:mrow></mml:msup></mml:math></inline-formula>, respectively. Additionally, each task waiting to be offloaded has multiple attributes defined as <inline-formula id="ieqn-6"><mml:math id="mml-ieqn-6"><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>, where <inline-formula id="ieqn-7"><mml:math id="mml-ieqn-7"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> represents the computational resources required by the task (in MIPS), <inline-formula id="ieqn-8"><mml:math id="mml-ieqn-8"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> denotes the size of the task data (in bytes), and <inline-formula id="ieqn-9"><mml:math id="mml-ieqn-9"><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> indicates the time sensitivity of the task. Furthermore, each computing node is defined as <inline-formula id="ieqn-10"><mml:math id="mml-ieqn-10"><mml:msub><mml:mi>v</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>, where <inline-formula id="ieqn-11"><mml:math id="mml-ieqn-11"><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> represents the computational resources (in MIPS), <inline-formula id="ieqn-12"><mml:math id="mml-ieqn-12"><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> denotes the data storage resources (in bytes), <inline-formula id="ieqn-13"><mml:math id="mml-ieqn-13"><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> indicates the type of platform where the VM is located (1 for edge, 2 for cloud), and <inline-formula id="ieqn-14"><mml:math id="mml-ieqn-14"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> represents the resource utilization. Thus, the offloading decision variable <inline-formula id="ieqn-15"><mml:math id="mml-ieqn-15"><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> indicates whether the task is assigned to a virtual machine <inline-formula id="ieqn-16"><mml:math id="mml-ieqn-16"><mml:mi>j</mml:mi></mml:math></inline-formula>, this is a common definition in this type of research [<xref ref-type="bibr" rid="ref-20">20</xref>,<xref ref-type="bibr" rid="ref-22">22</xref>]:
<disp-formula id="eqn-1"><label>(1)</label><mml:math id="mml-eqn-1" display="block"><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mtable columnalign="left" rowspacing="4pt" columnspacing="1em"><mml:mtr><mml:mtd><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mspace width="1em" /><mml:mrow><mml:mtext>if</mml:mtext></mml:mrow><mml:mtext>&#x00A0;</mml:mtext><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mtext>&#x00A0;</mml:mtext><mml:mrow><mml:mtext>is assigned to&#xA0;</mml:mtext></mml:mrow><mml:msub><mml:mi>v</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mn>0</mml:mn><mml:mo>,</mml:mo><mml:mspace width="1em" /><mml:mrow><mml:mtext>&#xA0;otherwise</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable><mml:mo fence="true" stretchy="true" symmetric="true"></mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>Accepted offloaded tasks will be allocated computational resources <inline-formula id="ieqn-17"><mml:math id="mml-ieqn-17"><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> and network bandwidth resources <inline-formula id="ieqn-18"><mml:math id="mml-ieqn-18"><mml:msub><mml:mi>B</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>. However, not all tasks can be completed within the specified time due to various uncertainties. Therefore, we define the failure state of a task as:
<disp-formula id="eqn-2"><label>(2)</label><mml:math id="mml-eqn-2" display="block"><mml:msub><mml:mi>F</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mtable columnalign="left" rowspacing="4pt" columnspacing="1em"><mml:mtr><mml:mtd><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:mspace width="1em" /><mml:mrow><mml:mtext>if task&#xA0;</mml:mtext></mml:mrow><mml:mi>i</mml:mi><mml:mtext>&#x00A0;</mml:mtext><mml:mrow><mml:mtext>&#xA0;fails</mml:mtext></mml:mrow></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mn>0</mml:mn><mml:mo>,</mml:mo><mml:mspace width="1em" /><mml:mrow><mml:mtext>&#xA0;otherwise</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable><mml:mo fence="true" stretchy="true" symmetric="true"></mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>Consequently, the average task failure rate can be expressed as:
<disp-formula id="eqn-3"><label>(3)</label><mml:math id="mml-eqn-3" display="block"><mml:mover><mml:mi>F</mml:mi><mml:mo accent="false">&#x00AF;</mml:mo></mml:mover><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:mn>1</mml:mn><mml:mi>N</mml:mi></mml:mfrac><mml:munderover><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>F</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>In this case, the remote server operates in timesharing mode, which means multiple tasks can be executed in parallel on the server providing computational resources. The computational delay of the offloaded tasks can be expressed by:
<disp-formula id="eqn-4"><label>(4)</label><mml:math id="mml-eqn-4" display="block"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>c</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>&#x22C5;</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:mfrac></mml:math></disp-formula>where <inline-formula id="ieqn-19"><mml:math id="mml-ieqn-19"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> represents the computational resource demand of the task, and <inline-formula id="ieqn-20"><mml:math id="mml-ieqn-20"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> denotes the resource utilization for <inline-formula id="ieqn-21"><mml:math id="mml-ieqn-21"><mml:msub><mml:mrow><mml:mtext>VM</mml:mtext></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>. In addition to the computation time associated with tasks, another significant delay that contributes to the overall completion time is the transmission delay of task data. In the context of this study, multiple TDs are competing for the limited bandwidth of the wireless access network to upload their data to the edge-computing infrastructure. However, the transmission rate for each data transfer is subject to temporal fluctuations due to device mobility and intricate contention conflicts. Consequently, it is imperative to dynamically optimize the scheduling of available communication resources for each task&#x2019;s data within each time slot. <xref ref-type="fig" rid="fig-2">Fig. 2</xref> illustrates the fundamental principle of bandwidth adjustment for multiple data streams across time slots.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>The fundamental principle of bandwidth adjustment for multiple data streams</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-2.tif"/>
</fig>
<p>Here, the downstream network transmission delay is neglected due to the size of the task computation results being significantly smaller than the size of the uploaded data, and the downstream bandwidth typically being larger than the upstream bandwidth [<xref ref-type="bibr" rid="ref-35">35</xref>&#x2013;<xref ref-type="bibr" rid="ref-37">37</xref>]. The delay associated with the data transmission over the network can be denoted by:
<disp-formula id="eqn-5"><label>(5)</label><mml:math id="mml-eqn-5" display="block"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mfrac><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:msub><mml:mi>B</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:mrow></mml:mfrac><mml:mo>+</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>w</mml:mi><mml:mi>a</mml:mi><mml:mi>n</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-22"><mml:math id="mml-ieqn-22"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>w</mml:mi><mml:mi>a</mml:mi><mml:mi>n</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mn>0</mml:mn></mml:math></inline-formula> when the task is assigned to the edge server. For cloud computing, where data is transmitted over the Wide Area Network (WAN), the delay is modeled using an M/M/1 queue system due to the more complex nature of the transmission [<xref ref-type="bibr" rid="ref-38">38</xref>]. Thus, service delays can be expressed as:
<disp-formula id="eqn-6"><label>(6)</label><mml:math id="mml-eqn-6" display="block"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>c</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></disp-formula></p>
<p>In high-density IoT networks, the substantial volume of upload data streams from terminal devices (TDs) competes for the limited available bandwidth of the wireless access network. The data associated with tasks should be transmitted to the matched computing nodes at appropriate times. Therefore, the optimization objective for bandwidth resource allocation is to minimize the service time of tasks while improving resource utilization: <inline-formula id="ieqn-23"><mml:math id="mml-ieqn-23"><mml:mo movablelimits="true" form="prefix">min</mml:mo><mml:munderover><mml:mo>&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>, while also enhancing the Quality of Experience (QoE): <inline-formula id="ieqn-24"><mml:math id="mml-ieqn-24"><mml:mo movablelimits="true" form="prefix">max</mml:mo><mml:mi>U</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mi>Q</mml:mi><mml:mi>o</mml:mi><mml:mi>E</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>. Consequently, the objective function can be expressed as:</p>
<p><disp-formula id="eqn-7"><label>(7)</label><mml:math id="mml-eqn-7" display="block"><mml:mtable columnalign="left" rowspacing="4pt" columnspacing="1em"><mml:mtr><mml:mtd><mml:mo movablelimits="true" form="prefix">min</mml:mo><mml:mrow><mml:mi>&#x1D4AA;</mml:mi></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:munderover><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:mfrac><mml:mn>1</mml:mn><mml:mi>M</mml:mi></mml:mfrac><mml:munderover><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>j</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>M</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>U</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub><mml:mi>Q</mml:mi><mml:mi>o</mml:mi><mml:mi>E</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msub><mml:munderover><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mrow><mml:mtext>s</mml:mtext></mml:mrow><mml:mo>.</mml:mo><mml:mrow><mml:mtext>t</mml:mtext></mml:mrow><mml:mo>.</mml:mo><mml:mrow><mml:mtext>&#xA0;C</mml:mtext></mml:mrow><mml:mn>1</mml:mn><mml:mo>&#x003A;</mml:mo><mml:munderover><mml:mo movablelimits="false">&#x2211;</mml:mo><mml:mrow><mml:mi>i</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>N</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2264;</mml:mo><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>&#x22C5;</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:mn>1</mml:mn><mml:mo>&#x2212;</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>)</mml:mo></mml:mrow><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mi>j</mml:mi></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mrow><mml:mtext>&#xA0;C</mml:mtext></mml:mrow><mml:mn>2</mml:mn><mml:mo>&#x003A;</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>&#x003C;</mml:mo><mml:mn>1</mml:mn><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mi>j</mml:mi></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mrow><mml:mtext>&#xA0;C</mml:mtext></mml:mrow><mml:mn>3</mml:mn><mml:mo>&#x003A;</mml:mo><mml:munderover><mml:mo>&#x2211;</mml:mo><mml:mrow><mml:mi>j</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mrow><mml:mi>M</mml:mi></mml:mrow></mml:munderover><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mi mathvariant="normal">&#x2200;</mml:mi><mml:mi>i</mml:mi></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>where <inline-formula id="ieqn-25"><mml:math id="mml-ieqn-25"><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula> are weighting coefficients and <inline-formula id="ieqn-26"><mml:math id="mml-ieqn-26"><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>w</mml:mi><mml:mrow><mml:mn>4</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>. The allocation of weights should be optimized according to the requirements of different application scenarios. Constraints C1 and C2 denote that the scheduler will not oversubscribe resources to tasks waiting for offloading. Constraints C3 specifies that each task can only be offloaded to a single computing node. For clarity, the main notations are shown in <xref ref-type="table" rid="table-1">Table 1</xref>. It is worth mentioning that the model can be enhanced by adding more parameters and constraints for different application contexts.</p>
<table-wrap id="table-1">
<label>Table 1</label>
<caption>
<title>List of main notations</title>
</caption>
<table frame="hsides">
<colgroup>
<col align="left"/>
<col align="left"/>
<col align="left"/>
<col align="left"/>
</colgroup>
<thead>
<tr>
<th>Symbol</th>
<th>Definition</th>
<th>Symbol</th>
<th>Definition</th>
</tr>
</thead>
<tbody>
<tr>
<td><inline-formula id="ieqn-27"><mml:math id="mml-ieqn-27"><mml:mi>I</mml:mi></mml:math></inline-formula></td>
<td>Total number of tasks</td>
<td><inline-formula id="ieqn-28"><mml:math id="mml-ieqn-28"><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>The <italic>i</italic>-th task</td>
</tr>
<tr>
<td><inline-formula id="ieqn-29"><mml:math id="mml-ieqn-29"><mml:mi>J</mml:mi></mml:math></inline-formula></td>
<td>Total number of VMs</td>
<td><inline-formula id="ieqn-30"><mml:math id="mml-ieqn-30"><mml:mi>t</mml:mi></mml:math></inline-formula></td>
<td>Time slot</td>
</tr>
<tr>
<td><inline-formula id="ieqn-31"><mml:math id="mml-ieqn-31"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Computing resources required</td>
<td><inline-formula id="ieqn-32"><mml:math id="mml-ieqn-32"><mml:msub><mml:mi>v</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>The <italic>j</italic>-th VM</td>
</tr>
<tr>
<td><inline-formula id="ieqn-33"><mml:math id="mml-ieqn-33"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Size of the task data</td>
<td><inline-formula id="ieqn-34"><mml:math id="mml-ieqn-34"><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Time sensitivity of the task i</td>
</tr>
<tr>
<td><inline-formula id="ieqn-35"><mml:math id="mml-ieqn-35"><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Computing resources of the VM</td>
<td><inline-formula id="ieqn-36"><mml:math id="mml-ieqn-36"><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Storage space for VM j</td>
</tr>
<tr>
<td><inline-formula id="ieqn-37"><mml:math id="mml-ieqn-37"><mml:msub><mml:mi>P</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>The type of platform</td>
<td><inline-formula id="ieqn-38"><mml:math id="mml-ieqn-38"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Resource utilization of the VM</td>
</tr>
<tr>
<td><inline-formula id="ieqn-39"><mml:math id="mml-ieqn-39"><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Task offloading decision</td>
<td><inline-formula id="ieqn-40"><mml:math id="mml-ieqn-40"><mml:msub><mml:mi>F</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Failed task</td>
</tr>
<tr>
<td><inline-formula id="ieqn-41"><mml:math id="mml-ieqn-41"><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Allocated computing resources</td>
<td><inline-formula id="ieqn-42"><mml:math id="mml-ieqn-42"><mml:msub><mml:mi>B</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Allocated network resources</td>
</tr>
<tr>
<td><inline-formula id="ieqn-43"><mml:math id="mml-ieqn-43"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>c</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Task calculation delay</td>
<td><inline-formula id="ieqn-44"><mml:math id="mml-ieqn-44"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Data transmission delay</td>
</tr>
<tr>
<td><inline-formula id="ieqn-45"><mml:math id="mml-ieqn-45"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>w</mml:mi><mml:mi>a</mml:mi><mml:mi>n</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula></td>
<td>Data transmission delay on WAN</td>
<td><inline-formula id="ieqn-46"><mml:math id="mml-ieqn-46"><mml:mi>Q</mml:mi><mml:mi>o</mml:mi><mml:mi>E</mml:mi></mml:math></inline-formula></td>
<td>Quality of experience</td>
</tr>
<tr>
<td><inline-formula id="ieqn-47"><mml:math id="mml-ieqn-47"><mml:msub><mml:mi>s</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msubsup><mml:mi>s</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>State space</td>
<td><inline-formula id="ieqn-48"><mml:math id="mml-ieqn-48"><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msubsup><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup></mml:math></inline-formula></td>
<td>Action space</td>
</tr>
<tr>
<td><inline-formula id="ieqn-49"><mml:math id="mml-ieqn-49"><mml:mi>r</mml:mi><mml:mo>,</mml:mo><mml:msup><mml:mi>r</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:math></inline-formula></td>
<td>Reward function</td>
<td><inline-formula id="ieqn-50"><mml:math id="mml-ieqn-50"><mml:mi>w</mml:mi></mml:math></inline-formula></td>
<td>Weight coefficient of the objective</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4">
<label>4</label>
<title>Proposed Asynchronous Data Transmission Policy (ADTP) Based on Reinforcement Learning</title>
<p>In this section, we address the optimization problem presented in <xref ref-type="sec" rid="s3">Section 3</xref>. An asynchronous resource allocation-based data transmission optimization strategy is proposed, which aims to minimize the average completion time of tasks. This optimization method first utilizes Deep Q-Network (DQN) to determine the virtual machine to which task offloading requests are assigned. Subsequently, it employs a Deep Deterministic Policy Gradient (DDPG) approach to dynamically generate bandwidth allocation decisions for task data transmission. <xref ref-type="fig" rid="fig-3">Fig. 3</xref> illustrates the proposed Asynchronous Data Transmission Protocol (ADTP) logical framework. Furthermore, the VM allocation decisions are event-driven and are not repeated in every time slot to reduce computational load and energy consumption. In contrast, adjustments to wireless communication resources occur in every time slot due to the mobility of the TD and the rapid changes in network conditions.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>The architecture of CRADTP</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-3.tif"/>
</fig>
<p>For VM allocation, we employ the widely recognized DQN-based approach to facilitate offloading decisions [<xref ref-type="bibr" rid="ref-39">39</xref>&#x2013;<xref ref-type="bibr" rid="ref-41">41</xref>]. The inputs to the DQN encompass the operational state of the edge network, the resource requirements of the tasks, and the failure rates associated with task offloading. The output generated by the decision-making algorithm is an allocation vector that delineates the offloading of tasks to designated VMs. The reward for the algorithm is derived from the weighted sum of the service time and user satisfaction of the offloaded tasks, thereby incentivizing optimal performance in task allocation. The state-action space and reward definitions for the reinforcement learning algorithm are as follows:</p>
<p><bold>State Space:</bold> Let <inline-formula id="ieqn-51"><mml:math id="mml-ieqn-51"><mml:mi>S</mml:mi></mml:math></inline-formula> represents the system state space. The current system state space <inline-formula id="ieqn-52"><mml:math id="mml-ieqn-52"><mml:mi>s</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mi>S</mml:mi></mml:math></inline-formula> is expressed as:</p>
<p><disp-formula id="eqn-8"><label>(8)</label><mml:math id="mml-eqn-8" display="block"><mml:msub><mml:mi>s</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:msubsup><mml:mi>d</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msubsup><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mspace width="0pt" /><mml:mo>,</mml:mo><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mspace width="0pt" /><mml:mo>,</mml:mo><mml:mover><mml:mi>F</mml:mi><mml:mo accent="false">&#x00AF;</mml:mo></mml:mover><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mspace width="0pt" /><mml:mo>,</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mspace width="0pt" /><mml:mo>,</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>,</mml:mo><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>}</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-53"><mml:math id="mml-ieqn-53"><mml:msubsup><mml:mi>d</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msubsup><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> denotes the distribution of the task on the virtual machine based on ongoing offloading decisions. <inline-formula id="ieqn-54"><mml:math id="mml-ieqn-54"><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> is the available MIPS on the server <inline-formula id="ieqn-55"><mml:math id="mml-ieqn-55"><mml:mi>j</mml:mi></mml:math></inline-formula>. <inline-formula id="ieqn-56"><mml:math id="mml-ieqn-56"><mml:mover><mml:mi>F</mml:mi><mml:mo accent="false">&#x00AF;</mml:mo></mml:mover><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> is the average task failure rate. <inline-formula id="ieqn-57"><mml:math id="mml-ieqn-57"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> is the service time. <inline-formula id="ieqn-58"><mml:math id="mml-ieqn-58"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> denotes the computational resource utilization of <inline-formula id="ieqn-59"><mml:math id="mml-ieqn-59"><mml:mi>V</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>. <inline-formula id="ieqn-60"><mml:math id="mml-ieqn-60"><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is the Computing resources required for the task <inline-formula id="ieqn-61"><mml:math id="mml-ieqn-61"><mml:mi>i</mml:mi></mml:math></inline-formula>. <inline-formula id="ieqn-62"><mml:math id="mml-ieqn-62"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is the data size of task <inline-formula id="ieqn-63"><mml:math id="mml-ieqn-63"><mml:mi>i</mml:mi></mml:math></inline-formula>.</p>
<p><bold>Action Space:</bold> The action space for the DQN algorithm will be the selection of a VM for a particular task. Thus, the action <inline-formula id="ieqn-64"><mml:math id="mml-ieqn-64"><mml:mi>a</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mi>A</mml:mi></mml:math></inline-formula> can be given by:</p>
<p><disp-formula id="eqn-9"><label>(9)</label><mml:math id="mml-eqn-9" display="block"><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:msub><mml:mi>d</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>}</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-65"><mml:math id="mml-ieqn-65"><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is the action to allocate task <inline-formula id="ieqn-66"><mml:math id="mml-ieqn-66"><mml:mi>i</mml:mi></mml:math></inline-formula> to <inline-formula id="ieqn-67"><mml:math id="mml-ieqn-67"><mml:mi>V</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>.</p>
<p><bold>Reward:</bold> The reward function will be designed to encourage the allocation of tasks to the servers that can minimize the expected completion time.</p>
<p><disp-formula id="eqn-10"><label>(10)</label><mml:math id="mml-eqn-10" display="block"><mml:mi>r</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:mi>a</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mi>v</mml:mi><mml:mi>Q</mml:mi><mml:mi>o</mml:mi><mml:mi>E</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-68"><mml:math id="mml-ieqn-68"><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula> and <inline-formula id="ieqn-69"><mml:math id="mml-ieqn-69"><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula> stand for the weight parameters, which indicate the preferences for service time and satisfaction. Here, <inline-formula id="ieqn-70"><mml:math id="mml-ieqn-70"><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:mn>0</mml:mn><mml:mo>,</mml:mo><mml:mn>1</mml:mn><mml:mo>]</mml:mo></mml:mrow></mml:math></inline-formula> and <inline-formula id="ieqn-71"><mml:math id="mml-ieqn-71"><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03B2;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>.</p>
<p>Overall, the DQN iteratively learns and generates offloading decisions for the matching of tasks and VMs. The pseudocode for the algorithm is presented in Algorithm 1.</p>
<fig id="fig-8">
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-8.tif"/>
</fig>
<p>As illustrated in Algorithm 1, the neural network and replay memory are initialized in the first line. The second line initiates a loop to iteratively execute the core functionalities of the algorithm at each time step. Lines 3 and 4 evaluate the necessity for offloading decisions and algorithm updates based on the current state of the edge network. The decision-making component remains inactive when no new offloading requests are received and no task computations are completed, thereby minimizing computational resource usage and energy consumption. Lines 6 to 9 execute the generation and output of resource-matching decisions based on reinforcement learning. Finally, Lines 10 to 12 are devoted to the periodic updating of the neural network to enhance its adaptability to scheduling optimizations. The core unit of the algorithm operates based on DQN, allocating VM resources for incoming task offloading requests in each time slot. Therefore, the algorithm has a time complexity of O(N).</p>
<p>In the context of the scenarios addressed in this study, we adopt the widely recognized DDPG-based [<xref ref-type="bibr" rid="ref-42">42</xref>&#x2013;<xref ref-type="bibr" rid="ref-44">44</xref>] approach to dynamically allocate bandwidth in each time slot, capitalizing on its self-learning capabilities and proficiency in generating continuous values. The state-action space and reward definitions for the reinforcement learning algorithm are as follows:</p>
<p><bold>State Space:</bold> The state space for the DDPG algorithm will represent the current state of the network regarding bandwidth allocation, which includes:</p>
<p><disp-formula id="eqn-11"><label>(11)</label><mml:math id="mml-eqn-11" display="block"><mml:msubsup><mml:mi>s</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>,</mml:mo><mml:mover><mml:mi>F</mml:mi><mml:mo accent="false">&#x00AF;</mml:mo></mml:mover><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>,</mml:mo><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>}</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-78"><mml:math id="mml-ieqn-78"><mml:msub><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> is the decision made by the DQN for offloading tasks to the VM. <inline-formula id="ieqn-79"><mml:math id="mml-ieqn-79"><mml:msub><mml:mi>R</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> denotes the computational resources of <inline-formula id="ieqn-80"><mml:math id="mml-ieqn-80"><mml:mi>V</mml:mi><mml:msub><mml:mi>M</mml:mi><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>. <inline-formula id="ieqn-81"><mml:math id="mml-ieqn-81"><mml:mover><mml:mi>F</mml:mi><mml:mo accent="false">&#x00AF;</mml:mo></mml:mover><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> represents the average task failure rate. <inline-formula id="ieqn-82"><mml:math id="mml-ieqn-82"><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> is the service time of the task <inline-formula id="ieqn-83"><mml:math id="mml-ieqn-83"><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula>.</p>
<p><bold>Action Space:</bold> The action space for the DDPG algorithm will be the bandwidth allocation for each task in each time slot.</p>
<p><disp-formula id="eqn-12"><label>(12)</label><mml:math id="mml-eqn-12" display="block"><mml:msubsup><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:msub><mml:mi>B</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>}</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-84"><mml:math id="mml-ieqn-84"><mml:msubsup><mml:mi>a</mml:mi><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup></mml:math></inline-formula> is the bandwidth allocated to task <inline-formula id="ieqn-85"><mml:math id="mml-ieqn-85"><mml:msub><mml:mi>&#x03C4;</mml:mi><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub></mml:math></inline-formula> in time slot <inline-formula id="ieqn-86"><mml:math id="mml-ieqn-86"><mml:mi>t</mml:mi></mml:math></inline-formula>.</p>
<p><bold>Reward:</bold> The reward function for the DDPG algorithm will encourage efficient bandwidth allocation that minimizes the total transmission time for all tasks.</p>
<p><disp-formula id="eqn-13"><label>(13)</label><mml:math id="mml-eqn-13" display="block"><mml:msup><mml:mi>r</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup><mml:mrow><mml:mo>(</mml:mo><mml:msup><mml:mi>s</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup><mml:mo>,</mml:mo><mml:msup><mml:mi>a</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup><mml:mo>)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mo>&#x2212;</mml:mo><mml:mrow><mml:mo>(</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:msub><mml:mi>D</mml:mi><mml:mrow><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>i</mml:mi><mml:mo>,</mml:mo><mml:mi>j</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mi>v</mml:mi><mml:mi>Q</mml:mi><mml:mi>o</mml:mi><mml:mi>E</mml:mi><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub><mml:msub><mml:mi>C</mml:mi><mml:mrow><mml:mi>n</mml:mi><mml:mi>e</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mrow><mml:mo>(</mml:mo><mml:mi>t</mml:mi><mml:mo>)</mml:mo></mml:mrow><mml:mo>)</mml:mo></mml:mrow></mml:math></disp-formula>where <inline-formula id="ieqn-87"><mml:math id="mml-ieqn-87"><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mrow><mml:mtext>&#xA0;and&#xA0;</mml:mtext></mml:mrow><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub></mml:math></inline-formula> represent the weight parameters, which specify the preferences for service time, satisfaction and network utilization. Here, <inline-formula id="ieqn-88"><mml:math id="mml-ieqn-88"><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub><mml:mo>&#x2208;</mml:mo><mml:mrow><mml:mo>[</mml:mo><mml:mn>0</mml:mn><mml:mo>,</mml:mo><mml:mn>1</mml:mn><mml:mo>]</mml:mo></mml:mrow></mml:math></inline-formula> and <inline-formula id="ieqn-89"><mml:math id="mml-ieqn-89"><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msub><mml:mi>&#x03B4;</mml:mi><mml:mrow><mml:mn>3</mml:mn></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:math></inline-formula>.</p>
<p>The pseudocode for the algorithm is presented in Algorithm 2.</p>
<fig id="fig-9">
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-9.tif"/>
</fig>
<p>As illustrated in Algorithm 2, the Actor-Critic networks are created in Lines 1 and 2. Correspondingly, various hyper-parameters and the buffer for experience replay are initialized in Lines 3 and 4. Lines 5 to 7 establish three nested loops to iterate through each training epoch, each time slot, and each task. Lines 8 to 11 are dedicated to generating bandwidth allocation decisions and saving the replay memory records. Lines 13 to 18 conditionally execute model training. Finally, Lines 19 to 21 update the target networks when the update conditions are met. The time complexity of the DDPG part in the algorithm is linear. When the algorithm operates continuously in each time slots, the overall time complexity is O(N).</p>
</sec>
<sec id="s5">
<label>5</label>
<title>Performance Evaluation</title>
<p>In this section, we verify the performance of the proposed task data transmission policy through simulation experiments. We use EdgeCloudSim [<xref ref-type="bibr" rid="ref-34">34</xref>] as the foundational environment for task offloading simulation. Additionally, we extend the network transmission and virtual machine allocation modules of EdgeCloudSim. Thus, the proposed ADTP and the comparison algorithms can be implemented. The resource allocation module, based on deep neural networks, is implemented in PyTorch 3.8 and provides functional enhancements to EdgeCloudSim via a custom developed interface. The computer hardware comes with inter I7 CPU, 16 GB RAM to support the operation of the simulation environment. The detailed parameters of the experiments are shown in <xref ref-type="table" rid="table-2">Table 2</xref>.</p>
<table-wrap id="table-2">
<label>Table 2</label>
<caption>
<title>Simulation parameters</title>
</caption>
<table frame="hsides">
<colgroup>
<col align="left"/>
<col align="left"/>
</colgroup>
<thead>
<tr>
<th>Parameters</th>
<th>Value</th>
</tr>
</thead>
<tbody>
<tr>
<td>Iterations</td>
<td>50</td>
</tr>
<tr>
<td>Simulation time (minutes)</td>
<td>60</td>
</tr>
<tr>
<td>Number of VMs on cloud/edge network</td>
<td>4/28</td>
</tr>
<tr>
<td>Core of VM on cloud/edge network</td>
<td>4/2</td>
</tr>
<tr>
<td>MIPS of VM on cloud/edge network (MIPS)</td>
<td>10,000/1000</td>
</tr>
<tr>
<td>Ram of VM on cloud/edge network (MB)</td>
<td>32,000/2000</td>
</tr>
<tr>
<td>Storage of VM on cloud/edge network (Byte)</td>
<td>1,000,000/50,000</td>
</tr>
<tr>
<td>Bandwidth of WAN/WLAN/MAN (Mbps)</td>
<td>15/100/1000</td>
</tr>
<tr>
<td>Number of TDs</td>
<td>100&#x007E;1200</td>
</tr>
<tr>
<td>Task length of AR/HA/HCA/IA (MI)</td>
<td>2000/400/3000/750</td>
</tr>
<tr>
<td>Data upload of AR/HA/HCA/IA (KB)</td>
<td>2100/1850/3000/725</td>
</tr>
<tr>
<td>Data download of AR/HA/HCA/IA (KB)</td>
<td>25/20/250/2500</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>In the context of task offloading, the most significant factors affecting user experience are delay and failure rate. Therefore, we concentrated on evaluating task data transmission delay, average service time, and the effects of various factors on task offloading failure rates to demonstrate the advantages of ADTP. To visually evaluate the performance of the proposed ADTP, the following benchmark strategies are simulated for comparison:
<list list-type="bullet">
<list-item>
<p><bold>Bandwidth Sharing (BS):</bold> This serves as the baseline. In this scheme, all tasks engage in unrestricted competition for data uploads.</p></list-item>
<list-item>
<p><bold>Relative-execution Deadline First (RDF):</bold> In this scheme, the priority of each task&#x2019;s data flow is dynamically adjusted based on deadlines when bandwidth resources become scarce [<xref ref-type="bibr" rid="ref-45">45</xref>].</p></list-item>
<list-item>
<p><bold>Double Deep Q-Network (DDQN):</bold> In this scheme, the bandwidth resources of the AP are divided into multiple virtual channels of identical performance. A deep learning network collects information on data transmission requests and network bandwidth conditions to dynamically optimize bandwidth allocation [<xref ref-type="bibr" rid="ref-46">46</xref>].</p></list-item>
<list-item>
<p><bold>Asynchronous Data Transmission Policy (ADTP):</bold> Proposed dynamic data transmission strategy based on asynchronous reinforcement learning to facilitate optimized scheduling of task data flows and enhance the overall performance of task offloading.</p></list-item>
</list></p>
<p>Network latency is the primary focus of this study. <xref ref-type="fig" rid="fig-4">Fig. 4</xref> compares the network latency of various solutions. The baseline free competition scheme exhibits lower performance due to a high incidence of conflicts during the competition process, resulting in a significant number of data transmission failures. In contrast, the RDF approach strives to ensure that multiple packets belonging to the same task are uploaded with priority. Furthermore, the DDQN-based solution is capable of comprehensively gathering information regarding data transmission requests and network bandwidth conditions to dynamically optimize bandwidth allocation, thereby demonstrating superior performance. However, it lacks awareness of task execution processes within the virtual machines (VMs). Additionally, the fixed-bandwidth allocation of network resources into virtual channels introduces a challenge related to excessive scheduling granularity. In contrast, the Asynchronous Data Transmission Policy (ADTP) holistically considers task offloading decisions and network conditions to deliver refined network resource allocations. Thus, this approach exhibits significantly higher performance.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>Average data transmission delay for (a) Augmented reality App; (b) Health App; (c) Infotainment App; (d) Heavy Comp. App</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-4.tif"/>
</fig>
<p>Additionally, network latency and computational latency together influence the overall service time for tasks. <xref ref-type="fig" rid="fig-5">Fig. 5</xref> presents a comparative analysis of service times for each application, further highlighting the relative advantages of the ADTP. This superiority is attributable to the fact that network transmission latency constitutes a critical component of overall service time. As the duration of task data transmission diminishes, there is a corresponding reduction in service time. It is noteworthy that the disparities in service times across the various schemes remain relatively minimal when the number of mobile devices is limited, as the data flow within the wireless network is not significantly congested. Conversely, the influence of data transmission scheduling on service time becomes markedly more pronounced as the number of mobile devices increases.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Service time for (a) Augmented reality App; (b) Health App; (c) Infotainment App; (d) Heavy Comp. App</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-5.tif"/>
</fig>
<p>While many factors can lead to task offloading failures, the primary challenges stem from inadequate computational resources and limited network transmission capabilities. As shown in <xref ref-type="fig" rid="fig-6">Fig. 6</xref>, both data upload conflicts and resource limitations of VMs are equally significant contributors to task failures when the number of TDs is relatively low. However, as the number of TDs increases, inefficient mechanisms for network resource allocation give rise to communication-related issues, which subsequently become the predominant factor leading to task failures. In this context, the proportion of task failures attributable to computational resource constraints exhibits a consistent decline. Conversely, the ADTP demonstrates effective data transmission optimization capabilities, which results in computational blocking becoming the main reason for task failures.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Failed task due to VM congestion for (a) Augmented reality App; (b) Health App; (c) Infotainment App; (d) Heavy Comp. App</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-6.tif"/>
</fig>
<p><xref ref-type="fig" rid="fig-7">Fig. 7</xref> illustrates the relationship between data transmission efficiency and task failure rates. Notably, tasks offloaded to the edge-computing network require data uploads solely through the wireless access network. In contrast, tasks directed to the cloud platform necessitate multi-hop data transmission through both the WAN and the wireless access network. This study concentrates exclusively on optimizing data transmission within the wireless access network, while the WAN is configured in a resource-sharing mode. Analysis of <xref ref-type="fig" rid="fig-7">Fig. 7</xref> reveals that when the density of task offloading is low, the influence of various network resource scheduling strategies on task failure rates is minimal. This phenomenon can be attributed to the capability of task data to reach computing nodes within an acceptable time frame. Conversely, as the volume of offloaded tasks escalates, the efficient scheduling facilitated by the ADTP significantly mitigates data transmission delays and failure rates, thereby resulting in a decreased overall task offloading failure rate.</p>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>Failed task due to data upload failure for (a) Augmented reality App; (b) Health App; (c) Infotainment App; (d) Heavy Comp. App</title>
</caption>
<graphic mimetype="image" mime-subtype="tif" xlink:href="CMC_59616-fig-7.tif"/>
</fig>
<p>In summary, the ADTP effectively monitors the requirements for task data transmission and the fluctuations in network operating conditions to generate optimized bandwidth resource allocation strategies. As a result, task data can be transmitted efficiently to VMs, rationally utilizing the available network bandwidth. Thus, the overall operational performance of the task offloading network is enhanced.</p>
</sec>
<sec id="s6">
<label>6</label>
<title>Conclusion</title>
<p>Task offloading technology has developed significantly in this information age. In this paper, we propose and focus on the optimization of data transmission within task offloading scheduling in high-density IoT network environments. To address this issue, we consider the dynamic allocation of available bandwidth for each uploaded task data stream, facilitating the efficient execution of tasks on virtual machines based on the timely arrival of task data at the virtual computing nodes. We propose an Asynchronous Data Transmission Policy (ADTP) to jointly consider the matching of tasks with virtual machines and the congestion status of the wireless access network. ADTP comprises two asynchronously functioning intelligent agents, each focusing on the discrete VM allocation decisions and the continuous bandwidth adjustment, aimed at optimizing the overall task offloading data transmission.</p>
<p>Experimental results indicate that ADTP effectively reduces network latency and improves data transmission efficiency in resource-constrained networks. Consequently, more tasks can be timely transferred to VM hosts for execution. This reduces the service time for task offloading and increases the success rate of task offloading. Notably, as the number of TDs increases, task offloading failures tend to be primarily driven by insufficient VM resources rather than transmission barriers. This further demonstrates that ADTP effectively optimizes the transmission process of task data.</p>
<p>The limitation of this study lies in its exclusive focus on optimizing the data uploads of task data from the terminal device, without addressing the optimization of data transmission from the edge network to the cloud. In future work, we aim to jointly optimize the data transmission process of task data within the edge-cloud continuum. Additionally, we will consider incorporating Spiking Neural Network (SNN) technology to reduce the computational costs and energy consumption of decision generation.</p>
</sec>
</body>
<back>
<ack>
<p>We thank UTM for supporting us during this work.</p>
</ack>
<sec><title>Funding Statement</title>
<p>The authors received no specific funding for this study.</p>
</sec>
<sec><title>Author Contributions</title>
<p>The authors confirm their contribution to the paper as follows: Dayong Wang contributed to conceptualization and writing&#x2014;original draft preparation, Babangida Isyaku and Dayong Wang contributed to methodology, Dayong Wang and Liping Lei contributed to integrate the results from multiple rounds of experiments and analysis, Babangida Isyaku and Kamalrulnizam Bin Abu Bakar contributed to writing reviews and editing, and Kamalrulnizam Bin Abu Bakar supervised the process of the research. All authors reviewed the results and approved the final version of the manuscript.</p>
</sec>
<sec sec-type="data-availability"><title>Availability of Data and Materials</title>
<p>Not applicable.</p>
</sec>
<sec><title>Ethics Approval</title>
<p>Not applicable.</p>
</sec>
<sec sec-type="COI-statement"><title>Conflicts of Interest</title>
<p>The authors declare no conflicts of interest to report regarding the present study.</p>
</sec>
<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>A.</given-names> <surname>Islam</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Debnath</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Ghose</surname></string-name>, and <string-name><given-names>S.</given-names> <surname>Chakraborty</surname></string-name></person-group>, &#x201C;<article-title>A survey on task offloading in multi-access edge computing</article-title>,&#x201D; <source>J. Syst. Archit.</source>, vol. <volume>118</volume>, <year>Sep. 2021</year>, <comment>Art. no. 102225</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.sysarc.2021.102225</pub-id>.</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>B.</given-names> <surname>Isyaku</surname></string-name>, <string-name><given-names>K. B. A</given-names> <surname>Bakar</surname></string-name>, <string-name><given-names>N. M.</given-names> <surname>Yusuf</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Abaker</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Abdelmaboud</surname></string-name> and <string-name><given-names>W.</given-names> <surname>Nagmeldin</surname></string-name></person-group>, &#x201C;<article-title>Software defined wireless sensor load balancing routing for internet of things applications: Review of approaches</article-title>,&#x201D; <source>Heliyon</source>, vol. <volume>10</volume>, <year>May 2024</year>. doi: <pub-id pub-id-type="doi">10.1016/j.heliyon.2024.e29965</pub-id>; <pub-id pub-id-type="pmid">38698990</pub-id></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>N.</given-names> <surname>Kumari</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Yadav</surname></string-name>, and <string-name><given-names>P. K.</given-names> <surname>Jana</surname></string-name></person-group>, &#x201C;<article-title>Task offloading in fog computing: A survey of algorithms and optimization techniques</article-title>,&#x201D; <source>Comput. Netw.</source>, vol. <volume>214</volume>, <year>Sep. 2022</year>, <comment>Art. no. 109137</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.comnet.2022.109137</pub-id>.</mixed-citation></ref>
<ref id="ref-4"><label>[4]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Dong</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Xia</surname></string-name>, and <string-name><given-names>J.</given-names> <surname>Kamruzzaman</surname></string-name></person-group>, &#x201C;<article-title>Quantum particle swarm optimization for task offloading in mobile edge computing</article-title>,&#x201D; <source>IEEE Trans. Ind. Inform.</source>, vol. <volume>19</volume>, no. <issue>8</issue>, pp. <fpage>9113</fpage>&#x2013;<lpage>9122</lpage>, <year>Aug. 2023</year>. doi: <pub-id pub-id-type="doi">10.1109/TII.2022.3225313</pub-id>.</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>W.</given-names> <surname>Dayong</surname></string-name>, <string-name><given-names>K. B. A.</given-names> <surname>Bakar</surname></string-name>, <string-name><given-names>B.</given-names> <surname>Isyaku</surname></string-name>, <string-name><given-names>T. A. E.</given-names> <surname>Eisa</surname></string-name>, and <string-name><given-names>A.</given-names> <surname>Abdelmaboud</surname></string-name></person-group>, &#x201C;<article-title>A comprehensive review on internet of things task offloading in multi-access edge computing</article-title>,&#x201D; <source>Heliyon</source>, vol. <volume>10</volume>, no. <issue>9</issue>, <year>May 2024</year>. doi: <pub-id pub-id-type="doi">10.1016/j.heliyon.2024.e29916</pub-id>; <pub-id pub-id-type="pmid">38698997</pub-id></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>A.</given-names> <surname>Javadpour</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Nafei</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Ja&#x2019;fari</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Pinto</surname></string-name>, <string-name><given-names>W.</given-names> <surname>Zhang</surname></string-name> and <string-name><given-names>A. K.</given-names> <surname>Sangaiah</surname></string-name></person-group>, &#x201C;<article-title>An intelligent energy-efficient approach for managing IoE tasks in cloud platforms</article-title>,&#x201D; <source>J. Ambient Intell. Humaniz. Comput.</source>, vol. <volume>14</volume>, no. <issue>4</issue>, pp. <fpage>3963</fpage>&#x2013;<lpage>3979</lpage>, <year>Apr. 2023</year>. doi: <pub-id pub-id-type="doi">10.1007/s12652-022-04464-x</pub-id>.</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>C.</given-names> <surname>Feng</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Han</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>B.</given-names> <surname>Yang</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Liu</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Guo</surname></string-name></person-group>, &#x201C;<article-title>Computation offloading in mobile edge computing networks: A survey</article-title>,&#x201D; <source>J. Netw. Comput. Appl.</source>, vol. <volume>202</volume>, <year>Jun. 2022</year>, <comment>Art. no. 103366</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.jnca.2022.103366</pub-id>.</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>A.</given-names> <surname>Javadpour</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>An energy-optimized embedded load balancing using DVFS computing in cloud data centers</article-title>,&#x201D; <source>Comput. Commun.</source>, vol. <volume>197</volume>, pp. <fpage>255</fpage>&#x2013;<lpage>266</lpage>, <year>Jan. 2023</year>. doi: <pub-id pub-id-type="doi">10.1016/j.comcom.2022.10.019</pub-id>.</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>M. Y.</given-names> <surname>Akhlaqi</surname></string-name> and <string-name><given-names>Z. B.</given-names> <surname>Mohd Hanapi</surname></string-name></person-group>, &#x201C;<article-title>Task offloading paradigm in mobile edge computing-current issues, adopted approaches, and future directions</article-title>,&#x201D; <source>J. Netw. Comput. Appl.</source>, vol. <volume>212</volume>, <year>Mar. 2023</year>, <comment>Art. no. 103568</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.jnca.2022.103568</pub-id>.</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>Zhang</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Joint resource allocation for latency-sensitive services over mobile edge computing networks with caching</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, vol. <volume>6</volume>, no. <issue>3</issue>, pp. <fpage>4283</fpage>&#x2013;<lpage>4294</lpage>, <year>Jun. 2019</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2018.2875917</pub-id>.</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>M. Z.</given-names> <surname>Khan</surname></string-name>, <string-name><given-names>O. H.</given-names> <surname>Alhazmi</surname></string-name>, <string-name><given-names>M. A.</given-names> <surname>Javed</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Ghandorh</surname></string-name>, and <string-name><given-names>K. S.</given-names> <surname>Aloufi</surname></string-name></person-group>, &#x201C;<article-title>Reliable internet of things: Challenges and future trends</article-title>,&#x201D; <source>Electronics</source>, vol. <volume>10</volume>, no. <issue>19</issue>, <year>Jan. 2021</year>, <comment>Art. no. 19</comment>. doi: <pub-id pub-id-type="doi">10.3390/electronics10192377</pub-id>.</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>B.</given-names> <surname>Jamil</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Ijaz</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Shojafar</surname></string-name>, <string-name><given-names>K.</given-names> <surname>Munir</surname></string-name>, and <string-name><given-names>R.</given-names> <surname>Buyya</surname></string-name></person-group>, &#x201C;<article-title>Resource allocation and task scheduling in fog computing and internet of everything environments: A taxonomy, review, and future directions</article-title>,&#x201D; <source>ACM Comput. Surv.</source>, vol. <volume>54</volume>, no. <issue>11s</issue>, pp. <fpage>233:1</fpage>&#x2013;<lpage>233:38</lpage>, <year>Sep. 2022</year>. doi: <pub-id pub-id-type="doi">10.1145/3513002</pub-id>.</mixed-citation></ref>
<ref id="ref-13"><label>[13]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Dong</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Task offloading strategies for mobile edge computing: A survey</article-title>,&#x201D; <source>Comput. Netw.</source>, vol. <volume>254</volume>, <year>Dec. 2024</year>, <comment>Art. no. 110791</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.comnet.2024.110791</pub-id>.</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>C.</given-names> <surname>Jong</surname></string-name>, <string-name><given-names>Y. C.</given-names> <surname>Kim</surname></string-name>, <string-name><given-names>J. H.</given-names> <surname>So</surname></string-name>, and <string-name><given-names>K. C.</given-names> <surname>Ri</surname></string-name></person-group>, &#x201C;<article-title>QoS and energy-efficiency aware scheduling and resource allocation scheme in LTE-A uplink systems</article-title>,&#x201D; <source>Telecommun. Syst.</source>, vol. <volume>82</volume>, no. <issue>2</issue>, pp. <fpage>175</fpage>&#x2013;<lpage>191</lpage>, <year>Feb. 2023</year>. doi: <pub-id pub-id-type="doi">10.1007/s11235-022-00980-5</pub-id>.</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>B.</given-names> <surname>Isyaku</surname></string-name>, <string-name><given-names>K. A.</given-names> <surname>Bakar</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Abdulrahman</surname></string-name>, <string-name><given-names>M. N.</given-names> <surname>Yusuf</surname></string-name>, <string-name><given-names>F. B.</given-names> <surname>Muchtar</surname></string-name> and <string-name><given-names>F. A.</given-names> <surname>Ghaleb</surname></string-name></person-group>, &#x201C;<chapter-title>Mobile device influence on SDN controller performance in IoT-managed software-defined wireless networks</chapter-title>,&#x201D; in <source>Advances in Intelligent Computing Techniques and Applications</source>, <person-group person-group-type="editor"><string-name><given-names>F.</given-names> <surname>Saeed</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Mohammed</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Fazea</surname></string-name></person-group>, Eds. <publisher-loc>Cham</publisher-loc>: <publisher-name>Springer Nature Switzerland</publisher-name>, <year>2024</year>, pp. <fpage>62</fpage>&#x2013;<lpage>72</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-031-59707-7_6</pub-id>.</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>B.</given-names> <surname>Isyaku</surname></string-name>, <string-name><given-names>K. B. A.</given-names> <surname>Bakar</surname></string-name>, <string-name><given-names>W.</given-names> <surname>Nagmeldin</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Abdelmaboud</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Saeed</surname></string-name> and <string-name><given-names>F. A.</given-names> <surname>Ghaleb</surname></string-name></person-group>, &#x201C;<article-title>Reliable failure restoration with bayesian congestion aware for software defined networks</article-title>,&#x201D; <source>Comput. Syst. Sci. Eng.</source>, vol. <volume>46</volume>, no. <issue>3</issue>, <year>2023</year>. doi: <pub-id pub-id-type="doi">10.32604/csse.2023.034509</pub-id>.</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>X.</given-names> <surname>Dai</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Task co-offloading for D2D-assisted mobile edge computing in industrial internet of things</article-title>,&#x201D; <source>IEEE Trans. Ind. Inform.</source>, vol. <volume>19</volume>, no. <issue>1</issue>, pp. <fpage>480</fpage>&#x2013;<lpage>490</lpage>, <year>Jan. 2023</year>. doi: <pub-id pub-id-type="doi">10.1109/TII.2022.3158974</pub-id>.</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>C.</given-names> <surname>Tang</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Zhu</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Guizani</surname></string-name>, and <string-name><given-names>J. J. P. C.</given-names> <surname>Rodrigues</surname></string-name></person-group>, &#x201C;<article-title>SDN-assisted mobile edge computing for collaborative computation offloading in industrial internet of things</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, vol. <volume>9</volume>, no. <issue>23</issue>, pp. <fpage>24253</fpage>&#x2013;<lpage>24263</lpage>, <year>Dec. 2022</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2022.3190281</pub-id>.</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>Y.</given-names> <surname>Li</surname></string-name> and <string-name><given-names>W.</given-names> <surname>Zhang</surname></string-name></person-group>, &#x201C;<article-title>Task-offloading strategy of mobile edge computing for WBANs</article-title>,&#x201D; <source>Electronics</source>, vol. <volume>13</volume>, no. <issue>8</issue>, <year>Jan. 2024</year>, <comment>Art. no. 8</comment>. doi: <pub-id pub-id-type="doi">10.3390/electronics13081422</pub-id>.</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>Y.</given-names> <surname>Dai</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Zhao</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Zhang</surname></string-name>, and <string-name><given-names>T.</given-names> <surname>Jiang</surname></string-name></person-group>, &#x201C;<article-title>Federated deep reinforcement learning for task offloading in digital twin edge networks</article-title>,&#x201D; <source>IEEE Trans. Netw. Sci. Eng.</source>, vol. <volume>11</volume>, no. <issue>3</issue>, pp. <fpage>2849</fpage>&#x2013;<lpage>2863</lpage>, <year>May 2024</year>. doi: <pub-id pub-id-type="doi">10.1109/TNSE.2024.3350710</pub-id>.</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>C. -W.</given-names> <surname>Huang</surname></string-name>, <string-name><given-names>S. -C.</given-names> <surname>Tseng</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Lin</surname></string-name>, and <string-name><given-names>Y.</given-names> <surname>Kawamoto</surname></string-name></person-group>, &#x201C;<article-title>Radio resource scheduling for narrowband internet of things systems: A performance study</article-title>,&#x201D; <source>IEEE Netw.</source>, vol. <volume>33</volume>, no. <issue>3</issue>, pp. <fpage>108</fpage>&#x2013;<lpage>115</lpage>, <year>May 2019</year>. doi: <pub-id pub-id-type="doi">10.1109/MNET.2018.1700386</pub-id>.</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>S.</given-names> <surname>Pandiyan</surname></string-name>, <string-name><given-names>T. S.</given-names> <surname>Lawrence</surname></string-name>, <string-name><given-names>V.</given-names> <surname>Sathiyamoorthi</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Ramasamy</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Xia</surname></string-name> and <string-name><given-names>Y.</given-names> <surname>Guo</surname></string-name></person-group>, &#x201C;<article-title>A performance-aware dynamic scheduling algorithm for cloud-based IoT applications</article-title>,&#x201D; <source>Comput. Commun.</source>, vol. <volume>160</volume>, pp. <fpage>512</fpage>&#x2013;<lpage>520</lpage>, <year>Jul. 2020</year>. doi: <pub-id pub-id-type="doi">10.1016/j.comcom.2020.06.016</pub-id>.</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>W. K. G.</given-names> <surname>Seah</surname></string-name>, <string-name><given-names>C. -H.</given-names> <surname>Lee</surname></string-name>, <string-name><given-names>Y. -D.</given-names> <surname>Lin</surname></string-name>, and <string-name><given-names>Y. -C.</given-names> <surname>Lai</surname></string-name></person-group>, &#x201C;<article-title>Combined communication and computing resource scheduling in sliced 5G multi-access edge computing systems</article-title>,&#x201D; <source>IEEE Trans. Veh. Technol.</source>, vol. <volume>71</volume>, no. <issue>3</issue>, pp. <fpage>3144</fpage>&#x2013;<lpage>3154</lpage>, <year>Mar. 2022</year>. doi: <pub-id pub-id-type="doi">10.1109/TVT.2021.3139026</pub-id>.</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>A.</given-names> <surname>Hazra</surname></string-name>, <string-name><given-names>P. K.</given-names> <surname>Donta</surname></string-name>, <string-name><given-names>T.</given-names> <surname>Amgoth</surname></string-name>, and <string-name><given-names>S.</given-names> <surname>Dustdar</surname></string-name></person-group>, &#x201C;<article-title>Cooperative transmission scheduling and computation offloading with collaboration of fog and cloud for industrial IoT applications</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, <year>2022</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2022.3150070</pub-id>.</mixed-citation></ref>
<ref id="ref-25"><label>[25]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>N.</given-names> <surname>Unnisa</surname></string-name> and <string-name><given-names>M.</given-names> <surname>Tatineni</surname></string-name></person-group>, &#x201C;<chapter-title>Intelligent allocation strategy of mobile users for multi-access edge computing resources</chapter-title>,&#x201D; <source>presented at 2021 Emerging Trends in Industry 4.0 (ETI 4.0)</source>, <publisher-loc>Raigarh, India</publisher-loc>, <year>May 2021</year>, pp. <fpage>1</fpage>&#x2013;<lpage>7</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ETI4.051663.2021.9619420</pub-id></mixed-citation></ref>
<ref id="ref-26"><label>[26]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>X.</given-names> <surname>Chen</surname></string-name>, <string-name><given-names>Z.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Chen</surname></string-name>, and <string-name><given-names>X.</given-names> <surname>Wang</surname></string-name></person-group>, &#x201C;<article-title>Performance analysis and uplink scheduling for QoS-aware NB-IoT networks in mobile computing</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>7</volume>, pp. <fpage>44404</fpage>&#x2013;<lpage>44415</lpage>, <year>2019</year>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2019.2908985</pub-id>.</mixed-citation></ref>
<ref id="ref-27"><label>[27]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Gao</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>W.</given-names> <surname>Zhuang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Shen</surname></string-name>, and <string-name><given-names>X.</given-names> <surname>Li</surname></string-name></person-group>, &#x201C;<article-title>MAC for machine-type communications in industrial IoT&#x2014;Part II: Scheduling and numerical results</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, vol. <volume>8</volume>, no. <issue>12</issue>, pp. <fpage>9958</fpage>&#x2013;<lpage>9969</lpage>, <year>Jun. 2021</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2020.3045831</pub-id>.</mixed-citation></ref>
<ref id="ref-28"><label>[28]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>N.</given-names> <surname>Jiang</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Deng</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Nallanathan</surname></string-name>, and <string-name><given-names>J. A.</given-names> <surname>Chambers</surname></string-name></person-group>, &#x201C;<article-title>Reinforcement learning for real-time optimization in NB-IoT networks</article-title>,&#x201D; <source>IEEE J. Sel. Areas Commun.</source>, vol. <volume>37</volume>, no. <issue>6</issue>, pp. <fpage>1424</fpage>&#x2013;<lpage>1440</lpage>, <year>Jun. 2019</year>. doi: <pub-id pub-id-type="doi">10.1109/JSAC.2019.2904366</pub-id>.</mixed-citation></ref>
<ref id="ref-29"><label>[29]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Wu</surname></string-name>, <string-name><given-names>G.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Nie</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Peng</surname></string-name>, and <string-name><given-names>Y.</given-names> <surname>Zhang</surname></string-name></person-group>, &#x201C;<article-title>Deep reinforcement learning for scheduling in an edge computing-based industrial internet of things</article-title>,&#x201D; <source>Wirel Commun. Mob. Comput.</source>, vol. <volume>2021</volume>, p. <fpage>e8017334</fpage>, <year>2021</year>. doi: <pub-id pub-id-type="doi">10.1155/2021/8017334</pub-id>.</mixed-citation></ref>
<ref id="ref-30"><label>[30]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>L. P.</given-names> <surname>Qian</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Wang</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Wu</surname></string-name>, and <string-name><given-names>B.</given-names> <surname>Lin</surname></string-name></person-group>, &#x201C;<article-title>Joint multi-domain resource allocation and trajectory optimization in UAV-assisted maritime IoT networks</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, vol. <volume>10</volume>, no. <issue>1</issue>, pp. <fpage>539</fpage>&#x2013;<lpage>552</lpage>, <year>Jan. 2023</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2022.3201017</pub-id>.</mixed-citation></ref>
<ref id="ref-31"><label>[31]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Y.</given-names> <surname>Gong</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Yao</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Wang</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Li</surname></string-name>, and <string-name><given-names>S.</given-names> <surname>Guo</surname></string-name></person-group>, &#x201C;<article-title>Edge intelligence-driven joint offloading and resource allocation for future 6G industrial internet of things</article-title>,&#x201D; <source>IEEE Trans. Netw. Sci. Eng.</source>, <year>2022</year>. doi: <pub-id pub-id-type="doi">10.1109/TNSE.2022.3141728</pub-id>.</mixed-citation></ref>
<ref id="ref-32"><label>[32]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Y.</given-names> <surname>Hao</surname></string-name>, <string-name><given-names>Z.</given-names> <surname>Song</surname></string-name>, <string-name><given-names>Z.</given-names> <surname>Zheng</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Zhang</surname></string-name>, and <string-name><given-names>Z.</given-names> <surname>Miao</surname></string-name></person-group>, &#x201C;<article-title>Joint communication, computing, and caching resource allocation in LEO satellite MEC networks</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>11</volume>, pp. <fpage>6708</fpage>&#x2013;<lpage>6716</lpage>, <year>2023</year>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2023.3237701</pub-id>.</mixed-citation></ref>
<ref id="ref-33"><label>[33]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>H.</given-names> <surname>Peng</surname></string-name> and <string-name><given-names>X.</given-names> <surname>Shen</surname></string-name></person-group>, &#x201C;<article-title>Deep reinforcement learning based resource management for multi-access edge computing in vehicular networks</article-title>,&#x201D; <source>IEEE Trans. Netw. Sci. Eng.</source>, vol. <volume>7</volume>, no. <issue>4</issue>, pp. <fpage>2416</fpage>&#x2013;<lpage>2428</lpage>, <year>Oct. 2020</year>. doi: <pub-id pub-id-type="doi">10.1109/TNSE.2020.2978856</pub-id>.</mixed-citation></ref>
<ref id="ref-34"><label>[34]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>C.</given-names> <surname>Sonmez</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>EdgeCloudSim: An environment for performance evaluation of edge computing systems</article-title>,&#x201D; <source>Transacti. Emerging Telecommunicati. Technologi</source>, vol. <volume>29</volume>, no. <issue>11</issue>, <year>2018</year>, <comment>Art. no. 3493</comment>. doi: <pub-id pub-id-type="doi">10.1002/ett.3493</pub-id>.</mixed-citation></ref>
<ref id="ref-35"><label>[35]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Y.</given-names> <surname>Chiang</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Management and orchestration of edge computing for IoT: A comprehensive survey</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, vol. <volume>10</volume>, no. <issue>16</issue>, pp. <fpage>14307</fpage>&#x2013;<lpage>14331</lpage>, <year>Aug. 2023</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2023.3245611</pub-id>.</mixed-citation></ref>
<ref id="ref-36"><label>[36]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>K.</given-names> <surname>Sadatdiynov</surname></string-name>, <string-name><given-names>L.</given-names> <surname>Cui</surname></string-name>, <string-name><given-names>L.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>J. Z.</given-names> <surname>Huang</surname></string-name>, <string-name><given-names>N. N.</given-names> <surname>Xiong</surname></string-name> and <string-name><given-names>C.</given-names> <surname>Luo</surname></string-name></person-group>, &#x201C;<article-title>An intelligent hybrid method: Multi-objective optimization for MEC-enabled devices of IoE</article-title>,&#x201D; <source>J. Parallel Distrib. Comput.</source>, vol. <volume>171</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>13</lpage>, <year>Jan. 2023</year>. doi: <pub-id pub-id-type="doi">10.1016/j.jpdc.2022.09.008</pub-id>.</mixed-citation></ref>
<ref id="ref-37"><label>[37]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>P.</given-names> <surname>Yang</surname></string-name>, <string-name><given-names>R.</given-names> <surname>Ma</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Yi</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>B.</given-names> <surname>Li</surname></string-name> and <string-name><given-names>Z.</given-names> <surname>Bai</surname></string-name></person-group>, &#x201C;<article-title>A computation offloading strategy for multi-access edge computing based on DQUIC protocol</article-title>,&#x201D; <source>J. Supercomput.</source>, vol. <volume>80</volume>, pp. <fpage>18285</fpage>&#x2013;<lpage>18318</lpage>, <year>May 2024</year>. doi: <pub-id pub-id-type="doi">10.1007/s11227-024-06176-9</pub-id>.</mixed-citation></ref>
<ref id="ref-38"><label>[38]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Roy</surname></string-name>, <string-name><given-names>J. L.</given-names> <surname>Pachuau</surname></string-name>, and <string-name><given-names>A. K.</given-names> <surname>Saha</surname></string-name></person-group>, &#x201C;<article-title>An overview of queuing delay and various delay based algorithms in networks</article-title>,&#x201D; <source>Computing</source>, vol. <volume>103</volume>, no. <issue>10</issue>, pp. <fpage>2361</fpage>&#x2013;<lpage>2399</lpage>, <year>Oct. 2021</year>. doi: <pub-id pub-id-type="doi">10.1007/s00607-021-00973-3</pub-id>.</mixed-citation></ref>
<ref id="ref-39"><label>[39]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>K.</given-names> <surname>Moghaddasi</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Rajabi</surname></string-name>, <string-name><given-names>F. S.</given-names> <surname>Gharehchopogh</surname></string-name>, and <string-name><given-names>A.</given-names> <surname>Ghaffari</surname></string-name></person-group>, &#x201C;<article-title>An advanced deep reinforcement learning algorithm for three-layer D2D-edge-cloud computing architecture for efficient task offloading in the Internet of Things</article-title>,&#x201D; <source>Sustain. Comput. Inform. Syst.</source>, vol. <volume>43</volume>, <year>Sep. 2024</year>, <comment>Art. no. 100992</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.suscom.2024.100992</pub-id>.</mixed-citation></ref>
<ref id="ref-40"><label>[40]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>I.</given-names> <surname>Khan</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Tao</surname></string-name>, <string-name><given-names>G. M. S.</given-names> <surname>Rahman</surname></string-name>, <string-name><given-names>W. U.</given-names> <surname>Rehman</surname></string-name>, and <string-name><given-names>T.</given-names> <surname>Salam</surname></string-name></person-group>, &#x201C;<article-title>Advanced energy-efficient computation offloading using deep reinforcement learning in MTC edge computing</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>8</volume>, pp. <fpage>82867</fpage>&#x2013;<lpage>82875</lpage>, <year>2020</year>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2020.2991057</pub-id>.</mixed-citation></ref>
<ref id="ref-41"><label>[41]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>L.</given-names> <surname>Ale</surname></string-name>, <string-name><given-names>N.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Fang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Chen</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Wu</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Li</surname></string-name></person-group>, &#x201C;<article-title>Delay-aware and energy-efficient computation offloading in mobile-edge computing using deep reinforcement learning</article-title>,&#x201D; <source>IEEE Trans. Cogn. Commun. Netw.</source>, vol. <volume>7</volume>, no. <issue>3</issue>, pp. <fpage>881</fpage>&#x2013;<lpage>892</lpage>, <year>Sep. 2021</year>. doi: <pub-id pub-id-type="doi">10.1109/TCCN.2021.3066619</pub-id>.</mixed-citation></ref>
<ref id="ref-42"><label>[42]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>H.</given-names> <surname>Mai Do</surname></string-name>, <string-name><given-names>T. P.</given-names> <surname>Tran</surname></string-name>, and <string-name><given-names>M.</given-names> <surname>Yoo</surname></string-name></person-group>, &#x201C;<article-title>Deep reinforcement learning-based task offloading and resource allocation for industrial IoT in MEC federation system</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>11</volume>, pp. <fpage>83150</fpage>&#x2013;<lpage>83170</lpage>, <year>2023</year>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2023.3302518</pub-id>.</mixed-citation></ref>
<ref id="ref-43"><label>[43]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>M. A.</given-names> <surname>Ebrahim</surname></string-name>, <string-name><given-names>G. A.</given-names> <surname>Ebrahim</surname></string-name>, <string-name><given-names>H. K.</given-names> <surname>Mohamed</surname></string-name>, and <string-name><given-names>S. O.</given-names> <surname>Abdellatif</surname></string-name></person-group>, &#x201C;<article-title>A deep learning approach for task offloading in multi-UAV aided mobile edge computing</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>10</volume>, pp. <fpage>101716</fpage>&#x2013;<lpage>101731</lpage>, <year>2022</year>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2022.3208584</pub-id>.</mixed-citation></ref>
<ref id="ref-44"><label>[44]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>D. S.</given-names> <surname>Lakew</surname></string-name>, <string-name><given-names>A. -T.</given-names> <surname>Tran</surname></string-name>, <string-name><given-names>N. -N.</given-names> <surname>Dao</surname></string-name>, and <string-name><given-names>S.</given-names> <surname>Cho</surname></string-name></person-group>, &#x201C;<article-title>Intelligent offloading and resource allocation in heterogeneous aerial access IoT networks</article-title>,&#x201D; <source>IEEE Internet Things J.</source>, vol. <volume>10</volume>, no. <issue>7</issue>, pp. <fpage>5704</fpage>&#x2013;<lpage>5718</lpage>, <year>Apr. 2023</year>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2022.3161571</pub-id>.</mixed-citation></ref>
<ref id="ref-45"><label>[45]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>C.</given-names> <surname>Xia</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Jin</surname></string-name>, <string-name><given-names>C.</given-names> <surname>Xu</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Wang</surname></string-name>, and <string-name><given-names>P.</given-names> <surname>Zeng</surname></string-name></person-group>, &#x201C;<article-title>Real-time scheduling under heterogeneous routing for industrial internet of things</article-title>,&#x201D; <source>Comput. Electr. Eng.</source>, vol. <volume>86</volume>, <year>Sep. 2020</year>, <comment>Art. no. 106740</comment>. doi: <pub-id pub-id-type="doi">10.1016/j.compeleceng.2020.106740</pub-id>.</mixed-citation></ref>
<ref id="ref-46"><label>[46]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>H.</given-names> <surname>Zhong</surname></string-name>, <string-name><given-names>R.</given-names> <surname>Sun</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Mei</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Chen</surname></string-name>, <string-name><given-names>F.</given-names> <surname>Jin</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Ning</surname></string-name></person-group>, &#x201C;<article-title>Deep grid scheduler for 5G NB-IoT uplink transmission</article-title>,&#x201D; <source>Secur. Commun. Netw.</source>, vol. <volume>2021</volume>, pp. <fpage>1</fpage>&#x2013;<lpage>10</lpage>, <year>Aug. 2021</year>. doi: <pub-id pub-id-type="doi">10.1155/2021/5263726</pub-id>.</mixed-citation></ref>
</ref-list>
</back></article>