mGuard

# Producer Architecure

#

## Overview

The producer ingests data, converts it into NDN-named packets, attaches attributes, applies NAC-ABE encryption, and publishes encrypted data, CKs, and manifests to the NDN network. It loads configuration, certificates, ABE parameters, and stream settings at startup and then runs continuously as the system’s data source.

---

## Configuration Inputs

- **producerPrefix** – NDN identity for naming and signing packets  

- **aaPrefix** – Prefix where AA publishes ABE parameters  

- **dbName** – Lookup database for semantic-location attributes  

- **producerCertPath** – Certificate for signing outgoing data  

- **aaCertPath** – Certificate for validating AA material  

- **trustSchemaPath** – Producer’s trust schema  

- **attributeMappingFilePath** – Maps streams to attribute rules  

- **granularity** – CK rotation granularity (sec/min/hr)  

- **streams** – Stream prefixes + per-stream certificates  

- **port** – port that Reciever listens to get the data

---

### 1. DataAdapter

A Receiver listens on port **15000**. Data arrives either from the data-generator or from pre-generated file insertion.

Each incoming JSON payload provides:  **streamName** , **metaData**, **streamContent** CSV payload containing all rows. DataAdapter converts the logical name into an NDN-style stream prefix and begins processing.

When the **semantic-location** stream arrives, its rows are inserted into the lookup DB. to generate timestamp-based attributes for all other streams.

Metadata is published once per stream.

Each Data Row is then made into NDN Names with its attribute list. Each data row is then sent to the Publisher as `<name, rawRow, attributeList>`.