1 / 10

Proactive PREQ/P and HWMP MIB Variables

Proactive PREQ/P and HWMP MIB Variables. Authors:. Date: 2009-03-02. Abstract.

dyami
Download Presentation

Proactive PREQ/P and HWMP MIB Variables

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. Proactive PREQ/P and HWMP MIB Variables Authors: Date: 2009-03-02 Michael Bahr (Siemens AG, CT)

  2. Abstract This presentation gives the motivation for the changes proposed in document 11-09/0261r1, that will solve some deficiencies with the updating of bidirectional paths in proactive PREQ without proactive PREP mode. Furthermore, the presentation highlights and explains the proposed changes. The presentation outlines the additions and changes to the HWMP MIB variables briefly. Michael Bahr (Siemens AG, CT)

  3. Proactive PREQ without Proactive PREP  unidirectional paths from all MSTAs to root MSTA  bidirectional path from root MSTA to single MSTA (sent proactive PREP before first data frame)  unidirectional path from single MSTA to root MSTA is updated/ changed  unidirectional path from root MSTA to single MSTA is not updated and breaks Michael Bahr (Siemens AG, CT)

  4. Update of Paths from Root MSTA to Single MSTA • send a proactive PREP in response to a proactive PREQ with proactive PREP flag set to 0 as long as a bidirectional path is required • need to recognize „bidirectional path is required“ • concept of virtual „data flow“: number of subsequent root intervals with data to be sent to root MSTA by MSTA as source • mechanism that controls the response with a proactive PREP based on the concept of „data flow“ Michael Bahr (Siemens AG, CT)

  5. Proposed Changes for Updating Bidirectional Paths • two boolean fields in forwarding information to root MSTA • Proactive PREP field • controls sending a proactive PREP in response to a proactive PREQ • Proactive PREP Sent field • avoids sending a proactive PREP before every data packet • compatible with proactive PREQ with proactive PREP Michael Bahr (Siemens AG, CT)

  6. Text Changes in 11-09/0261r1 • Necessary behaviour described in HWMP clauses • clause 11B.10.1.3.1 Proactive PREQ mechanism • clause 11B.10.6.3.2 Effect of receipt (of PREQ) • missing description on receipt of a proactive PREQ • Detailed concept is described in new clause of (informative) Annex V • definition of the two fields in forwarding information to root MSTAs • initial proactive PREP just before first data frame of „data flow“ • setting of the boolean fields in forwarding information • procedures after receiving a proactive PREQ • conditions for generation of proactive PREP Michael Bahr (Siemens AG, CT)

  7. HWMP MIB Variables Clean-up • dot11MeshHWMPrannInterval vs. dot11MeshHWMProotInterval • …rann… indicates just one special mechanism • …root… introduced for proactive PREQ • dot11MeshHWMPpathToRootIntervaldot11MeshHWMPpathToRootTimeout • this is actually the lifetime of the forwarding information to the root mesh STA • timeout is consistent with on-demand terminology • dot11MeshHWMPnetDiameter • has been missing in annex Michael Bahr (Siemens AG, CT)

  8. HWMP MIB Variables Clean-up • dot11MeshHWMProotMode defined • 0 = 000  not a root mesh STA (default value) • 2 = 010  root mesh STA with proactive PREQ, no proactive PREP • 3 = 011  root mesh STA with proactive PREQ, with proactive PREP • 4 = 100  root mesh STA using RANNs • dot11MeshHWMPtargetOnly / …replyAndForward • have been missing in annex • dot11MeshHWMPmaintenanceInterval / …confirmationInterval • have been missing in annex • revisited descriptions of HWMP MIB variables Michael Bahr (Siemens AG, CT)

  9. Other Changes • Rewrite of definition of TO and RF flags • clause 7.3.2.102 • CIDs 1858-1860 • (HWMP) forwarding  propagation • in definition of PREQ element in 7.3.2.102 • mesh STAs with dot11MeshForwardingEnabled has to be also part of the proactive tree • included target address = broadcast address as acceptance criteria • included dot11MeshForwardingEnabled = 1 as condition for propagation of PREQ • PANN/RANN may be included in beacon frame Michael Bahr (Siemens AG, CT)

  10. References • IEEE 802.11s Draft Standard version D2.07, January 2009 • 11-08/0493r39 “Letter Ballot 126 Comment Resolutions” • 11-09/0261r1 „Proactive PREQ/P and HWMP MIB Variables“ • proposed text changes based on this presentation Michael Bahr (Siemens AG, CT)

More Related