From: Jeremy Austin <jeremy@aterlo.com>
To: Mike Puchol <mike@starlink.sx>
Cc: David Lang <david@lang.hm>,
starlink@lists.bufferbloat.net,
Dave Collier-Brown <dave.collier-brown@indexexchange.com>
Subject: Re: [Starlink] SpaceX ordered to explain pricing strategy
Date: Tue, 12 Apr 2022 14:30:36 -0800 [thread overview]
Message-ID: <CACw=56J_X=j5JRsGdAtAMewJ8na=SzpYiw99MEbK+FEPq3iLcA@mail.gmail.com> (raw)
In-Reply-To: <67d53857-4b4d-4604-be1c-e3972477bc75@Spark>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Tue, Apr 12, 2022 at 1:25 PM Mike Puchol <mike@starlink.sx> wrote:
> The frequency re-use is a factor of steering angle. Take these two spot
> beams, and the cells that they cover. The left side is a beam almost at
> nadir, the right side is close to maximum steering angle. Any hexagonal
> cell inside the beam’s footprint cannot be covered by another beam (from
> same or other satellite), as the overlap would violate the restrictions on
> Starlink’s license:
>
I don't disagree with the description of this type of spatial reuse. It
will be interesting to see how nonlinear the capacity growth due to tighter
angles is, however, and whether it's more like a 4x increase or an 8x
increase.
The question of whether they can achieve their goals without additional
reuse (for example, covering a given hex with more than one channel) is
open. Fun times.
--
--
Jeremy Austin
Sr. Product Manager
Preseem | Aterlo Networks
preseem.com
Book a Call: https://app.hubspot.com/meetings/jeremy548
Phone: 1-833-733-7336 x718
Email: jeremy@preseem.com
Stay Connected with Newsletters & More:
*https://preseem.com/stay-connected/* <https://preseem.com/stay-connected/>
[-- Attachment #2: Type: text/html, Size: 2579 bytes --]
next prev parent reply other threads:[~2022-04-12 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 8:59 Daniel AJ Sokolov
2022-04-08 18:15 ` David Lang
2022-04-08 21:04 ` Daniel AJ Sokolov
2022-04-08 21:45 ` David Lang
2022-04-10 13:55 ` Dave Collier-Brown
2022-04-12 1:56 ` David Lang
2022-04-12 20:39 ` Jeremy Austin
2022-04-12 21:25 ` Mike Puchol
2022-04-12 22:30 ` Jeremy Austin [this message]
2022-04-12 22:39 ` Mike Puchol
2022-04-12 22:41 ` Daniel AJ Sokolov
2022-04-12 22:43 ` Daniel AJ Sokolov
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='CACw=56J_X=j5JRsGdAtAMewJ8na=SzpYiw99MEbK+FEPq3iLcA@mail.gmail.com' \
--to=jeremy@aterlo.com \
--cc=dave.collier-brown@indexexchange.com \
--cc=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