CPVs in Mesh formation Date: Authors: September, 2008

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0560r0 Submission May 2009 Allan Thomson, Cisco SystemsSlide 1 Time Features Date: Authors:
Advertisements

Doc.: IEEE /0089r0 Submission Listen interval update Jan 2013 Slide 1 Date: Authors: Jinsoo Choi, LG Electronics.
Doc.: IEEE s Submission January 2011 Dee Denteneer, PhilipsSlide 1 MCCAOP Advertisement discussion Date: Authors:
Doc.: IEEE /2215r4 Submission August 2007 Ganesh Venkatesan, Intel CorporationSlide 1 Proposal –Radio Resource Measurement Capability Enabled.
Doc.: IEEE /0357r0 Submission March 2008 Michelle Gong, Intel, et alSlide 1 Enhancement to Mesh Discovery Date: Authors:
Doc.: IEEE /0862r0 Submission July 2009 Michael Bahr, Siemens AGSlide 1 Proxy Update Element Revision Date: Authors:
EDMG Capability and Operation Element Channel Indications
40 MHz Coexistence in 2.4 GHz Tutorial
Time Features Date: Authors: May 2009 Month Year
Service discovery architecture for TGaq
BSSID Information in FCS
Improve Scanning for Identifying Transmitted BSSID
“All Groups” multicast diagnostics request
Link Metric for High Throughput Mesh
Symmetrical Airtime Link Metric Report and Path Loop Avoidance
“All Groups” multicast diagnostics request
Wake Up Frame to Indicate Group Addressed Frames Transmission
BSS Scanning through Low Power Radio
Consideration on WUR frame for Fast Scanning
Consideration on WUR frame for Fast Scanning
Power Efficient PS Poll
MCCA Comments Resolution 159 ppt
Symmetrical Airtime Link Metric Report and Path Loop Avoidance
Multi-band Discovery Assistance
Link Metric for High Throughput Mesh
Enhancements to Mesh Discovery
Enhancement to Mesh Discovery
Multi-band Discovery Assistance
MDA Comments 1 Date: Authors: September, 2008 Feb, 2008
Fix inconsistency in PLM specification
Mesh Frame Formats Date: Authors: July 2007 March 2007
Resolutions to orphan comments
FILS Handling of Large Objects
BSSID Information in FCS
CID#102 - Channel Allocation
Fair Quiet for DFS Date: Authors: February 2008
Reverse Direction in ac
MCCAOP Advertisement motivation discussion
TIM Compression for No Buffered Unicast Traffic
Local Administrator Advertisements
MDA comments categorization
Slot-based Power Save without PS-Poll
Slot-based Power Save Improvement
AP Power Down Notification
80MHz/160MHz Protection Date: Authors: Date: September 2010
Further Consideration for WUR Acknowledgement Indication
MCCA Comments Resolution 159 ppt
FDMA MAC Support Date: Authors: Liwen Chu Marvell
MDA Comment Resolution 2
FILS Handling of Large Objects
Channel Allocation March 2008 Authors: Date: Month Year
HT Features in Mesh Network
80MHz/160MHz Protection Date: Authors: Date: September 2010
Terminology changes in a nutshell …
Common Mesh TSF Issues Date: Authors: September 2007
Mutliband-60GHz-Location-Capability-Publishing
Mesh Frame Formats Date: Authors: June 2007 March 2007
NGV Backward Interoperability: Follow-up
80MHz/160MHz Protection Date: Authors: Date: September 2010
MAC beaconing sync comment resolution overview
Time Features Date: Authors: May 2009 Month Year
FILS Frame Content Date: Authors: February 2008
MBCA and Beacon Timing element clean up
80MHz/160MHz Protection Date: Authors: Date: September 2010
EHT Multi-link Operation
Mesh Frame Formats Date: Authors: July 2007 March 2007
Further Consideration for WUR Acknowledgement Indication
FDMA MAC Support Date: Authors: Liwen Chu Marvell
80MHz/160MHz Protection Date: Authors: Date: September 2010
Multiple Link Operation Capability Announcement
Presentation transcript:

CPVs in Mesh formation Date: 2008-09-08 Authors: September, 2008 Feb, 2008 doc.: IEEE 802.11-07/xxxx September, 2008 CPVs in Mesh formation Date: 2008-09-08 Authors: Dee Denteneer, Philips Liwen Chu, STMicroelectronics

Resolve a number of CIDs on the use of the CPV during mesh formation September, 2008 Resolve a number of CIDs on the use of the CPV during mesh formation CIDs: 428, 429, 924, 496, 1044, 1045, 287, 650 Dee Denteneer, Philips

Channel precedence value September, 2008 Channel precedence value Recap: 4 octet field in mesh configuration element Contains a random value of 31 bits Used in mesh formation and channel switch We consider mesh formation only: In case MESH STA detects candidate peers on different channels, it selects the peer with the numerically highest channel precedence value Several issues in comments Dee Denteneer, Philips

Channel precedence value: issues September, 2008 Channel precedence value: issues Is not what one wants: (429, 924, 650) 429: MESH STA in mesh should get high priority in channel selection 650: “Although the sentence here requires MPs to operate the unification of the channel unconditionally, some MPs within a mesh would like to oprate on a different channel, depending on the bridging function within an MP which has multiple radio capability. This channel unification should not be mandated.” Dee Denteneer, Philips

Channel precedence value: timing issues September, 2008 Channel precedence value: timing issues Leads to detailed timing issues: 428: if new MESH STA, joining a mesh, has higher CPV? “Because the mesh configuration IE is carried in beacon/probe responses, an MP needs to configure it before it does anything else.” Dee Denteneer, Philips

CPV: Multi-radio issues September, 2008 CPV: Multi-radio issues CID 28, 426, 496, 1167, 650 There seems to be a hole in the use of CPV for multi-radio, as all neighboring MPs are forced to select the MP with the highest CPV. Hence, one radio is ignored. Conversely: if the device has two radios, both are mandated to use the same channel Dee Denteneer, Philips

Having a CPV leads to issues in switching (1044, 1045) September, 2008 Having a CPV leads to issues in switching (1044, 1045) 1044: how is the new CPV chosen 1045: Having one leads to algorithmic problem during switching (i.e there is a cpv associated with the current channel) Defines an increasing sequence that ultimately converges and invalidates further use Dee Denteneer, Philips

Suggestion Remove CPV-usage for mesh formation September, 2008 Suggestion Remove CPV-usage for mesh formation Introduce a bit (e.g. in mesh flags field) indicating being part of a mesh or connection to portal Additionally include some channel characterisation (e.g. number of peers, CSA-measurement) Use the channel switch protocol to coalesce the mesh to one channel. Dee Denteneer, Philips

Straw poll Should we A: Retain CPV for mesh formation September, 2008 Straw poll Should we A: Retain CPV for mesh formation B: Introduce a bit to indicate whether the MESH STA is connected to a portal C: Introduce a bit to indicate whether the MESH STA is part of a mesh and include some channel characterisation (e.g. number of peers, CSA-measurement) as well D: don’t know/care Dee Denteneer, Philips