Method and apparatus for recovery for user equipment (UE) initiated beam management (UEIBM)

By implementing criteria-based operations for beam recovery in UEIBM, the solution addresses beam failure and latency issues in 5G New Radio, enhancing communication reliability and efficiency.

WO2026074380A1PCT designated stage Publication Date: 2026-04-09NOKIA TECHNOLOGIES OY
View PDF 4 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-09-18
Publication Date
2026-04-09

AI Technical Summary

Technical Problem

Existing beam management techniques in 5G New Radio face challenges in maintaining reliable communication due to inefficiencies in handling beam failures and associated latency issues, particularly in user equipment (UE) initiated beam management (UEIBM) processes.

Method used

The implementation of criteria-based operations at the UE and network node for managing beam recovery, including resource release, random access procedures, and CSI reporting, to address beam failure and reduce latency.

Benefits of technology

The proposed solution enhances UEIBM performance by reducing latency and improving communication reliability through efficient beam management recovery mechanisms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2025059388_09042026_PF_FP_ABST
    Figure IB2025059388_09042026_PF_FP_ABST
Patent Text Reader

Abstract

Methods, apparatuses, and systems provide recovery for UEIBM. In the context of a method, the method includes determining a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and performing at least one operation based at least in part on the criterion being satisfied.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR RECOVERY FOR USER EQUIPMENT (UE) INITIATED BEAM MANAGEMENT (UEIBM)RELATED APPLICATION

[0001] This application claims priority to US provisional Application No. 63 / 702952 filed October 3, 2024, which is incorporated herein by reference in its entirety.TECHNOLOGICAL FIELD

[0002] The present disclosure relates generally to techniques for user equipment (UE) initiated beam management (UEIBM) and, more particularly, to techniques for recovery for UEIBM.BACKGROUND

[0003] In 5G New Radio, beam management is used for maintaining reliable communication within a network. A user equipment (UE) may be configured to support one or more beam management procedures to improve beam selection for communications with one or more network nodes. In accordance with a beam management procedure, the UE may perform measurements to assess a quality of one or more beams used for communications with the one or more network nodes. The UE may report information pertaining to the quality of the beam(s) to a network node, which may use the reported information for beam selection.BRIEF SUMMARY

[0004] Methods, apparatuses, and computer program products are disclosed to provide for recovery for UEIBM. In this regard, the method, apparatus and system are configured to provide for one or more operations performed at a UE and / or a network node based on a criterion associated with UEIBM being satisfied, which may reduce latency and increase a performance of UEIBM at the UE.

[0005] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) configured to, with the at least one processor, cause the apparatus at least to determine a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an eventtriggered channel state information (CSI) report; and perform at least one operation based at least in part on the criterion being satisfied.

[0006] In at least one example embodiment, performing the at least one operation comprises: refraining from performing an event evaluation associated with the event triggered CSI report.

[0007] In at least one example embodiment, performing the at least one operation comprises releasing at least one resource, and wherein the at least one resource comprises at least one of the following: one or more PUCCH resources associated with the PUCCH message; one or more resources associated with event triggered CSI reporting; one or more resources associated with at least one serving cell; or one or more PUCCH resources associated with the event triggered CSI report.

[0008] In at least one embodiment, releasing the at least one resource comprises at least one of the following: determining a resource configuration associated with the at least one resource is invalid; or refraining from providing for transmission of an uplink message via the at least one resource.

[0009] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to receive a control message associated with CSI reporting, wherein the control message comprises an indication of the at least one PUCCH resource.

[0010] In at least one embodiment, performing the at least one operation comprises providing for transmission of an uplink message via at least one uplink resource in accordance with an uplink grant, wherein the uplink message comprises at least one indication associated with the event triggered CSI report based at least in part on the criterion being satisfied.

[0011] In at least one embodiment, performing the at least one operation comprises initiating a random access procedure with a network entity.

[0012] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to receive, from the network entity, a random access response indicative of an uplink grant; and provide for transmission of at least one indication to the network entity in accordance with the uplink grant, wherein the at least one indication is associated with the event triggered CSI report.

[0013] In at least one embodiment, the at least one indication comprises a medium access control (MAC) control element (CE) or an indication included in the MAC CE.

[0014] In at least one embodiment, the MAC CE is associated with at least one of the following: user equipment (UE) event triggered reporting, beam failure recovery, or UE initiated beam management reporting.

[0015] In at least one embodiment, the UE event triggered reporting is for lower-layer triggered mobility (LTM).

[0016] In at least one embodiment, the MAC CE is for indicating one or more failures associated with event triggered transmissions.

[0017] In at least one embodiment, the at the at least one indication comprises at least one of the following: an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

[0018] In at least one embodiment, the at least one indication comprises at least one of the following: an indication of a codepoint, at least one bit, or at least one bitmap.

[0019] In at least one embodiment, the at least one indication comprises the indication of the codepoint, and providing for transmission of the indication of the codepoint comprises providing for transmission of a medium access control (MAC) control element (CE) comprising a bit field, wherein the bit field includes the indication of the codepoint, and wherein the codepoint corresponds to an identifier of a reporting configuration.

[0020] In at least one embodiment, the reporting configuration is associated with at least one of the following: aperiodic CSI reporting or user equipment (UE) initiated beam management.

[0021] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to determine that a procedure associated with the criterion has been completed based at least in part on the transmission of the at least one indication or successful completion of the random access procedure.

[0022] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to, based at least in part on the procedure being completed, reset a counter associated with the criterion, or restart an event evaluation for at least one of the following: a reporting configuration associated with the event triggered CSI report or a configuration associated with the PUCCH message.

[0023] In at least one embodiment, the at least one indication comprises at least one of the following: an indication of a random access resource associated with event triggered CSI reporting or an indication of provisioning information pertaining to event triggered CSI reporting.

[0024] In at least one embodiment, the random access procedure comprises a contention based random access (CBRA) procedure.

[0025] In at least one embodiment, performing the at least one operation comprises at least one of the following: providing for transmission of an indication associated with a beam failure recovery, wherein the indication triggers a beam failure recovery procedure for a serving cell for which the criterion is satisfied; providing for transmission of an indication associated with the event triggered CSI report in accordance with an uplink grant; or providing for transmission of an indication that the criterion is satisfied.

[0026] In at least one embodiment, the criterion is associated with a user equipment (UE) initiated beam management reporting configuration, and wherein the indication indicates that at least one reporting criterion for at least one UE initiated beam management report is satisfied.

[0027] In at least one embodiment, providing for transmission of the indication comprises providing for transmission of a medium access control (MAC) control element (CE) comprising the indication.

[0028] In at least one embodiment, the criterion comprises a threshold quantity of retransmissions for the PUCCH message, and determining the criterion is satisfied comprises determining the at least one retransmission satisfies the threshold quantity of retransmissions.

[0029] In at least one embodiment, the threshold quantity of retransmissions comprises a maximum quantity of retransmissions of PUCCH messages associated with event triggered CSI reporting.

[0030] In at least one embodiment, the criterion comprises a timer associated with retransmission of the PUCCH message, and wherein determining the criterion is satisfied comprises determining an expiration of the timer.

[0031] In at least one embodiment, the criterion is associated with a user equipment (UE) initiated beam management reporting configuration, and determining the criterion is satisfied comprises determining the criterion is satisfied in accordance with the UE initiated beam management reporting configuration.

[0032] In at least one embodiment, the criterion is one of a plurality of criteria configured at the apparatus for event triggered CSI reporting, and each criterion of the plurality of criteria is associated with a respective reporting event.

[0033] In at least one embodiment, the PUCCH message is associated with at least one of the following: a scheduling request identifier configured at the apparatus for event triggered CSI reporting, a PUCCH resource identifier configured at the apparatus for event triggered CSI reporting, a PUCCH resource identifier configured at the apparatus for indication of at least one event associated with event triggered CSI reporting, or a PUCCH resource identifier configured at the apparatus for indication of event triggered CSI reporting.

[0034] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to receive a control message comprising an indication of a type of unified transmission configuration indicator state, wherein a power associated with the at least one retransmission is based at least in part on the indication.

[0035] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) configured to, with the at least one processor, cause the apparatus at least to receive at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; and perform at least one operation based at least in part on a the criterion being satisfied.

[0036] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to provide for transmission of a control message associated with CSI reporting, wherein the control message comprises an indication of at least one PUCCH resource associated with the event triggered CSI report.

[0037] In at least one embodiment, receiving the at least one indication comprises receiving an uplink message via at least one uplink resource in accordance with an uplink grant, wherein the uplink message comprises the at least one indication.

[0038] In at least one embodiment, performing the at least one operation comprises performing a random access procedure with a user equipment (UE).

[0039] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to providefor transmission of a random access response to the UE, wherein the random access response is indicative of an uplink grant; and receive the at least one indication from the UE in accordance with the uplink grant.

[0040] In at least one embodiment, the at least one indication comprises a medium access control (MAC) control element (CE) or an indication included in the MAC CE.

[0041] In at least one embodiment, the at least one indication comprises an uplink message transmitted on an uplink-shared channel (UL-SCH).

[0042] In at least one embodiment, the uplink message comprises a physical (PHY) layer message.

[0043] In at least one embodiment, the MAC CE is associated with at least one of the following: user equipment (UE) event triggered reporting, beam failure recovery, or UE initiated beam management reporting .

[0044] In at least one embodiment, the MAC CE is for indicating one or more failures associated with event triggered transmissions.

[0045] In at least one embodiment, the at least one indication comprises at least one of the following: an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

[0046] In at least one embodiment, the at least one indication comprises at least one of the following: an indication of a codepoint, at least one bit, or at least one bitmap.

[0047] In at least one embodiment, the at least one indication comprises the indication of the codepoint, and receiving the indication of the codepoint comprises receiving a medium access control (MAC) control element (CE) comprising a bit field, wherein the bit field includes the indication of the codepoint, and wherein the codepoint corresponds to an identifier of a reporting configuration.

[0048] In at least one embodiment, the reporting configuration is associated with at least one of the following: aperiodic CSI reporting or UE initiated beam management.

[0049] In at least one embodiment, the at least one indication comprises at least one of the following: an indication of a random access resource associated with event triggered CSI reporting or an indication of provisioning information pertaining to event triggered CSI reporting.

[0050] In at least one embodiment, the random access procedure comprises a contention based random access (CBRA) procedure.

[0051] In at least one embodiment, the at least one indication comprises at least one of the following: an indication associated with a beam failure recovery; or an indication associated with the event triggered CSI report.

[0052] In at least one embodiment, the at least one indication triggers a beam failure recovery procedure for a serving cell for which the criterion is satisfied.

[0053] In at least one embodiment, the criterion is associated with a UE initiated beam management reporting configuration, and the at least one indication indicates that at least one reporting criterion for at least one UE initiated beam management report is satisfied.

[0054] In at least one embodiment, receiving the at least one indication comprises receiving a medium access control (MAC) control element (CE) comprising the indication.

[0055] In at least one embodiment, the criterion comprises a threshold quantity of retransmissions for the PUCCH message.

[0056] In at least one embodiment, the threshold quantity of retransmissions comprises a maximum quantity of retransmissions of PUCCH messages associated with event triggered CSI reporting.

[0057] In at least one embodiment, the criterion is associated with a UE initiated beam management reporting configuration.

[0058] In at least one embodiment, the criterion comprises a timer associated with the retransmission of the PUCCH.

[0059] In at least one embodiment, the criterion is one of a plurality of criteria for event triggered CSI reporting, and wherein each criterion of the plurality of criteria is associated with a respective reporting event.

[0060] In at least one embodiment, the PUCCH message is associated with at least one of the following: a scheduling request identifier for event triggered CSI reporting, or a PUCCH resource identifier for event triggered CSI reporting.

[0061] In at least one embodiment, the at least one memory including computer program code is configured to, with the at least one processor, cause the apparatus at least to provide for transmission of a control message comprising an indication of a type of unified transmission configuration indicator state, wherein a power associated with the at least one retransmission is based at least in part on the indication.

[0062] In at least one example embodiment, a method is provided comprising determining a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and performing at least one operation based at least in part on the criterion being satisfied.

[0063] In at least one example embodiment, a method is provided comprising receiving at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; and performing at least one operation based at least in part on the criterion being satisfied.

[0064] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to determine a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and perform at least one operation based at least in part on the criterion being satisfied.

[0065] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to receive at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; and perform at least one operation based at least in part on the criterion being satisfied.

[0066] In at least one example embodiment, an apparatus is provided that comprises means for determining a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and performing at least one operation based at least in part on the criterion being satisfied.

[0067] In at least one example embodiment, an apparatus is provided that comprises means for receiving at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggeredchannel state information (CSI) report is satisfied; and performing at least one operation based at least in part on the criterion being satisfied.

[0068] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) configured to, with the at least one processor, cause the apparatus at least to determine a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and perform at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the at least one operation includes performing resource selection for the CBRA procedure in accordance with one or more prioritization rules.

[0069] In at least one example embodiment, performing the resource selection comprises identifying a first downlink reference signal associated with a transmission configuration indicator (TCI) state; determining a received power associated with the first downlink reference signal; and selecting, in accordance with the one or more prioritization rules, at least one downlink reference signal for the CBRA procedure based at least in part on the received power.

[0070] In at least one example embodiment, the TCI state comprises an indicated TCI state or an activated TCI state.

[0071] In at least one example embodiment, selecting the at least one downlink reference signal comprises selecting the first downlink reference signal based at least in part on the received power satisfying a threshold, or selecting a second downlink reference signal based at least in part on the received power failing to satisfy the threshold.

[0072] In at least one example embodiment, the resource selection further comprises identifying a plurality of downlink reference signals associated with a plurality of TCI states, wherein the plurality of downlink reference signals comprises at least the first downlink reference signal, and wherein the second downlink reference signal comprises one of the plurality of downlink reference signals.

[0073] In at least one example embodiment, the resource selection further comprises identifying the TCI state based at least in part on a TCI state codepoint, wherein the TCI state codepoint is indicative of a TCI state type associated with the TCI state, and whereinperforming the resource selection in accordance with the one or more prioritization rules is based at least in part on the TCI state type.

[0074] In some examples, the TCI state type comprises a first TCI state type based at last in part on the TCI state codepoint being associated with a single TCI state, and wherein the TCI state type comprises a second TCI state based at least in part on the TCI state codepoint being associated with one or two TCI states.

[0075] In at least one example embodiment, performing the at least one operation comprises initiating the CBRA procedure with a network entity.

[0076] In at least one example embodiment, performing the at least one operation comprises initiating the CBRA procedure with a network entity, wherein the resource selection is in response to initiating the CBRA procedure.

[0077] In at least one example embodiment, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus at least to provide for transmission of at least one indication to the network entity in accordance with the CBRA procedure, wherein the at least one indication is associated with the event triggered CSI report.

[0078] In at least one example embodiment, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus at least to receive, from the network entity, a random access response indicative of an uplink grant, wherein the transmission of the at least one indication is in accordance with the uplink grant.

[0079] In at least one example embodiment, the at least one indication comprises a medium access control (MAC) control element (CE) or an indication included in the MAC CE.

[0080] In at least one example embodiment, the MAC CE is associated with at least one of the following: user equipment (UE) event triggered reporting, beam failure recovery, or UE initiated beam management reporting.

[0081] In at least one example embodiment, the MAC CE is for indicating one or more failures associated with event triggered transmissions.

[0082] In at least one example embodiment, the at least one indication comprises at least one of the following: an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

[0083] In at least one example embodiment, the at least one indication comprises at least one of the following: an indication of a codepoint, at least one bit, or at least one bitmap.

[0084] In at least one example embodiment, the at least one indication comprises the indication of the codepoint, and wherein providing for transmission of the indication of the codepoint comprises providing for transmission of a medium access control (MAC) control element (CE) comprising a bit field, wherein the bit field includes the indication of the codepoint, and wherein the codepoint corresponds to an identifier of a reporting configuration.

[0085] In at least one example embodiment, the reporting configuration is associated with at least one of the following: aperiodic CSI reporting or user equipment (UE) initiated beam management.

[0086] In at least one example embodiment, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus at least to determine that a procedure associated with the criterion has been completed based at least in part on the transmission of the at least one indication or successful completion of the CBRA procedure.

[0087] In at least one example embodiment, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus at least to, based at least in part on the procedure being completed, reset a counter associated with the criterion, or restart an event evaluation for at least one of the following: a reporting configuration associated with the event triggered CSI report or a configuration associated with the PUCCH message.

[0088] In at least one example embodiment, the at least one indication comprises at least one of the following: an indication of a random access resource associated with event triggered CSI reporting or an indication of provisioning information pertaining to event triggered CSI reporting.

[0089] In at least one example embodiment, the resource selection includes selection of a synchronization signal block (SSB).

[0090] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) configured to, with the at least one processor, cause the apparatus at least to: receive at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; provide for transmission of a plurality of downlink reference signals; and perform at least one operation in accordance with a contention based random access(CBRA) procedure based at least in part on the criterion being satisfied, wherein the CBRA procedure is in accordance with at least one downlink reference signal of the plurality of downlink reference signals based at least in part on one or more prioritization rules.

[0091] In at least one example embodiment, the at least one downlink reference signal is based at least in part on a received power of a first downlink reference signal associated with a transmission configuration indicator (TCI) state.

[0092] In at least one example embodiment, the TCI state comprises an indicated TCI state or an activated TCI state.

[0093] In at least one example embodiment, in accordance with the one or more prioritization rules, the at least one downlink reference signal includes: the first downlink reference signal based at least in part on the received power satisfying a threshold, or a second downlink reference signal based at least in part on the received power failing to satisfy the threshold, wherein the second downlink reference signal comprises one of the plurality of downlink reference signals including at least the first downlink reference signal.

[0094] In at least one example embodiment, the one or more prioritization rules are based at least in part on a TCI state type associated with the TCI state.

[0095] In at least one example embodiment, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus at least to provide for transmission of second control information indicative of a TCI state codepoint corresponding to the TCI state, wherein the TCI state type comprises a first TCI state type based at last in part on the TCI state codepoint corresponding to a single TCI state, and wherein the TCI state type comprises a second TCI state based at least in part on the TCI state codepoint corresponding to one or two TCI states.

[0096] In at least one example embodiment, performing the at least one operation comprises performing the CBRA procedure with a user equipment (UE).

[0097] In at least one example embodiment, receiving the at least one indication comprises receiving the at least one indication from the UE in accordance with the CBRA procedure.

[0098] In at least one example embodiment, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus at least to provide for transmission of a random access response to the UE, wherein the random access response is indicative of an uplink grant, and wherein the reception of the at least one indication is in accordance with the uplink grant.

[0099] In at least one example embodiment, the at least one indication comprises a medium access control (MAC) control element (CE) or an indication included in the MAC CE.

[0100] In at least one example embodiment, the MAC CE is associated with at least one of the following: user equipment (UE) event triggered reporting, beam failure recovery, or UE initiated beam management reporting.

[0101] In at least one example embodiment, the MAC CE is for indicating one or more failures associated with event triggered transmissions.

[0102] In at least one example embodiment, the at least one indication comprises at least one of the following: an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

[0103] In at least one example embodiment, the at least one indication comprises at least one of the following: an indication of a codepoint, at least one bit, or at least one bitmap.

[0104] In at least one example embodiment, the at least one indication comprises the indication of the codepoint, and wherein receiving the indication of the codepoint comprises receiving a medium access control (MAC) control element (CE) comprising a bit field, wherein the bit field includes the indication of the codepoint, and wherein the codepoint corresponds to an identifier of a reporting configuration.

[0105] In at least one example embodiment, the reporting configuration is associated with at least one of the following: aperiodic CSI reporting or UE initiated beam management.

[0106] In at least one example embodiment, the at least one indication comprises at least one of the following: an indication of a random access resource associated with event triggered CSI reporting or an indication of provisioning information pertaining to event triggered CSI reporting.

[0107] In at least one embodiment, transmission of the at least one indication via a random access resource indicates that the random access resource is associated with event triggered reporting.

[0108] In at least one example embodiment, the criterion comprises a threshold quantity of retransmissions for the PUCCH message.

[0109] In at least one example embodiment, the threshold quantity of retransmissions comprises a maximum quantity of retransmissions of PUCCH messages associated with event triggered CSI reporting.

[0110] In at least one example embodiment, the criterion comprises a timer associated with retransmission of the PUCCH message.

[0111] In at least one example embodiment, the criterion is associated with a UE initiated beam management reporting configuration.

[0112] In at least one example embodiment, the criterion is one of a plurality of criteria for event triggered CSI reporting, and wherein each criterion of the plurality of criteria is associated with a respective reporting event.

[0113] In at least one example embodiment, the PUCCH message is associated with at least one of the following: a scheduling request identifier for event triggered CSI reporting, or a PUCCH resource identifier for event triggered CSI reporting.

[0114] In at least one example embodiment, a method is provided comprising determining a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and performing at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the at least one operation includes performing resource selection for the CBRA procedure in accordance with one or more prioritization rules.

[0115] In at least one example embodiment, a method is provided comprising receiving at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; providing for transmission of a plurality of downlink reference signals; and performing at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the CBRA procedure is in accordance with at least one downlink reference signal of the plurality of downlink reference signals based at least in part on one or more prioritization rules.

[0116] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to determine a criterion pertaining to at least one retransmission of a physical uplink control channel(PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and perform at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the at least one operation includes performing resource selection for the CBRA procedure in accordance with one or more prioritization rules.

[0117] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to receive at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; provide for transmission of a plurality of downlink reference signals; and perform at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the CBRA procedure is in accordance with at least one downlink reference signal of the plurality of downlink reference signals based at least in part on one or more prioritization rules.

[0118] In at least one example embodiment, an apparatus is provided that comprises means for determining a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and performing at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the at least one operation includes performing resource selection for the CBRA procedure in accordance with one or more prioritization rules.

[0119] In at least one example embodiment, an apparatus is provided that comprises means for receiving at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; providing for transmission of a plurality of downlink reference signals; and performing at least one operation in accordance with a contention based random access (CBRA) procedure based at least in part on the criterion being satisfied, wherein the CBRA procedure is in accordance with at least one downlink reference signal of the plurality of downlink reference signals based at least in part on one or more prioritization rules.

[0120] The above summary is provided merely for purposes of summarizing some example embodiments to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above-described embodiments are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. It will also be appreciated that the scope of the disclosure encompasses many potential embodiments in addition to those summarized here, some of which will be further described below.BRIEF DESCRIPTION OF THE DRAWINGS

[0121] Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0122] FIG. 1 illustrates an example of a communication network to which one or more examples disclosed herein may be applied;

[0123] FIG. 2A and FIG. 2B illustrate examples of MAC subheaders to which one or more examples disclosed herein may be applied;

[0124] FIG. 3A and FIG. 3B illustrate examples of a signaling diagram for UEIBM to which one or more examples disclosed herein may be applied;

[0125] FIG. 4 illustrates an example of a signaling diagram for conditional handover (CHO) to which one or more examples disclosed herein may be applied;

[0126] FIG. 5 illustrates an example of a signaling diagram for UEIBM to which one or more examples disclosed herein may be applied;

[0127] FIG. 6 illustrates an example flowchart of a method to which one or more examples disclosed herein may be applied;

[0128] FIG. 7 illustrates an example flowchart of a method to which one or more examples disclosed herein may be applied;

[0129] FIG. 8 illustrates an example flowchart of a method to which one or more examples disclosed herein may be applied;

[0130] FIG. 9 illustrates an example flowchart of a method to which one or more examples disclosed herein may be applied;

[0131] FIG. 10 illustrates an example block diagram of an apparatus to which one or more examples disclosed herein may be applied.DETAILED DESCRIPTION

[0132] The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms “first,” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0133] For the purposes of the present disclosure, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0134] Embodiments described may be implemented in a communication network, such as any of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication network may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0135] As used herein, the term “network device” or “network node” refers to a node in a communication network via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point(AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a nonterrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0136] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralized unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU, (e.g. server, host or node) operationally coupled to the DU, (e.g. a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In at least one embodiment, the DUs may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too. In practice, any processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0137] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0138] A term “resource”, as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g. a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and / or “reception” may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0139] FIG. 1 illustrates an example of a communication network to which examples disclosed herein may be applied. The communication network (also referred to herein as a cellular communication network or system) may comprise a network node 110 providing one or more cells, such as source cell 100, and a network node 112 providing one or more other cells, such as target cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0140] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication network. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprise physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0141] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to- device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0142] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0143] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication network. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise e.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0144] In 5G New Radio, different kinds of data transfer services are offered by the medium access control (MAC) layer. To accommodate different kinds of data transfer services, multiple types of logical channels are defined. A MAC protocol data unit (MAC PDU) may consist of one or more MAC control elements (MAC CEs) corresponding to one or more features requiring the MAC CEs. According to the third generation partnership project (3GPP) technical specification (TS) 38.321, the MAC PDU includes a subheader with a logical channel identification (LCID) value or an extended LCID (eLCID) value. In some examples, the UEs 120, 122 may be configured to transmit information pertaining to a beam management procedure to the network nodes 110, 112 via one or more MAC CEs.

[0145] FIG. 2A and FIG. 2B illustrate examples of MAC subheaders to which one or more examples disclosed herein may be applied. For example, FIG. 2A shows an example of a downlink MAC PDU and FIG. 2B shows an example of an uplink MAC PDU.

[0146] A MAC PDU is a bit string that is byte aligned (i.e., multiple of 8 bits) in length. The bit strings are represented by tables in which the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0147] A MAC SDU is a bit string that is byte aligned (i.e., multiple of 8 bits) in length. A MAC SDU is included into a MAC PDU from the first bit onward. A MAC CE is a bit string that is byte aligned (i.e., multiple of 8 bits) in length. A MAC subheader is a bit string that is byte aligned (i.e., multiple of 8 bits) in length. Each MAC subheader is placed immediately in front of the corresponding MAC SDU, MAC CE, or padding. The MAC entity shall ignore the value of the Reserved bits in downlink MAC PDUs. The MAC SDUs may have variable sizes. Referring to FIGs. 2A or 2B, the MAC PDU comprises one or more MAC subPDUs. Each MAC subPDU comprises one of the following: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; or a MAC subheader and padding.

[0148] Referring back to FIGs. 2A and 2B, the MAC CEs are placed together. DL MAC subPDU(s) with MAC CE(s) is placed before any MAC subPDU with MAC SDU and MAC subPDU with padding. UL MAC subPDU(s) with MAC CE(s) is placed after all the MAC subPDU(s) with MAC SDU and before the MAC subPDU with padding in the MAC PDU. The size of padding can be zero. A maximum of one MAC PDU can be transmitted per TB per MAC entity.

[0149] Referring back to FIG. 1 , the system may be configured to support multiple input multiple output (MIMO) operations, for example, at the UEs 120, 122 or the network nodes 110, 112. In some examples, the system may support UE event driven reporting for MIMO operations. For example, the system may support one or more features to facilitate UE- initiated / event-driven beam management for reducing overhead and / or latency. As used herein, UE-initiated / event-driven beam management refers to event-driven beam management that is initiated by a UE. In some examples, the term event-driven beam management refers to a beam management procedure that is triggered in response to one or more events. In some examples, UE-initiated / event-driven beam management may include the use of a unified transmission configuration indicator (TCI) and / or one or more CSI measurement and reporting configuration frameworks. Additionally, in some examples, UE- initiated / event-driven beam management may utilize one or more frequency ranges, such as FR2 (Frequency Range 2) or other frequency ranges that may include operational frequencies in the millimeter wave (mmWave) region (e.g., above 24 giga Hertz (GHz)). Additionally, in some examples, UE-initiated / event-driven beam management may include (or be otherwise associated with) a single transmission reception point (sTRP) with intra-cell beam management and / or inter-cell beam management. In some instances, uplink signaling (e.g.,uplink signaling content(s) and / or uplink signaling procedure(s)) for UE-initiated / event- driven beam reporting facilitates relatively fast beam switching. Additionally, in some instances, the UE-initiated / event-driven nature of uplink transmissions, uplink signaling medium(s) / container(s) may be used for (e.g., designed for) the purpose of beam reporting.

[0150] FIGs. 3A and 3B illustrate examples of a signaling diagram for UEIBM to which one or more examples disclosed herein may be applied. As illustrated in FIGs. 3A and 3B, the system may support one or more beam report transmission procedures for UE- initiated / event-driven beam reporting. For example, the UE 120 may support one or more beam report transmission procedures in accordance with a first mode, referred to herein as Mode-A. In accordance with Mode-A, transmission of an event triggered report is preceded by an uplink indication, referred to herein as a first PUCCH message. For example, the UE 120 may transmit the event triggered report to the network node 110 in a message via a physical layer signalling and the message may lack a field (e.g., a header) for indicating, to the network node 110, that the message includes the event triggered report. The network node 110 may therefore be unaware of the contents of the message and, as such, may fail to properly decode the message. Consequently, in some cases, transmitting the event triggered report without first notifying the network of the report may lead to decoding failures at the network. Accordingly, prior to transmission of the report, the UE 120 may transmit the first PUCCH message to notify the network of the event triggered report. In some examples, in response to receiving the uplink indication, the network requests the event triggered report via downlink control information (DCI) that includes an uplink grant for the event triggered report.

[0151] As shown in FIG. 3A, at 312, the UE 120 transmits the first PUCCH message with an indication of the event triggered report. At 314, in response to receiving the first PUCCH message, the network node 110 transmits a DCI requesting the event triggered report from the UE 120. In some examples, the DCI may indicate an uplink grant for transmission of the requested report. At 316, in response to receiving the uplink grant, the UE 120 provisions the event triggered report (e.g., a layer 1 (LI) report) on the provided uplink grant associated with the DCI indication. In other words, the UE 120 transmits a PUSCH message (also referred to as a PUSCH channel) indicating the event triggered report in accordance with the uplink grant. In some examples, in accordance with Mode-A, a beam report transmission procedure may support a one-bit indication in a first PUCCH message (also referred to as a PUCCH channel) to request a resource for a second uplink message (also referred to herein asan uplink channel), which may include a UE-initiated / event-driven beam report. In other words, the beam report transmission procedure may support a one-bit indication in the first PUCCH message to request a resource for a second uplink channel to carry a UE- initiated / event-driven beam report. In some such examples, a periodic PUCCH resource (e.g., with PUCCH format 0 / 1) may be configured via dedicated radio resource control (RRC) signalling.

[0152] Additionally, or alternatively, as shown in FIG. 3B, the UE 120 may support one or more beam report transmission procedures in accordance with a second mode, referred to herein as Mode-B. In accordance with Mode-B, the transmission of an event triggered report is preceded by an uplink indication. That is, prior to transmission of an event triggered report, the UE 120 may transmit a first PUCCH message to notify the network node 110 of the event triggered report. In accordance with Mode-B, event triggered reports are provided on preprovisioned uplink grants. For example, in accordance with Mode-B, the UE 120 may use a previously received periodical uplink grant to transmit the event triggered report. Accordingly, the first PUCCH message may indicate that the UE 120 intends to provide an event triggered report via an uplink grant, which has been pre-provisioned.

[0153] As shown in FIG. 3B, at 318, the UE 120 transmits a first PUCCH message with an indication of the event triggered report. After transmission of the first PUCCH message, at 320, the UE 120 transmits a PUSCH message with one or more indications of the event triggered report via a pre-provisioned uplink grant associated with the event triggered report. In some examples, in accordance with Mode-B, a beam report transmission procedure (e.g., an event triggered report configuration) may support a one-bit indication in the first PUCCH message, which the UE 120 may use to indicate, to the network node 110, a second uplink channel that the UE 120 may use to transmit a UE-initiated / event-driven beam report. In other words, the beam report transmission procedure may support a one-bit indication in the first PUCCH message to notify the network of a second uplink channel, which may carry a UE-initiated / event-driven beam report. In some such examples, a periodic PUCCH resource (e.g., with PUCCH format 0 / 1) may be configured by dedicated RRC signalling.

[0154] In some examples, the system may be configured with one or more rules for determining whether and / or how to support multi-bit indication in the first PUCCH message for Mode-A and / or Mode-B (e.g., when multiple events are configured). In some examples, the one or more beam report transmission procedures for UE-initiated / event-driven beam reporting include signalling for single component carrier scenarios.

[0155] The system may support one or more types of reference signal measurements for UE-initiated / event-driven beam reporting. In some examples, the system may support a first reference signal measurement scheme (scheme- 1) in which one or more reference signals for a current beam are quasi co-located reference signal(s) associated with an indicated transmission configuration indicator (TCI) state. As used herein, a current beam refers to a beam for with the UE is configured to use for communications with a network node. In some examples, the UE may support one or more rules for determining whether and / or how to manage a scenario in which a single reference signal (e.g., only one tracking reference signal (TRS)) is configured in the indicated TCI state. Additionally, or alternatively, the system may support a second RS measurement scheme (scheme-2) in which one or more reference signals for a current beam are SSB(s) QCLed with the QCL reference signal(s) in the indicated TCI state.

[0156] In some examples, the UE may be configured to enable one of scheme- 1 or scheme-2 based on a selection by the network. In some such examples, the network may indicate the selection via an explicit RRC parameter or in an implicit manner, such as via a rule. In some examples, the rule may specify that, if the RS(s) for a candidate beam are channel state information-reference signals (CSI-RSs), scheme- 1 is enabled; otherwise, scheme-2 is enabled. In some examples, enabling of either scheme- 1 or scheme-2 enables the same reference signal type for reference signal measurements for a current beam and a candidate beam. Additionally, in some examples, the QCL reference signal(s) are the reference signals with respect to QCL-TypeD if, for example, there are two QCL reference signals in the indicated TCI state.

[0157] In some examples, the UE may support reference signal measurements for a candidate beam for an event (e.g., Event-2). In some such examples, the reference signal(s) for candidate beam(s) may be explicitly configured. Additionally, or alternatively, in some such examples, the reference signal(s) for candidate beam(s) may be implicitly derived from the QCL reference signal(s) of activated TCI state(s). Additionally, or alternatively, in some such examples, the reference signal(s) for candidate beam(s) may be implicitly derived from QCL reference signal(s) of TCI state(s) in a configured subset of an RRC-configured TCI state list.

[0158] In some examples of UE-initiated / event-driven beam reporting, the UE may support a layer 1 -reference signal received power (Ll-RSRP) report format, which may depend on Event-2, for example, for a report instance in which N > 1 beam(s) are reported. Insome such examples, RRC signalling may be used to enable or disable reporting for a current beam. In some examples, when enabled via RRC signalling, reference signal measurements for a current beam + N beams are reported. In some such examples, the reported measurement(s) for the current beam may not be counted in the N reported beams (e.g., the current beam may not be considered as one of the N beams). In some other examples, when disabled via RRC signalling, N beams may be reported.

[0159] In some examples of a beam report transmission procedure for UE-initiated / event- driven beam reporting in accordance with Mode- A, a DCI format includes an uplink grant DCI format, and the second channel includes at least a PUSCH. In some such examples, the uplink grant DCI format at least comprises DCI format 0_l / 0_2. In some such examples, the uplink grant DCI format includes DCI format 0_3. In some examples, the UE may support one or more rules for determining how to trigger a UE-initiated beam report via an uplink grant DCI format. In some such examples, the DCI format includes a downlink grant DCI format, and the second channel includes a PUCCH. In some examples, a 1 -bit field in the downlink grant DCI format is introduced to indicate the transmission of the UE-initiated beam report. Additionally, in some examples, a PUCCH resource for a feedback transmission (e.g., a hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission) may be reused to carry both the HARQ feedback (e.g., a HARQ-ACK) and the UE-initiated beam report. In some examples, the downlink grant DCI format includes at least a DCI format 1_1 / 1_2. In some examples, the downlink grant DCI format includes DCI format 1_3.

[0160] In some examples, the UE may be configured to support a triggering event determination for Event 2. In some such examples, if within a time window (which is configurable), the quantity of Event-2 instance(s) for at least one same candidate beam is greater than or equal to a configurable number M, a UE-initiated beam report occurs. In some examples, an event instance (e.g., an Event-2 instance) for a candidate beam is determined if the measurement result (e.g., an Ll-RSRP value) for the candidate beam satisfies a threshold. For example, the event instance may be determined for a candidate beam if a value of an Ll- RSRP measurement for a candidate beam exceeds the value of an Ll-RSRP measurement for the current beam by an amount that satisfies a threshold. In some examples, the triggering event determination may be based on one or more UE capabilities. In some examples, after the Ll-RSRP value of the candidate beam becomes exceeds the Ll-RSRP value of the current beam by an amount that satisfies the threshold (e.g., becomes greater than the currentbeam by an amount equal to or greater than a threshold value), a UE-initiated beam report occurs.

[0161] Some examples of triggering events associated with UE-initiated / event-driven beam reporting include: a quality of the current beam failing to satisfy a threshold quality (e.g., becoming worse than a threshold), a quality of at least one candidate beam (e.g., an Ll- RSRP value) becoming a threshold value greater than the quality of a beam derived from the activated TCI state with the lowest (e.g., worst) quality; and a quality of at least one candidate beam (e.g., an Ll-RSRP value) becoming a threshold value greater than the quality of a beam derived from the activated TCI state with the highest (e.g., best) quality.

[0162] In some examples, an explicit reference signal configuration for one or more candidate beam measurements for an event (e.g., for Event 2) may include down- selection from one or more options. The one or more options may include a first option (Option- 1) in which the reference signal(s) for candidate beam(s) may be explicitly configured in one or more reference signal resource sets associated with a CSI reporting configuration. In some examples of Option- 1, a reference signal in a reference signal resource set may be updated via a MAC-CE.

[0163] Additionally, or alternatively, the one or more options may include a second option (Option-2) in which a list of reference signal(s) for candidate beam measurements may be configured via RRC signalling, and a subset of reference signals included in the list may be activated for candidate beam measurements via MAC-CE. In some examples of Option-2, if a list size is small, MAC-CE activation may not be used.

[0164] Additionally, or alternatively, the one or more options may include a third option (Option-3) in which a list of reference signal resource(s) for candidate beam measurements may be configured via RRC signalling, and a subset of the reference signal resource(s) included in the list may be provided for candidate beam measurement via an indicated TCI state. In some examples of Option-3, each reference signal for candidate beam measurements may be associated with a configured joint / downlink TCI state, which may be used as the indicated TCI state.

[0165] In some examples, for reference signal measurements for the current beam for an event (e.g., Event 2), the UE may be configured with one or more options for handling a scenario in which a single TRS is configured in the indicated TCI state. The options may include a first option (Option- 1) in which an additional scheme is introduced and, inaccordance with the additional scheme, a reference signal for a current beam may be a CSI- RS for beam management derived from the QCL reference signal in the indicated TCI state.

[0166] Additionally, or alternatively, the options may include a second option (Option- 2) in which the TRS may be used as the measurement reference signal of the current beam for determining Ll-RSRP values.

[0167] Additionally, or alternatively, the options may further include a third option (Option-3) in which an additional scheme is introduced and, in accordance with the additional scheme, the reference signal for a current beam is explicitly configured via RRC signalling or a MAC-CE, such as a MAC CE illustrated by and described with reference to FIGs. 2A and 2B.

[0168] Referring back to FIG. 1 , the system may be configured to support one or more random access procedures, such as a contention free random access procedure (CFRA) and / or a contention based random access procedure (CBRA). For example, the UEs 120, 122 may be configured to perform a CFRA procedure and / or a CBRA procedure as part of a conditional handover (CHO) procedure.

[0169] CHO is described in 3GPP Rel. 16, with the CHO procedure being a way to improve mobility robustness. CHO is further developed in Rel. 17 and will continue to evolve in future 3GPP releases. In the case of CHO, the RAN network may prepare multiple target cells (also referred to herein as candidate cells), where each conditional handover reconfiguration is associated with a CHO execution condition that is evaluated by the UE. The CHO execution condition refers to a measurement ID (associating a measurement object with a reporting configuration) and is configured by a source gNB. The reporting configuration defines the measurement event (A3 or A5), which triggers the CHO execution. Whenever a CHO execution condition is met, the corresponding target configuration is selected, and handover is executed towards the selected target cell.

[0170] CHO may also take place with dual connectivity, in order to further increase mobility robustness and achieve a smooth handover. In reference to this, mention is made to Primary Secondary Cells (PSCells), Primary Cells (PCells), and Secondary Cells (SCells). The following will outline features of PSCells in relation to 5G New Radio, using terminology found therein. However, it is understood that the presently described principles are not limited to such terminology and may be applied to other systems having a similar architecture. For example, in multi-radio-dual connectivity (MR-DC), a Primary Cell (PCell)may be a Long Term Evolution (LTE) cell (e.g., Evolved-Universal Terrestrial Radio Access- New Radio-dual connectivity (EN-DC)).

[0171] PSCells are a type of cell currently defined in 5G New Radio, along with Primary Cells (PCells), Secondary Cells (SCells) and Special Cells (SpCells). A PCell may be used as part of an initial access between a UE and an access network and is considered to be a main cell in a master cell group (MCG). A PSCell may be comprised as part of a secondary cell group (SCG). The SpCells and SCells may be in at least one of the MCG and the SCG.

[0172] The cells may be controlled by network nodes. There are two different types of network nodes in 5G New Radio: Master nodes (which provide a control plane connection to a core network); and Secondary Nodes (which do not have control plane connections to the core network). The Master and Secondary nodes may both provide user plane (e.g., data) connections to the core network. The Master node may control the PCell. In addition to the PCell, the Master node may control at least one PSCell, although this is not always the case. The Secondary node may control at least one PSCell.

[0173] FIG. 4 illustrates an example of a signaling diagram for conditional handover (CHO) to which one or more examples disclosed herein may be applied. In other words, the signalling procedure for CHO is shown in FIG. 4, with reference to the network schematically illustrated in Figure 1.

[0174] A UE 120 is served by the source cell 100 with gNB 110 providing access to the source cell 100. At 1, the UE 120 sends a measurement report to the serving network gNB 110 to initiate the CHO preparation of target cell 102 served by the gNB 112. At 2, the source gNB 110 sends a CHO request to the target gNB 112. At 3, target gNB 112 sends a CHO Acknowledge message to gNB 110 to acknowledge the CHO request from source cell 100 to target 102. The source cell 100 prepares the target cell 102 and sends to the UE 120 the CHO configuration, along with the CHO execution condition with RRCReconfiguration message at 4. At 5, once the CHO execution condition against target cell 102 is met, the UE 120 detaches from source gNB 110: i.e.; stops transmission / reception to / from source cell 100.

[0175] At 6, the UE 120 initiates the random access procedure towards target cell 102 by sending a PRACH Preamble message (e.g., MSG1) to the gNB 112 serving the target cell 102. gNB 112 responds at 7 by sending a RACH Response message (e.g., a random access response) back to the gNB 110 serving the source cell 100. At 8, the UE 120 sends the RRC Reconfiguration Complete message (e.g., MSG3) to the gNB 112 in the target cell 102. Once the random access procedure is completed successfully, target cell 102 notifies source cell100 about successful completion of the handover procedure by sending a Handover Success message from source gNB 110 to target gNB 112 at 9.

[0176] At 10, upon receiving the handover success indication from target gNB 112, source gNB 110 initiates data forwarding to target gNB 112 serving target cell 102. Once the data forwarding and path switch procedure is completed with the new data path from the UE 120 to the core network 116, the UE 120 will continue its data transmission / reception with the network.

[0177] In some examples, the UE 120 (or the UE 122) may be configured to support two types of random access procedures, a 4-step random access type (with MSG1) and a 2-step random access type (with MSGA). Both types of random access procedures may support contention-based random access (CBRA) and / or contention-free random access (CFRA).

[0178] In some examples, the UE 120 may select a type of random access procedure at initiation of the random access procedure. In some such examples, the UE may select the type of random access procedure based on a network configuration. For example, in some examples, when one or more CFRA resources are not configured, the UE may use a reference signal received power (RSRP) threshold to select between a 2-step random access type and a 4-step random access type. In some examples, when one or more CFRA resources for a 4- step random access type are configured, the UE may perform random access with the 4-step random access type. In some examples, when one or more CFRA resources for a 2-step random access type are configured, the UE may perform random access with 2-step random access type.

[0179] In some examples, the network may not configure CFRA resources for 4-step and 2-step random access types concurrently (e.g., at the same time). For example, the network may not configure CFRA resources for 4-step and 2-step random access types concurrently for a particular bandwidth part (BWP). In some examples, CFRA with 2-step random access type is supported (e.g., is only supported) for handover.

[0180] In some examples, MSG1 of the 4-step random access type includes a preamble transmitted on a physical random access channel (PRACH). After transmission of MSG1, the UE may monitor for a response (e.g., a random access response) from the network within a configured window. For CFRA, a dedicated preamble for the MSG1 transmission may be assigned by the network. In some examples, in response to receiving the random access response from the network, the UE may end the random access procedure. In other words, in response to receiving the random access response, the UE may determine that the randomaccess procedure is successfully completed. For CBRA, in response to receiving (e.g., upon reception of) the random access response, the UE may send a MSG3 using an uplink grant scheduled via the random access response. Additionally, the UE may monitor for contention resolution. In some examples, if contention resolution is not successful after the MSG3 transmission, or after one or more MSG3 retransmissions, the UE may retransmit MSG1 (e.g., may revert back to MSG1 transmission).

[0181] In some examples, the MSGA of the 2-step random access type includes a preamble transmitted on a PRACH and a pay load transmitted on a PUSCH. After the MSGA transmission, the UE may monitor for a response (e.g., a random access response) from the network within a configured window. For CFRA, a dedicated preamble and PUSCH resource may be configured for the MSGA transmission and, in response to receiving (e.g., upon receiving) the network response, the UE may end the random access procedure. For CBRA, if contention resolution is successful, after receiving the network response, the UE may end the random access procedure. In other words, in response to receiving the random access response, the UE may determine that the random access procedure is successfully completed. In some examples, if a fallback indication is received in MSGB, the UE may perform a MSG3 transmission using an uplink grant scheduled in the fallback indication and may monitor for contention resolution. If contention resolution is not successful after the MSG3 transmission, or after one or more MSG3 retransmissions, the UE may retransmit MSGA (e.g., may revert back to MSGA transmission).

[0182] In some examples, if the random access procedure with a 2-step random access type is not completed after a quantity of MSGA transmissions, the UE may be configured to switch to CBRA with a 4-step random access type.

[0183] The system may support lower-layer triggered mobility (LTM). In some examples, LTM is a procedure that allows a serving cell to change through L1 / L2 signaling. L1 / L2 signaling refers to signaling that supports the transmission of uplink and downlink transport channels. L1 / L2 signaling includes signaling of information that originates from both the physical layer (Layer 1) and the MAC (Layer 2). In other words, information carried via L1 / L2 signaling partly originates from the physical layer (Layer 1) and partly from MAC (Layer 2). LTM may lead to reduced latency, overhead, and interruption time during handover.

[0184] In some examples, for a random access procedure directed towards an LTM candidate cell for uplink timing advance (TA) acquisition (e.g., early uplink TA acquisition),CFRA may be triggered by a PDCCH order. The UE may send MSG1 towards the candidate cell without monitoring for a response from the candidate cell. In some examples, to support UE power ramping, the UE may perform one or more MSG1 retransmissions as indicated by the network.

[0185] In some examples, the UE may be configured to support a beam report transmission procedure for UE-initiated / event-driven beam reporting. The beam report transmission procedure may provide for operations in accordance with Mode-A and / or Mode- B. In some instances, the beam report transmission procedure may provide one or more constraints for a first PUCCH transmission. For example, the beam report transmission procedure may provide for a rule, such as a UCI multiplexing / dropping / prioritization rule, one or more conditions for the transmission of the first PUCCH, one or more rules for determining whether the PUCCH resource in the first PUCCH message can be associated with multiple CSI report configurations for UE-initiated / event-driven beam reporting from one or multiple CC(s), one or more rules for determining whether to retransmit the first PUCCH message, one or more rules for determining how to retransmit the first PUCCH message, one or more rules for determining whether to apply a timer (e.g., a prohibit-timer) or a threshold number (e.g., a maximum number) of retransmission(s) for the first PUCCH message, and / or one or more rules for determining how to apply a prohibit-timer or a threshold number (e.g., a maximum number) of retransmission(s) for the first PUCCH message.

[0186] In some examples, however, the UE may lack a mechanism for determining one or more operations (e.g., actions) to perform in response to determining that the threshold number of retransmissions for the first PUCCH message is satisfied. In other words, the UE may not be configured with one or more rules for determining one or more UE actions to perform once a maximum number of retransmissions of the first PUCCH message is reached. In some examples, the lack of such a mechanism may lead to increased latency and reduce a performance of the UE.

[0187] Various aspects of the present disclosure provide a mechanism for the UE to determine one or more operations to perform in response to determining that a criterion associated with UE-initiated event reporting is satisfied. For example, the present disclosure provides a framework for UE actions once a timer expires and / or once the maximum number of retransmissions of the first PUCCH message is reached. In accordance with at least one embodiment of the present disclosure, when the UE determines that a criterion is satisfied(e.g., where the criterion is a timer and / or a maximum number of retransmissions has been made for the first channel and the criterion is associated with one or more UEIBM reporting configurations), the UE may be configured to perform one or more actions. In some examples, in accordance with one or more aspects of the present disclosure, the UE may determine a criterion pertaining to at least one retransmission of a PUCCH message (e.g., a first PUCCH channel) is satisfied, where the PUCCH message is associated with an event triggered CSI report. In some such examples, the UE (e.g., and an associated network node) may be configured to perform at least one operation based on the criterion being satisfied.

[0188] In some examples, the one or more actions includes the UE refraining from performing one or more event evaluations for one or more reporting configurations associated with the first PUCCH message. Additionally, or alternatively, the one or more actions includes the UE releasing (e.g., refraining from using) one or more PUCCH resources associated with the first PUCCH message, in which the PUCCH resource(s) are configured via a CSI report configuration (e.g., via a CSI-ReportConfig IE). In some examples, the UE may release one or more PUCCH resources (e.g., all the PUCCH resources) that are configured via the CSI report configuration and are associated with event triggered reporting. In some other examples, the UE may release one or more PUCCH resources (e.g., all PUCCH resources) that are configured via the CSI report configuration for at least one serving cell.

[0189] Additionally, or alternatively, the one or more actions includes the UE initiating a random access procedure (e.g., a CBRA procedure). In some such examples, as part of the CBRA procedure, the UE may provide one or more indications associated with event triggered reporting, referred to herein as event indications. The event triggered reporting may be associated with lower-layer triggered mobility (LTM). In some examples, the event indication may be a MAC CE for indicating failure for an event triggered transmission. In some other examples, the event indication may be a MAC CE for beam failure recovery. In some examples, the UE may transmit (e.g., provision) an event indication in accordance with an available uplink grant. In some such examples, the event indication be associated with event triggered reporting. In some other examples, the UE may transmit the at least one event indication in a MAC CE. In some such examples, the at least one event indication may include an indication that at least one reporting criterion for at least one UEIBM report has been triggered. In some examples, by performing the one or more operations, the UE (and the network node) may reduce latency and improve communications within a communicationsnetwork, such as a communications network illustrated by and described with reference to FIG. 1.

[0190] FIG. 5 illustrates an example of a signaling diagram for UEIBM to which one or more examples disclosed herein may be applied. The signalling flow diagram of FIG. 5 illustrates operations performed, such as within the system of FIG. 1, by the UE 120 and the network node 110 in accordance with one or more aspects of the present disclosure. One or more operations performed at the UE 120 and the network node 110 may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 120 and the network node 110 may be omitted and / or one or more other operations may be added.

[0191] In some scenarios, a UE and a network entity may be unaware of UE actions when a threshold quantity of retransmissions is reached for a first PUCCH message associated with event based CSI reporting, which may lead to increased latency and reduced performance for the UE. To reduce latency and improve performance of the UE 120 (and the network 110) the present disclosure provides a framework for UE actions when a threshold quantity of retransmissions is reached for a PUCCH message associated with event based CSI reporting. That is, in accordance with the present disclosure, the UE 120 and the network node 110 support one or more UE behaviors when the threshold quantity (e.g., a maximum number) of retransmissions is reached for a PUCCH message associated with event based CSI reporting.

[0192] At 514, the UE 120 may determine a criterion pertaining to at least one retransmission of a PUCCH message is satisfied. The PUCCH message may be associated with an event triggered channel CSI report. For example, the PUCCH message may include the first PUCCH message illustrated by and described with reference to FIGs. 3 A and 3B. The first PUCCH message may also be referred to as a first PUCCH channel.

[0193] At 512, the UE 120 may retransmit the PUCCH message and the UE may determine (at 514) that a criterion associated with the retransmission of the PUCCH message is satisfied. In other words, in response to the retransmission of the PUCCH message at 512, the UE 120 may determine that a threshold quantity of retransmissions for the PUCCH message is reached. That is, in some examples, the criterion includes a threshold quantity of retransmissions for the PUCCH message and, at 514, the UE 120 may determine the retransmission performed at 512 satisfies the threshold quantity of retransmission. In some examples, the threshold quantity of retransmissions includes a maximum quantity of retransmissions of PUCCH messages associated with event triggered CSI reporting. That is,in some examples, the criterion includes that a maximum number of retransmissions of the PUCCH message is reached. In some examples, in response to the determination at 514, the UE 120 (e.g., and the network node 110) may perform at least one operation. That is, the UE 120 may perform at least one operation based on the criterion being satisfied.

[0194] For example, at 516, the UE 120 may refrain from performing one or more event evaluations associated with the PUCCH message. In other words, in some examples, the one or more operations includes the UE 120 determining not to perform one or more event evaluations for one or more reporting configurations associated with the PUCCH message.

[0195] Additionally, or alternatively, at 518, the UE 120 may release at least one resource. For example, the UE may release at least one PUCCH resource, in which the at least one PUCCH resource may include at least one of the following: at least one PUCCH resource associated with the PUCCH message; at least one PUCCH resource associated with event triggered CSI reporting, at least one PUCCH resource associated with an event triggered CSI report, or at least one PUCCH resource associated with at least one serving cell. In other words, in some examples, the one or more actions includes the UE 120 releasing (e.g., refraining from using) one or more PUCCH resources associated with the first PUCCH message. In some examples, the PUCCH resource(s) are configured via a CSI report configuration (e.g., via a CSI-ReportConfig IE). In some such examples, the UE may release one or more PUCCH resources (e.g., all the PUCCH resources) configured via the CSI report configuration and are associated with event triggered reporting. In some other examples, the UE may release one or more PUCCH resources (e.g., all PUCCH resources) that are configured via the CSI report configuration for at least one serving cell. In some examples, the UE 120 may receive a control message associated with CSI reporting from the network node 110. In some such examples, the control message includes an indication of the at least on PUCCH resource. In other words, the UE 120 may release a PUCCH resource configured by the network node 110 for CSI Reporting.

[0196] In some examples, releasing a resource may refer to at least one of the UE 120 determining that a resource configuration (that indicate the resource) is no longer configured for the UE, or the UE determining to refrain from transmitting (e.g., suspend transmission) an uplink message via the resource. In other words, releasing the at least one resource includes at least one of the following: determining a resource configuration associated with the at least one resource is invalid; or refraining from providing for transmission of an uplink message via the at least one resource.

[0197] Additionally, or alternatively, at 522, the UE 120 may transmit an uplink message that includes at least one event indication associated with the event triggered CSI report. That is, in some examples, the one or more actions include the UE 120 transmitting an uplink message. In some such examples, the UE 120 may transmit the uplink message via at least one uplink resource in accordance with an uplink grant. For example, the UE 120 may transmit an event indication for the event triggered CSI report in an uplink grant. That is, in some examples, the UE 120 may transmit the uplink message via at least one uplink resource in accordance with an uplink grant, in which the uplink message includes at least one indication associated with the event triggered CSI report based on the criterion being satisfied. In other words, the UE 120 may transit an indication associated with the event triggered CSI report in accordance with an uplink grant.

[0198] In some examples, the event indication indicates a failure for the event triggered CSI report and / or indicates a beam failure recovery. That is, in some examples, the uplink message includes an event indication associated with a beam failure recovery, in which the indication triggers a beam failure recovery procedure for a serving cell for which the criterion is satisfied. In some examples, the UE 120 may transmit an indication that the criterion is satisfied. For example, the uplink message may include an event indication indicating a criterion associated with the event triggered CSI report is triggered.

[0199] In some examples, the criterion is associated with a UEIBM reporting configuration. In some such examples, the event indication indicates that at least one reporting criterion for the UEIBM report is satisfied. In some examples, the uplink message includes a MAC CE. In some such examples, the event indication may be the MAC CE or an indication provided in the MAC CE.

[0200] In some examples, the UE may be configured with a timer to monitor the event triggered reporting. In some such examples, the timer may be used to monitor the transmission and / or the retransmission of the (first) PUCCH message associated with event triggered reporting (e.g., the event triggered report). The timer may be started (e.g., initiated) in response to the PUCCH message being transmitted for the event triggered reporting. In some examples, while the timer is running, the UE may perform transmission of the PUCCH message associated with the event triggered report. In some examples, the timer may be stopped in response to the UE receiving a DCI message indicating a request (e.g., and one or more uplink resources) for an event triggered report associated with the PUCCH message. In some examples, in response to expiration of the timer, the UE may refrain from transmitting(e.g., is not allowed to perform transmission of) the PUCCH message associated with the event triggered report. Accordingly, the UE may determine to perform one or more actions based on the expiration of the timer. The UE may use the timer, for example, as an alternative to the counter (e.g., a maximum number of PUCCH (re-)transmissions). The timer may be applied and / or configured per event triggered reporting configuration. In at least one example, the timer may have a value on the order of tens of milliseconds or hundreds of milliseconds (e.g. a value of 100ms).

[0201] In some examples, the UE 120 may transmit the uplink message in accordance with a random access procedure. For example, at 520, the one or more actions may include the UE 120 initiating a random access procedure, such as a CBRA procedure. In such an example, the UE 120 may transmit one or more event indications to the network node 110 in accordance with the random access procedure (e.g., at least one indication associated with the event triggered CSI report). In some examples, the UE 120 may transmit the uplink message in accordance with an uplink grant. For example, the UE 120 may receive, a random access response from the network node 110, in which the random access response indicates the uplink grant. In some such examples, the uplink grant may be for the UE 120 to transmit a third message (e.g., MSG3) of the CBRA procedure. In other words, in some examples, the event indication provided in the CBRA procedure may be included in MSG3, which may be transmitted in accordance with the uplink grant. In some such examples, the event indication provided in the CBRA procedure may be a MAC CE included in MSG3. Additionally, or alternatively, the event indication may be provided in a MAC CE included in the uplink grant for MSG3. That is, the event indication may include the MAC CE or an indication provided in the MAC CE. In some examples, the uplink message may include a physical (PHY) layer message (also referred to as a layer one (LI) message. In some examples, the random access procedure may include one or more operations performed by the network node 110. For example, at the network node 110, performing the random access procedure may include reception of a random access preamble (e.g., and an associated payload in the case of 2-step CBRA), transmission of a random access response, and / or contention resolution. In some examples, initiating the random access procedure may include one or more operations at the UE 120. For example, at the UE 120, initiation of the random access procedure may include transmission of a random access preamble (e.g., and an associated payload in the case of 2- step CBRA) and / or reception of a random access response.

[0202] In some examples, the MAC CE is associated with UEIBM reporting, UE event triggered reporting, and / or beam failure recovery. For example, the MAC CE may be for indicating failures associate with event triggered transmissions.

[0203] In some examples, the MAC CE may indicate a serving cell or multiple serving cells for which the criterion is satisfied (e.g., may include a bitmap of one or more serving cells in which each bitfield maps to a serving cell index / identifier). Additionally, or alternatively, the MAC CE may indicate an event triggered reporting configuration identifier for which the first criterion is satisfied. Additionally, or alternatively, the MAC CE may indicate an identifier of the PUCCH message for which the criterion is satisfied (e.g., an identifier corresponding to the PUCCH message retransmitted at 512). Additionally, or alternatively, the MAC CE may indicate that the criterion is satisfied for at least one PUCCH message. In some examples, the LCID of the MAC CE may indicate that the MAC CE provisions (e.g., indicates) information on the event indication. In some such examples, the information is related to the transmission of the PUCCH for event triggered reporting.Additionally, or alternatively, the MAC CE may indicate a PCI corresponding to at least one serving cell for which the criterion is satisfied. Additionally, or alternatively, the MAC CE may indicate a serving cell index / identifier corresponding to at least one serving cell for which the criterion is satisfied. In some examples, the serving cell index / identifier for primary cell may be ‘O’. In some other examples, for Secondary cells, the identifier may be a non-zero index value (e.g., based on the RRC configuration). In some examples, the bit fields in the bitmap may refer / map to one or more reporting configuration identifiers. In some examples, the event indication may include an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, and / or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

[0204] In some examples, the PUCCH message may include the event indication in the form of a codepoint indication, bit, and / or bitmap. In other words, the event indication may include at least one of the following: an indication of a codepoint, at least one bit, or at least one bitmap. In some examples in which the event indication includes an indication of codepoint, the codepoint indication may be indicated by a bit field in the MAC CE. In some such examples, the codepoint indication may indicate a codepoint that maps to a reporting configuration identifier. In other words, the UE 120 may transmit a MAC CE including a bitfield, in which the bit field includes an indication of the codepoint, and the codepoint corresponds to an identifier of a reporting configuration. In some examples, the reporting configuration is associated with aperiodic CSI reporting and / or UEIBM. In some examples, the MAC CE indication may include, or refer to, at least one of the following: an identifier of a (CSI) reporting configuration, event identifier, event triggered CSI reporting configuration, the reporting configuration is associated with aperiodic CSI reporting and / or UEIBM reporting configuration. In some examples, the UE 120 may be configured to trigger a beam failure recovery procedure for one or more serving cells for which the criterion is satisfied. In some such examples, the UE 120 may transmit a beam failure recovery MAC CE in the uplink grant for MSG3 of the CBRA procedure and the beam failure recovery MAC CE may include the event indication.

[0205] In some examples, the UE 120 (e.g., and the network node 110) may determine that a procedure associated with the criterion has been completed based on the UE 120 transmitting the event indication and / or based on the UE 120 successfully completing the CBRA procedure. In other words, upon provisioning a MAC CE indicating that that the criterion is satisfied and / or successful completion of the CBRA procedure, the UE 120 may determine that a procedure for indicating that the criterion is satisfied is completed. In some examples, based on completing the procedure, the UE 120 may reset a counter associated with the criterion. Additionally, or alternatively, the UE 120 may restart an event evaluation for a reporting configuration associated with the event triggered CSI report and / or a configuration associated with the PUCCH message. In other words, the UE 120 may be configured to reset the threshold transmission counter (e.g., the maximum transmission counter) and / or restart an event evaluation, in which the event evaluation is for a reporting configuration or one or more configurations associated with the PUCCH message for which the indication is completed.

[0206] In some examples, the event indication includes an indication transmitted using a random access resource associated with event triggered CSI reporting and / or an indication of provisioning information pertaining to event triggered CSI reporting. For example, transmission of the at least one indication via a random access resource may indicate that the random access resource is associated with event triggered reporting.

[0207] For example, the event indication provided in the CBRA procedure may indicate a selection of a random access channel (RACH) resource associated with event triggered reporting and / or provisioning information related to event triggered reporting. That is, if theUE transmits an indication using a random access resource, the network may determine that the random access resource is associated with event triggered reporting. In other words, transmission of the at least one indication via a random access resource indicates that the random access resource is associated with event triggered reporting.

[0208] In some examples, the criterion is associated with a UEIBM reporting configuration. In some such examples, the event indication indicates that at least one reporting criterion for at least one UEIBM report is satisfied. Additionally, in some such examples, determining the criterion is satisfied (e.g., at 514) is in accordance with the UEIBM reporting configuration.

[0209] In some examples, the criterion is one of multiple criteria configured at the UE 120 for event triggered CSI reporting. In some such examples, each criterion of the criteria is associated with a respective reporting event. In other words, in some examples, the criterion (e.g., a maximum number of retransmissions) is configured per reporting event.

[0210] In some examples, the PUCCH message is associated with a scheduling request identifier configured at the UE 120 for event triggered CSI reporting and / or a PUCCH resource identifier configured at the apparatus for event triggered CSI reporting. For example, the first PUCCH message may include a scheduling request identifier configured for the even triggered reporting and / or a PUCCH resource identifier configured for the even triggered reporting. In some examples, the PUCCH message may be associated with at least one of the following: a scheduling request identifier configured at the apparatus for event triggered CSI reporting, a PUCCH resource identifier configured at the apparatus for event triggered CSI reporting, a PUCCH resource identifier configured at the apparatus for indication of at least one event associated with event triggered CSI reporting, and / or a PUCCH resource identifier configured at the apparatus for indication of event triggered CSI reporting.

[0211] In some examples, the UE 120 may receive a control message from the network node 110, in which the control message includes an indication of a type of unified TCI state. In some such examples, a power associated with the retransmission of the PUCCH message (e.g., at 512) is based on the indication. In other words, if a unifiedTCI-StateType - joint information element (IE) is configured at the UE 120, the UE 120 may determine (e.g., assume) that the indicated unified TCI-state is re-configured with different PUCCH power control settings, such that the UE 120 may increase the transmission power for upcoming PUCCH transmission(s), given there is sufficient power budget available for the transmission power increase at the UE 120.

[0212] In some examples in which the UE 120 performs the CBRA procedure in response to the criterion being satisfied, the UE 120 may perform resource selection for the CBRA procedure in accordance with one or more prioritization rules. That is, in response to initiating a CBRA procedure, the UE 120 may identify one or more downlink reference signals to use for the CBRA procedure. Stated alternatively, the UE may perform resource selection in response to initiating a CBRA procedure. In some examples, the UE 120 may determine whether one or more downlink reference signals (e.g., one or more synchronization signal blocks (SSBs)) satisfies a resource selection threshold. For examples in with the UE 120 identifies one or more SSBs that satisfy the resource selection threshold, the UE 120 may prioritize those SSBs. That is, the UE 120 may select SSBs that satisfy the resource selection threshold for CBRA. In some examples, the selection threshold is a received power threshold, such as a reference signal received power (RSRP) threshold. In some such examples, the UE 120 may select SSBs with a received power that is above the resource selection threshold.

[0213] For example, the UE 120 may identify a first downlink reference signal (e.g., SSB) associated with a transmission configuration indicator (TCI) state. The TCI state may be an indicated TCI state or an activated TCI state. For example, the UE 120 may determine an SSB associated with a TCI state indicated as indicated (e.g., a quasi co-located (QCLed) source reference signal of a tracking reference signal (TRS) that is included in the indicated TCI state) or the UE 120 may determine an SSB associated with an activated TCI state (e.g., a previously configured TCI state that is activated, such as via other control signaling). The UE 120 may determine a received power associated with the first downlink reference signal and then may select, in accordance with the one or more prioritization rules, one or more downlink reference signals for the CBRA procedure based on the determined received power.

[0214] In some examples, the one or more prioritization rules may specify for the UE 120 to select the first downlink reference signal based on the received power satisfying a resource selection threshold. That is, the UE 120 may determine that an SSB associated with the indicated TCI state has a received power above an SSB selection threshold and, in accordance with the one or more prioritization rules, may select that SSB with priority for the CBRA procedure. Additionally, the one or more prioritization rules may specify for the UE 120 to select a second downlink reference signal based on the received power failing to satisfy the resource selection threshold. In some examples, the UE 120 may identify a set of multiple downlink reference signals associated with multiple TCI states, in which the set of downlink reference signals includes at least the first downlink reference signal. In such anexample, the UE 120 may select the second downlink reference signal from the set of downlink reference signals. That is, the second reference signal may be one of the multiple downlink reference signals included in the set from which the second downlink reference signal is selected. In other words, in accordance with the prioritization rules, if a received power of an SSB associated with the indicated TCI state is not above the resource selection threshold, the UE 120 may select an identified SSB (e.g., any identified SSB).

[0215] In some examples, the UE 120 may identify the TCI state based on a TCI state codepoint, in which the TCI state codepoint is indicative of a TCI state type associated with the TCI state. In some such examples, the UE 120 may perform the resource selection in accordance with the one or more prioritization rules based on the TCI state type. For example, the TCI state type may be a first TCI state type (e.g., a joint TCI state) based on the TCI state codepoint being associated with a single TCI state or a second TCI state type (e.g., a separate TCI state) based on the TCI state codepoint being associated with one or two TCI states. In some examples, the UE 120 may apply the one or more prioritization rules if the UE 120 is configured with a joint TCI state and / or a separate TCI state.

[0216] FIG. 6 illustrates an example flowchart 600 of a method to which one or more examples disclosed herein may be applied. The method may be computer-implemented. The method may be performed by a UE, such as a UE illustrated by and described with reference to FIGs. 1-5. In some examples, the UE may be an example of an apparatus 10 illustrated by and described with reference to FIG. 10.

[0217] As shown in FIG. 6, the UE at block 610 determines a criterion pertaining to at least one retransmission of a PUCCH message is satisfied, where the PUCCH message is associated with an event triggered CSI report. In other words, the UE includes the means (e.g., processor 12, memory 14) for determining that a criterion pertaining to at least one retransmission of a PUCCH message is satisfied, where the PUCCH message is associated with an event triggered CSI report. The criterion may be an example of a retransmission criterion illustrated by and described with reference to at least FIG. 5. For example, the PUCCH message may be an example of a first PUCCH message of a UEIBM procedure and the criterion may include a threshold quantity (e.g., a maximum number) of retransmissions for the first PUCCH message.

[0218] As shown in FIG. 6, the UE at block 620, performs at least one operation based on the criterion being satisfied. In other words, the UE includes the means (e.g., a processor 12, memory 14, radio interface 16) for preforming at least one operation based on the criterionbeing satisfied. The at least one operation may include one or more operations illustrated by and described with reference to FIGs. 3A, 3B, 4 and / or 5. For example, the at least one operation may include refraining for performing one or more event evaluations, releasing one or uplink resources, initiating a random access procedure, and / or transmitting an uplink message.

[0219] FIG. 7 illustrates an example flowchart 700 of a method to which one or more examples disclosed herein may be applied. The method may be computer-implemented. The method may be performed by a network node, such as a network node illustrated by and described with reference to FIGs. 1-5. In some examples, the network node may be an example of an apparatus 10 illustrated by and described with reference to FIG. 10.

[0220] As shown in FIG. 7, the network node at block 710, receives at least one indication that a criterion pertaining to a retransmission of a PUCCH message associated with an event triggered CSI report is satisfied. In other words, the network node includes the means (e.g., processor 12, memory 14, radio interface 16) for receiving at least one indication that a criterion pertaining to a retransmission of a PUCCH message associated with an event triggered CSI report is satisfied. The PUCCH message may be an example of a PUCCH message illustrated by and described with reference to at least FIG. 5. For example, the PUCCH message may be an example of a first PUCCH message of a UEIBM procedure.

[0221] As shown in FIG. 7, the network node at block 720, performs at least one operation based on the criterion being satisfied. In other words, the network node includes the means (e.g., a processor 12, memory 14, radio interface 16) for preforming at least one operation based on the criterion being satisfied. The criterion may be an example of a retransmission criterion illustrated by and described with reference to at least FIG. 5. For example, the criterion may include a threshold quantity (e.g., a maximum number) of retransmissions for the first PUCCH message. Additionally, the at least one operation may include one or more operations illustrated by and described with reference to FIGs. 3 A, 3B, 4 and / or 5. For example, the at least one operation may include receiving an uplink message via at least one uplink resource in accordance with an uplink grant and / or performing a random access procedure with a UE.

[0222] FIG. 8 illustrates an example flowchart 800 of a method to which one or more examples disclosed herein may be applied. The method may be computer-implemented. The method may be performed by a UE, such as a UE illustrated by and described with referenceto FIGs. 1-5. In some examples, the UE may be an example of an apparatus 10 illustrated by and described with reference to FIG. 10.

[0223] As shown in FIG. 8, the UE at block 810, determines a criterion pertaining to at least one retransmission of a PUCCH message is satisfied, where the PUCCH message is associated with an event triggered CSI report. In other words, the UE includes the means (e.g., processor 12, memory 14) for determining that a criterion pertaining to at least one retransmission of a PUCCH message is satisfied, where the PUCCH message is associated with an event triggered CSI report. The criterion may be an example of a retransmission criterion illustrated by and described with reference to at least FIG. 5. For example, the PUCCH message may be an example of a first PUCCH message of a UEIBM procedure and the criterion may include a threshold quantity (e.g., a maximum number) of retransmissions for the first PUCCH message.

[0224] As shown in FIG. 8, the UE at block 820, performs at least one operation in accordance with a CBRA procedure based on the criterion being satisfied, where the at least one operation includes performing resource selection for the CBRA procedure in accordance with one or more prioritization rules. In other words, the UE includes the means (e.g., a processor 12, memory 14, radio interface 16) for preforming at least one operation in accordance with a CBRA procedure based on the criterion being satisfied, where the at least one operation includes performing resource selection for the CBRA procedure in accordance with one or more prioritization rules. The prioritization rules may be an example of prioritization rules illustrated by and described with reference to at least FIG. 5. For example, in accordance with the prioritization rules, the UE may select the first downlink reference signal based on the received power satisfying a threshold, or the UE may select a second downlink reference signal based on the received power failing to satisfy the threshold.

[0225] FIG. 9 illustrates an example flowchart 900 of a method to which one or more examples disclosed herein may be applied. The method may be computer-implemented. The method may be performed by a network node, such as a network node illustrated by and described with reference to FIGs. 1-5. In some examples, the network node may be an example of an apparatus 10 illustrated by and described with reference to FIG. 10.

[0226] As shown in FIG. 9, the network node at block 910, receives at least one indication that a criterion pertaining to a retransmission of a PUCCH message associated with an event triggered CSI report is satisfied. In other words, the network node includes the means (e.g., processor 12, memory 14, radio interface 16) for receiving at least one indicationthat a criterion pertaining to a retransmission of a PUCCH message associated with an event triggered CSI report is satisfied. The PUCCH message may be an example of a PUCCH message illustrated by and described with reference to at least FIG. 5. For example, the PUCCH message may be an example of a first PUCCH message of a UEIBM procedure.

[0227] As shown in FIG. 9, the network node at block 920, provides for transmission of a plurality of downlink reference signals. In other words, the network node includes the means e.g., a processor 12, memory 14, radio interface 16) for providing for transmission of a plurality of downlink reference signals.

[0228] As shown in FIG. 9, the network node at block 930, performs at least one operation in accordance with a CBRA procedure based at least in part on the criterion being satisfied, wherein the CBRA procedure is in accordance with at least one downlink reference signal of the plurality of downlink reference signals based at least in part on one or more prioritization rules. In other words, the network node includes the means (e.g., a processor 12, memory 14, radio interface 16) for preforming at least one operation in accordance with a CBRA procedure based at least in part on the criterion being satisfied, wherein the CBRA procedure is in accordance with at least one downlink reference signal of the plurality of downlink reference signals based at least in part on one or more prioritization rules. The criterion may be an example of a retransmission criterion illustrated by and described with reference to at least FIG. 5. For example, the PUCCH message may be an example of a first PUCCH message of a UEIBM procedure and the criterion may include a threshold quantity (e.g., a maximum number) of retransmissions for the first PUCCH message. Additionally, the prioritization rules may be an example of prioritization rules illustrated by and described with reference to at least FIG. 5. For example, in accordance with the prioritization rules, the resource selection may include selection of the first downlink reference signal based on the received power satisfying a threshold, or the resource selection may include selection of a second downlink reference signal based on the received power failing to satisfy the threshold.

[0229] FIG. 10 illustrates an example block diagram of an apparatus to which one or more examples disclosed herein may be applied. FIG. 10 shows, by way of example, a block diagram of an apparatus 10. The apparatus 10 comprises, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause the apparatus 10 at least to perform the method or methods as disclosed herein, and any of the embodiments thereof. In an example, the at least one memory and the instructions (e.g. a computer program code, software), are configured, with the at least oneprocessor, to cause the apparatus 10 to perform the method or methods as disclosed herein, and any of the embodiments thereof.

[0230] A processor 12 may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with one or more example embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a user equipment, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0231] The memory 14 may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory 14 may be at least in part external to apparatus 10 but accessible to apparatus 10.

[0232] The instructions 15 may be comprised in a computer readable medium or a non- transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. random access memory, RAM, vs. read only memory, ROM).

[0233] For example, the apparatus 10 is a terminal device, such as the UE of FIGs. 1 and 3-5. As another example, the apparatus is comprised in such a terminal device, e.g. as a chipset configured to control the terminal device. The apparatus 10 may be caused or configured to perform at least the method of FIGs. 6 and 8 and / or any one or more of the embodiments described.

[0234] As another example, the apparatus 10 is a network node, e.g. the network node of FIGs. 1 and 3-5. In another embodiment, the apparatus is comprised in such a network node, e.g. as a chipset configured to control the network node. The apparatus 10 may be caused or configured to perform at least the method of FIGs. 7 and 9 and / or any one or more of the embodiments described.

[0235] The apparatus may comprise one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity. In at least one embodiment, the entity is configured to perform at least the method of Figs.6-9, and / or any one or more of the embodiments described.

[0236] The apparatus 10 comprises a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may comprise a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may comprise a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may comprise more than one receiver. The transmitter may comprise more than one transmitter. The radio interface 16 may comprise a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard. The transceiver may comprise more than one transceiver.

[0237] The apparatus 10 may comprise a user interface 18 comprising, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The user interface 18 may be used to control the apparatus by the user. The user interface 18 may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled by the user via the computer.

[0238] In at least one embodiment, at least some of the processes described herein may be carried out by an apparatus comprising means for carrying out at least some of the described processes. Means for performing methods as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and any of the embodiments thereof. As used herein the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only onemeans for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[0239] Even though the present disclosure has been described above with reference to an example according to the accompanying drawings, it is clear that the present disclosure is not restricted thereto but can be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, the embodiment. It will be obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. Further, it is clear to a person skilled in the art that the described embodiments may, but are not required to, be combined with other embodiments in various ways.

Claims

What is claimed is:

1. An apparatus, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; and perform at least one operation based at least in part on the criterion being satisfied.

2. An apparatus according to claim 1, wherein performing the at least one operation comprises: refraining from performing an event evaluation associated with the event triggered CSI report.

3. An apparatus according to claim 1 or 2, wherein performing the at least one operation comprises releasing at least one resource, and wherein the at least one resource comprises at least one of the following: one or more PUCCH resources associated with the PUCCH message; one or more resources associated with event triggered CSI reporting; one or more resources associated with at least one serving cell; or one or more PUCCH resources associated with the event triggered CSI report.

4. An apparatus according to claim 3, wherein releasing the at least one resource comprises at least one of the following: determining a resource configuration associated with the at least one resource is invalid; or refraining from providing for transmission of an uplink message via the at least one resource.

5. An apparatus according to claim 3 or 4, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive a control message associated with CSI reporting, wherein the control message comprises an indication of the at least one resource.

6. An apparatus according to any one of claims 1-5, wherein performing the at least one operation comprises: providing for transmission of an uplink message via at least one uplink resource in accordance with an uplink grant, wherein the uplink message comprises at least one indication associated with the event triggered CSI report based at least in part on the criterion being satisfied.

7. An apparatus according to any one of claims 1-6, wherein performing the at least one operation comprises: initiating a random access procedure with a network entity.

8. An apparatus according to claim 7, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive, from the network entity, a random access response indicative of an uplink grant; and provide for transmission of at least one indication to the network entity in accordance with the uplink grant, wherein the at least one indication is associated with the event triggered CSI report.

9. An apparatus according to claim 8, wherein the at least one indication comprises a medium access control (MAC) control element (CE) or an indication included in the MAC CE.

10. An apparatus according to claim 9, wherein the MAC CE is associated with at least one of the following: user equipment (UE) event triggered reporting, beam failure recovery, or UE initiated beam management reporting.

11. An apparatus according to claim 9 or 10, wherein the MAC CE is for indicating one or more failures associated with event triggered transmissions.

12. The apparatus according to any one of claims 8-11, wherein the at least one indication comprises at least one of the following: an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

13. An apparatus according to any one of claims 8-12, wherein the at least one indication comprises an indication of at least one of the following: a codepoint, at least one bit, or at least one bitmap.

14. An apparatus according to claim 13, wherein the at least one indication comprises the indication of the codepoint, and wherein providing for transmission of the indication of the codepoint comprises: providing for transmission of a medium access control (MAC) control element (CE) comprising a bit field, wherein the bit field includes the indication of the codepoint, and wherein the codepoint corresponds to an identifier of a reporting configuration.

15. An apparatus according to claim 14, wherein the reporting configuration is associated with at least one of the following: aperiodic CSI reporting or user equipment (UE) initiated beam management.

16. An apparatus according to any one of claims 8-15, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: determine that a procedure associated with the criterion has been completed based at least in part on the transmission of the at least one indication or successful completion of the random access procedure.

17. An apparatus according to claim 16, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to:based at least in part on the procedure being completed, reset a counter associated with the criterion, or restart an event evaluation for at least one of the following: a reporting configuration associated with the event triggered CSI report or a configuration associated with the PUCCH message.

18. An apparatus according to any one of claims 8-17, wherein the at least one indication comprises at least one of the following: an indication of a random access resource associated with event triggered CSI reporting or an indication of provisioning information pertaining to event triggered CSI reporting.

19. An apparatus according to any one of claims 7-18, wherein the random access procedure comprises a contention based random access (CBRA) procedure.

20. An apparatus according to any one of claims 1-19, wherein performing the at least one operation comprises at least one of the following: providing for transmission of an indication associated with a beam failure recovery, wherein the indication triggers a beam failure recovery procedure for a serving cell for which the criterion is satisfied; providing for transmission of an indication associated with the event triggered CSI report in accordance with an uplink grant; or providing for transmission of an indication that the criterion is satisfied.

21. An apparatus according to claim 20, wherein the criterion is associated with a user equipment (UE) initiated beam management reporting configuration, and wherein the indication indicates that at least one reporting criterion for at least one UE initiated beam management report is satisfied.

22. An apparatus according to claim 21, wherein providing for transmission of the indication comprises: providing for transmission of a medium access control (MAC) control element (CE) comprising the indication.

23. An apparatus according to any one of claims 1-22, wherein the criterion comprises a threshold quantity of retransmissions for the PUCCH message, and wherein determining the criterion is satisfied comprises: determining the at least one retransmission satisfies the threshold quantity of retransmissions.

24. An apparatus according to claim 23, wherein the threshold quantity of retransmissions comprises a maximum quantity of retransmissions of PUCCH messages associated with event triggered CSI reporting.

25. An apparatus according to any one of claims 1-22, wherein the criterion comprises a timer associated with retransmission of the PUCCH message, and wherein determining the criterion is satisfied comprises: determining an expiration of the timer.

26. An apparatus according to any one of claims 1-25, wherein the criterion is associated with a user equipment (UE) initiated beam management reporting configuration, and wherein determining the criterion is satisfied comprises: determining the criterion is satisfied in accordance with the UE initiated beam management reporting configuration.

27. An apparatus according to any one of claims 1-26, wherein the criterion is one of a plurality of criteria configured at the apparatus for event triggered CSI reporting, and wherein each criterion of the plurality of criteria is associated with a respective reporting event.

28. An apparatus according to any one of claims 1-27, wherein the PUCCH message is associated with at least one of the following: a scheduling request identifier configured at the apparatus for event triggered CSI reporting or a PUCCH resource identifier configured at the apparatus for event triggered CSI reporting.

29. An apparatus according to any one of claims 1-28, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: receive a control message comprising an indication of a type of unified transmission configuration indicator state, wherein a power associated with the at least one retransmission is based at least in part on the indication.

30. An apparatus, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; and perform at least one operation based at least in part on the criterion being satisfied.

31. An apparatus according to claim 30, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for transmission of a control message associated with CSI reporting, wherein the control message comprises an indication of at least one PUCCH resource associated with the event triggered CSI report.

32. An apparatus according to claim 30 or 31, wherein receiving the at least one indication comprises: receiving an uplink message via at least one uplink resource in accordance with an uplink grant, wherein the uplink message comprises the at least one indication.

33. An apparatus according to any one of claims 30-32, wherein performing the at least one operation comprises: performing a random access procedure with a user equipment (UE).

34. An apparatus according to claim 33, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for transmission of a random access response to the UE, wherein the random access response is indicative of an uplink grant; and receive the at least one indication from the UE in accordance with the uplink grant.

35. An apparatus according to claim 34, wherein the at least one indication comprises a medium access control (MAC) control element (CE) or an indication included in the MAC CE.

36. An apparatus according to claim 35, wherein the MAC CE is associated with at least one of the following: user equipment (UE) event triggered reporting, beam failure recovery, or UE initiated beam management reporting.

37. An apparatus according to claim 35 or 36, wherein the MAC CE is for indicating one or more failures associated with event triggered transmissions.

38. An apparatus according to any one of claims 34-37, wherein the at least one indication comprises at least one of the following: an identifier corresponding to a reporting configuration for which the criterion is satisfied; an identifier corresponding to the PUCCH message, an indication that the criterion is satisfied for at least one PUCCH message, or at least one identifier corresponding to at least one serving cell for which the criterion is satisfied.

39. An apparatus according to any one of claims 34-38, wherein the at least one indication comprises at least one of the following: an indication of a codepoint, at least one bit, or at least one bitmap.

40. An apparatus according to claim 39, wherein the at least one indication comprises the indication of the codepoint, and wherein receiving the indication of the codepoint comprises: receiving a medium access control (MAC) control element (CE) comprising a bit field, wherein the bit field includes the indication of the codepoint, and wherein the codepointcorresponds to an identifier of a reporting configuration.

41. An apparatus according to claim 40, wherein the reporting configuration is associated with at least one of the following: aperiodic CSI reporting or UE initiated beam management.

42. An apparatus according to any one of claims 34-41, wherein the at least one indication comprises at least one of the following: an indication of a random access resource associated with event triggered CSI reporting or an indication of provisioning information pertaining to event triggered CSI reporting.

43. An apparatus according to any one of claims 34-42, wherein the random access procedure comprises a contention based random access (CBRA) procedure.

44. An apparatus according to any one of claims 30-43, wherein the at least one indication comprises at least one of the following: an indication associated with a beam failure recovery; or an indication associated with the event triggered CSI report.

45. An apparatus according to claim 44, wherein the at least one indication triggers a beam failure recovery procedure for a serving cell for which the criterion is satisfied.

46. An apparatus according to claim 45, wherein the criterion is associated with a UE initiated beam management reporting configuration, and wherein the at least one indication indicates that at least one reporting criterion for at least one UE initiated beam management report is satisfied.

47. An apparatus according to claim any one of claims 44-46, wherein receiving the at least one indication comprises: receiving a medium access control (MAC) control element (CE) comprising the indication.

48. An apparatus according to any one of claims 30-47, wherein the criterion comprises a threshold quantity of retransmissions for the PUCCH message.

49. An apparatus according to claim 48, wherein the threshold quantity of retransmissions comprises a maximum quantity of retransmissions of PUCCH messages associated with event triggered CSI reporting.

50. An apparatus according to any one of claims 30-47, wherein the criterion comprises a timer associated with the retransmission of the PUCCH message.

51. An apparatus according to any one of claims 30-50, wherein the criterion is associated with a UE initiated beam management reporting configuration.

52. An apparatus according to any one of claims 30-51, wherein the criterion is one of a plurality of criteria for event triggered CSI reporting, and wherein each criterion of the plurality of criteria is associated with a respective reporting event.

53. An apparatus according to any one of claims 30-52, wherein the PUCCH message is associated with at least one of the following: a scheduling request identifier for event triggered CSI reporting, or a PUCCH resource identifier for event triggered CSI reporting.

54. An apparatus according to any one of claims 30-53, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for transmission of a control message comprising an indication of a type of unified transmission configuration indicator state, wherein a power associated with the retransmission is based at least in part on the indication.

55. A method, comprising: determining a criterion pertaining to at least one retransmission of a physical uplink control channel (PUCCH) message is satisfied, wherein the PUCCH message is associated with an event triggered channel state information (CSI) report; andperforming at least one operation based at least in part on the criterion being satisfied.

56. A method, comprising: receiving at least one indication that a criterion pertaining to a retransmission of a physical uplink control channel (PUCCH) message associated with an event triggered channel state information (CSI) report is satisfied; and performing at least one operation based at least in part on the criterion being satisfied.

Citation Information

Patent Citations

  • Method and apparatus for beam failure recovery

    US20200275524A1

  • Terminal and radio communication method

    US20220279366A1

  • Beam Selection in Uplink Repetition

    US20230180242A1

  • US202463702952P