From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Mon, 10 Jun 2024 05:06:16 -0700 (PDT) [thread overview]
Message-ID: <7023574s-qpso-1661-530n-o15rr9rs7305@ynat.uz> (raw)
In-Reply-To: <8986fa02-3c6a-4d66-9105-979d7e4ef248@auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
Ulrich Speidel wrote:
> On 10/06/2024 2:38 pm, David Lang via Starlink wrote:
>>
>> the V2 were about 8-10x the capacity of the V1.5 (the ones they could
>> launch 50-60 per flight), the v2 mini they have been launching (~22/flight)
>> are about midway between the two. No recent word on the V2s, but Tim Dodd
>> did another starbase visit with Elon before the flight, so watch for that
>> to show up soon.
>
> I think it'd be useful we could agree on what we mean by "capacity" before we
> start throwing numbers around, especially relative ones. For Starlink, I can
> think of the following capacities (yes, plural):
>
> * User up-/downlink capacity from/to a single user. (How many bits/s
> can I throw at a Dishy?)
> * Downlink capacity to all users in a single cell (under the proviso
> that we don't have any users in adjacent cells that need / want
> service - think small island in the middle of the Pacific).
> * Overall user downlink capacity from a single satellite to multiple
> cells. (Can't deploy co-frequency beams with identical polarisation
> to the same cell if you have multiple such beams on your bird, but
> can do so if we can aim them at different cells)
> * Gateway uplink capacity (to users served directly by the satellite
> or indirectly via ISLs)
> * Gateway downlink (from users served directly by the satellite or
> indirectly via ISLs)
> * Dto. per gateway (see co-frequency beam issue)
> * Processing capacity: Number of bits / s that a satellite can pump
> between its receive beams / incoming ISLs and transmit beams /
> outgoing ISLs.
I believe the numbers thrown around are for the total satellite capability, it's
not per user or per cell and it includes the in-space laser links.
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-10 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 23:50 Dave Taht
2024-06-10 0:15 ` Ulrich Speidel
2024-06-10 2:22 ` Michael Richardson
2024-06-10 10:51 ` Ulrich Speidel
2024-06-10 12:04 ` David Lang
2024-06-10 12:15 ` Ulrich Speidel
2024-06-10 2:38 ` David Lang
2024-06-10 11:04 ` Ulrich Speidel
2024-06-10 12:06 ` David Lang [this message]
2024-06-10 12:21 ` Ulrich Speidel
2024-06-10 8:57 ` Alexandre Petrescu
2024-06-10 9:49 ` David Lang
2024-06-10 13:22 ` Alexandre Petrescu
2024-06-10 13:37 ` David Lang
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=7023574s-qpso-1661-530n-o15rr9rs7305@ynat.uz \
--to=david@lang.hm \
--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