3 ms·
What I'm talking about is the nature of a dedicated access (1:1) single carrier per channel geostationary link, via a pair of modems such as comtech cdm760 and
by walrus01 6y ago
What I'm talking about is the nature of a dedicated access (1:1) single carrier per channel geostationary link, via a pair of modems such as comtech cdm760 and appropriately sized rf chains and antennas on both ends. It'll be a rock solid 492ms and the bandwidth (in Mbps) will be proportional to the size of the transponder space leased, and influenced by antenna sizing/gain, overall link budget, tx power on both ends and so forth.
Example: at one location, a 3.8 meter ku band dual linear polarity compact cassegrain dish in somalia, a 200W BUC+SSPA, good quality norsat PLL LNB, a cdm760 modem. Ten MHz of transponder space occupied total. Other end, a 5.5m dish with similar gear on it in a teleport in Cyprus.
If the person I'm replying to isn't willing or able to clarify whether they were in a contended, or dedicated network, or specify the gear, it's hard to say exactly why they're seeing jitter. But I can quite confidently say that excursions above 495ms are not something seen in a dedicated network.
It's how that dedicated capacity can get sliced up and shared that is the most common cause of packet loss, jitter and high latency in geostationary based two way satellite IP links.
The most common thing for a cheap VSAT isp to do is to acquire one chunk of Ku transponder capacity (let's say about $8000 a month worth), install something like an idirect hub with line cards in it, and sell access to individual end users in $developingnation at an 8:1 oversubscription ratio or more. Meaning that an end user vsat terminal might see 495ms at a lucky time when its peers in the same network were not also moving traffic, but could also often see latency anywhere from 500 to 850 during busy periods.
Now that same 8000 bucks a month of transponder space could equally well be assigned to a single high priority end user with money to pay, in which case they would never see above 495ms. Or it could be oversubscribed to all hell, such as if the ISP wanted to sell $280/month service to a bunch of very cost conscious end users in a developing nation environment who can only afford very cheap VSAT terminal hardware (one 1.2m fiberglass compression molded reflector, a 4W BUC, and an idirect modem) and minimal monthly ongoing payments. In which case each user will be in a 16:1 or worse oversubscribed network.
The economics of making a 5500 kilogram $200 million satellite in geostationary orbit pay for itself, before its lifespan is done in 15 years, are not favorable. If you ever want to truly be shocked go price the $ per Mbps per month that results from the 1:1 dedicated setup I described above.
On the topic of what the average hn reader considers "satellite internet". Based on consumer experience with the absolute cheapest consumer grade ku and Ka band vsat terminals in the usa, they almost 99% of the time mean Hughesnet or viasat/wildblue. Very few people actually have money or reason to lay their hands on real two way satellite stuff. Generally if you work for a company that needs something like a $3500/month link for a mine in Nunavut you're paying some third party experts to implement it.
- runako 6y ago(I'm definitely not very knowledgable about any of this, naive questions incoming.) > 3.8 meter ku band dual linear polarity compact cassegrain dish > a 5.5m dish Are these receiver sizes in the range of what Starlink expects from users? I had in mind something more like a DirectTV dish. If the consumer dish sizes are indeed smaller, how does that affect the discussion about jitter and other aspects of link quality?
- walrus01 6y agoNo not at all, I was referring to the size of equipment seen in Afghanistan for dedicated geostationary links to military facilities. The starlink cpe is indeed in the category of directv dish sized.
- runako 6y agoHow does that affect the discussion about jitter and other aspects of link quality? With only a tiny bit of the relevant subjects under my belt, I would expect the metrics to be significantly worse using a much smaller dish. But it seems like you're suggesting Starlink could achieve similar metrics on a smaller dish? I'm curious how that works. Apologies if I'm misunderstanding.
- deleted 6y ago[deleted]
- mlyle 6y ago> It'll be a rock solid 492ms Note that may be true for one bird in Afghanistan, but the path length isn't exactly the same everywhere, nor are the delays of all modulaiton schemes.
- walrus01 6y agoIt will vary a few ms but not much. First hand experience, latency differs at most a millisecond or two between an Afghanistan-germany link, and an Afghanistan-singapore link. More latency variation to internet based things is seen based on where the teleport is. The same as would be experienced by a terrestrial internet user in either Raising, Germany or near the Singtel teleport in Singapore. For instance our site in Germany was more than 15ms away by fiber from DE-CIX stuff in Frankfurt. The site in Singapore had better latency to any cdn or hosting operation that was in Singapore itself, but much worse if traffic had to find its way through the terrestrial submarine fiber internet to other places. End to end latency between Afghanistan-germany-seattle or Afghanistan-singapore-seattle was considerably different. Yes, the position of the two end point sites on the sphere that is the earth will have slightly different speed of light times to a satellite in geostationary orbit. But 99% of that latency in the above 490ms figure is the extreme distance of the satellite, and not whether or not one site is slightly further down the sphere, as viewed from a theoretical observer sitting on the satellite. It is also worth noting that modern scpc/mcpc modems can be intentionally configured to use more computationally "expensive" FECs, in a trade off of slightly more bps/Hz squeezed into a given sized slice of transport kHz, at the expense of a few ms higher latency. This is a network engineering design decision made when a link is first brought online. Modern modems and ASICs, FPGAs have made this less difficult than it used to be. If I can use an analogy for software developers, this is sort of like the speed vs file size trade off choice made between using gzip, bzip2, xzip, at different settings and compression levels.