Maritime Rescue & Ship Squadron Communication Solution: 1.4G Mesh Anti-Multipath Beyond-Line-of-Sight Networking, 50–150km

Solution Overview: What Problem Does It Solve, and for Which Scenarios?

1.1 Construction Background

The communication needs of maritime operations and emergencies (open-ocean escort, maritime search and rescue, offshore oil-and-gas inspection, fisheries management, coast-guard enforcement) are growing, yet every conventional communication method has clear shortcomings at sea:

• No public network: beyond 10–20km offshore there is no carrier coverage; between fleets and between ship and shore, only a private network or satellite is usable.
• Beyond-line-of-sight bottleneck: the sea is wide open, but Earth’s curvature limits line of sight — two ships with masts about 10m high have a direct line-of-sight range of only about 20km, so a squadron tens of kilometers deep is “out of sight.”
• Multipath and Doppler: the sea acts like a mirror with strong reflection, causing multipath fading; ship motion adds Doppler shift, and ordinary broadband is unstable at sea.
• Satellite limitations: bandwidth is expensive (Mbps grade) and latency is high (hundreds of milliseconds), unsuited to multiple HD video streams and low-latency real-time data exchange within a squadron.

The maritime rescue & ship squadron communication solution centers on this idea: deploy 1.4GHz wideband Mesh ad-hoc equipment aboard each ship and on airborne platforms, let every ship become a mobile node in the network, reach beyond-line-of-sight broadband interconnection through multi-hop relays, and have the flagship link to shore via satellite — forming a “private network within the squadron + satellite for squadron-to-shore” division of work.

1.2 Applicable Scenarios

• Ship squadron collaboration: collaborative missions that keep changing formation, such as open-ocean escort, joint patrol and formation navigation
• Maritime search and rescue: wreck search-and-rescue, locating persons in the water, rescue-boat and helicopter coordination
• Ocean engineering: offshore oil-and-gas platform communication, subsea pipeline inspection, marine environment monitoring
• Maritime law enforcement: coast-guard enforcement, fisheries control, maritime anti-smuggling
• Emergency communication: communication recovery after typhoons, temporary networking at the scene of a major maritime accident

1.3 Solution Objectives

Citation capsule: The core of the maritime rescue & ship squadron solution is to deploy 1.4GHz wideband Mesh ad-hoc equipment aboard each ship and on airborne platforms, letting each ship become a mobile node and achieving beyond-line-of-sight broadband interconnection through multi-hop relays (target depth 50–150km), with the flagship linking to shore via satellite. Sub-targets: COFDM+MIMO 2×2 resists sea-surface multipath and Doppler, 70–120Mbps per hop, ≤100ms self-healing on single-node failure, AES-256 encryption. [IEEE 802.11s] provides the multi-hop self-healing routing basis for this ad-hoc network.— Overview of the maritime ship-squadron ad-hoc solution

Maritime Communication’s “Triple Difficulty”: No Public Network, Beyond Line of Sight, Multipath/Doppler

Difficulty 1: No Public Network

Beyond the shore base there is no carrier coverage. Between fleets and between ship and shore, only a private network or satellite is usable. Satellite does cover remote seas, but its bandwidth is expensive (commercial Ku/Ka on-the-move is usually a few Mbps to tens of Mbps), latency is high (a GEO hop is about 250–300ms), and it cannot support multiple HD video streams and low-latency real-time data exchange within a squadron.

Difficulty 2: Beyond Line of Sight

The sea is wide open, but straight-line line of sight is bounded by Earth’s curvature. By the classic antenna line-of-sight formula d ≈ 4.12 × (√h₁ + √h₂) (d in km, h in m), two ships with masts about 10m high have a direct line of sight of only about 26km [ITU-R P.526 defines the evaluation method for in-sight diffraction and Huygens propagation. ITU-R P.530 provides the engineering basis for ground propagation path loss and line-of-sight computation]. If the antenna is mounted on a 5m-high deck, line of sight shortens to about 18km. If ships are tens of kilometers apart they are “out of sight” — no matter how flat the sea is, the Earth is round.

Difficulty 3: Multipath/Doppler

The sea is like a mirror with strong reflection, causing multipath fading; ship motion adds Doppler shift, and ordinary broadband is unstable at sea. These three difficulties overlay to make the sea one of the most “treacherous” broadband communication environments.

What a ship squadron truly needs is a wideband private network that is free of terrestrial public networks, multipath-resistant, supports multi-hop beyond line of sight, and can flexibly come and go — precisely where ad-hoc networking finds its use at sea. It is not “stealing the satellite’s job” but dividing work with satellite: high-frequency video/data inside the fleet is carried on the private network, while slow aggregated cross-ocean / shore-bound traffic is given to satellite — each does its own job.

Citation capsule: The three difficulties of maritime broadband are: no public network (no carrier coverage 10–20km offshore), beyond line of sight (Earth’s curvature limits the view; two ships with masts 10m high have direct line of sight of only about 26km, per ITU-R P.526/P.530), and a weakened signal (sea-surface mirror reflection causes multipath fading, ship motion introduces Doppler shift). A ship squadron therefore needs a wideband private network that is free of public networks, multipath-resistant and supports multi-hop beyond line of sight, dividing work with satellite.— Maritime communication’s “triple difficulty” and the ad-hoc solution

The Physical Roots of Sea-Surface Multipath and Doppler: Why the Sea Is “More Treacherous” Than Land

Maritime communication difficulties concentrate at the physical layer and are “more treacherous” than on land because the sea has no buffer of any kind:

Multipath Fading: The Sea Is Like a Mirror

The sea surface is like a mirror; the direct wave and the reflected sea-surface wave superpose at the receiver. The phase difference between the two varies continuously with path difference, and peaks and troughs alternate to make the signal surge and fade — this is frequency-selective fading. The worse the sea state and the higher the waves, the more “fragmented” the reflecting surface and the more complex the fading; short deep fades can swallow an entire data block.

Unlike land multipath, the sea-surface reflection coefficient is extremely high (close to 0.9 on a calm sea); direct and reflected wave powers are similar, and fade depth can reach 20–40dB — far above the typical values of urban-land multipath. Thus the maritime link budget must reserve a larger fade margin.

Doppler Shift: Ship Motion + Antenna Rocking

Ships and airborne nodes move toward and away at high relative speed, “stretching” the frequency. At 1.4GHz, a relative speed of 30 knots (about 55km/h) produces a Doppler shift of about 72Hz; if two ships move toward each other it adds to roughly 144Hz. A rocking ship also keeps changing the antenna pointing, further magnifying frequency offset and gain jitter. Unless the system compensates effectively, carrier synchronization drifts and the bit-error rate spikes.

Fresnel Zone: Height Determines Distance

Beyond line of sight, raising the antenna height is the way to enlarge the effective link. The first-Fresnel-zone radius is inversely proportional to frequency — the 1.4GHz Fresnel-zone radius is about twice that of 5.8GHz, meaning the low band tolerates more sea-surface obstruction. Mast height and airborne height directly determine how far a single hop can cover.

Countermeasures: COFDM + Low Band + MIMO Diversity

The equipment series is built on COFDM + MIMO 2×2, using diversity combining to further hedge deep fading [ETSI EN 300 744][IEEE 802.11n], a natural fit for scenes where the signal is “shredded” at sea. By contrast, ordinary single-antenna OFDM or DSSS equipment tends toward “intermittent link loss” under sea-surface deep fading, while the COFDM + MIMO combination compresses the “link-loss probability” to an engineering-acceptable level.

Citation capsule: Why sea-surface multipath and Doppler are “more treacherous” than on land: on a calm sea the reflection coefficient is close to 0.9, direct and reflected wave powers are similar, and deep fading can reach 20–40dB; at 1.4GHz a 30-knot relative speed produces a Doppler shift of about 72Hz, compounding to about 144Hz on approaching courses. Countermeasures are COFDM subcarrier diversity + cyclic prefix (ETSI EN 300 744) absorbing multipath delay, MIMO 2×2 (IEEE 802.11n) hedging deep fading, and the 1.4GHz low band lengthening the symbol period for higher Doppler tolerance.— Physical roots of sea-surface multipath/Doppler and countermeasures

Band Selection Comparison: Why 1.4G Is the Optimal Choice for a Maritime Private Network

Conclusion: 1.4GHz is comprehensively optimal across the five dimensions of “coverage distance, diffraction capability, Doppler tolerance, multipath resistance and no infrastructure dependency.” 5G and satellite each have their place, but 5G covers only near-shore areas and depends on shore stations, while satellite has high latency and expensive bandwidth — they complement, not replace, 1.4G Mesh. Commercial projects are recommended to adopt the “1.4G Mesh primary + 5G/satellite secondary” hybrid backup model.

Citation capsule: 1.4GHz (wavelength about 21cm) is the optimal maritime private-network band: versus the 2.4G/5.8G civil bands (power-limited by FCC 47 CFR Part 15, wavelengths 12/5cm) it has larger sea-surface diffraction and Fresnel-zone radius and a longer symbol period, hence higher Doppler tolerance; versus 5G public (near-shore only, depends on shore stations) and satellite (latency 250–600ms, expensive bandwidth) it is infrastructure-free, offers 70–120Mbps, and 30–120ms latency. Recommended: the “1.4G Mesh primary + 5G/satellite secondary” hybrid backup model.— The 1.4G maritime private-network band-selection basis

Link Budget and Coverage Analysis: How Far Can a Single Hop Reach?

Line-of-Sight Calculation

Sea-surface line of sight is bounded by Earth’s curvature; the classic formula is d ≈ 4.12 × (√h₁ + √h₂) (d in km, h in m) [ITU-R P.526][ITU-R P.530].

Link Budget Estimate (1.4GHz, P1 to P1)

Conclusion: at 1.4GHz the P1-to-P1 link can retain about 4dB margin over a 15km single hop on the sea surface, meeting the engineering usability threshold. With a directional high-gain antenna (e.g., 12dBi), coverage rises to 20–25km. When the airborne P2 lifts to 100–300m, line of sight and link margin improve together, extending a single hop to 30–50km.

Citation capsule: The link budget determines the maritime single-hop range: taking the 1.4GHz P1-to-P1 link, a 2W transmit (33dBm) plus dual 6dBi antennas yields a system gain of 45dBm; subtracting the -95dBm receiver sensitivity gives an allowable path loss of 140dB; the 15km free-space loss is about 119dB, and after deducting a 15dB sea-surface multipath margin + 2dB feed loss only about 4dB remains. A 12dBi directional antenna extends reach to 20–25km, and the airborne P2 lifted to 100–300m reaches 30–50km per hop (line-of-sight formula per ITU-R P.526/P.530).— Maritime single-hop link budget and coverage analysis

Ship Squadron Networking Architecture: How to Achieve a Three-Layer Structure and Full-Network Self-Healing

The flagship deploys the P3 platform as the squadron center, each escort ship deploys a P1 backpack node, and a ship-based UAV (P2) takes off as a high-point relay. The airborne node stands out in “high point + flexible gap-filling”: when an escort ship is occluded by an island or a large hull, the P2 rises above the mast to break the geometric occlusion and bring the blocked ship into the network. Should the link between any two ships fail, data automatically routes around through other ships to rebuild the path — the squadron network “has no single point of failure,” precisely the maritime embodiment of ad-hoc self-healing [IEEE 802.11s defines the multi-hop routing and self-healing mechanism of a wireless Mesh]. Even if one ship’s radio fails outright, the network simply skips that node, the remaining ships continue to interconnect, and the squadron’s overall command is unaffected.

Fig. 1 | 1.4G Mesh for a remote-sea squadron: each ship deploys P1/P3 nodes meshing into one self-healing network, the P2 UAV lifts off between ships as a beyond-line-of-sight high-point relay, and the flagship command-cabin screen presents the entire squadron topology at a glance.

Citation capsule: Ship squadron networking is a three-layer structure with “one node per ship and full-network self-healing”: the flagship uses the P3 as the coordination hub and links to shore via satellite, each escort ship deploys a P1 backpack node that auto-meshes and mutually relays, the ship-based UAV P2 lifts off as a beyond-line-of-sight high point, and rescue boats/soldiers access at the edge via P5. When the link between any two ships fails, data routes around automatically through other ships to rebuild the path (IEEE 802.11s multi-hop self-healing), with no single point of failure and no central dependency; a single-node failure self-heals in ≤100ms.— The three-layer three-dimensional squadron networking architecture

How Near-Sea and Far-Sea Relay Extends Reach to 50–150km

At sea there is no mountain occlusion, but Earth’s curvature limits single-hop line of sight. The solution is the multi-hop link — every hop is bounded by “height” and “distance,” and stringing links together crosses beyond-line-of-sight depth:

In practice, the combination of “ship-to-ship + ship-to-aircraft + aircraft-to-shore” connects a squadron tens of kilometers deep into one network, far more than any single device’s straight-line coverage. It should be noted that depth extension costs bandwidth: each hop splits off part of the end-to-end bandwidth, so in a deep network the “backbone backhaul” should take the shortest reliable path, and high-flow services such as HD video should avoid crossing too many hops.

Citation capsule: With no mountain occlusion but single-hop line of sight limited by Earth’s curvature, “multi-hop relay” turns single-hop coverage into deep coverage: near shore use 0–30km ship–buoy–shore multi-stage point-to-point, mid-to-far sea 30–80km use 4–6 escort ships relaying ship by ship (10–15km × 4 hops ≈ 40–60km), and far sea 80–150km have the P2 airborne lift above 300m to stretch a single-hop line of sight to 50–80km as a “high-altitude springboard.” The trade-off: each hop splits off end-to-end bandwidth, so the backbone backhaul should take the shortest reliable path.— Near-sea and far-sea multi-hop relay extending to 50–150km

Flagship Coordination and Shore Connectivity: How Do the Private Network and Satellite Divide Work?

Maritime emergency response and command usually have two layers: real-time collaboration within the squadron + data linkage with the shore command center. The ad-hoc network covers the former, satellite/public network covers the latter, and the flagship becomes the convergence point of both and the squadron’s sole “external exit”:

Satellite carries only one “uplink” aggregated stream; dozens of HD streams inside the squadron stay on the private network, minimizing cost and bandwidth. The flagship’s value is not merely “accessing satellite” but “situation aggregation + unified exit”: it converges the raw data of 64 nodes into a single situation map reportable to shore, so the shore command center sees not 64 isolated streams but one picture of the entire squadron.

Data security: integration with cipher machines/encryption is supported, and AES-256 encryption protects sensitive video and commands within the squadron, guarding against private-network disclosure. The squadron is both a “closed ad-hoc network” and an “open offshore node,” combining both benefits.

Citation capsule: Maritime command adopts the “within-squadron private network + squadron-to-shore satellite” division of work: the 1.4G Mesh ad-hoc network carries HD video, position, command and situational data among 64 nodes within the squadron (70–120Mbps, 30–120ms); the shipborne satellite (Ku/Ka) carries only one aggregated situation uplink to shore (1–10Mbps, 250–600ms); 4G/5G acts as backup when near-shore coverage exists. The flagship is the “convergence point” of the two networks, converging 64 raw streams into one reportable situation map and applying AES-256 encryption to sensitive services.— Flagship coordination and the private-network + satellite division model

Two Topologies for Rescue/Squadron: Hub-and-Spoke or Chain/Mesh?

Mature ship-squadron ad-hoc solutions in the industry (such as the Tengyuan-Zhizhuo ship-squadron case, Jixiang Technology, and public ship/ocean-industry designs) generally adopt the “flagship + escort ships + airborne high point + satellite-to-shore” architecture, where the failure of any single node does not affect the squadron network. This solution differs by sinking the “backpack/handheld 1.4G Mesh” down to each ship and each rescue edge, so every ship and every rescue point can become a mobile node in the network rather than relying only on large shipborne stations — lower cost, faster deployment and broader coverage.

Citation capsule: Maritime networking divides into two topologies by mission objective: rescue leans toward “hub-and-spoke” (command ship centered, rescue boats/UAVs/edges converging, P3 dispatching at center, few hops and low latency), while squadron collaboration leans toward “chain/mesh” (ships as mutual nodes, flagship coordinating, airborne gap-filling, multi-hop data relay; when the squadron changes formation the nodes move with the ships and ad-hoc routing re-selects automatically without manual intervention). Mature industry solutions generally adopt the “flagship + escort ships + airborne high point + satellite-to-shore” architecture, and this solution further sinks the 1.4G Mesh down to each ship and each rescue edge.— Rescue hub-and-spoke vs squadron chain/mesh topology

Service Carriage: How Is Multi-Service QoS Prioritized?

Citation capsule: The whole maritime network carries services by priority class: control signaling (navigation/squadron/emergency alarms) gets the highest priority <200ms, video services (shipborne electro-optical/IR, rescue-scene feeds) high priority 30–150ms, situational data (AIS position/speed/SNR/radar) and voice dispatch medium priority 100–500ms, and extended services (weather/monitoring/file) low priority non-real-time. QoS tiering ensures that control signaling and critical video are protected first when the sea state degrades or the network congests.— Maritime multi-service QoS-tiered carriage

Key Technical Specifications

Maritime Deployment Essentials: Antennas, Protection, Power and O&M

Notes

• Waves and motion: ship rocking makes antenna pointing jitter on top of Doppler; COFDM + diversity should be used to stabilize the link, and critical nodes should be shock-mounted.
• Multi-hop bandwidth: far-sea multi-hop splits end-to-end bandwidth; plan the shortest reliable path for important services, and route HD video preferentially over the backbone direct link.
• Electromagnetic compatibility: a ship carries radar, navigation and satellite-communication RF equipment; an EMC assessment is needed to avoid co-channel/adjacent-channel interference. The 1.4GHz private band does not overlap common shipborne radar bands, so interference risk is low.
• Band compliance: 1.4GHz is a licensed private network band; maritime use requires station-registration procedures per maritime and radio-management regulations.

Citation capsule: Maritime deployment is four things: antenna installation — raise to the mast top for better Fresnel-zone clearance, use ship-based UAV/buoy nodes to fill critical blind zones, and choose omnidirectional vertically polarized or directional high-gain antennas per the link budget; salt-spray protection — salt-spray-resistant device design (IP67, IEC 60529), anti-corrosion sealing tape on antenna connectors, dehumidification in the cabinet against condensation; power redundancy — preferentially ship power 220V/24V plus a separate battery, the P1’s own 25.2V/10.5Ah battery for 6–12h, a voltage regulator against ship-power transients; O&M monitoring — real-time per-hop SNR/bandwidth/topology via MESHCOM/WEB, and ad-hoc routing re-selects automatically when the squadron changes formation.— Maritime deployment essentials and O&M

What Risks Arise When Building a Maritime Network, and How to Solve Them?

Citation capsule: Main risks and countermeasures of a maritime ad-hoc network: multipath deep fading → COFDM subcarrier diversity + cyclic prefix (ETSI EN 300 744) + MIMO 2×2 (IEEE 802.11n) hedging, with a 15–25dB margin in the link budget; Doppler shift → long symbol period at low band + automatic frequency-offset compensation; limited beyond-line-of-sight → multi-hop relays + airborne lift above 300m stretching a single hop to 50–80km; salt-spray corrosion → IP67 (IEC 60529) protection and routine maintenance; multi-hop bandwidth loss → keep hops ≤ 4 and use directional backbone antennas; electromagnetic interference → 1.4GHz does not overlap shipborne radar bands + automatic spectrum-sensing hopping.— Maritime ad-hoc network risks and countermeasures

What Is the Solution’s Evolution Path?

• Communication-sensing integration: the communication payload simultaneously enables sea-surface target radar detection and AIS signal fusion sensing, achieving “communication + situational awareness” in one
• AI intelligent networking: auto-computing optimal relay positions, dynamic RF power adjustment, and predicting link interruption to adjust squadron formation in advance
• Sky-sea-space fusion: UAV Mesh + low-orbit satellite constellation (Starlink/China SatNet) + sea-surface buoy network with full-domain heterogeneous interconnection
• USV collaboration: incorporating unmanned surface vessels (USVs) into the Mesh network to extend communications coverage for maritime patrol and search-and-rescue

Frequently Asked Questions (FAQ)

References

1. Tengyuan-Zhizhuo ship-squadron case study, Jixiang Technology and public ship/ocean-industry solutions (ship-squadron Mesh networking, near-sea ship–buoy–shore multi-stage point-to-point, far-sea multi-hop relay of 50–150km).
2. International Maritime Organization (IMO): the Maritime Search and Rescue Communications Standard and related GMDSS regulations.
3. Public technical material on COFDM’s resistance to sea-surface multipath and Doppler (related papers in IEEE Journal of Oceanic Engineering).
4. Maritime emergency/maritime-search-and-rescue and coast-guard UAV ad-hoc applications industry material.
5. Equipment-manufacturer datasheets (YNWMicro P1/P2/P3/P5 ad-hoc equipment maritime application parameters).
6. Ministry of Emergency Management (China): regulations and operational news on maritime search-and-rescue and emergency communication support.
7. ITU – International Telecommunication Union: standards for maritime radiocommunication and GMDSS radio planning.

Standard-reference notes

• [IEEE 802.11s]: defines the multi-hop routing and self-healing mechanism of a wireless Mesh ad-hoc network (the basis for “one node per ship, full-network self-healing” and single-node-failure route rebuild in this article).
• [IEEE 802.11n]: defines the MIMO multi-antenna technique (the basis for MIMO 2×2 spatial diversity countering sea-surface deep fading in this article).
• [ETSI EN 300 744]: the European telecommunications standard defining COFDM/orthogonal frequency-division multiplexing and the cyclic prefix (CP) (the basis for COFDM subcarrier diversity and CP absorbing multipath delay in this article).
• [ITU-R P.526]: the ITU evaluation method for diffraction in radio-wave propagation (the basis for sea-surface line-of-sight diffraction, crossing obstacles, and antenna height affecting coverage radius in this article).
• [ITU-R P.530]: the ITU engineering basis for ground propagation path loss and line-of-sight computation (the basis for the “d≈4.12×(√h₁+√h₂)” line-of-sight formula and link budget in this article).
• [FCC 47 CFR Part 15]: US federal regulations capping the transmit power of license-exempt civil bands (2.4G/5.8G ISM) (the basis for band power and compliance comparisons in this article).
• [IEC 60529]: the international standard defining IP protection ratings (IP65/IP67/IP66) (the basis for the devices’ salt-spray resistance and protection ratings in this article).