1. Analysis of burst-based forwarding for non-transparent RS
IEEE Presentation Submission Template (Rev. 9)
Document Number:
IEEE S802.16j-07/271
Date Submitted:
[The date this revision of the document is uploaded, in the format Tell the truth. Automatic numbering is prohibited]
Source:
Kanchei (Ken) Loa, Yung-Ting Lee, Voice:
Yi-Hsueh Tsai, Hua-Chiang Yin, Shiann-Tsong Sheu, Youn-Tai Lee
Institute for Information Industry (III)
8F, No. 218, Sec. 2, Dunhua S. Rd.,
Taipei City 106, Taiwan
Venue:
IEEE Session #52, Atlanta, USA
Base Contribution:
C802.16j-07/271r5
Purpose:
Notice:
This document does not represent the agreed views of the IEEE Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who 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:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
< and <
Further information is located at < and < >.

2. Summary (1/3)
Burst-based forwarding scheme incurs an extra MAP overheads between 0.67% and 3.22% for a 2-hops MR system with centralized scheduling (assuming that no MPDU-based forwarding is used)
Burst-based forwarding scheme for the non-transparent RS is pending (comment #505 and 07_271r5 provides details)

3. Summary (2/3)
The burst-based forwarding scheme + the MPDU-based forwarding provide the most efficient and complete solution for non-transparent RS under centralized scheduling
When the routing table is converged, MPDU-based forwarding is used to minimize the overhead
When the routing table is in the transition state, burst-based forwarding is used to minimize the outage due to MS movement

4. Summary (3/3)
In an RS group with non-transparent RSs, the burst-based forwarding + the MPDU-based forwarding + RS member list update messages provide the most efficient and complete solution
When the RS group routing table is converged, MPDU-based forwarding is used to minimize the overhead
Using the unicast/multicast RS member list update and the acknowledgement, the convergence of the routing table update could be time-consuming
Burst-based forwarding are used to minimize the outage

5. RSs in an RS group send different preamble/FCH/MAP
Example 1
RSs in an RS group send different preamble/FCH/MAP

6. Enhance PDU Forwarding with Burst-based Forwarding – MS Movement (1/2)
The MS moves from RS1 to RS2, where RS1 and RS2 broadcast different preamble/FCH/MAP
MR-BS
RS1
(access RS)
RS2 MS
RS1 is the access station
………..
MSID  MS
MAP IE (RS1)
PDU (MSID)
MAP IE (MS)
PDU (MSID)
MS move into the proximity of RS2
MOB_MSHO-REQ
MOB_MSHO-REQ
MOB_BSHO-RSP
MOB_BSHO-RSP
MOB_HO-IND
MR-BS
Recognize MS attachment to RS2
MOB_HO-IND

7. Burst-based forwarding via RS2 for MS Data Burst
Enhance PDU Forwarding with Burst-based Forwarding – MS Movement (2/2)
When MS successfully finishes network re-entry and during the period that CID to path binding at RS1 is removed and the CID to path binding at RS2 is not set, burst-based forwarding can be used for data forwarding
MR-BS
RS1
RS2
(Access RS) MS
802.16e NW re-entry success
Burst-based forwarding via RS2 for MS Data Burst
MS_INFO-DEL
CID to path
binding removal
………..
MSID  MS
MR_Generic-ACK
CID to path binding
(MS  RS2)
DSA-REQ
………..
MSID  MS
DSA-RSP
MAP IE (RS2)
PDU (MSID)
MAP IE (MS)
PDU (MSID)

8. RSs send the same preamble/FCH/MAP
Example 2
RSs send the same preamble/FCH/MAP

9. Enhance PDU Forwarding with Burst-based Forwarding In an RS Group – MS Movement (1/3)
The MS moves from RS1 to RS2, where RS1 and RS2 broadcast same preamble/FCH/MAP
MR-BS
RS1
(access RS)
RS2 MS
RS1 is the access station
………..
MSID  MS
MAP IE (RS1)
PDU (MSID)
MAP IE (MS)
PDU (MSID)
MS move into the proximity of RS2. But MS is unaware
MOB_RSSCN-REP
Mode 1 or 2
Event trigger or periodic
MOB_RSSCN-REP
Mode 1 or 2
Event trigger or periodic
MR-BS
Recognize MS attachment to RS2

10. Enhance PDU Forwarding with Burst-based Forwarding In an RS Group – MS Movement (2/3)
MR_Member_List_Update message could be used to update the forwarding rules of specific MSs in a multicast fasion
However, the issues of multicast ACK need to be resolved. Moreover, the period to complete the member list update could be long due to ACK failure
MR-BS
RS1
RS2
(Access RS) MS
RNG-RSP (Adjustments to sync with RS2)
MR_Member_List_Update
CID to path
binding update
………..
MSID  MS
ACK??
………..
MSID  MS
ACK??
CID to path binding
(MS  RS2)
MAP IE (RS2)
PDU (MSID)
MAP IE (MS)
PDU (MSID)

11. Burst-based forwarding via RS2
Enhance PDU Forwarding with Burst-based Forwarding In an RS Group – MS Movement (3/3)
Instead, MR_Member_List_Update message is used to update the forwarding rules of specific MSs in an unicast fashion
Then burst-based forwarding can be used for data forwarding before the member list update is complete
MR-BS
RS1
RS2
(Access RS) MS
RNG-RSP (Adjustments to sync with RS2)
Burst-based forwarding via RS2
MR_Member_List_Update
CID to path
binding update
………..
MSID  MS
ACK?
MR_Member_List_Update
CID to path binding
(MS  RS2)
………..
MSID  MS
ACK??
MAP IE (RS2)
PDU (MSID)
MAP IE (MS)
PDU (MSID)