MétaCan
Menu
Back to cohort
Record W2116644713 · doi:10.1109/comst.2003.5341336

A survey of congestion control schemes for multicast video applications

2003· article· en· W2116644713 on OpenAlexaff
Ashraf Matrawy, Ioannis Lambadaris

Bibliographic record

VenueIEEE Communications Surveys & Tutorials · 2003
Typearticle
Languageen
FieldComputer Science
TopicNetwork Traffic and Congestion Control
Canadian institutionsCarleton University
Fundersnot available
KeywordsMulticastComputer scienceComputer networkSource-specific multicastXcastNetwork congestionPragmatic General MulticastProtocol Independent MulticastIP multicastReliable multicast

Abstract

fetched live from OpenAlex

Congestion control for IP multicast on the Internet has been one of the main issues that challenge a rapid deployment of IP multicast. In this article, we survey and discuss the most important congestion control schemes for multicast video applications on the Internet. We start with a discussion of the different elements of a multicast congestion control architecture. A congestion control scheme for multicast video possesses specific requirements for these elements. These requirements are discussed, along with the evaluation criteria for the performance of multicast video. We categorize the schemes we present into end-to-end schemes and router-supported schemes. We start with the end-to-end category and discuss several examples of both single-rate multicast applications and layered multicast applications. For the router-supported category, we first present single-rate schemes that utilize filtering of multicast packets by the routers. Next we discuss receiver-based layered schemes that rely on routers group/flow control of multicast sessions. We evaluate a number of schemes that belong to each of the two categories.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: none
Teacher disagreement score0.003
Threshold uncertainty score0.013

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.005
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0010.001
Scholarly communication0.0020.003
Open science0.0020.001
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0030.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.060
GPT teacher head0.314
Teacher spread0.254 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreReview

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations38
Published2003
Admission routes1
Has abstractyes

Explore more

Same venueIEEE Communications Surveys & TutorialsSame topicNetwork Traffic and Congestion ControlFrench-language works237,207