Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Hesham ElBakoury <helbakoury@gmail.com>
To: contact@olegkutkov.me
Cc: "David Fernández" <davidfdzp@gmail.com>,
	"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink
Date: Fri, 23 Jun 2023 09:59:13 -0700	[thread overview]
Message-ID: <CAFvDQ9rs6PqTU_CfwdFnM8HEJOZFZNKfPL9w2Dz1b50cKODWOg@mail.gmail.com> (raw)
In-Reply-To: <0401A097-59CD-4A30-B853-04D1F3945DA0@olegkutkov.me>

[-- Attachment #1: Type: text/plain, Size: 3093 bytes --]

Professor Todd mentions that Elon had a tweet about it last Oct.  But I
have not seen it.

Hesham

Hesham

On Fri, Jun 23, 2023, 9:50 AM contact@olegkutkov.me <contact@olegkutkov.me>
wrote:

>
> No reaction from SpaceX or Elon
>
> On 23 Jun 2023, at 19:15, Hesham ElBakoury via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
> 
> What was Elon Musk reaction to this research?
>
> Hesham
>
> On Fri, Jun 23, 2023, 9:12 AM David Fernández via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
>> I think that paper has already been discussed in this list. It
>> appeared in the news a while ago:
>> https://www.theregister.com/2022/10/24/starlink_signal_decoded_for_use
>>
>> Regards,
>>
>> David
>>
>> > Date: Fri, 23 Jun 2023 06:17:08 -0700
>> > 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
>> > Message-ID:
>> >       <CAO0-hXar-KaB=p=
>> HGeGe39vAKTeG5RHBxSgioccOj+R4Nt7yeA@mail.gmail.com>
>> > Content-Type: text/plain; charset="utf-8"
>> >
>> > Most interesting:
>> >
>> > " VIII. CONCLUSIONS We have developed and applied a blind signal
>> > identification technique to uncover the frequency- and time-domain
>> > structure of the Starlink Ku-band downlink signal. We further identified
>> > four synchronization sequences that can be used to *passively exploit*
>> > Starlink signals for pseudorange-based positioning, navigation, and
>> timing
>> > (PNT), and explicitly evaluated two of these. The results in this paper
>> > illuminate the *path to use of Starlink signals as a backup to
>> traditional
>> > GNSS* for PNT."
>> >
>> > On Fri, Jun 23, 2023 at 6:09 AM Joe Hamelin <nethead@gmail.com> wrote:
>> >
>> >>
>> >>
>> 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
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>

[-- Attachment #2: Type: text/html, Size: 5934 bytes --]

  parent reply	other threads:[~2023-06-23 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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
2023-06-23 13:17                           ` Joe Hamelin

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=CAFvDQ9rs6PqTU_CfwdFnM8HEJOZFZNKfPL9w2Dz1b50cKODWOg@mail.gmail.com \
    --to=helbakoury@gmail.com \
    --cc=contact@olegkutkov.me \
    --cc=davidfdzp@gmail.com \
    --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