Project

General

Profile

Wiki » History » Version 27

Lan Wang, 11/24/2025 12:01 AM

1 1 Suravi Regmi
# MGuard: A Secure mHealth Infrastructure for Real-Time Data transfer with Fine-grained Access Control over NDN
2
3
4 15 Lan Wang
**MGuard** is an NDN-based system designed to support high-frequency mHealth data sharing with **fine-grained contextual access control** and **real-time data distribution**.  It is built on name-based access control (NAC/NAC-ABE) and PSync to enable timely access to sensitive mobile health data.
5 1 Suravi Regmi
6
---
7
8
## Purpose
9
MGuard addresses two core challenges in mHealth data sharing:
10
11
1. **Access to privacy-sensitive data is limited to authorized users based on well defined polcies**  
12
13
2. **Supporting real-time sharing of high-frequency sensor data**  
14
15
---
16
17
## Core Components
18
19
### **Producer**
20
21 26 Lan Wang
- converts raw or derived data streams into NDN-named data objects,
22
- associates each object with appropriate attributes,
23
- stores encrypted data into the NDN repository,
24
- notifies subscribers when new data is available (via published manifest names).
25 19 Lan Wang
26 27 Lan Wang
### **Controller** has two compnents:
27 22 Lan Wang
28 25 Lan Wang
Policy Manager 
29 22 Lan Wang
30 1 Suravi Regmi
- defines **who** can access **which** data streams,  
31
- parses and manages access control policies, and  
32
- collaborates with the Attribute Authority to issue decryption keys (DKEYs) to validated data requesters.
33
34 23 Lan Wang
Attribute Authority (AA)  
35
36 1 Suravi Regmi
- validates requester identities (using the system’s trust anchor),
37
- issues policy-compliant decryption keys based on KP-ABE, and  
38 23 Lan Wang
- publishes public parameters required for encryption.
39 1 Suravi Regmi
40
### **Consumer**
41
Subscribes to mHealth data streams according to the access rights defined for the requester.  
42
The consumer:
43
- receives notifications for new manifests,  
44
- fetches the corresponding encrypted data objects from the repository, and  
45
- decrypts data based on issued keys and permitted attributes.  
46
47
### **Repository**
48
Persistent storage for all published mHealth data objects, content keys, and manifests.  
49
The repository allows consumers to:
50
- retrieve data independently of the producer,  
51
- fetch CKs needed for decryption, and  
52
- access previously published (historical) data.  
53
54
---
55
56
## Navigation
57 8 Suravi Regmi
58 1 Suravi Regmi
- **[[Architecture]]**
59 8 Suravi Regmi
  - **[[Architecture_Details|Architecture Details]]**
60
- **[[Design_Elements|Design Elements]]**
61
  - **[[Naming_Scheme|Naming Scheme]]**
62
  - **[[Trust_Model|Trust Model]]**
63
  - **[[Access_Control|Access Control]]**
64
  - **[[NAC-ABE_Design|NAC-ABE Design]]**
65
  - **[[Manifest_Design|Manifest Design]]**
66
  - **[[PSync_Design|PSync Design]]**
67 12 Suravi Regmi
  - **[[Pub-Sub API|Pub-Sub API Design]]**
68 13 Suravi Regmi
  - **[[Repo|Repo Design]]**
69 8 Suravi Regmi
- **[[Developer_Guide|Developer Guide]]**
70 11 Suravi Regmi
- [Open editable Figma diagram](https://www.figma.com/design/I2SLqGN17XJHh8KsyAJ88l/Untitled?node-id=0-1&t=xWqhvwrDlUOlkeVU-1)