1. Department of Digital SystemsMsc.Digital Communications and Networks HANDOVERIN 4G NETWORKS OikonomakisSpyridon PantelopoulouCharikleia
2. Structure of Presentation Handover Basics Handover in and between 4G networks Handover procedures IEEE 802.16m Advanced handover features IEEE 802.16m Legacy supported handover IEEE 802.16m Handover Framework 3GPP LTE-Advanced Interworking between IEEE 802.16m & 3GPP LTE-Advanced Conclusions
3. The Term Handover The process of transferring an ongoing call or data session from one channel to another in a cellular network. Basic reasons why a handover might be conducted: The user has moved out of range The base station is full It is a key component in cellular network mobility management as it requires a specific latency on server interruption time.
4. Handover Framework Requirements Latency and Flexibility Scalability of handover framework to handle increased handovers without compromising latency performance Handling networks with heterogeneous BS entities (pico / femtocells) Optimizations to allow handover to multicarrier-capable devices.
13. ADVANCED HANDOVER FEATURES IEEE 802.16m Goal: To reduce latency during handover in physical and MAC layers and provide a better end-user experience Advanced handover enhancements based on the general handover call flow: Seamless Handover EBB Handover (Entry Before Break) Newly introduced in the IEEE 802.16m air interface protocol: Legacy Supported Handover Multicarrier Handover
16. Legacy Supported Handover IEEE 802.16m (2) Handover procedure from an IEEE 802.16e BS to a mixed-mode IEEE 802.16m BS
17. Legacy Supported Handover IEEE 802.16m (3) Handover from a 16e BS to a 16m Only BS (direct handover) Case of the largest interruption time due to lack of the demanded BSs’ interfaces Legacy ASN : Security update is a typical intra-16m handover case Requires capability negotiation and MAC context setup 16m ASN: Requires full network entry
18. Legacy Supported Handover IEEE 802.16m (4) Handover from a 16m BS to a 16e BS Either the 16m MS performs legacy handover to the 16e BS through the Lzone Or the 16m MS performs direct handover to the 16e BS through the MZone
19. The Handover Framework of 3GPP LTE-Advanced Hard handover is similar to IEEE 802.16m Differences: Allows only BBE (Break Before Entry) operation Handover initiation and target selection are more tightly controlled by the network Supports seamless and lossless handover User procedure can be assigned in a per resource bearer (RB) manner Packet Data Convergence Protocol (PDCP) handles differently the data forwarding at the UE and eNodeB sides in different modes
20. Interworking Between IEEE 802.16m and 3GPP LTE-Advanced (1) Handover from IEEE 802.16m to 3GPP LTE-Advanced can use tow layer-2 protocols: IEEE 802.16m generic MAC layer-2 transfer tunnel IEEE 802.21 media-independent handover protocol Given these frameworks and MAC layer control signaling there can be support of: single-radio handover dual radio handover
21. Interworking Between IEEE 802.16m and 3GPP LTE-Advanced (2) Handover from 3GPP LTE-Advanced to IEEE 802.16 family supports dual radio procedure via layer 3 transport. The 3GPP Service and Architecture 2 (SA2) specification requires layer 3 handover signaling for UE to preregister with WiMAX network. Disadvantage: No layer-2 radio access network 2 (RAN2) specification defined to optimize handover
22. Conclusions Reducing service interruption time is becoming more in next-generation wireless systems. IMT-Advanced Systems provide advanced handover mechanisms in order to provide enhanced user experience during handover. Important requirement when design IEEE 802.16m and 3GPP systems is: Legacy supported mobility management All previously described advanced features of handover mechanisms enhance the user experience by: Reducing handover interruption time Diminishing the coverage hole
Scalability of handover framework to handle increased handovers without compromising latency performanceFlexibility to support various 4G deployments
Mobility framework designed to cover: all possible deployment scenarios enable and optimize handover between IEEE 802.16m Bss handover from an IEEE 802.16e BS to an IEEE 802.16m BS (note: under a legacy ASN network) intra-BS zone switch between LZone and Mzone
Exception HandlingThe handover is considered failedMS performs cell reselectionMS performs network re-entry procedure or initial network entry procedure
Seamless handover is a network re-entry procedure:Exchange of PDUs between MS and BS before network re-entrySupports data integrity protectionNot demanding full uplink synchronization from MS to BSRequires coordination serving and target BSsEBB handover is an optimized hard handover procedure:Network re-entry to the target BS during the negotiated network re-entry procedure intervalsCommunication with serving BS until the completion of the network re-entryLegacy supported handover provides:Backward compatibilitySupport mobility capability across coexisting legacy and advanced networks.Multicarrier handover:Capability of BSs and MSs to operate over multiple carriers upon a common MAC layerResults in high data rate service and cell capacity increaseCombined with seamless handover allows zero tolerance of data interruption time
One or two iterations to avoid excessive scheduling overhead
One or two iterations to avoid excessive scheduling overhead
Handover from a 16e BS to a 16m Mixed Mode BS
(Access Service Network)
(Access Service Network)
Seamless handover mode:Minimizes complexity and delayPotential loss of Service Data Units (SDUs)Appropriate for loss-tolerant but delay-sensitive data (e.g. VoIP)Lossless handover mode:Guarantees in-sequence packet delivery during handoverRetransmits any unacknowledged PDUs prior to handoverAppropriate for dealy-tolerant services (e.g. FTP)
TSG SA WG2 Architecture is in charge of developing the Stage 2 of the 3GPP network. Based on the services requirements elaborated by SA1, SA2 identifies the main functions and entities of the network, how these entities are linked to each other and the information they exchange. The output of SA2 is used as input by the groups in charge of the definition of the precise format of messages in Stage 3