Method and apparatus for handling user equipment-initiated beam reporting in a wireless communication

Abstract

A method and device for handling a beam report initiated by a user equipment in wireless communications are provided, where the method of the user equipment comprises: configuring a beam report initiated by a first user equipment 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 the candidate beam of the serving cell; maintaining a counter associated with a beam report initiated by a first user equipment of the serving cell; and resetting the counter in response to a beam change of the current beam on the serving cell.

Description

(19) State Intellectual Property Office (12) Invention Patent Application (10) Application Publication Number (43) Application Publication Date (21) Application Number 202510594099.0 (22) Application Date 2025.05.09 (30) Priority Data 63 / 644,989 2024.05.09 US 63 / 645,012 2024.05.09 US (71) Applicant ASUS Technology Licensing Co., Ltd. Address Taipei, Taiwan (72) Inventors Huang Junwei, Guo Yuxuan, Gong Yixuan (74) Patent Agency Beijing Liu Shen Law Firm 11105 Patent Attorney Xu Xiecheng (51) Int.Cl. H04W 24 / 10 (2009.01) H04W 36 / 00 (2009.01) H04W 36 / 08 (2009.01) H04W 36 / 30 (2009.01) (54) Invention Title: Method and Apparatus for Handling Beam Reports Initiated by User Equipment in Wireless Communication (57) Abstract: A method and apparatus for handling beam reports initiated by a user equipment in wireless communication are provided, wherein a method of 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 of the serving cell; and resetting the counter in response to a beam change of the current beam on the serving cell. Claims 2 pages, Description 94 pages, Drawings 20 pages, CN 120935649 A 2025.11.11 CN 1 20 93 56 49 A 1. A method for a user equipment, characterized in that it comprises: 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 a 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 of the serving cell; and resetting the counter in response to a beam change of the current beam on the serving cell. 2. The method of claim 1, wherein the counter is used to detect whether an event associated with the beam report initiated by the first user equipment is satisfied within a time period. 3. The method of claim 2, wherein 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 of claim 1, wherein the user equipment maintains a beam report associated with the first user equipment.5. The method of claim 1, wherein, in response to the beam change of the current beam on the serving cell, the user equipment does not restart or stop a second timer associated with a beam report initiated by a second user equipment associated with a candidate cell. 6. The method of claim 5, wherein the second timer is a timeToTrigger(ttt), and wherein the second timer is a time during which an event needs to be satisfied to trigger a beam report triggered by a Layer 1 event associated with the candidate cell. 7. The method of claim 6, wherein the event is that the quality of a 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 of claim 5, wherein the candidate cell is associated with a candidate configuration for Layer 1 / Layer 2 triggered mobility. 9. The method of claim 5, wherein the beam report initiated by the second user equipment is for Layer 1 / Layer 2 triggered mobility. 10. The method of claim 1, wherein the current beam is an activation or indicated transmission configuration indication state of the serving cell. 11. The method of claim 1, wherein the candidate beam is associated with the transmission configuration indication state or reference signal of the serving cell. 12. The method of claim 1, wherein the beam change of the current beam is indicated by network reconfiguration via downlink control information, media access control elements, or radio resource control. 13. The method of claim 1, wherein the beam report initiated by the first user equipment is for multiple-input multiple-output and / or for intra-cell beam management. 14. A user equipment, characterized in that it comprises: a memory; and a processor operably coupled to the memory, wherein the processor is configured to execute program code to: be configured with a beam report initiated by a first user equipment 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 a candidate beam of the serving cell; maintain a counter associated with the beam report initiated by the first user equipment of the serving cell; and reset the counter in response to a beam change of the current beam on the serving cell. 15. The user equipment of claim 14, characterized in that the counter is used to detect within a time period...16. The user equipment of claim 15, wherein the event is that the quality of the candidate beam is higher than the quality of the current beam plus a first threshold. 17. The user equipment of claim 14, wherein the user equipment maintains a first timer associated with the 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. 18. The user equipment of claim 14, wherein in response to a beam change of the current beam on the serving cell, the user equipment does not restart or stop a second timer associated with a beam report initiated by a second user equipment associated with a candidate cell. 19. The user equipment of claim 18, wherein the second timer is a timeToTrigger(ttt), and wherein the second timer is a time during which an event needs to be satisfied to trigger a Layer 1 event-triggered beam report associated with the candidate cell. 20. The user equipment of claim 19, wherein the event is that the quality of a candidate beam associated with the candidate cell is higher than the quality of the current beam of the serving cell plus a second threshold. Claims 2 / 2 Page 3 CN 120935649 A Method and apparatus for handling beam reports initiated by a user equipment in wireless communication

[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, wherein each of the applications and disclosures 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 particularly to methods and apparatus for handling beam reports initiated by a user equipment (UE) in wireless communication systems. Background Art

[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) packets. This IP packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and on-demand communication services.

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

[0006] A method, system, 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 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 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 UE in the serving cell; and resetting the counter in response to a beam change of the current beam on the serving cell. Brief Description of the Drawings

[0007] FIG1 shows a drawing of a wireless communication system according to an embodiment of the present invention.

[0008] FIG2 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] FIG3 is a functional block diagram of a communication system according to an embodiment of the present invention.

[0010] FIG4 is a functional block diagram of the program code of FIG3 according to an embodiment of the present invention.

[0011] FIG5 is a reproduction of FIG6.1.3.23-1: BFR and a truncated BFR MAC CE with one octet Ci field in 3GPP 38.321 v17.4.0.

[0012] FIG6 is a reproduction of FIG6.1.3.23-2: BFR and a truncated BFR MAC CE with four octet Ci fields in 3GPP 38.321 v17.4.0, page 1 / 94 of specification 4 CN 120935649 A.

[0013] Figure 7 is a reproduction of Figure 9.2.3.5.2-1, the signaling procedure for LTM, in draft 38.300 v 18.0.0.

[0014] Figure 8 is a reproduction of Figure 6.1.3.75-1, LTM cell handover command MAC CE, in 3GPP 38.321 v18.1.0.

[0015] Figure 9 is a reproduction of Figure 6.1.3.76-1, candidate cell TCI state activation / deactivation activation MAC CE, in 3GPP 38.321 v18.1.0.

[0016] Figure 10A is an example drawing illustrating a problem where the network may receive outdated beam information or the UE may transmit unnecessary beam report information when two procedures conflict, according to an embodiment of the present invention.

[0017] Figure 10B is an illustration of an embodiment of the present invention showing that the UE can determine or discover that at t1, the trigger for the cell is satisfied.Figure 11 is an example of an illustration of an event reported according to an embodiment of the present invention, showing that the UE can determine whether to perform an action in response to a beam report initiated by the UE based at least on the type of the procedure.

[0019] Figure 12 is an example of an illustration of an embodiment of the present invention, showing that the UE determines whether to perform action 1 in response to a beam report initiated by the UE based on different events associated with the beam report initiated by the UE.

[0020] Figure 13A is an example of an illustration of an embodiment of the present invention, showing that the UE determines whether to perform actions 1 and 2 in response to a beam report initiated by the UE based on different events associated with the beam report initiated by the UE.

[0021] Figure 13B is an example of an illustration of an embodiment of the present invention, showing that the UE can be configured with a UE-initiated beam report configuration (e.g., for MIMO) associated with the serving cell.

[0022] Figure 14 is an example of an illustration of an embodiment of the present invention, showing that at time t1, the UE measures the cell A (or the RS associated with it) associated with the beam report initiated by the UE.

[0023] FIG. 15 is an example drawing illustrating that a UE can perform a measurement (RS) on cell B according to an embodiment of the present invention.

[0024] FIG. 16 is an example drawing illustrating that a UE can measure cell C (on or associated with the RS) and determine at t1 that the quality of activated TCI state A is less than a threshold of cell C.

[0025] FIG. 17 is an example drawing illustrating that at time t1, the UE triggers a UE-initiated beam report for serving cell A according to an embodiment of the present invention.

[0026] FIG. 18 is an example drawing illustrating that at time t1, the UE initiates a beam fault recovery procedure for serving cell A (e.g., SpCell) according to an embodiment of the present invention.

[0027] FIG. 19 is an example drawing illustrating that at time t1, the UE initiates or executes a random access procedure (e.g., handover, reconfiguration with synchronization, or LTM) according to an embodiment of the present invention.

[0028] FIG. 20 is an example drawing illustrating candidate RS, CSI reference resources, PN, and (pre)configured resources for determining the quality of candidate beams according to an embodiment of the present invention.

[0029] FIG21 is an example drawing illustrating, according to an embodiment of the present invention, that a UE may be (pre-)configured with three pairs or three bundles of PN resources, denoted as A, B, and C, and resources for UEI reporting.

[0030] FIG22 is an example drawing illustrating, according to an embodiment of the present invention, that a first dynamic signal (starting from the left of the figure) deactivates cell DRX, which means the active time within a time interval, and a second dynamic signal activates cell DRX, which means the cell DRX active time and cell DRX inactive time are based on an on-time duration timer associated with the cell DRX configuration.

[0031] Figure 23 is an example drawing illustrating a method for a solution primarily targeting the existence / occurrence / triggering of one or more specific events at or overlapping with said timing t1, according to an embodiment of the present invention.

[0032] Figure 24 is an example drawing illustrating 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, according to an embodiment of the present invention.

[0033] Figure 25 is an example drawing illustrating that a UE can be configured with associations, i.e., each PN resource can correspond to more than one resource for UEI in one or more BWPs (cross-BWP indication for supporting PN resources and resources for UEI reporting).

[0034] Figure 26 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 UE-initiated beam report in a cell, based at least on an event associated with a beam report initiated by the UE.

[0035] FIG. 27 is a flowchart of a method of 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] FIG. 28 is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention, the method including: being configured with a beam report initiated by a first UE 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] FIG. 29 is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention, the method including: receiving a first CSI report configuration associated with a report initiated by the UE; generating a report initiated by the first UE based on a condition satisfying a first event; transmitting a PN on a first UL resource at a first timing; and transmitting the report initiated by the first UE on a second UL resource at a second timing.

[0038] FIG30 is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention, the method comprising: 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 a 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 event if at least a second event is later than a first event; receiving a signal indicating a change in an active UL BWP from a network node at a second event; and transmitting a PN on a second event at a third event if at least the second event is later than the first event.Transmit the report initiated by the first UE on the PUSCH resource. Detailed Description

[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 primarily described 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, data, etc. These systems can 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, 3GPP2 Ultra Mobile Broadband (UMB), 3GPP New Radio (NR), or some other modulation techniques.

[0041] Specifically, the exemplary wireless communication systems and apparatus described below can be designed to support one or more standards, such as the standards provided by the consortium referred to herein as 3GPP, which is named the “3rd Generation Partnership Project”, page 3 / 94, CN 120935649 A, 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.300v18.0.0; [6] RP-234036 New WID: NR Mobility Enhancement Phase 4; [7] 3GPP 38.321v18.1.0; [8] Chairman's Notes RAN1#116eom0; and [9] Chairman's Notes RAN1#116bis eom0;

[10] 3GPP TS 38.214V17.3.0 (2022-09) Third Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedures for Data (Version 17); and

[11] 3GPP TS38.213V18.2.0(2024-03) Third Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedure for Control (Version 18). The standards and documents listed above are hereby expressly and entirely incorporated herein by reference.

[0042] Figure 1 illustrates a multiple access wireless communication system according to an embodiment of the present invention. Access network 100 (AN) includes multiple antenna groups, one containing 104 and 106, another containing 108 and 110, and another containing 112 and 114. In Figure 1, only two antennas are shown for each antenna group; however, more or fewer antennas may be used for each antenna group. Access terminal (AT) 116 communicates with antennas 112 and 114, wherein antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, wherein antennas 106 and 108 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 frequency different from that used by 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 communication 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 of the 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 the entire coverage area of ​​the access network typically causes less interference to access terminals in neighboring cells.

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

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

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

[0048] The decoded data of each data stream can be multiplexed with pilot data using OFDM technology. 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 the 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 a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM) as described on page 4 / 94 of the specification (CN 120935649 A). The TX MIMO processor 220 then provides NT modulation symbol streams to NT transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and the antennas from which the symbols are transmitted.

[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 upconverts) the analog signals to provide modulated signals suitable for transmission via the MIMO channel. The NT modulated signals from transmitters 222a to 222t are then transmitted from the NT antennas 224a to 224t, respectively.

[0051] At receiver system 250, the transmitted modulated signal is received by NR antennas 252a to 252r, and the signal received from each antenna 252 is provided to the 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 the corresponding “received” symbol stream.

[0052] RX data processor 260 then receives and processes NR received symbol streams from NR receivers 254 based on a specific receiver processing technique to provide NT “detected” symbol streams. RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the service data for the data stream. The processing performed by RX data processor 260 is synchronized with the TX signal received by transmitter system 210.The processing performed by MIMO processor 220 and TX data processor 214 is complementary.

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

[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 TX data processor 238 (which also receives traffic data from several data streams from data source 236), modulated by modulator 280, regulated by transmitters 254a to 254r, and transmitted back to transmitter system 210.

[0055] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, regulated 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 messages.

[0056] Memory 232 can be used to temporarily store some buffered / computational 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 / computational data from 260 via processor 270, some buffered data from 236, or some specific program code.

[0057] Turning to FIG. 3, this figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As shown in FIG. 3, a communication device 300 in a wireless communication system can be used to implement UE (or AT) 116 and 122 in FIG. 1, and the wireless communication system is preferably an NR system. 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 the 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, transmit the received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.

[0058] FIG4 is a simplified block diagram of the program code 312 shown in FIG3 according to an embodiment of the present invention. In this embodiment, the 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 connection.

[0059] For LTE, LTE-A, or NR systems, Layer 2 portion 404 may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. Layer 3 portion 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 paragraphs or sections of the invention may be implemented independently and separately to form a particular method or apparatus. In the following disclosure of the present invention, dependencies such as "based on," "more specifically," and "example" are merely one possible embodiment that does not limit a particular method or device.

[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 reports (e.g., N best beams and corresponding L1-RSRPs) or trigger frequent non-periodic beam reports in order to obtain the best / preferred beam for data / control transmission in a timely manner. However, this obviously leads to large UL report overhead and control signaling overhead. At the same time, if less frequent beam reports are configured, the network cannot always obtain the "best / preferred" beam because the UE's beam report may be outdated, resulting in performance degradation. Considering that the UE has a better and more timely understanding of beam quality changes, the UE-initiated beam reporting procedure can cause more timely beam reporting, but with reduced reporting overhead. In such a procedure, if the UE determines, for example, that the current beam quality has deteriorated, the UE can trigger a beam report without network configuration or triggering frequent reports.

[0065] …

[0066] 4 Objectives

[0067] 4.1 Objectives of SI or Core Part WI or Test Part WI

[0068] Detailed objectives are as follows:

[0069] RAN1:

[0070] 1. Specify enhancements to facilitate UE-initiated / event-driven beam management to reduce overhead and / or latency, assuming a unified TCI, while (as much as possible) utilizing the existing CSI measurement and reporting configuration framework to have intra-cell and smallFR2 and sTRP for Interval 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, taking into account the UE-initiated / event-driven nature of UL transmission

[0073] …

[0074] Acronyms:

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

[0076] ● mTRP: Multiple TRP (Transmit / Receive Point)

[0077] In [2] 3GPP 38.214v17.4.0, CSI reporting is described:

[0078] 5.2 UE procedures for reporting Channel State Information (CSI)

[0079] 5.2.1 Channel State Information Framework Specification 6 / 94 pages 9 CN 120935649 A

[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 layer parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize.

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

[0082] For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, and capability [set] indexes, 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 an associated CSI-AperiodicTriggerStateList indicating the resource set ID used for the channel and optionally for interference.A list of ReportConfigs. Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList contains an associated CSI-ReportConfig.

[0083] 5.2.1.1 Report Settings

[0084] Each report setting CSI-ReportConfig is associated with a single downlink BWP (indicated by the higher layer parameter BWP-Id) given in the associated CSI-ResourceConfig 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 items 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 contains a configuration of 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 Reporting Configuration

[0090] The UE shall assume the following dependencies between CSI parameters (if reported) to calculate the CSI parameters (if reported):

[0091] - LI shall be calculated conditioned on the reported CQI, PMI, RI, and CRI

[0092] - CQI shall be calculated conditioned on the reported PMI, RI, and CRI

[0093] - PMI shall be calculated conditioned on the reported RI and CRI

[0094] - RI shall be calculated conditioned on the reported CRI.

[0095] The reporting configuration for CSI 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 configuration and CSI-RS resource configuration and how to target each CSI-RS resource configuration.RS resource configuration triggers CSI reports. Periodic CSI-RS is configured by a higher layer. Semi-persistent CSI-RS is activated and deactivated as described in Clause 5.2.1.5.2. Non-periodic CSI-RS is configured and triggered / activated as described in Clause 5.2.1.5.1.

[0096] Table 5.2.1.4-1: Triggering / activation of CSI reports for possible CSI-RS configurations.

[0097]

[0098]

[0099] …

[0100] 5.2.1.4.1 Resource Setting Configuration

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

[0102] - When a resource setting is configured, the resource setting (given by the higher-layer 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 three resource settings are configured, the first resource setting (given by the higher-layer parameter resourcesForChannelMeasurement) is for channel measurement, the second (given by the higher-layer parameter csi-IM-ResourcesForInterference) is for CSI-IM-based interference measurement, and the third (given by the higher-layer parameter nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS-based interference measurement.

[0105] For aperiodic CSI, and for both 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 for L1-RSRP measurements, respectively corresponding to the first and second resource sets.

[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-layer 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 for channel measurements, and the second resource setting (given by the higher-layer parameter csi-IM-ResourcesForInterference) is for interference measurements performed on CSI-IM. For L1-SINR calculation, the second resource setting (given by the higher-layer parameter csi-IM-ResourcesForInterference or the higher-layer parameter nzp-CSI-RS-ResourceForInterference) is 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, where the higher-level parameter reportQuantity is set to 'none', the UE will not report any number of CSI-ReportConfig items.

[0115] …

[0116] If the UE is configured with CSI-ReportConfig, where 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 the different CRI or SSBRI for each report 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, wherein 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-layer parameter groupBasedBeamReporting-r17, the UE does not need to update measurements for more than 64 CSI-RS and / or SSB resources, and the UE will report measurements for more than 64 CSI-RS and / or SSB resources in a single report instance nrofReportedGroups (if...In the configuration, the report uses a group of two CRIs or SSBRIs selected from each of two CSI resource sets for the reporting settings, 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, where the higher layer 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 layer parameter groupBasedBeamReporting set to 'disable', then the UE will report different CRIs or SSBRIs for each reporting setting in a single report nrofReportedRS (configured by the higher layer).

[0122] - If the UE is configured to use the higher-layer parameter groupBasedBeamReporting set to 'Enable', 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 Reporting

[0125] For L1-RSRP Calculation

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

[0127] - The UE may be configured with CSI-RS resource settings for up to 16 sets of CSI-RS resources, 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 with a 1dB step size in the range [-140, -44] dBm. 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, then the UE should use differential L1-RSRP reporting, where the maximum measured value of L1-RSRP is quantized to have a 1dB step size in the range [-140, -44] dBm.The 7-bit value within 44 dBm, and the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is calculated with a 2 dB step size, referencing the maximum measured L1-RSRP value as part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133]. Specification 10 / 94 pages 13 CN 120935649 A

[0129] When the higher-layer 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-layer 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 associated with the CSI resource setting no later than the CSI reference resource (defined in TS 38.211[4]) 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 only based on the most recent timing of the SS / PBCH or NZP CSI-RS associated with the CSI resource setting no later than the CSI reference resource (defined in TS 38.211[4]) for calculating the L1-RSRP reported in uplink slot n.

[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, wherein each SSB index is associated with a PCI index.

[0133] When the UE is configured with CSI-ReportConfig, wherein 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 Aperiodic CSI Reporting / Aperiodic CSI-RS When PDCCH and CSI-RS Have the Same Base Parameters

[0136] For a CSI-RS resource set associated with a resource setting configured with a higher-layer parameter resource Type 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 report triggering, a single set of CSI trigger states is configured by the higher layer, where the 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 configured 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 a time slot that overlaps with any time slot in the same cell group in which aperiodic CSI report transmission occurs. If the UE does not indicate its capability CSITriggerStateContainingNonactiveBWP, it is not expected that the UE will trigger with a CSI report for a non-active DL BWP. Otherwise, when the UE triggers a CSI report for an inactive DL BWP at the latest time no later than the CSI reference resource when the associated NZP CSI-RS is expected to be received, the UE is not expected to report a CSI for the inactive DL BWP, and the CSI report associated with the BWP is omitted. When the UE triggers an aperiodic NZP CSI-RS in an inactive DL BWP when the NZP CSI-RS is expected to be received, 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 expected to be received, if the active DL BWP at the time of receiving the NZP CSI-RS is different from the active DL BWP at the time of receiving the DCI trigger, 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 (page 11 / 94, CN 120935649 A), 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 carrying CSI triggering and before the first symbol of the triggered NZP CSI-RS or CSI-IM.

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

[0140] The triggering state is initiated using the CSI request field in the DCI.

[0141] …

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

[0143] For semi-static reporting on 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 by a CSI request field scrambled with SP-CSI-RNTI. It is not expected that the UE will receive a DCI scrambled with SP-CSI-RNTI that activates a semi-static CSI report having the same CSI-ReportConfigId as a semi-static CSI report activated by a previously received DCI scrambled with SP-CSI-RNTI.

[0144] For semi-static reporting on PUCCH, the PUCCH resource used to transmit the CSI report is configured via reportConfigType. Semi-static reporting on the 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 of the PDSCH corresponding to the activation command, the indicated semi-persistent reporting setting shall be applied starting from the first slot after the slot, where μ is the SCS configuration for the PUCCH.

[0145] For a UE configured with a CSI resource setting in which the higher layer parameter resourceType is set to 'semi-persistent'.

[0146] - As described in [10, TS 38.321]As described in Clause 6.1.3.12 of [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 will transmit 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 with the configured CSI-RS / CSI-IM resource settings shall be applied from the first slot after the slot, where μ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for kmac, having a value of 0 for frequency range 1, and kmac is provided by K-Mac, or if K-Mac is not provided, then kmac = 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 the configured CSI resource settings, 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 assumption that the transmission of CSI-RS / CSI-IM corresponding to the deactivated CSI-RS / CSI-IM resource set is stopped should be applied from the first slot after the slot, as stated on page 12 / 94 of the specification, 15 CN 120935649 A, where μ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for kmac, having a value of 0 for frequency range 1, and kmac is provided by K-Mac, or if K-Mac is not provided, then kmac = 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 transmission.

[0152] A MAC entity may 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 consistent LBT fault recovery (see Section 5.21), at most one PUCCH resource is configured for SR per BWP. 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 the cell, at most two PUCCH resources are configured for SR per BWP. For positioning measurement gap activation / deactivation requests, a dedicated SR configuration is configured.

[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 the RRC. The SR configuration of the logical channel that triggers a BSR (clause 5.4.5), SCell beam fault recovery, BFD-RS set beam fault recovery, or consistent LBT fault recovery (clause 5.21) (if this configuration exists), or a location measurement gap activation / deactivation request (clause 5.25) is considered as 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 an advance timing report (clause 5.4.8).

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

[0155] -sr-ProhibitTimer (according to the SR configuration);

[0156] -sr-TransMax (according to the SR configuration).

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

[0158] -SR_COUNTER (according to 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 cancelled.

[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 does not have a valid PUCCH resource configured for the pending SR:

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

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

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

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

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

[0169] … Specification 13 / 94 pages 16 CN 120935649 A

[0170] 4> Treat the SR transmission as a priority SR transmission.

[0171] 4> Treat other overlapping uplink grants (if any) as de-prioritized uplink grants, except for overlapping uplink grants whose simultaneous transmission is permitted by the configuration of simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup, or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0172] 4> If the de-prioritized uplink grant is a configured uplink grant with autonomousTx whose PUSCH has already started:

[0173] 5> Stop the configuredGrantTimer for the corresponding HARQ procedure used for the de-prioritized uplink grant;

[0174] 5> Stop the cg-RetransmissionTimer for the corresponding HARQ procedure used for the de-prioritized uplink grant.

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

[0176] 5> Instruct the physical layer to send the SR on a valid PUCCH resource 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 for all serving cells;

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

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

[0186] 5> Clear 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 the upper layer requests a reset of the MAC entity or the MAC entity is triggered by the revocation of SCG activation as defined in Clause 5.29, the MAC entity shall:

[0190] 1> If the MAC reset is not due to the revocation of SCG activation:

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

[0192] 1> In the case of configuring side link 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 revoked and the SCG to be revoked is configured with a true 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 the MBS broadcast DRX timer;

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

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

[0199] 1> Set the NDI of all HARQ process IDs to the value 0 to monitor the PDCCH in sidelink resource allocation mode 1; Specification 14 / 94 pages 17 CN 120935649 A

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

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

[0202] 1> Clear Msg3 buffer;

[0203] 1> Clear MSGA buffer;

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

[0205] 1> Cancel (if present) triggered buffer status report procedure;

[0206] 1> Cancel (if present) triggered power margin report procedure;

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

[0208] 1> Cancel (if present) triggered BFR;

[0209] 1> Cancel (if present) triggered side link buffer status report procedure;

[0210] 1> Cancel (if present) triggered preemptive buffer status report procedure;

[0211] 1> Cancel (if present) triggered timing advance report procedure;

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

[0213] 1> Cancel (if present) the triggered configured uplink grant acknowledgment;

[0214] 1> Cancel (if present) the triggered configured sidelink grant acknowledgment;

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

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

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

[0218] 1> Clear the soft buffer for all DL HARQ processes except for DL ​​HARQ processes currently used for MBS broadcasting;

[0219] 1> For each DL HARQ process except for DL ​​HARQ processes currently used for MBS broadcasting, treat the next received transmission for TB as the first transmission;

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

[0221] 1> If the upper layer instructs the 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 the SCG revocation activation:

[0223] 2> Reset all BFI_COUNTER;

[0224] 1> Reset all LBT_COUNTER.

[0225] …

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

[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 UE-specific PDSCH MAC CE TCI state activation / deactivation as described in Clause 6.1.3.14. The network can activate and deactivate the configured TCI state of the serving cell's PDSCH by sending enhanced TCI state activation / deactivation for the UE-specific PDSCH MAC CE as described in Clause 6.1.3.24, as specified in TS 38.212[9]. The configured TCI state of the PDSCH is initially deactivated when (re)configured by the upper layer and after a reconfiguration with synchronization.

[0228] The MAC entity will:

[0229] 1> In the case that the MAC entity receives TCI state activation / deactivation for the UE-specific PDSCH MAC CE on the serving cell:

[0230] 2> Indicate information about the activation / deactivation of the TCI state of the UE-specific PDSCH MAC CE to the lower layer. Specification 15 / 94 pages 18 CN 120935649 A

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

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

[0233] 5.18.5 Indication for TCI State of UE-Specific PDCCH

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

[0235] The MAC entity will:

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

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

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

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

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

[0241] The network can activate and deactivate the spatial relationships 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 relationships 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 relationships of activated PUCCH resources are deactivated first during (re)configuration by the upper layer and after synchronization following reconfiguration. The network can also activate and deactivate the serving cell's PUCCH resources by sending the PUCCH spatial relationship activation / deactivation MAC CE for multiple TRP PUCCH repeating MAC CEs described in Section 6.1.3.45.Two spatial relationships of a source or PUCCH resource group.

[0242] The MAC entity will:

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

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

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

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

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

[0248] 2> Indicate information about the PUCCH spatial relationship activation / deactivation for multiple TRP PUCCH repeating MAC CEs to the lower layer.

[0249] …

[0250] 5.18.23 Unified TCI State 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 upon (re)configuration by the upper layer and after a reconfiguration with synchronization. Instruction manual 16 / 94 pages 19 CN 120935649 A

[0252] The MAC entity will:

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

[0254] 2> Indicate information about the unified TCI state activation / deactivation MAC CE to the lower layer.

[0255] 6.1.3.23 BFR MAC CE

[0256] The MAC CE for BFR consists of:

[0257] - BFR MAC CE; or

[0258] - Truncated BFR MAC CE.

[0259] The BFR MAC CE and the 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] BFR MAC CE and truncated BFR MAC CEThe CE has a variable size. It contains a bitmap and includes 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 a 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 a truncated BFR MAC CE, a single octet bitmap is used in the following cases, and in other cases, four octets are used:

[0262] - A beam fault is detected and the highest ServCellIndex of the SCell of the MAC entity that has completed the evaluation of the candidate beams as required by TS 38.133

[11] is less than 8; or

[0263] - A beam fault is detected in the SpCell (as specified in section 5.17), the SpCell will be indicated in the truncated BFR MAC CE, and the UL-SCH resources available for transmission cannot accommodate a truncated BFR MAC CE with four octets bitmaps plus their subheaders as the LCP result.

[0264] The fields in the BFR MAC CE are defined as follows:

[0265] - SP: This field indicates beam fault detection of the SpCell of this MAC entity (as specified in clause 5.17). The SP field is set to 1 only when the BFR MAC CE or the 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] -Ci(BFR MAC CE): This field indicates beam fault detection (as specified in Clause 5.17) and the presence of an octet containing the AC field for the SCell having ServCellIndex i as specified in TS 38.331[5]. A Ci field set to 1 indicates that a beam fault has been detected, the evaluation of the candidate beams required as specified in TS 38.133

[11] has been completed, and an octet containing the AC field exists for the SCell having ServCellIndex i. A Ci field set to 0 indicates that no beam fault was detected, or that 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 eight-bit field containing the AC field for the SCell with ServCellIndex i.Bit groups. There are octets containing the AC field in ascending order based on ServCellIndex;

[0267] - Ci (truncated BFR MAC CE): This field indicates beam fault detection for a SCell having ServCellIndex i as specified in TS 38.331[5] (as specified in Clause 5.17). A Ci field set to 1 indicates that a beam fault has been detected, the evaluation of candidate beams as required by TS 38.133

[11] has been completed, and an octet containing the AC field may exist for the SCell having ServCellIndex i. A Ci field set to 0 indicates that a beam fault has not been detected, or a beam fault has been detected but the evaluation of candidate beams as required by TS 38.133

[11] has not been completed, and an octet containing the AC field does not exist for the SCell having ServCellIndex i. According to the basic specification, page 17 / 94, 20 CN 120935649 A, the ascending order of ServCellIndex contains octets containing the AC field (if present). Maximize the number of 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 RSID field in this octet. If at least one of the SSBs in candidateBeamRSSCellList with an SS-RSRP higher than rsrp-ThresholdBFR or the CSI-RS in candidateBeamRSSCellList with a CSI-RSRP higher than rsrp-ThresholdBFR is available, then the AC field is set to 1; otherwise, it is set to 0. If the AC field is set to 1, then the candidate RS ID field exists. If the AC field is set to 0, then 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. (SSB or CSI-RS index)This is the index of the entry in the candidateBeamRSSCellList corresponding to the 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. The length of this field is 6 bits.

[0271] Figure 5 is a reproduction of Figure 6.1.3.23-1 in 3GPP 38.321v17.4.0: BFR and a truncated BFR MAC CE with one octet Ci field.

[0272] Figure 6 is a reproduction of Figure 6.1.3.23-2 in 3GPP 38.321v17.4.0: BFR and a truncated BFR MAC CE with four octets Ci fields.

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

[0274] 5.5.4 Measurement Report Triggering

[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 in 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 serving cell is considered applicable;

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

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

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

[0287] 5> Only the serving L2 U2N relay UE is considered applicable;

[0288] 4> If the corresponding reportConfig contains a reportType that is set to periodic; 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 in question is included in allowedCellsToAddModList defined for this meas ID in VarMeasConfig, any neighboring cells detected based on the parameters in the associated measObjectNR are considered applicable;

[0292] 5> Otherwise:

[0293] 6> When the cell in question is not included in excludedCellsToAddModList defined for this meas ID in VarMeasConfig, any neighboring cells detected based on the parameters in the associated measObjectNR are considered applicable;

[0294] …

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

[0296] 3> Cells detected on the associated measObject are considered applicable if they have a physical cell identity that matches the value of cellForWhichToReportCGI in the corresponding reportConfig contained in 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> NR PSCells are considered applicable;

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

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

[0303] 6> Any NR neighboring cells detected on the associated measObjectNR that have a physical cell identity contained in cellsForWhichToReportSFTD are considered applicable;

[0304] 5> Otherwise:

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

[0306] …

[0307] 2> 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 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> Contains a measurement report entry in VarMeasReportList for this measId;

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

[0310] 3> Contains the involved cells in cellsTriggeredList defined for this measId in VarMeasReportList;

[0311] …

[0312] 3> Initiate a 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 in 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 in VarMeasConfig (subsequent cell triggering event): Specification 19 / 94 Page 22 CN 120935649 A

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

[0315] 3> Include the involved cells in cellsTriggeredList defined for this measId in VarMeasReportList;

[0316] …

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

[0318] …

[0319] 2> Otherwise, if reportType is set to eventTriggered and if it applies to this event, that is, the entry condition of the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig is for one or moreThe applicable transport resource pool satisfies all measurements performed during the timeToTrigger period defined for this event in VarMeasConfig, and VarMeasReportList does not contain a measurement report entry for this measId (first transport resource pool triggered event):

[0320] 3> Includes a measurement report entry in VarMeasReportList for this measId;

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

[0322] 3> Includes the involved transport resource pool in poolsTriggeredList defined in VarMeasReportList for this measId;

[0323] 3> Initiates a 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 in VarMeasConfig is met for one or more applicable transport resource pools not included in poolsTriggeredList for all measurements performed during the timeToTrigger period defined for this event in VarMeasConfig (subsequent transport resource pool triggering event):

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

[0326] 3> Include the involved transport resource pool in poolsTriggeredList defined in VarMeasReportList for this measId;

[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 exit conditions applicable to this event for one or more applicable transport resource pools included in poolsTriggeredList defined for this measId within VarMeasReportList:

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

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

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

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

[0333] …

[0334] 2> If reportType is set to periodic and (first) measurement results are available: Specification 20 / 94 page 23 CN 120935649 A

[0335] 3> Include the measurement report entry in VarMeasReportList for this measId;

[0336] 3> Set 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 an RSSI sample value after the first L1 measurement duration, immediately initiate a 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 a 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 according to 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 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, initiate a measurement reporting procedure 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 L2After the U2N remote UE), initiate a measurement reporting procedure as specified in 5.5.5;

[0347] …

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

[0349] 3> Include a measurement report entry in the VarMeasReportList for this measId;

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

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

[0352] 2> After the periodic reporting timer 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 it contains drx-SFTD-NeighMeas:

[0357] 5> If the amount to be reported becomes available for each of the requested PCell and NR cell pairs:

[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, immediately initiate the measurement reporting procedure after the amount to be reported becomes available for each of the requested PCell and NR cell pairs or after the maximum measurement reporting delay specified in TS 38.133

[14] ;

[0362] …

[0363] 2> If reportType is set to reportCGI: Specification 21 / 94 pages 24 CN 120935649 A

[0364] 3> If the UE acquires 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> Include the measurement report entry in VarMeasReportList for this measId;

[0368] 4> Set 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 T321 for this measId expires:

[0371] 3>If there is a measurement report entry within the VarMeasReportList for this measId;

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

[0373] 3>Initiate the measurement report procedure specified in 5.5.5.

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

[0375] 3>Initiate the measurement report procedure specified in 5.5.5.

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

[0377] The UE shall:

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

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

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

[0381] Inequality A

[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 defined in reportConfigNR for this event).

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

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

[0406] Hys is expressed in dB.

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

[0408] 5.5.4.4 Event A3 (Neighbor becomes offset better than SpCell)

[0409] The UE shall:

[0410] 1> Consider it to meet the entry condition of this event when the condition A3-1 specified below is met;

[0411] 1> Consider it to meet the exit condition of this event when the condition A3-2 specified below is met;

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

[0413] Note 1: The cell triggering the event has the reference signal indicated in the measObjectNR associated with this event, and the measObjectNR can be different from the NR SpCell measObjectNR.

[0414] Inequality A3-1 (Entry condition)

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

[0416] Inequality A3-2 (Exit 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 the neighboring cell without considering any offset.

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

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

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

[0423] Ofp is the measurement object specific offset of the SpCell (i.e., the offsetMO defined within the measObjectNR corresponding to the SpCell).

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

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

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

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

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

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

[0430] 5.5.4.5 Event A4 (Neighbor becomes better than threshold) Description of the specification Page 23 / 94 Page 26 CN 120935649 A

[0431] The UE shall:

[0432] 1> When the condition A4-1 specified below is satisfied, it is considered that the entry condition of this event is satisfied;

[0433] 1> When the condition A4-2 specified below is satisfied, it is considered that the exit condition of this event is satisfied.

[0434] Inequality A4-1 (Entry condition)

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

[0436] Inequality A4-2 (Exit condition)

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

[0438] The variable definitions in the formula are as follows:

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

[0440] Ofn is the measurement object specific offset of the neighboring cell (i.e., the offsetMO defined in measObjectNR corresponding to 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 not configured for the neighboring cell.

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

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

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

[0445] Ofn, Ocn, Hys are expressed in dB.

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

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

[0448] 5.5.4.6 Event A5 (the serving cell becomes worse than threshold1 and the neighbor becomes better than threshold2)

[0449] The UE shall:

[0450] 1> Consider that the entry condition for this event is met when the following specified condition A5-1 and condition A5-2 are met;

[0451] 1> Consider that the exit condition for this event is met when the following specified condition A5-3 or condition A5-4, that is, at least one of the two conditions, is met;

[0452] 1> Use the serving cell for Mp.

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

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

[0455] Mp + Hys < Thresh1

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

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

[0458] Inequality A5-3 (exit condition 1)

[0459] Mp - Hys > Thresh1

[0460] Inequality A5-4 (exit 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 the NR serving cell, without considering any offset.

[0464] Mn is the measurement result of the neighboring cell, without considering any offset. Description 24 / 94 Page 27 CN 120935649 A

[0465] Ofn is the measurement object specific offset of the neighboring cell (i.e., the offsetMO defined within the measObjectNR corresponding to 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 within the measObjectNR), and is set to zero when not configured for the neighboring cell.

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

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

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

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

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

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

[0473] Thresh2 is represented in the same unit as Mn.

[0474] …

[0475] -PDSCH-Config

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

[0477] PDSCH-Config information elements

[0478]

[0479] …

[0480] Specification 25 / 94 pages 28 CN 120935649 A

[0481] -ControlResourceSet

[0482] 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 excluding 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 included 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] Specification 26 / 94 pages 29 CN 120935649 A

[0486]

[0487] -BWP-UplinkDedicated

[0488] IE BWP-UplinkDedicated is used to configure dedicated (UE-specific) parameters of uplink BWP.

[0489] BWP-UplinkDedicated Information Element

[0490] Specification 27 / 94 pages 30 CN 120935649 A

[0491] Specification 28 / 94 pages 31 CN 120935649 A

[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] Specification 29 / 94 pages 32 CN 120935649 A

[0498]

[0499]

[0500] Specification 30 / 94 pages 33 CN 120935649 A

[0501]

[0502] -TCI-StateId

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

[0504] -TCI-UL-State IE TCI-UL-State indicates the TCI status information used for UL transmission. TCI-UL-State Information Element Specification 31 / 94 pages 34 CN 120935649 A

[0505]

[0506] Specification 32 / 94 pages 35 CN 120935649 A

[0507]

[0508] -TCI-UL-StateId

[0509] 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: Service becomes better than the absolute threshold;

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

[0516] Event A3: Neighbor becomes better than PCell / PSCell by one offset;

[0517] Event A4: Neighbor becomes better than the absolute threshold;

[0518] Event A5: PCell / PSCell becomes worse than absolute threshold1 and neighbor / Scell ​​becomes better than another absolute threshold2;

[0519] …

[0520] ReportConfigNR Information Element Specification 33 / 94 Page 36 CN 120935649 A

[0521] Specification 34 / 94 Page 37 CN 120935649 A

[0522] Specification 35 / 94 Page 38 CN 120935649 A

[0523] Specification 36 / 94 Page 39 CN 120935649 A

[0524] Specification 37 / 94 pages 40 CN 120935649 A

[0525] Specification 38 / 94 pages 41 CN 120935649 A

[0526] Specification 39 / 94 pages 42 CN 120935649 A

[0527]

[0528] DescriptionPage 43 of 40 / 94 CN 120935649 A

[0529]

[0530] …

[0531] -TimeToTrigger

[0532] IE TimeToTrigger specifies the range of values ​​for the trigger time parameter, which relates to the time for which a specific criterion of the event needs to be met in order to trigger the measurement report. The value ms0 corresponds to 0ms and applies as specified in 7.1.2, the 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, on this basis, the gNB changes the UE's serving cell by sending a cell handover command via MAC CE. The cell handover command instructs the gNB to provide the LTM candidate configuration to the UE via RRC signaling, which has been previously prepared. 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 current 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 cell handover is triggered.

[0538] …

[0539] LTM supports intra-gNB-DU and intra-gNB-CU gNB-DU mobility. LTM supports 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; Specification 41 / 94 pages 44 CN 120935649 A

[0541] - PCell and SCell changes in CA scenarios;

[0542] - PCell and MCG SCell changes in dual connectivity scenarios and PSCell and SCG SCell changes within the SN that do not involve the MN. LTM for simultaneous PCell and PSCell changes is 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.2 C-plane processing

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

[0546] The general procedure for LTM is shown in Figure 9.2.3.5.2-1 below. 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 via the air interface applies to SCG LTM. Further details of SCG LTM can be found in TS 37.340

[21] .

[0547] Figure 7 is a reproduction of the signaling procedure for LTM in Figure 9.2.3.5.2-1 of draft 38.300v 18.0.0.

[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. The gNB transmits an RRCReconfiguration message containing LTM candidate configurations to the UE.

[0551] 3. The UE stores the LTM candidate configuration and transmits 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 the UE-based TA measurement is configured, the UE obtains 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 by CFRA triggered by a PDCCH command from the source cell, after which the UE sends a preamble toward the indicated candidate cell. In order to minimize the data interruption of the source cell due to 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 measurement on the configured candidate cell and transmits the L1 measurement report to the gNB. As long as RRC reconfiguration (step 2) applies, L1 measurement should be performed.

[0555] 6. The gNB decides to perform a cell handover to the target cell and transmits a MAC CE that triggers the cell handover by including the candidate configuration index of the target cell. The UE switches 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 by sending an RRCReconfigurationComplete message to the target cell.Change procedure. If the UE has already executed 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 the UE determines that the network has successfully received its first UL data.

[0558] Steps 4 to 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 processing

[0560] After 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 through RRC signaling.

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

[0562] 3 Justification Specification 42 / 94 pages 45 CN 120935649 A

[0563] Layer 2 Mobility (LTM) is introduced in Rel-18 and provides improvements in handover delay and downtime compared to Layer 3 based mobility. However, LTM introduced in Rel-18 also has many 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 for measurement report triggering and reduce signaling overhead compared to periodic measurement reports. L1 measurements for LTM mobility do not support this event triggering.

[0566] …

[0567] 4 Objectives

[0568] 4.1 Objectives of SI or Core Part WI or Test Part WI

[0569] ○ …

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

[0571] ○ Measurement-related enhancements are applicable to MCG / SCG LTM within CU and MCG / SCG LTM between CUs

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

[0573] ■ RAN1 and RAN2 make independent progress on event-triggered measurement objectives for their respective MIMO and mobility enhancement WIs. Review the progress of RAN#105 to see if any modifications to the target are needed to avoid / manage any overlap in the work

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

[0575] In the Rel-18 3GPP specification (e.g., [7] 3GPP 38.321v18.1.0), the small size of LTM candidate cells is described.District-level energy saving and TCI status activation / deactivation:

[0576] 5.34 Cell-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 operation affects the UE's monitoring activities for PDCCH and configured downlink assignments in RRC_CONNECTED. For all active serving cells with cell DTX configured and activated, the MAC entity can monitor PDCCH and configured downlink assignments using the cell DTX operation 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 permission transmission activities in RRC_CONNECTED. For all active serving cells with cell DRX configured and activated, the MAC entity can use the cell DRX operation specified in Clause 5.34.3 to transmit configured uplink-permitted transmission and scheduling requests.

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

[0581] -cellDTXDRXconfigType: Defines whether only cell DTX, only cell DRX, or both are configured;

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

[0583] -celldtxdrx-StartOffset: Defines the subframe at which the cell DTX / DRX cycle begins;

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

[0585] -celldtxdrx-Cycle: The cell DTX / DRX cycle period;

[0586] -cellDTXDRXactivationStatus: The initial activation status of cell DTX and cell DRX operations. Instruction manual, pages 43 / 94, 46 CN 120935649 A

[0587] 5.34.2 Discontinuous cell transmission

[0588] If cellDTXDRXconfigType is set to dtx or dtxdrx, then cell DTX is configured. For each serving cell, cell DTX activation is activated and deactivated by 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] - Configure C from the upper layerell DTXDRX-Config: 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 cell reception

[0595] If cellDTXDRXconfigType is set to drx or dtxdrx, then cell DTX is configured. For each serving cell, the activation and deactivation of cell DRX operations are performed as follows:

[0596] - Receive a cell DRX indication from the lower layer indicating activation or deactivation of cell DRX operations, as specified in TS 38.213 [6];

[0597] - Configure Cell DTXDRX-Config from the upper layer: If cell DRX is configured and cellDTXDRXactivationStatus is set to active, the cell DRX operation is activated immediately after cell DRX configuration; if cell DRX is configured and cellDTXDRXactivationStatus is set to deactivate, the activation of cell DRX operations is deactivated immediately after cell DRX configuration; if CellDTXDRX-Config is released, the activation of cell DRX operations 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 status of LTM candidate cells configured in CandidateTCI-State and CandidateTCI-UL-State by sending the Candidate Cell TCI Status Activation / Deactivation MAC CE described in Clause 6.1.3.76. The network deactivates the TCI status of an LTM candidate cell by not including the corresponding TCI status ID field in the Candidate Cell TCI Status Activation / Deactivation MAC CE.

[0601] The MAC entity will:

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

[0603] 2> Indicate information about the candidate cell TCI state activation / deactivation MAC CE to the lower layer.

[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 has 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 the LTM cell handover, corresponding to ltm-CandidateId minus 1, as specified in TS 38.331[5]. The field is 3 bits long;

[0607] - Timing Advance 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 on page 44 / 94 of the specification, CN 120935649 A). 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 TA of the amount of timing adjustment that must be applied by the MAC entity in TS 38.213 [6], and the UE can skip the random access procedure 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 TCI-StateId in ltm-DL-OrJointTCI-StateToAddModList, as specified in TS 38.331[5]. If the value of unifiedTCI-StateType in the configuration indicated by the target configuration ID field is united, then this field is used for the united TCI state; otherwise, this field is used for the downlink TCI state. The field length is 7 bits;

[0609] - UL TCI Status ID: This field indicates and activates the uplink TCI status 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 Status ID is considered a reserved bit, and the remaining 6 bits...The bit represents 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 the contention-free random access resource field. If the value of this field is set to 1, the following fields are present: including the random access preamble index field, S / U field, SS / PBCH index field, PRACH mask index field, and repetition number field. If the value of this field is set to 0, the random access preamble index field, SS / PBCH index field, PRACH mask index field, and repetition number 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 the PRACH of the contention-free random access resource. If the value of this field is set to 1, SUL is used; otherwise, NUL is used. The field length is 1 bit;

[0612] - Random Access Preamble Index: This field indicates the random access preamble index for contention-free random access resources. 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 RACH timing for PRACH transmission of contention-free random access resources. The field length is 6 bits;

[0614] - PRACH Mask Index: This field indicates the RACH timing associated with the SS / PBCH indicated by the 'SS / PBCH Index' transmitted by PRACH of contention-free random access resources. 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 length is 4 bits.

[0615] Figure 8 is a reproduction of Figure 6.1.3.75-1 of 3GPP 38.321v18.1.0: LTM cell handover command MAC CE.

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

[0617] The candidate cell TCI state activation / deactivation MAC CE is identified by a MAC subheader having 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 MAC address.The identity of the LTM candidate cell for the CE application corresponds to ltm-CandidateId minus 1, as specified in TS 38.331[5]. The length of the field is 3 bits;

[0619] -Pi: This field indicates whether each TCI code point has multiple TCI states or a single TCI state. If the Pi field is set to 1, the i-th TCI code point contains both DL TCI state and UL TCI state. If the Pi field is set to 0, the i-th TCI code point contains only DL / joint TCI state or UL TCI state. 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 state ID in the same octet is used for joint / downlink or uplink TCI state. If this field is set to 1, the TCI state ID in the same octet is used for joint / downlink TCI state. If this field is set to 0, the TCI state ID in the same octet is used for the uplink TCI state;

[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 TS 38.331[5]. If D / U is set to 1, the 7-bit TCI state ID, i.e., TCI-StateId, as specified in TS 38.331[5] is used. If D / U is set to 0, the most significant bit of the TCI state ID is considered a reserved bit, 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 is a reproduction of Figure 6.1.3.76-1 of 3GPP 38.321v18.1.0: activation / deactivation of candidate cell TCI state activation MAC CE.

[0623] In Chairman's Note RAN1#116eom0 of [8], the following is provided:

[0624] Protocol

[0625] Regarding UE-initiated / event-driven beam reports, at least the following aspects should be included:

[0626] ● Detection of triggering events for UE beam reports

[0627] - UE monitors RS to assess whether beam report triggering conditions have been met

[0628] - Further study needed: triggering conditions for declaring beam report events

[0629] ● UE beam report transmission

[0630] - Signaling content in the beam report

[0631] - Select one or more of the following options (strive for one) as the signaling medium / container for beam report transmission

[0632] ●MAC-CE

[0633] ●UCI

[0634] ●Others are not excluded.

[0635] Regarding UE-initiated / event-driven beam reports, the following aspects may be included

[0636] ●UE request for UL resources for beam reports

[0637] ●UE notification of beam report transmission

[0638] ●gNB pre-configured resources

[0639] Protocol

[0640] Regarding UE-initiated / event-driven beam reports, regarding the detection of triggering events for beam reports, RAN1 further studies at least the following aspects: quality metrics, event definitions, and thresholds.

[0641] - Further study of triggering events, including the following examples 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 of L1-RSRP becomes better than the current beam by a certain 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] ●Others are not excluded.

[0647] Protocol specification 46 / 94 pages 49 CN 120935649 A

[0648] Regarding UE-initiated / event-driven beam reports, at least L1-RSRP is supported as a measurement quantity for intra-cell and inter-cell SSBs, and 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, regarding signaling content, at least DL RS resource indicator and L1-RSRP are supported.

[0652] In Chairman's Note RAN1#116bis eom0 [9], the following is provided:

[0653] Protocol

[0654] Regarding the beam report transmission procedure for UE-initiated / event-driven beam reports, the following modes are supported:

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

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

[0657] ●To be further investigated: request format, e.g., SR or new UCI type.

[0658] ●Step 2: The UE detects the DCI format to indicate resources for carrying beam reports on the second UL channel.

[0659] ●Step 3: The beam report is transmitted in the second UL channel.

[0660] ● Further research is needed: details regarding the second UL channel, such as whether the second UL channel is a 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 is introduced.

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

[0664] ● Step 1: The UE transmits a first PUCCH (one-bit / multi-bit) to notify the second UL channel carrying the beam report.

[0665] ● Further investigation needed: Notification format, e.g., SR or new UCI type.

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

[0667] ● Further investigation needed: Details regarding the second UL channel, e.g., 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 each step of all modes by receiving confirmation information? For the above procedure, cross-CC beam reporting is supported for both modes.

[0670] Protocol

[0671] Regarding UE-initiated / event-driven beam reporting, regarding the detection of triggering events for beam reporting, at least event 2 is supported: the quality of at least one new beam, such as L1-RSRP, becomes a threshold better than the current beam.

[0672] - At least L1-RSRP is supported as a quality metric for event 2.

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

[0674] ● Further investigation needed: Whether the network controls how L1-RSRP is used to determine triggering events - Regarding RS measurement for the new beam for event 2, select one or more of the following:

[0675] ● Option 3a (explicit): The RS for the new beam is explicitly configured by RRC (e.g., a conventional configuration that reuses RS measurement or in TCI-State) or MAC-CE. (Page 47 / 94, 50 CN 120935649 A) ​​

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

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

[0678] Protocol

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

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

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

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

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

[0684] ● Further investigation needed: Option 2c (Explicit): The RS used 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 are 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 among the best K>1 beams (in the configured beams used for measurement and reporting).

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

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

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

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

[0697] Protocol

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

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

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

[0701] ● Nmax is configured by gNB

[0702] ● Further investigation needed: Whether an indication of payload size should be provided additionally.

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

[0704] ● At least one of the N reported beams should satisfy the conditions of event 2

[0705] ● Nmax is configured by gNB

[0706] ● Further investigation needed: Should an indication of payload size be provided separately? Specification 48 / 94 pages 51 CN 120935649 A

[0707] ● Further investigation needed: Details on how the UE determines the value of N

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

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

[0710] ● Nmax is configured by gNB

[0711] ● Payload size does not change with N

[0712] ● Further investigation needed: If N is less than Nmax, zero padding can be provided.

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

[0714] ● The reported beams should satisfy the condition of event 2

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

[0716] ● At least one of the N reported beams should satisfy the condition of event 2

[0717] ● N is configured by gNB

[0718] - Other options are not excluded.

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

[0720] - Further investigation needed: When reporting the current beam, whether the current beam is counted in the N reported beams.

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

[0722] In

[10] 3GPP TS 38.214 V17.3.0 (2022-09), the following TCI state-related paragraph is quoted:

[0723] 5.1.5 Antenna Port Quasi-Co-location

[0724] The UE may be configured with a list of up to M TCI-State configurations within 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-location 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-location relationship is configured by 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-level parameter qcl-Type in QCL-Info and can take one of the following values:

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

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

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

[0728] -'Type D': {Spatial 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 to provide quasi-co-located reference signals for the DM-RS of PDSCH and DM-RS of PDCCH in CC, for CSI-RS, and, where applicable, to provide references for determining the UL TX spatial filter for PUSCH and PUCCH resources in CC based on dynamic grant and configuration grant, as well as SRS.

[0730] If the TCIState or UL-TCIState configuration does not exist in the BWP of the CC, then 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 frequency band, then the UE is not expected to be configured with TCI-State, SpatialRelationInfo or PUCCH-SpatialRelationInfo in the same CC, except for SpatialRelationInfoPos. The UE may assume that when the UE is configured with a 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 a dl-OrJoint-TCIStateList or UL-TCIState in any CC within the same frequency band in the CC list. (See manual page 49 / 94, 52 CN 120935649 A)

[0731] The UE receives an activation command, as described in Clause 6.1.3.14 of [10, TS 38.321] or 6.1.3.47 of [10, TS 38.321], for mapping up to 8 TCI states and / or TCI state pairs to code points for the DCI field 'Transmission Configuration Indication' for one or a set of CC / DL BWPs and (if applicable) for one or a set of CC / UL BWPs, one of whichA TCI state is used for a DL channel / signal and / or a TCI state is used for a UL channel / signal. When a set of TCI state IDs is activated for a set of CC / DL BWPs and, where applicable, a set of CC / UL BWPs, wherein the applicable list of CCs is determined by the CCs indicated in the activation command, 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, where 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 to which the TCI state applies.

[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 to 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 / no DL assignment, the UE may assume the following:

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

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

[0736] - RV = all '1'

[0737] - MCS = all '1'

[0738] - NDI = 0

[0739] - Set to all '0' for FDR A type 0, or all '1' for FDR A 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, and the CSI-RS applying 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 PUSCH and PUCCH based on dynamic and configured approval, and the SRS applying the indicated TCI state.

[0743] When the UE transmits a PUCCH or PUSCH with HARQ-ACK information corresponding to a DCI that corresponds to a bearer TCI state indication and does not have a DL assignment, or a PDSCH that corresponds to a DCI scheduled by a bearer TCI state indication, and if the indicated TCI state is different from the 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 for which beam indication is applied.

[0744] If the UE is configured with the higher layer parameter tci-PresentInDCI set to 'enabled' for scheduling PDSCH, 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 a TCI field of the size of the DCI field 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 for L1-RSRP and L1-SINR calculation

[0746] If the UE is configured with an NZP-CSI-RS-ResourceSet, which is configured with the higher-layer parameter repetition set to 'on', then the UE may assume that the NZP-CSI-RS-ResourceSet described in Clause 5.2.2.3.1 contains the following parameters:CSI-RS resources are transmitted with the same downlink spatial domain transmission filter, wherein 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 in the NZP-CSI-RS-ResourceSet are transmitted with the same downlink spatial domain transmission filter.

[0747] If the UE is configured with a CSI-ReportConfig where reportQuantity is set to 'cri-RSRP', 'cri-SINR', or 'none', and if the CSI-ResourceConfig (higher layer parameter resourcesForChannelMeasurement) 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 for all CSI-RS resources in the set, the UE can only configure the same number (1 or 2) ports with the higher layer parameter nrofPorts. 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 SS / PBCH blocks.

[0748] In

[11] 3GPP TS 38.213 V18.2.0 (2024-03), the following is provided:

[0749] 11.2A Cancellation Instruction

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

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

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

[0753] - Information payload size of DCI format 2_4 provided by dci-PayloadSize-ForCI

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

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

[0756] - NCI is the number of bits provided by ci-PayloadSize

[0757] - BCI is the number of PRBs provided by frequencyRegionforCI in timeFrequencyRegion

[0758] - TCI is the number of symbols, excluding symbols used to receive SS / PBCH blocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon, according to the number of symbols, specification page 51 / 94, 54 CN 120935649 A

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

[0760] - Otherwise, equal to the PDCCH monitoring periodicity.

[0761] - GCI is the number of partitions of TCI symbols provided by timeGranularityforCI in timeFrequencyRegion

[0762] The GCI set of bits from the MSB of NCI bits has a one-to-one mapping with the GCI symbol groups, where each of the first groups contains symbols and each of the remaining groups contains symbols. The UE determines the symbol duration of the SCS configuration of the active DL BWP for PDCCH detection in DCI format 2_4.

[0763] For a set of symbols, the NBI = NCI / GCI bits of the MSB from each bit set have a one-to-one mapping with the NBI PRB groups, where each of the first N groups contains NBI PRBs and each of the remaining N groups contains NBI PRBs. The offset RB is determined by the frequencyRegionforCI starting from the indicated offset RB and the length LRB as RIV according to [6, TS 38.214], and by the SCS configuration indication of the active DL BWP for the PDCCH used for DCI format 2_4 detection, which indicates the offs in the FrequencyInfoUL-SIB or FrequencyInfoUL of the carrier.et To Carrier, the UE determines the first PRB index as and determines the number of adjacent RBs as BCI = LRB.

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

[0765] For the serving cell, the UE determines the first symbol among the TCI symbols as the first symbol after T′proc,2 from which the UE detects the end of the PDCCH reception of DCI format 2_4, where T′proc,2 is obtained from Tproc,2 for PUSCH processing capability 2 [6, TS 38.214], assuming that the d offset is provided by delta_Offset, and μ is the minimum SCS configuration between the SCS configuration of the PDCCH and the minimum SCS configuration μUL provided in the scs-SpecificCarrierList of FrequencyInfoUL or FrequencyInfoUL-SIB. The UE does not intend to cancel the PUSCH transmission or SRS transmission preceding the corresponding symbol as Tproc,2, assuming that d2,1 = 0 after the last symbol of the PDCCH reception of DCI format 2_4 is detected.

[0766] When the serving cell detects that a UE of DCI format 2_4 has a PUSCH transmission with repetition type B (as determined in clauses 9 and 9.2.5 or clause 6.1 of [6, TS 38.214]), the PUSCH transmission or actual repetition of the PUSCH transmission [6, TS 38.214] is cancelled, or the SRS transmission is cancelled on the serving cell in the following cases respectively:

[0767] - The transmission is a PUSCH with priority 0, if the UE is provided with uplinkCancellationPriority,

[0768] - A set of symbols from TCI symbols has at least one bit value '1' in the corresponding set of NBI bits in DCI format 2_4, and contains symbols of either a PUSCH transmission (repetition) or an SRS transmission, and

[0769] - A group of PRBs from BCI have a corresponding bit value '1' in the bit set corresponding to the symbol group in DCI format 2_4, and include PRBs transmitted (repeated) or transmitted by SRS,

[0770] wherein the specification is on pages 52 / 94, CN 120935649 A

[0771] - Cancellation of a 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] - Cancellation of an SRS transmission includes only symbols from one or more sets of symbols with corresponding bit values ​​'1' in DCI format 2_4.

[0773] If the UE cancels a PUSCH transmission or SRS transmission based on an indication via DCI format 2_4, then the UE does not expect to be scheduled by the second DCI format to transmit PUSCH or SRS via symbols containing 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 Part Operation

[0775] …

[0776] A UE configured to operate in the bandwidth part (BWP) of the serving cell is configured by a higher layer of the serving cell. A set of up to four bandwidth parts (BWPs) are used by the UE (DL BWP set) in the DL bandwidth via parameter BWP-Downlink or via parameter initialDownlinkBWP having a set of parameters configured by BWP-DownlinkCommon and BWP-DownlinkDedicated, and a set of up to four BWPs are used by the UE (UL BWP set) in the UL bandwidth via parameter BWP-Uplink or via 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 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, then 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 start 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 ULBWP is provided to the UE via the initial Uplink BWP. If the UE is configured with a supplementary UL carrier...Then, an initial UL BWP can be provided to the UE via initialUplinkBWP on the supplementary UL carrier.

[0779] If the UE has a dedicated BWP configuration, then a first active DL BWP for reception can be provided to the UE via firstActiveUplinkBWP-Id, and a first active UL BWP for transmission on the carrier of the primary cell can 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, TS 38.211] or [6, TS 38.214]:

[0781] - SCS, provided by subcarrierSpacing

[0782] - Cyclic prefix, provided by cyclicPrefix

[0783] - The number of common RBs and adjacent RBs is provided by locationAndBandwidth indicating the start of the offset RB and the length LRB as RIV according to [6, TS 38.214], set and value 0. The carrier is provided by offsetToCarrier for subcarrierSpacing

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

[0785] - A set of BWP common parameters and a set of BWP specific parameters, provided by BWP-DownlinkCommon and BWP-DownlinkDedicated for DL Provided by BWP, or by BWP-UplinkCommon and BWP-UplinkDedicated for the specification page 53 / 94 56 CN 120935649 A UL BWP [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 the index provided by BWP-Id is associated with the UL BWP from the group of configured UL BWPs with the 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 in which the center frequency of the DL BWP is different 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 CORESET for each type of CSS set and USS, as described in clause 10.1. The UE is not expected to be configured without PCell in the active DL BWP.CSS set.

[0788] If controlResourceSetZero and searchSpaceZero are provided to the UE in PDCCH-Config SIB1 or PDCCH-Config Common, then the UE determines the CORESET of the search space set from controlResourcesetZero as described in Clause 13 and for Tables 13-0 to 13-10, and determines the corresponding PDCCH monitoring timing as described in Clause 13 and for 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, a resource set for PUCCH transmission is configured for the UE 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 portion 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 interpretation of the UL BWP or DL ​​BWP indicated by the bandwidth portion indicator, then the UE will zero-prepend the information field until its size is the corresponding size required for interpretation of the information field of the UL BWP or DL ​​BWP before interpreting the DCI format information field

[0796] - if the size of the information field is larger than the DCI format of the UL BWP or DL ​​BWP indicated by the bandwidth portion indicator.The size required for format interpretation, so before interpreting 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 information fields containing a certain number of blocks [5, TS 38.212], the above procedure is applied 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 a change in the active DL BWP or active UL BWP, wherein the corresponding time domain resource assignment field provides a value smaller than the specification page 54 / 94 of the specification for the UE to use for changes in the active DL BWP or UL BWP, respectively. CN 120935649 A The required delay for PDSCH reception or PUSCH transmission slot offset value [10, TS 38.133].

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

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

[0803] The UE expects 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 detects the DCI format from two PDCCH receptions in search space sets si and sj containing searchSpaceLinkingId with the same value, as described in Clause 10.1, the UE considers the PDCCH reception in which the UE detected the 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 defaultDownlinkBWP-Id. If the default DL BWP is not provided to the UE via defaultDownlinkBWP-Id,If the BWP is used, 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 the subframe of FR1 or the 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 [10, TS 38.133] required by the UE for the change of the active DL BWP or the change of the active UL BWP, the UE does not need 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 an active UL / DL BWP change 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 immediately following the subframe of FR1 or the half-frame of FR2 after the UE completes the active UL / DL BWP change for the cell or different cells within FR1 (or FR2).

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

[0809] In the New Radio (NR), the network can configure beam reports (e.g., periodic or semi-persistent beam reports) or activate or trigger aperiodic beam reports (e.g., channel state information (CSI) reports) for the user equipment (UE) to obtain or acquire channel state information or channel quality or beam quality for data / control transmission. Typically, beam reports can be CSI reports with an amount corresponding to the Reference Signal Received Power (RSRP). However, in the case of frequent reporting, the UE may experience significant transmission overhead. On the other hand, in the case of 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, the use of...UE-initiated / event-driven beam management reduces latency and / or overhead. A UE may initiate or trigger a beam report in response to a condition being met (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 a new / candidate beam is better than the current beam). Additionally, in Mobility Enhancement Phase 4, UE-initiated beam reports are introduced for candidate cells to enable faster L1 / L2 Triggered Mobility (LTM).

[0810] In the current NR, there are other beam management mechanisms and / or other reports and / or other procedures regarding beam changes and / or beam reports. For example, a UE may change its (activated) beam for a cell in response to receiving an Activated Transport Configuration Indication (TCI) state Media Access Control (MAC) element (CE) associated with or indicating a cell (or the bandwidth portion (BWP) of the cell). 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] An example of this problem is illustrated in Figure 10A. At time t1, for example, due to a degradation in the beam quality 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 with) 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 a beam change for the BWP or for the cell (e.g., TCI state reconfiguration, activation / deactivation via MAC CE, etc.). At time t3, the UE transmits a beam report to the network. Since the beam may be changed by the network in t2, the report in t3 may not be up-to-date or may cause confusion for the network.

[0812] Another example is shown in Figure 10B. The UE may determine or discover an event that is met at t1 to trigger a report for the cell (e.g., the event may be a threshold that the quality of the new beam is better than the current beam of the cell). The UE may maintain or monitor the event for a period of time with a value timeToTrigger(ttt), where the UE may 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 may be a beam activation / deactivation of MAC CE.CE. 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] Regarding the present invention, a method for handling UE-initiated beam reports that overlap with other UE procedures or interactions between UE-initiated beam reports and other UE procedures is disclosed.

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

[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 secondary cell (SCell) when the SCell is deactivated, (triggered report,) TTT.

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

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

[0823] --Events of the SCell when the timing advance (TA) timer is associated with a cell whose report transmission has expired, (triggering the report in the specification, page 56 / 94, 59 CN 120935649 A,) TTT.

[0824] --Events of the cell when beam fault recovery (BFR) is in progress, (triggered report,) TTT.

[0825] --- Events of the cell when the BFR of another cell used for reporting transmission is in progress, (triggered report,) TTT.

[0826] --- Events of the cell when the current beam of the cell changes, (triggered report,) TTT.

[0827] --- LTM:

[0828] --- Events of the candidate cell when the TCI state of the candidate cell is deactivated, (triggered report,) TTT.

[0829] --- Events of the candidate cell when the activated TCI state of the candidate cell changes, such as all deactivated, some deactivated, from the first group to the second group, or a new activated TCI state, (triggered report,) TTT.

[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 the LTM command MAC CE for switching to another candidate cell is received.Events of candidate cells during CE, (triggered reports,) TTT.

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

[0833] --- Events of candidate cells during CE, (triggered reports,) TTT.

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

[0835] A beam report initiated by the UE can be associated with or triggered for a cell. 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 can perform one or more actions in response to a beam report initiated by the UE. 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 without responding 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 without responding 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 report initiated by the UE 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 second procedure in the one or more procedures for a UE-initiated beam report, and may perform another portion of the one or more actions in response to a report initiated by the UE without responding to the second procedure.

[0838] The UE may 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 may 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 may not perform the action in response to the first procedure.Specification page 57 / 94 60 CN 120935649 A

[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 the procedure for 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 may determine, at least based on the state of one or more procedures of the UE, whether to cancel a UE-initiated beam report. When or if (at least) there are one or more (in progress) procedures of the UE, the UE may cancel the UE-initiated beam report. When or if (at least) there are no one or more (in progress) procedures of the UE, the UE may not cancel the UE-initiated beam report. Additionally and / or alternatively, in some embodiments, when or if (at least) there is a (triggered or in progress) UE-initiated beam report, the UE may cancel or stop (parts) of the one or more procedures.

[0841] The UE may determine whether to perform an action in response to a UE-initiated (UEI) beam report based at least on the type of the procedure. An example is shown in Figure 11. For a UE-initiated beam report, 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 and 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 an event associated with the UEI beam report. Another example is shown in Figure 12. For a UE-initiated beam report associated with event 1, the UE may perform action 1 in response to procedures 1 and 2. The UE does not perform action 1 in response to procedure 3 for a UE-initiated beam report associated with event 1. 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 perform action 1 in response to procedures 2 and 3 without performing action 1 for a beam report initiated by a UE associated with event 1.

[0843] Another example is shown in FIG13A. The UE performs actions 1 and 2 in response to a beam report initiated by a UE associated with event 1 in response to procedure 1, and the UE performs action 1 but does not perform action 2 in response to a beam report initiated by a UE associated with event 2 in response to procedure 1.

[0844] List of actions

[0845] The one or more actions for 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 for a UE-initiated beam report may (or may not) include / include resuming (paused) UE-initiated beam reports.

[0847] The one or more actions for a UE-initiated beam report may (or may not) include / include pausing events associated with (in-process) UE-initiated beam reports. To pause an event, the UE may stop performing measurements associated with the event and / or stop / deactivate triggering beam reports associated with the event and / or stop / deactivate triggering beam reports associated with measurement objects (e.g., cell-associated) related to the UE-initiated beam report.

[0848] The one or more actions for a UE-initiated beam report may (or may not) include / include resuming (paused) UE-initiated beam reports. To recover from an event, the UE may begin performing measurements associated with the event and / or enable triggering of 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 UE-initiated beam report may (or may not) contain / include discarding or clearing or deconfiguring or releasing the (configured) event of the UE-initiated beam report. Specification 58 / 94 pages 61 CN 120935649 A

[0850] The one or more actions for a UE-initiated beam report may (or may not) contain / include canceling or clearing (one or all) triggers associated with the UE-initiated beam report.

[0851] The one or more actions for a UE-initiated beam report may (or may not) contain / include continuing (in progress) the UE-initiated beam report.

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

[0853] The one or more actions for 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 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).

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

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

[0856] The one or more actions for a UE-initiated beam report may (or may not) include / include continuing to perform measurements during the ongoing timeToTrigger time period.

[0857] The one or more actions for a UE-initiated beam report may (or may not) include / include reinitializing or recounting the time for satisfying the event within the time period determined by the timeToTrigger for events associated with or related to the UE-initiated beam report or the cell.

[0858] List of Procedures

[0859] The one or more procedures may contain / include or correspond to a state change 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 state change of a UE-initiated report (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 associated with an event, and / or if a first specific procedure is not associated with the event, the one or more procedures do not contain / include a first specific procedure.

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

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

[0864] In one example, the event corresponds to the beam quality of the current beam associated with an RS on a first cell, and the beam quality of a candidate beam associated with one or more RSs on a second cell. The first cell may be related to the second cell. (See specification 59 / 94)Page 62 CN 120935649 A Same or different. If the first specific procedure does not change the state of the RS (e.g., deactivate the third cell or change the activity (DL) BWP associated with the third cell), then the one or more procedures do not contain / include the first specific procedure. If the second specific procedure changes the state of the RS (e.g., deactivate the first cell or the second cell, or change the activity (DL) BWP associated with the first cell or the 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 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 if the first specific procedure does not have an effect on or does not make a state change on a report initiated by a UE related to the event, then the one or more procedures do not contain / include the first specific procedure.

[0867] The one or more procedures are associated with a UE-initiated report related to an event, and / or if a second specific procedure has an effect on or makes a state change on a UE-initiated report associated with 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 a candidate beam 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 the 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 a first specific procedure. If the second specific procedure makes a state change on the UE-initiated report (e.g., deactivating the third and / or fourth cell, or changing the activity (UL) BWP associated with the third and / or fifth cell), then the one or more procedures contain / include a second specific procedure.

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

[0870] The cell may be an SCell. A beam report initiated by the UE may be associated with a subcell.

[0871] The one or more procedures may include / include activation or deactivation of an SCG. A beam report initiated by the UE may be associated with a PSCell.

[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 undergoing a handover (e.g., switching 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 undergoing 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 associated with a Timing Advance Group (TAG). The 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. The TAG may be associated with the cell associated with the UE-initiated beam report.

[0875] The one or more procedures may (or may not) contain / 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 a UE-initiated beam report for that cell. The one or more procedures may contain / include a triggered and uncancelled BFR. The one or more procedures may contain / include a random access procedure initiated for beam fault recovery (PCell or SCell). The one or more procedures may contain / include triggering a scheduling request (SR) for beam fault recovery (SCell). The one or more procedures may contain / include a triggered and uncancelled SR for beam fault recovery. The one or more procedures may contain / include the assembly and / or transmission of a BFR MAC CE.

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

[0877] The one or more procedures may contain / include (associated with the cell associated with the beam report initiated by the UE).The beam-changing procedure may include / 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 a TCI state-activated MAC CE for Physical Downlink Shared Channel (PDSCH) and / or Physical Downlink Control Channel (PDCCH) and / or for PUCCH and / or for Physical Uplink Shared Channel (PUSCH). The TCI state-activated MAC CE may be used for DL ​​and / or UL beam changes.

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

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

[0881] Alternatively, in some embodiments, the one or more procedures may not include / 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 the candidate cell.

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

[0885] The one or more procedures may (or may not) include a beam report initiated or requested by the network. The beam report may be a (periodic or nonperiodic or semi-persistent) CSI report associated with the cell.

[0886] Procedures for LTM Candidates

[0887] The one or more procedures may (or may not) contain / include a handover or reconfiguration procedure with synchronization. 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 associated with the UE-initiated beam report or another cell).

[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 an LTM candidate 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) contain / include 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 of an LTM candidate configuration (e.g., an LTM candidate).

[0892] The one or more procedures may contain / include a change in the activated TCI state of the cell. The cell may be an LTM candidate cell associated with a beam report initiated by the UE. The one or more procedures may (or may not) contain / include a candidate cell TCI state activation / deactivation MAC CE that receives an indication ltm-CandidateId (e.g., an indication ltm-CandidateId or an indication ltm-CandidateId-1), wherein ltm-CandidateId is associated with the cell associated with the beam report initiated by the UE. 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 beam report initiated by the UE.

[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) on the cell where the UE transmits the report / measured cell

[0895] Additionally and / or alternatively, in some embodiments, the one or more procedures may contain / include cells that are not in the cell DRX activity period. A cell may be associated with a UE-initiated beam report. Alternatively, in some embodiments, a cell may be a cell on which the UE transmits a (UE-initiated) beam report associated with a UE-initiated beam report. A cell may not be in the cell DRX activity period during the time period or when the UE is configured or available to transmit a report. A cell may not be in the cell DRX activity period 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 based on different types of UE-initiated beam reports: for LTM (for candidate cells) or for the serving cell

[0897] The event may be associated with the serving cell. Additionally and / or alternatively, in some embodiments, the event may be associated with a candidate cell.

[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 a cell, at least based on the cell type or at least based on the type or purpose of the UE-initiated beam report.

[0899] A UE-initiated beam report associated with a serving cell may be used for MIMO (enhanced), (intra-cell and / or inter-cell) beam management.

[0900] A UE-initiated beam report associated with a candidate cell may be used for LTM.

[0901] For example, the UE may perform one or more actions in response to a UE-initiated beam report associated with a serving cell (e.g., a UE-initiated beam report initiated or triggered based on a comparison between the quality of the current beam in Area A and the candidate beam of the serving cell, as specified in the service cell specification (pages 62 / 94, CN 120935649 A). The UE may not (be permitted to) perform a portion of the one or more actions for a beam report initiated by the UE associated with the candidate cell (or LTM) in response to the one or more procedures (e.g., in response to a reconfiguration procedure with synchronization or in response to an LTM procedure).

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

[0903] In another instance, the UE may reset a counter associated with a beam report initiated by a first UE in the serving cell in response to a beam change of the current beam on the serving cell. The counter may be used to trigger a beam report initiated by the first UE in the serving cell. The UE may stop a first timer or treat the first timer as expired in response to a beam change of the current beam on the serving cell. The first timer may 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 may 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 may reset or restart a second timer associated with a beam report initiated by a second UE in the candidate cell without responding to a beam change of the current beam. The second timer may be a timeToTrigger(ttt) associated with a beam report initiated by a second UE in the candidate cell. ttt may be a time during which an event needs to be met to trigger a measurement report. An event can be that the quality of a candidate beam is higher than the quality of the current beam plus a threshold. A beam report initiated by a second UE can be associated with a candidate beam of the candidate cell and the current beam of the serving cell. A beam report initiated by a second UE can be an L1 measurement report triggered by an event associated with LTM.

[0905] An example is shown in Figure 13B. The UE can be configured with a UE-initiated beam report configuration 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 a counter 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 counter associated with the UE-initiated beam report 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 (part of) 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 perform one or more actions (part of) 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. Specification 63 / 94 pages 66 CN 120935649 A

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

[0909] For example, the UE may suspend events associated with a beam report initiated by the UE associated with the cell in response to the cell's reactivation. Additionally and / or alternatively, in some embodiments, the UE may resume events in response to cell activation. The UE can cancel or discard a triggered UE-initiated beam report (or report) in response to the cell's reactivation. 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 a UE-initiated report associated with the event (e.g., a cell including / containing a UE-initiated report associated with the (triggered and uncancelled) event).

[0910] Additionally and / or alternatively, in some embodiments, the UE can disable beam reports that trigger events associated with UE-initiated beam reports.

[0911] An example is shown in FIG14. At time t1, the UE measures cell A (on or associated with the RS) associated with a UE-initiated beam report. Preferably, in some embodiments, or additionally, in FIG14, at time t1, the UE triggers an event and determines or attempts to transmit a UE-initiated report on cell A. The UE can be configured with UE-initiated beam reports associated with cell A. The UE determines a threshold that the quality of the new beam associated with cell A is better than the current beam of cell A (e.g., satisfying the conditions of an 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). At time t2, the UE receives a revocation activation MAC CE indicating the revocation activation of cell A. In response to receiving the revocation activation of cell A, the UE may stop...Stop the accumulation of the timer / counter associated with the ttt of the beam report initiated by the UE. If (e.g., before t2) a trigger associated with the beam report initiated by the UE has been triggered, the UE may cancel the trigger in response to the deactivation of cell A. The UE may not consider the event (condition) to be met when cell A is deactivated. The UE may not trigger the beam report initiated by the UE when cell A is deactivated. At time t3, the UE receives the activation MAC CE for cell A. In response to cell activation, the UE may resume the beam report initiated by the UE. The UE may start or restart the 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, if or when the sum of the time periods [t1, t2] and [t3, t4] is equal to (or greater than) the timeToTrigger associated with the beam report initiated by the UE, the UE may trigger the beam report initiated by the UE at t4. Alternatively, in some embodiments, the UE may reset the value of the timer in response to the deactivation of cell A (timing t2).

[0912] For another example shown in FIG15, the UE may perform a measurement (RS) on cell B. Cell B may be a serving cell or a candidate cell. At timing 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 timing t1, the UE discovers or determines that a triggering event is met (e.g., the condition of an event is met). The UE may maintain a timer or counter (e.g., ttt) for determining whether the condition of an event is met within the timeToTrigger time period. At timing 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 may stop or restart the timer used for timeToTrigger. The UE may consider UE-initiated beam reports for cell B (generated before t2) as invalid. The UE can cancel a UE-initiated beam report triggered by cell B.

[0913] For another example shown in Figure 16, the UE can measure cell C (on or associated RS) and, at t1, determine that the quality of the activated TCI state A is less than a threshold of cell C (e.g., the condition of 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 an event is triggered (e.g., the condition of event () is met). The UE can trigger a UE-initiated beam report in cell C (if the condition of event () is met within the time period ttt). The UE can be configured to transmit the UE-initiated beam report of cell C on cell D. Cell D can be configured with cell-level specifications 64 / 94.Page 67 CN 120935649 A Yes, and is not in the cell DRX activity period during the time period (t3, t4). When cell D is not in the cell DRX activity period or in response to cell D not being in the cell DRX activity period, the UE can suspend (e.g., avoid) the triggering of UE-initiated beam reports. When cell D is not in the cell DRX activity period, the UE can not generate UE-initiated beam reports.

[0914] For another example, 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, the UE can cancel or stop (triggered or ongoing) UE-initiated beam reports in response to the triggering of BFR. The UE can cancel or stop (triggered or ongoing) UE-initiated beam reports of the first serving cell in response to the triggering of BFR of the first serving cell. The UE may cancel or stop beam reports initiated by the UE in the first serving cell without responding to the triggering of the BFR of the second serving cell.

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

[0917] For 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] For 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 (successful) completion of a beam fault recovery procedure associated with a triggered BFR of the first serving cell (BWP).

[0919] For another instance, the UE may cancel or stop a (triggered or ongoing) beam report initiated by the UE in response to a beam change procedure. The UE may cancel or stop a UE-initiated beam report in the first serving cell (BWP) in response to a beam change procedure of the first serving cell (BWP). The UE may cancel or stop a UE-initiated beam report in the first serving cell without responding to a beam change procedure of the second serving cell. The UE may cancel or stop a UE-initiated beam report in the first serving cell's first BWP without responding to a beam change procedure of the second BWP of the first serving cell.

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

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

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

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

[0924] For another instance, the UE may cancel or stop (triggered or ongoing) UE-initiated beam reports in response to a MAC reset. The UE may cancel or stop (triggered or ongoing) UE-initiated beam reports for the first serving cell in response to a MAC reset associated with the MAC entity of the first serving cell. The UE may not cancel or stop UE-initiated beam reports for the first serving cell in response to a MAC reset not associated with a serving cell.

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

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

[0927] For another instance, the UE may cancel or stop a UE-initiated beam report (triggered or in progress) in response to a SCell deactivation (triggered). The UE may cancel or stop a UE-initiated beam report for the first serving cell (triggered or in progress) 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 may not...The beam report initiated by the UE in the first serving cell is cancelled or stopped in response to the reactivation of the second serving cell.

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

[0929] In another instance, the UE may (re)start, reset, or stop the timer or counter associated with the beam report initiated by the UE in the cell (BWP) in response to the (triggering) of the cell's activation.

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

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

[0932] 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 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 report 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 not 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 (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] An example is shown in Figure 17. 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.(For example, TCI state activation / deactivation of MAC CE or TCI state RRC reconfiguration). In response to a beam change indication, the UE cancels or stops triggering a UE-initiated beam report.

[0936] Report not triggered based on a first procedure in progress

[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 at least the existence of one or more procedures in progress. If or when (at least) one or more procedures in progress are associated with the serving cell specification page 66 / 94 69 CN 120935649 A, the UE may not trigger, initiate, or execute a UE-initiated beam report for the serving cell.

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

[0939] For another instance, if or when (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 when (at least) no UE-triggered beam fault recovery procedure exists in 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 beam fault recovery (e.g., an SR triggered for 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 for beam fault recovery is not initiated, 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 change procedure (associated with the cell) exists, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell. Alternatively, in...In some embodiments, when or if (at least) an ongoing beam change procedure is not associated with a 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 (as associated with a 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 a 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 a 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 a cell, the UE may trigger, initiate, or execute a UE-initiated beam report for the cell.

[0944] Additionally and / or alternatively, in some embodiments, the UE may not trigger, initiate, or execute a UE-initiated beam report for the cell if or if (at least) an ongoing, synchronized reconfiguration procedure (associated with the cell) exists. Alternatively, in some embodiments, the UE may trigger, initiate, or execute a UE-initiated beam report for the cell if 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).

[0945] For another instance, the UE may not trigger a UE-initiated beam report for the first serving cell in response 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 not trigger a UE-initiated beam report for the first serving cell in response 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] An example is shown in Figure 18. 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. In the random access procedure, the UE performs a random access preamble transmission to the network. 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 beam report initiated by the UE (as associated with serving cell A) are met (e.g., the quality of the currently active beam is below a threshold and / or the candidate beam).(Beam quality is above a threshold). The UE may not initiate or trigger a UE-initiated beam report if the window / timer is running and / or if there is an ongoing random access procedure (for serving cell A beam failure recovery).

[0947] Parallel

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

[0949] Different handling based on different types of UE-initiated beam reports: for LTM (for candidate cells) or for serving cell

[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 procedures is in progress, the UE may initiate or execute a UE-initiated beam report for LTM or for a candidate cell. For another instance, when or if (at least) one of the 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 or initiate or execute a UE-initiated beam report for LTM or for L1 measurement reporting for a candidate cell. 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 or 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 or initiate or execute a UE-initiated beam report for LTM or for 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 or initiate or execute a UE-initiated beam report for the serving cell.

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

[0954] Prioritization between different types of UE-initiated beam reports

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

[0956] One type of UE-initiated beam report may be a report for a candidate cell or LTM. One type of UE-initiated beam report may 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, a 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, a UE may be configured with a priority associated with the prioritization of UE-initiated beam reports. For example, the network may configure a UE to prioritize beam reports initiated by a UE for the serving cell (over candidate cells), or the network may configure a UE to prioritize beam reports initiated by a UE for candidate cells (over serving cells). 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 with respect to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[0961] The UE-initiated beam report may be a CSI report. The UE-initiated beam report may be an event-driven beam report.

[0962] The UE-initiated beam report (procedure) for a cell may contain / include measuring the RS on the cell. The 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. The 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 UE-initiated beam report may be associated with a cell and / or a TCI state or beam associated with the cell. The measurement object may be configured with an event or associated with an event.

[0964] A UE-initiated beam report may be triggered or initiated in response to the satisfaction of one or more conditions.

[0965] The one or more conditions may include / include conditions associated with beam quality. For example, the 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, the 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 triggering event.

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

[0967] A UE-initiated beam report may include / include determining whether to trigger a report based on at least the measured beam quality.

[0968] The condition may be associated with a (configured) event.

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

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

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

[0972] The event could be associated with eventId in EventTriggerConfig.

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

[0974] Preferably, in some embodiments, the current beam corresponds to a Synchronization Signal Block (SSB), which is associated with 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 activated by TCI state (cancellation).

[0977] Preferably, in some embodiments, the indicated TCI state or activated TCI corresponds to DL or a 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 UE-initiated beam report may contain / include a trigger (of the report).

[0979] A UE-initiated beam report may contain / include a trigger and / or transmission of an SR.

[0980] A UE-initiated beam report may contain / include initiating a random access (RA) procedure.

[0981] A UE-initiated beam report may contain / include assembling a beam report (e.g., a beam report may be a MAC CE and / or RRC message and / or a PUCCH signal).

[0982] A UE-initiated beam report may contain / include transmitting the beam report to the network.

[0983] UE-initiated beam reports may be initiated and / or configured for a serving cell. Additionally and / or alternatively, in some embodiments, UE-initiated beam reports may be initiated and / or configured 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] A UE-initiated beam report may contain / include a trigger to cancel the beam report.

[0986] A UE-initiated beam report for a cell may contain / include the performance of measurements of the cell (BWP). A UE-initiated beam report may contain / include a trigger to cancel the 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] A UE may cancel a UE-initiated beam report in response to the initiation of one or more procedures.

[0988] A UE may 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 a 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 may cancel a UE-initiated beam report (associated with the cell) in response to transmitting a corresponding UE-initiated beam report (report information associated with the cell).

[0989] When canceling or stopping a UE-initiated beam report, the UE may stop the corresponding procedure (mentioned above) contained in the UE-initiated beam report.

[0990] When canceling or stopping a UE-initiated beam report, the UE may stop or restart a timer (e.g., a timeToTrigger-like timer) used to calculate or determine whether to trigger a UE-initiated beam report.

[0991] The cancellation or stopping of a UE-initiated beam report may include / include stopping the random access procedure. Additionally and / or alternatively, in some embodiments, the cancellation or stopping of a UE-initiated beam report may include / include stopping the beam report associated with the UE.One or more timers associated with the beam report (e.g., timeToTrigger for beam reporting or timers associated with the random access procedure and / or SR).

[0992] Cancellation or cessation of a UE-initiated beam report in a cell may contain / include (beam) information not included or reported in the UE-initiated beam report.

[0993] Cancellation or cessation of a UE-initiated beam report in a cell may contain / include (re)starting or resetting or stopping timers or counters associated with the UE-initiated beam report in the cell.

[0994] Timers or counters may be used or configured to trigger or disable UE-initiated beam reports in a cell. Timing Specification 70 / 94 pages 73 CN 120935649 A Timers or counters may be used to determine or detect whether an event is met within a time period. An event may be 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 may be considered met if, for example, the number of instances is greater than or equal to a threshold in the time period, or a UE-initiated beam report may be triggered. An instance 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 the new beam is greater than or equal to the quality of the current beam plus a threshold. A cell-level and / or new, candidate, or current beam maintenance counter can be used.

[0995] The UE can be configured with measurement objects associated with UE-initiated beam reports.

[0996] Measurement objects can contain / include serving cells and / or non-serving cells.

[0997] Measurement objects can be associated with an SSB and / or Channel State Information Reference Signal (CSI-RS) associated with the serving cell and / or non-serving cell.

[0998] To prioritize a UE-initiated beam report over one or more procedures, the UE stops the procedure and continues reporting.

[0999] To prioritize a first or more procedures over a UE-initiated beam report, the UE stops / cancels the report and continues the one or more procedures.

[1000] Reports and the first or more procedures can 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] Beams may 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 may be a serving cell, a candidate cell, and / or a neighboring cell.

[1004] A candidate cell may be an LTM candidate cell. A neighboring cell may be a cell 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. The 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 the UE-initiated report, MAC CE or UCI can be considered in general. MAC CE may have a delay due to the need for UL permission to transmit MAC CE. 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 the UE-initiated report (i.e., when an event condition is met). To address this issue, a pre-notification (PN) can be used to at least indicate the future use of one or more periodic UL resources associated with the 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 is a pending UE-initiated report, the UE determines whether to transmit the PN and / or set the PN to indicate the use of the periodic UL resource. In one instance, when a UE-initiated report is not triggered, or the UE does not use periodic UL resources to transmit the UE-initiated report, or there are no pending UE-initiated reports, the UE may skip transmitting the PN and / or the UE may not use periodic UL resources. 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 than used / unused needs to be carried, 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 used for UE-initiated reports, similar to CG-UCI on a PUSCH configured to grant uplink control information (CG-UCI) indicating future CG PUSCH resource use, this may not be useful because the triggering is more dynamic and not periodic. The PN (Passive Node) can be considered as a UL (Universal Utility) resource transmitted together with the same Transmission Time Interval (TTI) as per CN 120935649 A on pages 71 / 94 of the specification. 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 area to carry the PN (e.g., symbols 1 and / or 2 in the TTI (e.g., symbols 0 and 1 in a time slot)). The PN area can be shared by multiple UEs.Alternatively, in some embodiments, a PN area may be dedicated to the UE. Alternatively, in some embodiments, one or more PNs may be dedicated to the UE. Alternatively, in some embodiments, a second or more PNs may be shared by the UE. Typically, to achieve better resource efficiency in network nodes, time gaps or constraints are required between PNs and corresponding UL resources. Time gaps or constraints are used to ensure that network nodes have 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 downlink control information (DCI) using scheduling information (and / or using requests to resolve UEI reports). The UE transmits UEI reports on resources scheduled by the DCI.

[1009] In Mode B, a PN will be 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, PN resources and (pre)configured resources are configured in different instances / timings / TTIs. Alternatively, in some embodiments, PN resources and (pre)configured resources are configured in the same instance / timing / TTI. Once the conditions of an event 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 triggering of the event. The UEI report is pending before the UE receives a response from the network node. The UEI report is pending before the end of the event's delay limit.

[1011] For a pending UEI 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 UEI report). The DCI may indicate whether the request is for requesting a UEI report or a report triggered by the network node. A code point in the bit field may be used to indicate whether the request is for requesting a UEI report or a report triggered by the network node. The bit field can be a CSI request. Based on the code point of the bit field, the UE can determine whether the DCI request is for a network node-triggered report or a UEI report. If the UE has more than one pending UEI report, the UE determines one of the more than one UEI report once it receives the DCI. Alternatively, in some embodiments, the UE can multiplex the more than one UEI report (if resources scheduled by a DCI with an adapted code rate can accommodate the more than one UEI report).

[1012] For pending UIE reports, in Mode B, the UE will determine or select a valid PN resource and / or a valid (pre)configured resource for transmitting the UIE report. The UE will transmit the PN on the determined / selected PN resource and the pending UIE report on the determined / selected (pre)configured resource.

[1013] For Mode B, a general problem that may exist is that once the UE changes characteristics during the transmission of the PN resource and the (pre)configured resource for transmitting the UIE report, or the UE changes characteristics for the PN and the UIE report and the mapping between the PN and the (pre)configured resource disappears. Further design is needed to obtain a consistent understanding between the UE and the network node when the PN is transmitted.

[1014] Concept

[1015] This concept is to design the handling of PN and UIE reports when the UE detects one or more specific events. PN and UIE 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 change indicated or triggered by a network node or UE, Specification 72 / 94 pages 75 CN 120935649 A

[1018] - Active cell DTX / DRX with inactive time overlapping with PN or UEI reports,

[1019] - Receiving an update / change of an active beam,

[1020] - Applying an active beam,

[1021] - Receiving an update / change of an indicated beam,

[1022] - Applying an indicated beam,

[1023] - Transmitting a HARQ in response to receiving a DL signal for an update / change of an active beam,

[1024] - Transmitting a HARQ in response to receiving a DL signal for indicating an update / change of an indicated beam,

[1025] - Changing, activating or reconfiguring a candidate beam,

[1026] - The serving cell having configured resources for PN and / or resources for UEI reporting is deactivated,

[1027] - The resources for PN and / or resources for UEI reporting are reconfigured,

[1028] - The serving cell having configured resources for PN and / or resources for UEI reporting is switched from a first serving cell or changed to a second serving cell,

[1029] - A request for reporting from a network node (e.g., a beam report requested by a next-generation Node B (gNB)),

[1030] - Overlap with the timing for transmitting network-based reports, and / or

[1031] - UL cancellation based on a UE-specific signal (e.g., Dynamic Scheduling DCI) or a group common signal (e.g., DCI format 2_4).

[1032] Preferably, in some embodiments, one method is that the UE does not expect to receive the one or more specific events.Configuration associated with UEI reporting.

[1033] Preferably, in some embodiments, possible methods may be shown below (e.g., solutions primarily for the existence / occurrence / triggering of one or more specific events in FIG. 23 at or overlapping with said timing):

[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 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 overlaps with the timing or resources or reporting 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 an event or resource or report associated with one or more specific events, the UE does not determine 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 an event or resource or report associated with one or more specific events, the UE does not determine 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 resources or first resources for UEI reporting overlaps with an event or resource or report associated with one or more specific events, the UE determines the second PN resources and / or second resources for UEI reporting. Preferably, in some embodiments, the second PN resource and / or the second resource for UEI reporting does not overlap with the timing or 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 at or after the completion or cancellation of the one or more specific events.

[1039] Preferably, in some embodiments, possible methods may be shown below (e.g., solutions primarily for the existence / occurrence / triggering of one or more specific events in FIG. 23 at timing t2 or overlapping with the timing): Specification 73 / 94 pages 76 CN 120935649 A

[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 a PN for UEI reporting, and after the PN transmission (and before the transmission of the UEI report), 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 transmission (and before the transmission of the UEI report), the UE suspends the triggering of one or more specific events.

[1043] - The UE transmits a PN for UEI reporting, and after the PN transmission (and before the transmission of the UEI report), the PN transmission will delay the triggering of one or more specific events.

[1044] - The UE transmits a PN for UEI reporting, and after the PN transmission (and before the transmission of the UEI report), the UE prioritizes the transmission of the UEI report (over one or more specific events or reports associated with one or more specific events).

[1045] - The UE transmits a PN for UEI reporting, and after the PN transmission (and before the transmission of the UEI report), 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 transmission (but before the transmission of the UEI report), the UE keeps the UEI report pending.

[1047] - The UE transmits the PN for the UEI report, and after the PN transmission (but before the transmission of the UEI report), the UE determines the later valid PN resources and the valid resources for the UEI report.

[1048] - The UE transmits the PN for the UEI report, and after the PN transmission (but before the transmission of the UEI report), 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 transmission (but before the transmission of the UEI report), the UE does not cancel the transmission of the UEI report or keeps the transmission of the UEI report on the corresponding resources for the UEI report.

[1050] - The UE transmits a PN for a UEI report, and after the PN transmission (and before the transmission of the UEI report), 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 refers to the timing of the one or more specific events. Preferably, in some embodiments, the window refers to the timing of the end, completion, or cancellation of the one or more specific events.

[1051] - The UE transmits a PN for a UEI report, and after the PN transmission (and before the transmission of the UEI report), the UE anticipates receiving a DL signal from the network node requesting a pending UEI report (after the one or more specific events).

[1052] Preferably, in some embodiments, possible methods may be shown below (e.g., solutions primarily for the one or more specific events in FIG. 23 existing / occurring / triggered at or overlapping with said timing):

[1053] - After the UE transmits the UEI report (or after the UE transmits the UEI 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 from the timing of the UEI report transmission, and / or the duration is for monitoring network (NW) responses).

[1054] - After the UE transmits the UEI report (or after the UE transmits the UEI 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 UEI report (or after the UE transmits the UEI 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 a network node.

[1056] - After the UE transmits the UEI report (or after the UE transmits the UEI report with a time offset), the UE cancels the triggering of one of the one or more specific events. Instruction manual 74 / 94 pages 77 CN 120935649 A

[1057] - After the UE transmits the UEI report (or after the UE transmits the UEI report with a time offset), the UE suspends triggering one or more specific events (until a network node response is received from the UEI report).

[1058] - After the UE transmits the UEI report (or after the UE transmits the UEI 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 the UEI report (or after the UE transmits the UEI report with a time offset), the UE prioritizes the one or more specific events and / or de-prioritizes monitoring of NW responses.

[1060] Once the UE transmits the 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 the new current beam is associated with a UEI report or a 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, the signal is monitored in the BFR search space once the UE transmits a UEE report (adding 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 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 the currently indicated TCI state while a procedure other than the BFR procedure is in progress. Preferably, in some embodiments, the currently indicated TCI state signifies or corresponds to monitoring (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 unified 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 unified 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 requirement is 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 may transmit the PN via a first resource for the PN and transmit the UEI report via a first resource for the UEI report, wherein the first resource for the UEI report is associated with the PN or the first resource for the PN. After transmitting the UEI report, the UE may 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 may retransmit the UEI report via a second resource for the UEI report. Alternatively, the UE may trigger and transmit a second UEI report via the second resource for the UEI report (associated with a triggered and uncancelled event). The second resource for the UEI report may be associated with a second resource for the PN. The UE may not need to perform the transmission of the second PN via the second resource for the PN (in response to the network node response). Preferably, in some embodiments, the network node response may provideThis includes an interval of a certain number of nearest resources (associated with a pending event) for UEI. Preferably, in some embodiments, the network node response may provide a certain number of (later / future) nearest resources (associated with a pending event) for UEI. Preferably, in some embodiments, based on the indication of the network node response, the UE may trigger and transmit a second UEI report via a second resource for UEI reporting (associated with a triggered and uncancelled event). In other words, the UE may skip transmitting the second PN via the second resource for PN (in response to the network node response) as per page 78 of the specification (75 / 94, CN 120935649 A).

[1062] The second resource for UEI reporting may be the nearest resource for UEI reporting (configured for the UE) after the timing (plus a time offset) of receiving the network node response. The first resource for UEI and the second resource for UEI may be at the same frequency (e.g., completely overlapping in the frequency domain). The time domain allocation and / or frequency domain allocation of the second resource for UEI reporting may be indicated by the network node response.

[1063] The network node response may 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 per event, per BWP, per serving cell, per cell group, per PUCCH group, or per co-frequency band. Preferably, in some embodiments, for 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, due to a network node response...The blocking response has no effect. Preferably, in some embodiments, after the time interval, the UE will change 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 the retransmission of UEI reports. 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 PN and does not transmit or is unable to transmit the UEI report (due to the one or more specific events), the UE will monitor the DCI of the network node for scheduling resources for retransmission of UEI reports. 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 the (pre)configured resource. 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)configuration of resources or the next symbol or the next time slot in the specification for transmitting UEI reports, page 76 / 94, 79 CN 120935649 A.

[1068] Preferably, in some embodiments, once the UE receives the signal, the UE can determine that the network node has received the UEI 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 embodimentsIn this example, 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 network node responses. Preferably, in some embodiments, explicit signals will be CRC-scrambled via a 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, based on the information block associated with the resource used for (already) transmitted UEE reports, the UE may determine whether the network node has received the report and / or whether the UE needs to retransmit it. Alternatively, in some embodiments, once the UE transmits a UEE report, no network node response is required, and / or the UE does not retransmit the UEE report. Unless a resource is (pre-)configured or associated with a repetition count or aggregation factor, the UE does not retransmit the UEE report. Preferably, in some embodiments, the UE does not anticipate a repetition count for resources configured to be associated with the UEE 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 resources used to transmit the UEE report have no repetitions. Preferably, in some embodiments, the UE assumes that the resources used to transmit the UEE report have 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 to transmit the UEE report will be greater than 1. Preferably, in some embodiments, the UE does not anticipate that the repetition count associated with the resources used to transmit the UEE report will be greater than 1. Alternatively, in some embodiments, the UE can determine the number of resources used to transmit the UEE report based on the number of repetitions 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 (e.g., greater than 1) is applied or assumed, the UE can transmit more than one PN resource to notify the network node. Alternatively, in some embodiments, the UE may transmit a PN resource associated with a (pre)configured resource. Preferably, in some embodiments, the number of remaining resources, calculated by subtracting one from the repetition or the aggregation factor, follows the (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 (pre)configured resource. Preferably,In some embodiments, the number of remaining resources, determined by subtracting one from the number of repetitions or one from the aggregation factor, is based on future available (continuous) TTIs. Preferably, in some embodiments, the future available (continuous) TTIs are at least configured with flexible symbols and / or PRBs or ULs to determine the same format for 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 number of aggregation factors or repetitions. 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 UEI 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 UEI 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 the UEI 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 specified in the specification 77 / 94 of the PN transmission (80 CN 120935649 A). Preferably, in some embodiments, the time period ends when the UE transmits a UEI 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 value of the offset can 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, in response to an event...A UEI report is triggered. 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 within a single time instance. Preferably, in some embodiments, once the UE receives a BWP handover command during the PN and UEI report period (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 a bwp-InactivityTimer. Preferably, in some embodiments, when a PDCCH addressing a C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received at least in the BWP, the UE starts or restarts the timer (of the DL BWP). Preferably, in some embodiments, the UE starts or restarts a timer when at least a PDCCH addressing a downlink assignment or uplink grant C-RNTI or CS-RNTI to the scheduled BWP is received. 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 purposes). Preferably, in some embodiments, the UE may face the choice of whether to switch the active BWP change or transmit a PN and UEI report due to a UE-initiated UEE report. Preferably, in some embodiments, the UE can determine whether to change the active BWP due to timer expiration based at least on the existence of a triggered event (and not canceled). 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 and has not yet transmitted a UEI report. Preferably, in some embodiments, based on the determination of the existence of a triggered event (and not canceled), the UE can delay switching the active BWP (due to timer expiration). Preferably, in some embodiments, the UE switches the active BWP (due to timer expiration) based on the determination that no triggered event exists (or the triggered event has been cancelled). Preferably, in some embodiments, the UE may delay switching the active BWP (due to timer expiration) based on the determination that the UE has transmitted a PN but has not yet transmitted a UEI report. Preferably, in some embodiments, the UE does not delay switching the active BWP (due to timer expiration) based on the determination that the UE has not yet transmitted a PN or has transmitted a UEI report. Preferably, in some embodiments, based on the above, the UE delays switching the active BWP at least until the UE transmits a 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 or within mode B (transmitting UEI reports via (pre)configured resources). Preferably, in some embodiments, the UE may pause the timer or not switch active BWPs 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 UEI reports 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 UEI reports. 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 the UEI report) based on the configuration associated with the new active BWP. Preferably, in some embodiments, "effective" means that the resource does not overlap with the BWP handover time in the time domain (partial or complete specification 78 / 94 pages 81 CN 120935649 A). Preferably, in some embodiments, "effective" means the 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 the beginning of a time slot in which the UE can receive or transmit. Alternatively, in some embodiments, the UE cancels the 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 the 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 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 suspends 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 suspends 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 UEE 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 there is no valid PN resource 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, the UE can be configured with multiple resources for transmitting the UEI report once the UEI report is triggered (pending and not canceled). Preferably, in some embodiments, the multiple resources include the second resource and the third resource.

[1072] A 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 applied together 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 may be associated with one or more resources used for UEI reporting, wherein the one or more resources used for UEI reporting may be associated with the same or different BWPs. Preferably, in some embodiments, a resource used for UEI reporting may be associated with one or more PN resources in the same or different BWPs. Preferably, in some embodiments, at least when the UE is in a PN in a first BWPWhen a PN is transmitted in a resource, the resource in the second BWP associated with the PN resource used for UEI reporting 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 a PN resource in one or each of the more than one BWP. Preferably, in some embodiments, the UE is (pre-configured) with a resource for UEI reporting in one or each of the more than one BWP. Preferably, in some embodiments, when the UE is in an active BWP where the PN resource is located, the UE determines that the PN resource is activated. 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 the PN on a PN resource in an inactive BWP (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 a PN resource and / or a resource for UEI reporting. Preferably, in some embodiments, when the UE is in an active BWP where the resource for UEI reporting is located, the UE determines that the resource for UEI reporting is activated. Preferably, in some embodiments, the UE determines whether the resource for UEI reporting is activated based on whether the resource for UEI reporting is in the 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 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. This excludes the case where the new active BWP is a dormant BWP, where the UE transmits PN on the PN resources in the old active BWP and transmits UEI reports on resources for UEI reporting in the new active BWP. (After switching from the old active BWP to the new active BWP and) before transmitting UEI reports in the new active BWP, PN may not be transmitted in the new active BWP. Resources associated with UEI reports transmitted in the old active BWP and used for UEI reporting can be used during the time period for switching from the old active BWP to the new active BWP. Similarly, PN resources associated with UEI reports transmitted in the new active BWP can 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 PN resources in the old active BWP and resources used for UEI reporting in the new active BWP can be based on implicit determination or explicit signals. Preferably, in some embodiments, explicit signals can be RRC, MAC CE, and / or DCI. Preferably, in some embodiments...In this method, explicit signals can provide the association between a first resource (for PN) in a first BWP and a second resource (for UEI reporting) in a 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, implicit determination may be that the UE determines, based on the periodicity of the PN resource (e.g., t1, t1+n, t1+2n, t1+3n represent periodic PN resources in a BWP), that the PN resource is associated with one or more resources for UEI reporting within one or more 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 PN on the PN resource in the old active BWP and switches to the active BWP, the UE can transmit UEI reports on cross-BWP associated resources for UEI.

[1073] Preferably, in some embodiments, a first PN resource in a first BWP is associated with a 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 a 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 (without transmitting the PN in the second BWP) after a BWP handover. 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 in the second BWP used for UEI reporting after a BWP handover, and / or the UE transmits the PN on the third PN resource and / or transmits the UEI report on the third resource.

[1076] Preferably, in some embodiments, based on the 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, the UE can determine that the second resource can be associated with the first PN resource. Preferably, in some embodiments, if the second resource and the first resource are configured with the same (resource) identity (or associated to the first PN resource), the UE can transmit the UEI report on the second resource after BWP handover.

[1077] Preferably, in some embodiments, the UE does not transmit UEI reports 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 FIG24, the first PN resource and the first (pre)configured resource for UEI reporting are in the first BWP, and the second PN resource and the second (pre)configured resource for UEI reporting are in the 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, which in another example may be after the BWP handover time. In this example, the third PN resource and the third resource for UEI reporting are after the BWP handover time. The UE can transmit a PN and receive a BWP handover command on a first PN resource. In one instance, the UE can transmit a UEI report on a second resource used for UEI. Based on the association between the first PN resource in the first BWP and the second resource used for UEI reporting in the second BWP (if the second resource used for UEI reporting is later than the BWP handover time), the UE can transmit a UEI report on the second resource used 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, the same identity, or the same identifier. Preferably, in some embodiments, resource identities or identifiers in 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 for transmitting UEI reports. Preferably, in some embodiments, the association can be a time interval starting from the first PN resource or the periodicity of the PN resource in a BWP. Preferably, in some embodiments, the UE can be configured with the association shown in FIG25, i.e., each PN resource can correspond to more than one resource for UEI in one or more BWPs (cross-BWP indication for 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 (not shown in FIG24), once the UE transmits the PN on the first PN resource, the UE can directly transmit the UEI report on the second resource for UEI reporting. Preferably, in some embodiments, the UE does not need to...The PN is transmitted again on the second PN resource. Preferably, in some embodiments, the UE may transmit the UEI report on the second resource used for UEI reporting even if the second PN resource is unavailable for transmission. 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 with a configuration for Network Energy Saving (NES). The UE may be configured with cell DRX, which includes cell DRX modes for cell inactivity time and cell activity time. Preferably, in some embodiments, cell inactivity time means that the network node is in energy-saving operation. Preferably, in some embodiments, cell activity time means that the network node is in normal operation.

[1081] Preferably, in some embodiments, the cell DRX mode may be configured semi-statically. Preferably, in some embodiments, the cell DRX mode may 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 gain 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). Specification 81 / 94 pages 84 CN 120935649 A

[1082] In the first method, the UE expects resources for 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 during cell activity time and resources for UEI reporting 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), when a triggered event occurs, the UE determines the 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 activity. Preferably, in some embodiments, the UE determines whether the PN resources and the resources for UEI reporting are during cell activity based on semi-static configuration and / or dynamic signals. For simplicity, the PN resources and the resources for UEI reporting are configured on a single dynamic signal.Within an indicated time interval or period. 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 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 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 fact that the PN resource and the resource for UEI reporting are associated 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 fact that the PN resource and the resource for UEI reporting are associated 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 that the valid resource for transmitting the UEI report is based on the fact that both the resource for PN and the resource for UEI reporting are during cell DRX activity time. Preferably, in some embodiments, the cell DRX activity time may be based on one or more dynamic signals and / or semi-static cell DRX modes. Preferably, in some embodiments, when the UE determines a valid resource for transmitting a UEI report, the UE determines that at least the PN resource is within the cell DRX activity time.

[1083] In the second method, the UE does not expect to be configured with cell DRX and UEI reports simultaneously. Preferably, in some embodiments, when a cell is configured with cell DRX, the UE does not expect to be configured with UEI reports. Preferably, in some embodiments, when a cell is configured with cell DRX, the UE does not expect to be configured with mode B for UEI reports (e.g., mode A for UEI reports is allowed to be configured with cell DRX simultaneously).

[1084] For the example in FIG20, the UE determines the CSI reference resource (time domain) for UEI reports based on the resource associated with the PN. Preferably, the time domain location of the resource associated with the PN (associated with the first resource for transmitting UEI reports) is used to determine the CSI reference resource for UEI reports. 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 the transmission PN. Preferably, the timing associated with the transmission 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 the UEI report based on a virtual bundle 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 bundle of the first and second resources.

[1086] This determination is based at least on the case where the UE is configured or operating in mode B. Mode B indicates or corresponds to the UE being (pre-)configured with UL resources for transmitting the UEI report, and the UL resources are associated with a resource associated with the PN (or for transmitting the PN). Specification 82 / 94 pages 85 CN 120935649 A

[1087] When the UE is configured or operating in mode A, the UE determines the CSI reference resource (time domain) for the UEI report based on the resource associated with the UEI report. Mode A indicates or corresponds to the UE being scheduled to transmit the UEI report via UL resources. Mode A may not require resources for the PN. Once the UE is configured or operating in Mode-A, the UE will determine the CSI reference resource (time domain) for UEI reporting based on the resource associated with the PN (not the PN resource).

[1088] Preferably, for CSI reporting but not UEI reporting, 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 of the UE transmitting the CSI report. The UE is preferably associated with a UE configured in Mode-B.

[1089] Preferably, the binding of PN and UEI can be used to determine whether PUCCH cell handover (or PUCCH cell handover) is allowed. Preferably, during the binding of PN and UEI, when PN is associated with UEI reporting, the UE should not expect to hand over from the first cell transmitting PN to the second cell transmitting UEI reporting. Alternatively, the UE should not expect PN and UEI reporting to be transmitted in different cells containing PUCCH resources. In other words, the TTI between the TTI of PN and the TTI of UEI reporting can indicate PUCCH cell handover.

[1090] For the example in Figure 21, the UE can be (pre-)configured with three pairs or bundles of PN resources and resources for UEI reporting, labeled A, B, and C. When the UE triggers a UEI report, the UE will determine or select valid resources for transmitting the UEI report. The determination or selection can satisfy the condition that both resources (for PN and for UEI reporting) should be available during the cell 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 there is no resource for transmitting the UEI report in Figure 21.The next valid resource for reporting is 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 as bundle B and bundle C. An alternative is that UEI reporting and cell DRX cannot be configured simultaneously.

[1091] For another example, as shown in FIG22, the first dynamic signal (starting from the left of the figure) deactivates cell DRX, which means the active time within a time interval. The second dynamic signal activates cell DRX, which means that cell DRX active time and cell DRX inactivity time are based on the on-time duration timer associated with cell DRX configuration. In this example, if the first dynamic signal indicates that cell DRX has been activated, the dotted square can correspond to the original cell DRX active time. There are 3 instances of resource bundles for PN and UEI reporting, labeled A, B and C. Bundle A can correspond to resources for both PN and UEI reporting that are associated with a dynamic signal. Bundle B may correspond to at least one resource being active during cell DRX activity time, while another resource is not active during cell DRX activity time. Bundle C may correspond to at least one resource for PN and UEI reporting being active during cell DRX activity time, and another resource for PN and UEI reporting being inactive during cell DRX inactivity time. In this example, for bundle C, the PN resource is active during cell DRX activity time, while the resource for UEI reporting is inactive during cell DRX inactivity time. Preferably, in some embodiments, cell (DRX) activity time corresponds to the on-time duration timer being running. Preferably, in some embodiments, the on-time duration timer is associated with cell DRX configuration. The start timing of the on-time duration timer may be associated with 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 an order between the PN resources and the resources used for UEI reporting, i.e., an earlier PN resource is associated with an earlier resource used for UEI reporting (simultaneous timing can be considered valid). Preferably, in some embodiments, disorder between the PN resources and the resources used for UEI reporting is not allowed. In this example, both bundle B and bundle C correspond to the PN resources and the resources used for UEI reporting being associated with different dynamic signals. In one instance, the UE does not expect to receive a configuration that results in bundle B or bundle C. Alternatively, in some embodiments, the UE expects both the PN resources and the resources used 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 UEVirtual resources can be configured, including cell (DRX) activity time assuming (always) cell DRX activation. The UE determines periodic PN resources and 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 time. Preferably, in some embodiments, the periodicity of the PN resources or the periodicity of the resources for UEI reporting is configured with a plurality of integer numbers of cell DRX or time intervals (cell DRX) cycles. Preferably, in some embodiments, the periodicity of the PN resources is limited to alignment with the periodicity of the time interval (e.g., the periodicity of dynamic signals used to activate / deactivate the cell DRX mechanism). Alternatively, in some embodiments, the UE can receive configurations for bundles B and C. The UE can determine the verification of bundles B and C upon an event triggered by the UE or upon a pending UEI report to be transmitted. By assuming no dynamic signal or indication of activation of the cell DRX mechanism is received, the UE determines bundle B as an invalid resource. By assuming no dynamic signal or indication of cell DRX activation is received, the UE determines bundle C as an invalid resource. Alternatively, in some embodiments, the UE determines bundle C as a valid resource by assuming no dynamic signal or indication of cell DRX activation is received. Since the resources for UEI reports for bundle C are initially configured during cell (DRX) activity time, the UE determines bundle C as a valid resource. Preferably, in some embodiments, if the first dynamic signal in FIG22 indicates that cell DRX activation has occurred, the PN resources in bundles B and C are invalid. Preferably, in some embodiments, based on the indication that the first dynamic signal indicates cell DRX activation (resulting in PN resources during inactive time), the UE determines 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 uncancelled) UEI reports, the UE can determine the valid bundle and / or valid PN resources and / or valid resources for UEI reporting.

[1092] Preferably, in some embodiments, the UE does not expect to receive both the configuration and the on-time duration timer for UEI reporting. 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 the PN via resources for the PN during cell DRX active time, the UE may transmit the UEI report via resources for the UEI report during cell DRX inactive time. Resources for the UEI report may be associated with either the PN transmitted by the UE or the resources for the PN. If both the resources for the PN and the resources for the UEI report associated with the resources for the PN are during cell DRX inactive time, the UE may not (be allowed) transmit the PN via the resources for the PN and / or transmit the UEI report via the resources for the UEI report. If both the resources for the PN and the resources for the UEI report associated with the resources for the PN are during cell DRX inactive time, the UE determines that the resources for the PN and the resources for the UEI report are not valid.

[1094] Alternatively, in some embodiments, the UE may transmit the PN via resources for the PN during cell DRX inactive time. In other words, the UE may transmit the PN via resources for the PN regardless of whether the resources for the PN are during cell DRX inactive time. Alternatively and / or additionally, the UE may transmit the UEI report via resources for the UEI report during cell DRX inactive time. In other words, the UE can transmit the UEI report via the resources used for UEI reporting, regardless of whether the resources used for UEI reporting are inactive during the cell DTX period.

[1095] After the UE transmits the UEI report, if the resources used for the network node response to the UEI report are inactive during the cell DTX period, the UE can (still) monitor or receive the network node response via the resources used for the network node response. In other words, the UE can monitor or receive the network node response via the resources used for the network node response, regardless of whether the resources used for the network node response are inactive during the cell DTX period. Alternatively, in some embodiments, the UE may not (be allowed) monitor or receive the network node response via the resources used for the network node response (during the cell DTX 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, when the UE faces some problems in transmitting pending UEI reports, the UE maintains the event that triggers the specification on pages 84 / 94 of CN 120935649 A. When the UE removes priority or postpones the transmission of the PN, the UE may retain the triggered event.

[1097] Preferably, in some embodiments, the UE cancels the triggered event when the UE transmits a corresponding UEI report or receives a response associated with the transmitted UEI report from a network node, or after a window begins from the time the UE transmits the corresponding UEI report.

[1098] The UE is configured with a unified TCI framework. The unified TCI framework may correspond to a joint TCI mode or a separate TCI mode.Joint TCI mode means or corresponds to DL and UL using the same TCI state. Separate TCI mode means or corresponds to DL and UL using different TCI states. Without loss of generality, as shown in Figure 23, 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 an activated TCI state, applies an activated TCI state, (updates) an indicated TCI state, applies an indicated TCI state, transmits a HARQ in response to receiving a DL signal for updating / changing an 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 a candidate TCI state is changed, activated, or reconfigured.

[1099] If before the UE transmits PN on the PN resource (or at a time offset before the UE transmits PN on the PN resource) (e.g., t1 in FIG23), the UE:

[1100] - receives a DL signal for (updating) activating / deactivating the TCI state,

[1101] - applies the activated TCI state,

[1102] - (updates) the indicated TCI state, applies the indicated TCI state,

[1103] - transmits a HARQ in response to receiving a DL signal for updating / changing the activated TCI state,

[1104] - transmits a HARQ in response to receiving a DL signal for indicating an update / change of the indicated TCI state, 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 a PN and / or UEI report for the triggered event.

[1107] If after the UE transmits PN on the PN resource (e.g., t2 in FIG23), the UE:

[1108] - receives a DL signal for (updating) activating / deactivating the TCI state,

[1109] - applies the activated TCI state,

[1110] - (updates) the indicated TCI state, applies the indicated TCI state,

[1111] - transmits a HARQ in response to receiving a DL signal for updating / changing the activated TCI state,

[1112] - transmits a HARQ in response to receiving a DL signal for indicating an update / change of the indicated TCI state, 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 a UEI report for the triggered event (or the UE avoids transmitting a 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 choose not to monitor or receive network node responses to UEI reports from network nodes. Alternatively, in certain...In this embodiment, the UE may ignore the network node response to the UEI report received from the network node. In other words, the UE may retransmit the UEI report without responding to the received network node response (e.g., indicating NACK or unsuccessful transmission / reception) or may transmit a new UEI report without responding to the 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 for indicating specific / default / empty information associated with the current beam. Preferably, in some embodiments, based on the one or more specific events associated with the candidate beam or the current beam, the UE may determine the specific / default / empty information to be reported 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 an 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 (current) serving cell. Preferably, in some embodiments, if the update of the new candidate beam is not associated with a (current) triggered event, 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 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 triggered event and the second triggered event 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 associated with the current beam in response to the one or more specific events.

[1119] For another instance, once the UE detects one or more specific events associated with both the first set of candidate beams and the second set of candidate beams (e.g., changing / updating one or more candidate beams that overlap with the first set of candidate beams and also overlap with the second set 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 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).

[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 (revoking) activation of PN resources and / or resources for UEI reporting, the UE cancels the triggered event (regardless of whether the UE transmits PN on the old PN resources). Alternatively, in some embodiments, the UE does not expect to receive PN resources and / or resources for UEI reporting between the timing of the old PN resources and the (corresponding) resources for UEI reporting. (See page 86 / 94 of the specification, 89 CN)120935649 A's (re)configuration and / or (revocation) activation.

[1122] The UE may 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 the first timing and resources for UEI reporting in timing b 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, the UE does not expect the PN resources in the first timing and the PN resources in the second timing to be transmitted on different carriers, even for different timings. 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 said 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 switching, the UE can determine whether to apply PUCCH carrier switching and / or whether a bundle of PN resources and resources for UEI reporting are valid. Preferably, in some embodiments, if the UE receives a signal indicating carrier switching (e.g., t1 in FIG23) before transmitting the PN, then when there is a switch between PN resources and resources for UEI reporting, the UE transmits the PN on the first cell and transmits the UEI report on the second cell. Alternatively, in some embodiments, the UE determines this bundle of PN resources based on the carrier switching information.The resources used for UEI reporting are not valid. Preferably, in some embodiments, if the UE receives a signal indicating carrier switching information after transmitting the PN (e.g., t2 in FIG23), then when there is a switch between the PN resource and the resource used for UEI reporting, the UE transmits the PN on the first cell and transmits 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 carrier switching information for the PN resource and the resource used for UEI reporting. In one instance, the signal may indicate a PUCCH carrier switch 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 may be configured with both a Mode B associated with a UEI report and a network node request report. Once a request is received from the network node before transmitting the PN on the PN resource (e.g., t1 in FIG. 23), the UE will cancel the transmission of the PN and UEI report 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 may determine whether to cancel the transmission of the PN and UEI report 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 may cancel the transmission of the PN and UEI report on the PN resource. If the request is not associated with any of 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 may base the transmission of PN and UEI reports on the relationship 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.The presence or absence of (temporal) overlap determines whether to cancel the transmission of PN and UEI reports on PN resources. Preferably, in some embodiments, the UE cancels UEI report and / or PN transmission when there is (temporal) overlap between the UL resource used to transmit the network node request report and the PN resource, or between the UL resource used to transmit the network node request report and the resource used to transmit the UEI report. Alternatively, in some embodiments, the UE does not expect to receive signals from UL resources scheduled to overlap with the PN resource in the temporal domain (e.g., symbol domain and / or time slot domain overlap). Preferably, in some embodiments, after PN is transmitted on the PN resource (e.g., t2 in FIG23), the UE prioritizes transmitting the network node request report when there is overlap between the UL resource used to transmit the network node request report and the resource used to transmit the UEI 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 resource used to transmit the UEI report. Preferably, in some embodiments, if a network node request report is associated with the current beam and / or the candidate beam, the UE may cancel the UEI report and / or the UE may cancel the triggered event. Alternatively, in some embodiments, the UE may multiplex the UCI between the network node request report and the UEI report. Preferably, in some embodiments, the UE may discard a portion of the UEI report. Preferably, in some embodiments, the UE may discard a portion of the network node request report. Preferably, in some embodiments, the UE may determine whether to discard the UEI report (or multiplex the UEI report into the network node request report) based on whether the PN is transmitted.

[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 or a UE-specific DCI or a MAC CE. Preferably, in some embodiments, the group common DCI corresponds to a DCI indicating a cancellation indication that includes the cancellation of (pre)configured resources for the UEI report. Preferably, in some embodiments, the UE-specific DCI corresponds to a DCI that schedules higher priority transmissions. Preferably, in some embodiments, before transmitting the PN, if the UE receives a DL signal indicating the cancellation of a resource used for transmitting the UEI report, the UE determines the resource used for transmitting the UEI report as invalid. Preferably, in some embodiments, before transmitting the PN, if either the resource used for transmitting the UEI report or the PN resource...If a DL signal indicates cancellation, the UE determines that the resource used to transmit the UEI report is invalid. Preferably, in some embodiments, if the UE receives a DL signal indicating cancellation of a resource used for the UEI report after transmitting the PN (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 cancellation of a resource used for the UEI report after transmitting the PN (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 to transmit 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 cancellation of the PN resource or the resource used to transmit 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 UEI reports or transmitting PN resources. Preferably, in some embodiments, the DL signal may provide a priority threshold. Specification 88 / 94 pages 91 CN 120935649 A

[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 (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 above and herein may be combined, in whole or in part, to form new concepts, instances,...

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 the counter associated with the 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. 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 the counter associated with the 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.

15. The user equipment according to claim 14, 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.

16. The user equipment according to claim 15, 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.

17. The user equipment according to claim 14, 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.

18. The user equipment according to claim 14, 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.

19. The user equipment according to claim 18, 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.

20. The user equipment according to claim 19, 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.

Images