Source: http://www.google.com/patents/USRE43109?dq=6322901
Timestamp: 2017-10-17 02:25:37
Document Index: 560123430

Matched Legal Cases: ['§7', '§7', '§11', '§7', '§11', 'art 11', 'art 11', 'art 11', 'art 11']

Patent USRE43109 - Method to negotiate consumed power versus medium occupancy time in MIMO ... - Google Patents
A method of selectively providing MIMO transmission/reception in a WLAN system includes using a TSPEC reservation and signaling mechanism to instantiate and tear down, dynamically, multi-channel operation in a WLAN; providing an inference algorithm to determine the minimum number of channels required...http://www.google.com/patents/USRE43109?utm_source=gb-gplus-sharePatent USRE43109 - Method to negotiate consumed power versus medium occupancy time in MIMO based WLAN systems using admission control
Publication number USRE43109 E1
Application number US 13/086,296
Also published as US7519035, US20050185613
Publication number 086296, 13086296, US RE43109 E1, US RE43109E1, US-E1-RE43109, USRE43109 E1, USRE43109E1
Inventors John M. Kowalski, Srinivas Kandala
Patent Citations (10), Non-Patent Citations (8), Referenced by (12), Classifications (23), Legal Events (2)
Method to negotiate consumed power versus medium occupancy time in MIMO based WLAN systems using admission control
US RE43109 E1
A method of selectively providing MIMO transmission/reception in a WLAN system includes using a TSPEC reservation and signaling mechanism to instantiate and tear down, dynamically, multi-channel operation in a WLAN; providing an inference algorithm to determine the minimum number of channels required to establish a TSPEC using a MIMO WLAN system; providing specific channel parameters as parameters to be negotiated in the TSPEC; providing frame exchange sequences to be used in Enhanced Distributed Coordinated Access contention based access and to be used in polled access; and providing a mechanism wherein an access point makes a decision as to whether to admit MIMO functionality on a given link, wherein a “link” is a set of communications between two specific WLAN stations.
providing a mechanism wherein an access point makes a decision as to whether to admit MIMO functionality on a given link, wherein a “link”is a set of communications between two specific WLAN stations; and
providing a mechanism wherein an access point makes a decision as to whether to admit MIMO functionality on a given link, wherein a “link” is a set of communications between two specific WLAN stations; and
3. The method of claim 2 wherein said Add MIMO Request Frame has Information Elements which include: Category, Dialog Token, and MIMO Channel Element, where “Category” is set to “Add.”
5. The method of claim 2 wherein said Delete MIMO Request Frame has Information Elements which include: Category, Dialog Token, and MIMO Channel Element, wherein “Category” is set to “Delete”.
providing a mechanism wherein an access point makes a decision as to whether to admit MIMO functionality on a given link, wherein a “link” is a set of communications between two specific WLAN stations.
11. The method of claim 10 wherein said Add MIMO Request Frame has Information Elements which include: Category, Dialog Token, and MIMO Channel Element, where “Category” is set to “Add;” and wherein said Delete MIMO Request Frame has Information Elements which include: Category, Dialog Token, and MIMO Channel Element, wherein “Category” is set to “Delete”.
determining whether to initiate or remove MIMO resources in a link between the station and an other station, wherein the link is a set of communications between two specific WLAN stations;
providing channel parameters to be exchanged in the link between the station and the other station; and
initiating a frame exchange sequence, separate from a TSPEC negotiation frame exchange sequence, wherein the frame exchange sequence sets SISO and MIMO resources for the link,
providing parameters to be exchanged in the link between the station and the other station, the parameters including a power save mode for the link; and
initiating a frame exchange sequence separate from a TSPEC negotiation frame exchange sequence,
communicating in a frame exchange sequence, separate from a TSPEC negotiation frame exchange sequence, wherein the frame exchange sequence sets SISO and MIMO resources for the link,
sending a response to the station, the response containing information regarding the number of channels specified for reception by the station over the link and whether or not the power save mode is to be used in the link.
39. The method of claim 38 wherein the request frame received by the other station has information elements which include a number of channels.
communicating in a frame exchange sequence separate from a TSPEC negotiation frame exchange sequence,
transmitting, from the other station to the station, a response over one channel or multiple channels as requested in the request frame.
48. The method of claim 47 wherein the other station adds MIMO resources or reverts to SISO resources, for the link, for a given transmission.
initiating a frame sequence, separate from a TSPEC negotiation frame exchange sequence, wherein the frame sequence sets SISO and MIMO resources for the link,
This Application is a reissue application of U.S. Pat. No. 7,519,035, which was derived from U.S. patent application Ser. No. 11/050,487, filed on Feb. 1, 2005, which is related to and claims priority from U.S. Provisional Patent Application Ser. No. 60/547,102, filed Feb. 23, 2004, entitled Method to negotiate consumed power versus medium occupancy time in MIMO based WLAN systems using admission control, which are herein incorporated by reference in their entirety for all purposes.
This invention describes use of a multiple input, multiple output enhancement for IEEE 802.11 protocols and specifically to a MIMO enhancement which is selectively applied, thereby reducing overall power consumption.
Wireless LAN systems are proposed that utilize Multiple Input Multiple Output (MIMO) transmission technology for high throughput extensions to the IEEE 802.11 standard by the IEEE 802.11n Task Group. MIMO techniques promise a significant throughput increase over legacy techniques, however, they consume more power for increased signal processing, and, for the same range, require transmitted power to be roughly N times that of a single channel, where N is the number of channels used to transmit a signal.
FIG. 1 depicts a TSPEC negotiation stream of IEEE 802.11e.
This invention embeds in the Transmission Specification (TSPEC) used in IEEE 802.11e and as will be used by IEEE 802.11n, either implicitly or explicitly, information as to how many channels it is desired to use for Multiple Input Multiple Output (MIMO) signal processing. Explicit notification is the preferred embodiment, as the number of channels in which to transmit and receive may then be explicitly negotiated by IEEE 802.11 entities negotiating the TSPEC, with the objective of saving power consistent with minimizing time on the air.
To summarize, the unique aspects of the invention include (1) the use of the TSPEC reservation and signaling mechanism to instantiate and tear down, dynamically, multi-channel operation in an IEEE 802.11e/n WLAN; (2) an inference algorithm to determine the minimum number of channels required to establish a TSPEC using a MIMO system; (3) the inclusion of specific channel parameters, e.g., the number of transmit and receive channels required, as parameters to be negotiated in an IEEE 802.11e-like TSPEC; (5) the use of the frame exchange sequences to be used in Enhanced Distributed Coordinated Access (EDCA contention based access), as well as polled access; (5) a method by which the Access Point (AP) makes a decision as to whether to admit MIMO functionality on a given link, wherein a “link” is a set of communications between two specific IEEE 802.11 radios; and (6) an alternative embodiment wherein a management frame exchange sequence separate from the TSPEC negotiation frame exchange sequence, but modeled after its logic is used to allow for non-QoS Data to be sent, as well as to clarify the protocol's functionality.
MIMO systems, as stated earlier herein, are multiple-input multiple output systems that in general, use “N” transmitting “channels” and “M” receiving “channels” to realize up to an N×M increase in throughput over that available in a single input, single output (SISO) system. The exact form of the MIMO systems may vary according to the specific parameters established by the method of the invention, however, the amount of signal processing required over a SISO system is significantly more than N×M MIPS, because additional signal processing is done for interference cancellation, optimal filtering, etc.
Thus, it is in the best interests of the WLAN architect to use MIMO “sparingly,” that is, only for those applications which need to use MIMO, or when congestion on the medium demands use of MIMO. As is well known by those of ordinary skill in the art, IEEE 802.11 systems are Carrier Sense Multiple Access with Collision Avoidance, thus all IEEE 802.11 terminals share the same medium time, and use channel sensing and collision back off as “medium etiquette.”
Element Length TS Info Nominal Maximum Minimum
ID (13) (55) MSDU MSDU Service
Size Size Interval
Maximum Inactivity Suspension Service Minimum Mean
Service Interval Interval Start Data Rate Data Rate
Peak Data Maximum Delay Minimum Surplus Medium
Rate Burst Size Bound PHY rate Bandwidth Time
In a like manner two four bit fields may be appended to the convention TSPEC:
Number of Tx Channels Number of Rx Channels
These two field indicate the number of channels that the requestor is specifying for transmission, i.e., the Number of Tx Channels field and reception, i.e., the Number of Rx Channels field, on the medium. These two four bit fields are referred to collectively herein as the “MIMO Channel” field. The TSPEC negotiation features present in IEEE 802.11e are used to negotiate the actual number of channels used, which, in general represents a tradeoff of power to be saved versus medium access time.
This TSPEC object is used as an element in the Add Traffic Stream (ADDTS) QoS management action frame, with an action set to “request,” as in §7.4.2.1 of IEEE 802.11e, which is used by a client device to negotiate the instantiation of a QoS data stream. The format of the ADDTS frame body, minus header, CRC information, etc., is presented in Table 3. The “Order” column identifies the order of the “Information Elements” as located in the Frame Body. The specific Information Elements are described in the draft of IEEE 802.11e.
Order Information Element
4 TSPEC
5-n TCLAS (optional )
n + 1 TCLAS Processing (optional)
The “Category” element here signals the type of QoS Management Action for this frame, which indicates an ADDTS request frame. As is known to one of ordinary skill in the art, embedding the MIMO information within a TSPEC, i.e., element 4 of the request frame, the identical frame body structures and frame exchange sequences as used in IEEE 802.11e may be used to negotiate channel resources for a MIMO system.
The AP responds with an ADDTS management frame with an action set to “response.” The format of that frame is the same as the ADDTS request, with “Category” set to “response.” The response frame is similar to the request frame, with the addition of the fields “Status Code,” “TS Delay” and “Schedule,” as shown in Table 4. The Status Code field, e.g., IEEE 802.11e, §7.3.1.9 in particular, contains the form of the response from the AP in response to the request: the request is either accepted, declined without additional information, declined with a suggestion for an acceptable TSPEC, or declined but information is given as to when a QoS stream might be able to be created, using the TS Delay field. Furthermore, the Schedule element determines witch parameters in time as to the exact details of the polling sequence. These elements and action codes are identical to action codes that may be created to instantiate different MIMO transmit/receive channel configurations with sufficient flexibility and precision. Moreover, by doing this with the same paradigm as used in IEEE 802.11e, albeit for a different purpose, the MAC designer implements both a QoS functionality and MIMO resource negotiation the same way, which yields a simpler design.
5 TS Delay
6 TSPEC
7-n TCLAS (optional)
n + 2 Schedule
The stream negotiation procedure for IEEE 802.11e is depicted in FIG. 68.2 of IEEE 802.11e, and is repeated herein as FIG. 1. The STA's Station Management Entity (SME), as the requester, is the entity that initiates an MLMEADDTS.request primitive, containing the information required to set up a traffic stream, which triggers an ADDTS Request message sent from the non-AP station's Media Access Control (MAC) to the AP's Hybrid Coordinator MAC (HC MAC) which in turn triggers an MLMEADDTS.indication primitive from the AP'S HC MAC to the AP's Station Management Entity (AP SME), which in turn triggers an MLMEADDTS.response primitive. That primitive contains the information regarding the decision regarding admission of the stream, schedule, if admitted, and possible alternate TSPECs, etc. The MLMEADDTS.response primitive in turn is sent as an ADDTS Response frame to the requesting station. That primitive contains the information regarding the decision regarding admission of the stream, schedule, if admitted, and possible alternate TSPECs, etc. The MLMEADDTS.response primitive in turn is sent as an ADDTS Response frame to the requesting station. For brevity, here, we will not review the Delete Traffic Stream (DELTS) frame exchange which is the frame exchange sequence that tears down a traffic stream, and is fully described in IEEE 802.11e, D6, §11.4.7.
An alternative embodiment is for the TSPEC Minimum PHY rate to convey this information implicitly, and use the minimum number of channels to cover the Minimum PHY rate, however, as the minimum PHY rate is related to an underlying Physical Layer, within a single channel, it provides less flexibility than does the previous embodiment, may be harder to achieve interoperability because the Minimum PHY rate parameter is now “overloaded,” and allows fewer “degrees of freedom” in the negotiation (the Minimum PHY rate in a channel could be increased for SISO operation or decreased for MIMO operation, and depends on the application which would have better performance or occupy less medium time.)
Yet another embodiment is to use a separate action management frame exchange sequence that mirrors the TSPEC negotiation in IEEE 802.11e. This provides more flexibility and allows the TSPEC negotiation mechanism to be decoupled from the resource negotiation mechanism. Moreover, it provides for a simple extension to AP-to-AP negotiation of MIMO parameters, useful for Wireless Distribution Systems.
Add MIMO Request Frame, which requests a number of channels for transmit and receive;
Add MIMO Response Frame, which is the response the AP makes in response to the request frame, which allows the AP to manage medium occupancy time on the channel; and
Delete MIMO Request Frame, which allows a STA to revert back to SISO, i.e., one channel for transmit/receive, operation.
These frames include appropriate identifying fields within the syntax of IEEE 802.11 to uniquely identify these frames; those formats are not the relevant to the claims of this patent, and only the details of the frame bodies are discussed here.
2 Dialog Token
3 MIMO Channel Element
The “Category” field is either Request, Response, or Delete, by uniquely mapping those actions into three of the reserved fields currently allocated in the QoS Action Field defined in §7.4.2 of IEEE 802.11e. The “Dialog Token” field is used for matching action responses with action requests when there are multiple concurrent action requests; this may be the case as their may be, for example, concurrent QoS actions pending as well as the actions described herein. The “MIMO Channel Element” field, in this case, is the MIMO Channel Field defined above, with the an appropriate element ID appended, following the syntax of IEEE 802.11.
4 MIMO Delay
5 MIMO Channel Element
6 MIMO Schedule (optional)
The “Action” and “Dialog Token” fields are as described above. The “Status Code” field uses existing, or new, status codes to indicate the following actions:
(1) “Request Accepted” (already used; this field, with the Dialog Token, allows overloading of this field, so no new field is needed);
(2) “Request Denied” (already used; this field, with the Dialog Token, allows overloading of this field, so no new field is needed);
The frame exchange sequences of the method of the invention are depicted in FIG. 2, to request MIMO resources, which essentially follow the logic described earlier for traffic stream admission. The STA's Station Management Entity, as the requester, is the entity that initiates a MLMEADDMIMO.request primitive, containing the information regarding the STA, and the requested receive and transmit resources, which triggers an ADDMIMO Request message sent from the non-AP station's MAC to the AP's HC MAC, which in turn triggers an MLMEADDMIMO.indication primitive from the AP'S MAC to the AP's Station Management Entity (AP SME), which in turn triggers an MLMEMIMO.response primitive. That primitive contains the information regarding the decision regarding admission of the transmission of receive/transmission for the number of channels, a schedule, if admitted, and possible alternate resource allocations, etc. The MLMEADDMIMO.response primitive in turn is sent as an ADDMIMOResponse frame to the requesting station. The Delete MIMO Request Frame is identical to the Add MIMO Request Frame, but with the Category set to “Delete,” as depicted in FIG. 3.
The AP generally bases its decisions to use MIMO resources on a number of criteria, including, but not limited to: the number of stations associated on the network, the overall time usage that any one particular station may be using compared to its throughput (higher throughput stations would be readily granted MIMO resources), whether or not power save modes of 80211 are used, etc. To remove MIMO resources, a frame exchange sequence patterned after the deletion of traffic streams, as described in IEEE 802.11e §11.4.7, may be used. This embodiment is preferred, over the other two embodiments, as it allows for the negotiation of MIMO resources independently of QoS functions, and in particular, may be used for contention based channel access. As in the deletion of traffic streams, no response is necessary, because no decision is really needed from the AP to remove resources.
Finally, it should be noted that this last embodiment may be extended to AP-to-AP communication, by replacing “non-AP” with “AP” in the above signal flow diagrams.
US7489652 Jan 11, 2005 Feb 10, 2009 Samsung Electronics Co., Ltd. Method of communications between MIMO stations
1 "Draft Amendment to Standard [for] Information Technology-Telecommunications and Information Exchange Between System-LAN/MAN Specific Requirements", Part 11: Wireless Medium Access Control (MAC) and Physical Layer (PHY) specifications: Medium Access Control (MAC) Quality of Service (QoS) Enhancements, IEEE P802.11e/D8.0, Feb. 2004 (181 pages).
2 "Draft Amendment to Standard [for] Information Technology—Telecommunications and Information Exchange Between System—LAN/MAN Specific Requirements", Part 11: Wireless Medium Access Control (MAC) and Physical Layer (PHY) specifications: Medium Access Control (MAC) Quality of Service (QoS) Enhancements, IEEE P802.11e/D8.0, Feb. 2004 (181 pages).
3 "Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific Requirements", Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std 802.11-1997, Jun. 26, 1997 (466 pages).
4 "Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific Requirements", Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std 802.11-1997, Jun. 26, 1997 (466 pages).
5 "System Description and Operating Principles for High Throughput Enhancements to 802.11", Qualcomm, IEEE 802.11-04/0870r3, Feb. 2004 (150 pages).
6 "The MIMO Cross-Talk Interference Problem: A Novel Solution", IEEE80.11-003/1002, Daniel N. Nissani, Mar. 17, 2003 (10 pages).
7 "WWiSE Proposal: High throughput extension to the 802.11 Standard", Broadcom, TI, STMicroelectronics, Airgo et al., IEEE 802.11-040886r6, Jan. 6, 2005 (136 pages).
8 Gesbert, David, "From Theory to Practice: An Overview of MIMO Space-Time Coded Wireless Systems", IEEE Journal on Selected Areas in Communications, vol. 21, No. 3, Apr. 2003 (22 pages).
International Classification H04W74/06, H04W74/08, H04L12/28, H04W74/02, H04W40/00, H04W28/26, H04W76/02, H04W4/00, H04W84/12, H04W76/06, H04W28/18, H04W52/02
Cooperative Classification H04B7/0689, H04B7/0413, H04W74/02, H04W52/0206, H04W40/00, H04W84/12, Y02B60/50
European Classification H04W40/00, H04W72/04N