Methods and apparatus for handling beam reports initiated by user equipment in wireless communications

Abstract

A method and apparatus for handling beam reports initiated by a user equipment in wireless communication are provided. One method for a user equipment includes: a beam report initiated by a first user equipment configured to be associated with a serving cell, wherein the beam report initiated by the first user equipment is initiated or triggered based on a comparison between the quality of the current beam of the serving cell and the quality of a candidate beam of the serving cell; maintaining a counter associated with the beam report initiated by the first user equipment in the serving cell; and resetting the counter in response to a beam change of the current beam in the serving cell.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 644,989, filed May 9, 2024, and U.S. Provisional Patent Application No. 63 / 645,012, filed May 9, 2024; each of the applications and publications cited and listed herein is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for handling beam reports initiated by user equipment (UE) in wireless communication systems. Background Technology

[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This IP data packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing new radio technologies for next-generation technologies (e.g., 5G). Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate their evolution and completion. Summary of the Invention

[0006] Methods, systems, and apparatus are provided for handling beam reports initiated by a user equipment (UE) in a wireless communication system. In various embodiments, a method for a UE includes: a beam report initiated by a first UE configured to be associated with a serving cell, wherein the beam report initiated by the first UE is initiated or triggered based on a comparison between the quality of a current beam of the serving cell and the quality of candidate beams of the serving cell; maintaining a counter associated with the beam report initiated by the first UE in the serving cell; and resetting the counter in response to a beam change of the current beam on the serving cell. Attached Figure Description

[0007] Figure 1 The accompanying drawings illustrate a wireless communication system according to an embodiment of the present invention.

[0008] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention.

[0009] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention.

[0010] Figure 4 This is an embodiment of the present invention. Figure 3 Functional block diagram of the program code.

[0011] Figure 5 It is in 3GPP 38.321 v17.4.0 Figure 6 1.3.23-1: BFR and C with one octet i Reproduction of the truncated BFR MAC CE field.

[0012] Figure 6 It is in 3GPP 38.321 v17.4.0 Figure 6 1.3.23-2: BFR and C with four octets i Reproduction of the truncated BFR MAC CE field.

[0013] Figure 7 It is in draft 38.300 v 18.0.0 Figure 9 2.3.5.2-1 Reproduction of the signaling procedure for LTM.

[0014] Figure 8 It's 3GPP 38.321 v18.1.0. Figure 6 1.3.75-1: Reproduction of the LTM cell handover command MAC CE.

[0015] Figure 9 It's 3GPP 38.321 v18.1.0. Figure 6 1.3.76-1: Reproduction of candidate cell TCI status activation / deactivation MAC CE.

[0016] Figure 10A The accompanying drawings are examples illustrating, according to embodiments of the present invention, the problem that the network may receive outdated beam information or the UE may transmit unnecessary beam report information when two programs conflict.

[0017] Figure 10B The accompanying drawings are examples illustrating, according to embodiments of the present invention, how a UE can determine or discover that an event triggering a report for the cell is satisfied at t1.

[0018] Figure 11The accompanying drawings illustrate an example of how a UE can determine, at least based on the type of program, whether to perform an action in response to a beam report initiated by the UE in response to a program.

[0019] Figure 12 The accompanying drawings illustrate an example of how a UE determines whether to perform action 1 in response to a beam report initiated by the UE based on different events related to the beam report initiated by the UE, according to an embodiment of the present invention.

[0020] Figure 13A The accompanying drawings illustrate an example of how a UE determines, based on different events related to a beam report initiated by the UE, whether to perform actions 1 and 2 in response to a procedure for the beam report initiated by the UE.

[0021] Figure 13B The accompanying drawings are examples illustrating, according to embodiments of the present invention, that a UE can be configured with a UE-initiated beam reporting configuration (e.g., for MIMO) associated with a serving cell.

[0022] Figure 14 The accompanying drawing illustrates an example of a cell A (or its associated RS) associated with a beam report initiated by the UE at time t1, according to an embodiment of the present invention.

[0023] Figure 15 The accompanying drawings are examples illustrating how a UE can perform measurements (RS) on cell B according to an embodiment of the present invention.

[0024] Figure 16 The accompanying figure illustrates an example of an embodiment of the present invention, showing that a UE can measure cell C (on or associated RS) and determine at t1 that the quality of activated TCI state A is less than a threshold of cell C.

[0025] Figure 17 The accompanying drawing illustrates an example of a beam report initiated by a UE in serving cell A at time t1, according to an embodiment of the present invention.

[0026] Figure 18 The accompanying drawing illustrates an example of a beam fault recovery procedure initiated by a UE in serving cell A (e.g., SpCell) at time t1, according to an embodiment of the present invention.

[0027] Figure 19 The accompanying drawings are examples illustrating, according to embodiments of the present invention, a UE initiating or executing a random access procedure (e.g., handover, reconfiguration with synchronization, or LTM) at time t1.

[0028] Figure 20The accompanying drawings are examples illustrating candidate RS, CSI reference resources, PN, and (pre)configured resources for determining the quality of candidate beams according to embodiments of the present invention.

[0029] Figure 21 The accompanying drawings illustrate an example of a UE being (pre-)configured with three pairs or three bundles of PN resources, denoted as A, B, and C, and resources for UEI reporting, according to an embodiment of the present invention.

[0030] Figure 22 The accompanying drawings, which are examples of embodiments of the present invention, show a first dynamic signal (starting from the left of the figure) deactivating cell DRX, which means an active time within a time interval, and a second dynamic signal activating cell DRX, which means that cell DRX active time and cell DRX inactive time are based on an on-time duration timer associated with cell DRX configuration.

[0031] Figure 23 The accompanying drawings are examples of methods for providing solutions to one or more specific events that exist / occur / trigger at or overlap with time t1, according to embodiments of the present invention.

[0032] Figure 24 The accompanying drawings are examples illustrating, according to embodiments of the present invention, a first PN resource and a first (pre)configured resource for UEI reporting in a first BWP, and a second PN resource and a second (pre)configured resource for UEI reporting in a second BWP.

[0033] Figure 25 The accompanying drawings illustrate an example of a UE that can be configured with associations according to an embodiment of the present invention, wherein each PN resource can correspond to more than one resource in one or more BWPs for UEI (cross-BWP indication for supporting PN resources and resources for UEI reporting).

[0034] Figure 26 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, the method including, in response to one or more procedures, determining whether to perform one or more actions for a beam report initiated by a UE in a cell, based at least on an event associated with a beam report initiated by the UE.

[0035] Figure 27 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, the method including performing one or more actions in response to a beam report initiated by the UE in a cell in response to one or more procedures.

[0036] Figure 28This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, the method comprising: a beam report initiated by a first UE configured to be associated with a serving cell; maintaining a counter associated with the beam report initiated by the first UE in the serving cell; and resetting the counter in response to a beam change of the current beam on the serving cell.

[0037] Figure 29 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes: receiving a first CSI report configuration associated with a report initiated by the UE; generating a first UE-initiated report based on a condition satisfying a first event; transmitting a PN on a first UL resource at a first opportune time; and transmitting the first UE-initiated report on a second UL resource at a second opportune time.

[0038] Figure 30 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes: receiving a configuration of a serving cell having at least a first UL BWP and a second UL BWP; receiving a first CSI report configuration associated with a report initiated by the UE; generating a first UE-initiated report based on a condition satisfying a first event; transmitting a PN on a first PUCCH resource at a first time if at least a second time is later than a first time; receiving a signal from a network node indicating a change in an active UL BWP at a second time; and transmitting the first UE-initiated report on a second PUSCH resource at a third time if at least the second time is later than the first time. Detailed Implementation

[0039] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is described primarily in the context of the 3GPP architecture reference model. However, it should be understood that, with the aid of the disclosed information, those skilled in the art can readily adapt and implement aspects of the invention in 3GPP2 network architectures and other network architectures.

[0040] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice and data. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), 3GPP Long Term Evolution (LTE) Radio Access, 3GPP Long Term Evolution Advanced (LTE-A) Radio Access, and 3GPP2 Ultra Mobile Broadband (UMB). 3GPP New Radio (NR), or some other modulation technology.

[0041] Specifically, the exemplary wireless communication systems and apparatus described below can be designed to support one or more standards, such as those provided by the consortium referred to herein as 3GPP, which is named the “3rd Generation Partnership Project”, including: [1] RP-234007 New WID: NR MIMO Phase 5; [2] 3GPP 38.214v17.4.0; [3] 3GPP 38.321v17.4.0; [4] 3GPP 38.331v17.4.0; [5] Draft 38.300v 18.0.0; [6] RP-234036 New WID: NR Mobility Enhancement Phase 4; [7] 3GPP 38.321v18.1.0; [8] Chairman's Note RAN1#116eom0; and [9] Chairman's Note RAN1#116bis eom0;

[10] 3GPP TS 38.214V17.3.0(2022-09) 3GPP TS38.213V18.2.0(2024-03 ...

[0042] Figure 1A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one containing antennas 104 and 106, another containing antennas 108 and 110, and yet another containing antennas 112 and 114. Figure 1 In the diagram, only two antennas are shown for each antenna group; however, more or fewer antennas can be used for each antenna group. Access Terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, forward link 120 can use a different frequency than the reverse link 118.

[0043] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by access network 100.

[0044] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, an access network that uses beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in adjacent cells.

[0045] An AN can be a fixed station or base station used for communication with a terminal, and can also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or any other term. An AT can also be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or any other term.

[0046] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for multiple data streams is provided from the data source 212 to the transport (TX) data processor 214.

[0047] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data streams based on a specific decoding scheme selected for each data stream to provide decoded data.

[0048] OFDM technology can be used to multiplex the decoded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for said data stream are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. The data rate, decoding, and modulation for each data stream can be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.

[0049] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to symbols of the data stream and the antennas transmitting said symbols therefrom.

[0050] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and up-converts) the analog signals to provide modulated signals suitable for transmission via a MIMO channel. Then, from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0051] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.

[0052] The RX data processor 260 then uses specific receiver processing technology from N R 254 receivers receive and process N REach received symbol stream provides N T Each detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data used for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0053] Processor 270 periodically determines which pre-decoding matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index part and the rank part.

[0054] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0055] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Next, processor 230 determines which pre-decoding matrix to use to determine beamforming weights and then processes the extracted message.

[0056] Memory 232 can be used to temporarily store some buffered / calculated data from 240 or 242 via processor 230, some buffered data from 212, or some specific program code. Furthermore, memory 272 can be used to temporarily store some buffered / calculated data from 260 via processor 270, some buffered data from 236, or some specific program code.

[0057] Go to Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to achieve... Figure 1The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.

[0058] Figure 4 According to an embodiment of the present invention Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.

[0059] For LTE, LTE-A, or NR systems, layer 2, part 404, may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. Layer 3, part 402, may include a Radio Resource Control (RRC) layer.

[0060] Any two or more of the following paragraphs, (sub)bullets, points, actions, or claims described in each paragraph or section of the invention may be logically, reasonably, and appropriately combined to form a particular method.

[0061] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following invention paragraphs or sections can be implemented independently and separately to form a particular method or apparatus. Dependencies such as "based on," "more specifically," and "example" in the following invention disclosure are merely one possible embodiment and do not limit the specific method or apparatus.

[0062] In the work item description [1] RP-234007 New WID: NR MIMO Phase 5, MIMO enhancements for Rel-19 are introduced:

[0063] 3 reasons

[0064] In the existing beam management procedure, the network can configure / activate frequent periodic or semi-persistent beam reporting (e.g., N best beams and their corresponding L1-RSRPs) or trigger frequent aperiodic beam reporting to promptly acquire the best / preferred beams for data / control transmissions. However, this obviously leads to significant UL reporting overhead and control signaling overhead. Furthermore, if less frequent beam reporting is configured, the network cannot always acquire the "best / preferred" beam because the UE's beam reports may be outdated, resulting in performance degradation. Considering that the UE has a better and more timely understanding of beam quality changes, a UE-initiated beam reporting procedure can induce more timely beam reporting with reduced reporting overhead. In this procedure, if the UE determines, for example, that the current beam quality has deteriorated, the UE can trigger a beam report without requiring the network to configure or trigger frequent reporting.

[0065] …

[0066] 4 objectives

[0067] 4.1 Target of SI or core WI or test WI

[0068] The detailed objectives are as follows:

[0069] RAN1:

[0070] 1. Specify enhancements to facilitate UE-initiated / event-driven beam management, aiming to reduce overhead and / or latency, assuming a unified TCI, while (as much as possible) leveraging the existing CSI measurement and reporting configuration framework, targeting FR2 and sTRP with intra-cell and inter-cell beam management.

[0071] a. UL signaling content (and on-demand procedures) for UE-initiated / event-driven beam reporting to facilitate fast beam switching.

[0072] b. UL signaling media / containers, designed primarily for beam reporting, take into account the UE-initiated / event-driven nature of UL transmission.

[0073] …

[0074] Acronyms:

[0075] ●sTRP: Single TRP (Transmit / Receive Point)

[0076] ●mTRP: Multiple TRPs (transmitter / receiver points)

[0077] In [2] 3GPP 38.214v17.4.0, the CSI report is introduced:

[0078] 5.2 UE Procedure for Reporting Channel State Information (CSI)

[0079] 5.2.1 Channel State Information Framework

[0080] The procedure for non-periodic CSI reporting described in this clause assumes that CSI reports are triggered by DCI format 0_1, but they are equally applied to CSI reports triggered by DCI format 0_2 by applying the higher-level parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize.

[0081] The UE can use time and frequency resources to report CSI controlled by the gNB. CSI can consist of Channel Quality Indicator (CQI), Pre-decoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), L1-RSRP, L1-SINR, or CapabilityIndex.

[0082] For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, and Capability [Set] Index, the UE is configured by a higher layer through the following: N ≥ 1 CSI-ReportConfig settings, M ≥ 1 ResourceConfig settings, and one or two trigger state lists (given by the higher layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs indicating the resource set IDs used for the channel and optionally for interference. Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList contains one associated CSI-ReportConfig.

[0083] 5.2.1.1 Report Setup

[0084] Each report configuration CSI-ReportConfig is associated with a single downlink BWP (indicated by the higher-layer parameter BWP-Id) given in the associated CSI-ResourceConfig used for channel measurements and contains parameters for a CSI reporting band: codebook configuration including codebook subset restrictions, time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configuration, and the number of CSI-related parameters to be reported by the UE, such as layer indicator (LI), L1-RSRP, L1-SINR, CRI, and SSBRI (SSB resource indicator) and CapabilityIndex.

[0085] …

[0086] 5.2.1.2 Resource Settings

[0087] Each CSI resource setting (CSI-ResourceConfig) is configured to contain a list of S ≥ 1 CSI resource sets (given by the higher-level parameter csi-RS-ResourceSetList), wherein the list includes references to any one or both of the NZP CSI-RS resource set and the SS / PBCH block set, or the list includes references to the CSI-IM resource set. Each CSI resource setting resides in a DL BWP identified by the higher-level parameter BWP-id, and all CSI resource settings linked to the CSI reporting setting share the same DL BWP.

[0088] …

[0089] 5.2.1.4 Report Configuration

[0090] The UE should assume the following dependencies between CSI parameters (if reported) when calculating the CSI parameters (if reported).

[0091] -LI should be calculated based on the reported CQI, PMI, RI, and CRI.

[0092] - The CQI should be calculated based on the reported PMI, RI, and CRI.

[0093] - The PMI should be calculated based on the reported RI and CRI.

[0094] - The RI should be calculated based on the reported CRI.

[0095] CSI reporting configurations can be aperiodic (using PUSCH), periodic (using PUCCH), or semi-persistent (using PUCCH and DCI-activated PUSCH). CSI-RS resources can be periodic, semi-persistent, or aperiodic. Table 5.2.1.4-1 shows the supported combinations of CSI reporting configurations and CSI-RS resource configurations and how to trigger CSI reports for each CSI-RS resource configuration. Periodic CSI-RS are configured by higher levels. Semi-persistent CSI-RS are activated and deactivated as described in Clause 5.2.1.5.2. Aperiodic CSI-RS are configured and triggered / activated as described in Clause 5.2.1.5.1.

[0096] Table 5.2.1.4-1: Possible CSI-RS configuration for triggering / activating CSI reports.

[0097]

[0098]

[0099] …

[0100] 5.2.1.4.1 Resource Settings and Configuration

[0101] For aperiodic CSI, each trigger state configured using the higher-level parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, where CSI-ReportConfigs not configured with groupBasedBeamReporting-r17 are linked to periodic, semi-static, or aperiodic resource settings:

[0102] - When a resource setting is configured, the resource setting (given by the higher-level parameter resourcesForChannelMeasurement) is for channel measurements for L1-RSRP or for channel and interference measurements for L1-SINR calculation.

[0103] - When two resource settings are configured, the first resource setting (given by the higher-layer parameter resourcesForChannelMeasurement) is for channel measurement, and the second (given by the higher-layer parameter csi-IM-ResourcesForInterference or the higher-layer parameter nzp-CSI-RS-ResourcesForInterference) is for interference measurement performed on CSI-IM or NZP CSI-RS.

[0104] - When the three resource settings are configured, the first resource setting (the higher-layer parameter resourcesForChannelMeasurement) is used for channel measurement, the second (given by the higher-layer parameter csi-IM-ResourcesForInterference) is used for CSI-IM-based interference measurement, and the third (given by the higher-layer parameter nzp-CSI-RS-ResourcesForInterference) is used for NZP-CSI-RS-based interference measurement.

[0105] For non-periodic CSI, and for periodic and semi-static CSI resource settings, each trigger state configured using the higher-level parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, where a CSI-ReportConfig configured with groupBasedBeamReporting-r17 is linked to the periodic or semi-static setting:

[0106] - When configuring a resource setting, the resource setting is given by resourcesForChannelMeasurement for L1-RSRP measurements. In this case, the number of CSI resource sets configured in the resource setting is S=2.

[0107] For aperiodic CSI, and for aperiodic CSI resource settings, each trigger state configured using the higher-level parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, where a CSI-ReportConfig configured with groupBasedBeamReporting-r17 is associated with resourcesForChannel and resourcesForChannel2, which correspond to the first and second resource sets, respectively, for L1-RSRP measurements.

[0108] For semi-persistent or periodic CSI, each CSI-ReportConfig is linked to a periodic or semi-persistent resource setting:

[0109] - When a resource setting (given by the higher-level parameter resourcesForChannelMeasurement) is configured, the resource setting is for channel measurements for L1-RSRP or for channel and interference measurements for L1-SINR calculation.

[0110] When two resource settings are configured, the first resource setting (given by the higher-layer parameter resourcesForChannelMeasurement) is used for channel measurements, and the second resource setting (given by the higher-layer parameter csi-IM-ResourcesForInterference) is used for interference measurements performed on CSI-IM. For L1-SINR calculation, the second resource setting (given by either the higher-layer parameter csi-IM-ResourcesForInterference or the higher-layer parameter nzp-CSI-RS-ResourceForInterference) is used for interference measurements performed on CSI-IM or NZP CSI-RS.

[0111] …

[0112] 5.2.1.4.2 Report Quantity Configuration

[0113] The UE can be configured with CSI-ReportConfig, where the higher-level parameter reportQuantity is set to any of the following: 'none', 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', cri-RSRP', cri-SINR', ssb-Index-RSRP', ssb-Index-SINR', 'cri-RI-LI-PMI-CQI', cri-RSRP-Index', ssb-Index-RSRP-Index', cri-SINR-Index', or 'ssb-Index-SINR-Index'.

[0114] If the UE is configured with CSI-ReportConfig, and the higher-level parameter reportQuantity is set to 'none', then the UE will not report any quantity of CSI-ReportConfig.

[0115] …

[0116] If the UE is configured with CSI-ReportConfig, the higher-level parameter reportQuantity is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP-Index', or 'ssb-Index-RSRP-Index'.

[0117] - If the UE is configured with the higher-level parameter groupBasedBeamReporting set to 'disable', the UE does not need to update measurements for more than 64 CSI-RS and / or SSB resources, and the UE will report different CRIs or SSBRIs for each reporting setting in a single report nrofReportedRS (configured by the higher level).

[0118] - When the UE is configured with the higher-layer parameter groupBasedBeamReporting set to 'Enabled', the UE does not need to update measurements for more than 64 CSI-RS and / or SSB resources, and the UE will report two different CRIs or SSBRIs for each report setting in a single report instance, where the CSI-RS and / or SSB resources can be received simultaneously by the UE using a single spatial domain receive filter or multiple simultaneous spatial domain receive filters.

[0119] - If the UE is configured with the higher-level parameter groupBasedBeamReporting-r17, the UE does not need to update measurements of more than 64 CSI-RS and / or SSB resources, and the UE will report a group of two CRIs or SSBRIs selected from each of the two CSI resource sets for reporting settings in a single reporting instance nrofReportedGroups (if configured), where the CSI-RS and / or SSB resources of each group can be received by the UE simultaneously.

[0120] If the UE is configured with CSI-ReportConfig, the higher-level parameter reportQuantity is set to 'cri-SINR', 'ssb-Index-SINR', 'cri-SINR-Index', or 'ssb-Index-SINR-Index'.

[0121] - If the UE is configured to use the higher-level parameter groupBasedBeamReporting set to 'disable', then the UE will report a different CRI or SSBRI for each report setting in a single report nrofReportedRS (configured by the higher level).

[0122] - If the UE is configured to use the high-level parameter groupBasedBeamReporting set to 'Enabled', then the UE will report two different CRIs or SSBRIs for each reporting setting in a single reporting instance, where CSI-RS and / or SSB resources can be received by the UE simultaneously.

[0123] …

[0124] 5.2.1.4.3 L1-RSRP Report

[0125] For L1-RSRP calculation

[0126] - When used with 'Type C' and 'Type D' per-resource quasi-co-addressable as applicable, the UE can be configured with CSI-RS resources, SS / PBCH block resources, or CSI-RS and SS / PBCH block resources.

[0127] - The UE can be configured with CSI-RS resource settings of up to 16 CSI-RS resource sets, each set containing up to 64 resources. The total number of different CSI-RS resources across all resource sets shall not exceed 128.

[0128] For L1-RSRP reporting, if the higher-layer parameter nrofReportedRS in CSI-ReportConfig is configured to one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with a 1 dB step. If the higher-layer parameter nrofReportedRS is configured to be greater than one, or if the higher-layer parameter groupBasedBeamReporting is configured to 'enabled', or if the higher-layer parameter groupBasedBeamReporting-r17 is configured, the UE should use differential L1-RSRP reporting, where the maximum measured L1-RSRP value is quantized as a 7-bit value in the range [-140, -44] dBm with a 1 dB step, and the differential L1-RSRP is quantized as a 4-bit value. The differential L1-RSRP value is calculated with a 2 dB step, referencing the maximum measured L1-RSRP value that is part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP values ​​and the measured quantities is described in [11, TS 38.133].

[0129] When the higher-level parameter groupBasedBeamReporting-r17 in CSI-ReportConfig is configured, the UE should indicate the CSI resource set associated with the maximum measured value of L1-RSRP, and for each group, the CRI or SSBRI of the indicated CSI resource set should exist first.

[0130] If the higher-level parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Not Configured", the UE should derive channel measurements only based on the SS / PBCH or NZP CSI-RS (defined in TS 38.211[4]) associated with the CSI resource settings no later than the CSI reference resource for calculating the L1-RSRP value reported in uplink slot n.

[0131] If the higher-layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE should derive channel measurements for calculating the L1-RSRP reported in uplink slot n based solely on the most recent timing (defined in 4, TS 38.211) of the SS / PBCH or NZP CSI-RS associated with the CSI resource setting, which is no later than the CSI reference resource.

[0132] When the UE is configured with SSB-MTC-AdditionalPCI, the CSI-SSB-ResourceSet configured for L1-RSRP reporting contains an SSB index set and a PCI index set, where each SSB index is associated with a PCI index.

[0133] When a UE is configured with CSI-ReportConfig, where the higher-layer parameter reportQuantity is set to 'cri-RSRP-Index' or 'ssb-Index-RSRP-Index', the index of the set of UE capability values ​​indicating the maximum number of UE capability values ​​supported by the SRS antenna port is reported together with the pair of SSBRI / CRI and L1-RSRP.

[0134] 5.2.1.5 CSI Reporting and CSI-RS Triggering / Activation

[0135] 5.2.1.5.1 Non-periodic CSI reporting / non-periodic CSI-RS when triggering PDCCH and CSI-RS have the same underlying parameters

[0136] For a CSI-RS resource set associated with a resource setting configured with a higher-layer parameter `resourceType` set to 'aperiodic', 'periodic', or 'semi-persistent', the higher-layer parameter `CSI-AperiodicTriggerStateList` is used to configure the trigger state of the reporting settings (configured with a higher-layer parameter `reportConfigType` set to 'aperiodic') and / or resource settings for channel and / or interference measurements on one or more component carriers. For aperiodic CSI reporting triggers, a single set of CSI trigger states is configured by the higher layer, where a CSI trigger state can be associated with any candidate DL BWP. It is not expected that the UE will receive more than one DCI with a non-zero CSI request field per time slot per cell. It is not expected that the UE will receive a DCI with a non-zero CSI request field within the same cell group in a time slot that overlaps with any time slot in which a DCI with a non-zero CSI request field is received in the same cell group. It is not expected that the UE will have different TCI-StateIds configured for the same aperiodic CSI-RS resource ID in multiple aperiodic CSI-RS resource sets, where the same trigger offset exists in the same aperiodic trigger state. It is not expected that the UE will receive more than one aperiodic CSI report request per cell in a given time slot. It is not expected that the UE will receive aperiodic CSI report requests for transmission in time slots that overlap with any time slots in the same cell group that have aperiodic CSI report transmissions. If the UE does not indicate its capability CSITriggerStateContainingNonactiveBWP, it is not expected that the UE will trigger with a CSI report for an inactive DLBWP. Otherwise, when the UE triggers with a CSI report for an inactive DLBWP at the latest time when the associated NZP CSI-RS is expected to be received no later than the latest CSI reference resource, it is not expected that the UE will report a CSI for the inactive DLBWP and the CSI report associated with said BWP will be omitted. When the UE triggers an aperiodic NZP CSI-RS in an inactive DLBWP during the anticipated reception of NZP CSI-RS, the UE is not expected to measure the aperiodic CSI-RS. In the carrier of the serving cell where the associated NZP CSI-RS is anticipated to be received, if the active DLBWP during NZP CSI-RS reception differs from the active DLBWP during DCI reception triggering, then...

[0137] - The last symbol of the PDCCH span of the DCI carrying BWP handover should be no later than the last symbol of the PDCCH span of the DCI carrying CSI triggering, regardless of whether the two symbols are in the same carrier of the serving cell or in the same SCS.

[0138] - No other BWP handover is expected on the carrier after the last symbol of the PDCCH span covering the DCI triggered by the CSI and before the first symbol of the triggered NZPCSI-RS or CSI-IM.

[0139] - When the PDCCH reception contains two PDCCH candidates from two corresponding search space sets, as described in Clause 10.1 of [6, TS38.213], the span involving the PDCCH candidate that ends at a later time is used.

[0140] Use the CSI request field in DCI to initiate the trigger state.

[0141] …

[0142] 5.2.1.5.2 Semi-Persistent CSI / Semi-Persistent CSI-RS

[0143] For semi-static reporting on the PUSCH, a set of trigger states is configured at a higher level via CSI-SemiPersistentOnPUSCH-TriggerStateList, where one of the trigger states is activated in the DCI using a CSI request field scrambled with SP-CSI-RNTI. The UE is not expected to receive a DCI scrambled with SP-CSI-RNTI that activates a semi-static CSI report having the same CSI-ReportConfigId as a previously received semi-static CSI report activated by a DCI scrambled with SP-CSI-RNTI.

[0144] For semi-static reporting on PUCCH, the PUCCH resource used to transmit CSI reports is configured via reportConfigType. Semi-static reporting on PUCCH is activated by an activation command as described in Clause 6.1.3.16 of [10, TS 38.321], which selects one of the semi-static reporting settings for the UE to use on the PUCCH. When the UE will transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, the indicated semi-persistent reporting setting should be selected from the slot n. The application is applied in the first time slot thereafter, where μ is the SCS configuration for PUCCH.

[0145] For UEs configured with CSI resource settings where the higher-level parameter resourceType is set to 'semi-persistent'.

[0146] As described in Clause 6.1.3.12 of [10, TS 38.321], when the UE receives an activation command for the CSI-RS resource set for channel measurement and the CSI-IM / NZP CSI-RS resource set for interference measurement associated with the configured CSI resource settings, and when the UE transmits a PUCCH with HARQ-ACK information in slot n of the PDSCH corresponding to the bearer selection command, the corresponding actions in [10, TS 38.321] and the UE assumptions (including QCL assumptions provided by the reference list of TCI-State, one for each activated resource) corresponding to the CSI-RS / CSI-IM transmission of the configured CSI-RS / CSI-IM resource settings should be generated from the slot n. The first time slot thereafter is used, where μ is the SCS configuration for PUCCH, and It is used for k mac The subcarrier spacing configuration has a value of 0 for frequency range 1, and k mac Provided by K-Mac, or if K-Mac is not provided, then k mac =0. If the TCI-State mentioned in the list refers to an RS configuration configured with qcl-Type set to 'Type D', then the RS can be an SS / PBCH block, a periodic or semi-persistent CSI-RS located in the same or different CC / DL BWPs.

[0147] - As described in Clause 6.1.3.12 of [10, TS 38.321], when the UE receives a deactivation command for an activated CSI-RS / CSI-IM resource set associated with a configured CSI resource setting, and when the UE will transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the deactivation command, the corresponding actions in [10, TS 38.321] and the UE assuming that the CSI-RS / CSI-IM transmission corresponding to the deactivated CSI-RS / CSI-IM resource set should stop in slot n are assumed to be from the time slot. The first time slot thereafter is used, where μ is the SCS configuration for PUCCH, and It is used for k mac The subcarrier spacing configuration has a value of 0 for frequency range 1, and k mac Provided by K-Mac, or if K-Mac is not provided, then k mac =0.

[0148] …

[0149] In [3] 3GPP 38.321 v17.4.0, scheduling requests, MAC resets, beam activation for channel TCI state activation MAC CE, and BFR MAC CE are described:

[0150] 5.4.4 Scheduling Request

[0151] A scheduling request (SR) is used to request UL-SCH resources for a new transfer.

[0152] A MAC entity can be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For logical channels, or for SCell beam fault recovery (see Section 5.17) and for consistency LBT fault recovery (see Section 5.21), at most one PUCCH resource is configured per BWP for SR. For logical channels serving radio bearers configured with SDTs, no PUCCH resources for SR are configured for the SDTs. For beam fault recovery of the BFD-RS set serving a cell, at most two PUCCH resources are configured per BWP for SR. A dedicated SR configuration is configured for location measurement gap activation / deactivation requests.

[0153] Each SR configuration corresponds to one or more logical channels and / or SCell beam fault recovery and / or consistent LBT fault recovery and / or BFD-RS set beam fault recovery and / or positioning measurement gap activation / deactivation requests. Each logical channel, SCell beam fault recovery, BFD-RS set beam fault recovery, and consistent LBT fault recovery can be mapped to a zero or one SR configuration configured by RRC. The SR configuration of the logical channel that triggers a BSR (clause 5.4.5) or SCell beam fault recovery or BFD-RS set beam fault recovery or consistent LBT fault recovery (clause 5.21) (if this configuration exists) or positioning measurement gap activation / deactivation request (clause 5.25) is considered the corresponding SR configuration used for the triggered SR. Any SR configuration can be used for an SR triggered by a preemptive BSR (clause 5.4.7) or timing advance reporting (clause 5.4.8).

[0154] RRC configures the following parameters for the scheduling request program:

[0155] -sr-ProhibitTimer (based on SR configuration);

[0156] -sr-TransMax (based on SR configuration).

[0157] The following UE variables are used in the scheduling request procedure:

[0158] -SR_COUNTER (based on SR configuration).

[0159] If an SR is triggered and there are no other pending SRs corresponding to the same SR configuration, the MAC entity sets the SR_COUNTER of the corresponding SR configuration to 0.

[0160] When an SR is triggered, it will be considered pending until it is canceled.

[0161] …

[0162] As long as at least one SR is pending, for each pending SR, the MAC entity will:

[0163] 1> If the MAC entity is not configured with a valid PUCCH resource for pending SRs:

[0164] 2> Initiate a random access procedure on SpCell (see Clause 5.1) and cancel the pending SR.

[0165] 1> Otherwise, for the SR configuration corresponding to the undetermined SR:

[0166] 2> When the MAC entity has an SR transmission opportunity on a valid PUCCH resource for the configured SR; and

[0167] 2> If sr-ProhibitTimer is not running during the SR transmission timing; and

[0168] 2> If the PUCCH resource used for SR transmission timing does not overlap with the measurement gap:

[0169] …

[0170] 4> Treat SR transfers as priority SR transfers.

[0171] 4> Treat other overlapping uplink grants (if they exist) as de-prioritized uplink grants, except for overlapping uplink grants that are allowed to be transmitted simultaneously by the configuration of simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, or simultaneousSR-PUSCH-diffPUCCH-Groups.

[0172] 4> If de-prioritizing uplink granting is a configured uplink granting that has started its PUSCH and is configured with autonomousTx:

[0173] 5> Stop the configuredGrantTimer used for the corresponding HARQ procedure to de-prioritize uplink grants;

[0174] 5> Stop the cg-RetransmissionTimer used for the corresponding HARQ procedure to de-prioritize uplink grants.

[0175] 4> If SR_COUNTER <sr-TransMax:

[0176] 5> Instruct the physical layer to send the SR on a valid PUCCH resource used for the SR;

[0177] 5> If no LBT fault indication is received from the lower layer:

[0178] 6> Increment SR_COUNTER by 1;

[0179] 6> Start sr-ProhibitTimer.

[0180] 5> Otherwise, if lbt-FailureRecoveryConfig is not configured:

[0181] 6> Increment SR_COUNTER by 1.

[0182] 4> Otherwise:

[0183] 5> Notify RRC to release PUCCHs used for all serving cells;

[0184] 5> Notify RRC to release SRS for all serving cells;

[0185] 5> Clear any configured downlink assignments and uplink permissions;

[0186] 5> Remove any PUSCH resources used for semi-persistent CSI reporting;

[0187] 5> Initiate a random access procedure on SpCell (see Clause 5.1) and cancel all pending SRs.

[0188] 5.12 MAC Reset

[0189] If a MAC entity is reset by a request from an upper layer or by a reactivation of an SCG as defined in Clause 5.29, the MAC entity shall:

[0190] 1> If the MAC reset is not due to SCG reactivation:

[0191] 2> Initialize Bj of each logical channel to zero;

[0192] 1> When configuring sidelink resource allocation mode 1 via RRC, initialize SBj for each logical channel to zero;

[0193] 1> If the upper layer instructs the SCG to be deactivated and the configuration for the deactivated SCG has a true value for bfd-and-RLM:

[0194] 2> Stop (if running) all timers except beamFailureDetectionTimer and timeAlignmentTimers associated with PSCell.

[0195] 1> Otherwise:

[0196] 2> Stop (if running) all timers, except for the MBS broadcast DRX timer;

[0197] 2> Treat all timeAlignmentTimers, inactivePosSRS-timeAlignmentTimer, and cg-SDT-TimeAlignmentTimer (if configured) as expired and perform the corresponding actions in clause 5.2;

[0198] 1> Set the NDI of all uplink HARQ processes to a value of 0;

[0199] 1> Set the NDI of all HARQ process IDs to the value 0 to monitor PDCCH in sidelink resource allocation mode 1;

[0200] 1> Stop (if any) the ongoing random access procedure;

[0201] 1> For 4-step RA type and 2-step RA type, discard explicitly delivered contention-free random access resources (if they exist);

[0202] 1> Clear the Msg3 buffer;

[0203] 1> Clear the MSGA buffer;

[0204] 1> Cancel (if any) the triggered scheduling request procedure;

[0205] 1> Cancel (if it exists) the triggered buffer status reporting procedure;

[0206] 1> Cancel (if it exists) the triggered power margin reporting procedure;

[0207] 1> Cancel (if any) the triggered consistent LBT fault;

[0208] 1> Cancel (if it exists) the triggered BFR;

[0209] 1> Cancel (if present) the triggered sidelink buffer status reporting procedure;

[0210] 1> Cancel (if it exists) the triggered preemptive buffer status reporting procedure;

[0211] 1> Cancel (if any) the advance reporting procedure for when it is triggered;

[0212] 1> Cancel (if present) the triggered recommended bit rate query procedure;

[0213] 1> Cancel (if any) the configured uplink grant confirmation triggered;

[0214] 1> Cancel (if any) the configured sidelink grant confirmation triggered;

[0215] 1> Cancel (if present) the triggered query for the required protection symbol;

[0216] 1> Cancel (if any) the triggered positioning measurement gap activation / revoke activation request procedure;

[0217] 1> Cancel (if it exists) the triggered SDT procedure;

[0218] 1> Clear the soft buffer used by all DL HARQ processes, except for DL ​​HARQ processes that are being used for MBS broadcasts;

[0219] 1> For each DL HARQ process other than the one that is being used for MBS broadcasting, the next received transmission for TB shall be regarded as the first transmission.

[0220] 1> Release (if present) the temporary C-RNTI;

[0221] 1> If the upper layer instructs SCG to revoke activation and no bfd-and-RLM with a true value is configured; or

[0222] 1> If the MAC reset is not due to SCG reactivation:

[0223] 2> Reset all BFI_COUNTERs;

[0224] 1> Reset all LBT_COUNTERs.

[0225] …

[0226] 5.18.4 Activation / Deactivation of UE-Specific PDSCH TCI Status

[0227] The network can activate and deactivate the configured TCI state of the serving cell or a set of serving cells configured in simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 by sending the TCI state activation / deactivation of the UE-specific PDSCH MAC CE as described in Clause 6.1.3.14. The network can activate and deactivate the configured TCI state of the serving cell's PDSCH as specified in the code point of the DCI transmission configuration indication field in TS 38.212[9] as described in Clause 6.1.3.24 for the enhanced TCI state activation / deactivation of the UE-specific PDSCH MAC CE. The configured TCI state of the PDSCH is initially deactivated when (re)configured by the upper layer and after a reconfiguration with synchronization.

[0228] MAC entities will:

[0229] 1> When the MAC entity receives a UE-specific PDSCH MAC CE TCI state activation / deactivation on the serving cell:

[0230] 2> Indicate information to the lower layer regarding the activation / deactivation of the TCI status of the UE-specific PDSCH MAC CE.

[0231] 1> When the MAC entity receives an enhanced TCI state activation / deactivation from a UE-specific PDSCH MAC CE on the serving cell:

[0232] 2> Indicate information to the lower layer regarding the activation / deactivation of the enhanced TCI state for the UE-specific PDSCH MAC CE.

[0233] 5.18.5 Indication of TCI status for UE-specific PDCCH

[0234] The network can indicate the TCI status of PDCCH reception for a serving cell or a core set of serving cells configured in simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 by sending a TCI status indication for a UE-specific PDCCH MAC CE as described in Clause 6.1.3.15. The network can also indicate both TCI statuses for PDCCH reception for a serving cell or a core set of serving cells configured in simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 by sending an enhanced TCI status indication for a UE-specific PDCCH MAC CE as described in Clause 6.1.3.44.

[0235] MAC entities will:

[0236] 1> If the MAC entity receives a TCI status indication from a UE-specific PDCCH MAC CE on the serving cell:

[0237] 2> Indicate information about the TCI status indication of the UE-specific PDCCH MAC CE to the lower layer.

[0238] 1> If the MAC entity receives an enhanced TCI status indication for a UE-specific PDSCH MAC CE on the serving cell:

[0239] 2> Indicate information about the enhanced TCI status indication of the UE-specific PDSCH MAC CE to the lower layer.

[0240] 5.18.8 Activation / Deactivation of Spatial Relationships of PUCCH Resources

[0241] The network can activate and deactivate the spatial relationship of the serving cell's PUCCH resources by sending the PUCCH spatial relationship activation / deactivation MAC CE described in Section 6.1.3.18. The network can also activate and deactivate the spatial relationship of the serving cell's PUCCH resources or PUCCH resource groups by sending the enhanced PUCCH spatial relationship activation / deactivation MAC CE described in Section 6.1.3.25. The configured spatial relationship activating the PUCCH resources is deactivated first during (re)configuration by the upper layer and after synchronization following reconfiguration. The network can also activate and deactivate two spatial relationships activating the serving cell's PUCCH resources or PUCCH resource groups by sending the PUCCH spatial relationship activation / deactivation for multiple TRPPUCCH repeated MAC CEs described in Section 6.1.3.45.

[0242] MAC entities will:

[0243] 1> If a MAC entity receives a PUCCH spatial relationship activation / deactivation MAC CE on the serving cell, then:

[0244] 2> Instruct the lower layer about information regarding the activation / deactivation of the MAC CE in the PUCCH spatial relationship.

[0245] 1> If a MAC entity receives enhanced PUCCH spatial relationship activation / deactivation of MAC CE on the serving cell, then:

[0246] 2> Instruct the lower layer about information regarding the activation / deactivation of the enhanced PUCCH spatial relationship MAC CE.

[0247] 1> If a MAC entity receives a PUCCH spatial relationship activation / deactivation for multiple TRP PUCCH duplicate MAC CEs on the serving cell:

[0248] 2> Instruct the lower layer about the activation / deactivation information of the PUCCH spatial relationship for multiple TRP PUCCH repeating MAC CE.

[0249] …

[0250] 5.18.23 Unified TCI Status Activation / Deactivation MAC CE

[0251] The network can activate and deactivate the configured unified TCI state of a serving cell or a set of serving cells configured in simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 by sending the unified TCI state activation / deactivation MAC CE described in Clause 6.1.3.47. Initial deactivation of the configured unified TCI state occurs during (re)configuration by the upper layer and after a synchronized reconfiguration.

[0252] MAC entities will:

[0253] 1> If the MAC entity receives a unified TCI status activation / deactivation MAC CE on the serving cell:

[0254] 2> Instruct the lower layer about information regarding the activation / deactivation of the unified TCI status MAC CE.

[0255] 6.1.3.23 BFR MAC CE

[0256] The MAC CE for BFR consists of the following:

[0257] -BFR MAC CE; or

[0258] - Truncation of BFR MAC CE.

[0259] BFR MAC CE and truncated BFR MAC CE are identified by a MAC subheader with LCID / eLCID, as specified in Tables 6.2.1-2 and 6.2.1-2b.

[0260] The BFR MAC CE and the truncated BFR MAC CE are of variable size. They contain a bitmap and contain beam fault recovery information in ascending order based on ServCellIndex, i.e., an octet of bits for the candidate beam availability indication (AC) of the SCell indicated in the bitmap. For the BFR MAC CE, a single octet bitmap is used when a beam fault is detected and the highest ServCellIndex of the SCell of this MAC entity is less than 8, as required by TS 38.133

[11] , otherwise four octets are used. The MAC PDU should contain at most one BFR MAC CE.

[0261] For truncated BFR MAC CE, a single octet bitmap is used in the following cases; otherwise, four octets are used:

[0262] - The highest ServCellIndex of the SCell of the MAC entity for which a beam fault has been detected and the evaluation of the candidate beams as required by TS 38.133

[11] has been completed is less than 8; or

[0263] - If a beam fault is detected in the SpCell (as specified in Section 5.17), the SpCell will indicate in the truncated BFR MACCE that the available UL-SCH resources for transmission cannot accommodate a truncated BFR MACCE with four octet bitmaps plus their subheaders as the LCP result.

[0264] The field definitions in BFR MAC CE are as follows:

[0265] -SP: This field indicates beam fault detection of the SpCell for this MAC entity (as specified in Clause 5.17). The SP field is set to 1 only if the BFR MAC CE or a truncated BFR MAC CE is included in the MAC PDU as part of the random access procedure, indicating that a beam fault of the SpCell has been detected (as specified in 5.1.3a and 5.1.4); otherwise, it is set to 0.

[0266] -C i (BFR MAC CE): This field indicates the presence of beam fault detection (as specified in Clause 5.17) and an octet containing the AC field for a SCell having ServCellIndex i as specified in TS 38.331[5]. C set to 1 i The field indicates that a beam fault has been detected, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, and an octet containing the AC field exists for the SCell with ServCellIndex i. The C field is set to 0. i The field indicates that no beam fault was detected, or that a beam fault was detected but the evaluation of the candidate beams as required by TS 38.133

[11] has not been completed, and there is no octet containing the AC field for the SCell with ServCellIndex i. An octet containing the AC field exists in ascending order based on ServCellIndex;

[0267] -C i (Truncation BFR MAC CE): This field indicates beam fault detection for SCells with ServCellIndex i as specified in TS 38.331[5] (as specified in Clause 5.17). C set to 1 i The field indicates that a beam fault has been detected, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, and an octet containing the AC field can exist for the SCell with ServCellIndex i. C is set to 0. i The field indicates that no beam fault was detected, or a beam fault was detected but the evaluation of the candidate beam according to the requirements specified in TS 38.133

[11] has not been completed, and there is no octet containing the AC field for the SCell with ServCellIndex i. Include octets containing the AC field (if present) in ascending order based on ServCellIndex. Maximize the number of included octets containing the AC field while not exceeding the available allowable size;

[0268] Note: The number of octets containing the AC field in the truncated BFR MAC CE can be zero.

[0269] -AC: This field indicates the presence of the candidate RS ID field in this octet. The AC field is set to 1 if at least one of the SSBs in candidateBeamRSSCellList with an SS-RSRP higher than rsrp-ThresholdBFR or a CSI-RS in candidateBeamRSSCellList with a CSI-RSRP higher than rsrp-ThresholdBFR is available; otherwise, it is set to 0. If the AC field is set to 1, the candidate RS ID field exists. If the AC field is set to 0, R bits actually exist.

[0270] - Candidate RS ID: This field is set to the index of the SSB in the candidateBeamRSSCellList that has an SS-RSRP higher than rsrp-ThresholdBFR, or the index of the CSI-RS in the candidateBeamRSSCellList that has a CSI-RSRP higher than rsrp-ThresholdBFR. The SSB or CSI-RS index corresponds to the index of the entry in the candidateBeamRSSCellList for that SSB or CSI-RS. Index 0 corresponds to the first entry in the candidateBeamRSSCellList, index 1 corresponds to the second entry in the list, and so on. This field is 6 bits long.

[0271] Figure 5 It is in 3GPP 38.321v17.4.0 Figure 6 1.3.23-1: BFR and C with one octet i Reproduction of the truncated BFR MAC CE field.

[0272] Figure 6 It is in 3GPP 38.321v17.4.0 Figure 6 1.3.23-2: BFR and C with four octets i Reproduction of the truncated BFR MAC CE field.

[0273] In [4] 3GPP 38.331v17.4.0, the measurement report triggering and associated configurations are described:

[0274] 5.5.4 Measurement Report Trigger

[0275] 5.5.4.1 Overview

[0276] If AS security has been successfully activated, then the UE should:

[0277] 1> For each measId in the measIdList contained within VarMeasConfig:

[0278] 2> If the corresponding reportConfig contains a reportType set to eventTriggered or periodic:

[0279] 3> If the corresponding measObject involves NR:

[0280] 4> If the corresponding reportConfig contains measRSSI-ReportConfig:

[0281] 5> Treat the resources indicated by rmtc-Config on the associated frequency as applicable;

[0282] 4> If eventA1 or eventA2 is configured in the corresponding reportConfig:

[0283] 5> Only the service area is considered applicable;

[0284] 4> If eventA3 or eventA5 is configured in the corresponding reportConfig:

[0285] 5> If a serving cell is associated with a measObjectNR and its neighbor is associated with another measObjectNR, then any serving cell associated with the other measObjectNR will also be considered a neighboring cell;

[0286] 4> If eventX2 is configured in the corresponding reportConfig:

[0287] 5> Only L2 U2N relay UEs are considered applicable;

[0288] 4> If the corresponding reportConfig contains a reportType that is set to periodicity; or

[0289] 4> For measurement events other than eventA1, eventA2, eventD1, or eventX2:

[0290] 5> If useAllowedCellList is set to true:

[0291] 6> When the cell involved is included in allowedCellsToAddModList defined for this measId in VarMeasConfig, any neighboring cells detected based on the parameters in the associated measObjectNR will be considered applicable;

[0292] 5> Otherwise:

[0293] 6> When the cell involved is not included in the excludedCellsToAddModList defined for this measId in VarMeasConfig, any neighboring cells detected based on the parameters in the associated measObjectNR will be considered applicable;

[0294] …

[0295] 2> Otherwise, if the corresponding reportConfig contains a reportType set to reportCGI:

[0296] 3> The cells detected on the associated measObject are considered applicable, and the cells have physical cell identities that match the values ​​of cellForWhichToReportCGI contained in the corresponding reportConfig within VarMeasConfig;

[0297] 2> Otherwise, if the corresponding reportConfig contains a reportType set to reportSFTD:

[0298] 3> If the corresponding measObject involves NR:

[0299] 4> If reportSFTD-Meas is set to true:

[0300] 5> Treat NR PSCell as applicable;

[0301] 4> Otherwise, if reportSFTD-NeighMeas is included:

[0302] 5> If cellsForWhichToReportSFTD is configured in the corresponding reportConfig:

[0303] 6> Any NR neighboring cell detected on the associated measObjectNR that has a physical cell identity included in cellsForWhichToReportSFTD will be considered applicable;

[0304] 5> Otherwise:

[0305] 6> When the cell in question is not included in the excludedCellsToAddModList defined in the VarMeasConfig for this measId, the up to 3 strongest NR adjacent cells detected based on the parameters in the associated measObjectNR will be considered applicable;

[0306] …

[0307] 2> If reportType is set to eventTriggered and if applicable to this event, that is, the entry conditions for the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig are met for one or more applicable cells for all measurements after Layer 3 filtering performed during the timeToTrigger period defined for this event in VarMeasConfig, and VarMeasReportList does not contain a measurement report entry for this measId (first cell triggered event):

[0308] 3> Includes measurement report entries within the VarMeasReportList for this measId;

[0309] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0310] 3> The cells involved are included in the cellsTriggeredList defined for this measId within VarMeasReportList;

[0311] …

[0312] 3> Initiate the measurement reporting procedure as specified in 5.5.5;

[0313] 2> Otherwise, if reportType is set to eventTriggered and if applicable to this event, i.e., the entry condition for the event corresponding to the eventId of the corresponding reportConfig within VarMeasConfig is satisfied for one or more applicable cells not included in cellsTriggeredList for all measurements after Layer 3 filtering performed during the timeToTrigger period defined for this event within VarMeasConfig (subsequent cell triggering event):

[0314] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0315] 3> The cells involved are included in the cellsTriggeredList defined for this measId within VarMeasReportList;

[0316] …

[0317] 3> Initiate the measurement reporting procedure as specified in 5.5.5;

[0318] …

[0319] 2> Otherwise, if reportType is set to eventTriggered and if applicable to this event, i.e., the entry conditions for the event corresponding to the eventId of the corresponding reportConfig within VarMeasConfig are met for one or more applicable transport resource pools for all measurements performed during the timeToTrigger period defined for this event within VarMeasConfig, and VarMeasReportList does not contain a measurement report entry for this measId (first transport resource pool triggered event):

[0320] 3> Includes measurement report entries within the VarMeasReportList for this measId;

[0321] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0322] 3> The poolsTriggeredList defined within the VarMeasReportList used for this measId contains the transport resource pools involved.

[0323] 3> Initiate the measurement reporting procedure as specified in 5.5.5;

[0324] 2> Otherwise, if reportType is set to eventTriggered and if applicable to this event, i.e., the entry condition for the event corresponding to the eventId of the corresponding reportConfig within VarMeasConfig is satisfied for one or more applicable transport resource pools not included in poolsTriggeredList for all measurements performed during the timeToTrigger period defined for this event within VarMeasConfig (subsequent transport resource pool triggers the event):

[0325] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0326] 3> The poolsTriggeredList defined within the VarMeasReportList used for this measId contains the transport resource pools involved.

[0327] 3> Initiate the measurement reporting procedure as specified in 5.5.5;

[0328] 2> If reportType is set to eventTriggered and if all measurements taken during the timeToTrigger period defined for this event in VarMeasConfig satisfy the departure conditions applicable to this event for one or more applicable transport resource pools in poolsTriggeredList defined for this measId within VarMeasReportList:

[0329] 3> Remove the involved transport resource pool from the poolsTriggeredList defined within the VarMeasReportList used for this measId;

[0330] 3> If the poolsTriggeredList defined for this measId in VarMeasReportList is empty:

[0331] 4> Remove the measurement report entry from the VarMeasReportList used for this measId;

[0332] 4> If it is running, stop the periodic reporting timer used for this measId.

[0333] …

[0334] 2> If reportType is set to periodic and (first) measurement results are available:

[0335] 3> Includes measurement report entries within the VarMeasReportList for this measId;

[0336] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0337] 3> If the corresponding reportConfig contains measRSSI-ReportConfig:

[0338] 4> When the physical layer reports the RSSI sample value after the first L1 measurement duration, immediately initiate the measurement reporting procedure as specified in 5.5.5;

[0339] 3> Otherwise, if the corresponding reportConfig contains ul-DelayValueConfig:

[0340] 4> Immediately after providing the first measurement result from the lower layer of the associated DRB identity, initiate the measurement reporting procedure as specified in 5.5.5;

[0341] 3> Otherwise, if the corresponding reportConfig contains ul-ExcessDelayConfig:

[0342] 4> Immediately after providing the first measurement result from the lower layer of the associated DRB identity based on the configured threshold for each DRB identity, initiate a measurement reporting procedure as specified in 5.5.5;

[0343] 3> Otherwise, if reportAmount exceeds 1:

[0344] 4> Immediately after the quantity to be reported becomes available for use in NR SpCell or for serving L2 U2N relay UE (if the UE is an L2 U2N remote UE), initiate a measurement reporting procedure as specified in 5.5.5;

[0345] 3> Otherwise (i.e., reportAmount equals 1):

[0346] 4> Immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or for the NR SpCell and for the strongest L2 U2N relay UE among the applicable L2 U2N relay UEs, a measurement reporting procedure shall be initiated as specified in 5.5.5; or immediately after the quantity to be reported becomes available for the serving L2 U2N relay UE and for the strongest cell among the applicable cells (if the UE is an L2 U2N remote UE), a measurement reporting procedure shall be initiated as specified in 5.5.5;

[0347] …

[0348] 2> If reportType is set to rxTxPeriodical and if (first) measurement results are available:

[0349] 3> Includes measurement report entries within the VarMeasReportList for this measId;

[0350] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0351] 3> Initiate the measurement reporting procedure as specified in 5.5.5;

[0352] 2> After the periodic reporting timer used for this measId expires:

[0353] 3> Initiate a measurement reporting procedure as specified in 5.5.5.

[0354] 2> If the corresponding reportConfig contains a reportType set to reportSFTD:

[0355] 3> If the corresponding measObject involves NR:

[0356] 4> If drx-SFTD-NeighMeas is included:

[0357] 5> If the amount to be reported becomes available for each requested pair of PCells and NR cells:

[0358] 6> Stop timer T322;

[0359] 6> Initiate the measurement reporting procedure as specified in 5.5.5;

[0360] 4> Otherwise

[0361] 5> As specified in 5.5.5, the measurement reporting procedure shall be initiated immediately after the quantity to be reported becomes available for each pair of PCells and NR cells requested or the maximum measurement reporting delay specified in TS 38.133

[14] ;

[0362] …

[0363] 2> If reportType is set to reportCGI:

[0364] 3> If the UE obtains SIB1 or SystemInformationBlockType1 for the requested cell; or

[0365] 3> If the UE detects that the requested NR cell is not transmitting SIB1 (see TS 38.213

[13] , Clause 13):

[0366] 4> Stop timer T321;

[0367] 4> Includes measurement report entries within the VarMeasReportList for this measId;

[0368] 4> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0369] 4> Initiate the measurement reporting procedure as specified in 5.5.5;

[0370] 2> After the T321 used for this measId expires:

[0371] 3> Includes measurement report entries within the VarMeasReportList for this measId;

[0372] 3> Set the numberOfReportsSent defined for this measId in VarMeasReportList to 0;

[0373] 3> Initiate a measurement reporting procedure as specified in 5.5.5.

[0374] 2> After the T322 used for this measId expires:

[0375] 3> Initiate a measurement reporting procedure as specified in 5.5.5.

[0376] 5.5.4.2 Event A1 (Service becomes better than threshold)

[0377] UE should:

[0378] 1> When the condition A1-1 specified below is met, the entry condition for this event is considered to be met;

[0379] 1> When the conditions A1-2 specified below are met, the exit condition for this event is considered to be met;

[0380] 1> For this measurement, consider the NR serving cell corresponding to the associated measObjectNR associated with this event.

[0381] Inequality A1-1 (Entry Condition)

[0382] Ms-Hys>Thresh

[0383] Inequality A1-2 (without conditions)

[0384] Ms+Hys <Thresh

[0385] The variables in the formula are defined as follows:

[0386] Ms is the measurement result of the serving cell, without considering any offset.

[0387] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0388] Thresh is the threshold parameter for this event (i.e., a1-Threshold as defined in reportConfigNR for this event).

[0389] Ms is represented by dBm in the case of RSRP, or by dB in the cases of RSRQ and RS-SINR.

[0390] Hys is represented in dB.

[0391] Thresh is expressed in the same units as Ms.

[0392] 5.5.4.3 Event A2 (Service deteriorates below threshold)

[0393] UE should:

[0394] 1> The entry condition for this event is considered to be met when the following specified condition A2-1 is satisfied;

[0395] 1> When condition A2-2 specified below is met, the exit condition for this event is considered to be met;

[0396] 1> For this measurement, consider the serving cell indicated by the measObjectNR associated with this event.

[0397] Inequality A2-1 (Entry Condition)

[0398] Ms+Hys <Thresh

[0399] Inequality A2-2 (leaving the condition)

[0400] Ms-Hys>Thresh

[0401] The variables in the formula are defined as follows:

[0402] Ms is the measurement result of the serving cell, without considering any offset.

[0403] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0404] Thresh is the threshold parameter for this event (i.e., a2-Threshold as defined in reportConfigNR for this event).

[0405] Ms is represented by dBm in the case of RSRP, or by dB in the cases of RSRQ and RS-SINR.

[0406] Hys is represented in dB.

[0407] Thresh is expressed in the same units as Ms.

[0408] 5.5.4.4 Event A3 (Neighbors become offset better than SpCell)

[0409] UE should:

[0410] 1> When condition A3-1 specified below is met, the entry condition for this event is considered to be met;

[0411] 1> When condition A3-2 specified below is met, the exit condition for this event is considered to be met;

[0412] 1> Use SpCell for Mp, Ofp, and Ocp.

[0413] Note 1: The cell that triggers the event has a reference signal indicated in the measObjectNR associated with this event, which may be different from NR SpCell measObjectNR.

[0414] Inequality A3-1 (Entry Condition)

[0415] Mn+Ofn+Ocn-Hys>Mp+Ofp+Ocp+Off

[0416] Inequality A3-2 (leaving the condition)

[0417] Mn+Ofn+Ocn+Hys <Mp+Ofp+Ocp+Off

[0418] The variables in the formula are defined as follows:

[0419] Mn is the measurement result of neighboring cells, without considering any offset.

[0420] Ofn is the measurement object-specific offset of the reference signal of the neighboring cell (i.e., the offset MO defined within the measObjectNR of the neighboring cell).

[0421] Ocn is the cell-specific offset of the neighboring cell (i.e., cellIndividualOffset corresponding to the frequency of the neighboring cell, as defined in measObjectNR), and is set to zero if no neighboring cell is configured.

[0422] Mp is the measurement result from SpCell, without considering any offset.

[0423] Ofp is the measurement object-specific offset of SpCell (i.e., the offset MO bounded within the measObjectNR of SpCell).

[0424] Ocp is the cell-specific offset of the SpCell (i.e., the cellIndividualOffset defined within the measObjectNR of the SpCell), and is set to zero if not configured for the SpCell.

[0425] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0426] Off is the offset parameter for this event (i.e., a3-Offset as defined in reportConfigNR for this event).

[0427] Mn and Mp are represented in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0428] Ofn, Ocn, Ofp, Ocp, Hys, and Off are represented in dB.

[0429] Note 2: The definition of event A3 also applies to CondEvent A3.

[0430] 5.5.4.5 Event A4 (Neighbors become better than the threshold)

[0431] UE should:

[0432] 1> When the condition A4-1 specified below is met, the entry condition for this event is considered to be met;

[0433] 1> When the condition A4-2 specified below is met, the exit condition for this event is considered to be met.

[0434] Inequality A4-1 (Entry Condition)

[0435] Mn+Ofn+Ocn-Hys>Thresh

[0436] Inequality A4-2 (Leaving the condition)

[0437] Mn+Ofn+Ocn+Hys <Thresh

[0438] The variables in the formula are defined as follows:

[0439] Mn is the measurement result of neighboring cells, without considering any offset.

[0440] Ofn is the measurement object-specific offset of the neighboring cell (i.e., the offset MO defined within the measObjectNR of the neighboring cell).

[0441] Ocn is the measurement object-specific offset of the neighboring cell (i.e., the cellIndividualOffset corresponding to the neighboring cell as defined in measObjectNR), and is set to zero if no neighboring cell is configured.

[0442] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0443] Thresh is the threshold parameter for this event (i.e., a4-Threshold as defined in reportConfigNR for this event).

[0444] Mn is expressed in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0445] Ofn, Ocn, and Hys are represented in dB.

[0446] Thresh is expressed in the same units as Mn.

[0447] Note: The definition of event A4 also applies to CondEvent A4.

[0448] 5.5.4.6 Event A5 (SpCell becomes worse than threshold1 and its neighbor becomes better than threshold2)

[0449] UE should:

[0450] 1> The entry conditions for this event are considered met when the specified conditions A5-1 and A5-2 are satisfied;

[0451] 1> The exit condition for this event is considered to be satisfied when either condition A5-3 or condition A5-4 is met, i.e., at least one of the two conditions is satisfied.

[0452] 1> Use SpCell for Mp.

[0453] Note 1: The parameters of the reference signal of the cell that triggered the event are indicated in the measObjectNR associated with the event, which may be different from the measObjectNR of NR SpCell.

[0454] Inequality A5-1 (Entry condition 1)

[0455] Mp+Hys <Thresh1

[0456] Inequality A5-2 (entering condition 2)

[0457] Mn+Ofn+Ocn-Hys>Thresh2

[0458] Inequality A5-3 (Away from condition 1)

[0459] Mp-Hys>Thresh1

[0460] Inequality A5-4 (leaving condition 2)

[0461] Mn+Ofn+Ocn+Hys <Thresh2

[0462] The variables in the formula are defined as follows:

[0463] Mp is the measurement result of NR SpCell, without considering any offset.

[0464] Mn is the measurement result of neighboring cells, without considering any offset.

[0465] Ofn is the measurement object-specific offset of the neighboring cell (i.e., the offset MO defined within the measObjectNR of the neighboring cell).

[0466] Ocn is the cell-specific offset of the neighboring cell (i.e., the cellIndividualOffset corresponding to the neighboring cell as defined in measObjectNR), and is set to zero if no neighboring cell is configured.

[0467] Hys is the hysteresis parameter for this event (i.e., the hysteresis as defined in reportConfigNR for this event).

[0468] Thresh1 is the threshold parameter for this event (i.e., a5-Threshold1 as defined in reportConfigNR for this event).

[0469] Thresh2 is the threshold parameter for this event (i.e., a5-Threshold2 as defined in reportConfigNR for this event).

[0470] Mn and Mp are represented in dBm in the case of RSRP, or in dB in the cases of RSRQ and RS-SINR.

[0471] Ofn, Ocn, and Hys are represented in dB.

[0472] Thresh1 is represented in the same units as Mp.

[0473] Thresh2 is expressed in the same units as Mn.

[0474] …

[0475] -PDSCH-Config

[0476] The PDSCH-Config IE is used to configure UE-specific PDSCH parameters. …

[0477] PDSCH-Config information element

[0478]

[0479] …

[0480]

[0481] -ControlResourceSet

[0482] The IE ControlResourceSet is used to configure the time / frequency control resource set (CORESET) in which downlink control information is searched (see TS 38.213

[13] , section 10.1). For UEs that do not support multipleCORESET in FR1, in order to receive MBS multicast in CFR within the UE's active BWP, if CORESET is not configured in PDCCH-ConfigMulticast, then CORESET other than CORESET#0 configured in the UE's active BWP for scheduling unicast can be used to schedule MBS multicast, and the CORESET is expected to be fully contained in CFR, and the parameters configured in the CORESET are expected to be supported by the UE for MBS multicast.

[0483] ControlResourceSet information element

[0484]

[0485]

[0486]

[0487] -BWP-UplinkDedicated

[0488] The IE BWP-UplinkDedicated parameter is used to configure dedicated (UE-specific) parameters for the uplink BWP.

[0489] BWP-UplinkDedicated Information Element

[0490]

[0491]

[0492]

[0493]

[0494] -TCI-State

[0495] IE TCI-State associates one or two DL reference signals with the corresponding QCL type.

[0496] TCI-State Information Element

[0497]

[0498]

[0499]

[0500]

[0501]

[0502] -TCI-StateId

[0503] The IE TCI-StateId is used to identify a TCI-State configuration.

[0504] -TCI-UL-State indicates the TCI status information used by UL for transmission. TCI-UL-State information element

[0505]

[0506]

[0507]

[0508] -TCI-UL-StateId

[0509] The IE TCI-UL-StateId is used to identify a TCI-UL-State configuration.

[0510] 6.3.2 Radio Resource Control Information Elements

[0511] …

[0512] -ReportConfigNR

[0513] IE ReportConfigNR specifies the criteria for triggering NR measurement report events, or CHO, CPA, or CPC events, or L2 U2N relay measurement report events. For events marked AN, where N equals 1, 2, etc., measurement report events and CHO, CPA, or CPC events are based on cell measurement results, which can be derived from SS / PBCH blocks or CSI-RS.

[0514] Event A1: The service becomes better than the absolute threshold;

[0515] Event A2: The service becomes worse than the absolute threshold;

[0516] Event A3: The neighbor becomes one offset better than PCell / PSCell;

[0517] Event A4: Neighbors become better than the absolute threshold;

[0518] Event A5: PCell / PSCell becomes worse than absolute threshold 1 and its neighbor / Scell ​​becomes better than another absolute threshold 2;

[0519] …

[0520] ReportConfigNR information element

[0521]

[0522]

[0523]

[0524]

[0525]

[0526]

[0527]

[0528]

[0529]

[0530] …

[0531] -TimeToTrigger

[0532] The IE TimeToTrigger specifies a range of values ​​for the trigger time parameter, which relates to the specific criteria for the event that must be met in order to trigger a measurement report. A value ms0 corresponds to 0ms and applies the behavior specified in 7.1.2, a value ms40 corresponds to 40ms, and so on.

[0533] In [5] draft 38.300v 18.0.0, L1 / L2 mobility (LTM) is introduced:

[0534] 9.2.3.5 L1 / L2 triggered mobility

[0535] 9.2.3.5.1 Overview

[0536] LTM is a procedure in which the gNB receives an L1 measurement report from the UE and, based on this, changes the UE's serving cell by sending a cell handover command via the MAC CE. The cell handover command indicates a candidate LTM configuration that the gNB has previously prepared and provided to the UE via RRC signaling. The UE then switches to the target configuration according to the cell handover command. The LTM procedure can be used to reduce mobility latency as described in Appendix G.

[0537] When configured by the network, the TCI state of one or more cells different from the currently serving cell can be activated. For example, the TCI state of an LTM candidate cell can be activated in advance before any of those cells becomes the serving cell. This allows the UE to perform DL synchronization with those cells, thereby facilitating a faster handover to one of those cells when a handover is triggered.

[0538] …

[0539] LTM supports intra-gNB-DU and inter-gNB-DU mobility within a gNB-CU. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cells that are not the current serving cell. LTM is supported only for licensed spectrum. The following scenarios are supported:

[0540] - PCell changes in non-CA and non-DC scenarios;

[0541] -Changes in PCell and SCell in the CA context;

[0542] - Dual-connection scenarios, PCell and MCG SCell changes, and PSCell and SCG SCell changes within the SN that do not involve the MN. LTMs for simultaneous PCell and PSCell changes are not supported.

[0543] Although the UE has stored LTM candidate configurations, the UE can also execute any L3 handover command sent by the network.

[0544] 9.2.3.5.2C Plane Treatment

[0545] Cell handover commands are delivered in the MAC CE, which contains the necessary information to perform LTM cell handover.

[0546] The overall procedure for LTM is described below. Figure 9 As shown in .2.3.5.2-1. The subsequent LTM is completed by repeating the early synchronization, LTM cell handover execution and LTM cell handover completion steps without releasing other LTM candidate configurations after each LTM cell handover is completed. The general procedure over the air interface applies to SCG LTM. Further details of SCG LTM can be found in TS37.340

[21] .

[0547] Figure 7 It is in draft 38.300v 18.0.0 Figure 9 2.3.5.2-1 Reproduction of the signaling procedure for LTM.

[0548] The procedure for LTM is as follows:

[0549] 1. The UE sends a MeasurementReport message to the gNB. The gNB decides to configure LTM and initiates LTM preparation.

[0550] 2.gNB will send an RRCReconfiguration message containing LTM candidate configurations to the UE.

[0551] 3. The UE stores the LTM candidate configuration and sends the RRCReconfigurationComplete message to the gNB.

[0552] 4a. The UE performs DL synchronization with the candidate cell before receiving the cell handover command.

[0553] 4b. When UE-based TA measurement is configured, the UE acquires the TA value of the candidate cell through measurement. The UE performs an early TA acquisition of the candidate cell requested by the network before receiving the cell handover command as specified in Clause 9.2.6. This is accomplished via a CFRA triggered by a PDCCH command from the source cell, after which the UE sends a preamble toward the indicated candidate cell. To minimize data interruption of the source cell due to the CFRA toward the candidate cell, the UE does not receive a random access response from the network for the purpose of TA value acquisition, and the TA value of the candidate cell is indicated in the cell handover command. The UE does not maintain a TA timer for the candidate cell and relies on the network implementation scheme to ensure TA validity.

[0554] 5. The UE performs L1 measurements on the configured candidate cells and transmits the L1 measurement report to the gNB. L1 measurements should be performed whenever RRC reconfiguration (step 2) is applicable.

[0555] 6.gNB decides to perform a cell handover to the target cell and transmits a MAC CE that triggers the handover via a candidate configuration index containing the target cell. The UE hands over to the target cell and applies the configuration indicated by the candidate configuration index.

[0556] 7. If the UE does not have a valid TA for the target cell as specified in Clause 6.1.3.xy of TS 38.321[6], the UE performs a random access procedure to the target cell.

[0557] 8. The UE completes the LTM cell handover procedure by sending an RRCReconfigurationComplete message to the target cell. If the UE has already performed the RA procedure in step 7, the UE considers the LTM cell handover to be successfully completed when the random access procedure is successfully completed. For LTM without RACH, the UE considers the LTM cell handover to be successfully completed when it determines that the network has successfully received its first UL data.

[0558] Steps 4 through 8 can be executed multiple times for subsequent LTMs using the LTM candidate configuration provided in step 2.

[0559] 9.2.3.5.3 U-plane treatment

[0560] Upon receiving the LTM cell handover command MAC CE, the UE performs a MAC reset. Whether the UE performs RLC re-establishment and PDCP data recovery during cell handover is explicitly controlled by the network via RRC signaling.

[0561] In the WID used for Mobility Enhancement Phase 4 (e.g., [6] RP-234036 New WID), the objectives for LTM measurement reporting are described:

[0562] 3 reasons

[0563] Layer 2 Mobility (LTM), introduced in Rel-18, offers improvements in handover latency and downtime compared to Layer 3-based mobility. However, LTM, as introduced in Rel-18, also has several limitations compared to Layer 3 mobility. This Rel-19 work item aims to remove some of these limitations.

[0564] …

[0565] Layer 3 mobility uses Layer 3 measurement reports, which support UE evaluation events triggered by measurement reports and reduce signaling overhead compared to periodic measurement reports. L1 measurements used for LTM mobility do not support this event triggering.

[0566] …

[0567] 4 objectives

[0568] 4.1 SI or core WI or test WI target

[0569] ○…

[0570] ● Measurement-related enhancements for the purpose of supporting LTM: [RAN2, RAN1]

[0571] ○ Measurement-related enhancement is applicable to both intra-CU MCG / SCG LTM and inter-CU MCG / SCG LTM

[0572] ○ Specify the necessary components to support event-triggered L1 measurement reporting [RAN2, RAN1]

[0573] ■ RAN1 and RAN2 have made independent progress on their respective MIMO and Mobility Enhancement WI event-triggered measurement objectives. Review the progress of RAN#105 to see if any modifications to the objectives are needed to avoid / manage any overlap in the work.

[0574] ○ Specifies support for CSI-RS measurements used in LTM procedures and implements CSI-RS-based beam management, and / or other necessary physical layer operations on candidate cells prior to LTM [RAN1]

[0575] The Rel-18 3GPP specification (e.g., [7] 3GPP 38.321v18.1.0) describes cell-level power saving and TCI state activation / deactivation for LTM candidate cells:

[0576] 5.34 Community-level energy saving

[0577] 5.34.1 Overview

[0578] Each serving cell can be configured with a periodic cell DTX mode (i.e., active and inactive periods) via RRC. Cell DTX operations affect the UE's monitoring activities of the PDCCH and configured downlink assignments in RRC_CONNECTED. For all active serving cells with cell DTX configured and activated, the MAC entity can monitor the PDCCH and configured downlink assignments using the cell DTX operations specified in Clause 5.34.2.

[0579] Each serving cell can be configured with a periodic cell DRX mode (i.e., active and inactive periods) via RRC. Cell DRX operation controls scheduling requests and configured uplink-granted transmission activities in RRC_CONNECTED. For all active serving cells with cell DRX configured and activated, the MAC entity can transmit configured uplink-granted transmission and scheduling requests using the cell DRX operation specified in Clause 5.34.3.

[0580] The RRC controls cell DTX and cell DRX operations by configuring the following parameters in the cellDTXDRX-Config of each serving cell:

[0581] -cellDTXDRXconfigType: Determines whether to configure only cell DTX, only cell DRX, or both;

[0582] -celldtxdrx-onDurationTimer: The duration of activity at the start of the cell DTX / DRX cycle;

[0583] -celldtxdrx-StartOffset: Defines the subframe at the start of the cell's DTX / DRX cycle;

[0584] -celldtxdrx-SlotOffset: The delay before starting celldtxdrx-onDurationTimer;

[0585] -celldtxdrx-Cycle: Cell DTX / DRX cycle period.

[0586] -cellDTXDRXactivationStatus: The initial activation status of cell DTX and cell DRX operations.

[0587] 5.34.2 Discontinuous transmission in cells

[0588] If cellDTXDRXconfigType is set to dtx or dtxdrx, then cell DTX is configured. For each serving cell, cell DTX activation and deactivation are performed using the following operations:

[0589] - Receive from the lower layer an activation or deactivation cell DTX indication indicating cell DTX operation, as specified in TS 38.213[6];

[0590] - CellDTXDRX-Config is configured by the upper layer: If cell DTX is configured and cellDTXDRXactivationStatus is set to active, the cell DTX operation is activated immediately after cell DTX configuration; if cell DTX is configured and cellDTXDRXactivationStatus is set to deactivate, the cell DTX operation is deactivated immediately after cell DTX configuration; if CellDTXDRX-Config is released, the cell DTX operation is deactivated and all corresponding configurations are released.

[0591] When cell DTX is configured and activated for a serving cell, the cell DTX activity period includes the time during which the following operations are performed simultaneously:

[0592] -celldtxdrx-onDurationTimer is running for the associated serving cell.

[0593] …

[0594] 5.34.3 Discontinuous reception in the cell

[0595] If cellDTXDRXconfigType is set to drx or dtxdrx, then the cell DRX is configured. For each serving cell, the following operations are used to activate and deactivate cell DRX:

[0596] - Receive from the lower layer a cell DRX indication to activate or deactivate cell DRX operation, as specified in TS 38.213[6];

[0597] - CellDTXDRX-Config is configured by the upper layer: If the cell DRX is configured and cellDTXDRXactivationStatus is set to active, the cell DRX operation is activated immediately after the cell DRX is configured; if the cell DRX is configured and cellDTXDRXactivationStatus is set to deactivate, the cell DRX operation is deactivated immediately after the cell DRX is configured; if CellDTXDRX-Config is released, the cell DRX operation is deactivated and all corresponding configurations are released.

[0598] …

[0599] 5.18.36 Candidate Cell TCI Status Activation / Deactivation

[0600] The network can activate and deactivate the TCI state of an LTM candidate cell configured in CandidateTCI-State and CandidateTCI-UL-State by sending the Candidate Cell TCI State Activation / Deactivation MACCE as described in Clause 6.1.3.76. The network deactivates the TCI state of an LTM candidate cell by not including the corresponding TCI state ID field in the Candidate Cell TCI State Activation / Deactivation MACCE.

[0601] MAC entities will:

[0602] 1> If the MAC entity receives a candidate cell TCI state activation / deactivation MAC CE on the serving cell:

[0603] 2> Instruct the lower layer about information regarding the activation / deactivation of MAC CE in the candidate cell TCI status.

[0604] 6.1.3.75 LTM Cell Handover Command MAC CE

[0605] The LTM cell handover command MAC CE is identified by a MAC subheader with eLCID, as specified in Table 6.2.1-1b. It has a variable size and contains the following fields ( Figure 6 .1.3.75-1):

[0606] - Target Configuration ID: This field indicates the index of the candidate target configuration to be applied to LTM cell handover, corresponding to ltm-CandidateId minus 1, as specified in TS 38.331[5]. The field is 3 bits long;

[0607] - Timing Advancement Command: This field indicates whether the TA is valid for the LTM target cell (i.e., the SpCell corresponding to the target configuration indicated by the Target Configuration ID field). If the value of this field is set to FFF, this field indicates that there is no valid timing adjustment available for the PTAG of the LTM target cell; otherwise, this field indicates the index value T of the amount of timing adjustment that the MAC entity must apply in TS 38.213[6]. A Furthermore, the UE can skip the random access procedure used for this LTM cell handover. The field is 12 bits long. If tag-Id-ptr is configured for the TCI state indicated by the TCI state ID field in the LTM target cell and tag-Id-ptr is set to the value n1, then this field indicates the TA for the TAG indicated by tag2-Id of the LTM target cell; otherwise, this field indicates the TA for the TAG indicated by tag-id of the LTM target cell.

[0608] -TCI State ID: This field indicates and activates the TCI state of the LTM target cell (i.e., the SpCell of the target configuration indicated by the Target Configuration ID field). The TCI state is identified by the TCI-StateId in ltm-DL-OrJointTCI-StateToAddModList, as specified in TS 38.331[5]. This field is used for the joint TCI state if the value of unifiedTCI-StateType in the configuration indicated by the Target Configuration ID field is joint; otherwise, this field is used for the downlink TCI state. The field is 7 bits long;

[0609] -UL TCI State ID: This field indicates and activates the uplink TCI state of the LTM target cell (i.e., the SpCell of the target configuration indicated by the Target Configuration ID field). The most significant bit of the UL TCI State ID is considered a reserved bit, and the remaining 6 bits represent the TCI-UL-StateId in ltm-UL-TCI-StatesToAddModList, as specified in TS 38.331[5]. This field is included if the value of unifiedTCI-StateType in the configuration indicated by the Target Configuration ID field is separate. The field is 8 bits long;

[0610] -C: This field indicates the presence of a contention-free random access resource field. If this field is set to 1, the following fields are present: the random access preamble index field, the S / U field, the SS / PBCH index field, the PRACH mask index field, and the repetition count field. If this field is set to 0, the random access preamble index field, the SS / PBCH index field, the PRACH mask index field, and the repetition count field are not present, and the S / U field is considered a reserved field.

[0611] -S / U: This field indicates which UL carrier is used to transmit PRACH for contention-free random access resources. If this field is set to 1, SUL is used; otherwise, NUL is used. The field is 1 bit long.

[0612] - Random Access Preamble Index: This field indicates the random access preamble index for a contention-free random access resource. This field should not be set to 0b000000. The field length is 6 bits.

[0613] -SS / PBCH Index: This field indicates the SS / PBCH that will be used to determine the timing of RACH transmission for PRACH in contention-free random access resources. The field is 6 bits long.

[0614] -PRACH Mask Index: This field indicates the RACH timing associated with the SS / PBCH indicated by the 'SS / PBCH Index' transmitted by the PRACH of a contention-free random access resource. It indicates a subset of the RACH timings from the rach-ConfigDedicated (indicated by the S / U field) for the UL carrier (if provided), otherwise it indicates a subset of the RACH timings from the rach-ConfigCommon (indicated by the S / U field) for the UL carrier in the UL BWP configuration of firstActiveUplinkBWP-Id, as specified in TS 38.331[5]. The field is 4 bits long.

[0615] Figure 8 It's 3GPP 38.321v18.1.0. Figure 6 1.3.75-1: Reproduction of the LTM cell handover command MAC CE.

[0616] 6.1.3.76 Candidate Cell TCI Status Activation / Deactivation MAC CE

[0617] The candidate cell TCI status activation / deactivation MAC CE is identified by a MAC subheader with the eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of the following fields:

[0618] - Candidate Cell ID: This field indicates the identity of the LTM candidate cell for the MAC CE application, corresponding to ltm-CandidateId minus 1, as specified in TS 38.331[5]. The field is 3 bits long;

[0619] -P i This field indicates whether each TCI code point has multiple TCI states or a single TCI state. If P i If the field is set to 1, then the i-th TCI code point contains both the DL TCI state and the UL TCI state. If P i If the field is set to 0, then the i-th TCI code point contains only DL / joint TCI states or UL TCI states. The code point to which the TCI state is mapped is determined by its ordinal position in all TCI state ID fields;

[0620] -D / U: This field indicates whether the TCI status ID in the same octet is used for the combined / downlink or uplink TCI status. If this field is set to 1, the TCI status ID in the same octet is used for the combined / downlink TCI status. If this field is set to 0, the TCI status ID in the same octet is used for the uplink TCI status.

[0621] -TCI State ID: This field indicates the TCI state identified by TCI-StateId in ltm-DL-OrJointTCI-StateToAddModList or TCI-UL-StateId in ltm-UL-TCI-StatesToAddModList, as specified in TS38.331[5]. If D / U is set to 1, a 7-bit TCI state ID, i.e., TCI-StateId, is used as specified in TS 38.331[5]. If D / U is set to 0, the most significant bit of the TCI state ID is considered reserved, and the remaining 6 bits indicate TCI-UL-StateId as specified in TS 38.331[5]. The maximum number of active TCI states is 16;

[0622] Figure 9 It's 3GPP 38.321v18.1.0. Figure 6 1.3.76-1: Reproduction of candidate cell TCI status activation / deactivation MACCE.

[0623] The following is provided in [8] Chairman's Notes RAN1#116eom0:

[0624] protocol

[0625] UE-initiated / event-driven beam reports should include at least the following:

[0626] ● Trigger event detection for beam reporting in UE

[0627] - The UE monitors the RS to assess whether the beam report trigger condition has been met.

[0628] - Further research is needed on the triggering conditions used to declare beam reporting events.

[0629] ●UE beam report transmission

[0630] - Signaling content in the beam report

[0631] - Select one or more options below (try one) as the signaling medium / container for beam report transmission.

[0632] ●MAC-CE

[0633] ●UCI

[0634] ●Other possibilities cannot be ruled out.

[0635] UE-initiated / event-driven beam reports can include the following aspects

[0636] ●UE requests UL resources for beam reporting

[0637] ● UE notification beam report transmission

[0638] ●gNB pre-configured resources

[0639] protocol

[0640] Regarding UE-initiated / event-driven beam reports, RAN1 should further investigate at least the following aspects related to beam report trigger event detection: quality metrics, event definitions, and thresholds.

[0641] - Further research into triggering events, including the following instances as starting points.

[0642] ●Event 1: The quality of the current beam is worse than a certain threshold.

[0643] ●Event 2: For example, the quality of at least one new beam in L1-RSRP becomes better than the current beam by a threshold.

[0644] ●Event 3: The quality of the new beam is better than a certain threshold.

[0645] ●Event 4: The quality of the current beam is worse than threshold 1, and the quality of at least one new beam is better than threshold 2.

[0646] ●Other possibilities cannot be ruled out.

[0647] protocol

[0648] Regarding UE-initiated / event-driven beam reports, at least L1-RSRP should be supported as a measurement quantity for intra-cell and inter-cell SSBs, as well as periodic CSI-RS for beam management.

[0649] -Note: Measurement results can be included in beam reports and / or used as quality metrics to initiate / trigger reports.

[0650] protocol

[0651] Regarding UE-initiated / event-driven beam reports, and signaling content, at least DL RS resource indicators and L1-RSRPs should be supported.

[0652] The following is provided in [9] Chairman's Notes RAN1#116bis eom0:

[0653] protocol

[0654] The beam report delivery procedure for UE-initiated / event-driven beam reports supports the following modes:

[0655] ●Mode A (UCI dynamically scheduled by gNB):

[0656] ●Step 1: The UE transmits a first PUCCH (one bit or multiple bits) to request resources for the second UL channel bearer beam report.

[0657] ● Further research is needed: request format, such as SR or new UCI type.

[0658] ●Step 2: The UE detects the DCI format to indicate the resources used for the second UL channel bearer beam report.

[0659] ●Step 3: Transmit beam report in the second UL channel.

[0660] ● Further research is needed: details regarding the second UL channel, such as whether the second UL channel is PUCCH, PUSCH, or both.

[0661] ● This mode is a basic UE capability (i.e., all UEs that support UE-initiated / event-driven beam reporting should support this feature).

[0662] ● No new DCI format will be introduced.

[0663] ●Mode B (UCI in pre-configured resources for the second UL channel):

[0664] ●Step 1: The UE transmits the first PUCCH (one-bit / multi-bit) of the notification notification second UL channel bearer beam report.

[0665] ● Further research is needed on notification formats, such as SR or new UCI types.

[0666] ●Step 2: The UE transmits a beam report in the second UL channel.

[0667] ● Further research is needed: details regarding the second UL channel, such as whether the second UL channel is PUCCH, PUSCH, or both.

[0668] ●The notification in step 1 is in a separate report instance from the beam report in step 2.

[0669] Further research is needed: Does the UE respond to receiving confirmation information at every step in all modes? For the above procedure, cross-CC beam reporting is supported for both modes.

[0670] protocol

[0671] Regarding UE-initiated / event-driven beam reports, the detection of triggering events for beam reports should at least support event 2: the quality of at least one new beam, such as L1-RSRP, becomes better than the current beam's threshold.

[0672] - At least L1-RSRP should be supported as a quality metric for Event 2.

[0673] ● Further research is needed: How to use L1-RSRP to determine triggering events (e.g., timers, counters, filter coefficients)

[0674] ● Further research is needed: Does the network control how L1-RSRP is used to determine the triggering event - regarding RS measurements for the new beam used in event 2, select one or more of the following:

[0675] ● Option 3a (Explicit Method): The RS for the new beam is explicitly configured by RRC (e.g., using the conventional configuration of RS measurement again or in TCI-State) or MAC-CE.

[0676] ●Option 3b (Implicit mode): The RS used for the new beam is implicitly derived from the QCL RS in the activated TCI state.

[0677] ●Option 3c (Implicit mode): The RS used for the new beam is implicitly derived from the QCL RS configured in TCI state.

[0678] protocol

[0679] Regarding UE-initiated / event-driven beam reports, specifically event 2, the threshold is configured in the RRC protocol.

[0680] Regarding UE-initiated / event-driven beam reports, for event 2, 'Current Beam' is the beam corresponding to the indicated TCI state.

[0681] - Regarding RS measurements for the current beam used in event 2, option 2a is supported:

[0682] ●Option 2a (Implicit mode): The RS used for the current beam is implicitly derived from the QCL RS of the indicated TCI state.

[0683] ■ Further research is needed: The RS used for the current beam can be the QCL RS in the indicated TCI state, or the SSB of the QCL with the QCL RS in the indicated TCI state.

[0684] ● Further research needed: Option 2c (explicit mode): The RS for the current beam is explicitly configured by RRC or MAC-CE.

[0685] ■Note: SSB or CSI-RS can be configured.

[0686] protocol

[0687] Regarding UE-initiated / event-driven beam reports, the following triggering events should be further investigated:

[0688] Event 1: The quality of the current beam is worse than a certain threshold.

[0689] Event 3: The quality of the new beam is better than a certain threshold.

[0690] Event 4: The quality of the current beam is worse than threshold 1, and the quality of at least one new beam is better than threshold 2.

[0691] Event 5: The absolute value of the difference between the quality of the current beam and the quality of at least one new beam is below a threshold.

[0692] Event 6: When the current beam is not in the optimal K>1 beams (the configured beams used for measurement and reporting).

[0693] - Event 7a: The quality of at least one new beam, such as L1-RSRP, becomes a better threshold than the RS derived from the activated TCI state with the worst quality.

[0694] - Event 7b: The quality of at least one new beam, such as L1-RSRP, becomes a better threshold than the RS derived from the activated TCI state with the best quality.

[0695] Event 8: M > 1. The quality of a new beam, such as L1-RSRP, becomes a better threshold than the current beam.

[0696] Event 9: The quality of at least one new beam, such as L1-RSRP, becomes a better threshold than the configured reference RS (which may be SSB or CSI-RS).

[0697] protocol

[0698] Regarding UE-initiated / event-driven beamforming reports, concerning the UL signaling content of the L1-RSRP report dependent on event 2, the following options are provided in the report instance for downward selection in RAN1#117 (other options are not excluded).

[0699] - Option 1 (Variable Size): Report N beams in the report instance, where N ∈ {1, 2, ..., N} max}

[0700] ●The N beams should satisfy the condition of event 2.

[0701] ●N max Configured by gNB

[0702] ● Further research is needed: Should an indication of the payload size be provided separately?

[0703] - Option 1a (Variable Size): Report N beams in the reporting instance, where N ∈ {1, 2, ..., N} max}

[0704] ●At least one of the N reporting beams should satisfy condition 2.

[0705] ●N max Configured by gNB

[0706] ● Further research is needed: Should an indication of the payload size be provided separately?

[0707] ● Further research is needed: details regarding how the UE determines the value of N.

[0708] - Option 1b: Report N beams in the report instance, where N ∈ {1, 2, ..., N} max}

[0709] ●The N beams should satisfy the condition of event 2.

[0710] ●N max Configured by gNB

[0711] ● The payload size does not change with N.

[0712] ● Further research is needed: If N is less than N max Then zero padding can be provided.

[0713] Option 2: Report only N=1 beams in the reporting instance.

[0714] ●The beam in the report should meet the conditions of Event 2.

[0715] - Option 3: Report N≥1 beams in the reporting instance.

[0716] ●At least one of the N reporting beams should satisfy condition 2.

[0717] ●N is configured by gNB

[0718] - Other options are not excluded.

[0719] - Further research is needed: whether the measurement results of the current beam are always reported or can be enabled by RRC.

[0720] - Further research is needed: When reporting the current beam, is the current beam counted among the N reporting beams?

[0721] - The selected option should satisfy event 2.

[0722] In

[10] 3GPP TS 38.214V17.3.0 (2022-09), the following is a quote from the relevant paragraph on TCI status:

[0723] 5.1.5 Quasi-co-addressable antenna ports

[0724] The UE can be configured with a list of up to M TCI-States configured in the higher-layer parameter PDSCH-Config to decode the PDSCH based on the detected PDCCH having a predetermined DCI for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring a quasi-co-address relationship between one or two downlink reference signals and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. The quasi-co-address relationship is configured via the higher-layer parameter qcl-Type1 for the first DL RS and the higher-layer parameter qcl-Type2 for the second DL RS (if configured). In the case of two DL RSs, the QCL type will be different, regardless of whether the reference is for the same DL RS or different DL RSs. The quasi-co-address type corresponding to each DL RS is given by the higher-layer parameter qcl-Type in QCL-Info and can take one of the following values:

[0725] -'Type A': {Doppler shift, Doppler spread, average delay, delay spread}

[0726] -'Type B': {Doppler shift, Doppler spread}

[0727] -'Type C': {Doppler shift, average delay}

[0728] -'Type D': {Space Rx parameter}

[0729] The UE can configure a list of up to 128 TCIState configurations in the higher-layer parameter dl-OrJoint-TCIStateList in PDSCH-Config. These configurations provide quasi-co-address reference signals for the DM-RS of PDSCH and DM-RS of PDCCH in CC, for CSI-RS, and, where applicable, for determining the UL TX spatial filter for PUSCH and PUCCH resources in CC based on dynamic and configuration-approved grants, as well as for SRS.

[0730] If the TCIState or UL-TCIState configuration does not exist in the BWP of the CC, the UE may apply the TCIState or UL-TCIState configuration from the reference BWP of the reference CC. If the UE is configured with dl-OrJoint-TCIStateList or UL-TCIState in any CC in the band, the UE is not expected to be configured with TCI-State, SpatialRelationInfo, or PUCCH-SpatialRelationInfo in CCs in the same band, except for SpatialRelationInfoPos. The UE may assume that when the UE is configured with TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16, the UE is not configured with dl-OrJoint-TCIStateList or UL-TCIState in any CC in the same band of the CC list.

[0731] The UE receives an activation command, as described in Clause 6.1.3.14 of [10, TS 38.321] or Clause 6.1.3.47 of [10, TS 38.321], to map up to eight TCI states and / or TCI state pairs to code points in the DCI field 'Transmission Configuration Indication' for one or a set of CC / DLBWPs and (if applicable) one or a set of CC / UL BWPs, where one TCI state is for a DL channel / signal and / or one TCI state is for a UL channel / signal. When a set of TCI state IDs is activated for a set of CC / DL BWPs and, where applicable, for a set of CC / UL BWPs, the applicable list of CCs is determined by the CCs indicated in the activation command, and the same set of TCI state IDs is applied to all DL and / or UL BWPs in the indicated CCs. If the activation command maps TCIState and / or UL-TCIState to only one TCI code point, then once the indicated mapping for the single TCI code point is applied as described in [11, TS 38.133], the UE shall apply the indicated TCIState and / or UL-TCIState to a CC / DL BWP or a set thereof, and if applicable, to a CC / UL BWP or a set thereof.

[0732] When the bwp-id or cell of the QCL-Type A / D source RS in the QCL-Info of the TCI state is not configured, the UE assumes that the QCL-Type A / D source RS is configured in the CC / DL BWP applicable to the TCI state.

[0733] When tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured for CORESET, a UE with an active TCIState or UL-TCIState and configured with dl-OrJoint-TCIStateList receives DCI format 1_1 / 1_2, which provides the indicated TCIState or UL-TCIState for one or all CCs in the same CC list configured by simultaneousTCI-UpdateList1-r17, simultaneousTCI-UpdateList2-r17, simultaneousTCI-UpdateList3-r17, and simultaneousTCI-UpdateList4-r17. DCI format 1_1 / 1_2 may or may not have (if applicable) DL assignment. If DCI format 1_1 / 1_2 has no DL assignment, the UE may assume the following:

[0734] -CS-RNTI is used for CRC scrambling of DCI.

[0735] - Set the values ​​for the following DCI fields as follows:

[0736] -RV = all '1's

[0737] -MCS = all '1'

[0738] -NDI=0

[0739] - Set to all '0' for FDRA type 0, or all '1' for FDRA type 1, or all '0' for dynamicSwitch (same as in Table 10.2-4 of [6, TS 38.213]).

[0740] …

[0741] If the UE receives a higher-layer configuration of a dl-OrJoint-TCIStateList with a single TCIState that can be used as the indicated TCI state, the UE obtains the QCL assumption from the configured TCI states of the DM-RS for PDSCH and the DM-RS for PDCCH, as well as the CSI-RS that applies the indicated TCI state.

[0742] If the UE receives a higher-layer configuration of a dl-OrJoint-TCIStateList with a single TCIState or a single UL-TCIState that can be used as the indicated TCI state, the UE determines the UL TX spatial filter (if applicable) from the configured TCI states of the dynamically granted and configured granted PUSCH and PUCCH, and the SRS applying the indicated TCI state.

[0743] When a UE transmits a PUCCH or PUSCH with HARQ-ACK information corresponding to a DCI that bears a TCI state indication but does not have a DL assignment, or a PDSCH that corresponds to a DCI scheduled by a DCI that bears a TCI state indication, and if the indicated TCI state differs from a previously indicated TCI state, the indicated DLorJointTCIState or UL-TCIState should be applied starting from the first time slot at least beamAppTime symbols after the last symbol of the PUCCH or PUSCH. The first time slot and the beamAppTime symbols are determined on the active BWP with the smallest SCS among the active BWPs of the carriers applying beam indication.

[0744] If the UE is configured with the higher-layer parameter tci-PresentInDCI set to 'enabled' for scheduling PDSCH in the CORESET, the UE assumes that the TCI field exists in DCI format 1_1 of the PDCCH transmitted on the CORESET. If the UE is configured with the higher-layer parameter tci-PresentDCI-1-2 for scheduling PDSCH in the CORESET, then the UE assumes that the TCI field with the DCI field size indicated by tci-PresentDCI-1-2 exists in DCI format 1_2 of the PDCCH transmitted on the CORESET. …

[0745] 5.1.6.1.2 CSI-RS used for L1-RSRP and L1-SINR calculation

[0746] If a UE is configured with an NZP-CSI-RS-ResourceSet and its higher-layer parameter repetition is set to 'on', the UE may assume that the CSI-RS resources within the NZP-CSI-RS-ResourceSet, as described in Clause 5.2.2.3.1, are transmitted using the same downlink spatial domain transmission filter, where the CSI-RS resources in the NZP-CSI-RS-ResourceSet are transmitted in different OFDM symbols. If repetition is set to 'off', the UE should not assume that the CSI-RS resources within the NZP-CSI-RS-ResourceSet are transmitted using the same downlink spatial domain transmission filter.

[0747] If the UE has a CSI-ReportConfig where reportQuantity is set to 'cri-RSRP', 'cri-SINR', or 'none', and if the CSI-ResourceConfig (higher-layer parameter resourcesForChannelMeasurement) used for channel measurement contains an NZP-CSI-RS-ResourceSet configured with the higher-layer parameter repetition but not the higher-layer parameter trs-Info, then the UE can only configure the same number (1 or 2) ports with the higher-layer parameter nrofPorts for all CSI-RS resources within that set. If the UE has configured CSI-RS resources in the same OFDM symbol as the SS / PBCH block, then, where 'Type D' applies, the UE can assume that the CSI-RS and the SS / PBCH block are quasi-co-located with 'Type D'. Furthermore, the UE will not expect to configure CSI-RS in PRBs that overlap with those PRBs of the SS / PBCH block, and the UE will expect the same subcarrier spacing for both the CSI-RS and the SS / PBCH block.

[0748] The following is provided in

[11] 3GPP TS 38.213V18.2.0 (2024-03):

[0749] 11.2A Cancellation Instruction

[0750] If the UE is provided with Uplink Cancellation, a search space set is provided for the UE in one or more serving cells for L in each search space set. CIThe first PDCCH candidate is monitored at the CCE aggregation level of each CCE for detection of DCI format 2_4 [5, TS 38.212] with CI-RNTI provided by ci-RNTI, as described in clause 10.1. UplinkCancellation further provides the UE with

[0751] - A collection of serving cells provided by ci-ConfigurationPerServingCell, which includes a collection of serving cell indexes and a collection of corresponding positions of fields in DCI format 2_4 provided by positionInDCI.

[0752] - Multiple fields in DCI format 2_4 provided by positionInDCI-forSUL for each serving cell used for an SUL carrier, if the serving cell is configured with an SUL carrier.

[0753] - The payload size in DCI format 2_4 provided by dci-PayloadSize-ForCI.

[0754] - Indication of time-frequency resources provided by timeFrequencyRegion

[0755] For a serving cell with associated fields in DCI format 2_4, this field is represented as follows:

[0756] -N CI The number of bits provided by ci-PayloadSize

[0757] -B CI The number of PRBs provided by the frequencyRegionforCI in the timeFrequencyRegion.

[0758] -T CI The number of symbols, excluding symbols used to receive SS / PBCH blocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon, depends on the number of symbols.

[0759] - Provided by timeDurationforCI in timeFrequencyRegion, if the PDCCH monitoring period of the search space set with DCI format 2_4 is one time slot and there are more than one PDCCH monitoring opportunity in the time slot, or

[0760] Otherwise, it is equivalent to PDCCH monitoring periodically.

[0761] -G CIT provided by timeGranularityforCI in timeFrequencyRegion CI Number of partitions for each symbol

[0762] From N CI The unit MSB of the G CI A set and G CI Each symbol group has a one-to-one mapping, where the first... Each of the groups contains There are 1 symbol, and the remainder is 1 symbol. Each of the groups contains Symbols. The UE determines the symbol duration of the SCS configuration for the UE monitoring the PDCCH activity DL BWP used for DCI format 2_4 detection.

[0763] For a set of symbols, N is the MSB from each set. BI =N CI / G CI Units digit and N BI Each PRB group has a one-to-one mapping, where the first Each of the groups contains One, and the remaining Each of the groups contains One PRB. Based on the indicated offset RB. 开始 The frequency region for CI and the length L of RIV according to [6, TS 38.214] RB And according to the SCS configuration indication O for the UE monitoring of the PDCCH activity DL BWP used for DCI format 2_4 detection. 载波 In the FrequencyInfoUL-SIB or the offsetToCarrier in FrequencyInfoUL, the UE determines the first PRB index as And the number of adjacent RBs is determined to be B. CI =L RB .

[0764] The DCI format 2_4 indication for the serving cell applies to either PUSCH or SRS transmissions on the serving cell. If the PUSCH or SRS transmission is scheduled by the DCI format, then the DCI format 2_4 indication applies to the PUSCH or SRS transmission only if the last symbol of the PDCCH reception providing the DCI format is earlier than the first symbol of the PDCCH reception providing the DCI format 2_4.

[0765] For the serving cell, the UE will T CIThe first symbol among the symbols is determined to be T′ at the point where the UE detects the end of the PDCCH reception of DCI format 2_4. proc，2 The first symbol that follows, where T′ proc，2 This is from the T for PUSCH processing capability 2 [6, TS38.214]. proc，2 Obtained, assumed Where d 偏移 Provided by delta_Offset, μ is the minimum SCS configuration μ provided in the SCS configuration of PDCCH and the scs-SpecificCarrierList of FrequencyInfoUL or FrequencyInfoUL-SIB. UL Minimum SCS configuration between. UE is not expected to cancel as T. proc，2 The corresponding symbol preceding the PUSCH transmission or SRS transmission, assuming that the UE detects the last symbol of the PDCCH received in DCI format 2_4 after d 2，1 =0.

[0766] The serving cell may cancel PUSCH transmissions or actual duplication of PUSCH transmissions [6, TS38.214] when it detects that a UE of DCI format 2_4 has a PUSCH transmission with duplicate type B (as determined in Clauses 9 and 9.2.5 or Clause 6.1 of [6, TS 38.214]), or cancel SRS transmissions on the serving cell in the following circumstances respectively:

[0767] - Transmit as a PUSCH with priority 0 if the UE is provided with uplinkCancellationPriority.

[0768] -From T CI A group of symbols in DCI format 2_4 N BI The corresponding set of units has at least one bit value '1', and contains symbols for PUSCH transmission (repetition) or SRS transmission, and

[0769] -From B CI A group of PRBs has a corresponding bit value '1' in the bit set corresponding to the symbol group in DCI format 2_4, and includes PRBs that are PUSCH transmissions (repetitions) or SRS transmissions.

[0770] in

[0771] - Cancellation of PUSCH transmission (repetition) includes all symbols from the earliest symbol of the PUSCH transmission (repetition) in a set of symbols with corresponding bit values ​​'1' in DCI format 2_4.

[0772] - The cancellation of SRS transmission only includes symbols from one or more groups of symbols in DCI format 2_4 with corresponding bit values ​​'1'.

[0773] If the UE cancels a PUSCH transmission or SRS transmission based on an instruction via DCI format 2_4, then the UE does not expect to be scheduled by the second DCI format to transmit the PUSCH or SRS via a symbol containing the symbol of the canceled PUSCH transmission or SRS transmission, wherein the last symbol of the PDCCH reception provided by the second DCI format is not earlier than the first symbol of the PDCCH reception provided by DCI format 2_4.

[0774] 12-bandwidth section operation

[0775] …

[0776] A UE configured to operate in the bandwidth portion (BWP) of the serving cell is configured by the higher layers of the serving cell. A set of up to four bandwidth portions (BWPs) are used by the UE (DL BWP set) in the DL bandwidth via the parameter BWP-Downlink or via the parameter initialDownlinkBWP having a set of parameters configured by BWP-DownlinkCommon and BWP-DownlinkDedicated. A set of up to four BWPs are used by the UE (UL BWP set) in the UL bandwidth via the parameter BWP-Uplink or via the parameter initialUplinkBWP having a set of parameters configured by BWP-UplinkCommon and BWP-UplinkDedicated.

[0777] For operations performed via shared spectrum channel access, the UE expects the BWP configured by the parameter initialUplinkBWP provided by UplinkConfigCommonSIB to be mapped to only a single RB set.

[0778] If the UE is not provided with an initial Downlink BWP, the initial DL BWP is defined by the location and number of adjacent PRBs and the SCS and cyclic prefix of the PDCCH received in the CORESET for the Type 0-PDCCH CSS set. The adjacent PRBs begin with the PRB with the lowest index and end with the PRB with the highest index in the CORESET for the Type 0-PDCCH CSS set, and are after pruning (if any) [4, TS 38.211]; otherwise, the initial DL BWP is provided by the initial Downlink BWP. For operation on the primary or secondary cell, the initial UL BWP is provided to the UE via the initial Uplink BWP. If the UE is configured with a supplementary UL carrier, the initial UL BWP can be provided to the UE via the initial Uplink BWP on the supplementary UL carrier.

[0779] If the UE has a dedicated BWP configuration, then the first active DL BWP for reception can be provided to the UE via firstActiveUplinkBWP-Id, and the first active UL BWP for transmission on the carrier of the primary cell can also be provided to the UE via firstActiveUplinkBWP-Id.

[0780] For each DL BWP or UL BWP in the set of DL BWPs or UL BWPs respectively, the UE is provided with the following parameters of the serving cell as defined in [4, TS38.211] or [6, TS 38.214]:

[0781] -SCS, provided by subcarrierSpacing

[0782] - Cyclic prefix, provided by cyclicPrefix

[0783] -Common RB and the number of adjacent RBs By indicator offset RB 开始 The locationAndBandwidth and the length L of the RIV according to [6, TS 38.214] RB Provide, set And the value is O 载波 Provided by offsetToCarrier for subcarrierSpacing

[0784] - The index in the set of DL BWPs or UL BWPs is provided by the corresponding BWP-Id.

[0785] - A set of common BWP parameters and a set of BWP-specific parameters, provided by BWP-DownlinkCommon and BWP-DownlinkDedicated for DL ​​BWPs, or by BWP-UplinkCommon and BWP-UplinkDedicated for UL BWPs [12, TS 38.331]

[0786] For unpaired spectrum operation, when the DL BWP index is the same as the UL BWP index, the DL BWP from the group of configured DL BWPs with an index provided by BWP-Id is associated with the UL BWP from the group of configured UL BWPs with an index provided by BWP-Id. For unpaired spectrum operation, when the BWP-Id of the DL BWP is the same as the BWP-Id of the UL BWP, the UE does not expect to receive a configuration where the center frequency of the DL BWP differs from the center frequency of the UL BWP.

[0787] For each DL BWP in the PCell or DL ​​BWP set, the UE can be configured as a CORESET for each type of CSS set and USS, as described in Clause 10.1. The UE is not expected to be configured without a CSS set on the PCell in the active DL BWP.

[0788] If controlResourceSetZero and searchSpaceZero are provided to the UE in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon, then the UE determines the CORESET of the search space set from controlResourceSetZero as described in Clause 13 and with reference to Tables 13-0 to 13-10, and determines the corresponding PDCCH monitoring timing as described in Clause 13 and with reference to Tables 13-11 to 13-15. If the active DL BWP is not the initial DL BWP, then the UE determines the PDCCH monitoring timing of the search space set only if the CORESET bandwidth is within the active DL BWP and the active DL BWP has the same SCS configuration and the same cyclic prefix as the initial DL BWP.

[0789] For each UL BWP in the set of PCell, PUCCH-SCell, or PUCCH-sSCell, configure a resource set for the UE for PUCCH transmission as described in Clause 9.2.1.

[0790] The UE receives PDCCH and PDSCH in the DL BWP according to the SCS and CP length configured for the DL BWP. The UE transmits PUCCH and PUSCH in the UL BWP according to the SCS and CP length configured for the UL BWP.

[0791] If the bandwidth portion indicator field is configured in DCI format, the bandwidth portion indicator field value indicates the active DL BWP for DL ​​reception from the configured DL BWP set, as described in [5, TS 38.212]. If the bandwidth portion indicator field is configured in DCI format, the bandwidth portion indicator field value indicates the active UL BWP for UL transmission from the configured UL BWP set, as described in [5, TS 38.212].

[0792] …

[0793] If the bandwidth indicator field is configured in DCI format and indicates a UL BWP or DL ​​BWP that is different from the active UL BWP or DL ​​BWP, then the UE will

[0794] -For each information field in DCI format

[0795] - If the size of the information field is smaller than the size required for DCI format decoding of the UL BWP or DL ​​BWP indicated by the bandwidth portion indicator, then the UE prefixes the information field with zeros until its size is the corresponding size required for information field decoding of the UL BWP or DL ​​BWP before decoding the DCI format information field.

[0796] - If the size of the information field is larger than the size required for DCI format decoding of the UL BWP or DL ​​BWP indicated by the bandwidth portion indicator, then before decoding the DCI format information field, the UE uses several least significant bits of the DCI format equal to the corresponding size required for the UL BWP or DL ​​BWP indicated by the bandwidth portion indicator.

[0797] - For DCI format 0_3, or for DCI format 1_3, and for an information field containing a certain number of blocks [5, TS 38.212], the above procedure applies individually to each block of the information field.

[0798] - Set the active UL BWP or DL ​​BWP to the UL BWP or DL ​​BWP indicated by the bandwidth portion indicator in the DCI format.

[0799] …

[0800] The UE does not expect to detect a DCI format with a BWP indicator field indicating an active DL BWP or active UL BWP change, wherein the corresponding time domain resource assignment field provides a slot offset value for PDSCH reception or PUSCH transmission that is less than the delay required by the UE for active DL BWP change or UL BWP change, respectively [10, TS 38.133].

[0801] If the UE detects a DCI format with a BWP indicator field that indicates a change in the cell's active DL BWP, then the UE is not required to receive or transmit in the cell for the duration from the end of the third symbol of the time slot (where the UE receives a PDCCH containing the DCI format in the scheduling cell) until the start of the time slot indicated by the time slot offset value of the time domain resource assignment field in the DCI format.

[0802] If the UE detects a DCI format indicating a change in the active UL BWP of the cell, then the UE is not required to receive or transmit in the cell for the duration from the end of the third symbol of the time slot (where the UE receives a PDCCH containing the DCI format in the scheduling cell) until the start of the time slot indicated by the time slot offset value of the time domain resource allocation field in the DCI format.

[0803] The UE is expected to detect the DCI format with a BWP indicator field indicating an active UL BWP change or an active DL BWP change only when it receives the corresponding PDCCH within the first 3 symbols of the time slot. If the UE receives a search space set containing searchSpaceLinkingId with the same value... i and s j If two PDCCH receptions detect DCI format, as described in Clause 10.1, the UE shall regard the PDCCH reception in which the UE detects DCI format as the later of the two PDCCH receptions.

[0804] For the serving cell, the default DL BWP among the configured DL BWPs can be provided to the UE via the defaultDownlinkBWP-Id. If the default DL BWP is not provided to the UE via the defaultDownlinkBWP-Id, then the default DL BWP is the initial DL BWP.

[0805] If the service cell timer value [11, TS 38.321] is provided to the UE via bwp-InactivityTimer and the timer is running, then if the restart condition in [11, TS 38.321] is not met during the interval of a subframe of FR1 or a half-subframe of FR2, the UE decrements the timer at the end of the subframe of FR1 or at the end of the half-subframe of FR2.

[0806] For cells where the UE changes the active DL BWP due to the expiration of the BWP inactivity timer, in order to accommodate the delay of the UE's required change of active DL BWP or active UL BWP [10, TS 38.133], the UE is not required to receive or transmit in the cell during the duration from the start of the subframe of FR1 or the half-subframe of FR2 to the start of the time slot that the UE can receive or transmit, the start of the subframe of FR1 or the half-subframe of FR2 immediately following the expiration of the BWP inactivity timer.

[0807] When the BWP inactivity timer of a UE in a cell within FR1 (or FR2) expires within the duration during which the UE does not need to receive or transmit active UL / DL BWP changes for the cell or different cells within FR1 (or FR2), the UE delays the active UL / DL BWP change triggered by the expiration of the BWP inactivity timer until the subframe of FR1 or half-frame of FR2 immediately following the completion of the active UL / DL BWP change for the UE in the cell or different cells within FR1 (or FR2).

[0808] If a first active DLBWP is provided to the UE via firstActiveDownlinkBWP-Id and a first active UL BWP is provided to the UE via firstActiveUplinkBWP-Id on the carrier of the subcell, then the UE uses the indicated DLBWP and the indicated UL BWP as the corresponding first active DLBWP and first active UL BWP on the subcell carrier.

[0809] In New Radio (NR), the network can configure beam reporting (e.g., periodic or semi-persistent beam reporting) or activate or trigger aperiodic beam reporting (e.g., Channel State Information (CSI) reporting) for User Equipment (UE) to obtain or acquire channel state information, channel quality, or beam quality for data / control transmission. Typically, beam reporting can be a CSI report with a quantity corresponding to the Reference Signal Received Power (RSRP). However, with frequent reporting, the UE may experience significant transmission overhead. On the other hand, with sparse reporting, the network may not be able to obtain the latest beam information in a timely manner, and the communication quality between the network and the UE may degrade. In Rel-19 Multiple-Input Multiple-Output (MIMO) Phase 5, UE-initiated / event-driven beam management for reducing latency and / or overhead is discussed. The UE can initiate or trigger beam reporting in response to the fulfillment of a certain condition (e.g., the quality of the currently active beam is below a threshold and / or the quality of a new / candidate beam is above a threshold and / or the quality of the new / candidate beam is a better threshold than the current beam). In addition, during the mobility enhancement phase 4, UE-initiated beam reports are introduced for candidate cells to enable faster L1 / L2 triggered mobility (LTM).

[0810] In current NR systems, there are other beam management mechanisms and / or other reporting and / or procedures regarding beam changes and / or beam reporting. For example, a UE may change its (activated) beam for a cell in response to receiving an Active Transport Configuration Indicator (TCI) state Media Access Control (MAC) element (CE) associated with or indicating the cell (or the cell's bandwidth portion (BWP)). In the case of UE-initiated beam reporting, the UE may have concurrent beam reporting procedures and other procedures. One problem is that when the two procedures conflict, the network may receive outdated beam information, or the UE may transmit unnecessary beam reports.

[0811] exist Figure 10AAn example of the problem is illustrated below. At time t1, for example, due to beam quality degradation of the BWP or cell, the UE triggers (UE-initiated) a beam report. The UE may assemble a Transport Block (TB) or MAC Protocol Data Unit (PDU) for transmission of the report at time t3. Additionally and / or alternatively, in some embodiments, the UE may (prepare or be configured) Physical Uplink Control Channel (PUCCH) resources for transmission of the report at time t3. Additionally and / or alternatively, in some embodiments, the UE may trigger a Scheduling Request (SR) and / or initiate a random access procedure to the network to obtain uplink (UL) permission for report transmission. At time t2, the network may provide the UE with beam changes for the BWP or for the cell (e.g., TCI state reconfiguration, activation / deactivation via MAC CE, etc.). At time t3, the UE transmits the beam report to the network. Since the beam may have been changed by the network in t2, the report in t3 may not be up-to-date or may cause confusion for the network.

[0812] Figure 10B Another example is illustrated below. The UE can determine or detect an event that is met at time t1 to trigger a report for the cell (e.g., the event could be a threshold that the quality of the new beam is better than the current beam of the cell). The UE can maintain or monitor the event for a period of time having a value of timeToTrigger(ttt), where the UE can trigger a report in response to the event being met during ttt. At time t2, the network provides a beam change for the cell. The beam change can be a beam activation / deactivation MACCE. The previous current beam can be deactivated and / or replaced by a second current beam. However, monitoring of the event may still be in progress (e.g., the reference current beam used to measure the event may not change accordingly and / or the quality of the second current beam may be lower than the new beam for a short period of time), and the UE may trigger a report prematurely or unnecessarily.

[0813] The present invention discloses a method for handling beam reports initiated by a UE that overlap with other UE programs, or for the interaction between beam reports initiated by a UE and other UE programs.

[0814] -Handling of events (triggered reports,) and Time-To-Trigger (TTT) events in the following scenarios:

[0815] --Event: Pause / Resume, Discard / Clear, or Continue.

[0816] -- Triggered report: Discard / Clear or Keep.

[0817] --TTT: Restart, stop, or continue.

[0818] Different events and situations can be handled in different ways.

[0819] --MIMO:

[0820] ---Events of the subcell (SCell) when SCell is reactivated, (triggered reports,) TTT.

[0821] ---Events (triggered reports,) of primary and secondary cells (PSCells) when the secondary cell group (SCG) is deactivated.

[0822] ---SCell events (triggered reports,) TTT when the active downlink (DL) BWP of SCell switches to the dormant BWP.

[0823] ---The event of SCell when the Timing Advance (TA) timer is associated with a cell where the report transmission is due, (the triggered report,) TTT.

[0824] ---Cell events (triggered reports, TTT) during beam fault recovery (BFR) in progress.

[0825] ---Events of a cell (triggered reports) when another cell's BFR (Browser Free Flight) is in progress for reporting transmission.

[0826] ---Cell events (triggered reports, TTT) when the cell's current beam changes.

[0827] --LTM:

[0828] ---Events (triggered reports) of the candidate cell when the candidate cell's TCI status is revoked and activation is cancelled.

[0829] ---When the activated TCI status of a candidate cell changes, such as all activations being revoked, some activations being revoked, moving from the first group to the second group, or a new activated TCI status, the candidate cell's events, (triggered reports,) TTT (Time to Trigger) occur.

[0830] ---Events of the candidate cell when the LTM command MAC CE for switching to the candidate cell is received, (triggered report,) TTT.

[0831] ---Events of the candidate cell when receiving the LTM command MAC CE to switch to another candidate cell, (triggered report,) TTT.

[0832] ---Events of candidate cells during handover or LTM, (triggered reports,) TTT.

[0833] ---Events of candidate cells when the current beam of the primary cell (PCell) / special cell (SpCell) changes, (triggered reports,) TTT.

[0834] One concept of this invention is that the UE can determine, in response to one or more procedures, whether to perform one or more actions (part of one action) in response to a beam report initiated by the UE.

[0835] A beam report initiated by the UE can be associated with or triggered on a cell-specific basis. The cell can be a PCell or SCell. Additionally and / or alternatively, in some embodiments, the cell can be a candidate cell (associated with an LTM candidate configuration). The candidate cell can be a PCell associated with an LTM candidate configuration. Preferably, in some embodiments, the candidate cell corresponds to a cell associated with an LTM candidate configuration (configured in a PCell).

[0836] The UE may perform one or more actions in response to a UE-initiated beam report in response to one or more procedures. Additionally and / or alternatively, in some embodiments, the UE may determine not to perform the one or more actions in response to (a portion of) the one or more procedures. Additionally and / or alternatively, in some embodiments, the UE may determine to perform the one or more actions in response to a UE-initiated beam report in response to a portion of the one or more procedures, and not to perform the one or more actions in response to another portion of the one or more procedures.

[0837] Additionally and / or alternatively, in some embodiments, the UE may perform a first portion of the one or more actions in response to a first procedure in the one or more procedures for a UE-initiated beam report (associated with an event), and may perform another portion of the one or more actions in response to a UE-initiated report without responding to the first procedure. Additionally and / or alternatively, in some embodiments, the UE may perform a second portion of the one or more actions in response to a UE-initiated beam report in response to a second procedure in the one or more procedures, and may perform another portion of the one or more actions in response to a UE-initiated report without responding to the second procedure.

[0838] The UE can determine, at least based on an event associated with the UE-initiated beam report, whether to perform one of the one or more actions in response to a first procedure of the one or more procedures. For example, if or when the UE-initiated beam report is associated with a first event, the UE can perform the action in response to the first procedure, and if or when the UE-initiated beam report is associated with a second event, the UE can choose not to perform the action in response to the first procedure.

[0839] Additionally and / or alternatively, in some embodiments, the UE may determine, at least based on a procedure, whether to perform an action (one or more actions) in response to a UE-initiated beam report. For example, the UE may perform the action in response to a first procedure for a UE-initiated beam report, and the UE may not perform the action in response to a second procedure.

[0840] The UE can determine whether to cancel a UE-initiated beam report based at least on the state of one or more of its programs. The UE can cancel the beam report if or if at least one or more of its programs are in progress. The UE can not cancel the beam report if or if at least no one or more of its programs are in progress. Additionally and / or alternatively, in some embodiments, the UE can cancel or stop (parts) of the one or more programs if or if at least a triggered or ongoing beam report is present.

[0841] The UE can determine whether to perform an action in response to a UE-initiated (UEI) beam report based at least on the type of procedure. Figure 11 An example is shown. For a beam report initiated by the UE, in response to one or more procedures, namely procedure 1 (occurring during an ongoing UE-initiated beam report), the UE may not perform any of the one or more actions (actions 1 to 4). Additionally and / or alternatively, in some embodiments, in response to one or more procedures, namely procedure 2, the UE may perform actions 1 and 2 but not actions 3 and 4. In response to one or more procedures, namely procedure 3, the UE may perform actions 1 to 4.

[0842] Additionally and / or alternatively, in some embodiments, the UE may determine whether to perform an action in response to a procedure for a UEI beam report based at least on events associated with the UEI beam report. Figure 12 Another example is shown below. For a beam report initiated by a UE associated with event 1, the UE may perform action 1 in response to procedures 1 and 2. The UE may not perform action 1 in response to procedure 3. For a beam report initiated by a UE associated with event 2, the UE may perform action 1 in response to procedure 1. The UE may not perform action 1 in response to procedures 2 and 3.

[0843] exist Figure 13AAnother example is shown below. In response to procedure 1, the UE performs actions 1 and 2 on a beam report initiated by the UE related to event 1, and in response to procedure 1, the UE performs action 1 on a beam report initiated by the UE related to event 2 but does not perform action 2.

[0844] List of actions

[0845] The one or more actions related to a UE-initiated beam report may (or may not) include / include pausing (in-process) UE-initiated beam reports. When a UE-initiated beam report is paused, the UE may not generate a UE-initiated beam report for that beam report.

[0846] The one or more actions in response to a beam report initiated by a UE may (or may not) include / include resuming (suspended) a beam report initiated by a UE.

[0847] The one or more actions related to a UE-initiated beam report may (or may not) include / include suspending an event associated with the (ongoing) UE-initiated beam report. To suspend an event, the UE may stop performing measurements associated with the event and / or stop / disable triggering beam reports associated with the event and / or stop / disable triggering beam reports associated with a measurement object (e.g., cell-related) associated with the UE-initiated beam report.

[0848] The one or more actions related to a UE-initiated beam report may (or may not) include / include resuming (suspended) the UE-initiated beam report. To resume the event, the UE may begin performing measurements associated with the event and / or enable triggering beam reports associated with the event and / or with the measurement objects associated with the beam report.

[0849] The one or more actions for a beam report initiated by a UE may (or may not) include / include (configured) events for discarding, clearing, deconfiguring, or releasing a beam report initiated by a UE.

[0850] The one or more actions in response to a beam report initiated by a UE may (or may not) include / include canceling or clearing one or all of the triggers associated with the beam report initiated by the UE.

[0851] The one or more actions in response to a beam report initiated by the UE may (or may not) include / include continuing the (ongoing) beam report initiated by the UE.

[0852] The one or more actions for a beam report initiated by a UE may (or may not) include / include not canceling one (or any) trigger associated with the beam report initiated by the UE.

[0853] The one or more actions related to a UE-initiated beam report may (or may not) include starting or restarting a timer for determining a time period, wherein the UE triggers or transmits a UE-initiated beam report if all measurements during said time period satisfy an event (condition) associated with the UE-initiated beam report. The length of the timer may be set to a configurable value for the event (e.g., timeToTrigger, or ttt).

[0854] The one or more actions related to a UE-initiated beam report may (or may not) include starting or restarting a timer for determining a time period, wherein the UE triggers or transmits a UE-initiated beam report if a certain number of (consecutive) measurements during the time period satisfy an event (condition) associated with the UE-initiated beam report. The length of the timer may be set to a configurable value for the event (e.g., timeToTrigger, or ttt).

[0855] The one or more actions for a beam report initiated by a UE may (or may not) include / include a timeToTrigger reset for events associated with the beam report initiated by the UE or associated with the cell.

[0856] The one or more actions in a beam report initiated by the UE may (or may not) include / include continuing the measurement during the ongoing timeToTrigger time period.

[0857] The one or more actions in response to a UE-initiated beam report may (or may not) include / include re-initializing or recounting the time of satisfying the event within the time period determined by the timeToTrigger of the event associated with the UE-initiated beam report or associated with the cell.

[0858] List of programs

[0859] The one or more procedures may contain / include or correspond to a change in the state of a measurement reference signal (RS) associated with an event (e.g., serving cell deactivation, active BWP change, cell discontinuous transmission (DTX) activity / inactivity time associated with the measurement RS, BFR occurrence).

[0860] The one or more procedures may contain / include or correspond to a status change reported by the UE (e.g., serving cell deactivation, active BWP change, cell discontinuous reception (DRX) activity / inactivity time associated with a UE-initiated report).

[0861] The one or more procedures are associated with a measurement RS related to the event, and / or if the first specific procedure is not associated with the event, the one or more procedures do not contain / include the first specific procedure.

[0862] The one or more procedures are associated with a measurement RS related to the event, and / or the one or more procedures do not contain / include the first specific procedure if the first specific procedure has no effect on or does not make a state change on the measurement RS associated with the event.

[0863] The one or more procedures are associated with a measurement RS related to an event, and / or if a second specific procedure has an effect on or makes a state change on the measurement RS associated with the event, the one or more procedures contain / include a second specific procedure.

[0864] In one instance, the event corresponds to the beam quality of the current beam associated with an RS on a first cell, and the beam quality of candidate beams associated with one or more RSs on a second cell. The first cell may be the same as or different from the second cell. If a first specific procedure does not change the state of an RS (e.g., deactivating a third cell or changing the activity (DL)BWP associated with a third cell), then the one or more procedures do not contain / include the first specific procedure. If a second specific procedure changes the state of an RS (e.g., deactivating the first or second cell, or changing the activity (DL)BWP associated with the first or second cell), then the one or more procedures contain / include the second specific procedure.

[0865] The one or more procedures are associated with a report initiated by a UE related to an event, and / or if the first specific procedure is not associated with an event and / or preferably is not associated with a report initiated by a UE, then the one or more procedures do not contain / include the first specific procedure.

[0866] The one or more procedures are associated with a report initiated by a UE related to an event, and / or the one or more procedures do not contain / include the first specific procedure if the first specific procedure does not affect or make a state change to the report initiated by the UE related to the event.

[0867] The one or more procedures are associated with a report initiated by a UE related to an event, and / or if a second specific procedure has an effect on or makes a state change on a report initiated by a UE related to the event, then the one or more procedures contain / include a second specific procedure.

[0868] In one instance, the event corresponds to the beam quality of the current beam associated with an RS on a first cell and the beam quality of candidate beams associated with one or more RSs on a second cell. The UE may be (pre-)configured with multiple UL resources for transmitting UE-initiated reports. Preferably, in some embodiments, the UE-initiated report is configured on a third cell (and / or a fourth cell). The first cell may be the same as or different from the second cell. If a first specific procedure does not change the state of the UE-initiated report (e.g., deactivating the third cell or changing the activity (UL) BWP associated with a fifth cell), then the one or more procedures do not contain / include the first specific procedure. If a second specific procedure changes the state of the UE-initiated report (e.g., deactivating the third and / or fourth cells, or changing the activity (UL) BWP associated with the third and / or fifth cells), then the one or more procedures contain / include the second specific procedure.

[0869] The one or more procedures may contain / include the activation or deactivation of a cell associated with a beam report initiated by the UE.

[0870] A cell can be a SCell. Beam reports initiated by the UE can be associated with a subcell.

[0871] The one or more procedures may include / include SCG activation or deactivation. UE-initiated beam reports may be associated with PSCells.

[0872] The one or more procedures may contain / include an active DL BWP (or UL BWP) associated with an SCell, the SCell being associated with a beam report initiated by a UE during a handover (e.g., a handover to a dormant BWP).

[0873] The one or more procedures may contain / include an active DL BWP (or UL BWP) associated with a PCell, the PCell being associated with a beam report initiated by a UE during a handover (e.g., switching to a default BWP or another active BWP).

[0874] The one or more procedures may contain / include the expiration / expiration of a timer (e.g., timeAlignmentTimer) associated with a TA (Take-Ahead Group) linked to a Timing Alignment Group (TAG). A TAG may be associated with a cell on which the UE transmits a (UE-initiated) beam report in response to a UE-initiated beam report. A TAG may be associated with the cell to which the UE-initiated beam report is linked.

[0875] The one or more procedures may (or may not) include / include the triggering or initiation of a beam fault recovery procedure on the cell associated with the UE-initiated beam report. Additionally and / or alternatively, in some embodiments, the beam fault recovery procedure may be associated with (a different or second) cell on which the UE transmits the UE-initiated beam report. The one or more procedures may include / include a triggered and uncancelled BFR. The one or more procedures may include / include a random access procedure initiated for beam fault recovery (PCell or SCell). The one or more procedures may include / include triggering a scheduling request (SR) for beam fault recovery (SCell). The one or more procedures may include / include a triggered and uncancelled SR for beam fault recovery. The one or more procedures may include / include the assembly and / or transmission of a BFR MAC CE.

[0876] Alternatively, in some embodiments, the one or more procedures may not include / include a beam fault recovery procedure. The one or more procedures may not include / include a triggered and uncancelled BFR. The one or more procedures may not include / include a random access procedure initiated for (PCell or SCell) beam fault recovery. The one or more procedures may not include / include a SR triggered for (SCell) beam fault recovery. The one or more procedures may not include / include a triggered and uncancelled SR for beam fault recovery. The one or more procedures may not include / include the assembly and / or transmission of the BFR MAC CE.

[0877] The one or more procedures may contain / include a beam-changing procedure (associated with the cell to which the beam report is initiated by the UE). The beam-changing procedure may contain / include receiving a Radio Resource Control (RRC) reconfiguration (message) indicating a reconfiguration of one or more TCI states.

[0878] The beam-changing procedure may include / include receiving TCI state-activated MAC CEs for Physical Downlink Shared Channel (PDSCH) and / or Physical Downlink Control Channel (PDCCH) and / or PUCCH and / or Physical Uplink Shared Channel (PUSCH). TCI state-activated MAC CEs may be used for DL ​​and / or UL beam-changing.

[0879] Alternatively, in some embodiments, the one or more procedures may not contain / include beam-changing procedures.

[0880] Additionally and / or alternatively, in some embodiments, the one or more procedures may contain / initiate a random access procedure. A random access procedure may be initiated for reconfiguration with synchronization. A random access procedure may be initiated for an LTM procedure.

[0881] Alternatively, in some embodiments, the one or more procedures may not contain / include a random access procedure.

[0882] Additionally and / or alternatively, in some embodiments, a random access procedure may be initiated for early UL synchronization of candidate cells.

[0883] The one or more procedures may (or may not) include a MAC reset. Alternatively, in some embodiments, the one or more procedures may not include a MAC reset.

[0884] The one or more procedures may (or may not) include / include serving cell deactivation. Alternatively, in some embodiments, the one or more procedures may not include / include serving cell deactivation. Serving cell deactivation may include / include receiving a SCell activation / deactivation MAC CE. Serving cell deactivation may include / include the expiration of a SCell deactivation timer. The serving cell may be associated with a beam report (associated with a measurement object) initiated by the UE.

[0885] The one or more procedures may (or may not) contain / include beam reports initiated or requested by the network. Beam reports may be cell-associated (periodic, non-periodic, or semi-persistent) CSI reports.

[0886] Program for LTM candidates

[0887] The one or more procedures may (or may not) contain / include a synchronized handover or reconfiguration procedure. The one or more procedures may contain / include an LTM procedure for handing over to a cell associated with a UE-initiated beam report (e.g., receiving an LTM cell handover command MAC CE). Alternatively, in some embodiments, the one or more procedures may (or may not) contain / include an LTM procedure for handing over to a cell not associated with a UE-initiated beam report (e.g., handing over to another LTM candidate cell).

[0888] The one or more procedures may (or may not) contain / include an ongoing reconfiguration procedure with synchronization. Additionally and / or alternatively, in some embodiments, the one or more procedures may (or may not) contain / include an ongoing LTM procedure (to the cell or another cell associated with the beam report initiated by the UE).

[0889] The one or more procedures may contain / include a beam-changing procedure (associated with the SpCell of the cell associated with the UE-initiated beam report). The beam-changing procedure may contain / include receiving an RRC reconfiguration (message) indicating a reconfiguration of one or more TCI states. The SpCell may be associated with or may be configured with an LTM candidate associated with the cell associated with the UE-initiated beam report.

[0890] The one or more procedures may (or may not) include / include the reconfiguration or release of candidate cells.

[0891] The one or more procedures may (or may not) contain / include TCI state activation or deactivation associated with the cell. The cell may be an LTM candidate cell associated with a beam report initiated by the UE. The cell may be a PCell or SpCell (e.g., an LTM candidate) of an LTM candidate configuration.

[0892] The one or more procedures may contain / include a change in the activated TCI state of a cell. The cell may be an LTM candidate cell associated with a UE-initiated beam report. The one or more procedures may (or may not) contain / include a candidate cell TCI state activation / deactivation MAC CE receiving an indication ltm-CandidateId (e.g., indicating ltm-CandidateId or indicating ltm-CandidateId-1), where ltm-CandidateId is associated with the cell associated with the UE-initiated beam report. The candidate cell TCI state activation / deactivation MAC CE may indicate a change (e.g., activation / deactivation) in the TCI state associated with the cell associated with the UE-initiated beam report.

[0893] Additionally and / or alternatively, in some embodiments, the one or more procedures may contain / include a change in the activated TCI state (e.g., activation / deactivation) associated with at least a UE-initiated beam report (event). Additionally and / or alternatively, in some embodiments, the one or more procedures may contain / include a change in the (newly deactivated) TCI state (e.g., activation / deactivation) associated with a UE-initiated beam report (event or measurement object).

[0894] Network energy saving (NES) reported by the UE on the cell / measured on the cell.

[0895] Additionally and / or alternatively, in some embodiments, the one or more procedures may contain / include a cell not in the cell DRX activity cycle. The cell may be associated with a UE-initiated beam report. Alternatively, in some embodiments, the cell may be a cell on which the UE transmits a (UE-initiated) beam report associated with a UE-initiated beam report. The cell may not be in the cell DRX activity cycle during the time period or when the UE is configured or available to transmit a report. The cell may not be in the cell DRX activity cycle during the time period or when the UE triggers a report or performs a measurement in response to a UE-initiated beam report.

[0896] Different handling of beam reports initiated by different types of UEs: for LTM (for candidate cells) or for... Service Community

[0897] Events can be associated with the serving cell. Additionally and / or alternatively, in some embodiments, events can be associated with candidate cells.

[0898] Additionally and / or alternatively, in some embodiments, the UE may determine whether to perform one or more actions in response to a UE-initiated beam report associated with the cell, based at least on the cell type or at least on the type or purpose of the beam report initiated by the UE.

[0899] Beam reports initiated by a UE associated with the serving cell can be used for MIMO (enhanced), (intra-cell and / or inter-cell) beam management.

[0900] Beam reports initiated by UEs associated with candidate cells can be used for LTM.

[0901] For example, a UE may perform one or more of the actions (e.g., a UE-initiated beam report initiated or triggered based on a comparison between the quality of the current beam of the serving cell and a candidate beam of the serving cell) in response to one or more procedures associated with the serving cell. A UE may not (is not permitted to) perform one or more of the actions (e.g., in response to a reconfiguration procedure with synchronization or in response to an LTM procedure) in response to a beam report initiated by a UE associated with a candidate cell (or LTM).

[0902] For example, a UE may (re)start, reset, or stop a timer or counter (e.g., timeToTrigger) associated with a beam report initiated by a UE associated with the serving cell in response to one or more procedures associated with the serving cell. A UE may not (be allowed to) (re)start, reset, or stop a timer or counter (e.g., timeToTrigger) associated with a beam report initiated by a UE associated with a candidate cell (or LTM) in response to one or more procedures (e.g., in response to a reconfiguration procedure with synchronization or in response to an LTM procedure).

[0903] In another instance, the UE can reset a counter associated with a beam report initiated by the first UE in the serving cell in response to a beam change of the current beam in the serving cell. This counter can be used to trigger a beam report initiated by the first UE in the serving cell. The UE can stop a first timer or treat the first timer as expired in response to a beam change of the current beam in the serving cell. The first timer can be a time period or time window associated with the beam report initiated by the first UE. The beam report initiated by the first UE can be associated with a candidate beam and the current beam associated with the serving cell. The beam report initiated by the first UE may not be associated with LTM.

[0904] The UE can reset or restart a second timer associated with a beam report initiated by a second UE in a candidate cell without responding to a beam change in the current beam. The second timer can be a timeToTrigger(ttt) associated with the beam report initiated by the second UE in the candidate cell. ttt can be a time period during which an event needs to be met to trigger a measurement report. The event can be that the quality of the candidate beam is higher than the quality of the current beam plus a threshold. The beam report initiated by the second UE can be associated with a candidate beam of the candidate cell and the current beam of the serving cell. The beam report initiated by the second UE can be an L1 measurement report triggered by an event associated with LTM.

[0905] Figure 13B An example is shown below. The UE can be configured with UE-initiated beam reporting settings associated with the serving cell (e.g., for MIMO). The UE can be configured with a time window and a maximum number of instances (e.g., maxcount = 3), and can maintain counters for calculating the instances of UE-initiated beam reports (for candidate beams and / or for the serving cell). The UE can receive an instance indication at time t1 indicating that the quality of the new beam A is greater than the quality of the current beam B plus a threshold. At time t2, the network can instruct the UE to perform a beam change from the current beam B to beam C. The UE can reset the counters associated with the UE-initiated beam reports of the serving cell in response to the beam change.

[0906] Additionally and / or alternatively, in some embodiments, the UE may perform one or more actions in response to one or more procedures (as associated with the candidate cell) (e.g., in response to a reconfiguration procedure with synchronization or in response to an LTM procedure) for a beam report initiated by the UE associated with the candidate cell. The UE may also perform one or more actions in response to a beam report initiated by the UE associated with the serving cell without responding to one or more procedures associated with the serving cell.

[0907] Additionally and / or alternatively, in some embodiments, the UE may (re)start, reset, or stop a timer or counter (e.g., associated with timeToTrigger) associated with a beam report initiated by the UE associated with the candidate cell in response to one or more procedures (e.g., in response to a reconfiguration procedure with synchronization or in response to an LTM procedure). The UE may (re)start, reset, or stop a timer or counter (e.g., associated with timeToTrigger) associated with a beam report initiated by the UE associated with the serving cell without responding to one or more procedures associated with the serving cell.

[0908] Conflict with one or more procedures while beam reporting is in progress

[0909] For example, a UE may suspend events associated with UE-initiated beam reports related to a cell in response to cell deactivation. Additionally and / or alternatively, in some embodiments, a UE may resume events in response to cell activation. A UE may cancel or discard triggered UE-initiated beam reports (or reports) in response to cell deactivation. Preferably, in some embodiments, the cell corresponds to a cell having a measurement RS associated with the event (associated with the UE-initiated beam report) (e.g., a cell including / containing RSs for measuring the current beam or one or more candidate beams). Preferably, in some embodiments, the cell corresponds to a cell having UE-initiated reports associated with the event (e.g., a cell including / containing reports initiated by a UE associated with the (triggered and uncancelled) event).

[0910] Additionally and / or alternatively, in some embodiments, the UE may disable beam reporting that triggers events associated with beam reporting initiated by the UE.

[0911] Figure 14 An example is shown. At time t1, the UE measures the cell A (or its associated RS) associated with the beam report initiated by the UE. Preferably, in some embodiments, or additionally, in Figure 14In the event t1, the UE triggers an event and determines or attempts to transmit a UE-initiated report on cell A. The UE may be configured with UE-initiated beam reports associated with cell A. The UE determines that the quality of the new beam associated with cell A is a threshold better than the current beam of cell A (e.g., satisfying the conditions of the event associated with cell A). The UE may maintain a timer or counter for detecting / determining whether the conditions of the event are satisfied within a time period (e.g., the same length as timeToTrigger, ttt). In the event t2, the UE receives a Revocation Activation MAC CE indicating the revocation of cell A. In response to receiving the revocation activation of cell A, the UE may stop the accumulation of the timer / counter associated with the ttt of the UE-initiated beam report. If (e.g., before t2) a trigger associated with the UE-initiated beam report has been triggered, the UE may cancel the trigger in response to the revocation activation of cell A. When cell A is reactivated, the UE may not consider the conditions of the event to be satisfied. When cell A is reactivated, the UE may not trigger the UE-initiated beam report. At time t3, the UE receives an activation MAC CE for cell A. In response to cell activation, the UE can resume the UE-initiated beam report. The UE can start or restart a timer or counter for ttt in response to cell activation. The value of the timer can be continued / resumed from the last time cell A was deactivated. For example, the UE can trigger the UE-initiated beam report at t4 if or when the sum of time periods [t1, t2] and [t3, t4] is equal to (or greater than) the timeToTrigger associated with the UE-initiated beam report. Alternatively, in some embodiments, the UE can reset the timer value in response to cell A deactivation (time t2).

[0912] for Figure 15In another example shown, the UE can perform a measurement (RS) on cell B. Cell B can be a serving cell or a candidate cell. At time t1, the UE discovers or determines that the quality of the activated TCI state A is below a threshold (e.g., the condition of an event is met), which is an example but not limited to this event. Preferably, in some embodiments, at time t1, the UE discovers or determines that a triggering event is met (e.g., the condition of an event is met). The UE can maintain a timer or counter (e.g., ttt) for determining whether the condition of an event is met within the timeToTrigger time period. At time t2, the UE receives a TCI state activation / deactivation MAC CE indicating the activation of TCI state C (and / or the deactivation of TCI state A) of cell B. In response to the MAC CE, the UE can stop or restart the timer used for timeToTrigger. The UE can treat UE-initiated beam reports for cell B (generated before t2) as invalid. The UE can cancel UE-initiated beam reports triggered by cell B.

[0913] for Figure 16 In another example shown, the UE can measure cell C (or its associated RS) and, at time t1, determine that the quality of the activated TCI state A is less than a threshold for cell C (e.g., the conditions of an event are met). This is an example, but not limited to, event t1. Preferably, in some embodiments, at time t1, the UE discovers or determines that an event is triggered (e.g., the conditions of an event are met). The UE can trigger a UE-initiated beam report for cell C (if the conditions of an event are met within the time period ttt). The UE can be configured to transmit the UE-initiated beam report for cell C on cell D. Cell D can be configured with cell-level power saving and is not in a cell DRX activity cycle during the time period (t3, t4). When cell D is not in a cell DRX activity cycle or in response to cell D not being in a cell DRX activity cycle, the UE can suspend (e.g., avoid) the triggering of UE-initiated beam reports. When cell D is not in a cell DRX activity cycle, the UE can not generate UE-initiated beam reports.

[0914] In another instance, if or when the TA timer associated with the second cell expires, the UE can cancel the cell-triggered UE-initiated beam report. The UE can be instructed or configured to transmit the cell-triggered UE-initiated beam report on the second cell.

[0915] For example, a UE can cancel or stop a UE-initiated beam report (triggered or in progress) in response to a BFR trigger. A UE can cancel or stop a UE-initiated beam report in the first serving cell (triggered or in progress) in response to a BFR trigger in the first serving cell. A UE can cancel or stop a UE-initiated beam report in the first serving cell without responding to a BFR trigger in the second serving cell.

[0916] In another instance, when there is a beam report initiated by a UE (triggered or in progress) associated with at least the serving cell, the UE may not trigger a BFR for the serving cell.

[0917] In another instance, the UE may (re)start, reset, or stop a timer or counter associated with a beam report initiated by the UE in the cell (BWP) in response to the triggering of the BFR of the first serving cell (BWP).

[0918] In another instance, the UE may (re)start, reset, or stop the timer or counter associated with the UE-initiated beam report of the cell (BWP) in response to the (successful) completion of the beam fault recovery procedure associated with the BFR triggered by the first serving cell (BWP).

[0919] In another instance, the UE can cancel or stop a UE-initiated beam report (triggered or in progress) in response to a beam-changing procedure. The UE can cancel or stop a UE-initiated beam report (triggered or in progress) in the first serving cell (BWP) in response to a beam-changing procedure of the first serving cell. The UE can cancel or stop a UE-initiated beam report in the first serving cell without responding to a beam-changing procedure of the second serving cell. The UE can cancel or stop a UE-initiated beam report in the first serving cell's first BWP without responding to a beam-changing procedure of the second BWP of the first serving cell.

[0920] In another instance, the UE can (re)start, reset, or stop a timer or counter associated with a beam report initiated by the UE in the first serving cell (BWP) in response to a beam change procedure of the first serving cell (BWP). The timer or counter can be used or configured to trigger or disable beam reports initiated by the UE in the cell.

[0921] In another instance, when there is a (triggered or ongoing) beam report initiated by a UE associated with at least the serving cell (BWP), the UE may not perform the beam changing procedure for the serving cell (BWP).

[0922] In another instance, the UE may cancel or stop a UE-initiated beam report (triggered or in progress) in response to the initiation of a random access procedure. The UE may cancel or stop a UE-initiated beam report for the first serving cell (or first candidate cell) in response to the initiation of a random access procedure associated with the first serving cell (or first candidate cell). The UE may not cancel or stop a UE-initiated beam report for the first serving cell (of the first candidate cell) without responding to the initiation of a random access procedure not associated with the first serving cell (of the second candidate cell).

[0923] In another instance, when or if there is a (triggered or ongoing) beam report initiated by a UE associated with at least the serving cell (or candidate cell), the UE may not initiate a random access procedure for the serving cell (or candidate cell) (for early UL synchronization).

[0924] In another instance, a UE can cancel or stop (triggered or ongoing) UE-initiated beam reporting in response to a MAC reset (initiated). A UE can cancel or stop (triggered or ongoing) UE-initiated beam reporting for a first serving cell in response to a MAC reset associated with the MAC entity of the first serving cell. A UE can also cancel or stop UE-initiated beam reporting for a first serving cell without responding to a MAC reset not associated with the first serving cell.

[0925] In another instance, the UE can (re)start, reset, or stop the timer or counter associated with the UE-initiated beam report of the cell (BWP) in response to a MAC reset associated with the cell.

[0926] In another instance, when there is a beam report initiated by a UE (triggered or in progress) associated with at least the serving cell, the UE may not perform a MAC reset associated with the serving cell.

[0927] In another instance, the UE can cancel or stop (triggered or ongoing) UE-initiated beam reporting in response to SCell deactivation (triggering). The UE can cancel or stop (triggered or ongoing) UE-initiated beam reporting in the first serving cell in response to deactivation of the first serving cell (or in response to receiving a deactivation MAC CE for deactivation of the first serving cell, or in response to the expiration of the SCell deactivation timer for the first serving cell). The UE can cancel or stop UE-initiated beam reporting in the first serving cell without responding to deactivation of the second serving cell.

[0928] In another instance, the UE can (re)start, reset, or stop the timer or counter associated with the UE-initiated beam report of the cell (BWP) in response to the cell's reactivation (trigger).

[0929] In another instance, the UE can (re)start, reset, or stop timers or counters associated with UE-initiated beam reports for the cell (BWP) in response to cell activation (triggering).

[0930] In another instance, the UE can (re)start, reset, or stop the timer or counter associated with the UE-initiated beam report of the cell (BWP) in response to the (successful) completion of the cell's reactivation.

[0931] In another instance, when there is a beam report initiated by a UE associated with at least the serving cell (triggered or in progress), the UE may not perform the reactivation of the serving cell.

[0932] In another instance, the UE may cancel or stop a (triggered or ongoing) UE-initiated beam reporting for the first serving cell in response to receiving an aperiodic CSI report request associated with the first serving cell from the network. Alternatively, in some embodiments, the UE may not cancel or stop a (triggered or ongoing) UE-initiated beam reporting for the first serving cell when receiving an aperiodic CSI report request associated with the first serving cell from the network.

[0933] In another instance, the UE may cancel or stop a (triggered or ongoing) UE-initiated beam report for the first serving cell in response to the initiation of a synchronized reconfiguration procedure or in response to receiving a synchronized reconfiguration message from the network. Alternatively, in some embodiments, the UE may cancel or stop a (triggered or ongoing) UE-initiated beam report for the first serving cell without responding to the initiation of a synchronized reconfiguration procedure or in response to receiving a synchronized reconfiguration message from the network (not associated with the first serving cell).

[0934] In another instance, the UE may cancel or stop a (triggered or ongoing) UE-initiated beam report for the first serving cell in response to the initiation of an LTM procedure or in response to receiving an LTM cell handover command MAC CE from the network. Alternatively, in some embodiments, the UE may cancel or stop a (triggered or ongoing) UE-initiated beam report for the first serving cell without responding to the initiation of an LTM procedure or in response to receiving an LTM cell handover command MAC CE from the network (not associated with the first serving cell).

[0935] Figure 17An example is shown below. At time t1, the UE triggers a UE-initiated beam report for serving cell A (e.g., because the current beam quality is below a threshold). At time t2, the UE receives a beam change indication associated with serving cell A from the network (e.g., TCI state activation / deactivation of MAC CE or TCI state RRC reconfiguration). In response to the beam change indication, the UE cancels or stops triggering the UE-initiated beam report.

[0936] The first procedure is in progress and no report is triggered.

[0937] Additionally and / or alternatively, in some embodiments, the UE may determine whether to trigger, initiate, or execute a UE-initiated beam report based on the existence of at least one or more ongoing procedures. If or when (at least) one or more ongoing procedures associated with the serving cell exist, the UE may not trigger, initiate, or execute a UE-initiated beam report for the serving cell.

[0938] For example, if at least a triggered (and uncancelled) BFR exists, the UE may not (be allowed to) trigger, initiate, or execute a UE-initiated beam report. If at least a triggered (and uncancelled) BFR exists in the serving cell, the UE may not (be allowed to) trigger a UE-initiated beam report in the serving cell. If at least no triggered BFR exists in the first serving cell, the UE may trigger a UE-initiated beam report in the first serving cell.

[0939] For another instance, if or if (at least) an ongoing beam fault recovery procedure associated with the cell exists, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. For example, when the ra-responswindow and / or contention resolution timer is running, the UE may not trigger, initiate, or execute a UE-initiated beam report. If or if (at least) no ongoing beam fault recovery procedure exists for the first serving cell, the UE may trigger a UE-initiated beam report for the first serving cell. The ongoing beam fault recovery procedure may include a random access procedure (initiated for beam fault recovery). The ongoing beam fault recovery procedure may include a triggered and uncancelled SR associated with the beam fault recovery (e.g., an SR triggered for a SCell BFR).

[0940] Additionally and / or alternatively, in some embodiments, when or if (at least) an ongoing random access procedure associated with the cell exists, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. Alternatively, in some embodiments, when or if (at least) an ongoing random access procedure associated with the cell is not initiated for beam fault recovery, the UE may trigger, initiate, or execute a UE-initiated beam report for the cell.

[0941] Additionally and / or alternatively, in some embodiments, when or if (at least) an ongoing beam-changing procedure (as associated with the cell) exists, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. Alternatively, in some embodiments, when or if (at least) an ongoing beam-changing procedure is not associated with the cell, the UE may trigger, initiate, or execute a UE-initiated beam report for the cell.

[0942] Additionally and / or alternatively, in some embodiments, when or if (at least) an ongoing MAC reset procedure (associated with the cell) exists, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. Alternatively, in some embodiments, when or if (at least) an ongoing MAC reset is not associated with the cell, the UE may trigger, initiate, or execute a UE-initiated beam report for the cell.

[0943] Additionally and / or alternatively, in some embodiments, when or if (at least) an ongoing serving cell deactivation procedure (as associated with the cell) exists, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. Alternatively, in some embodiments, when or if (at least) an ongoing serving cell deactivation procedure is not associated with the cell, the UE may trigger, initiate, or execute a UE-initiated beam report for the cell.

[0944] Additionally and / or alternatively, in some embodiments, when or if (at least) there is an ongoing synchronized reconfiguration procedure (associated with the cell), the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. Alternatively, in some embodiments, when or if (at least) an ongoing synchronized reconfiguration procedure is not associated with the cell (e.g., associated with another cell group from the cell), the UE may trigger, initiate, or execute a UE-initiated beam report for the cell.

[0945] In another instance, the UE may trigger a beam report initiated by the UE of the first serving cell without responding to an ongoing LTM procedure or in response to receiving an LTM cell handover command MAC CE from the network. Alternatively, in some embodiments, the UE may trigger a beam report initiated by the UE of the first serving cell without responding to an ongoing LTM procedure or in response to receiving an LTM cell handover command MAC CE from the network (not associated with the first serving cell).

[0946] Figure 18 An example is shown below. At time t1, the UE initiates a beam fault recovery procedure for serving cell A (e.g., SpCell). The beam fault recovery procedure may contain / include a random access procedure for serving cell A. The UE performs a random access preamble transmission to the network in the random access procedure. In response to the preamble transmission, the UE starts a window / timer (e.g., a random access response window). During the window period / while the timer is running, at time t2, the conditions for a UE-initiated beam report (as associated with serving cell A) are met (e.g., the quality of the currently active beam is below a threshold and / or the quality of a candidate beam is above a threshold). Because the window / timer is running and / or because there is an ongoing random access procedure (for serving cell A beam fault recovery), the UE may not initiate or may trigger a UE-initiated beam report.

[0947] parallel

[0948] Additionally and / or alternatively, in some embodiments, the UE may perform UE-initiated beam reporting for the cell while one or more of the procedures are in progress. For example, if or when (at least) a cell deactivation indication is received, the UE may not cancel or stop UE-initiated beam reporting associated with the cell.

[0949] Different handling of beam reports initiated by different types of UEs: for LTM (for candidate cells) or for... Service Community

[0950] Additionally and / or alternatively, in some embodiments, when or if (at least) one or more procedures are in progress, the UE may determine whether to trigger, initiate, or execute a UE-initiated beam report based on at least the type or purpose of the UE-initiated beam report. For example, when or if (at least) one of the one or more procedures is in progress, the UE may initiate or execute a UE-initiated beam report for LTM or for a candidate cell. In another instance, when or if (at least) one of the one or more procedures is in progress, the UE may not execute a UE-initiated beam report for the serving cell.

[0951] For example, when or if (at least) one or more procedures are in progress (e.g., BFR, beam change procedure, MAC reset or handover, or LTM procedure), the UE may trigger, initiate, or execute a UE-initiated beam report for LTM or for L1 measurement reporting of candidate cells. When or if (at least) one or more procedures are in progress (e.g., BFR, beam change procedure, MAC reset or handover, or LTM procedure), the UE may not trigger, initiate, or execute a UE-initiated beam report for the serving cell.

[0952] Alternatively, in some embodiments, when or if (at least) one or more procedures in progress (e.g., BFR, beam change procedure, MAC reset or handover, or LTM procedure), the UE may not trigger, initiate, or execute UE-initiated beam reporting for LTM or L1 measurement reporting for candidate cells. When or if (at least) one or more procedures in progress (e.g., BFR, beam change procedure, MAC reset or handover, or LTM procedure), the UE may trigger, initiate, or execute UE-initiated beam reporting for the serving cell.

[0953] Figure 19 An example is shown. At time t1, the UE initiates or executes a random access procedure (e.g., handover, reconfiguration with synchronization, or LTM). The UE performs a preamble transmission and initiates a random access response window. While the window is running at time t2, the conditions for a UE-initiated beam report for the serving cell are met. The UE does not trigger a UE-initiated beam report. At time t3, the conditions for a UE-initiated beam report for the candidate cell are met, and the UE can trigger a UE-initiated beam report for the candidate cell while the window is running.

[0954] Prioritization between beam reports initiated by different types of UEs

[0955] Additionally and / or alternatively, in some embodiments, the UE may determine whether to prioritize the beam report initiated by the first UE or the beam report initiated by the second UE based on the type of the beam report initiated by at least the first UE and the second UE.

[0956] One type of UE-initiated beam report can be a report for candidate cells or LTM. Another type of UE-initiated beam report can be a report for the serving cell.

[0957] For example, a UE may prioritize a beam report initiated by a first UE associated with or in response to a candidate cell (or LTM) over a beam report initiated by a second UE associated with the serving cell.

[0958] Alternatively, in some embodiments, the UE may prioritize a beam report initiated by a first UE associated with or in response to a serving cell over a beam report initiated by a second UE associated with a candidate cell (or LTM).

[0959] Additionally and / or alternatively, in some embodiments, the UE may be configured with a priority associated with UE-initiated beam reports. For example, the network may configure the UE to prioritize UE-initiated beam reports for the serving cell (over candidate cells), or the network may configure the UE to prioritize UE-initiated beam reports for candidate cells (over the serving cell). Alternatively, in some embodiments, each of the measurement objects (e.g., serving cell, candidate cell) may be configured with a priority for UE-initiated beam reports.

[0960] Various examples and embodiments of the invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[0961] Beam reports initiated by the UE can be CSI reports. Beam reports initiated by the UE can also be event-driven beam reports.

[0962] A UE-initiated beam report (procedure) for a cell may contain / include measurements of the RS (Representative Scale) on the cell. A UE-initiated beam report (procedure) for a cell may contain / include determining the beam quality of the cell that satisfies one or more events associated with the cell (the measurement object) within a certain time period. A UE-initiated beam report may contain / include triggering the UE-initiated beam report when one or more events have been satisfied within a certain time period (alternatively, in some embodiments, the UE may trigger the UE-initiated beam report (immediately) when one or more events (conditions) have been satisfied).

[0963] The measurement object associated with a beam report initiated by the UE can be associated with a cell and / or a TCI status or beam associated with the cell. The measurement object can be configured with an event or associated with an event.

[0964] A beam report initiated by the UE can be triggered or initiated in response to the fulfillment of one or more conditions.

[0965] The one or more conditions may include / include conditions associated with beam quality. For example, a condition may be that the quality of the (currently) active beam is less than or equal to a threshold. Additionally and / or alternatively, in some embodiments, a condition may be that the quality of a candidate beam is greater than or equal to a threshold. The one or more conditions may be associated with or based on a measurement report trigger event.

[0966] Additionally and / or alternatively, in some embodiments, the condition may include / include that the candidate beam quality is higher than or equal to the (currently) active beam quality (for a period of time, e.g., timeToTrigger).

[0967] A beam report initiated by a UE may contain / include a determination of whether to trigger a report based on at least the measured beam quality.

[0968] Conditions can be associated with (configured) events.

[0969] An event could be a threshold where the quality of a new (measured) beam in the cell is better than that of the current beam.

[0970] An event could be that the quality of the current beam is below a threshold.

[0971] An event could be that the quality of the new (measured) beam in the cell is better than the threshold (+offset).

[0972] An event can be associated with the eventId in EventTriggerConfig.

[0973] Preferably, in some embodiments, the current beam corresponds to RS in the indicated TCI state, which corresponds to Quasi-Co-located (QCL) type D.

[0974] Preferably, in some embodiments, the current beam corresponds to a synchronization signal block (SSB), which is associated with an RS in the indicated TCI state corresponding to QCL type D.

[0975] Preferably, in some embodiments, the current beam corresponds to RS in an activated TCI state, which corresponds to QCL type D (having the worst or best beam quality among more than one activated TCI state).

[0976] Preferably, in some embodiments, more than one activated TCI state is activated by MAC CE through TCI state (revocation).

[0977] Preferably, in some embodiments, the indicated TCI state or activated TCI corresponds to the DL or combined TCI state. Beam quality may include beam-associated RSRP, Reference Signal Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), and / or Signal-to-Interference-Noise Ratio (SINR).

[0978] A beam report initiated by a UE may contain / include (the report's) trigger.

[0979] The beam report initiated by the UE may contain / include triggering and / or transmitting SR.

[0980] The beam report initiated by the UE may contain / include the initiation of a random access (RA) procedure.

[0981] The beam report initiated by the UE may contain / include an assembled beam report (e.g., the beam report may be a MAC CE and / or RRC message and / or PUCCH signal).

[0982] The beam report initiated by the UE may include / include transmitting the beam report to the network.

[0983] Beam reports can be initiated and / or configured to be initiated by the UE for the serving cell. Additionally and / or alternatively, in some embodiments, beam reports can be initiated and / or configured to be initiated by the UE for a candidate cell or a non-serving cell.

[0984] A UE-initiated beam report may be an L1 measurement report triggered by an event associated with LTM. Alternatively, in some embodiments, a UE-initiated beam report may not be associated with LTM (and / or may be associated with the serving cell).

[0985] The beam report initiated by the UE may contain / include the triggering of the beam report cancellation.

[0986] A UE-initiated beam report for a cell may contain / include measurements of the cell's (BWP). A UE-initiated beam report may contain / include the triggering of a UE-initiated beam report. A UE-initiated beam report may contain / include the generation and / or transmission of a UE-initiated beam report (at least associated with the cell).

[0987] The UE can cancel a beam report initiated by the UE in response to the initiation of one or more procedures.

[0988] The UE can cancel a UE-initiated beam report in response to an acknowledgment of the beam report from the network. The acknowledgment may be a new transmission of UL permission associated with the Hybrid Automatic Repeat Request (HARQ) process used to transmit the beam report. The acknowledgment may be a beam activation / deactivation MAC CE. Additionally and / or alternatively, in some embodiments, the UE can cancel a UE-initiated beam report (associated with the cell) in response to the transmission of the corresponding UE-initiated beam report (report information associated with the cell).

[0989] When a beam report initiated by a UE is canceled or stopped, the UE can stop the corresponding procedure contained in the beam report (mentioned above).

[0990] When a UE-initiated beam report is canceled or stopped, the UE can stop or restart the timer used to calculate or determine whether to trigger the UE-initiated beam report (e.g., a timeToTrigger-like timer).

[0991] Cancellation or cessation of a UE-initiated beam report may include / include stopping the random access procedure. Additionally and / or alternatively, in some embodiments, cancellation or cessation of a UE-initiated beam report may include / include stopping one or more timers associated with the UE-initiated beam report (e.g., timeToTrigger for beam reporting or timers associated with the random access procedure and / or with the SR).

[0992] The cancellation or cessation of beam reports initiated by the UE in a cell may include / include information (beams) that is not included in or reported in the UE-initiated beam reports related to the cell.

[0993] Cancellation or cessation of beam reports initiated by a UE in a cell may include (re)starting, resetting, or stopping timers or counters associated with beam reports initiated by a UE in a cell.

[0994] Timers or counters can be used or configured to trigger or disable beam reports initiated by the UE in a cell. Timers or counters can be used to determine or detect whether an event is met within a time period. An event is considered met if, for example, the quality of a new beam is greater than or equal to the quality of the current beam plus a threshold. An event is considered met, or a beam report initiated by the UE can be triggered, if the number of instances is greater than or equal to a threshold within the time period. Instances can be associated with the quality of a new or candidate beam and / or the quality of the current beam / indicated beam. For example, an instance can be indicated by the UE's physical layer if or when the quality of a new beam is greater than or equal to the quality of the current beam plus a threshold. Counters can be maintained for the cell and / or for the new, candidate, or current beam.

[0995] The UE can be configured with measurement objects associated with beam reports initiated by the UE.

[0996] The measurement object may contain / include serving cells and / or non-serving cells.

[0997] The measurement object may be associated with the SSB and / or Channel State Information Reference Signal (CSI-RS) associated with the serving cell and / or non-serving cell.

[0998] In order to prioritize beam reports initiated by the UE over one or more procedures, the UE stops the procedure and continues reporting.

[0999] In order to prioritize the first or more procedures over the beam report initiated by the UE, the UE stops / cancels the report and continues the one or more procedures.

[1000] The report and the first one or more procedures may overlap in the time domain.

[1001] Reports and procedures may be associated with the same serving cell and / or the same MAC entity and / or the same cell group (e.g., primary cell group (MCG) or SCG).

[1002] The beam can be replaced by SSB, CSI-RS and / or (DL or UL) TCI states, or referred to as SSB, CSI-RS and / or (DL or UL) TCI states.

[1003] A cell can be a serving cell, a candidate cell, and / or a neighboring cell.

[1004] Candidate cells can be LTM candidate cells. Neighboring cells can be cells associated with the measurement object. Candidate cells and neighboring cells are not serving cells.

[1005] A UE-initiated beam report (generated in response to a UE-initiated beam report) can be a MAC CE and / or uplink control information (UCI) on PUCCH signaling and / or PUSCH. A UE-initiated beam report can indicate at least one of the measurement objects associated with the UE-initiated beam report or the associated cell.

[1006] Regarding the container carrying UE-initiated reports, MAC CE or UCI can be considered. MAC CE may have latency due to the need for UL approval for transmission. On the other hand, UCI may require network nodes to configure multiple periodic UL resources for transmission. However, the UE will only use a portion of these periodic UL resources to transmit UE-initiated reports (i.e., when event conditions are met). To address this, a pre-notification (PN) can be used to at least indicate the future use of one or more periodic UL resources associated with a UE-initiated report. Depending on whether a UE-initiated report is transmitted on a periodic UL resource, whether a UE-initiated report is triggered, or whether there are pending UE-initiated reports, the UE determines whether to transmit a PN and / or set a PN to indicate the use of the periodic UL resource. In one instance, when a UE-initiated report is not triggered, or the UE will not use periodic UL resources to transmit a UE-initiated report, or there are no pending UE-initiated reports, the UE may skip transmitting a PN and / or not use the periodic UL resource. Typically, a PN can be a sequence-based signal indicating the future use of one or more periodic UL resources. In one instance, the sequence-based signal could be a Sound Reference Signal (SRS) or SR or PUCCH format 0, which in one instance has different cyclic shifts mapped to “used” or “unused”. If more information needs to be carried in addition to used / unused, PUCCH format 0 or other PUCCH formats (e.g., PUCCH formats 1, 2, 3, or 4) with more cyclic shifts could be considered. While the PN can be transmitted along with UL resources for UE-initiated reports, similar to CG-UCI on a PUSCH configured to grant uplink control information (CG-UCI) indicating future use of CG PUSCH resources, this may not be useful because the triggering is more dynamic and not periodic. The PN can be considered as transmitted as a UL resource along with the same Transmission Time Interval (TTI). The PN can be transmitted as a UL resource in different Orthogonal Frequency Division Multiplexing (OFDM) symbols. A set of adjacent OFDM symbols in the TTI can be used as a PN region to carry the PN (e.g., symbols 1 and / or 2 in the TTI (e.g., symbols 0 and 1 in the time slot)). A PN area can be shared by multiple UEs. Alternatively, in some embodiments, a PN area can be dedicated to a UE. Alternatively, in some embodiments, one or more PNs are dedicated to a UE. Alternatively, in some embodiments, a second or more PNs are shared by the UEs. Typically, to achieve better resource efficiency in a network node, a time gap or constraint is required between the PN and the corresponding UL resource. The time gap or constraint is used to ensure that the network node has sufficient time for handover and / or for other purposes.

[1007] Regarding the introduction of UEI reports, there are two modes for resource allocation for UEI reports. Mode A corresponds to dynamic scheduling, and Mode B corresponds to (pre)configured resources for transmitting UEI reports.

[1008] In Mode A, the UE will transmit a scheduling request to the network node. After the scheduling request is transmitted, the UE monitors the downlink control information (DCI) using the scheduling information (and / or the request to resolve the UEI report). The UE transmits the UEI report on the resources scheduled by the DCI.

[1009] For Mode B, a PN (Pre-Configured Node) is used to notify the use of (pre-)configured resources, which can enhance resource efficiency for latency reduction when more (pre-configured) resources are deployed. Typically, the PN resource and the (pre-)configured resource are configured in different instances / timings / TTIs. Alternatively, in some embodiments, the PN resource and the (pre-)configured resource are configured in the same instance / timing / TTI. Once the event conditions are met, the UE triggers the event and / or the UE triggers the transmission of a UEI report.

[1010] The UEI report is pending before the UE transmits it. The UEI report is pending before the UE cancels the event. The UEI report is pending before the UE receives a response from the network node. The UEI report is pending until the event's delay limit expires.

[1011] For a pending UEE report, in Mode A, the UE will determine or select a valid resource. The UE will transmit a scheduling request on the determined / selected resource. The UE will monitor the DCI using scheduling information (and / or using the request for the pending UEE report). The DCI may indicate whether the request is for a request for a UEE report or a network node-triggered report. A code point in the bit field can be used to indicate whether the request is for a request for a UEE report or a network node-triggered report. The bit field may be a CSI request. Based on the code point in the bit field, the UE can determine whether the DCI request is for a network node-triggered report or a UEE report. If the UE has more than one pending UEE report, the UE will determine one of the more than one UEE report once it receives the DCI. Alternatively, in some embodiments, the UE may multiplex the more than one UEE report (if the resource scheduled by the DCI with an adaptive code rate can accommodate the more than one UEE report).

[1012] For pending UEI reports, in Mode B, the UE will determine or select a valid PN resource and / or a valid (pre)configured resource for transmitting the UEI report. The UE will transmit the PN on the determined / selected PN resource and the pending UEI report on the determined / selected (pre)configured resource.

[1013] For Mode B, a common problem that may arise is that the mapping between the PN resource and the (pre)configured resource used for transmitting UEI reports will disappear once the UE changes characteristics during the period between the PN resource and the (pre)configured resource used for transmitting UEI reports, or the UE changes characteristics for both the PN and UEI reports. Further design is needed to ensure a consistent understanding between the UE and the network node when the PN is transmitted.

[1014] concept

[1015] This concept designs the handling of PN and UEI reports when the UE detects one or more specific events. PN and UEI reports are associated with one or more events related to beam management triggered by the UE.

[1016] The one or more specific events correspond to:

[1017] - DL / UL BWP changes indicated or triggered by network nodes or UEs

[1018] -Activated cell DTX / DRX that overlap with inactivity periods reported by PN or UEI.

[1019] -Received an update / change to the activated beam.

[1020] - The application has activated the beam.

[1021] -Received an update / change to the indicated beam.

[1022] - Apply the indicated beam

[1023] - HARQ is transmitted in response to receiving a DL signal for updating / changing the activated beam.

[1024] - HARQ is transmitted in response to receiving a DL signal indicating an update / change of the indicated beam.

[1025] - Change, activate, or reconfigure the candidate beams

[1026] - The serving cell with configured resources for PN and / or resources for UEI reporting is deactivated.

[1027] - Resources used for PN and / or resources used for UEI reporting have been reconfigured.

[1028] - A serving cell with configured resources for PN and / or resources for UEI reporting is switched from the first serving cell to the second serving cell.

[1029] - Requests for reports from network nodes (e.g., beam reports requested by a next-generation node B (gNB)).

[1030] - Overlaps with the timing of transmitting network-based reports, and / or

[1031] - UL cancellation based on UE-specific signals (e.g., dynamic scheduling DCI) or group common signals (e.g., DCI format 2_4).

[1032] Preferably, in some embodiments, one approach is that the UE does not expect to receive configurations associated with the one or more specific events and UEI reports.

[1033] Preferably, in some embodiments, possible methods may be shown below (e.g., primarily for...). Figure 23 The solution where one or more specific events exist / occur / trigger at or overlapping with time t1:

[1034] - Before the UE transmits the PN for UEI reporting (or if the UE transmits the PN for UEI reporting with a time offset), the UE determines whether the PN resources and / or the resources for UEI reporting are valid.

[1035] - Before the UE transmits the PN for UEI reporting (or if the UE transmits the PN for UEI reporting with a time offset), the UE determines whether a bundle of PN resources and / or resources for UEI reporting overlap with the timing, resources, or reports associated with one or more specific events.

[1036] - Before the UE transmits the PN for UEI reporting (or if the UE transmits the PN for UEI reporting with a time offset), when a bundle of PN resources and resources for UEI reporting overlap with the timing or resources or reporting associated with one or more specific events, the UE is unsure of the PN resources and / or resources for UEI reporting.

[1037] - Before the UE transmits the PN for UEI reporting (or if the UE transmits the PN for UEI reporting with a time offset), when at least one of the PN resources or resources for UEI reporting overlaps with the timing or resources or reporting associated with one or more specific events, the UE is unsure of the PN resources and / or resources for UEI reporting.

[1038] - Before the UE transmits the PN for UEI reporting (or if the UE transmits the PN for UEI reporting with a time offset), when at least one of the first PN resource or the first resource for UEI reporting overlaps with a timing, resource, or report associated with one or more specific events, the UE determines the second PN resource and / or the second resource for UEI reporting. Preferably, in some embodiments, the second PN resource and / or the second resource for UEI reporting does not overlap with a timing, resource, or report associated with one or more specific events. Preferably, in some embodiments, the second PN resource and / or the second resource for UEI reporting is available when or after the one or more specific events are completed or canceled.

[1039] Preferably, in some embodiments, possible methods may be shown below (e.g., primarily for...). Figure 23 The solution to the problem of one or more specific events existing / occurring / triggered at or overlapping with time t2:

[1040] - The UE transmits the PN for UEI reporting, and after the PN transmission (and before the transmission of the UEI report), the UE does not expect the one or more specific events to occur.

[1041] - The UE transmits the PN for UEI reporting, and after the PN is transmitted (but before the UEI report is transmitted), the UE assumes that one or more specific events have not occurred.

[1042] - The UE transmits a PN for UEI reporting, and after the PN is transmitted (but before the UEI report is transmitted), the UE suspends the triggering of one or more specific events.

[1043] - The UE transmits the PN for UEI reporting, and the PN transmission will delay the triggering of one or more specific events after the PN transmission (but before the UEI report transmission).

[1044] - The UE transmits the PN for UEI reporting, and after the PN is transmitted (but before the UEI report is transmitted), the UE transmits the UEI report first (with priority over one or more specific events or reports associated with one or more specific events).

[1045] - The UE transmits the PN for UEI reporting, and after the PN transmission (and before the UEI report transmission), the UE determines to maintain the verification used for UEI report transmission (due to the PN transmission).

[1046] - The UE transmits the PN for the UEI report, and after the PN is transmitted (but before the UEI report is transmitted), the UE keeps the UEI report pending.

[1047] - The UE transmits the PN for UEI reporting, and after the PN transmission (and before the UEI reporting transmission), the UE determines the valid PN resources and valid resources for UEI reporting later.

[1048] - The UE transmits the PN for the UEI report, and after the PN is transmitted (but before the UEI report is transmitted), the UE cancels the triggered event and / or the UE cancels or clears the UEI report.

[1049] - The UE transmits the PN for the UEI report, and after the PN is transmitted (but before the UEI report is transmitted), the UE does not cancel the transmission of the UEI report or maintain the transmission of the UEI report on the corresponding resource used for the UEI report.

[1050] - The UE transmits a PN for UEI reporting, and after the PN transmission (and before the UEI report transmission), the UE changes the mode associated with the UEI report from mode B to mode A (after the one or more specific events within the window). Preferably, in some embodiments, the window references the timing of the one or more specific events. Preferably, in some embodiments, the window references the timing of the end, completion, or cancellation of the one or more specific events.

[1051] - The UE transmits a PN for UEI reporting, and after the PN transmission (and before the UEI report transmission), the UE expects to receive a DL signal requesting a pending UEI report from the network node (after the one or more specific events).

[1052] Preferably, in some embodiments, possible methods may be shown below (e.g., primarily for...). Figure 23 The solution to the problem of one or more specific events existing / occurring / triggered at or overlapping with the time t3:

[1053] - After the UE transmits the UEE report (or after the UE transmits the UEE report with a time offset), the UE does not expect one of the one or more specific events to occur before the duration (e.g., the duration begins with or without an offset to the timing of the UEE report transmission, and / or the duration is for monitoring network (NW) responses).

[1054] - After the UE transmits the UEE report (or after the UE transmits the UEE report with a time offset), the UE delays the triggering of one of the one or more specific events.

[1055] - After the UE transmits the UEE report (or after the UE transmits the UEE report with a time offset), the UE assumes that one of the one or more specific events will not occur until the duration ends or the UE receives a response from the network node.

[1056] - After the UE transmits the UEE report (or after the UE transmits the UEE report with a time offset), the UE cancels the triggering of one of the one or more specific events.

[1057] - After the UE transmits the UEE report (or after the UE transmits the UEE report with a time offset), the UE suspends triggering one or more specific events (until the network node that received the UEE report responds).

[1058] - After the UE transmits the UEE report (or after the UE transmits the UEE report with a time offset), the UE determines that the one or more specific events are dynamically indicated by the network node as a network node response.

[1059] - After the UE transmits a UEE report (or after the UE transmits a UEE report with a time offset), the UE prioritizes handling one or more of the specific events and / or de-prioritizes monitoring of NW responses.

[1060] Once the UE transmits a UEI report on (pre)configured resources, the UE will attempt to detect a network node response. The network node response will be an explicit signal. Preferably, in some embodiments, the explicit signal will be an activation signal or indication signal used to change or update or indicate a new current beam or a new candidate beam. Preferably, in some embodiments, the new candidate beam or new current beam is associated with the UEI report or the reported event (in the UEI report). Preferably, in some embodiments, the explicit signal can be an event-based signal. Preferably, in some embodiments, the UE monitors the signal once it transmits a UEI report. Preferably, in some embodiments, the UE does not monitor the signal when it does not transmit a UEI report. Preferably, in some embodiments, the UE can be configured with a search space for monitoring the signal. Preferably, in some embodiments, the signal can be a UEI search space (in addition to the BFR search space). Alternatively, in some embodiments, once the UE transmits a UEI report, the UE monitors the signal in the BFR search space (which adds a new purpose via the BFR search space). Preferably, in some embodiments, the signal has a Cyclic Redundancy Check (CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI) (or a Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI) or a Modulation and Coding Scheme Radio Network Temporary Identifier (MCS-RNTI), or a UE-specific RNTI). Preferably, in some embodiments, the UE monitors the signal based on a currently indicated TCI state while a procedure different from the BFR procedure is in progress. Preferably, in some embodiments, the currently indicated TCI state signifies or corresponds to monitoring a (UE-specific) DL channel / signal. Preferably, in some embodiments, if the BFR search space or UEI search space is associated with Control Resource Set (CORESET) 0 or a CORESET that does not follow a uniform TCI state, the UE monitors the signal in the BFR search space or UEI search space based on the TCI state associated with CORESET 0 or a CORESET that does not follow a uniform TCI state. More specifically, the TCI state will be activated and / or indicated by the MAC CE. Preferably, in some embodiments, the UE will monitor the signal for a duration. Preferably, in some embodiments, the duration is configured by the network node. Preferably, in some embodiments, the UE will stop monitoring the signal once the duration has elapsed or the UE receives the signal. Preferably, in some embodiments, if the UE does not detect the signal (during the duration), the UE will retransmit the UEI report (if the UEI report latency requirements are also met). Preferably, in some embodiments, for the retransmission of the UEI report, the UE will increase the transmission power used for the retransmission of the UEI report.

[1061] The UE can transmit the PN via a first resource for PN and the UEI report via a first resource for UEI reporting, wherein the first resource for UEI reporting is associated with the PN or the first resource for PN. After transmitting the UEI report, the UE can receive a network node response to the UEI report, for example, indicating a negative acknowledgment (NACK) or unsuccessful transmission / reception. In response to the network node response, the UE can retransmit the UEI report via a second resource for UEI reporting. Alternatively, the UE can trigger and transmit a second UEI report via the second resource for UEI reporting (associated with a triggered and uncancelled event). The second resource for UEI reporting can be associated with a second resource for PN. The UE may not need to perform the transmission of the second PN via the second resource for PN (in response to a network node response). Preferably, in some embodiments, the network node response can provide an interval including a certain number of nearest resources (associated with a pending event) for UEI. Preferably, in some embodiments, the network node response can provide a certain number of (later / future) nearest resources (associated with a pending event) for UEI. Preferably, in some embodiments, based on an indication from a network node response, the UE can trigger and transmit a second UEI report via a second resource for UEI reporting (associated with a triggered but not cancelled event). In other words, the UE can skip transmitting a second PN via the second resource for PN (in response to a network node response).

[1062] The second resource used for UEI reporting can be the closest resource (configured for UE) after the timing (plus time offset) of receiving the network node response. The first and second resources used for UEI can be at the same frequency (e.g., completely overlapping in the frequency domain). The time-domain and / or frequency-domain allocation of the second resource used for UEI reporting can be indicated by the network node response.

[1063] Network node responses can be transmitted via PDCCH.

[1064] Alternatively, in some embodiments, a network node response (indicating NACK or unsuccessful transmission / reception) may block one or more PN resources and / or (pre)configured resources for UEI reporting. Preferably, in some embodiments, once the UE receives the network node response, the UE will determine a time interval for changing from mode B to mode A, and / or the UE assumes that the UE is not allowed to transmit PN and / or UEI reports on (pre)configured resources. Alternatively, in some embodiments, the UE will receive an indication from the network node to change from mode A to mode B. Preferably, in some embodiments, the UE assumes that PN resources and / or resources for UEI reporting are unavailable for transmission before receiving the indication from the network node to change from mode A to mode B. Preferably, in some embodiments, if during the time interval or if before receiving the indication from the network node to change from mode A to mode B, once the UE triggers an event, the UE will transmit a scheduling request to the network node and monitor the DCI scheduling resources for transmitting UEI reports. Preferably, in some embodiments, the length of the time interval is (pre)configured or (pre)defined. Preferably, in some embodiments, blocking one or more PN resources and / or (pre)configured resources for UEI reporting due to a network node response is performed per event, per BWP, per serving cell, per cell group, per PUCCH group, or per co-frequency band. Preferably, in some embodiments, the blocking due to a network node response has no effect on PN resources and / or (pre)configured resources for UEI reporting associated with different events or different BWPs, different serving cells, different cell groups, different PUCCH groups, or different frequency bands. Preferably, in some embodiments, after the time interval, the UE will change from mode A to mode B.

[1065] Preferably, in some embodiments, the signal will indicate whether to increase the transmission power for retransmission of UEI reports. Preferably, in some embodiments, the retransmission is a mode change from mode B to mode A. Alternatively, in some embodiments, the UE will autonomously perform UEI report retransmission. Preferably, in some embodiments, the UE will (re)transmit the UEI report on the next (pre)configured resource for transmitting the UEI report. Preferably, in some embodiments, when the UE transmits a PN but does not transmit or is unable to transmit a UEI report (due to one or more specific events), the UE will monitor the network node's DCI for scheduling resources for UEI report retransmission. Alternatively, in some embodiments, the UE will (re)transmit the UEI report on the next / future (pre)configured resource for the UEI report. Preferably, in some embodiments, the UE will transmit the next PN associated with the next / future (pre)configured resource for the UEI report. Preferably, in some embodiments, the UE may (directly) skip transmitting the PN associated with the next / future (pre)configured resource. Alternatively, in some embodiments, the UE may skip transmitting the PN associated with the next / future (pre)configured resource. Preferably, in some embodiments, the PN or grant is actually given by an indication from the network node. Preferably, in some embodiments, when the network node receives the PN stick but not the UEI report, the network node may (directly) indicate the (re)transmission of the UEI report on (pre)configured resources. Preferably, in some embodiments, the signaling details may be reusing dynamic DCI scheduling or using an indicator indicating one or more (pre)configured resources for retransmission of the UEI report.

[1066] Preferably, in some embodiments, the UE cancels the triggered event when it receives a response from the network node.

[1067] Preferably, in some embodiments, the UE cancels the triggered event in response to the end of the duration. Preferably, in some embodiments, the duration is used to implicitly cancel the triggered event (when the UE does not receive a response from the network node). Preferably, in some embodiments, the duration may or may not have an offset, said offset starting from the timing of the (pre)configured resources used to transmit the UEI report or the next symbol or the next time slot.

[1068] Preferably, in some embodiments, once the UE receives the signal, the UE can determine that the network node has received the UEE report. The network node response will be an indication (e.g., a bit in the DCI indicating that it has been received). The network node response will be a group common signal. Alternatively, in some embodiments, the network node response will be a UE-specific signal. Preferably, in some embodiments, the network node response will be a DCI with or without (DL / UL) scheduling information. Preferably, in some embodiments, the UE may be configured with a group common RNTI to monitor the network node response. Preferably, in some embodiments, the explicit signal will be CRC scrambled via the group common RNTI (dedicated to UEE reports). Preferably, in some embodiments, the UE may be configured with one or more start positions to indicate information blocks. Preferably, in some embodiments, each information block is associated with a PN resource and / or a (pre)configured resource for transmitting UEE reports. Preferably, in some embodiments, packetization may occur, such that an information block is associated with one or more PN resources and / or one or more (pre)configured resources for transmitting UEE reports. Preferably, in some embodiments, the UE can determine whether the network node has received the UE report and / or whether the UE needs to retransmit it, based on the information block associated with the resource used for (already) transmitting the UEI report. Alternatively, in some embodiments, once the UE transmits the UEI report, no network node response is required, and / or the UE does not retransmit the UEI report. The UE does not retransmit the UEI report unless it is (pre-)configured with or associated with a repetition count or aggregation factor. Preferably, in some embodiments, the UE does not anticipate a repetition count for the resource configured to be associated with the UEI report. Preferably, in some embodiments, when the UL BWP is configured or associated with an aggregation factor (greater than 1), the UE assumes that the resource used for transmitting the UEI report has no repetitions. Preferably, in some embodiments, the UE assumes that the resource used for transmitting the UEI report has no aggregations, regardless of whether the aggregation factor is greater than 1. Preferably, in some embodiments, the UE does not anticipate that the aggregation factor configured in the UL BWP used for transmitting the UEI report will be greater than 1. Preferably, in some embodiments, the UE does not anticipate that the repetition count associated with the resource used for transmitting the UEI report will be greater than 1. Alternatively, in some embodiments, the UE may determine the number of resources used to transmit UEI reports based on the number of repetition or aggregation factors. Preferably, in some embodiments, one PN resource is associated with one (pre)configured resource. Preferably, in some embodiments, when repetition or aggregation is applied or assumed (e.g., greater than 1), the UE may transmit more than one PN resource to notify network nodes. Alternatively, in some embodiments, the UE may transmit one PN resource associated with one (pre)configured resource.Preferably, in some embodiments, the number of remaining resources, calculated by subtracting one from the repetition number or the aggregation factor, follows the one (pre)configured resource. Preferably, in some embodiments, the number of remaining resources is associated with the same format and the same number of start and symbol numbers and physical resource blocks (PRBs) and the one (pre)configured resource. Preferably, in some embodiments, the number of remaining resources, calculated by subtracting one from the repetition number or the aggregation factor, is determined based on future available (continuous) TTIs. Preferably, in some embodiments, the future available (continuous) TTIs are configured with at least flexible symbols and / or PRBs or ULs to determine the same format of the one (pre)configured resource. Preferably, in some embodiments, the UE will transmit UEI reports on the one (pre)configured resource and on the remaining number of resources. Alternatively, in some embodiments, the UE will transmit UEI reports on at most the aggregation factor number or the repetition number. Preferably, in some embodiments, a PN resource is associated with a certain number of (pre)configured resources. Preferably, in some embodiments, the number of (pre)configured resources associated with a PN resource is used for repetition or aggregation. Preferably, in some embodiments, the number of (pre)configured resources are in different TTIs. Preferably, in some embodiments, the number of (pre)configured resources have the same (PUCCH) format.

[1069] The first method is that the UE transmits a PN for a UEEI report, and after the PN transmission, the UE does not expect to receive a BWP handover command from the network node. In one instance, the resources for both the PN and the UEEI report can be determined as a bundle. Preferably, in some embodiments, the UE does not expect to receive a BWP handover command from the network node within / during the bundle. Preferably, in some embodiments, each bundle of resources for the PN and UEEI report is configured per BWP. Preferably, in some embodiments, the UE does not expect to receive a BWP handover command from the network node during the time period of the reference PN transmission. Preferably, in some embodiments, the time period ends when the UE transmits a UEEI report or in response to it. Preferably, in some embodiments, the time period can begin from the end of the PN transmission. Preferably, in some embodiments, the time period can begin from the next symbol after the PN transmission. Preferably, in some embodiments, the time period can begin with an offset after the PN transmission. Preferably, in some embodiments, the offset can correspond to the round-trip time and / or the processing time of the network node. Preferably, in some embodiments, the UE can receive a BWP handover command within the offset. Preferably, in some embodiments, the value of the offset can be configured or predefined. Preferably, in some embodiments, the offset value may be the same or different between different events. Preferably, in some embodiments, for the same serving cell, the same UL BWP, the same frequency band, and the same cell group, the UE is expected to be configured with the same offset value, or to use or determine the same offset value. Preferably, in some embodiments, a UEI report is triggered in response to an event. Preferably, in some embodiments, once more than one event is triggered (and not canceled), the UE can multiplex one or more UEI reports for transmission in a single time instance. Preferably, in some embodiments, once the UE receives a BWP handover command during PN and UEI reporting (e.g., t1 refers to PN transmission, t2 refers to BWP handover command reception, t3 refers to UEI report transmission, and t1 precedes t2, t2 precedes t3), the UE does not cancel the triggered event. Preferably, in some embodiments, the UE maintains a timer for each (DL)BWP. Preferably, in some embodiments, the timer corresponds to bwp-InactivityTimer. Preferably, in some embodiments, the UE starts or restarts a timer (of the DL BWP) when a PDCCH addressing a C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received at least in the BWP. Preferably, in some embodiments, the UE starts or restarts a timer when a PDCCH addressing a C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received at least in the BWP. Preferably, in some embodiments, the UE switches the active BWP once the timer expires.More specifically, the UE changes the active DL BWP to the default DL BWP (primarily for power saving). Preferably, in some embodiments, since the UE initiates a UEI report, the UE may face the choice of whether to switch the active BWP change or transmit the PN and UEI reports. Preferably, in some embodiments, the UE can determine whether to change the active BWP due to timer expiration based at least on whether a triggered event exists (and has not been cancelled). Preferably, in some embodiments, the UE can determine whether to change the active BWP due to timer expiration based at least on whether the UE has transmitted a PN but has not yet transmitted a UEI report. Preferably, in some embodiments, based on the determination that a triggered event exists (and has not been cancelled), the UE can delay switching the active BWP change (due to timer expiration). Preferably, in some embodiments, based on the determination that no triggered event exists (or the triggered event has been cancelled), the UE switches the active BWP (due to timer expiration). Preferably, in some embodiments, based on the determination that the UE has transmitted a PN but has not yet transmitted a UEI report, the UE can delay switching the active BWP change (due to timer expiration). Preferably, in some embodiments, based on the determination that the UE has not yet transmitted a PN or has transmitted a UEI report, the UE does not delay the handover of the active BWP (due to timer expiration). Preferably, in some embodiments, based on the above, the UE delays the handover of the active BWP at least until the UE transmits the UEI report. Preferably, in some embodiments, the UEI report and PN are (pre)configured resources. Preferably, in some embodiments, the UE is configured to operate in Mode B or in Mode B (transmitting the UEI report via (pre)configured resources). Preferably, in some embodiments, the UE may pause the timer or not switch the active BWP before transmitting the UEI report. Alternatively, in some embodiments, the UE does not transmit the UEI report in the old active BWP (e.g., the resource for the UEI report in the old active BWP is after the timer expires). Preferably, in some embodiments, the UE may transmit the PN in the old active BWP (before the timer expires). Preferably, in some embodiments, the UE needs to transmit the PN and UEI report on another resource in the new active BWP. Preferably, in some embodiments, the UE may be configured with multiple different resources for the UEI report. Preferably, in some embodiments, the UE may be configured with multiple different resources for the PN. Preferably, in some embodiments, the UE determines the valid resources for the PN (and the valid resources for UEI reporting) based on the configuration associated with the new active BWP. Preferably, in some embodiments, valid means that the resources do not overlap (partially or completely) with the BWP handover time in the time domain.Preferably, in some embodiments, "effective" means a resource after a timing event, said timing being the first time slot or first symbol of the UE ending the active BWP handover, or after the BWP handover time, or at the beginning of a time slot in which the UE can perform reception or transmission. Alternatively, in some embodiments, the UE cancels a triggered event due to timer expiration, and / or the UE switches the active BWP due to timer expiration. Alternatively, in some embodiments, the UE starts or restarts a timer once it determines that the condition of an event is met (or once an event is triggered). Preferably, in some embodiments, a basic theory is that the UE has a request to perform a UL transmission due to the triggered event, without considering changing the active BWP to the default BWP. Alternatively, in some embodiments, the UE pauses the timer once it determines that the condition of an event is met (or once an event is triggered). More specifically, the UE pauses the timer until the UE transmits a UEE report (e.g., the last symbol of the resource used for the UEE report). More specifically, the UE pauses the timer until the UE transmits a PN (e.g., the last symbol of the resource used for the PN).

[1070] The UE may start or restart a timer associated with the serving cell (associated with the active DL BWP) in response to the transmission of a PN on the serving cell (e.g., via PUCCH). Alternatively and / or additionally, the UE may start or restart a timer associated with the serving cell (associated with the active DL BWP) in response to the transmission of a UEI report on the serving cell (e.g., via PUCCH).

[1071] The second method is that the UE transmits a PN for UEEI reporting, and after the PN transmission, the UE receives a BWP handover command from the network node. Preferably, in some embodiments, the UE does not transmit the UEEI report on the first UL resource on the previous UL BWP. Preferably, in some embodiments, after / in response to changing the active BWP to a new BWP that includes a second UL resource, its corresponding PN resource is used during the BWP handover time and / or the time interval during which the UE is not allowed to transmit or does not transmit. Preferably, in some embodiments, the time interval may begin from the next symbol of the CORESET including the DCI format indicating the BWP handover. Preferably, in some embodiments, the length of the time interval may be (pre)configured and / or depends on the UE capability and / or depends on whether the frequency range is FR1 or FR2. Preferably, in some embodiments, the UE does not transmit the UEEI report on the second resource. Preferably, in some embodiments, the UE does not transmit the UEEI report on the second resource when there is no valid PN resource for the second resource. Preferably, in some embodiments, the second resource may be the earliest / most recent UL resource used for UEEI reporting after the active BWP change. Preferably, in some embodiments, based on the determination that no valid PN resource is associated with the second resource after the UE changes the active BWP, the UE does not transmit the UEI report on the second resource. Preferably, in some embodiments, the third resource is associated with a valid PN resource after the UE changes the active BWP to the new active BWP when the third resource is later than the second resource. Preferably, in some embodiments, the second resource and the third resource are associated with the UEI report. Preferably, in some embodiments, once the UEI report is triggered (pending and not canceled), the UE can be configured with multiple resources for transmitting the UEI report. Preferably, in some embodiments, the multiple resources include the second resource and the third resource.

[1072] The third method is that the indication of the PN in the old active BWP can be applied to the new active BWP. In one instance, the indication of the PN is jointly applied to the TTI in a serving cell. Preferably, in some embodiments, the indication of the PN in the first BWP can be associated with the use of resources for UEI reporting in the first BWP and the second BWP, wherein the first BWP and the second BWP are in the same serving cell or associated with the same serving cell. Preferably, in some embodiments, a PN resource can be associated with one or more resources for UEI reporting, wherein the one or more resources for UEI reporting can be associated with the same or different BWPs. Preferably, in some embodiments, a resource for UEI reporting can be associated with one or more PN resources in the same or different BWPs. Preferably, in some embodiments, at least when the UE transmits the PN in a PN resource in the first BWP, the resource for UEI reporting in the second BWP associated with the one PN resource is used for transmission. In one instance, the UE can be configured with more than one BWP. Preferably, in some embodiments, the UE is (pre-)configured with PN resources in one or each of the more than one BWP. Preferably, in some embodiments, the UE is (pre-)configured with resources for UEI reporting in one or each of the more than one BWP. Preferably, in some embodiments, the UE determines that the PN resource is activated when it is in an active BWP in which the PN resource is located. Preferably, in some embodiments, the UE determines whether the PN resource is activated based on whether the PN resource is in an active BWP. Preferably, in some embodiments, the UE does not transmit PN on PN resources in inactive BWPs (even if a triggered event exists). Preferably, in some embodiments, there may be some exceptions where the UE can be configured with a dormant BWP, in which the UE is not expected to be configured with PN resources and / or resources for UEI reporting. Preferably, in some embodiments, the UE determines that the resources for UEI reporting are activated when it is in an active BWP in which the resources for UEI reporting are located. Preferably, in some embodiments, the UE determines whether the resources for UEI reporting are activated based on whether the resources for UEI reporting are in an active BWP. Preferably, in some embodiments, the UE does not transmit UEI reports on resources for UEI reporting in inactive BWPs (even if a triggered event exists). Preferably, in some embodiments, there may be exceptions where the UE can be configured with a dormant BWP, in which the UE is not expected to be configured with PN resources and / or resources for UEI reporting. This excludes the case where the new active BWP is a dormant BWP, in which the UE transmits PN on the PN resources of the old active BWP and transmits UEI reports on the resources for UEI reporting in the new active BWP.(After switching from the old active BWP to the new active BWP and) before transmitting the UEI report in the new active BWP, the PN may not be transmitted in the new active BWP. Resources associated with the PN transmitted in the old active BWP for UEI reporting may be used during the time period for switching from the old active BWP to the new active BWP. PN resources associated with the UEI report transmitted in the new active BWP may be used during the time period for switching from the old active BWP to the new active BWP. Preferably, in some embodiments, the association between the PN resources in the old active BWP and the resources for UEI reporting in the new active BWP may be based on implicit determination or explicit signaling. Preferably, in some embodiments, explicit signaling may be RRC, MAC CE, and / or DCI. Preferably, in some embodiments, explicit signaling may provide the association between a first resource (for the PN) in the first BWP and a second resource (for UEI reporting) in the second BWP. Preferably, in some embodiments, the first BWP may be the same as or different from the second BWP. Preferably, in some embodiments, the first BWP and the second BWP correspond to the same serving cell. Preferably, in some embodiments, the new active BWP and the old active BWP correspond to the same serving cell. Preferably, in some embodiments, the implicit determination can be based on the periodicity of PN resources by the UE (e.g., t1, t2). 1+n t 1+2n t 1+3n (Representing a periodic PN resource in a BWP) determines that the PN resource is associated with one or more resources for UEI reporting in future periods. Preferably, in some embodiments, the one or more resources for UEI reporting may be configured in a first BWP or a second BWP that is the same as or different from the BWP of the PN resource. In the third method, when the UE transmits the PN on the PN resource in the old active BWP and switches to the active BWP, the UE may transmit the UEI report on the cross-BWP associated resources for UEI.

[1073] Preferably, in some embodiments, the first PN resource in the first BWP is associated with the first resource in the first BWP used for UEI reporting.

[1074] Preferably, in some embodiments, a first PN resource in a first BWP is associated with a second resource in a second BWP used for UEI reporting.

[1075] Preferably, in some embodiments, the UE can determine that a second resource can be associated with the first PN resource based on a time interval following or associated with the first PN resource. Preferably, in some embodiments, if the second resource is within the time interval, the UE can transmit a UEI report on the second resource after a BWP handover (without transmitting the PN in the second BWP). Preferably, in some embodiments, if the second resource is not within the time interval (e.g., later than a timer interval), the UE will determine a third PN resource associated with a third resource used for UEI reporting in the second BWP after a BWP handover, and / or the UE will transmit the PN on the third PN resource and / or transmit the UEI report on the third resource.

[1076] Preferably, in some embodiments, the UE can determine that a second resource can be associated with a first PN resource based on a configured association between PN resources with the same (resource) identity or the same identifier (associated to the first PN resource) or different BWPs and resources used for UEI reporting. Preferably, in some embodiments, if the second resource and the first resource are configured with the same (resource) identity (or associated with the first PN resource), the UE can transmit UEI reports on the second resource after a BWP handover.

[1077] Preferably, in some embodiments, the UE does not transmit the UEI report on the first resource.

[1078] If the (UL) BWP is deactivated, any or all PN resources on the BWP and / or resources used for UEI reporting can be suspended. If the BWP is activated, any or all PN resources on the BWP and / or resources used for UEI reporting can be restored or (re)initialized. Alternatively, in some embodiments, if the BWP is deactivated, any or all PN resources on the BWP and / or resources used for UEI reporting can be cleared.

[1079] For example, in Figure 24In this example, a first PN resource and a first (pre)configured resource for UEI reporting are in a first BWP, and a second PN resource and a second (pre)configured resource for UEI reporting are in a second BWP. In this example, the first resource for UEI reporting is during the BWP handover time. In this example, the second PN resource is during the BWP handover time, but in another example it may be after the BWP handover time. In this example, a third PN resource and a third resource for UEI reporting are after the BWP handover time. The UE can transmit the PN and receive the BWP handover command on the first PN resource. In one example, the UE can transmit the UEI report on the second resource for UEI. Based on the association between the first PN resource in the first BWP and the second resource for UEI reporting in the second BWP (if the second resource for UEI reporting is later than the BWP handover time), the UE can transmit the UEI report on the second resource for UEI reporting. Preferably, in some embodiments, the association can be implicitly derived or determined or based on explicit signals. Preferably, in some embodiments, the implicit determination or derivation of the association is based on a time interval, identical identity, or identical identifier. Preferably, in some embodiments, resource identities or identifiers from different BWPs can be reused. Preferably, in some embodiments, the resource identity or identifier can be global for one or more BWPs in a serving cell used to transmit UEI reports. Preferably, in some embodiments, the association can be a time interval starting from a first PN resource or the periodicity of PN resources in a BWP. Preferably, in some embodiments, the UE can be configured with, for example, Figure 25 The association shown indicates that each PN resource can correspond to more than one resource for UEI in one or more BWPs (cross-BWP indication for resources supporting PN resources and resources for UEI reporting). Preferably, in some embodiments, even if the second PN resource is later than the BWP handover time ( Figure 24 (Not shown in the image), once the UE transmits the PN on the first PN resource, the UE can directly transmit the UEI report on the second resource used for UEI reporting. Preferably, in some embodiments, the UE does not need to transmit the PN again on the second PN resource. Preferably, in some embodiments, even if the second PN resource is unavailable for transmission, the UE can still transmit the UEI report on the second resource used for UEI reporting. In another instance, the UE will delay the BWP handover time until the UEI report is transmitted on the first resource used for UEI reporting. Preferably, in some embodiments, the UE (again) transmits the PN on the third PN resource. Preferably, in some embodiments, the UE transmits the UEI report on the third resource used for UEI reporting.

[1080] The UE may be configured for Network Energy Saving (NES). The UE may be configured with Cell DRX, including cell DRX modes for cell inactivity and cell activity times. Preferably, in some embodiments, cell inactivity time refers to the network node being in energy-saving operation. Preferably, in some embodiments, cell activity time refers to the network node being in normal operation.

[1081] Preferably, in some embodiments, the cell DRX mode can be configured semi-statically. Preferably, in some embodiments, the cell DRX mode can be activated or deactivated based on dynamic signals. Preferably, in some embodiments, when the dynamic signal indicates activation within a time interval or period, the time interval or period may include one or more cell DRX modes (meaning the network will have some power-saving gains during cell inactivity). Preferably, in some embodiments, when the dynamic signal indicates deactivation within a time interval or period, the time interval or period does not include any cell DRX modes (meaning the network will be in cell activity time during the time interval or period).

[1082] In the first method, the UE expects resources for the PN and resources for UEI reporting to be configured during cell activity time. Preferably, in some embodiments, the UE expects a bundle of PN resources and resources for UEI reporting to be configured during cell activity time. Preferably, in some embodiments, the UE does not expect a PN resource to be during cell activity time and resources for UEI reporting to be during cell inactivity time. Preferably, in some embodiments, (if network nodes are allowed to configure at least one resource for PN or UEI reporting during cell inactivity time), when a triggered event occurs, the UE determines the valid resources for transmitting UEI reports based on the fact that both resources for PN and resources for UEI reporting are during cell activity time. Preferably, in some embodiments, the UE determines whether PN resources and resources for UEI reporting are during cell activity time based on semi-static configuration and / or dynamic signals. For simplicity, PN resources and resources for UEI reporting are configured within a time interval or period indicated by a single dynamic signal. Preferably, in some embodiments, the UE does not expect the PN resource to be associated with a first dynamic signal (or within a first time interval or a first period indicated by the first dynamic signal), while the resource for transmitting the UEI report is associated with a second dynamic signal (or within a second time interval or a second period indicated by the second dynamic signal). Alternatively, in some embodiments, the UE determines that the resource for UEI reporting is invalid based on the association of the PN resource and the resource for UEI reporting with different dynamic signals (e.g., an earlier dynamic signal for PN and a later dynamic signal for UEI reporting). More specifically, the resource for UEI reporting may be during cell DRX inactivity. Preferably, in some embodiments, the UE determines that the resource for UEI reporting is invalid based on the association of the PN resource and the resource for UEI reporting with different dynamic signals and that at least one resource for PN or for UEI reporting is during cell DRX inactivity. Preferably, in some embodiments, the UE determines valid resources for transmitting the UEI report based on the fact that both the resources for PN and the resources for UEI reporting are during cell DRX activity time. Preferably, in some embodiments, cell DRX activity time may be based on one or more dynamic signals and / or a semi-static cell DRX mode. Preferably, in some embodiments, when the UE determines valid resources for transmitting UEI reports, the UE determines that at least the PN resources are available during the cell DRX activity period.

[1083] In the second method, the UE is not expected to be configured with both cell DRX and UEI reporting simultaneously. Preferably, in some embodiments, when a cell is configured with cell DRX, the UE is not expected to be configured with UEI reporting. Preferably, in some embodiments, when a cell is configured with cell DRX, the UE is not expected to be configured with mode B for UEI reporting (e.g., mode A for UEI reporting is allowed to be configured with cell DRX simultaneously).

[1084] for Figure 20 In the example, the UE determines the CSI reference resource (time domain) for UEI reporting based on the resource associated with the PN. Preferably, the time domain position of the resource associated with the PN (associated with the first resource used to transmit the UEI report) is used to determine the CSI reference resource for UEI reporting. Preferably, the start or end symbol of the resource associated with the PN is used as a reference for determining the CSI reference resource. The end symbol of the CSI reference resource is offset by at least one offset before the start or end symbol of the resource associated with the PN. The start symbol of the CSI reference resource is offset by at least one offset before the end symbol of the resource associated with the PN. Preferably, the UE determines the CSI reference resource (time domain) for UEI reporting based on the timing associated with transmitting the PN. Preferably, the timing associated with transmitting the PN corresponds to or is the timing of the UE transmitting the PN associated with the UEI report (or associated with the resource used to transmit the UEI report).

[1085] Alternatively, the UE determines the CSI reference resource for UEI reporting based on a virtual binding of a first resource associated with the UEI report and a second resource associated with the PN. The CSI reference resource (time domain) is offset by at least one offset before the resource associated with the PN. Preferably, the CSI reference resource (time domain) is offset by at least one offset before the virtual binding with the first and second resources.

[1086] The determination is based at least on the UE configuration or operation in Mode B. Mode B indicates or corresponds to the UE being (pre-)configured with UL resources for transmitting UEI reports, and these UL resources are associated with a resource associated with a PN (or for transmitting a PN).

[1087] When the UE is configured or operating in Mode A, the UE determines the CSI reference resource (time domain) for UEI reporting based on the resources associated with the UEI report. Mode A indicates or corresponds to the UE being scheduled to transmit UEI reports via UL resources. Mode A may not require resources for the PN. Once the UE is configured or operating in Mode-A, the UE determines the CSI reference resource (time domain) for UEI reporting based on the resources associated with the PN (not the PN resources).

[1088] Preferably, for CSI reports rather than UEI reports, the UE determines the CSI reference resource based on the CSI report (and its associated timing). The timing associated with the CSI report corresponds to or is the timing in which the UE transmits the CSI report. The UE is preferably associated with a UE configured as Mode-B.

[1089] Preferably, the binding of PN and UEI can be used to determine whether PUCCH cell handover (or PUCCH cell handover) is permitted. Preferably, during PN and UEI binding, when PN is associated with a UEI report, the UE should not expect a handover from the first cell transmitting PN to the second cell transmitting the UEI report. Alternatively, the UE should not expect PN and UEI reports to be transmitted in different cells containing PUCCH resources. In other words, the TTI between the TTI of PN and the TTI of the UEI report can indicate a PUCCH cell handover.

[1090] for Figure 21 In the example, the UE can be (pre-)configured with three pairs or bundles of PN resources and resources for UEI reporting, denoted as A, B, and C. When the UE triggers a UEI report, the UE will determine or select the valid resources for transmitting the UEI report. This determination or selection can satisfy the condition that both resources (for PN and for UEI reporting) should be available during the cell's DRX activity time. If the UE triggers a UEI report before the start of PN resource A, the UE can select or determine PN resource A and resource A for UEI reporting as valid. If the UE triggers a UEI report after the start of PN resource A, then... Figure 21 There is no next valid resource available for transmitting UEI reports because bundle B may face PN resource B during cell DRX inactivity, and bundle C may face resource C for UEI reporting during cell DRX inactivity. An alternative is that the UE does not expect to be configured with UL resources for both bundle B and bundle C. Another alternative is that UEI reporting and cell DRX cannot be configured simultaneously.

[1091] For another example, such as Figure 22As shown, the first dynamic signal (starting from the left of the figure) deactivates cell DRX, meaning the active time within a time interval. The second dynamic signal activates cell DRX, meaning the cell DRX active and inactive times are based on an on-time duration timer associated with the cell DRX configuration. In this example, if the first dynamic signal indicates that cell DRX is activated, the dotted square can correspond to the original cell DRX active time. There are three instances of resource bundles for PN and UEI reporting, labeled A, B, and C. Bundle A can correspond to resources used for PN and UEI reporting both associated with a single dynamic signal. Bundle B can correspond to at least one resource during cell DRX active time, while another resource is not. Bundle C can correspond to at least one resource used for PN and UEI reporting during cell DRX active time, and another resource used for PN and UEI reporting during cell DRX inactive time. In this example, for bundle C, the PN resource is during cell DRX active time, while the resource used for UEI reporting is during cell DRX inactive time. Preferably, in some embodiments, the cell (DRX) activity time corresponds to the on-duration timer being in operation. Preferably, in some embodiments, the on-duration timer is associated with the cell DRX configuration. The start timing of the on-duration timer may be associated with the RRC configuration or MAC CE or DCI. Preferably, in some embodiments, in this example, for bundle C, when the resource for UEI reporting is within the cell (DRX) activity timer, bundle C, the resource for UEI reporting, can be determined as a valid resource for transmitting UEI reports. It is assumed that there is order between the PN resource and the resource for UEI reporting, i.e., an earlier PN resource is associated with an earlier resource for UEI reporting (simultaneous timing can be considered valid). Preferably, in some embodiments, disorder between the PN resource and the resource for UEI reporting is not allowed. In this example, both bundle B and bundle C correspond to the PN resource and the resource for UEI reporting being associated with different dynamic signals. In one example, the UE does not expect to receive the configuration that results in bundle B or bundle C. Alternatively, in some embodiments, the UE expects both the PN resources and the resources for UEI reporting to be configured during the cell (DRX) activity period, regardless of whether the cell DRX is activated (once the cell DRX is configured). In one method, the UE may be configured with virtual resources, which includes a cell (DRX) activity period assuming (always) activated cell DRX. The UE determines the periodic PN resources and the resources for UEI reporting within the virtual resources. Preferably, in some embodiments, the virtual resources correspond to resources in the TTI during the cell DRX activity period. Preferably, in some embodiments, the periodicity of the PN resources or the periodicity of the resources for UEI reporting is configured with a cell DRX or a plurality of integer numbers of (cell DRX) cycles of time intervals.Preferably, in some embodiments, the periodicity for PN resources is limited to alignment with the periodicity of time intervals (e.g., the periodicity of dynamic signals used to activate / deactivate the cell DRX mechanism). Alternatively, in some embodiments, the UE may receive configurations for bundles B and C. The UE may determine the verification of bundles B and C upon an event triggered by the UE or upon a pending UEI report to be transmitted. The UE determines bundle B as an invalid resource by assuming no dynamic signal is received or indicating activation of the cell DRX mechanism. The UE determines bundle C as an invalid resource by assuming no dynamic signal is received or indicating activation of the cell DRX mechanism. Alternatively, in some embodiments, the UE determines bundle C as a valid resource by assuming no dynamic signal is received or indicating activation of the cell DRX mechanism. Since the resource reported for bundle C was initially configured during cell (DRX) activity time, the UE determines bundle C as a valid resource. Preferably, in some embodiments, if... Figure 22 If the first dynamic signal indicates that the cell DRX mechanism has been activated, then the PN resources in bundles B and C are invalid. Preferably, in some embodiments, based on the indication that the first dynamic signal indicates that the cell DRX mechanism has been activated (causing PN resources during inactive times), the UE determines the invalid resources for UEI reports for bundles B and C. Preferably, in some embodiments, for invalid bundles, and / or for invalid PN resources, and / or for invalid resources used for UEI reports, the UE does not determine or selects such resources for transmitting UEI reports. Preferably, in some embodiments, once the UE has one or more triggered events and / or the UE has one or more pending (and not canceled) UEI reports, the UE can determine valid bundles and / or valid PN resources and / or valid resources for UEI reports.

[1092] Preferably, in some embodiments, the UE does not expect to receive both the configuration for UEI reporting and the call duration timer. Preferably, in some embodiments, the UE does not expect to receive both the configuration for UEI reporting and the dynamic signal for activating / deactivating the cell DRX mechanism. Preferably, in some embodiments, the UE may be configured with a cell DTX mechanism.

[1093] If the UE transmits a PN via resources used for PN during cell DRX active time, the UE can transmit a UEI report via resources used for UEI reporting during cell DRX inactive time. Resources used for UEI reporting can be associated with either the PN transmitted by the UE or the resources used for PN. If both the resources used for PN and the resources associated with the resources used for PN for UEI reporting are during cell DRX inactive time, the UE may not (be allowed) transmit the PN via the resources used for PN and / or transmit the UEI report via the resources used for UEI reporting. If both the resources used for PN and the resources associated with the resources used for PN for UEI reporting are during cell DRX inactive time, the UE determines that the resources used for PN and the resources used for UEI reporting are invalid.

[1094] Alternatively, in some embodiments, the UE can transmit the PN via resources designated for the PN during cell DRX inactivity. In other words, the UE can transmit the PN via resources designated for the PN regardless of whether the resources designated for the PN are in cell DRX inactivity. Alternatively and / or additionally, the UE can transmit the UEI report via resources designated for the UEI report during cell DRX inactivity. In other words, the UE can transmit the UEI report via resources designated for the UEI report regardless of whether the resources designated for the UEI report are in cell DRX inactivity.

[1095] After the UE transmits a UEE report, if the resources for the network node response used for the UEI report are inactive during the cell DTX inactivity period, the UE can (still) monitor or receive the network node response via those resources. In other words, the UE can monitor or receive the network node response via those resources regardless of whether they are inactive during the cell DTX inactivity period. Alternatively, in some embodiments, the UE may not (be allowed to) monitor or receive the network node response via those resources (during the cell DTX inactivity period). The UE may assume that the transmission of the UEI report failed. Alternatively, in some embodiments, the UE may assume that the transmission of the UEI report was successful.

[1096] Preferably, in some embodiments, the UE maintains the triggered event when it faces problems transmitting pending UEI reports. The UE can also maintain the triggered event when it de-prioritizes or postpones the transmission of the PN.

[1097] Preferably, in some embodiments, the UE cancels the triggered event when the UE transmits a corresponding UEI report or when the UE receives a response associated with the transmitted UEI report from a network node, or after a window has begun from the time the UE transmits the corresponding UEI report.

[1098] The UE is configured with a unified TCI framework. The unified TCI framework can correspond to either a joint TCI mode or a separate TCI mode. A joint TCI mode means or corresponds to the DL and UL using the same TCI state. A separate TCI mode means or corresponds to the DL and UL using different TCI states. Without loss of generality, such as Figure 23 As shown, by introducing UEI reports and PN for notification, t1 or t2 corresponds to the timing when the UE receives a DL signal for (updating) activating / deactivating the TCI state, applies the activated TCI state, (updates) the indicated TCI state, applies the indicated TCI state, transmits a HARQ in response to receiving a DL signal for updating / changing the activated TCI state, and / or transmits a HARQ in response to receiving a DL signal for indicating an updated / changed indicated TCI state, and / or the candidate TCI state is changed, activated, or reconfigured.

[1099] If before the UE transmits PN on the PN resource (or before the time offset before the UE transmits PN on the PN resource) (e.g., Figure 23 In t1), UE:

[1100] - Received a DL signal for (updating) the TCI status of activation / deactivation.

[1101] - The application has activated TCI status.

[1102] - (Update) Indicates the TCI status, applies the indicated TCI status,

[1103] - HARQ is transmitted in response to receiving a DL signal used to update / change the state of the activated TCI.

[1104] - Transmit HARQ in response to receiving a DL signal indicating an update / change of the TCI status, and / or

[1105] - The candidate TCI state is changed, activated, or reconfigured.

[1106] The UE cancels the triggered event, and / or the UE does not transmit the PN and / or UEI report used to trigger the event.

[1107] If the UE transmits the PN on the PN resource (e.g., Figure 23 t2), UE:

[1108] - Received a DL signal for (updating) the TCI status of activation / deactivation.

[1109] - The application has activated TCI status.

[1110] - (Update) Indicates the TCI status, applies the indicated TCI status,

[1111] - HARQ is transmitted in response to receiving a DL signal used to update / change the state of the activated TCI.

[1112] - Transmit HARQ in response to receiving a DL signal indicating an update / change of the TCI status, and / or

[1113] - The candidate TCI state is changed, activated, or reconfigured.

[1114] The UE cancels the triggered event, and / or the UE does not transmit the UEI report for the triggered event (or the UE avoids transmitting the UEI report for the triggered event), or alternatively, in some embodiments, the UE transmits a specific / default / empty UEI report to the network node. The UE may not monitor or receive network node responses to the UEI report from the network node. Alternatively, in some embodiments, the UE may ignore network node responses to the UEI report received from the network node. In other words, the UE may retransmit the UEI report without responding to a received network node response (e.g., indicating NACK or unsuccessful transmission / reception) or may transmit a new UEI report without responding to a received network node response.

[1115] Preferably, in some embodiments, the specific / default / empty UEI report may include specific / default / empty information for the current beam. Preferably, in some embodiments, the specific / default / empty UEI report may include information indicating specific / default / empty information associated with the current beam. Preferably, in some embodiments, based on one or more specific events associated with the candidate beam or the current beam, the UE may determine the specific / default / empty information to report for the candidate beam or the current beam.

[1116] Preferably, in some embodiments, regardless of whether the timing of receiving the DL signal indicating a change / update of the current beam is before or after the timing of the PN resource (as associated with the triggered event), the UE cancels all triggered events (as associated with the current beam). Preferably, in some embodiments, regardless of whether the timing of receiving the DL signal indicating a change / update of the candidate beam is before or after the timing of the PN resource (as associated with the triggered event), the UE cancels all triggered events (as associated with the candidate beam).

[1117] Preferably, in some embodiments, based on the DL signal (e.g., a DCI format having a TCI field indicating a TCI code point different from the currently used / applied / indicated TCI code point), the new current beam corresponds to the indicated TCI state or an activated TCI state. Preferably, in some embodiments, one or more candidate beams correspond to one or more configured TCI states or MAC CEs that activate one or more TCI states. Preferably, in some embodiments, the update of one or more new candidate beams is associated with a (currently) triggered event. Preferably, in some embodiments, the update of one or more new candidate beams is associated with the (currently) serving cell. Preferably, in some embodiments, if the update of a new candidate beam is not associated with a (currently) triggered event, then the update of the new candidate beam does not affect the triggered event. Alternatively, in some embodiments, based on a first event and a second event associated with the same serving cell or the same BWP, or the same co-frequency band, or the same cell group, or the same PUCCH group, or other similar characteristics (e.g., the same serving cell, the same measurement RS), once the UE has triggered the first event and the second event and applied the update of the new candidate beam, the UE can cancel both the first and second triggered events due to the one or more specific events (associated with beam change / update).

[1118] Preferably, in some embodiments, when the UE has triggered a first event and a second event, wherein the first event is associated with the current beam and a first set of candidate beams and the second event is associated with a candidate beam and a second set of candidate beams, once the UE has detected one or more specific events associated with the current beam (e.g., changing / updating the current beam), the UE cancels both the first and second triggered events in response to the one or more specific events (and does not transmit a UEI report associated with the first event or a UEI report associated with the second event in response to the one or more specific events). Preferably, in some embodiments, if the UE has transmitted a PN for a UEI report associated with the first event, but the UE does not transmit a PN for a UEI report associated with the second event, then once the UE detects one or more specific events associated with the current beam (e.g., changing / updating the current beam), the UE may have the same or different actions. Preferably, in some embodiments, the UE cancels the second triggered event in response to detecting the one or more specific events associated with the current beam. Preferably, in some embodiments, the UE does not cancel the first triggered event in response to detecting one or more specific events that are associated with the current beam.

[1119] In another instance, once the UE detects one or more specific events associated with both the first group of candidate beams and the second group of candidate beams (e.g., changing / updating one or more candidate beams that overlap with both the first group of candidate beams and the second group of candidate beams), the UE cancels both the first triggered event and the second triggered event in response to the one or more specific events (and does not transmit the UEI report associated with the first event or the UEI report associated with the second event in response to the one or more specific events).

[1120] For other instances, once the UE detects one or more specific events associated with the first group of candidate beams but not with the second group of candidate beams (e.g., changing / updating one or more candidate beams that overlap with the first group of candidate beams but not with the second group of candidate beams), the UE cancels the first triggered event and does not cancel the second triggered event in response to the one or more specific events (and does not transmit the UEI report associated with the first event but transmits the UEI report associated with the second event in response to the one or more specific events).

[1121] When the UE receives (re)configuration and / or (revoked) activation of PN resources and / or resources used for UEI reporting, the UE cancels the triggered event (regardless of whether the UE transmitted PN on the old PN resources). Alternatively, in some embodiments, the UE does not expect to receive (re)configuration and / or (revoked) activation of PN resources and / or resources used for UEI reporting between the timing of the old PN resources and the (corresponding) resources used for UEI reporting.

[1122] The UE can be configured with a PUCCH group, which includes a PCell and a PUCCH-sSecondary cell (sSCell) (i.e., an Scell ​​for supporting PUCCH carrier handover). PUCCH transmission for the PUCCH group occurs between the PCell and the PUCCH-sSCell. Preferably, in some embodiments, the UE does not expect to be configured with both PUCCH carrier handover and UEI reporting. Preferably, in some embodiments, the UE expects PN resources and / or resources for UEI reporting to be configured in one cell or carrier. Preferably, in some embodiments, for a given configuration associated with UEI reporting, the UE does not expect PN resources in time 1 and resources for UEI reporting in time 2 to be transmitted in different cells or carriers. Preferably, in some embodiments, for a given configuration associated with UEI reporting, PN resources and / or resources for UEI reporting are restricted to being configured in the same carrier. Preferably, in some embodiments, even for different times, the UE does not expect PN resources in time 1 and PN resources in time 2 to be transmitted in different carriers. Preferably, in some embodiments, the UE is configured to transmit PN resources without performing PUCCH carrier handover (if the UE is configured for PUCCH carrier handover). Preferably, in some embodiments, the UE does not expect to transmit PN and UEI reports on different carriers. Alternatively, in some embodiments, the UE may transmit on a first bundle of PN resources and resources for UEI reports in a PCell, and on a second bundle of PN resources and resources for UEI reports in a PUCCH-sSCell. Preferably, in some embodiments, for a given bundle of PN resources and resources for UEI reports, the UE does not expect to receive a signal indicating a change in the serving cell for PUCCH transmission within the bundle. Preferably, in some embodiments, the UE does not expect to have or receive a signal indicating a different cell for associated PN resources and resources for UEI reports. Based on the timing of the received signal indicating carrier handover, the UE can determine whether to apply PUCCH carrier handover and / or the UE can determine whether a bundle of PN resources and resources for UEI reports is valid. Preferably, in some embodiments, if the UE receives a signal indicating carrier handover before transmitting PN (e.g., ...), Figure 23 If t1 is specified in the original text, then when there is a handover between PN resources and resources used for UEI reporting, the UE transmits PN on the first cell and transmits UEI reports on the second cell. Alternatively, in some embodiments, the UE determines that this bundle of PN resources and resources used for UEI reporting are not valid due to carrier handover information. Preferably, in some embodiments, if the UE receives a signal indicating carrier handover information after transmitting PN (e.g., ...), ... Figure 23If t2), then when there is a handover between the PN resource and the resource used for UEI reporting, the UE transmits the PN on the first cell and the UEI report on the second cell. Alternatively, in some embodiments, the UE cancels the transmission of the UEI report on the second cell. Preferably, in some embodiments, the UE changes from mode B to mode A. Preferably, in some embodiments, the UE expects to receive a gNB signal for requesting a pending UEI report during the window period. Alternatively, in some embodiments, the UE does not expect a signal indicating information about the carrier handover between the PN resource and the resource used for UEI reporting. In one instance, the signal may indicate a PUCCH carrier handover for a TTI other than the TTI associated with the PN resource and the TTI associated with the resource used for UEI reporting. Preferably, in some embodiments, the TTI between the PN resource and the resource used for UEI reporting may be indicated as being transmitted in the second serving cell, while the PN resource and the resource used for UEI reporting are indicated as being transmitted in the first serving cell.

[1123] Preferably, in some embodiments, the PN resource includes different or the same number of symbols, PRB number, PUCCH format, start symbol and / or start PRB.

[1124] The UE can be configured with both Mode B associated with UEI reporting and network node request reporting. Once a request is received from the network node before transmitting the PN resource (e.g., ...), Figure 23If t1 occurs, the UE will cancel the transmission of PN and UEI reports on the PN resource. Preferably, in some embodiments, both the PN resource and the UEI report are in response to or associated with a triggered event. Preferably, in some embodiments, the triggered event is associated with at least one candidate beam and one current beam. The UE can determine whether to cancel the transmission of PN and UEI reports on the PN resource based on whether the request is associated with the at least one candidate beam or the current beam. If the request is associated with the at least one candidate beam or the current beam, the UE can cancel the transmission of PN and UEI reports on the PN resource. If the request is not associated with either the at least one candidate beam or the current beam, the UE does not cancel the transmission of PN and UEI reports on the PN resource (in response to or due to the request). Preferably, in some embodiments, the UE transmits PN and UEI reports on the PN resource. Preferably, in some embodiments, the UE can determine whether to cancel the transmission of PN and UEI reports on the PN resource based on whether there is a (time domain) overlap between the UL resource used for transmitting network node request reports and the PN resource, or between the UL resource used for transmitting network node request reports and the resource used for transmitting UEI reports. Preferably, in some embodiments, the UE cancels the transmission of UEI reports and / or PN reports when there is a (time domain) overlap between the UL resource used for transmitting network node request reports and the PN resource, or between the UL resource used for transmitting network node request reports and the resource used for transmitting UEI reports. Alternatively, in some embodiments, the UE does not expect to receive signals from UL resources scheduled to overlap with the PN resource in the time domain (e.g., symbol domain and / or time slot domain overlap). Preferably, in some embodiments, after the PN is transmitted on the PN resource (e.g., ...), the UE cancels the transmission of PN and / or UEI reports on the PN resource. Figure 23 In t2), when there is overlap between the UL resources used to transmit the Network Node Request Report and the resources used to transmit the UEE Report, the UE prioritizes transmitting the Network Node Request Report. Preferably, in some embodiments, PN transmission is used to indicate a mode change of the UEI report from Mode B to Mode A due to the overlap between the Network Node Request Report and the resources used to transmit the UEI Report. Preferably, in some embodiments, if the Network Node Request Report is associated with the current beam and / or the candidate beam, the UE can cancel the UEI Report and / or the UE can cancel the triggered event. Alternatively, in some embodiments, the UE can multiplex the UCI between the Network Node Request Report and the UEI Report. Preferably, in some embodiments, the UE can discard a portion of the UEI Report. Preferably, in some embodiments, the UE can discard a portion of the Network Node Request Report. Preferably, in some embodiments, based on whether the PN is transmitted, the UE can determine whether to discard the UEI Report (or multiplex the UEI Report into the Network Node Request Report).

[1125] The UE may be configured with a cancellation mechanism for one or more UL resources. The cancellation may be indicated by a DL signal. Preferably, in some embodiments, the DL signal may be a group common DCI, a UE-specific DCI, or a MAC CE. Preferably, in some embodiments, the group common DCI corresponds to a DCI indicating a cancellation indication, which includes the cancellation of a (pre)configured resource for UEI reporting. Preferably, in some embodiments, the UE-specific DCI corresponds to a DCI that schedules higher-priority transmissions. Preferably, in some embodiments, if the UE receives a DL signal indicating the cancellation of a resource for UEI reporting before transmitting the PN, the UE determines the resource for transmitting the UEI report as invalid. If the UE receives a DL signal indicating the cancellation of a PN resource before transmitting the PN, the UE determines the resource for transmitting the UEI report as invalid. Preferably, in some embodiments, if either a bundle of resources for transmitting the UEI report or the PN resource is indicated by a DL signal to be cancelled before transmitting the PN, the UE determines the resource for transmitting the UEI report as invalid. Preferably, in some embodiments, if the UE receives a DL signal indicating the cancellation of a resource used for the UEI report after transmitting the PN (but before transmitting the UEI report), the UE cancels the UEI report. Preferably, in some embodiments, the UE does not expect to receive a DL signal indicating the cancellation of a resource used for the UEI report after transmitting the PN (but before transmitting the UEI report). Alternatively, in some embodiments, the UE does not expect DCI cancellation including (pre)configured resources. Preferably, in some embodiments, the cancellation timeline may include a processing offset preceding the PN resource and / or the resource used for transmitting the UEI report. Preferably, in some embodiments, if the UE receives cancellation before the processing offset, the UE may cancel the UEI report or the PN resource. Preferably, in some embodiments, if the UE receives cancellation within the processing offset, the UE transmits the UEI report or the PN. Preferably, in some embodiments, when the cancellation indication indicates the cancellation of the PN resource or the resource used for transmitting the UEI report, the UE does not expect to receive the cancellation indication within the processing offset.

[1126] Preferably, in some embodiments, the DL signal for cancellation may indicate a second resource for transmitting a UEI report or transmitting PN resources. Preferably, in some embodiments, the DL signal may provide a priority threshold.

[1127] Additionally and / or alternatively, in some embodiments, if or when the cell is deactivated, the UE may not transmit the UEI report or PN associated with the cell (on the PUCCH cell). If or when the cell is deactivated, the UE may treat the PN resources and / or UEI resources (as associated with the cell) as invalid or suspended. The PUCCH cell on which the UEI report and / or PN is transmitted may not be the same cell as said cell. Alternatively, in some embodiments, the PUCCH cell may be said cell.

[1128] All concepts, instances, and embodiments described above and herein may be combined, in whole or in part, to form new concepts, instances, and embodiments.

[1129] Various concepts, examples, and embodiments of the present invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[1130] See Figure 26 Regarding such and other concepts, systems and methods of the present invention, method 1000 for a UE in a wireless communication system includes determining, in response to one or more procedures, whether to perform one or more actions (step 1002) for a UE-initiated beam report in a cell, based at least on an event associated with the beam report initiated by the UE.

[1131] Return to reference Figure 3 and 4 In one or more embodiments, from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) determine, in response to one or more procedures, whether to perform one or more actions for a UE-initiated beam report in a cell, based at least on an event associated with such a beam report. Furthermore, CPU 308 may execute program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[1132] See Figure 27 Regarding such and other concepts, systems and methods of the present invention, method 1010 for a UE in a wireless communication system includes performing one or more actions (step 1012) in response to one or more procedures for a beam report initiated by the UE in a cell.

[1133] Return to reference Figure 3 and 4In one or more embodiments, from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) perform one or more actions in response to a beam report initiated by the UE of the cell in response to one or more programs. Furthermore, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[1134] In various embodiments, the cell can be a serving cell or an LTM candidate cell.

[1135] In various embodiments, the one or more procedures include / include BWP handover of the cell.

[1136] In various embodiments, the one or more procedures include / include the reactivation of a cell.

[1137] In various embodiments, the one or more procedures include / include cell activation.

[1138] In various embodiments, the one or more procedures include / include cell beam or TCI state activation / deactivation.

[1139] In various embodiments, the one or more procedures contain / include a BWP handover to a dormant DL BWP in the cell.

[1140] In various embodiments, the one or more procedures contain / include a (in-process) beam fault recovery or triggered BFR for the cell.

[1141] In various embodiments, the one or more procedures contain / include a (in progress) beam fault recovery or triggered BFR for a second cell, wherein the UE is configured or instructed on the second cell to transmit a UE-initiated beam report for the cell.

[1142] In various embodiments, the one or more procedures contain / include the expiration of a time alignment timer associated with the cell.

[1143] In various embodiments, the one or more procedures include / include the expiration of a TA timer (timealignment timer) associated with a second cell, on which the UE is configured or instructed to transmit a UE-initiated beam report for the cell.

[1144] In various embodiments, the one or more actions include / include an event that suspends beam reporting initiated by the UE.

[1145] In various embodiments, the one or more actions include / including stopping or restarting a timer associated with the timeToTrigger of an event, which is associated with a beam report initiated by the UE or with a cell.

[1146] In various embodiments, the one or more actions include / include discarding UE-initiated beam reports.

[1147] In various embodiments, the one or more actions include / include canceling a beam report initiated by the UE.

[1148] In various embodiments, the one or more actions include / include not generating a UE-initiated beam report.

[1149] In various embodiments, the event includes the quality of the cell's currently (active) beam falling below a threshold.

[1150] In various embodiments, the event includes a new (or candidate) beam in the cell whose quality exceeds a threshold.

[1151] In various embodiments, the event includes the fact that the quality of the cell's current (active) beam is below a threshold of the quality of the cell's new (or candidate) beam.

[1152] See Figure 28 ...

Claims

1. A method for a user equipment, characterized in that, include: A beam report initiated by a first user equipment configured to be associated with a serving cell, wherein the beam report initiated by the first user equipment is based on a comparison between the quality of the current beam of the serving cell and the quality of the candidate beams of the serving cell; Maintain a counter associated with a beam report initiated by the first user equipment of the serving cell, the counter being used to trigger a beam report initiated by the first user equipment of the serving cell; as well as The counter is reset in response to a beam change of the current beam on the serving cell.

2. The method according to claim 1, characterized in that, The counter is used to detect whether an event associated with a beam report initiated by the first user equipment is met within a time period.

3. The method according to claim 2, characterized in that, The event is that the quality of the candidate beam is higher than the quality of the current beam plus a first threshold.

4. The method according to claim 1, characterized in that, The user equipment maintains a first timer associated with a beam report initiated by the first user equipment, and the user equipment stops the first timer in response to a beam change of the current beam on the serving cell.

5. The method according to claim 1, characterized in that, In response to the beam change of the current beam on the serving cell, the user equipment does not restart or stop the second timer associated with the beam report initiated by the second user equipment associated with the candidate cell.

6. The method according to claim 5, characterized in that, The second timer is timeToTrigger(ttt), and the second timer is a time during which an event needs to be satisfied in order to trigger a beam report of a Layer 1 event associated with the candidate cell.

7. The method according to claim 6, characterized in that, The event is when the quality of the candidate beam associated with the candidate cell is higher than the quality of the current beam of the serving cell plus a second threshold.

8. The method according to claim 5, characterized in that, The candidate cells are associated with candidate configurations for mobility triggered at Layer 1 / Layer 2.

9. The method according to claim 5, characterized in that, The beam report initiated by the second user equipment is for mobility triggered by Layer 1 / Layer 2.

10. The method according to claim 1, characterized in that, The current beam is the activation of the serving cell or the indicated transmission configuration indication state.

11. The method according to claim 1, characterized in that, The candidate beam is associated with the transmission configuration indication status or reference signal of the serving cell.

12. The method according to claim 1, characterized in that, The beam change of the current beam is indicated by the network via downlink control information, media access control control elements, or radio resource control reconfiguration.

13. The method according to claim 1, characterized in that, The beam report initiated by the first user equipment is used for multiple input multiple output and / or for intra-cell beam management.

14. The method according to claim 1, characterized in that, The user equipment is configured with discontinuous reception, including a discontinuous reception mode for both inactive and active periods of discontinuous reception. The user equipment is also configured with one or more resource bundles for beam reports initiated by the first user equipment. One of these resource bundles includes physical uplink control channel resources for transmitting pre-notification and physical uplink shared channel resources for transmitting beam reports initiated by the user equipment. Furthermore, based on the fact that at least the physical uplink control channel resources and the physical uplink shared channel resources are both active during the cell discontinuous reception period, the user equipment transmits the beam report initiated by the user equipment on the physical uplink shared channel resources. Conversely, based on the fact that either the physical uplink shared channel resources or at least one of the physical uplink shared channel resources is inactive during the cell discontinuous reception period, the user equipment does not transmit the beam report initiated by the user equipment on the physical uplink shared channel resources.

15. A user equipment, characterized in that, include: Memory; as well as A processor, operably coupled to the memory, wherein the processor is configured to execute program code to: A beam report initiated by a first user equipment configured to be associated with a serving cell, wherein the beam report initiated by the first user equipment is based on a comparison between the quality of the current beam of the serving cell and the quality of the candidate beams of the serving cell; Maintain a counter associated with a beam report initiated by the first user equipment of the serving cell, the counter being used to trigger a beam report initiated by the first user equipment of the serving cell; as well as The counter is reset in response to a beam change of the current beam on the serving cell.

16. The user equipment according to claim 15, characterized in that, The counter is used to detect whether an event associated with a beam report initiated by the first user equipment is met within a time period.

17. The user equipment according to claim 16, characterized in that, The event is that the quality of the candidate beam is higher than the quality of the current beam plus a first threshold.

18. The user equipment according to claim 15, characterized in that, The user equipment maintains a first timer associated with a beam report initiated by the first user equipment, and the user equipment stops the first timer in response to a beam change of the current beam on the serving cell.

19. The user equipment according to claim 15, characterized in that, In response to the beam change of the current beam on the serving cell, the user equipment does not restart or stop the second timer associated with the beam report initiated by the second user equipment associated with the candidate cell.

20. The user equipment according to claim 15, characterized in that, The user equipment is configured with discontinuous reception, including a discontinuous reception mode for both inactive and active periods of discontinuous reception. The user equipment is also configured with one or more resource bundles for beam reports initiated by the first user equipment. One of these resource bundles includes physical uplink control channel resources for transmitting pre-notification and physical uplink shared channel resources for transmitting beam reports initiated by the user equipment. If at least the physical uplink control channel resources and the physical uplink shared channel resources are both active during the discontinuous reception period, the user equipment transmits the beam report initiated by the user equipment on the physical uplink shared channel resources. If, during the discontinuous reception inactive period, the user equipment does not transmit the beam report initiated by the user equipment on the physical uplink shared channel resources, the user equipment does not transmit the beam report initiated by the user equipment on the physical uplink shared channel resources.

Images