The present invention relates to data transmission in a communications network, and more particularly to a method and system for data transmission in a network wherein receivers of the network have different data reception rate capabilities.
Multi-rate capabilities are increasingly becoming a necessity for wireless data networks. For example, to be competitive and allow a flexible sales strategy, network service providers may need to be able to offer customers different data rates at different prices.
Additionally, as technology advances, manufacturers and service providers are able to offer customers new generations of improved receiving equipment at regular intervals. This leads to a situation wherein some network users may have the newest equipment with the highest data reception rate capabilities, while others who may be unwilling to undertake the cost of an upgrade may have older equipment with lower data reception rate capabilities.
More generally, for various reasons, wireless networks of the future will tend to become increasingly heterogeneous in terms of the processing capabilities of users' receiving equipment.
Known data transmission methods in wireless networks either do not allow for a disparity in data reception rate capabilities among users, or typically do not efficiently handle such a disparity if it does exist. Rather, such data transmission methods may waste bandwidth in that data transmission rates must accommodate the user with the slowest equipment.
In view of the foregoing, a method and system are needed for efficiently handling data transmission in a wireless network wherein network users have different data reception rate capabilities.
According to embodiments of the present invention, in a communications network comprising a plurality of receivers with different data reception rate capabilities, data frames targeted to respective receivers may be transmitted to the receivers in accordance with the respective data reception rate capabilities of the receivers.
In one embodiment, a queue of data frames targeted to respective receivers may be maintained, and a data frame may be selected from the queue to transmit, based on the data reception rate capability of the target receiver of the selected data frame. To select the data frame, a data reception rate capability of the target receiver of the queued frame may be identified. If the data reception rate capability of the target receiver is not exceeded by transmitting the queued data frame in a next consecutive channel resource slot, the queued data frame may be transmitted to the target receiver. Otherwise, the queue may be searched for a data frame which can be transmitted in the next consecutive channel resource slot without exceeding the data reception rate capability of its target receiver.
According to embodiments of the invention, a rate controller for efficiently controlling the transmission of data to network users with different data reception rate capabilities may be embodied in a base station of a wireless communications network.
Users 1 through m may, for example, download information from an information source such as the Internet 104. The information will typically be in the form of data “frames” (also called “packets”), each formatted with a header for routing the data frame in a point-to-point fashion, according to some data protocol such as TCP/IP (Transmission Control Protocol/Internet Protocol), through the network to a target user. The downloaded information may, for example, be transmitted via a wired or wireless link to base station 100.
Each user 1-m may have a different data reception rate capability. More specifically, each user may have receiving equipment (referred to herein as a “receiver”) with a different data reception rate capability than the receivers of the other users. A typical receiver 105 may be embodied as a modular unit which may be installed externally to a residence or office. A typical receiver may include a processor or processors and a receiving antenna. In known receivers, depending on such factors as processing speed, data reception rate capabilities may vary, for example, between 512 bits/sec and 2.5 Mbits/sec.
In the example of
It should be further understood that “data reception rate capability” as used herein refers not only to limitations of receiver technology such as processing speed, but also to limitations on a transmitted data rate which may be arbitrarily imposed, for example according to a pricing agreement with a user.
Transmitter 210 of base station 100 may comprise computational resources such as computer processors, memory, storage media such as disks, and software for processing data as described above. These computational resources and associated channel bandwidth are collectively referred to herein as “transmitter resources.” Because the channel bandwidth may be used to transmit data to a plurality of users, the transmitter resources may be committed to some multiplexing scheme. In such a multiplexing scheme, the available bandwidth of the channel may be partitioned into “channel resource slots.” These channel resource slots may be time slots, frequency slots or frequency-time slots. As is well understood in time division multiplexing (TDM), for example, available channel resources are partitioned into time slots, wherein individual time slices of bandwidth are allocated to different users. Other multiplexing schemes which may be used according to embodiments of the invention include frequency division multiplexing and frequency-time division multiplexing.
As noted earlier, a plurality of users 101 may download information from Internet 104 or some other data source, resulting in a plurality of data frames targeted for a plurality of receivers 105 being sent to transmitter 210 of base station 100. After being processed by source encoder 201 and channel encoder 202 as described above, the data frames targeted to respective receivers may be processed by rate controller 203 according to embodiments of the invention. It should be understood that typical digital communication systems are not multi-rate, and therefore lack rate controller 203 as shown. Rate controller 203 may comprise a frame buffer 206 wherein a queue 208 of the targeted data frames received from the channel encoder is maintained. Rate controller 203 may further comprise a frame selector 207.
As discussed above, transmitter 210 of base station 100 may comprise computer processors, memory, storage and software for implementing its functions. In particular, frame selector 207 may be implemented in computer-executable instructions, and frame buffer 206 containing queue 208 may be maintained in a memory of the transmitter. Frame buffer 206 could be formatted, for example, as an array, or as a linked list.
Frame selector 207 may be configured to select a data frame from queue 208 to transmit, based on the data reception rate capability of the target receiver of the selected data frame. To select the data frame, a data reception rate capability of the target receiver of the queued frame may be identified. If the data reception rate capability of the target receiver is not exceeded by transmitting the queued data frame in a next consecutive channel resource slot, the queued data frame may be transmitted to the target receiver. Otherwise, the queue may be searched for a data frame which can be transmitted in the next consecutive channel resource slot without exceeding the data reception rate capability of its target receiver.
In
Typically, the frames would arrive at base station 100 in “bursts,” as shown: i.e. in groupings of consecutive frames targeted to one receiver. In the example of
In this example, assume that base station 100 can transmit data at a maximum rate of 1 frame per second. Also, assume that each second corresponds to a time slot of the channel resource slots. Further, assume that receiver A has a data reception rate capability of 1 frame per 5 seconds, receiver B has a data reception rate capability of 2 frames per 5 seconds, and receiver C has a data reception rate capability of 3 frames per 5 seconds.
When it is the turn of frames B1-B5 to be transmitted to receiver B, two frames can be sent in consecutive time slots as shown. However, because the data reception rate capability of receiver B is only 2 frames per 5 seconds, three time slots are wasted between the transmitting of B.sub.2 and B.sub.3, and B.sub.4 and B.sub.5.
Because the data reception rate capability of receiver C is 3 frames per 5 seconds, three frames targeted to receiver C can be transmitted in three consecutive time slots. However, two time slots are wasted, as shown.
Finally, when the second burst targeted to receiver A is transmitted, four times slots per frame are again wasted.
However, because the data reception rate capability of receiver B is only 2 frames per 5 seconds, it is next determined that frame B.sub.3 cannot be transmitted in the time slot consecutive to frame B.sub.2's time slot. Thus, queue 208 in frame buffer 206 is searched for a frame that can be transmitted in the next consecutive time slot without exceeding the data reception rate capability of its target receiver.
Accordingly, frame C.sub.1 is then selected for transmission. Frame C.sub.1 is transmitted in the time slot consecutive to frame B.sub.2's time slot, with no need for intervening idle slots. Similarly, frame C.sub.2 can be sent in the time slot consecutive to frame C.sub.1's time slot.
Next, because four time slots have elapsed since frame A.sub.1 was transmitted, frame A.sub.2, the oldest frame in queue 208, can now be transmitted, in the time slot consecutive to C.sub.2's time slot. Frame A.sub.3 cannot be transmitted next, however, so frames B.sub.3, B.sub.4, C.sub.3 and C.sub.4 are transmitted in the four consecutive time slots following frame A.sub.2's time slot, by making the same determinations as described above in connection with frames B.sub.1, B.sub.2, C.sub.1 and C.sub.2.
Next, because four time slots have elapsed since frame A.sub.2 was transmitted, frame A.sub.3 can now be transmitted, in the time slot consecutive to C.sub.4's time slot. Frames B.sub.5 and C.sub.5 are then transmitted in the next two consecutive time slots.
Finally, frames A.sub.4, A.sub.5 and A.sub.6 are transmitted. In this particular example, a non-refreshed queue has been discussed, and therefore idle time slots occur between the time slots for frame C.sub.5 and A.sub.4, and the time slots for frames A.sub.5 and A.sub.6. In practice, new data frames would be continually fed to frame buffer 206 and added to queue 208, and such idle slots would not occur in significant numbers.
As shown in ellipse 400, the process starts with the oldest frame in queue 208. As shown in block 401, it is determined whether the frame can be transmitted to its target receiver in the next consecutive time slot of the channel resource slots without exceeding the data reception rate capability of the target receiver. In order to implement this step, according to one embodiment, the data reception rate capability of the target receiver could be included in the frame header. Alternatively, the data reception rate capability of each receiver in the network could be included in a look-up table accessible to frame selector 207. After determining the data reception rate capability of the target receiver, frame selector 207 could compare it with a running tally of how many frames had been transmitted to the target receiver within the past N consecutive time slots, where N was some suitably-chosen, user-dependent number.
If the data reception rate capability of the target receiver was not exceeded, the frame could be transmitted to the target receiver, as shown in block 402.
If the data reception rate capability of the target receiver was exceeded, however, the frame could not be transmitted to the target receiver. Thus, a check could be performed to determine whether all the frames in queue 208 had been tested for whether they could be transmitted in the next consecutive time slot, as shown in block 403. If not, the next frame in queue 208 could be read and tested, as shown in block 404.
On the other hand, if all queued frames had been tested and none could be transmitted in the next consecutive time slot without exceeding the data reception rate capability of its target receiver, transmission of data could be idled for that time slot, as shown in block 405.
As noted above, frame selector 207 may be implemented in computer-executable instructions, which when executed by a processor carry out the advantageous features of the invention. The computer-executable instructions could be tangibly embodied in computer-usable media such as diskettes, magnetic tapes, CD-ROMs, RAM, ROM, FPGAs (Field Programmable Gate Arrays) or ASICs (Application Specific Integrated Circuits).
What has been described is merely illustrative of the application of the principles of the present invention. Other arrangements and methods can be implemented by those skilled in the art without departing from the spirit and scope of the present invention.
This is a continuation of U.S. patent application No. 12/829,813,filed on Jul. 2, 2010, entitled “REAL-TIME RATE CONTROL MECHANISM FOR MULTI-RATE DATA TRANSMISSIONS IN WIRELESS NETWORKS”, which is a continuation of U.S. patent application No. 12/480,509, filed on June 8, 2009, entitled “REAL-TIME RATE CONTROL MECHANISM FOR MULTI-RATE DATA TRANSMISSIONS IN WIRELESS NETWORKS” (now U.S. Pat. No. 7,773,520), which is a continuation of U.S. patent application No. 11/713,691, filed on Mar. 5, 2007, entitled “REAL-TIME RATE CONTROL MECHANISM FOR MULTI-RATE DATA TRANSMISSIONS IN WIRELESS NETWORKS” (now U.S. Pat. No. 7,554,912), which is a continuation of U.S. patent application No. 10/116,160, filed on Apr. 5, 2002, entitled “REAL-TIME RATE CONTROL MECHANISM FOR MULTI-RATE DATA TRANSMISSIONS IN WIRELESS NETWORKS” (now U.S. Pat. No. 7,230,922). The entireties of the aforementioned applications are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
5483676 | Mahany et al. | Jan 1996 | A |
5912921 | Warran et al. | Jun 1999 | A |
6141353 | Li | Oct 2000 | A |
6229795 | Pankaj et al. | May 2001 | B1 |
6292476 | Zehavi et al. | Sep 2001 | B1 |
6393012 | Pankaj et al. | May 2002 | B1 |
6836480 | Basso et al. | Dec 2004 | B2 |
7016318 | Pankaj et al. | Mar 2006 | B2 |
7230922 | Rodriguez-Sanchez et al. | Jun 2007 | B1 |
7298719 | Andrews | Nov 2007 | B2 |
7406098 | Taneja et al. | Jul 2008 | B2 |
7554912 | Rodriguez-Sanchez et al. | Jun 2009 | B2 |
7773520 | Rodriguez-Sanchez et al. | Aug 2010 | B2 |
8441928 | Rodriguez-Sanchez et al. | May 2013 | B2 |
20010006508 | Pankaj et al. | Jul 2001 | A1 |
Number | Date | Country |
---|---|---|
0111828 | Feb 2001 | WO |
03088604 | Oct 2003 | WO |
Entry |
---|
Sanot, et al, Monitoring -based flow control for reliable multicast protocols and its evaluation, Performance, Computing, and Communications Conference, 1997, IEEE International Phoenix, Tempe, AZ, USA, Feb. 5-7, 1997, New York, NY, USA, IEEE, US, Feb. 197, pp. 403-409. |
International Search Report mailed Jul. 16, 2003 for PCT Application No. PCT/US03/08721, 2 pages. |
Office Action mailed Feb. 17, 2006 for Chinese Patent Application Serial No. 03812225.1, 16 pages. |
Office action mailed Sep. 14, 2006 for Chinese Patent Application Serial No. 03812225.1, 8 pages. |
Office Action mailed Jun. 30, 2008 for European Patent Application Serial No. 03714321.1, 7 pages. |
Chinese Office Action dated Sep. 18, 2009 for CN Application Serial No. 200710089610.3, 5 pages. |
Office action mailed Feb. 3, 2010 for Chinese Patent Application Serial No. 2007100896103.3, 4 pages. |
Office Action dated Jan. 28, 2010 for U.S. Appl. No. 12/480,509, 10 pages. |
Office Action dated Sep. 9, 2009 for U.S. Appl. No. 12/480,509, 16 pages. |
CN OA dated May 6, 2011 for Chinese Patent Application No. 200710089610.3, 3 pages (untranslated). |
Office Action dated Sep. 19, 2012 for U.S. Appl. No. 12/829,813, 16 pages. |
Number | Date | Country | |
---|---|---|---|
20130229917 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12829813 | Jul 2010 | US |
Child | 13859449 | US | |
Parent | 12480509 | Jun 2009 | US |
Child | 12829813 | US | |
Parent | 11713691 | Mar 2007 | US |
Child | 12480509 | US | |
Parent | 10116160 | Apr 2002 | US |
Child | 11713691 | US |