Method and apparatus for beam updations with component carrier configuration

Abstract

A UE may receive information from a base station indicating a set of beams associated with a plurality of CCs. The UE may be configured to activate a set of beams on the plurality of CCs for a single TRP or for a plurality of TRPs, the set of beams being activated for a single TRP when less than two beam IDs respectively associated with the set of beams are mapped to code points and less than two pool indices are configured for CORESET associated with at least one CC of the plurality of CCs. When at least one of: the code point is mapped to two or more beam IDs, or the CORESET is configured with two or more pool indices or is not configured with a pool index, a set of beams may be activated for multiple TRPs when at least one of: the code point is mapped to two or more beam IDs, or the CORESET is configured with two or more pool indices.

Description

[0001] This application is a divisional application of an application with an application date of May 7, 2021, application number 202180032490.1 (international application number PCT / CN2021 / 092050), and name “Method and device for beam updating using component carrier configuration”. CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of International Application No. PCT / CN2020 / 089188, filed on May 8, 2020, entitled “SYSTEM AND METHOD FOR GROUP COMPONENT CARRIER-BASED BEAM UPDATE,” the disclosure of which is expressly incorporated herein by reference in its entirety. background Technical Field

[0005] The present disclosure relates generally to communication systems, and more particularly to procedures for beam management with a user equipment (UE) on a set of component carriers (CCs).

[0006] introduction

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0008] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is a part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0009] Overview

[0010] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0011] According to an example radio access technology (RAT) such as 5G New Radio (NR), a user equipment (UE) and a base station (e.g., a gNB) may have the ability to communicate on more than one component carrier (CC) and potentially simultaneously. For example, a gNB may assign a CC group to a UE for carrier aggregation, which may increase the data rate of the UE. The gNB may configure the CC group to carry certain downlink communications (e.g., downlink control information and / or downlink data) and / or certain uplink communications.

[0012] Potentially, the example RAT may include more than one transmit receive point (TRP). The TRP may be another cell (such as a secondary cell (SCell)) that is different from the cell provided by the gNB (which may be a primary cell (PCell)). For example, the TRP may be a pico cell, a femto cell, a remote radio head, or a cell connected to a radio access network (RAN) including the gNB. Potentially, the TRP may be included in the cell of a base station - for example, the TRP may effectively serve as an antenna panel for the base station. In many instances, the TRP may be configured to provide at least one CC to the UE. The set of CCs assigned to the UE may be configured by a single TRP (sTRP) or multiple TRPs (mTRP).

[0013] The UE and the gNB may communicate on a CC using directional beamforming. However, the mTRP configured for the UE may affect the directional beamforming of the UE, and the sTRP may cause the UE to sacrifice some throughput and / or reliability relative to the mTRP. For example, the UE may use different beams for communication with different TRPs of the mTRP, which may increase throughput and / or reliability, but may interfere with each other, may be quite expensive in terms of power and / or processing overhead, etc. Therefore, there is a need for TRP management with the UE for communication on a CC group.

[0014] The present disclosure describes various techniques and solutions for applying (e.g., updating) a beam by a UE for communicating with an sTRP or mTRP on at least one CC. Specifically, the present disclosure describes various methods for determining whether to apply a beam to a CC group for communicating with an sTRP or mTRP. For example, the UE may determine whether communication on a CC group is configured via an sTRP or mTRP, and the UE may determine whether to apply a beam to a CC group or a single CC based on whether the communication is configured via an sTRP or mTRP.

[0015] In a first aspect of the present disclosure, a first method, a first computer-readable medium, and a first device are provided. The first device may be a UE or a component thereof configured to receive information indicating a beam set associated with a plurality of CCs. The first device may be further configured to: activate a beam set on the plurality of CCs for sTRP or for mTRP, and when less than two beam identifiers (IDs) respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a control resource set (CORESET) associated with at least one CC of the plurality of CCs, the beam set is activated for sTRP.

[0016] In a second aspect of the present disclosure, a second method, a second computer-readable medium, and a second device are provided. The second device may be a base station or a component thereof that can configure a beam set on multiple CCs for sTRP or for mTRP, and when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a CORESET associated with at least one CC of the multiple CCs, the beam set is configured for sTRP. The second device may be further configured to transmit information indicating the beam set associated with the multiple CCs to the UE.

[0017] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0020] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0021] Figure 2Bis a diagram illustrating an example of downlink channels within a subframe according to various aspects of the present disclosure.

[0022] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0023] Figure 2D is a diagram illustrating an example of uplink channels within a subframe according to various aspects of the present disclosure.

[0024] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0025] Figure 4 is a call flow diagram illustrating an example process for communications and operations for beam management with a UE on at least one component carrier (CC) in a wireless communication system including at least one transmit reception point (TRP).

[0026] Figure 5 is a flowchart of an example method for a UE to communicate wirelessly with at least one TRP on at least one CC.

[0027] Figure 6 Flow chart of an example method for wireless communications performed by a base station for beam management of a UE configured to communicate with at least one TRP on at least one CC.

[0028] Figure 7 is a diagram illustrating an example of a hardware implementation for an example device.

[0029] Figure 8 is a diagram illustrating another example of a hardware implementation for another example device. Detailed Description

[0031] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, those skilled in the art will recognize that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, computer executable codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0034] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, each function may be stored or encoded on a computer-readable medium as one or more instructions or computer executable code. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer-accessible instructions or data structure forms of computer executable code.

[0035] In various aspects of the present disclosure, a user equipment (UE) and a base station (e.g., a gNB) may be able to communicate on more than one component carrier (CC) in an example radio access network (RAN) such as a 5G new radio (NR) RAN. For example, a base station may assign a CC group to a user equipment (UE) for carrier aggregation, which may increase the data rate and / or reliability of the UE. The base station may configure the CC group to carry certain downlink communications (e.g., downlink control information and / or downlink data) and / or certain uplink communications.

[0036] Potentially, an example radio access technology (RAT) may support more than one transmit receive point (TRP) for transmitting and / or receiving on a CC group configured for a UE. A TRP may be a cell - for example, a secondary cell (SCell) that is different from a primary cell (PCell) provided by a gNB. For example, a TRP may be a pico cell, a femto cell, a remote radio head (RRH), a smart radio head, a central unit (CU), a distributed unit (DU), a radio unit (RU), and / or a remote unit, some or all of which may be co-located or distributed, and / or may communicate with each other or with other cells or carriers connected to a radio access network (RAN) including the gNB. Potentially, a TRP may be included in a cell of a base station - for example, a TRP may effectively serve as an antenna panel of a base station and, in some instances, communicate on the same CC(s). In many instances, a TRP may be configured to provide at least one CC to a UE. The set of CCs assigned to a UE may be configured by a single TRP (sTRP) or multiple TRPs (mTRP).

[0037] The UE may communicate on a set of CCs using directional beamforming, for example, based on a configuration provided by a base station (e.g., a gNB). However, the mTRP configured for the UE may affect the directional beamforming of the UE, and the sTRP may cause the UE to sacrifice some throughput and / or reliability relative to the mTRP. For example, the UE may use different beams for communications with different TRPs of the mTRP, which may increase throughput and / or reliability, but may interfere with each other, may be quite expensive in terms of power and / or processing overhead, etc. Therefore, there is a need for TRP management with the UE for communications on a CC group.

[0038] The present disclosure describes various techniques and solutions for applying (e.g., updating) a beam by a UE for communicating with an sTRP or mTRP on at least one CC. Specifically, the present disclosure describes various methods for determining whether to activate one or more beams on a CC group for an sTRP or an mTRP. The UE can determine whether communications on a CC group are configured via an sTRP or an mTRP, and the UE can determine whether to activate the beam for communicating with an sTRP or an mTRP on one or more CCs in the group.

[0039] In a first aspect of the present disclosure, a first method, a first computer-readable medium, and a first device are provided. The first device may be a UE or a component thereof configured to receive information indicating a beam set associated with a plurality of CCs. The first device may be further configured to: activate a beam set on the plurality of CCs for sTRP or for mTRP, and when less than two beam identifiers (IDs) respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a control resource set (CORESET) associated with at least one CC of the plurality of CCs, the beam set is activated for sTRP.

[0040] In a second aspect of the present disclosure, a second method, a second computer-readable medium, and a second device are provided. The second device may be a base station or a component thereof that can configure a beam set on multiple CCs for sTRP or for mTRP, and when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a CORESET associated with at least one CC of the multiple CCs, the beam set is configured for sTRP. The second device may be further configured to transmit information indicating the beam set associated with the multiple CCs to the UE.

[0041] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0042] The base station 102 configured for 4G Long Term Evolution (LTE), collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR, which can be collectively referred to as the Next Generation RAN (NG-RAN), can interface with the core network 190 via a second backhaul link 184. The base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages, among other functions.

[0043] In some aspects, the base stations 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the core network 190) on a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless. At least some of the base stations 102 may be configured for integrated access and backhaul (IAB). Therefore, such base stations may communicate wirelessly with other such base stations. For example, at least some of the base stations 102 configured for IAB may have a split architecture including at least one of a CU, a DU, a RU, an RRH, and / or a remote unit, one or more of which may be co-located or distributed and / or may communicate with each other. In some configurations of such a split architecture, the CU may implement some or all of the functionality of the radio resource control (RRC) layer, and the DU may implement some or all of the functionality of the radio link control (RLC) layer.

[0044] Illustratively, some base stations 102 configured for IAB may communicate with DUs of IAB donor nodes or other parent IAB nodes (e.g., base stations) through corresponding CUs, and further, may communicate with child IAB nodes (e.g., other base stations) and / or one or more UEs 104 through corresponding DUs. One or more base stations 102 configured for IAB may be IAB donors connected to at least one of EPC 160 and / or core network 190 through CUs. By doing so, base station(s) 102 operating as IAB donor(s) may provide a link to one of EPC 160 and / or core network 190 for other IAB nodes (which may be direct or indirect (e.g., separated from the IAB donor by more than one hop)) and / or one or more UEs 104 (both of which may communicate with DU(s) of the IAB donor(s)). In some additional aspects, one or more base stations 102 may be configured with connectivity in an open RAN (ORAN) and / or a virtualized RAN (VRAN), which may be achieved via at least one corresponding CU, DU, RU, RRH and / or remote unit.

[0045] The base stations 102 may communicate wirelessly with the UEs 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG).

[0046] The communication link 120 between the base station 102 and the UE 104 may include an uplink (also known as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (also known as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. These communication links may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x CCs) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y megahertz (MHz) (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth. These CCs may or may not be adjacent to each other. The allocation of CCs may be asymmetric with respect to downlink and uplink (e.g., more or fewer CCs may be allocated to downlinks than to uplinks).

[0047] The CC may include a primary CC and one or more secondary CCs. The primary CC may be referred to as a primary cell (PCell), and the secondary CC may be referred to as a secondary cell (SCell). When the UE is known to both a base station at the access network level and to at least one core network entity (e.g., AMF and / or MME) at the core network level, and the UE is configured to receive downlink control information in the access network (e.g., the UE may be in an RRC connected state), the PCell may also be referred to as a serving cell. In some instances where carrier aggregation is configured for the UE, each of the PCell and one or more SCells may be a serving cell.

[0048] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use a downlink / uplink WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0049] The wireless communication system may further include a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152 via a communication link 154, such as in a 5 gigahertz (GHz) unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0050] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0051] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, although unlike the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” (mmW) band by the International Telecommunication Union (ITU), FR2 is typically (interchangeably) referred to as “millimeter wave” (or “mmWave” or simply “mmW”) in various documents and articles.

[0052] In view of the above aspects, unless otherwise specifically stated, if used in this document, the term "sub-6 GHz" and the like may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if used in this document, the term "millimeter wave" and the like may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0053] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave frequencies or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.

[0054] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0055] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming (PSS) service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0056] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides quality of service (QoS) flows and session management. All user IP packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0057] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (although some aspects of a TRP may not include the complete circuitry of a base station), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0058] Reference again Figure 1In certain aspects, the UE 104 may be configured to receive information indicating beam sets associated with a plurality of CCs from the base station 102 / 180. The UE 104 may be further configured to activate the beam sets on the plurality of CCs for sTRP or for mTRP, the beam sets being activated for sTRP when less than two beam IDs respectively associated with the beam sets are mapped to code points and less than two pool indexes are configured for CORESETs associated with at least one CC of the plurality of CCs. The information indicating the beam sets associated with the plurality of CCs may be a group beam update 198. The group beam update 198 may indicate the beam sets to be activated on the plurality of CCs for the UE 104.

[0059] In some aspects, a beam set may be activated for mTRP when at least one of the following is true: a codepoint is mapped to two or more beam IDs, or the CORESET is configured with two or more pool indices or is configured with no pool index.

[0060] On the other hand, the base station 102 / 180 can configure a beam set on multiple CCs for sTRP or for mTRP, and the beam set is configured for sTRP when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for CORESET associated with at least one CC of the multiple CCs. The base station 102 / 180 can be further configured to transmit information indicating the beam sets associated with the multiple CCs to the UE 104. For example, the base station 102 / 180 can transmit a group beam update 198 to the UE 104, for example, to instruct the UE 104 which beams are to be used for communication on which CCs.

[0061] Various aspects of beam management for UEs with sTRPs, mTRPs, and combinations thereof are further described herein. The various aspects can be implemented in various wireless and / or access networks to facilitate carrier aggregation and other operations occurring on multiple CCs.

[0062] Although the present disclosure may focus on 5G NR, the concepts and aspects described herein may be applicable to other similar areas such as LTE, Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), or other wireless / radio access technologies.

[0063] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of downlink channels within a 5G NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D 280 is a diagram illustrating an example of an uplink channel within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to either the downlink or the uplink; or can be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to both the downlink and the uplink. Figure 2A , 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly downlink) and subframe 3 is configured with slot format 34 (mostly uplink), where D is downlink, U is uplink, and F is for flexible use between downlink / uplink. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full downlink and full uplink, respectively. Other slot formats 2-61 include a mix of downlink, uplink, and flexible symbols. The UE is configured with a slot format (dynamically configured by downlink control information (DCI) or semi-statically / statically configured by RRC signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure for TDD.

[0064] Other wireless communication technologies may have different frame structures and / or different channels. A frame (e.g., a 10 millisecond (ms) frame) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the downlink may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the uplink may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μtime slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15 kilohertz (kHz), where μ is parameter design 0 to 4. Thus, parameter design μ=0 has a subcarrier spacing of 15 kHz, while parameter design μ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example of slot configuration 0 and parameter design μ=2 with 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs). Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter design.

[0065] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0066] like Figure 2A As illustrated in FIG. 1 , some REs carry at least one pilot and / or reference signal (RS) for the UE. In some configurations, the RS may include at least one demodulation RS (DM-RS) (indicated as R for a particular configuration) for channel estimation at the UE. x , where 100x is the port number, but other DM-RS configurations are possible) and / or at least one channel state information (CSI) RS (CSI-RS). In some other configurations, the RS may additionally or alternatively include at least one beam measurement (or management) RS (BRS), at least one beam refinement RS (BRRS) and / or at least one phase tracking RS (PT-RS).

[0067] Figure 2BExamples of various downlink channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including 9 RE groups (REGs), each REG including 4 consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a CORESET. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH (such as the system information block (SIB)), and paging messages.

[0068] As in Figure 2C As explained in , some REs carry DM-RSs for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the comb teeth. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the uplink.

[0069] Figure 2DExamples of various uplink channels within a subframe of a frame are illustrated. The PUCCH may be located at a location as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request (SR), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0070] Figure 3 3 is a block diagram of a base station 310 and a UE 350 in communication in an access network. In the downlink, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 2 (L2) and layer 3 (L3) functionality. The L3 includes the RRC layer, and the L2 includes the service data adaptation protocol (SDAP) layer, the packet data convergence protocol (PDCP) layer, the RLC layer, and the media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0071] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 (L1) functionality associated with various signal processing functions. The L1 including the physical (PHY) layer may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0072] At the UE 350, each receiver 354RX receives a signal through a corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement L1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 that implements L3 and L2 functionality.

[0073] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the uplink, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0074] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0075] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0076] The uplink transmission is processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through a corresponding antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0077] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the uplink, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0078] In some aspects, at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The Group Beam Update 198 combines various aspects.

[0079] In some other aspects, at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The Group Beam Update 198 combines various aspects.

[0080] Figure 4 4 is a call flow diagram illustrating example operations in an example access network 400. The example access network 400 may include a base station 402 (e.g., a gNB) and a UE 404. The base station 402 may provide a serving cell and / or PCell on which the UE 404 operates. According to various aspects, the base station 402 may assign a CC group to the UE 404. For example, the base station 402 may assign a CC group to the UE 404 by transmitting an applicable CC list to the UE 404 via RRC signaling.

[0081] The access network 400 may further include a set of TRPs 406, 408, each of which may be a picocell, a femtocell, an RRH, a smart radio head, a CU, a DU, a RU, and / or a remote unit, some or all of which may be co-located or distributed, and / or may communicate with each other or with other cells or carriers connected to the access network 400 including a gNB (e.g., base station 402). Potentially, a TRP may be included in a cell of a base station - for example, a TRP may effectively serve as an antenna panel for a base station and, in some instances, communicate on the same CC(s). In many instances, a TRP may be configured to provide at least one CC to a UE. The set of CCs assigned to a UE may be configured via an sTRP or an mTRP.

[0082] When the base station 402 may be a TRP, the base station 402 may provide a PCell and / or a serving cell, and each of the TRPs 406, 408 may be configured as an SCell for the UE 404. For example, the base station 402 may be able to configure one or more CCs in a CC group assigned to the UE 404 through one or more of the TRPs 406, 408.

[0083] In some aspects, each CC in the CC group may include a BWP, such as a downlink BWP. One or more (e.g., all) of the CCs may be configured with a corresponding CORESET, for example, on which some DCI regarding the corresponding CC(s) may be carried. These CCs may be assigned for carrier aggregation, which may be intra-band carrier aggregation and / or (if supported) inter-band carrier aggregation.

[0084] In some other aspects, the base station 402 can assign CC groups to the UE 404 for uplink communications. The base station 402 can assign CC groups based on a certain band configuration - for example, the base station 402 can activate BWP, some of these band configurations can be TDD (e.g., n30, n41, etc.), while other band configurations can be FDD (e.g., n3, n8, etc.). The UE 404 can transmit SRS on the CC group (see, e.g., Figure 2C ). The UE 404 may transmit the SRS aperiodically and / or semi-periodically.

[0085] The UE 404 and the base station 402 may communicate on the CC using directional beamforming—e.g., the UE 404 may generate beams 414a-d, which may be paired with beams 412a, 412b generated by the base station 402 and / or one or more beams 412c, 412d generated by one or more TRPs 406, 408, respectively. The base station 402 may configure the beams used by the UE 404. For example, the base station 402 may transmit information (e.g., a beam identifier and / or a beam index) to the UE 404 indicating the beams to be applied (e.g., activated, updated, etc.) by the UE 404.

[0086] In some aspects, the base station 402 may indicate one of the beams 412a-d to be paired with one of the UE beams 414a-d at the UE 404 for downlink communication by indicating a transmission configuration indication (TCI) state identifier (ID), which may be interpreted as and / or may correspond to a beam ID. The base station 402 may configure different TCI state IDs for different types of communications for the UE 404. For example, the base station 402 may configure a respective TCI state ID for each CORESET corresponding to each CC / BWP configured for the UE 404. The base station 402 may indicate the TCI state ID in a MAC control element (CE) and / or in at least one RRC message.

[0087] In some other aspects, the base station 402 may indicate one of the beams 412a-d to be paired with one of the UE beams 414a-d and applied for uplink communications by the UE 404 by setting a value of a spatial relationship information field (e.g., an information element labeled “SpatialRelationInfo”). The UE 404 may use the value of the spatial relationship information field to determine the corresponding one of the beams 414a-d (such as by determining an index or ID corresponding to the indicated one of the beams 414a-d).

[0088] In some aspects, the base station 402 may configure one beam for all CCs in a CC group assigned to the UE 404, which may be referred to as group CC based beam updating. For example, the base station 402 may set a value indicating a TCI state ID or spatial relationship information for a first CC in a MAC CE or an information element, and the base station 402 may indicate that the value of the TCI state ID or spatial relationship information is further applicable to each of the other CCs in the CC group.

[0089] Potentially, the base station 402 may configure the beam by identifying a TCI state and / or a quasi co-located (QCL) (or quasi co-located) type and selecting the TCI state and / or QCL type. For example, when a TCI state ID is activated for a CORESET by a MAC CE for at least a CC / BWP set of the same frequency band (the applicable list of CCs is indicated by RRC signaling), the TCI state ID may be applied to the CORESET(s) with the same CORESET ID for all BWPs in the CC indicated on the list. The CORESET ID, which may be signaled in the information element ControlResourceSetID, may be used to identify a CORESET within a cell or CC - for example, a CORESET ID of 0 may identify a control resource set #0 configured via PBCH (MIB) and controlResourceSetZero (ServingCellConfigCommon). The ID space may be used across BWPs of a cell or CC.

[0090] In some aspects, DCI on a CORESET for the base station 402 and / or at least one of the TRPs 406, 408 may be found via one of the beams 412a-d in association with a pool index. The UE 404 may receive such a CORESET, where one of the beams 414a-d is paired with one of the beams 412a-d. The pool index may indicate a mapping between an activated TCI state (e.g., beam) for the CORESET and a code point included in the DCI. Thus, the UE 404 may be configured with at least one pool index (e.g., configured by the base station 402), the signaling of which may be index-based to enable the UE 404 to find and decode the CORESET.

[0091] In some examples, the base station 402 may use a single MAC CE to activate the same TCI state ID for a downlink control channel (e.g., PDCCH) for multiple CCs / BWPs. In a further example, when spatial relationship information is activated for semi-periodic / aperiodic SRS resources by a MAC CE for at least a set of CCs / BWPs of the same frequency band (the applicable list of CCs is indicated by RRC signaling), the spatial relationship information may be applied to the semi-periodic / aperiodic resource(s) with the same SRS resource ID for all BWPs in the CC indicated on the list.

[0092] In some aspects, the base station 402 may indicate to the UE 404 a mapping of at least one TCI state ID to a set of code points in the DCI using a MAC CE of one message. The code point may be the value of the TCI field in the DCI. For example, the number of TCI state IDs that may be configured for the UE 404 (e.g., 128 TCI state IDs for receiving the PDSCH) may exceed the capacity of the DCI message, and therefore, the base station 402 may indicate that each code point in the DCI message corresponds to at least one corresponding TCI state ID using a MAC CE of one message. However, for example, when a CC group is configured on an mTRP, each code point may be able to be mapped to two TCI state IDs.

[0093] Because each of the TRPs 406, 408 may include a respective antenna array for beamforming, the UE 404 may apply different beams 412c, 412d to communicate with different ones of the TRPs 406, 408 and the base station 402. In other words, the UE 404 may use different ones of the beams 414a-d to direct communications in a direction appropriate for one of the TRPs 406, 408 or the base station 402 with which the UE 404 is communicating.

[0094] Since the UE 404 may apply different beams to communicate with different ones of the TRPs 406, 408, the UE 404 may not be able to apply the same beam to all CCs in the group assigned to the UE 404 when one or more of those CCs are configured by a different TRP 406, 408 than the base station 402. In other words, the UE 404 may be configured to update the beams used for the assigned CC group when the assigned CC group is configured on the sTRP (e.g., the base station 402). However, the UE 404 may not be configured to update the beams used for the assigned CC group when the assigned CC group is configured on the mTRP (e.g., on the TRPs 406, 408).

[0095] When the base station 402 is configuring a beam for the UE 404, the base station 402 may determine whether to configure an sTRP or an mTRP for the UE 404 on the assigned CC group (420). When all assigned CCs are configured on the sTRP, the base station 402 may transmit only group CC-based beam updates for all assigned CCs to the UE 404. However, if the assigned CCs are configured on the mTRP, the base station 402 may configure a corresponding beam for each CC.

[0096] In the illustrated aspect, base station 402 can configure group CC based beam updates (422) for UE 404. That is, base station 402 can configure a beam for one CC in the assigned CC group, and base station 402 can configure communications on all other CCs in the group to use the same beam.

[0097] In some aspects, the base station 402 may configure group CC-based beam updating for downlink data on a downlink data channel (e.g., PDSCH). In some other aspects, the base station 402 may configure group CC-based beam updating for downlink control information on a downlink control channel (e.g., PDCCH). In yet other aspects, the base station 402 may configure group CC-based beam updating for semi-periodic / aperiodic SRS transmitted by the UE 404. In yet further aspects, the base station 402 may configure group CC-based beam updating for a combination of two or more of downlink control information, downlink data, aperiodic SRS, and / or semi-periodic SRS.

[0098] In order for the CC group to be configured on the sTRP, the CORESET pool index for each CORESET in the CORESET set may be configured with less than two indices (e.g., one index or no index). In some further aspects, each codepoint in the set of codepoints (e.g., mapped to a TCI state ID corresponding to a beam as indicated by the DCI) may correspond to (e.g., mapped to) less than two TCI state IDs (e.g., a mapping included in a MAC CE for UE 404 may map each codepoint in the set of codepoints indicated therein to zero or one TCI state ID).

[0099] In addition, the base station 402 can configure each code point in the set of code points to be mapped to a corresponding TCI state ID in the DCI for the UE 404. Since the base station 402 can configure the group CC-based beam update for the UE 404, the base station 402 can configure each code point to be mapped to only a single TCI state ID. In some other aspects, the base station 402 can configure one or more of the code points to be mapped to a corresponding plurality of TCI state IDs, each of which can correspond to one of the beams 412a-d at the base station 402 and / or the mTRPs 406, 408.

[0100] The base station 402 may transmit first control information 424 indicating the CORESET set, and further, may transmit second control information 426 indicating a set of code points in the DCI that are respectively associated with a single TCI state ID. In some aspects, the base station 402 may transmit the first control information 424 via RRC signaling, and may transmit the second control information 426 in at least one MAC CE.

[0101] Additionally, the base station 402 may transmit a group CC based beam update 428 to the UE 404. In some aspects, the group CC based beam update 428 may be included in at least one MAC CE and / or RRC message.

[0102] UE 404 may receive first control information 424 (e.g., via RRC signaling) and second control information 426 (e.g., in at least one MAC CE). Based on this, UE 404 may determine whether a single TRP or an mTRP is configured for communication on the assigned CC group (430). UE 404 may determine that the first control information 424 indicates less than two pool indexes (i.e., zero or one index) associated with a CORESET in all CORESETs in the CORESET set configured in the CC / BWP assigned to UE 404. For example, all CORESETs given to UE 404 may be configured with the same value of the CORESET pool index. In another example, all or some of the CORESETs given to UE 404 may be configured without a CORESET pool index. UE 404 may also determine that the second control information 426 indicates that each codepoint in the codepoint set in the DCI maps to a corresponding single TCI state ID. In some aspects, each of the TCI state IDs may correspond to a beam in a beam set for communication on the CC, and a code point may be mapped to a subset of the beam set, where each subset includes less than two beams (i.e., less than two TCI state IDs) when the sTRP is configured for communication on the assigned CC.

[0103] If either of the above two conditions is not met, the UE 404 may determine that the CC group is configured on the mTRP. That is, when the first control information 424 indicates two or more pool indices associated with a CORESET in the CORESET set and / or the second control information 426 indicates that at least one code point in the code point set is mapped to more than one (e.g., two) TCI state IDs included in the DCI, the UE 404 may determine that the CC group is configured on the mTRP. For example, each of the TCI state IDs may correspond to a beam in a beam set for communication on a CC, wherein one code point is mapped to a subset of two or more beams (i.e., two or more TCI state IDs) of the beam set when the mTRP is configured for communication on the assigned CC.

[0104] UE 404 may further receive a group CC based beam update 428. UE 404 may determine that a CC group is assigned on a single TRP, and therefore, UE 404 may apply the beam to each CC in the assigned CC group (432).

[0105] In a first aspect, the group CC based beam update 428 may configure a beam for downlink control information on a downlink control channel (e.g., PDCCH). In such aspect, if the number of up to two cell lists for simultaneous TCI state activations is provided to the UE 404 by the simultaneousTCI-CellList through the simultaneousTCI-UpdateList-r16 and / or simultaneousTCI-UpdateListSecond-r16, the UE 404 applies the antenna port quasi-colocation provided by the TCI state with the same activation tci-StateID value to the CORESET with index p in all configured DL BWPs of all configured cells in the list determined according to the serving cell index provided by the MAC CE command. The simultaneousTCI-CellList can be provided for simultaneous TCI state activation only if different values ​​of CORESETPoolIndex in ControlResourceSets are not provided to UE 404 and at least one TCI codepoint mapped with two TCI states is not provided to UE 404.

[0106] Further to the first aspect, when UE 404 has applied a beam to an assigned CC group on a downlink control channel (eg, PDCCH), UE 404 may receive downlink control information 434 on the downlink control channel via one of beams 414a-d activated by group CC based beam update 428.

[0107] In a second aspect, the group CC based beam update 428 may configure a beam for downlink data on a downlink data channel (e.g., PDSCH). In such an aspect, the UE 404 may receive the group CC based beam update 428 as an activation command for mapping up to eight TCI states to code points of the DCI field "Transmission Configuration Indication" in one CC / DL BWP or in a CC / DL BWP set, respectively. When a TCI state ID set is activated for a CC / DL BWP set (where the applicable list of CCs is determined by the indicated CC in the activation command), the same TCI state ID set is applied to all DL BWPs in the indicated CC. The TCI state ID set may be activated for a CC / DL BWP set only if different values ​​of CORESETPoolIndex in ControlResourceSets are not provided to the UE 404 and at least one TCI code point mapped to two TCI states is not provided to the UE 404.

[0108] Further to the second aspect, when UE 404 has applied a beam to the assigned CC group on a downlink data channel (e.g., PDSCH), UE 404 can receive downlink data 436 on the downlink data channel via one of beams 414a-d activated by group CC based beam update 428.

[0109] In a third aspect, group CC based beam update 428 may configure beams for semi-periodic / aperiodic SRS. In such aspect, when spatialRelationInfo (spatial relationship information) is activated / updated by a MAC CE for a CC / BWP set for a semi-persistent or aperiodic SRS resource configured by a higher layer parameter SRSResource (where the applicable list of CCs is indicated by a higher layer parameter simultaneousSpatial-UpdatedList-r16 or simultaneousSpatial-UpdatedListSecond-r16), spatialRelationInfo is applied to the semi-persistent or aperiodic SRS resource(s) with the same SRS resource ID for all BWPs in the indicated CC. The spatialRelationInfo for a semi-persistent or aperiodic SRS resource configured by the higher layer parameter SRSResource can be activated / updated by a MAC CE for a CC / BWP set only if a different value of CORESETPoolIndex in ControlResourceSets is not provided to the UE 404 and at least one TCI code point mapped to two TCI states is not provided to the UE 404.

[0110] Further to the third aspect, when the UE 404 has applied a beam to the assigned CC group, the UE 404 may transmit semi-periodic / aperiodic SRS(es) on the SRS resource(s) via one of the beams 414a-d activated by the group CC based beam update 428.

[0111] Figure 5 is a flow chart of an example wireless communication method 500. The method may be performed by a UE (e.g., UE 104, 350, 404), an apparatus (e.g., device 702), and / or another component or device at a UE. According to different aspects, one or more of the illustrated operations may be swapped, omitted, and / or performed concurrently.

[0112] At 502, the UE may receive first control information associated with a CORESET. The UE may receive the first control information via RRC signaling. The first control information may indicate a number of pool indexes associated with at least one CORESET, which may be resource pools in which the CORESET may be found. The information associated with the CORESET may indicate zero, one, or more than one pool index associated with the CORESET for each CORESET of the set.

[0113] exist Figure 4 In the context of, for example, UE 404 may receive first control information 424 from base station 402. For example, the first control information may include information identifying at least one of a CORESET ID, a BWPID where the CORESET may be found, and / or a CORESET pool index(es) corresponding to the CORESET ID.

[0114] At 504, the UE may receive second control information indicating a set of code points associated with at least one corresponding TCI state ID included in the third control information. For example, the second control information may indicate a mapping of a set of code points to a set of IDs (e.g., TCI state IDs) corresponding to a beam set. Based on the second control information, the UE may be able to determine the number of IDs mapped to each code point. In some aspects, one or more of the code points may be mapped to less than two TCI state IDs. In some other aspects, one or more of the code points may be mapped to two or more TCI state IDs. For example, a code point may correspond to two (or more) TCI state IDs, and potentially, those two or more TCI state IDs may identify corresponding beams at two (or more) TRPs. The second control information may be received in at least one MAC CE. In some other aspects, the second control information may be received before, after, or concurrently with the first control information.

[0115] exist Figure 4In the context of, for example, the UE 404 may receive second control information 426 from the base station 402. The second control information 426 may indicate a mapping of a set of code points to a set of IDs (eg, corresponding to a set of beams).

[0116] At 506, the UE may receive information indicating beams associated with communications on multiple CCs. For example, the aforementioned first and second control information may configure the UE to receive DCI in a first CORESET set, for example, from an sTRP or mTRP, and the UE may subsequently receive an information update, wherein the UE will receive DCI, for example, from the same or different sTRP or mTRP. In one aspect, the information indicating beams associated with communications on multiple CCs may be information indicating a beam set associated with a CC set. The information may be configured by a base station for the UE, for example, for carrier aggregation on multiple CCs provided by multiple beams. The UE may receive information indicating beams in a DCI (e.g., on a PDCCH) or in a MAC CE. The information indicating beams associated with communications on multiple CCs may be received separately from the aforementioned first and second control information.

[0117] exist Figure 4 In the context of, for example, UE 404 may receive a group CC-based beam update 428 from base station 402. Update 428 may indicate a set of one or more of beams 412a-d associated with a set of CCs. For example, each CC may be available through base station 402 and / or at least one of TRPs 406, 408.

[0118] At 508, the UE may determine whether a single TRP or an mTRP is configured for communication on the multiple CCs. For example, if any of the code points is mapped to more than one beam, the UE may determine that the mTRP is configured for the UE. Similarly, if each CORESET is configured with at most one pool index, the UE may determine that the sTRP is configured for the UE. If the UE determines that any of the foregoing conditions is false - i.e., if a code point is mapped to more than one TCI state ID and / or if a CORESET is configured with more than one pool index - the UE may determine that the mTRP is configured for the UE.

[0119] exist Figure 4In the context of, for example, UE 404 may determine whether one or both of TRPs 406, 408 are configured for communication on a CC group (430). If one but not all of TRPs 406, 408 are configured on a CC on which UE 404 may communicate, UE 404 may be obligated to monitor DCI in the CORESET from all TRPs 406, 408. If all TRPs 406, 408 are configured on a CC on which UE 404 may communicate, UE 404 may be obligated to monitor DCI in the CORESET from all TRPs 406, 408.

[0120] To determine whether a single TRP or an mTRP is configured for communication on the multiple CCs, at 510, the UE may determine whether less than two (i.e., zero or one) pool indexes associated with the CORESET are configured for each CORESET in the CORESET set. The UE may calculate the number of pool indexes for the CORESET, for example, based on the first control information, and the UE may compare the number with a threshold of one (1) to determine whether the number is less than two. For example, the UE may determine whether less than two pool indexes are associated with each CORESET found on a corresponding one of the CCs in the CC group. Reference Figure 4 , the UE 404 may determine whether the first control information 424 indicates that less than two pool indexes associated with the CORESET are configured for each CORESET in the CORESET set of the CC / BWP.

[0121] At 512, the UE may determine whether each code point in the second control information is associated with a single TCI state ID of the third control information. For example, the UE may identify whether each code point in the control information maps to one TCI state ID in the DCI or two TCI state IDs in the DCI. The UE may calculate the number of TCI state IDs to which each code point is mapped, for example, based on the second control information, and the UE may compare the number to a threshold value equal to one (1) to determine whether the number of IDs to which the code point is mapped is less than two. Reference Figure 4 , the UE 404 may determine whether the second control information 426 indicates whether each code point is mapped to a single TCI state ID in the DCI or to two TCI state IDs in the DCI.

[0122] If the UE determines at 510 that less than two (ie, zero or one) pool indexes associated with the CORESET are configured for each CORESET in the CORESET set, and determines at 512 that each code point in the second control information is mapped to a single TCI state ID of the third control information, the UE may determine that the sTRP is configured for communication on the plurality of CCs. The UE may perform the following operations at 514 and 516:

[0123] At 514, the UE may apply the beam to communications on the multiple CCs. For example, the UE may activate the beam set for an sTRP on the CC set based on a subset of the beam set to which the codepoint is mapped or a pool index number of a CORESET configured for association with at least one CC in the CC set. In some aspects, applying and / or activating may include: identifying at least one pilot signal quasi-co-located with the beam; measuring or detecting one or more parameters associated with the pilot signal; and selecting a spatial filter for the beam that steers the beam in a direction substantially similar to the direction of the QCL pilot signal. Communications on multiple CCs may include semi-periodic / aperiodic SRS(es), downlink data on a downlink data channel (e.g., PDSCH), or downlink control information on a downlink control channel (e.g., PDCCH).

[0124] exist Figure 4 In the context of, for example, the UE 404 may apply one of the beams 414a-d corresponding to the beam update 428 to receive downlink control information 434 on a downlink control channel, to receive downlink data 436 on a downlink data channel, or to transmit (s) semi-periodic / aperiodic SRS 438.

[0125] At 516, the UE may communicate with the sTRP on at least one of the multiple CCs via the applied beam. In some aspects, the UE may receive downlink data or control information from the sTRP on at least one of the multiple CCs via the applied beam. For example, the UE detects signaling on the PDCCH CORESET for one CC of the multiple CCs for the sTRP. The UE may decode the signaling carried thereon to obtain a DCI that may schedule downlink data on the PDSCH from the sTRP. The UE may then use the scheduling to receive downlink data from the sTRP on the PDSCH. Figure 4In the context of, for example, the UE 404 may apply at least one of the beams 414a-d corresponding to one of the beams 412a-d indicated by the beam update 428 to at least one of: receiving downlink control information 434 on a downlink control channel from the base station 402, the first TRP 406, or the second TRP 408 and / or receiving downlink data 436 on a downlink data channel from the base station 402, the first TRP 406, or the second TRP 408.

[0126] In some other aspects, when the UE applies or activates a beam on one of the multiple CCs for an sTRP, the UE may be configured to sound an uplink channel. Thus, the UE may transmit an SRS set on at least one CC in the multiple CCs for an sTRP via a beam. Figure 4 In the context of, for example, UE 404 may apply two of beams 414a-d corresponding to beam(s) 412c-d indicated by beam update 428 to transmit semi-periodic / aperiodic SRS 438 to base station 402 or one of TRPs 406, 408.

[0127] If the UE determines at 510 that two or more pool indexes associated with the CORESET are configured for each CORESET in the CORESET set, and / or determines at 512 that at least one code point in the second control information is mapped to more than one TCI state ID of the third control information, the UE may determine that the mTRP is configured for communication on the multiple CCs. The UE may perform the following operations at 518 and 520:

[0128] At 518, the UE may apply the beam for communications on at most one CC of the plurality of CCs. In some aspects, applying and / or activating may include: identifying at least one pilot signal to be quasi-co-located with the beam; measuring or detecting one or more parameters associated with the pilot signal; and selecting a spatial filter for the beam that steers the beam in a manner substantially similar to that of the pilot signal.

[0129] exist Figure 4 In the context of, for example, the UE 404 may apply two of the beams 414a-d corresponding to the beam update 428 and / or paired with the beam(s) 412c-d to at least one of: receiving downlink control information 434 on a downlink control channel, receiving downlink data 436 on a downlink data channel, or transmitting semi-periodic / aperiodic SRS 438.

[0130] At 520, the UE may communicate with at most one CC among the multiple CCs via the applied beam for each TRP in the mTRP. In some aspects, when the UE applies or activates a beam on one CC among the multiple CCs for a TRP in the mTRP, the UE may receive downlink data or control information from the TRP in the mTRP on the CC among the multiple CCs via the applied beam. For example, the UE detects signaling on a PDCCH CORESET of a CC among the multiple CCs for a TRP in the mTRP. The UE may decode the signaling carried thereon to obtain a DCI that may schedule downlink data on a PDSCH in the CC associated with the TRP. The UE may then use the scheduling to receive downlink data on the PDSCH from the TRP in the mTRP. Figure 4 In the context of, for example, the UE 404 may apply two of the beams 414a-d corresponding to one or both of the base station / TRP beams 412a-d indicated, for example, by the beam update 428 to at least one of: receiving downlink control information 434 on a downlink control channel from each of at least two of the base station 402, the first TRP 406, or the second TRP 408 and / or receiving downlink data 436 on a downlink data channel from each of at least two of the base station 402, the first TRP 406, or the second TRP 408.

[0131] In some other aspects, when the UE applies or activates a beam on one of the multiple CCs for an mTRP, the UE may be configured to sound an uplink channel. Thus, the UE may transmit an SRS set on at most one CC in the multiple CCs for each TRP in the mTRP via the beam. Figure 4 In the context of, for example, the UE 404 may apply two of the beams 414a-d corresponding to the beams 412a-d indicated by the beam update 428 to transmit (s) semi-periodic / aperiodic SRS 438 to each of at least two of the base station 402, the first TRP 406, or the second TRP 408.

[0132] Figure 6 600 is a flow chart of an example wireless communication method. The method may be performed by a base station (e.g., base station 102 / 180, 310, 402), an apparatus (e.g., apparatus 802), and / or another component or device at a UE. According to different aspects, one or more of the illustrated operations may be swapped, omitted, and / or performed concurrently.

[0133] At 602, the base station may configure a CORESET set for the UE. For example, the base station may configure a corresponding CORESET for each CC / BWP assigned to the UE in the CC group. First, the base station may activate the BWP, and second, the base station may select a resource set to carry the PDCCH. The base station may also select an aggregation level. For example, refer to Figure 4 , base station 402 can configure the CORESET set for UE 404.

[0134] At 604, the base station may configure a code point set associated with at least one corresponding TCI state ID included in another control information for the UE. For example, the base station may identify the TCI state set that has been activated, and the base station may map the ID of each TCI state to a code point for the CORESET. For example, referring to Figure 4 , the base station 402 may configure, for the UE 404, a set of code points associated with at least one corresponding TCI state ID included in the DCI.

[0135] At 606, the base station may transmit first control information indicating the CORESET set to the UE. The first information may indicate a pool index set for each CORESET in the CORESET set. The base station may transmit the first control information via RRC signaling. For example, referring to Figure 4 , the base station 402 can transmit the first control information 424 to the UE 404.

[0136] At 608, the base station may transmit to the UE second control information indicating a set of code points associated with at least one corresponding TCI state ID included in the other control information. The base station may transmit the second control information in at least one MAC CE, and the other control information may be a DCI. The second control information may indicate a corresponding subset of the beam set corresponding to each code point. For example, referring to Figure 4 , the base station 402 can transmit the second control information 426 to the UE 404.

[0137] At 610, the base station may determine whether a single TRP or an mTRP is to be configured for communications by the UE on multiple CCs assigned to the UE. For example, the base station may determine whether the UE supports carrier aggregation and whether another TRP is available to provide a set of CCs to be assigned to the UE for carrier aggregation. If the base station determines that the UE does not support carrier aggregation and / or no TRP is available to provide CCs for carrier aggregation, the base station may assign an sTRP to the UE for multiple CCs. If an sTRP is configured, the base station may configure less than two (i.e., zero or one) pool indexes associated with the CORESET for each CORESET in the set of CORESETs indicated in the first control information, and further, each code point in the second control information may be configured to map to a single TCI state ID of an activated beam.

[0138] At 612, if a single TRP is configured (at 610), the base station may configure beams for communication by the UE on multiple CCs. For example, the base station may configure a beam update based on a group CC. The base station may identify a resource set on which a CORESET may be found, and the base station may select a beam to transmit the resource set to the UE. In some aspects, the base station may configure the beam by identifying multiple candidate beams that may be used to communicate with the UE, and the base station may compare corresponding wireless channel measurements corresponding to two or more of the multiple beams to each other to identify the best serving beam for the UE. In some other aspects, the base station may configure the beam by identifying a location or position of the UE (which may be relative to a sTRP) and then selecting a beam having a direction toward the UE location or position. Reference Figure 4 , the base station 402 can configure at least one of the beams 412a-d of the base station 402 and / or (these) TRPs 406, 408, which can be paired with one of the beams 414a-d of the UE 404 to communicate on multiple CCs (422).

[0139] At 614, if a single TRP is configured (at 610), the base station may allocate resources for communication with the UE by the sTRP on at least one CC of the multiple CCs. For example, the base station may schedule or allocate a first set of resources on a downlink data channel to carry downlink data for the UE, and the base station may schedule or allocate a second set of resources on a downlink control channel to carry DCI that notifies the UE of the scheduling of the downlink data.

[0140] refer to Figure 4, the base station 402 may allocate resources on a downlink control channel to carry control information 434 from the base station 402 or at least one of the TRPs 406, 408 on at least one CC. In addition, the base station 402 may allocate resources on a downlink data channel (e.g., PDSCH) to carry downlink data 436 from the base station 402 or at least one of the TRPs 406, 408. The control information 434 may indicate a set of resources on the downlink data channel at which the downlink data 436 may be found.

[0141] However, if mTRP is configured (at 610), the base station may configure two or more pool indexes associated with the CORESET for at least one CORESET in the CORESET set, and / or the base station may configure at least one code point in the second control information to be mapped to two or more TCI state IDs of another control information. Thus, the base station may configure one beam for each different CC available through mTRP.

[0142] At 616, if the mTRP is configured (at 610), the base station may configure a beam for communication by the UE on one of the multiple CCs. For example, the base station may configure an update for each of the multiple CCs on which a corresponding beam may be configured, wherein the corresponding one of the multiple CCs is available through one of the TRPs. For example, the base station may identify a resource set on which a CORESET may be found for each CC in the CC set, and the base station may select a beam to transmit the resource set to the UE. In some aspects, the base station may configure the beam by identifying multiple beams available for communication with the UE at the mTRP, and the base station may compare wireless channel measurements corresponding to the multiple beams, respectively, to determine which of the multiple beams provides the best channel quality (e.g., the highest channel measurement). The base station may select the beam with the best channel quality and utilize the beam to configure the UE to communicate on one of the multiple CCs. In some other aspects, the base station may configure the beam by identifying the location or position of the UE (which may be relative to one of the TRPs in the mTRP) and then selecting a beam of the TRP with a direction toward the UE location or position.

[0143] refer to Figure 4 , base station 402 may configure at least one of beams 412a-d of base station 402 and / or TRP(s) 406, 408. One of beams 412a-d may be used for directional beamforming toward UE 404. In some aspects, one of beams 412a-d may be paired with one of beams 414a-d of UE 404 to communicate with base station 402 or one of TRP(s) 406, 408 on one of the plurality of CCs (422).

[0144] At 618, if the mTRP is configured (at 610), the base station may allocate resources for each of the at least two TRPs of the mTRP to communicate with the UE on at most one CC of the multiple CCs, respectively. For example, the base station may schedule or allocate a first set of resources on a downlink control channel on one CC to carry a first DCI for one TRP of the UE, and allocate a second set of resources on a downlink control channel on another CC to carry a second DCI for another TRP of the UE. The base station may also allocate a third set of resources on a downlink data channel on the CC to carry the first downlink data of the TRP of the UE, and allocate a fourth set of resources on a downlink data channel on the other CC to carry the second downlink data of the other TRP of the UE. The first DCI may be configured to indicate scheduling of first downlink data on the downlink control channel of the CC, and the second DCI may be configured to indicate scheduling of second downlink data on the downlink control channel of the other CC.

[0145] refer to Figure 4 , the base station 402 may allocate resources on a downlink control channel to carry control information 434 from the base station 402 or at least one of the TRPs 406, 408 on at least one CC. In addition, the base station 402 may allocate resources on a downlink data channel (e.g., PDSCH) to carry downlink data 436 from the base station 402 or at least one of the TRPs 406, 408. The control information 434 may indicate a set of resources on the downlink data channel at which the downlink data 436 may be found.

[0146] Upon allocating resources for communicating with the UE by the sTRP on at least one CC in the plurality of CCs or by each of the at least two TRPs of the mTRP on at most one CC in the plurality of CCs, the base station may perform the following operations at 620:

[0147] At 620, the base station may transmit information indicating the beam to the UE. The information indicating the beam may be included in at least one MAC CE. In some aspects, the information may configure the UE to perform directional beamforming on one or more CCs on which the CORESET may be found. In some other aspects, the UE may use the beam to sound on at least one of the CCs. For example, the UE may transmit an uplink SRS on at least one of the CCs toward the base station 402 and / or at least one of the TRPs 406, 408 via the beam. For example, referring to Figure 4 , the base station 402 can transmit the beam update 428 to the UE 404.

[0148] Figure 7700 is a diagram illustrating an example of a hardware implementation of a device 702. The device 702 may be a UE or similar device, or the device 702 may be a component of a UE or similar device. The device 702 may include a cellular baseband processor 704 (also referred to as a modem) and / or a cellular RF transceiver 722, which may be coupled together and / or integrated into the same package or module.

[0149] In some aspects, the device 702 may receive or include one or more subscriber identity module (SIM) cards 720, which may include one or more integrated circuits, chips, or similar circuit systems, and which may be removable or embedded. The one or more SIM cards 720 may carry identification and / or authentication information, such as an International Mobile Subscriber Identity (IMSI) and / or (all) IMSI-related keys. In addition, the device 702 may include one or more of an application processor 706 coupled to a secure digital (SD) card 708 and a screen 710, a Bluetooth module 712, a wireless local area network (WLAN) module 714, a global positioning system (GPS) module 716, and / or a power supply 718.

[0150] The cellular baseband processor 704 communicates with the TRP 180' and / or the base station 102 / 180 through the cellular RF transceiver 722. The cellular baseband processor 704 may include a computer-readable medium / memory. The cellular baseband processor 704 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 704, enables the cellular baseband processor 704 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 704 when executing the software. The cellular baseband processor 704 further includes a receiving component 730, a communication manager 732, and a transmission component 734. The communication manager 732 includes the one or more illustrated components. The components within the communication manager 732 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 704.

[0151] exist Figure 3 In the context of , the cellular baseband processor 704 may be a component of the UE 350 and may include the memory 360 and / or at least one of the following: the TX processor 368, the RX processor 356, and / or the controller / processor 359. In one configuration, the device 702 may be a modem chip and / or may be implemented as the baseband processor 704, while in another configuration, the device 702 may be the entire UE (e.g., Figure 3UE 350) and may include some or all of the above modules, components and / or circuit systems explained in the context of device 702. In one configuration, the cellular RF transceiver 722 may be implemented as at least one of the transceiver 354TX and / or the receiver 354RX.

[0152] The receiving component 730 may be configured to receive signaling on a wireless channel, such as signaling from TRP 180 or TRP 180″. The transmitting component 734 may be configured to transmit signaling on a wireless channel, such as signaling to a base station or TRP 180 or TRP 180″. The communication manager 732 may coordinate or manage some or all wireless communications performed by the device 702, including wireless communications across the receiving component 730 and the transmitting component 734.

[0153] Receiving component 730 may provide some or all data and / or control information included in received signaling to communications manager 732, and communications manager 732 may generate some or all data and / or control information to be included in transmitted signaling and provide such data and / or control information to transmission component 734. Communications manager 732 may include various illustrated components, including one or more components configured to process received data and / or control information, and / or one or more components configured to generate data and / or control information for transmission.

[0154] The communication manager 732 can include, among other things, a map identification component 740, a TRP identification component 742, a beam activation component 744, and a communication component 746. One or more of the foregoing components can be in communication with the receiving component 730 and / or the transmitting component 734.

[0155] The receiving component 730 may be configured to receive first control information indicating at least one beam associated with a plurality of CCs, for example, as described in conjunction with Figure 5 502. The receiving component 730 may receive the first control information via RRC signaling. The first control information may indicate a number of pool indexes associated with at least one CORESET, which may be resource pools in which the CORESET may be found, and / or may indicate a mapping between an activated TCI state (e.g., beam) and a CORESET-specific code point. The information associated with the CORESET may indicate zero, one, or more than one pool index associated with the CORESET for each CORESET of the set.

[0156] The receiving component 730 may be further configured to receive second control information indicating a set of code points associated with at least one corresponding TCI state ID included in the third control information, for example, as combined with Figure 5As described in 504. For example, the second control information may indicate a mapping of a code point set to an ID set (eg, TCI state ID) corresponding to a beam set. The second control information may be received in at least one MAC CE.

[0157] The receiving component 730 may be configured to receive information indicating beams associated with communications on multiple CCs, for example, as described in conjunction with Figure 5 As described in 506 of . For example, the first and second control information can configure the device 702 to receive DCI in the first CORESET set, and the receiving component 730 can then receive the information update of the DCI location. In one aspect, the information indicating the beam associated with the communication on the multiple CCs can be information indicating the beam set associated with the CC set. The information can be configured by the base station, for example, for carrier aggregation on multiple CCs provided by multiple beams.

[0158] The mapping identification component 740 can be configured to determine whether each CORESET in the CORESET set is configured with less than two (ie, zero or one) pool indexes associated with the CORESET, for example, as combined with Figure 5 510. The mapping identification component 740 may calculate the number of pool indexes for CORSET, for example, based on the first control information, and the mapping identification component 740 may compare the number with a threshold value of one (1) to determine whether the number is less than two.

[0159] The mapping identification component 740 may be further configured to determine whether each code point in the second control information is associated with a single TCI state ID of the third control information, for example, as combined with Figure 5 512. For example, the mapping identification component 740 can determine whether one or two TCI state IDs are mapped to a single code point. The mapping identification component 740 can calculate the number of TCI state IDs to which each code point is mapped, for example, based on the second control information, and the mapping identification component 740 can compare the number with a threshold value equal to one (1) to determine whether the number of IDs to which the code point is mapped is less than two.

[0160] The TRP identification component 742 can be configured to determine whether a single TRP or an mTRP 180', 180" is configured for communication on the multiple CCs, for example, as combined Figure 5508 as described. For example, if any of the code points is mapped to more than one beam, the TRP identification component 742 can determine that the mTRP 180', 180" is configured for the device 702. Similarly, if each CORESET is configured with at most one pool index, the TRP identification component 742 can determine that the sTRP 180' is configured for the device 702. If the TRP identification component 742 determines that any of the foregoing conditions is false - that is, if a code point is mapped to more than one TCI state ID and / or if a CORESET is configured with more than one pool index - the TRP identification component 742 can determine that the mTRP 180', 180" is configured for the device 702.

[0161] The beam activation component 744 can be configured to apply the beam to communicate with the sTRP on the multiple CCs when less than two TCI state IDs are mapped to a single code point and less than two pool indexes are configured for the CORESET, for example, as combined with Figure 5 514 described. That is, the beam activation component 744 can activate a beam set on the multiple CCs for sTRP 180' or for mTRP 180', 180", and the beam set is activated for sTRP 180' when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for CORESET associated with at least one CC among the multiple CCs. In some aspects, applying and / or activating a beam may include: identifying at least one pilot signal QCL associated with the beam; measuring or detecting one or more parameters associated with the pilot signal; and selecting a spatial filter for the beam, which causes the beam to steer in a direction substantially similar to the direction of the QCL pilot signal.

[0162] In some aspects, the communication component 746 can be configured to communicate with the sTRP 180' on at least one of the plurality of CCs via the applied beam, for example, as in conjunction with Figure 5 516 described. In some aspects, the communication component 746 can receive downlink data or control information from the sTRP 180' (through the receiving component 730) on at least one of the multiple CCs via the applied beam. For example, the communication component 746 detects signaling on the PDCCH CORESET for one CC of the multiple CCs for the sTRP 180'. The communication component 746 can decode the signaling carried thereon to obtain a DCI, which can schedule downlink data on the PDSCH from the sTRP 180'. Subsequently, the communication component 746 can use the scheduling to receive downlink data from the sTRP 180' on the PDSCH.

[0163] In some other aspects, when the beam activation component 744 applies or activates the beam on one of the multiple CCs for mTRP 180', 180", the communication component 746 can be configured to sound the uplink channel. Therefore, the communication component 746 can transmit the SRS set via the beam on at most one CC in the multiple CCs for each TRP in mTRP 180', 180" (through the transmission component 734).

[0164] In some aspects, the beam activation component 744 can apply the beam for each TRP in the mTRP 180', 180" to communicate with the TRP on only one CC in the multiple CCs. In some aspects, the communication component 746 can be configured to communicate with the TRP on at most one of the multiple CCs via the applied beam for each TRP in the mTRP 180', 180", for example, as combined Figure 5 520 as described. In some aspects, when the beam activation component 744 applies or activates a beam on one of the multiple CCs for a TRP in an mTRP 180', 180", the communication component 746 can receive downlink data or control information from the TRP in the mTRP 180', 180" (through the receiving component 730) on the CC in the multiple CCs via the applied beam. For example, the communication component 746 detects signaling on a PDCCH CORESET of a CC in the multiple CCs for a TRP in an mTRP 180', 180". The communication component 746 can decode the signaling carried thereon to obtain a DCI, which can schedule downlink data on a PDSCH in the CC associated with the TRP. Subsequently, the communication component 746 can use the scheduling to receive downlink data on the PDSCH from the TRP in the mTRP 180', 180".

[0165] In some other aspects, when the beam activation component 744 applies or activates the beam on one of the multiple CCs for mTRP 180', 180", the communication component 746 can be configured to sound the uplink channel. Therefore, the communication component 746 can transmit the SRS set via the beam on at most one CC in the multiple CCs for each TRP in mTRP 180', 180" (through the transmission component 734).

[0166] Device 702 may include executing Figure 4 and 5 Some or all of the additional components of the blocks, operations, signaling, etc. of the algorithm(s) in the aforementioned call flow diagram and / or flowchart. Thus, Figure 4 and 5Some or all of the blocks, operations, signaling, etc. in the aforementioned call flow diagrams and flowcharts may be performed by a component and the device 702 may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0167] In one configuration, the device 702, and in particular the cellular baseband processor 704, includes: a device for receiving information indicating a beam set associated with multiple CCs; and a device for activating the beam set on the multiple CCs for a single sTRP or for an mTRP, the beam set being activated for the sTRP when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a CORESET associated with at least one CC among the multiple CCs.

[0168] In one configuration, a beam set is activated for mTRP when at least one of the following is true: a codepoint is mapped to two or more beam IDs, or the CORESET is configured with two or more pool indices or is not configured with a pool index.

[0169] In one configuration, the device for activating the beam set is configured to: activate at least one beam in the beam set on at least two CCs among the multiple CCs for sTRP, or activate each beam in the beam set on at most one CC among the multiple CCs for mTRP.

[0170] In one configuration, the device 702, and in particular the cellular baseband processor 704, may further include: a device for receiving at least one MAC CE separately from information indicating a beam set associated with the multiple CCs, the at least one MAC CE indicating a mapping of each code point in the code point set to a corresponding beam ID set; and a device for identifying a beam in the beam set based on the mapping of each code point in the code point set to a corresponding beam ID set.

[0171] In one configuration, the device 702, and in particular the cellular baseband processor 704, may further include: a device for receiving at least one RRC message separately from information indicating a beam set associated with the multiple CCs, the at least one RRC message indicating a pool index configured for the CORESET; and a device for identifying, based on the pool index and based on a codepoint, a CORESET associated with the sTRP for which the beam is activated on one CC among the multiple CCs.

[0172] In one configuration, the device 702, and in particular the cellular baseband processor 704, may further include: a device for decoding information on at least one CC associated with the CORESET for an sTRP in a plurality of CCs or on at least two CCs associated with at least two CCs respectively for at least two TRPs in an mTRP in a plurality of CCs.

[0173] In one configuration, the device 702, and in particular the cellular baseband processor 704, may further include: a device for transmitting an SRS set to an sTRP via at least one beam in the beam set or to an mTRP via the beam set on at least one CC among the multiple CCs.

[0174] In one configuration, the device 702, and in particular the cellular baseband processor 704, may further include: a device for receiving downlink data or control information from an sTRP via at least one beam in the beam set or from an mTRP via each beam in the beam set on the multiple CCs.

[0175] In one configuration, information indicating beam sets associated with the plurality of CCs is included in at least one of a DCI or a MAC CE.

[0176] The aforementioned means may be one or more of the aforementioned components in the device 702 configured to perform the functions recited by the aforementioned means. As described above, the device 702 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0177] Figure 8 8 is a diagram 802 illustrating an example of a hardware implementation of device 800. Device 802 may be a base station or similar device or system, or device 802 may be a component of a base station or similar device or system. Device 802 may include a baseband unit 804. Baseband unit 804 may communicate via a cellular RF transceiver. For example, baseband unit 804 may communicate with UE 104 (such as for downlink and / or uplink communications) and / or communicate with a TRP or other base station (such as for IAB) via a cellular RF transceiver.

[0178] The baseband unit 804 may include a computer-readable medium / memory. The baseband unit 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 804, enables the baseband unit 804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 804 when executing the software. The baseband unit 804 further includes a receiving component 830, a communication manager 832, and a transmission component 834. The communication manager 832 includes the one or more illustrated components. The components within the communication manager 832 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 804. The baseband unit 804 may be a component of the base station 310 and may include a memory 376 and / or at least one of the following: a TX processor 316, an RX processor 370, and a controller / processor 375.

[0179] The receiving component 830 may be configured to receive signaling on a wireless channel, such as signaling from a UE 104 or a TRP (e.g., an sTRP or an mTRP). The transmitting component 834 may be configured to transmit signaling on a wireless channel, such as signaling to a UE 104 or a TRP. The communication manager 832 may coordinate or manage some or all wireless communications performed by the device 802, including wireless communications across the receiving component 830 and the transmitting component 834.

[0180] Receiving component 830 may provide some or all of the data and / or control information included in the received signaling to communication manager 832, and communication manager 832 may generate some or all of the data and / or control information to be included in the transmitted signaling and provide such data and / or control information to transmission component 834. Communication manager 832 may include various illustrated components, including one or more components configured to process received data and / or control information, and / or one or more components configured to generate data and / or control information for transmission. In some aspects, the generation of data and / or control information may include packetizing or otherwise reformatting data and / or control information received from a core network, such as core network 190 or EPC 160, for transmission.

[0181] The communication manager 832 includes an indexing component 840, a codepoint mapping component 842, a beam updating component 844, and a scheduling component 846. One or more of the foregoing components may be configured to transmit and / or receive signaling via the transmission component 834 and the reception component 830, respectively.

[0182] The index component 840 can configure a corresponding CORESET for each CC / BWP assigned to the UE 104 in the CC group, for example, as combined with Figure 6As described in 602. First, the index component 840 can activate the BWP, and second, the index component 840 can select a resource set to carry the PDCCH. The index component 840 can also select an aggregation level.

[0183] The code point mapping component 842 can configure the UE 104 with a set of code points associated with at least one corresponding TCI state ID included in another control information, for example, as combined with Figure 6 604. For example, the code point mapping component 842 can identify the set of TCI states that have been activated, and the code point mapping component 842 can map the ID of each TCI state to a code point for the CORESET.

[0184] In some aspects, the index component 840 may configure one or more pool indexes for a CORESET, e.g., based on a codepoint. The pool index may indicate a mapping between an activated TCI state (e.g., beam) and a CORESET-specific codepoint (e.g., in a DCI). The pool index may be configured as one (1) to indicate an application of downlink transmissions scheduled by a CORESET having a CORESET Pool ID equal to one (1). In some other aspects, the pool index is not configured for any CORESET.

[0185] Transmitting component 834 can transmit first control information indicating a CORESET set to UE 104, for example, as combined with Figure 6 As described in 606. The first information may indicate a pool index set for each CORESET in the CORESET set. The transmission component 834 may transmit the first control information via RRC signaling.

[0186] Transmitting component 834 can transmit to UE 104 second control information indicating a set of code points associated with at least one corresponding TCI state ID included in another control information, e.g., as combined with Figure 6 As described in 608. The transmission component 834 can transmit the second control information in at least one MAC CE, and the other control information can be DCI. The second control information can indicate the corresponding subset of the beam set corresponding to each code point.

[0187] The beam updating component 844 can determine whether a single TRP or an mTRP is to be configured for communication by the UE 104 on multiple CCs assigned to the UE 104, for example, as combined Figure 6610 described. For example, the beam update component 844 can determine whether the UE 104 supports carrier aggregation and whether another TRP is available to provide a set of CCs to be assigned to the UE for carrier aggregation. If the beam update component 844 determines that the UE 104 does not support carrier aggregation and / or no TRP is available to provide CCs for carrier aggregation, the beam update component 844 can assign an sTRP to the UE 104 for multiple CCs. If the sTRP is configured, the index component 840 can configure less than two (i.e., zero or one) pool indexes associated with the CORESET for each CORESET in the set of CORESETs indicated in the first control information, and further, each code point in the second control information can be configured to map to a single TCI state ID of the activated beam.

[0188] If sTRP is configured, beam updating component 844 can configure beams for communication by UE 104 on the plurality of CCs, e.g., as in conjunction with Figure 6 612. For example, the beam update component 844 can configure a group CC based beam update. The beam update component 844 can identify a resource set on which a CORESET can be found, and the beam update component 844 can select a beam to transmit the resource set to the UE 104. In some aspects, the beam update component 844 can configure the beam by identifying a plurality of candidate beams that can be used to communicate with the UE 104, and the beam update component 844 can compare respective wireless channel measurements corresponding to two or more of the plurality of beams with each other to identify the best serving beam for the UE 104. In some other aspects, the beam update component 844 can configure the beam by identifying a location or position of the UE 104 (which can be relative to the sTRP) and then selecting a beam having a direction toward the location or position of the UE 104.

[0189] If the sTRP is configured, the scheduling component 846 can allocate resources for the sTRP to communicate with the UE 104 on at least one CC of the plurality of CCs, for example, as described in conjunction with Figure 6 614. For example, the scheduling component 846 can schedule or allocate a first set of resources on a downlink data channel to carry downlink data for the UE 104, and the scheduling component 846 can schedule or allocate a second set of resources on a downlink control channel to carry a DCI that notifies the UE 104 of the scheduling of the downlink data.

[0190] The beam updating component 844 can configure a beam for communication by the UE 104 with a TRP in the mTRP on a CC in the plurality of CCs, for example, as combined with Figure 6616. For example, the beam update component 844 can configure an update for each CC in a plurality of CCs on which a corresponding beam can be configured, wherein a corresponding one of the plurality of CCs is available through one of the TRPs. For example, the beam update component 844 can identify a resource set on which a CORESET can be found for each CC in the set of CCs, and the beam update component 844 can select a beam to transmit the resource set to the UE 104. In some aspects, the beam update component 844 can configure the beam by identifying a plurality of beams available for communication with the UE 104 at the mTRP, and the beam update component 844 can compare wireless channel measurements corresponding to the plurality of beams, respectively, to determine which of the plurality of beams provides the best channel quality (e.g., the highest channel measurement). The beam update component 844 can select the beam with the best channel quality to configure the UE 104 to communicate on one of the plurality of CCs using the beam. In some other aspects, the beam update component 844 can configure the beam by identifying a location or position of the UE 104 (which can be relative to a TRP in the mTRPs) and then selecting a beam for the TRP having a direction toward the UE 104 location or position.

[0191] If an mTRP is configured, scheduling component 846 can allocate resources for communicating with UE 104 on at most one CC of the plurality of CCs by each of at least two TRPs of the mTRP, respectively, e.g., as in conjunction with Figure 6 618. For example, the scheduling component 846 can schedule or allocate a first set of resources on a downlink control channel on one CC to carry a first DCI for one TRP of the UE 104, and allocate a second set of resources on a downlink control channel on another CC to carry a second DCI for another TRP of the UE 104. The scheduling component 846 can also allocate a third set of resources on a downlink data channel on the CC to carry the first downlink data for the TRP of the UE 104, and allocate a fourth set of resources on a downlink data channel on the other CC to carry the second downlink data for the other TRP of the UE 104. The first DCI can be configured to indicate scheduling of the first downlink data on the downlink control channel of the CC, and the second DCI can be configured to indicate scheduling of the second downlink data on the downlink control channel of the other CC.

[0192] Transmitting component 834 may be configured to transmit information indicating the beam to UE 104, for example, in conjunction with Figure 6620. Information indicating the beam may be included in at least one MAC CE. In some aspects, the information may configure UE 104 to perform directional beamforming on one or more CCs on which a CORESET may be found. In some other aspects, UE 104 may use the beam to sound on at least one of the CCs. For example, UE 104 may transmit an uplink SRS on at least one of the CCs toward at least one of the devices 802 via the beam.

[0193] The device 802 may include executing Figure 4 and 6 Some or all of the additional components of the blocks, operations, signaling, etc. of the algorithm(s) in the aforementioned call flow diagram and / or flowchart. Thus, Figure 4 and 6 Some or all of the blocks, operations, signaling, etc. in the aforementioned call flow diagrams and flowcharts may be performed by a component and the device 802 may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0194] In one configuration, the device 802, and in particular the baseband unit 804, includes: a device for configuring a beam set on multiple component carriers (CCs) for sTRP or for mTRP, the beam set being configured for sTRP when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a CORESET associated with at least one CC of the multiple CCs; and a device for transmitting information indicating the beam set associated with the multiple CCs to a UE.

[0195] In one configuration, a beam set is configured for mTRP if at least one of the following is true: a codepoint is mapped to two or more beam IDs, or a CORESET is configured with two or more pool indices or is not configured with a pool index.

[0196] In one configuration, the device for configuring a beam set is configured to configure at least one beam in the beam set on at least two CCs among the multiple CCs for sTRP, or to configure each beam in the beam set on at most one CC among the multiple CCs for mTRP.

[0197] In one configuration, the device 802, and in particular the baseband unit 804, may further include: a device for mapping each code point in the code point set to a corresponding beam ID set; and a device for transmitting at least one MAC CE indicating the code point set mapped to the corresponding beam ID set separately from the information indicating the beam set associated with the multiple CCs.

[0198] In one configuration, the device 802, and in particular the baseband unit 804, may further include: a device for configuring a pool index for the CORESET based on the code point; and a device for transmitting at least one RRC message indicating the pool index configured for the CORESET separately from the information indicating the beam sets associated with the multiple CCs.

[0199] In one configuration, the apparatus 802, and in particular the baseband unit 804, may further include means for receiving a set of SRSs from the UE on at least one CC of the plurality of CCs based on information indicating a set of beams associated with the plurality of CCs.

[0200] In one configuration, the apparatus 802, and in particular the baseband unit 804, may further include means for transmitting downlink data or control information to the UE on at least one CC of the plurality of CCs based on the information indicating the beam sets associated with the plurality of CCs.

[0201] In one configuration, information indicating beam sets associated with the plurality of CCs is included in at least one of a DCI or a MAC CE.

[0202] The aforementioned means may be one or more of the aforementioned components in the device 802 configured to perform the functions recited by the aforementioned means. As described above, the device 802 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0203] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. Based on design preferences, the specific order or hierarchy of each box in these process / flowcharts can be rearranged. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0204] The following examples are merely illustrative and may be combined with other embodiments or aspects of the teachings described herein without limitation.

[0205] Example 1 may be a method at a UE, comprising: receiving information indicating a beam set associated with multiple CCs; and activating the beam set on the multiple CCs for a single sTRP or for an mTRP, the beam set being activated for the sTRP when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a CORESET associated with at least one CC among the multiple CCs.

[0206] Example 2 may include a method as in Example 1, wherein the beam set is activated for mTRP when at least one of the following is true: the code point is mapped to two or more beam IDs, or the CORESET is configured with two or more pool indexes or is not configured with a pool index.

[0207] Example 3 may include a method as in Example 1, wherein activating the beam set includes: activating at least one beam in the beam set on at least two CCs among the multiple CCs for sTRP, or activating each beam in the beam set on at most one CC among the multiple CCs for mTRP.

[0208] Example 4 may include a method as in Example 1, further comprising: receiving at least one MAC CE separately from information indicating a beam set associated with the multiple CCs, the at least one MAC CE indicating a mapping of each code point in the code point set to a corresponding beam ID set; and identifying a beam in the beam set based on the mapping of each code point in the code point set to a corresponding beam ID set.

[0209] Example 5 may include a method as in Example 4, further comprising: receiving at least one RRC message separately from information indicating a beam set associated with the multiple CCs, the at least one RRC message indicating a pool index configured for the CORESET; and identifying, based on the pool index and based on the code point, on one CC among the multiple CCs, the CORESET associated with the sTRP for which the beam is activated.

[0210] Example 6 may include a method as in Example 1, further comprising: decoding information on at least one CC associated with the CORESET for sTRP in the multiple CCs or on at least two CCs associated with at least two CCs respectively for at least two TRPs in the mTRP in the multiple CCs.

[0211] Example 7 may include a method as in Example 1, further comprising: transmitting the SRS set to the sTRP via at least one beam in the beam set on at least one CC among the multiple CCs or to the mTRP via the beam set.

[0212] Example 8 may include a method as in Example 1, further comprising: receiving downlink data or control information from an sTRP via at least one beam in the beam set or from an mTRP via each beam in the beam set on the multiple CCs.

[0213] Example 9 may include a method as in Example 1, wherein information indicating a beam set associated with the plurality of CCs is included in at least one of a DCI or a MAC CE.

[0214] Example 10 may be a wireless communication method at a base station, comprising: configuring a beam set on multiple CCs for sTRP or for mTRP, the beam set being configured for the sTRP when less than two beam IDs respectively associated with the beam set are mapped to code points and less than two pool indexes are configured for a CORESET associated with at least one CC of the multiple CCs; and transmitting information indicating the beam set associated with the multiple CCs to the UE.

[0215] Example 11 may include a method as in Example 10, wherein the beam set is configured for mTRP if at least one of the following is true: the code point is mapped to two or more beam IDs, or the CORESET is configured with two or more pool indexes or is not configured with a pool index.

[0216] Example 12 may include a method as in Example 10, wherein configuring the beam set includes: configuring at least one beam in the beam set on at least two CCs among the multiple CCs for sTRP, or configuring each beam in the beam set on at most one CC among the multiple CCs for mTRP.

[0217] Example 13 may include a method as in Example 10, further comprising: mapping each code point in the code point set to a corresponding beam ID set; and transmitting at least one MAC CE indicating the code point set mapped to the corresponding beam ID set separately from information indicating the beam sets associated with the multiple CCs.

[0218] Example 14 may include a method as in Example 10, further comprising: configuring a pool index for the CORESET based on the code point; and transmitting at least one RRC message indicating the pool index configured for the CORESET separately from information indicating beam sets associated with the multiple CCs.

[0219] Example 15 may include the method of Example 10, further comprising: receiving an SRS set from the UE on at least one CC of the multiple CCs based on information indicating a beam set associated with the multiple CCs.

[0220] Example 16 may include a method as in Example 10, further comprising: transmitting downlink data or control information to the UE on at least one CC of the multiple CCs based on information indicating a beam set associated with the multiple CCs.

[0221] Example 17 may include a method as in Example 10, wherein information indicating a beam set associated with the plurality of CCs is included in at least one of a DCI or a MAC CE.

[0222] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the language. Therefore, the language employed herein is not intended to limit the scope of the claims to only those aspects shown herein, but should be granted the full scope consistent with the language of the claims.

[0223] As an example, the language "determine" may encompass a wide variety of actions, and thus may not be limited to the concepts and aspects explicitly described or illustrated by the present disclosure. In some contexts, "determine" may include calculating, computing, processing, measuring, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, and the like. In some other contexts, "determining" may include some communication and / or memory operations / procedures by which some information or value is obtained, such as "receiving" (e.g., receiving information), "accessing" (e.g., accessing data in a memory), "detecting," and the like.

[0224] As another example, references to singular elements are not intended to mean "there is and only one" (unless specifically so stated), but "one or more". Specifically, references to singular elements are not intended to mean "there is and only one" (unless specifically so stated), but "one or more". Terms such as "if", "when..." and "when..." should be interpreted as meaning "under the condition", rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., "when...") do not imply immediate action in response to the occurrence of an action or during the occurrence of an action, but only imply that an action will occur if the condition is met, without requiring a specific or immediate time constraint for the action to occur. The wording "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily to be interpreted as being superior to or superior to other aspects. Unless specifically stated otherwise, the term "some / certain" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc. may not be replacements for the term “means.” Thus, no claim element should be construed as means-plus-function unless the element is explicitly recited using the phrase “means for….”

Claims

1. A method for wireless communication at a user equipment UE, comprising: Receiving information indicating a beam set associated with a plurality of component carriers CC; as well as The beam set is activated on the multiple CCs, and when less than two beam identifiers IDs respectively associated with the beam set are mapped to code points or less than two pool indexes are configured for a control resource set CORESET associated with at least one CC among the multiple CCs, the beam set is activated for a single transmission reception point sTRP.

2. The method of claim 1, wherein: The beam set is activated for multiple TRPs mTRP when at least one of the following is true: The code point is mapped to two or more beam IDs, or The CORESET is configured with two or more pool indexes or is configured with no pool index.

3. The method of claim 1, wherein: Activating the beam set includes: For the sTRP, at least one beam in the beam set is activated on at least two CCs among the multiple CCs, or for multiple TRPs mTRP, each beam in the beam set is activated on at most one CC among the multiple CCs.

4. The method according to claim 1, before activating the beam set, the method further comprising: receiving, separately from the information indicating the beam sets associated with the plurality of CCs, at least one medium access control MAC control element CE, the at least one MAC CE indicating a mapping of each code point in a set of code points to a corresponding set of beam IDs; as well as A beam in the set of beams is identified based on the mapping of each codepoint in the set of codepoints to a corresponding set of beam IDs.

5. The method according to claim 4, before activating the beam set, the method further comprising: receiving at least one radio resource control (RRC) message separately from the information indicating the beam sets associated with the plurality of CCs, the at least one RRC message indicating a pool index configured for the CORESET; as well as The CORESET associated with the sTRP for which the beam is activated is identified on one of the multiple CCs based on the pool index and based on the codepoint.

6. The method of claim 1, wherein upon or after activating the beam set, the method further comprises: Decode information on at least one CC associated with the CORESET for the sTRP in the multiple CCs or on at least two CCs associated with at least two CCs in the multiple CCs for at least two TRPs in the multiple TRPs mTRPs, respectively.

7. The method of claim 1, wherein upon or after activating the beam set, the method further comprises: A sounding reference signal SRS set is transmitted to the sTRP via at least one beam in the beam set on at least one CC among the multiple CCs, or to multiple TRPs mTRPs via the beam set.

8. The method of claim 1, wherein upon or after activating the beam set, the method further comprises: Downlink data or control information is received from the sTRP via at least one beam in the beam set or from multiple TRPs mTRP via each beam in the beam set on the multiple CCs.

9. The method of claim 1, wherein: The information indicating the beam sets associated with the plurality of CCs is included in at least one of downlink control information DCI or a media access control MAC control element CE.

10. A method for wireless communication at a network node, comprising: configuring a beam set on a plurality of component carriers CC, wherein when less than two beam identifiers ID respectively associated with the beam set are mapped to code points or less than two pool indexes are configured for a control resource set CORESET associated with at least one CC of the plurality of CCs, the beam set is configured for a single transmission reception point sTRP; as well as Information indicating the beam sets associated with the plurality of CCs is transmitted to a user equipment (UE).

11. The method of claim 10, wherein: The beam set is configured for multiple TRPs mTRP if at least one of the following is true: The code point is mapped to two or more beam IDs, or The CORESET is configured with two or more pool indexes or is configured with no pool index.

12. The method of claim 10, wherein: Configuring the beam set includes: For the sTRP, at least one beam in the beam set is configured on at least two CCs among the multiple CCs, or for multiple TRPs mTRP, each beam in the beam set is configured on at most one CC among the multiple CCs.

13. The method of claim 10, further comprising: When configuring the beam set, mapping each code point in the code point set to a corresponding beam ID set; as well as At least one medium access control MAC control element CE is transmitted separately from the information indicating the beam sets associated with the plurality of CCs, the at least one MAC CE indicating the set of code points mapped to the corresponding set of beam IDs.

14. The method of claim 10, further comprising: When configuring the beam set, configuring a pool index for the CORESET based on the code point; as well as At least one radio resource control (RRC) message is transmitted separately from the information indicating the beam sets associated with the plurality of CCs, the at least one RRC message indicating the pool index configured for the CORESET.

15. The method of claim 10, after transmitting the information, further comprising: A sounding reference signal (SRS) set is received from the UE on at least one CC among the plurality of CCs based on the information indicating the beam sets associated with the plurality of CCs.

16. The method of claim 10, after transmitting the information, further comprising: Downlink data or control information is transmitted to the UE on at least one CC among the plurality of CCs based on the information indicating the beam sets associated with the plurality of CCs.

17. The method of claim 10, wherein: The information indicating the beam sets associated with the plurality of CCs is included in at least one of downlink control information DCI or a media access control MAC control element CE.

18. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: Receiving information indicating a beam set associated with a plurality of component carriers CC; as well as The beam set is activated on the multiple CCs, and when less than two beam identifiers (IDs) respectively associated with the beam set are mapped to code points or less than two pool indexes are configured for a control resource set (CORESET) associated with at least one CC among the multiple CCs, the beam set is activated for a single transmission reception point sTRP.

19. The device of claim 18, wherein: The beam set is activated for multiple TRPs mTRP when at least one of the following is true: The code point is mapped to two or more beam IDs, or The CORESET is configured with two or more pool indexes or is configured with no pool index.

20. The apparatus of claim 18, wherein: Activating the beam set includes: activating at least one beam in the beam set on at least two CCs among the multiple CCs for the sTRP, or activating each beam in the beam set on at most one CC among the multiple CCs for multiple TRPs mTRP.

21. The apparatus of claim 18, wherein: The at least one processor is further configured to, prior to activating the set of beams: receiving, separately from the information indicating the beam sets associated with the plurality of CCs, at least one medium access control MAC control element CE, the at least one MAC CE indicating a mapping of each code point in a set of code points to a corresponding set of beam IDs; as well as A beam in the set of beams is identified based on the mapping of each codepoint in the set of codepoints to a corresponding set of beam IDs.

22. The device of claim 21, wherein: The at least one processor is further configured to, prior to activating the set of beams: receiving at least one radio resource control (RRC) message separately from the information indicating the beam sets associated with the plurality of CCs, the at least one RRC message indicating a pool index configured for the CORESET; as well as The CORESET associated with the sTRP for which the beam is activated is identified on one of the multiple CCs based on the pool index and based on the codepoint.

23. The apparatus of claim 18, wherein: The at least one processor is further configured to, upon or after activating the set of beams: Decode information on at least one CC associated with the CORESET for the sTRP in the multiple CCs or on at least two CCs associated with at least two CCs in the multiple CCs for at least two TRPs in the multiple TRPs mTRPs, respectively.

24. The apparatus of claim 18, wherein: The at least one processor is further configured to, upon or after activating the set of beams: A sounding reference signal SRS set is transmitted to the sTRP via at least one beam in the beam set on at least one CC among the multiple CCs, or to multiple TRPs mTRPs via the beam set.

25. The apparatus of claim 18, wherein: The at least one processor is further configured to, upon or after activating the set of beams: Downlink data or control information is received from the sTRP via at least one beam in the beam set or from multiple TRPs mTRP via each beam in the beam set on the multiple CCs.

26. An apparatus for wireless communication at a network node, comprising: Memory; as well as at least one processor coupled to the memory and configured to: configuring a beam set on a plurality of component carriers CC, wherein when less than two beam identifiers ID respectively associated with the beam set are mapped to code points or less than two pool indexes are configured for a control resource set CORESET associated with at least one CC of the plurality of CCs, the beam set is configured for a single transmission reception point sTRP; as well as Information indicating the beam sets associated with the plurality of CCs is transmitted to a user equipment (UE).

27. The device of claim 26, wherein: The beam set is configured for multiple TRPs mTRP if at least one of the following is true: The code point is mapped to two or more beam IDs, or The CORESET is configured with two or more pool indexes or is configured with no pool index.

28. The apparatus of claim 26, wherein: Configuring the beam set includes: configuring at least one beam in the beam set on at least two CCs among the multiple CCs for the sTRP, or configuring each beam in the beam set on at most one CC among the multiple CCs for multiple TRPs mTRP.

29. The apparatus of claim 26, wherein: The at least one processor is further configured to: When configuring the beam set, mapping each code point in the code point set to a corresponding beam ID set; and At least one medium access control MAC control element CE is transmitted separately from the information indicating the beam sets associated with the plurality of CCs, the at least one MAC CE indicating the set of code points mapped to the corresponding set of beam IDs.

30. The apparatus of claim 26, wherein: The at least one processor is further configured to: When configuring the beam set, configuring a pool index for the CORESET based on the code point; as well as At least one radio resource control (RRC) message is transmitted separately from the information indicating the beam sets associated with the plurality of CCs, the at least one RRC message indicating the pool index configured for the CORESET.

Images