Method and apparatus for user equipment trigger reporting in wireless communication system

Abstract

A method and apparatus for user equipment triggering reporting in a wireless communication system are provided, comprising: receiving a configuration of at least one condition for triggering reporting by a user equipment; receiving a downlink signal indicating at least one joint or downlink transmission configuration indicator state, wherein the at least one joint or downlink transmission configuration indicator state is associated with the first reference signal; and triggering a report based on satisfying a first condition of the at least one condition, the first condition comprising: L1-Reference Signal Received Power of the one or more candidate beams is better than L1-Reference Signal Received Power of the current beam by an offset, and the L1-Reference Signal Received Power of the one or more candidate beams is an offset greater than the L1-Reference Signal Received Power of the current beam. The number of instances in which the L1-Reference Signal Received Power of one or more candidate beams is better than the L1-Reference Signal Received Power of the current beam by an offset exceeds or reaches a maximum number, and the user equipment determines the L1-Reference Signal Received Power of the current beam based on the measurement of the first reference signal.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 525,502, filed on July 7, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for transmitting user equipment triggered reports in a wireless communication system. Background Art

[0004] With the rapid growth of 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) packets. This IP packet communication can provide IP-bearing voice, multimedia, multicast and on-demand communication services for users of mobile communication devices.

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

[0006] Methods, systems and devices for transmitting user equipment (UE) triggered reports in a wireless communication system are provided. In various embodiments, the method of the UE includes: receiving a configuration of at least one condition for triggering a report by the UE, wherein the report is an L1 report or a medium access control (MAC) control element (CE); receiving a downlink signal indicating at least one joint or downlink (DL) transmission configuration indicator (TCI) state, wherein the at least one joint or DL ​​TCI state is associated with a first reference signal (RS); and triggering the report based on satisfying a first condition of the at least one condition, wherein: the first condition includes: the L1-reference signal received power (RSRP) of one or more candidate beams is better than the L1-RSRP of the current beam by an offset, or the number of instances in which the L1-RSRP of the one or more candidate beams is better than the L1-RSRP of the current beam by an offset exceeds or reaches a maximum number, and the UE determines the L1-RSRP of the current beam based on the measurement of the first RS and determines the L1-RSRP of the one or more candidate beams based on the measurement of one or more candidate RSs. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0010] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code;

[0011] Figure 5 It is from 3GPP TS 38.300V17.2.0(2022-09) Figure 5 .1-2: Reproduction of uplink-downlink timing relationship;

[0012] Figure 6 It is from 3GPP TS 38.321V17.3.0(2022-12) Figure 6 .1.3.47-1: Unify the reappearance of TCI state activation / deactivation of MAC CE 1;

[0013] Figure 7It is from 3GPP TS 38.321V17.3.0(2022-12) Figure 6 .1.3.15-1: Reproduction of TCI status indication for UE-specific PDCCH MAC CE;

[0014] Figure 8 It is from 3GPP TS 38.321V17.3.0(2022-12) Figure 6 .1.3.44-1: Reproduction of enhanced TCI status indication for UE-specific PDCCH MAC CE;

[0015] Fig. 9 is an example diagram showing that once a condition for triggering UE reporting is met, a UE transmits a UE-triggered report to a gNB according to an embodiment of the present invention;

[0016] Fig.10 is an example diagram showing that a UE triggers a first (type of) report when both the quality associated with a candidate RS and the quality associated with an indicated RS are satisfied according to an embodiment of the present invention;

[0017] Fig.11 is an example diagram showing that RS1 on cell 1 corresponds to an indicated TCI state and the UE has or is configured with RS2-7 on cells 1, 1, 2, 3, 4, 5 respectively according to an embodiment of the present invention;

[0018] Fig.12 is an example diagram showing that each RS may have associated parameters related to a first (type of) report and / or parameters related to a second (type of) report according to an embodiment of the present invention;

[0019] Fig.13 is an example diagram showing that a UE may be configured with two lists of RSs according to an embodiment of the present invention;

[0020] Fig.14 is an example diagram showing that a UE triggers a report based on a comparison based on a beam pair according to an embodiment of the present invention;

[0021] Fig.15 is a flow chart of a method of a UE according to an embodiment of the present invention, the method comprising: receiving one or more configurations associated with trigger conditions, preferably performing measurements on a first RS set and a second RS set, triggering one or more reports associated with a first serving cell when at least one trigger condition is met, and transmitting the one or more reports to a network node;

[0022] Fig.16is a flow chart of a method of a UE according to an embodiment of the present invention, the method comprising: transmitting a network-based report or a UE-triggered report to a network node in a timing, and performing a prohibition / skipping mechanism for a UE-triggered report associated with at least one triggering condition when at least one triggering condition is satisfied during an interval relative to the timing;

[0023] Fig.17 is a flow chart of a method of a UE according to an embodiment of the present invention, the method comprising: triggering a first report for a target, transmitting a second report in a timing, determining whether to perform a prohibition / skip mechanism for the first report based on whether the first report and the second report are associated with the same target, and transmitting the first triggered report to a network node based on the determination of different targets;

[0024] Fig.18 It is a flowchart of a method of a UE according to an embodiment of the present invention, the method comprising: receiving a configuration of at least one condition for triggering a report by the UE, receiving a downlink signal indicating at least one joint or DL ​​TCI state, and triggering a report based on satisfying a first condition of the at least one condition. DETAILED DESCRIPTION

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

[0026] The exemplary wireless communication systems and devices described below employ wireless communication systems that support 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 Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0027] In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by a consortium named "3rd Generation Partnership Project" referred to herein as 3GPP, including: [1] 3GPP TS 38.300 V17.2.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 17); [2] Chair's Note RAN1#111eom3; [3] Chair's Note RAN1#112eom3; [4] R2-2213332 38.300 Operational CR for Introduction of Further Mobility Enhancements for NR; [5] 3GPP TS 38.331 V17.3.0 (2022-12) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Release 17); [6] 3GPP TS 38.214 V17.3.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 17); [7] Chair's Note RAN1#112b-e eom3; [8] Chair's Note RAN1#113eom3; [9] 3GPP TS 38.321 V17.3.0 (2022-12) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) Protocol Specification (Release 17); and

[10] 3GPP TS 38.212 V17.3.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and Channel Coding (Release 17). The standards and documents listed above are hereby expressly and completely incorporated herein by reference in their entirety.

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

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

[0030] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Additionally, an access network that transmits to access terminals randomly dispersed throughout its coverage area using beamforming may cause less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals via a single antenna.

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

[0032] Figure 2 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 number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0033] In one embodiment, each data stream is transmitted through a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0034] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for the data stream to provide modulation symbols. Instructions executed by processor 230 may determine the data rate, coding, and modulation for each data stream. Memory 232 is coupled to processor 230.

[0035] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0036] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and up-converts) the analog signals to provide a modulated signal suitable for transmission via a MIMO channel. T The antennas 224a to 224t transmit N signals from transmitters 222a to 222t. T a modulated signal.

[0037] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

[0038] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R received symbol streams to provide N TThe RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0039] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

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

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

[0042] The memory 232 may be used to temporarily store some buffer / calculated data from 240 or 242 via the processor 230, store some buffer data from 212, or store some specific program codes. Also, the memory 272 may be used to temporarily store some buffer / calculated data from 260 via the processor 270, store some buffer data from 236, or store some specific program codes.

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

[0044] Figure 4 According to one embodiment of the present invention, Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connectivity.

[0045] For LTE, LTE-A or NR systems, the layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

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

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

[0048] In TS 38.300 ([1] 3GPP TS 38.300 V17.2.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN overall description; Stage 2 (Release 17)), the NR waveform, basic parameters and frame structure are described below.

[0049] The basic parameters are based on the exponentially scalable subcarrier spacing Δf=2 μ × 15kHz, where μ = {0, 1, 3, 4, 5, 6} for PSS, SSS and PBCH, and μ = {0, 1, 2, 3, 5, 6} for other channels. Normal CP is supported for all subcarrier spacings, and extended CP is supported for μ = 2. 12 consecutive subcarriers form a physical resource block (PRB). Up to 275 PRBs are supported on a carrier.

[0050] Table 5.1-1: Supported transmission basic parameters. A UE may be configured with one or more bandwidth parts on a given component carrier, of which only one may be in operation at a time.

[0051] μ <![CDATA[Δf=2 μ ·15[kHz]]]> CP Support for data Support for synchronization 0 15 normal yes yes 1 30 normal yes yes 2 60 Normal, Extended yes no 3 120 normal yes yes 4 240 normal no yes 5 480 normal yes yes 6 960 normal yes yes

[0052] The active bandwidth part defines the operating bandwidth of the UE within the operating bandwidth of the cell. For initial access and until configuration of the UE in the cell is received, the initial bandwidth part detected from the system information is used.

[0053] Downlink and uplink transmissions are organized into frames with 10 ms duration, consisting of ten 1 ms subframes. Each frame is divided into two equally sized half-frames of five subframes each. The slot duration is 14 symbols with normal CP and 12 symbols with extended CP, and varies in time with the subcarrier spacing used, so that there is always an integer number of slots in a subframe.

[0054] The timing advance TA is used to adjust the uplink frame timing relative to the downlink frame timing.

[0055] Figure 5 It is from 3GPP TS 38.300V17.2.0(2022-09) Figure 5 .1-2: Reproduction of uplink-downlink timing relationship.

[0056] Operation on both paired and unpaired spectrum is supported.

[0057] In [2] Moderator Notes RAN1#111eom3, relevant progress on mobility is cited below.

[0058] protocol

[0059] ● For L1 measurement reporting for Rel-18 L1 / L2 mobility, if UE event triggered reporting for L1 measurements is supported based on further study

[0060] - At least the following aspects can be considered

[0061] - How to define UE events and the exact definition of events,

[0062] - Report container

[0063] - Resource allocation / assignment for UE event-triggered reporting

[0064] - Necessity of indication to the gNB when a conditional UE event is met, and how to indicate

[0065] - the necessity to define the conditions for starting / stopping reporting,

[0066] - Contents of reports / report formats, PCI, RS ID, measurement results, etc.

[0067] -Interaction with filtered L1 measurements (if supported)

[0068] -Supports simultaneous configuration of any of UE event-triggered reporting and periodic / semi-persistent / aperiodic reporting, as well as solutions when both are configured.

[0069] - Report destination, whether the report is sent only to the serving cell or can be sent to one or more candidate cells.

[0070] -Benefits when it comes to L3 measurements

[0071] protocol

[0072] - For L1 measurement reports scheduled by gNB in ​​Rel-18 LTM, support reporting as UCI

[0073] -Supports semi-persistent reporting on PUSCH and aperiodic reporting on PUSCH

[0074] - For further study: Periodic and semi-persistent PUCCH

[0075] - In a single reporting instance, reports for intra-frequency and / or inter-frequency serving cells and candidate cells may be included.

[0076] protocol

[0077] - Beam indication timing for Rel-18 LTM,

[0078] - Support scenario 2: beam indication together with cell handover command,

[0079] - For Rel-17 unified TCI framework,

[0080] -Beam indication indicates the TCI status of each target serving cell

[0081] -For further study: Scenario 1: Beam indication before cell handover command

[0082] -For further study: Scenario 3: Beam indication after cell handover command

[0083] - For further study: Activation of TCI state of target serving and / or candidate cells.

[0084] protocol

[0085] Regarding the mechanism for obtaining the TA of the candidate cell in Rel-18 LTM, at least PDCCH-ordered RACH is supported.

[0086] ●PDCCH command triggered only by the source cell

[0087] Agreement (made in RAN1#110b-e)

[0088] Candidate cell TA acquisition before receiving a cell handover command is supported in L1 / L2 based mobility.

[0089] protocol

[0090] For RACH with PDCCH ordering in LTM, at least the following enhancements are supported

[0091] ● Introduce candidate cell indication and / or candidate cell RO in DCI

[0092] ● Provide configuration of RACH resources for candidate cells before PDCCH command

[0093] protocol

[0094] • TA update (ie re-acquisition of TA) for candidate cells may be triggered by the NW.

[0095] ● The same trigger mechanism is used again for initial TA acquisition, i.e., RACH triggered by PDCCH command in the candidate cell

[0096] In [3] Moderator Notes RAN1#112eom3, the following is cited regarding progress in mobility.

[0097] protocol

[0098] -RAN1 shares the same understanding with RAN2 regarding the protocol:

[0099] -Deliver LTM mobility trigger information in MAC CE

[0100] - The same MAC CE is used for LTM triggering.

[0101] protocol

[0102] - The agreement under RAN1#111 on scenario 2 (with beam indication of cell handover command) is further elaborated as follows:

[0103] -Deliver beam indication protocol for target cell in LTM triggered MAC CE for scenario 2

[0104] - At least for the beam indication based on the Rel-17 unified TCI framework contained in the cell handover command (i.e., scenario 2), the beam indication is applicable to the signal / channel that follows or is configured to follow the Rel-17 unified TCI at the target cell

[0105] -For further study: Beam indication for mTRP cases

[0106] protocol

[0107] For Rel-18 LTM, each candidate cell is configured with a random access preamble index and an indication of the RACH occasion with the associated SSB index.

[0108] protocol

[0109] The PDCCH order from the source cell contains an indication of the candidate cells.

[0110] ■ The reserved bits in DCI format 1_0 for PDCCH commands can be used for indication of cell identity

[0111] In [4] 3GPP R2-2213332 38.300 Operational CR for the introduction of further mobility enhancements for NR, L1 / L2 Triggered Mobility (LTM) is introduced:

[0112] 9.2.3.x L1 / L2 Triggered Mobility

[0113] 9.2.3.x.1 General

[0114] LTM is a procedure in which the gNB receives L1 measurement reports from the UE and based on them the gNB changes the serving cell of the UE via MAC CE. The gNB prepares one or more candidate cells and provides the candidate cell configurations to the UE via RRC messages. LTM cell switching is then triggered by the gNB selecting one of the candidate configurations as the target configuration for LTM. Candidate cell configurations can only be added, modified and released by the network via RRC signaling.

[0115] Editor's note: Whether some optimizations such as release should be applied later is for further study.

[0116] Editor's Note: Current options for configuring LTM candidate cells:

[0117] a. An RRCReconfiguration message for a candidate target cell

[0118] b. One CellGroupConfig IE for each candidate target cell

[0119] The following principles apply to LTM:

[0120] - The candidate cell configuration may be provided as a delta configuration on top of the reference configuration. The reference configuration is managed separately and the UE stores the reference configuration as a separate configuration.

[0121] - The user plane is continuous whenever possible (e.g., within a DU) without the need for reset to avoid data loss and additional delays in data recovery.

[0122] - Security is not updated in LTM.

[0123] - Subsequent LTM between candidates can be performed (ie, the UE does not release other candidate cell configurations after LTM triggering) without RRC reconfiguration.

[0124] LTM supports intra-gNB-DU and intra-gNB-CU inter-gNB-DU mobility. LTM also supports inter-frequency mobility, including mobility to an inter-frequency cell that is not the current serving cell. The following scenarios are supported:

[0125] - PCell change in non-CA scenario,

[0126] - PCell change in CA scenario without SCell change,

[0127] -PCell change and SCell change in CA scenario, including the following cases:

[0128] a) Target PCell / target SCell is not the current serving cell (CA to CA scenario with PCell change)

[0129] b) The target PCell is the current SCell

[0130] c) The target SCell is the current PCell.

[0131] - Dual connectivity scenarios, at least for PSCell change cases without MN participation, ie intra-SN.

[0132] Inter-cell beam management is also supported, but it is not considered a prerequisite for using LTM.

[0133] In [5] 3GPP TS 38.331 V17.3.0 (2022-12) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Release 17), the relevant information elements are quoted below.

[0134] -CondReconfigToAddModList

[0135] The IE CondReconfigToAddModList refers to the list of conditional reconfigurations to be added or modified, with for each entry a condReconfigld and the associated condExecutionCond / condExecutionCondSCG and condRRCReconfig.

[0136] CondReconfigToAddModList Information Element

[0137] --ASN1START

[0138] --TAG-CONDRECONFIGTOADDMODLIST-START

[0139] CondReconfigToAddModList-r16::=SEQUENCE(SIZE(1..maxNrofCondCells-r16))OF CondReconfigToAddMod-r16

[0140] CondReconfigToAddMod-r16::=SEQUENCE{

[0141]

[0142] -CSI-MeasConfig

[0143] The IE CSI-MeasConfig is used to configure the CSI-RS (reference signal) belonging to the serving cell in which the CSI-MeasConfig is contained, the channel state information report to be transmitted on the PUCCH on the serving cell in which the CSI-MeasConfig is contained, and the channel state information report on the PUSCH triggered by the DCI received by the serving cell in which the CSI-MeasConfig is contained. See also TS 38.214

[19] clause 5.2.

[0144] CSI-MeasConfig Information Elements

[0145]

[0146]

[0147]

[0148] -CSI-ResourceConfig

[0149] IE CSI-ResourceConfig defines a set of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and / or CSI-SSB-ResourceSet.

[0150] CSI-ResourceConfig Information Element

[0151]

[0152]

[0153]

[0154] -CSI-RS-ResourceConfigMobility

[0155] The IE CSI-RS-ResourceConfigMobility is used to configure CSI-RS-based RRM measurements.

[0156] -CSI-SSB-ResourceSet

[0157] IE CSI-SSB-ResourceSet is used to configure a SS / PBCH block resource set referring to the SS / PBCH as indicated in ServingCellConfigCommon and ServingCellConfig.

[0158] CSI-SSB-ResourceSet information element

[0159]

[0160]

[0161] -NZP-CSI-RS-Resource

[0162] The IE NZP-CSI-RS-Resource is used to configure the non-zero power (NZP) CSI-RS transmitted in the cell containing the IE, which the UE can be configured to measure (see TS 38.214

[19] , clause 5.2.2.3.1). Configuration changes between periodic, semi-persistent or aperiodic of NZP-CSI-RS-Resource are not supported without release and addition.

[0163] NZP-CSI-RS-Resource information element

[0164]

[0165]

[0166] -NZP-CSI-RS-ResourceSet

[0167] IE NZP-CSI-RS-ResourceSet is a set of non-zero power (NZP) CSI-RS resources (their IDs) and set specific parameters.

[0168] NZP-CSI-RS-ResourceSet information element

[0169]

[0170]

[0171]

[0172] -TCI-State IE TCI-State associates one or two DL reference signals with the corresponding quasi-colocation (QCL) type.

[0173] TCI-State Information Element

[0174]

[0175]

[0176] In [6] 3GPP TS 38.214 V17.3.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 17), the TCI state related details are quoted below.

[0177] 5.1.5 Quasi-co-location of antenna ports

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

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

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

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

[0182] - 'Type D': {Spatial Rx Parameters}

[0183] The UE may be configured with a list of up to 128 TCIState configurations within the higher layer parameter dl-OrJoint-TCIStateList in PDSCH-Config for providing quasi-co-located reference signals for the DM-RS of the PDSCH and the DM-RS of the PDCCH in a CC, for CSI-RS, and, where applicable, for determining the UL TX spatial filter for PUSCH and PUCCH resources and SRS in the CC based on dynamic grants and configured grants.

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

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

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

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

[0188] -CS-RNTI is used to scramble the CRC of the DCI

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

[0190] -RV=all '1'

[0191] -MCS=all '1'

[0192] -NDI=0

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

[0194] After the UE receives an initial higher layer configuration of dl-OrJoint-TCIStateList with more than one TCIState and before applying the indicated TCI state from the configured TCI state:

[0195] - The UE assumes that the DM-RS of the PDSCH and the DMR-S of the PDCCH and the CSI-RS to which the indicated TCI state is applied are quasi-co-located with the SS / PBCH block identified by the UE during the initial access procedure

[0196] After the UE receives an initial higher layer configuration of dl-OrJoint-TCIStateList with more than one TCIState or more than one UL-TCIState and before applying the indicated TCI state from the configured TCI state:

[0197] - The UE assumes, if applicable, that the UL TX spatial filters for PUSCH and PUCCH based on dynamic grants and configured grants, and for SRS to which the indicated TCI state is applied, are the same as the UL TX spatial filters used for PUSCH transmissions scheduled by the RAR UL grant during the initial access procedure

[0198] After the UE receives a higher layer configuration of a dl-OrJoint-TCIStateList with more than one TCIState as part of the reconfiguration procedure with synchronization as described in [12, TS 38.331], and before applying the indicated TCI from the configured TCI state:

[0199] - The UE assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, and the CSI-RS to which the indicated TCI state is applied, are quasi-co-located with the SS / PBCH blocks or the CSI-RS resources identified by the UE during the random access procedure initiated with the synchronized reconfiguration procedure as described in [12, TS 38.331].

[0200] After the UE receives a higher layer configuration with more than one TCIState or more than one UL-TCIState as part of the reconfiguration procedure with synchronization as described in [12, TS 38.331] and before applying the indicated TCI from the configured TCI state:

[0201] - The UE assumes, if applicable, that the UL TX spatial filters for PUSCH and PUCCH based on dynamic grants and configured grants, and for SRS to which the indicated TCI state is applied, are the same as the UL TX spatial filters used for PUSCH transmissions scheduled by the RAR UL grant during the initial access procedure initiated by the reconfiguration procedure with synchronization as described in [12, TS 38.331]

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

[0203] If the UE receives a higher layer configuration of dl-OrJoint-TCIStateList with a single TCIState or a single UL-TCIState that can be used as the indicated TCI state, the UE determines the UL TX spatial filter (if applicable) from the configured TCI states of PUSCH and PUCCH based on the dynamic grants and configured grants, and the SRS to which the indicated TCI state is applied.

[0204] When the UE is to transmit a PUCCH with HARQ-ACK information or a PUSCH with HARQ-ACK information corresponding to a DCI carrying a TCI state indication and without a DL assignment or corresponding to a PDSCH scheduled by a DCI carrying a TCI state indication, and if the indicated TCI state is different from the one previously indicated, the indicated DLorJointTCIState or UL-TCIstate shall apply starting from the first slot at least beamAppTime symbols after the last symbol of the PUCCH or PUSCH. The first slot and beamAppTime symbols are both determined on the active BWP with the smallest SCS among the active BWPs of the carrier to which the beam indication is applied.

[0205] If the UE is configured with pdsch-TimeDomainAllocationListForMultiPDSCH-r17, where one or more rows contain multiple SLIVs for PDSCH on the DL BWP of the serving cell, and the UE receives a DCI carrying a TCI-State indication and without DL assignment, the UE does not expect the number of SLIVs indicated by the DCI in the rows of pdsch-TimeDomainAllocationListForMultiPDSCH-r17 to be more than one.

[0206] If the UE is configured with SSB-MTC-AdditionalPCI and PDCCH-Config containing two different values ​​of coresetPoolIndex in ControlResourceSet, the UE receives an activation command for the CORESET associated with each coresetPoolIndex, as described in clause 6.1.3.14 of [10, TS 38.321] to map up to 8 TCI states to the codepoint of the DCI field 'Transmission Configuration Indication' in one CC / DL BWP. When a set of TCI state IDs is activated for a coresetPoolIndex, the activated TCI state corresponding to one coresetPoolIndex is associated with the serving cell physical cell ID, and the activated TCI state corresponding to another coresetPoolIndex may be associated with another physical cell ID.

[0207] When the UE supports two TCI states in the code point of the DCI field 'Transmission Configuration Indication', the UE may receive an activation command as described in clause 6.1.3.24 of [10, TS 38.321], the activation command being used to map up to 8 combinations of one or two TCI states to the code point of the DCI field 'Transmission Configuration Indication'. The UE is not expected to receive more than 8 TCI states in the activation command.

[0208] When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and when the number of code points S in the DCI field 'Transmission Configuration Indication' of DCI format 1_2 is less than the number of TCI code points activated by the activation command, as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321], only the first S activated code points are applied to DCI format 1_2.

[0209] When the UE is to transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, the indicated mapping between the TCI states and the code points of the DCI field 'Transmission Configuration Indication' shall be from , where μ is the SCS configuration for PUCCH, and It is for k mac subcarrier spacing configuration, where k has a value of 0 for frequency range 1, and mac Supplied by K-Mac, or if K-Mac is not provided, k mac= 0. If tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured as CORESET for scheduling PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL (if applicable), then after the UE receives the initial higher layer configuration of the TCI state and before the reception of the activation command, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the SS / PBCH blocks determined in the initial access procedure with respect to the qcl-Type set to 'Type A' and, if applicable, also with respect to the qcl-Type set to 'Type D'.

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

[0211] If the UE is configured with a NZP-CSI-RS-ResourceSet that is configured with the higher layer parameter repetition set to 'on', the UE may assume that the CSI-RS resources within the NZP-CSI-RS-ResourceSet described in clause 5.2.2.3.1 are transmitted with the same downlink spatial domain transmit filter, where the CSI-RS resources in the NZP-CSI-RS-ResourceSet are transmitted in different OFDM symbols. If repetition is set to 'off', the UE shall not assume that the CSI-RS resources within the NZP-CSI-RS-ResourceSet are transmitted with the same downlink spatial domain transmit filter.

[0212] 5.2.1.4.3L1-RSRP Report

[0213] For L1-RSRP calculation

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

[0215] - A UE may be configured with a CSI-RS resource configuration of up to 16 CSI-RS resource sets, each with up to 64 resources. The total number of different CSI-RS resources across all resource sets does not exceed 128.

[0216] 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 1 dB step size in the range [-140, -44] dBm, if the higher layer parameter nrofReportedRS is configured to be greater than one, or if the higher layer parameter groupBasedBeamReporting is configured to 'enabled', or if the higher layer parameter groupBasedBeamReporting-r17 is configured, 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 1 dB step size 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 reference to the maximum measured L1-RSRP value as part of the same L1-RSRP reporting instance with a 2 dB step size. The mapping between reported L1-RSRP values ​​and measured quantities is described in [11, TS 38.133].

[0217] 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 is present first.

[0218] If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive channel measurements for calculating the L1-RSRP value reported in uplink timeslot n only based on the SS / PBCH or NZP CSI-RS (defined in TS 38.211 [4]) associated with the CSI resource configuration that is no later than the CSI reference resource.

[0219] If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall only derive channel measurements for calculating the L1-RSRP reported in uplink timeslot n based on the SS / PBCH or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource configuration no later than the latest occasion of the CSI reference resource.

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

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

[0222] In [7] Moderator Notes RAN1#112b-e eom3, the following is explained.

[0223] protocol

[0224] - Alternative 2 for beam indication of target cell and TCI status activation of candidate cell (if supported),

[0225] -Alternative 1: By indicating the RS identifier, i.e. the mapping between the RS identifier and the Rel-17 unified TCI state is done by the UE

[0226] -Alternative 2: By indicating the Rel-17 TCI status index

[0227] protocol

[0228] From the RAN1 point of view, at least the following information may be included in the cell handover command delivered by the MAC CE:

[0229] -Information used to identify the target cell

[0230] - Details including number of bits are designed by RAN2

[0231] -TA related information (for details, refer to the discussion in AI9.10.2)

[0232] - 1 joint or 1 pair of UL and DL unified TCI state index for the target cell

[0233] - Note: Discussions on target SpCell are not excluded

[0234] protocol

[0235] For beam selection based on SSB-based L1-RSRP measurement reporting,

[0236] - Perform beam selection across L cells from the configured (or activated, if introduced) cells, i.e. M beams for each of the L cells

[0237] -For further study: How to select L cells and M beams per cell depends on the UE

[0238] - Report M x L ​​beams in a single reporting instance

[0239] - The maximum values ​​of M and L are based on UE capabilities, and at least M x L ​​= 4 are supported as UE capabilities. Other UE capabilities are subject to further study.

[0240] - Whether to allow UE to report less than M x L ​​beams is for further study

[0241] - The values ​​of M and L are configured to the UE in the report configuration

[0242] - For further study: Introduce the following configurability in report configuration

[0243] -1) Whether to always select the serving cell in the L cell selection performed by the UE, and applicable when the UE is configured with L>=2

[0244] -2) always select at least one of the inter-frequency cells in the L cell selection performed by the UE, and is applicable when the UE is configured with L>=2 and at least one of the inter-frequency cells

[0245] protocol

[0246] For Rel-17 unified TCI-based beam indication in Rel-18 LTM, at least Alternative 1 is supported:

[0247] ● Alternative 1: Receiving the TCI state activation of the candidate cell before receiving the beam indication of the candidate cell,

[0248] ● Alternative 2: TCI state activation of the candidate cell is received together with the reception of the beam indication of the candidate cell

[0249] ○ For further study: Signalling details for TCI status indication if activation and indication are done in the same MAC CE message of the bearer handover command

[0250] ●Alternative solution 3: Alternative solution 1 and / or alternative solution 2 may be supported based on UE capabilities

[0251] For further study: Signaling details for TCI state activation

[0252] For further study: For Alternative 1, whether / how to allow TCI state activation for candidate cells

[0253] NOTE: If scenarios 1 and 3 are to be supported, other beam indication / TCI activation timing relationships are not excluded.

[0254] Working hypothesis

[0255] In the presence of beam indication in the cell handover command, at least for scenario 2, the following cases are supported:

[0256] ● 1 combination of target cell fields or 1 pair of UL and DL unified TCI state index fields are always present in the cell handover command.

[0257] protocol

[0258] ●L1 measurement reporting for gNB scheduling also supports periodic and semi-persistent reporting on PUCCH.

[0259] protocol

[0260] ● In this conference, LS is sent to RAN2, 3, and 4 based on the RAN1 protocol

[0261] ○ Includes all protocols in AI 9.10.1 and 9.10.2 in RAN1#112bis-e

[0262] ○LS contains the following contents

[0263] ■RAN1 has made the following agreement in RAN1#112bis-e

[0264] ● Alternative 2 for beam indication of target cell and TCI status activation of candidate cell (if supported),

[0265] ○Alternative 1: By indicating the RS identifier, i.e. the mapping between the RS identifier and the Rel-17 unified TCI state is done by the UE

[0266] ○Alternative 2: By indicating the Rel-17 TCI status index

[0267] ■ This protocol implies that the source cell must have information so that the source cell can send the Rel-17 TCI state index of the target / candidate cell to the UE even when the source cell and the target / candidate cell belong to different DUs. RAN1 respectfully requests RAN3 to perform any necessary specification work to support this functionality.

[0268] In [8] Moderator Notes RAN1#113eom3, the following is explained.

[0269] protocol

[0270] The UE may be instructed and activate a single joint TCI state or a pair of UL / DL TCI states in a cell switching command.

[0271] protocol

[0272] - For configuration of SSB-based L1-RSRP measurements,

[0273] - Provides SSB periodicity, SSB position in burst as time domain information for co-frequency and off-frequency

[0274] protocol

[0275] - Each TCI state contains at most 2 qcl-types, and each qcl-type source RS in the QCL-Info of the TCI state is provided based at least on the RS configuration of the LTM

[0276] - For further study: Other RS ​​indexes than the measurement RS configuration for LTM

[0277] - For further study: Additional content for TCI status of LTM

[0278] protocol

[0279] - For the TCI state activation of the candidate cell before the cell handover command,

[0280] - Using MAC CE, the details of MAC-CE for TCI state activation for LTM depends on RAN2

[0281] - Further study whether PDCCH orders for candidate cells can be used

[0282] protocol

[0283] For PRACH based on PDCCH command to candidate cells, the candidate cell SSB indicated in the PDCCH command serves as the path loss RS for PRACH Tx power determination.

[0284] protocol

[0285] Based on the determination of PRACH transmission power when reception of RAR is not configured, a [1 bit] field in the PDCCH order that explicitly indicates initial transmission or retransmission of PRACH is supported.

[0286] protocol

[0287] A 1-bit field in the PDCCH order that explicitly indicates the initial transmission or retransmission of PRACH based on the determination of PRACH transmit power when reception of RAR is not configured. For further study

[0288] - The UE shall increase power by the power ramp configured value if it is instructed to retransmit, unless the maximum allowed power is achieved

[0289] - Whether / how to reset the counter

[0290] protocol

[0291] ● For PDCCH-commanded PRACH of candidate cells, if UE capabilities do not support simultaneous / parallel transmissions, when PRACH transmissions to candidate cells other than the current serving cell (including any interruptions due to processing time to construct PRACH transmissions, carrier and / or BWP switching time (if any), UL or DL ​​RF re-tuning time (if any), additional preparation time (if any)) happen to overlap on one or more symbols or have a time gap below a certain threshold (e.g., N symbols, value of N is for further study), with the following UL transmission to one of the serving cells

[0292] PRACH transmission

[0293] ● PUCCH / PUSCH transmission carrying HARQ-ACK, SR, P / SP CSI, and aperiodic CSI

[0294] SRS transmission

[0295] ●Any other PUCCH / PUSCH transmission

[0296] ● In this case select UE behavior down

[0297] ●Alternative 1: Need to discard rules

[0298] ●Alternative 2: Depends on UE implementation

[0299] In [9] 3GPP TS 38.321 V17.3.0 (2022-12) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) Protocol Specification (Release 17), the following is explained.

[0300] 6.1.3.47 Unified TCI status activation / deactivation of MAC CE

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

[0302] - 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], then 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;

[0303] - BWP ID: This field indicates the DL BWP applied by the MAC CE 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;

[0304] -BWP ID: This field indicates the UL BWP applied by the MAC CE 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 joint, this field is considered reserved. The length of the BWP ID field is 2 bits;

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

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

[0307] -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, the 7-bit length TCI State ID, i.e., TCI-StateId, as specified in TS 38.331 [5] is used. If D / U is set to 0, the most significant bit of the TCI State ID is considered a reserved bit, and the remaining 6 bits indicate the UL-TCIState-Id as specified in TS 38.331 [5]. The maximum number of activated TCI states is 16;

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

[0309] Figure 6 It is from 3GPP TS 38.321V17.3.0(2022-12) Figure 6 .1.3.47-1: Unified TCI state activation / deactivation of MAC CE 1 reappearance.

[0310] 6.1.3.15 TCI status indication for UE-specific PDCCH MAC CE

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

[0312] - 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 the set simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, respectively;

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

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

[0315] Figure 7 It is from 3GPP TS 38.321V17.3.0(2022-12) Figure 6 .1.3.15-1: Reproduction of TCI status indication for UE-specific PDCCH MAC CE.

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

[0317] 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:

[0318] - 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 the set simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, respectively;

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

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

[0321] NOTE 1: If a CORESET is configured with different CORESETPoolindex values ​​in a BWP, the enhanced TCI status indication for the UE-specific PDCCH MAC CE is not applicable to any of the configured CORESETs in the BWP.

[0322] NOTE 2: Enhanced TCI status indication for UE-specific PDCCH MAC CE applies only when sfnSchemePdcch is configured.

[0323] NOTE 3: If a 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 status indication for the UE-specific PDCCH MAC CE is not applicable for the CORESET configured by controlResourceSetZero.

[0324] Figure 8 It is from 3GPP TS 38.321V17.3.0(2022-12) Figure 6.1.3.44-1: Reproduction of enhanced TCI status indication for UE-specific PDCCH MAC CE.

[0325] In

[10] 3GPP TS 38.212 V17.3.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and Channel Coding (Release 17), the following is explained.

[0326] 7.3.1.1.2 Format 0_1

[0327] DCI format 0_1 ​​is used for scheduling one or more PUSCHs in a cell, or to indicate CG downlink feedback information (CG-DFI) to the UE.

[0328] The following information is transmitted via DCI format 0_1, where the CRC is scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI:

[0329] - Identifier for DCI format - 1 bit

[0330] - The value of this bit field is always set to 0, indicating the UL DCI format

[0331] - Carrier indicator - 0 or 3 bits, as defined in clause 10.1 of [5, TS 38.213]. When this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, this field is reserved with the same number of bits as carried by PDCH on the SCell in this format for scheduling on the primary cell.

[0332] …

[0333] -UL / SUL indicator - For UEs not configured with supplementaryUplink in ServingCellConfig in the cell or UEs configured with supplementaryUplink in ServingCellConfig in the cell, but only one carrier in the cell is configured for PUSCH transmission, 0 bit; otherwise, 1 bit, as defined in Table 7.3.1.1.1-1.

[0334] - Bandwidth part indicator – 0, 1 or 2 bits, such as the number n of UL BWPs configured by higher layers BWP ,RRC determines,excluding the initial UL bandwidth part. The bit width used for this field is determined as bits, of which

[0335] -If n BWP,RRC ≤3, then nBWP =n BWP,RRC +1, in which case the bandwidth part indicator is equal to the higher layer parameter BWP-Id in ascending order;

[0336] - Otherwise, n BWP =n BWP ,RRC, in this case, the bandwidth part indicator is defined in Table 7.3.1.1.2-1;

[0337] If the UE does not support active BWP change via DCI, the UE ignores this bit field.

[0338] - Frequency domain resource assignment - the number of bits determined by, where is the size of the active UL bandwidth portion:

[0339] - If the higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is not configured, then

[0340] - N if only resource allocation type 0 is configured RBG bits, where N RBG Defined in clause 6.1.2.2.1 of [6, TS 38.214],

[0341] - If only resource allocation type 1 is configured, then bit, or if resourceAllocation is configured as 'dynamicSwitch', then Bit.

[0342] - If resourceAllocation is configured to 'dynamicSwitch', then the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where a bit value of 0 indicates resource allocation type 0 and a bit value of 1 indicates resource allocation type 1.

[0343] -For resource allocation type 0, N RBG The LSBs provide resource allocation as defined in clause 6.1.2.2.1 of [6, TS 38.214].

[0344] -For resource allocation type 1, Each LSB provides the following resource allocation:

[0345] - For PUSCH frequency hopping of resource allocation type 1:

[0346] - According to clause 6.3 of [6, TS 38.214], N UL_hopThe MSB bits are used to indicate the frequency offset, where if the high-level parameter frequencyHoppingOffsetLists contains two offset values, then N UL_hop = 1, if the high-level parameter frequencyHoppingOffsetLists contains four offset values, then N UL_hop =2

[0347] - The ones digit provides the frequency domain resource allocation according to clause 6.1.2.2.2 of [6, TS 38.214]

[0348] - For non-PUSCH frequency hopping of resource allocation type 1:

[0349] - The ones digit provides the frequency domain resource allocation according to clause 6.1.2.2.2 of [6, TS 38.214]

[0350] …

[0351] -Time domain resource assignment - 0, 1, 2, 3, 4, 5, or 6 bits

[0352] - If the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 is not configured, and if the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH is not configured, and if the higher layer parameter pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17 is not configured, and if the higher layer parameter pusch-TimeDomainAllocationList is configured, then 0, 1, 2, 3 or 4 bits as defined in clause 6.1.2.1 of [6, TS38.214]. The bit width used for this field is determined to be bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationList;

[0353] - If the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 is configured, or if the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH is configured, or if the higher layer parameter push-TimeDomainResourceAllocationListForMultiPUSCH-r17 is configured, then 0, 1, 2, 3, 4, 5 or 6 bits as defined in clause 6.1.2.1 of [6, TS38.214]. The bit width used for this field is determined as bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 or pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17;

[0354] Otherwise, the bit width used for this field is determined as bits, where I is the number of entries in the default table.

[0355] …

[0356] - Modulation and coding scheme - 5 bits, as defined in clause 6.1.4.1 of [6, TS 38.214]

[0357] - New Data Indicator - 1 bit if the number of scheduled PUSCHs indicated by the Time Domain Resource Assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits, which is determined based on the maximum number of schedulable PUSCHs among all entries in the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17, where each bit corresponds to one scheduled PUSCH, as defined in clause 6.1.4 of [6, TS 38.214].

[0358] - Redundancy version - the number of bits determined by:

[0359] - If the number of scheduled PUSCHs indicated by the Time Domain Resource Allocation field is 1, then 2 bits, as defined in Table 7.3.1.1.1-2;

[0360] - Otherwise 2, 3, 4, 5, 6, 7 or 8 bits, determined by the maximum number of schedulable PUSCHs among all entries in the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainResourceAllocationListForMultiPUSCH-r17, where each bit corresponds to one scheduled PUSCH, as defined in clause 6.1.4 of [6, TS38.214], and the redundancy version is determined according to Table 7.3.1.1.2-34.

[0361] - HARQ process number - 5 bits if higher layer parameter harq-ProcessNumberSizeDCI-0-1 is configured; otherwise 4 bits

[0362] …

[0363] - TPC command of scheduled PUSCH - 2 bits, as defined in clause 7.1.1 of [5, TS38.213]

[0364] - Second TPC command for scheduled PUSCH, 2 bits if higher layer parameter SecondTPCFieldDCI-0-1 is configured, as defined in clause 7.1.1 of [5, TS38.213]; otherwise 0 bit.

[0365] - SRS resource set indicator - 0 or 2 bits

[0366] - In the following cases, according to Table 7.3.1.1.2-36, 2 bits

[0367] -txConfig=nonCodeBook, and there are two SRS resource sets configured via srs-ResourceSetToAddModList and associated with the usage value 'non-codebook', or

[0368] -txConfig=codebook, and there are two SRS resource sets configured via srs-ResourceSetToAddModList and associated with usage value 'codebook';

[0369] -Otherwise 0 bit.

[0370] -SRS Resource Indicator- or bits, where N SRS is the number of configured SRS resources in the SRS resource set indicated by the SRS resource set indicator field (if present); otherwise N SRSis the number of configured SRS resources in the SRS resource set configured by the higher layer parameter srs-ResourceSetToAddModList and is associated with a higher layer parameter usage with a value of 'codebook' or 'non-codebook',

[0371] - According to Table 7.3.1.1.2-28 / 29 / 30 / 31, if the higher layer parameter txConfig = nonCodebook, then bits, where N SRS is the number of configured SRS resources in the SRS resource set indicated by the SRS resource set indicator field (if present), otherwise N SRS is the number of configured SRS resources in the SRS resource set configured by the higher layer parameter srs-ResourceSetToAddModList and is associated with the higher layer parameter usage with the value 'non-codebook', and

[0372] - If the UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of the PUSCH-ServingCellConfig of the serving cell is configured, then L max Given by the parameters

[0373] - Otherwise, L max Given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.

[0374] - According to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B, if the higher layer parameter txConfig = codebook, then bits, where N SRS is the number of configured SRS resources in the SRS resource set indicated by the SRS resource set indicator field (if present), otherwise N SRS is the number of configured SRS resources in the SRS resource set configured by the higher layer parameter srs-ResourceSetToAddModList and is associated with the higher layer parameter usage of the value 'codebook'.

[0375] - Second SRS resource indicator – 0, or Bit,

[0376] - According to Table 7.3.1.1.2-28 / 29A / 30A / 31A, for the same number of layers indicated by the SRS Resource Indicator field, if the higher layer parameter txConfig = nonCodebook and the SRS Resource Set Indicator field is present, then bits, where N SRS is the number of configured SRS resources in the second SRS resource set, and

[0377] - If the UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of the PUSCH-ServingCellConfig of the serving cell is configured, then L max Given by the parameters

[0378] - Otherwise, L max Given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.

[0379] - According to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B, if the higher layer parameter txConfig = codebook and the SRS resource set indicator field is present, then bits, where N SRS is the number of configured SRS resources in the second SRS resource set.

[0380] -Otherwise 0 bit.

[0381] …

[0382] - CSI request - 0, 1, 2, 3, 4, 5 or 6 bits determined by the higher layer parameter reportTriggerSize.

[0383] 7.3.1.2.2 Format 1_1

[0384] DCI format 1_1 is used for scheduling one or more PDSCHs in a cell.

[0385] The following information is transmitted via DCI format 1_1, where the CRC is scrambled by the C-RNTI or CS-RNTI or MCS-C-RNTI:

[0386] - Identifier for DCI format - 1 bit

[0387] - The value of this bit field is always set to 1, indicating the DL DCI format

[0388] - Carrier indicator - 0 or 3 bits, as defined in clause 10.1 of [5, TS 38.213]. When this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, this field is reserved with the same number of bits as carried by PDCH on the SCell in this format for scheduling on the primary cell.

[0389] - Bandwidth part indicator – 0, 1 or 2 bits, such as the number n of DL BWPs configured by higher layers BWP ,RRC determines,excluding the initial DL bandwidth part. The bit width used for this field is determined as bits, of which

[0390] -If n BWP,RRC ≤3, then n BWP =n BWP,RRC +1, in which case the bandwidth part indicator is equal to the higher layer parameter BWP-Id in ascending order;

[0391] - Otherwise, n BWP =n BWP ,RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;

[0392] If the UE does not support active BWP change via DCI, the UE ignores this bit field.

[0393] - Frequency domain resource assignment - the number of bits determined by, where is the size of the active DL bandwidth portion:

[0394] - N if only resource allocation type 0 is configured RBG bits, where N RBG Defined in clause 5.1.2.2.1 of [6, TS38.214],

[0395] - If only resource allocation type 1 is configured, then bit, or

[0396] - If resourceAllocation is configured as 'dynamicSwitch'; Bit.

[0397] - If resourceAllocation is configured to 'dynamicSwitch', then the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where a bit value of 0 indicates resource allocation type 0 and a bit value of 1 indicates resource allocation type 1.

[0398] -For resource allocation type 0,N RBG The LSBs provide resource allocation as defined in clause 5.1.2.2.1 of [6, TS 38.214].

[0399] -For resource allocation type 1, LSBs provide resource allocation as defined in clause 5.1.2.2.2 of [6, TS 38.214]

[0400] If the "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part, and if resourceAllocation is configured to 'dynamicSwitch' for the indicated bandwidth part, then if the bit width of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bit width of the "Frequency domain resource assignment" field of the indicated bandwidth part, the UE adopts resource allocation type 0 for the indicated bandwidth part.

[0401] -Time domain resource assignment - 0, 1, 2, 3, 4, 5, or 6 bits

[0402] - If the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH is not configured, and if the higher layer parameter pdsch-TimeDomainAllocationList is configured, then 0, 1, 2, 3 or 4 bits as defined in clause 5.1.2.1 of [6, TS 38.214]. The bit width used for this field is determined as bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter is configured;

[0403] - If the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH is configured, it is 0, 1, 2, 3, 4, 5 or 6 bits as defined in clause 5.1.2.1 of [6, TS38.214]. The bit width used for this field is determined as bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH;

[0404] - Otherwise I is the number of entries in the default table.

[0405] …

[0406] -ZP CSI-RS Trigger – 0, 1, or 2 bits, as defined in clause 5.1.4.2 of [6, TS 38.214]. The bit width used for this field is determined as bits, where n ZP is the number of aperiodic ZP CSI-RS resource sets configured by higher layers.

[0407] For transport block 1:

[0408] - Modulation and coding scheme - 5 bits, as defined in clause 5.1.3.1 of [6, TS 38.214]

[0409] - New Data Indicator - 1 bit if the number of scheduled PDSCHs indicated by the Time Domain Resource Assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits, which is determined based on the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH, as defined in clause 5.1.3 of [6, TS 38.214].

[0410] - Redundancy version - the number of bits determined by:

[0411] - If the number of scheduled PDSCHs indicated by the Time Domain Resource Assignment field is 1, 2 bits, as defined in Table 7.3.1.1.1-2;

[0412] - Otherwise 2, 3, 4, 5, 6, 7 or 8 bits, determined by the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH, as defined in clause 5.1.3 of [6, TS 38.214], and the redundancy version is determined according to Table 7.3.1.1.2-34.

[0413] For transport block 2 (only present when maxNrofCodeWordsScheduledByDCI is equal to 2):

[0414] - Modulation and coding scheme - 5 bits, as defined in clause 5.1.3.1 of [6, TS 38.214]

[0415] - New Data Indicator - 1 bit if the number of scheduled PDSCHs indicated by the Time Domain Resource Assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits, which is determined based on the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH, as defined in clause 5.1.3 of [6, TS 38.214].

[0416] - Redundancy version - the number of bits determined by:

[0417] - If the number of scheduled PDSCHs indicated by the Time Domain Resource Assignment field is 1, 2 bits, as defined in Table 7.3.1.1.1-2;

[0418] - Otherwise 2, 3, 4, 5, 6, 7 or 8 bits, determined by the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH, as defined in clause 5.1.3 of [6, TS 38.214], and the redundancy version is determined according to Table 7.3.1.1.2-34.

[0419] …

[0420] - HARQ process number - 5 bits if higher layer parameter harq-ProcessNumberSizeDCI-1-1 is configured; otherwise 4 bits

[0421] …

[0422] - TPC command for scheduled PUCCH - 2 bits, as defined in clause 7.2.1 of [5, TS 38.213]

[0423] - Second TPC command for scheduled PUCCH - 2 bits as defined in clause 7.2.1 of [5, TS 38.213] if higher layer parameter SecondTPCFieldDCI-1-1 is configured; otherwise 0 bits.

[0424] - PUCCH resource indicator - 3 bits, as defined in clause 9.2.3 of [5, TS 38.213]

[0425] -PDSCH-to-HARQ_feedback timing indicator – 0, 1, 2 or 3 bits, as defined in clause 9.2.3 of [5, TS 38.213]. The bit width used for this field is determined as bits, where I is the number of entries in the higher layer parameter dl-DataToUL-ACK.

[0426] …

[0427] -Transmission Configuration Indication - 0 bits if the higher layer parameter tci-PresentInDCI is not enabled; otherwise 3 bits as defined in clause 5.1.5 of [6, TS38.214].

[0428] If the Bandwidth Part Indicator field indicates a bandwidth part other than the active bandwidth part

[0429] - If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for PDCCH carrying DCI format 1_1,

[0430] - The UE assumes that tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth part;

[0431] -otherwise,

[0432] - The UE assumes that tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth part.

[0433] In order to make the handover earlier, L1 / L2 triggered mobility (LTM) is introduced. The source network node can trigger the physical random access channel (PRACH) transmission through the physical downlink control channel (PDCCH) command for acquiring the timing advance (TA) before transmitting the handover (HO) command. The PDCCH command will trigger the contention-free random access procedure (CFRA). In order to save signaling, the network node may not transmit the message including TA information to the user equipment (UE), which is called the random access response (RAR) TA mechanism in our disclosure. In fact, the network node provides TA information together with the HO command, which can benefit from storing too much TA information for each candidate cell. Without loss of generality, the number of candidate cells can be configured by the network node and / or subject to the capabilities of the UE. Each candidate cell is not a serving cell before the UE receives the HO command. Before receiving the HO command, the UE will have a light or full configuration associated with one or more candidate cells. The light configuration may include a random access channel (RACH) configuration. The complete configuration may further include RACH configuration, physical uplink shared channel (PUSCH) configuration, physical uplink control channel (PUCCH) configuration, or sounding reference signal (SRS) configuration. In addition, the channel state information (CSI) report for beam management (BM) is pre-configured by the network. Regardless of whether the time behavior of CSI is periodic, semi-persistent, or aperiodic reporting, CSI reporting for BM is based on network instructions.

[0434] In view of the above, regardless of whether there is an LTM or CSI report for BM, the UE reports in response to the network's instructions or configuration. However, the UE is actually a device that is notified of various downlink (DL) channel conditions at an earlier moment. In order to have a fast response of the DL channel, a framework for designing UE-triggered reports (or event-triggered reports or UE-initiated reports) is considered. Among other things, such UE-triggered reports can be used not only for LTM, but also for assisting network nodes in making decisions for intra-cell cell scheduling. More specifically, the UE-triggered report can include any one or any combination of the following: within a distributed unit (DU), between DUs, within a centralized unit (CU), between CUs, within a cell, between cells, multiple downlink control information (mDCI), multiple transmission and reception points (mTRP), single DCI (sDCI), mTRP, and / or single TRP. For example, in Fig. 9 In the UE-triggered report, once the conditions for triggering the UE report are met, the UE transmits the UE-triggered report to the next generation Node B (gNB). The gNB can make a decision on possible actions.

[0435] In NR Rel-16, regulated handover may be the starting point. For example, one may consider (conditional) events A3, A4 or A5 in TS 38.331, which may be summarized as checking the quality of candidate and / or primary cell (PCell) / primary secondary cell (PSCell).

[0436] With the introduction of UE triggered reporting, there may be some issues that need to be addressed.

[0437] The first problem is to design the conditions for UE triggered reporting. Since the network node can use this UE triggered report to make different decisions (for example, for changing the scheduling beam, changing the number of scheduled TRPs, changing the scheduling of the number of coordinated TRPs, changing the number of TRPs, etc.), the conditions for UE triggering seem to be designed in different ways. For example, when the UE has good channel quality via a currently used beam, once the UE identifies a candidate beam with good quality for communication, using the condition of comparing the currently used beam with the candidate beam will cause the UE to not trigger a report, but in fact the candidate beam can be triggered for assisting the network node's scheduling mTRP scheme or adding / activating / indicating decisions on additional beams. In other words, when a candidate beam with good quality is identified for possible operation of an mTRP, the UE can trigger a report without comparing the quality of the candidate beam to an offset that is better than the quality of the currently used beam. On the other hand, when the UE has poor channel quality via one currently used beam, once the UE identifies a candidate beam whose communication quality is preferably better than the channel quality of one currently used beam by an offset, using a condition that only compares the candidate beams will result in the UE not triggering a report, but in fact the candidate beams may be reported for assisting the network node's decision to replace the currently used beam. This may occur when the quality of the candidate beam is not better than the threshold but it is actually better than the quality of the currently used beam by an offset. In view of the above, the design of conditions for different scenarios may be required.

[0438] The second problem is that when the network node receives a UE-triggered report, how does the network node know the underlying reason for the report (e.g., the triggering reason). For example, if the triggered report includes candidate beam related information and beam quality (e.g., with a quality matrix such as L1 or L3 reference signal received power (RSRP)), the network node may be confused as to whether the report is triggered to change the current beam or to add or use the reported candidate beam.

[0439] The third issue is that the UE determines which object to measure for the triggered report. For Rel-15 / 16, without considering the unified TCI state, the UE can receive beam information per control resource set (CORESET) for monitoring. When UE-triggered reporting is introduced on a cell without having / applying a unified TCI state, how to determine which RS or beam is used to declare whether the triggering condition is met. For Rel-17 / 18, which considers a unified TCI state, if the condition requires the quality of the currently used beam, it seems feasible to use the indicated TCI state as the currently used state. In addition, the UE's determination of which object as a candidate reference signal (RS) / beam may also require further design. For mTRP operation, whether the triggering conditions are determined individually or jointly may require further study. For example, consider that the UE is indicated by a BM DCI with TCI state x and TCI state y associated with beam 1 and beam 2, respectively, and is an object corresponding to the currently used beam for each indicated beam (e.g., beam 1, beam 2 individually) or corresponds to an indicated beam pair (e.g., beam 1 and beam 2 as a pair). And, the object of candidates corresponds to each candidate beam (e.g., candidate beam 1 is preferably compared with beam 1, and candidate beam 2 is preferably compared with beam 2) or corresponds to a beam pair (e.g., a candidate beam pair is preferably compared with beam 1 and beam 2). Finally, once the UE supports group-based beam reporting (and / or the UE is also configured with group-based beam reporting), how to determine support for this feature and UE-triggered reporting may require further design.

[0440] The fourth question is how / whether to prohibit the behavior of such UE-triggered reporting so as to trigger such reporting frequently. In addition, the interaction between the beam reporting configured / indicated / requested by the network and the UE-triggered reporting may need further design.

[0441] The fifth issue is the detailed content of the UE-triggered report. Based on the issues identified above, what the UE sets or places in the triggered report may require appropriate design.

[0442] Preferably in certain embodiments, the container for UE-initiated reporting may be a MAC CE or a L1 signal (eg, Uplink Control Information (UCI) on PUCCH / PUSCH).

[0443] Preferably in certain embodiments, the conditions or criteria for UE-initiated reporting may be (pre-)configured per UE, serving cell, beam, RS, BWP or TCI state.

[0444] Preferably in certain embodiments the UE triggers the reporting and / or transmits the triggered reporting wherein any beam failure detection counter has not expired.

[0445] Preferably in certain embodiments, the UE triggers the reporting when the beam failure recovery (BFR) procedure is not triggered.

[0446] Preferably in certain embodiments, the UE triggered reporting is not in response to beam failure or radio link failure.

[0447] Preferably in certain embodiments, the UE triggers the report and / or transmits the triggered report when the UE does not experience beam failure or radio link failure.

[0448] Preferably in certain embodiments, the UE triggered report is not or does not correspond to a report in response to a beam failure.

[0449] Preferably in certain embodiments, the UE triggered report is not or does not correspond to a BFR report or request transmitted via the UE.

[0450] Preferably in certain embodiments, the UE-triggered report is transmitted here when the channel condition via the currently used beam is not so bad as to declare or determine as beam failure or radio link failure.

[0451] Preferably in certain embodiments, a UE-triggered report is transmitted when a candidate beam identified by the UE has good quality and / or has better quality than the beam currently in use.

[0452] Concept 0

[0453] The triggering conditions for UE-triggered reporting may consider one or more of the following:

[0454] The quality of at least one candidate beam;

[0455] ● the quality of at least one currently used / indicated beam; and / or

[0456] ●The content (beam / TCI status / RS and / or associated quality) of the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report (associated with the same serving cell).

[0457] The triggering conditions for UE triggered reporting may be based on one or more of the following criteria:

[0458] ● The quality (plus or minus an offset) of at least one candidate beam is greater than (or equal to) a threshold;

[0459] ● The quality (plus or minus an offset) of at least one currently used / indicated beam is less than (or equal to) a threshold;

[0460] The quality (plus or minus an offset) of at least one candidate beam is greater than (or equal to) the quality (plus or minus an offset) of at least one currently used / indicated beam;

[0461] ● the beam / TCI state / RS indicated by the UE triggered report is different from the beam / TCI state / RS indicated by the last transmitted (UE triggered, periodic, aperiodic or semi-persistent) report (associated with the same serving cell); and / or

[0462] ●The quality (plus or minus an offset) of the beam / TCI state / RS indicated by the UE-triggered report is different from (e.g., greater than (or equal to) or less than (or equal to)) the quality (plus or minus an offset) of the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report (associated with the same serving cell).

[0463] The quality of at least one candidate beam may be derived from one or more of the following:

[0464] The quality of the candidate beams having a quality greater than (or equal to) a threshold (plus or minus an offset);

[0465] ● the quality of one of the at least one candidate beams having the best quality, e.g. its quality is the best among the at least one candidate beam; and / or

[0466] • The (average) quality of several of the at least one candidate beams having the best quality, e.g. the N best beams (N may be configured by the network and / or N may be 1 or greater than 1).

[0467] The at least one candidate beam may be one or more of the following:

[0468] Candidate RS, e.g., for BFR to declare beam failure, or to be a candidate RS in response to beam failure;

[0469] (All) (deactivated) TCI states, e.g., TCI states for PDCCH monitoring, for (all) CORESETs, for CORESET 0 and / or one or more or all CORESET pools, for CORESETs associated with a common search space (CSS), for CORESETs associated with both a UE-specific search space (USS) and a CSS;

[0470] ● The (activated) TCI status of one, multiple or all candidate cells;

[0471] ● RS associated with one or more triggering conditions or criteria;

[0472] ● RS associated with a triggering condition or criterion; and / or

[0473] ● RS configured for UE triggered reporting.

[0474] The at least one candidate beam does not include (or should exclude) at least one currently used / indicated beam.

[0475] The quality of at least one currently used / indicated beam may be derived from one or more of the following:

[0476] The quality of one of the at least one currently used / indicated beams having the worst quality, e.g., the quality of one of the at least one currently used / indicated beams being the worst among the at least one currently used / indicated beam;

[0477] = the (average) quality of a number of the at least one currently used / indicated beams having the worst quality, e.g. the N worst beams (N may be configured by the network and / or N may be 1 or greater than 1);

[0478] The quality of the currently used / indicated beam having a quality less than (or equal to) a threshold value (plus or minus an offset);

[0479] The quality of a beam of the at least one currently used / indicated beam having the best quality, for example, the quality of which is the best among the at least one currently used / indicated beam;

[0480] ● the (average) quality of a number of said at least one currently used / indicated beams having the best quality, e.g. the N best beams (N may be configured by the network and / or N may be 1 or greater than 1); and / or

[0481] - The (average) quality of all the at least one currently used / indicated beams.

[0482] The at least one currently used / indicated beam may be one or more of the following:

[0483] ● One beam failure detection (BFD)-reference signal (RS) in the RS set;

[0484] ● Multiple (or all) RSs in the BFD-RS set;

[0485] ● (all) activated TCI states, e.g., for PDCCH monitoring, for (all) CORESETs, for CORESET 0 and / or activated TCI states for one or more or all CORESET pools; and / or

[0486] ●Beam / TCI status indicated by the (last received) beam indication DCI.

[0487] The UE may use one or more of the following triggering conditions for UE triggered reporting:

[0488] ● The quality (plus or minus an offset) of at least (or any) candidate beam of the serving cell is greater than (or equal to) a threshold;

[0489] ● The quality (plus or minus an offset) of at least (or any) currently used / indicated beam of the serving cell is less than (or equal to) a threshold;

[0490] The quality (plus or minus an offset) of at least (or any) candidate beam of the serving cell is greater than (or equal to) the quality (plus or minus an offset) of at least (or any) currently used / indicated beam of the serving cell;

[0491] The beam / TCI state / RS indicated by a UE-triggered report associated with the serving cell is different from the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report associated with the serving cell;

[0492] The quality of the beam / TCI state / RS indicated by the UE-triggered report (plus or minus an offset) is different from (e.g., greater than (or equal to) or less than (or equal to)) the quality of the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report (plus or minus an offset);

[0493] ● The quality (plus or minus an offset) of at least (or any) candidate beam of the serving cell is greater than (or equal to) the quality (plus or minus an offset) of at least (or any) currently used / indicated beam of the serving cell (and preferably, the at least one candidate beam of the serving cell and the at least one currently used / indicated beam of the serving cell are associated with the same TRP or the same UE panel). Preferably, in some embodiments, if the at least one currently used / indicated beam is replaced by the at least one candidate beam and both are associated with the same TRP or the same UE panel, the operation of multiple TRPs still works;

[0494] ● The quality (plus or minus an offset) of at least one (or any) candidate beam of one (or any) candidate cell is greater than (or equal to) a threshold;

[0495] ● the quality (plus or minus an offset) of at least (or any) candidate beam of one (or any) candidate cell is greater than (or equal to) the quality (plus or minus an offset) of at least (or any) currently used / indicated beam of a PCell or a special cell (SpCell) (e.g., not considering a PSCell or a secondary cell (SCell)); and / or

[0496] ●The beam / TCI state / RS indicated by a UE-triggered report associated with the candidate cell is different from the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report associated with the candidate cell.

[0497] The thresholds may be configured for specific triggered conditions, specific serving cells, specific candidate cells, specific LTM candidate configurations (for a set of cells), and / or specific additional physical cell identities (PCIs). The thresholds may be (pre-)configured or associated with different conditions, different serving cells, different candidate cells, different LTM candidate configurations, or different additional PCIs. The thresholds for different conditions, different serving cells, different candidate cells, different LTM candidate configurations, or different additional PCIs may be different.

[0498] The UE-triggered report may contain one or more of the following information:

[0499] ● one or more serving cells associated with at least one currently used / indicated beam and / or at least one candidate beam indicated by the report triggered by the UE;

[0500] ● At least one currently used / indicated beam of the serving cell;

[0501] At least one currently used / indicated beam of the PCell;

[0502] The quality of the at least one currently used / indicated beam;

[0503] ● at least one candidate beam of the serving cell, e.g., associated with the same or different additional PCI;

[0504] ● one or more candidate cells associated with at least one candidate beam indicated by the report triggered by the UE;

[0505] ● At least one candidate beam of the same or different candidate cell;

[0506] The quality of the at least one candidate beam;

[0507] ● Information associated with LTM or non-LTM (explicit fields or via implicit derivation from other fields); and / or

[0508] ●An identity associated with UETriggeredCondConfig, comprising a triggering condition or parameter associated with the at least one candidate beam.

[0509] A UE-triggered report may not indicate one or more of the following information:

[0510] ● a serving cell associated with at least one currently used / indicated beam and / or at least one candidate beam indicated by a report triggered by the UE;

[0511] ● At least one currently used / indicated beam of a serving cell other than PCell or SpCell;

[0512] ● Candidate beams of serving cells associated with different additional PCIs; and / or

[0513] ●Candidate beams of different candidate cells.

[0514] UE triggered reporting (for or associated with a serving cell) may be cancelled in one or more of the following conditions:

[0515] UE-triggered reporting is transmitted by the UE or included in a transmission (e.g., MAC PDU or TB);

[0516] ● Periodic, semi-persistent or network-requested reports are transmitted by the UE. The content of periodic, semi-persistent or network-requested reports is (partially) the same as the (expected) content of UE-triggered reports;

[0517] MAC reset;

[0518] ● Parameters for UE triggered reporting are reconfigured;

[0519] ● BFR is triggered (for serving cell or BFD-RS set). UE-triggered reporting can be associated with serving cell or BFD-RS set;

[0520] ●Initiate a random access procedure for (SpCell or SCell) BFR;

[0521] ● at least one currently used / indicated beam indicated in the UE-triggered report is deactivated or becomes a non-currently used / indicated beam;

[0522] ● at least one candidate beam indicated in the UE-triggered report is deactivated or becomes a non-candidate beam;

[0523] ● at least one serving cell associated with the UE-triggered report is deactivated or released;

[0524] ● at least one candidate cell associated with the UE-triggered report is deactivated or released;

[0525] PCell change (eg, a change of cell for receiving a PDCCH associated with a common search space);

[0526] ● Receiving a MAC CE for LTM (e.g., LTM Cell Switch Command) or initiating LTM; and / or

[0527] • The network node of the UE's serving cell is in a power saving state (eg, cell discontinuous transmission (DTX) discontinuous reception (DRX)).

[0528] The serving cell can be a PCell, PSCell, SpCell or SCell (if not explicitly excluded).

[0529] The beam can be replaced by RS or TCI state. The RS can be replaced by beam or TCI state. The TCI state can be replaced by beam or RS.

[0530] The (UE triggered) report may be a CSI report. The (UE triggered) report may be a MAC CE for CSI.

[0531] Concept 1

[0532] This concept will have different trigger conditions for the UE communicating with a single TRP or with multiple TRPs (in the case where the identified candidate beam is on the same cell as the currently used beam) and / or LTM (in the case where the identified candidate beam is on a different cell than the currently used beam). Preferably, in some embodiments, the UE communicating with a single TRP may correspond to the UE performing (UE-specific) downlink reception via the first beam associated with the single TRP. Preferably, in some embodiments, the UE communicating with multiple TRPs may correspond to the UE performing (UE-specific) downlink reception via the first beam and the second beam associated with multiple TRPs.

[0533] Preferably in certain embodiments, for a single TRP scenario, the triggering condition for the UE-triggered report may be (based on) the UE identifying (at least) a first candidate beam having a quality greater than a threshold. Preferably in certain embodiments, the UE triggers the report (for a single TRP) without considering the quality of the currently used / indicated beam.

[0534] Preferably in certain embodiments, for the LTM scenario, the triggering condition for the UE-triggered report may be (based on) the UE identifying (at least) a first candidate beam with good quality and a currently used beam with poor quality. More specifically, the triggering condition for LTM may be (based on) the quality of the first candidate beam having an offset better than the quality of one or two or all currently used / indicated beams. For example, the triggering condition for LTM may be (based on) the quality of the first candidate beam plus or minus an offset better than the quality of one or two or all currently used / indicated beams. Alternatively, and more specifically, the triggering condition for LTM may be (based on) the quality of the first candidate beam being better than a threshold and the quality of one or two or all currently used / indicated beams being worse than a second threshold. Preferably in certain embodiments, the triggering condition for LTM may be (pre-)configured per UE or per serving cell. Preferably in some embodiments, the UE may trigger a report (for LTM) when the triggering condition for LTM is met (preferably it may further consider the first number of times that the quality of the first candidate beam is better than a threshold and the quality of one or two or all currently used / indicated beams is worse than a second threshold). Preferably in some embodiments, the UE may trigger a report (for LTM) when the triggering condition for LTM is met (preferably it may further consider the first number of times that the quality of the first candidate beam is better than the quality of one or two or all currently used / indicated beams by an offset).

[0535] Preferably, in certain embodiments, for multiple TRP scenarios, the triggering condition for UE-triggered reporting may be based on a per-beam comparison or a per-beam pair comparison.

[0536] Preferably in some embodiments, for the comparison based on per-beam, the triggering condition for the UE-triggered report may be (based on) the UE identifying (at least) a first candidate beam having a quality greater than a first threshold or a second candidate beam having a quality greater than a second threshold. Preferably in some embodiments, the first candidate beam and the second candidate beam correspond to different TRPs. Alternatively and / or preferably, the triggering condition for the UE-triggered report may be (based on) the UE identifying (at least) a first candidate beam having a quality greater than a first threshold or a second candidate beam having a quality greater than a second threshold.

[0537] Preferably, in some embodiments, whether to utilize a comparison based on each beam or a comparison based on each beam pair is based on a signal. Preferably, in some embodiments, the signal may be a radio resource control (RRC) configuration, a MAC CE and / or a DCI. Preferably, in some embodiments, the signal may include one or more parameters (and / or based on the one or more parameters, the UE may determine to use a comparison based on each beam or a comparison based on each beam pair). Preferably, in some embodiments, the signal may indicate a comparison based on each beam or a comparison based on each beam pair. Preferably, in some embodiments, the signal may indicate enabling / disabling a comparison based on each beam and / or enabling / disabling a comparison based on each beam pair. Preferably, in some embodiments, the signal may be per-characteristic. Preferably, in some embodiments, a characteristic may be a frequency range (e.g., FR1, FR2, FR2-2, FR3), a frequency band, a TRP, a BWP, a serving cell, a carrier, a UE, a beam, a beam pair, a type of report, a report. Preferably, in some embodiments, the same characteristic (e.g., the same BWP) can be associated with the same operation (e.g., comparison based on each beam or each beam pair) based on a signal per characteristic. Preferably, in some embodiments, different characteristics can be associated with the same or different operations based on a signal per characteristic. Preferably, in some embodiments, one or more characteristics can share a signal (e.g., the signal is applied to the one or more characteristics). Preferably, in some embodiments, based on the signal, the UE determines whether to trigger a report based on a beam pair comparison. Preferably, in some embodiments, for each report of the first category, the UE can be configured with a signal (for indicating whether the report is triggered based on a beam pair comparison or a beam based comparison).

[0538] Preferably in certain embodiments, the UE receives a TCI state (de-)activation MAC CE, wherein the MAC CE indicates an association between the TCI state and one or more code points in the TCI field in the DCI.

[0539] Preferably, in some embodiments, there are no code points associated with more than one or two same-direction TCI states (e.g., the same DL or the same UL), and the UE operates in a single TRP operation. Preferably, in some embodiments, the UE receives a (beam indication) DCI indicating a first TCI state via the TCI field of the beam indication DCI. Preferably, in some embodiments, the first TCI state corresponds to one "indicated TCI state". Preferably, in some embodiments, the UE will determine the currently used TCI state for triggering UE reporting based on the one indicated TCI state (e.g., the first TCI state). Preferably, in some embodiments, the first TCI state is on the first serving cell. Preferably, in some embodiments, the UE will receive a UE-specific channel or signal based on the one indicated TCI state (e.g., a quasi-co-location (QCL) assumption with a first RS associated with the first TCI state). Preferably, in some embodiments, the UE may be configured with one or more RSs (and / or one or more TCI states) associated with a cell. Preferably, in some embodiments, the one or more RSs (or the one or more TCI states) are candidate RSs (or candidate TCI states). Preferably, in some embodiments, the one or more RSs may be configured via an RS list. Preferably, in some embodiments, the cell includes a first serving cell, a second serving cell, a third cell (which is an additional cell with a different PCI and is associated with the first serving cell), a fourth cell (which is an additional cell with a different PCI and is associated with the second serving cell) and / or a fifth cell (which has no association with the first serving cell or the second serving cell).

[0540] Preferably in some embodiments, the UE determines whether to trigger a first (type of) report based on both the currently used / indicated TCI state and at least one candidate TCI state. Preferably in some embodiments, the first (type of) report may correspond to an LTM (i.e., inter-cell) or a serving beam change (i.e., intra-cell). Preferably in some embodiments, the triggering condition for the first (type of) report may be (based on) the quality of the currently used / indicated TCI state being lower than a threshold and the quality of the at least one candidate TCI state being higher than a second threshold. Alternatively and / or preferably, the triggering condition for the first (type of) report may be (based on) the quality of the at least one candidate TCI state being higher than the quality of the currently used / indicated TCI state by an offset. Preferably in some embodiments, once the triggering condition is met, the UE triggers the generation of the first (type of) report and / or the transmission of the first (type of) report. Preferably in some embodiments, the first (type of) report may correspond to a first sub-report of a serving cell change. Preferably in some embodiments, the first (type of) report may correspond to a second sub-report of a serving cell not changing. Preferably in some embodiments, it may depend on whether the candidate RSs are associated with the same serving cell (eg, the first serving cell).

[0541] Preferably in some embodiments, the UE determines whether to trigger the second (kind of) report based on (only) the candidate TCI state (without additionally considering the currently used / indicated TCI state). Preferably in some embodiments, the UE triggers the second (kind of) report when the quality of the candidate TCI state is higher than a third threshold. Preferably in some embodiments, the UE triggers the second (kind of) report when the quality of the currently used / indicated TCI state is not lower than the threshold. Preferably in some embodiments, the UE triggers the second (kind of) report when the quality of the currently used / indicated TCI state is not lower than the quality of the candidate TCI state by an offset. Preferably in some embodiments, in view of the above, the second (kind of) report is not triggered for assisting the network node to perform serving beam / cell switching. In fact, the second (kind of) report is triggered for assisting the network node to perform a certain number of TRP / beam / TCI state scheduling / activation / addition. Preferably in some embodiments, the second (kind of) report may correspond to a candidate beam addition without a serving beam change. Preferably in some embodiments, once the triggering condition is met, the UE triggers the generation of the second (kind of) report and / or the transmission of the second (kind of) report.

[0542] For example, in Fig.10In the embodiment, the UE triggers the first (type of) report when both the quality associated with the candidate RS and the quality associated with the indicated RS are satisfied. In addition, satisfying the quality associated with the candidate RS and the quality associated with the indicated RS may correspond to a count, and the UE triggers the first (type of) report when there are # number of events (associated with the first type of report) being satisfied.

[0543] exist Fig.10 In the embodiment, the UE triggers the second (type of) report when the quality associated with the candidate RS is met and the quality associated with the indicated RS is not met. Alternatively and / or preferably, the UE triggers the second (type of) report when the quality associated with the candidate RS is met (regardless of whether the quality associated with the indicated RS is met). In addition, satisfying the quality associated with the candidate RS and the quality associated with the indicated RS may correspond to a count, and the UE triggers the second (type of) report when there is a # number of events (associated with the second type of report) being met.

[0544] Preferably in some embodiments, the triggering condition for the first (kind of) report or the second (kind of) report may be (further) based on:

[0545] a first number of times the quality of the currently used / indicated TCI state is below a threshold and the quality of the at least one candidate TCI state is above a second threshold, or

[0546] the quality of the at least one candidate TCI state is higher than the quality of the currently used / indicated TCI state by an offset a second number of times, or

[0547] The quality of the candidate TCI state is above a third threshold for a third number of times.

[0548] Preferably in some embodiments, the first number, the second number and the third number can be (pre-)configured or specified.

[0549] Preferably, in some embodiments, the first number, the second number and the third number may be (pre-)configured or specified based on UE capabilities.

[0550] Preferably in some embodiments, the first number, the second number and the third number can be different values ​​or the same value.

[0551] Preferably in some embodiments, the third number may be smaller than the first number or the second number.

[0552] Preferably, in some embodiments, the triggering condition for the first (type) report or the second (type) report may be based at least on information or configuration associated with the candidate RS. Preferably, in some embodiments, RSs on different cells may correspond to the same or different triggering conditions. Preferably, in some embodiments, RSs on the same cell may correspond to the same or different triggering conditions. For example, in Fig.11 , RS1 on cell 1 corresponds to the indicated TCI state, and the UE has or is configured with RS2-7 on cells 1, 1, 2, 3, 4, 5, respectively. Cell 1 and cell 2 are serving cells, and cell 3 and cell 4 are additional cells in addition to cell 1 and cell 2, respectively. Cell 5 is a cell having a PCI different from that of the serving cell and having no association with the serving cell (e.g., cell 1 and cell 2). It can be shown that each RS can have associated parameters related to the first (type) report and / or parameters related to the second (type) report. Preferably, in some embodiments, different RSs can be associated with different parameters. Preferably, in some embodiments, different (types) of reports can be associated with the same or different parameters. In one example, for the second (type) report, the parameters for the candidate RS in the serving cell can be configured with conditions that are triggered more frequently than the candidate RS on the non-serving cell (e.g., cells 3, 4, 5) (e.g., fewer times of triggering reports, loose thresholds for comparison). For candidate RSs on additional cells associated with the serving cell, a more frequent triggering condition may be associated with candidate RSs on cells that do not have an association with the serving cell. Preferably, in some embodiments, (even more), candidate RSs on cells with the same frequency band may be associated with a more frequent triggering condition than candidate RSs on cells in different frequency bands. The parameters may correspond to the # of times to trigger (UE-triggered) reports, an offset (for comparing L1 / L3-RSRP), a threshold associated with the candidate RS (also relevant for reports of the first category) (e.g., Fig.10 ), a threshold value associated with a candidate RS (also related to a second type of report) (eg, Fig.10 , and / or a threshold value associated with the currently used / indicated RS (e.g., Fig.10), and / or information about which kind of report and / or which explicit indication / signaling (e.g., eventA3, A4, A5) is used for the triggering condition. Alternatively and / or preferably, based on the presence / absence of one or more parameters, the UE may determine which triggering condition to use. Preferably in some embodiments, based on whether the candidate RS is on the serving cell, the UE determines whether the triggered condition is for LTM. Preferably in some embodiments, one of the # times corresponds to a time instance when the UE identifies that the triggering condition is met. Preferably in some embodiments, the UE triggers a report when the # times is reached. Preferably in some embodiments, it may be shown that the UE triggers a report when a sufficient number of satisfactory events are accumulated. Preferably in some embodiments, one candidate RS with one indicated RS may correspond to one event. Preferably in some embodiments, a pair of candidate RSs with a pair of indicated RSs may correspond to one event. Alternatively and / or preferably, there may be no long-term check (without # times), and in this case, a default number (e.g., 1) will be applied, or the UE will trigger a report once the triggering condition is met.

[0553] Preferably, in certain embodiments, when the UE receives a TCI state (de)activation MAC CE, the MAC CE indicates an association between the TCI state and one or more code points in the TCI field in the DCI.

[0554] Preferably in certain embodiments, when there is at least one code point associated with two same-direction TCI states (e.g., the same DL or the same UL), the UE operates in multi-TRP operation. Preferably in certain embodiments, the UE receives a (beam indication) DCI indicating a first TCI state and a second TCI state via the TCI field of the beam indication DCI. Preferably in certain embodiments, the first TCI state or the second TCI state corresponds to two "indicated TCI states". Preferably in certain embodiments, the first TCI state or the second TCI state corresponds to a pair of "indicated TCI states". Preferably in certain embodiments, the first TCI state and the second TCI state correspond to the same direction (e.g., both DL or both UL). Preferably in certain embodiments, the UE will determine the currently used TCI state for triggering UE reporting based on the two indicated TCI states (e.g., the first TCI state and the second TCI state). Preferably in certain embodiments, the first TCI state is on the first serving cell. Preferably in certain embodiments, the second TCI state is on the second serving cell. Preferably, in certain embodiments, the UE will receive a UE-specific channel or signal (e.g., a QCL assumption with a first RS associated with a first TCI state and / or a QCL assumption with a second RS associated with a second TCI state) based on one or both of the two indicated TCI states. Preferably, in certain embodiments, the UE may be configured with one or more RSs (and / or one or more TCI states) associated with a cell. Preferably, in certain embodiments, the one or more RSs (or the one or more TCI states) are candidate RSs (or candidate TCI states). Preferably, in certain embodiments, the one or more RSs may be configured via an RS list. Preferably, in certain embodiments, the one or more RSs may be configured via two RS lists. Preferably, in certain embodiments, one of the two RS lists corresponds to a first TRP and the other of the two RS lists corresponds to a second TRP. Preferably, in certain embodiments, the trigger condition is based on a comparison between the RSs in the list and the first indicated TCI state or the second indicated TCI state associated with the same TRP. Preferably, in some embodiments, the cell includes a first service cell, a second service cell, a third cell (which is an additional cell with a different PCI and is associated with the first service cell), a fourth cell (which is an additional cell with a different PCI and is associated with the second service cell), and / or a fifth cell (which has no association with the first service cell or the second service cell).

[0555] Preferably in some embodiments, the UE determines whether to trigger a first (type of) report based on one or both of the currently used / indicated TCI state and at least one candidate TCI state. Preferably in some embodiments, the first (type of) report may correspond to at least one of an LTM (i.e., inter-cell) or a service beam change (i.e., intra-cell). Preferably in some embodiments, the triggering condition for the first (type of) report may be that the quality of at least one of the two currently used / indicated TCI states is lower than a threshold and the quality of the at least one candidate TCI state is higher than a second threshold. Alternatively and / or preferably, the triggering condition for the first (type of) report may be that the quality of the at least one candidate TCI state is higher than the quality of at least one of the two currently used / indicated TCI states by an offset. Preferably in some embodiments, once the triggering condition is met, the UE triggers the generation of the first (type of) report and / or the transmission of the first (type of) report. Alternatively and / or preferably, the UE determines whether to trigger a first (kind of) report associated with LTM based on a TCI state associated with CORESET 0, or based on a TCI state associated with a first indicated TCI state, or based on a TCI state associated with common PDCCH monitoring, or based on a TCI state associated with a serving cell. In other words, the currently used / indicated TCI state (for determining whether to trigger a first kind of report associated with LTM) corresponds to the TCI state associated with CORESET 0, or the TCI state associated with the first indicated TCI state, or the TCI state associated with common PDCCH monitoring, or the TCI state associated with a serving cell.

[0556] Preferably in some embodiments, the UE may be configured with a per-TRP list of RSs. Preferably in some embodiments, the UE may be configured with two lists of RSs. Preferably in some embodiments, when the UE determines whether to trigger a first (kind of) report, the currently used RS corresponds to the first indicated TCI state, and the first candidate RS is in the first list of RSs. Preferably in some embodiments, when the UE determines whether to trigger a first (kind of) report, the currently used RS corresponds to the second indicated TCI state, and the second candidate RS is in the second list of RSs. Preferably in some embodiments, the first list of RSs is associated with the first indicated TCI state. Preferably in some embodiments, the second list of RSs is associated with the second indicated TCI state. Preferably in some embodiments, cross-list comparisons with non-associated indicated TCI states are not allowed or prohibited.

[0557] Preferably in some embodiments, the UE determines whether to trigger the second (kind of) report based on (only) the candidate TCI state (without additionally considering the currently used / indicated TCI state). Preferably in some embodiments, the UE triggers the second (kind of) report when the quality of the candidate TCI state is above a third threshold. Preferably in some embodiments, the UE triggers the second (kind of) report when the quality of the currently used / indicated TCI state is not lower than the threshold. Preferably in some embodiments, the UE triggers the second (kind of) report when the quality of the currently used / indicated TCI state is not lower than the quality of the candidate TCI state by an offset. Preferably in some embodiments, in view of the above, the second (kind of) report is not triggered for assisting the network node in performing a serving beam / cell switching. In fact, the second (kind of) report is triggered for assisting the network node in scheduling / activating / adding a certain number of TRPs / beams / TCI states. Preferably in some embodiments, the second (kind of) report may correspond to a candidate beam addition without a serving beam change. Preferably in some embodiments, once the triggering condition is met, the UE triggers the generation of the second (kind of) report and / or the transmission of the second (kind of) report.

[0558] Preferably, in some embodiments, the triggering condition for the first (type of) report or the second (type of) report may be based at least on information or configuration associated with the candidate RS. Preferably, in some embodiments, RSs on different cells may correspond to the same or different triggering conditions. Preferably, in some embodiments, the RSs on the same cell may correspond to the same or different triggering conditions. For example, in Fig.12In it can be shown that each RS can have associated parameters related to the first (type) report and / or parameters related to the second (type) report. Preferably, in some embodiments, different RSs can be associated with different parameters. Preferably, in some embodiments, different (types) of reports can be associated with the same or different parameters. In one example, for the second (type) of reports, the parameters for the candidate RS in the serving cell can be configured with conditions that are triggered more frequently than the candidate RS on the non-serving cell (e.g., cells 3, 4, 5) (e.g., fewer times of triggering reports, loose thresholds for comparison). For candidate RSs on additional cells associated with the serving cell, they can be associated with conditions that are triggered more frequently than candidate RSs on cells that do not have an association with the serving cell. Preferably, in some embodiments, (even more), the candidate RSs on cells with the same frequency band can be associated with conditions that are triggered more frequently than candidate RSs on cells in different frequency bands. The parameters may correspond to # of times to trigger (UE triggered) reporting, an offset (for comparing L1 / L3-RSRP), a threshold value associated with the candidate RS (also related to the first category of reporting and the first indicated TCI state) (e.g. Fig.12 ), a threshold value (eg, threshold_c1 in ), associated with the candidate RS (also associated with the first type of report and the second indicated TCI state) Fig.12 , threshold_c3 in ), a threshold value associated with the candidate RS (also associated with the second type of report and the first indicated TCI state) (e.g., Fig.12 , threshold_c2 in ), a threshold value associated with the candidate RS (also associated with the second type of report and the second indicated TCI state) (e.g., Fig.12 , and / or a threshold value associated with the currently used / indicated RS and the first indicated TCI state (e.g., Fig.12 ), a threshold value associated with the currently used / indicated RS and a second indicated TCI state (eg, Fig.12, threshold_c2 and / or threshold_c4) in the second category of reports, and / or information about which kind of report and / or which kind of explicit indication / signaling (e.g., eventA3, A4, A5) is used for the triggering condition, information about which list indicating the TCI state (e.g., the first / second indicated TCI state). Alternatively and / or preferably, based on the presence / absence of one or parameters, the UE can determine which triggering condition to use. For example, when the parameters associated with the second kind of report (e.g., threshold_c2 and / or threshold_c4) are not present, the triggering condition associated with the first kind of report is used. Preferably in some embodiments, based on the candidate RS being on or not on the serving cell, the UE determines whether the triggered condition is for LTM. Preferably in some embodiments, based on one or two currently used / indicated RSs having a quality below a (corresponding) threshold, the UE determines whether the triggered condition is for LTM. Preferably in some embodiments, one of the # times corresponds to a time instance at which the UE identifies that the triggering condition is met. Preferably in some embodiments, the UE triggers a report when the # times is reached. Preferably in some embodiments, it may be shown that the UE triggers a report when a sufficient number of satisfactory events are accumulated. Preferably in some embodiments, one candidate RS with one indicated RS may correspond to one event. Preferably in some embodiments, a pair of candidate RSs with a pair of indicated RSs may correspond to one event. Alternatively and / or preferably, there may be no long-term check (without # times), in which case a default number (e.g., 1) will be applied, or the UE will trigger a report once the trigger condition is met.

[0559] For example, in Fig.12Among them, similar to single TRP, mTRP operations can be regarded as two single TRP operations respectively. The currently used / indicated TCI state associated with at least one TRP has a quality lower than the (corresponding) threshold, and the UE triggers a report. The event can be a TRP-specific configuration and satisfied (each TRP can be associated with a corresponding event that triggers a report). At a time instance, the UE triggers a first (type of) report for the first TRP (or for the first indicated TCI state) and a second (type of) report for the second TRP (or for the second indicated TCI state). The comparison for triggering the first (type of) report is based on each TRP or each indicated TCI state. In this instance, when the UE determines whether to trigger the first (type of) report for the first TRP, the quality associated with the first indicated TCI state is used as Q1, and / or preferably in some embodiments, threshold1 associated with the first indicated TCI state or the first TRP. On the other hand, when the UE determines whether to trigger the second (type of) report for the second TRP, the quality associated with the second indicated TCI state is used as Q2, and / or preferably in some embodiments, threshold2 associated with the second indicated TCI state or the second TRP. For another instance, Qc1 corresponds to the quality associated with the first candidate RS, and the first candidate RS can be associated with the first TRP. Qc2 corresponds to the quality associated with the second candidate RS, and the second candidate RS can be associated with the second TRP. Preferably in some embodiments, the UE can be configured with two lists of RSs, as Fig.13 shown. Preferably in some embodiments, the first candidate RS is selected or identified or determined or utilized from the first list of RSs (associated with the first TRP). Preferably in some embodiments, the second candidate RS is selected or identified or determined or utilized from the second list of RSs (associated with the second TRP). Alternatively and / or preferably, the UE is configured with one list of RSs. Preferably in some embodiments, the UE determines whether to trigger the first (type of) report based on the comparison of the quality of the candidate RS with the currently used / indicated RS. Preferably in some embodiments, when comparing the quality of the candidate RS and the currently used / indicated RSs of the two TRPs, at least one of the currently used / indicated RSs of one TRP is determined to trigger a report or to satisfy the event compared with the candidate RS. In Fig.12 the instance of, Qc1 > Q1 + offset1, or Qc1 > threshold_c1 & Q1 < threshold1, or Qc1 > Q2 + offset2, or Qc1 > threshold_c1 & Q2 < threshold2, which means Qc1 is used to compare Q1 and A2. And once Qc1 is at least better than Q1 or Q2, the UE triggers a report.

[0560] For example, in Fig.13 In the embodiment, the UE is configured with two lists of RSs, where one list of RSs (the upper list) is associated with a first indicated TCI state (e.g., RS1, cell 1), and the other list of RSs (the lower list) is associated with a second indicated TCI state (e.g., RS2, cell 2).

[0561] Alternatively and / or preferably, a beam pair-based comparison is utilized. Preferably, in some embodiments, the UE determines whether to trigger a first (type of) report based on a currently used / indicated TCI state and at least one pair of candidate TCI states including a first candidate TCI state and a second candidate TCI state. More specifically, when the quality associated with the first candidate TCI state and the quality associated with the second candidate TCI state are opposite / better than the first currently used / indicated TCI state and the second currently used / indicated TCI state, respectively, the UE triggers the first (type of) report. Preferably, in some embodiments, when the quality associated with the first candidate TCI state and the quality associated with the second candidate TCI state are opposite / better than the corresponding threshold, the UE triggers the second (type of) report. Alternatively and / or preferably, when at least the quality associated with the first candidate TCI state is opposite / better than the corresponding threshold or the quality associated with the second candidate TCI state is opposite / better than the corresponding threshold, the UE triggers the second (type of) report. Preferably, in some embodiments, a beam pair-based comparison is used to assist the network node in single frequency network (SFN) operation or coherent joint transmission (CJT) operation. Preferably in some embodiments, it may assist the network node to change a pair of beams instead of changing one beam, which may cause disruption such that the UE may not receive better performance after changing only one beam.

[0562] For example, in Fig.14 In the embodiment of the present invention, the UE triggers a report based on a beam pair based comparison. The beam pair based comparison can be used for the first and second (kinds of) reports. Alternatively and / or preferably, the beam pair based comparison can be used for only the first (kind of) report. Alternatively and / or preferably, the beam pair based comparison can be used for only the second (kind of) report.

[0563] Preferably in some embodiments, the first (type of) report or the second (type of) report corresponds to a UE-triggered report.

[0564] Preferably in certain embodiments, the UE receives a TCI state (de)activation MAC CE per CORESETPoolIndex or per TRP, wherein the per CORESETPoolIndex MAC CE indicates an association between the TCI state and one or more code points in the TCI field in the DCI for one CORESETPoolIndex or for one TRP.

[0565] Due to the non-ideal backhaul for mDCI mTRP (e.g., UE is configured with CORESETPoolIndex), the trigger conditions for reporting will be per TRP operation (e.g., mTRP operation can be considered as two single TRP operations respectively). The trigger conditions for the first (type) of reporting and the trigger conditions for the second (type) of reporting can be found in Fig.12 and / or with Fig.12 Related description. Preferably, in some embodiments, the UE respectively receives a first (beam indication) DCI (for a first TRP, for example, CORESETPoolIndex=0) indicating a first TCI state (which is the first indicated TCI state or the currently used / indicated TCI state) and receives a second DCI (for a second TRP, for example, CORESETPoolIndex=1) indicating a second TCI state (which is the second indicated TCI state or the currently used / indicated TCI state).

[0566] Preferably, in some embodiments, the candidate RSs (or TCI states) may have different priorities. Preferably, in some embodiments, the candidate RSs on the cells in the same frequency band may have a higher priority than the candidate RSs on the cells in different frequency bands. Preferably, in some embodiments, the candidate RSs on the serving cell may have a higher priority than the candidate RSs on the non-serving cell. Preferably, in some embodiments, the candidate RSs that are not activated may have a higher priority than the candidate RSs that are activated (or in the activation command). Preferably, in some embodiments, the UE may be configured with a trigger condition for each priority. Preferably, in some embodiments, the UE may be configured with a trigger condition for each candidate RS (or TCI state). Preferably, in some embodiments, the priority may correspond to 1 to 4, where lower values ​​have higher priority.

[0567] Preferably in some embodiments, the priority here can be used as an order for inclusion in a time instance (or in a report). Preferably in some embodiments, when the capacity of the resources for one (UE triggered) report cannot include all triggered candidate RSs (associated with the first / second category of reports), the UE prioritizes from higher priority to lower priority to include candidate RSs or reports associated with candidate RSs or triggering conditions. Preferably in some embodiments, for candidate RSs with lower priority, the UE does not include information associated with the candidate RS or triggered reports into the resources for one (UE triggered) report.

[0568] Preferably in some embodiments, different candidate RSs (or TCI states) may have different conditions for triggering a report. Preferably in some embodiments, a candidate RS on a serving cell or (already) in an activation command may be configured with conditions that trigger for reporting more frequently than a candidate RS on an additional cell or non-serving cell or not in an activation command. Preferably in some embodiments, a candidate RS with a higher priority may be configured with a smaller number of times (the event is satisfied) for triggering a report than a candidate RS with a lower priority.

[0569] Preferably in certain embodiments, whether the UE transmits a (UE triggered) report may depend on whether the MAC PDU may include the first (kind of) report.

[0570] Preferably in some embodiments, once the (UE triggered) report is triggered, the UE will generate a (UE triggered) report. Preferably in some embodiments, the UE generates a (UE triggered) report by setting the content associated with the currently used / indicated TCI state, one or more candidate TCI states. Preferably in some embodiments, the content of the (UE triggered) report may include the quality of the used / indicated TCI state, the quality of the one or more candidate TCI states, an explicit indication of the first or second (kind of) report, the triggering condition, the cell identity (ID) (of the triggered cell), the BWP ID, and / or the number of triggering events in one reporting instance. Preferably in some embodiments, the content of the (UE triggered) report may include information associated with which TRP or which indicated TCI state (e.g., the first indicated TCI state or the second indicated TCI state) is associated with the (UE triggered) report.

[0571] Preferably in some embodiments, one report instance may be associated with a (UE triggered) report of one or more triggering events. Preferably in some embodiments, one report instance may be associated with a (UE triggered) report of one or more triggered cells and / or BWPs. Preferably in some embodiments, one report instance may be associated with one or more first (kind of) reports and / or second (kind of) reports. Preferably in some embodiments, one report instance may be associated with only (triggered) reports of the same kind. Preferably in some embodiments, one report instance means or corresponds to the same timing report.

[0572] Preferably, in some embodiments, the UE is configured with an RS list. Preferably, in some embodiments, the one RS list is used to trigger a report. Preferably, in some embodiments, the RS in the one RS list may be configured with information of a trigger condition. Preferably, in some embodiments, the trigger condition may check only the candidate RS, or check both the candidate RS and the serving RS. Preferably, in some embodiments, the trigger condition is associated with a single TRP context, a multi-TRP context, and an LTM. Preferably, in some embodiments, when the UE is configured with an RS associated with a certain trigger condition, the triggered report may not include information associated with the trigger condition (because the RS index in the one RS list may refer to the triggered condition). Alternatively and / or preferably, the UE may be configured with an RS list for LTM and another RS ​​list for non-LTM. Preferably, in some embodiments, for the one RS list for LTM, the RS in the RS list is on one or more cells that are different from the serving cell and are preferably additional cells. Preferably, in some embodiments, for another RS ​​list for non-LTM, the RS in the RS list is on one or more cells that are serving cells and are preferably additional cells. For a single TRP scenario, the UE may be configured with one RS list including RSs associated with a serving cell and another RS ​​list including RSs different from the serving cell (i.e., a non-serving cell or a cell with an additional PCI).

[0573] Alternatively and / or preferably, the UE may be configured with two RS lists, one of which is used to determine whether the current / used beam is bad, and the other RS ​​list is used to determine candidate beams. Preferably in some embodiments, the two RS lists are configured per TRP (for example, one TRP is configured with two RS lists). Preferably in some embodiments, each RS list may be configured with information associated with a trigger condition. Preferably in some embodiments, each RS in an RS list may be configured with information associated with a trigger condition.

[0574] Preferably in some embodiments, the one or more indicated TCI states are indicated by the same beam indication DCI.

[0575] Preferably, in some embodiments, the UE receives a first beam indication DCI indicating a first TCI state.

[0576] Preferably, in some embodiments, when there is no code point including more than one same-direction TCI state and the UE receives a second beam indication DCI indicating a second TCI state, the UE performs UE-specific reception based on the second TCI state (which is a change from the first TCI state to the second TCI state) and preferably after a specific timing. Preferably, in some embodiments, the specific timing corresponds to the timing applied by the UE to the second TCI state (which is the beam application time after the timing for transmitting a hybrid automatic repeat request (HARQ) associated with the second beam indication DCI). Preferably, in some embodiments, the first TCI state may be a currently used / indicated TCI state used to determine whether to trigger a report (before a specific timing). Preferably, in some embodiments, the second TCI state may be a currently used / indicated TCI state used to determine whether to trigger a report (after a specific timing).

[0577] Preferably, in some embodiments, the UE receives a first beam indication DCI indicating a first TCI state and a third TCI state (having the same direction).

[0578] Preferably, in some embodiments, when there is at least one code point including more than one same-direction TCI state and the UE receives a second beam indication DCI indicating a second TCI state (for updating a first or third TCI state), the UE performs UE-specific reception based on the second TCI state (which is a change from the first TCI state or the third TCI state to the second TCI state) and preferably after a specific timing. Preferably, in some embodiments, the specific timing corresponds to the timing applied by the UE to the second TCI state (which is the beam application time after the timing for transmitting the HARQ associated with the second beam indication DCI). Preferably, in some embodiments, the first TCI state and the third TCI state may be the currently used / indicated TCI state for determining whether to trigger reporting (before the specific timing). Preferably, in some embodiments, based on which TCI state is updated by the second TCI state, (the first TCI state and the second TCI state) or (the third TCI state and the second TCI state) may be the currently used / indicated TCI state for determining whether to trigger reporting (after the specific timing).

[0579] By way of example, one or more of the following trigger conditions for UE-triggered reporting may be used by the UE, e.g., for non-LTM scenarios and / or for single TRP scenarios:

[0580] ● The quality (plus or minus an offset) of at least one candidate beam of the serving cell is greater than (or equal to) a threshold;

[0581] ● The quality (plus or minus an offset) of at least one currently used / indicated beam of the serving cell is less than (or equal to) a threshold;

[0582] The quality (plus or minus an offset) of at least one candidate beam of the serving cell is greater than (or equal to) the quality (plus or minus an offset) of at least one currently used / indicated beam of the serving cell;

[0583] ● the beam / TCI state / RS indicated by a UE-triggered report associated with the serving cell is different from the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report associated with the serving cell; and / or

[0584] ●The quality (plus or minus an offset) of the beam / TCI state / RS indicated by the UE-triggered report is different from (e.g., greater than (or equal to) or less than (or equal to)) the quality (plus or minus an offset) of the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, non-periodic, or semi-persistent) report.

[0585] By way of example, one or more of the following trigger conditions for UE-triggered reporting may be used by the UE, e.g., for non-LTM scenarios and / or for multi-TRP scenarios:

[0586] ● The quality (plus or minus an offset) of at least one currently used / indicated beam of the serving cell is less than (or equal to) a threshold;

[0587] ● The quality (plus or minus an offset) of at least one candidate beam of the serving cell is greater than (or equal to) the quality (plus or minus an offset) of at least one currently used / indicated beam of the serving cell (and preferably, the at least one candidate beam of the serving cell and the at least one currently used / indicated beam of the serving cell are associated with the same TRP or the same UE panel). Preferably, in certain embodiments, if the at least one currently used / indicated beam is replaced by the at least one candidate beam and both are associated with the same TRP or the same UE panel, the operation of multiple TRPs will still work;

[0588] ● the beam / TCI state / RS indicated by a UE-triggered report associated with the serving cell is different from the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report associated with the serving cell; and / or

[0589] ●The quality (plus or minus an offset) of the beam / TCI state / RS indicated by the report triggered by the UE is different from (for example, greater than (or equal to) or less than (or equal to)) the quality (plus or minus an offset) of the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, non-periodic or semi-persistent) report.

[0590] By way of example, one or more of the following trigger conditions for UE-triggered reporting may be used by the UE, e.g., for LTM contexts:

[0591] ● The quality (plus or minus an offset) of at least one candidate beam of the candidate cell is greater than (or equal to) a threshold;

[0592] The quality (plus or minus an offset) of at least one candidate beam of the candidate cell is greater than (or equal to) the quality (plus or minus an offset) of at least one currently used / indicated beam of the PCell or SpCell (e.g., not considering the PSCell or SCell);

[0593] ● the beam / TCI state / RS indicated by a UE-triggered report associated with the candidate cell is different from the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report associated with the candidate cell; and / or

[0594] ●The quality (plus or minus an offset) of the beam / TCI state / RS indicated by the report triggered by the UE is different from (for example, greater than (or equal to) or less than (or equal to)) the quality (plus or minus an offset) of the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, non-periodic or semi-persistent) report.

[0595] Which trigger condition for UE triggered reporting is to be enabled (e.g., used by the UE) may be based on a configuration from the network, e.g., the network explicitly indicates which trigger condition is to be enabled. Parameters of the trigger condition for UE triggered reporting, such as thresholds and / or offsets, may be configured by the network. Whether the trigger condition for UE triggered reporting is enabled (e.g., used by the UE) may be based on whether the UE is configured with a configuration for LTM (e.g., candidate cells / configuration for LTM) and / or whether the UE is served by multiple TRPs (beams / TCI states / RS associated with multiple TRPs are activated) or is configured with a configuration for multiple TRPs (e.g., more than one CORESET pool for serving cells), e.g., the network does not explicitly indicate which trigger condition is to be enabled.

[0596] The triggering conditions of the UE-triggered report applicable to (or allowed to be configured for) one of the scenarios may not be applicable to (or not allowed to be configured for) another of the scenarios. The scenarios include a single TRP, multiple TRPs and / or LTMs.

[0597] The format of the UE triggered report for one of the scenarios may be different from that for another of the scenarios. The scenarios include a single TRP, multiple TRPs and / or LTM.

[0598] A UE triggered report not for LTM may indicate a serving cell associated with at least one currently used / indicated beam and / or at least one candidate beam indicated by the UE triggered report. A UE triggered report for LTM may not indicate a serving cell.

[0599] Preferably, in certain embodiments, throughout this disclosure, "A of B" may be replaced by "A associated with B".

[0600] Preferably, in certain embodiments, throughout this disclosure, "A for B" may be replaced by "A associated with B".

[0601] Preferably, in certain embodiments, throughout this disclosure, “the quality of A” or “the quality associated with A” corresponds to the channel quality measured based on A.

[0602] Preferably, in certain embodiments, throughout this disclosure, "quality" may be L1-RSRP, L3-RSRP (with long-term average), L1-Signal to Interference and Noise Ratio (SINR), L3-SINR (with long-term average).

[0603] Preferably, in certain embodiments, throughout this disclosure, "beam" may be replaced by "TCI state", "spatial relationship", "spatial filter", "QCL (Type D) assumption" or "RS".

[0604] Preferably, in certain embodiments, throughout the present disclosure, "RS" and "TCI state" may be replaced inversely, which means that the source RS of the TCI state is RS.

[0605] Preferably in certain embodiments throughout this disclosure, the threshold corresponds to an RSRP threshold or a SINR threshold based on which the quality is defined or specified.

[0606] Preferably, in certain embodiments, throughout this disclosure, "one currently used / indicated RS" may be replaced by "one serving RS".

[0607] Preferably, in some embodiments, the first (type of) report or the second (type of) report corresponds to a report triggered by the UE.

[0608] Preferably, in some embodiments, the RS may be a synchronization signal (SS)-physical broadcast channel (PBCH), a CSI-RS for CSI, a CSI-RS for tracking, or a CSI-RS for beam management.

[0609] Preferably in some embodiments, the RS may be replaced by an RS resource.

[0610] Preferably, in certain embodiments, throughout the present disclosure, the currently used beam may be applied to or may be on a PCell, a PSCell or a SCell.

[0611] Preferably, in certain embodiments, throughout the present disclosure, "beam" may be replaced by "beam of a cell", and vice versa.

[0612] Preferably, in certain embodiments, throughout the present disclosure, beam A and beam B being associated with the same TRP or the same UE panel may correspond to beam A and beam B being associated with the same CORESETPoolIndex.

[0613] Preferably, in certain embodiments, throughout the present disclosure, beam A and beam B being associated with the same TRP or the same UE panel may correspond to beam A and beam B being associated with the same order of indicated TCI states (e.g., the 1st indicated TCI state or the 2nd indicated TCI state).

[0614] Preferably, in certain embodiments, throughout this disclosure, "an indicated TCI state" corresponds to "one or more TCI states associated with the same code point of the TCI field in one beam indication DCI".

[0615] Preferably, in certain embodiments, throughout the present disclosure, for each code point of the TCI field in the DCI including TCI state p and TCI state q associated with the same direction, the TCI state p or TCI state q with a lower octet index in the TCI state (de)activation MAC CE is or corresponds to or is associated with the first TRP, and the TCI state p or TCI state q with a higher octet index in the TCI state (de)activation MAC CE is or corresponds to or is associated with the second TRP.

[0616] Alternatively and / or preferably, throughout the present disclosure, for each code point of the TCI field in the DCI that includes TCI state p and TCI state q associated with the same direction, the TCI state (de)activation MAC CE provides information that TCI state p or TCI state q corresponds to or is associated with the first TRP or the second TRP.

[0617] Preferably, in certain embodiments, throughout the present disclosure, when the beam indication DCI indicates a TCI state associated with a first TRP, the TCI state associated with the first TRP is or corresponds to the 1st (or first) indicated TCI state.

[0618] Preferably, in certain embodiments, throughout the present disclosure, when the beam indication DCI indicates a TCI state associated with a second TRP, the TCI state associated with the second TRP is or corresponds to the 2nd (or second) indicated TCI state.

[0619] Preferably, in certain embodiments, throughout the present disclosure, one UE panel is associated with one TRP, or a first TRP is associated with a first UE panel and a second TRP is associated with a second UE panel.

[0620] Preferably, in certain embodiments, throughout the present disclosure, the beam indication DCI corresponds to or may be replaced by a DCI format having a TCI field indicating different TCI states of at least one TRP. More specifically, the DCI format corresponds to DCI format 1_1 or DCI format 1_2, and / or the DCI format will schedule or not schedule a downlink assignment or PDSCH.

[0621] Preferably in some embodiments, throughout the present disclosure, the quality of the currently used / indicated beam may be determined via one or more beams. Preferably in some embodiments, the quality of the currently used / indicated beam may be the average quality of all RSs in the RS list.

[0622] Preferably in certain embodiments, the UE may be configured with or enabled by UE triggered reporting.

[0623] Preferably in certain embodiments, the UE has the capability to support UE-triggered reporting.

[0624] Preferably in certain embodiments, throughout the present disclosure, the currently used beam for LTM may be applied to or may be on PCell or PSCell. Preferably in certain embodiments, for beams used for SCell operation, the UE does not trigger reporting of LTM for SCell.

[0625] Preferably, in certain embodiments, throughout the present disclosure, the currently used beam for a single TRP (sTRP) or mTRP (regardless of which cell) may be applied to or may be on a PCell, PSCell or SCell.

[0626] Preferably in certain embodiments, the network node or serving cell will indicate whether UE triggered reporting is enabled.

[0627] Preferably in some embodiments, the UE-triggered reporting is based on L1 / L2 signaling.

[0628] Preferably in certain embodiments, once RRC or L3 signaling is enabled / configured, the UE shall not use additional L3 signals for UE-triggered reporting.

[0629] Preferably, in certain embodiments, throughout the present disclosure, the (average) quality of all of the at least one currently used / indicated beams may have a weighting factor. Preferably, in certain embodiments, both the quality of the currently used / indicated beam in timing x and the quality of the currently used / indicated beam in timing y are used for the (average) quality of all of the at least one currently used / indicated beams. Preferably, in certain embodiments, both timing x and timing y are earlier than the current timing, and when timing x is closer to the current timing than timing y, the weighting for the quality of the currently used / indicated beam in timing x has more weighting.

[0630] Preferably, in certain embodiments, throughout the present disclosure, one UE panel may be replaced by one (logical) antenna port comprising a set of antenna elements. Preferably, in certain embodiments, different UE panels may be associated with different (logical) antenna ports. Preferably, in certain embodiments, an antenna port may be used for SRS transmission, PUCCH transmission, PUSCH transmission, PDSCH reception, PDCCH reception, CSI-RS reception and / or SS-PBCH reception.

[0631] Concept 2

[0632] This concept is to determine the object of RS or TCI state for determining the trigger report (for example, for determining whether the trigger condition of the UE-triggered report is met). Preferably, in some embodiments, different UE-triggered reports (trigger conditions) are based on or associated with the same or different RS or TCI states.

[0633] For the TCI state (or RS) currently used / indicated, it may be a first indicated TCI state and / or a second indicated TCI state indicating DCI through one or more beams.

[0634] For the TCI state (or RS) currently used / indicated, it can be configured by an RS list. Preferably, in some embodiments, the RS list is configured per UE, or per carrier, or per BWP, or per TRP. Preferably, in some embodiments, the RS list may include RSs associated with the TCI state indicated via the beam indication DCI. Preferably, in some embodiments, the RS list may include RSs associated with CORESET 0 or a CORESET with a common search space.

[0635] For the currently used / indicated TCI state (or RS), it can be determined from the beam failure detection RS list.

[0636] For the TCI state (or RS) currently used / indicated, the UE maintains or records or utilizes an RS list. Preferably, in some embodiments, the RS list is determined based on the TCI state of a common DL channel or signal and / or a UE-specific DL channel or signal. Preferably, in some embodiments, the RS list is determined based on the TCI state of a first set of DL channels or signals that do not use / apply a unified TCI state and / or a second set of DL channels or signals that use / apply a unified TCI state. For example, CORESET 0 is associated with TCI state x, and the beam indication DCI indicates TCI state y, then the TCI state (or RS) currently used / indicated may be TCI state x and TCI state y (e.g., the maintained RS list includes TCI state x and TCI state y). More specifically, the first set of DL channels or signals includes CORESET 0, a CORESET associated with a common search space (e.g., for paging, for system information, for RAR), and / or CSI-RS. In some instances, the CSI-RS used for beam management is not used as the currently used / indicated TCI state (preferably because such CSI-RS is used for potential beam changes or updates). In some instances, the CSI-RS used for tracking is not used as the currently used / indicated TCI state. Preferably, in certain embodiments, the unified TCI state corresponds to one or more joint / DL TCI states that indicate DCI via one or more beams.

[0637] Preferably, in some embodiments, the UE will trigger a report when the quality of at least one of the RSs in the RS list is poor. Preferably, in some embodiments, the UE will trigger a report when the quality of all RSs in the RS list is poor. Preferably, in some embodiments, the trigger condition may be further based on one or more candidate TCI states. Preferably, in some embodiments, the threshold for LTM and the threshold for beam management may correspond to different values. Preferably, in some embodiments, the poor quality of at least one RS may correspond to the quality of the at least one RS being lower than the quality of the candidate RS by an offset or the quality of the at least one RS being lower than a threshold.

[0638] For the currently used / indicated TCI state (or RS), when the UE is configured with an RS list associated with UE-triggered reporting, the currently used / indicated TCI state (or RS) is determined based on the RS list. For the currently used / indicated TCI state (or RS), when the UE is not configured with an RS list associated with UE-triggered reporting (and the UE is configured with UE-triggered reporting or enabled by UE-triggered reporting), the currently used / indicated TCI state (or RS) is determined based on the indicated TCI state and / or the activated TCI state and / or the TCI state for CORESET monitoring.

[0639] For candidate RS, the UE may be configured with a list of candidate RS associated with the UE triggered report. Preferably in some embodiments, the list of candidate RS includes one or more of the following or a subset thereof: CSI-RS-ResourceConfigMobility or CSI-ResourceConfig or CSI-SSB-ResourceSet, or NZP-CSI-RS-ResourceSet or configuration / information associated with SS-PBCH index. Alternatively and / or preferably, the UE shall maintain a list of candidate RS associated with the UE triggered report.

[0640] For candidate RSs, the UE may be configured with one or more lists of candidate RSs. Preferably in some embodiments, a first list in the one or more lists of candidate RSs is associated with candidate RSs for UE-triggered reports associated with LTM. Preferably in some embodiments, a second list in the one or more lists of candidate RSs is associated with candidate RSs for UE-triggered reports associated with a single TRP (and preferably multiple TRPs). Preferably in some embodiments, a third list in the one or more lists of candidate RSs is associated with candidate RSs for UE-triggered reports associated with multiple TRPs.

[0641] When the UE is configured with one or more candidate RS lists, the UE determines the candidate RS for the UE triggered report based on the one or more candidate RS lists. When the UE is not configured with one or more candidate RS lists, the UE determines the candidate RS for the UE triggered report based on the RS associated with one or more CSI report configurations (e.g., CSI-ReportConfig). Preferably in certain embodiments, in particular, the one or more CSI report configurations correspond to a report at least associated with the number of RSRPs. Alternatively and / or preferably, when the UE is not configured with one or more candidate RS lists, the UE determines the candidate RS for the UE triggered report based on CSI-RS-ResourceConfigMobility or CSI-ResourceConfig or CSI-SSB-ResourceSet or NZP-CSI-RS-ResourceSet or configuration / information associated with the SS-PBCH index. Alternatively and / or preferably, the UE determines candidate RSs for UE triggered reporting based on a subset of RSs from CSI-RS-ResourceConfigMobility or CSI-ResourceConfig or CSI-SSB-ResourceSet or NZP-CSI-RS-ResourceSet or configuration / information associated with the SS-PBCH index. In one instance, specific parameters will be configured per candidate RS, and / or based on specific parameters (enabled or present / absent), the UE determines whether to use or apply or determine a candidate RS for UE triggered reporting. Preferably in some embodiments, the UE is configured with a maximum number of candidate RSs for UE triggered reporting. Preferably in some embodiments, the maximum number of candidate RSs for UE triggered reporting may depend on UE capabilities. Preferably in some embodiments, different candidate cells may have different maximum numbers of candidate RSs for UE triggered reporting.

[0642] Preferably, in some embodiments, a UETriggeredCondConfig may refer to a trigger condition. Preferably, in some embodiments, a UETriggeredCondConfig (parameters related to the first (type of) report and / or parameters related to the second (type of) report) includes associations with: one or more candidate RSs, quality types (e.g., RSRP, SINR), one or more thresholds (for the currently used / indicated beam, and / or for the one or more candidate RSs), one or more offsets (for the currently used / indicated beam, and / or for the one or more candidate RSs), first or second TRP, first (type of) TRP or second (type of) TRP, beam-based triggering or beam pair-based triggering, and / or LTM or non-LTM. In one instance, a UETriggeredCondConfig corresponds to parameters related to the first (type of) report and / or parameters related to the second (type of) report (e.g., where the association Fig.11 or Fig.13 An entry in a RS in can be a UETriggeredCondConfig).

[0643] Preferably, in some embodiments, the UE may be configured with one or more UETriggeredCondConfigs. Preferably, in some embodiments, each UETriggeredCondConfig includes parameters related to the first (type) report or parameters related to the second (type) report. Preferably, in some embodiments, the UE will be configured with an association between a UETriggeredCondConfig and a candidate RS. Preferably, in some embodiments, for the UETriggeredCondConfig associated with the first (type) report, the UE will use this condition to also compare with the RS currently used / indicated. Preferably, in some embodiments, for the UETriggeredCondConfig associated with the second (type) report, the UE will use this condition to also compare with the RS currently used / indicated. Preferably, in some embodiments, distinguishing between the UETriggeredCondConfig associated with the first (type) report and the second (type) report can be based on the indication of an explicit parameter or the absence / presence of a parameter (for example, whether there is a second threshold for comparing the currently used RS). Preferably, in some embodiments, the UETriggeredCondConfig may include which root cause (trigger cause, such as LTM, beam management) or a UETriggeredCondConfig is associated with a trigger condition. Preferably in some embodiments, when UETriggeredCondConfig is associated with a first (type of) report, the UE determines whether to trigger a report based on the quality of both the currently used / indicated RS and the candidate RS associated with one UETriggeredCondConfig. Preferably in some embodiments, one UETriggeredCondConfig corresponds to LTM or non-LTM. Preferably in some embodiments, one UETriggeredCondConfig corresponds to one trigger condition.

[0644] Preferably, in some embodiments, a CSI-RS resource set or a CSI-RS resource (associated with CSI-ResourceConfig or CSI-RS-ResourceConfigMobility) is configured to be associated with a UETriggeredCondConfig (for example, it can be associated with the identity of the UETriggeredCondConfig). Preferably, in some embodiments, a CSI-RS resource set or a CSI-RS resource associated with a UETriggeredCondConfig can be used or utilized or determined as a candidate RS for UE-triggered reporting. For example, when the quality of all or at least part or at least one RS in the one CSI-RS resource set is higher than a threshold (if the UETriggeredCondConfig is not associated with the currently used / indicated RS), the UE will trigger a report. For another example, when the quality of the currently used / indicated RS is poor and the quality of all or at least part or at least one RS in the one CSI-RS resource set is good (if the UETriggeredCondConfig is associated with the currently used / indicated RS), the UE will trigger a report. Preferably in some embodiments, for one CSI-RS resource set or one CSI-RS resource configured to be associated with one UETriggeredCondConfig, the UE transmits a report associated with the one CSI-RS resource set or the one CSI-RS based on the associated CSI-ReportConfig and also the associated UETriggeredCondConfig. Preferably in some embodiments, for a second one CSI-RS resource set or a second one CSI-RS resource not configured to be associated with one UETriggeredCondConfig, the UE transmits a report associated with the second one CSI-RS resource set or the second one CSI-RS based on the associated CSI-ReportConfig. Preferably in some embodiments, one CSI-RS resource set or one CSI-RS resource configured to be associated with one UETriggeredCondConfig corresponds to a CSI-RS resource used for beam management or associated with a CSI report having a number associated with RSRP.

[0645] Alternatively and / or preferably, one UETriggeredCondConfig is associated with one CSI-RS resource or one CSI-RS resource set (e.g., one UETriggeredCondConfig may include the identity of one CSI-RS resource or one CSI-RS resource set). Based on which RS is associated with the one UETriggeredCondConfig, the UE determines a candidate RS for triggering a report. For an RS that is not associated with any UETriggeredCondConfig, this RS cannot be used to trigger a report.

[0646] Alternatively and / or preferably, one CSI-ReportConfig may be configured with an association with a UETriggeredCondConfig (e.g., one CSI-ReportConfig may include the identity of the UETriggeredCondConfig). Based on which RS is associated with one CSI-ReportConfig configured with an association with the UETriggeredCondConfig, the UE determines a candidate RS for triggering a report. For an RS associated with another CSI-ReportConfig that is not configured with an association with the UETriggeredCondConfig, this RS cannot be used to trigger a report. Preferably, in certain embodiments, for one CSI-ReportConfig configured with an association with the UETriggeredCondConfig, the UE may transmit a UE-triggered report in addition to one or more CSI reports according to the CSI-ReportConfig in a periodic / aperiodic / semi-persistent manner.

[0647] Preferably in some embodiments, one or more CSI-ReportConfigs may be associated with the same UETriggeredCondConfig. Preferably in some embodiments, one or more UETriggeredCondConfigs may be associated with the same CSI-ReportConfig.

[0648] Preferably in some embodiments, the first (kind of) report is configured or set or specified to have a higher priority than the second (kind of) report. Preferably in some embodiments, the UE will prioritize to include the first (kind of) report into the MAC PDU instead of the second (kind of) report (especially when the size of the MAC PDU cannot accommodate both the first and second types of reports).

[0649] Preferably, in some embodiments, a UETriggeredCondConfig may include parameters associated with the first TRP or the second TRP.

[0650] Preferably, in some embodiments, a UETriggeredCondConfig may include parameters associated with the first UE panel or the second UE panel.

[0651] Preferably, in some embodiments, the UE determines whether to trigger a beam pair based report based on an associated CSI-ReportConfig (e.g., groupBasedBeamReporting-v1710). Preferably, in some embodiments, this method is an implicit way of determining whether to trigger a beam pair based report based on the CSI-ReportConfig rather than (directly) based on the UETriggeredCondConfig. Preferably, in some embodiments, when the UETriggeredCondConfig is associated with a CSI-ReportConfig configured with group-based beam reporting, the UE triggers a report when the quality of both candidate RSs in a pair of candidate RSs is better than the corresponding threshold (at least for the second type of report).

[0652] Alternatively and / or preferably, the UE determines whether to trigger a beam pair based report based on a specific parameter. Preferably, in some embodiments, the specific parameter is configured in UETriggeredCondConfig. Preferably, in some embodiments, the specific parameter is used to configure or enable a trigger condition based on a beam pair. In the case where this specific parameter indicates enabling, the trigger condition is based on the quality of at least two RSs in a pair of RSs. In one instance, enabling the specific parameter and configuring the associated CSI-ReportConfig with a group-based beam report (e.g., groupBasedBeamReporting-v1710) are configured simultaneously. In the case where this specific parameter indicates enabling, the trigger condition is based on the quality of at least two RSs in a pair of RSs. In one instance, the specific parameter enabling is not associated with the CSI-ReportConfig not being configured with a group-based beam report (e.g., groupBasedBeamReporting-v1710). In one instance, indicating that the first TRP, the second TRP, or a joint configuration of the two TRPs is used or configured in a UETriggeredCondConfig. Preferably in certain embodiments, when one UETriggeredCondConfig has this joint configuration indicating a first TRP, the RS associated with the UETriggeredCondConfig is used as a candidate RS associated with the first TRP for triggering the report, and / or in other words, a quality comparison between the currently used / indicated RS and the candidate RS (if any) is applied to the first TRP. Preferably in certain embodiments, the triggered report (according to the UETriggeredCondConfig having this joint configuration indicating the first TRP) is associated with the first TRP and / or the triggering condition is based on the quality of the first TRP. On the other hand, when the UETriggeredCondConfig has this joint configuration indicating a second TRP, the triggered report is associated with the second TRP and / or the triggering condition is based on the quality of the second TRP. Finally, when the UETriggeredCondConfig has this joint configuration indicating two TRPs (or beam pair-based reporting), the triggered report is associated with the two TRPs and / or the triggering condition is at least based on the quality of the two TRPs. Alternatively and / or preferably, whether the UETriggeredCondConfig is associated with the first or second TRP and whether beam pair based reporting is present / enabled corresponds to different configurations / parameters (in one UETriggeredCondConfig).

[0653] Alternatively and / or preferably, whether the UETriggeredCondConfig is associated with the first TRP or the second TRP is based on an associated RS or RS set configured with or associated with the first TRP or the second TRP. Preferably in some embodiments, when a CSI-RS resource or a CSI-RS resource set is configured with or associated with the first TRP, once the UETriggeredCondConfig is associated with the CSI-RS resource or the CSI-RS resource set, the UETriggeredCondConfig is associated with the first TRP. Preferably in some embodiments, the triggered report (according to the UETriggeredCondConfig with the RS associated with the first TRP) is associated with the first TRP and / or the triggering condition is based on the quality of the first TRP. Preferably in some embodiments, the quality comparison is based on the used / indicated RS and the candidate RS associated with the first TRP. Preferably in some embodiments, the triggering condition is (based on) the quality of the CSI-RS resource or the CSI-RS resource set and / or the quality of the used / indicated RS associated with the first TRP (not based on the quality of the used / indicated RS associated with the second TRP used for this UETriggeredCondConfig). Additionally and / or preferably, a UETriggeredCondConfig may be configured with an association with one CSI-RS resource or a set of CSI-RS resource sets. Preferably in certain embodiments, a UETriggeredCondConfig may be configured with an association with more than one CSI-RS resource or more than one set of CSI-RS resource sets. Preferably in certain embodiments, a UETriggeredCondConfig may be configured with an association with a pair of CSI-RS resources or a pair of CSI-RS resource sets. Preferably in certain embodiments, the first CSI-RS resource in the pair of CSI-RS resources is configured with a first TRP. Preferably in certain embodiments, the second CSI-RS resource in the pair of CSI-RS resources is configured with a second TRP. Preferably in certain embodiments, when UETriggeredCondConfig is configured with more than one CSI-RS resource or more than one CSI-RS resource set, the trigger condition is (based on) the quality of both the CSI-RS resource or the CSI-RS resource set and / or the quality of the used / indicated RS associated with the first TRP and the quality of the used / indicated RS associated with the second TRP (for this UETriggeredCondConfig).Preferably, in certain embodiments, when UETriggeredCondConfig is configured with more than one CSI-RS resource or more than one CSI-RS resource set, beam pair based reporting is used / applied / determined.

[0654] In addition and / or preferably, a UETriggeredCondConfig may be configured with an association with a TCI state currently in use / indicated. In one instance, a UETriggeredCondConfig may include a TCI state or RS identity associated with a TCI state currently in use / indicated. In another instance, the TCI state currently in use / indicated is implicitly based on a TCI state indicated via a first TCI state and / or a second TCI state indicated and / or a TCI state for monitoring CORESER 0 and / or a TCI state for monitoring a CORESER with a CSS. Preferably in some embodiments, a UETriggeredCondConfig may include one or more RSs configured to be used as a TCI state currently in use / indicated or RS. Preferably in some embodiments, a UETriggeredCondConfig may be associated with a list of TCI states or RSs currently in use / indicated. Preferably in some embodiments, a UETriggeredCondConfig may be associated with a list of RSs per TRP that is currently in use / indicated or RSs per TRP. Preferably in some embodiments, a UETriggeredCondConfig may be associated with a list of RSs per TRP that is currently in use / indicated or RSs per TRP. Preferably in some embodiments, one UETriggeredCondConfig may be associated with the RS list of two TRPs being used as the currently used / indicated TCI state or RS for two TRPs.

[0655] Preferably in certain embodiments, the UE may have a capability regarding the maximum number of triggered reports.

[0656] Preferably in certain embodiments, the maximum number of triggered reports depends on the UE capabilities.

[0657] Concept 3

[0658] This concept will have a disabling / skipping mechanism to avoid triggering UE reports too frequently. Preferably, the disabling / skipping mechanism (e.g., a timer or counter) is used to disabling / skipping reports for the same target, e.g., reports for non-LTM, reports associated with the same serving cell, or reports for LTM.

[0659] For example, after transmitting a report for non-LTM, a subsequent UE-triggered report for non-LTM may not be triggered / transmitted due to a prohibition / skipping mechanism (and a subsequent UE-triggered report for LTM is allowed to be triggered / transmitted). For example, after transmitting a report for LTM, a subsequent UE-triggered report for LTM may not be triggered / transmitted due to a prohibition / skipping mechanism (and a subsequent UE-triggered report for non-LTM is allowed to be triggered / transmitted). For example, after transmitting a report associated with a first serving cell, a subsequent UE-triggered report associated with the first serving cell may not be triggered / transmitted due to a prohibition / skipping mechanism (and a subsequent UE-triggered report associated with a second serving cell is allowed to be triggered / transmitted).

[0660] Preferably in some embodiments, the same target may correspond to (the quality of) the same RS that has been reported by one of the periodic / aperiodic / semi-persistent reports or UE-triggered reports. Preferably in some embodiments, the same target may correspond to the RS used for RSRP.

[0661] Preferably, in some embodiments, the UE maintains one or more timers associated with the prohibition / skipping mechanism. Preferably, in some embodiments, the one or more timers are associated with a report triggered by the UE. Preferably, in some embodiments, the prohibition / skipping mechanism may correspond to the UE not generating a triggered report until the timer expires. Preferably, in some embodiments, the prohibition / skipping mechanism may correspond to the UE not triggering a report when the timer is running. Preferably, in some embodiments, the prohibition / skipping mechanism may correspond to the UE not transmitting a triggered report when the timer is running. Preferably, in some embodiments, the prohibition / skipping mechanism may correspond to the UE not transmitting / triggering / generating a report during a specific time interval. Preferably, in some embodiments, the specific time interval is based on the timing of the last time the UE transmitted a report associated with the same target or starts after this timing or from this timing. Preferably, in some embodiments, the length of the first time interval is (per target) configured. Preferably, in some embodiments, within a specific time interval, the UE may transmit a report based on a network node (e.g., a periodic report, a semi-persistent report, or a report requested by a DCI), but cannot transmit a UE-triggered report.

[0662] Preferably in some embodiments, the UE may be configured with (periodic) PUCCH resources and / or (periodic) PUSCH resources for UE-triggered reporting. Preferably in some embodiments, the configured PUCCH resources and / or PUSCH resources for UE-triggered reporting are configured not to overlap with the first time interval relative to the timing of transmitting network node-based reports. Preferably in some embodiments, when the UE does not trigger a report, the UE does not transmit on the configured PUCCH resources and / or PUSCH resources for UE-triggered reporting or for other purposes other than UE-triggered reporting. Preferably in some embodiments, the UE is not allowed to transmit / trigger / generate UE-triggered reports (for targets) within the first interval relative to the timing of the network node configuration for transmitting network-based reports (for targets). Preferably in some embodiments, the prohibition / skipping mechanism can be per trigger condition (configuration), trigger criteria, per UE or per scenario (e.g., LTM, sTRP, mTRP), or per cell, or per TRP or per UE panel configuration. Preferably in some embodiments, each of the above can be a target. Preferably, in some embodiments, a target corresponds to any one or any combination of the following trigger conditions, or a trigger criterion, or a scenario (e.g., LTM, sTRP, mTRP), or a cell, or a TRP, or a UE panel. Preferably, in some embodiments, the first TRP and the second TRP in the sDCI or mTRP scenario may share a prohibition / skip mechanism (e.g., an ideal backhaul for the two TRPs, and when the UE transmits a UE-triggered report for at least one of the first or second TRPs, the UE applies the prohibition / skip mechanism for the two TRPs). Preferably, in some embodiments, the first TRP and the second TRP in the mDCI or mTRP scenario may have a corresponding prohibition / skip mechanism (e.g., a non-ideal backhaul for the two TRPs, and when the UE transmits a UE-triggered report for at least one of the first or second TRPs, the UE applies the prohibition / skip mechanism for the corresponding TRP). Preferably, in some embodiments, different trigger conditions (configurations) may be enabled / disabled or configured with a prohibition / skip mechanism, or different trigger conditions (configurations) may have different timer values. Preferably in some embodiments, different trigger criteria may be enabled / disabled or configured with a prohibition / skip mechanism, or different trigger criteria may have different timer values. Preferably in some embodiments, different scenarios may be enabled / disabled or configured with a prohibition / skip mechanism, or different scenarios may have different timer values. Preferably in some embodiments, different cells may be enabled / disabled or configured with a prohibition / skip mechanism, or different cells may have different timer values. Preferably in some embodiments, the same trigger condition (configuration) may be (all) associated with the same timer value and / or prohibition / skip mechanism.Preferably in some embodiments, the same enabled behavior for the prohibition / skipping mechanism and the same timer value is configured or shared for the same trigger condition (configuration), or for the same trigger criteria, or for the same UE, or for the same context (e.g., LTM, sTRP, mTRP), or for the same cell. Preferably in some embodiments, the UE may be configured with one or more timers. Preferably in some embodiments, each timer corresponds to one or more trigger conditions (configuration), one or more trigger criteria, one or more contexts (e.g., LTM, sTRP, mTRP), or one or more cells, or one or more TRPs, or one or more UE panels. More specifically, each timer corresponds to one trigger condition (configuration), one trigger criterion, one or more contexts (e.g., LTM, sTRP, mTRP), or one cell, or one TRP, or one UE panel. Preferably in some embodiments, for the same target, the UE maintains one timer. Preferably in some embodiments, in other words, the per-target maintenance of the timer is performed on the UE side. Preferably, in some embodiments, when timer A for target A is in operation, a corresponding prohibition mechanism is executed for target A, and preferably, in some embodiments, the prohibition mechanism is not executed for targets other than target A. In one instance, the trigger condition for the first TRP may be associated with the first timer, and the trigger condition for the second TRP may be associated with the second timer. When the UE has reported the quality of the candidate RS associated with the first TRP, the UE (re)starts the first timer and / or the UE does not trigger or transmit a triggered report associated with the first TRP. Preferably, in some embodiments, while the first timer is running, the UE may trigger a UE-triggered report and / or transmit a UE-triggered report associated with the second TRP.

[0663] Preferably, in some embodiments, when a timer among the one or more timers expires, the UE stops the timer among the one or more timers.

[0664] Preferably in some embodiments, the UE (re)starts the timer in response to transmitting a periodic / aperiodic / semi-persistent report (associated with the timer). Preferably in some embodiments, the UE (re)starts the timer in response to transmitting a UE-triggered report (associated with the timer). Preferably in some embodiments, the UE triggers a report not associated with the RS when the RS used to determine the quality of the candidate beam has been reported by one of the periodic / aperiodic / semi-persistent reports or the UE-triggered report. Preferably in some embodiments, when the timer expires or in response to the timer expiring, the UE may transmit a UE-triggered report (also when the triggering condition is met). Preferably in some embodiments, when the timer has not expired or in response to the timer not expiring, the UE is not allowed to transmit a UE-triggered report (even when the triggering condition is met). Preferably in some embodiments, when the timer is running, the UE is not allowed to transmit a UE-triggered report (even when the triggering condition is met).

[0665] Preferably in some embodiments, the first time interval is associated with a TTI in which the timer is running. Preferably in some embodiments, the second time interval is associated with a TTI in which the timer is not running. Preferably in some embodiments, different parameters and / or triggering conditions may be associated with the first time interval and the second time interval, respectively. In one example, the configuration of the triggering condition (e.g., UETriggeredCondConfig) may be configured with two sets of parameters associated with the first and second time intervals. Preferably in some embodiments, the UE is prevented from triggering or transmitting a report during the first time interval, unless the triggering condition associated with the parameter associated with the first time interval is met. Preferably in some embodiments, the triggering condition associated with the first time interval may be stricter (e.g., the quality of the candidate beam is better than the strict threshold, and / or the quality of the currently used beam is worse than the strict threshold). Otherwise, the UE does not transmit or trigger a UE-triggered report during the first time interval. Preferably in some embodiments, when the timer is running, the first set of parameters is used to determine the triggering condition. Preferably in some embodiments, when the timer expires, the second set of parameters is used to determine the triggering condition.

[0666] Preferably in some embodiments, in some special cases when the timer is running, the UE may trigger a report and / or transmit a report. Preferably in some embodiments, the UE stops the timer in response to some special cases or when some special cases occur. Preferably in some embodiments, the special case is that the currently used beam changes, the candidate beam changes, the parameters related to the triggering condition are reconfigured, or an LTM MAC CE (e.g., an LTM cell switching command) is received. Preferably in some embodiments, the UE skips or ignores or stops the timer. Preferably in some embodiments, (even when the timer is running), for special cases, the UE triggers a report once the triggering condition is met, or the UE triggers once the special case occurs. Preferably in some embodiments, for special cases, the triggering condition is (based on) the first set of parameters when the timer is running. Preferably in some embodiments, the special case is based on each target. Preferably in some embodiments, "target" may correspond to a triggering condition, a triggering criterion, a UE or a scenario (e.g., LTM, sTRP, mTRP), or a cell, or a TRP or a UE panel (configuration). Preferably, in certain embodiments, when the UE receives a beam indication DCI indicating a current beam change for the second TRP, the special case is associated with the second TRP (and not associated with the first TRP). Preferably, in certain embodiments, when the UE receives an LTM MAC CE (e.g., an LTM cell switching command), the special case is associated with the affected target (e.g., both the first TRP and the second TRP). Preferably, in certain embodiments, when the UE receives an LTM MAC CE (e.g., an LTM cell switching command), the special case is associated with only the first TRP or the TRP used to receive the PDCCH associated with the common search space.

[0667] Preferably in some embodiments, the same target may correspond to RS associated with network node based reporting and UE triggered reporting. Preferably in some embodiments, the same target may correspond to one or more RS associated with the same TRP associated with network node based reporting and UE triggered reporting.

[0668] Preferably in certain embodiments, when the UE receives a UL grant or a configured UL grant with UL resources, the UE will transmit a (UE) triggered report based on the UL grant or the configured UL grant. Preferably in certain embodiments, the UL resources are in timing. Preferably in certain embodiments, the UE is requested by the network node to transmit an aperiodic CSI report (associated with RSRP) and / or is configured by the network node to transmit a periodic CSI report (associated with RSRP) and / or is activated by the network node to transmit a semi-persistent CSI report (associated with RSRP). Preferably in certain embodiments, based on the request and / or configuration of the network node, the UE will transmit a CSI report in timing (same as the UL resources). Preferably in certain embodiments, the UE will omit or discard or ignore one of the network requested / configured reports or the UE triggered reports. Preferably in certain embodiments, the UE will transmit only one of the network requested / configured reports or the UE triggered reports. Preferably in certain embodiments, the UE will discard or not transmit one of the network requested / configured reports or the UE triggered reports. Preferably in certain embodiments, the UE will transmit both the network requested / configured reports and the UE triggered reports. Preferably in certain embodiments, the UE shall discard or ignore or omit UE triggered reports. Preferably in certain embodiments, the UE shall discard or ignore or omit UE triggered reports in case both network requested / configured reports and UE triggered reports are associated with the same target.

[0669] For example, the UE may have a UE-triggered report 1 associated with a first TRP and a UE-triggered report 2 associated with a second TRP to be transmitted in timing. Preferably, in certain embodiments, when the UE has a network node-based CSI report associated with the first TRP, the UE discards the UE-triggered report 1 and / or transmits the UE-triggered report 2. Preferably, in certain embodiments, regardless of whether the timing has an overlap with the UE-triggered report and the network node-based report, the UE transmits both in the timing. Preferably, in certain embodiments, the network node-based report or the network node-requested / configured report corresponds to a report configured by or associated with the CSI-ReportConfig.

[0670] Preferably, in certain embodiments, the UE transmits at most one report (for the first target) in a time interval or in a (PUCCH / PUSCH) transmission. For example, when a first report for LTM (e.g., a periodic report, a semi-persistent report, or a network-requested report) and a UE-triggered report for LTM are to be transmitted in a time interval or in a transmission, only one of them (e.g., the first report or the UE-triggered report) is transmitted. UE-triggered reports for non-LTM are allowed to be transmitted in a time interval or in a transmission. For example, when a first report associated with a first serving cell (e.g., a periodic report, a semi-persistent report, or a network-requested report) and a UE-triggered report associated with the first serving cell are to be transmitted in a time interval or in a transmission, only one of them (e.g., the first report or the UE-triggered report) is transmitted. A UE-triggered report associated with a second serving cell is allowed to be transmitted in a time interval or in a transmission.

[0671]

[00106] With respect to the embodiments, examples and concepts detailed above and herein, the following aspects and embodiments are possible.

[0672] See also Fig.15 , with respect to such and other concepts, systems and methods of the present invention, a method 1000 for a UE to perform transmission and reception with a first serving cell includes receiving one or more configurations associated with a trigger condition (e.g., one or more configurations of the trigger condition) (step 1002), preferably performing measurements (at least for the first serving cell) on a first RS set and a second RS set, wherein the first RS set is associated with a currently used / indicated beam of the first serving cell and the second RS set is associated with candidate RSs associated with one or more cells (step 1004), triggering one or more reports associated with the first serving cell when at least one trigger condition is met (step 1006), and transmitting the one or more reports to a network node (step 1008).

[0673] Reference now Figure 3 and Figure 4In one or more embodiments, from the perspective of the UE performing transmission and reception with the first serving cell, the device 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive one or more configurations associated with the trigger condition (e.g., one or more configurations of the trigger condition); (ii) preferably perform (at least for the first serving cell) measurements on a first RS set and a second RS set, wherein the first RS set is associated with the currently used / indicated beam of the first serving cell, and the second RS set is associated with candidate RSs associated with one or more cells; (iii) trigger one or more reports associated with the first serving cell when at least one trigger condition is met; and (iv) transmit the one or more reports to the network node. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps and methods described above, below or otherwise described herein.

[0674] See also Fig.16 , with respect to such and other concepts, systems and methods of the present invention, a method 1010 for a UE to perform transmission and reception with a first serving cell includes transmitting a network-based report or a UE-triggered report to a network node in a timing (e.g., or TTI or time slot) (step 1012), and performing a prohibition / skipping mechanism for a UE-triggered report associated with at least one triggering condition when at least one triggering condition is met during an interval relative to the timing (step 1014).

[0675] Reference now Figure 3 and Figure 4 In one or more embodiments, from the perspective of the UE performing transmission and reception with the first serving cell, the device 300 includes a program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) transmit a network-based report or a UE-triggered report to a network node in a timing (e.g., or TTI or time slot); and (ii) perform a prohibition / skipping mechanism for UE-triggered reports associated with at least one triggering condition when at least one triggering condition is met during an interval relative to the timing. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or otherwise herein.

[0676] See also Fig.17, with respect to such and other concepts, systems and methods of the present invention, a method 1020 for a UE to perform transmission and reception with a first serving cell includes triggering a first report for a target (step 1022), transmitting a second report in a timing (e.g., or TTI or time slot) (before transmitting the first report), wherein preferably the second report is a network-based report or a UE-triggered report to a network node, or wherein preferably the second report is transmitted before the transmission of the triggered first report (step 1024), determining whether to perform a prohibition / skip mechanism for the first report based on whether the first report and the second report are associated with the same target (step 1026); and based on the determination of different targets, transmitting the first triggered report to the network node (step 1028).

[0677] Reference now Figure 3 and Figure 4 In one or more embodiments, from the perspective of the UE performing transmission and reception with the first serving cell, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) trigger a first report for a target; (ii) transmit a second report (before transmitting the first report) in a timing (e.g., or TTI or time slot), wherein preferably the second report is a network-based report or a UE-triggered report to the network node, or wherein preferably the second report is transmitted before transmitting the triggered first report; (iii) determine whether to perform a prohibition / skip mechanism for the first report based on whether the first report and the second report are associated with the same target; and (iv) transmit the first triggered report to the network node based on the determination of different targets. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps and methods described above, below or otherwise described herein.

[0678] Preferably, in certain embodiments, the first report and the second report are associated with the same target, and / or the UE performs a prohibition / skipping mechanism for the first report, and / or the UE cancels / discards / ignores the triggered first report.

[0679] Preferably in certain embodiments, based on the determination of the same target, the UE cancels the transmission of the first triggered report.

[0680] Preferably in certain embodiments, based on the determination of the same objective, the UE performs a prohibition / skipping mechanism for the first report during a time interval (with respect to timing).

[0681] Preferably in certain embodiments, based on the determination of different objectives, the UE does not perform a prohibition / skipping mechanism for the first report during the time interval (with respect to timing).

[0682] Preferably in certain embodiments, when the UE can include the first triggered report in timing with the transmission for the second report, the UE transmits both the first report and the second report.

[0683] Preferably in certain embodiments, after the timing and within the time interval, the UE is not allowed to transmit or does not transmit or cancels transmission of the triggered report and / or the UE cancels the triggered report (based on determination of the same target).

[0684] Alternatively in certain embodiments, the UE performs a prohibition / skipping mechanism for the first report (regardless of whether there is the same or different target between the first report and the second report), and / or cancels the first triggered report once the UE transmits the second report.

[0685] Preferably in certain embodiments, when the first report and the second report are associated with the same target, the UE cancels the first triggered report when / once the UE transmits the second report.

[0686] Preferably in certain embodiments, the UE cancels the (already) triggered first report when / once the UE transmits the second report (regardless of whether there is the same target, or alternatively based on having the same target between the first report and the second report).

[0687] Preferably, in some embodiments, the UE receives one or more configurations associated with the triggering condition (eg, one or more configurations of the triggering condition).

[0688] Preferably in certain embodiments, once the UE transmits the second report, the UE resets a counter associated with one or more triggering conditions or criteria (whether or not there is the same target, or alternatively based on having the same target between the first report and the second report).

[0689] Preferably in certain embodiments, satisfying the trigger condition corresponds to at least an associated counter reaching (or exceeding) a maximum number, wherein the counter is used to count the number of times the criterion is satisfied.

[0690] Preferably in certain embodiments, during the time interval, the UE does not trigger and / or transmit a triggered report.

[0691] Preferably in certain embodiments, during the time interval, the UE uses or determines the triggering condition based on another set of parameters.

[0692] Preferably, in some embodiments, different sets of parameters for determining whether to trigger UE reporting are determined based on whether the UE is in a time interval (associated with a prohibition / skipping mechanism), and / or different trigger conditions can be grouped into triggering within a time interval or triggering outside a time interval.

[0693] Preferably in certain embodiments, the UE maintains a timer associated with the inhibit / skip mechanism (for one target).

[0694] Preferably in certain embodiments the UE (re)starts the timer when the UE transmits a report (eg a network node based report or a UE triggered report).

[0695] Preferably in some embodiments, when the timer expires, the UE stops the timer.

[0696] Preferably in certain embodiments, the UE performs the inhibit / skip mechanism while the timer is running.

[0697] Preferably in some embodiments, when the timer expires or stops, the UE may transmit a UE-triggered report (eg, a first triggered report).

[0698] Preferably, in some embodiments, the UE may trigger the first report when the timer expires or stops.

[0699] Preferably in certain embodiments, the length of the time interval is determined based on a timer.

[0700] Preferably in certain embodiments, the length of the time interval is configured by RRC signaling and / or is associated with a target.

[0701] Preferably in certain embodiments, the timer may be per target, and / or the timer for target A does not affect the transmission of the triggered report for target B by the UE.

[0702] Preferably in certain embodiments, when the network node based reporting is aperiodic or requested by DCI, the UE cancels the triggered reporting in response to receiving the DCI or request (preferably based on the same target between the triggered reporting and the network node based reporting).

[0703] Preferably in certain embodiments, the UE cancels the triggered first report when the UE receives a DCI or request for a second report from the network node (preferably based on the same target between the first report and the second report).

[0704] Preferably in certain embodiments, after transmitting the one or more reports to the network node, the UE receives a PDCCH order or beam indication DCI (indicating a change of one or more indicated TCI states).

[0705] Preferably in certain embodiments, the PDCCH order indicates a RACH procedure for acquiring the TA of the candidate cell.

[0706] Preferably in certain embodiments, the PDCCH order instructs the UE to perform a RACH procedure associated with the RS associated with the one or more reports.

[0707] Preferably in some embodiments, the one or more reports include at least one candidate RS in the second RS set.

[0708] Preferably in some embodiments, the at least one candidate RS is associated with a cell having a different PCI than the first cell.

[0709] Preferably in some embodiments, a configuration associated with a trigger condition corresponds to or provides the following information: criteria for triggering a report and / or the number of criteria, and / or thresholds, and / or offsets, and / or quality types, and / or associations with currently used / indicated beams or RSs, and / or associations with candidate beams or RSs, associations with reporting configurations, and / or LTM or non-LTM, and / or first type of reports or second type of reports, and / or beam-based comparisons or beam-pair-based comparisons.

[0710] Preferably, in some embodiments, satisfying a trigger condition corresponds to the number of times one or more criteria are satisfied, wherein the one or more criteria are or correspond to: the quality (plus or minus an offset) of at least one candidate beam is greater than (or equal to) a threshold, and / or the quality (plus or minus an offset) of at least one currently used / indicated beam is less than (or equal to) a threshold, and / or the quality (plus or minus an offset) of at least one candidate beam is greater than (or equal to) the quality (plus or minus an offset) of at least one currently used / indicated beam, and / or the number of times the report to be triggered by the UE indicates that the UE has reached a certain level of quality. The beam / TCI state / RS is different from the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report (associated with the same serving cell), and / or the quality (plus or minus an offset) of the beam / TCI state / RS indicated by the UE-triggered report is different from (e.g., greater than (or equal to) or less than (or equal to)) the quality (plus or minus an offset) of the beam / TCI state / RS indicated by the last transmitted (UE-triggered, periodic, aperiodic or semi-persistent) report (associated with the same serving cell).

[0711] Preferably in some embodiments, (the configuration of) the at least one trigger condition is associated with a criterion associated with the quality of the candidate beam (regardless of the quality of the currently used / indicated beam).

[0712] Preferably, in some embodiments, when the quality of the currently used / indicated beam is not bad (for example, the quality of the currently used / indicated beam is not lower than the quality of the candidate beam by an offset, or the quality of the currently used / indicated beam is not lower than a threshold), the at least one trigger condition (configuration) is associated with the criterion associated with the quality of the candidate beam.

[0713] Preferably in certain embodiments, (the configuration of) the at least one trigger condition is associated with criteria associated with both the quality of the candidate beams and the currently used / indicated beam.

[0714] Preferably, in certain embodiments, the at least one trigger condition or criterion (configuration) may be associated with the first TRP or the second TRP.

[0715] Preferably, in certain embodiments, the at least one trigger condition or criterion (configuration) includes a parameter / indication / signal indicating that the at least one trigger condition or criterion (configuration) is associated with the first TRP or the second TRP.

[0716] Preferably, in certain embodiments, when the at least one trigger condition or criterion (configuration) is associated with the first TRP, the RS for determining the quality of the currently used / indicated beam and the RS for determining the quality of the candidate beam are associated with the first TRP.

[0717] Preferably, in some embodiments, based on the fact that the associated RS for determining the quality of the currently used / indicated beam and / or for determining the quality of the candidate beam is associated with the first TRP or the second TRP, the UE determines which TRP of the first and second TRPs the at least one trigger condition or criterion (configuration) is associated with.

[0718] Preferably, in some embodiments, an RS resource or a set of RS resources may be configured with a first TRP or a second TRP, and based on this information, when such RS is associated with the at least one trigger condition or criterion (configuration), it is determined which TRP the at least one trigger condition or criterion (configuration) is associated with.

[0719] Preferably, in certain embodiments, when the RS associated with the at least one trigger condition or criterion (configuration) for determining the quality of the currently used / indicated beam is associated with the first TRP, the at least one trigger condition or criterion (configuration) is associated with the first TRP.

[0720] Preferably, in some embodiments, when the at least one trigger condition or criterion (configuration) is associated with a first TRP, the RS used to determine the quality of the candidate beam is based on the first TRP, and on the other hand, when the at least one trigger condition or criterion (configuration) is associated with a second TRP, the RS used to determine the quality of the candidate beam is based on the second TRP.

[0721] Preferably, in certain embodiments, when the RS for determining the quality of the candidate beam associated with the at least one trigger condition or criterion (configuration) is associated with the first TRP.

[0722] Preferably, in some embodiments, when the at least one trigger condition or criterion (configuration) is associated with a first TRP, the RS used to determine the quality of the currently used / indicated beam is based on the first TRP, and on the other hand, when the at least one trigger condition or criterion (configuration) is associated with a second TRP, the RS used to determine the quality of the currently used / indicated beam is based on the second TRP.

[0723] Preferably, in certain embodiments, the UE does not expect the RS used to determine the quality of the currently used / indicated beam and the RS used to determine the quality of the candidate beam to be associated with different TRPs, and / or at this time or wherein the two RSs are associated with the same at least one trigger condition or criterion (configuration).

[0724] Preferably, in certain embodiments, based on the indication / parameter / signaling of (the configuration of) the at least one trigger condition or criterion (wherein the indication / parameter / signaling indicates the first or second TRP), the UE determines that the at least one trigger condition or criterion (the configuration) is associated with the first TRP.

[0725] Preferably in certain embodiments, the at least one triggering condition or criterion may be configured with or enable beam pair based triggering / comparison.

[0726] Preferably in certain embodiments, beam pair triggering / comparison corresponds to satisfying criteria for two TRPs or satisfying criteria for each TRP.

[0727] Preferably, in certain embodiments, the at least one trigger condition or criterion (configuration) is associated with the RS of the first TRP and the RS of the second TRP or the RS associated with the first panel of the UE and the RS associated with the second panel of the UE.

[0728] Preferably, in some embodiments, the at least one trigger condition or criterion (configuration) is associated with the RS of the first TRP for determining the quality of the candidate beam and the RS of the second TRP for determining the quality of the candidate beam.

[0729] Preferably, in certain embodiments, when the at least one trigger condition or criterion (configuration) is configured with RSs of two TRPs for determining the quality of a candidate beam, the at least one trigger condition or criterion (configuration) is enabled or configured with beam pair triggering / reporting.

[0730] Preferably in certain embodiments, for beam pair triggering / reporting, the trigger condition is (based on) when at least the criteria of two TRPs are met.

[0731] Preferably, in certain embodiments, the at least one trigger condition or criterion (configuration) includes signaling / indication indicating the first TRP, the second TRP or both TRPs.

[0732] Preferably, in some embodiments, the at least one trigger condition or criterion (configuration) includes signaling / indication indicating that the trigger condition is based on: satisfying the quality of the beam associated with the first TRP (including the quality of the currently used / indicated beam associated with the first TRP and / or the quality of the candidate beam associated with the first TRP), or satisfying the quality of the beam associated with the second TRP (including the quality of the currently used / indicated beam associated with the second TRP and / or the quality of the candidate beam associated with the second TRP), or satisfying the quality of the beams associated with both TRPs (including the quality of the currently used / indicated beam associated with the first TRP and / or the quality of the candidate beam associated with the first TRP, as well as the quality of the currently used / indicated beam associated with the second TRP and / or the quality of the candidate beam associated with the second TRP).

[0733] Preferably in some embodiments, the beam pair triggering / comparison may be replaced by a joint TRP triggering.

[0734] Preferably in certain embodiments, when beam pair triggering / comparison (joint TRP triggering) is configured or enabled, the UE is expected to be configured with RS associated with two TRPs.

[0735] Preferably in certain embodiments, when beam pair triggering / comparison (joint TRP triggering) is configured or enabled, the offset, threshold and / or quality type, which criterion is configured by the at least one trigger condition (configuration), can be configured per TRP (then there are two corresponding above parameters) or a configuration shared by two TRPs.

[0736] Preferably in some embodiments, different criteria may have or be configured with different times for triggering reporting.

[0737] Preferably in some embodiments, a trigger condition corresponds to the number of times a criterion is met.

[0738] Preferably in some embodiments, the number of timers may be one, and / or one trigger condition may be replaced by one criterion.

[0739] Preferably, in some embodiments, the first RS set may include one or more currently used / indicated beams of the first service cell, and / or preferably the first RS set may include one or more currently used / indicated beams of the second cell configured with an additional PCI associated with the first service cell.

[0740] Preferably, in some embodiments, the first RS set may include RSs associated with the first indicated TCI state through at least one beam indication DCI.

[0741] Preferably, in some embodiments, the first RS set may include RSs that indicate DCI associated with the second indicated TCI state through at least one beam.

[0742] Preferably, in some embodiments, the first RS set may include RSs for CORESET monitoring, for CORESET 0 and / or for beam failure detection.

[0743] Preferably, in some embodiments, the first RS set may include a first RS subset associated with the first TRP and a second RS subset associated with the second TRP.

[0744] Preferably in some embodiments, the first RS set is used to determine the quality of at least one currently used / indicated beam.

[0745] Preferably in certain embodiments, a first subset of the first RS set is used to determine the quality of at least one currently used / indicated beam associated with a first TRP or a first UE panel.

[0746] Preferably in certain embodiments, a second subset of the first RS set is used to determine the quality of at least one currently used / indicated beam associated with a second TRP or a second UE panel.

[0747] Preferably in some embodiments, the first set of RSs used to determine the quality of the currently used / indicated beam is configured by a list of RSs, and / or the list of RSs is different from the RSs used for beam failure detection.

[0748] Alternatively, in some embodiments, the first set of RSs may include RSs from beam failure detection.

[0749] Alternatively, in some embodiments, the first subset of RSs may include RSs from beam failure detection associated with the first TRP.

[0750] Alternatively, in some embodiments, the second subset of RSs may include RSs from beam failure detection associated with the second TRP.

[0751] Alternatively, in certain embodiments, when the UE is configured with an RS list for the first RS set (via explicit RRC signaling), the UE determines the first RS set based on the currently used / indicated TCI state and / or RS associated with the TCI state for CORESET monitoring.

[0752] Preferably, in certain embodiments, for configuration of a trigger condition associated with the LTM, the first RS set includes RSs associated with monitoring a TCI state of a CORESET with a CSS.

[0753] Preferably, in some embodiments, the first RS set is updated or changed based on the beam indication DCI and / or TCI status (de-)activation MAC CE.

[0754] Preferably, in certain embodiments, when the UE receives a beam indication DCI indicating a TCI state (with the same direction) that is different from the TCI state currently used / indicated, the UE updates the RS in the first RS set, and / or the UE replaces RS1 (associated with the original indicated TCI state) with RS2 (associated with the TCI state indicated by the beam indication DCI).

[0755] Preferably in certain embodiments, the UE maintains a counter per TRP or per (configuration of) triggering condition, wherein the counter is used to determine or count the number of times the criterion is met.

[0756] Preferably, in certain embodiments, the UE resets the counter when or in response to a UE change of PCell, a serving beam change, a beam indication DCI is received, a TCI state (de)activation MAC CE is received, a beam failure and / or a transmission triggered report.

[0757] Preferably in certain embodiments, the UE maintains a timer per TRP or per (configuration of) a trigger condition, wherein the UE triggers a report based on at least when the timer expires (and the trigger condition is met).

[0758] Preferably, in certain embodiments, in response to UE changing PCell, serving beam changing, receiving beam indication DCI, receiving TCI state (deactivation) activation MAC CE, beam failure, transmission triggered reporting, the UE restarts the timer.

[0759] Preferably in certain embodiments, the UE does not trigger a report (associated with a trigger condition) while the timer is running.

[0760] Alternatively in certain embodiments the UE maintains a specific timer for all UE triggered reports.

[0761] Preferably, in certain embodiments, when the RS used to determine the quality of the candidate beam is associated with one, the trigger condition (configuration) has a connection or association with periodic, aperiodic, semi-persistent CSI reporting configuration and / or BFR, and once one of the periodic, aperiodic, semi-persistent CSI reporting configuration and / or BFR is transmitted, the UE triggers a report after a duration after the one report.

[0762] Preferably, in certain embodiments, when the UE triggers the BFR procedure and / or identifies the BFR for the first TRP, the UE will cancel the ongoing triggered report associated with the first TRP.

[0763] Preferably, in certain embodiments, when the UE triggers the BFR procedure and / or identifies the BFR for the first TRP, the UE will cancel the ongoing triggered report associated with the affected TRP.

[0764] Preferably, in certain embodiments, when the UE triggers the BFR procedure and / or identifies the BFR for the first TRP, the UE will cancel the ongoing triggered reports associated with both the first TRP and the second TRP.

[0765] Preferably in certain embodiments, when the UE triggers the BFR procedure and / or identifies a BFR for a first TRP, the UE (re)starts the timer for the first TRP, and / or the UE considers / determines that the timer is running, and / or the UE does not transmit a trigger report associated with the first TRP.

[0766] Preferably in certain embodiments, the BFR MAC CE takes precedence over the triggered report.

[0767] Preferably in certain embodiments the UE will transmit both a BFR MAC CE and a triggered report.

[0768] Preferably in some embodiments, the UE triggers the BFR procedure after the UE-triggered reporting.

[0769] Preferably in certain embodiments, the UE triggers the BFR procedure before transmitting the UE-triggered report.

[0770] Preferably in some embodiments, a timer is used to prohibit the UE from triggering reporting too frequently (regardless of which triggering condition is met).

[0771] Preferably in certain embodiments, the UE does not trigger a report (associated with any triggering condition) while the timer is running.

[0772] Preferably, in certain embodiments, the UE deactivates the timer for UE-triggered reporting when or in response to a UE change in PCell, a serving beam change, a beam indication DCI is received, a TCI state (de)activation MAC CE is received, a beam failure occurs, a transmission-triggered report occurs.

[0773] Preferably, in certain embodiments, when or in response to a UE change PCell, a serving beam change, a beam indication DCI is received, a TCI status (de)activation MAC CE is received, a beam failure and / or a transmission triggered report, the UE deactivates the timer, and / or the UE considers / determines that the timer is not in operation, and / or the UE considers / determines that the timer expires.

[0774] Alternatively in certain embodiments, the UE maintains a timer per TRP or per (configuration of) a trigger condition, wherein the UE triggers a report based on at least when the timer has not expired.

[0775] Preferably in certain embodiments, for beam pair based reporting / comparison, whether the criteria (associated with the configuration of the trigger condition) are met is based on whether the criteria of two TRPs are met, and / or whether the counter is increased by one is based on whether the criteria of two TRPs are met (or the criteria is to check whether the criteria of two TRPs are met).

[0776] Preferably, in certain embodiments, when the criteria of only one TRP are met and not the criteria of another TRP, the UE does not increment the counter associated with the configuration of the trigger condition for beam pair based reporting / comparison.

[0777] Preferably in certain embodiments, when the criteria of both TRPs are met, for beam pair based reporting / comparison, the UE increments a counter associated with the configuration of the triggering condition.

[0778] Preferably in certain embodiments, the UE triggers a report (associated with the triggering condition) when the counter reaches (or exceeds) a maximum number associated with the configuration of the triggering condition.

[0779] Preferably, in some embodiments, the second RS set includes RSs used to determine the quality of the candidate beams.

[0780] Preferably, in some embodiments, the second RS set is used for RSRP measurement.

[0781] Preferably in some embodiments, the second RS set includes RSs associated with the candidate RSs in response to the beam failure.

[0782] Preferably, in certain embodiments, the second RS set includes RSs associated with a deactivated TCI state for PDCCH monitoring, for (all) CORESETs, for CORESET 0 and / or one or more or all CORESET pools, for CORESETs associated with a CSS, and for CORESETs associated with both a USS and a CSS.

[0783] Preferably, in some embodiments, the second RS set includes RSs associated with (configurations of) one or more trigger conditions or criteria.

[0784] Preferably, in some embodiments, the second RS set includes RSs associated with (configuration of) a triggering condition or criterion.

[0785] Preferably in some embodiments, the second RS set is associated with candidate RSs for triggering reporting.

[0786] Preferably, in some embodiments, the second RS set includes SS-PBCH and / or CSI-RS (used for beam management, associated with RSRP).

[0787] Preferably in some embodiments, the second RS set includes RSs associated with one, multiple or candidate cells.

[0788] Preferably, in some embodiments, the second RS set includes RSs associated with the first serving cell, wherein the second RS set includes RSs that are not configured or included in the first RS set.

[0789] Preferably, in some embodiments, the second RS set includes RSs associated with the second serving cell, the third cell, the fourth cell and / or the fifth cell.

[0790] Preferably in some embodiments, the one, multiple or candidate cells are activated cells.

[0791] Preferably, in some embodiments, based on the association between the configuration of the at least one trigger condition and the configuration of one or more RS resources, the quality of the candidate beam (associated with the configuration of the at least one trigger condition) as the RS of the associated one or more RS resources is determined.

[0792] Preferably, in some embodiments, the second RS set may include a first subset of RSs associated with the first TRP and a second subset of RSs associated with the second TRP.

[0793] Preferably in certain embodiments, a first subset of the second RS set is used to determine the quality of at least one candidate beam associated with a first TRP or a first UE panel.

[0794] Preferably in certain embodiments, a second subset of the second RS set is used to determine the quality of at least one candidate beam associated with a second TRP or a second UE panel.

[0795] Preferably in some embodiments, the second set of RSs used to determine the quality of the currently used / indicated beam is configured by a list of RSs, and / or the list of RSs is different from the RSs used as candidate RSs for responding to beam failure.

[0796] Preferably, in some embodiments, when one or more RSs in the second RS set are on a cell in which the UE is in an inactive state or a network node for the cell is in an inactive state, the UE ignores or cancels or does not perform measurements on the one or more RSs.

[0797] Alternatively, in some embodiments, the second RS set may include RSs for candidate RSs that respond to beam failure.

[0798] Alternatively, in some embodiments, the first subset of RSs may include RSs for candidate RSs responsive to beam failures associated with the first TRP.

[0799] Alternatively in some embodiments, a second subset of RSs may be used for candidate RSs responsive to beam failure associated with a second TRP.

[0800] Alternatively, in certain embodiments, when the UE is configured with an RS list for the second RS set (via explicit RRC signaling), the UE determines the second RS set based on RSs from the (RRC configured) TCI state list.

[0801] Preferably, in certain embodiments, the second RS set is updated or changed based on RS reconfiguration and / or a second MAC CE or a specific DCI indicating addition, removal and / or replacement of RSs in the second RS set.

[0802] Preferably, in some embodiments, the at least one trigger condition (configuration) is associated with one or more first RSs (which may be a subset) in the first RS set.

[0803] Preferably, in some embodiments, the at least one trigger condition (configuration) is associated with one or more second RSs (which may be a subset) in the second RS set.

[0804] Preferably, in some embodiments, based on the association between the at least one trigger condition (configuration), the UE determines one or more first RSs associated with the at least one trigger condition (configuration), which are preferably used to determine the quality of at least one currently used / indicated beam.

[0805] Preferably, in some embodiments, based on the association between the at least one trigger condition (configuration), the UE determines one or more second RSs associated with the at least one trigger condition (configuration), which are preferably used to determine the quality of at least one candidate beam.

[0806] Preferably, in some embodiments, the UE determines whether the at least one trigger condition is met based at least on the quality of the candidate beams associated with the one or more RSs associated with (the configuration of) the at least one trigger condition.

[0807] Preferably in certain embodiments, different times and / or different criteria and / or different thresholds, different offsets being used / configured correspond to different trigger conditions.

[0808] Preferably in some embodiments, the UE transmits a capability signal to inform the network node whether it supports beam pair based triggering / reporting.

[0809] Preferably, in some embodiments, the UE triggers the report based on whether the network node provides a configuration of the trigger condition.

[0810] Preferably in some embodiments, the UE triggers the report before triggering the beam failure.

[0811] Preferably, in some embodiments, the one or more reports include information associated with: which trigger condition (configuration), the trigger cause (if the UE does not report the configuration of the trigger condition), one or more RS from the second RS set, one or more RS from the first RS set, and / or which TRP (if the configuration of the trigger condition does not have explicit TRP information).

[0812] Preferably in certain embodiments the (UE triggered) report is transmitted via a MAC CE.

[0813] Preferably in certain embodiments the (UE triggered) report is transmitted via UCI.

[0814] It should be noted that any of the methods, alternatives, examples and embodiments described above and herein may be combined in whole or in part, or applied simultaneously or individually.

[0815] See also Fig.18, with respect to such and other concepts, systems and methods of the present invention, a method 1030 for a UE includes receiving a configuration of at least one condition for triggering a report by the UE, wherein the report is an L1 report or a MAC CE (step 1032), receiving a downlink signal indicating at least one joint or DL ​​TCI state, wherein the at least one joint or DL ​​TCI state is associated with a first RS (step 1034), and triggering the report in response to or based on satisfying a first condition of the at least one condition, wherein: the first condition includes: the L1-RSRP of one or more candidate beams is better than the L1-RSRP of the current beam by an offset, or the number of instances in which the L1-RSRP of the one or more candidate beams is better than the L1-RSRP of the current beam by the offset exceeds or reaches a maximum number, the UE determines the L1-RSRP of the current beam based on a measurement of the first RS and determines the L1-RSRP of the one or more candidate beams based on a measurement of the one or more candidate RSs (step 1036).

[0816] In various embodiments, the at least one joint or DL ​​TCI state includes two QCL information, wherein one of the two QCL information is associated with a first RS having a QCL type as type D, and the other of the two QCL information is associated with a second RS having a QCL type other than type D; and / or the first RS corresponds to a CSI-RS for beam management or a CSI-RS for L1-RSRP measurement (i.e., the first RS does not correspond to a CSI-RS for purposes other than beam management); and / or the first RS does not correspond to a CSI-RS for tracking.

[0817] In various embodiments, the at least one condition includes at least one of: a second condition, which includes that the L1-RSRP of the current beam is worse than the first threshold; and / or a third condition, which includes that the L1-RSRP of the one or more candidate beams is better than the second threshold; and / or a fourth condition, which includes that the L1-RSRP or the average L1-RSRP of the N best beams among the one or more candidate beams is better than the L1-RSRP of the current beam by one of the offsets, where N is greater than one.

[0818] In various embodiments, the UE triggers reporting in response to or based on satisfying the second condition, and / or the UE triggers reporting in response to or based on satisfying the third condition, and / or the UE triggers reporting in response to or based on satisfying the fourth condition.

[0819] In various embodiments, the one or more candidate beams are at least one of: one or more configured joint or DL ​​TCI states; and / or one or more activated joint or DL ​​TCI states; and / or one or more RSs associated with the first condition; and / or one or more RSs configured for reporting triggered by a UE.

[0820] In various embodiments, the UE is configured with one or more periodic PUCCH resources and / or one or more periodic PUSCH resources for transmitting reports, and / or the UE does not expect to multiplex network-triggered content into the one or more periodic PUCCH resources and / or the one or more periodic PUSCH resources, and / or the UE transmits a report on one of the one or more periodic PUCCH resources or one of the one or more periodic PUSCH resources when a report is triggered.

[0821] In various embodiments, the DL signal corresponds to a DCI having a TCI field for indicating the at least one joint or DL ​​TCI state, or to a TCI state (de-)activation MAC CE having only one TCI code point for indicating the at least one joint or DL ​​TCI state.

[0822] In various embodiments, the offset is configured by configuration, per condition of the at least one condition, per BWP, or per serving cell; and / or different conditions of the at least one condition are configured with the same or different offsets; and / or conditions of the at least one condition in different BWPs are configured with the same or different offsets; and / or conditions of the at least one condition in different serving cells are configured with the same or different offsets. Based on configuring the offset per BWP, different conditions in the same BWP are configured with the same offset. Based on configuring the offset per serving cell, different conditions in the same serving cell are configured with the same offset. The offset is a positive or negative number.

[0823] In various embodiments, the UE maintains a counter associated with the number of instances; and / or increases the counter or the number of instances by one in response to the L1-RSRP of the one or more candidate beams being better than the L1-RSRP of the current beam by an offset; and / or the UE resets the counter or the number of instances when or in response to the UE changing PCell, the current beam changing, receiving a beam indication DCI indicating another joint or DL ​​TCI state different from the at least one joint or DL ​​TCI state, receiving a TCI state (de)activation MAC CE, beam failure, triggered beam failure recovery and / or transmitting a (triggered) report; and / or the maximum number is configured by configuration, per condition of the at least one condition, per bandwidth part (BWP) or per serving cell; and / or the default value of the maximum number is one. Based on configuring the maximum number per BWP, different conditions in the same BWP are configured with the same maximum number. Based on configuring the maximum number per serving cell, different conditions in the same serving cell are configured with the same maximum number.

[0824] In various embodiments, the maximum number is based on the capabilities of the UE; and / or the UE reports its capabilities associated with the maximum number (i.e., long-term trigger) to the network node; and / or the maximum number is configured by configuration, per condition of the at least one condition, per BWP or per serving cell; and / or the UE is configured with the maximum number associated with the first condition; and / or the default value of the maximum number is one; and / or if the UE is not configured with the maximum number associated with the first condition, the default value of the maximum number is one (i.e., single-shot trigger).

[0825] In various embodiments, the UE triggers a report when the UE is configured with a maximum number and determines that the number of instances in which the L1-RSRP of the same beam in the one or more candidate beams is better than the L1-RSRP of the current beam by an offset exceeds or reaches the maximum number; and / or the UE determines the number of instances based at least on each of the one or more candidate beams; and / or the UE determines the number of instances based at least on the current beam.

[0826] In various embodiments, the UE maintains a timer associated with a first condition; and / or the first condition includes expiration of the timer; and / or the first condition is not satisfied when the timer is running; and / or the UE starts or restarts the timer when the UE transmits a report, a periodic report, or a report triggered by the network; and / or the UE stops the timer in response to a change in the current beam, a change in the one or more candidate beams, or receipt of an LTM MAC CE (e.g., an LTM cell switching command); and / or the UE restarts the timer in response to the UE changing PCell, changing the serving beam, receiving a beam indication DCI, receiving a TCI state (revocation) activation MAC CE, and / or a beam failure.

[0827] In various embodiments, the UE cancels a report under one or more of the following conditions: the report is transmitted by the UE or included in a MAC PDU or TB; and / or the UE transmits a periodic, semi-persistent or network-requested report; and / or the MAC is reset; and / or one or more parameters used for the report are reconfigured; and / or BFR is triggered and not canceled for the serving cell, and the report is associated with the serving cell; and / or a random access procedure for SpCell or SCell BFR is initiated; and / or the current beam is deactivated; and / or the one or more candidate beams to be indicated in the report are deactivated; and / or at least one serving cell associated with the report is deactivated or released; and / or at least one candidate cell associated with the report is deactivated or released; and / or the PCell changes; and / or an LTM cell switching command is received or LTM is initiated; and / or the network node of the UE's serving cell is in a power saving state.

[0828] In various embodiments, the one or more candidate beams and the current beam are associated with the same service cell; and / or the one or more candidate beams are associated with the candidate cell and the current beam is associated with the service cell; and / or the one or more candidate RSs include an RS of a service cell that is associated with the same service cell as the first RS (for example, the one or more candidate RSs and the first RS are associated with the same service cell); and / or the one or more candidate RSs include an RS of a PCI that is associated with a different PCI from the first RS (for example, the PCI of the candidate cell associated with the one or more candidate RSs is different from the PCI of the service cell associated with the first RS).

[0829] In various embodiments, the UE receives a PDSCH and / or PDCCH configured to follow the indicated TCI state based on the at least one joint or DL ​​TCI state, and / or the first RS used to determine the L1-RSRP of the current beam is used not only for receiving PDCCH but also for receiving PDSCH.

[0830] In various embodiments, the report indicates one or more of the following information: one or more serving cells associated with the current beam indicated by the report; and / or one or more serving cells associated with the one or more candidate beams indicated by the report; and / or the current beam of the serving cell; and / or the current beam of the PCell; and / or the L1-RSRP of the current beam; and / or the one or more candidate beams of the serving cell; and / or one or more candidate cells associated with the one or more candidate beams indicated by the report; and / or the one or more candidate beams of the same or different candidate cells; and / or the L1-RSRP of the one or more candidate beams; and / or information associated with LTM or non-LTM; and / or an identity associated with the first condition.

[0831] In various embodiments, the UE further determines the L1-RSRP of the current beam based on measurement of the second RS; and / or the second RS is associated with a second joint or DLTCI state for monitoring a DL channel or signal without applying the at least one joint or DL ​​TCI state; and / or the second RS corresponds to a QCL type D RS associated with the second joint or DL ​​TCI state; and / or the second RS corresponds to SS / PBCH or CSI-RS.

[0832] Reference now Figure 3 and Figure 4 In one or more embodiments from the perspective of the UE, the apparatus 300 includes a program code 312 stored in a memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive a configuration of at least one condition for triggering a report by the UE, wherein the report is an L1 report or a MAC CE; (ii) receive a downlink signal indicating at least one joint or DL ​​TCI state, wherein the at least one joint or DL ​​TCI state is associated with a first RS; and (iii) trigger the report in response to or based on satisfying a first condition of the at least one condition, wherein: the first condition includes: the L1-RSRP of one or more candidate beams is better than the L1-RSRP of the current beam by an offset, or the number of instances where the L1-RSRP of the one or more candidate beams is better than the L1-RSRP of the current beam by an offset exceeds or reaches a maximum number, and the UE determines the L1-RSRP of the current beam based on the measurement of the first RS and determines the L1-RSRP of the one or more candidate beams based on the measurement of the one or more candidate RSs. Furthermore, CPU 308 may execute program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

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

[0834] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[0835] 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 only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

[0836] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0837] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0838] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction 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 both. A 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0839] It should be understood that any specific 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 can be rearranged while remaining within the scope of the present disclosure. The accompanying 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.

[0840] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with a software module executed by a processor, or with 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 a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of a computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine can be referred to as a "processor" in this article) so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium can be integrated with a 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 in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium, and the computer-readable medium includes a code related to one or more of the various aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0841] Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.

Claims

1. A method for triggering a report by a user equipment, characterized in that: include: receiving a configuration of at least one condition for triggering a report by the user equipment, wherein the report is an L1 report or a medium access control control element; receiving a downlink signal indicating at least one joint or downlink transmission configuration indicator state, wherein the at least one joint or downlink transmission configuration indicator state is associated with a first reference signal; and The reporting is triggered based on satisfying a first condition of the at least one condition, wherein: The first condition includes: The L1-RSRP of one or more candidate beams is better than the L1-RSRP of the current beam by an offset, or the number of instances in which the L1-reference signal received power of the one or more candidate beams is better than the L1-reference signal received power of the current beam by the offset exceeds or reaches a maximum number, and The user equipment determines the L1-reference signal received power of the current beam based on the measurement of the first reference signal and determines the L1-reference signal received power of the one or more candidate beams based on the measurement of one or more candidate reference signals.

2. The method according to claim 1, characterized in that The at least one joint or downlink transmission configuration indicator state comprises two quasi co-location information, wherein one of the two quasi co-location information is associated with the first reference signal having a quasi co-location type being type D, and the other of the two quasi co-location information is associated with a second reference signal having a quasi co-location type other than type D; The first reference signal corresponds to a channel state information reference signal for beam management or a channel state information reference signal for L1-reference signal received power measurement; or The first reference signal does not correspond to a channel state information reference signal used for tracking.

3. The method according to claim 1, characterized in that The at least one condition includes at least one of the following: A second condition, which includes that the L1-reference signal received power of the current beam is worse than a first threshold; A third condition, which comprises that the L1-reference signal received power of the one or more candidate beams is better than a second threshold; or A fourth condition includes that the L1-reference signal received power or the average L1-reference signal received power of the N best beams among the one or more candidate beams is better than the L1-reference signal received power of the current beam by one of the offsets, where N is greater than one.

4. The method according to claim 3, characterized in that The user equipment triggers the report based on satisfying the second condition, the user equipment triggers the report based on satisfying the third condition, or the user equipment triggers the report based on satisfying the fourth condition.

5. The method according to claim 1, characterized in that The one or more candidate beams are at least one of: one or more configured joint or downlink transmission configuration indicator states; one or more activated joint or downlink transmission configuration indicator states; one or more reference signals associated with the first condition; or One or more reference signals configured for said reporting triggered by said user equipment.

6. The method according to claim 1, characterized in that The user equipment is configured with one or more periodic physical uplink control channel resources or one or more periodic physical uplink shared channel resources for transmitting the report, and the user equipment does not expect to multiplex network-triggered content into the one or more periodic physical uplink control channel resources or the one or more periodic physical uplink shared channel resources, or the user equipment transmits the report on one of the one or more periodic physical uplink control channel resources or one of the one or more periodic physical uplink shared channel resources when the report is triggered.

7. The method according to claim 1, characterized in that The downlink signal corresponds to downlink control information having a transmission configuration indicator field for indicating the state of the at least one joint or downlink transmission configuration indicator, or corresponds to a transmission configuration indicator state activation or deactivation media access control control element having only one transmission configuration indicator code point for indicating the state of the at least one joint or downlink transmission configuration indicator.

8. The method according to claim 1, characterized in that: configuring the offset by the configuration, per condition of the at least one condition, per bandwidth part, or per serving cell; Different conditions of the at least one condition are configured with the same or different offsets; The conditions in different bandwidth parts of the at least one condition are configured with the same or different offsets; or The conditions in different serving cells among the at least one condition are configured with the same or different offsets.

9. The method according to claim 1, characterized in that: The user equipment maintains a counter associated with the number of instances; In response to the L1-reference signal received power of the one or more candidate beams being better than the L1-reference signal received power of the current beam by the offset, increasing the counter or the number of instances by one; or In response to the user equipment changing the primary cell, the current beam changing, receiving a beam indication downlink control information indicating another joint or downlink transmission configuration indicator state different from the at least one joint or downlink transmission configuration indicator state, receiving a transmission configuration indicator state activation or deactivation media access control control element, a beam failure, triggering beam failure recovery or transmitting the report, the user equipment resets the counter or the number of instances.

10. The method according to claim 1, characterized in that: The maximum number is based on the capabilities of the user equipment; reporting, by the user equipment, the capabilities of the user equipment associated with the maximum number to a network node; configuring the maximum number by the configuration, per condition of the at least one condition, per bandwidth part, or per serving cell; The user equipment is configured with the maximum number associated with the first condition; The default value of the maximum number is one; or If the user equipment is not configured with the maximum number associated with the first condition, the default value of the maximum number is one.

11. The method according to claim 1, characterized in that The user equipment cancels the report under one or more of the following conditions: The report is transmitted by the user equipment or included in a media access control packet data unit or a transport block; The user equipment transmits periodic, semi-persistent or network-requested reports; Media access control reset; One or more parameters for the report are reconfigured; Beam failure recovery is triggered and not cancelled for a serving cell, and the report is associated with the serving cell; Initiate a random access procedure for special cell or secondary cell beam failure recovery; The current beam is deactivated; deactivating the one or more candidate beams indicated in the report; At least one serving cell associated with the report is deactivated or released; At least one candidate cell associated with the report is deactivated or released; The primary cell changes; Receiving an L1 / L2 triggered mobility cell handover command or initiating an L1 / L2 triggered mobility; or A network node of the serving cell of the user equipment is in a power saving state.

12. The method according to claim 1, characterized in that: The one or more candidate beams and the current beam are associated with the same serving cell; The one or more candidate beams are associated with a candidate cell and the current beam is associated with a serving cell; The one or more candidate reference signals include a reference signal of a serving cell that is associated with the same reference signal as the first reference signal; or The one or more candidate reference signals include a reference signal associated with a different physical cell identity than the first reference signal.

13. The method according to claim 1, characterized in that The user equipment receives a physical downlink shared channel or a physical downlink control channel configured to follow the indicated transmission configuration indicator state based on the at least one joint or downlink transmission configuration indicator state, or the first reference signal used to determine the L1-reference signal reception power of the current beam is used not only for receiving a physical downlink control channel but also for receiving a physical downlink shared channel.

14. The method according to claim 1, characterized in that The report indicates one or more of the following: one or more serving cells associated with the current beam indicated by the report; one or more serving cells associated with the one or more candidate beams indicated by the report; the current beam of the serving cell; the current beam of the primary cell; The L1-reference signal received power of the current beam; the one or more candidate beams of the serving cell; one or more candidate cells associated with the one or more candidate beams indicated by the report; the one or more candidate beams of the same or different candidate cells; the L1-reference signal received power of the one or more candidate beams; Information associated with L1 / L2 triggered mobility or non-L1 / L2 triggered mobility; or The identity associated with the first condition.

15. The method according to claim 1, characterized in that: The user equipment further determines the L1-reference signal received power of the current beam based on the measurement of the second reference signal; the second reference signal being associated with a second joint or downlink transmission configuration indicator state for monitoring a downlink channel or signal without applying the at least one joint or downlink transmission configuration indicator state; The second reference signal corresponds to a quasi co-located type D reference signal associated with the second joint or downlink transmission configuration indicator state; or The second reference signal corresponds to a synchronization signal, a physical broadcast channel or a channel state information reference signal.

16. A user equipment for triggering a report of a user equipment, characterized in that: include: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: receiving a configuration of at least one condition for triggering a report by the user equipment, wherein the report is an L1 report or a medium access control control element; receiving a downlink signal indicating at least one joint or downlink transmission configuration indicator state, wherein the at least one joint or downlink transmission configuration indicator state is associated with a first reference signal; and The reporting is triggered based on satisfying a first condition of the at least one condition, wherein: The first condition includes: The L1-RSRP of one or more candidate beams is better than the L1-RSRP of the current beam by an offset, or the number of instances in which the L1-reference signal received power of the one or more candidate beams is better than the L1-reference signal received power of the current beam by the offset exceeds or reaches a maximum number, and The user equipment determines the L1-reference signal received power of the current beam based on the measurement of the first reference signal and determines the L1-reference signal received power of the one or more candidate beams based on the measurement of one or more candidate reference signals.

17. The user equipment according to claim 16, characterized in that The at least one joint or downlink transmission configuration indicator state comprises two quasi co-location information, wherein one of the two quasi co-location information is associated with the first reference signal having a quasi co-location type being type D, and the other of the two quasi co-location information is associated with a second reference signal having a quasi co-location type other than type D; The first reference signal corresponds to a channel state information reference signal for beam management or a channel state information reference signal for L1-reference signal received power measurement; or The first reference signal does not correspond to a channel state information reference signal used for tracking.

18. The user equipment according to claim 16, characterized in that The at least one condition includes at least one of the following: A second condition, which includes that the L1-reference signal received power of the current beam is worse than a first threshold; A third condition, which comprises that the L1-reference signal received power of the one or more candidate beams is better than a second threshold; or A fourth condition includes that the L1-reference signal received power or the average L1-reference signal received power of the N best beams among the one or more candidate beams is better than the L1-reference signal received power of the current beam by one of the offsets, where N is greater than one.

19. The user equipment according to claim 18, characterized in that The user equipment triggers the report based on satisfying the second condition, the user equipment triggers the report based on satisfying the third condition, or the user equipment triggers the report based on satisfying the fourth condition.

20. The user equipment according to claim 16, characterized in that The one or more candidate beams are at least one of: one or more configured joint or downlink transmission configuration indicator states; one or more activated joint or downlink transmission configuration indicator states; one or more reference signals associated with the first condition; or One or more reference signals configured for said reporting triggered by said user equipment.

Images