Configuring SMART MAC
Obtaining Contention Table Values
To obtain the contention table values, you can:
- Use theoretical/expected throughput values
- Use values from the emulated MAC model
The remainder of this section describes how to obtain contention table values when the actual MAC model being emulated with SMART MAC is available.
If the actual MAC model that will be emulated using SMART MAC is available, create a set of learning networks with it. The purpose of each learning network (scenario) is to obtain the network throughput value that corresponds to a given number of contenders. Each scenario will then populate the information for one row in the contention table.
For example, suppose you wanted to use SMART MAC to emulate the Wireless LAN model. You could learn about the contention table values under congestion conditions in a single collision domain network, varying the number of contenders. If the targeted network (actual network that will be simulated using SMART MAC) contains multiple collision domains, which introduce the effects of hidden nodes, then SMART MAC should be configured to activate hidden nodes detection during the simulation. The hidden node effect will be handled by the model independently of the contention table, which was learned with no hidden node effects.
Procedure 108: Obtaining Contention Table Values for a SMART MAC Emulation of Wireless LAN (an example)
-
Create multiple scenarios that use Wireless LAN nodes, increasing the number of nodes in each scenario (from 1 up to the maximum number of contenders the model is expected to handle). Each of these scenarios will represent a row in the table. To represent a case with only one contender, place two nodes in the scenario but enable traffic transmission on only one of the nodes.
-
All nodes in each scenario should be in the same collision domain. In other words, all nodes should be able to reach the others (no hidden nodes in the network).
-
Set traffic characteristics so the network reaches traffic saturation conditions. Every node in the network must be a persistent traffic source. This ensures that the number of the nodes in the network is the actual number of contenders during the entire simulation.
- Make sure that the traffic configuration on each node does not change from one scenario to the other. The only difference in the learning scenarios should be the number of nodes.
- The size of the packets used in the learning scenarios should be as close as possible to the packet size used in the targeted network(s). If a new targeted network is created based on a very different packet size, you should run a new set of learning scenarios using the new packet size.
-
Compute the average throughput and dropping probability using the following Wireless LAN statistics (global):
- Throughput (average)
- Data Dropped (Retry Threshold Exceeded)
- Load
- Data Dropped (Buffer Overflow)

End of Procedure 108
In Procedure 108, the increment in number of nodes from one scenario to the other defines the granularity of the contention table. A finer granularity reduces the error introduced by the fixed throughput values provided in the table. When a specific number of contenders value is not matched exactly by the contention table look up, the next greater number of contenders is used.