Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 1 M-QoS Comments Date: 2010-05-17 Authors:

Similar presentations


Presentation on theme: "Doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 1 M-QoS Comments Date: 2010-05-17 Authors:"— Presentation transcript:

1 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 1 M-QoS Comments Date: 2010-05-17 Authors:

2 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 2 Abstract The presentation asks 802.11s group opinion to resolve M- QoS comments.

3 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 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

4 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 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

5 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 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

6 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 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

7 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 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.

8 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 8 Strawpoll 1 May MBSS use only the default EDCA parameters? Yes No

9 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 9 Strawpoll 2 Should mesh STA be capable to indicate the EDCA parameters it uses? Yes No

10 doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 10 References


Download ppt "Doc.: IEEE 802.11-10/xxxxr0 Submission May 2010 Jarkko Kneckt, NokiaSlide 1 M-QoS Comments Date: 2010-05-17 Authors:"

Similar presentations


Ads by Google