<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research | Shaojian Yang</title><link>https://www.sjyang.top/category/research/</link><atom:link href="https://www.sjyang.top/category/research/index.xml" rel="self" type="application/rss+xml"/><description>Research</description><generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><image><url>https://www.sjyang.top/media/icon_hu0b7a4cb9992c9ac0e91bd28ffd38dd00_9727_512x512_fill_lanczos_center_3.png</url><title>Research</title><link>https://www.sjyang.top/category/research/</link></image><item><title>Receiverless Underwater Telemetry with Submarine Cables</title><link>https://www.sjyang.top/post/das-underwater-communications/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.sjyang.top/post/das-underwater-communications/</guid><description>&lt;p>&lt;strong>Language:&lt;/strong> English | &lt;a href="https://www.sjyang.top/zh/post/das-underwater-communications/">中文&lt;/a>&lt;/p>
&lt;p>Underwater communication is usually introduced through familiar technical limits: bandwidth is narrow, sound propagation is slow, multipath is messy, and Doppler spread is hard to tame. My doctoral dissertation started from an even more basic difficulty: sometimes the receiver is simply not there.&lt;/p>
&lt;p>An autonomous underwater vehicle can spend hours or days collecting valuable data during ecological surveys, environmental monitoring, deep-sea exploration, or subsea infrastructure inspection. But the data only becomes useful if it can get back to shore in time. In remote oceans, deep water, polar regions, and surface-restricted missions, a relay buoy, a ship, a seabed hydrophone, or a fixed cabled station may be too expensive, too visible, too fragile, or unavailable.&lt;/p>
&lt;p>That is the problem behind the word &amp;ldquo;receiverless&amp;rdquo; in my dissertation. It does not mean communication without physics. It means communication when the usual receiving infrastructure cannot be assumed.&lt;/p>
&lt;p>My PhD dissertation, &lt;em>Research on Underwater Acoustic Communications Based on Unconventional Receivers for Data Backhaul&lt;/em>, explored two ways to create a receiving path from things that were not originally designed as underwater acoustic receivers:&lt;/p>
&lt;ol>
&lt;li>An airborne microphone on an unmanned aerial vehicle, listening after an underwater acoustic signal crosses the water-air interface.&lt;/li>
&lt;li>A submarine optical-electric cable, interrogated by distributed acoustic sensing (DAS), acting as a long distributed acoustic receiver.&lt;/li>
&lt;/ol>
&lt;p>This post focuses on the second route. It connects directly to my 2021 paper, &lt;a href="https://doi.org/10.1109/JSEN.2021.3115581" target="_blank" rel="noopener">&lt;em>Channel Distribution and Noise Characteristics of Distributed Acoustic Sensing Underwater Communications&lt;/em>&lt;/a>, and to the later cable-assisted communication framework in my dissertation.&lt;/p>
&lt;h2 id="turning-a-cable-into-a-receiver">Turning a cable into a receiver&lt;/h2>
&lt;p>The idea is simple to state: let the cable listen.&lt;/p>
&lt;p>A DAS system sends coherent optical pulses into an optical fiber and measures phase changes in the Rayleigh backscatter. When an external acoustic wave shakes the cable, it creates tiny strain variations along the fiber. Those variations appear in the optical return. In effect, a long fiber can become a dense line of sensing channels.&lt;/p>
&lt;p>This is attractive because submarine cables already cross large ocean regions. Many optical-electric cables also include fibers that can be accessed from shore. If a DAS interrogator is connected to such a fiber, the cable can become a passive acoustic receiving array without deploying a separate hydrophone on the seabed.&lt;/p>
&lt;p>But there is a catch. A DAS cable does not hear the ocean the way a hydrophone does. A hydrophone records pressure at a point. A cable-based DAS receiver records strain over fiber sections after the signal has passed through water, sediment, cable structure, and optical sensing hardware. Chapter 4 of my dissertation therefore treated the received signal as a cascade:&lt;/p>
&lt;ul>
&lt;li>acoustic propagation in water,&lt;/li>
&lt;li>coupling through the seafloor or cable environment,&lt;/li>
&lt;li>mechanical response of the cable,&lt;/li>
&lt;li>conversion from cable strain to optical phase variation.&lt;/li>
&lt;/ul>
&lt;p>That cascade is the reason the channel study matters. Before designing a modem around a submarine cable, we need to know what the cable actually hears.&lt;/p>
&lt;h2 id="what-the-2021-experiment-showed">What the 2021 experiment showed&lt;/h2>
&lt;p>The field experiment used a lightweight protected armored optical-electric cable in Mulan Lake. A transducer was suspended from a boat about 2 m below the surface. The cable lay on the lakebed and was connected to a shore-based DAS device. We transmitted several acoustic waveforms, including LFM, BASK, MFSK, QPSK, and OFDM signals, at distances from 1 m to 1000 m.&lt;/p>
&lt;p>Three observations from that work continued to shape my later research.&lt;/p>
&lt;p>First, the DAS channel did not follow the simplest textbook assumptions. The envelope amplitudes of the measured impulse responses were better fitted by a Burr distribution than by Rayleigh or normal distributions. The source position also mattered: when the transmitter moved closer to the region above the cable, the received energy became more concentrated.&lt;/p>
&lt;p>Second, neighboring cable sections were not independent clean channels. Vibration could couple along the cable, so a signal recorded at one section could include contributions from nearby sections. This produced additional arrivals and affected the effective delay spread. In QPSK measurements, the estimated maximum delays were about 9.9 to 13.8 ms, with roughly 12 to 14 effective taps.&lt;/p>
&lt;p>Third, the background noise was not just ordinary ocean noise. Below 1 kHz, the DAS noise power spectral density decreased at about 18 dB per octave, mainly shaped by the equipment and cable system rather than only by shipping or wind. The noise also fluctuated across time, frequency, and sensing channel. A receiver designed for a hydrophone noise model would miss part of the problem.&lt;/p>
&lt;p>The important conclusion was not that the cable behaves like an ideal hydrophone. It does not. The useful conclusion was that the cable still carries recoverable communication information, as long as the receiver is designed for the channel it actually observes.&lt;/p>
&lt;h2 id="from-channel-study-to-communication-loop">From channel study to communication loop&lt;/h2>
&lt;p>Chapter 5 of my dissertation asked the next question: if a submarine optical-electric cable can receive data from an AUV, can it also help complete a two-way communication loop?&lt;/p>
&lt;p>For the uplink, the answer was acoustic-to-optical. The AUV transmits an acoustic packet; the cable senses the vibration through DAS; the shore station demodulates the signal from the optical return. In a lake-trial uplink system, a QPSK signal at a 5 kHz carrier occupied about 3660 Hz of bandwidth and achieved an effective packet data rate of about 2628 bps. The DAS signal had much lower SNR than a nearby hydrophone, but it was still usable.&lt;/p>
&lt;p>For the downlink, the dissertation introduced a complementary magnetic route. A shore station injects a modulated low-frequency current into the copper conductor of an optical-electric cable. The current creates a magnetic field near the cable. A high-sensitivity NV-center diamond magnetometer carried by the underwater platform can detect the field and recover low-rate commands. In the sea trial, an MFSK downlink used 16 tones from 27 Hz to 477 Hz with a symbol duration of 0.5 s, achieving about 7.2 bps.&lt;/p>
&lt;p>The two links are asymmetric, but they fit the mission:&lt;/p>
&lt;ul>
&lt;li>acoustic-optical uplink for returning data from AUV to shore,&lt;/li>
&lt;li>electric-magnetic downlink for sending commands from shore to AUV.&lt;/li>
&lt;/ul>
&lt;p>This is the broader architecture behind the framework diagram. A submarine cable is no longer only a data pipe. It can also act as a distributed acoustic receiver, a magnetic transmitter, and a physical reference line for underwater systems.&lt;/p>
&lt;h2 id="why-this-still-feels-important">Why this still feels important&lt;/h2>
&lt;p>The 2021 DAS channel paper did not solve the entire telemetry problem by itself. Its value was more foundational: it clarified what a cable-based receiver hears, how different that observation is from a hydrophone recording, and what kind of channel and noise structure a modem must face.&lt;/p>
&lt;p>The later dissertation work built on that foundation and moved from &amp;ldquo;Can the cable hear an acoustic signal?&amp;rdquo; to &amp;ldquo;Can the cable help an AUV return data when ordinary receiving infrastructure is missing?&amp;rdquo;&lt;/p>
&lt;p>For me, that shift is the exciting part. Instead of asking only how to deploy more receivers in the ocean, we can ask a more flexible question:&lt;/p>
&lt;p>What existing infrastructure can already receive something useful, if we learn how to listen?&lt;/p>
&lt;h2 id="sources-and-related-pages">Sources and related pages&lt;/h2>
&lt;ul>
&lt;li>Paper DOI: &lt;a href="https://doi.org/10.1109/JSEN.2021.3115581" target="_blank" rel="noopener">https://doi.org/10.1109/JSEN.2021.3115581&lt;/a>&lt;/li>
&lt;li>PhD dissertation source: Chapters 1, 4, and 5 of my doctoral thesis&lt;/li>
&lt;li>Google Scholar profile: &lt;a href="https://scholar.google.com/citations?hl=en&amp;amp;user=KvxU4p4AAAAJ" target="_blank" rel="noopener">https://scholar.google.com/citations?hl=en&amp;user=KvxU4p4AAAAJ&lt;/a>&lt;/li>
&lt;li>ResearchGate profile: &lt;a href="https://www.researchgate.net/profile/Shaojian-Yang" target="_blank" rel="noopener">https://www.researchgate.net/profile/Shaojian-Yang&lt;/a>&lt;/li>
&lt;/ul></description></item></channel></rss>