Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a transmission / reception unit that receives, in a beam report (UEIBR) initiated by the terminal on the basis of a specific event related to a new beam, a configuration related to support of activation of an autonomous transmission configuration indicator (TCI) state of the terminal, or reports a capability relating to support of activation of the TCI state; and a control unit that, if activation of the TCI state is supported, anticipates the number of active TCI states to be supported and controls activation of the TCI states.

Description

Terminal, Wireless Communication Method, and Base Station

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

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

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

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

[0005] In a future wireless communication system (for example, NR, Rel. 19 and later), it is being considered to support UE-initiated Beam Report (UEIBR) that is initiated by a terminal (user terminal, User Equipment (UE)) (event-based).

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

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

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

[0009] A terminal according to one aspect of the present disclosure includes a transceiver unit that receives a setting for supporting the activation of autonomous transmit configuration instructions (TCI) states of the terminal, or reports the terminal's ability to support the activation of said TCI states, in a beam report (UEIBR) initiated by the terminal based on a specific event relating to a new beam, and a control unit that, when supporting the activation of said TCI states, controls the activation of said TCI states with respect to the number of supported active TCI states.

[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 TCI state deactivation according to this disclosure. Figure 3 shows the correspondence between the reporting beam (CSI-RS) and the activated TCI state according to this disclosure. Figure 4 shows the correspondence between the reporting beam (SSB) and the activated TCI state according to this disclosure. Figure 5 shows an example of TCI state setting for each CC (correspondence between QCL source RS and QCL type). Figure 6 shows an example of acceptable settings for the DMRS of PDCCH / PDSCH. 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 the 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] (TCI, Spatial Relations, QCL) In NR, it is being considered to control the receive processing (e.g., at least one of receive, demapping, demodulation, and decoding) and transmit processing (e.g., transmit, mapping, precoding, modulation, and encoding) of at least one of the signal and channel (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0013] The TCI state may represent the one applied to the downlink signal / channel. The equivalent of the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0014] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set in the UE for each channel or signal.

[0015] QCL is an index that indicates the statistical properties of a signal / channel. For example, if one signal / channel and another signal / channel have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0016] The spatial reception parameters may correspond to the received beam of the UE (e.g., the received analog beam), or the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0017] QCL may have multiple types (QCL types). For example, there may be four QCL types A-D with different parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread; QCL type B (QCL-B): Doppler shift and Doppler spread; QCL type C (QCL-C): Doppler shift and mean delay; QCL type D (QCL-D): Spatial reception parameters.

[0018] The QCL information shown in the above-mentioned QCL types A to D may also be called QCL properties.

[0019] The assumption by a User Engineer (UE) that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

[0020] The UE may determine at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of a signal / channel based on the TCI status or QCL assumption of the signal / channel.

[0021] The TCI state may, for example, be information regarding the QCL between the channel in question (in other words, the reference signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by upper-layer signaling, physical layer signaling, or a combination thereof.

[0022] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0023] The channel on which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

[0024] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Tracking CSI-RS (also called a Tracking Reference Signal (TRS)), or a QCL detection reference signal (also called a QRS).

[0025] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be called an SS / PBCH block.

[0026] The RS of a QCL type X in a TCI state may also mean the RS in the relationship between a channel / signal (and its DMRS) and a QCL type X, and this RS may be called the QCL source of the QCL type X in that TCI state.

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

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

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

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

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

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

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

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

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

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

[0037] (Beam reporting type) <Intra-cell beam reporting in Rel. 15 / 16> Intra-cell beam reporting is supported in Rel. 15 / 16. For example, L1-RSRP / SINR reporting can be configured by upper-layer signaling (RRC).

[0038] For example, in the calculation of L1-RSRP, the UE may configure either or both a CSI-RS resource and / or an SS / PBCH block resource if the resource is associated with QCL type C / type D.

[0039] Furthermore, the UE may configure up to 16 CSI-RS resource sets, each containing up to 64 resources. In all resource sets, the total number of different CSI-RS resources is 128 or less.

[0040] In L1-RSRP reporting, if the upper layer parameter nrofReportedRS (for example, in CSI-ReportConfig) is set to 1, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB.

[0041] Here, the maximum measurement of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB. The difference value of L1-RSRP is quantized to a 4-bit value.

[0042] The difference value is calculated with a step size of 2 dB by referring to the maximum measurement value that is part of the same L1-RSRP reporting instance.

[0043] For example, in L1-SINR calculation and channel measurement, the UE may be configured with either or both of the NZP CSI-RS resource and the SS / PBCH block resource. Also, for interference measurement, the UE may be configured with the NZP CSI-RS resource or the CSI-IM resource.

[0044] For channel measurement, the UE may be configured with CSI resource settings related to a maximum of 64 CSI resources or a maximum of 16 CSI-RS resource sets having SS / PBCH block resources.

[0045] In L1-SINR reporting, when the upper layer parameter nrofReportedRS is set to 1, the reported L1-SINR value is defined as a 7-bit value in the range of [-23 to 40] dBm with a step size of 0.5 dB.

[0046] When the upper layer parameter nrofReportedRS is set to a value greater than 1 or when the upper layer parameter groupBasedBeamReporting is set to "enabled", the UE uses the difference value-based L1-SINR value for reporting.

[0047] The difference value is calculated with a step size of 1 dB by referring to the maximum measurement value that is part of the same L1-SINR reporting instance.

[0048] In the present disclosure, the in-cell beam reporting of Rel. 15 / 16 (which may also be simply referred to as in-cell beam reporting) may be referred to as type 1 beam reporting (beam reporting type 1) or beam reporting for in-cell beam switching.

[0049] <Inter-cell beam report for Rel. 17> As mentioned above, L1 / L2 inter-cell mobility is supported in Rel. 17. For example, a UE can send and receive UL / DL channels / signals to and from a PCI of a different cell than the PCI of the serving cell. For example, if a non-serving cell has a larger RSRP than the serving cell, the UE can send and receive UL / DL channels / signals to and from the non-serving cell without performing a handover.

[0050] In the L1-RSRP report, the absolute value / difference value of L1-RSRP may be used, as in Rel. 15 / 16. In the inter-cell beam report of Rel. 17 (Type 2-1 beam report described later), each L1-RSRP value is associated with a PCI ID (for the serving cell / additional cell / candidate cell). The association between the L1-RSRP value and the PCI ID may be set / instructed by upper-layer signaling / physical-layer signaling.

[0051] The configuration using upper-layer signaling supports up to seven additional cells. Note that ID=0 indicates the PCI of the serving cell.

[0052] In this disclosure, inter-cell beam reporting (in Rel. 17 / 18) may be referred to as Type 2 beam reporting (Beam reporting type 2). Type 2 beam reporting can be further classified into types 2-1 and 2-2, as described below.

[0053] In this disclosure, the beam report of Rel. 17 may be referred to as a type 2-1 beam report, or a beam report for inter-cell beam switching.

[0054] <Inter-cell beam reporting for Rel. 18> Furthermore, beam reporting for Rel. 18 is only supported as SSB-based L1-RSRP reporting (beam reporting). Here, the number of candidate cells L is one of 1 to 4, and the number of beams M per cell may be one of 1 to 4. For example, in beam reporting, a 7-bit absolute value (the largest L1-RSRP value among all cells) is reported for one cell, and all remaining L1-RSRP values ​​are reported as difference values.

[0055] Regarding beam selection in SSB-based L1-RSRP reporting, the maximum value of M*L and the combination of M and L that can be set in RRC may vary depending on the UE capabilities.

[0056] In the L1-RSRP report, the absolute value / difference value of L1-RSRP may be used, as in Rel. 15 / 16 / 17.

[0057] In L1-RSRP reporting, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB.

[0058] Here, the maximum measurement of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB. The difference value of L1-RSRP is quantized to a 4-bit value.

[0059] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP reporting instance.

[0060] The L1-RSRP report includes the SSBRI between the configured candidate cells. In other words, the L1-RSRP report includes the SSBRI of the configured candidate cells and the corresponding L1-RSRP. The format may be the same as the existing specification.

[0061] In this disclosure, the beam report of Rel. 18 may also be referred to as a type 2-2 beam report or a beam report for cell switching. Note that the type 2-2 beam report does not include PCI information (PCI ID). Instead, the SSBRI may include PCI information. For example, if four cells have 64 SSBs, the SSBRI will be one of {0, 1, ..., 255}.

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

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

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

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

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

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

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

[0069] Note that this type of event does not exclude the events described above. For example, this type of event may be interpreted as a substitute for the events described above as appropriate.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0089] (Considerations for Measurement Reports) CSI-RS-based L1-RSRP measurement is supported. Furthermore, support for CSI-RS-based L1-SINR measurement is being considered.

[0090] Explicit configuration of CSI-RS resources for candidate cells for L1 measurement is supported.

[0091] CSI-RS-based L1-RSRP reports are supported for measurement reports scheduled by gNBs. Furthermore, support for CSI-RS-based L1-SINR reports for measurement reports scheduled by gNBs is being considered.

[0092] The Rel. 18 framework for CSI reporting for LTMs can serve as a baseline for CSI-RS-based L1 measurement reports scheduled by gNBs.

[0093] SSB-based / CSI-RS-based L1-RSRP measurement is supported for event-triggered reporting (event-based beam reporting). Furthermore, support for L1-SINR measurement for event-triggered reporting (event-based beam reporting) is being considered.

[0094] (Event-Triggered Beam Reporting for Mobility) The above-mentioned UEIBR (Event-Triggered Beam Reporting) can also be extended for mobility.

[0095] For example, the following LTM events are supported as L1 LTM measurement events, based on the beam quality of the serving cell and candidate cell: • Event LTM2: The serving cell's beam falls below the absolute threshold. • Event LTM3: The candidate cell's beam is offset better than the serving cell's beam. • Event LTM4: The candidate cell's beam is better than the absolute threshold. • Event LTM5: The serving cell's beam falls below absolute threshold 1 (first absolute threshold), and the candidate cell's beam is better than another absolute threshold 2 (second absolute threshold).

[0096] In addition to the events mentioned above, consideration is being given to which beams in the serving cell and adjacent cells should be used for event evaluation, as well as the necessity of event LTM1.

[0097] (Various settings in the CSI reporting framework for Rel. 18 LTM) In the CSI reporting settings for Rel. 18 LTM, the resource settings include a list of candidate IDs that are one-to-one mapped to a list of SSB indices. Rel. 18 LTM only supports SSB-based L1-RSRP.

[0098] In LTM Rel. 18, the configuration of CSI-RS resources / resource sets may be provided under a parameter (LTM-TCI-Info) for a single LTM candidate ID.

[0099] The configuration of NZP CSI-RS resource sets follows the rules of Rel. 17 and has resource set-specific parameters.

[0100] (MAC CE-based event-triggered beam reporting for mobility) The use of MAC CE is being considered for L1 measurement reporting.

[0101] For example, an event-triggered L1 measurement may be reported from the UE to the network (NW) via the MAC CE.

[0102] The following is specified regarding existing resource allocations:

[0103] Logical channels may be prioritized in the following order (the highest priority may be placed first): • MAC CE for C-RNTI, or data from the Uplink Common Control Channel (UL-CCCH). • [Extended] MAC CE for Beam Fault Recovery (BFR), or MAC CE for Setting Grant (CG) Verification, or MAC CE for Multiple Entry CG Verification. • MAC CE for Sidelink (SL) CG Verification. • MAC CE for Listen Before Talk (LBT) failure. • MAC CE for SL LBT failure according to specific specifications. • MAC CE for Timing Advance Report. • MAC CE for Buffer Status Report (BSR) included for padding. • MAC CE for SL-BSR included for padding.

[0104] The prioritization of MAC CEs with the same priority level may depend on the UE implementation.

[0105] (Analysis) The event-triggered beam reporting described above is being considered for extension to mobility applications (for LTMs). For example, the activation of autonomous TCI states in event-triggered beam reporting for LTMs is being considered.

[0106] Autonomous TCI state activation can reduce the delay in such activation and minimize data [reception] interruption time in LTM.

[0107] Furthermore, the use of MAC CE as a reporting container is being considered for event-triggered beam reporting for LTM.

[0108] However, the method for activating autonomous TCI states in event-triggered reporting for LTMs is unclear. Specifically, it is necessary to define the detailed behavior regarding how to determine the activated TCI state (active TCI state) based on event-triggered beam reporting.

[0109] Furthermore, the UE's ability to maintain a number of active TCI states may be limited. For example, if the number of TCI states activated by MAC CE and the number of TCI states autonomously activated by the UE exceeds the UE's capacity, it is necessary to clarify what action the UE should take.

[0110] In other words, it is important / necessary for the network side and the UE side to have the same understanding (share) of whether or not the TCI status is active in the UE.

[0111] Thus, the regulations for activating the autonomous TCI state in event-triggered reporting for LTM are not sufficiently clear. The same applies to UEIBR for MIMO. If these regulations are not clear, it will be impossible to achieve lower latency communication, which may lead to a suppression of improvements in communication quality / throughput.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] In this disclosure, event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting, event-triggered reporting / measurement, and UE-initiated beam management (UEIBM) are interchangeable.

[0128] In this disclosure, event-triggered [beam] reports may be interpreted interchangeably with beam reports, CSI reports, L1-RSRP beam reports, and L1-SINR beam reports. These reports may also be simply referred to as reports.

[0129] In this disclosure, the CSI report and the CSI report for LTMs Rel. 18 may be interpreted as mutually interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0174] (Wireless Communication Method) Embodiments of this disclosure can be classified as follows: • First embodiment: Activation of TCI state. • First' embodiment: Relationship between TCI state activation and UE capability. • First'' embodiment: Correspondence (association / mapping) between reported beam and [activated] TCI state. • Second embodiment: Method for activating TCI state. The following will be explained based on these.

[0175] The UE may perform / control measurement / reporting or activation / deactivation of the TCI status by applying the provisions described herein (the various provisions described above and the embodiments described below). The NW / BS / gNB may provide / transmit to the UE settings / instructions, etc., for the UE to implement such control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive such reports (beam reports / CSI reports) from the UE.

[0176] This disclosure is applicable to both MIMO and mobility use cases. Beam reporting for MIMO may be handled by UEIBR, while beam reporting for mobility may be handled by event-triggered beam reporting.

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

[0178] In this disclosure, CSI-RS, SSB, and TRS may be interpreted as interchangeable.

[0179] In this disclosure, the terms resource, resource set, and resource list may be interpreted interchangeably.

[0180] In this disclosure, the channel measurement resource, the interference measurement resource, and the resource may be interpreted as interchangeable.

[0181] In this disclosure, the terms activated TCI state, active TCI state, and simply TCI state may be interpreted interchangeably.

[0182] In this disclosure, UE capability and UE feature may be interpreted interchangeably.

[0183] Embodiments of this disclosure may apply only to any of the following: • Unified TCI state (in this case, not applicable to the Rel. 15 TCI framework); • Rel. 15 TCI framework; • Rel. 15 TCI framework and Rel. 17 Unified TCI framework; • Joint TCI state / DL TCI state (in this case, not applicable to the UL TCI state).

[0184] In the following embodiments, event-triggered beam reporting for mobility is used as an example, but the invention is not limited thereto. The following embodiments (including the entire disclosure) are also applicable to UEIBR for MIMO or self-free scenarios.

[0185] For example, for MIMO applications, event-triggered beam reporting may be interpreted as UEIBR. For MIMO applications, the reporting beam may be a beam from a serving cell / candidate cell. Also, the TCI status associated with the reporting beam may be a TCI status from a serving cell / candidate cell.

[0186] Furthermore, in a self-free scenario, if a beam report from a specific transmit / receive point (TRP) / TRP cluster / RS set is triggered, the UE may activate the TCI state associated with that specific TRP / TRP cluster / RS set.

[0187] In this disclosure, TRP group, TRP cluster, TRP clustering, and RS set may be interpreted interchangeably.

[0188] This disclosure clarifies the provisions regarding the activation / deactivation of the TCI state (autonomous activation / deactivation of the TCI state by the UE). Based on these provisions, the UE can appropriately control the activation / deactivation of the TCI state. As a result, lower latency communication can be achieved, and communication quality / throughput can be improved.

[0189] <First Embodiment> The first embodiment relates to the activation of the TCI state.

[0190] Whether the UE supports autonomous activation of the TCI state based on event-triggered beam reports may be configured / instructed by higher-layer signaling / physical-layer signaling, or may be determined according to the UE's capabilities.

[0191] The following describes how the TCI state is determined. The actions shown below (TCI state activation / deactivation actions) can be performed by the UE, assuming a number of activated TCI states (not exceeding the UE's capabilities) for each candidate cell or across all cells.

[0192] <<Option 1>> In event-triggered beam reporting, all reported beams from candidate cells associated with the TCI status [from candidate cells] may be assumed to be activated by the UE.

[0193] <<Option 2>> In event-triggered beam reporting, some (partial) reported beams from candidate cells associated with the TCI status from candidate cells may be assumed to be activated by the UE.

[0194] Some of the reporting beams [from candidate cells] may fall under at least one of the following options:

[0195] (Option 2-A) One or more beams of higher quality than the serving beam (serving beam) selected based on the L1-RSRP / L1-SINR values ​​in the beam report.

[0196] (Option 2-B) One or more indicated beams, indicated based on an explicit indication in the report regarding whether a beam is of better / worse quality than the serving beam.

[0197] (Option 2-C) One or more indicated beams, indicated based on an explicit indication in the report regarding whether a beam has been activated by the UE.

[0198] (Option 2-D) One or more beams indicated / selected based on explicit instructions regarding the TCI state to be activated by the UE.

[0199] Option 2-D differs from Option 2-C in that the activated TCI state is directly indicated instead of the beam.

[0200] (Option 2-E) One or more beams specified / selected based on instructions regarding the number of beams and resource location / arrangement (mapping order).

[0201] (Note) In addition to the above-mentioned options 2-A / 2-B / 2-C, the following other constraints may also apply.

[0202] For example, the number of activated beam / TCI states based on event-triggered beam reports may be limited by predefined / configured values ​​(M1, M2).

[0203] Here, M1 may represent the number of beam / TCI states per candidate cell. More specifically, M1 may represent the maximum number of activated TCI states (or the maximum number of beams) per candidate cell based on a single event-triggered beam report.

[0204] Furthermore, M2 may represent the number of beam / TCI states (across all candidate cells) that span multiple candidate cells. More specifically, M2 may represent the maximum number of activated TCI states (or the maximum number of beams) that span multiple candidate cells (across all candidate cells) based on a single event-triggered beam report.

[0205] <<Applicable RS>> Examples of RS to which this disclosure applies / is supported include:

[0206] (Alt1) Both SSB and CSI-RS. This disclosure may be applied to and supported in both SSB-based measurement / reporting and CSI-RS-based measurement / reporting.

[0207] (Alt2) CSI-RS only. This disclosure may apply to / support only CSI-RS based measurements / reports. In other words, this disclosure may not apply to / support SSB based measurements / reports.

[0208] <<Feature Settings / Activation>> The following options may be applied to the settings / activation of the features in this disclosure.

[0209] (Alt1) The functions described in this disclosure may be configured / enabled on a per-UE basis. For example, the functions described in this disclosure may be applied to all reporting settings for event-triggered beam reporting.

[0210] (Alt2) The functionality described in this disclosure may be configured / enabled for each reporting configuration for event-triggered beam reporting. The functionality described in this disclosure may also be configured / enabled for only a specific reporting configuration (e.g., ReportConfigID=5).

[0211] (Note) The functionality of this disclosure may be applied to reporting settings associated with the specific events described above (e.g., events LTM3 / LTM4 / LTM5).

[0212] <<Modification 1>> In addition to activating the TCI state, the UE may also deactivate the TCI state based on the event-triggered beam report. For example, the following options can be illustrated. Figure 2 shows an example of TCI state deactivation according to this disclosure.

[0213] As shown in Figure 2, we assume a case where four resources (for example, RS#1-a / 1-b / 1-c / 1-d, 2-a / 2-b / 2-c / 2-d, 3-a / 3-b / 3-c / 3-d, 4-a / 4-b / 4-c / 4-d) are set for each of the four candidate cells #1 to #4.

[0214] (Alt1) The TCI state of candidate cells other than the candidate cell that has an activated TCI state may be deactivated by the UE.

[0215] For example, as shown in Figure 2, if a report includes report beams from candidate cells #3 and #4, the UE may activate the TCI state for candidate cells #3 and #4 and deactivate the TCI state for the other candidate cells #1 and #2.

[0216] (Alt2) For candidate cells with activated TCI states, only the decision / indication TCI state or decision / indication beam may be activated, and all other TCI states for the reported candidate cell may be deactivated.

[0217] For example, as shown in Figure 2, if a report includes two TCI states for candidate cell #3 (RS#3-a, #3b) and two TCI states for candidate cell #4 (RS#4-c, #4-d), the UE may activate only the four TCI states for candidate cells #3 and #4 (RS#3-a, #3-b, #4-c, #4-d) and deactivate the other TCI states for candidate cells #3 and #4 (RS#3-c, #3-d, #4-a, #4-b).

[0218] (Alt3) The UE does not need to deactivate TCI states as long as it does not exceed the UE's capacity regarding the number (maximum number) of TCI states.

[0219] (Alt4) The above Alt1 and Alt2 may be applied in combination. For example, the UE may deactivate the activated TCI state of all set candidate cells. That is, the UE may deactivate the previous (past) TCI state of all candidate cells.

[0220] (Note) This disclosure (modification 1) is also applicable to UEIBR for MIMO. In this case, the previous (past) active TCI state activated by the MAC CE of the serving cell may be deactivated.

[0221] <<Modification 2>> The following options can be given as examples of the timing of TCI state activation / deactivation. That is, the UE may perform TCI state activation / deactivation at at least one of the following timings.

[0222] (Alt1) Alt1: The timing at which the event-triggered beam report is reported / sent.

[0223] (Alt2) Alt2: Timing after a predetermined time (X symbol / slot / other time unit) has passed since the event-triggered beam report was reported / sent.

[0224] According to this embodiment, the UE can appropriately control the activation / deactivation of the TCI state in event-triggered beam reporting.

[0225] <Embodiment 1'> Embodiment 1' relates to the relationship between TCI state activation and UE capability.

[0226] After the activation of TCI states is performed based on the first embodiment described above, the number of activated TCI states may exceed the UE capacity.

[0227] Here, let X be the number of TCI states to be activated according to the first embodiment. Let X + E be the total number of active TCI states after activation (where E may represent the number of existing active TCI states). Let Y be the maximum number of TCI states supported by the UE capability.

[0228] In this case, the following options can be exemplified as possible (applicable) UE behaviors.

[0229] <<Option 1>> The UE may refuse (do not perform) the activation of the TCI state.

[0230] <<Option 2>> The UE may select and activate some (partial) TCI states until it reaches the maximum number supported by the UE capabilities.

[0231] <<Option 3>> The UE may first decide to activate all (i.e., X) TCI states to be activated. Next, the UE may select and deactivate some (some) TCI states from all (i.e., X + E) active TCI states that would remain if the activation were performed, until the number of remaining active TCI states is less than or equal to the UE's capacity (i.e., Y or less).

[0232] In other words, the UE first performs activation on all TCI states to be activated, regardless of the UE's capabilities. If the number of active TCI states exceeds the UE's capabilities as a result, the UE performs deactivation on the active TCI states that exceed the UE's capabilities. The UE may continue this deactivation until the UE's capabilities are satisfied. This allows the UE to adjust the number of active TCI states to be below the maximum number supported by the UE's capabilities.

[0233] In other words, the first step in Option 3 (where the UE decides to activate multiple TCI states) may include the deactivation step in the first embodiment.

[0234] <<Other>> The UE may determine / decide which TCI states are activated based on the corresponding procedure [in the first embodiment]. The UE may then decide / decide and perform deactivation of several TCI states based on at least one of the following conditions until the corresponding UE capability is met.

[0235] - The oldest (first) timing to activate a single TCI state (or the predetermined period for which a single TCI state remains activated / maintained). - TCI state ID. - Candidate cell ID. - Frequency ID.

[0236] Priorities may be assigned to these conditions. In the case of UEIBR for MIMO, an additional condition may be added: whether the TCI status is associated with the serving cell / candidate cell.

[0237] According to this embodiment, the UE can appropriately control the activation / deactivation of the TCI state in event-triggered beam reporting.

[0238] <Embodiment 1''> Embodiment 1'' relates to the correspondence (association / mapping) between reported beams and activated TCI states.

[0239] A specific RS resource reported within a beam report (e.g., an SSB / CSI-RS / TRS resource) may be associated with one or more TCI states.

[0240] <<Case 1: SSB>> More specifically, if the reporting beam is an SSB#S from a candidate cell (where S can mean any number / index), then one or more TCI states from the same candidate cell may be determined to be related in the following cases:

[0241] In other words, the UE may determine / confirm that a reported beam from a candidate cell is associated with one or more TCI states from that candidate cell in the following cases:

[0242] - If at least one of the QCL source RSs in the TCI state is QCLed (QCLed, i.e., QCL relationship) with the reported SSB (reporting beam).

[0243] Here, the QCL source RS may be an RS of a specific QCL type (e.g., QCL type A / D), and may be represented, for example, as CSI-RS#T,#M (where T and M represent any number / index).

[0244] For example, SSB#S and CSI-RS#T may be directly associated. Alternatively, SSB#S and CSI-RS#T may be indirectly associated via CSI-RS#M. More specifically, SSB#S and CSI-RS#M may be associated, and CSI-RS#M and CSI-RS#T may be associated.

[0245] Furthermore, multiple TCI states may be associated with a single SSB.

[0246] <<Case 2: CSI-RS>> If the reporting beam is CSI-RS#A from a candidate cell (where A can mean any number / index), then one TCI state from the same candidate cell may be determined to be associated in the following cases:

[0247] In other words, the UE may determine / confirm that a reported beam from a candidate cell is associated with one or more TCI states from that candidate cell in the following cases:

[0248] - If at least one of the TCI-state QCL source RSs is QCLed (QCLed, i.e., QCL relationship) with the reported CSI-RS (reporting beam).

[0249] Here, the QCL source RS may be an RS of a specific QCL type (e.g., QCL type A / D), and may be represented, for example, as CSI-RS#T,#M (where T and M represent any number / index).

[0250] For example, CSI-RS#A and CSI-RS#T may be directly related. Alternatively, CSI-RS#A and CSI-RS#T may be indirectly related via CSI-RS#M. More specifically, CSI-RS#A and CSI-RS#M may be related, and CSI-RS#M and CSI-RS#T may be related.

[0251] The "TCI state" in Case 1 / Case 2 described above may be set (or included in the list) in the following list: • For event-triggered beam reporting for mobility, the Candidate TCI state (CandidateTCI-State). • For UEIBR for MIMO, the PDSCH setting (PDSCH-Config).

[0252] <<Specific Example 1>> Figure 3 is a diagram showing the correspondence between the reporting beam (CSI-RS) of this disclosure and the activated TCI state.

[0253] For example, consider the case shown in Figure 3, where one SSB with a wide beam corresponds to a CSI-RS with four narrow beams.

[0254] The reporting beam (CSI-RS) may be associated with an SSB (e.g., QCL type D). The SSB may be a QCL source RS for a periodic CSI-RS.

[0255] Furthermore, TRS#1 may be associated with an SSB (e.g., QCL type A / D). The SSB may be the QCL source RS of TRS#1 set in a certain TCI state #1.

[0256] In Figure 3, the activation of TCI state #1 (TRS#1) associated with the SSB may be supported.

[0257] <<Specific Example 2>> Figure 4 is a diagram showing the correspondence between the reporting beam (SSB) of this disclosure and the activated TCI state.

[0258] Figure 4 shows an example where multiple TCI states are associated with a single reporting beam (SSB), and that SSB activates multiple TCI states.

[0259] For example, SSB #1 (report beam) may be the QCL source RS for TRS #1 corresponding to TCI state #1 and TRS #2 corresponding to TCI state #2 (e.g., QCL type A / D). TRS #1 and #2 may be the QCL target RS for SSB #1. SSB #1 (report beam) may activate two TCI states, #1 and #2.

[0260] Furthermore, SSB #2 (report beam) may be the QCL source RS for CSI-RS #1 and CSI-RS #2 corresponding to TCI state #3 (e.g., QCL type A / D). CSI-RS #1 and #2 may be the QCL target RS for SSB #2. SSB #2 (report beam) may activate two TCI states #3 and #4.

[0261] <<Other>> The TCI status may be used to indicate QCL information for the DMRS of PDCCH / PDSCH or CSI-RS / TRS. Here, the QCL information may include up to two sets (QCL #1, #2) for the QCL source RS and QCL type.

[0262] A TCI state may be set for the target RS (for example, the DMRS of PDCCH / PDSCH).

[0263] Figure 5 shows an example of TCI status settings for each CC (correspondence between QCL source RS and QCL type).

[0264] As shown in Figure 5, two QCL#, #2 are set (associated) with the DMRS (Target RS) of PDCCH in BWP#1 of CC#2.

[0265] QCL#1 (QCL Type A) is associated with the QCL source RS in the BWP#1 of CC#2.

[0266] QCL#2 (QCL Type D) associates CSI-RS#1 in BWP#1 of CC#1 with QCL source RS.

[0267] Furthermore, the following specific constraints may be imposed on the setting of the TCI state.

[0268] For example, the cell ID of the source RS should be the same as that of the target RS, except for RS of a specific QCL type (e.g., QCL type C / D).

[0269] Alternatively, only a limited number of combinations of two QCL RSs may be permitted.

[0270] Figure 6 shows an example of an acceptable setting (combination) for DMRS in PDCCH / PDSCH.

[0271] In Figure 6, the TRS of QCL type A and the TRS of QCL type D (which is the same as the TRS of QCL type A) may be associated (combined). Also, the TRS of QCL type A and the CSI-RS of QCL type D (with repetition [transmission]) may be associated (combined). Also, the CSI-RS of QCL type A (without repetition [transmission]) and the CSI-RS of QCL type D (with repetition [transmission]) may be associated (combined).

[0272] According to this embodiment, the correspondence between the reported beam and the TCI state becomes clear. Based on this correspondence, the UE can appropriately control the activation / deactivation of the TCI state.

[0273] <Second Embodiment> The second embodiment relates to a method for activating the TCI state.

[0274] Two methods can be exemplified for activating the TCI status: • Activation by MAC CE. • Activation based on event-triggered beam reporting.

[0275] <<Setting / Applying Activation Methods>> The following options are examples of how to set / apply the two methods described above.

[0276] (Option 1) The UE may be configured (applied) using two methods simultaneously.

[0277] (Option 2) The UE may be set (applied) using only one of the two methods at a time.

[0278] <<UE Capabilities>> Regarding UE capabilities related to the activation method of the TCI state, the following options can be exemplified.

[0279] (Option 1) UE capability regarding the maximum number of activated TCI states per candidate cell or across all cells, based on event-triggered beam reporting, may be introduced / defined separately from existing UE functions (e.g., UE functions 45-3a / 4a of Rel. 18).

[0280] Separate UE capabilities may be introduced / defined for the two methods.

[0281] (Option 2) A new UE capability may be introduced / defined [common to] the two different activation methods described above, regarding the maximum number of activated TCI states per candidate cell or across all cells.

[0282] In other words, regardless of the type of activation method (which activation method it is), one UE capability may be introduced / defined for an activated TCI state.

[0283] (Note) Separate UE capabilities may be introduced / defined for each unified TCI state mode (joint TCI state mode, or individual DL / UL TCI state modes).

[0284] <<Activation Method Priority / Procedure>> When the two activation methods described above are set / applied simultaneously, at least one of the following options may be applied to determine the priority (priority) / procedure.

[0285] (Option 1) The priority order of the two methods for activating the TCI state may be the same. The UE may control / execute the activation / deactivation of the TCI state based on the corresponding procedures (chronological order) of each method.

[0286] If the TCI state is activated based on a specific method, but the corresponding UE capability is not met, the UE may perform the following actions:

[0287] The UE may determine / judge the activated TCI states based on the corresponding procedure. The UE may then decide / judge and perform deactivation of several TCI states based on at least one of the following conditions until the corresponding UE capability is met.

[0288] - The oldest (first) timing to activate a single TCI state (or the predetermined period for which a single TCI state remains activated / maintained). - TCI state ID. - Candidate cell ID. - Frequency ID.

[0289] (Option 2) The priority order of the two methods for activating the TCI state may be different. That is, different priorities may be defined / introduced for each method. For example, when a UE performs TCI state deactivation, it may apply at least one of the following optional actions.

[0290] ((Opt2-1)) The following options are examples of deactivation behavior based on event-triggered beam reporting. That is, the UE may apply deactivation behavior based on event-triggered beam reporting to the TCI conditions shown in the following options.

[0291] <Alt-A> A TCI state that was previously activated by the same method (activation based on event-triggered beam reporting).

[0292] <Alt-B> TCI status that was previously activated by any method (by MAC CE / based on event trigger reporting).

[0293] ((Opt2-2)) Existing MAC CE deactivation behavior (e.g., Rel. 18) (i.e., TCI states not indicated in candidate cells indicated by MAC CE are deactivated) can be exemplified by the following options. That is, the UE may apply MAC CE deactivation behavior to the TCI states shown in the following options.

[0294] <Alt-C> TCI state that was previously activated using the same method (activation via MAC CE).

[0295] <Alt-D> TCI states that were previously activated by any method (by MAC CE / based on event trigger reporting).

[0296] In Option 2, if the activation of a TCI state is performed based on a specific method, but the corresponding UE capability is not met, the UE may decide to deactivate some TCI states based on the conditions of Option 1 until the corresponding UE capability is met.

[0297] Furthermore, the UE may consider / apply at least one of the following additional conditions, in addition to the conditions of Option 1 described above, as a condition for the decision / judgment.

[0298] - Whether a particular TCI state was previously activated by the MAC CE method. - Whether a particular TCI state was previously activated by the event-triggered beam reporting method.

[0299] Priorities may be defined / specified for these conditions (the conditions of Option 1 and additional conditions). These priorities may be predefined by the specification or set / indicated by upper-layer signaling / physical layer signaling.

[0300] The second embodiment is also applicable to a UEIBR for MIMO. In this case, the activation of the TCI state by MAC CE may mean the activation of the TCI state by MAC CE from the serving cell.

[0301] According to this embodiment, the method for activating the TCI state becomes clear. Based on this activation method, the UE can appropriately control the activation / deactivation of the TCI state.

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

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

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

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

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

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

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

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

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

[0311] 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 the Rel. 18 framework for CSI reporting for LTM; • Supporting MIMO / mobility from Rel. 19 onwards; • Supporting MAC CE-based event-triggered beam reporting (UEIBR); • Supporting L1-RSRP / SINR measurement / reporting; • Maximum number of candidate cells / frequency / report configurations / CSI-RS / IMR resources / resource sets per UE; • Supporting CSI measurement / reporting for candidate cells before cell switching; • Supporting aperiodic / semi-persistent / periodic CSI reporting; • Supporting CSI reporting by PUCCH / PUSCH / MAC CE; • Supported codebook types (e.g., whether to support Type 1 single-panel CSI reporting); • Supported reporting volume. - Whether to support CSI measurement / reporting for candidate cells during cell switching via MAC CE. - Whether to support CSI reporting for candidate cells / target candidate cells to the serving cell. - To support autonomous TCI status activation / deactivation by UE.

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

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

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

[0315] (Note) The following inventions are added with respect to one embodiment of the present disclosure (for mobility): [Note 1] A terminal having: a transceiver unit that receives a setting for supporting the activation of autonomous transmit setting instruction (TCI) states of a terminal in an event-triggered beam report based on a specific event relating to a candidate cell, or reports the terminal's ability to support the activation of the TCI states; and a control unit that, when supporting the activation of the TCI states, controls the activation of the TCI states with respect to the number of supported active TCI states. [Note 2] The terminal according to Note 1, wherein if the number of TCI states to be activated exceeds the number of supported active TCI states, the control unit selects some of the active TCI states and performs deactivation. [Note 3] The terminal according to Note 1 or Note 2, wherein the TCI states to be activated are associated with a specific reference signal resource reported in the beam report. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit controls the activation of the TCI state by a MAC control element (MAC CE) or based on the event-triggered beam report.

[0316] (Note) The following inventions are added with respect to one embodiment of the present disclosure (for MIMO): [Note 1] A terminal having: a transceiver unit that receives a setting for supporting the activation of autonomous transmit setting instruction (TCI) states of the terminal, or reports the capability to support the activation of the TCI states, in a beam report (UEIBR) initiated by the terminal based on a specific event relating to a new beam; and a control unit that, when supporting the activation of the TCI states, controls the activation of the TCI states with respect to the number of supported active TCI states. [Note 2] The terminal according to Note 1, wherein the control unit does not deactivate the active TCI states unless the number of TCI states to be activated exceeds the number of supported active TCI states. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit performs the activation of the TCI states at the timing when the beam report is transmitted, or a predetermined time after the beam report is transmitted. [Note 4] When two activation methods are set simultaneously for the activation of the TCI state, the control unit controls the activation of the TCI state based on the priority of application of the activation methods, as described in any of Notes 1 to 3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0364] The transmitting / receiving unit 120 may transmit a setting in an event-triggered beam report based on a specific event relating to a candidate cell that supports the activation of the terminal's autonomous transmit configuration instruction (TCI) state. The transmitting / receiving unit 120 may receive the capability to support the activation of the TCI state. If the control unit 110 supports the activation of the TCI state, it may control the reception of beam reports associated with the TCI state activated by the terminal, assuming a number of supported active TCI states.

[0365] The transmitting / receiving unit 120 may transmit a setting for supporting the activation of the terminal's autonomous transmit configuration instruction (TCI) states in a terminal-initiated beam report (UEIBR) based on a specific event relating to a new beam. The transmitting / receiving unit 120 may receive the capability to support the activation of the TCI states. If the control unit 110 supports the activation of the TCI states, it may control the reception of beam reports associated with the TCI states activated by the terminal, assuming a number of supported active TCI states.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0386] For a single reporting configuration, the channel measurement resource configuration may include a list of candidate IDs that are associated one-to-one with a list of CSI-RS resource indexes or CSI-RS resource set indexes. Certain constraints may be applied to channel measurement resources or channel measurement resource sets associated with the same candidate cell.

[0387] The interference measurement resource may be the same size as the channel measurement resource, the candidate ID of the channel measurement resource, or the frequency ID of the channel measurement resource. Certain constraints may be applied to the interference measurement resource or set of interference measurement resources associated with the same candidate cell.

[0388] One or more event IDs may be defined for a single reporting setting. Parameters relating to the range of reference signal received power (RSRP) may be used as candidate threshold values. Resource allocation priorities may be applied to MAC CE.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0446] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each of the smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

[0447] In the present disclosure, the base station transmitting information to the terminal may be read as the base station instructing the terminal to perform control / operation based on the information, and vice versa.

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

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

[0450] At least one of the base station and the mobile station may also be called a transmitting device, receiving device, wireless communication device, etc. Note that 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.

[0451] The mobile object refers to an object that can move, and its moving speed is arbitrary, and of course includes the case where the mobile object is stopped. The mobile object includes, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, shovel cars, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, rear cars, rickshaws, ships (ship and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and things mounted on these, and is not limited thereto. Further, the mobile object may be a mobile object that autonomously travels based on an operation command.

[0452] The mobile object may be a vehicle (for example, a car, an airplane, etc.), a mobile object that moves without a driver (for example, a drone, an autonomous driving vehicle, etc.), or a robot (human type or non-human type). Note that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. 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.

[0453] FIG. 11 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, 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.

[0454] The drive unit 41 is composed of, for example, at least one of an engine, a motor, and a hybrid of an engine and a motor. 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 an operation of the steering wheel operated by a user.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0483] In the present disclosure, terms such as "hereinafter", "less than", "more than", "more", "equal to", etc. may be read interchangeably with each other. Also, in the present disclosure, words that mean "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read interchangeably with each other, not limited to the positive, comparative, and superlative degrees. Further, in the present disclosure, words that mean "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read interchangeably with each other, not limited to the positive, comparative, and superlative degrees, as expressions with "the i-th" (where i is an arbitrary integer) (for example, "highest" may be read interchangeably with "the i-th highest").

[0484] In the present disclosure, terms such as "of", "for", "regarding", "related to", "associated with", etc. may be read interchangeably with each other.

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

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

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

Claims

1. A terminal having a transceiver unit that, in a beam report (UEIBR) initiated by the terminal based on a specific event relating to a new beam, receives a setting regarding support for the activation of autonomous transmit configuration instructions (TCI) states of the terminal, or reports the terminal's ability to support the activation of said TCI states; and a control unit that, when supporting the activation of said TCI states, controls the activation of said TCI states based on the number of supported active TCI states.

2. The terminal according to claim 1, wherein the control unit does not deactivate the active TCI states unless the number of TCI states to be activated exceeds the number of supported active TCI states.

3. The terminal according to claim 1, wherein the control unit performs activation of the TCI state at the timing when the beam report is transmitted, or a predetermined time after the beam report is transmitted.

4. When two activation methods are set simultaneously for the activation of the TCI state, the control unit controls the activation of the TCI state based on the priority of application of the activation methods, as described in claim 1.

5. A wireless communication method for a terminal, comprising the steps of: receiving a setting for supporting the activation of autonomous transmit configuration instructions (TCI) states of the terminal, or reporting the terminal's ability to support the activation of said TCI states, in a beam report (UEIBR) initiated by the terminal based on a specific event relating to a new beam; and, if the terminal supports the activation of said TCI states, controlling the activation of said TCI states with respect to the number of supported active TCI states.

6. A base station having: a transceiver unit that transmits a setting for supporting the activation of an autonomous transmit configuration instruction (TCI) state of a terminal, or receives the capability to support the activation of the TCI state, in a terminal-initiated beam report (UEIBR) based on a specific event relating to a new beam; and a control unit that, when supporting the activation of the TCI state, controls the reception of beam reports associated with the TCI state activated by the terminal, assuming a number of supported active TCI states.

Images