<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Bohr. Scit.</journal-id>
<journal-title>BOHR International Journal of Smart Computing and Information Technology</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Bohr. Scit.</abbrev-journal-title>
<issn pub-type="epub">2583-2026</issn>
<publisher>
<publisher-name>BOHR</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.54646/bijscit.2026.51</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Research</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Adaptive context-aware middleware for seamless integration and service optimization in smart environments</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name><surname>Franklin</surname> <given-names>Mission</given-names></name>
<xref ref-type="corresp" rid="c001"><sup>&#x002A;</sup></xref>
</contrib>
</contrib-group>
<aff><institution>Department of Computer Engineering, Rivers State University</institution>, <addr-line>Port Harcourt</addr-line>, <country>Nigeria</country></aff>
<author-notes>
<corresp id="c001">&#x002A;Correspondence: Mission Franklin, <email>mission.franklin@ust.edu.ng</email></corresp>
</author-notes>
<pub-date pub-type="epub">
<day>29</day>
<month>05</month>
<year>2026</year>
</pub-date>
<volume>7</volume>
<issue>1</issue>
<fpage>10</fpage>
<lpage>21</lpage>
<history>
<date date-type="received">
<day>18</day>
<month>02</month>
<year>2026</year>
</date>
<date date-type="accepted">
<day>13</day>
<month>05</month>
<year>2026</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#x00A9; 2026 Franklin.</copyright-statement>
<copyright-year>2026</copyright-year>
<copyright-holder>Franklin</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>&#x00A9; The Author(s). 2024 Open Access This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.</p></license>
</permissions>
<abstract>
<p>The rapid growth of the internet of things (IoT) and the rise of smart environments have increased the need for middleware systems that can support seamless communication among diverse devices while adapting to changing conditions. Many existing middleware solutions struggle with device heterogeneity, scalability, and real-time responsiveness, often leading to inefficiencies in performance and service delivery. To address these limitations, this study proposes an Adaptive Context-Aware Middleware framework designed to enable seamless integration and service optimization in smart environments. The framework continuously observes environmental and user contexts and dynamically adjusts system behavior to meet changing demands. It is built on four core components: context acquisition, context modeling, context reasoning, and adaptive management. These components work together to interpret real-time data and support intelligent decision-making within the system. The proposed framework was evaluated through simulation-based experiments under different workload scenarios. The results show that it consistently outperforms traditional static and conventional dynamic middleware approaches. In particular, it achieves lower latency, higher throughput, and improved system stability under increasing load conditions. The adaptive design also demonstrates strong scalability and flexibility, allowing it to operate effectively in diverse smart environments. These include applications such as smart homes, healthcare monitoring systems, intelligent transportation systems, and industrial IoT infrastructures. The findings indicate that adaptive context-aware middleware significantly improves system performance by enabling better integration of devices, optimizing resource usage, and enhancing service delivery. This makes it a promising approach for managing the complexity and dynamism of modern IoT-enabled environments.</p>
</abstract>
<kwd-group>
<kwd>adaptive middleware</kwd>
<kwd>context awareness</kwd>
<kwd>smart environments</kwd>
<kwd>internet of things (IoT)</kwd>
<kwd>real-time adaptation</kwd>
<kwd>resource optimization</kwd>
</kwd-group>
<counts>
<fig-count count="8"/>
<table-count count="1"/>
<equation-count count="7"/>
<ref-count count="31"/>
<page-count count="12"/>
<word-count count="5919"/>
</counts>
</article-meta>
</front>
<body>
<sec id="S1" sec-type="intro">
<title>Introduction</title>
<p>Adaptive context-aware middleware has become a critical infrastructural layer for enabling smart environments such as smart homes, intelligent offices, and pervasive computing ecosystems. These environments rely on systems that can continuously sense, interpret, and respond to changing environmental conditions and user contexts (<xref ref-type="bibr" rid="B1">1</xref>). With the rapid expansion of interconnected devices driven by the internet of things (IoT), the role of middleware has become increasingly important in managing system complexity, supporting interoperability among heterogeneous devices, and facilitating efficient service delivery (<xref ref-type="bibr" rid="B2">2</xref>, <xref ref-type="bibr" rid="B3">3</xref>). In this regard, context-aware middleware extends the capabilities of traditional middleware by incorporating mechanisms for context acquisition, modeling, reasoning, and adaptation (<xref ref-type="bibr" rid="B4">4</xref>). Through these capabilities, systems are able to dynamically modify their behavior in response to variations in user activities, device states, and environmental conditions (<xref ref-type="bibr" rid="B2">2</xref>, <xref ref-type="bibr" rid="B5">5</xref>).</p>
<p>Within smart environments, context awareness refers to a system&#x2019;s ability to detect and utilize relevant information about its surrounding environment and users. Such information may include user location, device status, time, environmental conditions, and patterns of user activity (<xref ref-type="bibr" rid="B6">6</xref>). By capturing and interpreting this contextual information, systems can provide services that are more responsive and tailored to specific situations (<xref ref-type="bibr" rid="B7">7</xref>, <xref ref-type="bibr" rid="B8">8</xref>). As a result, context-aware middleware contributes significantly to improved system usability, efficiency, and overall user experience (<xref ref-type="bibr" rid="B9">9</xref>). Without a middleware layer capable of managing and processing context data effectively, developers of distributed applications would face considerable difficulties in dealing with system heterogeneity, rapidly changing environments, and the need for real-time service adaptation.</p>
<p>Adaptive middleware builds upon the principles of context awareness by enabling systems to dynamically reconfigure their behavior during runtime in response to evolving user needs and environmental changes (<xref ref-type="bibr" rid="B10">10</xref>). This capability addresses several limitations associated with static architectures, which often lack the flexibility required to handle fluctuating workloads and contextual variations (<xref ref-type="bibr" rid="B11">11</xref>). In IoT-driven smart environments, adaptive context-aware middleware can enhance system performance by optimizing resource allocation, reducing response times (<xref ref-type="bibr" rid="B12">12</xref>, <xref ref-type="bibr" rid="B13">13</xref>), and supporting personalized services across diverse devices and communication protocols (<xref ref-type="bibr" rid="B14">14</xref>, <xref ref-type="bibr" rid="B15">15</xref>).</p>
<p>Previous research has proposed various frameworks and architectures aimed at improving adaptive middleware systems through contextual reasoning and dynamic reconfiguration (<xref ref-type="bibr" rid="B16">16</xref>). For instance, adaptive ubiquitous middleware frameworks have been developed to intelligently manage heterogeneous IoT ecosystems by incorporating multiple context sources and monitoring network conditions to achieve lower latency and improved quality of service (<xref ref-type="bibr" rid="B15">15</xref>). Similarly, reconfigurable context-sensitive middleware designed for pervasive computing environments has demonstrated improved interoperability and responsiveness by dynamically adjusting device interactions based on real-time contextual information (<xref ref-type="bibr" rid="B5">5</xref>, <xref ref-type="bibr" rid="B17">17</xref>).</p>
<p>Despite these advances, many existing middleware architectures still fall short of fully integrating all stages of the context lifecycle, including comprehensive context modeling, efficient reasoning mechanisms, and effective adaptive decision-making processes. These limitations highlight persistent challenges related to scalability, reasoning efficiency, and real-time responsiveness in complex smart environments (<xref ref-type="bibr" rid="B2">2</xref>). Consequently, there remains a strong need for middleware solutions that not only support context awareness but also provide robust adaptive capabilities capable of meeting the performance, scalability, and personalization requirements of next-generation smart systems.</p>
<sec id="S1.SS1">
<title>Problem statement</title>
<p>The rapid expansion of IoT technologies and the growing adoption of smart environments have created highly complex and heterogeneous ecosystems in which numerous devices, sensors, and applications must interact seamlessly (<xref ref-type="bibr" rid="B18">18</xref>). These environments often involve devices that operate using different communication protocols, data formats, and functional capabilities (<xref ref-type="bibr" rid="B25">25</xref>). However, many traditional middleware solutions were not originally designed to manage such levels of diversity and dynamism. As a result, they frequently rely on relatively static architectures that provide limited support for context awareness and dynamic adaptation. This limitation makes it difficult for middleware to effectively integrate heterogeneous devices and ensure smooth interoperability across diverse platforms (<xref ref-type="bibr" rid="B2">2</xref>).</p>
<p>Another major challenge lies in the limited ability of conventional middleware systems to acquire, model, and reason about contextual information in real time. Contextual information, such as user behavior, environmental conditions, device status, and network changes, is essential for enabling intelligent system responses in smart environments (<xref ref-type="bibr" rid="B20">20</xref>, <xref ref-type="bibr" rid="B21">21</xref>). When middleware systems lack robust mechanisms for managing this contextual information, system responses may become delayed or less effective, thereby reducing the overall responsiveness and usefulness of smart applications (<xref ref-type="bibr" rid="B5">5</xref>, <xref ref-type="bibr" rid="B7">7</xref>).</p>
<p>Furthermore, many existing middleware frameworks do not possess the capability to dynamically reconfigure their operations in response to changing system conditions. Factors such as fluctuating workloads, variations in network performance, and evolving user requirements demand flexible systems that can adapt their behavior in real time. Without such adaptability, middleware systems may experience inefficient resource utilization, increased latency, and reduced overall system performance (<xref ref-type="bibr" rid="B15">15</xref>).</p>
<p>Scalability and performance also present significant challenges in modern IoT environments. As the number of connected devices continues to increase, middleware frameworks must handle higher volumes of data and interactions while still maintaining service quality, reliability, and low latency. These limitations underscore the urgent need for middleware solutions that combine context awareness with adaptive capabilities (<xref ref-type="bibr" rid="B22">22</xref>). An adaptive context-aware middleware framework capable of monitoring environmental conditions (<xref ref-type="bibr" rid="B23">23</xref>, <xref ref-type="bibr" rid="B24">24</xref>), interpreting real-time context, and dynamically adjusting system behaviour could significantly improve the robustness, scalability, and responsiveness of smart environments (<xref ref-type="bibr" rid="B25">25</xref>). Such advancements would support a wide range of applications, including smart homes, healthcare monitoring systems, industrial IoT infrastructures, and other pervasive computing domains (<xref ref-type="bibr" rid="B26">26</xref>).</p>
</sec>
<sec id="S1.SS2">
<title>Aim and objectives of the study</title>
<p>The aim of this study is to develop and evaluate an adaptive context-aware middleware that improves performance and enables dynamic interaction among heterogeneous IoT devices in smart environments.</p>
</sec>
<sec id="S1.SS3">
<title>The objectives of the study are</title>
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Analyze existing middleware architectures to identify limitations in context awareness and adaptability.</p>
</list-item>
<list-item>
<label>2.</label>
<p>Design a context-aware middleware framework incorporating context acquisition, reasoning, and adaptation.</p>
</list-item>
<list-item>
<label>3.</label>
<p>Implement the framework to support real-time adaptive behavior.</p>
</list-item>
<list-item>
<label>4.</label>
<p>Evaluate system performance using metrics such as latency, throughput, consistency, and robustness.</p>
</list-item>
<list-item>
<label>5.</label>
<p>Assess its applicability in smart homes, healthcare systems, and industrial IoT environments.</p>
</list-item>
</list>
</sec>
<sec id="S1.SS4">
<title>Significance and scope of the study</title>
<p>This study contributes an adaptive context-aware middleware framework that enhances service personalization, responsiveness, and efficiency in smart environments. The framework improves resource and energy utilization, supports heterogeneous devices, and enables real-time context acquisition, prediction, and adaptive service management. Its performance is evaluated through simulations and testbed experiments under varying workloads, demonstrating its suitability for real-world applications, including smart homes, healthcare systems, and industrial IoT deployments.</p>
</sec>
<sec id="S1.SS5">
<title>Literature review</title>
<sec id="S1.SS5.SSS1">
<title>Context-aware middleware in smart environments</title>
<p>Middleware is essential in smart environments for managing heterogeneous IoT devices and enabling seamless service delivery (<xref ref-type="bibr" rid="B27">27</xref>). While traditional middleware focuses on device interoperability and message exchange, it often lacks real-time context awareness (<xref ref-type="bibr" rid="B2">2</xref>). Context-aware middleware addresses this gap by sensing, interpreting, and responding to contextual information such as user location, device status, and environmental conditions (<xref ref-type="bibr" rid="B7">7</xref>, <xref ref-type="bibr" rid="B8">8</xref>), allowing systems to provide more relevant and adaptive services that enhance user experience and efficiency.</p>
</sec>
<sec id="S1.SS5.SSS2">
<title>Adaptive middleware approaches</title>
<p>While context-aware middleware improves responsiveness, adaptive middleware is crucial for dynamically handling changing environments, workloads, and user behaviors. These frameworks combine context reasoning with real-time system reconfiguration, adjusting resource allocation, service quality, and operational strategies as needed (<xref ref-type="bibr" rid="B5">5</xref>, <xref ref-type="bibr" rid="B15">15</xref>). Adaptive middleware also helps mitigate challenges such as network congestion, device failures, and workload spikes, enhancing system robustness and reliability in pervasive computing environments (<xref ref-type="bibr" rid="B11">11</xref>).</p>
</sec>
<sec id="S1.SS5.SSS3">
<title>Context modeling and reasoning</title>
<p>Adaptive middleware depends on effective context modeling and reasoning. Context is commonly represented using key-value pairs, ontologies, or semantic graphs (<xref ref-type="bibr" rid="B28">28</xref>). Reasoning techniques, such as rule-based engines, probabilistic models, and machine learning, allow systems to derive meaningful insights from raw data. For instance, Do et al. (<xref ref-type="bibr" rid="B15">15</xref>) proposed a middleware framework that leverages predictive context reasoning to adjust services proactively, reducing latency and improving throughput in smart IoT environments.</p>
</sec>
<sec id="S1.SS5.SSS4">
<title>Applications in smart environments</title>
<p>Adaptive context-aware middleware has demonstrated significant benefits across various domains. In smart homes, it enables energy management and personalized automation based on occupancy and user behavior (<xref ref-type="bibr" rid="B14">14</xref>, <xref ref-type="bibr" rid="B29">29</xref>). In healthcare, it supports real-time patient monitoring, triggering timely alerts and interventions. Industrial IoT systems use adaptive middleware to optimize resource allocation (<xref ref-type="bibr" rid="B30">30</xref>) and maintenance scheduling, reducing downtime and improving production efficiency (<xref ref-type="bibr" rid="B15">15</xref>). These examples illustrate how adaptive middleware can enhance operational performance and service quality in diverse smart environments.</p>
</sec>
<sec id="S1.SS5.SSS5">
<title>Challenges and research gaps</title>
<p>Despite recent advancements, several challenges persist in adaptive context-aware middleware. Scalability remains an issue in environments with many devices and high data volumes. Real-time reasoning and adaptation can introduce computational overhead, affecting latency and responsiveness. Integrating security and privacy measures into adaptive frameworks also remains a key concern. These gaps emphasize the need for middleware that balances adaptability, efficiency, and security while maintaining robust performance in heterogeneous smart environments.</p>
</sec>
</sec>
<sec id="S1.SS6">
<title>Empirical review</title>
<p>Li et al. (<xref ref-type="bibr" rid="B2">2</xref>) conducted a comprehensive review of existing context-aware middleware architectures, evaluating them on features such as context acquisition, modeling, reasoning, adaptability, and scalability. Their study found that while many frameworks support basic context awareness, they often lack the adaptivity required for dynamic smart environments. Key limitations included handling heterogeneous devices, processing context information in real time, and maintaining scalability under high device loads. This work highlights critical gaps in current middleware and underscores the need for frameworks capable of dynamically adapting to changing environmental and user contexts.</p>
<p>Do et al. (<xref ref-type="bibr" rid="B15">15</xref>) proposed an adaptive ubiquitous middleware framework for IoT ecosystems that integrates context acquisition, predictive reasoning, and adaptive resource management. They implemented a prototype and evaluated it through simulations representing smart homes and industrial IoT scenarios. Results showed that the middleware significantly reduced latency and improved throughput under varying workloads. By using predictive context reasoning, the system could proactively adjust services, minimizing bottlenecks and enhancing user experience. This study provides empirical evidence that embedding predictive adaptation in middleware improves responsiveness and performance in heterogeneous smart environments.</p>
<p>Yadav Yanamala and Suryadevara (<xref ref-type="bibr" rid="B5">5</xref>) developed a middleware framework for adaptive, context-aware pervasive computing. Their system collected real-time context data, used rule-based reasoning, and dynamically reconfigured services to respond to changes in the environment and user behavior. Evaluated on a small-scale smart home testbed, the framework improved service personalization and energy efficiency, maintaining performance during sudden fluctuations in sensor activity or user actions. This study highlights the value of real-time context reasoning and adaptive service delivery for managing dynamic and unpredictable environments.</p>
<p>Gubbi et al. (<xref ref-type="bibr" rid="B14">14</xref>) examined IoT frameworks and middleware architectures in smart environments, focusing on smart homes and energy management. Their study showed that middleware with context awareness and adaptive resource allocation can optimize energy use and improve service quality. However, challenges with device heterogeneity and scalability were noted, highlighting the need to balance adaptability with operational efficiency. The findings emphasize the practical benefits of adaptive middleware in enabling energy-efficient and responsive IoT systems.</p>
<p>Roman et al. (<xref ref-type="bibr" rid="B11">11</xref>) proposed an adaptive middleware model that supports context-aware services through dynamic reconfiguration. They tested the system via simulations under varying network and device conditions. Results showed that adaptive middleware-maintained service quality during network congestion and device failures, with dynamic reconfiguration reducing disruptions and enhancing reliability. This study provides strong evidence that adaptivity is crucial for resilience and continuous service delivery in smart and IoT environments.</p>
<p>Michalakis et al. (<xref ref-type="bibr" rid="B31">31</xref>) developed context-aware middleware that integrates semantic context modeling with reasoning techniques to enable adaptive behavior in pervasive computing environments. By using formal context models and hybrid reasoning, the system can infer high-level situational information from raw sensor data. Evaluations in real-world deployments with multiple devices showed that it efficiently represents context, supports adaptive service decisions, and scales effectively, demonstrating the benefits of ontology-based semantic modeling for enhancing middleware adaptability.</p>
</sec>
</sec>
<sec id="S2">
<title>Methodology</title>
<sec id="S2.SS1">
<title>Research design</title>
<p>This study uses a design science and experimental approach to build and test an adaptive context-aware middleware for seamless integration and service optimization in smart environments. The focus is on developing a working system and then evaluating how well it performs under different conditions.</p>
</sec>
<sec id="S2.SS2">
<title>System development environment</title>
<p>The middleware is developed in a Java-based programming environment and built on an IoT-focused architecture. This setup is designed to support communication and interaction between different types of smart devices in a distributed environment.</p>
</sec>
<sec id="S2.SS3">
<title>Middleware architecture</title>
<p>The system is structured around four main components: context acquisition, context modeling, context reasoning, and adaptive service management. Together, these modules allow the middleware to understand changes in the environment and adjust services automatically to ensure smooth operation.</p>
</sec>
<sec id="S2.SS4">
<title>Experimental setup and simulation tools</title>
<p>The system is tested using CloudSim and MATLAB simulation tools, along with a small IoT testbed made up of different sensors and smart devices. These tools help recreate real-world smart environment conditions such as changing workloads and network variability.</p>
</sec>
<sec id="S2.SS5">
<title>Performance evaluation metrics</title>
<p>The evaluation focuses on important performance indicators such as latency, throughput, consistency overhead, resource usage, and system reliability, especially when the system is under stress like network congestion or device failure.</p>
</sec>
<sec id="S2.SS6">
<title>Workload and scenario design</title>
<p>Different workload patterns and changing context scenarios are introduced to see how well the system adapts to real-life conditions and maintains good service performance.</p>
</sec>
<sec id="S2.SS7">
<title>Comparative analysis and data evaluation</title>
<p>The proposed middleware is compared with traditional static and dynamic middleware systems. The results are analyzed using statistical methods and visual charts to clearly show improvements in performance, scalability, and service optimization.</p>
</sec>
<sec id="S2.SS8">
<title>Proposed adaptive context-aware middleware: UML-style model description</title>
<p>The Adaptive Context-Aware Middleware for Seamless Integration and Service Optimization in Smart Environments is modeled as a layered system composed of interacting components responsible for context processing, decision-making, and service adaptation. This UML-style model represents the middleware as a modular, layered, and event-driven system where context flows from IoT devices through processing modules, culminating in adaptive service optimization decisions that enhance performance in smart environments.</p>
<p>The class diagram as shown in <xref ref-type="fig" rid="F1">Figure 1</xref> shows the main building blocks of the Adaptive Context-Aware Middleware and how they interact. It includes the IoTDevice, which generates sensor data and receives control commands. The Context Acquisition class collects this data, while the Context Model organizes it into structured context information. The Context Reasoning Engine then interprets the context to detect situations and support decision-making. At the center is the Middleware Controller, which coordinates all components, manages system operations, and ensures smooth communication between modules. The class diagram represents the system&#x2019;s structure and the relationships between its core components.</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption><p>Class diagram (logical structure) of the adaptive context-aware middleware.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g001.tif"/>
</fig>
</sec>
<sec id="S2.SS9">
<title>Component diagram</title>
<p>The component diagram as shown in <xref ref-type="fig" rid="F2">Figure 2</xref> shows the main functional parts of the middleware and how they interact at a high level. It illustrates how IoT Devices send data into the Context Acquisition component, which processes and forwards it to Context modeling. The data is then interpreted by the Context Reasoning component, which generates meaningful insights. Based on these insights, the Adaptive Service Management component adjusts system behavior to optimize performance and service delivery. Finally, the results are delivered to the Application Services layer. The figure highlights how the middleware is organized into modular components and how data flows through the system to achieve seamless integration and service optimization.</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption><p>Component diagram (system view) of the adaptive context-aware middleware.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g002.tif"/>
</fig>
<p>The <xref ref-type="fig" rid="F3">Figure 3</xref> is a sequence diagram, which shows how the system components interact step by step over time when processing data. It begins with an IoT device sending sensor data to the middleware. The Context Acquisition module receives and processes this data, then passes it to Context Modeling, where it is structured into meaningful context. Next, the Reasoning Engine analyzes the context to generate decisions or detect situations. Finally, the Adaptive Service Manager uses these decisions to adjust system behavior and send adaptation commands back to the system or applications. The sequence diagram illustrates the real-time flow of information and how the middleware responds dynamically to changing conditions.</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption><p>Sequence diagram (runtime behavior) of the adaptive context-aware middleware.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g003.tif"/>
</fig>
<p>The deployment diagram as shown in <xref ref-type="fig" rid="F4">Figure 4</xref> shows how the middleware system is physically distributed across different computing environments. It illustrates three main layers: the Edge Layer, where IoT devices such as sensors and actuators operate and generate data; the Middleware Layer, which runs the core components (context acquisition, modeling, reasoning, and adaptive service management) on a Java-based runtime; and the Cloud/Server Layer, which provides storage, analytics, and monitoring services. The diagram explains how the system is deployed in a real-world smart environment, showing where each component runs and how data moves from edge devices to cloud services for processing and optimization.</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption><p>Deployment diagram (physical architecture) of the adaptive context-aware middleware.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g004.tif"/>
</fig>
</sec>
<sec id="S2.SS10">
<title>Mathematical models</title>
<p><xref ref-type="fig" rid="F5">Figure 5</xref> illustrates a middleware performance optimization framework designed to achieve adaptive system behavior by integrating latency, throughput, consistency, and resource utilization. The framework consists of the following components: (1) Adaptive Decision Module (central block), (2) Latency Model (blue), (3) Throughput Model (green), (4) Consistency Overhead Model (orange), (5) Resource Utilization Model (red), and (6) Optimized Performance and Adaptivity (bottom).</p>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption><p>Optimized performance and adaptivity framework.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g005.tif"/>
</fig>
<sec id="S2.SS10.SSS1">
<title>Latency model</title>
<p>Let (<italic>L<sub>r</sub></italic>) and (<italic>L<sub>w</sub></italic>) denote read latency and write latency (ms), respectively, for a distributed smart environment. Latency can be modeled as:</p>
<disp-formula id="S2.E1">
<label>(1)</label>
<mml:math id="M1">
<mml:mrow>
<mml:mpadded width="+3.3pt">
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>r</mml:mi>
</mml:msub>
</mml:mpadded>
<mml:mo rspace="5.8pt">=</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>min</mml:mi>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>net</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>u</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>proc</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
<disp-formula id="S2.E2">
<label>(2)</label>
<mml:math id="M2">
<mml:mrow>
<mml:mpadded width="+3.3pt">
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>w</mml:mi>
</mml:msub>
</mml:mpadded>
<mml:mo rspace="5.8pt">=</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>max</mml:mi>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>net</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>u</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>proc</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>sync</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
<p>Where: <italic>R</italic> = set of replicas in the system, <italic>L</italic><sub><italic>net</italic></sub>(<italic>u</italic>,<italic>i</italic>) = network delay between user (<italic>u</italic>) and replica (<italic>i</italic>), <italic>L</italic><sub><italic>proc</italic></sub>(<italic>i</italic>) = processing time at replica (<italic>i</italic>), <italic>L</italic><sub><italic>sync</italic></sub>(<italic>i</italic>) = <italic>time</italic> to synchronize replica (<italic>i</italic>) with other replicas. Adaptive middleware in equation (1) reduces (<italic>L<sub>r</sub></italic>) by placing replicas closer to high-demand regions and reduces (<italic>L</italic><sub><italic>w</italic></sub>) by optimizing replica synchronization as expressed in equation (2).</p>
</sec>
<sec id="S2.SS10.SSS2">
<title>Throughput model</title>
<p>Throughput (<italic>T</italic>) is defined as the number of successful operations per second:</p>
<disp-formula id="S2.E3">
<label>(3)</label>
<mml:math id="M3">
<mml:mrow>
<mml:mpadded width="+3.3pt">
<mml:mi>T</mml:mi>
</mml:mpadded>
<mml:mo rspace="5.8pt">=</mml:mo>
<mml:mfrac>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mi>ops</mml:mi>
</mml:msub>
<mml:msub>
<mml:mi>t</mml:mi>
<mml:mi>total</mml:mi>
</mml:msub>
</mml:mfrac>
</mml:mrow>
</mml:math>
</disp-formula>
<p>Where: <italic>N</italic><sub><italic>ops</italic></sub> = total number of successfully completed read/write operations, <italic>t</italic><sub><italic>total</italic></sub> = total time of operation execution.</p>
<p>Adaptive middleware improves (<italic>T</italic>) in equation (3) by distributing requests among multiple replicas and reducing contention.</p>
</sec>
<sec id="S2.SS10.SSS3">
<title>Consistency overhead model</title>
<p>Consistency overhead, (<italic>C</italic><sub><italic>o</italic></sub>)as shown in equation (4), can be measured as the additional messages or time required to maintain consistency among replicas:</p>
<disp-formula id="S2.E4">
<label>(4)</label>
<mml:math id="M4">
<mml:mrow>
<mml:mpadded width="+3.3pt">
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mi>o</mml:mi>
</mml:msub>
</mml:mpadded>
<mml:mo rspace="5.8pt">=</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mo largeop="true" symmetric="true">&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:msub>
<mml:mo largeop="true" symmetric="true">&#x2211;</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
<mml:mo>,</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:msub>
<mml:mi>M</mml:mi>
<mml:mi>sync</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
<p>Where: (<italic>M</italic><sub><italic>sync</italic></sub>(<italic>i</italic>,<italic>j</italic>)) = number of messages exchanged or time spent to synchronize replica (<italic>i</italic>) with (<italic>j</italic>), and (<italic>R</italic>)= set of replicas. The adaptive replication may slightly increase (<italic>C<sub>o</sub></italic>) to achieve lower latency and higher throughput.</p>
</sec>
<sec id="S2.SS10.SSS4">
<title>Resource utilization model</title>
<p>Let (<italic>U<sub>c</sub></italic>) denote CPU utilization in equation (5) and (<italic>U<sub>n</sub></italic>) network utilization in equation (6):</p>
<disp-formula id="S2.E5">
<label>(5)</label>
<mml:math id="M5">
<mml:mrow>
<mml:mpadded width="+3.3pt">
<mml:msub>
<mml:mi>U</mml:mi>
<mml:mi>c</mml:mi>
</mml:msub>
</mml:mpadded>
<mml:mo rspace="5.8pt">=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mo largeop="true" symmetric="true">&#x2211;</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:mpadded width="+5pt">
<mml:mi>i</mml:mi>
</mml:mpadded>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
<mml:mo>,</mml:mo>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:mi>j</mml:mi>
</mml:mrow>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi>proc</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi>sim</mml:mi>
</mml:msub>
</mml:mfrac>
</mml:mrow>
</mml:math>
</disp-formula>
<disp-formula id="S2.E6">
<label>(6)</label>
<mml:math id="M6">
<mml:mrow>
<mml:mpadded width="+3.3pt">
<mml:msub>
<mml:mi>U</mml:mi>
<mml:mi>n</mml:mi>
</mml:msub>
</mml:mpadded>
<mml:mo rspace="5.8pt">=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mo largeop="true" symmetric="true">&#x2211;</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi>
</mml:mrow>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
<mml:mo>,</mml:mo>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2260;</mml:mo>
<mml:mi>j</mml:mi>
</mml:mrow>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mi>b</mml:mi>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:msub>
<mml:mi>B</mml:mi>
<mml:mi>total</mml:mi>
</mml:msub>
</mml:mfrac>
</mml:mrow>
</mml:math>
</disp-formula>
<p>where: <italic>t</italic><sub>{proc}</sub>(<italic>i</italic>) = CPU processing time for replica (i), <italic>T</italic><sub>{sim}</sub> = total simulation or operation time, <italic>b</italic><sub><italic>{i,j}</italic></sub> = data exchanged between replicas (<italic>i</italic>) and (<italic>j</italic>), <italic>B</italic><sub>{total}</sub> = total available network bandwidth. These models in equations (5) and (6) quantify the efficiency and scalability respectively of adaptive middleware under different workloads.</p>
</sec>
<sec id="S2.SS10.SSS5">
<title>Adaptive replica placement decision model</title>
<p>Let (<italic>x</italic><sub><italic>i</italic></sub> &#x2208; {0,1}) denote whether a replica is placed at a node (<italic>i</italic>). The placement is optimized to minimize read latency and maintain consistency, as shown in equation (7):</p>
<disp-formula id="S2.E7">
<label>(7)</label>
<mml:math id="M7">
<mml:mrow>
<mml:mrow>
<mml:mi>min</mml:mi>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mo largeop="true" symmetric="true">&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>u</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>U</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mrow>
<mml:msub>
<mml:mo largeop="true" symmetric="true">&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>R</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:mrow>
</mml:mrow>
<mml:mo>.</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:mi>net</mml:mi>
</mml:msub>
<mml:mo>&#x2062;</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mi>u</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
<p>Subject to: &#x2211;<italic>x</italic><sub><italic>i</italic></sub>=<italic>k</italic>; <italic>C</italic><sub><italic>o</italic></sub>&#x2264;<italic>C</italic><sub><italic>max</italic></sub></p>
<p>where: (<italic>U</italic>) = set of users, (<italic>k</italic>)= total number of replicas, and (<italic>C</italic><sub>{<italic>max</italic>}</sub>) = maximum acceptable consistency overhead. This model formalizes adaptive decision-making in replica placement, balancing latency reduction and consistency costs.</p>
<p>This framework is a feedback-driven adaptive middleware system that uses latency, throughput, consistency, and resource utilization as inputs. An adaptive decision module dynamically places replicas and adjusts operations, achieving optimized performance with lower latency, higher throughput, controlled consistency overhead, and efficient use of CPU and network resources.</p>
</sec>
</sec>
</sec>
<sec id="S3">
<title>Results and finding</title>
<p>The middleware&#x2019;s performance under different scenarios (S1&#x2013;S5) is evaluated using three key metrics: latency, throughput, and consistency overhead.</p>
<sec id="S3.SS1">
<title>Latency comparison</title>
<p><xref ref-type="fig" rid="F6">Figure 6</xref> compares latency across middleware types, showing a consistent decrease from static to dynamic and then adaptive middleware across all scenarios. Static middleware exhibits the highest and increasing delays (120&#x2013;180 ms), reflecting poor scalability. Dynamic middleware lowers latency moderately (95&#x2013;150 ms) but still rises with load. Adaptive middleware achieves the lowest and most stable latency (65&#x2013;85 ms), reducing delays by up to 50% compared to static systems. This demonstrates that adaptive mechanisms handle workload fluctuations more efficiently, making them well-suited for latency-sensitive environments.</p>
<fig id="F6" position="float">
<label>FIGURE 6</label>
<caption><p>Latency comparison (ms).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g006.tif"/>
</fig>
</sec>
<sec id="S3.SS2">
<title>Throughput comparison</title>
<p><xref ref-type="fig" rid="F7">Figure 7</xref> compares throughput across middleware types, showing steady improvement from static to dynamic and then adaptive middleware across all scenarios. Static middleware exhibits the lowest and decreasing throughput (200&#x2013;160 ops/sec), reflecting limited scalability. Dynamic middleware provides moderate gains, while adaptive middleware consistently achieves the highest throughput (290&#x2013;320 ops/sec), improving performance by up to 80% over static systems. This demonstrates that adaptive optimization effectively maintains higher system capacity under increasing workloads.</p>
<fig id="F7" position="float">
<label>FIGURE 7</label>
<caption><p>Throughput comparison (ops/sec).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g007.tif"/>
</fig>
</sec>
<sec id="S3.SS3">
<title>Consistency overhead</title>
<p><xref ref-type="fig" rid="F8">Figure 8</xref> shows consistency overhead, where Adaptive middleware experiences only a modest increase, rising from 10% in S1 to 15% in S5. In comparison, Dynamic middleware overhead grows faster (8%&#x2013;18%). Adaptive mechanisms manage consistency efficiently, keeping overhead low while delivering significant latency and throughput benefits.</p>
<fig id="F8" position="float">
<label>FIGURE 8</label>
<caption><p>Consistency overhead (%).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="bijscit-2026-51-g008.tif"/>
</fig>
<sec id="S3.SS3.SSS1">
<title>Comparison of middleware approaches</title>
<p>Refer to <xref ref-type="table" rid="T1">Table 1</xref> for additional information.</p>
<table-wrap position="float" id="T1">
<label>TABLE 1</label>
<caption><p>Comparison of static, dynamic, and adaptive middleware.</p></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Feature/metric</td>
<td valign="top" align="left">Static middleware</td>
<td valign="top" align="left">Dynamic middleware</td>
<td valign="top" align="left">Proposed adaptive context-aware middleware</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left"><bold>Context awareness</bold></td>
<td valign="top" align="left">Very low / none</td>
<td valign="top" align="left">Moderate</td>
<td valign="top" align="left">High (real-time context-aware)</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Adaptation type</bold></td>
<td valign="top" align="left">No adaptation</td>
<td valign="top" align="left">Reactive adaptation</td>
<td valign="top" align="left">Proactive and continuous adaptation</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Latency</bold></td>
<td valign="top" align="left">High: 120&#x2013;180 ms (increases with load)</td>
<td valign="top" align="left">Medium: 95&#x2013;150 ms (variable)</td>
<td valign="top" align="left">Low and stable: 65&#x2013;85 ms</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Throughput</bold></td>
<td valign="top" align="left">Low: 200&#x2013;160 ops/sec (declines)</td>
<td valign="top" align="left">Moderate: improves but unstable</td>
<td valign="top" align="left">High and stable: 290&#x2013;320 ops/sec</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Consistency overhead</bold></td>
<td valign="top" align="left">Not optimized / inefficient under load</td>
<td valign="top" align="left">8%&#x2013;18% (increases faster)</td>
<td valign="top" align="left">10%&#x2013;15% (controlled and stable)</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Scalability</bold></td>
<td valign="top" align="left">Poor</td>
<td valign="top" align="left">Moderate</td>
<td valign="top" align="left">Strong (supports IoT growth)</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Resource utilization</bold></td>
<td valign="top" align="left">Inefficient</td>
<td valign="top" align="left">Partially optimized</td>
<td valign="top" align="left">Highly optimized</td>
</tr>
<tr>
<td valign="top" align="left"><bold>System stability</bold></td>
<td valign="top" align="left">Low</td>
<td valign="top" align="left">Moderate</td>
<td valign="top" align="left">High stability under varying workloads</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Performance trend</bold></td>
<td valign="top" align="left">Degrades as workload increases</td>
<td valign="top" align="left">Improves but fluctuates</td>
<td valign="top" align="left">Consistently optimal across scenarios</td>
</tr>
<tr>
<td valign="top" align="left"><bold>Service optimization</bold></td>
<td valign="top" align="left">Minimal</td>
<td valign="top" align="left">Partial optimization</td>
<td valign="top" align="left">Full optimization with adaptive control</td>
</tr>
</tbody>
</table></table-wrap>
</sec>
<sec id="S3.SS3.SSS2">
<title>Static middleware (traditional approach)</title>
<p>As shown in the comparison of <xref ref-type="table" rid="T1">Table 1</xref>, static middleware exhibits the poorest performance across all evaluated metrics. The graphs in <xref ref-type="fig" rid="F6">Figures 6</xref> and <xref ref-type="fig" rid="F7">7</xref> indicate consistently high latency and low throughput, with performance worsening as workload increases. This is because static middleware relies on fixed configurations and does not adjust to environmental changes. The accompanying results confirm that latency remains high (around 120&#x2013;180 ms), throughput is the lowest (200&#x2013;160 ops/sec), and scalability is limited, which shows that static middleware is unsuitable for dynamic smart environments due to its inability to adapt.</p>
</sec>
<sec id="S3.SS3.SSS3">
<title>Dynamic middleware (conventional approach)</title>
<p><xref ref-type="table" rid="T1">Table 1</xref> shows the comparison of Dynamics middleware as it compare against static and adaptive, which supports what the <xref ref-type="fig" rid="F6">Figures 6</xref>&#x2013;<xref ref-type="fig" rid="F8">8</xref> show; that dynamic middleware performs better than static middleware, with moderate improvements in both latency and throughput. However, its performance still fluctuates as workload increases, indicating limited stability. Latency decreases compared to static systems but still rises under heavy load, while throughput shows improvement but not consistency. Simulation results show moderate latency reduction (95&#x2013;150 ms) and improved throughput compared to static systems but also highlight increasing overhead and instability under stress. The results confirm that dynamic middleware provides partial adaptability but remains reactive rather than fully optimized.</p>
</sec>
<sec id="S3.SS3.SSS4">
<title>Proposed adaptive context-aware middleware</title>
<p>In <xref ref-type="fig" rid="F6">Figures 6</xref>&#x2013;<xref ref-type="fig" rid="F8">8</xref> and <xref ref-type="table" rid="T1">Table 1</xref> evidence that the proposed adaptive middleware consistently outperforms both static and dynamic systems across all scenarios. It achieves the lowest latency and highest throughput, with very stable performance even as workload increases. The graphs (<xref ref-type="fig" rid="F6">Figures 6</xref>&#x2013;<xref ref-type="fig" rid="F8">8</xref>) show latency maintained at approximately 65&#x2013;85 ms and throughput reaching 290&#x2013;320 ops/sec, indicating strong efficiency and scalability. This shows up to 50% latency reduction compared to static systems and up to 80% improvement in throughput. Unlike the other approaches, the adaptive middleware maintains stability under changing conditions due to real-time context awareness and proactive optimization.</p>
<p>In summary, the combined results show a clear progression in performance from static to dynamic to adaptive middleware. Static middleware performs poorly due to fixed behaviour, dynamic middleware offers partial improvement through reactive adjustments, while the proposed adaptive context-aware middleware consistently achieves superior performance through real-time context awareness and proactive optimization.</p>
<p>Overall, the results confirm that the proposed system delivers superior performance in smart environments by ensuring seamless integration and effective service optimization, demonstrating that adaptive middleware achieves the best balance of low latency, high throughput, and manageable overhead, highlighting its effectiveness for latency-sensitive and high-demand distributed systems.</p>
</sec>
</sec>
</sec>
<sec id="S4" sec-type="discussion">
<title>Discussion</title>
<p>The results show that adaptive middleware outperforms both static and dynamic approaches in latency reduction, throughput, and consistency management. Latency measurements indicate that adaptive mechanisms consistently minimize read/write delays across all scenarios, as context awareness, optimized replica placement, and load-sensitive routing reduce network and processing bottlenecks. Unlike static middleware, which is inflexible, and dynamic middleware, which responds only to limited changes, the adaptive framework proactively adjusts to workload variations, maintaining stable performance even under high demand.</p>
<p>Throughput analysis further highlights the benefits of adaptive middleware. It consistently sustains the highest operations per second across all scenarios, showing that intelligent resource allocation and parallel request handling enhance system capacity. Static middleware shows declining throughput due to poor scalability, while dynamic middleware offers moderate gains but is limited by fixed optimization policies. In contrast, the adaptive framework uses continuous feedback from latency and utilization metrics to maximize operational efficiency.</p>
<p>While adaptive middleware introduces a slight increase in consistency overhead due to synchronization and monitoring, the growth remains modest and manageable. This overhead is a necessary trade-off for ensuring data correctness in distributed environments. Notably, under higher loads, adaptive middleware handles consistency more efficiently than dynamic middleware, as coordinated replica management reduces excessive synchronization costs. Overall, the results show that the proposed framework balances performance and consistency effectively, making it well-suited for latency-sensitive, high-throughput applications such as IoT platforms, edge-cloud systems, and real-time data services.</p>
<p>Evaluation of the proposed adaptive context-aware middleware demonstrates clear performance benefits over static and conventional dynamic approaches. Read latency is reduced by 30%&#x2013;57% through demand-aware replica placement, with moderate improvements in write performance. Throughput also rises by 20%&#x2013;40%, as adaptive resource allocation and distributed processing enable the system to handle variable workloads efficiently.</p>
<p>Although adaptive replication adds a modest 10%&#x2013;15% consistency overhead, this is outweighed by significant improvements in responsiveness and system capacity. The middleware also remains robust under stress conditions, such as network congestion or node failures, maintaining stable latency and throughput. Overall, the results confirm that adaptive context-aware middleware offers a scalable, reliable solution for smart environments, effectively balancing performance, consistency, and resource utilization.</p>
</sec>
<sec id="S5" sec-type="results">
<title>Results</title>
<list list-type="simple">
<list-item>
<label>1.</label>
<p>Latency is highest in static middleware, lower in dynamic middleware, and lowest in adaptive middleware. Adaptive middleware also provides the most stable performance and reduces delay by up to 50%, making it best for latency-sensitive environments.</p>
</list-item>
<list-item>
<label>2.</label>
<p>Throughput improves from static to dynamic and is highest in adaptive middleware. Static middleware has the lowest and declining performance, dynamic shows moderate improvement, while adaptive middleware achieves the best and most stable throughput, improving system capacity by up to 80% under higher workloads.</p>
</list-item>
<list-item>
<label>3.</label>
<p>Consistency overhead increases slightly in adaptive middleware (10%&#x2013;15%) but remains lower and more stable than dynamic middleware (8%&#x2013;18%). This indicates that adaptive mechanisms maintain efficiency while controlling overhead despite workload changes.</p>
</list-item>
</list>
<p>In summary, the results demonstrate that adaptive middleware achieves the best balance of low latency, high throughput, and manageable overhead, highlighting its effectiveness for latency-sensitive and high-demand distributed systems.</p>
</sec>
<sec id="S6" sec-type="conclusion">
<title>Conclusion</title>
<p>This study presented the design, implementation, and evaluation of an adaptive context-aware middleware framework for smart environments. The framework combines real-time context acquisition, intelligent reasoning, and dynamic adaptation to optimize service delivery across heterogeneous devices. By continuously monitoring system and environmental conditions, it adjusts replica placement, resource allocation, and communication strategies to handle changing workloads effectively.</p>
<p>Experimental results show that the adaptive middleware significantly lowers read and write latency, increases throughput, and improves the use of computational and network resources compared to static and traditional dynamic solutions. While it introduces a slight consistency overhead from synchronization and monitoring, this remains modest and is outweighed by the gains in responsiveness and overall efficiency.</p>
<p>The framework also demonstrates strong robustness under network congestion, workload fluctuations, and partial device failures. This resilience makes it suitable for real-world smart environments, such as smart homes, healthcare monitoring systems, and industrial IoT platforms where reliability and low latency are essential. Overall, the study confirms that integrating adaptivity and context-awareness into middleware enhances scalability, efficiency, and user experience, providing a solid foundation for intelligent and responsive smart environment applications.</p>
</sec>
<sec id="S7">
<title>Recommendations</title>
<p>System designers should use adaptive context-aware middleware to enhance latency, throughput, and overall service performance in smart environments. Implementations should prioritize scalability for large-scale IoT deployments and efficient use of computational and network resources. Security and privacy measures must protect sensitive context data, and thorough testing under realistic conditions is essential to ensure reliability and stability.</p>
</sec>
<sec id="S8">
<title>Future work</title>
<p>Future research should investigate incorporating predictive analytics and machine learning to improve adaptive control under dynamic workloads and user behaviour. Expanding the framework to large-scale heterogeneous IoT systems and edge&#x2013;cloud collaboration could further enhance performance and scalability. Additionally, real-world deployments in smart homes, healthcare, and industrial IoT are needed to validate long-term performance, robustness, and usability.</p>
</sec>
</body>
<back>
<sec id="S9" sec-type="funding-information">
<title>Funding</title>
<p>The author declares that no financial support was received for the research, authorship, and/or publication of this article.</p>
</sec>
<sec id="S10">
<title>Conflict of interest</title>
<p>The author declares that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<ref-list>
<title>References</title>
<ref id="B1"><label>1.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ilyas</surname> <given-names>A</given-names></name> <name><surname>Alatawi</surname> <given-names>MN</given-names></name> <name><surname>Hamid</surname> <given-names>Y</given-names></name></person-group>. <article-title>Software architecture for pervasive critical health monitoring system using fog computing.</article-title> <source><italic>J Cloud Comput.</italic></source> (<year>2022</year>) <volume>11</volume>:<fpage>84</fpage>. <pub-id pub-id-type="doi">10.1186/s13677-022-00371-w</pub-id></citation></ref>
<ref id="B2"><label>2.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Li</surname> <given-names>X</given-names></name> <name><surname>Eckert</surname> <given-names>M</given-names></name> <name><surname>Martinez</surname> <given-names>J-F</given-names></name> <name><surname>Rubio</surname> <given-names>G</given-names></name></person-group>. <article-title>Context-aware middleware architectures: survey and challenges.</article-title> <source><italic>Sensors.</italic></source> (<year>2015</year>) <volume>15</volume>(<issue>8</issue>):<fpage>20570</fpage>&#x2013;<lpage>607</lpage>. <pub-id pub-id-type="doi">10.3390/s150820570</pub-id></citation></ref>
<ref id="B3"><label>3.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Fortino</surname> <given-names>G</given-names></name> <name><surname>Guerrieri</surname> <given-names>A</given-names></name> <name><surname>Russo</surname> <given-names>W</given-names></name> <name><surname>Savaglio</surname> <given-names>C</given-names></name> <name><surname>Spezzano</surname> <given-names>G</given-names></name></person-group>. <article-title>Integration of agent-based and IoT systems for smart environments.</article-title> <source><italic>J Comput Syst Sci.</italic></source> (<year>2017</year>) <volume>83</volume>(<issue>1</issue>):<fpage>74</fpage>&#x2013;<lpage>94</lpage>. <pub-id pub-id-type="doi">10.1016/j.jcss.2016.06.002</pub-id></citation></ref>
<ref id="B4"><label>4.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Chen</surname> <given-names>G</given-names></name> <name><surname>Kotz</surname> <given-names>D</given-names></name></person-group>. <article-title>A survey of context-aware mobile computing research.</article-title> <source><italic>Dartmouth College Technical Report.</italic></source> (<year>2000</year>). Available online at: <ext-link ext-link-type="uri" xlink:href="https://citeseerx.ist.psu.edu">https://citeseerx.ist.psu.edu</ext-link>.</citation></ref>
<ref id="B5"><label>5.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Yadav Yanamala</surname> <given-names>AK</given-names></name> <name><surname>Suryadevara</surname> <given-names>S</given-names></name></person-group>. <article-title>Adaptive middleware framework for context-aware pervasive computing environments.</article-title> <source><italic>Int J Mach Learn Res Cybersecur Artif Intel.</italic></source> (<year>2022</year>) <volume>13</volume>(<issue>1</issue>):<fpage>35</fpage>&#x2013;<lpage>57</lpage>.</citation></ref>
<ref id="B6"><label>6.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Shi</surname> <given-names>W</given-names></name> <name><surname>Cao</surname> <given-names>J</given-names></name> <name><surname>Zhang</surname> <given-names>Q</given-names></name> <name><surname>Li</surname> <given-names>Y</given-names></name> <name><surname>Xu</surname> <given-names>L</given-names></name></person-group>. <article-title>Edge computing: vision and challenges.</article-title> <source><italic>IEEE Int Things J.</italic></source> (<year>2016</year>) <volume>3</volume>(<issue>5</issue>):<fpage>637</fpage>&#x2013;<lpage>46</lpage>. <pub-id pub-id-type="doi">10.1109/JIOT.2016.2579198</pub-id></citation></ref>
<ref id="B7"><label>7.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Dey</surname> <given-names>AK</given-names></name></person-group>. <article-title>Understanding and using context.</article-title> <source><italic>Pers Ubiquit Comput.</italic></source> (<year>2001</year>) <volume>5</volume>(<issue>1</issue>):<fpage>4</fpage>&#x2013;<lpage>7</lpage>. <pub-id pub-id-type="doi">10.1007/s007790170019</pub-id></citation></ref>
<ref id="B8"><label>8.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Baumgartner</surname> <given-names>J</given-names></name> <name><surname>Fischer</surname> <given-names>R</given-names></name> <name><surname>Emmanouilidis</surname> <given-names>C</given-names></name></person-group>. <article-title>Context-aware knowledge-based middleware for selective information delivery in data-intensive monitoring systems.</article-title> <source><italic>Eng Appl Artif Intel.</italic></source> (<year>2015</year>) <volume>43</volume>:<fpage>111</fpage>&#x2013;<lpage>26</lpage>. <pub-id pub-id-type="doi">10.1016/j.engappai.2015.04.008</pub-id></citation></ref>
<ref id="B9"><label>9.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Liang</surname> <given-names>G</given-names></name> <name><surname>Cao</surname> <given-names>J</given-names></name></person-group>. <article-title>Social context-aware middleware: a survey.</article-title> <source><italic>Perv Mobile Comput.</italic></source> (<year>2015</year>) <volume>17</volume>:<fpage>207</fpage>&#x2013;<lpage>19</lpage>. <pub-id pub-id-type="doi">10.1016/j.pmcj.2014.12.003</pub-id></citation></ref>
<ref id="B10"><label>10.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Elkhodr</surname> <given-names>M</given-names></name> <name><surname>Khan</surname> <given-names>S</given-names></name> <name><surname>Gide</surname> <given-names>E</given-names></name></person-group>. <article-title>A novel semantic IoT middleware for secure data management: blockchain and AI-driven context awareness.</article-title> <source><italic>Future Internet.</italic></source> (<year>2024</year>) <volume>16</volume>(<issue>1</issue>):<fpage>22</fpage>. <pub-id pub-id-type="doi">10.3390/fi16010022</pub-id></citation></ref>
<ref id="B11"><label>11.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Roman</surname> <given-names>R</given-names></name> <name><surname>Lopez</surname> <given-names>J</given-names></name> <name><surname>Mambo</surname> <given-names>M</given-names></name></person-group>. <article-title>Mobile edge computing, fog et al.: a survey and analysis of security threats and challenges.</article-title> <source><italic>Future Gen Comput Syst.</italic></source> (<year>2018</year>) <volume>78</volume>:<fpage>680</fpage>&#x2013;<lpage>98</lpage>. <pub-id pub-id-type="doi">10.1016/j.future.2016.11.009</pub-id></citation></ref>
<ref id="B12"><label>12.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Satyanarayanan</surname> <given-names>M</given-names></name></person-group>. <article-title>The emergence of edge computing.</article-title> <source><italic>Computer.</italic></source> (<year>2017</year>) <volume>50</volume>(<issue>1</issue>):<fpage>30</fpage>&#x2013;<lpage>9</lpage>. <pub-id pub-id-type="doi">10.1109/MC.2017.9</pub-id></citation></ref>
<ref id="B13"><label>13.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zhang</surname> <given-names>Y</given-names></name> <name><surname>Qiu</surname> <given-names>M</given-names></name> <name><surname>Tsai</surname> <given-names>CW</given-names></name> <name><surname>Hassan</surname> <given-names>MM</given-names></name> <name><surname>Alamri</surname> <given-names>A</given-names></name></person-group>. <article-title>Health-CPS: healthcare cyber-physical system assisted by cloud and big data.</article-title> <source><italic>IEEE Syst J.</italic></source> (<year>2015</year>) <volume>11</volume>(<issue>1</issue>):<fpage>88</fpage>&#x2013;<lpage>95</lpage>. <pub-id pub-id-type="doi">10.1109/JSYST.2015.2460747</pub-id></citation></ref>
<ref id="B14"><label>14.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Gubbi</surname> <given-names>J</given-names></name> <name><surname>Buyya</surname> <given-names>R</given-names></name> <name><surname>Marusic</surname> <given-names>S</given-names></name> <name><surname>Palaniswami</surname> <given-names>M</given-names></name></person-group>. <article-title>Internet of Things (IoT): a vision, architectural elements, and future directions.</article-title> <source><italic>Future Gen Comput Syst.</italic></source> (<year>2013</year>) <volume>29</volume>(<issue>7</issue>):<fpage>1645</fpage>&#x2013;<lpage>60</lpage>. <pub-id pub-id-type="doi">10.1016/j.future.2013.01.010</pub-id></citation></ref>
<ref id="B15"><label>15.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Do</surname> <given-names>LT</given-names></name> <name><surname>Nguyen</surname> <given-names>QT</given-names></name> <name><surname>Kim</surname> <given-names>DS</given-names></name></person-group>. <article-title>A holistic approach to a context-aware IoT ecosystem with adaptive ubiquitous middleware.</article-title> <source><italic>Perv Mobile Comput.</italic></source> (<year>2021</year>) <volume>72</volume>:<fpage>101342</fpage>. <pub-id pub-id-type="doi">10.1016/j.pmcj.2021.101342</pub-id></citation></ref>
<ref id="B16"><label>16.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Perera</surname> <given-names>C</given-names></name> <name><surname>Zaslavsky</surname> <given-names>A</given-names></name> <name><surname>Christen</surname> <given-names>P</given-names></name> <name><surname>Georgakopoulos</surname> <given-names>D</given-names></name></person-group>. <article-title>Context-aware computing in Internet of Things: a survey.</article-title> <source><italic>IEEE Commun Surv Tutor.</italic></source> (<year>2014</year>) <volume>16</volume>(<issue>1</issue>):<fpage>414</fpage>&#x2013;<lpage>54</lpage>. <pub-id pub-id-type="doi">10.1109/SURV.2013.050813.00197</pub-id></citation></ref>
<ref id="B17"><label>17.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Gu</surname> <given-names>T</given-names></name> <name><surname>Wang</surname> <given-names>XH</given-names></name> <name><surname>Pung</surname> <given-names>HK</given-names></name> <name><surname>Zhang</surname> <given-names>DQ</given-names></name></person-group>. <article-title>An ontology-based context model in intelligent environments.</article-title> <source><italic>PerCom Workshops.</italic></source> (<year>2004</year>). Available online at: <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/2003.05055">https://arxiv.org/abs/2003.05055</ext-link>.</citation></ref>
<ref id="B18"><label>18.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zanella</surname> <given-names>A</given-names></name> <name><surname>Bui</surname> <given-names>N</given-names></name> <name><surname>Castellani</surname> <given-names>A</given-names></name> <name><surname>Vangelista</surname> <given-names>L</given-names></name> <name><surname>Zorzi</surname> <given-names>M</given-names></name></person-group>. <article-title>Internet of Things for smart cities.</article-title> <source><italic>IEEE Inter Things J.</italic></source> (<year>2014</year>) <volume>1</volume>(<issue>1</issue>):<fpage>22</fpage>&#x2013;<lpage>32</lpage>. <pub-id pub-id-type="doi">10.1109/JIOT.2014.2306328</pub-id></citation></ref>
<ref id="B19"><label>19.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Miorandi</surname> <given-names>D</given-names></name> <name><surname>Sicari</surname> <given-names>S</given-names></name> <name><surname>De Pellegrini</surname> <given-names>F</given-names></name> <name><surname>Chlamtac</surname> <given-names>I</given-names></name></person-group>. <article-title>Internet of things: vision, applications and research challenges.</article-title> <source><italic>Ad Hoc Netw.</italic></source> (<year>2012</year>) <volume>10</volume>(<issue>7</issue>):<fpage>1497</fpage>&#x2013;<lpage>516</lpage>. <pub-id pub-id-type="doi">10.1016/j.adhoc.2012.02.016</pub-id></citation></ref>
<ref id="B20"><label>20.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ben Sada</surname> <given-names>A</given-names></name> <name><surname>Ning</surname> <given-names>H</given-names></name> <name><surname>Naouri</surname> <given-names>A</given-names></name> <name><surname>Dhelim</surname> <given-names>S</given-names></name></person-group>. <article-title>Context-aware service recommendation system for the Social Internet of Things</article-title>. <source><italic>Int Things</italic></source>. (<year>2023</year>) <volume>23</volume>:<fpage>100843</fpage>.</citation></ref>
<ref id="B21"><label>21.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Baz&#x00E1;n Mu&#x00F1;oz</surname> <given-names>A</given-names></name> <name><surname>Ortiz Bellot</surname> <given-names>G</given-names></name> <name><surname>Augusto</surname> <given-names>JC</given-names></name></person-group>. <article-title>Taxonomy and software architecture for real-time context-aware collaborative smart environments.</article-title> <source><italic>Inter Things.</italic></source> (<year>2024</year>) <volume>26</volume>:<fpage>101160</fpage>. <pub-id pub-id-type="doi">10.1016/j.iot.2024.101160</pub-id></citation></ref>
<ref id="B22"><label>22.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>De Brouwer</surname> <given-names>M</given-names></name> <name><surname>Steenwinckel</surname> <given-names>B</given-names></name> <name><surname>De Turck</surname> <given-names>F</given-names></name></person-group>. <article-title>Context-aware query derivation for IoT data streams with DIVIDE enabling privacy by design.</article-title> <source><italic>Semantic Web.</italic></source> (<year>2023</year>) <volume>14</volume>(<issue>5</issue>):<fpage>893</fpage>&#x2013;<lpage>941</lpage>. <pub-id pub-id-type="doi">10.3233/SW-223281</pub-id></citation></ref>
<ref id="B23"><label>23.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Hossain</surname> <given-names>MS</given-names></name> <name><surname>Muhammad</surname> <given-names>G</given-names></name></person-group>. <article-title>Cloud-assisted industrial Internet of Things-enabled framework for health monitoring.</article-title> <source><italic>Future Gen Comput Syst.</italic></source> (<year>2016</year>) <volume>61</volume>:<fpage>1</fpage>&#x2013;<lpage>11</lpage>. <pub-id pub-id-type="doi">10.1016/j.future.2016.01.008</pub-id></citation></ref>
<ref id="B24"><label>24.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ni</surname> <given-names>H</given-names></name> <name><surname>Abdulrazak</surname> <given-names>B</given-names></name> <name><surname>Zhang</surname> <given-names>D</given-names></name> <name><surname>Wu</surname> <given-names>S</given-names></name></person-group>. <article-title>CDTOM: context-driven task-oriented middleware for pervasive homecare environment.</article-title> <source><italic>arXiv preprint.</italic></source> (<year>2011</year>). Available online at: <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/1102.1152">https://arxiv.org/abs/1102.1152</ext-link></citation></ref>
<ref id="B25"><label>25.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Weerasinghe</surname> <given-names>S</given-names></name> <name><surname>Zaslavsky</surname> <given-names>A</given-names></name> <name><surname>Loke</surname> <given-names>SW</given-names></name> <name><surname>Hassani</surname> <given-names>A</given-names></name> <name><surname>Medvedev</surname> <given-names>A</given-names></name> <name><surname>Abken</surname> <given-names>A</given-names></name></person-group>. <article-title>Adaptive context caching for IoT-based applications: a reinforcement learning approach.</article-title> <source><italic>Sensors.</italic></source> (<year>2023</year>) <volume>23</volume>(<issue>10</issue>):<fpage>4767</fpage>. <pub-id pub-id-type="doi">10.3390/s23104767</pub-id></citation></ref>
<ref id="B26"><label>26.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Baccarelli</surname> <given-names>E</given-names></name> <name><surname>Cordeschi</surname> <given-names>N</given-names></name> <name><surname>Mei</surname> <given-names>A</given-names></name> <name><surname>Panella</surname> <given-names>M</given-names></name></person-group>. <article-title>Energy-efficient dynamic resource allocation for distributed cloud-based IoT systems.</article-title> <source><italic>Future Gen Comput Syst.</italic></source> (<year>2017</year>) <volume>73</volume>:<fpage>131</fpage>&#x2013;<lpage>45</lpage>. <pub-id pub-id-type="doi">10.1016/j.future.2017.02.014</pub-id></citation></ref>
<ref id="B27"><label>27.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Pliatsios</surname> <given-names>A</given-names></name> <name><surname>Lymperis</surname> <given-names>D</given-names></name> <name><surname>Goumopoulos</surname> <given-names>C</given-names></name></person-group>. <article-title>S2NetM: a semantic social network of things middleware for developing smart and collaborative IoT-based solutions</article-title>. <source><italic>Fut Int</italic></source>. (<year>2023</year>) <volume>15</volume>(<issue>6</issue>):<fpage>207</fpage>. <pub-id pub-id-type="doi">10.3390/fi15060207</pub-id></citation></ref>
<ref id="B28"><label>28.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bettini</surname> <given-names>C</given-names></name> <name><surname>Brdiczka</surname> <given-names>O</given-names></name> <name><surname>Henricksen</surname> <given-names>K</given-names></name> <name><surname>Indulska</surname> <given-names>J</given-names></name> <name><surname>Nicklas</surname> <given-names>D</given-names></name> <name><surname>Ranganathan</surname> <given-names>A</given-names></name> <etal/> </person-group> <article-title>A survey of context modelling and reasoning techniques for pervasive and mobile computing.</article-title> <source><italic>Perv Mobile Comput.</italic></source> (<year>2010</year>) <volume>6</volume>(<issue>2</issue>):<fpage>161</fpage>&#x2013;<lpage>80</lpage>. <pub-id pub-id-type="doi">10.1016/j.pmcj.2009.06.002</pub-id></citation></ref>
<ref id="B29"><label>29.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Inshi</surname> <given-names>S</given-names></name> <name><surname>Chowdhury</surname> <given-names>R</given-names></name> <name><surname>Ould-Slimane</surname> <given-names>H</given-names></name> <name><surname>Talhi</surname> <given-names>C</given-names></name></person-group>. <article-title>Secure adaptive context-aware ABE for smart environments</article-title>. <source><italic>IoT</italic></source>. (<year>2023</year>) <volume>4</volume>(<issue>2</issue>):<fpage>112</fpage>&#x2013;<lpage>30</lpage>. <pub-id pub-id-type="doi">10.3390/iot4020007</pub-id></citation></ref>
<ref id="B30"><label>30.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kalaria</surname> <given-names>R</given-names></name> <name><surname>Kayes</surname> <given-names>ASM</given-names></name> <name><surname>Rahayu</surname> <given-names>W</given-names></name> <name><surname>Pardede</surname> <given-names>E</given-names></name> <name><surname>Shahraki</surname> <given-names>AS</given-names></name></person-group>. <article-title>Adaptive context-aware access control for IoT environments leveraging fog computing.</article-title> <source><italic>Int J Inform Secur.</italic></source> (<year>2024</year>) <volume>23</volume>:<fpage>3089</fpage>&#x2013;<lpage>107</lpage>. <pub-id pub-id-type="doi">10.1007/s10207-024-00866-4</pub-id></citation></ref>
<ref id="B31"><label>31.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Michalakis</surname> <given-names>K</given-names></name> <name><surname>Christodoulou</surname> <given-names>Y</given-names></name> <name><surname>Caridakis</surname> <given-names>G</given-names></name> <name><surname>Voutos</surname> <given-names>Y</given-names></name> <name><surname>Mylonas</surname> <given-names>P</given-names></name></person-group>. <article-title>A context-aware middleware for smart cultural spaces.</article-title> <source><italic>Appl Sci.</italic></source> (<year>2021</year>) <volume>11</volume>(<issue>13</issue>):<fpage>5770</fpage>. <pub-id pub-id-type="doi">10.3390/app11135770</pub-id></citation></ref>
</ref-list>
</back>
</article>
