Title of Invention

METHOD AND SYSTEM FOR TRANSFERRING INFORMATION BETWEEN NETWORK MANAGEMENT ENTITIES OF A WIRELESS COMMUNICATION SYSTEM

Abstract

A method and wireless communication system for transferring management information is shown in figure 1B below. The system includes at least one access point (AP) (110) including a first management entity (150) and a second management entity (155), and at least one wireless transmit/receive unit (WTRU) (105) including a third management entity (165) and a fourth management entity (170). The AP transmits a management information base (MIB) information request action frame including a category field and an action details field to the WTRU. In response to receiving the information request action frame, the WTRU determines whether or not to provide management information to the AP. When the WTRU provides management information to the AP, the WTRU compiles management information stored in a MIB located in the WTRU and transmits a MIB information report action frame to the AP.

Full Text

FIELD OF INVENTION The present invention is related to wireless communication systems. More particularly, the present invention is related to a method and system for communicating management information between a wireless transmit/receive unit (WTRU) and an access point (AP) to optimize radio resource management (RRM). BACKGROUND Wireless local area networks (WLANs) have become more popular because of their convenience and flexibility. As new applications for such networks are being developed, their popularity is expected to significantly increase. Institute of Electrical and Electronics Engineers (IEEE) working groups have defined an IEEE 802.11 baseline standard having extensions which are intended to provide higher data rattrs and other network capabilities. Under the IEEE 802.11 standards, network entities include a management information base (MIB). The MIB may be either a media access control (MAC) layer MIB or a physical (PHY) layer MIB. Data entries in a MIB table use IEEE 802.11 standards. Network management entities (NMEs), connected to a WLAN, communicate with each other by sending frames. There are three types of MAC frames defined by the IEEE 802.11 standards'-1) data frames'. 2) control frames; and 3) management frames. There are also sub-types for each of these frames. For example, an action frame is a sub-type of a management frame. Action frames are further defined by categories. Currently, several action frame categories are defined as follows' 0- spectrum management; 1- quality of service management; 2- direct link protocol; and 3- radio measurement. . A service primitive is an internal signaling message used for inter-layer or inter-protocol entity exchanges, such as between a station management entity (SME) and a MAC layer management entity (MLME), with standardized message contents. Although a particular format of message is not specified by the standards, the standards do specify the content. Service primitives are typically used to initiate, confirm or report a particular action, such as by sending a particular frame for management purposes from one WTRU to another WTRU. In accordance with IEEE 802.11 standards, an SME is incorporated into the WTRU in order to provide correct MAC operation. The SME is a layer-independent entity that may be viewed as residing in a separate management plane or as residing "off to the side." Thus, the SME may be viewed as being responsible for such functions as the gathering of layer-dependent status from the various layer management entities, and similarly setting the value of layer-specific parameters. The SME typically performs such functions on behalf of general system management entities and implements standard management protocols. Furthermore, according to IEEE 802.11 standards, a WTRU contains configuration settings in the MIB that control its behavior. It is important for an AP to be able to understand the configuration of each WTRU in order to interpret the WTRU's behavior and to improve performance in the context of WLAN RRM. For example, a WTRU keeps track, in its MIB, of successfully received but not decodable data frames. This is important information for an AP to provide a minimum level of quality of service to the WTRU. RRM is one of the most important aspects in WLAN management. A WLAN can achieve significant performance enhancement by performing RRM, including in-band interference mitigation and frequency re-use. The MIB, as currently defined under IEEE 802.11 standards, does not contain enough information to support WLAN RRM. Therefore, there is a need for an improved MIB data structure to assist the inter-working of a WTRU and an AP in terms of WLAN RRM. The request/report messaging and retrieving of a WTRU's physical measurement data or MAC performance statistics of all sorts in a basic service set (BSS) are key parameters for interference mitigation and RRM. However, these physical measurements or MAC performance statistics are not passed from an LI PHY or L2 MAC protocol entity to the SME, which serves as an interface to an external WLAN RRM entity. The SME typically contains interface software to read/write into the MIBs. For example, upon receiving a command from a simple network management protocol (SNMP), a read of a particular MIB entry is reported back to the SNMP. In conventional systems, the MIB of the AP does not currently contain the physical measurement data or MAC performance statistics stored in the MIB of the WTRU. Furthermore, the NMEs do not know what is in the WTRU's MIB, because in almost all cases, only the AP has implemented a management protocol (e.g., an SNMP) to read/write to a MIB in the AP, but not to the MIB in the WTRU. SUMMARY The present invention is method and wireless communication system for transferring management information. The system includes at least one access point (AP) including a first management entity and a second management entity, and at least one wireless transmit/receive unit (WTRU) including a third management entity and a fourth management entity. The AP transmits a management information base (MIB) information request action frame including a category field and an action details field to the WTRU. In response to receiving the information request action frame, the WTRU determines whether or not to provide management information to the AP. When the WTRU provides management information to the AP, the WTRU compiles management information stored in a MIB located in the WTRU and transmits a MIB information report action frame to the AP. The MIB lists a plurality of tables containing information associated with radio resource management (RRM) and at least one table containing physical layer measurements. BRIEF DESCRIPTION OF THE DRAWINGS A more detailed understanding of the invention may be had from the following description of a preferred example, given by way of example and to be understood in conjunction with the accompanying drawing wherein' Figure 1A is a block diagram of a wireless communication system operating in accordance with the present invention! Figure IB is a detailed block diagram illustrating the configuration of an AP and WTRU used in the wireless communication system of Figure 1A! Figure 2 is a signal flow diagram showing communication between a WTRU and an AP for obtaining MIB information in accordance with the present invention; Figure 3 is a signal flow diagram showing communication between a WTRU and an AP for requesting and receiving a measurement report in accordance with the present invention; Figure 4 is a signal flow diagram illustrating an exemplary process tor transferring management information using service primitives between network management entities in accordance with the present invention; Figure 5 shows exemplary MIB information action frames including a frame body in accordance with the present invention! Figure 6 shows the details of the frame body of the action frames of Figure 5; and Figures 7A and 7B, taken together, is a flowchart of an exemplary process including method steps for transferring management information between network entities in accordance with the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereafter, a WTRU includes but is not limited to a user equipment, a mobile station, a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment. When referred to hereafter, an AP includes but is not limited to a base station, a Node-B, a site controller, or any other type of interfacing device in a wireless environment. The present invention will be described with reference to the drawing figures wherein like numerals represent like elements throughout. The present invention applies as add-on to the WLANIEEE 802.11 standards (802.11 baseline, 802.1 la, 802.lib, and 802.llg), and also applies to IEEE 802.lie, 802.11h and 802.16. The present invention may be further applicable to Time Division Duplex (TDD), Frequency Division Duplex (FDD), and Time Division Synchronous CDMA (TDSCDMA), as applied to a Universal Mobile Telecommunications System (UMTS), CDMA 2000 and CDMA in general, but is envisaged to be applicable to other wireless systems as well. The features of the present invention may be incorporated into an integrated circuit (1C) or be configured in a circuit comprising a multitude of interconnecting components. Figure 1A is a block diagram of a wireless communication system 100 including a plurality of WTRUs 105, a plurality of APs 110, a distribution system (DS) 115, an NME 120 and a network 125. The WTRUs 105 and APs 110 form respective base service sets (BSSs) 130. The BSSs 130 and the DS 115 form an extended service set (ESS). The APs 110 are connected to the NME 120 through the network 125. The wireless communication system 100 may be a WLAN. Figure IB is a detailed block diagram illustrating the configuration of the APs 110 and WTRUs 105 used in the wireless communication system 100. The AP 110 includes a first management entity 150, a second management entity 155 and a first MIB 160. The WTRU 105 includes a third management entity 165, a fourth management entity 170 and a second MIB 175. The MIBs 160 and 175 consist of one or more storage devices (e.g., a counter, a register or other memory device) used to store configuration parameters, performance metrics and fault indicators. The first management entity 150 may be an SME. The second management entity 155 may be an MLME. The third management entity 165 may be an MLME. The fourth management entity 170 may be an SME. The present invention expands the data content of the MIB 160 in the AP 110 such that it stores the contents of the MIB 175 in the WTRU 105. The NME 120 may request the AP 110 to obtain and provide to the NME at least a portion of information stored in the MIB 175 of the WTRU 105. Once the AP 110 stores the information, the NME 120 may access the MIB 160, which now contains at least a portion of the contents of the MIB 175. Figure 2 illustrates a process which supports communication between a WTRU 105 and an AP 110 in order to obtain MIB data in accordance with the present invention. Once an AP 110 decides to retrieve MIB data from a target WTRU 105, the AP 110 transmits a MIB information request frame 205 to the target WTRU 105. The WTRU 105 compiles MIB data (stored in the second MIB 175) and transmits a MIB information report frame 210 to the AP 110. Referring to Figures 1A and IB, the process to initiate the retrieval of WTRU MIB contents can also be initiated by the NME 120, which in turn triggers the first management entity 150 in the AP 110 to send a primitive to the second management entity 155 to send a MAC signaling frame to the WTRU 105 and so on. The MIB information report frame 210 is preferably generated as a new category of action frame. However, the MIB information report frame 210 may be generated as a new sub-type of management frame, or may comprise a new information element (IE) attached to either a management frame or an action frame that currently exists or will be developed in the future. Figure 3 illustrates a process which supports communication between a WTRU 105 and an AP 110 in order for the AP 110 to request a WTRU 105 to perform one or more measurements and report specific physical parameters of the WTRU 105 to the AP 110. Once an AP 110 decides to request physical measurement data from a WTRU 105, the AP 110 transmits a measurement request action frame 305 to a target WTRU 105 for measuring and reporting certain physical parameters of the target WTRU 105. The measurements may include transmit power, link margin, a clear channel assessment (CCA) report, received power indicator (RPI) histogram report, or any other physical related measurements. These may be absolute values, statistical averages or histogram values, or values that are calculated utilizing any type of "algorithm or optimization routine. After performing the requested measurement, the target WTRU 105 compiles measurement data and transmits a measurement report action frame 310 to the AP 110. The measurement data is stored in the MIB 160 of the AP 110 and the MIB 175 of the WTRU 105. The MIB 175 in the WTRU 105 stores two different categories of information. The first category includes a variety of physical measurements such as signal power, interference levels, noise histograms, or the like. The second category is a variety of MAC performance statistics such as CCA busy fractions, average back-off times, erroneous frame counters, or the like. When the received physical measurement and MAC performance statistics are stored in the MIB 160 of the AP 110, it is made available to an entity which is responsible for RRM. The MIB 160 maybe either a MAC MIB or a PHY MIB. A MAC MIB is preferred because RRM messaging is also performed in MAC layer, and it is much faster than PHY layer. These physical measurement data are made available to external entities by storing them in the MIB 160 of the AP 110. Thus, effective load control and BSS range adjustments become possible. Figure 4 is a signal flow diagram illustrating an exemplary process 400 for obtaining MIB information using service primitives between an AP 110 and a WTRU 105. Internal messaging is performed with service primitives newly introduced by the present invention. Using process 400, an AP 110 may retrieve data stored in the MIB 175 of a WTRU 105 and store the retrieved data in the MIB 160 of the AP 110. The AP 110 includes an SME 450 and an MLME 455. The WTRU 105 includes a MLME 465 and an SME 470. The SME 450 of the AP 110 determines whether or not to request MIB information from the WTRU 105 (step 402). In step 404, the SME 450 transmits a first message (MLME-MIBREQUEST.req) to the MLME 455 of the AP 110 requesting MIB information if the SME 450 determines in step 402 to request MIB information from the WTRU 105. In step 406, the MLME 455 transmits a second message (MLME-MIBREQUEST.cfm) to the SME 450 confirming receipt of the first message (MLME-MIBREQUEST.req). In step 408, the MLME 455 transmits a third message (MIB information request frame) to the target WTRU 105 requesting MIB information, and the MLME 465 of the target WTRU 105 receives the third message (MIB information request frame). In step 410, the MLME 465 transmits a fourth message (MLME-MIBREQUEST.ind) to the SME 470 in the target WTRU 105 requesting MIB information. Still referring to Figure 4, in step 412, the SME 470 determines whether or not to provide MIB information in response to the fourth message (MLME-MIBREQUEST.ind). Some of the decisions involved in step 412 may include whether or not the WTRU 105 has the MIB information elements that the AP requested. For some error conditions, the AP 110 may request MIB information that the WTRU 105does not have stored in the MIB 175. Also, it may be desired to implement security checking process whereby, for example, if the WTRU 105 has reason to believe that the MIB information request is not coming from a valid, (i.e., authorized), AP 110, the SME 470 in the WTRU 105 may decide not to send the requested MIB information. Still referring to Figure 4, in step 414, the SME 470 compiles MIB information stored in the MIB 175 of WTRU 105, if the SME 470 determines to provide MIB information, (i.e., accepts the MIB information request), in step 412. In step 416, the SME 470 transmits a fifth message (MLME-MIBREPORT.req) to the MLME 465. In step 418, the MLME 465 transmits a sixth message (MLME-MIBREPORT.cfm) to the SME 470 confirming receipt of the fifth message (MLME-MIBREPORT.req). In step 420, the MLME 465 transmits a seventh message (MIB information report frame) including the requested information to the AP 110, and the MLME 455 of the AP 110 receives the seventh message (MIB information report frame). In step 422, the MLME 455 transmits an eighth message (MLME-MIBREPORT.ind) including the requested MIB information to the SME 450. The requested MIB information may be stored in the MIB 160 of the AP 110. The MIB information request is completed in step 424. In accordance with the present invention, protection is provided for the contents of the MIB 160 of the WTRU 105 by prohibiting an entity outside of the WTRU 105 from directly reading the contents of the MIB 160. Signaling frames and related~mter-layer primitives are exchanged between the layers in either the AP 110 or WTRU 105. MAC frames which directly carry specific MIB entries consisting of physical measurements and MAC performance statistics are used to build a WTRTJ-related MIB entry, thus forming a "peer table". In one alternate embodiment, measurements performed by the WTRU 105, such as signal strength measurements, may be transmitted from the WTRU 105 to the AP 110 via MAC frames and stored in the MIP 160 of the AP 110, without the WTRU 105 storing the measurements in its own MIP 175. Data entries of the MIB are defined by IEEE 802.11 standards. However, the MIB currently defined under the IEEE 802.11 standards does not contain enough information to support WLAN RRM. Therefore, the present invention introduces an improved MIB data structure to assist the inter-working of a WTRU 105 and an AP 110 in terms of WLAN RRM. For example, Table 1, as shown below, includes a list of six (6) MIB tables containing RRM relevant information and one (l) MIB table containing PHY measurements in accordance with the present invention. In accordance with IEEE 802.11 standards, these tables are preferably contained within IEEE 802.11 RRM MIB and IEEE 802.11 PHY MIB, respectively. However, each of the MIB tables could be included as extensions of other existing IEEE 802.11 MIB tables, including but not limited to, 802.11 PHY, 802.11 MAC, and 802.11 SMT (station management). (Table Removed) Peer physical layer measurements that are reported to or passively observable pertaining to a particular WTRU are written into the MIB dotllpeerPhyMeasTable. This includes a BSS of the AP and its neighbors, as observed either by the AP itself or by the WTRUs. Examples of the BSS AP PhyMeas include a received signal strength indicator (RSSI) and a bit error rate (BER). With respect to BSS global status, high level network information pertaining to association, roaming, authentication, and security status and history of all WTRUs are stored in MIB table dotllBSSGlobalStatusTable. Other examples include the number of WTRUs in the network, and the number of WTRUs that are sleeping. MAC and PHY BSS statistics and AP measurements, such as load, congestion, interference, interference sources, and neighbors, are stored in MIB table dot 11 BSSGlobalStatisticsTable. Overall BSS control configuration pertaining to RRM, such as how long an AP is to keep data in a MIB table and when to perform a particular task, is stored in MIB table dotllBSSRrmConfigurationTable. A list of action items and network monitoring tools for external NMEs is contained in MIB table dotllBSSRrmActionsTable. The information stored in this MIB table acts as an interface for NMEs to force and prioritize WLAN actions. Availability of peer features and capabilities is stored in a MIB dotllpeerCapabilityTable. For example, information on whether a WTRU has two antennas is stored in the MIB table. In another example, information on whether a WTRU has encryption capability is stored in the MIB table. Information regarding the actual configuration of the aforementioned peer features and capabilities is stored in MIB table dotllpeerConfigurationTable. Using the example of a WTRU with encryption capability, the associated configuration is the ON/OFF status of the encryption feature. With the above mentioned MIB tables containing RRM information relevant to the BSS, RRM information is distributed among a plurality of APs, WTRUs and NMEs. Figure 5 shows an exemplary configuration of a MIB information frame 500 which includes a frame body field 505 in accordance with the present invention. The MIB information, frame 500 is an action frame, (i.e., a MAC frame), but it should be understood that the format of MIB information frame 500 may be formatted as a management frame or information elements attached to either a management frame or an action frame. The MIB information frame 500 includes type and the subtype fields which indicate the specific characteristics of MAC frame and how it should be processed. Data uses a different MAC frame type than management frames. A subtype field is used to differentiate different sorts of management frames. The MAC frame is used to retrieve MIB information from the WTRU 105. Figure 6 shows that the frame body 505 of the MIB information frame 500 may include a category field 605 and an action details field 610. The category field 605 may include a MIB information category and indicates the specific characteristics of the frame 500 and how it should be processed. The action details field 610 includes action details which vary depending on the category field. For example, the action details field 610 may indicate specific frequencies to measure. A MIB request would typically specify which MIB entries should be reported back from the WTRU 105, e.g., only a specific table, only a particular value in a specific table, or the like. Figures 7A and 7B, taken together, is a flowchart of an exemplary process 700 including method steps for transferring management information between network entities in accordance with the present invention. Process 700 is implemented in a wireless communication system 100 including at least one AP 110 and at least WTRU 105 (see Fig. 1A). As shown in Figure IB, the AP 110 includes a first management entity 150 and a second management entity 155. Furthermore, as shown in Figure IB, the WTRU 105 includes a third management entity 165 and a fourth management entity 170. Referring to Figures 7A and IB, the first management entity 150 in an AP 110 determines whether or not to request management information from the WTRU 105 (step 705). In step 710, the first management entity 150 transmits a first message to the second management entity 155 in the AP 110 requesting management information if the first management entity 150 determines to request management information from the WTRU 105 in step 705. In step 715, the second management entity 155 transmits a second message to the first management entity 150 confirming receipt of the first message. In step 720, the second management entity 155 transmits a third message including a request for management information to the WTRU 105. In step 725, the third management entity 165 in the WTRU 105 receives the third message. In step 730, the third management entity 165 transmits a fourth message including the request for management information to the fourth management entity 170 in the WTRU 105. In step 735, the fourth management entity 170 determines whether or not to provide management information stored in response to the fourth message. In step 740, the fourth management entity 170 compiles management information stored in the WTRU, (i.e., in the MIB 175), if the fourth management entity 170 determines to provide management information in step 735. Referring now to Figures 7B and IB, in step 745, the fourth management entity 170 transmits a fifth message including the requested management information to the third management entity!65. In step 750, the third management entity 165 transmits a sixth message to the fourth management entity 170 confirming receipt of the fifth message. In step 755, the third management entity 165 transmits a seventh message including the requested management information to the AP 110. In step 760, the second management entity 155 in the AP 110 receives the seventh message. In step 765, the second management entity 155 transmits an eighth message including the requested management information to the first management entity 150. The requested information may then be stored in the MIB 160 of the AP 110. While this invention has been particularly shown and described with reference to preferred embodiments, 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 scope of the invention described hereinabove. We claim: 1. A wireless transmit/receive unit (WTRU) (105) comprising: a station management entity (SME) (150, 170); a medium access control (MAC) layer management entity (MLME) (155, 165) in communication with the SME; and a radio resource management (RRM) management information base (MIB) (160, 175) in communication with the SME, the RRM MIB having a first table having access point (AP) (110) configuration information, a second table having security information, and a third table having signal strength information, wherein: the MLME (155,165) is configured to: receive a first message that comprises a request for management information; and communicate a second message that comprises the request for management information to the SME; and the SME (150,170) is configured to: receive the second message; compile management information stored in the MIB (160,175); and communicate a third message that comprises the compiled management information to the MLME (155,165). 2. The WTRU (105) as claimed in claim 1, wherein the MLME (155,165) is configured to transmit a fourth message that comprises the compiled management information to an access point (AP) (110) in response to the third message. 3. The WTRU (105) as claimed in claim 2, wherein the first message comprises a MIB information request action frame (205) that comprises a category field and an action details field. 4. The WTRU (105) as claimed in claim 2, wherein the fourth message comprises a MIB information report action frame (210) that comprises a category field and an action details field. 5. The WTRU (105) as claimed in claim 1, wherein the WTRU is configured to operate within a wireless local area network (WLAN). 6. The WTRU (105) as claimed in claim 1, wherein the second table has authentication information. 7. The WTRU (105) as claimed in claim 1, wherein the RRM MIB (160,175) has a fourth table having channel load information. 8. A wireless transmit/receive unit (105) comprising: a station management entity (SME) (150, 170); a medium access control (MAC) layer management entity (MLME) (155, 165) in communication with the SME; and a radio resource management (RRM) management information base (MIB) (160,175) in communication with the SME (150,170), wherein: the SME is configured to send a first message that comprises a request for management information to the MLME (155,165); the MLME is configured, in response to the first message, to communicate a second message that comprises the request for management information to a second MLME in a second WTRU; the MLME is configured to receive, in response to the second message, a third message comprising management information, and is configured to communicate a fourth message to the SME, the fourth message comprising the management information; and the SME is configured to receive the fourth message and to store the management information in the RRM MIB (160,175). 9. The WTRU (105) as claimed in claim 8, wherein the second message comprises a MIB information request action frame (205) that comprises a category field and an action details field. 10. The WTRU (105) as claimed in claim 8, wherein the third message comprises a MIB information report action frame (210) that comprises a category field and an action details field. 11. The WTRU (105) as claimed in claim 8, wherein the RRM MIB (160,175) has a first table having AP (110) configuration information, a second table having security information, and a third table having signal strength information 12. The WTRU (105) as claimed in claim 11, wherein the second table has authentication information. 13. The WTRU (105) as claimed in claim 11, wherein the RRM MIB (160,175) has a fourth table having channel load information.

Documents:

778-delnp-2006-abstract.pdf

778-DELNP-2006-Claims-(16-04-2009).pdf

778-DELNP-2006-Claims-(28-01-2010).pdf

778-delnp-2006-claims.pdf

778-DELNP-2006-Correspondence Others-(29-04-2011).pdf

778-DELNP-2006-Correspondence-Others (28-01-2010).pdf

778-delnp-2006-correspondence-others 1.pdf

778-DELNP-2006-Correspondence-Others-(16-04-2009).pdf

778-DELNP-2006-Correspondence-Others-(17-04-2009).pdf

778-DELNP-2006-Correspondence-Others-(18-02-2010).pdf

778-delnp-2006-correspondence-others.pdf

778-delnp-2006-description (complete).pdf

778-delnp-2006-drawings.pdf

778-DELNP-2006-Form-1-(16-04-2009).pdf

778-delnp-2006-form-1.pdf

778-delnp-2006-form-13.pdf

778-delnp-2006-form-18.pdf

778-DELNP-2006-Form-2-(16-04-2009).pdf

778-delnp-2006-form-2.pdf

778-DELNP-2006-Form-26-(16-04-2009).pdf

778-delnp-2006-form-26.pdf

778-DELNP-2006-Form-27-(29-04-2011).pdf

778-DELNP-2006-Form-3-(17-04-2009).pdf

778-DELNP-2006-Form-3-(28-01-2010).pdf

778-delnp-2006-form-3.pdf

778-delnp-2006-form-5.pdf

778-delnp-2006-pct-101.pdf

778-delnp-2006-pct-105.pdf

778-delnp-2006-pct-210.pdf

778-delnp-2006-pct-220.pdf

778-delnp-2006-pct-237.pdf

778-delnp-2006-pct-301.pdf

778-delnp-2006-pct-306.pdf

778-delnp-2006-pct-326.pdf

778-delnp-2006-pct-373.pdf

778-DELNP-2006-Petition 137-(28-01-2010).pdf

778-DELNP-2006-Petition-137-04-2011).pdf

abstract.jpg