Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that, on the basis of whether an uplink (UL) channel for transmitting a beam report initiated by the terminal includes UL data, controls at least one of dropping of the UL channel or another UL channel overlapping the UL channel and mapping of uplink control information (UCI) pertaining to the other UL channel to the UL channel; and a transmission unit that transmits the UL channel or the other UL channel. The one aspect of the present disclosure can improve communication quality / throughput.

Description

Terminal, wireless communication method and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] It is being considered that future wireless communication systems (e.g., NR, Rel. 19 and later) will support UE-initiated Beam Report (UEIBR), which is event-based and initiated by a terminal (user terminal, User Equipment (UE)).

[0006] Such beam reporting is being considered for support in MIMO / mobility in Rel. 19 and later.

[0007] However, there are cases where UEIBR has not been sufficiently considered. If this consideration is insufficient, it may not be possible to achieve communication with lower latency, which may result in a suppression of improvement in communication quality / throughput.

[0008] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication quality / throughput.

[0009] A terminal according to one aspect of the present disclosure has a control unit that controls at least one of dropping an uplink (UL) channel or another UL channel that overlaps with the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel, based on whether the UL channel transmitting a beam report initiated by the terminal includes UL data, and a transmission unit that transmits the UL channel or the other UL channel.

[0010] According to one aspect of the present disclosure, communication quality / throughput can be improved.

[0011] Fig. 1A is a diagram showing an example of UE movement in Rel. 17. Fig. 1B is a diagram showing an example of UE movement in Rel. 18. Fig. 2 is a diagram showing an example of beta offset configuration according to the first embodiment. Fig. 3A is a diagram showing an example of UCI multiplexing support according to embodiment 2-1-1. Fig. 3B is a diagram showing an example of UCI multiplexing support according to embodiment 2-1-2. Fig. 4A is a diagram showing an example of UCI multiplexing support according to embodiment 2-2-1. Fig. 4B is a diagram showing an example of UCI multiplexing support according to embodiment 2-2-2. Fig. 5 is a diagram showing an example of channel dropping according to the third embodiment. Fig. 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 7 is a diagram showing an example of a base station configuration according to an embodiment. Fig. 8 is a diagram showing an example of a user terminal configuration according to an embodiment. Fig. 9 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. Fig. 10 is a diagram showing an example of a vehicle according to an embodiment.

[0012] (NR PUSCH) PUSCHs defined in NR Rel. 15 and later are broadly divided into dynamic grant-based transmissions and configured grant-based transmissions.

[0013] Dynamic grant (DG)-based transmission is a method of transmitting a Physical Uplink Shared Channel (PUSCH) based on a dynamic UL grant (DG, dynamic UL grant, DCI). The PUSCH may be referred to as a DG PUSCH, for example.

[0014] Configured grant (CG)-based transmission is a method of transmitting a PUSCH based on an UL grant (which may be referred to as a configured grant, a configured UL grant, or the like) configured by a higher layer. In configured grant-based transmission, UL resources are already allocated to a UE, and the UE can spontaneously transmit a PUSCH using the configured resources, which is expected to achieve low-latency communication.

[0015] Configured grant-based transmission may also be referred to as configured grant-based PUSCH, UL Transmission with configured grant, PUSCH with configured grant, CG PUSCH, etc.

[0016] For CG PUSCH transmission, several types (such as Type 1 and Type 2) are defined.

[0017] In CG type 1 transmission (configured grant type 1 transmission), parameters used for CG-based transmission (which may also be referred to as CG-based transmission parameters, CG parameters, etc.) are configured in the UE using only higher layer signaling.

[0018] In a configured grant type 2 transmission, CG parameters are configured in the UE by higher layer signaling, and at least some of the CG parameters may be signaled to the UE by physical layer signaling (e.g., DCI for activation).

[0019] The CG parameters may be configured in the UE using a ConfiguredGrantConfig information element of the RRC. The CG parameters may include, for example, information specifying CG resources. The CG parameters may include, for example, a CG index, a time offset, a periodicity, a number of repeated transmissions of a transport block (TB) (the number of repeated transmissions may be expressed as K), a redundancy version (RV) sequence used in repeated transmission, information on the above-mentioned timer, etc.

[0020] Here, the periodicity and the time offset may be expressed in units of symbols, slots, subframes, frames, etc. The periodicity may be indicated, for example, by a predetermined number of symbols. The time offset may be indicated, for example, by an offset relative to the timing of a predetermined index (such as at least one of slot number = 0 and system frame number = 0). The number of repeated transmissions may be any integer, such as 1, 2, 4, 8, etc. If the number of repeated transmissions is n (> 0), the UE may transmit the CG PUSCH for a predetermined TB using n transmission opportunities.

[0021] If the UE is configured for CG type 1 transmission, the UE may determine that one or more configuration grants have been triggered. The UE may perform PUSCH transmission without DG using resources for the configured configuration grant-based transmission (which may also be referred to as CG resources, transmission occasions, etc.). Note that even if CG-based transmission is configured, the UE may skip CG-based transmission if there is no data in the transmission buffer.

[0022] When the UE is configured with CG type 2 transmission and is notified of a predetermined activation signal, the UE may determine that one or more CGs are triggered (or activated). The predetermined activation signal (e.g., DCI for activation) may be a DCI (PDCCH) that is CRC (Cyclic Redundancy Check) scrambled with a predetermined identifier (e.g., CS-RNTI: Configured Scheduling RNTI). Note that the DCI may be used to control CG deactivation, retransmission, etc.

[0023] The UE may determine whether to transmit a PUSCH using a CG resource configured by a higher layer based on the predetermined activation signal. The UE may release (may be called "release," "deactivate," etc.) a resource (PUSCH) corresponding to the configured grant based on a DCI that deactivates the CG or expiration of a predetermined timer (elapse of a predetermined time).

[0024] The UE may perform PUSCH transmission without DG using activated resources for CG-based transmission (which may also be referred to as CG resources, transmission occasions, etc.). Note that even when CG-based transmission is activated (is in an active state), the UE may skip CG-based transmission if there is no data in the transmission buffer.

[0025] Each of the DG and CG may be referred to as an actual UL grant, which may be higher layer signaling (e.g., the ConfiguredGrantConfig information element of the RRC), physical layer signaling (e.g., the above-mentioned predetermined activation signal), or a combination thereof.

[0026] (Beta Offset) In NR, a UE can transmit uplink control information (UCI) using a PUSCH. The operation of transmitting UCI on a PUSCH is also called UCI on a PUSCH.

[0027] In the case of UCI on PUSCH, the UE may determine the coding rate of the UCI to be transmitted using the PUSCH based on the number / amount of resources used to transmit the UCI (e.g., the number of coded modulation symbols per layer, the number of resource elements (REs)), the number of bits of the UCI, the modulation order, etc.

[0028] The UE determines the number / amount of resources (e.g., the number of coded modulation symbols per layer) for transmitting the UCI based on a beta offset. The beta offset is expressed as β Ｏｆｆｓｅｔ The beta offset may be different for each type or content of UCI (HARQ-ACK, CSI Part 1, CSI Part 2, etc.), and may be different for each type or content of UCI. In addition, the transmission power of the PUSCH including the UCI may be determined based on the beta offset.

[0029] A set of multiple beta offsets may be configured in the UE by higher layer signaling (eg, Radio Resource Control (RRC) signaling).

[0030] An information element (BetaOffsets IE) for a set of multiple beta offsets includes the following seven parameters that indicate indexes for the beta offsets.

[0031] The parameters betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 indicate an index for the beta offset that is applied when transmitting HARQ-ACK of up to 2 bits, up to 11 bits, and more than 11 bits on the PUSCH, respectively.

[0032] The parameters betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 indicate the indexes for the beta offsets that are applied when transmitting CSI Part 1 up to 11 bits and more than 11 bits on the PUSCH, respectively.

[0033] The parameters betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 indicate the indexes for the beta offsets that are applied when transmitting CSI Part 2 up to 11 bits and more than 11 bits on the PUSCH, respectively.

[0034] The UE refers to one index in one set based on the type (or content) and number of bits (payload size) of the UCI to be transmitted, and determines the corresponding beta offset value. Note that the correspondence between the index and the beta offset value is specified by the standard. The correspondence may be different for each UCI content.

[0035] In NR, a dynamic beta offset and a semi-static beta offset are specified. When a dynamic beta offset is configured in a UE, one of up to four offset indexes is specified by a beta offset indicator field included in the DCI format that schedules the PUSCH. The UE uses the beta offset information element corresponding to the specified offset index to determine the beta offset for the UCI transmitted in the PUSCH.

[0036] When a semi-static beta offset is configured, the UE determines that the beta offset indicator field included in the DCI format that schedules the PUSCH is set to 0. The UE also uses one beta offset information element configured by the RRC to determine the beta offset for the UCI transmitted in the PUSCH.

[0037] A beta offset information element regarding a dynamic beta offset or a semi-static beta offset for a PUSCH (DG PUSCH) scheduled by a DCI format is included in PUSCH configuration information (PUSCH-Config information element) and configured in the UE. Note that the DCI that schedules the PUSCH may be, for example, DCI format 0_0, 0_1, 0_2, etc.

[0038] The UCI-OnPUSCH information element (UCI-OnPUSCH IE) specified in Rel. 15 / 16 NR may include a betaOffsets parameter (betaOffsets) and a scaling parameter (scaling). When the betaOffsets parameter includes "dynamic", it indicates that a dynamic beta offset is used for DCI formats other than DCI format 0_2, and when it includes "semiStatic", it indicates that a semi-static beta offset is used for DCI formats other than DCI format 0_2. "Dynamic" includes a betaOffsets information element of size 4 (i.e., four), and "semiStatic" includes one betaOffsets information element.

[0039] The scaling parameter indicates a scaling factor for limiting the number of REs allocated to UCI on PUSCH for DCI formats other than DCI format 0_2. For example, f0p5 corresponds to 0.5.

[0040] The UCI-OnPUSCH-DCI-0-2 information element (UCI-OnPUSCH-DCI-0-2 IE) specified in Rel. 16 NR indicates the betaOffsets parameter (betaOffsetsDCI-0-2) and scaling parameter (scalingDCI-0-2) for DCI format 0_2. It differs from the UCI-OnPUSCH information element in that a beta offset information element of size 2 can be configured instead of a beta offset information element of size 4 for a dynamic beta offset. Depending on this size, the size of the beta offset indicator field included in DCI format 0_2 varies from 1 bit to 2 bits. Note that when a semi-static beta offset is configured, the size of the beta offset indicator field included in DCI format 0_2 is also 0 bits.

[0041] In Rel. 16 NR, a UE may be configured to generate two HARQ-ACK codebooks by a higher layer parameter (pdsch-HARQ-ACK-CodebookList). In this case, the UE may be configured with a list (UCI-OnPUSCH-ListDCI-0-1-r16) of two UCI-OnPUSCH information elements (UCI-OnPUSCH IEs) for DCI format 0_1. The UE may also be configured with a list (UCI-OnPUSCH-ListDCI-0-2-r16) of two UCI-OnPUSCH-DCI-0-2 information elements (UCI-OnPUSCH-DCI-0-2 IEs) for DCI format 0_2. The first entry in these lists may correspond to the first HARQ-ACK codebook, and the second entry may correspond to the second HARQ-ACK codebook.

[0042] The first HARQ-ACK codebook is associated with a Physical Uplink Control Channel (PUCCH) with a priority index of 0, and the second HARQ-ACK codebook is associated with a PUCCH with a priority index of 1. The larger the priority index value, the higher the priority. Priority will be described later.

[0043] The actual UL grant for the CG PUSCH is configured by RRC signaling (ConfiguredGrantConfig information element) for Type 1 CG PUSCH, and is provided by PDCCH (DCI) for Type 2 CG PUSCH.

[0044] A beta offset information element regarding a dynamic beta offset or a semi-static beta offset for the CG PUSCH is included in CG PUSCH configuration information (ConfiguredGrantConfig information element) and configured in the UE.

[0045] The CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) specified in Rel. 15 / 16 NR includes settings (one or more BetaOffsets information elements corresponding to "dynamic" or "semiStatic") for transmitting UCI (HARQ-ACK / CSI) that does not include CG-UCI on CG PUSCH. If the CG-UCI-OnPUSCH information element includes "dynamic," it indicates that a dynamic beta offset is used for UCI on CG PUSCH, and if it includes "semiStatic," it indicates that a semi-static beta offset is used for UCI on CG PUSCH. "Dynamic" includes a BetaOffsets information element of size 1 to 4, and "semiStatic" includes one BetaOffsets information element.

[0046] Note that "semiStatic" is set for Type 1 CG PUSCH. Furthermore, when "dynamic" is set for Type 2 CG PUSCH, the UE is assigned one of up to four offset indexes by the beta offset indicator field included in the DCI for CG PUSCH activation. The UE uses the beta offset information element corresponding to the assigned offset index to determine the beta offset for the UCI transmitted in the CG PUSCH.

[0047] The betaOffset parameter for CG-UCI in CG PUSCH (betaOffsetCG-UCI-r16) specified in Rel. 16 NR indicates an index related to the beta offset when only CG-UCI is transmitted on the CG PUSCH. Note that when HARQ-ACK and CG-UCI are transmitted on the CG PUSCH, the applied beta offset may be the beta offset for HARQ-ACK.

[0048] In addition, the CG-UCI may include a HARQ Process Number (HPN) field, a Redundancy Version (RV) field, a New Data Indicator (NDI) field, and a Channel Occupancy Time (COT) sharing information field.

[0049] (Priority) In NR Rel. 16 and later, multiple levels (e.g., two levels) of priority can be set for signals / channels. For example, it is expected that different priorities will be set for signals / channels corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.) to control communications (e.g., transmission control in the event of a collision). This makes it possible to control communications for the same signal / channel based on different priorities depending on the service type, etc.

[0050] Priority may be set / defined for at least one of information (e.g., UCI, Channel State Information (CSI)), channels (Physical Downlink Shared Channel (PDSCH), PUSCH, PUCCH, etc.), reference signals (e.g., CSI-RS, SRS, etc.), and HARQ-ACK codebook. Also, different priorities may be set for the PUCCH used to transmit SR, the PUCCH used to transmit HARQ-ACK, and the PUCCH used to transmit CSI.

[0051] The priority may be defined as a first priority (e.g., high, 1, etc.) and a second priority (e.g., low, 0, etc.) lower than the first priority. Alternatively, three or more types of priority may be set. The priority may be represented by a priority index, and a larger priority index may correspond to a higher priority.

[0052] High priority may be expressed as high priority (HP), and low priority may be expressed as low priority (LP). For example, a high-priority PUSCH may be expressed as HP PUSCH, and a low-priority HARQ-ACK may be expressed as LP HARQ-ACK.

[0053] Priorities may be set for HARQ-ACK for dynamically scheduled PDSCH, HARQ-ACK for semi-persistent scheduling (SPS) PDSCH, and HARQ-ACK for SPS PDSCH release. Priorities may also be set for HARQ-ACK codebooks corresponding to these HARQ-ACKs. When setting a priority for a PDSCH, the priority of the PDSCH may be read as the priority of the HARQ-ACK for that PDSCH.

[0054] Furthermore, a priority (priority index (for example, p0 (for example, 0) or p1 (for example, 1))) may be set for the DG PUSCH, the CG PUSCH, and the like.

[0055] Priority information may be notified from the base station to the UE using at least one of higher layer signaling and DCI. For example, the priority of a scheduling request may be configured by a higher layer parameter (e.g., schedulingRequestPriority). The priority of HARQ-ACK for a PDSCH scheduled by a DCI (e.g., a dynamic PDSCH) may be signaled by the DCI. The priority of HARQ-ACK for an SPS PDSCH may be configured by a higher layer parameter (e.g., HARQ-ACK-Codebook-indicator-forSPS) or may be signaled by a DCI indicating activation of the SPS PDSCH.

[0056] A predetermined priority (e.g., low) may be set for aperiodic CSI (A-CSI) / semi-persistent CSI (SP-CSI) transmitted on the PUCCH. On the other hand, the priority of aperiodic CSI (A-CSI) / SP-CSI transmitted on the PUSCH may be indicated by DCI (e.g., trigger DCI or activation DCI).

[0057] The priority of the DG PUSCH may be indicated by a priority indicator field of the DCI that schedules the PUSCH. The priority of the CG PUSCH may be set by a higher layer parameter (e.g., priority). A predetermined priority (e.g., low) may be set for the P-SRS / SP-SRS and the A-SRS triggered by a DCI (e.g., DCI format 0_1 / DCI format 2_3).

[0058] The UE may control UL transmissions based on priority when multiple UL signals / UL channels overlap (or collide).

[0059] The overlap of multiple UL signals / UL channels may refer to the case where the time resources (or the time resources and the frequency resources) of multiple UL signals / UL channels overlap, or the case where the transmission timings of multiple UL signals / UL channels overlap. The time resource may be interpreted as the time domain. The time resource may be in units of a symbol, a slot, a subslot, or a subframe.

[0060] Overlapping UL signals / UL channels at the same UE (e.g., intra-UE) may mean overlapping UL signals / UL channels at least in the same time resource (e.g., symbol), and colliding UL signals / UL channels at different UEs (e.g., inter-UE) may mean overlapping UL signals / UL channels in the same time resource (e.g., symbol) and frequency resource (e.g., RB).

[0061] For example, when multiple UL signals / UL channels with the same priority overlap, the UE may control the multiple UL signals / UL channels to be multiplexed into one UL channel and transmitted.

[0062] For example, when a HARQ-ACK (or a PUCCH for transmitting the HARQ-ACK) set to the first priority (high) overlaps with UL data / UL-SCH (or a PUSCH for transmitting the UL data / UL-SCH) set to the first priority (high), the UE may multiplex (or map) the HARQ-ACK onto the PUSCH and transmit both the UL data and the HARQ-ACK.

[0063] When multiple UL signals / UL channels with different priorities overlap, the UE may control the UL transmission with the higher priority (e.g., prioritize the UL transmission with the higher priority) and not perform the UL transmission with the lower priority (e.g., drop it).

[0064] When UL data / HARQ-ACK (or UL channel for transmitting UL data / HARQ-ACK) set to a first priority (high) overlaps with UL data / HARQ-ACK (or UL channel for transmitting UL data / HARQ-ACK) set to a second priority (low), the UE may perform control to drop the UL data / HARQ-ACK with a lower priority and prioritize the transmission of the UL data / HARQ-ACK with a higher priority. Note that the UE may change (e.g., postpone or shift) the transmission timing of the UL transmission with a lower priority.

[0065] When more than two (or three or more) UL signals / UL channels overlap in the time domain, transmission may be controlled in two steps: In step 1, one UL channel is selected to multiplex UL signals transmitted by UL transmissions with the same priority; and in step 2, among UL transmissions with different priorities, control may be performed so that UL transmissions with higher priority are transmitted first and UL transmissions with lower priority are dropped.

[0066] In this way, the UE can resolve collisions between multiple UL transmissions with the same priority in step 1, and between multiple UL transmissions with different priorities in step 2.

[0067] (Simultaneous Transmission / Multiplexing of UL Transmissions with Different Priorities) There may be cases where multiple UL transmissions transmitted on different carriers (or cells, CCs) overlap in the time domain and have different priorities.

[0068] For example, when UL channels / UL signals are scheduled on different inter-cell carriers supported by different RFs (Radio Frequencies), transmitting each UL channel / UL signal is beneficial from the viewpoint of low latency and spectral efficiency. When a UE supports RF processing for each of different carriers (CCs), transmitting each UL channel / UL signal on each carrier can improve resource utilization efficiency and reduce latency.

[0069] For example, for each UE that supports inter-band carrier aggregation (e.g., inter-band CA) functionality, it may be supported that simultaneous PUCCH / PUSCH transmissions with different priorities (e.g., PHY priorities) in different cells are RRC configured within the same PUCCH group.

[0070] Alternatively, when multiple UL transmissions with different priorities are scheduled intra-cell / inter-cell, multiplexing of UL transmissions with different priorities (e.g., transmitting using the same UL channel) may be supported. For example, multiple UL transmissions with a certain priority may be multiplexed onto an UL channel for UL transmissions with another priority.

[0071] Whether or not to multiplex / map (e.g., enable / disable, or activate / deactivate) a UCI (e.g., HARQ-ACK) to an UL channel (e.g., PUSCH) having a different priority from the UCI may be configured by higher layer signaling.

[0072] In Rel. 17, when a low-priority HARQ-ACK (LP HARQ-ACK) is multiplexed onto a high-priority PUSCH (HP PUSCH), a beta offset of 0 < < 1 is supported. Also, it is supported to set a different beta offset index for the case where the LP HARQ-ACK is multiplexed onto the HP PUSCH and the case where the HP HARQ-ACK is multiplexed onto the LP PUSCH from the other cases.

[0073] For example, a beta offset information element for LP HARQ-ACK multiplexed in HP dynamic PUSCH (which may be referred to as BetaOffsetsCrossPri0 IE), a beta offset information element for HP HARQ-ACK multiplexed in LP dynamic PUSCH (which may be referred to as BetaOffsetsCrossPri1 IE), etc. are defined. Note that these beta offset information elements may include parameters equivalent to betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 of the existing beta offset information element (BetaOffsets IE) (parameters related to CSI Part 1 and CSI Part 2 may not be included).

[0074] Also, Rel. The following parameters / information elements are supported: a betaOffsets parameter (betaOffsets) up to 15, a betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI-0-2), and a parameter / information element in which the existing beta offset information element (BetaOffsets IE) in the CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) is replaced with the BetaOffsetsCrossPri0 IE or BetaOffsetsCrossPri1 IE (e.g., betaOffsetsCrossPri0-r17, betaOffsetsCrossPri1-r17, betaOffsetsCrossPri0DCI-0-2-r17, betaOffsetsCrossPri1DCI-0-2-r17, CG-betaOffsetsCrossPri0, CG-betaOffsetsCrossPri1).

[0075] (L1 / L2 Inter-Cell Mobility) A UE may perform UL transmission to one or more cells / TRPs. The following scenario 1 or scenario 2 may be considered as a procedure in this case. In the present disclosure, a serving cell may be interpreted as a TRP in the serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as interchangeable. In the present disclosure, a physical cell identity (PCI) different from the physical cell identity (PCI) of the current serving cell may be simply referred to as a "different PCI." A non-serving cell, a cell having a different PCI, and an additional cell may be interpreted as interchangeable.

[0076] <Scenario 1> Scenario 1 corresponds to, for example, multi-TRP inter-cell mobility, but may be a scenario that does not correspond to multi-TRP inter-cell mobility.

[0077] (1) The UE receives from the serving cell the configuration necessary for using radio resources for data transmission and reception, including the SSB configuration for beam measurement of the TRP corresponding to a PCI different from that of the serving cell and the resources of the different PCI. (2) The UE performs beam measurement of the TRP corresponding to the different PCI and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) state associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) The UE transmits and receives using UE-dedicated channels on the TRP corresponding to the different PCI. (5) The UE must always cover the serving cell, including in the case of multiple TRPs. As in conventional systems, the UE must use common channels from the serving cell, such as the Broadcast Control Channel (BCCH) and the Paging Channel (PCH).

[0078] In Scenario 1, when the UE transmits and receives signals to and from an additional cell / TRP (a TRP corresponding to the PCI of the additional cell), the serving cell (the serving cell assumption in the UE) is not changed. The UE is configured with higher layer parameters related to the PCI of non-serving cells from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.

[0079] Figure 1A shows an example of UE movement in Rel. 17. Assume that the UE moves from a cell (serving cell) with PCI #1 to a cell (additional cell) with PCI #3 (which overlaps with the serving cell). In this case, Rel. 17 does not support switching of serving cells via L1 / L2.

[0080] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. The UE needs to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, a cell change is required, such as by handover (also called L3 mobility).

[0081] <Scenario 2> In scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, the serving cell can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with an additional cell is possible without handover. Since handover requires RRC reconnection, which results in a period when data communication is unavailable, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can be continued even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In scenario 2, for example, the following procedure is performed.

[0082] (1) The UE receives SSB configuration for a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement for the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration for the cell with a different PCI (serving cell configuration) via higher layer signaling (e.g., RRC). That is, pre-configuration for the serving cell change may be performed. This configuration may be performed together with or separately from the configuration in (1). (4) Based on the above report, the TCI state of the cell with a different PCI may be activated via L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts reception / transmission using the pre-configured UE-dedicated channel and TCI state.

[0083] That is, in Scenario 2, the serving cell (the serving cell assumed by the UE) is updated by L1 / L2 signaling. Scenario 2 may be applied in Rel. 18.

[0084] Figure 1B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). The UE can receive / transmit UE-dedicated channels / common channels to / from the new serving cell (or target serving cell). The UE may move out of the coverage of the current serving cell (e.g., current serving cell).

[0085] (UE-initiated Beam Report (UEIBR)) It is being considered that event-based beam reporting will be supported in future wireless communication systems (e.g., Rel. 19 and later). Event-based beam reporting may be called event-triggered beam reporting or UE-initiated beam reporting (UEIBR).

[0086] UEIBR / UE initiated beam management (UEIBM) can be used for measurement reporting / beam switching / cell switching etc.

[0087] In UEIBR, it is considered that the beam report includes at least one of the following information as report content: Beam / reference signal index (e.g., CSI-RS / SSB resource index / indicator) Measurement result (e.g., L1-RSRP / SINR (absolute value / relative value)) Number of beams / RSs to be reported Whether the serving beam is included in the beam report.

[0088] Regarding the information regarding the number of beams / RSs to be reported, since the base station / network and the UE need to have a common understanding of the size of the beam report (e.g., UCI), it is preferable that this information be included in the beam report reported from the UE.

[0089] In this case, the UCI may be reported in two parts, for example, the UCI (which may have a fixed size) transmitted in the first part (step) may indicate the size (e.g., the number of beams) of the UCI transmitted in the second part (step).

[0090] In this case, the UCI may be coded in two parts, for example, the first part of the UCI (which may have a fixed size) may indicate the size of the second part of the UCI.

[0091] Events related to UEIBR (the events mentioned above) may be broadly categorized into the following event types: Event 1: The quality of the current beam becomes worse than a certain threshold. Event 2: The quality of at least one new beam (e.g., L1-RSRP) becomes better than a certain threshold compared to the quality of the current beam. Event 3: The quality of the new beam becomes better than a certain threshold. Event 4: The quality of the current beam becomes worse than a first threshold and the quality of at least one new beam becomes better than a second threshold. Event 5: The absolute value of the difference between the quality of the current beam and the quality of at least one new beam becomes smaller than a certain threshold. Event 6: The current beam is no longer included in the best K (greater than 1: K>1) beams (among the beams configured for measurement / reporting). Event 7: The quality (e.g., L1-RSRP) of at least one new beam becomes better than the RS derived from the best quality activated (active) TCI state by more than a threshold (M is 1 or more, M may be configured in RRC). Event 8: The quality (e.g., L1-RSRP) of M (more than 1: M>1) new beams becomes better than the current beam by more than a threshold. Event 9: The quality (e.g., L1-RSRP) of at least one new beam becomes better than the configured reference RS (which may be SSB / CSI-RS) by more than a threshold.

[0092] It should be noted that such event types do not exclude the events described above. For example, such event types may be appropriately interpreted as the events described above.

[0093] Furthermore, at least two of the above events may be defined in combination.

[0094] (UCI-based UEIBR) In the UCI-based UEIBR procedure, the following modes may be supported.

[0095] Mode A relates to dynamic scheduling of UCI by the NW (gNB). That is, in Mode A, resources for UCI are scheduled by the gNB. Mode A may be a basic function of the UE (a UE that supports UE IBR may naturally support this function).

[0096] Step 1: The UE transmits a first UL channel (e.g., PUCCH), which may consist of one or more bits, that notifies / requests a second UL channel (e.g., PUCCH) for transmitting a beam report.

[0097] Step 2: The UE detects the DCI format indicating the second UL channel resource.

[0098] Step 3: The UE transmits a beam report using resources (UCI) on the second UL channel.

[0099] For mode A, at least a one-bit indication in the first UL channel (PUCCH) may be supported to request resources in the second UL channel for transmitting a beam report.

[0100] In this case, periodic PUCCH resources (PUCCH format 0 / 1) may be configured by dedicated higher layer signaling.

[0101] Mode B Mode B relates to UCI within pre-configured resources for the second UL channel.

[0102] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is an UL channel that indicates a second UL channel for transmitting a beam report and may be configured with one or more bits. The first UL channel may be configured with one or more bits.

[0103] Step 2: The UE transmits a beam report in the second UL channel (e.g., using specific resources (UCI) within the channel).

[0104] Note that the notification in step 1 may be included in a separate reporting instance from the beam report in step 2.

[0105] In the case of Mode B, a one-bit indication in at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel is used to transmit a beam report.

[0106] In this case, periodic PUCCH resources (PUCCH format 0 / 1) may be configured by dedicated higher layer signaling.

[0107] In either of the above-mentioned modes A / B, cross-CC (component carrier) beam reporting may be supported.

[0108] The pre-configured resource for the second UL channel in step 2 of Mode B may be at least a CG PUSCH (e.g., a Type 1 CG PUSCH).

[0109] The CG PUSCH may carry UL data (UL-SCH) and beam reports.

[0110] In addition, the CG PUSCH may be a CG PUSCH specific to transmitting beam reports (and may not transmit UL data / other UCI).

[0111] Furthermore, use of PUCCH and PUSCH with / without UL data as the second UL channel is being considered.

[0112] (Analysis) There are cases where UEIBR as described above has not been sufficiently considered.

[0113] For example, for the second UL channel that transmits the beam report of the above-mentioned mode A / B, when the beam report (UEIBR-CSI) is transmitted in the [DG] PUSCH / CG PUSCH (e.g., Type 1 CG PUSCH), respectively, there is insufficient consideration as to how to multiplex / map / encode the information.

[0114] Furthermore, for example, in the case where a beam report is transmitted in a [DG] PUSCH / CG PUSCH (e.g., type 1 CG PUSCH) for the second UL channel and the [DG] PUSCH / CG PUSCH collides / overlaps with a PUCCH, there has been insufficient consideration given to how information / channels are multiplexed / dropped, and to the provisions / settings for each information / channel related to multiplexing / dropping (e.g., provisions / settings for priority (e.g., whether to assign a higher or lower priority compared to other CSI / HARQ-ACKs) / beta offset, etc.).

[0115] If these considerations are not sufficient, it may not be possible to implement appropriate UEIBR that can coexist with other UL channels / signals, and it may not be possible to achieve communication with lower latency, which may result in suppression of improvements in communication quality / throughput.

[0116] Therefore, the present inventors came up with a method for solving these problems.

[0117] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0118] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

[0119] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0120] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0121] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0122] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0123] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0124] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0125] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.

[0126] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, pool, etc. may be interchangeable.

[0127] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0128] In the present disclosure, base station, gNB, and network (NW) may be read interchangeably.

[0129] In the present disclosure, a cell group, a serving cell group, a master cell group (MCG), and a secondary cell group (SCG) may be interchangeable. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interchangeable. A serving cell may be replaced with a cell that transmits a PDSCH. A candidate cell may refer to a cell that is a candidate to become a serving cell through L1 / L2 inter-cell mobility. L1L2-triggered mobility (LTM) and L1 / L2 inter-cell mobility may be interchangeable.

[0130] In the present disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within a CC, and band may be interchangeable. In the present disclosure, the terms cell, PCI, cell with an additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, and target cell may be interchangeable. The target cell may be a cell selected from multiple candidate cells. In the present disclosure, the terms switch, change, and update may be interchangeable. The serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch.

[0131] In the present disclosure, event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting, UEIBR, etc. may be read interchangeably.

[0132] In this disclosure, terms such as table, mapping, association, list, format, content, report, etc. may be read interchangeably.

[0133] In the present disclosure, the MAC CE, UCI, cell switch command, beam switch command, beam report MAC CE, and cell switch MAC CE may be read as interchangeable terms.

[0134] In the present disclosure, the UEIBR may be reported in a PUSCH (e.g., a CG PUSCH / DG PUSCH). That is, the report content in the present disclosure may be transmitted using at least one of a MAC CE / UCI / PUCCH / PUSCH.

[0135] In the present disclosure, serving may be interchangeably read as serving beam / serving cell / SpCell.

[0136] In the present disclosure, neighbor may be interpreted interchangeably as a beam / cell other than the serving beam / serving cell / SpCell / SCell.

[0137] In the present disclosure, candidate cells, target cells, neighboring cells, cells, etc. may be read interchangeably.

[0138] In the present disclosure, the occurrence of an event and the satisfaction of the conditions for the event may be read interchangeably.

[0139] In the present disclosure, beam, RS, RS index (CRI / SSBRI), and [L1 / L3] measurement results may be interchangeable.

[0140] In the present disclosure, the RS to be measured may be a QCL source RS in an active / indicated TCI state.

[0141] In the present disclosure, event-based beam reporting (for Rel. 19), event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBM), beam reporting, etc. may be read interchangeably.

[0142] In the present disclosure, the terms indicated TCI state, active TCI state, activated TCI state, configured TCI state, configured TCI state, and RS configured in RRC may be read interchangeably.

[0143] Each embodiment of the present disclosure can be applied to any event.

[0144] In the present disclosure, the terms rule, case, factor, condition, threshold, etc. may be read interchangeably.

[0145] In this disclosure, the CSI / UCI related to the UEIBR may be referred to as the UEIBR-CSI / UCI. In this disclosure, the term "other" UCI (or simply "UCI") may refer to UCI other than the CSI / UCI related to the UEIBR.

[0146] In the present disclosure, beam report, CSI report, UEIBR, CSI related to UEIBR, UEIBR-CSI, UEIBR-UCI, report, etc. may be read interchangeably.

[0147] In the present disclosure, Mode A and Mode B may be interpreted as interchangeable.

[0148] In the present disclosure, multiplexing (multiplexing / being multiplexed) and mapping (mapping / being mapped) may be read interchangeably.

[0149] In the present disclosure, the UL channel that transmits UEIBR-CSI, CG PUSCH, Type 1 CG PUSCH, Type 2 CG PUSCH, DG PUSCH, and PUSCH may be read as interchangeable.

[0150] In the present disclosure, other UL channels (transmitting other UCI), PUCCH, and PUSCH may be read as interchangeable.

[0151] (Wireless communication method) The UE may perform beam measurement / reporting (e.g., UE IBR) by applying the present disclosure. The NW / BS / gNB may provide / send to the UE settings / instructions, etc. for the UE to realize the control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive the beam report / CSI report from the UE.

[0152] The present disclosure is applicable to each of the MIMO / mobility use cases.

[0153] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0154] In the present disclosure, the collision / overlap between an UL channel (e.g., [DG] PUSCH / CG PUSCH) that transmits UEIBR-CSI and another channel (e.g., PUCCH) may mean complete collision / overlap in the time domain, or at least partial collision / overlap, and one time resource may or may not be included in the other time resource.

[0155] First Embodiment The first embodiment relates to setting a beta offset related to UEIBR.

[0156] <<Embodiment 1-1>> Embodiment 1-1 may be applied to, for example, Mode B described above.

[0157] The UE may transmit a beam report (e.g., UE IBR-CSI) using the CG PUSCH.

[0158] The UE may receive a configuration regarding a beta offset for the UEIBR-CSI (or for an UL channel carrying the UEIBR-CSI), and may control transmission of the UL channel carrying the beam report (e.g., the UEIBR-CSI) based on the configuration.

[0159] 2 is a diagram illustrating an example of a beta offset setting according to the first embodiment. In the example illustrated in FIG. 2, the UE receives a beta offset setting for the UEIBR-CSI from the NW (step S201). The UE transmits the UEIBR-CSI to the NW based on the setting (step S202).

[0160] For the setting of the beta offset for the UEIBR-CSI, at least one of the following embodiments 1-1-1 to 1-1-3 may be applied.

[0161] <<<Embodiment 1-1-1>>> There is no need to newly define additional signaling for setting the beta offset for the UEIBR-CSI.

[0162] The UE may treat (e.g., multiplex / encode) the UEIBR-CSI in the same way as a specific UCI (e.g., a specific CSI part (e.g., CSI part 1)).

[0163] For example, the UE may apply the [existing] parameters of the beta offset for a specific CSI part (eg, CSI part 1) for the CG configuration to the UEIBR-CSI.

[0164] For example, a beta offset (e.g., β CSI-1 offset ) may be provided by the BetaOffsets information element = "semiStatic".

[0165] <<<Embodiment 1-1-2>>> A specific setting for setting the beta offset for the UEIBR-CSI may be defined.

[0166] For example, the UE may be configured / provided with a [new] beta offset value using a configuration related to beta offset for UEIBR-CSI (eg, betaOffsetUEIBR).

[0167] The configuration regarding the beta offset for UEIBR-CSI (eg, betaOffsetUEIBR) may be included in, for example, a specific RRC configuration (eg, a configured grant (CG) configuration (eg, ConfiguredGrantConfig)).

[0168] A common setting for the beta offset may be defined for UEIBR Mode A and Mode B. The UE may be configured with a common beta offset value for Mode A and Mode B based on the setting.

[0169] For example, the UE may assume that the same beta offset value is configured for Mode A and Mode B, respectively.

[0170] Separate settings for the beta offset may be defined for UEIBR Mode A and Mode B. The UE may be configured with separate (different / same) beta offset values ​​for Mode A and Mode B based on the settings.

[0171] For example, the UE may assume that different (different / same) beta offset values ​​are configured for Mode A and Mode B, respectively.

[0172] <<<Embodiment 1-1-3>>> There is no need to newly define additional signaling for setting the beta offset for the UEIBR-CSI.

[0173] The UE may treat (e.g., multiplex / encode) the UEIBR-CSI in the same way as a specific UCI (e.g., HARQ-ACK).

[0174] For example, the UE may apply the [existing] parameter of beta offset for HARQ-ACK for CG configuration to the UEIBR-CSI.

[0175] For example, a beta offset for HARQ-ACK (e.g., β CSI-1 offset ) may be provided by the BetaOffsets information element = "semiStatic".

[0176] According to the above embodiment 1-1, even when a beam report is transmitted using a CG PUSCH, the beta offset can be set appropriately.

[0177] <<Embodiment 1-2>> Embodiment 1-2 may be applied to, for example, Mode A described above.

[0178] The UE may transmit a beam report (e.g., UE IBR-CSI) using the [DG]PUSCH.

[0179] The UE may receive a configuration regarding a beta offset for the UEIBR-CSI (or for an UL channel carrying the UEIBR-CSI), and may control transmission of the UL channel carrying the beam report (e.g., UEIBR-CSI) based on the configuration (see FIG. 2).

[0180] For the setting of the beta offset for the UEIBR-CSI, at least one of the following embodiments 1-2-1 to 1-2-3 may be applied.

[0181] <<<Embodiment 1-2-1>>> There is no need to newly define additional signaling for setting the beta offset for the UEIBR-CSI.

[0182] The UE may treat (e.g., multiplex / encode) the UEIBR-CSI in the same way as a specific UCI (e.g., a specific CSI part (e.g., CSI part 1)).

[0183] For example, the UE may apply the [existing] parameters of the beta offset for a specific CSI part (e.g., CSI part 1) for the [DG] PUSCH configuration (e.g., PUSCH-Config) to the UEIBR-CSI.

[0184] <<<Embodiment 1-2-2>>> A specific setting for setting the beta offset for the UEIBR-CSI may be defined.

[0185] For example, the UE may be configured / provided with a [new] beta offset value using a configuration related to beta offset for UEIBR-CSI (eg, betaOffsetUEIBR).

[0186] The configuration regarding the beta offset for UE IBR-CSI (e.g., betaOffsetUEIBR) may be included in, for example, a specific RRC configuration (e.g., [DG] PUSCH configuration (e.g., PUSCH-Config)).

[0187] <<<Embodiment 1-2-3>>> There is no need to newly define additional signaling for setting the beta offset for the UEIBR-CSI.

[0188] The UE may treat (e.g., multiplex / encode) the UEIBR-CSI in the same way as a specific UCI (e.g., HARQ-ACK).

[0189] For example, the UE may apply the [existing] parameter of beta offset for HARQ-ACK for the [DG] PUSCH configuration (e.g., PUSCH-Config) to the UE IBR-CSI.

[0190] According to the above embodiment 1-2, the beta offset can be set appropriately even when a beam report is transmitted using [DG]PUSCH.

[0191] According to the first embodiment described above, the beta offset for UEIBR-CSI can be appropriately set.

[0192] Second Embodiment The second embodiment relates to a case where a UL channel transmitting UEIBR-CSI collides / overlaps with another UL channel.

[0193] The UL channel that transmits the UEIBR-CSI may be, for example, at least one of the DG PUSCH (PUSCH) [in Mode A] and the CG PUSCH [in Mode B].

[0194] The other UL channel may be, for example, a PUCCH, and may carry [other] UCI.

[0195] For example, the UE may determine at least one of dropping the UL channel transmitting the UEIBR-CSI or other UL channels, and multiplexing / mapping UCI of other UL channels onto the UL channel transmitting the UEIBR-CSI, based on whether the UL channel transmitting the UEIBR-CSI includes UL data / UL-SCH.

[0196] In the following embodiments 2-1 and 2-2, the CG PUSCH in Mode B will be mainly described as an example, but both embodiments can also be applied to the [DG] PUSCH in Mode A.

[0197] <<Embodiment 2-1>> A UE may transmit UEIBR-CSI using a CG PUSCH without UL data (UL-SCH).

[0198] The embodiment 2-1 may be the default setting / function.

[0199] The UE may follow at least one of the following embodiments 2-1-1 to 2-1-3.

[0200] <<<<Embodiment 2-1-1>>> Multiplexing / mapping of [other] UCI to the CG PUSCH that transmits UEIBR-CSI may not be supported.

[0201] The UE may not assume / expect to multiplex / map any other UCI to the CG PUSCH that carries the UEIBR-CSI.

[0202] 3A is a diagram showing an example of support for multiplexing UCI according to embodiment 2-1-1. In the example shown in FIG. 3A, UEIBR-CSI is transmitted in CG-PUSCH without UL data / UL-SCH. In this case, UCI in PUCCH that collides / overlaps with CG-PUSCH is not supported to be multiplexed / mapped in CG-PUSCH.

[0203] <<<<Embodiment 2-1-2>>> It may be possible to support multiplexing / mapping of [other] UCI to the CG PUSCH that transmits UEIBR-CSI.

[0204] The UE may assume / expect to multiplex / map [other] UCI to the CG PUSCH that carries the UEIBR-CSI.

[0205] 3B is a diagram showing an example of support for multiplexing UCI according to embodiment 2-1-2. In the example shown in FIG. 3B, UEIBR-CSI is transmitted in CG-PUSCH without UL data / UL-SCH. At this time, UCI in PUCCH that collides / overlaps with CG-PUSCH is supported to be multiplexed / mapped in CG-PUSCH.

[0206] <<<<Embodiment 2-1-3>>> For the CG PUSCH that carries UEIBR-CSI, a [new] setting / parameter may be defined that indicates whether multiplexing / mapping of [other] UCI is supported / enabled or not.

[0207] Based on the configuration / parameters, the UE may determine whether multiplexing / mapping of [other] UCI is supported / enabled for the CG PUSCH carrying the UEIBR-CSI.

[0208] The conditions / rules for multiplexing / mapping of the [other] UCI will be described in detail in the fifth embodiment below.

[0209] In the present disclosure, support for UCI multiplexing / mapping may mean that UCI multiplexing / mapping is performed under any conditions, or may mean that whether UCI multiplexing / mapping can be performed is determined based on specific rules.

[0210] According to embodiment 2-1, it is possible to appropriately define multiplexing / mapping of [other] UCI to CG PUSCH not accompanied by UL data (UL-SCH).

[0211] <<Embodiment 2-2>> The UE may transmit the UEIBR-CSI by using a CG PUSCH with UL data (UL-SCH).

[0212] The UE may be configured using a [new] setting / parameter to determine whether or not it can transmit UEIBR-CSI in CG PUSCH with UL data (UL-SCH).

[0213] For example, if the configuration / parameters indicate that the UE IBR-CSI can be transmitted in the CG PUSCH with UL data (UL-SCH), the UE may follow this embodiment.

[0214] For example, if the setting / parameter indicates that the UE IBR-CSI cannot be transmitted in the CG PUSCH with UL data (UL-SCH), the UE may follow the above embodiment 2-1.

[0215] The UE may follow at least one of the following embodiments 2-2-1 to 2-2-3.

[0216] <<<<Embodiment 2-2-1>>> Multiplexing / mapping of [other] UCI to the CG PUSCH that transmits UEIBR-CSI may not be supported.

[0217] The UE may not assume / expect to multiplex / map any other UCI to the CG PUSCH that carries the UEIBR-CSI.

[0218] 4A is a diagram illustrating an example of support for multiplexing UCI according to embodiment 2-2-1. In the example illustrated in FIG. 4A, UEIBR-CSI is transmitted in CG-PUSCH accompanied by UL data / UL-SCH. At this time, UCI in PUCCH that collides / overlaps with CG-PUSCH is not supported to be multiplexed / mapped in CG-PUSCH.

[0219] <<<<Embodiment 2-2-2>>> It may be possible to support multiplexing / mapping of [other] UCI to the CG PUSCH that transmits UEIBR-CSI.

[0220] The UE may assume / expect to multiplex / map [other] UCI to the CG PUSCH that carries the UEIBR-CSI.

[0221] 4B is a diagram illustrating an example of support for multiplexing UCI according to embodiment 2-2-2. In the example illustrated in FIG. 4B, UEIBR-CSI is transmitted in CG-PUSCH accompanied by UL data / UL-SCH. At this time, UCI in PUCCH that collides / overlaps with CG-PUSCH is supported to be multiplexed / mapped in CG-PUSCH.

[0222] <<<Embodiment 2-2-3>>> For the CG PUSCH that carries UEIBR-CSI, a [new] setting / parameter may be defined that indicates whether multiplexing / mapping of [other] UCI is supported / enabled or not.

[0223] The setting / parameter may be a setting / parameter common to the [new] setting / parameter described in the above embodiment 2-1-3, or may be a setting / parameter that is set separately (different) from the [new] setting / parameter described in the above embodiment 2-1-3.

[0224] Based on the configuration / parameters, the UE may determine whether multiplexing / mapping of [other] UCI is supported / enabled for the CG PUSCH carrying the UEIBR-CSI.

[0225] The conditions / rules for multiplexing / mapping of the [other] UCI will be described in detail in the fifth embodiment below.

[0226] According to embodiment 2-2, multiplexing / mapping of [other] UCI to CG PUSCH with UL data (UL-SCH) can be properly defined.

[0227] <<Embodiment 2-3 (Variation of Embodiment 2-1 / 2-2)>> The multiplexing / mapping of UCI described in the above-described embodiment 2-1 / 2-2 may include multiplexing / mapping of at least one of existing (defined up to Rel. 18) / normal UCI, [other] UCI in CG PUSCH (e.g., may be referred to as CG-UCI), and UCI indicating unused transmission occasion(s) (CG PUSCH transmission opportunity) (UCI indicating unused transmission occasion(s) (UTO-UCI)).

[0228] The UE may not assume / expect a CG configuration that establishes the presence of both UEIBR-CSI and a specific UCI (eg, CG-UCI / UTO-UCI).

[0229] <<Embodiment 2-4>> A UE does not need to assume / expect collision / overlap between a UL channel (eg, PUSCH) that transmits UEIBR-CSI and another UL channel (eg, PUCCH).

[0230] The network (NW, e.g., a base station) may schedule each UL channel (e.g., PUSCH) that transmits UEIBR-CSI so that it does not collide / overlap with other UL channels (e.g., PUCCH).

[0231] According to the second embodiment, it is possible to appropriately define the multiplexing / mapping of UCI to the UL channel that transmits UEIBR.

[0232] Third Embodiment The third embodiment relates to dropping of channels / information when a UL channel carrying UEIBR-CSI collides / overlaps with another UL channel.

[0233] The third embodiment may be applied, for example, in the case where multiplexing / mapping of [other] UCI to the UL channel transmitting UEIBR-CSI is not supported / configured in the second embodiment.

[0234] The UE may decide whether to drop the UL channel carrying UEIBR-CSI (UEIBR-CSI) or other UL channels (PUCCH / [other] UCI) based on certain rules.

[0235] Fig. 5 is a diagram illustrating an example of channel dropping in the third embodiment. In the example illustrated in Fig. 5, the UE determines whether to drop a UL channel carrying UEIBR-CSI (UEIBR-CSI) or another UL channel (PUCCH / [other] UCI) that (at least partially) collide / overlap in the time domain, based on a specific rule.

[0236] The specific rule may be, for example, at least one of the following embodiments 3-1 to 3-5.

[0237] <<Embodiment 3-1>> The UE may not transmit (may drop) the [other] UCI.

[0238] The UE may transmit the UEIBR-CSI using a UL channel (e.g., CG PUSCH / [DG] PUSCH) that transmits the UEIBR-CSI.

[0239] <<Embodiment 3-2>> The UE may determine whether to transmit / drop a UL channel carrying UEIBR-CSI (UEIBR-CSI) or another UL channel ([other] UCI) based on the priority / priority index.

[0240] The UE may follow the set / defined priority / priority index, which will be described in detail in the fourth embodiment below.

[0241] The UE may transmit channels / information of higher priority / priority index and not transmit (drop) channels / information of lower priority / priority index.

[0242] When channels / information of the same priority / priority index collide / overlap, the UE may apply embodiments 3-1 / 3-3 / 3-4 / 3-5.

[0243] <<Embodiment 3-3>> The UE may determine whether to transmit / drop the UL channel carrying UEIBR-CSI (UEIBR-CSI) or the other UL channel (the other UCI) based on the type / content of the other UCI in the other UL channel (e.g., PUCCH).

[0244] <<<Embodiment 3-3-1>>> If the UCI includes [only] HARQ-ACK (if the UCI does not include CSI / SR), the UE may transmit the UCI and drop the UL channel (UEIBR-CSI) that carries the UEIBR-CSI.

[0245] <<<Embodiment 3-3-2>>> If the UCI includes [only] CSI (if the UCI does not include HARQ-ACK / SR), the UE may transmit a UL channel (UEIBR-CSI) that carries the UEIBR-CSI and drop the UCI.

[0246] <<<<Embodiment 3-3-3>>> If the UCI includes [only] SR (if the UCI does not include HARQ-ACK / CSI), the UE may transmit a UL channel (UEIBR-CSI) that transmits UEIBR-CSI and drop the UCI (SR).

[0247] <<<Embodiment 3-3-4>>> When the UCI includes HARQ-ACK and SR, the UE may transmit the UCI and drop the UL channel (UEIBR-CSI) carrying the UEIBR-CSI.

[0248] <<<Embodiment 3-3-5>>> When the UCI includes HARQ-ACK and CSI, the UE may transmit the UCI and drop the UL channel (UEIBR-CSI) carrying the UEIBR-CSI.

[0249] The channel / information selection described in the above embodiments 3-3-1, 3-3-2, 3-3-3, 3-3-4, and 3-3-5 is merely an example. For example, the UL channel (UEIBR-CSI) that transmits HARQ-ACK, CSI, SR, and UEIBR-CSI in these embodiments may be interchangeable.

[0250] For example, HARQ-ACK may be transmitted with priority over (having a higher priority than) an UL channel (UEIBR-CSI) that transmits UEIBR-CSI, and the UL channel (UEIBR-CSI) that transmits UEIBR-CSI may be transmitted with priority over (having a higher priority than) CSI.

[0251] <<Embodiment 3-4>> The UE may determine whether to transmit / drop the UL channel transmitting the UEIBR-CSI (UEIBR-CSI) or another UL channel ([other] UCI), based on whether the UL channel transmitting the UEIBR-CSI includes UL data.

[0252] <<<Embodiment 3-4-1>>> When the UL channel transmitting UEIBR-CSI includes UL data / UL-SCH, the UE may transmit the UL channel transmitting UEIBR-CSI (UEIBR-CSI) and drop the UCI.

[0253] <<<Embodiment 3-4-2>>> If the UL channel transmitting UEIBR-CSI does not include UL data / UL-SCH, the UE may transmit the UCI and drop the UL channel transmitting UEIBR-CSI (UEIBR-CSI).

[0254] The channel / information selection described in the above embodiments 3-4-1 and 3-4-2 is merely an example. For example, the UL channel (UEIBR-CSI) that transmits UCI and UEIBR-CSI in these embodiments may be interchangeable.

[0255] <<Embodiment 3-5>> At least two of the above-described embodiments 3-1 to 3-4 may be combined.

[0256] For example, the UE may decide whether to transmit / drop the UL channel carrying UEIBR-CSI (UEIBR-CSI) or other UL channels ([other] UCI) based on at least two of the following: specification provisions, priority / priority index, type / content of UCI, and presence or absence of UL data / UL-SCH.

[0257] <<Embodiment 3-6 (Variation)>> RRC parameters corresponding to at least one of the above-described embodiments 3-1 to 3-5 may be configured for the UE.

[0258] The RRC parameter may, for example, configure whether or not any of the above embodiments is enabled.

[0259] The RRC parameters may be configured based on the UE capability reports.

[0260] For example, if a parameter is configured that enables transmission / dropping of channels / information based on the configured priority / priority index, the UE may apply the above embodiment 3-2.

[0261] For example, if a parameter enabling dropping an UL channel (e.g., CS PUSCH) including UL data / UL-SCH is configured, the UE may decide to drop the UL channel (e.g., CS PUSCH) including UL data / UL-SCH.

[0262] The UCI described in at least the above embodiments 3-1 to 3-6 may include at least one of existing (defined up to Rel. 18) / normal UCI, CG UCI, and UTO-UCI.

[0263] The UE may assume / determine that a common transmit / drop rule applies regardless of the matching event (e.g., regardless of event 1 / 2 / 7).

[0264] The UE may assume / determine that different (different) transmit / drop rules apply based on the matching event (e.g., whether it is event 1, 2, or 7).

[0265] For example, transmission of an UL channel (UEIBR-CSI) carrying UEIBR-CSI relating to a particular event (e.g., event 2) may be prioritized over transmission of an UL channel (UEIBR-CSI) carrying UEIBR-CSI relating to another event (e.g., event 1 / 7).

[0266] According to the third embodiment described above, even when the UL channel transmitting the UEIBR-CSI collides / overlaps with other UL channels, it is possible to appropriately determine the channel / information to transmit / drop.

[0267] <Fourth Embodiment> The fourth embodiment relates to a priority index.

[0268] A priority / priority index for the UL channel carrying the UEIBR-CSI (e.g., CG PUSCH / [DG] PUSCH) or for the UEIBR-CSI may be defined.

[0269] <<Embodiment 4-1>> The priority / priority index may be set using RRC signaling.

[0270] The priority index may be, for example, a specific value (for example, a specific value between 0 and 1).

[0271] If the priority index is not configured, the UE may assume that the priority / priority index for the UL channel (e.g., CG PUSCH / [DG] PUSCH) carrying the UEIBR-CSI or for the UEIBR-CSI is a default value (e.g., 1 (or 0)).

[0272] <<Embodiment 4-2>> The priority / priority index may be defined as a specific value (for example, 1 (or 0)) (without configuring RRC signaling).

[0273] For example, if the configuration of the UL channel that transmits UEIBR-CSI (e.g., CG configuration (ConfiguredGrantConfig)) is for UEIBR-CSI, the UE may assume that the priority index configuration (e.g., phy-PriorityIndex) within that configuration is [always] set to a specific value (e.g., 1 (or 0)).

[0274] For example, if the configuration (e.g., CG configuration (ConfiguredGrantConfig)) of the UL channel transmitting UEIBR-CSI is for UEIBR-CSI and no priority index configuration (e.g., phy-PriorityIndex) is provided within the configuration, the UE may assume that the priority of the UL channel transmitting UEIBR-CSI is [always] a specific value (e.g., 1 (or 0)).

[0275] <<Embodiment 4-3 (Variation)>> The priority / priority index for a UL channel (e.g., CG PUSCH / [DG] PUSCH) that transmits UEIBR-CSI or for UEIBR-CSI may be a newly defined / set value (e.g., 2).

[0276] According to the fourth embodiment described above, the priority / priority index for UEIBR-CSI can be appropriately defined / set.

[0277] Fifth Embodiment The fifth embodiment relates to multiplexing / mapping of channels / information when a UL channel transmitting UEIBR-CSI and another UL channel collide / overlap.

[0278] The fifth embodiment may be applied, for example, in the case where multiplexing / mapping of [other] UCI to the UL channel transmitting UEIBR-CSI is supported / configured in the second embodiment.

[0279] In addition, the UE may apply this embodiment when a specific timeline condition (for example, an existing timeline condition (defined up to Rel. 18)) is satisfied.

[0280] The UE may determine the multiplexing / mapping of other UL channels (other UCI) to the UL channel carrying UEIBR-CSI (UEIBR-CSI) based on a specific rule.

[0281] The specific rule may be, for example, at least one of the following embodiments 5-1 to 5-4.

[0282] <<Embodiment 5-1>> The UE may determine whether to multiplex / map (or drop) the [other] UCI onto the UL channel (UEIBR-CSI) that transmits the UEIBR-CSI, based on the configured / defined priority / priority index.

[0283] For example, if the priority / priority index of the UL channel (UEIBR-CSI) transmitting the UEIBR-CSI is the same as the priority / priority index of another UL channel ([other] UCI), the UE may assume / decide to multiplex / map the [other] UCI onto the UL channel transmitting the UEIBR-CSI.

[0284] For example, if the priority / priority index of the UL channel (UEIBR-CSI) carrying the UEIBR-CSI is different from the priority / priority index of other UL channels ([other] UCI), the UE may follow at least one of the methods described in the third embodiment above.

[0285] <<Embodiment 5-2>> The UE may determine whether to multiplex / map (or drop) the [other] UCI onto the UL channel (UEIBR-CSI) that transmits the UEIBR-CSI, based on the type / content of the UCI.

[0286] For example, when the UCI includes [only] HARQ-ACK and / or when the UCI includes at least HARQ-ACK, the UE may assume / decide to multiplex / map the [other] UCI onto the UL channel that transmits the UE IBR-CSI.

[0287] For example, if the UCI includes [only] CSI / SR, the UE may assume / decide to multiplex / map (or not) the [other] UCI onto the UL channel that transmits the UE IBR-CSI.

[0288] <<Embodiment 5-3>> The UE may determine whether to multiplex / map (or drop) [other] UCI onto the UL channel (UEIBR-CSI) transmitting the UEIBR-CSI, based on whether the UL channel transmitting the UEIBR-CSI includes UL data / UL-SCH.

[0289] For example, if the UL channel transmitting the UEIBR-CSI includes UL data / UL-SCH, the UE may assume / decide to multiplex / map (or not) the [other] UCI onto the UL channel transmitting the UEIBR-CSI.

[0290] For example, if the UL channel transmitting the UEIBR-CSI does not include UL data / UL-SCH, the UE may assume / decide not to (or will) multiplex / map the [other] UCI onto the UL channel transmitting the UEIBR-CSI.

[0291] <<Embodiment 5-4>> At least two of the above-described embodiments 5-1 to 5-3 may be combined.

[0292] For example, the UE may determine whether to multiplex / map (or drop) the [other] UCI onto the UL channel (UEIBR-CSI) transmitting the UEIBR-CSI based on at least two of the following: priority / priority index, type / content of the UCI, and the presence or absence of UL data / UL-SCH.

[0293] <<Embodiment 5-5 (Variation)>> When the above-mentioned [other] UCI multiplexing / mapping is not performed, the rules regarding dropping / transmission described in the above-mentioned third embodiment may be applied.

[0294] RRC parameters corresponding to at least one of the above embodiments 5-1 to 5-4 may be configured for the UE.

[0295] The RRC parameter may, for example, configure whether or not any of the above embodiments is enabled.

[0296] The RRC parameters may be configured based on the UE capability reports.

[0297] For example, if a parameter that enables multiplexing / mapping of UCI based on a set priority / priority index is set, the UE may apply the above embodiment 5-1.

[0298] For example, if a parameter enabling multiplexing / mapping of UCI in the case of different priorities / priority indices is configured, the UE may decide to perform multiplexing / mapping for different priorities / priority indices.

[0299] The UE may assume / determine that a common multiplexing / mapping rule applies regardless of the matching event (e.g., regardless of whether it is event 1 / 2 / 7).

[0300] Based on the matching event (e.g., whether it is event 1, 2, or 7), the UE may assume / determine that different (different) multiplexing / mapping rules apply.

[0301] According to the fifth embodiment described above, even when the UL channel transmitting UEIBR-CSI and other UL channels collide / overlap, it is possible to appropriately determine the multiplexing of UCI.

[0302] Sixth Embodiment The sixth embodiment relates to a UCI multiplexing / mapping procedure.

[0303] This embodiment may be applied, for example, to the case where multiplexing / mapping of UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) transmitting UEIBR-CSI) and [other] UCI is performed, as in the second / fifth embodiments.

[0304] The UE may control the multiplexing / mapping of UEIBR-CSI / UCI based on the priority / priority index (or difference) between the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) transmitting the UEIBR-CSI) and the [other] UCI.

[0305] <<Embodiment 6-1>> The priority / priority index of the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) that transmits the UEIBR-CSI) and the [other] UCI may be the same.

[0306] The UE may multiplex / map the UL channel ([DG] PUSCH / CG PUSCH) carrying the UEIBR-CSI as a specific UCI type.

[0307] <<<Embodiment 6-1-1>>> The specific UCI type may be, for example, CSI part 1 (or part 2).

[0308] The UE may multiplex / map the UEIBR-CSI using the same multiplexing / mapping method as that for CSI Part 1 (or Part 2) in the UCI (HARQ-ACK / CSI / SR) multiplexing / mapping method.

[0309] The UCI multiplexing / mapping method may be, for example, an existing UCI multiplexing / mapping method (defined up to Rel. 18).

[0310] The UE may multiplex / map UEIBR-CSI by replacing / reading CSI Part 1 (or Part 2) in the existing UCI multiplexing / mapping method (specified up to Rel. 18) with UEIBR-CSI.

[0311] For example, the UE may reuse the existing UCI multiplexing / mapping method (defined up to Rel. 18) by treating both CSI Part 1 (or Part 2) and UEIBR-CSI (if any) as CSI Part 1 (or Part 2).

[0312] In this case, the UE may determine to apply the beta offset value for CSI part 1 to the UL channel ([DG] PUSCH / CG PUSCH) that transmits the UE IBR-CSI (as in higher-level embodiment 1-1-1).

[0313] <<<Embodiment 6-1-2>>> The specific UCI type may be, for example, HARQ-ACK.

[0314] The UE may multiplex / map the UEIBR-CSI using the same method as the multiplexing / mapping of HARQ-ACK in the multiplexing / mapping method of UCI (HARQ-ACK / CSI / SR).

[0315] The UCI multiplexing / mapping method may be, for example, an existing UCI multiplexing / mapping method (defined up to Rel. 18).

[0316] The UE may multiplex / map UEIBR-CSI by replacing / reading HARQ-ACK in the existing UCI multiplexing / mapping method (defined up to Rel. 18) with UEIBR-CSI.

[0317] For example, the UE may reuse the existing UCI multiplexing / mapping method (defined up to Rel. 18) by treating both HARQ-ACK and UE IBR-CSI (if any) as HARQ-ACK.

[0318] In this case, the UE may determine to apply the beta offset value for HARQ-ACK to the UL channel ([DG] PUSCH / CG PUSCH) that transmits the UE IBR-CSI (as in higher-level embodiment 1-1-3).

[0319] Also, for example, if HARQ-ACK is multiplexed / mapped (in addition to UEIBR-CSI), the UE may apply the beta offset value for HARQ-ACK to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI. Otherwise, the UE may apply the beta offset value for UEIBR-CSI to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI.

[0320] According to embodiment 6-1, even if the priority / priority index of the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) that transmits the UEIBR-CSI) and the [other] UCI are the same, the UEIBR-CSI and the [other] UCI can be multiplexed / mapped appropriately.

[0321] <<Embodiment 6-2>> The priority / priority index of the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) that transmits the UEIBR-CSI) and the [other] UCI may be different.

[0322] The UE may multiplex / map the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) carrying the UE IBR-CSI) of a configured / defined (specific) priority index as a specific UCI type of the specific priority index.

[0323] <<<Embodiment 6-2-1>>> The specific UCI type for the specific priority index may be, for example, CSI part 1 (or part 2) for the corresponding priority index.

[0324] The UE may multiplex / map the UEIBR-CSI of a configured / specified (specific) priority index using the same method as the multiplexing / mapping of CSI Part 1 (or Part 2) of the corresponding priority index in the UCI (HARQ-ACK / CSI / SR) multiplexing / mapping method.

[0325] The UCI multiplexing / mapping method may be, for example, an existing UCI multiplexing / mapping method (defined up to Rel. 18).

[0326] The UE may multiplex / map UEIBR-CSI by replacing / reading CSI part 1 (or part 2) of the corresponding priority index in the existing UCI multiplexing / mapping method (specified up to Rel. 18) with UEIBR-CSI of the configured / specified (specific) priority index.

[0327] For example, the UE may multiplex / map the UEIBR-CSI with priority index 0 as CSI part 1 (or part 2) with priority index 0.

[0328] For example, the UE may multiplex / map the UEIBR-CSI with priority index 1 as CSI part 1 (or part 2) with priority index 1.

[0329] The UE may decide to apply the beta offset value for CSI Part 1 (or Part 2) of the corresponding priority index to the UL channel ([DG] PUSCH / CG PUSCH) carrying the UE IBR-CSI.

[0330] Also, for example, if CSI Part 1 (or Part 2) of the corresponding priority index is multiplexed / mapped (in addition to UEIBR-CSI), the UE may apply the beta offset value for CSI Part 1 (or Part 2) of the corresponding priority index to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI. Otherwise, the UE may apply the beta offset value for UEIBR-CSI to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI.

[0331] <<<Embodiment 6-2-2>>> The specific UCI type for the specific priority index may be, for example, CSI part 1 (or part 2) for a priority index of a specific value.

[0332] The specific value may be, for example, 1 (or 0 or any other value).

[0333] The UE may multiplex / map the UEIBR-CSI of a configured / specified (specific) priority index using the same method as the multiplexing / mapping of CSI Part 1 (or Part 2) of a specific priority index in the UCI (HARQ-ACK / CSI / SR) multiplexing / mapping method.

[0334] The UCI multiplexing / mapping method may be, for example, an existing UCI multiplexing / mapping method (defined up to Rel. 18).

[0335] The UE may multiplex / map UEIBR-CSI by replacing / reading CSI part 1 (or part 2) of a specific priority index in the existing UCI multiplexing / mapping method (specified up to Rel. 18) with UEIBR-CSI of a (specific) priority index that is set / specified.

[0336] The UE may decide to apply a beta offset value for CSI Part 1 (or Part 2) of a particular priority index to the UL channel ([DG] PUSCH / CG PUSCH) that carries the UE IBR-CSI.

[0337] Also, for example, when CSI Part 1 (or Part 2) of a specific priority index is multiplexed / mapped (in addition to UEIBR-CSI), the UE may apply the beta offset value for CSI Part 1 (or Part 2) of the specific priority index to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI. Otherwise, the UE may apply the beta offset value for UEIBR-CSI to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI.

[0338] <<<Embodiment 6-2-3>>> The specific UCI type for the specific priority index may be, for example, HARQ-ACK for the corresponding priority index.

[0339] The UE may multiplex / map the UEIBR-CSI of a configured / specified (specific) priority index using the same method as the multiplexing / mapping of HARQ-ACK of the corresponding priority index in the UCI (HARQ-ACK / CSI / SR) multiplexing / mapping method.

[0340] The UCI multiplexing / mapping method may be, for example, an existing UCI multiplexing / mapping method (defined up to Rel. 18).

[0341] The UE may multiplex / map UEIBR-CSI by replacing / reading the HARQ-ACK of the corresponding priority index in the existing UCI multiplexing / mapping method (specified up to Rel. 18) with UEIBR-CSI of the configured / specified (specific) priority index.

[0342] For example, the UE may multiplex / map the UEIBR-CSI with priority index 0 as the HARQ-ACK with priority index 0.

[0343] For example, the UE may multiplex / map the UEIBR-CSI with priority index 1 as the HARQ-ACK with priority index 1.

[0344] The UE may determine to apply the beta offset value for HARQ-ACK of the corresponding priority index to the UL channel ([DG] PUSCH / CG PUSCH) that carries the UE IBR-CSI.

[0345] Also, for example, if HARQ-ACK of the corresponding priority index is multiplexed / mapped (in addition to UEIBR-CSI), the UE may apply the beta offset value for HARQ-ACK of the corresponding priority index to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI. Otherwise, the UE may apply the beta offset value for UEIBR-CSI to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI.

[0346] <<<Embodiment 6-2-4>>> The specific UCI type for the specific priority index may be, for example, a HARQ-ACK for a priority index of a specific value.

[0347] The specific value may be, for example, 1 (or 0 or any other value).

[0348] The UE may multiplex / map the UEIBR-CSI of a configured / specified (specific) priority index using the same method as the multiplexing / mapping of HARQ-ACK of a specific priority index in the UCI (HARQ-ACK / CSI / SR) multiplexing / mapping method.

[0349] The UCI multiplexing / mapping method may be, for example, an existing UCI multiplexing / mapping method (defined up to Rel. 18).

[0350] The UE may multiplex / map UEIBR-CSI by replacing / reading HARQ-ACK with a specific priority index in the existing UCI multiplexing / mapping method (specified up to Rel. 18) with UEIBR-CSI with a (specific) priority index that is set / specified.

[0351] The UE may determine to apply a beta offset value for HARQ-ACK of a particular priority index to the UL channel ([DG] PUSCH / CG PUSCH) that transmits the UE IBR-CSI.

[0352] Also, for example, when a HARQ-ACK with a specific priority index is multiplexed / mapped (in addition to the UEIBR-CSI), the UE may apply a beta offset value for the specific HARQ-ACK to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI. Otherwise, the UE may apply a beta offset value for the UEIBR-CSI to the UL channel ([DG]PUSCH / CG PUSCH) carrying the UEIBR-CSI.

[0353] According to embodiment 6-2, even if the priorities / priority indices of the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) that transmits the UEIBR-CSI) and the [other] UCI are different, the UEIBR-CSI and the [other] UCI can be multiplexed / mapped appropriately.

[0354] According to the sixth embodiment described above, UEIBR-CSI and [other] UCI can be multiplexed / mapped appropriately based on the priority / priority index of the UEIBR-CSI (UL channel ([DG] PUSCH / CG PUSCH) that transmits the UEIBR-CSI)) and the [other] UCI.

[0355] Seventh Embodiment (Variation) In the rules for multiplexing / mapping / transmission / dropping described in the second, third, and fifth embodiments, (presence or absence of) multiplexing / mapping / transmission / dropping may be determined further based on at least one of the following factors / conditions: - The number of HARQ-ACK bits (for example, whether it is greater than 2 bits, or whether it is greater than 11 bits); - The number of CSI bits; - The number of UEIBR-CSI bits; - Whether the UCI type / content of CSI is CSI Part 1 [only], or CSI Part 1 and CSI Part 2; - Whether the UCI type / content of SR is a specific SR for UEIBR (Mode A / B); - Event ID / event type.

[0356] A rule based on at least one of these factors / conditions may be defined, and at least one of these factors / conditions may be additionally used in the judgment in the above-described embodiments.

[0357] For example, in the case of a drop between a specific SR for UEIBR and an UL channel (e.g., CG PUSCH) carrying UEIBR-CSI, the UE may transmit (or drop) the SR and drop (or transmit) the UL channel.

[0358] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0359] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0360] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0361] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0362] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0363] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0364] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0365] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0366] <<Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: - A higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured. - The specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters. - The specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS. - A specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported. - The application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0367] The specific UE capabilities may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments. - Supporting UEIBR. - Supporting MIMO / mobility for Rel. 19 and later. - Supporting UEIBR with MAC CE / UCI. - Supporting event combinations. - Total / aggregate number of beams reported. - Number of beams meeting the conditions. - Supporting UEIBR with 2-part UCI / 1-part UCI. - Supporting one or more pre-configured resources for the second UL channel for UEIBR. - Supporting specific beta offset configuration for UEIBR-CSI (in [DG] PUSCH / CG PUSCH). Support multiplexing / mapping of [other] UCI in [DG] PUSCH / CG PUSCH carrying UEIBR-CSI with / without UL data / UL-SCH. Support RRC configuration to enable / disable multiplexing / mapping of [other] UCI in [DG] PUSCH / CG PUSCH carrying UEIBR-CSI. Support dropping of [DG] PUSCH / CG PUSCH carrying UEIBR-CSI or [other] UCI for specific cases. Support configuration / specification of priority / priority index for [DG] PUSCH / CG PUSCH carrying UEIBR-CSI. Support multiplexing / mapping of [other] UCI for specific collision / overlap cases (taking into account conditions / factors separately for each case).

[0368] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0369] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0370] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0371] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1-1] A terminal having a receiving unit that receives a configuration related to a beta offset for an uplink (UL) channel that transmits a beam report initiated by the terminal, and a control unit that controls transmission of the UL channel that transmits the beam report based on the configuration related to the beta offset. [Supplementary Note 1-2] The terminal according to Supplementary Note 1-1, wherein the control unit applies a beta offset value for specific uplink control information to the UL channel. [Supplementary Note 1-3] The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the UL channel is a Physical Uplink Shared Channel (PUSCH) based on a dynamic grant or a PUSCH based on a configured grant. [Supplementary Note 1-4] The terminal according to any one of Supplements 1-1 to 1-3, wherein the receiving unit determines to drop the UL channel or another UL channel that overlaps with the UL channel based on a priority index for the UL channel. [Supplementary Note 2-1] A terminal having: a control unit that controls at least one of dropping an uplink (UL) channel or another UL channel overlapping with the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel, based on whether the UL channel transmitting a beam report initiated by the terminal includes UL data; and a transmission unit that transmits the UL channel or the other UL channel. [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, wherein the UL channel is a physical uplink shared channel (PUSCH) based on a dynamic grant or a PUSCH based on a configured grant. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein the control unit determines at least one of the dropping and the mapping based on a parameter that enables mapping of the UCI to the UL channel. [Supplementary Note 2-4] The terminal according to any one of Supplementary Note 2-1 to Supplementary Note 2-3, wherein the UCI includes at least one of a UCI based on a configured grant and a UCI indicating an unused transmission opportunity.[Supplementary Note 3-1] A terminal having: a control unit that, when an uplink (UL) channel transmitting a beam report initiated by the terminal overlaps with another UL channel, controls at least one of dropping the UL channel or the other UL channel and mapping uplink control information (UCI) of the other UL channel to the UL channel based on a specific rule; and a transmission unit that transmits the UL channel or the other UL channel. [Supplementary Note 3-2] The terminal according to Supplementary Note 3-1, wherein the control unit controls the dropping based on at least one of a priority index, a UCI type, and whether the UL channel includes UL data. [Supplementary Note 3-3] The terminal according to Supplementary Note 3-1 or Supplementary Note 3-2, wherein the control unit controls the mapping based on at least one of a priority index, a UCI type, and whether the UL channel includes UL data. [Supplementary Note 3-4] The terminal according to any one of Supplementary Note 3-1 to Supplementary Note 3-3, wherein the control unit controls the mapping based on a priority index of the UL channel and a priority index of the other UL channel.

[0372] (Wireless Communication System) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0373] 6 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0374] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0375] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0376] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0377] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as the base station 10.

[0378] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

[0379] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0380] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.

[0381] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0382] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0383] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0384] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

[0385] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0386] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0387] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0388] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0389] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0390] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0391] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0392] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0393] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0394] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0395] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0396] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0397] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0398] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0399] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0400] 7 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0401] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0402] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0403] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0404] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0405] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0406] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0407] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0408] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0409] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0410] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0411] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

[0412] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.

[0413] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0414] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0415] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0416] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0417] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0418] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0419] The transceiver 120 may transmit a setting regarding a beta offset for an uplink (UL) channel that transmits a beam report initiated by the terminal, and the control unit 110 may control reception of the UL channel that transmits the beam report, which is transmitted based on the setting regarding the beta offset (first embodiment).

[0420] The control unit 110 may determine whether to perform at least one of dropping an uplink (UL) channel or another UL channel overlapping with the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel, based on whether the UL channel transmitting a beam report initiated by the terminal includes UL data. The transceiver unit 120 may receive the UL channel or the other UL channel (second embodiment).

[0421] When an uplink (UL) channel transmitting a beam report initiated by a terminal overlaps with another UL channel, the control unit 110 may determine at least one of dropping the UL channel or the other UL channel and mapping uplink control information (UCI) of the other UL channel to the UL channel, which are performed based on a specific rule. The transceiver unit 120 may receive the UL channel or the other UL channel (third / fifth embodiments).

[0422] (User Terminal) Fig. 8 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0423] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0424] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0425] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.

[0426] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0427] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0428] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0429] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0430] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0431] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0432] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0433] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0434] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

[0435] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.

[0436] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0437] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0438] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0439] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0440] The transceiver 220 may receive a setting regarding a beta offset for an uplink (UL) channel that transmits a beam report initiated by the terminal, and the controller 210 may control transmission of the UL channel that transmits the beam report based on the setting regarding the beta offset (first embodiment).

[0441] The control unit 210 may apply a beta offset value for specific uplink control information to the UL channel (first embodiment).

[0442] The UL channel may be a Physical Uplink Shared Channel (PUSCH) based on a dynamic grant or a PUSCH based on a configured grant (first embodiment).

[0443] The transceiver unit 220 may determine whether to drop the UL channel or other UL channels that overlap with the UL channel based on the priority index for the UL channel (third and fourth embodiments).

[0444] The control unit 210 may control at least one of dropping an uplink (UL) channel or another UL channel overlapping the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel, based on whether the UL channel transmitting a beam report initiated by the terminal includes UL data. The transceiver unit 220 may transmit the UL channel or the other UL channel (second embodiment).

[0445] The UL channel may be a Physical Uplink Shared Channel (PUSCH) based on a dynamic grant or a PUSCH based on a configured grant (second embodiment).

[0446] The control unit 210 may determine at least one of the dropping and the mapping based on a parameter that enables mapping of the UCI to the UL channel (second embodiment).

[0447] The UCI may include at least one of UCI based on a configured grant and UCI indicating an unused transmission opportunity (second embodiment).

[0448] When an uplink (UL) channel transmitting a beam report initiated by a terminal overlaps with another UL channel, the control unit 210 may control at least one of dropping the UL channel or the other UL channel and mapping uplink control information (UCI) of the other UL channel to the UL channel based on a specific rule. The transceiver unit 220 may transmit the UL channel or the other UL channel (third, fifth, and sixth embodiments).

[0449] The control unit 210 may control the dropping based on at least one of a priority index, a UCI type, and whether the UL channel includes UL data (third embodiment).

[0450] The control unit 210 may control the mapping based on at least one of a priority index, a UCI type, and whether the UL channel includes UL data (fifth embodiment).

[0451] The control unit 210 may control the mapping based on the priority index of the UL channel and the priority index of the other UL channel (sixth embodiment).

[0452] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0453] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0454] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0455] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0456] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0457] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0458] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0459] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0460] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0461] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0462] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0463] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0464] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0465] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0466] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

[0467] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0468] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0469] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0470] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

[0471] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0472] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0473] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0474] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0475] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0476] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0477] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0478] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0479] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0480] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0481] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0482] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0483] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0484] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0485] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0486] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0487] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0488] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0489] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0490] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0491] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0492] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

[0493] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0494] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0495] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0496] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0497] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0498] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0499] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0500] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0501] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0502] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0503] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0504] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0505] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0506] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0507] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0508] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0509] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0510] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

[0511] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0512] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0513] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0514] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0515] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0516] 10 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0517] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0518] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0519] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0520] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0521] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0522] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0523] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0524] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0525] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0526] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0527] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0528] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0529] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0530] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0531] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0532] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0533] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0534] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0535] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0536] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0537] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0538] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0539] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0540] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0541] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0542] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0543] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0544] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0545] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0546] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0547] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0548] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0549] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0550] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal having a control unit that controls at least one of dropping an uplink (UL) channel or another UL channel that overlaps with the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel, based on whether the UL channel transmitting a beam report initiated by the terminal includes UL data; and a transmission unit that transmits the UL channel or the other UL channel.

2. The terminal of claim 1, wherein the UL channel is a physical uplink shared channel (PUSCH) based on a dynamic grant or a PUSCH based on a configured grant.

3. The terminal according to claim 1, wherein the control unit determines at least one of the dropping and the mapping based on a parameter that enables mapping of the UCI to the UL channel.

4. The terminal of claim 1, wherein the UCI includes at least one of UCI based on a configured grant and UCI indicating an unused transmission opportunity.

5. A wireless communication method for a terminal, comprising: a step of controlling at least one of dropping an uplink (UL) channel or another UL channel that overlaps with the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel, based on whether the UL channel transmitting a beam report initiated by the terminal includes UL data; and a step of transmitting the UL channel or the other UL channel.

6. A base station having: a control unit that determines, based on whether or not an uplink (UL) channel transmitting a beam report initiated by a terminal includes UL data, to perform at least one of dropping the UL channel or another UL channel that overlaps with the UL channel, and mapping uplink control information (UCI) of the other UL channel to the UL channel; and a receiving unit that receives the UL channel or the other UL channel.

Images