QualNet 4.0 Model Library: Wireless

Transcription

1 QualNet 4.0 Model Library: Wireless December 2006 Scalable Network Technologies, Inc Center Drive West, Suite 520 Los Angeles, CA Phone: Fax: QualNet 4.0 Wireless Model Library 1

2 Copyright Information 2006 Scalable Network Technologies, Inc. All rights reserved. QualNet is a registered trademark of Scalable Network Technologies, Inc. All other trademarks and trade names used are property of their respective companies. Scalable Network Technologies, Inc Center Drive West, Suite 520 Los Angeles, CA Phone: Fax: QualNet 4.0 Wireless ModelLibrary

3 IEEE Standard Wireless Model Library The QualNet 4.0 Wireless Library contains many models that were previously in a model library named MANET for Mobile Ad-Hoc Networking. This technology enables communications by constantly reconfiguring itself. This library contains the following models, reading across the page: MAC Legacy MAC e MAC a/g PHY b PHY Abstract PHY Aloha AODV BRP CSMA DEM Directional Antenna DSR DTED DYMO Fading Fisheye State Routing Group Mobility IARP IERP ITM LANMAR LAR1 MACA ODMRP OLSR INRIA OLSRv2 Pedestrian Mobility Model Random Waypoint STAR TDMA Weather ZRP IEEE Standard The IEEE standard defines a set of MAC and PHY specifications for wireless LAN, also known as WiFi. It was developed by the IEEE working group. The original standard was developed in Later, several amendments have been proposed to extend at both the MAC and physical layers to support various features such as higher bandwidth, QoS, security, etc. These amendments are known as x. QualNet 4.0 implements the basic MAC and PHY models, as well as several amendments. Namely, QualNet 4.0 has following models: MAC QualNet 4.0 Wireless Model Library 3

4 Wireless Model Library Legacy MAC e MAC a/g PHY b PHY The MAC (the current version in QualNet 4.0) and Legacy MAC (the older version that was in QualNet up to version 3.8) are duplicate implementations of the IEEE MAC specifications. The Legacy MAC version of QualNet includes support to both Distributed Coordinate Function (DCF) and Point Coordinate Function (PCF). However, it is only an implementation of the coordinate functions without other management components and Access Point (AP) functionalities such as beaconing, channel scan, association, etc. The MAC on the other hand, is a more complete implementation which supports DCF as well as most management functionalities. However, since PCF is not widely used, the MAC doesn t support PCF. QualNet s MAC implementation of IEEE MAC supports the coordinate function Distributed Coordinate Function (DCF), as well as most management components and Access Point (AP) functionalities such as beaconing, channel scan, association, etc. With QualNet 4.0, we also support Power Save (PS) Mode for energy consumption at stations (STA s). QualNet s MAC does not, however, support Point Coordinate Function (PCF) since PCF is not widely used e MAC is an implementation of the QoS amendments to MAC specified in the IEEE e standard. It defines a new Hybrid Coordination Function (HCF), that provides an Enhanced Distributed Channel Access (EDCA) method and an HCF Controlled Channel Access (HCCA) method. The e MAC EDCA is basically a QoS extension to MAC DCF and e MAC HCCA is a kind of QoS extension to MAC PCF. The e MAC is not compatible with the MAC. IEEE standard has defined several PHY models in different amendments. The most widely known PHY models are b PHY, a PHY, and g PHY. The b PHY operates in a 2.4G frequency band and supports up to 11Mbps data rates. The a PHY operates in a 5G frequency band and supports up to 54Mbps data rates via OFDM technology. However, since a is not compatible with b, it didn t get widely used g PHY was proposed later to combine b PHY and a PHY. It supports a high data rate of up to 54Mbps and at the same time still operates in the 2.4 frequency band g PHY is compatible with b PHY. It supports both data rates of b PHY and a PHY. This is achieved by modifying the PHY PLCP header to bring necessary modulation information. QualNet has implemented both b PHY and a PHY as separated PHY models. Users can easily switch them via configurations. Please note, b and a are just PHY models. They need to work with MAC as well as other MAC variants such as e MAC. QualNet does not have a complete implementation of g PHY. However, since g PHY is a combination of b PHY and a PHY, you can still use a PHY to emulate the OFDM part of g PHY. QualNet cannot support coexisting b devices and g devices as a complete g PHY can. Because MAC and Legacy MAC are duplicate implementations, we suggest always using MAC. The only situation where Legacy MAC should be used is when you want to simulate the PCF capability. The e MAC is based on the MAC. So when e MAC configured, the MAC is automatically selected. The b and a PHY models are independent from MAC. Thus, they can work with MAC, Legacy MAC as well as e MAC. 4 QualNet 4.0 Wireless ModelLibrary

5 IEEE Standard Note: Legacy MAC is depreciated and may be removed from future releases. QualNet 4.0 Wireless Model Library 5

6 Wireless Model Library MAC The MAC is an implementation of the MAC specifications of the IEEE standard. It supports both infrastructure mode (also known as AP mode) and infrastructureless mode (also known as ad hoc mode). It has implemented management functionalities such as beaconing, channel scan, association/deassociation, power saving, etc. However, it only supports the distributed coordinate function (DCF). The point coordinate function (PCF) is not supported in this implementation. The DCF is a carrier-sensing protocol with acknowledgements, and provides optional channel reservation capability using Request-to- Send (RTS) / Clear-to-Send (CTS) Packets. The reference configuration in the IEEE MAC standard sets the longest propagation delay (one way) to be 1 microsecond, so the model requires parameter adjustments in order to allow a communication range of more than 300 meters. Note: There are no specific guidelines on how to adjust these parameters, because other parameters need to be changed to keep the slot time (10 microseconds) the same. Configuration To select the MAC as the MAC protocol in *.config, place the following entry in *.config: MAC-PROTOCOL MACDOT11 Note: The *.config file is the sample scenario input file. Table 1 shows the parameters used for MAC. TABLE 1. Parameters for MAC Parameter MAC-DOT11-AP MAC-DOT11-ASSOCIATION MAC-DOT11-DIRECTIONAL-ANTENNA- MODE MAC-DOT11-DIRECTION-CACHE- EXPIRATION-TIME MAC-DOT11-DIRECTIONAL-NAV-AOA- DELTA-ANGLE MAC-DOT11-DIRECTIONAL-SHORT- PACKET-TRANSMIT-LIMIT Description Set if the station is an AP. Default value is NO. Usage: MAC-DOT11-AP YES NO Types for nodes to associate with the AP with the SSID. NONE means no association. DYNAMIC will dynamically associate with a AP of the appropriate SSID. Default is NONE. Usage: MAC-DOT11-ASSOCIATION NONE DYNAMIC Specifies whether the radio will use directional antenna for transmissions. Note: The default is NO. Usage: MAC-DOT11-DIRECTIONAL-ANTENNA-MODE YES NO Specifies how long radio keeps track of last known direction of receiver (for directional antenna mode). Usage: MAC-DOT11-DIRECTION-CACHE-EXPIRATION-TIME 2S Specifies how much space (in degrees) is NAV'ed when the radio overhears frames to neighboring nodes (for directional antenna mode). Usage: MAC-DOT11-DIRECTIONAL-NAV-AOA-DELTA-ANGLE 37.0 Specifies how many times the radio tries transmitting control frames (RTS/CTS/ACK) directionally before going omni mode (for directional antenna mode). Usage: MAC-DOT11-DIRECTIONAL-SHORT-PACKET-TRANSMIT-LIMIT 4 6 QualNet 4.0 Wireless ModelLibrary

7 MAC TABLE 1. Parameters for MAC (Continued) MAC-DOT11-LONG-PACKET-TRANSMIT- LIMIT MAC-DOT11-RELAY-FRAMES MAC-DOT11-RTS-THRESHOLD MAC-DOT11-SCAN-TYPE MAC-DOT11-SHORT-PACKET- TRANSMIT-LIMIT MAC-DOT11-SSID Parameter MAC-DOT11-STA-CHANNEL MAC-DOT11-LONG-PACKET-TRANSMIT- LIMIT 4 Note: Parameters are not required. Description Transmission limit in waiting for ACK in response to data of length greater than RTS threshold. Default is 4. Usage: MAC-DOT11-LONG-PACKET-TRANSMIT-LIMIT 4 Specify if the AP relays frames to wireless nodes outside the BSS. The default is YES, the AP relays frames. Usage: MAC-DOT11-RELAY-FRAMES YES NO Determine whether RTS/CTS is used based on data packet size. If data packet size is greater than MAC-DOT11-RTS-THRESHOLD, then RTS/CTS is used. 0 means always used RTS/CTS. Broadcast data packets NEVER use RTS/CTS. Default is 0. Usage: MAC-DOT11-RTS-THRESHOLD 0 Type of scanning the dynamic association will use to find an AP to associate with. DISABLED means no channel scan. ACTIVE will actively probe channels to find an AP. PASSIVE means no probing. Passively listen to channels for beacons. Default value is DISABLED. Usage: MAC-DOT11-SCAN-TYPE DISABLED ACTIVE PASSIVE Specifies transmission limit in waiting for CTS/ACK frames. Note: Default is 7. Usage: MAC-DOT11-SHORT-PACKET-TRANSMIT-LIMIT 7 Sets the SSID of the station/ap. This is also the SSID of the AP (BSS) to associate with. Default is "NONE". Usage: MAC-DOT11-SSID <name-string> Sets the channel to start listening on for a dynamic association. Default is 0. Usage: MAC-DOT11-STA-CHANNEL <channel-index> Specifies transmission limit in waiting for ACK in response to data of length greater than RTS threshold. Note: Default is 4. Usage: MAC-DOT11-LONG-PACKET-TRANSMIT-LIMIT 4 Statistics Table 2 lists the basic statistics collected by the MAC. TABLE 2. Basic Statistics for MAC Statistic Description MAC,UNICAST packets sent to channel Total number of unicast data packets sent to the channel during contention free period and DCF MAC,BROADCAST packets sent to channel Total number of broadcast data packets sent to the channel during contention free period and DCF QualNet 4.0 Wireless Model Library 7

8 Wireless Model Library TABLE 2. Basic Statistics for MAC MAC,UNICAST packets received clearly MAC,BROADCAST packets received clearly DCF,Unicasts sent DCF,Broadcasts sent DCF,Unicasts received DCF,Broadcasts received DCF,CTS packets sent DCF,RTS packets sent DCF,ACK packets sent DCF,RTS retransmissions due to timeout DCF,Packet retransmissions due to ACK timeout DCF,Packet drops due to retransmission limit Total number of unicast data packets successfully received from the channel during contention free period and DCF Total number of broadcast data packets successfully received from the channel during contention free period and DCF. Number of unicast data packets sent under DCF Number of broadcast data packets sent under DCF Number of unicast data packets received under DCF Number of broadcast data packets received under DCF Number of CTS packets sent under DCF Number of RTS packets sent under DCF Number of ACK packets sent under DCF Number of RTS packets retransmissions due to timeout for waiting CTS under DCF. Number of data packets retransmissions due to timeout for waiting the ACK under DCF. Number of data packets dropped due to retransmissions exceeds the limit. Table 3 shows the management statistics for MAC TABLE MAC Management Statistics Statistic MGMT, Management packets sent to channel MGMT, Management packets received from channel MGMT, Beacons received MGMT, Beacons sent Description Number of management frames sent to the channel. Number of management frames received from the channel. Number of beacons received. Number of beacons sent. Configuring MAC in the GUI In the GUI, MAC can be enabled for a wireless sub network, for a specific node, for a specific interface, as well as globally for all nodes. According to QualNet s way of working, node-wise specification overrides global specification like all other protocol specifications. To configure MAC for a specific node in the GUI, perform the following steps: 1. Select Hierarchy -> Nodes -> host #-> Node configurations -> MAC Protocol -> MAC Protocol. a. In the Properties Explorer, click on the Configurable Property tab and set MAC Protocol to , as shown in Figure 1 and Figure 2. b. In the Properties Explorer, click on the Detailed Properties tab and set MAC parameters to their desired values, as shown in selecting Legacy MAC as the MAC Protocol and Setting Parameters. 8 QualNet 4.0 Wireless ModelLibrary

9 MAC FIGURE 1. Selecting MAC as the MAC Protocol QualNet 4.0 Wireless Model Library 9

10 Wireless Model Library FIGURE 2. Setting Parameters 2. Select Hierarchy -> Nodes -> host #-> Node configurations -> MAC Protocol -> MAC Protocol -> Station Association Type. a. In the Properties Explorer, click on the Configurable Property tab and set Station Association Type to Dynamic, as shown in Configuring Association Type and Scan Type. b. In the Properties Explorer, click on the Detailed Properties tab and set scan type and other parameters to their desired values, as shown in Configuring Association Type and Scan Type. See Figure 3 and Figure QualNet 4.0 Wireless ModelLibrary

11 MAC FIGURE 3. Configuring Association Type QualNet 4.0 Wireless Model Library 11

12 Wireless Model Library FIGURE 4. Configuring Scan Type 3. Select Hierarchy -> Nodes -> host #-> Node configurations -> MAC Protocol -> MAC Protocol -> Station Association Type -> Is Access Point (AP)? a. In the Properties Explorer, click on the Configurable Property tab and set Is Access Point (AP)? to Yes, if the node is an access point, as shown in Configuring Access Point. b. If the node is configured to be an access point, in the Properties Explorer, click on the Detailed Properties tab and set the parameters to their desired values, as shown in Configuring Access Point. See Figure 5 and Figure QualNet 4.0 Wireless ModelLibrary

13 MAC FIGURE 5. Configuring Access Point - 1 QualNet 4.0 Wireless Model Library 13

14 Wireless Model Library FIGURE 6. Configuring Access Point QualNet 4.0 Wireless ModelLibrary

15 MAC PS-Mode MAC PS-Mode The IEEE standard defined the Power Save (PS) Mode for energy consumption at stations (STA s). Use of this mode results in a decreased energy consumption. Three distinct building blocks are provided to support power savings: a Wakeup Procedure, a Sleep Procedure, and a Power-Save Poll (PS-Poll) Procedure. An STA can combine these power management building blocks for different applications. Wakeup Procedure: There are two reasons for the STA to wake up: to transmit pending data or to retrieve buffered data from an Access Point (AP). Waking up to transmit data is a straightforward operation, driven by the STA. The decision to wake up and receive data is also made by the STA after monitoring its pending data bit in a periodic beacon frame sent out by its AP. Once STA decides to transition from sleep mode to active mode, it notifies the AP by sending an uplink frame with the Power- Save (PS) bit set to active. Following such transmissions, STAs remain active so the AP can send any buffered downlink frames. Sleep Procedure: Similar to the wakeup procedure, STA in the active mode must complete a successful STA-initiated frame exchange sequence with the PS bit set to sleep, to transition into the sleep mode. Following this operation, the AP buffers all the downlink frames to this STA. PS-Poll Procedure: Instead of waiting for the AP to transmit the buffered downlink frames, the STA in sleep mode can solicit an immediate delivery from its AP by using a PS-Poll frame. Upon receiving this PS-Poll, the AP can immediately send a buffered downlink frame (immediate data response) or simply send an acknowledgement message and response with a buffered data frame later (delayed data response). For the immediate data response case, the STA can stay in the sleep state after finishing this frame exchange since there is no need for the STA to transition to the active state given that the AP can only send a buffered downlink frame in response to the PS-poll from the STA. For the delayed data response case, the STA must transition to the active state until receiving a downlink frame from the AP. Configuration Table 4 shows the Configurable parameters for PS Mode, there Default Value and Permissible range/value. TABLE 4. Configurable Parameters for PS Mode Parameter Default Value Permissible Range/Value MAC-DOT11-STA-PS-MODE-ENABLED NO YES/NO MAC-DOT11-AP-SUPPORT-PS-MODE NO YES/NO MAC-DOT11-DTIM-PERIOD (In Beacon Interval) MAC-DOT11-STA-PS-MODE-LISTEN-INTERVAL (In Beacon Interval) MAC-DOT11-STA-PS-MODE-LISTEN-DTIM-FRAME YES YES/NO MAC-DOT11-IBSS-SUPPORT-PS-MODE NO YES/NO ATIM DURATION (In TU) 20 ITU - Beacon Interval MAC-DOT11-IBSS-BEACON-START-TIME (In TU) 1 ITU - Beacon Interval MAC-DOT11-IBSS-BEACON-INTERVAL (In TU) QualNet 4.0 Wireless Model Library 15

16 Wireless Model Library Configuring Using the Simulator Table 5 shows the parameters required for configuring PS mode at AP in Infrastructure/AP mode: TABLE 5. Parameters Required for Configuring Power Save Mode at Access Point Parameter [nodeid] MAC-DOT11-DTIM-PERIOD 3 [nodeid] MAC-DOT11-AP-SUPPORT- PS-MODE YES/NO Definition The DTIM Period field indicates the number of Beacon intervals between DTIM frames. After transmission of a beacon containing a DTIM, AP transmits all broadcast and multicast data. The default value for this parameter is 3 Beacon Intervals that is DTIM Frame is transmitted with in every third beacon. This parameter defines whether or not AP supports PS mode. If it is Yes, AP transmits TIM/DTIM information along with the beacon and buffers packet for STA which are in Sleep Mode. The default value for this parameter is NO. Table 6 shows the parameters required for configuring PS mode at STAs in Infrastructure mode: TABLE 6. Parameters Required for Configuring PS Mode at STAs Parameter [nodeid] MAC-DOT11-STA-PS-MODE- ENABLED YES/NO [nodeid] MAC-DOT11-STA-PS-MODE- LISTEN-INTERVAL10 [nodeid] MAC-DOT11-STA-PS-MODE- LISTEN-DTIM-FRAME YES/NO Definition This parameter defines whether PS Mode is enabled or disabled at STA. If it is Yes, and the joined AP supports PS Mode, STA changes its state from awake to doze and vice versa. The default value for this parameter is No. The Listen Interval is used to indicate to the AP how often an STA wakes to listen to Beacon management frames. The unit for this parameter is the beacon interval, and the default value for this parameter is 10 beacon intervals. If the parameter MAC-DOT11-PS-MODE-STA-LISTEN-DTIM- FRAME value is Yes, STA receives DTIM frames from AP. In that case, STAs change to awake state after expiration of listen interval or DTIM period. If the value of this parameter is No, STA changes to the awake state only after the expiration of the listen interval. Table 7 shows the parameters required for configuring PS mode in Ad Hoc Mode: TABLE 7. Parameters Required for Configuring PS Mode in Ad Hoc Mode Parameter [network-address] MAC-DOT11-IBSS- BEACON-INTERVAL 150 [network-address] MAC-DOT11-IBSS- BEACON-START-TIME 1 Definition This parameter is used to define the beacon interval in ad hoc mode. The default value for this variable is 200 TU (Time Units). This parameter is used to define the beacon start time for the subnet. The default value for this variable is TU (Time Units). Beacon start time is the time when the node hits the first beacon transmission in ad hoc mode. 16 QualNet 4.0 Wireless ModelLibrary

17 MAC PS-Mode TABLE 7. Parameters Required for Configuring PS Mode in Ad Hoc Mode Parameter [network-address] MAC-DOT11-IBSS- BEACON-INTERVAL 150 [network-address] MAC-DOT11-IBSS- PS-MODE-ATIM-DURATION 20 [network-address] MAC-DOT11-IBSS- SUPPORT-PS-MODE YES/NO Definition This parameter is used to define the beacon interval in ad hoc mode. The default value for this variable is 200 TU (Time Units). The ATIM Window is defined as a specific period of time, during which only Beacon or ATIM frames shall be transmitted. The default value for this parameter is 20 TU (Time Units). ATIM duration period should be less than beacon interval. The default value for this parameter is No. Configuring Using the GUI/Animator Use the following steps to configure MAC DOT11 in the GUI: 1. Configure the parameter in Figure 7, if association type is Dynamic and station type is AP: Parameter must be configured as AP. Is AP support Power Save Mode? YES/NO DTIM period. In terms of number of beacon interval. FIGURE 7. Association Type is Dynamic, Station Type is AP 2. Configure the parameters shown in Figure 8 in configurable property section, if the station association type is Dynamic and node is not AP: QualNet 4.0 Wireless Model Library 17

18 Wireless Model Library Parameter must be configured at STA. Is Power Save Mode enabled? YES/NO FIGURE 8. Station Type Dynamic, Node is Not AP 3. Configure the parameters shown in Figure 9 in detailed properties section, if the station association type is Dynamic and node is not AP. Set YES for the parameter Is Power save mode enabled? 18 QualNet 4.0 Wireless ModelLibrary

19 MAC PS-Mode Parameter must be configured at STA. Listen Interval: In terms of number of beacon intervals. Received DTIM Frame? YES/NO FIGURE 9. Setting Listen Interval and Receive DTIM Frame 4. Configure the parameters shown in Figure 10 if the station association type is NONE: QualNet 4.0 Wireless Model Library 19

20 Wireless Model Library Is IBSS Subnet Support Power Save Mode enabled? YES/NO FIGURE 10. Enabling IBSS Subnet Support in Power Save Mode 5. Configure the parameters in Figure 11 if the station association type is None. Set YES for the parameter Is Power save mode enabled?: 20 QualNet 4.0 Wireless ModelLibrary

21 MAC PS-Mode 1. Beacon Start Time in TU (Time Unit). 2. Beacon Interval in TU. 3. ATIM Duration in TU. FIGURE 11. Setting Beacon Start Time, Beacon Interval, and ATIM Duration Statistics MAC PS mode provides statistics for the Infrastructure/AP mode (see Table 8) and for the IBSS mode (see Table 9). QualNet 4.0 Wireless Model Library 21

22 Wireless Model Library TABLE 8. Infrastructure/AP Mode Statistics Statistics <nodeid>,,, MAC, MAC, PS Poll Requests Sent <nodeid>,,, MAC, MGMT, PS Mode DTIM Frames Received <nodeid>,,, MAC, MGMT, PS Mode TIM Frames Received <nodeid>,,, MAC, MAC, PS Poll Requests Received <nodeid>,,, MAC, MAC, PS Poll Requests Received <nodeid>,,, MAC, MAC, PS Mode Broadcast Data Packets Sent <nodeid>,,, MAC, MGMT, PS Mode Unicast Data Packets Sent <nodeid>,,, MAC, MGMT, PS Mode TIM Frames Sent Definition Number of PS Poll request packets sent by STA. Number of DTIM frame STA received from AP. Number of TIM frame STA received from AP. Number of PS Poll request received by AP. Number of unicast data packet AP transmits in PS Mode. Number of broadcast data packet AP transmits in PS Mode. Number of DTIM frame AP transmits. Number of TIM frame AP transmits. TABLE 9. IBSS Mode Statistics Statistic <nodeid>,,, MAC, MGMT, Beacons received <nodeid>,,, MAC, MGMT, Beacons sent <nodeid>,,, MAC, MGMT, Management ATIM Frames Sent <nodeid>,,, MAC, MGMT, Management ATIM Frames Received <nodeid>,,, MAC, MAC, PS Mode Broadcast Data Packets Sent <nodeid>,,, MAC, MGMT, PS Mode Unicast Data Packets Sent Definition Number of Beacons received by STA in ad hoc mode Number of Beacons STA transmits in ad hoc mode Number of ATIM Frames STA transmits. Number of ATIM Frames received by STA. Number of broadcast data packet STA transmits in PS Mode. Number of Unicast data packets STA transmits in PS Mode. Examples The following example scenarios are provided: Ad Hoc mode Infrastructure mode Example Scenario for Ad Hoc Mode The following scenario test the functionality of QualNet PS model for Ad Hoc mode. 22 QualNet 4.0 Wireless ModelLibrary

23 MAC PS-Mode [1] [2] \ / \ / \ / \ / \ / [6] [3] / \ / \ / \ / \ / \ [5] [4] Six nodes are present in a subnet. Node 2 is sending 100 packets to node 4. Similarly, Node 5 is sending 100 packets to node 3. Using the Simulator Use the following code to create this scenario using the Simulator: SIMULATION-TIME 30S SUBNET N { 1 thru 6 } [ N ] MAC-PROTOCOL MACDOT11 [ N ] MAC-DOT11-ASSOCIATION DYNAMIC [ N ] MAC-DOT11-SCAN-TYPE PASSIVE [ N ] MAC-DOT11-SSID Test1 [ N ] MAC-DOT11-STA-CHANNEL 1 [ 1 ] MAC-DOT11-AP YES [ 1 ] MAC-DOT11-DTIM-PERIOD 3 [ 1 ] MAC-DOT11-AP-SUPPORT-PS-MODE YES [ 1 ] MAC-DOT11-BEACON-START-TIME 1 [ 1 ] MAC-DOT11-BEACON-INTERVAL 200 [ 1 ] MAC-DOT11-RELAY-FRAMES YES [ 1 ] MAC-DOT11-SCAN-TYPE DISABLED [ 2 thru 4 ] MAC-DOT11-STA-PS-MODE-ENABLED YES [ 2 thru 4 ] MAC-DOT11-STA-PS-MODE-LISTEN-INTERVAL 10 [ 2 thru 4 ] MAC-DOT11-STA-PS-MODE-LISTEN-DTIM-FRAME YES Using Animator Follow these steps to create this scenario using Animator: 1. Create a new scenario. 2. Select the Device tab from the Scenario Designer window and then select the Default icon and place six nodes. 3. Select Wireless Subnet and place a wireless cloud. 4. Connect all the six nodes with the Wireless Subnet by first selecting the Links tab in the ScenarioDesigner window, and then selecting link to create a Wireless link between the six nodes and the Wireless cloud. 5. Using the Inspector Window navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol->MAC Protocol. Set as the MAC PROTOCOL using the Configurable Property window as shown Figure 12. QualNet 4.0 Wireless Model Library 23

24 Wireless Model Library FIGURE 12. Configurable Property Window 6. Click Detailed Properties to configure the following parameters, as shown in Figure 13: AP Address Short Packet Transmit limit Long Packet Transmit limit RTSthreshold 24 QualNet 4.0 Wireless ModelLibrary

25 MAC PS-Mode FIGURE Using the Inspector Window, navigate to Wireless Subnet N >Wireless Subnet Properties->MAC Protocol-> MAC Protocol->Station Association Type. Set Station Association Type to None using the Configurable Property window as shown in Figure 14. QualNet 4.0 Wireless Model Library 25

26 Wireless Model Library FIGURE Using the Inspector Window, Navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol-> MAC Protocol->Station Association Type->Is IBSS support Power Save Mode? Set the value of Is IBSS support Power Save Mode? to YES using the Configurable Property window as shown below. Click the Detailed Properties to configure the following parameters and see Figure 15. Beacon Start Time (TU) Beacon Interval (TU) ATIM Duration (TU) 26 QualNet 4.0 Wireless ModelLibrary

27 MAC PS-Mode FIGURE Select the Applications tab of Scenario Designer window. Select CBR and set the application between Node 2 and Node 4. Similarly, between Node 5 and Node 3. Set the Application Parameters using the Configurable Property window. 10. Save the changes by clicking on the Save button. Click on the Run button. Click on the Play button to execute the scenario. 11. On completion of the Scenario execution, check the corresponding Statistics for the desired results. QualNet 4.0 Wireless Model Library 27

28 Wireless Model Library Example Scenario for Infrastructure Mode The following scenario tests the functionality of QualNet PS model for Infrastructure mode [1] [2] \ / \ / \ / \ / \ / [6] [3] / \ / \ / \ / \ / \ [5] [4] Six nodes are present in a subnet. Node 1 is AP. Nodes 2, 3, and 4 are in PS Mode. Node 2 is sending 100 packets node 4. Similarly, Node 5 is sending 100 packets to node 3. Using Simulator Use the following code to create this scenario using the Simulator: SIMULATION-TIME 30S SUBNET N { 1 thru 6 } [ N ] MAC-PROTOCOL MACDOT11 [ N ] MAC-DOT11-ASSOCIATION NONE [ N ] MAC-DOT11-IBSS-SUPPORT-PS-MODE YES [ N ] MAC-DOT11-IBSS-BEACON-START-TIME 1 [ N ] MAC-DOT11-IBSS-BEACON-INTERVAL 200 [ N ] MAC-DOT11-IBSS-PS-MODE-ATIM-DURATION 20 Using the Animator Follow these steps to create this scenario using Animator: 1. Create a new scenario. 2. Select the Device tab from the Scenario Designer window and then select the Default icon and place six nodes. 3. Select Wireless Subnet and place a wireless cloud. 4. Connect all the six nodes with the Wireless Subnet by first selecting the Links tab in the ScenarioDesigner window, and then selecting link to create a Wireless link between the six nodes and the Wireless cloud. 5. Using the Inspector Window navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol->MAC Protocol. Click Detailed Properties to configure the following parameters, as shown in Figure 16: AP Address Short Packet Transmit limit Long Packet Transmit limit RTSthreshold 28 QualNet 4.0 Wireless ModelLibrary

29 MAC PS-Mode FIGURE Using the Inspector Window, navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol-> MAC Protocol->Station Association Type. Set Station Association Type to Dynamic using the Configurable Property window as shown in Figure 17. Click the Detailed Properties window to configure: Station Scan Type SSID Channel QualNet 4.0 Wireless Model Library 29

30 Wireless Model Library FIGURE Enable PS mode for Node 2, 3, and 4. Go to Hierarchy (0) ->Nodes ->host2 ->Node Configurations- >MAC PROTOCOL->MAC PROTOCOL->Station Association Type. Set Station Association Type to Dynamic using the Configurable Property window. Click the Detailed Properties window to configure the following and see Figure 18. Station Scan Type SSID Channel 30 QualNet 4.0 Wireless ModelLibrary

31 MAC PS-Mode FIGURE Go to Hierarchy (0) ->Nodes ->host2 ->Node Configurations->MAC PROTOCOL->MAC PROTOCOL->Station Association Type->Is Power saving mode Enable? Set value of Is Power Saving mode Enabled? to Yes using the Configurable Property window. Click the Detailed Properties window to configure the following and see Figure 19. Listen Interval Receive DTIM Frame QualNet 4.0 Wireless Model Library 31

32 Wireless Model Library FIGURE 19. Similarly, enable PS mode for Node 2, 3, and Configure host 1 as AP. Go to Hierarchy (0) -> Nodes -> host1 -> Node Configurations->MAC PROTOCOL-MAC PROTOCOL->Station Association Type. Set value of Station Association Type to DYNAMIC. Click the Detailed Properties window to configure the following and see Figure 20. Station Scan Type SSID Channel 32 QualNet 4.0 Wireless ModelLibrary

33 MAC PS-Mode FIGURE Go to Hierarchy (0)->Nodes->host1->Node Configurations->MAC PROTOCOL-MAC PROTOCOL- >Station Association Type->Is Access Point? Set value of Is Access Point? to Yes. Click the Detailed Properties window to configure the following and see Figure 21. DTIM Period Is AP Support PS Mode Beacon Start Time Beacon Interval Relay Frames QualNet 4.0 Wireless Model Library 33

34 Wireless Model Library FIGURE Select the Applications tab of Scenario Designer window. Select CBR and set the application between Node 2 and Node 4. Similarly, between Node 5 and Node 3. Set the Application Parameters using the Configurable Property window. 12. Save the changes by clicking on the Save button. Click on the Run button. Click on the Play button to execute the scenario. 13. On completion of the Scenario execution, check the corresponding Statistics for the desired results. 34 QualNet 4.0 Wireless ModelLibrary

35 Legacy MAC Legacy MAC The legacy MAC is the older implementation of the MAC specifications of the IEEE standard. It is not a full implementation. In fact, it only supports the coordinate functions, including the Distributed Coordination Function (DCF) and Point Coordination Function (PCF). The Legacy MAC is also capable to operate directional antennas.legacy MAC-DCF Legacy MAC-DCF The Legacy MAC-DCF is a carrier-sensing protocol with acknowledgements, and provides optional channel reservation capability using Request-to-Send (RTS) / Clear-to-Send (CTS) Packets, and fragmentation. The reference configuration in the IEEE MAC standard sets the longest propagation delay (one way) to be 1 microsecond, so the model requires parameter adjustments in order to allow a communication range of more than 300 meters. Note: There are no specific guidelines on how to adjust these parameters, because other parameters need to be changed to keep the slot time (10 microseconds) the same. Configuration and Parameters To select the Legacy MAC-DCF as the MAC protocol in *.config, place the following entry in *.config: MAC-PROTOCOL MAC Note: The *.config file is the sample scenario input file. Table 10 shows the parameters used for Legacy MAC-DCF. TABLE 10. Parameters for Legacy MAC-DCF Parameter MAC DIRECTIONAL-ANTENNA- MODE MAC DIRECTION-CACHE- EXPIRATION-TIME MAC DIRECTIONAL-NAV-AOA- DELTA-ANGLE MAC DIRECTIONAL-SHORT- PACKET-TRANSMIT-LIMIT Description Specifies whether the radio will use directional antenna for transmissions. Note: The default is NO. Usage: MAC DIRECTIONAL-ANTENNA-MODE YES NO Specifies how long radio keeps track of last known direction of receiver (for directional antenna mode). Usage: MAC DIRECTION-CACHE-EXPIRATION-TIME Specifies how much space (in degrees) is NAV'ed when the radio overhears frames to neighboring nodes (for directional antenna mode). Usage: MAC DIRECTIONAL-NAV-AOA-DELTA-ANGLE Specifies how many times the radio tries transmitting control frames (RTS/CTS/ACK) directionally before going omni mode (for directional antenna mode). Usage: MAC DIRECTIONAL-SHORT-PACKET-TRANSMIT- LIMIT QualNet 4.0 Wireless Model Library 35

36 Wireless Model Library TABLE 10. Parameters for Legacy MAC-DCF (Continued) Parameter MAC SHORT-PACKET-TRANSMIT- LIMIT MAC LONG-PACKET-TRANSMIT- LIMIT MAC RTS-THRESHOLD Description Specifies transmission limit in waiting for CTS/ACK frames. Note: Default is 7. Usage: MAC SHORT-PACKET-TRANSMIT-LIMIT 7 Specifies transmission limit in waiting for ACK in response to data of length greater than RTS threshold. Note: Default is 4. Usage: MAC LONG-PACKET-TRANSMIT-LIMIT 4 Determine whether RTS/CTS is used based on data packet size. If data packet size is greater than MAC RTS- THRESHOLD, then RTS/CTS is used. 0 means always used RTS/CTS. Broadcast data packets NEVER use RTS/CTS. Default is 0. Usage: MAC RTS-THRESHOLD 0 Note: Parameters are not required. Statistics Table 11 lists the statistics collected by the Legacy MAC-DCF. TABLE 11. Statistics for Legacy MAC-DCF Statistic Packets From Network Packets Lost to Buffer Overflow Unicast packets to channel Broadcast packets to channel Unicast packets from channel Broadcast packets from channel Retransmitted Packets due to CTS timeout Retransmitted Packets due to ACK timeout Retransmitted Fragments due to Frag ACK timeout Packets drops due to excessive retransmission attempts Packet drops due to excessive retransmission attempts of fragments Explanation Packets received from Network Layer Protocol, i.e. IPv4 Packets dropped at the MAC layer due to buffer overflow Packets with a specific destination address transmitted on the channel Packets broadcast to all radios within transmission range Packets destined for this specific radio and successfully received Packets destined for all radios and successfully received by this radio Packets rescheduled for transmission due to lack of CTS response to RTS transmission Packets rescheduled due to lack of ACK response to packet transmission Fragments of packets retransmitted due to lack of acknowledgement of the fragment Packets not rescheduled after exceeding the maximum number of attempts Packets not rescheduled after exceeding the maximum number of unsuccessfully delivered fragments 36 QualNet 4.0 Wireless ModelLibrary

37 Legacy MAC Legacy MAC-PCF The Legacy MAC-PCF requires that a BSS be input via the SUBNET statement. A node within the BSS may be an Access Point. When the AP is also a Point Coordinator, additional inputs allow the configuration of the contention-free period. Configuration and Parameters This example shows a BSS with 10 nodes. Node 3 is a PC. SUBNET N4-1.0 { 1 thru 10 } [N4-1.0] MAC-PROTOCOL MAC [N4-1.0] MAC AP 3 [3] MAC PC YES Stations associate statically with the AP. If a station is out of range of the AP as a result of node placement or mobility, it may be unable to communicate. The implementation does not support overlapping CFPs for overlapping BSSs. In such situations, we suggest using different CFP start times or, better still, different channels or frequencies. Table 12 shows the configuration parameters. TABLE 12. Parameters for Legacy MAC-PCF Parameter MAC AP MAC RELAY-FRAMES MAC PC MAC BEACON-INTERVAL MAC BEACON-START-TIME Description Identifies the AP of the subnet. If no AP is given, the behavior is equivalent to that of an ad hoc network. Usage: [N4-1.0] MAC AP <node identification or interfaceaddress> Configures whether the AP (or PC) sends or receives frames to wireless nodes outside the BSS. Note: The default is YES, the AP relays frames. Usage: MAC RELAY-FRAMES YES NO Specifies that the AP would also behave as a Point Coordinator. Note: The default is NO, the AP does not operate as a PC with contention-free periods. Usage: [node identification or interfaceaddress] MAC PC YES NO Configures the target interval between PCF beacons or the contention-free period. The PCF beacon starts every CFP. Note: Default is 200 TUs or about 0.2 seconds. The max value is TUs. (1 Time Unit = 1024 microseconds). Usage: MAC BEACON-INTERVAL 200 Configures the time offset for first beacon. Specify the start time of the first CFP from start of simulation. This offset is useful to prevent overlapping CFPs in neighboring BSSs. Note: The default is 1 TU. The max value is the same as the CFP interval (beacon interval). Usage: MAC BEACON-START-TIME 1 QualNet 4.0 Wireless Model Library 37

38 Wireless Model Library TABLE 12. Parameters for Legacy MAC-PCF (Continued) Parameter MAC PC-CONTENTION-FREE- DURATION MAC PC-DELIVERY-MODE MAC PC-POLL-SAVE MAC PC-POLL-SAVE-MIN 1 MAC STATION-POLL-TYPE MAC PCF-STATISTICS Description Configures the CFP duration. Note: The default is 50 TUs. The minimum value is approximately 17 TUs. The maximum value is smaller than the CFP interval to allow some frame transfer during the contention period. Usage: MAC PC-CONTENTION-FREE-DURATION 50 During the contention-free period, the PC can have variations in its mode of coordination: POLL-ONLY. The PC polls stations in turn. If the round of pollable stations completes before the CFP duration, the CFP terminates. POLL-AND-DELIVER. The PC behavior is similar to the POLL-ONLY mode except that if the round of poll completes before the CFP duration, the PC would use the balance time to deliver packets in its queue. DELIVER-ONLY. The PC does not poll stations. Instead, the PC dequeues and transmits packets to stations during the CFP. Note: The default mode is POLL-AND-DELIVER. Usage: MAC PC-DELIVERY-MODE POLL-ONLY POLL- AND-DELIVER DELIVER-ONLY Specifies whether or not the PC attempts to minimize polls (by avoiding polling stations that seem idle) during CFP. Note: By default, poll-saving is enabled or BY-COUNT; the PC keeps track of null data response and absence of transmits by a pollable station. If set to NONE, the PC polls all pollable stations in a round-robin fashion. Usage: MAC PC-POLL-SAVE BY-COUNT NONE For poll-saving BY-COUNT, the poll-save can be qualified with a min. count value that prevents the PC from precipitately skipping polls in case the station is unable to respond due to other factors. Note: Default value is 1, the PC allows 1 null-data response to be ignored. Used for poll-saving BY-COUNT, the maximum count value protects against any long absence of polls to a station. Note: Default is 10, there will be a max of 10 skipped polls. Usage: MAC PC- POLL-SAVE-MAX 10 Specifies whether or not a BSS station may be pollable. Pollable stations are polled during CFPs; other stations are not polled but may have frames delivered to them (depending on the PC mode). Note: By default, stations are POLLABLE Usage: MAC STATION-POLL-TYPE POLLABLE NOT- POLLABLE Specifies whether or not PCF specific statistics should be printed. Note: Default is YES, PCF statistics will be printed for PC coordinated BSSs. Usage: MAC PCF-STATISTICS YES 38 QualNet 4.0 Wireless ModelLibrary

39 Legacy MAC Configuring Legacy MAC-DCF/PCF in the GUI In the GUI, MAC can be enabled for a wireless sub network, for a specific node, for a specific interface, as well as globally for all nodes. According to QualNet s way of working, node-wise specification overrides global specification like all other protocol specifications. To configure MAC for a specific node in the GUI, perform the following steps: 1. Select Hierarchy -> Nodes -> host #-> Node configurations -> MAC Protocol -> MAC Protocol. a. In the Properties Explorer, click on the Configurable Property tab and set MAC Protocol to Legacy , as shown in Figure 22 and Figure 23. b. In the Properties Explorer, click on the Detailed Properties tab and set MAC parameters to their desired values, as shown in selecting Legacy MAC as the MAC Protocol and Setting Parameters. FIGURE 22. Selecting Legacy MAC as the MAC Protocol QualNet 4.0 Wireless Model Library 39

40 Wireless Model Library FIGURE 23. Setting Parameters 2. Select Hierarchy -> Nodes -> Interfaces-> interface# ->Interface configurations -> MAC Protocol - > MAC Protocol -> Station Association Type. a. In the Properties Explorer, set Is Access Point (AP)? to Yes, if the node is an access point, as shown in Configuring Access Point. b. If the node is configured to be an access point, in the Properties Explorer, set the parameters to their desired values, as shown in Figure QualNet 4.0 Wireless ModelLibrary

41 Legacy MAC FIGURE 24. Configuring Access Point 3. Select Hierarchy -> Nodes -> host #-> Interfaces-> interface# ->Interface configurations -> MAC Protocol -> MAC Protocol -> Is Access Point (AP)?-> Is Point Coordinator (PC)? a. In the Properties Explorer, set Is Point Coordinator (PC)? to Yes, if the node is a point coordinator, as shown in Configuring Point Coordinator. b. If the node is configured to be a point coordinator, in the Properties Explorer, set the parameters to their desired values, as shown in Figure 25. QualNet 4.0 Wireless Model Library 41

42 Wireless Model Library FIGURE 25. Configuring Point Coordinator 42 QualNet 4.0 Wireless ModelLibrary

43 802.11e MAC e MAC The IEEE e MAC enhances the basic MAC to provide quality-of-service support for audio and video streams. The e MAC defines a new Hybrid Coordination Function (HCF), which provides an Enhanced Distributed Channel Access (EDCA) method and an HCF Controlled Channel Access (HCCA) method. EDCA The contention-based channel access of HCF is also referred to as EDCA. A new concept, transmission opportunity (TXOP), is introduced in IEEE e. A TXOP is a time period when a station has the right to initiate transmissions onto the wireless medium. It is defined by a starting time and a maximum duration. A station cannot transmit a frame that extends beyond a TXOP. If a frame is too large to be transmitted in a TXOP, it must be fragmented into smaller frames. EDCA works with four Access Categories (ACs), which are virtual DCFs as shown in Figure 26, where each AC achieves a differentiated channel access. This differentiation is achieved through varying the amount of time; a station would sense the channel to be idle, and the length of the contention window for a backoff. Mapping to Access Category AC (0) AC (1) AC (2) AC (3) Backoff AFIS(0) BO(0) Backoff AFIS(1) BO(1) Backoff AFIS(2) BO(2) Backoff AFIS(3) BO(3) Virtual Collision Handler Transmission Attempt FIGURE 26. Enhanced Distributed Channel Access Differentiated ACs are achieved by differentiating the Arbitration Inter-Frame Space (AIFS), the initial window size, and the maximum window size. That is, for AC i (where i is from 0,...,3),the initial backoff QualNet 4.0 Wireless Model Library 43

44 Wireless Model Library window size is CWmin[i], the maximum backoff window size is CWmax[i], and the arbitration inter-frame space is AIFS[i]. For 0 < = i <= j <= 3, we have CWmin[i] >= CWmin[j] and CWmax[i] >= CWmax[j], and AIFS[i] >= AIFS[j] and at least one of above inequalities must be not equal to. In other words, the EDCA employs AIFS[i], CWmin[i], and CWmax[i] (all for i=0,...,3) instead of DIFS, min CW, and max CW, respectively. If one AC has a smaller AIFS or min CW, the traffic of AC has a better chance to access the wireless medium earlier, thus providing the QoS effect. HCCA The contention-free channel access of HCF is also referred to as HCCA. HCCA allows for the reservation of TXOPs with the HC. A non-ap QSTA based on its requirements requests the HC for TXOPs - both for its own transmissions as well as transmissions from the QAP to itself. The request is initiated by the Station Management Entity (SME) of the non-ap QSTA. The HC, which is collocated at the QAP, either accepts or rejects the request based on an admission control policy. If the request is accepted, the HC schedules TXOPs for both the QAP and the non-ap QSTA. For transmissions from the non-ap QSTA, the HC polls the non-ap QSTA based on the parameters supplied by the non-ap QSTA at the time of its request. For transmissions to the non-ap QSTA, the QAP directly obtains TXOPs from the collocated HC and delivers the queued frames to the non-ap QSTA, again based on the parameters supplied by the non-ap QSTA. This mechanism may be used for applications such as voice and video, which may need periodic service from the HC. Admission Control and Scheduling of HCCA In QualNet e MAC model traffic specification includes user priority that will generate four traffic streams as per TSID (TS Identification). The QSTA initiates ADDTS request only if the priority of the data is between 4 to 7. The TSID will be generated by adding eight to User priority. HC will always accept the ADDTS request. HC will poll QSTA based on the priority of the traffic stream. Configuration Using the Simulator You can configure e using the parameters specified in Table 13. TABLE e Parameters Parameter Specifying MAC-DOT11e as MAC-PROTOCOL Specifying Station Association Type Definition e MAC can be enabled at the network/node/interface using the following syntax: [nodeid network-address interface-address] MAC-PROTOCOL MAC- DOT11e MAC-DOT11e-ASSOCIATION configures the mode of association with QAP/ AP. Currently it supports two modes; DYNAMIC mode specifies that QSTA needs to be dynamically associated will QAP. This will set up a QIBSS (QoS enabled Infrastructure mode). If this parameter is NONE then QSTA will work in ad-hoc mode. This will help to set up an ad hoc mode QoS enabled scenario. [nodeid network-address interface-address] MAC-DOT11e-ASSOCIATION DYNAMIC NONE 44 QualNet 4.0 Wireless ModelLibrary

45 802.11e MAC TABLE e Parameters (Continued) Parameter Enabling HCCA Specifying QAP Specifying HC Specifying CAP_LIMIT Specifying SHORT-PACKET Specifying LONG-PACKET Specifying RTS-THRESHOLD Specifying ASSOCIATION DYNAMIC STATIC Specifying SCAN-TYPE DISABLED PASSIVE Definition This parameter enables HCCA at a node/interface. The default value is NO, in this case only EDCA will be used. [nodeid network-address interface-address] MAC-DOT11e-HCCA YES NO This parameter configures a node/interface as AP. The default value is NO. [nodeid network-address interface-address] MAC-DOT11e-AP YES NO This parameter configures a node/interface as HC. This parameter is only valid for an AP. The default value is NO. [nodeid interface-address] MAC-DOT11e-HC YES This is the maximum duration of CAP. HC cannot start CAP for more then this duration in a beacon period. This parameter is specified in Time unites (TUs). Default value for CAP-LIMT is 50 TU where TU is 1024 micro-seconds. [nodeid interface-address] MAC-DOT11e-CAP-LIMIT 50 This parameter allows you to limit the number of short packets transmitted. [nodeid network-address interface-address] MAC-DOT11-SHORT-PACKET- TRANSMIT-LIMIT 7 This parameter allows you to limit the number of long packets transmitted. [nodeid network-address interface-address] MAC-DOT11-LONG-PACKET- TRANSMIT-LIMIT 4 This parameter allows you to set an RTS threshold level. [nodeid network-address interface-address] MAC-DOT11-RTS- THRESHOLD 0 This parameter allows you to specify the type of association. [nodeid network-address interface-address] MAC-DOT11-ASSOCIATION DYNAMIC STATIC This parameter allows you to specify the scan type. [nodeid network-address interface-address] MAC-DOT11-SCAN-TYPE DISABLED PASSIVE Configuration Using the GUI/Animator In animator, you can enable Mac Protocol e for a wireless subnet /wireless node (node having wireless interface), or globally for all the nodes. To configure e MAC in animator, follow the steps in the appropriate section. Configuring MAC Protocol e MAC at the Subnet 1. Inside the Inspector window, navigate to Wireless Subnet Wireless Subnet properties MAC Protocol MAC Protocol. Set the MAC Protocol to e using the Configurable Property Window as shown below. Click the Detailed Properties Window to configure the following parameters. See Figure 27: Short Packet Transmit limit Long Packet Transmit limit RTS threshold QualNet 4.0 Wireless Model Library 45

46 Wireless Model Library Enable HCCA Note: To use only EDCA set the Enable HCCA value to No. FIGURE 27. Configuring e at the Subnet 46 QualNet 4.0 Wireless ModelLibrary

47 802.11e MAC Configuring Association Type and Scan Type 1. Set Station Association Type to Dynamic using Configurable Property Window. Click the Detailed properties Window to configure the following parameters. See Figure 28. Station Scan Type SSID Channel FIGURE 28. Configuring Association Type and Scan Type QualNet 4.0 Wireless Model Library 47

48 Wireless Model Library Configuring QAP 1. Go to Hierarchy(0) -> Nodes -> host1 ->Node Configurations-> Station Access Point->Is Access Point(AP). Set Is Access Point(AP) using Configurable Properties as shown below. Click the Detailed Properties to configure the following parameters. See Figure 29. Beacon Start Time Beacon Interval Relay Frames FIGURE 29. Configuring QAP 48 QualNet 4.0 Wireless ModelLibrary

49 802.11e MAC Configuring HC 1. From the Inspector window, navigate to Hierarchy(0) -> Nodes -> host1 ->Node Configurations-> Station Access Point->Is Access Point(AP )->Is HC?. Set Is HC? to Yes using Configurable Properties. Click Detailed Properties to configure the e CAP Limit. See Figure 30. FIGURE 30. Configuring HC Note: HC can be enabled only if HCCA is enabled. QualNet 4.0 Wireless Model Library 49

50 Wireless Model Library Statistics Table 14 lists all the statistics collected by this protocol. A brief explanation for each of them is as followed. Note: e MAC also enables basic MAC statistics TABLE e MAC Statistics Statistic Explanation Basic Statistics Packets from Total packets from UNICAST packets sent to channel Total UNICAST packets sent to channel BROADCAST packets sent to channel Total BROADCAST packets sent to channel UNICAST packets received clearly Total UNICAST packets received clearly BROADCAST packets received clearly Total BROADCAST packets received clearly DCF Statistics Unicasts sent Total unicasts packet sent Broadcasts sent Total Broadcast sent Unicasts received Total unicast packet received Broadcasts received Total broadcast packet received CTS packets sent Total CTS packets sent RTS packets sent Total RTS packets sent ACK packets sent Total Ack packets sent RTS retransmissions due to timeout Total RTS retransmissions due to timeout Packet retransmissions due to ACK timeout Total packet retransmission due to Ack timeout Packet drops due to retransmission limit Total Packets drop due to retransmission limit Management Statistics Management packets sent to channel Total management pkts sent to channel Management packets received from channel Total management pkts received Beacons received Total Beacons frames received Beacons sent Total Beacons frames sent e MAC Statistics AC[0] Total Frame Queued Total Background packet queued AC[0] Total Frame de-queued Total Background packet de-queued AC[1] Total Frame Queued Total Best effort packet queued AC[1] Total Frame de-queued Total Best effort packet de-queued AC[2] Total Frame Queued Total Video traffic packet queue AC[2] Total Frame de-queued Total Video packet de-queued AC[3] Total Frame Queued Total Voice traffic queued AC[3] Total Frame de-queued Total Voice traffic queued QoS Data Frame send Total QoS data frame sent Non-QoS Data Frame send Total Non-QoS Data Frame send QoS Data Frame received Total QoS Data Frame received 50 QualNet 4.0 Wireless ModelLibrary

51 802.11e MAC TABLE e MAC Statistics (Continued) Statistic Non-QoS Data Frame received HCCA HCCA HCCA HCCA HCCA HCCA Explanation Total Non-QoS Data Frame received HCCA Statistics Polls transmitted Data packets transmitted Data packets received NullData received Data packets received NullData transmitted Examples This section provides sample scenarios for EDCA mode and HCCA mode. Example Scenario for EDCA Mode This example scenario tests the functionality of QualNet e MAC EDCA mode. Six nodes are present in a subnet. All nodes are QSTAs. [1] [2] \ / \ / \ / \ / \ / [6] [3] / \ / \ / \ / \ / \ [5] [4] Simulator Configurations: [ N ] MAC-PROTOCOL MACDOT11e [ N ] MAC-DOT11-DIRECTIONAL-ANTENNA-MODE NO [ N ] MAC-DOT11-SHORT-PACKET-TRANSMIT-LIMIT 7 [ N ] MAC-DOT11-LONG-PACKET-TRANSMIT-LIMIT 4 [ N ] MAC-DOT11-RTS-THRESHOLD 0 [ N ] MAC-DOT11-ASSOCIATION DYNAMIC [ N ] MAC-DOT11-SCAN-TYPE PASSIVE [ N ] MAC-DOT11-SSID Test1 [ N ] MAC-DOT11-STA-CHANNEL 1 [ 1 ] MAC-DOT11-AP YES [ 1 ] MAC-DOT11-BEACON-START-TIME 1 [ 1 ] MAC-DOT11-BEACON-INTERVAL 200 [ 1 ] MAC-DOT11-RELAY-FRAMES YES [ 1 ] MAC-DOT11-SCAN-TYPE DISABLED QualNet 4.0 Wireless Model Library 51

52 Wireless Model Library Node 2 is sending 100 packets with PRECEDENCE 0 to node 3. Similarly, Node 3 is sending 100 packets with PRECEDENCE 3 to node 5. Animator Configuration To configure e MAC in the Animator, follow these steps: 1. Create a New scenario. See Figure 31. FIGURE 31. Create a New Scenario 2. Select Device from ScenarioDesigner. Now select the default icon and place 6 nodes. 3. Select Wireless Subnet and place a wireless cloud. 4. Connect all 6 nodes with a Wireless Subnet: a. Select Links from ScenarioDesigner b. Select Link and create Wireless link between nodes and Wireless clouds. 5. Using the Inspector Window, navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol-> MAC Protocol. Set the MAC Protocol to e using the Configurable Property Window as shown below. Click Detailed Properties to configure the following parameters. See Figure 32 and Figure 33. AP Address 52 QualNet 4.0 Wireless ModelLibrary

53 802.11e MAC Short Packet Transmit limit Long Packet Transmit limit RTS threshold Enable HCCA FIGURE 32. Configuring Parameters from the Detailed Properties Window QualNet 4.0 Wireless Model Library 53

54 Wireless Model Library FIGURE 33. Configuring Station Association Type 6. Using the Inspector Window, navigate to Wireless Subnet N >Wireless Subnet Properties->MAC Protocol-> MAC Protocol->Station Association Type. Set Station Association Type as DYNAMIC using Configurable Property window as shown below. Click Detailed Properties to configure the following parameters. See Figure 34 and Figure 35. Station Scan Type SSID Channel 54 QualNet 4.0 Wireless ModelLibrary

55 802.11e MAC FIGURE 34. Setting the Station Association Type as Dynamic QualNet 4.0 Wireless Model Library 55

56 Wireless Model Library FIGURE 35. Setting the Station Scan Type as Passive 7. Go to Hierarchy (0) -> Nodes -> host1 -> Node Configurations->MAC Protocol. Set MAC Protocol to e MAC window and set Station Association Type as Dynamic. See Figure 36 and Figure QualNet 4.0 Wireless ModelLibrary

57 802.11e MAC FIGURE 36. QualNet 4.0 Wireless Model Library 57

58 Wireless Model Library FIGURE Using the Inspector Window, navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol-> MAC Protocol->Station Association Type->Is Access Point(AP). Set Is Access Point(AP) to Yes using Configurable Property window as shown below. Click Detailed Properties to configure the following parameters. See Figure 38. Beacon Start Time Beacon Interval Time Relay Frames 58 QualNet 4.0 Wireless ModelLibrary

59 802.11e MAC FIGURE Select the Applications from ScenarioDesigner window. a. Select CBR and set the three application between Node 2 and Node 3. Similarly an application between Node 4 and Node 5. b. Now set the Application Parameters using the Configurable Property window. c. Set PRECEDENCE for one CBR link between node 2 and node 3 as 0, PRECEDENCE for two CBR link between node 2 and node 3 as 5 and PRECEDENCE for CBR link between node 4 and node 5 as 5 using Detailed Property window: See Figure 39. QualNet 4.0 Wireless Model Library 59

60 Wireless Model Library FIGURE 39. Example Scenario for HCCA Mode This example scenario tests the functionality of QualNet e MAC HCCA mode. Six nodes are present in a subnet. All nodes are QSTAs. [1] [2] \ / \ / \ / \ / \ / [6] [3] / \ / \ / \ / \ / \ [5] [4 ] 60 QualNet 4.0 Wireless ModelLibrary

61 802.11e MAC Simulator Configurations [ N ] MAC-PROTOCOL MACDOT11e [ N ] MAC-DOT11-DIRECTIONAL-ANTENNA-MODE NO [ N ] MAC-DOT11-SHORT-PACKET-TRANSMIT-LIMIT 7 [ N ] MAC-DOT11-LONG-PACKET-TRANSMIT-LIMIT 4 [ N ] MAC-DOT11-RTS-THRESHOLD 0 [ N ] MAC-DOT11e-HCCA YES [ N ] MAC-DOT11-ASSOCIATION DYNAMIC [ N ] MAC-DOT11-SCAN-TYPE PASSIVE [ N ] MAC-DOT11-SSID Test1 [ N ] MAC-DOT11-STA-CHANNEL 1 [ 1 ] MAC-DOT11-AP YES [ 1 ] MAC-DOT11-BEACON-START-TIME 1 [ 1 ] MAC-DOT11-BEACON-INTERVAL 200 [ 1 ] MAC-DOT11-RELAY-FRAMES YES [ 1 ] MAC-DOT11e-HC YES [ 1 ] MAC-DOT11e-CAP-LIMIT 190 [ 1 ] MAC-DOT11-SCAN-TYPE DISABLED Animator Configuration 1. Create a new scenario. See Figure 40. FIGURE Select Device from the ScenarioDesigner window. Select the Default icon and place 6 nodes. 3. Select Wireless Subnet and place wireless cloud. See Figure 41. QualNet 4.0 Wireless Model Library 61

62 Wireless Model Library FIGURE Connect all the 6 nodes with Wireless Subnet: a. Select Links from ScenarioDesigner window b. Select link and create Wireless link between nodes and Wireless clouds. 5. Using the Inspector Window, Navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol-> MAC Protocol. Set the MAC Protocol to e using the Configurable Property window as shown below. Click the Detailed Properties to configure the following parameters. See Figure 42 and Figure 43. AP Address Short Packet Transmit limit Long Packet Transmit limit RTS threshold Enable HCCA 62 QualNet 4.0 Wireless ModelLibrary

63 802.11e MAC FIGURE 42. QualNet 4.0 Wireless Model Library 63

64 Wireless Model Library FIGURE Using the Inspector Window, navigate to Wireless Subnet ->Wireless Subnet Properties->MAC Protocol-> MAC Protocol->Station Association Type. Set Station Association Type as Dynamic using Configurable Property window as shown in Figure 44 and Figure 45. Click the Detailed Properties window to configure: Station Scan Type SSID Channel 64 QualNet 4.0 Wireless ModelLibrary

65 802.11e MAC FIGURE 44. QualNet 4.0 Wireless Model Library 65

66 Wireless Model Library FIGURE Go to Hierarchy (0) -> Nodes -> host1 -> Node Configurations->MAC Protocol. Set MAC PROTOCOL to e MAC using Configurable Property window and set Station Association Type as Dynamic. See Figure 46 and Figure QualNet 4.0 Wireless ModelLibrary

67 802.11e MAC FIGURE 46. QualNet 4.0 Wireless Model Library 67

68 Wireless Model Library FIGURE Using Inspector Window, navigate to Hierarchy (0) -> Nodes -> host1 -> Node Configurations- >MAC Protocol->Station Association Type->Is Access point (AP). Set Is Access point to Yes using Configurable Property window. Click the Detailed Properties window to configure the following and see Figure 48. Beacon Start Time Beacon Interval 68 QualNet 4.0 Wireless ModelLibrary

69 802.11e MAC FIGURE Using Inspector Window, navigate to Hierarchy (0) -> Nodes -> host1 -> Node Configurations- >MAC Protocol->Station Association Type->Is Access point (AP)->Is HC. Set Is HC to Yes using Configurable Property window. Click the Detailed Properties window to configure: e CAP LIMT. See Figure 49 QualNet 4.0 Wireless Model Library 69

70 Wireless Model Library FIGURE 49. Node 2 is sending packets with PRECEDENCE 0 to node 3 up to the end of simulation in one CBR. Node 2 is sending packets with PRECEDENCE 0 to node 5 up to the end of simulation in one CBR. Node 2 is sending packets with PRECEDENCE 0 to node 5 up to the end of simulation in one CBR. Node 3 is sending packets with PRECEDENCE 5 to node 5 up to the end of simulation. See Figure QualNet 4.0 Wireless ModelLibrary

71 802.11e MAC FIGURE 50. QualNet 4.0 Wireless Model Library 71

72 Wireless Model Library a/g PHY a PHY is an extension to IEEE PHY that applies to wireless LANs and provides up to 54 Mbps in the 5GHz band a PHY uses an orthogonal frequency division multiplexing encoding scheme rather than FHSS or DSSS. Configuration To simulate a WLAN using PHY specifications in QualNet, the following parameters in physical layer are required. See Table 15. TABLE a PHY Parameters Parameter PHY-MODEL PHY AUTO-RATE-FALLBACK PHY802.11a-TX-POWER-6MBPS PHY802.11a-TX-POWER-9MBPS PHY802.11a-TX-POWER-12MBPS PHY802.11a-TX-POWER-18MBPS PHY802.11a-TX-POWER-24MBPS PHY802.11a-TX-POWER-36MBPS PHY802.11a-TX-POWER-48MBPS PHY802.11a-TX-POWER-54MBPS PHY802.11a-RX-SENSITIVITY-6MBPS PHY802.11a-RX-SENSITIVITY-9MBPS PHY802.11a-RX-SENSITIVITY- 12MBPS Description Indicates the phy model to transmit and receive packets. This is BER- BASED preconfigured for a PHY model. Options: PHY802.11a (example PHY-MODEL PHY802.11a) PHY802.11b (example PHY-MODEL PHY802.11b) Specifies multirate or single rate service. If turned on the scenario will have multirate transfer capabilities to perform dynamic rate switching with the objective of improving. Note: Performance for multirate service, the related multiple PHY-RX- BER-TABLE-FILE for different data rates are required. Options: YES (example PHY AUTO-RATE-FALLBACK YES NO (example PHY AUTO-RATE-FALLBACK NO) Sets the transmission power in dbm for the nodes using a PHY at the 6Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 9Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 12Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 18Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 24Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 36Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 48Mbps data rate. Sets the transmission power in dbm for the nodes using a PHY at the 54Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 6Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 9Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 12Mbps data rate. 72 QualNet 4.0 Wireless ModelLibrary

73 802.11a/g PHY TABLE a PHY Parameters (Continued) PHY802.11a-RX-SENSITIVITY- 18MBPS PHY802.11a-RX-SENSITIVITY- 24MBPS PHY802.11a-RX-SENSITIVITY- 32MBPS PHY802.11a-RX-SENSITIVITY- 48MBPS PHY802.11a-RX-SENSITIVITY- 54MBPS PHY DATA-RATE PHY DATA-RATE-FOR- BROADCAST PHY ESTIMATED- DIRECTIONAL-ANTENNA-GAIN Sets the receiver sensitivity in dbm for the nodes using a PHY at the 18Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 24Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 32Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 48Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using a PHY at the 54Mbps data rate. Specifies the fixed data rate to use if AUTO-RATE-FALLBACK is disabled. Specifies the data rate for broadcast, it should be one of the multirate, or same as the data rate in single rate service. Specifies the estimated directional antenna gain. Statistics Table 16 shows the statistics collected by a PHY: TABLE a PHY Statistics Statistic Signals transmitted Signals received and forwarded to MAC Signals locked on by PHY Signals received but with errors Energy consumption Explanation Number of signals transmitted Number of signals received and forwarded to MAC Number of signals locked on by PHY Number of signals received with errors Energy consumption in mwhr QualNet 4.0 Wireless Model Library 73

74 Wireless Model Library b PHY b PHY is an extension to IEEE PHY that applies to wireless LANS and provides 11 Mbps transmission (with a fallback to 5.5, 2 and 1 Mbps) in the 2.4 GHz band b PHY uses only DSSS b PHY was a 1999 ratification to the original PHY standard, allowing wireless functionality comparable to Ethernet b is a direct extension of the DSSS (Direct-sequence spread-spectrum) modulation technique. As with other spread-spectrum technologies, the signal transmitted using DSSS takes up more bandwidth than the information signal that is being modulated. The carrier signals occur over the full bandwidth (spectrum) of a device transmitting frequency. DSSS modulates the signal by multiplying the data being transmitted by a "noise" signal. This noise signal is a pseudorandom sequence of 1 and -1 values, at a frequency much higher than that of the original signal, thereby spreading the energy of the original signal into a much wider band. The b standard uses Complementary code keying (CCK) as its modulation technique, which is a variation on CDMA. Complementary codes are sets of finite sequences of equal length, such that the number of pairs of identical elements with any given separation in one sequence is equal to the number of pairs of unlike elements having the same separation in the other sequences. CCK is a variation and improvement on, M-ary Orthogonal Keying and uses "polyphase complementary codes". Configuration Table 17 shows the physical layer parameters for b PHY. TABLE b PHY Parameters Parameter PHY-MODEL PHY AUTO-RATE-FALLBACK PHY802.11b-TX-POWER-1MBPS PHY802.11b-TX-POWER-2MBPS PHY802.11b-TX-POWER-6MBPS PHY802.11b-TX-POWER-11MBPS Description Indicates the phy model to transmit and receive packets. This is BER- BASED preconfigured for b PHY model. Options: PHY802.11a (example PHY-MODEL PHY802.11a) PHY802.11b (example PHY-MODEL PHY802.11b) Specifies multirate or single rate service. If turned on the scenario will have multirate transfer capabilities to perform dynamic rate switching with the objective of improving. Note: Performance for multirate service, the related multiple PHY-RX- BER-TABLE-FILE for different data rates are required. Options: Yes (example PHY AUTO-RATE-FALLBACK YES No (example PHY AUTO-RATE-FALLBACK NO) Sets the transmission power in dbm for the nodes using b PHY at the 1Mbps data rate. Sets the transmission power in dbm for the nodes using b PHY at the 2Mbps data rate. Sets the transmission power in dbm for the nodes using b PHY at the 5.5Mbps data rate. Sets the transmission power in dbm for the nodes using b PHY at the 11Mbps data rate. 74 QualNet 4.0 Wireless ModelLibrary

75 802.11b PHY TABLE b PHY Parameters (Continued) Parameter PHY802.11b-RX-SENSITIVITY- 1MBPS PHY802.11b-RX-SENSITIVITY- 2MBPS PHY802.11b-RX-SENSITIVITY- 6MBPS PHY802.11b-RX-SENSITIVITY- 11MBPS PHY DATA-RATE PHY DATA-RATE-FOR- BROADCAST PHY ESTIMATED- DIRECTIONAL-ANTENNA-GAIN Description Sets the receiver sensitivity in dbm for the nodes using b PHY at the 1Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using b PHY at the 2Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using b PHY at the 5.5Mbps data rate. Sets the receiver sensitivity in dbm for the nodes using b PHY at the 11Mbps data rate. Specifies the fixed data rate to use if AUTO-RATE-FALLBACK is disabled. Specifies the data rate for broadcast, it should be one of the multirate, or same as the data rate in single rate service. Estimated antenna gain (in dbm) for directional communication. Statistics Table 18 shows the statistics collected by b PHY: TABLE b PHY Statistics Statistic Signals transmitted Signals received and forwarded to MAC Signals locked on by PHY Signals received but with errors Energy consumption Explanation Number of signals transmitted Number of signals received and forwarded to MAC Number of signals locked on by PHY Number of signals received with errors Energy consumption in mwhr QualNet 4.0 Wireless Model Library 75

76 Wireless Model Library Abstract PHY Model The abstract PHY model is a simple radio model that supports either Signal-to-Noise Ratio (SNR) or Bit Error Rate (BER) based reception. It is not abstract in the mathematical sense; it still models all the signal transmissions and receptions. Rather, it is a simple flexible model that can be used to model various types of radios where a detailed model of the radio is not required. Configuration This parameter is used to select the abstract PHY: PHY-MODEL PHY-ABSTRACT The abstract PHY supports SNR-threshold-based and BER-based packet reception models. PHY-RX-MODEL SNR-THRESHOLD-BASED BER-BASED Table 19 lists the four parameters specific to the abstract PHY. TABLE 19. Abstract PHY Parameters Parameter Description PHY-ABSTRACT-DATA-RATE The data rate. PHY-ABSTRACT-TX-POWER The transmission power in db. PHY-ABSTRACT-RX-SENSITIVITY The sensitivity (in db) determines the sensing range. PHY-ABSTRACT-RX-THRESHOLD The threshold (in db) is the minimum strength signal that can be received. Statistics Table 20 lists the statistics output by the abstract physical layer model: TABLE 20. Statistics Collected by the Abstract Physical Layer Model Statistics Description Signals transmitted Number of signals transmitted. Signals detected Total number of incoming signals. Signals locked on by PHY Incoming signals the radio tried to receive. Signals received but with errors Incoming signals the radio failed to receive. Signals received and forwarded to MAC Incoming signals successfully received. Energy consumption Energy consumed (primarily due to transmissions). 76 QualNet 4.0 Wireless ModelLibrary

77 Aloha Aloha Aloha is a wireless random access MAC protocol that transmits data whenever there is data to send (no carrier sensing). If no acknowledgement is received, the source retransmits at a later time. Configuration To specify Aloha, use the following parameter in the *.config file: MAC-PROTOCOL ALOHA Statistics Aloha MAC collects the following statistics: TABLE 21. Aloha Statistics Statistics Packets Sent to Channel Packets Received from Channel Packets Dropped Description Number of data packets sent to channel Number of data packets received from channel Number of data packets dropped QualNet 4.0 Wireless Model Library 77

78 Wireless Model Library AODV The Ad-hoc On Demand Distance Routing (AODV) protocol is specially used for mobile ad hoc networks. It provides a quick adaptation to dynamic link condition, link fault, low processing and memory usage overhead. The important feature of AODV is its use of Sequence Number to prevent routing loops. Routing loops prevent the availability of more than one route to a particular destination, which is determined by the sequence number. Configuration and Parameters To select AODV as the routing protocol, place the following entry in *.config: ROUTING-PROTOCOL AODV To configure AODV at a specific node, subnet, or IPv6 interface, specify the following configuration in the *.config file: [Global Node Id IPv4 Address] ROUTING-PROTOCOL AODV [Global Node Id IPv6 Address] ROUTING-PROTOCOL AODV AODV takes the following optional parameters, shown in Table 22, that can be used to override the default values. TABLE 22. Optional AODV Parameters Parameter AODV-DEST-ONLY-NODE ROUTING STATISTICS AODV-NET-DIAMETER AODV-NODE TRAVERSAL- TIME AODV-ACTIVE-ROUTE- TIMEOUT AODV-MY-ROUTE-TIMEOUT AODV-PROCESS-HELLO Explanation To enable a particular node to set the destination-only-node while sending RREQ, you must specify the following configuration in the *.config file as follows. The default value is NO. [Node Id] AODV-DEST-ONLY-NODE YES NO To enable AODV to collect the statistics and store the statistics after completing the simulation, you must specify the following configuration in the *.config file as follows. The default value is YES. ROUTING-STATISTICS YES This parameter specifies the maximum possible number of hops between two nodes in the network. The default value is 35 This parameter specifies the conservative estimate of the average one-hop traversal time for packets and should include queuing, transmission, propagation and other delays. The default value is 40 ms This parameter specifies the Timeout time for an active route; each time a data packet is sent, the lifetime of that route is updated to this value.the default value is 3000ms. This parameter specifies the destination of a RREQ replies with AODV-MY- ROUTE-TIMEOUT as the lifetime of the route. The default value is 2 * AODV- ACTIVE-ROUTE-TIMEOUT If the value for this parameter is set YES, a node will send a hello message, if there is no broadcast within the last hello interval.the default value is NO 78 QualNet 4.0 Wireless ModelLibrary

79 AODV TABLE 22. Optional AODV Parameters (Continued) Parameter AODV-HELLO-INTERVAL AODV-ALLOWED-HELLO-LOSS AODV-RREQ-RETRIES AODV-ROUTE-DELECTION- CONSTANT AODV-LOCAL-REPAIR AODV-SEARCH-BETTER- ROUTE AODV-BUFFER-MAX-PACKET AODV-BUFFER-MAX-BYTE AODV-BI-DIRECTIONAL- CONNECTION AODV-TTL-START AODV-TTL-INCREMENT AODV-TTL-THRESHOLD Explanation This parameter specifies the lifetime of a hello message using the following equation: AODV-ALLOWED_HELLO_LOSS * AODV-HELLO_INTERVAL. The default value is 1000ms This parameter specifies the maximum number of times for AODV to repeat the expanded ring search for a destination, if no Route Reply is received within the specified time. The default value is 2 This parameter specifies the maximum number of times for AODV to repeat the expanded ring search for a destination, if no Route Reply is received within the specified amount of time. The default value is 2 This parameter specifies a constant, which is used for calculating the time after which an active route must be deleted. After timeout of an active route, the route is deleted from the routing table after a time period of K * Max(AODV- ACTIVE_ROUTE_TIMEOUT,AODV-ALLOWED_HELLO_LOSS * AODV- HELLO_INTERVAL). Here, K is the AODV-ROUTE-DELETION-CONSTANT. The default value is 5 If this value is set to YES, the node tries to locally Repair a broken route.the default value is NO. If a route source node gets a route error message, it initiates a new Route Request for the destination if the value is set to YES.The default value is NO. This parameter specifies the maximum number of packets for the message buffer of AODV. If the buffer reaches its maximum, the incoming packets for the buffer is dropped.the default value is 100. If nothing is specified, buffer overflow will be checked by number of packets in the buffer. If some value is specified, incoming packets are dropped if the total of the incoming packet size and current size of the buffer exceeds this value. The default value is 0. This parameter specifies, which applications to open in a bi-directional connection. If this parameter is specified, Route Request is sent with Gratuitous flag in the ON state, which causes a Gratuitous Reply. This parameter specifies the TTL value when initiating a route request.the default value is 1. This parameter specifies the value by which the TTL is incremented, each time when a Request is retransmitted.the default value is 2. This parameter specifies the maximum value of TTL over which the NET_DIAMETER value is used to broadcast Route Request. The default value is 7. AODV Configurations using GUI / Animator To configure the AODV routing protocol in Animator, you need to perform the steps as follows: 1. Inside the Inspector window, navigate to ConfigSettings->Network Protocols->Routing Protocol- >Routing Policy. Set the Routing Policy to Dynamic using the Configurable Property window as shown in Figure 51: QualNet 4.0 Wireless Model Library 79

80 Wireless Model Library FIGURE Navigate to ConfigSettings->Network Protocols->Routing Protocol->Routing Policy ->Routing Protocol to select AODV using the Configurable Property window as shown in Figure 52: 80 QualNet 4.0 Wireless ModelLibrary

81 AODV FIGURE For Node configurations, navigate to Hierarchy#->Node Configurations->Routing Protocol ->Routing Policy. See Figure 53 and Figure 54. QualNet 4.0 Wireless Model Library 81

82 Wireless Model Library FIGURE QualNet 4.0 Wireless ModelLibrary

83 AODV FIGURE To configure or specify the AODV optional parameters, navigate the detailed properties window for AODV and change the required parameters. See Figure 55. QualNet 4.0 Wireless Model Library 83

84 Wireless Model Library FIGURE QualNet 4.0 Wireless ModelLibrary

85 AODV Statistics To enable AODV to collect statistics and report them after completing a simulation, use the statistics variable by entering it in the configuration file. ROUTING-STATISTICS YES Table 23 shows the statistics collected by AODV: TABLE 23. AODV Statistics Statistic <nodeid>, AODV,Number of RREQ Initiated <nodeid>, AODV,Number of RREQ Retried <nodeid>, AODV,Number of RREQ Forwarded <nodeid>, AODV,Number of RREQ Initiated for local repair <nodeid>, AODV,Number of RREQ sent for alternate route <nodeid>, AODV,Number of RREQ received <nodeid>, AODV,Number of Duplicate RREQ received <nodeid>, AODV,Number RREQ ttl expired <nodeid>, AODV,Number RREQ discarded for blacklist <nodeid>, AODV,Number RREQ received by Dest <nodeid>, AODV,Number of RREP Initiated as Dest <nodeid>, AODV,Number of RREP Initiated as intermediate node <nodeid>, AODV,Number of RREP Forwarded <nodeid>, AODV,Number of Gratuitous RREP sent <nodeid>, AODV,Number of RREP Received <nodeid>, AODV,Number of RREP Received for local repair <nodeid>, AODV,Number of RREP Received as Source <nodeid>, AODV,Number of Hello message sent <nodeid>, AODV,Number of Hello message received <nodeid>, AODV,Number of RERR Initiated <nodeid>, AODV,Number of RERR Initiated with N flag <nodeid>, AODV,Number of RERR forwarded <nodeid>, AODV,Number of RERR forwarded with N flag <nodeid>, AODV,Number of RERR received Description Number of route request messages initiated. Number of route requests resent because node did not receive a route reply. Number of route request messages forwarded by intermediate nodes. Number of route requests sent for local repair. Number of route requests sent for alternate routes. Number of route requests received. Number of duplicate route requests received. Number of route requests not forwarded due to TTL expiration. Number of route requests received from senders in node route request Blacklist. Number of route requests received as the destination. Number of route replies initiated from the destination. Number of route replies initiated as an intermediate hop. Number of route replies forwarded by intermediate hops. Number of gratuitous route replies sent. Number of route replies received. Number of route replies received for local repair. Number of route replies received as data source. Number of hello messages sent. Number of hello message received. Number of route error packets initiated. Number of route error packets sent with the N flag set. Number of route error packets forwarded. Number of route error packets forwarded with the N flag set. Number of route error packets received. QualNet 4.0 Wireless Model Library 85

86 Wireless Model Library TABLE 23. AODV Statistics (Continued) <nodeid>, AODV,Number of RERR received with N flag <nodeid>, AODV,Number of RERR discarded <nodeid>, AODV,Number of Data packets sent as Source <nodeid>, AODV,Number of Data Packets Forwarded <nodeid>, AODV,Number of Data Packets Received <nodeid>, AODV,Number of Data Packets Dropped for no route <nodeid>, AODV,Number of Data Packets Dropped for buffer overflow <nodeid>, AODV,Number of Routes Selected <nodeid>, AODV,Total Hop Counts for all routes <nodeid>, AODV,Number of Packets Dropped for exceeding Maximum Hop Count <nodeid>, AODV,Number of times link broke Number of route error packets received with the N flag set. Number of route error packets discarded. Number of data packets sent as the source of the data. Number of data packets forwarded. Number of data packets received as the destination of the data. Number of data packets dropped due to lack of route. Number of data packets dropped due to buffer overflow. Number of routes added to the route cache. Aggregate sum of the hop counts of all routes added to the route cache. Number of data packets dropped because maximum hop count exceeded. Total number of times links broke. To view statistics, follow the steps described below and shown in Figure Navigate to ConfigSettings->Statistics->Statistics. 2. Enable the Routing statistics using the Configurable Property window: Routing' YES 86 QualNet 4.0 Wireless ModelLibrary

87 AODV FIGURE 56. Example Scenario Figure 57 shows an example of how you can use the AODV routing protocol in the QualNet main configuration file. This example is a six-node ad-hoc scenario with the routing protocol set to AODV. QualNet 4.0 Wireless Model Library 87

88 Wireless Model Library FIGURE 57. Example AODV Scenario Configuration Using the Simulator In the *.config file, specify the following parameters. SIMULATION-TIME 10M // The scenario is executed for a simulation time of 10minutes. NETWORK-PROTOCOL IP IP-ENABLE-LOOPBACK YES IP-LOOPBACK-ADDRESS DUAL-IP NO IP-FRAGMENTATION-UNIT 2048 IP-QUEUE-NUM-PRIORITIES 3 IP-QUEUE-PRIORITY-INPUT-QUEUE-SIZE DUMMY-PRIORITY-QUEUE-SIZE NO IP-QUEUE-PRIORITY-QUEUE-SIZE DUMMY-PRIORITY-WISE-IP-QUEUE-TYPE NO IP-QUEUE-TYPE FIFO # ECN as presented in RFC Requires one of the IP-QUEUE-TYPE (RED, RIO, or WRED). Furthermore, the source and destination nodes must be ECN enabled. ECN NO IP-QUEUE-SCHEDULER STRICT-PRIORITY # ************* Routing Protocol *********** DUMMY-ROUTING DYNAMIC ROUTING-PROTOCOL AODV # Subnet ID SUBNET N { 1 thru 6 } Default COMPONENT 0 { } CBR S 1S 0 PRECEDENCE 0 The application is configured between node 1 and node 6, node 1 sends 100 packets to node 6, each packet is 512 bytes. See Figure QualNet 4.0 Wireless ModelLibrary

89 AODV FIGURE 58. Configuration Using the GUI Creating a New Scenario To create a new scenario, you must perform the following steps: 1. Navigate to ConfigSettings->General->General->Experiment Name a. Configure the Simulation time and Experiment name using the Configurable Property window. b. Click Devices of Scenario Designer window. c. Click Default and place 6 nodes. Using the Inspector Window To configure using the Inspector window, follow these steps: 1. Navigate to ConfigSettings->Network Protocols->Routing Protocol->Routing Policy. QualNet 4.0 Wireless Model Library 89

90 Wireless Model Library 2. Set the routing policy to Dynamic. Using the Inspector Window To configure AODV in the Inspector window, follow these steps: 1. Navigate to ConfigSettings->Network Protocol->Routing Protocol->Routing Policy->Routing Protocol. a. Select AODV as the Routing Protocol using the Configurable Property Window. 2. Click Applications from the Scenario Designer window. a. Select CBR and set the application between Node 1 and Node 6. b. Set the Application Parameters using the Configurable Property Window. Inside the Inspector window To configure AODV inside the Inspector window, follow these steps: 1. Navigate to ConfigSettings->Statistics->Statistics. a. Set the Routing Statistics to YES using the Configurable Property Window. 2. Save the changes by a clicking the Save button. Click the RUN button. Click the Play button to execute the scenario. 3. On completion of the Scenario execution, check the corresponding Statistics for the desired results. Verification Scenarios Table 24 shows the verification scenarios for AODV. TABLE 24. AODV Verification Scenarios Name Location Purpose generating-rrep $QUALNET_HOME/scenarios/wireless/ aodv/generating-rrep To test AODV implementation for IPv6/Ipv4 RREP generation by intermediate node and destination node. link-addressing local-repair mixed-wired mixed-wireless ns3-wired ns3-wireless ns5-wired $QUALNET_HOME/scenarios/wireless/ aodv/ link-addressing $QUALNET_HOME/scenarios/wireless/ aodv/ local-repair $QUALNET_HOME/scenarios/wireless/ aodv/ mixed-wired $QUALNET_HOME/scenarios/wireless/ aodv/ mixed-wireless $QUALNET_HOME/scenarios/wireless/ aodv/ ns3-wired $QUALNET_HOME/scenarios/wireless/ aodv/ ns3-wireless $QUALNET_HOME/scenarios/wireless/ aodv/ ns5-wired To show AODV functionality for IPv6 addressing. To show AODV operation where the link between nodes fails and local repair is enabled. To show activities of AODV under mixed wired scenario. To show activities of AODV under mixed (wired and wireless) scenario. Normal AODV test for 3 nodes in wired scenario. Normal AODV test for 3 nodes in wireless scenario. Normal AODV test for 5 nodes in wired scenario. 90 QualNet 4.0 Wireless ModelLibrary

91 BRP TABLE 24. AODV Verification Scenarios ns5-wireless processing-rrep processing-rreq route-errors dualip Ipv4-tunnel Ipv6-tunnel $QUALNET_HOME/scenarios/wireless/ aodv/ ns5-wireless $QUALNET_HOME/scenarios/wireless/ aodv/ processing-rrep $QUALNET_HOME/scenarios/wireless/ aodv/ processing-rreq $QUALNET_HOME/scenarios/wireless/ aodv/ route-errors $QUALNET_HOME/scenarios/wireless/ aodv/ dualip $QUALNET_HOME/scenarios/wireless/ aodv/ Ipv4-tunnel $QUALNET_HOME/scenarios/wireless/ aodv/ Ipv6-tunnel Normal AODV test for 5 nodes in wireless scenario. To verify basic RREP Generation and forwarding. Test duplicate RREQ processing. Tests destination sequence number update when new path is found to the same destination. / Test local repair. To test the functionality of AODV when both IPv6 and IPv4 are enabled on different interfaces of a node. To test IPv4-tunnel between a pair of dual-ip enabled nodes for both wired and wireless. To test IPv6-tunnel between a pair of dual-ip enabled nodes in wired/wireless medium. BRP The Bordercast Resolution Protocol (BRP) is a component of Zone Routing Protocol (ZRP). It is used to efficiently flooding broadcast packet throughout the network. It is not a full-featured routing protocol. BRP follows draft-ietf-manet-zone-brp-02. Configuration To configure BRP in the QualNet GUI, complete the following steps: 1. Select the Inspector tab. 2. Go to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. 3. Select Dynamic. 4. Select Routing Protocol properties as ZRP from the list. 5. In ZRP properties, set IERP use BRP as Yes and specify Zone Radius. Parameter BRP is enabled from the main configuration file by the following statement: ROUTING-PROTOCOL ZRP ZRP accepts the following parameter: QualNet 4.0 Wireless Model Library 91

92 Wireless Model Library IERP-USE-BRP YES ZONE-RADIUS Used to specify the zone radius. The zone radius has to be greater than or equal to 0, or INFINITY. If Zone Radius is not given then a default zone radius of 0 assumed by the protocol. ZONE-RADIUS 0 Statistics Table 25 shows the statistics collected by BRP: TABLE 25. BRP Statistics Statistic Number of query packets sent. Number of query packets received. Explanation Number of BRP query packets sent. Number of BRP query packets received by the node. 92 QualNet 4.0 Wireless ModelLibrary

93 CSMA CSMA Carrier Sense Multiple Access is a generic carrier-sensing protocol. When a radio wishes to send data, it senses the channel. If the channel is busy, it backs off for a random time period before sensing the channel again. If the channel is free, the radio transmits the packet. Configuration To select CSMA as the MAC protocol, place the following entry in the *.config file: MAC-PROTOCOL CSMA Parameters CSMA takes no parameters. Statistics Table 26 shows the statistics collected by the CSMA model. TABLE 26. CSMA Statistics Collected Statistics Packets From Network Packets Lost to Buffer Overflow Unicast packets to channel Broadcast packets to channel Unicast packets from channel Broadcast packets from channel Explanation Packets received from Network Layer Protocol, i.e., IP Packets dropped at the MAC layer due to buffer overflow Packets with a specific destination address transmitted on the channel Packets broadcast to all radios within transmission range Packets destined for this specific radio and successfully received Packets destined for all radios and successfully received by this radio QualNet 4.0 Wireless Model Library 93

94 Wireless Model Library Digital Elevation Model (DEM) Terrain Terrain Data Type The TERRAIN-DATA-TYPE parameter specifies the type of terrain data to interface with. TERRAIN-DATA-TYPE The available options for this parameter are as follows: Digital Elevation Model (DEM) format terrain data is a standard, widely-available format. Digital Terrain Elevation Data (DTED) - provides basic quantitative data for systems and application that require terrain elevation, slope, and surface roughness information. Note: QualNet can include multiple terrain files. At the customer s request, DTED1 and DTED2 can also be mixed. Contact QualNet Sales for more information on this. Irregular Terrain Use the following parameters to specify irregular terrain: DEM-FILENAME - Specifies the relative or absolute path and filename for the DEM data file for the selected terrain. Note: Only one-degree DEM format is supported in QualNet. Note: The relative path is relative to the [QUALNET_HOME] path. DTED-FILENAME - Specifies the relative or absolute path and filename for the DTED data file. TERRAIN-DATA-BOUNDARY-CHECK - Checks the boundary of terrain data. Options are YES and NO. The default is YES. If TERRAIN-DATA-BOUNDARY-CHECK is set to YES, the simulation terminates when it attempts to use an elevation not included in the terrain data files. If set to NO, the execution assumes that such elevations are 0.0. To specify more than one file: TERRAIN-DATA-TYPE DEM DEM-FILENAME[0]../data/terrain/los_angeles-w DEM-FILENAME[1]../data/terrain/los_angeles-e TERRAIN-DATA-TYPE DTED DTED-FILENAME../data/terrain/s11e105.dt0 TERRAIN-DATA-BOUNDARY-CHECK NO The MOBILITY-GROUND-NODE parameter, if turned on (YES) uses the terrain file to determine the altitude coordinates of nodes. Each node's coordinates (x, y or lat, lon) are fed to the mobility model, and the altitude of the ground at those coordinates is used as the Z (altitude) coordinate for the node. This parameter overrides any Z coordinates that appear in node position or mobility trace files or models. It can be specified using node-specific or network-specific parameterization. # MOBILITY-GROUND-NODE YES 94 QualNet 4.0 Wireless ModelLibrary

95 Digital Elevation Model (DEM) Terrain For more information, please see the following websites: The government standard is currently available at: Data Sets Information is available at: Legacy/"native" format 1x1 degree information is available at: QualNet 4.0 Wireless Model Library 95

96 Wireless Model Library Directional Antennas QualNet provides the following directional antenna models: Omnidirectional - The antenna model returns 0 dbi gain in all directions. Switched-Beam - Stores multiple radiation patterns and returns Ga and Ge for a given direction with a specified pattern. Steerable - Steerable antenna model. Configuration Configure these models as follows: ANTENNA-MODEL OMNIDIRECTIONAL ANTENNA-MODEL SWITCHED-BEAM ANTENNA-MODEL STEERABLE Parameters Table 27 shows the parameters for the Directional Antenna Mode: TABLE 27. Directional Antenna Mode Parameters Parameter ANTENNA-EFFICIENCY ANTENNA-MISMATCH-LOSS ANTENNA-CABLE-LOSS ANTENNA-CONNECTION-LOSS ANTENNA-GAIN ANTENNA-HEIGHT Explanation Efficiency of the antenna. Example: ANTENNA-EFFICIENCY 0.8 Mismatch loss (in db). Example: ANTENNA-MISMATCH-LOSS 0.3 Antenna cable loss (in db). Example: ANTENNA-CABLE-LOSS 0.0 Connection loss (in db). Example: ANTENNA-CONNECTION-LOSS 0.2 Antenna Gain. Represents the antenna gain in db. Increasing the antenna gain increases the radio s range. Example: ANTENNA-GAIN 0.0 Antenna Height. Represents the antenna height in meters. Example: ANTENNA-HEIGHT QualNet 4.0 Wireless ModelLibrary

97 Directional Antennas TABLE 27. Directional Antenna Mode Parameters (Continued) Parameter ANTENNA-AZIMUTH-PATTERN-FILE ANTENNA-ELEVATION-PATTERN-FILE Explanation Antenna Azimuth Pattern. Specifies the filename for an antenna pattern file that determines the gain provided by each pattern at each angle. Example: ANTENNA-AZIMUTH-PATTERN-FILE./default.antenna-azimuth Note: This is used only when SWITCHED-BEAM is selected. The first line in the Azimuth Pattern file indicates the number of patterns to follow: NUMBER-OF-RADIATION-PATTERNS <numpatterns> The remaining lines in the Azimuth Pattern file are of the following format: <patternindex> <angle> <gain> Where: patternindex is the pattern number, from 0 to (NUMBER- OF-RADIATION-PATTERNS ñ 1) angle is in degrees where 0 is north gain is the antenna gain for this pattern, at this angle, in dbi. Antenna Elevation Pattern File. Specifies the filename for an antenna pattern file that determines the gain provided by each pattern at each angle. Example: ANTENNA-ELEVATION-PATTERN-FILE./default.antennaelevation Note: This file is an option only for 3-dimensional antenna patterns. The first line in the Elevation Pattern file indicates the number of patterns to follow: NUMBER-OF-RADIATION-PATTERNS <numpatterns> The remaining lines in the Elevation Pattern file are of the following format: <patternindex> <angle> <gain> Where: patternindex is the pattern number, from 0 to (NUMBER- OF-RADIATION-PATTERNS ñ 1) angle is in degrees where 0 is perpendicular to the antenna gain is the antenna gain for this pattern, at this angle, in dbi. QualNet 4.0 Wireless Model Library 97

98 Wireless Model Library DSR Dynamic Source Routing (DSR) is an on-demand routing protocol that is specifically designed for use in multi-hop wireless ad hoc networks of mobile nodes. DSR builds routes only on-demand by flooding ROUTE REQUEST packets if a sender wishes to send data to a destination with no known route. In addition to the on-demand algorithm, DSR implements a set of optimizations to attempt to route packets more efficiently, and reduce the control overhead. Configuration To configure DSR in Animator, complete the following steps: 1. Select the Inspector tab. 2. Go to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. 3. Select Dynamic. 4. Select Routing Protocol properties as DSR from the list. 5. Specify DSR properties Max Buffer Packet and Max Buffer Size if required. To select DSR as the routing protocol, place the following entry in *.config: ROUTING-PROTOCOL DSR Parameters DSR takes the parameters shown in Table 28: TABLE 28. DSR Parameters Parameter DSR-BUFFER-MAX-PACKET DSR-BUFFER-MAX-BYTE Description Specifies the maximum size of the message buffer in packets. The default value is 50. Specifies the maximum size of the message buffer in bytes. When not specified, the value of DSR-BUFFER-MAX-PACKET is used. Statistics Table 29 shows the statistics collected by DSR: TABLE 29. DSR Statistics Collected Statistic Number of RREQ Initiated Number of RREQ Retried Number of RREQ Forwarded Number of RREQ received Number of Duplicate RREQ received Explanation Number of Route Request initiated by a node Number of Route Request retransmitted by a node Number of Route Request forwarded by a node Number of Route Request received by a node Number of duplicate Route Request received 98 QualNet 4.0 Wireless ModelLibrary

99 DSR TABLE 29. DSR Statistics Collected (Continued) Number RREQ ttl expired Number RREQ received by Dest Number RREQ discarded for loop Number of RREP Initiated as Dest Number of RREP Initiated as intermediate node Number of RREP Received Number of RREP Received as Source Number of RERR Initiated Number of RERR received as source Number of RERR received Number of Data packets sent as Source Number of Data Packets Forwarded Number of Data Packets Received Number of Data Packets Dropped for no route Number of Data Packets Dropped for buffer overflow Number of times Retransmission failed Number of Routes Selected Number of Hop Counts Number of packet salvaged Number of times Mac failed to transmit data Number of Packets Dropped for Exceeding MTU Number of Route Request received by a node which was not relayed because of expiration of TTL Number of Route Request received as the target node Number of Route Request discarded for detecting a routing loop Number of Route Reply originated at target node Number of cached route reply originated as an intermediate node Number of Route Reply received by a node Number of Route Reply received by the source node Number of Route Error originated by a node Number of Route Error received by the source node Number of Route Error received by an intermediate node Number of data packets sent by a node Number of data packets forwarded by a node Number of data packets received by a destination node Number of packets dropped from DSR packet buffer because of no route Number of data packets dropped from packet buffer for overflow Number of data packets dropped after Maximum Retransmission Number of new route found by a node Accumulated number of hops of all routes found by DSR at a node Number of packets a node salvaged Number of times MAC layer failed to transmit a data packet. Number of data packets dropped because it's size exceeds MTU QualNet 4.0 Wireless Model Library 99

100 Wireless Model Library DTED This section describes the steps required in creating a DTED terrain based scenario. QualNet supports use of multi-resolution DTED files (levels 0, 1 and 2) in the graphical IDE. Sample Scenario A sample DTED scenario (dtedtest.scn) is included in the gui/scenarios directory. The terrain area covered by this scenario has a South-West Corner: 12S, 105E and a North-East Corner: 9S, 106E. Three onedegree DTED level 0 files (s12e105.dt0, s11e105.dt0 and s10e105.dt0) are used to provide basic coverage of the entire area. A DTED level 2 file (s11e105.dt2) is used to provide high-resolution coverage of the area of interest. These files are located in the gui/scenarios/dtedtest directory. FIGURE 59. Sample DTED Scenario 100 QualNet 4.0 Wireless ModelLibrary

101 DTED Setting Up A DTED Scenario To create a scenario using a DTED file as the terrain requires access to the DTED files and knowing their terrain dimensions. DTED files are generally distributed in a 1 degree by 1 degree format. Users will need to provide the coordinates of the South-West and North-East corners of the desired terrain. 1. Set Coordinate System to Latitude-Longitude as shown in Figure 60. FIGURE 60. Setting Coordinate System to Latitude-Longitude 2. Click on the Detailed Properties tab and set the terrain dimensions (SW and NE corners). 3. Set Terrain Data Format to DTED, as shown in Figure 61. QualNet 4.0 Wireless Model Library 101

102 Wireless Model Library FIGURE 61. Setting Terrain Type to DTED 4. Set the file location of the first DTED file by clicking on the button shown below and specifying the file name in the Configurable Property tab of the Properties Explorer. Add additional DTED files, as necessary, by right clicking on the first file, selecting Add Another and then specifying their location, the same as was done for the first file. 102 QualNet 4.0 Wireless ModelLibrary

103 DTED FIGURE 62. Specifying DTED Files 5. Enable Ground Node Elevation to be Yes so that nodes will use the altitude specified in the terrain file at their latitude-longitude as their elevation. QualNet 4.0 Wireless Model Library 103

104 Wireless Model Library FIGURE 63. Enabling Ground Node Elevation 6. Set other properties of the scenario. 7. Place nodes at desired positions and run the scenario. 104 QualNet 4.0 Wireless ModelLibrary

105 DYMO DYMO The DYnamic MANET On-demand (DYMO) routing protocol is a unicast reactive routing protocol which is intended for used by mobile nodes in wireless multihop networks. DYMO is a reactive routing protocol. In this Routing Message (Control Packet) is generated only when the node receives a data packet and it does not have any routing information. The basic operation of DYMO protocol is route discovery and route management. During route discovery the Route Request (RREQ) routing message is generated for a target for which it does not have any routing formation. So the originating node floods the RREQ message to find the target node. During flooding each intermediate node records a route to the originating node by maintaining routing table. When the target node receives the RREQ, it responds with a Route Reply (RREP) which is unicast toward the originating node. Each node that receives the RREP records a route to the target node, and forwards the RREP to next hop. When the originating node receives the RREP, routes have been established between the originating node and the target node in both directions. In order to react changes in the network topology nodes maintain their routes and monitor their links. When a packet is received for a route that is no longer available the source of the packet generates Route Error (RERR). This RERR RM notifies other nodes that the current route is broken. Once the source receives the RERR, it re-initiates route discovery if it still has packets to deliver. In order to maintain active route it uses hello message broadcasting scheme. DYMO uses standard MANET packet structure. DYMO uses sequence numbers to avoid loop freedom, so that old routing information will not be propagated further. Configuration To configure DYMO at specific node or subnet or IPv6 interface, specify the following configuration in the *.config file: [Global Node Id IPv4 Address] ROUTING-PROTOCOL DYMO [Global Node Id IPv6 Address] ROUTING-PROTOCOL DYMO Parameters Table 30 shows the optional configuration parameters for DYMO. TABLE 30. DYMO Optional Configuration Parameters Parameter DYMO-NET-DIAMETER DYMO-NODE-TRAVERSAL-TIME: DYMO-VALID-ROUTE-TIMEOUT DYMO-DELETE-ROUTE-TIMEOUT Description This parameter specifies the maximum possible number of hops between two nodes in the network. The default value is 10 hops. This is the conservative estimate of the average one-hop traversal time for packets and should include queuing, transmission, propagation and other delays. The default value is 40ms. This is the timeout time for an active route; each time a data packet is sent, the lifetime of that route is updated to this value. The default value is 5000ms..After expiration of this duration node will remove this path from routing table. The default value is 5 * DYMO-VALID-ROUTE-TIMEOUT. QualNet 4.0 Wireless Model Library 105

106 Wireless Model Library TABLE 30. DYMO Optional Configuration Parameters (Continued) Parameter DYMO-HELLO-INTERVAL DYMO-ALLOWED-HELLO-LOSS DYMO-RREQ-RETRIES DYMO-PROCESS-HELLO DYMO-BUFFER-MAX-PACKET Table 31 shows the Gateway Configuration: Description Lifetime of a hello message using the following equation: DYMO-ALLOWED_HELLO_LOSS * DYMO-HELLO_INTERVAL. The default value is 1000ms. This is the number of times for DYMO will repeat expanded ring search for a destination, if no Route Reply is received within the specified amount of time. The default value is 2 times. Specifies the number of times for DYMO will repeat expanded ring search for a destination, if no Route Reply is received within the specified amount of time. The default value is 3 times. If the value is set to YES, a node will send a hello message, if there is no broadcast within the last hello interval. The default value is NO. Maximum number of packets the message buffer of DYMO can hold. If the buffer fills up, incoming packets for the buffer will be dropped. The default value is 100 packets. DYMO -TTL-START Specifies the ttl value when initiating a route request. The default value is 1. DYMO-TTL-INCREMENT Specifies the value by which the ttl is incremented each time a request is transmitted. The default value is 2. DYMO -TTL-THRESHOLD. Specifies the maximum value of ttl over which NET_DIAMETER value will be used to broadcast Route Request. The default value is 7. TABLE 31. Gateway Configuration Parameter GATEWAY-NODE GATEWAY-PREFIX_LENGTH Description This parameter specifies if interface is selected for gateway.the default value is NO. Specifies the number of bits common in the gateway enabled. The default value is 16 bits. Configuration Using the GUI/Animator To configure the DYMO routing protocol in Animator, use the following steps: 1. Inside the Inspector window, navigate to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. Change the Routing Policy to Dynamic using the Configurable Property window, as shown in Figure QualNet 4.0 Wireless ModelLibrary

107 DYMO FIGURE 64. Changing the Routing Policy to Dynamic 2. Navigate to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy -> Routing Protocol. Select DYMO as the Routing Protocol, using the Configurable Property window shown in Figure 65. QualNet 4.0 Wireless Model Library 107

108 Wireless Model Library FIGURE 65. Configuring the DYMO Parameters 3. Click on the Detailed Properties of DYMO to configure the configuration parameters. You must set the respective value for all configurable parameters, or they will be set to default values. See Figure QualNet 4.0 Wireless ModelLibrary

109 DYMO FIGURE 66. Setting the DYMO Parameter Values 4. To configure a node as DYMO gateway, follow these steps: QualNet 4.0 Wireless Model Library 109

110 Wireless Model Library a. Navigate to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy -> Routing Protocol. b. Select DYMO as the Routing Protocol using the Configurable Property window. c. Select Is Gateway using the Configurable Property window as shown in Figure 67. d. Set value of Is Gateway to Yes. By default, this value is No. FIGURE 67. Configuring a Node as DYMO Gateway 5. Click on the Detailed Properties to configure the Gateway Prefix Length. This parameter specifies the prefix length of the MANET subnet. The default prefix length is 24, as shown in Figure QualNet 4.0 Wireless ModelLibrary

111 DYMO FIGURE 68. Setting the Gateway Prefix Length QualNet 4.0 Wireless Model Library 111

112 Wireless Model Library Statistics Table 32 shows the statistics collected by DYMO TABLE 32. DYMO Statistics Collected Statistic Number Of RREQ Initiated Number Of RREQ Retried Number Of RREQ Forwarded Number Of RREQ Received Number Of Duplicate RREQ Received Number Of RREQ TTL expired Number RREQ Received By Target Number Of RREP Initiated As Target Number Of RREP Forwarded Number Of RREP Received Number Of RREP Received As Target Number Of Hello message Sent Number Of Hello message received Number Of RERR Initiated Number Of RERR Forwarded Number Of RERR Received Number Of RERR Discarded Number Of Data packets sent as originator Number Of Data Packets Forwarded Number Of Data Packets Received Number Of Data Packets Dropped For Buffer Overflow Number Of Times Link Broke Description Number of Route Request message Initiated. Number of Route Request message retried. Number of Route Request message forwarded. Number of Route Request message received. Number of duplicate Route Request message received. Number of Route Request TTL (Time To Live) Expired. Number of Route Request received by target. Number of Route Reply initiated as target. Number of Route Reply forwarded. Number of Route Reply Received. Number of Route Reply Received as target. Number of Hello Message Sent. Number of Hello Message Received. Number of Route Error Initiated. Number of Route Error forwarded. Number of Route Error received. Number of Route Error discarded. Number of data packet sent as Originator. Number of data packet forwarded. Number of data packet received. Number of data packets dropped for buffer overflow. Number of times link broken. Examples Figure 69 is an example of how to use the DYMO routing protocol in the QualNet main configuration file (i.e. using *.config). It is a seven-node scenario with the routing protocol set to DYMO from node 1 to 5. Nodes 6 and 7 are connected through Wired Link (Static Route). Node 3 is the gateway node. 112 QualNet 4.0 Wireless ModelLibrary

113 DYMO Wireless Subnet FIGURE 69. Using the DYMO Routing Protocol Configuration Example Using the Simulator *.config file Specify the following parameters in the *.config file: SIMULATION-TIME 10M // The scenario is executed for a simulation time of 10minutes. # Default routes have less priority than static routes and those discovered by routing protocols DEFAULT-ROUTE YES DEFAULT-ROUTE-FILE MANET-static-route.routes-default LINK N { 3, 6 } [ ] LINK-MAC-PROTOCOL ABSTRACT [ ] LINK-PHY-TYPE WIRED [ ] LINK-PROPAGATION-DELAY 1MS [ ] LINK-BANDWIDTH [ ] NETWORK-PROTOCOL IP [ ] SWITCH-STATION-VLAN-ID 0 [ ] SWITCH-STATION-VLAN-TAGGING NO LINK N { 6, 7 } [ ] LINK-MAC-PROTOCOL ABSTRACT QualNet 4.0 Wireless Model Library 113

114 Wireless Model Library [ ] LINK-PHY-TYPE WIRED [ ] LINK-PROPAGATION-DELAY 1MS [ ] LINK-BANDWIDTH [ ] NETWORK-PROTOCOL IP [ ] SWITCH-STATION-VLAN-ID 0 [ ] SWITCH-STATION-VLAN-TAGGING NO [ 1 thru 5 ] DUMMY-ROUTING DYNAMIC [ 1 thru 5 ] ROUTING-PROTOCOL DYMO [ 1 thru 5 ] DYMO-NET-DIAMETER 10 [ 1 thru 5 ] DYMO-NODE-TRAVERSAL-TIME 40MS [ 1 thru 5 ] DYMO-VALID-ROUTE-TIMEOUT 5S [ 1 thru 5 ] DYMO-DELETE-ROUTE-TIMEOUT 25S [ 1 thru 5 ] DYMO-HELLO-INTERVAL 1S [ 1 thru 5 ] DYMO-ALLOWED-HELLO-LOSS 2 [ 1 thru 5 ] DYMO-RREQ-RETRIES 3 [ 1 thru 5 ] DYMO-PROCESS-HELLO NO [ 1 thru 5 ] DYMO-BUFFER-MAX-PACKET 100 [ 1 thru 5 ] DYMO-BUFFER-MAX-BYTE 0 [ 1 thru 5 ] DYMO-TTL-START 1 [ ] DYMO-GATEWAY NO [ ] DYMO-GATEWAY-PREFIX-LENGTH 16 [ 1 thru 5 ] DYMO-TTL-INCREMENT 2 [ 1 thru 5 ] DYMO-TTL-THRESHOLD 7 [ ] STATIC-ROUTE NO [ 3 ] DYMO-GATEWAY YES [ 3 ] DYMO-GATEWAY-PREFIX-LENGTH 24 [ ] STATIC-ROUTE YES [ ] STATIC-ROUTE-FILE manet-static-route.routes-static [ 6 7 ] DUMMY-ROUTING NONE [ 6 7 ] ROUTING-PROTOCOL NONE *.app file Specify the following parameters in the *.app file: CBR S 1S 0S PRECEDENCE 0 CBR S 1S 0S PRECEDENCE 0 Node 1 is sending 100 packets to node 7. Similarly, Node 7 is sending 100 packets to node 5. It is a Gateway scenario, in which node 3 is the gateway and there is a static route between nodes 6 and 7. Configuration Example Using the GUI Follow these steps to configure in the GUI: 1. Create a new Scenario inside the Inspector window by: a. Navigating to ConfigSettings -> General -> General -> Experiment Name. b. Configure the Simulation time and Experiment name using the Configurable Property window, as shown in Figure QualNet 4.0 Wireless ModelLibrary

115 DYMO FIGURE 70. Configuring the Simulation Time and Experiment Name Adding Nodes and Links Follow these steps to add nodes and links: 1. Select the Devices tab in the Scenario Designer window. 2. Select the Default icon and place seven nodes. 3. Connect Nodes 1 through 5 using Subnet. 4. Select the Links tab in the Scenario Designer window. 5. Select the Link icon and connect the nodes using links. 6. Connect Nodes 3, 6, 7 with the wired link by first selecting the Links tab in the Scenario Designer window. 7. Select the Link icon and connect the nodes. QualNet 4.0 Wireless Model Library 115

116 Wireless Model Library Setting Network and Routing Protocols Follow these steps to set network and routing protocols: 1. Navigate to Connections -> Point to point link -> Network Protocol. 2. Change the Network Protocol to IPv4 using the Configurable Property window. 3. Navigate to ConfigSettings -> Network Protocol -> Routing Protocol -> Routing Policy. 4. Select None as the Routing Policy using the Configurable Property window. 5. Navigate to Node Configurations -> Network Protocol -> Routing Protocol -> Routing Policy. 6. Select None as the Routing Protocol using the Configurable Property window. 7. Navigate to Hierarchy(0) -> Nodes -> host2 -> Node Configurations -> Network Protocol -> Routing Protocol. 8. Select DYMO as the Routing Protocol using the Configurable Property window. 9. Similarly, set Routing Protocol as DYMO for host 4 and Click on the Detailed Properties of DYMO to configure the required configurations parameters. 11. Set the respective value of all the configurable parameters, otherwise the default values are automatically set. See Figure 71. FIGURE 71. Setting the Parameter Values 116 QualNet 4.0 Wireless ModelLibrary

117 DYMO Configuring DYMO Gateway To configure node 3 as DYMO Gateway, follow these steps. 1. Navigate to Hierarchy(0) -> Nodes -> host3 -> Node Configurations -> Network Protocol -> Routing Protocol. 2. Select DYMO as the Routing Protocol using the Configurable Property window. 3. Select Is Gateway using the Configurable Property window as shown in as shown in Figure Select Yes as the value. FIGURE 72. Configuring Node 3 as DYMO Gateway Adding Static Routes Follow these steps to add static routes. 1. Inside Inspector window, navigate to Nodes -> host3 -> Network Protocol -> Routing Protocol -> Static Routes. 2. Select Use Static Route in the Configurable Property window. 3. Click on Detailed Properties and give the path to the static route file: manet-static-route.routesstatic. QualNet 4.0 Wireless Model Library 117

118 Wireless Model Library Using the Property Editor 4. Select the Applications tab in the Scenario Designer window. 5. Select CBR and set the Application link from Node 1 to Node 7 and from Node 7 and Node Set the Application Parameters as follows, using the Configurable Property window. Source is the client node. Destination is the server node. Item to Send is how many application layer items to send. Item Size is the size of each application layer item. Interval is the interdeparture time between the application layer items. Start Time is when to start CBR during the simulation. End Time is when to terminate CBR during the simulation. 7. Navigate to ConfigSettings -> Statistics -> Statistics Routing -> Statistics. 8. Select Yes as the Routing Statistics using the Configurable Property window. Executing the scenario Follow these steps to execute the scenario. 1. Save the changes by clicking on Save. 2. Click on the Run button to execute the scenario. 118 QualNet 4.0 Wireless ModelLibrary

119 Fading Fading The Fading Models available in QualNet 4.0 are narrowband flat fading models that implement the Rayleigh and Ricean distributions. The Rayleigh distribution is useful in highly mobile cases and signals without line of sight. The Ricean distribution is more useful in the presence of line of sight. The PROPAGATION-FADING-MODEL parameter specifies the distribution to use. This can be either a global default, or specified per channel, using the Instance ID specification, as in the example below. Table 33 shows the fading models found in QualNet. PROPAGATION-FADING-MODEL[0] NONE PROPAGATION-FADING-MODEL[1] RAYLEIGH # PROPAGATION-FADING-MODEL RICEAN # PROPAGATION-RICEAN-K-FACTOR 0.0 TABLE 33. Fading Models in QualNet Model Rayleigh Ricean High Speed None Explanation The Rayleigh Distribution The Ricean Distribution. The Ricean K factor is given using the PROPAGATION-RICEAN-K-FACTOR parameter Handles the rapidly changing conditions of objects moving at high speed No Fading Model Configuration Fading model requires the following parameters to be set in the *.config file: PROPAGATION-FADING-GAUSSIAN-COMPONENTS-FILE PROPAGATION-FADING-MAX-VELOCITY PROPAGATION-FADING-GAUSSIAN-COMPONENTS-FILE is the file that stores series of Gaussian components. The file should include the following variables at the beginning of file, followed by the actual Guassian components: SAMPLING-RATE (in Hz) BASE-DOPPLER-FREQUENCY (in Hz) NUMBER-OF-GAUSSIAN-COMPONENTS PROPAGATION-FADING-MAX-VELOCITY It specifies the maximum velocity of any object on the terrain. High Speed Fading As shown in the following figure, motion effects for high speed aircraft are enabled in the wireless settings of the global parameters in the GUI. The Fading Model must be set to High Speed Fading, and the subparameter for Fading Gaussian Components File be set to the provided default.fading file in the bin/ directory. QualNet 4.0 Wireless Model Library 119

120 Wireless Model Library Whereas the Ricean and Rayleigh fading models use a fixed maximum velocity, the high speed model dynamically calculates the actual speed of the nodes to determine fading values. This results in rapidly changing conditions. A sample scenario is provided in gui/scenarios/motioneffects.scn. One node in the scenario is moving at ~250mps, while the other is stationary. Run this sample with and without the high speed fading model to see the impact on network throughput. Parameters The Rayleigh Fading model reports how much and how fast the received signal power fluctuates because of fading by considering Doppler frequency. Rayleigh is a special form and equal to Ricean with K factor of 0.0. The required parameters are shown in Table 34: TABLE 34. Fading Parameters Parameters PROPAGATION-FADING-GAUSSIAN- COMPONENTS-FILE PROPAGATION-FADING-MAX-VELOCITY PROPAGATION-RICEAN-K-FACTOR Description Rayleigh - A file that stores a series of Gaussian components. Ricean - The maximum velocity of any objects on the terrain. Ricean K factor (linear value) - This fading model reports how much and how fast the received signal power fluctuates because of fading by considering Doppler frequency. It requires an additional parameter to be specified in the *.config file. As shown in Figure 73, motion effects for high speed aircraft are enabled in the wireless settings of the global parameters in the GUI. The Fading Model must be set to High Speed Fading, and the subparameter for Fading Gaussian Components File be set to the provided default.fading file in the bin/ directory. 120 QualNet 4.0 Wireless ModelLibrary

121 Fading FIGURE 73. High Speed Fading Whereas the Ricean and Rayleigh fading models use a fixed maximum velocity, the high speed model dynamically calculates the actual speed of the nodes to determine fading values. This results in rapidly changing conditions. A sample scenario is provided in gui/scenarios/motioneffects.scn. One node in the scenario is moving at ~250mps, while the other is stationary. Run this sample with and without the high speed fading model to see the impact on network throughput. QualNet 4.0 Wireless Model Library 121

122 Wireless Model Library Fisheye State Routing Fisheye State Routing (FSR) is a link state type protocol that maintains a topology map at each node. FSR differs from the standard link state algorithm by the following: Having only neighboring nodes exchange the link state information Utilizing only time-triggered, not event-triggered link state exchanges Using different exchange intervals for nearby versus far away nodes Configuration To select FSR as the routing protocol in *.config, place the following entry in *.config. See Table 35. ROUTING-PROTOCOL FISHEYE Parameters Table 35 shows the Fisheye State Routing parameters: TABLE 35. Fisheye State Routing Parameters Parameter FISHEYE-SCOPE FISHEYE-INTRA-UPDATE-INTERVAL FISHEYE-INTER-UPDATE-INTERVAL FISHEYE-NEIGHBOR-TIMEOUT- INTERVAL Definition Fisheye scope. Example: FISHEYE-SCOPE 2 Note: The default is 2. Routing table update frequency within the fisheye scope. Example: FISHEYE-INTRA-UPDATE-INTERVAL 5S Note: The default is 5 seconds. Routing table update frequency outside of the fisheye scope. Example: FISHEYE-INTER-UPDATE-INTERVAL 15S Note: The default is 15 seconds. Expiration period of the neighbor list. Example: FISHEYE-NEIGHBOR-TIMEOUT-INTERVAL 15S Note: The default is 15 seconds. 122 QualNet 4.0 Wireless ModelLibrary

123 Group Mobility Group Mobility The group mobility model is for simulating the group movement behaviors in the real world, such as a group of travelers, etc. The members of the same group tend to have similar movement tracks. However, inside the group, members also have relative mobility. To depict such behaviors, the mobility vector of a node can be considered as the sum of two mobility vectors. One is called the group mobility vector, which is shared by all members of the same group. The other is called the internal mobility vector which represents the relative mobility of a node inside the group. The vector sum of the two mobility vectors decides the mobility of the node. The movements of a node are also limited by the group boundary. In QualNet, the two mobility vectors, group mobility vector and internal mobility vector, are simulated by using the random waypoint mobility model independently. Configuration and Parameters Need basic configuration information Table 36 shows the group mobility-related parameters, which fall into three categories: Defining Groups - you must specify the group membership and the initial group area. Group Node Placement - Used to guarantee that group nodes are distributed inside the initial group area. This is optional for using group mobility model. However, if group node placement is not used, you must guarantee that initial positions of nodes in a group are inside the group boundary. Group Mobility - including group mobility vector and internal mobility vector. TABLE 36. Group Mobility Parameters Parameter Description Defining Groups NUM-MOBILITY-GROUPS <number-of-groups> Defines how many groups are specified in this scenario. Example: NUM-MOBILITY-GROUPS 4 MOBILITY-GROUP[<group-id>] {<node-id-list>} Specifies nodes in each group. Where: <group-id> is from 0 to (NUM-MOBILITY- GROUPS 1). <node-id-list> gives the nodes in this mobility group. Examples: MOBILITY-GROUP[0] {1 through 25} MOBILITY-GROUP[1] {26 through 50} MOBILITY-GROUP[2] {51 through 75} MOBILITY-GROUP[3] {76 through 100} QualNet 4.0 Wireless Model Library 123

124 Wireless Model Library TABLE 36. Group Mobility Parameters (Continued) Parameter GROUP-AREA[<group-id>] <origin> <dimension> GROUP-AREA-ORIGIN[<group-id>] <origin> GROUP-AREA-DIMENSION[<group-id>] <dimension> GROUP-TERRAIN-CONSTRAINT-SOUTH-WEST- CORNER[<group-id>] <southwest corner> GROUP-TERRAIN-CONSTRAINT-NORTH-EAST- CORNER[<group-id>] <northeast corner> GROUP-TERRAIN-CONSTRAINT-LOWER-LEFT- CORNER[<group number>] <lower left corner> GROUP-TERRAIN-CONSTRAINT-UPPER-RIGHT- CORNER[<group number>] (upper right corner> Description Specifies the initial group area of the group indicated. Where: <group-id> indicates the group identification. <origin> indicates the origin of the group area. <dimension> indicates dimensions of the group area. Examples: GROUP-AREA[0] (0, 0) (750, 750) GROUP-AREA[1] (750, 0) (750, 750) GROUP-AREA[2] (0, 750) (750, 750) GROUP-AREA[3] (750, 750) (750, 750) Alternatively, the GROUP-AREA parameter can be replaced by two separate parameters. Where: <origin> specifies the origin of the group area. <dimension> specifies dimensions of the group area. Examples: GROUP-AREA-ORIGIN[0] (0, 0) GROUP-AREA-DIMENSION[0] (750, 750) GROUP-AREA-ORIGIN[1] (750, 0) GROUP-AREA-DIMENSION[1] (750, 750) GROUP-AREA-ORIGIN[2] (0, 750) GROUP-AREA-DIMENSION[2] (750, 750) GROUP-AREA-ORIGIN[3] (750, 750) GROUP-AREA-DIMENSION[3] (750, 750) Used for the LATLONALT coordinate system to influence the group movement within a particular region. These parameters are optional. If not specified, the whole terrain is assumed. Examples: GROUP-TERRAIN-CONSTRAINT-SOUTH-WEST- CORNER[0] (-0.005, ) GROUP-TERRAIN-CONSTRAINT-NORTH-EAST- CORNER[0] (0, 0) Used for the CARTESIAN coordinate system to influence the group movement within a particular region. These parameters are optional. If not specified, the whole terrain is assumed. Examples: GROUP-TERRAIN-CONSTRAINT-LOWER-LEFT- CORNER[0] (0, 750) GROUP-TERRAIN-CONSTRAINT-UPPER-RIGHT- CORNER[0] (750, 1500) NODE-PLACEMENT GROUP Group Node Placement Indicates using GROUP node distribution for placing nodes. 124 QualNet 4.0 Wireless ModelLibrary

125 Group Mobility TABLE 36. Group Mobility Parameters (Continued) Parameter GROUP-NODE-PLACEMENT[<group-id>] RANDOM UNIFORM GRID Description Specifies how nodes in each group are initially placed. Examples: GROUP-NODE-PLACEMENT[0] UNIFORM GROUP-NODE-PLACEMENT[1] UNIFORM GROUP-NODE-PLACEMENT[2] UNIFORM GROUP-NODE-PLACEMENT[3] UNIFORM Group Mobility Parameters MOBILITY-GROUP-MOBILITY MOBILITY-GROUP-PAUSE[group-id] <time> MOBILITY-GROUP-MIN-SPEED[group-id] <speed> MOBILITY-GROUP-MAX-SPEED[group-id] <speed> MOBILITY-GROUP-INTERNAL-PAUSE[group-id] <time> MOBILITY-GROUP-INTERNAL-MIN-SPEED[group-id] <speed> MOBILITY-GROUP-INTERNAL-MAX-SPEED[group-id] <speed> Indicates that group mobility is specified. Specifies the pause period, minimum speed, and maximum speed of the group movements. The speeds are in meters per second. Examples: MOBILITY-GROUP-PAUSE[1] 0S MOBILITY-GROUP-MIN-SPEED[1] 40S MOBILITY-GROUP-MAX-SPEED[1] 60 Specify the pause period, minimum speed, and maximum speed of the internal movements. The speeds are in meters per second. Examples: MOBILITY-GROUP-INTERNAL-PAUSE[1] 10S MOBILITY-GROUP-INTERNAL-MIN-SPEED[1] 10S MOBILITY-GROUP-INTERNAL-MAX-SPEED[1] 20S Statistics None Examples The following sample scenario demonstrates the above group mobility parameters. In this scenario, a total of five groups are defined. They are: Group 0: From node 1 to node 40. This group is static, with nodes scattered in the whole simulation field. Group 1: From node 41 to node 50. This is a fast moving group with speed between 40 m/s to 60 m/s. Group 2: From node 51 to node 60. This is a fast moving group with speed between 20 m/s to 40 m/s. Group 3: From node 61 to node 70. This is a middle-speed moving group with speed between 10 m/s to 20 m/s. Group 4: From node 71 to node 80. This is a slow-moving group with speed between 1 m/s to 10 m/s. To configure the above mobility scenario, use the following parameters: # a total of 80 nodes in the scenario SUBNET N16-0 {1 thru 80} QualNet 4.0 Wireless Model Library 125

126 Wireless Model Library # define groups NUM-MOBILITY-GROUPS 5 MOBILITY-GROUP[0] {1 thru 40} MOBILITY-GROUP[1] {41 thru 50} MOBILITY-GROUP[2] {51 thru 60} MOBILITY-GROUP[3] {61 thru 70} MOBILITY-GROUP[4] {71 thru 80} # define initial group areas GROUP-AREA-ORIGIN[0] (0, 0) GROUP-AREA-DIMENSION[0] (1500, 1500) GROUP-AREA-ORIGIN[1] (150, 150) GROUP-AREA-DIMENSION[1] (450, 450) GROUP-AREA-ORIGIN[2] (900, 150) GROUP-AREA-DIMENSION[2] (450, 450) GROUP-AREA-ORIGIN[3] (150, 900) GROUP-AREA-DIMENSION[3] (450, 450) GROUP-AREA-ORIGIN[4] (900, 900) GROUP-AREA-DIMENSION[4] (450, 450) # specify group node placement NODE-PLACEMENT GROUP # specify group mobility model and configure movement speeds MOBILITY GROUP-MOBILITY # group 0 is static MOBILITY-GROUP-PAUSE[0] 0S MOBILITY-GROUP-MIN-SPEED[0] 0 MOBILITY-GROUP-MAX-SPEED[0] 0 MOBILITY-GROUP-INTERNAL-PAUSE[0] 0S MOBILITY-GROUP-INTERNAL-MIN-SPEED[0] 0 MOBILITY-GROUP-INTERNAL-MAX-SPEED[0] 0 # group 1 is a fast moving group with speed between 40m/s to 60m/s MOBILITY-GROUP-PAUSE[1] 0S MOBILITY-GROUP-MIN-SPEED[1] 40 MOBILITY-GROUP-MAX-SPEED[1] 60 MOBILITY-GROUP-INTERNAL-PAUSE[1] 10S MOBILITY-GROUP-INTERNAL-MIN-SPEED[1] 10 MOBILITY-GROUP-INTERNAL-MAX-SPEED[1] 20 # group 2 is a fast moving group with speed between 20m/s to 40m/s MOBILITY-GROUP-PAUSE[2] 0S MOBILITY-GROUP-MIN-SPEED[2] 20 MOBILITY-GROUP-MAX-SPEED[2] 40 MOBILITY-GROUP-INTERNAL-PAUSE[2] 10S MOBILITY-GROUP-INTERNAL-MIN-SPEED[2] 10 MOBILITY-GROUP-INTERNAL-MAX-SPEED[2] 20 # group 3 is a middle speed moving group with speed between 10m/s to 20 m/s MOBILITY-GROUP-PAUSE[3] 10S MOBILITY-GROUP-MIN-SPEED[3] 10 MOBILITY-GROUP-MAX-SPEED[3] 20 MOBILITY-GROUP-INTERNAL-PAUSE[3] 10S 126 QualNet 4.0 Wireless ModelLibrary

127 Group Mobility MOBILITY-GROUP-INTERNAL-MIN-SPEED[3] 10 MOBILITY-GROUP-INTERNAL-MAX-SPEED[3] 20 # group 4 is a slow moving group with speed between 0m/s to 10m/s MOBILITY-GROUP-PAUSE[4] 10S MOBILITY-GROUP-MIN-SPEED[4] 1 MOBILITY-GROUP-MAX-SPEED[4] 10 MOBILITY-GROUP-INTERNAL-PAUSE[4] 10S MOBILITY-GROUP-INTERNAL-MIN-SPEED[4] 10 MOBILITY-GROUP-INTERNAL-MAX-SPEED[4] 20 Note: In above sample scenario, the moving groups have the same internal mobility speed. Note: Group Mobility is not currently configurable in the GUI/Animator. QualNet 4.0 Wireless Model Library 127

128 Wireless Model Library IARP IntrAzone Routing Protocol (IARP) is a component of the Zone Routing Protocol (ZRP). It is an proactive routing used inside the zone. However, it could be used standalone where nodes can only reach other nodes insider its zone. IARP follows draft-ietf-manet-zone-iarp-01. Configuration and Parameter To configure IARP, complete the following steps: 1. Select the Inspector tab. 2. Go to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. 3. Select Dynamic. 4. Select Routing Protocol properties as IARP from the list. 5. Specify IARP property IARP Zone Radius if required. IARP is enabled from main configuration file by the following statement: ROUTING-PROTOCOL IARP IARP accepts the following parameter: ZONE-RADIUS Used to specify the zone radius. The zone radius has to be greater than or equal to 0, or INFINITY. If Zone Radius is not given then a default zone radius of 2 assumed by the protocol. ZONE-RADIUS 2 Statistics Table 37 shows the statistics collected by IARP: TABLE 37. IARP Statistics Collected Statistic Number of triggered updates sent Number of regular updates sent Number of update messages relayed Number of update messages received Number of packets routed Explanation Number of triggered updates sent by the node Number of regular updates sent by the node Number of update messages relayed by the node Number of update messages received Number of packets routed 128 QualNet 4.0 Wireless ModelLibrary

129 IERP IERP IntErzone Routing Protocol (IERP) is a component of the Zone Routing Protocol (ZRP). It is used to discover a route to remote nodes outside of the zone of the node. However, it could be used as a standalone routing protocol. It is an on-demand routing protocol. IERP follows draft-ietf-manet-zone-ierp- 02. Configuration and Parameter To configure IERP, complete the following steps: 1. Select the Inspector tab. 2. Go to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. 3. Select Dynamic. 4. Select Routing Protocol properties as IERP from the list. 5. Specify IERP property IERP Zone Radius if required. IERP is enabled from main configuration file by the following statement: ROUTING-PROTOCOL IERP IERP accepts the following parameter: ZONE-RADIUS Used to specify the zone radius. The zone radius has to be greater than or equal to 0, or INFINITY. If Zone Radius is not given then a default zone radius of 0 assumed by the protocol. ZONE-RADIUS 0 IERP-MAX-MESSAGE-BUFFER-SIZE Used to define the maximum buffer size. If not specified, the default value will be 100. IERP-MAX-MESSAGE-BUFFER-SIZE 100 Statistics Table 38 shows the statistics collected by IERP: TABLE 38. IERP Statistics Collected Statistic Number of query packets sent Number of query packets received Number of query packets relayed Number of reply packets sent Explanation Number of query packets sent Number of query packets received by the node Number of query packets relayed by the node Number of reply packets sent QualNet 4.0 Wireless Model Library 129

130 Wireless Model Library TABLE 38. IERP Statistics Collected (Continued) Number of reply packets received Number of reply packets replayed Number of packets routed via IERP Number of data packets dropped because of buffer overflow Number of reply packets received Number of reply packets relayed Number of packets routed via IERP Number of data packets dropped because of buffer overflow 130 QualNet 4.0 Wireless ModelLibrary

131 ITM ITM The following two sections describe QualNet integration with irregular terrain files for propagation and mobility modeling. Terrain data provides information about the surface of the playing field that nodes are simulated on. Propagation models, such as Irregular Terrain Model (ITM), can use this information to calculate line-ofsight (LOS) between senders and receivers, ground-reflection characteristics, and path loss. All QualNet mobility models can use this information to update the altitude coordinates for nodes that move along the ground. The TERRAIN-DATA-TYPE parameter specifies the type of terrain data to interface with. TERRAIN-DATA-TYPE The available data type options for the Irregular Terrain Model are DEM - Digital Elevation Model (DEM) format terrain data is a standard, widely available format. CTDB - Compact Terrain DataBase (CTDB) format terrain data is used by various Semi-Automated Forces (SAFs such as ModSAF, OTB, and JSAF), and support for this format simplifies hybrid simulation with these tools. DTED - Digital Terrain Elevation Data. It provides basic quantitative data for systems and applications that require terrain elevation, slope, and surface roughness information. Note: QualNet can include multiple terrain files. At the customer's request, DTED1 and DTED2 can also be mixed. Contact QualNet Sales for more information on this. Configuration Table 39 shows the Terrain Data Type parameters: TABLE 39. Terrain Data Type Parameters Parameter DEM-FILENAME CTDB-FILENAME TERRAIN-DATA- BOUNDARY-CHECK Description Specifies the relative or absolute path and filename for the DEM data file for the selected terrain. Note: Only 1-degree DEM format is supported in QualNet. Specifies the relative or absolute path and filename for the CTDB data file for the selected terrain, and must be specified. Note: The relative path is relative to the [QUALNET_HOME] path. The program checks the boundary of terrain data. Options are YES and No. The default is YES. If TERRAIN-DATA-BOUNDARY-CHECK is set to YES, the simulation terminates when it attempts to use an elevation not included in the terrain data files. If it is NO, the execution assumes that such elevations are 0.0. QualNet 4.0 Wireless Model Library 131

132 Wireless Model Library Tie Nodes to Irregular Terrain The MOBILITY-GROUND-NODE parameter, if turned on (YES) uses the terrain file to determine the altitude coordinates of nodes. Each node's coordinates (x, y or lat, lon) are fed to the mobility model, and the altitude of the ground at those coordinates is used as the Z (altitude) coordinate for the node. This parameter overrides any Z coordinates that appear in node position or mobility trace files or models. It can be specified using node-specific or network-specific parameterization. # MOBILITY-GROUND-NODE YES Example To specify more than one file, use the following commands: TERRAIN-DATA-TYPE DEM DEM-FILENAME[0]../data/terrain/los_angeles-w DEM-FIlENAME[1]../data/terrain/los_angeles-e TERRAIN-DATA-TYPE CTDB CTDB-FILENAME nebosnia_mes TERRAIN-DATA-BOUNDARY-CHECK NO 132 QualNet 4.0 Wireless ModelLibrary

133 LANMAR LANMAR Landmark Ad Hoc Routing (LANMAR) protocol follows draft-ietf-manet-lanmar-04.txt and uses Fisheye (draft-ietf-manet-fsr-03.txt) as the local scope routing protocol. Configuration and Parameters To configure LANMAR in QualNet GUI, complete the following steps: 1. Select the Inspector tab. 2. Go to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. 3. Select Dynamic. 4. Select Routing Protocol properties as LANMAR from the list. 5. Specify LANMAR properties if required. LANMAR is enabled from the main configuration file by the following statement: ROUTING-PROTOCOL FSRL Table 40 shows LANMAR related parameters that are specified in the *.config file: TABLE 40. LANMAR Parameters Parameter ROUTING-PROTOCOL LANMAR-MIN-MEMBER-THRESHOLD Explanation Enables the LANMAR routing protocol. Example: ROUTING-PROTOCOL FSRL Note: This parameter is mandatory. Minimum number of neighbors in order to be considered a landmark. Defaults to 18 if not specified. Example: LANMAR-MIN-MEMBER-THRESHOLD 18 LANMAR-LANDMARK-UPDATE-INTERVAL Landmark update interval. Example: LANMAR-LANDMARK-UPDATE-INTERVAL 15S Note: This parameter is mandatory. LANMAR-NEIGHBOR-TIMEOUT-INTERVAL Landmark neighbor timeout interval. LANMAR-NEIGHBOR-TIMEOUT-INTERVAL 15S Note: This parameter is mandatory. LANMAR-LANDMARK-MAX-AGE Maximum age for landmark entries. Example: LANMAR-LANDMARK-MAX-AGE 10S Note: This parameter is mandatory. LANMAR-DRIFTER-MAX-AGE Maximum age for drifter entries. Example: LANMAR-DRIFTER-MAX-AGE 4S Note: This parameter is mandatory. LANMAR-FISHEYE-SCOPE Fisheye scope. Default is 2. Example: LANMAR-FISHEYE-SCOPE 2 QualNet 4.0 Wireless Model Library 133

134 Wireless Model Library TABLE 40. LANMAR Parameters (Continued) LANMAR-FISHEYE-UPDATE-INTERVAL LANMAR-FISHEYE-MAX-AGE Routing table update frequency within the fisheye scope. Example: LANMAR-FISHEYE-UPDATE-INTERVAL 5S Note: This parameter is mandatory. Maximum age for fisheye entries. Example: LANMAR-FISHEYE-MAX-AGE 4S Note: This parameter is mandatory. Statistics TABLE 41. LANMAR Statistics Statistic The number of intra-scope updates The number of landmark updates Control overhead in bytes Number of control packets Drop within the scope Drop due to no landmark matching Drop due to no drifter matching Packet dropped Explanation Number of intra update packets sent Number of landmark update packets sent Total control packets sent in bytes Total number of control packets sent Number of data packets dropped where the destination is in the same landmark group, but no route found in intra routing table. Number of data packets dropped where the destination address has no matching landmark can be found. Number of data packets dropped where the destination is recognized as a drifter node, but distance is unreachable. Number of data packets dropped where no any route can be found to the destination. 134 QualNet 4.0 Wireless ModelLibrary

135 LAR1 LAR1 Location-Aided Routing (LAR) is an on-demand routing protocol that exploits location information. It is similar to DSR, but with the additional requirement of GPS information. In scheme 1 (implemented), the source defines a circular area in which the destination may be located, determined by the following information: The destination location known to the source The time instant when the destination was located at that position The average moving speed of the destination. The smallest rectangular area that includes this circle and the source is the request zone. This information is attached to a ROUTE REQUEST by the source and only nodes inside the request zone propagate the packet. If no ROUTE REPLY is received within the timeout period, the source retransmits a ROUTE REQUEST via pure flooding. Configuration To select LAR1 as the routing protocol, place the following entry in *.config: ROUTING-PROTOCOL LAR1 Note: LAR1 does not accept any parameters. To configure LAR in QualNet GUI, complete the following steps: 1. Select the Inspector tab. 2. Go to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy. 3. Select Dynamic. 4. Select Routing Protocol properties as LAR1 from the list. Statistics Table 42 lists the statistics collected by LAR1. TABLE 42. LAR1 Statistics Collected Statistic Data Packets Sent As Data Source Data Packets Relayed Route Requests Sent As Data Source Route Replies Sent as Data Receiver Route Error Packets Sent As Source of Error Explanation The number of data packets sent as source of the data by the node. The number of data packets relayed by the node. The number of route requests sent by a node when it was it was source of the data to send. The number of route replies sent by a node when it was a destination. The number of route error packets sent by the node when it was the source of the error. QualNet 4.0 Wireless Model Library 135

136 Wireless Model Library TABLE 42. LAR1 Statistics Collected Route Requests Relayed as Intermediate Node Route Replies Relayed as Intermediate Node Route Error Packets Relayed as Intermediate Node Number of route request packets relayed by the node when it was an intermediate hop between the source and the destination. Number of route reply packets relayed by the node when it was an intermediate hop between the source and the destination. Number of route error packets relayed by the node when it was an intermediate hop between the source and the destination. 136 QualNet 4.0 Wireless ModelLibrary

137 MACA MACA MACA (Multiple Access Collision Avoidance) is a wireless MAC protocol that uses an RTS/CTS dialog to solve the hidden terminal problem. It does not use carrier sensing. MACA can also easily be extended so that it provides automatic transmitter power control. Doing this can substantially increase the channel capacity. It can be specified with the following parameter: MAC-PROTOCOL MACA Note: There are no further variables. Statistics TABLE 43. MACA Statistics Packets from network Packets lost due to buffer overflow UNICAST packets sent to channel BROADCAST packets sent to channel UNICAST packets received clearly BROADCAST packets received clearly RTS Packets sent CTS Packets sent RTS Packets received CTS Packets received Noisy Packets received Number of data packets passed from upper layer. Number of data packets dropped due to buffer overflow. Number of unicast packets sent to the channel. Number of broadcast packets sent to the channel. Number of unicast packets received successfully. Number of broadcast packets received successfully. Number of RTS control packets sent. Number of CTS control packets sent. Number of RTS control packets received. Number of CTS control packets received. Number of packets overhead with destination address is not the node. QualNet 4.0 Wireless Model Library 137

138 Wireless Model Library ODMRP The On-Demand Multicast Routing Protocol (ODMRP) is a wireless multicast routing protocol. It is designed for single subnet, wireless ad-hoc multicast routing, and operates similarly to an on-demand wireless unicast routing protocol. ODMRP is a mesh-based, rather than a conventional tree-based, multicast scheme and uses a forwarding group concept (only a subset of nodes forwards the multicast packets via scoped flooding). It applies on-demand procedures to dynamically build routes and uses soft state to maintain multicast group membership. Configuration To select ODMRP as the multicast routing protocol in *.config, place the following two entries in *.config: MULTICAST-PROTOCOL ODMRP MULTICAST-GROUP-FILE./default.member Optional Parameters Table 44 shows the ODMRP related parameters that are specified in the *.config file: TABLE 44. ODMRP Parameters Parameter ODMRP-JR-REFRESH ODMRP-FG-TIMEOUT ODMRP-DEFAULT-TTL ODMRP-PASSIVE-CLUSTERING ODMRP-CLUSTER-TIMEOUT Explanation The time for periodic Join Query Message Transmission. With the propagation of Join Query, Route is being refreshed. So it can be called Route Refresh Interval. Note: The default value of 20S is used. The Forwarding Group Timeout Interval. After expiring this value a node supporting ODMRP will not forward Data Packet. The value must be 3 to 5 times larger than Route Refresh Interval. Note: The default value of 60S is used. ODMRP-DEFAULT-TTL specifies the TTL value for ODMRP routing control packets. Note: the default value of 64 is used. ODMRP-PASSIVE-CLUSTERING specifies whether or not to use passive clustering with ODMRP. Options are YES and NO. Note: the default value of NO is used. ODMRP-CLUSTER-TIMEOUT specifies the timeout for maintaining clusters. This option is used only when passive-clustering is enabled. Note: the default value of 10S is used. Note: For highly mobile nodes, small Route Refresh Interval value should be chosen. For a stable network, large values provide better network performance. 138 QualNet 4.0 Wireless ModelLibrary

139 ODMRP Statistics Table 45 lists the statistics collected by ODMRP. TABLE 45. ODMRP Statistics Collected Statistics Join queries originated Join queries transmitted Join replies sent Join replies forwarded Join replies transmitted Number of ACK packets sent Number of data packets relayed Number of data packets sent as source Number of data packets received Total Give Up messages sent Total Give Up messages received Explanation Number of Join Queries originated. Number of Join Query (with piggybacked stat) packets transmitted. Number of Join Reply packets sent. Number of Join Replies forwarded. Number of Join Replies retransmitted. Number of ACK packets sent. Total Number of ODMRP data packets relayed. Number of data packets sent as the source of the data. Number of data packets received as the destination of the data. Total number of Give Up messages transmitted. Only printed when passive clustering is enabled. Total number of Give Up messages received. Only printed when passive clustering is enabled. QualNet 4.0 Wireless Model Library 139

140 Wireless Model Library OLSR INRIA The Optimized Link State Routing (OLSR) protocol, developed by the French National Institute for Research in Computer Science and Control (INRIA), was developed for mobile ad-hoc networks. It operates in a table-driven and proactive manner, i.e., topology information is exchanged between the nodes on periodic basis. Its main objective is to minimize the control traffic by selecting a small number of nodes, known as Multi Point Relays (MPR) for flooding topological information. In route calculation, these MPR nodes are used to form an optimal route from a given node to any destination in the network. This routing protocol is particularly suited for a large and dense network. OLSR generally proposes four types of periodic control messages, namely: Hello messages Topological Control (TC) messages Multiple Interface Declaration (MID) messages, and Host and Network Association (HNA) messages. Hello messages are periodically exchanged within the one-hop neighborhood to obtain the neighborhood information. Using this neighborhood information, each node in the network selects a subset of one-hop away neighbors known as the MPR set. In the MPR set, all two-hop away neighbors are reachable through any member of the MPR set. TC messages are generated and retransmitted for flooding topological information in the whole network only through MPR nodes. Also, MID and HNA messages are relayed only by MPR nodes. Therefore, OLSR optimizes the control traffic overhead by minimizing the size of the MPR set. An MPR member generates and retransmits TC messages. These messages provide each node in the network with sufficient link-state information to allow route calculation. MID messages are generated by an OLSR node with multiple-olsr interfaces to notify other OLSRnodes about its interfaces participating in the OLSR routing domain. Apart from these OLSR control messages, a node associated with OLSR-MANET and Non-OLSR-MANET periodically issues HNA messages notifying the connected Non-OLSR-Networks. These HNA messages are also flooded throughout the OLSR domain by the MPR nodes so that the external routes are learned by all the OLSR nodes. Configuration The OLSR routing protocol can be configured in the Simulator and in the GUI/Animator. Configuration Using the Simulator Just like other standard routing protocol configuration inside QualNet, OLSR-INRIA can be configured at node level, interface level, subnet level, and global level. The configuration details are as follows: Specification of OLSR-INRIA as routing protocol ROUTING-PROTOCOL <ROUTING-PROTOCOL> [<node-id> <Subnet/network> <interface-address>] ROUTING-PROTOCOL OLSR-INRIA For example: 140 QualNet 4.0 Wireless ModelLibrary

141 OLSR INRIA # Node Level Specification [6] ROUTING-PROTOCOL OLSR-INRIA # Subnet Level Specification [N ] ROUTING-PROTOCOL OLSR-INRIA # Interface Level Specification [ ] ROUTING-PROTOCOL OLSR-INRIA # Global Specification ROUTING-PROTOCOL OLSR-INRIA OLSR can run either in IPv4 or in IPv6 mode. The IP-version for OLSR can be specified as shown below. Note: By default, the OLSR IP version is IPv4. [<node-id> <interface-address>] OLSR-IP-VERSION For example: For IPv4, [6] OLSR-IP-VERSION IPv4 <IPv6/IPv4> For IPv6, [6] OLSR-IP-VERSION IPv6 User-configurable OLSR control messages are configured as follows: OLSR periodically broadcasts hello messages within a one-hop neighborhood to obtain the neighborhood information. From this neighborhood information, each node in the network selects a subset of one-hop away neighbors, known as MPR (Multi Point Relay) set, such that all the two-hop away neighbors are reachable through any one of these MPR members. Note: The default interval for issuing hello messages is 2 seconds. [<node-id> <interface-address>] OLSR-HELLO-INTERVAL <time-interval> For example: OLSR-HELLO-INTERVAL 2S Only MPR nodes broadcast and relay Topology Control (TC) messages. It contains a list of neighbor which selected the TC generating node as MPR. Note: The default interval for issuing TC messages is 5 seconds. [<node-id> <interface-address>] OLSR-TC-INTERVAL <time-interval> For example: OLSR-TC-INTERVAL 5S Multiple Interface Description (MID) messages are periodically issued only by an OLSR node with multiple OLSR-interfaces. Note: The default interval for issuing MID messages is 5 seconds. [<node-id> <interface-address>] OLSR-MID-INTERVAL <time-interval> For example: QualNet 4.0 Wireless Model Library 141

142 Wireless Model Library OLSR-MID-INTERVAL 5S Apart from these OLSR control messages, a node associated with OLSR-MANET and Non-OLSR- MANET periodically issue HNA messages notifying the connected Non-OLSR-Networks. These HNA messages are also flooded throughout the OLSR domain by the MPR nodes so that the external routes are learnt by all the OLSR nodes. Note: The default interval for issuing HNA messages is 5 seconds. [<node-id> <interface-address>] OLSR-HNA-INTERVAL <time-interval> For example: OLSR-HNA-INTERVAL 5S OLSR times out an entry in its table, if the entry does not refresh within a stipulated time. QualNet also allows specification of such time-out duration for various OLSR-INRIA Information repositories. OLSR maintains its neighborhood information in the neighbor-table. Note: The default time out period for the neighbor table is 12 seconds. [<node-id> <interface-address>] OLSR-NEIGHBOR-HOLD-TIME <time-interval> For example: OLSR-NEIGHBOR-HOLD-TIME 12S OLSR holds topological information in the topology-table. The topology table stores the address of a MPR node as the last hop node along with its one-hop away MPR selector nodes which are directly reachable through the MPR node. Note: The default time out period for the topology table is 15 seconds. [<node-id> <interface-address>] OLSR-TOPOLOGY-HOLD-TIME <time-interval> For example: OLSR-TOPOLOGY-HOLD-TIME 15S An OLSR node maintains a duplicate table where it records information about the most recently received messages to avoid duplicate processing of an already received and processed message. Note: The default time out period for the duplicate table is 15 seconds. [<node-id> <interface-address>] OLSR-DUPLICATE-HOLD-TIME <time-interval> For example: OLSR-DUPLICATE-HOLD-TIME 15S An OLSR node also maintains a table called, MID table that contains information about the OLSR interfaces of a participating OLSR-node having multiple interfaces connected to OLSR-MANET domain. Note: The default time out period for the MID table is 15 seconds. [<node-id> <interface-address>] OLSR-MID-HOLD-TIME <time-interval> For example: OLSR-MID-HOLD-TIME 15S OLSR nodes maintain HNA tables to store information about gateways inside OLSR-domain to get to the associated Non-OLSR MANET domain. 142 QualNet 4.0 Wireless ModelLibrary

143 OLSR INRIA Note: The default time out period for the HNA table is 15 seconds. [<node-id> <interface-address>] OLSR-HNA-HOLD-TIME For example: OLSR-HNA-HOLD-TIME 15S <time-interval> Configuration Using the GUI/Animator The following steps show how to configure the OLSR-INRIA routing protocol in Animator: 1. Using the Inspector window, navigate to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy -> Routing Protocol. Select routing OLSR-INRIA as routing protocol using the Configurable Property window. 2. Using the Inspector window, navigate to ConfigSettings -> Network Protocols -> Routing Protocol -> Routing Policy -> Routing Protocol. Set the OLSR IP Version as IPv4 or IPv6 using the Detailed Property window. 3. To configure OLSR-INRIA parameters, navigate to ConfigSettings -> Network Protocols -> Routing Protoco l-> Routing Policy -> Routing Protocol. Using the Detailed Properties window set the following parameters with the desired values: Hello Interval TC Interval MID Interval HNA Interval Neighbor Table Time-out Topology Table Time-out Duplicate Table Time-out MID Table Time-out HNA Table Time-out Examples This section contains sample scenarios for both IPv4 and IPv6. Sample Scenario for IPv4 This sample IPv4 scenario tests the following OLSR-INRIA features: MPR MPRselector HNA MID QualNet 4.0 Wireless Model Library 143

144 Wireless Model Library [1] [6] [Wireless-Subnet] [Wireless-Subnet] [3] [4] [5] \ / \ / +--- [Wireless-Subnet] ---+ [2]--- [HUB] [HUB] --- [7] FIGURE 74. IPv4 Sample Scenario As shown in Figure 74: Nodes 1 and 3 are connected with 1 st wireless subnet. Nodes 3, 4, and 5 are connected with 2 nd wireless subnet. Nodes 5 and 6 are connected with the 3 rd wireless subnet. Nodes 2 and 3 and Nodes 5 and 7 are connected using a HUB. The wireless networks are running OLSR as the routing protocol. Nodes 2 and 3 and Nodes 5 and 7 are running RIP as the routing protocol. This, in turn means that both nodes 3 and 5 are having multiple interfaces along with Non-OLSR configured interfaces. CBR Applications are configured between Nodes 1 & 6, Nodes 5 & 1 and 4 & 2. Simulator Configuration SIMULATION-TIME 5M #At Subnet level: The routing protocols are configured as below: [N ] NETWORK-PROTOCOL IP [N ] ROUTING-PROTOCOL OLSR-INRIA [N ] NETWORK-PROTOCOL IP [N ] ROUTING-PROTOCOL OLSR-INRIA [N ] NETWORK-PROTOCOL IP [N ] ROUTING-PROTOCOL OLSR-INRIA #At Node level: The routing protocols are configured as below: 144 QualNet 4.0 Wireless ModelLibrary

145 OLSR INRIA [ ] ROUTING-PROTOCOL OLSR-INRIA [ ] OLSR-IP-VERSION IPv4 [ 2 7 ] ROUTING-PROTOCOL RIP #At Interface level: The routing protocols are configured as below: [ ] ROUTING-PROTOCOL OLSR-INRIA [ ] OLSR-IP-VERSION IPv4 [ ] ROUTING-PROTOCOL RIP All other OLSR configurable parameters that are not configured in the above example scenario use default values. Animator Configuration 1. Create a new scenario using the Scenario designer. Using the Inspector window, navigate to ConfigSettings -> General -> General. a. Configure the Experiment name and Simulation time using the Configurable Property window to any desired name and value. b. Select the Devices tab of ScenarioDesigner window. c. Select Default icon and place the nodes. d. Select the Network components tab of ScenarioDesigner window. e. Select Wireless subnet and connect the nodes. f. Similarly, select Hub and connect the nodes accordingly. 2. To configure at subnet level: Using the Inspector window, navigate to Hierarchy -> Nodes -> Wireless Subnet <Network address> -> Wireless subnet Properties -> Routing Protocol. Set routing protocol as OLSR INRIA. QualNet 4.0 Wireless Model Library 145

146 Wireless Model Library FIGURE 75. Setting OLSR-INRIA as the Routing Protocol at the Subnet Level 3. For Node level configuration: Using the Inspector window, navigate to Hierarchy -> Nodes -> host Node Configurations -> Routing Protocol -> Routing Policy -> Routing Protocol. Set routing protocol as Olsr Inria as shown in Figure QualNet 4.0 Wireless ModelLibrary

147 OLSR INRIA FIGURE 76. Setting OLSR-INRIA as the Routing Protocol at the Node Level 4. OLSR-INRIA IP version and other configurable parameters can be configured as follows: Using Inspector window, navigate to Hierarchy -> Nodes -> host -> Node Configurations -> Routing Protocol -> Routing Policy -> Routing Protocol -> Properties Window -> Detailed Properties. Set OLSR IP version as IPv4. Set other configuration parameters to any desired values, as shown in Figure 77. QualNet 4.0 Wireless Model Library 147

148 Wireless Model Library FIGURE 77. Setting OLSR-INRIA Configuration Parameters at the Node Level 5. For Interface level configuration: Using Inspector window, navigate to Hierarchy -> Nodes -> host -> Interfaces -> Interface -> Interface Configurations Routing -> Protocol Routing Policy Routing Protocol. Set routing protocol as Olsr Inria, as shown in Figure QualNet 4.0 Wireless ModelLibrary

149 OLSR INRIA FIGURE 78. Setting OLSR-INRIA as the Routing Protocol at the Interface Level Sample Scenario IPv6 To test the OLSR-INRIA features using an IPv6 scenario in ad-hoc mode. [1] [2] [3] [4] [5] FIGURE 79. Sample Scenario IPv6 QualNet 4.0 Wireless Model Library 149

150 Wireless Model Library As shown in Figure 79: Nodes 1 through 5 are placed in an ad-hoc multi-hop subnet. All the nodes are running OLSR-INRIA as routing protocol. The network is configured to be IPv6. CBR Applications are configured between Nodes 1 and 4 and Nodes 2 and 5. Simulator Configuration # The scenario is executed for a simulation time of 5minutes. SIMULATION-TIME 5M # 5 nodes are placed in an ad-hoc multi-hop wireless subnet SUBNET SLA-1 { 1 thru 5 } Default #At Global level: The OLSR-INRIA as routing protocol is configured as below: ROUTING-PROTOCOL OLSR-INRIA #At Global level: The OLSR-INRIA configuration parameters are configured as below: OLSR-IP-VERSION OLSR-HELLO-INTERVAL OLSR-TC-INTERVAL OLSR-MID-INTERVAL OLSR-HNA-INTERVAL OLSR-NEIGHBOR-HOLD-TIME OLSR-TOPOLOGY-HOLD-TIME OLSR-DUPLICATE-HOLD-TIME OLSR-MID-HOLD-TIME OLSR-HNA-HOLD-TIME NETWORK-PROTOCOL MAC-PROTOCOL IPv6 2S 5S 5S 5S 12S 15S 15S 15S 15S IPv6 MAC Animator Configuration 1. Create a new scenario using the Scenario designer. Using Inspector window, navigate to ConfigSettings -> General -> General. a. Configure the Experiment name and Simulation time using the Configurable Property window to any desired name and values. b. Select the Devices tab of ScenarioDesigner window. c. Select Default icon and place the nodes. 2. Using the Inspector window: navigate to ConfigSettings -> Network Protocol -> Routing Protocol - > Routing Policy -> Routing Protocol. Set routing protocol as Olsr Inria in the Configurable Property window, as shown in Figure QualNet 4.0 Wireless ModelLibrary

151 OLSR INRIA FIGURE 80. Setting Olsr-Inria as the Routing Protocol 3. Using the Inspector window: navigate to ConfigSettings -> Network Protocol -> Routing Protocol -> Routing Policy -> Routing Protocol. Set OLSR IP Version to be IPv6 using the Detailed Properties window, as shown in Figure 81. QualNet 4.0 Wireless Model Library 151

152 Wireless Model Library FIGURE 81. Setting IPv6 as the OLSR-INRIA IP Version 4. Using Inspector window: navigate to ConfigSettings -> Network Protocol -> Network Protocol. Set Network Protocol as IPv6 using the Configurable Property window, as shown in Figure QualNet 4.0 Wireless ModelLibrary

153 OLSR INRIA FIGURE 82. Configuring the IPv6 Network 5. Using Inspector window: navigate to ConfigSettings -> Wireless Settings -> MAC Protocol -> MAC Protocol. Set MAC protocol as Legacy model in the Configurable Property window, as shown in Figure 83. QualNet 4.0 Wireless Model Library 153

154 Wireless Model Library FIGURE 83. Setting MAC Protocol as Legacy model 6. Now, select the Applications tab of ScenarioDesigner window. a. Select CBR and set the application between Node 1 and Node 4. Do the same between Node 2 and Node 5. b. Now set the Application Parameters using the Configurable Property window to any desired values. 7. Make the changes by clicking on the Save button. Click on the Run button. Now, Click on the Play button to execute the scenario. 154 QualNet 4.0 Wireless ModelLibrary

155 OLSRv2 OLSRv2 OLSRv2 is developed for mobile ad hoc networks. It operates as a table driven, proactive protocol, i.e. it exchanges topology information with other nodes of the network regularly. Each node selects a set of its neighbor nodes as "Multi Point Relay" (MPR). Only nodes that are selected as such MPR are then responsible for forwarding control traffic intended for diffusion into the entire network. MPR provide an efficient mechanism for flooding control traffic by reducing the number of transmissions required. A node selects MPR from among its one hop neighbors with "symmetric", i.e. bi-directional, linkages. Therefore, selecting routes through MPRs automatically avoids the problems associated with data packet transfer over unit-directional links (such as the problem of not getting link-layer acknowledgments for data packets at each hop, for link-layers employing this technique for unicast traffic). OLSRv2 is developed to work independently from other protocols. Likewise, OLSRv2 makes no assumptions about the underlying link-layer. However, OLSRv2 may use link-layer information and notifications when available and applicable. It uses mainly two basic types of control packets as stated below Hello: The OLSRv2 neighborhood discovery protocol using HELLO messages. This neighborhood discovery protocol serves to ensure that each OLSRv2 node has available continuously updated information repositories describing the node's 1-hop and 2-hop neighbors. Neighborhood discovery protocol using HELLO messages uses generic multi-message packet format, for carrying MANET routing protocol signals. TC:TC messages(topology Control messages) in OLSRv2 serve to: inject link-state information into the entire network; inject addresses of hosts and networks for which they may serve as a gateway into the entire network. TC messages are emitted periodically, thereby allowing nodes to continuously track global changes in the network. The purpose of OLSRv2 is to determine the Routing Set, which may be used to update IP's Routing Table, providing "next hop" routing information for IP datagrams. In order to accomplish this, OLSRv2 uses a number of protocol sets: Neighborhood Information Base: The neighborhood information base stores information about links between local interfaces and interfaces on adjacent nodes. Topology Information Base: The Topology Information Base stores information, required for the generation and processing of TC messages. Configuration and Parameters OLSRv2-NIIGATA Configurations using Simulator Just like the other standard routing protocol configuration inside QualNet, OLSRv2-NIIGATA as well as it's all other parameters can be configured at node level, interface level, subnet level and global level. The configuration details are as below: QualNet 4.0 Wireless Model Library 155

156 Wireless Model Library Specification of OLSRv2-NIIGATA as routing protocol ROUTING-PROTOCOL <ROUTING-PROTOCOL> OLSRv2-NIIGATA can be configured on Node, Subnet/Network, Interface basis and globally using the following syntax. Syntax: [<node-id> <Subnet/network> <interface-address>] ROUTING-PROTOCOL OLSRv2- NIIGATA For example: # Node Level Specification [6] ROUTING-PROTOCOL OLSRv2-NIIGATA # Subnet Level Specification [N ] ROUTING-PROTOCOL OLSRv2-NIIGATA # Interface Level Specification [ ] ROUTING-PROTOCOL OLSRv2-NIIGATA # Global Specification ROUTING-PROTOCOL OLSRv2-NIIGATA User configurable OLSRv2 control messages are configured as below: a. OLSRv2 periodically broadcasts hello messages within one-hop neighborhood to obtain the neighborhood information. The default value of OLSRv2-HELLO-INTERVAL is 2 seconds. [<node-id> <interface-address>] OLSRv2-HELLO-INTERVAL <time-interval> For example: OLSRv2-HELLO-INTERVAL 2S b. OLSRv2 TC messages are generated and transmitted periodically, with a default interval between two consecutive TC emissions by the same node. That interval can be set by the OLSRv2-TC- INTERVAL configuration parameter. The default value of OLSRv2-TC-INTERVAL is 5 seconds. [<node-id> <interface-address>] OLSRv2-TC-INTERVAL <time-interval> For example: OLSRv2-TC-INTERVAL 5S c. This parameter concerns with the occurrence of the timeout event for the validation of tuples in various information repositories of OLSRv2-NIIGATA. The default value of OLSRv2-TIMEOUT-INTERVAL is 2 seconds. [<node-id> <interface-address>] OLSRv2-TIMEOUT-INTERVAL <time-interval> For example: OLSRv2-TIMEOUT-INTERVAL 2S d. This parameter configures the start time of the HELLO packet periodical emission by the nodes. The default value of OLSRv2-START-HELLO is 1 seconds. [<node-id> <interface-address>] OLSRv2-START-HELLO <time-interval> For example: OLSRv2-START-HELLO 1S e. This parameter configures the start time of the TC packet periodical emission by the nodes. The default value of OLSRv2-START-TC is 1 seconds. [<node-id> <interface-address>] OLSRv2-START-TC <time-interval> For example: OLSRv2-START-TC 1S 156 QualNet 4.0 Wireless ModelLibrary

157 OLSRv2 f. This parameter configures the start time for the occurrence of OLSRv2-TIMEOUT-INTERVAL event for the olsrv2 information repositories. The default value of OLSRv2-START-TIMEOUT is 1 seconds. [<node-id> <interface-address>] OLSRv2-START-TIMEOUT <time-interval> For example: OLSRv2-START-TIMEOUT 1S g. This parameter configures the settings for the notification of link disconnection from MAC layer. The default value of OLSRv2-LINK-LAYER-NOTIFICATION is NO. [<node-id> <interface-address>] OLSRv2-LINK-LAYER-NOTIFICATION <YES/NO> For example: OLSRv2-LINK-LAYER-NOTIFICATION h. This parameter configures the packet restoration feature on the event of Link Layer Notification, occurred because of any link disconnection. The default value of OLSRv2-PACKET-RESTORATION is NO. [<node-id> <interface-address>] OLSRv2-PACKET-RESTORATION <YES/NO> For example: OLSRv2-PACKET-RESTORATION NO NO OLSRv2-NIIGATA Configurations using GUI / Animator Following are the steps to configure the OLSRv2-NIIGATA routing protocol in Animator: 1. Inside Inspector window, go to ConfigSettings ' Network Protocols ' Routing Protocol ' Routing Policy ' Routing Protocol. Select routing protocol to OLSRv2-NIIGATA using the Configurable Property Window as shown in Figure 84. QualNet 4.0 Wireless Model Library 157

158 Wireless Model Library FIGURE 84. Setting OLSRv2-NIIGATA as Routing Protocol 2. To configure OLSRv2 parameters, go to ConfigSettings ' Network Protocols ' Routing Protocol ' Routing Policy ' Routing Protocol, using the Configurable Properties Window set the following parameters as shown in Figure 85: OLSRv2-HELLO-INTERVAL OLSRv2-TC-INTERVAL OLSRv2-TIMEOUT-INTERVAL OLSRv2-START-HELLO OLSRv2-START-TC OLSRv2-START-TIMEOUT OLSRv2-LINK-LAYER-NOTIFICATION OLSRv2-PACKET-RESTORATION 158 QualNet 4.0 Wireless ModelLibrary

159 OLSRv2 FIGURE 85. Setting OLSRv2-NIIGATA Configurable Parameters 3. Using Inspector window, navigate to ConfigSettings ' Network Protocols 'Network Protocol' Network Protocol. Set the Network Protocol as IPv4 or IPv6 using the Configurable Property window as shown in Figure 86. QualNet 4.0 Wireless Model Library 159

160 Wireless Model Library FIGURE 86. Setting IP Version for OLSRv2-NIIGATA as IPv4 (left), and as IPv6 (right) 4. For Node level configuration: Using Inspector window, navigate to Hierarchy' Nodes' host[id]' Node Configurations' Routing Protocol ' Routing Policy' Routing Protocol. Set routing protocol as shown in Figure QualNet 4.0 Wireless ModelLibrary

161 OLSRv2 FIGURE 87. Setting OLSRv2-NIIGATA as Routing Protocol at Node Level 5. OLSRv2 parameters can be configured at Node Level as follows: Go to Hierarchy' Nodes' host[id] ' Node Configurations' Routing Protocol 'Routing Policy' Routing Protocol' Properties Window' Configurable Properties. Set OLSRv2-NIIGATA configurable parameters through this window as shown in Figure 88. QualNet 4.0 Wireless Model Library 161

162 Wireless Model Library FIGURE 88. Setting OLSRv2-NIIGATA Configuration Parameters at Node Level 6. For Interface level configuration: Go to Hierarchy' Nodes' host [id]' Interfaces' Interface [id]' Interface Configurations' Routing Protocol' Routing Policy' Routing Protocol. Set Routing protocol as shown in Figure QualNet 4.0 Wireless ModelLibrary

163 OLSRv2 FIGURE 89. Setting OLSRv2-NIIGATA as Routing Protocol at Interface Level 7. OLSRv2 parameters can be configured at Interface Level as follows: Go to Hierarchy' Nodes' host [id] ' Interfaces' Interface [id]' Interface configurations' Routing Protocol 'Routing Policy' Routing Protocol' Properties Window' Configurable Properties. Set OLSRv2-NIIGATA configurable parameters window as shown in Figure 90. QualNet 4.0 Wireless Model Library 163

164 Wireless Model Library FIGURE 90. Setting OLSRv2-NIIGATA Configuration Parameters at Interface Level 8. To set the Network Protocol as IPv4 or IPv6, at Node Level: Go to Hierarchy' Nodes' host[id] ' Node Configurations' Network Protocol ' Network Protocol Set the Network Protocol using the Configurable Property as shown in Figure QualNet 4.0 Wireless ModelLibrary

165 OLSRv2 FIGURE 91. Setting IP Version for OLSRv2-NIIGATA at Node Level 9. To set the Network Protocol as IPv4 or IPv6, on Interface Level: Go to Hierarchy' Nodes' host[id] ' Interfaces' Interface[id]' Interface Configurations' Network Protocol ' Network Protocol Set the Network Protocol using the Configurable Property as shown in Figure 92. QualNet 4.0 Wireless Model Library 165

166 Wireless Model Library FIGURE 92. Setting IP Version for OLSRv2-NIIGATA at Interface Level 10. To set Routing Protocol as OLSRv2-NIIGATA, at Subnet Level: Go to Hierarchy' Nodes' Wireless Subnet' Wireless Subnet Properties' Routing Protocol Set the Routing Protocol using the Configurable Property as shown in Figure QualNet 4.0 Wireless ModelLibrary

167 OLSRv2 FIGURE 93. Setting OLSRv2-NIIGATA as Routing Protocol at Subnet Level 11. To set the Network Protocol as IPv4 or IPv6, at Subnet Level: Go to Hierarchy' Nodes' Wireless Subnet' Wireless Subnet Properties' Network Protocol. Set the Network Protocol using the Configurable Property. Example Scenario Sample-scenario-ipv4 Test the OLSRv2-NIIGATA functionality using an IPv4 scenario as shown in Figure 94: [1] [2] [3] FIGURE 94. Testing OLSRv2-NIIGATA with IPv4 Nodes 1, 2 and 3 are in Ad-hoc mode. In this scenario the routing protocol is OLSRv2-NIIGATA. QualNet 4.0 Wireless Model Library 167

168 Wireless Model Library One CBR application is configured from Node 1 to Node 3. Configuring the Simulator In *.config file, the following parameters have to be specified: # The scenario is executed for a simulation time of 5minutes. SIMULATION-TIME 5M # 3 nodes are placed in an ad-hoc multi-hop wireless subnet SUBNET N { 1 thru 3 } Default #At Global level: OLSRv2-NIIGATA is configured as routing protocol as below: [ ] ROUTING-PROTOCOL OLSRv2-NIIGATA NETWORK-PROTOCOL IP All other OLSRv2-NIIGATA configurable parameters that are not configured in the above example scenario use default values. Node 1 is sending 500 packets to Node 3. Configuring the GUI/Animator 1. Create a new scenario using the Scenario Designer. a. Navigate to ConfigSettings General General Experiment Name b. Configure the Simulation time and Experiment name using the Configurable Property Window. c. Select the Devices tab of Scenario Designer window. d. Select Default icon and place the nodes as shown in the below Fig QualNet 4.0 Wireless ModelLibrary

169 OLSRv2 FIGURE 95. Scenario Created through GUI 2. Inside Inspector window, go to ConfigSettings ' Network Protocols ' Routing Protocol ' Routing Policy ' Routing Protocol. Select OLSRv2-NIIGATA as routing protocol using the Configurable Property Window as shown in Figure 96. QualNet 4.0 Wireless Model Library 169

170 Wireless Model Library FIGURE 96. Setting OLSRv2-NIIGATA as Routing Protocol 3. To configure OLSRv2 parameters, go to ConfigSettings ' Network Protocols ' Routing Protocol ' Routing Policy ' Routing Protocol, using the Configurable Properties Window set the following parameters as shown in Figure QualNet 4.0 Wireless ModelLibrary

171 OLSRv2 FIGURE 97. Setting OLSRv2-NIIGATA Configurable Parameters 4. Select the "Applications" tab of ScenarioDesigner window. a. Select CBR and set the application between Node 1 and Node 3. b. Now set the Application Parameters using the Configurable Property Window. This is done as shown in Figure 98: QualNet 4.0 Wireless Model Library 171