Lesson 5 of 5 · Gonets
Gonets: match a data service to the message and its deadline
8 minute lesson · 3 checks along the way
Your goal for this lessonExplain the Gonets low-orbit communications program and distinguish geographic access, waiting time and end-to-end message delivery.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
Connect remote users with a complete data service
Gonets is a Russian low-orbit satellite communications system developed to connect mobile and fixed users, including places with limited terrestrial infrastructure. Its history includes the Gonets-D demonstrations, Gonets-D1 and the later Gonets-M spacecraft used in Gonets-D1M development. These names describe related generations and system elements; they do not mean one satellite remained unchanged throughout the program.
A 2013 paper by Reshetnev system designers discusses user terminals, spacecraft, regional stations and control facilities. The operator’s later overview describes uses such as infrastructure and environmental monitoring. A remote sensor needs more than a satellite overhead: its terminal must collect the information, communicate through an available link and deliver a usable message to the intended recipient.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Distinguish a short radio path from a short delivery time
Low-orbit satellites are closer to users than geostationary satellites, reducing radio travel distance and changing terminal requirements. They also move through the sky, so an individual spacecraft is visible for a limited interval. The constellation, user location and ground-network arrangement affect when a communication opportunity exists. A short does not guarantee that a newly created message reaches its destination immediately.
The system designers explicitly discuss communication waiting time and message delivery time. Their historical tables depend on stated constellation and coverage assumptions. They should not be copied as a present-day service guarantee. Geographic coverage over time is also different from uninterrupted access at every instant. For a specific application, the relevant question is whether the complete service can meet that application’s actual deadline.
A Rokot rocket stands at Plesetsk during Gonets-M launch preparations in 2014. The enclosed satellites and their subsequent message-delivery performance are not visible in this ground photograph.
Look closely
What connects this launch preparation to the later communication service?
See what to notice
Launch and spacecraft records establish the deployment history; service measurements establish what messages were delivered and when.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Work through the message’s timeline
In a fictional monitoring example, a terminal waits eight minutes for a suitable contact, then the message spends twelve minutes in the remaining delivery process and two minutes in validation at the receiving center. The total is twenty-two minutes. These are teaching values, not measured Gonets performance. Shortening the radio signal’s travel time by a fraction of a second would have little effect on that total.
Such a service might fit periodic environmental reports better than an application that requires an immediate interactive response, depending on the actual service specification. Message timestamps let the recipient distinguish when a condition was measured from when its report arrived. Tracking identifiers and acknowledgments help determine whether information was delivered or needs another attempt. Gonets demonstrates why useful satellite communications should be evaluated from the user’s complete task: the content, destination, reliability and deadline matter alongside the orbit and the launch history.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.
- Read: Reshetnev system designers: development and waiting time in Gonets-D1MKuzovnikov, Testoedov and Agureev, 2013. Historical architecture and modeled waiting times; the projected fleet and service figures are not present-day guarantees.
- Read: Gonets: satellite data service overviewOperator brochure describing low-orbit data services and infrastructure monitoring; promotional coverage language is not used as a measured latency guarantee.
- Read: Gonets operator authors: contrasting Luch and Gonets systemsDiordiev and Panasov, 2021, printed pages 77–78. Read the orbit and ground-segment distinctions; dated fleet totals and future modernization plans are not current service guarantees.
- Read: NASA: telecommunicationsCompare the explanation and its assumptions with the worked example in this lesson.