1. Link 17 AFAIK uses TDMA like Link 16 but may incorporate limited mesh or dynamic slot allocation concepts. No indication it uses CDMA.
2. Bandwidth is likely comparable or slightly higher than Link 16, but not enough for full raw radar data. Missile guidance would need much more.
3. To guide PL-15 from Erieye, Link 17 would need at least 10 Mbps and sub-millisecond latency plus synchronized processors. Unlikely in current form.
4. It could enable limited networked targeting with heavily pre-processed tracks. Main barriers are latency, bandwidth, and lack of unified processing.
5. integration is not the problem. bandwidth is.
6. A hybrid model is possible but would still fall short of CEC. Would need new hardware, CEPs, and a real-time DDS-like system.
7. Today it’s likely used for situational awareness, basic targeting, and track sharing. Not yet capable of true offboard fire control.
8. Incorporating Chinese data link tech is more feasible than Swedish. Would be more seamless but would still require deep integration across systems. However, PAF prefers proprietary systems which begs the question - perhaps the PAF has done some upgrades and implemented something new which is not declared
@arslank01
9. To handle high-speed targets, Link 17 would need updates every 50–100 ms. Dwell-by-dwell updates would need a completely new architecture.
10. Solid proof would be raw radar sharing, CEP presence, and identical fused track files across platforms. Only US, China and select allies have CEC-like nets today.