Single DCI and multi-TRP unified TCI activation design

Abstract

This disclosure provides systems, methods, and apparatus, including computer storage media for communicating between a base station having two transmit receive points (TRPs) and a UE based on a single DCI. The UE receives a single downlink control information (DCI) for the UE, the UE being configured with a first unified transmit configuration indication (TCI) state for a first TRP and a second unified TCI state for a second TRP. The DCI includes at least a first TCI field. The UE updates a configuration of at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on the at least one TCI field. The UE communicates with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority to U.S. Non - Provisional Application No. 18 / 499,712, filed on November 1, 2023, entitled "SINGLE DCI AND MULTIPLE TRP UNIFIED TCI ACTIVATION DESIGN", U.S. Provisional Application No. 63 / 422,342, filed on November 3, 2022, entitled "SINGLE DCI AND MULTIPLE TRP UNIFIED TCI ACTIVATION DESIGN", and U.S. Provisional Application No. 63 / 447,844, filed on February 23, 2023, entitled "SINGLE DCI AND MULTIPLE TRP UNIFIED TCI ACTIVATION DESIGN", all of which are assigned to the assignee of this application and are hereby incorporated by reference in their entireties. Technical Field

[0003] This disclosure relates to wireless communications including a single downlink control information (DCI) and multiple transmit - receive point (TRP) unified transmit configuration indicator (TCI) design.

[0004] Description of Related Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system 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.

[0006] These multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (such as related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Summary of the Invention

[0007] The systems, methods, and devices of the present disclosure each have several innovative aspects, and no single aspect is solely responsible for the desired attributes disclosed herein.

[0008] One innovative aspect of the subject matter described in the present disclosure can be implemented in a method for communicating with one or more transmission reception points (TRPs) based on one or more unified transmission configuration indicator (TCI) states. The method includes receiving a single downlink control information (DCI) for a user equipment (UE) that is configured with a first unified transmission configuration indicator (TCI) state for a first transmission reception point (TRP) and a second unified TCI state for a second TRP, where the DCI includes at least a first TCI field. The method includes updating the configuration of at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field. The method includes communicating with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

[0009] The present disclosure also provides an apparatus (e.g., a UE) including a memory storing computer-executable instructions and at least one processor configured to execute the computer-executable instructions to perform at least one of the above methods, an apparatus including units for performing at least one of the above methods, and a non-transitory computer-readable medium storing computer-executable instructions for performing at least one of the above methods.

[0010] One innovative aspect of the subject matter described in this disclosure can be implemented in a method for communicating with a UE via one or more TRPs at a network node. The method includes sending a single downlink control information (DCI) to a user equipment (UE) configured with a first unified transmit configuration indication (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, where the DCI includes at least a first TCI field. The method includes updating the UE's configuration for at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field. The method includes communicating with the UE via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

[0011] This disclosure also provides an apparatus (e.g., a BS) including a memory storing computer-executable instructions and at least one processor configured to execute the computer-executable instructions to perform at least one of the above methods, an apparatus including units for performing at least one of the above methods, and a non-transitory computer-readable medium storing computer-executable instructions for performing at least one of the above methods.

[0012] Details of one or more specific implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures are not drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0014] Figure 2A is a diagram illustrating an example of a first frame.

[0015] Figure 2B is a diagram illustrating an example of DL channels within a subframe.

[0016] Figure 2C is a diagram illustrating an example of a second frame.

[0017] Figure 2D is a diagram illustrating an example of a subframe.

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

[0019] Figure 4It is a diagram illustrating an exemplary decomposed base station architecture.

[0020] Figure 5 It is a diagram illustrating a first example of transmission involving multiple transmit-receive points (TRPs).

[0021] Figure 6 It is a diagram illustrating an example of downlink control information (DCI) for indicating a transmission configuration indication (TCI) state for one or more TRPs.

[0022] Figure 7 It is a timing diagram illustrating an example application time for a TCI state.

[0023] Figure 8 It is a message diagram illustrating various messages for configuring a unified TCI state for two TRPs.

[0024] Figure 9 It is a conceptual data flow diagram illustrating the data flow between different components / elements in an exemplary base station.

[0025] Figure 10 It is a conceptual data flow diagram illustrating the data flow between different components / elements in an exemplary user equipment (UE).

[0026] Figure 11 It is a flowchart of an example method for a UE to communicate with a base station having two TRPs based on a single DCI.

[0027] Figure 12 It is a flowchart of another example method for a UE to communicate with a base station having two TRPs based on a single DCI.

[0028] Figure 13 It is a flowchart of an example method for a network node to communicate with a UE via two TRPs based on a single TRP.

[0029] Figure 14 It is a flowchart of another example method for a network node to communicate with a UE via two TRPs based on a single TRP.

[0030] The same reference numerals and names in different figures represent the same elements. Detailed Description

[0031] For purposes of describing innovative aspects of the present disclosure, the following description refers to certain specific implementations. However, those of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. Some examples in the present disclosure are based on wireless and wired local area network (LAN) communications according to Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standards, IEEE 802.3 Ethernet standards, and IEEE 1901 power line communication (PLC) standards. However, the specific implementations described can be implemented in any device, system, or network capable of transmitting and receiving RF signals according to any one of the following wireless communication standards: including any one of the IEEE 802.11 standards, standards, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, High-Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), Evolved High-Speed Packet Access (HSPA+), Long-Term Evolution (LTE), AMPS, or other known signals for communication within a wireless network, cellular network, or Internet of Things (IoT) network (such as a system utilizing technologies of 3G, 4G, or 5G or further specific implementations thereof).

[0032] Traditionally, in a wireless communication network such as a 5G NR network, a Transmission Configuration Indicator (TCI) state is used to indicate the attributes of a transmission. For example, the TCI state can indicate the Quasi-Co-Location (QCL) relationship between an antenna port and a reference signal. The TCI state can be indicated for each transmission. For example, the Downlink Control Information (DCI) or Semi-Persistent Scheduling (SPS) configuration for a transmission can indicate the TCI state. The TCI state for a control channel can be configured separately. Unified TCI can be applicable to multiple transmissions and transmission types. For example, the Downlink (DL) only unified TCI is applicable to at least the UE-dedicated Physical Downlink Shared Channel (PDSCH) and Physical Downlink Control Channel (PDCCH). The Uplink (UL) only unified TCI is applicable to at least the UE-dedicated Physical Uplink Shared Channel (PUSCH) and Physical Uplink Control Channel (PUCCH). The Joint UL / DL unified TCI state is applicable to at least PDSCH, PDCCH, PUSCH, and PUCCH. The unified TCI state can also be optionally configured by RRC to be applicable to: non-UE-dedicated PDCCH and PDSCH, aperiodic CSI-RS for Channel State Information (CSI), aperiodic CSI-RS for Beam Management (BM), the Sounding Reference Signal (SRS) for codebook or non-codebook antenna switching, or aperiodic SRS for BM.

[0033] The unified TCI state can be configured in an RRC pool and activated by a MAC-CE. For example, the RRC message can configure multiple TCI states. The MAC-CE can select a set of the configured TCI states as the activated TCI states, with each activated TCI state associated with a code point. The DCI (such as DCI format 1_1 or 1_2) can indicate the unified TCI from the activated TCI states. For example, the DCI can include a TCI field indicating the code point.

[0034] The DCI that specifies a unified TCI state can be DCI format 1_1 or 1_2 with or without a downlink assignment scheduling. In the case of a downlink assignment, the TCI field in the DCI indicates the TCI for downlink transmission. In the case of no downlink assignment, the DCI can have a CRC scrambled with CS-RNTI, the redundancy version (RV) is set to all 1s, the modulation and coding scheme (MCS) is set to all 1s, and the new data indicator (NDI) is set to 0, and the frequency domain resource assignment (FDRA) is set to all 1s or all 0s. The TCI field indicates the TCI state ID (e.g., code point) of the activated TCI state. The PDSCH to HARQ feedback timing indicator field can be used to indicate the time offset from the DCI to its ACK in the PUCCH. The TDRA field can be used to derive the virtual PDSCH position, which is used to determine the position of the ACK information (acknowledging the DCI rather than the PDSCH). The TCI information can be applicable to the PDCCH after the activation time.

[0035] The unified TCI state is limited to a single transmit receive point (TRP) associated with a single unified TCI state. Therefore, the current unified TCI state cannot be used to configure transmissions involving multiple TRPs. Therefore, when the base station is associated with multiple TRPs, signaling is required to allow the configuration of the unified TCI state.

[0036] In one aspect, the present disclosure provides for configuring, updating, and selecting TCI states for multiple TRPs using a single DCI. The UE can be configured with a first unified TCI state for a first TRP and a second unified TCI state for a second TRP. The unified TCI state can initially be configured with RRC configuration and MAC-CE as discussed above, and the MAC-CE selects a set of activated TCI states. The UE can receive a single DCI including at least one TCI field. The UE can determine whether the TCI field is applicable to the first unified TCI state, the second unified TCI state, or both. The UE can update the configuration of at least one of the first TCI state or the second TCI state based on the unified TCI state to which the TCI field is applicable. Then, the UE can communicate with at least one of the first TRP or the second TRP based on the updated TCI state.

[0037] In one aspect, the DCI can include a dynamic TCI state indication field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception. The UE can start using the indicated TCI state to receive PDSCH reception from the application time after the DCI. That is, the UE can use the indicated TCI state to receive PDSCH reception scheduled by the DCI or other scheduling.

[0038] In one aspect, when the UE operates in multi-TRP mode and the DCI includes a single TCI field, the UE may remain in multi-TRP mode. One of these TCI states is updated based on the single TCI field. In some specific implementations, default rules indicate which TCI states are used for PDSCH reception. The UE continues to communicate using both TRPs.

[0039] Specific implementations of the subject matter described in this disclosure can be realized to achieve one or more of the following potential advantages. Configuring multiple TCI states using a single DCI can simplify signaling for multiple TRPs. The UE can be configured with fewer control resource sets (CORESETS) to search for DCI and can search fewer DCI formats, which can save power and / or use resources more efficiently. Additionally, using multiple TRPs can improve reliability and / or throughput.

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

[0041] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a “processing system” that includes 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, system on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. A processor can include an interface or be coupled to an interface that can obtain or output signals. A processor can obtain signals via the interface and output signals via the interface. In some particular implementations, the interface can be a printed circuit board (PCB) trace. In some other particular implementations, the interface can include a wireless transmitter, a wireless transceiver, or a combination thereof. For example, the interface can include a radio frequency (RF) transceiver that can be implemented to receive or transmit signals, or both. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, executing threads, processes, functions, etc.

[0042] Thus, in one or more example implementations, the functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded on a computer-readable medium as one or more instructions or code. A computer-readable medium includes computer storage media, which can be referred to as non-transitory computer-readable media. Non-transitory computer-readable media may not include transitory signals. A storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the foregoing types of computer-readable media, or any other medium capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0043] Figure 1FIG. is a diagram illustrating an example of a wireless communication system and an 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 (high-power cellular base station) or a small cell (low-power cellular base station). Macro cells include base stations. Small cells include femtocells, picocells, and microcells. Small cells include femtocells, picocells, and microcells. The base station 102 may be configured with a split RAN (D-RAN) or an open RAN (O-RAN) architecture, where functionality is split among multiple units (such as a central unit (CU), one or more distributed units (DU), or radio units (RU)). Such an architecture may be configured to utilize a protocol stack that is logically split between one or more units (such as one or more CUs and one or more DUs). In some aspects, the CU may be implemented within an edge RAN node, and in some aspects, one or more DUs may be co-located with the CU or may be geographically distributed among one or more RAN nodes. The DU may be implemented to communicate with one or more RUs. A network node may include one or more of the base station 102, CU, DU, or RU.

[0044] In some embodiments, one or more of the UEs 104 may include a unified TCI component 140 configured to communicate via two TRPs based on a single DCI. The unified TCI component 140 includes a DCI component 142 configured to receive a single DCI for the UE configured with a first unified TCI state for a first TRP and a second unified TCI state for a second TRP. The DCI includes at least a first TCI field. The unified TCI component 140 includes a TCI update component 144 configured to update the configuration of at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on at least one TCI field. The unified TCI component 140 includes a communication component 146 configured to communicate with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state. In some embodiments, the DCI includes a dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state is applicable for PDSCH reception starting from an application time after the single DCI. In such embodiments, the communication component 146 is configured to receive PDSCH reception after the application time using at least one of the first TRP or the second TRP based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field.

[0045] In some specific implementations, one or more of the base stations 102 may include a unified TCI control component 120 configured to indicate the unified TCI status of two TRPs with a single DCI. The unified TCI control component 120 may include a DCI component 122 configured to send a single DCI to a UE configured with a first unified TCI status for a first TRP and a second unified TCI status for a second TRP. The DCI includes at least a first TCI field. The unified TCI control component 120 includes a configuration component 124 configured to update the UE's configuration for at least one of the first unified TCI status to a first updated unified TCI status or the second unified TCI status to a second updated unified TCI status based on at least one TCI field. The unified TCI control component 120 includes a communication component 126 configured to communicate with the UE via at least one of the first TRP or the second TRP based on the first updated unified TCI status or the second updated unified TCI status. Communication. In some specific implementations, the DCI includes a dynamic TCI selection field indicating whether the first unified TCI status or the second unified TCI status applies to the physical downlink shared channel (PDSCH) reception starting from the application time after the single DCI. In such specific implementations, the communication component 126 is configured to send the PDSCH via at least one of the first TRP or the second TRP after the application time based on the first unified TCI status or the second unified TCI status indicated by the dynamic TCI selection field.

[0046] The base stations 102 configured for 4G 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 (such as the S1 interface), which can be wired or wireless. The base stations 102 configured for 5G NR (which are collectively referred to as the Next Generation RAN (NG-RAN)) can interact with the core network 190 via a second backhaul link 184, where the second backhaul link 184 can be wired or wireless. In addition to other functions, the base stations 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (such as handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (such as via the EPC 160 or the core network 190) on a third backhaul link 134 (such as the X2 interface). The third backhaul link 134 can be wired or wireless.

[0047] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, 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 including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which can serve a restricted group called a closed subscriber group (CSG). The communication link 112 between base station 102 and UE 104 may include an UL (also referred to as the reverse link) transmission from UE 104 to base station 102 or a DL (also referred to as the forward link) transmission from base station 102 to UE 104. The communication link 112 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (such as 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (such as, more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCell).

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

[0049] The wireless communication system may further include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0050] The small cell 102' may operate in licensed or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may adopt NR and use the same 5 GHz unlicensed spectrum as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may boost the coverage of the access network or increase the capacity of the access network.

[0051] Whether it is the small cell 102' or a large cell (such as a macro base station), the base station 102 may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations (such as the gNB 180) may operate in one or more frequency bands within the electromagnetic spectrum.

[0052] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as the Frequency Range Designation FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. A similar naming issue sometimes occurs with FR2. Although it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) determined by the International Telecommunication Union (ITU) as the "millimeter wave" (mmW) band, it is generally (interchangeably) referred to as the "millimeter wave" band in various documents and articles. Communication using the mmW radio frequency band has extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for this path loss and short range.

[0053] Considering the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, terms such as "sub-6 GHz" may generally represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" etc. is used in this article, it may generally represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band. Communication using the mmW radio frequency band has extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for this path loss and short range.

[0054] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the Serving Gateway 166, which itself 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 an IP service 176. The IP service 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for MBMS transmissions sent by content providers, may be used to authorize and initiate MBMS bearer services in 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 for a particular broadcast service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0055] 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. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, or other IP services.

[0056] The base station may include or be referred to as a gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of the UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (such as MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some UEs 104 may be referred to as IoT devices (such as parking meters, fuel pumps, ovens, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0057] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies, including future 6G technologies.

[0058] Figure 2A FIG. 200 is a diagram illustrating an example of a first frame. Figure 2B FIG. 230 is a diagram illustrating an example of DL channels within a subframe. Figure 2C FIG. 250 is a diagram illustrating an example of a second frame. Figure 2D FIG. 280 is a diagram illustrating an example of a subframe. The 5G NR frame structure may be FDD, where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL, or it may be TDD, where for a specific set of subcarriers (carrier system bandwidth), the subframes in the set of subcarriers are dedicated to both DL and UL. A subset of the total cell bandwidth of a cell is referred to as a bandwidth part (BWP), and bandwidth adaptation is achieved by configuring the UE with a BWP and informing the UE which of the configured BWPs is the current active BWP. In one aspect, a narrow bandwidth part (NBWP) refers to a BWP having a bandwidth less than or equal to the maximum configurable bandwidth of the BWP. The bandwidth of the NBWP is less than the carrier system bandwidth.

[0059] In Figure 2A, Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and X can be flexibly used between DL / UL, and subframe 3 is configured with slot format 34 (where most are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are full DL and full UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by receiving a slot format indicator (SFI) (configured dynamically via downlink control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0060] Other wireless communication technologies may have different frame structures or different channels. One frame (10 milliseconds (ms)) can be divided into 10 equally sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini-slots, which can include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot can include 14 symbols, and for slot configuration 1, each slot can include 7 symbols. The symbols on the DL can be cyclic prefix (CP) OFDM (CP - OFDM) symbols. The symbols on the UL can 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 slots within a subframe is based on the slot configuration and numerology. For slot configuration 0, the different numerologies μ0 to 5 allow each subframe to have 1, 2, 4, 8, 16, and 32 slots respectively. For slot configuration 1, the different numerologies 0 to 2 allow each subframe to have 2, 4, and 8 slots respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols per slot and 2 μ slots per subframe. The sub - carrier spacing and symbol length / duration are functions of the numerology. The sub - carrier spacing can be equal to 2 μ *15 kHz, where μ is the numerology from 0 to 5. Thus, the sub - carrier spacing for numerology μ = 0 is 15 kHz, and the sub - carrier spacing for numerology μ = 5 is 480 kHz. The symbol length / duration is negatively correlated with the sub - carrier spacing. Figures 2A to 2DAn example of a slot configuration 0 with 14 symbols per slot and a parameter set μ = 2 with 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).

[0061] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (RE). The number of bits carried by each RE depends on the modulation scheme.

[0062] As Figure 2A illustrated, some of the REs in the RE carry reference (pilot) signals (RS) for the UE. The RS can include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R x , where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signal (CSI-RS). The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0063] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCE), each CCE including nine resource element groups (REG), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) can be in symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and L1 identity. The secondary synchronization signal (SSS) can be in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the L1 cell identity group number and radio frame timing. Based on the L1 identity and the L1 cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can 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 (SSB). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted by the PBCH (such as system information blocks (SIB)) and paging messages.

[0064] As Figure 2CAs illustrated, some of the REs in the RE carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can send the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the combs in the comb structure. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0065] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), or UCI.

[0066] Figure 3FIG. is a diagram illustrating an example of a base station 310 and a UE 350 in an access network. In DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (such as, MIB, SIB), RRC connection control (such as, RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the 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 via HARQ, priority handling, and logical channel prioritization.

[0067] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes 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 such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM). The encoded and modulated symbols may be split into parallel streams. Each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot) in the time domain or frequency domain, and combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is precoded in space to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 or channel condition feedback. Each spatial stream may be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX modulates an RF carrier with the corresponding spatial stream for transmission.

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

[0069] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between the transport channel and the logical channel, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for supporting HARQ operations using error detection with the ACK or NACK protocol.

[0070] Similar to the functionality described in connection with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (such as 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 the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between the logical channel and the transport channel, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0071] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate decoding 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 a separate transmitter 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0072] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0073] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between the transport channel and the logical channel, packet reassembly, decryption, 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 supporting HARQ operations using error detection with the ACK or NACK protocol.

[0074] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects associated with Figure 1 the unified TCI component 140. For example, memory 360 may include executable instructions that define the unified TCI component 140. TX processor 368, RX processor 356, and / or controller / processor 359 may be configured to execute the unified TCI component 140.

[0075] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects associated with Figure 1 the unified TCI control component 120. For example, memory 376 may include executable instructions that define the unified TCI control component 120. TX processor 316, RX processor 370, and / or controller / processor 375 may be configured to execute the unified TCI control component 120.

[0076] Figure 4 FIG. is a diagram illustrating an example disaggregated base station 400 architecture. The disaggregated base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with the core network 420 via a backhaul link or indirectly with the core network 420 through one or more disaggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (non RT) RIC 415 associated with a service management and orchestration (SMO) framework 405, or both). The CU 410 may communicate with one or more distributed units (DUs) 430 via a respective midhaul link (such as an F1 interface). The DU 430 may communicate with one or more radio units (RUs) 440 via a respective fronthaul link. The RU 440 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 440.

[0077] Each of the units (i.e., CU 410, DU 430, RU 440, and the near RT RIC 425, non-RT RIC 415, and SMO framework 405) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or transmit signals to one or more of the other units on a wireless transmission medium, or both.

[0078] In some aspects, the CU 410 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 410. The CU 410 may be configured to handle user plane functionality (i.e., central unit - user plane (CU-UP)), control plane functionality (i.e., central unit - control plane (CU-CP)), or a combination thereof. In some embodiments, the CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 410 may be implemented to communicate with the DU 430 for network control and signaling.

[0079] The DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, the DU 430 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially depending on a functional split (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 430 or with control functions hosted by the CU 410.

[0080] Lower layer functionality may be implemented by one or more RUs 440. In some deployments, the RUs 440 controlled by the DU 430 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least partially based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 440 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control and user plane communication with the RUs 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the implementation of the DU 430 and the CU 410 in a cloud-based RAN architecture (such as a vRAN architecture).

[0081] The SMO framework 405 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 405 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 490) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 410, DU 430, RU 440, and the Near RT RIC 425. In some specific implementations, the SMO framework 405 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 411) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 can communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 can also include the Non-RT RIC 415 configured to support the functionality of the SMO framework 405.

[0082] The Non-RT RIC 415 can be configured to include logical functions that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the Near RT RIC 425. The Non-RT RIC 415 can be coupled to or communicate with the Near RT RIC 425 (such as via the A1 interface). The Near RT RIC 425 can be configured to include logical functions that can enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 410, one or more DUs 430, or both, and the O-eNB to the Near RT RIC 425.

[0083] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 425, the non-RT RIC 415 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 425 and can be received from non-network data sources or from network functions at the SMO framework 405 or the non-RT RIC 415. In some examples, the non-RT RIC 415 or the near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 415 may monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 405 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0084] Figure 5 FIG. 500 is a diagram illustrating an example of transmissions involving multiple TRPs. The base station 502 may include two or more TRPs (e.g., a first TRP 510 and a second TRP 512). The base station 502 may define various TCI states, which may be configured for the UE 504 via RRC signaling and activated via MAC-CE and / or DCI signaling. For example, the base station 502 may configure a first TCI state 520 associated with the first TRP 510 and a second TCI state 522 associated with the second TRP 512. In each of the TCI states 520 and 522, the corresponding TRP may transmit reference signals 530, 532. The UE 504 may determine the corresponding QCLs 550, 552 based on the reference signals and use the corresponding QCLs 550, 552 to receive the corresponding downlink signals (e.g., PDSCHs 440, 442).

[0085] In one aspect, when the base station includes multiple TRPs, the downlink transmission may be performed from one of these TRPs, from these two TRPs separately, or from these two TRPs as a single-frequency network (SFN) transmission. For example, if the base station 502 transmits from a single TRP (e.g., TRP 510), the UE 504 may receive the transmission (e.g., PDSCH 540) based on the TCI state 520 and the associated QCL 550. When the base station transmits separately from these two TRPs, the PDSCHs 540 and 542 may be associated with different beams. In addition, the PDSCHs 540 and 542 may be transmitted on different DMRS ports, different layers, or different resource blocks and symbols. The UE 504 may receive each of the PDSCHs 540 and 542 using the corresponding TCI states 520, 522 and the corresponding QCLs 550, 552, respectively.

[0086] For SFN transmission, the base station 502 may configure a third TCI state 524, where the base station transmits jointly from both the first TRP 510 and the second TRP 512. In the third TCI state 524, both the first TRP 510 and the second TRP 512 may transmit a third reference signal 534 as an SFN transmission. The UE 504 may receive the third reference signal 534, determine the third QCL 554, and receive the SFN PDSCH 544 based on the third QCL 554. Thus, the SFN transmission is transparent to the UE 504 because the UE 504 determines the QCL based on the reference signal in the same manner for both single-TRP transmission and SFN transmission.

[0087] Figure 6 FIG. is an illustration of an example DCI 600 for indicating a TCI state for one or more TRPs. The DCI 600 may be based on DCI format 1_1 and may be used to schedule downlink transmissions. In some embodiments, DCI format 1_1 may be extended to include the information discussed herein, or a new DCI format may be defined to provide transmission parameters for different transport block types. In some embodiments, DCI format 1_2 may include similar fields. Additionally, DCI format 1_1 or DCI format 1_2 may have a CRC scrambled with a CS-RNTI and include fixed values in some fields to indicate a TCI configuration update without a downlink schedule. The DCI indicating the TCI configuration, whether or not there is a downlink schedule, may be referred to as a beam indication instance.

[0088] The DCI 600 may include multiple fields, such as a carrier indicator field 602, a format identifier field 604, a BWP indicator field 606, an FDRA field 608, a TDRA field 610, a VRB-to-PRB mapping field 612, a PRB binding size indicator field 614, a rate matching indicator field 616, a ZP CSI-RS trigger field 618, an MCS field 620, a new data indicator field 622, a redundancy version field 624, a HARQ process number field 626, a downlink assignment index field 628, a TPC command field 630, a PUCCH resource indicator field 632, a PDSCH-to-HARQ timing indicator field 634, an antenna port field 636, a TCI field 638, an SRS request field 640, a CBGTI field 642, a CBGFI field 644, and / or a DMRS sequence field 646. In some embodiments, depending on parameters configured by a higher layer, some fields (e.g., indicated by a vertical hatching pattern) are optional or variable in length.

[0089] In some specific implementations, when a base station (e.g., base station 502) is configured with a first TRP 510 and a second TRP 512, the TCI field 638 may indicate one of the two TRPs or one or more DL, UL, or combined unified TCI states in a component carrier (CC) or a bandwidth part (BWP) or a set of CC / BWPs in a CC list. For example, the carrier indicator field 602 or the BWP indicator field 606 may indicate the CC / BWP.

[0090] In some specific implementations, the TCI field 638 may indicate a single DL, UL, or combined unified TCI state only for a component carrier (CC) or a bandwidth part (BWP) or one of the two TRPs in a set of CC / BWPs in a CC list. In such specific implementations, further information may be required to indicate which of the two TRPs the TCI field 638 applies to. For example, the DCI 600 may include a dynamic TCI selection field 660 to associate the TCI field 638 with one of the first TRP 510 or the second TRP 512, or with the associated unified TCI state. As another example, a second TCI field 650 may be included to indicate the TCI state for the second TRP 512, and the TCI field 638 may be understood to indicate the TCI state for the first TRP 510.

[0091] When the base station is configured with a first TRP 510 and a second TRP 512, receiving a DCI with a single TCI field may involve the interpretation by the UE 104. In some specific implementations, the UE may be configured to interpret a DCI with a single TCI field to indicate a single TRP mode in which only the indicated TCI state is used. In some specific implementations, the UE may assume that the multi-TRP mode is still used, but only update one of these unified TCI states based on the single TCI field. The UE may be configured by RRC configuration or according to rules to interpret a DCI with a single TCI field.

[0092] In some specific implementations, when the UE is configured with a multi-TRP mode (e.g., having unified TCI states for both the first TRP 510 and the second TRP 512), not all PDSCH assignments will use the two indicated TCIs. For example, the base station 502 may determine to use single-TRP transmission of the PDSCH 540 from the first TRP 510. The DCI field in DCI format 1_1 / 1_2 may be used to indicate which of the indicated combined / DL TCI states the UE should apply to PDSCH reception starting from the application time (if defined) after DCI format 1_1 / 1_2. For example, the DCI field may be the dynamic TCI selection field 660.

[0093] If two unified TCI states are indicated for the scheduled or activated PDSCH, the dynamic TCI selection field 660 may indicate which TCI state to use. In some specific implementations, the effect of the dynamic TCI selection field 660 may be sticky. That is, the TCI state indicated by the dynamic TCI selection field 660 may be used for all subsequent PDSCHs until the selection changes. In some specific implementations, in the case where the DCI 600 including the dynamic TCI selection field 660 schedules the PDSCH, the effect of the dynamic TCI selection field 660 may only apply to the scheduled PDSCH. The dynamic TCI selection field 660 may be an optional field, and its presence may be configured via RRC configuration.

[0094] In some specific implementations, in the case of sDCI mTRP, instead of using DCI to indicate the sticky sTRP / mTRP mode, for example, via indicating the code points mapped to a single TCI or two TCIs, the sticky sTRP / mTRP mode may be indicated by other signaling. In the first example, the RRC indicates the sticky sTRP / mTRP mode. For example, if any channel is configured to follow the 1st TCI and / or the 2nd TCI, this means that the sticky mTRP mode is enabled and 2 active TCIs must be indicated. For example, if the dedicated flag indicates the sTRP mode, all the configured indications on the following 1st TCI and / or 2nd TCI are ignored. In the second example, the MAC-CE indicates the sticky sTRP / mTRP mode. For example, if the MAC-CE may have code points mapped to both the 1st TCI and the 2nd TCI, only the 1st TCI, or only the 2nd TCI. For example, if one of the two TCIs mapped to the code point has a reserved value, this means that the TCI is empty / invalid. This means that the sticky mTRP mode is enabled and 2 TCIs are always indicated. The base station (such as a gNB) may update each of the 1st and 2nd indicated TCIs respectively by indicating the corresponding code point (for example, the code point mapped only to the 1st TCI). This saves code points compared to activating all TCI combinations. For example, if the MAC-CE only has all the code points mapped to 1 TCI without the TCI order index. This means that the sticky sTRP mode is enabled and 1 TCI is always indicated. For example, the MAC-CE has a flag explicitly indicating whether the sticky sTRP or mTRP mode is enabled. The sticky mTRP mode maps each code point to 1 or 2 TCIs with the corresponding order index. The sticky sTRP mode maps each code point to 1 TCI without the corresponding order index or is ignored.

[0095] In some specific implementations, when two unified TCI states are configured or indicated for a component carrier or a bandwidth part or a set of component carriers or bandwidth parts in a component carrier list, UE 104 may not expect the dynamic TCI selection field 660 to be absent. For example, after the activation time of the indicated TCI, UE 104 may expect the dynamic TCI selection field 660 to be present in the DCI of the received scheduled transmission. In some specific implementations, if the dynamic TCI selection field 660 is absent, UE 104 may apply a default unified TCI state. The default unified TCI state may be determined by RRC configuration or a fixed rule. The RRC configuration of the default rule may be included in the PDSCH configuration information element. An example fixed default rule may be to always use the first indicated TCI or always use the TCI of the scheduled PDCCH. In some specific implementations, the default rule may be to use both the first unified TCI and the second unified TCI. That is, the absence of the dynamic TCI selection field 660 may not result in a dynamic switch between the single-TRP mode and the multi-TRP mode. The default rule of using both the first unified TCI and the second unified TCI (e.g., when two TCI states have not been indicated) may use the lowest activation code point that supports two TCI states. For example, the default rule may be applied before UE receives the DCI indicating the TCI state (e.g., after initial access to the network or after beam failure recovery).

[0096] In some specific implementations, the PDSCH scheduled by DCI without a dynamic TCI selection field 660 may follow separate or additional default rules. When the PDSCH scheduling offset is greater than the time duration of QCL, the default rules for the PDSCH may be applied. In a first example, for DCI format 1_1 or 1_2 without a dynamic TCI selection field 660, all the indicated TCI states may be applied to the scheduled PDSCH. As another example, based on whether single-frequency network (SFN) transmission is configured or PDCCH repetition is configured, there may be separate default rules for DCI format 1_0 without a dynamic TCI selection field 660. For the first rule, if the scheduling CORESET is indicated for scheduling SFN transmission and SFN transmission for the PDSCH is configured, then the 2 TCI states of the scheduling SFN CORESET may be applied to the PDSCH. Otherwise (if SFN transmission for the PDSCH is not configured), the first TCI state or the second TCI state of the scheduling SFN CORESET may be applied to the PDSCH. For the second rule, if the scheduling CORESET is configured with PDCCH repetition with a search space having two links, UE 104 may select the TCI state of the CORESET with the lowest ID for the PDSCH. For the third rule, if the scheduling CORESET is neither configured for SFN nor configured for PDCCH repetition, then the TCI of the scheduling CORESET may be applied to the PDSCH.

[0097] In some specific implementations, in the unified TCI architecture extension for S-DCI-based MTRP, the DCI field in DCI format 1_1 / 1_2 that schedules / activates PDSCH reception is used to determine which one or both of the indicated combined / DL TCI states should be applied to the scheduled / activated PDSCH reception. The presence of the DCI field may be configured by RRC; when the DCI field does not exist in DCI format 1_1 / 1_2, the UE shall apply the default indicated combined / DL TCI state to the PDSCH reception.

[0098] Technical issues related to the unified TCI framework extension include: details about the default indicated combined / DL TCI state for PDSCH reception; whether the DCI field is a new indicator field or an existing field (e.g., an existing TCI field); how to apply the indicated combined / DL TCI state to the PDSCH reception if the offset between the reception of DCI format 1_1 / 1_2 and the corresponding PDSCH reception is less than a threshold; and how to apply the indicated combined / DL TCI state to the PDSCH reception scheduled / activated by DCI format 1_0. The above applies to the case of PDSCH scheduled by the same DCI.

[0099] In some specific implementations, two TCIs may always be indicated for the mTRP mode, which is signaled via RRC or MAC-CE rather than DCI. In some specific implementations, the UE may support one or two default beams, which are reported as UE capabilities. Based on this report, when the time offset between the reception of DCI and the scheduling of PDSCH is less than a threshold, the UE will have different default beam behaviors. If the UE supports two default beams, two default beams will be used for reception. If the UE supports one default beam, reception will be from one default beam, e.g., from one TRP (i.e., following the configuration of the first indicated beam, and in this case the second indicated beam is not used for reception).

[0100] In some specific implementations, in the mTRP mDCI case, if the CORESET is configured to share the indicated TCI, the indicated TCI for the same CORESETPoolIndex associated with the CORESET is applied to both its PDCCH and the scheduled / activated PDSCH. Otherwise, in mDCI mTRP, the TCI for the PDCCH and PDSCH is determined in the legacy way. The PDCCH beam of the CORESET is configured by MAC-CE. The PDSCH follows the scheduled PDCCH beam.

[0101] In some specific implementations, the UE may be configured with a TCI associated with a non-serving cell physical cell ID (PCI), which is different from the PCI of the serving cell and is configured in an RRC list (e.g., SSB-MTC-AdditionalPCI). When the TCI associated with the non-serving cell PCI is configured as the active TCI for the CORESET, the UE does not need to monitor the PDCCH candidates for a specific PDCCH cell-specific search space (CSS) set (e.g., type 0 / 0A / 0B / 1 / 1A / 2 / 2A CSS set).

[0102] In some specific implementations, in the mDCImTRP case, when the UE is configured with SSB-MTC-AdditionalPCI, the CORESETs corresponding to different coresetPoolIndex values may be associated with different PCIs via the indicated joint / DL TCI state, where the CORESET corresponding to one coresetPoolIndex value is associated with the serving cell PCI, and the CORESET corresponding to another coresetPoolIndex value may be associated with a PCI different from the serving cell PCI, e.g., via the additionalPCI in the indicated joint / DL TCI state specific to the other coresetPoolIndex value.

[0103] In some specific implementations, in the sDCI case, the UE may report its ability to support the inter-cell beam management scenario. In the inter-cell beam management scenario, the TCI state within the active TCI code point or the indicated TCI may be associated with the non-serving cell PCI. In some specific implementations, when the UE supports the inter-cell beam management scenario and when two indicated TCIs are active for the UE, one indicated TCI shall be associated with the serving cell, while the other indicated TCI may be associated with the non-serving cell PCI.

[0104] In some specific implementations, when the UE is configured to perform a beam failure recovery procedure in the serving cell. When the UE detects a beam failure event associated with the indicated active TCI, the UE may transmit a beam failure request to the base station. The UE may additionally indicate a replacement beam in the beam failure request. After a predefined time upon receiving a response to the beam failure request, the UE starts monitoring the PDCCH in all CORESETs and receives the PDSCH and the aperiodic CSI-RS using the same antenna port quasi-co-location parameters as those associated with the replacement beam indicated in the beam failure request. When an RRC list of non-serving cell PCI is configured at the UE, the UE shall not report the replacement beam associated with the non-serving cell PCI.

[0105] In some specific implementations, in the mTRP mDCI case, when two SRS resource sets are configured for codebook (CB)- and / or non-codebook (NCB)-based transmission, if the SRS resource set is configured to follow the indicated joint / UL TCI state via the RRC flag followUnifiedTCIState, the UE may apply the indicated joint / UL TCI state specific to the coresetPoolIndex value to the SRS resource set for CB / NCB-based transmission associated with the same coresetPoolIndex value. When a single SRS resource set is configured for CB / NCB-based transmission, the base station may indicate which coresetPoolIndex value the UE shall use to select the indicated TCI for the SRS. Alternatively, the UE may always assume that a single SRS resource for CB / NCB-based transmission is always associated with the indicated TCI corresponding to a predefined coresetPoolIndex value (e.g., coresetPoolIndex 0). Additionally and alternatively, when the scheduling CORESET is configured to follow one of the indicated TCIs, the UE may apply the same indicated TCI as the CORESET to the SRS resource for CB / NCB transmission to schedule the SRS transmission.

[0106] In some specific implementations, the UE may report to the base station its ability of the minimum beam application time in different scenarios. For example, the UE may report different minimum beam application time capabilities for DL reception and UL transmission respectively. For the mDCImTRP case and the sDCI mTRP case, the UE may report different minimum beam application time capabilities. Based on the UE capability report, the base station may configure different beam application times for different scenarios at the UE. For example, the base station may configure different beam application time values for DL, UL, mTRPmDCI, and mTRP sDCI at the UE.

[0107] In some specific implementations, in the sDCI mTRP case, if the CORESET other than the CORESET with index 0 is only associated with the user-specific search space (USS) set and / or the type 3-PDCCH CSS set, the CORESET is configured by the RRC to apply the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both the first indicated joint / DL TCI state and the second indicated joint / DL TCI state to the PDCCH reception on the CORESET.

[0108] In some specific implementations, in the sDCI mTRP case, if the CORESET other than the CORESET with index 0 is associated with at least one CSS set other than the type 3-PDCCH CSS set and followUnifiedTCIstate = 'enabled' is configured for the CORESET, the CORESET is configured by the RRC to apply the first indicated joint / DL TCI state, the second indicated joint / DL TCI state, or both the first indicated joint / DL TCI state and the second indicated joint / DL TCI state to the PDCCH reception on the CORESET.

[0109] In some specific implementations, in the sDCI mTRP case, if the CORESET with index 0 is configured with followUnifiedTCIstate = 'enabled' and if the CORESET is associated with SS#0 for the type 0 / 0A / 2 CSS set, the CORESET is configured by the RRC to apply the first indicated joint / DL TCI state or the second indicated joint / DL TCI state to the PDCCH reception on the CORESET.

[0110] In some specific implementations, in the case of sDCI mTRP, if the CORESET with index 0 is configured with followUnifiedTCIstate = 'enabled', and if the CORESET is not associated with SS#0 for type 0 / 0A / 2 CSS sets, the CORESET is configured by RRC to apply the first indicated combined / DL TCI state, the second indicated combined / DL TCI state, or both the first indicated combined / DL TCI state and the second indicated combined / DL TCI state to PDCCH reception on the CORESET.

[0111] Figure 7 FIG. 700 is a timing diagram illustrating an example application time for a TCI state. After confirming the inclusion of the updated DCI 600, the update to the unified TCI state may become applicable. For example, when the DCI 600 includes the TCI field 638, in the case where the DCI 600 does not schedule the PDSCH 710 (i.e., no DL assignment), the TDRA field 610 can be used to determine the K0 parameter for the PDSCH 710 or the virtual PDSCH 712. The PDSCH to HARQ_feedback timing indicator field 634 can indicate the time slot for sending the ACK 720 to the PDSCH or the DCI 600. The unified TCI state indicated by the TCI field 638 can be applied after the ACK 720.

[0112] In one aspect, when the DCI 600 includes the dynamic TCI selection field 660 to dynamically switch the applicable TCI state, the UE may not need to wait for the ACK 720. The dynamic TCI selection time 730 can indicate when the indicated TCI state is applicable. For example, the dynamic TCI selection time 730 can be based on UE capabilities and / or RRC configuration. In some specific implementations, the dynamic TCI selection time 730 can be the same as the timeDurationForQCL parameter. For example, the application time of the new field should reuse the timeDurationForQCL because the new field is applied to the scheduled PDSCH. Since Release 15, the timeDurationForQCL has been defined. The UE can only comply with the DCI beam indication when the offset > timeDurationForQCL. Therefore, it may not be necessary to explicitly apply the time for only the dynamic TCI selection time 730, which can be regarded as another DCI beam indication.

[0113] If the PDSCH 710 is scheduled before the dynamic TCI selection time 730, the UE 104 may apply the default unified TCI state determined by RRC configuration or fixed rules to PDSCH reception. Before the application time, the UE buffers data with the default PDSCH beam. The default beam may be determined based on previously defined rules. In some specific implementations, the UE 104 may continue to use the previously selected unified TCI state until the dynamic TCI selection time 730. If the PDSCH 710 is scheduled after the dynamic TCI selection time 730, the UE 104 may apply the TCI state indicated by the dynamic TCI selection field. The selected TCI state may be the TCI state indicated in the scheduling DCI, the indicated unified TCI state active during the time slot of the PDSCH 710, or the indicated unified TCI state active during the time slot of receiving the DCI 600.

[0114] Figure 8 FIG. 800 is a message diagram illustrating various messages for configuring unified TCI states for two TRPs.

[0115] The UE 104 may optionally send a capability message 810. The capability message 810 may indicate, for example, the ability to use default rules for multiple TCIs or the ability to indicate the time for changing QCL.

[0116] The base station 502 may send an RRC configuration 820 via one or both of the TRPs 510, 512. The RRC configuration 820 may configure multiple TCI states including the unified TCI state. The base station 502 may send a MAC-CE 830 via one or both of the TRPs 510, 512. The MAC-CE 830 may select a set of TCI states configured as active TCI states, each active TCI state corresponding to a code point. In some specific implementations, the MAC-CE 830 may indicate that two TCI states are associated with the code point.

[0117] The base station 502 may send the first DCI 840 to the UE 104 via one or both of the TRPs 510 and 512, for example, based on the currently indicated unified TCI state for the PDCCH (e.g., combined or DL). The first DCI 840 may include at least the TCI field 638. In some specific embodiments, the TCI field 638 may apply to both of the TRPs 510 and 512. For example, the TCI field 638 may indicate code points associated with two TCI states. In other specific embodiments, the TCI field 638 may indicate a single TCI state. In some specific embodiments, the DCI 840 may include a second TCI field 650 that indicates a second code point for the second activated TCI state. Thus, when the first DCI 840 includes the TCI field 638 and the second TCI field 650, the UE 104 may determine two TCI states. In some specific embodiments, the first DCI 840 includes a dynamic TCI selection field 660 that specifies whether the TCI field 638 applies to the first unified TCI state corresponding to the first TRP 510 or to the second unified TCI state corresponding to the second TRP 512. Thus, the UE 104 may determine which of the unified TCI states the TCI field 638 indicating a single TCI state corresponds to.

[0118] At block 850, the UE 104 may update the unified TCI state based on the first DCI 840. For example, in the case where the first DCI 840 indicates two TCI states, the UE 104 may update each of the unified TCI states in the unified TCI state to an updated TCI state (e.g., update the configured value) with the corresponding TCI information indicated by the first DCI 840. In some specific embodiments, in the case where the first DCI 840 indicates a single TCI state, the UE 104 may update the unified TCI state indicated by the dynamic TCI selection field 660 without updating the other unified TCI state.

[0119] The base station 502 and the UE 104 may exchange communication 860 based on the unified TCI state. For example, the communication 860 may include PDSCH, PDCCH, PUSCH, and PUCCH, and may optionally include a reference signal that may be indicated by the unified TCI state. Thus, the base station 502 and the UE 104 may communicate according to the updated unified TCI state.

[0120] In one aspect, the base station 502 may send a second DCI 870 to the UE 104. The second DCI 870 may indicate the TRP to be used for the PDSCH. For example, the second DCI 870 may include a dynamic TCI selection field 660. For example, the dynamic TCI selection field 660 of the second DCI 870 may indicate only the second TRP 512. Even if a unified TCI state is configured for the first TRP 510, the UE 104 may use the second TRP 512 to switch to the single-TRP mode to receive the PDSCH 880. In some specific implementations, the base station 502 may send a subsequent DCI with the dynamic TCI selection field 660 to switch to the first TRP 510 or indicate both TRPs. In some specific implementations, the dynamic TCI selection field 660 of the second DCI 870 may apply only to the PDSCH 880 scheduled by the second DCI 870.

[0121] Figure 9 FIG. 900 is a conceptual data flow diagram illustrating the data flow between different components / elements in an exemplary base station 902, which may be an example of the base station 102 including a unified TCI control component 120. The unified TCI control component 120 may be implemented by Figure 3 the memory 376 and the TX processor 316, the RX processor 370, and / or the controller / processor 375. For example, the memory 376 may store executable instructions defining the unified TCI control component 120, and the TX processor 316, the RX processor 370, and / or the controller / processor 375 may execute these instructions.

[0122] The base station 102 may include a receiver component 970, which may include, for example, a radio frequency (RF) receiver for receiving the signals described herein. The base station 102 may include a transmitter component 972, which may include, for example, an RF transmitter for transmitting the signals described herein. In one aspect, the receiver component 970 and the transmitter component 972 may be co-located in a transceiver such as Figure 3 illustrated by the TX / RX 318 therein. Additionally, the receiver component 970 and the transmitter component 972 may each communicate via the first TRP 510 and the second TRP 512.

[0123] As discussed with respect to Figure 1 the unified TCI control component 120 may include a DCI component 122, a configuration component 124, and a communication component 126.

[0124] The receiver component 970 may receive UL signals from the UE 104, including UL communications such as the capability message 810 and the communication 860 (e.g., PUSCH and PUCCH). The receiver component 970 may provide the capability message 810 to the configuration component 124. The receiver component 970 may provide the communication to the communication component 126.

[0125] The configuration component 124 is configured to update the UE's configuration for at least one of the first unified TCI state to the first updated unified TCI state or the second unified TCI state to the second updated unified TCI state based on at least one TCI field. For example, the configuration component 124 may obtain the capability message 810 from the UE 104 via the receiver component 970. The configuration component 124 may determine the potential TCI states for the UE 104 to communicate with the base station 902 via the TRPs 510 and 512. The configuration component 124 may output the RRC configuration 820 and the MAC-CE 830 for transmission to the UE 104 via the transmitter component 972. The configuration component 124 may also output the active TCI state to the DCI component 122. The configuration component 124 may receive the indicated TCI state from the DCI component 122. The configuration component 124 may update the receiver component 970 with the Rx configuration and update the transmitter component 972 with the Tx configuration. The Rx configuration and the Tx configuration may be based on the updated unified TCI state for the UE 104.

[0126] The DCI component 122 may be configured to send a single DCI (e.g., the first DCI 840) to the UE 104, and the UE 104 is configured with a first unified TCI state for the first TRP and a second unified TCI state for the second TRP. The first DCI 840 includes at least a first TCI field 638. The DCI component 122 may obtain the active TCI state from the configuration component 124. The DCI component 122 may select the active TCI state, for example, based on the channel state information (CSI) received from the UE 104. The DCI component 122 may generate the first DCI 840 to include at least the first TCI field 638. Depending on the TCI state to be used, the DCI component 122 may additionally include a second TCI field 650 or a dynamic TCI selection field 660. The DCI component 122 may output the first DCI 840 for transmission via the transmitter component 972. In some embodiments, the DCI component 122 is further configured to generate a second DCI 870 including the dynamic TCI selection field 660. For example, the DCI component 122 may use the second DCI 870 to schedule the PDSCH 880. The dynamic TCI selection field 660 indicates whether the first unified TCI state or the second unified TCI state is applicable to the reception of the PDSCH 880 starting from the application time (e.g., the dynamic TCI selection time) 730 after the second DCI 870. The DCI component 122 may output the second DCI 870 for transmission via the transmitter component 972.

[0127] The communication component 126 is configured to communicate with the UE via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state. For example, the communication component 126 may receive UL communication 860 (e.g., PUSCH and PUCCH) via the receiver component 970 and send DL communication 860 (e.g., PDSCH and PDCCH) via the transmitter component 972. In such embodiments, the communication component 126 is configured to send the PDSCH via at least one of the first TRP or the second TRP after the application time based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field 660.

[0128] Figure 10 is a conceptual data flow diagram 1000 illustrating the data flow between different components / parts in the exemplary UE 104, and this exemplary UE may be the UE 104( Figure 1) example and includes a unified TCI component 140. The unified TCI component 140 may be implemented by the memory 360 and the TX processor 368, the RX processor 356, and / or the controller / processor 359. For example, the memory 360 may store executable instructions defining the unified TCI component 140, and the TX processor 368, the RX processor 356, and / or the controller / processor 359 may execute these instructions.

[0129] The UE 104 may include a receiver component 1070, which may include, for example, an RF receiver for receiving the signals described herein. The UE 104 may include a transmitter component 1072, which may include, for example, an RF transmitter for transmitting the signals described herein. In one aspect, the receiver component 1070 and the transmitter component 1072 may be co-located in a transceiver (such as Figure 3 the TX / RX 352 in).

[0130] As discussed with respect to Figure 1 the unified TCI component 140 may include a DCI component 142, a TCI update component 144, and a communication component 146. The unified TCI component 140 may optionally include a capability component 1010.

[0131] The receiver component 1070 may receive the DL signals described herein, such as the RRC configuration 820, the MAC-CE 830, the first DCI 840, the communication 860, the second DCI 870, and the PDSCH 880. The receiver component 1070 may provide the RRC configuration 820, the MAC-CE 830, the first DCI 840, and the second DCI 870 to the DCI component 142. The receiver component 1070 may provide the communication 860 and the PDSCH 880 to the communication component 146.

[0132] The DCI component 142 is configured to receive a single DCI for the UE 904, and the UE 904 is configured with a first unified TCI state (e.g., the first TCI state 520) for the first TRP 510 and a second unified TCI state (e.g., the TCI state 522) for the second TRP 512. For example, the DCI component 142 may receive, via the receiver component 1070, one of the first DCI 840 or the second DCI 870 from the base station 102. The DCI includes at least a first TCI field 638. In some embodiments, the DCI includes a second TCI field 650 or a dynamic TCI selection field 660. The DCI component 142 may output the fields of the TCI-related fields of the first DCI 840 or the second DCI 870 to the TCI update component 144.

[0133] The TCI update component 144 is configured to update the configuration of at least one of the first unified TCI state 520 to a first updated unified TCI state or the second unified TCI state 522 to a second updated unified TCI state based on at least one TCI field. For example, the TCI update component 144 may obtain the TCI field 638, the second TCI field 650, and / or the dynamic TCI selection field 660 from the DCI component 142. The TCI update component 144 may determine the unified TCI states 520, 522 indicating how many TCI states and to which configurations the indicated TCI states apply. For example, when the TCI field 638 or the combination of the TCI field 638 and the second TCI field 650 indicates two TCI states, the TCI update component 144 may update both the unified TCI states 520 and 522. When the TCI field 638 indicates only a single TCI state, the TCI update component 144 may use the dynamic TCI selection field 660 or a default rule to determine which unified TCI state 520, 522 is being updated. The TCI update component 144 may output the updated unified TCI state to the communication component 146.

[0134] The communication component 146 is configured to communicate with at least one of the first TRP 510 or the second TRP 512 based on the first updated unified TCI state 520 or the second updated unified TCI state 522. For example, the communication component 146 may receive the DL communication 860 via the receiver component 1070 and send the UL communication 860 via the transmitter component 1072. The communication component 146 may use the unified TCI state 520 and / or the unified TCI state 522 for the communication 860. For example, the communication component 146 may indicate the unified TCI states 520, 522 to configure the receiver component 1070 or the transmitter component 1072 (e.g., with the correct beam). In some specific implementations, in the case where the unified TCI states 520, 522 have not been indicated, the communication component 146 may communicate according to the default rule 1020. In some specific implementations, the communication component 146 may obtain the selected TRP for the PDSCH 880 from the DCI component 142. The communication component 146 is configured to receive PDSCH reception after the application time (e.g., the dynamic TCI selection time 730) using at least one of the first TRP or the second TRP based on the first unified TCI state or the second unified TCI state corresponding to the selected TRP.

[0135] The capability component 1010 may be configured to send an indication of the UE's capability to support the default rule. For example, the capability component 1010 may output a capability message 810 for transmission to the base station 102 via the transmitter component 1072.

[0136] Figure 11FIG. 1100 is a flowchart of an example method 1100 for a UE to communicate with a base station having two TRPs based on a single DCI. Method 1100 may be performed by a UE (such as UE 104, which may include a memory 360 and may be the entire UE 104 or a component of UE 104, such as the unified TCI component 140, the TX processor 368, the RX processor 356, or the controller / processor 359). Method 1100 may be performed by the unified TCI component 140 that communicates with the unified TCI control component 120 of the base station 102. Optional boxes are shown with dashed lines.

[0137] At block 1110, method 1100 may optionally include sending an indication of the UE's ability to support a default rule. In some implementations, for example, UE 104, the TX processor 368, or the controller / processor 359 may execute the unified TCI component 140 or the capability component 1010 to send an indication (e.g., a capability message 810) of the UE's ability to support the default rule 1020. Thus, UE 104, the TX processor 368, or the controller / processor 359 that executes the unified TCI component 140 or the capability component 1010 may provide the means for sending an indication of the UE's ability to support a default rule.

[0138] At block 1120, method 1100 may optionally include applying the default rule before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery. In some implementations, for example, UE 104, the RX processor 356, or the controller / processor 359 may execute the unified TCI component 140 or the communication component 146 to apply the default rule before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery. Thus, UE 104, the RX processor 356, or the controller / processor 359 that executes the unified TCI component 140 or the communication component 146 may provide the means for applying the default rule before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery.

[0139] At block 1130, method 1100 includes receiving a single DCI for a UE that is configured with a first unified TCI state for a first TRP and a second unified TCI state for a second TRP. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute unified TCI component 140 or DCI component 142 to receive the single DCI for the UE that is configured with the first unified TCI state for the first TRP and the second unified TCI state for the second TRP. In some implementations, the first unified TCI state or the second unified TCI state applies to both control channels and shared channels in the uplink direction, the downlink direction, or both the uplink and downlink directions. Accordingly, UE 104, RX processor 356, or controller / processor 359 that executes unified TCI component 140 or DCI component 142 may provide means for receiving the single DCI for the UE that is configured with the first unified TCI state for the first TRP and the second unified TCI state for the second TRP.

[0140] At block 1140, method 1100 includes configuring to update at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on at least one TCI field. In some implementations, for example, UE 104, RX processor 356, TX processor 368, or controller / processor 359 may execute unified TCI component 140 or TCI update component 144 to configure to update at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on at least one TCI field. In some implementations, the first TCI field applies to both a first TRP and a second TRP. In some implementations, in the case where a single DCI further includes a second TCI field applicable to the second TRP, block 1140 may include configuring to update the second TRP to a second updated unified TCI state based on the second TCI field. In some implementations, the first TCI field applies to one of a first TRP or a second TRP. The single DCI may further include a second field associating the first TCI field with one of the first TRP or the second TRP. In such implementations, the update configuration may include updating only the first TCI state or the second TCI state associated with the first TCI field. Thus, UE 104, RX processor 356, TX processor 368, or controller / processor 359 that executes unified TCI component 140 or TCI update component 144 may provide components for configuring to update at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on at least one TCI field.

[0141] At block 1150, method 1100 includes communicating with at least one of a first TRP or a second TRP based on a first updated unified TCI state or a second updated unified TCI state. In some implementations, for example, UE 104, RX processor 356, TX processor 368, or controller / processor 359 may execute unified TCI component 140 or communication component 146 to communicate with at least one of a first TRP or a second TRP based on a first updated unified TCI state or a second updated unified TCI state. In some implementations, at sub-block 1152, block 1150 may optionally include communicating only with a first TRP or a second TRP associated with a first TCI field. In some implementations, at sub-block 1154, block 1150 may optionally include communicating with both a first TRP and a second TRP. In some implementations, at sub-block 1156, block 1150 may optionally include applying a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception. The default rule may indicate selecting both a first updated unified TCI state and a second updated unified TCI state in the absence of an indication of a single TCI state for PDSCH reception. For example, the default rule may indicate selecting a configured and active code point having the lowest index value associated with two unified TCI states. Thus, UE 104, RX processor 356, TX processor 368, or controller / processor 359 executing unified TCI component 140 or communication component 146 may provide means for communicating with at least one of a first TRP or a second TRP based on a first updated unified TCI state or a second updated unified TCI state.

[0142] At block 1160, method 1100 may optionally include receiving an RRC configuration message indicating the presence of a dynamic TCI selection field within a DCI format. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute unified TCI component 140 or TCI update component 144 to receive an RRC configuration message indicating the presence of a dynamic TCI selection field within a DCI format. Thus, UE 104, RX processor 356, or controller / processor 359 executing unified TCI component 140 or TCI update component 144 may provide means for receiving an RRC configuration message indicating the presence of a dynamic TCI selection field within a DCI format.

[0143] At block 1170, method 1100 may optionally include receiving a second DCI including a dynamic TCI selection field that indicates whether a first unified TCI state or a second unified TCI state is applicable to PDSCH reception starting from an application time after the second DCI. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute unified TCI component 140 or DCI component 142 to receive the second DCI including the dynamic TCI selection field that indicates whether a first unified TCI state or a second unified TCI state is applicable to PDSCH reception starting from an application time after the second DCI. In some implementations, the dynamic TCI selection field is applicable to any PDSCH reception associated with the first unified TCI state or the second unified TCI state after the application time until another TCI selection field is received. In such implementations, the second DCI may not include a downlink assignment for PDSCH reception. In some implementations, the dynamic TCI selection field is only applicable to PDSCH reception scheduled by the second DCI. In some implementations, the application time is based on the UE's capabilities (e.g., capability message 810). In some implementations, the application time is based on the configured time duration for QCL parameters. Thus, UE 104, RX processor 356, or controller / processor 359 that executes unified TCI component 140 or DCI component 142 may provide components for receiving the second DCI including the dynamic TCI selection field that indicates whether a first unified TCI state or a second unified TCI state is applicable to PDSCH reception starting from an application time after the second DCI.

[0144] At block 1180, method 1100 may optionally include receiving PDSCH reception after the application time using at least one of a first TRP or a second TRP based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute unified TCI component 140 or communication component 146 to receive PDSCH reception after the application time using at least one of a first TRP or a second TRP based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field. Thus, UE 104, RX processor 356, or controller / processor 359 that executes unified TCI component 140 or communication component 146 may provide components for receiving PDSCH reception after the application time using at least one of a first TRP or a second TRP based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field.

[0145] Figure 12 FIG. 1200 is a flow chart of another exemplary method for a UE to communicate with a base station having two TRPs based on a single DCI. Method 1200 may be performed by a UE (such as UE 104, which may include a memory 360 and may be the entire UE 104 or a component of UE 104, such as the unified TCI component 140, the TX processor 368, the RX processor 356, or the controller / processor 359). Method 1200 may be performed by the unified TCI component 140 communicating with the unified TCI control component 120 of the base station 102. Method 1200 may be performed in conjunction with method 1100 or separately. In some embodiments, block 1210 may correspond to block 1170, and block 1230 may correspond to block 1180. Additionally, any block of method 1100 may be performed in conjunction with method 1200. Optional blocks are shown with dashed lines.

[0146] At block 1210, method 1200 includes receiving a single DCI for the UE, the UE being configured with a first unified transmit TCI state for a first TRP and a second unified TCI state for a second TRP, where the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception starting from an application time after the single DCI. In some embodiments, for example, UE 104, the RX processor 356, or the controller / processor 359 may execute the unified TCI component 140 or the DCI component 142 to receive a single DCI for the UE, the UE being configured with a first unified transmit TCI state for a first TRP and a second unified TCI state for a second TRP, where the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception starting from an application time after the single DCI. Thus, UE 104, the RX processor 356, or the controller / processor 359 that executes the unified TCI component 140 or the DCI component 142 may provide means for receiving a single DCI for the UE, the UE being configured with a first unified transmit TCI state for a first TRP and a second unified TCI state for a second TRP, where the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception starting from an application time after the single DCI.

[0147] At block 1220, method 1200 may optionally include receiving PDSCH reception after a single DCI but before the application time based on the value of a dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute unified TCI component 140 or DCI component 142 to receive PDSCH reception after a single DCI but before the application time based on the value of a dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception. Thus, UE 104, RX processor 356, or controller / processor 359 that executes unified TCI component 140 or DCI component 142 may provide components for receiving PDSCH reception after a single DCI but before the application time based on the value of a dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception.

[0148] At block 1230, method 1200 includes receiving PDSCH reception after an application time using at least one of a first TRP or a second TRP based on a first unified TCI state or a second unified TCI state as indicated by a dynamic TCI selection field. In some implementations, for example, UE 104, RX processor 356, or controller / processor 359 may execute unified TCI component 140 or DCI component 142 to receive PDSCH reception after an application time using at least one of a first TRP or a second TRP based on a first unified TCI state or a second unified TCI state as indicated by a dynamic TCI selection field. In some implementations, at sub-block 1232, block 1230 may optionally include receiving PDSCH reception after an application time based on a first unified TCI state, a second unified TCI state, or both, the reception being based on a TCI field included in a single DCI, a first unified TCI state or a second unified TCI state active during a time slot of the PDSCH, or a first unified TCI state or a second unified TCI state active during a time slot on which the single DCI is received. Thus, UE 104, RX processor 356, or controller / processor 359 that executes unified TCI component 140 or DCI component 142 may provide components for receiving PDSCH reception after an application time using at least one of a first TRP or a second TRP based on a first unified TCI state or a second unified TCI state as indicated by a dynamic TCI selection field.

[0149] Figure 13 Is a flowchart of an example method 1300 in which a network node communicates with a UE via two TRPs based on a single TRP. Method 1300 may be performed by a network node (such as base station 102, which may include memory 376 and may be the entire base station 102 or a component of base station 102 (such as unified TCI control component 120, TX processor 316, RX processor 370, or controller / processor 375)). Method 1300 may be performed by unified TCI control component 120 that communicates with unified TCI component 140 of UE 104.

[0150] At block 1310, method 1300 may optionally include receiving an indication of the UE's ability to support a default rule. In some implementations, for example, base station 102, RX processor 370, or controller / processor 375 may execute unified TCI control component 120 or configuration component 124 to receive an indication of the UE's ability to support a default rule. Thus, base station 102, RX processor 370, or controller / processor 375 that executes unified TCI control component 120 or configuration component 124 may provide components for receiving an indication of the UE's ability to support a default rule.

[0151] At block 1320, method 1300 may optionally include applying default rules before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery. In some embodiments, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or communication component 126 to apply default rules before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery. Thus, base station 102, TX processor 316, or controller / processor 375 executing unified TCI control component 120 or communication component 126 may provide components for applying default rules before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery.

[0152] At block 1330, method 1300 includes transmitting a single DCI for a UE that is configured with a first unified TCI state for a first TRP and a second unified TCI state for a second TRP. In some embodiments, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or DCI component 122 to transmit a single DCI for a UE that is configured with a first unified TCI state for a first TRP and a second unified TCI state for a second TRP. In some embodiments, the first unified TCI state or the second unified TCI state applies to both control channels and shared channels in the uplink direction, the downlink direction, or both the uplink direction and the downlink direction. Thus, base station 102, TX processor 316, or controller / processor 375 executing unified TCI control component 120 or DCI component 122 may provide components for transmitting a single DCI for a UE that is configured with a first unified TCI state for a first TRP and a second unified TCI state for a second TRP.

[0153] At block 1340, method 1300 includes configuring to update at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on at least one TCI field. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or configuration component 124 to configure to update at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on at least one TCI field. In some implementations, the first TCI field applies to both the first TRP and the second TRP. In some implementations, in the case where a single DCI further includes a second TCI field applicable to the second TRP, block 1140 may include configuring to update the second TRP to a second updated unified TCI state based on the second TCI field. In some implementations, the first TCI field applies to one of the first TRP or the second TRP. The single DCI may further include a second field associating the first TCI field with one of the first TRP or the second TRP. In such implementations, the update configuration may include updating only the first TCI state or the second TCI state associated with the first TCI field. Thus, base station 102, TX processor 316, or controller / processor 375 executing unified TCI control component 120 or DCI component 122 may provide components for configuring to update at least one of a first unified TCI state to a first updated unified TCI state or a second unified TCI state to a second updated unified TCI state based on at least one TCI field.

[0154] At block 1350, method 1300 includes communicating with at least one of a first TRP or a second TRP based on a first updated unified TCI state or a second updated unified TCI state. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or communication component 126 to communicate with at least one of a first TRP or a second TRP based on a first updated unified TCI state or a second updated unified TCI state. In some implementations, at sub-block 1352, block 1150 may optionally include communicating only with a first TRP or a second TRP associated with a first TCI field. In some implementations, at sub-block 1354, block 1150 may optionally include communicating with both a first TRP and a second TRP. In some implementations, at sub-block 1356, block 1150 may optionally include applying a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception. The default rule may indicate selecting both a first updated unified TCI state and a second updated unified TCI state in the absence of an indication of a single TCI state for PDSCH reception. For example, the default rule may indicate selecting a configured and active code point having the lowest index value associated with two unified TCI states. Thus, base station 102, TX processor 316, or controller / processor 375 executing unified TCI control component 120 or DCI component 122 may provide means for communicating with at least one of a first TRP or a second TRP based on a first updated unified TCI state or a second updated unified TCI state.

[0155] At block 1360, method 1300 may optionally include sending an RRC configuration message indicating the presence of a dynamic TCI selection field within a DCI format. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or configuration component 124 to send an RRC configuration message indicating the presence of a dynamic TCI selection field within a DCI format. Thus, base station 102, TX processor 316, or controller / processor 375 executing unified TCI control component 120 or configuration component 124 may provide means for sending an RRC configuration message indicating the presence of a dynamic TCI selection field within a DCI format.

[0156] At block 1370, method 1300 may optionally include transmitting a second DCI that includes a dynamic TCI selection field that indicates whether a first unified TCI state or a second unified TCI state is applicable to PDSCH reception starting from an application time after the second DCI. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or DCI component 122 to transmit a second DCI that includes a dynamic TCI selection field that indicates whether a first unified TCI state or a second unified TCI state is applicable to PDSCH reception starting from an application time after the second DCI. In some implementations, the dynamic TCI selection field is applicable to any PDSCH reception associated with the first unified TCI state or the second unified TCI state after the application time until another TCI selection field is received. In such implementations, the second DCI may not include a downlink assignment for PDSCH reception. In some implementations, the dynamic TCI selection field is only applicable to PDSCH reception scheduled by the second DCI. In some implementations, the application time is based on the UE's capabilities (e.g., capability message 810). In some implementations, the application time is based on the configured time duration for QCL parameters. Thus, base station 102, TX processor 316, or controller / processor 375 that executes unified TCI control component 120 or DCI component 122 may provide components for transmitting a second DCI that includes a dynamic TCI selection field that indicates whether a first unified TCI state or a second unified TCI state is applicable to PDSCH reception starting from an application time after the second DCI.

[0157] At block 1380, method 1300 may optionally include transmitting PDSCH reception after the application time using at least one of a first TRP or a second TRP based on the first unified TCI state or the second unified TCI state as indicated by the dynamic TCI selection field. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or communication component 126 to transmit PDSCH reception after the application time using at least one of a first TRP or a second TRP based on the first unified TCI state or the second unified TCI state as indicated by the dynamic TCI selection field. Thus, base station 102, TX processor 316, or controller / processor 375 that executes unified TCI control component 120 or communication component 126 may provide components for transmitting PDSCH reception after the application time using at least one of a first TRP or a second TRP based on the first unified TCI state or the second unified TCI state as indicated by the dynamic TCI selection field.

[0158] Figure 14 It is a flowchart of an example method 1400 for a network node to communicate with a UE via two TRPs based on a single TRP. The method 1400 may be executed by a network node (such as the base station 102, which may include a memory 376 and may be the entire base station 102 or a component of the base station 102 (such as the unified TCI control component 120, the TX processor 316, the RX processor 370, or the controller / processor 375)). The method 1400 may be executed by the unified TCI control component 120 that communicates with the unified TCI component 140 of the UE 104. The method 1400 may be executed in combination with the method 1300 or separately. In some specific implementations, block 1410 may correspond to block 1370, and block 1430 may correspond to block 1380. Additionally, any block of the method 1300 may be executed together with the method 1400. Optional blocks are shown with dashed lines.

[0159] At block 1410, the method 1400 includes transmitting a single DCI for a UE that is configured with a first unified transmission TCI state for a first TRP and a second unified TCI state for a second TRP, where the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception starting from the application time after the single DCI. In some specific implementations, for example, the base station 102, the TX processor 316, or the controller / processor 375 may execute the unified TCI control component 120 or the DCI component 122 to transmit a single DCI for a UE that is configured with a first unified transmission TCI state for a first TRP and a second unified TCI state for a second TRP, where the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception starting from the application time after the single DCI. Thus, the base station 102, the TX processor 316, or the controller / processor 375 that executes the unified TCI control component 120 or the DCI component 122 may provide means for transmitting a single DCI for a UE that is configured with a first unified transmission TCI state for a first TRP and a second unified TCI state for a second TRP, where the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to PDSCH reception starting from the application time after the single DCI.

[0160] At block 1420, method 1400 may optionally include transmitting PDSCH reception after a single DCI but before the application time based on the value of the dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or communication component 126 to transmit PDSCH reception after a single DCI but before the application time based on the value of the dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception. Thus, base station 102, TX processor 316, or controller / processor 375 that executes unified TCI control component 120 or communication component 126 may provide components for transmitting PDSCH reception after a single DCI but before the application time based on the value of the dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select a first updated unified TCI state, a second updated unified TCI state, or both for PDSCH reception.

[0161] At block 1430, method 1300 includes transmitting PDSCH reception after an application time using at least one of a first TRP or a second TRP based on a first unified TCI state or a second unified TCI state as indicated by a dynamic TCI selection field. In some implementations, for example, base station 102, TX processor 316, or controller / processor 375 may execute unified TCI control component 120 or communication component 126 to transmit PDSCH reception after an application time using at least one of a first TRP or a second TRP based on a first unified TCI state or a second unified TCI state as indicated by a dynamic TCI selection field. In some implementations, at sub-block 1432, block 1430 may optionally include transmitting PDSCH reception after an application time based on a first unified TCI state, a second unified TCI state, or both, the transmission being based on a TCI field included in a single DCI, a first unified TCI state or a second unified TCI state active during a time slot of the PDSCH, or a first unified TCI state or a second unified TCI state active during a time slot on which the single DCI is received. Thus, base station 102, TX processor 316, or controller / processor 375 that executes unified TCI control component 120 or communication component 126 may provide means for transmitting PDSCH reception after an application time using at least one of a first TRP or a second TRP based on a first unified TCI state or a second unified TCI state as indicated by a dynamic TCI selection field.

[0162] The following numbered aspects provide an overview of aspects of the present disclosure:

[0163] Aspect 1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a single downlink control information (DCI) for the UE, the UE being configured with a first unified transmit configuration indicator (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, wherein the DCI includes at least a first TCI field; updating a configuration of at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field; and communicating with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

[0164] Aspect 2. The method according to aspect 1, wherein the first TCI field is applicable to both the first TRP and the second TRP.

[0165] Aspect 3. The method according to Aspect 1, wherein the first TCI field is applicable to one of the first TRP or the second TRP.

[0166] Aspect 4. The method according to Aspect 3, wherein the single DCI further includes a second field associating the first TCI field with the one of the first TRP or the second TRP, and wherein updating the configuration includes updating only the first TCI state or the second TCI state associated with the first TCI field.

[0167] Aspect 5. The method according to Aspect 4, wherein communicating with at least one of the first TRP or the second TRP includes communicating only with the first TRP or the second TRP associated with the first TCI field.

[0168] Aspect 6. The method according to Aspect 4, wherein communicating with at least one of the first TRP or the second TRP includes communicating with both the first TRP and the second TRP.

[0169] Aspect 7. The method according to Aspect 3, wherein the single DCI further includes a second TCI field applicable to the second TRP, and wherein updating the configuration includes updating the configuration of the second TRP to the second updated unified TCI state based on the second TCI field.

[0170] Aspect 8. The method according to any one of Aspects 1 to 7, the method further includes receiving a second DCI including a dynamic TCI selection field, the dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state is applicable to physical downlink shared channel (PDSCH) reception starting from an application time after the second DCI.

[0171] Aspect 9. The method according to Aspect 8, wherein the dynamic TCI selection field is applicable to any PDSCH reception associated with the first unified TCI state or the second unified TCI state after the application time until another TCI selection field is received.

[0172] Aspect 10. The method according to Aspect 9, wherein the second DCI does not include a downlink assignment for PDSCH reception.

[0173] Aspect 11. The method according to Aspect 8, wherein the dynamic TCI selection field is applicable only to PDSCH reception scheduled by the second DCI.

[0174] Aspect 12. The method according to any one of Aspects 8 to 11, the method further comprising receiving a radio resource control (RRC) configuration message indicating the presence of the dynamic TCI selection field within the DCI format.

[0175] Aspect 13. The method according to any one of Aspects 8 to 12, wherein the application time is based on the capabilities of the UE.

[0176] Aspect 14. The method according to any one of Aspects 8 to 12, wherein the application time is based on the time duration of the configuration for the quasi - co - location (QCL) parameters.

[0177] Aspect 15. The method according to any one of Aspects 8 to 14, the method further comprising receiving PDSCH reception after the second DCI but before the application time based on the value of the dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select the first updated unified TCI state, the second updated unified TCI state, or both for the PDSCH reception.

[0178] Aspect 16. The method according to any one of Aspects 8 to 14, the method further comprising receiving PDSCH reception after the application time based on the first unified TCI state, the second unified TCI state, or both, the reception being based on one of the TCI fields included in the second DCI, the first unified TCI state or the second unified TCI state active during the time slot of the PDSCH, or the first unified TCI state or the second unified TCI state active during the time slot on which the second DCI is received.

[0179] Aspect 17. The method according to any one of Aspects 1 to 16, wherein communicating with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state includes applying a default rule specified in a standard document, regulation, or RRC configuration to select the first unified TCI state, the second unified TCI state, or both for PDSCH reception.

[0180] Aspect 18. The method according to Aspect 17, wherein the default rule indicates that in the absence of an indication of a single TCI state for the PDSCH reception, both the first unified TCI state and the second unified TCI state are selected.

[0181] Aspect 19. The method according to Aspect 18, wherein the default rule indicates selecting the configured and active code point having the lowest index value associated with the two unified TCI states.

[0182] Aspect 20. The method according to any one of aspects 17 to 19, the method further comprising sending an indication of the UE's ability to support the default rule.

[0183] Aspect 21. The method according to any one of aspects 17 to 20, the method further comprising applying the default rule before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery.

[0184] Aspect 22. The method according to any one of aspects 17 to 21, the method further comprising receiving a second DCI for scheduling physical downlink shared channel (PDSCH) reception, the second DCI not including a dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state applies to the PDSCH reception.

[0185] Aspect 23. The method according to aspect 22, wherein the format of the second DCI is format 1_1 or 1_2, and wherein the default rule indicates that all the indicated TCI states apply to the scheduled PDSCH.

[0186] Aspect 24. The method according to aspect 22, wherein the format of the second DCI is format 1_0, and wherein if a scheduling CORESET is indicated for scheduling SFN transmission, the default rule indicates that two TCI states of the scheduling CORESET are applied.

[0187] Aspect 25. The method according to aspect 22, wherein the format of the second DCI is format 1_0, wherein two scheduling CORESETs are configured with PDCCH repetition having two linked search spaces, and wherein the default rule indicates selecting the TCI state of the scheduling CORESET with the lowest ID for the PDSCH.

[0188] Aspect 26. The method according to aspect 22, wherein the format of the second DCI is format 1_0, and wherein the default rule indicates applying the TCI state of the scheduling CORESET.

[0189] Aspect 27. The method according to any one of aspects 1 to 26, wherein the first unified TCI state or the second unified TCI state applies to both control channels and shared channels in the uplink direction, the downlink direction, or both the uplink direction and the downlink direction.

[0190] Aspect 28. A method for wireless communication at a user equipment (UE), the method comprising: receiving a single downlink control information (DCI) for the UE, the UE being configured with a first unified transmit control indicator (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, wherein the DCI includes a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state is applicable to physical downlink shared channel (PDSCH) reception starting from an application time after the single DCI; and receiving the PDSCH reception after the application time using at least one of the first TRP or the second TRP based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field.

[0191] Aspect 29. A method for wireless communication at a base station, the method comprising: transmitting a single downlink control information (DCI) to a user equipment (UE), the UE being configured with a first unified transmit configuration indicator (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, wherein the DCI includes at least a first TCI field; updating the UE's configuration for at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field; and communicating with the UE via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

[0192] Aspect 30. The method according to aspect 29, wherein the first TCI field is applicable to both the first TRP and the second TRP.

[0193] Aspect 31. The method according to aspect 29, wherein the first TCI field is applicable to one of the first TRP or the second TRP.

[0194] Aspect 32. The method according to aspect 31, wherein the single DCI further includes a second field that associates the first TCI field with the one of the first TRP or the second TRP, and wherein updating the configuration includes updating only the first TCI state or the second TCI state associated with the first TCI field.

[0195] Aspect 33. The method according to aspect 32, wherein communicating via at least one of the first TRP or the second TRP includes communicating only via the first TRP or the second TRP associated with the first TCI field.

[0196] Aspect 34. The method according to aspect 32, wherein communicating with at least one of the first TRP or the second TRP includes communicating via both the first TRP and the second TRP.

[0197] Aspect 35. The method according to aspect 29, wherein the single DCI further includes a second TCI field applicable to the second TRP, and wherein updating the configuration includes updating the configuration of the second unified TCI to the second updated unified TCI state based on the second TCI field.

[0198] Aspect 36. The method according to aspect 29, the method further includes transmitting a second DCI including a dynamic TCI selection field, the dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state is applicable to physical downlink shared channel (PDSCH) reception starting from an application time after the second DCI.

[0199] Aspect 37. The method according to aspect 36, wherein the dynamic TCI selection field is applicable to any PDSCH reception associated with the first unified TCI state or the second unified TCI state after the application time until another TCI selection field is received.

[0200] Aspect 38. The method according to aspect 37, wherein the second DCI does not include a downlink assignment for PDSCH reception.

[0201] Aspect 39. The method according to aspect 36, wherein the dynamic TCI selection field is only applicable to PDSCH reception scheduled by the second DCI.

[0202] Aspect 40. The method according to any one of aspects 36 to 39, the method further includes transmitting a radio resource control (RRC) configuration message indicating the presence of the dynamic TCI selection field within the DCI format.

[0203] Aspect 41. The method according to any one of aspects 36 to 40, wherein the application time is based on the capabilities of the UE.

[0204] Aspect 42. The method according to any one of aspects 36 to 41, wherein the application time is based on the time duration of the configuration for quasi - co - location (QCL) parameters.

[0205] Aspect 43. The method according to any one of Aspects 36 to 42, the method further comprising transmitting a PDSCH after the second DCI but before the application time based on a value of the dynamic TCI selection field before the second DCI or a default rule specified in a standard document, regulation, or RRC configuration to select the first updated unified TCI state, the second updated unified TCI state, or both for reception of the PDSCH.

[0206] Aspect 44. The method according to any one of Aspects 36 to 42, the method further comprising transmitting a PDSCH after the application time based on the first unified TCI state, the second unified TCI state, or both, the transmission being based on a TCI field included in the second DCI, the first unified TCI state or the second unified TCI state active during a time slot of the PDSCH, or the first unified TCI state or the second unified TCI state active during a time slot on which the second DCI is transmitted.

[0207] Aspect 45. The method according to Aspects 29 to 44, wherein communicating via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state includes applying a default rule specified in a standard document, regulation, or RRC configuration to select the first unified TCI state, the second unified TCI state, or both for PDSCH reception.

[0208] Aspect 46. The method according to Aspect 45, wherein the default rule indicates selecting both the first unified TCI state and the second unified TCI state in the absence of an indication of a single TCI state for PDSCH reception.

[0209] Aspect 47. The method according to Aspect 46, wherein the default rule indicates selecting a configured and activated code point having the lowest index value associated with two unified TCI states.

[0210] Aspect 48. The method according to any one of Aspects 45 to 47, the method further comprising receiving an indication of the UE's ability to support the default rule.

[0211] Aspect 49. The method according to any one of Aspects 45 to 48, the method further comprising applying the default rule before the UE receives any DCI indicating the first unified TCI or the second unified TCI, after initial access, or after beam failure recovery.

[0212] Aspect 50. The method according to any one of aspects 45 to 49, the method further comprising transmitting a second DCI for scheduling physical downlink shared channel (PDSCH) reception, the second DCI not including a dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state is applicable to the PDSCH reception.

[0213] Aspect 51. The method according to aspect 50, wherein the format of the second DCI is format 1_1 or 1_2, and wherein the default rule indicates that all the indicated TCI states are applied to the scheduled PDSCH.

[0214] Aspect 52. The method according to aspect 50, wherein the format of the second DCI is format 1_0, and wherein if a scheduling CORESET is indicated for scheduling SFN transmission, the default rule indicates that two TCI states of the scheduling CORESET are applied.

[0215] Aspect 53. The method according to aspect 50, wherein the format of the second DCI is format 1_0, wherein two scheduling CORESETs are configured with PDCCH repetitions having two linked search spaces, and wherein the default rule indicates selecting the TCI state of the scheduling CORESET with the lowest ID for the PDSCH.

[0216] Aspect 54. The method according to aspect 50, wherein the format of the second DCI is format 1_0, and wherein the default rule indicates applying the TCI state of the scheduling CORESET.

[0217] Aspect 55. The method according to any one of aspects 29 to 54, wherein the unified TCI state is applicable to both control channels and shared channels in the uplink direction, the downlink direction, or both the uplink direction and the downlink direction.

[0218] Aspect 56. A method for wireless communication at a base station, the method comprising: sending a single downlink control information (DCI) to a user equipment (UE) configured with a first unified transmit control indicator (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, wherein the DCI includes a dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state applies to physical downlink shared channel (PDSCH) reception starting from an application time after the single DCI; and transmitting the PDSCH via at least one of the first TRP or the second TRP after the application time based on the first unified TCI state or the second unified TCI state indicated by the dynamic TCI selection field.

[0219] Aspect 57. A device for wireless communication, the device comprising: a transceiver; a memory storing computer-executable instructions; and a processor coupled to the transceiver and the memory and configured to: execute the computer-executable instructions to perform instructions for performing the method according to any one of Aspects 1 to 28.

[0220] Aspect 58. A device for wireless communication, the device comprising: a transceiver; a memory storing computer-executable instructions; and a processor coupled to the transceiver and the memory and configured to execute the computer-executable instructions to perform the method according to any one of Aspects 29 to 56.

[0221] Aspect 59. A device for wireless communication, the device comprising components for performing the method according to any one of Aspects 1 to 28.

[0222] Aspect 60. A device for wireless communication, the device comprising components for performing the method according to any one of Aspects 29 to 56.

[0223] Aspect 61. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform the method according to any one of Aspects 1 to 28.

[0224] Aspect 62. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a processor of a network entity, cause the network entity to perform the method according to any one of Aspects 29 to 56.

[0225] As used herein, the phrase "at least one" in reference to 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 cover: a, b, c, a - b, a - c, b - c, and a - b - c.

[0226] The various illustrative logical, logical block, modules, circuits, and algorithmic processes described in connection with the specific implementations disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been described generally in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0227] The hardware and data processing apparatus for implementing or performing the various illustrative logical, logical block, modules, and circuits described in connection with the aspects disclosed herein can be realized using a general - purpose single - chip or multi - chip processor, a digital signal processor (DSP), an application - specific integrated circuit (ASIC), a field - programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof. The general - purpose processor may be a microprocessor, or any conventional processor, controller, micro - controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuitry specific to a given function.

[0228] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and structural equivalents thereof, or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by, or to control the operation of, a data processing apparatus.

[0229] If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. The processes of the methods or algorithms disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, where communication media includes any medium that can facilitate transfer of a computer program from one place to another. The storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer. Additionally, any connection may be properly termed a computer-readable medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, operations of a method or algorithm may reside as one or any combination of code and instruction sets on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0230] Various modifications to the specific implementations described in this disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of the disclosure. Thus, the claims are not intended to be limited to the specific implementations shown herein but are to be accorded the widest scope consistent with the disclosure, the principles disclosed herein, and the novel features.

[0231] Additionally, those of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of description of the drawings and indicate relative positions corresponding to the orientation of the drawing on a correctly oriented page and may not reflect the correct orientation of any device as implemented.

[0232] Certain features that are described in the context of a single specific implementation in this specification may also be implemented combinatorially in a single specific implementation. Conversely, various features described in the context of a single specific implementation may also be implemented separately or in any suitable sub-combination in multiple specific implementations. Additionally, although some features are described above as working in a particular combination and even initially claimed as such, in some cases, one or more features from the claimed combination may be excised from the combination, and the claimed combination may refer to a sub-combination or a variation of a sub-combination.

[0233] Similarly, although operations are depicted in the figures in a particular order, this should not be construed as requiring that such operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed to achieve the desired result. Additionally, the figures may schematically depict one or more example processes in the form of a flowchart. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the operations illustrated. In certain environments, multitasking and parallel processing are advantageous. Further, the separation of various system components in the specific embodiments described above should not be construed as requiring such separation in all specific embodiments, but rather it should be understood that the program components and systems described can generally be integrated together in a single software product or packaged into multiple software products. Beyond this, other specific embodiments are within the scope of the following claims. In some cases, the acts recited in the claims can be performed in a different order and still achieve the desired result.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprises: receiving a single downlink control information (DCI) for the UE, the UE being configured with a first unified transmit configuration indication (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, wherein the DCI at least comprises a first TCI field; updating the configuration of at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field; and communicating with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

2. The method according to claim 1, wherein the first TCI field is applicable to one of the first TRP or the second TRP.

3. The method according to claim 2, wherein the single DCI further comprises a second field associating the first TCI field with the one of the first TRP or the second TRP, wherein updating the configuration comprises updating only the first TCI state or the second TCI state associated with the first TCI field.

4. The method according to claim 3, wherein communicating with at least one of the first TRP or the second TRP comprises communicating with both the first TRP and the second TRP.

5. The method according to claim 1, the method further comprises receiving a second DCI comprising a dynamic TCI selection field, the dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state is applicable to physical downlink shared channel (PDSCH) reception starting from an application time after the second DCI.

6. The method according to claim 1, wherein communicating with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state comprises applying default rules specified in a standard document, regulation or RRC configuration to select the first unified TCI state, the second unified TCI state or both for PDSCH reception.

7. The method according to claim 6, wherein the default rules indicate that both the first unified TCI state and the second unified TCI state are selected in the absence of an indication of a single TCI state for the PDSCH reception.

8. The method according to claim 7, wherein the default rules indicate selecting a configured and active code point having the lowest index value associated with two unified TCI states.

9. The method according to claim 1, wherein the first unified TCI state or the second unified TCI state is applicable to both control channels and shared channels in the uplink direction, the downlink direction or both the uplink direction and the downlink direction.

10. A method for wireless communication at a base station, the method comprises: sending a single downlink control information (DCI) to a user equipment (UE), the UE being configured with a first unified transmission configuration indication (TCI) state for a first transmission reception point (TRP) and a second unified TCI state for a second TRP, wherein the DCI at least comprises a first TCI field; updating, based on the at least one TCI field, the configuration of the UE for at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state; and communicating with the UE via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

11. The method according to claim 10, wherein the first TCI field is applicable to one of the first TRP or the second TRP.

12. The method according to claim 11, wherein the single DCI further comprises a second field associating the first TCI field with the one of the first TRP or the second TRP, wherein updating the configuration comprises updating only the first TCI state or the second TCI state associated with the first TCI field.

13. The method according to claim 12, wherein communicating with at least one of the first TRP or the second TRP comprises communicating via both the first TRP and the second TRP.

14. The method according to claim 10, the method further comprises sending a second DCI comprising a dynamic TCI selection field, the dynamic TCI selection field indicating whether the first unified TCI state or the second unified TCI state is applicable to physical downlink shared channel (PDSCH) reception starting from an application time after the second DCI.

15. The method according to claim 10, wherein communicating via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state comprises applying a default rule specified in a standard document, regulation or RRC configuration to select the first unified TCI state, the updated unified TCI state or both for PDSCH reception.

16. The method according to claim 15, wherein the default rule indicates that both the first unified TCI state and the second unified TCI state are selected in the absence of an indication of a single TCI state for the PDSCH reception.

17. The method according to claim 16, wherein the default rule indicates selecting a configured and activated code point having the lowest index value associated with two unified TCI states.

18. The method according to claim 10, wherein the unified TCI state applies to both control channels and shared channels in the uplink direction, the downlink direction, or both the uplink direction and the downlink direction.

19. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: one or more memories that store computer-executable instructions, either individually or in combination; and one or more processors coupled to the one or more memories and configured, either individually or in combination, to: receive a single downlink control information (DCI) for the UE, the UE being configured with a first unified transmit configuration indication (TCI) state for a first transmission reception point (TRP) and a second unified TCI state for a second TRP, wherein the DCI includes at least a first TCI field; update the configuration of at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field; and communicate with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

20. The apparatus according to claim 19, wherein the first TCI field applies to one of the first TRP or the second TRP.

21. The apparatus according to claim 20, wherein the single DCI further includes a second field associating the first TCI field with the one of the first TRP or the second TRP, wherein updating the configuration includes updating only the first TCI state or the second TCI state associated with the first TCI field.

22. The apparatus according to claim 21, wherein communicating with at least one of the first TRP or the second TRP includes communicating with both the first TRP and the second TRP.

23. The apparatus according to claim 19, wherein the one or more processors are further configured, either individually or in combination, to receive a second DCI including a dynamic TCI selection field that indicates whether the first unified TCI state or the second unified TCI state applies to physical downlink shared channel (PDSCH) reception starting from an application time after the second DCI.

24. The apparatus according to claim 19, wherein, in order to communicate with at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state, the one or more processors are configured, either individually or in combination, to apply default rules specified in a standard document, regulation, or RRC configuration to select the first unified TCI state, the second unified TCI state, or both for PDSCH reception.

25. The apparatus according to claim 24, wherein the default rule indicates that both the first unified TCI state and the second unified TCI state are selected in the absence of an indication of a single TCI state for PDSCH reception.

26. The apparatus according to claim 25, wherein the default rule indicates selecting a configured and activated code point having the lowest index value associated with the two unified TCI states.

27. The apparatus according to claim 19, wherein the first unified TCI state or the second unified TCI state applies to both control channels and shared channels in the uplink direction, the downlink direction, or both the uplink direction and the downlink direction.

28. An apparatus for wireless communication at a network node, the apparatus comprising: one or more memories that store computer-executable instructions, either individually or in combination; and one or more processors coupled to the one or more memories and configured to execute the computer-executable instructions to: send a single downlink control information (DCI) to a user equipment (UE) configured with a first unified transmit configuration indication (TCI) state for a first transmit receive point (TRP) and a second unified TCI state for a second TRP, wherein the DCI includes at least a first TCI field; update the UE's configuration for at least one of the first unified TCI state to a first updated unified TCI state or the second unified TCI state to a second updated unified TCI state based on the at least one TCI field; and communicate with the UE via at least one of the first TRP or the second TRP based on the first updated unified TCI state or the second updated unified TCI state.

29. The apparatus according to claim 28, wherein the first TCI field applies to one of the first TRP or the second TRP, wherein the single DCI further includes a second field associating the first TCI field with the one of the first TRP or the second TRP, and wherein the one or more processors are configured, either individually or in combination, to: update only the first TCI state or the second TCI state associated with the first TCI field; and communicate via both the first TRP and the second TRP.

30. The apparatus according to claim 28, wherein the one or more processors are configured, either individually or in combination, to apply a default rule specified in a standard document, regulation, or RRC configuration to select both the first unified TCI state and the second unified TCI state in the absence of an indication of a single TCI state for PDSCH reception.

Images