Lesson 3 of 4 · Budget capacity for real program streams
Budget capacity for real program streams
6 minute lesson · 3 checks along the way
Your goal for this lessonDistinguish transponder counts, aggregate capacity and useful stream budgets using explicit fictional assumptions.
In this lesson 3 sections · 3 checks
Read & understand
A hardware count is not an audience-speed guarantee
A transponder is part of the radio relay system; counting transponders does not by itself specify useful data throughput. Bandwidth, power allocation, communication mode and service configuration affect what the system can carry. Counts of regional channels or switchable resources also need their definitions before they can be added.
Nilesat advertises aggregate Ka broadband capacity and describes multiple spot beams. Aggregate capacity is a system-level claim, not a guaranteed rate for every user. Some users may share a beam or a ground bottleneck while another part of the system has spare resources. A useful customer-rate statement needs the actual service arrangement and a measured or specified path.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Reserve space for the work that is not the program
Consider an invented carrier offering 24 megabits per second of coded bit capacity. If an illustrative code rate leaves three quarters for information bits, that stage yields 18 megabits per second. Reserving another three megabits per second for the example’s control and other overhead leaves a 15-megabit-per-second program budget. These simplified assumptions are not a Nilesat modulation or multiplex specification.
Three fictional program streams requiring six, five and four megabits per second exactly fill that budget. Replacing the four-megabit stream with a six-megabit stream raises demand to 17, so the same configuration no longer fits. A budget must account for what is actually sent; labeling every program high definition does not tell us its encoded rate.
Reserve capacity before fitting the programs
Original teaching diagram. Simplified fictional carrier and fixed-rate programs; not a Nilesat multiplex specification.
Open full-size diagram in a new tab: Reserve capacity before fitting the programsCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Quality and peaks belong in the acceptance test
Compressed video can need different rates for different content and quality targets. A quiet interview and a fast-moving sports scene may stress an encoder differently. If a multiplex shares capacity dynamically, testing only an easy scene may miss the peak combination the service must support. The fictional fixed-rate arithmetic is a planning exercise, not a substitute for measuring representative content.
A useful test includes the agreed video and audio quality, expected simultaneous programs and receiver compatibility. If operators reduce a stream’s rate to fit a budget, they should verify the resulting quality instead of declaring success solely because packets arrive. Advertised system capacity, allocated service capacity and acceptable audience experience are related but distinct results.
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.