<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="auto">What an informative post! Engrossing material. </div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
"Dark Magic".</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
Also: was early commercial adopter of 8PSK TCM service on 6.4-6.7/3.4-3.7 GHz. A company I was a partner in had contracts for many 3-3.7m VSAT systems, 64k-8M/64k-45M with 5W to 40W SSPA. We occupied close to a full 36 MHz transponder at 88E. </div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
Any EIRP estimates for TX ground and TX spacecraft at this stage for the required BER? Is the target to be greater or less than QO-100?</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
Since we will be GEO graveyard, what is our bounding box and fade margins at the boundaries? </div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
<br>
</div>
<div dir="auto" style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);">
Samudra N3RDX</div>
<div><br>
</div>
<div id="ms-outlook-mobile-signature" dir="auto">Sent via the Samsung Galaxy S21 5G, an AT&T 5G smartphone<br>
Get <a href="https://aka.ms/AAb9ysg">Outlook for Android</a></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Ground-Station <ground-station-bounces@lists.openresearch.institute> on behalf of Michelle Thompson via Ground-Station <ground-station@lists.openresearch.institute><br>
<b>Sent:</b> Saturday, July 2, 2022 9:49:32 AM<br>
<b>To:</b> Michelle Thompson via Ground-Station <ground-station@lists.openresearch.institute><br>
<b>Subject:</b> [Ground-station] Adapting M17 Protocol to Phase 4 Opulent Voice uplink</font>
<div> </div>
</div>
<div>
<div dir="ltr">Greetings all!<br>
<br>
Here's an update on the uplink. <br>
<br>
Paul KB5MU writes "We’ve concluded that there’s no good reason to keep the code puncturing from M17. As best we can tell, they used puncturing in order to fit their 3200 bit per second voice codec into a conservative 9 kHz channel width. We are aiming at a
wider channel that has no existing channelization to be compatible with, and we could use the better performance of an unpunctured code. If you see a flaw in this reasoning, speak now to save the puncturing.<br>
<br>
There’s also a design decision to be made on the uplink interleaver. M17 uses a particular quadratic polynomial interleaver. I’m not sure I understand why."<br>
<br>
For those curious about puncturing, it’s used in a variety of ways.<br>
<br>
What is puncturing in the first place? It’s either deliberately not sending a symbol (the smallest unit of information in digital RF signals. A symbol stands for some number of bits of data) or it is the practice of replacing a symbol with some other data to
make a sub-channel.<br>
<br>
An example of using puncturing to put in other data is in IS-95, where ever so often, power control commands (up or down) were inserted into the transmitted signal by overwriting a symbol.
<br>
<br>
This achieved power control, which is one way to make CDMA much more efficient.<br>
<br>
When you have puncturing with convolutional coding, it’s almost always used to manipulate the code rate. The code rate is the ratio between the data in to the convolutional encoder and the data coming out of the encoder, which is then sent over the air after
the data is mapped to symbols. <br>
<br>
For the convolutional encoder used in M17, it’s 1 bit in and 2 bits out, for a code rate of 1/2. If you puncture, or remove a symbol ever so often, then the resulting signal transmitted over the air has a higher code rate. This means you get a higher data rate
- the number on the top of the fractional code rate valule. <br>
<br>
M17 has 2/3 code rate (0.666) instead of 1.2 (0.5) because of puncturing.<br>
<br>
We know that to get something in physics or engineering you have to give up something. That is true here as well. Higher code rates mean worse performance at lower signal to noise ratios.Since VHF/UHF ham comms are almost always done at high power, it doesn’t
matter much. The vast majority of M17 communications is done with internet links and reflectors, where puncturing is not a factor. Repeaters are generally deployed in a way where the hit to performance from puncturing is not anywhere close to the top item
of concern. Anyone accustomed to analog repeaters will notice a performance difference in an M17 repeater, as analog gracefully deteriorates while M17 will fall off a cliff a bit earlier with puncturing than without it.<br>
<br>
The primary purpose of puncturing in this protocol is to reduce the number of bits down to the frame size required by the use of CODEC2 3200 bps frames.<br>
<br>
M17 is completely devoted to CODEC2 3200 codec. Everything in the protocol is hard-coded to that particular codec.<br>
<br>
Since we do not have to use such a low-rate codec, and definitely do not want to use such a low rate codec due to the voice quality, we have to rewrite the protocol. M17 is forced to because of datarate limitations for VHF/UHF. <br>
<br>
We use a minimum of 16 kpbs OPUS. We don't have the same regulatory limits for microwave communications. As a side effect of this work, we will be demonstrating terrestrial microwave HTs. <br>
<br>
The interleaver is another story. There’s no multipath at VHF/UHF in the same sense that we have for broadband microwave. Interleaving is required to make a convolutional coding system work to its best ability. Multipath is the source of most burst errors.
Burst errors are what interleavers, in general, are used to resolve.<br>
<br>
The way we’ve seen this described is that convolutional encoders are designed for memoryless channels. Multipath introduces errors with memory. <br>
<br>
Rearranging the bits to give space between errors (scrambling or interleaving) turns a channel with memory into the memoryless channel that convolutional encoders really want.<br>
<br>
Since there are no significant burst errors for a 9kHz signal at VHF/UHF, the interleaver doesn’t have much to do. Except one thing - provide an excellent opportunity for education. The greatest value of M17 is quite possibly as a protocol that is easy to use
over the air in educational settings. It has block coding, convolutional coding, puncturing, and interleaving. While the vast majority of M17 is lifted from P25 (like all the ham digital voice modes) it does simplify things compared to DMR.<br>
<br>
The downside to using an interleaver is delay.<br>
<br>
You also have to have storage.<br>
<br>
You want to guarantee that X symbols are separated by at least Y symbols, then you do have to buffer things up or at least hold certain symbols for their spot in a shift register with a commutator.<br>
<br>
While there is not a whole lot of burst error problems at VHF/UHF, there are definitely multipath issues for microwave broadband terrestrial applications.<br>
<br>
So yes, I think we will need an interleaver for Opulent Voice. But, do we need the one that M17 selected? Quadratic Permutation Polynomials are used in a variety of places, like LTE, for turbo codes.<br>
<br>
We need to look at this QPP and figure out whether it’s overkill or not for what is actually encountered on microwave bands.<br>
<br>
The basic idea from QPP is there’s a linear term that distorts the symbol stream, and then a quadratic term that provides finer “ripples”.<br>
<br>
The classic way of doing interleaving is lining all the symbols up in a matrix and re-distributing rows and columns. You pick how many symbols in a row you want to guarantee separation, and how far apart those symbols must at a minimum now be.<br>
<br>
We can afford quite a bit of hardware here, but the real question is how much latency.<br>
<br>
Comments and questions are welcomed and encouraged.<br>
<br>
-Michelle Thompson<br>
<br>
<br>
</div>
</div>
</body>
</html>