Traditional satellite internet uses satellites in geostationary orbits, or 35,786km high above the equator. This is great because satellites in that orbit are stationary relative to the ground, so you just need a parabolic antenna pointed at a specific point in the sky to get great reception. But it's also terrible for latency because the signal takes 120ms just to get up, and another 120ms to get down. Assuming you live on the equator, directly underneath the satellite. For someone living in the temperate regions, typical real rtts are in the 700ms area.
Starlink and OneWeb are different in that they intend to use a lot of satellites in low orbits to maintain constant coverage. This is technically much harder, not the least because you need thousands of satellites to get reasonably good coverage, but also because the ground station and the satellite transceiver both need to track each other. This was not technically feasible before, but modern AESA antennas can steer their signal without having to move the antenna, and can both transmit and receive multiple simultaneous beams and very rapidly move the beams around when doing time-sharing.
The minimum round-trip time to something very close to you and also close to it's own ground station will be on the order of 10ms. However, where the system really shines is long distance communication. The satellites will pass the signal between each other using lasers, and will get the signal to the other side of the earth much faster than terrestrial fiber, both because laser in vacuum travels substantially faster than one in fibre, and also because the fibres don't get to follow ideal great circle paths.
Independent researches have evaluated the likely latencies of the system, and the results are frankly shocking. For example, today on the existing fiber network, rtt between London and Singapore is ~160ms. On Starlink, the rtt will be ~90ms.
Not all satellite internet, currently, is dependent on geostationary. Read up on o3b's network and architecture, which has been operational for several years now. The cost, however, is basically "if you have to ask, you can't afford it". O3b is a market option for ISPs and telecoms in very remote or island areas that were previously dependent upon leasing Ku or C band transponder megahertz.
> Traditional satellite internet uses satellites in geostationary orbits, or 35,786km high above the equator. This is great because satellites in that orbit are stationary relative to the ground, so you just need a parabolic antenna pointed at a specific point in the sky to get great reception. But it's also terrible for latency because the signal takes 120ms just to get up, and another 120ms to get down. Assuming you live on the equator, directly underneath the satellite. For someone living in the temperate regions, typical real rtts are in the 700ms area.
This doesn't check out.
The radius of Earth is 6,300km. Assuming a receiver on the north pole, the total distance should only be sqrt((35786 + 6300)^2 + 6300^2) = 42555km, which isn't notably larger than the 36000km at the equator.
I'm sure you're still right about the latency, but it can't be just distance doing it.
in practical real world use the absolute minimum ping time you'll see from a 1:1 dedicated capaacity (SCPC) link via geostationary, from end terminal to larger earth station, is 489 to 491 ms. This will vary up to 495ms depending on modem modulation/framing and FEC type, and actual line of sight distance to satellite (low inclination aim angle for the antenna, if you're not directly under the satellite, vs two sites that are directly under it as viewed from geostationary).
Ignoring TDMA oversubscribed VSAT networks for the moment, there are a number of different possible modulation schemes and FEC types, and FEC code rate (payload vs FEC percentages), and things that are unique to different SCPC modems, which will vary the modulation by a few ms beyond pure speed of light.
The latency from the distance light travels does not vary that much. The rest of the ~600 ms latency is caused by the same thing as latency on ground systems (routers, etc.). And the processors on spacecraft are not particularly fast.
Is lower latency the main benefit? Because there are other ways to combat that, like locating servers closer to where users are. Yes, there are some applications like HFT or gaming or whatever that need lower latency, but I think it would be more useful to the world at large if Starlink provides people all over the world with affordable broadband Internet access with a minimum speed of say 20mbps, say. People far from cities, people in developing countries with bad infrastructure (till a few years back, I had a 4mbps connection), people on islands with bad connectivity, trains, ships, planes, etc. Does it do the latter?
Starlink and OneWeb are different in that they intend to use a lot of satellites in low orbits to maintain constant coverage. This is technically much harder, not the least because you need thousands of satellites to get reasonably good coverage, but also because the ground station and the satellite transceiver both need to track each other. This was not technically feasible before, but modern AESA antennas can steer their signal without having to move the antenna, and can both transmit and receive multiple simultaneous beams and very rapidly move the beams around when doing time-sharing.
The minimum round-trip time to something very close to you and also close to it's own ground station will be on the order of 10ms. However, where the system really shines is long distance communication. The satellites will pass the signal between each other using lasers, and will get the signal to the other side of the earth much faster than terrestrial fiber, both because laser in vacuum travels substantially faster than one in fibre, and also because the fibres don't get to follow ideal great circle paths.
Independent researches have evaluated the likely latencies of the system, and the results are frankly shocking. For example, today on the existing fiber network, rtt between London and Singapore is ~160ms. On Starlink, the rtt will be ~90ms.