Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising: a reception unit that receives a reporting configuration for beam reporting that is initiated by the terminal; and a control unit that, when the beam reporting is configured for a plurality of component carriers, controls determination of a resource for a first uplink (UL) channel for the beam reporting based on a resource identifier (ID) included in the reporting configuration, and transmission of a second UL channel for the beam reporting associated with the first UL channel. The terminal is also characterized in that a downlink (DL) channel based on the first UL channel is not transmitted. Said one aspect of the present disclosure makes it possible to 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 standardized 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 standardized.

[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 UE-initiated Beam Report (UEIBR), which is initiated by a terminal (user terminal, User Equipment (UE)) based on an event.

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

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

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

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a reporting setting for beam reporting initiated by the terminal, and a control unit that, when beam reporting is set for multiple component carriers, controls the determination of a resource for a first uplink (UL) channel for beam reporting based on a resource identifier (ID) included in the reporting setting, and the transmission of a second UL channel for beam reporting associated with the first UL channel, wherein no downlink (DL) channel based on the first UL channel is transmitted.

[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. Figures 2A-2C show an example of CC / reporting settings / first UL channel / first DL channel / second UL channel in UEIBR. Figures 3A and 3B show an example of reporting settings in the first embodiment. Figures 4A and 4B show other examples of reporting settings in the first embodiment. Figures 5A and 5B show other examples of reporting settings in the first embodiment. Figure 6 shows an example of settings according to Embodiment 2-1. Figure 7 shows an example of settings according to Embodiment 2-2. Figure 8 shows an example of UL resource determination according to Embodiment 3-1-1. Figure 9 shows an example of UL resource determination according to Embodiment 3-1-2. Figure 10 shows an example of UL resource determination according to Embodiment 3-2-1. Figure 11 shows an example of UL resource determination according to Embodiment 3-2-2. Figure 12 is a diagram showing an example of UL resource determination according to Embodiment 3-3-1. Figure 13 is a diagram showing an example of UL resource determination according to Embodiment 3-3-2. Figure 14 is a diagram showing an example of UL resource determination according to Embodiment 3-4. Figure 15 is a diagram showing an example of UEIBR operation according to Embodiment 4-1-2. Figure 16 is a diagram showing an example of UEIBR operation according to Embodiment 4-2-2. Figure 17 is a diagram showing an example of UEIBR operation according to Embodiment 4-3-2. Figure 18 is a diagram showing an example of UEIBR operation according to Embodiment 4-4. Figure 19 is a diagram showing an example of UEIBR operation according to Embodiment 5-1-2. Figure 20 is a diagram showing an example of the schematic configuration of a wireless communication system according to one embodiment. Figure 21 is a diagram showing an example of the configuration of a base station according to one embodiment. Figure 22 is a diagram showing an example of the configuration of a user terminal according to one embodiment. Figure 23 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 24 is a diagram showing 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-Based 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-level 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 per 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) is above the threshold of the best quality RS derived from the M best quality activated TCI states (M is 1 or greater, and M may be set by RRC (based on UE capability reporting)). - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) is above the threshold of the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the set reference RS (which may be SSB / CSI-RS).

[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 is the QCL RS of the indicated TCI state and the SSB that is QCLed. - 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 SSB that is QCLed.

[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 indicated 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 (e.g., one CSI-RS for tracking) may be set as the QCL-RS indicating the TCI state (e.g., Type A / D).

[0047] When only the TRS is set as the QCL-RS indicating the TCI state, a reference signal different from the TRS (e.g., 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 indicated 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 indicated 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., PUSCH / 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 (e.g., PUSCH / PUCCH) resource.

[0058] Step 3: The UE transmits the beam report using a resource (UCI) on the second UL channel (e.g., PUSCH / PUCCH).

[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 (e.g., PUSCH / PUCCH) 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 (e.g., PUSCH / PUCCH) (e.g., 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] The events exemplified in this way do not exclude other events. Furthermore, the MIMO 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").

[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] (Analysis) The aforementioned UEIBR considers scenarios that utilize multiple CCs.

[0103] In this scenario, each beam report from each CC may be transmitted (multi-CC scenario), or a measurement report from another CC may be triggered in one CC, and beam reports may be transmitted in that CC / other CC (cross-CC scenario).

[0104] However, detailed procedures and settings for using multiple CCs in a UEIBR (User Accounting Code) have not been sufficiently considered.

[0105] More specifically, in scenarios using multiple CCs, where each CC has multiple reporting settings for the same / different events, and a single primary UL channel resource is shared for reporting from multiple CCs, there is insufficient consideration given to how to define / configure the appropriate primary UL channel.

[0106] For example, as shown in Figure 2A, suppose reporting settings #0-0 to #0-2 are set for CC#0 (e.g., SPCell / PUCCH SCell), reporting settings #1-0 to #1-2 are set for CC#1, reporting settings #2-0 to #2-2 are set for CC#2, and an event related to reporting setting #1-0 is triggered / satisfied. In this case, as in the case of mode A shown in Figure 2B, if the first UL channel (e.g., first PUCCH) is transmitted via CC#0, the first UL channel may not be able to be transmitted via CC#1.

[0107] Furthermore, in cases where the transmitted CC is different, the network may not be able to recognize the CC associated with the transmitted first UL channel, and may not be able to transmit the first DL channel with the appropriate CC.

[0108] In addition to Mode A as shown in Figure 2B, in Mode B as shown in Figure 2C, the payload of the second UL channel may differ depending on the event. In such a situation, the network needs to recognize the event associated with the first UL channel at the first UL channel stage, but the specific method for doing so is not clear.

[0109] Furthermore, in the case of Mode B as shown in Figure 2C, it is possible to specify that the CC will not transmit on the second UL channel if the first UL channel is not transmitted, and to allocate the resources for the second UL channel to other purposes, but this method is also not clear.

[0110] If the detailed definition / configuration of the appropriate first UL channel in such cases is not sufficiently considered, it may not be possible to guarantee UEIBR operation, and the efficiency of resource utilization and improvement of the transmitted puts may be suppressed.

[0111] Therefore, the inventors of this invention came up with a way to solve this problem.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0147] In this disclosure, "target," "changed," "target," "directed," "updated," etc., may be interpreted interchangeably.

[0148] In this disclosure, the triggering of a CC / reporting setting / event setting report may mean that an event corresponding to the CC / reporting setting / event setting occurs.

[0149] (Wireless communication method) The UE may apply each embodiment of the present 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 present disclosure. Furthermore, the NW / BS / gNB may perform various operations / controls necessary to receive the beam report / UEIBR from the UE.

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

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

[0152] Each embodiment of this disclosure may be applied to at least one of Case 1 and Case 2 described above.

[0153] Each embodiment of the present disclosure may be applied in at least one of Mode A and Mode B described above.

[0154] This disclosure primarily describes the configuration of the first UL channel.

[0155] Each embodiment of this disclosure may be applied, for example, when certain higher layer (RRC) parameters are set.

[0156] For example, each embodiment of the present disclosure may be applicable in at least one of the following cases: when multiple events are set for one CC by RRC parameters, and when a UEIBR that utilizes multiple CCs (UEIBR for multiple CCs) is set.

[0157] <First Embodiment> The first embodiment relates to the details of reporting settings for the UEIBR / First UL channel.

[0158] UE may receive reporting settings for the UEIBR / First UL channel using specific RRC parameters.

[0159] The reporting setting may include, for example, a reporting setting ID and at least one ID indicating a resource for the first UL channel.

[0160] In this disclosure, the resources for the first UL channel, the first UL channel resources, and the first UL channel transmission resources may mean resources used for transmission on the first UL channel.

[0161] The ID indicating the resource for the first UL channel may include, for example, at least one of the resource ID for scheduling requests (e.g., SchedulingRequestResourceID) and the scheduling request ID (e.g., SchedulingRequestID).

[0162] The ID indicating resources for the first UL channel may include, for example, an ID indicating resources for a UCI [new UCI type introduced in Rel. 19 or later].

[0163] The ID indicating the resource for the first UL channel may include the resource ID for the first UL channel for UEIBR (e.g., PUCCH) (e.g., UEIBR-1stPUCCHResourceId).

[0164] The ID indicating the resource for the first UL channel may be included, for example, in the event configuration within the reporting configuration (e.g., EventConfig-r19).

[0165] According to this, for example, in cases where a single reporting setting includes multiple event settings, each event (setting) can be associated with a resource for the first UL channel.

[0166] The ID indicating the resource for the first UL channel may be included, for example, within the reporting configuration (but outside the event configuration (e.g., EventConfig-r19)).

[0167] According to this, for example, in a case where one event setting is included within one reporting setting, it is possible to associate that one event (setting) with a resource for the first UL channel.

[0168] The reporting setting in question may be, for example, an existing reporting setting (as defined up to Rel. 18) that is being extended.

[0169] For example, the reporting setting may be the CSI reporting setting for LTM [as defined in Rel. 18] (e.g., LTM-CSI-ReportConfig-r18).

[0170] The CSI reporting settings for the LTM may be applied / used in specific scenarios, for example (e.g., the mobility / LTM case).

[0171] Alternatively, for example, the reporting setting may be the CSI reporting setting [as defined in Rel. 15] (e.g., CSI-ReportConfig).

[0172] The CSI reporting settings may be applied / used, for example, in specific scenarios (e.g., the MIMO case).

[0173] Furthermore, for example, the reporting setting may be a CSI reporting setting for UEIBR (specifically for UEIBR) [newly defined in Rel. 19 and later] (e.g., UEIBR-CSI-ReportConfig-r19).

[0174] The CSI reporting settings may be applied / used in specific scenarios, for example (e.g., the mobility / LMT / MIMO case).

[0175] Figures 3A and 3B show an example of a reporting configuration in the first embodiment. The CSI reporting configuration for LTM (for example, LTM-CSI-ReportConfig-r18) includes an event configuration (for example, EventConfig-r19). This event configuration may include, for example, an event ID (for example, eventId-r19 / EventId-r19), threshold parameters related to the event (for example, threshold2-forEvent-r19 / threshold1-forEvent-r19), and at least one of filtering parameters related to the event (for example, a parameter indicating the time until trigger (TimeToTrigger (TTT)) and at least one of a parameter indicating a timer / counter). The reporting configuration also includes a setting for the reporting content (for example, ltm-ReportContent-r19 (which may include the maximum number of beams to report)).

[0176] In the example shown in Figure 3A, the event configuration includes a scheduling request resource ID (e.g., SchedulingRequestResourceID) to indicate the first UL channel resource. Alternatively, the event configuration may also include a scheduling request ID (e.g., SchedulingRequestID) in addition to the scheduling request resource ID.

[0177] Furthermore, in the example shown in Figure 3B, the event settings include a first PUCCH resource ID for UEIBR (e.g., UEIBR-1stPUCCHResourceId) to indicate the first UL channel resource.

[0178] Figures 4A and 4B show other examples of reporting configurations in the first embodiment. In the examples shown in Figures 4A and 4B, the reporting type setting (e.g., reportConfigType) within the CSI reporting configuration (e.g., CSI-ReportConfig) [as defined in Rel. 15] includes a triggered parameter for the UEIBR (e.g., UEI-triggered-r19). This triggered parameter may include, for example, an event ID (e.g., eventId-r19 / EventId-r19), a threshold parameter associated with the event (e.g., threshold2-forEvent-r19 / threshold1-forEvent-r19), and at least one of a filtering parameter associated with the event (e.g., a parameter indicating the time to trigger (TimeToTrigger (TTT)) and at least one of a parameter indicating a timer / counter).

[0179] In the example shown in Figure 4A, the triggered parameter includes a scheduling request resource ID (e.g., SchedulingRequestResourceID) to indicate the first UL channel resource. Alternatively, the triggered parameter may also include a scheduling request ID (e.g., SchedulingRequestID) in addition to the scheduling request resource ID.

[0180] Furthermore, in the example shown in Figure 4B, the triggered parameter includes a first PUCCH resource ID for UEIBR (e.g., UEIBR-1stPUCCHResourceId) to indicate the first UL channel resource.

[0181] The triggered parameter may be included in, for example, a parameter of the reporting configuration type (e.g., reportConfigType), or it may be set independently outside of the parameters of the reporting configuration type.

[0182] Figures 5A and 5B show other examples of reporting configurations in the first embodiment. In the examples shown in Figures 5A and 5B, the CSI reporting configuration for UEIBR (e.g., UEIBR-CSI-ReportConfig-r19), which is newly defined in Rel. 19 and later, includes an event configuration (e.g., EventConfig-r19). This event configuration may include, for example, an event ID (e.g., eventId-r19 / EventId-r19), threshold parameters related to the event (e.g., threshold2-forEvent-r19 / threshold1-forEvent-r19), and at least one of the filtering parameters related to the event (e.g., a parameter indicating the time to trigger (TimeToTrigger (TTT)) and at least one of the parameters indicating a timer / counter). Furthermore, the examples shown in Figures 5A and 5B include an ID for identifying the reporting configuration (for example, UEIBR-CSI-ReportConfigId-r19) and settings related to the reporting content within the reporting configuration (for example, UEIBR-ReportContent-r19, which may include the maximum number of beams to be reported).

[0183] In the example shown in Figure 5A, the event configuration includes a scheduling request resource ID (e.g., SchedulingRequestResourceID) to indicate the first UL channel resource. Alternatively, the event configuration may also include a scheduling request ID (e.g., SchedulingRequestID) in addition to the scheduling request resource ID.

[0184] Furthermore, in the example shown in Figure 5B, the event settings include a first PUCCH resource ID for UEIBR (e.g., UEIBR-1stPUCCHResourceId) to indicate the first UL channel resource.

[0185] According to the first embodiment described above, by appropriately defining the reporting settings for the UEIBR, the first UL channel resource for the UEIBR can be appropriately configured.

[0186] <Second Embodiment> The second embodiment relates to the details of resource configuration for the UEIBR / First UL channel.

[0187] Resource settings for the first UL channel may be configured using specific RRC parameters.

[0188] <<Embodiment 2-1>> Resource settings for the first UL channel may be configured, for example, using existing RRC parameters (as defined up to Rel. 18).

[0189] The RRC parameter may be, for example, at least one of the following for an existing scheduling request: a PUCCH setting (e.g., PUCCH-Config), a scheduling request setting (e.g., SchedulingRequestConfig), and a scheduling request resource setting (e.g., SchedulingRequestResourceConfig).

[0190] The UE may reuse existing scheduling request transmission behavior (as defined up to Rel. 18) for transmission on the first UL channel.

[0191] For example, the first UL channel may be associated with one or more scheduling request IDs (e.g., schedulingRequestID).

[0192] For example, the resource for the first UL channel may be determined based on a scheduling request resource configuration (e.g., SchedulingRequestResourceConfig) identified by a scheduling request resource ID (e.g., schedulingRequestResourceId).

[0193] For example, the first UL channel may be assumed to be transmitted [only] in a specific cell / CC (e.g., a special cell (SpCell, e.g., PCell / PSCell) / PUCCH SCell).

[0194] For example, scheduling request settings (e.g., SchedulingRequestConfig) and scheduling request resource settings (e.g., SchedulingRequestResourceConfig) may be associated (one-to-one).

[0195] Multiple scheduling request resource settings (e.g., SchedulingRequestResourceConfig) may be configured, and a single list may contain up to a specific number of scheduling request resource settings (e.g., eight).

[0196] According to this, the number of PUCCH resources that can be allocated to UEIBR can be kept below a certain number, thereby ensuring resource utilization efficiency.

[0197] Figure 6 shows an example of the settings according to Embodiment 2-1. In the example shown in Figure 6, the PUCCH setting (for example, PUCCH-Config) includes a list of scheduling request resources (for example, schedulingRequestResourceList (or schedulingRequestToAddModList)). The list of scheduling request resources includes up to eight scheduling request resource settings (for example, SchedulingRequestResourceConfig).

[0198] Furthermore, in the example shown in Figure 6, the scheduling request configuration (e.g., SchedulingRequestConfig) includes a list of scheduling requests (for example, schedulingRequestList (or schedulingRequestToAddModList)). The list of scheduling requests may contain up to eight SchedulingRequestToAddMods, each identified by a scheduling request ID (e.g., schedulingRequestId).

[0199] By using parameters as illustrated in Figure 6, the number of PUCCH resources that can be allocated to UEIBR can be kept to eight or less.

[0200] According to Embodiment 2-1, by using existing RRC parameters to set resources for the first UL channel, it becomes possible to implement appropriate UEIB operation while minimizing the impact on the specifications.

[0201] <<Embodiment 2-2>> Resource settings for the first UL channel may be configured, for example, using the RRC parameter [as defined in Rel. 19 and later].

[0202] The RRC parameter may be, for example, at least one of a list of resources for the first UL channel in the UEIBR (e.g., UEIBR-1stPUCCH-ResourceList) and a resource setting for the first UL channel in the UEIBR (e.g., UEIBR-1stPUCCH-Resource).

[0203] The list of resources for the first UL channel in the UEIBR (e.g., UEIBR-1stPUCCH-ResourceList) may include at least one resource setting for the first UL channel in the UEIBR (e.g., UEIBR-1stPUCCH-Resource).

[0204] The RRC parameter may include, for example, a specific number of resource IDs and elements / parameters for a first UL channel (e.g., PUCCH) associated with those resource IDs.

[0205] The minimum and maximum numbers of this specific number may be defined. The minimum number may be, for example, 1, and the maximum number may be, for example, N. This allows the number of PUCCH resources that can be allocated to UEIBR to be less than or equal to N, thereby ensuring resource utilization efficiency.

[0206] <<<Option 2-2-1>>> The RRC parameter may include, for example, a parameter that [explicitly] indicates the CC / cell to which the first UL channel is transmitted.

[0207] The UE may select / determine a CC / cell to transmit the first UL channel based on / because of the parameter. The UE may decide to use the resource associated with the resource ID in the selected / determined CC / cell to transmit the first UL channel.

[0208] According to this, flexible control becomes possible without limiting the cells transmitting the first UL channel to specific cells (e.g., SpCell / PUCCH SCell), thereby improving resource utilization efficiency.

[0209] <<<Option 2-2-2>>> The RRC parameter does not have to include, for example, a parameter that [explicitly] indicates the CC / cell to which the first UL channel is transmitted.

[0210] The UE may determine the CC / cell to be used for transmitting the first UL channel using the existing scheduling request transmission behavior (as defined up to Rel. 18). In other words, the first UL channel may be assumed to be transmitted [only] in a specific cell / CC (e.g., a special cell (SpCell, e.g., PCell / PSCell) / PUCCH SCell).

[0211] Figure 7 shows an example of the settings according to Embodiment 2-2. In the example shown in Figure 7, the PUCCH setting (for example, PUCCH-Config) includes a list of first UL channel (e.g., PUCCH) resources for UEIBR (for example, UEIBR-1stPUCCHResourceList (or UEIBR-1stPUCCHResourceToAddModList)). This list includes up to N first UL channel (e.g., PUCCH) resource settings for UEIBR (for example, UEIBR-1stPUCCHResource).

[0212] Furthermore, in the example shown in Figure 7, the resource settings include a resource ID (for example, UEIBR-1stPUCCHResourceId), a PUCCH resource ID (for example, resource / PUCCH-ResourceId), and a parameter indicating the CC / cell to which the first UL channel is transmitted (for example, ServCellIndex).

[0213] According to Embodiment 2-2, by using newly defined RRC parameters to set resources for the first UL channel, it becomes possible to implement more flexible and appropriate UEIBR operation.

[0214] According to the second embodiment described above, the first UL channel resource for the UEIBR can be appropriately configured / defined.

[0215] <Third Embodiment> The third embodiment relates to the determination operation of the first UL channel resource.

[0216] The third embodiment can be broadly classified into the following embodiments 3-1 to 3-4. Any of the following embodiments 3-1 to 3-4 may be applied, or at least two of the following embodiments 3-1 to 3-4 may be applied in combination, or at least two of the following embodiments 3-1 to 3-4 may be switched and applied based on a specific setting / instruction.

[0217] <<Embodiment 3-1>> The first UL channel resource may be configured separately for each CC / cell and for each reporting setting / event [setting].

[0218] A number of first UL channel resources may be configured to correspond to reporting settings / events [settings] that are included across multiple (for example, all) CCs.

[0219] The first UL channel resource may be uniquely assigned a resource ID.

[0220] The first UL channel resource may be configured using a list, or it may be configured without using a list.

[0221] <<<Embodiment 3-1-1>>> A CC / report setting / event that triggers a report may be configured to correspond one-to-one with the first UL channel resource.

[0222] The network may determine / identify the triggered CC / reporting settings / events based on the first UL channel resource it receives.

[0223] Each reporting setting may include the resource ID of the primary UL channel resource used when reporting is triggered.

[0224] When a report is triggered, the UE may send the report using the first UL channel resource corresponding to the resource ID.

[0225] Figure 8 shows an example of UL resource determination according to Embodiment 3-1-1. In the example shown in Figure 8, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 8, CC / report settings / events are set to correspond one-to-one with the first UL channel resource.

[0226] In the example shown in Figure 8, an event corresponding to reporting setting #1-0 occurs. At this time, the UE determines and uses the first UL channel (e.g., PUCCH) resource (e.g., first UL channel resource #1-0) corresponding to reporting setting #1-0, in both mode A and mode B.

[0227] <<<Embodiment 3-1-2>>> The correspondence between the CC / report setting / event that triggers the report and the first UL channel resource does not need to be configured.

[0228] The resources for the first UL channel may be set to a number calculated as CC count * reporting settings (or number of events). Alternatively, the resources for the first UL channel may be set to a number calculated as CC count * reporting settings * number of events.

[0229] The UE / NW may determine the first UL channel resource to be used for triggered reporting according to / based on specific rules that are predetermined.

[0230] Rule 3-1-2-1: Multiple pre-configured reporting settings may first be sorted in ascending (or descending) order by CC ID, then in ascending / descending order by Event ID, and the sorted reporting settings may then be associated in ascending / descending order with the Resource ID of the first UL channel resource.

[0231] Rule 3-1-2-2: Multiple pre-configured reporting settings may first be sorted in ascending (or descending) order by event ID, then in ascending / descending order by CC ID, and the sorted reporting settings may then be associated in ascending / descending order with the resource ID of the first UL channel resource.

[0232] Note that rules 3-1-2-1 and 3-1-2-2 above are merely examples, and CC ID, event ID, resource ID, and other IDs may be interchangeable.

[0233] Figure 9 shows an example of UL resource determination according to Embodiment 3-1-2. In the example shown in Figure 9, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 9, a plurality of pre-configured first UL channel resources are sorted in ascending (or descending) order by the triggered CC / event, and resource IDs are assigned to the sorted first UL channel resources in ascending (or descending) order.

[0234] In the example shown in Figure 9, an event corresponding to reporting setting #1-0 occurs. In this case, the UE selects / determines / uses CC#1, the event ID corresponding to reporting setting #1-0, and the associated resource ID from the sorted first UL channel resources, regardless of whether it is mode A or B.

[0235] <<Embodiment 3-2>> The first UL channel resource may be set separately for each CC / cell.

[0236] A single primary UL channel resource corresponding to a CC / cell may be shared (common) across multiple reporting settings / events [settings].

[0237] A first UL channel resource may be configured with a number of multiple (for example, all) CCs.

[0238] The first UL channel resource may be uniquely assigned a resource ID.

[0239] The first UL channel resource may be configured using a list, or it may be configured without using a list.

[0240] <<<Embodiment 3-2-1>>> A CC that triggers a report and a first UL channel resource may be configured to correspond one-to-one.

[0241] The network may determine / identify the triggered CC based on the first UL channel resource it receives.

[0242] Each reporting setting may include the resource ID of the primary UL channel resource used when reporting is triggered.

[0243] When a report is triggered, the UE may send the report using the first UL channel resource corresponding to the resource ID.

[0244] Within one or more reporting settings corresponding to a particular CC, the resource ID of the same first UL channel resource may be included. In this case, the resource IDs of different first UL channel resources may be included separately (for example, different) in reporting settings corresponding to different CCs.

[0245] For example, CC#1's reporting settings #1-3 may be configured to use the first PUCCH resource #1, and CC#2's reporting settings #1-3 may be configured to use the first PUCCH resource #2.

[0246] Figure 10 shows an example of determining UL resources according to Embodiment 3-2-1. In the example shown in Figure 10, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 10, CC (and multiple report settings in CC) and the first UL channel resource are set to correspond one-to-one.

[0247] In the example shown in Figure 10, an event corresponding to reporting setting #1-0 occurs. At this time, the UE determines and uses the first UL channel (e.g., PUCCH) resource corresponding to CC#1, in both mode A and mode B.

[0248] <<<Embodiment 3-2-2>>> The correspondence between the CC that triggers the report and the first UL channel resource does not need to be set.

[0249] The number of resources for the first UL channel to be configured may be the same as the number of CCs. Alternatively, the number of resources for the first UL channel may be set to a number calculated as the number of CCs * number of events.

[0250] The UE / NW may determine the first UL channel resource to be used for triggered reporting according to / based on specific rules that are predetermined.

[0251] For example, multiple pre-configured reporting settings may be sorted in ascending (or descending) order by CC ID, and the sorted reporting settings may then be associated in ascending / descending order with the resource ID of the first UL channel resource.

[0252] Please note that this rule is merely an example, and CC IDs, resource IDs, and other IDs may be interpreted as interchangeable.

[0253] Figure 11 shows an example of determining UL resources according to Embodiment 3-2-2. In the example shown in Figure 11, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 11, a plurality of pre-configured first UL channel resources are sorted in ascending (or descending) order for CC, and resource IDs are assigned to the sorted first UL channel resources in ascending (or descending) order.

[0254] In the example shown in Figure 11, an event corresponding to reporting setting #1-0 occurs. At this time, in both mode A and mode B, the UE selects / determines the resource ID associated with CC#1 from the sorted first UL channel resources.

[0255] <<Embodiment 3-3>> The first UL channel resource may be configured separately for each reporting setting / event [setting].

[0256] A single first UL channel resource corresponding to a certain reporting setting / event [setting] may be shared (common) across multiple CCs / cells.

[0257] The number of first UL channels configured may also be the number of reporting settings / events (settings) in each CC for multiple CCs.

[0258] The first UL channel resource may be uniquely assigned a resource ID.

[0259] The first UL channel resource may be configured using a list, or it may be configured without using a list.

[0260] <<<Embodiment 3-3-1>>> A report setting / event (setting) that triggers a report may be configured to correspond one-to-one with the first UL channel resource.

[0261] The network may determine / identify the triggered reporting settings / events (settings) based on the first UL channel resource it receives.

[0262] Each reporting setting may include the resource ID of the primary UL channel resource used when reporting is triggered.

[0263] When a report is triggered, the UE may send the report using the first UL channel resource corresponding to the resource ID.

[0264] For multiple (e.g., all) CCs, reporting settings corresponding to the same ID / event (setting) ID may have the same resource ID of the first UL channel resource. For multiple (e.g., all) CCs, reporting settings corresponding to different IDs / event (setting) IDs may have separate (different) resource IDs of the first UL channel resources.

[0265] For example, CC#0's reporting setting #1 (e.g., reporting setting #0-1), CC#1's reporting setting #1 (e.g., reporting setting #1-1), and CC#2's reporting setting #1 (e.g., reporting setting #2-1) may be configured to use the same first UL channel resource (e.g., PUCCH resource #1), while CC#0's reporting setting #2 (e.g., reporting setting #0-2), CC#1's reporting setting #2 (e.g., reporting setting #1-2), and CC#2's reporting setting #2 (e.g., reporting setting #2-2) may be configured to use the same first UL channel resource (e.g., PUCCH resource #2).

[0266] Figure 12 shows an example of UL resource determination according to Embodiment 3-3-1. In the example shown in Figure 12, UEIBR is set for the UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 12, the report settings and the first UL channel resource are set to correspond one-to-one.

[0267] In the example shown in Figure 12, an event corresponding to reporting setting #1-0 occurs. At this time, the UE determines the first UL channel (e.g., PUCCH) resource corresponding to reporting setting #0 (e.g., reporting settings #0-1 to #2-0) in both mode A and mode B.

[0268] <<<Embodiment 3-3-2>>> The correspondence between the reporting setting / event (setting) that triggers the report and the first UL channel resource does not need to be configured.

[0269] The number of resources for the first UL channel that is configured may be the same as the number of reporting settings. Alternatively, the number of resources for the first UL channel may be calculated as the number of reporting settings multiplied by the number of events.

[0270] The UE / NW may determine the first UL channel resource to be used for triggered reporting according to / based on specific rules that are predetermined.

[0271] For example, multiple pre-configured reporting settings may be sorted in ascending (or descending) order by reporting setting ID / event (setting) ID, and the sorted reporting settings may then be associated in ascending / descending order with the resource ID of the first UL channel resource.

[0272] Please note that this rule is merely an example, and CC IDs, resource IDs, and other IDs may be interpreted as interchangeable.

[0273] Figure 13 shows an example of UL resource determination according to Embodiment 3-3-2. In the example shown in Figure 13, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 13, a plurality of pre-configured first UL channel resources are sorted in ascending (or descending) order with respect to their report settings, and resource IDs are assigned to the sorted first UL channel resources in ascending (or descending) order.

[0274] In the example shown in Figure 13, an event corresponding to reporting setting #1-0 occurs. At this time, in both mode A and mode B, the UE selects / determines the resource ID associated with reporting setting #0 (for example, reporting settings #0-1 to #2-0) from the sorted first UL channel resources.

[0275] <<Embodiment 3-4>> The first UL channel resource may be set in common for multiple (for example, all) CC / cell / report settings / event [settings].

[0276] When UEIBR is configured for multiple CCs, a single (specific) first UL channel resource may be configured regardless of the number of CCs or the number of reporting settings / events (settings) per CC.

[0277] Regardless of which CC / reporting setting / event (setting) triggers a report at a given measurement timing, the UE may use that single first UL channel resource.

[0278] Any reporting configuration for the UEIBR set for a UE may include a common first UL channel resource (ID). The UE may assume / determine that any reporting configuration for the UEIBR set includes a common first UL channel resource (ID).

[0279] A specific reporting configuration for a UEIBR may include one primary UL channel resource (ID), while reporting configurations for other UEIBRs may not include a primary UL channel resource (ID). In this case, the UE may assume / determine that the single primary UL channel resource will be used for multiple (e.g., all) CCs / cells / reporting configurations / events.

[0280] Figure 14 shows an example of UL resource determination according to Embodiment 3-4. In the example shown in Figure 14, UEIBR is set for the UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2. In the example shown in Figure 14, the UE uses a specific first UL channel resource regardless of which CC / report setting / event (setting) triggers the report.

[0281] According to the third embodiment described above, it is possible to define the operation for determining the appropriate first UL channel resource for the UEIBR corresponding to multiple CC / report settings / events.

[0282] <Fourth Embodiment> In each of embodiments 3-1 / 3-2 / 3-3 / 3-4 of the third embodiment described above, it is conceivable that the content of the first and second UL channels required to ensure UEIBR operation (for example, transmission and reception operation of the first UL channel / first DL channel / second UL channel) may differ.

[0283] Therefore, in the fourth embodiment described below, the details of the content of the first / second UL channels will be explained.

[0284] This embodiment may be applied in combination with the third embodiment described above, or it may be applied independently of the third embodiment.

[0285] In this embodiment, one CC may trigger a report based on one event [simultaneously].

[0286] <<Embodiment 4-1>> <<<Embodiment 4-1-1>>> Embodiment 4-1-1 may correspond, for example, to Embodiment 3-1-1 described above.

[0287] A CC / reporting setting / event (setting) that triggers reporting may be configured to have a one-to-one correspondence with the first UL channel resource. The network may determine / identify the CC / reporting setting / event (setting) that triggers reporting based on the resources of the first UL channel it receives.

[0288] The first UL channel may transmit information indicating whether or not a report is triggered regarding the CC / reporting settings.

[0289] This information may, for example, be a single bit of information.

[0290] The UE may transmit the first UL channel using resources corresponding to the CC / reporting settings.

[0291] The network may determine / identify the CC / reporting settings / events (settings) that trigger reporting based on the resource, and perform subsequent actions (e.g., sending via the first DL channel / sending via the second UL channel) based on that determination / identification.

[0292] <<<Embodiment 4-1-2>>> Embodiment 4-1-2 may correspond, for example, to Embodiment 3-1-2 described above.

[0293] The correspondence between the CC / report settings / events (settings) that trigger the report and the first UL channel resource does not need to be configured. The first UL channel resource may be associated with the triggered CC / report / event according to specific rules defined in advance.

[0294] The first UL channel may contain at least two bits (multiple bits) of information.

[0295] This information may include, for example, at least the ID of the CC / cell from which the report is triggered.

[0296] The UE may transmit the first UL channel using resources allocated based on predetermined rules.

[0297] The network may determine / identify the CC that triggers the report based on the CC / cell ID included in the first UL channel, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0298] Furthermore, this information may include the ID of the event that triggers the report (in addition to the CC / cell ID).

[0299] The payload / size of the second UL channel may differ for each event. In this case, the first UL channel may include the CC / cell ID and event ID.

[0300] The network may determine / identify the event that triggers reporting based on the event ID included in the first UL channel, and perform subsequent actions (e.g., sending to the first DL channel / sending to the second UL channel) based on that determination / identification.

[0301] In this case, the network can identify the event (ID) before the second UL channel is transmitted / received / scheduled, so the event ID does not need to be included in the second UL channel.

[0302] For multiple events (for example, all of them), the payload / size of the second UL channel may be the same. In this case, the first UL channel may include the CC / cell ID but not the event ID.

[0303] The network does not need to be aware of events that are triggered before the second UL channel is transmitted, received, or scheduled.

[0304] In this case, the network may include an event ID in the second UL channel to identify the reported event.

[0305] Figure 15 shows an example of UEIBR operation according to Embodiment 4-1-2. In the example shown in Figure 15, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2.

[0306] In the example shown in Figure 15, an event corresponding to reporting setting #1-0 occurs. At this time, the UE transmits a first UL channel corresponding to CC / reporting setting / event (CC#1 / reporting setting #0 (#1-0) in the figure) (for example, in mode A). Next, the NW transmits a first DL channel, taking into consideration that it is a report / event triggered in CC#1 based on the information contained in the first UL channel. At this time, the UE may or may not include the event ID in the second UL channel scheduled by the first DL channel. The second UL channel may also be transmitted using a different CC (for example, CC#1) than the first UL channel / first DL channel.

[0307] <<Embodiment 4-2>> <<<Embodiment 4-2-1>>> Embodiment 4-2-1 may correspond, for example, to Embodiment 3-2-1 described above.

[0308] A CC that triggers a report may be configured to have a one-to-one correspondence with a first UL channel resource. The UE may transmit the first UL channel using the resource corresponding to the CC. The NW may determine / identify the CC that triggers the report based on the resources of the first UL channel it receives, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0309] The first UL channel may transmit only one bit of information. In this case, the information may indicate whether or not a report is triggered in the corresponding CC.

[0310] Furthermore, the first UL channel may contain at least two bits (multiple bits) of information.

[0311] For example, the information may include the ID of the event that triggers the report.

[0312] The payload / size of the second UL channel may differ for each event. In this case, the event ID may be included in the first UL channel.

[0313] The network may determine / identify the event that triggers reporting based on the event ID included in the first UL channel, and perform subsequent actions (e.g., sending to the first DL channel / sending to the second UL channel) based on that determination / identification.

[0314] In this case, the network can identify the event (ID) before the second UL channel is transmitted / received / scheduled, so the event ID does not need to be included in the second UL channel.

[0315] The payload / size of the second UL channel may be common for multiple (e.g., all) events. In this case, the event ID may not be included in the first UL channel (e.g., the first UL channel may transmit only 1 bit of information).

[0316] The network does not need to be aware of events that are triggered before the second UL channel is transmitted, received, or scheduled.

[0317] In this case, the network may include an event ID in the second UL channel to identify the reported event.

[0318] <<<Embodiment 4-2-2>>> Embodiment 4-2-2 may correspond, for example, to Embodiment 3-2-2 described above.

[0319] The correspondence between the CC that triggers the report and the first UL channel resource does not need to be established. The first UL channel resource may be associated with the CC that triggers the report according to specific rules that are defined in advance.

[0320] The first UL channel may contain at least two bits (multiple bits) of information.

[0321] This information may include, for example, at least the ID of the CC / cell from which the report is triggered.

[0322] The UE may transmit the first UL channel using resources allocated based on predetermined rules.

[0323] The network may determine / identify the CC that triggers the report based on the CC / cell ID included in the first UL channel, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0324] Furthermore, this information may include the ID of the event that triggers the report (in addition to the CC / cell ID).

[0325] The payload / size of the second UL channel may differ for each event. In this case, the first UL channel may include the CC / cell ID and event ID.

[0326] The network may determine / identify the event that triggers reporting based on the event ID included in the first UL channel, and perform subsequent actions (e.g., sending to the first DL channel / sending to the second UL channel) based on that determination / identification.

[0327] In this case, the network can identify the event (ID) before the second UL channel is transmitted / received / scheduled, so the event ID does not need to be included in the second UL channel.

[0328] For multiple events (for example, all of them), the payload / size of the second UL channel may be the same. In this case, the first UL channel may include the CC / cell ID but not the event ID.

[0329] The network does not need to be aware of events that are triggered before the second UL channel is transmitted, received, or scheduled.

[0330] In this case, the network may include an event ID in the second UL channel to identify the reported event.

[0331] Figure 16 shows an example of UEIBR operation according to Embodiment 4-2-2. In the example shown in Figure 16, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2.

[0332] In the example shown in Figure 16, an event corresponding to reporting setting #1-0 occurs. At this time, the UE (for example, in mode A) transmits a first UL channel corresponding to the reporting setting / event (in the figure, reporting setting #0 (#1-0)). Next, the NW transmits a first DL channel, considering that it is a report / event triggered at CC#1 based on the information contained in the first UL channel (for example, CC / cell ID). At this time, the UE may or may not include the event ID in the second UL channel scheduled by the first DL channel. The second UL channel may also be transmitted using a different CC (for example, CC#1) than the first UL channel / first DL channel.

[0333] <<Embodiment 4-3>> <<<Embodiment 4-3-1>>> Embodiment 4-3-1 may correspond, for example, to Embodiment 3-3-1 described above.

[0334] A one-to-one correspondence may be established between the [Report Trigger] event and the first UL channel resource. The UE may transmit the first UL channel using the resource corresponding to the event. The NW may determine / identify the triggered event based on the resources of the first UL channel it receives, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0335] The first UL channel may contain at least two bits (multiple bits) of information.

[0336] For example, this information may include the ID of the CC / cell from which the report is triggered.

[0337] (Regardless of the differences in payload / size of the second UL channel for each event,) the event ID does not need to be included in the first UL channel.

[0338] <<<Embodiment 4-3-2>>> Embodiment 4-3-2 may correspond, for example, to Embodiment 3-3-2 described above.

[0339] The correspondence between the event that triggers the report and the first UL channel resource does not need to be configured. The first UL channel resource may be associated with the triggered event according to specific rules that are defined in advance.

[0340] The first UL channel may contain at least two bits (multiple bits) of information.

[0341] This information may include, for example, at least the ID of the CC / cell from which the report is triggered.

[0342] The UE may transmit the first UL channel using resources allocated based on predetermined rules.

[0343] The network may determine / identify the CC that triggers the report based on the CC / cell ID included in the first UL channel, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0344] Furthermore, this information may include the ID of the event that triggers the report (in addition to the CC / cell ID).

[0345] If the first UL channel contains an event ID, the second UL channel does not need to contain an event ID. Conversely, if the first UL channel does not contain an event ID, the second UL channel may contain an event ID.

[0346] Figure 17 shows an example of UEIBR operation according to Embodiment 4-3-2. In the example shown in Figure 17, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2.

[0347] In the example shown in Figure 17, an event corresponding to reporting setting #1-0 occurs. At this time, the UE transmits a first UL channel corresponding to the CC (CC#1 in the figure) (for example, in mode A). Next, the NW transmits a first DL channel, considering that it is a report / event triggered at CC#1 based on the information contained in the first UL channel (e.g., CC / cell ID). At this time, the UE may or may not include the event ID in the second UL channel scheduled by the first DL channel. The second UL channel may also be transmitted using a different CC (for example, CC#1) than the first UL channel / first DL channel.

[0348] <<Embodiment 4-4>> Embodiment 4-4 may correspond, for example, to Embodiment 3-4 described above.

[0349] A common first UL channel resource may be configured for multiple (for example, all) CC / report settings / events (settings).

[0350] The network may determine / identify the triggered CC / reporting settings / events based on the first UL channel it receives, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0351] The first UL channel may contain at least two bits (multiple bits) of information.

[0352] For example, this information may include the ID of the CC / cell from which the report is triggered.

[0353] The network may determine / identify the CC that triggers the report based on the CC / cell ID included in the first UL channel, and perform subsequent actions (e.g., first DL channel transmission / second UL channel transmission) based on that determination / identification.

[0354] Furthermore, this information may include the ID of the event that triggers the report (in addition to the CC / cell ID).

[0355] The payload / size of the second UL channel may differ for each event. In this case, the first UL channel may include the CC / cell ID and event ID.

[0356] The network may determine / identify the event that triggers reporting based on the event ID included in the first UL channel, and perform subsequent actions (e.g., sending to the first DL channel / sending to the second UL channel) based on that determination / identification.

[0357] In this case, the network can identify the event (ID) before the second UL channel is transmitted / received / scheduled, so the event ID does not need to be included in the second UL channel.

[0358] For multiple events (for example, all of them), the payload / size of the second UL channel may be the same. In this case, the first UL channel may include the CC / cell ID but not the event ID.

[0359] The network does not need to be aware of events that are triggered before the second UL channel is transmitted, received, or scheduled.

[0360] In this case, the network may include an event ID in the second UL channel to identify the reported event.

[0361] Figure 18 shows an example of UEIBR operation according to Embodiment 4-4. In the example shown in Figure 18, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2.

[0362] In the example shown in Figure 18, an event corresponding to reporting setting #1-0 occurs. At this time, the UE (for example, in mode A) transmits a first UL channel common to multiple CCs / reporting settings / events. Next, the NW transmits a first DL channel, considering that it is a report / event triggered in CC#1, based on the information contained in the first UL channel (for example, CC / cell ID). At this time, the UE may or may not include the event ID in the second UL channel scheduled by the first DL channel. The second UL channel may also be transmitted using a different CC (for example, CC#1) than the first UL channel / first DL channel.

[0363] According to the fourth embodiment described above, the content of the first and second UL channels can be appropriately determined according to each case, and appropriate UEIB operation can be ensured.

[0364] <Fifth Embodiment> When reports corresponding to multiple reporting settings / events are triggered simultaneously in a single CC, at least one of the following is possible: multiple second UL channel resources are allocated, and the payload / size of the second UL channel (resource) is made different (for example, larger) than when a report corresponding to a single reporting setting / event is triggered.

[0365] In each embodiment of the third and fourth embodiments described above, it is necessary to consider the transmission and reception operations of the first UL channel, first DL channel, and second UL channel, as well as the content of the first UL channel and second UL channel, when reports corresponding to multiple report settings / events are triggered simultaneously in a certain CC.

[0366] Therefore, in the fifth embodiment described below, the details of the content of the first UL channel and the second UL channel in order to ensure the transmission and reception operation of the first UL channel, the first DL channel, and the second UL channel will be explained.

[0367] This embodiment may be applied in combination with the third / fourth embodiments described above, or it may be applied independently of the third / fourth embodiments described above.

[0368] In a given CC, reports corresponding to multiple reporting settings / events may be triggered simultaneously (this may be referred to as Case V below).

[0369] In this disclosure, the simultaneous triggering of reports corresponding to multiple reporting settings / events may mean that multiple events corresponding to one or more reporting settings occur within a particular period, that multiple reports corresponding to one or more reporting settings / event settings are triggered within a particular period, and so on.

[0370] <<Embodiment 5-1>> <<<Embodiment 5-1-1>>> Embodiment 5-1-1 may correspond, for example, to the above embodiments 3-1-1 / 4-1-1.

[0371] Since the network can identify the triggered CC / reporting settings / events (settings) based on the first UL channel resource, the above embodiment 4-1-1 may also be applied in case V.

[0372] In this case, the first UL channel may transmit only one bit of information.

[0373] Furthermore, the second UL channel may include an event ID. This allows the network to identify which of several events corresponds to the reported event.

[0374] <<<Embodiment 5-1-2>>> Embodiment 5-1-2 may correspond, for example, to Embodiments 3-1-2 / 4-1-2 described above.

[0375] If the first UL channel transmits multi-bit information (for example, if the first UL channel contains a CC / cell / event ID), the network can identify / determine the number of CCs / reports / events to be triggered based on the first UL channel.

[0376] In this case, the embodiment 4-1-2 described above may also be applied to the first UL channel in case V.

[0377] Additionally, the second UL channel may include an event ID.

[0378] Figure 19 shows an example of UEIBR operation according to Embodiment 5-1-2. In the example shown in Figure 19, UEIBR is set for UE in CC#0 to #2. Report settings #0-0 to #0-2 are set in CC#0, report settings #1-0 to #1-2 are set in CC#1, and report settings #2-0 to #2-2 are set in CC#2.

[0379] In the example shown in Figure 19, events corresponding to report settings #0-0, #1-0, and #1-1 occur simultaneously (or within a specific period). At this time, the UE transmits a first UL channel corresponding to each report setting (for example, in mode A). The NW then transmits a first DL channel, considering that it is a report corresponding to report setting #0-0 in CC#0, report setting #1-0 in CC#1, and report setting #1-1 in CC#1, based on the information contained in the first UL channel (at this time, the first DL channel corresponding to report setting #0-0 is transmitted in CC#0, and the first DL channels corresponding to report settings #1-0 / #1-1 are transmitted in CC#1).

[0380] In this case, the UE may or may not include the event ID in the second UL channel scheduled by the first DL channel. For example, if one event corresponding to a CC occurs, the event ID does not need to be included in the second UL channel for that CC. Also, for example, if multiple events corresponding to a CC occur, the event IDs may be included in the second UL channel for that CC.

[0381] Although the resource for the first UL channel shown in Figure 19 is shown as a single resource, the first UL channel corresponding to each reporting setting may be transmitted using separate resources (transmission opportunities) or using a common resource (transmission opportunity).

[0382] <<Embodiment 5-2>> <<<Embodiment 5-2-1>>> Embodiment 5-2-1 may correspond, for example, to Embodiments 3-2-1 / 4-2-1 described above.

[0383] If the first UL channel does not contain the triggered reporting setting / event ID, the network cannot identify the number of reporting settings / events triggered in a given CC, and therefore cannot properly process subsequent actions.

[0384] Therefore, in the above embodiment 4-2-1, the first UL channel may transmit information of multiple bits and include at least one of the following: information regarding the number of triggered reporting settings / events, and the ID of the triggered reporting setting / event.

[0385] Information regarding the number of triggered reporting settings / events may be represented by a code point (binary number) corresponding to that number, or by a bitmap format showing the triggered reporting settings / events.

[0386] Additionally, the second UL channel may include an event ID.

[0387] <<<Embodiment 5-2-2>>> Embodiment 5-2-2 may correspond, for example, to Embodiments 3-2-2 / 4-2-2 described above.

[0388] If the first UL channel does not contain the triggered reporting setting / event ID, the network cannot identify the number of reporting settings / events triggered in a given CC, and therefore cannot properly process subsequent actions.

[0389] Therefore, in the above embodiment 4-2-2, the first UL channel may include at least one of the following: information regarding the number of triggered reporting settings / events, and the ID of the triggered reporting setting / event.

[0390] Information regarding the number of triggered reporting settings / events may be represented by a code point (binary number) corresponding to that number, or by a bitmap format showing the triggered reporting settings / events.

[0391] Additionally, the second UL channel may include an event ID.

[0392] <<Embodiment 5-3>> <<<Embodiment 5-3-1>>> Embodiment 5-3-1 may correspond, for example, to the above embodiments 3-3-1 / 4-3-1.

[0393] Since the network can identify the triggered CC / reporting settings / events (settings) based on the first UL channel resource, the above embodiment 4-3-1 may also be applied in case V.

[0394] In this case, the first UL channel may conform to the first UL channel described in Embodiment 4-3-1 above.

[0395] Furthermore, the second UL channel may include an event ID. This allows the network to identify which of several events corresponds to the reported event.

[0396] <<<Embodiment 5-3-2>>> Embodiment 5-3-2 may correspond, for example, to Embodiments 3-3-2 / 4-3-2 described above.

[0397] If the first UL channel does not contain the triggered reporting setting / event ID, the network cannot identify the number of reporting settings / events triggered in a given CC, and therefore cannot properly process subsequent actions.

[0398] Therefore, in the above embodiment 4-3-2, the first UL channel may include at least one of the following: information regarding the number of triggered reporting settings / events, and the ID of the triggered reporting setting / event.

[0399] Information regarding the number of triggered reporting settings / events may be represented by a code point (binary number) corresponding to that number, or by a bitmap format showing the triggered reporting settings / events.

[0400] Additionally, the second UL channel may include an event ID.

[0401] <<Embodiment 5-4>> Embodiment 5-4 may correspond, for example, to Embodiments 3-4 / 4-4 described above.

[0402] If the first UL channel does not contain the triggered reporting setting / event ID, the network cannot identify the number of reporting settings / events triggered in a given CC, and therefore cannot properly process subsequent actions.

[0403] Therefore, in the above embodiment 4-4, the first UL channel may include at least one of the following: information regarding the number of triggered reporting settings / events, and the ID of the triggered reporting setting / event.

[0404] Information regarding the number of triggered reporting settings / events may be represented by a code point (binary number) corresponding to that number, or by a bitmap format showing the triggered reporting settings / events.

[0405] Additionally, the second UL channel may include an event ID.

[0406] According to the fifth embodiment described above, even when reports corresponding to multiple report settings / events are triggered simultaneously in a single CC, the UEIBR operation (transmission and reception operation of the first UL channel / first DL channel / second UL channel) can be properly executed.

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

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

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

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

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

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

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

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

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

[0416] 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 a UEIBR. • Supporting MIMO / mobility Rel. 19 and later. • Supporting a UEIBR using MAC CE / UCI. • Supporting combinations of events. • Total number of beams reported. • Number of beams that meet the conditions. • Supporting a UEIBR using 2-part UCI / 1-part UCI. • Supporting one or more pre-configured resources for a second UL channel for a UEIBR. • Supporting a UEIBR using multiple CCs. • Supporting a UEIBR being configured across multiple CCs.

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

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

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

[0420] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1-1] A terminal having a receiving unit that receives a report setting for beam reporting initiated by a terminal, and a control unit that controls, when beam reporting is set for a plurality of component carriers, the determination of a resource for a first uplink (UL) channel for beam reporting based on a resource identifier (ID) included in the report setting, the reception of a first downlink (DL) channel transmitted based on the first UL channel, and the transmission of a second UL channel for beam reporting based on the first DL channel. [Note 1-2] The terminal according to Note 1-1, wherein the report setting is at least one of a channel status information (CSI) report setting, a CSI report setting relating to lower layer triggered mobility (LTM), and a CSI report setting dedicated to beam reporting. [Appendix 1-3] The terminal according to Appendix 1-1 or Appendix 1-2, wherein the resource of the first UL channel corresponds to at least one of the triggered reporting setting, the triggered component carrier, and the triggered event. [Appendix 1-4] The terminal according to any one of Appendix 1-1 to Appendix 1-3, wherein the information transmitted using the first UL channel includes at least one of the component carrier ID, the reporting setting ID, and the event ID. [Appendix 2-1] A terminal having a receiving unit that receives a reporting setting for beam reporting initiated by a terminal, and a control unit that controls, when beam reporting is set for multiple component carriers, the determination of the resource of the first uplink (UL) channel for beam reporting based on the resource identifier (ID) included in the reporting setting, and the transmission of the second UL channel for beam reporting associated with the first UL channel, wherein no downlink (DL) channel based on the first UL channel is transmitted. [Appendix 2-2] The terminal described in Appendix 2-1, wherein the reporting setting is at least one of the following: a channel status information (CSI) reporting setting, a CSI reporting setting for lower layer triggered mobility (LTM), and a CSI reporting setting specifically for beam reporting.[Appendix 2-3] The resource of the first UL channel is the terminal described in Appendix 2-1 or Appendix 2-2, which corresponds to at least one of the triggered reporting setting, the triggered component carrier, and the triggered event. [Appendix 2-4] The information transmitted using the first UL channel is the terminal described in any of Appendix 2-1 to Appendix 2-3, which includes at least one of the component carrier ID, the reporting setting ID, and the event ID.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0447] The synchronization signal may be, for example, at least one of a primary synchronization signal (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, an SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0448] In the wireless communication system 1, as an uplink reference signal (Uplink Reference Signal (UL-RS)), a sounding reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted. Note that DMRS may also be called a UE-specific reference signal.

[0449] (Base station) FIG. 21 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

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

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

[0452] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission, reception, measurement, etc. using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal and transfer it to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of a communication channel, state management of the base station 10, management of radio resources, etc.

[0453] The transmission / reception 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 transmission / reception unit 120 may 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. described based on the common understanding in the technical field related to the present disclosure.

[0454] The transmission / reception unit 120 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 1211 and the RF unit 122. The reception unit may be composed of the reception processing unit 1212, the RF unit 122, and the measurement unit 123.

[0455] The transmission / reception antenna 130 may 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 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 120 may receive the above-described uplink channel, uplink reference signal, etc.

[0457] The transmission / reception unit 120 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 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.

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

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

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

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

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

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

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

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

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

[0468] The transmitting / receiving unit 120 may transmit a report setting for beam reporting initiated by a terminal. When beam reporting is set up for multiple component carriers, the control unit 110 may control the identification of a first uplink (UL) channel resource for beam reporting transmitted based on a resource identifier (ID) included in the report setting, the transmission of a first downlink (DL) channel based on the first UL channel, and the reception of a second UL channel for beam reporting transmitted based on the first DL channel (first / second embodiment).

[0469] The transmitting / receiving unit 120 may transmit a report setting for beam reporting initiated by a terminal. The control unit 110 may, when beam reporting is configured for multiple component carriers, control the identification of a first uplink (UL) channel resource for beam reporting transmitted based on a resource identifier (ID) included in the report setting, and the reception of a second UL channel for beam reporting associated with the first UL channel. A downlink (DL) channel based on the first UL channel does not need to be transmitted (first / second embodiment).

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

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

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

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

[0474] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

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

[0481] Note that whether to apply DFT processing may also be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is enabled, the transmission unit 220 (transmission processing unit 2211) may perform DFT processing as the above-mentioned transmission processing to transmit the channel using the DFT-s-OFDM waveform. Otherwise, DFT processing may not be performed as the above-mentioned transmission processing.

[0482] The transmission unit 220 (RF unit 222) may perform modulation to the radio frequency band, filter processing, amplification, etc. on the baseband signal, and transmit the signal in the radio frequency band via the transmission and reception antenna 230.

[0483] On the other hand, the transmission unit 220 (RF unit 222) may perform amplification, filter processing, demodulation to the baseband signal, etc. on the signal in the radio frequency band received by the transmission and reception antenna 230.

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

[0485] The transmission unit 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), reception 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.

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

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

[0488] The transmitting / receiving unit 220 may receive a report setting for beam reporting initiated by a terminal. When beam reporting is set up for multiple component carriers, the control unit 210 may control the determination of a resource for a first uplink (UL) channel for beam reporting based on a resource identifier (ID) included in the report setting, the reception of a first downlink (DL) channel transmitted based on the first UL channel, and the transmission of a second UL channel for beam reporting based on the first DL channel (first / second embodiment).

[0489] The transmitting / receiving unit 220 may receive a report setting for beam reporting initiated by a terminal. When beam reporting is set up for multiple component carriers, the control unit 210 may control the determination of the resource for the first uplink (UL) channel for beam reporting based on the resource identifier (ID) included in the report setting, and the transmission of the second UL channel for beam reporting associated with the first UL channel. The downlink (DL) channel based on the first UL channel does not need to be transmitted (first / second embodiment).

[0490] The reporting setting may be at least one of the following: a channel status information (CSI) reporting setting, a CSI reporting setting for lower layer triggered mobility (LTM), and a CSI reporting setting specifically for beam reporting (first embodiment).

[0491] The resource of the first UL channel may correspond to at least one of a triggered reporting setting, a triggered component carrier, and a triggered event (third embodiment).

[0492] The information transmitted using the first UL channel may include at least one of a component carrier ID, a reporting setting ID, and an event ID (fourth embodiment).

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

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

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

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

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

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

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

[0500] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

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

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

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

[0505] Furthermore, each device, such as the processor 1001 and 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0592] This application is based on Japanese Patent Application No. 2024-174598, filed on October 3, 2024. All of its contents are included herein.

Claims

1. A terminal having a receiving unit that receives a reporting setting for beam reporting initiated by a terminal, and a control unit that, when beam reporting is set for multiple component carriers, controls the determination of a resource for a first uplink (UL) channel for beam reporting based on a resource identifier (ID) included in the reporting setting, and the transmission of a second UL channel for beam reporting associated with the first UL channel, wherein no downlink (DL) channel based on the first UL channel is transmitted.

2. The terminal according to claim 1, wherein the reporting setting is at least one of a channel status information (CSI) reporting setting, a CSI reporting setting for lower layer triggered mobility (LTM), and a CSI reporting setting specifically for beam reporting.

3. The terminal according to claim 1, wherein the resource of the first UL channel corresponds to at least one of a triggered reporting setting, a triggered component carrier, and a triggered event.

4. The terminal according to claim 1, wherein the information transmitted using the first UL channel includes at least one of a component carrier ID, a reporting setting ID, and an event ID.

5. A wireless communication method for a terminal, comprising the steps of: receiving a reporting setting for beam reporting initiated by a terminal; and, if beam reporting is set for multiple component carriers, controlling the determination of a resource for a first uplink (UL) channel for beam reporting based on a resource identifier (ID) included in the reporting setting, and the transmission of a second UL channel for beam reporting associated with the first UL channel, wherein no downlink (DL) channel based on the first UL channel is transmitted.

6. A base station having a transmitting unit that transmits a reporting setting for beam reporting initiated by a terminal, and a control unit that, when beam reporting is set for multiple component carriers, controls the identification of a first uplink (UL) channel resource for reporting transmitted based on a resource identifier (ID) included in the reporting setting, and the reception of a second UL channel for beam reporting associated with the first UL channel, wherein no downlink (DL) channel based on the first UL channel is transmitted.

Images