Method and apparatus for user equipment initiated beam reporting in wireless communication system

Abstract

Methods, systems, and devices are provided for handling user equipment initiated beam reports in a wireless communication system, wherein the method of a user equipment comprises: triggering user equipment initiated beam reports associated with a plurality of candidate cells; and when the uplink grant is unable to accommodate all of the one or more information associated with the plurality of candidate cells for user equipment initiated beam reporting. It is determined whether to preferentially transmit information of a candidate cell of the plurality of candidate cells via an uplink grant based on at least a quality associated with the candidate cell.

Description

Cross - Reference to Related Applications

[0001] This application claims the priority and benefit of U.S. Provisional Patent Application No. 63 / 624,132, filed on January 23, 2024, which is incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure generally relates to wireless communication networks, and more particularly, to methods and apparatuses for handling user equipment (UE) - initiated beam reporting in a wireless communication system. Background Art

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

[0004] An exemplary network structure is the Evolved Universal Terrestrial Radio Access Network (E - UTRAN). The E - UTRAN system can provide high data throughput to enable the above - mentioned IP - bearer voice and multimedia services. Currently, the 3GPP standard organization is discussing new radio technologies for the next generation (e.g., 5G). Thus, changes to the current body of the 3GPP standard are currently being submitted and considered to evolve and complete the 3GPP standard. Summary of the Invention

[0005] Provided are methods, systems, and apparatuses for handling UE - initiated beam reporting in a wireless communication system.

[0006] In various embodiments, a method for a UE in a wireless communication system triggers UE - initiated beam reporting associated with a plurality of candidate cells, and determines whether to preferentially transmit information of a candidate cell via a UL grant based on at least the quality associated with the candidate cell when the UL grant cannot accommodate all one or more information associated with the plurality of candidate cells for UE - initiated beam reporting.

[0007] In various embodiments, a method of a UE in a wireless communication system includes triggering UE-initiated beam reporting associated with one or more candidate cells, and determining whether to prioritize transmission of the information via a UL grant based on the quality of at least a beam associated with the information in the one or more information when the UL grant cannot accommodate all of the one or more information associated with the one or more candidate cells for the UE-initiated beam reporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 A diagram showing a wireless communication system according to an embodiment of the present invention.

[0009] Figure 2 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.

[0010] Figure 3 A functional block diagram of a communication system according to an embodiment of the present invention.

[0011] Figure 4 is according to an embodiment of the present invention Figure 3 of the program code functional block diagram.

[0012] Figure 5 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.14-1: Reproduction of activation / deactivation of TCI states for UE-specific PDSCH MAC CE.

[0013] Figure 6 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.15-1: Reproduction of indication of TCI states for UE-specific PDCCH MAC CE.

[0014] Figure 7 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.24-1: Reproduction of enhanced activation / deactivation of TCI states for UE-specific PDSCH MAC CE.

[0015] Figure 8 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.23-1: Reproduction of BFR and truncated BFR MAC CE with one-octet Ci field.

[0016] Figure 9 is in 3GPP 38.321 v17.4.0 Figure 6.1.3.23-2: Reproduction of BFR and Truncated BFR MAC CE with Four Octet Ci Field.

[0017] Figure 10 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.43-1: Reproduction of Enhanced BFR and Truncated Enhanced BFR MAC CE with One Octet Ci Field.

[0018] Figure 11 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.43-2: Reproduction of Enhanced BFR and Truncated Enhanced BFR MAC CE with Four Octet Ci Field.

[0019] Figure 12 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.44-1: Reproduction of Enhanced TCI State Indication for UE-Specific PDCCH MAC CE.

[0020] Figure 13 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.47-1: Reproduction of Unified TCI State Activation / Deactivation MACCE.

[0021] Figure 14 is in Draft 38.300 v 18.0.0 Figure 9 .2.3.5.2-1 Reproduction of Signaling Procedures for LTM.

[0022] Figure 15 is an example diagram according to an embodiment of the present invention showing the problem that the network may receive outdated beam information or the UE may transmit unnecessary beam report information when two procedures conflict.

[0023] Figure 16 is an example diagram according to an embodiment of the present invention showing that the UE can cancel or stop the (triggered or ongoing) UE-initiated beam report of the first serving cell in response to the initiation of the LTM procedure or in response to receiving an LTM cell handover command MAC CE from the network.

[0024] Figure 17 is an example diagram according to an embodiment of the present invention showing that the UE can trigger the UE-initiated beam report of the first serving cell without responding to the ongoing LTM procedure or in response to receiving an LTM cell handover command MAC CE from the network.

[0025] Figure 18It is an example diagram showing that when or if there is one or more ongoing first programs (e.g., BFR, beam change program, MAC reset, or handover or LTM program), the UE may not trigger or initiate or execute a UE-initiated beam report for LTM or for L1 measurement reporting of candidate cells, according to an embodiment of the present invention.

[0026] Figure 19 It is an example diagram showing an example of a UE-initiated beam report, according to an embodiment of the present invention.

[0027] Figure 20 It is an example diagram showing an example of a UE-initiated beam report including a cell index (e.g., serving cell index or candidate cell index) or id (e.g., physical cell id), cell type (e.g., serving cell, candidate cell, or neighboring cell), BWP id associated with the reported beam, and beam information associated with (only) one cell, according to an embodiment of the present invention.

[0028] Figure 21 It is an example diagram showing a process of determining information to be reported in a (truncated) UE-initiated beam report, according to an embodiment of the present invention.

[0029] Figure 22 It 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 determining whether to trigger a UE-initiated beam report based on at least whether there is an ongoing first program in response to satisfying the conditions for the UE-initiated beam report.

[0030] Figure 23 It 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 triggering a UE-initiated beam report of a cell in response to satisfying the conditions for the UE-initiated beam report, and canceling the UE-initiated beam report of the cell in response to the initiation or reception of a first program associated with the cell.

[0031] Figure 24 It 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 triggering a UE-initiated beam report of a cell in response to satisfying the conditions for the UE-initiated beam report, and assembling and transmitting the UE-initiated beam report to the network in response to the triggered UE-initiated beam report.

[0032] Figure 25It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention. The method includes triggering a UE-initiated beam report associated with a plurality of candidate cells, and when an UL grant cannot accommodate all one or more information associated with the plurality of candidate cells for the UE-initiated beam report, determining whether to preferentially transmit the information of the candidate cell via the UL grant based on at least the quality associated with the candidate cell among the plurality of candidate cells.

[0033] Figure 26 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention. The method includes triggering a UE-initiated beam report associated with one or more candidate cells, and when an UL grant cannot accommodate all one or more information associated with the one or more candidate cells for the UE-initiated beam report, determining whether to preferentially transmit the information via the UL grant based on at least the quality of the beam associated with the information among the one or more information. Detailed implementation

[0034] The present invention described herein can be applied to or implemented in the exemplary wireless communication systems and devices described below. Additionally, the present invention is mainly described in the context of the 3GPP architecture reference model. However, it should be understood that those skilled in the art can easily adapt and implement aspects of the present invention using and in 3GPP2 network architectures and other network architectures with the disclosed information.

[0035] The exemplary wireless communication systems and devices described below employ a wireless communication system that supports broadcast services. Wireless communication systems are widely deployed to provide various types of communications, 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 LTE (Long Term Evolution) radio access, 3GPP LTE-A (Advanced Long Term Evolution) radio access, 3GPP2 UMB (Ultra Mobile Broadband), WIMAX®, 3GPP NR (New Radio) or some other modulation techniques.

[0036] Specifically, the exemplary wireless communication systems and devices described below can be designed to support one or more standards, such as those provided by the consortium named "Third Generation Partnership Project" and referred to herein as 3GPP, including: [1] RP-234007 New WID: NR MIMO Phase 5; [2] 3GPP 38.214 v17.4.0; [3] 3GPP38.321 v17.4.0; [4] 3GPP 38.331 v17.4.0; [5] Draft 38.300 v 18.0.0; and [6] RP-234036 New WID: NR Mobility Enhancement Phase 4. The standards and documents listed above are hereby expressly and fully incorporated herein by reference in their entireties.

[0037] Figure 1 FIG. shows a multi-access wireless communication system according to an embodiment of the present invention. The access network 100 (access network, AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and still another including 112 and 114. In Figure 1 FIG., only two antennas are shown for each antenna group; however, more or fewer antennas can be utilized for each antenna group. The access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to the access terminal 116 via the forward link 120 and receive information from the AT 116 via the reverse link 118. The AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to the AT 122 via the forward link 126 and receive information from the AT 122 via the reverse link 124. In an FDD system, the communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, the forward link 120 can use a frequency different from the frequency used by the reverse link 118.

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

[0039] In the communication via the forward links 120 and 126, the transmitting antennas of the access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links of different access terminals 116 and 122. Also, compared to an access network that transmits to all its access terminals via a single antenna, the access network that uses beamforming to transmit to access terminals randomly dispersed throughout the coverage area of the access network generally generates less interference to access terminals in adjacent cells.

[0040] AN can be a fixed station or a base station for communicating with a terminal, 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), a wireless communication device, a terminal, an access terminal, or some other term.

[0041] Figure 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an 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, traffic data for a plurality of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0042] In one embodiment, each data stream is transmitted via a respective transmit antenna. The TX data processor 214 formats, encodes, and interleaves the traffic data of the data streams based on a particular encoding scheme selected for each data stream to provide encoded data.

[0043] The encoded data of each data stream can be multiplexed with pilot data using OFDM techniques. Pilot data is typically a known data pattern that is processed in a known manner and can be used at the receiver system to estimate the channel response. Subsequently, the multiplexed pilot and encoded data for the data stream are modulated (e.g., symbol mapped) based on a particular modulation scheme selected for each data stream (e.g., BPSK, QPSK, M-PSK, or M-QAM) to provide modulated symbols. The data rate, encoding, and modulation for each data stream can be determined by instructions executed by a processor 230. A memory 232 is coupled to the processor 230.

[0044] Then, the modulated symbols of all data streams are provided to a TX MIMO processor 220, which can further process the modulated symbols (e.g., for OFDM). The TX MIMO processor 220 then provides N T modulated symbol streams to N T transmitters (TMTR) 222a through 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.

[0045] Each transmitter 222 receives and processes the corresponding symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via the MIMO channel. Then, from N TAntennas 224a through 224t transmit N modulated signals from transmitters 222a through 222t. T modulated signals.

[0046] At receiver system 250, the transmitted modulated signals are received by N antennas 252a through 252r, and the signals received from each antenna 252 are provided to corresponding receivers (RCVRs) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream. R At receiver system 250, the transmitted modulated signals are received by N antennas 252a through 252r, and the signals received from each antenna 252 are provided to corresponding receivers (RCVRs) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0047] RX data processor 260 then receives and processes N received symbol streams from N receivers 254 based on specific receiver processing techniques to provide N "detected" symbol streams. RX data processor 260 then demodulates, de-interleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by RX data processor 260 is complementary to the processing performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210. R receivers 254 to provide N R received symbol streams to provide N T "detected" symbol streams. RX data processor 260 then demodulates, de-interleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by RX data processor 260 is complementary to the processing performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

[0048] Processor 270 periodically determines which precoding matrix (discussed below) to use. Processor 270 formulates a reverse link message that includes a matrix index portion and a rank value portion.

[0049] The reverse link message can include various types of information regarding the communication link and / or the received data streams. The reverse link message is then processed by TX data processor 238 (which also receives traffic data for several data streams from data source 236), modulated by modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to transmitter system 210.

[0050] At transmitter system 210, the modulated signals from receiver system 250 are received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0051] The memory 232 can be used to temporarily store some buffered / computed data from 240 or 242 via the processor 230, store some buffered data from 212, or store some specific program code. Also, the memory 272 can be used to temporarily store some buffered / computed data from 260 via the processor 270, store some buffered data from 236, or store some specific program code.

[0052] Go to Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As Figure 3 shown, the communication device 300 in a wireless communication system can be used to implement Figure 1 the UEs (or ATs) 116 and 122 in, and the wireless communication system is preferably an NR system. The communication device 300 can 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 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user through the input device 302 (e.g., a keyboard or keypad), and can output images and sounds through the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, deliver the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

[0053] Figure 4 is a simplified block diagram of the program code 312 shown in Figure 3 . 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. The layer 3 portion 402 generally performs radio resource control. The layer 2 portion 404 generally performs link control. The layer 1 portion 406 generally performs physical connection.

[0054] For an LTE, LTE-A, or NR system, the layer 2 portion 404 can include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. The layer 3 portion 402 can include a Radio Resource Control (RRC) layer.

[0055] Any two or more of the following paragraphs, (sub)bullet points, key points, actions, or claims described in each invention paragraph or section can be logically, reasonably, and appropriately combined to form a specific method.

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

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

[0058] 3 Reasons

[0059] In the original beam management procedure, the network can configure / activate frequent periodic or semi - persistent beam reports (e.g., N best beams and corresponding L1 - RSRP) or trigger frequent aperiodic beam reports to timely obtain the best / optimal beams for data / control transmission. However, this will obviously result in a large UL reporting overhead and control signaling overhead. At the same time, if less frequent beam reports are configured, the network cannot always obtain the "best / optimal" beams because the UE's beam report may be outdated, leading to performance degradation. Considering that the UE has a better and more timely understanding of the beam quality change, the UE - initiated beam reporting procedure can cause more timely beam reports with reduced reporting overhead. In this procedure, if the UE determines that, for example, the current beam quality deteriorates, the UE can trigger a beam report without the network configuring or triggering frequent reports.

[0060] 4 Objectives

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

[0062] The detailed objectives are as follows:

[0063] RAN1:

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

[0065] a. UL signaling content (and procedures as needed) for UE - initiated / event - driven beam reports to facilitate fast beam switching

[0066] b. Considering the UL signaling medium / container of UE-initiated / event-driven nature transmitted by UL, mainly designed for beam reporting

[0067] …

[0068] In [2] 3GPP 38.214 v17.4.0, CSI reporting is introduced:

[0069] 5.2 UE procedures for reporting channel state information (CSI)

[0070] 5.2.1 Channel state information framework

[0071] The procedures for aperiodic CSI reporting described in this clause assume that the CSI reporting is triggered by DCI format 0_1, but they apply equally to CSI reporting triggered by DCI format 0_2 by applying the higher layer parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize.

[0072] The UE may use time and frequency resources to report CSI under the control of the gNB. The CSI may consist of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator, a rank indicator (RI), L1-RSRP, L1-SINR, or a CapabilityIndex.

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

[0074] 5.2.1.1 Report settings

[0075] 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 measurement and contains parameters for one CSI reporting band: codebook configuration including codebook subset restrictions, time domain behavior, frequency granularity for CQI and PMI, measurement restriction configuration, and CSI related quantities to be reported by the UE, such as layer indicator (LI), L1-RSRP, L1-SINR, CRI, and SSBRI (SSB resource indicator) and CapabilityIndex.

[0076] The time domain behavior of CSI-ReportConfig is indicated by the higher layer parameter reportConfigType and can be set to 'aperiodic','semiPersistentOnPUCCH','semiPersistentOnPUSCH' or 'periodic'. For 'periodic' and'semiPersistentOnPUCCH' / 'semiPersistentOnPUSCH' CSI reports, the configured periodicity and slot offset apply to the base parameters of the UL BWP on which the CSI report is configured to be transmitted. The higher layer parameter reportQuantity indicates the CSI related, L1-RSRP related, L1-SINR related or CapabilityIndex related quantities to be reported. reportFreqConfiguration indicates the reporting granularity in the frequency domain, including the CSI reporting band and whether the PMI / CQI reporting is wideband or subband. The timeRestrictionForChannelMeasurements parameter in CSI-ReportConfig can be configured to enable time domain restrictions for channel measurement, and timeRestrictionForInterferenceMeasurements can be configured to enable time domain restrictions for interference measurement. CSI-ReportConfig may also contain CodebookConfig, which contains configuration parameters for Type-I, Type II, enhanced Type IICSI or further enhanced Type II port selection (including codebook subset restrictions where applicable) and group-based reporting configuration. If reportConfigType is set to 'aperiodic', it is not expected that the UE is configured with a CSI report setting associated with a dormant DL BWP.

[0077] 5.2.1.2 Resource settings

[0078] Each CSI resource setting CSI-ResourceConfig contains a configuration of a list of S≥1 CSI resource sets (given by the higher layer parameter csi-RS-ResourceSetList), where 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 a reference to a CSI-IM resource set. Each CSI resource setting is located in the DL BWP identified by the higher layer parameter BWP-id, and all CSI resource settings linked to a CSI reporting setting have the same DL BWP.

[0079] The time domain behavior of the CSI-RS resources within a CSI resource setting is indicated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource settings, when the UE is configured with groupBasedBeamReporting-r17, the number of configured CSI resource sets is S = 2, and in other cases, the number of configured CSI-RS resource sets is limited to S = 1. For periodic and semi-persistent CSI resource settings, the configured periodicity and slot offset are given in the base parameters of its associated DL BWP given by BWP-id. When the UE is configured with multiple CSI-ResourceConfigs that form the same NZP CSI-RS resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. When the UE is configured with multiple CSI-ResourceConfigs that form the same CSI-IM resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. All CSI resource settings linked to a CSI reporting setting shall have the same time domain behavior.

[0080] The following are configured via higher layer signaling for one or more CSI resource settings for channel and interference measurement:

[0081] - CSI-IM resources for interference measurement as described in clause 5.2.2.4.

[0082] - NZP CSI-RS resources for interference measurement as described in clause 5.2.2.3.1.

[0083] - NZP CSI-RS resources for channel measurement as described in clause 5.2.2.3.1.

[0084] The UE may assume that the NZP CSI-RS resources for channel measurement and the CSI-IM resources for interference measurement configured for a CSI report are QCL per resource with respect to 'type D'. When the NZP CSI-RS resources are used for interference measurement, the UE may assume that the NZP CSI-RS resources for channel measurement and the CSI-IM resources or NZP CSI-RS resources configured for a CSI report are QCL with respect to 'type D'.

[0085] …

[0086] 5.2.1.4 Reporting Configuration

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

[0088] - The LI shall be calculated conditional on the reported CQI, PMI, RI, and CRI.

[0089] - The CQI shall be calculated conditional on the reported PMI, RI, and CRI.

[0090] - The PMI shall be calculated conditional on the reported RI and CRI.

[0091] - The RI shall be calculated conditional on the reported CRI.

[0092] The reporting configuration for CSI can be aperiodic (using PUSCH), periodic (using PUCCH), or semi-persistent (using PUCCH and DCI-activated PUSCH). The CSI-RS resources can be periodic, semi-persistent, or aperiodic. Table 5.2.1.4-1 shows the supported combinations of CSI reporting configurations and CSI-RS resource configurations and how CSI reporting is triggered for each CSI-RS resource configuration. The periodic CSI-RS is configured by the higher layers. The semi-persistent CSI-RS is activated and deactivated as described in clause 5.2.1.5.2. The aperiodic CSI-RS is configured and triggered / activated as described in clause 5.2.1.5.1.

[0093]

[0094] When the UE is configured with a higher layer parameter NZP-CSI-RS-ResourceSet and when the higher layer parameter repetition is set to 'off', the UE shall determine the CRI from the set of supported CRI values defined in clause 6.3.1.1.2 of [5, TS 38.212] and report the number in each CRI report. When the higher layer parameter repetition for the CSI-RS resource set used for channel measurement is set to 'on', the CRI for the CSI-RS resource set used for channel measurement is not reported. When the higher layer parameter codebookType is set to 'typeII', 'typeII-PortSelection', 'typeII-r16', 'typeII-PortSelection-r16' or 'typeII-PortSelection-r17', CRI reporting is not supported.

[0095] For periodic or semi-persistent CSI reporting on PUCCH, the period (measured in slots) and the slot offset are configured by the higher layer parameter reportSlotConfig. Unless otherwise specified, the UE shall transmit the CSI report in a frame where the SFN and the slot number within the frame satisfy

[0096]

[0097] where is the SCS configuration of the UL BWP on which the CSI report is transmitted.

[0098] For semi-persistent CSI reporting on PUSCH, the period (measured in slots) is configured by the higher layer parameter reportSlotConfig. Unless otherwise specified, the UE shall transmit the CSI report in a frame where the SFN and the slot number within the frame satisfy

[0099]

[0100] where and are the SFN and the slot number within the frame of the initial semi-persistent PUSCH transmission according to the activated DCI, respectively.

[0101] For semi-persistent or aperiodic CSI reporting on PUSCH, the allowed slot offsets are configured by the following higher layer parameters:

[0102] - If triggered / activated by DCI format 0_2 and the higher layer parameter reportSlotOffsetListDCI-0-2 is configured, the allowed slot offset is configured by reportSlotOffsetListDCI-0-2, and

[0103] - If triggered / activated by DCI format 0_1 and the higher layer parameter reportSlotOffsetListDCI-0-1 is configured, the allowed slot offset is configured by reportSlotOffsetListDCI-0-1, and

[0104] - Otherwise, the allowed slot offset is configured by the higher layer parameter reportSlotOffsetList.

[0105] The offset is selected in the activated / triggered DCI.

[0106] …

[0107] 5.2.1.4.2 Reporting Quantity Configuration

[0108] The UE may be configured with CSI-ReportConfig, where the higher layer parameter reportQuantity is set to any one 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'.

[0109] If the UE is configured with CSI-ReportConfig, where the higher layer parameter reportQuantity is set to 'none', the UE shall not report any quantity of CSI-ReportConfig.

[0110] If the UE is configured with CSI-ReportConfig, where the higher layer parameter reportQuantity is set to 'cri-RI-PMI-CQI' or 'cri-RI-LI-PMI-CQI', then the UE shall report the preferred precoder matrix for the entire reporting band or the preferred precoder matrix for each sub-band according to Clause 5.2.2.2.

[0111] If the UE is configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to 'cri-RI-i1',

[0112] - For the CSI-ReportConfig, it is expected that the UE is configured with a higher layer parameter codebookType set to 'typeI-SinglePanel' and a pmi-FormatIndicator set to 'widebandPMI' and,

[0113] - The UE will report a PMI consisting of a single wideband indication (in clause 5.2.2.2.1 for ) for the entire CSI reporting band.

[0114] …

[0115] If the UE is configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to 'cri-RSRP','ssb-Index-RSRP', 'cri-RSRP-Index', or'ssb-Index-RSRP-Index',

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

[0117] - In the case where the UE is configured with a 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 reporting setting in a single reporting instance, where the CSI-RS and / or SSB resources can be received by the UE simultaneously using a single spatial domain receive filter or multiple simultaneous spatial domain receive filters.

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

[0119] If the UE is configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to 'cri-SINR','ssb-Index-SINR', 'cri-SINR-Index', or'ssb-Index-SINR-Index',

[0120] - If the UE is configured to use the higher layer parameter groupBasedBeamReporting set to 'disabled', then the UE will report different CRIs or SSBRIs for each reporting setting in a single report nrofReportedRS (configured by the higher layer).

[0121] - In the case where the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'enabled', the UE will report two different CRIs or SSBRIs for each reporting setting in a single report instance, where the CSI-RS and / or SSB resources can be received by the UE simultaneously.

[0122] If the UE is configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to 'cri-RSRP', 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RI-LI-PMI-CQI', 'cri-SINR', or 'cri-SINR-Index', and If a resource is configured in a corresponding resource set for channel measurement, the UE shall derive CSI parameters other than the CRI conditioned on the reported CRI, where CRI k (k ≥ 0) corresponds to the configured (k + 1)-th entry of the associated nzp-CSI-RS-Resources in the corresponding NZP-CSI-RS-ResourceSet for channel measurement and the (k + 1)-th entry of the associated csi-IM-Resource in the corresponding csi-IM-ResourceSet for interference measurement (if configured) or the (k + 1)-th entry of the associated nzp-CSI-RS-Resources in the corresponding NZP-CSI-RS-ResourceSet (if configured for CSI-ReportConfig where reportQuantity is set to 'cri-SINR' or 'cri-SINR-Index'). If CSI-RS resources are configured, each resource shall contain at most 16 CSI-RS ports. If CSI-RS resources are configured, each resource shall contain at most 8 CSI-RS ports.

[0123] …

[0124] If the UE is configured with CSI-ReportConfig where the higher layer parameter reportQuantity is set to'ssb-Index-RSRP' or'ssb-Index-RSRP-Index', the UE shall report SSBRI, where SSBRI k (k ≥ 0) corresponds to the configured (k + 1)-th entry of the associated csi-SSB-ResourceList in the corresponding CSI-SSB-ResourceSet.

[0125] If the UE is configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to'ssb-Index-SINR' or'ssb-Index-SINR-Index', the UE shall derive the L1-SINR conditioned on the reported SSBRI, where the SSBRI k (k≥0) corresponds to the configured (k+1)-th entry of the associated csi-SSB-ResourceList in the corresponding CSI-SSB-ResourceSet for channel measurement, and the (k+1)-th entry of the associated csi-IM-Resource in the corresponding csi-IM-ResourceSet for interference measurement (if configured) or the (k+1)-th entry of the associated nzp-CSI-RS-Resources in the corresponding NZP-CSI-RS-ResourceSet (if configured).

[0126] …

[0127] 5.2.1.4.3 L1-RSRP Reporting

[0128] For L1-RSRP calculation

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

[0130] - The UE may be configured with a CSI-RS resource setting of up to 16 CSI-RS resource sets, with up to 64 resources within each set. The total number of different CSI-RS resources over all resource sets does not exceed 128.

[0131] For L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to one, the reported L1-RSRP value is bounded by a 7-bit value with a 1 dB step 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, the UE shall use differential L1-RSRP based reporting, where the maximum measured value of L1-RSRP is quantized to a 7-bit value with a 1 dB step in the range [-140, -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 with reference to the maximum measured L1-RSRP value that is 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].

[0132] When the higher layer parameter groupBasedBeamReporting-r17 in CSI-ReportConfig is configured, the UE shall 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 shall be present first.

[0133] If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive the channel measurements used to calculate the L1-RSRP value reported in uplink slot n only based on the SS / PBCH or NZP CSI-RS (defined in TS 38.211 [4]) associated with the CSI resource set and not later than the CSI reference resource.

[0134] If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements used to calculate the L1-RSRP reported in uplink slot n only based on the latest instance of the SS / PBCH or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource set and not later than the CSI reference resource.

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

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

[0137] 5.2.1.5 CSI reporting and triggering / activation of CSI-RS

[0138] 5.2.1.5.1 Aperiodic CSI reporting / aperiodic CSI-RS when the triggering PDCCH and CSI-RS have the same basic parameters

[0139] For a CSI-RS resource set associated with a resource setting of a higher layer parameter resourceType configured as 'aperiodic', 'periodic', or'semi-persistent', the higher layer parameter CSI-AperiodicTriggerStateList is used to configure the reporting settings (configured with a higher layer parameter reportConfigType set to 'aperiodic') for channel and / or interference measurements on one or more component carriers and / or the trigger state of the resource setting. For an aperiodic CSI report trigger, a single set of CSI trigger states is configured by a higher layer, where the CSI trigger states can be associated with any candidate DL BWP. It is not expected that the UE receives more than one DCI with a non-zero CSI request field per time slot per cell. It is not expected that the UE receives a DCI with a non-zero CSI request field within a 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 is configured with different TCI-StateIds for the same aperiodic CSI-RS resource ID configured in multiple aperiodic CSI-RS resource sets, where there is the same trigger offset in the same aperiodic trigger state. It is not expected that the UE receives more than one aperiodic CSI report request for transmission per cell in a given time slot. It is not expected that the UE receives an aperiodic CSI report request for transmission in a time slot that overlaps with any time slot in which there is an aperiodic CSI report transmission in the same cell group. If the UE does not indicate its ability for CSItriggerStateContainingNonactiveBWP, it is not expected that the UE is triggered with a CSI report for an inactive DL BWP. Otherwise, when at the latest occasion of the CSI reference resource when it is expected to receive the associated NZP CSI-RS, for an inactive DL BWP, when the UE is triggered with a CSI report, it is not expected that the UE reports CSI for the inactive DL BWP and the CSI report associated with the BWP is omitted. When the UE is triggered with an aperiodic NZP CSI-RS in an inactive DL BWP when it is expected to receive the NZP CSI-RS, it is not expected that the UE measures the aperiodic CSI-RS. In the carrier of the serving cell where it is expected to receive the associated NZP CSI-RS, 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 triggering DCI, then

[0140] - The last symbol of the PDCCH span carrying the DCI for BWP switching shall not be later than the last symbol of the PDCCH span carrying the DCI for CSI trigger, regardless of whether the two symbols are in the same carrier of the serving cell and regardless of whether the two symbols are in the same SCS;

[0141] - After the last symbol of the PDCCH span covering the DCI triggering CSI and before the first symbol of the triggered NZP CSI-RS or CSI-IM, no other BWP switch in the carrier is expected for the UE.

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

[0143] Initiate the trigger state using the CSI request field in the DCI.

[0144] - When all bits of the CSI request field in the DCI are set to zero, no CSI is requested.

[0145] - When the number of configured CSI trigger states in the CSI-AperiodicTriggerStateList is greater than where is the number of bits in the DCI CSI request field, the UE receives a sub-selection indication, as described in clause 6.1.3.13 of [10, TS38.321], which is used to map at most trigger states to the code points of the CSI request field in the DCI. Configured by the higher layer parameter reportTriggerSize, where . When the UE will transmit a PUCCH with HARQ-ACK information in the slot n of the PDSCH corresponding to the bearer sub-selection indication, the corresponding actions in [10, TS 38.321] and the UE assumptions regarding the mapping of the selected CSI trigger state to the code points of the DCI CSI request field should be applied starting from the first slot after slot where μ is the SCS configuration for the PUCCH, and is the sub-carrier spacing configuration for with value 0 for frequency range 1, and is provided by K-Mac, or if K-Mac is not provided, .

[0146] - When the number of CSI trigger states in the CSI-AperiodicTriggerStateList is less than or equal to , the CSI request field in the DCI directly indicates the trigger state.

[0147] - For each aperiodic CSI-RS resource in the CSI-RS resource set associated with each CSI trigger state, a quasi-co-location configuration of the quasi-co-location RS source and the quasi-co-location type is indicated to the UE by higher layer signaling of qcl-info, as described in Clause 5.1.5. The qcl-info contains a list of references to the TCI-State of the aperiodic CSI-RS resources associated with the CSI trigger state. If the State referenced in the list is configured by reference to an RS with a qcl-Type set to 'type D', the RS can be an SS / PBCH block located in the same or different CC / DL BWP, or a CSI-RS resource configured as periodic or semi-persistent located in the same or different CC / DL BWP.

[0148] …

[0149] For a UE configured with the higher layer parameter CSI-AperiodicTriggerStateList, if the resource setting linked to the CSI-ReportConfig has multiple aperiodic resource sets, only one of the aperiodic CSI-RS resource sets from the resource setting is associated with the trigger state, and the UE performs higher layer configuration per trigger state per resource setting to select one CSI-IM / NZP CSI-RS resource set from the resource setting.

[0150] When an aperiodic CSI-RS is used with an aperiodic report, the CSI-RS offset is configured by the higher layer parameter aperiodicTriggeringOffset or aperiodicTriggeringOffset-r16 or aperiodicTriggeringOffset-r17 per resource set. The CSI-RS triggering offset is for values having {0, 1, 2, 3, 4, 5, 6, …, 15, 16, 24} time slots, or for and values having {0, 4, 8, 12, …, 60, 64, 96} time slots, where This is the subcarrier spacing configuration for CSI-RS. If the UE is not configured with minimumSchedulingOffsetK0 for any DL BWP and minimumSchedulingOffsetK2 for any UL BWP, and if all the associated triggering states do not have the higher layer parameter qcl-Type set to 'type D' in the corresponding TCI state, the CSI-RS trigger offset is fixed to zero. The aperiodic trigger offset of CSI-IM follows the offset of the associated NZP CSI-RS for channel measurement. If the UE is configured with ca-SlotOffset for at least one of the triggered cell and the triggering cell, the aperiodic CSI-RS is transmitted in slot ; otherwise, it is transmitted in slot , and where

[0151] - According to the higher layer parameter aperiodicTriggeringOffset or aperiodicTriggeringOffset-r16 or aperiodicTriggeringOffset-r17, n is the slot containing the triggering DCI, X is the CSI-RS trigger offset,

[0152] - and are determined by ca-SlotOffset configured by the higher layer for the cell receiving the PDCCH, respectively and , and are determined by ca-SlotOffset configured by the higher layer for the cell transmitting the CSI-RS, respectively and , as defined in clause 4.5 of [4, TS 38.211].

[0153] …

[0154] In [3] 3GPP 38.321 v17.4.0, scheduling requests, MAC resets, activation of beams for channels, and activation of TCI state MAC CE are introduced:

[0155] 5.4.4 Scheduling Request

[0156] The Scheduling Request (SR) is used to request UL-SCH resources for new transmissions.

[0157] ​The MAC entity can be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For a logical channel or for SCell beam failure recovery (see clause 5.17) and for consistent LBT failure recovery (see clause 5.21), at most one PUCCH resource for SR is configured per BWP. For a logical channel serving a radio bearer configured with SDT, no PUCCH resource for SR is configured for SDT. For beam failure recovery of the BFD-RS set of the serving cell, at most two PUCCH resources for SR are configured per BWP. For a positioning measurement gap activation / deactivation request, a dedicated SR configuration is configured.

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

[0159] …

[0160] For each pending SR not triggered for the serving cell according to the BSR procedure (clause 5.4.5), the MAC entity will:

[0161] …

[0162] 1> If this SR is triggered by SCell beam failure recovery (see clause 5.17) and a MAC PDU is transmitted, and this PDU contains a MAC CE for the BFR containing the beam failure recovery information of this SCell; or

[0163] 1> If this SR is triggered by beam failure recovery of the BFD-RS set for the serving cell (see clause 5.17) and a MAC PDU is transmitted, and this PDU contains an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE containing the beam failure recovery information of this BFD-RS set for the serving cell; or

[0164] 1> If this SR is triggered by beam failure recovery of the SCell (see clause 5.17) and this SCell is deactivated (see clause 5.9); or

[0165] 1> If this SR is triggered by beam failure recovery of the BFD-RS set for the SCell (see clause 5.17) and this SCell is deactivated (see clause 5.9); or

[0166] …

[0167] 2> Cancel the pending SR and stop the corresponding sr-ProhibitTimer (if it is running).

[0168] Only the PUCCH resources that are active at the time of the SR transmission opportunity on the BWP are considered valid.

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

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

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

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

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

[0174] 2> If the sr-ProhibitTimer is not running at the time of the SR transmission opportunity; and

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

[0176] 3> If the PUCCH resource for the SR transmission opportunity neither overlaps with a UL-SCH resource nor with an SL-SCH resource, and the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups does not allow the simultaneous transmission of the UL-SCH resource and the SR; or

[0177] 3> If the MAC entity is able to perform this SR transmission simultaneously with the transmission of the SL-SCH resource; or

[0178] …

[0179] 4> Treat the SR transmission as a prioritized SR transmission.

[0180] 4> Treat other overlapping uplink grants (if any) as deprioritized uplink grants, except for overlapping uplink grants allowed for simultaneous transmission by the configuration of simultaneousPUCCH-PUSCH or simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup or simultaneousSR-PUSCH-diffPUCCH-Groups;

[0181] 4> If the deprioritized uplink grant is a configured uplink grant with autonomousTx whose PUSCH has started:

[0182] 5> Stop the configuredGrantTimer for the corresponding HARQ process of the deprioritized uplink grant;

[0183] 5> Stop the cg-RetransmissionTimer for the corresponding HARQ process of the deprioritized uplink grant.

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

[0185] 5> Indicate to the physical layer to send the SR on a valid PUCCH resource for the SR;

[0186] 5> If no LBT failure indication is received from the lower layer:

[0187] 6> Increment SR_COUNTER by 1;

[0188] 6> Start the sr-ProhibitTimer.

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

[0190] 6> Increment SR_COUNTER by 1.

[0191] 4> Otherwise:

[0192] 5> Notify the RRC to release the PUCCH for all serving cells;

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

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

[0195] 5> Clear any PUSCH resources for semi-persistent CSI reporting;

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

[0197] 3> Otherwise:

[0198] 4> Treat the SR transmission as a de-prioritized SR transmission.

[0199] …

[0200] Due to a pending SR for BSR initiated by the MAC entity before MAC PDU assembly and without a configured valid PUCCH resource, the MAC entity may stop (if any) the ongoing random access procedure, provided that:

[0201] - Transmit the MAC PDU using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload as specified in clause 5.1.2a, and this PDU contains a BSR MAC CE, the BSR MAC CE containing the buffer status up to (and including) the previous event that triggered the BSR (see clause 5.4.5) before MAC PDU assembly; or

[0202] - The UL grant can accommodate all pending data available for transmission.

[0203] Due to a pending SR for SL-BSR and / or SL-CSI reporting and / or SL-DRX command indication initiated by the MAC entity before sidelink MAC PDU assembly and without a configured valid PUCCH resource, the MAC entity may stop (if any) the ongoing random access procedure, provided that:

[0204] - Transmit the MAC PDU using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload as specified in clause 5.1.2a, and this PDU contains a SL-BSR MAC CE, the SL-BSR MAC CE containing the buffer status up to (and including) the previous event that triggered the SL-BSR (see clause 5.22.1.6) before MAC PDU assembly; or

[0205] - The SL grant can accommodate all pending data available and / or SL-CSI reporting MAC CE and / or SL-DRX command indication for transmission.

[0206] Due to a pending SR for BFR of a SCell without a configured valid PUCCH resource, the MAC entity may stop (if any) an in-progress random access procedure, provided that:

[0207] - a MAC PDU is transmitted using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload as specified in clause 5.1.2a, and this PDU contains a MAC CE for BFR that includes beam failure recovery information for the SCell; or

[0208] - the SCell is deactivated (as specified in clause 5.9), and all triggered BFRs for the SCell are cancelled.

[0209] Due to a pending SR for BFR of the BFD-RS set of a serving cell without a configured valid PUCCH resource, the MAC entity may stop (if any) an in-progress random access procedure, provided that:

[0210] - a MAC PDU is transmitted using a UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of the MSGA payload as specified in clause 5.1.2a, and this PDU contains an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE that includes beam failure recovery information for the BFD-RS set of the serving cell.

[0211] …

[0212] 5.7 Discontinuous Reception (DRX)

[0213] The MAC entity may be configured by RRC with DRX functionality that controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SL-CS-RNTI, and SL semi-persistent scheduling V-RNTI. When operating in DRX, the MAC entity shall also monitor the PDCCH according to requirements present in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, then for all activated serving cells, the MAC entity may discontinuously monitor the PDCCH using the DRX operation specified in this clause; otherwise, the MAC entity shall monitor the PDCCH as specified in TS 38.213 [6].

[0214] …

[0215] When configuring DRX, the active time for a serving cell in a DRX group includes the time at the following times:

[0216] - The drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0217] - The drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running on any serving cell in the DRX group; or

[0218] - The ra-ContentionResolutionTimer (as described in Clause 5.1.5) or msgB-ResponseWindow (as described in Clause 5.1.4a) is running; or

[0219] - A scheduling request is sent on the PUCCH and is pending (as described in Clause 5.4.4 or 5.22.1.5). If this serving cell is part of a non-terrestrial network, the active time starts after the scheduling request transmission, which is performed for all SR configurations with a pending SR plus the UE-gNB RTT when SR_COUNTER is 0; or

[0220] - After successful reception of a random access response for a random access preamble not selected by the MAC entity among the contention-based random access preambles, no PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is received (as described in Clauses 5.1.4 and 5.1.4a).

[0221] …

[0222] 5.12 MAC Reset

[0223] If the upper layer requests a reset of the MAC entity or the MAC entity is triggered to reset due to SCG deactivation as defined in Clause 5.29, the MAC entity shall:

[0224] 1> If the MAC reset is not due to SCG deactivation:

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

[0226] 1> In the case of configuring sidelink resource allocation mode 1 by RRC, initialize SBj for each logical channel to zero;

[0227] 1> If the upper layer indicates deactivation of the SCG and the bfd-and-RLM for the deactivated SCG configuration has a value of true:

[0228] 2> Stop all timers (if running), except for the beamFailureDetectionTimer and timeAlignmentTimers associated with the PSCell.

[0229] 1> Otherwise:

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

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

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

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

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

[0235] 1> Discard the explicitly signaled contention-free random access resources (if any) for 4-step RA type and 2-step RA type;

[0236] 1> Clear the Msg3 buffer;

[0237] 1> Clear the MSGA buffer;

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

[0239] 1> Cancel the triggered buffer status report procedure (if any);

[0240] 1> Cancel the triggered power headroom report procedure (if any);

[0241] 1> Cancel the triggered consistent LBT failure (if any);

[0242] 1> Cancel the triggered BFR (if any);

[0243] 1> Cancel the triggered sidelink buffer status report procedure (if any);

[0244] 1> Cancel the triggered pre-emption buffer status reporting procedure (if it exists);

[0245] 1> Cancel the triggered timing advance reporting procedure (if it exists);

[0246] 1> Cancel the triggered recommended bit rate query procedure (if it exists);

[0247] 1> Cancel the triggered configured uplink grant confirmation (if it exists);

[0248] 1> Cancel the triggered configured sidelink grant confirmation (if it exists);

[0249] 1> Cancel the triggered required guard symbol query (if it exists);

[0250] 1> Cancel the triggered positioning measurement gap activation / deactivation request procedure (if it exists);

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

[0252] 1> Clear the soft buffers for all DL HARQ processes, except for the DL HARQ process being used for MBS broadcast;

[0253] 1> For each DL HARQ process except for the DL HARQ process being used for MBS broadcast, consider the next received transmission for a TB as the first transmission;

[0254] 1> Release the temporary C-RNTI (if it exists);

[0255] 1> If the upper layer indicates SCG deactivation and bfd-and-RLM is not configured with the value true; or

[0256] 1> If the MAC reset is not due to SCG deactivation:

[0257] 2> Reset all BFI_COUNTER;

[0258] 1> Reset all LBT_COUNTER.

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

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

[0261] The MAC entity shall:

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

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

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

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

[0266] 5.18.5 Indication of TCI states for UE-specific PDCCH

[0267] The network may indicate the TCI state for 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 described in clause 6.1.3.15. The network may 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 the enhanced TCI state indication for the UE-specific PDCCH MAC CE described in clause 6.1.3.44.

[0268] The MAC entity shall:

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

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

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

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

[0273] 5.18.6 Activation / Deactivation of Semi-Persistent CSI Reporting on PUCCH

[0274] The network may activate and deactivate the configured semi-persistent CSI reporting on the PUCCH of a serving cell by sending the SPCSI report on the PUCCH activation / deactivation MAC CE described in clause 6.1.3.16. After (re)configuration by the upper layer and after a reconfiguration with synchronization, the configured semi-persistent CSI reporting on the PUCCH is initially deactivated.

[0275] The MAC entity shall:

[0276] 1> If the MAC entity receives the SP CSI report on the PUCCH activation / deactivation MAC CE on a serving cell:

[0277] 2> Indicate to the lower layer the information on the SP CSI report on the PUCCH activation / deactivation MAC CE.

[0278] …

[0279] 5.18.23 Unified TCI State Activation / Deactivation MAC CE

[0280] The network can activate and deactivate the configured unified TCI state of the 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. The configured unified TCI state is initially deactivated when reconfigured by the upper layer and after a reconfiguration with synchronization.

[0281] The MAC entity will:

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

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

[0284] 6.1.3.14 TCI State Activation / Deactivation for UE-Specific PDSCH MAC CE

[0285] The TCI state activation / deactivation for UE-specific PDSCH MAC CE is identified by a MAC subheader with an LCID specified in Table 6.2.1-1. It has a variable size consisting of the following fields:

[0286] - Serving cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells configured in a set of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, respectively;

[0287] - BWP ID: This field indicates the DL BWP to which the MAC CE applies as the code point of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits. If this MAC CE applies to a set of serving cells, then this field is ignored;

[0288] - T i : If there is a TCI state with TCI-StateId i as specified in TS 38.331 [5], then this field indicates the activation / deactivation state of the TCI state with TCI-StateId i, otherwise the MAC entity shall ignore the T i field. The T i field is set to 1 to indicate that the TCI state with TCI-StateId i will be activated and mapped to the code point of the DCI transmission configuration indication field as specified in TS 38.214 [7]. The T i field is set to 0 to indicate that the TCI state with TCI-StateId i will be deactivated and not mapped to the code point of the DCI transmission configuration indication field. The code point to which the TCI state is mapped is determined by its ordinal position among all TCI states with the T i field set to 1, i.e., the first TCI state with the T i field set to 1 will be mapped to the code point value 0, the second TCI state with the T i field set to 1 will be mapped to the code point value 1, and so on. The maximum number of active TCI states is 8. An active TCI state can be associated with at most one PCI different from the serving cell PCI each time;

[0289] - CORESET pool ID: This field indicates that the mapping between the active TCI state and the code point of the DCI transmission configuration indication set by the T i field is specific to the ControlResourceSetId configured with the CORESET pool ID as specified in TS 38.331 [5]. This field set to 1 indicates that this MAC CE will apply to DL transmissions with a CORESET pool ID equal to 1 scheduled by the CORESET, otherwise, this MAC CE will apply to DL transmissions scheduled by a CORESET pool ID equal to 0. If coresetPoolIndex is not configured for any CORESET, then when receiving the MAC CE, the MAC entity shall ignore the CORESET pool ID field in this MAC CE. If the serving cell in the MAC CE is configured in a cell list containing more than one serving cell, then when receiving the MAC CE, the CORSET pool ID field shall be ignored.

[0290] Figure 5 It is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.14-1: Reproduction of activation / deactivation of TCI states for UE-specific PDSCH MAC CE

[0291] 6.1.3.15 TCI state indication for UE-specific PDCCH MAC CE

[0292] The TCI state indication for UE-specific PDCCH MAC CE is identified by a MAC subheader with an LCID specified in Table 6.2.1-1. It has a fixed size of 16 bits and has the following fields:

[0293] - Serving cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells in a group of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 respectively;

[0294] - CORESET ID: This field indicates the control resource set identified by ControlResourceSetId as specified in TS 38.331 [5], which indicates its TCI state. In the case where the value of the field is 0, the field refers to the control resource set configured by controlResourceSetZero as specified in TS 38.331 [5]. The length of the field is 4 bits;

[0295] - TCI State ID: This field indicates the TCI state applicable to the control resource set identified by the CORESET ID, identified by the TCI-StateId as specified in TS 38.331 [5]. If the field of the CORESET ID is set to 0, this field indicates the TCI-StateId of the TCI state among the first 64 TCI states configured by tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config in the active BWP or by dl-OrJoint-TCI-State-ToAddModList and dl-OrJoint-TCI-State-ToReleaseList in PDSCH-Config in the active BWP or the reference BWP. If the field of the CORESET ID is set to a value other than 0, then this field indicates the TCI-StateId configured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID. The length of the field is 7 bits.

[0296] Figure 6 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.15-1: Reproduction of TCI state indication for UE-specific PDCCH MAC CE.

[0297] 6.1.3.24 Enhanced TCI state activation / deactivation for UE-specific PDSCH MAC CE

[0298] Enhanced TCI state activation / deactivation for UE-specific PDSCH MAC CE is identified by a MAC PDU sub-header with an eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of the following fields:

[0299] - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells configured in a set of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 respectively;

[0300] - BWP ID field: This field indicates the DL BWP to which the MAC CE is applied as the code point of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits;

[0301] - C i : This field indicates whether there is an octet containing the TCI state ID i,2 If this field is set to 1, then there is an octet containing the TCI state ID i,2 If this field is set to 0, then there is no octet containing the TCI state ID i,2 ;

[0302] - TCI state ID i,j : This field indicates the TCI state identified by the TCI-StateId as specified in TS 38.331 [5], where i is the index of the code point of the DCI transmission configuration indication field as specified in TS 38.212 [9], and the TCI state ID i,j represents the j-th TCI state indicated by the i-th code point in the DCI transmission configuration indication field. The TCI code point to which the TCI state is mapped is determined by its ordinal position among all the TCI code points having the set of TCI state ID i,j fields, that is, the first TCI code point having TCI state ID 0,1 and TCI state ID 0,2 will be mapped to the code point value 0, the second TCI code point having TCI state ID 1,1 and TCI state ID 1,2 will be mapped to the code point value 1, and so on. The TCI state ID i,2 is optional based on the indication of the C i field. The maximum number of active TCI code points is 8, and the maximum number of TCI states mapped to TCI code points is 2.

[0303] - R: Reserved bit, set to 0.

[0304] Figure 7 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.24 - 1: Reproduction of enhanced TCI state activation / deactivation for UE-specific PDSCH MAC CE.

[0305] 6.1.3.23 BFR MAC CE

[0306] The MAC CE for BFR consists of:

[0307] -BFR MAC CE; or

[0308] - Truncated BFR MAC CE.

[0309] BFR MAC CE and Truncated BFR MAC CE are identified by a MAC sub-header with LCID / eLCID, as specified in Table 6.2.1-2 and Table 6.2.1-2b.

[0310] BFR MAC CE and Truncated BFR MAC CE have variable sizes. It contains a bitmap and beam failure recovery information in ascending order based on ServCellIndex, i.e., octets containing candidate beam availability indication (AC) for the SCell indicated in the bitmap. For BFR MAC CE, when a beam failure is detected and the highest ServCellIndex of the SCell of this MAC entity for which the evaluation of candidate beams has been completed according to the requirements specified in TS 38.133

[11] is less than 8, a single-octet bitmap is used, otherwise four octets are used. The MAC PDU shall contain at most one BFR MAC CE.

[0311] For Truncated BFR MAC CE, a single-octet bitmap is used for the following cases, otherwise four octets are used:

[0312] - A beam failure is detected and the highest ServCellIndex of the SCell of the MAC entity for which the evaluation of candidate beams has been completed according to the requirements specified in TS 38.133

[11] is less than 8; or

[0313] - A beam failure of the SpCell is detected (as specified in Clause 5.17), the SpCell will be indicated in the Truncated BFR MAC CE, and the UL-SCH resources available for transmission cannot accommodate the Truncated BFR MAC CE with a four-octet bitmap plus its sub-header as an LCP result.

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

[0315] - SP: This field indicates the beam failure 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 Truncated BFR MAC CE is to be included in the MAC PDU as part of a random access procedure, indicating that a beam failure of the SpCell is detected (as specified in 5.1.3a and 5.1.4), otherwise it is set to 0;

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

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

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

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

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

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

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

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

[0320] -Candidate RS ID: This field is set to the index of the SSB with an SS-RSRP higher than rsrp-ThresholdBFR among the SSBs in candidateBeamRSSCellList or to the index of the CSI-RS with a CSI-RSRP higher than rsrp-ThresholdBFR among the CSI-RS in candidateBeamRSSCellList. The index of the SSB or CSI-RS is the index of the entry in candidateBeamRSSCellList corresponding to the SSB or CSI-RS. Index 0 corresponds to the first entry in candidateBeamRSSCellList, index 1 corresponds to the second entry in the list, and so on. The length of this field is 6 bits.

[0321] -R: Reserved bit, set to 0.

[0322] Figure 8 It is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.23-1: BFR and has one octet C i A rendition of a truncated BFR MAC CE of the field.

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

[0324] 6.1.3.43 Enhanced BFR MAC CE

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

[0326] - Enhanced BFR MAC CE; or

[0327] - Truncated Enhanced BFR MAC CE.

[0328] The Enhanced BFR MAC CE and the Truncated Enhanced BFR MAC CE are identified by a MAC sub-header with eLCID / LCID, as specified in Table 6.2.1-2 and Table 6.2.1-2b.

[0329] The Enhanced BFR MAC CE and the Truncated Enhanced BFR MAC CE have variable sizes. It contains the SP field, C i bitmap (single octet or four octets), S j bitmap (0 to 4 octets), containing beam failure recovery information in ascending order based on ServCellIndex, i.e., the octet containing the candidate beam availability indication (AC) of the BFD-RS set for the SpCell configured with two BFD-RS sets, and contains beam failure recovery information, i.e., the octet containing the candidate beam availability indication (AC) of the BFD-RS set for the SCell or the BFD-RS set of the SCell configured with two BFD-RS sets indicated in the C i bitmap. For the Enhanced BFR MAC CE, when a beam failure is detected for the SCell or at least one BFD-RS set of the SCell and the highest ServCellIndex of the SCell of this MAC entity for which the evaluation of candidate beams has been completed according to the requirements specified in TS 38.133

[11] is less than 8, a single octet C i bitmap is used, otherwise a four-octet C i bitmap is used. The MAC PDU shall contain at most one MAC CE for BFR.

[0330] For the Truncated Enhanced BFR MAC CE, a single octet C i bitmap is used for the following cases, otherwise a four-octet C i bitmap:

[0331] - A beam failure is detected for the SCell or at least one BFD-RS set of the SCell and the highest ServCellIndex of the SCell of this MAC entity for which the evaluation of candidate beams has been completed according to the requirements specified in TS38.133

[11] is less than 8; or

[0332] - Beam failure is detected for a SpCell that is not configured with two BFD-RS sets (as specified in clause 5.17), and the SpCell will indicate it in the truncated enhanced BFR MAC CE, and the UL-SCH resources available for transmission cannot accommodate four-octet C due to LCP i Truncated enhanced BFR MAC CE of the bitmap plus its sub-header; or

[0333] - Initiate a random access procedure for beam failure recovery of two BFD-RS sets of a SpCell configured with two BFD-RS sets (as specified in clause 5.17), and the SpCell will indicate it in the truncated enhanced BFR MAC CE, and the UL-SCH resources available for transmission cannot accommodate four-octet C due to LCP i Truncated enhanced BFR MAC CE of the bitmap plus its sub-header.

[0334] For the enhanced BFR MAC CE and the truncated enhanced BFR MAC CE, if the total number of serving cells of two BFD-RS sets configured with the SP / C i field set to 1 is greater than 0 and less than 9, it contains a single-octet S k bitmap; if the total number of serving cells of two BFD-RS sets configured with the SP / C i field set to 1 is greater than 8 and less than 17, it contains a two-octet S k bitmap; if the total number of serving cells of two BFD-RS sets configured with the SP / C i field set to 1 is greater than 16 and less than 25, it contains a three-octet S k bitmap; if the total number of serving cells of two BFD-RS sets configured with the SP / C i field set to 1 is greater than 24, it contains a four-octet S k bitmap; if the total number of serving cells of two BFD-RS sets configured with the SP / C i field set to 1 is zero, it does not contain an S k bitmap.

[0335] For the truncated enhanced BFR MAC CE, first for the SpCell, an octet containing the AC field (if present) is included, then for each SCell (in ascending order of ServCellIndex), an octet containing the AC field is included, and then for each SCell (in ascending order of ServCellIndex), a second octet containing the AC field (if present) is included, while not exceeding the available grant size. The number of octets containing the AC field in the truncated enhanced BFR MAC CE can be zero.

[0336] The field definitions in the enhanced BFR MAC CE are as follows:

[0337] - SP (enhanced BFR MAC CE): This field indicates the beam failure detection for the SpCell of this MAC entity (as specified in clause 5.17) and the presence of the octet containing the AC field in case the SpCell is configured with multiple BFD-RS sets. For a SpCell configured with two BFD-RS sets, this field is set to 1 to indicate that beam failure has been detected for at least one BFD-RS set, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, and there is an octet containing the AC field for the SpCell; otherwise, it is set to 0. The octets containing the AC field for the SpCell are included before those for the SCell. For a SpCell not configured with multiple BFD-RS sets, the SP field is set to 1 to indicate that beam failure has been detected for the SpCell when the enhanced BFR MAC CE is to be included in the MAC PDU as part of a random access procedure (as specified in 5.1.3a and 5.1.4); otherwise, it is set to 0;

[0338] - SP (truncated enhanced BFR MAC CE): This field indicates the beam failure detection for the SpCell of this MAC entity (as specified in clause 5.17). For a SpCell configured with two BFD-RS sets, this field is set to 1 to indicate that beam failure has been detected for at least one BFD-RS set, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, and there may be an octet containing the AC field for the SpCell; otherwise, it is set to 0. For a SpCell not configured with multiple BFD-RS sets, the SP field is set to 1 to indicate that beam failure has been detected for the SpCell when the truncated enhanced BFR MAC CE is to be included in the MAC PDU as part of a random access procedure (as specified in 5.1.3a and 5.1.4); otherwise, it is set to 0;

[0339] -C i (Enhanced BFR MAC CE): This field indicates the presence of beam failure detection (as specified in Clause 5.17) and an octet containing the AC field for the SCell with ServCellIndex i as specified in TS 38.331 [5]. C i A value of 1 for the field indicates that beam failure has been detected for the SCell or at least one set of BFD-RSs of the SCell, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, and an octet containing the AC field exists for the SCell with ServCellIndex i. C i A value of 0 for the field indicates that beam failure has not been detected for the SCell or any set of BFD-RSs of the SCell, and an octet containing the AC field does not exist for the SCell with ServCellIndex i; or beam failure has been detected for the SCell or at least one set of BFD-RSs of the SCell, but the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has not been completed, and an octet containing the AC field does not exist for the SCell with ServCellIndex i. Octets containing the AC field exist in ascending order based on ServCellIndex and are included after the octet containing the AC field for the SpCell (if it exists);

[0340] -C i (Truncated Enhanced BFR MAC CE): This field indicates the beam failure detection (as specified in Clause 5.17) for the SCell with ServCellIndex i as specified in TS 38.331 [5]. C i A value of 1 for the field indicates that beam failure has been detected for the SCell or at least one set of BFD-RSs of the SCell, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, and an octet containing the AC field may exist for the SCell with ServCellIndex i. C iThe field is set to 0 indicating that no beam failure is detected for the SCell or any BFD-RS set of the SCell, and there is no octet containing the AC field for the SCell with ServCellIndex i; or beam failure is detected for the SCell or at least one BFD-RS set of the SCell, but the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has not been completed, and there is no octet containing the AC field for the SCell with ServCellIndex i;

[0341] -S k (Enhanced BFR MAC CE): This field corresponds to SP / C i The field is set to 1 and for the k-th serving cell configured with two BFD-RS sets. SP / C i The field is set to 1 and the serving cells configured with two BFD-RS sets are indexed sequentially starting from the SpCell and then the SCell in ascending order of ServCellIndex i. This field indicates whether beam failure is detected for one or two BFD-RS sets and the presence of one or two octets containing the AC field of the serving cell. S k The field set to 1 indicates that beam failure is detected for two BFD-RS sets, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed for the two BFD-RS sets, and there are octets containing the AC field for the two BFD-RS sets of the serving cell. S k The field set to 0 indicates that beam failure is detected for one of the BFD-RS sets and the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, or beam failure is detected for two BFD-RS sets but the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has not been completed for the two BFD-RS sets, and there is an octet containing the AC field for only one BFD-RS set of the serving cell. S not mapped to any serving cell k The field is set to 0;

[0342] -S k (Truncated Enhanced BFR MAC CE): This field corresponds to SP / C i The field is set to 1 and for the k-th serving cell configured with two BFD-RS sets. SP / C iThe serving cell for which the field is set to 1 and which is configured with two BFD-RS sets is indexed sequentially starting from the SpCell and then for SCell in ascending order of ServCellIndex i. This field indicates whether a beam failure has been detected for one or two BFD-RS sets for the serving cell. S k The field set to 1 indicates that a beam failure has been detected for two BFD-RS sets, the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed for the two BFD-RS sets, and there is an octet containing the AC field for zero, one, or two BFD-RS sets for the serving cell. S k The field set to 0 indicates that a beam failure has been detected for one of the BFD-RS sets and the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has been completed, or that a beam failure has been detected for two BFD-RS sets but the evaluation of candidate beams according to the requirements specified in TS 38.133

[11] has not been completed for the two BFD-RS sets, and there is an octet containing the AC field for zero or one BFD-RS sets for the serving cell. S k The field is set to 0;

[0343] -AC: This field indicates the presence of a candidate RS ID field in this octet. If there is at least one available SSB with an SS-RSRP higher than rsrp-ThresholdBFR among the SSBs in the candidate beam list (i.e., candidateBeamRS-List-r16 for SCell not configured with two BFD-RS sets, candidateBeamRS-List-r16 or candidateBeamRS-List2-r17 for serving cells configured with two BFD-RS sets) or at least one available CSI-RS with a CSI-RSRP higher than rsrp-ThresholdBFR among the CSI-RSs in the candidate beam list, the AC field is set to 1; otherwise, it is set to 0. If the AC field is set to 1, there is a candidate RS ID field. If the AC field is set to 0, there are actually R bits;

[0344] -ID: This field indicates the identity of the BFD-RS set. If this octet corresponds to BFD-RS set one failureDetectionSet1-r17, this field is set to 0. If this octet corresponds to BFD-RS set two failureDetectionSet2-r17, this field is set to 1. For serving cells not configured with two BFD-RS sets, this field is set to 0;

[0345] - Candidate RS ID: This field is set to the index of an SSB with an SS-RSRP higher than rsrp-ThresholdBFR among the SSBs in the candidate beam list (i.e., candidateBeamRS-List-r16 for a SCell not configured with two BFD-RS sets, candidateBeamRS-List-r16 or candidateBeamRS-List2-r17 for a serving cell configured with two BFD-RS sets), or to the index of a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdBFR among the CSI-RS in the candidate beam list. The index of an SSB or CSI-RS is the index of the entry in the candidate beam list corresponding to the SSB or CSI-RS. Index 0 corresponds to the first entry in the candidate beam list, index 1 corresponds to the second entry in the list, and so on. The length of this field is 6 bits;

[0346] -R: Reserved bit, set to 0.

[0347] Figure 10 It is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.43-1: Enhanced BFR and with one octet C i Rendering of a truncated enhanced BFR MAC CE for the field.

[0348] Figure 11 It is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.43-2: Enhanced BFR and C with four octets i Rendering of a truncated enhanced BFR MAC CE for the field.

[0349] 6.1.3.44 Enhanced TCI status indication for UE-specific PDCCH MAC CE

[0350] The enhanced TCI status indication for UE-specific PDCCH MAC CE is identified by a MAC PDU subheader with an eLCID as specified in Table 6.2.1-1b. It has a fixed size of 24 bits with the following fields:

[0351] - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells in a set of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 respectively;

[0352] - CORESET ID: This field indicates the control resource set identified by ControlResourceSetId as specified in TS 38.331 [5], indicating its TCI state. In the case where the value of the field is 0, the field refers to the control resource set configured by controlResourceSetZero as specified in TS38.331 [5]. The length of the field is 4 bits;

[0353] - TCI State IDi: This field indicates the TCI state applicable to the control resource set identified by the CORESET ID field, identified by TCI-StateId as specified in TS 38.331 [5]. If the field of CORESET ID is set to a value other than 0, then this field indicates the TCI-StateId configured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID. The length of the field is 7 bits.

[0354] Note 1: If the CORESET is configured with different CORESETPoolindex values in the BWP, the enhanced TCI state indication for UE-specific PDCCH MAC CE does not apply to any of the configured CORESETs in the BWP.

[0355] Note 2: The enhanced TCI state indication for UE-specific PDCCH MAC CE is applied only when sfnSchemePdcch is configured.

[0356] Note 3: If the CORESET is associated with a search space configured by pdcch-ConfigSIB1 in the MIB or searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in PDCCH-ConfigCommon, the enhanced TCI state indication for UE-specific PDCCH MAC CE does not apply to the CORESET configured by controlResourceSetZero.

[0357] Figure 12 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.44-1: Reproduction of enhanced TCI state indication for UE-specific PDCCH MAC CE.

[0358] …

[0359] 6.1.3.47 Unified TCI state activation / deactivation MAC CE

[0360] The unified TCI state activation / deactivation MAC CE is identified by a MAC sub-header with an eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of the following fields:

[0361] - Serving cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 as specified in TS 38.331 [5], this MAC CE applies to all serving cells in the set simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, respectively;

[0362] - DL BWP ID: This field indicates the DL BWP to which the MAC CE applies as a code point of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits;

[0363] - BWP ID field: This field indicates the UL BWP to which the MAC CE is applied as the code point of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. If the value of unifiedTCI - StateType in the serving cell indicated by the serving cell ID is combined, this field is regarded as a reserved bit. The length of the BWP ID field is 2 bits;

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

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

[0366] - TCI state ID: This field indicates the TCI state identified by TCI - StateId as specified in TS 38.331 [5]. If D / U is set to 1, a 7-bit length TCI state ID as specified in TS 38.331 [5], i.e., TCI - StateId, is used. If D / U is set to 0, the most significant bit of the TCI state ID is regarded as a reserved bit, and the remaining 6 bits indicate the TCI - UL - State - Id as specified in TS 38.331 [5]. The maximum number of active TCI states is 16;

[0367] - R: Reserved bit, set to 0.

[0368] Figure 13 is in 3GPP 38.321 v17.4.0 Figure 6 .1.3.47 - 1: Reproduction of unified TCI state activation / deactivation MAC CE.

[0369] In [4] 3GPP 38.331 v17.4.0, measurement events are introduced:

[0370] 5.5.4 Measurement report triggering

[0371] 5.5.4.1 Overview

[0372] If AS security has been successfully activated, the UE shall:

[0373] 1> For each measId in the measIdList included in VarMeasConfig:

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

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

[0376] 4> If the corresponding reportConfig includes measRSSI - ReportConfig:

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

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

[0379] 5> Consider only the serving cell as applicable;

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

[0381] 5> If the serving cell is associated with measObjectNR and the neighbor is associated with another measObjectNR, then also consider any serving cell associated with the other measObjectNR as a neighbor cell;

[0382] 4> If the corresponding reportConfig includes a reportType set to periodic; or

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

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

[0385] 6> When the cell involved is included in the allowedCellsToAddModList defined for this measId in VarMeasConfig, consider any neighbor cell detected based on the parameters in the associated measObjectNR as applicable;

[0386] 5> Otherwise:

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

[0388] …

[0389] 2> 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 all measurements after layer 3 filtering during the timeToTrigger defined for this event for one or more applicable cells, while VarMeasReportList does not contain a measurement report entry for this measId (first cell triggers the event):

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

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

[0392] 3> Include the cell in question in the cellsTriggeredList defined for this measId in VarMeasReportList;

[0393] 3> If useT312 is set to true for this event in reportConfig:

[0394] 4> If T310 for the corresponding SpCell is in operation; and

[0395] 4> If T312 for the corresponding SpCell is not in operation:

[0396] 5> Start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

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

[0398] 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 all measurements during the timeToTrigger defined for this event in VarMeasConfig for one or more applicable cells not included in the cellsTriggeredList (subsequent cell triggering event):

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

[0400] 3> Include the cell(s) involved in the cellsTriggeredList defined for this measId in VarMeasReportList;

[0401] 3> If useT312 is set to true for this event in the reportConfig:

[0402] 4> If the T310 for the corresponding SpCell is in operation; and

[0403] 4> If the T312 for the corresponding SpCell is not in operation:

[0404] 5> Start the timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;

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

[0406] 2> If reportType is set to eventTriggered and if after layer 3 filtering during the timeToTrigger defined for this event in VarMeasConfig, the leave condition applicable to this event is satisfied for one or more of the cells included in the cellsTriggeredList defined for this measId in VarMeasReportList for all measurements:

[0407] 3> Remove the cell(s) involved from the cellsTriggeredList defined for this measId in VarMeasReportList;

[0408] 3> If reportOnLeave is set to true for the corresponding report configuration:

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

[0410] 3> If the cellsTriggeredList defined for this measId within VarMeasReportList is empty:

[0411] 4> Remove the measurement report entry within VarMeasReportList for this measId;

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

[0413] …

[0414] 2> Otherwise if reportType is set to eventTriggered and if applicable to this event, i.e., the entry condition for the event corresponding to the eventId of the corresponding reportConfig within VarMeasConfig is satisfied for all measurements made during the timeToTrigger defined for this event within VarMeasConfig for one or more applicable transmission resource pools, and VarMeasReportList does not contain a measurement report entry for this measId (first transmission resource pool triggers the event):

[0415] 3> Include a measurement report entry within VarMeasReportList for this measId;

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

[0417] 3> Include the concerned transmission resource pool in the poolsTriggeredList defined within VarMeasReportList for this measId;

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

[0419] …

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

[0421] 3> Include a measurement report entry within VarMeasReportList for this measId;

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

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

[0424] 4>Immediately initiate the measurement reporting procedure specified in 5.5.5 when the RSSI sample value is reported by the physical layer after the first L1 measurement duration;

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

[0426] 4>Initiate the measurement reporting procedure immediately after the first measurement result is provided by the lower layer associated with the relevant DRB identity, as specified in 5.5.5;

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

[0428] 4>Initiate the measurement reporting procedure immediately after the first measurement result is provided by the lower layer associated with the relevant DRB identity according to the configured threshold per DRB identity, as specified in 5.5.5;

[0429] 3>Otherwise if the reportAmount exceeds 1:

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

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

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

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

[0434] 3> Initiate the measurement reporting procedure specified in 5.5.5.

[0435] …

[0436] 5.5.4.3 Event A2 (Service becomes worse than the threshold)

[0437] The UE shall:

[0438] 1> When the condition A2-1 specified below is met, it is considered that the entry condition for this event is satisfied;

[0439] 1> When the condition A2-2 specified below is met, it is considered that the exit condition for this event is satisfied;

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

[0441] Inequality A2-1 (Entry condition)

[0442] Ms + Hys < Thresh

[0443] Inequality A2-2 (Exit condition)

[0444] Ms - Hys > Thresh

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

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

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

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

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

[0450] Hys is expressed in dB.

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

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

[0453] The UE shall:

[0454] 1> When the condition A3-1 specified below is met, it is considered that the entry condition for this event is satisfied;

[0455] 1> When the following specified condition A3-2 is satisfied, it is considered that the departure condition of this event is satisfied;

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

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

[0458] Inequality A3-1 (entry condition)

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

[0460] Inequality A3-2 (departure condition)

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

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

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

[0464] 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).

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

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

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

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

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

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

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

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

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

[0474] 5.5.4.5 Event A4 (Neighbor becomes better than threshold)

[0475] The UE shall:

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

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

[0478] Inequality A4-1 (Entry condition)

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

[0480] Inequality A4-2 (Exit condition)

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

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

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

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

[0485] Ocn is the measurement object specific offset of the neighboring cell (i.e., the cellIndividualOffset corresponding to the neighboring cell as defined within measObjectNR), and is set to zero when not configured for the neighboring cell.

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

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

[0488] Mn is expressed in dBm for RSRP, or in dB for RSRQ and RS-SINR.

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

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

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

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

[0493] The UE shall:

[0494] 1> Consider the entry condition for this event to be satisfied when the following specified Condition A5-1 and Condition A5-2 are met;

[0495] 1> Consider the exit condition for this event to be satisfied when the following specified Condition A5-3 or Condition A5-4, i.e., at least one of the two conditions, is met;

[0496] 1> Use the SpCell for Mp.

[0497] 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 SpCell.

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

[0499] Mp + Hys < Thresh1

[0500] Inequality A5-2 (Entry condition 2)

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

[0502] Inequality A5-3 (Exit condition 1)

[0503] Mp - Hys > Thresh1

[0504] Inequality A5 - 4 (departure condition 2)

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

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

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

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

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

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

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

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

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

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

[0515] Ofn, Ocn, and Hys are expressed in dB.

[0516] Thresh1 is expressed in the same unit as Mp.

[0517] Thresh2 is expressed in the same unit as Mn.

[0518] Note 2: The definition of Event A5 also applies to CondEvent A5.

[0519] …

[0520] In Draft [5] 38.300 v18.0.0, L1 / L2 Mobility (LTM) is introduced:

[0521] 9.2.3.5 L1 / L2 Triggered Mobility

[0522] 9.2.3.5.1 Overview

[0523] LTM is a procedure where the gNB receives L1 measurement reports from the UE and, based on these, the gNB changes the serving cell of the UE by means of a cell handover command sent via MAC CE. The cell handover command indicates the LTM candidate configurations that the gNB has previously prepared and provided to the UE via RRC signaling. Subsequently, the UE switches to the target configuration according to the cell handover command. The LTM procedure can be used to reduce the mobility latency as described in Appendix G.

[0524] When configured by the network, the TCI states of one or more cells different from the current serving cell can be activated. For example, the TCI states of LTM candidate cells can be pre-activated before any of those cells becomes the serving cell. This allows the UE to synchronize with those cells in the DL, thus facilitating a faster cell handover to one of those cells when a cell handover is triggered.

[0525] When configured by the network, a UL TA acquisition (referred to as early TA) procedure for one or more cells different from the current serving cell can be initiated. If a cell has the same N TA or N TA = 0, then the early TA acquisition procedure is not required. The network can request the UE to perform the early TA acquisition for candidate cells before a cell handover. The early TA acquisition procedure is triggered by a PDCCH command as specified in Clause 9.2.6, or by UE-based TA measurements configured by RRC. In the former case, the gNB to which the candidate cell belongs calculates the TA value and sends it to the gNB to which the serving cell belongs. When an LTM cell handover is triggered, the serving cell sends the TA value in the LTM cell handover command MAC CE. In the latter case, the UE performs TA measurements for the candidate cells after being configured by RRC, but the exact time at which the UE performs the TA measurements depends on the UE implementation. The UE applies the TA value it has measured and performs RACH-less LTM after receiving the cell handover command. The network can also send the TA value in the LTM cell handover command MAC CE without early TA acquisition.

[0526] Depending on the availability of a valid TA value, the UE performs RACH-less LTM or RACH-based LTM cell handover. If the TA value is provided in the cell handover command, the UE applies the TA value indicated by the network. In the case where UE-based TA measurement is configured but the TA value is not provided in the cell handover command, the UE applies the TA value itself if available. Meanwhile, the UE performs RACH-less LTM cell handover after receiving the cell handover command. If no valid TA value is available, the UE performs RACH-based LTM cell handover.

[0527] Regardless of whether the UE is configured for UE-based TA measurement for a certain candidate cell, it will still follow the PDCCH command that includes a request for a random access procedure to the candidate cell. This also applies to candidate cells for which the UE can derive the TA value itself. Additionally, regardless of whether the UE has already performed a random access procedure to the candidate cell, it will still follow the UE-based measurement configuration (if configured by the network).

[0528] For RACH-less LTM, the UE uses a configured grant or a dynamic grant to access the target cell. The configured grant is provided in the LTM candidate configuration, and the UE selects the configured grant occasion associated with the beam indicated in the cell handover command. After initiating the RACH-less LTM cell handover to the target cell, the UE starts monitoring the PDCCH on the target cell for dynamic scheduling. Before the RACH-less LTM procedure is completed, the UE should not trigger a random access procedure if it does not have a valid PUCCH resource for triggering an SR.

[0529] The following principles apply to LTM:

[0530] - Maintain the security key during LTM cell handover;

[0531] - Support subsequent LTM.

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

[0533] - PCell change in non-CA and non-DC scenarios;

[0534] - PCell and SCell change in CA scenarios;

[0535] - Dual-connectivity scenarios, PCell and MCG SCell change, and PSCell and SCG SCell change within the SN without involving the MN. LTM for simultaneous PCell and PSCell change is not supported.

[0536] Although the UE has stored the LTM candidate configuration, the UE may also execute any L3 handover command sent by the network.

[0537] 9.2.3.5.2 C-plane handling

[0538] The cell handover command is delivered in a MAC CE that contains the necessary information to perform an LTM cell handover.

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

[21] .

[0540] Figure 14 is a reproduction of the signaling procedure for LTM in draft 38.300 v18.0.0 Figure 9 .2.3.5.2-1.

[0541] The procedure for LTM is as follows:

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

[0543] 2. The gNB transmits an RRCReconfiguration message containing the LTM candidate configuration to the UE.

[0544] 3. The UE stores the LTM candidate configuration and transmits an RRCReconfigurationComplete message to the gNB.

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

[0546] 4b. When UE-based TA measurement is configured, the UE obtains the TA value of the candidate cell through measurement. The UE performs early TA acquisition to the candidate cell requested by the network before receiving the cell handover command in the receiving cell as specified in Clause 9.2.6. This is done through CFRA triggered by a PDCCH command from the source cell, after which the UE transmits a preamble towards the indicated candidate cell. To minimize the data interruption of the source cell due to CFRA towards 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 to ensure TA validity.

[0547] 5. The UE performs L1 measurement on the configured candidate cells and transmits the L1 measurement report to the gNB. L1 measurement shall be performed as long as the RRC reconfiguration (step 2) applies.

[0548] 6. The gNB decides to perform a cell handover to the target cell and transmits a MAC CE triggering 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.

[0549] 7. If the UE does not have a valid TA of 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.

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

[0551] Steps 4 to 8 can be performed multiple times for subsequent LTM using the LTM candidate configuration provided in step 2.

[0552] The procedures over the air interface described in Figure x apply to both intra-gNB-DU LTM and inter-gNB-DU LTM. The overall LTM procedure over the F1-C interface is described in TS38.401 [4].

[0553] 9.2.3.5.3 U-plane Disposition

[0554] 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 via RRC signaling.

[0555] In the WID for mobility enhancement phase 4 ([6] RP-234036 New WID: NR mobility enhancement phase 4), the objectives regarding measurement reports for LTM are presented:

[0556] 3 Reasons

[0557] Layer 2 mobility (LTM) was introduced in Rel-18 and provides improvements in handover latency and outage time compared to layer 3-based mobility. However, the 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.

[0558] LTM operation is only supported for mobility between cells of the same gNB (same CU). Depending on the network deployment, this may significantly limit the opportunities to use LTM. By implementing LTM operation between cells of different gNBs (i.e., inter-CU), the network will be able to obtain the benefits of LTM for the majority of handovers.

[0559] 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.

[0560] L1 measurements for the LTM procedure are limited to SSB measurements. Extending the L1 measurements to include CSI-RS can address this limitation and is expected to achieve a higher throughput on the target cell immediately after cell handover.

[0561] Layer 3 mobility has evolved over several releases. Conditional handover (CHO) and other conditional mobility procedures (CPAC, SCPAC) have been developed to achieve high robustness by enabling the procedures to execute without prior signaling exchange with the source cell. The LTM introduced in Rel-18 provides short outage times but does not have the same level of robustness as the conditional L3 mobility procedures. In Rel-19, enhancements should be specified so that the system can benefit from high robustness and short outages.

[0562] 4 Objectives

[0563] 4.1 Objectives of the SI or Core Part WI or Test Part WI

[0564] ○…

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

[0566] ○ Measurement related enhancements apply to MCG / SCG LTM within CU and MCG / SCG LTM between CUs

[0567] ○ Specify the necessary components to support event-triggered L1 measurement reports: [RAN2, RAN1]

[0568] ■ 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 modification of the objectives is needed to avoid / manage any overlap in the work

[0569] ○ Specify the support for CSI-RS measurements used in the LTM procedure and implement CSI-RS based beam management, and / or other necessary physical layer operations on candidate cells prior to LTM: [RAN1]

[0570] In New Radio (NR), the network can configure beam reports (e.g., periodic or semi-persistent beam reports) for a User Equipment (UE) or activate or trigger aperiodic beam reports (e.g., Channel State Information (CSI) reports) to obtain or acquire channel state information or channel quality or beam quality for data / control transmission. However, in the case of frequent reporting, the UE may experience a huge 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 deteriorate. In Rel-19 Multiple Input Multiple Output (MIMO) Phase 5, UE-initiated / event-driven beam management for reducing latency and / or overhead was discussed. The UE can initiate or trigger a beam report in response to meeting a certain condition or event (e.g., the quality of the currently active beam is lower than a threshold and / or the quality of a candidate beam is higher than a threshold). Additionally, in Mobility Enhancement Phase 4, UE-initiated beam reports for candidate cells were also introduced to perform faster lower layer (e.g., L1 / L2) triggered mobility (LTM).

[0571] In the current NR, there are other beam management mechanisms and / or other reports and / or other procedures regarding beam change and / or beam reporting. For example, a UE may change its (activated) beam for a cell in response to receiving an activated transmission configuration indicator (TCI) state media access control (MAC) control element (CE) associated with or indicating a cell (or a bandwidth part (BWP) of a cell). In the case where UE-initiated beam reporting is introduced, the UE may have a simultaneous ongoing beam reporting procedure and other procedures. A problem may be that when the two procedures conflict, the network may receive outdated beam information or the UE may transmit unnecessary beam reports.

[0572] In Figure 15 illustrates an example of the problem. At timing t1, for example, due to the deterioration of the beam quality of a BWP or a cell, the UE triggers a (UE-initiated) beam report. The UE may assemble a transport block (TB) or a MAC protocol data unit (PDU) for the transmission of the report at timing t3. Additionally and / or alternatively, the UE may (prepare or be configured with) a physical uplink control channel (PUCCH) resource for the transmission of the report at timing t3. Additionally and / or alternatively, the UE may trigger a scheduling request (SR) and / or initiate a random access procedure to the network for an uplink (UL) grant for report transmission. At timing t2, the network may provide a beam change for the BWP or for the cell (e.g., a transmission configuration indicator (TCI) state reconfiguration, activation / deactivation via MAC CE, etc.) to the UE. At timing t3, the UE transmits the beam report to the network. Since the beam may be changed by the network at t2, the report at t3 may not be up-to-date or may cause confusion to the network.

[0573] In the present invention, methods for handling UE-initiated beam reporting that overlaps with other UE procedures are discussed.

[0574] Conflicts between UE-initiated / event-driven beam reporting and (a) beam failure recovery (BFR), (b) beam change, (c) serving cell change (handover (HO) or LTM), (d) early random access channel (RACH), (e) serving cell deactivation, and (f) MAC reset.

[0575] - The same cell or different cells.

[0576] - Handling depends on the beam / cell in different ways.

[0577] - Parallel or cancel one of them.

[0578] - If the UE-initiated / event-driven beam reporting is to be cancelled, cancel / stop the corresponding trigger / SR / RACH / timer.

[0579] -Prioritization between UE-initiated / event-driven beam reporting MAC CE and BFR MAC CE (a).

[0580] -Duplicate information avoidance.

[0581] -The estimation of UE-initiated beam reporting may or may not be restarted.

[0582] -UE-initiated / event-driven beam reporting.

[0583] -Truncation is supported or not supported for UE-initiated / event-driven beam reporting.

[0584] -If so, which one to report first.

[0585] -Whether to trigger SR for UE-initiated / event-driven beam reporting.

[0586] -Which SR configuration to use?

[0587] -Format (MAC CE), e.g., one cell or multiple cells, serving cell only or also neighboring / candidate cells.

[0588] -Discontinuous reception (DRX) duty cycle consideration for receiving beam change MAC CE / indication.

[0589] One concept of the present invention is that the UE can determine whether to prioritize UE-initiated beam reporting or one of the first one or more procedures. The UE can prioritize UE-initiated beam reporting over a part of the first one or more procedures. Additionally and / or alternatively, the UE can deprioritize UE-initiated beam reporting from a part of the first one or more procedures. Additionally and / or alternatively, the UE can prioritize a part of the first one or more procedures and deprioritize another part of the first one or more procedures. The UE can determine whether to cancel UE-initiated beam reporting based on at least the state of the first one or more procedures of the UE. When or if there is (at least) one of the first one or more procedures of the UE in progress, the UE can cancel UE-initiated beam reporting. When or if there is (at least) no first one or more procedures of the UE in progress, the UE may not cancel UE-initiated beam reporting. Additionally and / or alternatively, when or if there is (at least) an UE-initiated beam reporting in progress or triggered, the UE can cancel or stop a part of the first one or more procedures.

[0590] Determined based on the same / different cells

[0591] Additionally and / or alternatively, the UE may determine whether to cancel or deprioritize UE-initiated beam reporting associated with the cell based on at least a part of one or more first procedures associated with the cell. The UE may cancel UE-initiated beam reporting associated with the cell due to / in response to a part of one or more first procedures associated with the cell. The UE may not cancel UE-initiated beam reporting associated with the cell due to / in response to a part of one or more first procedures not associated with the cell (e.g., (only) associated with other cells).

[0592] The one or more first procedures may include a beam failure recovery procedure. The one or more first procedures may include a triggered and uncancelled BFR. The one or more first procedures may include a random access procedure initiated for (primary cell (PCell) or secondary cell (SCell)) beam failure recovery. The one or more first procedures may include triggering a scheduling request (SR) for (SCell) beam failure recovery. The one or more first procedures may include a triggered and uncancelled SR for beam failure recovery. The one or more first procedures may include the assembly and / or transmission of a BFR MAC CE.

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

[0594] The one or more first procedures may include a beam change procedure. The beam change procedure may include receiving a radio resource control (RRC) reconfiguration indicating one or more TCI states.

[0595] The beam change procedure may include receiving a TCI state activation MAC CE for a physical downlink shared channel (PDSCH) and / or for a physical downlink control channel (PDCCH) and / or for a physical uplink control channel (PUCCH) and / or for a physical uplink shared channel (PUSCH). The TCI state activation MAC CE may be used for downlink (DL) and / or UL beam change.

[0596] Alternatively, in some embodiments, the one or more first procedures may not include a beam change procedure.

[0597] Additionally and / or alternatively, the first one or more procedures may include initiating a random access procedure. A random access procedure may be initiated for a synchronized reconfiguration. A random access procedure may be initiated for an L1 / L2-triggered mobility (LTM) procedure.

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

[0599] Additionally and / or alternatively, early UL synchronization for a candidate cell may be initiated.

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

[0601] The first one or more procedures may include deactivating a serving cell. Alternatively, in some embodiments, the first one or more procedures may not include deactivating a serving cell. Deactivating a serving cell may include receiving an SCell activation / deactivation MAC CE. Deactivating a serving cell may include expiration of an SCell deactivation timer.

[0602] The first one or more procedures may include a beam report initiated or requested by the network. The beam report may be a (periodic or aperiodic or semi-persistent) channel state information (CSI) report associated with a cell.

[0603] The first one or more procedures may include a handover or reconfiguration with a synchronization procedure. The first one or more procedures may include an LTM procedure.

[0604] The first one or more procedures may include reconfiguring or releasing a candidate cell.

[0605] Different dispositions for reports initiated by different types of UEs: for LTM (for candidate cells) or for serving cell

[0606] Additionally and / or alternatively, the UE may determine whether to cancel or deprioritize or stop a UE-initiated beam report associated with the cell in response to (a part of) the first one or more procedures (associated with the cell) based on at least the type of the cell or based on at least the type or purpose of the UE-initiated beam report.

[0607] For example, the UE may cancel or deprioritize or stop a UE-initiated beam report associated with the serving cell in response to the first one or more procedures associated with the serving cell. The UE may not (be allowed to) cancel or deprioritize or stop a UE-initiated beam report associated with a candidate cell (or LTM) in response to the first one or more procedures (associated with the candidate cell), e.g., in response to a reconfiguration with a synchronization procedure or in response to an LTM procedure.

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

[0609] Additionally and / or alternatively, the UE may cancel or deprioritize or stop a UE-initiated beam report associated with a candidate cell in response to one or more procedures (e.g., in response to a reconfiguration with a synchronization procedure or in response to an LTM procedure) associated with the candidate cell. The UE may not cancel or deprioritize or stop a UE-initiated beam report associated with the serving cell in response to one or more procedures associated with the serving cell.

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

[0611] Conflict with the first procedure when beam reporting is in progress

[0612] For example, the UE may cancel or stop a (triggered or ongoing) UE-initiated beam report in response to the triggering of a BFR. The UE may cancel or stop a (triggered or ongoing) UE-initiated beam report of the first serving cell in response to the triggering of a BFR of the first serving cell. The UE may not cancel or stop a UE-initiated beam report of the first serving cell in response to the triggering of a BFR of the second serving cell.

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

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

[0615] For another example, the UE may (re)start or reset or stop a timer or counter associated with UE-initiated beam reporting for a cell (or a BWP of the cell) in response to the (successful) completion of a beam failure recovery procedure associated with a triggered BFR for the first serving cell (or a BWP thereof).

[0616] For another example, the UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting in response to a beam change procedure. The UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting for the first serving cell (or a BWP thereof) in response to a beam change procedure for the first serving cell (or a BWP thereof). The UE may not cancel or stop UE-initiated beam reporting for the first serving cell in response to a beam change procedure for a second serving cell. The UE may not cancel or stop UE-initiated beam reporting for the first BWP of the first serving cell in response to a beam change procedure for the second BWP of the first serving cell.

[0617] For another example, the UE may (re)start or reset or stop a timer or counter associated with UE-initiated beam reporting for the first serving cell (or a BWP thereof) in response to a beam change procedure for the first serving cell (or a BWP thereof). The timer or counter may be used or configured to trigger or inhibit UE-initiated beam reporting for a cell.

[0618] For another example, when there is (triggered or in-progress) UE-initiated beam reporting associated with at least a serving cell (or a BWP thereof), the UE may not perform a beam change procedure for the serving cell (or a BWP thereof).

[0619] For another example, the UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting in response to the initiation of a random access procedure. The UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting for the first serving cell (or a first candidate cell) in response to the initiation of a random access procedure associated with the first serving cell (or a first candidate cell). The UE may not cancel or stop UE-initiated beam reporting for the first serving cell in response to the initiation of a random access procedure not associated with the first serving cell (of a second candidate cell).

[0620] For another example, when or if there is (at least) (triggered or in-progress) UE-initiated beam reporting associated with at least a serving cell (or a candidate cell), the UE may not initiate a random access procedure for the serving cell (or a candidate cell) (for early UL synchronization).

[0621] For another example, the UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting in response to a MAC reset (initiation). The UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting 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 reporting for the first serving cell in response to a MAC reset not associated with the first serving cell.

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

[0623] For another example, when there is (triggered or in-progress) UE-initiated beam reporting associated with at least a serving cell, the UE may not perform a MAC reset associated with the serving cell.

[0624] For another example, the UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting in response to SCell deactivation (trigger). The UE may cancel or stop (triggered or in-progress) UE-initiated beam reporting for the first serving cell in response to deactivating the first serving cell (or in response to receiving a deactivation MAC CE for deactivating the first serving cell, or in response to the expiration of the SCell deactivation timer of the first serving cell). The UE may not cancel or stop UE-initiated beam reporting for the first serving cell in response to deactivation of the second serving cell.

[0625] For another example, the UE may (re)start or reset or stop a timer or counter associated with UE-initiated beam reporting for a cell (BWP) in response to the trigger of deactivation of the cell.

[0626] For another example, the UE may (re)start or reset or stop a timer or counter associated with UE-initiated beam reporting for a cell (BWP) in response to the trigger of activation of the cell.

[0627] For another example, the UE may (re)start or reset or stop a timer or counter associated with UE-initiated beam reporting for a cell (BWP) in response to the successful completion of deactivation of the cell.

[0628] For another example, when there is (triggered or in-progress) UE-initiated beam reporting associated with at least a serving cell, the UE may not perform deactivation of the serving cell.

[0629] For another example, the UE may cancel or stop the (triggered or in-progress) 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, when receiving an aperiodic CSI report request associated with the first serving cell from the network, the UE may not cancel or stop the (triggered or in-progress) UE-initiated beam report for the first serving cell.

[0630] For another example, the UE may cancel or stop the (triggered or in-progress) UE-initiated beam report for the first serving cell in response to the initiation of a reconfiguration with a synchronization procedure or in response to receiving a reconfiguration with a synchronization message from the network. Alternatively, in some embodiments, the UE may not cancel or stop the (triggered or in-progress) UE-initiated beam report for the first serving cell in response to the initiation of a reconfiguration with a synchronization procedure or in response to receiving a reconfiguration with a synchronization message from the network (not associated with the first serving cell).

[0631] For another example, the UE may cancel or stop the (triggered or in-progress) 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 not cancel or stop the (triggered or in-progress) 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 (not associated with the first serving cell).

[0632] Figure 16 Examples are shown. At timing 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 timing t2, the UE receives a beam change indication associated with serving cell A from the network (e.g., a TCI state activation / deactivation MAC CE or an RRC reconfiguration of the TCI state). In response to the beam change indication, the UE cancels or stops the triggered UE-initiated beam report.

[0633] Do not trigger reporting based on the first procedure being in progress

[0634] Additionally and / or alternatively, the UE may determine whether to trigger or initiate or execute a UE-initiated beam report based at least on whether there is an ongoing first one or more procedures. If or when (at least) there is an ongoing first one or more procedures associated with the serving cell, the UE may not trigger or initiate or execute a UE-initiated beam report for the serving cell.

[0635] For example, when or if (at least) there is a triggered (and not cancelled) BFR, the UE may not (be allowed to) trigger or initiate or execute a UE-initiated beam report. When or if (at least) there is a triggered (and not cancelled) BFR of the serving cell, the UE may not (be allowed to) trigger a UE-initiated beam report of the serving cell. If or when (at least) there is no triggered BFR of the first serving cell, the UE may trigger a UE-initiated beam report of the first serving cell.

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

[0637] Additionally and / or alternatively, when or if (at least) there is an ongoing random access procedure associated with a cell, the UE may not trigger or 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 has not been initiated for beam failure recovery, the UE may trigger or initiate or execute a UE-initiated beam report for the cell.

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

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

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

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

[0642] For another example, 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).

[0643] Figure 17 An example is shown. At timing t1, the UE initiates a beam failure recovery procedure for serving cell A (e.g., SpCell). The beam failure recovery procedure may include a random access procedure for serving cell A. The UE performs a random access preamble transmission to the network in the random access procedure. The UE starts a window / timer (e.g., random access response window) in response to the preamble transmission. During the window, when the timer is running, the conditions for a UE-initiated beam report (associated with serving cell A) are met at timing t2 (e.g., the quality of the currently active beam is below a threshold and / or the quality of a candidate beam is above a threshold). Since the window / timer is running and / or since there is an ongoing random access procedure (for serving cell A beam failure recovery), the UE may not initiate or trigger a UE-initiated beam report.

[0644] Parallel

[0645] Additionally and / or alternatively, when a part of the first one or more procedures is ongoing, the UE may execute a UE-initiated beam report for the cell. For example, if or when (at least) a deactivation indication for the cell is received, the UE may not cancel or stop a UE-initiated beam report associated with the cell.

[0646] Different dispositions for beam reports initiated by different types of UEs: for LTM (for candidate cells) or for serving cell

[0647] Additionally and / or alternatively, when or if there is (at least) a first one or more procedures in progress, the UE may determine whether to trigger or 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 first one or more procedures is in progress, the UE may initiate or execute a UE-initiated beam report for LTM or for a candidate cell. For another example, when or if (at least) one of the first one or more procedures is in progress, the UE may not execute a UE-initiated beam report for the serving cell.

[0648] For example, when or if (at least) a first 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 L1 measurement reports for LTM or for a candidate cell. When or if (at least) a first 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.

[0649] Alternatively, in some embodiments, when or if (at least) a first 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 L1 measurement reports for LTM or for a candidate cell. When or if (at least) a first 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 the serving cell.

[0650] Figure 18 Examples are shown. The UE initiates or executes a random access procedure (e.g., handover, reconfiguration with synchronization, or LTM) at timing t1. The UE performs preamble transmission and starts a random access response window. When the window is in operation at timing t2, the conditions for a UE-initiated beam report for the serving cell are met. The UE does not trigger a UE-initiated beam report. At timing t3, the conditions for a UE-initiated beam report for a candidate cell are met, and the UE may trigger a UE-initiated beam report for the candidate cell when the window is in operation.

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

[0652] Additionally and / or alternatively, the UE may determine whether to prioritize the beam report initiated by the first UE or the beam report initiated by the second UE based on at least the types of beam reports initiated by the first and second UEs.

[0653] 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 a serving cell.

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

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

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

[0657] Beam report format

[0658] Additionally and / or alternatively, the UE may transmit the UE-initiated beam report in the UE-initiated beam reporting procedure. The UE-initiated beam report may be a MAC CE and / or RRC message and / or physical layer signal or uplink control information (UCI) via PUCCH or PUSCH.

[0659] The UE-initiated beam report may indicate whether the cell is reported in the report and / or whether the beam of the cell is reported in the report. Additionally and / or alternatively, one format of the UE-initiated beam report may indicate information for only one cell. It may not be allowed for one format of the UE-initiated beam report to indicate information for more than one cell. Additionally and / or alternatively, one format of the UE-initiated beam report may indicate information for more than one cell. More than one cell may be associated with the same cell group. It may not be allowed for more than one cell to be associated with different cell groups. Alternatively, in some embodiments, more than one cell may be associated with different cell groups.

[0660] Neighboring cell

[0661] Additionally and / or alternatively, the UE-initiated beam report may indicate whether a candidate cell or neighboring cell and / or a beam of a candidate cell or neighboring cell is reported in the report. The report may indicate whether the reported cell is a serving cell, a candidate cell, or a neighboring cell. The report may indicate a measurement object associated with the cell.

[0662] Additionally and / or alternatively, the UE-initiated beam report may indicate one or more beams of a candidate cell for reporting (e.g., via a TCI state identity (ID) or via a bitmap mapped to a TCI state or a beam). The one or more beams may be (a part of) the (configured or candidate) beams associated with the candidate cell having a quality higher than a threshold. The one or more beams may be n (configured or candidate) beams associated with the candidate cell having the highest n quality. The UE may select a certain (configured or fixed) number of beams (among the one or more beams meeting the quality requirement, e.g., having a quality higher than the threshold or having the highest n quality) to report. n may be configured or fixed, e.g., 1 or greater than 1.

[0663] Additionally and / or alternatively, the UE-initiated beam report may indicate one or more beams of a serving cell for reporting (e.g., via a TCI state ID or via a bitmap mapped to a TCI state or a beam). The one or more beams may be (a part of) the (configured or candidate) beams associated with the serving cell having a quality higher than a threshold. The one or more beams may be n (configured or candidate) beams associated with the serving cell having the highest n quality. The UE may select a certain (configured or fixed) number of beams (among the one or more beams meeting the quality requirement, e.g., having a quality higher than the threshold or having the highest n quality) to report. n may be configured or fixed, e.g., 1 or greater than 1.

[0664] Additionally and / or alternatively, the one or more beams may be the top n beams having the highest quality among all the (configured) beams of the serving cell.

[0665] Additionally and / or alternatively, the one or more beams may be the top n beams having the highest quality among all the (configured) beams of the candidate cell.

[0666] The quality may be associated with (L1 or L3) reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), signal-to-interference ratio (SINR).

[0667] UE-initiated beam reports may indicate the quality (value) of the one or more beams being reported. Additionally and / or alternatively, UE-initiated beam reports may not report or indicate the quality (value) of the one or more beams. Additionally and / or alternatively, UE-initiated beam reports may not indicate the beam of the serving cell (e.g., index or ID) (e.g., only quality). Additionally and / or alternatively, UE-initiated beam reports may not indicate the beam of a candidate cell (e.g., index or ID) (e.g., only quality).

[0668] UE-initiated beam reports may indicate the BWP of the serving cell being reported. The BWP may be associated with the triggered UE-initiated beam report. The BWP may contain DL and / or UL BWP ids.

[0669] Truncated or non-truncated

[0670] Additionally and / or alternatively, when the UL grant is not sufficient to accommodate all the information of all cells and / or all the beams of the cells to be reported, a part of the information may be reported first (in a truncated UE-initiated beam report). UE-initiated beam reports may indicate whether the information contained in the UE-initiated beam report is complete. UE-initiated beam reports may indicate that the information contained in the UE-initiated beam report is incomplete.

[0671] The UE may determine or select which cell's information to report in a (truncated) UE-initiated beam report based on the priority of the cell. For example, the priority may be associated with the serving cell index of the serving cell. The UE may include the information of the serving cell in ascending or descending order of the serving cell index. A special cell (SpCell) (e.g., a PCell or a primary and secondary cell (PSCell)) may have a higher priority than an SCell.

[0672] For another example, the priority may be associated with the type of the cell. For example, the UE may prioritize the reporting information of the serving cell over the reporting information of candidate cells or neighboring cells. Alternatively, in some embodiments, the UE may prioritize the reporting information of candidate cells or neighboring cells over the reporting information of the serving cell.

[0673] The UE may determine or select which cell's information to report in a (truncated) UE-initiated beam report based on the quality associated with the cell. If the quality associated with the first cell is higher than the quality associated with the second cell (if or when the UL grant cannot accommodate all the information associated with the triggered user equipment initiated (UEI) beam reports of all cells), then the information of the first (candidate) cell may be prioritized (to be included in the (truncated) UE-initiated beam report) over the information of the second (candidate) cell. Alternatively, in some embodiments, if the quality associated with the first cell is lower than the quality associated with the second cell, then the information of the first cell may be prioritized (to be included in the UE-initiated beam report) over the information of the second cell. The quality may be the quality of the cell. Alternatively, in some embodiments, the quality may be the quality of the beam of the cell. The beam may have the highest quality (among all the beams of the cell). The beam may be a candidate beam. The beam may not be an active beam. Alternatively, in some embodiments, the beam may be an active beam.

[0674] Additionally and / or alternatively, the UE may determine or select which information of the cell to report based on the quality associated with the beam (associated with the information). The UE may prioritize the information of the first (candidate) beam over the information of the second beam if the quality of the first (candidate) beam is higher than the quality of the second beam (if or when the UL grant cannot accommodate all the information associated with the triggered UEI beam reports of all cells).

[0675] The information of the cell may include the beam and / or (beam) quality value associated with the cell.

[0676] Figure 19 An example of a UE-initiated beam report is shown. The report may include a bitmap (e.g., 8-bit), which includes whether to report the information of the cell and / or whether the corresponding cell has triggered a UE-initiated beam report. For example, a bit equal to '1' for cell 0 indicates that cell 0 has experienced a UE-initiated beam report / experienced a beam quality problem. A bit equal to '0' for cell 1 indicates that cell 1 is not associated with the triggered UE-initiated beam report. The report may contain the beam information of the reported cell. The information may be included in descending order of cell index or cell id (physical cell id). The report may include a field (e.g., the E field) indicating whether the report includes other information of the cell. For example, the E field set to '1' in the second octet indicates that the next octet is for the information of the same cell (e.g., another candidate beam). The V field may indicate whether to report the quality value. For example, the V field set to '1' indicates that the quality value for this beam is reported in the next octet.

[0677] Figure 20Another example is shown. A UE-initiated beam report may include a cell index (e.g., serving cell index or candidate cell index) or an id (e.g., physical cell id). The report may include a cell type (e.g., serving cell, candidate cell, or neighbor cell). The network may determine how to interpret the cell index / id field based on the cell type. The report may include a BWP id associated with the reported beam. The report may contain beam information associated with (only) one cell. Alternatively, in some embodiments, the report may be extended to include beam information for multiple cells.

[0678] Figure 21 An example of determining the information to be reported in a (truncated) UE-initiated beam report is shown. The UE may be configured with a serving cell and two candidate cells A and B. The quality of the serving cell (e.g., the beam quality of the currently active beam) is degrading, and events are satisfied for candidate cells A and B (e.g., serving beam quality < candidate beam quality + offset (over a certain time period)). The UE may trigger a UE-initiated beam report for candidate cells A and B. The UE may receive a UL grant for transmitting the UEI beam report (or a configured UL grant is available). The UL grant is not sufficient to accommodate all the information including the beam values and beam IDs (e.g., synchronization signal block (SSB) index) for candidate cells A and B. The UE may determine to prioritize candidate cell A information based on the cell quality of candidate cell A being higher than that of candidate cell B. Alternatively and / or additionally, the UE may determine to prioritize candidate beam A over candidate beam B based on the quality of beam A being higher than that of beam B.

[0679] Prioritize UE-initiated beam reports over BFR MAC CE

[0680] Additionally and / or alternatively, when assembling the MAC PDU, the UE may prioritize including the UE-initiated beam report (associated with a cell) in the MAC PDU over including the BFR MAC CE (associated with the cell). Alternatively, in some embodiments, the UE may prioritize including the BFR MAC CE in the MAC PDU over the UE-initiated beam report. Additionally and / or alternatively, the UE may not include both the UE-initiated beam report and the BFR MAC CE (for the same cell) in one MAC PDU.

[0681] Additionally and / or alternatively, when assembling the MAC PDU, the UE may prioritize including a UE-initiated beam report (associated with a candidate cell, e.g., for LTM) in the MAC PDU over including a BFR MAC CE (associated with the serving cell). Alternatively, in some embodiments, when assembling the MAC PDU, the UE may prioritize including a BFR MAC CE (associated with the serving cell) over including a UE-initiated beam report (associated with a candidate cell, e.g., for LTM). Additionally and / or alternatively, the UE may prioritize including a BFR MAC CE (associated with the serving cell) in the MAC PDU over a UE-initiated beam report (associated with the serving cell).

[0682] If or when (at least) there are no available UL resources for the transmission of a report, the UE may trigger an SR for a UE-initiated beam report (requesting UL resources for it). Alternatively, in some embodiments, (even if or) when (at least) there are no available UL resources for the transmission of a report, the UE may not trigger an SR for a UE-initiated beam report (requesting UL resources for it). The SR may be associated with the same SR configuration as the SR for beam failure recovery (e.g., SCell BFR MAC CE). It may not be allowed for the SR to be associated with an SR configuration different from the SR for beam failure recovery (e.g., SCell BFR MAC CE). Additionally and / or alternatively, the SR configuration for a UE-initiated beam report may be different from the SR configuration for beam failure recovery (e.g., SCell BFR MAC CE). The SR configuration for a UE-initiated beam report may be configured by the network. Alternatively, in some embodiments, the SR configuration for a UE-initiated beam report may be associated with a fixed id.

[0683] Additionally and / or alternatively, the UE may indicate the (buffer) size required for a UE-initiated beam report in a buffer status report (BSR).

[0684] DRX active time

[0685] Additionally and / or alternatively, when sending or transmitting a UE-initiated beam report associated with the serving cell (on the PUSCH or PUCCH to the network) and until a condition (any of them) is met, the UE may remain in the DRX on-duration or consider itself to be in DRX-on. Additionally and / or alternatively, when triggering a UE-initiated beam report associated with the serving cell and until a condition (any of them) is met, the UE may remain in the DRX on-duration or consider itself to be in DRX-on. The condition may include one or more of the following:

[0686] - Initiate or complete a beam change procedure; and / or

[0687] The beam change procedure may receive TCI state activation / deactivation MAC CE. The beam change procedure may receive a configuration for reconfiguring the TCI state for the serving cell. The beam change procedure may be used for one, part, or all of the serving cells;

[0688] - (All) serving cells are deactivated; and / or

[0689] A serving cell may be deactivated based on an SCell activation / deactivation MAC CE. A serving cell may be deactivated based on the expiration of an sCellDeactivationTimer associated with the serving cell. A serving cell may be deactivated based on a secondary cell group (SCG) deactivation;

[0690] - Initiate a beam failure recovery procedure for (all) serving cells; and / or

[0691] A beam change procedure may be initiated when a BFR associated with a serving cell is triggered;

[0692] - Receive an LTM cell handover command MAC CE that reconfigures or changes (all or some) serving cells with synchronization.

[0693] The DRX on-duration of the UE may include the time between the timing when a UE-initiated beam report is transmitted for a cell or afterwards and a second timing when a signaling for changing the beam (to be activated / deactivated) for the cell is received.

[0694] Additionally and / or alternatively, the DRX on-duration of the UE may include the time between the timing when a UE-initiated beam report is triggered for a cell or afterwards and a second timing when a signaling for changing the beam (to be activated / deactivated) for the cell is received.

[0695] Additionally and / or alternatively, when transmitting or sending a UE-initiated beam report associated with a candidate cell (on a PUSCH or PUCCH to the network) and until a condition (any one of them) is met, the UE may remain in the DRX on-duration or consider itself to be in DRX-on. Additionally and / or alternatively, when a UE-initiated beam report associated with a candidate cell is triggered and until a condition (any one of them) is met, the UE may remain in the DRX on-duration or consider itself to be in DRX-on. The condition may include one or more of the following:

[0696] - (All) serving cells associated with (one, some, or all of) the candidate cells are deactivated; and / or

[0697] The serving cell can be deactivated based on SCell activation / deactivation MAC CE. The serving cell can be deactivated based on the expiration of the sCellDeactivationTimer associated with the serving cell. The serving cell can be deactivated based on SCG deactivation;

[0698] The serving cell and the candidate cell can be associated with the same cell group, e.g., the master cell group (MCG) or SCG. For example, the serving cell can belong to the SCG and the candidate cell can be configured to replace the serving cell belonging to the SCG;

[0699] - Receiving a MAC CE for a synchronized reconfiguration or an LTM cell handover command indicating one of the candidate cells;

[0700] The synchronized reconfiguration or the LTM cell handover command MAC CE is to change the SpCell (e.g., the PCell or the PSCell) to one of the candidate cells.

[0701] The DRX on-duration of the UE can include the time between the timing when a UE-initiated beam report is transmitted for a cell or afterwards and a second timing when a signaling for changing the serving cell to the cell is received.

[0702] Additionally and / or alternatively, the DRX on-duration of the UE can include the time between the timing when a UE-initiated beam report is triggered for a cell or afterwards and a second timing when a signaling for changing the serving cell to the cell is received.

[0703] Various examples and embodiments of the present invention are described below. For the methods, alternatives, concepts, examples and embodiments detailed above and herein, the following aspects and embodiments are possible.

[0704] The UE-initiated beam report can be a CSI report. The UE-initiated beam report can be an event-driven beam report.

[0705] The UE-initiated beam report can be triggered or initiated in response to meeting one or more conditions or events.

[0706] The one or more conditions or events can include conditions associated with beam quality. For example, the condition can be that the quality of the (currently) active beam is lower than or equal to a threshold. Additionally and / or alternatively, the condition can be that the quality of the candidate beam is higher than or equal to a threshold. The one or more conditions can be associated with or based on a measurement report trigger event. Additionally and / or alternatively, the condition or event can be that the quality of the (currently) active beam is lower than the quality of the candidate beam by a certain offset.

[0707] Additionally and / or alternatively, the condition may include that the candidate beam quality is higher than or equal to the (current) active beam quality (within a certain time period).

[0708] The (current) active beam may be associated with the serving cell.

[0709] The candidate beam may be associated with a candidate cell.

[0710] The UE-initiated beam report may include determining whether to trigger the report based on at least the measured beam quality.

[0711] The beam quality may include RSRP, RSRQ, RSSI, and / or SINR associated with the beam.

[0712] The UE-initiated beam report may include the (reported) trigger.

[0713] The UE-initiated beam report may include triggering and / or transmitting an SR.

[0714] The UE-initiated beam report may include initiating a random access procedure.

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

[0716] The UE-initiated beam report may include transmitting the beam report to the network.

[0717] The UE-initiated beam report may be initiated and / or configured for the serving cell. Additionally and / or alternatively, the UE-initiated beam report may be initiated and / or configured for a candidate cell or a non-serving cell.

[0718] The UE-initiated beam report may be an L1 measurement report triggered by an event associated with LTM.

[0719] The UE-initiated beam report may include a trigger to cancel the beam report.

[0720] The UE may cancel the UE-initiated beam report in response to the initiation of the first one or more procedures.

[0721] The UE may cancel the UE-initiated beam report in response to the confirmation of the beam report from the network. The confirmation may be a new transmitted UL grant associated with the hybrid automatic repeat request (HARQ) process used to transmit the beam report. The confirmation may be a beam activation / deactivation MAC CE. Additionally and / or alternatively, the UE may cancel the (cell-associated) UE-initiated beam report in response to transmitting the corresponding UE-initiated beam report (report information associated with the cell).

[0722] When canceling or stopping the UE-initiated beam report, the UE may stop the corresponding procedures (mentioned above) included in the UE-initiated beam report.

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

[0724] The cancellation or stop of the UE-initiated beam report may stop the random access procedure. Additionally and / or alternatively, the cancellation or stop of the UE-initiated beam report may include stopping one or more timers associated with the UE-initiated beam report (e.g., timetotrigger for beam reporting or timers associated with the random access procedure and / or associated with SR).

[0725] The cancellation or stop of the UE-initiated beam report for a cell may include not including or reporting (beam) information associated with the cell in the UE-initiated beam report.

[0726] The cancellation or stop of the UE-initiated beam report for a cell may include (re)starting or resetting or stopping a timer or counter associated with the UE-initiated beam report for the cell.

[0727] A timer or counter may be used or configured to trigger or prohibit the UE-initiated beam report for a cell.

[0728] The UE may be configured with measurement objects associated with the UE-initiated beam report.

[0729] The measurement objects may include the serving cell and / or non-serving cells.

[0730] The measurement objects may be associated with SSBs and / or channel state information reference signals (CSI-RS) associated with the serving cell and / or non-serving cells.

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

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

[0733] To prioritize the first UE-initiated beam report over the second UE-initiated beam report, the UE may cancel the trigger associated with the second UE-initiated beam report (when or if (at least) the UE triggers the first UE-initiated beam report), and / or the UE does not trigger the second UE-initiated beam report.

[0734] To prioritize the beam report initiated by a first UE over the beam report initiated by a second UE, the UE may include, in the MAC PDU (when assembling the MAC PDU), the beam report initiated by the first UE (the UE-initiated beam report associated therewith), and then include the beam report initiated by the second UE (the UE-initiated beam report associated therewith). To prioritize the beam report initiated by a first UE over the beam report initiated by a second UE, if or when (at least) the MAC PDU cannot accommodate both the beam reports (reports) initiated by the first and second UEs, the UE may include, in the MAC PDU, the beam report initiated by the first UE (the UE-initiated beam report associated therewith) and may not include the beam report initiated by the second UE (the UE-initiated beam report associated therewith).

[0735] Prioritization will determine the order or priority of different contents (e.g., different MAC CEs) to be included in the MAC PDU. If (at least) the remaining space of the MAC PDU is insufficient, the content with a lower priority may not be included in the MAC PDU.

[0736] The reporting and the first one or more procedures may overlap in the time domain.

[0737] The reporting and the procedures may be associated with the same serving cell and / or the same MAC entity and / or the same cell group (e.g., MCG or SCG).

[0738] The beam may be replaced by or referred to as an SSB (associated with an SSB index or an SSB resource indicator, a synchronization signal (SS) / physical broadcast channel (PBCH) resource block indicator (SSBRI)), a CSI-RS, and / or a (DL or UL) TCI state.

[0739] The cell may be a serving cell, a candidate cell, and / or an adjacent cell.

[0740] The candidate cell may be an LTM candidate cell. The adjacent cell may be a cell associated with a measurement object. The candidate cell and the adjacent cell are not serving cells.

[0741] All concepts, examples, and embodiments above and herein may be combined into new concepts.

[0742] Various examples and embodiments of the present invention are described below. For the methods, alternatives, concepts, examples, and embodiments detailed above and herein, the following aspects and embodiments are possible.

[0743] See Figure 22, for such and other concepts, systems, and methods of the present invention, method 1000 for a UE in a wireless communication system includes: determining whether to trigger a UE-initiated beam report based on at least whether there is an ongoing first procedure in response to meeting the conditions for the UE-initiated beam report (step 1002).

[0744] In various embodiments, if or when there is no ongoing first procedure, the UE triggers a UE-initiated beam report in response to meeting the conditions for the UE-initiated beam report.

[0745] In various embodiments, if or when there is at least one ongoing first procedure, the UE does not trigger a UE-initiated beam report in response to meeting the conditions for the UE-initiated beam report.

[0746] In various embodiments, the first procedure is a random access procedure.

[0747] In various embodiments, a random access procedure is initiated in response to beam failure recovery.

[0748] In various embodiments, the first procedure is a reconfiguration with a synchronization procedure.

[0749] In various embodiments, the UE-initiated beam report is associated with a cell.

[0750] In various embodiments, if or when there is no ongoing first procedure associated with the serving cell, the UE triggers a UE-initiated beam report associated with the serving cell in response to meeting the conditions for the UE-initiated beam report.

[0751] Return reference Figure 3 and 4 , in one or more embodiments from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) determine whether to trigger a UE-initiated beam report based on at least whether there is an ongoing first procedure in response to meeting the conditions for the UE-initiated beam report. Additionally, the CPU 308 may execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0752] See Figure 23 , for such and other concepts, systems, and methods of the present invention, method 1010 for a UE in a wireless communication system includes triggering a UE-initiated beam report for a cell in response to meeting the conditions for the UE-initiated beam report (step 1012), and canceling the UE-initiated beam report for the cell in response to the initiation or reception of a first procedure associated with the cell (step 1014).

[0753] In various embodiments, the first procedure includes a random access procedure.

[0754] In various embodiments, a random access procedure is initiated in response to beam failure recovery of a cell.

[0755] In various embodiments, the first procedure includes a reconfiguration with a synchronization procedure.

[0756] In various embodiments, the first procedure includes receiving a TCI status or beam activation / deactivation MAC CE indicating a TCI status / beam activation / deactivation associated with the cell.

[0757] In various embodiments, the first procedure includes at least cell deactivation of the cell.

[0758] In various embodiments, the first procedure includes a MAC reset.

[0759] In various embodiments, the first procedure includes triggering a (SCell) BFR of the cell.

[0760] Return reference Figure 3 and 4 , in one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) trigger a UE-initiated beam report of a cell in response to satisfaction of conditions for the UE-initiated beam report; and (ii) cancel the UE-initiated beam report of the cell in response to the initiation or reception of a first procedure associated with the cell. Additionally, the CPU 308 may execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0761] Refer to Figure 24 , for such and other concepts, systems, and methods of the present invention, a method 1020 for a UE in a wireless communication system includes triggering a UE-initiated beam report of a cell in response to satisfaction of conditions for the UE-initiated beam report (step 1022), and assembling and transmitting the UE-initiated beam report to the network in response to the triggered UE-initiated beam report (step 1024).

[0762] In various embodiments, the UE-initiated beam report indicates a cell index associated with the cell.

[0763] In various embodiments, the UE-initiated beam report indicates that the cell has been reported or the UE-initiated beam report has been triggered.

[0764] In various embodiments, the UE-initiated beam report indicates beam information of the cell.

[0765] In various embodiments, the beam information includes a beam index or a TCI state id associated with a cell.

[0766] In various embodiments, the UE-initiated beam report includes beam information of a cell based on a cell index in ascending or descending order.

[0767] Return reference Figure 3 and 4 and, in one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) trigger a UE-initiated beam report of a cell in response to a condition for the UE-initiated beam report being satisfied; and (ii) assemble and transmit the UE-initiated beam report to the network in response to the triggered UE-initiated beam report. In addition, the CPU 308 may execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0768] See Figure 25 and, regarding such and other concepts, systems, and methods of the present invention, a method 1030 for a UE in a wireless communication system includes triggering a UE-initiated beam report associated with a plurality of candidate cells (step 1032), and determining whether to prioritize transmission of information of the candidate cell via an UL grant based at least on a quality associated with the candidate cell in the plurality of candidate cells when the UL grant cannot accommodate all one or more information associated with the plurality of candidate cells for the UE-initiated beam report (step 1034).

[0769] In various embodiments, if or when the quality associated with a first candidate cell is higher than the quality associated with a second candidate cell, the UE prioritizes first information associated with the first candidate cell over second information associated with the second candidate cell.

[0770] In various embodiments, the method further includes determining whether to prioritize information of a beam associated with a candidate cell based on the quality of the beam.

[0771] In various embodiments, if or when the quality of a first beam is higher than the quality of a second beam, the UE prioritizes first information of the first beam (associated with a first candidate cell) over second information of the second beam (associated with a first candidate cell or a second candidate cell).

[0772] In various embodiments, the first beam and the second beam are associated with different candidate cells or the same candidate cell.

[0773] In various embodiments, the quality associated with a candidate cell is the quality of the beam associated with the candidate cell.

[0774] In various embodiments, the beam among one or more beams of a candidate cell is associated with the highest quality.

[0775] In various embodiments, when the UL grant cannot accommodate all of the one or more information, the UE performs UE-initiated beam reporting with truncated UE-initiated beam reporting.

[0776] In various embodiments, the information indicates at least one of one or more beams, the quality of the one or more beams, or a cell index.

[0777] In various embodiments, the UE performs UE-initiated beam reporting via a MAC CE.

[0778] In various embodiments, the MAC CE indicates that the information contained in the MAC CE is incomplete.

[0779] In various embodiments, UE-initiated beam reporting is triggered in response to meeting one or more conditions, where the one or more conditions include at least one of the following: the quality of the currently active beam is lower than a threshold; and / or the quality of a candidate beam is higher than a threshold.

[0780] Return reference Figure 3 and 4 , in one or more embodiments from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) trigger UE-initiated beam reporting associated with a plurality of candidate cells; and (ii) when the UL grant cannot accommodate all of the one or more information associated with the plurality of candidate cells for UE-initiated beam reporting, determine whether to transmit the information of the candidate cell preferentially via the UL grant based at least on the quality associated with the candidate cell among the plurality of candidate cells. Additionally, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or herein.

[0781] See Figure 26, for such and other concepts, systems, and methods of the present invention, method 1040 for a UE in a wireless communication system includes triggering UE-initiated beam reporting associated with one or more candidate cells (step 1042), and determining whether to prioritize transmitting the information via a UL grant based at least on the quality of the beam associated with the information in the one or more information when the UL grant cannot accommodate all of the one or more information associated with the one or more candidate cells for the UE-initiated beam reporting (step 1044).

[0782] In various embodiments, if or when the quality of a first beam is higher than the quality of a second beam, the UE prioritizes the first information of the first beam over the second information of the second beam.

[0783] In various embodiments, if or when the quality associated with a first candidate cell is higher than the quality associated with a second candidate cell, the UE prioritizes the first information associated with the first candidate cell over the second information associated with the second candidate cell.

[0784] In various embodiments, the quality associated with a candidate cell is the quality of the beam associated with the candidate cell.

[0785] In various embodiments, when the UL grant cannot accommodate all of the one or more information, the UE performs UE-initiated beam reporting with a truncated UE-initiated beam report.

[0786] In various embodiments, the information indicates at least one of one or more beams, the quality of the one or more beams, or a cell index.

[0787] In various embodiments, the UE performs UE-initiated beam reporting via a MAC CE.

[0788] In various embodiments, the MAC CE indicates that the information contained in the MAC CE is incomplete.

[0789] Return reference Figure 3 and 4, in one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) trigger a UE-initiated beam report associated with one or more candidate cells; and (ii) determine whether to prioritize transmitting the information via a UL grant when the UL grant cannot accommodate all of the one or more information associated with the one or more candidate cells for the UE-initiated beam report, based at least on the quality of the beams associated with the information in the one or more information. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

[0790] Any combination of the concepts or teachings above or herein may be fully or partially combined together or formed into a new embodiment. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.

[0791] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein can be applied independently, individually, and / or together with multiple methods, alternatives, steps, examples, and embodiments combined together.

[0792] The various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art should understand that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in different ways. For example, any number of the aspects set forth herein can be used to implement an apparatus or practice a method. In addition, this apparatus can be implemented or this method can be practiced by using other structures, functionality, or structures and functionality in addition to or different from one or more of the aspects set forth herein. As examples of some of the above concepts, in some aspects, parallel channels can be established based on the pulse repetition frequency. In some aspects, parallel channels can be established based on the pulse position or offset. In some aspects, parallel channels can be established based on the time-hopping sequence. In some aspects, parallel channels can be established based on the pulse repetition frequency, pulse position or offset, and time-hopping sequence.

[0793] Those of ordinary skill in the art will appreciate that any of a variety of different technologies and techniques can be used to represent information and signals. By way of example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0794] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithmic steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., digital implementations, analog implementations, or combinations thereof, which may be designed using source coding or some other technique), various forms of program or design code with instructions (for convenience, which may be referred to herein as "software" or "software modules"), or combinations of both. To clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0795] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or in both cases. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0796] It should be understood that any particular order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process may be rearranged while remaining within the scope of the present disclosure. The appended method claims present elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0797] The steps of a method or algorithm described in connection with the various aspects disclosed herein can be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. Software modules (e.g., including executable instructions and related data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. The exemplary storage medium can be coupled to a machine, such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The exemplary storage medium can be integral with the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can reside as discrete components in a user device. Additionally, in some aspects, any suitable computer program product can include a computer-readable medium that includes code associated with one or more of the aspects of the present disclosure. In some aspects, the computer program product can include packaging material.

[0798] Although the invention has been described in connection with various aspects and examples, it should be understood that the invention is capable of further modification. This application is intended to cover any variations, uses, or adaptations of the invention, which generally follow the principles of the invention and include such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains.

Claims

1. A method for a user equipment, characterized in that, Comprising: Triggering a beam report initiated by a user equipment associated with a plurality of candidate cells; And When an uplink grant cannot accommodate all one or more information associated with the plurality of candidate cells used for the beam report initiated by the user equipment, determining whether to preferentially transmit the information of the candidate cell via the uplink grant based on at least the quality associated with the candidate cell among the plurality of candidate cells.

2. The method according to claim 1, wherein If or when the quality associated with a first candidate cell is higher than the quality associated with a second candidate cell, the user equipment prioritizes first information associated with the first candidate cell over second information associated with the second candidate cell.

3. The method according to claim 1, characterized in that, Further comprising determining whether to prioritize the information of the beam based on the quality of the beam associated with the candidate cell.

4. The method according to claim 3, wherein If or when the quality of a first beam is higher than the quality of a second beam, the user equipment prioritizes first information of the first beam over second information of the second beam.

5. The method according to claim 4, characterized in that, The first beam and the second beam are associated with different candidate cells or the same candidate cell.

6. The method according to claim 1, characterized in that, The quality associated with the candidate cell is the quality of the beam associated with the candidate cell.

7. The method according to claim 6, characterized in that, The beam among one or more beams of the candidate cell is associated with the highest quality.

8. The method according to claim 1, wherein When the uplink grant cannot accommodate all the one or more information, the user equipment performs the beam report initiated by the user equipment with a truncated user equipment-initiated beam report.

9. The method according to claim 1, characterized in that, The information indicates at least one of one or more beams, the quality of the one or more beams, or a cell index.

10. The method according to claim 1, wherein The user equipment performs the beam report initiated by the user equipment via a media access control control element.

11. The method according to claim 10, wherein The media access control control element indicates that the information contained in the media access control control element is incomplete.

12. The method according to claim 1, wherein Triggering the beam report initiated by the user equipment in response to satisfying one or more conditions, where the one or more conditions include at least one of the following: The quality of the currently active beam is lower than a threshold; and / or The quality of a candidate beam is higher than a threshold.

13. A method for a user equipment, characterized in that, Comprising: Triggering a beam report initiated by a user equipment associated with one or more candidate cells; And When an uplink grant cannot accommodate all one or more information associated with the one or more candidate cells used for the beam report initiated by the user equipment, determining whether to preferentially transmit the information via the uplink grant based on at least the quality of the beam associated with the information among the one or more information.

14. The method according to claim 13, characterized in that, If or when the quality of a first beam is higher than the quality of a second beam, the user equipment prioritizes first information of the first beam over second information of the second beam.

15. The method according to claim 13, wherein If or when the quality associated with a first candidate cell is higher than the quality associated with a second candidate cell, the user equipment prioritizes first information associated with the first candidate cell over second information associated with the second candidate cell.

16. The method according to claim 15, characterized in that, The quality associated with the candidate cell is the quality of the beam associated with the candidate cell.

17. The method according to claim 13, characterized in that When the uplink grant cannot accommodate all of the one or more information, the user equipment performs the user equipment initiated beam report with a truncated user equipment initiated beam report.

18. The method according to claim 13, wherein The information indicates at least one of one or more beams, the quality of the one or more beams, or a cell index.

19. The method according to claim 13, characterized in that The user equipment performs the user equipment initiated beam report via a media access control control element, and / or the media access control control element indicates that the information contained in the media access control control element is incomplete.

20. A user equipment, characterized in that, Comprising: a memory; and a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: trigger a user equipment initiated beam report associated with a plurality of candidate cells; and when the uplink grant cannot accommodate all of the one or more information associated with the plurality of candidate cells for the user equipment initiated beam report, determine whether to preferentially transmit the information of the candidate cell via the uplink grant based at least on the quality associated with the candidate cell among the plurality of candidate cells.

Images