1. Scalable Station Association Information Handling
November 2006
doc.: IEEE /1842r1
November 2006
Scalable Station Association Information Handling
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Youiti Kado, et.al.
Youiti Kado, et.al.

2. November 2006
Abstract
We examine how to handle the associated stations alternatively in the mesh networks.
Youiti Kado, et.al.

3. November 2006
RA-OLSR
Youiti Kado, et.al.

4. Huge Proxy Table in RA-OLSR
November 2006
Huge Proxy Table in RA-OLSR + +
MAP
Table
STA
Table
MAP
STA +
Youiti Kado, et.al.

5. November 2006
Motivation
In RA-OLSR, each MAP broadcasts LABA periodically. This phenomena gives a huge proxy table in each MP.
Approach
Quick sharing the most up-to-dated associated stations information among MAPs.
Youiti Kado, et.al.

6. When station S2 moves away
November 2006
When station S2 moves away
When a station S2 leaves MAP-10 and moves to MAP-16, S2 is re-associated by MAP-16. 1 3 2 5 9 4 7 6 8 12 11 S2 10 15 14 13 16 S2 17 18 S1 21 19 23 22 20
Youiti Kado, et.al.

7. Broadcasting LABA from MAP-16
November 2006
Broadcasting LABA from MAP-16
MAP-16 broadcasts its LABA using HELLO message. 1 3 2 5 9 4 7 6 8 12 11 S2 10 15 14 13 16 S2 17 18 S1 21 19 23 22 20
Youiti Kado, et.al.

8. MAPs stop broadcasting the LABA
November 2006
MAPs stop broadcasting the LABA
Upon receiving the LABA from MAP-16, MAP-10 and MAP-19 stop broadcasting the LABA. 1 3 2 5 9 4 7 6 8 12 11 S2 10 15 14 13 16 S2 17 18 S1 21 19 23 22 20
Youiti Kado, et.al.

9. When S1 wants to communicate with S2
November 2006
When S1 wants to communicate with S2
When a station S1 wants to communicate with S2, S1 sends its data messages to MAP-15 that associating S1. Upon receiving the data message from S1, MAP-15 transforms the header of the data messages to the header containing 6-address scheme and directs the data messages to MAP-10 (without knowing that S2 moved). 1 3 2 5 9 4 7 6 8 12 11 S2 10 15 14 13 16 17 18 S1 21 S2 19 23 22 20
Youiti Kado, et.al.

10. When S1 wants to communicate with S2
November 2006
When S1 wants to communicate with S2
Upon receiving the data messages from MAP-15, MAP-10 redirects the data messages to MAP-16 that is currently associating S2. Then, MAP-16 sends the data messages to S2. 1 3 2 5 9 4 7 6 8 12 11 S2 10 15 14 13 16 17 18 S1 21 S2 19 23 22 20
Youiti Kado, et.al.

11. November 2006
HWMP
Youiti Kado, et.al.

12. November 2006
Motivation
When the Root is configured in HWMP, a proactive tree-topology is formed to transport the intra-mesh traffic.
Therefore, the associated stations use the tree-topology as a backbone to send their traffic to the corresponding destination, which could be inside or outside mesh network.
Approach
Each MAP shall piggyback the list of associated stations (including MAC addresses) into the RREP destined to Root.
Youiti Kado, et.al.

13. Broadcasting RANN from Root
November 2006
Broadcasting RANN from Root
RANN arrives at MAP-16, which associating a station S2.
Root X 1 3 2 5 9 4 7 6 8 12 11 10 15 14 13 16 17 18 S1 21 S2 19 23 22 20
Youiti Kado, et.al.

14. Unicasting RREP to Root
November 2006
Unicasting RREP to Root
The MAP-16 generates RREP with piggybacking associated station S2 address information and unicasts it to Root
Root X 1 3 2 5 9 4 7 6 8 12 11 10
RREP 15 14 13
Octets: 1 1 6 4 ID
Length
Mode Flags
= Report
Hopcount
Time to Live
Destination Address
Destination Seq.Num. 16 17 18 S1 21 S2 19 23 22 20 4 6 1
Lifetime
Metric
Source Address #1
Source Seq. Num.
Dependent MP Count N
Dependent MP MAC Address #1
Dependent MP DSN #1
...
Dependent MP MAC Address #N
Dependent MP DSN #N
Youiti Kado, et.al.

15. When S1 wants to communicate with S2
November 2006
When S1 wants to communicate with S2
When a station S1 wants to communicate with S2, S1 sends its data messages to MAP-15 that associating S1. Upon receiving the data message from S1, MAP-15 transforms the header of the data messages to the header containing 6-address scheme and directs the data messages to Root.
Root X 1 3 2 5 9 4 7 6 8 12 11 10 15 14 13 16 17 18 S1 21 S2 19 23 22 20
Youiti Kado, et.al.

16. When S1 wants to communicate with S2
November 2006
When S1 wants to communicate with S2
Upon receiving the data messages from MAP-15, Root that knew MAP-16 is associating S2 redirects the data messages to MAP-16. Upon receiving the data message from the Root, MAP-16 sends the data messages to S2.
Root X 1 3 2 5 9 4 7 6 8 12 11 10 15 14 13 16 17 18 S1 21 S2 19 23 22 20
Youiti Kado, et.al.

17. When S1 wants to communicate with S2
November 2006
When S1 wants to communicate with S2
Assuming the Root has a centralized routing support scheme, the Root informs a recommended route from MAP-15 to MAP-16 by sending a RREP to MAP-15.
Upon receiving the RREP from the Root, MAP-15 sends the S1’s data messages to MAP-16 along the recommended route.
Root X 1 3 2 5 9 4 7 6 8 12 11 10 15 14 13 16
Octets: 1 1 6 4 ID
Length
Mode Flags
= Info
Hopcount
Time to Live
Destination Address
Destination Seq.Num. 17 18 S1 21 S2 19 23 22 20 4 6 1
Lifetime
Metric
Source Address = S1
Source Seq. Num.
Dependent MP Count N = 2
MAC Address
= S2
S2’s DSN
= MP16
MP16’s DSN
Youiti Kado, et.al.

18. November 2006
Additional
MAP to MPP
Youiti Kado, et.al.

19. November 2006
Motivation
When the Root is configured in HWMP, a proactive tree-topology is formed to transport the intra-mesh traffic.
Therefore, the dependent MPs of MAP use the tree-topology as a backbone to send their traffic to the corresponding destination, which could be inside or outside mesh network.
Approach
Each MPP shall piggyback the list of dependant MPs (including MAC addresses) into the RREP destined to Root.
Youiti Kado, et.al.

20. Broadcasting RANN from Root
November 2006
Broadcasting RANN from Root
RANN arrives at MAP-16 who is a Root (a0) of another mesh segment (in this case, wireless portal contains MAP-16 and a0).
Root X 1 3 2 5 9 4 7 6 8 12 a4 11 10 a1 15 14 13 a5 a0 16 17 18 S1 a6 a2 21 19 23 22 20
Youiti Kado, et.al.

21. Unicasting RREP to Root
November 2006
Unicasting RREP to Root
The MAP-16 generates RREP with piggybacking MPs’ address information of another mesh segment and unicasts it to Root.
Root X 1 3 2 5 9 4 7 6 8 12 a4 11 10 a1 15 14 13 a5 a0 16 17 18 S1 a6 a2 21 19 23 22 20
Youiti Kado, et.al.

22. When S1 wants to communicate with MP-a2
November 2006
When S1 wants to communicate with MP-a2
When a station S1 wants to communicate with MP-a2, S1 sends its data messages to MAP-15 that associating S1. Upon receiving the data message from S1, MAP-15 transforms the header of the data messages to the header containing 6-address scheme and directs the data messages to Root.
Root X 1 3 2 5 9 4 7 6 8 12 a4 11 10 a1 15 14 13 a5 a0 16 17 18 S1 a6 a2 21 19 23 22 20
Youiti Kado, et.al.

23. When S1 wants to communicate with MP-a2
November 2006
When S1 wants to communicate with MP-a2
Upon receiving the data messages from MAP-15, Root that knew MAP-16 is a wireless portal of MP-a2 redirects the data messages to MAP-16. Upon receiving the data message from the Root, MAP-16 sends the data messages to MP-a2.
Root X 1 3 2 5 9 4 7 6 8 12 a4 11 10 a1 15 14 13 a5 a0 16 17 18 S1 a6 a2 21 19 23 22 20
Youiti Kado, et.al.

24. When S1 wants to communicate with MP-a2
November 2006
When S1 wants to communicate with MP-a2
Assuming the Root has a centralized routing support scheme, the Root informs a recommended route from MAP-15 to MAP-16 by sending a RREP to MAP-15.
Upon receiving the RREP from the Root, MAP-15 sends the S1’s data messages to MAP-16 along the recommended route.
Root X 1 3 2 5 9 4 7 6 8 12 a4 11 10 a1 15 14 13 a5 a0 16 17 18 S1 a6 a2 21 19 23 22 20
Youiti Kado, et.al.