Enhanced PDSCH and PDCCH beam update based on group component carriers

Abstract

Certain aspects of the present disclosure relate to methods and apparatus for indicating a transmission configuration indication (TCI) status of multiple component carriers (CCs).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. application No. 17 / 091,866, filed on November 6, 2020, which claims the benefit of and priority to U.S. Provisional Patent Application No. 62 / 933,323, filed on November 8, 2019, which is assigned to the assignee of this application and is incorporated herein by reference in its entirety and for all applicable purposes as if fully set forth below. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to methods and apparatus for indicating a transmission configuration indication (TCI) status of multiple component carriers (CCs). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies, which are capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Long Term Evolution (LTE) systems, 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 (SCFDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] In some examples, a wireless multiple access communication system may include multiple base stations, each of which simultaneously supports communication for multiple communication devices (also known as user equipment (UE)). In an LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next-generation network or 5G network), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) communicating with multiple centralized units (CUs) (e.g., centralized nodes (CNs), access node controllers (ANCs), etc.), wherein the set of one or more distributed units communicating with the centralized unit may define an access node (e.g., new radio base stations (NR BSs), new radio node Bs (NR NBs), network nodes, 5G NBs, eNBs, next-generation node Bs (gNBs), etc.). A base station or DU may communicate with a group of UEs on downlink channels (e.g., for transmissions from or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at municipal, national, regional, and even global levels. An example of an emerging telecommunication standard is New Radio (NR), such as 5G radio access. NR is a set of enhancements to the LTE mobile standard released by the Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on the downlink (DL) and uplink (UL), and supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as demand for mobile broadband access continues to increase, there is a desire to further improve NR technology. Preferably, these improvements should also apply to other multiple access technologies and the telecommunication standards that employ them. Summary of the Invention

[0008] The systems, methods, and devices of the present disclosure each have several aspects, no single aspect of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," one will understand how the features of the present disclosure provide advantages, including improved communication between access points and stations in a wireless network.

[0009] Certain aspects provide a method for wireless communications by a user equipment. The method generally includes receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the DCI having a transmission configuration indicator (TCI) codepoint value; determining at least two activated PDSCH TCI state IDs for at least two frequency resource sets based on the codepoint value; and processing the PDSCH according to the indicated TCI state IDs.

[0010] Certain aspects provide a method for wireless communications by a network entity. The method generally includes determining a codepoint value associated with at least two activated PDSCH TCI state IDs for at least two frequency resource sets; and transmitting downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the DCI having a transmission configuration indicator (TCI) codepoint value.

[0011] Certain aspects provide a method for wireless communications by a user equipment. The method generally includes receiving a medium access control (MAC) control element (MAC CE) that activates at least one physical downlink control channel (PDCCH) TCI state ID for multiple control resource set (CORESET) IDs; and monitoring PDCCH transmissions in the CORESET IDs based on the activated TCI state IDs.

[0012] Certain aspects provide a method for wireless communications by a network entity. The method generally includes transmitting a medium access control (MAC) control element (MAC CE) that activates at least one physical downlink control channel (PDCCH) TCI state ID for multiple control resource set (CORESET) IDs; and sending at least one PDCCH in the CORESET ID according to the activated TCI state ID.

[0013] Aspects generally include methods, apparatus, systems, computer-readable media, and processing systems substantially as described herein with reference to and as illustrated in the accompanying drawings.

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

[0015] In order that the manner in which the above-described features of the present disclosure may be understood in detail, a more particular description, briefly summarized above, may be had by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the disclosure and are therefore not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0016] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in which aspects of the present disclosure may be performed.

[0017] Figure 2 is a block diagram illustrating an example logical architecture of a distributed RAN according to certain aspects of the present disclosure.

[0018] Figure 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0019] Figure 4is a block diagram conceptually illustrating a design of an example BS and user equipment (UE), in accordance with certain aspects of the present disclosure.

[0020] Figure 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

[0021] Figure 6 Illustrated are examples of frame formats for New Radio (NR) systems in accordance with certain aspects of the present disclosure.

[0022] Figure 7 An example of transmission configuration indicator (TCI) status information for signaling quasi co-location (QCL) information is illustrated.

[0023] Figure 8 An example QCL relationship between a source reference signal and a target reference signal is graphically illustrated.

[0024] Figure 9 An exemplary medium access control (MAC) control element (CE) for activating or deactivating the TCI state of a UE-specific physical channel according to previously known techniques is illustrated.

[0025] Figure 10 An exemplary MAC CE 400 for activating or deactivating the TCI state of a PDCCH according to previously known techniques is illustrated.

[0026] Figure 11 Example operations for wireless communications by a user equipment (UE) are illustrated in accordance with aspects of the present disclosure.

[0027] Figure 12 Example operations for wireless communications by a network entity are illustrated in accordance with aspects of the present disclosure.

[0028] Figure 13 Example operations for wireless communications by a user equipment (UE) are illustrated in accordance with aspects of the present disclosure.

[0029] Figure 14 Example operations for wireless communications by a network entity are illustrated in accordance with aspects of the present disclosure.

[0030] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION

[0031] Various aspects of the present disclosure provide mechanisms for indicating the transmission configuration indication (TCI) status of multiple component carriers (CCs). These mechanisms can be applied to New Radio (NR) (new radio access technology or 5G technology).

[0032] NR can support various wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., over 80 MHz), millimeter wave (mmW) for high carrier frequency (e.g., 60 GHz), massive MTC (mMTC) for non-backward compatible MTC technology, and / or mission-critical ultra-reliable low-latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0033] The following description provides examples, not limitations on the scope, applicability, or examples set forth in the claims. Without departing from the scope of this disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may appropriately omit, replace, or add various procedures or components. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, a device or method may be implemented using any number of aspects set forth herein. In addition, the scope of this disclosure is intended to cover such a device or method that is implemented using other structures, functions, or structures and functions other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims. The word "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 preferred or advantageous over other aspects.

[0034] The techniques described herein can be used in various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and others. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA, and others. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are versions of UMTS that use EUTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization called "3rd Generation Partnership Project 2" (3GPP2). "LTE" generally refers to LTE, LTE-Advanced (LTE-A), LTE in unlicensed spectrum (LTE-white space), etc. The techniques described herein can be used for the above-mentioned wireless networks and radio technologies as well as other wireless networks and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applied to other generation-based communication systems, such as 5G and later systems, including NR technologies.

[0035] Example Wireless Communication System

[0036] Figure 1 An example wireless network 100, such as a New Radio (NR) or 5G network, is illustrated in which aspects of the present disclosure may be performed. For example, the network 100 may include a network configured to perform Figure 11 Operation 1100 and / or Figure 13 Similarly, the network 100 may include one or more UEs 120 configured to perform the operations 1300. Figure 12 Operation 1200 and / or Figure 14 The operations 1400 may include one or more base stations 110.

[0037] like Figure 1 As shown, the wireless network 100 may include multiple BSs 110 and other network entities. A BS may be a station that communicates with a UE. Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a Node B and / or a Node B subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is interchangeable with eNB, Node B, 5G NB, AP, NR BS, NR BS, gNB, or TRP. In some examples, a cell may not necessarily be fixed, and the geographic area of ​​a cell may move depending on the location of a mobile base station. In some examples, base stations may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0038] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0039] A BS may provide communication coverage to macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.

[0040] The wireless network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and sends transmissions of data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions of other UEs. Figure 1 In the example shown, a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay, or the like.

[0041] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmit power level (e.g., 1 watt).

[0042] Wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, BSs can have similar frame timing, and transmissions from different BSs can be approximately aligned in time. For asynchronous operation, BSs can have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein can be used for both synchronous and asynchronous operation.

[0043] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other, directly or indirectly, for example, via a wireless or wired backhaul.

[0044] UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer property equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, medical device or medical equipment, healthcare device, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, virtual reality goggles, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, robot, drone, industrial manufacturing equipment, positioning device (e.g., GPS, BeiDou, terrestrial), or any other suitable device configured to communicate via wireless or wired media. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices, which may include remote devices that can communicate with a base station, another remote device, or some other entity. Machine type communication (MTC) may refer to communication involving at least one remote device on at least one end of the communication, and may include a form of data communication involving one or more entities that does not necessarily require human interaction. For example, an MTC UE may include a UE capable of MTC communication with an MTC server and / or other MTC devices via a public land mobile network (PLMN). MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, cameras, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. MTC UEs, as well as other UEs, may be implemented as Internet of Things (IoT) devices, such as narrowband IoT (NB-IoT) devices.

[0045] exist Figure 1 In FIG, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A dashed line with double arrows indicates interfering transmissions between the UE and the BS.

[0046] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0047] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR. NR can utilize OFDM with CP on the uplink as well as the downlink and includes support for half-duplex operation using time division duplexing (TDD). A single component carrier bandwidth of 100 MHz can be supported. NR resource blocks can span 12 subcarriers with a subcarrier bandwidth of 75 kHz in a duration of 0.1 ms. Each radio frame can consist of 50 subframes with a length (period) of 10 ms. Therefore, each subframe can have a length of 0.2 ms. In some cases, a subframe can have a length (duration) of 1 ms, and each subframe can be further divided into two slots of 0.5 ms each (e.g., each slot contains 6 or 7 OFDM symbols depending on the cyclic prefix (CP) length). The slots can be further divided into mini-slots, each of which has a smaller duration (e.g., contains fewer symbols than a full slot). Each subframe can indicate the link direction (e.g., DL or UL) for data transmission, and the link direction of each subframe can be switched dynamically. Each subframe can include DL / UL data and DL / UL control data. Beamforming can be supported, and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. The MIMO configuration in DL can support up to 8 transmit antennas, with up to 8 streams and multi-layer DL transmission of up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported with up to 8 serving cells. Alternatively, NR can support different air interfaces other than those based on OFDM. The NR network may include entities such as CU and / or DU.

[0048] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communications between some or all devices and equipment within its service area or cell. Within the present disclosure, as further discussed below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, subordinate entities utilize resources allocated by the scheduling entity. The base station is not the only entity that can serve as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE acts as a scheduling entity, and other UEs utilize the resources scheduled by the UE for wireless communications. The UE can serve as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity, the UEs can also optionally communicate directly with each other.

[0049] Therefore, in a wireless communication network having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more slave entities may communicate using the scheduled resources.

[0050] As described above, the RAN may include a CU as well as a DU. A NR BS (e.g., an eNB, a 5G Node B, a Node B, a Transmission Reception Point (TRP), an Access Point (AP)) may correspond to one or more BSs. An NR cell may be configured as an access cell (ACell) or a data-only cell (DCell). For example, a RAN (e.g., a centralized unit or a distributed unit) may configure a cell. DCells may be cells used for carrier aggregation or dual connectivity, but not for initial access, cell selection / reselection, or handover. In some cases, a DCell may not transmit a synchronization signal—in some cases, a DCell may transmit an SS. The NR BS may transmit a downlink signal indicating the cell type to the UE. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine the NR BS to consider for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0051] Figure 2 An example logical architecture of a distributed radio access network (RAN) 200 is illustrated, which may be Figure 1 206. The 5G access node 206 may include an access node controller (ANC) 202. The ANC may be a centralized unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC. The backhaul interface to the adjacent next generation access node (NG-AN) may terminate at the ANC. The ANC may include one or more TRPs 208 (which may also be referred to as BS, NR BS, Node B, 5G NB, AP, gNB or some other term). As described above, TRP may be used interchangeably with "cell".

[0052] The TRP 208 may be a DU. The TRP may be connected to one ANC (ANC 202) or more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, the TRP may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRP may be configured to provide information flows to the UE individually (e.g., dynamically selected) or jointly (e.g., joint transmission).

[0053] The local architecture 200 can be used to illustrate the fronthaul definition. An architecture can be defined to support fronthaul solutions across different deployment types. For example, the architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter).

[0054] The architecture may share features and / or components with LTE. According to various aspects, the next generation AN (NG-AN) 210 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.

[0055] This architecture may enable collaboration between TRPs 208. For example, collaboration may be provisioned within a TRP and / or across TRPs via ANC 202. According to various aspects, an inter-TRP interface may not be required / present.

[0056] According to various aspects, dynamic configuration of split logic functions may exist within architecture 200. Figure 5 Describing in more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer can be adaptively placed at the DU or CU (e.g., at the TRP or ANC, respectively). According to certain aspects, the BS may include a centralized unit (CU) (e.g., the ANC 202) and / or one or more distributed units (e.g., one or more TRPs 208).

[0057] Figure 3 An example physical architecture of a distributed RAN 300 according to aspects of the present disclosure is illustrated. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU can be centrally deployed. C-CU functions can be offloaded (e.g., to Advanced Radio Services (AWS)) to help handle peak capacity.

[0058] The centralized RAN unit (C-RU) 304 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can have a distributed deployment. The C-RU can be closer to the network edge.

[0059] DU 306 may host one or more TRPs (edge ​​nodes (EN), edge units (EU), radio heads (RH), smart radio heads (SRH), etc.) DU may be located at the edge of a network with radio frequency (RF) capabilities.

[0060] Figure 4 Illustrated Figure 11 and 120, which may be used to implement various aspects of the present disclosure. As described above, the BS may include a TRP. One or more components of the BS 110 and UE 120 may be used to practice various aspects of the present disclosure. For example, the antenna 452, processors 466, 458, 464, and / or controller / processor 480 (for implementing transceiver or separate receiver and transmitter chain functions) of the UE 120 may be used to perform Figure 11 Operation 1100 and / or Figure 13 Similarly, antenna 434, processors 430, 420, 438 and / or controller / processor 440 of BS 110 may be used to perform Figure 12 Operation 1200 and / or Figure 14 Operation 1400.

[0061] Figure 4 A block diagram showing a design of a BS 110 and a UE 120, which may be Figure 1 For the restricted association scenario, the base station 110 may be one of the BSs and one of the UEs. Figure 1 1. The macro BS 110c in FIG. 1 may be macro BS 110c, while UE 120 may be UE 120y. Base station 110 may also be some other type of base station. Base station 110 may be equipped with antennas 434a through 434t, and UE 120 may be equipped with antennas 452a through 452r.

[0062] At base station 110, transmit processor 420 may receive data from data source 412 and control information from controller / processor 440. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), etc. Data may be for a physical downlink shared channel (PDSCH), etc. Processor 420 may process (e.g., encode and symbol map) the data and control information, respectively, to obtain data symbols and control symbols. Processor 420 may also generate reference symbols, such as the PSS, SSS, and cell-specific reference signals. If applicable, transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols and may provide output symbol streams to modulators (MODs) 432a through 432t. For example, TX MIMO processor 430 may perform certain aspects described herein for RS multiplexing. Each modulator 432 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

[0063] At UE 120, antennas 452a through 452r may receive downlink signals from base station 110 and may provide received signals to demodulators (DEMODs) 454a through 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 454 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. For example, MIMO detector 456 may provide a detected RS transmitted using the techniques described herein. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 460, and provide decoding control information to a controller / processor 480. Depending on one or more scenarios, CoMP aspects may include providing antennas and some Tx / Rx functionality such that they reside in distributed units. For example, some Tx / Rx processing can be done in a centralized unit, while other processing can be done at a distributed unit.For example, according to one or more aspects as shown, BS MOD / DEMOD (modulator / demodulator) 432 can be in a distributed unit.

[0064] On the uplink, at the UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal. The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 (if applicable), further processed by demodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signal from the UE 120 may be received by the antenna 434, processed by the modulator 432, detected by the MIMO detector 436 (if applicable), and further processed by the receive processor 438 to obtain decoded data and control information transmitted by the UE 120. The receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller / processor 440 .

[0065] The controller / processor 440 and 480 may direct the operations at the base station 110 and the UE 120, respectively. As described above, the processor 440 and / or other processors and modules at the base station 110 may execute or direct the operations described herein. Figure 10 The processor 480 and / or other processors and modules at the UE 120 may also execute or direct the processes referenced herein. Figure 9 Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0066] Figure 5Illustrated is a diagram showing an example of implementing a communication protocol stack according to various aspects of the present disclosure. The illustrated communication protocol stack can be implemented by a device operating in a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communication protocol stack including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, the layers of the protocol stack can be implemented as separate modules of software, as part of a processor or ASIC, as part of a non-collocated device connected by a communication link, or various combinations thereof. For example, collocated and non-collocated implementations can be used in the protocol stack of a network access device (e.g., AN, CU, and / or DU) or a UE.

[0067] The first option 505-a shows a split implementation of the protocol stack, where the protocol stack is implemented in a centralized network access device (e.g., Figure 2 ANC 202 in the ) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 can be implemented by a centralized unit, and the RLC layer 520, the MAC layer 525, and the PHY layer 530 can be implemented by the DU. In various examples, the CU and the DU can be collocated or non-collocated. The first option 505-a can be used for macrocell, microcell, or picocell deployments.

[0068] The second option 505-b illustrates a unified implementation of the protocol stack, wherein the protocol stack is implemented in a single network access device (e.g., an access node (AN), a new radio base station (NR BS), a new radio node B (NR NB), a network node (NN), etc.). In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 can each be implemented by the AN. The second option 505-b can be used for femtocell deployment.

[0069] Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (eg, the RRC layer 510 , the PDCP layer 515 , the RLC layer 520 , the MAC layer 525 , and the PHY layer 530 ).

[0070] Figure 6is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes, each 1 ms, indexed from 0 to 9. Depending on the subcarrier spacing, each subframe may include a variable number of time slots. Depending on the subcarrier spacing, each time slot may include a variable number of symbol periods (e.g., 7 or 14 symbols). The symbol periods in each time slot may be assigned an index. A microslot, which may be referred to as a subslot structure, refers to a transmission time interval having a duration less than a time slot (e.g., 2, 3, or 4 symbols).

[0071] Each symbol in a slot can indicate the link direction (e.g., DL, UL, or flexible) used for data transmission, and the link direction can be dynamically switched for each subframe. The link direction can be based on the slot format. Each slot can include DL / UL data and DL / UL control information.

[0072] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and two-symbol PBCH. The SS block can be transmitted in a fixed time slot position, such as Figure 6 Symbols 0-3 are shown. PSS and SSS can be used by UE for cell search and acquisition. PSS can provide half-frame timing, and SS can provide CP length and frame timing. PSS and SSS can provide cell identification. PBCH carries some basic system information, such as downlink system bandwidth, timing information within a radio frame, SS burst set periodicity, system frame number, etc. SS blocks can be organized into SS bursts to support beam scanning. Other system information such as remaining minimum system information (RMSI), system information block (SIB), and other system information (OSI) can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes.

[0073] The UE can operate in various radio resource configurations, including a configuration associated with transmitting pilot signals using a dedicated resource set (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilot signals using a common resource set (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE can select a dedicated resource set for transmitting pilot signals to the network. When operating in the RRC common state, the UE can select a common resource set for transmitting pilot signals to the network. In either case, the pilot signals transmitted by the UE can be received by one or more network access devices (such as an AN or a DU, or portions thereof). Each receiving network access device can be configured to receive and measure pilot signals transmitted on the common resource set, and also receive and measure pilot signals transmitted on a dedicated resource set allocated to the UE, the network access device for transmitting pilot signals on the dedicated resource set allocated to the UE being a member of the UE's network access device monitoring set. The CU that receives the measurement results of the pilot signals transmitted by one or more of the network access devices can use the measurement results to identify the serving cell of the UE or to initiate a change of the serving cell of one or more of the UEs.

[0074] Example QCL signaling

[0075] In many cases, it is important for the UE to know which assumptions it can make on the channels corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode the transmitted signal (e.g., PDCCH or PDSCH). It may also be important for the UE to be able to report relevant channel state information (CSI) to the BS (gNB) for scheduling, link adaptation, and / or beam management purposes. In NR, the concepts of Quasi Co-location (QCL) and Transmission Configuration Indicator (TCI) status are used to convey information about these assumptions.

[0076] The QCL assumption is typically defined in terms of channel characteristics. According to 3GPP TS 38.214, "Two antenna ports are said to be quasi co-located if the characteristics of the channel over which symbols on one antenna port are transmitted can be inferred from the channel over which symbols on the other antenna port are transmitted." Different reference signals may be considered quasi co-located ("QCL'd") if a receiver (e.g., a UE) can apply the channel characteristics determined by detecting the first reference signal to aid in detecting the second reference signal. The TCI state typically includes configurations such as the QCL relationship between the DL RS and PDSCH DMRS ports in one CSI-RS set.

[0077] In some cases, a UE can be configured with up to M TCI states. The configuration of the M TCI states can be implemented via higher layer signaling, and the UE can be informed to decode the PDSCH based on the detected PDCCH with DCI indicating one of the TCI states. For example, a specific TCI state can be indicated by an N-bit DCI field for the PDSCH. Each configured TCI state can include an RS set TCI-RS-SetConfig, which indicates different QCL assumptions between certain source and target signals.

[0078] In certain deployments, techniques are used to provide quasi-co-site (QCL) signaling for reference signals (RS) and channels in scenarios involving multiple cells, such as coordinated multi-point (CoMP) scenarios where multiple transmission reception points (TRPs) or integrated access and backhaul (IAB) nodes each have their own cell ID.

[0079] Figure 7 This section illustrates how RS associated with a TCI state can be configured via radio resource control (RRC) signaling. In some cases, QCL information and / or type may depend on or be a function of other information. For example, the quasi-co-location (QCL) type indicated to the UE may be based on a higher-layer parameter, QCL-Type, and may be one or a combination of the following types:

[0080] QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread},

[0081] QCL-TypeB: {Doppler shift, Doppler spread},

[0082] QCL-TypeC: {average delay, Doppler shift}, and

[0083] QCL-TypeD: {spatial Rx parameters}.

[0084] The spatial QCL assumption (QCL-Type D) can be used to help the UE select the simulated Rx beam (e.g., during the beam management procedure). For example, the SSB resource indicator can indicate that the same beam used for the previous reference signal should be used for subsequent transmissions.

[0085] like Figure 7 As shown, the TCI state can indicate which RS is QCL'd and the QCL type. The TCI state can also indicate the ServCellIndex, which is a short identifier used to identify the serving cell, such as the primary cell (PCell) or secondary cell (Scell) in a carrier aggregation (CA) deployment. A value of 0 for this field can indicate the PCell, while a previously assigned SCellIndex can be applied to the SCell.

[0086] Figure 8 An example of association of DL reference signals with corresponding QCL types that can be indicated by TCI-RS-SetConfig is illustrated.

[0087] exist Figure 8 In the example of FIG, a source reference signal (RS) is indicated in the top block and is associated with a target signal indicated in the bottom block. In this context, a target signal generally refers to a signal whose channel characteristics can be inferred by measuring those of the associated source signal. As described above, the UE can use the source RS to determine various channel parameters according to the associated QCL type and use those various channel characteristics (determined based on the source RS) to process the target signal. The target RS does not necessarily need to be the DMRS of the PDSCH, but can be any other RS: PUSCH DMRS, CSIRS, TRS, and SRS.

[0088] As shown in the figure, each TCI-RS-SetConfig contains parameters. These parameters can, for example, configure the quasi-co-location relationship (or multiple) between the reference signals in the RS set and the DM-RS port group of the PDSCH. The RS set contains references to one or two DL RSs and the associated quasi-co-location type (QCL-Type) for each DL RS, which is configured by the higher-layer parameter QCL-Type.

[0089] like Figure 8 As shown, for the case of two DL RSs, the QCL type can take various arrangements. For example, the QCL type can be different, whether referring to the same DL RS or different DL RSs. In the example shown, the SSB is associated with Type C QCL for P-TRS, while the CSI-RS for beam management (CSIRS-BM) is associated with Type D QCL.

[0090] Figure 9An exemplary medium access control (MAC) control element (CE) 900 for activating or deactivating the TCI state of a UE-specific physical downlink shared channel (PDSCH) according to previously known techniques (e.g., Rel-15) is illustrated. The exemplary MAC CE includes a plurality of octets 910, 920, 930, 940, etc. The first octet 910 includes a serving cell ID field 912, which is five bits long and indicates the identity of the serving cell to which the MAC CE applies. The first octet also includes a BWP ID field 914, which is two bits long and indicates the downlink (DL) bandwidth part (BWP) to which the MAC CE applies, as a codepoint of the downlink control information (DCI) bandwidth part indicator field as specified in TS 38.212 (available from the 3GPP website and other sources). The second octet 920 and subsequent octets include bits indicating the serving cell ID and the TCI state of the BWP ID. For each T i , if there is a TCI state with TCI-StateId i as specified in TS 38.331 (also available from 3GPP), the corresponding T i The field indicates the activation state or deactivation state of the TCI state with TCI-StateId i. Otherwise (i.e., there is no TCI state with TCI-StateID i), the MAC entity ignores TCI-StateId i. i Field. T i The field is set to 1 to indicate that the TCI state with TCI-StateId i is activated and is mapped to the codepoint of the DCI Transmission Configuration Indication field, as specified in TS 38.214 (available from 3GPP). i The field is set to 0 to indicate that the TCI state with TCI-StateId i is deactivated and is not mapped to the codepoint of the DCI transmission configuration indication field. The codepoint to which the TCI state is mapped is determined by its TCI-StateId i. i The sequential position of all TCI states in which the field is set to 1 is determined, i.e., T i The first TCI state with the field set to 1 shall be mapped to code point value 0. i The second TCI state with the field set to 1 shall be mapped to code point value 1, etc. The maximum number of activated TCI states may be 8.

[0091] Figure 10An exemplary MAC CE 1000 for activating or deactivating the TCI state of a PDCCH according to previously known techniques (e.g., Rel-15) is illustrated. A first octet 1010 includes a serving cell ID field 1012, which is five bits long and indicates the identity of the serving cell to which the MAC CE applies. The last three bits 1014 and first bit 1022 of a second octet 1020 constitute a CORESET ID field, which is four bits long and indicates the control resource set (CORESET) identified by ControlResourceSetId (e.g., as specified in TS 38.331, available from 3GPP) for which the TCI state is indicated. If the value of the field is 0, then the field refers to a control resource set configured by controlResourceSetZero (e.g., as specified in TS 38.331). The second octet 1020 includes a TCI State ID field, which is seven bits long and indicates the TCI state identified by TCI-StateId (e.g., as specified in TS 38.331) that is applicable to the control resource set identified by the CORESET ID field. If the value of the CORESET ID field is set to 0, the TCI State ID field indicates the TCI-StateId of the first 64 TCI states configured by the tci-States-ToAddModList and tci-States-ToReleaseList in the PDSCH-Config in the active BWP. If the value of the CORESET ID field is set to a non-zero value, the TCI State ID field indicates the TCI-StateId configured by the tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID.

[0092] Example Enhanced Group-CC-Based PDSCH & PDCCH Beam Update

[0093] Aspects of the present disclosure provide a mechanism for indicating the transmission configuration indication (TCI) status of multiple component carriers (CCs).

[0094] In scenarios involving multiple Transmission Reception Points (TRPs), conventional DCI-based signaling presents various potential issues. For example, one potential issue is that (in Rel-16) for mTRPs based on a single DCI, the mapping between PDSCH TCI codepoints and the corresponding activated PDSCH TCI state IDs is indicated by a MAC-CE per CC. In the case of multiple CCs, multiple such MAC-CEs must be sent, increasing overhead and latency.

[0095] Another potential problem is that (in Rel. 16) for the Group-CC PDCCH TCI state activation MAC-CE, each MAC-CE can only indicate the activation TCI state of a specific CORESET ID. For multiple CORESET IDs, multiple such MAC-CEs must be sent, which increases overhead and delay.

[0096] Another potential issue is that (in Rel-16) for the Group-CC PDCCH TCI State Activation MAC-CE, the UE behavior may need to be clarified if the indicated CORESET ID or the corresponding activation TCI state ID is not configured on a CC in the indicated CC list.

[0097] In some cases, for group-CC-based PDSCH beam updates, when a set of TCI state IDs for PDSCH is activated by a MAC CE for at least a set of CCs / BWPs for the same band (where the applicable CC list is indicated by RRC signaling), the same set of TCI state IDs is applied to all BWPs in the indicated CCs. In some cases, inter-band CA for this feature can be supported. In some cases, an indication of the applicable band list can be provided for a single MAC-CE feature to activate the same set of PDSCH TCI state IDs for multiple CCs / BWPs. RRC can configure how many CC combinations can be used based on UE capabilities.

[0098] In some cases, to enable simultaneous TCI state activation across multiple CCs / BWPs, each UE's RRC may configure up to two CC lists, with the list to be applied being determined by the indicating CC in the MAC CE. In this case, the UE may expect that there are no overlapping CCs in the multiple RRC-configured CC lists.

[0099] However, aspects of the present disclosure may help resolve the above-mentioned potential issues, for example, in the case of mTRP where a single DCI is utilized to schedule a PDSCH.

[0100] Figure 11 Illustrated are example operations 1100 for wireless communications by a UE in accordance with aspects of the present disclosure.

[0101] Operations 1100 begin by receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) at 1102, the DCI having a transmission configuration indicator (TCI) code point value. In some cases, the DCI includes a single DCI scheduling multiple PDSCHs from multiple transmission reception points.

[0102] At 1104, the UE determines at least two activated PDSCH TCI state IDs for at least two frequency resource sets based on the codepoint values. In some cases, the UE receives a single medium access control (MAC) control element (CE) that activates the at least two PDSCH TCI state IDs. In some cases, the at least two frequency resource sets include at least one of a plurality of component carriers (CCs) or a plurality of bandwidth parts (BWPs). For example, the UE determines the at least two activated PDSCH TCI state IDs based on a mapping of codepoint values ​​to TCI state IDs. The UE may receive signaling indicating a list of CCs, and the same mapping is applied to all CCs in the list and corresponding BWPs.

[0103] In some cases, the CC list is indicated via at least one of radio resource control (RRC) signaling, MAC CE, or DCI. The CC list may be configured via RRC signaling, and the applicable list may be implicitly determined by the indicated CC in the MAC CE or DCI, or by explicit signaling of the applicable CC list ID in the MAC CE or DCI.

[0104] In some cases, the UE receives signaling indicating the mapping via a MAC CE activating the PDSCH TCI state ID or a separate MAC CE.

[0105] At 1106, the UE processes the PDSCH according to the indicated TCI state ID.

[0106] Figure 12 Example operations 1200 for wireless communication by a network entity according to aspects of the present disclosure are illustrated. For example, operations 1200 may be performed by a base station to communicate with a UE that performed operations 1100 described above.

[0107] Operations 1200 begin by determining a codepoint value associated with at least two activated PDSCH TCI state IDs for at least two frequency resource sets at 1202. At 1204, a network entity transmits downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the DCI having a transmission configuration indicator (TCI) codepoint value.

[0108] In this way, for a single DCI-based mTRP on each of multiple CCs, a (single) PDSCH TCI code point value can be mapped to at least two activated PDSCH TCI state IDs by a single MAC CE for a group of CCs / BWPs. In some cases, the DCI includes a single DCI that schedules PDSCHs from multiple transmission reception points.

[0109] In some cases, the same mapping between codepoint values ​​and TCI state IDs may apply to each BWP / CC in the applicable CC list. The applicable CC list may be indicated, for example, by RRC / MAC-CE / DCI signaling. If multiple CC lists are configured by RRC, the applicable list may be implicitly determined by the CC indicated in the MAC-CE / DCI, or the applicable list may be explicitly signaled via the applicable CC list ID in the MAC-CE / DCI.

[0110] The group-CC TCI code point mapping may be done by the same or a different MAC-CE than the group-CC TCI state activation MAC-CE.In some cases, the network sends a single MAC CE that activates the PDSCH TCI state ID.

[0111] In some cases, for group-CC based PDCCH beam updates, when a TCI state ID is activated for a CORESET by a MAC CE for at least a group of CCs / BWPs for the same band (where the applicable CC list is indicated by RRC signaling), the TCI state ID is applied to the CORESET(s) with the same CORESET ID for all BWPs in the indicated CCs. In some cases, inter-band CA for this feature may be supported. In some cases, an indication of the applicable band list may be provided for a feature of a single MAC-CE to activate the same group of PDCCH TCI state IDs for multiple CCs / BWPs.

[0112] To enable simultaneous TCI state activation across multiple CCs / BWPs, each UE's RRC can configure up to two CC lists, and the list applied is determined by the CC indicated in the MAC CE. The UE may expect that there are no overlapping CCs in multiple RRC-configured CC lists.

[0113] In some cases, the at least two frequency resource sets may include at least one of a plurality of component carriers (CCs) or a plurality of bandwidth parts (BWPs). For example, the network determines the codepoint value based on a mapping of the codepoint value to the TCI state ID. The network may further send signaling indicating a CC list, and the same mapping is applied to all CCs in the list and the corresponding BWPs. The CC list may be indicated via at least one of RRC signaling, MAC CE, or DCI. In some cases, multiple CC lists are configured via RRC signaling. The network entity determines the applicable list implicitly by the indicated CC in the MAC CE or DCI, or explicitly by signaling the applicable CC list ID in the MAC CE or DCI. The network entity may further send signaling indicating the mapping via a MAC CE that activates the PDSCH TCI state ID or a separate MAC CE.

[0114] Figure 13 Illustrated are example operations 1300 for wireless communications by a UE, in accordance with aspects of the present disclosure.

[0115] Operations 1300 begin by receiving a medium access control (MAC) control element (MAC CE) that activates at least one physical downlink control channel (PDCCH) TCI state ID for multiple control resource set (CORESET) IDs at 1302. At 1304, the UE monitors PDCCH transmissions in the CORESET IDs according to the activated TCI state IDs.

[0116] In some cases, a UE receives a single DCI that schedules PDSCHs from multiple transmission reception points. In some cases, at least one activated TCI state ID is applied to a CORESET in one or more configured downlink BWPs for one or more CCs in a component carrier (CC) list.

[0117] In some cases, the multiple CORESET IDs are members of a group having a CORESET group ID. The MAC CE indicates the CORESET group ID with a set of activated TCI state IDs applied to the CORESETs in the CORESET group. The CORESET group may include CORESETs with different higher layer transmitter receiver point (TRP) indices. The UE may receive signaling configuring the CORESET ID of the CORESET group. In some cases, the UE may determine the CORESET ID of the CORESET group based on a rule. For example, the rule may group CORESETs with certain IDs for different TRP indices into a first group. The rule may group CORESETs with certain IDs for different TRP indices into a second group.

[0118] In some cases, the group activated TCI state ID for each CORESET group may be indicated by at least one of a separate TCI state ID or a TCI state group ID. The TCI state group ID may be mapped to a separate TCI state ID. A CORESET group may include CORESETs with different higher layer transmitter receiver point (TRP) indices. A network entity may signal the CORESET IDs of the CORESET group or determine the CORESET IDs of the CORESET group based on a rule that may group CORESETs with certain IDs for different TRP indices into a first group and group CORESETs with certain IDs for different TRP indices into a second group.

[0119] In some cases, different CORESET IDs are configured for at least some of the CCs included in a component carrier (CC) list. A rule may dictate that all CCs must have the same configured CORESET ID to be included in the same CC list.

[0120] In some cases, the UE is configured to ignore the MAC CE of Group-CC PDCCH TCI State Activation for CORESET IDs not configured in the CC. For CCs included in the CC list, each CC may be configured with a TCI State ID per CORESET ID. A rule may dictate that the TCI State ID for each CORESET ID should be the same for all CCs in the CC list.

[0121] In some cases, the UE is configured to ignore MAC CEs for Group-CC PDCCH TCI State Activation for TCI State IDs that are not configured in the CC for the indicated CORESET ID.

[0122] Figure 14 Example operations 1400 for wireless communication by a network entity according to aspects of the present disclosure are illustrated. For example, operations 1400 may be performed by a base station to communicate with a UE performing operations 1300 described above.

[0123] Operations 1400 begin by transmitting a medium access control (MAC) control element (MAC CE) that activates at least one physical downlink control channel (PDCCH) TCI state ID for multiple control resource set (CORESET) IDs at 1402. At 1404, a network entity transmits at least one PDCCH in the CORESET ID according to the activated TCI state ID.

[0124] In this way, for the Group-CC PDCCH TCI State Activation MAC-CE, the TCI states of multiple CORESET IDs can be activated. In some cases, the activated TCI state ID for a given CORESET ID can be applied to all BWPs / CCs in the CC list. For CCs included in the CC list, each CC can be configured with these multiple CORESET IDs. In some cases, rules may dictate that all CCs must have the same configured CORESET ID to be included in the same CC list.

[0125] In some cases, a network entity sends downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) with a transmission configuration indicator (TCI) codepoint value. The DCI may include a single DCI that schedules a PDSCH from multiple transmission reception points.

[0126] In some cases, instead of individual CORESET IDs, the Group-CC PDCCH TCI State Activation MAC-CE may indicate a CORESET Group ID with a set of activated TCI State IDs applied to the CORESETs in the CORESET Group. In this case, the CORESET Group may contain CORESETs with different higher layer TRP indices.

[0127] The group CORESET ID for each CORESET group can be explicitly configured or implicitly determined by a rule. For example, a rule may specify that the two CORESETs with the lowest IDs, 0 and 1 respectively, form the first group, and the two CORESETs with the second lowest IDs, 0 and 1 respectively, form the second group, and so on, depending on the number of groups.

[0128] In some cases, the set of activated TCI state IDs for each CORESET group may be indicated by a separate TCI state ID. In other cases, the set of active TCI state IDs may be indicated by a TCI state group ID, which is mapped to a separate TCI state ID. In some cases, at least one activated TCI state ID is applied to a CORESET in one or more configured downlink bandwidth parts (BWPs) of one or more CCs in a component carrier (CC) list. According to various options, a CORESET ID may be configured for each CC included in the CC list. For example, according to a first option, all CCs may be required to have the same configured CORESET ID to be included in the same CC list. According to a second option, all CCs may be allowed to have different configured CORESET IDs. In this case, for the Group-CC PDCCH TCI State Activation MAC-CE, the UE may ignore the indicated CORESET ID that is not configured in the CC.

[0129] In some cases, according to various options, a TCI state ID may be configured for each CC and each CORESET ID for CCs included in the CC list. For example, for the first option, the configured TCI state ID for each CORESET ID may be required to be the same for all CCs in the CC list. For the second option, the configured TCI state ID for each CORESET ID may be allowed to be different for all CCs in the CC list. In this case, for the Group-CC PDCCH TCI State Activation MAC-CE, the UE may ignore activated TCI state IDs that are not configured in the CC for the indicated CORESET ID.

[0130] Example aspects

[0131] Aspect 1: A method for wireless communication performed by a user equipment (UE), comprising: receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the DCI having a transmission configuration indicator (TCI) code point value; determining at least two activated PDSCH TCI state IDs for at least two frequency resource sets based on the code point value; and processing the PDSCH according to the indicated TCI state ID.

[0132] Aspect 2: The method according to aspect 1, wherein the DCI comprises a single DCI that schedules PDSCHs from multiple transmission reception points.

[0133] Aspect 3: The method according to aspect 1 or 2, further comprising receiving a single medium access control (MAC) control element (MAC CE) activating a PDSCH TCI state ID.

[0134] Aspect 4: The method according to any one of aspects 1-3, wherein the plurality of frequency resource sets comprises at least one of: a plurality of component carriers (CCs); or a plurality of bandwidth parts (BWPs).

[0135] Aspect 5: The method according to any one of aspects 1-4, wherein the determination is based on a mapping of codepoint values ​​to TCI state IDs.

[0136] Aspect 6: The method according to any one of aspects 1 to 5, further comprising receiving signaling indicating a list of CCs, and the same mapping is applied to all CCs in the list and the corresponding BWPs.

[0137] Aspect 7: The method according to any one of aspects 1-4, further comprising receiving signaling indicating the mapping via: a medium access control (MAC) control element (MAC CE) activating the PDSCH TCI state ID; or a separate MAC CE.

[0138] Aspect 8: A method for wireless communication performed by a network entity, comprising: determining a code point value associated with at least two activated PDSCH TCI state IDs of at least two frequency resource sets; and sending downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the DCI having a transmission configuration indicator (TCI) code point value.

[0139] Aspect 9: The method of aspect 8, wherein the DCI comprises a single DCI that schedules PDSCHs from multiple transmission reception points.

[0140] Aspect 10: The method according to aspect 8 or 9, further comprising sending a single medium access control (MAC) control element (MAC CE) activating the PDSCH TCI state ID.

[0141] Aspect 11: The method according to any one of aspects 8 to 10, wherein the plurality of frequency resource sets comprises at least one of: a plurality of component carriers (CCs); or a plurality of bandwidth parts (BWPs).

[0142] Aspect 12: The method according to any one of aspects 8-11, wherein the determination is based on a mapping of codepoint values ​​to TCI state IDs.

[0143] Aspect 13: The method according to any one of aspects 8 to 12, further comprising sending signaling indicating a list of CCs, and the same mapping is applied to all CCs in the list and corresponding BWPs.

[0144] Aspect 14: The method according to any one of aspects 8 to 13, further comprising sending signaling indicating the mapping via: a medium access control (MAC) control element (MAC CE) activating the PDSCH TCI state ID; or a separate MAC CE.

[0145] Aspect 15: A method for wireless communication performed by a user equipment (UE), comprising: receiving a medium access control (MAC) control element (MAC CE) that activates at least one physical downlink control channel (PDCCH) TCI state ID for multiple control resource sets (CORESET) IDs; and monitoring PDCCH transmission in the CORESET ID according to the activated TCI state ID.

[0146] Aspect 16: The method according to aspect 15, further comprising receiving a single DCI scheduling PDSCH from multiple transmission reception points.

[0147] Aspect 17: The method according to aspect 15 or 16, wherein at least one activated TCI state ID is applied to a CORESET in one or more configured downlink BWPs of one or more CCs in a component carrier (CC) list.

[0148] Aspect 18: The method according to any one of aspects 15-17, wherein the plurality of CORESET IDs are members of a group having a CORESET Group ID; and the MAC CE indicates the CORESET Group ID having an active TCI State ID group applied to the CORESETs in the CORESET Group.

[0149] Aspect 19: The method according to any one of aspects 15-18, wherein the group activated TCI state ID of each CORESET group is indicated by at least one of: an individual TCI state ID; or a TCI state group ID, which is mapped to an individual TCI state ID.

[0150] Aspect 20: The method according to any one of aspects 15 to 19, wherein different CORESET IDs are configured for at least some of the component carriers (CCs) included in the CC list.

[0151] Aspect 21: The method according to any one of aspects 15-20, wherein the UE is configured to ignore the MAC CE of Group-CC PDCCH TCI State Activation for a CORESET ID not configured in the CC.

[0152] Aspect 22: The method according to any one of aspects 15 to 21, wherein for CCs included in the CC list, a TCI state ID is configured per CORESET ID per CC.

[0153] Aspect 23: The method according to any one of aspects 15-22, wherein the UE is configured to ignore a MAC CE for Group-CC PDCCH TCI State Activation for a TCI State ID not configured in the CC for the indicated CORESET ID.

[0154] Aspect 24: A method for wireless communication performed by a network entity, comprising: transmitting a medium access control (MAC) control element (MAC CE), the MAC CE activating at least one physical downlink control channel (PDCCH) TCI state ID for multiple control resource sets (CORESET) IDs; and sending at least one PDCCH in the CORESET ID according to the activated TCI state ID.

[0155] Aspect 25: The method of aspect 24, wherein the DCI comprises a single DCI that schedules PDSCHs from multiple transmission reception points.

[0156] Aspect 26: The method according to aspect 24 or 25, wherein at least one activated TCI state ID is applied to a CORESET in one or more configured downlink bandwidth parts (BWPs) of one or more CCs in a component carrier (CC) list.

[0157] Aspect 27: The method according to any one of aspects 24-26, wherein the plurality of CORESET IDs are members of a group having a CORESET Group ID; and the MAC CE indicates the CORESET Group ID having an active TCI State ID group applied to the CORESETs in the CORESET Group.

[0158] Aspect 28: The method according to any one of aspects 24-27, wherein the set activated TCI state ID of each CORESET group is indicated by at least one of: an individual TCI state ID; or a TCI state group ID, which is mapped to an individual TCI state ID.

[0159] Aspect 29: The method according to any one of aspects 24 to 28, wherein for CCs included in a component carrier (CC) list, the plurality of CORESET IDs are configured per CC.

[0160] Aspect 30: The method according to any one of aspects 24 to 29, wherein for CCs included in the CC list, a TCI state ID is configured per CORESET ID per CC.

[0161] Aspect 31: An apparatus having at least one processor and a memory, configured to perform the operations according to any one of aspects 1-7.

[0162] Aspect 32: An apparatus having at least one processor and a memory, configured to perform the operations according to any one of aspects 8-14.

[0163] Aspect 33: An apparatus having at least one processor and a memory, configured to perform the operations according to any one of aspects 15-23.

[0164] Aspect 34: An apparatus having at least one processor and a memory, configured to perform the operations according to any one of aspects 24-30.

[0165] Aspect 35: An apparatus having means for performing the operations according to any one of aspects 1-7.

[0166] Aspect 36: An apparatus having means for performing the operations according to any one of aspects 8-14.

[0167] Aspect 37: An apparatus having means for performing the operations according to any one of aspects 15-23.

[0168] Aspect 38: An apparatus having means for performing the operations according to any one of aspects 24-30.

[0169] Aspect 39: A computer-readable medium having stored thereon instructions for performing the operations according to any one of aspects 1-7.

[0170] Aspect 40: A computer-readable medium having stored thereon instructions for performing the operations according to any one of aspects 8-14.

[0171] Aspect 41: A computer-readable medium having stored thereon instructions for performing the operations according to any one of aspects 15-23.

[0172] Aspect 42: A computer-readable medium having stored thereon instructions for performing the operations according to any one of aspects 24-30.

[0173] The methods disclosed herein include one or more steps or actions for implementing the methods. Method steps and / or actions may be interchangeable with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0174] As used herein, a phrase referring to "at least one" of a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c). As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as comprising components A, B, and / or C, the composition may comprise: A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C.

[0175] As used herein, the term "determining" includes a variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or another data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Furthermore, "determining" may include resolving, selecting, choosing, establishing, etc.

[0176] The previous description is provided to enable those skilled in the art to practice the various aspects described herein. Those skilled in the art will readily appreciate the various modifications to these aspects, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but rather to conform to the full scope consistent with the language claims, wherein, unless explicitly stated otherwise, reference to an element in the singular is not intended to mean "one and only one", but rather "one or more". For example, the articles "one" and "an" as used in this application and the appended claims should generally be interpreted as meaning "one or more", unless otherwise specified or clearly indicated by the context to be singular. Unless otherwise specifically stated, the term "some" refers to one or more. In addition, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly indicated by the context, a phrase (e.g., "X employs A or B") is intended to mean any one of the natural inclusive arrangements. That is, for example, any of the following situations satisfies the phrase "X employs A or B": X employs A; X employs B; or X employs both A and B. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. A claim element is not to be construed under 35 U.S.C. §112, paragraph 6, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for”.

[0177] The various operations of the above methods may be performed by any suitable component capable of performing the corresponding functions. The component may include various hardware and / or (multiple) software components and / or (multiple) modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors. For example, Figure 11 、 12 Operations 1100, 1200, 1300, and 1400 of steps 1100, 1200, 1300, and 1400 may be performed by Figure 4 The various processors shown perform. Generally, where there are operations shown in the figures, those operations may have corresponding counterparts with components plus functionality.

[0178] The various illustrative logical blocks, modules, and circuits described in conjunction with this disclosure may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0179] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application of the processing system and the overall design constraints, the bus may include any number of interconnecting buses and bridges. The bus may connect various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter and other components to the processing system via the bus. The network adapter may be used to implement signal processing functions at the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., keyboard, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also connect various other circuits well known in the art, such as timing sources, peripherals, voltage regulators, power management circuits, etc., and therefore will not be described further. The processor may be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will understand how to best implement the described functionality of the processing system based on the specific application and the overall design constraints imposed on the entire system.

[0180] If implemented in software, the functionality may be stored or transmitted as one or more instructions or code on a computer-readable medium. Software should be broadly construed to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. For example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a computer-readable storage medium having instructions stored thereon separate from the wireless node, all of which may be accessed by the processor via a bus interface. Alternatively, or in addition, the machine-readable medium or any portion thereof may be integrated into the processor, such as may be the case with a cache memory and / or a general register file. For example, examples of machine-readable storage media may include RAM (random access memory), flash memory, phase change memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. The machine-readable medium may be embodied in a computer program product.

[0181] A software module may include a single instruction or multiple instructions and may be distributed across several different code segments, between different programs, and across multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a transmission module and a reception module. Each software module may reside in a single storage device or be distributed across multiple storage devices. For example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During execution of a software module, the processor may load some instructions into a cache memory to increase access speed. One or more cache memory lines may then be loaded into a general register file for execution by the processor. When referring to the functions of a software module below, it should be understood that such functions are implemented by the processor when executing instructions from that software module.

[0182] Moreover, any connection is properly termed a computer-readable medium. For example, if the software is transferred from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray Disks, where magnetic disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). The phrase "computer-readable medium" does not refer to a transient propagating signal. Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above are also intended to be included within the scope of computer-readable media.

[0183] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored thereon (and / or encoded thereon) instructions, the instructions being executable by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and illustrated in the accompanying figures.

[0184] Further, it should be understood that, if applicable, the modules and / or other suitable components for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station. For example, such a device can be coupled to a server to facilitate the transmission of components for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage component (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that the user terminal and / or base station can obtain the various methods when the storage component is coupled or provided to the device. In addition, any other suitable technology for providing the methods and techniques described herein to a device can be utilized.

[0185] It should be understood that the claims are not limited to the precise configuration and components described above, and that various modifications, changes, and variations may be made in the arrangement, operation, and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Receiving a single media access control element MAC CE, wherein the single MAC CE activates multiple physical downlink shared channels PDSCH transmission configuration indicators TCI state identifiers ID; receiving a single downlink control information (DCI) scheduling a PDSCH from a plurality of transmission reception points, wherein the DCI includes a single TCI code point value; determining at least two activated PDSCH TCI state IDs for at least two frequency resource sets among the plurality of activated PDSCH TCI state IDs based on the TCI code point value; and The PDSCH is processed according to the indicated TCI state ID.

2. The method according to claim 1, wherein the at least two frequency resource sets include at least one of the following: Multiple component carriers CC; or A plurality of bandwidth parts BWP.

3. The method according to claim 2, wherein: The determination is based on a mapping of the TCI code point value to the TCI state ID. 4 . The method of claim 3 , further comprising receiving signaling indicating a list of CCs, and the same mapping is applied to all CCs in the list and corresponding BWPs.

5. The method of claim 3 , further comprising receiving signaling indicating the mapping via: activating the MAC CE of the multiple PDSCH TCI state IDs; or Separate MAC CE.

6. A method for wireless communication performed by a network entity, the method comprising: Sending a single media access control element MAC CE, wherein the single MAC CE activates multiple physical downlink shared channels PDSCH transmission configuration indicators TCI state identifiers ID; determining a single TCI codepoint value associated with at least two activated PDSCH TCI state IDs for at least two frequency resource sets among the plurality of activated PDSCH TCI state IDs; as well as Single downlink control information (DCI) is transmitted, the single DCI scheduling PDSCHs from multiple transmission reception points, wherein the DCI includes the TCI code point value.

7. The method according to claim 6, wherein the at least two frequency resource sets include at least one of the following: Multiple component carriers CC; or A plurality of bandwidth parts BWP.

8. The method according to claim 7, wherein: The determination is based on a mapping of the TCI code point value to the TCI state ID.

9. The method of claim 8, further comprising sending signaling indicating a list of CCs, and the same mapping is applied to all CCs in the list and corresponding BWPs.

10. The method of claim 8, further comprising sending signaling indicating the mapping via: activating the MAC CE of the multiple PDSCH TCI state IDs; or Separate MAC CE.

11. An apparatus for wireless communication, comprising means for performing the method according to any one of claims 1 to 10.

12. A computer-readable medium having instructions stored thereon, which, when executed by a processor, cause the processor to perform the method of any one of claims 1-10.

13. A computer program product comprising computer instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 10.

Images