2011
DOI: 10.1109/lcomm.2011.060111.102514
|View full text |Cite
|
Sign up to set email alerts
|

Obtaining Models for Realistic Mobile Network Simulations using Real Traces

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Year Published

2013
2013
2021
2021

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 6 publications
(8 citation statements)
references
References 8 publications
0
8
0
Order By: Relevance
“…We have also surveyed the trace diagnostics support in the tools that were contestants of the "offline monitoring" track of the 2014 and 2015 international Competition on Software for Runtime Verification (CSRV 2014 [3] and CSRV 2015 [22]). Four of the tools (STePr, AgMon [29], LogFire [27], OptySim [8]) are not publicly available; another tool RiTHM-v2.0 [34], is available but does not work when executed by following the instructions specified in the README file on its GitHub page [39]; the remaining tools that we analyzed are: Breach [10], MonPoly [5], QEA [37], SOLOIST+ZOT [7], and RV-Monitor [33]. Table 2 summarizes our findings, indicating whether a tool produces a boolean output (column "boolean"), whether it takes into account all the (events leading to) violations in a trace (column "positions"), whether it provides detailed diagnostic information, such as the cause of a violation (column "cause"), and whether it is based on MDE technologies (column "MDE").…”
Section: Related Workmentioning
confidence: 99%
“…We have also surveyed the trace diagnostics support in the tools that were contestants of the "offline monitoring" track of the 2014 and 2015 international Competition on Software for Runtime Verification (CSRV 2014 [3] and CSRV 2015 [22]). Four of the tools (STePr, AgMon [29], LogFire [27], OptySim [8]) are not publicly available; another tool RiTHM-v2.0 [34], is available but does not work when executed by following the instructions specified in the README file on its GitHub page [39]; the remaining tools that we analyzed are: Breach [10], MonPoly [5], QEA [37], SOLOIST+ZOT [7], and RV-Monitor [33]. Table 2 summarizes our findings, indicating whether a tool produces a boolean output (column "boolean"), whether it takes into account all the (events leading to) violations in a trace (column "positions"), whether it provides detailed diagnostic information, such as the cause of a violation (column "cause"), and whether it is based on MDE technologies (column "MDE").…”
Section: Related Workmentioning
confidence: 99%
“…We have implemented a version of the analyzer using the S pin model checker, and have applied it to ns-2 network simulations 31,32,37,38 and Java programs. 33 In later sections we will present the particular implementation for ns-2 and several case studies regarding performance, reliability and validation analysis.…”
Section: Analysis and Optimization Frameworkmentioning
confidence: 99%
“…The property we used for this validation case study is similar to the one we had previously used in another application of our framework: configuring jitter simulation models to conform to real network traffic. 32…”
Section: Validation Of E-model Extensionmentioning
confidence: 99%
See 1 more Smart Citation
“…In general, low 2 values have been obtained (0.7 or less) with the equations used, which exposes the complexity of the relationships between the cross-layer parameters analyzed. In future work, we will apply objective-driven simulations [28] to obtain more accurate patterns between cross-layer parameters under study.…”
Section: Harq and Packet Lossesmentioning
confidence: 99%