From: Oleg Kutkov <contact@olegkutkov.me>
To: David Lang <david@lang.hm>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] System and method of providing a medium access control scheduler
Date: Fri, 24 Feb 2023 02:18:23 +0200 [thread overview]
Message-ID: <9dd258eb-1bdb-4234-1301-744ee77b4097@olegkutkov.me> (raw)
In-Reply-To: <q61966n4-ns93-25qn-899o-3r8os67q7qos@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Yes. The cell size is ~20 km
On 2/24/23 02:08, David Lang wrote:
> they can only narrow the radio beam so much (probably whatever their
> cell size is). They can't change the footprint without changing the
> antenna, so unless they have the beam move around in the cell, the
> footprint should be slightly larger than the cell size
>
> sometimes there is a lot of data going to one station, but sometims
> it's only going to be a trival amount (think ack packets for a lot of
> uploads), so they can save airtime by using one timeslot to transmit
> to many stations at once.
>
> David Lang
>
> On Fri, 24 Feb 2023, Oleg Kutkov via Starlink wrote:
>
>> Date: Fri, 24 Feb 2023 01:47:05 +0200
>> From: Oleg Kutkov via Starlink <starlink@lists.bufferbloat.net>
>> Reply-To: Oleg Kutkov <contact@olegkutkov.me>
>> To: starlink@lists.bufferbloat.net
>> Subject: Re: [Starlink] System and method of providing a medium
>> access control
>> scheduler
>>
>> Oh, that's interesting.
>>
>> >> the satellite broadcasts the downlink radio frame to all the user
>> terminals in a group and they each retrieve their respective data
>> from the downlink radio frame
>>
>> I thought the satellite beamformer only sends data frames to the
>> appropriate UT. It looks like the given satellite covers the whole
>> cell at one TX channel.
>> Otherwise, it would be too complex, I guess.
>>
>> On 2/23/23 23:53, Dave Taht via Starlink wrote:
>>> For those of you that don't look at patents, don't look at:
>>>
>>> https://patents.justia.com/patent/11540301
>>>
>>> But I would welcome comment from those that do.
>>>
>>> H/T virtuallynathan.
>>>
>>
--
Best regards,
Oleg Kutkov
[-- Attachment #2.1: Type: text/html, Size: 3078 bytes --]
[-- Attachment #2.2: dUsO08OKzqrAgrTa.png --]
[-- Type: image/png, Size: 35251 bytes --]
next prev parent reply other threads:[~2023-02-24 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:53 Dave Taht
2023-02-23 23:47 ` Oleg Kutkov
2023-02-24 0:08 ` David Lang
2023-02-24 0:18 ` Oleg Kutkov [this message]
2023-02-24 0:51 ` Ulrich Speidel
2023-02-24 1:05 ` Oleg Kutkov
2023-02-24 1:17 ` Dave Taht
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=9dd258eb-1bdb-4234-1301-744ee77b4097@olegkutkov.me \
--to=contact@olegkutkov.me \
--cc=david@lang.hm \
--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