The subject application relates to data transmission, e.g., asymmetrical data transmission over simplex and duplex channels.
Cellular telephones are tremendously popular. It is estimated that at the end of 2007 the total worldwide subscriber rate reached 3.3 billion. Close to 80% of the world's population enjoys mobile telephone coverage, a figure that will only increase. As cellular telephones gain popularity, their functionality has increased also. Standard service includes voice calling, caller ID, call waiting, and voice mail. Service providers also offer text messaging, push mail, navigation, and even a high-speed internet connection directly to the telephone through the use of protocols such as those included in High Speed Packet Access (HSPA).
HSPA is a collection of wireless protocols that improve upon the performance of existing Universal Mobile Telecommunications System (UMTS) protocols. High-Speed Downlink Packet Access (HSDPA), a standard within HSPA, increases data packet transfer performance by using improved modulation schemes. These improved schemes better utilize existing radio bandwidth provided by UMTS. HSDPA currently supports downlink speeds of 1.8, 3.6, 7.2, and 14.4 Mbit/s. Long Term Evolution (LTE) is a promising standard for the next generation (4G) of mobile broadband networking.
Multiple-input and multiple-output (MIMO) requires the use of multiple antennas at both the transmitter and receiver. The signals from the antennas are combined to minimize errors and optimize data speed, providing better range and performance. However, the use of multiple inputs and outputs requires a device to utilize the same radio spectrum frequency. The United States presently uses the GSM-850 and GSM-1900 radio spectrum frequencies for cellular transmissions. GSM-850 uses 824-849 MHz for uplink and 869-894 MHz for downlink, providing channel numbers 128-251. GSM-1900 uses 1850-1910 MHz to uplink and 1930-1990 MHz to downlink, providing channel numbers 512-818. The MIMO concept defined in Third Generation Partnership Project Revision 7 (3GPP R7) and Revision 8 (MIMO R8), incorporated by reference herein in their entirety into this disclosure, requires the use of the same radio spectrum frequency for both transmission paths. These frequencies and antennas are used in spatial multiplexing or transmission diversity mode according to radio conditions. This allows for multiple simultaneous data streams, thereby increasing the data transmission rate.
MIMO R8 also requires twice the amount of antennas at both the transmitter and the receiver locations, even though the transmission takes place across a single frequency band. This creates interference in the signal, which decreases the actual gain in bandwidth created by MIMO R8. The additional signal used in MIMO R8 is another two-way transmit path. Although MIMO R8 can have up to four transmit paths, the uplink bandwidth is still equivalent to the downlink bandwidth, because each additional transmit path adds a duplex channel.
Demanding data services for individual users can exceed the capabilities of a single frequency carrier and/or radio path for a variety of transmission technologies. In this case, the capacity of multiple bi-directional frequency carriers and/or radio paths are combined, or “bonded” for the single demanding user. Multiple pre-existing bi-directional transmission pairs are allocated to the demanding user and traffic is spread across them. The Federal Communications Commission (FCC) recently auctioned the 700 MHz frequency spectrum. AWS-700 uses 776-794 MHz for uplink and 746-764 MHz for downlink. As is, these transmission techniques offer useful means to boost individual peak throughput within the capabilities of the available transmission technology.
However, bi-directional frequency carriers and/or radio paths, and the equipment required to use them, are best utilized if the data load and equipment capabilities are symmetrical. Unfortunately, this is often not the case. Traffic for most data, audio, and video applications is heavily weighted in the downlink, server to user, direction. Roughly eight times as much data is downloaded to as is uploaded from mobile devices. The number of duplex signals available may limit these downlink requests. Many frequency bands are not intended for and not licensed for transmission by an individual user. Currently there are many of these frequencies available for downlink only which are being underutilized. Subscriber equipment, especially wireless, is also limited in terms of available space, power (battery life for mobile devices) and cost. The need for subscriber equipment to simultaneously transmit on all bonded frequency carriers and/or radio paths is therefore an unnecessary burden from an equipment complexity, cost and power perspective.
What is needed is a system that utilizes a downlink only channel to supplement the bandwidth of a conventional duplex channel to distribute the data load.
The present application supplements a duplex frequency by providing one or more simplex frequencies and distributing a data load among them. Embodiments of the present application include a server containing a scheduler in communication with a communications device. The server initially communicates with the communications device using a duplex channel, or anchor channel. The scheduler determines when it is no longer optimal to use the single duplex channel, and distributes data among the duplex channel and one or more simplex channels. Before sending this data through multiple channels, the server must first send a schedule to the communications device, so the communications device knows which bits of data are coming through which channels at which times. The scheduler compiles this schedule and sends it to the communications device through the duplex channel. A descheduler within the communications device receives the schedule and alerts the communications device to start receiving data on other simplex channels. The descheduler then puts the bits of data in order as they stream in across the duplex and simplex channel.
Furthermore, embodiments of the present application are not limited to HSPA, LTE, or wireless communication at all. The methods described herein are useful for any bi-directional communications system where there is more traffic in one direction than the other. Embodiments of the present application are not limited to improving downlink capacity, as a simplex channel could be used to improve uplink capacity. For even more capacity multiple simplex channels can be used alongside the duplex channel.
In one exemplary embodiment, a communications device is provided comprising a memory, a descheduler on the memory, and a transceiver which communicates on a plurality of channels. An anchor channel is used for duplex transmission and one or more simplex channels are used to supplement one direction of the anchor channel.
In another exemplary embodiment, the present application provides an asymmetrical multicarrier communications system comprising a server, a scheduler in communication with the server, and a communications device in communication with the server via a plurality of channels. An anchor channel is used for a duplex transmission and one or more simplex channels are used to supplement one direction of the anchor channel.
In yet another exemplary embodiment, the present application provides a method of supplementing a data transmission of a duplex communication comprising selecting one or more simplex channels, compiling a data schedule, sending the data schedule to a recipient through a duplex channel, and sending the data transmission through the duplex channel and a first simplex channel. The data schedule comprises an association of bits of data to channels in which each bit is sent.
The present application supplements a duplex frequency by providing one or more simplex frequencies and distributing a data load among them. Embodiments of the present application include a server containing a scheduler in communication with a communications device. The server initially communicates with the communications device using a duplex channel, or anchor channel. The scheduler determines when it is no longer optimal to use the single duplex channel, and distributes data among the duplex channel and one or more simplex channels. Device feedback of the received data, such as level, quality, load, and various parameter settings are used to balance the transmission across duplex and simplex radio channels. These factors may all contribute to the initial and adapted ratio of data traffic sent on the various channels. Before sending this data through multiple channels, the server must first send a schedule to the communications device, so the communications device knows which bits of data are coming through which channels at which times. The scheduler compiles this schedule and sends it to the communications device through the duplex channel. A descheduler within the communications device receives the schedule and alerts the communications device to start receiving data on other simplex channels. The descheduler then puts the bits of data in order as they stream in across the duplex and simplex channels.
Furthermore, embodiments of the present application are not limited to HSPA, LTE, or wireless communication at all. The methods described herein are useful for any bi-directional communications system where there is more traffic in one direction than the other. Embodiments of the present application are not limited to improving downlink capacity, as a simplex channel could be used to improve uplink capacity. For even more capacity multiple simplex channels can be used alongside the duplex channel.
“Channel,” as used herein and throughout this disclosure, refers to a single data pipeline among a plurality. Examples of channels include, but are not limited to, a specific frequency, a single cable when many are present, a specific radio path, a block of frequencies, a single wideband carrier, etc.
“Duplex,” as used herein and throughout this disclosure, refers to a channel capable of bidirectional communication. Most duplex channels are symmetrical, meaning they have equal bandwidth in each direction.
“Simplex,” as used herein and throughout this disclosure, refers to a channel capable of unidirectional communication. Most simplex channels are set to one direction or the other, but some can switch back and forth.
“Communications device,” as used herein and throughout this disclosure, refers to any device capable of sending and receiving electronic bits of data. Examples of a communications device include but are not limited to mobile and land-line telephones, computers, personal digital assistants (PDAs), two-way radios, walkie-talkies, satellite transceivers, etc.
According to this embodiment, a channel within the 1900 MHz frequency band is used for most communication since it is the duplex or anchor channel. Another channel, within the 850 MHz frequency band, is used as a simplex channel. Since many cellular towers already use these frequencies the current hardware can be utilized to implement this embodiment. However, simplex channels that are licensed for downlink only can also be used to supplement the duplex channel since uplink is only required on one channel.
In further embodiments of the present application, simplex channels may instead be used in the uplink direction. Users with high volumes of data that need to be uploaded use the simplex channels to send data to the server. This may require the use of different frequencies for uplink and downlink because there are some frequencies that are only licensed for one or the other.
In other exemplary embodiments, using for example, the system presented in
Due to a current limit in the power of the 1900 MHz antenna the same configuration may not be possible in the far field. Another exemplary embodiment uses a channel within the 850 MHz frequency band for the anchor channel, while a channel within the 1900 MHz frequency band is used for downlink only. Similar to the last example, channel 222 breaks down into four parts. Channel 222A is a payload uplink where communications device 200A sends information to the server such as requests for content, outgoing email, etc. Channel 222B is a payload downlink where communications device 200A receives internet content, incoming email, etc. Channel 222B is the main gateway for receiving data on communications device 200A, and is the pipeline that needs broadening. Channel 220E is another downlink that effectively doubles the bandwidth in the downlink direction when combined with Channel 222B. However, in order to receive data on both channels 222B and 220E, a schedule must be transmitted by server 212 to communications device 200A. Channels 222C and 2220 serve as bidirectional control plain uplink and downlink, respectively, solely for this schedule. The schedule is received by communications device 200A through channel 2220. Once the packets of data from the schedule have been received by communications device 200A, confirmation of the reception is sent through channel 222C.
In other embodiments of the process shown in
Even more downlink channels can be used alongside an anchor channel to supplement the downlink, or alternatively the uplink direction of a communications device.
The foregoing disclosure of the exemplary embodiments of the present application has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the application to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be apparent to one of ordinary skill in the art in light of the above disclosure. The scope of the invention is to be defined only by the claims appended hereto, and by their equivalents.
Further, in describing representative embodiments of the present application, the specification may have presented the method and/or process of the present application as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. In addition, the claims directed to the method and/or process of the present application should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the present inventions.
This application is a continuation of, and claims priority to each of, U.S. patent application Ser. No. 15/977,467 (now U.S. Pat. No. 10,389,511), filed May 11, 2018 and entitled “DEVICES AND METHODS FOR ASYMMETRICAL MULTICARRIER TRANSMISSION AND RECEPTION,” which is a continuation of U.S. patent application Ser. No. 14/857,429 (now U.S. Pat. No. 9,998,273), filed Sep. 17, 2015 and entitled “DEVICES AND METHODS FOR ASYMMETRICAL MULTICARRIER TRANSMISSION AND RECEPTION,” which is a continuation of U.S. patent application Ser. No. 13/421,734 (now U.S. Pat. No. 9,167,595), filed Mar. 15, 2012 and entitled “DEVICES AND METHODS FOR ASYMMETRICAL MULTICARRIER TRANSMISSION AND RECEPTION,” which is a continuation of Ser. No. 12/334,353 (now U.S. Pat. No. 8,150,467), filed Dec. 12, 2008, and entitled “DEVICES AND METHODS FOR ASYMMETRICAL MULTICARRIER TRANSMISSION AND RECEPTION.” The entireties of these applications are hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5546549 | Barrett et al. | Aug 1996 | A |
5809395 | Hamilton-Piercy et al. | Sep 1998 | A |
5952922 | Shober | Sep 1999 | A |
5970056 | Brailean et al. | Oct 1999 | A |
6175550 | van Nee | Jan 2001 | B1 |
6356540 | Kojiro | Mar 2002 | B1 |
6791952 | Lin et al. | Sep 2004 | B2 |
6980533 | Abraham et al. | Dec 2005 | B1 |
7206581 | Zhang et al. | Apr 2007 | B2 |
7359311 | Paranjpe et al. | Apr 2008 | B1 |
7415282 | Tillet et al. | Aug 2008 | B2 |
7636327 | Doran | Dec 2009 | B1 |
7912070 | Choksi | Mar 2011 | B1 |
8149743 | Choksi | Apr 2012 | B1 |
8811240 | Chindapol et al. | Aug 2014 | B2 |
8879602 | Brisebois | Nov 2014 | B2 |
9319210 | Choi et al. | Apr 2016 | B2 |
9621194 | Brisebois | Apr 2017 | B2 |
9655004 | Yu et al. | May 2017 | B2 |
20020193146 | Wallace et al. | Dec 2002 | A1 |
20030161343 | Ghosh | Aug 2003 | A1 |
20040071163 | Hogberg | Apr 2004 | A1 |
20040198425 | Mellone et al. | Oct 2004 | A1 |
20040213144 | Murakami et al. | Oct 2004 | A1 |
20050181752 | Sahota | Aug 2005 | A1 |
20060025165 | Tillet et al. | Feb 2006 | A1 |
20060041657 | Wen et al. | Feb 2006 | A1 |
20060056534 | Ionescu et al. | Mar 2006 | A1 |
20060067263 | Li et al. | Mar 2006 | A1 |
20060142021 | Mueckenheim et al. | Jun 2006 | A1 |
20060146750 | Chen et al. | Jul 2006 | A1 |
20060229093 | Bhutiani et al. | Oct 2006 | A1 |
20060256761 | Meylan et al. | Nov 2006 | A1 |
20070110029 | Gilmore, II | May 2007 | A1 |
20070239885 | Vadlakonda et al. | Oct 2007 | A1 |
20080037502 | Yokoyama | Feb 2008 | A1 |
20080117859 | Shahidi et al. | May 2008 | A1 |
20080137606 | Zuniga | Jun 2008 | A1 |
20080174470 | Lum et al. | Jul 2008 | A1 |
20080232311 | Reumerman | Sep 2008 | A1 |
20090036062 | Tanaka et al. | Feb 2009 | A1 |
20090180402 | Lindoff et al. | Jul 2009 | A1 |
20090203326 | Vesma et al. | Aug 2009 | A1 |
20090232233 | Duan et al. | Sep 2009 | A1 |
20090296609 | Choi et al. | Dec 2009 | A1 |
20100008332 | Balachandran et al. | Jan 2010 | A1 |
20100034123 | Razdan et al. | Feb 2010 | A1 |
20110007664 | Diab et al. | Jan 2011 | A1 |
20120178373 | Brisebois | Jul 2012 | A1 |
20120182952 | Stanwood et al. | Jul 2012 | A1 |
20130083835 | Gupta | Apr 2013 | A1 |
20130287042 | Kliger | Oct 2013 | A1 |
20130336147 | Tong et al. | Dec 2013 | A1 |
20150003398 | Agrawal et al. | Jan 2015 | A1 |
20150009865 | Sharma et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
2009002269 | Dec 2008 | WO |
Entry |
---|
Non-Final Office Action dated Jun. 6, 2014 for U.S. Appl. No. 13/688,486, 21 pages. |
Non-Final Office Action dated Mar. 15, 2011 for U.S. Appl. No. 12/206,774, 14 pages. |
Non-Final Office Action dated Aug. 23, 2011 for U.S. Appl. No. 12/206,774, 15 pages. |
Non-Final Office Action dated Aug. 23, 2011 for U.S. Appl. No. 12/334,353, 23 pages. |
International Search Report and Written Opinion received for PCT Application Serial No. PCT/US2010/042007 dated Jan. 26, 2011, 15 pages. |
3GPP TS 25.308 V7.0.0; Jun. 18, 2009; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 (Release 7) 52 pgs. |
3GPP TS 25.308 V8.6.0; Jun. 18, 2009; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 (Release 8) 63 pgs. |
3GPP TS 25.308 V9.0.0; Jun. 18, 2009; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 (Release 9) 65 pgs. |
3GPP TS 25.308 V7.8.0 (Sep. 2008);Technical Specification; 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 (Release 7); 51 pgs. |
3GPP TS 25.308 V8.3.0 (Sep. 2008);Technical Specification; 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 (Release 8) 56 pgs. |
3GPP TS 36.300 V8.6.0 (Sep. 2008);Technical Specification;3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8) 137 pgs. |
Final Office Action dated Sep. 11, 2013 for U.S. Appl. No. 12/508,711, 28 pages. |
Final Office Action dated Oct. 15, 2012 for U.S. Appl. No. 12/508,711, 28 pages. |
Non-Final Office Action dated Feb. 24, 2014 for U.S. Appl. No. 12/508,711, 31 pages. |
Non-Final Office Action dated Mar. 14, 2013 for U.S. Appl. No. 12/508,711, 25 pages. |
Non-Final Office Action dated Apr. 3, 2012 for U.S. Appl. No. 12/508,711, 24 pages. |
Non-Final Office Action dated Jun. 4, 2012 for U.S. Appl. No. 13/422,608, 20 pages. |
Notice of Allowance dated Oct. 8, 2014 for U.S. Appl. No. 13/688,486, 20 pages. |
Non-Final Office Action dated Mar. 3, 2015 for U.S. Appl. No. 13/421,734, 33 pages. |
Non-Final Office Action dated Feb. 26, 2015 for U.S. Appl. No. 14/502,442, 17 pages. |
Non-Final Office Action dated May 11, 2016 for U.S. Appl. No. 14/918,187, 25 pages. |
Non-Final Office Action dated Feb. 6, 2017 for U.S. Appl. No. 14/857,429, 40 pages. |
Non-Final Office Action dated Apr. 19, 2017 for U.S. Appl. No. 15/469,451, 17 pages. |
Office Action dated May 16, 2017 for U.S. Appl. No. 15/469,451, 13 pages. |
Final Office Action dated May 15, 2017 for U.S. Appl. No. 14/857,429, 27 pages. |
Non-Final Office Action dated Sep. 8, 2017 for U.S. Appl. No. 14/857,429, 36 pages. |
Non-Final Office Action dated Nov. 13, 2018 for U.S. Appl. No. 15/977,467, 42 pages. |
U.S. Appl. No. 15/977,467, filed May 11, 2018, U.S. Pat. No. 10,389,511. |
U.S. Appl. No. 14/857,429, filed Sep. 17, 2015, U.S. Pat. No. 9,998,273. |
U.S. Appl. No. 13/421,734, filed Mar. 15, 2012, U.S. Pat. No. 9,167,595. |
U.S. Appl. No. 12/334,353, filed Dec. 12, 2008, U.S. Pat. No. 8,150,467. |
Number | Date | Country | |
---|---|---|---|
20190327071 A1 | Oct 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15977467 | May 2018 | US |
Child | 16503429 | US | |
Parent | 14857429 | Sep 2015 | US |
Child | 15977467 | US | |
Parent | 13421734 | Mar 2012 | US |
Child | 14857429 | US | |
Parent | 12334353 | Dec 2008 | US |
Child | 13421734 | US |