Event-driven beamforming for Unified TCI

Abstract

Example embodiments of this disclosure relate to user equipment, base stations, methods, apparatus, and computer-readable media for event-driven beam reporting for a unified TCI. In this approach, a UE can transmit a beam report indicating that an event associated with an indicated joint or DL ​​TCI state has been satisfied. In some cases, the beam report may also indicate an active joint or DL ​​TCI state different from the indicated joint or DL ​​TCI state. Therefore, the UE can know at least the channel quality associated with the indicated joint / DL TCI state, and thus, further decisions regarding TCI state switching can be made.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to user equipment (UE), base station (BS), methods, apparatus, and computer-readable media for event-driven beam reporting for a unified transmission configuration indicator (TCI). Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, fifth-generation (5G) wireless access technology, and other suitable wireless access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] Beam measurement and beam reporting have been specified for network (NW) control; however, the network needs to be configured or activated for frequent periodic or semi-persistent beam reporting, or to trigger frequent periodic beam reporting, which results in significant overhead. Summary of the Invention

[0004] This disclosure relates to base stations, user equipment, methods, apparatuses, processors, and computer-readable media for event-driven beam reporting for a unified TCI. According to the proposed solutions, beam reports can be sent when an event associated with an indicated joint or downlink (DL) TCI state is satisfied, thereby defining UE behavior for beam reporting and reducing overhead.

[0005] In some implementations, a UE is provided. The UE includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the UE: determines that an event associated with an indicated joint or DLTCI state is satisfied; and, based on the determination that a triggering condition associated with the event is satisfied, sends a beam report to a base station, the beam report indicating one of the following: the event, or an active joint or DLTCI state other than the indicated joint or DLTCI state.

[0006] In some implementations, a base station is provided. The base station includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the base station: sends downlink control information (DCI) to a UE, the DCI indicating an indicated joint or DL ​​TCI state; and receives a beam report from the UE, the beam report indicating one of the following: an event associated with the indicated joint or DL ​​TCI state, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

[0007] In some implementations, a method is provided to be performed by the UE. The method includes: determining that an event associated with an indicated joint or DLTCI state is satisfied; and, based on the determination that a triggering condition associated with the event is satisfied, sending a beam report to a base station, the beam report indicating one of the following: the event, or an active joint or DLTCI state other than the indicated joint or DLTCI state.

[0008] In some implementations, a method is provided that is performed by a base station. The method includes: sending downlink control information (DCI) to a UE, the DCI indicating an indicated joint or DL ​​TCI state; and receiving a beam report from the UE, the beam report indicating one of the following: an event associated with the indicated joint or DL ​​TCI state, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

[0009] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to: determine that an event associated with an indicated joint or DL ​​TCI state is satisfied; and, based on the determination that a trigger condition associated with the event is satisfied, send a beam report to a base station, the beam report indicating one of the following: the event, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

[0010] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to at least one memory and configured to cause the processor to: send a DCI to a UE, the DCI indicating an indicated joint or DL ​​TCI state; and receive a beam report from the UE, the beam report indicating one of the following: an event associated with the indicated joint or DL ​​TCI state, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

[0011] The method described herein and some implementations of the UE also include: sending a dedicated scheduling request (SR) to the base station to request transmission resources for a Media Access Control (MAC) Control Element (CE); and receiving a first DCI from the base station to schedule the transmission of a Physical Uplink Shared Channel (PUSCH) carrying the MACCE.

[0012] In the methods described herein and some implementations of the UE, the event includes a first event or a second event, and these implementations further include: receiving a second DCI from a base station, the second DCI indicating another indicated joint or DL ​​TCI state, wherein the other indicated joint or DL ​​TCI state is the same as or different from the active joint or DL ​​TCI state in the beam report; and applying the other indicated joint or DL ​​TCI state to another transmission or reception.

[0013] In the methods described herein and some implementations of the UE, the events include a third or fourth event, and these implementations also include: applying an active joint or DL ​​TCI state after a specific time point, wherein the specific time point is 28 symbols away from the last symbol received by the Physical Downlink Control Channel (PDCCH) with the third DCI, the third DCI scheduling a PUSCH transmission with the same Hybrid Automatic Repeat Request (HARQ) procedure number as the first PUSCH transmission, the first PUSCH carrying a MACCE, and the third DCI having a flipped New Data Indicator (NDI) field value.

[0014] The methods described herein and some implementations of the UE also include: applying the UL TCI state to another transmission based on the determination that there is an uplink (UL) TCI state paired with the active DL TCI state; or continuing to apply the current UL TCI state to another transmission based on the determination that there is no UL TCI state paired with the active DL TCI state.

[0015] The method described herein and some implementations of the UE also include: receiving a second DCI from the base station before the third DCI, the second DCI indicating another indicated joint or DL ​​TCI state, wherein the third DCI is scheduling a PUSCH transmission with the same HARQ procedure number as the transmission of the first PUSCH, the first PUSCH carrying a MAC CE, and the third DCI having an inverted NDI field value; and applying another indicated joint or DL ​​TCI state to another transmission or reception.

[0016] The method described herein and some implementations of the BS also include: receiving a dedicated SR from the UE for requesting transport resources for the MAC CE; and sending a first DCI to the UE to schedule the PUSCH transport carrying the MAC CE.

[0017] In the methods described herein and some implementations of the BS, the event includes a first event or a second event, and these implementations further include: sending a second DCI to the UE, the second DCI indicating another indicated joint or DL ​​TCI state, wherein the other indicated joint or DL ​​TCI state is the same as or different from the active joint or DL ​​TCI state in the beam report; and applying the other indicated joint or DL ​​TCI state to another transmission or reception with the UE.

[0018] In the methods described herein and some implementations of BS, the events include a third or fourth event, and these implementations also include: applying an active joint or DL ​​TCI state after a specific time point, wherein the specific time point is 28 symbols from the last symbol received by the PDCCH with the third DCI, the third DCI scheduling a PUSCH transmission with the same HARQ procedure number as the transmission of the first PUSCH, the first PUSCH carrying a MAC CE, and the third DCI having an inverted NDI field value.

[0019] The methods described herein and some implementations of BS also include: applying the UL TCI state to another transmission based on the determination that there is an UL TCI state paired with the active DL TCI state; or continuing to apply the current UL TCI state to another transmission based on the determination that there is no UL TCI state paired with the active DL TCI state.

[0020] The method described herein and some implementations of the BS also include: sending a second DCI to the UE before the third DCI, the second DCI indicating another indicated joint or DL ​​TCI state, wherein the third DCI is scheduling a PUSCH transmission with the same HARQ procedure number as the transmission of the first PUSCH, the first PUSCH carrying a MAC CE, and the third DCI having an inverted NDI field value; and applying the other indicated joint or DL ​​TCI state to another transmission or reception with the UE.

[0021] In some implementations of the methods, UEs, and BSs described in this paper, the triggering condition includes one of the following: the event is satisfied, or the event has been satisfied multiple times consecutively within a time window, wherein the number of consecutive times is predefined or preconfigured.

[0022] In some implementations of the methods, UEs, and BSs described herein, an event includes one of the following: a first event indicating that the quality of the indicated joint or DL ​​TCI state is less than or not greater than a first threshold; a second event indicating that the quality of one of the active joint or DL ​​TCI states exceeds or is not less than a second threshold; a third event indicating that the difference between the quality of one of the active joint or DL ​​TCI states and the quality of the indicated joint or DL ​​TCI state exceeds or is not less than a third threshold; or a fourth event indicating that the quality of the indicated joint or DL ​​TCI state is less than or not greater than a fourth threshold, and the quality of one of the active joint or DL ​​TCI states exceeds or is not less than a fifth threshold.

[0023] In some implementations of the methods, UEs, and BSs described herein, at least one threshold associated with an event is at least one block error rate (BLER), and at least one BLER is determined based on one or more specific assumed PDCCH transmission parameters, or the Layer 1 Reference Signal Received Power (L1-RSRP) configured by Radio Resource Control (RRC) signaling.

[0024] In the methods, UEs, and BSs described in this paper, events include the first event, and beam reports are included in the SR.

[0025] In some implementations of the methods, UEs, and BSs described herein, the event includes one of a second, third, or fourth event, wherein beam reporting is included in the MAC CE, which indicates one of the active joint or DL ​​TCI states.

[0026] In some implementations of the methods, UEs, and BSs described herein, the MAC CE includes a bitmap in which bits corresponding to one of the active joint or DL ​​TCI states of the bandwidth portion (BWP) of the serving cell for the UE are set to specific values.

[0027] In some implementations of the methods, UEs, and BSs described herein, the MAC CE includes one of the following: an identifier (ID) of an active joint or DL ​​TCI state; a non-zero power (NZP) channel state information (CSI) reference signal (RS) resource ID associated with an active joint or DL ​​TCI state; or an indication of a TCI code point mapped to an active joint or DL ​​TCI state.

[0028] In some implementations of the methods, UEs, and BSs described in this paper, different events are associated with different Logical Channel Identifiers (LCIDs), and the MAC CE also includes the LCID associated with the event.

[0029] In some implementations of the methods, UEs, and BSs described in this paper, different events are associated with the same LCID, and the MAC CE includes: an LCID carried in a specific location associated with the event. Attached Figure Description

[0030] Figure 1 The illustration shows an example of a wireless communication system in which some embodiments of the present disclosure may be implemented;

[0031] Figure 2 The illustration shows an example schematic diagram of the timing relationship of the transmission of the PRACH preamble according to some example embodiments of the present disclosure;

[0032] Figure 3A The illustration shows an example schematic diagram of a MAC CE including a bitmap for indicating an active union or TCI state, according to some example embodiments of the present disclosure.

[0033] Figure 3B The illustration shows an example schematic diagram of a MAC CE including an NZP CSI-RS resource ID associated with an active union or TCI state, according to some example embodiments of the present disclosure;

[0034] Figure 3C The illustration shows an example schematic diagram of a MAC CE for TCI code points that maps an indication to an active union or TCI state according to some example embodiments of the present disclosure.

[0035] Figure 3D The illustration shows an example schematic diagram of a MAC CE including an ID of an active union or TCI state according to some example embodiments of the present disclosure;

[0036] Figure 4A The illustration shows an example schematic diagram of a MAC CE including an ID of an active federated or TCI state and an event ID, according to some example embodiments of the present disclosure;

[0037] Figure 4B The illustration shows an example schematic diagram of a MAC CE including an NZP CSI-RS resource ID and an event ID according to some example embodiments of the present disclosure;

[0038] Figure 4CThe illustration shows an example schematic diagram of a MAC CE including a TCI code point and an event ID mapped to an active union or TCI state, according to some example embodiments of the present disclosure.

[0039] Figure 5A The illustration shows an example schematic diagram of TCI state switching according to some example embodiments of the present disclosure;

[0040] Figure 5B The illustration shows another example schematic diagram of TCI state switching according to some example embodiments of the present disclosure;

[0041] Figure 6 Examples of devices suitable for implementing embodiments of the present disclosure are illustrated;

[0042] Figure 7 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated;

[0043] Figure 8 The diagram illustrates a flowchart of an example method implemented at the UE according to various aspects of this disclosure; and

[0044] Figure 9 The diagram illustrates a flowchart of an example method implemented at the BS according to various aspects of this disclosure.

[0045] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0046] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not constitute any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0047] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments(s) may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that incorporating other embodiments (whether explicitly described or not) to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0048] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a variety of functional alternatives may be chosen, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0049] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “containing,” and / or “comprise”, when used herein, specify the presence of the stated features, elements, components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.

[0050] Figure 1The illustration shows an example of a wireless communication system 100 in which some embodiments of the present disclosure may be implemented. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network (CN) 106, and a packet data network 108. The wireless communication system 100 may support a variety of wireless access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable wireless access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0051] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0052] Network entity 102 can provide a geographic coverage area 112, and network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0053] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine-Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0054] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 The diagram illustrates some examples of UE 104. UE 104 is capable of communicating with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., CN 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104 that may be used as relays in wireless communication system 100.

[0055] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink (SL). For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0056] Network entity 102 may support communication with CN 106 or with another network entity 102, or both. For example, network entity 102 may interface with CN 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0057] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: Central Unit (CU), Distributed Unit (DU), Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., Near Real-Time RIC, Non-Real-Time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0058] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0059] The functional decomposition between CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU.

[0060] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU or between the DU and RU can be within a protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer can be performed by another of the CU, DU, or RU).

[0061] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-C, F1-U), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the corresponding network entity 102 communicating via such communication links.

[0062] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and user plane entities that route packets or interconnect with external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with CN 106.

[0063] CN 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with CN 106 via network entity 102. CN 106 can use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be an example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0064] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable wireless access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0065] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some implementations, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0066] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). ms The duration of a frame. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, such as 1... ms The duration of a frame. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0067] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a regular cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes can depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0068] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range identifiers FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other equipment or devices, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, along with other equipment or devices, for short-range, high data rate capabilities.

[0069] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with: a first parameter set (e.g., μ=0) comprising a subcarrier spacing of 15 kHz; a second parameter set (e.g., μ=1) comprising a subcarrier spacing of 30 kHz; and a third parameter set (e.g., μ=2) comprising a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with: a third parameter set (e.g., μ=2) comprising a subcarrier spacing of 60 kHz; and a fourth parameter set (e.g., μ=3) comprising a subcarrier spacing of 120 kHz.

[0070] The first version of NR specified NW control beam measurement and beam reporting for beam management, and it has been enhanced from version 16 (Rel-16) to version 18 (Rel-18) to improve performance or reduce signaling overhead. To obtain the quality of beams of interest in a timely manner, such as the quality of the (multiple) active TCI states of the BWP for the serving cell, the network needs to configure or activate frequent periodic or semi-persistent beam reporting (e.g., N best beams and corresponding L1-RSRPs) or trigger frequent aperiodic beam reporting. However, this obviously results in significant uplink (UL) reporting overhead. Beams in FR2 can be represented by reference signals. For example, DL beams can be represented by NZP CSI-RS resources or SSB resources. Beam IDs can be represented by NZP CSI-RS resource IDs or SSB resource IDs. When a beam for DL ​​reception is indicated, the UE can receive the DL signal using the same Rx spatial filter parameters as the reception of the NZP CSI-RS resource or SSB resource representing the beam. Beam information used for DL ​​reception is indicated or configured by the joint or DL ​​TCI status, which contains DL reference signal resources with QCL type D. Beam measurement and beam reporting procedures are configured by the CSI report configuration, and beam reports are carried by the CSI report.

[0071] For example, when a unified TCI framework is configured for the serving cell, the NW can activate up to eight joint or DLTCI states for the TRP, any of which can be designated for DL ​​channel or RS reception. To ensure better performance of the designated TCI states, frequent beam reporting is required for the beams corresponding to the activated TCI states. Given that the UE has a better and more timely understanding of beam quality changes for each activated TCI state, a UE-initiated beam reporting procedure with specified events could result in more timely beam reporting while reducing reporting overhead. Under this procedure, if the UE determines that the conditions of one or more specified events are met, the UE can trigger beam reporting without network configuration or triggering frequent reporting. For this reason, the following objectives for MIMO evolution in Revision 19 (Rel-19) have been approved. ○Specify enhancements to facilitate UE-initiated / event-driven beam management, thereby reducing overhead and / or latency, assuming unified TCI, while (where possible) utilizing the traditional CSI measurement and reporting configuration framework, targeting FR2 and TRP for intra-cell and inter-cell beam management. - Multiple UL signaling contents (and multiple required procedures) for UE-initiated / event-driven beam reporting to facilitate fast beam switching. -UL signaling medium / container, taking into account the UE-initiated / event-driven characteristics of UL transmission, is primarily designed for beam reporting.

[0072] Embodiments of this disclosure provide a technical solution for event-driven beam reporting for a unified TCI. In this solution, the UE can determine whether an event associated with an indicated joint / DL TCI state has been met; for example, the UE can be configured with one or more events. If the conditions for an event are met, the UE can also send a beam report to the base station, which can then use the beam report for further consideration, such as TCI state switching.

[0073] In this disclosure, channel quality may also be referred to as wireless link quality or beam quality, and it should be understood that they can be used interchangeably.

[0074] Figure 2 A signaling diagram is illustrated, illustrating a communication process 200 according to some example embodiments of this disclosure. Process 200 may involve a UE 201 and a base station 202. References Figure 1 UE 201 can be implemented as UE 104, and base station 202 can be implemented as network entity 102. It should be understood that process 200 can be applied to other communication scenarios, which will not be described in detail hereafter.

[0075] For each BWP serving the cell, it can be done through... failureDetectionResourcesToAddModList Provide UE 201 with a set of periodic CSI-RS resource configuration indexes and through candidateBeamRSList or candidateBeamRSListExt or candidateBeamRSSCellList Provide the UE with a set of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes. Used for radio link quality measurement on the BWP of the serving cell. Instead of a set. and For each BWP serving the cell, it can be done through failureDetectionSet1 and failureDetectionSet2 Provide UE 201 with two corresponding sets of periodic CSI-RS resource configuration indexes respectively. and ( and (and can be activated by MAC CE), and through candidateBeamRS-List and candidateBeamRS-List2 Two sets of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes are provided to UE 201 respectively. and This is used for radio link quality measurement on the BWP serving the cell. (Set) With sets Related, and set With sets Related.

[0076] When a unified TCI framework is configured for the serving cell, UE 201 is configured with up to 128 joint or DL ​​TCI states via RRC signaling for the serving cell's BWP, which can be used to determine the Rx beam for DL ​​reception; and up to 64 UL TCI states, which can be used to determine the Tx beam for UL transmission. When a joint TCI state is configured, it is used by the UE to determine both the Rx beam for DL ​​reception and the Tx beam for UL transmission. The NW can also send a MAC CE to UE 201 to activate up to 8 joint / DL / UL TCI states to the TRP for the serving cell's BWP, and each activated joint / DL / UL TCI state is mapped to a TCI field code point contained in DCI format 1_1 / 1_2. When TCI field code points are mapped to DL TCI states and UL TCI states, it is assumed that DL TCI states are paired with UL TCI states. The NW should also send a DCI with format 1_1 / 1_2 to indicate the TCI field code point of UE 201, to indicate a joint TCI state or a pair of DL and UL TCI states, which are mapped to the indicated TCI code point for DL ​​reception and UL transmission in the BWP of the serving cell.

[0077] In procedure 200, BS 202 sends a DCI with format 1_1 / 1_2 to UE 201 at 210. This DCI indicates the TCI code point for UE 201. The TCI code point can be used to specify the indicated joint or DL ​​TCI state. Specifically, the TCI code point can indicate a joint TCI state or a pair of DL and UL TCI states, which are mapped to the indicated TCI code point for DL ​​reception and UL transmission in the BWP of the serving cell. Each joint / DL TCI state includes a quasi-co-located (QCL) type D RS for the UE to determine the spatial RX filter parameters for DL ​​reception, and the RS can be a periodic CSI-RS for beam management or a periodic CSI-RS for tracking.

[0078] In procedure 200, UE 201 determines at 220 that an event associated with the indicated joint or DL ​​TCI state has been satisfied. In some examples, UE 201 may determine whether the event has been satisfied multiple times consecutively within a time window. In some implementations, UE 201 may be configured with one or more of a first event, a second event, a third event, and a fourth event.

[0079] In this disclosure, the indicated joint or DL ​​TCI state can be represented as the current joint / DL TCI state, for example, it refers to the current TCI state applied by UE 201 and BS 202 for the BWP of the serving cell.

[0080] The first event can indicate that the quality of the indicated joint or DL ​​TCI state is less than or no greater than a first threshold. In some implementations, the first event can be represented as event 1, and the first threshold can be represented as Q1. In some examples, Q1 can be a BLER derived based on specific assumed PDCCH transmission parameters (e.g., the parameters shown in Table 1 below), or an L1-RSRP configured by RRC signaling. Table 1

[0081] In some implementations, UE 201 can determine whether the triggering condition for the first event (Event 1) has been met. In some example embodiments, UE 201 may need to monitor the quality of the indicated joint or DL ​​TCI state. Through this event, UE 201 can inform BS 202 in a timely manner that the current indicated TCI state is not good enough before triggering a beam failure event.

[0082] In some examples, UE 201 may evaluate (e.g., compare) the quality of the indicated joint or DL ​​TCI state against a first threshold Q1. If UE 201 detects that the quality of the indicated joint or DL ​​TCI state (which may be controlled by a timer in the MAC) is less than Q1 for N1 consecutive times within a time window W1 (which may be controlled by a counter in the MAC), it will send a beam report (see 230) to BS 202 to indicate such an event. For example, a dedicated SR may be configured for the beam report used for the first event (Event 1). In some examples, after receiving the beam report (i.e., the dedicated SR), BS 202 may indicate a new joint TCI state or DL ​​TCI state, or a pair of DL and UL TCI states, for the BWP of the serving cell.

[0083] The second event can indicate that the quality of one of the active joint or DL ​​TCI states exceeds or is not less than a second threshold. In some implementations, the second event can be denoted as event 2, and the second threshold can be denoted as Q2. In some examples, Q2 can be a BLER derived based on specific assumed PDCCH transmission parameters, or an L1-RSRP configured by RRC signaling.

[0084] In some implementations, UE 201 can determine whether the triggering condition for the second event (Event 2) has been met. In some example embodiments, UE 201 can monitor (e.g., measure) the quality of all active joint / DL TCI states other than the indicated joint / DL TCI state. Through this event, UE 201 can promptly report a better candidate TCI state to BS 202, a state good enough for a potential TCI state switchover.

[0085] In some examples, UE 201 may evaluate (e.g., compare) each quality of a corresponding active joint or DL ​​TCI state other than the indicated joint / DLTCI state against a second threshold Q2. If UE 201 detects that the quality of an active joint / DL TCI state is equal to or greater than Q2 for N2 consecutive times within time window W2, it will send a beam report (see 230) to BS 202 to indicate such an event and report the active joint / DL TCI state (or the CSI-RS associated with the active joint / DL TCI state). For example, N2 may be equal to N1, and time window W2 may be the same as time window W1. For example, MAC CE may be configured for beam reporting of a second event (event 2). In some examples, after receiving the beam report, BS 202 may indicate a TCI code point mapped to the joint / DL state reported by the serving cell's BWP.

[0086] A third event can indicate that the difference between the quality of one of the active joint or DL ​​TCI states (e.g., the optimal active joint or DL ​​TCI state) and the quality of the indicated joint / DL TCI state exceeds or is not less than a third threshold. In some implementations, the third event can be denoted as event 3, and the third threshold can be denoted as Q3. In some examples, Q3 can be a BLER derived based on specific assumed PDCCH transmission parameters, or an L1-RSRP configured by RRC signaling.

[0087] In some implementations, UE 201 can determine whether the triggering condition for a third event (Event 3) has been met. In some example embodiments, UE 201 can monitor (e.g., measure) the quality of all active joint / DL TCI states, including the indicated joint / DL TCI state. Based on this event, UE 201 can promptly report to BS 202 a better candidate TCI state than the currently indicated joint / DL TCI state for potential TCI state switching.

[0088] In some examples, UE 201 may evaluate (e.g., compare) the difference between the quality of the active joint / DL TCI state and the indicated joint / DL TCI state with a third threshold Q3. If UE 201 detects that the quality of an active joint / DL TCI state becomes better than the currently indicated TCI state for N1 consecutive times within a time window W1, and the quality offset is equal to or greater than Q3, it will send a beam report to BS 202 to indicate such an event and report the active joint / DL TCI state (or the CSI-RS associated with that joint / DL TCI state). For example, MAC CE can be configured for beam reporting of the third event (Event 3).

[0089] The fourth event can indicate that the quality of the indicated joint or DL ​​TCI state is less than or no greater than a fourth threshold, and the quality of one of the active joint or DL ​​TCI states exceeds or is no less than a fifth threshold. In some implementations, the fourth event can be represented as event 4, the fourth threshold can be represented as Q4, and the fifth threshold can be represented as Q5. In some examples, Q4 and / or Q5 can be a BLER derived based on specific assumed PDCCH transmission parameters, or an L1-RSRP configured by RRC signaling.

[0090] In some implementations, UE 201 can determine whether the triggering condition for the fourth event (Event 4) has been met. In some example embodiments, the fourth event can be considered as a combination of the first and second events, for example, Q4=Q1 and Q5=Q2. Through this event, UE 201 can inform BS 202 in time that the currently indicated TCI state is not good enough before triggering the beam failure event, and a better candidate TCI state is identified before triggering the beam failure event for, for example, fast TCI state switching.

[0091] In some examples, if UE 201 detects a quality less than Q4 for an indicated joint or DL ​​TCI state N1 consecutive times within time window W1, and identifies an active joint / DL TCI state with a quality greater than Q5 for N2 consecutive times within time window W2, it will send a beam report (see 230) to BS 202 to indicate such an event and report the active joint / DL TCI state (or the CSI-RS associated with the active joint / DL TCI state). For example, MAC CE can be configured for beam reporting of a fourth event (Event 4).

[0092] In procedure 200, UE 201 sends a beam report to BS 202 at 230. In some implementations, the beam report may be triggered by the occurrence of at least one of a first event, a second event, a third event, and a fourth event. In some example embodiments, the beam report may be considered as an event-driven beam report or an event-triggered beam report.

[0093] In some implementations, the beam report may indicate a trigger condition for at least one event to be met. In some implementations, if the met event includes one or more of a second, third, or fourth event, the beam report may also indicate an active joint or DL ​​TCI state that is different from the indicated joint or DL ​​TCI state and associated with the met event.

[0094] In some implementations, beam reporting can be sent via a dedicated SR or MAC CE if the triggering condition of the first event is met. For example, the MAC CE may include a dedicated field that may include at least one bit. For example, the MAC CE may include a specific field that includes the event ID of the first event.

[0095] In some other implementations, beam reports can be sent via MAC CE if one or more of the triggering conditions of the second, third, or fourth event are met.

[0096] In some example embodiments, the MAC CE can indicate an active joint or DL ​​TCI state associated with a satisfied event. In some examples, one of the second, third, or fourth events can be configured for UE 201 in the serving cell's BWP. For example, an active joint or DL ​​TCI state indicated by the MAC CE can be the optimal joint / DL TCI state determined by UE 201, such as having the highest channel quality. In some examples, an active joint or DL ​​TCI state can be explicitly or implicitly indicated by the MAC CE.

[0097] In some embodiments, an active joint or DL ​​TCI state indicated by the MAC CE may be referred to as a reported joint / DL TCI state, a suggested joint / DL TCI state, a selected joint / DL TCI state, or a recommended joint / DLTCI state, etc. This disclosure does not limit this aspect. In some embodiments, the MAC CE may further include: a serving cell ID field, a BWP ID field, and an L1-RSRP field, for example, the serving cell ID field and the BWP ID field may indicate the serving cell and BWP to which the MAC CE applies, and the L1-RSRP field may indicate the measured RSRP on the NZPCSI-RS associated with the reported joint / DL TCI state.

[0098] In some examples, the MAC CE may include a bitmap that includes multiple bits corresponding to multiple active joint or DLTCI states. Figure 3A The illustration shows an example schematic diagram of a MAC CE 310 including a bitmap for indicating an active union or TCI state, according to some example embodiments of the present disclosure. Figure 3A As shown, bitmap 312 may include T7 to T0 corresponding to eight active union or TCI states. For example, one of T7 to T0 may be a first value, and the other Ts in T7 to T0 may be second values, in which case the active union or TCI state corresponding to the first value may be indicated, for example, when the state satisfies a satisfied event. For example, the first value may be 1, and the second value may be 0.

[0099] In some examples, the MAC CE may include the NZP CSI-RS resource ID. Since each federated / DL TCI state contains a QCL D-type RS, such as an NZP CSI-RS, the resource ID of the NZP CSI-RS can be included in the MAC CE to indicate the corresponding active federated / DL TCI state. Figure 3B The illustration shows an example schematic diagram of a MAC CE 320 for an NZP CSI-RS resource ID associated with an activated joint or TCI state, according to some example embodiments of this disclosure. Figure 3B As shown, field 322 may include the NZP CSI-RS resource ID corresponding to the active Federation / DL TCI status.

[0100] In some examples, the MAC CE may include an indication of a TCI code point mapped to an active joint or DL ​​TCI state. Figure 3C The illustration shows an example schematic diagram of a MAC CE 330 including TCI code points mapped to an active union or TCI state, according to some example embodiments of the present disclosure. Figure 3C As shown, field 332 may include TCI code point i. For example, field 332 may have 3 bits. For example, field 332 may indicate the active joint / DL TCI state mapped to TCI code point i.

[0101] In some examples, the MAC CE may include an identifier or identity (ID) of an active or DL ​​TCI state. Figure 3D The illustration shows an example schematic diagram of a MAC CE 340 including an ID of an active union or TCI state, according to some example embodiments of the present disclosure. Figure 3D As shown, field 342 may include a union or DL ​​TCI state ID associated with an active union / DL TCI state.

[0102] In some other example embodiments, the MAC CE may also include an event ID. For example, if more than one event is configured for UE 201, such as two or three of a second, third, and fourth event, the MAC CE may include a field indicating the event that is satisfied.

[0103] In some examples, the MAC CE corresponding to different events can be associated with different LCIDs. For example, different LCIDs can be configured for different events.

[0104] In some other examples, the field may include multiple subfields corresponding to multiple events. For example, a single event field can be configured for multiple events, such as three events: a second event, a third event, and a fourth event. For example, subfields at different positions in the field can correspond to different events. In this case, subfields in a single event field can indicate the corresponding event, while other subfields can be set to predefined values ​​(e.g., all 0) or invalid.

[0105] Figures 4A-4C The diagram illustrates some examples of MAC CEs including event IDs. It should be understood that... Figures 4A-4C The examples shown are for illustrative purposes only and are not intended to limit anything. For example, MAC CE can be based on... Figure 3B / Figure 3C / Figure 3D The MAC CE in the data is used to determine that the event field has three subfields, one of which is associated with the event.

[0106] As mentioned above, beam reports can be transmitted via MAC CE. In some implementations, there may be available UL resources for MAC CE transmission, and the MAC CE may be carried by PUSCH.

[0107] In some other implementations, if no UL resources are available for MAC CE transmission, UE 201 may also send a regular SR or a dedicated SR to request UL resources for transmitting beam reports. For example, a regular SR or a dedicated SR for beam reports can be used to request transmission resources for MAC CE. In some examples, different SRs can be configured with different priorities, and the transmission of regular SRs or dedicated SRs for beam reports can be performed by taking priority into account. For example, the priority of a dedicated SR for beam reports can be higher than the priority of a SR for beam failure reports (BFRs), which in turn is higher than the priority of a regular SR. In some examples, in response to a regular SR or a dedicated SR for beam reports from UE 201, BS 202 may send a first DCI that schedules a PUSCH transmission capable of carrying MAC CE, and therefore, UE 201 can transmit MAC CE based on the first DCI.

[0108] In some implementations, if multiple events are configured for UE 201, more than one event can be satisfied. In this case, the event with the highest priority can be reported. For example, different events can be configured with different priorities. For example, the priority order of these events could be: P(Event 4) > P(Event 3) > P(Event 1) > P(Event 2).

[0109] In some examples, if the first, second, and fourth events are met, the fourth event can be reported. For example, MAC CE can indicate the fourth event and the associated active joint / DL TCI state.

[0110] Refer again Figure 2 Alternatively, BS 202 may determine at 240 whether to perform a TCI state switch for UE 201 based on beam reports.

[0111] In some implementations, the beam report can indicate that the first event has been met. In this case, the beam report does not include a report of the joint / DL TCI state for a potential handover, and BS 202 can, for example, determine on its own whether to switch to another TCI state. That is, it is BS 202 that decides whether to switch to another TCI state.

[0112] In some implementations, the beam report can indicate that a second event has been satisfied. In this case, the reported joint / DL TCI state is included in the beam report; however, the channel quality of the indicated joint / DL TCI state (i.e., the current joint / DL TCI state) is not taken into account for the second event. For example, the current joint / DL TCI state may be sufficient for data transmission. Therefore, UE 201 can follow instructions from BS 202, such as those in the conventional approach.

[0113] In some implementations, beam reports can indicate that a third or fourth event has been met. In this case, the reported joint / DL TCI status is included in the beam report, which can be used for potential handovers.

[0114] In some example embodiments, UE 201 and BS 202 may switch to a reported joint / DL TCI state (one of the active joint / DL TCI states) for further communication. For example, UE 201 and BS 202 may automatically switch to a reported joint / DL TCI state after a specific point in time.

[0115] In some examples, UE 201 may apply a reported joint / DL TCI state 28 symbols after the last symbol received by the PDCCH with a third DCI, the third DCI scheduling a PUSCH transmission with the same Hybrid Automatic Repeat Request (HARQ) procedure number as the first PUSCH transmission, the first PUSCH carrying a MAC CE, and the third DCI having a flipped New Data Indicator (NDI) field value. Figure 5A The illustration shows an example schematic diagram of a TCI state transition 510 according to some example embodiments of the present disclosure. For example... Figure 5A As shown, a beam report can be sent by MAC CE 512, indicating a third or fourth event and the reported joint / DL TCI status. Additionally, DCI 514 can be received, which schedules a PUSCH transmission with the same HARQ procedure number as the first PUSCH transmission, the first PUSCH carrying the MAC CE, and DCI 514 having an inverted NDI field value. The reported joint / DL TCI status can then be applied 28 symbols after the last symbol of the PDCCH carrying DCI 514.

[0116] For example, if the reported joint / DL TCI status is an active joint TCI status, that is, the joint TCI mode is applied, then the active joint TCI status can be applied.

[0117] Another example is that if the reported joint / DL TCI state is an active DL TCI state, then the active DL TCI state can be applied. Furthermore, the UL TCI state can be further determined. In some cases, there may be paired UL TCI states that map to the same TCI code point as the active DL TCI state (i.e., the reported DL TCI state), and then UE 201 can apply both the active DL TCI state and the paired UL TCI state. In some other cases, there may not be a paired UL TCI state mapped to the same TCI code point as the active DL TCI state (i.e., the reported DLTCI state), in which case the current UL TCI state can continue to be applied; in other words, UE 201 can apply the active DL TCI state and maintain the current UL TCI state.

[0118] Therefore, the joint or DL ​​TCI status of the report can be applied, and the additional DCI with format 1_1 / 1_2 is not required to indicate the joint or DL ​​TCI status of the report. As a result, signaling overhead can be reduced, and TCI status switching can be more efficient.

[0119] In some example embodiments, the reported joint / DL TCI state may not be applied automatically. In some example embodiments, UE 201 may expect to receive a DCI with format 1_1 / 1_2, which indicates a TCI code point mapped to the reported joint / DL TCI state, for example, after receiving the DCI format, which schedules a PUSCH transmission with the same HARQ procedure number as the transmission of the first PUSCH, the first PUSCH carrying a MAC CE, and the DCI format having an inverted NDI field value.

[0120] In some examples, after receiving a beam report (i.e., a MAC CE including the reported joint / DL TCI state), BS 202 may send a second DCI with format 1_1 / 1_2, indicating a different joint / DL TCI state. For example, the different indicated joint / DL TCI state may differ from the current joint / DL TCI state, and the different indicated joint / DL TCI state may be a new TCI state. For example, the second DCI may instruct UE 201 to perform a TCI state switch.

[0121] In some examples, if UE 201 receives a second DCI with format 1_1 / 1_2 before receiving the DCI format, UE 201 can apply a new TCI state, wherein the second DCI indicates a new TCI state, the DCI format scheduling a PUSCH transmission with the same HARQ procedure number as the transmission of the first PUSCH, the first PUSCH carrying a MAC CE, and the DCI format having an inverted NDI field value. Figure 5B The illustration shows an example schematic diagram of a TCI state transition 520 according to some example embodiments of the present disclosure. For example... Figure 5B As shown, a beam report can be sent by MAC CE 522, indicating a third or fourth event and the reported joint / DL TCI status. Additionally, a DCI 524 indicating a new TCI status can be received. The new joint / DL TCI status can then be applied after the beam application time from the last symbol of the Physical Uplink Control Channel (PUCCH) / PUSCH 526.

[0122] For example, PUCCH / PUSCH 526 can carry a positive HARQ-ACK corresponding to DCI 524 indicating a new TCI state. For example, the beam application time can be N symbols from a set of {1, 2, 4, 7, 14, 28, 42, 56, 70, 84, 98, 112, 224, 336} symbols.

[0123] According to the reference Figures 2-5B In some embodiments, UE 201 can send event-driven beam reports to BS 202, and BS 202 can therefore use the beam reports for consideration, for example, for potential TCI state switching. This can thus save signaling overhead and make TCI state switching more efficient.

[0124] It should be understood that BS 202 can be implemented as a TRP, for example, this disclosure can be applied to a single TRP scenario. For example, periodic CSI-RS resources associated with all active joint or DL ​​TCI states (which can be CSI-RS for beam management or tracking reference signals (TRS)) are identified as a single measurement resource pool for a single TRP scenario. UE 201 can monitor the quality of these CSI-RS resources and compare them with a configured threshold, or with the quality of the indicated joint / DL TCI state, to determine whether to trigger beam reporting.

[0125] In some other cases, this disclosure can also be applied to multi-TRP scenarios. For example, the above embodiments can be directly extended to multi-TRP scenarios. For example, a resource pool for measurement can be determined for each TRP, and an event can be triggered for each TRP.

[0126] For a single-DCI-based multi-TRP (S-DCI MTRP), all first joint / DL TCI states mapped to each active TCI code point in the active TCI code points are determined as a first measurement resource set for the first TRP, and all second joint / DL TCI states mapped to each active TCI code point in the active TCI code points are determined as a second measurement resource set for the second TRP. For a multi-DCI-based multi-TRP (M-DCI MTRP), all active joint / DL TCI states specific to a coresetPoolIndex value of 0 are determined as a first measurement resource set for the first TRP, and all active joint / DL TCI states specific to a coresetPoolIndex value of 1 are determined as a second measurement resource set for the second TRP.

[0127] The combined / DL TCI state of the two indicators used for the S-DCI MTRP is determined as the combined / DL TCI state of the first indicator and the combined / DL TCI state of the second indicator. For the M-DCI MTRP, the combined / DL TCI state of the first indicator and the combined / DL TCI state of the second indicator are respectively the combined / DL TCI state specific to coresetPoolIndex value 0 and the combined / DL TCI state specific to coresetPoolIndex value 1. That is, the current TCI state of the first TRP is the combined / DL TCI state of the first indicator, and the current TCI state of the second TRP is the combined / DL TCI state of the second indicator.

[0128] UE 201 can evaluate each event for each TRP level. In some examples, an event for a first TRP can be satisfied, and / or another event for a second TRP can be satisfied; furthermore, UE 201 can send an SR or MACCE, which may include beam reports for the first TRP and / or the second TRP. For example, the SR or MACCE may include fields for indicating the first TRP and / or the second TRP.

[0129] For example, if UE 201 identifies any of the joint / DL TCI states in the first measurement resource set as being better than the first indicated TCI state offset, then event 3 corresponding to the first TRP will be triggered. If UE 201 identifies a second indicated TCI state as becoming worse than a threshold, and at least one TCI state in the second measurement resource set is identified as becoming better than a threshold, then event 4 corresponding to the second TRP will be triggered.

[0130] In this way, event-driven beam reports can be sent to BS 202, and BS 202 can know at least the channel quality associated with the indicated joint / DL TCI state. In some examples, UE 201 and BS 202 can apply better TCI states, such as the reported joint / DL TCI state in the beam report (if available), and therefore signaling overhead can be reduced, and TCI state switching can be more efficient. In some other examples, BS 202 can consider the beam report and determine whether to perform a TCI state switch for UE 201, and therefore the decision made by BS 202 will be more accurate.

[0131] Figure 6 An example of a device 600 suitable for implementing embodiments of the present disclosure is illustrated. Device 600 may be an example of a base station or UE as described herein. Device 600 may support wireless communication with UE 201, base station 202, or any combination thereof. Device 600 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 602, memory 604, transceiver 606, and optional I / O controller 608). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0132] Processor 602, memory 604, transceiver 606, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 602, memory 604, transceiver 606, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0133] In some implementations, processor 602, memory 604, transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 604 by processor 602).

[0134] For example, according to the examples disclosed herein, processor 602 may support wireless communication at device 600. Processor 602 may be configured to operate to support components used for the operations described above.

[0135] Processor 602 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 602 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory (e.g., memory 604) to cause device 600 to perform various functions of this disclosure.

[0136] Memory 604 may include random access memory (RAM) and read-only memory (ROM). Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 602, cause device 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 602, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 604 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0137] I / O controller 608 can manage the input and output signals of device 600. I / O controller 608 can also manage peripheral devices not integrated into device 600. In some implementations, I / O controller 608 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 608 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, I / O controller 608 can be implemented as part of a processor, such as processor 602. In some implementations, a user can interact with device 600 via I / O controller 608 or via hardware components controlled by I / O controller 608.

[0138] In some implementations, device 600 may include a single antenna 610. However, in other implementations, device 600 may have more than one antenna 610 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 606 may communicate bidirectionally via one or more antennas 610, wired or wireless links, as described herein. For example, transceiver 606 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 606 may also include a modem for modulating packets, providing modulated packets to one or more antennas 610 for transmission, and demodulating packets received from one or more antennas 610. Transceiver 606 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0139] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 610 for transmitting the amplified signal over the air or wireless medium.

[0140] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 610 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0141] Figure 7 An example of a processor 700 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0142] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 700) or included in the processor chipset), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0143] Controller 702 can be configured to manage and coordinate various operations of processor 700 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 700 to support various operations according to the examples described herein. For example, controller 702 can operate as a control unit of processor 700 to generate control signals for managing the operation of various components of processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0144] Controller 702 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 704 and determine subsequent instructions(s) to be executed, enabling processor 700 to support various operations according to the examples described herein. Controller 702 can be configured to track the memory addresses of instructions associated with memory 704. Controller 702 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 702 can be configured to interpret instructions and determine control signals to be output to other components of processor 700, enabling processor 700 to support various operations according to the examples described herein. Additionally or alternatively, controller 702 can be configured to manage data flow within processor 700. Controller 702 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0145] Memory 704 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., native to or included in processor 700). In some implementations, memory 704 may reside within or on the processor chipset (e.g., native to processor 700). In some other implementations, memory 704 may reside outside the processor chipset (e.g., remote from processor 700).

[0146] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and these processors and memories may be configured individually or collectively to perform the various functions described herein.

[0147] One or more ALU 706s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 706s may reside within or on a processor chipset (e.g., processor 700). In some other implementations, one or more ALU 706s may reside outside the processor chipset (e.g., processor 700). One or more ALU 706s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 706s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 706s are configured with a variety of logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 706s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0148] Based on the examples disclosed herein, processor 700 may support wireless communication. Processor 700 may be configured or operable to support components used in some embodiments of this disclosure.

[0149] Figure 8 A flowchart illustrating a method 800 performed by a UE according to various aspects of this disclosure is shown. The operation of method 800 can be implemented by the device or its components described herein. For example, the operation of method 800 can be performed by… Figure 2The UE 201 is executed. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described functions.

[0150] At 810, the method may include: determining that an event associated with the indicated joint or DL ​​TCI state has been satisfied. The operation of 810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 810 may be derived from references... Figure 2 The aforementioned UE 201 is executed.

[0151] At 820, the method may include: based on a determination that a triggering condition associated with an event is met, sending a beam report to a base station, the beam report indicating one of the following: the event, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state. The operation of 820 can be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be derived from references... Figure 2 The aforementioned UE 201 is executed.

[0152] Figure 9 A flowchart illustrating a method 900 performed by a base station according to various aspects of this disclosure is shown. Operation of method 900 can be implemented by the devices or components thereof described herein. For example, operation of method 900 can be performed by… Figure 2 The BS 202 in the system executes the function. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described function. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described function.

[0153] At 910, the method may include: sending downlink control information (DCI) to the UE, the DCI indicating an indicated joint or DL ​​TCI state. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references. Figure 2 The aforementioned BS 202 is executed.

[0154] At 920, the method may include: receiving a beam report from the UE, the beam report indicating one of the following: an event associated with the indicated joint or DL ​​TCI state, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state. The operation of 920 can be performed according to the examples described herein. In some implementations, aspects of the operation of 920 may be derived from references... Figure 2 The aforementioned BS 202 is executed.

[0155] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0156] The various illustrative blocks and components described herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0157] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0158] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0159] As used herein, including in the claims, the article “a” preceding an element is a non-limiting article and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or both of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, a “set” may include one or more elements.

[0160] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the UE: The event associated with the indicated combined or downlink (DL) Transport Configuration Indicator (TCI) state is satisfied; and Based on the determination that the triggering condition associated with the event is met, a beam report is sent to the base station, the beam report indicating one of the following: the event, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

2. The UE according to claim 1, wherein the triggering condition includes one of the following: The event is satisfied, or The event has been satisfied multiple times consecutively within a time window, wherein the number of consecutive times is predefined or preconfigured.

3. The UE according to claim 1, wherein the event includes one of the following: The first event indicates that the quality of the indicated joint or DL ​​TCI state is less than or no greater than a first threshold. The second event indicates that the quality of one of the active joint or DL ​​TCI states exceeds or is not less than a second threshold. The third event indicates that the difference between the quality of one of the activated joint or DL ​​TCI states and the quality of the indicated joint or DL ​​TCI state exceeds or is not less than a third threshold, or The fourth event indicates that the quality of the indicated joint or DL ​​TCI state is less than or no greater than a fourth threshold, and the quality of one of the activated joint or DL ​​TCI states exceeds or is not less than a fifth threshold.

4. The UE of claim 1, wherein at least one threshold associated with the event is at least one block error rate (BLER), and the at least one BLER is determined based on: One or more specific hypothetical physical downlink control channel (PDCCH) transmission parameters, or Layer 1 Reference Signal Received Power (L1-RSRP) configured by Radio Resource Control (RRC) signaling.

5. The UE of claim 3, wherein the event includes the first event, and the beam report is included in the scheduling request (SR).

6. The UE of claim 3, wherein the event includes one of the second event, the third event, or the fourth event, and wherein the beam report is included in a Media Access Control (MAC) control element (CE), the MAC CE indicating one of the active joint or DL ​​TCI states.

7. The UE of claim 6, wherein the MAC CE includes a bitmap, wherein a bit in the bitmap corresponding to one of the active joint or DL ​​TCI states of the bandwidth portion (BWP) of the serving cell for the UE is set to a specific value.

8. The UE of claim 6, wherein the MAC CE comprises one of the following: The identifier (ID) of one of the active joint or DL ​​TCI states. The non-zero power (NZP) channel state information (CSI) reference signal (RS) resource ID associated with one of the active joint or DL ​​TCI states, or An indication of a TCI code point that is mapped to one of the active joint or DL ​​TCI states.

9. The UE of claim 6, wherein different events are associated with different logical channel identifiers (LCIDs), and wherein the MAC CE further includes the LCID associated with the event.

10. The UE of claim 6, wherein different events are associated with the same LCID, and wherein the MAC CE comprises: The LCID is carried in a specific location associated with the event.

11. The UE of claim 6, wherein the at least one processor is further configured such that the UE: Send a dedicated SR to the base station to request transmission resources from the MAC CE; and The base station receives first downlink control information (DCI), which schedules the transmission of the Physical Uplink Shared Channel (PUSCH) carrying the MAC CE.

12. The UE of claim 3, wherein the event includes the first event or the second event, and wherein the at least one processor is configured to cause the UE to: Receive a second DCI from the base station, the second DCI indicating another indicated joint or DL ​​TCI state, wherein the other indicated joint or DL ​​TCI state is the same as or different from the active joint or DL ​​TCI state in the beam report; and Apply the other indicated joint or DL ​​TCI state to another transmission or reception.

13. The UE of claim 6, wherein the event includes the third event or the fourth event, and wherein the at least one processor is configured to cause the UE to: The activated joint or DL ​​TCI state is applied after a specific time point, wherein the specific time point is 28 symbols from the last symbol received by the PDCCH with the third DCI, the third DCI scheduling a PUSCH transmission with the same Hybrid Automatic Repeat Request (HARQ) process number as the transmission of the first PUSCH, the first PUSCH carrying the MAC CE, and the third DCI having a flipped New Data Indicator (NDI) field value.

14. The UE of claim 13, wherein the at least one processor is configured such that the UE: Based on the determination of the existence of an uplink (UL) TCI state paired with the activated DL TCI state, the ULTCI state is applied to another transmission; or Based on the determination that there is no UL TCI state paired with the activated DL TCI state, the current UL TCI state continues to be applied to another transmission.

15. The UE of claim 6, wherein the at least one processor is configured such that the UE: A second DCI is received from the base station prior to the third DCI, the second DCI indicating another indicated joint or DL ​​TCI state, wherein the third DCI is scheduling a PUSCH transmission with the same HARQ procedure number as the first PUSCH transmission, the first PUSCH carrying the MAC CE, and the third DCI has an inverted NDI field value; and Apply the other indicated joint or DL ​​TCI state to another transmission or reception.

16. A base station, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the base station: Send downlink control information (DCI) to user equipment (UE), the DCI indicating the combined or downlink (DL) transmission configuration indicator (TCI) status; as well as The UE receives a beam report indicating one of the following: an event associated with the indicated joint or DLTCI state, or an active joint or DLTCI state other than the indicated joint or DLTCI state.

17. The base station of claim 16, wherein the event includes one of the following: The first event indicates that the quality of the indicated joint or DL ​​TCI state is less than or no greater than a first threshold. The second event indicates that the quality of one of the active joint or DL ​​TCI states exceeds or is not less than a second threshold. The third event indicates that the difference between the quality of one of the activated joint or DL ​​TCI states and the quality of the indicated joint or DL ​​TCI state exceeds or is not less than a third threshold, or The fourth event indicates that the quality of the indicated joint or DL ​​TCI state is less than or no greater than a fourth threshold, and the quality of one of the activated joint or DL ​​TCI states exceeds or is not less than a fifth threshold.

18. The base station of claim 16, wherein at least one threshold associated with the event is at least one block error rate (BLER), and the at least one BLER is determined based on: One or more specific hypothetical physical downlink control channel (PDCCH) transmission parameters, or Layer 1 Reference Signal Received Power (L1-RSRP) configured by Radio Resource Control (RRC) signaling.

19. A method performed by a user equipment (UE), comprising: The event associated with the indicated combined or downlink (DL) transport configuration indicator (TCI) state is satisfied; as well as Based on the determination that the triggering condition associated with the event is met, a beam report is sent to the base station, the beam report indicating one of the following: the event, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

20. A processor for wireless communication, comprising at least one controller coupled to at least one memory and configured such that the processor: The event associated with the indicated combined or downlink (DL) Transport Configuration Indicator (TCI) state is satisfied; and Based on the determination that the triggering condition associated with the event is met, a beam report is sent to the base station, the beam report indicating one of the following: the event, or an active joint or DL ​​TCI state other than the indicated joint or DL ​​TCI state.

Images