## 4 Use Case Study: [PERSON]'s Healthcare Monitoring
### Scenario Overview
While generally fast, this process's speed can vary based on the complexity of the data and the efficiency of the annotation algorithms. * **Encryption and Security:** Encrypting data and ensuring their security is paramount, especially in healthcare applications. The process of encryption and any associated security checks (like verifying digital signatures or interfacing with a blockchain) can introduce delays. The specific amount of time taken can depend on the encryption algorithm's efficiency and the underlying hardware. * **Blockchain Transaction:** Interacting with a blockchain can introduce variable delays. Typical blockchain transactions may take from several seconds to minutes depending on the network's current load, the consensus mechanism in place, and the specific blockchain configuration. For SIM, this step is crucial for ensuring data integrity and auditability but is also one of the most significant sources of latency. * **Smart Contract Execution:** Executing smart contracts involves running code on the blockchain, which can vary in execution time based on the contract's complexity and the current state of the blockchain network. * **AI Feedback and Analysis:** The AI-driven feedback and analysis module, while providing valuable adaptability and learning capabilities, can also introduce computational delays. The extent depends on the amount of data processed and the efficiency of the implementation. Figure 12: Combined visualisation of annotation categorisation before and after AI feedback. The blue bars represent the initial annotations, and the orange bars show the updated annotations following feedback, demonstrating the system’s adaptability to incorporate user-provided exercise context. While this proof of concept abstracts many of these details, it is important to consider these factors in a real-world implementation. Optimising each step to reduce latency without compromising functionality or security is crucial for the success of middleware solutions like SIM. Future work will involve empirical testing and optimisation of these components to meet the stringent performance requirements of healthcare and IoT applications. The full project, including all the source code and visualisations, is available on GitHub for further exploration and contribution by the research community. The repository can be accessed at [[https://github.com/[PERSON]/SIM.git](https://github.com/[PERSON]/SIM.git)]([https://github.com/[PERSON]/SIM.git](https://github.com/[PERSON]/SIM.git)) accessed on 1 January 2024. ## 6 Comparing the Semantic IoT Middleware with other Middleware Approaches

In this section, we conduct a theoretical comparative analysis of SIM against traditional IoT middleware, cloud-centric middleware, and edge-centric middleware. This analysis uses key metrics crucial for evaluating IoT systems' performance and adaptability, such as computational cost, scalability, semantic capabilities, data integrity, decentralization, and user control. The comparison, illustrated in Table 4, offers a comprehensive view of the strengths and weaknesses of each approach. The assessments presented in Table 4 are based on a theoretical framework that considers the inherent design and feature set of SIM as compared to existing middleware approaches. This comparison offers a broad view of the relative strengths and weaknesses of each middleware type, with the following justifications for the anticipated performance metrics:

* Computational Cost: SIM's expected low computational cost is based on its efficient data handling and processing algorithms, which are designed to minimise resource usage. In contrast, traditional and edge-centric middleware may have moderate costs due to less optimised data processing. * Scalability: High scalability of SIM is anticipated due to its decentralised architecture and blockchain integration, which are inherently scalable. Cloud-centric middleware also scores high in scalability due to its cloud-based nature.