From: Joe Hamelin <nethead@gmail.com>
To: Hesham ElBakoury <helbakoury@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink
Date: Fri, 23 Jun 2023 06:09:56 -0700 [thread overview]
Message-ID: <CAO0-hXadKJNSvUV5jTszKCgBdhzWz8E3SH1cZaTr0BYfBJ0vbg@mail.gmail.com> (raw)
In-Reply-To: <09222329-da10-21c2-9905-0b9a23d86852@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf
Here's the PDF.
On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Has anyone looked at this paper (Signal Structure of the Starlink
> Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published in
> IEEE Transactions on Aerospace and Electronic Systems. Are there other
> research efforts which try to do the same?
>
> Thanks
>
> Hesham
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
--
Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
[-- Attachment #2: Type: text/html, Size: 1489 bytes --]
next prev parent reply other threads:[~2023-06-23 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <71psq926-osqr-70n0-264s-363162o77958@qbaryna.pbz>
[not found] ` <2d6314f0-1742-20c0-ab0d-7f5fcdf3809b@mtcc.com>
[not found] ` <CAAcrURLFkLKA3AG4SwRncgMEJ+4dDqKqtfidAXHFKqzGfRmc8Q@mail.gmail.com>
[not found] ` <c62ed36e-f552-c913-5d3e-ae2c925aa177@mtcc.com>
[not found] ` <84894b58-528a-a032-3f3d-a884f5b4a24f@tinka.africa>
[not found] ` <CAN9qwJ9whTOBk0puQYChPujBDHj8pYgfYLLo5hqkKZYDXcib_Q@mail.gmail.com>
[not found] ` <ae1cd18a-318a-6f92-7695-ab3dbc8ff815@tinka.africa>
[not found] ` <95633c24-c7c0-e0d9-3c74-d946acfccb41@mtcc.com>
[not found] ` <CAL9Qcx4BJQ6htQoRa_Rq1MaCdj56iV1FUAfHc4c4eU8XwH5LBQ@mail.gmail.com>
[not found] ` <cf5fc49f-3e75-92d9-ee4e-24ed33241d95@mtcc.com>
[not found] ` <CAL9Qcx5a=zbhs7pk=tWdZT42_ytz2StxPL8gNF6z6yOe6XRGxg@mail.gmail.com>
2023-06-17 23:08 ` [Starlink] FCC Chair Rosenworcel Proposes to Investigate Impact of Data Caps Dave Taht
2023-06-23 9:55 ` [Starlink] Signal Structure of the Starlink Ku-Band Downlink Hesham ElBakoury
2023-06-23 13:09 ` Joe Hamelin [this message]
2023-06-23 13:17 ` Joe Hamelin
2023-06-23 16:12 David Fernández
2023-06-23 16:14 ` Hesham ElBakoury
2023-06-23 16:50 ` contact
2023-06-23 16:56 ` David Fernández
2023-06-23 16:59 ` Hesham ElBakoury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO0-hXadKJNSvUV5jTszKCgBdhzWz8E3SH1cZaTr0BYfBJ0vbg@mail.gmail.com \
--to=nethead@gmail.com \
--cc=helbakoury@gmail.com \
--cc=joe@hamelin.us \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox