How to Implement Network line switching in ns3

To implement the network line switching (otherwise called as circuit switching) in ns3, during the session there has to be some implementation of keen communication to do so we have to simulate the network. We have to implement line switching, so that it sets up a fixed path before the data transmission starts. But, in packet switching the data packets are routed separately.

Implementation and comparative analysis of network line switching in the ns3 tool has been conducted by our team. We encourage you to reach out to us for optimal results.

Now, we will provide the implementation process of the line switching network in ns3:

Step-by-Step Implementation:

Step 1: Setup ns3 Environment

Make certain that you have installed the ns3 in your computer and check the configuration.

git clone https://gitlab.com/nsnam/ns-3-dev.git

cd ns-3-dev

./waf configure

./waf build

Step 2: Create the Line Switching Simulation Script

For better communication, we will create a script that sets up a network with dedicated paths. In this script, we will see the simulation of executing a circuit and their data transmits through the path.

#include “ns3/core-module.h”

#include “ns3/network-module.h”

#include “ns3/internet-module.h”

#include “ns3/point-to-point-module.h”

#include “ns3/applications-module.h”

#include “ns3/flow-monitor-module.h”

using namespace ns3;

NS_LOG_COMPONENT_DEFINE(“LineSwitchingExample”);

int main(int argc, char *argv[])

{

CommandLine cmd;

cmd.Parse(argc, argv);

// Create nodes

NodeContainer nodes;

nodes.Create(4); // Four nodes in a simple line

// Create point-to-point links

PointToPointHelper p2p;

p2p.SetDeviceAttribute(“DataRate”, StringValue(“10Mbps”));

p2p.SetChannelAttribute(“Delay”, StringValue(“2ms”));

NetDeviceContainer devices;

devices = p2p.Install(nodes.Get(0), nodes.Get(1));

devices.Add(p2p.Install(nodes.Get(1), nodes.Get(2)));

devices.Add(p2p.Install(nodes.Get(2), nodes.Get(3)));

// Install the internet stack

InternetStackHelper stack;

stack.Install(nodes);

// Assign IP addresses

Ipv4AddressHelper address;

address.SetBase(“10.1.1.0”, “255.255.255.0”);

Ipv4InterfaceContainer interfaces = address.Assign(devices);

// Install applications to simulate line switching

uint16_t port = 9;

// Client on node 0 will establish a path to server on node 3

OnOffHelper onoff(“ns3::TcpSocketFactory”, Address(InetSocketAddress(interfaces.GetAddress(3), port)));

onoff.SetConstantRate(DataRate(“1Mbps”));

ApplicationContainer clientApps = onoff.Install(nodes.Get(0));

clientApps.Start(Seconds(1.0));

clientApps.Stop(Seconds(10.0));

// Install packet sink on the last node to receive packets

PacketSinkHelper sink(“ns3::TcpSocketFactory”, Address(InetSocketAddress(Ipv4Address::GetAny(), port)));

ApplicationContainer serverApps = sink.Install(nodes.Get(3));

serverApps.Start(Seconds(0.0));

serverApps.Stop(Seconds(10.0));

// Enable FlowMonitor to measure performance metrics

FlowMonitorHelper flowmon;

Ptr<FlowMonitor> monitor = flowmon.InstallAll();

// Run the simulation

Simulator::Stop(Seconds(10.0));

Simulator::Run();

// Print per-flow statistics

monitor->CheckForLostPackets();

Ptr<Ipv4FlowClassifier> classifier = DynamicCast<Ipv4FlowClassifier>(flowmon.GetClassifier());

std::map<FlowId, FlowMonitor::FlowStats> stats = monitor->GetFlowStats();

for (std::map<FlowId, FlowMonitor::FlowStats>::const_iterator i = stats.begin(); i != stats.end(); ++i)

{

Ipv4FlowClassifier::FiveTuple t = classifier->FindFlow(i->first);

NS_LOG_UNCOND(“Flow ” << i->first << ” (” << t.sourceAddress << ” -> ” << t.destinationAddress << “)”);

NS_LOG_UNCOND(”  Tx Packets: ” << i->second.txPackets);

NS_LOG_UNCOND(”  Tx Bytes:   ” << i->second.txBytes);

NS_LOG_UNCOND(”  Rx Packets: ” << i->second.rxPackets);

NS_LOG_UNCOND(”  Rx Bytes:   ” << i->second.rxBytes);

NS_LOG_UNCOND(”  Lost Packets: ” << i->second.lostPackets);

NS_LOG_UNCOND(”  Throughput: ” << i->second.rxBytes * 8.0 / (i->second.timeLastRxPacket.GetSeconds() – i->second.timeFirstTxPacket.GetSeconds()) / 1024 / 1024 << ” Mbps”);

}

// Clean up

Simulator::Destroy();

return 0;

}

Step 3: Compile and Run the Simulation

1. Compile the Simulation:

./waf configure –enable-examples

./waf build

2. Run the Simulation:

./waf –run scratch/line-switching-example

Step 4: Analyze Results

If we want the nodes to communication with the help of the dedicated paths, we have to simulate a script that sets up a better linear network then if we want to aggregate and print out statistics about the traffic flows, such as packet loss, throughput, and delay we have to use FlowMonitor.

Additional Considerations

To extend the functionality of your line switching simulation, follow the steps below:

1. Complex Topologies

First, we can simulate more realistic line switching scenarios by creating more complex network topologies (like rings, meshes).

2. Dynamic Path Setup

If we want the paths be established as per the requirements and be released once the session ends, we have to simulate more circuit switching networks by executing dynamic path setup and teardown.

3. Traffic Patterns

To comprehend the impact on the network, we have to simulate various kinds of traffic patterns like VoIP, Video Streaming.

4. Quality of Service (QoS)

We have to establish QoS mechanism, to make sure whether the complex data flows gets the necessary bandwidth and low latency and to prioritize certain kinds of traffic.

5. Performance Metrics

Finally, we can also accumulate and examine additional metrics includes jitter, packet delay variation, and error rates to evaluate the network performance more comprehensively.

Through the script, we were successfully providing the process on how to implement the network line switching in ns3 with the sample for your reference. We can also any further information about the line switching networks.