Performance Evaluation of Ad Hoc Routing Protocols using ns2 simulations
Performance Metrics
Three important performance metrics are evaluated:
-
Packet delivery fraction ? The ratio of the data packets delivered to the destinations to those generated by the CBR sources.
-
Average end-to-end delay of data packets ? This includes all possible delays caused
by buffering during route discovery latency, queuing at the interface queue,
retransmission delays at the MAC, and propagation and transfer times.
-
Normalized routing load ? The number of routing packets transmitted per data packet delivered at the destination. Each hop-wise transmission of a routing packet is counted as one transmission.
Evaluating Packet delivery fraction (pdf):
Calculate the number of "sent packets" that have the trace form:
|
/^s *- Nl AGT.*-Is (\d{1,3})\.\d{1,3} -Id (\d{1,3})\.\d{1,3}.*-It cbr.*-Ii (\d{1,6})/ |
AGT => Agent Level Trace
Calculate the number of "received packets" of the trace form:
|
/^r -t (\d{1,3}\.\d{9}).*-Nl AGT.*-Is (\d{1,3})\.\d{1,3} -Id (\d{1,3})\.\d{1,3}.*-It cbr.*-Ii (\d{1,6})/ |
|
packet delivery fraction (pdf %) = (received packets/ sent packets) *100 |
Evaluating Average End-End packet delivery time:
For each packet with id (Ii) of trace level (AGT) and type (cbr), calculate the send(s) time (t) and the receive (r) time (t) and average it.
Evaluating Normalized routing load:
Calculate the routing packet sent:
|
/^[s|f].*-Nl RTR.*-It (?:AODV|DSR|message) -Il (\d{1,4})/ |
f=> forward
RTR=> Routing Trace Level
|
Normalized routing load = (routing packets sent) / receives. |
[ 적용시 참고 내용 ]
grep -E (same as `egrep', --extended-regexp)
ex) grep -E '^(foo|bar)' file.txt
same as grep '^\(foo\|boar\)'
In basic regular expressions the metacharacters ?, +, {, |, (, and ) lose their special
meaning; instead use the backslashed versions \?, \+, \{, \|, \(, and \).

Comments List
移
以
以