10th IEEE Symposium on Computers and Communications (ISCC'05)
DOI: 10.1109/iscc.2005.106
|View full text |Cite
|
Sign up to set email alerts
|

Modular Reference Implementation of an IP-DSLAM

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Publication Types

Select...
5
1
1

Relationship

2
5

Authors

Journals

citations
Cited by 8 publications
(8 citation statements)
references
References 13 publications
0
8
0
Order By: Relevance
“…In general, these latencies can be derived by simulating kernels, static analysis, or from worst-case requirements. In our case, a waiting time of 18.7 μs has been derived, using the method described in [25], for the upstream direction. We derived a downstream latency of 13.8 μs by summing up all estimated latencies of the system in downstream direction.…”
Section: Simulation Setupmentioning
confidence: 99%
“…In general, these latencies can be derived by simulating kernels, static analysis, or from worst-case requirements. In our case, a waiting time of 18.7 μs has been derived, using the method described in [25], for the upstream direction. We derived a downstream latency of 13.8 μs by summing up all estimated latencies of the system in downstream direction.…”
Section: Simulation Setupmentioning
confidence: 99%
“…We apply the Click/CRACC framework to the domain of access networks and model a complete IP based DSL access multiplexer (DSLAM) [10] on the functional level in Click. We use Click for the functional verification of the model and the CRACC execution profiles on embedded processors for further design space exploration.…”
Section: Case Studymentioning
confidence: 99%
“…We need to develop a reference application that must capture the following trends in access networks [19]:…”
Section: Trendsmentioning
confidence: 99%
“…We have defined a set of line and trunk card configurations in terms of number of ports and supported bandwidth for representative subscriber line technologies: ADSL, VDSL(2+), and SHDSL. Our traffic mix has an average packet length of about 260 Byte versus 64 Byte for the worst-case (see [19]). …”
Section: Traffic Scenariosmentioning
confidence: 99%
See 1 more Smart Citation