Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives one or a plurality of report configurations, the one report configuration being associated with one or a plurality of events pertaining to a beam report initiated by the terminal; and a control unit that performs control on the basis of the one or the plurality of report configurations and occurrences of the plurality of events such that the beam report which includes an instruction pertaining to the events or does not include the instruction pertaining to the events is transmitted. According to the one aspect of the present disclosure, communication quality and throughput can be improved.

Description

Terminal, wireless communication method, and base station

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) 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 (e.g., NR, Rel. 19 and later), support for event-based beam reporting (or possibly called event-triggered beam reporting / UE-initiated Beam Report (UEIBR)) initiated by a terminal (user terminal, user equipment (UE)) is being considered.

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

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

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

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives one or more reporting settings, one of which is associated with one or more events relating to a beam report initiated by the terminal, and a control unit that controls the transmission of the beam report, which includes or does not include instructions relating to the events, based on the one or more reporting settings and the occurrence of the events.

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

[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of a report format for case 2A. Figure 3 shows an example of a report format for case 2B. Figure 4 shows an example of a report format for case 2C. Figure 5 shows an example of zero padding for option 3A of the third embodiment. Figure 6 shows an example of zero padding for option 3B of the third embodiment. Figure 7 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 8 shows an example of a base station configuration according to one embodiment. Figure 9 shows an example of a user terminal configuration according to one embodiment. Figure 10 shows an example of a hardware configuration of a base station and user terminal according to one embodiment. Figure 11 shows an example of a vehicle according to one embodiment.

[0012] (L1 / L2 Inter-Cell Mobility) A UE may perform UL transmissions to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 procedures are possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may be simply referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive.

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

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

[0015] In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the UE's assumption of the serving cell) remains unchanged. The UE sets higher-layer parameters related to the PCI of the non-serving cell from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.

[0016] Figure 1A shows an example of UE movement in Rel. 17. It assumes a UE moving from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support L1 / L2 switching of serving cells.

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

[0018] <Scenario 2> In Scenario 2, L1 / L2 cell mobility is applied. With L1 / L2 cell mobility, serving cell changes can be made using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with additional cells are possible without handover. Since handover requires RRC reconnection and other factors, resulting in a period of no data communication, applying L1 / L2 cell mobility that does not require handover allows data communication to continue even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In Scenario 2, for example, the following procedure is performed.

[0019] (1) The UE receives the SSB configuration of a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement on the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration of the cell with the different PCI (serving cell configuration) by upper layer signaling (e.g., RRC). In other words, a pre-configuration regarding the serving cell change may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI state of the cell with the different PCI may be activated by L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] Events related to the UEIBR for MIMO may be broadly categorized into the following event types: • Event 1: The quality of the current beam falls below a certain threshold. • Event 2: The quality of at least one new beam (e.g., L1-RSRP) is better than a certain threshold compared to the quality of the current beam. • Event 3: The quality of a new beam is better than a certain threshold. • Event 4: The quality of the current beam falls below a first threshold, and the quality of at least one new beam is better than a second threshold. • Event 5: The absolute difference between the quality of the current beam and the quality of at least one new beam falls below a certain threshold. • Event 6: The current beam is no longer included in the best K beams (more than 1: K > 1) (of the beams set up for measurement / reporting). - Event 7: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the RS derived from the Q-th (Q may be M; Q or M is 1 or greater; Q or M may be set in the RRC (based on UE capability reporting)) quality good activated (active) TCI state. - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) improves by a threshold beyond the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) improves by a threshold beyond the set reference RS (which may be SSB / CSI-RS).

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

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

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

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

[0042] For example, for a 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 for TCI states (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 setting subset of the list of TCI states set by RRC (set TCI states).

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

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

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

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

[0047] If only TRS is set as the QCL-RS for the indicated TCI state, a reference signal different from the TRS (e.g., the RS corresponding to the TRS) may be selected for measuring / reporting the RS of the current beam.

[0048] For the current beam RS measurement 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 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: TRS is further supported as the measured RS for the current beam to determine the L1-RSRP. • Processing Option 3: An additional scheme is introduced. The RS for the current beam is explicitly set / indicated by the RRC or MAC CE. • Processing Option 4: No further extensions are made.

[0050] Explicit RS settings for measuring new beams in Event 2 may be configured in a single RS resource set associated with the CSI reporting settings.

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

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

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

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

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

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

[0057] Step 2: The UE detects a DCI format (which may also be called the first DL signal) indicating the second UL channel resource.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0073] In mode B, a one-bit instruction on at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel will transmit a beam report.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0102] (Analysis) In the above-mentioned UEIBR, a field indicating the CSI reporting setting (CSI reporting setting indicator field) may be included in the UEIBR to identify which CSI reporting setting corresponds to the report.

[0103] Furthermore, it is being considered that UEIBR may include information about events (e.g., event type / event setting ID, etc.).

[0104] A second UL channel may contain at least one report / UEIBR.

[0105] In this case, the report payload size may be the largest payload size among the report payload sizes corresponding to the associated CSI reporting settings (for the same first UL channel resource).

[0106] If the payload size of the report to be sent is less than the maximum payload size, zero-padding may be performed.

[0107] The question is whether multiple reports / UEIBRs can be included in a single second UL channel.

[0108] The introduction of parameters for at least one of the following is being considered as RRC parameters for events in the UEIBR: • Event type (eventType-r19). • Event threshold (eventThreshold-r19). • Event threshold for event 1 (eventThresholdEvent1-r19). • Event detection time window length (eventDetectionTimeWindowLength-r19). • Event instance count (eventInstanceCount-r19). • Q value for event 7 (valueOfQ-r19).

[0109] In cases where multiple events are configured for UE / UEIBR (which may also be called a multi-event case), it is being considered that the RRC parameters for those events be placed under / directly under the CSI reporting settings (which may also simply be called reporting settings).

[0110] For example, the list of CSI reporting configurations (CSI-ReportConfig) included within the CSI measurement configuration (CSI-MeasConfig) may include at least one of the existing CSI reporting configurations and the CSI reporting configuration for the UEIBR.

[0111] Within a single CSI reporting configuration, RRC parameters for a single event (e.g., a single event type, a single event threshold, a single time window length, etc.) may be configured.

[0112] In other words, different CSI reporting settings may be used for different event types, and different CSI reporting settings may be used for different parameters (e.g., threshold / time window length) for the same event type.

[0113] In a multi-event case, the following configuration options 1 to 4 are assumed for setting RRC parameters related to an event: • Configuration Option 1: Some / all of the RRC parameters related to the event are placed / defined directly under the CSI reporting settings. • Configuration Option 2: Some / all of the RRC parameters related to the event are placed / defined directly under a new information element (e.g., event configuration (eventConfig)), and this new information element is placed / defined directly under the CSI reporting settings. • Configuration Option 3: Some / all of the RRC parameters related to the event are placed / defined directly under a new information element (e.g., event configuration (eventConfig)), and a parameter indicating the event type is placed / defined directly under the CSI reporting settings. This new information element is defined for each event type and identified by the parameter indicating the event type. - Configuration Option 4: Some / all of the RRC parameters related to the event, and an ID (e.g., event configuration ID (eventConfigID)) to identify the new information element (e.g., event configuration (eventConfig)), are placed / defined directly under the new information element, and the ID is placed / defined directly under the CSI reporting settings. The new information element is identified by the ID.

[0114] In configuration option 1, one CSI reporting setting may be associated with one event type. In configuration options 2 / 3 / 4, one CSI reporting setting may be associated with one or more event types.

[0115] In setting option 2, the new information element does not need to include an ID to identify the new information element. A single CSI reporting setting may contain one or more new information elements.

[0116] In setting option 2, the new information element may include an ID to identify the new information element. A single CSI reporting setting may include one or more new information elements with different setting values ​​that correspond to the same event type.

[0117] In setting option 3, it is not necessary to set multiple new information elements corresponding to the same event type.

[0118] In setting option 4, a single CSI reporting setting may include an ID to identify one or more new information elements.

[0119] In setting option 4, one CSI reporting setting may correspond to one or more new information elements with different setting values ​​that correspond to the same event type.

[0120] Multiple scenarios are possible regarding the association between the first UL channel resource and reporting settings, and the association between reporting settings and event types.

[0121] For example, in the case of a UEIBR using one CC (which may also be called a single CC case), at least one of the following cases S1 to S4 is assumed: • Case S1: One first UL channel resource is associated with one or more CSI reporting settings. One CSI reporting setting associated with multiple (e.g., all) first UL channel resources is associated with one event type. • Case S2: One first UL channel resource is associated with one or more CSI reporting settings. One CSI reporting setting associated with one first UL channel resource is associated with one or more event types. • Case S3: One first UL channel resource is associated with one CSI reporting setting. One CSI reporting setting associated with one first UL channel resource is associated with one event type. • Case S4: One first UL channel resource is associated with one CSI reporting setting. One CSI reporting setting associated with one primary UL channel resource is associated with one or more event types.

[0122] Case S1 can be further divided into the following cases S1-1 / S1-2 / S1-3: • Case S1-1: Multiple (e.g., all) first UL channel resources are associated with CSI reporting settings of the same event type. • Case S1-2: One first UL channel resource is associated with CSI reporting settings of the same event type. • Case S1-3: One first UL channel resource may be associated with CSI reporting settings of different event types.

[0123] Case S3 can be further divided into the following cases S3-1 / S3-2: • Case S3-1: Multiple (e.g., all) first UL channel resources are associated with CSI reporting settings of the same event type. • Case S3-2: Different first UL channel resources may be associated with CSI reporting settings of different event types (i.e., the event type of a CSI reporting setting associated with one first UL channel resource may be different from the event type of a CSI reporting setting associated with another first UL channel resource).

[0124] For example, in the case of a UEIBR using multiple CCs (which may also be called a multi-CC case), at least one of the following cases M1 to M4 is assumed: • Case M1: One primary UL channel resource is associated with one or more CSI reporting settings. One CSI reporting setting associated with multiple (e.g., all) primary UL channel resources is associated with one event type. • Case M2: One primary UL channel resource is associated with one or more CSI reporting settings. One CSI reporting setting associated with one primary UL channel resource is associated with one or more event types. • Case M3: One primary UL channel resource is associated with one CSI reporting setting. One CSI reporting setting associated with one primary UL channel resource is associated with one event type. • Case M4: One primary UL channel resource is associated with one CSI reporting setting. One CSI reporting setting associated with one primary UL channel resource is associated with one or more event types.

[0125] In case M1, the following options 1-1 / 1-2 / 2-1 / 2-2 / 2-3 / 3-1 / 3-2 may apply: • Option 1-1: Only one CSI reporting setting configured in one CC is associated with one primary UL channel resource. • Option 1-2: Multiple / different CSI reporting settings configured in different CCs may be associated with one primary UL channel resource. • Option 2-1: The event type related to the configured CSI reporting setting is the same across multiple CCs. Multiple (e.g., all) primary UL channel resources are associated with CSI reporting settings of the same event type. • Option 2-2: The event type related to the configured CSI reporting setting is the same across one of the multiple CCs. The event types related to different CSI reporting settings configured in different CCs may be different (or the same). - Option 2-3: For one of the multiple CCs that are configured, the event types associated with the configured CSI reporting settings may be different (or the same). - Option 3-1: A single first UL channel resource is associated with CSI reporting settings of the same event type. - Option 3-2: A single first UL channel resource may be associated with CSI reporting settings of different event types.

[0126] Furthermore, at least two of options 1-1 / 1-2 / 2-1 / 2-2 / 2-3 / 3-1 / 3-2 may be applied in combination. For example, either option 1-1 or 1-2 may be applied in combination with any of options 2-1 to 2-3 and either option 3-1 or 3-2.

[0127] Case M2 can be further divided into the following cases M2-1 / M2-2: • Case M2-1: One first UL channel resource is associated with a CSI reporting setting configured for one CC. • Case M2-2: One first UL channel resource may be associated with CSI reporting settings configured for different (multiple) CCs.

[0128] Case M3 is further divided into the following cases M3-1 / M3-2 / M3-3: • Case M3-1: In multiple (e.g., all) CCs that are configured, the event type related to the configured CSI reporting settings is the same. Multiple (e.g., all) first UL channel resources are associated with CSI reporting settings of the same event type. • Case M3-2: In one of the multiple CCs that are configured, the event type related to the configured CSI reporting settings is the same. The event types related to different CSI reporting settings configured for different CCs may be different (or the same). • Case M3-3: For one of the multiple CCs that are configured, the event types related to the configured CSI reporting settings may be different (or the same).

[0129] In the case of Mode A (or when Mode A is set by RRC signaling), any of the above-mentioned cases relating to single CC / multi CC cases may apply.

[0130] In the case of Mode B (or when Mode B is set by RRC signaling), a specific case from the above-mentioned cases relating to single CC / multi CC cases may apply.

[0131] The specific case in question may be, for example, a case excluding at least one of the options 1-2 of case M1 and case M2-2.

[0132] Furthermore, at least one of the single CC cases / multi-CC cases described above (or a combination of multiple cases) may be defined as a multi-event case.

[0133] <Analysis 1> The UEIBR is transmitted using the second UL channel. The UEIBR / second UL channel may contain instructions to identify the corresponding CSI reporting settings.

[0134] For the same first UL channel resource, one or more CSI reporting settings configured for the same CC are associated. Therefore, since the CC to which the CSI reporting settings are configured can be identified based on the first UL channel resource, the second UL channel / UEIBR does not need to include information to identify the CC.

[0135] Depending on the settings of the first UL channel resource / CSI reporting settings / event type / event settings, the UEIBR / second UL channel may contain instructions about the event (e.g., event type / event setting ID). This allows the network to determine which event occurred based on the reported UEIBR.

[0136] In particular, for multi-event cases, such as cases S2 / S4 / M2 / M4 mentioned above, it is necessary to consider including instructions regarding the event within the UEIBR / second UL channel.

[0137] On the other hand, from the perspective of signaling overhead, it is preferable to be able to choose / decide whether or not to include instructions regarding the event in question. However, this method has not been sufficiently considered (Problem 1).

[0138] <Analysis 2> As described above, one primary UL channel resource may be associated with one or more CSI reporting settings.

[0139] Additionally, a single CSI reporting setting may be associated with a single event (for example, an event type and settings related to that event).

[0140] If multiple CSI reporting settings are associated with a single first UL channel resource, the report (e.g., UEIBR / second UL channel) may include instructions to identify the corresponding CSI reporting setting.

[0141] The payload size of a second UL channel corresponding to a first UL channel resource may be the largest payload size among the reports corresponding to multiple (e.g., all) CSI reporting settings associated with that first UL channel resource. In this case, unused fields in the report may be zero-padded to match the largest payload size.

[0142] The number of reported beams for each CSI reporting setting for UEIBR (e.g., nrofReportedRS-UEIBR-r19) may be the same or different.

[0143] Multiple CSI reporting settings with different event types may be associated with a single first UL channel resource.

[0144] The payload size of the second UL channel corresponding to one first UL channel resource is uniquely determined. Therefore, the network can receive the second UL channel without blinding.

[0145] On the other hand, if there is a large difference in payload size between the second UL channels corresponding to each of the multiple CSI reporting settings associated with a single first UL channel resource, the number of bits to be zero-padding becomes excessive. This is undesirable from the standpoint of signaling overhead, and it is desirable to resolve this.

[0146] However, the details of this method have not been sufficiently examined (Issue 2).

[0147] <Analysis 3> The details of the operational rules for zero padding and the position / arrangement of fields in the report, as described in Analysis 2, have not been sufficiently examined (Issue 3).

[0148] In this case, the network may not be able to accurately determine or interpret the location, arrangement, or delimiter of information fields within the received report.

[0149] If the detailed examination of the above-mentioned issues 1 to 3 is insufficient, it may not be possible to properly implement UEIBR, and low-latency communication that takes advantage of the beam reporting benefits may not be achieved, potentially leading to a suppression of improvements in communication quality / throughput.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0191] In this disclosure, “all” may mean “all that are set for the UE.”

[0192] In this disclosure, new information elements, event types (settings), event settings, combinations of event types (settings), and combinations of event settings, etc., may be interpreted interchangeably.

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

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

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

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

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

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

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

[0200] In this disclosure, “a report contains a beam” may mean that the report contains information about the beam (e.g., the RS ID corresponding to the beam and information about at least one of the measurement results of the RS). In this disclosure, the number of reported beams may be the same as the number of CRI / SSBRI fields included in one report.

[0201] The following embodiments will be described primarily using events 1, 2, and 7 as examples, but the types of events are not limited to these. Events 1, 2, and 7 may be applied without limiting the type of event, such as the first event, the second event, and the third event, respectively, or they may be substituted for any of the above events.

[0202] Furthermore, each embodiment of this disclosure (the first to third embodiments) may be applied even if there are restrictions on the number of reports included in the second UL channel.

[0203] For example, the constraint may be that there is only one report included in a single second UL channel.

[0204] For example, the constraint may be that the number of reports included in a single second UL channel is one or more specific numbers.

[0205] For example, the constraint may include multiple (e.g., all) reports from multiple (e.g., all) CSI reporting settings associated with the first UL channel for transmitting on the second UL channel.

[0206] The second and third embodiments described below may apply to cases where multiple CSI reporting settings associated with one first UL channel resource are set to the same CC, or they may apply to cases where multiple CSI reporting settings associated with one first UL channel resource are set to different CCs.

[0207] <First Embodiment> The first embodiment relates to a solution to the above problem 1.

[0208] In a multi-event case, if only cases S1 / S3 / M1 / M3 apply / are included, the second UL channel / UEIBR does not need to contain any instructions regarding the event.

[0209] In a multi-event case, if cases S2 / S4 / M2 / M4 apply / are included, the second UL channel / UEIBR may contain instructions regarding the events.

[0210] Regarding whether or not an event instruction is included in the second UL channel / UEIBR, the following options 1-1 / 1-2 / 1-3 may apply: • Option 1-1: The inclusion of the instruction is consistent across multiple (e.g., all) CSI reporting settings in the UEIBR. • Option 1-2: The inclusion of the instruction is consistent across multiple (e.g., all) CSI reporting settings associated with the same first UL channel resource in the UEIBR. • Option 1-3: There is no consistency across multiple UEIBRs (for example, if multiple event types / event settings are associated with a CSI reporting setting, the event instruction may be included in the UEIBR; otherwise, the event instruction may not be included in the UEIBR).

[0211] In option 1-1, any UEIBR may use a reporting format that includes an instruction field for the (unified) event. The UE / NW may assume that such a reporting format will be used.

[0212] The reporting format may be specified in advance in the specifications.

[0213] In option 1-2, the following options 1-2-1 / 1-2-2 / 1-2-3 may apply: Option 1-2-1: Any UEIBR relating to multiple (e.g., all) CSI reporting settings associated with the same first UL channel resource may use a reporting format that includes an indicator field for (unified) events. The UE / NW may assume that such a reporting format will be used. Option 1-2-2: Any UEIBR relating to multiple (e.g., all) CSI reporting settings associated with the same first UL channel resource may be configured / indicated using RRC signaling / MAC CE / DCI whether a reporting format that includes an indicator field for (unified) events is used, or whether a reporting format that does not include such an indicator field is used. Option 1-2-3: Based on the first UL channel resource / CSI reporting settings / event type / event settings and specific conditions, it may be determined (e.g., implicitly calculated) whether a reporting format that includes an indicator field for the event (which will be unified) or a reporting format that does not include such indicator field will be used.

[0214] These specific conditions may be defined in the specifications beforehand.

[0215] The specific conditions may, for example, be conditions relating to at least two associations: a first UL channel (resource), CSI reporting settings, and event type.

[0216] For example, the specific condition may be that multiple different event types are set (simultaneously) for a single CSI reporting setting associated with a single first UL channel resource.

[0217] If the specific conditions are met, the UE may use a reporting format that includes an event-related instruction field for the UEIBR transmitted using the second UL channel corresponding to the first UL channel relating to the specific conditions.

[0218] If the specific conditions are not met, the UE may use a reporting format that does not include an event-related instruction field for the UEIBR transmitted using the second UL channel corresponding to the first UL channel relating to the specific conditions.

[0219] In the above options 1-3, the UE may apply the largest payload among the multiple (e.g., all) reporting settings of the UEIBR payload.

[0220] In the above options 1-3, the UE may apply the largest payload among the multiple (e.g., all) reporting settings associated with the same first UL channel resource to the UEIBR payload.

[0221] In the above options 1-3, if a reporting format is used that does not include an instruction field for the event, the UE may zero-padding the field to reach the maximum payload.

[0222] In any option, the number of bits in the event instruction field is the number of event types / event settings set in the CSI reporting settings (e.g., N). Ｅｖｅｎｔ This may be determined based on the ReportConfig.

[0223] The number of bits is, for example, Ceil(log ２ (N Ｅｖｅｎｔ It may also be ReportConfig). In this disclosure, Ceil(X) may mean the output of X due to the ceiling function.

[0224] For example, if the number of event types / event settings configured in the CSI reporting settings is 3, the number of bits may be 2.

[0225] The instruction field may indicate the type of event to be reported. For example, if the number of bits is two, the instruction field with a first value (e.g., "01") may correspond to an instruction for event 1, the instruction field with a second value (e.g., "10") may correspond to an instruction for event 2, and the instruction field with a third value (e.g., "11") may correspond to an instruction for event 7.

[0226] According to the first embodiment described above, it is possible to contribute to solving the above problem 1.

[0227] <Second Embodiment> The second embodiment relates to a solution to the above problem 2.

[0228] The indication of whether the CRI / SSBRI meets the event conditions, and the indication of whether each reported beam meets the event conditions, may indicate whether the CRI / SSBRI, the corresponding measurement result (e.g., L1-RSRP), and the corresponding reported beam meet the event conditions.

[0229] The indications for whether the CRI / SSBRI meets the event criteria, and the indications for whether each reporting beam meets the event criteria (these indications may hereafter be simply referred to as "the indications"), may be represented by a specific number of bits (e.g., 1 bit).

[0230] The instructions for each reporting beam may be placed in a specific order within the report.

[0231] For example, the instructions may be arranged in the same order as CRI / SSBRI / measurement results.

[0232] For example, the instructions may be arranged in an order independent of the CRI / SSBRI / immediate result order.

[0233] For example, the instructions may be arranged in ascending / descending order for the CRI / SSBRI of the corresponding reporting beam.

[0234] The total number of bits for the instruction included in the report may be N* (a specific number of bits) if the number of reported beams is N.

[0235] The field indicating the TCI status code point included in the report may indicate the code point of a specific TCI status among the active TCI states.

[0236] The specific TCI state may be at least one of the following (where M may be the number of active TCI states): • M+1-Q poor quality TCI states (the first M+1-Q poor quality TCI states). • Q-1 good quality TCI states (the first Q-1 good quality TCI states). • X poor quality TCI states (the first X poor quality TCI states; X may be between 1 and M, and may be set using RRC signaling / MAC CE). • X good quality TCI states (the first X good quality TCI states; X may be between 1 and M, and may be set using RRC signaling / MAC CE).

[0237] Here, X may be a number based on Q.

[0238] The fields indicating the TCI status code points may be placed in a specific order within the report.

[0239] For example, the fields indicating the TCI status code points may be arranged in ascending or descending order of quality.

[0240] For example, the fields indicating the TCI status code points may be arranged in ascending or descending order of the TCI status code points.

[0241] The instruction field for one CSI reporting setting included in the report may indicate which CSI reporting setting the report pertains to, when CSI reporting settings associated with the same first UL channel resource are ordered in ascending order by their corresponding CSI reporting setting ID.

[0242] The number of bits in the instruction field of the CSI reporting setting is equal to the number of CSI reporting settings associated with the same first UL channel resource (for example, N). ＣＳＩＣｏｎｆｉｇ ) may be determined based on the following.

[0243] For example, the number of bits may be Ceil(log ２ (N ＣＳＩＣｏｎｆｉｇ )).

[0244] Cases where a difference in payload size occurs among multiple UEIBRs may be the following cases 2A / 2B / 2C: ・Case 2A: One first UL channel resource is associated (simultaneously) with CSI reporting configurations for different event types (e.g., events 1, 2, and 7). ・Case 2B: For multiple CSI reporting configurations associated with one first UL channel resource, the number of reporting beams (e.g., nrofReportedRS-UEIBR-r19) is configured to different values. ・Case 2C: For multiple CSI reporting configurations associated with one first UL channel resource, the number of RSs included in the RS resource set for new beams (K ＲＳ Ｓ , the RS may be CSI-RS or SSB), or the value of Ceil(log ２ (K ＲＳ Ｓ )) (that is, the number of bits of the reported CRI / SSBRI field) is configured / specified to different values.

[0245] In case 2A, for example, the reports related to events 2 and 7 may include an indication field indicating whether each reported beam satisfies the event condition, and the report related to event 1 may not include the indication field.

[0246] In case 2A, for example, the report related to event 7 may include a field indicating the code point of the TCI state, and the reports related to events 2 and 1 may not include the field.

[0247] Figure 2 is a diagram showing an example of the reporting format according to case 2A. In the example shown in Figure 2, for one first UL channel (PUCCH), the CSI reporting configuration related to event 1, the CSI reporting configuration related to event 2, and the reporting configuration related to event 7 are associated. In the example shown in Figure 2, the CRI / SSBRI field is Ceil(log ２ (K ＲＳＳ )) may be represented by bits, and the instruction field of the CSI reporting settings is Ceil(log ２ (N ＣＳＩＣｏｎｆｉｇ )) It may also be represented in bits (the same applies to subsequent drawings).

[0248] At this time, differences in the payload size of reports will occur for each event type / CSI reporting setting (zero padding will be necessary).

[0249] Figure 3 shows an example of a reporting format for Case 2B. In the example shown in Figure 3, multiple CSI reporting settings related to Event 2 are associated with one first UL channel (PUCCH), and the number of reporting beams differs for each reporting setting (Figure 3 shows cases where the number of reporting beams is 2, N1, and N2 (N2 > N1)). In this case, there is a difference in the size of the report payload for each CSI reporting setting (zero padding is required).

[0250] Figure 4 shows an example of a reporting format for Case 2C. In the example shown in Figure 4, the CSI reporting settings for Event 1, Event 2, and Event 7 are associated with one first UL channel (PUCCH), and each reporting setting has Ceil(log) ２ (K ＲＳ Ｓ )) are different. In this case, there will be a difference in the size of the report payload for each event type / CSI reporting setting (zero padding will be necessary).

[0251] Thus, if at least one of cases 2A through 2C is met, a difference in payloads between multiple CSI reporting settings / UEIBRs associated with a single first UL channel may occur. Furthermore, if multiple cases from 2A through 2C are met in combination, the difference in payload size between UEIBRs increases.

[0252] The UE / NW may assume the association between the first UL channel resource and the CSI reporting settings according to the following embodiments 2-1 / 2-2 / 2-3.

[0253] <<Embodiment 2-1>> <<<Option 2-1-1>>> The UE / NW may assume that one first UL channel resource is associated with CSI reporting settings [only] that correspond to a specific event type / event setting.

[0254] In other words, UE / NW may assume that the first UL channel resource referenced by the first UL channel resource configuration (e.g., firstPUCCHResourceConfig-UEIBR-r19) configured for a CSI reporting configuration corresponding to a specific event type / event configuration is different from the first UL channel resource referenced by the first UL channel resource configuration configured for a CSI reporting configuration corresponding to a different event type / event configuration, or for a configuration that does not correspond to that particular event type / event configuration.

[0255] <<<Option 2-1-2>>> Multiple CSI reporting settings may be associated with a single first UL channel resource, each corresponding to a different event type / event setting, or to an event type / event setting other than a specific event type / event setting.

[0256] In this case, the UE / NW may assume / perform an action relating to at least one of the following options 2-1-2-1 to 2-1-2-4: • Option 2-1-2-1: Only the CSI reporting settings associated with a single first UL channel resource that correspond to a specific event type (or a combination of specific event types) are enabled, and all other CSI reporting settings are disabled. • Option 2-1-2-2: Multiple (e.g., all) CSI reporting settings are enabled. • Option 2-1-2-3: Multiple (e.g., all) CSI reporting settings are disabled. • Option 2-1-2-4: The UE performs an action based on its implementation.

[0257] For option 2-1-2-1, for example, the specific event type may be at least one of events 1, 2, and 7. The specific event type may be defined in advance in the specifications, set / indicated using RRC signaling / MAC CE / DCI, or determined according to UE capability reporting.

[0258] For option 2-1-2-1, for example, a specific combination of event types may be at least two of events 1, 2, and 7. This specific combination of event types may be specified in advance, configured / instructed using RRC signaling / MAC CE / DCI, or determined according to UE capability reporting.

[0259] UE / NW may apply the above options / specific events / specific event combinations separately for each R from Case A onwards.

[0260] - When a single first UL channel resource is associated with both a CSI reporting setting for Event 1 and a CSI reporting setting for Event 2 (simultaneously): - Case A: The report for Event 2 includes an indicator field indicating whether each reporting beam satisfies the event conditions, while the report for Event 1 does not include such an indicator field. - Case B: Both the report for Event 2 and the report for Event 1 include an indicator field indicating whether each reporting beam satisfies the event conditions.

[0261] - When a single first UL channel resource is associated with both a CSI reporting setting for event 2 and a CSI reporting setting for event 7 (simultaneously), and the report for event 2 includes an indicator field indicating whether each reporting beam satisfies the event conditions, but the report for event 7 does not include such an indicator field: - Case C: The report for event 7 (only) includes a field indicating the TCI status code point. - Case D: The report for event 7 does not include a field indicating the TCI status code point.

[0262] - When a single first UL channel resource is associated with both a CSI reporting setting for event 2 and a CSI reporting setting for event 7 (simultaneously), and the reports for event 2 and event 7 include an indicator field that shows whether each reporting beam satisfies the event conditions: - Case E: The report for event 7 (only) includes a field indicating the TCI status code point. - Case F: The report for event 7 does not include a field indicating the TCI status code point.

[0263] - When a single first UL channel resource is associated with both a CSI reporting setting for event 1 and a CSI reporting setting for event 7 (simultaneously), and the report for event 7 includes an indicator field showing whether each reporting beam satisfies the event conditions, while the report for event 1 does not include such an indicator field: - Case G: The report for event 7 (only) includes a field indicating the TCI status code point. - Case H: The report for event 7 does not include a field indicating the TCI status code point.

[0264] - When a single first UL channel resource is associated with both a CSI reporting setting for event 1 and a CSI reporting setting for event 7 (simultaneously), and the reports for event 1 and event 7 include an indicator field that shows whether each reporting beam satisfies the event conditions: - Case I: The report for event 7 (only) includes a field indicating the TCI status code point. - Case J: The report for event 7 does not include a field indicating the TCI status code point.

[0265] - When a single first UL channel resource is associated with CSI reporting settings for Event 1, CSI reporting settings for Event 2, and CSI reporting settings for Event 7 (simultaneously), and the report for Event 2 (only) includes an indicator field showing whether the reporting beam satisfies the event conditions, while the reports for Event 1 and Event 7 do not include such an indicator field: - Case K: The report for Event 7 (only) includes a field indicating the TCI status code point. - Case L: The report for Event 7 does not include a field indicating the TCI status code point.

[0266] - When a single first UL channel resource is associated with CSI reporting settings for Event 1, CSI reporting settings for Event 2, and CSI reporting settings for Event 7 (simultaneously), and the reports for Event 2 and Event 7 include an indicator field that shows whether the reporting beam satisfies the event conditions, but the report for Event 1 does not include such an indicator field: - Case M: The report for Event 7 (only) includes a field that shows the TCI status code point. - Case N: The report for Event 7 does not include a field that shows the TCI status code point.

[0267] - When a single first UL channel resource is associated with (simultaneously) CSI reporting settings for Event 1, CSI reporting settings for Event 2, and CSI reporting settings for Event 7, and the reports for Event 2 and Event 1 include an indicator field that shows whether the reporting beam satisfies the event conditions, but the report for Event 7 does not include such an indicator field: - Case O: The report for Event 7 (only) includes a field that indicates the TCI status code point. - Case P: The report for Event 7 does not include a field that indicates the TCI status code point.

[0268] - When a single first UL channel resource is associated with CSI reporting settings for Event 1, CSI reporting settings for Event 2, and CSI reporting settings for Event 7 (simultaneously), and the reports for Event 1, Event 2, and Event 7 include an indicator field that shows whether the reporting beam satisfies the event conditions: - Case Q: The report for Event 7 (only) includes a field indicating the TCI status code point. - Case R: The report for Event 7 does not include a field indicating the TCI status code point.

[0269] <<Embodiment 2-2>> <<<Option 2-2-1>>> The UE / NW may assume that a single first UL channel resource is associated with only a CSI reporting setting, which has the same number of reported beams (e.g., nrofReportedRS-UEIBR-r19).

[0270] In other words, UE / NW may assume that the first UL channel resource referenced by the first UL channel resource setting configured for a CSI reporting setting where the number of reported beams is set to a certain value is different from the first UL channel resource referenced by the first UL channel resource setting configured for a CSI reporting setting where the number of reported beams is set to a value other than that certain value.

[0271] UE / NW may also follow the following options 2-2-1-1 / 2-2-1-2: • Option 2-2-1-1: The number of reporting beams is set to the same value in multiple (e.g., all) CSI reporting settings associated with a single primary UL channel resource. • Option 2-2-1-2: The number of reporting beams set for a specific CSI reporting setting associated with a specific primary UL channel resource is also applied to other CSI reporting settings.

[0272] Regarding option 2-2-1-2, the number of reporting beams may be set for a specific CSI reporting setting associated with a specific first UL channel resource, while the number of reporting beams may not be set for other CSI reporting settings. In this case, the number of reporting beams set for the specific CSI reporting setting may be applied to the CSI reporting setting for which the number of reporting beams is not set.

[0273] <<<Option 2-2-2>>> Multiple CSI reporting settings may be associated with a single first UL channel resource, each with a different number of reported beams (nrofReportedRS-UEIBR-r19).

[0274] UE / NW may also follow the following options 2-2-2-1 / 2-2-2-2 / 2-2-2-3: • Option 2-2-2-1: The number of reporting beams set for a CSI reporting setting with a specific (e.g., highest) priority among the CSI reporting settings associated with one primary UL channel resource is applied to other CSI reporting settings associated with the same primary UL channel resource. • Option 2-2-2-2: The number of reporting beams set for each CSI reporting setting associated with one primary UL channel resource is applied to other CSI reporting settings associated with the same primary UL channel resource. • Option 2-2-2-3: The number of reporting beams is determined according to the UE implementation.

[0275] The priority of option 2-2-2-1 may be determined according to at least one of the following options 2-2-2-1-1 to 2-2-2-1-4.

[0276] Option 2-2-2-1-1: The priority for Option 2-2-2-1 may be determined according to the existing method for calculating the priority of CSI reports (as defined up to Rel. 18).

[0277] Priority of existing CSI reports (as defined up to Rel. 18) iCSI ) may also be determined using the following formula: Pri iCSI (y,k,c,s) = 2*N cells *Ms *y+N cells *M s *k+M s *c+s

[0278] Here, y may be a value based on the type of CSI report (A-CSI report, SP-CSI report, or P-CSI report) and the channel through which the CSI report is transmitted (Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH)).

[0279] For example, y=0 for a non-periodic CSI report transmitted via PUSCH, y=1 for a semi-persistent CSI report transmitted via PUSCH, y=2 for a semi-persistent CSI report transmitted via PUCCH, and y=3 for a periodic CSI report transmitted via PUCCH.

[0280] k may be a value based on whether the CSI report includes L1-RSRP / SINR (for example, k=0 if the CSI report includes L1-RSRP / SINR, and k=1 if it does not). c may be the serving cell index. s may be the report configuration ID (reportConfigID). Note that L1-RSRP / L1-SINR may be set in different CSI reports.

[0281] Also, N ｃｅｌｌｓ This is the value of the maximum number of serving cells that can be set (upper layer parameter maxNrofServingCells), M ｓ This may also be the maximum number of CSI reporting configurations that can be set (the upper-layer parameter maxNrofCSI-ReportConfigurations).

[0282] In option 2-2-2-1-1, priority may be determined in descending order of CSI reporting setting IDs. In other words, priority may be determined to be highest for the smallest CSI reporting setting ID.

[0283] For UEIBR, y may be a specific value (for example, it may be 0, or any other value (any value from 1 to 3)).

[0284] Option 2-2-2-1-2: The priority for Option 2-2-2-1 may be determined according to a calculation method based on the existing (as defined up to Rel. 18) method for calculating the priority of CSI reports.

[0285] The priority for option 2-2-2-1 may be determined based on the priority between events.

[0286] For example, the priority for option 2-2-2-1 may be determined according to a calculation method in which a variable indicating the event type (e.g., e) is added to the existing CSI reporting priority calculation method (as defined up to Rel. 18).

[0287] Priority for Option 2-2-2-1 (Pri iCSI ) may be determined, for example, using at least one of the following formulas: Pri iCSI (e,y,k,c,s) = 8*N cells *M s *e+2*N cells *M s *y+N cells *M s *k+M s *c+s Pri iCSI (y,e,k,c,s) = 6*N cells *M s *y+2*N cells *M s *e+N cells *M s *k+M s *c+s Pri iCSI (y,k,e,c,s) = 6*N cells *M s *y+3*N cells *M s *k+N cells *M s *e+M s *c+s Pri iCSI (y,k,c,e,s) = 6*N cells *M s *y+3*N cells*M s *k+3*M s *c+M s *e+s Pri iCSI (y,k,c,s,e) = 6*N cells *M s *y+3*N cells *M s *k+3*M s *c+3*s+e

[0288] Note that the priority (Pri iCSI The calculation formulas shown are merely examples and are not limited to these. The constants / variables listed in the example formulas may be changed as appropriate. In addition, the variables listed in the example formulas may be reused from the variables in the existing CSI reporting priority calculation formulas (as defined up to Rel. 18).

[0289] For example, a variable indicating the event type (e.g., e) may have a first value (e.g., 0) for the highest priority event (e.g., event 2 or 7), a second value (e.g., 1) for the second priority event (e.g., event 2 or 7), and a third value (e.g., 2) for the third priority event (e.g., event 1).

[0290] For UEIBR, y may be a specific value (for example, it may be 0, or any other value (any value from 1 to 3)).

[0291] Option 2-2-2-1-3: The priority of option 2-2-2-1 may be determined according to the UE implementation.

[0292] Option 2-2-2-1-4: The priority for Option 2-2-2-1 may be determined based on RRC parameters indicating the priority of multiple CSI reporting settings associated with the same first UL channel source.

[0293] The RRC parameter may be defined, for example, within the CSI reporting settings.

[0294] The RRC parameter may be represented by x bits, and may have a maximum of 2 bits. ｘ You may also indicate the priority of the stages.

[0295] Furthermore, in Option 2-2-2-1-4, when the same priority is configured for different CSI reporting configurations, the UE / NW may apply the above Option 2-2-2-1-1 / 2-2-2-1-2 / 2-2-2-1-3.

[0296] <<Embodiment 2-3>> <<<Option 2-3-1>>> For one first UL channel resource, the UE / NW uses the same Ceil(log ２ (K ＲＳ Ｓ ) ) value, or the same K ＲＳ Ｓ value, it may be assumed that only the corresponding CSI reporting configuration is associated.

[0297] In other words, the UE / NW has a Ceil(log ２ (K ＲＳ Ｓ ) ) with a certain value, or a K ＲＳ Ｓ with a certain value, the first UL channel resource referenced by the first UL channel resource configuration configured for the corresponding CSI reporting configuration, and a Ceil(log ２ (K ＲＳ Ｓ ) ) with a different value, or a K ＲＳ Ｓ with a different value, it may be assumed that the first UL channel resource referenced by the first UL channel resource configuration configured for the corresponding CSI reporting configuration is different from the foregoing first UL channel resource.

[0298] The UE may assume that, in a plurality (for example, all) of CSI reporting configurations associated with one first UL channel resource, the RS resource set related to a new beam is configured such that Ceil(log ２ (K ＲＳ Ｓ ) ), or K ＲＳ Ｓ has the same value.

[0299] In a plurality (for example, all) of CSI reporting configurations associated with one first UL channel resource, the NW uses Ceil(log ２ (K ＲＳ Ｓ ) ), or KＲＳ Ｓ An RS resource set related to a new beam may be configured such that they have the same value.

[0300] <<<<Option 2-3-2>>>> For one first UL channel resource, Ceil(log ２ (K ＲＳ Ｓ )), or multiple CSI report configurations with different values of K ＲＳ Ｓ may be associated with each other.

[0301] The UE / NW may follow Option 2-3-2-1 / 2-3-2-2 below: ・Option 2-3-2-1: In multiple CSI report configurations associated with one first UL channel resource, Ceil(log ２ (K ＲＳ Ｓ )) is within a specific range, an RS resource set related to a new beam may be configured. ・Option 2-3-2-2: In multiple CSI report configurations associated with one first UL channel resource, Ceil(log ２ (K ＲＳ Ｓ )) have different values, an RS resource set related to a new beam may be configured.

[0302] In Option 2-3-2-1, the specific range is, for example, from the lower limit value of Ceil(log ２ (K ＲＳ Ｓ )) to the upper limit value of Ceil(log ２ (K ＲＳ Ｓ )).

[0303] In Option 2-3-2-1, the specific range may be, for example, a range up to the maximum number of bits that allows zero padding for a report.

[0304] In Option 2-3-2-1, the specific range may be defined in the specification in advance, may be configured / indicated using RRC signaling / MAC CE / DCI, or may be determined according to a report of UE capability.

[0305] Option 2-3-2-1 may include the following options 2-3-2-1-1 / 2-3-2-1-2: Option 2-3-2-1-1: CRI / SSBRI in the second UL channel / UEIBR transmitted based on the CSI reporting settings associated with one first UL channel resource is Ceil(log ２ (K ＲＳ Ｓ )) may be represented by the number of bits set as the upper limit. Option 2-3-2-1-2: CRI / SSBRI in the second UL channel / UEIBR may be represented by the number of bits determined according to the UE implementation.

[0306] Option 2-3-2-2 may include the following options 2-3-2-2-1 / 2-3-2-2-2 / 2-3-2-2-3: Option 2-3-2-2-1: CRI / SSBRI in the second UL channel / UEIBR transmitted based on the CSI reporting settings associated with one first UL channel resource is Ceil(log) corresponding to each CSI reporting setting ２ (K ＲＳ Ｓ )) may be represented using the largest number of bits among them. Option 2-3-2-2-2: In multiple CSI reporting settings associated with one first UL channel resource, Ceil(log) outside a specific range ２ (K ＲＳ Ｓ The CSI reporting setting corresponding to the value of )) may be disabled. In this case, the CRI / SSBRI in the second UL channel / UEIBR transmitted based on multiple CSI reporting settings associated with one first UL channel resource will be Ceil(log ２ (K ＲＳ Ｓ )) may be expressed in the number of bits set as the upper limit. The specific range may be one of the specific ranges described in option 2-3-2-1 above. Option 2-3-2-2-3: CRI / SSBRI in the second UL channel / UEIBR may be expressed in the number of bits determined according to the UE implementation.

[0307] According to the second embodiment described above, it is possible to contribute to solving the above problem 2.

[0308] <Third Embodiment> The third embodiment relates to a solution to the above problem 3.

[0309] The provisions described in the second embodiment above may apply to the indication of whether the CRI / SSBRI meets the event conditions, the indication of whether each reporting beam meets the event conditions, the field indicating the code point of the TCI status included in the report, and the field indicating the (one) CSI reporting setting included in the report.

[0310] The reporting format for Event 2 may include at least the following fields: • CRI or SSBRI (1st to Nth). • L1-RSRP (corresponding to the first CRI / SSBRI). • Differential L1-RSRP (corresponding to each of the second to Nth CRI / SSBRI). • Differential L1-RSRP of the current beam (if RRC signaling enables a reporting mode in which the current beam is always reported). • An indication that the CRI / SSBRI (1st to Nth) meets the event conditions (if enabled by RRC signaling). • An indication of (one) CSI reporting setting.

[0311] Each field shown as an example may be fixed in a specific order. This specific order may be defined in advance in the specification, set / instructed using RRC signaling / MAC CE / DCI, or determined according to UE capability reporting.

[0312] The reporting format for Event 7 may include a field indicating the TCI status code point, in addition to the reporting format for Event 2.

[0313] UE may perform zero padding if the (total) size of the UEIBR's reported content is less than the UEIBR's payload size reserved within the second UL channel.

[0314] The payload size of a UEIBR included in the second UL channel may be set aside to the largest payload size among the multiple UEIBRs associated with the CSI reporting settings linked to the first UL channel for determining transmission on the second UL channel.

[0315] If one report does not include a field that is present in another report, the UE may zero-padding that report.

[0316] The zero padding may be, for example, one of the following options 3A / 3B: Option 3A: In a given report, a sequence of zeros with the same number of bits as a given field is inserted at the same position as in the format of another report. Option 3B: In a given report, a sequence of zeros with the same number of bits as a given field is inserted at a specific position in the report (for example, at the end of the report).

[0317] Furthermore, option 3A or 3B may be applied separately or independently to each report / field.

[0318] Figure 5 shows an example of zero padding according to option 3A of the third embodiment. In Figure 5, the respective reporting formats for events 7, 2, and 1 are shown. In the example shown in Figure 5, since the reporting format for event 7 has the largest payload size, zero padding is performed on the respective reporting formats for events 2 and 1.

[0319] In the example shown in Figure 5, the report format for Event 1 does not include an indicator field showing whether the CRI / SSBRI (from the 1st to the Nth) meets the event's conditions, nor a field indicating the TCI status code point. Therefore, in the report format for Event 7, a sequence of zeros with the same number of bits as the indicator field / TCI status code point field is inserted at the same position.

[0320] In the example shown in Figure 5, the reporting format for event 2 does not include a field indicating the TCI status code point. Therefore, in the reporting format for event 7, a sequence of zeros with the same number of bits as the TCI status code point field is inserted at the same position as the TCI status code point field.

[0321] Figure 6 shows an example of zero padding according to option 3B of the third embodiment. In Figure 6, the respective report formats for events 7, 2, and 1 are shown. In the example shown in Figure 6, since the report format for event 7 has the largest payload size, zero padding is performed on the respective report formats for events 2 and 1.

[0322] In the example shown in Figure 6, the report format for Event 1 does not include an indicator field showing whether the CRI / SSBRI (from the 1st to the Nth) meets the event's conditions, nor a field indicating the TCI status code point. Therefore, a sequence of zeros with the same number of bits as the indicator field / TCI status code point field is inserted at the end of the report format for Event 1.

[0323] In the example shown in Figure 6, the report format for event 2 does not include a field indicating the TCI status code point. Therefore, a sequence of zeros with the same number of bits as the TCI status code point field is inserted at the end of the report format for event 2.

[0324] <<Embodiment 3-1>> The UE may perform zero-padding of the report format based on at least two associations of the first UL channel resource, event type, and CSI reporting settings, and the fields included in the report for each event.

[0325] At least two CSI reporting settings may be associated (simultaneously) with a single first UL channel resource: a CSI reporting setting for event 1, a CSI reporting setting for event 2, and a CSI reporting setting for event 7.

[0326] <<<Embodiment 3-1-1>>> A CSI reporting setting for event 1 and a CSI reporting setting for event 2 may be associated (simultaneously) with a single first UL channel resource.

[0327] The report for Event 2 may include an indicator field showing whether each reported beam satisfies the event conditions, while the report for Event 1 may not include such an indicator field.

[0328] In this case, zero padding for the instruction field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0329] The reports relating to Event 2 and Event 1 may include an indicator field that shows whether each reporting beam satisfies the event conditions.

[0330] In this case, zero padding may not be performed on the report related to Event 1 to match the payload size of the report related to Event 2.

[0331] <<<Embodiment 3-1-2>>> A CSI reporting setting for event 2 and a CSI reporting setting for event 7 may be associated (simultaneously) with a single first UL channel resource.

[0332] The report for Event 2 may include an indicator field showing whether each reporting beam satisfies the event conditions, while the report for Event 7 may not include such an indicator field. In this case, the report for Event 7 may (only) include a field indicating the TCI status code point.

[0333] In this case, zero-padding of the TCI status code point field in the report relating to event 2 may be performed using option 3A or option 3B described above.

[0334] In this case, zero padding for the instruction field may also be performed in the report relating to event 7 using option 3A or option 3B.

[0335] The report for Event 2 may include an indicator field showing whether each reported beam satisfies the event conditions, while the report for Event 7 may not include such an indicator field. In this case, the report for Event 7 may not include a field indicating the TCI status code point.

[0336] In this case, zero padding for the instruction field may be performed in the report relating to event 7 using option 3A or option 3B.

[0337] The reports for Event 2 and Event 7 may include an indicator field showing whether each reporting beam satisfies the event conditions. In this case, the report for Event 7 may (only) include a field indicating the TCI status code point.

[0338] In this case, zero-padding of the TCI status code point field in the report relating to event 2 may be performed using option 3A or option 3B described above.

[0339] The reports for Event 2 and Event 7 may include an indicator field showing whether each reporting beam satisfies the event conditions. In this case, the report for Event 7 does not need to include a field indicating the TCI status code point.

[0340] In this case, zero-padding may not be performed on the reports related to Event 2 and Event 7.

[0341] <<<Embodiment 3-1-3>>> A CSI reporting setting for event 1 and a CSI reporting setting for event 7 may be associated (simultaneously) with a single first UL channel resource.

[0342] In this case, the operation / provision to replace "event 2" with "event 1" in the above embodiment 3-1-2 may be applied.

[0343] <<<Embodiment 3-1-4>>> A CSI reporting setting for event 1, a CSI reporting setting for event 2, and a CSI reporting setting for event 7 may be associated (simultaneously) with a single first UL channel resource.

[0344] The report for Event 2 may include an indicator field showing whether each reported beam satisfies the event conditions, while the reports for Event 1 and Event 7 may not include such an indicator field. In this case, the report for Event 7 may (only) include a field indicating the TCI status code point.

[0345] In this case, zero padding for the instruction field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0346] In this case, zero padding for the TCI status code point field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0347] In this case, zero-padding of the TCI status code point field may be performed in the report relating to event 2 using either option 3A or option 3B.

[0348] In this case, zero padding for the instruction field may also be performed in the report relating to event 7 using option 3A or option 3B.

[0349] The report for Event 2 may include an indicator field showing whether each reported beam satisfies the event conditions, while the reports for Event 1 and Event 7 may not include such an indicator field. In this case, the report for Event 7 may not include a field indicating the TCI status code point.

[0350] In this case, zero padding for the instruction field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0351] In this case, zero padding for the instruction field may also be performed in the report relating to event 7 using option 3A or option 3B.

[0352] <<<Embodiment 3-1-5>>> A CSI reporting setting for event 1, a CSI reporting setting for event 2, and a CSI reporting setting for event 7 may be associated (simultaneously) with a single first UL channel resource.

[0353] The reports for Event 2 and Event 7 may include an indicator field showing whether each reported beam satisfies the event conditions, while the report for Event 1 may not include such an indicator field. In this case, the report for Event 7 may (only) include a field indicating the TCI status code point.

[0354] In this case, zero padding for the instruction field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0355] In this case, zero padding for the TCI status code point field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0356] In this case, zero-padding of the TCI status code point field may be performed in the report relating to event 2 using either option 3A or option 3B.

[0357] The reports for Event 2 and Event 7 may include an indicator field showing whether each reported beam satisfies the event conditions, while the report for Event 1 may not include such an indicator field. In this case, the report for Event 7 may not include a field indicating the TCI status code point.

[0358] In this case, zero padding for the instruction field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0359] <<<Embodiment 3-1-6>>> A CSI reporting setting for event 1, a CSI reporting setting for event 2, and a CSI reporting setting for event 7 may be associated (simultaneously) with a single first UL channel resource.

[0360] The reports for Event 1 and Event 2 may include an indicator field showing whether each reported beam satisfies the event conditions, while the report for Event 7 may not include such an indicator field. In this case, the report for Event 7 may (only) include a field indicating the TCI status code point.

[0361] In this case, zero padding for the TCI status code point field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0362] In this case, zero-padding of the TCI status code point field may be performed in the report relating to event 2 using either option 3A or option 3B.

[0363] In this case, zero padding for the instruction field may also be performed in the report relating to event 7 using option 3A or option 3B.

[0364] The reports for Event 1 and Event 2 may include an indicator field showing whether each reported beam satisfies the event conditions, while the report for Event 7 may not include such an indicator field. In this case, the report for Event 7 may not include a field indicating the TCI status code point.

[0365] In this case, zero padding for the instruction field may be performed in the report relating to event 7 using option 3A or option 3B.

[0366] <<<Embodiment 3-1-7>>> A CSI reporting setting for event 1, a CSI reporting setting for event 2, and a CSI reporting setting for event 7 may be associated (simultaneously) with a single first UL channel resource.

[0367] The reports for Event 1, Event 2, and Event 7 may include an indicator field showing whether each report beam satisfies the event conditions. In this case, the report for Event 7 may (only) include a field indicating the TCI status code point.

[0368] In this case, zero padding for the TCI status code point field may be performed in the report relating to event 1 using either option 3A or option 3B.

[0369] In this case, zero-padding of the TCI status code point field may be performed in the report relating to event 2 using either option 3A or option 3B.

[0370] The reports for Event 1, Event 2, and Event 7 may include an indicator field showing whether each reporting beam satisfies the event conditions. In this case, the report for Event 7 does not need to include a field indicating the TCI status code point.

[0371] In this case, zero-padding may not be required for the reports related to Event 1, Event 2, and Event 7.

[0372] <<Embodiment 3-2>> Multiple CSI reporting settings may be associated with one first UL channel resource.

[0373] For each of the multiple CSI reporting settings, different values ​​for the number of reporting beams (e.g., nrofReportedRS-UEIBR-r19) may be set.

[0374] In this case, zero-padding may be performed for a given report based on at least one of the following: the maximum number of report beams set for the CSI reporting settings, the number of report beams related to that report, and the number of bits required for reporting one beam.

[0375] For example, zero-padding may be performed on a given report by a number of bits calculated as {(maximum number of reporting beams set for the CSI reporting settings) - (number of reporting beams related to that particular report)} * (number of bits required for reporting one beam).

[0376] The zero padding may be, for example, one of the following options 3C / 3D: Option 3C: A sequence of zeros equal to the number of bits required for information about each beam in a report (e.g., CRI / SSBRI, measurement result (L1-RSRP), and an indicator field indicating whether the corresponding CRI / SSBRI meets the event criteria) is inserted at the same position as in the format of other reports. Option 3D: A sequence of zeros equal to the number of bits required for information about each beam in a report (e.g., CRI / SSBRI, measurement result (L1-RSRP), and an indicator field indicating whether the corresponding CRI / SSBRI meets the event criteria) is inserted at a specific position in the report (e.g., at the end of the report).

[0377] Furthermore, option 3C or 3D may be applied separately or independently to each report / field.

[0378] <<Embodiment 3-3>> Multiple CSI reporting settings may be associated with one first UL channel resource.

[0379] For each of the multiple CSI reporting settings, the number of RSs included in the RS resource set of new beams with different values ​​(e.g., K ＲＳ Ｓ ), and the number of bits in the CRI / SSBRI field that reports different values ​​(e.g., Ceil(log ２ (K ＲＳ Ｓ At least one of the following may be set: )))

[0380] In this case, for a given report, the maximum Ceil(log) set for the CSI reporting settings is... ２ (K ＲＳ Ｓ The value of )), Ceil(log) related to the said report ２ (K ＲＳ ＳZero padding may be performed based on at least one of the value of )) and the number of reported beams.

[0381] For example, for a certain report, {(the maximum Ceil(log configured for a CSI report configuration ２ (K ＲＳ Ｓ ))) - (Ceil(log related to said certain report ２ (K ＲＳ Ｓ ))))} * (number of reported beams) bits of zero padding may be performed.

[0382] Said zero padding may be performed at a specific position within the report. Said specific position may be, for example, option 3E / 3F below: ・Option 3E: A zero sequence having the calculated number of bits is inserted immediately after / right below a specific field (e.g., a CRI / SSBRI field) in said certain report. ・Option 3F: A zero sequence having the calculated number of bits is inserted at the end of said certain report in said certain report.

[0383] Note that option 3C or 3D may be applied separately / independently for each report / each field.

[0384] <<Embodiment 3-4>> An indication field for one CSI report configuration included in a UEIBR may be arranged at a specific position within the report.

[0385] Said specific position may be, for example, the beginning of the report.

[0386] Particularly when the aforementioned option 3B / 3D / 3F is applied, in order for the NW to determine the delimitation positions of each field in the report, it is desirable that the event type of the report can be identified in the earlier half (e.g., the beginning) of the report. Therefore, it is preferable that the indication field for one CSI report configuration is arranged at the beginning of the report.

[0387] According to the third embodiment described above, it is possible to contribute to solving the problem 3 above.

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

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

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

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

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

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

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

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

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

[0397] The specific UE capabilities described above may include at least one of the following: • Supporting specific processing / operations / controls / information for at least one of the embodiments described above; • Supporting event-triggered beam reporting / UEIBR; • Supporting MIMO / mobility Rel. 19 and later; • Supporting UEIBR using MAC CE / UCI; • Supporting event combinations (e.g., event 1 / 2 / 7); • Total number of beams reported; • Number of beams that meet the conditions; • Supporting a reporting format for a specific event (e.g., event 2 / 7 / 1); • Supporting zero-padding for the reporting format for a specific event (e.g., event 2 / 7 / 1).

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

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

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

[0401] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: • The information is set by one or more higher-layer parameters / RRC IEs. • The information is determined by one or more relevant higher-layer parameters / RRC IEs. • The information is indicated by MAC CE / DCI. • The information is based on one or more UE capabilities. • The information is described / defined in the specification. • The information is based on conditions described / defined in the specification. • The information is determined by a combination of several of the above. For example, the information is determined by the setting / indication of higher-layer parameters / MAC CE / DCIs and reported by UE capabilities.

[0402] The above multiple embodiments / options / choices may be combined into a single embodiment / option / choice.

[0403] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having a receiving unit that receives one or more reporting settings, one of which is associated with one or more events relating to a beam report initiated by the terminal, and a control unit that controls the transmission of the beam report, which includes or does not include instructions relating to the events, based on the one or more reporting settings and the occurrence of the multiple events. [Note 2] The terminal according to Note 1, wherein if one of which is associated with a first uplink channel relating to the beam report, the control unit assumes that one of which is associated with at least one of one or more reporting beam counts and one or more reference signal resource sets relating to new beams. [Note 3] The terminal according to Note 1 or Note 2, wherein if a field included in another beam report relating to a particular event among the multiple events is not included in the beam report, the control unit places a sequence of zeros with the same number of bits as the field in the beam report at the same position as in the other beam report. [Note 4] If a field included in another beam report relating to a specific event among the multiple events is not included in the beam report, the control unit places a sequence of zeros with the same number of bits as the field at the end of the beam report, as described in any of Notes 1 to 3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0436] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0451] The transmitting / receiving unit 120 may transmit one or more reporting settings. One of the reporting settings may be associated with one or more events relating to beam reporting initiated by a terminal. The control unit 110 may control the reception of the beam reporting, which may include or may not include instructions regarding the events, transmitted based on the one or more reporting settings and the occurrence of the events (first embodiment).

[0452] (User Terminal) Figure 9 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0470] The transmitting / receiving unit 220 may receive one or more report settings. One of the report settings may be associated with one or more events relating to beam reporting initiated by a terminal. The control unit 210 may control the transmission of the beam reporting, which may or may not include instructions relating to the events, based on the one or more report settings and the occurrence of the events (first embodiment).

[0471] If the one reporting setting is associated with a first uplink channel relating to the beam reporting, the control unit 210 may assume that the one reporting setting corresponds to at least one of the number of reporting beams and the number of reference signal resource sets relating to one or more new beams (second embodiment).

[0472] If a field included in another beam report relating to a particular event among the plurality of events is not included in the beam report, the control unit 210 may place a sequence of zeros with the same number of bits as the field in the beam report at the same position as in the other beam report (third embodiment).

[0473] If a field included in another beam report relating to a particular event among the multiple events is not included in the beam report, the control unit 210 may place a sequence of zeros with the same number of bits as the field at the end of the beam report (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0502] 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. Each TTI, subframe, etc., may consist of one or more resource blocks.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0573] This application is based on Japanese Patent Application No. 2025-051196, filed on March 26, 2025. All of its contents are included herein.

Claims

1. A terminal having a receiving unit that receives one or more reporting settings, one of which is associated with one or more events relating to beam reporting initiated by the terminal, and a control unit that controls the transmission of beam reporting, which includes or does not include instructions relating to the events, based on the one or more reporting settings and the occurrence of the events.

2. The terminal according to claim 1, wherein, if one of the reporting settings is associated with one first uplink channel relating to the beam reporting, the control unit assumes that one of the reporting settings corresponds to at least one of one of the number of reporting beams and the number of reference signal resource sets relating to one or more new beams.

3. The terminal according to claim 1, wherein if a field included in another beam report relating to a specific event among the plurality of events is not included in the beam report, the control unit places a sequence of zeros with the same number of bits as the field at the same position in the beam report as in the other beam report.

4. The terminal according to claim 1, wherein if a field included in another beam report relating to a particular event among the plurality of events is not included in the beam report, the control unit places a sequence of zeros with the same number of bits as the field at the end of the beam report.

5. A wireless communication method for a terminal, comprising the steps of: receiving one or more reporting settings, one of which is associated with one or more events relating to a beam report initiated by the terminal; and controlling the terminal to transmit the beam report, which includes or does not include instructions relating to the events, based on the one or more reporting settings and the occurrence of the events.

6. A base station having: a transmitting unit that transmits one or more reporting settings, one of which is associated with one or more events relating to beam reporting initiated by a terminal; and a control unit that controls the reception of the beam reporting, which is transmitted based on the one or more reporting settings and the occurrence of the multiple events, and which includes or does not include instructions relating to the events.

Images