Carrier aggregation bandwidth class with overlapping bandwidth ranges

Abstract

The present disclosure relates to carrier aggregation bandwidth classes with overlapping bandwidth ranges. A backoff group is assigned aggregated channel bandwidth classes that overlap in frequency. The backoff group can define an increase or maximum bandwidth of aggregated component carriers assigned by a network. By enabling the aggregated channel bandwidth classes of the backoff group to overlap in frequency, for an available aggregated channel bandwidth, a first aggregated channel bandwidth class can be implemented using a first number of component carriers, and a second aggregated channel bandwidth class can be implemented using a second number of component carriers that is different than the first number of component carriers. The different number of component carriers can enable greater flexibility to more fully utilize the available aggregated channel bandwidth for communication. The network can then assign one of these aggregated channel bandwidth classes to a user equipment that more fully utilizes the available aggregated channel bandwidth for communication.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 169,638, filed April 1, 2021, entitled “CARRIER AGGREGATION BANDWIDTH CLASSES WITH OVERLAPPING BANDWIDTH RANGES,” the contents of which are incorporated by reference in their entirety for all purposes. BACKGROUND

[0003] The present disclosure relates generally to wireless communications, and more particularly to efficiently using allocated bandwidth for communication.

[0004] In cellular communications, user equipment (e.g., cellular phones) can communicate (e.g., with a base station) under guidelines or rules that can be set and enforced by the Third Generation Partnership Project (3GPP). However, in communicating, following such guidelines or rules can result in inefficiencies. SUMMARY

[0005] A summary of certain implementations disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain implementations and that

[0006] The disclosed implementations allocate aggregated channel bandwidths for a fallback group that overlap in frequency. In this way, user equipment can more fully utilize allocated aggregated channel bandwidths for communication.

[0007] In one implementation, a method includes receiving, at a base station, a request for a carrier aggregation bandwidth from user equipment based on a fallback group. The method also includes determining, via processing circuitry, available aggregated channel bandwidths and sending, from the base station to the user equipment, an indication of an aggregated channel bandwidth class based on the available aggregated channel bandwidths for the fallback group. The aggregated channel bandwidth class overlaps with another aggregated channel bandwidth class for the fallback group.

[0008] In another embodiment, an electronic device includes a receiver that receives signals from a user equipment and a transmitter that transmits signals to the user equipment. The electronic device also includes at least one processor that receives a request for a carrier aggregation bandwidth from a user equipment based on a fallback group and determines an available aggregated channel bandwidth. The at least one processor also transmits an indication of an aggregated channel bandwidth category via the at least one processor to the user equipment based on the available aggregated channel bandwidth of the fallback group. The aggregated channel bandwidth category is associated with a number of component carriers and enables the user equipment to utilize a full range of the available aggregated channel bandwidth using the number of component carriers.

[0009] In yet another embodiment, a user equipment includes a transmitter that is communicatively coupled to a base station and a receiver that is communicatively coupled to the base station. The user equipment also includes at least one processor that requests a carrier aggregation bandwidth from the base station via the transmitter based on a supported fallback group. The at least one processor also receives an indication of an aggregated channel bandwidth category that implements the supported fallback group via the receiver. The aggregated channel bandwidth category overlaps another aggregated channel bandwidth category of the supported fallback group. The at least one processor further transmits signals to the base station via the transmitter or receives signals from the base station via the receiver through the aggregated channel bandwidth.

[0010] Various improvements to the above features can exist with respect to various aspects of the present disclosure. Other features can also be added to these various aspects. These improvements and additional features can exist individually or in any combination. For example, various features discussed below in relation to one or more illustrated embodiments can be incorporated into any of the above aspects of the present disclosure, individually or in any combination. The brief summary presented above is intended only to familiarize the reader with certain aspects and contexts of implementations of the disclosure, and does not limit the claimed subject matter. BRIEF DESCRIPTION OF DRAWINGS

[0011] Various aspects of the disclosure can be better understood when read in conjunction with the following detailed description and with reference to the following drawings, in which like numerals represent similar parts.

[0012] Figure 1 is a block diagram of a user equipment in accordance with an embodiment of the disclosure;

[0013] Figure 2 is a block diagram of a user equipment in accordance with an embodiment of the disclosure; Figure 1 is a functional diagram of a user equipment of

[0014] Figure 3 is a schematic diagram of a communication system including a user equipment in communication with a communication network via a base station in accordance with an embodiment of the disclosure;Figure 1 a user equipment;

[0015] Figure 4 is a carrier aggregation bandwidth class chart for New Radio (NR) Frequency Range 2 (FRD) as set and implemented by the Third Generation Partnership Project (3GPP);

[0016] Figure 5 is a carrier aggregation bandwidth class chart for a fallback group 1 in NR FR2 that enables efficient carrier aggregation bandwidth usage according to embodiments of the present disclosure;

[0017] Figure 6 is a carrier aggregation bandwidth class chart for a fallback group 2 in NR FR2 that enables efficient carrier aggregation bandwidth usage according to embodiments of the present disclosure;

[0018] Figure 7 is a table showing full aggregation channel bandwidth coverage for a fallback group 1 in NR FR2 with up to 1600 megahertz (MHz) and 50 MHz resolution according to embodiments of the present disclosure;

[0019] Figure 8 is a table showing full aggregation channel bandwidth coverage for a fallback group 2 in NR FR2 with up to 1600 megahertz (MHz) and 50 MHz resolution according to embodiments of the present disclosure;

[0020] Figure 9 is a method for a user equipment to more fully utilize an aggregation channel bandwidth according to embodiments of the present disclosure; Figure 1 is a flowchart of a method for a user equipment to more fully utilize an aggregation channel bandwidth according to embodiments of the present disclosure; and

[0021] Figure 10 is a method for a communication network and / or base station to provide an aggregation channel bandwidth that can be more fully used for communication according to embodiments of the present disclosure. Figure 3 is a flowchart of a method for a communication network and / or base station to provide an aggregation channel bandwidth that can be more fully used for communication according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0022] One or more specific embodiments will be described below. To provide a context for these embodiments, Figure 1 shows, in simplified form, a diagram of a wireless communication system 100 in accordance with some embodiments. As shown in Figure 1, the wireless communication system 100 includes a number of base stations 110 and other network entities. A base station is generally a fixed station that communicates with the

[0023] When introducing elements of various embodiments of the present disclosure, the articles "a," "an," and "the" are intended to mean that there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there can be additional elements other than the listed elements. Additionally, it should be understood that references to "one embodiment" or "an embodiment" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate those features. Furthermore, various features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. The usage of terms such as "about," "approximately," "substantially," and / or "essentially," when used in reference to a quantity, is understood to mean that the quantity is within a reasonable range of error for the quantity measured or used under the circumstances, such as within 0.1% of the value, within 1% of the value, within 5% of the value, within 10% of the value, within 25% of the value, etc.

[0024] In cellular communications, a user equipment (e.g., a mobile communication device, a cellular phone) can communicate (e.g., with a base station) using a single frequency block (e.g., a component carrier). For some standards, such as a 4th Generation (4G) or Long Term Evolution (LTE) standard, or a 5th Generation (5G) or New Radio (NR) standard, a user equipment can communicate using multiple frequency blocks (e.g., referred to as carrier aggregation). In cases where the multiple frequency blocks are contiguous, guidelines or rules can be set and enforced by the 3rd Generation Partnership Project (3GPP) related to the allocated (e.g., total) bandwidth for communicating using the multiple frequency blocks, the individual bandwidth of each frequency block, the number of contiguous multiple frequency blocks that can be used to communicate with the allocated bandwidth, etc. However, following such guidelines or rules when communicating using multiple frequency blocks through an allocated bandwidth can result in inefficiencies. Specifically, according to 3GPP specifications, aggregated channels in a carrier aggregation combination cannot overlap.

[0025] The disclosed embodiments allocate aggregated channel bandwidth classes for a fallback group that overlap in frequency. The fallback group can define an increase or maximum bandwidth of aggregated component carriers allocated by a network. By enabling the aggregated channel bandwidth classes of the fallback group to overlap in frequency, for an available aggregated channel bandwidth, a first aggregated channel bandwidth class can be implemented using a first number of component carriers, and a second aggregated channel bandwidth class can be implemented using a second number of component carriers that is different than the first number of component carriers. The different numbers of component carriers can enable greater flexibility to more fully utilize the available aggregated channel bandwidth for communication (e.g., enabling utilization of a lowest frequency of the available aggregated channel bandwidth to a highest frequency of the available aggregated channel bandwidth). The network can then allocate one of these aggregated channel bandwidth classes to a user equipment that more fully utilizes the available aggregated channel bandwidth for communication. ​

[0026] Figure 1 This is a block diagram of user equipment 10 (e.g., an electronic device, a wireless communication device, a mobile communication device) according to an embodiment of this disclosure. Among other things, user equipment 10 may include one or more processors 12 (collectively referred to herein as a single processor, which may be implemented in any suitable form of processing circuitry), memory 14, non-volatile storage device 16, display 18, input structure 22, input / output (I / O) interface 24, network interface 26, and power supply 29. Figure 1 The various functional blocks shown may include hardware elements (including circuitry), software elements (including machine-executable instructions), or combinations of hardware and software elements (which may be referred to as logic). Processor 12, memory 14, non-volatile storage device 16, display 18, input structure 22, input / output (I / O) interface 24, network interface 26, and / or power supply 29 may each be directly or indirectly communicatively coupled to each other (e.g., via another component, communication bus, network) to transmit and / or receive data between them. It should be noted that... Figure 1 This is merely an example of a specific implementation and is intended to illustrate the types of components that may exist in user equipment 10.

[0027] For example, user equipment 10 may include any suitable computing device, including desktop or laptop computers (e.g., those available from Apple Inc. in Cupertino, California). Pro mini or Mac (in the form of) portable or handheld electronic devices such as wireless electronic devices or smartphones (e.g., those available from Apple Inc. in Cupertino, California). (in the form of a model), wearable electronic devices (e.g., those available from Apple Inc. in Cupertino, California). (in the form of) or other similar equipment. It should be noted that Figure 1 The processor 12 and other related items may be embodied, in whole or in part, as software, hardware, or both. Furthermore, the processor 12 and Figure 1Other related items may be a single, independent processing module, or may be fully or partially integrated into any of the other elements within user equipment 10. Processor 12 may be implemented using a combination of a general-purpose microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), programmable logic device (PLD), controller, state machine, gated logic, discrete hardware components, dedicated hardware finite state machine, or any other suitable entity capable of performing computational or other manipulations of information. Processor 12 may include one or more application processors, one or more baseband processors, or both, and performs the various functions described herein.

[0028] exist Figure 1 In user equipment 10, processor 12 may be operatively coupled to memory 14 and non-volatile storage device 16 to execute various algorithms. Such programs or instructions executed by processor 12 may be stored in any suitable article of writing comprising one or more tangible computer-readable media. The tangible computer-readable media may include memory 14 and / or non-volatile storage device 16, individually or jointly, to store instructions or routines. Memory 14 and non-volatile storage device 16 may include any suitable article of writing for storing data and executable instructions, such as random access memory, read-only memory, rewritable flash memory, hard disk drive, and optical disk. Furthermore, programs (e.g., operating systems) encoded on such computer program products may also include instructions executable by processor 12 to enable user equipment 10 to provide various functions.

[0029] In some embodiments, display 18 may facilitate a user's viewing of images generated on user equipment 10. In some embodiments, display 18 may include a touchscreen that facilitates user interaction with the user interface of user equipment 10. Furthermore, it should be understood that in some embodiments, display 18 may include one or more liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, or some combination of these and / or other display technologies.

[0030] The input structure 22 of user equipment 10 enables a user to interact with user equipment 10 (e.g., pressing a button to increase or decrease the volume level). Like network interface 26, I / O interface 24 enables user equipment 10 to interact with a variety of other electronic devices. In some embodiments, I / O interface 24 may include I / O ports for hardwired connections for charging and / or content manipulation using standard connectors and protocols such as the Lightning connector supplied by Apple Inc. of Cupertino, California, Universal Serial Bus (USB), or other similar connectors and protocols. Network interface 26 may include, for example, one or more interfaces for personal area networks (PANs) such as Ultra Wideband (UWB) or... Networks, local area networks (LANs), or wireless local area networks (WLANs) such as those employing a protocol from the IEEE 802.11x family of protocols (e.g., Networks and / or wide area networks (WANs) such as any standards related to the 3rd Generation Partnership Project (3GPP), including, for example, 3rd generation (3G) cellular networks, Universal Mobile Telecommunications System (UMTS), 4th generation (4G) cellular networks, Long Term Evolution (LTE) Cellular networks, Long Term Evolution License Assisted Access (LTE-LAA) cellular networks, 5G cellular networks and / or New Radio (NR) cellular networks, satellite networks, non-terrestrial networks, etc. Specifically, network interface 26 may include, for example, one or more interfaces for using the version 15 cellular communication standard of the 5G specification, which includes millimeter-wave (mmWave) frequency ranges (e.g., 24.25–300 GHz), and / or any other version of the cellular communication standard (e.g., version 16, version 17, any future version) that defines and / or implements frequency ranges for wireless communication. The network interface 26 of user equipment 10 may allow communication via the aforementioned networks (e.g., 5G, Wi-Fi, LTE-LAA, etc.).

[0031] Network interface 26 may also include one or more interfaces for, for example, a broadband fixed wireless access network (e.g., Mobile broadband wireless network (mobile) Asynchronous digital subscriber lines (e.g., ADSL, VDSL) and digital video terrestrial broadcasting Network and its extensions DVB handheld Networks, ultra-wideband (UWB) networks, AC power lines, etc.

[0032] As shown, network interface 26 may include transceiver 30. In some embodiments, all or part of transceiver 30 may be located within processor 12. Transceiver 30 may support the transmission and reception of various wireless signals via one or more antennas, and therefore may include both a transmitter and a receiver. The power supply 29 of user equipment 10 may include any suitable power source, such as a rechargeable lithium polymer (Li-poly) battery and / or an alternating current (AC) power converter.

[0033] Figure 2 It is based on the implementation scheme of this disclosure. Figure 1 The functional diagram of user equipment 10 is shown. As shown, processor 12, memory 14, transceiver 30, transmitter 52, receiver 54 and / or antenna 55 (shown as 55A-55N, collectively referred to as antenna 55) may be directly or indirectly communicatively coupled to each other (e.g., through or via another component, communication bus, network) to transmit and / or receive data between each other.

[0034] User equipment 10 may include transmitter 52 and / or receiver 54, which respectively enable the user equipment 10 to transmit and receive data with external devices via, for example, a network (e.g., including a base station) or a direct connection. As shown, transmitter 52 and receiver 54 may be combined into transceiver 30. User equipment 10 may also have one or more antennas 55A-55N electrically coupled to transceiver 30. Antennas 55A-55N may be configured in omnidirectional or directional configurations, single-beam, dual-beam, or multi-beam arrangements, etc. Each antenna 55 may be associated with one or more beams and various configurations. In some embodiments, multiple antennas in antennas 55A-55N of an antenna group or module may be communicatively coupled to a respective transceiver 30 and each transmits radio frequency signals that can be advantageously and / or destructively combined to form a beam. User equipment 10 may include multiple transmitters, multiple receivers, multiple transceivers, and / or multiple antennas suitable for various communication standards. In some implementations, transmitter 52 and receiver 54 may transmit and receive information via other wired or wired systems or devices.

[0035] As shown in the figure, various components of user equipment 10 can be coupled together via bus system 56. Bus system 56 may include, for example, a data bus, as well as power buses, control signal buses, and status signal buses in addition to the data bus. Components of user equipment 10 can be coupled together or use some other mechanism to accept or provide input to each other.

[0036] Figure 3is a schematic diagram of a communication system 58 in accordance with an embodiment of the present disclosure, which includes a user equipment 10 in communication with a communication network 60 via a base station 62. The network 60 can include any suitable communication network, such as a cellular network (e.g., a 3G cellular network, a 4G / LTE cellular network, a 5G / NR cellular network, etc.). Similarly, the base station 62 can include any suitable electronic device (such as a communication hub or node) that facilitates, supports, and / or implements the network 60, including a NodeB, an eNodeB, a gNodeB, etc. The network 60 and / or the base station 62 can include some or all of the components of the user equipment 10 shown in FIGS. 1, 2, and 3 (e.g., including the processor 12, the memory 14, the storage device 16, the transceiver 30, the transmitter 52, the receiver 54, etc.). The user equipment 10 can communicate with the base station 62 using any suitable communication protocol, but purely by way of example for the remainder of the present disclosure, the user equipment 10 can communicate with the base station 62 using a frequency range 2 (FR2) of a 5G / NR communication protocol (e.g., between 24.25 and 52.6 gigahertz (GHz)). Figure 1 and Figure 2 The user equipment 10 can request one or more frequency blocks or component carriers from the network 60 via the base station 62 through which the user equipment 10 can transmit and receive wireless (e.g., radio frequency) signals. In response, the network 60 can allocate one or more component carriers via the base station 62. For some standards, such as the 4th Generation (4G) or Long Term Evolution (LTE) standard, or the 5th Generation (5G) or New Radio (NR) standard, the network 60 can allocate multiple component carriers. The use of multiple component carriers for the user equipment 10 to transmit and / or receive signals can be referred to as carrier aggregation. In cases where the multiple component carriers are contiguous (e.g., immediately adjacent to each other in frequency, such that there are no frequency gaps between the multiple component carriers), guidelines or rules can be set and enforced by the 3rd Generation Partnership Project (3GPP) related to the allocated (e.g., total) bandwidth for communication using the multiple component carriers, the individual bandwidth of each component carrier, the number of contiguous multiple component carriers that can be used to communicate with the allocated bandwidth, etc. Specifically, according to the 3GPP specification, the aggregated channel in a carrier aggregation (CA) combination cannot overlap. However, following such guidelines or rules when communicating using multiple component carriers through an allocated bandwidth can result in inefficiencies.

[0037] The user equipment 10 can request one or more frequency blocks or component carriers from the network 60 via the base station 62 through which the user equipment 10 can transmit and receive wireless (e.g., radio frequency) signals. In response, the network 60 can allocate one or more component carriers via the base station 62. For some standards, such as the 4th Generation (4G) or Long Term Evolution (LTE) standard, or the 5th Generation (5G) or New Radio (NR) standard, the network 60 can allocate multiple component carriers. The use of multiple component carriers for the user equipment 10 to transmit and / or receive signals can be referred to as carrier aggregation. In cases where the multiple component carriers are contiguous (e.g., immediately adjacent to each other in frequency, such that there are no frequency gaps between the multiple component carriers), guidelines or rules can be set and enforced by the 3rd Generation Partnership Project (3GPP) related to the allocated (e.g., total) bandwidth for communication using the multiple component carriers, the individual bandwidth of each component carrier, the number of contiguous multiple component carriers that can be used to communicate with the allocated bandwidth, etc. Specifically, according to the 3GPP specification, the aggregated channel in a carrier aggregation (CA) combination cannot overlap. However, following such guidelines or rules when communicating using multiple component carriers through an allocated bandwidth can result in inefficiencies.

[0038] ​For example, when carrier aggregation is performed, if the network conditions of the user equipment 10 become low or worse (e.g., at a threshold level), the network 60 can cause the user equipment 10 to reduce or fall back to fewer component carriers according to a fallback group defined by 3GPP from the originally allocated and aggregated carriers, which can be referred to as a parent combination of aggregated carriers. That is, the network 60 can cause the user equipment 10 to release at least one component carrier of the parent combination when falling back to fewer component carriers. Specifically, 3GPP specifies that the component carriers the network 60 can cause the user equipment 10 to fall back to must be in the same fallback group as the parent combination. The fallback group of a carrier aggregation combination is a group of a fewer number of aggregated carriers (e.g., a lower order carrier aggregation bandwidth class) than the parent combination that the user equipment 10 can fall back or fallback to. Thus, when the user equipment 10 communicates using carrier aggregation, the fallback group can define an increase or maximum bandwidth of the aggregated component carriers.

[0039] Figure 4 is a table of carrier aggregation (CA) bandwidth (BW) classes for NR FR2 as set and enforced by 3GPP. The table lists the NR CA bandwidth classes 70 (e.g., A-Q) as set forth by the 3GPP specification, the aggregated channel bandwidth 72 for each NR CA bandwidth class 70, the number of contiguous component carriers (CCs) 74 whose bandwidths are aggregated together to produce each aggregated channel bandwidth 72, and the fallback group identifier 76 to which each NR CA bandwidth class 70 belongs.

[0040] For example, for a user equipment 10 that supports fallback group 2 (as indicated by 80), three carrier aggregation bandwidth classes are available: D (as indicated by 82) corresponding to 2 contiguous component carriers, E (as indicated by 84) corresponding to 3 contiguous component carriers, and F (as indicated by 84) corresponding to 4 contiguous component carriers. The aggregated channel bandwidth for the carrier aggregation bandwidth class D 82 is greater than 200 megahertz (MHz) and less than or equal to 400 MHz, the aggregated channel bandwidth for the carrier aggregation bandwidth class E 84 is greater than 400 MHz and less than or equal to 600 MHz, and the aggregated channel bandwidth for the carrier aggregation bandwidth class F 86 is greater than 600 MHz and less than or equal to 800 MHz. Thus, the aggregated channel bandwidths for the three carrier aggregation bandwidth classes D 82, E 84, and F 86 of the fallback group 2 80 do not overlap in frequency. Further, for a user equipment 10 that supports 50 MHz resolution, the user equipment 10 can communicate with the base station 62 using component carrier bandwidths of 50 MHz, 100 MHz, and 200 MHz (with a maximum supported component carrier bandwidth of 200 MHz).

[0041] However, this can result in inefficient use of the aggregated channel bandwidth. For example, the base station 62 can allocate the aggregated channel bandwidth 350 MHz to a user equipment 10 using the fallback group 2 80. For a user equipment 10 using the fallback group 2 80, this falls into category D 82 (e.g., greater than 200 megahertz (MHz) and less than or equal to 400 MHz). Category D 82 enables the use of two contiguous component carriers. Due to the possible component carrier bandwidths of 50 MHz, 100 MHz, 200 MHz, and 400 MHz of the fallback group 2 80, the user equipment 10 can be for the closest component carrier bandwidth to utilize the full bandwidth of 350 MHz as 300 MHz (one component carrier with a bandwidth of 100 MHz and one component carrier with a bandwidth of 200 MHz). Thus, 50 MHz of the allocated aggregated channel bandwidth remains unused. In some embodiments, although Figure 4 400 MHz is listed as a possible scenario, the possible component carrier bandwidths can be limited to 50 MHz, 100 MHz, and 200 MHz of the fallback group 2 80, as a 400 MHz component carrier bandwidth can not yet be implemented. Further, it should be understood that the listed possible component carrier bandwidths can be merely examples, and other bandwidths can also be considered.

[0042] To remedy at least this inefficiency, the disclosed embodiments extend at least some of the aggregated channel bandwidths of at least some of the fallback groups, such that the aggregated channel bandwidths of at least some of the fallback groups can overlap. In some embodiments, the lower bound of at least some of the aggregated channel bandwidths of the fallback groups can be extended. Figure 5 is a chart of the carrier aggregation bandwidth categories for fallback group 1 88 in NR FR2 according to an embodiment of the disclosure that enables efficient carrier aggregation bandwidth usage. As shown, the lower bound of at least some of the aggregated channel bandwidths of the fallback group 1 88 is extended (e.g., compared to those shown in Figure 4 That is, for each of the listed CA BW categories 70, the upper bound of the CA BW category 70 can be the same as the upper bound of the CA BW category with the same number of component carriers 74 and fallback group 76, as Figure 4 shown, but the lower bound can be different (e.g., extended). Further, the aggregated channel bandwidths of up to 2400 MHz of carrier aggregation are shown to be supported at 50 MHz resolution.

[0043] For example, as Figure 4 shown, the CA BW category B 90 (which is a bandwidth category corresponding to having two component carriers in the fallback group 1 88) has an upper bound of 800 MHz and a lower bound of 400 MHz. Returning to Figure 5 , the CA BW category FG1B (as indicated by 100) corresponds to having two component carriers in the fallback group 1 88. The CA BW category FG1B has an upper bound of 800 MHz and a lower bound of 400 MHz, as Figure 4The CA BW category B90 shown has the same upper bound of 800MHz, but a different lower bound of 150MHz. Therefore, a general rule could be that when the number of component carriers 74 (denoted as n) is less than 3 (e.g., n < 3), the lower bound of the bandwidth 72 of these aggregated channels in the backoff group 188 can be set to 150MHz.

[0044] When the number of component carriers 74 is greater than or equal to 3, the lower bound of the bandwidth 72 of these aggregated channels in backoff group 1 88 can be defined by the following expression 1 (in MHz):

[0045] (2n-5)×200+150 n≥3 (Expression 1)

[0046] For example, such as Figure 4 As shown, CA BW category C 92 (which corresponds to the bandwidth category with three component carriers in backoff group 1 88) has an upper bound of 1200 MHz and a lower bound of 800 MHz. Return to Figure 5 This also corresponds to the CA BW category FG1C (as indicated by 102) having three component carriers in backoff group 1 88 having the same upper bound of 1200MHz as CA BW category C 92, but having a different lower bound (e.g., 350MHz) that can be determined using expression 1.

[0047] Therefore, for each listed CA BW category 70, the upper bound of CA BW category 70 may be the same as the upper bound of CA BW categories having the same number of component carriers 74 and backoff groups 76, such as... Figure 4 As shown, but the lower bound can be different (e.g., extended). By extending the lower bound of the aggregated channel bandwidth of backoff group 1 88, at least some of the CA BW categories 70 can overlap. For example, CA BW category FG1B 100 (greater than or equal to 150 MHz and less than or equal to 800 MHz) and CA BW category FG1C 102 (greater than or equal to 350 MHz and less than or equal to 1200 MHz) overlap in frequency. This overlap can enable a first CA BW category 70 using a first component carrier number 74 and a second CA BW category 70 using a second component carrier number 74 different from the first component carrier number for the available aggregated channel bandwidth 72 in backoff group 76. The different component carrier numbers allow for greater flexibility to more fully utilize the available aggregated channel bandwidth for communication.

[0048] As an illustrative example of more efficient bandwidth usage, a 550 MHz aggregate channel bandwidth can now fall into CA BW Class FG1B 100 or FG1C 102. However, since CA BW Class FG1B 100 has only two component carriers, and the component carriers can only have 50 MHz resolution (e.g., user equipment 10 can communicate with base station 62 using component carrier bandwidths of 50 MHz, 100 MHz, 200 MHz, and 400 MHz), the two component carriers of CA BW Class FG1B 100 can best utilize 500 MHz of the full 550 MHz aggregate channel bandwidth (e.g., by using one component carrier with a bandwidth of 100 MHz and one component carrier with a bandwidth of 400 MHz). Similarly, following the 3GPP specification CA BW Class chart shown in Figure 4 As an illustrative example of more efficient bandwidth usage, a 550 MHz aggregate channel bandwidth can now fall into CA BW Class FG1B 100 or FG1C 102. However, since CA BW Class FG1B 100 has only two component carriers, and the component carriers can only have 50 MHz resolution (e.g., user equipment 10 can communicate with base station 62 using component carrier bandwidths of 50 MHz, 100 MHz, 200 MHz, and 400 MHz), the two component carriers of CA BW Class FG1B 100 can best utilize 500 MHz of the full 550 MHz aggregate channel bandwidth (e.g., by using one component carrier with a bandwidth of 100 MHz and one component carrier with a bandwidth of 400 MHz). Similarly, following the 3GPP specification CA BW Class chart shown in Figure 4 As an illustrative example of more efficient bandwidth usage, a 550 MHz aggregate channel bandwidth can now fall into CA BW Class FG1B 100 or FG1C 102. However, since CA BW Class FG1B 100 has only two component carriers, and the component carriers can only have 50 MHz resolution (e.g., user equipment 10 can communicate with base station 62 using component carrier bandwidths of 50 MHz, 100 MHz, 200 MHz, and 400 MHz), the two component carriers of CA BW Class FG1B 100 can best utilize 500 MHz of the full 550 MHz aggregate channel bandwidth (e.g., by using one component carrier with a bandwidth of 100 MHz and one component carrier with a bandwidth of 400 MHz). Similarly, following the 3GPP specification CA BW Class chart shown in

[0049] In contrast, via base station 62, network 60 can determine that CA BW Class FG1C 102 can better (e.g., fully) utilize the 550 MHz aggregate channel bandwidth, and assign CA BW Class FG1C 102 to user equipment 10. In particular, CA BW Class FG1C 102 enables the three component carriers of fallback group 1 88, thereby enabling user equipment 10 to fully utilize (e.g., utilize the full range of) the 550 MHz aggregate channel bandwidth by using one component carrier with a bandwidth of 100 MHz, one component carrier with a bandwidth of 400 MHz, and one component carrier with a bandwidth of 50 MHz. The notations “FG1B,” “FG1C,” etc. are introduced as examples, and the concepts can be implemented in the 3GPP specification with any other suitable and / or convenient notations (e.g., by simply extending the sequence of letters currently used in the specification).

[0050] Figure 6 is a carrier aggregation bandwidth class chart for fallback group 2 80 in NR FR2 that implements efficient carrier aggregation bandwidth usage according to embodiments of the present disclosure. Like the carrier aggregation bandwidth class chart for fallback group 1 88 in Figure 5 Like the carrier aggregation bandwidth class chart for fallback group 1 88 in Figure 4those shown). That is, for each of the listed CA BW classes 70, the upper bound of the CA BW class 70 can be the same as the upper bound of a CA BW class having the same number of component carriers 74 and fallback group 76, as Figure 4 shown, but the lower bound can be different (e.g., extended). Moreover, aggregated channel bandwidths of up to 1800MHz of carrier aggregation are shown to be supported at 50MHz resolution.

[0051] For example, as Figure 4 shown, CA BW class D 82 (which is a bandwidth class corresponding to having two component carriers in fallback group 2 80) has an upper bound of 400MHz and a lower bound of 200MHz. Returning to Figure 6 , CA BW class FG2B (as indicated by 110) corresponds to having two component carriers in fallback group 2 80. CA BW class FG2B 110 has the same upper bound of 400MHz as CA BW class D 82, as Figure 4 shown, but has a different lower bound of 150MHz. Thus, when the number of component carriers 74 (denoted as n) is greater than or equal to 2 (e.g., n > 2), the lower bound of these aggregated channel bandwidths 72 of fallback group 2 80 can be defined by the following expression 2 (in MHz) :

[0052] (n - 2) x 200 + 150 n > 2 (Expression 2)

[0053] For example, as Figure 4 shown, CA BW class E 84 (which is a bandwidth class corresponding to having three component carriers in fallback group 2 80) has an upper bound of 600MHz and a lower bound of 400MHz. Returning to Figure 6 , CA BW class FG2C (as indicated by 112) also corresponds to having three component carriers in fallback group 2 80 has the same upper bound of 600Mhz as CA BW class E 84, but has a different lower bound (e.g., 350MHz) that can be determined using expression 2.

[0054] Thus, for each of the listed CA BW classes 70, the upper bound of the CA BW class 70 can be the same as the upper bound of a CA BW class having the same number of component carriers 74 and fallback group 76, as Figure 4 shown, but the lower bound can be different (e.g., extended). By extending the lower bounds of the aggregated channel bandwidths of fallback group 2 80, at least some of the CA BW classes 70 can overlap. For example, CA BW class FG2B 100 (greater than or equal to 150MHz and less than or equal to 400MHz) and CA BW class FG1C 102 (greater than or equal to 350MHz and less than or equal to 600MHz) overlap in frequency.

[0055] As an illustrative example of more efficient bandwidth usage, a 350 MHz aggregate channel bandwidth can now fall into the CA BW Category FG2B 110 or FG2C 112. However, since the CA BW Category FG2B 110 has only two component carriers, and the component carriers can only have 50 MHz resolution (e.g., user equipment 10 can communicate with base station 62 using component carrier bandwidths of 50 MHz, 100 MHz, and 200 MHz), the two component carriers of the CA BW Category FG2B 110 can optimally utilize 300 MHz of the full 350 MHz aggregate channel bandwidth (e.g., by using one component carrier with a bandwidth of 100 MHz and one component carrier with a bandwidth of 200 MHz). Similarly, following the 3GPP specification CA BW Category chart shown, Figure 4 the 350 MHz aggregate channel bandwidth would fall under the CA BW Category D 82, which also corresponds to having two component carriers. Thus, following the 3GPP specification CA BW Category chart shown, Figure 4 the network 60 would optimally utilize 300 MHz of the full 350 MHz aggregate channel bandwidth (e.g., by using one component carrier with a bandwidth of 100 MHz and one component carrier with a bandwidth of 200 MHz).

[0056] In contrast, via the base station 62, the network 60 can determine that the CA BW Category FG2C 112 can better (e.g., fully) utilize the 350 MHz aggregate channel bandwidth, and assign the CA BW Category FG2C 112 to the user equipment 10. In particular, the CA BW Category FG2C 112 enables the three component carriers of the fallback group 2 80, thereby enabling the user equipment 10 to fully utilize the 350 MHz aggregate channel bandwidth (e.g., utilize its full range) by using one component carrier with a bandwidth of 100 MHz, one component carrier with a bandwidth of 200 MHz, and one component carrier with a bandwidth of 50 MHz. The symbols "FG2B," "FG2C," etc. are introduced as examples, and the concepts can be implemented in the 3GPP specification with any other suitable and / or convenient symbols (e.g., by simply extending the sequence of letters currently used in the specification).

[0057] In this way, the aggregate channel bandwidth of the fallback groups that are assigned to overlap in frequency can more fully utilize the assigned aggregate channel bandwidth for communication. Moreover, enabling more efficient utilization of the assigned aggregate channel bandwidth scales well with increased aggregate channel bandwidth. For example, while conventional aggregate channel bandwidths can include about 100 MHz of bandwidth, the disclosed embodiments can enable efficient utilization of any suitable range of assigned aggregate channel bandwidth, such as 1600 MHz.

[0058] Figure 7 is a table illustrating full aggregation channel BW 72 coverage for a fallback group 188 having up to 1600 MHz and 50 MHz resolution in accordance with an embodiment of the present disclosure. For each aggregation channel BW 72 (in MHz), the composition 120 corresponding to the bandwidth of component carriers (in MHz) and the CA BW class 70 are indicated. For example, the previously discussed example of an allocated aggregation channel bandwidth of 550 MHz for fallback group 1 is included and identified as CA BW class FBG1C (as indicated by 122), which enables network 60 to allocate a first component carrier of 400 MHz, a second component carrier of 100 MHz, and a third component carrier of 50 MHz to user equipment 10. As shown, the table uses up to six component carriers to achieve full aggregation channel BW 72 coverage for fallback group 188 having up to 1600 MHz and 50 MHz resolution (e.g., full coverage of 50 MHz to 1600 MHz bandwidth in 50 MHz increments) (e.g., with the use of CA BW class FBG1F as indicated by 124 to enable an example of an allocated aggregation channel bandwidth of 1550 MHz).

[0059] Figure 8 is a table illustrating full aggregation channel BW 72 coverage for a fallback group 280 having up to 1600 MHz and 50 MHz resolution in accordance with an embodiment of the present disclosure. For each aggregation channel BW 72 (in MHz), the composition 140 corresponding to the bandwidth of component carriers (in MHz) and the CA BW class 70 are indicated. For example, the previously discussed example of an allocated aggregation channel bandwidth of 350 MHz for fallback group 2 is included and identified as CA BW class FBG2C (as indicated by 142), which enables network 60 to allocate a first component carrier of 200 MHz, a second component carrier of 100 MHz, and a third component carrier of 50 MHz to user equipment 10. As shown, the table uses up to nine component carriers to achieve full aggregation channel BW 72 coverage for fallback group 280 having up to 1600 MHz and 50 MHz resolution (e.g., full coverage of 50 MHz to 1600 MHz bandwidth in 50 MHz increments) (e.g., with the use of CA BW class FBG2I as indicated by 144 to enable an example of an allocated aggregation channel bandwidth of 1550 MHz).

[0060] Figure 9is a flowchart of a method 150 for a user equipment 10 to more fully utilize an aggregated channel bandwidth in accordance with embodiments of the present disclosure. Any suitable device (e.g., a controller) that can control a component of the user equipment 10, such as the processor 12, can perform the method 150. In some embodiments, the method 150 can be implemented by using the processor 12 to execute instructions stored in a tangible, non-transitory computer-readable medium, such as the memory 14 or the storage 16. For example, the method 150 can be performed, at least in part, by one or more software components, such as an operating system of the user equipment 10, one or more software applications of the user equipment 10, and the like. Although the method 150 is described using a particular order of steps, it should be understood that the present disclosure contemplates that the described steps can be performed in a different order than shown, and that certain described steps can be skipped or not performed at all.

[0061] In process block 152, the processor 12 of the user equipment 10 requests a carrier aggregation bandwidth based on the supported fallback groups. Specifically, the processor 12 can receive or determine its supported fallback groups 76. Then, the processor 12 can cause the transmitter 52 of the user equipment 10 to transmit a request to the base station 62, and the request can include one or more supported fallback groups 76 (e.g., the fallback group 2 80).

[0062] In process block 154, the processor 12 receives an indication of an aggregated channel bandwidth category 70 that implements the supported fallback groups 76 (e.g., via the receiver 54 of the user equipment 10). Specifically, the network 60 can determine the aggregated channel bandwidth category 70 based on the supported fallback groups 76 received from the user equipment 10, and send an indication of the determined aggregated channel bandwidth category 70 to the user equipment 10. As discussed above, the aggregated channel bandwidth category 70 can overlap in frequency with at least one other aggregated channel bandwidth category 70 of the fallback groups 76. Further, the aggregated channel bandwidth category 70 can use the component carrier bandwidths associated with that fallback group 76 to implement full or complete utilization of the corresponding aggregated channel bandwidth 72 (or more utilization of the aggregated channel bandwidth 72 than the illustrated 3GPP specification CA BW category chart). Figure 4 Referring to the previous example, the CA BW category FG2C 112 enables the user equipment 10 to fully utilize the full aggregated channel bandwidth of 350 MHz (e.g., utilize its full range) by using the three component carriers with bandwidths of 50 MHz, 100 MHz, and 200 MHz in the fallback group 2 80, as compared to the illustrated 3GPP specification CA BW category chart, which only implements 300 MHz of use of the allocated aggregated channel bandwidth of 350 MHz, as it best implements use of two component carriers with bandwidths of 100 MHz and 200 MHz. Figure 4 Referring to the previous example, the CA BW category FG2C 112 enables the user equipment 10 to fully utilize the full aggregated channel bandwidth of 350 MHz (e.g., utilize its full range) by using the three component carriers with bandwidths of 50 MHz, 100 MHz, and 200 MHz in the fallback group 2 80, as compared to the illustrated 3GPP specification CA BW category chart, which only implements 300 MHz of use of the allocated aggregated channel bandwidth of 350 MHz, as it best implements use of two component carriers with bandwidths of 100 MHz and 200 MHz.

[0063] In process block 156, the processor 12 transmits and / or receives signals using the number of component carriers 74 based on the supported back-off groups 76 and the received aggregated channel bandwidth 72 associated with the aggregated channel bandwidth category 70. In the previous example, the processor 12 can cause the transmitter 52 and / or receiver 54 to transmit and / or receive signals (e.g., wireless signals, radio frequency signals) using a full aggregated channel bandwidth of 350 MHz via three component carriers with bandwidths of 50 MHz, 100 MHz, and 200 MHz in the back-off group 2 80. It should be understood that in some cases, the processor 12 can store the available aggregated channel bandwidth categories 70 that fully or more fully utilize each aggregated channel bandwidth 72 in a memory 14 or storage device 16 in the network 60, base station 62, and / or user equipment 10 (such as in the form of a lookup table), and the processor 12 can determine the number of component carriers 74 by looking up the aggregated channel bandwidth category 70 in the memory 14 or storage device 16 and determining the corresponding number of component carriers 74. In this way, the method 150 enables the user equipment 10 to more fully utilize the aggregated channel bandwidth.

[0064] Figure 10 is a flowchart of a method 170 for a network 60 and / or base station 62 to provide an aggregated channel bandwidth that can be more fully used for communication according to embodiments of the present disclosure. Any suitable device (e.g., a controller) that can control a component of the network 60 and / or base station 62, such as the processor 12, can perform the method 170. In some embodiments, the method 170 can be implemented by using the processor 12 to execute instructions stored in a tangible, non-transitory computer-readable medium, such as the memory 14 or storage device 16. For example, the method 170 can be performed, at least in part, by one or more software components, such as an operating system of the network 60 and / or base station 62, one or more software applications of the network 60 and / or base station 62, and the like. Although the method 170 is described using a particular order of steps, it should be understood that the present disclosure contemplates that the steps described can be performed in a different order than shown and that certain described steps can be skipped or not performed at all.

[0065] In process block 172, the processor 12 of the network 60 and / or base station 62 receives a request for a carrier aggregation bandwidth based on the back-off groups 76 from the user equipment 10. Specifically, the request can include one or more back-off groups 76 (e.g., the back-off group 2 80) supported by the user equipment 10. The request can be received via the receiver 54 of the base station 62.

[0066] In process block 174, processor 12 determines an available aggregate channel bandwidth 72. Specifically, at certain times, the available aggregate channel bandwidth 72 can be limited (e.g., due to other user equipment 10 or devices utilizing network resources). Accordingly, processor 12 can determine which aggregate channel bandwidth 72 is available for allocation to user equipment 10. For example, processor 12 can determine that a 350 MHz aggregate channel bandwidth 72 is available for allocation to user equipment 10.

[0067] In process block 176, processor 12 determines an aggregate channel bandwidth category 70 based on the available aggregate channel bandwidth 72. The aggregate channel bandwidth category 70 can overlap in frequency with at least one other aggregate channel bandwidth category 70 of the fallback group 76. Specifically, processor 12 can determine the aggregate channel bandwidth category 70 to utilize the component carrier bandwidths associated with the fallback group 76 to fully or more fully utilize the corresponding aggregate channel bandwidth 72. That is, processor 12 can compare the available aggregate channel bandwidth categories 70 and determine which available aggregate channel bandwidth category 70 increases or maximizes the use of the aggregate channel bandwidth 72. In some cases, processor 12 can determine the available aggregate channel bandwidth category 70 that fully or more fully utilizes the aggregate channel bandwidth 72 of the available aggregate channel bandwidth category 70 by applying the available bandwidth of each component carrier (e.g., 50 MHz, 100 MHz, 200 MHz, 400 MHz) to each component carrier available to the available aggregate channel bandwidth category 70.

[0068] For the above example, if processor 12 receives an indication in process block 172 that user equipment 10 supports fallback group 2 80 and determines in process block 174 that the available aggregate channel bandwidth 72 is 350 MHz, processor 12 can determine that the available aggregate channel bandwidth category 70 is FG2B 110 or FG2C 112, as both support a 350 MHz aggregate channel bandwidth 72, as shown in Table 1. Figure 6However, the processor 12 can determine to assign the user equipment 10 the available aggregation channel bandwidth class 70 FG2C 112, as it enables the user equipment 10 to fully utilize the full aggregation channel bandwidth of 350 MHz by using three component carriers having bandwidths of 50 MHz, 100 MHz, and 200 MHz (as opposed to FG2B 110, which can only optimally utilize 300 MHz of the full aggregation channel bandwidth of 350 MHz by using two component carriers having bandwidths of 100 MHz and 200 MHz). It should be understood that in some cases, the processor 12 can store the available aggregation channel bandwidth classes 70 that fully or more fully utilize each aggregation channel bandwidth 72 in a memory 14 or storage device 16 in the network 60, base station 62, and / or user equipment 10 (such as in the form of a lookup table), and the processor 12 can determine the available aggregation channel bandwidth class 70 that fully or more fully utilizes the aggregation channel bandwidth 72 by looking up the aggregation channel bandwidth 72 in the memory 14 or storage device 16 and determining the corresponding aggregation channel bandwidth class 70.

[0069] In process block 178, the processor 12 sends (e.g., using the transmitter 52 of the base station 62) an indication of the aggregation channel bandwidth class 70 to the user equipment 10. For the above example, the processor 12 can send the full and available aggregation channel bandwidth 72 of 350 MHz to the user equipment 10, as opposed to the aggregation channel bandwidth of 300 MHz, as the user equipment 10 can fully utilize the aggregation channel bandwidth 72 of 350 MHz using three component carriers having bandwidths of 50 MHz, 100 MHz, and 200 MHz. In the absence of the disclosed embodiments implementing the overlapping aggregation channel bandwidth classes 70, the processor 12 would follow the 3GPP specification CA BW Class chart shown and would be able to only optimally send the aggregation channel bandwidth 72 of 300 MHz, as only two component carriers would be available to the user equipment in the absence of the overlapping aggregation channel bandwidth classes 70, which would limit the utilization of the aggregation channel bandwidth 72 to a first component carrier having a bandwidth of 200 MHz and a second component carrier having a bandwidth of 100 MHz. In this way, the method 170 enables the network 60 and / or base station 62 to provide an aggregation channel bandwidth 72 that can be more fully utilized for communication. Figure 4 the 3GPP specification CA BW Class chart shown and would be able to only optimally send the aggregation channel bandwidth 72 of 300 MHz, as only two component carriers would be available to the user equipment in the absence of the overlapping aggregation channel bandwidth classes 70, which would limit the utilization of the aggregation channel bandwidth 72 to a first component carrier having a bandwidth of 200 MHz and a second component carrier having a bandwidth of 100 MHz. In this way, the method 170 enables the network 60 and / or base station 62 to provide an aggregation channel bandwidth 72 that can be more fully utilized for communication.

[0070] The foregoing detailed description has shown, by way of example, various embodiments as described in detail, and it should be understood that these embodiments can be subjected to various modifications and alternative forms. It should also be understood that the specification is not intended to limit the claims to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

[0071] The technology described and claimed herein was made in all good faith, which will be evident on reading the foregoing disclosure, and thus is not abstract, intangible or purely theoretical. Moreover, to the extent that any claim appended to the end of this specification contains one or more elements designated as "means for [performing a function]..." or "steps for [performing a function]...", those elements are to be interpreted in accordance with 35 U.S.C. 112(f). However, for any claim that contains elements designated in any other manner, those elements are not to be interpreted in accordance with 35 U.S.C. 112(f).

[0072] It is well understood that, by using personally identifiable information, one must follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risks it faces of being accidentally or unlawfully accessed or used, and that is consistent with maintaining user trust and confidence, and that is in accordance with governmental privacy requirements and consumer awareness.

Claims

1. A method for communication, comprising: At the base station, requests for carrier aggregation bandwidth are received from the user equipment based on backoff groups; The available aggregated channel bandwidth is determined by the processing circuitry; as well as Based on the available aggregated channel bandwidth of the backoff group, an indication of the aggregated channel bandwidth category is sent from the base station to the user equipment. The aggregated channel bandwidth category overlaps with another aggregated channel bandwidth category in the backoff group. The aggregated channel bandwidth category has multiple aggregated channel bandwidth categories that use at least five component carriers to utilize the full range of available aggregated channel bandwidth from 50 MHz to at least 1550 MHz at a resolution of 50 MHz.

2. The method of claim 1, wherein a first component carrier number is used to implement the aggregated channel bandwidth category, a second component carrier number is used to implement the other aggregated channel bandwidth category, and the first component carrier number is different from the second component carrier number.

3. The method of claim 1, wherein the aggregated channel bandwidth category utilizes the lowest frequency to the highest frequency of the available aggregated channel bandwidth.

4. The method of claim 1, wherein the aggregated channel bandwidth category corresponds to a first bandwidth range including the available aggregated channel bandwidth, and the other aggregated channel bandwidth category corresponds to a second bandwidth range including the available aggregated channel bandwidth.

5. The method of claim 1, wherein the backoff group achieves a maximum supported component carrier bandwidth of 400 MHz.

6. The method of claim 1, wherein the backoff group achieves a maximum supported component carrier bandwidth of 200 MHz.

7. The method of claim 1, wherein the aggregated channel bandwidth category uses at least seven component carriers to utilize the full range of available aggregated channel bandwidth from 50 MHz to 1600 MHz at a resolution of 50 MHz.

8. An electronic device, the electronic device comprising: A receiver configured to receive a first signal from user equipment; A transmitter configured to send a second signal to the user equipment; and At least one processor, the at least one processor being configured to receive a request for carrier aggregation bandwidth from the user equipment based on a backoff group; Determine the available aggregated channel bandwidth, and Based on the available aggregated channel bandwidth of the backoff group, an indication of an aggregated channel bandwidth category is sent to the user equipment via the at least one processor. The aggregated channel bandwidth category has multiple aggregated channel bandwidth categories that utilize the full range of available aggregated channel bandwidth from 50 MHz to at least 1550 MHz at a resolution of 50 MHz using at least five component carriers, and enable the user equipment to utilize the full range of available aggregated channel bandwidth using a number of component carriers.

9. The electronic device of claim 8, wherein the available aggregation channel bandwidth is greater than 100 MHz.

10. The electronic device of claim 8, wherein the available aggregation channel bandwidth is 1600 MHz.

11. The electronic device of claim 8, wherein the backoff group achieves a maximum supported component carrier bandwidth of 400 MHz, and wherein the aggregated channel bandwidth category has multiple aggregated channel bandwidth categories that utilize six component carriers to take advantage of the full range of available aggregated channel bandwidth from 50 MHz to 1600 MHz at a resolution of 50 MHz.

12. The electronic device of claim 11, wherein the rollback group includes rollback group 1 as defined by the 3rd Generation Partnership Project (3GPP) specification.

13. The electronic device of claim 8, wherein the backoff group achieves a maximum supported component carrier bandwidth of 200 MHz, and wherein the aggregated channel bandwidth category has multiple aggregated channel bandwidth categories that utilize nine component carriers to take advantage of the full range of available aggregated channel bandwidth from 50 MHz to 1600 MHz at a resolution of 50 MHz.

14. The electronic device of claim 13, wherein the rollback group includes rollback group 2 as defined by the 3rd Generation Partnership Project (3GPP) specification.

15. A user equipment comprising: A transmitter configured to be communicatively coupled to a base station; A receiver configured to be communicatively coupled to the base station; and At least one processor, the at least one processor being configured to request carrier aggregation bandwidth from the base station via the transmitter based on a supported backoff group; The receiver receives an indication of the aggregated channel bandwidth category implementing the supported backoff group, the aggregated channel bandwidth category having multiple aggregated channel bandwidth categories that use at least five component carriers to utilize the full range of available aggregated channel bandwidth from 50 MHz to at least 1550 MHz at a resolution of 50 MHz, and wherein the aggregated channel bandwidth category overlaps with another aggregated channel bandwidth category of the supported backoff group; and Based on the aggregated channel bandwidth category, signals are transmitted to the base station via the transmitter or received from the base station via the receiver through the aggregated channel bandwidth.

16. The user equipment of claim 15, wherein the at least one processor is configured to transmit the signal to the base station via the transmitter or receive the signal from the base station via the receiver based on the number of component carriers using the aggregation channel bandwidth category.

17. The user equipment of claim 15, wherein the aggregated channel bandwidth category has multiple aggregated channel bandwidth categories utilizing the full range of available aggregated channel bandwidth at a resolution of 50 MHz, wherein the full range of available aggregated channel bandwidth includes up to 1600 MHz.

18. The user equipment of claim 15, wherein a first number of component carriers is used to implement the aggregated channel bandwidth category, a second number of component carriers is used to implement the other aggregated channel bandwidth category, and the first number is different from the second number.

19. The user equipment of claim 15, wherein the aggregated channel bandwidth category utilizes the lowest frequency to the highest frequency of the available aggregated channel bandwidth.

20. The user equipment of claim 15, wherein the aggregated channel bandwidth category corresponds to a first bandwidth range including available aggregated channel bandwidth, and the other aggregated channel bandwidth category corresponds to a second bandwidth range including the available aggregated channel bandwidth.

Images