summaryrefslogtreecommitdiffstats
path: root/index.html
blob: e93681527b78d0cfab5f989200a4996aa01c2e6b (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>ARFHL Tactical Wi-Fi HaLow Mesh Network</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<style>
body {
    font-family: Arial, Helvetica, sans-serif;
    margin: 0;
    background-color: #0f1419;
    color: #e6e6e6;
    line-height: 1.6;
}
header {
    background: linear-gradient(135deg, #1b2633, #0f1419);
    padding: 40px;
}
header h1 {
    margin: 0;
    font-size: 2.4em;
}
header p {
    max-width: 900px;
    color: #cfd8dc;
}
section {
    padding: 40px;
    max-width: 1200px;
    margin: auto;
}
h2 {
    border-bottom: 2px solid #2e3b4a;
    padding-bottom: 8px;
}
h3 {
    color: #90caf9;
}
table {
    width: 100%;
    border-collapse: collapse;
    margin-top: 20px;
}
th, td {
    border: 1px solid #2e3b4a;
    padding: 10px;
    text-align: left;
    vertical-align: top;
}
th {
    background-color: #1b2633;
}
ul {
    margin-left: 20px;
}
.badge {
    display: inline-block;
    background-color: #263238;
    padding: 4px 10px;
    margin: 4px 0;
    border-radius: 4px;
    font-size: 0.85em;
}
.footer {
    background-color: #0b0f14;
    padding: 20px;
    text-align: center;
    font-size: 0.85em;
    color: #9e9e9e;
}
.diagram {
    background-color: #111820;
    padding: 20px;
    margin: 20px 0;
    border: 1px solid #2e3b4a;
}
.note {
    background-color: #1a222b;
    padding: 15px;
    border-left: 4px solid #90caf9;
    margin: 20px 0;
}
</style>
</head>

<body>

<header>
<h1>ARFHL Tactical Wi-Fi HaLow Mesh Network</h1>
<p>
A distributed, sub-GHz tactical communications backbone designed for contested,
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">Distributed Mesh</span>
<span class="badge">Post-Quantum Ready</span>
<span class="badge">Open IP Backbone</span>
</header>

<section>
<h2>1. Product Description</h2>

<p>
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>
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>Technical Summary</h3>
<table>
<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>&gt;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. Doctrine-Aligned Use Cases</h2>

<h3>Platoon Level (0–2 km)</h3>
<ul>
<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>Company Level (2–10 km, multi-hop)</h3>
<ul>
<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>Battalion Level (Distributed)</h3>
<ul>
<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>4. Device Management and Lifecycle Control</h2>

<h3>Device Management</h3>
<ul>
<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>Firmware and Configuration</h3>
<ul>
<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>Capture and Compromise Handling</h3>
<ul>
<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>5. Costed BOM and Unit Economics (Indicative)</h2>

<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>Target unit production cost: &lt; 200 EUR</li>
<li>Indicative procurement price: low hundreds EUR</li>
<li>Order-of-magnitude cheaper than SDR-based tactical radios</li>
</ul>

<div class="note">
Cost structure enables mass deployment and attrition tolerance,
not boutique low-volume procurement.
</div>
</section>

<section>
<h2>6. Manufacturing Readiness and Scaling</h2>

<table>
<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>7. Security Architecture</h2>

<ul>
<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 assumes persistent compromise attempts and prioritizes rapid
recovery and survivability over theoretical perfect secrecy.
</p>
</section>

<section>
<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="90" r="40" fill="#1e88e5"/>
<text x="400" y="95" fill="#ffffff" text-anchor="middle">Gateway</text>

<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="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="180" y1="250" x2="400" y2="320" stroke="#90caf9"/>
<line x1="400" y1="320" x2="620" y2="250" stroke="#90caf9"/>

<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, Scalable
</div>

</body>
</html>