Showing posts with label Handover. Show all posts
Showing posts with label Handover. Show all posts

Saturday, June 12, 2010

Handover Process | WiMAX Mobility Management



Add a Note HereAccording to the scope of node movement, mobility can be divided into micro-mobility and macro-mobility. On the link layer, most access networks provide mobility by having an access router keep track of the specific AP to which a MS is attached. The localized mobility between pico-cells (probably heterogeneous cells) in the same subnet and the mobility between subnets in one domain is called micro-mobility, whereas the mobility between domains in wide-area wireless networks is called macro-mobility. The mobility solutions like Mobile IP are classified as macro-mobility. But Mobile IP is not suitable for micro-mobility due to its signaling overhead, handover latency, and transient packet loss.

1 Hard Handover and Soft Handover

Add a Note HereHard handover is mandatory to be supported in mobile WiMAX networks. Hence, break-before-make operations may happen during the handover process. In other words, link disconnection may occur and throughput may degrade. Therefore, various levels of optimization are demanded to reduce association and connection establishment with the target BS. These optimization methods are not clearly defined in the IEEE 802.16e specification, so they should be supported on specific WiMAX systems and products.
Add a Note HereOn the contrary, soft handover is optional in mobile WiMAX networks. Two schemes, macro-diversity handover (MDHO) and fast Base Station switching (FBSS) are supported. In case of MDHO, MS receives from multiple BSs simultaneously during handover, and chooses one as its target BS. As for FBSS, the MS receives from/transmits to one of several BSs (determined on a frame-by-frame basis) during handover, such that the MS can omit the decision process of selecting the target BS to shorten the latency of handover.

2 MAC Layer Handover Procedure

Add a Note HereThe handover procedure in IEEE 802.16e-2005 is divided into MAC- and PHY-layer handover. Looking at the MAC-layer handover procedure, it is divided into the network topology acquisition phase and the handover process phase according to its performing sequence.
Add a Note HereIn the network topology acquisition phase, as illustrated in Figure 1, three functions are performed, namely network topology advertisement, MS scanning for neighboring BSs, and association procedure. After receiving a neighbor advertisement message broadcast from the serving BS, the MS gets all the neighboring BSs of its current serving BS. The MS can then perform synchronization with each neighboring BS, and then continue to the handover process phase.
Figure 1: Network topology acquisition phase for handover.

Add a Note HereFigure 1: Network topology acquisition phase for handover.
Add a Note HereDuring the handover procedure, the process includes handover decision, handover initiation, and ranging procedures, followed by authorization and registration procedures. These procedures include cell reselection, handover decision and handover initiation, synchronization with new DL, acquisition of UL parameters, ranging, MS reauthorization, reregistration, and termination with the serving BS. These are shown in Figure 2 and Figure 3.
Figure 2: Handover decision, handover initiation, and ranging procedures.


Figure 3: Authorization and registration procedure.

Add a Note HereWhen the MS migrates from its serving BS to its target BS, the following process is executed. First, the MS conducts cell reselection based on the information obtained from the network topology acquisition stage. The handover decision and the handover initiation can be originated by both MS and BS using the MOB_MSHO-REQ/MOB_BSHO-REQ message. When the target BS is decided, the MS sends a MOB_HO-IND message to the serving BS and the actual handover process begins as illustrated in Figure 2.
Add a Note HereIn the ranging process, the MS can synchronize to the DL of the target BS and obtain DL and UL parameters using the DCD/UCD message. Then RNG_REG/RNG_RSP messages are exchanged to complete the initial ranging process. It may be done in a contention-based or non-contention-based manner.
Add a Note HereIf the RNG_REG contains the serving BSID, the target BS can obtain the MS information from the serving BS through the backbone network. If the MS is already associated with the target BS at the previous stage, some steps may be omitted. Therefore, the neighboring BS scanning and association should be done right after the handover initiation by utilizing preobtained information before the channel condition changes.
Add a Note HereIf all physical parameter adjustments are done successfully, the network re-entry process is initiated. Figure 3 shows this procedure. It includes MS authorization and new BS registration. The target BS requests MS authorization information via its backbone network. The new BS registration is performed by REG_REQ and REG_RSP messages. This includes capabilities negotiation, MS authorization, key exchange, and registration. After successful registration with the target BS, the MS can send a MOB_HO-IND message to the serving BS to indicate that handover is completed.

Sunday, May 2, 2010

The Handover Process | WiMAX


Add a Note HereThe 802.16 standard states that the handover decision algorithm is beyond its scope. The WiMAX Forum documents do not select a handover algorithm either. Only the framework is defined. The MS, using its current information on the neighbour BS or after a request to obtain such information, evaluates its interest in a potential handover with a target BS. Once the handover decision is taken by either the serving BS or the MS, a notification is sent over the MOB_BSHO-REQ (BS Handover REQuest) or the MOB_MSHO-REQ (MS Handover REQuest) MAC management messages, depending on the handover decision maker: the BS or MS. The handover process steps are described in the following.
Add a Note HereThe handover process is made of five stages which are summarized in Figure 1. The HO process stages are described in the following sections


Figure 1: Illustration of handover process stages.

Add a Note Here
1: Cell Reselection
Add a Note HereCell reselection refers to the process of an MS scanning and/or association with one or more BS in order to determine their suitability, along with other performance considerations, as a handover target. The MS may use neighbour BS information acquired from a decoded MOB_NBR-ADV message or may make a request to schedule scanning intervals or sleep intervals to scan, and possibly range, the neighbour BS for the purpose of evaluating the MS interest in the handover to a potential target BS.

Add a Note Here2: Handover Decision and Initiation
Add a Note HereA handover begins with a decision for an MS to make a handover from a serving BS to a target BS. The decision may originate either at the MS or the serving BS. The handover decision results in a notification of MS intent to make a handover thruugh the MOB_MSHO-REQ (MS HO REQuest) message (handover decision by the MS) or the MOB_BSHO-REQ (BS HO REQuest) message (handover decision by the BS).
Add a Note HereThe BS may transmit a MOB_BSHO-REQ message when it wants to initiate a handover. This request may be recommended or mandatory. In the case where it is mandatory, at least one recommended BS must be present in the MOB_BSHO-REQ message. If mandatory, the MS responds with the MOB_HO-IND message, indicating commitment to the handover unless the MS is unable to make the handover to any of the recommended BSs in the MOB_ BSHO-REQ message, in which case the MS may respond with the MOB_HO-IND message with proper parameters indicating HO reject. An MS receiving the MOB_BSHO-REQ messsage may scan recommended neighbour BSs in this message.
Add a Note HereIn the case of an MS initiated handover, the BS transmits an MOB_BSHO-RSP message upon reception of the MOB_MSHO-REQ message.

Add a Note Here3: Synchronisation to a Target BS Downlink
Add a Note HereSynchronisation to a target BS downlink must be done. If the MS had previously received a MOB_NBR-ADV (MAC management) message including a target BSID, physical frequency, DCD and UCD, this process may be shortened. If the target BS had previously received hanndover notification from a serving BS over the backbone, then the target BS may allocate a non-contention-based initial ranging opportunity.

Add a Note Here4: Ranging and Network Re-entry
Add a Note HereThe MS and the target BS must conduct handover ranging. Network re-entry proceeds from the initial ranging step in the Network Entry process: negotiate basic capabilities, PKM authentication phase, TEK establishment phase, registration (the BS may send an unsolicited REG-RSP message with updated capabilities information or skip the REG-RSP message when there is no TLV information to be updated) and the other following Network Entry optional steps (lP connectivity, etc.).
Add a Note HereNetwork re-entry may be shortened by target BS possession of MS information obtained from the serving BS over the backbone network. Depending on the amount of that information, the target BS may decide to skip one or several of the Network Entry steps (Figure 2). Handover ranging can then be a simplified version of initial ranging. To notify an MS seeking handover of possible omission of re-entry process management messages during the current handover attempt (due to the availability of MS service and operational context information obtained over the backbone network), the target BS must place, in the RNG-RSP message, an HO Process Optimisation TLV indicating which re-entry management messages may be omitted. The MS completes the processing of all indicated messages before entering Normal Operation with the target BS.


Figure 2: Summary of network re-entry steps
Add a Note Here
Add a Note HereRegardless of having received MS information from a serving BS, the target BS may request MS information from the backbone network.

Add a Note Here5: Termination of MS Context
Add a Note HereThis is the final step of a handover. Termination of the MS context is defined as the serving BS termination of the context of all connections belonging to the MS and the discarding of the context associated with them, i.e. information in queues, ARQ state machine, counters. timers, header suppression information. etc. This is accomplished by sending the MOB__HO-IND message with the HO_IND_type value indicating a serving BS release.

Add a Note Here6: Handover Cancellation
Add a Note HereAn MS may cancel HO at any time prior to expiration of the Resource_Retain_Time interval after transmission of the MOB_HO-IND message. Resource_Retain_Time is one of the parameters exchanged during the registration procedure (part of Network Entry). The standard indicates that Resource_Retain_Time is a multiple of 100 milliseconds and that 200 milliseconds is recommended as default.



Tuesday, April 20, 2010

Mobility, Handover and Power-Save Modes

Handover Considerations

Add a Note HereOne of the major goals of the 802.16e amendment is to introduce mobility in WiMAX. Consequently, mobile WiMAX profiles are based on 802.16e. Mobility is based on handover. Handover operation (sometimes also known as ‘handoff’) is the fact that a mobile user goes from one cell to another without interruption of the ongoing session (whether a phone call. data session or other). The handover can be due to mobile subscriber moves, to radio channel condition changes or to cell capacity considerations. Handover is a mandatory feature of a cellular network. The handover (HO) is described as defined in 802.16e.

Add a Note HereIn 802.16e, the two known generic types of handover are defined:
§  Add a Note HereHard handover, also known as break-before-make. The subscriber mobile station (MS) stops its radio link with the first BS before establishing its radio link with the new BS. This is a rather simple handover.
§  Add a Note HereSoft handover, also known as make-before-break. The MS establishes its radio link with a new BS before stopping its radio link with the first BS. The MS may have two or more links with two or more BSs, which gives the soft handover state. The soft handover is evidently faster than the hard handover.

Add a Note HereTwo types of soft handover are then defined in 802.16e:
§  Add a Note HereFast BS Switching (FBSS). This is a state where the MS may rapidly switch from one BS to another. The switch is fast because the MS makes it without realising the complete network entry procedure with regard to the new BS.
§  Add a Note HereMacro Diversity HandOver (MDHO). Transmissions are between the MS and more than one BS.

Add a Note HereIn the mobile WiMAX profiles, only the hard handover is mandatory. The FBSS and MDHO are optional. The 802.16 standard also indicates that the support of the MDHO or FBSS is optional for both the MS and the BS.
Add a Note HereHandover has challenging objectives. First, it has to be fast enough, of the order of 50 ms or 150ms. There are also security requirements, as some attacks are possible at the occasion of the handover procedure. Finally, the handover does not have only Layer 2 considerations. Layer 3 considerations are also needed. Hence, the handover is not independent of the architecture.

Related Posts with Thumbnails