4 ms·
If they were to put a few GB of memory on these terminal dish things, and (say) a few PB on each satellite, they could have satellites broadcast a cache of what
by ncmncm 5y ago
If they were to put a few GB of memory on these terminal dish things, and (say) a few PB on each satellite, they could have satellites broadcast a cache of what a lot of people in the service area are watching, saving a lot of up-and-down traffic. Broadcast, so all the terminals are listening to identically the same packets arriving.
The flagship use for such a capability would be for World Cup games, where not much actual storage would be involved, because almost everybody is interested only in the latest few seconds of the game.
It looks like launches of Starlink satellites are volume-limited, not mass-limited, so adding a few kg to each for the PB or so of SSDs would be cheap (albeit x17k for that many satellites). But they are going to be bandwidth-limited pretty soon, and eliminating a whole bunch of high-traffic up-and-down streams will be worth a lot.
I think right now the on-board lasers in the last one (or two?) launches just point to the satellite immediately in front and behind in the same orbit. (Please correct me if I am mistaken.) Probably soon they will have extra lasers on board that can track satellites in other orbits, with galvanomically controlled mirrors, to be able to route traffic and, usefully, share content of on-board SSDs, multiplying the available cache capability by splitting it among subsets of the satellites.
Of course it will need app-level adaptations to be able to take advantage of this sort of caching, but it needn't be complex, mostly like a redirect to a proxy running in the dish. Strictly speaking, RAM on the dish hardware is not strictly necessary, given custom software running in the clients, but everything gets a lot easier if the client software is maximally simple.
- morei 5y agoThis is much harder than you're assuming. With the increasing prevalence of TLS traffic (https et al), any cache almost certainly needs to be an explicitly configured proxy which is a user configuration issue with all it's associated support and compatibility problems. Add to that the power consumption on a satellite is often a limiting factor, the security issues, the added latency, the ever decreasing fraction of traffic that is cache-able, etc etc ... it's very much not clear that this is a good idea.
- ncmncm 5y agoI see that you replied before reading the final paragraph. Whatever is the power consumption of broadcasting to all receivers in the cell, it is much, much less than transmitting the same data to each of the receivers individually, and less again than receiving it over and over again from the fiber terminal, even if you have to power up an SSD for it.