Patent Application
20130223408
This description relates to wireless networks.
In wireless networks, mobile stations may stop receiving service from a serving base station and begin receiving service from a target base station by handing over from the serving base station to the target base station.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.
The network 100 may include one or more wireless networks 102. Each wireless network 102 may provide wireless data service to one or more mobile stations 104. While only one mobile station 104 is shown in
The wireless network 102 may include a serving base station 106. The serving base station 106 may provide wireless (or unguided) data and/or voice service to the mobile station 104 via an air interface. The serving base station 106 may, for example, send data to the mobile station 104 in a downlink (DL) direction, and may receive data from the mobile station 104 in an uplink (UL) direction. The serving base station 106 may include a base station, relay station, node B, or access point, according to example embodiments. The serving base station 106 may be connected or coupled to the network 100 via a wired or guided connection.
The network 100 may also include a plurality of target base stations 108, 110, 112. While three target base stations 108, 110, 112 are shown in
The network 100 may also include a gateway 114. The gateway 114 may include, for example, an access service node (ASN) gateway. The gateway 114 may be connected or coupled to each of the serving base station 106 and the target base stations 108, 110, 112 via wired or guided connections. The gateway 114 may also be connected to the Internet, and may provide the serving base station 106 and target base stations 108, 110, 112 with access to the Internet; the serving base station 106 and target base stations 108, 110, 112 may provide the mobile stations 104 within their respective wireless networks 102 with access to the Internet, according to an example embodiment.
The mobile station 104 may provide data service to a user or subscriber by wirelessly (or without a guided medium) communicating with the serving base station 106 via the air interface. The mobile station 104 may include a cellular telephone, personal digital assistant (PDAs), smartphone, laptop or notebook computer, or other portable devices capable of processing data, receiving input from and providing output to a user, and communicating with the serving base station 106 via the air interface. The mobile station 104 may send data to the serving base station 106 in the uplink (UL) direction, and may receive data from the serving base station 106 in the downlink direction.
As a user of the mobile station 104 travels throughout the network 100, determinations may be made, such as by the gateway 114, the serving base station 106, and/or the mobile station 104, to hand the mobile station 104 over to one of the target base stations 108, 110, 112. The mobile station 104 and/or serving base station 106 may, for example, monitor a channel or signal quality of communication between the mobile station 104 and serving base station 106, such as by measuring and/or determining the channel-to-interference-and-noise ratio (CINR), signal-to-interference-and-noise ratio (SINR) and/or signal-to-noise ratio (SNR) of communication in the uplink and/or downlink direction between the mobile station 104 and serving base station 106. The mobile station 104 may also monitor a channel or signal quality of communication with the target base stations 108, 110, 112. The mobile station 104 may monitor the channel or signal quality of communication with the target base stations 108, 110, 112 based, for example, on pilot signals received from each of the target base stations 108, 110, 112. The mobile station 104 may monitor the channel or signal quality of communication with the target base stations 108, 110, 112 periodically, or based on the channel or signal quality of communication with the serving base station 106 dropping below a threshold level, according to example embodiments. In an example embodiment, the mobile station 104 may send the channel quality of communication with the target base stations 108, 110, 112 to the serving base station 106.
The mobile station 104 and/or serving base station 106 may compare the channel or signal quality of communication between the mobile station 104 and the serving base station 106 with the channel or signal quality of communication between the mobile station 104 and the target base stations 106, 108, 110. Based on the comparison, either the mobile station 104 or the serving base station 106 may initiate a handover.
Without an example embodiment disclosed herein, a target base station 108, 110, 112 would only set one “Action Time” (at this time (Action Time) the mobile station 104 is offered by a base station to perform a fast hand over without contention) which resulted in more fast HO (handover) failures (if the “Action Time” time limit is too short, i.e. if this time comes to soon after being announced) or in longer handover delays (if “Action Time” time is too long).
According to an example embodiment, more than one “Action Time” may be set for a mobile station 104 for at least one target base station 108, 110, 112 or for each target base station 108, 110, 112 the mobile station 104 could move to.
According to an embodiment of the invention, one or more action times can be used for each target base station 108, 110, 112. These multiple action time values may be signalled from a target base station 108, 110, 112 to a serving base station 106 in a R6/R4 HO_Rsp signal (TBD in NWG Rel1 Ver 1.2). Signalling of these multiple action time values from the serving base station 106 to a mobile station 104 can be done across a R1 interface in, e.g. a MOB_BSHO-RSP message or in a MOB_BSHO-REQ (TBD in 802.16e-Rev2) message for mobile-triggered or network-triggered handover respectively. A target base station 108, 110, 112 may stop the broadcast of fast ranging opportunities for a particular mobile station 104 if that mobile station 104 has succeeded in using one opportunity. A target base station 108, 110, 112 may stop the broadcast of fast ranging opportunities for a particular mobile station 104 if that mobile station 104 has reverted to a conventional contention-based ranging for hand-over process.
According to example embodiments, action times may be signalled either as a list of discrete action times, as a list of pairs (T-BS ID, Action Time) where the same T-BS ID may show up in more than one pair, as a list of bursts, each being denoted by the start instant and number of instances, or as a list of bursts each being denoted by the start of burst, end of burst and the frequency of action times. The broadcast of fast ranging opportunities may follow standardized formula (in 802.16e-Rev2), e.g., exponentially-growing inter-Action Time spacing, etc. and the size.
Based on determining to initiate the handover, the mobile station 104 may send a handover request message 202 to the serving base station 106. The handover request message 202 may, for example, indicate which target base station(s) 108, 110, 112 the mobile station 104 is interested in handing over to.
In response to receiving the handover request message 202 from the mobile station 104, the serving base station 106 may send backhaul network handover request messages 204A, 204B, 204C to each of the target base stations 108, 110, 112 that were indicated by the mobile station 104 in the handover request message 202. The serving base station 106 may send the backhaul network handover request messages 204A, 204B, 204C to the target base stations 108, 110, 112 via the backhaul network, such as via the wired or guided connections in the network 100, and/or via the gateway 114. In an example in which the network 100 includes relay stations, any or all of the backhaul network handover request messages 204A, 204B, 204C may be sent wirelessly via an air interface for one or more of their respective hops. The backhaul network handover request messages 204A, 204B, 204C may identify themselves as such, may identify the mobile station 104 to be handed over, may identify the location of the mobile station 104 to be handed over, may indicate the channel or signal quality of the mobile station 104 with the target base station 108, 110, 112 to which the backhaul network handover request message 204A, 204B, 204C is sent, may indicate whether the mobile station 104 supports multiple action times, and/or may include other information about the mobile station 104 to be handed over, according to example embodiments.
In an example embodiment, the handover request messages 204A, 204B, 204C may include the following fields or information elements:
O1
O1
O1
In response to receiving the backhaul network handover request messages 204A, 204B, 204C, the respective target base stations 108, 110, 112 may determine whether they can provide a fast ranging opportunity for the mobile station 104 to send a fast ranging request upon entry into their respective wireless networks, or whether the mobile station 104 will have to make a contention-based request. The target base stations 108, 110, 112 may determine whether they can provide the fast ranging opportunity to the mobile station 104 based at least in part, for example, on the information included in the backhaul network handover request messages 204A, 204B, 204C, and/or based on information such as the number of mobile stations already served by the target base station 108, 110, 112 and/or the volume of data traffic served by the target base station 108, 110, 112.
If the target base stations 108, 110, 112 determine that they can provide the fast ranging opportunity to the mobile station 104, then an action time 222, 224, 226, 228, 230, 232 may be determined. The action time 222, 224, 226, 228, 230, 232 may be determined by the respective target base stations 108, 110, 112, by the serving base station 106, or by the gateway 114, according to example embodiments. The action time 222, 224, 226, 228, 230, 232 may be a time after which the target base station 108, 110, 112 may send an uplink map to the mobile station 104. The action time 222, 224, 226, 228, 230, 232 may, for example, be a time when the target base station 108, 110, 112 may dedicate a time slot to send an uplink map to the mobile station 104. The uplink map may indicate when the mobile station 104 may send a ranging request to one or more of the target base station 108, 110, 112 in response to the fast ranging opportunities, so that the mobile station 104 does not need to engage in contention-based ranging.
In an example embodiment, the action time 222, 224, 226, 228, 230, 232 may be the number of frames until the target base station 108, 110, 112 will allocate a dedicated transmission opportunity for the mobile station 104 to transmit a ranging request message using a fast ranging information element. The dedicated transmission opportunity may allow the mobile station 104 to transmit the ranging request with channel parameters that were provided to the mobile station 104 for the target base station 108, 110, 112 before the handover, and which stay valid and can be reused during network re-entry by the mobile station 104 into the wireless network served by the target base station without CDMA-based ranging. The serving base station 106 may determine a final action time 222, 224, 226, 228, 230, 232 based on information obtained by the serving base station 106 from the target base stations 108, 110, 112 over the backbone network 100.
While two action times 222, 224, 226, 228, 230, 232 are shown for each target base station 108, 110, 112 in
The target base stations 108, 110, 112 may each send backhaul network handover response messages 206A, 206B, 206C to the serving base station 106. The backhaul network handover response messages 206A, 206B, 206C may be based on the determination of whether the target base station 108, 110, 112 can provide the fast ranging opportunity to the mobile station 104, and may be based on the determination of the action time. The backhaul network handover response messages 206A, 206B, 206C may, for example, indicate whether the respective target base station 108, 110, 112 can provide the fast ranging opportunity to the mobile station 104, and may indicate the action time. In an example embodiment, one or more of the backhaul network handover response messages 206A, 206B, 206C may indicate more than one action time after which the respective target base station 108, 110, 112 can send the uplink map to the mobile station 104. One or more, or all, of the backhaul network handover response messages 206A, 206B, 206C may indicate whether the sending target base station 108, 110, 112 supports multiple action times.
In an example in which one or more of the target base stations 108, 110, 112 may have two or more available action times 222, 224, 226, 228, 230, 232, one or more of the backhaul network handover response messages 206A, 206B, 206C may include at least two action times 222, 224, 226, 228, 230, 232. In an example in which each of the target base stations 108, 110, 112 may have two or more available action times 222, 224, 226, 228, 230, 232, each of the backhaul network handover response messages 206A, 206B, 206C may include at least two action times 222, 224, 226, 228, 230, 232. While two action times 222, 224, 226, 228, 230, 232 have been discussed herein, any number of action times 222, 224, 226, 228, 230, 232 may be included in the backhaul network handover response messages, according to various example embodiments.
In an example embodiment, the backhaul network handover response messages may include the following fields or information elements:
The serving base station 106 may receive the backhaul network handover response messages 206A, 206B, 206C from some or all of the target base stations 108, 110, 112. The serving base station 106 may determine whether each of the target base stations 108, 110, 112 is capable of providing the fast ranging opportunity to the mobile station 104, and, for each of the target base stations 108, 110, 112 which is capable of providing the fast ranging opportunity to the mobile station 104, the serving base station 106 may determine the action time after which the target base station 108, 110, 112 can send the uplink map to the mobile station 104. The serving base station 106 may determine whether the target base stations 108, 110, 112 are capable of providing the fast ranging opportunity and/or the action time based on the received backhaul network handover response messages 206A, 206B, 206C.
In an example in which one or more of the backhaul network handover response messages 206A, 206B, 206C include two or more action times 222, 224, 226, 228, 230, 232, the serving base station 106 may select one or more action times 222, 224, 226, 228, 230, 232 per target base station from the action times 222, 224, 226, 228, 230, 232 included in the backhaul network handover response messages 206A, 206B, 206C. The serving base station 106 may, for example, select one action time 222, 224, 226, 228, 230, 232 per target base station 108, 110, 112 from the action times included in the backhaul network handover response messages 206A, 206B, 206C. In an example embodiment, the serving base station 106 may select, for each target base station, the lowest action time 222, 224, 226, 228, 230, 232 included in the backhaul network handover response message by that target base station 108, 110, 112. Thus, in the example shown in
In an example embodiment, the serving base station 106 may select a generic action time from all of the action times 222, 224, 226, 228, 230, 232 included in the backhaul network handover response messages 206A, 206B, 206C. The serving base station 106 may select the generic action time in embodiments in which each backhaul network handover response message 206A, 206B, 206C includes a single action time 222, 224, 226, 228, 230, 232, as well as in embodiments in which one or more, or all of the backhaul network handover response messages 206A, 206B, 206C include more than one action time 222, 224, 226, 228, 230, 232. In an example embodiment, the serving base station 106 may select as the generic action time the lowest action time 222, 224, 226, 228, 230, 232 received from the target base stations 108, 110, 112 in the backhaul network handover response messages 206A, 206B, 206C.
In an example embodiment, the serving base station 106 may not receive all of the backhaul network handover response messages 206A, 206B, 206C at the same time. In an example embodiment, the serving base station 106 may determine whether to wait to receive backhaul network handover response messages 206A, 206B, 206C from any or all of the target base stations 108, 110, 112 from which the backhaul network handover response messages 206A, 206B, 206C have not been received, or to send a handover message (such as a handover response message or a handover request message) to the mobile station 104 without receiving backhaul network handover response messages 206A, 206B, 206C from all of the target base stations 108, 110, 112 to which backhaul network handover request messages 204A, 204B, 204C were sent. If the serving base station 106 determines to send the handover message without receiving backhaul network handover response messages 206A, 206B, 206C from all of the target base stations 108, 110, 112, the serving base station 106 may assume that the target base station(s) 108, 110, 112 from which backhaul network handover response message(s) 106A, 206B, 206C were not received are not capable of providing a fast ranging opportunity to the mobile station 104.
The determination of whether the wait for the remaining target base station(s) 108, 110, 112 to send its respective backhaul network handover response message 206A, 206B, 206C may be based on the action time indicated by one, at least one, some, or all of the target base station(s) 108, 110, 112 from which the backhaul network handover response message(s) 206A, 206B, 206C were received. The serving base station 106 may determine whether to wait for the remaining target base station(s) 108, 110, 112 based on policy such as whether waiting would still allow the mobile station 104 to receive the uplink map, or whether waiting would cause the mobile station 104 to miss the indicated action time during which the uplink map would be sent. For example, if the indicated action time is a long time away, then the serving base station 106 may wait to receive the unreceived backhaul network handover response message(s) 206A, 206B, 206C, but if the indicated action time is a short time away, then the serving base station 106 may not wait to receive the unreceived backhaul network handover response message(s) 206A, 206B, 206C. Or, the time which the serving base station 106 will wait may be based on one or more of the indicated action times, such as the shortest action time. The serving base station 106 may, for example, wait the maximum possible time to receive backhaul network handover response messages 206A, 206B, 206C while still allowing the target base station(s) to provide the fast ranging opportunity to the mobile station 104.
The serving base station 106 may send a handover message 208 to the mobile station 104. In an example in which the mobile station 104 initiated the handover process by sending the handover request 202 to the serving base station 106, the handover message 208 may include a handover response message. In an example in which the serving base station 106 initiates the handover process, and the mobile station 104 has not sent the handover request 202 to the serving base station 106, the handover message 208 may include a handover request message.
The handover message 208 may indicate whether each of the plurality of target base stations 108, 110, 112 is capable of providing the fast ranging opportunity for the mobile station 104. The handover message 208 may also indicate, for each of the target base stations 108, 110, 112 which is capable of providing the fast ranging opportunity, the action time after which the respective target base station 108, 110, 112 can send the uplink map to the mobile station 104. In an example in which one or more of the backhaul network handover response messages 206A, 206B, 206C indicated that the respective target base station 108, 110, 112 has more than one available action time, the handover message 208 may indicate each of the action times or a subset of the action times for the respective target base station 108, 110, 112. The handover message 208 may, for example, include the action times 222, 224, 226, 228, 230, 232 selected by the serving base station 106 from among the action times 222, 224, 226, 228, 230, 232 included in the backhaul network handover response messages 206A, 206B, 206C. The serving base station 106 may, for example, have selected one, or one or more, action times 222, 224, 226, 228, 230, 232 per target base station 108, 110, 112. The handover message 208 may also include the generic action time selected by the serving base station 106. In example embodiments, the action time may be pre-negotiated, hard-coded, and/or randomly determined.
In an example embodiment, the handover message 208 may indicate whether each of the target base stations 108, 110, 112 is capable of providing a fast ranging opportunity to the mobile station 104 by including a zero (0) in an action time field to indicate that the respective target base station 108, 110, 112 is not capable of providing the fast ranging opportunity, or by including a non-zero value in the action time field to indicate that the respective target base station 108, 110, 112 is capable of providing the fast ranging opportunity. The non-zero value in the action time field may also indicate the action time after which the target base station 108, 110, 112 can send the uplink map to the mobile station 104. Thus, in this example, the handover message 208 may include an action time field for each of the target base stations 108, 110, 112. The handover message 208 may also include a target base station identifier field identifying the respective target base station 108, 110, 112. The action time fields may be associated with their respective target base station identifier fields according to predetermined protocols, such as the target base station identifier field immediately preceding the action time field with which the target base station identifier field is associated, or the target base station identifier fields being in a same order within the handover message 208 as their respective action time fields. The action time fields may serve two purposes: to indicate whether the target base station 108, 110, 112 can provide the fast ranging opportunity (by including either a zero or non-zero value), and, if the target base station 108, 110, 112 can provide the fast ranging opportunity, to indicate the action time (or action times) 222, 224, 226, 228, 230, 232 after which the target base station 108, 110, 112 can send the uplink map to the mobile station 104.
In an example embodiment, the handover message 208 may include specific action times according to the target base stations 108, 110, 112 that the mobile station 104 has indicated interest in by including them in the handover request message to increase the likelihood of successful fast ranging at a target base station 108, 110, 112. In this case, the serving base station 106 may include the “Additional Action Time” TLV in the handover message 208 that the mobile station 104 may use in addition to the action time indicated in the handover message 208. If this TLV is not present in the message, then the single Action Time value may apply.
The order of Additional Action Time may match the order of Neighbor BSID (which may identify the target base station 108, 110, 112) listed in the message. A value of zero may indicate that no fast ranging is possible with the particular target base station 108, 110, 112.
If seamless handover is used, as described below with reference to
The serving base station 106 may also send a handover acknowledgment 210A, 210B, 210C to each of the target base stations 108, 110, 112 from which the serving base station 106 received handover response messages 206A, 206B, 206C. While
In an example in which the serving base station 106 selected a generic action time from the action times 222, 224, 226, 228, 230, 232 included in the backhaul network handover response messages 206A, 206B, 206C, the handover acknowledgment messages 210A, 210B, 210C may include the generic action time selected by the serving base station 106. In an example in which one or more of the backhaul network handover response messages 206A, 206B, 206C included more than one action time 222, 224, 226, 228, 230, 232, and the serving base station 106 selected one or more action times 222, 224, 226, 228, 230, 232 per target base station 108, 110, 112, the respective handover acknowledgments 210A, 210B, 212C may include, for the respective target base station 108, 110, 112 to which the handover acknowledgment 210A, 212B, 212C is sent, the action time 222, 224, 226, 228, 230, 232 selected by the serving base station 106. In various example embodiments, the handover acknowledgments 210A, 210B, 210C may also indicate a T55 parameter.
In an example embodiment, the handover acknowledgment messages 210A, 210B, 210C may include the following fields or information elements:
The mobile station 104 may receive the handover message 208. The mobile station 104 may select one of the target base stations 108, 110112 to handover to based at least in part on information included in the handover message 208. The mobile station 104 may, for example, select the target base station 108, 110, 112 with the earliest available action time, may select the target base station 108, 110, 112 with an action time which most closely coincides with the time that the mobile station 104 desires to hand over, or may consider the respective action times along with other factors, such as the mobile station's 104 proximity to the respective target base station 108, 110, 112, the channel or signal quality of the mobile station 104 with the respective target base station 108, 110, 112, or other factors. The mobile station 104 may also select an action time 218 from among the action times 222, 224, 226, 228, 232 included in the handover message 208. For example, if the handover message 208 included more than one action time 222, 224, 226, 228, 230, 232 per target base station 108, 110, 112, the mobile station 104 may select both a target base station 108, 110, 112 to handover to, as well as an action time 218.
After selecting the target base station 108, 110, 112 to hand over to, the mobile station 104 may send a handover indication message 212 to the serving base station 106. The handover indication message 212 may indicate the selected target base station 108, 110, 112 to which the mobile station 104 will hand over. The handover indication message 212 may also include one of the action times 222, 224, 226, 228, 230, 232 included in the handover message 208. In response to receiving the handover indication message 212 from the mobile station 104, the serving base station 106 may send a handover confirmation message 214 to the selected target base station 108, 110, 112. In this example shown in
In example embodiments, the serving base station 106 may send the handover confirmation message 214 to either the selected target base station 108, 110, 112, or to all the target base stations 108, 110, 112. The handover confirmation message 214 may indicate which target base station 108, 110, 112 was selected by the mobile station 104 and indicated in the handover indication message 212, and/or may indicate the selected action time 218 indicated by the handover indication message 212.
The selected target base station 110 may, in response to receiving the handover confirmation message 214, send an uplink map 216 to the mobile station 104 at the indicated action time 218. The uplink map 216 may indicate a dedicated time slot during which the mobile station 104 may send a fast ranging request 220. The mobile station 104 may, in response to receiving the uplink map 216, send the fast ranging request 220 during the dedicated time slot to the target base station 110. The mobile station 104 and the target base station 110 may thereafter wirelessly communicate via the air interface.
At 2, the mobile station 104 may initiate handover (=HO) and signal a list of candidate target base stations T-BS1 . . . T-BSn and an indication that it can do/requests to do a fast handover procedure.
At 3, the serving base station 106 may signal the request to target base stations 108, 110, 112.
At 4, the target base stations 108, 110, 112 reply to the serving base station 106 and indicate a multitude of Action Times (e.g., #1, #2, #3, #4, . . . , N) at which times respectively a fast handover is possible.
At 5, the serving base station 106 collects and forwards the list of target base stations 108, 110, 112, each with the associated lists of Action Times.
At 6, action time #1 timer expires in a target base station 108, 110, 112. It timed out too early, i.e. before a HO confirm message has been received by the target base station 108, 110, 112. The target base station 108, 110, 112 does not allocate any fast ranging opportunity for the mobile station 104 at this action time #1.
At 7, a mobile station 104 may make a decision and signal an identity of the target base station 110 selected by the mobile station 104 to the serving base station 106.
At 8, the serving base station 106 may forward this decision in a signal to the selected target base station 110.
At 9, action time #2 timer expires in the target base station 108, 110, 112.
At 10, action time #2 expired too early for the mobile station 104 to receive the UL-MAP broadcast carrying the fast ranging opportunity. The mobile station 104 is not yet ready.
At 11, action time #3 expires in the target base station 108, 110, 112.
At 12, the target base station 110 allocated fast ranging opportunity to the mobile station 104 and broadcasts it in a UL-MAP message.
At 13, the mobile station 104 may send a ranging request in the allocated fast ranging (time) slot.
At 14, the target base station 104 may reply according to a predetermined protocol, such as the WiMax standard.
At 15, subsequent action time timers may expire in the target base station 108, 110, 112 but no fast ranging opportunity is allocated or broadcast since the target base station 108, 110, 112 is already aware of the mobile station 104 having used the opportunity #3.
Example embodiments described herein may allow for multiple action times for each target base station 108, 110, 112 in a fast handover procedure. These may be set to represent, e.g., fastest possible HO action time, expected fast HO action time, conservative HO action time (still faster than normal network re-entry).
A target base station 108, 110, 112 may send multiple action time opportunities for the mobile station 104 fast handover. They may be signalled via R4 and R6 interfaces in a HO_Rsp signal (TBD in NWG Rel1 Ver 1.2) from a target base station 108, 110, 112 to a serving base station 106.
Then they may be signalled via R1 e.g. in a MOB_BSHO-RSP or MOB_BSHO-REQ (TBD in 802.16e-Rev2) signal to the mobile station 104 for mobile- or network-triggered handover respectively.
Once a mobile station 104 used the first opportunity or obviously has ignored it by starting CDMA ranging (normal, slow HO), a target base station 108, 110, 112 may not give further fast ranging opportunities to that mobile station 104.
Alternative to listing action time instants, action times may be announced in bursts wherein only the first one and number of following ones are signalled.
An alternative to listing action times may be to employ a formula for distributing Action Time events after the first one, e.g., exponentially increasing inter-Action Time spacing.
Example embodiments cross a radio interface and could be standardized in IEEE 802.16e-Rev2 and/or in NWG Rel.1 CR.
In this example, the serving base station 106 may receive the backhaul network handover response messages 206A, 206B, 206C. The serving base station 106 may, based on receiving the backhaul network handover response messages 206A, 206B, 206C, determine whether each of the target base stations 108, 110, 112 is capable of performing the seamless handover with the mobile station 104, and, for those target base stations which are capable of performing the seamless handover, determine an action time after which the pre-allocated CID will be available for the seamless handover. Based on this determination, the serving base station 106 may send a handover message 208 to the mobile station 104. The serving base station 106 may also determine whether to send the handover message 106 before receiving backhaul network handover response messages 206A, 206B, 206C or to wait to receive more or all of the backhaul network handover response messages 206A, 206B, 206C based on the action times, as described with reference to
The handover message 208 may indicate to the mobile station 104 which of the target base stations 108, 110, 112 are capable of performing the seamless handover with the mobile station 104 using pre-allocated CIDs, and, for those that are capable, an action time at which the pre-allocated CID(s) are available for the seamless handover. The handover message 208 may include action time fields indicating the action time for each of the target base stations 108, 110, 112, as described with reference to
The serving base station 106 may send handover acknowledgments 210A, 210B, 210C to the target base stations 108, 110, 112 from which the serving base station 106 received backhaul network handover responses 206A, 206B, 206C, as described with reference to
In response to receiving the handover confirmation message 214, the selected target base station 110 may, at the action time (or later, if the selected target base station 110 did not receive the handover confirmation message 214 soon enough), send an uplink grant 302, and/or unicast encrypted downlink data, to the mobile station 104. The target base station 110 may send the uplink grant 302 and/or unicast encrypted downlink data to the mobile station 104 based on the pre-allocated CID. In response to receiving the uplink grant 302 and/or unicast encrypted downlink data, the mobile station 104 may send uplink data 304, which may be unicast and/or encrypted, and/or a bandwidth request, to the target base station, using the pre-allocated CID. The mobile station 104 may also send a fast ranging request 306 to the target base station 110 according to the uplink grant 302. The target base station 110 may, in response to receiving the fast ranging request 306, send a ranging response 308 to the mobile station 104. The mobile station 104 may respond to the ranging response 308 by sending a bandwidth request 310 to the target base station 110 requesting allocation of bandwidth, completing the seamless handover.
In some cases, not all mobile stations 104 will support handovers according to the processes described above. Thus, a legacy mobile station may not support the inclusion of multiple action times in a handover message 208, or even be aware of this feature. When such a legacy mobile station enters a network or cell that is using this feature, this may create problems in some cases, especially if the serving base station 106 does not know whether the mobile station 104 supports this feature. Thus, according to an example embodiment, as described below with reference to at least
The capabilities exchange 412 may include the mobile station 104 transmitting or providing a list of its capabilities to the serving base station 106, e.g., via a capability request message, such as an IEEE 802.16 subscriber station basic capability (SBC) request message (SBC-REQ), 414, or other message. The SBC-REQ message may include a multiple action time flag (e.g., within an extended capability field of SBC-REQ message 414) that indicates whether or not the mobile station 104 supports inclusion of multiple action times or action times within the handover message 208. For example, setting this multiple action times flag to 1 in the SBC-REQ message 414 may indicate that the mobile station 104 supports multiple action times, and clearing this bit to zero indicates that this feature is not supported by the mobile station 104. The lack of an explicit capability request message containing a multiple action times flag may indicate that this feature is not supported by the mobile station 104. Thus, according to an example embodiment, when mobile station 104 indicates that it supports this feature, and connects to a serving base station 106 that uses or implements this feature, the mobile station 104 may then initiate handover only according to a procedure that may include multiple action times within the handover message 208.
Similarly, although not required, the serving base station 106 may send the mobile station 104 a list of its capabilities, e.g., via a capability message, such as a subscriber station basic capability response (SBC-RSP) message 416. The SBC-RSP message 416 may include a multiple action time flag (e.g., within an extended capability field of SBC-RSP 416) that indicates whether or not the serving base station 106 supports multiple action times. For example, setting this flag to 1 in the SBC-RSP message 416 may indicate that the serving base station 106 supports this feature, and clearing this bit to zero indicates that this feature is not supported by the serving base station 106. Thus, according to one example embodiment, multiple action times may be implemented between a serving base station 106 and a mobile station 104 only if both serving base station 106 and mobile station 104 have indicated capability for such feature via capability messages or other messages exchanged between the serving base station 106 and mobile station 104. According to another example embodiment, multiple action time may also be implemented even if some mobile stations are not capable of supporting such feature.
The capabilities exchange 412 may include both messages 414 and 416 in one embodiment (2-way exchange, where both mobile station 104 and serving base station 106 indicate their ability to support multiple action times), or may just include SBC-REQ message 414 (e.g., 1-way communication indicating mobile station's 104 capability to support multiple action times). Thus, in one example embodiment, it may be optional, for example, whether the serving base station 106 sends the message indicating the serving base station's 106 support for this feature, e.g., via the SBC-RSP 416. Thus, SBC-RSP message 416 may be omitted, in an example embodiment. In this case, according to an example embodiment, the mobile station 104 may assume that the serving base station 106 supports multiple action times unless specifically informed otherwise (e.g., via the SBC-RSP message with multiple action times flag set to 0 indicating no support for this feature).
A serving base station 106 may, in some cases, transmit or broadcast a message(s) indicating which of its capabilities are being used or turned on. Some features may be indicated as in use simply via the capabilities exchange, while other capabilities may use an additional transmission of DCD or other message to indicate that such feature is actually in use by the serving base station 106. For example, serving base station 106 may transmit or broadcast a DCD (downlink channel descriptor) 422 (or other message) that includes a multiple action time field, e.g., set to 1, to indicate that the serving base station 106 is using (or enforcing or implementing) the multiple action time feature, or in other words, that this feature is turned on or in use by the serving base station 106. Since this DCD broadcast may occur at any time, e.g., before and/or after the ranging, capabilities exchange, authentication and registration, and may occur from time to time, the mobile station 104 may acquire the knowledge that the serving base station 106 is capable of supporting the multiple action time feature even before the capability exchange messages. However the lack of a multiple action time field in the broadcast message or the value set to 0 does not necessarily mean the serving base station 106 is not capable of supporting the multiple action time feature. While the DCD 422 may indicate use of the multiple action time, such a broadcast does not inform the serving base station 106 of whether or not the mobile station 104 actually supports multiple action times. Thus, the capabilities exchange, including a message (e.g., SBC-REQ 414) sent from the mobile station 104 may be used to inform the serving base station 106 of whether or not the mobile station 104 supports the multiple action times.
According to an example embodiment, based on the capabilities information provided by the mobile station 104 (e.g., via SBC-REQ message 414) indicating whether or not the mobile station 104 supports the multiple action times feature, the serving base station 106 may decide or determine whether or not to allow the mobile station 104 to continue with network entry, e.g., authentication, registration, etc. For example, the serving base station 106 may decide to reject the mobile station 104 (or prevent the mobile station 104 from completing network entry) if the serving base station 106 is requiring every mobile station 104 in its cell or network to comply with (or support) multiple action times. On the other hand, in the event that the mobile station 104 does not support multiple action times, the serving base station 106 may still decide to accept or allow the mobile station 104 to enter or join its cell or network, e.g., if the serving base station 106 is not currently using the multiple action times feature, or if the serving base station 106 has a light network load and adding a non-compliant mobile station will likely not create unacceptable network impact/delays.
For example, in response to receiving a message indicating that the mobile station 104 does not support multiple action times, the serving base station 106 may reject the mobile station 104 by the serving base station 106 transmitting to the mobile station 104 a rejection message, such as by sending a rejection message to the mobile station 104 that rejects one or more network entry related requests from the mobile station 104. The serving base station 106 may send a rejection message, such as, for example: a ranging response message indicating abort to the mobile station, which may cause the mobile station 104 to abort ranging or network entry; a ranging response message indicating downlink frequency overwrite or preamble index overwrite instructing the mobile station 104 to move to another serving base station 106; a registration response message rejecting a registration request from the mobile station 104; and an authentication response rejecting an authentication request from the mobile station 104, as some examples.
In addition, the serving base station 106 may send a message to the mobile station 104 indicating whether or not the serving base station 106 supports multiple action times, shown by way of example, as SBC-RSP message 416 in
The tables shown below illustrate examples of the multiple action times field, which may be used by a mobile station 104 or serving base station 106 to indicate support for this feature.
Extended Capability: Additional Action Times
The extended capability field may specify the extended capability support for the specified features.
The following Handover Supported field may indicate what type(s) of handover the base station (BS) and the mobile station (MS) support. A bit value of 0 indicates “not supported,” while 1 indicates it is supported.
Processor 1304 may also make decisions or determinations, generate frames or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 1304, which may be a baseband processor, for example, may generate messages, packets, frames or other signals (such as those described above) for transmission via wireless transceiver 1302. Processor 1304 may control transmission of signals or messages over a wireless network, and may receive signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1302, for example). Processor 1304 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 904 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 904 and transceiver 902 together may be considered as a wireless transmitter/receiver system, for example.
In addition, referring to
In addition, a storage medium such as the memory 1306 may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1304, or other controller or processor, performing one or more of the functions or tasks described above.
Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
Method steps may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry.
To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the embodiments of the invention.
This application is a continuation of U.S. patent application Ser. No. 12/936,115, given a filing date of on Oct. 14, 2011, entitled, “Action Times for Handover of Mobile Stations,” which was a national stage entry of PCT/IB2009/005681, filed on Apr. 3, 2009, entitled “Action Times for Handover of Mobile Stations”, which, in turn, claims the benefit of priority based on U.S. patent application Ser. No. 12/098,156, filed on Apr. 4, 2008, entitled, “Multiple Action Times in Mobile WiMAX Fast HO,” and U.S. Provisional Application No. 61/114,460, filed on Nov. 13, 2008, entitled, “Indicating Action Times and Fast Ranging Capabilities of Target Based Stations,” and U.S. Provisional Application No. 61/118,564, filed on Nov. 28, 2008, entitled, “Action Times for Handover of Mobile Stations,” the disclosures of all of which are hereby incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12936115 | Oct 2011 | US |
| Child | 13864855 | US |
