Performance Analysis in Cross Layer protocol in IoT
Scenario 1: MCROSS Protocol With Static network
Step 1: Initially, we constructed an IoT network with 200 Sensor nodes , 1 Base Station (BS), and 1 Server .
Step 2: Then, we implement the MCROSS protocol with DSDMAC-based MAC layer optimization and directional communication.
Step 3: Next, we simulate the network and collect the multimedia network traffic data generated during transmission.
Step 4: Finally, we analyzed performance metrics for the following:
4.1 Number of Sensor Nodes Vs. Throughput
4.2 Number of Sensor Nodes Vs. Delay
4.3 Number of Sensor Nodes Vs. Energy Consumption
4.4 Number of Sensor Nodes Vs. Load
Scenario 2: CL-HHO Protocol With Static network
Step 1: Initially, we constructed an IoT network with 200 Sensor nodes , 1 Base Station (BS), and 1 Server .
Step 2: Then, we implement the CLHHO protocol using cross-layer Harris Hawk Optimization for adaptive route selection
Step 3: Next, we simulate the network and collect the multimedia network traffic data generated during transmission.
Step 4: Finally, we analyzed performance metrics for the following:
4.1 Number of Sensor Nodes Vs. Throughput
4.2 Number of Sensor Nodes Vs. Delay
4.3 Number of Sensor Nodes Vs. Energy Consumption
4.4 Number of Sensor Nodes Vs. Load
Scenario 3: ONCP Protocol With Static network
Step 1: Initially, we constructed an IoT network with 200 Sensor nodes , 1 Base Station (BS), and 1 Server .
Step 2: Then, we implement the ONCP protocol using modified PSO with crossover and mutation for optimal clustering and routing,
Step 3: Next, we simulate the network and collect the multimedia network traffic data generated during transmission.
Step 4: Finally, we analyzed performance metrics for the following:
4.1 Number of Sensor Nodes Vs. Throughput
4.2 Number of Sensor Nodes Vs. Delay
4.3 Number of Sensor Nodes Vs. Energy Consumption
4.4 Number of Sensor Nodes Vs. Load
Scenario 4: MCROSS Protocol With dynamic network
Step 1: Initially, we constructed an IoT network with 30 Sensor nodes (dynamic mobility) , 1 Base Station (BS), and 1 Server .
Step 2: Then, we implement the MCROSS protocol with DSDMAC-based MAC layer optimization and directional communication.
Step 3: Next, we simulate the network with dynamic mobility and collect the multimedia network traffic data generated during transmission.
Step 4: Finally, we analyzed performance metrics for the following:
4.1 Number of Sensor Nodes Vs. Throughput
4.2 Number of Sensor Nodes Vs. Delay
4.3 Number of Sensor Nodes Vs. Energy Consumption
4.4 Number of Sensor Nodes Vs. Load
Scenario 5: CL-HHO Protocol With dynamic network
Step 1: Initially, we constructed an IoT network with 30 Sensor nodes (dynamic mobility) , 1 Base Station (BS), and 1 Server .
Step 2: Then, we implement the CLHHO protocol using cross-layer Harris Hawk Optimization for adaptive route selection
Step 3: Next, we simulate the network with dynamic mobility and collect the multimedia network traffic data generated during transmission.
Step 4: Finally, we analyzed performance metrics for the following:
4.1 Number of Sensor Nodes Vs. Throughput
4.2 Number of Sensor Nodes Vs. Delay
4.3 Number of Sensor Nodes Vs. Energy Consumption
4.4 Number of Sensor Nodes Vs. Load
Scenario 6: ONCP Protocol With dynamic network
Step 1: Initially, we constructed an IoT network with 30 Sensor nodes (dynamic mobility), 1 Base Station (BS), and 1 Server .
Step 2: Then, we implement the ONCP protocol using modified PSO with crossover and mutation for optimal clustering and routing,
Step 3: Next, we simulate the network with dynamic mobility and collect the multimedia network traffic data generated during transmission.
Step 4: Finally, we analyzed performance metrics for the following:
4.1 Number of Sensor Nodes Vs. Throughput
4.2 Number of Sensor Nodes Vs. Delay
4.3 Number of Sensor Nodes Vs. Energy Consumption
4.4 Number of Sensor Nodes Vs. Load
Software Requirements:
1. Development Tool: NS 2 with Python
2. Operating System: Ubuntu 18.04 LTS (64-bit) or above
Note:
1) If the proposed plan does not fully align with your requirements, please provide all necessary details—including steps, parameters, models, and expected outcomes—in advance. Kindly ensure that any missing configurations or specifications are clearly outlined in the plan before confirming.
2) If there’s no built-in solution for what the project needs, we can always turn to reference models, customize our own, different math models or write the code ourselves to fulfil the process.
3) If the plan satisfies your requirement, Please confirm with us.
4) Project based on Simulation only.
| Technology | Ph.D | MS | M.Tech |
|---|---|---|---|
| NS2 | 75 | 117 | 95 |
| NS3 | 98 | 119 | 206 |
| OMNET++ | 103 | 95 | 87 |
| OPNET | 36 | 64 | 89 |
| QULANET | 30 | 76 | 60 |
| MININET | 71 | 62 | 74 |
| MATLAB | 96 | 185 | 180 |
| LTESIM | 38 | 32 | 16 |
| COOJA SIMULATOR | 35 | 67 | 28 |
| CONTIKI OS | 42 | 36 | 29 |
| GNS3 | 35 | 89 | 14 |
| NETSIM | 35 | 11 | 21 |
| EVE-NG | 4 | 8 | 9 |
| TRANS | 9 | 5 | 4 |
| PEERSIM | 8 | 8 | 12 |
| GLOMOSIM | 6 | 10 | 6 |
| RTOOL | 13 | 15 | 8 |
| KATHARA SHADOW | 9 | 8 | 9 |
| VNX and VNUML | 8 | 7 | 8 |
| WISTAR | 9 | 9 | 8 |
| CNET | 6 | 8 | 4 |
| ESCAPE | 8 | 7 | 9 |
| NETMIRAGE | 7 | 11 | 7 |
| BOSON NETSIM | 6 | 8 | 9 |
| VIRL | 9 | 9 | 8 |
| CISCO PACKET TRACER | 7 | 7 | 10 |
| SWAN | 9 | 19 | 5 |
| JAVASIM | 40 | 68 | 69 |
| SSFNET | 7 | 9 | 8 |
| TOSSIM | 5 | 7 | 4 |
| PSIM | 7 | 8 | 6 |
| PETRI NET | 4 | 6 | 4 |
| ONESIM | 5 | 10 | 5 |
| OPTISYSTEM | 32 | 64 | 24 |
| DIVERT | 4 | 9 | 8 |
| TINY OS | 19 | 27 | 17 |
| TRANS | 7 | 8 | 6 |
| OPENPANA | 8 | 9 | 9 |
| SECURE CRT | 7 | 8 | 7 |
| EXTENDSIM | 6 | 7 | 5 |
| CONSELF | 7 | 19 | 6 |
| ARENA | 5 | 12 | 9 |
| VENSIM | 8 | 10 | 7 |
| MARIONNET | 5 | 7 | 9 |
| NETKIT | 6 | 8 | 7 |
| GEOIP | 9 | 17 | 8 |
| REAL | 7 | 5 | 5 |
| NEST | 5 | 10 | 9 |
| PTOLEMY | 7 | 8 | 4 |