How to Calculate Network Served Number of users in NS2

To calculate the network served number of users in NS2, we required to regulate how many users (or nodes) effectively transfer and receive data in excess of the network for the duration of the replication period. This can be deduced as the number of nodes (users) that effectively transmit and/or receive packets.

The following is the step-by-step approach to calculating the number of served users in NS2:

Step-by-Step Implementation:

  1. Define the Simulation Setup

We should configure a network topology with multiple nodes, in which each node can behave as user. The nodes can interact with a base station, access point, or with each other. The served users are those nodes that effectively transmit and receive data.

  1. Generate a Trace File

In NS2, the trace file logs events like packets being sent, received, and dropped. We can utilize this trace file to classify that nodes successfully sent and received packets.

  1. Extract Served Users from the Trace File

We can regulate either a user was served by checking:

  • Packets Sent: If a node successfully sent packets.
  • Packets Received: If a node successfully received packets.

The users that have effectively sent or received packets for the period of the replication are considered “served.”

Example Tcl Script for NS2 Simulation:

Below is a sample NS2 script in which multiple users (nodes) are routing the information to a common receiver such as base station.

# Create a new simulator instance

set ns [new Simulator]

# Open trace file to record events

set tracefile [open trace.tr w]

$ns trace-all $tracefile

# Create 5 nodes (representing 5 users)

set num_nodes 5

for {set i 0} {$i < $num_nodes} {incr i} {

set node($i) [$ns node]

}

# Define UDP agents and attach them to the nodes (users)

for {set i 0} {$i < [expr $num_nodes-1]} {incr i} {

set udp($i) [new Agent/UDP]

set null($i) [new Agent/Null]

$ns attach-agent $node($i) $udp($i)

$ns attach-agent $node($num_nodes-1) $null($i)  # Last node as receiver

$ns connect $udp($i) $null($i)

# Create CBR traffic source and attach to the UDP agent

set cbr($i) [new Application/Traffic/CBR]

$cbr($i) attach-agent $udp($i)

$cbr($i) set packetSize_ 512

$cbr($i) set rate_ 1Mb

}

# Schedule start and stop times for the CBR traffic

for {set i 0} {$i < [expr $num_nodes-1]} {incr i} {

$ns at 1.0 “$cbr($i) start”

$ns at 4.0 “$cbr($i) stop”

}

$ns at 5.0 “finish”

# Define finish procedure

proc finish {} {

global ns tracefile

$ns flush-trace

close $tracefile

exit 0

}

# Run the simulation

$ns run

  1. Analyzing the Trace File

After executing the simulation, the trace file (trace.tr) will encompass lines that log sent and received events for each node (user). These events are tagged with node IDs.

Example Trace File Output:

s 1.000000 _0_ AGT — 512 [0 0 0 0] ——- [1:0 2:0 32 0]

r 1.100000 _4_ AGT — 512 [0 0 0 0] ——- [1:0 2:0 32 0]

s 1.000000 _1_ AGT — 512 [0 0 0 0] ——- [1:0 2:0 32 0]

r 1.100000 _4_ AGT — 512 [0 0 0 0] ——- [1:0 2:0 32 0]

s 1.000000 _2_ AGT — 512 [0 0 0 0] ——- [1:0 2:0 32 0]

r 1.100000 _4_ AGT — 512 [0 0 0 0] ——- [1:0 2:0 32 0]

  • The _0_, _1_, _2_ denote the node IDs of the users.
  • The s designates packet sent.
  • The r signifies packet received.
  1. Counting Served Users

A user is deliberated “served” if they have sent or received packets. we can count these events for each node using the following command-line script (Bash example).

Bash Script to Count Served Users:

# Get all unique nodes that sent packets

sent_nodes=$(grep “^s” trace.tr | awk ‘{print $3}’ | sort | uniq)

# Get all unique nodes that received packets

received_nodes=$(grep “^r” trace.tr | awk ‘{print $3}’ | sort | uniq)

# Merge the two sets of nodes and count unique served users

served_nodes=$(echo “$sent_nodes\n$received_nodes” | sort | uniq | wc -l)

echo “Number of served users: $served_nodes”

  1. Result Interpretation
  • The number of unique nodes (users) that have effectively routed or received data will give you the network served number of users.

Summary of Steps:

  1. Configure a multi-node NS2 simulation in which each node denotes a user.
  2. Create a trace file for the period of the simulation.
  3. Use grep and awk to classify nodes that sent or received packets.
  4. Summing up the unique nodes that have effectively interacted (sent or received packets).
  5. Result the total number of served users.

We had successfully calculated the network served number of users in ns2 simulation that has create the network topology then classify nodes to effectively communicated then it  analyse the results. We plan to provide the additional data on how to calculate the network served number of users in other simulation scenarios.

Drop us all of your parameter information, and our large staff will be available to assist you with the specifics of the networking comparison analysis. Keep in contact with us, and we’ll assist you with timely delivery and the best results possible. To determine the number of users served by the NS2 tool, it is recommended to seek our professional assistance.