Method for compulsorily performing handover in broadband wireless communication system
Abstract
Disclosed is a method for enabling a mobile station existing in a serving cell area to perform a handover procedure in a broadband mobile communication system including the mobile station, a serving base station providing a service to the mobile station, and one or more target base stations containing at least one target cell area overlapping with the serving cell area occupied by the serving base station. The method includes transmitting a handover request message from the mobile station to the serving base station when it is detected that a performance of a handover is necessary; and transmitting a handover indication message containing handover cancel information to the serving base station when the mobile station determines a cancel of the handover while the mobile station is being handed over to one or more target base stations by the serving base station.
Term
Term ended
Projected expiry passed 6 September 2024, 2 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
46 claims: 10 independent, 36 dependent
- 1A method for a serving base station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, the serving base station providing a service to the mobile station in the serving cell area, and at least one target base station adjacent to the serving base station, the method comprising the steps of:determining a handover when the serving base station needs to make the mobile station performed the handover procedure;notifying one of the target base stations to perform the handover procedure;and transmitting a handover message to the mobile station including forced handover information signifying that the serving base station commands the mobile station to be handed over to the notified target base station.
- 7A method for handover of a mobile station located in a serving cell area of a serving base station in a broadband wireless communication system including the mobile station, the serving base station, and at least one target base station having a target cell area adjacent to the serving cell area, the serving base station providing a service to the mobile station in the serving cell area, the method comprising the steps of:receiving a message including handover information from the serving base station;confirming by the mobile station the handover information in the message, and releasing link between the mobile station and the serving base station when the message is a forced handover indication message;and performing handover toward one handover-executable target base station included in the message.
- 10A method for a mobile station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station, the method comprising the steps of:transmitting a handover request message to the serving base station when it is detected that a handover is necessary;and transmitting a handover indication message including handover cancellation information to the serving base station when the mobile station decides to cancel the handover during a time period in which the mobile station performs the handover to one of the target base stations.
- 17A method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area, the method comprising the steps of:progressing handover process between the serving base station and the target base station after receiving a handover request message from the mobile station;canceling the handover process when the serving base station has received a handover cancellation message including handover cancellation information from the mobile station while the handover process is in progress;and maintaining link between the mobile station and the serving base station after the serving base station cancels the handover process.
- 22A method for a mobile station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station, the method comprising the steps of:transmitting a handover request message to the serving base station when it is detected that a handover is necessary;receiving a first handover response message from the serving base station;and transmitting a handover indication message including handover rejection information to the serving base station when the mobile station determines a rejection of the handover after receiving the handover response message.
- 30A method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area, the method comprising the steps of:progressing handover process between the serving base station and the target base station after receiving a handover request message from the mobile station;stopping the handover process when the serving base station has received a handover rejection message including handover rejection information from the mobile station while the handover process is in progress;and transmitting a list of the target base stations from the serving base station to the mobile station after the serving base station stops the handover process.
- 35A method for a mobile station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station, the method comprising the steps of:receiving a handover request message from the serving base station and performing the handover procedure;and transmitting a handover indication message including handover cancellation information to the serving base station when the mobile station decides to cancel the handover during a time period in which the mobile station performs the handover to one of the target base stations.
- 38A method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area, the method comprising the steps of:transmitting a handover request message from the serving base station to the mobile station and progressing handover process between the serving base station and the target base station;canceling the handover process when the serving base station has received a handover cancellation message including handover cancellation information from the mobile station while the handover process is in progress;andmaintaining link between the mobile station and the serving base station after the serving base station cancels the handover process.
- 41A method for a mobile station to enable the mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station, the method comprising the steps of:receiving a handover request message including a list of the target base stations from the serving base station ;and transmitting a handover indication message including handover rejection information to the serving base station when the mobile station determines a rejection of the handover after checking the list of the target base stations.
- 45A method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area, the method comprising the steps of:transmitting a handover request message from the serving base station to the mobile station and progressing handover process between the serving base station and the target base station, the handover request message including a list of the target base stations;stopping the handover process when the serving base station has received a handover rejection message including handover rejection information from the mobile station while the handover process is in progress;and transmitting a new list of the target base stations from the serving base station to the mobile station.
Independent claims10
195 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
1.
Field of the Invention
The present invention relates to a broadband mobile communication system, and more particularly to a method for performing a handover in a broadband wireless communication system employing an orthogonal frequency division multiplexing (hereinafter, referred to as an OFDM) method and an orthogonal frequency division multiplexing access (hereinafter, referred to as an OFDMA) method.
2.
Description of the Related Art
In the fourth generation (hereinafter, referred to as a 4G) communication system, which is the next generation communication system, research has been actively pursued to provide users with services having various quality of services (hereinafter, referred to as a QoSs) and supporting a transmission speed of about 100 Mbps. The current third generation (hereinafter, referred to as a 3G) communication system supports a transmission speed of about 384 kbps in an outdoor channel environment having a relatively unfavorable channel environment, and supports a transmission speed of 2 Mbps at maximum even in an indoor channel environment having a relatively favorable channel environment.
Meanwhile, wireless local area network (hereinafter, referred to as a LAN) system, and a wireless metropolitan area network (hereinafter, referred to as a MAN) systems generally support transmission speeds of 20 to 50 Mbps. Accordingly, in the current 4G communication system, research has been actively pursued to develop a communication system to ensure mobility and QoS in the wireless LAN system and the wireless MAN system supporting relatively high transmission speeds, and to support a high speed service which will be provided by the 4G communication system.
Since the wireless MAN system has a wide service coverage and supports a high transmission speed, it is suitable for supporting a high speed communication service. However, because the wireless MAN system is a system which does not completely consider the mobility of a subscriber station (SS), a handover due to the high-speed movement of a subscriber station is also not considered. Herein, the wireless MAN system is a broadband wireless access (BWA) communication system, and it has a service coverage area which is largerthan that which the wireless LAN system provides and, additionally, supports a transmission speed higher than that which the wireless LAN system provides.
A system employing an OFDM method and an OFDMA method in order to enable a physical channel of the wireless MAN system to support a broadband transmission network is known as an IEEE (Institute of Electrical and Electronics Engineers) 802.16a communication system. The IEEE 802.16a communication system is a broadband wireless access communication system employing an OFDM/OFDMA method. Further, since the IEEE 802.16a communication system applies an OFDM/OFDMA method to the wireless MAN system, the IEEE 802.16a communication system transmits a physical channel signal using a plurality of sub-carriers, thereby enabling a high speed data transmission. Therefore, the IEEE 802.16a communication system is called a broadband wireless access communication system.
Hereinafter, the structure of the conventional IEEE 802.16a communication system will be descried with reference to FIG. 1.
FIG. 1 is a block diagram schematically showing the structure of the IEEE 802.16a communication system. The IEEE 802.16a communication system has a single cell structure and includes a base station (BS) 100 and a plurality of subscriber stations 110, 120, and 130 controlled by the base station 100. The transmission/reception of signals between the base station 100 and the subscriber stations 110, 120, and 130 are accomplished through the OFDM/OFDMA method.
Hereinafter, the structure of the downlink frame of the conventional IEEE 802.16a communication system will be descried with reference to FIG. 2 which is a view which illustrates the structure of the downlink frame of the IEEE 802.16a communication system.
Referring to FIG. 2, the downlink frame of the IEEE 802.16a communication system includes a preamble portion 200, a broadcast control portion 210, and a plurality of time division multiplex (hereinafter, referred to as a TDM) portions 220 and 230. A synchronization signal (i.e., preamble sequence) used in obtaining a mutual synchronization between a base station and a subscriber station is transmitted through the preamble portion 200. The broadcast control portion 210 includes a downlink (hereinafter, referred to as a DL) portion DL-MAP 211 and an uplink (hereinafter, referred to as an UL) portion UL-MAP 213. The DL_MAP portion 211 is a portion through which a DL_MAP message is transmitted. Table 1 shows information elements (hereinafter, referred to as IEs) contained in the DL_MAP message. <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">DL_MAP_Message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Management Message Type=2</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">PHY Synchronization Field</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="center">See Appropriate PHY specification</entry></row><row><entry namest="col1" nameend="col1" align="left">DCD Count</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Base Station ID</entry><entry namest="col2" nameend="col2" align="left">48 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Number of DL MAP Element n</entry><entry namest="col2" nameend="col2" align="left">16 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Begin PHY specific section {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" align="center">See Applicable PHY section</entry></row><row><entry namest="col1" nameend="col1" align="left"> for (i=1; i<=n; i++) {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" align="center">For each DL MAP element 1 to n</entry></row><row><entry namest="col1" nameend="col1" align="left">DL_MAP Information Element()</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="center">See corresponding PHY specification</entry></row><row><entry namest="col1" nameend="col1" align="left"> If! (byte boundary) { Padding Nibble</entry><entry namest="col2" nameend="col2" align="left">4 bits</entry><entry namest="col3" nameend="col3" align="center">Padding to reach byte boundary</entry></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 1, the DL_MAP message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, the 'PHYsical (PHY) Synchronization' set according to a modulation method and a demodulation method applied to a physical channel in order to obtain a synchronization, the 'DCD count' representing a count corresponding to the configuration variation of a downlink channel descript (hereinafter, referred to as a DCD) message containing a downlink bust profile, the 'Base Station ID' representing a base station identifier (BSID), and the 'Number of DL_MAP Elements n' representing the number of elements existing after the Base Station ID. Especially, the DL_MAP message contains information on ranging codes assigned to each ranging which will be described later.
Further, the UL_MAP portion 213 is a portion through which an UL_MAP message is transmitted. Table 2 shown below illustrates IEs contained in the UL MAP message. <tables id="tabl0002" num="0002"><table frame="all"><title>Table 2</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">UL_MAP Message_Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center">Management Message Type=3</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center">Uplink Channel ID</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center">UCD Count</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center">Number of UL MAP Element n</entry><entry namest="col2" nameend="col2" align="left">16 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center">Allocation Start Time</entry><entry namest="col2" nameend="col2" align="left">32 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center">Begin PHY specific section {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" align="center">See Applicable PHY section</entry></row><row><entry namest="col1" nameend="col1" align="center">for (i=1; i<=n; i++) {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" align="center">For each UL MAP element 1 to n</entry></row><row><entry namest="col1" nameend="col1" align="center">UL_MAP_Information_Element()</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="center">See corresponding PHY specification</entry></row><row><entry namest="col1" nameend="col1" align="center"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="center"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 2, the UL_MAP message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, the 'Uplink Channel ID' representing a used uplink channel identifier, the 'UCD count' representing a count corresponding to the configuration variation of an uplink channel descript (hereinafter, referred to as an UCD) message containing an uplink bust profile, and the 'Number of UL_MAP Elements n' representing the number of elements existing after the UCD count. Herein, the uplink channel identifier is uniquely assigned in a media access control (hereinafter, referred to as a MAC) sub-layer.
Further, the TDM portions 220 and 230 (as shown in FIG. 2) are portions corresponding to time slots assigned to each subscriber station by a time division multiplexing (hereinafter, referred to as a TDM) time division multiple access (hereinafter, referred to as a TDMA) TDM/TDMA method. The base station transmits broadcast information, which must be broadcasted, to subscriber stations managed by the base station through the DL_MAP portion 211 of the downlink frame by means of a preset center carrier. Then, each of the subscriber stations is powered on and the base station then monitors all frequency bands set in each of the subscriber stations in advance, and detects a pilot channel signal having the highest pilot carrier to interference and noise ratio (hereinafter, referred to as a CINR).
Also, the subscriber station determines a base station having transmitted the pilot channel signal having the highest CINR to be a base station to which the subscriber station currently belongs. Further, the subscriber station confirms the DL_MAP portion 211 and the UL_MAP portion 213 of the downlink frame transmitted by the base station, and confirms control information controlling an uplink and a downlink of the subscriber station and information representing an actual position of data transmission/reception.
Table 3, illustrated below, shows the structure of the UCD message. <tables id="tabl0003" num="0003"><table frame="all"><title>Table 3</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">UCD-message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=0</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Uplink Channel ID</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Configuration Change Count</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Mini-slot size</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Ranging Backoff Start</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Ranging Backoff End</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Request Backoff Start</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Request Backoff End</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> TLV Encoded Information for the overall channel</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Begin PHY Specific Section {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> for(i=1; i<=n; I+n) {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Uplink Burst Descriptor</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 3, the UCD message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, the 'Uplink Channel ID' representing a used uplink channel identifier, the 'Configuration Change Count' counted by a base station, the 'Mini-slot Size' representing the size of a mini-slot of an uplink physical channel, the 'Ranging Backoff Start' representing a start point of a backoff using an initial ranging, that is, the size of an initial backoff window using an initial ranging, the 'Ranging Backoff End representing an end point of a backoff using an initial ranging, that is, the size of a final backoff window, the 'Request Backoff Start' representing a start point of a backoff for 'contention data and requests', that is, the size of an initial backoff window, and the 'Request Backoff End representing an end point of a backoff for 'contention data and requests', that is, the size of a final backoff window.
Herein, the value of the backoff represents a kind of waiting time value for which a subscriber station must wait for the next ranging when failure occurs in rangings which will be described later. Further, a base station must transmit the backoff value, which is information on a time period for which the subscriber station must wait for the next ranging, to the subscriber station when the subscriber station fails in a ranging. For instance, when a value by the Ranging Backoff Start and the Ranging Backoff End is set to be 10, the subscriber station passes a chance in which the subscriber station can perform rangings of 2<sup>10</sup> times (i.e., 1024 times) and then must perform the next ranging.
Hereinafter, the structure of the uplink frame of the conventional IEEE 802.16a communication system will be descried with reference to FIG. 3, which is a view which illustrates the structure of the uplink frame of the IEEE 802.16a communication system.
Before describing FIG. 3, rangings as described and used in the IEEE 802.16a communication system, include, an initial ranging, a maintenance ranging, that is, a periodic ranging, and a bandwidth request ranging each of which will be described in detail below.
The initial ranging is a ranging which is performed when a base station requests the initial ranging in order to obtain a synchronization with a subscriber station. Further, the initial ranging is a ranging which is performed in order to match an exact time offset between the subscriber station and the base station and adjust the transmit power. That is, the subscriber station is powered on, receives a DL_MAP message, an UL_MAP message, and a UCD message, and obtains synchronization with the base station. Then, the subscriber station performs the initial ranging to adjust the time offset and the transmit power with the base station. The base station receives the MAC address of the subscriber station from the subscriber station through the initial ranging procedure. Further, the base station generates a basic connection ID (hereinafter, referred to as a basic CID) and a primary management connection ID (hereinafter, referred to as a primary management CID) mapped with the received MAC address of the subscriber station, and then transmits the generated basic CID and the primary management CID to the subscriber station. Then, the subscriber station recognizes the basic CID and the primary management CID of the subscriber station through the initial ranging procedure.
Herein, since the IEEE 802.16a communication system employs an OFDM/OFDMA method, the ranging procedure requires ranging sub-channels and ranging codes. A base station assigns usable raging codes (RCs) according to the object of a raging, that is, the kind of a raging. This will be described in detail.
The raging code is generated by segmenting pseudo-random noise (hereinafter, referred to as a PN) sequence having a predetermined length (e.g., length of 2<sup>15</sup>-1 bits) by a predetermined unit. Generally, two sub-channels having a length of 53 bits constitute one ranging channel. Further, the raging code is constructed by segmenting a PN code through the ranging channel having a length of 106 bits. The 48 raging codes i.e., RC#1 to RC#48) (at maximum for 48 ranging codes per subscriber station) constructed in this way may be assigned to a subscriber station, and two raging codes (at minimum per a subscriber station) are applied to the three types of rangings, that is, the initial ranging, the periodic ranging and the bandwidth request ranging, according to a default value. In this way, different raging codes are assigned to each ranging. For instance, N number of raging codes are assigned for the initial ranging (N RCs for initial ranging), M number of raging codes are assigned for the periodic ranging (M RCs for periodic ranging), and L number of raging codes are assigned for the bandwidth request ranging (L RCs for BW-request ranging). The raging codes assigned in this way are transmitted to subscriber stations through the DL_MAP message as described above, and the subscriber stations perform the ranging procedure by using the raging codes contained in the DL_MAP message according to the objects of the raging code.
The periodic ranging is a ranging periodically performed when the subscriber station having adjusted the time offset and the transmit power with the base station through the initial ranging adjusts a channel status, etc., with the base station. The subscriber station performs the periodic ranging by means of the ranging codes assigned for the periodic ranging.
The bandwidth request ranging is a ranging performed when the subscriber station having adjusted the time offset and the transmit power with the base station through the initial ranging requests a bandwidth assignment in order to actually perform a communication with the base station.
Referring to FIG. 3, the uplink frame includes an 'Initial Maintenance Opportunities' portion 300 using the initial ranging, and the maintenance ranging, that is, the periodic ranging, a 'Request Contention Opportunities' portion 310 using the bandwidth request ranging, and a 'SS scheduled data' portion 320 containing the uplink data of subscriber stations. The Initial Maintenance Opportunities portion 300 includes a plurality of access burst intervals actually containing an initial ranging and a periodic ranging, and a collision interval in which collision between access burst intervals occurs. The Request Contention Opportunities portion 3 10 includes a plurality of bandwidth request intervals containing a bandwidth request ranging, and a collision interval in which collision between bandwidth request intervals occurs. Further, the SS scheduled data portion 320 includes a plurality of SS scheduled data parts (i.e., SS 1 scheduled data part to SS N scheduled data part) and a subscriber station transition gap which is present in each of the SS scheduled data parts.
An uplink interval usage code (hereinafter, referred to as a UIUC) portion which is a portion in which information designating the use of an offset recorded in an offset portion is recorded. Table 4 below shows the UIUC portion. <tables id="tabl0004" num="0004"><table frame="all"><title>Table 4</title><tgroup cols="4" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="39.37mm" /><colspec colnum="2" colname="col2" colwidth="39.37mm" /><colspec colnum="3" colname="col3" colwidth="39.37mm" /><colspec colnum="4" colname="col4" colwidth="39.37mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">IE name</entry><entry namest="col2" nameend="col2" align="center">UIUC</entry><entry namest="col3" nameend="col3" align="center">Connection ID</entry><entry namest="col4" nameend="col4" align="center">Description</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">Reserved</entry><entry namest="col2" nameend="col2" align="left">0</entry><entry namest="col3" nameend="col3" align="left">NA</entry><entry namest="col4" nameend="col4" align="left">Reserved for future use</entry></row><row><entry namest="col1" nameend="col1" align="left">Request</entry><entry namest="col2" nameend="col2" align="left">1</entry><entry namest="col3" nameend="col3" align="left">any</entry><entry namest="col4" nameend="col4" align="left">Starting offset of request region</entry></row><row><entry namest="col1" nameend="col1" align="left">Initial Maintenance</entry><entry namest="col2" nameend="col2" align="left">2</entry><entry namest="col3" nameend="col3" align="left">broadcast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of maintenance region (used in Initial Ranging)</entry></row><row><entry namest="col1" nameend="col1" align="left">Station Maintenance</entry><entry namest="col2" nameend="col2" align="left">3</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of maintenance region (used in periodic Ranging)</entry></row><row><entry namest="col1" nameend="col1" align="left">Data Grant Burst Type 1</entry><entry namest="col2" nameend="col2" align="left">4</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of Data Grant Burst Type 1 assignment</entry></row><row><entry namest="col1" nameend="col1" align="left">Data Grant Burst Type 2</entry><entry namest="col2" nameend="col2" align="left">5</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of Data Grant Burst Type 2assignment</entry></row><row><entry namest="col1" nameend="col1" align="left">Data Grant Burst Type 3</entry><entry namest="col2" nameend="col2" align="left">6</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of Data Grant Burst Type 3 assignment</entry></row><row><entry namest="col1" nameend="col1" align="left">Data Grant Burst Type 4</entry><entry namest="col2" nameend="col2" align="left">7</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of Data Grant Burst Type 4 assignment</entry></row><row><entry namest="col1" nameend="col1" align="left">Data Grant Burst Type 5</entry><entry namest="col2" nameend="col2" align="left">8</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of Data Grant Burst Type 5 assignment</entry></row><row><entry namest="col1" nameend="col1" align="left">Data Grant Burst Type 6</entry><entry namest="col2" nameend="col2" align="left">9</entry><entry namest="col3" nameend="col3" align="left">unicast</entry><entry namest="col4" nameend="col4" align="left">Starting offset of Data Grant Burst Type 6 assignment</entry></row><row><entry namest="col1" nameend="col1" align="left">Null IE</entry><entry namest="col2" nameend="col2" align="left">10</entry><entry namest="col3" nameend="col3" align="left">zero</entry><entry namest="col4" nameend="col4" align="left">Ending offset of the previous grant. Used to bound the length of the last actual interval allocation</entry></row><row><entry namest="col1" nameend="col1" align="left">Empty</entry><entry namest="col2" nameend="col2" align="left">11</entry><entry namest="col3" nameend="col3" align="left">zero</entry><entry namest="col4" nameend="col4" align="left">Used to schedule gaps in transmission</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">Reserved</entry><entry namest="col2" nameend="col2" align="left">12 to 15</entry><entry namest="col3" nameend="col3" align="left">N/A</entry><entry namest="col4" nameend="col4" align="left">Reserved</entry></row></tbody></tgroup></table></tables>
As shown in Table 4, the UIUC portion contains information designating the use of the offset recorded in the offset portion. For instance, when a value of 2 is recorded in the UIUC portion, it signifies that a starting offset used in the initial ranging is recorded in the offset portion. When a value of 3 is recorded in the UIUC portion, it signifies that a starting offset used in the maintenance ranging or the bandwidth request ranging is recorded in the offset portion. As described above, the offset portion is a portion recording a starting offset value used in the initial ranging, the bandwidth request ranging, or the maintenance ranging according to the information recorded in the UIUC portion. Further, information on a characteristic of a physical channel to be transmitted in the UIUC portion is recorded in the UCD message.
Hereinafter, a ranging process between a base station and a subscriber station in the conventional IEEE 802.16a communication system will be descried with reference to FIG. 4 which is a flow diagram illustrating the ranging process between the base station and the subscriber station in the IEEE 802.16a communication system.
Referring to FIG. 4, the subscriber station 400 is powered on, monitors all frequency bands set in the subscriber station 400 in advance, and detects a pilot channel signal having the highest CINR. Also, the subscriber station 400 determines a base station 420 having transmitted the pilot channel signal having the highest CINR to be the base station 420 to which the subscriber station 400 currently belongs. Then, the subscriber station 400 receives the preamble of the downlink frame transmitted from the base station 420 and obtains a system synchronization with the base station 420.
As described above, when the system synchronization is obtained between the subscriber station 400 and the base station 420, the base station 420 transmits a DL_MAP message and an UL_MAP message to the subscriber station 400 in steps 411 and 413, respectively. Herein, as described in Table 1, the DL_MAP message performs the function of informing the subscriber station 400 of information required when the subscriber station 400 obtains a synchronization with respect to the base station 420 in a downlink, and information on the structure of a physical channel capable of receiving messages transmitted to the subscriber station 400 in the downlink. Further, as described in table 2, the UL_MAP message performs the function of informing the subscriber station 400 of information on the scheduling period of a subscriber station and the structure of a physical channel in an uplink.
Meanwhile, the DL_MAP message is broadcasted from a base station to all subscriber stations. Herein, a case in which a certain subscriber station can continuously receive the DL_MAP message signifies that the subscriber station has synchronized with the base station. That is, the subscriber stations having received the DL_MAP message can receive all messages transmitted through a downlink. Further, as described in Table 2, when the subscriber station fails in an access, the base station transmits the UCD message containing information notifying an usable backoff value to the subscriber station.
Meanwhile, when the subscriber station 400 having synchronized with the base station 420 performs the ranging, the subscriber station 400 transmits a ranging request (hereinafter, referred to as a RNG_REQ) message to the base station 420 in step 415. Then, in step 417, the base station 420 having received the RNG_REQ message transmits a ranging response (hereinafter, referred to as a RNG_RSP) message, which contains information for compensating for frequency, time, and transmit power for the ranging, to the subscriber station 400.
Table 5 illustrated below, shows the structure of the RNG_REQ message. <tables id="tabl0005" num="0005"><table frame="all"><title>Table 5</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">RNG _REQ_message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=4</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Downlink Channel ID</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Pending Until Complete</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> TLV Encoded Information</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="left">TLV specific</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 5, the 'Downlink Channel ID' represents a downlink channel identifier contained in the RNG_REQ message received in the subscriber station 400 through the UCD. The 'Pending Until Complete' represents a priority of a transmitted ranging response. That is, when the Pending Until Complete has a value of 0, a previous ranging response has a high priority. In contrast, when the Pending Until Complete has values other than 0, a currently transmitted ranging response has a high priority.
Table 6 illustrated below, shows the structure of the RNG_RSP message corresponding to the RNG_REQ message shown in Table 5. <tables id="tabl0006" num="0006"><table frame="all"><title>Table 6</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">RNG_RSP_message_Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=5</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Uplink Channel ID</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> TLV Encoded Information</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="left">TLV specific</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 6, the 'Uplink Channel ID' represents an uplink channel identifier contained in the RNG_REQ message. Meanwhile, in FIG. 4, since the IEEE 802.16a communication system considers only a state in which a subscriber station is currently motionless, that is, it does not entirely consider the mobility of the subscriber station, the base station 420 (as shown in Fig. 4) communicating with the subscriber station 400 unconditionally becomes a serving base station.
As described above, the IEEE 802.16a communication system considers only a state in which a subscriber station is currently motionless (i.e., a state in which the mobility of the subscriber station is not entirely considered), and a single cell structure. However, an IEEE 802.16e communication system is stipulated as a system considering the mobility of a subscriber station in the IEEE 802.16a communication system. Accordingly, the IEEE 802.16e communication system must consider the mobility of a subscriber station in a multi-cell environment. In order to support the mobility of the subscriber station in a multi-cell environment, changes in operations of the subscriber station and a base station are necessarily required. Especially, in order to support the mobility of the subscriber station, research into a handover of the subscriber station considering a multi-cell structure has been actively pursued.
Hereinafter, the structure of the conventional IEEE 802.16e communication system will be described with reference to FIG. 5.
FIG. 5 is a block diagram schematically showing the structure of the IEEE 802.16e communication system.
Referring to FIG. 5, the IEEE 802.16e communication system has a multi-cell structure, that is, a cell 500 and a cell 550. Further, the IEEE 802.16a communication system includes a base station 510 controlling the cell 500, a base station 540 controlling the cell 550, and a plurality of mobile subscriber stations (MSSs) 511, 513, 530, 551, and 553. The transmission/reception of signals between the base stations 510 and 540 and the mobile subscriber stations 511, 513, 530, 551, and 553 is accomplished through an OFDM/OFDMA method. Herein, the mobile subscriber station 530 (of the mobile subscriber stations 511, 513, 530, 551, and 553) exists in an overlapping area (i.e., handover area) between the cell 500 and the cell 550. Accordingly, only when a handover for the mobile subscriber station 530 must be supported, it is possible to support the mobility for the mobile subscriber station 530.
In the IEEE 802.16e communication system, a certain mobile subscriber station receives pilot channel signals transmitted from a plurality of base stations, and measures CINRs of the received pilot channel signals. The mobile subscriber station then selects a base station, which is the base station that has transmitted a pilot channel signal having the highest CINR from among the measured CINRs of the pilot channel signals, as a base station to which the mobile subscriber station currently belongs. That is, the mobile subscriber station recognizes a base station, which transmits a pilot channel signal capable of being favorably received in the mobile subscriber station, from among base stations having transmitted pilot channel signals as a base station to which the mobile subscriber station belongs. As a result, the base station to which the mobile subscriber station currently belongs becomes a serving base station. The mobile subscriber station having selected the serving base station receives a downlink frame and an uplink frame transmitted from the serving base station. Herein, the downlink frame and the uplink frame of the IEEE 802.16e communication system have the same structures as those of the downlink frame and the uplink frame of the IEEE 802.16a communication system shown in FIGS. 2 and 3 above and described herein.
The serving base station transmits a mobile subscriber station neighbor advertisement (hereinafter, referred to as a MOB_NBR_ADV) message to the mobile subscriber station. Table 7 illustrated below shows the structure of the MOB NBR ADV message. <tables id="tabl0007" num="0007"><table frame="all"><title>Table 7</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB NBR ADV_message_Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=48</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Configuration Change Count</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> N_NEIGHBORS</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> For (j=0;j< N_NEIGHBORS;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Neighbor BS-ID</entry><entry namest="col2" nameend="col2" align="left">48 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Physical Frequency</entry><entry namest="col2" nameend="col2" align="left">32 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> TLV Encoded Neighbor Information</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="left">TLV specific</entry></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 7, the MOB_NBR_ADV message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, the 'Configuration Change Count' representing the number of times by which a Configuration changes, the 'N_NEIGHBORS' representing the number of neighbor base stations, the 'Neighbor BS-ID' representing identifiers (ID) of the neighbor base stations, the 'Physical Frequency' representing the physical frequency of the neighbor base station, and the 'TLV Encoded Neighbor Information' representing extra information relating to the neighbor base station in addition to the information.
The mobile subscriber station having received the MOB_NBR_ADV message transmits a mobile subscriber station scanning interval allocation request (hereinafter, referred to as a MOB_SCN_REQ) message to the serving base station when the mobile subscriber station intends to scan the CINRs of pilot channel signals transmitted from neighbor base stations. Herein, since a time point at which the mobile subscriber station requests a scanning has no direct relation to a scanning operation for the CINR of the pilot channel signal, a detailed description about the time point will be omitted.
Table 8 illustrated below shows the structure of the MOB_SCN_REQ message. <tables id="tabl0008" num="0008"><table frame="all"><title>Table 8</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB SCN REQ message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=?</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Scan Duration</entry><entry namest="col2" nameend="col2" align="left">16 bits</entry><entry namest="col3" nameend="col3" align="left">Units are frames</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 8, the MOB_SCN_REQ message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message and the 'Scan Duration' representing a scan duration for which the mobile subscriber station scans the CINRs of the pilot channel signals transmitted from the neighbor base stations. The 'Scan Duration' is constructed by the frame. Herein, the 'Management Message Type' of the MOB_SCN_REQ message to be transmitted has not been defined yet (i.e., Management Message Type = undefined or "?" as is shown in the table to conserve space).
Meanwhile, the serving base station having received the MOB_SCN_REQ message transmits a mobile subscriber station scanning interval allocation response (hereinafter, referred to as a MOB_SCN_RSP) message, which contains information to be scanned by the mobile subscriber station, to the mobile subscriber station. Table 9 illustrated below shows the structure of the MOB SCN RSP message. <tables id="tabl0009" num="0009"><table frame="all"><title>Table 9</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB SCN RSP message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=?</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Length</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" align="left">in bytes</entry></row><row><entry namest="col1" nameend="col1" align="left"> For(I=0;i<Length/3 ;i++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> CID</entry><entry namest="col2" nameend="col2" align="left">16 bits</entry><entry namest="col3" nameend="col3" align="left">basic CID of the MSS</entry></row><row><entry namest="col1" nameend="col1" align="left"> Duration</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" align="left">in frames</entry></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 9, the MOB_SCN_RSP message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, the connection ID (hereinafter, referred to as a CID) of the mobile subscriber station having transmitted the MOB_SCN_REQ message, and a scan duration. In Table 9, the 'Management Message Type' of the MOB_SCN_RSP message to be transmitted has not been defined yet (i.e., Management Message Type = undefined), and the scan duration is a duration for which the mobile subscriber station performs the pilot CINR scanning. The mobile subscriber station having received the MOB_SCN_RSP message containing the scanning information scans pilot CINRs for neighbor base stations, which has been recognized through the MOB_NBR_ADV message, according to the scanning information parameters.
In order to support a handover in the IEEE 802.16e communication system, a mobile subscriber station must measure CINRs of pilot channel signals transmitted from neighbor base stations and a base station (i.e., serving base station) to which the mobile subscriber station currently belongs. Further, when the CINR of the pilot channel signal transmitted from the serving base station is smaller than the CINRs of the pilot channel signals transmitted from the neighbor base stations, the mobile subscriber station requests a handover from the serving base station. Herein, for convenience of description, the sentence 'measure the CINR of the pilot channel signal' may be expressed by a sentence 'scan or perform a scanning for the CINR of the pilot channel signal'. Also, the words 'scan' and 'scanning' have the same concept; 'scan' is used together with 'scanning' for convenience of description,.
Hereinafter, a handover process by the request of a mobile subscriber station in the conventional IEEE 802.16e communication system will be descried with reference to FIG. 6.
FIG. 6 is a flow diagram illustrating the handover process by the request of the mobile subscriber station in the conventional IEEE 802.16e communication system.
Referring to FIG. 6, first, a serving base station 640 transmits a MOB_NBR_ADV message to a mobile subscriber station 600 in step 611. Then, the mobile subscriber station 600 receives the MOB_NBR_ADV message and obtains information on neighbor base stations. Further, in step 613, the mobile subscriber station 600 transmits a MOB_SCN_REQ message to the serving base station 640 when the mobile subscriber station 600 intends to scan the CINRs of pilot channel signals transmitted from the neighbor base stations. Herein, since a time point at which the mobile subscriber station 600 requests a scanning has no direct relation to a scanning operation for the CINR of the pilot channel signal, a detailed description about the time point will be omitted. Meanwhile, in step 615, the serving base station 640 having received the MOB_SCN_REQ message transmits the MOB_SCN_RSP message, which contains information to be scanned by the mobile subscriber station 600, to the mobile subscriber station 600. In step 617, the mobile subscriber station 600 having received the MOB_SCN_RSP message containing the scanning information performs a scanning for the CINRs of pilot channel signals with respect to neighbor base stations, which have been recognized through the reception of the MOB_NBR_ADV message, according to parameters (i.e., scan duration) contained in the MOB_SCN_RSP message.
Next, after having completely scanned the CINRs of the pilot channel signals received from the neighbor base stations, when the mobile subscriber station 600 determines to change the serving base station 640 to which the mobile subscriber station 600 currently belongs in step 619, that is, the mobile subscriber station 600 determines to change the current serving base station 640 to another new base station, the mobile subscriber station 600 transmits a mobile subscriber station handover request (hereinafter, referred to as a MOB_MSSHO_REQ) message to the serving base station 640 in step 621. Herein, a new base station (i.e., a base station to which the mobile subscriber station 600 is to be handed over), which is not a serving base station to which the mobile subscriber station 600 currently belongs, is called a target base station (target BS). Table 10 shows the structure of the MOB_MSSHO_REQ message and is illustrated below. <tables id="tabl0010" num="0010"><table frame="all"><title>Table 10</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB MSSHO REQ message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=52</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> N Recommended</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> For (j=0;j<N_NEIGHBORS;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Neighbor BS-ID</entry><entry namest="col2" nameend="col2" align="left">48 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> BS S/(N+1)</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Service level prediction</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 10, the MOB_MSSHO_REQ message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, and the 'N_Recommended' representing a result obtained by a scanning of a mobile subscriber station. Herein, as shown in Table 10, the 'N_Recommended' contains the identifiers of neighbor base stations, a CINR of a pilot channel signal for each of the neighbor base stations, and the level of a service predicted to be provided from the neighbor base stations to the mobile subscriber station.
Meanwhile, when the serving base station 640 receives the MOB_MSSHO_REQ message transmitted from the mobile subscriber station 600, the serving base station 640 detects a list of target base stations to which the mobile subscriber station 600 can be handed over by means of the 'N_Recommended' information of the received MOB_MSSHO_REQ message in step 623. Herein, for convenience of description, the list of target base stations to which the mobile subscriber station 600 can be handed over will be called a 'handover-executable target base station list'. In FIG. 6, it is assumed that a first target base station 660 and a second target base station 680 exist in the handover-executable target base station list. Also, the handover-executable target base station list may include a plurality of target base stations. In steps 625 and 627, the serving base station 640 transmits a handover notifications (hereinafter, referred to as HO_notifications) message to the target base stations (i.e., the first target base station 660 and the second target base station 680) contained in the handover-executable target base station list. Table 11 shows the structure of the HO_notification message and illustrated below. <tables id="tabl0011" num="0011"><table frame="all"><title>Table 11</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">Global Header</entry><entry namest="col2" nameend="col2" align="left">152-bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">For (j=0;j< Num Records;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> MSS unique identifier</entry><entry namest="col2" nameend="col2" align="left">48-bit</entry><entry namest="col3" nameend="col3" align="left">48-bit unique identifier used by MSS (as provided by the MSS or by the I-am-host-of message)</entry></row><row><entry namest="col1" nameend="col1" align="left"> Estimated Time to HO</entry><entry namest="col2" nameend="col2" align="left">16-bit</entry><entry namest="col3" nameend="col3" align="left">In milliseconds, relative to the time stamp, value 0 of this parameter indicates that no actual HO is pending</entry></row><row><entry namest="col1" nameend="col1" align="left"> Required BW</entry><entry namest="col2" nameend="col2" align="left">8-bit</entry><entry namest="col3" nameend="col3" align="left">Bandwidth which is required by MSS (to guarantee minimum packet data transmission)</entry></row><row><entry namest="col1" nameend="col1" align="left"> Required QoS</entry><entry namest="col2" nameend="col2" align="left">8-bit</entry><entry namest="col3" nameend="col3" align="left">Name of Service Class representing Authorized QoSparamSet</entry></row><row><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Security field</entry><entry namest="col2" nameend="col2" align="left">TBD</entry><entry namest="col3" nameend="col3" align="left">A means to authenticate this message</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">CRC field</entry><entry namest="col2" nameend="col2" align="left">32-bit</entry><entry namest="col3" nameend="col3" align="left">IEEE CRC-32</entry></row></tbody></tgroup></table></tables>
As shown in Table 11, the HO_notification message includes a plurality of IEs, that is, an identifier MSS ID of the mobile subscriber station 600 intending to perform a handover procedure to the first target base station 660 or the second target base station 680, an estimated start time of a handover by the mobile subscriber station 600, and information on the bandwidth requested from the mobile subscriber station 600 to a target base station which will become the new serving base station, and the level of a service that is to be provided to the mobile subscriber station 600. Herein, the bandwidth and the service level requested by the mobile subscriber station 600 are identical to the predicted service level information recorded in the MOB_MSSHO-REQ message described in Table 10 above.
Meanwhile, when the first target base station 660 or the second target base station 680 receive the HO_notification messages from the serving base station 640, they each transmit handover notification response (hereinafter, referred to as a HO_notification_response) messages, response messages with respect to the HO_notification message, to the serving base station 640 in steps 629 and 631, respectively. Table 12 shows the structure of the HO_ notification_ response message and is illustrated below. <tables id="tabl0012" num="0012"><table frame="all"><title>Table 12</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">Global Header</entry><entry namest="col2" nameend="col2" align="left">152-bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">For (j=0;j< Num Records;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> MSS unique identifier</entry><entry namest="col2" nameend="col2" align="left">48-bit</entry><entry namest="col3" nameend="col3" align="left">48-bit unique identifier used by MSS (as provided by the MSS or by the I-am-host-of message)</entry></row><row><entry namest="col1" nameend="col1" align="left"> QoS Estimated</entry><entry namest="col2" nameend="col2" align="left">8-bit</entry><entry namest="col3" nameend="col3" align="left">Bandwidth which is provided by BS(to guarantee minimum packet data transmission)TBD how to set this field</entry></row><row><entry namest="col1" nameend="col1" align="left"> BW Estimated</entry><entry namest="col2" nameend="col2" align="left">8-bit</entry><entry namest="col3" nameend="col3" align="left">Quality of Service level Unsolicited Grant Service (UGS) Real-time polling Service (rtPS) Non-Real-time polling Service nrtPS) Best effort</entry></row><row><entry namest="col1" nameend="col1" align="left"> ACK/NACK</entry><entry namest="col2" nameend="col2" align="left">1-bit</entry><entry namest="col3" nameend="col3" align="left">Acknowledgement or Negative acknowledgement 1 is Acknowledgement which means that the neighbor BS accepts the HO_notification message from the serving BS 0 is Negative Acknowledgement which means that the neighbor BS may not accept the HO_notification message from the serving BS</entry></row><row><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Security field</entry><entry namest="col2" nameend="col2" align="left">TBD</entry><entry namest="col3" nameend="col3" align="left">A means to authenticate this message</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">CRC field</entry><entry namest="col2" nameend="col2" align="left">32-bit</entry><entry namest="col3" nameend="col3" align="left">IEEE CRC-32</entry></row></tbody></tgroup></table></tables>
As shown in Table 12, the HO_notification_response message includes a plurality of IEs, that is, an identifier MSS ID (MSS unique identifier) of a mobile subscriber station intending to perform a handover procedure to target base stations, a response ACK/NACK regarding whether or not the target base stations can perform a handover according to the handover request of the mobile subscriber station, and bandwidth and service level information capable of being provided by each target base station when the mobile subscriber station is handed over to each target base station.
Meanwhile, the serving base station 640 having received the HO_notification_response messages from the first target base station 660 and the second target base station 680 analyzes the received HO_notification_response message, and selects a target base station, which can optimally provide the bandwidth and the service level requested by the mobile subscriber station 600 when the mobile subscriber station 600 is handed over, as a final target base station to which the mobile subscriber station 600 is to be handed over. For instance, when it is assumed that the service level capable of being provided by the first target base station 660 is smaller that that requested by the mobile subscriber station 600, and the service level capable of being provided by the second target base station 680 is identical to that requested by the mobile subscriber station 600, the serving base station 640 selects the second target base station 680 as a final target base station to which the mobile subscriber station 600 is to be handed over. Accordingly, the serving base station 640 transmits a handover notification confirmation (hereinafter, referred to as a HO_ notification_confirm) message, a response message with respect to the HO_notification_response message, to the second target base station 680 in step 633. Table 13 shows the structure of the HO_ notification_confirm message and is illustrated below. <tables id="tabl0013" num="0013"><table frame="all"><title>Table 13</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">Global Header</entry><entry namest="col2" nameend="col2" align="left">152-bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">For (j=0;j< Num Records;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> MSS unique identifier</entry><entry namest="col2" nameend="col2" align="left">48-bit</entry><entry namest="col3" nameend="col3" align="left">48-bit universal MAC address of the MSS (as provided to the BS on the RNG-REQ message)</entry></row><row><entry namest="col1" nameend="col1" align="left"> QoS Estimated</entry><entry namest="col2" nameend="col2" align="left">8-bit</entry><entry namest="col3" nameend="col3" align="left">Bandwidth which is provided by BS(to guarantee minimum packet data transmission)TBD how to set this field</entry></row><row><entry namest="col1" nameend="col1" align="left"> BW Estimated</entry><entry namest="col2" nameend="col2" align="left">8-bit</entry><entry namest="col3" nameend="col3" align="left">Quality of Service level Unsolicited Grant Service (UGS) Real-time polling Service (rtPS) Non-Real-time polling Service (nrtPS) Best effort</entry></row><row><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Security field</entry><entry namest="col2" nameend="col2" align="left">TBD</entry><entry namest="col3" nameend="col3" align="left">A means to authenticate this message</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">CRC field</entry><entry namest="col2" nameend="col2" align="left">32-bit</entry><entry namest="col3" nameend="col3" align="left">IEEE CRC-32</entry></row></tbody></tgroup></table></tables>
As shown in Table 13, the HO_ notification_confirm message includes a plurality of IEs, that is, an identifier MSS ID (MSS unique identifier) of a mobile subscriber station intending to perform a handover procedure to a selected target base station, and bandwidth and service level information capable of being provided by the selected target base station when the mobile subscriber station is handed over to the selected target base station.
Also, the serving base station 640 transmits a mobile subscriber station handover response (hereinafter, referred to as a MOB_HO_RSP) message, a response message with respect to the MOB_MSSHO_REQ message, to the mobile subscriber station 600 in step 635. Herein, the MOB_HO_RSP message contains information on a target base station to which the mobile subscriber station 600 is to be handed over. Table 14 illustrated below, shows the structure of the MOB_HO_RSP message. <tables id="tabl0014" num="0014"><table frame="all"><title>Table 14</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB HO_RSP_message_Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=53</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Estimated HO time</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> N Recommended</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> For (j=0;j< N_NEIGHBORS;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Neighbor BS-ID</entry><entry namest="col2" nameend="col2" align="left">48 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Service level prediction</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" align="left">This parameter exists only when the message is sent by the BS</entry></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 14, the MOB_HO_RSP message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, an estimated start time of a handover procedure, and the 'N_Recommended' representing a result for target base stations selected by a serving base station. Herein, as shown in Table 14, the 'N_Recommended' contains identifiers of the selected target base stations and the level of a service predicted to be provided from each target base station to a mobile subscriber station. In FIG. 6, the MOB_HO_RSP message finally includes only target base station information on the second target base station 680 from among target base stations existing in the handover-executable target base station list. However, when there exist a plurality of target base stations capable of providing bandwidth and service level requested by the mobile subscriber station 600 from among the target base stations existing in the handover-executable target base station list, the MOB_HO_RSP message includes information on the plurality of target base stations.
Next, the mobile subscriber station 600 having received the MOB_HO_RSP message analyzes the 'N_Recommended' information contained in the MOB_HO_RSP message and selects a target base station to which the mobile subscriber station 600 is to be handed over. Then, the mobile subscriber station 600 having selected the target base station to which the mobile subscriber station 600 is to be handed over transmits a mobile subscriber station handover indication (hereinafter, referred to as a MOB_HO_IND) message, a response message with respect to the MOB_HO_RSP message, to the serving base station 640 in step 637. Table 15 illustrated below, shows the structure of the MOB HO IND message. <tables id="tabl0015" num="0015"><table frame="all"><title>Table 15</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB HO_IND_message_Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=54</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> TLV Encoded Information</entry><entry namest="col2" nameend="col2" align="left">Variable</entry><entry namest="col3" nameend="col3" align="left">TLV specific</entry></row><row><entry namest="col1" nameend="col1" align="left"> Target_BS ID</entry><entry namest="col2" nameend="col2" align="left">48 bits</entry><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 15, the MOB_HO_IND message includes a plurality of IEs, that is, the 'Management Message Type' representing the type of a transmitted message, the 'Target_BS_ID' representing an identifier of a target base station selected by a mobile subscriber station, and the 'TLV Encoded Information' representing extra information in addition to the information.
Meanwhile, in step 639, the serving base station 640 having received the MOB_HO_IND message recognizes that the mobile subscriber station 600 is handed over to the target base station (i.e., the second target base station 680) contained in the MOB_HO_IND message, and then releases a link currently setup with the mobile subscriber station 600. In this way, when the link with the serving base station 640 is released, the mobile subscriber station 600 performs a handover procedure to the second target base station 680 in step 641.
Hereinafter, a handover process by the request of a base station in the conventional IEEE 802.16e communication system will be described with reference to FIG. 7.
FIG. 7 is a flow diagram illustrating the handover process by the request of the base station in the conventional IEEE 802.16e communication system.
Before describing FIG. 7, the handover process by the request of the base station occurs when the base station is overloaded and requires some type of load- sharing for dispersing the load of the base station, or the base station must cope with the change of the uplink status of a mobile subscriber station.
Referring to FIG. 7, first, a serving base station 740 transmits a MOB_NBR_ADV message to a mobile subscriber station 700 in step 711. Then, the mobile subscriber station 700 receives the MOB_NBR_ADV message and obtains information on neighbor base stations. Further, in step 713, the mobile subscriber station 700 transmits a MOB_SCN_REQ message to the serving base station 740 when the mobile subscriber station 700 intends to scan the CINRs of pilot channel signals transmitted from the neighbor base stations. Herein, since a time point at which the mobile subscriber station 700 requests a scanning has no direct relation to a scanning operation for the CINR of the pilot channel signal, a detailed description about the time point will be omitted. In step 715, the serving base station 740 having received the MOB_SCN_REQ message transmits the MOB_SCN_RSP message, which contains information to be scanned by the mobile subscriber station 700, to the mobile subscriber station 700. In step 717, the mobile subscriber station 700 having received the MOB_SCN_RSP message containing the scanning information performs a CINR scanning of pilot channel signals with respect to neighbor base stations, which has been recognized through the reception of the MOB_NBR_ADV message, according to parameters (i.e., scan duration) contained in the MOB_SCN_RSP message.
Meanwhile, when the mobile subscriber station 700 managed by the serving base station 740 determines to perform a handover procedure by its own handover necessity in step 719, the serving base station 740 transmits the HO_notification messages to neighbor base stations 760 an 780 in steps 721 and 723. Herein, the HO_notification message contains information on a bandwidth and the level of a service which must be provided by a target base station to be a new serving base station of the mobile subscriber station 700. In FIG. 7, it is assumed that the neighbor base stations of the serving base station 740 are two base stations, that is, the first target base station 760 and the second target base station 780.
In steps 725 and 727, the first target base station 760 and the second target base station 780 receive the HO_notification messages respectively, and transmit the HO_notification_response messages, response messages for the HO_notification messages, to the serving base station 740. As described in Table 12, the HO_notification_response message contains a response ACK/NACK regarding whether or not the target base stations can perform a handover procedure requested by the serving base station 740, and bandwidth and service level information capable of being provided to the mobile subscriber station 700.
Next, after receiving the HO_ notification_ response messages from the first target base station 760 and the second target base station 780, the serving base station 740 then selects target base stations capable of providing the bandwidth and the service level requested by the mobile subscriber station 700. For instance, when it is assumed that the service level capable of being provided by the first target base station 760 is smaller than that requested by the mobile subscriber station 700, and the service level capable of being provided by the second target base station 780 is identical to that requested by the mobile subscriber station 700, the serving base station 740 selects the second target base station 780 as a final target base station to which the mobile subscriber station 700 is to be handed over. Further, the serving base station 740 having selected the second target base station 780 as the final target base station transmits a HO_notification_confirm message, which is a response message for the HO_notification_response message in step 729.
Next, after transmitting the HO_notification_confirm message to the second target base station 780, the serving base station 740 transmits a MOB_HO_RSP message to the mobile subscriber station 700 in step 731. Herein, the MOB_HO_RSP message contains N_Recommended information selected by the serving base station 740, that is, selected target base stations e.g., in FIG. 7, the second target base station 780) and the bandwidth and the service level capable of being provided from the target base stations to the mobile subscriber station 700. The mobile subscriber station 700 having received the MOB_HO_RSP message recognizes the a handover has been requested by the serving base station 740, and selects a final target base station to which the mobile subscriber station 700 is to be handed over with reference to the N_Recommended information contained in the MOB_HO_RSP message. After selecting the final target base station, the mobile subscriber station 700 transmits a MOB_HO_IND message, a response message for the MOB_HO_RSP message, to the serving base station 740 in step 733. Then, in step 735, the serving base station 740 having received MOB_HO_IND message recognizes that the mobile subscriber station 700 is to be handed over to the target base station contained in the MOB_HO_IND message, and then releases a link currently setup with the mobile subscriber station 700. In this way, when the link with the serving base station 740 is released, the mobile subscriber station 700 performs a handover procedure to the second target base station 780 in step 737.
As described above, in the currently proposed handover procedure in the IEEE 802.16e communication system, a serving base station collects information of neighbor base stations, transmits a HO_notification message, and collects information necessary for the handover. Then, the serving base station receives a HO_notification_response message as a response of the HO_notification message, and transmits a MOB_HO_RSP message containing information of target base stations to which a mobile subscriber station can be handed over to the corresponding mobile subscriber station. Meanwhile, the mobile subscriber station determines a base station to which the mobile subscriber station is to be handed over from a list of target base stations, to which the mobile subscriber station can be handed over, contained in the MOB_HO_RSP message, and then transmits a MOB_HO_IND message containing information on the determined base station to the serving base station. Then, the mobile subscriber station releases a current connection with the serving base and tries to connect with the determined base station.
As described above, only a simple procedure for a handover is defined up to now. However, various circumstances may exist which have been not described in the procedure in a broadband mobile communication service of actual various radio environments. For instance, there may occur a case in which the serving base station must forcedly cause the subscriber station to perform a handover procedure according to the resource condition of the serving base station, or special circumstances such as the rejection of the subscriber station for a handover requested by the serving base station. Also, there may occur a case in which the movement direction of the subscriber station changes while being handed over to a target base station, and the subscriber station must cancel the handover procedure in order to connect to an original serving base station again.
However, the conventional broadband mobile communication system has not yet presented methods for solving the circumstances which may occur as described above. Additionally, when the conventional method is applied to the aforementioned circumstances, it is ineffective and further, the performance of the system may be substantially reduced.
SUMMARY OF THE INVENTION
Accordingly, the present invention has been made to solve the above-mentioned problems occurring in the prior art, and it is an object of the present invention is to provide a handover method for ensuring the mobility of a subscriber station contained in a broadband wireless communication system and performing smooth data communication.
It is another object of the present invention is to provide a method for performing a handover between base stations in order to ensure the mobility of a subscriber station in a broadband wireless communication system.
It is a further another object of the present invention is to provide a handover method by which a serving base station performing a data communication receives a handover request message containing handover-related information from a subscriber station by a handover request of the serving base station, determines base stations to which the subscriber station is to be handed over, and transmits the list of the base stations to the subscriber station.
It is a still another object of the present invention is to provide a method by which a serving base station commands a subscriber station to perform a handover operation for being handed over to a base station by a handover request of the serving base station, and thus the subscriber station performs a forced handover without alternative.
It is a still another object of the present invention is to provide a method by which a subscriber station performs a handover rejection function for a handover request message received from a serving base station when the subscriber station is handed over to a base station by a handover request of the serving base station.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for a serving base station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, the serving base station providing a service to the mobile station in the serving cell area, and at least one target base station adjacent to the serving base station. The method comprises the steps of determining a handover when the serving base station needs to make the mobile station performed the handover procedure; notifying one of the target base stations to perform the handover procedure; and transmitting a handover message to the mobile station including forced handover information signifying that the serving base station commands the mobile station to be handed over to the notified target base station.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for handover of a mobile station located in a serving cell area of a serving base station in a broadband wireless communication system including the mobile station, the serving base station, and at least one target base station having a target cell area adjacent to the serving cell area, the serving base station providing a service to the mobile station in the serving cell area. The method comprises the steps of receiving a message including handover information from the serving base station; confirming by the mobile station the handover information in the message, and releasing link between the mobile station and the serving base station when the message is a forced handover indication message; and performing handover toward one handover-executable target base station included in the message.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for a mobile station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station. The method comprises the steps of transmitting a handover request message to the serving base station when it is detected that a handover is necessary and transmitting a handover indication message including handover cancellation information to the serving base station when the mobile station decides to cancel the handover during a time period in which the mobile station performs the handover to one of the target base stations.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area. The method comprises the steps of progressing handover process between the serving base station and the target base station after receiving a handover request message from the mobile station; canceling the handover process when the serving base station has received a handover cancellation message including handover cancellation information from the mobile station while the handover process is in progress; and maintaining link between the mobile station and the serving base station after the serving base station cancels the handover process.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for a mobile station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station. The method comprises the steps of transmitting a handover request message to the serving base station when it is detected that a handover is necessary; receiving a first handover response message from the serving base station; and transmitting a handover indication message including handover rejection information to the serving base station when the mobile station determines a rejection of the handover after receiving the handover response message.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area. The method comprises the steps of progressing handover process between the serving base station and the target base station after receiving a handover request message from the mobile station; stopping the handover process when the serving base station has received a handover rejection message including handover rejection information from the mobile station while the handover process is in progress; and transmitting a list of the target base stations from the serving base station to the mobile station after the serving base station stops the handover process.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for a mobile station to enable a mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station. The method comprises the steps of receiving a handover request message from the serving base station and performing the handover procedure; and transmitting a handover indication message including handover cancellation information to the serving base station when the mobile station decides to cancel the handover during a time period in which the mobile station performs the handover to one of the target base stations.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area. The method comprises the steps of transmitting a handover request message from the serving base station to the mobile station and progressing handover process between the serving base station and the target base station; canceling the handover process when the serving base station has received a handover cancellation message including handover cancellation information from the mobile station while the handover process is in progress; and maintaining link between the mobile station and the serving base station after the serving base station cancels the handover process.
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for a mobile station to enable the mobile station existing in a serving cell area to perform a handover procedure in a broadband wireless communication system including the mobile station, a serving base station providing a service to the mobile station in the serving cell area, and one or more target base stations adjacent to the serving base station. The method comprising the steps of receiving a handover request message including a list of the target base stations from the serving base station ; and transmitting a handover indication message including handover rejection information to the serving base station when the mobile station determines a rejection of the handover after checking the list of the target base stations
In order to accomplish the aforementioned object, according to one aspect of the present, there is provided a method for performing handover by a serving base station in a broadband wireless communication system including a mobile station, the serving base station, and at least one target base station having a target cell area station adjacent to a serving cell area of the serving base station, the serving base station providing a service to the mobile station located in the serving cell area. The method comprising the steps of transmitting a handover request message from the serving base station to the mobile station and progressing handover process between the serving base station and the target base station, the handover request message including a list of the target base stations; stopping the handover process when the serving base station has received a handover rejection message including handover rejection information from the mobile station while the handover process is in progress; and transmitting a new list of the target base stations from the serving base station to the mobile station
BRIEF DESCRIPTION OF THE DRAWINGS
The above and other objects, features and advantages of the present invention will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li>FIG. 1 a block diagram which illustrates a structure of a conventional broadband mobile communication system employing an OFDM/OFDMA method;</li><li>FIG. 2 is a view which illustrates a structure of a downlink frame of a conventional broadband mobile communication system employing an OFDM/OFDMA method;</li><li>FIG. 3 is a view which illustrates a structure of an uplink frame of a broadband mobile communication system employing an OFDM/OFDMA method;</li><li>FIG. 4 is a flow diagram illustrating a ranging procedure between a base station and a subscriber station in a broadband mobile communication system employing an OFDM/OFDMA method;</li><li>FIG. 5 is a block diagram schematically showing a structure of a broadband mobile communication system employing an OFDM/OFDMA method in a multi-cell;</li><li>FIG. 6 is a flow diagram illustrating a handover process by request of a subscriber station in a broadband mobile communication system employing an OFDM/OFDMA method;</li><li>FIG. 7 is a flow diagram illustrating a handover process by request of a base station in a broadband mobile communication system employing an OFDM/OFDMA method;</li><li>FIG. 8 is a flow diagram illustrating a procedure by which a base station forces a handover in a broadband wireless access communication system according to an embodiment of the present invention;</li><li>FIG. 9 is a flow diagram illustrating a procedure by which a subscriber station cancels a handover in a broadband wireless access communication system according to an embodiment of the present invention;</li><li>FIG. 10 is a flow diagram illustrating a procedure by which a subscriber station rejects a handover in a broadband wireless access communication system according to an embodiment of the present invention;</li><li>FIG. 11 is a flowchart illustrating a procedure by which a base station forces a handover in a broadband wireless access communication system according to a first embodiment of the present invention;</li><li>FIG. 12 is a flowchart illustrating a procedure by which a subscriber station cancels or rejects a handover in a broadband wireless access communication system according to a second embodiment of the present invention;</li><li>FIG. 13 is a flowchart illustrating a procedure by which a subscriber station cancels or rejects a handover in a broadband wireless access communication system according to a third embodiment of the present invention; and</li><li>FIG. 14 is a flowchart illustrating a procedure by which a subscriber station cancels or rejects a handover in a broadband wireless access communication system according to a third modified embodiment of the present invention.</li></ul>
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
Hereinafter, a preferred embodiment according to the present invention will be described with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.
In describing the present invention, the terms 'handover' and 'handoff' have the same concept; 'handover' is used together with 'handoff'. That is, when a predetermined mobile station releases a connection with a base station (hereinafter, referred to as a serving base station) currently maintaining a connection with the mobile station according to circumstances, and connects to one (hereinafter, referred to as an object base station or a target base station) of neighbor base stations, the term 'handover' or the term 'handoff' is used.
Also, generally, a base station to/with which the mobile station currently connects and can exchange data is called a serving base station, and a plurality of base stations which are adjacent to the serving base station and can perform a handover procedure according to the moving of the mobile station are called neighbor base stations (neighbor BS).
Meanwhile, in the conventional handover procedure as shown in FIGS. 6 and 7 and described in the corresponding text, peripheral base stations of the serving base station, which are transmitted from the serving base station to the station through a MOB_NBR_ADV message, are called neighbor base stations as described above. Herein, when the mobile station scans CINR values of the neighbor base stations and selects base stations satisfying predetermined conditions from among the neighbor base stations as base stations to which the mobile station can be handed over, the base stations selected by the mobile station are called recommended base stations.
Further, the serving base station transmits HO_notification message to each recommended base station selected by the mobile station or each neighbor base station, and then receives HO_notification response messages. Also, the serving base station selects one or multiple base stations satisfying predetermined conditions under which a handover is possible for the station according to values contained in the received message. Herein, from among the recommended base stations or the neighbor base stations, one or multiple base stations satisfying predetermined conditions selected by serving base station are called target base stations. That is, one or multiple base stations may become the target base station.
Meanwhile, when the serving base station transmits a predetermined message (e.g., MOB_HO_RSP message) containing information on one or more target base stations to the corresponding station, and the station selects one target base station from among one or more target base stations, the finally selected target base station is called a designated target base station.
The present invention proposes various functions enabling a broadband mobile communication system to be capable of effectively processing various situations, in addition to a basic and simple handover function proposed in the conventional broadband mobile communication system. Accordingly, definitions of specific handoffs added according to circumstances proposed by the present invention are as follows.
1) Forced Handoff
A serving base station can command a subscriber station to be handed over to a target base station of a neighbor cell. That is, the subscriber station having received a message containing the forced handoff option must necessarily perform a handoff procedure to a target base station within a time period designated by the serving base station. In the case of the forced handoff, the subscriber station cannot reject the handoff command.
2) Suggesting Handoff
A serving base station transmits a mobile station (also known as a subscriber station) handoff message containing a message, which suggests that a subscriber station perform a handoff procedure to one of object base stations of a neighbor cell according to the request of the subscriber station or the judgment of the serving base station, to the subscriber station. Herein, the serving base station collects information on the base stations in the neighbor cell, selects a list of base stations, which satisfy service requirement conditions enabling the subscriber station to perform a handoff procedure and for which the subscriber station can perform a handoff procedure, and transmits the list to the subscriber station through a predetermined handoff message. When the subscriber station receives the suggesting handoff message, the subscriber station confirms the list of the target base stations contained in the message to select an optimum base station, thereby trying the suggesting handoff.
The handoff type option differently defined as described above is added to a predetermined field of the aforementioned MOB_HO_RSP message and then is transmitted. In the present invention, the handoff type option is added to the MOB_HO_RSP message form described in the prior art, and Table 16 (shown below) shows the new structure of the MOB_HO_RSP message according to the present invention. <tables id="tabl0016" num="0016"><table frame="all"><title>Table 16</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB HO RSP_message Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=53</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> HO Type</entry><entry namest="col2" nameend="col2" align="left">1 bits</entry><entry namest="col3" nameend="col3" align="left">0 : suggesting handoff 1 : forced handoff</entry></row><row><entry namest="col1" nameend="col1" align="left"> Estimated HO time</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> N Recommended</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> For (j=0;j<N NEIGHBORS;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Neighbor BS-ID</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Service level prediction</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> }</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 16, the MOB_HO_RSP message according to the present invention contains the 'HO Type' field for the application of the present invention. Accordingly, whether the MOB_HO_RSP message is a suggesting handoff or a forced handoff is determined according to the values of the field.
That is, as shown in Table 16, when the 'HO Type' field has a value of 0, a suggesting handoff is performed. In contrast, when the 'HO Type' field has a value of 1, a forced handoff is performed. In processing the 'N_Recommended' field after the function of the handoff is expanded as described above, when the value of the 'HO Type' field represents a suggesting handoff, the 'N_Recommended' field can have a value of more than 1. In contrast, when the value of the 'HO Type' field represents a forced handoff, a serving base station designates a specific target base station and orders a forced handoff. Accordingly, it is preferred that the 'N_Recommended' field has a value of only 1. That is, in the case of the forced handoff, a subscriber station must be handed over to an object base station, which is designated by the value of the 'N_Recommended' field, without alternative.
Accordingly, when the forced handoff and the suggesting handoff are performed as described above, it is preferred that the 'Neighbor BS-ID' field includes a list of one or more base stations in the case of a suggesting handoff and includes a list of only one base station in the case of a forced handoff.
Further, the present invention proposes a method for differently classifying a MOB_HO_IND message transmitted from a station to a base station according to circumstances and transmitting the MOB_HO_IND message in a basic handoff procedure proposed by the conventional broadband wireless mobile communication system. Definitions of procedures relating to each handoff newly added according to this method are as follows.
1) Connection Release
When a handoff has been normally performed and a connection with a serving base station must be ended, a subscriber station transmits a connection end message (i.e., a MOB_HO_IND message) containing a connection end option to the serving base station. The serving base station having received the connection end message immediately releases a connection with the corresponding subscriber station.
2) Handoff Cancel
When a subscriber station moves into an original serving base station again during a handoff and thus it is unnecessary to perform a handoff procedure, or a subscriber station intends to cancel a handoff by other reasons, the subscriber station transmits a MOB_HO_IND message containing a handoff cancel option to the serving base station. The serving base station having received the handoff cancel message immediately cancels a handoff procedure for a corresponding subscriber station. If necessary, the serving base station notifies a proposed object base station that a handoff performance by a corresponding subscriber station has been cancelled.
3) Handoff Rejection
After receiving a HO_RSP message from a serving base station, a subscriber station has not yet determined a proper target base station or does not perform a handoff procedure to a predetermined target base station contained in a target base station list by other reasons, the subscriber station transmits a MOB_HO_IND message containing a handoff rejection option to the serving base station according to the received HO_RSP message.
In the present invention, a 'HO Indication Type' field is added to the MOB_HO_IND message to enable the MOB_HO_IND message according to each state to be processed. Table 17 shows the structure of the MOB_HO_IND message according to the present invention and is illustrated below. <tables id="tabl0017" num="0017"><table frame="all"><title>Table 17</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">MOB HO_IND_message _Format() {</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Management Message Type=54</entry><entry namest="col2" nameend="col2" align="left">8 bits</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> HO Indicator Type</entry><entry namest="col2" nameend="col2" align="left">2 bits</entry><entry namest="col3" nameend="col3" align="left">00 : Serving BS release 01 : Handoff cancel 10 : Handoff rejection 11 : Reserved</entry></row><row><entry namest="col1" nameend="col1" align="left"> TLV Encoded Information</entry><entry namest="col2" nameend="col2" align="left">variable</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> Target BS ID</entry><entry namest="col2" nameend="col2" align="left">48 bits</entry><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">}</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 17, in order to perform a function proposed by the present invention, the 'HO Indicator Type' field is added to the MOB_HO_IND message, thereby constructing a MOB_HO_IND message having various functions. The 'HO Indicator Type' field in Table 17 is proposed to enable the MOB_HO_IND message to inform a serving base station of a connection release with a base station or handoff rejection according to corresponding values.
For instance, when the 'HO Indicator Type' field has a value of 00, a subscriber station releases a connection with a serving base station similarly to the prior art, and performs a normal handoff procedure to an already received corresponding target base station.
Meanwhile, when the 'HO Indicator Type' field has a binary value of 01, the MOB_HO_IND message represents a handoff cancel. Accordingly, the subscriber station cancels a handoff procedure being performed and maintains a connection with an existing serving base station. Further, when the 'HO Indicator Type' field has a binary value of 10, the MOB_HO_IND message represents a handoff rejection. Accordingly, the subscriber station rejects a handoff to a target base station contained in the MOB_HO_IND message received from a serving base station, and maintains a connection with an existing serving base station. Furthermore, when the 'HO Indicator Type' field has a binary value of 11, the 'HO Indicator Type' field is reserved as a reserved portion.
Further, the HO_notification_confirm message defined in Table 13 is a message enabling a serving base station to inform a target base station of a handoff. Accordingly, in the present invention, in the case of a handoff cancel, the HO_notification_confirm message is sent in advance, thereby enabling a target base station having received a handoff preparation instruction to understand the cancel of the handoff. That is, the HO_notification_confirm message has a changed structure as shown in the following Table 18. <tables id="tabl0018" num="0018"><table frame="all"><title>Table 18</title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52.50mm" /><colspec colnum="2" colname="col2" colwidth="52.50mm" /><colspec colnum="3" colname="col3" colwidth="52.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col1" align="center">Syntax</entry><entry namest="col2" nameend="col2" align="center">Size</entry><entry namest="col3" nameend="col3" align="center">Notes</entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">Global Header</entry><entry namest="col2" nameend="col2" align="left">152 bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left">Confirm type</entry><entry namest="col2" nameend="col2" align="left">1 bit</entry><entry namest="col3" nameend="col3" align="left">0:handoff preparation 1 : handoff cancel</entry></row><row><entry namest="col1" nameend="col1" align="left">For (j=0;j< Num Recorders;J++){</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> MSS unique identifier</entry><entry namest="col2" nameend="col2" align="left">48 bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> QoS Estimated</entry><entry namest="col2" nameend="col2" align="left">8 bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" align="left"> BW Estimated</entry><entry namest="col2" nameend="col2" align="left">8 bit</entry><entry namest="col3" nameend="col3" /></row><row><entry namest="col1" nameend="col1" /></row><row><entry namest="col1" nameend="col1" align="left">Security field</entry><entry namest="col2" nameend="col2" align="left">TBD</entry><entry namest="col3" nameend="col3" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">CRC field</entry><entry namest="col2" nameend="col2" align="left">32 bit</entry><entry namest="col3" nameend="col3" /></row></tbody></tgroup></table></tables>
As shown in Table 18, in order to perform a function proposed by the present invention, the 'Confirm type' field is added to the HO_notification_confirm message, thereby constructing a HO_notification_confirm message having various functions. According to the 'Confirm type' field having corresponding values in Table 18, the HO_notification_confirm message enables the serving base station to inform the target base station of the performance of a handoff or the cancel of a handoff.
For instance, when the 'Confirm type' field has a value of 0, the HO_notification_confirm message informs the target base station of the handoff of the subscriber station and enables the target base station to prepare the handoff of the subscriber station.
In contrast, when the 'Confirm type' field has a value of 1, the HO_notification_confirm message represents the cancel of the handoff. Accordingly, the target base station cancels the handoff procedure being performed by the already-sent HO_notification_confirm message.
In the present invention as described above, in order to accomplish a handover according to various handover circumstances, related fields of various messages are defined. Hereinafter, a procedure by which a subscriber station rejects or cancels a handover being performed according to each circumstance according to the present invention will be described in detail with reference to FIGS. 8 to 12.
First, a message transmission/reception procedure between a subscriber station and base stations according to an embodiment of the present invention will be described in detail with reference to FIGs. 8 to 10.
FIG. 8 is a flow diagram illustrating a case in which a base station determines whether or not a subscriber station performs a handoff procedure and forces the corresponding subscriber station to perform the handoff procedure according to an embodiment of the present invention. FIG. 9 is a flow diagram illustrating a case in which a subscriber station requests a handoff to a serving base station, and then cancels the requested handoff before receiving a response message from the serving base station or after receiving the response message from the serving base station, according to an embodiment of the present invention. Further, FIG. 10 is a flow diagram illustrating a case in which a subscriber station requests a handoff to a serving base station, receives a response message, and rejects the handoff using information of the received response message because a target base station list contained in the response message received in the subscriber station is not proper, according to an embodiment of the present invention.
Meanwhile, messages used in each procedure for achieving the embodiments are messages used in performing the conventional handover. However, the present invention is achieved by adding parameters described in Tables 16 and 17 proposed by the present invention to each of the messages.
Hereinafter, a case in which a base station commands a forced handover will be described with reference to FIG. 8. FIG. 8 is a flow diagram illustrating a procedure by which a base station forces a handover in a broadband wireless access communication system according to an embodiment of the present invention.
Referring to FIG. 8, a base station determines a handover for a mobile subscriber station as described in FIG. 7. Accordingly, since a procedure for steps 811, 813, 815, 817, 819, 821, 823, 825, 827, and 829 in FIG. 8, and 829 is the same as that for steps 711, 713, 715, 717, 719, 721, 723, 725, 727, and 729 in FIG. 7, respectively, a description about the procedure will be omitted.
A serving base station 840 determines object base stations among a plurality of target base stations to which a mobile subscriber station can be handed over, transmits a HO_notification_confirm message to the object base station through step 829, and then transmits a list of the determined target base stations, to which a mobile subscriber station can be handed over, to the corresponding mobile subscriber station through a MOB_HO_RSP message.
Meanwhile, after the procedure, the present invention enables the following process to be performed. That is, in a case in which the MOB_HO_RSP message is transmitted, when the MOB_HO_RSP message containing information signifying that the MOB_HO_RSP message is a message of a forced handover is transmitted in step 831, for instance, the MOB_HO_RSP message containing information (HO Type=1) reporting a forced handover is transmitted, the mobile subscriber station 800 having received the MOB_HO_RSP message does not reject the forced handover instruction. Accordingly, the mobile subscriber station 800 receives the MOB_HO_RSP message containing information (HO Type=1) of the forced handover, and must perform a handover procedure to a base station, to which the mobile subscriber station 800 must be handed over, contained in the MOB_HO_RSP message. That is, the mobile subscriber station 800 transmits a MOB_HO_IND message to the serving base station 840 in step 833, releases a link with the serving base station 840 in step 835, and starts a connection with the corresponding base station to which the mobile subscriber station 800 must be handed over in step 837.
Meanwhile, in order to signify that the MOB_HO_RSP message is a forced handover message, the 'HO Type' field is added to the MOB_HO_RSP message as shown in Table 16, and then the MOB_HO_RSP message including the 'HO Type' field is transmitted.
For instance, as described above, when the 'HO Type' field is set to have a value of 1, the mobile subscriber station having received the MOB_HO_RSP message recognizes that the MOB_HO_RSP message is a forced handover message, and then does not reject the determined handover. That is, the mobile subscriber station receives the MOB_HO_RSP message and then must perform a handover procedure to one selected base station among the base stations, to which the mobile subscriber station 800 must be handed over, contained in the MOB_HO_RSP message. When the number of the base stations, to which the mobile subscriber station 800 must be handed over, contained in the MOB_HO_RSP message is one, the mobile subscriber station must unconditionally perform a handover procedure to the base station to which the mobile subscriber station 800 must be handed over.
Meanwhile, when the mobile subscriber station transmits the MOB_HO_IND message to the serving base station, it is possible to generate and transmit the MOB_HO_RSP message having the form as shown in Table 17. That is, the mobile subscriber station can select the type of the MOB_HO_IND message and transmit the selected type of MOB_HO_IND message. Herein, since the MOB_HO_IND message is a message transmitted when the mobile subscriber station cannot reject or cancel a handover, it is preferred that the value of the 'HO Indicator Type' field described in Table 17 is set to be 00 and then the MOB_HO_IND message is transmitted. Herein, a case in which the value of the 'HO Indicator Type' field is set to be 00 is a case in which the mobile subscriber station releases a link with the serving base station and performs a normal handover procedure.
Hereinafter, a case in which the mobile subscriber station rejects or cancels a handover being performed will be described with reference to FIGS. 9 and 10.
Herein, cancellation of the handover represents a case in which the mobile subscriber station randomly stops the handover procedure before the serving base station selects target base stations and transmits a MOB_HO_RSP message to the mobile subscriber station, that is, the mobile subscriber station receives the handover response message including the list of the target base stations, in performing the handover. Further, the rejection of the handover represents a case in which the mobile subscriber station randomly stops a determined handover procedure after the serving base station selects target base stations and transmits a MOB_HO_RSP message to the mobile subscriber station, that is, the mobile subscriber station receives the handover response message including the list of the target base stations, in performing the handover.
First, a case in which the mobile subscriber station cancels a handover being performed will be described with reference to FIG. 9, and then a case in which the mobile subscriber station rejects a determined handover will be described with reference to FIG. 10.
FIG. 9 is a flow diagram illustrating a procedure by which a mobile subscriber station cancels a handover in a broadband wireless access communication system according to an embodiment of the present invention.
Referring to FIG. 9, the mobile subscriber station 900 receives information on neighbor base stations from a serving base station 940 in step 911 and determines whether to perform a scanning or not in steps 913 and 915. Then, the mobile subscriber station 900 scans the CINRs of the neighbor base stations in step 917, determines the change of the serving base station 940 in step 919, and transmits a MOB_HO_REQ message to the serving base station 940 in step 921. Herein, the serving base station 940 refers to the received MOB_HO_REQ message in step 923 and transmits HO_notification messages to corresponding recommended base stations in steps 925 and 927. Therefore, a handover procedure is performed. Next, in step 925, the recommended base stations having received the HO_notification messages transmit HO_notification_response messages containing information regarding whether or not the recommended base stations can perform the handover procedure to the serving base station 940 in step 928. Then, the serving base station 940 having received the HO_notification_response messages determines a base station to which the mobile subscriber station 900 is to be handed over to, of the recommended base stations having sent the response messages, and transmits a HO_notification_confirm message to the determined base station in steps 931 and 933, thereby causing the determined base station to prepare the handover so that the mobile subscriber station 900 can be handed over to the determined base station.
Meanwhile, when the mobile subscriber station 900 intends to cancel the handover while the handover procedure is performed, the mobile subscriber station 900 determines to cancel the handover in step 929. Then, the mobile subscriber station 900 transmits the MOB_HO_IND message containing cancel determination information (i.e., the value of HO indicator type is set to be 01) to the serving base station 940 in step 932, thereby canceling the handover procedure being performed in step 934.
Herein, a method for including the cancel determination information into the MOB_HO_IND message can be achieved by adding the 'HO indicator type' field as described in Table 17. That is, the serving base station 940 receives the MOB_HO_IND message transmitted from the mobile subscriber station 900 in step 932, confirms the information of the 'HO indicator type' field added to the message, and recognizes that the MOB_HO_IND message is a message reporting the cancel of the handover.
For instance, the 'HO indicator type' field may include two bits and has a value of 01 as described above, thereby signifying that the MOB_HO_IND message is a cancel message. Then, the serving base station 940 having received the MOB_HO_IND message containing the handover cancel message information stops the handover procedure being performed and continuously maintains a link with the mobile subscriber station 900 in step 934.
Herein, the procedure is classified according to a case (step 93 1) in which the MOB_HO_IND message reporting the cancel of the handover is received by the serving base station 940 after the HO_notification_confirm message has been transmitted from the serving base station 940 to a target base station, and a case (step 933) in which the MOB_HO_IND message reporting the cancel of the handover is received by the serving base station 940 before the HO_notification_confirm message is transmitted from the serving base station 940 to the target base station.
That is, after transmitting the HO_notification message to the target base station (step 927) and then receiving the HO_notification_response message from the target base station (step 928), the serving base station 940 selects a target base station to which the mobile subscriber station 900 can be actually handed over. Herein, when the serving base station 940 determines the target base station to which the mobile subscriber station 900 can be actually handed over, the serving base station 940 transmits the HO _notification_confirm message to the selected corresponding target base station (step 931), thereby enabling the corresponding target base station to prepare the handover so that the mobile subscriber station 900 can be handed over to the corresponding target base station.
However, when the mobile subscriber station 900 transmits the MOB_HO_IND message in order to report the cancelation of the handover before the HO_notification_confirm message is transmitted from the serving base station 940 to the target base station (step 933), the serving base station 940 performs a different operation. Hereinafter, this operation will be described in detail.
That is, when the MOB_HO_IND message reaches the serving base station 940 (step 932) before the serving base station 940 transmits the HO_notification_confirm message to the target base station (step 933), the serving base station 940 cancels every handover procedure (step 934). Accordingly, the handover is cancelled.
In contrast, a case in which the MOB_HO_IND message is transmitted to the serving base station 940 (step 932) after the transmission of the HO_notification_confirm message (step 931) is a case in which the serving base station 940 has already transmitted the HO_notification_confirm message to the target base station (step 931) and has reported the handover. Accordingly, on receiving the MOB_HO_IND message from the mobile subscriber station 900, the serving base station 940 must transmit the message to the corresponding target base station again to report the cancellationof the handover.
Herein, since the HO_notification_confirm message transmitted from the serving base station 940 to the target base station is used in both a case for reporting the performance of a normal handover and a case for reporting the cancellation of the handover, the two cases are distinguished by the 'Confirm type' field as shown in Table 18. Herein, the 'Confirm type' field has a length of 1 bit. Accordingly, when the 'Confirm type' field has a value of 0, the HO_notification_confirm message reports the performance of a normal handover. In contrast, when the 'Confirm type' field has a value of 1, the HO_notification_confirm message reports the cancel of the handover.
Further, a case in which the handover is cancelled is a case in which a handover procedure has been performed as a result of the mobile subscriber station 900 going away from the serving base station 940 and approaching one of neighbor base stations, but the mobile subscriber station 900 must be handed over to the serving base station 940 again as a result of the mobile subscriber station 900 approaching the original serving base station 940 again during the performance of the handover procedure.
Herein, according to the prior art, after being handed over to a neighbor base station, a mobile subscriber station must be handed over to an original serving base station again. Further, in a special situation, there may occur a case which such a handover must be performed continuously and repeatedly. However, according to the present invention, an unnecessary handover is not repeated and a connection with a serving base station can be continuously maintained.
Hereinafter, a case in which the mobile subscriber station rejects a determined handover will be described with reference to FIG. 10.
FIG. 10 is a flowchart illustrating a procedure by which a mobile subscriber station rejects a handover in a broadband wireless access communication system according to an embodiment of the present invention.
Referring to FIG. 10, the mobile subscriber station 1000 receives information on neighbor base stations from a serving base station 1040 in step 1011 and determines whether to perform a scanning or not in steps 1013 and 1015. Then, the mobile subscriber station 1000 scans the CINRs of the neighbor base stations in step 1017, determines the change of the serving base station 1040 in step 1019, and transmits a MOB_HO_REQ message to the serving base station 1040 in step 1021. Then, the serving base station 1040 refers to the received MOB_HO_REQ message in step 1023 and transmits HO_notification messages to corresponding recommended base stations in steps 1025 and 1027. Meanwhile, the serving base station 1040 receives HO_notification_response messages from the corresponding recommended base stations, selects target base stations according to the message reception result, and transmits a MOB_HO_RSP message to the mobile subscriber station 1000 in step 1035. Therefore, a handover is determined.
That is, a procedure for steps 1011, 1013, 1015, 1017, 1019, 1021, 1023, 1025, 1027, 1029, 1031, 1033, and 1035 in FIG. 10 is identical to that for steps 611, 613, 615, 617, 619, 621, 623, 625, 627, 629, 631, 633, and 635 in FIG. 6,respectively.
Meanwhile, after the target base stations to which the mobile subscriber station 1000 can be handed over are determined and the mobile subscriber station 1000 receives the MOB_HO_RSP message from the serving base station 1040, when the mobile subscriber station 1000 intends to reject the determined handover, the mobile subscriber station 1000 determines a handover rejection in step 1037 and transmits MOB_HO_IND message containing rejection determination information to the serving base station 1040, thereby rejecting the determined handover.
Herein, a method for including the rejection determination information into the MOB_HO_IND message can be achieved by adding the 'HO indicator type' field as described in Table 17. That is, the serving base station 1040 having received the MOB_HO_IND message confirms the information of the 'HO indicator type' field added to the message, and recognizes that the MOB_HO_IND message is a message reporting the rejection of the handover.
For instance, the 'HO indicator type' field may include two bits and has a value of 01 as described above, thereby signifying that the MOB_HO_IND message is a rejection message. Then, the serving base station 1040 having received the MOB_HO_IND message containing the handover rejection message information stops the determined handover procedure and continuously maintains a link with the mobile subscriber station 1000 in step 1041. Herein, since the serving base station 1040 has already selected the target base stations and has transmitted HO_notification_confirmation messages to the target base stations, the target base stations judges that the mobile subscriber station 1000 performs the handover procedure. Accordingly, it is preferred that the serving base station 1040 notifies the target base stations of the stop of the handover.
Meanwhile, a case in which the handover is rejected is a case in which the mobile subscriber station 1000 has received a HO_RSP message from the serving base station 1040, but does not select a proper target base station because there is no base station satisfying a predetermined condition from among the target base stations contained in the message. That is, since the mobile subscriber station 1000 cannot be handed over to any base station of the target base stations contained in the message transmitted from the serving base station 1040, it is preferred that the mobile subscriber station 1000 rejects the handover.
In the above description, a transmission procedure of messages exchanged between a mobile subscriber station and base stations in performing a procedure of a forced handover, a cancel procedure of a handover, and a rejection procedure of a handover performed in various circumstances according to the present invention has been described.
Hereinafter, a procedure performed by the mobile subscriber station according to embodiments of the present invention will be described with reference to FIGS. 11 and 14.
1. Handover Forced By A Base Station
FIG. 11 is a flowchart illustrating a procedure by which a base station forces a handover in a broadband wireless access communication system according to a first embodiment of the present invention.
Referring to FIG. 11, as described above, a mobile subscriber station receives a MOB_HO_RSP message from a serving base station while a handover procedure is performed in step 1100. Herein, the MOB_HO_RSP message contains the lists of target base stations selected by the serving base station. Accordingly, the mobile subscriber station confirms the lists of the target base stations through the MOB_HO_RSP message and determines one base station to be a designated target base station in step 1103.
Further, as described in FIG. 8 according to the present invention, when the 'HO Type' field of the MOB_HO_RSP message has been set to have a value of 1 in step 1105, the MOB_HO_RSP message becomes a message signifying that the serving base station forces the mobile subscriber station to be inevitably handed over to the target base stations. Accordingly, the mobile subscriber station does not reject the determined handover procedure and transmits a MOB_HO_IND message in step 1109. Further, the mobile subscriber station releases a connection with the serving base station in step 1111.
In contrast, when the 'HO Type' field of the MOB_HO_RSP message has been set to have a value of 0, since the MOB_HO_RSP message is not a message representing a forced handover, the mobile subscriber station can reject the handover according to its own judgment. Accordingly, when the mobile subscriber station rejects the handover instead of being handed over to the target base stations in step 1113, the mobile subscriber station sets the 'HO indicator type' field constituting the MOB_HO_IND message to have a value of 10 and transmits the MOB_HO_IND message in step 1115 as described above. In contrast, when the mobile subscriber station is normally handed over to the target base stations, the mobile subscriber station sets the 'HO indicator type' field to have a value of 00, transmits the MOB_HO_IND message to the serving base station in step 1109, and releases a connection with the serving base station in step 1111.
Hereinafter, a procedure by which a mobile subscriber station cancels or rejects a handover according to predetermined conditions during the handover will be described in detail with reference to FIGS. 12 and 14.
2. The Cancellation and Rejection of a Handover According to a Threshold Value.
FIG. 12 is a flowchart illustrating a procedure by which a mobile subscriber station cancels or rejects a handover in a broadband wireless access communication system according to a second embodiment of the present invention.
Referring to FIG. 12, the mobile subscriber station compares the CINR of a serving base station with a predetermined threshold value and determined whether to perform a handover procedure or not. Further, while performing the handover procedure, the mobile subscriber station determines to cancel the handover by means of a second threshold value different from the first threshold value.
First, the mobile subscriber station scans the CINR of the serving base station in step 1200. As a result of the scanning, when the CINR of the serving base station is smaller than a first predetermined threshold value, the mobile subscriber station determines that it is difficult to exchange data with the serving base station, and measures the CINRs of neighbor base stations in step 1211. That is, in order to scan the CINRs of the neighbor base stations, the mobile subscriber station transmits a MOB_SCN_REQ message to the serving base station in step 1207 and receives a MOB_SCN_RSP message from the serving base station in step 1209.
The mobile subscriber station having received the MOB_SCN_RSP message measures the CINRs of the neighbor base stations in step 1211. As a result of the measurement, when the CINR of the serving base station is smaller than a second predetermined threshold value and the CINR of one of the neighbor base stations in step 1213, the mobile subscriber station determines a handover and transmits a MOB_HO_REQ message to the serving base station in step 1215. In contrast, when such a condition is not satisfied, returns to step 1200. That is, the mobile subscriber station repeats the aforementioned procedure.
Meanwhile, while the MOB_HO_REQ message is transmitted to the serving base station and the handover procedure is performed according to the present invention, the mobile subscriber station continuously measures the CINR of the serving base station and compares the CINR of the serving base station with the first critical value. As a result of the comparison, when the CINR of the serving base station is still smaller than the first threshold value, the handover procedure is normally performed. In contrast, when the CINR of the serving base station grows larger than the first threshold value due to the movement of the mobile subscriber station in step 1217, the mobile subscriber station cancels the handover procedure being performed in step 1219. Accordingly, when the mobile subscriber station determines to cancel the handover procedure in this way, the mobile subscriber station transmits a MOB_HO_IND message (i.e., the value of the 'HO Indicator Type' field is set to be 01) containing handover cancel information to the serving base station in step 1221. Then, the serving base station having received the MOB_HO_IND message cancels the handover procedure and continuously maintains a connection with the mobile subscriber station.
Meanwhile, when the CINR of the serving base station is still smaller than the first threshold value during the performance of the handover as described above, the serving base station normally performs the handover procedure and transmits a MOB_HO_RSP message to the mobile subscriber station. Next, the mobile subscriber station having received the MOB_HO_RSP message from the serving base station in step 1223 confirms a list of target base stations contained in the MOB_HO_RSP message, determines one target base station to be a designated target base station according to conditions in step 1225.
Herein, when the MOB_HO_RSP message is a forced handover message, that is, when the 'HO Type' field contained in the MOB_HO_RSP message has been set to have a value of 1, a forced handover is performed according to the procedure described in FIG. 11. In other words, the mobile subscriber station transmits the MOB_HO_IND message in step 1237 and release a connection with the serving base station in step 1239. Further, the mobile subscriber station is handed over to one base station contained in the list of the target base stations transmitted from the serving base station.
In contrast, when the MOB_HO_RSP message is not the forced handover message, that is, when the 'HO Type' field contained in the MOB_HO_RSP message has been set to have a value of 0, it is possible to continuously measure the CINR of the serving base station according to the second embodiment of the present invention. That is, when the CINR of the serving base station is larger than the first threshold value in step 1229, the handover can be cancelled in step 1219. Otherwise, the handover can be normally performed. In contrast, when the CINR of the serving base station is still smaller than the first threshold value, whether to perform a normal handover procedure to the target base station or not is determined in step 1231. From the result of the determination, the handover is rejected in step 1233 or the handover is performed in steps 1237 and 1239.
3. Cancel and Rejection of a Handover According to the Comparison of CINRs
FIG. 13 is a flowchart illustrating a procedure by which a mobile subscriber station cancels or rejects a handover in a broadband wireless access communication system according to a third embodiment of the present invention.
The third embodiment of the present invention shown in FIG. 13 performs the same procedure as that of the second embodiment of FIG. 12, but a difference exists in reference values in performing the determination of the handover and the determination of the handover cancellation.
Referring to FIG. 13, the mobile subscriber station compares the CINR of a serving base station with a predetermined threshold value and determined whether to perform a handover procedure or not. Further, while performing the handover procedure, the mobile subscriber station determines the handover or the cancellation of the handover by means of another threshold value different from the threshold value.
First, the mobile subscriber station scans the CINR of the serving base station in step 1300. As a result of the scanning, when the CINR of the serving base station is smaller than a predetermined threshold value, the mobile subscriber station determines that it is difficult to exchange data with the serving base station, and measures the CINR of neighbor base stations in step 1311. That is, in order to scan the CINR of the neighbor base stations, the mobile subscriber station transmits a MOB_SCN_REQ message to the serving base station in step 1307 and receives a MOB_SCN_RSP message from the serving base station in step 1309.
The mobile subscriber station having received the MOB_SCN_RSP message measures the CINR of the neighbor base stations in step 1310. As a result of the measurement, when the CINR of the serving base station is smaller than the CINR of one of the neighbor base stations in step 1311, the mobile subscriber station determines a handover and transmits a MOB_HO_REQ message to the serving base station in step 1312. In contrast, when such a condition is not satisfied, returns to step 1300. That is, the mobile subscriber station repeats the aforementioned procedure.
Meanwhile, while the MOB_HO_REQ message is transmitted to the serving base station and the handover procedure is performed according to the present invention, the mobile subscriber station continuously measures the CINR of the serving base station and compares the CINR of the serving base station with the CINR of the neighbor base stations. As a result of the comparison, when the CINR of the serving base station is still smaller than the CINR of the neighbor base stations, the handover procedure is normally performed. In contrast, when the CINR of the serving base station grows larger than the CINR of the neighbor base stations due to the movement of the mobile subscriber station in step 1313, the mobile subscriber station cancels the handover procedure being performed in step 1315. Accordingly, when the mobile subscriber station determines to cancel the handover procedure in this way, the mobile subscriber station transmits a MOB_HO_IND message (i.e., the value of the 'HO Indicator Type' field is set to be 01) containing handover cancel information to the serving base station in step 1317. Then, the serving base station having received the MOB_HO_IND message cancels the handover procedure and continuously maintains a connection with the mobile subscriber station.
Meanwhile, when the CINR of the serving base station is still smaller than the CINR of the neighbor base stations during the performance of the handover, the serving base station normally performs the handover procedure and transmits a MOB_HO_RSP message to the mobile subscriber station. Next, the mobile subscriber station having received the MOB_HO_RSP message from the serving base station in step 1319 confirms a list of target base stations contained in the MOB_HO_RSP message, determines one target base station to be a designated target base station according to conditions in step 1321.
Herein, when the MOB_HO_RSP message is a forced handover message, that is, when the 'HO Type' field contained in the MOB_HO_RSP message has been set to have a value of 1, a forced handover is performed according to the procedure described in FIG. 11. In other words, the mobile subscriber station transmits the MOB_HO_IND message in step 1333 and releases a connection with the serving base station in step 1335. Further, the mobile subscriber station is handed over to one base station contained in the list of the target base stations transmitted from the serving base station.
In contrast, when the MOB_HO_RSP message is not the forced handover message, that is, when the 'HO Type' field contained in the MOB_HO_RSP message has been set to have a value of 0, it is possible to continuously measure the CINR of the serving base station according to the third embodiment of the present invention. That is, when the CINR of the serving base station is larger than the CINR of the neighbor base stations in step 1325, the handover can be cancelled in step 1315. Otherwise, the handover can be normally performed. In contrast, when the CINR of the serving base station is still smaller than the CINR of the neighbor base stations, whether to perform a normal handover procedure to the target base station or not, is determined in step 1327. From the result of the determination, the handover is rejected in step 1329 or the handover is performed in steps 1333 and 1335.
As describe above, when the handover has been rejected according to the circumstances of the mobile subscriber station in step 1331, the mobile subscriber station transmits a MOB_HO_REQ message to the serving base station again in step 1312. That is, a case in which the handover is rejected is a case in which the mobile subscriber station has tried to be handed over to the neighbor base station because the serving base station has bad transmission/reception conditions, but the handover is rejected because the neighbor base station also has bad transmission/reception conditions. Herein, since the serving base station may continuously have the bad transmission/reception conditions, it is preferred to transmit a MOB_HO_REQ message to the serving base station again (step 1312) and find target base stations.
However, since the reliability for recommended base stations contained in the MOB_HO_REQ message and selected by the mobile subscriber station may be reduced, it may be preferred to scan all neighbor base stations one more time and to find new recommended base stations having a high reliability. Hereinafter, the latter case will be described with reference to FIG. 14.
FIG. 14 is a flowchart illustrating a procedure by which a mobile subscriber station cancels or rejects a handover in a broadband wireless access communication system according to a third embodiment of the present invention.
Referring to FIG. 14, the third embodiment of FIG. 14 has the same procedure as that of the second embodiment of FIG. 13, except for the aforementioned difference. That is, when the mobile subscriber station rejects the handover in step 1429, the mobile subscriber station transmits a MOB_HO_IND message (i.e., the value of the 'HO Indicator Type' field is set to be 10) representing a handover rejection to the serving base station in step 1431.
Then, the mobile subscriber station performs an initial scanning in step 1400 in order to select new recommended base stations. That is, the mobile subscriber station measure the CINR of the serving base station again, compares the measured CINR of the serving base station with a predetermined threshold value set in advance in step 1403, and performs a scanning for neighbor base stations again in steps 1407, 1409, and 1410. All steps after step 1411 are identical to those of FIG. 13.
As described above, in order to support the mobility of a mobile subscriber station, the present invention further incorporates a function by which a base station enables a mobile subscriber station to be forcedly handed over and a function by which a mobile subscriber station rejects a handover request received from a base station to the conventional handover procedure in a multi-cell structure. In addition, the present invention further incorporates a function by which a base station enables a mobile subscriber station cancels or rejects a handover procedure to maintain a connection with a serving base station again due to the change of the moving direction of the mobile subscriber station while the mobile subscriber station is being handed over from the serving base station to a target base station. Therefore, a handover can be performed with certainty and efficiency.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Contents4
15 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP3713273A4 | Cited by | European Patent Office (EPO) | Search report |
| EP1775983A1 | Cited by | European Patent Office (EPO) | Search report |
| US11582650B2 | Cited by | United States of America | Applicant |
| EP1867181A2 | Cited by | European Patent Office (EPO) | Search report |
| GB2456912A | Cited by | United Kingdom | Search report |
| WO2007033558A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US10880791B2 | Cited by | United States of America | Applicant |
| US10582434B2 | Cited by | United States of America | Applicant |
| FR2947137A1 | Cited by | France | Search report |
| US11716673B2 | Cited by | United States of America | Applicant |
| GB2456912B | Cited by | United Kingdom | Search report |
| US9351215B2 | Cited by | United States of America | Applicant |
| EP1867181A4 | Cited by | European Patent Office (EPO) | Search report |
| CN100450023C | Cited by | China | Search report |
| WO2008040245A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US12464421B2 | Cited by | United States of America | Applicant |
| US11516727B2 | Cited by | United States of America | Applicant |
| WO2012171910A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO2010146095A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8693394B2 | Cited by | United States of America | Applicant |
| EP4615148A3 | Cited by | European Patent Office (EPO) | Search report |
| US7831253B2 | Cited by | United States of America | Applicant |
| KR100883790B1 | Cited by | Republic of Korea | Search report |
| WO2016200660A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO0139538A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
| US5267261A | Cites | United States of America | Search report |
| WO9805175A2 | Cites | World Intellectual Property Organization (WIPO) | Search report |
28 members in 9 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 20030061945 | Republic of Korea | A | |
| 20030061945 | Republic of Korea | A | |
| 2003061945 | Republic of Korea | – | |
| 2003061945 | – | – | – |
| KR20030061945 | – | – | – |
Members28
| Document | Office | Kind | |
|---|---|---|---|
| EP1513364A2This record | European Patent Office (EPO) | A2 | |
| KR20050024124A | Republic of Korea | A | |
| AU2004303040A1 | Australia | A1 | |
| CA2535912A1 | Canada | A1 | |
| WO2005025091A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2005096051A1 | United States of America | A1 | |
| EP1513364A3 | European Patent Office (EPO) | A3 | |
| RU2006106706A | Russian Federation | A | |
| KR100689508B1 | Republic of Korea | B1 | |
| CN1934798A | China | A | |
| EP1791385A1 | European Patent Office (EPO) | A1 | |
| EP1791386A1 | European Patent Office (EPO) | A1 | |
| JP2007535205A | Japan | A | |
| AU2004303040B2 | Australia | B2 | |
| RU2321970C2 | Russian Federation | C2 | |
| US2010029279A1 | United States of America | A1 | |
| JP4489774B2 | Japan | B2 | |
| CN101820654A | China | A | |
| US7877093B2 | United States of America | B2 | |
| CN102158914A | China | A | |
| US8112088B2 | United States of America | B2 | |
| CN1934798B | China | B | |
| US2012094711A1 | United States of America | A1 | |
| CN101820654B | China | B | |
| US8374611B2 | United States of America | B2 | |
| CA2535912C | Canada | C | |
| EP1791386B1 | European Patent Office (EPO) | B1 | |
| CN102158914B | China | B |
12 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Application deemed to be withdrawnWithdrawn18D | 18D | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWNSTAA | STAA | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: EXAMINATION IS IN PROGRESSSTAA | STAA | |
| Designation fees paidAKX | AKX | |
| First examination report despatched17Q | 17Q | |
| Designated contracting statesAK | AK | |
| Request for extension of the european patentAX | AX | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | |
| Request for examination filed17P | 17P | |
| Designated contracting statesAK | AK | |
| Request for extension of the european patentAX | AX | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI |
Numbers
- Publication
- 1513364
- Publication, DOCDB
- 1513364
- Publication, EPODOC
- EP1513364
- Application
- 4021156
- Application, DOCDB
- 04021156
- Application, EPODOC
- EP20040021156
Titles3
- German
- Verfahren zum gezwungenen Weiterreichen in einem drahtlosen Breitbandkommunikationssystem
- English
- Method for compulsorily performing handover in broadband wireless communication system
- French
- Procédé pour forcer l'opération de transfert de la communication dans un système sl de communication sans fil à large bande
Classification
- CPC, 9
- H04W36/0058
- H04W36/0079
- H04L5/0053
- H04W36/38
- H04W92/20
- H04W36/08
- H04W36/302
- H04W36/305
- H04B17/345
- IPC, 2
- H04B7 26
- H04W36 08
Designated states2
- Contracting states, 1
- Türkiye
- Extension states, 1
- North Macedonia