1 / 10

M-QoS Comments

M-QoS Comments. Authors:. Date: 2010-05-17. Abstract. The presentation asks 802.11s group opinion to resolve M-QoS comments. EDCA parameters use in MBSS. In current 802.11s draft, only the standard EDCA parameter values are allowed

chase-lee
Télécharger la présentation

M-QoS Comments

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. M-QoS Comments Authors: Date: 2010-05-17 Jarkko Kneckt, Nokia

  2. Abstract The presentation asks 802.11s group opinion to resolve M-QoS comments. Jarkko Kneckt, Nokia

  3. EDCA parameters use in MBSS • In current 802.11s draft, only the standard EDCA parameter values are allowed • Many CIDs, like 3020, 3189, 3191 suggest to be able to use also other than default parameter values • There are arguments for and against using the non-default EDCA parameters • Some arguments are introduced in the following slides Jarkko Kneckt, Nokia

  4. 802.11s EDCA Parameters History • The default EDCA parameters were selected, because the coordination or control of the EDCA parameters range was considered difficult. • The coordination of EDCA parameters is close to congestion control problems and so far the congestion control is considered to be vendor specific solution Jarkko Kneckt, Nokia

  5. EDCA Parameters Trade-off • A mesh STA may influence on the probability to obtain the TXOP when it adjusts EDCA parameters. • If the parameters are wisely set, the extra throughput may be provided to correct devices and congestions may be avoided • If the parameters are set selfishly, the extra throughput may increase network congestions, create priority inversion and inequality among the mesh STAs Jarkko Kneckt, Nokia

  6. Reasons to Enable use of Non-default EDCA Parameters • The Infrastructure BSS has possibility to control EDCA parameters • The mesh BSS should have the same capabilities, i.e. mesh BSS should not be restricted to default parameters • The congestion control schemes need to adjust EDCA parameters • Without EDCA parameters adjustment, the congestion control protocols will not operate Jarkko Kneckt, Nokia

  7. One possible outcome for EDCA parameter handling • One could be that EDCA parameter values are not controlled/coordinated, i.e. devices may use any EDCA parameter values. If devices use other than default EDCA parameters, it would be polite to signal the EDCA parameter values among neighborhood in beacon and probe.response frames. Jarkko Kneckt, Nokia

  8. Strawpoll 1 • May MBSS use only the default EDCA parameters? • Yes • No Jarkko Kneckt, Nokia

  9. Strawpoll 2 • Should mesh STA be capable to indicate the EDCA parameters it uses? • Yes • No Jarkko Kneckt, Nokia

  10. References Jarkko Kneckt, Nokia

More Related