The Internet of Things (IoT) is an extensive network of heterogeneous devices that provides an array of innovative applications and services. IoT networks enable the integration of data and services to seamlessly interconnect the cyber and physical systems.
1. Introduction
The Internet of Things (IoT) is widely regarded as one of the most prevailing technology revolutions of the previous two decades. IoT devices are often perceived as computing devices with sensing capabilities, onboard computational power, and an internet-enabled network to communicate with each other. It is one of the most rapidly growing areas that relies on machine-to-machine communications and utilizes an internet stack for end-to-end connectivity. In its simplest term, IoT is perceived as a network of billions of devices that can sense, actuate and relay the information to a centralized system. Nowadays, IoT devices and applications are deployed in various domains such as logistics, retail, health care, smart city network, intelligent transportation and disaster management. Despite the technological advancements in these individual domains, the heterogeneity of IoT devices and lack of standardization challenges are yet to be addressed. It is vital to examine the “Things” themselves, which operate differently depending on the implementation scenario, ranging from time-critical to mission-critical applications.
2. IoT Architectures, Platforms and Technology Stack
The modern Internet is a complex blend of Internet nodes, IoT devices, and smart objects. Internet-enabled networks require the implementation of an IP stack for communication between networks of objects. With the expansion of Internet networks, enterprises as well as research communities are investing in flexible and scalable IP networks for the future
[13][1]. Currently, the Internet-enabled networks vary greatly both in technical implementations and in end-application needs. A conventional computing node (such as Personal Computers, Laptops, Mobiles and Tablets) implements an entire TCP/IP stack based on the Open Systems Interconnection (OSI) Model. However, due to the limited resources available on IoT devices, a lightweight IP stack is normally implemented. The on-board resource availability and energy consumption of the device primarily regulate the implementation of suitable protocols and standards in IoT devices. Therefore, it is fundamentally important to investigate the IoT architectures and platforms to understand the role and behavior at every layer of the technology stack.
The horizontal fabric is made up of “Things” and the communication stack, whereas middlewares, edge networks, and the cloud make application development simpler and thus enable vertical markets on top of this fabric [50]. A closer look at Figure 4 reveals a three-tier architectural model for IoT systems. A subtle balance between components and processes is presented in this model, where devices or “Things” are the primary layer of the architecture. It is apparent that this layer is open for vendor-specific implementations, resulting in a myriad of distinct components, modules and operating systems.
Figure 41.
IoT architecture model: technology fabric from physical (PHY) to application (APP) layers.
This layer is responsible for translating and propagating the heterogeneity of the entire IoT stack. The network layer exhibits similar variation in terms of component, module, and operating system selection. Devices are connected to the cloud at this layer, either through gateway devices or through a fog/edge network interface. The cloud layer is in charge of handling raw data from billions of IoT devices. To integrate business intelligence, current cloud-driven corporate systems offer solutions based on Artificial Intelligence (AI) and Machine Learning (ML). The cloud layer is dominated mostly by enterprise solutions that offer a variety of IoT network applications. While each cloud technology is different, the heterogeneity of this layer is often defined by the efficacy of the application design.
Since the Internet of Things primarily relies on the internet to connect these devices to services, most reference models and architectures use a layered approach to understanding and defining the functions at each layer.
[47][3]. The alignment of this reference architecture model in layers that greatly simplify overall design goals is a popular trend. However, it is important to remember that most of these reference models do not correspond to the Internet or the TCP/IP stack
[51][4]. It is indeed worth noting that the majority of alliances and organisations contribute to the standardisation of IoT protocol and architecture stacks by proposing their own reference models. This section looks into several of these models, which range from three-layer to middleware and five-layer models, as given in the literature
[12,52,53][5][6][7].
Most architecture models now support the inclusion of middleware as a software-based interface between IoT processes and components. Middleware enables reliable and efficient communication between elements that are mostly not supported within the native operating systems. This results in simpler and standardised communication between processes, components, and devices, thus enabling a software interface that can extend to upper layers and promote vertical market integration.
uBiuitous, secUre inTernet-of-things with Location and contExt-awaReness (BUTLER) is one of the first European consortium research projects to focus on pervasive computing and security for IoT applications in various domains. One of the project’s main objectives was to create context-aware and secure apps for a variety of deployment scenarios (such as healthcare, transportation, smart offices, and smart homes). The researchers proposed a device-centric architecture that included smartObjects, smartMobiles, and smartServers as three key components. The BUTLER project examines technology versus integration concerns using a five-layer architecture that closely resembles the internet layer model, with enabling technologies that help develop the horizontal fabric and address vertical integration problems
[58][8] as shown in
Figure 52.
Figure 52.
BUTLER EU Project—layered IoT architecture model.
Instead of incorporating middlewares into lower layers that enable vertical market integration, another architectural alternative is to add a business layer on top. The top market layer uses a service-oriented approach to provide application availability, sharing, and cross-vendor deployment as necessary
[59,60][9][10]. These models are mostly service oriented in design, and they extend object extractions to middleware service management layers. Thus, the application and business layers enable intelligence and integration of the SOA-based fabric into vertical markets. Al-Fuqaha et al.
[48][11] investigated various architecture models and presented a comparison of a few architectures based on multiple layers toward the need to design a reference architecture that provides scalability, interoperability, and easier integration.
R. Khan et al.
[53][7] proposed a basic IoT architecture model where the three-layered approach aligns the IoT fabric close to the internet stack. The three layers, namely Perception, Network and Application, as presented in
Figure 63, outline the technology and device-level information in the perception layer. The network layer is responsible for the transport or communication of this information to the upper layers. The application layer is a unique blend of managing the data and scaling vertical application-specific integration in multiple domains.
Figure 63.
The IoT architecture: layered model approach.
Modern internet-based systems are made up of billions of devices with varying components, modules, operating systems, and thus standards implementation. Due to limited equipment resources and energy usage requirements, the introduction of lightweight protocols and specifications is a common trend in IoT-based systems. This deviation from the standard IP-based implementation necessitates a thorough examination of various technology layers. This section provided a reference IoT architecture model with device, network, and cloud layers, with components and processes decoupled at each layer. There are also several other reference models that support a layered architecture. Support for middlewares and enterprise business layers to enable vertical market integration is one of the most notable developments in comparison to IoT architectures. Reference IoT architectures were found to be mostly aligned with application-specific markets. In addition, the reference models proposed a layered architecture that can be mapped to the OSI layer models. However, a tradeoff in terms of complexity and scalability is on the horizon, limiting the standardisation of IoT architecture even further.
3. Understanding IoT Functional Blocks
3.1. Identification
Typically, data streams on the Internet are aggregated to monitor overall network traffic. To successfully provision network resources and security policies on an IP-based network, source identification is required. Traditional internet traffic relied on the IPv4 addressing scheme, which is gradually giving way to the IPV6 addressing scheme. The IP stack implementation in IoT devices differs from that of traditional Internet nodes. The Internet endpoint typically implements the entire TCP/IP stack, whereas IoT applications frequently use a lightweight protocol implementation. With the number of IoT devices expected to exceed 75 billion by 2025, the IPv4 addressing scheme may be insufficient. As a result, almost every IoT implementation now uses the IPv6 addressing scheme. IEEE protocols, such as 6LowPAN (IPv6 Low-power wireless Personal Area Network), provide a full-stack IPv6 protocol implementation alternative in low-power devices
[61,62][12][13]. It enables encapsulation and header compression, reducing network overhead while providing unique node addresses for billions of devices.
Another important factor to consider when addressing IoT nodes is the various roles that the node may take on (such as sensing, actuation, relaying or edge-gateway). The aggregation of information based on common service roles is very popular, so nodes must be identified using their Service IDs. An IPv6 address can only identify a node in the network and cannot provide additional information about its roles or behaviours. Therefore, service tag identification is also required for IoT nodes
[63][14]. Radio Frequency Identification (RFID) provides a typical example of service identification by assigning Electronic Product Codes (EPC) to differentiate between various objects and services
[64,65][15][16].
IP-based networks are becoming very large and complex as IoT applications grow at such a rapid pace. A high volume of network traffic on a single route can degrade overall network traffic, causing congestion and bottlenecks. It is therefore critical to logically slice a larger network in order to ensure faster and more reliable network traffic routes. Traditional IP-based networks logically subnetted a large network by using a private addressing scheme and techniques like Network Address Translation (NAT). Maintaining private routing information for billions of IoT devices, on the other hand, is a challenge. IoT edge-gateway devices may be unable to maintain routing and translation tables due to limited on-board computing and networking resources.
A lot of researchers are investigating smart addressing schemes for these devices. One such interesting addressing mechanism is proposed by Moghadam et al.
[4][17], where traditional EPC codes are mapped over the IPv6 addressing scheme to uniquely identify IoT objects. The mapping technique discussed in this research focuses on creating a unique IPv6 address for every unique EPC code assigned to an IoT node based on its functionality. However, one may argue that the proposed scheme may not scale well, as multiple addresses are required to identify the same node. Hirotsugu Seiki et al.
[66][18] presented a unique concept of a de-centralizing blockchain-based
μCode management system that can also be implemented on IoT nodes, allowing scalability and a unique addressing scheme.
3.2. Sensing
IoT networks sense, aggregate, and relay data from billions of smart objects all over the world. In cloud data warehouses, a large amount of raw data is stored and analysed. The knowledge gained from the data assists in the introduction of business intelligence in order to make informed decisions. IoT sensors can be deployed as individual devices (actuators, smart sensors, smart wearables) or as a network of devices (such as WSN) that perform a similar function collectively
[67][19].
WSNs are commonly used in military and industrial research applications where a large number of IoT nodes sense, collect, and relay data collectively. The roles/behaviors of on-board sensors may differ depending on the application. It is also common to see IoT nodes equipped with a variety of sensors that can be triggered based on the situation. These smart sensors’ operational requirements (such as degree of accuracy and/or power consumption) may also vary.
Figure 8 4 provides an overview of a range of sensors typically deployed in industrial applications.
Figure 84. Sensors and actuators currently deployed in the IoT domain [68]. Sensors and actuators currently deployed in the IoT domain [20].
Most of the sensors are passive in nature and require a hardware platform to process the input. Usually a Single Board Computer (SBCs) is capable of processing the information on-board. These SBCs then use the communication tools and built-in TCP/IP stack to connect these nodes to the internet. Currently, we have several IoT-enabled plug and play platforms available that are extensively used in IoT research (e.g., Arduino, Raspberry Pi, Galileo, and BeagleBone). These devices are typically deployed as a single sensing node or in a mesh network topology as the sensing requirements grow. These nodes can be programmed to relay data within their network or to connect with a central management portal where the data is offloaded, analyzed, and then presented on custom dashboards.
IoT nodes are energy-constrained devices that require optimal use of on-board computing to conserve energy. Another consideration that regulates the use of energy-efficient sensors is the overall price of the IoT device. A typical node usually integrates passive sensing devices to reduce its cost. Therefore, smart sensing schemes
[69][21] are required to conserve and, in some cases, harvest energy for IoT nodes
[70,71][22][23]. In addition, IoT devices generate exabytes of data every day, which is relayed to data warehouses for processing. Researchers have been investigating ubiquitous energy autonomy and compressing schemes to provide smart sensing in recent years
[71,72][23][24].
Energy autonomous compressing schemes aggregate the sensor data and relay the critical information to the data warehouses. Amarlingam et al.
[73][25] presented an exciting compressed sensing technique for WSNs. The fundamental observation was based on treating the WSN network as the sensing node for IoT networks. The researchers presented the concept of dictionary learning of data over the wireless nodes that could be aggregated to save energy by choosing the minimal transmission cost path from the data to the sink. Such compressed sensing techniques can significantly help to save energy resources over large-scale deployments.
3.3. Communication
IoT networks are a combination of heterogeneous smart objects, communication technologies, and protocols that collectively perform application-specific tasks. Most of the IoT networks are built on top of the WSN that use low power wireless communications
[74][26]. The IoT nodes must run in low power modes during their lifespan due to energy restrictions. Low power radios and the (noisy) wireless channel contribute to their architecture and working complexities. A typical communication protocol must provide instructions on data coding, transmission and flow controls, sequencing, and error correction. The hardware stack implements these protocols to develop basic applications and interfaces to transmit the data towards the target device. There are several technologies for IoT communication, which currently range from close-to-short range communications. Examples of communications technologies commonly used in IoT networks include Near Field Communication (NFC), Narrowband IoT (NB-IoT), Ultra-Wide Bandwidth (UWB), LTE-A, WiMax, WiFi and LoRaWAN
[75][27].
RFID Technology has been extensively used in the last decade for M2M autonomous communication. Several RFID-based systems (active, passive, and hybrid) for object identification and communication have been developed in the past. RFID systems operate on a data query signal that returns locally stored object information from the reader. RFID-based systems are mostly passive, offering a low-transmission rate over a short range
[77][28]. Logistics and warehousing is one of these industry applications
[78][29]. Some very fascinating IoT implementations focused on RFID have now emerged, including pervasive RFID installations for real-time information systems
[79][30].
Intelligent healthcare systems are one of the most active research subjects in electronics, bioengineering, and computer science
[80,81][31][32]. The current expenditure on Intelligent Health Care is about $7 billion annually. Amendola et al.
[82][33] presented an environment of a health care system that included the implementation of body-centric wearable RFID tags to track the patient’s motion and environmental features autonomously, generating a real-time knowledge database. Wearable smart devices (smart tags, fitness trackers, smartwatches) are increasingly being deployed for health and personal activity monitoring. A wearable fitness tracker is mainly concerned with sensing personal activity and computing a fitness rating. Low cost and low power consumption are some of the common design considerations of wearable devices. Many of these devices combine identical sensors and computational algorithms; there are considerable wireless technologies available. In
[83][34], Fan Wu et al. presented an interesting comparison in wireless technology that is suitable for wearable nodes.
LoRa is another networking technology that operates over longer transmission distances and consumes low power. The lower cost compared to cellular and WiFi systems is a significant efficiency factor for LoRa. LoRa-based IoT systems are commonly used for long-range communication where high transmission speeds are not required. One such design and evaluation environment is presented by H. Lee
[84][35], where LoRa is chosen as the communication technology for a mesh network of IoT sensor nodes. The research also proposed an architecture for improved coverage, with fewer gateways to reduce complexity and overall deployment costs.
Cellular communication, especially 3G, 4G, LTE, and LTE-A (including the prospects of 5G technologies), is thought of as a significant communication technology for IoT applications that demand multimedia transfer or streaming capabilities
[85][36]. Current research on 5G systems supports a design trend that enables LTE-A and beyond cellular technologies as major backbone network contenders for extended coverage, high throughput, and lower latencies
[85,86][36][37]. Although, by its design, the IoT architecture is heterogeneous, it seems nearly impossible to use a single communication technology implementation for IoT applications.
3.4. Compute
Computation is the process of calculating the system workload (both arithmetic and non-arithmetic) for a set of I/O instructions. In traditional computer technology, microprocessors handle the computing load in their CPU cores. High computation and efficiency tasks necessitated the implementation of GPU in order to form computational clusters. IoT systems are primarily governed by a number of factors, including device costs, lower calculation loads, and low energy usage, necessitating the use of power and cost-effective processing units (microprocessors, microcontrollers, System on Chip (SOC), and Field Programmable Gate-Arrays (FPGAs)). The majority of IoT deployments include sensing, processing, and relaying data to the cloud for intensive calculations. These requirements necessitate a limited on-board processor and storage space, thereby reducing system costs and complexity. CPU optimization is frequently essential when the idle CPU wastes a significant amount of computing power. An under-provisioned CPU, on the other hand, will quickly reach its processing peak, necessitating more resources and potentially causing processing bottlenecks. As a result, workload optimization is critical and is taken into account during the initial design stages.
Traditionally, workload optimization is performed by the CPU and is typically managed by the device’s operating system. However, as the number of IoT devices grows year after year, it is clear that a heterogeneous approach is required, with edge computing playing a significant role. In comparison to low-processing, node-level IoT devices, such a solution necessitates heavy computing devices. Processing platforms such as (Arduino, Raspberry Pi, Intel IoT Development Boards, BeagleBone, and ARM Corstone) provide a range of processing capabilities from low-power to full application-specific SoC platforms. In terms of programming, the hardware is only as good as the operating system (OS) that it runs. IoT OS enables devices and applications to communicate with one another as well as other devices such as cloud networks and utilities. The IoT OS also handles the computing power and other services required to collect, transfer, and store data, essentially acting as the device’s central nervous system.
The cloud infrastructure model for IoT devices has matured in recent years. Market leaders such as Amazon IoT, Google Cloud Server, ThingWorx, and IBM Watson are attempting to turn their IoT platform (PaaS) into a service. Cloud systems, as opposed to traditional IoT networks, have greater computational, storage, redundancy, and analysis capabilities. Many exciting solutions (augmented by the cloud computing model) for real-world challenges, such as traffic management in the Internet of Vehicles, are proposed (IoV)
[89,90][38][39]. It is one of the fastest growing areas of research that relies entirely on high-speed cloud computing. The Open Automotive Alliance (OAA) is investing a great deal of technical resources to realise an IoV-based Intelligent Transportation System (ITS)
[91,92][40][41]. It is worth mentioning that future IoT systems need hybrid computing capabilities ranging from low-power IoT nodes to mid-end gateways to high-compute cloud networks.
3.5. Services
The Internet of Things (IoT) is a vast network of heterogenous devices, infrastructure, protocols, and applications. In the previous section, we looked at several IoT architectures that provide a variety of services for vertical market integration. SOAs (Service Oriented Architectures) provide an abstraction layer that connects objects to application layers. The underlying device complexities in the technology stack are greatly simplified by an abstraction layer, allowing for easier vertical market integration. However, the addition of an abstraction layer alters the system architecture at both the OS and Middleware levels. A few researchers also proposed simplifying the architecture by integrating web services directly into IoT sensors
[93,94][42][43]. This strategy not only eliminates the need for abstraction, but it also ensures rapid production and deployment.
Although several service models are available, the long-term objective is to incorporate scalability, interoperability, and easier market integration. However, the categorization will distinguish between different IoT service industries and service models in terms of their services. Mathew Gigli et al.
[95][44] presented an IoT service model based on four categories, including, identity-related services, information aggregation services, collaborative-aware services, and ubiquitous services. These categories use processes that integrate components into various layers of the technology stack. The object identification service helps to sense and identify the virtual object, which is passed on to the information aggregation layer for data aggregation. Collaborative-awareness is achieved by aggregation of information gathered from similar service profile end devices. The omnipresence of IoT intelligence is the desired end goal that can be accomplished by creating collaborative-conscious services that are intelligent enough to make automated decisions. Applications that require user-related data (such as in banking, health care, smart homes) may contain confidential information that can enable user-tailored ubiquitous services. However, the actual implementation of ubiquitous services still seems complicated and challenging.
A category-specific application analysis is used to highlight the scope of these Services in the following context. The goal is to link the literature to application scenarios in which different services stack up to achieve ubiquitous computing. Intelligent automation and orchestration are expected to be features of future ubiquitous IoT environments. RFID-based technologies are frequently used by early adopters of WSN and IoT-based technologies, including application domains such as logistics, digital storage, and fleet management. M2M systems, which include mobile, GPS, and internet technology, have been used in recent years to automate logistics operations and track goods in real time
[96,97][45][46]. These examples classify applications on the basis of identity-related classes in the service model. Some of the top developments in the logistics industry, where identity-related information is mainly used, are location management systems and inventory and tracking systems
[98,99][47][48]. Intel reports that almost 30% of perishable produce from farms never make it to the markets
[100][49]. Object and inventory tracking can help track products such as farm produce, pharmaceuticals, and industrial chemicals in real-time, thus saving a fortune annually.
Logistics 4.0 enables to monitor the shipment quality and object tracking in real-time. Real-time logistics tracking systems are commonly used in the transportation of pharmaceuticals, industrial hazardous chemicals, and life-saving drugs
[101,102][50][51]. On-board sensors transmit information on shipping in real-time, which lets companies not only monitor items but also ensure the optimal consistency of handling procedures. Next, ITS systems are known to be a core component of the information aggregation class. These networks include a range of subsystems, such as smart parking, smart roads, traffic management, and control systems. The sensor information from these subsystems is aggregated to ensure a consistent and safe transport experience. The aggregated information is then passed to the upper collaborative-aware services model in order to thoroughly investigate the data and make smart decisions
[97][46]. Connected vehicles utilize this concept to leverage a collaborative-aware service model, to make real-time collaborative decisions. Driver-less cars use this service model to adapt to road and weather conditions, avoid highway congestion, and book parking spaces in advance
[89,103][38][52].
Connected vehicles or smart vehicles use this concept to leverage information gathered from all of the modules mentioned above and present it to the cloud via a Collaborative-aware service mode, where real-time decisions are made, allowing for the driverless self-driving vision of cars to become a reality. Google is widely regarded as a pioneer in the development and deployment of self-driving vehicles. It creates a collaborative-aware experience for driverless cars by combining user-generated data and cloud-based machine learning models
[104][53]. The technology has advanced so much that autonomous cars have reportedly already driven more than 4 million miles
[105][54]. Scientific standardisation is constantly updating its blueprint to keep up with such fast-paced research and deployments. IEEE 802.11p included amendments to support short-range communication vehicles.
Wireless Access for Vehicular Environments (WAVE)
[106][55] is an approved standard for ITS systems. The National Highway Traffic Safety Administration, USA (NHTSA) has been working closely with research organizations, standards bodies, and academic institutions to advance the goal of Vehicle-to-Vehicle (V2V) communications
[107][56]. Researchers investigated the self-configuration capabilities of future IoV systems that support the standardized technologies and protocols
[108][57]. In a recent report on the readiness of V2V Technology, NHSTA reported a decline in the annual deployment costs of V2V technology. The study further proposed that cross-industry standardization not only decreases the cost of development but also assures a quick rollout. Standardization also helps eliminate loopholes in the area of transportation which can be crucial, and in some cases, life-saving. The report also stated that if V2V safety applications are adopted, it could prevent 25,000 to 592,000 car crashes annually
[109][58]. This report provides vital statistics regarding technological advancement and the standardization efforts towards the internet of connected vehicles.
Another important IoT area that is rapidly expanding is the Industrial Internet of Things (IIoT). In most cases, IIoT systems are associated with high-volume, high-speed data streams. A typical IIoT system is ideally a low-power, small-form-factor sensor or actuator node with internet connectivity that can relay sensed data to the cloud. The cloud-based ML models are then required to automate the industrial systems in near real-time.
Many industrial IIoT architectures and their integration with existing automation platforms require a layer of abstraction. Siemens, one of the world’s most prominent industrial automation leaders, proposed the addition of a connectivity layer to the present automation products and technologies. This concept is integrated into its cloud-based industrial automation solution, the MindSphere
[117][59]. Lastly, smart cities can be observed as an application of the ubiquitous services class
[118,119,120][60][61][62]. It is a system of numerous smaller subsystems, including smart homes, smart grids, ITS and environmental response systems, that form a completely pervasive system focused on collaborative awareness
[121,122,123,124][63][64][65][66].
3.6. Semantics and Analytics
Intelligence and autonomy at the device level are needed in order to achieve ubiquitous computing where devices can self-configure and adapt to their environment
[125,126][67][68]. The autonomy of future IoT networks is projected to minimize working loads by accurately, efficiently, and smartly collecting, processing, and modelling the information
[127][69]. A semantics framework is needed that provides granularity to distinguish between a multitude of objects and their attributes in the IoT networks
[127,128,129][69][70][71]. Such a system helps to define and understand the correct object, and can demand the appropriate resource for the desired feature or behavior, thus acting as the central intelligence or brain of the overall operation
[130][72].
Resource Description Framework (RDF) and its variants have been widely deployed to map attributes to the data. The semantic frameworks are used at various levels in the architecture to make the overall data trustworthy. A semantic framework for translating between different technologies and protocols may be used at the lower layers as a gateway, whereas at the higher layers it can be used for data collection. Word Wide Web Consortium (W3C) Semantic Sensor Network (SSN) ontology and annotation framework is one such example
[131][73]. Effective XML Interchange (EXI), a lightweight representation of Extensible Markup Language (XML), is often commonly utilized for constrained devices
[132][74].
The researchers investigated RDF frameworks to efficiently store and retrieve data from IoT devices. Rahman et al.
[133][75] proposed a lightweight, dynamic ontology-based IoT scheme. The proposed scheme develops dynamic feature-based clusters using ML models. This abstraction of the ML-based SSN ontology scheme reduces query response latency as well as memory footprints. Padiya et al.
[134][76] used the RDF model to analyze vast amounts of IoT-based sensor data management. They used various RDF storage mechanisms to store and retrieve data efficiently. The study also compares vertical portioning and hybrid data-aware methodology, concluding that the latter technique yields a 12% increase in results. Although the reviewers have analyzed a comprehensive data collection using various data storage and retrieval models, it is still unclear how it compares with the other EXI or JSON-LD techniques. It is also uncertain if the solution can be adequate to ensure the interoperability between various layers and systems. In general, the research model and the test bed will serve as excellent starting points for a detailed analysis of data management in IoT systems.
Hasemann et al.
[135][77] presented a rather fascinating use-case focused on asymmetric data transfer by IoT devices. Their approach is based on IoT networks that publish a large amount of data, but receive relatively few updates. They incorporated serialization for RDF documents and opted for streaming Header-Dictionary-Triples (HDT) serialization to encrypt sensor data, resulting in a reduced data lookup table size that enables the re-use of searching entities to further save resources. Along the same lines, lightweight serialization based on RDF documentation seems to be a promising approach, since it reduces the size of data collection and can be conveniently integrated. WiseLib is one of the most common lightweight serialization frameworks for constrained heterogeneous devices. The serialization maps various device role and behaviors to the data by encoding at the device level. On the one hand, reduced table sizes can help to store and retrieve data efficiently. On the other hand, the devices use additional computational power for the encoding of information. This also opens up debates about a major study gap in the benchmarks for IoT-related energy saving schemes.
Maarala et al.
[136][78] presented an evaluation model to test various sizes of IoT networks and corresponding semantics reasoning data. Maintaining performance, scalability, and interoperability as their primary goals, researchers calculated latencies imposed by various semantic models. During the assessment of semantic models, the researchers suggested data aggregation strategies suitable for the heterogeneous IoT network. The experimental results claim that distributed reasoning with Entity Notation (EN) formats outperforms other techniques. The results also summarized the possibility of having multiple reasoning nodes with a short EN format as the best case. The researchers also proposed that time-based aggregation produces a more stable output as compared to other strategies. Many researchers also focus on content caching schemes that reduce the energy consumption footprint for IoT networks
[137][79].
The research provided a rigorous model for analysing emerging semantic technologies and determining the best supply cases. The effects of data formats on centralised structures, on the other hand, have not been reported. Another notable trend in their research is the similarity and uniformity in latencies as system resources or overall throughput increase, whereas this may not be the case in real-world heterogeneous IoT systems.