From: Christian von der Ropp <cvdr@vdr.net>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink for Tonga?
Date: Tue, 8 Feb 2022 14:50:43 +0100 [thread overview]
Message-ID: <10acc51c-f00c-02cc-c117-ed6083faf9d0@vdr.net> (raw)
In-Reply-To: <bd881274-3ffe-d283-31d4-d1388b0bfa1c@cs.auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 4067 bytes --]
And to make things even more complicated Starlink also have to avoid
emissions within a certain angle towards O3b's satellites in MEO
(relatively easy as they are close to the geostationary arc) and to all
its LEO competitors with higher ITU priority which would be OneWeb,
Telesat Lightspeed, KLEO Connect and before all these a potential
European LEO constellation should it use Thales' ITU filings (MCSAT-2
LEO-x) - see
https://www.itu.int/en/ITU-R/space/workshops/danang-2015/Documents/Presentations/Yvon%20Henri%20-%20NGSO%20Issues.pdf
The more satellites these LEO competitors deploy, the more in-line
events will occur during which Starlink will have to seize emissions - a
so far underestimated issue that could severely impair coverage and
service availability.
Am 08.02.2022 um 11:11 schrieb Ulrich Speidel:
>
> That's an interesting aspect that I hadn't considered! A quick
> back-of-the-envelope reveals that the GSO arc is at least 15 times
> beyond a Starlink LEO satellite, and with Friis propagation, that's
> about 23 dB in terms of difference in path loss, and thus not as much
> separation as you'd want. Under ITU regs you're competing with noise,
> not signal ;-)
>
> Either way, I know it's a contested topic even at the regulatory level.
>
> Tonga is at around 20 deg south so could be using anything from north
> just over zenith to further south, but as I've pointed out, there are
> other issues here also.
>
> On 8/02/2022 9:58 pm, Mike Puchol wrote:
>> The GSO satellite operators, due to the fact that they have been
>> there for eons, plus they cannot move the satellites around, are at a
>> disadvantage with NGSO operators such as Starlink, when it comes to
>> using the same shared spectrum. The Ku band downlink spectrum
>> Starlink uses is the same as your satellite TV, thus, if your Dishy
>> was inline with a Starlink satellite and the line towards the GSO
>> arc, the satellite would kill all satellite TV in your area.
>>
>> The ITU in its article 22 specifies how NGSO operators must protect
>> GSO operators, by not generating interference above certain power
>> levels to or from the GSO arc. For Dishy, this means it cannot
>> transmit anywhere between the GSO arc elevation and +18° (up), -18°
>> (down).
>>
>> In Barcelona, the GSO arc due South sits at around 43° in elevation,
>> thus, my Dishy cannot transmit between 25° and 61° in elevation due
>> South. However, the protection band begins around an azimuth of 120°,
>> up to around 240°.
>>
>> In the Equator, the GSO protection band starts due East, and goes all
>> the way across the sky due West. It also takes out 37° of visible sky
>> at zenith.
>>
>> Hope this helps!
>>
>> Best,
>>
>> Mike
>> On Feb 8, 2022, 09:49 +0100, Daniel AJ Sokolov
>> <daniel@sokolov.eu.org>, wrote:
>>> On 2022-02-08 at 01:47, Mike Puchol wrote:
>>>> the biggest impact on Fiji and Tonga is the GSO protection, which
>>>> takes out 36° of usable sky, all the way from East to West.
>>>
>>> Ho Mike,
>>>
>>> would you please be so kind to explain that a bit more?
>>>
>>> Thank you
>>> Daniel
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
> --
> ****************************************************************
> Dr. Ulrich Speidel
>
> School of Computer Science
>
> Room 303S.594 (City Campus)
> Ph: (+64-9)-373-7599 ext. 85282
>
> The University of Auckland
> ulrich@cs.auckland.ac.nz
> http://www.cs.auckland.ac.nz/~ulrich/
> ****************************************************************
>
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
M +49.179.3695000
T +49.7071.538720
F +49.7071.538722
Ecvdr@vdr.net
Wwww.vdr.net
[-- Attachment #2: Type: text/html, Size: 7567 bytes --]
next prev parent reply other threads:[~2022-02-08 13:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:50 Daniel AJ Sokolov
2022-02-07 18:51 ` Nathan Owens
2022-02-07 19:05 ` Christian von der Ropp
2022-02-07 19:06 ` Nathan Owens
2022-02-07 20:38 ` Ulrich Speidel
2022-02-07 20:44 ` Ulrich Speidel
2022-02-10 7:53 ` Ulrich Speidel
2022-02-07 21:18 ` Ben Greear
2022-02-07 21:24 ` David Lang
2022-02-07 21:36 ` Mike Puchol
2022-02-07 22:22 ` Ulrich Speidel
2022-02-07 22:29 ` Mike Puchol
2022-02-07 23:36 ` Ulrich Speidel
2022-02-07 23:47 ` David Lang
2022-02-08 0:20 ` Ulrich Speidel
2022-02-08 1:20 ` David Lang
2022-02-08 4:46 ` Inemesit Affia
2022-02-08 6:25 ` Daniel AJ Sokolov
2022-02-08 7:30 ` Ulrich Speidel
2022-02-08 7:49 ` Daniel AJ Sokolov
2022-02-08 8:22 ` Ulrich Speidel
2022-02-08 8:47 ` Mike Puchol
2022-02-08 8:49 ` Daniel AJ Sokolov
2022-02-08 8:58 ` Mike Puchol
2022-02-08 9:05 ` Daniel AJ Sokolov
2022-02-08 9:10 ` Mike Puchol
2022-02-08 15:22 ` Sebastian Moeller
2022-02-08 10:11 ` Ulrich Speidel
2022-02-08 13:50 ` Christian von der Ropp [this message]
2022-02-08 15:28 ` Mike Puchol
2022-02-08 16:25 ` Dave Taht
2022-02-08 18:20 ` Gary E. Miller
2022-02-08 19:12 ` David Lang
2022-02-09 12:09 ` Ulrich Speidel
2022-02-09 19:28 ` [Starlink] Sunburp kills 40 starlink satellites Doc Searls
2022-02-09 19:51 ` Michael Richardson
2022-02-09 12:58 ` [Starlink] Starlink for Tonga? Ulrich Speidel
2022-02-18 5:04 ` Daniel AJ Sokolov
2022-02-18 7:27 ` Mike Puchol
2022-02-18 9:01 ` Ulrich Speidel
2022-04-19 11:57 ` Mike Puchol
2022-04-19 12:06 ` Dave Taht
2022-04-19 12:43 ` Ulrich Speidel
2022-04-20 1:06 ` Ulrich Speidel
2022-04-20 1:14 ` Jeremy Austin
2022-02-18 10:27 ` Ulrich Speidel
2022-02-18 12:48 ` Rich Brown
2022-02-18 15:43 ` Nathan Owens
2022-02-18 10:29 ` Ulrich Speidel
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=10acc51c-f00c-02cc-c117-ed6083faf9d0@vdr.net \
--to=cvdr@vdr.net \
--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