Callback HO Procedure for Reentry Femtocell IEEE 802

  • Slides: 7
Download presentation
Call-back HO Procedure for Reentry Femtocell IEEE 802. 16 Presentation Submission Template (Rev. 9)

Call-back HO Procedure for Reentry Femtocell IEEE 802. 16 Presentation Submission Template (Rev. 9) Document Number: IEEE C 802. 16 m-09/1304 Date Submitted: 2009 -07 -06 Source: Shiann-Tsong Sheu, Chih-Cheng Yang National Central University Kanchei (Ken) Loa, , Chun-Yen Hsu, Yung-Ting Lee, Tsung-Yu Tsai, Chiu-Wen Chen Institute for Information Industry Yang-Han Lee, Yih Guang Jan Tamkang University *<http: //standards. ieee. org/faqs/affiliation. FAQ. html> Re: 802. 16 m Amendment Working Document Call for contributions on “Support for Femtocell BS” Base Contribution: IEEE 802. 16 m-09/0010 r 2 Purpose: To be discussed and adopted by TGm for the 802. 16 m Amendment. Notice: [email protected] com [email protected] org. tw This document does not represent the agreed views of the IEEE 802. 16 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 802. 16. Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http: //standards. ieee. org/guides/bylaws/sect 6 -7. html#6> and <http: //standards. ieee. org/guides/opman/sect 6. html#6. 3>. Further information is located at <http: //standards. ieee. org/board/pat-material. html> and <http: //standards. ieee. org/board/pat >. 1

Problem Statement • Since the Femtocell backhaul link may disconnect from network and reconnect

Problem Statement • Since the Femtocell backhaul link may disconnect from network and reconnect to network sometimes, the method for handling the associated MSs to leave and return the Femtocell should be designed in order to – continue the services, and – optimize the network performance. 2

Handover Trigger • The Wi. MAX Forum document “Requirements for Wi. MAX Femtocell Systems”

Handover Trigger • The Wi. MAX Forum document “Requirements for Wi. MAX Femtocell Systems” states that – A Femtocell BS SHALL disable its downlink air interface transmitter until the connection with the operator’s network is fully established. • As the serving Femtocell loses the backhaul connection, it shall command all the associated MSs to perform handover procedure. – The handover request signal shall include the reason code, which is used to notify the MSs to record the original Femtocell BS information and wait for any callback signal. 3

Call-back handover procedure • As the Femtocell BS reconnects to the network again, the

Call-back handover procedure • As the Femtocell BS reconnects to the network again, the Femtocell BS or the network HO controller initiates the call-back handover procedure to generate the callback HO message with the original Femtocell BS ID for related BS in order to call back those MSs who have recorded the information of original Femtocell BS. • Upon the MS receiving the call-back handover signal from serving BS, it will try to handover to the recorded Femtocell BS if the signal quality is better than the current connection. 4

HO procedure when Serving Femtocell BS lost backhual link 5

HO procedure when Serving Femtocell BS lost backhual link 5

BS-initiated Call-back handover procedure 6

BS-initiated Call-back handover procedure 6

Proposed Text [Add the following sections 15. x. y “Femtocell BS Handover trigger condition”

Proposed Text [Add the following sections 15. x. y “Femtocell BS Handover trigger condition” and 15. x. y “Call-back Handover Support”] 15. x. y Femtocell BS Handover trigger condition As the Femtocell BS loses the connectivity of backhaul link, it shall send the handover command message with reason code to all associated MSs. All the notified MSs shall perform handover procedure to re-associate with the designated BSs, if any. 15. x. y Call-back Handover Support Upon the backhaul connectivity is recovered, the Femtocell BS may issue call-back handover signals with Femtocell BS ID to the related BSs for notifying those MSs, who have stored the information of Femtocell BS, to handover back. 7