Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a transmission unit that transmits a first uplink (UL) channel which provides notification of a second UL channel for transmitting a beam report (UEIBR) that is started by the terminal; and a control unit that controls UL transmission in accordance with a specific rule when the second UL channel and another UL channel overlap in a time domain.

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] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and 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] In a future wireless communication system (for example, NR, Rel. 19 and later), it is being considered to support UE-initiated Beam Report (UEIBR) initiated by a terminal (user terminal, User Equipment (UE)) (event-based).

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

[0007] However, there are cases where the UEIB (Unified Interconnected Network) has not been adequately considered. If this consideration is insufficient, it may not be possible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.

[0008] Therefore, one of the objectives of this 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 includes a transmitting unit that transmits a first UL channel that notifies a second uplink (UL) channel for transmitting beam reports (UEIBR) initiated by the terminal, and a control unit that controls UL transmission according to specific rules when the second UL channel and other UL channels overlap in the time domain.

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

[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of collision / overlap between specific channels / signals of this disclosure. Figure 3 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 4 shows an example of a base station configuration according to one embodiment. Figure 5 shows an example of a user terminal configuration according to one embodiment. Figure 6 shows an example of a hardware configuration of a base station and user terminal according to one embodiment. Figure 7 shows an example of a vehicle according to one embodiment.

[0012] (NR PUSCH) PUSCH as defined in NR Rel. 15 and later is broadly classified into dynamic grant-based transmission and configured grant-based transmission.

[0013] Dynamic grant (DG)-based transmission is a method of performing PUSCH (Physical Uplink Shared Channel) transmission based on dynamic UL grants (DG, dynamic UL grant, DCI). This PUSCH may be called, for example, DG PUSCH.

[0014] Configured grant (CG)-based transmission is a method of performing push transmissions based on UL grants (which may also be called configured grants or configured UL grants) set up by higher layers. With configured grant-based transmission, UL resources are already allocated to the UE, and the UE can spontaneously perform push transmissions using the configured resources, thus enabling low-latency communication.

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

[0016] Several types of CG push transmissions (such as Type 1 and Type 2) are defined.

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

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

[0019] CG parameters may be set in the UE using the ConfiguredGrantConfig information element of the RRC. CG parameters may include, for example, information that identifies the CG resource. CG parameters may include, for example, information about the CG index, time offset, periodicity, the number of repetitions of the Transport Block (TB) (the number of repetitions may be expressed as K), the Redundancy Version (RV) series used for repetitions, and the timers mentioned above.

[0020] Here, the period and time offset may be expressed in units such as symbols, slots, subframes, and frames, respectively. The period may be represented, for example, by a predetermined number of symbols. The time offset may be represented, 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, for example, 1, 2, 4, 8, etc. If the number of repeated transmissions is n (>0), the UE may transmit a predetermined TB using n transmission opportunities via CG PUSCH.

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

[0022] If a UE is configured to transmit a CG type 2 and a predetermined activation signal is notified, it may determine that one or more CGs have been triggered (or activated). The predetermined activation signal (e.g., an activation DCI) may be a DCI (PDCCH) that is scrambled with a predetermined identifier (e.g., CS-RNTI: Configured Scheduling RNTI) using a Cyclic Redundancy Check (CRC). The DCI may also be used to control CG deactivation, retransmission, etc.

[0023] The UE may determine whether or not to perform a PUSCH transmission using the CG resources configured in the upper layer, based on the predetermined activation signal described above. The UE may release (or deactivate, etc.) the resources (PUSCH) corresponding to the configuration grant based on the DCI that deactivates the CG or the expiration of a predetermined timer (elapsed time).

[0024] The UE may perform a PUSCH transmission without a DG using an activated CG-based transmission resource (which may also be called a CG resource or transmission occasion). However, even if CG-based transmission is activated, the UE may skip the CG-based transmission if there is no data in the transmit buffer.

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

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

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

[0028] The UE determines the number / quantity of resources (e.g., the number of encoded modulation symbols per layer) for transmitting the above UCI based on the beta offset. The beta offset is β Ｏｆｆｓｅｔ It may also be expressed as such, and may differ depending on the type or content of the UCI (e.g., HARQ-ACK, CSI Part 1, CSI Part 2). Furthermore, the transmit power of the PUSCH including the UCI may be determined based on the beta offset.

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

[0030] The set of information elements for multiple beta offsets (BetaOffsets IE) includes the following seven parameters that indicate the index for the beta offsets.

[0031] The parameters betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 indicate indices for the beta offset that apply when transmitting HARQ-ACKs of up to 2 bits, up to 11 bits, and greater than 11 bits in PUSCH, respectively.

[0032] The parameters betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 indicate indices for the beta offset applied when transmitting CSI Part 1 up to 11 bits and greater than 11 bits in PUSCH, respectively.

[0033] The parameters betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 indicate indices for the beta offset applied when transmitting CSI Part 2 up to 11 bits and greater than 11 bits in PUSCH, respectively.

[0034] The UE (User Encoder) refers to one index within a 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. The correspondence between the index and the beta offset value is defined by the standard. This correspondence may differ for each type of UCI.

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

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

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

[0038] The UCI-OnPUSCH information element (UCI-OnPUSCH IE) defined in Rel. 15 / 16 NR may include a betaOffsets parameter and a scaling parameter. If the betaOffsets parameter includes "dynamic," it indicates that dynamic beta offsets are used for DCI formats other than DCI format 0_2, and if it includes "semiStatic," it indicates that quasi-static beta offsets are used for DCI formats other than DCI format 0_2. "dynamic" includes four (i.e., four) betaOffsets information elements, 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) defined in Rel. 16 NR indicates the betaOffsets parameter (betaOffsetsDCI-0-2) and the scaling parameter (scalingDCI-0-2) for DCI format 0_2. It differs from the UCI-OnPUSCH information element in that, for dynamic beta offsets, a beta offsets information element of size 2 can be set instead of a beta offsets information element of size 4. 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 quasi-static beta offset is set, the size of the beta offset indicator field included in DCI format 0_2 is still 0 bits.

[0041] In Rel. 16 NR, the UE may be configured by a higher-layer parameter (pdsch-HARQ-ACK-CodebookList) to generate two HARQ-ACK codebooks. In this case, the UE may be configured by a list (UCI-OnPUSCH-ListDCI-0-1-r16) to have two UCI-OnPUSCH information elements (UCI-OnPUSCH IE) for DCI format 0_1. The UE may also be configured by a list (UCI-OnPUSCH-ListDCI-0-2-r16) to have two UCI-OnPUSCH-DCI-0-2 information elements (UCI-OnPUSCH-DCI-0-2 IE) 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] Note that the first HARQ-ACK codebook is related to the Physical Uplink Control Channel (PUCCH) with a priority index of 0, and the second HARQ-ACK codebook is related to the PUCCH with a priority index of 1. The higher the value of the priority index, the higher the priority. The priority will be described later.

[0043] The actual UL grant of the CG PUSCH is set by RRC signaling (ConfiguredGrantConfig information element) in the case of type 1 CG PUSCH, and provided by PDCCH (DCI) in the case of type 2 CG PUSCH.

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

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

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

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

[0048] Note that 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 after Rel. 16, multiple levels (e.g., two levels) of priority can be set for signals / channels. For example, it is assumed that communication is controlled (e.g., transmission control at the time of collision) by setting different priorities for signals / channels corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.). Thereby, for the same signal / channel, communication control based on different priorities can be performed according to the service type, etc.

[0050] Priorities may be set / defined for at least one of the following: information (e.g., UCI, channel status information (CSI)), channels (e.g., Physical Downlink Shared Channel (PDSCH), PUSCH, PUCCH, etc.), reference signals (e.g., CSI-RS, SRS, etc.), and the HARQ-ACK codebook. Furthermore, different priorities may be set for the PUCCH used for SR transmission, the PUCCH used for HARQ-ACK transmission, and the PUCCH used for CSI transmission.

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

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

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

[0054] Additionally, a priority (priority index (e.g., p0 (e.g., 0) or p1 (e.g., 1))) may be assigned to DG PUSCH, CG PUSCH, etc.

[0055] Priority information may be communicated 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 set by a higher-layer parameter (e.g., schedulingRequestPriority). The priority of HARQ-ACK for a PDSCH scheduled by a DCI (e.g., dynamic PDSCH) may be communicated by the DCI. The priority of HARQ-ACK for an SPS PDSCH may be set by a higher-layer parameter (e.g., HARQ-ACK-Codebook-indicator-forSPS) or communicated by a DCI instructing the activation of an SPS PDSCH.

[0056] Aperiodic CSI (A-CSI) / Semi-persistent CSI (SP-CSI) transmitted via PUCCH may be assigned a predetermined priority (e.g., low). On the other hand, the priority of aperiodic CSI (A-CSI) / SP-CSI transmitted via PUCCH may be notified by DCI (e.g., trigger DCI or activation DCI).

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

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

[0059] Multiple UL signals / UL channels overlap when the time resources (or time resources and frequency resources) of multiple UL signals / UL channels overlap, or when the transmission timings of multiple UL signals / UL channels overlap. Time resources may be interpreted as time domains or time areas. Time resources may be in units of symbols, slots, subslots, or subframes.

[0060] The overlap of multiple UL signals / UL channels within the same UE (e.g., intra-UE) may mean that the multiple UL signals / UL channels overlap in at least the same time resource (e.g., symbol). Conversely, the collision of UL signals / UL channels in different UEs (e.g., inter-UE) may mean that the multiple UL signals / UL channels overlap in the same time resource (e.g., symbol) and frequency resource (e.g., RB).

[0061] For example, if multiple UL signals / UL channels with the same priority overlap, the UE may control the transmission of these multiple UL signals / UL channels by multiplexing them into a single UL channel.

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

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

[0064] If UL data / HARQ-ACK (or a UL channel for transmitting UL data / HARQ-ACK) with a first priority (high) set and UL data / HARQ-ACK (or a UL channel for transmitting UL data / HARQ-ACK) with a second priority (low) set overlap, the UE may control the system to drop the lower-priority UL data / HARQ-ACK and prioritize the transmission of the higher-priority UL data / HARQ-ACK. The UE may also change the transmission timing of the lower-priority UL transmission (e.g., postpone or shift it).

[0065] If more than two (or three or more) UL signals / UL channels overlap in the time domain, transmission may be controlled in two steps. Step 1 selects one UL channel that multiplexes the UL signals transmitted by UL transmissions of the same priority. Step 2 may control transmissions with different priorities so that higher priority UL transmissions are transmitted first and lower priority UL transmissions are dropped.

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

[0067] (Simultaneous / multiplexing of UL transmissions with different priorities) It is also possible that multiple UL transmissions sent from different carriers (or cells, CCs) overlap in the time domain, and that the priorities of the multiple UL transmissions differ.

[0068] For example, if UL channels / UL signals are scheduled on different carriers in an inter-cell supported by different RF (Radio Frequency) frequencies, transmitting each UL channel / UL signal is useful from the standpoint of reducing latency and spectral efficiency. If a UE supports RF processing for different carriers (CCs), transmitting UL channels / UL signals on each carrier can improve resource utilization efficiency and reduce latency.

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

[0070] Alternatively, when multiple UL transmissions with different priorities are scheduled within a cell (intra-cell) or between cells (inter-cell), multiplexing of UL transmissions with different priorities (for example, transmitting using the same UL channel) may be supported. For example, multiple UL transmissions may be supported by multiplexing a UL transmission of one priority onto a UL channel intended for UL transmissions of other priorities.

[0071] Whether or not a UCI (e.g., HARQ-ACK) is multiplexed / mapped to a UL channel with a different priority than the UCI (e.g., PUSCH) (e.g., enable / disable, or activate / deactivate) may be configured by higher-layer signaling.

[0072] In Rel. 17, when multiplexing a lower-priority HARQ-ACK (LP HARQ-ACK) against a higher-priority PUSCH (HP PUSCH), the beta offset of 0 < 1 is supported. Furthermore, it is supported to set different beta offset indexes for the cases where LP HARQ-ACK is multiplexed with HP PUSCH, and for the cases where HP HARQ-ACK is multiplexed with LP PUSCH, compared to other cases.

[0073] For example, beta offsets information elements for LP HARQ-ACK multiplexed in HP Dynamic PUSCH (which may be called, for example, BetaOffsetsCrossPri0 IE) and beta offsets information elements for HP HARQ-ACK multiplexed in LP Dynamic PUSCH (which may be called, for example, BetaOffsetsCrossPri1 IE) are defined. These beta offsets information elements may include parameters equivalent to betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 of existing beta offsets information elements (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: betaOffsets parameters up to 15 (betaOffsets), betaOffsets parameters for DCI format 0_2 (betaOffsetsDCI-0-2), and parameters / information elements in which existing betaoffsets information elements (BetaOffsets IE) in CG-UCI-OnPUSCH information elements (CG-UCI-OnPUSCH IE) are replaced with the above 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 transmissions to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 procedures are possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may be simply referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive.

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

[0077] (1) The UE receives from the serving cell the SSB settings for beam measurement of the TRP corresponding to a PCI different from that of the serving cell, and the settings necessary to use wireless resources for data transmission and reception, including 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) status 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 a dedicated channel on the TRP corresponding to the different PCI. (5) The UE must always cover the serving cell, including in the case of multiple TRPs. The UE must use a common channel from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc., as in conventional systems.

[0078] In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the UE's assumption of the serving cell) remains unchanged. The UE sets higher-layer parameters related to the PCI of the non-serving cell 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. It assumes a UE moving from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support L1 / L2 switching of serving cells.

[0080] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. UEs can receive and transmit UE-dedicated channels from additional cells. UEs need to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). If a UE moves outside the coverage of the serving cell, a cell switch is required, such as through a handover (also called L3 mobility).

[0081] <Scenario 2> In Scenario 2, L1 / L2 cell mobility is applied. With L1 / L2 cell mobility, serving cell changes can be made using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with additional cells are possible without handover. Since handover requires RRC reconnection and other factors, resulting in a period of no data communication, applying L1 / L2 cell mobility that does not require handover allows data communication to continue 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 the SSB configuration of a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement on the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration of the cell with the different PCI (serving cell configuration) by upper layer signaling (e.g., RRC). In other words, a pre-configuration regarding the serving cell change may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI state of the cell with the different PCI may be activated by 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 receiving / transmitting using the pre-configured UE-specific channel and TCI state.

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

[0084] Figure 1B shows an example of UE movement in Rel. 18. In Rel. 18, serving cells are switched by L1 / L2 (e.g., DCI / MAC CE). UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell (or target serving cell). UEs may leave the coverage of the current serving cell (e.g., Current serving cell).

[0085] (UE-initiated Beam Report (UEIBR)) In future wireless communication systems (e.g., Rel. 19 and beyond), support for event-based beam reporting is being considered. Event-based beam reporting may also be called event-triggered beam reporting, or UE-initiated beam reporting (UEIBR).

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

[0087] At UEIBR, the report content is being considered to include at least one of the following pieces of information in the beam report: • Beam / reference signal index (e.g., CSI-RS / SSB resource index / indicator). • Measurement result (e.g., L1-RSRP / SINR (absolute / relative)). • Number of beams / RSs reported. • Whether or not serving beams are included in the beam report.

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

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

[0090] In this case, the UCI may be encoded in two parts. For example, the size of the second part of the UCI may be indicated by the first part of the UCI (which may have a fixed size).

[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 falls below a certain threshold. • Event 2: The quality of at least one new beam (e.g., L1-RSRP) is better than a certain threshold compared to the quality of the current beam. • Event 3: The quality of a new beam is better than a certain threshold. • Event 4: The quality of the current beam falls below a first threshold, and the quality of at least one new beam is better than a second threshold. • Event 5: The absolute difference between the quality of the current beam and the quality of at least one new beam falls below a certain threshold. • Event 6: The current beam is no longer included in the best K beams (more than 1: K > 1) (of the beams set up for measurement / reporting). - Event 7: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the RS derived from the best quality activated TCI state up to the Mth (M is 1 or greater, and M may be set by RRC). - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) is above the threshold of the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the set reference RS (which may be SSB / CSI-RS).

[0092] Note that this type of event does not exclude the events described above. For example, this type of event may be interpreted as equivalent to the events described above as appropriate.

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

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

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

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

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

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

[0099] In mode A, a 1-bit instruction in at least the first UL channel (PUCCH) may be supported to request resources on the second UL channel for transmitting beam reports.

[0100] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0101] <<Mode B>> Mode B relates to the UCI in the 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 a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.

[0103] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (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 mode B, a one-bit instruction on at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel will transmit a beam report.

[0106] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0107] In either mode A or B as described above, 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., type 1 CG PUSCH).

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

[0110] Furthermore, the CG PUSCH may be a dedicated CG PUSCH for transmitting beam reports (it does not need to transmit UL data / other UCI).

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

[0112] (Collision / Overlap of PUSCH#A / #B) Regarding UE behavior when PUSCH#A / #B collide / overlap, existing rules stipulate the following: - Collisions between DG PUSCH#A and DG PUSCH#B are avoided by the gNB implementation. - When CG PUSCH#A and CG PUSCH#B collide, it is determined by the UE implementation. - When CG PUSCH#A / #B and DG PUSCH#B / #A collide, DG PUSCH#B / #A takes precedence if certain time conditions (timeline) are met.

[0113] Furthermore, if PUSCH#A, which has a semi-persistent CSI, and PUSCH#B, which has data, collide, PUSCH#A will not be transmitted (and PUSCH#A will not be multiplexed into PUSCH#B) if certain time conditions (timeline) are met.

[0114] (Collision / Overlap of SRS and PUSCH) Regarding UE behavior when SRS and PUSCH collide / overlap, existing rules stipulate the following:

[0115] For example, if CC#1's SRS and CC#2's PUSCH collide / overlap, at least one of the following actions may be applied: - The UE drops the PUSCH that transmits / carries a periodic / semi-persistent CSI. - If the UE collides with an aperiodic SRS, it drops the PUSCH that transmits / carries an aperiodic CSI.

[0116] (Analysis) In the above-mentioned UEIBR modes A and B, collisions / overlaps between specific channels / signals are expected during the transmission of UL channels / signals (which may also be simply called UL transmission).

[0117] For example, when a Mode A beam report (UEIBR-CSI) is transmitted on the second UL channel, a DG PUSCH scheduled by a specific DCI (e.g., DCI format 0_1 / 0_2) may be used.

[0118] Alternatively, if a Mode B beam report (UEIBR-CSI) is transmitted on the second UL channel, CG PUSCH may be used.

[0119] The following are examples of cases where collisions / overlaps occur between specific channels / signals.

[0120] (Case 1) Collision / overlap between a PUSCH (i.e., the second UL channel) with beam reporting (UEIBR-CSI) (transmitting / carrying) and another PUSCH (which may be any UL channel).

[0121] (Case 2) Collision / overlap between PUSCH (i.e., second UL channel) and SRS (UL signal) accompanied by beam reporting (UEIBR-CSI).

[0122] (Case 3) Collision / overlap between PUSCH (i.e., second UL channel) with beam reporting (UEIBR-CSI) and SR / UCI for UEIBR (i.e., may be the first UL channel).

[0123] However, there are no clear regulations to support these cases. Without such clear regulations, UEs may not be able to properly perform UEIB (the network may not be able to recognize the appropriate beams / RS to be updated), and thus lower latency communication may not be achievable, potentially hindering improvements in communication quality / throughput.

[0124] Therefore, the inventors of this invention conceived a way to solve these problems.

[0125] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0126] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0127] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0128] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0129] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0130] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0131] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0132] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0133] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.

[0134] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, and pool may be interpreted interchangeably.

[0135] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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 relationship group, Code Division Multiplexing (CDM) group, Reference Signal group, CORESET group, Physical Uplink Control The following terms may be interchangeable: 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.

[0136] In this disclosure, base station, gNB, and network (NW) may be interpreted as interchangeable.

[0137] In this disclosure, cell group, serving cell group, master cell group (MCG), and secondary cell group (SCG) may be interpreted interchangeably. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interpreted interchangeably. A serving cell may be replaced with a cell that transmits PDSCH. A candidate cell may mean a candidate cell that becomes a serving cell through L1 / L2 inter-cell mobility. L1 / L2-triggered mobility (LTM) and L1 / L2 inter-cell mobility may be interpreted interchangeably.

[0138] In this disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, cell, PCI, cell with 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 current serving cell's PCI, another serving cell, and target cell may be interpreted interchangeably. A target cell may be a cell selected from among several candidate cells. In this disclosure, switch, change, and update may be interpreted interchangeably. A serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.

[0139] In this disclosure, event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, and UE-initiated beam reporting may be interpreted interchangeably.

[0140] In this disclosure, event-triggered beam reporting may simply be referred to as beam reporting / CSI reporting / L1-RSRP / SINR beam reporting.

[0141] In this disclosure, the Type 1 beam report and the beam report for in-cell beam switching may be interpreted as interchangeable.

[0142] In this disclosure, Type 2 beam reporting and inter-cell beam reporting may be interpreted interchangeably.

[0143] In this disclosure, the type 2-1 beam report and the beam report for inter-cell beam switching may be interpreted as interchangeable.

[0144] In this disclosure, the type 2-2 beam report and the beam report for cell switching may be interpreted as interchangeable.

[0145] In this disclosure, tables, mappings, associations, lists, formats, content, reports, etc., may be interpreted interchangeably.

[0146] In this disclosure, the (new) MAC CE, UCI, cell switching command, beam switching command, MAC CE for beam reporting, and MAC CE for cell switching may be interpreted as interchangeable.

[0147] In this disclosure, event-based beam reporting may be reported using PUSCH (e.g., config-grant PUSCH, grant-based PUSCH). That is, the reporting content in this disclosure may be transmitted using at least one of MAC CE / UCI / PUCCH / PUSCH.

[0148] In this disclosure, the CSI report and the report may be interpreted interchangeably.

[0149] In this disclosure, "report," "reporting resources," and "resources" may be interpreted interchangeably. For example, the first resource and the first report may be interpreted interchangeably, and the second resource and the second report may be interpreted interchangeably.

[0150] In this disclosure, the number of beams and the number of resources may be interpreted interchangeably.

[0151] In this disclosure, ACK may be referred to as an affirmative response and NACK as a negative response. In this disclosure, NACK may be information indicating a first value (e.g., 0 (or 1)), and ACK may be information indicating a second value (e.g., 1 (or 0)).

[0152] In this disclosure, "Serving" may be interpreted as "Serving beam," "Serving cell," or "SpCell."

[0153] In this disclosure, "Neighbor" may be interpreted as any beam or cell other than a serving beam / serving cell / SpCell / SCell.

[0154] In this disclosure, the RS index and the L1-RSRP / SINR pair may be referred to as the L1 measurement report. That is, the L1 measurement report may include the RS index and the L1-RSRP / SINR pair.

[0155] In this disclosure, candidate cells, target cells, adjacent cells, cells, etc., may be interpreted interchangeably.

[0156] In this disclosure, the phrases "an event occurred" and "the conditions for the event were met" may be interpreted interchangeably.

[0157] In this disclosure, the beam, RS, and [L1 / L3] measurement results may be interpreted interchangeably.

[0158] In this disclosure, the measured RS may be the QCL source RS in an active TCI state / indicated TCI state.

[0159] In this disclosure, spatial domain filters, temporal domain filters, and domain filters may be interpreted as interchangeable.

[0160] In this disclosure, NW / BS / gNB may be interpreted as interchangeable.

[0161] In this disclosure, the CSI report and the beam report may be interpreted interchangeably.

[0162] In this disclosure, the terms event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBMM), beam reporting, etc., [for Rel. 19] may be interpreted interchangeably.

[0163] In this disclosure, the current beam / new beam may correspond to at least one of the following: indicated TCI state, indicated TCI state, active TCI state, activated TCI state, set TCI state, and RS set in RRC.

[0164] In this disclosure, indicated TCI state, active TCI state, activated TCI state, set TCI state, configured TCI state, and RS configured in RRC may be interpreted interchangeably.

[0165] In this disclosure, the number of current beams / new beams may be one or more.

[0166] In this disclosure, the terms "new beam / RS," "candidate beam / RS," "measurement beam / RS," "beam for measurement / RS," etc., may be interpreted interchangeably.

[0167] In this disclosure, a novel type of UCI (novel UCI) may mean a UCI that is transmitted in multiple bits (and multiple steps / parts).

[0168] Each embodiment of this disclosure is applicable to any event.

[0169] In this disclosure, L1-RSRP may be interpreted as L1-SINR.

[0170] In this disclosure, conditions and thresholds may be interpreted interchangeably.

[0171] In this disclosure, the filtered value (measured value: L1-RSRP), the filtered value, and the L1-RSRP to which filtering by NW settings has been applied (NW-filtered L1-RSRP) may be interpreted interchangeably.

[0172] In this disclosure, beam report, UEIBR, UEIBR report, and simply report may be interpreted interchangeably.

[0173] In this disclosure, Mode A and Mode B may be interpreted as interchangeable.

[0174] In this disclosure, CC, carrier, cell, serving cell, frequency, frequency carrier, carrier frequency, etc., may be interpreted interchangeably. In this disclosure, reporting of multiple CCs may be interpreted interchangeably with reporting of multiple events.

[0175] In this disclosure, UCI and MAC CE may be interpreted as containers used in UEIBR interchangeably.

[0176] In this disclosure, reporting of a (current / measured) beam may mean reporting of the RS index (e.g., CSI-RS resource indicator (CRI) / SSB resource indicator (SSBRI)) and measurement results (e.g., L1-RSRP / RSRQ / SINR) corresponding to the (current / measured) beam. In this disclosure, information about a beam may mean the RS index / measurement results corresponding to the beam.

[0177] In this disclosure, “current beam” may mean “current beam of the current serving cell” in mobility.

[0178] In this disclosure, beam, RS, RS resource, RS resource set, RS index, RS indicator, RS ID, etc. may be interpreted interchangeably. In this disclosure, RS resource set, subset of RS resource, subset of RS, etc. may be interpreted interchangeably.

[0179] In this disclosure, the type of CSI reporting may be periodic, semi-persistent, or aperiodic. In other words, this disclosure is applicable to any type of CSI reporting.

[0180] In this disclosure, multiplexing (to multiplex / to be multiplexed) and mapping (to map / to be mapped) may be interpreted interchangeably.

[0181] In this disclosure, the UL channel for transmitting UEIBR-CSI, CG PUSCH, type 1 CG PUSCH, type 2 CG PUSCH, DG PUSCH, and PUSCH may be interpreted as being interchangeable.

[0182] In this disclosure, other UL channels, PUCCH, and PUSCH [for transmitting other UCIs] may be interpreted as interchangeable.

[0183] In this disclosure, steps 2 and 3 in mode A may be collectively referred to as step 2. That is, steps 2 and 3 in mode A may be interpreted as interchangeable.

[0184] (Wireless Communication Method) Embodiments of this disclosure can be classified as follows according to the cases of collision / overlap between specific channels / signals described above: • First embodiment: Case 1 (Second UL channel and other UL channels). • Second embodiment: Case 2 (Second UL channel and SRS). • Third embodiment: Case 3 (Second UL channel and first UL channel). • Fourth embodiment: Case 4 (Mode A and Mode B). The following will be explained based on these.

[0185] The UE may apply this disclosure to perform beam measurement / reporting (e.g., UEIBR). The NW / BS / gNB may provide / transmit to the UE settings / instructions, etc., for the UE to implement such control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive the beam report / CSI report from the UE.

[0186] This disclosure is applicable to various MIMO / mobility use cases.

[0187] In this disclosure, each embodiment / option may be applied individually or in combination with others.

[0188] In this disclosure, the multiple events may be any of the events described above (or a combination of multiple events).

[0189] In this disclosure, Mode A and Mode B may be interpreted as interchangeable. Step 1 in Mode A / Mode B may be interpreted as interchangeable. Step 3 in Mode A and Step 2 in Mode B may be interpreted as interchangeable.

[0190] In this disclosure, collisions / overlaps between specific channels / signals may mean complete collisions / overlaps in the time domain (transmission opportunities), or at least partial collisions / overlaps, and one time resource may or may not be included in the other time resource.

[0191] A specific channel may be PUSCH / PUCCH, and a specific signal may be SRS. However, the specific channel / signal may be any other channel / signal.

[0192] In this disclosure, the first UL channel may be a PUCCH that notifies / requests the second UL channel, and the second UL channel may be, for example, a DG / CG PUCCH.

[0193] <First Embodiment> The first embodiment relates to Case 1 (the second UL channel and other UL channels).

[0194] In Case 1, the UE may control UL transmission (multiplexing / dropping, etc.) in accordance with the existing rules described above or the following rules.

[0195] In the first embodiment, other UL channels are represented by PUSCH#A, and a second UL channel with beam reporting (UEIBR-CSI) is represented by PUSCH#B.

[0196] The first embodiment can be classified into several cases depending on the type of PUSCH#A / #B. The UE may control UL transmission according to each case. Figure 2 shows an example of collision / overlap between specific channels / signals of the present disclosure.

[0197] <<Case 1-1>> Case 1-1 concerns a case where DG PUSCH#A and DG PUSCH#B collide / overlap.

[0198] (Opt1) The UE may follow existing rules. In this case, the UE may treat PUSCH#B for UEIBR in the same way as the existing DG PUSCH#B. That is, the UE does not expect DG PUSCH#A and DG PUSCH#B to collide / overlap [or be scheduled to].

[0199] (Opt2) UE may be scheduled by a later (second) DCI to transmit DG PUSCH#B (with UEIBR-CSI) which overlaps in time with the transmission opportunity of DG PUSCH#A scheduled by the earlier (first) DCI, provided that certain time conditions (timeline) are met (see Figure 2).

[0200] In other words, if certain conditions are met, UE may schedule DG PUSCH#B overlapping with DG PUSCH#A by a second DCI.

[0201] The specific time conditions (timeline) may refer to the timeline for scheduling DG PUSCH#B.

[0202] <<Case 1-2>> Case 1-2 concerns a case where DG PUSCH#A and CG PUSCH#B collide / overlap.

[0203] (Opt1) The UE may follow existing rules. That is, the UE may prioritize DG PUSCH#A if certain time conditions (timeline) are met. In other words, the UE may drop CG PUSCH#B.

[0204] (Opt2) UE may send CG PUSCH#B with UEIBR-CSI even if the specific time conditions (timeline) for scheduling DG PUSCH#A are met.

[0205] In other words, UE may prioritize CG PUSCH#B over DG PUSCH#A (may transmit it preferentially).

[0206] (Variations) In Case 1-2, whether the UE sends / drops either DG PUSCH#A or CG PUSCH#B, or whether to apply either Opt1 or Opt2, may be determined according to at least one of the following conditions: - The priority index of PUSCH#A / #B. - Whether PUSCH#A is accompanied by (sent) data (UL-SCH). - Whether PUSCH#A is accompanied by (sent) periodic / aperiodic / semi-persistent CSI.

[0207] Furthermore, the priority of whether the UE sends / drops either DG PUSCH#A or CG PUSCH#B, or whether to apply either Opt1 or Opt2, may be set / instructed by upper-layer signaling / physical-layer signaling.

[0208] <<Case 1-3>> Cases 1-3 concern the case where CG PUSCH#A and DG PUSCH#B collide / overlap.

[0209] The UE may follow existing rules. That is, the UE may prioritize DG PUSCH#B if certain time conditions (timeline) are met. In other words, the UE may drop CG PUSCH#A.

[0210] <<Case 1-4>> Case 1-4 concerns the case where CG PUSCH#A and CG PUSCH#B collide / overlap.

[0211] (Opt1) The UE may follow its implementation. That is, it may prioritize one of CG PUSCH#A or #B (transmit it preferentially). In other words, the UE may drop the other of CG PUSCH#A or #B. Alternatively, the UE may not send either CG PUSCH#A or #B.

[0212] (Opt2) UE may send CG PUSCH#B accompanied by UEIBR-CSI.

[0213] In other words, UE may prioritize CG PUSCH#B over CG PUSCH#A (may transmit it preferentially).

[0214] (Variations) In cases 1-2, whether the UE sends / drops either DG PUSCH#A or CG PUSCH#B, or whether it applies either Opt1 or Opt2, may be determined according to specific conditions (e.g., priority index of PUSCH#A / #B).

[0215] Furthermore, the priority of whether the UE sends / drops either CG PUSCH#A or CG PUSCH#B, or whether to apply either Opt1 or Opt2, may be set / instructed by upper-layer signaling / physical-layer signaling.

[0216] <<Case 1-5>> Cases 1-5 concern the case where PUSCH#A and DG PUSCH#B, which transmit / carry a semi-persistent CSI (SP-CSI), collide / overlap.

[0217] If certain time conditions (timeline) are met, the UE does not need to send PUSCH#A (and does not multiplex PUSCH#A to PUSCH#B). In this case, the UE may prioritize DG PUSCH#B (it may send it preferentially).

[0218] <<Case 1-6>> Case 1-6 concerns a case where PUSCH#A and CG PUSCH#B, which are (transmitting / carrying) semi-persistent CSI (SP-CSI), collide / overlap.

[0219] The UE does not need to send PUSCH#A (and does not multiplex PUSCH#A into PUSCH#B). In this case, the UE may prioritize DG PUSCH#B (it may send it preferentially).

[0220] <<Note>> UE capabilities to support collision handling for each of the above cases may be introduced. If such UE capabilities are not supported, the UE does not need to expect the collision handling described herein (scheduling / UE operation, etc., corresponding to each case).

[0221] Which option to apply in each case may be predefined by the specification, or it may be set / instructed by upper-layer signaling / physical layer signaling.

[0222] For example, in a particular case among the above cases (e.g., case 1-1 / 1-2), the UE may treat PUSCH#B [with UEIBR-CSI] as a normal / existing DG / CG PUSCH and control UL transmission by applying existing rules.

[0223] The specific time conditions (timeline) described above for scheduling PUSCH#B are such that the end [timing] of the second DCI is at least a predetermined time (N) before the start [timing] of PUSCH#A. ２ The symbol may be before (see Figure 2). If the time condition is met, the UE may multiplex PUSCH#B over PUSCH#A. That is, PUSCH#B may override PUSCH#A scheduled by the first DCI.

[0224] (Variation) The second DCI multiplexing rule may be applied to any two DG PUSCHs. Alternatively, the second DCI multiplexing rule may be applied only to the DG PUSCH (second UL channel) that transmits / carries the UEIBBR-CSI.

[0225] According to this embodiment, the UE operation when specific channels / signals (e.g., DG / CG PUSCH#A / #B) collide / overlap becomes clear. The UE can appropriately control the UEIBR in the case of collision / overlap. As a result, lower latency communication can be achieved, and communication quality / throughput can be improved.

[0226] <Second Embodiment> The second embodiment relates to Case 2 (Second UL Channel and SRS).

[0227] In Case 2, the UE may control UL transmission (multiplexing / dropping, etc.) in accordance with the existing rules described above or the following rules.

[0228] In the second embodiment, the SRS is represented by SRS#A, and the second UL channel with beam reporting (UEIBR-CSI) is represented by PUSCH#B.

[0229] The second embodiment can be classified into several cases depending on the type of PUSCH#B. The UE may control UL transmission according to each case.

[0230] <<Case 2-1>> Case 2-1 concerns a case where SRS#A and DG PUSCH#B collide / overlap.

[0231] (Opt1) The UE may drop the transmission of SRS#A and transmit DG PUSCH#B. In other words, the UE may prioritize DG PUSCH#B over SRS#A (transmit it preferentially).

[0232] (Opt2) The UE may apply different actions depending on the type of SRS (periodic / semi-persistent / aperiodic).

[0233] For example, a UE may drop an SRS#A transmission if the SRS[type] is periodic / semi-persistent. In this case, the UE may only transmit an SRS#A if the SRS[type] is aperiodic.

[0234] Alternatively, the UE may drop sending PUSCH#B if the SRS [type] is aperiodic. In this case, the UE may only send PUSCH#B if the SRS [type] is periodic / semi-persistent.

[0235] <<Case 2-2>> Case 2-2 concerns a case where SRS#A and CG PUSCH#B collide / overlap.

[0236] (Opt1) The UE may drop the transmission of SRS#A and transmit CG PUSCH#B. In other words, the UE may prioritize CG PUSCH#B over SRS#A (transmit it preferentially).

[0237] (Opt2) The UE may apply different actions depending on the type of SRS (periodic / semi-persistent / aperiodic).

[0238] For example, a UE may drop an SRS#A transmission if the SRS[type] is periodic / semi-persistent. In this case, the UE may only transmit an SRS#A if the SRS[type] is aperiodic.

[0239] Alternatively, the UE may drop sending PUSCH#B if the SRS [type] is aperiodic. In this case, the UE may only send PUSCH#B if the SRS [type] is periodic / semi-persistent.

[0240] Aperiodic SRS#A may be preferred over CG PUSCH#B because it is not triggered by gNB.

[0241] <<Note>> In the second embodiment, different options may be applied depending on the type (DG / CG) of PUSCH#B.

[0242] UE capabilities to support collision handling for each of the above-described cases may be introduced. If such UE capabilities are not supported, the UE does not need to expect the collision handling described herein (scheduling / UE operation, etc., corresponding to each case).

[0243] Which option to apply in each case may be predefined by the specification, or it may be set / instructed by upper-layer signaling / physical layer signaling.

[0244] For example, in the above cases (Case 2-1 / 2-2), the UE may treat PUSCH#B [with UEIBR-CSI] as a normal / existing DG / CG PUSCH and control UL transmission by applying existing rules.

[0245] According to this embodiment, the UE operation when specific channels / signals (e.g., SRS#A and DG / CG PUSCH#B) collide / overlap becomes clear. The UE can appropriately control the UEIBR in the case of collision / overlap. As a result, lower latency communication can be achieved, and communication quality / throughput can be improved.

[0246] <Third Embodiment> The third embodiment relates to Case 3 (the second UL channel and the first UL channel).

[0247] Case 3 may more specifically be the case in which the first UL channel of Mode A / Mode B (Step 1) and the second UL channel of Mode A / Mode B (Step 3 / Step 2) collide.

[0248] In the third embodiment, the first UL channel is represented by PUCCH#A, and the second UL channel that transmits / carries beam reports (UEIBR-CSI) is represented by PUSCH#B. As described above, the first UL channel may be a PUCCH that notifies / requests the second UL channel and may include scheduling requests for the UEIBR (UEIBR-SR) / new UCI types.

[0249] In Case 3, the UE may control UL transmission (multiplexing / dropping, etc.) in accordance with the existing rules described above or the following rules.

[0250] (Alt1) The UE may send PUSCH#B and drop PUCCH#A. In other words, the UE may prioritize sending PUSCH#B over PUCCH#A.

[0251] (Alt2) The UE may send PUSCH#B and drop PUCCH#A only if at least one of the following conditions is met. That is, the UE may prioritize PUSCH#B over PUCCH#A (send it preferentially) only if at least one of the following conditions is met.

[0252] - PUSCH#B (UEIBR-CSI) and PUCCH#A (UEIBR-SR / new UCI type) are associated with the same CC / event. - At least one CC / event associated with PUSCH#B (UEIBR-CSI) and at least one CC / event associated with PUCCH#A (UEIBR-SR / new UCI type) are the same.

[0253] (Note) UE may apply the same or different options / behaviors depending on the collision / overlap case (whether PUSCH involves UEIBBR-CSI or whether PUCCH includes UEIBBR-SR / new UCI type / normal SR).

[0254] UE capabilities to support collision handling in the above-described cases may be introduced. If such UE capabilities are not supported, the UE does not need to expect the collision handling described herein (scheduling / UE operation, etc., corresponding to each case).

[0255] In the cases described above, which option (Alt1 / Alt2) to apply may be predefined by the specification, or it may be set / instructed by upper-layer signaling / physical-layer signaling.

[0256] For example, in the above case, UE may treat PUSCH#B [with UEIBR-CSI] as a normal / existing DG / CG PUSCH and control UL transmission by applying existing rules.

[0257] According to this embodiment, the UE operation when specific channels / signals (e.g., PUSCH#A and DG / CG PUSCH#B) collide / overlap becomes clear. The UE can appropriately control the UEIBR in the case of collision / overlap. As a result, lower latency communication can be achieved, and communication quality / throughput can be improved.

[0258] <Fourth Embodiment> The fourth embodiment relates to Case 4 (Mode A and Mode B).

[0259] <<Case 4-1>> The UE does not expect mode A and mode B to be set simultaneously. This operation may be applied in the following units: - Per BWP / CC. - Any BWP / CC within a single cell group. - Any BWP / CC in a single UE.

[0260] <<Case 4-2>> UE may be set to both Mode A and Mode B simultaneously.

[0261] If collisions / overlaps occur between different modes, a priority order for each mode (between Mode A and Mode B) may be defined. The rules regarding the priority of Mode A and Mode B may be predefined by the specification, or they may be set / instructed by upper-layer signaling / physical-layer signaling.

[0262] The following are examples of collision / overlap cases between different modes.

[0263] (Example 1) If step 1 of mode A (first UL channel, i.e., PUCCH) and step 1 of mode B (first UL channel, i.e., PUCCH) collide / overlap, mode A may take precedence, or mode B may take precedence.

[0264] (Example 2) If step 1 of mode A (first UL channel, i.e., PUCCH) and step 2 of mode B (second UL channel, i.e., CG PUSCH) collide / overlap, mode A may take precedence, or mode B may take precedence.

[0265] (Example 3) If step 3 of mode A (second UL channel, i.e., DG PUSCH) and step 1 of mode B (first UL channel, i.e., PUCCH) collide / overlap, mode A may take precedence, or mode B may take precedence.

[0266] (Example 4) If step 3 of mode A (second UL channel, i.e., DG PUSCH) and step 2 of mode B (second UL channel, i.e., CG PUSCH) collide / overlap, mode A may take precedence, or mode B may take precedence.

[0267] In each of the above cases, mode A may be set to take precedence, or mode B may be set to take precedence.

[0268] According to this embodiment, the priority between Mode A and Mode B becomes clear. The UE can appropriately control the UEIBR according to this priority.

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

[0270] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0271] If the above 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 the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0272] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0273] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0274] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0275] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0276] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0277] <<Regarding the Application of Each Embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set. - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter. - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS. - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported. - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0278] The specific UE capabilities described above may include at least one of the following: • Supporting specific processing / operations / controls / information for at least one of the embodiments described above; • Supporting UCI-based event-triggered beam reporting (UEIBR); • Supporting MIMO / mobility Rel. 19 and later; • Supporting Mode A / Mode B of the UEIBR; • Supporting the priority index of this disclosure; • Supporting the multiplexing / dropping rules (methods) of this disclosure; • Supporting shared settings for other uses / purposes for the SR; • Supporting PUCCH format 0 / 1; • Supporting 1-bit / 2-bit UCI; • Supporting one or more settings (maximum number of supported settings); • Supporting the same / different settings for each mode (Mode A / Mode B); • Supporting specific events (e.g., events 2, 1, 7 (7a / 7b)); • Supporting one or more events in the UEIBR. - Support for one or more CCs in UEIBR. - Support for one or more event combinations and one or more CCs in UEIBR.

[0279] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0280] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

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

[0282] (Note) The following inventions are added with respect to one embodiment of the present disclosure (first embodiment): [Note 1] A terminal having: a transmitting unit that transmits a first UL channel that notifies a second uplink (UL) channel for transmitting a beam report (UEIBR) initiated by the terminal; and a control unit that controls UL transmission according to specific rules when the second UL channel and other UL channels overlap in the time domain. [Note 2] The terminal according to Note 1, wherein the second UL channel is a dynamic grant physical uplink shared channel (DG PUSCH) or a configured grant PUSCH (CG PUSCH), and the other UL channel is a DG PUSCH, a CG PUSCH, or a PUSCH with semi-persistent CSI. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit controls to preferentially transmit either the second UL channel or the other UL channel when specific time conditions are met. [Note 4] When the other UL channel scheduled by the first downlink control information (DCI) and the second UL channel scheduled by the second DCI overlap, if the end timing of the second DCI is a predetermined time before the start timing of the other UL channel, the control unit multiplexes the second UL channel onto the other UL channel, as described in any of Notes 1 to 3.

[0283] (Note) The following inventions are added with respect to one embodiment of the present disclosure (second embodiment): [Note 1] A terminal having: a transmitting unit that transmits a first UL channel that notifies a second uplink (UL) channel for transmitting a beam report (UEIBR) initiated by the terminal; and a control unit that controls UL transmission according to a specific rule when the second UL channel and a measurement reference signal (SRS) overlap in the time domain. [Note 2] The terminal according to Note 1, wherein the second UL channel is a dynamic grant physical uplink shared channel (DG PUSCH) or a set grant PUSCH (CG PUSCH). [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit applies different transmission controls to the second UL channel and the SRS depending on the type of SRS. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit controls either the second UL channel or the SRS to drop and transmit either the other.

[0284] (Note) The following inventions are added with respect to one embodiment (third / fourth embodiment) of the present disclosure: [Note 1] A terminal having: a transmitting unit that transmits a first UL channel that notifies a second uplink (UL) channel for transmitting a beam report (UEIBR) initiated by the terminal; and a control unit that controls UL transmission according to a specific rule when the first UL channel and the second UL channel overlap in the time domain. [Note 2] The terminal according to Note 1, wherein the first UL channel is a physical uplink control channel (PUCCH) containing a scheduling request or a specific type of UCI for the UEIBR, and the second UL channel is a dynamic grant physical uplink sharing channel (DG PUSCH) or a setting grant PUSCH (CG PUSCH). [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit does not expect to set different modes of the UEIBR simultaneously. [Note 4] When an overlap of the second UL channel occurs between different modes of the UEIBR, the control unit controls the UL transmission according to the priority of each mode, as described in any of Notes 1 to 3.

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

[0286] Figure 3 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0287] Furthermore, the wireless communication system 1 may 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)), and the like.

[0288] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the 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.

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

[0290] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0291] 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 by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0292] 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 (CC) and Dual Connectivity (DC).

[0293] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

[0294] Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

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

[0296] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0297] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0298] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0299] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0300] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0302] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0303] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0305] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0306] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0307] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

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

[0309] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0310] 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, the DL-RS may include 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.

[0311] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0312] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0313] (Base Station) Figure 4 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0314] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0315] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0317] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0318] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0319] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0320] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0321] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0322] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0323] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0324] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

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

[0326] The transmitting / receiving unit 120 (receiving 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 (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0327] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

[0328] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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.

[0329] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0330] 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 physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0331] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0332] The transmitting / receiving unit 120 may receive a first UL channel that notifies a second uplink (UL) channel for transmitting beam reports (UEIBR) initiated by a terminal. The control unit 110 may control the reception of UL transmissions sent from the terminal according to specific rules if the second UL channel and other UL channels overlap in the time domain.

[0333] The control unit 110 may control the reception of UL transmissions transmitted from the terminal according to specific rules when the second UL channel and the measurement reference signal (SRS) overlap in the time domain.

[0334] The control unit 110 may control the reception of UL transmissions sent from the terminal according to specific rules when the first UL channel and the second UL channel overlap in the time domain.

[0335] (User Terminal) Figure 5 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0336] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0337] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0339] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0340] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0341] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0342] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0343] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0344] The transmitting / receiving 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 and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0345] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0346] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0347] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

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

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

[0350] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also 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.

[0351] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0352] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0353] The control unit 210 may perform at least a part of the processing of the control unit as described above.

[0354] The transmitting / receiving unit 220 may perform at least a part of the processing of the transmitting / receiving unit as described above.

[0355] The number of bits in the first UL channel may be determined based on the priority of the triggered event.

[0356] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0357] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0359] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0360] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

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

[0362] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0363] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.

[0364] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0365] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

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

[0367] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0368] 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 different buses may be configured for each device.

[0369] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0370] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0371] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0372] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0373] Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0374] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

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

[0376] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0377] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0378] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0379] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0380] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0381] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0382] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0383] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0384] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0385] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0386] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0387] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0388] A BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within a single carrier for a UE.

[0389] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0390] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

[0392] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0394] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0395] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0396] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0397] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0398] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0399] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0400] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0401] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0402] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0403] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0404] 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,” and “receiving entity” may be used interchangeably.

[0405] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0406] The above group may include, for example, at least one of the following: 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, or a panel group.

[0407] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0408] Furthermore, in this disclosure, 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 interpreted interchangeably.

[0409] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0410] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably.

[0411] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0412] In this disclosure, terms such as “Base Station (BS),” “wireless 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,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0413] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services 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 ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0414] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

[0415] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0416] A mobile station may also be called 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 appropriate term.

[0417] 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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0418] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0419] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.

[0420] Figure 7 shows an example of a vehicle according to one 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, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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.

[0421] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 the user.

[0422] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0423] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0424] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0425] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0426] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0427] 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0428] 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 external devices. For example, it can send and receive various types of information to and from external devices 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. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0430] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0431] 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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0432] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0433] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0434] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0435] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0436] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0437] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0438] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0439] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0440] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0441] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0442] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0443] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased 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).

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

[0445] As used in the present disclosure, the terms "connected" and "coupled", or any variations thereof, mean 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 "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 "accessed".

[0446] In the present disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, as some non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the radio frequency region, microwave region, optical (both visible and invisible) region, etc.

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

[0448] In the present disclosure, when the terms "include", "including" and their variations are used, these terms are intended to be inclusive, similar to the term "comprising". Furthermore, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0449] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0450] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0451] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0452] In the present disclosure, expressions 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", "B until A", etc. may be read interchangeably with each other. Here, A, B, etc. may be appropriately replaced with suitable expressions such as nouns, gerunds, ordinary sentences, etc. according to the context. The time difference between A and B may be approximately 0 (immediately before or after). Also, a time offset may be applied to the time when A occurs. For example, "A" may be read interchangeably with "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predefined or may be specified by the UE based on the notified information.

[0453] In the present disclosure, timing, time, hour, time instance, any time unit (e.g., slot, sub - slot, symbol, sub - frame), period, occasion, resource, etc. may be read interchangeably with each other.

[0454] As described above, the invention according to the present disclosure has been described in detail. However, 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 the purpose of illustrative explanation and does not impose any restrictive meaning on the invention according to the present disclosure.

Claims

1. A terminal having a transmitting unit that transmits a first UL channel that notifies a second uplink (UL) channel for transmitting beam reports (UEIBR) initiated by the terminal, and a control unit that controls UL transmission according to specific rules when the second UL channel and other UL channels overlap in the time domain.

2. The terminal according to claim 1, wherein the second UL channel is a dynamic grant physical uplink shared channel (DG PUSCH) or a configured grant PUSCH (CG PUSCH), and the other UL channel is a DG PUSCH, a CG PUSCH, or a PUSCH with semi-persistent CSI.

3. The terminal according to claim 1, wherein the control unit controls the transmission to prioritize either the second UL channel or the other UL channel when a specific time condition is met.

4. When the other UL channel scheduled by the first downlink control information (DCI) and the second UL channel scheduled by the second DCI overlap, if the end timing of the second DCI is a predetermined time before the start timing of the other UL channel, the control unit multiplexes the second UL channel onto the other UL channel, as described in claim 1.

5. A wireless communication method for a terminal, comprising the steps of: transmitting a first UL channel that notifies a second uplink (UL) channel for transmitting a beam report (UEIBR) initiated by the terminal; and controlling UL transmission according to a specific rule when the second UL channel and other UL channels overlap in the time domain.

6. A base station having a receiving unit that receives a first UL channel that notifies a second uplink (UL) channel for transmitting beam reports (UEIBR) initiated by a terminal, and a control unit that controls the reception of UL transmissions transmitted from a terminal according to specific rules when the second UL channel and other UL channels overlap in the time domain.

Images