Method and apparatus for transmitting report in wireless communication system

Abstract

Methods, systems, and devices for transmitting reports in a wireless communication system are provided. The method for the user equipment comprises the following steps: determining a first group of physical uplink control channel resources for a scheduling request, the first set of physical uplink control channel resources for an indication associated with a beam report initiated by a user equipment and a third set of physical uplink control channel resources for a hybrid automatic repeat request, and transmitting the hybrid automatic repeat request and information to a network node, the first set of physical uplink control channel resources being used for an indication associated with the beam report initiated by the user equipment, and the third set of physical uplink control channel resources for the hybrid automatic repeat request, wherein the information indicates one code point among a first group of physical uplink control channel resources for the scheduling request and a second group of physical uplink control channel resources for the indication.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application Serial No. 63 / 667,534, filed July 3, 2024, which is hereby incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to methods and apparatus for transmitting reports in wireless communication systems. Background Technology

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

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

[0006] Methods, systems, and devices for transmitting reports in wireless communication systems are provided.

[0007] In various embodiments, a method for user equipment (UE) in a wireless communication system includes: determining an overlap between a first set of physical uplink control channel (PUCCH) resources for a scheduling request (SR), a second set of PUCCH resources for an indication associated with a UE-initiated (UEI) beam report, and a third set of PUCCH resources for a hybrid automatic repeat request (HARQ); and transmitting HARQ and information to a network node, wherein the information indicates a code point between the first set of PUCCH resources for the SR and the second set of PUCCH resources for the indication. Attached Figure Description

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

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

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

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

[0012] Figure 5 It is in 3GPP TS 38.321 V17.3.0 Figure 6 1.3.47-1: Reproduction of unified TCI state activation / deactivation MACCE.

[0013] Figure 6 It is in 3GPP TS 38.321 V17.3.0 Figure 6 1.3.15-1: Reproduction of TCI status indication for UE-specific PDCCH MAC CE.

[0014] Figure 7 This is an example drawing illustrating timing for Mode A and Mode B according to an embodiment of the present invention, where t1 corresponds to the timing when the UE determines that a certain event condition is met or reached, and t2 corresponds to the timing when the UE transmits a request for UL resources to the network node.

[0015] Figure 8 The accompanying drawings are example drawings illustrating steps 1 and 2, the conditions used, and the results of the UCI multiplexing and / or overlap processing procedures according to embodiments of the present invention.

[0016] Figure 9 The accompanying drawings are example drawings according to embodiments of the present invention, illustrating that a UCI multiplexing procedure may include at least resolving PUCCH overlap and / or resolving PUCCH and PUSCH overlap.

[0017] Figure 10 The accompanying drawings are example drawings according to an embodiment of the present invention, illustrating step 2 of PUCCH2, which is assumed to include mode B of UEI reporting, and the UE has previously transmitted PN on the corresponding UL resource at a predetermined time.

[0018] Figure 11 The accompanying drawings are example drawings according to an embodiment of the present invention, illustrating a possible situation where network nodes may fail to align their understanding of the multiplexed content due to steps 1 and / or 2 (e.g., PUCCH2).

[0019] Figure 12The accompanying drawings are example drawings according to an embodiment of the present invention, illustrating step 2 of PUSCH2, which is assumed to include mode B of UEI reporting, and the UE has previously transmitted PN on the corresponding UL resource at a predetermined time.

[0020] Figure 13 The accompanying drawing is an example drawing according to an embodiment of the present invention, illustrating a second method for PUSCH in step 2.

[0021] Figure 14 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, comprising: maintaining or receiving one or more configurations associated with one or more UE trigger events; receiving one or more configurations for configuring a plurality of UL resources, including at least a first UL resource and a second UL resource; triggering the one event in response to satisfying a condition of one of the one or more UE trigger events; and before a timing associated with the first UL resource (having a processing time), the UE may determine whether to transmit PN and UEI reports on a pair of UL resources (or whether the pair of UL resources for transmitting PN and UEI reports is available or valid) based on whether either the first UL resource or the second UL resource is discarded or downgraded due to overlap with one or more UL resources in the time domain (not reused in either of the one or more UL resources).

[0022] Figure 15 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, including: maintaining or receiving one or more configurations associated with one or more UE trigger events; receiving one or more configurations for configuring a plurality of UL resources, including at least a first UL resource and a second UL resource; triggering the one event in response to satisfying a condition of one of the one or more UE trigger events; and preferably, in some embodiments, determining the priority of a PN (resource) based on a priority value determined by a priority value reported by the corresponding UEI.

[0023] Figure 16 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, comprising: determining one or more first (obtained) channels in response to resolving the overlap of a first plurality of UL channels not associated with an event; determining one or more second (obtained) channels in response to resolving the overlap of a second plurality of UL channels associated with an event; and determining, based on whether to transmit a first PUSCH, a first PUCCH, a second PUSCH and / or a second PUCCH, based on whether PUCCH and PUSCH are transmitted simultaneously.

[0024] Figure 17This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, including resolving the overlap of multiple UL channels, wherein the resolving includes individually determining the resulting channel associated with an event and a UEI report.

[0025] Figure 18 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, including: determining the overlap between a first set of PUCCH resources for SR, a second set of PUCCH resources for an indication associated with UEI beam reporting, and a third set of PUCCH resources for HARQ; and transmitting HARQ and information to a network node. Detailed Implementation

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

[0027] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMAX®, 3GPP New Radio (NR), or some other modulation techniques.

[0028] Specifically, the exemplary wireless communication system apparatus described below can be designed to support one or more standards, such as those provided by an association called the “3rd Generation Partnership Project” (referred to herein as 3GPP), including: [1] 3GPP TS 38.331 V18.1.0 (2024-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Version 18); [2] 3GPP TS 38.214 V17.3.0 (2022-09) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedure for Data (Version 17); [3] 3GPP TS 38.321 V17.3.0 (2022-12) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Media Access Control (MAC) Protocol; [4] Chairman's Notes RAN1#116 eom0; [5] 3GPP TS 38.214 V18.2.0 (2024-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedures for Data (Version 18); [6] 3GPP TS 38.213 V18.3.0 (2024-06) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedures for Control (Version 18); [7] Chair's Note RAN1#116biseom0; [8] 3GPP TS 38.321 V18.1.0 (2024-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Media Access Control (MAC) Protocol Specification (Version 18); [9] 3GPP TS 38.212 V18.2.0 (2024-03) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and Channel Coding (Version 18);

[10] Chair's Note RAN1#117 eom0; and

[11] RAN2#126 meeting minutes. The standards and documents listed above are hereby explicitly and completely incorporated in full.

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

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

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

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

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

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

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

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

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

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

[0039] The RX data processor 260 then uses specific receiver processing technology from N R Each receiver receives and processes N data. R One received symbol stream to provide N TEach detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data of the data stream. The processing performed by the RX 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.

[0040] Processor 270 periodically determines which pre-decoded matrix to use (discussed below). Processor 270 formulates a reverse link message that includes the matrix index portion and the rank portion.

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

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

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

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

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

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

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

[0048] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following invention paragraphs or sections can be implemented independently and separately to form a particular method or apparatus. The dependencies in the following invention disclosure (e.g., "based on," "more specifically," "example," etc.) are merely possible embodiments that do not limit the specific method or apparatus.

[0049] In [1] 3GPP TS 38.331 V18.1.0 (2024-03), the relevant information elements are cited as follows:

[0050] -CSI-AperiodicTriggerStateList

[0051] The CSI-AperiodicTriggerStateList IE is a list used to configure 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], Clause 6.1.3.13). Upon receiving the value associated with the trigger state, the UE will perform CSI-RS, CSI-IM and / or SSB (reference signal) measurements and aperiodic reporting on L1 based on all entries in the associatedReportConfigInfoList for the trigger state.

[0052] CSI-AperiodicTriggerStateList Information Element

[0053] CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState

[0054] CSI-AperiodicTriggerState ::= SEQUENCE {

[0055] associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo,

[0056] ..., [[

[0058] ap-CSI-MultiplexingMode-r17 ENUMERATED {enabled}

[0059] OPTIONAL -- Need R

[0060] ]], [[

[0062] ltm-AssociatedReportConfigInfo-r18 LTM-CSI-ReportConfigId-r18

[0063] OPTIONAL -- Need R ]]

[0065] }

[0066] CSI-AssociatedReportConfigInfo ::= SEQUENCE {

[0067] reportConfigId CSI-ReportConfigId,

[0068] resourcesForChannel CHOICE {

[0069] nzp-CSI-RS SEQUENCE {

[0070] resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),

[0071] qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId

[0072] OPTIONAL -- Cond Aperiodic

[0073] },

[0074] csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)

[0075] },

[0076] … ]]

[0078] }

[0079]

[0080]

[0081] -CSI-MeasConfig

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

[19] , Clause 5.2.

[0083] CSI-MeasConfig information element

[0084] CSI-MeasConfig ::= SEQUENCE {

[0085] nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N

[0086] nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need N

[0087] nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet

[0088] OPTIONAL, -- Need N

[0089] nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId

[0090] OPTIONAL, -- Need N

[0091] …

[0092] csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need N

[0093] csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need N

[0094] csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig

[0095] OPTIONAL, -- Need N

[0096] csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId

[0097] OPTIONAL, -- Need N

[0098] csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need N

[0099] csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId

[0100] OPTIONAL, -- Need N

[0101] reportTriggerSize INTEGER (0..6)

[0102] OPTIONAL, -- Need M

[0103] aperiodicTriggerStateList SetupRelease { CSI-AperiodicTriggerStateList}

[0104] OPTIONAL, -- Need M

[0105] semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList} OPTIONAL, -- Need M

[0106] ..., [[

[0108] reportTriggerSizeDCI-0-2-r16 INTEGER (0..6)

[0109] OPTIONAL -- Need R

[0110] ]], [[

[0112] …

[0113] ltm-CSI-ReportConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ReportConfigurations-r18)) OF LTM-CSI-ReportConfig-r18

[0114] OPTIONAL, -- Need N

[0115] ltm-CSI-ReportConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ReportConfigurations-r18)) OF LTM-CSI-ReportConfigId-r18

[0116] OPTIONAL -- Need N ]]

[0118] }

[0119]

[0120] -CSI-ResourceConfig

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

[0122] CSI-ResourceConfig Information Element

[0123] CSI-ResourceConfig ::= SEQUENCE {

[0124] csi-ResourceConfigId CSI-ResourceConfigId,

[0125] csi-RS-ResourceSetList CHOICE {

[0126] nzp-CSI-RS-SSB SEQUENCE {

[0127] nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId

[0128] OPTIONAL, -- Need R

[0129] csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R

[0130] },

[0131] csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId

[0132] },

[0133] bwp-Id BWP-Id,

[0134] resourceType ENUMERATED { aperiodic, semiPersistent, periodic},

[0135] ..., [[

[0137] csi-SSB-ResourceSetListExt-r17 CSI-SSB-ResourceSetId

[0138] OPTIONAL -- Need R ]]

[0140] }

[0141]

[0142] -CSI-ReportConfig

[0143] IE CSI-ReportConfig is used to configure periodic or semi-static reports containing CSI-ReportConfig to be sent on the PUCCH on a cell, or to configure semi-static or non-periodic reports containing CSI-ReportConfig to be sent on the PUSCH triggered by a DCI received on a cell (in which case the cell sending the report is determined by the received DCI). See TS 38.214

[19] , Clause 5.2.1.

[0144] CSI-ReportConfig Information Elements

[0145] CSI-ReportConfig ::= SEQUENCE {

[0146] reportConfigId CSI-ReportConfigId,

[0147] carrier ServCellIndexOPTIONAL, -- Need S

[0148] resourcesForChannelMeasurement CSI-ResourceConfigId,

[0149] csi-IM-ResourcesForInterference CSI-ResourceConfigIdOPTIONAL, -- Need R

[0150] nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigIdOPTIONAL, -- Need R

[0151] reportConfigType CHOICE {

[0152] periodic SEQUENCE {

[0153] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0154] pucch-CSI-ResourceList SEQUENCE (SIZE(1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0155] },

[0156] semiPersistentOnPUCCH SEQUENCE {

[0157] reportSlotConfig CSI-ReportPeriodicityAndOffset,

[0158] pucch-CSI-ResourceList SEQUENCE (SIZE(1..maxNrofBWPs)) OF PUCCH-CSI-Resource

[0159] },

[0160] semiPersistentOnPUSCH SEQUENCE {

[0161] reportSlotConfig ENUMERATED {sl5, sl10, sl20,sl40, sl80, sl160, sl320},

[0162] reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),

[0163] p0alpha P0-PUSCH-AlphaSetId

[0164] },

[0165] aperiodic SEQUENCE {

[0166] reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)

[0167] }

[0168] },

[0169] reportQuantity CHOICE {

[0170] none NULL,

[0171] cri-RI-PMI-CQI NULL,

[0172] cri-RI-i1 NULL,

[0173] cri-RI-i1-CQI SEQUENCE {

[0174] pdsch-BundleSizeForCSI ENUMERATED {n2, n4}

[0175] OPTIONAL -- Need S

[0176] },

[0177] cri-RI-CQI NULL,

[0178] cri-RSRP NULL,

[0179] ssb-Index-RSRP NULL,

[0180] cri-RI-LI-PMI-CQI NULL

[0181] },

[0182] }

[0183] OPTIONAL, -- Need R

[0184] …

[0185] … ]]

[0187] }

[0188] CSI-ReportPeriodicityAndOffset ::= CHOICE {

[0189] slots4 INTEGER(0..3),

[0190] slots5 INTEGER(0..4),

[0191] slots8 INTEGER(0..7),

[0192] slots10 INTEGER(0..9),

[0193] slots16 INTEGER(0..15),

[0194] slots20 INTEGER(0..19),

[0195] slots40 INTEGER(0..39),

[0196] slots80 INTEGER(0..79),

[0197] slots160 INTEGER(0..159),

[0198] slots320 INTEGER(0..319)

[0199] }

[0200] …

[0201] }

[0202]

[0203]

[0204] -ConfiguredGrantConfig

[0205] The IE ConfiguredGrantConfig is used to configure uplink transmission without dynamic granting based on two possible scenarios. Actual uplink granting can be configured via RRC (Type 1) or provided via PDCCH (Address to CS-RNTI) (Type 2). Multiple configured granting configurations can be configured in a single BWP of the serving cell.

[0206] ConfiguredGrantConfig information element

[0207] ConfiguredGrantConfig ::= SEQUENCE {

[0208] frequencyHopping ENUMERATED {intraSlot, interSlot}

[0209] OPTIONAL, -- Need S

[0210] …

[0211] uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH}

[0212] OPTIONAL, -- Need M

[0213] resourceAllocation ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

[0214] …

[0215] periodicity ENUMERATED {

[0216] sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,

[0217] sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,

[0218] sym640x14, sym1024x14, sym1280x14, sym2560x14,sym5120x14,

[0219] sym6, sym1x12, sym2x12, sym4x12, sym5x12,sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,

[0220] sym40x12, sym64x12, sym80x12, sym128x12,sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,

[0221] sym1280x12, sym2560x12

[0222] },

[0223] configuredGrantTimer INTEGER (1..64)

[0224] OPTIONAL, -- Need R

[0225] rrc-ConfiguredUplinkGrant SEQUENCE {

[0226] timeDomainOffset INTEGER (0..5119),

[0227] timeDomainAllocation INTEGER (0..15),

[0228] frequencyDomainAllocation BIT STRING (SIZE(18)),

[0229] … ]]

[0231] }

[0232] OPTIONAL, -- Need R

[0233] ..., [[

[0235] …

[0236] }

[0237]

[0238]

[0239]

[0240] -NZP-CSI-RS-Resource

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

[19] , Clause 5.2.2.3.1). Configuration changes between periodic, semi-static, and aperiodic configurations of the NZP-CSI-RS-Resource are not supported without release and addition.

[0242] NZP-CSI-RS-Resource Information Element

[0243] NZP-CSI-RS-Resource ::= SEQUENCE {

[0244] nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId,

[0245] resourceMapping CSI-RS-ResourceMapping,

[0246] powerControlOffset INTEGER (-8..15),

[0247] powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6}

[0248] OPTIONAL, -- Need R

[0249] scramblingID (ScramblingId)

[0250] periodicityAndOffset CSI-ResourcePeriodicityAndOffset

[0251] OPTIONAL, -- Cond PeriodicOrSemiPersistent

[0252] qcl-InfoPeriodicCSI-RS TCI-StateId

[0253] OPTIONAL, -- Cond Periodic ...

[0255] }

[0256]

[0257] -NZP-CSI-RS-ResourceSet

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

[0259] NZP-CSI-RS-ResourceSet Information Element

[0260] NZP-CSI-RS-ResourceSet ::= SEQUENCE {

[0261] nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,

[0262] nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,

[0263] repetition ENUMERATED { on, off}

[0264] OPTIONAL, -- Need S

[0265] aperiodicTriggeringOffset INTEGER(0..6)

[0266] OPTIONAL, -- Need S

[0267] trs-Info ENUMERATED {true}

[0268] OPTIONAL, -- Need R

[0269] ..., [[

[0271] aperiodicTriggeringOffset-r16 INTEGER(0..31)

[0272] OPTIONAL -- Need S

[0273] ]], [[

[0275] … ]]

[0277] }

[0278] …

[0279] NZP-CSI-RS-Pairing-r17 ::= SEQUENCE {

[0280] nzp-CSI-RS-ResourceId1-r17 INTEGER (1..7),

[0281] nzp-CSI-RS-ResourceId2-r17 INTEGER (1..7)

[0282] }

[0283]

[0284] …

[0285] PUCCH-Resource ::= SEQUENCE {

[0286] pucch-ResourceId PUCCH-ResourceId,

[0287] startingPRB PRB-Id,

[0288] intraSlotFrequencyHopping ENUMERATED { enabled}

[0289] OPTIONAL, -- Need R

[0290] secondHopPRB PRB-Id

[0291] OPTIONAL, -- Need R

[0292] format CHOICE {

[0293] format0 PUCCH-format0,

[0294] format1 PUCCH-format1,

[0295] format2 PUCCH-format2,

[0296] format3 PUCCH-format3,

[0297] format4 PUCCH-format4

[0298] }

[0299] }

[0300] PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources-1)

[0301] PUCCH-format0 ::= SEQUENCE {

[0302] initialCyclicShift INTEGER(0..11),

[0303] nrofSymbols INTEGER (1..2),

[0304] startingSymbolIndex INTEGER(0..13)

[0305] }

[0306] PUCCH-format1 ::= SEQUENCE {

[0307] initialCyclicShift INTEGER(0..11),

[0308] nrofSymbols INTEGER (4..14),

[0309] startingSymbolIndex INTEGER(0..10),

[0310] timeDomainOCC INTEGER(0..6)

[0311] }

[0312] PUCCH-format2 ::= SEQUENCE {

[0313] nrofPRBs INTEGER (1..16),

[0314] nrofSymbols INTEGER (1..2),

[0315] startingSymbolIndexINTEGER(0..13)

[0316] }

[0317] PUCCH-format3 ::= SEQUENCE {

[0318] nrofPRBs INTEGER (1..16),

[0319] nrofSymbols INTEGER (4..14),

[0320] startingSymbolIndexINTEGER(0..10)

[0321] }

[0322] PUCCH-format4 ::= SEQUENCE {

[0323] nrofSymbols INTEGER (4..14),

[0324] occ-Length ENUMERATED {n2, n4},

[0325] occ-Index ENUMERATED {n0, n1, n2, n3},

[0326] startingSymbolIndexINTEGER(0..10)

[0327] }

[0328] -ServingCellConfig

[0329] The IE ServingCellConfig is used to configure (add or modify) the UE and the serving cell, which can be an SpCell or SCell of an MCG or SCG. The parameters in this document are primarily UE-specific, but some are also cell-specific (e.g., in the bandwidth section of a separate configuration). Only SCells are used to release and add reconfiguration between SCells supporting PUCCH and those without PUCCH.

[0330] ServingCellConfig information element

[0331] ServingCellConfig ::= SEQUENCE {

[0332] …

[0333] csi-MeasConfig SetupRelease { CSI-MeasConfig}

[0334] OPTIONAL, -- Need M

[0335] …

[0336] -SchedulingRequestConfig

[0337] The IE SchedulingRequestConfig is used to configure parameters for dedicated scheduling request (SR) resources.

[0338] SchedulingRequestConfig information element

[0339] SchedulingRequestConfig ::= SEQUENCE {

[0340] schedulingRequestToAddModList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod

[0341] OPTIONAL, -- Need N

[0342] schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId

[0343] OPTIONAL -- Need N

[0344] }

[0345] SchedulingRequestToAddMod ::= SEQUENCE {

[0346] schedulingRequestId SchedulingRequestId,

[0347] sr-ProhibitTimer ENUMERATED {ms1, ms2, ms4, ms8,ms16, ms32, ms64, ms128} OPTIONAL, -- Need S

[0348] sr-TransMax ENUMERATED { n4, n8, n16, n32,n64, spare3, spare2, spare1}

[0349] }

[0350] SchedulingRequestConfig-v1700 ::= SEQUENCE {

[0351] schedulingRequestToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddModExt-v1700

[0352] OPTIONAL -- Need N

[0353] }

[0354] SchedulingRequestToAddModExt-v1700 ::= SEQUENCE {

[0355] sr-ProhibitTimer-v1700 ENUMERATED { ms192, ms256,ms320, ms384, ms448, ms512, ms576, ms640, ms1082, spare7, spare6, spare5,spare4, spare3, spare2, spare1}

[0356] OPTIONAL -- Need R

[0357] }

[0358]

[0359]

[0360] -SchedulingRequestId

[0361] The IE SchedulingRequestId is used to identify the scheduling request instance in the MAC layer.

[0362] -SchedulingRequestResourceConfig

[0363] IE SchedulingRequestResourceConfig determines the physical layer resources on the PUCCH on which the UE can send a dedicated scheduling request (D-SR) (see TS 38.213

[13] , Clause 9.2.4).

[0364] SchedulingRequestResourceConfig information element

[0365] SchedulingRequestResourceConfig ::= SEQUENCE {

[0366] schedulingRequestResourceId SchedulingRequestResourceId,

[0367] schedulingRequestID SchedulingRequestId,

[0368] periodicityAndOffset CHOICE {

[0369] sym2 NULL,

[0370] sym6or7 NULL,

[0371] sl1 NULL, -- Recurs in every slot

[0372] sl2 INTEGER (0..1),

[0373] sl4 INTEGER (0..3),

[0374] sl5 INTEGER (0..4),

[0375] sl8 INTEGER (0..7),

[0376] sl10 INTEGER (0..9),

[0377] sl16 INTEGER (0..15),

[0378] sl20 INTEGER (0..19),

[0379] sl40 INTEGER (0..39),

[0380] sl80 INTEGER (0..79),

[0381] sl160 INTEGER (0..159),

[0382] sl320 INTEGER (0..319),

[0383] sl640 INTEGER (0..639)

[0384] }

[0385] OPTIONAL, -- Need M

[0386] resource PUCCH-ResourceId

[0387] OPTIONAL -- Need M

[0388] }

[0389] SchedulingRequestResourceConfigExt-v1610 ::= SEQUENCE {

[0390] phy-PriorityIndex-r16 ENUMERATED {p0, p1}

[0391] OPTIONAL, -- Need M ...

[0393] }

[0394] …

[0395] }

[0396]

[0397]

[0398] In [2] 3GPP TS 38.214 V17.3.0 (2022-09), the relevant paragraphs on TCI status are quoted as follows:

[0399] 5.1.5 Quasi-co-addressable antenna ports

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

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

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

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

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

[0405] The UE can be configured with a list of up to 128 TCIState configurations in the higher-layer parameter dl-OrJoint-TCIStateList in PDSCH-Config, which are used to provide quasi-co-address reference signals for the DM-RS of PDSCH and DM-RS of PDCCH in CC and for CSI-RS, and, where applicable, to provide references for determining the UL TX spatial filters for PUSCH and PUCCH resources in CC based on dynamic and configuration-approved grants and for SRS.

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

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

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

[0409] …

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

[0411] If the UE receives a higher-layer configuration of a dl-OrJoint-TCIStateList that can be used as the indicated TCI state, the UE determines the UL TX spatial filter from the configured TCI state used for dynamically granted and configured granted PUSCH and PUCCH and the SRS that applies the indicated TCI state, where applicable.

[0412] When a UE transmits a PUCCH or PUSCH with HARQ-ACK information that corresponds to a DCI bearing a TCI state indication but does not have a DL assignment, or a PDSCH corresponding to a DCI scheduled by a DCI bearing a TCI state indication, and if the indicated TCI state differs from a previously indicated TCI state, then at least [the following should be noted] after the last symbol of the PUCCH or PUSCH. The first time slot of each symbol begins to apply the indicated DLorJointTCIState or UL-TCIState. The first time slot is determined on the active BWP with the smallest SCS among the active BWPs of the applied beam-indicating carriers. A symbol.

[0413] …

[0414] When the UE supports two TCI states in the code point of the 'Transmission Configuration Indicator' field of the DCI, the UE may receive an activation command, as described in Clause 6.1.3.24 of [10, TS 38.321], which maps up to eight combinations of one or two TCI states to the code point of the 'Transmission Configuration Indicator' field of the DCI. The UE does not expect to receive more than eight TCI states in the activation command.

[0415] …

[0416] When the UE transmits a PUCCH with HARQ-ACK information in time slot n, which corresponds to the PDSCH carrying the activation command, it should start from time slot n. The first time slot thereafter begins applying the mapping between the TCI status and code points indicated in the DCI field 'Transmission Configuration Indication', where μ is the SCS configuration of the PUCCH. yes The subcarrier spacing configuration is set to 0 for frequency range 1. Provided by K-Mac, or if K-Mac is not available, then If tci-PresentInDCI is set to 'Enabled' or tci-PresentDCI-1-2 is configured for the CORESET of the PDSCH scheduling, and the time offset between the reception of 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 receiving the activation command, for qcl-Type set to 'typeA', and, where applicable, for qcl-Type set to 'typeD', the UE may assume that the DM-RS port of the serving cell's PDSCH is quasi-co-located with the SS / PBCH block determined during the initial access process.

[0417] If the UE is configured to use the higher-layer parameter tci-PresentInDCI with CORESET set to 'Enabled' for scheduling PDSCH, the UE assumes that the TCI field exists in DCI format 1_1 of the PDCCH transmitted on the CORESET. If the UE is configured to use the higher-layer parameter tci-PresentDCI-1-2 with CORESET for scheduling PDSCH, the UE assumes that the TCI field with the DCI field size indicated by tci-PresentDCI-1-2 exists in DCI format 1_2 of the PDCCH transmitted on the CORESET. If the UE is configured to use the higher-layer parameter tci-PresentInDCI with CORESET set to 'Enabled' for scheduling multicast PDSCH, the UE assumes that the TCI field exists in DCI format 4_2 of the PDCCH transmitted on the CORESET. If PDSCH is scheduled via a DCI format that does not have a TCI field, and the time offset between the reception of DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL (if applicable), where the threshold is based on the reported UE capability [13, TS 38.306], in order to determine the PDSCH antenna port quasi-co-address, the UE assumes that the TCI state or QCL assumption for PDSCH is the same as the TCI state or QCL assumption applied to the CORESET for PDCCH transmission within the BWP of the serving cell (whichever is correct).

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

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

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

[0421] 5.2.1.4.3 L1-RSRP Report

[0422] For L1-RSRP calculation

[0423] - Where applicable, when quasi-co-located with 'typeC' and 'typeD' per resource, the UE can be configured to use CSI-RS resources, SS / PBCH block resources, or both CSI-RS and SS / PBCH block resources.

[0424] - The UE can be configured to use CSI-RS resource settings with up to 16 CSI-RS resource sets, each with up to 64 resources. The total number of distinct CSI-RS resources across all resource sets does not exceed 128.

[0425] For L1-RSRP reporting, if the higher-layer parameter nrofReportedRS in CSI-ReportConfig is configured to one, the reported L1-RSRP value is defined by a 7-bit value within a range of [-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, the UE should use differential L1-RSRP reporting, where the maximum measured L1-RSRP value is quantized into a 7-bit value within a range of [-140, -44] dBm with a step size of 1 dB, and the differential L1-RSRP is quantized into a 4-bit value. The differential L1-RSRP value is calculated with a 2 dB step size, referencing the maximum measured L1-RSRP value that is part of the same L1-RSRP reporting example. The mapping between the reported L1-RSRP values ​​and the measured quantities is described in [11, TS38.133].

[0426] The following is provided in [3] 3GPP TS 38.321 V17.3.0 (2022-12):

[0427] 6.1.3.47 Unified TCI Status Activation / Deactivation MAC CE

[0428] The Unified TCI Status Activation / Deactivation MAC CE is identified by a MAC subheader with the eLCID as specified in Table 6.2.1-1b. It is of variable size and consists of the following fields:

[0429] -Serving Cell ID: This field indicates the identifier of the serving cell in which MAC CE is applied. The field length 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;

[0430] -DL BWP ID: This field indicates the DL BWP of the code point used by the MAC CE as the DCI bandwidth section indicator field, as specified in TS 38.212[9]. The length of the BWP ID field is 2 bits;

[0431] -UL BWP ID: This field indicates the UL BWP of the code point used by the MAC CE as the DCI bandwidth portion indicator field, as specified in TS 38.212[9]. If the value of the unifiedTCI-StateType of the serving cell indicated by the serving cell ID is unionized, then this field is considered reserved. The length of the BWP ID field is 2 bits;

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

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

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

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

[0436] Figure 5 It is in 3GPP TS 38.321 V17.3.0 Figure 6 1.3.47-1: Reproduction of unified TCI state activation / deactivation MACCE.

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

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

[0439] -Serving Cell ID: This field indicates the identifier of the serving cell for the MAC C application. The field is 5 bits long. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells configured in the sets simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 respectively;

[0440] -CORESET ID: This field indicates the control resource set identified by ControlResourceSetId as specified in TS 38.331[5], where TCI status is indicated. When the value of this field is 0, it refers to the control resource set configured as specified in controlResourceSetZero as specified in TS38.331[5]. This field is 4 bits long;

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

[0442] Figure 6 It is in 3GPP TS 38.321 V17.3.0 Figure 6 1.3.15-1: Reproduction of TCI status indication for UE-specific PDCCH MAC CE.

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

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

[0445] ● Trigger event detection for beam reporting performed by the UE

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

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

[0448] ● Beam report transmission performed by the UE

[0449] - Signaling content in the beam report

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

[0451] ●MAC-CE

[0452] ●UCI

[0453] ●Others cannot be excluded.

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

[0455] ●UE requests UL resources for beam reporting

[0456] ● UE notification beam report transmission

[0457] ●gNB pre-configured resources

[0458] Regarding UE-initiated / event-driven beam reporting, RAN1 further investigates at least the following aspects related to trigger event detection for beam reporting: quality metrics, event definitions, and thresholds.

[0459] - Further research into triggering events, using the following examples as a starting point.

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

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

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

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

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

[0465] -Note: Measurement results may be included in beam reports and / or used as quality metrics for initiating / triggering reports.

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

[0467] The following is provided in [5] 3GPP TS 38.214 V18.2.0 (2024-03):

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

[0469] 5.2.1 Channel State Information Framework

[0470] The procedures for non-periodic CSI reporting described in this clause assume that CSI reports are triggered by DCI format 0_1, but they also apply to CSI reports triggered by DCI format 0_2 by applying the higher-level parameter reportTriggerSizeDCI-0-2 instead of reportTriggerSize. The procedures for non-periodic CSI reporting described in this clause assume that CSI reports are triggered by DCI format 0_1, but they also apply to CSI reports triggered by DCI format 0_3.

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

[0472] For CQI, PMI, CRI, SSBRI, L1, RI, L1-RSRP, L1-SINR, CapabilityIndex, and TDCP, the UE is configured by a higher layer with N ≥ 1 CSI-ReportConfig settings and / or [X ≥ 1 LTM-CSI-ReportConfig settings], M ≥ 1 CSI-ResourceConfig settings and / or [Y ≥ 1 LTM-CSI-ResourceConfig 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 or LTM-CSI-ReportConfigs indicating the resource set IDs used for the channel and optionally for interference, wherein the resource set for interference exists only for 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-ReportSubConfigIDs], as described in Clause 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-ReportSubConfigIDs], as described in Clause 5.2.1.1.

[0473] 5.2.1.1 Report Setup

[0474] Each report setting CSI-ReportConfig is associated with a single downlink BWP (indicated by the higher-layer parameter BWP-Id) given in the associated CSI-ResourceConfig used for channel measurements and contains parameters for a CSI reporting band: codebook configuration including codebook subset restrictions, time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configuration, and 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.

[0475] …

[0476] The time-domain behavior of CSI-ReportConfig is indicated by the higher-level 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 underlying parameters of the UL BWP on which the CSI report is configured to be transmitted. The higher-level parameter reportQuantity indicates the amount of CSI-related, L1-RSRP-related, L1-SINR-related, CapabilityIndex-related, or TDCP-related quantities to be reported. reportFreqConfiguration indicates the reporting granularity in the frequency domain, including the CSI reporting band and whether the PMI / CQI report is wideband or subband. The timeRestrictionForChannelMeasurements parameter in CSI-ReportConfig can be configured to enable time-domain restriction for channel measurements, and timeRestrictionForInterferenceMeasurements can be configured to enable time-domain restriction for interference measurements. … It is not expected that the UE will be configured to use a mixed CSI-ReportConfig containing a list of sub-configurations, each corresponding to one or more CSI-RS resources, and some other sub-configurations, each corresponding to a subset of CSI-RS antenna ports.

[0477] …

[0478] 5.2.1.2 Resource Settings

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

[0480] The temporal behavior of CSI-RS resources within a CSI resource setting is indicated by the higher-level parameter `resourceType` and can be set to aperiodic, periodic, or semi-static. … For periodic and semi-static CSI resource settings, the configured periodicity and slot offset are given in the underlying parameters of its associated DL BWP, which is given by the BWP-id. When a UE is configured to use multiple CSI-ResourceConfigs that make up the same NZP CSI-RS resource ID, the same temporal behavior should be configured for the CSI-ResourceConfigs. … All CSI resource settings linked to a CSI reporting setting should have the same temporal behavior.

[0481] …

[0482] 5.2.3 Using PUSCH's CSI Report

[0483] After successfully decoding either DCI format 0_1 ​​or DCI format 0_2 that triggers the aperiodic CSI trigger state, the UE should use PUSCH to perform an aperiodic CSI report on serving cell c. The UE should use PUSCH to perform an aperiodic CSI report on the serving cell with the minimum serving cell index scheduled by DCI format 0_3, thereby triggering the aperiodic CSI trigger state.

[0484] When DCI format 0_1 ​​schedules two PUSCH allocations, the aperiodic CSI report is carried on the second scheduled PUSCH. When DCI format 0_1 ​​schedules more than two PUSCH allocations, the aperiodic CSI report is carried on the penultimate scheduled PUSCH.

[0485] The non-periodic CSI reports carried on the PUSCH support both wideband and subband frequency granularity.

[0486] …

[0487] CSI reports on the PUSCH can be multiplexed with uplink data on the PUSCH, but semi-static CSI reports on the PUSCH activated by the DCI format are not expected to be multiplexed with uplink data on the PUSCH. CSI reports on the PUSCH can also be performed without any multiplexing with uplink data from the UE.

[0488] …

[0489] When the higher-level parameter reportQuantity is configured with one of the values ​​'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP-Index', 'ssb-Index-RSRP-Index', 'cri-SINR-Index', 'ssb-Index-SINR-Index', or 'tdcp', the CSI feedback consists of a single part.

[0490] When the CSI report on the PUSCH consists of two parts, the UE may omit part 2 of the CSI. The omission of part 2 of the CSI is based on the priority order shown in Table 5.2.3-1, where... This is the number of CSI reports configured to be carried on the PUSCH. Priority 0 is the highest priority. It is the lowest priority, and CSI report n corresponds to Among the CSI reports, the nth smallest Pri i，CSI CSI reports with values ​​of (y, k, c, s) are defined as in Clause 5.2.5. Subbands of a given CSI report n, indicated by the higher-layer parameter csi-ReportingBand with a value of '1', are numbered sequentially in ascending order, where the lowest subband of the csi-ReportingBand with a value of '1' is subband 0. When part 2 CSI information is omitted for a specific priority, the UE shall omit all information for that priority, except for part 2 subband CSIs when the corresponding CSI report contains one or more CSI subreports, where each part 2 corresponds to a subconfiguration in the subconfiguration list provided by csi-ReportSubConfigList contained in CSI-ReportConfig, as described in Clause 5.2.1.1.

[0491] The following is provided in [6] 3GPP TS 38.213 V18.3.0 (2024-06):

[0492] 9. UE program for reporting control information

[0493] …

[0494] When a UE determines that a PUCCH and / or PUSCH transmission with the same priority index, other than a PUCCH transmission, overlaps with an SL HARQ-ACK report before considering UE transmission restrictions described in clauses 11.1, 11.1.1, 11.2A, 15, and 17.2 (including duplicates, if any), prior to considering cell DRX operations [11, TS 38.321] or the UE transmission restrictions described in clauses 11.1, 11.1.1, 11.2A, 15, and 17.2 (including duplicates, if any),

[0495] - First, the UE resolves PUCCH overlap in cases where there are duplicates as described in Clause 9.2.6 (if any).

[0496] - Second, the UE resolves PUCCH overlap in the absence of duplication as described in Clause 9.2.5.

[0497] - Third, the UE resolves overlaps between PUSCH and PUCCH in cases of duplication as described in Clause 9.2.6.

[0498] - Fourth, the UE, as described in the following clause, resolves the overlap of PUSCH and PUCCH in the absence of duplication.

[0499] …

[0500] If UE

[0501] - A simultaneous PUCCH-PUSCH is provided, and a PUCCH with a first priority index and a PUSCH with a second priority index different from the first priority index will be transmitted, wherein the PUCCH and PUSCH overlap in time in different cells.

[0502] - It can simultaneously transmit PUCCH and PUSCH [18, TS 38.306] with different priority indices.

[0503] The UE excludes PUSCHs used to resolve time overlaps between PUCCHs and PUSCHs with different priority indices, wherein the excluded PUSCHs do not need to meet the timeline conditions for resolving PUCCH and PUSCH overlaps.

[0504] If UE

[0505] - It is provided with simultaneous PUCCH-PUSCH-Same Priority and will transmit PUCCH and PUSCH with the same priority index, where PUCCH and PUSCH overlap in time in different cells.

[0506] - It can transmit PUCCH and PUSCH [18, TS 38.306] with the same priority index simultaneously.

[0507] The UE excludes PUSCHs used to resolve time overlaps between PUCCHs and PUSCHs with the same priority index, wherein the excluded PUSCHs do not need to meet the timeline conditions for resolving PUCCH and PUSCH overlaps.

[0508] …

[0509] If the UE is to transmit a PUSCH that does not have a UL-SCH that overlaps with the PUCCH transmission on the serving cell containing positive SR information, then the UE will not transmit the PUSCH.

[0510] If the UE will transmit CSI reports on overlapping physical channels, the UE applies the priority rules described in [6, TS 38.214] for multiplexing CSI reports.

[0511] If UE

[0512] - UCI will be multiplexed in PUCCH transmissions that overlap with PUSCH transmissions, and

[0513] -PUSCH and PUCCH transmissions satisfy the conditions for UCI multiplexing in Clause 9.2.5.

[0514] UE

[0515] - If the UE reuses aperiodic or semi-static CSI reports in the PUSCH, it only reuses the HARQ-ACK information from the UCI transmitted in the PUSCH (if it exists) and does not transmit the PUCCH.

[0516] - If the UE does not reuse aperiodic or semi-static CSI reports in the PUSCH, it only reuses HARQ-ACK information and CSI reports (if present) from the UCI transmitted in the PUSCH, and does not transmit the PUCCH.

[0517] …

[0518] If the UE multiplexes the non-periodic CSI in the PUSCH and the UE multiplexes the UCI containing HARQ-ACK information in the PUCCH that overlaps with the PUSCH, and the timing conditions for overlapping PUCCH and PUSCH in Clause 9.2.5 are met, then the UE only multiplexes the HARQ-ACK information in the PUSCH and does not transmit the PUCCH.

[0519] …

[0520] If the UE transmits a PUSCH on one or more time slots scheduled by the DCI format, or transmits multiple PUSCHs on one or more time slots, and the UE transmits a PUCCH with HARQ-ACK and / or CSI information on a single time slot overlapping with the PUSCH transmissions in the one or more time slots, and the PUSCH transmissions in the one or more time slots satisfy the conditions for multiplexing HARQ-ACK and / or CSI information in Clause 9.2.5, then the UE multiplexes the HARQ-ACK and / or CSI information in the PUSCH transmissions in the one or more time slots. If the UE does not transmit a single-slot PUCCH with HARQ-ACK and / or CSI information in a time slot in the one or more time slots in the absence of PUSCH transmissions, then the UE does not multiplex the HARQ-ACK and / or CSI information in the PUSCH transmissions in that time slot.

[0521] …

[0522] When a UE multiplexes HARQ-ACK information in a PUSCH transmission configured by ConfiguredGrantConfig and containing CG-UCI [5, TS 38.212], if the UE is provided with cg-UCI-Multiplexing, then the UE multiplexes HARQ-ACK information in the PUSCH transmission; otherwise, if the HARQ-ACK information and the PUSCH have the same priority index, then the UE does not transmit the PUSCH and multiplexes HARQ-ACK information in the PUCCH transmission or another PUSCH transmission; if the HARQ-ACK information and the PUSCH have different priority indices, then the UE does not transmit the channel with the lower priority index.

[0523] In the following text, a DCI format with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI is also referred to as a unicast DCI format, and a DCI format with a CRC scrambled by multicast-MCCH-RNTI, G-RNTI for multicast, or G-CS-RNTI is also referred to as a multicast DCI format. The corresponding unicast DCI format is DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2, and the multicast DCI format is DCI format 4_0 / 4_1 / 4_2 [4, TS 38.212]. PDSCH reception scheduled by unicast or multicast DCI format is referred to as unicast or multicast PDSCH reception. HARQ-ACK information associated with the unicast or multicast DCI format used for PDCCH reception in the RRC_CONNECTED state is also referred to as unicast or multicast HARQ-ACK information, respectively.

[0524] 9.2.2 PUCCH Format for UCI Transmission

[0525] If the UE is not transmitting PUSCH but is transmitting UCI, then the UE uses the following items to transmit UCI in PUSCH.

[0526] -PUCCH format 0, provided that

[0527] - The transmission is on one or two symbols.

[0528] - The number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is 1 or 2.

[0529] -PUCCH format 1, provided that

[0530] - The transmission is on 4 or more symbols.

[0531] The number of HARQ-ACK / SR bits is 1 or 2.

[0532] -PUCCH format 2, provided that

[0533] - The transmission is on one or two symbols.

[0534] - The number of UCI bits is greater than 2

[0535] -PUCCH format 3, provided that

[0536] - The transmission is on 4 or more symbols.

[0537] - The number of UCI bits is greater than 2.

[0538] - The PUCCH resource does not contain orthogonal overlay code, or UEBWP-UplinkDedicated is provided with useInterlacePUCCH-PUSCH.

[0539] -PUCCH format 4, provided that

[0540] - The transmission is on 4 or more symbols.

[0541] - The number of UCI bits is greater than 2.

[0542] - The PUCCH resource contains orthogonal coverage codes, and the UE is not provided with useInterlacePUCCH-PUSCH in BWP-UplinkDedicated.

[0543] …

[0544] 9.2.3 UE Procedure for Reporting HARQ-ACK

[0545] …

[0546] If the UE uses PUCCH format 0 to transmit a PUCCH with HARQ-ACK information, then the UE determines the value. and To calculate cyclic shift [4, TS 38.211], where Provided by `initialCyclicShift` of `PUCCH-format0`, or, if `initialCyclicShift` is not provided, by the initial cyclic shift index described in Clause 9.2.1. It is determined by the value of one HARQ-ACK information bit or the value of two HARQ-ACK information bits, as shown in Tables 9.2.3-3 and 9.2.3-4, respectively.

[0547] Table 9.2.3-3: Mapping of a HARQ-ACK bit value to a sequence of PUCCH format 0 bits

[0548]

[0549] Table 9.2.3-4: Mapping of the values ​​of the two HARQ-ACK information bits to the sequence of PUCCH format 0

[0550]

[0551] If the UE transmits a PUCCH with HARQ-ACK information using PUCCH format 1, then the UE is provided with initial CyclicShift by PUCCH-format 1. The value is provided by the initial cyclic shift index if no initialCyclicShift is provided, as described in Clause 9.2.1.

[0552] …

[0553] 9.2.4 UE Procedure for Reporting SR

[0554] The UE can be provided with a set of configurations for SR by SchedulingRequestResourceConfig in PUCCH transmission using PUCCH format 0 or PUCCH format 1.

[0555] The UE can be configured for LRR by schedulingRequestID-BFR-SCell during PUCCH transmission using PUCCH format 0 or PUCCH format 1.

[0556] The UE can be provided with a first configuration for LRR by schedulingRequestID-BFR, and if the UE provides two LRR capabilities, the UE can be provided with a second configuration for LRR by schedulingRequestID-BFR2 in PUCCH transmission using PUCCH format 0 or PUCCH format 1.

[0557] The UE may be configured for consistent LBT fault recovery in PUCCH transmissions using PUCCH format 0 or PUCCH format 1, as described in [11, TS 38.321]. The UE may be provided with a priority index 0 or priority index 1 for the SR by the phy-PriorityIndex in the SchedulingRequestResourceConfig. If the UE is not provided with a priority index for the SR, the priority index is 0.

[0558] For PUCCH transmissions used to transmit SRs, the UE is also provided with a periodicity or slot period by periodicityAndOffset. and offset in time slots .if More than one time slot, and satisfying Then the UE will determine the timing of SR transmission in PUCCH as being in the number Frame numbering In the time slot [4, TS 38.211].

[0559] if If it is a time slot, then the UE expects... Furthermore, each time slot is a SR transmission opportunity in PUCCH.

[0560] if Less than one time slot, and satisfying Then the UE determines the SR transmission timing in the PUCCH from the index. The symbol begins [4, TS 38.211], where It is the value of startingSymbolIndex.

[0561] If the UE determines that, for the SR transmission timing in the PUCCH, the number of symbols available for PUCCH transmission in the time slot is less than the value provided by nrofSymbols, then the UE will not transmit the PUCCH in the time slot.

[0562] The timing of SR transmissions in the PUCCH is subject to UE transmission restrictions as described in Clauses 11.1, 11.1.1 and 17.2.

[0563] Only when the UE transmits a positive SR, the UE transmits the PUCCH in the PUCCH resource configured for the corresponding SR. For positive SR transmissions using PUCCH format 0, the UE, as described in [4, TS 38.211], obtains... (As described in section 9.2.3 regarding HARQ-ACK information) and set To transmit PUCCH. For positive SR transmission using PUCCH format 1, the UE, as described in [4, TS 38.211], sets... To transmit PUCCH.

[0564] …

[0565] 9.2.5.1 UE procedure for multiplexing HARQ-ACK or CSI and SR in PUCCH

[0566] In the following text, the UE is configured to transmit in a time slot for the corresponding SR A PUCCH, as determined by a set of schedulingRequestResourceIds, a schedulingRequestResourceId associated with schedulingRequestID-BFR-SCell, a schedulingRequestResourceId associated with schedulingRequestID-BFR, a schedulingRequestResourceId associated with schedulingRequestID-BFR2 (if the UE provides twoLRR capabilities), and a schedulingRequestResourceId associated with schedulingRequestID-LBT-SCell, wherein the timing of SR transmission will overlap with the transmission of a PUCCH with HARQ-ACK information from the UE in the time slot or with the transmission of a PUCCH with CSI report from the UE in the time slot.

[0567] If the UE intends to transmit a PUCCH with a positive SR and at most two HARQ-ACK information bits in a resource using PUCCH format 0, then the UE transmits the PUCCH in the PRB used for HARQ-ACK information in a resource using PUCCH format 0, as described in clause 9.2.3. The UE determines... and The value of is used to calculate the cyclic shift. The value is [4, TS 38.211], where Provided by initialCyclicShift of PUCCH-format0 It is determined by the value of one HARQ-ACK information bit or the value of two HARQ-ACK information bits, as shown in Tables 9.2.5-1 and 9.2.5-2, respectively.

[0568] If the UE will transmit a negative SR and a PUCCH with at most two HARQ-ACK information bits in a resource using PUCCH format 0, then the UE will transmit the PUCCH in a resource using PUCCH format 0 for HARQ-ACK information, as described in Clause 9.2.3.

[0569] Table 9.2.5-1: Mapping of the value of a HARQ-ACK information bit and a positive SR to the sequence used for PUCCH format 0

[0570]

[0571] Table 9.2.5-2: Mapping of the values ​​of the two HARQ-ACK information bits and the positive SR to the sequence used for PUCCH format 0.

[0572]

[0573] If the UE will transmit SR in a time slot using PUCCH format 0 and transmit HARQ-ACK information bits in a time slot using PUCCH format 1, then the UE will only transmit PUCCH with HARQ-ACK information bits in the PUCCH format 1 resource.

[0574] If the UE will transmit a positive SR in a first resource using PUCCH format 1 and transmit at most two HARQ-ACK information bits in a second resource using PUCCH format 1 within a time slot, then the UE will transmit a PUCCH with HARQ-ACK information bits in the first resource using PUCCH format 1, as described in clause 9.2.3. If the UE will not transmit a positive SR in a resource using PUCCH format 1 within a time slot and will transmit at most two HARQ-ACK information bits in a resource using PUCCH format 1, then the UE will transmit a PUCCH for HARQ-ACK information in a resource using PUCCH format 1, as described in clause 9.2.3.

[0575] If the UE uses PUCCH format 2, PUCCH format 3, or PUCCH format 4 in a time slot to transmit data with... The PUCCH of the HARQ-ACK information bits, as described in Clauses 9.2.1 and 9.2.3, indicates a negative SR or a positive SR. The last digit, ordered in ascending order of the values ​​of schedulingRequestResourceId, schedulingRequestResourceId associated with schedulingRequestID-BFR-SCell, schedulingRequestResourceId associated with schedulingRequestID-BFR, schedulingRequestResourceId associated with schedulingRequestID-BFR2 (if the UE provides twoLRR capability), and schedulingRequestResourceId associated with schedulingRequestID-LBT-SCell, is appended to the HARQ-ACK information bits, and the UE uses a resource transmission combination in the PUCCH with PUCCH format 2, PUCCH format 3, or PUCCH format 4 as determined by the UE as described in clauses 9.2.1 and 9.2.3. One UCI bit. If one of the SRs is a positive LRR, then The unit digit indicates a positive LRR. If If the units digit is all zeros, then it means all The SR value of each SR is negative.

[0576] If the UE uses PUCCH format 2, PUCCH format 3, or PUCCH format 4 in a time slot to transmit data with... A PUCCH with one CSI report bit will represent the corresponding negative or positive SR. The last digit, ordered in ascending order of the values ​​of schedulingRequestResourceId, schedulingRequestResourceId associated with schedulingRequestID-BFR-SCell, schedulingRequestResourceId associated with schedulingRequestID-BFR, schedulingRequestResourceId associated with schedulingRequestID-BFR2 (if the UE provides twoLRR capability), and schedulingRequestResourceId associated with schedulingRequestID-LBT-SCell, is added before the CSI information bits, as described in Clause 9.2.5.2, and the UE transmits the combined data in the resource using PUCCH format 2, PUCCH format 3, or PUCCH format 4. The PUCCH with one UCI bit is used for CSI reporting. If one of the SRs is a positive LRR, then The unit digit indicates a positive LRR. If If the units digit is all zero, it means that all... The SR value of each SR is negative.

[0577] If the UE is included The PUCCH resource of a PRB uses PUCCH format 2 or PUCCH format 3 to transmit data with... One HARQ-ACK bit, SR bits and If the PUCCH has CRC bits, the UE determines the number of PRBs transmitted via the PUCCH. The minimum number of PRBs is less than or equal to the number of PRBs provided by nrofPRBs in PUCCH-format2 or nrofPRBs in PUCCH-format3, and starts from the first PRB of said number of PRBs, such that... And if but, ,in , , and As specified in Clause 9.2.5.2. For PUCCH format 3, if in accordance with [4, TS38.211], Not equal to ,but Increase to the closest allowed value for nrofPRBs [12, TS 38.331]. If Then the UE passes Each PRB transmits a PUCCH.

[0578] If in InterlaceAllocation, interlace0 provides the UE with The first interleaving of the PRB, and transmission using PUCCH format 2 or PUCCH format 3 with... One HARQ-ACK bit, SR bits and A PUCCH with CRC bits, if it satisfies If interlace 1 in PUCCH-format2 or PUCCH-format3 provides a second interlace for the UE, then the UE transmits the PUCCH through the first interlace; otherwise, if interlace 1 in PUCCH-format2 or PUCCH-format3 provides a second interlace for the UE, then the UE transmits the PUCCH through the first and second interlaces.

[0579] …

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0599] ●FFS: Does the network control how L1-RSRP is used to determine triggering events?

[0600] - Regarding the RS measurement for the new beam used in Event 2, select one or more of the following items below:

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

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

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

[0604] -Note 1: 'New / Current Beam' is used for discussion purposes.

[0605] -Note 2: Other triggering events / quality metrics (e.g., L1-SINR) are not excluded.

[0606] -Note 3: For the above implicit method, if there are two QCL RS in the TCI state, the measured RS is derived from the RS relative to QCL-TypeD (if applicable).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0622] The following is provided in [9] 3GPP TS 38.212 V18.2.0 (2024-03):

[0623] 7.3.1 DCI Format

[0624] Supports the DCI format defined in Table 7.3.1-1.

[0625] …

[0626] Table 7.3.1-1: DCI Format

[0627]

[0628] …

[0629] 7.3.1.1.2 Format 0_1

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

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

[0632] -DCI format identifier--1 bit

[0633] - This field is always set to 0, indicating UL DCI format.

[0634] -Carrier Indicator--0 or 3 bits, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when the format is carried by the PDCCH on the primary cell and the UE is configured for scheduling from the SCell on the primary cell, and has the same number of bits as the PDCCH carried by the SCell in the format for scheduling in the primary cell.

[0635] …

[0636] -Bandwidth component indicator--such as the number of UL BWPs configured by higher layers The specified 0, 1, or 2 bits do not include the initial UL bandwidth portion. The bit width of this field is determined as follows. Position, among which

[0637] …

[0638] -Frequency domain resource allocation--The number of bits is determined by the following, where It refers to the size of the UL bandwidth portion during operation:

[0639] …

[0640] -CSI Request--0, 1, 2, 3, 4, 5, or 6 bits determined by the higher-level parameter reportTriggerSize.

[0641] …

[0642] 7.3.1.2.2 Format 1_1

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

[0644] The following information is transmitted using DCI format 1_1 with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI:

[0645] -DCI format identifier--1 bit

[0646] - This field is always set to 1, indicating DL DCI format.

[0647] -Carrier Indicator--0 or 3 bits, as defined in Clause 10.1 of [5, TS 38.213]. This field is reserved when the format is carried by the PDCCH on the primary cell and the UE is configured for scheduling from the SCell on the primary cell, and has the same number of bits as the PDCCH carried by the SCell in the format for scheduling in the primary cell.

[0648] -Bandwidth component indicator--such as the number of DL BWPs configured by higher layers The specified 0, 1, or 2 bits do not include the initial DL bandwidth portion. The bit width of this field is determined as follows. Position, among which

[0649] …

[0650] -The number of bits for frequency domain resource allocation is determined by the following, where It refers to the size of the DL bandwidth portion during operation:

[0651] …

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

[0653] …

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

[0655] …

[0656] In Chairman’s Notes RAN1#117 eom0 of

[10] , the 3GPP progress related to the UEI beam report is cited as follows:

[0657] Regarding UE-initiated / event-driven beamforming reports, and the UL signaling content of L1-RSRP reports dependent on event 2, at least option 3 should be supported in the reporting instance.

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

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

[0660] ●N is configured by gNB

[0661] Further research is needed on the candidate values ​​for 'N'.

[0662] ● Further research is needed: Whether RRC can enable or disable the current beam as a supplement to N beams is always reported.

[0663] - Further research is needed: Options 1 / 1a / 1b / 2.

[0664] - The above applies at least to single-CC cases.

[0665] Beam report delivery procedure for UE-initiated / event-driven beam reports

[0666] - For Mode A, at least one bit is supported in the first PUCCH channel to request resources in the second UL channel to carry beam reports.

[0667] In this case, the periodic PUCCH resource (with PUCCH format 0 / 1) is configured by dedicated RRC signaling.

[0668] - For Mode B, at least one bit is supported in the first PUCCH channel to indicate the second UL channel to carry beam reports.

[0669] In this case, the periodic PUCCH resource (with PUCCH format 0 / 1) is configured by dedicated RRC signaling.

[0670] - Further research is needed: whether / how to support multi-bit indications in the first PUCCH for both Mode A and Mode B, for example, when approving multiple events.

[0671] - The above applies at least to single CC cases.

[0672] Regarding the RS measurement of the current beam used for event 2, for option 2a, the following two schemes are supported.

[0673] Option 1: The RS of the current beam is the QCL RS in the indicated TCI state.

[0674] ● Further research is needed on whether / how to handle the case where only one TRS is configured in the indicated TCI state.

[0675] - Option 2: The current beam's RS is the QCL RS in the indicated TCI state via the QCL's SSB.

[0676] - Whether to enable Option 1 or Option 2 is selected by NW.

[0677] ● Further research is needed: The above selection is made via explicit RRC parameters or implicit methods. For example, if the RS of the new beam is CSI-RS, then Scheme 1 is enabled; otherwise, Scheme 2 is enabled.

[0678] ● (Working Assumptions) Enabling Scheme 1 or Scheme 2 should ensure that the RS type used for RS measurements of the current beam and the new beam is the same.

[0679] - The above QCL RS is relative to QCL-TypeD if there are two QCL RS in the indicated TCI state.

[0680] Regarding RS measurements for the new beam used in Event 2, at least option 3a should be supported.

[0681] - Option 3a (Explicit Mode): Explicitly configure the RS of the new beam.

[0682] - Further research is needed: Options 3b / 3c

[0683] ●Option 3b: The RS of the new beam is implicitly derived from the QCL RS of the activated TCI state.

[0684] ●Option 3c: The RS of the new beam is implicitly derived from the QCL RS of the TCI states in the configured subset of the traditional RRC configuration TCI state list.

[0685] Regarding UE-initiated / event-driven beam reports, and regarding L1-RSRP report format option 3 which depends on event 2, for report instances where N≥1 beams are reported, the following is supported.

[0686] -RRC can enable or disable whether the current beam always reports.

[0687] When enabled via RRC, report the current beam plus N beams of the measurement RS from the new beam.

[0688] ●Note: The reported current beam is not counted among the N reported beams.

[0689] When deactivated via RRC, report N beams.

[0690] Regarding the beam report transmission procedure for UE-initiated / event-driven beam reports, in mode A, the DCI format in step 2 includes the UL-approved DCI format, and the second channel in step 3 is at least PUSCH.

[0691] -UL allows DCI formats to include at least DCI formats 0_1 / 0_2.

[0692] Regarding the triggering event for event 2:

[0693] - A beam report initiated by the UE occurs if, within a time window (which is configurable), the number of Event 2 instances of at least one identical new beam is greater than or equal to the configurable number M.

[0694] ●Note: If the L1-RSRP of the new beam becomes one threshold better than the current beam, then event 2 instance is determined to be the new beam.

[0695] The above characteristics are affected by the UE's capabilities.

[0696] -Basic characteristics: Once the L1-RSRP of the new beam becomes a threshold better than the current beam, a beam report initiated by the UE occurs.

[0697] Regarding UE-initiated / event-driven beam reports, for triggering events, the following events 1 and 7a / 7b are provided for downward selection or combination in RAN1#118 (the possible result is that new events are not supported).

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

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

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

[0701] Regarding the explicit RS configuration for the new beam measurement used in Event 2, select the following options downwards in RAN1#118:

[0702] - Option 1: The RS for the new beam is explicitly configured in an RS resource set associated with the CSI report configuration;

[0703] ● Further research is needed: RS in the RS resource cluster can be updated by MAC-CE.

[0704] - Option 2: The list of RSs used for new beam measurements can be configured by RRC, and MAC-CE can activate a subset for new beam measurements.

[0705] ● Further research is needed: If the list size is small, MAC-CE activation may not be required.

[0706] - Option 3: The list of RS resources for new beam measurements can be configured by RRC, and the indicated TCI status can provide a subset of RS resources in the list for new beam measurements.

[0707] - Others are not excluded.

[0708] - Further research is needed: Each RS used for the new beam measurement should be associated with a configured joint / DL TCI state that can be used as the indicated TCI state.

[0709] Regarding the RS measurement for the current beam used in event 2, for option 2a, in addition to schemes 1 and 2, the following were further investigated to handle the case where only one TRS is configured in the indicated TCI state.

[0710] - Option 1: Introduce an additional scheme: The RS of the current beam can be a CSI-RS derived from the QCL RS in the indicated TCI state for beam management;

[0711] Option 2: Further support TRS as the measurement RS of the current beam for determining L1-RSRP

[0712] - Option 3: Introduce an additional scheme: The RS of the current beam is explicitly configured by RRC or MAC-CE (Option 2C in the RAN1 116b protocol).

[0713] - Option 4: No further enhancements (i.e., in this case, use option 2).

[0714] The following is provided in the meeting minutes of

[11] RAN2#126:

[0715] Proposal 6 (revised): Based on the beam-specific quality of the serving cell and candidate cells, support the following LTM events as L1 LTM measurement events.

[0716] - Event LTM2: The serving cell’s beam becomes worse than the absolute threshold;

[0717] - Event LTM3: The candidate cell's beam becomes one offset better than the serving cell's beam;

[0718] - Event LTM4: The beamforming of the candidate cell becomes better than the absolute threshold;

[0719] - Event LTM5: The serving cell’s beam becomes worse than absolute threshold1, and the candidate cell’s beam becomes better than another absolute threshold2.

[0720] Further research is needed regarding which beam from the serving cell and neighboring cells should be used for event assessment. Further research is also needed regarding the requirement for event LTM1.

[0721] agree.

[0722] In New Radio (NR) Rel-19, Phase 5 Multiple-Input Multiple-Output (MIMO) enhancements are designed for user equipment (UE)-initiated (UEI) reporting for beam management. Based on the current Radio Layer 1 (RAN1) progress, at least Event 1, Event 2, Event 3, and Event 4 can be considered. A network node can configure a UE to use one or more events. A serving cell or neighboring cells can be configured to use one or more events. That is, in response to the fulfillment of Event i, the UE will trigger the transmission of a UE-initiated report, and / or the UE will transmit a UE-initiated report. Based on the network node receiving the UE-initiated report, the network node will instruct the UE to change the indicated / activated / configured beam (e.g., transmit a Configuration Indicator (TCI) state). Typically, the content of a UE-initiated report includes a resource indicator associated with the resource (used to indicate the beam or TCI state), and / or the matrix / quality associated with the indicated resource, and / or the current beam quality being worse than a threshold. The same or different content will be designed depending on the different Event i.

[0723] Regarding the container carrying UE-initiated reports, a Media Access Control (MAC) control element (CE) or UCI can be considered. The MAC CE may have latency due to the UL approval required for its transmission. In other aspects, Uplink Control Information (UCI) may require network nodes to configure multiple periodic uplink (UL) resources for transmission; however, only a portion of these are available for the UE to use for transmitting UE-initiated reports (i.e., when the conditions of an event are met). To address this, a PreNotification (or Pre-Notification) (PN) can be used to at least indicate the future use of one or more periodic UL resources associated with a UE-initiated report. Depending on whether a UE-initiated report is transmitted on a periodic UL resource, whether a UE-initiated report is triggered, or whether there are pending UE-initiated reports, the UE determines whether to transmit a PN and / or a set of PNs to indicate the use of periodic UL resources. In one instance, when a UE-initiated report is not triggered, or the UE will not use periodic UL resources to transmit a UE-initiated report, or there are no pending UE-initiated reports, the UE may skip transmitting a PN and / or not use periodic UL resources. Typically, a PN can be a sequence-based signal indicating the future use of one or more periodic UL resources. In one instance, the sequence-based signal could be a Sounding Reference Signal (SRS), a Scheduling Request (SR), or a Physical Uplink Control Channel (PUCCH) format 0, where, in this instance, different cyclic shifts map to "used" or "unused." If more information needs to be carried beyond used / unused, a PUCCH format 0 with more cyclic shifts or another / other PUCCH format (e.g., PUCCH format 1, 2, 3, or 4) could be considered. Although the PN can be transmitted with the UL resource used for UE-initiated reports, similar to the Configurable Grant (CG)-UCI on the Physical Uplink Shared Channel (PUSCH), which indicates future use of the CG PUSCH resource, it may be useless because the triggering is dynamic rather than periodic. It is advisable to transmit the PN as a UL resource along with the same Transmission Time Interval (TTI). The PN can be transmitted as a UL resource in different Orthogonal Frequency Division Multiplexing (OFDM) symbols. Typically, for better resource efficiency in network nodes, a time gap or constraint between the PN and the corresponding UL resource is required. Time gaps or restrictions are used to ensure that network nodes have sufficient time for switching and / or for other purposes.

[0724] With the introduction of UEI reports, there are two resource allocation modes for UEI reports. Mode A (or Mode-A) corresponds to dynamic scheduling, while Mode B (or Mode-B) corresponds to (pre)configured resources for transmitting UEI reports.

[0725] For Mode A (or Mode-A), the UE will send a request to the network node. After sending the request, the UE listens for Downlink Control Information (DCI) using scheduling information (and / or using a request for a pending UEI report). The UE then sends the UEI report on the resources scheduled by the DCI. In one instance, in Figure 7 In this timeline, t1 corresponds to the timing when the UE determines that the conditions of an event are met or reached. t2 corresponds to the timing when the UE transmits a request to the network node for UL resources. Typically, the UL channel used for the request corresponds to or is a PUCCH. Preferably, in some embodiments, the UL channel (in timing t2) may correspond to PUCCH format 0, PUCCH format 1, or SR. t3 corresponds to the timing when the UE receives a DCI that schedules one or more UL resources. The UL resource corresponds at least to timing t4. The UL resource may be a PUCCH or a PUSCH. The UEI report can be considered as a UCI associated with a Channel State Information (CSI) report. Preferably, in some embodiments, the DCI received in t3 may request the UE to transmit one or more CSI reports that will be transmitted in timing t4. Therefore, the UEI report may have UL resources, and the UE may transmit the UEI report.

[0726] For Mode B (or Mode-B), a PN (Pre-Configured Node) will be used to notify the use of (pre-)configured resources, which can improve resource efficiency when deploying more (pre-)configured resources to reduce latency. Typically, PN resources and (pre-)configured resources are configured in different instances / timings / TTIs. Alternatively, PN resources and (pre-)configured resources are configured in the same instance / timing / TTI. Once the event conditions are met, the UE triggers the event and / or the UE triggers the transmission of a UEI report. In one instance, in Figure 7 In this context, t1 corresponds to the timing when the UE determines that the conditions for an event have been met or reached. t2 corresponds to the timing when the UE sends a notification to the network node to inform it of the use of UL resources (i.e., the UL resources in t3). Typically, the UL channel used for the request corresponds to either PUCCH or PUCCH. Preferably, in some embodiments, the UL channel (in timing t2) may correspond to PUCCH format 0, PUCCH format 1, or SR. The UL resources in timing t3 are (pre)configured. If the UE has a pending UEI report or an event that has been triggered (and not canceled), the UE uses the UL resources.

[0727] The UEI report is pending before the UE transmits it. The UEI report is pending before the UE cancels the event. The UEI report is pending before the UE receives a response from the network node. The UEI report is pending until the event's delay limit expires.

[0728] For a pending UEE report, in Mode A, the UE will determine or select a valid resource. The UE will transmit the request on the determined / selected resource. The UE will listen to the DCI using scheduling information (and / or using the request for the pending UEE report). The DCI can indicate whether the request is for a request for a UEE report or a network node-triggered report. A code point in the bit field can be used to indicate whether the request is for a request for a UEE report or a network node-triggered report. The bit field can be a CSI request. Based on the code point in the bit field, the UE can determine whether the DCI request is for a network node-triggered report or a UEE report. If the UE has more than one pending UEE report, the UE will determine one of the more than one UEE reports once it receives the DCI. Alternatively, the UE can reuse the more than one UEE report (if the DCI can accommodate the more than one UEE report by scheduling resources at the decoding rate).

[0729] For a pending UEI report, in Mode B, the UE will determine or select a valid PN resource and / or a valid (pre)configured resource for transmitting the UEI report. The UE will transmit the PN on the determined / selected PN resource and the pending UEI report on the determined / selected (pre)configured resource. Typically, the PN resource corresponds to a PUCCH resource, similar to the PUCCH used for SR. The PUCCH resource used for the PN can provide one or more bits (e.g., 2 bits or more) as the PN content (explicitly or implicitly). Furthermore, at this point, which UL channel (e.g., PUSCH or PUCCH) is used for transmitting the UEI report in step 2 remains pending. However, regardless of which channel is designed, the content of the UEI report is a UCI. Due to the coexistence of UCI and / or PUSCH unrelated to the UEI report, how the UE and / or network node handle this situation and the corresponding UE behavior once the resources of step 1 and / or step 2 overlap with UCI and / or PUSCH are discussed. In one instance, due to the two steps introduced for Mode-B, the network node might miss detecting step 1, even if the UE considers the resources for step 1 and step 2 to be effectively bundled. Therefore, when UCI and / or PUSCH (and / or another UL channel / signal unrelated to the UEI report) are configured or scheduled on resources to overlap with those used for step 2, the network node may have difficulty decoding the content due to the inconsistent payload sizes between the network node and the UE.

[0730] Currently, both Rel-19 MIMO and mobility (e.g., Layer 1 (L1) / Layer 2 (L2) triggered mobility (LTM)) items have introduced event-triggered reporting (or UE-initiated reporting). To date, Rel-19 MIMO has agreed to support one event (i.e., event 2 in Chairman's Note RAN1#116bis eom0 [7]), and Rel-19 mobility has agreed to support more than one event (i.e., event LTM2, event LTM3, event LTM4, and event LTM5).

[0731] Preferably, in some embodiments, such as Figure 9 As shown, the UCI multiplexing procedure may include at least resolving PUCCH overlap and / or resolving PUCCH and PUSCH overlap. The UE may determine the (derived) PUCCH whose last start symbol among PUCCH1~PUCCH3 can overlap with other PUCCHs. Then, based on whether the UE supports simultaneous PUCCH and PUSCH on a separate serving cell and / or PUSCH1, PUSCH2, PUCCH2 (or the derived channel) on the same serving cell, the UE determines whether to multiplex the UCI on PUSCH1 or PUSCH2 (which may include UCIs from PUCCH1, PUCCH2, and / or PUCCH3). Preferably, in some embodiments, the detailed determination of the derived PUSCH (e.g., PUSCH1) may depend on dynamic scheduling / indicating that PUSCHs prioritize configured (granted) PUSCHs. Preferably, in some embodiments, the detailed determination of the derived PUSCH (e.g., PUSCH1) may depend on the lower serving cell index of the PUSCH. Preferably, in some embodiments, the detailed determination of the resulting PUSCH (e.g., PUSCH1) may depend on the earlier start symbol of the PUSCH. In this example, PUSCH1 and PUCCH2 are on the same serving cell, and the UE cannot use two UL channels simultaneously on one serving cell. The UE needs to determine the resulting PUSCH for multiplexing UCI (other than allowing both PUCCH and PUSCH to be transmitted on the same serving cell).

[0732] concept

[0733] One or more of the following conditions may be considered:

[0734] -UCI can be a semi-static (SP) / periodic (P) CSI report for the same cell or different cells.

[0735] -UCI can be either a Hybrid Automatic Repeat Request (HARQ) feedback or a SR.

[0736] -PUSCH may or may not include non-periodic (AP) CSI reports.

[0737] - PUSCH / PUCCH can be enabled or disabled at the same time.

[0738] - Logical channel priority sorting can be enabled or disabled.

[0739] - Consider the start symbol of PUSCH, UCI, and step 2.

[0740] - Multiplexing with UL channels that have different priority indices

[0741] - HARQ and CSI can be enabled or disabled simultaneously.

[0742] - Implement carrier aggregation, and / or

[0743] - Priority index (e.g., 0 or 1).

[0744] based on Figure 8 Depending on the circumstances and conditions under which the UCI multiplexing and / or overlap processing procedures are performed, the results may correspond to any of the following (headings):

[0745] Step 1

[0746] Step 1 may have the following instructions:

[0747] 1. Due to mux (and UE transmission having a UL channel with multiplexed SR (PN)),

[0748] 2. No mux, but SR(PN) can be transmitted independently (and the UE transmits a UL channel with SR(PN)).

[0749] No instructions

[0750] 3. Due to the lack of a mux, and the inability of SR (PN) to be transmitted independently.

[0751] Step 2

[0752] Step 2 may have the following instructions:

[0753] 1. Due to mux (and UE transmission having UL channels with multiplexed UEI reports)

[0754] 2. No mux, but UEI reports can be transmitted independently (and the UE transmits UL channels with UEI reports).

[0755] No instructions

[0756] 3. Due to the lack of a mux, and the inability to transmit UEI reports independently.

[0757] In response to (or after) a UCI multiplexing and / or overlap processing procedure, the UE may determine at least one UL channel for transmission, which may be any one of the following or any combination thereof:

[0758] - (Pre-)configured UL resources for step 2 (associated with the triggered event or UEI report, or associated with the event).

[0759] - Pre-configured UL resources for additional UCI multiplexing, and / or

[0760] - UL resources of PUSCH / UCI (not associated with the event) (the UL resources of PUSCH / UCI overlap with the UL resources used in step 2 in the time domain).

[0761] In response to (or after) the UCI multiplexing and / or overlap processing procedure, for UL channels not determined for transmission, the UE will perform any one or more of the following:

[0762] -Drop or cancel UL channels, and / or

[0763] - Do not perform transmissions on the UL channel.

[0764] In response to at least one triggered event (not cancelled), before transmitting the PN in step 1, the UE will determine whether a bundle of resources for step 1 and resources for step 2 is valid / available, or not based on the indication to transmit step 1 and the indication to transmit step 2. If at least one of the indications for step 1 and step 2 is not transmitted before transmitting the PN in step 1, the UE will not determine the bundle of resources for step 1 and resources for step 2 as valid (or qualified). Due to priority reduction, the indication for step x will not be transmitted. Priority reduction can be based on any of the above conditions. In one instance, when the UL resources for step 1 overlap with the PUSCH in the time domain (especially in the same serving cell), priority reduction of the UL resources for step 1, including the PUSCH with a higher-priority logical channel, is possible due to enabled logical channel priority ordering. Additionally and / or preferably, in some embodiments, the above conditions may further include the execution (and incomplete) of random access (RA) procedures and / or the prioritization of measurement gaps and / or sidelink (SL) transmissions. In response to at least one triggered event and a UEI report, the UE will determine a bundle of valid resources for step 1 and resources for step 2.

[0765] For example, such as Figure 10As shown, PUCCH2 is assumed to be step 2 of mode-B, which includes the UEI report, and the UE has previously transmitted the PN on the corresponding UL resource at a predetermined time. In this example, the UE has PUCCH1 and PUCCH3 for transmitting UCIs other than the UEI report, and these five channels overlap with each other in the time domain (partially or completely). In this example, any two different UL channels can correspond to the same or different serving cells.

[0766] The first approach is to perform a separate UCI multiplexing procedure for UEI reports and UCI (not associated with the event or UEI report). Figure 10In this process, the UE will determine two (obtained) PUCCHs (i.e., PUCCH1 (UCI) and PUCCH2 (UEI report)). The UE will resolve overlaps between PUCCHs and PUSCHs (e.g., PUCCH1 and PUSCH1 with PUSCH2). The UE may assume the existence of a UEI report (and PUCCH2) even if no triggered event or pending UEI report exists. Alternatively, in this example, if PUCCH1 and PUSCH1 or PUSCH2 are in different serving cells, and the UE supports simultaneous transmission of PUCCHs and PUSCHs, the UE determines that PUCCH1, PUSCH1, and PUSCH2 are valid for transmission (before comparing with PUCCH2, e.g., comparing with the UEI report). In this example, the UE determines the resulting channels as PUCCH1, PUSCH1, and PUSCH2. After resolving overlaps with PUCCH2, the UE transmits either PUCCH1 or PUCCH2. This is because the UE transmits at most one channel on a serving cell, and PUCCH1 and PUCCH2 typically correspond to the same serving cell (e.g., primary cell (PCell) or PUCCH-secondary cell (SCell)). Preferably, in some embodiments, the comparison between PUCCH1 and PUCCH2 (i.e., UCI and UEI reports unrelated to the event) may depend on a priority rule (or priority ranking rule) or priority value associated with the CSI report. Preferably, in some embodiments, PUCCH2 may always be prioritized. Preferably, in some embodiments, PUCCH1 may always be prioritized. Based on the transmission of UEI reports and UCIs (unrelated to the event) other than UEI reports on different channels, the UE can avoid blind decoding of corresponding channels with unknown sizes even if the network node misses detection step 1. Alternatively, the UE determines the resulting PUSCH as PUSCH1 including the UCI. If the UE supports simultaneous PUCCH and PUSCH transmission, and PUSCH1 and PUSCH2 correspond to serving cells different from PUCCH2, then the UE can transmit PUCCH2 and PUSCH1 with PUSCH2. Alternatively, if PUCCH2 is on the same serving cell as PUSCH1 or PUSCH2, the UE determines a channel for transmission. Preferably, in some embodiments, the priority ordering rule can be configured, specified, or based on a priority value or priority index. Preferably, in some embodiments, the UE prioritizes transmitting PUSCH1 over PUCCH2. Preferably, in some embodiments, the UE does not transmit PUCCH2. Alternatively, the UE can determine another PUSCH for multiplexing UEI reports. Preferably, in some embodiments, the determination regarding the multiplexing of UEI reports on PUSCHs should ensure that multiplexing will occur on PUSCHs different from those determined for multiplexing UCIs other than UEI reports.Preferably, in some embodiments, the UE determines a first PUSCH for reusing UCIs other than the UEI report. Preferably, in some embodiments, the UE determines a second PUSCH for reusing the UEI report. Preferably, in some embodiments, when the UE determines a second PUSCH for reusing the UEI report, the UE excludes the first PUSCH. Preferably, in some embodiments, after excluding the first PUSCH, the UE determines the second PUSCH based on a PUSCH dynamically scheduled / indicated by configuration PUSCH, a PUSCH on a serving cell with a lower serving cell index, and / or a PUSCH that started earlier. An alternative implementation for determining the second PUSCH for reusing the UEI report can be based on the second in a sequence based on a PUSCH dynamically scheduled / indicated by configuration PUSCH, a PUSCH on a serving cell with a lower serving cell index, and / or a PUSCH that started earlier (meaning that the determination of the first PUSCH and the second PUSCH does not have a determining command). Preferably, in some embodiments, when the UE determines that there is no second PUSCH (other than the first PUSCH):

[0767] - If the UE supports simultaneous transmission of PUCCH and PUSCH, then the UE transmission includes the PUCCH reported by the UEI and the first PUSCH, or

[0768] If the UE does not support simultaneous transmission of PUCCH and PUSCH, and the UE prioritizes transmitting the first PUSCH (without transmitting PUCCH) or prioritizes transmitting PUCCH (without transmitting the first PUSCH), then the UE will prioritize one of the channels, the first PUSCH and the PUCCH. Preferably, in some embodiments, priority ordering rules can be specified throughout this disclosure.

[0769] The second approach is to reuse both the UEI and the UEI report, and determine the size of the reused content using a specified or configured payload. Figure 11In this second method, due to possible scenarios in step 1 (not shown in this figure) and / or step 2 (e.g., PUCCH2), network nodes may not be able to align their understanding of the multiplexed content. In this second method, once the UL resource / channel used for step 2 overlaps with another / other UL channel (to be transmitted), the UE should consider the UL resource / channel used for step 2 as part of the UCI multiplexing procedure, or adopt a payload size of a specified or configured size for UEI reporting. Preferably, in some embodiments, a specified code point corresponding to the payload size of the specified or configured size for UEI reporting corresponds to no UEI report. Regardless of whether the UE transmits PN and / or has pending UEI reports, the UE should consider the specified or configured size. Preferably, in some embodiments, the size determination may be based on considering the presence of UEI reports. Preferably, in some embodiments, the resulting channel determination may be based on considering the presence of UL channels used for UEI reporting. Alternatively, the resulting channel determination may not consider the presence of UL channels used for UEI reporting. Figure 11 In determining the obtained PUCCH, the UE does not consider it. Preferably, in some embodiments, the UE transmits multiplexed content with a specified or configured size for both UCI and UEI reports. Preferably, in some embodiments, the UE transmits multiplexed content including a specified or configured size associated with the UEI report (even if there are no pending events).

[0770] The third method is to transmit information associated with the payload size of the obtained information / content. Preferably, in some embodiments, specifying a combination or value or a predefined combination or value can serve as information that the obtained information / content does not include UEI reports. Preferably, in some embodiments, the information includes "how many UEI reports there are". Preferably and / or additionally, the information can indicate whether UEI reports are present in the obtained information / content. When UE is configured with mode-B or UEI reports or event 2 for MIMO (and the UL resources / channels used for step 2 and PUCCH or PUSCH unrelated to the event or UEI report overlap in the time domain), the UE transmits information associated with the payload size of the obtained information / content. Preferably, in some embodiments, if the UL resources / channels used for step 2 and PUCCH or PUSCH unrelated to the event or UEI report do not overlap in the time domain, the UE does not transmit information associated with the payload size of the obtained information / content.

[0771] For example, in Figure 12In this example, PUSCH2 is assumed to be step 2 of mode-B, which includes the UEI report, and the UE has previously transmitted the PN on the corresponding UL resource at a predetermined time. In this instance, the UE has PUCCH1~PUCCH3 for transmitting UCIs other than the UEI report, and these five channels overlap with each other in the time domain (partially or completely). In this instance, any two different UL channels can correspond to the same or different serving cells.

[0772] The first method for PUSCH in step 2 can be as follows: Figure 12As shown. The UE will determine a (derived) PUCCH (i.e., PUCCH2 (UCI)). The UE will resolve overlaps between the PUCCH and PUSCH (e.g., PUCCH2 and PUSCH1). The UE will determine the derived PUSCH as PUSCH1 including the UCI. If PUSCH1 and PUSCH2 correspond to different serving cells, the UE can transmit PUSCH1 and PUSCH2. When the UE determines the derived PUSCH to resolve overlaps between the PUSCH and / or the PUCCH associated with a UCI unrelated to the event, the UE does not consider the PUSCH associated with the UEI report (e.g., the PUSCH configured for the UEI report). In other words, in this instance, if PUSCH1 does not exist, the UE cannot reuse the UCI (which is unrelated to the event) in PUSCH2 (e.g., the UEI report). Even if the serving cell index or ID of the serving cell where PUSCH2 is located is lower than that of PUSCH1, the UE will still determine to reuse the UCI on PUSCH1. Preferably, in some embodiments, if the UE supports simultaneous transmission of PUSCH and PUCCH and PUCCH2 and PUSCH1 are associated with different serving cells, the UE can determine the resulting channels as PUSCH1 and PUCCH2 (before comparing with PUSCH2, e.g., with the UEI report). If the UE can transmit both PUSCH2 and PUSCH1 or all of PUSCH2, PUSCH1, and PUCCH2 simultaneously, the UE can transmit them individually. In one instance, these two channels or all channels are in different serving cells, and preferably, in some embodiments, the UE supports simultaneous transmission of PUCCH and PUSCH. If the UE cannot transmit PUSCH2 and PUSCH1 simultaneously, the UE will prioritize one of them. Preferably, in some embodiments, PUSCH2 can always be prioritized. Preferably, in some embodiments, PUCCH1 can always be prioritized. Preferably, in some embodiments, PUSCH1 can always be prioritized. Preferably, in some embodiments, a priority rule or priority ordering rule may be executed to determine a channel for transmission. Alternatively, if PUSCH1 and PUSCH2 are on the same serving cell, the UE determines a channel for transmission. Preferably, in some embodiments, the priority ordering rule may be configured, specified, or based on a priority value or priority index. Preferably, in some embodiments, the UE prioritizes transmitting PUSCH1 (including UCIs other than UEI reports or events) over PUSCH2 (including UEI reports). Preferably, in some embodiments, the UE does not transmit PUSCH2. Alternatively, the UE may determine another PUSCH for multiplexing UEI reports.Preferably, in some embodiments, the determination of multiplexing UEI reports on a PUSCH should ensure that multiplexing occurs in a PUSCH different from the PUSCH determined for multiplexing UCIs other than UEI reports. Preferably, in some embodiments, the UE determines a first PUSCH for multiplexing UCIs other than UEI reports. Preferably, in some embodiments, the UE determines a second PUSCH for multiplexing UEI reports. Figure 12 In this context, the second PUSCH may not be PUSCH2, and the second PUSCH can correspond to PUSCH3 (in...). Figure 12 (Not shown in the diagram), is another PUSCH in a serving cell different from PUSCH1. Preferably, in some embodiments, when the UE determines a second PUSCH for reusing a UEI report, the UE will exclude the first PUSCH. Preferably, in some embodiments, after excluding the first PUSCH, the UE will determine the second PUSCH based on a PUSCH that is dynamically scheduled / indicated by the configured PUSCH, a PUSCH on a serving cell with a lower serving cell index, and / or a PUSCH that started earlier. An alternative implementation for determining the second PUSCH for reusing a UEI report may be based on the second in a sequence based on a PUSCH that is dynamically scheduled / indicated by the configured PUSCH, a PUSCH on a serving cell with a lower serving cell index, and / or a PUSCH that started earlier (meaning that the determination of the first PUSCH and the second PUSCH does not have a determining command). Alternatively, the UE may determine a PUSCH associated with a UEI report for reusing one or more UCIs that are not associated with the event. Preferably, in some embodiments, the UE may reuse one or more UCIs and UEI reports to a PUSCH for UEI reporting (e.g., Figure 12 In PUSCH2), the UE can preferably multiplex different types of UCIs into the PUSCH used for UEI reporting. Preferably, in some embodiments, the different types of UCIs correspond to HARQ and / or SR. Preferably, in some embodiments, when resolving overlap between PUCCH and / or PUSCH, the UE can multiplex UCIs unrelated to the event into the PUSCH / PUCCH associated with UEI reporting. Preferably, in some embodiments, when resolving overlap between PUCCH and / or PUSCH, the UE does not multiplex UCIs unrelated to the event into the PUSCH / PUCCH associated with UEI reporting.

[0773] The second method for PUSCH in step 2 can be as follows: Figure 13As shown. In this second method, once the UL resource / channel used for step 2 overlaps with another / other UL channel (to be transmitted), the UE should consider the UL resource / channel used for step 2 as part of the UCI multiplexing procedure, or adopt a payload size of a specified or configured size for UEI reporting. Preferably, in some embodiments, a specified code point corresponding to the payload size of the specified or configured size for UEI reporting corresponds to no UEI report. Regardless of whether the UE transmits PN and / or has pending UEI reports, the UE should consider the specified or configured size. Preferably, in some embodiments, the size determination may be based on considering the presence of UEI reports. Preferably, in some embodiments, the resulting channel determination may be based on considering the presence of UL channels for UEI reporting. Alternatively, the resulting channel determination does not consider the presence of UL channels for UEI reporting. Figure 13 In determining the obtained PUCCH, the UE does not consider it. Preferably, in some embodiments, the UE transmits multiplexed content with a specified or configured size for both UCI and UEI reports. Preferably, in some embodiments, the UE transmits multiplexed content including a specified or configured size associated with the UEI report (even if there are no pending events).

[0774] The third method for PUSCH in step 2 is in Figure 13 As shown in the diagram, when the UE is configured with Mode-B or UEI report or Event 2 for MIMO (and the UL resources / channels used for step 2 and the PUCCH or PUSCH unrelated to the event or UEI report overlap in the time domain), the UE transmits information associated with the payload size of the resulting information / content. Preferably, in some embodiments, if the UL resources / channels used for step 2 and the PUCCH or PUSCH unrelated to the event or UEI report do not overlap in the time domain, the UE does not transmit information associated with the payload size of the resulting information / content.

[0775] Preferably, in some embodiments, any one of the first, second, and third methods for resolving overlaps in PUCCH and / or PUSCH associated with UEI reports can be applied to PN. Preferably, in some embodiments, Figure 10 or Figure 11The UEI report in the PUSCH can be replaced with PN. A key difference between the UEI report and PN is that the UE cannot multiplex the PN into the PUSCH. Instead, the UE can multiplex the PN into the PUSCH. Preferably, in some embodiments, the PN can be multiplexed into the PUSCH even if it is associated with or configured by an SR configuration. Preferably, in some embodiments, the UE can determine whether to multiplex the content or information of the PUCCH resource into the (overlapping in the time domain) PUSCH based on whether the PUCCH resource is associated with the UL resource of step 2.

[0776] In response to at least one triggered event (not cancelled), after the PN is transmitted in step 1, one or more different conditions are met. Figure 8 Different situations may cause different UE behaviors.

[0777] Case 1

[0778] In the time domain, there are no overlapping UL channels / signals between the resources used for step 1 and the resources used for step 2.

[0779] The UE determines that a bundle of resources for step 1 and resources for step 2 are valid. The UE can transmit the PN on the resources used for step 1 and the UEI report on the resources used for step 2.

[0780] Case 2

[0781] The UCI overlaps with the resources used in step 2 in the time domain.

[0782] Single cell: Preferably, in some embodiments, the UE communicates with one or more network nodes via a single cell. Preferably, in some embodiments, the UE performs uplink transmissions with one or more network nodes via a single cell.

[0783] The UCI multiplexing procedure may not be applied (not for UCIs that at least contain a UEI report and are unrelated to the event), or the UE may prioritize one of the PUCCH / PUSCH channels used for UCIs and the PUCCH / PUSCH channel used for step 2. Preferably, in some embodiments, the UE prioritizes transmitting UCIs. Preferably, in some embodiments, the UE lowers the priority of transmitting UEI reports. Preferably, in some embodiments, the UE determines which channel to prioritize based on the content of the UCI. Preferably, in some embodiments, the UE prioritizes transmitting UCIs if the UCI includes at least HARQ or SR. Preferably, in some embodiments, the UE prioritizes transmitting UEI reports if the UCI includes CSIs (excluding HARQ or SRs). Preferably, in some embodiments, the UEI report may have a configured or specified / predefined priority value (a higher priority value represents a lower priority, and a lower priority value represents a higher priority). Preferably, in some embodiments, the UE determines whether to prioritize transmitting a UEI report or a UCI based on the priority value. Preferably, in some embodiments, regardless of whether the UE supports multiplexing CSI and HARQ, the UE does not multiplex UEI reports (which are associated with CSI report configuration) and UCIs. Preferably, in some embodiments, the UE performs separate UCI multiplexing procedures for UCIs unrelated to the event and for UEI reports, respectively. Preferably, in some embodiments, a first (derived) channel is determined for UCIs (unrelated to the event). Preferably, in some embodiments, a second (derived) channel is determined for UEI reports (related to the event). Preferably, in some embodiments, the UE determines which of the first (derived) channel and the second (derived) channel should be given priority. Preferably, in some embodiments, the UL channel used for step 2 is a PUCCH. Preferably, in some embodiments, the UL channel used for step 2 is a PUSCH or a PUCCH.

[0784] Preferably, in some embodiments, the UCI multiplexing procedure includes at least the UE resolving PUCCH overlaps, followed by the UE resolving overlaps between PUCCH and PUSCH. Preferably, in some embodiments, the UE performs one or more UCI multiplexing procedures for a set of overlapping PUCCHs and PUSCHs containing UEI reports. Preferably, in some embodiments, the UE resolves overlaps of PUCCHs associated with UEI reports and resolves overlaps of PUCCHs associated with UCIs other than UEI reports, these two resolutions being performed separately. Preferably, in some embodiments, the UE resolves overlaps of PUCCHs and PUSCHs associated with UEI reports separately and resolves overlaps of PUCCHs and PUSCHs associated with UCIs other than UEI reports, these two resolutions being performed separately. Preferably, in some embodiments, after the UE resolves overlaps of PUCCHs and PUSCHs associated with UCIs other than UEI reports, a first (derived) channel corresponds to a UL channel. Preferably, in some embodiments, after the UE resolves overlaps of PUCCHs and PUSCHs associated with UEI reports, a second (derived) channel corresponds to a UL channel. Preferably, in some embodiments, the first (obtained) channel and the second (obtained) channel overlap in the time domain. In response to a single cell preventing the UE from simultaneously transmitting PUSCH and PUCCH, the UE determines a preferred channel between the first (obtained) channel and the second (obtained) channel. Preferably, in some embodiments, the priority ordering is based on HARQ / SR > UEI report > CSI report. Preferably, in some embodiments, the priority ordering is based on HARQ / SR > CSI report, using priority values ​​as a basis. Preferably, in some embodiments, the priority ordering is based on UEI report > UCI other than UEI report (or unrelated to the event). Preferably, in some embodiments, the priority ordering is based on UCI other than UEI report (or unrelated to the event) > UEI report. Preferably, in some embodiments, it is assumed that the priority indices of PUCCH and PUSCH are the same, or the UE is not configured to use a priority index (e.g., 0 or 1).

[0785] Preferably, in some embodiments, one possible implementation is to design the UL channel used for step 2 as a PUSCH. Preferably, in some embodiments, the UCI multiplexing procedure for UEI reporting may not include resolving overlaps between PUCCH and PUSCH associated with UEI reporting. Preferably, in some embodiments, the UCI multiplexing procedure for UEI reporting may not include resolving overlaps between PUCCH and PUSCH associated with UEI reporting. Preferably, in some embodiments, the second (derived) channel corresponds to a PUSCH.

[0786] Preferably, in some embodiments, when determining the first (obtained) channel, PUCCH and / or PUSCH associated with the UEI report are excluded (i.e., PUCCH and / or PUSCH not associated with the UEI report are included). Preferably, in some embodiments, when determining the second (obtained) channel, PUCCH and / or PUSCH not associated with the UEI report are excluded (i.e., PUCCH and / or PUSCH associated with the UEI report are included).

[0787] Alternatively, the UE is configured to multiplex UEI reports and UCIs (unrelated to events). Preferably, in some embodiments, the UE may be configured to multiplex using the size of the UEI report. Preferably, in some embodiments, a specified or predefined size is used to determine the size of the UEI report. Preferably, in some embodiments, the UE multiplexes with a specified or predefined or configured size and an event-unrelated UCI, regardless of whether the UE has pending UEI reports. Preferably, in some embodiments, when the UE determines to perform a UCI multiplexing procedure in response to at least the resources used for UEI reports and the resources used for UCIs overlapping in the time domain, the UE uses a specified or predefined or configured size for UEI reports. Preferably, in some embodiments, size alignment can be applied to the UE and network nodes to transmit multiplexed UEI reports and UCIs, regardless of whether the UE has a problem transmitting PNs (e.g., step 1) or whether the network node has missed detecting PNs. Preferably, in some embodiments, the UE may transmit event-unrelated multiplexed UEI reports and UCIs on the PUCCH or PUSCH.

[0788] Alternatively, the UE transmits information associated with the payload size of the resulting information / content in response to a UCI multiplexing procedure. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content after a UCI multiplexing procedure (in response to overlapping resources for UEI reporting and resources for UCI in the time domain, or in response to one or more events, or in response to one or more UEI reports). Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when resources for UCI and resources for UEI reporting overlap in the time domain. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when transmitting at least one UEI report (preferably with a UCI unrelated to an event or a second UEI report). Preferably, in some embodiments, the UE may transmit multiplexed UEI reports and UCIs unrelated to an event on a PUCCH or PUSCH.

[0789] In another instance, two portions of the UCI and / or UEI report will be transmitted. Preferably, in some embodiments, the first portion of the UCI and / or UEI report has a fixed size. Preferably, in some embodiments, the first portion of the UCI and / or UEI report will indicate the size of the second portion of the UCI and / or UEI report. Preferably, in some embodiments, a UCI multiplexing procedure, including at least the UCI and / or UEI report, will be performed based on the determination or assumption that the UEI report corresponds to a CSI report. Preferably, in some embodiments, the first portion of the UCI and / or UEI report may include higher priority content from the UCI (e.g., HARQ and / or SR from the UCI). Preferably, in some embodiments, the second portion of the UCI and / or UEI report may include lower priority content from the UCI (e.g., a CSI report from the UCI). Preferably, in some embodiments, the two portions of the UCI and / or UEI report here correspond to instances that can be expanded to three portions or other numbers of portions or one portion.

[0790] Preferably, in some embodiments, the UE prioritizes transmitting a UCI (unrelated to the event) instead of a UEI report (step 2). Preferably, in some embodiments, one principle is that the similarity in content between the UEI report and the UCI reduces signaling overhead. Preferably, in some embodiments, a UCI including HARQ / SR has a higher priority than a UEI report. Preferably, in some embodiments, a UCI including a CSI report has a higher priority than a UEI report in step 2. Preferably, in some embodiments, for a UCI including a CSI report, the UE prioritizes a CSI report based on the priority associated with the CSI report and the UEI report. Alternatively, regardless of which UEI report is associated with which priority, the UE prioritizes transmitting the UCI when the UEI report and the UCI overlap in the time domain. Because the UEI report may have the risk of the network node missing the detection of the PN in step 1, the UE prioritizes transmitting the UCI on the PUCCH.

[0791] Throughout this disclosure, the UEI report is a type of CSI report.

[0792] Throughout this disclosure, CSI reports and CSIs are interchangeable.

[0793] Carrier aggregation (or multiple cells): Preferably, in some embodiments, the UE communicates with one or more network nodes via more than one cell. Preferably, in some embodiments, the UE performs uplink transmissions with one or more network nodes via more than one cell.

[0794] Based on the UE's support for simultaneous transmission of PUCCH and PUSCH, the UE can transmit PUCCH and PUSCH on a separate cell. Preferably, in some embodiments, the PUCCH and PUSCH overlap in the time domain. Preferably, in some embodiments, the separate cell corresponds to an in-band cell. Preferably, in some embodiments, when the UE supports simultaneous transmission of PUCCH and PUSCH, the UCI multiplexing procedure may not include resolving the overlap of PUCCH and PUSCH. Preferably, in some embodiments, if the UE determines a first PUCCH for transmission, and if a PUSCH overlaps with the first PUCCH in the time domain and is also on the same serving cell, the UCI multiplexing procedure includes resolving the overlap of PUCCH and PUSCH.

[0795] Preferably, in some embodiments, if the first (derived) channel and the second (derived) channel that overlap in the time domain correspond to PUCCH and PUSCH or two PUSCHs on different serving cells, then the UE can transmit both the first (derived) channel and the second (derived) channel. Preferably, in some embodiments, the UEI report in step 2 corresponds to the first PUSCH, and the UCI other than the UEI report (or unrelated to the event) corresponds to the second PUCCH or the second PUSCH. Preferably, in some embodiments, the first PUSCH overlaps with the second PUCCH or the second PUSCH in the time domain. Preferably, in some embodiments, if the UE supports the simultaneous transmission of PUCCH and PUSCH (and the first PUSCH and the second PUCCH or the second PUSCH are on different serving cells), then the UE can transmit both the first PUSCH and the second PUCCH / PUSCH.

[0796] Alternatively, the UE is configured to multiplex UEI reports and UCIs (unrelated to events). Preferably, in some embodiments, the UE may be configured to multiplex using the size of the UEI report. Preferably, in some embodiments, a specified or predefined size is used to determine the size of the UEI report. Preferably, in some embodiments, the UE uses a specified or predefined or configured size to multiplex with UCIs unrelated to events, regardless of whether the UE has pending UEI reports. Preferably, in some embodiments, the UE uses a specified or predefined or configured size for UEI reports when it determines to perform a UCI multiplexing procedure in response to at least the resources for UEI reports and the resources for UCIs overlapping in the time domain. Preferably, in some embodiments, size alignment can be applied to the UE and network nodes to transmit multiplexed UEI reports and UCIs, regardless of whether the UE has problems transmitting PNs (e.g., step 1) or whether the network node misses detecting PNs. Preferably, in some embodiments, the UE may transmit multiplexed UEI reports and UCIs unrelated to events on the PUCCH or PUSCH.

[0797] Alternatively, the UE transmits information associated with the payload size of the resulting information / content in response to a UCI multiplexing procedure. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content after a UCI multiplexing procedure (in response to overlapping resources for UEI reporting and resources for UCI in the time domain, or in response to one or more events, or in response to one or more UEI reports). Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when resources for UCI and resources for UEI reporting overlap in the time domain. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when transmitting at least one UEI report (preferably with a UCI unrelated to an event or a second UEI report). Preferably, in some embodiments, the UE may transmit multiplexed UEI reports and UCIs unrelated to an event on a PUCCH or PUSCH.

[0798] In another instance, two portions of the UCI and / or UEI report will be transmitted. Preferably, in some embodiments, the first portion of the UCI and / or UEI report has a fixed size. Preferably, in some embodiments, the first portion of the UCI and / or UEI report will indicate the size of the second portion of the UCI and / or UEI report. Preferably, in some embodiments, a UCI multiplexing procedure, including at least the UCI and / or UEI report, will be performed based on the determination or assumption that the UEI report corresponds to a CSI report. Preferably, in some embodiments, the first portion of the UCI and / or UEI report may include higher priority content from the UCI (e.g., HARQ and / or SR from the UCI). Preferably, in some embodiments, the second portion of the UCI and / or UEI report may include lower priority content from the UCI (e.g., a CSI report from the UCI). Preferably, in some embodiments, the two portions of the UCI and / or UEI report here correspond to instances that can be expanded to three portions or other numbers of portions or one portion.

[0799] Preferably, in some embodiments, if the UCI corresponds to a serving cell other than the UEI report, the UE can determine a channel between the PUCCH used for the UCI and the PUSCH / PUCCH used for the UEI report. Preferably, in some embodiments, the UE can prioritize a channel based on the content of the UCI. Preferably, in some embodiments, the UE can prioritize a channel based on the priority associated with the CSI report in the UEI report and the UCI. Preferably, in some embodiments, the UE can prioritize a channel based on the associated serving cell index. Preferably, in some embodiments, the UE can prioritize a channel based on the CSI priority value. Preferably, in some embodiments, single-cell and multi-cell may correspond to different results. In one instance, for a single cell, the UE prioritizes transmitting UCIs unrelated to the event. For multiple cells, the UE prioritizes transmitting UEI reports. If both the UEI report and the UCI are associated with CSI, the priority and / or a channel for transmission can be determined using reportQuantity, (aperiodic / periodic / semi-static / UE-initiated) temporal behavior, serving cell index, and / or (CSI-)ReportconfigId.

[0800] Case 3

[0801] PUSCH overlaps with the resources used in step 2 in the time domain.

[0802] Single cell: Preferably, in some embodiments, the UE communicates with one or more network nodes via a single cell. Preferably, in some embodiments, the UE performs uplink transmissions with one or more network nodes via a single cell.

[0803] The UE determines whether to use the PUSCH or UL channel for transmitting the UEI report. Preferably, in some embodiments, the UE makes this determination based on a priority value or a predefined rule (e.g., a priority rule or a priority ordering rule). Preferably, in some embodiments, the predefined rule (e.g., a priority rule or a priority ordering rule) may be which channel has an earlier start symbol and includes the UEI report > which channel does not include the UEI report. Preferably, in some embodiments, (when the UL channel used for step 2 is a PUCCH) the UE does not multiplex the UEI report on a PUSCH that is not scheduled or configured for UEI reporting. Preferably, in some embodiments, (when the UL channel used for step 2 is a PUSCH) the UE prioritizes transmitting the PUSCH that does not include the UEI report. Alternatively, the UE prioritizes transmitting the PUSCH that includes the UEI report. Preferably, in some embodiments, the UE may determine which channel to use for transmission based on a configured UL channel or a dynamically scheduled / indicated UL channel. Preferably, in some embodiments, the UE prioritizes transmitting the UL channel associated with dynamic scheduling / indication.

[0804] Alternatively, (when the UL channel used for step 2 is a PUSCH) the UE can multiplex the UEI report on an earlier-starting PUSCH (regardless of whether the earlier-starting PUSCH corresponds to a PUSCH associated with an event or UEI report). Preferably, in some embodiments, (when the UL channel used for step 2 is a PUSCH) the UE can multiplex the UEI report on a dynamically scheduled / indicated PUSCH. Preferably, in some embodiments, (when the UL channel used for step 2 is a PUSCH) the UE can multiplex the UEI report on an earlier-starting configured PUSCH (if no dynamically scheduled / indicated PUSCH exists or only a configured PUSCH exists). Preferably, in some embodiments, (when the UL channel used for step 2 is a PUCCH) the UE multiplexes the UEI report on a PUSCH (which is not associated with an event or UEI report). Preferably, in some embodiments, the UE is configured to multiplex the UEI report and UCI (not associated with an event). Preferably, in some embodiments, the UE can be configured to multiplex using the size of the UEI report. Preferably, in some embodiments, a specified or predefined size is used to determine the size of the UEI report. Preferably, in some embodiments, the UE uses a specified or predefined or configured size and an event-independent UCI for multiplexing, regardless of whether the UE has a pending UEI report. Preferably, in some embodiments, when the UE determines to perform a UCI multiplexing procedure in response to the overlap in the time domain between resources for at least the UEI report and resources for the UCI, the UE uses a specified or predefined or configured size for the UEI report. Preferably, in some embodiments, size alignment can be applied to the UE and network node to transmit the multiplexed UEI report and UCI, regardless of whether the UE has a problem transmitting the PN (e.g., step 1) or whether the network node has missed detecting the PN. Preferably, in some embodiments, the UE can transmit the event-independent multiplexed UEI report and UCI on the PUCCH or PUSCH.

[0805] Alternatively, the UE transmits information associated with the payload size of the resulting information / content in response to a UCI multiplexing procedure. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content after a UCI multiplexing procedure (in response to overlapping resources for UEI reporting and resources for UCI in the time domain, or in response to one or more events, or in response to one or more UEI reports). Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when resources for UCI and resources for UEI reporting overlap in the time domain. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when transmitting at least one UEI report (preferably with a UCI unrelated to an event or a second UEI report). Preferably, in some embodiments, the UE may transmit multiplexed UEI reports and UCIs unrelated to an event on a PUCCH or PUSCH.

[0806] In another instance, two portions of the UCI and / or UEI report will be transmitted. Preferably, in some embodiments, the first portion of the UCI and / or UEI report has a fixed size. Preferably, in some embodiments, the first portion of the UCI and / or UEI report will indicate the size of the second portion of the UCI and / or UEI report. Preferably, in some embodiments, a UCI multiplexing procedure, including at least the UCI and / or UEI report, will be performed based on the determination or assumption that the UEI report corresponds to a CSI report. Preferably, in some embodiments, the first portion of the UCI and / or UEI report may include higher priority content from the UCI (e.g., HARQ and / or SR from the UCI). Preferably, in some embodiments, the second portion of the UCI and / or UEI report may include lower priority content from the UCI (e.g., a CSI report from the UCI). Preferably, in some embodiments, the two portions of the UCI and / or UEI report here correspond to instances that can be expanded to three portions or other numbers of portions or one portion.

[0807] Carrier aggregation (or multiple cells): Preferably, in some embodiments, the UE communicates with one or more network nodes via more than one cell. Preferably, in some embodiments, the UE performs uplink transmissions with one or more network nodes via more than one cell.

[0808] Based on the UE's support for simultaneous transmission of PUCCH and PUSCH, the UE can transmit PUCCH and PUSCH on a separate cell. Preferably, in some embodiments, the PUCCH and PUSCH overlap in the time domain. Preferably, in some embodiments, the separate cell corresponds to an in-band cell. Preferably, in some embodiments, when the UE supports simultaneous transmission of PUCCH and PUSCH, the UCI multiplexing procedure may not include resolving the overlap of PUCCH and PUSCH. Preferably, in some embodiments, if the UE determines a first PUCCH for transmission, and if a PUSCH overlaps with the first PUCCH in the time domain and is also on the same serving cell, the UCI multiplexing procedure includes resolving the overlap of PUCCH and PUSCH.

[0809] Preferably, in some embodiments, if the first (derived) channel and the second (derived) channel that overlap in the time domain correspond to PUCCH and PUSCH or two PUSCHs on different serving cells, then the UE can transmit both the first (derived) channel and the second (derived) channel. Preferably, in some embodiments, the UEI report in step 2 corresponds to the first PUSCH, and the PUSCH other than the UEI report (or unrelated to the event) corresponds to the second PUCCH or the second PUSCH. Preferably, in some embodiments, the first PUSCH overlaps with the second PUCCH or the second PUSCH in the time domain. Preferably, in some embodiments, if the UE supports the simultaneous transmission of PUCCH and PUSCH (and the first PUSCH and the second PUCCH or the second PUSCH are on different serving cells), then the UE can transmit both the first PUSCH and the second PUCCH / PUSCH. Preferably, in some embodiments, for case 3.

[0810] Alternatively, the UE is configured to multiplex UEI reports and UCIs (unrelated to events). Preferably, in some embodiments, the UE may be configured to multiplex using the size of the UEI report. Preferably, in some embodiments, a specified or predefined size is used to determine the size of the UEI report. Preferably, in some embodiments, the UE multiplexes with a specified or predefined or configured size and an event-unrelated UCI, regardless of whether the UE has pending UEI reports. Preferably, in some embodiments, when the UE determines to perform a UCI multiplexing procedure in response to at least the resources used for UEI reports and the resources used for UCIs overlapping in the time domain, the UE uses a specified or predefined or configured size for UEI reports. Preferably, in some embodiments, size alignment can be applied to the UE and network nodes to transmit multiplexed UEI reports and UCIs, regardless of whether the UE has a problem transmitting PNs (e.g., step 1) or whether the network node misses detecting PNs. Preferably, in some embodiments, the UE may transmit event-unrelated multiplexed UEI reports and UCIs on the PUCCH or PUSCH.

[0811] Alternatively, in response to a UCI multiplexing procedure, the UE transmits information associated with the payload size of the resulting information / content. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content after a UCI multiplexing procedure (in response to overlap in the time domain between resources for UEI reporting and resources for UCI, or in response to one or more events or one or more UEI reports). Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when resources for UCI and resources for UEI reporting overlap in the time domain. Preferably, in some embodiments, the UE transmits information associated with the payload size of the resulting information / content when transmitting at least one UEI report (preferably with a UCI unrelated to an event or a second UEI report). Preferably, in some embodiments, the UE may transmit multiplexed UEI reports and UCIs unrelated to an event on a PUCCH or PUSCH.

[0812] In another instance, two portions of the UCI and / or UEI report will be transmitted. Preferably, in some embodiments, the first portion of the UCI and / or UEI report has a fixed size. Preferably, in some embodiments, the first portion of the UCI and / or UEI report will indicate the size of the second portion of the UCI and / or UEI report. Preferably, in some embodiments, a UCI multiplexing procedure, including at least the UCI and / or UEI report, will be performed based on the determination or assumption that the UEI report corresponds to a CSI report. Preferably, in some embodiments, the first portion of the UCI and / or UEI report may include higher priority content from the UCI (e.g., HARQ and / or SR from the UCI). Preferably, in some embodiments, the second portion of the UCI and / or UEI report may include lower priority content from the UCI (e.g., a CSI report from the UCI). Preferably, in some embodiments, the two portions of the UCI and / or UEI report here correspond to instances that can be expanded to three portions or other numbers of portions or one portion.

[0813] Case 4

[0814] Both PUSCH and PUCCH of UCI overlap with the resources used in step 2 in the time domain.

[0815] When the UE performs the first method shown above, the UE may have two derived UL channels corresponding to a UCI (not associated with a UEI report or event) and a UEI report. If the UE can transmit both simultaneously, the UE transmits the two derived UL channels, each including a UCI and a UEI report. If the UE cannot transmit the two derived channels simultaneously, the UE preferentially transmits one of the two derived UL channels. Priority ordering rules (or priority rules) can be configured or specified. Preferably, in some embodiments, the detailed priority ordering may depend on... Figure 8 One or more conditions mentioned in the document.

[0816] When the UE performs the second method shown above, the UE is configured to use a specified payload size. When the UL channel / resource used in step 2 and the PUCCH / PUSCH unrelated to the UEI report or event overlap in time, the UE will determine or adopt the specified or configured size for the UEI report. Preferably, in some embodiments, the UE adopts or determines the specified or configured size regardless of whether the UE has a pending UEI report or has transmitted a PN.

[0817] When the UE performs the third method shown above, the UE needs to transmit "information associated with the payload size of the obtained information / content".

[0818] Cases 5 to 16

[0819] Typically, the PUCCH used for step 1 has a higher priority than another / other UL channel. If the UE can transmit such an indication of PN, whether or not due to multiplexing of PN on the PUCCH or another / other UL channel, such an indication of PN can indicate the use of one or more corresponding UL resources / channels for step 2. In some cases, step 1 may have a lower priority than another / other UL channel in response to the result of logical channel priority ordering, overlap with RA procedures in the time domain (partial or complete overlap), having a lower priority index, overlap with measurement gaps in the time domain (partial or complete overlap), and / or overlap with cell discontinuous reception (DRX) in the time domain during (or outside) a period of operation (partial or complete overlap). If the UE determines to transmit another / other channel instead of the PUCCH used for PN (e.g., step 1), the UE determines that the corresponding UL channel / resource for step 2 is invalid. If the UE cannot transmit such an indication of PN, the UE will determine that the corresponding UL channel / resource for step 2 is invalid. Preferably, in some embodiments, the UE determines a future / next valid UL resource for step 1 and a valid UL resource for step 2. In one instance, for cases 9-16, for a single cell or for carrier aggregation, where simultaneous PUCCH and PUSCH transmission is not supported, if the UE determines to transmit PUSCH instead of the PUCCH for step 1, the UE does not transmit the PUCCH for step 1 and / or the UE does not multiplex the PN into the PUSCH, and / or for cases 13-16, the UE may multiplex the UCI (other than the PN) into the PUSCH (if the timeline allows). If the UE determines to transmit the PUCCH for step 1 instead of the PUSCH, the UE does not transmit the PUSCH. Preferably, in some embodiments, the PUCCH for step 1 is configured via an SR configuration (e.g., SchedulingRequestConfig, SchedulingRequestConfig, and / or SchedulingRequestResourceConfig). Preferably, in some embodiments, the PN resource or PUCCH resource for step 1 is not configured via SR configuration (meaning there is no dedicated SR configuration for configuring the PUCCH resource for step 1). Alternatively, the PUCCH resource for step 1 can be configured directly via PUCCH resource. Preferably, in some embodiments, PN corresponds to a UCI content different from CSI, HARQ, and SR. Preferably, in some embodiments, PN corresponds to a UCI content different from CSI and SR. Preferably, in some embodiments, PN can be a UCI content similar to HARQ. Preferably, in some embodiments, PN corresponds to a UCI content different from HARQ and SR.Preferably, in some embodiments, PN can be a type of UCI content similar to CSI.

[0820] Preferably, in some embodiments, when the UL resources / channels used in step 1 and Figure 8 When the PUSCH / PUCCH overlaps in the time domain as shown in Scenarios 5-16, the UE performs a UCI multiplexing procedure by considering the PN associated with the event or UIE report. Preferably, in some embodiments, for step 2, the UE performs two UCI multiplexing procedures separately for UCIs other than the UIE report and for the UIE report. Preferably, in some embodiments, finally, if the UE cannot transmit the first (obtained) channel and the second (obtained) channel simultaneously, the UE determines one of the first (obtained) channel and the second (obtained) channel.

[0821] For cases 5-8 or 13-16, considering the temporal overlap between the PUCCH resources used for step 1 and the PUCCH(one or more) resources used for UCI, when UCI is SR, since only one indication or SR resource can be transmitted (considered in a PUCCH resource group, and preferably all PUCCHs on the same serving cell), the UE needs to determine the indication or SR resource among the PUCCH resources used for step 1 and the PUCCH(one or more) resources used for UCI.

[0822] The first approach is to avoid triggering two procedures simultaneously between SR and UEI reports. Preferably, in some embodiments, when the UE has a pending SR procedure (not cancelled), the UE is not allowed to trigger another SR procedure associated with the UEI report. Preferably, in some embodiments, when the UE has a pending SR procedure and / or determines a first SR resource (PUCCH resource) associated with the pending SR procedure. Preferably, in some embodiments, once the event condition is met, the UE does not determine a second SR resource (PUCCH resource) that partially or completely overlaps with the first SR resource (PUCCH resource).

[0823] The second approach is to determine an SR resource or an indication associated with an SR resource based on a configured or specified / predefined priority rule or priority ranking rule. Preferably, in some embodiments, the UE prioritizes determining an SR resource or prioritizing the provision of an indication associated with an SR resource that is associated with a UEI report or event (e.g., associated with a PN). Preferably, in some embodiments, the UE prioritizes determining an SR resource or prioritizing the provision of an indication associated with an SR resource that is not associated with a UEI report or event (e.g., not associated with a PN). Preferably, in some embodiments, a first priority threshold or a first priority can be configured or specified / predefined for a PN (PUCCH for the PN, SR configuration for the PN). Preferably, in some embodiments, a second priority threshold or a second priority can be configured or specified / predefined for SRs other than the PN. Alternatively, when a first SR resource is associated with a first SR configuration associated with at least one logical channel, the priority of the first SR resource is determined based on the highest priority associated with one or more logical channels. Preferably, in some embodiments, when the second SR resource is associated with a second SR configuration associated with at least one logical channel, the priority of the second SR resource is determined based on the highest priority associated with one or more logical channels.

[0824] The third approach is to transmit information associated with both the first and second SR resources. Alternatively, the UE is allowed to transmit both the first and second SR resources. Preferably, in some embodiments, the UE can transmit both the first and second SR resources simultaneously when they completely overlap in the time domain (but not in the frequency domain). Preferably, in some embodiments, the first and second SR resources are associated with different purposes. Preferably, in some embodiments, the first SR resource is associated with an SR configuration unrelated to an event or PN. Preferably, in some embodiments, the second SR resource is associated with a PN. Preferably, in some embodiments, the UE can reuse information associated with both the first and second SR resources with HARQ or CSI when the first and second SR resources overlap with one or more PUCCH resources used for HARQ or CSI.

[0825] When a UE has a triggered SR procedure, the UE determines the third SR resource associated with the triggered SR procedure. Preferably, in some embodiments, when there are K SR resources overlapping with PUCCH resources used for HARQ or CSI in the time domain, the UE can multiplex information indicating the third SR resource among the K SR resources with HARQ or CSI. Preferably, in some embodiments, the size of the information can be log2(K+1) rounded up.

[0826] When the UE must provide information about at most two SR resources out of K SR resources, one approach is to indicate them individually, and another is to indicate them jointly. Preferably, in some embodiments, for individual indication, the K SR resources can be divided into K1 SR resources and K2 SR resources, the size of the first sub-information can be log2(K1+1) rounded up, and the size of the second sub-information can be log2(K2+1) rounded up. Preferably, in some embodiments, for joint indication, the size of the information can be log2(K(K+1) / 2). Preferably, in some embodiments, a simplified approach is that the information includes log2(K-1+1)+1 bits, where K-1 SR resources are unrelated to the PN, and one bit indicates whether the corresponding resource used in step 2 is used.

[0827] If the UE determines that the first SR resource (which is not used for PN or event) is to be transmitted, the UE will determine the second SR resource used for PN that overlaps with the first SR resource in the time domain as invalid.

[0828] For cases 5-16, the priority of step 1 can be determined based on the lower priority of the bundle of steps 1 and 2. Preferably, in some embodiments, the UEI report corresponds to or is associated with a CSI report. Preferably, in some embodiments, when the UE performs a UCI multiplexing procedure to resolve overlap of PUCCHs including step 1, the UE assumes or determines the priority of the PN as the priority of the CSI. Preferably, in some embodiments, even if the resources used for step 1 are associated with or configured by an SR configuration, or even if step 1 is an SR type UCI, the UE prioritizes transmitting higher priority UCIs. Preferably, in some embodiments, the UE (always) transmits UCIs unrelated to the event and / or discards PUCCHs used for step 1. Preferably, in some embodiments, for cases 5-8, when the UCI corresponds to a HARQ and / or an SR, the UE (always) transmits those UCIs and / or discards PUCCHs used for step 1. Preferably, in some embodiments, one principle is that the PN (or the SR, as in step 1) will provide information about the use of step 2, and since step 2 can be de-prioritized via other channels, the priority of step 1 remains the same as that of step 2. Preferably, in some embodiments, the UE determines or assumes step 1 (PN) as a UCI. Preferably, in some embodiments, the UE determines or assumes step 1 (PN) as a CSI. Preferably, in some embodiments, when resolving PUCCH overlap, the UE excludes the UL channel used for step 1. Preferably, in some embodiments, if the determined PUCCH resources cannot accommodate one or more UCIs unrelated to the event and PN, the UE preferentially reuses the HARQ and SR in the one or more UCIs. Preferably, in some embodiments, if the determined PUCCH resources cannot accommodate one or more UCIs unrelated to the event and PN, the UE preferentially reuses the HARQ and SR in the one or more UCIs and the CSI report associated with higher priority. Preferably, in some embodiments, the priority of CSI reports is determined based on reportQuantity, (e.g., aperiodic / periodic / semi-static / UE-initiated) temporal behavior, and serving cell index (CSI-)ReportconfigId. Preferably, in some embodiments, lower values ​​of the serving cell index and / or (CSI-)ReportconfigId correspond to higher priority. Preferably, in some embodiments, increasing values ​​correspond to aperiodic, semi-static, and periodic. Preferably, in some embodiments, increasing values ​​correspond to UE-initiated, aperiodic, semi-static, and periodic. Alternatively, increasing values ​​correspond to aperiodic, UE-initiated, semi-static, and periodic. Alternatively, increasing values ​​correspond to aperiodic, semi-static, UE-initiated, and periodic. Alternatively, increasing values ​​correspond to aperiodic, semi-static, periodic, and UE-initiated.Preferably, in some embodiments, the priority value of PN is determined based on reportQuantity, (e.g., non-periodic / periodic / semi-static / UE-initiated) temporal behavior, serving cell index, and (CSI-)ReportconfigId associated with the UEI report (or CSI report associated with the UEI report).

[0829] Preferably, in some embodiments, regardless of or regardless of the priority value determined based on reportQuantity, (e.g., non-periodic / periodic / semi-static / UE-initiated) temporal behavior, serving cell index, or (CSI-)ReportconfigId, the PN associated with the UEI report is de-prioritized by any CSI report.

[0830] For cases 9-12, the UE can multiplex the PN into the PUSCH. Preferably, in some embodiments, the UE can multiplex the PN into the PUSCH when the PUSCH can accommodate the PN. Preferably, in some embodiments, the UE can multiplex the PN into the PUSCH even if the PN is an SR, such as a UCI. Preferably, in some embodiments, the UE does not expect the SR configuration for the PN to be associated with a logical channel. Preferably, in some embodiments, the UE does not expect the SR configuration for the PN to be associated with an SL CSI report. Preferably, in some embodiments, the UE does not expect the SR configuration for the PN to be associated with a Link Recovery Request (LRR). Preferably, in some embodiments, for an SR associated with at least one logical channel, the UE does not multiplex the SR into the PUSCH when the UE must transmit the SR on SR resources overlapping with the PUSCH (similar to step 1 in cases 9-12). Preferably, in some embodiments, when the UE communicates with a single serving cell and / or the UE does not support simultaneous transmission of PUCCH and PUSCH, the UE prioritizes transmitting either the PUCCH or PUSCH for the SR. Preferably, in some embodiments, if the UE can simultaneously transmit PUCCH and PUSCH for SR (on different serving cells), the UE can transmit both PUCCH and PUSCH. Preferably, in some embodiments, if the UE communicates with a single serving cell and / or the UE does not support simultaneous transmission of PUCCH and PUSCH, the UE can multiplex the PN into the PUSCH. Preferably, in some embodiments, if the UE can transmit an indication of the PN, the UE determines that the pair of resources used for steps 1 and 2 is valid regardless of whether the PUCCH is multiplexed into the PUSCH. Preferably, in some embodiments, when there are more than one PN resource (e.g., K PN resources) overlapping in the time domain, if the PN is multiplexed into the PUSCH or the PUCCH for a UCI unrelated to the event, the UE determines that the multiplexed result / content / information includes information associated with the PN. Preferably, in some embodiments, the information associated with the PN will indicate the reselection or determination of one or more PN resources or associated with one or more triggered events. Preferably, in some embodiments, the size of the information associated with the PN may depend on the number of more than one PN resource (e.g., K). Preferably, in some embodiments, the UE can transmit up to one PN resource. Preferably, in some embodiments, the UE can transmit up to two PN resources. Preferably, in some embodiments, the size of the information can be different based on the number of PN resources the UE can transmit simultaneously. Preferably, in some embodiments, for the case of at most one PN resource, the size of the information can be log2(K+1) rounded up. Preferably, in some embodiments, for the case of at most two PN resources, the size of the information can be log2(K(K+1) / 2) rounded up.Preferably, in some embodiments, for a maximum of three cases, the size of the information can be log2(K(K+1)(2K+1) / 6) rounded up. Preferably, in some embodiments, the ascending order of the PN resource ID or index (e.g., SR resource ID or index) can correspond to the code points of the information. Preferably, in some embodiments, based on the UE determining the PN resource to be transmitted, the UE transmits information indicating the PN resource.

[0831] For cases 13-16, the UE may multiplex the PN with the PUSCH or the PUCCH carrying a UCI unrelated to the event. Preferably, in some embodiments, the UE transmits a PUSCH with multiplexed content / information including the PN. Preferably, in some embodiments, the UE transmits a PUCCH with multiplexed content / information including the PN. Preferably, in some embodiments, the UE does not multiplex the SR on the PUSCH for SRs associated with logical channels or SL CSI reports or LRRs. Preferably, in some embodiments, the UE actually only multiplexes the HARQ and / or CSI and / or PN in the UCI into the PUSCH. Preferably, in some embodiments, whether the UE multiplexes the HARQ and / or CSI and / or PN into the PUSCH may depend on whether the number of decoded symbols for the HARQ and / or CSI and / or PN is sufficient. Preferably, in some embodiments, if the number of decoded symbols is insufficient, the UE prioritizes multiplexing the HARQ, followed by a higher priority CSI. Preferably, in some embodiments, the PN will be assumed or determined as a CSI.

[0832] Throughout this disclosure, any description, method, solution, approach, or mechanism may be combined, in whole or in part, for any situation (e.g., situations 1 to 16).

[0833] Preferably, in some embodiments, a UCI multiplexing procedure is performed for a set of UCIs (including UEI reports, if the corresponding event is triggered) that have corresponding PUCCHs overlapping in the time domain.

[0834] Preferably, in some embodiments, a UCI multiplexing procedure is performed for a set of UCIs (excluding UEI reports, if triggered) that have corresponding PUCCHs overlapping in the time domain.

[0835] Preferably, in some embodiments, a UCI multiplexing procedure is performed for a set of UEI reports (excluding UCIs unrelated to the event) that have corresponding PUCCHs overlapping in the time domain.

[0836] Preferably, in some embodiments, the UE will determine a (derived) UL channel for transmission. Preferably, in some embodiments, the (derived) UL channel comes from at least one of the corresponding overlapping PUCCHs. Preferably, in some embodiments, the (derived) UL channel is determined based on the PUCCH with the most recent start symbol among the corresponding overlapping PUCCHs.

[0837] Considering the possibility of missing detection step 1 on the network node side, the procedure for PUCCH / PUSCH / UCI overlap processing, including step 2, can be executed separately for both PUCCH / PUSCH / UCI (unrelated to the event) and PUCCH / PUSCH / UCI (related to the event). Preferably, in some embodiments, a first (obtained) channel is determined for PUCCH / PUSCH / UCI (unrelated to the event). Preferably, in some embodiments, a second (obtained) channel is determined for PUCCH / PUSCH / UCI (related to the event). It is assumed on the UE side that there is no multiplexing between the first (obtained) channel and the second (obtained) channel. If the UE cannot transmit both the first (obtained) channel and the second (obtained) channel simultaneously (assuming the priority index of these two channels is the same), the UE's behavior can be one or more of the following bullet points:

[0838] - (Always) Prioritize UCI (unrelated to the event) or the first (obtained) channel.

[0839] - (Always) Prioritize UEI reporting (associated with the event) or the second (obtained) channel.

[0840] - If the UCI corresponds to HARQ or SR, then the UCI (unrelated to the event) or the first (obtained) channel takes precedence.

[0841] - If the UCI corresponds to the CSI (without HARQ and SR), then the UCI (unrelated to the event) or the first (obtained) channel takes precedence.

[0842] Preferably, in some embodiments, the UE discards channels (and content) with lower priority.

[0843] Preferably, in some embodiments, if the UE determines that the UL resource for step 2 (or the UEI report in step 2) is de-prioritized before the corresponding SR / PN in step 1 is transmitted, the UE will not determine this bundle of steps 1 and 2 as a valid or candidate bundle.

[0844] Preferably, in some embodiments, if the UE determines that the UL resource for step 2 (or the UEI report in step 2) has a lower priority after the corresponding SR / PN in step 1 is transmitted, the UE discards the UEI report.

[0845] Throughout this disclosure, one or more UCIs or UCIs may be interchangeable.

[0846] Throughout this disclosure, an event-independent UCI corresponds to or includes any one or any combination of the following (event-independent): CSI, PC5 Quality of Service (QoS) Identifier (PQI), Rank Indicator (RI), SR, HARQ, Signal-to-Interference-Ratio (SINR), Layer 1 / Layer 3 (L1 / L3) - Reference Signal Received Power (RSRP).

[0847] Preferably, in some embodiments, a single transmit / receive point (TRP) is assumed for UCI multiplexing, or a separate mode is assumed for HARQ multiplexing.

[0848] Preferably, in some embodiments, the priority index corresponds to the value 0 or 1, where a higher index indicates a higher priority and a lower index indicates a lower priority (e.g., the priority index is different from the priority value).

[0849] Preferably, in some embodiments, the UL channel corresponds to PUSCH or PUCCH.

[0850] Preferably, in some embodiments, the condition for an event may be that the quality of the serving cell (e.g., L1-RSRP or L1-SINR) is worse than a threshold.

[0851] Preferably, in some embodiments, the condition for an event may be that the quality of the candidate cell (e.g., L1-RSRP or L1-SINR) is better than a threshold.

[0852] Preferably, in some embodiments, the condition for the event may be that the quality of the candidate cell (e.g., L1-RSRP or L1-SINR) is a threshold better than the quality of the serving cell.

[0853] Preferably, in some embodiments, the condition for the event may be that the quality of the candidate cell (e.g., L1-RSRP or L1-SINR) is better than a first threshold and the quality of the serving cell is worse than a second threshold.

[0854] Preferably, in some embodiments, the quality of the serving cell is based on the measurement results of the RS determined according to the indicated TCI state (e.g., Quasi-co-located (QCL) type D RS).

[0855] Preferably, in some embodiments, the quality of the serving cell is based on a measurement of the best or worst quality of the RS determined according to the activated TCI state (e.g., QCL type D RS).

[0856] Preferably, in some embodiments, the condition for the event may be that the quality of the current beam (e.g., L1-RSRP or L1-SINR) is less than a threshold.

[0857] Preferably, in some embodiments, the condition for the event may be that the quality of the candidate beam (e.g., L1-RSRP or L1-SINR) is better than a threshold.

[0858] Preferably, in some embodiments, the condition for the event may be that the quality of the candidate beam (e.g., L1-RSRP or L1-SINR) is a threshold better than the quality of the current beam.

[0859] Preferably, in some embodiments, the condition for the event may be that the quality of the candidate beam (e.g., L1-RSRP or L1-SINR) is better than a first threshold and the quality of the current beam is worse than a second threshold.

[0860] Preferably, in some embodiments, the quality of the current beam is based on the measurement of the RS determined according to the indicated TCI state (e.g., QCL type D RS).

[0861] Preferably, in some embodiments, the quality of the current beam is based on a measurement of the RS with the best or worst quality determined according to the activated TCI state (e.g., QCL type D RS).

[0862] Preferably, in some embodiments, when the UE has one or more triggered MIMO events, the one or more (UEI) reports associated with the one or more triggered MIMO events are generated as L1 signals (e.g., UCI).

[0863] Preferably, in some embodiments, when the UE has one or more triggered LTM events, the one or more (UEI) reports associated with the one or more triggered LTM events are regenerated as L2 signals (e.g., MAC CE).

[0864] Preferably, in some embodiments, for LTM events, the UE may ignore the configuration associated with mode-A or mode-B. Preferably, in some embodiments, the UE transmits the report associated with the LTM event based on multiplexed MAC CE (including information / content of the report associated with the LTM event).

[0865] Preferably, in some embodiments, when the UE has both an LTM event and a MIMO event triggered, the UE can transmit both a report associated with the MIMO event and a report associated with the LTM event. Preferably, in some embodiments, the information indicating the number of reports (associated with the event) can correspond to the MIMO event. Preferably, in some embodiments, the UE can transmit the report associated with the MIMO event based on UCI multiplexing and transmit the report associated with the LTM event based on MAC Protocol Data Unit (PDU) generation (e.g., the MAC PDU includes a MAC CE that includes information / content of the report associated with the LTM event).

[0866] Reports are carried by a single partial CSI, depending on the reporting configuration that does not have associated events (e.g., reportQuantity set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', or 'ssb-Index-SINR', or 'cri-RSRP-Index', 'ssb-Index-RSRP-Index', 'cri-SINR-Index', 'ssb-Index-SINR-Index'). Preferably, in some embodiments, the reporting configuration that does not have associated events may refer to an LTM reporting configuration or a MIMO / CSI reporting configuration. Preferably, in some embodiments, the UE either transmits the entire single partial CSI or does not transmit the single partial CSI (due to reduced priority).

[0867] Preferably, in some embodiments, Concept 2 can be used for events within MIMO or LTM. Preferably, in some embodiments, Concept 1 or Concept 2 can be used for both MIMO and LTM events.

[0868] Preferably, in some embodiments, the PN resource includes different or the same number of symbols, number of physical resource blocks (PRBs), PUCCH format, start symbol and / or start PRB.

[0869] Preferably, in some embodiments, the UE triggers the event or determines that the event has been triggered at one or more time instances where the conditions of the event are met.

[0870] Preferably, in some embodiments, as described in the RAN1 116 protocol, the RAN1 116bis protocol, the RAN1 117 protocol, or the RAN2 126 protocol, the conditions for the event are specified.

[0871] Throughout this disclosure, the events associated with a UEI report correspond to any one or any combination of the following: event 1, event 2, event 3, event 4, event 5, event 6, event 7a, event 7b, event 8, or event 9 (listed in the RAN1 116 protocol or the 116-bis protocol).

[0872] Throughout this disclosure, the UEI report corresponds to the beam report.

[0873] Throughout this disclosure, the UEI report includes (at least) information about the L1-RSRP associated with the current beam and / or the L1-RSRP associated with one or more candidate beams.

[0874] Throughout this disclosure, "quality" corresponds to "preferably having a quantified value of L1-RSRP".

[0875] Throughout this disclosure, the quality comparison between the current beam and the candidate beam corresponds to a comparison of L1-RSRP values, or a comparison of quantized L1-RSRP values ​​(or indices).

[0876] Throughout this disclosure, PN resources and resources used for PN can be interchangeable.

[0877] Throughout this disclosure, UEI resources and resources used for (transmitting) UEI reports may be interchangeable.

[0878] Throughout this disclosure, PN resources (associated with an event) can be configured for each bandwidth portion (BWP) and each serving cell.

[0879] Throughout this disclosure, PN resources (associated with an event) require a MAC CE or a dynamic signal for activation and / or deactivation.

[0880] Throughout this disclosure, UEI resources (associated with an event) can be configured for each BWP and each serving cell.

[0881] Throughout this disclosure, UEI resources (associated with an event) require a MAC CE or a dynamic signal for activation and / or deactivation.

[0882] Throughout this disclosure, for a bundle of PN resources and UEI resources, both the PN resources and UEI resources correspond to the same BWP or the same serving cell.

[0883] Throughout this disclosure, for a bundle of PN resources and UEI resources, the PN resources and UEI resources may correspond to different BWPs or different serving cells.

[0884] Throughout this disclosure, for a bundle of PN resources and UEI resources, both the PN resources and the UEI resources correspond to resources having MACCE or dynamic signals for activation or deactivation.

[0885] Throughout this disclosure, alternatively, for a bundle of PN resources and UEI resources, both the PN resources and UEI resources correspond to resources that do not have a MAC CE or are used for activation or deactivation (i.e., once (pre)configured, the UE can use them for transmission).

[0886] Preferably, in some embodiments, the UE may transmit a PN instead of transmitting a UEI report on the corresponding resource due to one or more specific events.

[0887] Throughout this disclosure, TCI states and beams can be interchangeable.

[0888] Throughout this disclosure, TTI can be replaced or can be a time slot, subframe, several symbols and / or sub-time slot.

[0889] Throughout this disclosure, the same thing can be referred to using uppercase / non-uppercase nouns or nouns with / without hyphens.

[0890] Throughout this disclosure, the IDs of the terms can be interchanged.

[0891] Throughout this disclosure, the concept of association between a PN and a UE-initiated report, for purposes other than those of a UE-initiated report, can be replaced by the PN and another / other pre-configured UL resource. Preferably, in some embodiments, the purpose of the report, other than that of a UE-initiated report, may have a time-critical characteristic.

[0892] This disclosure designs the association between PN and event or configured UL resources associated with the event.

[0893] This disclosure specifies which information is indicated by UL resources for PN.

[0894] This disclosure aims to address the uncertainty regarding the actual number of triggered events and the corresponding reports.

[0895] This disclosure designs a priority ordering for PN resources used for transmission or power allocation.

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

[0897] refer to Figure 14According to this and other concepts, systems, and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: maintaining or receiving one or more configurations associated with events triggered by one or more UEs, wherein the events triggered by the one or more UEs include a first event and a second event (step 1002); receiving one or more configurations for configuring a plurality of UL resources, including at least a first UL resource and a second UL resource, and preferably, in some embodiments, wherein the plurality of UL resources includes one or more pairs of UL resources associated with PN and UEI reports (step 1004); responding to the satisfaction of one of the events triggered by the one or more UEs. The conditions for the event trigger the event (step 1006); and before the timing associated with the first UL resource (having a processing time), based on whether either the first UL resource or the second UL resource is discarded or downgraded (not reused in either of the one or more UL resources) due to overlap with one or more UL resources in the time domain, the UE may determine whether to transmit the PN and the UEI report on a pair of UL resources (or whether the pair of UL resources for transmitting the PN and the UEI report is available or valid), wherein the pair of UL resources corresponds to the first UL resource and the second UL resource (step 1008).

[0898] Preferably, in some embodiments, when a third UL resource overlaps with a first UL resource in the time domain, preventing the UE from transmitting a PN on the first UL resource or from multiplexing the PN into the third UL resource, the UE does not transmit the PN on the first UL resource and / or the UE determines the future / next pair of UL resources; when a fourth UL resource overlaps with a second UL resource in the time domain, preventing the UE from transmitting a UEI report on the second UL resource or from multiplexing the UEI report into the fourth UL resource, the UE does not transmit a UEI report on the second UL resource and / or the UE determines the future / next pair of UL resources; when the third When a UL resource overlaps with a first UL resource in the time domain and the UE can transmit a PN on the first UL resource or can multiplex the PN into a third UL resource, the UE transmits the PN on the first UL resource and / or the UE transmits multiplexed content including the PN on the third UL resource; and / or when a fourth UL resource overlaps with a second UL resource in the time domain and the UE can transmit a UEI report on the second UL resource or can multiplex the UEI report into a fourth UL resource, the UE transmits the UEI report on the second UL resource and / or the UE transmits multiplexed content including the UEI report on the fourth UL resource.

[0899] Preferably, in some embodiments, the UE is not allowed to multiplex UEI reports and UCIs unrelated to the event into the same UL resource; the UE is not allowed to multiplex PNs and UCIs unrelated to the event into the same UL resource; the UE multiplexes UEI reports and UCIs unrelated to the event into the same UL resource, and / or the UE multiplexes PNs and UCIs unrelated to the event into the same UL resource.

[0900] Preferably, in some embodiments, the UE supports simultaneous transmission of PUCCH and PUSCH.

[0901] Preferably, in some embodiments, when the UE supports simultaneous transmission of PUCCH and PUSCH, the UE transmits a PUSCH including a UEI report on a second UL resource, while simultaneously transmitting a PUCCH including a UCI unrelated to the event on a fourth UL resource.

[0902] Preferably, in some embodiments, when the UE does not support simultaneous transmission of PUCCH and PUSCH: the UE transmits a PUSCH including a UEI report on the second UL resource, and / or discards a PUCCH including a UCI unrelated to the event and / or the PUSCH on the second UL resource further includes some or all / all of the UCI, and / or the UE multiplexes some or all / all of the UCI with the UEI report; and / or the UE transmits a PUCCH including a UCI unrelated to the event on the fourth UL resource, and / or discards a PUSCH including a UEI report; the UE transmits one of the channels of PUSCH and PUCCH; the UE determines the PUSCH and PUCCH based on priority rules and / or the content of the UCI. A channel to be transmitted; if the content of the UCI corresponds to HARQ or SR, the UE prioritizes transmitting PUCCH on the fourth UL resource; if the content of the UCI corresponds to CSI, the UE prioritizes transmitting PUSCH on the second UL resource; if the content of the UCI corresponds to an SR associated with a priority higher than the priority of a logical channel, and the PUSCH in the logical channel includes or exceeds a priority threshold, the UE prioritizes transmitting SR on the fourth UL resource; and / or if the content of the UCI corresponds to an SR associated with a priority lower than the priority of a logical channel, and the PUSCH in the logical channel includes or exceeds a second priority threshold, the UE prioritizes transmitting PUSCH that includes at least the UEI report on the second UL resource.

[0903] Preferably, in some embodiments, after the UE transmits the PN on the first UL resource, the UE transmits the UEI report on the second UL resource or discards the UEI report due to overlap with one or more UL resources.

[0904] Preferably, in some embodiments, the one or more UL resources can be scheduled or configured by network nodes.

[0905] Preferably, in some embodiments, the one or more UL resources are used for PUSCH (with / without non-periodic CSI or semi-static CSI) and / or PUCCH (with UCI).

[0906] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of a transmitter. CPU 308 may execute program code 312 to: (i) maintain or receive one or more configurations associated with events triggered by one or more UEs, wherein the events triggered by one or more UEs include a first event and a second event; (ii) receive one or more configurations for configuring a plurality of UL resources, including at least a first UL resource and a second UL resource, and preferably, in some embodiments, wherein the plurality of UL resources includes one or more pairs of UL resources associated with PN and UEI reports; (iii) trigger the one event in response to the satisfaction of a condition of one of the events triggered by one or more UEs; and (iv) prior to a timing associated with the first UL resource (having a processing time), the UE may determine whether to transmit the PN and the UEI report on a pair of UL resources (or whether a pair of UL resources for transmitting the PN and the UEI report is available or valid) based on whether either the first UL resource or the second UL resource is discarded or downgraded (not reused in any of the one or more UL resources) due to overlap with one or more UL resources in the time domain, wherein the pair of UL resources corresponds to the first UL resource and the second UL resource. In addition, CPU 308 can execute program code 312 to perform all the actions, steps and methods described herein above, below or otherwise.

[0907] refer to Figure 15According to this and other concepts, systems, and methods of the present invention, a method 1010 for a UE in a wireless communication system includes: maintaining or receiving one or more configurations associated with events triggered by one or more UEs, wherein the events triggered by one or more UEs include a first event and a second event (step 1012); receiving one or more configurations for configuring a plurality of UL resources, including at least a first UL resource and a second UL resource, and preferably, wherein the plurality of UL resources include one or more pairs of UL resources associated with a PN and a UEI report (step 1014); triggering the one event in response to satisfying a condition of one of the events triggered by one or more UEs (step 1016); and preferably, in some embodiments, determining the priority of the PN (resource) based on a priority value determined by a priority value corresponding to a UEI report (step 1018).

[0908] Preferably, in some embodiments, the priority sorting rule may be based on the following order: HARQ / SR > CSI (not associated with the event) > CSI (associated with the event, such as a UEI report), or HARQ / SR > CSI (associated with the event, such as a UEI report) > CSI (not associated with the event).

[0909] Preferably, in some embodiments, the priority sorting rule may be based on the following order: HARQ / SR > CSI.

[0910] Preferably, in some embodiments, for the priority ranking rule or comparison within CSI, the priority rule depends on reportQuantity, time-domain behavior, serving cell index, and / or (CSI-)ReportconfigId. Preferably, the priority rule is used to determine the CSI report. Preferably, the CSI report includes the UEI report.

[0911] Preferably, in some embodiments, the PN resource is configured by the SR configuration.

[0912] Preferably, in some embodiments, (when the UE does not support simultaneous transmission of PUCCH and PUSCH for multiple carriers or for a single carrier) when the first UL resource overlaps with the third UL resource for PUSCH in the time domain, the UE may multiplex the information associated with PN into the third UL resource, and / or the UE may transmit PUSCH on the third UL resource and / or the UE may not transmit PUCCH for PN on the first UL resource.

[0913] Preferably, in some embodiments, if a fifth UL resource (for transmitting PN) overlaps with a third UL resource for PUSCH or PUCCH in the time domain, the UE multiplexes the information associated with PN into the fifth UL resource; when the UE does not have a pending UEE report or no event is triggered, the information associated with PN indicates no triggered event or no PN or no pending UEE report; a specific code point of the information associated with PN is used to indicate no triggered event or no PN or no pending UEE report; the ascending code point of the information associated with PN corresponds to a PN resource with ascending PN resource ID / index; the code point zero of the information associated with PN is used to indicate no triggered event or no PN or no pending UEE report; and / or code points one to at most ((2^n)-1) correspond to a PN resource with ascending PN resource ID / index, and preferably, in some embodiments, multiple PN resources overlap in the time domain (or in a time slot).

[0914] Preferably, in some embodiments, for SR, the UE does not reuse the information associated with SR in the PUSCH.

[0915] Preferably, in some embodiments, for the PN, the UE can reuse the information associated with the PN into the PUSCH.

[0916] Preferably, in some embodiments, for an SR that overlaps with a PN and preferably with one or more UL channels, the UE multiplexes the SR or PN into a single UL channel, or the UE multiplexes both the SR and PN.

[0917] Preferably, in some embodiments, based on whether the obtained channel corresponds to PUSCH or PUCCH, the UE determines whether to multiplex both SR and PN or only.

[0918] Preferably, in some embodiments, when the UE determines to multiplex SR and PN into a PUCCH that includes HARQ, the UE provides information associated with SR and information associated with PN, and / or when the UE determines to multiplex SR and PN into a PUSCH, the UE provides information associated with PN (and does not provide information associated with SR).

[0919] Preferably, in some embodiments, the information associated with the SR provides a determined SR resource (or does not provide a triggered SR procedure), and / or the information associated with the PN provides a determined PN resource (or does not provide a triggered event).

[0920] Preferably, in some embodiments, the information associated with the SR and the information associated with the PN can be provided separately, or the information associated with the SR and the information associated with the PN can be jointly encoded.

[0921] Preferably, in some embodiments, for the information associated with the SR and the information associated with the PN, a specific code point (e.g., zero) of the joint information corresponds to an untriggered SR and an untriggered event; and / or the ascending order of the code points of the joint information corresponds to SR and PN resources in ascending order of resource ID / index, or the ascending order of the code points of the joint information corresponds to SR resources in ascending order of resource ID / index followed by PN resources in ascending order of resource ID / index, or the ascending order of the code points of the joint information corresponds to PN resources in ascending order of resource ID / index followed by SR resources in ascending order of resource ID / index.

[0922] Preferably, in some embodiments, the information associated with the PN indicates a maximum number of PN resources; the number is one; the number is two; the number depends on the capabilities of the UE; and / or the size of the information associated with the PN is based on a second number of overlapping PN resources and the number of (indicated) PN resources.

[0923] Preferably, in some embodiments, the information associated with the PN indicates a maximum number of SR resources; the number is one; the number is two; the number depends on the UE's capabilities; and / or the size of the information associated with the SR is based on a second number of overlapping SR resources and the number of (indicated) SR resources.

[0924] Preferably, in some embodiments, the joint information associated with PN and SR indicates a maximum number of resources; the number is one; the number is two; the number depends on the capabilities of the UE; and / or the size of the joint information associated with SR and PN is based on a second number of overlapping SR resources and PN resources and the number of (indicated) SR resources and PN resources.

[0925] Preferably, in some embodiments, when the UE resolves overlap with SR and PN, the UE prioritizes transmitting either one; the UE prioritizes transmitting SR; the UE prioritizes transmitting PN; when the priority associated with SR (e.g., and the priority associated with the logical channel associated with SR) is below a threshold, the UE transmits PN; when the priority associated with SR (e.g., and the priority associated with the logical channel associated with SR) is above a threshold, the UE transmits SR; when the priority associated with PN is above a second threshold, the UE transmits PN; when the priority associated with PN is below the second threshold, the UE transmits SR; the UE determines PN as or considers it a CSI type UCI; the UE determines SR as or considers it an SR type UCI; a higher priority value corresponds to a lower priority; and / or a lower priority value corresponds to a higher priority.

[0926] Return to reference Figure 3 and 4In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) maintain or receive one or more configurations associated with events triggered by one or more UEs, wherein the events triggered by one or more UEs include a first event and a second event; (ii) receive one or more configurations for configuring a plurality of UL resources, including at least a first UL resource and a second UL resource, and preferably, wherein the plurality of UL resources includes one or more pairs of UL resources associated with a PN and a UEI report; (iii) trigger an event in response to a condition being met (of the events triggered by one or more UEs); and (iv) preferably, in some embodiments, determine the priority of the PN (resource) based on a priority value determined by a priority value corresponding to a UEI report. Furthermore, CPU 308 may execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0927] refer to Figure 16 According to this and other concepts, systems, and methods of the present invention, a method 1020 for a UE in a wireless communication system includes: determining one or more first (obtained) channels in response to resolving overlap of a first plurality of UL channels unrelated to an event, wherein the one or more first (obtained) channels include a first PUSCH and / or a first PUCCH (step 1022); determining one or more second (obtained) channels in response to resolving overlap of a second plurality of UL channels associated with an event, wherein the one or more second (obtained) channels include a second PUSCH and / or a second PUCCH (step 1024); and determining, based on whether to transmit the first PUSCH, the first PUCCH, the second PUSCH, and / or the second PUCCH, based on whether the PUCCH and PUSCH are transmitted simultaneously (step 1026).

[0928] Preferably, in some embodiments, even if the UE supports simultaneous multiplexing of HARQ and CSI, the UE also executes the UCI multiplexing procedure for UEI reports (unrelated to events) for the corresponding CSI and HARQ separately.

[0929] Preferably, in some embodiments, for a single cell or for multiple cells, when simultaneous transmission of PUCCH and PUSCH is not supported, the UE prioritizes transmitting one of the following channels: the first PUSCH, the first PUCCH, the second PUSCH, and / or the second PUCCH.

[0930] Preferably, in some embodiments, for a single cell or for multiple cells, if simultaneous transmission of PUCCH and PUSCH is not supported, the UE prioritizes transmitting one of the first PUSCH and the second PUSCH.

[0931] Preferably, in some embodiments, for a single cell or for multiple cells, when simultaneous transmission of PUCCH and PUSCH is not supported, the UE prioritizes transmitting one of the channels of the first PUCCH and the second PUSCH, and / or the UE does not multiplex the UCI in the first PUCCH into the second PUSCH.

[0932] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) determine one or more first (obtained) channels in response to resolving overlap of a first plurality of UL channels unrelated to the event, wherein the one or more first (obtained) channels include a first PUSCH and / or a first PUCCH; (ii) determine one or more second (obtained) channels in response to resolving overlap of a second plurality of UL channels associated with the event, wherein the one or more second (obtained) channels include a second PUSCH and / or a second PUCCH; and (iii) determine, based on whether to transmit the first PUSCH, the first PUCCH, the second PUSCH, and / or the second PUCCH, based on whether both PUCCH and PUSCH are transmitted simultaneously. Furthermore, CPU 308 may execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0933] refer to Figure 17 Through this and other concepts, systems and methods of the present invention, a method 1030 for a UE in a wireless communication system includes resolving the overlap of multiple UL channels, wherein the resolving includes individually determining the resulting channel for event-related UCI and UEI reports (step 1032).

[0934] Preferably, in some embodiments, the resolution includes resolving overlap of PUCCHs in the time domain; the resolution includes determining the (derived) PUCCH after resolving PUCCH overlap; when the UE determines the (derived) PUCCH for a UCI unrelated to the event, the UE excludes the PUCCH resource associated with the event; the resolution includes resolving overlap of PUCCH and PUSCH (or the derived PUCCH and PUSCH) in the time domain; the resolution includes determining the (derived) PUSCH after resolving overlap of PUCCH and PUSCH (or the derived PUCCH and PUSCH); when the UE determines the (derived) PUSCH for a UCI unrelated to the event, the UE excludes the PUSCH resource associated with the event; and / or even when the PUSCH resource associated with the event has a lower serving cell index and / or an earlier start symbol and / or corresponds to dynamic scheduling or indication, the UE also determines the (derived) PUSCH for a UCI unrelated to the event based on the PUSCH unrelated to the event.

[0935] Preferably, in some embodiments, the UCI multiplexing procedure includes resolving overlap of PUCCH and / or PUSCH; PUCCH and / or PUSCH partially or completely overlapping in the time domain; PUCCH and / or PUSCH corresponding to the same cell group; and / or PUCCH and / or PUSCH on the same or different serving cells.

[0936] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) resolve overlap of multiple UL channels, wherein the resolution includes individually determining the resulting channels for UCI and UEI reports associated with the event. Furthermore, CPU 308 may execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0937] refer to Figure 18 According to this and other concepts, systems and methods of the present invention, a method 1040 for a UE in a wireless communication system includes: determining an overlap among a first set of PUCCH resources for SR, a second set of PUCCH resources for indication associated with a beam report initiated by the UE, and a third set of PUCCH resources for HARQ (step 1042); and transmitting HARQ and information to a network node, wherein the information indicates a code point among the first set of PUCCH resources for SR and the second set of PUCCH resources for indication (step 1044).

[0938] In various embodiments, the overlap corresponds to overlap in one time slot and one serving cell; the overlap corresponds to overlap in one time slot; the overlap corresponds to overlap in at least one symbol; and / or the first set of PUCCH resources, the second set of PUCCH resources and the third set of PUCCH resources are on PCell or PUCCH-SCell.

[0939] In various embodiments, the third PUCCH resource corresponds to PUCCH format 2, PUCCH format 3, or PUCCH format 4; the first set of PUCCH resources used for SR corresponds to PUCCH format 0 or PUCCH format 1; and / or the second set of PUCCH resources used for indication corresponds to PUCCH format 0 or PUCCH format 1; and / or HARQ and information are transmitted on the third PUCCH resource.

[0940] In various embodiments, the information is transmitted via The unit digit indicates that K1 corresponds to the number of PUCCH resources in the first group of PUCCH resources, and K2 corresponds to the number of PUCCH resources in the second group of PUCCH resources; a code point zero (e.g., a code point with zero or set to zero) corresponds to no triggered SR to be transmitted via a PUCCH resource in the first group of PUCCH resources and no triggered event with indication to be transmitted via a PUCCH resource in the second group of PUCCH resources (e.g., the SR will not be transmitted via the said (or any) PUCCH resource in the first group of PUCCH resources, and the indication will not be transmitted via the said (or any) PUCCH resource in the second group of PUCCH resources); the ascending order of the code points indicated by the information corresponds to the PUCCH resources for the SR in ascending order of resource ID or index, followed by the PUCCH resources for the indication in ascending order of resource ID or index; the resource ID or index for the SR corresponds to the schedulingRequestResourceId; and / or the resource ID or index for the indication corresponds to the PUCCH resource ID or index associated with the indication.

[0941] In various embodiments, the size of the information is based on the number of PUCCH resources in the first group of PUCCH resources and the number of PUCCH resources in the second group of PUCCH resources.

[0942] In various embodiments, each PUCCH resource in the second set of PUCCH resources is used to transmit an indication.

[0943] In various embodiments, the UE receives one or more CSI report configurations related to or for UEI beam reporting, wherein each of the one or more CSI report configurations is configured to use an event and a PUCCH resource for indication.

[0944] In various embodiments, if the UE determines to transmit both an SR and an indication associated with an event, or if there is a pending SR to be transmitted via a PUCCH resource in a first set of PUCCH resources and there is a pending indication (for UEI beam reporting) to be transmitted via a PUCCH resource in a second set of PUCCH resources, then: the UE determines the information based on the priority of the indication being higher than the priority of the SR, wherein the SR is associated with at least one logical channel, the information indicates a code point associated with the one PUCCH resource used for the indication, and / or the information indicates a code point associated with a positive indication (for UEI beam reporting).

[0945] In various embodiments, the UE determines to transmit the SR and not to transmit the indication, or if there is a pending SR to be transmitted via a PUCCH resource in the first set of PUCCH resources and there is no pending indication (for UEI beam reporting) to be transmitted via a PUCCH resource in the second set of PUCCH resources: the information indicates the code point associated with the PUCCH resource used for the SR, and / or the information indicates the code point associated with the affirmative SR.

[0946] In various embodiments, the UE is configured to use a fourth PUCCH resource; the fourth PUCCH resource is used to transmit an indication or a corresponding indication, wherein the indication and an event-associated CSI report are configured to be associated; and / or the fourth PUCCH resource is used to transmit an SR or a corresponding SR.

[0947] In various embodiments, the UE determines a second overlap between the fourth PUCCH resource and the PUSCH resource; the second overlap corresponds to an overlap in a second time slot; the second overlap corresponds to an overlap in at least one symbol; and / or the fourth PUCCH resource and the PUSCH resource are on the same serving cell or different serving cells.

[0948] In various embodiments, if the fourth PUCCH resource corresponds to or is used to transmit an SR, the UE does not multiplex the second information into the PUSCH resource and the UE discards the fourth PUCCH resource; and / or if the fourth PUCCH resource corresponds to or is used to transmit an indication, the UE multiplexes the second information into the PUSCH resource.

[0949] In various embodiments, when the conditions of the event are met, the UE triggers the transmission of a UEI beam report associated with the one CSI report configuration, and the UE generates or determines second information to indicate a positive indication (for the UEI beam report) or an indication of presence; and / or when the conditions of the event are not met, the UE does not trigger the transmission of a UEI beam report associated with the one CSI report configuration, and the UE generates or determines second information to indicate a negative indication (for the UEI beam report) or an indication of non-existence.

[0950] In various embodiments, the UEI beam report associated with an event corresponds to any of the following: a first event (e.g., event 1) which includes the quality of the current beam (e.g., L1-RSRP) being worse than a certain threshold; a second event (e.g., event 2) which includes the quality of at least one new beam (e.g., L1-RSRP) becoming better than the quality of the current beam by a threshold; a third event (e.g., event 7a) which includes the quality of at least one new beam (e.g., L1-RSRP) becoming better than the quality of another beam derived from the activated TCI state with the worst quality by a threshold; or a fourth event (e.g., event 7b) which includes the quality of at least one new beam, for example, L1-RSRP, becoming better than the quality of another beam derived from the activated TCI state with the best quality by a threshold.

[0951] In various embodiments, the indication corresponds to the PN for UEI beam reporting mode-B, or the indication corresponds to a request for UEI beam reporting mode-A. The indication is not configured via SR configuration, or the indication is not associated with SR configuration.

[0952] In various embodiments, the UE determines a third overlap between a fifth set of PUCCH resources for indication and a sixth PUCCH resource for the second HARQ; the third overlap corresponds to an overlap in a third time slot and a serving cell; and / or the third overlap corresponds to an overlap in a third time slot; the third overlap corresponds to an overlap in at least one symbol; and / or the fifth set of PUCCH resources and the sixth PUCCH resource are on a PCell or a PUCCH-SCell.

[0953] In various embodiments, the UE transmits a second HARQ and third information on a sixth PUCCH resource, wherein the third information indicates a code point in a fifth set of PUCCH resources for indication; and / or the third information is transmitted via... The unit digit indication, where K corresponds to the number of PUCCH resources in the fifth group of PUCCH resources; and / or code point zero (e.g., a code point with zero or set to zero) corresponds to an indication that the PUCCH resource will not be transmitted via one of the fifth group of PUCCH resources; the ascending order of the code points of the third information corresponds to the PUCCH resources used for indication in ascending order of resource ID or index; and / or the resource ID or index used for indication corresponds to the PUCCH resource ID or index associated with the indication.

[0954] Return to reference Figure 3 and 4 In one or more embodiments viewed from the perspective of a device (e.g., a UE) in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 may execute program code 312 to: (i) determine overlaps among a first set of PUCCH resources for SR, a second set of PUCCH resources for indication associated with a beam report initiated by the UE, and a third set of PUCCH resources for HARQ; and (ii) transmit HARQ and information to a network node, wherein the information indicates a code point among the first set of PUCCH resources for SR and the second set of PUCCH resources for indication. Furthermore, CPU 308 may execute program code 312 to perform all the actions, steps, and methods described herein above, below, or otherwise.

[0955] Any combination of the concepts or teachings described above or herein may be combined, in whole or in part, to form new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.

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

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

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

[0959] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both, which may be designed using source decoding or some other technique) and various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination thereof, with instructions. To clearly illustrate this interchangeability between hardware and software, the functionality of the various illustrative components, blocks, modules, circuits, and steps has been described above in general terms. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as causing a deviation from the scope of this disclosure.

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

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

[0962] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of computer-readable storage medium known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. Example storage media can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside in a user equipment as discrete components. Additionally, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some aspects, the computer program product may include packaging material.

[0963] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications are possible. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which this invention pertains.

Claims

1. A method for a user equipment, characterized in that, comprising: determining an overlap among a first set of physical uplink control channel resources for scheduling request, a second set of physical uplink control channel resources for an indication associated with a user equipment initiated beam report, and a third physical uplink control channel resource for hybrid automatic repeat request; and transmitting the hybrid automatic repeat request and information to a network node, wherein the information indicates a codepoint among the first set of physical uplink control channel resources for scheduling request and the second set of physical uplink control channel resources for the indication.

2. The method of claim 1, wherein: the overlap corresponds to an overlap in a time slot and a serving cell, the overlap corresponds to an overlap in a time slot, the overlap corresponds to an overlap in at least one symbol, and / or the first set of physical uplink control channel resources, the second set of physical uplink control channel resources, and the third physical uplink control channel resource are on a primary cell or a physical uplink control channel - secondary cell.

3. The method of claim 1, wherein: the third physical uplink control channel resource corresponds to a physical uplink control channel format 2, a physical uplink control channel format 3, or a physical uplink control channel format 4, the first set of physical uplink control channel resources for scheduling request corresponds to a physical uplink control channel format 0 or a physical uplink control channel format 1, the second set of physical uplink control channel resources for the indication corresponds to a physical uplink control channel format 0 or a physical uplink control channel format 1, and / or the hybrid automatic repeat request and the information are transmitted on the third physical uplink control channel resource.

4. The method of claim 1, wherein: a size of the information is determined based on a number of physical uplink control channel resources in the first set of physical uplink control channel resources and a number of physical uplink control channel resources in the second set of physical uplink control channel resources, the codepoint of zero corresponds to the scheduling request not being transmitted via a physical uplink control channel resource in the first set of physical uplink control channel resources and the indication not being transmitted via a physical uplink control channel resource in the second set of physical uplink control channel resources, The information is transmitted via a one-digit indication, where K1 corresponds to a number of physical uplink control channel resources in the first set of physical uplink control channel resources, and K2 corresponds to a number of physical uplink control channel resources in the second set of physical uplink control channel resources, an ascending order of the codepoint indicated by the information corresponds to physical uplink control channel resources for scheduling request in ascending order of resource identity or index followed by physical uplink control channel resources for the indication in ascending order of resource identity or index, a resource identity or index for scheduling request corresponds to schedulingRequestResourceId, and / or a resource identity or index for the indication corresponds to a physical uplink control channel resource identity or index associated with the indication. each physical uplink control channel resource in the second set of physical uplink control channel resources is for transmitting the indication.

5. The method of claim 1, wherein, ​ 6. The method of claim 1, wherein, The user equipment receives one or more channel state information report configurations for user equipment initiated beam reporting, wherein each of the one or more channel state information report configurations is configured to use an event and a physical uplink control channel resource for the indication.

7. The method of claim 1, wherein, If the user equipment determines to transmit both the scheduling request and the indication, or if there is a pending scheduling request to be transmitted via one of the first set of physical uplink control channel resources and there is a pending indication for user equipment initiated beam reporting to be transmitted via one of the second set of physical uplink control channel resources, then: the user equipment determines the information based on a priority of the indication being higher than a priority of the scheduling request, wherein the scheduling request is associated with at least one logical channel, the information indicates a codepoint associated with the one physical uplink control channel resource for the indication, and / or the information indicates a codepoint associated with a positive indication for user equipment initiated beam reporting.

8. The method of claim 1, wherein, If the user equipment determines to transmit the scheduling request and not the indication, or if there is a pending scheduling request to be transmitted via one of the first set of physical uplink control channel resources and there is no pending indication for user equipment initiated beam reporting to be transmitted via one of the second set of physical uplink control channel resources, then: the information indicates a codepoint associated with the one physical uplink control channel resource for the scheduling request, and / or the information indicates a codepoint associated with a positive scheduling request.

9. The method of claim 1, wherein: the user equipment is configured to use a fourth physical uplink control channel resource, the user equipment determines a second overlap between the fourth physical uplink control channel resource and a physical uplink shared channel resource, the second overlap corresponds to an overlap in a second time slot, the second overlap corresponds to an overlap in at least one symbol, and / or the fourth physical uplink control channel resource and the physical uplink shared channel resource are on a same serving cell or different serving cells.

10. The method of claim 9, wherein: if the fourth physical uplink control channel resource corresponds to the scheduling request or for transmitting the scheduling request, the user equipment does not multiplex second information into the physical uplink shared channel resource, and the user equipment drops the fourth physical uplink control channel resource, and / or if the fourth physical uplink control channel resource corresponds to the indication or for transmitting the indication, the user equipment multiplexes the second information into the physical uplink shared channel resource, wherein the indication is associated with one channel state information report configuration associated with an event.

11. The method of claim 10, wherein: when the condition of the event is satisfied, the user equipment triggers transmission of a user equipment initiated beam report associated with the one channel state information report configuration, and the user equipment generates or determines the second information for indicating a positive indication for user equipment initiated beam report or the indication is present, and / or when the condition of the event is not satisfied, the user equipment does not trigger transmission of the user equipment initiated beam report associated with the one channel state information report configuration, and the user equipment generates or determines the second information for indicating a negative indication for user equipment initiated beam report or the indication is not present.

12. The method of claim 1, wherein, the user equipment initiated beam report is associated with an event corresponding to any one of: a first event comprising a quality of a current beam being worse than a certain threshold, a second event comprising a quality of at least one new beam becoming better than a quality of the current beam by a threshold, a third event comprising a quality of at least one new beam becoming better than a quality of another beam derived from an activated transmission configuration indicator state with a worst quality by a threshold, or a fourth event comprising a quality of at least one new beam becoming better than a quality of another beam derived from an activated TCI state with a best quality by a threshold.

13. The method of claim 1, wherein: the indication corresponds to a pre-notification for user equipment initiated beam report mode-B, or the indication corresponds to a request for user equipment initiated beam report mode-A, the indication is not configured via a scheduling request configuration, and / or the indication is not associated with the scheduling request configuration.

14. The method of claim 1, wherein: the user equipment determines a third overlap between a fifth set of physical uplink control channel resources for the indication and a sixth physical uplink control channel resource for a second hybrid automatic repeat request, the third overlap corresponds to an overlap in a third time slot and one serving cell, the third overlap corresponds to an overlap in a third time slot, the third overlap corresponds to an overlap in at least one symbol, and / or the fifth set of physical uplink control channel resources and the sixth physical uplink control channel resource are on a primary cell or a physical uplink control channel-secondary cell.

15. The method of claim 14, wherein: the user equipment transmits the second hybrid automatic repeat request and a third information on the sixth physical uplink control channel resource, wherein the third information indicates one codepoint among the fifth set of physical uplink control channel resources for the indication, The third information is via a K-bit indication, where K corresponds to a number of physical uplink control channel resources in the fifth group of physical uplink control channel resources, the codepoint with zero corresponds to the indication not being transmitted via one physical uplink control channel resource in the fifth set of physical uplink control channel resources, an ascending order of codepoints of the third information corresponds to physical uplink control channel resources for the indication in an ascending order of resource identities or indices, a resource identity or index for the indication corresponds to a physical uplink control channel resource identity or index associated with the indication.

16. A user equipment, comprising: comprising: memory; and a processor, operatively coupled with the memory, wherein the processor is configured to execute program code to: determine an overlap among a first set of physical uplink control channel resources for scheduling request, a second set of physical uplink control channel resources for an indication associated with a user equipment initiated beam report, and a third physical uplink control channel resource for hybrid automatic repeat request; and transmit the hybrid automatic repeat request and information to a network node, wherein the information indicates a codepoint among the first set of physical uplink control channel resources for scheduling request and the second set of physical uplink control channel resources for the indication.

17. The user equipment of claim 16, wherein: the overlap corresponds to an overlap in one time slot and one serving cell, the overlap corresponds to an overlap in one time slot, the overlap corresponds to an overlap in at least one symbol, and / or the first set of physical uplink control channel resources, the second set of physical uplink control channel resources, and the third physical uplink control channel resource are on a primary cell or a physical uplink control channel - secondary cell.

18. The user equipment of claim 16, wherein: the third physical uplink control channel resource corresponds to a physical uplink control channel format 2, a physical uplink control channel format 3, or a physical uplink control channel format 4, the first set of physical uplink control channel resources for scheduling request corresponds to a physical uplink control channel format 0 or a physical uplink control channel format 1, the second set of physical uplink control channel resources for the indication corresponds to a physical uplink control channel format 0 or a physical uplink control channel format 1, and / or the hybrid automatic repeat request and the information are transmitted on the third physical uplink control channel resource.

19. The user equipment of claim 16, wherein: a size of the information is determined based on a number of physical uplink control channel resources in the first set of physical uplink control channel resources and a number of physical uplink control channel resources in the second set of physical uplink control channel resources, the codepoint with zero corresponds to the scheduling request not being transmitted via a physical uplink control channel resource in the first set of physical uplink control channel resources and the indication not being transmitted via a physical uplink control channel resource in the second set of physical uplink control channel resources, The information is transmitted via a one-digit indication, where K1 corresponds to a number of physical uplink control channel resources in the first set of physical uplink control channel resources, and K2 corresponds to a number of physical uplink control channel resources in the second set of physical uplink control channel resources, an ascending order of the codepoint indicated by the information corresponds to physical uplink control channel resources for scheduling request in ascending order of resource identity or index followed by physical uplink control channel resources for the indication in ascending order of resource identity or index, a resource identity or index for scheduling request corresponds to schedulingRequestResourceId, and / or a resource identity or index for the indication corresponds to a physical uplink control channel resource identity or index associated with the indication. ​ 20. The user equipment of claim 16, wherein, Each physical uplink control channel resource of the second set of physical uplink control channel resources is used to convey the indication.

Images