Survey of platforms for massive IoT

Hejazi, Hamdan; Rajab, Husam; Cinkler, Tibor; Lengyel, László

doi:10.1109/fiot.2018.8325598

Cited by 131 publications

(75 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…CoAP is similar to HTTP but is lightweight, therefore more suitable for mobile applications. MQTT is also lightweight and supports broker concept, making it good for limited bandwidth applications [8]. CoAP is good for multicast and broadcast.…”

Section: Criteria For Selection Of the Right Iot Middleware Platformmentioning

confidence: 99%

Investigating IoT Middleware Platforms for Smart Application Development

Agarwal

Alam

2020

Lecture Notes in Civil Engineering

View full text Add to dashboard Cite

With the growing number of Internet of Things (IoT) devices, the data generated through these devices is also increasing. By 2030, it is been predicted that the number of IoT devices will exceed the number of human beings on earth. This gives rise to the requirement of middleware platform that can manage IoT devices, intelligently store and process gigantic data generated for building smart applications such as Smart Cities, Smart Healthcare, Smart Industry, and others. At present, market is overwhelming with the number of IoT middleware platforms with specific features. This raises one of the most serious and least discussed challenge for application developer to choose suitable platform for their application development. Across the literature, very little attempt is done in classifying or comparing IoT middleware platforms for the applications. This paper categorizes IoT platforms into four categories namely: publicly traded, open source, developer friendly and end-to-end connectivity. Some of the popular middleware platforms in each category are investigated based on general IoT architecture. Comparison of IoT middleware platforms in each category, based on basic, sensing, communication and application development features is presented. This study can be useful for IoT application developers to select the most appropriate platform according to their application requirement.

show abstract

Section: Criteria For Selection Of the Right Iot Middleware Platformmentioning

confidence: 99%

Investigating IoT Middleware Platforms for Smart Application Development

Agarwal

Alam

2020

Lecture Notes in Civil Engineering

View full text Add to dashboard Cite

show abstract

“…Current advance in IoT researches shows a lot of platforms developments. Large number of these platforms has been surveyed in [8] [10] [11] [12] [13], [14], [15] and [16] concluded the lack of a dynamic scale-able IoT platform that helps in utilizing global system resources, support discovery and composition, reliability, security and privacy; the proposed architecture addresses such features.…”

Section: Related Workmentioning

confidence: 99%

Towards a Dynamic Scalable IoT Computing Platform Architecture

Abdelqawy¹,

Kamel²,

Makady³

2020

IJACSA

View full text Add to dashboard Cite

Internet of Things (IoT) has become an interesting topic among technology titans and different business groups. IoT platforms have been introduced to support the development of IoT applications and services. Such platforms connect the real and virtual worlds of objects, systems and people. Even though IoT platforms increasingly target various domains, they still suffer from various limitations. (1) Integrating hardware devices from different providers/vendors (thereafter referenced as heterogeneous hardware) is still a subtle task. (2) Providing a scalable solution without altering the end user privacy (e.g., through the use of cloud platforms) is hard to achieve. (3) Handling IoT Applications reliability as well as platform reliability is still not fully supported. (4) Addressing Safety-critical applications needs are still not covered by such platforms. A novel scalable dynamic computing platform architecture is proposed to address such limitations and provide simultaneous support for five non-functional requirements. The supported non-functional requirements are scalability, reliability, privacy, timing for real-time systems and safety. The proposed architecture uses a novel network topology design, virtualization and containerization concepts, along with a service-oriented architecture. We present and use a smart home case study to evaluate how traditional IoT platform architectures are compared to the proposed architecture, in terms of supporting the five non-functional requirements.

show abstract

“…Practitioners can rely on different IoT platforms available, both open-source and commercial solutions [11,19,24]. These platforms may use multiple protocols and standards or even proprietary solutions.…”

Section: Of 24mentioning

confidence: 99%

“…Since smart applications will typically have to deal with thousands of devices-or considerably more-performance and scalability concerns are key to any successful IoT deployment. Yet, most current reported experiences show: (a) small-scale pilots [7,44]; (b) simulation-based or analytical results [21,45]; (c) measurement-based results with limited scope [19,46]; (d) no quantitative results at all [2,3,5,8,9,11,12,16,24,37,47]. Also, different architectural and deployment choices for IoT systems affect scalability, and real-time decision-making is possible in an environment composed of thousands of sensors [4,48].…”

Section: Performance and Scalability Of Iot Systemsmentioning

confidence: 99%

Architecting and Deploying IoT Smart Applications: A Performance–Oriented Approach

Zyrianoff

Heideker

Silva

et al. 2019

Sensors

View full text Add to dashboard Cite

Layered internet of things (IoT) architectures have been proposed over the last years as they facilitate understanding the roles of different networking, hardware, and software components of smart applications. These are inherently distributed, spanning from devices installed in the field up to a cloud datacenter and further to a user smartphone, passing by intermediary stages at different levels of fog computing infrastructure. However, IoT architectures provide almost no hints on where components should be deployed. IoT Software Platforms derived from the layered architectures are expected to adapt to scenarios with different characteristics, requirements, and constraints from stakeholders and applications. In such a complex environment, a one-size-fits-all approach does not adapt well to varying demands and may hinder the adoption of IoT Smart Applications. In this paper, we propose a 5-layer IoT Architecture and a 5-stage IoT Computing Continuum, as well as provide insights on the mapping of software components of the former into physical locations of the latter. Also, we conduct a performance analysis study with six configurations where components are deployed into different stages. Our results show that different deployment configurations of layered components into staged locations generate bottlenecks that affect system performance and scalability. Based on that, policies for static deployment and dynamic migration of layered components into staged locations can be identified.

show abstract

Survey of platforms for massive IoT

Cited by 131 publications

References 13 publications

Investigating IoT Middleware Platforms for Smart Application Development

Investigating IoT Middleware Platforms for Smart Application Development

Towards a Dynamic Scalable IoT Computing Platform Architecture

Architecting and Deploying IoT Smart Applications: A Performance–Oriented Approach

Contact Info

Product

Resources

About