diff options
| -rw-r--r-- | index.html | 287 |
1 files changed, 164 insertions, 123 deletions
@@ -2,7 +2,7 @@ <html lang="en"> <head> <meta charset="UTF-8"> -<title>ARFHL Tactical HaLow Mesh Network</title> +<title>ARFHL Tactical Wi-Fi HaLow Mesh Network</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <style> body { @@ -45,6 +45,7 @@ th, td { border: 1px solid #2e3b4a; padding: 10px; text-align: left; + vertical-align: top; } th { background-color: #1b2633; @@ -73,6 +74,12 @@ ul { margin: 20px 0; border: 1px solid #2e3b4a; } +.note { + background-color: #1a222b; + padding: 15px; + border-left: 4px solid #90caf9; + margin: 20px 0; +} </style> </head> @@ -82,208 +89,242 @@ ul { <h1>ARFHL Tactical Wi-Fi HaLow Mesh Network</h1> <p> A distributed, sub-GHz tactical communications backbone designed for contested, -infrastructure-denied environments. ARFHL provides secure transport for messages, -telemetry, images, and opportunistic video using open standards and a survivable -mesh architecture. +infrastructure-denied environments. Optimized for attrition warfare, electronic +warfare pressure, and rapid field deployment without vendor lock-in. </p> <span class="badge">IEEE 802.11ah</span> -<span class="badge">Sub-GHz</span> +<span class="badge">Distributed Mesh</span> <span class="badge">Post-Quantum Ready</span> -<span class="badge">No Vendor Lock-In</span> +<span class="badge">Open IP Backbone</span> </header> <section> <h2>1. Product Description</h2> <p> -The ARFHL system is a portable Wi-Fi HaLow (IEEE 802.11ah) mesh network designed to -function in environments where no existing communications infrastructure can be -assumed and where electromagnetic conditions are hostile. +ARFHL is a portable Wi-Fi HaLow (IEEE 802.11ah) mesh network providing secure IP +transport for messages, telemetry, images, and opportunistic video. The system +is designed to operate where traditional tactical radios and centralized +command networks fail. </p> <p> -Unlike centralized tactical radios or SATCOM-dependent systems, ARFHL operates as -a <strong>self-forming, self-healing distributed network</strong>. Each node may act -as an endpoint, relay, or gateway without manual RF planning. +ARFHL prioritizes <strong>survivability, simplicity, and manufacturability</strong> +over peak throughput. It deliberately avoids proprietary waveforms and closed +ecosystems in favor of open standards and crypto agility. </p> -<h3>Key Characteristics</h3> -<ul> -<li>Sub-GHz operation for extended range and terrain penetration</li> -<li>Graceful degradation from Mbps to kbps under jamming or low SNR</li> -<li>Peer-to-peer mesh with optional backbone formation</li> -<li>Standard IP transport for interoperability with civilian and military devices</li> -<li>Designed for low electromagnetic signature and intermittent connectivity</li> -</ul> - -<h3>Technical Specifications (ARFHL-AP)</h3> +<h3>Technical Summary</h3> <table> -<tr><th>Feature</th><th>Specification</th></tr> -<tr><td>Standard</td><td>IEEE 802.11ah (Wi-Fi HaLow)</td></tr> -<tr><td>Frequency</td><td>Sub-1 GHz (regional bands)</td></tr> -<tr><td>Data Rate</td><td>150 kbps – 86.7 Mbps (adaptive)</td></tr> -<tr><td>Range</td><td>>1 km (terrain dependent)</td></tr> -<tr><td>Modulation</td><td>OFDM (BPSK, QPSK, 16/64/256-QAM)</td></tr> -<tr><td>Topology</td><td>Mesh / Star / Relay</td></tr> -<tr><td>Security</td><td>WPA3 + Hybrid Post-Quantum Key Exchange</td></tr> -<tr><td>OTA Updates</td><td>Supported (air-gapped capable)</td></tr> -<tr><td>Power Profile</td><td>Low-power, multi-day active, multi-year standby</td></tr> +<tr><th>Parameter</th><th>Specification</th></tr> +<tr><td>Frequency</td><td>Sub-1 GHz regional bands</td></tr> +<tr><td>Range</td><td>>1 km per hop (terrain dependent)</td></tr> +<tr><td>Throughput</td><td>150 kbps – 86.7 Mbps (adaptive)</td></tr> +<tr><td>Topology</td><td>Self-forming mesh, optional backbone</td></tr> +<tr><td>Security</td><td>WPA3 + hybrid PQ key exchange</td></tr> +<tr><td>Power</td><td>Multi-day active, multi-year standby</td></tr> +<tr><td>Interoperability</td><td>Standard IP (IPv4/IPv6)</td></tr> </table> </section> <section> -<h2>2. Concept of Operations (CONOPS)</h2> +<h2>2. Doctrine-Aligned Use Cases</h2> -<h3>Mission Context</h3> -<p> -ARFHL is intended for platoon to battalion-level operations in environments where: -</p> +<h3>Platoon Level (0–2 km)</h3> <ul> -<li>Fixed infrastructure is absent or destroyed</li> -<li>Spectrum is contested or actively jammed</li> -<li>Command nodes are subject to targeting</li> -<li>Logistics resupply is uncertain</li> +<li>Text and command messaging between squads</li> +<li>Still image transfer (UAV snapshots, ISR photos)</li> +<li>Blue-force tracking via low-rate telemetry</li> +<li>Operation without a fixed command vehicle</li> </ul> -<h3>Operational Flow</h3> +<h3>Company Level (2–10 km, multi-hop)</h3> <ul> -<li>Nodes are deployed manually, by vehicle, or by personnel</li> -<li>Network self-forms within seconds without RF planning</li> -<li>Traffic prioritization ensures command and text traffic survives first</li> -<li>Images and video are transferred opportunistically</li> -<li>Network continues operating despite loss of individual nodes</li> +<li>Mesh backbone formed by ARFHL-AP gateways</li> +<li>Forward elements remain connected despite node losses</li> +<li>Intermittent video bursts from ISR assets</li> +<li>Local autonomy when higher echelons are unreachable</li> </ul> -<h3>Supported Traffic</h3> +<h3>Battalion Level (Distributed)</h3> <ul> -<li>Encrypted text messaging and command data</li> -<li>Still images (UAV, body-worn cameras)</li> -<li>Low-frame-rate situational video (best-effort)</li> -<li>Sensor and telemetry data</li> +<li>ARFHL used as resilient last-mile and lateral network</li> +<li>Integration with SATCOM or fiber when available</li> +<li>Delay-tolerant networking for fragmented battlespace</li> </ul> + +<div class="note"> +<strong>Operational assumption:</strong> Command continuity must survive loss of +vehicles, gateways, and spectrum superiority. +</div> +</section> + +<section> +<h2>3. Current System Limitations vs ARFHL Improvements</h2> + +<table> +<tr> +<th>Observed Issue (Ukraine)</th> +<th>Typical Current Systems</th> +<th>ARFHL Response</th> +</tr> +<tr> +<td>Centralized nodes destroyed</td> +<td>Star topology collapses</td> +<td>Fully distributed mesh, no single point of failure</td> +</tr> +<tr> +<td>EW detection and targeting</td> +<td>Constant beacons, high RF signature</td> +<td>Adaptive duty cycle, low-power sub-GHz operation</td> +</tr> +<tr> +<td>High logistics burden</td> +<td>Short battery life, proprietary spares</td> +<td>Low power design, COTS components</td> +</tr> +<tr> +<td>Vendor lock-in</td> +<td>Closed waveforms, restricted devices</td> +<td>Open IEEE + IP backbone</td> +</tr> +<tr> +<td>Training overhead</td> +<td>Weeks of signal training</td> +<td>Hours-level operator training</td> +</tr> +<tr> +<td>Crypto obsolescence risk</td> +<td>Fixed algorithms</td> +<td>Crypto-agile, post-quantum ready</td> +</tr> +</table> </section> <section> -<h2>3. Threat Model and EW Survivability</h2> +<h2>4. Device Management and Lifecycle Control</h2> -<h3>Threat Assumptions</h3> +<h3>Device Management</h3> <ul> -<li>Wideband and narrowband jamming</li> -<li>RF direction finding and emitter geolocation</li> -<li>Node capture and physical compromise</li> -<li>Intermittent connectivity and network partitioning</li> +<li>Local device management server (no cloud dependency)</li> +<li>Role-based access control (operator / signal officer)</li> +<li>Bulk provisioning via mission profiles</li> +<li>Network health and link quality visualization</li> </ul> -<h3>Survivability Measures</h3> +<h3>Firmware and Configuration</h3> <ul> -<li>Sub-GHz operation reduces path loss and required transmit power</li> -<li>Adaptive duty cycling minimizes RF emissions</li> -<li>No constant beacons or centralized control traffic</li> -<li>Distributed routing avoids decapitation failures</li> -<li>End-to-end encryption with forward secrecy</li> +<li>OTA updates supported in connected environments</li> +<li>Air-gapped update capability via removable media</li> +<li>Cryptographic material managed independently of firmware</li> </ul> -<h3>Limitations (Explicit)</h3> +<h3>Capture and Compromise Handling</h3> <ul> -<li>Not designed for sustained high-definition video streaming</li> -<li>Not a replacement for long-range SATCOM</li> -<li>Performance degrades under continuous broadband jamming</li> +<li>Key rotation and node revocation</li> +<li>No centralized secrets stored on gateways</li> +<li>Limited intelligence value upon physical capture</li> </ul> </section> <section> -<h2>4. Training and Documentation</h2> +<h2>5. Costed BOM and Unit Economics (Indicative)</h2> -<p> -ARFHL is designed to minimize training burden under combat conditions. -</p> +<h3>Estimated Bill of Materials (ARFHL-AP)</h3> +<table> +<tr><th>Component</th><th>Estimated Unit Cost (EUR)</th></tr> +<tr><td>Wi-Fi HaLow SoC + RF front-end</td><td>35–50</td></tr> +<tr><td>MCU / Control processor</td><td>8–12</td></tr> +<tr><td>Memory (RAM + Flash)</td><td>6–10</td></tr> +<tr><td>Power management + regulators</td><td>5–8</td></tr> +<tr><td>Industrial PCB + assembly</td><td>12–18</td></tr> +<tr><td>Rugged enclosure + connectors</td><td>20–30</td></tr> +<tr><td><strong>Total BOM (approx.)</strong></td><td><strong>86–128</strong></td></tr> +</table> +<h3>Unit Economics (Order of Magnitude)</h3> <ul> -<li>Operator training: hours, not weeks</li> -<li>No RF engineering background required</li> -<li>Quick-reference cards for field use</li> -<li>CLI and GUI manuals for signal officers</li> +<li>Target unit production cost: < 200 EUR</li> +<li>Indicative procurement price: low hundreds EUR</li> +<li>Order-of-magnitude cheaper than SDR-based tactical radios</li> </ul> -<p> -Documentation includes: -</p> -<ul> -<li>Operator handbook</li> -<li>Signal officer configuration guide</li> -<li>Security and crypto management manual</li> -<li>Maintenance and field repair instructions</li> -</ul> +<div class="note"> +Cost structure enables mass deployment and attrition tolerance, +not boutique low-volume procurement. +</div> </section> <section> -<h2>5. Manufacturing and MRL Roadmap</h2> +<h2>6. Manufacturing Readiness and Scaling</h2> -<h3>Design Philosophy</h3> -<ul> -<li>COTS silicon where survivable</li> -<li>Open firmware architecture</li> -<li>No export-restricted proprietary waveforms</li> -</ul> - -<h3>Manufacturing Readiness Levels</h3> <table> -<tr><th>MRL</th><th>Status</th></tr> -<tr><td>MRL 3–4</td><td>Functional prototypes validated in lab and field trials</td></tr> -<tr><td>MRL 5</td><td>Pilot production using contract electronics manufacturers</td></tr> -<tr><td>MRL 6</td><td>Low-rate initial production with environmental testing</td></tr> -<tr><td>MRL 7+</td><td>Scalable production leveraging civilian supply chains</td></tr> +<tr><th>MRL</th><th>Description</th></tr> +<tr> +<td>MRL 4–5</td> +<td>Validated prototypes, field trials in contested RF environments</td> +</tr> +<tr> +<td>MRL 6</td> +<td>Low-rate initial production, environmental and shock testing</td> +</tr> +<tr> +<td>MRL 7–8</td> +<td>Scalable manufacturing using civilian EMS providers</td> +</tr> +<tr> +<td>MRL 9</td> +<td>Sustained production with multiple supply sources</td> +</tr> </table> </section> <section> -<h2>6. Security Architecture</h2> +<h2>7. Security Architecture</h2> <ul> -<li>WPA3 baseline security</li> -<li>Hybrid classical + post-quantum key exchange (e.g., X25519 + Kyber)</li> -<li>Algorithm agility via firmware updates</li> -<li>No mandatory cloud or subscription services</li> -<li>Supports air-gapped operation</li> +<li>End-to-end encryption (WPA3 baseline)</li> +<li>Hybrid classical + post-quantum key exchange</li> +<li>Algorithm agility without hardware replacement</li> +<li>No mandatory external infrastructure</li> </ul> <p> -Security design prioritizes survivability, crypto agility, and rapid field updates -over static, hard-coded solutions. +Security design assumes persistent compromise attempts and prioritizes rapid +recovery and survivability over theoretical perfect secrecy. </p> </section> <section> -<h2>7. Network Topology Overview (SVG)</h2> +<h2>8. Network Topology Overview (SVG)</h2> <div class="diagram"> <svg viewBox="0 0 800 500" width="100%" height="auto"> <rect x="0" y="0" width="800" height="500" fill="#111820"/> -<circle cx="400" cy="100" r="40" fill="#1e88e5"/> -<text x="400" y="105" fill="#ffffff" text-anchor="middle">Gateway</text> +<circle cx="400" cy="90" r="40" fill="#1e88e5"/> +<text x="400" y="95" fill="#ffffff" text-anchor="middle">Gateway</text> -<circle cx="200" cy="250" r="35" fill="#43a047"/> -<circle cx="400" cy="300" r="35" fill="#43a047"/> -<circle cx="600" cy="250" r="35" fill="#43a047"/> +<circle cx="180" cy="250" r="35" fill="#43a047"/> +<circle cx="400" cy="320" r="35" fill="#43a047"/> +<circle cx="620" cy="250" r="35" fill="#43a047"/> -<line x1="400" y1="140" x2="200" y2="215" stroke="#90caf9"/> -<line x1="400" y1="140" x2="400" y2="265" stroke="#90caf9"/> -<line x1="400" y1="140" x2="600" y2="215" stroke="#90caf9"/> +<line x1="400" y1="130" x2="180" y2="215" stroke="#90caf9"/> +<line x1="400" y1="130" x2="400" y2="285" stroke="#90caf9"/> +<line x1="400" y1="130" x2="620" y2="215" stroke="#90caf9"/> -<line x1="200" y1="250" x2="400" y2="300" stroke="#90caf9"/> -<line x1="400" y1="300" x2="600" y2="250" stroke="#90caf9"/> +<line x1="180" y1="250" x2="400" y2="320" stroke="#90caf9"/> +<line x1="400" y1="320" x2="620" y2="250" stroke="#90caf9"/> -<text x="200" y="255" fill="#ffffff" text-anchor="middle">Node</text> -<text x="400" y="305" fill="#ffffff" text-anchor="middle">Node</text> -<text x="600" y="255" fill="#ffffff" text-anchor="middle">Node</text> +<text x="180" y="255" fill="#ffffff" text-anchor="middle">Node</text> +<text x="400" y="325" fill="#ffffff" text-anchor="middle">Node</text> +<text x="620" y="255" fill="#ffffff" text-anchor="middle">Node</text> </svg> </div> </section> <div class="footer"> -ARFHL Tactical Communications System – Open, Distributed, Survivable +ARFHL Tactical Communications System — Open, Distributed, Survivable, Scalable </div> </body> </html> - |