From: J Pan <Pan@uvic.ca>
To: "David Fernández" <davidfdzp@gmail.com>
Cc: starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Time Synchronization in Satellite Networks
Date: Tue, 30 Apr 2024 10:12:14 -0700 [thread overview]
Message-ID: <CAHn=e4hoY1gCW9oTnHMW4QPawNcxyS+XVaUDqmQVsFzm5=WgNw@mail.gmail.com> (raw)
In-Reply-To: <CAC=tZ0owZ+qANKzTffheHzyAXz8dyCxeFTqZMHeyzTn4k5o_Jg@mail.gmail.com>
accurate timing is useful for starlink itself, e.g.,
https://patents.justia.com/patent/11924821 and its users---hopefully
starlink can allow its dish to advertise the time besides location to
lan
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Tue, Apr 30, 2024 at 1:47 AM David Fernández via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Dear Hesham,
>
> May I ask for what reason do you need the satellites to be synchronized in time? What application is requiring this? Earth observation? Then, go for GNSS-based time synchronization, as done by EO satellites in LEO: https://navi.ion.org/content/69/3/navi.531
>
> "GNSS signals could even be used for reliable navigation in lunar orbit", so also for time synchronization: https://www.nasa.gov/missions/tech-demonstration/nasa-navigation-tech-shows-timing-really-is-everything
>
> It seems that as long as your device can have a GNSS receiver, that's the best way to keep it time-synchronized. Is there anything preventing the use of GNSS on your intended application?
>
> https://lists.bufferbloat.net/pipermail/starlink/2024-March/002605.html
>
> Regards,
>
> David
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2024-04-30 17:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 8:46 David Fernández
2024-04-30 17:12 ` J Pan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-02 15:03 Hesham ElBakoury
2024-03-02 15:18 ` Sebastian Moeller
2024-03-02 15:25 ` Hesham ElBakoury
2024-03-02 15:38 ` Christian von der Ropp
2024-03-02 16:02 ` Hesham ElBakoury
2024-03-02 16:19 ` Christian von der Ropp
2024-04-01 22:04 ` Hesham ElBakoury
2024-04-01 22:22 ` Sebastian Moeller
2024-04-01 22:48 ` David Lang
2024-04-01 23:09 ` J Pan
2024-04-02 0:29 ` Hesham ElBakoury
2024-04-02 0:34 ` David Lang
2024-04-02 0:59 ` Vint Cerf
2024-03-02 17:01 ` Alexandre Petrescu
2024-03-02 17:18 ` Alexandre Petrescu
2024-03-02 17:26 ` Hesham ElBakoury
2024-03-02 18:26 ` Alexandre Petrescu
2024-03-02 15:45 ` Sebastian Moeller
2024-03-02 15:53 ` Hesham ElBakoury
2024-03-02 17:08 ` Alexandre Petrescu
2024-03-02 17:09 ` Alexandre Petrescu
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='CAHn=e4hoY1gCW9oTnHMW4QPawNcxyS+XVaUDqmQVsFzm5=WgNw@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=davidfdzp@gmail.com \
--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