Month Year Month Year doc.: IEEE yy/xxxxr0 doc.: IEEE /0135r0

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /0924r0 July 2015 Sean Coffey, RealtekSlide 1 Straw polls on preferred ways forward in 11ah Date: Authors:
Advertisements

Doc.: IEEE /0723r0 Submission July 2008 Stephen McCann, RokeSlide 1 TGu Motions Date: Authors:
Submission doc.: IEEE /0336r0 March 2016 Xiaofei Wang (InterDigital)Slide 1 Relay Improvement: Regarding CID 9058 & 9075 Date: Authors:
A Proposed Timeline for IEEE ba TG
Directed Multicast Service (DMS)
– Proposed change to Operations Manual – access to members area
January 2009 Closing Report
Fast Access to Network Information
Reconsidering RA-OLSR
TGz Los Angeles Closing Report
Corrections for D2.8 Date: Authors: May 2014 Name
120MHz channelization solution
Avoiding duplicated queries in 11aq
Motions for 2007/09 Date: Authors: September 2007
TGp Closing Report Date: Author: November 2008 Month Year
doc.: IEEE <doc#>
CID#102 - Channel Allocation
TGz Beijing May 2010 Closing Report
Resolution for CID 118 and 664 Date: Authors: Month Year
CR for CID 1105 Date: Authors: January 2019 Month Year
CID 186, 206 and 211 resolution Date: Authors: January 2007
QoS STA function applied to Mesh STA
CID#102 - Channel Allocation for P2P
AP Power Down Notification
Straw polls and Motions on Spec text for and
Straw polls and Motions on Spec text
FD TIG Summary for EHT Date: Authors: November 2018 Name
IEEE Liaison Report for
TGz Los Angeles Closing Report
802.11bd Timeline Date: Authors: January 2019
CID#89-Directed Multicast Service (DMS)
Motions for 2007/05 Date: Authors: May 2007 Month Year
PICS CF items Date: Author: April 2019 May 2015
Channel Allocation March 2008 Authors: Date: Month Year
IEEE Liaison Report for
TGaj Editor Report for CC22
TGaj Editor Report for CC22
TGu Motions Authors: March 2010 Date: March 2010
Discussion concerning MC-OOK and CIDs 212 and 665
Straw Polls and Motions on 256 QAM and BW: Optional-Mandatory Features
Motivation for Vendor Specific Request Element
Straw polls and Motions on Spec text for and
TGu Teleconference Motions
LB97 Coex: Duplicate DSSS
Synchronization related comment resolution
Proposed Normative Text Changes Concerning Interruptive Polling
CID 186, 206 and 211 resolution Date: Authors: January 2007
TGaj Editor Report for LB220
Proposed Resolution to CID2114
September 2008 Closing Report
TGaj Editor Report for LB226
FD TIG Summary for EHT Date: Authors: November 2018 Name
Resolutions of the Remaining Power Management Comments
Straw polls and Motions on Spec text for and
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
802.11s motion Date: Authors: November 2007 Month Year
Proposed Normative Text Changes Concerning Distributed Admissions
MIMO phase in MU-MIMO Beamforming
FD TIG Summary for EHT Date: Authors: November 2018 Name
Alternative Transport for Event and Diagnostic Reporting
Proposed Normative Text Changes Concerning Poll Responses
Timing Measurement Date: Authors: Jan 2010 November 2007
Discussion concerning MC-OOK and CIDs 212 and 665
TGaj editor report for Sponsor Ballot
TG ax DSC derived CCAeff and OBSS_PD
On the Need for an ai Annex
Coex Ad Hoc January London Agenda and Report
Clause Comment# 775,778,1558,1559 Resolutions
Editorial changes to approved resolutions
TGaj editor report for Sponsor Ballot
Presentation transcript:

Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-08/0135r0 January 2008 Co-located interference – comment resolution options to CIDs 591, 1277, 1745, 1746 and 1748 Date: 2008-01-15 Authors: Slide 1 Page 1 Jari Jokela John Doe, Some Company

Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-08/0135r0 January 2008 Abstract This presentation introduces some potential resolutions to CIDs 591, 1277, 1745, 1746 and 1748. Slide 2 Page 2 Jari Jokela John Doe, Some Company

January 2008 Comments

January 2008 Options Option 1: Continue with the current draft specification text and try to make some editorial changes to make it less vague. Option 2: Enable requesting STA to set the interference level threshold Option 3: Enable requesting STA to set the interference level threshold but enable reporting STA to use different threshold and report it back to the requesting STA

January 2008 Options

January 2008 Some observations Option 1: Simple but may be still too vague to satisfy commenters Option 2: Makes the reporting conditions more explicit. However the requesting STA may not have any glue of correct threshold which may result to unnecessary or missing reports => feature becomes useless. Option 3: Most complex. May not remove the concerns expressed in the comments.

January 2008 Straw Polls What is the prefferred option (please select only single option)? Straw Poll 1: Option 1 presented in 08/0135r0 is the best option YES: NO: Straw Poll 1: Option 2 presented in 08/0135r0 is the best option Straw Poll 1: Option 3 presented in 08/0135r0 is the best option