Methods, systems, and devices for separating signaling data and traffic data onto separate carriers for wireless communications systems are provided. Some embodiments utilize flexible bandwidth that may utilize portions of spectrum that may not be big enough to fit a normal waveform through utilizing flexible waveforms. flexible bandwidth systems may lead to reduced data rate on the signaling or other channels. Separating the signaling and the data traffic into different flexible bandwidth carriers so that assigned resources can be customized to different traffic patterns may address this issue. In some embodiments, the signaling data is received and/or transmitted over a first carrier separate from any other traffic data. For example, the signaling data may be received and/or transmitted over the first band carrier without any other traffic data. The traffic data and/or network data associated with the signaling data may be received and/or transmitted over a separate, second carrier.
|
13. A method of wireless communications, the method comprising:
at least transmitting or receiving traffic data over a first carrier, wherein the first carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable; and
transmitting signaling data associated with the traffic data over a second carrier separate from any other traffic data.
54. A wireless communications system comprising
a means for at least transmitting or receiving traffic data over a first carrier, wherein the first carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable; and
a means for transmitting signaling data associated with the traffic data over a second carrier separate from any other traffic data.
1. A method of wireless communications, the method comprising:
receiving signaling data over a first carrier; and
transitioning from receiving the signaling data over the first carrier to at least transmitting or receiving traffic data associated with the signaling data over a second carrier, wherein the first carrier or the second carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable.
39. A wireless communications system comprising:
a means for receiving signaling data over a first carrier; and
a means for transitioning from receiving signaling data over the first carrier to at least transmitting or receiving traffic data associated with the signaling data over a second carrier, wherein the first carrier or the second carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable.
64. A wireless communications device comprising:
at least one processor configured to:
at least transmit or receive traffic data over a first carrier, wherein the first carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable; and
transmit signaling data associated with the traffic data over a second carrier separate from any other traffic data; and
at least one memory coupled with the at least one processor.
59. A computer program product for a wireless communications system comprising:
a non-transitory computer-readable medium comprising:
code for at least transmitting or receiving traffic data over a first carrier, wherein the first carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable; and
code for transmitting signaling data associated with the traffic data over a second carrier separate from any other traffic data.
49. A wireless communications device comprising:
at least one processor configured to:
receive signaling data over a first carrier; and
transition from receiving signaling data over the first carrier to at least transmitting or receiving traffic data associated with the signaling data over a second carrier, wherein the first carrier or the second carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable; and
at least one memory coupled with the at least one processor.
44. A computer program product for a wireless communications system comprising:
a non-transitory computer-readable medium comprising:
code for receiving signaling data over a first carrier; and
code for transitioning from receiving signaling data associated with the signaling data over the first carrier to at least transmitting or receiving traffic data over a second carrier, wherein the first carrier or the second carrier comprises a scaled flexible bandwidth carrier that is dynamically adjustable.
2. The method of
performing a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier.
3. The method of
transitioning from at least transmitting or receiving the traffic data over the second carrier to at least transmitting or receiving the traffic data over a third carrier.
4. The method of
transitioning from receiving the signaling data over the first carrier to receiving the signaling data over a fourth carrier.
6. The method of
7. The method of
8. The method of
9. The method of
scaling the first bandwidth utilizing a first scaling factor; and
scaling the second bandwidth utilizing a second scaling factor.
10. The method of
adjusting at least the first bandwidth or the second bandwidth dynamically.
11. The method of
adjusting at least the first bandwidth or the second bandwidth based upon expected traffic demand.
12. The method of
scaling at least an uplink or a downlink for at least the first bandwidth or the second bandwidth utilizing different scaling factors.
14. The method of
transitioning from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier.
15. The method of
transitioning from transmitting the signaling data to the mobile device over the second carrier to at least transmitting or receiving the traffic data to the mobile device over the first carrier.
16. The method of
performing a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting the signaling data over the second carrier.
17. The method of
20. The method of
22. The method of
23. The method of
24. The method of
25. The method of
26. The method of
27. The method of
28. The method of
29. The method of
30. The method of
31. The method of
32. The method of
33. The method of
34. The method of
35. The method of
at least transmitting or receiving traffic data over a third carrier; and
transmitting signaling data over the second carrier, wherein the second carrier carriers information regarding at least the first carrier or the third carrier.
36. The method of
at least transmitting or receiving traffic data over a third carrier; and
transmitting signaling data over a fourth carrier, wherein the fourth carrier carries information regarding at least the first carrier or the third carrier and the second carrier carries information regarding at least the first carrier or the third carrier.
37. The method of
38. The method of
40. The wireless communications system of
a means for performing a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier.
41. The wireless communications system of
a means for scaling the first bandwidth utilizing a first scaling factor; and
a means for scaling the second bandwidth utilizing a second scaling factor.
42. The wireless communications system of
a means for adjusting at least the first scaling factor or the second scaling factor dynamically.
43. The wireless communications system of
a means for adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
45. The computer program product of
code for performing a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier.
46. The computer program product of
code for scaling a bandwidth of the first carrier utilizing a first scaling factor; and
code for scaling a bandwidth of the second carrier utilizing a second scaling factor.
47. The computer program product of
code for adjusting at least the first scaling factor or the second scaling factor dynamically.
48. The computer program product of
code for adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
50. The wireless communications device of
perform a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier.
51. The wireless communications device of
scale a bandwidth of the first carrier utilizing a first scaling factor; and
scale a bandwidth of the second carrier utilizing a second scaling factor.
52. The wireless communications device of
adjust at least the first scaling factor or the second scaling factor dynamically.
53. The wireless communications device of
adjust at least the first scaling factor or the second scaling factor based upon expected traffic demand.
55. The wireless communications system of
a means for transitioning from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier.
56. The wireless communications system of
a means for transitioning from transmitting the signaling data to the mobile device over the second carrier to at least transmitting or receiving the traffic data to the mobile device over the first carrier.
57. The wireless communications system of
a means for performing a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting signaling data over the second carrier.
58. The wireless communications system of
a means for at least transmitting or receiving the traffic data over a third carrier; and
a means for transmitting signaling data over the second carrier, wherein the second carrier carries information regarding at least the first carrier or the second carrier.
60. The computer program product of
code for transitioning from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier.
61. The wireless communications system of
code for transitioning from transmitting the signaling data to the mobile device over the second carrier to at least transmitting or receiving the traffic data to the mobile device over the first carrier.
62. The computer program product of
code for performing a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting signaling data over the second carrier.
63. The computer program product of
code for at least transmitting or receiving traffic data over a third carrier; and
code for transmitting signaling data over the second carrier, wherein the second carrier carries information regarding at least the first carrier or the third carrier.
65. The wireless communications device of
transition from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier.
66. The wireless communications device of
transition from transmitting the signaling data to the mobile device over the second carrier to transmitting the traffic data to the mobile device over the first carrier.
67. The wireless communications device of
perform a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting signaling data over the second carrier.
68. The wireless communications device of
at least transmit or receive traffic data over a third carrier; and
transmit signaling data over the second carrier, wherein the second carrier carries information regarding at least the first carrier or the third carrier.
|
The present application for patent claims priority to Provisional Application No. 61/556,777 entitled “FRACTIONAL SYSTEMS IN WIRELESS COMMUNICATIONS” filed Nov. 7, 2011, and assigned to the assignee hereof and hereby expressly incorporated by reference herein. The present application for patent also claims priority to Provisional Application No. 61/568,742 entitled “SIGNAL CAPACITY BOOSTING, COORDINATED FORWARD LINK BLANKING AND POWER BOOSTING, AND REVERSE LINK THROUGHPUT INCREASING FOR FLEXIBLE BANDWIDTH SYSTEMS” filed Dec. 9, 2011, and assigned to the assignee hereof and hereby expressly incorporated by reference herein.
Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast messages, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, 3GPP Long Term Evolution (LTE) systems, and orthogonal frequency-division multiple access (OFDMA) systems.
Service providers are typically allocated blocks of frequency spectrum for exclusive use in certain geographic regions. These blocks of frequencies are generally assigned by regulators regardless of the multiple access technology being used. In most cases, these blocks are not integer multiples of channel bandwidths, hence there may be unutilized parts of the spectrum. As the use of wireless devices has increased, the demand for and value of this spectrum has generally surged, as well. Nonetheless, in some cases, wireless communications systems may not utilize portions of the allocated spectrum because the portions are not big enough to fit a standard or normal waveform. The developers of the LTE standard, for example, recognized the problem and decided to support 6 different system bandwidths, namely 1.4, 3, 5, 10, 15 and 20 MHz. This may provide one partial solution to the problem. Another approach may be to utilize flexible bandwidth systems that may involve wireless communications systems that utilize portions of spectrum that may not be big enough to fit a normal waveform. A flexible bandwidth system, however, may lead to reduced data rate on the signaling or other channels.
Methods, systems, and devices for separating signaling and traffic data into separate carriers for wireless communications systems are provided. Some embodiments address reduced capacity issues, such as reduced data rates on the signaling or other channels, as a result of utilizing flexible bandwidth. Some embodiments provide for boosting capacity in wireless communications systems. For example, separating the signaling and the data traffic into different carriers, which may be flexible bandwidth carriers in some cases, may be utilized so that assigned resources can be customized to different traffic patterns. In some embodiments, the signaling data is received and/or transmitted over a first carrier separate from any other traffic data. For example, signaling data may be received and/or transmitted over the first carrier without any other traffic data. The traffic data may be transmitted and/or received over a second carrier. The traffic data may be associated with the signaling data. The first carrier and/or the second carrier may be flexible bandwidth carriers. Some embodiments provide for transitioning between the first and second carriers. Some embodiments provide for performing a transition to utilizing the first and second carriers.
Flexible bandwidths systems may involve wireless communications systems that utilize portions of spectrum that may not be big enough to fit a normal waveform utilizing flexible waveforms. A flexible bandwidth system may be generated with respect to a normal bandwidth system through dilating, or scaling down, the time or the chip rate of the flexible bandwidth system with respect to the normal carrier bandwidth system. Some embodiments increase the bandwidth of a flexible waveform through expanding, or scaling up, the time or the chip rate of the flexible carrier bandwidth system.
Some embodiments include a method of wireless communications that includes receiving signaling data over a first carrier; and/or transitioning from receiving the signaling data over the first carrier to at least transmitting or receiving traffic data over a second carrier. Some embodiments include performing a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier. Some embodiments include transitioning from at least transmitting or receiving the traffic data over the second carrier to at least transmitting or receiving the traffic data over a third carrier. Some embodiments include transitioning from receiving the signaling data over the first carrier to receiving the signaling data over a fourth carrier. In some embodiments, signaling data is transmitted over the first carrier. In some embodiments, the first carrier carries information regarding the second carrier. Receiving the signaling data over the first carrier and at least transmitting or receiving the traffic data over the second carrier may occur a mobile device.
In some embodiments, at least the first carrier or the second carrier includes a flexible bandwidth carrier. In some embodiments, the first carrier utilizes a first bandwidth and the second carrier utilizes a second bandwidth. Some embodiments include scaling the first bandwidth utilizing a first scaling factor; and/or scaling the second bandwidth utilizing a second scaling factor. At least the first bandwidth or the second bandwidth may be adjusted dynamically. Adjusting at least the first bandwidth or the second bandwidth dynamically may include adjusting at least the first bandwidth or the second bandwidth based upon expected traffic demand. In some embodiments, scaling at least the first bandwidth utilizing the first scaling factor or scaling the second bandwidth utilizing the second factor include scaling at least an uplink or a downlink for at least the first bandwidth or the second bandwidth utilizing different scaling factors.
Some embodiments include a method of wireless communications that includes at least transmitting or receiving traffic data over a first carrier; and/or transmitting signaling data over a second carrier separate from any other traffic data. Some embodiments include transitioning from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier. Some embodiments include transitioning from transmitting the signaling data to the mobile device over the second carrier to at least transmitting or receiving the traffic data to the mobile device over the first carrier. Some embodiments include performing a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting the signaling data over the second carrier. In some embodiments, the second carrier carries information regarding at least the first carrier. Some embodiments include receiving signaling data over the second carrier.
In some embodiments, at least the first carrier or the second carrier includes a flexible bandwidth carrier. The first bandwidth and the second bandwidth may utilize a common scaling factor. At least the first carrier or the second carrier may include a normal bandwidth carrier.
In some embodiments, at least transmitting or receiving the traffic data or transmitting the signaling data boosts at least a signaling capacity, a traffic capacity, or a paging capacity. In some embodiments, the signaling data includes at least broadcast messages, system information paging, synchronization, pilot data, cell configuration parameters, pages, or operator specific information that may or not may not be needed for traffic data transmission on the first carrier. The traffic data may include at least user data or control information to assist the traffic data.
In some embodiments, the second carrier is utilized for an idle mode and the first bandwidth carrier is utilized for a connected mode. In some embodiments, users within the first carrier and the second carrier are separated by at least codes, time, or frequency. Users on the first carrier may be separated differently from those on the second carrier. Users within the first carrier are separated by time and the users on the second carrier may be separated by frequency.
In some embodiments, the first carrier utilizes FDD and the second carrier utilizes TDD. In some embodiments, at least the first carrier or the second carrier separates forward link and reverse link transmissions utilizing at least codes, time, or frequency. The first carrier and the second carrier may separate forward link and reverse link transmissions in different ways.
In some embodiments, a bandwidth of the first carrier is scaled utilizing a first scaling factor and a bandwidth of the second carrier is scaled utilizing a second scaling factor. At least the first scaling factor or the second scaling factor may be dynamically adjusted. Dynamically adjusting at least the first scaling factor or the second scaling factor may be based upon expected traffic demand.
Some embodiments include at least transmitting or receiving traffic data over a third carrier; and/or transmitting signaling data over the second carrier. The second carrier may carrier information regarding at least the first carrier or the third carrier. Some embodiments include at least transmitting or receiving traffic data over a third carrier; and/or transmitting signaling data over a fourth carrier. The fourth carrier may carry information regarding at least the first carrier or the third carrier and the second carrier carriers may carry information regarding at least the first carrier or the third carrier.
In some embodiments, at least transmitting or receiving at least the traffic data or the signaling data occurs at a base station. In some embodiments, at least transmitting or receiving at least the traffic data or the signaling data occurs at a mobile device.
Some embodiments include a wireless communications system that includes: a means for receiving signaling data over a first carrier; and a means for transitioning from receiving signaling data over the first carrier to at least transmitting or receiving traffic data over a second carrier. Some embodiments include a means for performing a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier.
In some embodiments, a first carrier utilizes a first bandwidth and the second carrier utilizes a second bandwidth. Some embodiments may also include: a means for scaling the first bandwidth utilizing a first scaling factor; and/or a means for scaling the second bandwidth utilizing a second scaling factor. Some embodiments include a means for adjusting at least the first scaling factor or the second scaling factor dynamically. The means for adjusting at least the first scaling factor or the second scaling factor dynamically may include a means for adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Some embodiments include a computer program product for a wireless communications system that includes a non-transitory computer-readable medium that includes: code for receiving signaling data over a first carrier; and/or code for transitioning from receiving signaling data over the first carrier to at least transmitting or receiving traffic data over a second carrier.
The non-transitory computer-readable medium may include code for performing a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier. The non-transitory computer-readable medium may include: code for scaling a bandwidth of the first carrier utilizing a first scaling factor; and/or code for scaling a bandwidth of the second carrier utilizing a second scaling factor. The non-transitory computer-readable medium may include code for adjusting at least the first scaling factor or the second scaling factor dynamically. The non-transitory computer-readable medium including code for adjusting at least the first scaling factor or the second scaling factor dynamically may include code for adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Some embodiments include a wireless communications device that includes at least one processor configured to: receive signaling data over a first carrier; and/or transition from receiving signaling data over the first carrier to at least transmitting or receiving traffic data over a second carrier. The device may also include at least one memory coupled with the at least one processor. The at least one processor may be configured to: perform a transition from at least transmitting or receiving the traffic data over the second carrier to receiving the signaling data over the first carrier. The at least one processor may be configured to: scale a bandwidth of the first carrier utilizing a first scaling factor; and/or scale a bandwidth of the second carrier utilizing a second scaling factor. The at least one processor may be configured to adjust at least the first scaling factor or the second scaling factor dynamically. The at least one processor configured to adjust at least the first scaling factor or the second scaling factor dynamically may be configured to adjust at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Some embodiments include a wireless communications system that includes: a means for at least transmitting or receiving traffic data over a first carrier; and/or a means for transmitting signaling data over a second carrier separate from any other traffic data. The system may include a means for transitioning from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier. The system may include a means for transitioning from transmitting the signaling data to the mobile device over the second carrier to at least transmitting or receiving the traffic data to the mobile device over the first carrier. Some embodiments include a means for performing a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting signaling data over the second carrier. Some embodiments include a means for at least transmitting or receiving the traffic data over a third carrier; and/or a means for transmitting signaling data over the second carrier. The second carrier may include information regarding at least the first carrier or the second carrier.
Some embodiments include a computer program product for a wireless communications system that include a non-transitory computer-readable medium that includes: code for at least transmitting or receiving traffic data over a first carrier; and/or code for transmitting signaling data over a second carrier separate from any other traffic data. The non-transitory computer-readable medium may include code for transitioning from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier. Some embodiments include code for transitioning from transmitting the signaling data to the mobile device over the second carrier to at least transmitting or receiving the traffic data to the mobile device over the first carrier. The non-transitory computer-readable medium may include code for performing a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting signaling data over the second carrier. The non-transitory computer-readable medium may include: code for at least transmitting or receiving traffic data over a third carrier; and/or code for transmitting signaling data over the second carrier, wherein the second carrier carriers carries information regarding at least the first carrier or the third carrier.
Some embodiments include a wireless device that includes at least one processor configured to: at least transmit or receive traffic data over a first carrier; and/or transmit signaling data over a second carrier separate from any other traffic data. The device may include at least one memory coupled with the at least one processor. The at least one processor may be configured to transition from at least transmitting or receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier. The at least one processor may be configured to transition from transmitting the signaling data to the mobile device over the second carrier to transmitting the traffic data to the mobile device over the first carrier. The at least one processor may be configured to perform a transition to at least transmitting or receiving the traffic data over the first carrier and transmitting signaling data over the second carrier. The at least one processor may be configured to: at least transmit or receive traffic data over a third carrier; and/or transmit signaling data over the second carrier. The second carrier may carry information regarding at least the first carrier or the third carrier.
The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the spirit and scope of the appended claims. Features which are believed to be characteristic of the concepts disclosed herein, both as to their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description only, and not as a definition of the limits of the claims.
A further understanding of the nature and advantages of the present invention may be realized by reference to the following drawings. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
Methods, systems, and devices for separating signaling and traffic data into separate carriers for wireless communications systems are provided. Some embodiments address reduced capacity issues, such as reduced data rates on the signaling or other channels, as a result of utilizing flexible bandwidth. Some embodiments provide for boosting capacity in wireless communications systems. For example, separating the signaling and the data traffic into different carriers, which may be flexible bandwidth carriers in some cases, may be utilized so that assigned resources can be customized to different traffic patterns. In some embodiments, the signaling data is received and/or transmitted over a first carrier separate from any other traffic data. For example, signaling data may be received and/or transmitted over the first carrier without any other traffic data. The traffic data may be transmitted and/or received over a second carrier. The traffic data may be associated with the signaling data. The first carrier and/or the second carrier may be flexible bandwidth carriers. Some embodiments provide for transitioning between the first and second carriers. Some embodiments provide for performing a transition to utilizing the first and second carriers.
Flexible bandwidths systems may involve wireless communications systems that utilize portions of spectrum that may not be big enough to fit a normal waveform utilizing flexible waveforms. A flexible bandwidth system may be generated with respect to a normal bandwidth system through dilating, or scaling down, the time or the chip rate of the flexible bandwidth system with respect to the normal carrier bandwidth system. Some embodiments increase the bandwidth of a flexible waveform through expanding, or scaling up, the time or the chip rate of the flexible carrier bandwidth system.
Techniques described herein may be used for various wireless communications systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, Peer-to-Peer, and other systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0 and A are commonly referred to as CDMA20001x, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA or OFDM system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.
Thus, the following description provides examples, and is not limiting of the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to certain embodiments may be combined in other embodiments.
Referring first to
The mobile devices 115 may be any type of mobile station, mobile device, access terminal, subscriber unit, or user equipment. The mobile devices 115 may include cellular phones and wireless communications devices, but may also include personal digital assistants (PDAs), smartphones, other handheld devices, netbooks, notebook computers, etc. Thus, the term mobile device should be interpreted broadly hereinafter, including the claims, to include any type of wireless or mobile communications device.
The base stations 105 may wirelessly communicate with the mobile devices 115 via a base station antenna. The base stations 105 may be configured to communicate with the mobile devices 115 under the control of the controller 120 via multiple carriers. Each of the base station 105 sites can provide communication coverage for a respective geographic area. In some embodiments, base stations 105 may be referred to as a NodeB, eNodeB, Home NodeB, and/or Home eNodeB. The coverage area for each base station 105 herein is identified as 110-a, 110-b, or 110-c. The coverage area for a base station may be divided into sectors (not shown, but making up only a portion of the coverage area). The system 100 may include base stations 105 of different types (e.g., macro, micro, femto, and/or pico base stations).
The different aspects of system 100, such as the mobile devices 115, the base stations 105, the core network 130, and/or the controller 120 may be configured to utilize flexible bandwidth and waveforms in accordance with various embodiments. System 100, for example, shows transmissions 125 between mobile devices 115 and base stations 105. The transmissions 125 may include uplink and/or reverse link transmission, from a mobile device 115 to a base station 105, and/or downlink and/or forward link transmissions, from a base station 105 to a mobile device 115. The transmissions 125 may include flexible and/or normal waveforms. Normal waveforms may also be referred to as legacy and/or normal waveforms.
The different aspects of system 100, such as the mobile devices 115, the base stations 105, the core network 130, and/or the controller 120 may be configured to utilize flexible bandwidth and waveforms in accordance with various embodiments. For example, different aspects of system 100 may utilize portions of spectrum that may not be big enough to fit a normal waveform. Devices such as the mobile devices 115, the base stations 105, the core network 130, and/or the controller 120 may be configured to adapt the chip rates and/or scaling factors to generate and/or utilize flexible bandwidth and/or waveforms. Some aspects of system 100 may form a flexible subsystem (such as certain mobile devices 115 and/or base stations 105) that may be generated with respect to a normal subsystem (that may be implemented using other mobile devices 115 and/or base stations 105) through dilating, or scaling down, the time of the flexible subsystem with respect to the time of the normal subsystem.
In some embodiments, the different aspects of system 100, such as the mobile devices 115, the base stations 105, the core network 130, and/or the controller 120 are configured for separating the signaling and the traffic and/or network data into different carriers, which may be flexible. This may result in capacity boosting. In some cases, the assigned resources can be customized to the traffic pattern as a result of the separation. Some of the mobile devices 115 and/or base stations 105 may be configured to receive signaling data over a first carrier and then to transition from receiving signaling data over the first carrier to transmitting and/or receiving traffic data over a second carrier. The traffic data may correspond to the signal data in some cases. The first carrier may carry information regarding the second carrier. In some embodiments, the signaling data is received over the first carrier separate from any other traffic data. For example, the signaling data may be received over the first carrier without any other traffic data.
Some of the mobile devices 115 and/or base stations 105 may be configured to scale a bandwidth of the first carrier utilizing a first scaling factor and scale a bandwidth of the second carrier utilizing a second scaling factor. The first scaling factor and the second scaling factor may be the same or different. The scaling factor may be unity. The scaling factors may be associated with specific flexible bandwidths. Some of the mobile devices 115 and/or base stations 105 may dynamically adjust at least the first scaling factor or the second scaling. Adjusting at least the first scaling factor or the second scaling factor dynamically may include adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Some embodiments may include mobile devices 115 and/or base stations 105 that may generate flexible waveforms and/or normal waveforms. Flexible waveforms may occupy less bandwidth than a normal waveform. For example, at a band edge, there may not be enough available spectrum to place a normal waveform. For a flexible waveform in some embodiments, as time gets dilated, the frequency occupied by a waveform goes down, thus making it possible to fit a flexible waveform into spectrum that may not be broad enough to fit a normal waveform. Flexible waveforms may also be generated in some embodiments through using a scaling factor. Other embodiments may generate a flexible waveform to fit a portion of spectrum through altering a rate or chip rate (e.g., a spreading factor may change). Some embodiments may change a frequency of processing to change a chip rate or utilize a scaling factor. Changing frequency of processing may include changing an interpolation rate, an interruption rate, and/or a decimation rate. In some embodiments, a chip rate may be changed or a scaling factor utilized through filtering, by decimation, and/or by changing a frequency of an ADC, a DAC, and/or an offline clock. A divider may be used to change the frequency of at least one clock.
In some embodiments, a flexible system or waveform may be a fractional system or waveform. Fractional systems and/or waveforms may or may not change bandwidth for example. A fractional system or waveform may be flexible because it may offer more possibilities than a normal system or waveform (e.g., N=1 system). A normal system or waveform may refer to a standard and/or legacy system or waveform.
Some of the mobile device 115-c, the mobile device 115-d and/or the base station 105-c may be configured to scale a bandwidth of the first carrier utilizing a first scaling factor and scale a bandwidth of the second carrier utilizing a second scaling factor. The first scaling factor and the second scaling factor may be the same or different. The scaling factors may be associated with specific flexible bandwidths. Some of the mobile device 115-c, the mobile device 115-d and/or the base station 105-c may be configured to dynamically adjust at least the first scaling factor or the second scaling factor. Adjusting at least the first scaling factor or the second scaling factor dynamically may include adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Transmissions 305-a and/or 305-b between the mobile device 115-c/115-d and the base station 105-a may utilize flexible waveforms that may be generated to occupy less bandwidth than a normal waveform. For example, at a band edge, there may not be enough available spectrum to place a normal waveform. For a flexible waveform, as time gets dilated, the frequency occupied by a waveform goes down, thus making it possible to fit a flexible waveform into spectrum that may not be broad enough to fit a normal waveform. In some embodiments, the flexible waveform may be scaled utilizing a scaling factor N with respect to a normal waveform. Scaling factor N may take on numerous different values including, but not limited to, integer values such as 1, 2, 4, etc. N, however, does not have to be an integer.
Some embodiments may utilize additional terminology. A new unit D may be utilized. The unit D is dilated. The unit is unitless and has the value of N. One can talk about time in the flexible system in terms of “dilated time.” For example, a slot of say 10 ms in normal time may be represented as 10 Dms in flexible time (note: even in normal time, this will hold true since N=1 in normal time: D has a value of 1, so 10 Dms=10 ms). In time scaling, one can replace most “seconds” with “dilated-seconds.” Note frequency in Hertz is 1/s.
Some embodiments may include methods, systems, and/or devices for boosting capacity in wireless communications networks, including flexible bandwidth networks. The flexible bandwidth (FB) networks may lead to reduced data rate on the signaling channels. This may lead to reduced paging and/or broadcast capacity in the cell that could cause a problem for machine to machine (M2M) type applications where the number of devices in the network is expected to be high (e.g., in the millions). Mobile devices may experience an increase in delay in acquiring paging, broadcast messages, and/or data channel due to time stretching by flexible bandwidth scaling factor, N (especially for high N, e.g., N=16). Capacity boosting may include boosting signaling capacity, traffic capacity, network capacity, and/or paging capacity.
Some embodiments may address these issues through separating the signaling and the data traffic into different flexible bandwidth carriers so that assigned resources can be customized to the traffic pattern.
Separating the signaling and the data traffic into different carriers, such as flexible bandwidth carriers, may provide different benefits. For example, embodiments may increase the signaling capacity available in each flexible bandwidth carrier since previously reserved and/or unallocated codes, time slots, and/or frequencies bins for traffic can now be allocated solely to signaling. Likewise, traffic capacity available in each flexible bandwidth carrier may increase since previously reserved and/or unallocated codes, time slots, and/or frequencies bins for signaling can now be allocated solely to traffic. Embodiments may provide for decreasing the flexible bandwidth mobile device's waiting time in acquiring signaling and/or traffic (e.g., by a factor of K, where K is the number of freed-up channels previously for signaling or traffic). Embodiments may decrease mobile devices' waiting time leading to reduced power consumption. Embodiments may enable appropriate selection of N for all mobile device states (e.g., signaling, very small packets (e.g., sent in the UMTS RRC CELL_FACH state) or larger packets (e.g., sent in the UMTS RRC CELL_DCH)). A UMTS Release 99 mobile device can either be in the idle mode (which may be referred to as IDLE mode in some cases) or connected mode, for example.
An idle state may be a user state where no dedicated core network and radio resources are generally available to the mobile device, however, common resources may be used by the network in sending messages such as broadcast system information and pages to the mobile device. The mobile device's location may only be known to the network and not individual carriers or cells. In this state, the mobile device may be paged by the network to request radio resources when there is a mobile terminated call for the mobile device. To receive these pages, the mobile device can monitor the paging channel transmitted in a paging occasion every discontinuous reception (DRX) cycle. In IDLE mode, the DRX cycle may range between 640 ms and 5120 ms. In addition to paging channel monitoring, the mobile device also may perform functions such as periodic channel measurements, timing and frequency acquisition, inter-frequency and intra-frequency searches, inter-RAT searches, USIM polling, transmission of periodic location updates, etc.
The connected mode may include four states, such as, the URA_PCH/CELL_PCH, CELL_FACH and CELL_DCH. The network may transition the mobile device to the URA_PCH and CELL_PCH after a significant period of inactivity in CELL_DCH or CELL_FACH. The transition delay from these states back to CELL_DCH/CELL_FACH may be much lower than IDLE so these RRC states are used when the mobile device is expected to communicate with the network after some period of inactivity. The mobile device functions in these states may be similar to the IDLE state because the mobile device only monitors paging during paging occasions and does not perform any uplink transmissions. However, unlike the IDLE state, the mobile device may have radio resources which are assigned but preserved. In addition, the mobile device location may be known to the resolution of the cell in the CELL_PCH while in the URA_PCH, the mobile device is known on the UTRAN registration area (URA) level to the core network.
The CELL_FACH and CELL_DCH are two states where the mobile device can actively transmit and receive data from the network. In the CELL_FACH state, the mobile device and network may use common resources shared by other mobile devices in the cell while in CELL_DCH, dedicated resources assigned to mobile devices are used for communication. Unlike the URA_PCH, CELL_PCH and IDLE states where the mobile device monitors channels only during the paging occasions, in the CELL_FACH and CELL_DCH, the mobile device may continuously monitor data and control channels in WCDMA/HSPA Release 6 and earlier releases.
In some embodiments, different carriers can be mapped to different mobile device states. For example, in LTE, signaling carriers can be used for idle mode and traffic carriers used for connected mode especially. In UMTS, for example, different carriers can be used to carry data in the IDLE, CELL_FACH, CELL_DCH, URA_PCH and/or CELL_PCH modes. In some embodiments, IDLE and/or URA_PCH/CELL_PCH can be carried in the same signaling carrier (these are states where the mobile device may be receiving information from the network but not transmitting) and the CELL_DCH and/or CELL_FACH states (states where the mobile device may be actively transmitting and receiving data from the network) can be carried in the same traffic carrier.
In some embodiments, the Ns for the signaling and/or traffic carrier may be adjusted based on the expected traffic demand on the network. The signaling and traffic flexible carriers can have the same or different Ns (e.g., signaling flexible bandwidth carrier can use flexible bandwidth scaling factor, N=4, and the traffic flexible bandwidth carrier can use flexible bandwidth scaling factor, N=2). Multiple traffic flexible bandwidth carriers can share the signaling flexible bandwidth carrier. Signaling and traffic carriers Ns and frequencies can be selected to mitigate interference within a site or between adjacent sites.
While examples may be provided that utilize WCDMA and it terminology, separating signaling and traffic into different carriers, which may include flexible bandwidth carriers, can be applied to cellular technologies including, but not limited to, 1x, EV DO, LTE, FDD, TDD, TD-LTE, TD-SCDMA, TD-CDMA, etc. Furthermore, some embodiments may include a TDD system where typically one carrier is used to support both downlink and uplink transmissions. In this case, for both uplink and downlink transmissions, the signaling and data traffic information may be carried on separate carriers. In some embodiments, one of the carriers may be a FDD and the other may be a TDD (e.g., for downlink signaling). Furthermore, while embodiments are generally described where a signaling carrier and/or a traffic carrier may be flexible carriers, some embodiments may include signaling carriers and/or traffic carriers that may utilize normal carriers.
Merely by way of example, a mobile device may perform several different operations in relation to utilizing signaling flexible bandwidth carriers and traffic flexible bandwidth carriers. For example, a mobile device may power on and listen to a signaling flexible bandwidth carrier. In some cases, a mobile device may not realize when it is camping on a carrier that the carrier may be a signaling carrier. The mobile device may get system information that may include broadcasted system information to enable the mobile device to operate in idle mode). The mobile device may then register with the network using the signaling flexible bandwidth carrier. The mobile device may listen for pages and monitor other signaling and/or traffic flexible bandwidth carriers. While camping on the signaling carrier, the mobile device may receive a page or may want to originate a call in some cases so the mobile device may read the connected mode system information for specific information on how to access a selected flexible bandwidth traffic carrier. The mobile device may tune to the flexible bandwidth traffic carrier which supports CELL_FACH/CELL_DCH and may request radio resources on the traffic channel in order to make and/or receive calls. On the traffic carrier, the mobile device may transmit and/or receive packet data or voice data on the flexible bandwidth carrier and may also request and/or receive assistance data for accessing the next carrier (e.g., timing information about the signaling flexible bandwidth carrier) it intends to transition to when the call is completed. Once the call is completed, the mobile device may release the core network resources (i.e., bearers), and the mobile device may re-select to and camp on a signaling flexible bandwidth carrier (supporting IDLE mode). This example is for a UMTS WCDMA Release 99 scenario where the signaling carrier may support only the idle mode and the traffic carrier supports the CELL_FACH/CELL_DCH states. Some embodiments may utilize other states, divisions and/or groups (e.g., certain classes of overhead messages, paging, etc.).
Some embodiments may be implemented utilizing UMTS. Normal UMTS carriers today support all mobile device states in the same carrier (i.e., normal UMTS carrier=IDLE+CELL_FACH+CEL_PCH+CELL_DCH). In some embodiments, different signaling and traffic carriers providing support for these configurations is possible. For example, signaling may occur on the signaling carrier. In some embodiments, the IDLE, URA_PCH and CELL_PCH may be supported in separate signaling carriers; the CELL_FACH and CELL_DCH states may also be supported in separate traffic carriers. In some embodiments, the signaling carrier may include both IDLE and CELL_PCH/URA_PCH; the traffic carrier may also include both CELL_DCH and CELL_FACH states.
Some embodiments may include signaling and small packet transmission (especially for NAS mobility such as registration) on the signaling carrier. In those cases, a signaling carrier may include both IDLE and CELL_FACH states or both CELL_PCH/URA_PCH and CELL_FACH; the traffic carrier may include the CELL DCH, CELL_FACH, or both CELL_DCH and CELL_FACH states. In some embodiments, the signaling carrier may include IDLE, CELL_FACH and CEL_PCH/URA_PCH; the traffic carrier may include CELL_DCH, CELL_FACH, or CELL_DCH and CELL_FACH. Note that even though the signaling carrier may support CELL_FACH, the resources dedicated to the CELL_FACH state may be minimal compared to the IDLE/CELL_PCH states. Therefore, there could be other traffic carriers with CELL_FACH or CELL_DCH that the mobile device can migrate to to transmit medium to high data rate transmissions.
For example, the IDLE mobile device state may include the signaling carrier in accordance with various embodiments. Different channels in the mobile device state may be utilized including P-CCPCH, PICH & S-CCPCH, P-SCH & S-SCH, and/or CPICH. The P-CCPCH channel may include broadcasted system information like N, frequency, timing information of other signaling and traffic carriers, network load on those carriers, etc. Page indications may be sent in the PICH, and S-CCPCH and may be dedicated to pages as opposed to sharing between small packets and pages as done in existing Rel'99 systems. CPICH may carry pilots that may be required for synchronization and data demodulation. In some embodiments (e.g., Embodiment II), the PRACH & S-CCPCH for small packets may be added for mobile device registration, tracking updates, and/or small packet transmissions.
The CELL_FACH state may be supported in signaling and/or traffic carriers. Different channels in this mobile device state may be utilized, including PRACH, AICH & S-CCPCH, P/S-SCH, and/or CPICH. PRACH, AICH & S-CCPCH may be required for random access small packet transmissions with FACH. When the CELL_FACH is supported in the traffic flexible bandwidth carrier, P/S-SCH channels might be required depending on the quality of the timing information received from other carriers and/or the timing information derived from the pilots. CPICH can carry pilots that may be required for synchronization and data demodulation. Broadcast information in this state could be sent directly to a mobile device in the traffic CELL_FACH carrier.
The CELL_DCH state may include traffic carriers. Different channels in the mobile device state may be utilized including DPCCH & DPDCH, P-SCH/S-SCH, and/or CPICH. DPCCH & DPDCH carriers may include the control and/or data information. P-SCH/S-SCH might be required for the same reason as in the CELL_FACH state. CPICH might not be required if the pilots in the DPDCH allow adequate data demodulation.
The URA_PCH/CELL_PCH states may be supported in the signaling carriers. Different channels in this mobile device state may be utilized, including P-CCPCH, PICH/S-CCPCH, and/or CPICH. The channels required may be the same as in the idle mobile device state. Note that radio resources may be preserved as the mobile device moves from a traffic carrier supporting CELL_FACH/CELL_DCH to a signaling carrier supporting URA_PCH/CELL_PCH.
Some embodiments may be configured for transitioning from the signaling carrier to the traffic carrier. For example, mobile devices may camp on signaling carriers for an extended period of time. Mobile devices may camp on the signaling carrier and monitor other carriers to facilitate mobility. Mobile devices may monitor either other signaling or traffic carriers. Mobile devices may monitor other signaling flexible bandwidth carriers in case the mobile device loses connection with the current signaling flexible bandwidth carrier. Mobile devices may monitor other traffic flexible bandwidth carriers in case the mobile device may desire to start a mobile originated (MO)/mobile terminated (MT) call. Selection of which traffic flexible bandwidth cells to measure may be dependent on the N supported by carrier, carrier network load, and/or the mobility of the mobile device and not necessarily on the signal quality measured on those carriers as done in existing designs.
The information about potential signaling and traffic carriers may be signaled to the mobile devices through broadcast information on the system information blocks. The network may redirect the mobile device through a redirection message attached to a page instructing the mobile device to move to a particular traffic and/or signaling carrier for reasons such as based on subscription and device capability. Such redirection messages may include the N and timing info of the carriers. In some embodiments, the mobile device could be provisioned with carrier information (e.g., which signaling carrier to camp on).
Some embodiments may be configured for transitioning from the traffic carrier to the signaling carrier. For example, the mobile device may be transmitting data or observing an inactive period on the traffic carrier. A radio connection may be present between the mobile device and the network. In this scenario, some embodiments include a non-monitoring mode. To avoid the performance degradation that comes from the mobile device tuning away to measure other channels during data transmission, a mobile device could be allowed to not monitor other channels. However, before the radio connection is released, the traffic carrier can provide information to the mobile device on which signaling and/or traffic carrier to transition to next. This mode may not be recommended for non-stationary mobile devices.
Some embodiments may include a monitoring mode. For example, mobile devices may monitor other signaling and/or traffic carriers while operating on the traffic carrier by tuning away for a brief period or during periods of data inactivity. The mobile device may obtain information about carriers to monitor through: broadcasted system information while camping on a previous signaling carrier; dedicated information from current traffic carrier; and/or provisioned carrier information in the mobile device. Some embodiments may include periodic monitoring.
Some embodiments may include information sharing between signaling carriers and traffic carriers. To support mobility procedures, the signaling carriers can carry information for one or multiple traffic carriers.
The signaling and traffic carriers can operate on the same or different N values and with multiple traffic carriers, the N configuration could be different. The deployment of the carriers may be such that while on a signaling carrier the mobile device may be able to access at least one of the traffic carriers.
Some embodiments may include grouping that uses virtual location areas and/or routing areas. For example, to enable carrier information to flow between signaling and traffic carriers, the carriers can be grouped into virtual location areas (LA) and/or routing areas (RA) with the same LA/RA ID. For example, signaling and traffic carriers in the same LA/RA may have information about the signaling and traffic carriers in that location area. Some bordering carriers could have information about the signaling and/or traffic carriers in another LA/RA for mobility management reasons.
Some embodiments may include information sharing. Information sharing may occur between signaling carriers. For example, a signaling carrier can carry information about other signaling carriers with or without the same N. A signaling carrier may carry information about other signaling carriers in the same geographical location because of the possibility of mobile device movement within that area. A signaling carrier that is overloaded may offload to other signaling carriers in its geographical area.
Some embodiments may include information sharing between traffic carriers. A traffic carrier may carry information about other traffic carriers in the same geographical location because of the possibility of mobile device movement within that area. A traffic carrier may carry information about other traffic carriers within the same N.
Embodiments utilizing signaling and traffic carrier separation for flexible bandwidth may have numerous differences from known techniques. For example, embodiments may result in increased paging and system information (SI) capacity of the flexible carrier. Some embodiments may include signaling forward link only transmissions in a signaling carrier, which may include paging and broadcast SI only. Some embodiments may include signaling and small packet traffic, which may include forward link and uplink (for registration only) in a signaling carrier. Some embodiments may include signaling carriers for NAS mobility and security but no Radio Resource Control (RRC) maintenance. Some embodiments may include carriers that are dedicated for traffic only (no broadcast traffic may be sent on these carriers).
Some embodiments may include protocol changes with minimal or no impact above the RRC for the signal plane and RLC for user plane. Some embodiments may impact mobile device states, such that mobile devices in all the RRC states may be affected. Some embodiments may include transitions such that RRC resources may be released on the signaling carrier after registration and tracking area updates; mobile devices may be in the IDLE or CELL_PCH/URA_PCH state before transitioning to the traffic carrier. Information regarding data traffic carrier may be conveyed to a mobile device as broadcast message in the SIBs and/or appended to a page in some embodiments.
In some embodiments, recommendations for activation, deactivation, and/or reconfiguration of the traffic carrier may be sent to the mobile device through page messages; in other cases, the mobile device may be responsible for determining the best carrier based on applications, power savings, and/or signal quality. The mobile device may be either be associated with the signal carrier or the traffic carrier but not to both carriers at the same time. A mobile device's disassociation from a signaling carrier may involve the mobile device moving to the traffic carrier based on MT or MO calls. Transitioning from the signaling carrier to another signaling carrier may involve an idle mode reselection procedure. In some embodiments, transitioning from one traffic carrier to another when the mobile device is in the connected mode happens through handovers.
In some embodiments, discontinuous reception (DRX) procedures may be differently configured in the signaling carriers and the traffic carriers. For example, the DRX cycles in the signaling and traffic carriers can be configured independently.
Turning next to
These components of the device 800 may, individually or collectively, be implemented with one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In other embodiments, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
The receiver module 805 may receive information such as packet, data, and/or signaling information regarding what device 800 has received or transmitted. The received information may be utilized by the signaling carrier module 810 and/or traffic carrier module 815 for a variety of purposes.
The signaling carrier module 810 may receive signaling data over a first bandwidth carrier. In some embodiments, the signaling carrier module 810 prepares mobile device registration message to be transmitted to the network. The transition module 812 may facilitate transitioning from receiving signaling data over the first carrier to receiving at least traffic data or network data at the traffic carrier module 815 corresponding to the signaling data over a second carrier may occur. This transitioning may involve obtaining information about the neighboring signaling and traffic carriers that the mobile device is monitoring from the signaling carrier and assessing the viability of those carriers (e.g., in terms of signal power) for future transition. In some embodiments, the signaling data may be received over the first carrier separate from any other traffic data. For example, the signaling data may be received over the first carrier without any other traffic data. The traffic carrier module 815 may be used for supporting the transmission and reception of traffic data when the mobile device is on the traffic carrier. The traffic carrier module 815 may also support receiving data from the network about neighboring cells that the mobile device might desire to evaluate for future transition. The evaluation may be performed in the transition module 812.
In some embodiments, the signaling carrier module 810, the transition module 812, and/or the traffic carrier module 815 may perform a transition to transmitting and/or receiving traffic data over the first carrier and transmitting and/or receiving signaling data over a second carrier. The transition module 812 may be configured to transition from at least transmitting or receiving traffic data over the second carrier to at least transmitting or receiving traffic data over a third carrier. The transition module 812 may be configured to transition from receiving signaling data over the first carrier to receiving signaling data over a fourth carrier. In some embodiments, the received signaling data may correspond to the traffic data. The first carrier may carry information regarding the second carrier.
Some embodiments include scaling a bandwidth of the first carrier utilizing a first scaling factor and scaling a bandwidth of the second carrier utilizing a second scaling factor utilizing the signaling carrier module 810, the transition module 812, and/or the traffic carrier module 815. The first scaling factor and the second scaling factor may be the same or different. At least the first scaling factor or the second scaling factor may be adjusted dynamically. Adjusting at least the first scaling factor or the second scaling factor dynamically may include adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
In some embodiments, at least the first carrier or the second carrier includes a flexible bandwidth carrier. The first carrier and the second carrier may utilize a common scaling factor. In some embodiments, at least the first carrier or the second carrier includes a normal bandwidth carrier.
The signaling carrier module 810, the transition module 812, and/or the traffic carrier module 815 may be configured to receive at least the traffic data or the signaling data in order to boost at least a signaling capacity, a traffic capacity, or a paging capacity. The signaling data may include at least broadcast messages (such as system information), paging, synchronization, or pilot data. The signaling data may include at least cell configuration parameters, pages, or operator specific information that may or not may not be needed for traffic data transmission on the first bandwidth carrier. In some cases, signaling data may be referred to as network data. The traffic data may include at least user data or control information to assist the traffic data. In some embodiments, the first carrier is utilized for an idle mode and the second carrier is utilized for a connected mode.
In some embodiments, users within the first carrier and the second carrier are separated by at least codes, time, or frequency. Users on the first carrier may be separated differently from those on the second carrier. The users within the first carrier may be separated by time and the users on the second carrier are separated by frequency, for example. In some embodiments, the first carrier utilizes FDD and the second carrier utilizes TDD.
In some embodiments, the signaling carrier module 810, the transition module 812, and/or the traffic carrier module 815 are configured such that at least the first carrier or the second carrier separate forward link and reverse link transmissions utilizing at least codes, time, or frequency. The first carrier and/or the second carrier may separate forward link and reverse link transmissions in different ways.
Some embodiments may include receiving and/or transmitting traffic data over a third carrier utilizing the traffic carrier module 815. Signaling data may be received over the first carrier utilizing the signaling carrier module 810. In some cases, the signaling data may correspond to the traffic data. The first carrier may carry information regarding the second carrier and/or the third carrier. The third carrier may be a flexible bandwidth carrier. Some embodiments may include receiving and/or transmitting traffic data over a third carrier and transmitting signaling data over a fourth carrier. The fourth carrier may carry information regarding at least the first carrier and the second carrier; the second carrier may carry information regarding at least the first carrier or the second carrier.
The mobile device 115-e may include antennas 940, a transceiver module 950, memory 980, and a processor module 970, which each may be in communication, directly or indirectly, with each other (e.g., via one or more buses). The transceiver module 950 is configured to communicate bi-directionally, via the antennas 940 and/or one or more wired or wireless links, with one or more networks, as described above. For example, the transceiver module 950 may be configured to communicate bi-directionally with base stations 105 of
The memory 980 may include random access memory (RAM) and read-only memory (ROM). The memory 980 may store computer-readable, computer-executable software code 985 containing instructions that are configured to, when executed, cause the processor module 970 to perform various functions described herein (e.g., call processing, database management, message routing, etc.). Alternatively, the software code 985 may not be directly executable by the processor module 970 but be configured to cause the computer (e.g., when compiled and executed) to perform functions described herein.
The processor module 970 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel® Corporation or AMD®, a microcontroller, an application-specific integrated circuit (ASIC), etc. The processor module 970 may include a speech encoder (not shown) configured to receive audio via a microphone, convert the audio into packets (e.g., 30 ms in length) representative of the received audio, provide the audio packets to the transceiver module 950, and provide indications of whether a user is speaking. Alternatively, an encoder may only provide packets to the transceiver module 950, with the provision or withholding/suppression of the packet itself providing the indication of whether a user is speaking.
According to the architecture of
The components for mobile device 115-e may be configured to implement aspects discussed above with respect to device 800 in
The mobile device 115-e may also include a spectrum identification module 915. The spectrum identification module 915 may be utilized to identify spectrum available for flexible waveforms. In some embodiments, a handover module 925 may be utilized to perform reselection and handover procedures of the mobile device 115-e from one base station to another. For example, the handover module 925 may perform a handover procedure of the mobile device 115-e from signaling carrier to another signaling carrier, a traffic carrier to another traffic carrier and between a signaling and traffic carrier. The base stations supporting these carriers may utilize normal waveforms or flexible waveforms between the mobile device 115-e and base stations. In some embodiments, the transition module 812-a and/or the handover module 925 may be combined in one module. A scaling module 910 may be utilized to scale and/or alter chip rates to generate flexible waveforms.
In some embodiments, the transceiver module 950, in conjunction with antennas 940, along with other possible components of mobile device 115-e, may transmit information regarding flexible waveforms and/or scaling factors about the capability of the mobile device from the device 115-e to base stations and/or the core network. In some embodiments, the transceiver module 950, in conjunction with antennas 940, along with other possible components of mobile device 115-e, may transmit information, such as flexible waveforms and/or scaling factors about the capability of the mobile device, to base stations and/or the core network such that these devices or systems may utilize flexible waveforms in future transmission.
Turning next to
These components of the device 1000 may, individually or collectively, be implemented with one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In other embodiments, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
The receiver module 1005 may receive information such as packet, data, and/or signaling information regarding what device 1000 has received, transmitted, or about a new mobile device attempting to register with the network. The received information may be utilized by the signaling carrier module 1010 and/or traffic carrier module 1015 for a variety of purposes.
The traffic carrier module 1015 may transmit traffic over a first carrier. By utilizing the signaling carrier module 1010, the signaling data may be transmitted over a second carrier separate from any other traffic data. In transmitting the signaling data separate from any other traffic data over the second carrier, the signaling data may be transmitted over the second carrier without any other traffic data.
Some embodiments include having device 1000 configured for transitioning from transmitting and/or receiving traffic data to/from a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second carrier. Transitioning from transmitting the signaling data to the mobile device over the second carrier to transmitting and/or receiving the traffic data to the mobile device over the first carrier may also occur. The base station may perform a transition to transmitting and/or receiving traffic data over the first carrier and to transmitting signaling data over the second carrier.
In some embodiments, the signaling carrier module 1010 and/or the traffic carrier module 1015 may be configured such that at least the first carrier or the second carrier includes a flexible bandwidth carrier. The first carrier and the second carrier may utilize a common scaling factor. In some embodiments, at least the first carrier or the second carrier includes a normal bandwidth carrier.
Transmitting or receiving at least the traffic data or the signaling data utilizing the signaling carrier module 1010 and/or the traffic carrier module 1015 may boost at least a signaling capacity, a traffic capacity, or a paging capacity. The signaling data may include at least broadcast messages (such as system information), paging, synchronization, or pilot data. The traffic data may include at least user data or control information to assist the traffic data. The signal data may include at least cell configuration parameters, pages, or operator specific information that may or may not be needed for traffic data transmission on the first bandwidth carrier; this signaling data may be referred to as network data in some cases. In some embodiments, the second carrier is utilized for an idle mode and the first carrier is utilized for a connected mode.
In some embodiments, users within the first carrier and the second carrier are separated by at least codes, time, or frequency. Users on the first carrier may be separated differently from those on the second carrier. The users within the first carrier may be separated by time and the users on the second carrier are separated by frequency, for example. In some embodiments, the first carrier utilizes FDD and the second carrier utilizes TDD.
In some embodiments, the signaling carrier module 1010 and/or the traffic carrier module 1015 may be configured such that at least the first carrier or the second carrier may separate forward link and reverse link transmissions utilizing at least codes, time, or frequency. The first carrier and/or the second carrier may separate forward link and reverse link transmissions in different ways.
Some embodiments include scaling a bandwidth of the first carrier utilizing a first scaling factor and scaling a bandwidth of the second carrier utilizing a second scaling factor utilizing at least the signaling carrier module 1010 and/or the traffic carrier module 1015. The first scaling factor and the second scaling factor may be the same or different. At least the first scaling factor or the second scaling factor may be adjusted dynamically. Adjusting at least the first scaling factor or the second scaling factor dynamically may include adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Some embodiments may include transmitting and/or receiving traffic data over a third carrier using the traffic carrier module 1015. Signaling data may be transmitted over the second carrier using the signaling carrier module 1010. The signal data may correspond to the traffic data over the third carrier using the signaling carrier module 1010 and/or the traffic carrier module 1015. The second carrier may carry information regarding the first carrier and/or the third carrier. The third carrier may be a flexible bandwidth carrier. Some embodiments may include transmitting and/or receiving traffic data over a third carrier and transmitting signaling data over a fourth carrier. The fourth carrier may carry information regarding the first carrier and/or the third carrier; the second carrier may carry information regarding the first carrier and/or the third carrier.
Base station 105-d may also communicate with other base stations 105, such as base station 105-m and base station 105-n. Each of the base stations 105 may communicate with mobile device 115-f using different wireless communications technologies, such as different Radio Access Technologies. In some cases, base station 105-d may communicate with other base stations such as 105-m and/or 105-n utilizing base station communication module 1115. In some embodiments, base station communication module 1115 may provide an X2 interface within an LTE wireless communication technology to provide communication between some of the base stations 105. In some embodiments, base station 105-d may communicate with other base stations through controller 120-a and/or core network 130-a.
The memory 1170 may include random access memory (RAM) and read-only memory (ROM). The memory 1170 may also store computer-readable, computer-executable software code 1171 containing instructions that are configured to, when executed, cause the processor module 1165 to perform various functions described herein (e.g., call processing, database management, message routing, etc.). Alternatively, the software 1171 may not be directly executable by the processor module 1165 but be configured to cause the computer, e.g., when compiled and executed, to perform functions described herein.
The processor module 1165 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel® Corporation or AMD®, a microcontroller, an application-specific integrated circuit (ASIC), etc. The processor module 1165 may include a speech encoder (not shown) configured to receive audio via a microphone, convert the audio into packets (e.g., 30 ms in length) representative of the received audio, provide the audio packets to the transceiver module 1150, and provide indications of whether a user is speaking. Alternatively, an encoder may only provide packets to the transceiver module 1150, with the provision or withholding/suppression of the packet itself providing the indication of whether a user is speaking.
The transceiver module 1150 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 1145 for transmission, and to demodulate packets received from the antennas 1145. While some examples of the base station 105-d may include a single antenna 1145, the base station 105-d preferably includes multiple antennas 1145 for multiple links which may support carrier aggregation. For example, one or more links may be used to support macro communications with mobile device 115-f.
According to the architecture of
The components for base station 105-d may be configured to implement aspects discussed above with respect to device 800 in
The base station 105-d may also include a spectrum identification module 1115. The spectrum identification module 1115 may be utilized to identify spectrum available for flexible waveforms. In some embodiments, a handover module 1125 may be utilized to perform reselection and handover procedures of the mobile device 115-f from one base station 105 to another. For example, the handover module 1125 may perform a handover procedure of the mobile device 115-f from signaling carrier to another signaling carrier, a traffic carrier to another traffic carrier and between a signaling and traffic carrier. The base stations 105 supporting these carriers may utilize normal waveforms or flexible waveforms between the mobile device 115-f and base stations 105. In some embodiments the transition module 812-b and the handover module 1125 may be combined in one module. A scaling module 1110 may be utilized to scale and/or alter chip rates to generate flexible waveforms.
In some embodiments, the transceiver module 1150 in conjunction with antennas 1145, along with other possible components of base station 105-d, may transmit information regarding flexible waveforms and/or scaling factors from the base station 105-d to the mobile device 115-f, to other base stations 105-m/105-n, or core network 130-a. In some embodiments, the transceiver module 1150 in conjunction with antennas 1145 along with other possible components of base station 105-d may transmit information to the mobile device 115-f, to other base stations 105-m/105-n, or core network 130-a, such as flexible waveforms and/or scaling factors, such that these devices or systems may utilize flexible waveforms.
The transmit processor 1220 may process the data. The transmit processor 1220 may also generate reference symbols, and a cell-specific reference signal. A transmit (TX) MIMO processor 1230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, and/or reference symbols, if applicable, and may provide output symbol streams to the transmit modulators 1232-a through 1232-x. Each transmit modulator 1232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each transmit modulator 1232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink (DL) signal. In one example, DL signals from transmit modulators 1232-a through 1232-x may be transmitted via the antennas 1234-a through 1234-x, respectively. The transmitter processor 1220 may receive information from a processor 1240. The processor 1240 may be coupled with a memory 1242. The processor 1240 may be configured to generate flexible waveforms through altering a chip rate and/or utilizing a scaling factor; this may be done dynamically in some cases. The processor 1240 may also provide for different alignment and/or offsetting procedures. The processor 1240 may also utilize scaling and/or chip rate information to perform measurements on the other subsystems, perform handoffs to the other subsystems, perform reselection, etc. The processor 1240 may invert the effects of time stretching associated with the use of flexible bandwidth through parameter scaling. In some embodiments, the processor 1240 may be configured to separate the signaling and the data traffic into different carriers, which may be flexible bandwidth carriers. In some cases, this may be utilized so that assigned resources can be customized to the traffic pattern. In some embodiments, the processor 1240 may be implemented as part of a general processor, the transmitter processor 1220, and/or the receiver processor 1238.
At the mobile device 115-g, the mobile device antennas 1252-a through 1252-n may receive the DL signals from the base station 105-e and may provide the received signals to the demodulators 1254-a through 1254-n, respectively. Each demodulator 1254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 1254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 1256 may obtain received symbols from all the demodulators 1254-a through 1254-n, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 1258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the mobile device 115-g to a data output, and provide decoded control information to a processor 1280, or memory 1282.
On the uplink (UL), at the mobile device 115-g, a transmit processor 1264 may receive and process data from a data source. The transmit processor 1264 may also generate reference symbols for a reference signal. The symbols from the transmit processor 1264 may be precoded by a transmit MIMO processor 1266 if applicable, further processed by the demodulators 1254-a through 1254-n (e.g., for SC-FDMA, etc.), and be transmitted to the base station 105-e in accordance with the transmission parameters received from the base station 105-e. The transmitter processor 1264 may also be configured to generate flexible waveforms through altering a chip rate and/or utilizing a scaling factor; this may be done dynamically in some cases. The transmit processor 1264 may receive information from processor 1280. The processor 1280 may provide for different alignment and/or offsetting procedures. The processor 1280 may also utilize scaling and/or chip rate information to perform measurements on the other subsystems, perform handoffs to the other subsystems, perform reselection, etc. The processor 1280 may invert the effects of time stretching associated with the use of flexible bandwidth through parameter scaling. At the base station 105-e, the UL signals from the mobile device 115-g may be received by the antennas 1234, processed by the demodulators 1232, detected by a MIMO detector 1236 if applicable, and further processed by a receive processor. The receive processor 1238 may provide decoded data to a data output and to the processor 1280. In some embodiments, the processor 1280 may be configured to separate the signaling and the data traffic into different carriers, which may be flexible bandwidth carriers. In some cases, this may be utilized so that assigned resources can be customized to the traffic pattern. In some embodiments, the processor 1280 may be implemented as part of a general processor, the transmitter processor 1264, and/or the receiver processor 1258.
Turning to
At block 1305, signaling data may be received over a first carrier. At block 1310, transitioning from receiving signaling data over the first carrier to transmitting and/or receiving traffic data over a second carrier may occur. In some embodiments, the traffic data corresponds to the signaling data. In some embodiments, the signaling data may be received over the first carrier separate from any other traffic data. For example, the signaling data may be received over the first carrier without any other traffic data. In some embodiments, the signaling data such as mobile device registration can be transmitted over the first carrier.
In some embodiments, a transition is performed to transmitting and/or receiving traffic data over the first carrier and transmitting signaling data over the second carrier. In some embodiments, a transition is performed to transmitting and receiving traffic data over the first carrier and transmitting and/or receiving signaling data over the second bandwidth carrier. Some embodiments further include transitioning from at least transmitting or receiving traffic data over the second carrier to at least transmitting or receiving traffic data over a third carrier. Some embodiments further include transitioning from receiving signaling data over the first carrier to receiving signaling data over a fourth carrier. Some embodiments further include transmitting signaling data over the first carrier. In some embodiments, the first carrier utilizes a first bandwidth and the second carrier utilizes a second bandwidth. In some embodiments, the first carrier carries information regarding the second carrier.
Some embodiments include scaling the first bandwidth utilizing a first scaling factor and scaling the second bandwidth utilizing a second scaling factor. The first scaling factor and the second scaling factor may be the same or different. At least the first scaling factor or the second scaling factor, or the first bandwidth and/or the second bandwidth, may be adjusted dynamically. Adjusting at least the first scaling factor or the second scaling factor, or at least the first bandwidth or the second bandwidth, dynamically may include adjusting at least the first scaling factor or the second scaling factor, or at least the first bandwidth or the second bandwidth, based upon expected traffic demand. Some embodiments include scaling at least an uplink or a downlink for at least the first bandwidth or the second bandwidth utilizing different scaling factors.
In some embodiments, at least the first carrier or the second carrier includes a flexible bandwidth carrier. The first carrier and the second carrier may utilize a common scaling factor. In some embodiments, at least the first carrier or the second carrier includes a normal bandwidth carrier.
In some embodiments, transmitting and/or receiving at least the traffic data or the signaling data may boost at least a signaling capacity, a traffic capacity, or a paging capacity. The signaling data may include at least broadcast messages (such as system information), paging, synchronization, or pilot data. The traffic data may include at least user data or control information to assist the traffic data. The signaling data may also include at least cell configuration parameters, pages, or operator specific information that may or not may not be needed for traffic data transmission on the first bandwidth carrier; in some cases, this signaling data may be referred to as network data. In some embodiments, the first carrier is utilized for an idle mode and the second carrier is utilized for a connected mode.
In some embodiments, users within the first carrier and the second carrier are separated by at least codes, time, or frequency. Users on the first carrier may be separated differently from those on the second carrier. The users within the first carrier may be separated by time and the users on the second carrier are separated by frequency, for example. In some embodiments, the first carrier utilizes FDD and the second carrier utilizes TDD.
In some embodiments, at least the first carrier or the second carrier separates forward link and reverse link transmissions utilizing at least codes, time, or frequency. The first carrier and the second carrier may separate forward link and reverse link transmissions in different ways.
Some embodiments include receiving traffic data over a third carrier. Signaling data may be received over the first carrier. The first carrier may carry information regarding at least the second carrier or third carrier corresponding to the traffic data over the third carrier. The third carrier may be a flexible bandwidth carrier. Some embodiments include receiving traffic data over a third carrier and transmitting signaling data over a fourth carrier. The signaling data over the fourth carrier may correspond to the traffic data over the third carrier. The fourth carrier may carry information regarding the second and/or third carrier.
Turning to
At block 1305-a, signaling data may be received at a mobile device from a base station over a first flexible bandwidth carrier. At block 1310-a, transitioning from receiving signaling data over the first flexible bandwidth carrier to transmitting and receiving traffic data may occur at the mobile device. In some cases, the traffic data corresponds to the signaling data over a second flexible bandwidth carrier. At block 1315, at least the first flexible bandwidth carrier or the second flexible bandwidth carrier may be dynamically adjusted utilizing one or more scaling factors based upon expected traffic demand.
Turning to
At block 1405, traffic data may be transmitted and/or received over a first carrier. At block 1410, signaling data may be transmitted over a second carrier separate from any other traffic data. In some cases, the signaling data corresponds to the traffic data. In transmitting the signaling data separate from any other traffic data over the second carrier, the signaling data may be transmitted over the second carrier without any other traffic data.
Some embodiments include transitioning from transmitting and receiving the traffic data to a mobile device over the first carrier to transmitting the signaling data to the mobile device over the second bandwidth carrier. Transitioning from transmitting the signaling data to the mobile device over the second carrier to transmitting and receiving the traffic data to the mobile device over the first carrier may also occur. A transition may be performed to transmitting and receiving the traffic data over the first carrier and transmitting signaling over the second carrier. The second carrier may carry information regarding at least the first carrier. Signaling data may be received over the second carrier in some cases.
In some embodiments, at least the first carrier or the second carrier includes a flexible bandwidth carrier. The first carrier and the second carrier may utilize a common scaling factor. In some embodiments, at least the first carrier or the second carrier includes a normal bandwidth carrier.
Transmitting and/or receiving at least the traffic data, the network data, or the signaling data may boost at least a signaling capacity, a traffic capacity, or a paging capacity. The signaling data may include at least broadcast messages (such as system information), paging, synchronization, or pilot data. The traffic data may include at least user data or control information to assist the traffic data. The signal data may also include at least cell configuration parameters, pages, or operator-specific information that may or not may not be needed for traffic data transmission on the first carrier; this data may be referred to as network data in some cases. In some embodiments, the second carrier is utilized for an idle mode and the first carrier is utilized for a connected mode.
In some embodiments, users within the first carrier and the second carrier are separated by at least codes, time, or frequency. Users on the first carrier may be separated differently from those on the second carrier. The users within the first carrier may be separated by time and the users on the second carrier are separated by frequency, for example. In some embodiments, the first carrier utilizes FDD and the second carrier utilizes TDD.
In some embodiments, at least the first carrier or the second carrier separates forward link and reverse link transmissions utilizing at least codes, time, or frequency. The first carrier and the second carrier may separate forward link and reverse link transmissions in different ways.
Some embodiments include scaling a bandwidth of the first bandwidth carrier utilizing a first scaling factor and scaling a bandwidth of the second bandwidth carrier utilizing a second scaling factor. The first scaling factor and the second scaling factor may be the same or different. At least the first scaling factor or the second scaling factor may be adjusted dynamically. Adjusting at least the first scaling factor or the second scaling factor dynamically may include adjusting at least the first scaling factor or the second scaling factor based upon expected traffic demand.
Some embodiments may include transmitting and receiving traffic data over a third carrier. Signaling data may be transmitted over the second carrier. The signaling data may correspond to the traffic data the third carrier. The second carrier may carry information regarding at least the first carrier or the third carrier. The third carrier may be a flexible bandwidth carrier. Some embodiments may include transmitting and receiving traffic data over a third carrier and transmitting signaling data over a fourth carrier. The fourth carrier may carry information regarding at least the first carrier or the third carrier and the second carrier may carry information regarding at least the first carrier or the third carrier. The signaling data over the fourth carrier may correspond to the traffic data the third carrier.
Turning to
At block 1402, a transition to transmitting or receiving at least traffic data over a first flexible bandwidth carrier or signaling data over a second flexible bandwidth carrier may be performed. The signaling data may correspond to the traffic data in some cases. At block 1405-a, the traffic data may be transmitted over a first flexible bandwidth carrier from a base station to a mobile device. At block 1410-a, signaling data may be transmitted over the second flexible bandwidth carrier separate from any other traffic from the base station to the mobile device.
The detailed description set forth above in connection with the appended drawings describes exemplary embodiments and does not represent the only embodiments that may be implemented or that are within the scope of the claims. The term “exemplary” used throughout this description means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other embodiments.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, “or” as used in a list of items prefaced by “at least one of” indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).
Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
The previous description of the disclosure is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Throughout this disclosure the term “example” or “exemplary” indicates an example or instance and does not imply or require any preference for the noted example. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Das, Soumya, Song, Bongyong, Park, Edwin C., Soliman, Samir Salib, Awoniyi, Olufunmilola O.
Patent | Priority | Assignee | Title |
10111125, | Nov 07 2011 | Qualcomm Incorporated | Bandwidth information determination for flexible bandwidth carriers |
10123152, | Jul 20 2016 | AT&T Intellectual Property I, L.P.; AT&T MOBILITY II LLC | Smart load-based deployment and tuning of narrowband carriers |
10667162, | Nov 07 2011 | Qualcomm Incorporated | Bandwidth information determination for flexible bandwidth carriers |
10743313, | Jul 20 2016 | AT&T Intellectual Property I, L.P.; AT&T MOBILITY II LLC | Smart load-based deployment and tuning of narrowband carriers |
11224015, | Oct 31 2014 | Qualcomm Incorporated | Dynamic bandwidth switching for reducing power consumption in wireless communication devices |
11711762, | Oct 31 2014 | Qualcomm Incorporated | Dynamic bandwidth switching for reducing power consumption in wireless communication devices |
Patent | Priority | Assignee | Title |
5117443, | Nov 13 1989 | Lucid, Inc. (formerly Portable Computer) | Method and apparatus for operating at fractional speeds in synchronous systems |
5640385, | Jan 04 1994 | Google Technology Holdings LLC | Method and apparatus for simultaneous wideband and narrowband wireless communication |
5949767, | Apr 11 1995 | NEC Corporation | Reception unit for receiving a frequency division multi-accessed signal based on plural spread signals and method for receiving the same |
6041222, | Sep 08 1997 | Ericsson Inc.; Ericsson Inc | Systems and methods for sharing reference frequency signals within a wireless mobile terminal between a wireless transceiver and a global positioning system receiver |
6236647, | Feb 24 1998 | Intel Corporation | Dynamic frame size adjustment and selective reject on a multi-link channel to improve effective throughput and bit error rate |
6424826, | Sep 08 1997 | Ericsson, Inc. | Systems and methods for sharing reference frequency signals within a wireless mobile terminal between a wireless transceiver and a global positioning system receiver |
6535723, | Mar 15 1999 | WSOU Investments, LLC | Method of power control for a wireless communication system having multiple information rates |
6539050, | Jun 26 1997 | Hughes Electronics Corporation | Method for transmitting wideband signals via a communication system adapted for narrow-band signal transmission |
6693887, | Feb 15 2001 | QUARTERHILL INC ; WI-LAN INC | Method for allocating fractional bandwidth in a fixed-frame communication system |
6694147, | Sep 15 2000 | Qualcomm Incorporated | Methods and apparatus for transmitting information between a basestation and multiple mobile stations |
6829227, | Oct 27 2000 | Lucent Technologies Inc. | Dual polling media access control protocol for packet data in fixed wireless communication systems |
6845238, | Sep 15 1999 | Telefonaktiebolaget LM Ericsson | Inter-frequency measurement and handover for wireless communications |
6944460, | Jun 07 2001 | TELEFONAKTIEBOLAGET LM ERICSSON PUBL | System and method for link adaptation in communication systems |
7010300, | Jun 15 2000 | Sprint Spectrum LLC | Method and system for intersystem wireless communications session hand-off |
7069035, | Mar 30 2001 | Qualcomm, Incorporated; Qualcomm Incorporated | Method and apparatus for power control in a communication system |
7123710, | Apr 09 2002 | TEKELEC GLOBAL, INC | Method and systems for intelligent signaling router-based surveillance |
7123910, | May 10 2001 | Apple | System and method for message redirection between mobile telecommunication networks with different radio access technologies |
7145876, | May 31 2002 | Motorola, Inc.; Motorola, Inc | Method and apparatus incorporating adaptive datalink framing for message communication |
7193982, | Jan 11 2002 | AT&T MOBILITY II, LLC | System and method for providing flexible data rate transmission in a telecommunication system |
7263365, | Apr 14 2003 | Google Technology Holdings LLC | Reception method and apparatus |
7321780, | Apr 30 2003 | Google Technology Holdings LLC | Enhanced uplink rate selection by a communication device during soft handoff |
7324553, | Sep 30 2003 | CA, INC | Dynamic bandwidth management responsive to access link state in redundant network topologies |
7394792, | Oct 08 2002 | Urbain A., von der Embse | Multi-scale CDMA |
7535900, | Jan 21 2003 | IP GEM GROUP, LLC | Multiple transmission bandwidth streams with defferentiated quality of service |
7558310, | Jan 09 2001 | Urbain Alfred, von der Embse | Multi-scale code division frequency/wavelet multiple access |
7602707, | Feb 27 2003 | Microsoft Technology Licensing, LLC | Quality of service differentiation in wireless networks |
7796632, | Sep 29 2006 | RUCKUS IP HOLDINGS LLC | Transmission channel bandwidth selection for communications between multi-bandwidth nodes |
7839900, | Sep 29 2006 | Rockwell Collins, Inc | Method and architecture for TTNT symbol rate scaling modes |
7865359, | Nov 06 2006 | Futurewei Technologies, Inc.; FUTUREWEI TECHNOLOGIES, INC | Waveform modulated wireless rural area network (WRAN) systems and modulation and multiple access techniques for wireless communication systems |
7898947, | Aug 23 2006 | AMDOCS DEVELOPMENT LIMITED; Amdocs Systems Limited | Capacity management for data networks |
7953167, | Oct 29 2004 | FUJITSU CONNECTED TECHNOLOGIES LIMITED | Communications apparatus and communications system using multicarrier transmission mode |
7969858, | Oct 14 2004 | Qualcomm Incorporated | Wireless terminal methods and apparatus for use in wireless communications systems supporting different size frequency bands |
8000706, | Jan 07 2008 | LG Electronics Inc | Method of reselecting a cell based on priorities |
8045972, | Sep 03 2005 | Mayflower Communications Company, Inc. | Multimode wireless radio access network with distributed processing |
8054893, | Nov 29 2006 | Fujitsu Limited | Optimum radio communication method with radio frame variable control and radio communication system using the same |
8064398, | Apr 08 2005 | Qualcomm Incorporated | Seamless interfrequency handoff in a high data rate wireless system |
8085713, | Mar 27 2007 | Industrial Technology Research Institute | Resource allocation method of subscriber of service negotiation system |
8085731, | Jun 18 2008 | Malikie Innovations Limited | Mechanism for 3rd generation partnership project multiple inter-network quality of service continuity |
8150344, | Feb 19 2008 | Sprint Spectrum LLC | Method and system of planning a wireless telecommunication network |
8169953, | May 17 2005 | Qualcomm Incorporated | Method and apparatus for wireless multi-carrier communications |
8325670, | Mar 31 2006 | Nextel Communications, Inc. | Method, apparatus and computer-readable medium for asymmetric frequency division duplexing operation |
8514883, | Apr 24 2009 | InterDigital Patent Holdings, Inc | Method and apparatus for sending hybrid automatic repeat request feedback for component carrier aggregation |
8547840, | Feb 01 2011 | GOOGLE LLC | Bandwidth allocation of bursty signals |
8873505, | Mar 12 2009 | InterDigital Patent Holdings, Inc | Method and apparatus for performing component carrier-specific reconfiguration |
20010012271, | |||
20020065089, | |||
20020110101, | |||
20020158801, | |||
20020159501, | |||
20030081538, | |||
20030203721, | |||
20030224730, | |||
20040128110, | |||
20050065784, | |||
20050208973, | |||
20060171424, | |||
20060246930, | |||
20060291429, | |||
20070049307, | |||
20070081604, | |||
20070217440, | |||
20070268959, | |||
20080026752, | |||
20080095108, | |||
20080144612, | |||
20080165892, | |||
20080227453, | |||
20080253320, | |||
20080298442, | |||
20090016320, | |||
20090042532, | |||
20090074039, | |||
20090094650, | |||
20090116389, | |||
20090135713, | |||
20090141689, | |||
20090161732, | |||
20090252134, | |||
20090258671, | |||
20090274096, | |||
20090323608, | |||
20100061496, | |||
20100124940, | |||
20100157910, | |||
20100159859, | |||
20100167741, | |||
20100195618, | |||
20100195619, | |||
20100195668, | |||
20100214031, | |||
20100222060, | |||
20100234040, | |||
20100240356, | |||
20100246480, | |||
20100255849, | |||
20100260105, | |||
20100279691, | |||
20100322109, | |||
20100323622, | |||
20110013530, | |||
20110013550, | |||
20110013578, | |||
20110019556, | |||
20110021216, | |||
20110064162, | |||
20110080893, | |||
20110085497, | |||
20110086657, | |||
20110103243, | |||
20110103330, | |||
20110128922, | |||
20110134831, | |||
20110149853, | |||
20110151913, | |||
20110164707, | |||
20110205976, | |||
20110217980, | |||
20110244870, | |||
20110267978, | |||
20110268045, | |||
20110269453, | |||
20110276701, | |||
20110310835, | |||
20120002643, | |||
20120015656, | |||
20120044844, | |||
20120063421, | |||
20120102162, | |||
20120113982, | |||
20120120789, | |||
20120140743, | |||
20120142367, | |||
20120149377, | |||
20120157101, | |||
20120163249, | |||
20120165019, | |||
20120195209, | |||
20120202501, | |||
20130017805, | |||
20130044613, | |||
20130083778, | |||
20130084870, | |||
20130114415, | |||
20130114433, | |||
20130114436, | |||
20130114566, | |||
20130114571, | |||
20130115967, | |||
20130115991, | |||
20130115994, | |||
20130121265, | |||
20130122921, | |||
20130148520, | |||
20130148527, | |||
20130148576, | |||
20130148579, | |||
20130148627, | |||
20130148628, | |||
20130148629, | |||
20130150045, | |||
20130176952, | |||
20130182655, | |||
20130329670, | |||
20140044431, | |||
20140206350, | |||
EP1213868, | |||
EP1993237, | |||
EP2317816, | |||
EP2385653, | |||
EP2493257, | |||
GB2386506, | |||
GB2421880, | |||
JP10511818, | |||
JP2002330467, | |||
JP2002344965, | |||
JP2003051849, | |||
JP2003264524, | |||
JP2004173019, | |||
JP2004350259, | |||
JP2006094005, | |||
JP2006303739, | |||
JP2006515119, | |||
JP2009060601, | |||
JP2009218638, | |||
JP2009545227, | |||
JP2010011397, | |||
JP2011097443, | |||
JP2011176687, | |||
JP2011521507, | |||
JP2012525723, | |||
JP2013509055, | |||
JP2013524607, | |||
JP8288884, | |||
KR20070049091, | |||
KR20070058683, | |||
KR20080034857, | |||
KR20080106092, | |||
KR20090015857, | |||
KR20110067655, | |||
WO120942, | |||
WO3034645, | |||
WO3092212, | |||
WO2005112566, | |||
WO2006046307, | |||
WO2006110875, | |||
WO2006125149, | |||
WO2007024748, | |||
WO2007148911, | |||
WO2008015512, | |||
WO2009124377, | |||
WO2010105232, | |||
WO2010126418, | |||
WO2010141607, | |||
WO2010150767, | |||
WO2011047619, | |||
WO2011053974, | |||
WO2011121175, | |||
WO2013070710, | |||
WO2013070738, | |||
WO2013070751, | |||
WO9610320, | |||
WO9900911, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 21 2012 | Qualcomm Incorporated | (assignment on the face of the patent) | / | |||
Jun 07 2012 | AWONIYI, OLUFUNMILOLA O | Qualcomm Incorporated | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028377 | /0765 | |
Jun 07 2012 | SOLIMAN, SAMIR SALIB | Qualcomm Incorporated | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028377 | /0765 | |
Jun 07 2012 | SONG, BONGYONG | Qualcomm Incorporated | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028377 | /0765 | |
Jun 07 2012 | DAS, SOUMYA | Qualcomm Incorporated | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028377 | /0765 | |
Jun 08 2012 | PARK, EDWIN C | Qualcomm Incorporated | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028377 | /0765 |
Date | Maintenance Fee Events |
May 14 2019 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
May 10 2023 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Dec 22 2018 | 4 years fee payment window open |
Jun 22 2019 | 6 months grace period start (w surcharge) |
Dec 22 2019 | patent expiry (for year 4) |
Dec 22 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Dec 22 2022 | 8 years fee payment window open |
Jun 22 2023 | 6 months grace period start (w surcharge) |
Dec 22 2023 | patent expiry (for year 8) |
Dec 22 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Dec 22 2026 | 12 years fee payment window open |
Jun 22 2027 | 6 months grace period start (w surcharge) |
Dec 22 2027 | patent expiry (for year 12) |
Dec 22 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |