| Literature DB >> 36091662 |
Ashish Singh1, Kakali Chatterjee2.
Abstract
Nowadays, Smart Healthcare Systems (SHS) are frequently used by people for personal healthcare observations using various smart devices. The SHS uses IoT technology and cloud infrastructure for data capturing, transmitting it through smart devices, data storage, processing, and healthcare advice. Processing such a huge amount of data from numerous IoT devices in a short time is quite challenging. Thus, technological frameworks such as edge computing or fog computing can be used as a middle layer between cloud and user in SHS. It reduces the response time for data processing at the lower level (edge level). But, Edge of Things (EoT) also suffers from security and privacy issues. A robust healthcare monitoring framework with secure data storage and access is needed. It will provide a quick response in case of the production of abnormal data and store/access the sensitive data securely. This paper proposed a Secure Framework based on the Edge of Things (SEoT) for Smart healthcare systems. This framework is mainly designed for real-time health monitoring, maintaining the security and confidentiality of the healthcare data in a controlled manner. This paper included clustering approaches for analyzing bio-signal data for abnormality detection and Attribute-Based Encryption (ABE) for bio-signal data security and secure access. The experimental results of the proposed framework show improved performance with maintaining the accuracy of up to 98.5% and data security.Entities:
Keywords: Attribute-based encryption; Clustering; Data security and privacy; Edge computing; Electronic healthcare system; SEoT; Secure health monitoring
Year: 2022 PMID: 36091662 PMCID: PMC9438893 DOI: 10.1007/s10586-022-03717-w
Source DB: PubMed Journal: Cluster Comput ISSN: 1386-7857 Impact factor: 2.303
Fig. 1Proposed edge computing based secure health monitoring framework
Index table () for attribute generation
| Domain | Attribute | Attribute ID | Label | Codeword |
|---|---|---|---|---|
| Diagnosis | LID 01 RID 01 | 1 | 011 ( | |
| Treatment | LID 00 RID 00 | 1 | 001 ( | |
| Symptoms | LID 011 RID 011 | 2 | 0100 ( | |
| Test report | LID 010 RID 010 | 2 | 0110 ( | |
| Therapy | LID 000 RID 000 | 2 | 0000 ( | |
| Surgery | LID 001 RID 001 | 2 | 0010 ( |
Index table () for master key generation
| Domain | Label | Codeword | Key location | Generated key |
|---|---|---|---|---|
|
| 1 | 3 | 21 | |
|
| 1 | 4 | 22 | |
|
| 2 | 5 | 31 | |
|
| 2 | 6 | 32 | |
|
| 2 | 7 | 41 | |
|
| 2 | 8 | 42 | |
|
| 3 | 9 | 51 | |
|
| 3 | 10 | 52 | |
|
| 3 | 11 | 61 | |
|
| 3 | 12 | 62 |
Search key generation table ()
| Keyword (attribute name) | DOC_id | Encrypted index | Search token |
|---|---|---|---|
| ATTR_NM | |||
| ATTR_NM | |||
| ATTR_NM | |||
| ATTR_NM |
Fig. 2Attribute tree
Fig. 3Policy tree for proposed model
Fig. 4Statistic values while selecting the first attribute of subject 4
Fig. 5Statistic values while selecting the second attribute of subject 4
Fig. 6Statistic values of all attributes of subject 4
Fig. 7Clustering result of subject 4
Fig. 8Clustering accuracy of the proposed SEoT health monitoring framework
Training, validation, and testing accuracy results of different detection strategies
| Dataset length | Algorithm | Data points | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000 | 3000 | 5000 | 8000 | ||||||||||
| Train | Valid | Test | Train | Valid | Test | Train | Valid | Test | Train | Valid | Test | ||
| 50% | 98.35 | 98.28 | 98.37 | 98.17 | 98.16 | 98.08 | 99.67 | 99.68 | 99.69 | 98.59 | 98.58 | 98.43 | |
| 98.33 | 98.38 | 98.48 | 98.25 | 98.26 | 98.27 | 98.57 | 98.47 | 98.66 | 98.44 | 98.38 | 98.59 | ||
| 98.23 | 98.35 | 98.46 | 97.16 | 97.18 | 97.19 | 97.11 | 97.12 | 97.13 | 98.46 | 98.29 | 98.36 | ||
| 98.16 | 98.25 | 98.16 | 97.88 | 97.82 | 97.82 | 97.31 | 97.33 | 97.34 | 98.51 | 98.33 | 98.33 | ||
| 75% | 95.81 | 95.62 | 95.73 | 97.84 | 95.58 | 97.67 | 97.84 | 97.85 | 97.86 | 98.55 | 98.84 | 98.78 | |
| 97.02 | 97.01 | 97.12 | 97.18 | 98.02 | 98.01 | 97.04 | 97.03 | 97.04 | 98.73 | 98.66 | 97.52 | ||
| 97.62 | 97.41 | 97.35 | 97.12 | 97.13 | 97.13 | 97.88 | 97.89 | 97.90 | 98.44 | 98.42 | 98.40 | ||
| 96.88 | 96.45 | 96.89 | 97.85 | 97.86 | 97.87 | 97.91 | 97.92 | 97.93 | 98.52 | 98.50 | 98.48 | ||
| 100% | 91.31 | 91.11 | 91.19 | 98.82 | 98.80 | 98.81 | 97.11 | 97.15 | 97.17 | 98.43 | 98.42 | 98.44 | |
| 98.71 | 98.67 | 98.88 | 98.22 | 98.23 | 98.24 | 97.16 | 97.18 | 97.20 | 98.31 | 98.16 | 98.18 | ||
| 98.29 | 91.11 | 91.79 | 97.11 | 97.02 | 97.00 | 97.17 | 97.18 | 97.19 | 98.11 | 98.03 | 98.05 | ||
| 91.89 | 90.82 | 91.71 | 98.01 | 98.02 | 98.03 | 97.87 | 97.89 | 97.91 | 98.21 | 98.12 | 98.12 | ||
Description of performance metrics
| Test metric [ | Definition | Equation |
|---|---|---|
| Accuracy ( | Computed by dividing all classes’ correct identification by the dataset’s total data points. | Accuracy ( |
| Precision ( | Computed by dividing the value of (T+) by the total of (T+) and (F+). | Precision ( |
| Recall ( | Percentage of (T+) divided by the total of (T+) and (F-). | Recall ( |
| F-Score ( | Precision and Recall harmonic mean is defined as F-score. | F-Score = 2 * |
| False Positive Rate ( | Computed as the total number of (F+) divided by the sum of (T+) and (T-). | |
| Area Under Curve ( | It is the trade-off between misclassification rate and | |
| True Positive Rate ( | The total data points identified as normal while they were actually normal. | |
| True Negative Rate ( | The total data points identified as abnormal while they were actual abnormal. | |
| False Positive Rate ( | The total data points identified as normal while they were actual abnormal. | |
| False Negative Rate ( | The total data points identified as abnormal while they were actually normal. | |
Performance summary of our proposed SEoT health monitoring framework
| Data points | Algorithms | ||||||
|---|---|---|---|---|---|---|---|
| 1000 | KMC | 88.89 | 84.21 | 86.49 | 93.75 | 0.03 | 85.97 |
| FNN | 82.35 | 82.35 | 82.35 | 92.5 | 0.04 | 78.43 | |
| ANN | 84.62 | 88.00 | 86.27 | 91.25 | 0.05 | 78.46 | |
| KMNN | 94.74 | 94.74 | 94.74 | 97.5 | 0.01 | 93.18 | |
| 3000 | KMC | 83.72 | 75.79 | 79.56 | 90.75 | 0.04 | 79.88 |
| FNN | 94.94 | 75.76 | 84.27 | 93 | 0.01 | 93.68 | |
| ANN | 90.32 | 73.68 | 81.16 | 93.5 | 0.02 | 88.65 | |
| KMNN | 93.06 | 94.37 | 93.71 | 97.75 | 0.01 | 91.64 | |
| 5000 | KMC | 82.35 | 89.74 | 85.89 | 94.25 | 0.04 | 78.52 |
| FNN | 93.67 | 82.22 | 87.57 | 94.75 | 0.01 | 92.16 | |
| ANN | 90.00 | 86.30 | 88.11 | 95.75 | 0.02 | 88.07 | |
| KMNN | 95.95 | 93.42 | 94.67 | 98 | 0.01 | 95.06 | |
| 8000 | KMC | 91.11 | 86.32 | 88.65 | 94.75 | 0.02 | 88.72 |
| FNN | 90.14 | 87.67 | 88.89 | 96 | 0.02 | 88.21 | |
| ANN | 91.55 | 90.28 | 90.91 | 96.75 | 0.02 | 89.87 | |
| KMNN | 96.00 | 96.00 | 96.00 | 98.5 | 0.01 | 95.11 |
Fig. 9Required time to perform the operations with respect to the number of users
Fig. 10Required time to perform the operations with respect to data size