sensors
Review Recent Advances in Collaborative Scheduling of Computing Tasks in an Edge Computing Paradigm
Shichao Chen 1,2 , Qijie Li 3 , Mengchu Zhou 1,4,5,* and Abdullah Abusorrah 5
1 Faculty of Information Tecnology, Macau University of Science and Technology, Macau 999078, China; [email protected] 2 The State Key Laboratory for Management and Control of Complex Systems, Institute of Automation, Chinese Academy of Sciences, Beijing 100190, China 3 School of Mechanical and Electrical Engineering and Automation, Harbin Institute of Technology, Shenzhen 518000, China; [email protected] 4 Department of Electrical and Computer Engineering, New Jersey Institute of Technology, Newark, NJ 07102, USA 5 Department of Electrical and Computer Engineering, Faculty of Engineering, and Center of Research Excellence in Renewable Energy and Power Systems, King Abdulaziz University, Jeddah 21481, Saudi Arabia; [email protected] * Correspondence: [email protected]
Abstract: In edge computing, edge devices can offload their overloaded computing tasks to an edge server. This can give full play to an edge server’s advantages in computing and storage, and efficiently execute computing tasks. However, if they together offload all the overloaded computing tasks to an edge server, it can be overloaded, thereby resulting in the high processing delay of many computing tasks and unexpectedly high energy consumption. On the other hand, the resources in idle edge devices may be wasted and resource-rich cloud centers may be underutilized. Therefore, it
is essential to explore a computing task collaborative scheduling mechanism with an edge server, a cloud center and edge devices according to task characteristics, optimization objectives and system
Citation: Chen, S.; Li, Q.; Zhou, M.; status. It can help one realize efficient collaborative scheduling and precise execution of all computing Abusorrah, A. Recent Advances in tasks. This work analyzes and summarizes the edge computing scenarios in an edge computing Collaborative Scheduling of paradigm. It then classifies the computing tasks in edge computing scenarios. Next, it formulates the Computing Tasks in an Edge optimization problem of computation offloading for an edge computing system. According to the Computing Paradigm. Sensors 2021, problem formulation, the collaborative scheduling methods of computing tasks are then reviewed. 21, 779. https://doi.org/10.3390/ Finally, future research issues for advanced collaborative scheduling in the context of edge computing s21030779 are indicated.
Received: 28 December 2020 Keywords: collaborative scheduling; edge computing; internet of things; limited resources; optimiza- Accepted: 12 January 2021 tion; task offloading Published: 24 January 2021
Publisher’s Note: MDPI stays neutral with regard to jurisdictional claims in 1. Introduction published maps and institutional affil- iations. With the increasing deployment and application of Internet of Things (IoT), more and more intelligent devices, e.g., smart sensors and smart phones, can access a network, resulting in a considerable amount of network data. Despite that their computing power is very rapidly increasing, they are unable to achieve real-time and efficient execution due to their limited computing resources and ever-demanding applications. When it faces highly Copyright: © 2021 by the authors. Licensee MDPI, Basel, Switzerland. complex computing tasks and services, cloud computing [1,2] can process these tasks to This article is an open access article achieve device–cloud collaboration. In a cloud computing paradigm, users can rely on distributed under the terms and extremely rich storage and computing resources of a cloud computing center to expand the conditions of the Creative Commons computing and storage power of devices, and achieve the rapid processing of computing- Attribution (CC BY) license (https:// intensive tasks. Yet there are some disadvantages in the device–cloud collaboration mode, creativecommons.org/licenses/by/ such as incurring high transmission delay and pushing network bandwidth requirement 4.0/). to the limit.
Sensors 2021, 21, 779. https://doi.org/10.3390/s21030779 https://www.mdpi.com/journal/sensors Sensors 2021, 21, 779 2 of 22
In order to solve the problems of cloud computing for data processing, edge com- puting [3,4] is put forward to provide desired computing services [5] for users by using computing, network, storage and other resources on edge, that is near a physical entity or data source. Compared with cloud computing, some applications of users in edge computing can be processed on an edge server near intelligent devices, thus significantly reducing data transmission delay and network bandwidth load required in edge-cloud collaboration. Eliminating long-distance data transmissions encountered in device–cloud computing brings another advantage to edge computing, i.e., the latter can more effectively guarantee user data security. As a result, it has become an important development trend to use edge computing to accomplish various computing tasks for intelligent devices [6,7]. These devices are called edge devices in this paper. The traditional scheduling strategies of edge computing tasks are to offload all computing-intensive tasks of edge devices to an edge server for processing [8–10]. How- ever, it may result in the waste of computing and storage sources in edge devices and cloud computing centers. In addition, many devices may access an edge server at the same time period. As a result, the server may face too many computing tasks, thus resulting in a long queue of tasks. This increases the completion time of all queued tasks, even causing the processing delay of tasks in the edge server to exceed that at the edge devices. On the other hand, many edge devices may be idle, resulting in a waste of their computing resources; and resource-rich cloud centers may be underutilized. To solve the above problems, we can combine a cloud center, edge servers and edge devices together to efficiently handle the computing tasks of edge devices via task offloading. According to the computing tasks’ characteristics, optimization objectives and system status, we should utilize the computing and storage resources of a cloud center, edge servers and edge devices, and schedule computing tasks to them for processing on demand. It can effectively reduce the load of edge servers and improve the utilization of resources, and reduce the average completion time of computing tasks in a system. This paper focuses on the important problem of collaborative scheduling of com- puting tasks in an edge computing paradigm under IoT. It is noted that edge computing systems can be viewed as a special class of distributed computing systems. Traditional task scheduling in distributed computing focuses on distributing and scheduling a large task into multiple similarly powerful computing nodes and do not have task off-loading issues in edging computing [9–12]. Edging computing arises to handle an IoT scenario where edge devices are resource-constrained and relatively independent. In Section2, we analyze the edge computing scenarios, and clarify their composition, characteristics and application fields. In Section3, we analyze the computing tasks, and classify them together with factors influencing their completion. We formulate the optimization problem of computation offloading with multiple objective functions for an edge computing system in Section4. Based on the computing scenarios, computation tasks and formulated optimization model, we survey and summarize the collaborative scheduling methods of computing tasks in Section5. This work is concluded in Section6 by indicating the open issues for us to build a desired collaborative scheduling system for edge computing.
2. Computing Scenarios In IoT, computing resources on edge are mainly composed of edge devices and edge servers. In order to take the advantages of cloud centers, we also consider them as part of the whole system in task scheduling. In general, a cloud center contains a large number of computing servers with high computing power. It is very important to reasonably use the computing, storage, bandwidth and other system resources to process computing tasks efficiently. In this section, different computing scenarios are analyzed and summarized according to the composition of computing resources. On the edge, we have an edge server, edge devices and an edge scheduler. The server can provide computing, storage, bandwidth and other resources to support computing services for the edge computing tasks. Edge devices can execute computing tasks and Sensors 2021, 21, x FOR PEER REVIEW 3 of 22
On the edge, we have an edge server, edge devices and an edge scheduler. The server can provide computing, storage, bandwidth and other resources to support computing Sensors 2021, 21, 779 services for the edge computing tasks. Edge devices can execute computing3 of 22 tasks and may offload such tasks to the server and other available/idle edge devices. They have compu- ting, storage, network and other resources, and can provide limited computing services mayfor offloadedge computing such tasks to tasks. the server They and have other much available/idle fewer resources edge devices. than Theyedge haveservers do. An edge computing,scheduler storage, receives network the computing and other resources,tasks offloa andded can by provide edge limited devices, computing and provides schedul- servicesing services for edge for computing the edge tasks. computing They have tasks much according fewer resources to the than resources edge servers and do. status of all edge An edge scheduler receives the computing tasks offloaded by edge devices, and provides schedulingservers and services edge for devices the edge under computing its supervision. tasks according It is to a thecontroller resources to and realize status the collaborative ofscheduling all edge servers between and edge edge devices servers under and its supervision.edge devices. It is aBut controller it does to not realize have the to be in an edge collaborativecomputing scheduling system. between edge servers and edge devices. But it does not have to be in anAccording edge computing to the system. difference among the computing resources involved in the offload- According to the difference among the computing resources involved in the offloading ing and scheduling of computing tasks in edge computing, computing scenarios can be and scheduling of computing tasks in edge computing, computing scenarios can be divided intodivided four categories, into four i.e., categories, basic, scheduler-based, i.e., basic, edge-cloud scheduler-based, computing, edge-cloud and scheduler- computing, and basedscheduler-based edge-cloud one. edge-cloud Their characteristics one. Their and characteristics application are described and application next. An edge are described next. computingAn edge architecturecomputing is architecture shown in Figure is1 .shown in Figure 1.
Cloud Sever
Core Networks
Edge Sever Edge Sever Edge Sever
End Users
FigureFigure 1. Edge1. Edge computing computing architecture. architecture.
2.1. Basic Edge Computing 2.1. Basic Edge Computing The first scenario is composed of edge devices and edge servers. There is no edge schedulerThe on first the edge.scenario In this is composed scenario, an of edge edge device devices can execute and edge a computing servers. task There is no edge locally,scheduler or offload on the it to edge. its edge In server.this scenario, The edge an server edge executes device it, can and thenexecute feeds a back computing task lo- thecally, computing or offload result it to to the its corresponding edge server. edgeThe device.edge server This scenario executes is similar it, and to then the feeds back the scene that devices offload tasks to be performed in a cloud computing center. It is the simplestcomputing scenario result in edge to the computing. corresponding There is noedge edge de schedulervice. This on scenario the edge. Foris similar the to the scene computingthat devices tasks offload that can tasks be offloaded to be performed to the edge servers, in a cloud their offloadingcomputing locations center. are It is the simplest fixed.scenario Moreover, in edge the processedcomputing. types There of computing is no ed tasksge scheduler are fixed, and on the the specific edge. types For the computing aretasks determined that can by be edge offloaded server resources. to the edge In addition, servers, this their scenario offloading does not locations contain a are fixed. More- cloudover, computing the processed center. types Hence, of it computing is more suitable tasks for are processing fixed, and tasks the with specific a small types are deter- amount of computation and strict delay requirements in a relatively closed environment. Itsmined architecture by edge is shown server in Figureresources.2, which In has addition, been used this in [ 11scenario]. does not contain a cloud com- putingAccording center. to theHence, above it analysis, is more the suitable Quality offo Servicer processing (QoS) levels tasks are with expected a small to be amount of com- achievedputation with and the strict proposed delay scenario. requirements Task completion in a relatively time is used closed to measure environment. QoS. We Its architecture assumeis shown that allin edgeFigure servers 2, which are same has and been all edge used devices in [11]. are uniform. Note that most of the presented content can be easily extended to heterogeneous devices and servers. According to the above analysis, the Quality of Service (QoS) levels are expected to be achieved with the proposed scenario. Task completion time is used to measure QoS. We assume that all edge servers are same and all edge devices are uniform. Note that most of the presented content can be easily extended to heterogeneous devices and servers. Let 𝜏 denote the completion time of a task offloaded to an edge server, which in- cludes data transmission latency between an edge device and an edge server, and task processing time in an edge server and waiting time before it is processed. Let denote
Sensors 2021, 21, x FOR PEER REVIEW 4 of 22
the time to run a single instruction and be the waiting time before a task to be pro- cessed in an edge server. 𝐺 is the number of instructions for this task processing. Then the completion time of a task can be computed as:
𝜏=𝑛(1+ 𝑃 )𝜏̅ + + 𝐺 (1) where 𝑛is the number of packets transmitted, which includes the process of bidirectional data transmission between an edge device and an edge server, 𝑃 is the packet loss rate between an edge device and an edge server, occurring during 𝑛 packet transmissions. 𝜏̅ Sensors 2021, 21, 779 4 of 22 is the average latency per packet between an edge device and an edge server, which in- cludes the sum of delays caused by processing, queuing, and transmission of 𝑛 packets.
MAN
Edge Server Edge Server Edge Server WLAN WLAN WLAN
FigureFigure 2. 2.Basic Basic edge edge computing computing (MAN: (MAN: metropolitan metropolitan area network area and network WLAN: wirelessand WLAN: local wireless local area areanetwork). network). Let τ denote the completion time of a task offloaded to an edge server, which includes data2.2. transmission Scheduler-Based latency betweenEdge Computing an edge device and an edge server, and task processing time in an edge server and waiting time before it is processed. Let η denote the time to run a singleThe instructionsecond one and Ωis becomposed the waiting of time edge before device a task tos, beedge processed servers in an and edge an edge scheduler. server.ComparedG is the with number the of first instructions one, it for includes this task an processing. edge scheduler, Then the completion which can time schedule tasks stra- oftegically. a task can beIn computedthis scenario, as: an edge device can process a computing task locally or offload its task to an edge scheduler. The edge scheduler reasonably schedules the tasks to edge τ = n(1 + Pτ )τ + Ω + ηG (1) servers and edge devices according to scheduling policies. The policies are formed based whereon then is current the number computing, of packets transmitted, storage, task which exec includesution the status, process network of bidirectional status, and other infor- data transmission between an edge device and an edge server, Pτ is the packet loss rate betweenmation an related edge device to all and edge an edge servers server, and occurring device durings. Finally,n packet the transmissions. schedulerτ feedsis the computing theresults average back latency to perthe packet source between devices. an edge The device main and feature an edge of server, this whichscenario includes is that the computing thetasks sum can of delays be reasonably caused by processing, scheduled queuing, to different and transmission servers ofandn packets. edge devices by the edge sched- 2.2.uler, Scheduler-Based so that the Edge collaborative Computing processing of computing tasks in different edge servers and edgeThe devices second one can is be composed well-realized. of edge devices, The computing edge servers resources and an edge of scheduler. edge devices can be fully Comparedutilized. withThe thetypes first one,of computing it includes an resources edge scheduler, on the which edge can are schedule diverse; tasks so are the types of strategically.computing In thistasks scenario, that can an edge be deviceprocessed. can process The acomputing computing task and locally storage or offload resources on the edge itsare task limited to an edge in comparison scheduler. The with edge schedulera cloud computing reasonably schedules center. the Clearly, tasks to this edge architecture is suit- servers and edge devices according to scheduling policies. The policies are formed based on theable current for computing,processing storage, tasks task with execution a small status, amount network status,of computation and other information and strict delay require- relatedments, to allas edgeshown servers in Figure and devices. 3. The Finally, study the scheduler[12] has feedsadopted the computing it. results back to the source devices. The main feature of this scenario is that the computing tasks can be reasonably scheduled to different servers and edge devices by the edge scheduler, so that the collaborative processing of computing tasks in different edge servers and edgeEdge MAN devices can be well-realized. The computing resources of edge devices can be fully utilized.Scheduler The types of computing resources on the edge are diverse; so are the types of computing tasks that can be processed. The computing and storage resources on the edge are limited in comparison with a cloud computing center. Clearly, this architecture is suitable for processing tasks with a small amount of computation and strict delay requirements, as shown in FigureEdge3. Server The study [12] has adoptedEdge Server it. Edge Server WLAN WLAN WLAN
Figure 3. Scheduler-based edge computing.
Sensors 2021, 21, x FOR PEER REVIEW 4 of 22
the time to run a single instruction and be the waiting time before a task to be pro- cessed in an edge server. 𝐺 is the number of instructions for this task processing. Then the completion time of a task can be computed as:
𝜏=𝑛(1+ 𝑃 )𝜏̅ + + 𝐺 (1) where 𝑛is the number of packets transmitted, which includes the process of bidirectional data transmission between an edge device and an edge server, 𝑃 is the packet loss rate between an edge device and an edge server, occurring during 𝑛 packet transmissions. 𝜏̅ is the average latency per packet between an edge device and an edge server, which in- cludes the sum of delays caused by processing, queuing, and transmission of 𝑛 packets.
MAN
Edge Server Edge Server Edge Server WLAN WLAN WLAN
Figure 2. Basic edge computing (MAN: metropolitan area network and WLAN: wireless local area network).
2.2. Scheduler-Based Edge Computing The second one is composed of edge devices, edge servers and an edge scheduler. Compared with the first one, it includes an edge scheduler, which can schedule tasks stra- tegically. In this scenario, an edge device can process a computing task locally or offload its task to an edge scheduler. The edge scheduler reasonably schedules the tasks to edge servers and edge devices according to scheduling policies. The policies are formed based on the current computing, storage, task execution status, network status, and other infor- mation related to all edge servers and devices. Finally, the scheduler feeds the computing results back to the source devices. The main feature of this scenario is that the computing tasks can be reasonably scheduled to different servers and edge devices by the edge sched- uler, so that the collaborative processing of computing tasks in different edge servers and edge devices can be well-realized. The computing resources of edge devices can be fully utilized. The types of computing resources on the edge are diverse; so are the types of computing tasks that can be processed. The computing and storage resources on the edge Sensors 2021, 21, 779 are limited in comparison with a cloud computing center. Clearly, this architecture is5 ofsuit- 22 able for processing tasks with a small amount of computation and strict delay require- ments, as shown in Figure 3. The study [12] has adopted it.
Edge MAN Scheduler
Edge Server Edge Server Edge Server WLAN WLAN WLAN
FigureFigure 3. 3.Scheduler-based Scheduler-based edge edge computing. computing.
According to this scenario, the task can be scheduled to an edge server for handling by an edge scheduler. Similar to the first scenario, the completion time of the task scheduled to a target edge server can be computed as: