From: David Lang <david@lang.hm>
To: Mike Puchol <mike@starlink.sx>
Cc: Michael Richardson via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] SpaceX/Starlink says it's ready for a fall satellite-to-cell service with T-Mobile
Date: Tue, 4 Jun 2024 21:26:24 -0700 (PDT) [thread overview]
Message-ID: <r161q38p-8rsn-nq5s-833p-26op0p1q11p2@ynat.uz> (raw)
In-Reply-To: <e8a6c3fe-7bd1-4cc9-b80b-bce636e21656@Spark>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Mike Puchol wrote:
> Yes, they correct doppler in a single stream - what I was alluding to is the
> MIMO advantage of terrestrial networks which cannot be easily replicated from
> multiple satellites, as the UE cannot correct multiple doppler shifts and
> timing advances unless it implements an NTN-specific approach.
I am thinking that the doppler correction will be the same (or very close to it)
for everything in a single cell.
now, timing that exact between multiple satellites is something I would see as a
harder problem, but I'm not an expert there.
David Lang
>
> Best,
>
> Mike
> On Jun 4, 2024 at 20:17 -0700, David Lang <david@lang.hm>, wrote:
>> Mike Puchol wrote:
>>
>>> Something else that's much harder to implement is MIMO, as you don't get path
>>> diversity from a satellite. AST claims they will do this by using more than
>>> one satellite, however they haven't answered basic questions such as how will
>>> the UE compensate the huge differences in doppler shift on top of the multiple
>>> paths.
>>
>> for the starlink version, the satellite adjusts it's transmit/receive
>> frequencies to correct for the doppler shift so that the phones don't need to.
>>
>> David Lang
>>
>
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2024-06-05 4:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 18:08 Frantisek Borsik
2024-06-03 18:17 ` the keyboard of geoff goodfellow
2024-06-04 12:32 ` Alexandre Petrescu
2024-06-03 20:47 ` Eugene Y Chang
2024-06-03 21:16 ` David Lang
2024-06-03 21:57 ` Eugene Y Chang
2024-06-03 21:59 ` Frantisek Borsik
2024-06-03 22:41 ` David Lang
2024-06-04 0:13 ` Eugene Y Chang
2024-06-04 0:54 ` David Lang
2024-06-04 11:20 ` Frantisek Borsik
2024-06-04 11:43 ` Alexandre Petrescu
2024-06-04 11:54 ` Frantisek Borsik
2024-06-04 13:11 ` Ulrich Speidel
2024-06-04 18:10 ` David Lang
2024-06-04 18:51 ` Eugene Y Chang
2024-06-04 18:58 ` Michael Richardson
2024-06-04 23:01 ` Mike Puchol
2024-06-05 3:17 ` David Lang
2024-06-05 4:16 ` Mike Puchol
2024-06-05 4:26 ` David Lang [this message]
2024-06-05 4:47 ` Sebastian Moeller
2024-06-05 6:12 ` Mike Puchol
2024-06-05 7:03 ` David Lang
2024-06-05 11:30 ` Alexandre Petrescu
2024-06-04 10:42 David Fernández
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=r161q38p-8rsn-nq5s-833p-26op0p1q11p2@ynat.uz \
--to=david@lang.hm \
--cc=mike@starlink.sx \
--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