Also, the AP may determine the number of resource units forming the communication channel, based on network statistics on one or more previous transmission opportunities. Again, this is to optimize usage of the network bandwidth given the nodes' needs.
In a first embodiment, the number of resource units, the predetermined maximum small packet size or maximum overhead and the TXOP duration are fixed and known by all the nodes. Step 804 only retrieves these values. For instance, a maximum small packet size is set, typically to 256 bytes; the number of RUs dedicated to small packets is equal to the total number of possible RUs (typically 9 RU per 20 MHz channel) in the composite channel (typically 40 Mhz composite channel will contain 18 RU); and the TXOP duration is set to fit the predefined maximum small packet size given the number of RUs.
In a more complex second embodiment, step 804 uses predefined abacus to obtain a value for those TF characteristics.
For instance, the number of RUs dedicated to small packets may be set according to a predefined abacus (typically linking the number of SP RUs to the number of nodes in the cell depending on the AP type: hot spot, home, enterprise, etc.).
A similar mechanism may be used to determine the maximum small packet size.
Again, the TXOP duration may be set to fit the abacus-based maximum small packet size given the abacus-based number of RUs.
The abacus may be determined using simulation models or real measurement during evaluation tests of the access point implementing the invention.
In a third embodiment, a learning mechanism is used during step 804 to determine the TF characteristics.