This article has been accepted for publication in a future issue of this journal, but has not been

fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
1

High-performance Isolation Computing Technology

for Smart IoT Healthcare in Cloud Environments
Yin ZHANG Senior Member, IEEE1 , Yi SUN Member, IEEE 2,3
, Renchao JIN4 , Kaixiang LIN2,3 , and Wei LIU2,3
1
School of Information and Communication Engineering,
University of Electronic Science and Technology of China, Chengdu, China
2
School of Computer Science(National Pilot Software Engineering School),
Beijing University of Posts and Telecommunications, Beijing, China
3
National Engineering Laboratory for Mobile Network Security[No. [2013] 2685]
4
School of Computer Science and Technology,
Huazhong University of Science and Technology, Wuhan, China

Abstract—The development of the smart medical industry and
equipment has made great progress due to the fusion of the
IoT, cloud computing, and big data. In smart IoT healthcare,
patients can collect vital parameters from various medical sensors
attached to them to detect diseases and make initial diagnoses by
themselves. With the powerful storage and computing functions
of cloud computing, medical sensor devices deployed in a cloud
environment can effectively solve the problems that the devices
are highly dispersed, heterogeneous, and have limited processing
capabilities. As a result, this method can effectively provide
customized and scalable smart medical services for patients.
However, because these medical resources share computing re-
sources on the cloud platform, changes in equipment workloads
will lead to service performance competition among tenants.
Therefore, determining how to achieve performance isolation
between tenants and guarantee the service level agreements
(SLAs) of the tenants has become the most concerning issue
for cloud service providers. In this article, we propose a per-
formance isolation algorithm for multi-tenant IoT clouds, which
can effectively provide performance isolation between tenants.
Experiments show that the message processing delay of tenants
working within the allocated quota can be reduced by 82%.
Keywords: High-performance Isolation Technology, Smart
IoT Healthcare, Cloud Computing, Intelligent Medical Diag-
nosis
I. I NTRODUCTION
With the rapid development of Internet of Things healthcare,
multiple home medical equipment such as infrared thermome-
ter, blood pressure monitors, and heart rate monitor are already
quite common in people’s daily lives [1], [2]. Therefore,
patients can obtain personal medical diagnoses by uploading
their physical health data obtained from IoT medical devices
[3]to obtain professional healthcare advice from the cloud.
Furthermore, these types of personal service medical devices
are becoming more portable, accurate and specialized with the
rapid development of information technology [4], [5]. Like
e-commerce, it will be extremely convenient for patients to
obtain personalized and professional diagnostic report anytime
Corresponding Author: Yin ZHANG, yin.zhang.cn@ieee.org; Yi SUN,
sybupt@bupt.edu.cn
and anywhere, especially with the popular of IoT health-
care [6], [7]. Smart IoT healthcare in cloud environments [8] is
an irresistible and promising future trend in the medical field.
Traditionally, IoT application providers usually adopt cus-
tomized development mode to meet customers’ specific busi-
ness requirements. Although this service delivery mode has
promoted the rapid growth of the IoT business in the past few
years, its cost-effectiveness and scalability are very limited.
The emergence of IoT cloud applications brings new solutions
for the development and delivery of IoT applications [9]. IoT
cloud applications support the virtualized vertical solution by
inheriting the multitenant feature of cloud computing, which
means that each tenant can share the computing resources with
other tenants and customize their applications according to
their own business scenarios.
The IoT cloud makes it possible to access and analyze
the data flows of massive numbers of IoT devices [10] and
greatly improves the cost-effectiveness and scalability of IoT
services [11]. However, the responsibility of software system
maintenance is handed over to the cloud provider, which brings
many new technical challenges. In addition, the multitenant
performance isolation problem, which is how to ensure that
all tenants’ devices working within assigned quotas are not
interfered by the other tenants devices that have exceeded their
quotas in a multitenant scenario, has become a research focus
in this area [12].
In seeking to achieve multitenant performance isolation,
most existing research focuses on SaaS application in Web
scenarios, which are mainly divided into two types: virtual
machine-based tenant performance isolation and application-
level middleware-based composite performance isolation.
In 2011, L. Wu et al. [13] implemented the resource
allocation of tenants with different SLA levels through virtual
machines. In 2012, Takeshi et al. [12] proposed a scheme
to allocate independent virtual machines to each tenant for
isolation. The deployment of virtual machine will bring high
additional costs. Although the above patterns achieve effective
performance isolation, they sacrifice cost-effectiveness.
In 2012, David Shue et al. [14] proposed a Pisces sys-
tem that can achieve effective performance isolation in Web

2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
applications. Although there are many differences between
databases and IoT clouds, the architecture of Pisces systems
still has great significance to the design of isolation archi-
tectures in IoT clouds. In 2014, Krebs et al. [15] analyzed
and compared the existing request resource consumption esti-
mation algorithm and proposed an algorithm for performance
isolation in a single-instance SaaS application.
In order to organize and manage massive numbers of devices
in the IoT scenario, it is necessary to adopt a highly decoupled
communication model between the devices and the cloud
platform. As a result, the subscription/publishing communi-
cation model is widely adopted by IoT cloud providers. Since
devices and servers transmit data asynchronously through
message brokers in this communication mode, the existing
performance isolation algorithm based on Web middleware
cannot be directly applied to the Internet of Things platform.
In order to resolve this problem, it is necessary to implement
an algorithm that can control the data flows of tenants’ devices
to achieve performance isolation.
At present, research on multitenant performance isolation
in the IoT scenario is still in the initial stage. In 2016, Cai H.
et al. analyzed the prospects and challenges of IoT big data
platforms based on cloud computing [16]. Their research pro-
vided an application framework of the IoT cloud and analyzed
the framework layer by layer. Furthermore, they proposed the
existing challenges of IoT clouds, and multitenant performance
isolation is one of them.
In 2016, Caglar F. et al. proposed intelligent performance
interference-aware resource management for IoT cloud back-
ends [17]. They implemented a dynamic load prediction mech-
anism for a VM based on machine learning. However, their
research result is still a common cloud computing technology
failing to consider the characteristics of the IoT cloud platform
to achieve performance isolation.
In 2020, Ali S. A. et al. conducted a comprehensive study on
the resource management technology of the Internet of Things
cloud platform [18]. Based on the analysis and comparison
of existing resource allocation algorithms of the IoT cloud,
their study determined the parameters that must be considered
to improve the resource allocation of the IoT cloud, which
has guiding significance for multitenant performance isolation.
However, they did not propose an innovative algorithm for the
resource allocation and scheduling of the IoT cloud.
Aiming at the multitenant performance isolation of IoT
clouds, this paper proposes a comprehensive MQTT data flow
scheduling algorithm. The main contributions of this paper are
as follows.
1) An MQTT data flow scheduling algorithm combining the
priority scheduling algorithm with the improved distributed
token bucket algorithm is proposed. This algorithm can effec-
tively balance the resource occupation of tenant devices on the
cloud platform and achieve performance isolation.
2) The algorithm proposed in this paper is applied to
an IoT application in cloud environments for experimental
verification. The results show that compared with the scenario
without the performance isolation algorithm, the algorithm
proposed in this paper can reduce the device message delay
of an observant tenant by 82%.
2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
2
II. PRELIMINARIES
A. Subscription/publishing communication model in the IoT
cloud
How to construct the messaging layer of a cloud platform in
order to efficiently handle the data stream generated by mas-
sive numbers of IoT devices is the core problem to be solved
when constructing an IoT cloud. The subscription/publication
mode makes the selective distribution of messages possi-
ble [19]. The publication/subscription system is a message-
oriented middleware that provides distributed, asynchronous
and loosely coupled communication between message produc-
ers and message consumers. This mode provides three main
types of decoupling:
1) Message producers and consumers are decoupled in time
and do not need to connect at the same time.
2) Messages are not explicitly sent to specific users but
rather are sent to specific addresses (channels and topics).
3) Message delivery is asynchronous and nonblocking.
These three types of decoupling make the IoT cloud have
good scalability and are especially suitable for large-scale IoT
deployment. Figure 1 shows the general architecture of the
IoT cloud based on the subscription/publishing model.
Fig. 1: Publication/Subscription
Due to the extremely limited resources, IoT devices need to
transmit data through efficient and energy-saving application
protocols. The MQTT (message queuing telemetry transport)
protocol is widely used in IoT scenarios [20]. As a com-
munication protocol under the ISO standard, it works using
the TCP/IP protocol. It is often used in remote hardware
equipment with low performance or in low bandwidth, high
delay and unreliable networks. Considering the complex and
changeable network environment of the IoT, MQTT provides
three QoS levels for developers to customize according to
business scenarios.
B. Asynchronous Communication Algorithm
The subscription/publication model is an asynchronous
communication model. The message broker only needs to
be responsible for continuously forwarding messages to con-
sumers without waiting for a response. In this mode, in order
to achieve multitenant performance isolation, it is necessary to
traffic device messages from different tenants. Common cur-
rent limiting algorithms, such as the sliding window algorithm
and token bucket algorithm, control the flow of the message
forwarding. The core idea of these algorithms is to control the
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
3

Fig. 2: System Architcture

requested amount of the interface and realize resource control

in turn. The two algorithms are introduced below.
1) Sliding Window Algorithm
Wang X et al. used the sliding window algorithm to deter-
mine the fair distribution of server resources in the message
queue of the subscription/publication mode [21]. The sliding
window divides the window into smaller grids for flow control
based on the fixed window of the counter. As shown in
Figure 3, the entire dotted rectangle represents an overall time
window. Each grid maintains a counter independently. After
the time reaches the next small interval, the overall window
slides forward by one grid, and only the requested amount of
the earliest grid is reset. It is not difficult to see that the more
grid divisions of the sliding window there are, the smoother
the effect of current limiting. Considering that service interface
functions are usually different and their resource consumption
is also different, the use of a window mechanism for current
Fig. 3: Sliding Window Algorithm
limiting can only control the number of access requests, and
it cannot judge the resource consumption according to the
interface type; therefore, the effect of resource control is not
the best. the token is obtained. Requests that do not obtain a token wait
2) Token Bucket Algorithm or are rejected. The system continuously adds new tokens to
Caldas F. et al. used the token bucket algorithm in their the bucket at a set rate. There is an upper limit on the number
research to ensure that devices connected to the IoT gateway of tokens. When the bucket is full, the newly added tokens
obtain fair and effective services [22]. The token bucket will be discarded. Developers can set the number of tokens
algorithm can be considered to be an improved version of the required for each request according to the request type. In this
sliding window algorithm. All requests can be processed after way, more fine-grained resource control can be achieved. The

2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
workflow of the token bucket algorithm is shown in Figure 4
below.
Fig. 4: Token Bucket Algorithm
In multitenant applications in asynchronous communication
mode, by assigning a token bucket to each tenant, it is possible
to limit the resources consumed by each tenant, thereby
achieving a certain degree of performance isolation. However,
this solution has the following problems in the IoT scenario:
1) The replenishment rate of tokens is constant. The system
lacks an effective negative feedback mechanism to more
accurately control the resource consumption of tenants.
When many system resources are occupied by the job
tasks of a certain batch of equipment, the token issuer
lacks an effective mechanism to dynamically reduce the
token issuance rate, resulting in high system resource
occupation.
2) Considering the complexity and variability of the IoT
environment, it is difficult to determine how many tokens
are the most appropriate for each tenant. Once the token
rate of the tenant is set too high, it will cause some tenants
to encroach on the resources of other tenants; otherwise
system resources cannot be fully exploited.
3) When the equipment of some tenants is idle, to maximize
resource utilization, other tenants should be allowed to
use the remaining system resources, but the token bucket
severely restricts the resource quota, resulting in idle re-
sources that cannot be allocated to the remaining tenants.
C. Resource Demand Estimation Algorithm
In order to quantify tenants’ resource usage, we need to
adopt effective algorithms to estimate the resource consump-
tion of various request types. Brosig et al. proposed a request
resource estimation algorithm based on request latency for
Java Web applications [23]. For each type of request i, the
estimated resource consumption is Ci . Since the monitoring
tool can only obtain the total resource occupation U of the
application, it is assumed that the response time of the request
is approximately proportional to its resource demand. As a
result, we can estimate the resource consumption of each
request by the following formula.
2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
4
Ti · λi
Ci = U · ∑I (1)
r=1 Tr · λr
where I indicates the number of request types, Ti is the
average delay of the request, and λi is the throughput rate.
The overall resource usage U of the applications is:
U = α · Uc + β · UM + γ · UB (2)
where Uc is the CPU usage rate, UM is the memory usage
rate, and UB is the bandwidth usage rate. Considering that in
the IoT cloud scenario, the consumption of messages sent by
devices is also handled by the cloud server, which is identical
to processing of Web service requests, the same resource
estimation algorithm can be used to estimate the message
resource consumption.
III. H IGH - PERFORMANCE I SOLATION FOR S MART I OT
H EALTHCARE IN THE CLOUD
The architecture of the multitenant performance isolation
technology in this study is shown in Figure 2.
Device layer. The device layer consists of IoT devices and
the MQTT clients of the IoT cloud.
Access layer. The network layer consists of an MQTT
broker and a processor pool. The MQTT broker, as a message
agent of the IoT, is responsible for forwarding messages
between devices and application services. Its processor thread
group is the actual execution unit for the decoding, tenant au-
thentication, and topic resolution of each producer’s messages.
The processor pool maintains a FIFO processor queue for each
tenant, and the processor thread will join the corresponding
queue according to the tenant ID after tenant authentication.
Control layer. The control layer is composed of a priority
scheduler and distributed token bucket. The priority scheduler
maintains a tenant priority queue and a resource counter.
The token bucket is implemented using a distributed blocking
queue, which applies a token for the scheduler and return token
for the consumer.
Service layer. The service layer is responsible for processing
device messages. The service provider will offer customized
and scalable software services according to different vertical
businesses of the IoT.
A. MQTT data flow scheduling algorithm
The MQTT data flow scheduling algorithm proposed in
this paper consists of the priority scheduling algorithm and
improved distributed token bucket algorithm. The priority
scheduling algorithm is used to schedule the data flows of
the IoT devices. The priority of the tenants is determined by
dynamically counting the resource consumption of the tenants
in the cloud. The higher the resource consumption of the tenant
in a unit of time is, the lower the priority of their devices
to be scheduled. Due to the asynchronous communication
adopted by MQTT, it is difficult to know the specific number
of messages being processed in the consumer cluster, which
will make it difficult for brokers to decide when to trigger data
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
5

flow scheduling. In order to solve this problem, the distributed Algorithm 1 MQTT Data Flow Scheduling Algorithm
token bucket algorithm is introduced to the scheduling process. Input:
The token is stored through the distributed blocking queue.
inputBuffer: input buffer of consumer
The scheduler will not schedule until the token is obtained
from the token bucket. Variable:
In contrast to the traditional token bucket algorithm, the
timeInterval: time interval of resource consumption update
system no longer replenishes new tokens at a constant rate,
processorMap: map of processor queue
and the tokens will not be discarded after message forwarding;
priorityQueue: priority queue of tenants
instead, but the tokens will be returned to the queue by
currentProcessor: current processor
the consumer after message processing. Through this dis-
tributed token bucket algorithm, the distributed system using Function: handleMessage
the asynchronous communication mode can accurately control
message = inputBuffer.PeekMessage()
the number of messages consumed. As a result, the system
if message.type == PubilshMessage:
will have an effective negative feedback mechanism, and the
tenantId = ParseTenantID(message.topic)
speed of message sending is dynamically determined by the
processorQueue = processorMap.Get(tenantId)
message processing speed of microservices. Figure 5 shows
processorQueue.Add(currentProcessor)
the principle of the MQTT data flow scheduling algorithm.
currentProcessor.Wait()
Due to different business scales, tenants often have different tenant = getTenantInfo(tenantId)
equipment scales, so they will sign different SLA agreements processIncoming(msg)
with an IOT cloud platform. At present, the cloud platform of tenant.resource += getMessageWeight(message.topic)
the Internet of Things often focuses on the traffic demand [24]. tenant.weight = tenant.maxMessages/tenant.resource
Generally, the message traffic (the maximum number of
messages received from all devices in each service cycle) Functino: SchedulerLoop
is specified in an SLA [22]. The priority of tenants should while true :
consider the resource occupation and the maximum message token = blockingQueue.Acquire()
volume at the same time. In a normal scenario, the maximum tenant = priorityQueue.Get(1)
message traffic of a tenant should be proportional to their processor_queue = processorMap.Get(tenantId)
resource usage; therefore, the priority calculation formula of processor = processorQueue.Pop()
the tenant can be obtained as follows. processor.Notify()
if curruntTime lastTime > timeInterval :
Mi for tenant in tenantQueue
Pi = (3) tenant. resource = 0
Ri
lastTime = currentTime
where Pi is the priority of tenant i, Ri is the resource end while
consumption over a period of time, and Mi is the maximum
message traffic specified in an SLA. According to the above
formula, under the same resource consumption, the larger the
maximum message traffic ordered by a tenant is, the higher B. Results and Analysis
the priority of the tenant. The scheduling algorithm proposed
in this study is shown in algorithm 1. TABLE I: Performance without the isolation algorithm
Average Latency Latency Standard Deviation Throughput
Tenant
IV. E XPERIMENTS A ND A NALYSIS (ms) (ms) (sec−1 )
1 10897 8761.13 119.7
A. Computing Environment Setup 2 14470 8690.41 313.4
The hosts used in this section are configured using a Sum 13464 8845.14 433.1
computer with an Intel Core i7-9750H 6-core, 12-thread 2.60
GHz CPU; 16 GB of memory; and the 64-bit Ubuntu 16.04 The experiment tests the multitenant application in an IoT
operating system. Golang 1.12 and JAVA 1.8 are used as the scenario. A parking lock service is selected as the consumer.
development languages. MySQL 5.7 is used to simulate the The initial number of clients of two tenants is set to 100,
tenant data. Docker is used as Container. Spring Cloud Dalston and then 60 clients are added to tenant 2 every 5 seconds to
is used as the microservice framework. SurgeMQ is used as simulate the scenario of the increasing communication load
the MQTT broker. of tenant 2s devices. The messages sent by the device include
The IoT cloud platform used in experiments is an IoT the heartbeat frame and parking space status change message.
healthcare cloud in the smart IoT healthcare field. The plat- First, we tested the scenario without the tenant performance
form is developed based on the microservice framework spring isolation algorithm. The results of the related experiments are
cloud and the Web framework spring boot. It is a cloud shown in Table 1, Figure 6 and Figure 7.
service platform based on the multitenant mode that provides Message processing latency: The request latencies of the
intelligent IoT healthcare services. two tenants are almost the same throughout the whole process.

2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
6

Fig. 5: MQTT Data Flow Scheduling Algorithm

Due to the lack of an effective isolation mechanism, the

latency time of both tenants increases as the number of
client connections of tenant 2 increases, resulting in a serious
backlog of device messages that cannot be processed.

Fig. 7: Throughput without the performance isolation

IoT devices, the devices can continue generating messages

Fig. 6: Message Latency without the performance insolation
Throughput: The throughputs of the two tenants were ba-
sically the same in the initial stage. When the concurrency
of tenant 2 started to increase, the throughput of tenant 1
decreased dramatically and began to jitter dramatically, which
resulted in a large fluctuation in the performance perceived by
users.
Experiments show that there is a multitenant performance
interference problem in the context of the IoT cloud. In
addition, because of the asynchronous communication of the
without receiving the reply of the cloud server. This feature
leads to the backlog of messages, which makes the service
unable to respond to the status changes of devices in time,
and seriously affects the work of IoT devices.
Next, we test the scenario with the token bucket algorithm.
The results of the related experiments are shown in Table 2,
Figure 8 and Figure 9.
Message processing latency: The message processing la-
tency of the two tenants is obviously divided into two curves.
The latency of tenant 1 is significantly lower than that of tenant
2, which indicates that the token bucket algorithm can achieve
tenant isolation to some extent. However, the latency of tenant

2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
7

TABLE II: Performance comparison of token bucket algorithm

Average Latency Latency Standard Deviation Throughput
Tenant
(ms) (ms) (sec−1 )
1 6342 2658.72 201.4
2 14105 9659.54 254.9
Sum 10678 8372.51 456.3

Fig. 10: Throughput with the MQTT data flow scheduling

algorithm

Fig. 8: Message Latency with the token bucket algorithm

1 still increased with the number of client connections of

tenant 2, which indicates that the scheduler still passes on
too many requests of tenant 2 and fails to achieve completely
fair scheduling.

Fig. 11: Throughput with the MQTT data flow scheduling

algorithm

of device connections for tenant 2. Compared with the token

bucket algorithm, the message latency of tenant 1 is much
lower. This shows that the algorithm proposed in this study
can effectively shield the performance interference caused by
the load increase of other tenants’ devices, and guarantee the
service performance of tenants within their normal quota.
Throughput: When the number of connections for tenant 2
Fig. 9: Throughput with the token bucket algorithm starts to increase, after a short period of jitter, the through-
put of the two tenants basically remains at the same level.
Throughput: Compared with the previous scenario, the Compared with the token bucket algorithm, the MQTT data
throughput of tenant1 is improved. The isolation of the token flow scheduling algorithm can better balance the throughput of
bucket algorithm is relatively limited, which cannot completely tenants. The results show that the algorithm proposed in this
ensure that the two tenants have the same throughput. study can achieve fair scheduling of tenants device packets in
Finally, we test the scenario with the MQTT data flow the IoT scenario and maintain the communication throughput
scheduling algorithm. The results of the related experiments of each tenant device at the same level.
are shown in Table 3, Figure 10 and Figure 11. Based on the above three experiments, it is obvious that
the data flow scheduling algorithm proposed in this study can
TABLE III: Performance with the MQTT data flow scheduling achieve multitenant performance isolation in the IoT cloud.
algorithm The average message processing time of tenant 1 is reduced
by 82%, and the standard deviation is reduced by 92.2%.
Average Latency Latency Standard Deviation Throughput
Tenant
(ms) (ms) (sec−1 ) Because the data flow scheduling algorithm combines the
token bucket mechanism, which determines the execution state
1 1973 685.98 233.3
2 12750 10565.81 232.5 of the scheduler through token acquisition, the whole perfor-
Sum 10678 8372.51 465.8 mance isolation algorithm has a stronger negative feedback
mechanism. As a result, the algorithm can schedule the data
Message processing latency: The message processing la- flows of different tenants more accurately in the asynchronous
tency of tenant 1 is not affected by the increase in the number communication scenario.

2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2021.3051742, IEEE Internet of
Things Journal
V. C ONCLUSION AND F UTURE W ORK
In smart medicine, an IoT cloud platform not only provides
cloud computing resources for medical sensor devices, but it
also provides software services for tenants, controls equipment
and queries the status of equipment through network services.
In this situation, there will also be performance interference
between multiple tenants, and performance isolation on the
IoT device side alone cannot guarantee global fairness. We
implemented a unified tenant data flow scheduling scheme
for the IoT cloud to effectively ensure the fair distribution
of cloud resources. In addition, the experiments show that
the algorithm proposed in this paper can effectively isolate
the performance of tenants’ equipment. Furthermore, the al-
gorithm ensure the service quality for each tenant. Besides, by
applying this scheme in smart IoT healthcare can effectively
improve patients’ medical service experience.
In the field of future medicine, first, since the populariza-
tion of sensor technology and Internet of Things healthcare,
multiple home medical devices such as infrared thermometers
and heart rate monitors are already quite common in peoples
daily lives and have been used to measure essential body
parameters, such as heart rate, body temperature and others.
Therefore, in the IoT healthcare scenario, patients can obtain
personal medical diagnoses by uploading physical health data
obtained from IoT medical devices to iDoctor, which is a
self-serve medical system, to obtain professional healthcare
advice. Second, previous patients’ cases are more important
and valuable for personal disease diagnosis. Therefore, how to
make full use of previous cases information while not leaking
patients’ private information is a leading and promising field
of research, especially in future privacy-preserving intelligent
medical applications. Thus, we will consider the problem of
how to securely obtain personal medical diagnoses in IoT
healthcare while preserving performance isolation and service
quality in our future work.
ACKNOWLEDGEMENT
This work was supported by the National Key R&D Pro-
gram of China (No. 2020YFB1006002), the National Natural
Science Foundation of China (Grant Nos. 81671768 and
61601041), the Fundamental Research Funds for the Central
Universities(2019PTB-003), and the Key R&D Program of
Hebei Province (Grant No. 20313701D). This work was also
supported by the China NationalNatural Science Foundation
No. 61802139,No. 61802139, No. L1924068 and The work
was supported by the Technology Innovation Project of Hubei
Province of China under Grant 2019AEA171.
R EFERENCES
[1] A. Gatouillat, Y. Badr, B. Massot, and E. Sejdić, “Internet of medical
things: A review of recent contributions dealing with cyber-physical
systems in medicine,” IEEE internet of things journal, vol. 5, no. 5, pp.
3810–3822, 2018.
[2] A. Limaye and T. Adegbija, “Hermit: A benchmark suite for the internet
of medical things,” IEEE Internet of Things Journal, vol. 5, no. 5, pp.
4212–4222, 2018.
[3] M. Chen, Y. Hao, C.-F. Lai, D. Wu, Y. Li, and K. Hwang, “Opportunistic
task scheduling over co-located clouds in mobile environment,” IEEE
Transactions on Services Computing, vol. 11, no. 3, pp. 549–561, 2016.
2327-4662 (c) 2020 IEEE. Personal use is permitted, but republication/redistribution requires IEEE permission. See http://www.ieee.org/publications_standards/publications/rights/index.html for more information.
Authorized licensed use limited to: University of Prince Edward Island. Downloaded on May 30,2021 at 16:27:41 UTC from IEEE Xplore. Restrictions apply.
8
[4] N. Shi, L. Tan, W. Li, X. Qi, and K. Yu, “A blockchain-empowered
aaa scheme in the large-scale hetnet,” Digital Communications and
Networks, 2020.
[5] Z. Guo, Y. Shen, A. K. Bashir, M. Imran, N. Kumar, D. Zhang, and
K. Yu, “Robust spammer detection using collaborative neural network
in internet of thing applications,” IEEE Internet of Things Journal, 2020.
[6] F. Tao, Y. Cheng, L. Da Xu, L. Zhang, and B. H. Li, “Cciot-cmfg: cloud
computing and internet of things-based cloud manufacturing service
system,” IEEE transactions on industrial informatics, vol. 10, no. 2,
pp. 1435–1442, 2014.
[7] M. Chen and Y. Hao, “Label-less learning for emotion cognition,” IEEE
transactions on neural networks and learning systems, 2019.
[8] M. Chen, Y. Jiang, N. Guizani, J. Zhou, G. Tao, J. Yin, and K. Hwang,
“Living with i-fabric: Smart living powered by intelligent fabric and
deep analytics,” IEEE Network, 2020.
[9] A. Botta, W. De Donato, V. Persico, and A. Pescapé, “Integration of
cloud computing and internet of things: a survey,” Future generation
computer systems, vol. 56, pp. 684–700, 2016.
[10] E. Truyen, D. Van Landuyt, V. Reniers, A. Rafique, B. Lagaisse, and
W. Joosen, “Towards a container-based architecture for multi-tenant saas
applications,” in Proceedings of the 15th international workshop on
adaptive and reflective middleware, 2016, pp. 1–6.
[11] C. D. Weissman and S. Bobrowski, “The design of the force. com
multitenant internet application development platform,” in Proceedings
of the 2009 ACM SIGMOD International Conference on Management
of data, 2009, pp. 889–896.
[12] T. Takahashi, G. Blanc, Y. Kadobayashi, D. Fall, H. Hazeyama, and
S. Matsuo, “Enabling secure multitenancy in cloud computing: Chal-
lenges and approaches,” in 2012 2nd Baltic Congress on Future Internet
Communications. IEEE, 2012, pp. 72–79.
[13] L. Wu, S. K. Garg, and R. Buyya, “Sla-based resource allocation for
software as a service provider (saas) in cloud computing environments,”
in 2011 11th IEEE/ACM International Symposium on Cluster, Cloud
and Grid Computing. IEEE, 2011, pp. 195–204.
[14] D. Shue, M. J. Freedman, and A. Shaikh, “Performance isolation
and fairness for multi-tenant cloud storage,” in Presented as part of
the 10th {USENIX} Symposium on Operating Systems Design and
Implementation ({OSDI} 12), 2012, pp. 349–362.
[15] R. Krebs, C. Momm, and S. Kounev, “Metrics and techniques for
quantifying performance isolation in cloud environments,” Science of
Computer Programming, vol. 90, pp. 116–134, 2014.
[16] H. Cai, B. Xu, L. Jiang, and A. V. Vasilakos, “Iot-based big data storage
systems in cloud computing: perspectives and challenges,” IEEE Internet
of Things Journal, vol. 4, no. 1, pp. 75–87, 2016.
[17] F. Caglar, S. Shekhar, A. Gokhale, and X. Koutsoukos, “Intelligent,
performance interference-aware resource management for iot cloud
backends,” in 2016 IEEE First International Conference on Internet-of-
Things Design and Implementation (IoTDI). IEEE, 2016, pp. 95–105.
[18] S. A. Ali, M. Ansari, and M. Alam, “Resource management techniques
for cloud-based iot environment,” in Internet of Things (IoT). Springer,
2020, pp. 63–87.
[19] D. Happ, N. Karowski, T. Menzel, V. Handziski, and A. Wolisz, “Meet-
ing iot platform requirements with open pub/sub solutions,” Annals of
Telecommunications, vol. 72, no. 1-2, pp. 41–52, 2017.
[20] D. Locke, “Mq telemetry transport (mqtt) v3. 1 protocol specification,”
IBM developerWorks Technical Library, vol. 15, 2010.
[21] X. Wang, V. Devadhar, and P. Murugesan, “Mechanism for facilitating
sliding window resource tracking in message queues for fair manage-
ment of resources for application servers in an on-demand services
environment,” Feb. 23 2016, uS Patent 9,268,605.
[22] F. L. de Caldas Filho, R. L. Rocha, C. J. Abbas, L. M. E. Martins, E. D.
Canedo, and R. T. de Sousa, “Qos scheduling algorithm for a fog iot
gateway,” in 2019 Workshop on Communication Networks and Power
Systems (WCNPS). IEEE, 2019, pp. 1–6.
[23] F. Brosig, S. Kounev, and K. Krogmann, “Automated extraction of
palladio component models from running enterprise java applications,”
in Proceedings of the Fourth International ICST Conference on Perfor-
mance Evaluation Methodologies and Tools, 2009, pp. 1–10.
[24] M. Chen, Y. Hao, K. Lin, Z. Yuan, and L. Hu, “Label-less learning for
traffic control in an edge network,” IEEE Network, vol. 32, no. 6, pp.
8–14, 2018.