* Re: [Starlink] FCC Chair Rosenworcel Proposes to Investigate Impact of Data Caps [not found] ` <CAL9Qcx5a=zbhs7pk=tWdZT42_ytz2StxPL8gNF6z6yOe6XRGxg@mail.gmail.com> @ 2023-06-17 23:08 ` Dave Taht 2023-06-23 9:55 ` [Starlink] Signal Structure of the Starlink Ku-Band Downlink Hesham ElBakoury 0 siblings, 1 reply; 9+ messages in thread From: Dave Taht @ 2023-06-17 23:08 UTC (permalink / raw) To: Tom Beecher; +Cc: Michael Thomas, nanog, Dave Taht via Starlink I am happy to see the conversation about starlink escaping over here, because it is increasingly a game-changing technology (I also run the starlink mailing list, cc´d)... On Sat, Jun 17, 2023 at 3:56 PM Tom Beecher <beecher@beecher.cc> wrote: >> >> As I mentioned elsewhere, I'm not sure that the current economics are the real economics. There is a whole other cluster on the drawing boards, called Starshield, which you can read about here: https://www.spacex.com/starshield/ The current "retail"economics are limited to US allies as a result of the ukraine war showing how important information and bandwidth are to modern warfare. There are also political implications to downlinks in each country. I imagine, for example, that India is holding off on licensing until Musk gets them a tesla factory. Multiple other countries are making a huge investment into retaining control of the "spacewaves", so there´s that also. >I'm pretty sure they've been purposefully throttling demand because they still don't have the capacity so it would make sense to overcharge in the mean time. Throttling demand is not how I would put it. Each cell has a limited capacity, so starlink has been running promotions to get more subscribers into more rural cells where the capacity exists. I have kvetched elsewhere about how poorly starlink manages bandwidth and bufferbloat currently, but they are largely better than modern day 5G and DSL, so... > Is there something inherent in their cpe that makes them much more expensive than, say, satellite tv dishes? The original cost/dish was about 2k, so they were selling those at well below the install price, with a ROI of about 12 months, given that figure. I imagine with mass manufacturing the cost/dish has come down substantially, and they also charge a realistic price on the business quality dish of $2500. It would not surprise me if the basic dishy essentially cost less than 500 to manufacture nowadays. The default wifi router, which many replace, cannot be more than 50 dollars on the BOM. > I can see marginally more because of the LEO aspect, but isn't that mainly just software? It wouldn't surprise me that the main cost is the truck roll. There is no truck roll. They have gone to amazing extants in - put the dish in a clear area, power it up, you are on. Establishing infrastructure, like downlinks, connected near fiber in civilization does have a large cost, takes time, and is also subject to government regulation. > > - Starlink currently reports around 1.5M subscribers. At $110 a month, that's $165M in revenue, Creating A 2B dollar/year business in 4 years is quite impressive. A reasonable projection would be 10m subs in 4 more years, e.g. 10B/year. That aint' chicken scratch. In fact, I think it funds humanity´s expansion into the solar system quite handily. > - A Falcon 9 launch is billed out at $67M. A Falcon 9 can carry up to 60 Starlink sats. That's ~667 launches to reach the stated goal of 40k sats in the constellation. So roughly $45B in just launch costs, if you assume the public launch price. (Because if they are launching their own stuff, they aren't launching an external paying customer.) > - The reported price per sat is $250k. There are multiple sat types, the mini v2 (which can only be flown on the falcon 9, is rumored to cost about that much) Starship had had a much larger, much more highly capable sat designed for it, but it is running a few years behind schedule. The hope for that was that launch costs would decline even further. Also OPEX - running this network - is probably a substantial cost. I have lost track of the number of downlink stations established (over 200 now) but I would guess those are about 1m per. There is a really amazing site that looks at this stuff called starlink.sx. > > Assuming they give themselves a friendly internal discount, the orbital buildout cost are in the neighborhood of $30B for launches, and $10B for sats. The present day capacity, even if they were to do no more launches, is still underused. Roughly half the USA has no starlink service yet, multiple countries have been slow to license, and nearly all of Africa remains uncovered. Maritime and air are big sources of new business. I try to stress it is where people are but infrastructure isn´t is where starlink really shines, and that very little bandwidth is required for things like email and chat. > > - The satellite failure rate is stated to be ~ 3% annually. On a 40K cluster, that's 1200 a year. Where did you see that? So far as I can tell, the failure rate, exclusive of one launch lost to solar expansion, is trending towards zero. Also, maneuvering thrust (documented somewhere) has been quite under expectations, in terms of operating fuel they could use the existing sats for far, far longer than the intended 5 year operational lifetime, in this regard. > > That's about 20 more launches a year, and $300M for replacement sats. Let's round off and say that's $1B a year there. > > So far, that's a $40B buildout with a $1B annual run rate. And that's just the orbital costs. We haven't even calculated the manufacturing costs of the receiver dishes, terrestrial network infra cost , opex from staff , R&D, etc . > > Numbers kinda speak for themselves here. > >> I mean, I get that Musk is sort of a cuckoo bird but say what you will he does have big ambitions. > > > Ambition is good. But reality tends to win the day. As does math. > > > > > > On Sat, Jun 17, 2023 at 4:38 PM Michael Thomas <mike@mtcc.com> wrote: >> >> >> On 6/17/23 1:25 PM, Tom Beecher wrote: >>> >>> Won't Starlink and other LEO configurations be that backstop sooner >>> rather than later? >> >> >> Unlikely. They will remain niche. The economics don't make sense for those services to completely replace terrestrial only service. I agree they will not replace terrestrial service, but maritime, roaming, airplanes, and rural are big enough markets. >> >> Why would they put up 40000 satellites if their ambition is only niche? I mean, I get that Musk is sort of a cuckoo bird but say what you will he does have big ambitions. >> >> From my standpoint, they don't have to completely replace the incumbents. I'd be perfectly happy just keeping them honest. >> >> As I mentioned elsewhere, I'm not sure that the current economics are the real economics. I'm pretty sure they've been purposefully throttling demand because they still don't have the capacity so it would make sense to overcharge in the mean time. Is there something inherent in their cpe that makes them much more expensive than, say, satellite tv dishes? I can see marginally more because of the LEO aspect, but isn't that mainly just software? It wouldn't surprise me that the main cost is the truck roll. >> >> Mike >> >> >> >> On Fri, Jun 16, 2023 at 4:17 PM Michael Thomas <mike@mtcc.com> wrote: >>> >>> >>> On 6/16/23 1:09 PM, Mark Tinka wrote: >>> > >>> > >>> > On 6/16/23 21:19, Josh Luthman wrote: >>> >> Mark, >>> >> >>> >> In my world I constantly see people with 0 fixed internet options. >>> >> Many of these locations do not even have mobile coverage. >>> >> Competition is fine in town, but for millions of people in the US >>> >> (and I'm going to assume it's worse or comparable in CA/MX) there is >>> >> no service. >>> >> >>> >> As a company primarily delivering to residents, competition is not a >>> >> focus for us and for the urban market it's tough to survive on a ~1/3 >>> >> take rate. >>> > >>> > I should have been clearer... the lack of competition in many markets >>> > is not unique to North America. I'd say all of the world suffers that, >>> > since there is only so much money and resources to go around. >>> > >>> > What I was trying to say is that should a town or village have the >>> > opportunity to receive competition, where existing services are >>> > capped, uncapping that via an alternative provider would be low >>> > hanging fruit to gain local marketshare. Of course, the alternative >>> > provider would need to show up first, but that's a whole other thread. >>> > >>> Won't Starlink and other LEO configurations be that backstop sooner >>> rather than later? I don't know if they have caps as well, but even if >>> they do they could compete with their caps. >>> >>> Mike >>> -- Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/ Dave Täht CSO, LibreQos ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-17 23:08 ` [Starlink] FCC Chair Rosenworcel Proposes to Investigate Impact of Data Caps Dave Taht @ 2023-06-23 9:55 ` Hesham ElBakoury 2023-06-23 13:09 ` Joe Hamelin 0 siblings, 1 reply; 9+ messages in thread From: Hesham ElBakoury @ 2023-06-23 9:55 UTC (permalink / raw) To: starlink Has anyone looked at this paper (Signal Structure of the Starlink Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published in IEEE Transactions on Aerospace and Electronic Systems. Are there other research efforts which try to do the same? Thanks Hesham ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-23 9:55 ` [Starlink] Signal Structure of the Starlink Ku-Band Downlink Hesham ElBakoury @ 2023-06-23 13:09 ` Joe Hamelin 2023-06-23 13:17 ` Joe Hamelin 0 siblings, 1 reply; 9+ messages in thread From: Joe Hamelin @ 2023-06-23 13:09 UTC (permalink / raw) To: Hesham ElBakoury; +Cc: starlink [-- Attachment #1: Type: text/plain, Size: 736 bytes --] https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf Here's the PDF. On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink < starlink@lists.bufferbloat.net> wrote: > Has anyone looked at this paper (Signal Structure of the Starlink > Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published in > IEEE Transactions on Aerospace and Electronic Systems. Are there other > research efforts which try to do the same? > > Thanks > > Hesham > > > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > -- -- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 [-- Attachment #2: Type: text/html, Size: 1489 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-23 13:09 ` Joe Hamelin @ 2023-06-23 13:17 ` Joe Hamelin 0 siblings, 0 replies; 9+ messages in thread From: Joe Hamelin @ 2023-06-23 13:17 UTC (permalink / raw) To: Hesham ElBakoury; +Cc: starlink [-- Attachment #1: Type: text/plain, Size: 1456 bytes --] Most interesting: " VIII. CONCLUSIONS We have developed and applied a blind signal identification technique to uncover the frequency- and time-domain structure of the Starlink Ku-band downlink signal. We further identified four synchronization sequences that can be used to *passively exploit* Starlink signals for pseudorange-based positioning, navigation, and timing (PNT), and explicitly evaluated two of these. The results in this paper illuminate the *path to use of Starlink signals as a backup to traditional GNSS* for PNT." On Fri, Jun 23, 2023 at 6:09 AM Joe Hamelin <nethead@gmail.com> wrote: > > https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf > > Here's the PDF. > > On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink < > starlink@lists.bufferbloat.net> wrote: > >> Has anyone looked at this paper (Signal Structure of the Starlink >> Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published in >> IEEE Transactions on Aerospace and Electronic Systems. Are there other >> research efforts which try to do the same? >> >> Thanks >> >> Hesham >> >> >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink >> > > > -- > -- > Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 > -- -- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 [-- Attachment #2: Type: text/html, Size: 2648 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink
@ 2023-06-23 16:12 David Fernández
2023-06-23 16:14 ` Hesham ElBakoury
0 siblings, 1 reply; 9+ messages in thread
From: David Fernández @ 2023-06-23 16:12 UTC (permalink / raw)
To: starlink
I think that paper has already been discussed in this list. It
appeared in the news a while ago:
https://www.theregister.com/2022/10/24/starlink_signal_decoded_for_use
Regards,
David
> Date: Fri, 23 Jun 2023 06:17:08 -0700
> From: Joe Hamelin <nethead@gmail.com>
> To: Hesham ElBakoury <helbakoury@gmail.com>
> Cc: starlink@lists.bufferbloat.net
> Subject: Re: [Starlink] Signal Structure of the Starlink Ku-Band
> Downlink
> Message-ID:
> <CAO0-hXar-KaB=p=HGeGe39vAKTeG5RHBxSgioccOj+R4Nt7yeA@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Most interesting:
>
> " VIII. CONCLUSIONS We have developed and applied a blind signal
> identification technique to uncover the frequency- and time-domain
> structure of the Starlink Ku-band downlink signal. We further identified
> four synchronization sequences that can be used to *passively exploit*
> Starlink signals for pseudorange-based positioning, navigation, and timing
> (PNT), and explicitly evaluated two of these. The results in this paper
> illuminate the *path to use of Starlink signals as a backup to traditional
> GNSS* for PNT."
>
> On Fri, Jun 23, 2023 at 6:09 AM Joe Hamelin <nethead@gmail.com> wrote:
>
>>
>> https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf
>>
>> Here's the PDF.
>>
>> On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink <
>> starlink@lists.bufferbloat.net> wrote:
>>
>>> Has anyone looked at this paper (Signal Structure of the Starlink
>>> Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published in
>>> IEEE Transactions on Aerospace and Electronic Systems. Are there other
>>> research efforts which try to do the same?
>>>
>>> Thanks
>>>
>>> Hesham
>>>
>>>
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>>>
>>
>>
>> --
>> --
>> Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-23 16:12 David Fernández @ 2023-06-23 16:14 ` Hesham ElBakoury 2023-06-23 16:50 ` contact 0 siblings, 1 reply; 9+ messages in thread From: Hesham ElBakoury @ 2023-06-23 16:14 UTC (permalink / raw) To: David Fernández; +Cc: Dave Taht via Starlink [-- Attachment #1: Type: text/plain, Size: 2491 bytes --] What was Elon Musk reaction to this research? Hesham On Fri, Jun 23, 2023, 9:12 AM David Fernández via Starlink < starlink@lists.bufferbloat.net> wrote: > I think that paper has already been discussed in this list. It > appeared in the news a while ago: > https://www.theregister.com/2022/10/24/starlink_signal_decoded_for_use > > Regards, > > David > > > Date: Fri, 23 Jun 2023 06:17:08 -0700 > > From: Joe Hamelin <nethead@gmail.com> > > To: Hesham ElBakoury <helbakoury@gmail.com> > > Cc: starlink@lists.bufferbloat.net > > Subject: Re: [Starlink] Signal Structure of the Starlink Ku-Band > > Downlink > > Message-ID: > > <CAO0-hXar-KaB=p= > HGeGe39vAKTeG5RHBxSgioccOj+R4Nt7yeA@mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > Most interesting: > > > > " VIII. CONCLUSIONS We have developed and applied a blind signal > > identification technique to uncover the frequency- and time-domain > > structure of the Starlink Ku-band downlink signal. We further identified > > four synchronization sequences that can be used to *passively exploit* > > Starlink signals for pseudorange-based positioning, navigation, and > timing > > (PNT), and explicitly evaluated two of these. The results in this paper > > illuminate the *path to use of Starlink signals as a backup to > traditional > > GNSS* for PNT." > > > > On Fri, Jun 23, 2023 at 6:09 AM Joe Hamelin <nethead@gmail.com> wrote: > > > >> > >> > https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf > >> > >> Here's the PDF. > >> > >> On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink < > >> starlink@lists.bufferbloat.net> wrote: > >> > >>> Has anyone looked at this paper (Signal Structure of the Starlink > >>> Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published > in > >>> IEEE Transactions on Aerospace and Electronic Systems. Are there other > >>> research efforts which try to do the same? > >>> > >>> Thanks > >>> > >>> Hesham > >>> > >>> > >>> _______________________________________________ > >>> Starlink mailing list > >>> Starlink@lists.bufferbloat.net > >>> https://lists.bufferbloat.net/listinfo/starlink > >>> > >> > >> > >> -- > >> -- > >> Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > [-- Attachment #2: Type: text/html, Size: 4404 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-23 16:14 ` Hesham ElBakoury @ 2023-06-23 16:50 ` contact 2023-06-23 16:56 ` David Fernández 2023-06-23 16:59 ` Hesham ElBakoury 0 siblings, 2 replies; 9+ messages in thread From: contact @ 2023-06-23 16:50 UTC (permalink / raw) To: Hesham ElBakoury; +Cc: David Fernández, Dave Taht via Starlink [-- Attachment #1: Type: text/html, Size: 5013 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-23 16:50 ` contact @ 2023-06-23 16:56 ` David Fernández 2023-06-23 16:59 ` Hesham ElBakoury 1 sibling, 0 replies; 9+ messages in thread From: David Fernández @ 2023-06-23 16:56 UTC (permalink / raw) To: starlink This may be a reaction, but not from Elon, of course: https://www.esa.int/Applications/Navigation/Industry_invited_to_bid_for_low-Earth_orbit_satnav_demo 2023-06-23 18:50 GMT+02:00, contact@olegkutkov.me <contact@olegkutkov.me>: > > No reaction from SpaceX or Elon > >> On 23 Jun 2023, at 19:15, Hesham ElBakoury via Starlink >> <starlink@lists.bufferbloat.net> wrote: >> >> >> What was Elon Musk reaction to this research? >> >> Hesham >> >> On Fri, Jun 23, 2023, 9:12 AM David Fernández via Starlink >> <starlink@lists.bufferbloat.net> wrote: >>> >>> I think that paper has already been discussed in this list. It >>> appeared in the news a while ago: >>> https://www.theregister.com/2022/10/24/starlink_signal_decoded_for_use >>> >>> Regards, >>> >>> David >>> >>> > Date: Fri, 23 Jun 2023 06:17:08 -0700 >>> > From: Joe Hamelin <nethead@gmail.com> >>> > To: Hesham ElBakoury <helbakoury@gmail.com> >>> > Cc: starlink@lists.bufferbloat.net >>> > Subject: Re: [Starlink] Signal Structure of the Starlink Ku-Band >>> > Downlink >>> > Message-ID: >>> > >>> > <CAO0-hXar-KaB=p=HGeGe39vAKTeG5RHBxSgioccOj+R4Nt7yeA@mail.gmail.com> >>> > Content-Type: text/plain; charset="utf-8" >>> > >>> > Most interesting: >>> > >>> > " VIII. CONCLUSIONS We have developed and applied a blind signal >>> > identification technique to uncover the frequency- and time-domain >>> > structure of the Starlink Ku-band downlink signal. We further >>> > identified >>> > four synchronization sequences that can be used to *passively exploit* >>> > Starlink signals for pseudorange-based positioning, navigation, and >>> > timing >>> > (PNT), and explicitly evaluated two of these. The results in this paper >>> > illuminate the *path to use of Starlink signals as a backup to >>> > traditional >>> > GNSS* for PNT." >>> > >>> > On Fri, Jun 23, 2023 at 6:09 AM Joe Hamelin <nethead@gmail.com> wrote: >>> > >>> >> >>> >> https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf >>> >> >>> >> Here's the PDF. >>> >> >>> >> On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink < >>> >> starlink@lists.bufferbloat.net> wrote: >>> >> >>> >>> Has anyone looked at this paper (Signal Structure of the Starlink >>> >>> Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published >>> >>> in >>> >>> IEEE Transactions on Aerospace and Electronic Systems. Are there >>> >>> other >>> >>> research efforts which try to do the same? >>> >>> >>> >>> Thanks >>> >>> >>> >>> Hesham >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Starlink mailing list >>> >>> Starlink@lists.bufferbloat.net >>> >>> https://lists.bufferbloat.net/listinfo/starlink >>> >>> >>> >> >>> >> >>> >> -- >>> >> -- >>> >> Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 >>> _______________________________________________ >>> 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 > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Starlink] Signal Structure of the Starlink Ku-Band Downlink 2023-06-23 16:50 ` contact 2023-06-23 16:56 ` David Fernández @ 2023-06-23 16:59 ` Hesham ElBakoury 1 sibling, 0 replies; 9+ messages in thread From: Hesham ElBakoury @ 2023-06-23 16:59 UTC (permalink / raw) To: contact; +Cc: David Fernández, Dave Taht via Starlink [-- Attachment #1: Type: text/plain, Size: 3093 bytes --] Professor Todd mentions that Elon had a tweet about it last Oct. But I have not seen it. Hesham Hesham On Fri, Jun 23, 2023, 9:50 AM contact@olegkutkov.me <contact@olegkutkov.me> wrote: > > No reaction from SpaceX or Elon > > On 23 Jun 2023, at 19:15, Hesham ElBakoury via Starlink < > starlink@lists.bufferbloat.net> wrote: > > > What was Elon Musk reaction to this research? > > Hesham > > On Fri, Jun 23, 2023, 9:12 AM David Fernández via Starlink < > starlink@lists.bufferbloat.net> wrote: > >> I think that paper has already been discussed in this list. It >> appeared in the news a while ago: >> https://www.theregister.com/2022/10/24/starlink_signal_decoded_for_use >> >> Regards, >> >> David >> >> > Date: Fri, 23 Jun 2023 06:17:08 -0700 >> > From: Joe Hamelin <nethead@gmail.com> >> > To: Hesham ElBakoury <helbakoury@gmail.com> >> > Cc: starlink@lists.bufferbloat.net >> > Subject: Re: [Starlink] Signal Structure of the Starlink Ku-Band >> > Downlink >> > Message-ID: >> > <CAO0-hXar-KaB=p= >> HGeGe39vAKTeG5RHBxSgioccOj+R4Nt7yeA@mail.gmail.com> >> > Content-Type: text/plain; charset="utf-8" >> > >> > Most interesting: >> > >> > " VIII. CONCLUSIONS We have developed and applied a blind signal >> > identification technique to uncover the frequency- and time-domain >> > structure of the Starlink Ku-band downlink signal. We further identified >> > four synchronization sequences that can be used to *passively exploit* >> > Starlink signals for pseudorange-based positioning, navigation, and >> timing >> > (PNT), and explicitly evaluated two of these. The results in this paper >> > illuminate the *path to use of Starlink signals as a backup to >> traditional >> > GNSS* for PNT." >> > >> > On Fri, Jun 23, 2023 at 6:09 AM Joe Hamelin <nethead@gmail.com> wrote: >> > >> >> >> >> >> https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf >> >> >> >> Here's the PDF. >> >> >> >> On Fri, Jun 23, 2023 at 2:55 AM Hesham ElBakoury via Starlink < >> >> starlink@lists.bufferbloat.net> wrote: >> >> >> >>> Has anyone looked at this paper (Signal Structure of the Starlink >> >>> Ku-Band Downlink) by Todd E. Humphreys ? This paper will be published >> in >> >>> IEEE Transactions on Aerospace and Electronic Systems. Are there other >> >>> research efforts which try to do the same? >> >>> >> >>> Thanks >> >>> >> >>> Hesham >> >>> >> >>> >> >>> _______________________________________________ >> >>> Starlink mailing list >> >>> Starlink@lists.bufferbloat.net >> >>> https://lists.bufferbloat.net/listinfo/starlink >> >>> >> >> >> >> >> >> -- >> >> -- >> >> Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 >> _______________________________________________ >> 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 > > [-- Attachment #2: Type: text/html, Size: 5934 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2023-06-23 16:59 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <71psq926-osqr-70n0-264s-363162o77958@qbaryna.pbz> [not found] ` <2d6314f0-1742-20c0-ab0d-7f5fcdf3809b@mtcc.com> [not found] ` <CAAcrURLFkLKA3AG4SwRncgMEJ+4dDqKqtfidAXHFKqzGfRmc8Q@mail.gmail.com> [not found] ` <c62ed36e-f552-c913-5d3e-ae2c925aa177@mtcc.com> [not found] ` <84894b58-528a-a032-3f3d-a884f5b4a24f@tinka.africa> [not found] ` <CAN9qwJ9whTOBk0puQYChPujBDHj8pYgfYLLo5hqkKZYDXcib_Q@mail.gmail.com> [not found] ` <ae1cd18a-318a-6f92-7695-ab3dbc8ff815@tinka.africa> [not found] ` <95633c24-c7c0-e0d9-3c74-d946acfccb41@mtcc.com> [not found] ` <CAL9Qcx4BJQ6htQoRa_Rq1MaCdj56iV1FUAfHc4c4eU8XwH5LBQ@mail.gmail.com> [not found] ` <cf5fc49f-3e75-92d9-ee4e-24ed33241d95@mtcc.com> [not found] ` <CAL9Qcx5a=zbhs7pk=tWdZT42_ytz2StxPL8gNF6z6yOe6XRGxg@mail.gmail.com> 2023-06-17 23:08 ` [Starlink] FCC Chair Rosenworcel Proposes to Investigate Impact of Data Caps Dave Taht 2023-06-23 9:55 ` [Starlink] Signal Structure of the Starlink Ku-Band Downlink Hesham ElBakoury 2023-06-23 13:09 ` Joe Hamelin 2023-06-23 13:17 ` Joe Hamelin 2023-06-23 16:12 David Fernández 2023-06-23 16:14 ` Hesham ElBakoury 2023-06-23 16:50 ` contact 2023-06-23 16:56 ` David Fernández 2023-06-23 16:59 ` Hesham ElBakoury
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox