Signaling for aggregated channel bandwidth for carrier aggregation
By introducing a signaling mechanism of carrier aggregation channel bandwidth in the wireless communication system, the UE and network entities negotiate the supported aggregation bandwidth and optimize the carrier aggregation configuration, solving the problems of large signaling overhead and improper resource allocation in the prior art. Improves communication efficiency and system performance.
Patent Information
- Application Number
- CN202280094929.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-22
- Publication Date
- 2024-11-29
AI Technical Summary
It is difficult for existing wireless communication systems to effectively manage the aggregation channel bandwidth in carrier aggregation, resulting in increased signaling overhead and improper resource allocation, affecting communication efficiency.
Through the signaling mechanism of carrier aggregation channel bandwidth between the user equipment (UE) and the network entity, the UE sends a supported aggregation bandwidth indication and receives a carrier aggregation configuration based on the indication to optimize the carrier aggregation configuration and reduce signaling overhead.
By optimizing the carrier aggregation configuration, communication efficiency is improved, signaling overhead is reduced, resource configuration is ensured to meet the capabilities of the UE, and system performance is improved.
Smart Images

Figure CN119054329A_ABST
Abstract
Description
Technical Field
[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for signaling for aggregated channel bandwidth for carrier aggregation. Background Art
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.
[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention
[0005] Some aspects described herein relate to a user equipment (UE) for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an indication of a supported aggregate bandwidth for carrier aggregation associated with a frequency band combination to a network entity. The one or more processors may be configured to receive a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0006] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a supported aggregate bandwidth for carrier aggregation associated with a UE for frequency band combination. The one or more processors may be configured to send a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include sending an indication of supported aggregate bandwidths for carrier aggregation associated with a frequency band combination to a network entity. The method may include receiving a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving an indication of a supported aggregate bandwidth associated with a UE for carrier aggregation associated with a frequency band combination. The method may include sending a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to: send an indication of supported aggregate bandwidth for carrier aggregation associated with a frequency band combination to a network entity. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to: receive an indication of a supported aggregate bandwidth for carrier aggregation associated with a UE for a frequency band combination. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to: send a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of supported aggregate bandwidths for carrier aggregation associated with a frequency band combination to a network entity. The apparatus may include means for receiving, from the network entity, a carrier aggregation configuration associated with the frequency band combination, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of supported aggregate bandwidths for carrier aggregation associated with a UE for frequency band combination. The apparatus may include means for sending a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidths.
[0013] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings and description.
[0014] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above in order to better understand the subsequent specific embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the attached claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each figure is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0015] Although various aspects are described in the present disclosure by the description of some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment combined with the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of different sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0018] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.
[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.
[0020] Figure 4 is a diagram illustrating an example of carrier aggregation according to the present disclosure.
[0021] Figure 5 is a diagram of an example associated with signaling for aggregated channel bandwidth for carrier aggregation according to the present disclosure.
[0022] Figure 6is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.
[0023] Figure 7 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.
[0024] Figure 8 is a diagram of an example apparatus for wireless communications.
[0025] Fig. 9 is a diagram of an example apparatus for wireless communications. DETAILED DESCRIPTION
[0026] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0028] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0029] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.
[0030] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 that has an association with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.
[0031] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.
[0032] In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or with one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.
[0033] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.
[0034] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0035] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate directly with each other or indirectly via wireless or wired backhaul links.
[0036] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.
[0037] Some UEs 120 may be considered as machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as user premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. In a given geographic area, each frequency may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0041] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0042] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0043] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: send an indication of supported aggregate bandwidths for carrier aggregation associated with a frequency band combination to a network entity; and receive a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0044] In some aspects, a network entity (e.g., Figure 1 and Figure 2 10) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receive an indication of a supported aggregate bandwidth for carrier aggregation associated with a frequency band combination associated with a UE; and send a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0045] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.
[0046] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).
[0047] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 5 to 9 ) any aspects of any of the methods described herein.
[0052] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 5 to 9 ) any aspects of any of the methods described herein.
[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the base station 110 may perform one or more techniques associated with signaling for aggregated channel bandwidth for carrier aggregation, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Figure 6 The process of 600 Figure 7 700 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0054] In some aspects, the UE 120 includes: means for sending an indication of supported aggregate bandwidths for carrier aggregation associated with a frequency band combination to a network entity; and / or means for receiving a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth. The means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.
[0055] In some aspects, a network entity includes: means for receiving an indication of a supported aggregate bandwidth for carrier aggregation associated with a frequency band combination associated with a UE; and / or means for sending a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth. In some aspects, the means for the network entity to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.
[0056] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0057] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.
[0058] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station.
[0059] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as a CU, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.
[0060] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.
[0061] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. The DU 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.
[0062] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.
[0063] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.
[0064] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.
[0065] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.
[0066] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RTRIC 315 configured to support the functionality of the SMO framework 305.
[0067] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.
[0068] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).
[0069] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.
[0070] Figure 4 is a diagram illustrating an example 400 of carrier aggregation according to the present disclosure.
[0071] Carrier aggregation is a technique that enables two or more component carriers (CCs) to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. CCs may also be referred to herein as carriers. As shown, carriers may be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers may be combined. A network entity may configure carrier aggregation for a UE 120 (such as in an RRC message, downlink control information (DCI), and / or another signaling message).
[0072] The carrier aggregation configuration may be based on a frequency band combination associated with the carrier aggregation (e.g., sometimes referred to as a band combination). As used herein, a "band combination" may refer to one or more frequency bands associated with carrier aggregation. For example, a wireless communication standard (such as 3GPP) may define various frequency bands and may indicate various carrier aggregation configurations for frequency band combinations. For example, in 3GPP Technical Specification 38.101-1 Version 17.5.0, different frequency band combinations may be defined, such as CA_n1B, CA_n7B, CA_n48B, CA_n1A-n3A and / or CA_n1(2A)-n3B, etc. (e.g., where CA_n1B is associated with the n1 band and carrier aggregation category B). For intra-band carrier aggregation, a given frequency band combination may include a single frequency band. For inter-band carrier aggregation, a given frequency band combination may include multiple frequency bands.
[0073] In some examples, the configuration parameters for the carrier aggregation configuration may be different for different frequency band combinations. As an example, for different frequency band combinations, different channel bandwidths for carriers associated with carrier aggregation may be supported. As another example, the maximum aggregate bandwidth may be different for different frequency band combinations. As used herein, "aggregate bandwidth" may refer to the sum or combination of the bandwidths of all carriers associated with the carrier aggregation operation. For example, if a first carrier (or CC) is associated with a bandwidth of 10 MHz and a second carrier (or CC) is associated with a bandwidth of 15 MHz, the aggregate bandwidth for the carrier aggregation operation may be 25 MHz (e.g., 10 MHz + 15 MHz). The maximum aggregate bandwidth may be defined by a wireless communication standard (such as 3GPP) or otherwise fixed. For example, 3GPP Technical Specification 38.101-1 Version 17.5.0 may define the maximum aggregate bandwidth for various frequency band combinations.
[0074] Additionally or alternatively, the maximum aggregate bandwidth may be based on a carrier aggregation class (e.g., associated with a given frequency band). The carrier aggregation class may define a minimum aggregate channel bandwidth, a maximum aggregate channel bandwidth, and / or a number of carriers (or CCs). For example, the carrier aggregation class may be defined or otherwise fixed by a wireless communication standard (such as 3GPP) (e.g., such as by 3GPP Technical Specification 38.101-1 Version 17.5.0). As an example, carrier aggregation class B (e.g., as defined by 3GPP or otherwise fixed) may be associated with an aggregate bandwidth between 20 MHz and 100 MHz resulting from the aggregation of two carriers (e.g., due to the aggregation of two radio channels). As another example, carrier aggregation class D (e.g., as defined by 3GPP or otherwise fixed) may be associated with an aggregate bandwidth between 200 MHz and 300 MHz resulting from the aggregation of three carriers (e.g., due to the aggregation of three radio channels).
[0075] As indicated by reference numeral 405, in some examples, carrier aggregation may be configured as an intra-band contiguous mode, in which the aggregated carriers are contiguous with each other and in the same frequency band. As indicated by reference numeral 410, in some examples, carrier aggregation may be configured as an intra-band discontiguous mode, in which the aggregated carriers are discontiguous with each other and in the same frequency band. As indicated by reference numeral 415, in some examples, carrier aggregation may be configured as an inter-band discontiguous mode, in which the aggregated carriers are discontiguous with each other and in different frequency bands.
[0076] In carrier aggregation, UE 120 may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some examples, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some examples, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.
[0077] In some cases, UE 120 may send an indication of one or more capabilities of UE 120 associated with carrier aggregation. For example, UE 120 may send an indication to a network entity that enables UE 120 to support one or more frequency band combinations configured with carrier aggregation. In some examples, UE 120 may send an indication of a set of bandwidth combinations (BCS) for a given frequency band combination supported by UE 120. For example, a wireless communication standard (such as 3GPP) (e.g., such as in 3GPP Technical Specification 38.101-1 Version 17.5.0) may define supported channel or carrier bandwidths and a maximum aggregate bandwidth for a given frequency band combination and a given BCS. For example, a first set of supported channel or carrier bandwidths and a first maximum aggregate bandwidth for a given frequency band combination and a first BCS, a second set of supported channel or carrier bandwidths and a second maximum aggregate bandwidth for a given frequency band combination and a second BCS, and so on. As an example, for band combination n48, carrier aggregation category B, and BCS2 (BCS2), the supported bandwidths for the first carrier may include {10 MHz, 15 MHz, 20 MHz, 30 MHz, 40 MHz}, the supported bandwidths for the second carrier may include {10 MHz, 15 MHz, 20 MHz, 30 MHz, 40 MHz, 50 MHz, 60 MHz, 70 MHz, 80 MHz, and 90 MHz}, and the maximum aggregate bandwidth may be 100 MHz. In the above example, the network entity may avoid configuring channel bandwidth combinations for the two carriers 15+90, 20+90, 30+80, 30+90, 40+70, 40+80, and 40+90, because these combinations will equal or exceed the defined maximum aggregate bandwidth of 100 MHz. UE 120 may send an indication of supported BCS for a given band combination to indicate which set of supported channels or carrier bandwidths and / or which maximum aggregate bandwidth is supported by UE 120 for carrier aggregation associated with the given band combination.
[0078] However, the use of BCSs may introduce additional complexity because new parameters for different BCSs may need to be defined and / or agreed upon (e.g., by 3GPP) whenever a new band combination and / or a new channel bandwidth for a band combination is introduced for use in a wireless communication network. Therefore, a BCS (e.g., BCS4, BCS5, and / or other similar BCSs as defined by 3GPP or otherwise fixed) is introduced that, when reported by a UE 120 associated with a given band combination, indicates that all possible channel bandwidths defined for the given band combination are supported by the UE 120. For example, bandwidth combination sets 4 and 5 may include all possible defined channel bandwidths for each band in the combination.
[0079] However, in some cases, one or more combinations of supported bandwidths for a given band combination and / or carrier aggregation class may be associated with a possible aggregate channel bandwidth that equals or exceeds an aggregate channel bandwidth supported by UE 120. In other words, UE 120 may support all possible defined channel bandwidths for each band in the combination, but not all combinations of supported bandwidths for each band in the combination. For example, for band combination n7B, it may be possible to define carrier bandwidths up to 70 MHz in combination (e.g., by aggregating a first carrier associated with a 30 MHz bandwidth and a second carrier associated with a 40 MHz bandwidth), but UE 120 may only support a maximum aggregate bandwidth of 50 MHz. In such an example, UE 120 may send an indication of one or more feature sets from the possible defined channel bandwidths for each band in the combination to a network entity. Feature sets may also be referred to as feature set combinations. For example, for band combination n7B, UE 120 may send a first feature set ({10,15,20}, {10,15,20,30}), a second feature set ({10,15}, {10,15,20,30}), and a third feature set ({10}, {10,15,20,30,40}). As shown, the indication of different feature sets ensures that the network does not configure a carrier aggregation configuration for band combination n7B that does not exceed the supported maximum aggregate bandwidth of 50 MHz. Feature sets may be reported by UE 120 for other band combinations in a manner similar to that described above. However, reporting different supported feature sets for one or more (or all) supported band combinations may result in significant signaling overhead for UE 120 and network entities. In other words, this may increase the signaling overhead associated with configuring carrier aggregation for UE 120.
[0080] For other BCSs (e.g., other BCSs that are not associated with an indication that all possible channel bandwidths defined for a given band combination are supported by UE 120, such as BCS0, BCS1, BS2, and / or BCS3), similar issues may exist in situations where UE 120 supports a maximum aggregate channel bandwidth for a given band combination that is less than a maximum aggregate channel bandwidth defined for the given band combination and BCS (e.g., defined by 3GPP or another wireless communication standard). In such examples, UE 120 may send an indication of one or more feature sets of supported carrier bandwidth combinations supported by UE 120 to a network entity. This may increase signaling overhead associated with configuring carrier aggregation for UE 120.
[0081] Some techniques and apparatus described herein enable signaling for aggregate channel bandwidths for carrier aggregation. For example, a UE 120 may send an indication of supported aggregate bandwidths (e.g., supported maximum aggregate bandwidths) for carrier aggregation associated with a frequency band combination to a network entity. The UE 120 may receive a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth. The indication of supported aggregate bandwidths (e.g., supported maximum aggregate bandwidths) may be associated with intra-band carrier aggregation (e.g., intra-band contiguous carrier aggregation and / or intra-band non-contiguous carrier aggregation) and / or inter-band carrier aggregation. In some aspects, the UE 120 may report the maximum aggregate bandwidth supported by the UE 120 per frequency band combination (e.g., separately for one or more or each frequency band combination supported by the UE 120).
[0082] For example, by reporting the supported aggregate bandwidth (e.g., the supported maximum aggregate bandwidth) for carrier aggregation associated with the band combination, UE 120 may no longer need to report one or more feature sets of supported carrier bandwidth combinations supported by UE 120. For example, the network entity may avoid configuring carriers with bandwidths that, in combination, equal and / or exceed the indicated supported aggregate bandwidth for the band combination (e.g., because the network entity may now know the supported maximum aggregate bandwidth for the band combination for UE 120). Thus, signaling overhead associated with configuring carrier aggregation for UE 120 may be reduced.
[0083] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.
[0084] Figure 5 is a diagram of an example 500 associated with signaling for aggregated channel bandwidth for carrier aggregation according to the present disclosure. Figure 5As shown, a network entity 505 (e.g., base station 110, CU, DU, and / or RU) may communicate with a UE (e.g., UE 120). In some aspects, the network entity 505 and the UE 120 may be part of a wireless network (e.g., wireless network 100). The UE 120 and the network entity 505 may be in communication with each other. Figure 5 The operations shown are performed after a wireless connection has been established.
[0085] In some aspects, as shown by reference numeral 510, the network entity 505 may send configuration information intended for the UE 120. The UE 120 may receive the configuration (e.g., from the network entity 505 or from another network entity). In some aspects, the UE may receive the configuration information via one or more of radio resource control (RRC) signaling, one or more medium access control (MAC) control elements (MAC-CEs), and / or downlink control information (DCI), etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., that the UE 120 has stored and / or that was previously indicated by the network entity 505 or another network entity), and / or explicit configuration information for the UE 120 to configure the UE 120, etc.
[0086] In some aspects, the configuration information may indicate that the UE 120 is to report capabilities associated with supported aggregate bandwidths (e.g., supported maximum aggregate bandwidths) for carrier aggregation associated with a band combination. In some aspects, the configuration information may indicate that the UE 120 is to report capabilities associated with supported aggregate bandwidths per band combination (e.g., respectively for one or more or each band combination supported by the UE 120). In some aspects, the configuration information may indicate that the UE 120 is to report capabilities associated with supported aggregate bandwidths when an aggregate bandwidth defined or fixed for the band combination (e.g., by a wireless communication standard, such as 3GPP) is greater than the supported aggregate bandwidth. In some aspects, the configuration information may indicate that the UE 120 is to report capabilities associated with supported aggregate bandwidths for the band combination when the UE 120 supports certain BCSs for the band combination (e.g., associated with a BCS indicating that the UE 120 supports all possible channel bandwidths defined for a given band combination, such as BCS4 and / or BCS5).
[0087] In some aspects, the configuration information may indicate the capability of the UE 120 to associate reports with supported aggregate bandwidths for intra-band carrier aggregation. In some aspects, the configuration information may indicate the capability of the UE 120 to associate reports with supported aggregate bandwidths for intra-band contiguous carrier aggregation. Additionally or alternatively, the configuration information may indicate the capability of the UE 120 to associate reports with supported aggregate bandwidths for intra-band non-contiguous carrier aggregation. Additionally or alternatively, the configuration information may indicate the capability of the UE 120 to associate reports with supported aggregate bandwidths for inter-band carrier aggregation. In some aspects, the configuration information may indicate that the UE 120 is to report separate supported aggregate bandwidths for intra-band carrier aggregation and inter-band carrier aggregation for a given frequency band combination (e.g., a first supported aggregate bandwidth for intra-band carrier aggregation and a second supported aggregate bandwidth for inter-band carrier aggregation).
[0088] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.
[0089] As indicated by reference numeral 515, the UE 120 may send (e.g., to the network entity 505 or another network entity) an indication of supported aggregate bandwidths for carrier aggregation associated with the frequency band combination. The network entity 505 may receive (e.g., from the UE 120 or from another network entity) an indication of supported aggregate bandwidths for carrier aggregation associated with the frequency band combination. The UE 120 may send the indication via a capability report. In some aspects, the capability report may indicate that the UE supports supported aggregate bandwidths for carrier aggregation associated with the frequency band combination. In some aspects, the indication of supported aggregate bandwidths for carrier aggregation associated with the frequency band combination may be sent or included via uplink communication, uplink control channel communication (e.g., physical uplink control channel (PUCCH) communication), RRC communication, UE capability report, UE capability signaling, UE assistance information (UAI) communication, layer 1 signaling, layer 2 signaling, and / or layer 3 signaling, etc.
[0090] In some aspects, the supported aggregate bandwidth may be associated with intra-band carrier aggregation. For example, a capability parameter (e.g., a ca-intrabandMaxAggregatedBandwidth-NR parameter) associated with indicating the maximum aggregate bandwidth for intra-band carrier aggregation (e.g., for intra-band contiguous and / or intra-band non-contiguous carrier aggregation) for a given frequency band combination may be defined. The UE 120 may include the capability parameter in a communication to indicate the supported aggregate bandwidth for intra-band carrier aggregation associated with the frequency band combination. As another example, a capability parameter (e.g., a ca-interbandMaxAggregatedBandwidth-NR parameter) associated with indicating the maximum aggregate bandwidth for inter-band carrier aggregation for a given frequency band combination may be defined. The UE 120 may include the capability parameter in a communication to indicate the supported aggregate bandwidth for inter-band carrier aggregation associated with the frequency band combination. In other words, in some aspects, the UE 120 may report separate capabilities for supporting aggregate bandwidths for intra-band carrier aggregation and inter-band carrier aggregation.
[0091] In some aspects, UE 120 may report capabilities of supported aggregate bandwidths for carrier aggregation per frequency band combination. For example, UE 120 may send a first indication of a first supported aggregate bandwidth associated with a first frequency band combination. UE 120 may send a second indication (e.g., another indication) of a second supported aggregate bandwidth (e.g., another supported aggregate bandwidth) associated with a second frequency band combination (e.g., another frequency band combination) (e.g., in the same communication or another communication).
[0092] In some aspects, the UE 120 may send an indication of a supported aggregate bandwidth associated with a band combination based at least in part on the supported aggregate bandwidth being less than a maximum aggregate bandwidth associated with a BCS for the band combination supported by the UE 120. For example, the UE 120 may send an indication of a BCS associated with carrier aggregation associated with the same band combination. The BCS may be associated with another aggregate bandwidth for carrier aggregation associated with the band combination (e.g., as defined or otherwise fixed by a wireless communication standard such as 3GPP). The supported aggregate bandwidth may be less than the other aggregate bandwidth (e.g., which is defined or otherwise fixed by the BCS and the band combination). For example, a given band combination may be associated with a carrier bandwidth that, when combined, may total an aggregate bandwidth of 100 MHz. If the UE 120 supports all possible carrier bandwidths for a given band combination, the UE 120 may send an indication that BCS4 or BCS5 (or another similar BCS) is supported for the given band combination. However, for a given band combination, UE 120 may only support a maximum aggregate bandwidth of 50 MHz. Therefore, UE 120 may send an indication of the supported aggregate bandwidth (e.g., 50 MHz) for the given band combination.
[0093] As another example, UE 120 may send an indication of a supported aggregate bandwidth associated with a band combination based at least in part on the supported aggregate bandwidth being less than a maximum aggregate bandwidth associated with a carrier aggregation class associated with the same band combination. For example, a band combination may be associated with a carrier aggregation class (e.g., as defined or otherwise fixed by a wireless communication standard such as 3GPP). A carrier aggregation class may be associated with another aggregate bandwidth for carrier aggregation associated with the band combination (e.g., as defined or otherwise fixed by a wireless communication standard such as 3GPP). The supported aggregate bandwidth may be less than the other aggregate bandwidth (e.g., as defined or otherwise fixed by the carrier aggregation class). For example, carrier aggregation class B may be associated with a maximum aggregate bandwidth of 100 MHz (e.g., as defined or otherwise fixed by a wireless communication standard such as 3GPP). However, for a given band combination associated with carrier aggregation class B, UE 120 may only support a maximum aggregate bandwidth of 50 MHz. Thus, UE 120 may send an indication of a supported aggregate bandwidth for a given frequency band combination associated with carrier aggregation category B (eg, 50 MHz).
[0094] In some aspects, in addition to the supported aggregate bandwidth associated with the band combination, the UE 120 may also send an indication of the following items for carrier aggregation associated with the band combination: the minimum channel bandwidth for a single carrier or CC and the maximum channel bandwidth for a single carrier or CC. For example, the UE 120 may send an indication of the supported aggregate bandwidth, the minimum carrier bandwidth, and / or the maximum carrier bandwidth for carrier aggregation associated with the band combination. As an example, for the band combination n7B, the UE 120 may indicate that the supported aggregate bandwidth is 50 MHz, the minimum carrier bandwidth is 10 MHz, and the maximum carrier bandwidth is 40 MHz. As another example, for the band combination n1, the UE 120 may indicate that the supported aggregate bandwidth is 100 MHz, the minimum carrier bandwidth is 20 MHz, and the maximum carrier bandwidth is 50 MHz. As yet another example, for the band combination n78, the UE 120 may indicate that the supported aggregate bandwidth is 100 MHz, the minimum carrier bandwidth is 50 MHz, and the maximum carrier bandwidth is 80 MHz. Based at least in part on the reported information, the network entity 505 may be enabled to configure carrier aggregation for the UE 120 that does not exceed the supported aggregate bandwidth for the frequency band combination (e.g., without requiring the UE 120 to report an indication of one or more feature sets supported by the UE 120 that are associated with the frequency band combination, thereby reducing signaling overhead associated with configuring carrier aggregation for the frequency band combination).
[0095] As indicated by reference numeral 520, the network entity 505 may send (e.g., to the UE 120 or to another network entity) a carrier aggregation configuration intended for the UE 120 and associated with the frequency band combination based at least in part on the supported aggregated bandwidth. The UE 120 may receive the carrier aggregation configuration (e.g., from the network entity 505 or from another network entity). In some aspects, the UE 120 may receive the carrier aggregation configuration via one or more of RRC signaling, one or more MAC CEs and / or DCI, etc. In some aspects, the carrier aggregation configuration may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., that the UE 120 has stored and / or that was previously indicated by the network entity 505 or another network entity), and / or explicit configuration information for the UE 120 to configure the UE 120, etc.
[0096] Carrier aggregation may indicate two or more carriers configured for carrier aggregation (eg, associated with a frequency band combination) for UE 120. For example, the carrier aggregation configuration may indicate the bandwidth and / or frequency domain location associated with each configured carrier, as well as other configuration parameters.
[0097] In some aspects, the network entity 505 may determine a carrier aggregation configuration based at least in part on a supported aggregate bandwidth for a frequency band combination (e.g., as reported by the UE 120). For example, the network entity 505 may determine a channel bandwidth for carriers associated with the carrier aggregation for the frequency band combination based at least in part on the supported aggregate bandwidth. For example, the network entity 505 may select a channel bandwidth for the carriers associated with the carrier aggregation from the bandwidth associated with the frequency band combination (e.g., as defined or otherwise fixed by a wireless communication standard such as 3GPP). The network entity 505 may select the channel bandwidth for the carriers while ensuring that the sum or aggregation of the channel bandwidths does not equal or exceed the supported aggregate bandwidth for the frequency band combination (e.g., as reported by the UE 120, as described elsewhere herein). For example, in some aspects, a carrier aggregation configuration may be associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth. The network entity 505 may determine the carrier aggregation configuration such that the sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth. The network entity 505 may determine a carrier aggregation configuration to be associated with more than two carriers in a similar manner.
[0098] UE 120 may configure carriers for carrier aggregation associated with the frequency band combination based at least in part on receiving the carrier aggregation configuration. For example, for intra-band carrier aggregation, UE 120 may configure carriers to be in the same frequency band. For inter-band carrier aggregation, UE 120 may configure carriers to be in different frequency bands.
[0099] As indicated by reference numeral 525, UE 120 and network entity 505 may communicate according to a carrier aggregation configuration. For example, UE 120 may send (e.g., to network entity 505 or another network entity) one or more uplink signals according to the carrier aggregation configuration (e.g., using one or more of the carriers configured by the carrier aggregation configuration). Network entity 505 may receive the one or more uplink signals according to the carrier aggregation configuration (e.g., from UE 120 or another network entity). As another example, UE 120 may receive (e.g., from network entity 505 or another network entity) one or more downlink signals according to the carrier aggregation configuration. Network entity 505 may send (e.g., to UE 120 or another network entity) the one or more downlink signals according to the carrier aggregation configuration. In other words, the carrier aggregation configuration may be associated with uplink carrier aggregation and / or downlink carrier aggregation.
[0100] By enabling the UE 120 to report supported aggregate bandwidths (e.g., supported maximum aggregate bandwidths) for carrier aggregation associated with a band combination, the UE 120 may no longer need to report one or more feature sets of supported carrier bandwidth combinations supported by the UE 120. For example, the network entity 505 may avoid configuring carriers with bandwidths that, when combined, equal and / or exceed the indicated supported aggregate bandwidth for the band combination (e.g., because the network entity 505 may now know the supported maximum aggregate bandwidth for the band combination for the UE 120). Thus, signaling overhead associated with configuring carrier aggregation for the UE 120 may be reduced.
[0101] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.
[0102] Figure 6 is a diagram illustrating an example process 600, performed, for example, by a UE, according to the present disclosure. Example process 600 is an example in which a UE (eg, UE 120) performs operations associated with signaling for aggregated channel bandwidth for carrier aggregation.
[0103] like Figure 6 As shown, in some aspects, process 600 may include sending an indication of supported aggregate bandwidths for carrier aggregation associated with a frequency band combination to a network entity (block 610). Figure 8 The communication manager 140 and / or the sending component 804 depicted in FIG. 8 may send an indication of supported aggregate bandwidths for carrier aggregation associated with the frequency band combination to a network entity, as described above.
[0104] like Figure 6 As further shown, in some aspects, process 600 may include receiving, from the network entity, a carrier aggregation configuration associated with the frequency band combination, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth (block 620). Figure 8 The communication manager 140 and / or receiving component 802 depicted in FIG. 8 may receive a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth, as described above.
[0105] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0106] In a first aspect, process 600 includes sending one or more uplink signals according to the carrier aggregation configuration.
[0107] In a second aspect, alone or in combination with the first aspect, process 600 includes receiving one or more downlink signals according to the carrier aggregation configuration.
[0108] In a third aspect, alone or in combination with one or more of the first and second aspects, process 600 includes sending an indication of another supported aggregate bandwidth for carrier aggregation associated with another frequency band combination to the network entity.
[0109] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the supported aggregate bandwidth is associated with a capability of the UE.
[0110] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication of the supported aggregate bandwidth is included in at least one of a UE capability report, UE capability signaling, or UAI communication.
[0111] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the supported aggregate bandwidth is associated with intra-band carrier aggregation.
[0112] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the intra-band carrier aggregation comprises at least one of intra-band contiguous carrier aggregation or intra-band non-contiguous carrier aggregation.
[0113] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the supported aggregate bandwidth is associated with inter-band carrier aggregation.
[0114] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
[0115] In a tenth aspect, either alone or in combination with one or more of aspects 1 to 9, process 600 comprises sending to the network entity an indication of a BCS associated with the carrier aggregation associated with the frequency band combination, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is less than the another aggregate bandwidth.
[0116] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the frequency band combination is associated with a carrier aggregation class, wherein the carrier aggregation class is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is smaller than the other aggregate bandwidth.
[0117] In the twelfth aspect, alone or in combination with one or more aspects of the first to eleventh aspects, the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and the sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
[0118] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 The depicted blocks include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.
[0119] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a network entity according to the present disclosure. Example process 700 is an example in which a network entity (e.g., network entity 505, base station 110, CU, DU, and / or RU) performs operations associated with signaling for aggregated channel bandwidth for carrier aggregation.
[0120] like Figure 7 As shown, in some aspects, process 700 may include receiving an indication of supported aggregate bandwidths for carrier aggregation associated with a frequency band combination associated with a UE (block 710). For example, a network entity (e.g., using Fig. 9 The communications manager 150 and / or receiving component 902 depicted in FIG. 1 may receive an indication of supported aggregate bandwidth associated with a UE for carrier aggregation associated with a frequency band combination, as described above.
[0121] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include sending a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth (block 720). Fig. 9 The communications manager 150 and / or sending component 904 depicted in FIG. 1 may send a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth, as described above.
[0122] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0123] In a first aspect, process 700 includes receiving one or more uplink signals according to the carrier aggregation configuration.
[0124] In a second aspect, alone or in combination with the first aspect, process 700 includes sending one or more downlink signals according to the carrier aggregation configuration.
[0125] In a third aspect, alone or in combination with one or more of the first and second aspects, process 700 includes receiving an indication of another supported aggregate bandwidth associated with the UE for carrier aggregation associated with another frequency band combination.
[0126] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the supported aggregate bandwidth is associated with a capability of the UE.
[0127] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the indication of the supported aggregate bandwidth is included in at least one of a UE capability report, UE capability signaling, or UAI communication.
[0128] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the supported aggregate bandwidth is associated with intra-band carrier aggregation.
[0129] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the intra-band carrier aggregation comprises at least one of intra-band contiguous carrier aggregation or intra-band non-contiguous carrier aggregation.
[0130] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the supported aggregate bandwidth is associated with inter-band carrier aggregation.
[0131] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
[0132] In a tenth aspect, alone or in combination with one or more of aspects one to nine, process 700 includes receiving an indication of a BCS associated with the carrier aggregation associated with the same-band combination, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the band combination, and wherein the supported aggregate bandwidth is less than the other aggregate bandwidth.
[0133] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the frequency band combination is associated with a carrier aggregation class, wherein the carrier aggregation class is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is smaller than the other aggregate bandwidth.
[0134] In the twelfth aspect, alone or in combination with one or more aspects of the first to eleventh aspects, the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and the sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
[0135] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The depicted blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.
[0136] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using receiving component 802 and transmitting component 804. As further shown, apparatus 800 may include a communication manager 140. Communication manager 140 may include a determining component 808, among other things.
[0137] In some aspects, the apparatus 800 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 800 may be configured to perform one or more of the processes described herein (such as Figure 6 In some aspects, Figure 8 The device 800 and / or one or more components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Figure 8 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0138] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 800. In some aspects, the receiving component 802 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.
[0139] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications and may provide the generated communications to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.
[0140] Transmitting component 804 can transmit to a network entity an indication of supported aggregate bandwidth for carrier aggregation associated with the frequency band combination. Receiving component 802 can receive from the network entity a carrier aggregation configuration associated with the frequency band combination, the carrier aggregation configuration based at least in part on the supported aggregate bandwidth.
[0141] Determining component 808 can determine a supported aggregate bandwidth based at least in part on capabilities of apparatus 800 .
[0142] Transmitting component 804 may transmit one or more uplink signals according to the carrier aggregation configuration.
[0143] Receiving component 802 may receive one or more downlink signals according to the carrier aggregation configuration.
[0144] Transmitting component 804 can transmit, to the network entity, an indication of another supported aggregate bandwidth for carrier aggregation associated with another frequency band combination.
[0145] Transmitting component 804 may send an indication of a BCS associated with the carrier aggregation associated with the frequency band combination to the network entity, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is less than the another aggregate bandwidth.
[0146] Figure 8 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 8 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 8 Two or more components shown may be implemented in a single component, or Figure 8 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The illustrated set (one or more) of components may be described as being executable by Figure 8 Another group of components shown performs one or more functions.
[0147] Fig. 9 900 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a network entity, or a network entity may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include carrier aggregation configuration component 908, among other things.
[0148] In some aspects, the apparatus 900 may be configured to perform Figure 5 Additionally or alternatively, the apparatus 900 may be configured to perform one or more of the processes described herein (such as Figure 7 In some aspects, Fig. 9 The device 900 and / or one or more components shown may include a combination of Figure 2 One or more components of the network entity. Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0149] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the network entity (eg, where the network entity is shown as a base station 110 as an example).
[0150] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network entity (e.g., where the network entity is shown as a base station 110 as an example). In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.
[0151] Receiving component 902 can receive an indication of supported aggregate bandwidth associated with a UE for carrier aggregation associated with a frequency band combination. Sending component 904 can send a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration based at least in part on the supported aggregate bandwidth.
[0152] Carrier aggregation configuring component 908 can determine a carrier aggregation configuration based at least in part on the supported aggregate bandwidth.Carrier aggregation configuring component 908 can determine a carrier aggregation configuration such that a sum of bandwidths of carriers associated with the carrier aggregation configuration is less than or equal to the supported aggregate bandwidth.
[0153] Receiving component 902 may receive one or more uplink signals according to the carrier aggregation configuration.
[0154] Transmitting component 904 may transmit one or more downlink signals according to the carrier aggregation configuration.
[0155] Receiving component 902 can receive an indication of another supported aggregate bandwidth associated with the UE for carrier aggregation associated with another frequency band combination.
[0156] Receiving component 902 can receive an indication of a BCS associated with the carrier aggregation associated with the band combination, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the band combination, and wherein the supported aggregate bandwidth is less than the another aggregate bandwidth.
[0157] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set (one or more) of components may be described as being executable by Fig. 9 Another group of components shown performs one or more functions.
[0158] The following provides an overview of some aspects of the disclosure:
[0159] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: sending an indication of a supported aggregate bandwidth for carrier aggregation associated with a frequency band combination to a network entity; and receiving a carrier aggregation configuration associated with the frequency band combination from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0160] Aspect 2: The method according to aspect 1 further includes: sending one or more uplink signals according to the carrier aggregation configuration.
[0161] Aspect 3: The method according to any one of aspects 1 to 2 further includes: receiving one or more downlink signals according to the carrier aggregation configuration.
[0162] Aspect 4: The method according to any one of aspects 1 to 3, further comprising: sending an indication of another supported aggregate bandwidth for carrier aggregation associated with another frequency band combination to the network entity.
[0163] Aspect 5: The method according to any one of aspects 1 to 4, wherein the supported aggregate bandwidth is associated with the capability of the UE.
[0164] Aspect 6: The method according to any one of aspects 1 to 5, wherein the indication of the supported aggregate bandwidth is included in at least one of the following: UE capability report, UE capability signaling, or UE assistance information (UAI) communication.
[0165] Aspect 7: The method according to any one of aspects 1 to 6, wherein the supported aggregate bandwidth is associated with intra-band carrier aggregation.
[0166] Aspect 8: The method according to aspect 7, wherein the intra-band carrier aggregation comprises at least one of intra-band contiguous carrier aggregation or intra-band non-contiguous carrier aggregation.
[0167] Aspect 9: The method according to any one of aspects 1 to 8, wherein the supported aggregate bandwidth is associated with inter-band carrier aggregation.
[0168] Aspect 10: The method according to any one of aspects 1 to 9, wherein the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
[0169] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: sending an indication of a bandwidth combination set (BCS) associated with the carrier aggregation associated with the frequency band combination to the network entity, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is smaller than the other aggregate bandwidth.
[0170] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the frequency band combination is associated with a carrier aggregation category, wherein the carrier aggregation category is associated with another aggregation bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregation bandwidth is smaller than the other aggregation bandwidth.
[0171] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and wherein the sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
[0172] Aspect 14: A method of wireless communication performed by a network entity, the method comprising: receiving an indication of a supported aggregate bandwidth associated with a user equipment (UE) for carrier aggregation associated with a frequency band combination; and sending a carrier aggregation configuration associated with the frequency band combination for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
[0173] Aspect 15: The method according to aspect 14 further includes: receiving one or more uplink signals according to the carrier aggregation configuration.
[0174] Aspect 16: The method according to any one of aspects 14 to 15 further includes: sending one or more downlink signals according to the carrier aggregation configuration.
[0175] Aspect 17: The method according to any one of aspects 14 to 16, further comprising: receiving an indication of another supported aggregate bandwidth associated with the UE for carrier aggregation associated with another frequency band combination.
[0176] Aspect 18: The method according to any one of aspects 14 to 17, wherein the supported aggregate bandwidth is associated with the capability of the UE.
[0177] Aspect 19: The method according to any one of aspects 14 to 18, wherein the indication of the supported aggregate bandwidth is included in at least one of the following: UE capability report, UE capability signaling or UE assistance information (UAI) communication.
[0178] Aspect 20: The method according to any one of aspects 14 to 19, wherein the supported aggregate bandwidth is associated with intra-band carrier aggregation.
[0179] Aspect 21: The method according to aspect 20, wherein the intra-band carrier aggregation comprises at least one of intra-band contiguous carrier aggregation or intra-band non-contiguous carrier aggregation.
[0180] Aspect 22: The method according to any one of aspects 14 to 21, wherein the supported aggregate bandwidth is associated with inter-band carrier aggregation.
[0181] Aspect 23: The method according to any one of aspects 14 to 22, wherein the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
[0182] Aspect 24: The method according to any one of Aspects 14 to 23 further includes: receiving an indication of a bandwidth combination set (BCS) associated with the carrier aggregation associated with the frequency band combination, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is smaller than the other aggregate bandwidth.
[0183] Aspect 25: A method according to any one of Aspects 14 to 24, wherein the frequency band combination is associated with a carrier aggregation category, wherein the carrier aggregation category is associated with another aggregation bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregation bandwidth is smaller than the other aggregation bandwidth.
[0184] Aspect 26: A method according to any one of Aspects 14 to 25, wherein the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and wherein the sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
[0185] Aspect 27: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 13.
[0186] Aspect 28: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 1 to 13.
[0187] Aspect 29: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more aspects of aspects 1 to 13.
[0188] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 13.
[0189] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more aspects of Aspects 1 to 13.
[0190] Aspect 32: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 14 to 26.
[0191] Aspect 33: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of Aspects 14 to 26.
[0192] Aspect 34: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 14 to 26.
[0193] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 14 to 26.
[0194] Aspect 36: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more aspects of Aspects 14 to 26.
[0195] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.
[0196] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.
[0197] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0198] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).
[0199] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated. In addition, as used herein, the articles "one" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "said / the" is intended to include one or more projects connected with the article "said / the", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects, and can be used interchangeably with "one or more". If you want to refer to only one project, use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").
Claims
1. A user equipment (UE) for wireless communication, the user equipment comprising: Memory; and one or more processors coupled to the memory and configured to: sending an indication of supported aggregate bandwidths for carrier aggregation associated with the frequency band combination to a network entity; and A carrier aggregation configuration associated with the frequency band combination is received from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
2. The UE of claim 1, wherein the one or more processors are further configured to perform at least one of the following operations: sending one or more uplink signals according to the carrier aggregation configuration; or One or more downlink signals are received according to the carrier aggregation configuration.
3. The UE of claim 1 , wherein the one or more processors are further configured to: An indication of another supported aggregate bandwidth for carrier aggregation associated with another frequency band combination is sent to the network entity. The UE of claim 1 , wherein the supported aggregate bandwidth is associated with a capability of the UE. 5 . The UE of claim 1 , wherein the supported aggregate bandwidth is associated with intra-band carrier aggregation, wherein the intra-band carrier aggregation comprises at least one of intra-band contiguous carrier aggregation or intra-band non-contiguous carrier aggregation. The UE of claim 1 , wherein the supported aggregate bandwidth is associated with inter-band carrier aggregation. 7 . The UE of claim 1 , wherein the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
8. The UE of claim 1, wherein the one or more processors are further configured to: An indication of a bandwidth combination set (BCS) associated with the carrier aggregation associated with the frequency band combination is sent to the network entity, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is less than the another aggregate bandwidth.
9. The UE of claim 1 , wherein the frequency band combination is associated with a carrier aggregation class, wherein the carrier aggregation class is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is smaller than the another aggregate bandwidth.
10. The UE of claim 1, wherein the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and wherein a sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
11. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving an indication of supported aggregate bandwidth for carrier aggregation associated with a frequency band combination associated with a user equipment (UE); and A carrier aggregation configuration associated with the frequency band combination is transmitted for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
12. The network entity of claim 11, wherein the supported aggregate bandwidth is associated with a capability of the UE.
13. The network entity of claim 11, wherein the indication of the supported aggregate bandwidth is included in at least one of: UE capability report, UE capability signaling, or UE Assistance Information (UAI) communication.
14. The network entity of claim 11, wherein the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
15. The network entity of claim 11, wherein the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and wherein a sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
16. A method of wireless communication performed by a user equipment (UE), the method comprising: sending an indication of supported aggregate bandwidth for carrier aggregation associated with the frequency band combination to a network entity; as well as A carrier aggregation configuration associated with the frequency band combination is received from the network entity, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
17. The method of claim 16, further comprising at least one of the following: sending one or more uplink signals according to the carrier aggregation configuration; or One or more downlink signals are received according to the carrier aggregation configuration.
18. The method according to claim 16, further comprising: An indication of another supported aggregate bandwidth for carrier aggregation associated with another frequency band combination is sent to the network entity.
19. The method of claim 16, wherein the supported aggregate bandwidth is associated with a capability of the UE.
20. The method of claim 16, wherein the supported aggregate bandwidth is associated with intra-band carrier aggregation, wherein the intra-band carrier aggregation comprises at least one of intra-band contiguous carrier aggregation or intra-band non-contiguous carrier aggregation.
21. The method of claim 16, wherein the supported aggregate bandwidth is associated with inter-band carrier aggregation.
22. The method of claim 16, wherein the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
23. The method of claim 16, further comprising: An indication of a bandwidth combination set (BCS) associated with the carrier aggregation associated with the frequency band combination is sent to the network entity, wherein the BCS is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is less than the another aggregate bandwidth.
24. The method of claim 16, wherein the frequency band combination is associated with a carrier aggregation class, wherein the carrier aggregation class is associated with another aggregate bandwidth for the carrier aggregation associated with the frequency band combination, and wherein the supported aggregate bandwidth is smaller than the another aggregate bandwidth.
25. The method of claim 16, wherein the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and wherein a sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
26. A method of wireless communication performed by a network entity, the method comprising: receiving an indication of a supported aggregate bandwidth for carrier aggregation associated with a frequency band combination associated with a user equipment (UE); as well as A carrier aggregation configuration associated with the frequency band combination is transmitted for the UE, the carrier aggregation configuration being based at least in part on the supported aggregate bandwidth.
27. The method of claim 26, wherein the supported aggregate bandwidth is associated with a capability of the UE.
28. The method of claim 26, wherein the indication of the supported aggregate bandwidth is included in at least one of: UE capability report, UE capability signaling, or UE Assistance Information (UAI) communication.
29. The method of claim 26, wherein the supported aggregate bandwidth is a maximum aggregate bandwidth supported by the UE for the carrier aggregation associated with the frequency band combination.
30. The method of claim 26, wherein the carrier aggregation configuration is associated with a first carrier associated with a first bandwidth and a second carrier associated with a second bandwidth, and wherein a sum of the first bandwidth and the second bandwidth is less than or equal to the supported aggregate bandwidth.
