May 2006 doc.: IEEE 802.11-06/0601r0 May 2006 Handling the Groupcast Sequence Number for Proxied Device in Multihop Mesh Date: 2006-05-15 Authors: Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Hrishikesh Gossain, Motorola Hrishikesh Gossain, Motorola

May 2006 doc.: IEEE 802.11-06/0601r0 May 2006 Abstract Outlines method to use groupcast sequence number for non-routable device in multihop wireless network. Hrishikesh Gossain, Motorola Hrishikesh Gossain, Motorola

Outlook of the Presentation May 2006 doc.: IEEE 802.11-06/0601r0 May 2006 Outlook of the Presentation Motivation Problem Definition Proposed Approach Conclusion Hrishikesh Gossain, Motorola Hrishikesh Gossain, Motorola

May 2006 doc.: IEEE 802.11-06/0601r0 May 2006 Motivation Multihop packet forwarding in 802.11s is built on top of IEEE 802.11 DATA format. 802.11s requires AP (routable device ) to proxy STA (non-routable device or proxied device). How do we forward groupcast (including broadcast and multicast) packets from a STA and how do we set the sequence number of such groupcast packets. In this presentation we outline method to use sequence number to forward groupcast traffic in multihop wireless network using IEEE 802.11 DATA header for non-routable device. Hrishikesh Gossain, Motorola Hrishikesh Gossain, Motorola

Problem Definition (1) 802.11s DATA Frame Format 2 Sequence numbers May 2006 doc.: IEEE 802.11-06/0601r0 May 2006 Problem Definition (1) 802.11s DATA Frame Format 2 Sequence numbers IEEE 802.11 Hop by Hop Sequence Control IEEE 802.11s Mesh End to End Sequence Frame Control Duration Address 1 Address 2 Address 3 Sequence Control Address 4 QoS Control Mesh Forwarding Control Body FCS Hop by Hop Significance Mesh E2E Sequence Time To Live (TTL) Multihop Significance Hrishikesh Gossain, Motorola Hrishikesh Gossain, Motorola

May 2006 doc.: IEEE 802.11-06/0601r0 May 2006 Problem Definition (2) What sequence number MAP should use to forward groupcast packets from non-routable devices What if MAP uses its own sequence number? IAP AP2 AP1 STA Movement Self.Seq = 100 Self.Seq = 50 L2 Distribution Hrishikesh Gossain, Motorola Hrishikesh Gossain, Motorola

Proposed Approach (1) May 2006 <Source: STA, H2H:X> <Source: STA, H: Y, E2E: X> Non-Routable Device Routable Device To Neighboring Routable Device Hrishikesh Gossain, Motorola

Proposed Approach (2) May 2006 Sequence numbers for a groupcast address in the Address 1 field sent by QSTAs/MAP are assigned using an independent counter, starting at 0 and incrementing by 1 for each MSDU or MMPDU [802.11e]. After receiving a groupcast packet from a associated STA, AP copies the current sequence number used by the STA to the packet being forwarded by itself to its end to end sequence number filed [802.11s]. So in our proposed approach, groupcast packets are forwarded by using the “originating device” sequence number. Intermediate nodes after receiving the groupcast packet, use the tuple “originating device” and sequence number to decide it they need to forward this packet. This way even if a STA handoff to AP2, groupcast packets forwarded by itself still have a valid “originating device” and sequence number tuple and packet forwarding is done without creating any loop or packet drop because of wrong sequence numbers. Hrishikesh Gossain, Motorola

May 2006 Conclusion Provides forwarding mechanism for groupcast (including broadcast and multicast) packets from STAs and how an AP set the sequence number of such groupcast packets. Hrishikesh Gossain, Motorola