From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net, George Michaelson <ggm@apnic.net>
Subject: Re: [Starlink] apnic piece on starlink
Date: Fri, 7 Apr 2023 05:10:54 -0700 (PDT) [thread overview]
Message-ID: <s0587qs0-2213-5519-5p8s-57396porqon0@ynat.uz> (raw)
In-Reply-To: <dc209fe3-4ac7-aac4-2e0d-6da69bf1cddf@auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]
On Fri, 7 Apr 2023, Ulrich Speidel via Starlink wrote:
> Remember how cellphone networks evolve: You start with a few towers in high
> spots using high power to get wide area coverage while you have few users. At
> this point (which corresponds largely to where Starlink is at now), spectrum
> isn't much of an issue (and even that is only partially true for Starlink -
> see Mike's excellent article on this:
> https://mikepuchol.com/modeling-starlink-capacity-843b2387f501). As your user
> base grows, you move off the hills into the valleys and lower your power so
> your cells become smaller and shielded from each others, because now,
> frequency re-use is the name of the game. You use beamforming off phased
> arrays in order to further separate users.
>
> So what we are seeing now is Starlink as the new kid on the block turning up
> with what are in analogy effectively cell towers high in the sky. Their
> current user base is maybe at 1/1000th (ballpark) of potential demand before
> growth. Population growth on this planet alone adds a lot more potential
> users a day than Starlink does. So what options does Starlink have to scale?
> Unlike a terrestrial network operator, Starlink can't really come down all
> that far from their "space hills" without burning their satellites up in the
> atmosphere more quickly. "Space hills" also consist of vacuum only, which
> unlike earthly hills can't separate base stations by blocking signal. The
> distance from/to space also requires vastly larger phased array antennas for
> the same spot beam coverage area contour on the ground. It also places limits
> on transmit EIRP both ways. Larger antennas and solar arrays constrain the
> number of satellites that can be launched at a time, making constellation
> building and replacement harder.
All of this is correct, I will note that in the Starlink plans, there are plans
to put a layer of satellites at a sigificantly lower altitude.
By launching 10x as many satellites, and each one being able to handle 10x the
data, they _may_ get to 100x, but that is really going to be pushing it. (note
that this is for ~10x the number of satellites lauched by everyone other than
SpaceX since Sputnik)
If you can get fiber, it's always going to be better than a wireless option, DSL
is threatened by Starlink in many suburbs, cablemodems depend so much on the ISP
it's hard to say
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:[~2023-04-07 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:09 Dave Taht
2023-04-07 9:55 ` Ulrich Speidel
2023-04-07 12:10 ` David Lang [this message]
2023-04-08 11:48 ` Ulrich Speidel
2023-04-08 17:37 ` David Lang
2023-04-08 18:37 ` Michael Richardson
2023-04-08 18:58 ` Hesham ElBakoury
2023-04-08 19:07 ` Hesham ElBakoury
2023-04-08 19:38 ` Dave Taht
2023-04-08 19:56 ` Hesham ElBakoury
2023-04-08 22:37 ` Larry Press
2023-04-10 16:07 David Fernández
2023-04-10 16: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=s0587qs0-2213-5519-5p8s-57396porqon0@ynat.uz \
--to=david@lang.hm \
--cc=ggm@apnic.net \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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