Abstract:
A broadband wireless access communication system including a serving BS which broadcasts a MOB_NBR-ADV message to an MS is provided. A method for configuring the MOB_NBR-ADV message is also provided, and includes adding a specific field, which represents whether at least one information field constituting the MOB_NBR-ADV message exists, to the MOB_NBR-ADV message, determining if at least one information field is included in the MOB_NBR-ADV message, and determining a bit value of the specific field according to whether at least one information field is included in the MOB_NBR-ADV message.

Description:
PRIORITY  
       [0001]     This application claims priority to an application entitled “System and Method for Flexibly Configuring Length of Neighbor Base Station Information in Broadband Wireless Access Communication System” filed in the Korean Industrial Property Office on Nov. 4, 2004 and assigned Serial No. 2004-89488, the contents of which are incorporated herein by reference.  
       BACKGROUND OF THE INVENTION  
       [0002]     1. Field of the Invention  
         [0003]     The present invention relates to a broadband wireless access communication system, and more particularly to a system and a method for configuring a neighbor base station advertisement (hereinafter referred to as ‘MOB_NBR-ADV’) message including neighbor base station information.  
         [0004]     2. Description of the Related Art  
         [0005]     In a next generation communication system, that is, a 4 th  generation (hereinafter referred to as ‘4G’) communication system, much research has been undertaken to provide users with services which have various qualities of service (hereinafter referred to as ‘QoS’) and to support a transmission speed of about 100 Mbps. Particularly, in the current  4 G communication system, research is being vigorously pursued to support high-speed services to broadband wireless access (hereinafter referred to as ‘BWA’) communication systems such as wireless local area network (hereinafter referred to as ‘WLAN’) communication systems and wireless metropolitan area network (hereinafter referred to as ‘WMAN’) communication systems by ensuring both mobility and various QoSs. A typical communication system for this purpose is an IEEE (Institute of Electrical and Electronics Engineers) 802.16 communication system.  
         [0006]     The IEEE 802.16 communication system is a communication system which applies an orthogonal frequency division multiplexing (hereinafter referred to as ‘OFDM’)/orthogonal frequency division multiple access (hereinafter referred to as ‘OFDMA’) scheme in order to support a broadband transmission network to a physical channel of the WMAN system.  
         [0007]     A structure of an IEEE 802.16 communication system will now be described with reference to  FIG. 1 , which schematically illustrates the common IEEE 802.16e communication system.  
         [0008]     Referring to  FIG. 1 , the IEEE 802/16e communication system has a multiple cell structure, for example, it has cells  100  and  150 . The IEEE 802.16e communication system also includes a base station (hereinafter referred to as ‘BS’)  110  controlling the cell  100 , a BS  140  controlling the cell  150 , and a plurality of mobile stations (hereinafter referred to as ‘MS’)  111 ,  113 ,  130 ,  151 , and  153 . Signal transmission/reception between the BSs  110 ,  140  and the MSs  111 ,  113 ,  130 ,  151 , and  153  is implemented using the OFDM/OFDMA scheme. In addition, from among the MSs  111 ,  113 ,  130 ,  151 , and  153 , the MS  130  exists in a boundary area between the cells  100  and  150 , that is, a handover area. Thus, the BS  100  or the BS  150  must be capable of supporting handover of the MS  130 .  
         [0009]     For example, when the MS  130  moves to an area covered by the cell  150  while it communicates with the BS  110  in the cell  100 , and the MS  130  undergoes handover to the BS  140 , the MS  130  must conduct a network re-entry procedure with the BS  140 . This is because the BS  110  and the BS  140  have different physical layers and different medium access control (hereinafter referred to as ‘MAC’) layer structures.  
         [0010]     If an MS conducts a network re-entry procedure during handover from a serving BS, in which the MS is currently located, to a neighbor BS as stated above, a data service in transmission/reception is interrupted and must newly be started after the MS completes the handover to the neighbor BS. In order to handover to the neighbor BS in this way, the MS must be capable of recognizing neighbor BS information. The neighbor BS information may be recognized by receiving an MOB_NBR-ADV message which each BS periodically broadcasts.  
         [0011]     Hereinafter, an MOB-NBR-ADV message format will be described with reference to  FIGS. 2A and 2D , which illustrate a format of a common MOB_NBR-ADV message.  
         [0012]     Referring to  FIGS. 2A and 2D , the MOB_NBR-ADV message is configured of a plurality of information elements (hereinafter referred to as ‘IE’), and the IEs are as follows:  
         [0013]     Management Message Type: represents the type of a transmitted message:  
         [0014]     Operator ID: represents an unique identifier assigned to a operator,  
         [0015]     Configuration Change Count: each time message configuration changes, increases by 1 to indicate whether a corresponding message has changed;  
         [0016]     Fragmentation Index: represents the number of times that a message is transmitted when the MOB_NBR-ADV message is fragmented and the fragmented messages are separately transmitted;  
         [0017]     Total Fragmentation: represents the total number of fragmented messages;  
         [0018]     Skip-Optional-Fields Flag: indicates a BS-ID when the BS-ID is omitted in a corresponding message;  
         [0019]     N-NEIGHBORS: represents information on how many neighbor BSs are included in a current message; that is, it represents the number of neighbor BSs;  
         [0020]     Length: represents information field length according to BS-Ids;  
         [0021]     PHY Profile ID: indicates an information ID of a radio channel used in a corresponding BS;  
         [0022]     FA Index: indicates an inherent ID representing a frequency allocated to a corresponding BS;  
         [0023]     BS EIRP: represents transmission power intensity of a corresponding BS;  
         [0024]     Neighbor BS-ID: indicates IDs of neighbor BSs;  
         [0025]     Preamble Index: indicates an ID of a preamble to be used in a corresponding sector of a corresponding BS;  
         [0026]     HO Process Optimization: dividedly indicates information about indispensable procedures and information about omissible procedures during handover to a corresponding BS;  
         [0027]     Scheduling Service Supported: indicates QoS classes supportable by a corresponding BS, from among various QoS classes predefined between BSs;  
         [0028]     Available Radio Resource: indicates the degree of availability of radio channel resources of a corresponding BS;  
         [0029]     Handoff Neighbor Preference: defines the degree of logical preference when a serving BS controls an MS to handover to a neighbor BS;  
         [0030]     DCD Configuration Change Count: indicates the DCD (Downlink Channel Descriptor) information serial number of a corresponding neighbor BS;  
         [0031]     UCD Configuration Change Count: indicates the UCD (Uplink Channel Descriptor) information serial number of a corresponding neighbor BS;  
         [0032]     Other neighbor information (hereinafter referred to as ‘TLV (Type/Length/Value) Encoded Neighbor Information’): represents all information related to a neighbor BS other than the aforementioned information.  
         [0033]     Now, the MOB_NBR-ADV message will be described in more detail.  
         [0034]     The MS, having received the MOB_NBR-ADV message periodically broadcasted from the serving BS, can acquire scanning information for measuring signal intensities of neighbor BSs. The MS can identify neighbor BSs by using Neighbor BS-ID information included in the MOB_NBR-ADV message, and thus comes to recognize physical frequency band search information, which is necessary for scanning the neighbor BSs, through the Physical Frequency field. In this way, the serving BS periodically broadcasts the MOB_NBR-ADV message to provide information which the MS requires for handover.  
         [0035]     Therefore, the conventional MOB_NBR-ADV message includes a lot of information, and its large size is problematic.  
         [0036]     Here, the MS may require, or may not necessarily require, the information included in the MOB_NBR-ADV depending on the present circumstances. Also, the MOB_NBR-ADV message is not a message which is transmitted to a specific MS, but is a broadcast message which is repeatedly transmitted to many unspecified MSs in very short cycles. On account of this, bandwidth consumption in a radio channel section is very large. In the end, there is a problem in that radio channel resources are wasted because a network operator must include unnecessary information in the MOB_NBR-ADV message.  
       SUMMARY OF THE INVENTION  
       [0037]     Accordingly, the present invention has been made to solve at least the above-mentioned problems occurring in the prior art, and an object of the present invention is to provide a system and a method for configuring an MOB_NBR-ADV message in a broadband wireless access communication system, which can reduce the size of the MOB_NBR-ADV message.  
         [0038]     A further object of the present invention is to provide a system and a method for efficiently using radio channel resources in a broadband wireless access communication system.  
         [0039]     In order to accomplish these objects, in accordance with one aspect of the present invention, there is provided a method for configuring a MOB_NBR-ADV message in a broadband wireless access communication system including a serving BS which broadcasts neighbor BS information to an MS, the method including adding a specific field, which represents whether at least one information field constituting the MOB_NBR-ADV message exists, to the MOB_NBR-ADV message; deciding if at least one information field is included in the MOB_NBR-ADV message; and determining a bit value of the specific field according to whether at least one information field is included in the MOB_NBR-ADV message.  
         [0040]     In accordance with another aspect of the present invention, there is provided a system for configuring a MOB_NBR-ADV message in a broadband wireless access communication system including a serving BS which broadcasts neighbor BS information to an MS, the system including a serving BS for adding a specific field, which represents whether at least one information field constituting the MOB_NBR-ADV message exists, to the MOB_NBR-ADV message, deciding if at least one information field is included in the MOB_NBR-ADV message, and determining a bit value of the specific field according to whether at least one information field is included in the MOB_NBR-ADV message. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0041]     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:  
         [0042]      FIG. 1  is a schematic view illustrating a structure of a common IEEE 802.16e communication system;  
         [0043]      FIGS. 2A and 2D  are views illustrating a format of a common MOB_NBR-ADV message;  
         [0044]      FIGS. 3A  to  3 D are views illustrating a format of a new MOB_NBR-ADV message in accordance with a preferred embodiment of the present invention; and  
         [0045]      FIG. 4  is a flowchart illustrating a process of setting up an NBR_FLAG field when the MOB_NBR-ADV message is configured in accordance with a preferred embodiment of the present invention. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0046]     Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that similar components are designated by similar reference numerals although they are illustrated in different drawings. Also, in the following description, a detailed description of known functions and configurations incorporated herein will be omitted when it may obscure the subject matter of the present invention.  
         [0047]     The present invention proposes a method for newly configuring an MOB_NBR-ADV message in a broadband wireless access communication system. To be specific, whenever a BS periodically broadcasts the MOB_NBR-ADV message, it determines what information fields are to be included in the MOB_NBR-ADV message, and adds to a new field information about whether the information fields exist in order to clarify the information according to the above determination.  
         [0048]     Referring again to the conventional MOB_NBR-ADV message of  FIGS. 2A and 2B , prior to a description of the present invention, an Operator ID field is a field indicating an inherent ID of a BS which transmits the MOB_NBR-ADV message. However, the Operator ID is information which an MS has already recognized through a network entry procedure previously conducted with a serving BS in which the MS is currently located. Thus, the Operator ID is not information which the serving BS must periodically transmit to the MS.  
         [0049]     Also, in the conventional MOB_NBR-ADV message, the Neighbor BS-ID field is included in the message while a bit value of the Skip-Optional-Fields Flag is set to ‘0’ only when a physical layer scheme of a network is an OFDMA scheme. Thus, a broadband wireless access communication system employing an OFDM or single carrier scheme does not include the Neighbor BS-ID field while the bit value of the Skip-Optional-Fields Flag is set to ‘1’.  
         [0050]     Moreover, in the conventional MOB_NBR-ADV message, the HO Process Optimization field need not be necessarily included in the message because there may be a case in which a serving BS cannot support handover to some neighbor BSs.  
         [0051]     Furthermore, in the conventional MOB_NBR-ADV message, fields related to QoS (Quality of Service)s (i.e., Scheduling Service Supported, Available Radio Resource and Handover neighbor Preference fields) are not supportable by all BSs. Even if any BS is capable of supporting the QoS relation information, it cannot always provide the information in a case where it is impossible for the BS to collect neighbor BS information in real-time.  
         [0052]     In conclusion, the aforementioned fields can be omitted from the MOB_NBR-ADV message, and each BS, that is, each network operator, can reduce the length of the MOB_NBR-ADV message by properly inserting or omitting the omissible fields into or from the MOB_NBR-ADV message according to the present invention.  
         [0053]     An MOB_NBR-ADV message format newly proposed in the present invention will be described with reference to  FIGS. 3A  to  3 D, which illustrate the new MOB_NBR-ADV message format in accordance with a preferred embodiment of the present invention.  
         [0054]     Referring to  FIGS. 3A  to  3 D, first, the new MOB_NBR-ADV message includes an NBR-FLAG field which is added to the conventional MOB_NBR-ADV message. Although the size of the NBR_FLAG field is specified by 8 bits in this embodiment of the present invention, it should be noted that a network operator may appropriately change the size according to system situations. In the following description, it is assumed that the NBR_FLAG field has a size of 8 bits.  
         [0055]     In the added NBR_FLAG field of 8 bits, its first 4 bits are used for clarifying whether specific fields exist in the MOB_NBR-ADV message, and its last 4 bits are reserved bits available for future function extension.  
         [0056]     The 4 bits in the NBR_FLAG, which are used for clarifying whether specific fields exist in the MOB_NBR-ADV message, may be configured as follows:  
         [0057]     Bit [ 0 ]: is located in the first place of the 8 bits in the NBR_FLAG field, and informs whether the Operator ID field is included in the MOB_NBR-ADV message. For example, if a value of bit [ 0 ] is ‘0’, this means that the Operator ID field is included in the MOB_NBR-ADV message. Otherwise, if a value of bit [ 0 ] is ‘1’, this means that the Operator ID field is not included in the MOB_NBR-ADV message.  
         [0058]     Bit [ 1 ]: is located in the second place of the 8 bits in the NBR_FLAG field, and informs whether the Neighbor BS-ID field is included in the MOB_NBR-ADV message. For example, if a value of bit [ 1 ] is ‘0’, this means that the Neighbor BS-ID field is included in the MOB_NBR-ADV message. Otherwise, if a value of bit [ 1 ] is ‘1’, this means that the Neighbor BS-ID field is not included in the MOB_NBR-ADV message.  
         [0059]     Bit [ 2 ]: is located in the third place of the 8 bits in the NBR_FLAG field, and informs whether the HO Process Optimization field is included in the MOB_NBR-ADV message. For example, if a value of bit [ 2 ] is ‘0’, this means that the HO Process Optimization field is included in the MOB_NBR-ADV message. Otherwise, if a value of bit [ 2 ] is ‘1’, this means that the HO Process Optimization field is not included in the MOB_NBR-ADV message.  
         [0060]     Bit [ 3 ]: is located in the fourth place of the 8 bits in the NBR_FLAG field, and informs whether QoS related fields are included in the MOB_NBR-ADV message. For example, if a value of bit [ 3 ] is ‘0’, this means that the QoS related fields are included in the MOB_NBR-ADV message. Otherwise, if a value of bit [ 3 ] is ‘1’, this means that the QoS related fields are not included in the MOB_NBR-ADV message.  
         [0061]     Here, the QoS related fields included in the MOB_NBR-ADV message refer to the Scheduling Service Supported field, the Available Radio resource field and the Handover Neighbor Preference field.  
         [0062]     Besides the aforementioned bits, bits [ 4 ] to [ 7 ] are reserved bits.  
         [0063]     For example, if the NBR_FLAG field has a value of ‘1001 0000’, this means that the Operator ID field and the QoS related fields do not exist, but the Neighbor BS-ID field and the HO Process Optimization field exist in the MOB_NBR-ADV message.  
         [0064]     As stated above, by removing unnecessary fields from the MOB_NBR-ADV message and clarifying the presence/absence of the fields in the NBR_FALG field, the size of the MOB_NBR-ADV message can be reduced. That is, it is possible to configure an MOB_NBR-ADV message having flexibility in size (length). In addition, a serving BS may configure and transmit the new MOB_NBR-ADV message according to the present invention every single period or every several periods. That is, when information fields constituting an MOB_NBR-ADV message to be transmitted in a current period must be configured differently from those transmitted in a previous period, the serving BS can newly configure and transmit the MOB_NBR-ADV message according to the preferred embodiment of the present invention.  
         [0065]     Now, a process of setting up the NBR_FLAG field of the MOB_NBR-ADV message will be described with reference to  FIG. 4 , which is a flowchart illustrating the process of setting up the NBR_FLAG field when the MOB_NBR-ADV message is configured in accordance with a preferred embodiment of the present invention.  
         [0066]     Referring to  FIG. 4 , a serving BS must configure first the MOB_NBR-ADV message according to the preferred embodiment of the present invention in order to periodically transmit the MOB_NBR-ADV message. Thus, in step  402 , the serving BS begins to set up an NBR_FLAG field in the MOB_NBR-ADV message, and proceeds to step  404 . In step  404 , the serving BS determines if an Operator ID field is inserted into the MOB_NBR-ADV message. According to is the determination made in step  404 , the serving BS proceeds to step  406  when the Operator ID field is inserted into the MOB_NBR-ADV message, or proceeds to step  408  when the Operator ID field is not inserted.  
         [0067]     In step  406 , the serving BS sets to ‘NBR_FLAG [0]=0’, which means that the MOB_NBR-ADV message includes the Operator ID field, and proceeds to step  410 . In step  408 , the serving BS sets to ‘NBR_FLAG [0]=1’, which means that the MOB_NBR-ADV message does not include the Operator ID field, and proceeds to step  410 .  
         [0068]     In step  410 , the serving BS determines if a Neighbor BS-ID field is inserted into the MOB_NBR-ADV message. According to is the determination made in step  410 , the serving BS proceeds to step  412  when the Neighbor BS-ID field is inserted into the MOB_NBR-ADV message, and proceeds to step  414  when the Neighbor BS-ID field is not inserted.  
         [0069]     In step  412 , the serving BS sets to ‘NBR_FLAG [1]=0’, which means that the MOB_NBR-ADV message includes the Neighbor BS-ID field, and proceeds to step  416 . In step  414 , the serving BS sets to ‘NBR_FLAG [1]=1’, which means that the MOB_NBR-ADV message does not include the Neighbor BS-ID field, and proceeds to step  416 .  
         [0070]     In step  416 , the serving BS determines if an HO Process Optimization field is inserted into the MOB_NBR-ADV message. According to the determination made in step  416 , the serving BS proceeds to step  418  when the HO Process Optimization field is inserted into the MOB_NBR-ADV message, and proceeds to step  420  when the HO Process Optimization field is not inserted.  
         [0071]     In step  418 , the serving BS sets to ‘NBR_FLAG [2]=0’, which means that the MOB_NBR-ADV message includes the HO Process Optimization field, and proceeds to step  422 . In step  420 , the serving BS sets to ‘NBR_FLAG [2]=1’, which means that the MOB_NBR-ADV message does not include the HO Process Optimization field, and proceeds to step  422 .  
         [0072]     In step  422 , the serving BS determines if QoS related fields are inserted into the MOB_NBR-ADV message. According to is the determination made in step  422 , the serving BS proceeds to step  424  when the QoS related fields are inserted into the MOB_NBR-ADV message, and proceeds to step  426  when the QoS related fields are not inserted.  
         [0073]     In step  424 , the serving BS sets to ‘NBR_FLAG [3]=0’, which means that the MOB_NBR-ADV message includes the QoS related fields or, in step  426 , the serving BS sets to ‘NBR_FLAG [3]=1’, which means that the MOB_NBR-ADV message does not include the QoS related fields, and completes the setup of the NBR_FLAG field.  
         [0074]     Although information fields, which may not be included in the MOB_NBR-ADV message, are limited to the Operator ID field, the Neighbor BS-ID field, the HO Process Optimization field and the QoS related fields in the description of  FIG. 4 , these are merely one example. That is, it should be understood that a network operator may configure the new MOB_NBR-ADV message by using other information fields in combination with those stated above. It should be also noted that new information fields constituting the MOB_NBR-ADV message may be added and extended.  
         [0075]     As described above, since a field, which informs whether specific information fields are included in neighbor BS information broadcast message, that is, an MOB_NBR-ADV message, is newly added to the message, and omissible information fields are omitted according to the circumstances of a BS in the present invention, the MOB_NBR-ADV message can be flexibly configured. Therefore, there is an advantage in that the size of the MOB_NBR-ADV message is reduced as compared with that of the existing MOB_NBR-ADV message and thus radio channel resources can be efficiently utilized.  
         [0076]     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.