From: Daniel AJ Sokolov <daniel@falco.ca>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink as Cellular Backup
Date: Fri, 2 Dec 2022 02:16:33 -0700 [thread overview]
Message-ID: <6822e8d6-479a-c657-71d9-54d0f824fa92@falco.ca> (raw)
In-Reply-To: <CAC=tZ0p4B-tYcSNO_WehiG5G+Q32K8Kpujao84-JAoXgVV3CNA@mail.gmail.com>
On 2022-12-02 at 01:19, David Fernández via Starlink wrote:
> Hi Daniel,
>
> You may be interested on this paper:
> https://www.researchgate.net/publication/365488929_Concept_and_Evaluation_Of_5G_Backhauling_via_Starlink
>
> Looking at figure 9, I understand that you can serve up to 50
> simultaneous users with a Starlink dish as backhaul, more or less,
> before calls quality starts degrading for everybody.
Interesting. In some areas, this will be enough for a mobile tower.
(Also, there is a more powerful business version of Starlink now.)
BR
Daniel AJ
next prev parent reply other threads:[~2022-12-02 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 8:19 David Fernández
2022-12-02 9:16 ` Daniel AJ Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-01 18:46 Daniel AJ Sokolov
2022-12-01 19:48 ` contact
2022-12-01 19:51 ` 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=6822e8d6-479a-c657-71d9-54d0f824fa92@falco.ca \
--to=daniel@falco.ca \
--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