N.2.2 Deriving medium time AP use the following procedure to derive medium time in its ADDTS Response frame. There are two to consider: 1) the traffic requirements of the application, and 2) the expected error performance of the medium. The application requirements are captured by the following TSPEC parameters: Nominal MSDU Size and Mean Data Rate. The medium requirements are captured by the following parameters: Surplus Bandwidth Allowance, Minimum PHY Rate and, for aggregation, Nominal MSDU Aggregation. The following formula describes how Medium Time, in units of 32 periods per second, may be μs calculated: At 3035.63, pecified if Minimum Data Rate is specified” (2 occurrances) “Opt At 3036.24, ACM subfield for these categories set to 0.” “The At 3036. 31 parameters chosen by the AP further account for any unadmitted traffic” “AC At 3043. 38, scheduler consider these retransmissions” “the At 3044.64, values for as shown in Table N-2 (SBA vs Packets/s) are based upon a one second time “The SBA period and hence are used in the TSEC for EDCA Admission Control. The value used in an HCCA TSPEC be different, as will now be explained. At 3047.8, CBR traffic the minimum and maximum Service Intervals set to the same value. For example, “For most voice traffic requires a minimum and maximum service interval value of 20 ms.” At 3047. 12, the case of VBR traffic, such as video, Minimum Service Interval set to zero” “In At 3048.7, an HCCA for CBR traffic the Minimum, Mean and Maximum Data Rate fields contain the “For same value but it is allowable to just specify the Mean Data Rate noting that the Minimum and Maximum Service Intervals are the same. For an EDCA TSPEC, for CBR traffic the Minimum, Mean and Maximum Data Rate fields contain the same value but it is allowable to just specify the Mean Data Rate.” At 3048. 42, summing streams for EDCA Admission Control, the EDCA Overhead Factor needs to be taken “hen into account” References:
N.2.2 Deriving medium time AP use the following procedure to derive medium time in its ADDTS Response frame. There are two to consider: 1) the traffic requirements of the application, and 2) the expected error performance of the medium. The application requirements are captured by the following TSPEC parameters: Nominal MSDU Size and Mean Data Rate. The medium requirements are captured by the following parameters: Surplus Bandwidth Allowance, Minimum PHY Rate and, for aggregation, Nominal MSDU Aggregation. The following formula describes how Medium Time, in units of 32 μs periods per second, may be calculated: At 3035.63, “Opt pecified if Minimum Data Rate is specified” (2 occurrances) At 3036.24, “The ACM subfield for these categories set to 0.” At 3036. 31 “AC parameters chosen by the AP further account for any unadmitted traffic” At 3043. 38, “the scheduler consider these retransmissions” At 3044.64, “The values for SBA as shown in Table N-2 (SBA vs Packets/s) are based upon a one second time period and hence are used in the TSEC for EDCA Admission Control. The value used in an HCCA TSPEC be different, as will now be explained. At 3047.8, “For CBR traffic the minimum and maximum Service Intervals set to the same value. For example, most voice traffic requires a minimum and maximum service interval value of 20 ms.” At 3047. 12, “In the case of VBR traffic, such as video, Minimum Service Interval set to zero” At 3048.7, “For an HCCA for CBR traffic the Minimum, Mean and Maximum Data Rate fields contain the same value but it is allowable to just specify the Mean Data Rate noting that the Minimum and Maximum Service Intervals are the same. For an EDCA TSPEC, for CBR traffic the Minimum, Mean and Maximum Data Rate fields contain the same value but it is allowable to just specify the Mean Data Rate.” At 3048. 42, “hen summing streams for EDCA Admission Control, the EDCA Overhead Factor needs to be taken into account” References:
11-14-0263-03-000m-more-lb199-gen-comment-resolutions.docx