Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that, when at least one of a first case in which a terminal-initiated beam report is configured for a plurality of component carriers and a second case in which a plurality of events are configured for one component carrier or one report configuration is satisfied, determines the component carriers on which a first uplink (UL) channel related to the beam report, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal are respectively transmitted, and determines information included in the first UL channel, information included in the DL signal, and information included in the second UL channel; and a transmission / reception unit that performs transmission of the first UL channel and the second UL channel, and reception of the DL signal. The one aspect of the present disclosure can improve communication quality / throughput.

Description

Terminal, Wireless Communication Method, and Base Station

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

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of achieving further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further increasing 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 future wireless communication systems (for example, NR, Rel. 19 and later), it is being considered to support beam reporting (or, may also be called event-triggered beam reporting / UE-initiated Beam Report (UEIBR)) initiated by a terminal (user terminal, User Equipment (UE)).

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

[0007] However, there are cases where such beam reporting is not 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, when at least one of a first case in which beam reporting initiated by the terminal is set up for a plurality of component carriers, and a second case in which a plurality of events are set up for a single component carrier or a single reporting setting, a component carrier on which a first uplink (UL) channel relating to the beam reporting, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal are transmitted, a control unit that determines information contained in the first UL channel, information contained in the DL signal, and information contained in the second UL channel, and a transmitting / receiving unit that transmits the first UL channel and the second UL channel and receives the DL signal.

[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 transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 3 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 4 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 5 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 6 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 7 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 8 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 9 shows another example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. Figure 10 shows an example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. Figure 11 shows another example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. Figure 12 shows another example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. Figure 13 shows another example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. Figure 14 shows another example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. Figure 15 shows another example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. Figure 16 shows another example of first UL channel / second UL channel transmission according to Embodiment 3-2. Figure 17 shows another example of first UL channel / second UL channel transmission according to Embodiment 3-2. Figure 18 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 19 shows an example of a base station configuration according to one embodiment. Figure 20 shows an example of a user terminal configuration according to one embodiment.Figure 21 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 22 shows an example of a vehicle according to one embodiment.

[0012] (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.

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

[0014] (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.

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

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

[0017] 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).

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

[0019] (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.

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

[0021] 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).

[0022] (Event-Triggered Beam Reporting / 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).

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

[0024] <Applicable Cases> UEIBR may be applied, for example, in at least one of the following Case 1 or Case 2: • Case 1: L1-RSRP / SINR beam reporting including serving cell PCI / additional PCI (e.g., L1 / L2 inter-cell mobility / inter-cell multi-TRP (M-TRP inter-cell) / L1-RSRP / SINR beam reporting including serving cell / additional PCI cell for Rel. 18 L1 / L2 mobility with cell switching). • Case 2: L1-RSRP / SINR beam reporting including serving cell PCI only.

[0025] The UE may report the measurement results (e.g., at least L1-RSRP / L1-SINR and the corresponding resource indicator / RS index) to the NW when a specific event occurs (which may be interpreted in this disclosure as a specific condition being met / not met, a specific event being matched, etc.).

[0026] The specific event may be, for example, at least one of an event relating to a serving cell and an additional cell, and at least one of an event relating to a beam report including at least one of the PCI of the serving cell and the PCI of the additional cell.

[0027] <UEIBR Trigger Conditions / Events for Rel. 19> The UEIBR may be triggered when certain conditions (events) are met. For example, the UE may apply different / same conditions / events to the triggers of the following beam reports.

[0028] UE Feature #1: UEIBR for MIMO in Rel. 19. UE Feature #2: UEIBR for mobility in Rel. 19.

[0029] Different UE capabilities may be introduced / defined between UE features #1 and #2. Furthermore, different higher-layer parameters may be set to enable each UE feature. UE features and UE capabilities may be interchangeable.

[0030] UE does not expect UE features #1 and #2 to be set simultaneously in a given BWP / CC / band / frequency range / frequency (or for each UE).

[0031] A UE may have UE features #1 and #2 set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE). For example, a UE may have predefined which events (which UE features) to prioritize, if set, and this may be set / instructed by upper-layer signaling / physical-layer signaling.

[0032] This disclosure may be applied within the Unified TCI Framework.

[0033] This disclosure may apply only if the corresponding UE capability is reported, or if the corresponding higher-layer parameter (e.g., RRC) is notified / reported.

[0034] <UEIBR for MIMO> The following may apply to the UEIBR for MIMO in Rel. 19.

[0035] - MAC CE in PUCCH. - UCI in periodic / semi-persistent PUCCH, UCI in dynamic grant (DG) / configured grant (CG) PUCCH. - The relationship between the MAC CE-based method and the UCI-based method described above. For example, two independent methods may be configurable. Alternatively, a UCI-based method may be applied in addition to a MAC CE-based method (a combination of the two methods (2-step method) may be applied).

[0036] The report content may be essentially the same as existing L1 beam measurement reports, and may include at least one of the following, for example: • SSBRI / CRI. • Number of beams to be reported (X). • Method for selecting X beams. • L1-RSRP / SINR (absolute value / difference value) for each SSBRI / CRI. If MAC CE is used, • Indicator indicating whether the following octets are included. If MAC CE / UCI is used, • Serving cell ID, BWP ID (if the report requires activation of the TCI state or beam switching).

[0037] Events related to the UEIBR for MIMO 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) improves by a threshold beyond the RS derived from the Q-th (Q may be M; Q or M is 1 or greater; Q or M may be set in the RRC (based on UE capability reporting)) quality good activated (active) TCI state. - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) improves by a threshold beyond the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the set reference RS (which may be SSB / CSI-RS).

[0038] It should be noted that the events exemplified in this way do not exclude other events.

[0039] Priorities may be assigned to events 1 through 9. For example, one of events 1 through 9 (e.g., event 2) may have the highest priority (e.g., event 2 may be given priority in the decision-making process).

[0040] For example, in event 2, the current beam may be determined / derived based on the QCL RS of the indicated TCI state (e.g., QCL source RS).

[0041] For example, for the current beam in Event 2, at least one of the following beam options 2a to 2c may be supported: - Beam option 2a: The RS corresponding to the current beam is [implicitly] derived / determined based on the QCL RS of the indicated TCI state. - Beam option 2b: The RS corresponding to the current beam becomes the QCL RS of the indicated TCI state and the QCLed SSB. - Beam option 2c: The RS corresponding to the current beam is [explicitly] set / indicated using RRC signaling / MAC CE.

[0042] For example, for the new beam in Event 2, at least one of the following beam options 3a to 3c may be supported: - Beam option 3a: The RS corresponding to the new beam is [explicitly] set using RRC signaling (e.g., resetting of existing RS measurements, or setting parameters of the TCI state (e.g., TCI-State)) / MAC CE. - Beam option 3b: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of the activated TCI state (active TCI state). - Beam option 3c: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of one or more TCI states in a set subset of the list of TCI states set by RRC (set TCI state).

[0043] For example, for the reference signal measurement (RS measurement) of the current beam for Event 2 (and beam option 2a), multiple schemes may be supported: - Scheme 1: The RS of the current beam is the QCL RS in the indicated TCI state. - Scheme 2: The RS of the current beam is the QCL RS in the indicated TCI state and the QCLed SSB.

[0044] If there are two QCL RSs in the indicated TCI state, the QCL RS may be of QCL type D.

[0045] As the QCL RS set / applied to the indication TCI state, at least one of CSI-RS and SSB may be supported. When CSI-RS is set / applied as the QCL RS, at least one of the CSI-RS for tracking (TRS) and the CSI-RS for measurement may be supported. The CSI-RS for measurement may be the CSI-RS used for L1-RSRP / L1-SINR, or may be the CSI-RS used for beam management (BM).

[0046] In Scheme 1, only the TRS (for example, one CSI-RS for tracking) may be set as the QCL-RS (for example, type A / D) indicating the TCI state.

[0047] When only the TRS is set as the QCL-RS indicating the TCI state, a reference signal different from the TRS (for example, the RS corresponding to the TRS) may be selected as the measurement / reporting of the RS of the current beam.

[0048] For the RS measurement of the current beam in Event 2 / Option 2a, [in addition to Schemes 1 and 2,] at least one of the following processing options 1 to 4 may be applied as the processing when only one TRS is set in the indication TCI state:

[0049] - Processing Option 1: An additional scheme is introduced. The RS for the current beam can be the CSI-RS for beam management derived from the QCL RS in the indication TCI state. - Processing Option 2: The TRS is further supported as the measurement RS of the current beam for determining L1-RSRP. - Processing Option 3: An additional scheme is introduced. The RS for the current beam is explicitly set / indicated by RRC or MAC CE. - Processing Option 4: No further extension is made.

[0050] The explicit RS setting for the measurement of the new beam in Event 2 may be set in one RS resource set associated with the CSI report setting.

[0051] In this case, if existing UE capabilities cannot be reused, a UE capability indicating the maximum number of RSs to be set within the RS resource set may be defined / introduced.

[0052] The RS within that single RS resource set may be updated by MAC CE.

[0053] UEIBR for MIMO may be transmitted using UCI.

[0054] In a UCI-based UEIBR procedure using UCI, the following modes may be supported:

[0055] <<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).

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

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

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

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

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

[0061] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit instruction (for setting the one-bit instruction) may be defined. The RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0062] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeA-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

[0063] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).

[0064] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

[0065] The DCI format in step 2 may be, for example, UL Grant DCI (e.g., DCI format 0_1 / 0_2 / 0_3), and the second UL channel in step 3 may utilize at least PUSCH.

[0066] Furthermore, the DCI format in step 2 may be, for example, DL Grant DCI (e.g., DCI format 1_1 / 1_2), and the second UL channel in step 3 may utilize PUCCH.

[0067] A new 1-bit field in the DL grant DCI may be defined to instruct the transmission of the UEIBR.

[0068] PUCCH resources intended for HARQ-ACK transmission may be (re)used to transmit both HARQ-ACK and UEIBR.

[0069] <<Mode B>> Mode B relates to the UCI in the pre-configured resources for the second UL channel.

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

[0071] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (UCI) within the channel).

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

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

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

[0075] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.

[0076] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit instruction (for setting the one-bit instruction) may be defined. The RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0077] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeB-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

[0078] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).

[0079] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

[0080] The second UL channel in step 2 may be, for example, a type 1 configured grant (CG) PUSCH or PUCCH.

[0081] <UEIBR for Mobility> With respect to the UEIBR for mobility (e.g., LTM) in Rel. 19, the following may apply:

[0082] - MAC CE in semi-persistent / aperiodic PUCCH. - UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUCCH.

[0083] The report may include, for example, at least one of the following: If the measurement report is used for cell switching reporting, in addition to MIMO-related information: an indicator showing whether or not a cell switch has occurred, or TA-related information. Otherwise (if the measurement report is not used for cell switching reporting): the same information as MIMO-related information (the only difference being whether it is within a cell or between cells).

[0084] The supported events may be the same as those for a Conditional Hand-Over (CHO).

[0085] For example, since candidate cells are set based on the L3 measurement report, L1-RSRP / SINR may be used as the threshold.

[0086] If the report is used for cell switching commands, specific domain filters (e.g., time / frequency / space) may be considered / applied to prevent frequent switching.

[0087] It may also be specified whether flexibility in the trigger time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds) is required.

[0088] In the case of L1 measurements using UEIBR, at least the results of beam-level measurements may be used for event evaluation.

[0089] Events related to UEIBR for mobility may be broadly categorized into the following event types: • Event LTM2: The serving cell's beam quality falls below an (absolute) threshold. • Event LTM3: The candidate cell's beam quality improves beyond a certain offset amount compared to the serving cell's beam quality. • Event LTM4: The candidate cell's beam quality falls below an (absolute) threshold. • Event LTM5: The serving cell's beam quality falls below a first (absolute) threshold, AND the candidate cell's beam quality improves above a second (absolute) threshold.

[0090] It should be noted that the events exemplified in this way do not exclude other events. Furthermore, the MIMO-oriented events described above may be reused as appropriate (in this case, "current beam" may be replaced with "serving cell beam," and "new beam" with "candidate cell beam"). These reused / re-interpreted events may be called mobility / LTM-oriented events corresponding to MIMO-oriented events.

[0091] In the LTM configuration, the L1 measurement resource setting may support both SSB and CSI-RS beam settings.

[0092] In events LTM3 and LTM5, the same type of RS (e.g., CSI-RS / SSB) may be used for both the serving cell and the candidate cell (adjacent cell).

[0093] In mobility event evaluation, at least one of the following may be applied: TimeToTrigger (TTT), hysteresis for entering / leaving, and beam-specific / cell-specific offsets.

[0094] UEIBR for mobility may be transmitted using MAC CE.

[0095] <Definition of wording for specific events> In the existing events described above, the definitions of Serving [cell] and Neighbor [cell] may be reinterpreted / updated as follows in the UEIBR for Rel. 19.

[0096] For example, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL]TCI state) in event-triggered beam reports for MIMO in Rel. 19.

[0097] Furthermore, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL] TCI state) or the serving cell's beam (e.g., the RS ID associated with the serving cell's PCI TCI state) in the event-triggered beam reports for mobility in Rel. 19.

[0098] In existing L3 events, adjacent [cells] may be interpreted interchangeably with other beams (e.g., RS IDs that are not associated with the indicated [joint / DL]TCI state but are associated with the RS ID for the L1 beam measurement) in event-triggered beam reports for MIMO (which may be mobility) in Rel. 19.

[0099] Furthermore, adjacent [cells] in existing L3 events may be interpreted as corresponding to beams of non-serving cells / target cells / candidate cells (e.g., RS IDs associated with the TCI status of the PCI of target cells / candidate cells) in event-triggered beam reports for mobility in Rel. 19.

[0100] The measured values ​​of each reference signal (RS) may be RSRP / SINR, L3-RSRP / SINR, L1-RSRP / SINR, or the average of multiple L1-RSRP / SINR values.

[0101] For example, L1-RSRP / SINR can change dynamically. Therefore, by averaging multiple (X) L1-RSRP / SINR values ​​(e.g., X=5), control hunting (frequent switching of trigger states) in beam reporting triggers can be avoided.

[0102] <Event Instance Counters / Timers> In UEIBR / Event Triggered Beam Reporting, the use of counters / timers (or possibly time windows) is being considered to determine / judge the triggering / occurrence of events.

[0103] The counter / timer may be used in MIMO / mobility use cases. For example, in the case of an event-triggered beam for mobility (LTM), the timer may be TTT (Time to Trigger).

[0104] The UE may count the number of event instances (for example, measurements that satisfy the event's entering condition) and determine that the event has occurred / been triggered / been satisfied when that number reaches a certain number.

[0105] The number of event instances may, for example, represent a count for event triggers. The counting of event instances may be performed within a timer / time window.

[0106] The counter / timer may be specified in advance, set / instructed using RRC signaling / MAC CE / DCI, or determined based on UE capability information reports.

[0107] Of the events mentioned above, in Event 2, it is being considered that the event instance count will be performed for each new beam.

[0108] Furthermore, the evaluation cycle for the event instance of event 2 mentioned above is being considered.

[0109] For example, the period of the current beam's RS may be the same as the period of the new beam's RS.

[0110] In this case, the evaluation period of the event instance may be the same as the period of the RS of the current beam and the RS of the new beam.

[0111] Furthermore, for example, the RS period of the current beam and the RS period of the new beam may be different (and may be supported).

[0112] In this case, the evaluation period of the event instance may be at least one of the following periods 1 to 5: • The evaluation period of the event instance is the same as the period of the current beam's RS. • The evaluation period of the event instance is the same as the period of the new beam's RS. • The evaluation period of the event instance is the same as the shortest period among the periods of the current beam's RS and the new beam's RS. • The evaluation period of the event instance is the larger of the shortest period among the periods of the current beam's RS and the new beam's RS, and Xms (the maximum value). • The evaluation period of the event instance is the same as the longest period among the periods of the current beam's RS and the new beam's RS.

[0113] (Analysis) In some cases, the events in the event-triggered beam reports / UEIBR described above have not been adequately examined.

[0114] More specifically, the operation / provisions related to at least one of the following—UEIBRs (multi-CC cases / cross-CC cases) using multiple CCs, and UEIBRs (multi-event cases) related to multiple events—have not been sufficiently considered.

[0115] For example, in a Mode A UEIBR transmission procedure, it is being considered that a specific (existing) field (e.g., a CSI request field) within a specific DCI format (e.g., DCI format 0_1 / 0_2 / 0_3) may be (re)used for the first DL signal that triggers the transmission of the UEIBR (second UL channel).

[0116] In this case, the CSI trigger state associated with the UEIBR settings (e.g., reporting settings) may be indicated using the specific field in the specific DCI format, and the second UL channel may be transmitted in the resource scheduled by that DCI format.

[0117] However, there has been insufficient consideration of how to utilize these specific fields in multi-CC cases, cross-CC cases, and multi-event cases.

[0118] Furthermore, for example, in the UEIBR transmission procedure for Mode B, it is being considered to establish a one-to-one correspondence between a (periodic) UL resource for the first UL channel (e.g., a PUCCH resource) and a pre-configured UL resource for the second UL channel.

[0119] However, the handling of this UL resource in multi-CC cases, cross-CC cases, and multi-event cases has not been sufficiently considered.

[0120] The following sections will analyze the issues in more detail.

[0121] <Issue 1> In multi-event cases (single CC cases), the operation / regulations regarding transmission on the second UL channel have not been adequately considered. More specifically, when multiple events are set [simultaneously] for a single CC, it has not been adequately considered whether a single second UL channel contains only one report corresponding to one event, or whether it can contain multiple reports corresponding to multiple events. Furthermore, the operation / regulations when multiple reports are included for the second UL channel have not been adequately considered.

[0122] For example, if multiple reports cannot be included in a single second UL channel, there is a concern that greater delays may occur, potentially negating the expected delay reduction effect of UEIBR.

[0123] Furthermore, regarding the second UL channel, the use of PUSCH (Dynamic Grant (DG) PUSCH) and Configured Grant (CG) PUSCH based on DCI's dynamic instructions is being considered. However, the methods for securing the payload differ for each channel, and these methods need to be thoroughly examined.

[0124] <Issue 2> In multi-CC cases / cross-CC cases (single event cases), the operation / regulations regarding transmission on the second UL channel have not been sufficiently considered. More specifically, when multi-CC cases / cross-CC cases are supported, it has not been sufficiently considered whether a single second UL channel may contain only one report corresponding to one CC, or multiple reports corresponding to multiple CCs. Furthermore, the operation / regulations when multiple reports are included in the second UL channel have not been sufficiently considered.

[0125] For example, if multiple reports cannot be included in a single second UL channel, there is a concern that greater delays may occur, potentially negating the expected delay reduction effect of UEIBR.

[0126] Furthermore, regarding the second UL channel, the use of PUSCH (Dynamic Grant (DG) PUSCH) and Configured Grant (CG) PUSCH based on DCI's dynamic instructions is being considered. However, the methods for securing the payload differ for each channel, and these methods need to be thoroughly examined.

[0127] <Issue 3> In multi-CC cases / cross-CC cases / multi-event cases, the operation / regulations regarding transmission on the second UL channel have not been sufficiently considered. More specifically, when multi-CC cases / cross-CC cases / multi-event cases are supported, there has not been sufficient consideration of whether a single second UL channel contains only one report corresponding to one event / CC, or whether it can contain multiple reports corresponding to multiple events / CCs. Furthermore, the operation / regulations when multiple reports are included in the second UL channel have not been sufficiently considered.

[0128] Furthermore, if reports related to multiple CCs / events are triggered at the same (or within a certain period) evaluation timing, and the constraints / regulations regarding the operation from the first UL channel transmission to the second UL channel transmission are not properly determined, there is a risk that the UEIBR operation may not be able to be performed properly.

[0129] Furthermore, if, for example, multiple reports cannot be included in a single second UL channel, there is a concern that greater delays may occur, potentially negating the expected delay reduction effect of UEIBR. On the other hand, if multiple reports can be included in a single second UL channel, a reduction in latency and signaling overhead can be expected, leading to an improvement in overall system throughput.

[0130] Furthermore, regarding the second UL channel, the use of PUSCH (Dynamic Grant (DG) PUSCH) and Configured Grant (CG) PUSCH based on DCI's dynamic instructions is being considered. However, the methods for securing the payload differ for each channel, and these methods need to be thoroughly examined.

[0131] If these issues are not adequately considered, it may not be possible to properly implement UEIBR, and low-latency communication that takes advantage of the beam reporting benefits may not be achieved, potentially hindering improvements in communication quality and throughput.

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

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

[0134] (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.

[0135] 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".

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

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

[0138] 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).

[0139] 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).

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

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

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

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

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

[0145] 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 a PDSCH. A candidate cell may mean a cell that is a candidate to become a serving cell through L1 / L2 inter-cell mobility. L1 / L2-triggered mobility (or Lower layer triggered mobility, LTM) and L1 / L2 inter-cell mobility may be interpreted interchangeably.

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

[0147] In this disclosure, "transmission" and "reception" may be interpreted interchangeably.

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

[0149] In this disclosure, 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.

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

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

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

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

[0154] In this disclosure, the beam, RS, RS index (CRI / SSBRI), and [L1 / L3] measurement results may be interpreted interchangeably.

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

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

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

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

[0159] In this disclosure, rules, cases, factors, conditions, thresholds, etc., may be interpreted as interchangeable.

[0160] In this disclosure, the CSI / UCI relating to the UEIBR may be referred to as the UEIBR-CSI / UCI. In this disclosure, "other" UCI (or simply "UCI") may mean a UCI separate from the CSI / UCI relating to the UEIBR.

[0161] In this disclosure, beam report, CSI report, UEIBR, CSI relating to UEIBR, UEIBR-CSI, UEIBR-UCI, report, etc. may be interpreted interchangeably.

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

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

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

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

[0166] In this disclosure, terms such as switch, switching, activate, deactivate, instruct, change, update, etc., relating to the TCI state may be interpreted interchangeably.

[0167] In this disclosure, beam indicator (DCI / MAC CE), TCI status indicator (DCI / MAC CE), TCI status switching command (DCI / MAC CE), cell switch command (DCI / MAC CE), DCI, MAC CE, etc., may be interpreted interchangeably.

[0168] In this disclosure, the terms "report content," "field," "ID," "measurement result," and "reported quantity" may be interpreted interchangeably.

[0169] In this disclosure, beam report, report, MAC CE, beam report MAC CE, UCI, and PUSCH may be interpreted as interchangeable.

[0170] In this disclosure, beam, beam ID, beam identifier, RS index, SSBRI, and CRI may be interpreted as interchangeable.

[0171] In this disclosure, the current beam, the beam / RS corresponding to the current active TCI state, the beam / RS corresponding to the active TCI state, the beam / RS derived from the [current] active TCI state, etc., may be interpreted interchangeably.

[0172] In this disclosure, beam and beam ID, RS and RS ID, TCI state and TCI state ID may be interpreted as mutually interchangeable.

[0173] In this disclosure, the first DL signal may simply be referred to as the DL signal / DCI, etc.

[0174] In this disclosure, beam reporting (which may also be simply called reporting) may be included in the second UL channel. One reporting may correspond to one event / reporting setting.

[0175] In this disclosure, reporting settings, CSI reporting settings, UEIBR-specific CSI reporting settings, reporting settings for UEIBR, etc., may be interpreted interchangeably.

[0176] (Wireless communication method) The UE may apply each embodiment of the disclosure in conjunction with the performance of beam measurement / reporting (e.g., UEIBR). The NW / BS / gNB may provide / transmit to the UE settings / instructions etc. for the UE to perform the operations / controls described in each embodiment of the disclosure. Furthermore, the NW / BS / gNB may perform various operations / controls necessary to receive event-triggered beam reports / UEIBR from the UE.

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

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

[0179] In this disclosure, each operation / option may be applied in at least one of Case 1 and Case 2 described above.

[0180] In this disclosure, each operation / option may be applied in at least one of Mode A and Mode B as described above.

[0181] In this disclosure, the number of RS / beam reports [included in the beam report] may include the number of sets of RS indices (e.g., CRI / SSBRI) and corresponding measurement results (e.g., L1-RSRP) included in the beam report, or it may include the number of either the RS indices or the corresponding measurement results.

[0182] Each embodiment of the present disclosure described below is applicable to any event relating to the UEIBR (e.g., events 1 / 2 / 7).

[0183] The beam reports transmitted by the UE may be UCI-based or MAC CE-based. Accordingly, the operations / restrictions in each embodiment of this disclosure may apply to beam reports using UCI or to beam reports using MAC CE. For example, beam reports may be transmitted in UCI / MAC CE for UL cell switch commands.

[0184] In this case, in step 2 of mode A, the UE may receive a DCI that triggers / schedules a UL channel / resource related to the UCI of the UL cell switch command.

[0185] In this case, the UE may also receive a conditional LTM setting as a reporting setting for the UEIBR. The UE may control the UEIBR operation based on the conditional LTM setting.

[0186] UE / NW may switch the application of different event types (e.g., Event 2 and 7 / 1) using (or at the higher layer) higher-layer signaling, or under specific conditions.

[0187] The bit size of the UCI transmitted using the second UL channel may be standardized to a larger UCI size for different event types (e.g., events 2 and 7). In this case, zero-padding may be applied to the UCI of events with smaller reporting content to make it the same size as the larger UCI.

[0188] A UE may have a UEIBR set for / with multiple CCs. A UEIBR using multiple CCs may be set for a UE. Cases in which such a UEIBR is set may be called multi-CC cases. Cases that do not fall under multi-CC cases may be called single-CC cases.

[0189] At least two of the CCs (Communication Centers) on which the reporting settings for the UEIBR are configured, the CC to which the RS (Radio Speed) set as the measurement target in those reporting settings belongs, and the CC on which the first / second UL channels are transmitted may be different. Such a case may be called a cross-CC case.

[0190] Multiple events may be configured for a single CC / reporting setting. Alternatively, one (or more) events may be configured for each of multiple CC / reporting settings. At least one of these cases may be called a multi-event case. Cases that do not fall under the category of multi-event cases may be called single-event cases.

[0191] In this disclosure, the specified number may be one or more.

[0192] The operation / restrictions relating to each option described in each embodiment of this disclosure may be specified in the specification, set / instructed by RRC signaling / MAC CE / DCI, determined based on UE capability information reporting, or determined / selected based on at least a combination of these.

[0193] The operations / provisions relating to each option described in each embodiment of this disclosure may be applied simultaneously in appropriate combinations.

[0194] The operations, specifications, and drawings described below in each embodiment of this disclosure are merely examples and are not limited to those disclosed.

[0195] <First Embodiment> The first embodiment relates to operation handling in a multi-event case.

[0196] Multiple events may be set for a single CC simultaneously.

[0197] Multiple events may be triggered at the same or overlapping evaluation timing.

[0198] The timing of the reports corresponding to each of the multiple events may coincide with or overlap with the transmission opportunities on the same second UL channel.

[0199] <<Embodiment 1-1>> Embodiment 1-1 may be applied to Mode A.

[0200] For example, UE may transmit DG PUSCH as the second UL channel.

[0201] <<<Option 1-1-1>>> A single second UL channel transmitted in a single CC may contain reports on different types of events.

[0202] Multiple reports (e.g., all) triggered simultaneously (or within a certain period) in that CC may be included in a single second UL channel (Option 1-1-1-1).

[0203] A certain number of reports triggered simultaneously (or within a certain period) in that CC may be included in a single second UL channel (Option 1-1-1-2).

[0204] The specified number may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0205] The reporting of such specific numbers may be selected / determined using specific methods.

[0206] The specific method may be, for example, at least one of the following: • The priority of each event is specified / set / instructed, and a certain number of reports are selected / determined in order of the highest priority event. • A code point in a specific field (e.g., a CSI request field) within the first DL signal (DCI) is associated with an event (or combination thereof), and a certain number of reports are selected / determined based on the first DL signal for scheduling the second UL channel. • A certain number of reports are selected / determined in ascending / descending order by event ID.

[0207] The maximum number of reports that can be included in a single second UL channel may be predetermined by specification, set / instructed using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0208] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0209] <<<Option 1-1-2>>> A single second UL channel transmitted in a single CC may contain [only] reports concerning a specific type of event.

[0210] In that CC, certain reports that are triggered simultaneously (or within a certain period) may be included in one second UL channel.

[0211] The specific report in question may be selected / determined using a specific method.

[0212] The specific method may be, for example, at least one of the following: • The priority of each event is specified / set / instructed, and the reporting of the event with the highest priority is selected / determined. • A code point in a specific field (e.g., a CSI request field) within the first DL signal (DCI) is associated with an event, and a specific report is selected / determined based on the first DL signal for scheduling on the second UL channel. • The report corresponding to the smallest (or largest) event ID is selected / determined as the specific report.

[0213] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0214] If it is possible to identify multiple types of events that are triggered (simultaneously) based on the information contained in the first UL channel, then at least one of the above options may be applied.

[0215] If the number of events that are triggered (simultaneously) can be identified based on the information contained in the first UL channel, and the payload / size of the reports (content) corresponding to each event is equal, then at least one of the above options may be applied.

[0216] If the number of events that are triggered (simultaneously) can be identified based on the information contained in the first UL channel, and the payload / size of the report (content) corresponding to each event is different, then at least one of the above options may be applied.

[0217] According to Embodiment 1-1, operation in mode A can be guaranteed.

[0218] <<Embodiment 1-2>> Embodiment 1-2 may also be applied to Mode B.

[0219] For example, UE may transmit CG PUSCH as the second UL channel.

[0220] <<<Option 1-2-1>>> Reports on different types of events may be included within a single second UL channel transmitted in a single CC.

[0221] Multiple reports (e.g., all) triggered simultaneously (or within a certain period) in that CC may be included in a single second UL channel (Option 1-2-1-1).

[0222] Up to a certain number (maximum number) of reports triggered simultaneously (or within a certain period) in that CC may be included in a single second UL channel (Option 1-2-1-2).

[0223] The specified number / maximum number may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0224] The reporting of the specified number / maximum number may be selected / determined using a specific method.

[0225] The specific method may be, for example, at least one of the following: • A priority is specified / set / instructed for each event, and a specific number of reports are selected / determined in order of the highest priority event. • A specific number of reports are selected / determined in ascending / descending order by event ID.

[0226] The maximum number of reports that can be included in a single second UL channel may be predetermined by specification, set / instructed using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0227] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0228] Multiple reports triggered simultaneously (or within a certain period) in that CC may be included in a single second UL channel, such that the total payload / size is less than or equal to the payload available within the second UL channel (Option 1-2-1-3).

[0229] In this case, multiple reports may be selected / determined using a specific method.

[0230] The specific method may be, for example, at least one of the following: • A priority is specified / set / instructed for each event, and a certain number of reports are selected / determined in order of the highest priority event. • A certain number of reports are selected / determined in ascending / descending order by event ID. • Among multiple reports, reports may be selected / determined in ascending / descending order by the payload used in the report.

[0231] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0232] <<<Option 1-2-2>>> A single second UL channel transmitted in a single CC may contain [only] reports concerning a specific type of event.

[0233] In that CC, certain reports that are triggered simultaneously (or within a certain period) may be included in one second UL channel.

[0234] The specific report in question may be selected / determined using a specific method.

[0235] The specific method may be, for example, at least one of the following: • The priority of each event is specified / set / instructed, and the report of the event with the highest priority is selected / determined. • The report corresponding to the smallest (or largest) event ID is selected / determined as the specific report.

[0236] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0237] According to Embodiment 1-2, operation in mode B can be guaranteed.

[0238] According to the first embodiment described above, even in the case of multiple event cases, it is possible to realize UEIBR operation that appropriately utilizes the second UL channel, and this can contribute to resolving issue 1.

[0239] <Second Embodiment> The second embodiment relates to operation handling in a multi-CC case / cross-CC case.

[0240] Multi-CC cases / cross-CC cases may be supported.

[0241] Multiple reports related to the [CSI] reporting settings configured for multiple CCs may be triggered at the same / overlapping evaluation timing.

[0242] The timing of these multiple reports may coincide with or overlap with transmission opportunities on the same second UL channel.

[0243] <<Embodiment 2-1>> Embodiment 2-1 may be applied to Mode A.

[0244] For example, UE may transmit DG PUSCH as the second UL channel.

[0245] <<<Option 2-1-1>>> In a CC where the triggered reporting setting is configured, the second UL channel may be scheduled / transmitted using the first DL signal (DCI).

[0246] The first DL signal and the second UL channel may be associated with each other (for example, they may have a one-to-one correspondence). The first DL signal and the second UL channel may each be transmitted in the CC where the triggered reporting setting is configured (option 2-1-1-1).

[0247] A second UL channel may be scheduled [simultaneously] in multiple CCs where multiple triggered reporting settings are configured using a specific DCI format (for example, a DCI format for scheduling to multiple cells / CCs (DCI format 0_3)) (Option 2-1-1-2).

[0248] <<<Option 2-1-2>>> A second UL channel transmitted in one CC may include a report triggered in another CC.

[0249] If at least one report occurs / is triggered simultaneously (or within a certain period) within multiple configured CCs / cell groups / PUCCH groups, multiple reports relating to multiple CCs may be transmitted on a single second UL channel (Option 2-1-2-1).

[0250] The second UL channel may be scheduled, for example, for a specific cell (e.g., a special cell (SpCell, e.g., PCell / PSCell) / PUCCH SCell) using the first DL signal (DCI).

[0251] The second UL channel may, for example, include multiple reports (e.g., all of them) from multiple CCs occurring simultaneously (or within a certain period of time) (Option 2-1-2-1-1).

[0252] The second UL channel may, for example, include a specific number / part of reports (e.g., all) from multiple CCs that occur simultaneously (or within a certain period) (Option 2-1-2-1-2).

[0253] The specified number / part may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0254] Furthermore, if multiple reports are generated / triggered simultaneously (or within a certain period) within multiple configured CCs / cell groups / PUCCH groups, multiple reports relating to multiple CCs may be transmitted on a single second UL channel (Option 2-1-2-2).

[0255] The second UL channel may be scheduled, for example, for a specific CC using the first DL signal (DCI).

[0256] The specific CC in question may be, for example, a CC that has a specific CC ID (e.g., the smallest (or largest) CC ID) among the CCs from which the report is generated / triggered.

[0257] The second UL channel may, for example, include multiple reports (e.g., all of them) from multiple CCs occurring simultaneously (or within a certain period of time) (Option 2-1-2-2-1).

[0258] The second UL channel may, for example, include a specific number / part of reports (e.g., all) from multiple CCs that occur simultaneously (or within a certain period) (Option 2-1-2-2-2).

[0259] The specified number / part may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0260] In the above options 2-1-2-1-2 / 2-1-2-2-2, a specific number of reports may be selected / determined using a specific method.

[0261] The specific method may be, for example, at least one of the following: • The priority of each CC is specified / set / instructed, and a certain number of reports are selected / determined in order from the reports of the CC with the highest priority. • A code point in a specific field (e.g., the CSI request field) in the first DL signal (DCI) is associated with a CC ID, and a certain number of reports are selected / determined based on the first DL signal for scheduling the second UL channel. • A certain number of reports are selected / determined in order from the reports corresponding to the smallest (or largest) CC ID.

[0262] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0263] If, based on the information contained in the first UL channel, it is possible to identify multiple CC IDs that are triggered (simultaneously), then at least one of the above options may be applied.

[0264] If the number of CCs to be triggered (simultaneously) can be identified based on the information contained in the first UL channel, and the payload / size of the reports (content) corresponding to each CC is equal, then at least one of the above options may be applied.

[0265] If the number of CCs to be triggered (simultaneously) can be identified based on the information contained in the first UL channel, and the payload / size of the report (content) corresponding to each CC is different, then at least one of the above options may be applied.

[0266] According to Embodiment 2-1, operation in mode A can be guaranteed.

[0267] <<Embodiment 2-2>> Embodiment 2-2 may also be applied to Mode B.

[0268] For example, UE may transmit CG PUSCH as the second UL channel.

[0269] The second UL channel may be transmitted in the CC where the triggered [CSI] reporting setting is configured.

[0270] For example, if a second UL channel is transmitted in the CC of a serving cell where CSI reporting settings are configured, the reports included in the second UL channel may be only the triggered reports (Option 2-2-1).

[0271] In addition, under Option 2-2-1, if only one event / report setting is configured for one CC, there will be no cases where multiple reports are duplicated / mapped on the second UL channel.

[0272] Furthermore, for example, a second UL channel may be transmitted in the CC (the CC where the measured RS is set / transmitted) that is the target of the RS measurement, as set within the CSI reporting settings (Option 2-2-2).

[0273] In this case, the reports included in the second UL channel may be at least one of the following options 2-2-2-1 to 2-2-2-4: Option 2-2-2-1: A second UL channel contains multiple (e.g., all) triggered reports that share the same CC from which the second UL channel is transmitted. Option 2-2-2-2: A second UL channel contains one of multiple triggered reports that share the same CC from which the second UL channel is transmitted. Option 2-2-2-3: A second UL channel contains up to a specific number (maximum number) of triggered reports that share the same CC from which the second UL channel is transmitted. Option 2-2-2-4: A second UL channel contains multiple triggered reports that share the same CC from which the second UL channel is transmitted, such that the total payload / size is less than or equal to the payload available within the second UL channel.

[0274] The specified number / maximum number may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0275] The report selected / determined in at least one of the above options 2-2-2-1 to 2-2-2-4 may be selected / determined using a specific method.

[0276] The specific method may be, for example, at least one of the following: - The priority of each CC is specified / set / instructed, and reports are selected / determined in order from the CC with the highest priority among the CCs for which the reporting settings of the triggered report are set. - For the CCs for which the reporting settings of the triggered report are set, reports are selected / determined in ascending / descending order by CC ID.

[0277] Reports that are not selected or decided may be sent during subsequent opportunities to transmit on the 2nd UL channel, or they may be dropped.

[0278] According to Embodiment 2-2, operation in mode B can be guaranteed.

[0279] According to the second embodiment described above, even in multi-CC cases / cross-CC cases, it is possible to realize UEIBR operation that appropriately utilizes the second UL channel, thereby contributing to the resolution of issue 2.

[0280] <Third Embodiment> The third embodiment relates to operation handling in multi-CC cases / cross-CC cases and multi-event cases.

[0281] Multi-CC cases / cross-CC cases and multi-event cases may be supported [simultaneously].

[0282] <<Embodiment 3-1>> Embodiment 3-1 may be applied to Mode A.

[0283] For example, UE may transmit DG PUSCH as the second UL channel.

[0284] The UE may use the first UL channel to transmit information about the triggered report.

[0285] The information may include, for example, at least one of the following: • Option 3-1-1-1: The CC ID in which the triggered reporting settings are configured. • Option 3-1-1-2: The CC ID in which the triggered reporting settings are configured, and the event IDs / reporting setting IDs that are triggered in each CC (for example, information indicating that events 1 and 2 are triggered in CC#0, events 2 and 7 are triggered in CC#1, and event 1 is triggered in CC#1, etc.). • Option 3-1-1-3: The CC ID in which the triggered reporting settings are configured, and information on the number of events (IDs) / reporting setting (IDs) that are triggered in each CC (for example, information indicating that two events are triggered in CC#0, two events are triggered in CC#1, and one event is triggered in CC#1, etc.). Option 3-1-1-4: The CC ID in which the triggered reporting settings are configured, and the event IDs / reporting setting IDs that are triggered in multiple CCs (e.g., all of [configured]) (e.g., information indicating that events 1, 2, and 7 are triggered). Option 3-1-1-5: The CC ID in which the triggered reporting settings are configured, and information on the number of events (IDs) / reporting settings (IDs) that are triggered in multiple CCs (e.g., all of [configured]) (e.g., information indicating that five reporting settings are triggered). Option 3-1-1-6: Information on the number of events (IDs) / reporting settings (IDs) that are triggered in multiple CCs (e.g., all of [configured]) (e.g., information indicating that five reporting settings are triggered). Option 3-1-1-7: Does not include either the CC ID in which the triggered reporting settings are configured, or the event IDs / reporting setting IDs (including the number of IDs).

[0286] The UE may schedule the second UL channel using a first DL signal (DCI) (based on the first UL channel).

[0287] The scheduling method for the second UL channel may be, for example, at least one of the following: • Option 3-1-2-1: A single second UL channel is scheduled by a single DCI (e.g., DCI format 0_1 / 0-2). • Option 3-1-2-2: Multiple second UL channels are scheduled by a single DCI (e.g., DCI format 0_3).

[0288] Furthermore, a single scheduled 2nd UL channel may contain only one report related to one CC, or it may contain multiple reports related to multiple CCs.

[0289] The UE may use a specific field (e.g., the CSI request field) included in the first DL signal (DCI) to determine which reports / report candidates to include in the second UL channel. Such report candidates may mean the candidates for the reports actually transmitted.

[0290] The method of determination may be, for example, at least one of the following: Option 3-1-3-1: The code point / bitmap of a specific field is associated with the event ID / report setting ID of the report to be included in the second UL channel (for example, if the code point is 000000, it is event 1; if it is 000001, it is event 2; if it is 000010, it is event 7; if it is 000011, it is events 1 and 2; if it is 000100, it is events 2 and 7, ..., etc.). Option 3-1-3-2: The code point / bitmap of a specific field is associated with the number of reports to be included in the second UL channel (for example, if the code point is 000000, it is one report; if it is 000001, it is two reports; if it is 000010, it is three reports, ..., etc.). Option 3-1-3-3: The code point / bitmap of a specific field is associated with a combination of CC IDs to be included in the second UL channel for which reporting settings are configured for the triggered report (for example, CC#0 for 000000, CC#1 for 000001, CC#2 for 000010, etc.). Option 3-1-3-4: The code point / bitmap of a specific field is associated with the number of CC IDs to be included in the second UL channel for which reporting settings are configured for the triggered report (for example, one CC for 000000, two CCs for 000001, three CCs for 000010, etc.). Option 3-1-3-5: The code point / bitmap of a specific field is associated with a combination of CC ID and event ID / report setting ID for the report included in the second UL channel (for example, if the code point is 000000, it is CC#0 and event 1; if it is 000001, it is CC#0 and event 2; if it is 000010, it is CC#0 and event 7; if it is 000011, it is CC#0 and events 1 and 2; if it is 000100, it is CC#0 and events 2 and 7; if it is 000101, it is CC#1 and event 1, ..., etc.).Option 3-1-3-6: In UEIBR, associations are not made between certain fields and information (e.g., CC ID / Event ID / Reporting Settings ID (including numerical information)).

[0291] The event ID / reporting setting ID associated with a code point may be a single event ID / reporting setting ID, a combination of multiple event IDs / reporting setting IDs, or both.

[0292] The CC ID associated with a code point may be a single CC ID, a combination of multiple CC IDs, or both.

[0293] The combination of CC ID and Event ID / Reporting Setting ID associated with the code point may be arbitrary.

[0294] In this disclosure, certain fields included in the first DL signal (DCI) may include other fields in addition to the CSI request field. This allows the UE to include reporting information to be transmitted on the second UL channel using information bits exceeding the number of bits in the CSI request field (e.g., 6 bits).

[0295] The information contained in the first DL signal (DCI) (e.g., a specific field) does not have to determine / confirm the report / report content contained in the second UL channel (i.e., the specific field may determine only the report candidates).

[0296] In this case, the reports / reporting content included in the second UL channel may be determined / confirmed using a specific method.

[0297] For example, the number of reports / reported content included in the second UL channel may be determined using at least one of the following methods: • Option 3-1-4-1: Multiple (e.g., all) of the report candidates are included in the second UL channel. • Option 3-1-4-2: A specific number / maximum number of report candidates are included in the second UL channel. • Option 3-1-4-3: A specific number of report candidates are included in the second UL channel. • Option 3-1-4-4: One of the report candidates is included in the second UL channel.

[0298] The specific number / maximum number related to option 3-1-4-2 may be specified in advance in the specifications, set / instructed using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0299] The specific number relating to option 3-1-4-3 may be predetermined in the specifications, set / instructed using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, determined (implicitly) based on information contained in the first UL channel, or determined based on a combination of at least two of these.

[0300] For example, with respect to the specific number related to option 3-1-4-3, if reporting is triggered in one CC, the specific number may be 1, and if reporting is triggered in three CCs, the specific number may be 3. In other words, the specific number may be determined based on the number of CCs that trigger reporting, or it may be the same as the number of CCs that trigger reporting.

[0301] Furthermore, for example, with respect to the specific number related to option 3-1-4-3, if reporting is triggered for one type of event in multiple CCs (e.g., all [configured]), the specific number may be 1, and if reporting is triggered for three types of events in multiple CCs (e.g., all [configured] CCs), the specific number may be 3. In other words, the specific number may be determined based on the number of event types triggered in multiple CCs (e.g., all [configured]), or it may be the same as the number of event types.

[0302] Furthermore, for example, the reports / reporting content included in the second UL channel may be determined using at least one of the following methods:

[0303] Option 3-1-5-1: The priority of each event is specified / set / instructed, and the report candidates are sorted by at least one of the following: ascending / descending order of priority, ascending / descending order of CC ID, and ascending / descending order of report setting ID, and the reports to be included in the second UL channel are determined. Option 3-1-5-2: The report candidates are sorted by at least one of the following: ascending / descending order of CC ID, ascending / descending order of event ID, and ascending / descending order of report setting ID, and the reports to be included in the second UL channel are determined.

[0304] The sorting order by priority, CC ID, reporting setting ID, and event ID may be arbitrary.

[0305] The combinations of each of the above options will be described in detail using the following diagrams. In the following diagrams, the first UL channel, the first DL signal, and the second UL channel will be referred to as the first UL, the first DL, and the second UL, respectively.

[0306] Furthermore, the time domain arrangement of the first UL channel, the first DL signal, and the second UL channel described in this disclosure is merely an example and does not mean that each channel is arranged at the same or different times for each CC.

[0307] Figures 2-9 show an example of transmission / reception of the first UL channel / first DL signal / second UL channel according to Embodiment 3-1. In the example shown in Figures 2 to 9, a UEIBR utilizing multiple CCs (CC#0 to #2) is set for the UE, and reporting settings corresponding to events 1, 2, and 7 are set for each CC.

[0308] In the examples shown in Figures 2 to 9, reports related to multiple events / reporting settings are triggered simultaneously (or within a certain period). In the examples shown in Figures 2 to 8, reports related to events 1 and 7 (each with their corresponding reporting settings) in CC#0, reports related to event 1 (each with its corresponding reporting setting) in CC#1, and reports related to events 1, 2, and 7 (each with their corresponding reporting settings) in CC#2 are triggered simultaneously (or within a certain period). In the example shown in Figure 9, reports related to event 1 and event 7 (each with its corresponding reporting settings) are triggered simultaneously (or within a certain period) in each of CC#0 to CC#2.

[0309] In Figures 2-9, CC#0 may also be SpCell / PUCCH SCell.

[0310] Figure 2 corresponds to the cases of options 3-1-1-2, 3-1-2-1, and 3-1-3-1 described above. In the example shown in Figure 2, it is shown that the first UL channel triggers events 1 and 7 in CC#0, event #1 in CC#1, and events 1, 2, and 7 in CC#2.

[0311] Furthermore, in the example shown in Figure 2, a first DL signal transmitted at each CC schedules a single second UL channel at each CC. The second UL channel transmitted at each CC contains a report relating to an event triggered at that CC. In the example shown in Figure 2, the report in each second UL channel may or may not include the event ID corresponding to the report. If the report in the second UL channel does not include the event ID, the network may derive which event the report corresponds to.

[0312] Figure 3 corresponds to the cases of options 3-1-1-3, 3-1-2-1, and 3-1-3-2 described above. In the example shown in Figure 3, the first UL channel triggers two events in CC#0, one event in CC#1, and three events in CC#2.

[0313] Furthermore, in the example shown in Figure 3, a first DL signal transmitted at each CC schedules a single second UL channel at each CC. The second UL channel transmitted at each CC contains reports related to events triggered at that CC.

[0314] In the example shown in Figure 3, the report in each second UL channel may include the event ID corresponding to the report.

[0315] Figure 4 corresponds to the cases of options 3-1-1-1, 3-1-2-1, 3-1-3-6, 3-1-4-4, and 3-1-5-1. The example shown in Figure 4 demonstrates that the first UL channel triggers events / reports in CC#0, CC#1, and CC#2.

[0316] Furthermore, in the example shown in Figure 4, a first DL signal transmitted at each CC schedules a single second UL channel at each CC. No association is made between specific fields included in the first DL signal and the CC ID / event ID. The UE sorts the report candidates at each CC in a specific way and transmits one report on the second UL channel at each CC.

[0317] In the example shown in Figure 4, the report in each second UL channel may include the event ID corresponding to the report.

[0318] Figure 5 corresponds to the cases of options 3-1-1-2, 3-1-2-1, and 3-1-3-5 described above. In the example shown in Figure 5, it is shown that the first UL channel triggers events 1 and 7 in CC#0, event #1 in CC#1, and events 1, 2, and 7 in CC#2.

[0319] In the example shown in Figure 5, a single first DL signal transmitted in CC#0 schedules a single second UL channel in CC#0. This first DL signal instructs CC#0 to report event 1, CC#1 to report event 1, and CC# to report events 1 and 2. This single second UL channel contains reports related to events triggered in CC#0 through #2.

[0320] In the example shown in Figure 5, the report in the second UL channel may include the CC ID / event ID corresponding to the report. However, it may not include the CC ID / event ID. If the report in the second UL channel does not include the CC ID / event ID, the network may derive which CC / event the report corresponds to.

[0321] Figure 6 corresponds to the cases of options 3-1-1-2, 3-1-2-1, 3-1-3-2, and 3-1-5-1. In the example shown in Figure 6, it is shown that the first UL channel triggers events 1 and 7 in CC#0, event #1 in CC#1, and events 1, 2, and 7 in CC#2.

[0322] In the example shown in Figure 6, a single first DL signal transmitted in CC#0 schedules a single second UL channel in CC#0. This first DL signal instructs that three reports be included in the second UL channel. This single second UL channel contains reports related to the events triggered in CC#0 through CC#2, specifically event 1 in CC#0, event 1 in CC#1, and event 1 in CC#2.

[0323] In the example shown in Figure 6, the report in the second UL channel may or may not include the CC ID / event ID corresponding to the report. If the report in the second UL channel does not include the CC ID / event ID, the network may derive which CC / event the report corresponds to.

[0324] Figure 7 corresponds to the cases of options 3-1-1-1, 3-1-2-1, 3-1-3-6, 3-1-4-3, and 3-1-5-1. The example shown in Figure 7 demonstrates that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0325] Furthermore, in the example shown in Figure 7, a single first DL signal transmitted in CC#0 schedules a single second UL channel in CC#0. No association is made with the CC ID / event ID for specific fields included in the first DL signal. In this case, the UE determines that the first UL channel indicates that events are triggered in three CCs, and therefore decides to include the three reports in the second UL channel. The second UL channel contains reports related to event 1 in CC#0, event 1 in CC#1, and event 1 in CC#2, respectively, from the events triggered in CC#0 to #2.

[0326] In the example shown in Figure 7, the report in the second UL channel may include the CC ID / event ID corresponding to the report.

[0327] Figure 8 corresponds to the cases of options 3-1-1-6, 3-1-2-1, 3-1-3-2, and 3-1-5-1 described above. In the example shown in Figure 8, it is shown that the first UL channel triggers six events / reports.

[0328] In the example shown in Figure 8, a single first DL signal transmitted in CC#0 schedules a single second UL channel in CC#0. Three reports are instructed to be included in the second UL channel for specific fields contained in the first DL signal. The second UL channel contains reports related to events triggered in CC#0 through #2, specifically event 1 in CC#0, event 1 in CC#1, and event 1 in CC#2.

[0329] In the example shown in Figure 8, the report in the second UL channel may include the CC ID / event ID corresponding to the report.

[0330] Figure 9 corresponds to the cases of options 3-1-1-2, 3-1-2-2, and 3-1-3-1 described above. In the example shown in Figure 9, it is shown that events 1 and 7 are triggered in each CC by the first UL channel.

[0331] Furthermore, in the example shown in Figure 9, a single first DL signal transmitted in CC#0 schedules the second UL channels in each of CC#0 through CC#2. This first DL signal instructs each second UL channel to include reports relating to events 1 and 7. Each second UL channel contains reports relating to events 1 and 7 in each CC.

[0332] In this disclosure, if a corresponding event / report setting instructed to be included in a second UL channel using a specific DCI format (e.g., DCI format 0_3) is not actually triggered in the CC, the UE may apply zero-padding to the bits of the report relating to that event / report setting that is not included in the second UL channel. This behavior is applicable to any embodiment / option (combination) of this disclosure.

[0333] In the example shown in Figure 9, the report in each second UL channel may or may not include the event ID corresponding to the report. If the report in the second UL channel does not include the event ID, the network may derive which event the report corresponds to.

[0334] The examples shown in Figures 2 through 9 are merely illustrative, and the above options can be combined in any way you like.

[0335] According to Embodiment 3-1, operation in mode A can be guaranteed.

[0336] <<Embodiment 3-2>> Embodiment 3-2 may be applied to Mode B.

[0337] For example, UE may transmit CG PUSCH as the second UL channel.

[0338] The UE may use the first UL channel to transmit information about the triggered report.

[0339] The information may include, for example, at least one of the following: • Option 3-2-1-1: The CC ID in which the triggered reporting settings are configured. • Option 3-2-1-2: The CC ID in which the triggered reporting settings are configured, and the event IDs / reporting setting IDs that are triggered in each CC (for example, information indicating that events 1 and 2 are triggered in CC#0, events 2 and 7 are triggered in CC#1, and event 1 is triggered in CC#1, etc.). • Option 3-2-1-3: The CC ID in which the triggered reporting settings are configured, and information on the number of events (IDs) / reporting setting (IDs) that are triggered in each CC (for example, information indicating that two events are triggered in CC#0, two events are triggered in CC#1, and one event is triggered in CC#1, etc.). Option 3-2-1-4: The CC ID in which the triggered reporting settings are configured, and the event IDs / reporting setting IDs that are triggered in multiple CCs (e.g., all of [configured]) (e.g., information indicating that events 1, 2, and 7 are triggered). Option 3-2-1-5: The CC ID in which the triggered reporting settings are configured, and information on the number of events (IDs) / reporting settings (IDs) that are triggered in multiple CCs (e.g., all of [configured]) (e.g., information indicating that five reporting settings are triggered). Option 3-2-1-6: Information on the number of events (IDs) / reporting settings (IDs) that are triggered in multiple CCs (e.g., all of [configured]) (e.g., information indicating that five reporting settings are triggered). Option 3-2-1-7: Does not include either the CC ID in which the triggered reporting settings are configured, or the event IDs / reporting setting IDs (including the number of IDs).

[0340] UE may determine the number of reports to include in the second UL channel using a specific method.

[0341] The specific method may be, for example, at least one of the following: • Option 3-2-2-1: Multiple (e.g., all) of the reporting candidates are included in the second UL channel. • Option 3-2-2-2: A specific number / maximum number of reporting candidates are included in the second UL channel. • Option 3-2-2-3: Multiple reporting candidates are included in the second UL channel such that their total payload / size is less than or equal to the payload / size available within the second UL channel. • Option 3-2-2-4: One of the reporting candidates is included in the second UL channel.

[0342] The specified number / maximum number may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, determined based on UE capability information reports, or determined based on a combination of at least two of these.

[0343] In at least one of the above options 3-2-2-1 to 3-2-2-4, the reports selected / determined from the report candidates may be selected / determined by at least one of the following methods: Option 3-2-3-1: The priority of each event is specified / set / instructed, and the report candidates are sorted in ascending / descending order of the priority, ascending / descending order of the CC ID, and ascending / descending order of the report setting ID to determine the reports to be included in the second UL channel. Option 3-2-3-2: The report candidates are sorted in ascending / descending order of the CC ID, ascending / descending order of the event ID, and ascending / descending order of the report setting ID to determine the reports to be included in the second UL channel.

[0344] The sorting order by priority, CC ID, reporting setting ID, and event ID may be arbitrary.

[0345] The following diagrams will detail the combinations of each of the above options.

[0346] Figures 10-17 show an example of transmission of the first UL channel / second UL channel according to Embodiment 3-2. In the example shown in Figures 10 to 17, a UEIBR using multiple CCs (CC#0 to #2) is set for the UE, and reporting settings corresponding to events 1, 2, and 7 are set in each CC.

[0347] In the examples shown in Figures 10 to 17, reports related to multiple events / reporting settings are triggered simultaneously (or within a certain period). In the examples shown in Figures 10 to 17, reports related to events 1 and 7 (each with their corresponding reporting settings) in CC#0, reports related to event 1 (each with its corresponding reporting setting) in CC#1, and reports related to events 1, 2, and 7 (each with their corresponding reporting settings) in CC#2 are triggered simultaneously (or within a certain period).

[0348] In Figures 10-17, CC#0 may also be SpCell / PUCCH SCell.

[0349] Figures 10, 12, 14, and 16 show cases where a second UL channel is transmitted in the CC of a serving cell configured within the reporting settings.

[0350] Figures 11, 13, 15, and 17 show cases where a second UL channel is transmitted in a CC that is the target of RS measurement set in the reporting settings. In the examples shown in Figures 11, 13, 15, and 17, RS measurement in CC#1 is set in the reporting settings for event 1 of CC#0, RS measurement in CC#2 is set in the reporting settings for event 7 of CC#0, RS measurement in CC#0 is set in the reporting settings for event 1 of CC#1, RS measurement in CC#2 is set in the reporting settings for event 1 of CC#2, RS measurement in CC#2 is set in the reporting settings for event 2 of CC#2, and RS measurement in CC#1 is set in the reporting settings for event 7 of CC#2.

[0351] Figure 10 corresponds to the cases of options 3-2-1-1, 3-2-2-1, and 3-2-3-1 described above.

[0352] In the example shown in Figure 10, it is shown that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0353] Furthermore, in the example shown in Figure 10, the second UL channel transmitted by each CC includes reports related to events triggered in each CC.

[0354] In the example shown in Figure 10, the report in each second UL channel may or may not include the event ID corresponding to the report. If the report in the second UL channel does not include the event ID, the network may derive which event the report corresponds to.

[0355] Figure 11 corresponds to the cases of options 3-2-1-1, 3-2-2-1, and 3-2-3-1 described above.

[0356] In the example shown in Figure 11, it is shown that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0357] In the example shown in Figure 11, the second UL channel in CC#0 includes the report related to event 1 in CC#1, the second UL channel in CC#1 includes the report related to event 1 in CC#0 and the report related to event 7 in CC#2, and the second UL channel in CC#2 includes the report related to event 7 in CC#0, the report related to event 1 in CC#2, and the report related to event 2 in CC#2.

[0358] In the example shown in Figure 11, the report in each second UL channel may or may not include the CC ID / event ID corresponding to the report. If the report in the second UL channel does not include the CC ID / event ID, the network may derive which CC / event the report corresponds to.

[0359] Figure 12 corresponds to the cases of options 3-2-1-1, 3-2-2-2, and 3-2-3-1 described above.

[0360] The example shown in Figure 12 demonstrates that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0361] Furthermore, in the example shown in Figure 12, the second UL channel transmitted by each CC contains a specified number / maximum number (in this example, the specified number / maximum number may be 2) of reports related to events triggered in each CC. In the example shown in Figure 12, the second UL channel in CC#0 contains reports related to events 1 and 7 of CC#0, the second UL channel in CC#1 contains a report related to event 1 of CC#1, and the second UL channel in CC#2 contains reports related to events 1 and 2 of CC#2.

[0362] In the example shown in Figure 12, the report in each second UL channel may or may not include the event ID corresponding to the report. If the report in the second UL channel does not include the event ID, the network may derive which event the report corresponds to.

[0363] Figure 13 corresponds to the cases of options 3-2-1-1, 3-2-2-2, and 3-2-3-1 described above.

[0364] The example shown in Figure 13 demonstrates that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0365] Furthermore, in the example shown in Figure 13, the second UL channel transmitted in each CC contains a specified number / maximum number (in this example, the specified number / maximum number may be 2) of reports related to events triggered in each CC. In the example shown in Figure 13, the second UL channel in CC#0 contains the report related to event 1 in CC#1, the second UL channel in CC#1 contains the report related to event 1 in CC#0 and the report related to event 7 in CC#2, and the second UL channel in CC#2 contains the report related to event 7 in CC#0 and the report related to event 1 in CC#2.

[0366] In the example shown in Figure 13, the report in each second UL channel may or may not include the CC ID / event ID corresponding to the report. If the report in the second UL channel does not include the CC ID / event ID, the network may derive which CC / event the report corresponds to.

[0367] Figure 14 corresponds to the cases of options 3-2-1-1, 3-2-2-3, and 3-2-3-1 described above.

[0368] The example shown in Figure 14 demonstrates that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0369] Furthermore, in the example shown in Figure 14, the second UL channel transmitted in each CC contains a number of reports related to events triggered in each CC that do not exceed the payload / size of each second UL channel. In the example shown in Figure 14, the second UL channel in CC#0 contains reports related to events 1 and 7 of CC#0, the second UL channel in CC#1 contains a report related to event 1 of CC#1, and the second UL channel in CC#2 contains a report related to event 1 of CC#2.

[0370] In the example shown in Figure 14, the report in each second UL channel may or may not include the event ID corresponding to the report. If the report in the second UL channel does not include the event ID, the network may derive which event the report corresponds to.

[0371] Figure 15 corresponds to the cases of options 3-2-1-1, 3-2-2-3, and 3-2-3-1 described above.

[0372] In the example shown in Figure 15, it is shown that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0373] Furthermore, in the example shown in Figure 15, the second UL channel transmitted in each CC contains a number of reports related to events triggered in each CC that do not exceed the payload / size of each second UL channel. In the example shown in Figure 15, the second UL channel in CC#0 contains the report related to event 1 in CC#1, the second UL channel in CC#1 contains the report related to event 1 in CC#0 and the report related to event 7 in CC#2, and the second UL channel in CC#2 contains the report related to event 7 in CC#0.

[0374] In the example shown in Figure 15, the report in each second UL channel may or may not include the CC ID / event ID corresponding to the report. If the report in the second UL channel does not include the CC ID / event ID, the network may derive which CC / event the report corresponds to.

[0375] Figure 16 corresponds to the cases of options 3-2-1-1, 3-2-2-4, and 3-2-3-1 described above.

[0376] In the example shown in Figure 16, it is shown that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0377] Furthermore, in the example shown in Figure 16, the second UL channel transmitted in each CC contains one report from among the reports related to events triggered in each CC. In the example shown in Figure 16, the second UL channel in CC#0 contains the report related to event 1 of CC#0, the second UL channel in CC#1 contains the report related to event 1 of CC#1, and the second UL channel in CC#2 contains the report related to event 1 of CC#2.

[0378] In the example shown in Figure 16, the report in each second UL channel may or may not include the event ID corresponding to the report. If the report in the second UL channel does not include the event ID, the network may derive which event the report corresponds to.

[0379] Figure 17 corresponds to the cases of options 3-2-1-1, 3-2-2-4, and 3-2-3-1 described above.

[0380] The example shown in Figure 17 demonstrates that the first UL channel triggers events in CC#0, CC#1, and CC#2.

[0381] Furthermore, in the example shown in Figure 17, the second UL channel transmitted in each CC contains one report from among the reports related to events triggered in each CC. In the example shown in Figure 17, the second UL channel in CC#0 contains the report related to event 1 in CC#1, the second UL channel in CC#1 contains the report related to event 1 in CC#0, and the second UL channel in CC#2 contains the report related to event 1 in CC#2.

[0382] In the example shown in Figure 17, the report in each second UL channel may or may not include the CC ID / event ID corresponding to the report. If the report in the second UL channel does not include the CC ID / event ID, the network may derive which CC / event the report corresponds to.

[0383] The examples shown in Figures 10 to 17 are merely illustrative, and the above options can be combined in any way you like.

[0384] According to Embodiment 3-2, operation in mode B can be guaranteed.

[0385] According to the third embodiment described above, even in multi-CC cases, cross-CC cases, and multi-event cases, it is possible to realize UEIBR operation that appropriately utilizes the second UL channel, thereby contributing to the resolution of issue 3.

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

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

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

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

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

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

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

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

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

[0395] 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 event-triggered beam reporting / UEIBR; • Supporting MIMO / mobility from Rel. 19 onwards; • Supporting UEIBR using MAC CE / UCI; • Supporting event combinations (e.g., events 1 / 2 / 7); • Total number of beams reported; • Number of beams that satisfy the conditions; • Supporting multi-CC / cross-CC cases; • Supporting multi-event cases; • Supporting the transmission of a first UL channel / first DL signal / second UL channel in different CC / cell groups / PUCCH groups.

[0396] 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).

[0397] 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)).

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

[0399] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1-1] A terminal having, when at least one of the following is satisfied: a first case in which beam reporting initiated by the terminal is set up for a plurality of component carriers, and a second case in which a plurality of events are set up for a single component carrier or a single reporting setting, a component carrier on which a first uplink (UL) channel relating to the beam reporting, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal are each transmitted, a control unit that determines information to be included in the first UL channel, information to be included in the DL signal, and information to be included in the second UL channel, and a transmitting / receiving unit that transmits the first UL channel and the second UL channel and receives the DL signal. [Note 1-2] The terminal according to Note 1-1, wherein the control unit controls the second UL channel on a single component carrier to include beam reporting corresponding to one or more events when the second case is satisfied. [Appendix 1-3] The terminal according to Appendix 1-1 or Appendix 1-2, wherein the transmitting / receiving unit transmits the second UL channel using either the component carrier on which the triggered reporting setting is configured, or a component carrier other than the component carrier on which the triggered reporting setting is configured, from among the plurality of component carriers, when the first case is satisfied. [Appendix 1-4] The terminal according to any one of Appendix 1-1 to Appendix 1-3, wherein the control unit controls the second UL channel to include at least one of the identifier of the component carrier to which the beam report included in the second UL channel corresponds and the identifier of the event, when both the first case and the second case are satisfied.[Note 2-1] A terminal having, when at least one of the following is satisfied: a first case in which beam reporting initiated by the terminal is set up for multiple component carriers, and a second case in which multiple events are set up for one component carrier or one reporting setting, a component carrier on which a first uplink (UL) channel relating to the beam reporting and a second UL channel based on the first UL channel are transmitted, a control unit that determines information contained in the first UL channel and information contained in the second UL channel, and a transmitting unit that transmits the first UL channel and the second UL channel. [Note 2-2] The terminal according to Note 2-1, wherein the control unit controls the second UL channel on one component carrier to include beam reporting corresponding to one or more events when the second case is satisfied. [Appendix 2-3] The terminal according to Appendix 2-1 or Appendix 2-2, wherein the transmitting unit transmits the second UL channel using either the component carrier on which the triggered reporting setting is configured, or the component carrier corresponding to the measurement of the reference signal configured in the triggered reporting setting, from among the plurality of component carriers. [Appendix 2-4] The terminal according to any one of Appendix 2-1 to Appendix 2-3, wherein the control unit controls the second UL channel to include at least one of the identifier of the component carrier to which the beam report included in the second UL channel corresponds and the identifier of the event, when both the first case and the second case are met.

[0400] (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.

[0401] Figure 18 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).

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

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

[0404] 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))).

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

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

[0407] 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).

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

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

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

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

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

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

[0414] 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).

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

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

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

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

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

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

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

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

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

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

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

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

[0427] 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).

[0428] (Base Station) Figure 19 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0447] When at least one of the following cases is satisfied: a first case where beam reporting started by a terminal is set for a plurality of component carriers, and a second case where a plurality of events are set for one component carrier or one reporting setting, the control unit 110 may determine a first uplink (UL) channel related to the beam reporting, a downlink (DL) signal based on the first UL channel, and a component carrier for transmitting each of the second UL channels scheduled by the DL signal, and information included in the first UL channel, information included in the DL signal, and information included in the second UL channel. The transceiver unit 120 may transmit the first UL channel and the second UL channel and receive the DL signal (First / Second / Third Embodiments).

[0448] When at least one of the following cases is satisfied: a first case where beam reporting started by a terminal is set for a plurality of component carriers, and a second case where a plurality of events are set for one component carrier or one reporting setting, the control unit 110 may determine a component carrier for transmitting each of the first uplink (UL) channel related to the beam reporting and the second UL channel based on the first UL channel, and information included in the first UL channel and information included in the second UL channel. The transceiver unit 120 may receive the first UL channel and the second UL channel (First / Second / Third Embodiments).

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

[0450] In this example, mainly the functional blocks of the characteristic portions in the present embodiment are shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

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

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

[0453] The transmission / reception 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 transmission / reception unit 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common understanding in the technical field related to the present disclosure.

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

[0455] The transmission / reception antenna 230 can be composed of an antenna described based on the common understanding in the technical field related to the present disclosure, such as an array antenna.

[0456] The transmission / reception unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0457] The transmission / reception unit 220 may form at least one of a transmission beam and a reception beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

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

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

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

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

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

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

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

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

[0467] The control unit 210 may determine, when at least one of the following is satisfied: a first case in which beam reporting initiated by a terminal is set for multiple component carriers, and a second case in which multiple events are set for one component carrier or one reporting setting, the component carriers to which a first uplink (UL) channel relating to the beam reporting is transmitted, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal, as well as the information contained in the first UL channel, the information contained in the DL signal, and the information contained in the second UL channel. The transmitting / receiving unit 220 may transmit the first UL channel and the second UL channel and receive the DL signal (first / second / third embodiments).

[0468] The control unit 210 may, when the second case is met, control the second UL channel in one component carrier to include beam reports corresponding to one or more events (first embodiment).

[0469] If the first case is met, the transmitting / receiving unit 220 may transmit the second UL channel using either the component carrier on which the triggered reporting setting is configured, or a component carrier other than the component carrier on which the triggered reporting setting is configured (second embodiment).

[0470] The control unit 210 may control the second UL channel to include at least one of the component carrier identifier and the event identifier corresponding to the beam report contained in the second UL channel if both the first and second cases are satisfied (third embodiment).

[0471] The control unit 210 may determine the component carriers to which the first uplink (UL) channel and the second UL channel based on the first UL channel are transmitted, the information contained in the first UL channel, and the information contained in the second UL channel, if at least one of the following is satisfied: a first case in which beam reporting initiated by a terminal is set for multiple component carriers, and a second case in which multiple events are set for one component carrier or one reporting setting. The transmitting / receiving unit 220 may transmit the first UL channel and the second UL channel (first / second / third embodiments).

[0472] The control unit 210 may, when the second case is met, control the second UL channel in one component carrier to include beam reports corresponding to one or more events (first embodiment).

[0473] If the first case is met, the transmitting / receiving unit 220 may transmit the second UL channel using either the component carrier on which the triggered reporting setting is set, or the component carrier corresponding to the measurement of the reference signal set in the triggered reporting setting, from among the plurality of component carriers (second embodiment).

[0474] The control unit 210 may control the second UL channel to include at least one of the component carrier identifier and the event identifier corresponding to the beam report contained in the second UL channel if both the first and second cases are satisfied (third embodiment).

[0475] (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.

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

[0477] 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 21 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.

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

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

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

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

[0482] Further, the processor 1001 reads a program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and other functional blocks may be realized similarly.

[0483] The memory 1002 is a computer-readable recording medium, and may be constituted by, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other appropriate storage media. The memory 1002 may be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store a program (program code), software module, etc. executable for implementing the wireless communication method according to an embodiment of the present disclosure.

[0484] The storage 1003 is a computer-readable recording medium, and may be constituted by, for example, at least one of a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile 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, a stick, a key drive), a magnetic stripe, a database, a server, and other appropriate storage media. The storage 1003 may be referred to as an auxiliary storage device.

[0485] 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).

[0486] 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).

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

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

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

[0490] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0508] 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".

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

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

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

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

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

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

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

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

[0517] 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).

[0518] 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).

[0519] 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).

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

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

[0522] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0539] Figure 22 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.

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

[0541] 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).

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

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

[0544] 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.).

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

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

[0547] 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).

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

[0549] 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).

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

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

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

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

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

[0555] 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).

[0556] 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."

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

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

[0559] 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).

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

[0561] 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….”

[0562] 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).

[0563] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0564] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0565] In this 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, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0566] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0567] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

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

[0569] In this disclosure, terms such as "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, terms 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. Furthermore, in this disclosure, terms 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 as "i-th highest").

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

[0571] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0572] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0573] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0574] This application is based on Japanese Patent Application No. 2024-195896, filed on November 8, 2024. All of its contents are included here.

Claims

1. A terminal having, when at least one of the following is satisfied: a first case in which beam reporting initiated by the terminal is set up for multiple component carriers, and a second case in which multiple events are set up for one component carrier or one reporting setting, a component carrier on which a first uplink (UL) channel relating to the beam reporting, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal are each transmitted; a control unit that determines information contained in the first UL channel, information contained in the DL signal, and information contained in the second UL channel; and a transmitting / receiving unit that transmits the first UL channel and the second UL channel and receives the DL signal.

2. The terminal according to claim 1, wherein the control unit controls the second UL channel in one component carrier to include beam reports corresponding to one or more events when the second case is met.

3. The terminal according to claim 1, wherein, when the first case is met, the transmitting / receiving unit transmits the second UL channel using either the component carrier on which the triggered reporting setting is set, or a component carrier other than the component carrier on which the triggered reporting setting is set, from among the plurality of component carriers.

4. The terminal according to claim 1, wherein the control unit controls the second UL channel to include at least one of the component carrier identifier and the event identifier corresponding to the beam report contained in the second UL channel when both the first and second cases are satisfied.

5. A wireless communication method for a terminal, comprising the steps of: determining a component carrier to which a first uplink (UL) channel relating to the beam report, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal are transmitted, when at least one of a first case in which a beam report initiated by the terminal is set up for multiple component carriers, and a second case in which multiple events are set up for one component carrier or one report setting, the first uplink (UL) channel relating to the beam report, the information contained in the first UL channel, the information contained in the DL signal, and the information contained in the second UL channel; and transmitting the first UL channel and the second UL channel, and receiving the DL signal.

6. A base station having, when at least one of the following is satisfied: a first case in which beam reporting initiated by a terminal is set up for multiple component carriers, and a second case in which multiple events are set up for one component carrier or one reporting setting, a component carrier on which a first uplink (UL) channel relating to the beam reporting, a downlink (DL) signal based on the first UL channel, and a second UL channel scheduled by the DL signal are each transmitted; a control unit that determines information contained in the first UL channel, information contained in the DL signal, and information contained in the second UL channel; and a transceiver unit that transmits the first UL channel and the second UL channel and receives the DL signal.

Images