Event-triggered beam reporting for integrated TCI

Abstract

Exemplary embodiments of the present disclosure relate to user equipment, base stations, methods, devices, and computer-readable media for event-triggering beam reporting for an integrated TCI. In the solution, the UE may transmit a beam report indicating that an event associated with a indicated common or DL ​​TCI state has been satisfied. In some cases, the beam report may also indicate an active common or DL ​​TCI state that is different from the indicated common or DL ​​TCI state. Thus, the BS can recognize at least the channel quality associated with the indicated common / DL TCI state, and thus, further decisions regarding whether to switch the TCI state can be made.

Description

Technology Field

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

[0002] A wireless communication system may include one or more network communication devices, e.g., base stations, which may be known differently as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device, e.g., a base station, may support wireless communication with one or more user communication devices, which may be known differently as User Equipment (UE) or other suitable terms. A 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, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including 3rd generation (3G) radio access technology, 4th generation (4G) radio access technology, and 5th generation (5G) radio access technology, among other suitable radio access technologies other than 5G (e.g., 6th generation (6G)).

[0003] Although beam measurement and beam reporting controlled by the network (NW) are defined, the network needs to configure or enable frequent periodic or semi-permanent beam reporting, or trigger frequent periodic beam reporting, which results in greater overhead.

[0004] The present disclosure relates to a base station, user equipment, methods, devices, processors, and a computer-readable medium for event-triggered beam reporting for an integrated TCI. According to the proposed solution, a beam report can be transmitted when an event associated with an indicated joint or downlink (DL) TCI state is satisfied, thus defining the UE behavior for beam reporting and saving 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 the at least one processor is configured to cause the UE to: determine that an event associated with a indicated joint or DL ​​TCI state is satisfied; and, upon determining that a trigger condition associated with the event is satisfied, to transmit to a base station a beam report indicating the event, or one of an active joint or DL ​​TCI state different from the indicated joint or DL ​​TCI state.

[0006] In some implementations, a base station is provided. The base station comprises at least one memory; and at least one processor coupled to the at least one memory, and the at least one processor is configured to cause the base station to: transmit downlink control information (DCI) indicating an indicated common or DL ​​TCI state to a UE; and receive from the UE an event associated with the indicated common or DL ​​TCI state, or a beam report indicating one of an active common or DL ​​TCI state different from the indicated common or DL ​​TCI state.

[0007] In some implementations, a method performed by a UE is provided. The method includes the step of determining that an event associated with a indicated joint or DL ​​TCI state is satisfied; and the step of transmitting a beam report to a base station indicating the event, or one of an active joint or DL ​​TCI state different from the indicated joint or DL ​​TCI state, in accordance with the determination that a trigger condition associated with the event is satisfied.

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

[0009] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled with at least one memory, and the at least one controller is configured to cause the processor to: determine that an event associated with a indicated joint or DL ​​TCI state is satisfied; and, upon determining that a trigger condition associated with the event is satisfied, to transmit to a base station a beam report indicating the event, or one of an active joint or DL ​​TCI state different from 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 with at least one memory, and the at least one controller is configured to cause the processor to: transmit to the UE a DCI indicating an indicated joint or DL ​​TCI status; and receive from the UE an event associated with the indicated joint or DL ​​TCI status, or a beam report indicating one of an active joint or DL ​​TCI status different from the indicated joint or DL ​​TCI status.

[0011] In the methods and some implementations of the UE described herein, the method further comprises the step of transmitting a dedicated scheduling request (SR) to a base station for requesting a transmission resource of a media access control (MAC) control element (CE); and receiving from the base station a first DCI for scheduling a physical uplink shared channel (PUSCH) transmission carrying the MAC CE.

[0012] In the methods and some implementations of the UE described herein, an event comprises a first event or a second event, which comprises receiving a second DCI from a base station indicating an additional indicated joint or DL ​​TCI state—the additional indicated joint or DL ​​TCI state being the same or different from the activated joint or DL ​​TCI state in the beam report—and further comprising applying the additional indicated joint or DL ​​TCI state for further transmission or reception.

[0013] In the methods and some implementations of the UE described herein, the event includes a third event or a fourth event, which further includes applying a joint or DL ​​TCI state activated after a specific point in time, and the specific point in time is 28 symbols from the last symbol of a physical downlink control channel (PDCCH) reception having a third DCI having a toggled new data indicator (NDI) field value, scheduling a PUSCH transmission having the same hybrid automatic repeat request (HARQ) process number as for the transmission of the first PUSCH carrying MAC CE.

[0014] In the methods described herein and in some implementations of the UE, applying the UL TCI state for further transmission upon determining that there exists an uplink (UL) TCI state paired with the activated DL TCI state; or continuing to apply the current UL TCI state for further transmission upon determining that there does not exist a UL TCI state paired with the activated DL TCI state.

[0015] In the methods described herein and in some implementations of the UE, receiving from a base station a second DCI indicating an additional indicated common or DL ​​TCI status before a third DCI—the third DCI scheduling a PUSCH transmission having the same HARQ process number as for the transmission of the first PUSCH carrying MAC CE and having a toggled NDI field value—and further including applying an additional indicated common or DL ​​TCI status for additional transmission or reception.

[0016] In the methods and some implementations of the BS described herein, receiving a dedicated SR from the UE to request a transmission resource for MAC CE; and further including transmitting a first DCI to the UE to schedule a PUSCH transmission carrying MAC CE.

[0017] In the methods and some implementations of the BS described herein, the event comprises a first event or a second event, which further comprises transmitting to the UE a second DCI indicating an additional indicated joint or DL ​​TCI state—the additional indicated joint or DL ​​TCI state being the same or different from the activated joint or DL ​​TCI state in the beam report—and further comprising applying the additional indicated joint or DL ​​TCI state for further transmission or reception with the UE.

[0018] In the methods and some implementations of BS described herein, the event includes a third event or a fourth event, which further includes applying a joint or DL ​​TCI state activated after a specific point in time, and the specific point in time is 28 symbols from the last symbol of a PDCCH reception having a third DCI having a toggled NDI field value, scheduling a PUSCH transmission having the same HARQ process number as for a transmission of a first PUSCH carrying a MAC CE.

[0019] In the methods described herein and in some implementations of BS, applying the UL TCI state for further transmission upon determining that there exists a UL TCI state paired with the activated DL TCI state; or continuing to apply the current UL TCI state for further transmission upon determining that there does not exist a UL TCI state paired with the activated DL TCI state.

[0020] In the methods described herein and in some implementations of BS, transmitting to the UE a second DCI indicating an additional indicated joint or DL ​​TCI status before a third DCI—the third DCI scheduling a PUSCH transmission having the same HARQ process number as for the transmission of the first PUSCH carrying MAC CE and having a toggled NDI field value—and further comprising applying an additional indicated joint or DL ​​TCI status for further transmission or reception with the UE.

[0021] In some implementations of the methods, UE, and BS described herein, the trigger condition comprises one of an event being satisfied or an event being satisfied for a plurality of consecutive times within a time window, and the plurality of consecutive times is predefined or preconfigured.

[0022] In some implementations of the methods, UE, and BS described herein, the event comprises: 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 activated 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 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 one of 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 activated joint or DL ​​TCI states exceeds or is not less than a fifth threshold.

[0023] In some implementations of the methods, UE, and BS described herein, at least one threshold value 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 virtual PDCCH transmission parameters, or a layer 1 reference signal received power (L1-RSRP) configured by radio resource control (RRC) signaling.

[0024] In the methods, UE, and some implementations of BS described herein, the event includes a first event, and the beam report is included in the SR.

[0025] In some implementations of the methods, UE, and BS described herein, the event includes one of a second event, a third event, or a fourth event, and the beam report is included in a MAC CE indicating one of the activated co- or DL ​​TCI states.

[0026] In some implementations of the methods, UE, and BS described herein, MAC CE includes a bitmap, and a bit in the bitmap corresponding to one of the activated joint or DL ​​TCI states for the bandwidth portion (BWP) of the UE's serving cell is set to a specific value.

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

[0028] In some implementations of the methods, UE, and BS described herein, different events are associated with different logical channel identities (LCIDs), and MAC CE further includes the LCID associated with the event.

[0029] In the methods, UE, and some implementations of BS described herein, different events are associated with the same LCID, and MAC CE includes an LCID carried at a specific location associated with the event. Brief explanation of the drawing

[0030] FIG. 1 illustrates an example of a wireless communication system in which some embodiments of the present disclosure may be implemented. FIG. 2 illustrates an exemplary schematic diagram of a timing relationship for the transmission of a PRACH preamble according to some exemplary embodiments of the present disclosure. FIG. 3a illustrates an exemplary schematic diagram of a MAC CE including a bitmap for indicating an activated co- or TCI state according to some exemplary embodiments of the present disclosure. FIG. 3b illustrates an exemplary schematic diagram of a MAC CE including an NZP CSI-RS resource ID associated with an activated co- or TCI state according to some exemplary embodiments of the present disclosure. FIG. 3c illustrates an exemplary schematic diagram of a MAC CE indicating a TCI code point mapped to an activated co- or TCI state according to some exemplary embodiments of the present disclosure. FIG. 3d illustrates an exemplary schematic diagram of a MAC CE including an ID of an activated cavity or TCI state according to some exemplary embodiments of the present disclosure. FIG. 4a illustrates an exemplary schematic diagram of a MAC CE including an ID of an activated joint or TCI state and an event ID according to some exemplary embodiments of the present disclosure. FIG. 4b illustrates an exemplary schematic diagram of a MAC CE including an NZP CSI-RS resource ID and an event ID according to some exemplary embodiments of the present disclosure. FIG. 4c illustrates an exemplary schematic diagram of a MAC CE including an activated co- or TCI state and a TCI code point mapped to an event ID according to some exemplary embodiments of the present disclosure. FIG. 5a illustrates an exemplary schematic diagram for TCI state switching according to some exemplary embodiments of the present disclosure. FIG. 5b illustrates another exemplary schematic diagram for TCI state switching according to some exemplary embodiments of the present disclosure. FIG. 6 illustrates an example of a device suitable for implementing embodiments of the present disclosure. FIG. 7 illustrates an example of a processor suitable for implementing some embodiments of the present disclosure. FIG. 8 illustrates a flowchart of an exemplary method implemented in a UE according to embodiments of the present disclosure. FIG. 9 illustrates a flowchart of an exemplary method implemented in BS according to embodiments of the present disclosure. Throughout the drawings, identical or similar reference numbers represent identical or similar elements. Specific details for implementing the invention

[0031] Now, the principles of the present disclosure will be described with reference to some embodiments. These embodiments are described merely for illustrative purposes and are intended to help those skilled in the art understand and implement the present disclosure and do not imply any limitation to the scope of the present disclosure. The disclosure described herein may 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 generally understood by those skilled in the art to which the present disclosure pertains.

[0032] References to “one embodiment,” “exemplary embodiment,” “embodiment,” “some embodiments,” and similar terms in this disclosure indicate that the described embodiment(s) may include a particular feature, structure, or characteristic, but not that all embodiments must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment(s). Moreover, where a particular feature, structure, or characteristic is described in relation to an embodiment, it is suggested that implementing such feature, structure, or characteristic in relation to other embodiments is within the knowledge of a person skilled in the art, whether or not explicitly described.

[0033] Additionally, it should be understood that while terms such as "first," "second," or similar are used in this specification to describe various elements, these elements are not limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of the embodiments, the first element may also be referred to as the second element, and likewise, the second element may also be referred to as the first element. As used in this specification, the term "and / or" includes any and any combination of one or more of the listed terms. In some examples, values, procedures, or devices may be referred to as "best," "lowest," "highest," "minimum," "maximum," or similar. These descriptions are intended to indicate that a selection may be made among a number of functional alternatives used, and it should be understood that such a selection is not necessarily superior, smaller, higher, or otherwise more desirable than other selections.

[0034] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include plural forms unless the context clearly indicates otherwise. Furthermore, as used herein, terms such as “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the mentioned features, elements, components, and / or similar things, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “includes” and variations thereof should be interpreted as open terms meaning “includes but not limited thereto.” The term “based on” should be interpreted as “at least partially based on.” The terms “one embodiment” and “embodiment” should be interpreted as “at least one embodiment.” The term "other embodiment" shall be interpreted as "at least one other embodiment." The use of expressions such as "A and / or B" may mean "A alone," "B alone," or "both A and B." Other explicit or implicit definitions may be included below.

[0035] FIG. 1 illustrates 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 equipment (NE)), one or more UEs (104), a core network (CN) (106), and a packet data network (108). The wireless communication system (100) may support various radio 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 LTE-advanced (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 a 4G network and a 5G network, or other suitable radio access technology including IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system (100) may support radio access technologies beyond 5G. Additionally, the wireless communication system (100) may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0036] One or more network entities (102) may be distributed across a geographical area to form a wireless communication system (100). One or more of the network entities (102) described herein may be network nodes, base stations, network elements, radio access network (RAN) nodes, base transceiver stations, access points, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms, may include or be referred to as such. Network entities (102) and UEs (104) may communicate through a communication link (110) which may be a wireless or wired connection. For example, network entities (102) and UEs (104) may perform wireless communication (e.g., receiving signaling, transmitting signaling) through a Uu interface.

[0037] A network entity (102) may provide a geographic coverage area (112), and the network entity (102) may support services (e.g., voice, video, packet data, messages, broadcasts, etc.) for one or more UEs (104) within the geographic coverage area (112). For example, the network entity (102) and the UE (104) may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcasts, etc.) according to one or more radio access technologies. In some implementations, the network entity (102) may be mobile and may be, 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 may overlap, but different geographic coverage areas (112) may be associated with different network entities (102). The information and signals described herein may be represented using any of several different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification may be represented as voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0038] One or more UEs (104) may be distributed across the geographical area of ​​the wireless communication system (100). The UE (104) may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or any other suitable term. In some implementations, the UE (104) may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, the UE (104) may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, the UE (104) may be fixed within the wireless communication system (100). In some other implementations, the UE (104) may be mobile within the wireless communication system (100).

[0039] One or more UEs (104) may be devices having different forms or different capabilities. Some examples of UEs (104) are illustrated in FIG. 1. As illustrated in FIG. 1, the UE (104) may communicate with various types of devices, such as network entities (102), other UEs (104), or network equipment (e.g., CN (106), packet data network (108), relay devices, integrated access and backhaul (IAB) nodes, or other network equipment). Additionally or alternatively, the UE (104) may support communication with other network entities (102) or UEs (104) that can act as relays within the wireless communication system (100).

[0040] The UE (104) may also support direct wireless communication with other UEs (104) via a communication link (114). For example, the UE (104) may support direct wireless communication with other UEs (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, the communication link (114) may be referred to as a sidelink (SL). For example, the UE (104) may support direct wireless communication with other UEs (104) via a PC5 interface.

[0041] A network entity (102) may support communication with a CN (106), another network entity (102), or both. For example, a network entity (102) may interface with a CN (106) through one or more backhaul links (116) (e.g., through S1, N2, N3, or other network interfaces). Network entities (102) may communicate with each other through backhaul links (116) (e.g., through X2, Xn, or other network interfaces). 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., through a CN (106)). In some implementations, one or more network entities (102) may include subcomponents such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs (104) through one or more other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0042] In some implementations, the network entity (102) may be configured as a disaggregated architecture, which may be configured to use protocol stacks that are physically or logically distributed between two or more network entities (102), such as an integrated access backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration overseen by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, the network entity (102) may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0043] The RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). One or more components of network entities (102) within a segregated RAN architecture may be co-located, or one or more components of network entities (102) may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities (102) of a segregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0044] The functional partitioning between the CU, DU, and RU can be flexible and support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, functional partitioning of the protocol stack can be utilized between the CU and the DU, thereby 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 functions and signaling of higher protocol layers (e.g., Layer 3 (L3), Layer 2 (L2)) (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). A CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host the functionality and signaling of lower protocol layers, for example, Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each may be controlled at least partially by the CU.

[0045] Additionally or alternatively, functional partitioning of the protocol stack may be utilized between the DU and the RU, thereby 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 may support one or more different cells (e.g., through one or more RUs). In some implementations, functional partitioning between the CU and the DU, or between the DU and the RU, may be performed within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by the other of the CU, DU, or RU).

[0046] The CU can be functionally further divided into CU control plane (CU-CP) functions 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 communication links or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of the protocol stack supported by their respective network entities (102) communicating through such communication links.

[0047] CN (106) may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN (106) may be an evolved packet core (EPC) or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)), and a user plane entity that routes packets or interconnects them to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, a control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.), for one or more UEs (104) served by one or more network entities (102) associated with the CN (106).

[0048] CN (106) may communicate with a packet data network (108) through one or more backhaul links (116) (e.g., through S1, N2, N3 or other network interfaces). The packet data network (108) may include an application server (118). In some implementations, one or more UEs (104) may communicate with the application server (118). The UE (104) may establish a session with CN (106) (e.g., a protocol data unit (PDU) session or similar) through a network entity (102). CN (106) may use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, and similar) between the UE (104) and the application server (118). A PDU session may be an example of a logical connection between a UE (104) and a CN (106) (e.g., one or more network functions of the CN (106)).

[0049] In a wireless communication system (100), network entities (102) and UEs (104) can perform various operations (e.g., wireless communications) using the resources of the wireless communication system (100) (e.g., time resources (e.g., symbols, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers)). In some implementations, network entities (102) and UEs (104) may support different resource structures. For example, network entities (102) and UEs (104) may support different frame structures. In some implementations, for example in 4G, network entities (102) and UEs (104) may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, network entities (102) and UEs (104) can support various frame structures (i.e., multiple frame structures). Network entities (102) and UEs (104) can support various frame structures based on one or more numerologies.

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

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

[0052] Additionally or alternatively, the time intervals of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may contain a number (e.g., a large number) of slots. The number of slots within each subframe may also depend on one or more numerologies supported by the wireless communication system (100). For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with their respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may each use a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe. Each slot may contain a number (e.g., a large number) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some implementations, the number of slots per subframe (e.g., quantity) may depend on the numerology. For a standard cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the standard cyclic prefix and the extended cyclic prefix may depend on the numerology. It should be understood that a reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

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

[0054] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology including 15 kHz subcarrier spacing (e.g., μ=0); a second numerology including 30 kHz subcarrier spacing (e.g., μ=1); and a third numerology including 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology including 60 kHz subcarrier spacing (e.g., μ=2); and a fourth numerology including 120 kHz subcarrier spacing (e.g., μ=3).

[0055] NW control beam measurement and beam reporting for beam management were defined in the first release of NR and were improved from Release 16 (Rel-16) to Release 18 (Rel-18) for performance improvement or to reduce signaling overhead. To acquire the quality of beams of interest in a timely manner, e.g., the quality of the active TCI state(s) for the BWP of a serving cell, the network needs to configure or enable frequent periodic or semi-permanent beam reporting (e.g., N best beams and corresponding L1-RSRPs) or trigger frequent non-periodic beam reporting. However, this behavior clearly results in greater uplink (UL) reporting overhead. Beams in FR2 can be represented by reference signals. For example, a DL beam can be represented by an NZP CSI-RS resource or an SSB resource. A beam ID can be represented by an NZP CSI-RS resource ID or an SSB resource ID. When a beam is indicated for DL ​​reception, the UE can receive a DL signal having the same Rx spatial filter parameters for receiving the NZP CSI-RS resource or SSB resource representing the beam. Beam information for DL ​​reception is indicated or configured by a joint or DL ​​TCI state by including a DL reference signal resource in a TCI state having QCL type D. Beam measurement and beam reporting procedures are configured by a CSI reporting configuration, and beam reporting is carried by a CSI reporting.

[0056] For example, when an integrated TCI framework is configured for a serving cell, the NW may enable up to eight common or DL ​​TCI states for the TRP, any one of which may be indicated for the DL channel or RS reception. To ensure indicated TCI states with better performance, frequent beam reporting for beams corresponding to the enabled TCI states is required. Given that the UE possesses better and more timely knowledge of beam quality changes for each enabled TCI state, a UE-initiated beam reporting procedure utilizing designated events can lead to more timely beam reporting while reducing reporting overhead. Under this procedure, if the UE determines that conditions for one or more designated events are met, the UE can trigger a beam report without the need for the network to configure or trigger frequent reporting. On such grounds, the following objectives for the advancement of Release 19 (Rel-19) Multiple Input Multiple Output (MIMO) have been approved.

[0057] o For FR2 and TRP with intra-cell and inter-cell beam management, define enhancements to facilitate UE-initiated / event-triggered beam management to reduce overhead and / or latency by assuming an integrated TCI while utilizing legacy CSI measurement and reporting configuration frameworks (as much as possible).

[0058] - UL signaling content(s) (and required procedure(s)) for UE-initiated / event-triggered beam reporting to facilitate high-speed beam switching.

[0059] - A UL signaling medium / container designed primarily for beam reporting purposes, taking into account the UE-initiated / event-triggered nature of UL transmission.

[0060] Embodiments of the present disclosure provide a solution for event-triggered beam reporting for an integrated TCI. In the solution, a UE can determine whether an event associated with an indicated joint / DL TCI state is satisfied, for example, the UE may consist of one or more events. The UE may further transmit a beam report to a base station when the conditions for the event are satisfied, and as such, the beam report may be used by the base station for further consideration, such as TCI state switching.

[0061] In the present disclosure, it is understood that channel quality may also be referred to as radio link quality or beam quality, and that these may be used interchangeably.

[0062] FIG. 2 illustrates a signaling chart illustrating a communication process (200) according to some exemplary embodiments of the present disclosure. The process (200) may involve a UE (201) and a base station (202). Referring to FIG. 1, the UE (201) may be implemented as a UE (104), and the base station (202) may be implemented as a network entity (102). It will be understood that the process (200) may be applied to other communication scenarios not described in detail.

[0063] UE(201) measures radio link quality on the BWP of the serving cell for each BWP of the serving cell, failureDetectionResourcesToAddModList A set of periodic CSI-RS resource configuration indexes by and candidateBeamRSList or candidateBeamRSListExt or candidateBeamRSSCellList A set of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes by You can receive sets and Instead of, for each BWP of the serving cell, the UE (201) can be activated by the MAC CE failureDetectionSet1 and failureDetectionSet2Each of the two sets of periodic CSI-RS resource configuration indexes by and , and for radio link quality measurements on the BWP of the serving cell, each candidateBeamRS-List and candidateBeamRS-List2 Two corresponding sets of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes by and You can receive . Set silver set Associated with, set silver set It is related to.

[0064] When the integrated TCI framework is configured for a serving cell, the UE (201) may be configured, depending on the UE's capabilities, with up to 128 common or DL ​​TCI states that can be used to determine the Rx beam for DL ​​reception by RRC signaling for the serving cell's BWP, and up to 64 UL TCI states that can be used to determine the Tx beam for UL transmission. When common TCI states are configured, the common TCI states are used by the UE to determine both the Rx beam for DL ​​reception and the Tx beam for UL transmission. The NW may additionally transmit MAC CE to the UE (201) to activate up to 8 common / DL / UL TCI states for the TRP for the serving cell's BWP, and each activated common / DL / UL TCI state is mapped to a TCI field code point included in the DCI format 1_1 / 1_2. When a TCI field code point is mapped to a DL TCI state and a UL TCI state, it is assumed that the DL TCI state is paired with the UL TCI state. The NW must additionally transmit a DCI having format 1_1 / 1_2 for indicating the TCI field code point for the UE (201) to indicate one joint TCI state or a pair of DL and UL TCI states mapped to the indicated TCI code point for DL ​​reception and UL transmission in the BWP of the serving cell.

[0065] In process (200), BS (202) transmits a DCI to UE (201) having format 1_1 / 1_2, which indicates a TCI code point for UE (201) in 210. The indicated TCI code point may be used to indicate an indicated co- or DL ​​TCI state. Specifically, the TCI code point may indicate a single co-TCI state or a pair of DL and UL TCI states mapped to the indicated TCI code point for DL ​​reception and UL transmission in the BWP of the serving cell. Each co- / DL TCI state includes a quasi-colocation (QCL) type-D RS for the UE to determine spatial domain RX filter parameters for DL ​​reception, and the RS may be a periodic CSI-RS for beam management or a periodic CSI-RS for tracking.

[0066] In process (200), the UE (201) determines that an event associated with the joint or DL ​​TCI state indicated in 220 is satisfied. In some examples, the UE (201) may determine whether the event was satisfied for a number of consecutive times within a time window. In some implementations, the UE (201) may consist of one or more of the first event, second event, third event, and fourth event.

[0067] In the present disclosure, the indicated common or DL ​​TCI state may be expressed as the current common / DL TCI state, for example, it refers to the current TCI state applied by the UE (201) and BS (202) to the BWP of the serving cell.

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

[0069] attribute value DCI payload size 1-0 Number of control OFDM symbols 2 Assembly Level (Control Channel Element (CCE)) 4 Ratio of virtual PDCCH resource factor (RE) energy to average SSS RE energy 0 or 4 dB Ratio of virtual PDCCH DMRS energy to average second-order synchronization signal (SSS) RE energy 0 or 4 dB Bandwidth (physical resource blocks (PRBs)) 24 Subcarrier Spacing (SCS) (kHz) SCS of active DL BWP DMRS Precorder Particle Size REG Bundle Size Resource Element Group (REG) Bundle Size 6 Circular prefix (CP) length normal Mapping from REG to CCE dispersion

[0070] In some implementations, the UE (201) may determine whether the trigger condition for the first event (Event 1) is satisfied. In some exemplary embodiments, the UE (201) may need to monitor the quality of the indicated cavity or DL ​​TCI status. With such an event, the UE (201) may notify the BS (202) in a timely manner that the current indicated TCI status is not sufficiently good before triggering a beam failure event.

[0071] In some examples, the UE (201) may evaluate (e.g., compare) the quality of the indicated joint or DL ​​TCI state against a first threshold Q1. If the UE (201) detects that the quality of the indicated joint or DL ​​TCI state is less than Q1 for N1 consecutive times (which can be controlled by a counter in the MAC) within a time window W1 (which can be controlled by a timer in the MAC), it will send a beam report (see 230) to the BS (202) to indicate this event. For example, a dedicated SR may be configured for a beam report for a first event (Event 1). In some examples, after receiving the beam report, i.e., the dedicated SR, the 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.

[0072] A second event may indicate that the quality of one of the active co- or DL ​​TCI states exceeds a second threshold or is not less than a second threshold. In some implementations, the second event may be represented as Event 2, and the second threshold may be represented as Q2. In some examples, Q2 may be BLER derived based on specific virtual PDCCH transmission parameters, or L1-RSRP configured by RRC signaling.

[0073] In some implementations, the UE (201) can determine whether the trigger condition for a second event (event 2) is satisfied. In some exemplary embodiments, the UE (201) can monitor (e.g., measure) the quality of all active co / DL TCI states other than the indicated co / DL TCI state. With this event, the UE (201) can report a better candidate TCI state, which is sufficiently good, to the BS (202) in a timely manner for potential TCI state switching.

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

[0075] A third event may indicate that the difference between the quality of one of the active co- or DL ​​TCI states, for example, the best active co- or DL ​​TCI state, and the quality of the indicated co- / DL TCI state exceeds a third threshold or is not less than a third threshold. In some implementations, the third event may be represented as Event 3, and the third threshold may be represented as Q3. In some examples, Q3 may be BLER derived based on specific virtual PDCCH transmission parameters, or L1-RSRP configured by RRC signaling.

[0076] In some implementations, the UE (201) can determine whether the trigger condition for a third event (event 3) is satisfied. In some exemplary embodiments, the UE (201) can monitor (e.g., measure) the quality of all active co / DL TCI states, including the indicated co / DL TCI state. With this event, the UE (201) can timely beam to the BS (202) a better candidate TCI state, which is better than the currently indicated co / DL TCI state, for potential TCI state switching.

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

[0078] A fourth event may indicate that the quality of the indicated joint or DL ​​TCI state is less than or not greater than the fourth threshold, and that the quality of one of the activated joint or DL ​​TCI states exceeds or is not less than the fifth threshold. In some implementations, the fourth event may be represented as Event 4, the fourth threshold may be represented as Q4, and the fifth threshold may be represented as Q5. In some examples, Q4 and / or Q5 may be L1-RSRP configured by BLER derived based on specific virtual PDCCH transmission parameters, or RRC signaling.

[0079] In some implementations, the UE (201) can determine whether the trigger condition for the fourth event (event 4) is satisfied. In some exemplary embodiments, the fourth event may be considered as a combination of the first and second events, e.g., Q4=Q1 and Q5=Q2. With this event, the UE (201) can timely notify the BS (202) that the currently displayed TCI state is not sufficiently good before triggering the beam failure event, and that a better candidate TCI state is identified, e.g., for high-speed TCI state switching before triggering the beam failure event.

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

[0081] In process (200), the UE (201) transmits a beam report from 230 to the BS (202). In some implementations, the beam report may be triggered by the occurrence of at least one of the first event, the second event, the third event, and the fourth event. In some exemplary embodiments, the beam report may be considered as an event-triggered beam report or an event-triggered beam report.

[0082] In some implementations, the beam report may indicate the trigger condition of at least one event being satisfied. In some implementations, if the satisfied event includes one or more of a second event, a third event, or a fourth event, the beam report may additionally indicate one active joint or DL ​​TCI state associated with the satisfied event that is different from the indicated joint or DL ​​TCI state.

[0083] In some implementations, when the trigger condition of the first event is satisfied, the beam report may be transmitted via a dedicated SR or MAC CE. For example, the MAC CE may include a dedicated field that may contain at least one bit. For example, the MAC CE may include a specific field that includes the event ID of the first event.

[0084] In some other implementations, if one or more trigger conditions of the second, third, or fourth event are met, the beam report may be transmitted via MAC CE.

[0085] In some exemplary embodiments, the MAC CE may display one active cavity or DL ​​TCI state associated with the satisfied event. In some examples, one of the second, third, or fourth event may be configured for the UE (201) in the BWP of the serving cell. For example, one active cavity or DL ​​TCI state displayed by the MAC CE may be the best cavity / DL TCI state determined by the UE (201), for example, having the highest channel quality. In some examples, one active cavity or DL ​​TCI state may be explicitly or implicitly displayed by the MAC CE.

[0086] In some embodiments, one active cavity or DL ​​TCI state indicated by the MAC CE may be referred to as a reported cavity / DL TCI state, a proposed cavity / DL TCI state, a selected cavity / DL TCI state, or a recommended cavity / DL TCI state, and the present disclosure does not limit such embodiments. 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 for the NZP CSI-RS associated with the reported cavity / DL TCI state.

[0087] In some examples, the MAC CE may include a bitmap comprising a plurality of bits corresponding to a plurality of activated common or DL ​​TCI states. FIG. 3a illustrates an exemplary schematic diagram of a MAC CE (310) comprising a bitmap for displaying an activated common or TCI state according to some exemplary embodiments of the present disclosure. As illustrated in FIG. 3a, the bitmap (312) may include T7 through T0 corresponding to eight activated common or TCI states. For example, one of T7 through T0 may be a first value and the other of T7 through T0 may be a second value, in which case the activated common or TCI state corresponding to the first value may be displayed as satisfying, for example, a satisfied event. For example, the first value may be 1 and the second value may be 0.

[0088] In some examples, the MAC CE may include an NZP CSI-RS resource ID. Since each co-working / DL TCI state includes a QCL Type-D RS such as the NZP CSI-RS, the NZP CSI-RS resource ID may be included in the MAC CE to indicate the corresponding active co-working / DL TCI state. FIG. 3b illustrates an exemplary schematic diagram of a MAC CE (320) indicating an NZP CSI-RS resource ID associated with an active co-working or TCI state according to some exemplary embodiments of the present disclosure. As illustrated in FIG. 3b, the field (322) may include an NZP CSI-RS resource ID corresponding to the active co-working / DL TCI state.

[0089] In some examples, the MAC CE may include an indication of a TCI code point mapped to an activated joint or DL ​​TCI state. FIG. 3c illustrates an exemplary schematic diagram of a MAC CE (330) including a TCI code point mapped to an activated joint or TCI state according to some exemplary embodiments of the present disclosure. As illustrated in FIG. 3c, the field (332) may include a TCI code point i. For example, the field (332) may be 3 bits. For example, the field (332) may indicate an activated joint / DL TCI state mapped to a TCI code point i.

[0090] In some examples, the MAC CE may include an identifier or identity (ID) of an activated or DL ​​TCI state. FIG. 3d illustrates an exemplary schematic diagram of a MAC CE (340) including an ID of an activated co- or TCI state according to some exemplary embodiments of the present disclosure. As illustrated in FIG. 3d, the field (342) may include a co- or DL ​​TCI state ID associated with one activated co- / DL TCI state.

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

[0092] In some examples, MAC CEs corresponding to different events may be associated with different LCIDs. For example, different LCIDs may be configured for MAC CEs for different events.

[0093] In some other examples, a field may include multiple subfields corresponding to multiple events. For example, a single event field may be configured for multiple events, such as three events, namely the second event, the third event, and the fourth event. For example, subfields at different locations within the field may correspond to different events. In this case, the subfield having the single event field may indicate the corresponding event, while the other subfields may be set to predefined values ​​(e.g., all 0) or void.

[0094] FIGS. 4a–4c illustrate some examples of MAC CEs including event IDs. It should be understood that the examples illustrated in FIGS. 4a–4c are for illustrative purposes only and are not limited in any way. For example, a MAC CE may be determined based on the MAC CE of FIGS. 3b / 3c / 3c, which has an event field having three subfields, one of which is associated with an event.

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

[0096] In some other implementations, if there are no available UL resources for MAC CE transmission, the UE (201) may additionally transmit a regular SR or a dedicated SR to request UL resources for transmitting a beam report, for example, the regular SR or dedicated SR for the beam report may be used to request transmission resources for MAC CE. In some examples, different SRs may be configured with different priorities, and the transmission of the regular SR or dedicated SR for the beam report may be made by taking the priorities into account. For example, the priority of the dedicated SR for the beam report may be higher than the priority of the regular SR, and higher than the priority of the SR for the beam failure report (BFR). In some examples, the BS (202) may transmit a first DCI that schedules a PUSCH transmission capable of carrying MAC CE in response to the dedicated SR or regular SR for the beam report from the UE (201), and thus, the UE (201) may transmit the MAC CE based on the first DCI.

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

[0098] In some examples, if the first event, the second event, and the fourth event are satisfied, the fourth event may be reported. For example, MAC CE may indicate the fourth event and the associated activated co / DL TCI status.

[0099] Referring again to FIG. 2, in addition to or alternatively, BS (202) can determine whether to perform TCI state switching for UE (201) based on beam reporting at 240.

[0100] In some implementations, the beam report may indicate that the first event is satisfied. In this case, there is no reported co / DL TCI state for potential switching included in the beam report, and BS (202) may decide, for example, on its own whether to switch to another TCI state. That is, it is up to BS (202) to decide whether to switch to another TCI state.

[0101] In some implementations, the beam report may indicate that a second event is satisfied. In this case, the reported common / DL TCI status is included in the beam report, but the second event does not take into account the channel quality of the indicated common / DL TCI status (i.e., the current common / DL TCI status). For example, the current common / DL TCI status may be sufficiently good for data transmission. Thus, the UE (201) may follow instructions from the BS (202), as in legacy, for example.

[0102] In some implementations, the beam report may indicate that a third or fourth event has been satisfied. In this case, the reported co / DL TCI status is included in the beam report and can be used for potential switching.

[0103] In some exemplary embodiments, the 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, the UE (201) and BS (202) may switch to a reported joint / DL TCI state after a certain point in time, for example, automatically.

[0104] In some examples, the UE (201) may schedule a PUSCH transmission having the same Hybrid Auto Repeat Request (HARQ) process number as for the transmission of the first PUSCH carrying a MAC CE, and apply the reported Co / DL TCI status 28 symbols after the last symbol of the PDCCH reception having a third DCI having a toggled new Data Indicator (NDI) field value. FIG. 5a illustrates an exemplary schematic diagram of TCI status switching (510) according to some exemplary embodiments of the present disclosure. As illustrated in FIG. 5a, beam reporting may be transmitted by a MAC CE (512) indicating a third or fourth event and the reported Co / DL TCI status. Additionally, a PUSCH transmission having the same HARQ process number as for the transmission of the first PUSCH carrying a MAC CE may be scheduled, and a DCI (514) having a toggled NDI field value may be received. Next, the reported joint / DL TCI status can be applied 28 symbols after the last symbol of the PDCCH carrying the DCI (514).

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

[0106] As another example, if the reported joint / DL TCI state is an active DL TCI state, the active DL TCI state may be applied. Additionally, an additional UL TCI state may be determined. In some cases, there may exist a paired UL TCI state mapped to the same TCI code point having the active DL TCI state (i.e., the reported DL TCI state), and then the UE (201) may apply the active DL TCI state and the paired UL TCI state. In some other cases, there may not exist a paired UL TCI state mapped to the same TCI code point as the active DL TCI state (i.e., the reported DL TCI state), and then the current UL TCI state may continue to be applied; that is, the UE (201) may apply the active DL TCI state and maintain the current UL TCI state.

[0107] In this way, the reported joint or DL ​​TCI status can be applied, and an additional DCI having format 1_1 / 1_2 indicating the reported joint or DL ​​TCI status may not be required, and thus, signaling overhead can be reduced and TCI status switching can be more efficient.

[0108] In some exemplary embodiments, the reported joint / DL TCI status may not be applied automatically. In some exemplary embodiments, the UE (201) may expect to receive a DCI having format 1_1 / 1_2 that indicates a TCI code point mapped to the reported joint / DL TCI status, after scheduling a PUSCH transmission having the same HARQ process number as for the transmission of the first PUSCH carrying MAC CE, for example, and receiving a DCI format having a toggled NDI field value.

[0109] In some examples, after receiving a beam report (i.e., a MAC CE containing the reported joint / DL TCI status), the BS (202) may transmit a second DCI having format 1_1 / 1_2 that indicates a different indicated joint / DL TCI status. For example, the different indicated joint / DL TCI status may be different from the current joint / DL TCI status, and the different indicated joint / DL TCI status may be a new TCI status. For example, the second DCI may indicate to the UE (201) that a TCI status switching should be performed.

[0110] In some examples, when the UE (201) schedules a PUSCH transmission having the same HARQ process number as for the transmission of the first PUSCH carrying the MAC CE and receives a second DCI having format 1_1 / 1_2 indicating a new TCI state before receiving a DCI format having a toggled NDI field value, the UE (201) can apply the new TCI state. FIG. 5b illustrates an exemplary schematic diagram of TCI state switching (520) according to some exemplary embodiments of the present disclosure. As illustrated in FIG. 5b, a beam report indicating a third or fourth event and a reported common / DL TCI state may be transmitted by the MAC CE (522). Additionally, a DCI (524) may be received, which indicates a new TCI state. Then, the new common / DL TCI state may be applied after a beam application time from the last symbol of the physical uplink control channel (PUCCH) / PUSCH (526).

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

[0112] According to some embodiments with reference to FIGS. 2-5b, an event-triggered beam report can be transmitted to the BS (202) by the UE (201), and thus the beam report can be used by the BS (202) for consideration, for example, for potential TCI state switching. Thus, signaling overhead can be saved and TCI state switching can be more efficient.

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

[0114] In some other cases, the present disclosure may also be applied to multi-TRP scenarios. For example, the embodiments discussed above can be simply extended to multi-TRP scenarios. For example, a resource pool for measurement may be determined per TRP, and events may be triggered per TRP.

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

[0116] The two indicated co- / DL TCI states for the S-DCI MTRP are determined as the first and second indicated co- / DL TCI states. For the M-DCI MTRP, the first and second indicated co- / DL TCI states are the co- / DL TCI state specific to the coresetPoolIndex value 0 and the co- / DL TCI state specific to the coresetPoolIndex value 1, respectively. That is, the current TCI state for the first TRP is the first indicated co- / DL TCI state, and the current TCI state for the second TRP is the second indicated co- / DL TCI state.

[0117] The UE (201) can evaluate each of the events for each TRP level. In some examples, an event for the first TRP may be satisfied and / or another event for the second TRP may be satisfied; additionally, the UE (201) may transmit an SR or MAC CE that may include beam reports for the first TRP and / or the second TRP. For example, the SR or MAC CE may include a field for indicating the first TRP and / or the second TRP.

[0118] For example, if the UE (201) identifies that any one of the co / DL TCI states in the first set of measurement resources is offset better than the first indicated TCI state, an event 3 corresponding to the first TRP will be triggered. If the UE (201) identifies that the second indicated TCI state is worse than the threshold and identifies that at least one TCI state in the second set of measurement resources is better than the threshold, an event 4 corresponding to the second TRP will be triggered.

[0119] In this way, the event-triggered beam report can be transmitted to the BS (202), and the BS (202) can recognize the channel quality associated with at least the indicated common / DL TCI state. In some examples, the UE (201) and the BS (202) can apply a good TCI state, such as the reported common / DL TCI state in the beam report, if available, and thus signaling overhead can be reduced and TCI state switching can be more efficient. In some other examples, the BS (202) can consider the beam report and decide whether to perform TCI state switching for the UE (201), and thus the decision made by the BS (202) will be more accurate.

[0120] FIG. 6 illustrates an example of a device (600) suitable for implementing embodiments of the present disclosure. The device (600) may be an example of a base station or UE described herein. The device (600) may support wireless communication with a UE (201), a base station (202), or any combination thereof. The device (600) may include components for bidirectional communication, such as a processor (602), memory (604), a transceiver (606), and optionally, an I / O controller (608), for transmitting and receiving communications. These components may communicate electronically through one or more interfaces (e.g., a bus) or be coupled in other ways (e.g., kinetically, phonologically, functionally, electronically, electrically).

[0121] A processor (602), memory (604), transceiver (606), or various combinations thereof or various components thereof may be examples of means for carrying out various aspects of the disclosure described herein. For example, a processor (602), memory (604), transceiver (606), or various combinations thereof or components thereof may support a method for carrying out one or more of the operations described herein.

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

[0123] For example, the processor (602) may support wireless communication in the device (600) according to the examples disclosed herein. The processor (602) may be operably configured to support means for the operations discussed above.

[0124] The processor (602) may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor (602) may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor (602). The processor (602) may be configured to execute computer-readable instructions stored in memory (e.g., memory (604)) to enable the device (600) to perform various functions of the present disclosure.

[0125] Memory (604) may include random access memory (RAM) and read-only memory (ROM). Memory (604) may store computer-readable, computer-executable code containing instructions that enable the device (600) to perform the various functions described herein when executed by the processor (602). The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. In some implementations, the code may not be directly executable by the processor (602), but may enable the computer to perform the functions described herein (e.g., during compilation and execution). In some implementations, memory (604) may include a basic I / O system (BIOS) capable of controlling basic hardware or software operations, such as interactions with devices, among other things, peripheral components or others.

[0126] The I / O controller (608) can manage input and output signals for the device (600). The I / O controller (608) can also manage peripherals that are not integrated into the device (600). In some implementations, the I / O controller (608) may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller (608) may use an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, the I / O controller (608) may be implemented as part of a processor such as the processor (602). In some implementations, a user may interact with the device (600) through the I / O controller (608) or through a hardware component controlled by the I / O controller (608).

[0127] In some implementations, the device (600) may include a single antenna (610). However, in some other implementations, the device (600) may have more than one antenna (610) (i.e., multiple antennas) comprising multiple antenna panels or antenna arrays, which can transmit or receive multiple wireless transmissions simultaneously. The transceiver (606) may communicate bidirectionally through one or more antennas (610), wired links, or wireless links as described herein. For example, the transceiver (606) may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver (606) may also include a modem for modulating packets, providing the modulated packets to one or more antennas (610) for transmission, and demodulating packets received from one or more antennas (610). The transceiver (606) may include one or more transmission chains, one or more reception chains, or a combination thereof.

[0128] A transmission chain may be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator to modulate data onto a carrier signal to prepare the signal for transmission over a wireless medium. The 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 into air or a wireless medium.

[0129] A receiving chain may be configured to receive signals (e.g., control information, data, packets) through a wireless medium. For example, a receiving chain may include one or more antennas (610) for receiving signals through air or a wireless medium. A receiving chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. A receiving 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 the transmission of the signal. A receiving chain may include at least one decoder for receiving the transmitted data by decoding and processing the demodulated signal.

[0130] FIG. 7 illustrates an example of a processor (700) suitable for implementing some embodiments of the present disclosure. The processor (700) may be an example of a processor configured to perform various operations according to the examples described herein. The processor (700) may include a controller (702) configured to perform various operations according to the examples described herein. The processor (700) may optionally include at least one memory (704), such as an L1 / L2 / L3 cache. Additionally or alternatively, the processor (700) may optionally include one or more arithmetic logic units (ALUs) (706). One or more of these components may communicate electronically through one or more interfaces (e.g., buses) or otherwise be coupled (e.g., kinetically, kinetically, functionally, electronically, electrically).

[0131] The processor (700) may be a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or contained in the processor chipset (e.g., processor (700))), 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.).

[0132] A controller (702) may be configured to manage and coordinate various operations of the processor (700) (e.g., signaling, receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) so that the processor (700) may support various operations according to the examples described herein. For example, the controller (702) may operate as a control unit of the processor (700) and generate control signals that manage the operations of various components of the processor (700). These control signals include the activation or deactivation of function units, the selection of data paths, the initiation of memory access, and the timing adjustment of operations.

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

[0134] Memory (704) may include one or more caches (e.g., memory local to or contained in the processor (700)) or other memory, e.g., RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory (704) may be located within or on the processor chipset (e.g., local to the processor (700)). In some other implementations, memory (704) may be located outside the processor chipset (e.g., remote from the processor (700)).

[0135] Memory (704) may store computer-readable, computer-executable code containing instructions that, when executed by the processor (700), cause the processor (700) to perform the various functions described herein. The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. A controller (702) and / or a processor (700) may be configured to execute computer-readable instructions stored in memory (704) to cause the processor (700) to perform the various functions. For example, the processor (700) and / or the controller (702) may be coupled to or with memory (704), and the processor (700), the controller (702), and the memory (704) may be configured to perform the various functions described herein. In some examples, the processor (700) may include multiple processors, and the memory (704) may include multiple memories. One or more of the multiple processors may be combined with one or more of the multiple memories, and they may be configured to perform the various functions of this specification individually or collectively.

[0136] One or more ALUs (706) may be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs (706) may be located in or on a processor chipset (e.g., processor (700)). In some other implementations, one or more ALUs (706) may be located outside the processor chipset (e.g., processor (700)). One or more ALUs (706) may perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs (706) may receive input operands and an operation code that determines the operation to be executed. One or more ALUs (706) may be composed of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs (706) may support logical operations such as AND, OR, exclusive OR (XOR), negative OR (NOR), and negative AND (NAND), thereby enabling one or more ALUs (706) to handle conditional operations, comparisons, and bitwise operations.

[0137] Additionally, the processor (700) may support wireless communication according to the examples disclosed herein. The processor (700) may be configured to support means for operations described in some embodiments of the present disclosure or may be operable to support such means.

[0138] FIG. 8 illustrates a flowchart of a method (800) performed by a UE according to embodiments of the present disclosure. Operations of the method (800) may be implemented by a device or its components as described herein. For example, operations of the method (800) may be performed by the UE (201) in FIG. 2. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use special-purpose hardware to perform embodiments of the described functions.

[0139] In 810, the method may include a step of determining that an event associated with an indicated joint or DL ​​TCI state is satisfied. The operations of 810 may be performed according to the examples described herein. In some implementations, aspects of the operations of 810 may be performed by the UE (201) as described with reference to FIG. 2.

[0140] In 820, the method may include the step of transmitting a beam report to a base station indicating an event, or one of an active joint or DL ​​TCI state different from the indicated joint or DL ​​TCI state, upon determining that a trigger condition associated with the event is satisfied. The operations of 820 may be performed according to the examples described herein. In some implementations, aspects of the operations of 820 may be performed by the UE (201) as described with reference to FIG. 2.

[0141] FIG. 9 illustrates a flowchart of a method (900) performed by a base station according to embodiments of the present disclosure. Operations of the method (900) may be implemented by a device or its components as described herein. For example, operations of the method (900) may be performed by the BS (202) in FIG. 2. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use special-purpose hardware to perform embodiments of the described functions.

[0142] In 910, the method may include the step of transmitting downlink control information (DCI) indicating the indicated joint or DL ​​TCI status to the UE. The operations of 910 may be performed according to the examples described herein. In some implementations, aspects of the operations of 910 may be performed by BS (202) as described with reference to FIG. 2.

[0143] In 920, the method may include the step of receiving from the UE an event associated with a indicated joint or DL ​​TCI state, or a beam report indicating one of an active joint or DL ​​TCI state different from the indicated joint or DL ​​TCI state. The operations of 920 may be performed according to the examples described herein. In some implementations, aspects of the operations of 920 may be performed by BS (202) as described with reference to FIG. 2.

[0144] It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or modified in other ways, and other implementations are possible. Furthermore, aspects from two or more of the methods may be combined.

[0145] The various exemplary blocks and components described in connection with the disclosure of this specification may be implemented or performed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this specification. A 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 by 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).

[0146] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or code forms on a computer-readable medium or transmitted therethrough. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be located in various physical locations, including distributed so that parts of the functions are implemented in different physical locations.

[0147] Computer-readable media include both non-transient computer storage media and communication media, which include any medium that facilitates the transfer of computer programs from one place to another. Non-transient storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transient computer-readable media may include RAM, ROM, electrically erasable and programmable ROM (EEPROM), flash memory, compact disc (CD)-ROM or other optical disc storage, magnetic disc storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store desired means of program code 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.

[0148] As used herein, including in the claims, the article "a" preceding an element is not restricted and is understood to mean "at least one" of the elements or "one or more" of the elements. The terms article ("a"), "at least one," "one or more," and "at least one of one or more" may be interchangeable. When used in this specification, including in claims, the word “or” used in a list of items (e.g., a list of items accompanied by phrases such as “at least one of,” or “one or more of,” or “one or both of) indicates a comprehensive list; thus, 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, B, and C). Furthermore, when used in this specification, the phrase “based on” should not be interpreted as a reference to a closed set of conditions. For example, an exemplary 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, when used in this specification, the phrase “based on” should be interpreted in the same way as the phrase “at least partially based.” Furthermore, when used in this specification, including in claims, the “set” may include one or more elements.

[0149] This description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure is not limited to the examples and designs described herein, but should be given the broadest scope conforming to the principles and novel features disclosed herein.

Claims

Claim 1 A user device (UE) comprising at least one memory; and at least one processor coupled to said at least one memory, wherein said at least one processor is configured to cause said UE to: determine that an event associated with a indicated common or downlink (DL) transmission configuration indicator (TCI) state is satisfied; and, upon determining that a trigger condition associated with said event is satisfied, to cause said event, or one of an active common or DL ​​TCI state different from said indicated common or DL ​​TCI state, to transmit a beam report to a base station. Claim 2 In claim 1, the trigger condition comprises one of: the event being satisfied, or the event being satisfied for a plurality of consecutive times within a time window—the number of the plurality of consecutive times being predefined or preconfigured—a UE. Claim 3 In claim 1, the event comprises: 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 activated 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 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 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 activated joint or DL ​​TCI states exceeds or is not less than a fifth threshold. Claim 4 In claim 1, at least one threshold value 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 virtual physical downlink control channel (PDCCH) transmission parameters, or a layer 1 reference signal received power (L1-RSRP) configured by radio resource control (RRC) signaling, UE. Claim 5 In paragraph 3, the above event includes the above first event, and the beam report is included in the scheduling request (SR), UE. Claim 6 In paragraph 3, the event comprises one of the second event, the third event, or the fourth event, and the beam report is included in a Media Access Control (MAC) control element (CE) indicating one of the activated joint or DL ​​TCI states, UE. Claim 7 In paragraph 6, the MAC CE includes a bitmap, and a bit in the bitmap corresponding to one of the activated joint or DL ​​TCI states for the bandwidth portion (BWP) of the UE’s serving cell is set to a specific value, UE. Claim 8 In paragraph 6, the MAC CE comprises: an identifier (ID) of one of the activated common or DL ​​TCI states, a non-zero power (NZP) channel state information (CSI) reference signal (RS) resource ID associated with one of the activated common or DL ​​TCI states, or an indication of a TCI code point mapped to one of the activated common or DL ​​TCI states, UE. Claim 9 In paragraph 6, different events are associated with different logical channel identities (LCIDs), and the MAC CE further includes the LCID associated with the event, UE. Claim 10 In paragraph 6, different events are associated with the same LCID, and the MAC CE includes the LCID carried at a specific location associated with the event, UE. Claim 11 In claim 6, the at least one processor is further configured to cause the UE to: transmit a dedicated SR to the base station for requesting a transmission resource of the MAC CE; and receive from the base station a first downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) transmission carrying the MAC CE. Claim 12 In paragraph 3, the event comprises the first event or the second event, and the at least one processor is configured to cause the UE to: receive a second DCI indicating an additional indicated common or DL ​​TCI state from the base station—the additional indicated common or DL ​​TCI state being the same or different from the activated common or DL ​​TCI state in the beam report—; and to apply the additional indicated common or DL ​​TCI state for additional transmission or reception, the UE. Claim 13 In paragraph 6, the event comprises the third event or the fourth event, and the at least one processor is configured to cause the UE to: apply the activated joint or DL ​​TCI state after a specific point in time, wherein the specific point in time is 28 symbols from the last symbol of a PDCCH reception having a third DCI having a toggled new data indicator (NDI) field value, scheduling a PUSCH transmission having the same Hybrid Auto Repeat Request (HARQ) process number as for the transmission of the first PUSCH carrying the MAC CE. Claim 14 In paragraph 13, the at least one processor is configured to cause the UE to: apply the UL TCI state for additional transmission upon determining that an uplink (UL) TCI state paired with the activated DL TCI state exists; or continue to apply the current UL TCI state for additional transmission upon determining that a UL TCI state paired with the activated DL TCI state does not exist. Claim 15 In claim 6, the at least one processor is configured to cause the UE to: receive from the base station a second DCI indicating an additional indicated common or DL ​​TCI status prior to the third DCI, wherein the third DCI schedules a PUSCH transmission having the same HARQ process number as for the transmission of the first PUSCH carrying the MAC CE and has a toggled NDI field value; and to apply the additional indicated common or DL ​​TCI status for additional transmission or reception, the UE. Claim 16 A base station comprising: at least one memory; and at least one processor coupled to said at least one memory, wherein the at least one processor is configured to cause said base station to: transmit downlink control information (DCI) indicating a indicated common or downlink (DL) transmission configuration indicator (TCI) status to a user equipment (UE); and to receive from said UE an event associated with said indicated common or DL ​​TCI status, or a beam report indicating one of an active common or DL ​​TCI status different from said indicated common or DL ​​TCI status. Claim 17 In paragraph 16, the above event comprises: 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 activated 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 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 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 activated joint or DL ​​TCI states exceeds or is not less than a fifth threshold. Claim 18 In paragraph 16, at least one threshold value associated with the event is at least one block error rate (BLER), and said at least one BLER is: a base station determined based on one or more specific virtual physical downlink control channel (PDCCH) transmission parameters, or a layer 1 reference signal received power (L1-RSRP) configured by radio resource control (RRC) signaling. Claim 19 A method performed by a user equipment (UE), comprising: determining that an event associated with a indicated common or downlink (DL) transmission configuration indicator (TCI) state is satisfied; and transmitting a beam report to a base station indicating one of the activated common or DL ​​TCI states that is different from the event or the indicated common or DL ​​TCI state, in accordance with the determination that a trigger condition associated with the event is satisfied. Claim 20 A processor for wireless communication comprising at least one controller coupled with at least one memory, wherein the at least one controller is configured to cause the processor to: determine that an event associated with a indicated common or downlink (DL) transmission configuration indicator (TCI) state is satisfied; and, upon determining that a trigger condition associated with the event is satisfied, to cause the processor to transmit to a base station a beam report indicating the event, or one of an active common or DL ​​TCI state different from the indicated common or DL ​​TCI state.

Images