Multipoint to Point

Settings done in sample network

  1. Grid length(m) 100m, manually via Click and Drop.

  2. Routing protocol has set as RPL for 6LOWPAN Gateway and Sensor. Go to properties Network Layer Routing Protocol as shown Figure 4‑24.

Graphical user interface, text, application Description automatically generated

Figure 4‑24: Routing Protocol to RPL in Network layer

  1. In Adhoc Link Properties change Channel characteristics Path Loss only, Path Loss Model Log Distance and path loss exponent 4.2.

  2. Application properties has set as shown in below Table 4‑3.

Application Properties
Application ID Application Type Source Id Destination Id
1 SENSOR_APP 1 11
2 SENSOR_APP 3 11
3 SENSOR_APP 8 11

Table 4‑3: Application properties

  1. In NetSim GUI Plots and Packet Traces are Enabled. Run simulation 100s and observe that all the sensors are sending data to route node in animation window and also in packet trace.

    Result

    Animation window: The nodes send data messages to the root, creating an upward flow,

Figure 4‑25: Animation window for Multipoint to Point

Packet trace: Once the simulation is completed, to view the packet trace file, click on “Open Packet Trace” option present in the left-hand-side of the Results Dashboard and filter the PACKET_TYPE to Sensing. you can observe the flow of Sensor Application packets as shown below:

Figure 4‑26: Packet Trace for Multipoint to Point

Point to Multipoint#

Settings done in sample network

  1. Set the all the properties same as Multipoint to Point scenario

  2. Application properties has set as shown in below Table 4‑4.

Application Properties
Application ID Application Type Source Id Destination Id
1 SENSOR_APP 11 1
2 SENSOR_APP 11 3
3 SENSOR_APP 11 8

Table 4‑4: Application properties

  1. In NetSim GUI Plots are Enabled. Run simulation 100s and observe that all the sensors are sending data to route node in animation window and also in packet trace.

    Result

    Animation window: Root sends data messages to the other nodes, producing a downward flow.

Figure 4‑27: Animation window for Point to Multipoint

Packet trace: Once the simulation is completed, to view the packet trace file, click on “Open Packet Trace” option present in the left-hand-side of the Results Dashboard and filter the PACKET_TYPE to Sensing, you can observe the flow of Sensor Application packets as shown below:

Figure 4‑28: Packet trace for Point to Multipoint

Point to Point#

Settings done in sample network

  1. Set the all the properties same as Multipoint to Point scenario.

  2. Application properties has set as shown in below Table 4‑5.

Application Properties
Application ID Application Type Source Id Destination Id
1 SENSOR_APP 1 5

Table 4‑5: Application properties

  1. In NetSim GUI Plots are Enabled. Run simulation 100s and observe that all the sensors are sending data to route node in animation window and also in packet trace.

    Result

    Animation window: Root sends data messages to the other nodes, producing a downward flow.

Figure 4‑29: Animation window for Point to Point

Packet trace: Once the simulation is completed, to view the packet trace file, click on “Open Packet Trace” option present in the left-hand-side of the Results Dashboard and filter the PACKET_TYPE to Sensing, you can observe the flow of Sensor Application packets as shown below:

Figure 4‑30: Packet trace for Point to Point

Non-storing Mode#

Settings done in sample network

  1. Set the all the properties same as Multipoint to Point scenario.

  2. Application properties has set as shown in below table:

Application Properties
Application ID Application Type Source Id Destination Id
1 SENSOR_APP 3 8

Table 4‑6: Application properties

  1. In NetSim GUI Plots are Enabled. Run simulation 100s and observe > that all the sensors are sending data to route node in animation > window and also in packet trace.

    Result

    Animation window: In non-storing MOP (MOP 1 (Point to Multipoint)), downward routes are supported, and the use of P2P and MP2P is allowed. However, all downward routes are maintained in the root node. Thus, the total downward traffic should be initially sent to the DODAG root and subsequently be forwarded to its destination.

Figure 4‑31: Animation window for RPL Non-Storing Mode

Packet trace: Once the simulation is completed, to view the packet trace file, click on “Open Packet Trace” option present in the left-hand-side of the Results Dashboard and filter the PACKET_TYPE to Sensing, you can observe the flow of Sensor Application packets as shown below:

Figure 4‑32: Packet trace for RPL Non-Storing Mode

Storing Mode#

Settings done in sample network

  1. Set the all the properties same as Multipoint to Point scenario

  2. Application properties has set as shown in below Table 4‑7.

Application Properties
Application ID Application Type Source Id Destination Id
1 SENSOR_APP 3 8

Table 4‑7: Application properties

  1. In NetSim GUI Plots are Enabled. Run simulation 100s and observe that all the sensors are sending data to root node in animation window and also in packet trace.

    Result

    Animation window: In storing without multicast MOP (MOP 2 (Point to point)), downward routes are also supported, but are different from MOP 1 (Point to multipoint); the nodes maintain, individually, a routing table constructed using DAO messages to provide downward traffic. Hence, downward forwarding occurs without the use of the root node

Figure 4‑33: Animation window for RPL Storing Mode

Packet trace: Once the simulation is completed, to view the packet trace file, click on “Open Packet Trace” option present in the left-hand-side of the Results Dashboard and filter the PACKET_TYPE to Sensing, you can observe the flow of Sensor Application packets as shown below.

Figure 4‑34: Packet trace for RPL Storing Mode