PREQ/PREP Create/Process/Forward

Slides:



Advertisements
Similar presentations
1 A Review of Current Routing Protocols for Ad-Hoc Mobile Wireless Networks By Lei Chen.
Advertisements

Doc.: IEEE /2555r0 Submission September 2007 Guenael Strutt, MotorolaSlide 1 Mesh points that do not forward Date: Authors:
Doc.: IEEE /1267r0 Submission November 2008 L. Chu Etc.Slide 1 Multiple Radio MP Date: Authors:
Doc.: IEEE /2439r0 Submission September 2007 L.Chu Etc.Slide 1 Forwarding at Intermediate and Destination Mesh Points (MP) using 6-Address Scheme.
MANETs Routing Dr. Raad S. Al-Qassas Department of Computer Science PSUT
Mobile and Wireless Computing Institute for Computer Science, University of Freiburg Western Australian Interactive Virtual Environments Centre (IVEC)
Mobile and Wireless Computing Institute for Computer Science, University of Freiburg Western Australian Interactive Virtual Environments Centre (IVEC)
Ad-hoc On-Demand Distance Vector Routing (AODV) Sirisha R. Medidi.
Mobile Adhoc Network: Routing Protocol:AODV
Ad hoc On-demand Distance Vector (AODV) Routing Protocol ECE 695 Spring 2006.
Ad-hoc On-Demand Distance Vector Routing (AODV) and simulation in network simulator.
RFC 3561 AODV Routing Protocol Mobile Ad Hoc Networking Working Group Charles E. Perkins INTERNET DRAFT Nokia Research Center 19 June 2002 Elizabeth M.
1 Ad Hoc On-Demand Distance Vector Routing (AODV) Dr. R. B. Patel.
AODV: Introduction Reference: C. E. Perkins, E. M. Royer, and S. R. Das, “Ad hoc On-Demand Distance Vector (AODV) Routing,” Internet Draft, draft-ietf-manet-aodv-08.txt,
A Scalable Routing Protocol for Ad Hoc Networks Eric Arnaud Id:
Doc.: IEEE /1234r0 Submission October 2008 L. Chu Etc.Slide s Power Saving Issues Date: Authors:
Doc.: IEEE /0636r0 Submission April 2008 L. Chu Etc.Slide 1 Symmetrical Airtime Link Metric Report and Path Loop Avoidance Date: Authors:
Ad-hoc On Demand Distance Vector Protocol Hassan Gobjuka.
Doc.: IEEE /0278r5 Submission March 2008 Javier Cardona et al. Avoiding Interactions with Lazy-WDS Equipment Date:
6LoWPAN Ad Hoc On-Demand Distance Vector Routing Introduction Speaker: Wang Song-Ferng Advisor: Dr. Ho-Ting Wu Date: 2014/03/31.
Ad Hoc On-Demand Distance Vector Routing (AODV) ietf
Fundamentals of Computer Networks ECE 478/578
Doc.: IEEE /0174r1 Submission Hang Liu, et al. March 2005 Slide 1 A Routing Protocol for WLAN Mesh Hang Liu, Jun Li, Saurabh Mathur {hang.liu,
Doc.: IEEE /1893r0 Submission December 2006 Marc Mosko, PARCSlide 1 [HWMP Routing Loops] Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /0174r2 Submission Hang Liu, et al. March 2005 Slide 1 A Routing Protocol for WLAN Mesh Date: Authors: Notice: This document.
Author:Zarei.M.;Faez.K. ;Nya.J.M.
By Ioannis Chatzigiannakis, Elena Kaltsa, Sotiris Nikoletseas
Internet Networking recitation #4
Sensor Network Routing
任課教授:陳朝鈞 教授 學生:王志嘉、馬敏修
Path Selection and Power Save
Mobile and Wireless Networking
by Saltanat Mashirova & Afshin Mahini
1-PREQ : n-Targets versus n-PREQ : 1-Target
TDLS Setup Date: Authors: Mar 2008 September 2007
Symmetrical Airtime Link Metric Report and Path Loop Avoidance
RFI Update Date: Authors: September 2006 Month Year
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
Scalable Station Association Information Handling
Symmetrical Airtime Link Metric Report and Path Loop Avoidance
Scalable Station Association Information Handling
Multicast/Broadcast Communication With Acknowledge
EDCA and BlockAck Extensions for Reliable Multicast/Broadcast Services
Problem & Proposal for User Plane Support for QoS Mapping
Reverse Direction in ac
HWMP Specification Update
RTS CTS Rule Amendment Date: Authors: Date: January 2011
A Hybrid Mesh Routing Protocol
MAPID for User Plane Support
March 2007 doc.: IEEE /0389r0 March 2007
Proposed Resolutions to RFI comments of LB 166 on IEEE s D7.0
TBR Centralized Routing Extension
PREQ/PREP Create/Process/Forward
PREQ/PREP Create/Process/Forward
RFI Update Munich Meeting
PREQ/PREP Create/Process/Forward
Packet forwarding for non-routable devices in Multi-hop Wireless Mesh
HT Features in Mesh Network
LB93 Unresolved RFI Comments
Scalable Station Association Information Handling
VTS Robust Multicast/Broadcast Protocol
Vinay Singh Graduate school of Software Dongseo University
A Routing Protocol for WLAN Mesh
Routing protocols in Mobile Ad Hoc Network
RFI Update Munich Meeting
Routing in Mobile Wireless Networks Neil Tang 11/14/2008
RFI Update Munich Meeting
Fast Handover Date: Authors: May 2009 Feb, 2008
September 2006 doc.: IEEE /1351r0 September 2006
PREQ/PREP Create/Process/Forward
Presentation transcript:

PREQ/PREP Create/Process/Forward Feb, 2008 doc.: IEEE 802.11-07/xxxx September 2008 PREQ/PREP Create/Process/Forward Date: 2008-09-09 Authors: L. Chu Etc. Liwen Chu, STMicroelectronics

Path Stability With Rate of Sequence Number (SN) Change September 2008 Path Stability With Rate of Sequence Number (SN) Change Sequence number (SN) is used to avoid path loop in HWMP. Increasing SN by 1 each time a MP sends a PREQ may change the path frequently. One solution to maintain path stability in the current draft is to use the same source SN for dot11MeshHWMPnetDiameterTraversalTime. PREQ ID is increased by 1 each time a new PREQ is created. Why avoiding path instability is important: Baseline dot11 standard requires that “There shall be no reordering of unicast MSDUs with the same TID value and addressed to the same destination.” (Section 6.1.3) L. Chu Etc.

Current PREQ Acceptance Criteria September 2008 Current PREQ Acceptance Criteria The PREQ element shall not be accepted: The Originator DSN < previous Originator DSN (DSN = previous DSN) AND (updated path metric is worse than previous path metric) (the destination address of the PREQ is neither the recipient MAC address nor a MAC address proxied by the recipient) AND (dot11MeshForwarding is set to 0) PREQ ID is not considered in PREQ acceptance criteria. L. Chu Etc.

Current PREP Creating Criteria September 2008 Current PREP Creating Criteria Case A: Original transmission A PREP is transmitted if the MP has received a PREQ fulfilling all of the following conditions: a. One of the following applies: The Destination Address of the PREQ is the same as MAC address of the receiving MP The Destination Address of the PREQ = all 1’s (broadcast) and the PREP flag is set to 1 (”Proactive PREP”) The Destination Address of the PREQ is currently proxied by the MP b. One of the following applies: The Originator DSN of the PREQ (preq.orig_dsn) is greater than the DSN of the last PREQ received from the same originator address (that includes the case that there is no path to the originating MP) The Metric is better than the path selection metric currently associated with the Originator Address and the Originator DSN of the PREQ (preq.orig_dsn) is equal to the DSN of the last PREQ received from the same originator address PREQ ID is not considered in PREP creating criteria. L. Chu Etc.

PREQ Create/Process/Forward Procedure Refinement September 2008 PREQ Create/Process/Forward Procedure Refinement The PREQ element shall not be accepted if any of the following is true: The Originator DSN < previous Originator DSN (DSN = previous DSN) AND (PREQ ID of the originator is not the first time to be received) AND (updated path metric is worse than previous path metric) (the destination address of the PREQ is neither the recipient MAC address nor a MAC address proxied by the recipient) AND (dot11MeshForwarding is set to 0) Effect of PREQ receipt (Add the following restriction): The receiving MP shall not update the active forwarding information for the originator if the updated path metric is worse than the previous path metric L. Chu Etc.

September 2008 PREP Introduction PREP follows unicast reverse path from the destination MP to the source MP A destination does not need to increase its destination sequence number each time it sends a PREP in the current HWMP An intermediate MP uses the destination sequence number and path metric to decide if the received PREP is discarded The PREP element shall not be accepted (and shall not be processed as described in 11B.9.6.3.2) if any of the following is true: The DSN < previous DSN from this originator The Time to Live is 1 or less (the destination address of the PREQ is neither the recipient MAC address nor a MAC address proxied by the recipient) AND (dot11MeshForwarding is set to 0) Different reverse paths from a destination may have same intermediate MPs these intermediate MPs will decide if the PREPs for different source MPs from the same destination MP are discarded L. Chu Etc.

Destination Sequence Number in 11s Draft September 2008 Destination Sequence Number in 11s Draft In section 11B.9.4.2, a destination MP increments its sequence number Immediately before a destination MP originates a PREP in response to a PREQ, it shall update its own sequence number to the maximum of its current sequence number and the destination sequence number in the PREQ. The intermediate MP may wrongly discard received PREP based on this DSN updating criteria L. Chu Etc.

Updated Destination Sequence Number in 11s Draft September 2008 Updated Destination Sequence Number in 11s Draft A destination MP shall update its sequence number based on the following criteria: A destination MP shall increment its own sequence number the same as the destination sequence number in the RREQ plus 1 if the destination sequence number in the RREQ is larger than or equal to the sequence number in the destination MP. Otherwise, a destination MP shall not change its sequence number. Another equivalent description is that: Immediately before a destination MP originates a PREP in response to a PREQ, it shall update its own sequence number to the maximum of its current sequence number and the destination sequence number in the PREQ plus 1. L. Chu Etc.

Wrongly PREP Discard in Intermediate MP September 2008 Wrongly PREP Discard in Intermediate MP MP1 request a path to MP5 with DO = 1, DSN=0 MP3 discards PREP (D:1) since the SN and path metric are the same. MP1 S:1 D: 0 P:1 S:1D:0 P:1 MP3 S:1D:0 P:1 1 1 MP5 does not increase its destination SN since DSN in MP5 is 1. MP2 1 D:1 MP5 1 1 2 MP0 MP4 New MP2 FIB DST NHP DSN Metric PID MP5 MP3 1 2 MP1 Original MP2 FIB DST NHP DSN Metric PID MP5 MP3 1 2 MPi x MPj x: Metric between MPi and MPj New MP3 FIB DST NHP DSN Metric PID MP2 1 MP5 MP1 2 Original MP3 FIB DST NHP DSN Metric PID MP2 1 MP5 S:x D: y P:z PREQ for MP5 with source SN x, destination SN y PREQID z D:x PREP for MP5 with destination SN x New MP5 FIB DST NHP DSN Metric PID MP2 MP3 1 2 MP1 3 Original MP5 FIB DST NHP DSN Metric PID MP2 MP3 1 2 L. Chu Etc.

Updated Destination Sequence Number in 11s Draft September 2008 Updated Destination Sequence Number in 11s Draft The further update should be done in intermediate MP: When an intermediate MP accepts an PREQ, if the destination MP’s SN in the forwarding table of the intermediate MP is larger than the DSN of the destination MP in PREQ, the DSN in PREQ shall be updated to the destination MP’s SN maintained in this intermediate MP. L. Chu Etc.

September 2008 Backup Slides L. Chu Etc.

Wrongly PREQ Discard in Intermediate MP September 2008 Wrongly PREQ Discard in Intermediate MP MP1 requests a path to MP5. x MPi MPj x: Metric between MPi and MPj PREQ for MP5 with source SN x and PREQ ID y S:x P:y PREQ for MP6 with source SN x and PREQ ID y MP1 requests a path to MP6. MP2 S:1 P:2 S:1 P:2 S:1 P:1 MP5 1 2 1 MP1 MP4 MP4 discards PREQ (S:1 P:2) Since bullet 2 in PREQ accepting criteria is true 1 1 1 S:1 P:1 MP3 S:1 P:1 MP6 MP3 FIB DST NHP DSN Metric PID MP1 1 MP4 FIB DST NHP DSN Metric PID MP1 MP3 1 2 MP2 FIB DST NHP DSN Metric PID MP1 1 2 MP5 FIB DST NHP DSN Metric PID MP1 MP4 1 3 L. Chu Etc.

Wrongly PREQ Discard in Destination MP September 2008 Wrongly PREQ Discard in Destination MP MP1 requests a path to STA1 associated with MAP4. x MPi MPj x: Metric between MPi and MPj PREQ for STA1 with source SN x and PREQ ID y S:x P:y PREQ for STA2 with source SN x and PREQ ID y PREP for STA1 MP1 requests a path to STA2 associated with MAP4. S:1 P:2 S:1 P:2 MP2 STA1 1 2 MP1 MAP4 MAP4 discards PREQ (S:1 P:2) since the metric is not better than PREQ (S:1 P:1) 1 1 S:1 P:1 MP3 S:1 P:1 STA2 MP3 FIB DST NHP DSN Metric PID MP1 1 MAP4 FIB DST NHP DSN Metric PID MP1 MP3 1 2 MP2 FIB DST NHP DSN Metric PID MP1 1 2 MP3 FIB DST NHP DSN Metric PID MP1 1 MAP4 MP1 FIB DST NHP DSN Metric PID MAP4 MP3 1 2 MP1 Proxy Table Proxy Addr Proxied Addr MAP4 STA1 L. Chu Etc.

Destination Sequence Number in AODV September 2008 Destination Sequence Number in AODV In section 6.1, a destination MP increments its sequence number Immediately before a destination MP originates a PREP in response to a PREQ, it shall update its own sequence number to the maximum of its current sequence number and the destination sequence number in the PREQ In section 6.6.1, a destination MP increments its sequence number If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message These two criteria are contradictory with each other The description in section 6.6.1 is very difficult to understand L. Chu Etc.

Path Instability with PREP Replying Right away September 2008 Path Instability with PREP Replying Right away MP0 requests a path to MP5. x MPi MPj x: Metric between MPi and MPj PREQ for MP5 with source SN x S:x P:y PREP for MP5 with destination SN x D:x S:1 P:1 MP3 MP1 1 1 1 MP2 MP5 1 D:1 1 S:1 P:1 MP0 S:1 P:1 MP4 S:1 P:1 2 MP2 FIB DST NHP DSN Metric PID MP0 1 MP4 FIB DST NHP DSN Metric PID MP0 MP2 1 2 MP4 FIB DST NHP DSN Metric PID MP0 MP2 1 2 MP5 MP3 FIB DST NHP DSN Metric PID MP0 MP2 1 2 MP5 FIB DST NHP DSN Metric PID MP0 MP4 1 4 L. Chu Etc.

Path Instability with PREP Replying Right away (Cont’d) September 2008 Path Instability with PREP Replying Right away (Cont’d) MP0 requests a path to MP5. MPi x MPj x: Metric between MPi and MPj MP3 MP1 D:2 S:1 P:1 1 S:x P:y D:2 PREQ for MP5 with source SN x 1 1 MP2 MP5 D:x D:2 1 PREP for MP5 with destination SN x 1 D:1 D:1 2 MP0 MP4 MP2 FIB DST NHP DSN Metric PID MP0 1 MP5 MP4 3 MP2 FIB DST NHP DSN Metric PID MP0 1 MP5 MP3 2 MP0 FIB DST NHP DSN Metric PID MP5 MP2 1 4 MP0 FIB DST NHP DSN Metric PID MP5 MP2 2 3 MP3 FIB DST NHP DSN Metric PID MP0 MP2 1 2 MP5 MP5 FIB DST NHP DSN Metric PID MP0 MP3 1 3 L. Chu Etc.