1 / 9

MDA Comments 1

MDA Comments 1. Date: 2008-05-05. Authors:. Resolve a number of CIDs on MDA. CIDs: 368, 586, 633, 745, 1386, 1387, 1536, 1805, 1806, 1807, 1815, 1882, 338, 339, 587, 589, 591, 1039, 1308, 1485, 387, 1822, 1847.

aislin
Download Presentation

MDA Comments 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MDA Comments 1 Date: 2008-05-05 Authors: Dee Denteneer, Philips

  2. Resolve a number of CIDs on MDA CIDs: 368, 586, 633, 745, 1386, 1387, 1536, 1805, 1806, 1807, 1815, 1882, 338, 339, 587, 589, 591, 1039, 1308, 1485, 387, 1822, 1847 Normative text: IEEE 802.11-08/1104r0; the excell sheet describing the comment resolution is 1105. Dee Denteneer, Philips

  3. CIDs 368, 586, 633, 745, 1386, 1387, 1536, 1805, 1806, 1807, 1815 • Minor edits of text requested • Some other typos corrected Dee Denteneer, Philips

  4. CID 1882 • "All MDA supporting MPs" - this is imprecise • Relate to MIB variable or OTA signalling As suggested Dee Denteneer, Philips

  5. CID 338, 339 • "MDAOP setup, MP5: M", this is inconsistent with the statement that MDAOP is an optional feature" • Rejected, as “The MDA concept remains optional. However, if implemented MDA has some mandatory parts.” Dee Denteneer, Philips

  6. CID 587, 589, 591, 1039, 1308, 1485 • E.g. 1485: “MDAOP" is not adquately defined. Define it to be the last 4 fields in fig s23, or better, create a new fig and rpeat the field definitions” Dee Denteneer, Philips

  7. CID 587, 589, 591, 1039, 1308, 1485 Remedy: Have introduced a MDAOP field, as suggested, see new Clause 7.3.1.36 Dee Denteneer, Philips

  8. Dee Denteneer, Philips

  9. CIDs: 387, 1822, 1847 “The duration of MDA TXOPs must be determined beforehand, which is not possible.” • Section 9.9.1.2 („EDCA TXOPs“) in 802.11-2007 allows a station to transmit multiple frames within a single TXOP. However, the station shall not exceed its TXOPlimit. Thus, the standard already describes a mechanism that requires a station to calculate the frame transmission duration in advance (that is before transmitting the frame). Furthermore, the standard even requires the station to consider the response frame in its calculation as well. • Additionally, section 9.9.3.1 („Contention-based admission control procedures“) describes a procedure where a station decides in advance whether it may transmit or not. To do so, the station maintains two counters “admitted_time“ and „used_time.“ Based on these counters and the frame transmission duration that the station predicts, it decides whether it may transmit or not. • In summary, 802.11-2007 already describes two different mechanisms that require an STA to calculate the duration of a frame transmission in advance. Therefore, MDA does not require anything particularly new. Dee Denteneer, Philips

More Related