Remove Purdue attributions and pipeline references from docs

Name Mashroor Hasan Bhuiyan (UT Dallas) as owner in README and TERMS, drop
pipeline/code-repo references from collection docs, refresh MANIFEST hashes
and rebuild the collection tarballs with the cleaned docs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

README.md

@@ -19,7 +19,7 @@ size_categories:
 
 # POWDER and local-testbed cellular network data for OTel 2.5
 
-Operational cellular-network records collected by the UT Dallas / Purdue team for the OTel 2.5 training effort:
+Operational cellular-network records collected by the UT Dallas 5G lab for the OTel 2.5 training effort:
 the data classes the OTel 2.0 model card lists as absent from its training mix (event data, network-performance
 KPIs, RF/signal-quality measurements, 5G core control-plane and inter-NF signalling).
 
@@ -31,6 +31,7 @@ run records, summaries and documentation:
 | `powder-lte-v1` | 63 LTE runs on the POWDER testbed (srsRAN_4G), benign vs. fake base station: S1AP/NAS/RRC events, MAC byte counts, EPC measurement reports (RSRP/RSRQ/SINR), eNB/UE log events, frame-level malicious labels, detector outputs (kept separate), run records, derived summaries | measured, real radios |
 | `powder-5g-core-sim-v1` | 7 standalone-5G runs on POWDER (Open5GS 2.8.0 + UERANSIM): NGAP, 5G NAS, SBI, PFCP, GTP-U counters, NF logs, RADIUS, injected NF restarts and link impairment with ground-truth timelines | real core software, simulated radio |
 | `zmq-5g-core-sim-v1` | 87 local runs (Open5GS 2.7.7 + ocudu gNB + srsUE over ZMQ): NGAP, 5G NAS, NR RRC, SBI, PFCP, GTP-U/MAC-NR counters, gNB scheduler metrics, per-second UE radio metrics (RSRP, SNR, MCS, BLER, bitrates), iperf/ping/HTTP results, NF restarts/outages, scheduler MCS caps, TCP/UDP load, ground-truth timelines | real core/gNB/UE software, simulated radio |
+| `ota-5g-b210-v1` | 19 local over-the-air runs (two USRP B210s, Open5GS + ocudu gNB + srsUE, band 3, 10 MHz): NGAP, SBI, PFCP, 5G NAS, NR RRC, per-UE scheduler radio metrics (CQI/MCS/BLER/SNR/TA), iperf/ping/HTTP, NF restarts and real link losses with ground-truth timelines, plus judge-checked OTel SFT rows per category | measured, real (uncalibrated) radio link |
 
 ## Record format
 
@@ -57,7 +58,8 @@ powder-5g-core-sim-v1/      README.md, MANIFEST.csv, TERMS.md, run_records/, sum
 powder-5g-core-sim-v1.tar.gz
 zmq-5g-core-sim-v1/         same, plus runs/<run>/ran/metrics (UE metrics CSV)
 zmq-5g-core-sim-v1.tar.gz
+ota-5g-b210-v1/             README.md, MANIFEST.csv, TERMS.md, run_records/, docs/, sft/<category>/ (rows, review, chunks)
+ota-5g-b210-v1.tar.gz      full collection incl. processed/ NDJSON and runs/
 ```
 
-Owner: Mashroor Hasan Bhuiyan (UT Dallas). Collection and tooling: SysNetS Lab; pipeline at
-`github.com/mahabhu/otel-data-collection`.
+Owner: Mashroor Hasan Bhuiyan (UT Dallas). Collection and tooling: SysNetS Lab

TERMS.md

@@ -1,6 +1,6 @@
 # Terms (placeholder)
 
-Collected by the UT Dallas / Purdue POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
-contributors until the owner (Kazi Samin Mubasshir, Purdue) states redistribution terms. Subscriber and
+Collected by the UT Dallas 5G lab POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
+contributors until the owner (Mashroor Hasan Bhuiyan, UT Dallas) states redistribution terms. Subscriber and
 device identifiers are keyed pseudonyms; no raw IMSI/SUPI/IMEI or key material is included. Third-party
 material (Polaris operator captures and drive tests) is deliberately not part of this collection.

powder-5g-core-sim-v1.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3d6b4c3707e50de38b4b0d07eae30dccd2957374d851d8c2dba8078c0fea1590
-size 674506
+oid sha256:fceacbedfdaf85842463fc53b74f0f5ef02c31ae81dbd083e1f2e42d5e91c3be
+size 674269

powder-5g-core-sim-v1.tar.gz.sha256

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:96c64566729bbab65888844cb10181a06bc5adfe6fc30d4068b9f6cf6eeec5ab
+oid sha256:42a5882b007a9334e1968abed38ffbc0edc66b58838cfdcf89b9c52afe68438c
 size 95

powder-5g-core-sim-v1/MANIFEST.csv

@@ -1,9 +1,9 @@
 path,bytes,sha256
-README.md,1572,e1a822ef6325f9f9fbe6e59c76a6638fb18d6e9daf23237997b4e34add620454
-TERMS.md,434,44d84945b2580e7cbd0bef7b20302973085efacc9860a57ab39158da01d3e6e0
-docs/DEPLOYMENT.md,6983,74c47afbccbfa631f5b05be27d449a52fa230b9754f3c8999245455767e96e02
-docs/data_dictionary.md,13945,5f9947261259ebd75f66f315d29bc77f20830599af0c71b3d8c1cc4468ccf809
-docs/event.schema.json,3359,8854948b0ae9616f00b4823b77cc82e73fc2772038007d58004600e76476feb0
+README.md,1533,82bccfc1063feaff6ed6176b7768a8c03a6fa67c1e100f105fe970a500a43343
+TERMS.md,437,0a9370c7fef3552790f91ec022b6fc03a7a6da1e3a58f355d73ba06df5d58ef0
+docs/DEPLOYMENT.md,6504,f79d90e68e727d57a05ccb585ba76d4c0d9ff282d81c5c0767bd4d7275e7d8b2
+docs/data_dictionary.md,13796,e830dfc50ccbe90b2a63b6e1fb354373e2eff8e32156cba964425d0ece4efd2d
+docs/event.schema.json,3349,426e65e48edcad531b94e118aa36e38525030c77360c662ff6257d9718efb28e
 processed/2026-09-30T0919Z_core-sim_baseline_first/core.ngap_events.n2_ngap.ndjson,39593,b117bdb10e3d11073addb2f771bf4ee28b13da63cde7de4c2e35321a6d756480
 processed/2026-09-30T0919Z_core-sim_baseline_first/core.open5gs_log.amf.ndjson,60308,0091808c870fed85f8884f4fe46af9e37c5cfcf044ce869347ebfc5b49b272bc
 processed/2026-09-30T0919Z_core-sim_baseline_first/core.open5gs_log.ausf.ndjson,4454,c74e0c9392b647a2680f2b3cb3a922f441733369d23e3a1c74f67eb4569a101f

powder-5g-core-sim-v1/README.md

@@ -1,6 +1,6 @@
 # powder-5g-core-sim-v1
 
-Built 2026-10-14 from the otel-data-collection pipeline.
+Built 2026-10-14.
 
 Standalone 5G core runs on POWDER (Open5GS 2.8.0 + UERANSIM 3.3.0 simulated gNB/UE): 7 runs with NGAP, 5G NAS, SBI (HTTP/2), PFCP, GTP-U counters, NF logs, UERANSIM logs, RADIUS, injected faults (NF restarts, N2 impairment) with ground-truth timelines. Provenance: real core/gNB/UE software, simulated radio link (no RF).
 

powder-5g-core-sim-v1/TERMS.md

@@ -1,6 +1,6 @@
 # Terms (placeholder)
 
-Collected by the UT Dallas / Purdue POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
-contributors until the owner (Kazi Samin Mubasshir, Purdue) states redistribution terms. Subscriber and
+Collected by the UT Dallas 5G lab POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
+contributors until the owner (Mashroor Hasan Bhuiyan, UT Dallas) states redistribution terms. Subscriber and
 device identifiers are keyed pseudonyms; no raw IMSI/SUPI/IMEI or key material is included. Third-party
 material (Polaris operator captures and drive tests) is deliberately not part of this collection.

powder-5g-core-sim-v1/docs/DEPLOYMENT.md

@@ -19,16 +19,9 @@ Both nodes run `ntp` against `ops.emulab.net`; node-local time is America/Denver
 
 ## Running a collection
 
-```bash
-python -m pipeline.collectors.powder_run --core user@pcNNN.emulab.net --ran user@pcMMM.emulab.net \
-    --scenario baseline|smf-restart|amf-restart|n2-netem|radius --label <free text>
-python -m pipeline.parsers.parse_run --run '2026-*core-sim*'      # -> data/processed/powder_5g_sim/<run_id>/
-python -m validation.check_events_vs_raw --run '2026-*core-sim*'
-```
-
-The orchestrator deploys `pipeline/collectors/` to `~/otel/collectors` on both nodes, runs the node scripts,
-pulls `~/otel/runs/<run_id>` back to `data/raw/powder_5g_sim/<run_id>/{core,ran}/`, and writes the run record
-to `data/raw/powder_5g_sim/<run_id>/run_record.yaml` and to `runs/<run_id>.yaml` here (committed).
+An orchestrator deploys the collector scripts to both nodes, runs one scenario (baseline, smf-restart,
+amf-restart, n2-netem, radius), pulls the captures back, and writes the run record and ground-truth timeline
+(`runs/<run_id>/`, `run_records/<run_id>.yaml`).
 
 Capture points per run:
 
@@ -45,7 +38,7 @@ Capture points per run:
 | `core/config/*.yaml`, `ran/config/*` | exact configs; UE subscriber key/OPc are stripped | — |
 | `timeline.ndjson` + `run_record.yaml` | ground-truth timeline (node clocks + orchestrator clock) | — |
 
-Faults (`pipeline/collectors/fault_inject.sh`): NF restart, NF stop for N seconds, `tc netem` delay/loss on the
+Faults: NF restart, NF stop for N seconds, `tc netem` delay/loss on the
 N2/N3 link. Every injection writes `fault_start`/`fault_end` to the timeline independently of any detector.
 
 ## Runs collected on 2026-09-30 (run records in `runs/`)
@@ -75,7 +68,7 @@ labelled, never hidden.
    the start of the connection. The orchestrator therefore restarts all Open5GS NFs at the start of every run,
    inside the capture window, and records it (`nf_restart_all` / `nf_restart_done`). Frames that still cannot be
    decoded are kept as `kind: undecodable_headers` records so the gap is measurable (`sbi_undecodable_frames` in
-   `inventory/summaries/nr_core.csv`).
+   `summaries/nr_core.csv`).
 3. **UERANSIM gNB does not recover from an AMF restart.** Treat AMF restart as "gNB must be restarted too", or use it
    deliberately as a total-outage scenario.
 4. **NRF 404s after the restart burst** (`nnrf-nfm` heartbeats for instance ids the restarted NRF no longer knows)

powder-5g-core-sim-v1/docs/data_dictionary.md

@@ -1,8 +1,7 @@
 # Data dictionary — requested fields vs. existing data
 
 Stage 1 deliverable. For every field the proposal asks for, this table says whether it is
-**available** in the existing raw archive (`data/raw/raw.7z`), **derivable** from it with the parsers in
-`pipeline/parsers/`, or **needs new collection** on POWDER. "Where" names the raw file and the parser
+**available** in the existing raw archive (`data/raw/raw.7z`), **derivable** from it with the parsers, or **needs new collection** on POWDER. "Where" names the raw file and the parser
 output field. Provenance follows the project rule: `measured` = as captured, `derived` = computed
 from measured data, `simulated` = not from real radios.
 
@@ -10,15 +9,15 @@ Status legend: **A** available (measured, populated) · **D** derivable (compute
 **P** partially available (field exists but is unpopulated or unreliable — see note) · **N** needs new collection.
 
 Verified against the captures on 2026-09-30 (tshark 4.6.4, srsRAN_4G fork commits `ed736f7` and `dd62a9b`).
-Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonzero_fraction`) and
-`inventory/summaries/`.
+Population statistics come from `catalog/catalog.json` (`extra.mr_nonzero_fraction`) and
+`summaries/`.
 
 ## 1. Event data (Elasticsearch records)
 
 | Requested field | Status | Where (raw → processed) | Notes |
 |---|---|---|---|
 | Event timestamp (UTC) | A | pcap frame time → `ts`, `ts_epoch_ns` in `*.s1ap_events`, `*.nas_events`, `*.rrc_events`; srsRAN log stamp → `*.log_events` | pcap and srsRAN log clocks are UTC and agree. Measurement-report and detector timestamps are on other, unaligned clocks (`ts_received_raw`, `ts_local_raw`, `clock` field). |
-| Pseudonymous UE identifier | D | IMSI in Attach request / Identity response → `ue_id` (HMAC-SHA256, salt outside repo); M-TMSI → `tmsi_id` | Raw IMSI never written; validation checks for 15-digit leaks. RNTI (`rnti`) is kept as-is (temporary). |
+| Pseudonymous UE identifier | D | IMSI in Attach request / Identity response → `ue_id` (HMAC-SHA256, salt not distributed); M-TMSI → `tmsi_id` | Raw IMSI never written; validation checks for 15-digit leaks. RNTI (`rnti`) is kept as-is (temporary). |
 | Cell identifier | A | SIB1 in UE/eNB MAC pcaps → `enb_id`, `cell_id_in_enb`, `cell_identity_hex`, `tac` (rrc_events); S1SetupRequest → `enb_id` (s1ap_events); PCI in measurement reports → `serving_pci`, `neighbors[].pci` | ECGI is not present in InitialUEMessage of these srsRAN captures (`s1ap.cell_ID` empty). |
 | Procedure type | A | `procedure`, `message`, `pdu_type` (s1ap_events); `message` (nas_events, rrc_events) | All S1AP class-1/2 procedures named from TS 36.413 tables. |
 | Outcome | A/D | `outcome` = request / indication / success / failure (s1ap, nas) | From PDU choice and NAS message type. |
@@ -26,22 +25,22 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | Authentication events | A | NAS Authentication request/response/failure/reject, Security mode command/complete in s1ap_events and nas_events | Cellular (EPS-AKA) only. |
 | Mobility events | A | HandoverRequired / HandoverPreparationFailure / HandoverCommand (s1ap_events); RRC MeasurementReport, RRCConnectionReconfiguration with `handover_command: true`, RRCConnectionReestablishmentRequest (rrc_events) | Benign runs contain completed S1 handovers between the two eNBs (HandoverRequired → HandoverCommand); fake runs contain HandoverPreparationFailure `unknown-targetID` towards the fake cell. The Polaris MME captures add X2 PathSwitchRequest. |
 | Attach / service request / detach | A | NAS EMM messages (`nas_emm_message`), `Service reject` with `Implicitly detached` in fake runs | |
-| Benign vs. malicious behaviour label (run level) | A | Directory name → `scenario_label` (benign / fake) on every record; `inventory/run_records/*.yaml` scenario.timeline | The activation instant of the fake eNB is not recorded. |
+| Benign vs. malicious behaviour label (run level) | A | Directory name → `scenario_label` (benign / fake) on every record; `run_records/*.yaml` scenario.timeline | The activation instant of the fake eNB is not recorded. |
 | Malicious-event label (frame level) | A (single-ue fake only) | `single-ue/fake/labels/labels.txt` → `frame_label` = `fbs-attributed` on `cn_real.s1ap_events` records | Frame ranges of the EPC S1AP capture attributed to the fake BS (handover attempts towards it). Not available for two-ue runs. |
 | Detector alerts | A (separate) | `detector_outputs/**/*.csv` → `detector.*.ndjson`, `provenance: derived`, `record_type: detector_output`, `final_verdict_label` | Kept in their own index; never merged into the ground-truth timeline. Timestamps unaligned. |
 | Application activity (web, file transfer, streaming) | N (LTE archive) / partial (Stage 3) | Stage 3 runs log ping and one HTTP GET per phase through the UE tunnel | No application logs in the LTE archive; MAC byte counts per second are the closest proxy (`*.mac_stats`, derived). |
 | Node login / service-management events | N | — | Not collected. |
 | Injected fault records (restart, config error, load, backhaul delay/loss) | N (LTE archive) / A (Stage 3) | Stage 3: `scenario.timeline` in every run record | LTE archive: only condition is FBS present/absent. |
 | IMS events (registration, call setup/teardown) | N | — | Needs Kamailio IMS + Open5GS deployment. |
-| RADIUS authentication / accounting | A (Stage 3) | FreeRADIUS 3.0.16 on the core node; `core/pcap/radius.pcap` → `*.radius_events.*` (Access-Request/Accept/Reject, Accounting Start/Interim/Stop with session id, octets, terminate cause, latency, pseudonymised user); `core/logs/freeradius.log` slice | Test clients (`radtest`, `radclient`) drive accept, wrong-password reject, unknown-user reject and accounting per round (`pipeline/collectors/radius_ctl.sh`). Separate from the 5G NAS authentication on N2. |
+| RADIUS authentication / accounting | A (Stage 3) | FreeRADIUS 3.0.16 on the core node; `core/pcap/radius.pcap` → `*.radius_events.*` (Access-Request/Accept/Reject, Accounting Start/Interim/Stop with session id, octets, terminate cause, latency, pseudonymised user); `core/logs/freeradius.log` slice | Test clients (`radtest`, `radclient`) drive accept, wrong-password reject, unknown-user reject and accounting per round. Separate from the 5G NAS authentication on N2. |
 
 ## 2. Network-performance data
 
 | Requested field | Status | Where | Notes |
 |---|---|---|---|
-| Procedure counts per run | D | `inventory/summaries/procedure_counts.csv` | From s1ap_events per capture point. |
-| Handover-preparation failure rate | D | `inventory/summaries/handover_outcomes.csv` (`prep_failure_rate`, causes) | HandoverPreparationFailure ÷ HandoverRequired. |
-| Procedure durations (attach, service request) | D | `inventory/summaries/attach_service.csv` (`attach_ms_*`, `service_req_ms_*`) | Request/response correlated on ENB-UE-S1AP-ID within one capture. |
+| Procedure counts per run | D | `summaries/procedure_counts.csv` | From s1ap_events per capture point. |
+| Handover-preparation failure rate | D | `summaries/handover_outcomes.csv` (`prep_failure_rate`, causes) | HandoverPreparationFailure ÷ HandoverRequired. |
+| Procedure durations (attach, service request) | D | `summaries/attach_service.csv` (`attach_ms_*`, `service_req_ms_*`) | Request/response correlated on ENB-UE-S1AP-ID within one capture. |
 | Signal-quality change over time | D | measurement_reports + rrc MeasurementReport records (time series per UE) | See RF section for the underlying fields. |
 | UL/DL goodput, RTT, jitter, packet loss | A (ZMQ runs) / N (LTE archive) | ZMQ runs: iperf3 JSON (`ran/app/iperf_*.json`), `ping -D` files, `curl -w` timings; POWDER core-sim: ping/HTTP only | Through a simulated radio link; absolute numbers describe the host, not a radio. LTE archive has none. |
 | CQI | P (LTE) | `cqi` in measurement_reports | 0 in >99.9 % of LTE reports. Not exported by the ZMQ setup either (srsUE CSV has no CQI column); use DL SNR/MCS instead. |
@@ -84,7 +83,7 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | PFCP (SMF↔UPF) | A (Stage 3) | `core/pcap/core_lo_cp.pcap` → `*.pfcp_events.*` (message, cause, SEID, F-TEID, UE IP, latency) | |
 | GTP-U user plane (N3) | A/D (Stage 3) | `{core,ran}/pcap/n3_gtpu.pcap` → `*.gtpu_stats.*` per-second bytes/packets per TEID and direction (derived) | Raw user-plane pcap kept separate from control plane. |
 | NF application logs | A (Stage 3) | `core/logs/<nf>.log` slices → `*.open5gs_log.<nf>` (component, level, event class, pseudonymised SUPI) | Local-time stamps converted with the recorded node offset. |
-| Injected faults with ground truth | A (Stage 3) | `run_record.yaml` `scenario.timeline` (`fault_start`/`fault_end`, phase tags) from `pipeline/collectors/fault_inject.sh` | NF restart, NF stop for N s, netem delay/loss on N2/N3. |
+| Injected faults with ground truth | A (Stage 3) | `run_record.yaml` `scenario.timeline` (`fault_start`/`fault_end`, phase tags) from the fault-injection script | NF restart, NF stop for N s, netem delay/loss on N2/N3. |
 | Application workload at the UE | A (Stage 3, minimal) | `ran/app/ping_*.txt`, `ran/app/http.txt` (ping -D, curl timing through `uesimtun0`) | Ping/HTTP only; goodput tests (iperf) not yet run. |
 
 ## Cross-cutting fields required by the data rules
@@ -92,9 +91,9 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | Field | Status | Where |
 |---|---|---|
 | Provenance label | D | `provenance` on every processed record and summary row; run records list outputs with labels |
-| Run identifier | D | `run_id` (`pfl-<variant>-<scenario>-exp-NN`, `detector_outputs-server-data-exp-01`, `polaris-*`) on every record; `inventory/run_records/<run_id>.yaml` |
+| Run identifier | D | `run_id` (`pfl-<variant>-<scenario>-exp-NN`, `detector_outputs-server-data-exp-01`, `polaris-*`) on every record; `run_records/<run_id>.yaml` |
 | Software versions | A | srsRAN commit + branch from log start lines → run record `software_versions`; configs themselves are **not** in the archive |
 | Capture points | A | directory names → `capture_point`; per-file sha256 in run record |
-| Clock-sync information | P | pcap/log clocks consistent (UTC); MR/detector clocks unverified → `clock_sync` note in run record and `notes` in `inventory/catalog/runs.csv` |
+| Clock-sync information | P | pcap/log clocks consistent (UTC); MR/detector clocks unverified → `clock_sync` note in run record and `notes` in `catalog/runs.csv` |
 | Train/test split by whole runs | A | `powder_fbs_lte/single-ue/train_test_split.json` → `split` column in `runs.csv` and run records (single-ue only; two-ue has no split file) |
-| Dropped packets/samples | N | not recorded at capture time; `validation/report.md` compares parsed vs. raw counts instead |
+| Dropped packets/samples | N | not recorded at capture time; parsed vs. raw counts were compared during validation instead |

powder-5g-core-sim-v1/docs/event.schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "otel25/lte_event",
   "title": "LTE structured event record",
-  "description": "One record per protocol message / log line / measurement report produced by pipeline/parsers. Common envelope fields are required; layer-specific fields are optional and documented in inventory/data_dictionary.md.",
+  "description": "One record per protocol message / log line / measurement report produced by the parsers. Common envelope fields are required; layer-specific fields are optional and documented in docs/data_dictionary.md.",
   "type": "object",
   "required": ["run_id", "layer", "provenance", "parser", "source_file"],
   "properties": {

powder-lte-v1.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a1be068cf708055a97852dabc2a84db690e1b34b8d9b6aa40232f5a6ccdb78d2
-size 74625491
+oid sha256:dbf30b2bc8a853f2d99374baa38c7bbab1144c58b7218f37a6b4ccc732926392
+size 74625403

powder-lte-v1.tar.gz.sha256

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6e15bfa702ff263bfa56a1a59f494727296413a9209cc3f618a54ce53cf9c56a
+oid sha256:92f9bd77113fe77ba8ca0bbefe5ee593d4067282271d014ab5701a0d3d84e7ac
 size 87

powder-lte-v1/MANIFEST.csv

@@ -1,12 +1,12 @@
 path,bytes,sha256
-README.md,1683,e054f1a95b8d33476e90ae67cb26b9cba64ba7a3a7666ac0ac3b1d02ded1cd9b
-TERMS.md,434,44d84945b2580e7cbd0bef7b20302973085efacc9860a57ab39158da01d3e6e0
+README.md,1644,f9099838610ebe5d4324db6bf7844cb88a2f3b3838d2827e6cc2f6b15a1c7224
+TERMS.md,437,0a9370c7fef3552790f91ec022b6fc03a7a6da1e3a58f355d73ba06df5d58ef0
 catalog/duplicates.csv,1482,a996c8e13244e3bed5098858850a1b8446375ec50141fdfaeb9b5a84cf8a6836
 catalog/files.csv,253983,c00babce5d65d12ee7c3b239856dca060fd85568863deca56a54509ee3678e8e
 catalog/runs.csv,30440,bd35da3a0ef90278b7b620de477b482721b4048c33ce68c7841f5f37b25fff24
-docs/README.md,8049,478ba0c79bb3a522208e5e8f218986ee3135d6d9fea11c5dcdae12b0e99ddb2b
-docs/data_dictionary.md,13945,5f9947261259ebd75f66f315d29bc77f20830599af0c71b3d8c1cc4468ccf809
-docs/lte_event.schema.json,3359,8854948b0ae9616f00b4823b77cc82e73fc2772038007d58004600e76476feb0
+docs/README.md,7461,085cbe83fa9c9f6e6962ffcce353a7f6f0c7c0f19f6d8359516bd18a292e19ef
+docs/data_dictionary.md,13796,e830dfc50ccbe90b2a63b6e1fb354373e2eff8e32156cba964425d0ece4efd2d
+docs/lte_event.schema.json,3349,426e65e48edcad531b94e118aa36e38525030c77360c662ff6257d9718efb28e
 processed/detector_outputs/server-data/unknown/exp-01/detector.inference_log.ndjson,19566,e2fd4e68c200b3801683dcc72a8560537fa9cfd14334228e4b544a68e6ee0db2
 processed/detector_outputs/server-data/unknown/exp-01/detector.inference_performance.ndjson,5981,b0388998a0415776883d95153af054c2e74afc7fb25b8fd7364bb71eece53ff6
 processed/detector_outputs/server-data/unknown/exp-01/run_manifest.json,1297,a4d5fabe28e93423c5679745b040518a283ed7f65ee06165a98469181ddf8d82
@@ -1135,5 +1135,5 @@ summaries/nr_core.csv,51711,798079cb7365ca073e69ab8290298115670ec0d157e4a45775bb
 summaries/procedure_counts.csv,250576,b4d6308db97ea596a58fa769bd4d81d3e7233ae25dd81571cd8ed79aee77f9ec
 summaries/radio_quality.csv,55601,7fce323981bc8680228f0c6b298a666d6de9c9d9ae2f2dd5855d61cb8041cc2a
 summaries/run_overview.csv,10588,3adcbd145ed23421720a84183d799ed5411493585d1e4b5fc984add641548d78
-summaries/summary.md,43445,71295cd9720fdec6d5d56db47c12fc494d66ebba3375ae03879e535ec73a9251
+summaries/summary.md,43413,1e6f85591caa19dc66c3e7d29d160ea335b1ea9831680b842893ab8b893e17d3
 train_test_split.single-ue.json,489,13f26ceb61743ef57c8f58cbf162fb1c1f1cf82ca59d93c73f611f62e582a2c0

powder-lte-v1/README.md

@@ -1,6 +1,6 @@
 # powder-lte-v1
 
-Built 2026-10-14 from the otel-data-collection pipeline.
+Built 2026-10-14.
 
 POWDER LTE fake-base-station runs (srsRAN_4G): 63 runs, benign vs. fake base station, parsed into S1AP/NAS/RRC events, MAC byte counts, EPC measurement reports and srsENB/srsUE log events, with frame-level malicious labels for single-UE fake runs, detector outputs (predictions, separate), per-run records and derived summaries. Provenance: measured LTE signalling over real SDR radios on POWDER.
 

powder-lte-v1/TERMS.md

@@ -1,6 +1,6 @@
 # Terms (placeholder)
 
-Collected by the UT Dallas / Purdue POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
-contributors until the owner (Kazi Samin Mubasshir, Purdue) states redistribution terms. Subscriber and
+Collected by the UT Dallas 5G lab POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
+contributors until the owner (Mashroor Hasan Bhuiyan, UT Dallas) states redistribution terms. Subscriber and
 device identifiers are keyed pseudonyms; no raw IMSI/SUPI/IMEI or key material is included. Third-party
 material (Polaris operator captures and drive tests) is deliberately not part of this collection.

powder-lte-v1/docs/README.md

@@ -1,7 +1,7 @@
 # Stage 1 — Inventory of existing datasets
 
-What is in `data/raw/raw.7z`, how it is organised, what is wrong with it, and how it was catalogued.
-The archive itself is gitignored; only the metadata in this directory is committed.
+What is in the raw archive (`raw.7z`), how it is organised, what is wrong with it, and how it was catalogued.
+The raw archive itself is not distributed; only the metadata and processed records are.
 
 ## Contents of the archive
 
@@ -70,9 +70,9 @@ MME), UE context release on inactivity. In fake runs the UE additionally camps o
 7. **Missing capture points.** `catalog/runs.csv` column `missing_expected` lists absent files per run
    (e.g. two-ue/benign/exp-6 has no `cn_real` and no `enb_real` S1AP pcap).
 8. **Secrets in logs.** srsENB warning lines dump PDCP integrity keys as hex. The log parser drops every
-   continuation line; never copy raw logs into `data/processed/` or Elasticsearch.
+   continuation line; raw logs are never copied into the processed records.
 9. **Third-party data.** The Polaris MME captures contain real IMSIs/TMSIs of an operator network. Only parse with the
-   pseudonymisation salt in place (`data/.pseudonym_salt`, generated on first run, gitignored) and keep the raw files
+   pseudonymisation salt in place (generated on first run, never distributed) and keep the raw files
    out of any shared location. The Nemo RRC→pcap conversion decodes PCCH paging correctly but DCCH messages are
    partly misdecoded, and the converter writes the handset's local time (UTC-7) as if it were UTC, so those pcaps
    are 7 h early; `nmf_gps` applies the `#UT` offset from the NMF header and is correct. Treat the converted RRC
@@ -80,22 +80,15 @@ MME), UE context release on inactivity. In fake runs the UE additionally camps o
 
 ## How the inventory was produced
 
-```bash
-pip install -r requirements.txt            # + tshark/capinfos on PATH
-python -c "import py7zr; py7zr.SevenZipFile('data/raw/raw.7z').extractall('data/raw/_extract')"
-python -m inventory.catalog_raw -j 8        # -> inventory/catalog/*.csv|json   (sha256, capinfos, log/MR summaries)
-python -m inventory.make_run_records        # -> inventory/run_records/<run_id>.yaml (retro-fitted run records)
-python -m pipeline.parsers.parse_run -j 6   # -> data/processed/<dataset>/<variant>/<scenario>/<exp>/*.ndjson
-python -m pipeline.parsers.summaries        # -> inventory/summaries/*.csv, summary.md (derived)
-python -m validation.check_events_vs_raw    # -> validation/report.md
-python -m pipeline.parsers.es_export [--es-url http://host:9200]   # bulk NDJSON, optional live index
-```
+The raw archive was extracted and catalogued (sha256, capinfos, log and measurement-report summaries), each
+POWDER run got a retro-fitted run record, the captures were parsed into NDJSON event records, derived summaries
+were computed, and parsed records were checked against raw packet counts.
 
-Outputs of Stage 1:
+Outputs:
 
 * `data_dictionary.md` — every requested field marked available / derivable / needs new collection.
-* `catalog/` — file and run catalog (committed).
-* `run_records/` — one retro-fitted run record per POWDER run (committed).
+* `catalog/` — file and run catalog.
+* `run_records/` — one retro-fitted run record per POWDER run.
 * `summaries/` — handover outcomes, attach/service-request durations, radio-quality statistics, cells seen
-  (derived, committed).
-* `data/processed/` — structured LTE event records (NDJSON, gitignored, reproducible with the commands above).
+  (derived).
+* `processed/` (in the tarball) — structured LTE event records (NDJSON).

powder-lte-v1/docs/data_dictionary.md

@@ -1,8 +1,7 @@
 # Data dictionary — requested fields vs. existing data
 
 Stage 1 deliverable. For every field the proposal asks for, this table says whether it is
-**available** in the existing raw archive (`data/raw/raw.7z`), **derivable** from it with the parsers in
-`pipeline/parsers/`, or **needs new collection** on POWDER. "Where" names the raw file and the parser
+**available** in the existing raw archive (`data/raw/raw.7z`), **derivable** from it with the parsers, or **needs new collection** on POWDER. "Where" names the raw file and the parser
 output field. Provenance follows the project rule: `measured` = as captured, `derived` = computed
 from measured data, `simulated` = not from real radios.
 
@@ -10,15 +9,15 @@ Status legend: **A** available (measured, populated) · **D** derivable (compute
 **P** partially available (field exists but is unpopulated or unreliable — see note) · **N** needs new collection.
 
 Verified against the captures on 2026-09-30 (tshark 4.6.4, srsRAN_4G fork commits `ed736f7` and `dd62a9b`).
-Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonzero_fraction`) and
-`inventory/summaries/`.
+Population statistics come from `catalog/catalog.json` (`extra.mr_nonzero_fraction`) and
+`summaries/`.
 
 ## 1. Event data (Elasticsearch records)
 
 | Requested field | Status | Where (raw → processed) | Notes |
 |---|---|---|---|
 | Event timestamp (UTC) | A | pcap frame time → `ts`, `ts_epoch_ns` in `*.s1ap_events`, `*.nas_events`, `*.rrc_events`; srsRAN log stamp → `*.log_events` | pcap and srsRAN log clocks are UTC and agree. Measurement-report and detector timestamps are on other, unaligned clocks (`ts_received_raw`, `ts_local_raw`, `clock` field). |
-| Pseudonymous UE identifier | D | IMSI in Attach request / Identity response → `ue_id` (HMAC-SHA256, salt outside repo); M-TMSI → `tmsi_id` | Raw IMSI never written; validation checks for 15-digit leaks. RNTI (`rnti`) is kept as-is (temporary). |
+| Pseudonymous UE identifier | D | IMSI in Attach request / Identity response → `ue_id` (HMAC-SHA256, salt not distributed); M-TMSI → `tmsi_id` | Raw IMSI never written; validation checks for 15-digit leaks. RNTI (`rnti`) is kept as-is (temporary). |
 | Cell identifier | A | SIB1 in UE/eNB MAC pcaps → `enb_id`, `cell_id_in_enb`, `cell_identity_hex`, `tac` (rrc_events); S1SetupRequest → `enb_id` (s1ap_events); PCI in measurement reports → `serving_pci`, `neighbors[].pci` | ECGI is not present in InitialUEMessage of these srsRAN captures (`s1ap.cell_ID` empty). |
 | Procedure type | A | `procedure`, `message`, `pdu_type` (s1ap_events); `message` (nas_events, rrc_events) | All S1AP class-1/2 procedures named from TS 36.413 tables. |
 | Outcome | A/D | `outcome` = request / indication / success / failure (s1ap, nas) | From PDU choice and NAS message type. |
@@ -26,22 +25,22 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | Authentication events | A | NAS Authentication request/response/failure/reject, Security mode command/complete in s1ap_events and nas_events | Cellular (EPS-AKA) only. |
 | Mobility events | A | HandoverRequired / HandoverPreparationFailure / HandoverCommand (s1ap_events); RRC MeasurementReport, RRCConnectionReconfiguration with `handover_command: true`, RRCConnectionReestablishmentRequest (rrc_events) | Benign runs contain completed S1 handovers between the two eNBs (HandoverRequired → HandoverCommand); fake runs contain HandoverPreparationFailure `unknown-targetID` towards the fake cell. The Polaris MME captures add X2 PathSwitchRequest. |
 | Attach / service request / detach | A | NAS EMM messages (`nas_emm_message`), `Service reject` with `Implicitly detached` in fake runs | |
-| Benign vs. malicious behaviour label (run level) | A | Directory name → `scenario_label` (benign / fake) on every record; `inventory/run_records/*.yaml` scenario.timeline | The activation instant of the fake eNB is not recorded. |
+| Benign vs. malicious behaviour label (run level) | A | Directory name → `scenario_label` (benign / fake) on every record; `run_records/*.yaml` scenario.timeline | The activation instant of the fake eNB is not recorded. |
 | Malicious-event label (frame level) | A (single-ue fake only) | `single-ue/fake/labels/labels.txt` → `frame_label` = `fbs-attributed` on `cn_real.s1ap_events` records | Frame ranges of the EPC S1AP capture attributed to the fake BS (handover attempts towards it). Not available for two-ue runs. |
 | Detector alerts | A (separate) | `detector_outputs/**/*.csv` → `detector.*.ndjson`, `provenance: derived`, `record_type: detector_output`, `final_verdict_label` | Kept in their own index; never merged into the ground-truth timeline. Timestamps unaligned. |
 | Application activity (web, file transfer, streaming) | N (LTE archive) / partial (Stage 3) | Stage 3 runs log ping and one HTTP GET per phase through the UE tunnel | No application logs in the LTE archive; MAC byte counts per second are the closest proxy (`*.mac_stats`, derived). |
 | Node login / service-management events | N | — | Not collected. |
 | Injected fault records (restart, config error, load, backhaul delay/loss) | N (LTE archive) / A (Stage 3) | Stage 3: `scenario.timeline` in every run record | LTE archive: only condition is FBS present/absent. |
 | IMS events (registration, call setup/teardown) | N | — | Needs Kamailio IMS + Open5GS deployment. |
-| RADIUS authentication / accounting | A (Stage 3) | FreeRADIUS 3.0.16 on the core node; `core/pcap/radius.pcap` → `*.radius_events.*` (Access-Request/Accept/Reject, Accounting Start/Interim/Stop with session id, octets, terminate cause, latency, pseudonymised user); `core/logs/freeradius.log` slice | Test clients (`radtest`, `radclient`) drive accept, wrong-password reject, unknown-user reject and accounting per round (`pipeline/collectors/radius_ctl.sh`). Separate from the 5G NAS authentication on N2. |
+| RADIUS authentication / accounting | A (Stage 3) | FreeRADIUS 3.0.16 on the core node; `core/pcap/radius.pcap` → `*.radius_events.*` (Access-Request/Accept/Reject, Accounting Start/Interim/Stop with session id, octets, terminate cause, latency, pseudonymised user); `core/logs/freeradius.log` slice | Test clients (`radtest`, `radclient`) drive accept, wrong-password reject, unknown-user reject and accounting per round. Separate from the 5G NAS authentication on N2. |
 
 ## 2. Network-performance data
 
 | Requested field | Status | Where | Notes |
 |---|---|---|---|
-| Procedure counts per run | D | `inventory/summaries/procedure_counts.csv` | From s1ap_events per capture point. |
-| Handover-preparation failure rate | D | `inventory/summaries/handover_outcomes.csv` (`prep_failure_rate`, causes) | HandoverPreparationFailure ÷ HandoverRequired. |
-| Procedure durations (attach, service request) | D | `inventory/summaries/attach_service.csv` (`attach_ms_*`, `service_req_ms_*`) | Request/response correlated on ENB-UE-S1AP-ID within one capture. |
+| Procedure counts per run | D | `summaries/procedure_counts.csv` | From s1ap_events per capture point. |
+| Handover-preparation failure rate | D | `summaries/handover_outcomes.csv` (`prep_failure_rate`, causes) | HandoverPreparationFailure ÷ HandoverRequired. |
+| Procedure durations (attach, service request) | D | `summaries/attach_service.csv` (`attach_ms_*`, `service_req_ms_*`) | Request/response correlated on ENB-UE-S1AP-ID within one capture. |
 | Signal-quality change over time | D | measurement_reports + rrc MeasurementReport records (time series per UE) | See RF section for the underlying fields. |
 | UL/DL goodput, RTT, jitter, packet loss | A (ZMQ runs) / N (LTE archive) | ZMQ runs: iperf3 JSON (`ran/app/iperf_*.json`), `ping -D` files, `curl -w` timings; POWDER core-sim: ping/HTTP only | Through a simulated radio link; absolute numbers describe the host, not a radio. LTE archive has none. |
 | CQI | P (LTE) | `cqi` in measurement_reports | 0 in >99.9 % of LTE reports. Not exported by the ZMQ setup either (srsUE CSV has no CQI column); use DL SNR/MCS instead. |
@@ -84,7 +83,7 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | PFCP (SMF↔UPF) | A (Stage 3) | `core/pcap/core_lo_cp.pcap` → `*.pfcp_events.*` (message, cause, SEID, F-TEID, UE IP, latency) | |
 | GTP-U user plane (N3) | A/D (Stage 3) | `{core,ran}/pcap/n3_gtpu.pcap` → `*.gtpu_stats.*` per-second bytes/packets per TEID and direction (derived) | Raw user-plane pcap kept separate from control plane. |
 | NF application logs | A (Stage 3) | `core/logs/<nf>.log` slices → `*.open5gs_log.<nf>` (component, level, event class, pseudonymised SUPI) | Local-time stamps converted with the recorded node offset. |
-| Injected faults with ground truth | A (Stage 3) | `run_record.yaml` `scenario.timeline` (`fault_start`/`fault_end`, phase tags) from `pipeline/collectors/fault_inject.sh` | NF restart, NF stop for N s, netem delay/loss on N2/N3. |
+| Injected faults with ground truth | A (Stage 3) | `run_record.yaml` `scenario.timeline` (`fault_start`/`fault_end`, phase tags) from the fault-injection script | NF restart, NF stop for N s, netem delay/loss on N2/N3. |
 | Application workload at the UE | A (Stage 3, minimal) | `ran/app/ping_*.txt`, `ran/app/http.txt` (ping -D, curl timing through `uesimtun0`) | Ping/HTTP only; goodput tests (iperf) not yet run. |
 
 ## Cross-cutting fields required by the data rules
@@ -92,9 +91,9 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | Field | Status | Where |
 |---|---|---|
 | Provenance label | D | `provenance` on every processed record and summary row; run records list outputs with labels |
-| Run identifier | D | `run_id` (`pfl-<variant>-<scenario>-exp-NN`, `detector_outputs-server-data-exp-01`, `polaris-*`) on every record; `inventory/run_records/<run_id>.yaml` |
+| Run identifier | D | `run_id` (`pfl-<variant>-<scenario>-exp-NN`, `detector_outputs-server-data-exp-01`, `polaris-*`) on every record; `run_records/<run_id>.yaml` |
 | Software versions | A | srsRAN commit + branch from log start lines → run record `software_versions`; configs themselves are **not** in the archive |
 | Capture points | A | directory names → `capture_point`; per-file sha256 in run record |
-| Clock-sync information | P | pcap/log clocks consistent (UTC); MR/detector clocks unverified → `clock_sync` note in run record and `notes` in `inventory/catalog/runs.csv` |
+| Clock-sync information | P | pcap/log clocks consistent (UTC); MR/detector clocks unverified → `clock_sync` note in run record and `notes` in `catalog/runs.csv` |
 | Train/test split by whole runs | A | `powder_fbs_lte/single-ue/train_test_split.json` → `split` column in `runs.csv` and run records (single-ue only; two-ue has no split file) |
-| Dropped packets/samples | N | not recorded at capture time; `validation/report.md` compares parsed vs. raw counts instead |
+| Dropped packets/samples | N | not recorded at capture time; parsed vs. raw counts were compared during validation instead |

powder-lte-v1/docs/lte_event.schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "otel25/lte_event",
   "title": "LTE structured event record",
-  "description": "One record per protocol message / log line / measurement report produced by pipeline/parsers. Common envelope fields are required; layer-specific fields are optional and documented in inventory/data_dictionary.md.",
+  "description": "One record per protocol message / log line / measurement report produced by the parsers. Common envelope fields are required; layer-specific fields are optional and documented in docs/data_dictionary.md.",
   "type": "object",
   "required": ["run_id", "layer", "provenance", "parser", "source_file"],
   "properties": {

powder-lte-v1/summaries/summary.md

@@ -1,6 +1,6 @@
 # Derived summaries of the existing POWDER LTE runs
 
-Generated by `python -m pipeline.parsers.summaries` from `data/processed/`. All values are **derived** from measured captures; see the CSV files in this directory for the full tables.
+Generated from the processed event records. All values are **derived** from measured captures; see the CSV files in this directory for the full tables.
 
 ## Records per run
 

zmq-5g-core-sim-v1.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e286a75c57a52df6c145b8552f62513d246a6ee107b286c537c4eb76daf313cb
-size 9370315
+oid sha256:0537afd7f629223c756f2a5f4ab0346215ebeb8f4bb7e54d4a7b24a95b62d4ee
+size 9370094

zmq-5g-core-sim-v1.tar.gz.sha256

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:01e87ace0908b661372400b5a1c27689970f7d4c3d79fe350cf1f872a1c2f4a8
+oid sha256:bc8646ea8b46854d1d5104f370f1f8cd3f5a4a58248afb0312f2506f7ab02e9e
 size 92

zmq-5g-core-sim-v1/MANIFEST.csv

@@ -1,9 +1,9 @@
 path,bytes,sha256
-README.md,1717,b6ccfff617fd4b129809d0882e33fadf641d48ceadad2c75549c8467838592c0
-TERMS.md,434,44d84945b2580e7cbd0bef7b20302973085efacc9860a57ab39158da01d3e6e0
-docs/DEPLOYMENT.md,5084,5525658ef216cb087dbaa5f2105e8c7a04633b818a3f9f717d7f0b4c6a468dc8
-docs/data_dictionary.md,13945,5f9947261259ebd75f66f315d29bc77f20830599af0c71b3d8c1cc4468ccf809
-docs/event.schema.json,3359,8854948b0ae9616f00b4823b77cc82e73fc2772038007d58004600e76476feb0
+README.md,1678,b0fb8aba20769df8c526d71c073cfe5a71e561232f731883e43dd16d2071a15f
+TERMS.md,437,0a9370c7fef3552790f91ec022b6fc03a7a6da1e3a58f355d73ba06df5d58ef0
+docs/DEPLOYMENT.md,4835,417741945089bc661d02cfe2466c0923afcb4f4df434582cdbb6490467442b12
+docs/data_dictionary.md,13796,e830dfc50ccbe90b2a63b6e1fb354373e2eff8e32156cba964425d0ece4efd2d
+docs/event.schema.json,3349,426e65e48edcad531b94e118aa36e38525030c77360c662ff6257d9718efb28e
 processed/2026-10-14T075929Z_zmq_baseline_test/core.gtpu_stats.n3_gtpu.ndjson,50173,028f9a7ccd6e291293d55ef87141102f8d49212a0d7be2bd22e0acdafc34eb2f
 processed/2026-10-14T075929Z_zmq_baseline_test/core.ngap_events.n2_ngap.ndjson,19037,54a937e651fc38b7d7540b9a1a8da414e455ad116dcd69c15f8b23927d95151d
 processed/2026-10-14T075929Z_zmq_baseline_test/core.open5gs_log.amf.ndjson,23523,2498d51824e3288a93eb91f5ad62a1c26e664e5c8a9d490d236f95d034d5708f

zmq-5g-core-sim-v1/README.md

@@ -1,6 +1,6 @@
 # zmq-5g-core-sim-v1
 
-Built 2026-10-14 from the otel-data-collection pipeline.
+Built 2026-10-14.
 
 Local software-only 5G SA runs (Open5GS 2.7.7 + ocudu gNB + srsUE over a ZMQ radio link): 87 runs across baseline, re-attach cycles, NF restarts and outages, scheduler MCS caps, TCP/UDP load; NGAP, 5G NAS, NR RRC, SBI, PFCP, GTP-U and MAC-NR counters, gNB scheduler metrics and per-second UE radio metrics (RSRP, SNR, MCS, BLER, bitrates), iperf/ping/HTTP results, ground-truth timelines. Provenance: real core/gNB/UE software, simulated radio (no RF).
 

zmq-5g-core-sim-v1/TERMS.md

@@ -1,6 +1,6 @@
 # Terms (placeholder)
 
-Collected by the UT Dallas / Purdue POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
-contributors until the owner (Kazi Samin Mubasshir, Purdue) states redistribution terms. Subscriber and
+Collected by the UT Dallas 5G lab POWDER data-collection effort for OTel 2.5. Internal to the OTel 2.5
+contributors until the owner (Mashroor Hasan Bhuiyan, UT Dallas) states redistribution terms. Subscriber and
 device identifiers are keyed pseudonyms; no raw IMSI/SUPI/IMEI or key material is included. Third-party
 material (Polaris operator captures and drive tests) is deliberately not part of this collection.

zmq-5g-core-sim-v1/docs/DEPLOYMENT.md

@@ -21,12 +21,11 @@ Fixes that were needed on this host (already applied): freeDiameter config and c
 
 - `core_ctl.sh start|stop|status|restart-nf <nf>|stop-nf <nf> <s>` — core from the build tree; faults emit timeline events.
 - `ran_ctl.sh gnb-start|ue-start|ping|iperf|http|ue-stop|gnb-stop <run_dir>` — gNB/UE lifecycle and workload (iperf3 server bound to 10.45.0.1; UE side runs in `netns ue1`).
-- `pipeline/collectors/local_run.py --scenario X | --duration-hours H` — orchestrator: captures (tcpdump on `lo` for SBI/PFCP, NGAP, GTP-U via `pipeline/collectors/core_capture.sh`), scenario steps, run record and timeline into `data/raw/zmq_5g_sim/<run_id>/{core,ran}/`, committed run record in `runs/`.
+- orchestrator (`--scenario X | --duration-hours H`): captures (tcpdump on `lo` for SBI/PFCP, NGAP, GTP-U), scenario steps, run record and timeline per run.
 
 Host fix: Ubuntu's AppArmor profile for `/usr/bin/tcpdump` denies signals, so capture-stop could not end
 tcpdump and finished runs kept recording (first batch). The profile is now in complain mode
-(profile unloaded with `sudo apparmor_parser -R /etc/apparmor.d/usr.bin.tcpdump` and disabled via `/etc/apparmor.d/disable/`); affected runs were cut back to their windows with
-`pipeline/collectors/trim_captures.py` and carry `captures_trimmed` in their run records.
+(profile unloaded with `sudo apparmor_parser -R /etc/apparmor.d/usr.bin.tcpdump` and disabled via `/etc/apparmor.d/disable/`); affected runs were cut back to their windows and carry `captures_trimmed` in their run records.
 
 Quirks: the gNB must be restarted whenever the UE restarts (the ZMQ link blocks on a stale peer); a stale gNB
 holding :2152 or :2000 makes the next gNB fail to start (the orchestrator kills stale processes first);
@@ -39,7 +38,7 @@ ausf-stop · awgn-15 / awgn-8 / awgn-3 (srsUE downlink AWGN at that SNR) · dl-d
 emulation). Each run is 1–5 minutes; a baseline with 20 s of 10 Mbps iperf is about 240 MB because the user
 plane is captured at five points (gNB MAC, gNB RLC, gNB N3, UE MAC-NR, loopback N3).
 
-## What the parsers produce per run (`python -m pipeline.parsers.parse_run --run '*zmq*'`)
+## What the parsers produce per run
 
 core: `sbi_events`, `pfcp_events`, `ngap_events`, `gtpu_stats`, `open5gs_log.<nf>` · ran: `ngap_events.gnb_ngap`,
 `nas5g_events.ue_nas`, `nr_rrc_events.{ue_mac_nr,gnb_mac}`, `mac_nr_stats.*`, `gtpu_stats.gnb_n3`,

zmq-5g-core-sim-v1/docs/data_dictionary.md

@@ -1,8 +1,7 @@
 # Data dictionary — requested fields vs. existing data
 
 Stage 1 deliverable. For every field the proposal asks for, this table says whether it is
-**available** in the existing raw archive (`data/raw/raw.7z`), **derivable** from it with the parsers in
-`pipeline/parsers/`, or **needs new collection** on POWDER. "Where" names the raw file and the parser
+**available** in the existing raw archive (`data/raw/raw.7z`), **derivable** from it with the parsers, or **needs new collection** on POWDER. "Where" names the raw file and the parser
 output field. Provenance follows the project rule: `measured` = as captured, `derived` = computed
 from measured data, `simulated` = not from real radios.
 
@@ -10,15 +9,15 @@ Status legend: **A** available (measured, populated) · **D** derivable (compute
 **P** partially available (field exists but is unpopulated or unreliable — see note) · **N** needs new collection.
 
 Verified against the captures on 2026-09-30 (tshark 4.6.4, srsRAN_4G fork commits `ed736f7` and `dd62a9b`).
-Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonzero_fraction`) and
-`inventory/summaries/`.
+Population statistics come from `catalog/catalog.json` (`extra.mr_nonzero_fraction`) and
+`summaries/`.
 
 ## 1. Event data (Elasticsearch records)
 
 | Requested field | Status | Where (raw → processed) | Notes |
 |---|---|---|---|
 | Event timestamp (UTC) | A | pcap frame time → `ts`, `ts_epoch_ns` in `*.s1ap_events`, `*.nas_events`, `*.rrc_events`; srsRAN log stamp → `*.log_events` | pcap and srsRAN log clocks are UTC and agree. Measurement-report and detector timestamps are on other, unaligned clocks (`ts_received_raw`, `ts_local_raw`, `clock` field). |
-| Pseudonymous UE identifier | D | IMSI in Attach request / Identity response → `ue_id` (HMAC-SHA256, salt outside repo); M-TMSI → `tmsi_id` | Raw IMSI never written; validation checks for 15-digit leaks. RNTI (`rnti`) is kept as-is (temporary). |
+| Pseudonymous UE identifier | D | IMSI in Attach request / Identity response → `ue_id` (HMAC-SHA256, salt not distributed); M-TMSI → `tmsi_id` | Raw IMSI never written; validation checks for 15-digit leaks. RNTI (`rnti`) is kept as-is (temporary). |
 | Cell identifier | A | SIB1 in UE/eNB MAC pcaps → `enb_id`, `cell_id_in_enb`, `cell_identity_hex`, `tac` (rrc_events); S1SetupRequest → `enb_id` (s1ap_events); PCI in measurement reports → `serving_pci`, `neighbors[].pci` | ECGI is not present in InitialUEMessage of these srsRAN captures (`s1ap.cell_ID` empty). |
 | Procedure type | A | `procedure`, `message`, `pdu_type` (s1ap_events); `message` (nas_events, rrc_events) | All S1AP class-1/2 procedures named from TS 36.413 tables. |
 | Outcome | A/D | `outcome` = request / indication / success / failure (s1ap, nas) | From PDU choice and NAS message type. |
@@ -26,22 +25,22 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | Authentication events | A | NAS Authentication request/response/failure/reject, Security mode command/complete in s1ap_events and nas_events | Cellular (EPS-AKA) only. |
 | Mobility events | A | HandoverRequired / HandoverPreparationFailure / HandoverCommand (s1ap_events); RRC MeasurementReport, RRCConnectionReconfiguration with `handover_command: true`, RRCConnectionReestablishmentRequest (rrc_events) | Benign runs contain completed S1 handovers between the two eNBs (HandoverRequired → HandoverCommand); fake runs contain HandoverPreparationFailure `unknown-targetID` towards the fake cell. The Polaris MME captures add X2 PathSwitchRequest. |
 | Attach / service request / detach | A | NAS EMM messages (`nas_emm_message`), `Service reject` with `Implicitly detached` in fake runs | |
-| Benign vs. malicious behaviour label (run level) | A | Directory name → `scenario_label` (benign / fake) on every record; `inventory/run_records/*.yaml` scenario.timeline | The activation instant of the fake eNB is not recorded. |
+| Benign vs. malicious behaviour label (run level) | A | Directory name → `scenario_label` (benign / fake) on every record; `run_records/*.yaml` scenario.timeline | The activation instant of the fake eNB is not recorded. |
 | Malicious-event label (frame level) | A (single-ue fake only) | `single-ue/fake/labels/labels.txt` → `frame_label` = `fbs-attributed` on `cn_real.s1ap_events` records | Frame ranges of the EPC S1AP capture attributed to the fake BS (handover attempts towards it). Not available for two-ue runs. |
 | Detector alerts | A (separate) | `detector_outputs/**/*.csv` → `detector.*.ndjson`, `provenance: derived`, `record_type: detector_output`, `final_verdict_label` | Kept in their own index; never merged into the ground-truth timeline. Timestamps unaligned. |
 | Application activity (web, file transfer, streaming) | N (LTE archive) / partial (Stage 3) | Stage 3 runs log ping and one HTTP GET per phase through the UE tunnel | No application logs in the LTE archive; MAC byte counts per second are the closest proxy (`*.mac_stats`, derived). |
 | Node login / service-management events | N | — | Not collected. |
 | Injected fault records (restart, config error, load, backhaul delay/loss) | N (LTE archive) / A (Stage 3) | Stage 3: `scenario.timeline` in every run record | LTE archive: only condition is FBS present/absent. |
 | IMS events (registration, call setup/teardown) | N | — | Needs Kamailio IMS + Open5GS deployment. |
-| RADIUS authentication / accounting | A (Stage 3) | FreeRADIUS 3.0.16 on the core node; `core/pcap/radius.pcap` → `*.radius_events.*` (Access-Request/Accept/Reject, Accounting Start/Interim/Stop with session id, octets, terminate cause, latency, pseudonymised user); `core/logs/freeradius.log` slice | Test clients (`radtest`, `radclient`) drive accept, wrong-password reject, unknown-user reject and accounting per round (`pipeline/collectors/radius_ctl.sh`). Separate from the 5G NAS authentication on N2. |
+| RADIUS authentication / accounting | A (Stage 3) | FreeRADIUS 3.0.16 on the core node; `core/pcap/radius.pcap` → `*.radius_events.*` (Access-Request/Accept/Reject, Accounting Start/Interim/Stop with session id, octets, terminate cause, latency, pseudonymised user); `core/logs/freeradius.log` slice | Test clients (`radtest`, `radclient`) drive accept, wrong-password reject, unknown-user reject and accounting per round. Separate from the 5G NAS authentication on N2. |
 
 ## 2. Network-performance data
 
 | Requested field | Status | Where | Notes |
 |---|---|---|---|
-| Procedure counts per run | D | `inventory/summaries/procedure_counts.csv` | From s1ap_events per capture point. |
-| Handover-preparation failure rate | D | `inventory/summaries/handover_outcomes.csv` (`prep_failure_rate`, causes) | HandoverPreparationFailure ÷ HandoverRequired. |
-| Procedure durations (attach, service request) | D | `inventory/summaries/attach_service.csv` (`attach_ms_*`, `service_req_ms_*`) | Request/response correlated on ENB-UE-S1AP-ID within one capture. |
+| Procedure counts per run | D | `summaries/procedure_counts.csv` | From s1ap_events per capture point. |
+| Handover-preparation failure rate | D | `summaries/handover_outcomes.csv` (`prep_failure_rate`, causes) | HandoverPreparationFailure ÷ HandoverRequired. |
+| Procedure durations (attach, service request) | D | `summaries/attach_service.csv` (`attach_ms_*`, `service_req_ms_*`) | Request/response correlated on ENB-UE-S1AP-ID within one capture. |
 | Signal-quality change over time | D | measurement_reports + rrc MeasurementReport records (time series per UE) | See RF section for the underlying fields. |
 | UL/DL goodput, RTT, jitter, packet loss | A (ZMQ runs) / N (LTE archive) | ZMQ runs: iperf3 JSON (`ran/app/iperf_*.json`), `ping -D` files, `curl -w` timings; POWDER core-sim: ping/HTTP only | Through a simulated radio link; absolute numbers describe the host, not a radio. LTE archive has none. |
 | CQI | P (LTE) | `cqi` in measurement_reports | 0 in >99.9 % of LTE reports. Not exported by the ZMQ setup either (srsUE CSV has no CQI column); use DL SNR/MCS instead. |
@@ -84,7 +83,7 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | PFCP (SMF↔UPF) | A (Stage 3) | `core/pcap/core_lo_cp.pcap` → `*.pfcp_events.*` (message, cause, SEID, F-TEID, UE IP, latency) | |
 | GTP-U user plane (N3) | A/D (Stage 3) | `{core,ran}/pcap/n3_gtpu.pcap` → `*.gtpu_stats.*` per-second bytes/packets per TEID and direction (derived) | Raw user-plane pcap kept separate from control plane. |
 | NF application logs | A (Stage 3) | `core/logs/<nf>.log` slices → `*.open5gs_log.<nf>` (component, level, event class, pseudonymised SUPI) | Local-time stamps converted with the recorded node offset. |
-| Injected faults with ground truth | A (Stage 3) | `run_record.yaml` `scenario.timeline` (`fault_start`/`fault_end`, phase tags) from `pipeline/collectors/fault_inject.sh` | NF restart, NF stop for N s, netem delay/loss on N2/N3. |
+| Injected faults with ground truth | A (Stage 3) | `run_record.yaml` `scenario.timeline` (`fault_start`/`fault_end`, phase tags) from the fault-injection script | NF restart, NF stop for N s, netem delay/loss on N2/N3. |
 | Application workload at the UE | A (Stage 3, minimal) | `ran/app/ping_*.txt`, `ran/app/http.txt` (ping -D, curl timing through `uesimtun0`) | Ping/HTTP only; goodput tests (iperf) not yet run. |
 
 ## Cross-cutting fields required by the data rules
@@ -92,9 +91,9 @@ Population statistics come from `inventory/catalog/catalog.json` (`extra.mr_nonz
 | Field | Status | Where |
 |---|---|---|
 | Provenance label | D | `provenance` on every processed record and summary row; run records list outputs with labels |
-| Run identifier | D | `run_id` (`pfl-<variant>-<scenario>-exp-NN`, `detector_outputs-server-data-exp-01`, `polaris-*`) on every record; `inventory/run_records/<run_id>.yaml` |
+| Run identifier | D | `run_id` (`pfl-<variant>-<scenario>-exp-NN`, `detector_outputs-server-data-exp-01`, `polaris-*`) on every record; `run_records/<run_id>.yaml` |
 | Software versions | A | srsRAN commit + branch from log start lines → run record `software_versions`; configs themselves are **not** in the archive |
 | Capture points | A | directory names → `capture_point`; per-file sha256 in run record |
-| Clock-sync information | P | pcap/log clocks consistent (UTC); MR/detector clocks unverified → `clock_sync` note in run record and `notes` in `inventory/catalog/runs.csv` |
+| Clock-sync information | P | pcap/log clocks consistent (UTC); MR/detector clocks unverified → `clock_sync` note in run record and `notes` in `catalog/runs.csv` |
 | Train/test split by whole runs | A | `powder_fbs_lte/single-ue/train_test_split.json` → `split` column in `runs.csv` and run records (single-ue only; two-ue has no split file) |
-| Dropped packets/samples | N | not recorded at capture time; `validation/report.md` compares parsed vs. raw counts instead |
+| Dropped packets/samples | N | not recorded at capture time; parsed vs. raw counts were compared during validation instead |

zmq-5g-core-sim-v1/docs/event.schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "otel25/lte_event",
   "title": "LTE structured event record",
-  "description": "One record per protocol message / log line / measurement report produced by pipeline/parsers. Common envelope fields are required; layer-specific fields are optional and documented in inventory/data_dictionary.md.",
+  "description": "One record per protocol message / log line / measurement report produced by the parsers. Common envelope fields are required; layer-specific fields are optional and documented in docs/data_dictionary.md.",
   "type": "object",
   "required": ["run_id", "layer", "provenance", "parser", "source_file"],
   "properties": {