Wireless network throughput enhancement through channel aware scheduling
Summary by NHIP
Channel-aware wireless scheduler
The system classifies packets into transmission queues and executes a weighted round robin scheduling technique. It requeues failed packets at the queue head, penalizes credit registers, and modifies weights based on current channel conditions and throughput performance estimates.
Claim Score by NHIP
Abstract
A channel aware scheduler (CAS) is disclosed that takes advantage of changing wireless channel conditions in order to maximize aggregated system throughput. The CAS is aware of the different channel conditions for one or more stations and adjusts its scheduling of packet transmissions in light of the same. A related CAS algorithm may take advantage of that knowledge in order to increase aggregated system throughput while concurrently addressing other potential fairness constraints.

Term
Projected expiry 28 July 2028.
- Priority
- Filed
- Granted
- Today
- Projected expiry
17 claims: 3 independent, 14 dependent
- 1A system for increasing wireless network throughput, the system comprising:a classifier configured to assign a packet to one of a plurality of transmission queues;and a hierarchical scheduling module stored in a computer-readable storage medium and executable by a processing device, the hierarchical scheduling module configured to: select a priority scheduled packet for transmission, wherein the selection is made in accordance with a weighted scheduling technique utilizing weighted round robin for determining a weight for each transmission queue, assign queue weights to stations within each transmission queue, determine from which of the plurality of transmission queue a failed packet originated, requeue the failed packet for retransmission at the queue from which the failed packet is determined to have originated, and penalize a credit register of the determined queue, wherein a transmission queue is activated at a different station when penalizing the credit register of the determined queue results in a predetermined level.
- 9A method for increasing wireless network throughput, the method comprising:assigning a packet to one of a plurality of transmission queues;and executing a hierarchical scheduling module stored in a computer-readable storage medium, wherein execution of the hierarchical scheduling module by a processing device: selects a priority scheduled packet for transmission, wherein the selection is made in accordance with a weighted scheduling technique utilizing weighted round robin for determining a weight for each transmission queue, assigns queue weights to stations within each transmission queue, determines from which of the plurality of transmission queues a failed packet originated, requeues the failed packet for retransmission at the queue from which the failed packet is determined to have originated, and penalizes a credit register of the determined queue, wherein a transmission queue is activated at a different station when penalizing the credit register of the determined queue results in a predetermined level.
- 17Broadest claimClaim Score 51, average(NHIP)A non-transitory computer-readable storage medium, having embodied thereon a program executable by a processor to perform a process for increasing wireless network throughput, the process comprising:assigning a packet to one of a plurality of transmission queues;selecting a priority scheduled packet for transmission, wherein the selection is made in accordance with a weighted scheduling technique utilizing weighted round robin for determining a weight for each transmission queue;assigning queue weights to stations within each transmission queue;determining from which of the plurality of transmission queue a failed packet originated;requeuing the failed packet for retransmission at the queue from which the failed packet is determined to have originated;and penalizing a credit register of the determined queue, wherein a transmission queue is activated at a different station when penalizing the credit register of the determined queue results in a predetermined level.
Independent claims3
57 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001The present application is a continuation and claims the priority benefit of U.S. patent application Ser. No. 12/181,274 filed Jul. 28, 2008, which will issue as U.S. Pat. No. 8,547,899 on Oct. 1, 2013, which claims the priority benefit of U.S. provisional application No. 60/952,557 filed Jul. 28, 2007, the disclosures of which are incorporated herein by reference.
BACKGROUND OF THE INVENTION
00021. Field of the Invention
0003The present invention generally relates to communications networks. More particular, the present invention related to systems and method for increased data throughput in communications networks.
00042. Description of the Related Art
0005A wireless channel is generally understood as a pathway between two communication endpoints. Through a wireless channel, the communication of any number of forms of data may take place. The efficient and effective communication of data is, however, subject to any number of characteristics of a particular wireless channel.
0006For example, a wireless channel with low throughput would not be recommended for the communication of data related to a high-definition television program. Similarly, the use of a wireless channel with a large amount of available bandwidth may be better utilized in the context of time-sensitive data transfers (e.g., voice communications) rather than the exchange of low priority and low-bandwidth background data queries.
0007Characteristics of a wireless channel may vary over time. For example, a wireless channel that at one moment has available bandwidth may subsequently be subjected to bottlenecks and dropped data packets thus requiring retransmission of the same. These variances in network characteristics may be a result of, for example, terminal mobility, multipath fading, or interference.
0008With respect to terminal mobility, a terminal may (while in motion) access wireless services from different locations. The mobility of the terminal requires the network to expend resources related to identifying and locating that terminal. The accessing of the network at different locales over time in conjunction with the need of the network to identify and locate the terminal may affect the quality of a wireless signal in that network.
0009Multipath fading involves the phenomenon of multipath propagation whereby a radio signal arrives at a receiving station (e.g., an antenna), at different times, via two or more paths. Multipath propagation may be induced by the refracting and reflecting of a wireless signal by various objects in the wireless environment (e.g., walls and metal objects). As a result of multipath propagation, the wireless signal is distorted thereby resulting in a deteriorated communications experience, which may include jitter or ghosting in the case of audio or video content.
0010Interference, broadly stated, may be mobile or static. In the case of mobile interference, the reception of a signal by a first mobile device (e.g., a wireless terminal) may be impeded or degraded by the transmission of a signal by another mobile device. Static interference is representative of the superposition of white noise (i.e., static) and other disturbing influences on a wireless signal. These influences are inclusive of thermal noise, electronic noise from receiver input circuits, and radiated electromagnetic noise that might be picked up by a receiving station's antenna.
0011<figref idref="DRAWINGS">FIG. 1A</figref> illustrates how characteristics of a wireless channel may vary over time in light of the aforementioned terminal mobility, multipath fading, and interference. <figref idref="DRAWINGS">FIG. 1A</figref> illustrates a wireless channel <b>100</b> where signal quality <b>110</b> between an access point (AP) and station are illustrated as a function of time <b>120</b>. As can be seen from <figref idref="DRAWINGS">FIG. 1A</figref>, signal quality <b>110</b> is less at T+1 than at T+2. The signal quality <b>110</b> for T+1 and T+2 is less than the signal quality <b>110</b> illustrated at T+3, which is nearly equivalent to that of the signal quality <b>110</b> exhibited at T+4. Signal quality <b>110</b> improves at T+5 while experiencing a significant decrease at T+6.
0012Further complicating the understanding of wireless channel characteristics (and the optimal use of those channels) is that channel conditions often lack correlation amongst one another in a network of stations. The lack of correlation may be a result of different distances from an AP to a particular station, distances from a station (or the AP) to a particular source of interference, the movement of a mobile terminal or station, as well as varying multipath fading effects. <figref idref="DRAWINGS">FIG. 1B</figref> is exemplary in this regard with respect to illustrating the signal quality <b>110</b> between the aforementioned AP and Station A (<b>130</b>) and the AP and Station B (<b>140</b>). As shown in <figref idref="DRAWINGS">FIG. 1B</figref>, there is no immediately recognizable correlation in signal quality vis-a-vis the AP and the differing stations (<b>130</b>/<b>140</b>).
0013One attempt at managing variances in wireless channel characteristics, especially as they pertain to different stations, has been through the use of a scheduler. Schedulers may be embodied in hardware and/or software components—the latter being executable from memory or a storage device by a corresponding processing device—with respect to providing scheduling policies, rules, procedure, or other criteria in making scheduling decisions. A scheduler may, in light of the aforementioned policies or criteria and a given set of packets, select particular packets for serial transmission over a particular wireless channel.
0014Different scheduling policies may be used in an attempt to ensure a communications network's ability to provide different quality of service (QOS) guarantees. Policies may include strict priority (SP) where a particular station queue is always allocated bandwidth and/or transmitted before other queues. An alternative policy includes round robin (RR) scheduling, which assigns bandwidth and transmits packets in equal portion, in order, and without priority to a particular station queue.
0015Weighted round robin (WRR), on the other hand, is a best-effort scheduling discipline (i.e., the network does not provide any guarantees that data is delivered or that a user is given a guaranteed QOS level or priority). Through WRR scheduling, station queues can be assigned a weight—an integer value that might indicate capacity or priority. Station queues with higher weights have their packets transmitted prior to those with lesser weights. All queues are eventually given regular transmission access to a channel albeit it those queues with higher weight will get more transmission access attempts than those with lesser weights.
0016Yet another scheduling policy is fair queuing (FQ), which allows several packet flows to fairly share link capacity. Fair queuing differs from first-in-first-out (FIFO) (i.e., what comes in first is handled first and what comes in next waits until the first is finished) in that an ill-behaved flow that consists of, for example, large data packets or a large number of packets will punish itself and not other packet flows. In FQ scheduling, in order to decide which packet should be forwarded first, the FQ algorithm estimates a virtual finishing time of all candidate packets (i.e., the packets at the head of all non-empty queues) based on, for example, the arrival time of the packet, the packet size, and the number of queues. The FQ scheduling algorithm or policy then compares the virtual finishing time and selects the minimum one. The packet with the minimum virtual finishing time is transmitted.
0017A still further scheduling policy is weighted fair queuing (WFQ), which allows different scheduling priorities to be statistically multiplexed. WFQ is a generalization of the aforementioned FQ algorithm where each data flow has a separate FIFO queue. Whereas the aforementioned ill-behaved queue will only punish itself, WFQ allows different sessions to have different service shares. If N data flows currently are active, with weights ω<sub>1</sub>, ω<sub>2 </sub>. . . ω<sub>N</sub>, data flow number i will achieve an average data rate of
0018<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mfrac><mrow><mi>R</mi><mo></mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo></mo><msub><mi>ω</mi><mi>i</mi></msub></mrow><mrow><mo>(</mo><mrow><mrow><msub><mi>ω</mi><mn>1</mn></msub><mo>|</mo><msub><mi>ω</mi><mn>2</mn></msub><mo>|</mo><mi>…</mi></mrow><mo>❘</mo><msub><mi>ω</mi><mi>N</mi></msub></mrow><mo>)</mo></mrow></mfrac></math></maths><img file="US9271327B2_D0001.tif" /><br /> An end-to-end delay bound can be guaranteed in WFQ scheduling. By dynamically regulating WFQ weights, this policy can be used to control QOS and achieve a guaranteed data rate.
0019Typical wireless devices (e.g., an 802.11x compliant device) implement a simple class and/or priority scheduling mechanism with a FIFO queue per each traffic class. An example of such a mechanism <b>200</b> is illustrated in <figref idref="DRAWINGS">FIG. 2</figref>. The scheduling mechanism <b>200</b> of <figref idref="DRAWINGS">FIG. 2</figref> illustrates four classes of traffic priority: voice (<b>230</b>), video (<b>240</b>), best-effort (<b>250</b>), and background (<b>260</b>). While the voice, video, best-effort, and background represent the typical four traffic priorities, the actual number of classes may vary in order to accommodate, for example, additional traffic classes and management traffic.
0020In the scheduling mechanism <b>200</b> of <figref idref="DRAWINGS">FIG. 2</figref>, packets are introduced to the wireless device via a network/input interface <b>210</b>. It should be noted that certain hardware components (e.g. a processor or memory) are not illustrated in that one skilled in the art will appreciate and understand the requisite components to implement the various applications disclosed herein. Packets may be received from another wireless device, a network backbone, a router, or a primary source of content that has been converted into data packets for transmission.
0021Packets are then routed to the classifier <b>220</b>. The classifier <b>220</b> may identify packets based on application layer data regardless of port. The classifier <b>220</b> may alternatively identify packets based on Internet Protocol (IP) address, port numbers, and so on. Packet classification based on multiple fields may be implemented using basic search algorithms, geometric algorithms, heuristic algorithms, or hardware-specific search algorithms. A variety of methodologies for packet classification are generally known in the art.
0022Once classified by classifier <b>220</b>, packets are then routed to an appropriate queue: voice, video, best-effort, background (<b>230</b>-<b>260</b>). The priority scheduler <b>270</b> then schedules the classified and queued packets. In the priority based queuing and scheduling mechanism <b>200</b> of <figref idref="DRAWINGS">FIG. 2</figref>, all packet traffic of a specific class (e.g., voice (<b>230</b>) is subjected to FIFO queuing. Scheduling is done strictly by priority (SP). As such, priority N (e.g., voice (<b>230</b>)) must be empty before priority N+1 (e.g., video (<b>240</b>)) is allowed to transmit. Packets are then transmitted or further routed via the appropriate network/output interface <b>280</b>.
0023Problems exist with respect to prior art scheduling methodologies based on priority queuing with per class FIFO. Channel aware scheduling (as discussed in further detail below) may not be implemented in this context. For example, traffic to different stations is interleaved within each FIFO queue. Further, only one packet is available at any given time—the packet at the head of the highest priority queue.
0024Typical prior art scheduler implementations also blindly retransmit the head end packet from the highest priority active queue until that packet is either successfully acknowledged by the recipient or some maximum number of retransmissions occurs. This blind retransmission causes head-of-line blocking. As a result, poor system performance results and, in many circumstances, clients may become completely impaired.
SUMMARY OF THE PRESENTLY CLAIMED INVENTION
0025An embodiment of the presently claimed invention includes a system for increasing wireless network throughput. The system includes a classifier configured to assign a packet to one of a plurality of transmission queues. The system further includes a first scheduling module and a second scheduling module. The first scheduling module is stored in a computer-readable medium and executable by a processing device to select an assigned packet for transmission from one of the plurality of transmission queues in accordance with a strict priority schedule. The second scheduling module is likewise stored in a computer-readable medium and executable to select a priority scheduled packet for transmission, wherein the selection is made in accordance with a weighted scheduling technique.
0026In a second embodiment of the presently claimed invention, a method for increasing wireless throughput is disclosed. The method includes the steps of assigning a packet to one of a plurality of transmission queues; selecting an assigned packet for transmission from one of the plurality of transmission queues in accordance with a priority schedule; selecting a priority scheduled packet for transmission in accordance with a weighted scheduling technique; and transmitting the packet.
0027A third embodiment is for a computer-readable storage medium having embodied thereon a program. The program is executable by a processing device to perform a method for increasing wireless throughput, the method includes the steps of assigning a packet to one of a plurality of transmission queues; selecting an assigned packet for transmission from one of the plurality of transmission queues in accordance with a priority schedule; selecting a priority scheduled packet for transmission in accordance with a weighted scheduling technique; and transmitting the packet.
BRIEF DESCRIPTION OF THE DRAWINGS
0028<figref idref="DRAWINGS">FIG. 1A</figref> illustrates a wireless channel where signal quality between an access point and station are sown as a function of time.
0029<figref idref="DRAWINGS">FIG. 1B</figref> illustrates signal quality between an access point and two stations.
0030<figref idref="DRAWINGS">FIG. 2</figref> illustrates a class/priority scheduling mechanism with a FIFO queue for each traffic class.
0031<figref idref="DRAWINGS">FIG. 3</figref> illustrates the biasing of a scheduler in a channel aware scheduler network environment involving an AP and two stations.
0032<figref idref="DRAWINGS">FIG. 4</figref> illustrates an embodiment of a channel aware scheduling mechanism utilizing hierarchical schedulers.
0033<figref idref="DRAWINGS">FIG. 5</figref> illustrates a method for channel aware scheduling transmission including a channel aware scheduler mechanism utilizing a deferred retransmission module.
0034<figref idref="DRAWINGS">FIG. 6</figref> illustrates queue weighting as may occur in the context of the channel aware scheduler mechanism of <figref idref="DRAWINGS">FIG. 4</figref> and the corresponding method of <figref idref="DRAWINGS">FIG. 5</figref>.
DETAILED DESCRIPTION
0035The presently disclosed invention utilizes channel aware scheduling. Through channel aware scheduling, an optimized scheduler—a channel aware scheduler (CAS)—takes advantage of changing wireless channel conditions in order to maximize aggregated system throughput. A CAS is aware of the different channel conditions for one or more stations and adjusts its scheduling of packet transmissions in light of the same. The CAS algorithm may take advantage of that knowledge in order to increase aggregated system throughput while concurrently addressing other potential fairness constraints.
0036<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example of how a CAS may be beneficial in a network environment <b>300</b> involving an AP and two stations (A and B). Based on the particular signal quality for each station (A or B) over time (T=0, T+1, T+N), the scheduler is biased toward one station or the other (i.e., the scheduler is aware of the quality of both channels). For example, at time T+1, +2 and, +3, the scheduler is biased toward station B while at time T+4 and T+5, the scheduler is biased to station A.
0037The CAS mechanism of the present invention allows for finer queuing and scheduling granularity with respect to individual stations and packet flows. An embodiment of the present invention utilizes hierarchical scheduling. In a first level of the hierarchy, an SP scheduling algorithm may be employed as is common to enterprise and service-provider class networking equipment. In a second level, the CAS mechanism may utilize WRR or WFQ scheduling algorithms as described above.
0038<figref idref="DRAWINGS">FIG. 4</figref> illustrates an embodiment of a CAS mechanism <b>400</b> utilizing the aforementioned hierarchical schedulers. Packets are received at classifier <b>410</b> following initial receipt by a network/input interface. Classifier <b>410</b> may operate in a manner similar to classifier <b>220</b> as illustrated in <figref idref="DRAWINGS">FIG. 2</figref>.
0039Following classification of an incoming packet at a wireless device implementing the CAS mechanism <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref>, the packet is routed to a first part of the scheduling hierarchy (i.e., a second level scheduler). In <figref idref="DRAWINGS">FIG. 4</figref>, this first portion of the scheduling hierarchy is represented by a queue with an associated priority. The CAS mechanism <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref> illustrates three priority queues, which may be representative of voice, video, and background (<b>420</b>-<b>440</b>, respectively). Differing numbers of priority queues may be implemented subject to the particular type of packet flows being received at the CAS mechanism <b>400</b>. For example, if the wireless device implementing CAS mechanism <b>400</b> is dedicated to the delivery of Internet Packet Television (IPTV) content, the voice queue (<b>420</b>) may be omitted.
0040Corresponding to each priority queue (<b>420</b>-<b>440</b>) in <figref idref="DRAWINGS">FIG. 4</figref> is one or more station queues (<b>420</b>A-<b>420</b>C; <b>430</b>A-<b>430</b>C; and <b>440</b>A-<b>440</b>C). Each of the station queues <b>420</b>A-<b>420</b>C; <b>430</b>A-<b>430</b>C; and <b>440</b>A-<b>440</b>C operates in conjunction with a WRR mechanism (<b>450</b>-<b>470</b>). Utilizing an associated WRR mechanism, each station queue <b>420</b>A-<b>420</b>C; <b>430</b>A-<b>430</b>C; and <b>440</b>A-<b>440</b>C is assigned a weight indicative of capacity or priority. Station queues <b>420</b>A-<b>420</b>C; <b>430</b>A-<b>430</b>C; and <b>440</b>A-<b>440</b>C with higher weights will have their packets transmitted prior to those with lesser weights. Weighting of a station queue is discussed in greater detail with respect to <figref idref="DRAWINGS">FIG. 6</figref> below.
0041Following assignment to a priority and weighted station queue in the first portion of the hierarchy, the priority scheduler <b>480</b> of the second portion of the hierarchy (i.e., the first level scheduler) assumes responsibility for scheduling the transmission of the classified, prioritized, weighted, and queued packets. The priority scheduler <b>480</b> of <figref idref="DRAWINGS">FIG. 4</figref> may operate in a fashion similar to that of the priority scheduler <b>270</b> in <figref idref="DRAWINGS">FIG. 2</figref>. Packets are then transmitted or further routed via an appropriate network/output interface.
0042In some embodiments, the CAS mechanism <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref> may utilize additional scheduling techniques such as deferred retransmission and weighted feedback. Both of these techniques may be implemented in the context of the second level schedulers of <figref idref="DRAWINGS">FIG. 4</figref>.
0043In the case of deferred retransmission, an indication of a failed transmission may be used to temporarily defer transmission or retransmission to the failed station and instead service other active stations in a priority queue. A deferred retransmission module may make direct use of a standard retransmission request mechanism such as an 802.11 acknowledgment (ACK) that would indicates a retransmission is required when no ACK is received.
0044Alternatively, an Automated Repeat Request (ARQ), which uses acknowledgments and timeouts to achieve reliable data transmission, may be used. A Hybrid Automated Repeat Request (HARQ) may also be used. In standard ARQ, error-detection information (ED) bits are added to data to be transmitted, such as cyclic redundancy check (CRC). In HARQ, forward error correction (FEC) bits are also added to the existing ED bits, such as Reed-Solomon code or Turbo code. As a result HARQ performs better than ordinary ARQ in poor signal conditions but may adversely affect the environment in good signal conditions. HARQ may have particular applicability to the IEEE 802.16-2005 standard for mobile broadband wireless access, also known as ‘mobile WiMAX.’ HARQ mechanisms also tend to be implemented in hardware.
0045The absence of an ACK or the receipt of an ARQ or HARQ (i.e., a retransmission request) operates as an indication of packet corruption. Packet corruption, in turn, is an indication of potential channel fade or other adverse channel condition. Upon indication of a retransmission requirement, the second level scheduler mechanism may elect to defer retransmission and move on to the next queue station that has pending packets.
0046<figref idref="DRAWINGS">FIG. 5</figref> illustrates a method for CAS transmission in accordance with the CAS mechanism <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref> as well as a CAS mechanism utilizing a deferred retransmission module.
0047In step <b>510</b>, a packet is received. Receipt of the packet may occur via a network/input interface. Packets may be received from another wireless device, a network backbone, a router, or a primary source of content that has been converted into data packets for transmission.
0048In step <b>520</b>, received packets are classified. The packets may be classified based on an application layer data regardless of port. Packets may also be identified and subsequently classified based on IP address, port numbers, and so on. Packet classification based on multiple fields may be implemented using basic search algorithms, geometric algorithms, heuristic algorithms, or hardware-specific search algorithms.
0049In step <b>530</b>, packets are routed to an appropriate priority queue. Packets are then assigned to a station queue in step <b>540</b>. Weighting of the station queues takes place in step <b>550</b>. It should be noted that station queue weighting may be dynamic or static and may take place prior to or concurrent with the transmission of any particular packet or packet flow. Weighting of a station queue is discussed further with respect to <figref idref="DRAWINGS">FIG. 6</figref>. Packets are scheduled solely based on priority in <b>560</b> and transmitted in accordance with that priority in step <b>570</b>.
0050In an alternative embodiment of a CAS mechanism that utilizes a deferred retransmission module, a retransmission request is received at optional step <b>580</b>. In response to the retransmission request, a particular station queue is deferred in optional step <b>590</b>. Scheduling of the remaining priority and channel queues takes place in step <b>560</b> as would occur in an embodiment not utilizing a deferred retransmission module. Transmission of the scheduled packets takes place in step <b>570</b>.
0051<figref idref="DRAWINGS">FIG. 6</figref> illustrates queue weighting as may occur in the context of the CAS mechanism of <figref idref="DRAWINGS">FIG. 4</figref> and the corresponding method of <figref idref="DRAWINGS">FIG. 5</figref>. Using a WRR algorithm, a weight (<b>640</b>-<b>660</b>) is determined for each queue (<b>610</b>-<b>630</b>). The WRR scheduler <b>670</b> (e.g., WRR <b>450</b>) then round robins between active queues (those that have pending packets) and transmits up to N packets from a queue where N is the weight associated with that queue.
0052Weighting may be implemented via credit register <b>690</b> that is loaded with a particular weight when a new station queue <b>680</b> is selected. The credit register <b>680</b> is decremented with each transmission from that station queue <b>680</b>. When the credit register <b>690</b> reaches 0, the WRR scheduler <b>670</b> advances in a round robin fashion to the next queue with an associated load of credits.
0053An embodiment of the CAS mechanism utilizing a deferred retransmission module may modify the WRR scheduler <b>670</b> as follows. Upon receipt of a retransmission requirement, it is determined from which station queue the failed packet originated. The failed packet is then re-queued at the head of that queue. If that particular queue is still active (i.e., the queue still has credits), the queue is penalized through the additional decrement of the credit register or decrementing the credit register to zero thereby forcing an activation of a queue associated with a different station. These penalization activities may take place in the context of optional step <b>590</b> of <figref idref="DRAWINGS">FIG. 5</figref>.
0054A further embodiment of the CAS mechanism disclosed herein may implement weighted feedback, which may be applicable to a hierarchical implementation utilizing WFQ or WRR. In such an embodiment, per-station channel conditions are estimated. These estimates may utilize low-level metrics such as signal-to-noise ratio (SNR) or error-to-vector magnitude (EVM). Application level metrics such as estimated throughput may also be utilized. Queue weights are modified to reflect channel conditions such that the scheduler favors stations with the better channel. Generally, weights are proportional to each channel capacity in order to maximize throughput. Weights may be limited to some minimal value to prevent the starvation of poor stations.
0055A still further embodiment of weight feedback involves, for each associated station, the performance of throughput estimation. Estimation may occur using a throughput model and packet encoding rule (PER) statistics. Packet transmission time stamps may also be used. If the estimated throughput is below some minimum threshold, the estimated throughput is set to the minimum threshold in order to ensure that some minimal bandwidth allocation is made with respect to each station. The WRR or WFQ weight is scaled proportionally to the estimated throughput.
0056Computer-executable instructions and associated data structures represent examples of the programming means for executing steps of the methods and implementing particular system configurations disclosed herein. Such methodologies may be stored in a computer-readable storage medium. Such methodologies may be executed in the context of a corresponding processing device.
0057While the present invention has been described in the context of a series of exemplary embodiments, these descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. To the contrary, the present description is intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art.
Contents5
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10250722B2 | Cited by | United States of America | Applicant |
| US1653664A | Cites | United States of America | Applicant |
| US2007002750A1 | Cites | United States of America | Search report |
| US2007072612A1 | Cites | United States of America | Search report |
| US2007280168A1 | Cites | United States of America | Search report |
| US4176356A | Cites | United States of America | Applicant |
| US4193077A | Cites | United States of America | Applicant |
| US4253193A | Cites | United States of America | Applicant |
| US4305052A | Cites | United States of America | Applicant |
| US4513412A | Cites | United States of America | Applicant |
| US4814777A | Cites | United States of America | Applicant |
| US5097484A | Cites | United States of America | Applicant |
| US5117430A | Cites | United States of America | Applicant |
| US5173711A | Cites | United States of America | Applicant |
| US5203010A | Cites | United States of America | Applicant |
| US5220340A | Cites | United States of America | Applicant |
| US5220678A | Cites | United States of America | Applicant |
| US5361256A | Cites | United States of America | Applicant |
| US5373548A | Cites | United States of America | Applicant |
| US5408465A | Cites | United States of America | Applicant |
| US5507035A | Cites | United States of America | Applicant |
| US5559800A | Cites | United States of America | Applicant |
| US5570366A | Cites | United States of America | Applicant |
| US5608726A | Cites | United States of America | Applicant |
| US5636213A | Cites | United States of America | Applicant |
| US5754145A | Cites | United States of America | Applicant |
| US5767809A | Cites | United States of America | Applicant |
| US5802312A | Cites | United States of America | Applicant |
| US5867109A | Cites | United States of America | Applicant |
| US5930259A | Cites | United States of America | Applicant |
| US5940771A | Cites | United States of America | Applicant |
| US5960344A | Cites | United States of America | Applicant |
| US5964830A | Cites | United States of America | Applicant |
| US5970410A | Cites | United States of America | Applicant |
| US5974034A | Cites | United States of America | Applicant |
| US6018659A | Cites | United States of America | Applicant |
| US6034638A | Cites | United States of America | Applicant |
| US6044062A | Cites | United States of America | Applicant |
| US6088570A | Cites | United States of America | Applicant |
| US6094177A | Cites | United States of America | Applicant |
| US6132306A | Cites | United States of America | Applicant |
| US6181697B1 | Cites | United States of America | Applicant |
| US6249516B1 | Cites | United States of America | Applicant |
| US6266528B1 | Cites | United States of America | Applicant |
| US6266537B1 | Cites | United States of America | Applicant |
| US6292153B1 | Cites | United States of America | Applicant |
| US6307524B1 | Cites | United States of America | Applicant |
| US6317599B1 | Cites | United States of America | Applicant |
| US6326922B1 | Cites | United States of America | Applicant |
| US6337628B2 | Cites | United States of America | Applicant |
| US6337668B1 | Cites | United States of America | Applicant |
| US6339404B1 | Cites | United States of America | Applicant |
| US6345043B1 | Cites | United States of America | Applicant |
| US6356242B1 | Cites | United States of America | Applicant |
| US6356243B1 | Cites | United States of America | Applicant |
| US6356553B1 | Cites | United States of America | Applicant |
| US6356905B1 | Cites | United States of America | Applicant |
| US6377227B1 | Cites | United States of America | Applicant |
| US6392610B1 | Cites | United States of America | Applicant |
| US6393261B1 | Cites | United States of America | Applicant |
| US6404386B1 | Cites | United States of America | Applicant |
| US6404775B1 | Cites | United States of America | Applicant |
| US6407719B1 | Cites | United States of America | Applicant |
| US6414955B1 | Cites | United States of America | Applicant |
| US6418138B1 | Cites | United States of America | Applicant |
| US6442507B1 | Cites | United States of America | Applicant |
| US6445688B1 | Cites | United States of America | Applicant |
| US6493679B1 | Cites | United States of America | Applicant |
| US6498589B1 | Cites | United States of America | Applicant |
| US6499006B1 | Cites | United States of America | Applicant |
| US6505253B1 | Cites | United States of America | Applicant |
| US6507321B2 | Cites | United States of America | Applicant |
| US6570883B1 | Cites | United States of America | Search report |
| US6584080B1 | Cites | United States of America | Applicant |
| US6625454B1 | Cites | United States of America | Applicant |
| US6674459B2 | Cites | United States of America | Applicant |
| US6701522B1 | Cites | United States of America | Applicant |
| US6704301B2 | Cites | United States of America | Applicant |
| US6714551B1 | Cites | United States of America | Applicant |
| US6725281B1 | Cites | United States of America | Applicant |
| US6728514B2 | Cites | United States of America | Applicant |
| US6753814B2 | Cites | United States of America | Applicant |
| US6762723B2 | Cites | United States of America | Applicant |
| US6778517B1 | Cites | United States of America | Applicant |
| US6779004B1 | Cites | United States of America | Applicant |
| US6819287B2 | Cites | United States of America | Applicant |
| US6836481B1 | Cites | United States of America | Applicant |
| US6873627B1 | Cites | United States of America | Applicant |
| US6876280B2 | Cites | United States of America | Applicant |
| US6888504B2 | Cites | United States of America | Applicant |
| US6888893B2 | Cites | United States of America | Applicant |
| US6892230B1 | Cites | United States of America | Applicant |
| US6906678B2 | Cites | United States of America | Applicant |
| US6910068B2 | Cites | United States of America | Applicant |
| US6924768B2 | Cites | United States of America | Applicant |
| US6931429B2 | Cites | United States of America | Applicant |
| US6941143B2 | Cites | United States of America | Applicant |
| US6950019B2 | Cites | United States of America | Applicant |
| US6957042B2 | Cites | United States of America | Applicant |
| US6957277B2 | Cites | United States of America | Applicant |
6 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 95255707 | United States of America | P | |
| 18127408 | United States of America | A |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| US2009028095A1 | United States of America | A1 | |
| US8547899B2 | United States of America | B2 | |
| US2014016563A1 | United States of America | A1 | |
| US9271327B2This record | United States of America | B2 | |
| US2016249376A1 | United States of America | A1 | |
| US9674862B2 | United States of America | B2 |
94 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Mail PUBS Letter Withdrawing a Notice Requiring Inventors Oath or DeclarationMM327-W | MM327-W | |
| PUBS Letter Withdrawing a Notice Requiring Inventors Oath or DeclarationM327-W | M327-W | |
| Printer Rush- No mailingTCPB | TCPB | |
| Printer Rush- No mailingTCPB | TCPB | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Printer Rush- No mailingTCPB | TCPB | |
| Printer Rush- No mailingTCPB | TCPB | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Mail PUBS Letter Withdrawing a Notice Requiring Inventors Oath or DeclarationMM327-W | MM327-W | |
| PUBS Letter Withdrawing a Notice Requiring Inventors Oath or DeclarationM327-W | M327-W | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
26 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Notice of allowance mailedORIGINAL CODE: MN/=.ZAAB | ZAAB | |
| Notice of allowance and fees dueORIGINAL CODE: NOAZAAA | ZAAA | |
| AssignmentAS | AS |
Numbers
- Publication
- 9271327
- Application
- 14028323
Titles
- English
- Wireless network throughput enhancement through channel aware scheduling
Patent term adjustment
- A delay
- +29 daysthe office missed an examination deadline
- Applicant delay
- −140 days
- Net adjustment
- 0 days
Classification
- CPC, 6
- H04W80/04
- H04W72/569
- H04W72/535
- H04W72/1242
- H04W88/06
- H04W72/1257
- IPC, 3
- H04W80 04
- H04W72 12
- H04W88 06