1998
DOI: 10.1088/0967-1846/5/1/002
|View full text |Cite
|
Sign up to set email alerts
|

Capacity reservation for multimedia traffic

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
5
0

Year Published

1999
1999
2011
2011

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 20 publications
(5 citation statements)
references
References 18 publications
0
5
0
Order By: Relevance
“…Non-work-conserving schemes are described in [18], [19], [27]. In our architecture we use the non-work-conserving scheme described in [15]. Our contribution described in this section is a further evaluation of the chosen scheme, with experimental and formal justification of its suitability in our service architecture.…”
Section: Packet Scheduling In Routersmentioning
confidence: 99%
See 1 more Smart Citation
“…Non-work-conserving schemes are described in [18], [19], [27]. In our architecture we use the non-work-conserving scheme described in [15]. Our contribution described in this section is a further evaluation of the chosen scheme, with experimental and formal justification of its suitability in our service architecture.…”
Section: Packet Scheduling In Routersmentioning
confidence: 99%
“…We suggest a simple way of flow description based on a fixed rate. We further evaluate the non-work-conserving scheduling introduced in [15], and provide formal and experimental justification of its suitability for our service architecture.…”
Section: Introductionmentioning
confidence: 99%
“…Many other scheduling mechanisms that limit the delay of a selected flow keep track of a 'deadline' for each queued packet, such as earliest deadline first (EDF) [43,38] and alternative best-effort [26] or use virtual clocks [52]. An overview can be found in [25,40]. Another approach to accommodate delay-sensitive traffic, is to keep queues small by discarding packets before congestion can arise.…”
Section: Introductionmentioning
confidence: 99%
“…Jitter can remain controlled as long as the flows are shaped to their peak rate at the network ingress [4]. Also, the deployment of non-work conserving scheduling in routers for the real-time traffic class can be beneficial for controlling jitter [5]. Therefore, we assume that the real-time traffic flows can be shaped to their peak rate at the network ingress and that the scheduling mechanism for the real-time traffic class is priority scheduling with a strict bandwidth limit and with First-In-First-Out (FIFO) service discipline.…”
Section: Introductionmentioning
confidence: 99%