Method and apparatus for event-triggered reporting in wireless communication system

Abstract

A method and apparatus for event-triggered reporting in a wireless communication system are provided, wherein the method of a user equipment comprises: triggering a first report in response to a first condition being satisfied; transmitting a request in response to the triggering of the first report; receiving first downlink control information for scheduling a first physical uplink shared channel; determining whether to transmit a first report on a first physical uplink shared channel based on whether a channel state information request field in the first downlink control information indicates a first code point associated with a first channel state information trigger state, the first channel state information trigger state is associated with a first channel state information report configuration for a first report; and transmitting a first report on the first physical uplink shared channel if a channel state information request field in the first downlink control information indicates the first code point.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of U.S. Provisional Patent Application No. 63 / 616,481, filed on December 29, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more particularly, to methods and devices for event - triggered reporting in wireless communication systems. Background Art

[0004] With the rapid growth in the demand for transferring 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. Such IP packet communication can provide IP - bearer voice, multimedia, multicast, and on - demand communication services to users of mobile communication devices.

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

[0006] Methods, systems, and devices for event-triggered reporting in a wireless communication system are provided. In various embodiments, a method for a user equipment (UE) includes: triggering a first report in response to a first condition being met; transmitting a request in response to the triggering of the first report; receiving first downlink control information (DCI) scheduling a first physical uplink shared channel (PUSCH); determining whether to transmit the first report on the first PUSCH based on whether a channel state information (CSI) request field in the first DCI indicates a first code point associated with a first CSI trigger state, the first CSI trigger state being associated with a first CSI report configuration for the first report; and if the CSI request field in the first DCI indicates the first code point, transmitting the first report on the first PUSCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 Drawings illustrating 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 is according to an embodiment of the present invention Figure 3 of the program code.

[0011] Figure 5A is a reproduction of Figure 3-1 in R1-2204369: Two deployment scenarios of M-TRP CJT, (a) Intra-site M-TRP CJT.

[0012] Figure 5B is a reproduction of Figure 3-1 in R1-2204369: Two deployment scenarios of M-TRP CJT, (b) Inter-site M-TRP CJT.

[0013] Figure 6 is a reproduction of Figure 6 in 3GPP RS 38.321h60:.1.3.13-1: Aperiodic CSI trigger state sub-selection MAC CE.

[0014] Figure 7 It is in Figure 6 .1.3.47-1 reproduction: Unified TCI state activation / deactivation MAC CE.

[0015] Figure 8 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention. The method includes: receiving one or more specific (report) configurations associated with a UE-initiated report, where the one or more specific configurations are associated with parameters for configuring time-domain behavior as UE-initiated; when the UE attempts to transmit more than one report within a time point or TTI, the UE transmits the reports in priority order based on a priority value; and transmitting one or more reports to a network node at a time point or TTI.

[0016] Figure 9 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention. The method includes: triggering one or more reports based on or in response to satisfying one or more triggers, preferably the reports can be beam reports or CJT calibration reports; determining whether to trigger an SR based on whether there is UL resources available for new transmission including the one or more trigger reports; and transmitting one or more reports on the UL resources at a time point or TTI.

[0017] Figure 10 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention. The method includes: triggering a first report in response to satisfying a first condition; transmitting a request in response to the triggering of the first report; receiving a first DCI scheduling a first PUSCH; determining whether to transmit the first report on the first PUSCH based on whether a CSI request field in the first DCI indicates a first code point associated with a first CSI trigger state, the first CSI trigger state being associated with a first CSI report configuration for the first report; and if the CSI request field in the first DCI indicates the first code point, transmitting the first report on the first PUSCH. Detailed implementation

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

[0019] The exemplary wireless communication systems and devices described below employ a wireless communication system that supports broadcast services. Wireless communication systems have been widely deployed to provide various types of communications, such as voice, data, and so on. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), 3GPP New Radio (NR), or some other modulation techniques.

[0020] Specifically, the exemplary wireless communication systems and devices described below can be designed to support one or more standards, such as the standards provided by an association named "Third Generation Partnership Project" (referred to as 3GPP in this document), including: [1] RP-232915, Proposal for Rel-19 MIMO Targets; [2] 3GPP TS 38.214i00; [3] R1-2204369, DOCOMO; [4] 3GPP TS 38.211i00; [5] 3GPP TS 38.212i00; [6] 3GPP TS 38.331h60; [7] 3GPP TS 38.321h50; and [8] 3GPP TS 38.213h60. The standards and documents listed above are hereby expressly and fully incorporated herein by reference in their entirety.

[0021] Figure 1 FIG. shows a multi-access wireless communication system according to an embodiment of the present invention. The access network 100 (access network, AN) includes multiple antenna groups, where one antenna group includes 104 and 106, another antenna group includes 108 and 110, and yet another antenna group includes 112 and 114. In Figure 1In this figure, only two antennas are shown for each antenna group. However, each antenna group may utilize more or fewer antennas. An 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 communicate using different frequencies. For example, forward link 120 may use a frequency different from the frequency used by reverse link 118.

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

[0023] In the communication via forward links 120 and 126, the transmitting antennas of access network 100 may utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Additionally, compared to an access network that transmits to all its access terminals via a single antenna, an access network that uses beamforming to transmit to access terminals randomly scattered within its coverage generally causes less interference to access terminals in adjacent cells.

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

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

[0026] In one embodiment, each data stream is transmitted via a corresponding transmitting antenna. TX data processor 214 formats, encodes, and interleaves the traffic data for the data stream based on a particular encoding scheme selected for each data stream to provide encoded data.

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

[0028] Subsequently, the modulated symbols for all data streams are provided to TX MIMO processor 220, which can further process the modulated symbols (e.g., for OFDM). Subsequently, TX MIMO processor 220 provides N T streams of modulated symbols to N T transmitters (TMTRs) 222a through 222t. In some embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and the antennas from which the symbols are transmitted.

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

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

[0031] Subsequently, RX data processor 260 receives N R symbol streams from N R receivers 254 and processes the N R received symbol streams based on specific receiver processing techniques to provide N TA "detected" symbol stream. Next, the RX data processor 260 demodulates, deinterleaves, and decodes each detected symbol stream to recover the service data for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

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

[0033] The reverse link message can include various types of information about the communication link and / or the received data streams. Next, the reverse link message is processed by the TX data processor 238 (which also receives service data for several 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.

[0034] 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. Next, the processor 230 determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

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

[0036] Turning to Figure 3 which shows an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As Figure 3 shown, the communication device 300 in the wireless communication system can be used to implement Figure 1UEs (or APs) 116 and 122 therein, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 may receive signals input by a user via the input device 302 (such as a keyboard or keypad), and may output images and sounds via the output device 304 (such as a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, transfer the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

[0037] Figure 4 is according to an embodiment of the present invention Figure 3 is a simplified block diagram of the program code 312 shown in. In this embodiment, the program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. The layer 3 portion 402 generally performs radio resource control. The layer 2 portion 404 generally performs link control. The layer 1 portion 406 generally performs physical connection.

[0038] For an LTE, LTE-A, or NR system, 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.

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

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

[0041] In [1] RP-232915, some discussion points related to the asynchronous requirements of coherent joint transmission are provided.

[0042] 2. Proposed Objectives: RAN1

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

[0044] a. UL signaling content for UE-initiated / event-driven beam reporting to facilitate fast beam switching

[0045] b. UL signaling medium / container considering the UE-initiated / event-driven nature of UL transmission, mainly designed for beam reporting

[0046] 2. Specify UE reporting enhancements for CJT deployment in non-ideal synchronization and backhaul scenarios, targeting FR1 in both FDD and TDD

[0047] a. Inter-TRP time misalignment and frequency / phase offset measurements and reporting assuming the existing CSI-RS design, where independent aperiodic reporting can be performed on PUSCH

[0048] Acronyms:

[0049] · sTRP: Single TRP (Transmission-Reception Point)

[0050] · mTRP: Multiple TRPs (Transmission-Reception Points)

[0051] · CJT: Coherent Joint Transmission

[0052] · DU: Distributed Unit

[0053] · CRI: CSI-RS Resource Indicator

[0054] 3. Reasons for the Proposal

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

[0056] …

[0057] Coherent joint transmission (CJT) provides downlink spectral efficiency and coverage gain. In Rel-18, Type-II CSI has been enhanced to accommodate CJT assuming ideal synchronization and backhaul. For example, scenarios such as inter-site CJT and base stations equipped with distributed remote radio heads (RRHs) require additional delay and phase / frequency calibration. For TDD, additional inter-TRP DL / UL calibration between TRPs is also beneficial to ensure that proper DL / UL reciprocity holds. Since the UE has more knowledge of the DL channel conditions under both FDD and TDD, it is obvious that an inter-TRP calibration report from CSI-RS measurements is required, which not only expands the deployment scenarios but also provides additional robustness for CJT operation.

[0058] …

[0059] In [2] 3GPP TS 38.214 i00, the following is provided.

[0060] 5.1.5 Antenna Port Quasi-Co-location

[0061] The UE may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on the detected PDCCH with DCI established for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring the 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 (if configured) for the second DL RS. In the case of two DL RSs, the QCL types will be different, regardless of whether the reference is for 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:

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

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

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

[0065] - 'Type D': {Spatial Rx parameter}

[0066] The UE may be configured with a list of up to 128 TCI-State configurations within the higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config to provide quasi-co-located reference signals for the DM-RS of the PDSCH and the DM-RS of the PDCCH and the CSI-RS in the BWP / CC, and to provide a reference, where applicable, for determining the UL TX spatial filters for the PUSCH and PUCCH resources and the SRS based on dynamic grants and configured grants in the BWP / CC.

[0067] If the TCI-State or TCI-UL-State configuration does not exist in the BWP of the CC, the UE may apply the TCI-State or TCI-UL-State configuration from the reference BWP of the reference CC.

[0068] The UE receives an activation command as described in Section 6.1.3.xx of [10, TS 38.321], Section 6.1.3.47 of [10, TS 38.321], or Section 6.1.4.xx of [10, TS 38.321]. The activation command is used to map up to 8 TCI states and / or several pairs of TCI states (where one TCI state is for DL channels / signals and / or one TCI state is for UL channels / signals) to the code points of the DCI field 'Transmission Configuration Indication' for one or a group of CC / DL BWPs, [and / ] or map up to 8 groups of TCI states (where each group consists of up to two TCI states for DL and UL signals / channels, or up to two TCI states for DL channels / signals and up to two TCI states for UL channels / signals) to the code points of the DCI field 'Transmission Configuration Indication' for one or a group of CC / DL BWPs (and, where applicable, for one or a group of CC / UL BWPs). When a group of TCI state IDs is activated for a group of CC / DL BWPs and, where applicable, for a group of CC / UL BWPs, the applicable list of CCs is determined by the CCs indicated in the activation command, and the same group of TCI state IDs is applied to all DL and / or UL BWPs in the indicated CCs. If the activation command maps a TCI-State and / or a TCI-UL-State to only one TCI code point, the UE shall apply the indicated TCI-State and / or TCI-UL-State to one or a group of CC / DL BWPs, and, where applicable, to one or a group of CC / UL BWPs, once the indicated mapping for a single TCI code point is applied as described in [11, TS 38.133].

[0069] 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 where the TCI state is applicable.

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

[0071] If the UE receives a higher layer configuration of a dl-OrJointTCI-StateList with a single TCI-State that can be used as the indicated TCI state or an ul-TCI-StateList with a single TCI-UL-State, the UE determines the UL TX spatial filter from the configured TCI states for PUSCH and PUCCH based on dynamic grants and configured grants and for SRS to which the indicated TCI state is applied, where applicable.

[0072] When a UE configured with a dl-OrJointTCI-StateList is to transmit a PUCCH with a positive HARQ-ACK or a PUSCH with a positive HARQ-ACK 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 previously indicated TCI state, the indicated TCI-State and / or TCI-UL-State shall be applied starting from the first time slot that is at least beamAppTime symbols after the last symbol of the PUCCH or PUSCH. Both the first time slot and beamAppTime symbols are determined on the active BWP, where the minimum SCS among the BWPs from the CC is applied to the indicated TCI-State or TCI-UL-State active at the end of the PUCCH or PUSCH carrying the positive HARQ-ACK.

[0073] 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 section 6.1.3.24 of [10, TS 38.321], which is 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 does not expect to receive more than 8 TCI states in the activation command.

[0074] When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and when the number S of code points 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 sections 6.1.3.14 and 6.1.3.24 of [10, TS 38.321], only the first S activated code points are applied to DCI format 1_2.

[0075] When the UE is to transmit a PUCCH with HARQ-ACK information corresponding to the PDSCH carrying the activation command in slot n, the indicated mapping between the TCI state and the code point of the DCI field 'Transmission Configuration Indication' shall be applied starting from the first slot after the slot where μ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for k mac which has a value of 0 for frequency range 1, and k mac is provided by K-Mac, or k mac = 0 if K-Mac is not provided. If tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET scheduling the 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 block determined with respect to the qcl-Type set to 'typeA' and also with respect to the qcl-Type set to 'typeD' if applicable in the initial access procedure.

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

[0077] For the periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall expect the TCI-State to indicate one of the following quasi-co-location types:

[0078] - 'typeC' with an SS / PBCH block, and 'typeD' with the same SS / PBCH block when applicable, where the PCI of the SS / PBCH block can be different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, and SFN offset of the SS / PBCH block from the serving cell and the SS / PBCH block with a different PCI from the serving cell are the same, or

[0079] - 'typeC' with an SS / PBCH block, and 'typeD' with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition when applicable, where the PCI of the SS / PBCH block can be different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, and SFN offset of the SS / PBCH block from the serving cell and the SS / PBCH block with a different PCI from the serving cell are the same.

[0080] For periodic / semi-persistent CSI-RS, if the UE is configured with a dl-OrJointTCI-StateList, the UE may assume that the indicated TCI-State is not applied.

[0081] For aperiodic CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall expect the TCI-State indication to be set to the qcl-Type of 'typeA' with the periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and when applicable, to the qcl-Type of 'typeD' with the same periodic CSI-RS resources.

[0082] For CSI-RS resources in an NZP-CSI-RS-ResourceSet not configured with the higher layer parameter trs-Info and not configured with the higher layer parameter repetition, the UE shall expect the TCI-State indication to be one of the following quasi-co-location types:

[0083] - 'typeA' with the CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' with the same CSI-RS resources when applicable, or

[0084] - 'typeA' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' with an SS / PBCH block when applicable, where the PCI of the SS / PBCH block can be different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, and SFN offset of the SS / PBCH block from the serving cell and the SS / PBCH block with a different PCI from the serving cell are the same, or

[0085] - 'typeA' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition when applicable, or

[0086] - 'typeB' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info when 'typeD' is not applicable.

[0087] For CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, the UE shall expect the TCI-State to indicate one of the following quasi-co-location types:

[0088] - 'typeA' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' with the same CSI-RS resources when applicable, or

[0089] - 'typeA' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' for CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition when applicable, or

[0090] - 'typeC' with an SS / PBCH block, and 'typeD' with the same SS / PBCH block when applicable. The reference RS can additionally be an SS / PBCH block with a PCI different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, and SFN offset of the SS / PBCH block from the serving cell and the SS / PBCH block with a different PCI from the serving cell are the same.

[0091] For the DM-RS for PDCCH, if the UE is not configured with dl-OrJointTCI-StateList, the UE shall expect the TCI-State to indicate one of the following quasi-co-location types:

[0092] - 'typeA' of the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' of the same CSI-RS resources when applicable, or

[0093] - 'typeA' of the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and 'typeD' of the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition when applicable, or

[0094] - 'typeA' of the CSI-RS resources in the NZP-CSI-RS-ResourceSet not configured with the higher layer parameter trs-Info and not configured with the higher layer parameter repetition, and 'typeD' of the same CSI-RS resources when applicable.

[0095] 5.1.6 UE procedures for receiving reference signals

[0096] 5.1.6.1 CSI-RS reception procedures

[0097] The CSI-RS defined in clause 7.4.1.5 of [4, TS 38.211] can be used for time / frequency tracking, CSI calculation, L1-RSRP calculation, Layer 1 signal to interference and noise ratio (L1-SINR) calculation, mobility, and tracking during fast SCell activation.

[0098] For CSI-RS resources associated with an NZP-CSI-RS-ResourceSet with a higher layer parameter repetition set to 'on', it should not be expected that the UE is configured with CSI-RS on symbols where the UE is also configured to listen to a CORESET. For other NZP-CSI-RS-ResourceSet configurations, if the UE is configured with a CSI-RS resource and a search space set associated with a CORESET in the same OFDM symbol, then, where 'typeD' applies, the UE may assume that the CSI-RS and PDCCH DM-RS transmitted in all search space sets associated with the CORESET are quasi-co-located with 'typeD'. If the CORESET is activated with two TCI states, then the UE may assume the first TCI state of the CORESET as a predefined QCL assumption for the CSI-RS. Where 'typeD' applies, this also applies when the CSI-RS and CORESET are in different in-band component carriers. Additionally, it should not be expected that the UE is configured with CSI-RS in PRBs that overlap with those PRBs of the CORESET in the OFDM symbol occupied by the search space set.

[0099] The UE is not expected to receive CSI-RS and SIB1 messages in overlapping PRBs in the OFDM symbol in which SIB1 is transmitted.

[0100] 5.1.6.1.1 CSI-RS for tracking

[0101] It is expected that a UE in RRC connected mode receives a higher layer UE-specific configuration of an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info.

[0102] For an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall assume that the antenna ports with the same port index of the NZP CSI-RS resources configured in the NZP-CSI-RS-ResourceSet are the same.

[0103] - For frequency range 1, the UE may be configured with one or more NZP CSI-RS sets, where an NZP-CSI-RS-ResourceSet consists of four periodic NZP CSI-RS resources in two consecutive time slots, with two periodic NZP CSI-RS resources in each time slot. If no two consecutive time slots are indicated as downlink time slots by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, the UE may be configured with one or more NZP CSI-RS sets, where an NZP-CSI-RS-ResourceSet consists of two periodic NZP CSI-RS resources in one time slot.

[0104] - For frequency range 2, the UE may be configured with one or more NZP CSI-RS sets, where an NZP-CSI-RS-ResourceSet consists of two periodic CSI-RS resources in one time slot, or an NZP-CSI-RS-ResourceSet with four periodic NZP CSI-RS resources in two consecutive time slots, with two periodic NZP CSI-RS resources in each time slot.

[0105] A UE configured with an NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info may configure the CSI-RS resources as:

[0106] - Periodic, where the CSI-RS resources in the NZP-CSI-RS-ResourceSet are configured with the same periodicity, bandwidth, and subcarrier position.

[0107] - One set is for periodic CSI-RS resources and the second set is for aperiodic CSI-RS resources, where the aperiodic CSI-RS and periodic CSI-RS resources have the same bandwidth (with the same RB positions), and the aperiodic CSI-RS is configured with qcl-Type set to 'typeA' and 'typeD', and the 'typeA' and 'typeD' have the periodic CSI-RS resources where applicable. For frequency range 2, the UE does not expect the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource to be less than in the CSI-RS symbols where beamSwitchTiming is a value reported by the UE defined in [13, TS38.306], and the reported value is one of the values and if μ PDCCH < μCSIRS The beam switching timing delay d is defined in Table 5.2.1.5.1a-1, otherwise d is zero. The UE shall expect that the periodic CSI-RS resource set and the aperiodic CSI-RS resource set are configured with the same number of CSI-RS resources and that the same number of CSI-RS resources are configured in one time slot. For an aperiodic CSI-RS resource set, if triggered and if the associated periodic CSI-RS resource set is configured with four periodic CSI-RS resources for two consecutive time slots, with two periodic CSI-RS resources in each time slot, the higher layer parameter aperiodicTriggeringOffset indicates the triggering offset for the first time slot for the first two CSI-RS resources in the set.

[0108] …

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

[0110] 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 Section 5.2.2.3.1 are transmitted using the same downlink spatial domain transmission filter, where the CSI-RS resources in the NZP-CSI-RS-ResourceSet are transmitted in different OFDM symbols. If repetition is set to 'off', the UE shall not assume that the CSI-RS resources within the NZP-CSI-RS-ResourceSet are transmitted using the same downlink spatial domain transmission filter.

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

[0112] …

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

[0114] 5.2.1 Channel state information framework

[0115] The procedures for the aperiodic CSI reporting described in this section assume that the CSI report is triggered by DCI format 0_1, but the procedures are equally applicable to CSI reports triggered by DCI format 0_2 by applying the higher layer parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize. The procedures for the aperiodic CSI reporting described in this section assume that the CSI report is triggered by DCI format 0_1, but the procedures are equally applicable to CSI reports triggered by DCI format 0_3.

[0116] The UE can use time and frequency resources to report CSI controlled by the gNB. The CSI can consist of a Channel Quality Indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH Block Resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), L1-RSRP, L1-SINR, CapabilityIndex, or a time-domain channel property (TDCP).

[0117] For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, CapabilityIndex, TDCP, the UE is configured by higher layers with N ≥ 1 CSI-ReportConfig reporting settings and / or [X ≥ 1 LTM-CSI-ReportConfig reporting settings], M ≥ 1 CSI-ResourceConfig resource settings and / or [Y ≥ 1 LTM-CSI-ResourceConfig resource settings], and one or two lists of trigger states (given by the higher layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state in the CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs [and / or LTM-CSI-ReportConfigs], indicating the resource set ID of the channel and optionally the resource set ID of the interference [where the resource set of the interference can only exist under the reporting settings given by the CSI-ReportConfig], and if the associated CSI-ReportConfig is configured with a list of sub-configurations, the trigger state additionally contains one or more [csi-ReportSubConfigID], as described in Section 5.2.1.1. Each trigger state in the CSI-SemiPersistentOnPUSCH-TriggerStateList contains an associated CSI-ReportConfig [or LTM-CSI-ReportConfig], and if the associated CSI-ReportConfig is configured with a list of sub-configurations, the trigger state additionally contains one or more [csi-ReportSubConfigID], as described in Section 5.2.1.1.

[0118] 5.2.1.1 Reporting Settings

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

[0120] Each reporting setting [LTM-CSI-ReportConfig] is associated with [LTM-CSI-ResourceConfig] for channel measurement and contains parameters for time domain behavior, the number of cells, and the number of reference signals provided per cell by [noOfReportedCells] and [noOfReportedRSPerCell] respectively, including L1 measurement results associated with the current SpCell through SpCellInclusion.

[0121] The time domain behavior of CSI-ReportConfig is indicated by the higher layer parameter reportConfigType and can be set to 'aperiodic','semiPersistentOnPUCCH','semiPersistentOnPUSCH' or 'periodic'. For 'periodic' and'semiPersistentOnPUCCH' / 'semiPersistentOnPUSCH' CSI reports, the configured periodicity and slot offset apply to the base parameters of the UL BWP on which the CSI report is configured to be transmitted. The higher layer parameter reportQuantity indicates the CSI-related, L1-RSRP-related, L1-SINR-related, CapabilityIndex-related or TDCP-related quantity to be reported. reportFreqConfiguration indicates the reporting granularity in the frequency domain, including the CSI reporting band and whether the PMI / CQI reporting is wideband or subband.... CSI-ReportConfig can also include CodebookConfig, which contains configuration parameters for: Type-I, Type II, enhanced Type IICSI, further enhanced Type II port selection, enhanced Type II for coherent joint transmission (CJT), further enhanced Type II port selection for CJT, enhanced Type II for predicted PMI or further enhanced Type II port selection for predicted PMI (including codebook subset restrictions when applicable) and group-based reporting configuration. If reportConfigType is set to 'aperiodic', it is not expected that the UE is configured with CSI report settings associated with the dormant DL BWP. CSI-ReportConfig can include a list of sub-configurations provided by the higher layer parameter [csi-ReportSubConfigList], where each sub-configuration is identified by [csi-ReportSubConfigID] and corresponds to a list of one or more CSI-RS resources or to a subset of CSI-RS antenna ports, and / or to the power offset of the PDSCH relative to the CSI-RS. It is not expected that the UE is configured with a CSI-ReportConfig that contains a mixture of sub-configurations each corresponding to a list of one or more CSI-RS resources and some other sub-configurations each corresponding to a subset of CSI-RS antenna ports.

[0122] 5.2.1.2 Resource Setup

[0123] Each CSI resource setting CSI-ResourceConfig contains a configuration of a list of S≥1 CSI resource sets (given by the higher layer parameter csi-RS-ResourceSetList), where the list includes references to either or both of the NZP CSI-RS resource set and the SS / PBCH block set, or the list includes a reference to the CSI-IM resource set. Each CSI resource setting is located in the DL BWP identified by the higher layer parameter BWP-id, and all CSI resource settings linked to a CSI reporting setting have the same DL BWP.

[0124] The time domain behavior of the CSI-RS resources within a CSI resource setting is indicated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource settings, when the UE is configured with groupBasedBeamReporting-r17 or groupBasedBeamReporting-v18, the number of configured CSI resource sets is S = 2, and in other cases, the number of configured CSI-RS resource sets is restricted to S = 1. Except for periodic CSI resource settings, when the UE is configured with TDCP reporting, the number of CSI-RS resource sets in the CSI resource setting used for channel measurement is K TRS ∈{1, 2, 3} and all CSI-RS resource sets are configured with the higher layer parameter trs-Info. For periodic and semi-persistent CSI resource settings, the configured periodicity and slot offset are given in the base parameters of their associated DL BWP given by BWP-id. When the UE is configured with multiple CSI-ResourceConfigs that form the same NZP CSI-RS resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. When the UE is configured with multiple CSI-ResourceConfigs that form the same CSI-IM resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. All CSI resource settings linked to a CSI reporting setting shall have the same time domain behavior.

[0125] For TDCP measurement, one aperiodic or periodic CSI resource setting is configured, and the resource setting is used for channel measurement of CSI-RS for tracking.

[0126] Each LTM CSI resource setting [LTM-CSI-ResourceConfig] contains the configuration of [LTM-CSI-SSB-ResourceSet], and the [LTM-CSI-SSB-ResourceSet] includes a list of Z≥1 SS / PBCH block indices (given by [LTM-csi-SSB-ResourceList]) and a list of Z [PCI indices] of cells referring to the SS / PBCH block indices (given by [LTM-CandidateId-list]). The UE determines the time-domain behavior of the SS / PBCH block according to ssb-Periodicity and ssb-PositionsInBurst, and the frequency-domain behavior of the SS / PBCH block is determined by the higher-layer parameters subcarrierspacing and ssbFrequency.

[0127] 5.2.1.4 Reporting configuration

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

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

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

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

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

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

[0134] Table 5.2.1.4-1: Triggering / Activation of CSI Reporting for Possible CSI-RS Configurations.

[0135]

[0136]

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

[0138] For periodic or semi-persistent CSI reporting on PUCCH, the periodicity T CSI (measured in a slot) and the slot offset T offset are configured by the higher layer parameter reportSlotConfig. Unless otherwise specified, the UE shall transmit the CSI report in a frame with SFN n f and the number of slots within the frame being such that

[0139]

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

[0141] For semi-persistent CSI reporting on PUSCH, the periodicity T CSI (measured in a slot) is configured by the higher layer parameter reportSlotConfig. Unless otherwise specified, the UE shall transmit the CSI report in a frame with SFN n f and the number of slots within the frame being such that

[0142]

[0143] where and They are the SFN and the number of intra-frame time slots for the initial semi-persistent PUSCH transmission according to the activated DCI, respectively.

[0144] For semi-persistent or aperiodic CSI reporting on PUSCH, the allowed time slot offset is configured by the following higher layer parameters:

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

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

[0147] - In other cases, the allowed time slot offset is configured by the higher layer parameter reportSlotOffsetList or reportSlotOffsetList-r17.

[0148] 5.2.1.4.1 Resource setting configuration

[0149] For aperiodic CSI and for aperiodic CSI resource setting, each trigger state configured by the higher layer parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfig, where the CSI-ReportConfig configured with groupBasedBeamReporting-r17 or groupBasedBeamReporting-v18 is associated with resourcesForChannel and resourcesForChannel2 for L1-RSRP measurement, which correspond to the first resource set and the second resource set respectively.

[0150] For a UE configured with [LTM-CSI-ReportConfig], the aperiodic, semi-persistent or periodic CSI is associated with one resource setting for L1-RSRP measurement given by [LTM-resourcesForChannelMeasurement].

[0151] If each subconfiguration contains a list of one or more NZP CSI-RS resources, a resource subset of the NZP CSI-RS resource set for channel measurement (where the subset contains one or more resources) corresponds to the subconfiguration included in the CSI-ReportConfig, or if each subconfiguration does not contain a list of NZP CSI-RS resources, all resources of the NZP CSI-RS resource set for channel measurement correspond to each subconfiguration included in the CSI-ReportConfig, as described in Section 5.2.1.4.2.

[0152] 5.2.1.4.2 Reporting quantity configuration

[0153] The UE may be configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to 'none', 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'cri-SINR','ssb-Index-RSRP','ssb-Index-SINR', 'cri-RI-LI-PMI-CQI', 'cri-RSRP-index','ssb-Index-RSRP-Index', 'cri-SINR-Index','ssb-Index-SINR-Index' or 'tdcp'.

[0154] …

[0155] 5.2.1.4.3 L1-RSRP reporting

[0156] For L1-RSRP calculation

[0157] - When co-located per resource with 'typeC' and 'typeD' where applicable, the UE may be configured with CSI-RS resources, SS / PBCH block resources, or both CSI-RS and SS / PBCH block resources.

[0158] - The UE may be configured with CSI-RS resource settings for up to 16 CSI-RS resource sets, with up to 64 resources in each set. The total number of different CSI-RS resources across all resource sets does not exceed 128.

[0159] For L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to one, or if both of the higher layer parameters [noOfReportedCells] and [noOfReportedRSPerCell] are configured to one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with a step size of 1 dB; 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, or if any one of the higher layer parameters [noOfReportedCells] and [noOfReportedRSPerCell] is configured to be greater than one, the UE shall use differential L1-RSRP based reporting, where the maximum measured value of L1-RSRP is quantized to a 7-bit value in the range [-140, -44] dBm with a step size of 1 dB, and the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is calculated with a step size of 2 dB with reference to the maximum measured L1-RSRP value that is part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133].

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

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

[0162] When the UE is configured with a CSI-ReportConfig where the higher layer parameter reportQuantity is set to 'cri-RSRP-Index' or'ssb-Index-RSRP-Index', the index of the 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.

[0163] …

[0164] 5.2.1.5 CSI Report and Trigger / Activation of CSI-RS

[0165] 5.2.1.5.1 Aperiodic CSI Report / Aperiodic CSI-RS When the Triggering PDCCH and CSI-RS Have the Same Basic Parameters

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

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

[0168] - After covering the last symbol of the PDCCH span carrying the DCI for CSI triggering and before the first symbol of the triggered NZP CSI-RS or CSI-IM, it is not expected that the UE has any other BWP switching in the said carrier.

[0169] Use the CSI request field in the DCI to start the trigger state.

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

[0171] - When the number of configured CSI trigger states in the CSI-AperiodicTriggerStateList is greater than where N TS is the number of bits in the DCI CSI request field, the UE receives a sub-selection indication, as described in Section 6.1.3.13 of [10, TS38.321], which is used to map up to trigger states to the code points of the CSI request field in the DCI. N TS is configured by the higher layer parameter reportTriggerSize, where N TS ∈{0,1,2,3,4,5,6}. When the UE will transmit the PUCCH with HARQ-ACK information corresponding to the PDSCH carrying the sub-selection indication in slot n, the corresponding actions in [10, TS 38.321] and the UE assumptions for mapping the selected CSI trigger states to the code points of the DCI CSI request field shall be applied starting from the first slot after slot where μ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for k mac which is 0 for frequency range 1, and k mac is provided by K-Mac, or k mac = 0 if K-Mac is not provided.

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

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

[0174] - Whether the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource in the NZP-CSI-RS-ResourceSet not configured with the higher layer parameter trs-Info is less than the reported value beamSwitchTiming among the values defined in [13, TS38.306] when enableBeamSwitchTiming is not provided, or whether the scheduling offset is less than when the UE provides beamSwitchTiming-r16, enableBeamSwitchTiming is provided and the NZP-CSI-RS-ResourceSet is configured with the higher layer parameter repetition set to 'off' or not configured with the higher layer parameter repetition, or whether the scheduling offset is less than the threshold beamSwitchTiming-r16 reported by the UE when enableBeamSwitchTiming is provided and the NZP-CSI-RS-ResourceSet is configured with the higher layer parameter repetition set to 'on'.

[0175] - The non-zero code points of the CSI request field in the DCI are mapped to the CSI triggering states according to the order of the associated positions of at most triggering states in the CSI-AperiodicTriggerStateList, where the code point '1' is mapped to the triggering state in the first position.

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

[0177] If a UE is configured with a single carrier for uplink, it is not expected that the UE transmits more than one aperiodic CSI report triggered by different DCIs on overlapping OFDM symbols.

[0178] When a UE is configured with a dl-OrJointTCI-StateList and has two indicated TCI states, if the aperiodic CSI-RS resource set for CSI or BM is configured with followUnifiedTCI-State and if the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set is equal to or greater than a threshold, a higher layer configuration can be provided to the aperiodic CSI-RS resource set or the CSI-RS resources in the aperiodic CSI-RS resource set to inform the UE that the first or second indicated TCI-State should be applied to the aperiodic CSI-RS resource set or the CSI-RS resources in the aperiodic CSI-RS resource set.

[0179] - If a UE is configured with a higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in different ControlResourceSets, the first and second indicated TCI-States correspond to the indicated TCI-States specific to coresetPoolIndex value 0 and value 1, respectively.

[0180] When a UE is configured with a dl-OrJointTCI-StateList and has two indicated TCI states, and if the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set is less than the threshold:

[0181] - If there is no DL signal in the same symbol as the aperiodic CSI-RS

[0182] - If the UE is in frequency range 1, or the UE reports its ability of [two preset beams for S-DCI-based MTRP] in frequency range 2, the UE shall apply the first or second indicated joint / DL TCI state to the aperiodic CSI-RS according to the higher layer configuration provided to the aperiodic CSI-RS resource or aperiodic CSI-RS resource set.

[0183] - Otherwise, the UE shall apply the first indicated joint / DL TCI state to the aperiodic CSI-RS.

[0184] When the UE is configured with dl-OrJointTCI-StateList, configured by a higher layer parameter PDCCH-Config containing two different values of coresetPoolIndex in different ControlResourceSets, with two indicated TCI states, and if the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource in the aperiodic CSI-RS resource set is less than a threshold:

[0185] - If there is no DL signal in the same symbol as the aperiodic CSI-RS

[0186] - If the UE is in frequency range 1, or the UE reports its ability of [preset beam per coresetPoolIndex for M-DCI-based MTRP] in frequency range 2, the UE shall apply the first or second indicated joint / DL TCI state to the aperiodic CSI-RS according to the higher layer configuration provided to the aperiodic CSI-RS resource or aperiodic CSI-RS resource set.

[0187] - Otherwise, the UE shall apply the indicated joint / DL TCI state specific to coresetPoolIndex value 0 to the aperiodic CSI-RS resource set.

[0188] …

[0189] …

[0190] In [3]R1-2204369, the following is provided.

[0191] Deployment scenarios of CJT

[0192] In the Rel-18 MIMO WID for CJT, it is assumed that the backhaul and synchronization are ideal and the number of antenna ports is the same among at most 4 TRPs. For multiple TRPs used for CJT, there are generally two deployment scenarios for discussion: intra-site M-TRP and inter-site M-TRP, as Figure 3-1as shown

[0193] For in-site M-TRP CJT, multiple TRPs are co-located and have the same transmission power. One example is to consider the simultaneous transmission of multiple panels from the same gNB. For inter-site M-TRP CJT, multiple TRPs are non-co-located. In this case, CJT transmission can be used to schedule UEs only when the measured RSRP from multiple TRPs is within a certain threshold. And fiber optic backhaul can be used to ensure synchronization between multiple TRPs.

[0194] Figure 5A is a reproduction in R1-2204369 of Figure 3-1 : Two deployment scenarios of M-TRP CJT, (a) In-site M-TRP CJT.

[0195] Figure 5B is a reproduction in R1-2204369 of Figure 3-1 : Two deployment scenarios of M-TRP CJT, (b) Inter-site M-TRP CJT.

[0196] In Rel-18, in-site M-TRP and inter-site M-TRP scenarios should be studied and high-priority scenarios for NW deployment should be identified. Since it is easier to deploy in-site M-TRP CJT in an actual NW, it can be preferentially addressed in Rel-18.

[0197] Proposal 3-1

[0198] · Study in-site M-TRP and inter-site M-TRP scenarios for CJT.

[0199] · The priority of in-site M-TRP CJT is higher than that of inter-site M-TRP CJT.

[0200] In [4] 3GPP TS 38.211i00, the relevant paragraphs are quoted below.

[0201] 4 Frame Structure and Physical Resources

[0202] 4.1 Outline

[0203] Throughout this specification, unless otherwise indicated, the size of each field in the time domain is expressed in time unit T c = 1 / (Df max × N f ), where Δf max = 480·10 3 Hz and N f = 4096. The constant k = T s / T c = 64, where T s= 1 / (Df ref × N f,ref ), Δf ref = 15 × 10 3 Hz and N f,ref = 2048.

[0204] …

[0205] 4.4 Physical Resources

[0206] 4.4.1 Antenna Ports

[0207] Define an antenna port such that the channel through which a symbol is conveyed on the antenna port can be inferred from the channel through which another symbol is conveyed on the same antenna port.

[0208] If the large-scale properties of the channel through which a symbol is conveyed on one antenna port can be inferred from the channel through which a symbol is conveyed on another antenna port, then these two antenna ports are said to be quasi-co-located. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0209] In [5] 3GPP TS 38.212 i00, the relevant paragraphs are quoted below.

[0210] 7.3.1.1.2 Format 0_1

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

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

[0213] - Identifier of the DCI format - 1 bit

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

[0215] - Carrier indicator - 0 or 3 bits, as defined in Section 10.1 of [5, TS38.213]. When this format is carried by the PDCCH on the primary cell and the UE is configured for scheduling from the SCell on the primary cell, this field is reserved and has the same number of bits as the number of bits of this format carried by the PDCH on the SCell, for scheduling on the primary cell.

[0216] - Bandwidth part indicator - The number n of UL BWPs configured by the higher layers BWP,RRC Determined 0, 1 or 2 bits, excluding the initial UL bandwidth part. The bit width of this field is determined as bits, where

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

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

[0219] - Frequency domain resource allocation - The number of bits is determined as follows, where is the size of the active UL bandwidth part:

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

[0221] ‘’‘’ - For resource allocation type 0,...

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

[0223] - According to Section 6.1.2.2.2 of [6, TS 38.214], bits provide the frequency domain resource allocation

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

[0225] - 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-TimeDomainAllocationList is configured, then it is defined as 0, 1, 2, 3 or 4 bits as in Section 6.1.2.1 of [6, TS38.214]. The bit width of this field is determined as bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationList.

[0226] …

[0227] - Otherwise, the bit width of this field is determined as units digit, where I is the number of entries in the preset table.

[0228] For transport block 1:

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

[0230] - New data indicator - If the number of scheduled PUSCHs indicated by the time domain resource allocation field is 1, then 1 bit; 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, where each bit corresponds to a scheduled PUSCH, as defined in Section 6.1.4 of [6, TS 38.214].

[0231] - Redundancy version - The number of bits determined as follows:

[0232] - 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;

[0233] - 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, where each bit corresponds to a scheduled PUSCH, as defined in Section 6.1.4 of [6, TS 38.214], and the redundancy version is determined according to Table 7.3.1.1.2-34.

[0234] - …

[0235] - HARQ process number - If the higher layer parameter harq-ProcessNumberSizeDCI-0-1 is configured, then 5 bits; otherwise 4 bits

[0236] …

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

[0238] …

[0239] …

[0240] 7.3.1.2.2 Format 1_1

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

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

[0243] - Identifier of the DCI format - 1 bit

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

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

[0246] - Bandwidth part indicator - The number n of DL BWPs configured by the higher layers BWP ,RRC Determined 0, 1, or 2 bits, excluding the initial DL bandwidth part. The bit width of this field is determined as bits, where

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

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

[0249] …

[0250] - Transmission configuration indicator - 0 bits if the higher layer parameter tci-PresentInDCI is not enabled; otherwise 3 bits as defined in Section 5.1.5 of [6, TS38.214].

[0251] - …

[0252] …

[0253] In [6] 3GPP TS 38.331 h60, the relevant information elements (IEs) and parameters are cited below.

[0254] mTRP-CSI-EnhancementPerBC-r17 SEQUENCE{

[0255] maxNumNZP-CSI-RS-r17

[0256] INTEGER(2..8),

[0257] cSI-Report-mode-r17

[0258] ENUMERATED{Mode 1, Mode 2, both},

[0259] supportedComboAcrossCCs-r17 SEQUENCE(SIZE(1..16))OF CSI-MultiTRP-SupportedCombinations-r17,

[0260] codebookMode-NCJT-r17 ENUMERATED{Mode 1, Mode 1 and 2}

[0261] }

[0262] -CSI-AperiodicTriggerStateList

[0263] The CSI-AperiodicTriggerStateList IE is used to configure a list of aperiodic trigger states for the UE. Each code point of the DCI field "CSI request" is associated with a trigger state (see TS 38.321 [3], section 6.1.3.13). After receiving a value associated with a trigger state, the UE will perform measurements and aperiodic reporting of CSI-RS, CSI-IM, and / or SSB (reference signals) on L1 according to all entries in the associatedReportConfigInfoList for the said trigger state.

[0264] CSI-AperiodicTriggerStateList information element

[0265]

[0266]

[0267]

[0268]

[0269] -CSI-MeasConfig

[0270] IE CSI-MeasConfig is used to configure CSI-RS (Reference Signals) belonging to the serving cell in which CSI-MeasConfig is included, the channel state information reporting to be transmitted on PUCCH on the serving cell in which CSI-MeasConfig is included, and the channel state information reporting on PUSCH triggered by DCI received on the serving cell in which CSI-MeasConfig is included. See also TS 38.214

[19] , Section 5.2.

[0271] CSI-MeasConfig information element

[0272]

[0273]

[0274]

[0275]

[0276] -CSI-ReportConfig

[0277] IE CSI-ReportConfig is used to configure periodic or semi-persistent reporting transmitted on PUCCH on the cell in which CSI-ReportConfig is included, or to configure semi-persistent or aperiodic reporting transmitted on PUSCH triggered by DCI received on the cell in which CSI-ReportConfig is included (in this case, the cell on which the reporting is transmitted is determined by the received DCI). See TS 38.214

[19] , Section 5.2.1.

[0278] CSI-ReportConfig information element

[0279]

[0280]

[0281]

[0282]

[0283]

[0284]

[0285] -CSI-ResourceConfig

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

[0287] CSI-ResourceConfig information element

[0288]

[0289]

[0290]

[0291]

[0292] -ZP-CSI-RS-Resource

[0293] IE ZP-CSI-RS-Resource is used to configure zero-power (ZP) CSI-RS resources (see TS38.214

[19] , Section 5.1.4.2). Reconfiguration of ZP-CSI-RS-Resource between periodic or semi-persistent and aperiodic is not supported.

[0294] ZP-CSI-RS-Resource information element

[0295]

[0296]

[0297]

[0298] -ZP-CSI-RS-ResourceSet

[0299] IE ZP-CSI-RS-ResourceSet refers to a set of ZP-CSI-RS-Resources using its ZP-CSI-RS-ResourceIds.

[0300] ZP-CSI-RS-ResourceSet information element

[0301]

[0302]

[0303]

[0304] -TCI-State

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

[0306] TCI-State information element

[0307]

[0308]

[0309]

[0310] In [7] 3GPP TS 38.321 h50, the relevant MAC CE information is cited below.

[0311] 6.1.3.13 Aperiodic CSI trigger state sub - selection MAC CE

[0312] The aperiodic CSI trigger state sub - selection MAC CE is identified by a MAC sub - header with the LCID specified in Table 6.2.1 - 1. It has a variable size consisting of the following fields:

[0313] - 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;

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

[0315] - T i： This field indicates the selection status of the aperiodic trigger states configured within aperiodicTriggerStateList, as specified in TS 38.331 [5]. T0 refers to the first trigger state in the list, T1 refers to the second trigger state, and so on. If the list does not contain an entry with index i, the MAC entity shall ignore the T i field. The T i field is set to 1 to indicate that the aperiodic trigger state i will be mapped to the code point of the DCI CSI request field, as specified in TS 38.214 [7]. The code point to which the aperiodic trigger state is mapped is determined by its ordinal position among all the aperiodic trigger states with its T i field set to 1, i.e., T iThe first aperiodic triggering state with the field set to 1 will be mapped to the code point value 1, T i The second aperiodic triggering state with the field set to 1 will be mapped to the code point value 2, and so on. The maximum number of mapped aperiodic triggering states is 63;

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

[0317] Figure 6 It is in Figure 6 .1.3.13-1 of 3GPP TS 38.321 h50: Reproduction of aperiodic CSI triggering state sub-selection MAC CE.

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

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

[0320] - 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;

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

[0322] - UL BWP ID: This field indicates the UL BWP to which the MAC CE applies as the code point of the DCI bandwidth part indicator field 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 a reserved bit. The length of the BWP ID field is 2 bits;

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

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

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

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

[0327] Figure 7 is the reproduction of Figure 6 .1.3.47-1 in 3GPP TS 38.321h50: Unified TCI state activation / deactivation MAC CE.

[0328] …

[0329] 5.9 Activation / Deactivation of SCell

[0330] If the MAC entity is configured with one or more SCell(s), the network may activate and deactivate the configured SCell(s). After configuring an SCell, the SCell is deactivated unless the parameter sCellState is set by the upper layer for SCell activation.

[0331] The configured SCell(s) are activated and deactivated by:

[0332] - Receiving the SCell activation / deactivation MAC CE as described in Section 6.1.3.10;

[0333] - Receiving the enhanced SCell activation / deactivation MAC CE as described in Section 6.1.3.55;

[0334] - Configuring the sCellDeactivationTimer timer for each configured SCell (except for the SCell configured with PUCCH, if any): Deactivate the associated SCell when the timer expires;

[0335] - Configuring sCellState for each configured SCell: If configured, activate the associated SCell after SCell configuration.

[0336] - Receiving scg-State: Deactivate the SCell(s) of the SCG.

[0337] The MAC entity shall, for each configured SCell:

[0338] 1> If the SCell is configured with sCellState set to be activated after SCell configuration, or receives the SCell activation / deactivation MAC CE or the enhanced SCell activation / deactivation MAC CE for activating the SCell:

[0339] 2> If the SCell was deactivated before receiving the enhanced SCell activation / deactivation MAC CE and TRS is indicated for that SCell:

[0340] 3> Indicate information about the TRS to the lower layer.

[0341] 2> If the SCell was deactivated before receiving the SCell activation / deactivation MAC CE or the enhanced SCell activation / deactivation MAC CE; or

[0342] 2> If the SCell is configured with sCellState set to be activated after SCell configuration:

[0343] 3> If firstActiveDownlinkBWP-Id is not set to a dormant BWP:

[0344] 4> Activate the SCell according to the timing defined for MAC CE activation in TS 38.213 [6] and according to the timing defined for direct SCell activation in TS 38.133

[11] ; that is, apply normal SCell operation, including:

[0345] 5> SRS transmission on the SCell;

[0346] 5> CSI reporting for the SCell;

[0347] 5> PDCCH monitoring on the SCell;

[0348] 5> PDCCH monitoring for the SCell;

[0349] 5> PUCCH transmission on the SCell (if configured).

[0350] 3> Otherwise (i.e., firstActiveDownlinkBWP-Id is set to a dormant BWP):

[0351] 4> Stop the bwp-InactivityTimer for this serving cell if it is running.

[0352] 3> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, respectively.

[0353] 2> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined for MAC CE activation in TS 38.213 [6] and according to the timing defined for direct SCell activation in TS 38.133

[11] ;

[0354] 2> If the active DL BWP is not a dormant BWP:

[0355] 3> (Re)initialize any suspended configured uplink grants of configured grant type 1 associated with this SCell according to the stored configuration (if any), and start in the notation according to the rules in Section 5.8.2;

[0356] 3> Trigger a PHR according to Section 5.4.6.

[0357] 1> Otherwise, if an SCell activation / deactivation MAC CE or an enhanced SCell activation / deactivation MAC CE is received, deactivate the SCell; or

[0358] 1> If the sCellDeactivationTimer associated with the activated SCell expires: or

[0359] 1> If the SCG associated with the activated SCell is deactivated:

[0360] 2> Deactivate the SCell according to the timing defined in TS 38.213 [6];

[0361] 2> Stop the sCellDeactivationTimer associated with the SCell;

[0362] 2> Stop the bwp-InactivityTimer associated with the SCell;

[0363] 2> Deactivate any active BWP associated with the SCell;

[0364] 2> Clear any configured downlink assignment and any configured uplink grant type 2 associated with the SCell, respectively;

[0365] 2> Clear any PUSCH resources used for semi-persistent CSI reporting associated with the SCell;

[0366] 2> Suspend any configured uplink grant type 1 associated with the SCell;

[0367] 2> Clear all HARQ buffers associated with the SCell;

[0368] 2> If it exists, cancel the triggered consistent LBT failure of the SCell.

[0369] 1> If the PDCCH on the activated SCell indicates an uplink grant or a downlink assignment; or

[0370] 1> If the PDCCH on the serving cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or

[0371] 1> If the MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from the lower layer; or

[0372] 1> If the MAC PDU is received in a configured downlink assignment:

[0373] 2>Restart the sCellDeactivationTimer associated with the SCell.

[0374] 1>If the SCell is deactivated:

[0375] 2>Do not transmit SRS on the SCell;

[0376] 2>Do not report CSI for the SCell;

[0377] 2>Do not transmit on the UL-SCH on the SCell;

[0378] 2>Do not transmit on the RACH on the SCell;

[0379] 2>Do not monitor the PDCCH on the SCell;

[0380] 2>Do not monitor the PDCCH for the SCell;

[0381] 2>Do not transmit the PUCCH on the SCell.

[0382] The HARQ feedback of the MAC PDU containing the SCell activation / deactivation MAC CE or enhanced SCell activation / deactivation MAC CE should not be affected by the PCell, PSCell, and PUCCH SCell interruptions due to SCell activation / deactivation in TS 38.133

[11] .

[0383] When the SCell is deactivated, an ongoing random access procedure (if any) on the SCell is aborted.

[0384] In [8] 3GPP TS 38.213 h60, the following is provided.

[0385] 10.3 Indication for monitoring the SCell and PDCCH for sleep / non-sleep behavior

[0386] The following can be provided for a UE [11, TS 38.321] configured for DRX mode operation for detecting DCI format 2_6 [12, TS 38.331] in PDCCH reception on the PCell or SpCell

[0387] - The PS-RNTI of DCI format 2_6, denoted as ps-RNTI

[0388] - The number of search space sets, denoted as dci-Format2-6, for monitoring the PDCCH for detecting DCI format 2_6 on the active DL BWP of the PCell or SpCell according to the common search space as described in Section 10.1

[0389] - The payload size of DCI format 2_6, denoted as sizeDCI-2-6

[0390] - The position of the wake-up indication bit in DCI format 2_6, denoted as ps-PositionDCI-2-6

[0391] - When reported to the higher layer, a '0' value of the wake-up indication bit indicates not to start the drx-onDurationTimer of the next long DRX cycle [11, TS 38.321]

[0392] - When reported to the higher layer, a '1' value of the wake-up indication bit indicates to start the drx-onDurationTimer of the next long DRX cycle [11, TS 38.321]

[0393] - A bitmap when the UE is provided with multiple configured SCell groups, denoted as dormancyGroupOutsideActiveTime, where

[0394] - The bitmap position is immediately after the wake-up indication bit position

[0395] - The bitmap size is equal to the number of configured SCell groups, where each bit of the bitmap corresponds to one of the configured SCell groups among the multiple configured SCell groups

[0396] - A '0' value of a bit of the bitmap indicates the active DL BWP, which is provided by dormantBWP-Id for each activated SCell of the UE in the corresponding configured SCell group [11, TS 38.321]

[0397] - A '1' value of a bit of the bitmap indicates

[0398] - The active DL BWP, in the case where the current active DL BWP is a dormant DL BWP, which is provided by firstOutsideActiveTimeBWP-Id for each activated SCell of the UE in the corresponding configured SCell group

[0399] - The current active DL BWP, in the case where the current active DL BWP is not a dormant DL BWP, for each activated SCell of the UE in the corresponding configured SCell group

[0400] - The UE sets the active DL BWP to the indicated active DL BWP

[0401] - The time offset indicating the time is represented as ps-Offset, where the UE starts listening for PDCCH according to multiple search space sets to detect DCI format 2_6 before the slot in which the drx-onDurationTimer will start on the PCell or on the SpCell [11, TS 38.321]

[0402] - For each search space set, the PDCCH monitoring occasion is the slot among the first T s slots indicated by duration, or if duration is not provided, T s = 1 slot starting from the first slot among the first T s slots and ending before the drx-onDurationTimer starts.

[0403] If a search space set is provided to the UE to listen for PDCCH to detect DCI format 2_6 in the active DL BWP of the PCell or SpCell, and the UE detects DCI format 2_6, the physical layer of the UE reports the value of the wake-up indication bit used for the UE to the higher layer [11, TS 38.321] for the next long DRX cycle.

[0404] If a search space set is provided to the UE to listen for PDCCH to detect DCI format 2_6 in the active DL BWP of the PCell or SpCell, and the UE does not detect DCI format 2_6, the physical layer of the UE does not report the value of the wake-up indication bit to the higher layer for the next long DRX cycle.

[0405] If a search space set is provided to the UE to listen for PDCCH to detect DCI format 2_6 in the active DL BWP of the PCell or SpCell, and the UE

[0406] - For all corresponding PDCCH monitoring occasions outside the active time before the next long DRX cycle, there is no need to listen for PDCCH to detect DCI format 2_6, as described in Sections 10, 11.1, 12 and Section 5.7 of [11, TS 38.321]

[0407] - Outside the active time of the next long DRX cycle, there is no PDCCH monitoring occasion for detecting DCI format 2_6

[0408] The physical layer of the UE reports the value 1 of the wake-up indication bit to the higher layer for the next long DRX cycle.

[0409] If a search space set is provided to the UE to monitor the PDCCH for detecting DCI format 0_1 and DCI format 1_1, and if the DCI format 0_1 and / or DCI format 1_1 includes a SCell dormancy indication field, then

[0410] - The SCell dormancy indication field is a bitmap with a size equal to the number of configured SCell groups, provided by dormancyGroupWithinActiveTime

[0411] - Each bit of the bitmap corresponds to one of the configured SCell groups among the multiple configured SCell groups

[0412] - If the UE detects a DCI format 0_1 or DCI format 1_1 that does not include a carrier indicator field, or detects a DCI format 0_1 or DCI format 1_1 that includes a carrier indicator field with a value equal to 0, and if the DCI format 0_1 does not indicate a UL grant type 2 release nor deactivate semi-persistent CSI reporting on the PUSCH, or if the DCI format 1_1 does not indicate an SPS PDSCH release

[0413] - A '0' value of the bit of the bitmap indicates the active DL BWP, which is provided by dormantBWP-Id for the UE for each activated SCell in the corresponding configured SCell group

[0414] - A '1' value of the bit of the bitmap indicates

[0415] - The active DL BWP, in the case where the current active DL BWP is a dormant DL BWP, is provided by firstWithinActiveTimeBWP-Id for the UE for each activated SCell in the corresponding configured SCell group

[0416] - The current active DL BWP, in the case where the current active DL BWP is not a dormant DL BWP, for the UE for each activated SCell in the corresponding configured SCell group

[0417] - The UE sets the active DL BWP to the indicated active DL BWP

[0418] If the active DL BWP provided by dormantBWP-Id for the UE on the activated SCell is not the preset DL BWP for the UE on the activated SCell, as described in Section 12, then the BWP inactivity timer is not used to transition from the active DL BWP provided by dormantBWP-Id to the preset DL BWP on the activated SCell

[0419] In New Radio (NR) Rel-18, Coherent Joint Transmission (CJT) is introduced to improve spectral efficiency under the assumption of ideal synchronization and backhaul among multiple Transmission / Reception Points (TRPs). The number of multiple TRPs can be up to 4, and there are at most 2 (enhanced) unified Transmission Configuration Indicator (TCI) states. CJT can be a scheme where two TRPs use / utilize the same time-frequency resources through beams or source Reference Signals (RSs) associated with at most 2 unified TCI states. CJT can be regarded as a spatial domain multiplexing scheme. Based on the capabilities of the User Equipment (UE), the network node can configure one or two unified TCI states. Due to the characteristics of spatial multiplexing, time-frequency alignment among TRPs is required. That is, once the synchronization is not well aligned (or there is a delay between two TRPs due to non-ideal backhaul), the performance will degrade. Although Rel-18 applies the assumption of ideal synchronization for the simple design of CJT, the industry needs to deploy CJT in practical applications where non-ideal synchronization and non-ideal backhaul usually occur among TRPs. Preferably, in some embodiments, when the network vendor performs inter-site deployment for one or more TRPs that are more consistent with the real world, the communication between the UE and each of one or more different TRPs is usually associated with different Doppler offsets and time offsets. Preferably, in some embodiments, the non-ideal backhaul among TRPs can be considered together. The pre-compensation of time and / or frequency (and / or phase offset) among TRPs on the network node side may become outdated. Therefore, the performance of CJT will degrade, and a new design for UE-assisted CJT calibration will be required. Preferably, in some embodiments, with UE-assisted CJT calibration, the network node can perform pre-compensation to achieve time and / or frequency alignment (synchronization). Preferably, with UE-assisted CJT calibration, the CJT operation for the Physical Downlink Shared Channel (PDSCH) of the UE can be utilized to achieve better performance.

[0420] In NR Rel-19, since the UE is the first target to know the downlink (DL) channel conditions, event-triggered reporting is considered for beam reporting. In addition, event-triggered reporting requires new designs for NR Rel-19. Event-triggered reporting does not include receiving signals from network nodes to trigger the report. Preferably, in some embodiments, event-triggered reporting can be used for mobility or beam reporting (e.g., Layer 1 (L1)-Reference Signal Received Power (RSRP), L1-Signal-to-Interference-Plus-Noise Ratio (SINR), or L3-RSRP, determined using long-term averages) or CJT calibration reporting.

[0421] Preferably, in some embodiments, event-triggered reporting may require new designs for when to trigger such reporting. Preferably, in some embodiments, event-triggered reporting can be transmitted via Uplink Control Information (UCI) or Media Access Control (MAC) Control Element (CE). Preferably, in some embodiments, an example scenario is the deployment of a serving cell that includes a dormant Bandwidth Part (BWP) and a non-dormant BWP. Preferably, in some embodiments, when the UE is instructed to transition from a dormant BWP to a non-dormant BWP (e.g., when there is DL or uplink (UL) data arrival), due to the power-saving state of the UE when it is in the dormant BWP, the information for beam and / or time / frequency / phase synchronization may be insufficient or outdated. Without such information, for example, CJT-PDSCH deployed in the real world may have worse performance because time / frequency / phase synchronization is not accurately pre-compensated on the network side. For another example, in the absence of such information, Frequency Range 2 (FR2) deployment may be problematic because there are frequent beam changes in the FR2 scenario.

[0422] Throughout this disclosure, "event-triggered reporting", "UE-triggered reporting", "condition-triggered reporting", or "UE-initiated reporting" may be interchangeable.

[0423] Throughout this disclosure, a beam can be replaced by a "TCI state", a "reference signal", a "Quasi-Co-Location (QCL) assumption", or a "spatial filter".

[0424] Preferably, in some embodiments, the UE may perform measurement time offset / frequency offset / phase offset associated with CJT calibration based on one or more RSs / channels. Preferably, in some embodiments, the one or more RSs / channels include demodulation reference signals (DMRSs) associated with a physical downlink control channel (PDCCH) indicating a target change on the UE side.

[0425] The concept is to trigger one or more reports based on meeting one or more conditions. The one or more reports may include any one or any combination of CJT calibration reports, beam reports (UE-triggered / event-triggered). Preferably, in some embodiments, the one or more conditions correspond to a change in condition (e.g., a secondary cell (SCell) changing from deactivated to activated, from a dormant BWP to a non-dormant BWP, from a cell-specific inactive time (associated with a network energy saving (NES) mechanism) to a cell-specific active time, from an RRC inactive state to an RRC connected state, and / or better measurement results). Preferably, in some embodiments, the UE may transmit one or more reports in one resource and transmit a power headroom report (PHR) report in another resource. Preferably, in some embodiments, the one resource and the other resource are in different symbols (within the same TTI) or alternatively in different TTIs.

[0426] Preferably, in some embodiments, the UE receives first downlink control information (DCI) indicating entry into a dormant BWP of a serving cell. Preferably, in some embodiments, the UE changes the active DL BWP of the serving cell from a non-dormant BWP to a dormant BWP. Preferably, in some embodiments, the dormant BWP corresponds to the DL and / or UL BWP of the serving cell. Preferably, in some embodiments, when the active DL BWP corresponds to the dormant BWP, the UE assumes or treats the associated UL BWP as a dormant BWP. Preferably, in some embodiments, the active UL BWP paired with or associated with the dormant DL BWP is also a dormant BWP or corresponds to a dormant BWP. Preferably, in some embodiments, when the UE is in the dormant BWP of a serving cell (i.e., the BWP referred to in these sentences), the UE: stops the bwp-InactivityTimer of the serving cell, does not listen for the physical downlink control channel (PDCCH) on the BWP, does not listen for the PDCCH for the BWP, does not receive the downlink synchronization channel (DL-SynchronizationChannel, SCH) on the BWP, does not report channel state information (CSI) on the BWP, does not transmit the UL-SCH on the BWP, does not transmit the random access channel (Random Access Channel, RACH) on the BWP, does not transmit the physical uplink control channel (Physical Uplink Control Channel, PUCCH) on the BWP. Preferably, in some embodiments, the UE receives second DCI indicating exit from the dormant BWP of the serving cell. Preferably, in some embodiments, the UE is configured with one dormant BWP of the serving cell by RRC. Preferably, in some embodiments, the serving cell corresponds to a secondary cell (e.g., SCell). Preferably, in some embodiments, in response to the second DCI (or in response to the second DCI indicating exit from the dormant BWP), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, due to the second DCI indicating exit from the dormant BWP, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, in response to the trigger, the UE attempts to transmit one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with at least the serving cell (or one or more triggered (UE-initiated or event-triggered) reports include a report of at least the serving cell).Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with a (serving) cell group that includes the serving cell (e.g., a Master Cell Group (MCG) or a Secondary Cell Group (SCG)). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with all configured serving cell groups (one of all configured serving cell groups that includes the serving cell). Alternatively or additionally, one or more triggered (UE-initiated or event-triggered) reports are not associated with a (serving) cell group that does not include the serving cell (e.g., an MCG or an SCG). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are (triggered) for at least those serving cells in response to the UE changing the state from a dormant BWP to a non-dormant BWP (or for at least those serving cells in response to the UE receiving a second DCI for indicating a non-dormant BWP). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have reports associated with serving cells that are not affected, where the serving cells that are not affected do not have a state change from a dormant BWP to a non-dormant BWP. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have report information for serving cells associated with a dormant BWP (or associated with a non-dormant BWP that has not received a second DCI for indicating non-dormancy at this time). The serving cell may be configured with an uplink. Alternatively, in some embodiments, the serving cell may not be configured with an uplink. Preferably, in some embodiments, the serving cell may be configured with a DL BWP or a dormant DL BWP. Preferably, in some embodiments, the serving cell may correspond to DL-only operation. Preferably, in some embodiments, the serving cell may be configured with at least a DL BWP. Preferably, in some embodiments, the serving cell is not configured with a UL BWP. Preferably, in some embodiments, the serving cell is not configured with a Physical Uplink Shared Channel (PUSCH). Preferably, in some embodiments, the serving cell is not configured with a PUSCH or a Physical Uplink Control Channel (PUCCH) or a Sounding Reference Signal (SRS). Preferably, in some embodiments, the serving cell is not configured with UL resources for determining a type 1 PHR report. In one example, the relevant transmission direction for triggering one or more triggered (UE-initiated or event-triggered) reports is different from the transmission direction for triggering a PHR report.Alternatively, in some embodiments, the relevant transmission direction for triggering one or more triggered (UE-initiated or event-triggered) reports is the same as the transmission direction for triggering the PHR report.

[0427] Preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be the existence of configured downlink resources in the non-dormant BWP or the existence of configured downlink resources associated with the non-dormant BWP. Preferably, in some embodiments, when at least the UE is configured with configured downlink resources in the non-dormant BWP or configured downlink resources associated with the non-dormant BWP, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is not configured with configured downlink resources in the non-dormant BWP or configured downlink resources associated with the non-dormant BWP, the UE does not trigger one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the downlink resources correspond to control resource set (CORESET) configuration and / or PDSCH configuration, synchronization signal (SS) / physical broadcast channel (PBCH) reception. Preferably, in some embodiments, the downlink resources correspond to the configuration of the DL BWP and / or the initial DL BWP.

[0428] Alternatively and / or preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be whether there is a configured downlink (operation) in the non-dormant BWP or a configured downlink (operation) associated with the non-dormant BWP (or whether there is a configured downlink (operation) for the serving cell, or whether there is a configured downlink (operation) for the non-dormant BWP, or whether there is a configured downlink (operation) for the MAC entity associated with the serving cell). Preferably, in some embodiments, when at least the UE is configured with a downlink (operation) in the non-dormant BWP or a downlink (operation) associated with the non-dormant BWP (or when at least the UE is configured with a downlink (operation) for the serving cell, or when there is a configured downlink (operation) for the non-dormant BWP, or when there is a configured downlink (operation) for the MAC entity associated with the serving cell), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is not configured with a downlink (operation) in the non-dormant BWP or a downlink (operation) associated with the non-dormant BWP (or when at least the UE is not configured with a downlink (operation) for the serving cell, or when there is no configured downlink (operation) for the non-dormant BWP, or when there is no configured downlink (operation) for the MAC entity associated with the serving cell), the UE does not trigger one or more (UE-initiated or event-triggered) reports.

[0429] Alternatively and / or preferably, in some embodiments, regardless of whether the UE is configured with a downlink operation for the serving cell (or a downlink operation for the non-dormant BWP, or a downlink operation for the MAC entity associated with the serving cell), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the serving cell is configured in a MAC entity configured with a downlink (operation).

[0430] Preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports regarding a serving cell configured with a downlink (or configured with an uplink) (or configured with both a downlink and an uplink) may be applied or combined with any triggering reason mentioned throughout this disclosure.

[0431] Preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be whether there is a configured uplink resource in the non-dormant BWP or whether there is a configured uplink resource associated with the non-dormant BWP. Preferably, in some embodiments, when at least the UE is configured with a configured uplink resource in the non-dormant BWP or a configured uplink resource associated with the non-dormant BWP, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is not configured with a configured uplink resource in the non-dormant BWP or a configured uplink resource associated with the non-dormant BWP, the UE does not trigger one or more (UE-initiated or event-triggered) reports.

[0432] Alternatively and / or preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be whether there is a configured uplink (operation) in the non-dormant BWP or a configured uplink (operation) associated with the non-dormant BWP (or whether there is a configured uplink (operation) for the serving cell, or whether there is a configured uplink (operation) for the non-dormant BWP, or whether there is a configured uplink (operation) for the MAC entity associated with the serving cell). Preferably, in some embodiments, when at least the UE is configured with an uplink (operation) in the non-dormant BWP or an uplink (operation) associated with the non-dormant BWP (or when at least the UE is configured with an uplink (operation) for the serving cell, or when there is a configured uplink (operation) for the non-dormant BWP, or when there is a configured uplink (operation) for the MAC entity associated with the serving cell), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is not configured with an uplink (operation) in the non-dormant BWP or an uplink (operation) associated with the non-dormant BWP (or when at least the UE is not configured with an uplink (operation) for the serving cell, or when there is no configured uplink (operation) for the non-dormant BWP, or when there is no configured uplink (operation) for the MAC entity associated with the serving cell), the UE does not trigger one or more (UE-initiated or event-triggered) reports.

[0433] Alternatively and / or preferably, in some embodiments, regardless of whether the UE is configured for uplink operation of the serving cell (or configured for uplink operation of a non-dormant BWP, or configured for uplink operation of the MAC entity associated with the serving cell), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the serving cell is configured in the MAC entity configured for uplink (operation).

[0434] Preferably, in some embodiments, the UE is configured with at least one lower layer (L1 / L2) triggered mobility (LTM) candidate cell configuration. Preferably, in some embodiments, the UE may be configured with a set of TCI states associated with at least one LTM candidate cell. Preferably, in some embodiments, once the UE receives a signal for activating and / or indicating one TCI state (among a set of TCI states), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, such TCI state activation or TCI state indication for at least one LTM candidate cell corresponds to a trigger reason. Preferably, in some embodiments, the trigger reason may be associated with a candidate cell other than the (current) serving cell. Preferably, in some embodiments, one or more specific configurations (associated with UE-initiated or event-triggered reports) may be configured per LTM candidate cell. Preferably, in some embodiments, before the LTM candidate cell becomes the serving cell, the use or application of one or more specific configurations (associated with UE-initiated or event-triggered reports) associated with an LTM candidate cell is not allowed. Alternatively, in some embodiments, after the LTM candidate cell becomes the serving cell, the use or application of one or more specific configurations (associated with UE-initiated or event-triggered reports) associated with an LTM candidate cell may be used or applied. Preferably, in some embodiments, the use or application of a specific configuration (associated with UE-initiated or event-triggered reports) means or corresponds to the UE (being able to) trigger one or more reports based on one or more specific configurations. Preferably, in some embodiments, before the LTM candidate cell becomes the serving cell, the UE triggers one or more reports based on a first one or more trigger reasons (e.g., after receiving an activation for the LTM TCI state or an indication for the LTM TCI state). Preferably, in some embodiments, after the LTM candidate cell becomes the serving cell, the UE triggers one or more reports based on a second one or more trigger reasons (e.g., one or more specific configurations associated with UE-initiated or event-triggered reports).

[0435] Preferably, in some embodiments, the UE receives a signal for activating a SCell. Preferably, in some embodiments, in response to the signal (or in response to an indication of the signal), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, due to the signal for activating the secondary cell, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, in response to the trigger, the UE will attempt to transmit one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with at least the secondary cell (or one or more triggered (UE-initiated or event-triggered) reports include a report of at least the secondary cell). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with a (serving) cell group that includes the secondary cell (e.g., MCG or SCG). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with all configured serving cell groups (one of all configured serving cell groups that includes the secondary cell). Alternatively or additionally, one or more triggered (UE-initiated or event-triggered) reports are not associated with a (serving) cell group that does not include a serving cell (e.g., MCG or SCG). Preferably, in some embodiments, in response to at least those serving cells (including the secondary cell) for which the UE has received a signal for cell activation, one or more triggered (UE-initiated or event-triggered) reports are (triggered). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have a report associated with an unaffected serving cell that has not had a change in status or has not received a signal for cell activation. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have a report associated with a deactivated cell (or with an already activated cell that has not received a signal for cell activation at this time). The secondary cell may be configured with an uplink. Alternatively, in some embodiments, the secondary cell may not be configured with an uplink.

[0436] Preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be whether there is a configured uplink resource in the secondary cell or whether there is a configured uplink resource associated with the secondary cell. Preferably, in some embodiments, when at least the UE is configured with a configured uplink resource in the secondary cell or a configured uplink resource associated with the secondary cell, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is not configured with a configured uplink resource in the secondary cell or a configured uplink resource associated with the secondary cell, the UE does not trigger one or more (UE-initiated or event-triggered) reports.

[0437] Alternatively and / or preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be whether there is a configured uplink (operation) in the secondary cell or a configured uplink (operation) associated with the secondary cell (or whether there is a configured uplink (operation) for the secondary cell, or whether there is a configured uplink (operation) for the MAC entity associated with the secondary cell). Preferably, in some embodiments, when at least the UE is configured with an uplink (operation) in the secondary cell or an uplink (operation) associated with the secondary cell (or when at least the UE is configured with an uplink (operation) for the secondary cell, or when there is a configured uplink (operation) for the MAC entity associated with the secondary cell), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is not configured with an uplink (operation) in the secondary cell or an uplink (operation) associated with the secondary cell (or when at least the UE is not configured with an uplink (operation) for the secondary cell, or when there is no configured uplink (operation) for the MAC entity associated with the secondary cell), the UE does not trigger one or more (UE-initiated or event-triggered) reports.

[0438] Alternatively and / or preferably, in some embodiments, regardless of whether the UE is configured with an uplink operation for the secondary cell (or configured with an uplink operation for the MAC entity associated with the secondary cell), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the secondary cell is configured in a MAC entity configured with an uplink (operation).

[0439] Preferably, in some embodiments, the first active DL BWP of the secondary cell is not configured as a dormant BWP. Preferably, in some embodiments, one or more additional conditions for triggering one or more (UE-initiated or event-triggered) reports may be whether the first active DL BWP of the secondary cell is not configured as a dormant BWP. Preferably, in some embodiments, when the first active DL BWP of the secondary cell is configured as a dormant BWP, the UE does not trigger one or more (UE-initiated or event-triggered) reports (for at least the secondary cell). Preferably, in some embodiments, when at least the first active DL BWP of the secondary cell is configured as a non-dormant BWP, the UE triggers one or more (UE-initiated or event-triggered) reports (for at least the secondary cell). Preferably, in some embodiments, the "first active DL BWP" corresponds to the BWP in the secondary cell, and the BWP is associated with the firstActiveDownlinkBWP-Id.

[0440] Preferably, in some embodiments, simply put, when a signal for activating the secondary cell is received, if the first active DL BWP in the secondary cell or the first active DL BWP associated with the secondary cell or the first active DL BWP configured in the secondary cell is not a dormant BWP or does not correspond to a dormant BWP, the UE triggers one or more (UE-triggered or event-triggered) reports.

[0441] Preferably, in some embodiments, the UE receives a signal to activate the SCG. Preferably, in some embodiments, the UE may receive a signal in one serving cell in the (current) MCG. Preferably, in some embodiments, this situation change is from no cell change to a (new) added cell. Preferably, in some embodiments, the UE may not have an SCG configuration, or may not communicate with a serving cell in another cell group (CG) (except the current MCG). Preferably, in some embodiments, in response to the signal (or in response to an indication of the signal), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more (UE-initiated or event-triggered) reports at least include report information associated with a set of serving cells in the secondary cell group. Preferably, in some embodiments, for this trigger reason (e.g., after receiving the activation of the SCG), the UE triggers and reports all report information associated with the serving cells in the secondary cell group. Preferably, in some embodiments, for this trigger reason (e.g., after receiving the activation of the SCG), the UE triggers and reports one or more report information associated with the serving cells in the secondary cell group, where multiple serving cells correspond to the serving cells associated with or configured with the UE-initiated report. Alternatively, in some embodiments, the UE may determine whether to trigger and transmit a UE-initiated report associated with the serving cells in the SCG based on whether the SCG is configured with a UE-initiated report. Preferably, in some embodiments, in this scenario, the UE will trigger and transmit report information associated with all serving cells in the SCG (after receiving the signal or after an indication of the received signal). Preferably, in some embodiments, due to the signal for activating the SCG, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, in response to the trigger, the UE will attempt to transmit one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with at least the serving cells in the SCG (or one or more triggered (UE-initiated or event-triggered) reports include reports of at least the serving cells in the SCG). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with all configured serving cell groups including the SCG. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have reports associated with unaffected serving cells that have no situation change. Preferably, in some embodiments, in this instance, the UE triggers (and transmits) report information associated with the SCG (instead of the MCG), and / or the UE does not trigger (and transmit) report information associated with the MCG (due to this trigger reason).Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have a report associated with a deactivated cell (or associated with an activated cell that (at this time) has not received a cell activation signal). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports have or include report information associated with a deactivated cell. A secondary cell may be configured with an uplink. Alternatively, in some embodiments, a secondary cell may not be configured with an uplink.

[0442] Preferably, in some embodiments, the UE receives signals for adding or changing the primary SCG cell / primary secondary cell (PSCell) (in a secondary cell group (SCG)). Preferably, in some embodiments, the UE may receive signals in one serving cell in the (current) MCG. Preferably, in some embodiments, this situation change is from no cell change to an (new) added cell or from a first PSCell to a second PSCell. Preferably, in some embodiments, the UE may not have an SCG configuration or may not communicate with a serving cell in another cell group (except the current MCG). Preferably, in some embodiments, in response to a signal (or in response to an indication of a signal), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more (UE-initiated or event-triggered) reports at least include report information associated with a set of serving cells in the secondary cell group. Alternatively, in some embodiments, one or more (UE-initiated or event-triggered) reports at least include report information associated with a second PSCell in the secondary cell group. Alternatively, in some embodiments, one or more (UE-initiated or event-triggered) reports only include report information associated with a second PSCell in the secondary cell group. Preferably, in some embodiments, in this trigger reason (e.g., after receiving a signal for adding or changing the PSCell), the UE triggers and reports all report information associated with the serving cells in the secondary cell group. Preferably, in some embodiments, in this trigger reason (e.g., after receiving a signal for adding or changing the PSCell), the UE triggers and reports one or more report information associated with the serving cells (all serving cells or a subset of serving cells) in the secondary cell group, where the multiple serving cells (all serving cells or a subset of serving cells) correspond to the serving cells associated with or configured with UE-initiated reports. Preferably, in some embodiments, the subset of serving cells corresponds to the activated cells in the SCG. Preferably, in some embodiments, the UE does not trigger or transmit report information associated with deactivated cells or serving cells in a dormant BWP. Preferably, in some embodiments, in this instance, when the SCG is deactivated, the UE may not trigger UE-initiated reports (even if the UE receives a signal indicating an addition or change of the PSCell). Preferably, in some embodiments, throughout this disclosure, whether a serving cell is in a dormant BWP and / or whether a serving cell is not an activated cell may correspond to one or more additional trigger conditions for one or more triggered (UE-initiated or event-triggered) reports. For example, when a trigger reason is met, the UE may not trigger a triggered report for a serving cell in a dormant BWP or not activated.Alternatively, in some embodiments, the UE may determine whether to trigger and transmit a UE-initiated report associated with a serving cell in the SCG based on whether the SCG is configured with UE-initiated reporting. Preferably and / or alternatively, in some embodiments, the UE may determine whether to trigger and transmit a UE-initiated report associated with the PSCell based on whether the PSCell is configured with UE-initiated reporting. Preferably, in some embodiments, in this scenario, the UE will trigger and transmit report information associated with all serving cells in the SCG (after receiving a signal or after indicating the received signal). Preferably, in some embodiments, due to the addition or change of the signal of the PSCell, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, in response to the trigger, the UE will attempt to transmit one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with at least (or only) the PSCell in the SCG (or one or more triggered (UE-initiated or event-triggered) reports include a report of at least the PSCell in the SCG). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with all serving cells including the PSCell in the SCG (or one or more triggered (UE-initiated or event-triggered) reports include a report of at least the PSCell in the SCG). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with all configured serving cell groups. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have reports associated with unaffected serving cells that have no change in status. Preferably, in some embodiments, in this instance, the UE triggers (and transmits) report information associated with the SCG (rather than the MCG), and / or the UE does not trigger (and transmit) report information associated with the MCG (due to this trigger reason). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have reports associated with deactivated cells (or associated with activated cells that have not received a cell activation signal at this time). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports have or include report information associated with deactivated cells. The PSCell may be configured with an uplink. Alternatively, in some embodiments, the PSCell may not be configured with an uplink.

[0443] Preferably, in some embodiments, the UE receives a signal to switch or change the cell group (currently in use). Preferably, in some embodiments, the indication of the signal may be to change the first MCG to the second MCG, change the first SCG (if there is a currently used SCG) to the second SCG, or a secondary SCG. Preferably, in some embodiments, the UE may receive the signal in one serving cell in the (current) master cell group (MCG). Preferably, in some embodiments, in response to the signal (or in response to the indication of the signal), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the one or more (UE-initiated or event-triggered) reports at least include report information associated with a set of serving cells in the newly changed cell group. Preferably, in some embodiments, for this triggering reason (e.g., after receiving a modification or change to the current CG), the UE triggers and reports all report information associated with the serving cells in the new cell group. Preferably, in some embodiments, for this triggering reason (e.g., after receiving a modification or change to the current CG), the UE triggers and reports one or more report information associated with the serving cells in the new cell group, where the multiple serving cells correspond to the serving cells associated with or configured with the UE-initiated report. Alternatively, in some embodiments, the UE may determine whether to trigger and transmit the UE-initiated report associated with the serving cells in the new CG based on whether the new CG is configured with the UE-initiated report. Preferably, in some embodiments, in this scenario, the UE will trigger and transmit the report information associated with all serving cells in the new CG (after receiving the signal or after the indication of the received signal). Preferably, in some embodiments, due to the signal for changing or modifying the CG, the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, in response to the trigger, the UE will attempt to transmit one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the one or more triggered (UE-initiated or event-triggered) reports are associated with at least the serving cells in the new CG (or the one or more triggered (UE-initiated or event-triggered) reports include at least the reports of the serving cells in the new CG). Alternatively, in some embodiments, the one or more triggered (UE-initiated or event-triggered) reports are associated with all configured serving cell groups (including one of all configured serving cell groups in the new CG). Preferably, in some embodiments, the one or more triggered (UE-initiated or event-triggered) reports do not include the report information associated with the replaced or old CG. Preferably, in some embodiments, the one or more triggered (UE-initiated or event-triggered) reports do not have reports associated with the unaffected serving cells that have not changed in status.Preferably, in some embodiments, in this instance, the UE triggers (and transmits) report information associated with the SCG (instead of the MCG), and / or the UE does not trigger (and transmit) report information associated with the MCG (due to this triggering reason). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not have a report associated with a deactivated cell (or associated with an activated cell that has not received cell activation (at this time)). Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports have or include report information associated with a deactivated cell. The secondary cell may be configured with an uplink. Alternatively, in some embodiments, the secondary cell may not be configured with an uplink.

[0444] Preferably, in some embodiments, the UE may apply different processing to add a CG (or replace the entire CG) or modify one or more serving cells in the current CG. Preferably, in some embodiments, when the UE receives a signal indicating the addition or replacement of the entire CG, one or more triggered reports include report information associated with all serving cells in the new (added) CG. Preferably, in some embodiments, in this scenario (but not limited to this scenario), even if the first serving cell in at least the new (added) CG is deactivated or in a dormant BWP, one or more triggered reports include report information associated with the first serving cell. Alternatively, in some embodiments, the UE (still does not) trigger (and transmit) report information associated with the first serving cell.

[0445] Preferably, in some embodiments, when the UE receives a signal indicating the modification of one or more serving cells (including replacing the second serving cell with the third serving cell and adding the fourth serving cell), one or more triggered reports include report information associated only with or solely with the third serving cell or the fourth serving cell. Preferably, in some embodiments, in this scenario (but not limited to this scenario), even if at least the third serving cell or the fourth serving cell is deactivated or in a dormant BWP, one or more triggered reports include report information associated with the third serving cell or the fourth serving cell. Alternatively, in some embodiments, the UE (still does not) trigger (and transmit) report information associated with the second serving cell.

[0446] Alternatively, in some embodiments, regardless of whether a CG is added (or replaced in its entirety) or one or more serving cells in the current CG are modified, the UE applies the same processing for UE-initiated or event-triggered reports.

[0447] Preferably, in some embodiments, one trigger reason may be configured for each CG.

[0448] Preferably, in some embodiments, a CG may be configured with or assigned one or more triggering reasons.

[0449] Preferably, in some embodiments, different CGs correspond to independent sets of triggering reasons (which may include one or more triggering reasons).

[0450] Preferably, in some embodiments, based on the configured triggering reasons for each CG, the UE may determine whether to trigger one or more reports for the corresponding CG.

[0451] Preferably, in some embodiments, throughout the present disclosure, one or more triggered (UE-initiated or event-triggered) reports include report information associated with new targets (e.g., serving cell, (serving) cell group).

[0452] Preferably, in some embodiments, throughout the present disclosure, one or more triggered (UE-initiated or event-triggered) reports include report information associated with new targets (e.g., serving cell, (serving) cell group) and old targets.

[0453] Preferably, in some embodiments, based on the triggering reason being configured or specified according to a specific configuration (associated with UE-initiated or event-triggered reporting), the UE determines whether to include reporting information associated with both a candidate target (e.g., candidate RS, TCI state) and the currently used / indicated target (e.g., used / indicated TCI state or RS). Preferably, in some embodiments, for a triggering reason caused by a specific configuration, the UE includes reporting information associated with both the candidate target and the currently used / indicated target. Alternatively, in some embodiments, for a triggering reason attributed to a specific configuration, the UE includes reporting information associated with the candidate target. Preferably, in some embodiments, for a specified triggering reason, the UE includes reporting information associated with both the candidate target and the currently used / indicated target. Alternatively, in some embodiments, for a specified triggering reason, the UE includes reporting information associated with the candidate target. Preferably, in some embodiments, whether to include reporting information associated with both the candidate target and the used / indicated target is based on the configuration of the network node. Preferably, in some embodiments, the configuration of the network node provided to the UE can be a bit indicating whether to include reporting information associated with both the candidate target and the used / indicated target. Preferably, in some embodiments, the configuration of the network node provided to the UE can be a range of one or more RSRP levels or SINR levels. Preferably, in some embodiments, within a certain range of RSRP level or SINR level, if the gain between the candidate target and the used target is not significant, the UE can report the gain to the network node. Preferably, in some embodiments, the network node has the final decision-making ability to decide whether to instruct the UE to change the indicated beam. Alternatively, in some embodiments, the UE can set whether to include reporting information associated with the used / indicated target.

[0454] Preferably, in some embodiments, different uses of UE-initiated or event-triggered reporting can have different reporting formats. Preferably, in some embodiments, a first use (e.g., CJT calibration report) can correspond to a first reporting format. Preferably, in some embodiments, the first format can include reporting information associated with the used / indicated target and the candidate target. Preferably, in some embodiments, a second use (e.g., beam reporting) can correspond to a second reporting format. Preferably, in some embodiments, the second format can include (only) reporting information associated with the candidate target.

[0455] Throughout this disclosure, reporting information associated with a target means or corresponds to or can include measurement results associated with (or based on) a target, information of a target (e.g., ID of a target), and / or information associated with triggering or reporting configuration.

[0456] Preferably, in some embodiments, the UE receives a message that configures or reconfigures a specific configuration (associated with UE-initiated or event-triggered reporting). Preferably, in some embodiments, the received message will have a condition change that is a configuration or reconfiguration of a specific configuration (associated with UE-initiated or event-triggered reporting). Preferably, in some embodiments, the condition change means that the UE changes from a first specific configuration (if initially used) to a second specific configuration based on or due to receiving the message. Preferably, in some embodiments, in order to trigger one or more reports due to or in response to receiving the message, the condition change does not include or exclude the case where the message removes the first specific configuration without replacing it with a second specific configuration (or the message deactivates the functionality of the first specific configuration without configuring a replacement second specific configuration). Preferably, in some embodiments, in response to the message at least not deactivating the functionality of UE-initiated or event-triggered reporting, the UE triggers one or more reports. Preferably, in some embodiments, once the message will at least deactivate the functionality of UE-initiated or event-triggered reporting, the UE does not trigger one or more reports. Preferably, in some embodiments, the message is per UE (e.g., all serving cells share the same message). Preferably, in some embodiments, the message may include information regarding which set of serving cells has the specific configuration in the message or is associated or related to the specific configuration in the message. Preferably, in some embodiments, the message is per cell group (e.g., the serving cells in the MCG and the serving cells in the SCG correspond to different messages). Preferably, in some embodiments, the message for each CG may have or provide or indicate a set of independent serving cells in the corresponding cell group that have the specific configuration in the message or are associated or related to the specific configuration in the message. Preferably, in some embodiments, the message may be per serving cell. Preferably, in some embodiments, based on whether the message enables or indicates or configures or reconfigures the functionality of UE-initiated or event-triggered reporting or a specific configuration (associated with UE-initiated or event-triggered reporting), the UE may determine whether to trigger one or more reports and / or attempt to transmit one or more reports. Preferably, in some embodiments, once the message will deactivate the functionality of UE-initiated or event-triggered reporting, the UE does not trigger one or more reports. Preferably, in some embodiments, in response to the message (or in response to a message that configures or reconfigures a specific configuration), the UE triggers one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, in response to the trigger, the UE will attempt to transmit one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the message is associated with or used to configure UE-initiated or event-triggered reporting associated with the serving cell.Preferably, in some embodiments, the message is used to configure the UE-initiated or event-triggered report to include or comprise the serving cell. Preferably, in some embodiments, the UE receives the message and servingcellconfig or servingcellconfigcommon. Preferably, in some embodiments, the UE receives a message that is one of servingcellconfig or servingcellconfigcommon or belongs to or is included in servingcellconfig or servingcellconfigcommon. Preferably, in some embodiments, the UE receives a message associated with one of the CSI report configurations (for UE-initiated or event-triggered reports). Preferably, in some embodiments, the UE receives a message associated with a measurement configuration that is associated with UE-initiated or event-triggered reports. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with at least the serving cell (or one or more triggered (UE-initiated or event-triggered) reports include a report of at least the serving cell). Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with a cell group (e.g., MCG or SCG) that includes the serving cell. Alternatively, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports are associated with all configured serving cell groups that include the serving cell. Preferably, in some embodiments, in response to at least those serving cells (including the serving cell) for which the UE has received the message or the message contains or comprises a specific configuration (associated with UE-initiated or event-triggered reports), one or more triggered (UE-initiated or event-triggered) reports are triggered. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not (or do not include or comprise) reports associated with serving cells that are not affected, where the serving cells that are not affected have not had a change in status or have not received a message for configuring or reconfiguring a specific configuration. Preferably, in some embodiments, one or more triggered (UE-initiated or event-triggered) reports do not (or do not include or comprise) reports associated with serving cells that are not affected, where the serving cells that are not affected do not contain or comprise a message with a specific configuration or are not indicated by a message with a specific configuration. Preferably, in some embodiments, in some instances, the UE communicates with a first serving cell and a second serving cell.Preferably, in some embodiments, the three possible scenarios can be: both the first serving cell and the second serving cell are configured with a specific configuration; the first serving cell is configured with a specific configuration while the second serving cell is not configured with a specific configuration; or neither the first serving cell nor the second serving cell is configured with a specific configuration. Preferably, in some embodiments, in this instance, the first serving cell is configured with a specific configuration while the second serving cell is not configured with a specific configuration. Once the UE receives a message that configures or reconfigures the second serving cell with the specific configuration, the UE triggers one or more (UE-initiated or event-triggered) reports associated with at least the second serving cell and / or attempts to transmit one or more reports. Preferably, in some embodiments, for a similar instance, when the UE receives a second message that reconfigures the specific configuration associated with the first serving cell (e.g., adjusts / adds / removes one or more parameters or configurations or information elements in the previous configuration), the UE triggers one or more (UE-initiated or event-triggered) reports associated with at least the second serving cell and / or attempts to transmit one or more reports. Preferably, in some embodiments, it should be noted that when the message indicates the removal or adjustment of one or more parameters of the configuration or information element in the previous configuration, the UE triggers one or more reports at least when the message is stationary (in response to or due to the message), or maintains the functionality of the UE-initiated or event-triggered reports (regardless of whether the message is for each UE, each CG, or each serving cell). Preferably, in some embodiments, for another / other instance, the message or another type of message (in addition to the message) may include where one or more serving cells have or are configured with UE-initiated or event-triggered reports. Preferably, in some embodiments, when / once the UE receives a message that includes a different set of one or more serving cells that have or are configured with UE-initiated or event-triggered reports, the UE triggers one or more reports and / or attempts to transmit one or more reports. Preferably, in some embodiments, the UE triggers one or more reports only when receiving the configuration or reconfiguration of the specific configuration (associated with the UE-initiated report). Preferably, in some embodiments, other criteria can be that when a third serving cell carries or has a specific configuration and the UE detects that an event (associated with the third serving cell) meets the triggering condition, one or more reports are triggered. Preferably, in some embodiments, when the UE triggers one or more reports, the one or more reports include reports associated with at least the affected serving cells. Preferably, in some embodiments, none of the one or more triggered (UE-initiated or event-triggered) reports are associated with a cell that does not have or has not received a message for configuring or reconfiguring the specific configuration (associated with the UE-initiated or event-triggered report).

[0457] For example, each event trigger or trigger specified above corresponds to each of one or more reports. Preferably, in some embodiments, in response to receiving a configuration or reconfiguration message for a specific configuration (associated with a UE-initiated or event-triggered report) for a first serving cell or associated with a first serving cell, the first one or more reports may be triggered. Preferably, in some embodiments, in response to an (configured / specified) event or condition being satisfied for a second serving cell or associated with a second serving cell, the second one or more reports may be triggered. Preferably, in some embodiments, the (configured / specified) event or condition may be that the measurement result of the RS set is lower than a threshold. Preferably, in some embodiments, the measurement result may be applied with a long-term average (e.g., an L3 filter) or not applied with a long-term average. Preferably, in some embodiments, the (configured / specified) event or condition is associated with a specific configuration associated with the second serving cell.

[0458] Preferably, in some embodiments, a change in condition for triggering one or more (UE-initiated or event-triggered) reports may include an event or trigger reason when the UE changes from small data transmission (SDT) to non-SDT. More specifically, when the UE switches from a (Radio Resource Control (RRC)) inactive state to an (RRC) connected state, the UE will trigger one or more reports. Preferably, in some embodiments, in response to receiving a message indicating a change from SDT to non-SDT, the UE will trigger one or more reports. Preferably, in some embodiments, the UE will use CG SDT resources including one or more reports to a network node.

[0459] Preferably, in some embodiments, a change in condition for triggering one or more (UE-initiated or event-triggered) reports may include an event or trigger reason for the UE to receive an RRC resume message (or a message associated with or indicating RRC resume). More specifically, when the UE enters the RRC connected state (due to the RRC resume message) or the UE receives a message associated with or indicating RRC resume, the UE will trigger one or more reports.

[0460] Preferably, in some embodiments, throughout this disclosure, a state change may be interchanged with a change in condition.

[0461] Preferably, in some embodiments, the UE will not trigger one or more reports due to a change in condition between the NES active time and the NES inactive time.

[0462] Preferably, in some embodiments, the UE does not trigger one or more reports due to a change in the condition from beam failure trigger to beam failure report.

[0463] Preferably, in some embodiments, the UE does not trigger one or more reports due to one or more specific state changes.

[0464] Preferably, in some embodiments, since one or more triggered (UE-initiated or event-triggered) reports are associated with or measured for DL channel quality (e.g., UE-initiated CJT calibration report or UE-initiated beam report), one or more triggered (UE-initiated or event-triggered) reports include report information of a serving cell having DL operations.

[0465] Preferably, in some embodiments, in response to one or more triggered (UE-initiated or event-triggered) reports, when there is no UL resource (available for transmission) covering one or more reports, the UE will trigger an SR (associated with one or more UE-initiated or event-triggered reports). Preferably, in some embodiments, the UE will trigger any (permitted) SR for requesting a UL resource for transmitting one or more reports. Preferably, in some embodiments, the UL resource should be used for a new transport block (TB) or MAC protocol data unit (PDU) UL transmission. Alternatively, in some embodiments, the UE may not trigger an SR in response to one or more triggered reports.

[0466] Preferably, in some embodiments, the UE may be configured with an SR for one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the SR configuration for one or more reports is not configured with or not associated with a physical random access channel (PRACH). Preferably, in some embodiments, when the UE cancels the SR triggered by one or more triggered reports, due to the cancelled SR, the UE does not transmit or has not transmitted a PRACH (or initiate / trigger a RACH procedure). Preferably, in some embodiments, an intermediate group solution is to have a configuration for controlling or configuring whether the UE is to transmit a PRACH (or initiate / trigger a RACH procedure).

[0467] Preferably, in some embodiments, the UE avoids or does not trigger UE-initiated reports for a serving cell that is in a dormant BWP or is not an active serving cell.

[0468] Preferably, in some embodiments, the triggering reason may be applied (by the UE) to a serving cell that is not in a dormant BWP or is a serving cell of a serving cell, or associated with a serving cell that is not in a dormant BWP or is a serving cell of a serving cell.

[0469] Preferably, in some embodiments, when the serving cell is in a dormant BWP or is not an active serving cell, the triggering reason will not apply to the serving cell.

[0470] Preferably, in some embodiments, even if the UE triggers (and transmits) a report associated with multiple serving cells (e.g., each CG trigger / transmission), the report information is not associated with a serving cell that is in a dormant BWP or is not an active cell.

[0471] Preferably, in some embodiments, regardless of whether the multiple serving cells include a serving cell that is in a dormant BWP or is not an active cell, once the UE triggers a report associated with multiple serving cells (e.g., each CG trigger / transmission), the report information may be associated with the serving cells (e.g., all serving cells among the multiple serving cells).

[0472] Preferably, in some embodiments, different trigger cause (UE-initiated or event-triggered) reports are restricted or confined to multiplexing in one occasion or one PUCCH / PUSCH / UL resource. Preferably, in some embodiments, the UE shall transmit the first one or more reports on a first PUCCH / PUSCH / UL resource. Preferably, the UE shall transmit the second one or more reports on a second PUCCH / PUSCH / UL resource. Preferably, in some embodiments, the second PUCCH / PUSCH / UL resource and the first PUCCH / PUSCH / UL resource are in different time slots or different TTIs or different subframes or different sub-time slots or different symbols (even in the same time slot). Preferably, in some embodiments, the first PUCCH / PUSCH / UL resource is a scheduled / configured resource. Preferably, in some embodiments, the second PUCCH / PUSCH / UL resource is a scheduled / configured resource. Preferably, in some embodiments, the first PUCCH / PUSCH / UL resource is associated with or in a first serving cell. Preferably, in some embodiments, the second PUCCH / PUSCH / UL resource is associated with or in a second serving cell. Preferably, in some embodiments, the UE determines which cell includes the PUCCH / PUSCH / UL resource to include one or more resources based on which serving cell the one or more reports are associated with or which serving cell the trigger cause is associated with. In this instance, for the first one or more reports associated with the first serving cell (or since the first one or more reports are triggered for or associated with the first serving cell), the UE transmits the first one or more reports on the first PUCCH / PUSCH / UL resource on the first serving cell. In a similar instance, for the second one or more reports associated with the second serving cell, or since the second one or more reports are triggered for or associated with the second serving cell, the UE transmits the second one or more reports on the second PUCCH / PUSCH / UL resource on the second serving cell. Preferably, in some embodiments, in one instance, the first serving cell is the same as the second serving cell. Preferably, in some embodiments, in some instances, a specific configuration may indicate or configure one or more PUCCH / PUSCH / UL resources on a serving cell (e.g., the first serving cell or the second serving cell). Preferably, in some embodiments, based on which specific configuration the trigger cause is attributed to or associated with, the UE applies or uses the indicated / configured one or more PUCCH / PUSCH / UL resources on the serving cell. Preferably, in some embodiments, in some instances, different trigger causes may have the same priority for multiplexing in one UL resource.Preferably, in some embodiments, in another / other instances, different triggering reasons may have different priorities for multiplexing in a UL resource. Preferably, in some embodiments, based on a specific configured ID or the ID of a serving cell associated with a specific configuration or the measurement RS of a serving cell associated with a specific configuration or different triggering reasons, the priority of one or more reports attributable to different triggering reasons may be determined. In one instance, for example, a triggering reason such as a condition change may have a higher priority than a satisfied condition / event (e.g., the measurement result is lower than a threshold, or the number of events where the measurement result is lower than the threshold exceeds a number threshold). Alternatively, in some embodiments, a triggering reason such as a condition change may have a lower priority than a satisfied condition / event (e.g., the measurement result is lower than a threshold, or the number of events where the measurement result is lower than the threshold exceeds a number threshold). Preferably, in some embodiments, whenever or if a UL resource can cover a first one or more reports and a second one or more reports attributable to different triggering reasons, the UE may multiplex both the first one or more reports and the second one or more reports. Preferably, in some embodiments, whenever or if a UL resource cannot cover a first one or more reports and a second one or more reports attributable to different triggering reasons, the UE may preferentially multiplex the higher-priority reports. Preferably, in some embodiments, the triggering timing may be another criterion for determining the priority. Preferably, in some embodiments, in one instance, an earlier trigger may have a higher priority than a later trigger. Alternatively, in some embodiments, a later trigger may have a higher priority than an earlier trigger. Preferably, in some embodiments, the first serving cell is different from the second serving cell. Preferably, in some embodiments, in the time domain, the first PUCCH / PUSCH / UL resource does not overlap with the second PUCCH / PUSCH / UL resource. Alternatively, in some embodiments, in the time domain, the first PUCCH / PUSCH / UL resource may at least partially overlap with the second PUCCH / PUSCH / UL resource. Alternatively, in some embodiments, different triggering reason (UE-initiated or event-triggered) reports may be multiplexed in one timing or one PUCCH / PUSCH / UL resource. Preferably, in some embodiments, for a given serving cell, the UE does not expect or does not trigger or is restricted from triggering more than one report attributable to the same triggering reason (until the UE cancels a previous trigger or until a timer expires or before a timing). Preferably, in some embodiments, for example, when the UE triggers a report attributable to a specific configuration associated with a first serving cell, the UE does not expect or does not trigger or is restricted from triggering another report (attributable to the same specific configuration) (until the UE cancels a previous trigger or until a timer expires or before a timing).Preferably, in some embodiments, for a given serving cell, the UE does not expect or does not trigger or is restricted from triggering more than one report attributable to different triggering reasons. Preferably, in some embodiments, for example, when the UE triggers a report attributable to a change in the condition associated with the first serving cell, the UE does not expect or does not trigger or is restricted from triggering another report (attributable to a specific configuration associated with the first serving cell) (until the UE cancels the previous trigger or until the timer expires or before the occasion). Preferably, in some embodiments, based on whether the timer or occasion is per triggering reason or per serving cell, the UE can determine whether it is allowed to trigger another later report (attributable to the same or another specific configuration).

[0473] Additionally and / or alternatively, in some embodiments, the UE may (only) transmit one (single) (set) of one or more reports to indicate information (conditions) up to and including the last event / condition that triggered the report before combining or transmitting the one or more reports. For example, one (set of one or more) report(s) may be included in the MAC PDU.

[0474] Preferably, in some embodiments, once or whenever the UE triggers one or more reports, the UE starts a timer or determines a timing. Preferably, in some embodiments, the timer or the timing is used to control or determine whether to cancel the trigger. Preferably, in some embodiments, the trigger or the timer or the timing is any one or any combination thereof for each specific configuration, each serving cell, each serving cell group, or each trigger reason (associated with UE-initiated or event-triggered reports). Preferably, in some embodiments, before the timer expires or the timing, due to the different granularities of UE-initiated or event-triggered reports, the UE is restricted from triggering another report. In one example, if the timer or the timing is for each trigger reason, the UE can trigger for different trigger reasons at different timings for the same serving cell (before the timing and / or the timer expires). In another example, if the timer or the timing is for each serving cell, the UE is restricted from triggering another report for different trigger reasons at different timings for the same serving cell (before the timing and / or the timer expires). Preferably, in some embodiments, the timing and / or the timer corresponds to the latency requirement associated with the trigger reason or the UE-initiated or event-triggered report. Preferably, in some embodiments, each / a specific configuration (associated with the UE-initiated or event-triggered report) can include or configure its respective latency requirement. Preferably, in some embodiments, based on the UE's location (far from or near the network node), the UE can apply different specific configurations associated with the same serving cell. Preferably, in some embodiments, different specific configurations (associated with the same serving cell) can have different trigger reasons or different triggered events. In one example, the first specific configuration can be configured with a first number as the condition for triggering the UE-initiated or event-triggered report, while the second specific configuration can be configured with a second number as the condition for triggering the UE-initiated or event-triggered report. Preferably, in some embodiments, more than one specific configuration associated with the same serving cell can have different trigger reasons or different triggered events. Preferably, in some embodiments, different specific configurations (associated with the UE-initiated or event-triggered report) can have the same (or be restricted to be configured with the same) latency requirement.

[0475] Preferably, in some embodiments, when the UE transmits the triggered report, the UE resets the timer or stops the timer. For example, when the UE transmits the first one or more triggered reports, the UE stops or resets the timer associated with the first one or more triggered reports.

[0476] Preferably, to avoid frequent triggering, the UE may be configured with a prohibition timer associated with UE-initiated or event-triggered reporting. Preferably, in some embodiments, the granularity of the prohibition timer may be for each UE or for each serving cell or for each serving cell group or for each specific configuration (associated with UE-initiated or event-triggered reporting) or for each triggering reason or any combination thereof. Preferably, in some embodiments, whenever or in response to the UE transmitting a UE-initiated or event-triggered report, the UE starts the prohibition timer. Preferably, in some embodiments, one criterion that needs to be met to trigger one or more (UE-initiated or event-triggered) reports is based on the expiration of the prohibition timer. Preferably, in some embodiments, in other words, once the conditions for the first triggering reason (associated with a specific configuration) are met, the UE will not trigger a report because the corresponding prohibition timer has not expired. Preferably, in some embodiments, if the prohibition timer is configured or exists or is applied, the UE may trigger a (UE-initiated or event-triggered) report at least when the prohibition timer expires or is not running. Preferably, in some embodiments, (only) when the prohibition timer expires or has expired, the UE may trigger one or more reports (e.g., periodic reports). Preferably, in some embodiments, the prohibition timer (associated with UE-initiated or event-triggered reporting) may be a triggering reason for one or more reports. For example, the UE may trigger a (periodic) report in response to the expiration of the prohibition timer. Alternatively, in some embodiments, the UE may trigger a (periodic) report in response to the expiration of a periodic timer (different from the prohibition timer). Preferably, in some embodiments, power back-off due to power management (e.g., Power management Maximum Power Reduction, P-MPR c )) may be a triggering reason for one or more (UE-initiated or event-triggered) reports.

[0477] Preferably, in some embodiments, better measurement results can be replaced with: (i) a quantity attributable to the indicated beam or TCI state or the measurement results associated therewith is worse than a quantity attributable to a candidate beam or candidate TCI state or the measurement results associated therewith (e.g., the measurement results or quality of a candidate beam or candidate TCI state is better than a threshold (or better than an offset) of the measurement results or quality of the indicated beam or TCI state); or (ii) a quantity attributable to the indicated beam or TCI state or the measurement results associated therewith is worse than a quantity threshold (e.g., the measurement results or quality of the indicated beam or TCI state is worse than a threshold (or worse than an offset)); or (iii) a quantity attributable to a candidate beam or candidate TCI state or the measurement results associated therewith is better than a second quantity threshold; or (iv) a quantity attributable to the indicated beam or TCI state or the measurement results associated therewith is worse than a quantity threshold, and a quantity attributable to a candidate beam or candidate TCI state or the measurement results associated therewith is better than a second quantity threshold. Preferably, in some embodiments, for a first serving cell that satisfies the above (i) or (ii) or (iii) or (iv), one or more triggered reports include one or more candidate beam related information associated with the first serving cell. Preferably, in some embodiments, for a second serving cell that does not satisfy the above (i) or (ii) or (iii) or (iv), one or more triggered reports do not include one or more candidate beam related information associated with the second serving cell. Preferably, in some embodiments, the first serving cell and the second serving cell both utilize the same serving cell group configuration or are associated with the same serving cell group. Preferably, in some embodiments, the measurement results can correspond to long-term average measurement results. Preferably, in some embodiments, long-term can mean that there are more than one measurement results associated with more than one measurement opportunity.

[0478] Throughout this disclosure, the trigger cause report (UE-initiated or event-triggered) can correspond to any of the above triggers.

[0479] Throughout this disclosure, different trigger cause reports (UE-initiated or event-triggered) can correspond to any of the above triggers and / or correspond to different events / conditions or different specific configurations (associated with UE-initiated or event-triggered reports).

[0480] Throughout this disclosure, the trigger cause can correspond to an event / condition or the trigger situation specified above (e.g., a change in condition).

[0481] Throughout this disclosure, "change in state" can be interchanged with "state transition".

[0482] Preferably, in some embodiments, the number of one or more triggered (UE-initiated or event-triggered) reports is determined based at least on which of those serving cells or those serving cells are configured for UE-initiated or event-triggered reporting.

[0483] Preferably, in some embodiments, the UE may be configured with a maximum number of triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, when the UE is configured with L serving cells having one or more triggered (UE-initiated or event-triggered) reports, the number of one or more triggered reports includes report information associated with at most L serving cells. Preferably, in some embodiments, each of the L serving cells may be configured with one or more specific configurations or events or trigger reasons. Preferably, in some embodiments, the number of specific configurations may be configured independently for each of the L serving cells. Preferably, in some embodiments, the number of specific configurations may be configured or shared among the L serving cells (e.g., the number of specific configurations is the same among the L serving cells). Preferably, in some embodiments, each of the L serving cells may be assigned one or more trigger reasons. Preferably, in some embodiments, based on the number of the specified or configured number of trigger reasons, one or each of the L serving cells corresponds to at most M trigger report information.

[0484] Preferably, in some embodiments, the UE has the ability to maintain or control to trigger (and not cancel) a certain number of one or more triggered (UE-initiated or event-triggered) reports. Preferably, in some embodiments, the UE has the ability to maintain or control to maintain a certain number of one or more triggered reports among the serving cells configured with a specific configuration or among the serving cells associated with the UE-initiated or event-triggered reports or among all serving cells. Preferably, in some embodiments, the UE has a (second) ability to maintain or control to maintain a certain number of one or more triggered reports for each serving cell or for each serving cell associated with the UE-initiated or event-triggered reports. Preferably, in some embodiments, the UE has the ability to maintain or control to maintain a certain number of one or more triggered reports. Preferably, in some embodiments, once the UE has a first number of triggered reports (which are pending and not cancelled) and once an event or trigger cause is satisfied (e.g., there are multiple measurement results associated with a candidate beam or candidate RS that are better than the measurement results associated with the indicated beam), the UE does not trigger or has not triggered a UE-initiated report. Preferably, in some embodiments, in such a case, the UE will delay the UE-initiated trigger. Preferably, in some embodiments, the UE will store a counter or timer associated with the UE-initiated or event-triggered report, or store a counter timer associated with the trigger cause or event (e.g., depending on whether the counter or timer granularity is configured or for a specific target). Preferably, in some embodiments, the UE reports to the network node a second ability regarding the number of simultaneously pending (triggered and not cancelled) reports for each cell and a first ability regarding the number of simultaneously pending (triggered and not cancelled) reports for each UE. Preferably, in some embodiments, when the UE reports either the first ability or the second ability, there may be a preset number or value for determining the unreported ability. For example, when the UE does not report the first ability, the ability report implies or indicates that the UE does not support UE-initiated reports. Alternatively, in some embodiments, when the UE does not report the second ability, the ability report implies or indicates that the UE only supports a certain number of triggered reports for each cell. Preferably, in some embodiments, once the UE supports the first ability, the UE should (simultaneously) report the second ability.

[0485] Preferably, in some embodiments, the number of one or more triggered (UE-initiated or event-triggered) reports is determined at least based on which (which) serving cells are configured with UE-initiated or event-triggered reports.

[0486] Preferably, in some embodiments, the serving cell is configured with UE-initiated or event-triggered reporting. Preferably, in some embodiments, the UE receives from a network node a configuration for configuring UE-initiated or event-triggered reporting associated with the serving cell. Preferably, in some embodiments, the UE-initiated or event-triggered reporting is configured with a specific configuration. Preferably, in some embodiments, the specific configuration cannot or cannot be restricted to not being configured in an aperiodic CSI trigger state (for example, the basic principle is that there is an independent mechanism between UE-triggered and network-node-triggered). Preferably, in some embodiments, the specific configuration is dedicated to UE-triggered reporting. Preferably, in some embodiments, the network node is restricted from triggering the UE to apply or use the specific configuration to report one or more second reports in response to DCI. Preferably, in some embodiments, the DCI scheduling includes UL resources for transmitting one or more second reports. Preferably, in some embodiments, one or more second reports are multiplexed in the UL resources. Preferably, in some embodiments, one or more second reports are configured with one or more configurations different from the specific configuration (for example, one or more CSI report configurations). Preferably, in some embodiments, the specific configuration may correspond to a CSI report configuration. Preferably, in some embodiments, a parameter in the CSI report configuration may be used to indicate whether the CSI report configuration is associated with UE-triggered or network-node-triggered reporting. Based on a parameter, the UE can determine whether a CSI report configuration corresponds to UE-triggered or network-node-triggered reporting. Preferably, in some embodiments, a parameter in the CSI report configuration may correspond to an original parameter (or a new parameter) with a new code point or a new value for indicating time-domain behavior. For example, a parameter in the CSI report configuration may be CSI-AperiodicTriggerStateList. A parameter may be the (non-zero) code point of the CSI request field indicated in the DCI. In one instance, a parameter may indicate {aperiodic, periodic, semi-persistent, UE-triggered}. Preferably, in some embodiments, based on a parameter or an indication from a parameter, the UE can determine the time-domain behavior associated with a CSI report configuration. Preferably, in some embodiments, the UE does not expect to be configured with an aperiodic CSI trigger state associated with a CSI report configuration configured with UE-triggered or associated with UE-triggered. Preferably, in some embodiments, the UE will measure or receive one or more RSs associated with one or more CSI report configurations configured with UE-triggered. Preferably, in some embodiments, for UE-triggered reporting, the UE measures one or more RSs associated with one or more CSI report configurations configured with UE-triggered. Preferably, in some embodiments, one or more RSs (for deriving CSI associated with UE-triggered reporting) may also be associated with a CSI report configuration configured with a trigger other than UE-triggered.Alternatively, in some embodiments, one or more RSs are restricted to also be associated with a UE-triggered CSI reporting configuration.

[0487] Preferably, in some embodiments, the network node-triggered reports include or correspond to an aperiodic CSI report, a periodic CSI report, a semi-persistent CSI report.

[0488] Preferably, in some embodiments, the UL resources for transmitting one or more triggered reports (e.g., UE-triggered reports) can be based on semi-static configured resources or dynamic scheduling. Preferably, in some embodiments, the semi-static configured resources correspond to resources associated with type 1 UL configured grants or resources associated with type 2 UL configured grants. Preferably, in some embodiments, the dynamic resources correspond to resources scheduled by a third DCI. Preferably, in some embodiments, the third DCI is not allowed to trigger an aperiodic CSI report. Alternatively, in some embodiments, the third DCI is not allowed to trigger an aperiodic CSI report. Preferably, in some embodiments, the third DCI is received after the timing of the transmission request for at least the UE-triggered report.

[0489] Preferably, in some embodiments, a restriction is applied to the DCI for scheduling UL resources in the network node.

[0490] Preferably, in some embodiments, in response to a trigger, the UE will report one or more (triggered) reports to the network node. Preferably, in some embodiments, if (pre)configured, the resources for (delivering / including / transmitting) one or more triggered reports can be (pre)configured by the network in advance. Preferably, in some embodiments, the resources correspond to PUCCH or PUSCH resources. Preferably, in some embodiments, when there are no such resources covering one or more (triggered) reports, the UE will trigger a specific SR (for requesting resources). Preferably, in some embodiments, the specific SR is (pre)configured to request resources for transmitting (triggered) one or more reports. Preferably, in some embodiments, the triggering of one or more reports is triggered by the UE itself. Preferably, in some embodiments, the triggered one or more reports are at least based on signaling from one or more network nodes indicating a change in status. Preferably, in some embodiments, the specific SR is not associated with a logical channel. Alternatively, in some embodiments, the specific SR can be configured with or associated with a logical channel. Preferably, in some embodiments, the specific SR can be triggered without being associated with a Buffer Status Reporting / Report (BSR). Preferably, in some embodiments, the specific SR is not associated with a RACH configuration.

[0491] Preferably, in some embodiments, one or more conditions may have a relatively shorter period than an event associated with mobility.

[0492] Preferably, in some embodiments, after transmitting a specific SR, the UE (is expected to) receive a fourth DCI for scheduling UL resources for delivering / transmitting one or more triggered reports. Preferably, in some embodiments, before transmitting a specific SR or before triggering one or more reports, the UE does not expect to receive a fourth DCI for scheduling UL resources for delivering / transmitting one or more triggered reports. Preferably, in some embodiments, the fourth DCI is a type of third DCI. Preferably, in some embodiments, the fourth DCI schedules PUCCH or PUSCH resources for one or more UE-triggered reports. In an example, after the UE transmits a specific SR (and one or more triggered reports are not cancelled and / or the triggered scheduling request is not cancelled), the UL resources (scheduled by the third DCI or the fourth DCI) may correspond to PUCCH or PUSCH. The fourth DCI may indicate parameters associated with the (triggered) one or more reports (e.g., the (non-zero) code point in the CSI request field). If or whenever the DCI does not indicate parameters associated with one or more triggered reports, the UE may not deliver / transmit one or more triggered reports on the UL resources scheduled by the DCI. For a specific PUCCH scheduled by the fourth DCI, the fourth DCI may be a stand-alone DCI that does not schedule DL (e.g., PDSCH) or UL (e.g., PUSCH). Preferably, in some embodiments, the specific PUCCH only includes one or more triggered reports. Preferably, in some embodiments, the specific PUCCH may be further determined based on the payload size of one or more triggered reports. For example, different payload sizes may correspond to different specific PUCCHs. Preferably, in some embodiments, the UE may be configured with a set of specific PUCCH resources. Preferably, in some embodiments, when the payload size corresponds to a first range (e.g., 1 to (the first number - 1)), (in response to the fourth DCI) it is determined to use a first specific PUCCH resource in the set of PUCCH resources (with the lowest PUCCH resource ID or the lowest ID in the set of PUCCH resources). Preferably, in some embodiments, when the payload size corresponds to a second range (e.g., the first number to (the second number - 1)), (in response to the fourth DCI) it is determined to use a second specific PUCCH resource in the set of PUCCH resources (with the second lowest PUCCH resource ID or the second lowest ID in the set of PUCCH resources). In other words, since the network node does not know which one or which set of report configurations (associated with the triggered UE) is triggered, one fourth DCI may correspond to a set of specific PUCCH resources. Preferably, in some embodiments, the UE may be configured with one or more payload size ranges associated with a specific PUCCH resource in a set of specific PUCCH resources.Preferably, in some embodiments, the UE may be configured with a first number, a second number, …, an Nth number in an N+1 range for configuring the payload size. Preferably, in some embodiments, one or more (triggered) reports correspond to CSI reports. Preferably, in some embodiments, one or more (triggered) reports do not correspond to Hybrid Automatic Repeat Request (HARQ) reports. Preferably, in some embodiments, one or more (triggered) reports do not correspond to CSI report configurations not associated with the triggered UE.

[0493] When there is an overlap between the UE-triggered report and the UCI or network node-triggered report, or when the UE-triggered report and the UCI or network node-triggered report are (attempted to be transmitted) in the same TTI (e.g., sub-slot, multiple symbols, slot, sub-frame), they may be in different symbols (non-overlapping), and the UE gives priority to the UE-triggered report. Alternatively, in some embodiments, the UE gives priority to the network node-triggered report.

[0494] Preferably, in some embodiments, prioritization may be performed based on other criteria, and the UE may determine which triggered report has priority. Preferably, in some embodiments, the criteria may be the serving cell index associated with the measurement DL RS used to generate / deduce / determine the report, and / or a lower serving cell index corresponds to a higher priority. Preferably, in some embodiments, the report triggered by the UE corresponds to a higher priority than the aperiodic CSI report. Alternatively and / or preferably, in some embodiments, the report triggered by the UE corresponds to the same priority as the aperiodic CSI report. Preferably, in some embodiments, the report triggered by the UE corresponds to a higher priority than the periodic CSI report and / or the semi-persistent CSI report. Alternatively and / or preferably, in some embodiments, the report triggered by the UE corresponds to a lower priority than the periodic CSI report and / or the semi-persistent CSI report. Preferably, in some embodiments, the criteria may be based on the ID of the report configuration or the ID associated with the report configuration, and / or a lower ID corresponds to a higher priority. Preferably, in some embodiments, the criteria may be based on the report content, and / or the report content associated with L1-RSRP or L1-SINR may have a higher priority than the report content associated with non-L1-RSRP or non-L1-SINR (without CJT calibration report). Preferably, in some embodiments, the report content associated with CJT calibration may be associated with the same priority as the report content associated with L1-RSRP or L1-SINR. Alternatively and / or preferably, in some embodiments, the report content associated with CJT calibration may be associated with a higher priority than the report content associated with L1-RSRP or L1-SINR. Alternatively and / or preferably, in some embodiments, the report content associated with CJT calibration may be associated with a lower priority than the report content associated with L1-RSRP or L1-SINR. Preferably, in some embodiments, the report content associated with CJT calibration may be associated with a higher priority than the report content associated with non-L1-RSRP or non-L1-SINR.

[0495] Preferably, in some embodiments, the prioritization here means or corresponds to transmission in UL resources in a TTI. Preferably, in some embodiments, the prioritization here means or corresponds to being multiplexed first / earlier in UL resources in a TTI. Preferably, in some embodiments, once the capacity of the UL resources is achieved, the de-prioritized report will be discarded or cancelled or not transmitted or not multiplexed in UL resources in a TTI.

[0496] The text proposal 1 (assuming one or more re-arranged reports are in UCI form) may be provided in underline and bold below.

[0497]

[0498] The following text proposal 2 can be provided in underlined and bold (assuming one or more re - arranged reports are in UCI form).

[0499]

[0500] Preferably, in some embodiments, the UE maintains a counter for counting the number of opportunities for the measurement results of one or more RSs (or one or more RS sets) to meet the conditions for triggering (UE - initiated or event - triggered) reports. Preferably, in some embodiments, once the UE transmits a (UE - initiated or event - triggered) report, the UE resets the counter. Preferably, in some embodiments, when the counter exceeds a threshold, the UE triggers a (UE - initiated or event - triggered) report. Preferably, in some embodiments, the threshold can be configured for each serving cell, for each serving cell group, for each UE, or for each specific configuration (associated with the UE - initiated report configuration), and / or the counter can be maintained for each serving cell, for each serving cell group, for each UE, or for each specific configuration (associated with the UE - initiated report configuration).

[0501] Preferably, in some embodiments, once the UE changes the indicated or activated TCI state, the UE resets the counter associated with the UE - initiated or event - triggered report (this can be a reset count associated with one or more specific configurations associated with the UE - initiated or event - triggered report). Preferably, in some embodiments, the UE is configured with one or more first specific configurations associated with a first serving cell. Preferably, in some embodiments, the UE is configured with one or more second specific configurations associated with a second serving cell. Preferably, in some embodiments, once the UE changes the indicated TCI state (e.g., via beam - indicating DCI) or the activated TCI state (e.g., via TCI state (de) - activation MAC CE), the UE resets the count of one or more counters associated with the UE - initiated or event - triggered report. Preferably, in some embodiments, the reset count may affect one or more serving cells for which the UE performs communication using the changed indicated or activated TCI state. Preferably, in some embodiments, the TCI state can be a DL, UL, and / or joint TCI state. Preferably, in some embodiments, the TCI state can be a DL or joint TCI state. Preferably, in some embodiments, resetting the counter means or corresponds to setting the counter to 0 or an initial value.

[0502] Preferably, in some embodiments, once the UE triggers a UE-initiated or event-triggered report, the UE resets the counter (associated with the UE-initiated or event-triggered report). Preferably, in some embodiments, once the UE cancels a triggered UE-initiated or event-triggered report, the UE resets the counter. Preferably, in some embodiments, based on the granularity of the counter being for a specific target, the counter associated with target A is reset in response to triggering associated with target A, and / or the counter associated with target B is not reset in response to triggering associated with a different target (e.g., target A). Preferably, in some embodiments, the target corresponds to a serving cell, a serving cell group, a specific configuration (associated with the UE-initiated or event-triggered report), an RS associated with a specific configuration (associated with the UE-initiated or event-triggered report), or an RS set associated with a specific configuration (associated with the UE-initiated or event-triggered report).

[0503] Preferably, in some embodiments, once the UE executes a MAC reset procedure, the UE resets the counter (associated with the UE-initiated or event-triggered report).

[0504] Preferably, in some embodiments, once the UE executes a handover or receives an RRCReconfiguration or a handover command, the UE resets the counter (associated with the UE-initiated or event-triggered report).

[0505] Preferably, in some embodiments, when a first trigger reason is satisfied (due to or according to a first specific configuration associated with the UE-initiated or event-triggered report), the UE triggers a first UE-initiated report.

[0506] Preferably, in some embodiments, when a timer expires or after an opportunity (associated with the latency requirement associated with the first specific configuration), the UE cancels the trigger.

[0507] Preferably, in some embodiments, when the UE transmits a first UE-initiated report, the UE cancels the trigger.

[0508] Additionally and / or alternatively, in some embodiments, the UE may cancel all (previous) report triggers (including the trigger) triggered before combining or transmitting the first UE-initiated report.

[0509] Preferably, in some embodiments, the first UE-initiated report is determined based on the measurement results of at least an RS set.

[0510] Preferably, in some embodiments, the UE may receive one or more CSI report configurations associated with a network node trigger (which corresponds to one or more second reports).

[0511] Preferably, in some embodiments, the second report may be associated with another RS set. Preferably, in some embodiments, the another RS set may include at least one RS that is the same as at least the RS set.

[0512] Preferably, in some embodiments, once or whenever the UE transmits the second report (including measurement results based on at least one RS), the UE cancels the trigger. Preferably, in some embodiments, the second report is transmitted before the timer expires or before the occasion.

[0513] Alternatively and / or preferably, in some embodiments, once or whenever the UE transmits the second report (including measurement results based on the (one or more or all) RSs associated with a first specific configuration), the UE cancels the trigger. Preferably, in some embodiments, the second report is transmitted before the timer expires or before the occasion.

[0514] Preferably, in some embodiments, one limitation is that the UE does not expect to receive different RS sets to be configured for network-triggered reports and UE-initiated reports. In other words, the CSI report configuration associated with network node triggering is associated with a different RS set (not overlapping with the RS set associated with the specific configuration associated with UE-initiated or event-triggered reports).

[0515] Preferably, in some embodiments, the UE does not expect to receive a configuration such that a specific configuration (associated with UE-initiated or event-triggered reports) is configured as an aperiodic CSI trigger state (e.g., CSI-AperiodicTriggerState or associatedReportConfigInfoList). Preferably, in some embodiments, in addition to the CSI report configuration having or being configured with a UE-initiated time-domain behavior, the CSI report configuration may also be configured within an aperiodic CSI trigger state.

[0516] Alternatively, in some embodiments, the configuration of an aperiodic CSI trigger state may be associated with a specific configuration having or being configured with a UE-initiated time-domain behavior, and when the UE receives DCI for a MAC CE to activate or indicate or trigger an aperiodic CSI trigger state, the UE will consider or determine to interpret the specific configuration as an aperiodic CSI report configuration.

[0517] Preferably, in some embodiments, the detection / measurement RS for UE-initiated or event-triggered reporting or associated with UE-initiated or event-triggered reporting should be configured to be periodic. Preferably, in some embodiments, the detection / measurement RS for UE-initiated or event-triggered reporting or associated with UE-initiated or event-triggered reporting is not configured to be aperiodic. Preferably, in some embodiments, the UE is configured in a semi-static manner with the detection / measurement RS for detecting whether the triggering condition of an event is met.

[0518] Preferably, in some embodiments, the UE may receive a specific configuration associated with UE-initiated or event-triggered reporting. Preferably, in some embodiments, the specific configuration may correspond to CSI-ReportConfig. Preferably, in some embodiments, the specific configuration may be based on the fact that in CSI-ReportConfig, the reportConfigType (e.g., time-domain behavior) is UE-initiated.

[0519] The following may be an exemplary structure of CSI-ReportConfig, where the reportConfigType is configured to be UE-initiated (e.g., there is a UE-initiated selection target in the reportConfigType, as shown underlined and in bold). Preferably, in some embodiments, the UE may receive another / other CSI-ReportConfig, where the reportConfigType is configured to be periodic, semiPersistentOnPUCCH, semiPersistentOnPUSCH, aperiodic.

[0520]

[0521]

[0522] Preferably, in some embodiments, the detailed (or specific) configuration or parameters in the reportConfigType configured for UE-initiated may include information associated with any one of (one or more) triggering events, (one or more) detection / measurement RSs, or UL resources. Preferably, in some embodiments, the information of the UL resource corresponds to the UL resource ID. Preferably, in some embodiments, the information of the triggering event corresponds to multiple thresholds that satisfy the declared event. Preferably, in some embodiments, one or more detection / measurement RSs may be associated with one triggering event. Preferably, in some embodiments, one detection / measurement RS is mapped one-to-one with the triggering event. Preferably, in some embodiments, another structure may be one triggering event including information associated with one or more detection / measurement RSs. Preferably, in some embodiments, based on the associated one or more detection / measurement RSs, the UE may have a measurement result associated with the detection / measurement RS. Preferably, in some embodiments, a specific configuration (e.g., CSI-ReportConfig) may be associated with at least two sets of CSI-RS for detecting / measuring RS. Preferably, in some embodiments, the two sets of CSI-RS include a first RS set and a second RS set. Preferably, in some embodiments, the measurement result may be applied or determined or measured based on one or more RSs in the first RS set. Preferably, in some embodiments, the measurement result may be applied or determined or measured based on one or more RSs in the second set of RSs. Preferably, in some embodiments, using or applying one or two measurement results may be based on the configuration of the triggering event corresponding to (i), (ii), (iii), and / or (iv), as described above. Preferably, in some embodiments, the UL resource may be PUCCH or PUSCH. Preferably, in some embodiments, there may be no configuration or parameter of the UL resource in the CSI-ReportConfig. Preferably, in some embodiments, based on the specific configuration, the UE may determine or generate one or more (UE-initiated or event-triggered) reports. Preferably, in some embodiments, one or more (UE-initiated or event-triggered) reports are delivered or included in the MAC CE or UCI. Preferably, in some embodiments, the quantity associated with the specific configuration corresponds to at least including RSRP or SINR.

[0523]

[0524]

[0525] Preferably, in some embodiments, another instance for configuring a first RS set and a second RS set associated with a specific configuration may be based on a correlation / mapping configuration. For UE-initiated or event-triggered reporting, the UE may receive a configuration for configuring the correlation between a specific configuration and the first RS set and the second RS set. Preferably, in some embodiments, the first RS set or the second RS set may be configured based on a CSI-RS resource set ID or indicated by a CSI-RS resource set ID. Preferably, in some embodiments, based on the CSI-RS resource set ID, the UE may determine or identify which RS set is used for measuring / detecting the corresponding resourceSet1. Preferably, in some embodiments, based on the CSI-RS resource set ID, the UE may determine or identify which RS set is used for measuring / detecting the corresponding resourceSet2. Preferably, in some embodiments, resourceSet1 corresponds to the first RS set. Preferably, in some embodiments, resourceSet2 corresponds to the second RS set. Preferably, in some embodiments, the CSI-ReportConfigId corresponds to a specific configuration (associated with UE-initiated or event-triggered reporting).

[0526] For example, see below:

[0527] CSI-AssociatedReportConfigInfo::=SEQUENCE{

[0528] reportConfigId CSI-ReportConfigId,

[0529] resourcesForChannel resourceSet1

[0530] resourcesForChannel2 resourceSet2

[0531] Preferably, in some embodiments, another instance for configuring an RS set as a candidate RS (associated with a beam or TCI state for UE-initiated or event-triggered reporting) may be based on an association / mapping configuration. For UE-initiated or event-triggered reporting, the UE may receive a configuration for configuring the association between a specific configuration and the RS set. Preferably, in some embodiments, the RS set may be configured based on or indicated by a CSI-RS resource set ID. Preferably, in some embodiments, based on the CSI-RS resource set ID, the UE may determine or identify which RS set is used for measuring / detecting the corresponding resourceSet. Preferably, in some embodiments, the resourceSet corresponds to the RS set. Preferably, in some embodiments, the CSI-ReportConfigId corresponds to a specific configuration (associated with UE-initiated or event-triggered reporting). Preferably, in some embodiments, one or more RSs associated with the indicated DL / UL / joint TCI state may be determined as or regarded as the RSs for comparison. Preferably, in some embodiments, the RSs configured in the resoruceSet as shown below may be determined as candidate beams or candidate RSs. Preferably, in some embodiments, the RSs configured in the resourceSet may be used to trigger reporting. Preferably, in some embodiments, the measurement results of the RSs in the resourceSet may be transmitted as the content of UE-initiated or event-triggered reporting.

[0532] For example, see below:

[0533] CSI-AssociatedReportConfigInfo::=SEQUENCE{

[0534] reportConfigId CSI-ReportConfigId,

[0535] resourcesForChannel resourceSet

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

[0537] Refer to Figure 8, using this and other concepts, systems, and methods of the present invention, method 1000 for a UE (or network node or TRP) in a wireless communication system includes: receiving one or more specific (report) configurations associated with a UE-initiated report, where the one or more specific configurations are associated with parameters for configuring time-domain behavior as UE-initiated (step 1002); when the UE attempts to transmit more than one report within a time point or TTI, the UE prioritizes and transmits the reports based on a priority value (step 1004); and transmitting one or more reports to a network node at a time point or TTI (step 1006).

[0538] Preferably, in some embodiments, the priority value of a report is determined based at least on time-domain behavior, cell ID, report configuration ID, measurement RS ID.

[0539] Preferably, in some embodiments, a lower priority value corresponds to a higher priority.

[0540] Preferably, in some embodiments, UE-initiated reports have a higher priority than other reports associated with different time-domain behaviors.

[0541] Preferably, in some embodiments, the cell ID corresponds to which cell is configured by the (specific) report configuration for transmitting the report or which cell is associated with the (specific) report configuration for transmitting the report.

[0542] Preferably, in some embodiments, the cell ID corresponds to which cell is configured by the (specific) report configuration for receiving the RS for measurement or which cell is associated with the (specific) report configuration for receiving the RS for measurement.

[0543] Preferably, in some embodiments, the measurement RS ID corresponds to which RS is configured by the (specific) report configuration for receiving for measurement or is associated with which RS is configured by the (specific) report configuration for receiving for measurement.

[0544] Preferably, in some embodiments, the priority value associated with a UE-initiated report is lower than that of a network-triggered report.

[0545] Preferably, in some embodiments, based on the priority, the UE can prioritize multiplexing to transmit reports in ascending order of the priority value at a time point or TTI (e.g., first multiplex higher-priority reports).

[0546] Preferably, in some embodiments, the UE performs multiplexing until the capacity or payload size of the UL resources (for transmitting one or more reports) in the time point or TTI is satisfied.

[0547] Preferably, in some embodiments, the UE may be configured with a first threshold associated with UE-initiated reporting.

[0548] Preferably, in some embodiments, the UE may be configured with a second threshold associated with network node-triggered reporting.

[0549] Preferably, in some embodiments, based on the priority value associated with the UE-initiated reporting being less than the first threshold and the network node-triggered reporting being greater than the second threshold, the UE preferentially multiplexes the UE-initiated reporting associated with the priority value less than the first threshold (preferably, in some embodiments, otherwise, the UE prioritizes the network node-triggered reporting).

[0550] Preferably, in some embodiments, based on a threshold, if the priority value associated with the UE-initiated reporting is less than the first threshold, the UE preferentially multiplexes the UE-initiated reporting.

[0551] Preferably, in some embodiments, the UE does not expect to multiplex the UE-initiated reporting and the network node-triggered reporting at the same time point or in the same TTI.

[0552] Preferably, in some embodiments, once the UE multiplexes two types of reports (e.g., UE-initiated reporting and network node-triggered reporting), the report includes information associated with the report configuration ID or an indication related to the UE-initiated reporting or the network node reporting.

[0553] Preferably, in some embodiments, when the indication related to the UE-initiated reporting or the network node reporting corresponds to 1 or a first value of the first report, the first report corresponds to the UE-initiated reporting (the value 1 is an example, and it can also be the value 0).

[0554] Preferably, in some embodiments, when the indication related to the UE-initiated reporting or the network node reporting corresponds to 0 or a second value of the second report, the second report corresponds to the network node-triggered reporting (the value 0 is an example, and it can also be the value 1).

[0555] Return reference Figure 3 and 4, in one or more embodiments from the perspective of a UE (or network node or TRP) in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) receive one or more specific (report) configurations associated with UE-initiated reports, where the one or more specific configurations are associated with parameters for configuring time-domain behavior as UE-initiated; (ii) when the UE attempts to transmit more than one report within a time point or TTI, the UE prioritizes and transmits reports based on a priority value; and (iii) transmit one or more reports to a network node at a time point or TTI. Additionally, CPU 308 may execute program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0556] Reference Figure 9 , using this and other concepts, systems, and methods of the present invention, method 1010 for a UE (or network node or TRP) in a wireless communication system includes: triggering one or more reports based on or in response to satisfying one or more triggers, preferably the reports may be beam reports or CJT calibration reports (step 1012); determining whether to trigger an SR based on whether there are UL resources available for a new transmission that include one or more reports (step 1014); and transmitting one or more reports on the UL resources at a time point or TTI (step 1016).

[0557] Preferably, in some embodiments, when there are UL resources available for a new transmission that include one or more reports, the UE transmits one or more reports without triggering an SR.

[0558] Preferably, in some embodiments, when there are no UL resources available for a new transmission that include one or more reports, the UE triggers an SR, and / or transmits the SR on a PUCCH resource.

[0559] Preferably, in some embodiments, one or more trigger reasons correspond to a change in condition.

[0560] Preferably, in some embodiments, one or more trigger reasons are associated with each configured target.

[0561] Preferably, in some embodiments, one target corresponds to any one or any combination of an RS, a set of RSs, a report configuration, a serving cell, a candidate cell, a cell group.

[0562] Preferably, in some embodiments, the condition change corresponds to any one or any combination of the following: receiving a signal indication from a dormant BWP to a non-dormant BWP; expiration of a timer for changing a dormant BWP to a non-dormant BWP; transmitting a second signal to a network node to effect a change (for requesting a change from a dormant BWP to a non-dormant BWP); receiving an LTM TCI state activation or indication from a network node; receiving a signal indicating activation of an SCell; receiving a signal indicating activation of a CG; receiving a signal indicating addition of a PSCell (except in the case where the SCG is deactivated), preferably where the newly added or changed PSCell; receiving an RRC reconfiguration message, preferably, in some embodiments, the RRC reconfiguration message is associated with a UE-initiated report and has information regarding a change in an RS or serving cell, BWP, or a configuration change to the UE-initiated report; receiving a signal for switching from SDT to non-SDT (or from RRC inactive state to RRC connected state); receiving an RRC resume message from a network node; detecting that the number of path loss changes is higher than a value exceeding a threshold; and / or one or more specific configurations for configuring event-related configurations.

[0563] Preferably, in some embodiments, there may be one or more additional conditions for determining whether the trigger cause is satisfied, and / or one or more additional conditions may be any one or any combination of the following: whether the target (e.g., serving cell) associated with one or more reports is configured for uplink (operation); whether the target (e.g., serving cell) associated with one or more reports is configured for downlink (operation); and / or preferably, in some embodiments, at least when one or both of the above conditions are satisfied, it may be considered or determined that the trigger cause is satisfied.

[0564] Preferably, in some embodiments, there may be one or more additional conditions for determining whether the trigger cause is satisfied, and / or one or more additional conditions may be any one or any combination of the following: whether the target (e.g., serving cell) associated with one or more reports is in an active dormant BWP; whether the target (e.g., serving cell) associated with one or more reports is not activated; whether a prohibit timer associated with the trigger cause is running; whether a prohibit timer associated with a specific configuration is running; preferably, in some embodiments, at least when one or all of the above conditions are satisfied, it may be considered or determined that the trigger cause is not satisfied; and / or preferably, in some embodiments, at least when one or all of the above conditions are satisfied, the UE does not care whether the trigger cause of the target is satisfied.

[0565] Preferably, in some embodiments, one or more reports include report information associated with at least the trigger cause.

[0566] Preferably, in some embodiments, one or more reports do not include report information associated with a trigger reason of no trigger and / or a trigger reason for which the associated target is in a dormant state or not activated.

[0567] Preferably, in some embodiments, one or more reports include report information associated with both ID information and measurement results.

[0568] Preferably, in some embodiments, the measurement result corresponds to a candidate RS, or the measurement result corresponds to both a candidate RS and a source RS that are in the indicated TCI state or associated with a currently used / indicated / activated beam / RS.

[0569] Preferably, in some embodiments, the measurement result corresponds to the RSRP or SINR of the RS.

[0570] Preferably, in some embodiments, the ID information corresponds to a UE - initiated report or a network - node - triggered report, a report configuration ID.

[0571] Preferably, in some embodiments, once or in response to the UE transmitting a report associated with a trigger reason or a specific configuration, the UE starts a prohibition timer, where the specific configuration is associated with, includes, or configures the prohibition timer.

[0572] Preferably, in some embodiments, one or more specific configurations for configuring event - related configurations include information having a measurement RS and a measurement quantity.

[0573] Preferably, in some embodiments, one or more specific configurations correspond to a CSI report configuration, where a flag or parameter for configuring this CSI report configuration corresponds to a UE - initiated report configuration.

[0574] Preferably, in some embodiments, the flag or parameter can extend the current RRC parameter for configuring the time - domain behavior (e.g., aperiodic, periodic, semi - persistent, UE - initiated) of such a CSI report configuration.

[0575] Preferably, in some embodiments, for a UE - initiated CSI report configuration, the CSI report configuration does not include PUSCH or PUCCH resources of the RRC configuration associated with the report (e.g., PUSCH corresponds to type 1 uplink (UL) configured grant configuration), and / or preferably, the UE will make a request or transmission on the current PUCCH or PUSCH available for new transmissions, where the current PUCCH or PUSCH can cover or include a UE - initiated report associated with the UE - initiated CSI report configuration.

[0576] Preferably, in some embodiments, the number of one or more reports is determined based on at least or at most the number of trigger reasons satisfied.

[0577] Preferably, in some embodiments, based on the number of triggering reasons for which a trigger is satisfied, the number of specific configurations of conditions for which a trigger is satisfied, the number of triggering reasons associated with a target, and the fact that one triggering reason is associated with multiple reporting messages, the UE may determine the number of one or more reports.

[0578] Preferably, in some embodiments, one triggering reason may correspond to one or more reporting messages.

[0579] Preferably, in some embodiments, one target corresponds to a serving cell, a cell group, or a specific configuration associated with a report initiated by a UE.

[0580] Preferably, in some embodiments, one reporting message corresponds to a measurement result based on one candidate RS, or a pair of candidate RSs, or a set of candidate RSs.

[0581] Preferably, in some embodiments, one reporting message corresponds to a measurement result based on a pair of one candidate RS and a currently used / indicated / activated RS.

[0582] Preferably, in some embodiments, one reporting message includes index information associated with the triggering reason (for example, a change in condition corresponds to index 0, and a specific configuration corresponds to index 1).

[0583] Return reference Figure 3 and 4 , in one or more embodiments from the perspective of a UE (or network node or TRP) in a wireless communication system, apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) trigger one or more reports based on or in response to one or more triggers being satisfied, preferably the reports may be beam reports or CJT calibration reports; (ii) determine whether to trigger an SR based on whether there is UL resource available for a new transmission that includes one or more reports of triggers; and (iii) transmit one or more reports on the UL resource at a time point or TTI. Additionally, the CPU 308 may execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0584] It should be noted that any of the methods, alternatives, concepts, examples, and embodiments described above and herein may be combined fully or partially, or applied simultaneously or separately.

[0585] Reference Figure 10, using this and other concepts, systems, and methods of the present invention, a method 1020 for a UE in a wireless communication system includes: triggering a first report in response to a first condition being met (step 1022); transmitting a request in response to the triggering of the first report (step 1024); receiving a first DCI scheduling a first PUSCH (step 1026); determining whether to transmit the first report on the first PUSCH based on whether the CSI request field in the first DCI indicates a first code point associated with a first CSI trigger state, the first CSI trigger state being associated with a first CSI report configuration for the first report (step 1028); and if the CSI request field in the first DCI indicates the first code point, transmitting the first report on the first PUSCH (step 1030).

[0586] In various embodiments, if the CSI request field in the first DCI does not indicate the first code point, the UE does not transmit the first report on the first PUSCH.

[0587] In various embodiments, the request is specifically configured for the first report triggered by the UE, and / or the request is not associated with any logical channel, and / or the request is triggered without being associated with a BSR, and / or the request is not associated with a random access channel (RACH) configuration, and / or the request is or corresponds to an SR.

[0588] In various embodiments, before transmitting the request, the UE does not expect to receive a DCI with a CSI request field indicating the first code point; and / or if the UE has not triggered the first report, the UE does not expect to receive a DCI with a CSI request field indicating the first code point; and / or the first code point is configured with a single CSI report configuration.

[0589] In various embodiments, the UE receives a second configuration for configuring the association between the first CSI trigger state and the first CSI report configuration, where the first CSI report configuration is associated with the first report triggered by the UE; and / or the second configuration further provides the association between a second CSI trigger state and a second CSI report configuration; and / or the second CSI report configuration is for a second report triggered by a network node; and / or based on the absence of a parameter associated with the second CSI report configuration, the UE determines that the second CSI report configuration is for the second report triggered by the network node; and / or based on a parameter indicating aperiodic, periodic, or semi-persistent information, the UE determines that the second CSI report configuration is for the second report triggered by the network node.

[0590] In various embodiments, the UE receives a second DCI scheduling a second PUSCH and transmits a second report on the second PUSCH in response to the CSI request field in the second DCI indicating a second code point associated with a second CSI trigger state.

[0591] In various embodiments, a parameter associated with a first CSI report configuration is used to indicate or configure that the first CSI report configuration is for a first report triggered by a UE; and / or based on the existence of a parameter associated with the first CSI report configuration, the UE determines that the first CSI report configuration is for a first report triggered by the UE; and / or based on information indicating a report initiated by the UE, the UE determines that the first CSI report configuration is for a first report triggered by the UE.

[0592] In various embodiments, the UE determines whether the first CSI report configuration is for a first report triggered by the UE based on whether the first CSI report configuration is associated with information associated with an event or condition and / or based on whether the first CSI report configuration is associated with one or more candidate reference signals (RSs) corresponding to one or more candidate beams; and / or based on the first CSI report configuration being associated with the information associated with the event or condition and / or based on whether the first CSI report configuration is associated with one or more candidate RSs corresponding to one or more candidate beams, the UE determines that the first CSI report configuration is for a first report triggered by the UE.

[0593] In various embodiments, the UE receives a configuration of a first condition to trigger a first report by the UE, where the first report is a layer 1 (L1) report; and / or the first report corresponds to a type of uplink control information (UCI).

[0594] In various embodiments, the first condition includes at least one of the following: the quality of one or more candidate beams has an offset better than the quality of the current beam, and the UE determines the quality of the current beam based on measurements of a first RS and determines the quality of one or more candidate beams based on measurements of one or more candidate RSs, and the quality corresponds to L1 reference signal received power (RSRP).

[0595] In various embodiments, if the UE receives a type 1 uplink configured grant configuration for a set of uplink (UL) resources for transmitting a first report triggered by the UE, the UE transmits the first report on a UL resource among the set of UL resources; and / or if the UE does not receive a type 1 uplink configured grant configuration for a set of UL resources for transmitting a first report triggered by the UE, the UE transmits a request in response to the triggering of the first report.

[0596] Return reference Figure 3 and 4, in one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) trigger a first report in response to a first condition being met; (ii) transmit a request in response to the triggering of the first report; (iii) receive a first DCI scheduling a first PUSCH; (iv) determine whether to transmit the first report on the first PUSCH based on whether the CSI request field in the first DCI indicates a first code point associated with a first CSI triggering state, the first CSI triggering state being associated with a first CSI report configuration for the first report; and (v) if the CSI request field in the first DCI indicates the first code point, transmit the first report on the first PUSCH. Additionally, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or herein.

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

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

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

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

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

[0602] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented within or by an integrated circuit ("IC"), access terminal, or access point. The IC can 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 can execute code or instructions residing within the IC, outside the IC, or in both cases. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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

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

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

Claims

1. A method for a user equipment, characterized in that: include: triggering a first report in response to a first condition being satisfied; transmitting a request in response to said triggering of said first report; Receiving first downlink control information for scheduling a first physical uplink shared channel; determining whether to transmit the first report on the first physical uplink shared channel based on whether a channel state information request field in the first downlink control information indicates a first code point associated with a first channel state information triggering state, the first channel state information triggering state being associated with a first channel state information reporting configuration for the first report; as well as If the channel state information request field in the first downlink control information indicates the first code point, transmitting the first report on the first physical uplink shared channel.

2. The method according to claim 1, characterized in that: If the channel state information request field in the first downlink control information does not indicate the first code point, the user equipment does not transmit the first report on the first physical uplink shared channel.

3. The method according to claim 1, characterized in that: The request is specifically configured for the first report triggered by the user equipment, and / or The request is not associated with any logical channel, and / or The request is triggered without being associated with a buffer status report, and / or The request is not associated with a random access channel configuration, and / or The request is or corresponds to a scheduling request.

4. The method according to claim 1, characterized in that: Prior to transmitting the request, the user equipment does not expect to receive downlink control information having the channel state information request field indicating the first code point, and / or If the user equipment does not trigger the first report, the user equipment does not expect to receive the downlink control information having the channel state information request field indicating the first code point, and / or The first code point is configured with a single channel state information reporting configuration.

5. The method according to claim 1, characterized in that: The user equipment receives a second configuration for configuring an association between the first channel state information triggering state and the first channel state information reporting configuration, wherein the first channel state information reporting configuration is associated with the first report triggered by the user equipment, and / or The second configuration further provides an association between the second channel state information triggering state and the second channel state information reporting configuration, and / or The second channel state information report configuration is used for a second report triggered by a network node, and / or Based on the absence of a parameter associated with the second channel state information reporting configuration, the user equipment determines that the second channel state information reporting configuration is for a second report triggered by the network node, and / or Based on the one parameter indicating aperiodic, periodic or semi-persistent information, the user equipment determines that the second channel state information reporting configuration is for a second report triggered by the network node.

6. The method according to claim 5, characterized in that The user equipment receives second downlink control information scheduling a second physical uplink shared channel, and transmits the second report on the second physical uplink shared channel in response to the channel state information request field in the second downlink control information indicating a second code point associated with the second channel state information triggering state.

7. The method according to claim 1, characterized in that: a parameter associated with the first channel state information reporting configuration is used to indicate or configure that the first channel state information reporting configuration is used for the first report triggered by the user equipment, and / or Based on the presence of the one parameter associated with the first channel state information reporting configuration, the user equipment determines that the first channel state information reporting configuration is for the first report triggered by the user equipment, and / or Based on the one parameter indicating information of the report initiated by the user equipment, the user equipment determines that the first channel state information report configuration is used for the first report triggered by the user equipment.

8. The method according to claim 1, characterized in that: The user equipment determines whether the first channel state information reporting configuration is used for the first report triggered by the user equipment based on whether the first channel state information reporting configuration is associated with information associated with an event or condition and / or based on whether the first channel state information reporting configuration is associated with one or more candidate reference signals corresponding to one or more candidate beams, and / or Based on the first channel state information reporting configuration being associated with the information associated with the event or the condition and / or based on whether the first channel state information reporting configuration is associated with the one or more candidate reference signals corresponding to the one or more candidate beams, the user equipment determines that the first channel state information reporting configuration is used for the first report triggered by the user equipment.

9. The method according to claim 1, characterized in that: The user equipment receives a configuration of the first condition to trigger the first report by the user equipment, wherein the first report is a layer 1 report, and / or The first report corresponds to a type of uplink control information.

10. The method according to claim 1, characterized in that The first condition includes at least one of the following: The quality of one or more candidate beams has an offset that is better than the quality of the current beam, and The user equipment determines the quality of the current beam based on a measurement of a first reference signal, and determines the quality of the one or more candidate beams based on a measurement of one or more candidate reference signals, and The quality corresponds to the layer 1 reference signal received power.

11. The method according to claim 1, characterized in that: If the user equipment receives a type 1 uplink configured grant configuration for a set of uplink resources for transmitting the first report triggered by the user equipment, the user equipment transmits the first report on an uplink resource in the set of uplink resources, and / or The user equipment transmits the request in response to the triggering of the first report if the user equipment has not received the type 1 uplink configured grant configuration for the set of uplink resources for transmitting the first report triggered by the user equipment.

12. 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: triggering a first report in response to a first condition being satisfied; transmitting a request in response to said triggering of said first report; Receiving first downlink control information for scheduling a first physical uplink shared channel; determining whether to transmit the first report on the first physical uplink shared channel based on whether a channel state information request field in the first downlink control information indicates a first code point associated with a first channel state information triggering state, the first channel state information triggering state being associated with a first channel state information reporting configuration for the first report; and If the channel state information request field in the first downlink control information indicates the first code point, transmitting the first report on the first physical uplink shared channel.

13. The user equipment according to claim 12, characterized in that: The request is specifically configured for the first report triggered by the user equipment, and / or The request is not associated with any logical channel, and / or The request is triggered without being associated with a buffer status report, and / or The request is not associated with a random access channel configuration, and / or The request is or corresponds to a scheduling request.

14. The user equipment according to claim 12, characterized in that: Prior to transmitting the request, the user equipment does not expect to receive downlink control information having the channel state information request field indicating the first code point, and / or If the user equipment does not trigger the first report, the user equipment does not expect to receive the downlink control information having the channel state information request field indicating the first code point, and / or The first code point is configured with a single channel state information reporting configuration.

15. The user equipment according to claim 12, characterized in that: The user equipment receives a second configuration for configuring an association between the first channel state information triggering state and the first channel state information reporting configuration, wherein the first channel state information reporting configuration is associated with the first report triggered by the user equipment, and / or The second configuration further provides an association between the second channel state information triggering state and the second channel state information reporting configuration, and / or The second channel state information report configuration is used for a second report triggered by a network node, and / or Based on the absence of a parameter associated with the second channel state information reporting configuration, the user equipment determines that the second channel state information reporting configuration is for a second report triggered by the network node, and / or Based on the one parameter indicating aperiodic, periodic or semi-persistent information, the user equipment determines that the second channel state information reporting configuration is for a second report triggered by the network node.

16. The user equipment according to claim 15, characterized in that The user equipment receives second downlink control information scheduling a second physical uplink shared channel, and transmits the second report on the second physical uplink shared channel in response to the channel state information request field in the second downlink control information indicating a second code point associated with the second channel state information triggering state.

17. The user equipment according to claim 12, characterized in that: a parameter associated with the first channel state information reporting configuration is used to indicate or configure that the first channel state information reporting configuration is used for the first report triggered by the user equipment, and / or Based on the presence of the one parameter associated with the first channel state information reporting configuration, the user equipment determines that the first channel state information reporting configuration is for the first report triggered by the user equipment, and / or Based on the one parameter indicating information of the report initiated by the user equipment, the user equipment determines that the first channel state information report configuration is used for the first report triggered by the user equipment.

18. The user equipment according to claim 12, characterized in that: The user equipment determines whether the first channel state information reporting configuration is used for the first report triggered by the user equipment based on whether the first channel state information reporting configuration is associated with information associated with an event or condition and / or based on whether the first channel state information reporting configuration is associated with one or more candidate reference signals corresponding to one or more candidate beams, and / or Based on the first channel state information reporting configuration being associated with the information associated with the event or the condition and / or based on whether the first channel state information reporting configuration is associated with the one or more candidate reference signals corresponding to the one or more candidate beams, the user equipment determines that the first channel state information reporting configuration is used for the first report triggered by the user equipment.

19. The user equipment according to claim 12, characterized in that: The user equipment receives a configuration of the first condition to trigger the first report by the user equipment, wherein the first report is a layer 1 report, and / or The first report corresponds to a type of uplink control information.

20. The user equipment according to claim 12, characterized in that: If the user equipment receives a type 1 uplink configured grant configuration for a set of uplink resources for transmitting the first report triggered by the user equipment, the user equipment transmits the first report on an uplink resource in the set of uplink resources, and / or If the user equipment does not receive the request for transmitting the said type 1 uplink of said set of uplink resources of a first report is configured with a configured grant, The user equipment then transmits the request in response to the triggering of the first report.

Images