Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives an upper layer parameter relating to a unified transmission configuration indication (TCI) state, and receives downlink control information (DCI) triggering an aperiodic channel state information reference signal (A-CSI-RS); and a control unit that, if a parameter indicating following the operation of a default TCI state is not set for each control resource set (CORESET) pool index, determines an indication TCI state to be applied to a resource or a resource set of the A-CSI-RS on the basis of at least one of a frequency range, a report of the buffering capabilities of a plurality of beams for multi-transmission / reception points (TRPs), and an offset from a final symbol of a physical downlink control channel for transmitting the DCI to a start symbol of the A-CSI-RS. According to the one aspect of the present disclosure, the TCI state can be appropriately applied.

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] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

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

[0005] In future wireless communication systems (e.g., NR), it is being considered that user terminals (terminals, user terminals, User Equipment (UE)) will control transmission and reception processing based on information regarding quasi-co-location (QCL) (QCL assumptions / Transmission Configuration Indication (TCI) state / spatial relationship).

[0006] It is being considered to apply the set / activated / indicated TCI state to multiple types of signals (channels / RS). However, there are cases where the method for indicating the TCI state is unclear. If the method for indicating the TCI state is unclear, it may lead to a deterioration in communication quality, a decrease in throughput, etc.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately apply the TCI state.

[0008] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives upper layer parameters related to a unified Transmission Configuration Indication (TCI) state and receives downlink control information (DCI) that triggers an aperiodic channel state information reference signal (A-CSI-RS); and a control unit that, when a parameter indicating that a default TCI state operation is to be followed for each control resource set (CORESET) pool index is not set, determines an indicated TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of a frequency range, a report of buffering capability for multiple beams for multiple transmit / receive points (TRPs), and an offset from the last symbol of a physical downlink control channel that transmits the DCI to the start symbol of the A-CSI-RS.

[0009] According to one aspect of the present disclosure, the TCI state can be appropriately applied.

[0010] 1A and 1B show an example of a unified / common TCI framework. 2A and 2B show an example of a DCI-based TCI status indication. 3 shows an example of an application time of a unified TCI status indication. 4A to 4D are diagrams showing an example of a multi-TRP. 5A to 5C are diagrams showing an example of application of an indicated TCI status. 6 is a diagram showing an example of a correspondence between TCI code points and TCI statuses. 7A to 7C are diagrams showing an example of application of a TCI status to a PDSCH according to embodiment 1-1. 8 is a diagram showing an example of application of a TCI status to a PDSCH according to embodiment 1-2. 9A and 9B are diagrams showing an example of application of a TCI status to an A-CSI-RS according to a second embodiment. 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. 11 is a diagram showing an example of a configuration of a base station according to an embodiment. 12 is a diagram showing an example of a configuration of a user terminal according to an embodiment. 13 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment.

[0011] (TCI, spatial relationship, QCL) In NR, it is considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).

[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0014] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0016] A plurality of types of QCLs (QCL types) may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same.

[0017] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0019] The TCI state may be, for example, information about the QCL between the channel of interest (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 higher layer signaling, physical layer signaling, or a combination thereof.

[0020] The physical layer signaling may be, for example, Downlink Control Information (DCI).

[0021] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0022] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of 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)), and a QCL detection reference signal (also called a QRS).

[0023] An SSB is a signal block including 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 referred to as an SS / PBCH block.

[0024] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0025] Physical Layer Procedures for Data / Antenna Port QCL A UE can configure a list of up to M TCI-State settings in the higher layer parameter PDSCH-Config for PDSCH decoding according to a detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC.

[0026] Each TCI-State includes parameters for configuring a QCL relationship between one or two downlink reference signals and a DMRS port of a PDSCH, a DMRS port of a PDCCH, or a CSI-RS port of a CSI-RS resource, which is configured by the higher layer parameter qcl-Type1 for the first DL RS and the higher layer parameter qcl-Type2 for the second DL RS (if configured).

[0027] In the case of two DL RSs, the multiple QCL types are not the same, regardless of whether the references are to the same DL RS or to different DL RSs. The QCL type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and takes one of the following values: - 'typeA': {Doppler shift, Doppler spread, average delay, delay spread} - 'typeB': {Doppler shift, Doppler spread} - 'typeC': {Doppler shift, average delay} - 'typeD': {Spatial Rx parameter}

[0028] RRC Protocol Specification / RRC IE / TCI-State The TCI-State associates one or two DL Reference Signals (RS) with a corresponding QCL type. If an additional physical cell identifier (PCI) is configured for that RS, it is set to the same value for both DL RSs.

[0029] (Default TCI State / Default Spatial Relationship / Default PL-RS) In Rel. 16, PDSCH may be scheduled with a DCI having a TCI field. The TCI state for PDSCH is indicated by the TCI field. The TCI field of DCI format 1_1 is 3 bits, and the TCI field of DCI format 1_2 is a maximum of 3 bits.

[0030] In RRC connected mode, if the first TCI information element in DCI (higher layer parameter tci-PresentInDCI) is set to "enabled" for a CORESET scheduling a PDSCH, the UE assumes that the TCI field is present in DCI format 1_1 of the PDCCH transmitted in this CORESET.

[0031] Furthermore, if the TCI information element in the second DCI (higher layer parameter tci-PresentInDCI-1-2) for the CORESET scheduling the PDSCH is configured in the UE, the UE assumes that a TCI field with the DCI field size indicated in the TCI information element in the second DCI is present in DCI format 1_2 of the PDSCH transmitted in the CORESET.

[0032] Also, in Rel. 16, PDSCH may be scheduled by DCI without a TCI field. The DCI format of this DCI may be DCI format 1_0 or DCI format 1_1 / 1_2 in the case where the TCI information element in the DCI (the higher layer parameter tci-PresentInDCI or tci-PresentInDCI-1-2) is not configured (enabled). When PDSCH is scheduled by DCI without a TCI field, if the time offset between the reception of the DL DCI (the DCI that schedules the PDSCH (scheduling DCI)) and the corresponding PDSCH (the PDSCH scheduled by this DCI) is equal to or greater than a threshold (timeDurationForQCL), the UE assumes that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption (default TCI state) of CORESET (e.g., the scheduling DCI).

[0033] In RRC connected mode, both when the TCI information element in DCI (higher layer parameters tci-PresentInDCI and tci-PresentInDCI-1-2) is set to "enabled" and when the TCI information element in DCI is not set, if the time offset between the reception of a DL DCI (a DCI scheduling a PDSCH) and the corresponding PDSCH (the PDSCH scheduled by that DCI) is less than a threshold (timeDurationForQCL) (applicability condition, first condition), in the case of non-cross-carrier scheduling, the TCI state of the PDSCH (default TCI state) may be the TCI state of the lowest CORESET ID in the latest slot in the active DL BWP of that CC (for a particular UL signal). Otherwise, the TCI state of the PDSCH (default TCI state) may be the TCI state of the lowest TCI state ID of the PDSCH in the active DL BWP of the scheduled CC.

[0034] In Rel. 15, separate MAC CEs are required for the activation / deactivation of the PUCCH spatial relation and for the activation / deactivation of the SRS spatial relation. The PUSCH spatial relation follows the SRS spatial relation.

[0035] In Rel. 16, at least one of the MAC CE for activation / deactivation of the PUCCH spatial relationship and the MAC CE for activation / deactivation of the SRS spatial relationship may not be used.

[0036] If neither the spatial relationship nor the PL-RS for the PUCCH is configured in FR2 (applicable condition, second condition), default assumptions of the spatial relationship and the PL-RS for the PUCCH (default spatial relationship and default PL-RS) are applied. If neither the spatial relationship nor the PL-RS for the SRS (SRS resource for the SRS or SRS resource corresponding to the SRI in DCI format 0_1 ​​that schedules the PUSCH) is configured in FR2 (applicable condition, second condition), default assumptions of the spatial relationship and the PL-RS for the PUSCH and SRS scheduled by DCI format 0_1 ​​(default spatial relationship and default PL-RS) are applied.

[0037] If a CORESET is configured in the active DL BWP on that CC (if applicable), the default spatial relationship and default PL-RS may be the TCI state or QCL assumption of the CORESET with the lowest CORESET ID in that active DL BWP. If a CORESET is not configured in the active DL BWP on that CC, the default spatial relationship and default PL-RS may be the active TCI state with the lowest PDSCH ID in that active DL BWP.

[0038] In Rel. 15, the spatial relationship of the PUCCH scheduled by DCI format 0_0 follows the spatial relationship of the PUCCH resource with the lowest PUCCH resource ID among the active spatial relationships of the PUCCHs on the same CC. The network needs to update the PUCCH spatial relationship on all SCells, even if no PUCCH is transmitted on the SCell.

[0039] In Rel. 16, PUCCH configuration is not required for a PUSCH scheduled by DCI format 0_0. If there is no active PUCCH spatial relationship or no PUCCH resource on the active UL BWP in the CC for a PUSCH scheduled by DCI format 0_0 (applicable condition, second condition), the default spatial relationship and default PL-RS are applied to the PUSCH.

[0040] The application conditions for the default spatial relationship / default PL-RS for SRS may include a default beam path loss enable information element for SRS (upper layer parameter enableDefaultBeamPlForSRS) being set to valid. The application conditions for the default spatial relationship / default PL-RS for PUCCH may include a default beam path loss enable information element for PUCCH (upper layer parameter enableDefaultBeamPlForPUCCH) being set to valid. The application conditions for the default spatial relationship / default PL-RS for PUSCH scheduled by DCI format 0_0 may include a default beam path loss enable information element for PUSCH scheduled by DCI format 0_0 (upper layer parameter enableDefaultBeamPlForPUSCH0_0) being set to valid.

[0041] In Rel. 16, if an RRC parameter (a parameter enabling a default beam PL for PUCCH (enableDefaultBeamPL-ForPUCCH), a parameter enabling a default beam PL for PUSCH (enableDefaultBeamPL-ForPUSCH0_0), or a parameter enabling a default beam PL for SRS (enableDefaultBeamPL-ForSRS)) is configured for a UE and a spatial relationship or PL-RS is not configured, the UE applies the default spatial relationship / PL-RS.

[0042] This threshold may also be called time duration for QCL, "timeDurationForQCL", "Threshold", "Threshold for offset between a DCI indicating a TCI state and a PDSCH scheduled by the DCI", "Threshold-Sched-Offset", "beamSwitchTiming", schedule offset threshold, scheduling offset threshold, etc. This threshold may be reported by the UE as UE capability (per subcarrier spacing).

[0043] If the offset (scheduling offset) between the reception of a DL DCI and the corresponding PDSCH is smaller than a threshold timeDurationForQCL, and at least one TCI state configured for the serving cell of the scheduled PDSCH includes "QCL type D", and the UE configures the two default TCI enable information element (enableTwoDefaultTCIStates-r16), and at least one TCI codepoint (the codepoint of the TCI field in the DL DCI) indicates two TCI states, the UE assumes that the PDSCH or the DMRS port of the PDSCH transmission occasion of the serving cell is quasi-colocated with the RS for the QCL parameters associated with the two TCI states corresponding to the lowest codepoints among the TCI codepoints containing two different TCI states (two-default QCL assumption decision rule). The 2 default TCI enable information element indicates that Rel. 16 operation of the 2 default TCI states for the PDSCH is enabled when at least one TCI codepoint is mapped to 2 TCI states.

[0044] As the default TCI state for PDSCH in Rel. 15 / 16, the default TCI state for single TRP, the default TCI state for multi-TRP based on multi-DCI, and the default TCI state for multi-TRP based on single DCI are specified.

[0045] As default TCI states for aperiodic CSI-RS (A (aperiodic)-CSI-RS) in Rel. 15 / 16, the default TCI state for single TRP, the default TCI state for multi-TRP based on multi-DCI, and the default TCI state for multi-TRP based on single DCI are specified.

[0046] In Rel. 15 / 16, the default spatial relationship and default PL-RS for each of PUSCH / PUCCH / SRS are specified.

[0047] (Unified / Common TCI Framework) The unified TCI framework allows multiple types of channels / RSs (UL / DL) to be controlled by a common framework. The unified TCI framework does not specify TCI states or spatial relationships for each channel as in Rel. 15. Instead, it may specify a common beam (common TCI state) and apply it to all UL and DL channels, or it may apply a common beam for UL to all UL channels and a common beam for DL ​​to all DL channels.

[0048] One common beam for both DL and UL, or one common beam for DL ​​and one common beam for UL (two common beams overall) are considered.

[0049] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may assume different TCI states for UL and DL (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

[0050] The default beams for UL and DL may be aligned via MAC CE based beam management (MAC CE level beam indication). The default TCI state of the PDSCH may be updated to align with the default UL beam (spatial relationship).

[0051] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool for both UL and DL (joint common TCI pool, joint TCI pool, set). X (>1) TCI states may be activated by the MAC CE. The UL / DL DCI may select one from the X active TCI states. The selected TCI state may apply to both UL and DL channels / RS.

[0052] The TCI pool (set) may be multiple TCI states configured by RRC parameters, or multiple TCI states (active TCI states, active TCI pools, sets) activated by MAC CE among the multiple TCI states configured by RRC parameters. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be configured as the QCL type A / D RS.

[0053] The number of TCI states corresponding to each of one or more TRPs may be specified. For example, the number N (≧1) of TCI states applied to UL channels / RSs (UL TCI states) and the number M (≧1) of TCI states applied to DL channels / RSs (DL TCI states) may be specified. At least one of N and M may be notified / configured / instructed to the UE via higher layer signaling / physical layer signaling.

[0054] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / indicated to the UE. Also, when N=X (X is any integer) and M=Y (Y may be any integer, Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (i.e., separate TCI states) (corresponding to Y TRPs) are notified / configured / indicated to the UE.

[0055] For example, when N=M=1 is written, this may mean that a TCI state common to one UL and DL for a single TRP is notified / configured / indicated to the UE (joint TCI state for a single TRP).

[0056] Also, for example, when N=1 and M=1 are written, this may mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / configured / instructed to the UE (separate TCI states for a single TRP).

[0057] Also, for example, when N=M=2 is written, this may mean that a TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs is notified / configured / instructed to the UE (joint TCI state for multiple TRPs).

[0058] Also, for example, when N=2 and M=2, it may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified / configured / instructed to the UE (separate TCI states for multiple TRPs).

[0059] In the above example, the values ​​of N and M are 1 or 2, but the values ​​of N and M may be 3 or more, and N and M may be different.

[0060] It is being considered that N=M=1 will be supported in Rel. 17. It is being considered that other cases will be supported in Rel. 18 and later.

[0061] In the example of Figure 1A, RRC parameters (information elements) configure multiple TCI states for both DL and UL. The MAC CE may activate multiple TCI states from the configured multiple TCI states. A DCI may indicate one of the activated multiple TCI states. The DCI may be a UL / DL DCI. The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both UL TCI and DL TCI.

[0062] In the example of this figure, a point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL respectively.

[0063] At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).

[0064] In the present disclosure, higher layer parameters (RRC parameters) for setting multiple TCI states may be referred to as configuration information for setting multiple TCI states, or simply as "configuration information." Also, in the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information instructing one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information."

[0065] In the example of Figure 1B, the RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for each of the UL and DL may be configured / activated.

[0066] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) DL channels / RSs. The DL channels may be PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the TCI state behavior (TCI framework) of Rel. 16. The UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate UL TCI and DL DCI separately.

[0067] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.

[0068] [Physical Layer Procedures for Data / Antenna Port QCL] In PDSCH-Config, the UE can configure a list of up to 128 DLorJointTCIState configurations to provide reference signals for PDSCH DMRS and PDCCH DMRS and CSI-RS within a CC, and also to provide a reference for determining the UL TX (Transmit) spatial filter for PUSCH and PUCCH resources and SRS within a CC based on dynamic and configuration grants, if available.

[0069] If there is no DLorJointTCIState or UL-TCIState (UL TCI state) configuration in the BWP in that CC, the UE may apply the DLorJointTCIState or UL-TCIState configuration from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState configured in any CC in the same band, it does not assume that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band are configured, except for SpatialRelationInfoPos (spatial relation information for position). The UE assumes that if the UE has TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE does not have DLorJointTCIState or UL-TCIState configured in any CC in that CC list.

[0070] The UE receives an activation command used to map up to eight TCI states and / or TCI state pairs, with one TCI state for DL ​​channels / signals and one TCI state for UL channels / signals, to codepoints in the DCI field 'Transmission Configuration Indication' (TCI) for one CC / DL BWP or set of CC / DL BWPs, if available. If a set of TCI state IDs is activated for a set of CC / DL BWPs, and also for one CC / DL BWP, if available, the same set of TCI state IDs applies to all DL and / or UL BWPs within the indicated CC, where the applicable list of CCs is determined by the CC indicated in the activation command. If the activation command maps DLorJointTCIState and / or UL-TCIState to only one TCI codepoint, the UE applies the indicated DLorJointTCIState and / or UL-TCIState to one or a set of CC / DL BWPs, and if the indicated mapping to one single TCI codepoint applies, the UE applies the indicated DLorJointTCIState and / or UL-TCIState to one or a set of CC / DL BWPs.

[0071] If the bwp-id or cell for a QCL type A / D source RS in the QCL-Info of a TCI state with DLorJointTCIState set is not set, the UE shall assume that the QCL type A / D source RS is set in the CC / DL BWP to which the TCI state applies.

[0072] (TCI State Indication) The Rel. 17 unified TCI framework supports the following modes 1 to 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment [Mode 3] DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0073] A UE with a TCI state configured and activated with a Rel. 17 TCI State ID (e.g., tci-StateId_r17) receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel. 17 TCI State ID for one CC, or receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel. 17 TCI State ID for all CCs in the same CC list as the CC list configured by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). DCI format 1_1 / 1_2 may or may not be accompanied by a DL assignment if one is available.

[0074] If DCI format 1_1 / 1_2 does not carry a DL assignment, the UE can assume (verify) the following for that DCI: - the CS-RNTI is used to scramble the CRC for the DCI; - the values ​​of the following DCI fields (special fields) are set as follows: - the redundancy version (RV) field is all '1's; - the modulation and coding scheme (MCS) field is all '1's; - the new data indicator (NDI) field is 0; - the frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, or all '1's for FDRA type 1, or all '0's for Dynamic Switch (similar to PDCCH validation for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).

[0075] Note that the DCI in the above-mentioned mode 2 / mode 3 may be referred to as beam instruction DCI.

[0076] In Rel. 15 / 16, if a UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. A similar behavior is considered for the relationship between support for Rel. 17 TCI states and the interpretation of the TCI field. It is considered that if a UE is configured with Rel. 17 TCI states, the TCI field will always be present in DCI format 1_1 / 1_2, and if the UE does not support TCI updates via DCI, the UE will ignore the TCI field.

[0077] In Rel. 15 / 16, whether or not a TCI field is present (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0078] The TCI field in DCI format 1_1 is 0-bit if the higher layer parameter tci-PresentInDCI is not enabled, and 3-bit otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following behavior: [Action] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.

[0079] The TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions. [Operation] If the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used for the PDCCH carrying that DCI format 1_2, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.

[0080] 2A shows an example of a DCI-based joint DL / UL TCI status indication, in which a TCI status ID indicating the joint DL / UL TCI status is associated with a value of the TCI field for the joint DL / UL TCI status indication.

[0081] 2B shows an example of DCI-based separate DL / UL TCI status indication. At least one TCI status ID, indicating a DL-only TCI status or indicating a UL-only TCI status, is associated with a value of the TCI field for the separate DL / UL TCI status indication. In this example, TCI field values ​​000 to 001 are associated with only one TCI status ID for DL, TCI field values ​​010 to 011 are associated with only one TCI status ID for UL, and TCI field values ​​100 to 111 are associated with both one TCI status ID for DL ​​and one TCI status ID for UL.

[0082] (Indicated TCI State / Configured TCI State) For Rel. 17 TCI states, unified / common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC (indicated Rel. 17 TCI state).

[0083] In the present disclosure, the terms indicated Rel. 17 TCI state, indicated TCI state, unified / common TCI state, TCI state applicable to multiple types of signals (channels / RS), and TCI state for multiple types of signals (channels / RS) may be interpreted interchangeably.

[0084] The indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may be referred to as the indicated TCI state or the unified TCI state.

[0085] Regarding the Rel. 17 TCI state, a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using (Rel. 17) MAC CE / RRC (configured Rel. 17 TCI state). In this disclosure, the terms configured Rel. 17 TCI state, configured TCI state, TCI state other than the unified TCI state, and TCI state applied to a specific type of signal (channel / RS) may be interpreted interchangeably.

[0086] The configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured Rel. 17 TCI state may be configured by RRC / MAC CE per CORESET / per resource / per resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) is updated.

[0087] It is being considered that the indicated Rel. 17 TCI state will be applied to UE-specific channels / signals (RS), and that the UE will be notified by higher layer signaling (RRC signaling) whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels / signals.

[0088] It is being considered that the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15 / 16. It is also being considered that the configured Rel. 17 TCI state will be configured / instructed per CORESET / per resource / per resource set using RRC / MAC CE. It is also being considered that the UE will determine the configuration / instruction based on specific parameters.

[0089] It is considered that the UE updates the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated, the UE may not update the configured TCI state. It is also considered that the UE may determine whether to update the configured TCI state based on a specific parameter.

[0090] Furthermore, regarding the PDCCH / PDSCH, it is being considered to use higher layer signaling (RRC / MAC CE) to switch whether the indication Rel. 17 TCI state is applied or not (the configured Rel. 17 TCI state is applied, or a TCI state configured separately from the indication Rel. 17 TCI state is applied).

[0091] Regarding intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH, and a non-UE-specific CORESET and its associated PDSCH.

[0092] Also, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH.

[0093] In Rel. 15, whether to indicate the TCI state for CORESET #0 was up to the implementation of the base station. In Rel. 15, for CORESET #0 for which a TCI state is indicated, the indicated TCI state is applied. For CORESET #0 for which a TCI state is not indicated, the SSB and QCL selected at the time of the latest (most recent) PRACH transmission are applied.

[0094] In the unified TCI state framework for Rel. 17 and later, the TCI state for CORESET #0 is being considered.

[0095] For example, in the unified TCI state framework for Rel. 17 and later, whether or not to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication in CORESET #0 is configured by RRC for each CORESET, and if not, the legacy MAC CE / RACH signaling mechanism may be used.

[0096] Note that the CSI-RS associated with the Rel. 17 TCI state applied to CORESET #0 may be QCL'd with the SSB associated with the serving cell PCI (physical cell ID) (similar to Rel. 15).

[0097] For CORESET #0, a CORESET with a common search space (CSS), and a CORESET with a CSS and a UE-specific search space (USS), whether to follow the Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the Rel. 17 TCI state is not configured to be followed for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.

[0098] For non-UE-dedicated channels / RSs (except CORESET), whether to follow the indicated Rel. 17 TCI state may be configured by an RRC parameter for each channel / resource / resource set. If the indicated Rel. 17 TCI state is not configured for that channel / resource / resource set, the configured Rel. 17 TCI state may apply to that channel / resource / resource set.

[0099] (Channels / RSs to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

[0100] [PDCCH] - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state always applies. - For CORESETs with index other than 0 and at least CSS type other than 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0101] [PDSCH] - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in CSS), the indicated TCI state may apply if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH). Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

[0102] [CSI-RS] For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

[0103] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

[0104] [PUSCH] - For dynamic / configured grant PUSCH, the indication TCI state always applies.

[0105] [SRS] - When the SRS resource set for the A-SRS used for beam management and the A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state is applied. For other SRSs, the configured TCI state in the SRS resource set is applied.

[0106] (Beam Application Time (BAT)) In DCI-based beam indication in Rel. 17, the following considerations 1 and 2 are considered regarding the application time of the beam / unified TCI status indication (beam application time (BAT) conditions).

[0107] [Consideration 1] It is considered that the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the acknowledgement (ACK) for the joint or separate DL / UL beam indication. It is considered that the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the ACK / negative acknowledgement (NACK) for the joint or separate DL / UL beam indication. Y symbols may be set by the base station based on the UE capabilities reported by the UE. The UE capabilities may be reported in symbol units.

[0108] In the example of Figure 3, the ACK may be an ACK for the PDSCH scheduled by the beam instruction DCI. In this example, the PDSCH may not be transmitted. In this case, the ACK may be an ACK for the beam instruction DCI.

[0109] For DCI-based beam direction in Rel. 17, it is considered that at least one Y symbol per BWP / CC is configured in the UE.

[0110] If the SCS differs between multiple CCs, the value of the Y symbol also differs, and therefore the application time may differ between multiple CCs.

[0111] [Consideration 2] For the CA case, the timing / BAT of applying the beam instruction may follow any of the following options 1 to 3: [Option 1] Both the first slot and Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam instruction is applied. [Option 2] Both the first slot and Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam instruction is applied and the UL carrier carrying the ACK. [Option 3] Both the first slot and Y symbol are determined on the UL carrier carrying the ACK.

[0112] As part of the CC simultaneous beam update function of Rel. 17, the sharing of beams among multiple CCs in CA is being considered. According to Study 2, the application time will be shared among multiple CCs.

[0113] The application time (Y symbols) of beam direction for CA may be determined on the carrier with the smallest SCS among the carriers to which beam direction applies. Rel. 17 MAC CE-based beam direction (when only a single TCI codepoint is activated) may follow the Rel. 16 application timeline for MAC CE activation.

[0114] Based on these considerations, the following behavior is considered to be specified in the specification: [Behavior] When a UE transmits the last symbol of a PUCCH with HARQ-ACK information corresponding to a DCI carrying a TCI state indication, the indicated TCI state with a Rel. 17 TCI state may start to apply from the first slot that is at least Y symbols after the last symbol of the PUCCH. Y may be a higher layer parameter (e.g., BeamAppTime_r17[symbols]). Both the first slot and Y symbols may be determined on the carrier with the smallest SCS among the carriers to which the beam indication applies. At a given time, the UE may assume one indicated TCI state with a Rel. 17 TCI state for both DL and UL, or one indicated TCI state with a Rel. 17 TCI state for UL (separate from DL).

[0115] X [ms] may be used instead of Y [symbols].

[0116] Regarding the application time, it is considered that the UE reports at least one of the following UE capabilities 1 and 2: [UE capability 1] Minimum application time per SCS (minimum of Y symbols between the last symbol of the PUCCH carrying ACK and the first slot in which the beam is applied). [UE capability 2] Minimum time gap between the last symbol of the beam indication PDCCH (DCI) and the first slot in which the beam is applied. The gap between the last symbol of the beam indication PDCCH (DCI) and the first slot in which the beam is applied may satisfy the UE capability (minimum time gap).

[0117] UE capability 2 may be an existing UE capability (eg, timeDurationForQCL).

[0118] The relationship between the beam indication and the channel / RS to which the beam is applied may satisfy at least one of UE capabilities 1 and 2.

[0119] Regarding the application time, the parameter set by the base station (eg, BeamAppTime_r17) may be an optional field.

[0120] (Multi-TRP) In NR, one or more transmission / reception points (Transmission / Reception Points (TRP)) (multi-TRP) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs.

[0121] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs, which may be physical cell IDs (e.g., PCIs) or virtual cell IDs.

[0122] 4A-4D illustrate an example of a multi-TRP scenario, assuming, but not limited to, that each TRP is capable of transmitting four different beams.

[0123] 4A shows an example of a case where only one TRP (TRP1 in this example) of the multi-TRPs transmits to the UE (this may be referred to as single mode, single-TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0124] In this disclosure, single-TRP mode may refer to a mode in which multi-TRP (mode) is not set.

[0125] 4B shows an example of a case where only one TRP (TRP1 in this example) transmits control signals to the UE, and the multi-TRP transmits data signals (also called single master mode). The UE receives each PDSCH transmitted from the multi-TRP based on a single Downlink Control Information (DCI).

[0126] 4C shows an example of a case where each of the multi-TRPs transmits a part of the control signal to the UE, and the multi-TRPs transmit data signals (this may be called a master-slave mode). Part 1 of the control signal (DCI) may be transmitted on TRP1, and Part 2 of the control signal (DCI) may be transmitted on TRP2. Part 2 of the control signal may depend on Part 1. The UE receives each PDSCH transmitted from the multi-TRP based on these parts of the DCI.

[0127] 4D shows an example of a multi-TRP mode in which each TRP transmits a separate control signal to the UE, and the multi-TRP transmits a data signal (also referred to as a multi-master mode). A first control signal (DCI) may be transmitted from TRP1, and a second control signal (DCI) may be transmitted from TRP2. The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0128] When multiple PDSCHs from multiple TRPs as shown in Figure 4B (which may also be referred to as multiple PDSCHs) are scheduled using one DCI, the DCI may be referred to as a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from multiple TRPs as shown in Figure 4D are scheduled using multiple DCIs, these multiple DCIs may be referred to as multiple DCIs (M-DCI, multiple PDCCHs).

[0129] Each TRP in a multi-TRP may transmit a different transport block (TB) / code word (CW) / different layer, or each TRP in a multi-TRP may transmit the same TB / CW / layer.

[0130] Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and layer-maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding. TRP2 modulates and layer-maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

[0131] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in time and / or frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in time and / or frequency resources.

[0132] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (QCL). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0133] In URLLC for multi-TRP, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multi-TRP is supported. Repetition schemes (URLLC schemes, e.g., Schemes 1, 2a, 2b, 3, and 4) across multi-TRP in the frequency domain, layer (spatial) domain, or time domain are supported. In Scheme 1, multiple PDSCHs from multi-TRP are space division multiplexed (SDM). In Schemes 2a and 2b, PDSCHs from multi-TRP are frequency division multiplexed (FDM). In Scheme 2a, the redundancy version (RV) is the same for multi-TRP. In Scheme 2b, the RVs for multi-TRP may be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0134] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0135] NCJT using multiple TRPs / panels may use a high rank. To support ideal and non-ideal backhaul between multiple TRPs, both single DCI (single PDCCH, e.g., FIG. 4B) and multiple DCI (multiple PDCCH, e.g., FIG. 4D) may be supported. For both single DCI and multiple DCI, the maximum number of TRPs may be two.

[0136] For single PDCCH design (mainly for ideal backhaul), TCI extension is being considered. Each TCI codepoint in the DCI may correspond to one or two TCI states. The TCI field size may be the same as that of Rel. 15.

[0137] For PDCCH / CORESET specified in Rel. 15, one TCI state without CORESETPoolIndex (also referred to as TRP Info) is set to one CORESET.

[0138] Regarding the PDCCH / CORESET enhancements specified in Rel. 16, in multi-TRP based on multi-DCI, a CORESET pool index is configured for each CORESET.

[0139] (TCI Selection Field) A specific field (new DCI field) may be included in a DCI format for scheduling / activating / triggering DL channels / signals (for example, DCI format 1_1 / 1-2 (which may be referred to as DL DCI)).

[0140] The specific field may be a field indicating that one or more (e.g., both / two) indicated TCI states (joint / DL TCI states) are to be applied to the DL channel / signal to be scheduled / activated / triggered. In other words, the specific field may be a field indicating the number / order of the indicated TCI states to be applied.

[0141] The particular field may be represented by a particular number of bits (for example, 2 bits).

[0142] In the present disclosure, this particular field may be referred to as a TCI selection field, but the name is not limited to this.

[0143] If the offset (hereinafter, this may be referred to as a scheduling offset, a triggering offset, etc.) between the reception of the DL DCI and the reception of the corresponding DL channel / signal is smaller than a certain threshold, the UE may buffer the received signal using the indicated TCI state (joint / DL TCI state).

[0144] When a DL channel / signal is scheduled / triggered by a first DCI format (e.g., DCI format 1_0), if a single frequency network (SFN) scheme (e.g., an SFN scheme for PDSCH (RRC parameter sfnSchemePdsch)) is configured, multiple (e.g., both / two) indicated TCI states (joint / DL TCI states) may be applied to the DL channel / signal. Otherwise, one (e.g., first) indicated TCI state (joint / DL TCI state) may be applied to the DL channel / signal.

[0145] If a DL channel / signal is scheduled by a second DCI format (e.g., DCI format 1_1 / 1_2) that does not include a specific field, multiple (e.g., both / two) indicated TCI states (joint / DL TCI states) may be applied to the DL channel / signal.

[0146] 5A-5C are diagrams illustrating other examples of application of the indicated TCI states. In the example shown in FIG. 5A, two indicated TCI states (TCI state #1 as the first TCI state and TCI state #2 as the second TCI state) are indicated to the UE.

[0147] In the example shown in Figure 5B, the DL DCI includes a field (TCI selection field) indicating the number / order of the indicated TCI states to be applied. Code point "00" in this field indicates that the first indicated TCI state is applied. Code point "01" in this field indicates that the second indicated TCI state is applied. Code point "10" in this field indicates that both the first indicated TCI state and the second indicated TCI state are applied. Code point "11" in this field is unused.

[0148] Figure 5C shows an example where PDSCH is scheduled by DL DCI, which includes a TCI selection field indicating codepoint "00", so that the UE applies TCI state #1 for PDSCH reception (see Figure 5C).

[0149] If the offset between the reception of the scheduling / triggering DL DCI and the reception of the scheduled / triggered DL channel / signal is greater than (or equal to or greater than) a certain threshold, a certain DCI field (e.g., a TCI selection field) may indicate the channel / signal to which the indicated TCI state is to be applied. In this case, the operation may be at least one of the following operation 1 and operation 2.

[0150] The specific threshold may be, for example, at least one of an existing threshold (defined up to Rel. 15 / 16) and a value based on RRC parameters / UE capability information defined in Rel. 17 / 18 or later.

[0151] The existing threshold may be, for example, a value based on UE capability information specified in Rel. 15 in the second frequency range (e.g., FR2).

[0152] In a first frequency range (eg, FR1), the particular DCI field may always be included in the DCI.

[0153] [Operation 1] A specific field (eg, a TCI selection field) may be included in the DL DCI if a specific RRC parameter is configured.

[0154] When the code point of a specific field included in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a first value (e.g., “00”), the UE may apply a specific indicated TCI state (e.g., a first indicated (joint / DL) TCI state) to multiple (e.g., all) DL channels / signals (e.g., PDSCH DMRS ports of multiple (all) PDSCH transmission opportunities) scheduled / triggered by the DCI.

[0155] When the code point of a specific field included in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a second value (e.g., “01”), the UE may apply a specific indicated TCI state (e.g., a second indicated (joint / DL) TCI state) to multiple (e.g., all) DL channels / signals (e.g., PDSCH DMRS ports of multiple (all) PDSCH transmission opportunities) scheduled / triggered by the DCI.

[0156] When the code point of a specific field included in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a third value (e.g., “10”), the UE may apply multiple indication TCI states (e.g., both the first indication (joint / DL) TCI state and the second indication (joint / DL) TCI state) to reception of a DL channel / signal scheduled / triggered by the DCI.

[0157] For example, when the code point of a specific field included in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a third value (e.g., "10"), the multiple indicated TCI states may be applied in a first order (e.g., the first indicated TCI state, then the second indicated TCI state).

[0158] The above operation 1 may be applied in a specific condition, for example, if (if applicable) the offset between at least the reception of the scheduling / triggering DL DCI and the reception of the scheduled / triggered DL channel / signal is greater than or equal to a specific threshold.

[0159] [Operation 2] A DL channel / signal may be scheduled / triggered by a DL DCI that does not include a specific field (e.g., a TCI selection field). The UE may apply one or more specific indication TCI states to the DL channel / signal.

[0160] In this case, the UE may be configured to apply one or more indicated TCI states using higher layer signaling (RRC / MAC CE) (options 0-1). For example, the UE may be configured using specific RRC parameters to apply either a first indicated TCI state, a second indicated TCI state, or both to reception of DL channels / signals.

[0161] Also in this case, the UE may decide to apply the first (or second) indicated TCI state to the reception of the DL channel / signal (option 0-2).

[0162] Also in this case, the UE may decide to apply multiple indicated TCI states (e.g., both the first indicated TCI state and the second indicated TCI state) to reception of the DL channel / signal (options 0-3).

[0163] In this case, the UE may also decide to apply the same indicated TCI state to the DL channel / signal as the indicated TCI state of the PDCCH corresponding to the DL DCI that scheduled the DL channel / signal (options 0-4).

[0164] Also in this case, the UE may apply an indicated TCI state for one or more TRPs, which may be determined using the existing TCI fields (options 0-5).

[0165] The above operation 2 may be applied under certain conditions, for example, when (if applicable) the offset between at least the reception of the scheduling / triggering DL DCI and the reception of the scheduled / triggered DL channel / signal is greater than or equal to a certain threshold (e.g., "timeDurationForQCL").

[0166] (Analysis) Incidentally, in Rel. 18 and later, a case is being considered in which a multi-TRP (for example, a single DCI-based multi-TRP (single DCI multi-TRP)) is configured and a unified TCI state is applied.

[0167] Before decoding the DCI, the UE cannot know whether a DL signal / channel (eg, PDSCH / A-CSI-RS) is scheduled / triggered or not.

[0168] Therefore, for periods less than the threshold for the offset, the UE needs to buffer the received signal using a particular beam.

[0169] However, although a basic UE can only buffer received signals using two default beams, it is considered that buffering with two beams is an optional UE capability, which may be for single DCI multi-TRP DL signals / channels.

[0170] In Rel. 18 and later, it is considered that the TCI state activation command (MAC CE) will indicate whether each joint / separate (DL / UL) TCI state mapped to a TCI code point is the first or second joint / separate (DL / UL) TCI state (see Figure 6).

[0171] It is considered that the MAC CE activates a set (full set / subset) of joint TCI states ({first joint TCI, second joint TCI}) / separate TCI states ({first UL TCI, second UL TCI, first DL TCI, second DL TCI}) for each TCI codepoint.

[0172] If the TCI field indicates a subset of the TCI states, the TCI states for the other set that are not indicated may not be updated. For example, if the TCI field indicates a subset of the TCI states, two indicated TCI states may be maintained at all times.

[0173] For example, when one or more TCI states correspond to a TCI codepoint, the UE may maintain all sets of joint TCI states ({first joint TCI, second joint TCI}) / separate TCI states ({first UL TCI, second UL TCI, first DL TCI, second DL TCI}) for each TCI codepoint, regardless of the codepoint indicated by the DCI (TCI field). In this case, which TCI state applies to each channel / signal may be based on either the indicated TCI state or the maintained TCI state.

[0174] Also, for the application of TCI states to the A-CSI-RS in Rel. 18 and later, different DCI code points in the CSI request field may indicate the first / second indicated TCI state of the A-CSI-RS.

[0175] The NW may be able to set the association between the first and second TCI states for each CSI-RS resource or for each CSI-RS resource set.

[0176] Regarding the application of TCI states to PDSCH in Rel. 18 and later, if the DL DCI (e.g., DCI format 1_1 / 1_2) does not include a TCI selection field, it is considered that both of the indicated TCI states are applied. If the UE does not support the buffering capability using two beams in FR2, a specific beam (default beam) may be used.

[0177] The (presence of) the TCI selection field may be configured using RRC signaling per (configuration of) the BWP.

[0178] If the UE does not support buffering capability with two beams in FR2, the default beam for PDSCH may be the first joint indication / DL TCI state. The default beam for A-CSI-RS may be the same as the default beam for PDSCH or may be determined independently.

[0179] It is also possible that a multi-DCI based multi-TRP is configured and a unified TCI state is used.

[0180] The UE may be instructed based on the TCI field in the DL DCI (e.g., DCI format 1_1 / 1_2) to indicate the indicated TCI state corresponding to the CORESET pool index associated with the DCI.

[0181] Beam direction across TRPs (cross-TRP beam direction) may not be supported.

[0182] Explicit / implicit association of CORESET pool index with channel / signal is contemplated, e.g., inclusion of CORESET pool index in MAC CE for indication of TCI status.

[0183] The UE may apply the indicated TCI state associated with the CORESE pool index to the PDSCH / PDCCH.

[0184] For example, the UE may apply a CORESET pool index value specific indication (joint / DL) TCI state to PDCCHs on a CORESET associated with the same CORESET pool index value.

[0185] For example, the UE may apply an indication (joint / DL) TCI state specific to a CORESET pool index value to PDSCHs scheduled / activated by PDCCHs on a CORESET associated with the same CORESET pool index value.

[0186] The UE may receive an RRC parameter indicating an association between the indicated TCI state and a CSI-RS resource set / resource, the RRC parameter may indicate first or second, corresponding to values ​​0 and 1 of the CORESET pool index, respectively, and the UE may apply the indicated TCI state corresponding to the CORESET pool index to the A-CSI-RS based on the RRC parameter.

[0187] When the triggering offset is smaller than a certain threshold and the UE does not support buffering capability using two default beams, the TCI state that the UE applies to the A-CSI-RS has not been studied.

[0188] Also, in the unified TCI state introduced in Rel. 17, if the indicated TCI state is associated with the serving cell, the indicated TCI state always applies, otherwise the default QCL / TCI state introduced in Rel. 15 applies.

[0189] This is because the UE cannot receive the UE-common PDCCH from a non-serving cell. Note that always applying the indication TCI state to receive the PDSCH may mean that the UE receives the UE-common PDSCH from a non-serving cell in the inter-cell case.

[0190] In addition, in the unified TCI state in Rel. 18, support for inter-cell multi-TRP is being considered.

[0191] As described above, the application of the unified TCI state when using multi-TRP (including inter-cell multi-TRP) introduced in Rel. 18 and later has not been sufficiently studied, particularly in the case of PDSCH using multi-DCI and A-CSI-RS using multi-DCI / single DCI.

[0192] For example, if existing specifications (e.g., up to Rel. 17) are applied to the unified TCI state when multiple TRPs are used, for DL ​​channels / signals (e.g., PDSCH / A-CSI-RS) with scheduling offsets smaller than a certain threshold, all UEs need to buffer two default QCLs to receive PDSCHs associated with two different CORESET pool indices, which exceeds the basic UE's ability to buffer received signals using one beam.

[0193] In this way, if the TCI state to be applied by the UE is not sufficiently considered, the TCI state cannot be applied appropriately, which may result in a decrease in communication quality, a decrease in throughput, etc.

[0194] Therefore, the present inventors have focused on these problems, studied the operation in the unified TCI state, and conceived one aspect of the present embodiment.

[0195] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0196] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0197] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0198] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0199] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0200] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0201] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0202] In the present disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be read interchangeably.

[0203] In the present disclosure, a single DCI, a single PDCCH, multiple TRPs based on a single DCI, activating two TCI states on at least one TCI code point, mapping at least one code point of a TCI field to two TCI states, and setting a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a specific channel / CORESET may be read interchangeably.

[0204] In the present disclosure, the terms single TRP, channel / signal using single TRP, channel using one TCI state / spatial relationship, multi-TRP not enabled by RRC / DCI, multiple TCI states / spatial relationships not enabled by RRC / DCI, a CORESETPoolIndex value of 1 not set for any CORESET, and no code point in the TCI field mapped to two TCI states may be read interchangeably.

[0205] In the present disclosure, TRP #1 (first TRP) may correspond to CORESET pool index = 0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP #2 (second TRP) TRP #1 (first TRP) may correspond to CORESET pool index = 1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field.

[0206] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.

[0207] In the present disclosure, the beam indication DCI, the beam indication MAC CE, and the beam indication DCI / MAC CE may be interchangeable. In other words, an indication regarding the indication TCI state to the UE may be made using at least one of the DCI and the MAC CE.

[0208] In the present disclosure, the terms channel, signal, and channel / signal may be interchangeable. In the present disclosure, the terms DL channel, DL signal, DL signal / channel, transmission / reception of DL signal / channel, DL reception, and DL transmission may be interchangeable. In the present disclosure, the terms UL channel, UL signal, UL signal / channel, transmission / reception of UL signal / channel, UL reception, and UL transmission may be interchangeable.

[0209] In this disclosure, applying a TCI state / QCL assumption to each channel / signal / resource may mean applying the TCI state / QCL assumption to transmission and reception of each channel / signal / resource.

[0210] In the present disclosure, the first TRP may correspond to the first TCI state (the first indicated TCI state). In the present disclosure, the second TRP may correspond to the second TCI state (the second indicated TCI state). In the present disclosure, the nth TRP may correspond to the nth TCI state (the nth indicated TCI state).

[0211] In the present disclosure, a first CORESET pool index value (e.g., 0), a first TRP index value (e.g., 1), and a first TCI state (first DL / UL (joint / separate) TCI state) may correspond to each other. In the present disclosure, a second CORESET pool index value (e.g., 1), a second TRP index value (e.g., 2), and a second TCI state (second DL / UL (joint / separate) TCI state) may correspond to each other.

[0212] In the following embodiments of the present disclosure, the application of multiple TCI states in transmission and reception using multiple TRPs will be mainly described with respect to a method for two TRPs (i.e., when at least one of N and M is 2), but the number of TRPs may be three or more (multiple), and each embodiment may be applied to correspond to the number of TRPs. In other words, at least one of N and M may be a number greater than 2.

[0213] In the present disclosure, the terms schedule, trigger, and activate may be read interchangeably.

[0214] Each of the following embodiments of the present disclosure may be applied to reception of any DL channel / signal (e.g., PDSCH / A-CSI-RS).

[0215] (Wireless Communication Method) Each embodiment of the present disclosure may be applied regardless of the setting of a specific upper layer parameter, or may be applied when one or more specific upper layer parameters are set.

[0216] The specific upper layer parameter may be, for example, at least one of a parameter indicating whether a TCI selection field is present in the DL DCI (e.g., tciSelection-PresentInDCI), a parameter indicating the application of a unified TCI state (e.g., followUnifiedTCI-State), a parameter indicating the application of an indicated TCI state (e.g., applyIndicatedTCIState), and a parameter indicating whether a TCI field is present in the DL DCI (e.g., tciPresentInDCI).

[0217] First Embodiment At least one of higher layer (RRC) parameters related to the unified TCI state and RRC parameters corresponding to the TRP may be configured for the UE.

[0218] The RRC parameter related to the unified TCI state may be, for example, a parameter related to the joint / DL TCI state (eg, dl-OrJointTCI-StateList).

[0219] The UE may be indicated / activated with multiple (eg, two) indicated TCI states.

[0220] The RRC parameter corresponding to the TRP may be, for example, a parameter indicating a CORESET pool index (e.g., coresetPoolIndex).

[0221] The UE may determine the TCI state to apply to the DL channel / signal based on at least one of the frequency range, support for multiple beam buffering capability (e.g., multiple beam buffering capability for multiple DCIs and multiple TRPs), and scheduling offset.

[0222] For example, the UE / base station may follow at least one of the following embodiments 1-1 and 1-2. The following embodiments 1-1 and 1-2 may be applied independently or in combination. For example, the following embodiments 1-1 and 1-2 may be switched based on higher layer signaling.

[0223] The DL channel / signal of this embodiment may be, for example, a PDSCH or any other DL channel / signal.

[0224] <<Embodiment 1-1>> The UE may not support buffering capability using multiple (e.g., two) default beam / QCL / TCI states in a specific frequency range (e.g., FR2 / FR2-1 / FR2-2).

[0225] The UE does not have to report support for this capability.

[0226] In this disclosure, supporting a capability, reporting information corresponding to a capability, and reporting a capability may be interpreted interchangeably. Also, not supporting a capability, not reporting information corresponding to a capability, and not reporting a capability may be interpreted interchangeably.

[0227] The capability may be, for example, a buffering capability using two default beams for multi-DCI based multi-TRP.

[0228] This capability may be, for example, the same as the buffering capability using two default beams for a single DCI-based multi-TRP.

[0229] The capability may be, for example, a buffering capability using two default beams for single / multiple DCI based multi-TRP.

[0230] The buffering capability using two default beams for single DCI-based multi-TRP may be used for single DCI-based multi-TRP operation or for multiple DCI-based multi-TRP operation.

[0231] The buffering capability using two default beams for multi-DCI based multi-TRP may be used for multi-DCI based multi-TRP operation or for single DCI based multi-TRP operation.

[0232] The capability may be a (specific) capability for the PDSCH, or a capability common to multiple DL channels / signals (e.g., PDSCH / A-CSI-RS).

[0233] The UE may be indicated / activated for multiple (eg, two) indicated TCI states based on RRC parameters for unified TCI states.

[0234] The UE may be configured with an RRC parameter (e.g., dl-OrJointTCI-StateList) for the unified TCI state, with multiple (e.g., two) indicated TCI states, and with a PDCCH configuration (e.g., PDCCH-Config) including multiple (e.g., two) different values ​​of CORESET pool index (e.g., RRC parameter coresetPoolIndex) within the CORESET (e.g., RRC parameter ControlResourceSet).

[0235] The UE may follow a specific method if the offset (which may be referred to as the scheduling / triggering offset) between the reception of a DCI (e.g., DCI format 1_0 / 1_1 / 1_2) that schedules / activates / trigger a DL channel / signal and the reception of that DL channel / signal is less than a specific threshold (e.g., "timeDurationForQCL").

[0236] The specific method may be, for example, at least one of the following options 1-1-1 to 1-1-3.

[0237] [Option 1-1-1] The UE may not expect / expect (scheduling / reception of) DL channels / signals in a particular frequency range (FR2 / FR2-1 / FR2-2) with a scheduling offset smaller than a particular threshold.

[0238] 7A is a diagram showing an example of a PDSCH schedule according to option 1-1-1. If the UE does not report the buffering capability, it does not assume a PDSCH schedule with a scheduling offset smaller than a certain threshold.

[0239] Option 1-1-1 simplifies the implementation of the UE / base station.

[0240] [Option 1-1-2] The UE may apply the indicated TCI state associated with a particular CORESET pool index value to the scheduled DL channel / signal.

[0241] The value of the particular CORESET pool index may be, for example, a first value (e.g., 0) or a second value (e.g., 1).

[0242] For example, the UE may receive DL channels / signals associated with a first (or second) value of CORESET pool index, and may not receive DL channels / signals associated with a second (or first) value of CORESET pool index in a particular frequency range (FR2 / FR2-1 / FR2-2) where the scheduling offset is smaller than a particular threshold.

[0243] 7B is a diagram showing an example of application of the indicated TCI state to the PDSCH according to option 1-1-2. If the UE does not report the buffering capability, it applies the indicated TCI state associated with the value of CORESET pool index #0 to the PDSCH whose scheduling offset is smaller than a certain threshold.

[0244] Option 1-1-2 allows for more flexible DL channel / signal scheduling.

[0245] [Option 1-1-3] The UE may apply the indicated TCI state associated with a particular cell ID to the scheduled DL channel / signal.

[0246] The specific cell ID may be, for example, the physical cell ID (PCI) of the serving cell.

[0247] For example, the UE may receive DL channels / signals associated with the serving cell PCI, but not receive DL channels / signals associated with other PCIs.

[0248] 7C is a diagram showing an example of application of the indicated TCI state to the PDSCH according to option 1-1-3. If the UE does not report the buffering capability, it applies the indicated TCI state associated with the PCI of the serving cell to the PDSCH whose scheduling offset is smaller than a certain threshold.

[0249] Option 1-1-3 allows UEs to properly receive common DL channels / signals associated with the serving cell PCI.

[0250] In addition, the specific cell ID may be the PCI of a non-serving cell.

[0251] According to embodiment 1-1, even if the UE does not support a particular capability, the TCI state can be appropriately applied.

[0252] Embodiment 1-2 A UE may be instructed / activated to indicate multiple (eg, two) indicated TCI states based on RRC parameters related to the unified TCI state.

[0253] The UE may be configured with an RRC parameter (e.g., dl-OrJointTCI-StateList) for the unified TCI state, with multiple (e.g., two) indicated TCI states, and with a PDCCH configuration (e.g., PDCCH-Config) including multiple (e.g., two) different values ​​of CORESET pool index (e.g., RRC parameter coresetPoolIndex) within the CORESET (e.g., RRC parameter ControlResourceSet).

[0254] For a UE in the first frequency range (e.g., FR1), regardless of the value of the scheduling offset, the UE may apply to the scheduled DL channel / signal the indication TCI state specific to the value of the corresponding SORESET pool index.

[0255] The UE may support buffering capability using multiple (e.g., two) default beam / QCL / TCI states in a second frequency range (e.g., FR2 / FR2-1 / FR2-2).

[0256] The UE may report support for the capability.

[0257] The capability may be, for example, a buffering capability using two default beams for multi-DCI based multi-TRP.

[0258] This capability may be, for example, the same as the buffering capability using two default beams for a single DCI-based multi-TRP.

[0259] The capability may be, for example, a buffering capability using two default beams for single / multiple DCI based multi-TRP.

[0260] If the UE supports this capability, it may apply to the scheduled DL channel / signal an indication TCI state specific to the corresponding CORESET pool index value (see Figure 8).

[0261] If the UE does not support this capability and the scheduling offset is equal to or greater than a certain threshold (e.g., "timeDurationForQCL"), the UE may apply to the scheduled DL channel / signal an indication TCI state specific to the corresponding SORESET pool index value.

[0262] According to embodiment 1-2, even if the UE supports / does not support a particular capability, the TCI state can be appropriately applied.

[0263] <<Variations of the First Embodiment>> [Variation 1] A UE is configured with an RRC parameter (e.g., dl-OrJointTCI-StateList) related to a unified TCI state, has multiple (e.g., two) indicated TCI states, does not support buffering capability using multiple (e.g., two) default beams / QCLs / TCI states for a single DCI-based multi-TRP in a second frequency range (e.g., FR2 / FR2-1 / FR2-2), and the scheduling offset of a scheduled DL channel / signal is smaller than a specific threshold (e.g., "timeDurationForQCL") (Condition 1), the UE may apply the specific indicated TCI state to reception of the DL channel / signal.

[0264] The particular indicated TCI state may be, for example, the first (or second) indicated TCI state.

[0265] When condition 1 is met and a PDCCH configuration (e.g., PDCCH-Config) is configured that includes multiple (e.g., two) different values ​​of CORESET pool index (e.g., RRC parameter coresetPoolIndex) within the CORESET (e.g., RRC parameter ControlResourceSet), at least one of the above options 1-1-1 to 1-1-3 may be selected / determined / applied.

[0266] [Variation 2] An RRC parameter (for example, dl-OrJointTCI-StateList) related to the unified TCI state may be configured to have multiple (for example, two) indicated TCI states (condition 1-2-1).

[0267] For UEs in the first frequency range (eg, FR1), the operation of this variation may be applied regardless of the value of the scheduling offset (condition 1-2-2).

[0268] The UE may support buffering capability using multiple (e.g., two) default beam / QCL / TCI states for single DCI-based multi-TRP in a second frequency range (e.g., FR2 / FR2-1 / FR2-2).

[0269] If the UE reports support for the capability (conditions 1-2-3), it may apply the behavior of this variation.

[0270] If the UE does not support this capability and the scheduling offset is greater than or equal to a specific threshold (e.g., "timeDurationForQCL") (condition 1-2-4), the UE may apply the behavior of this variation.

[0271] If at least one of conditions 1-2-1 to 1-2-4 (e.g., conditions 1-2-1 and 1-2-2, conditions 1-2-1 and 1-2-3, or conditions 1-2-1 and 1-2-4) is met and a PDCCH configuration (e.g., PDCCH-Config) is configured that includes multiple (e.g., two) different values ​​of CORESET pool index (e.g., RRC parameter coresetPoolIndex) within the CORESET (e.g., RRC parameter ControlResourceSet), the UE may apply an indication TCI state specific to the value of the corresponding SORESET pool index.

[0272] According to the first embodiment described above, it is possible to appropriately apply a unified TCI state using multi-DCI-based multi-TRP.

[0273] Second Embodiment The DL channel / signal in this embodiment may be, for example, an A-CSI-RS or any other DL channel / signal.

[0274] This embodiment may be used for multi-DCI based multi-TRP operation or for single DCI based multi-TRP operation.

[0275] The UE may receive an aperiodic CSI-RS (A-CSI-RS) where the offset (which may be referred to as the triggering offset) between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the A-CSI-RS in the NZP CSI-RS resource set configuration (e.g., the RRC parameter NZP-CSI-RS-ResourceSet) is less than a certain threshold (e.g., beamSwitchTiming).

[0276] The configuration of the NZP CSI-RS resource set (for example, the RRC parameter NZP-CSI-RS-ResourceSet) may not include a parameter indicating TRS information (for example, trs-Info).

[0277] The UE may report on a specific threshold (eg, beamSwitchTiming / beamSwitchTiming-r16).

[0278] This embodiment may be applied, for example, in at least one of the following specific cases: - When the reported value is one of {14, 28, 48}×2max(0, (μ_CSI-RS)−3) and a parameter indicating triggering of A-CSI-RS with beam switching triggering operation (e.g., enableBeamSwitchTiming / enableBeamSwitchTiming-r16) is not provided. - When the reported value is smaller than 48×2max(0,(μ_CSI-RS)−3), the UE provides a specific threshold (e.g., beamSwitchTiming / beamSwitchTiming-r16), a parameter indicating triggering of A-CSI-RS with beam switching triggering operation (e.g., enableBeamSwitchTiming / enableBeamSwitchTiming-r16) is provided, and an NZP CSI-RS resource set configuration (e.g., NZP-CSI-RS-ResourceSet) in which the repetition transmission parameter (e.g., repetition) is set to “off” or an NZP CSI-RS resource set configuration in which the repetition transmission parameter (e.g., repetition) is not set is configured. - When the reported value is smaller than a specific threshold (e.g., beamSwitchTiming / beamSwitchTiming-r16) reported by the UE, a parameter (e.g., enableBeamSwitchTiming / enableBeamSwitchTiming-r16) indicating triggering of A-CSI-RS with beam switching triggering operation is provided, and an NZP CSI-RS resource set configuration (e.g., NZP-CSI-RS-ResourceSet) is configured in which the repetitive transmission parameter (e.g., repetition) is set to "on".

[0279] In the present disclosure, μ ＣＳＩ－ＲＳ (μ_CSI-RS) may be the subcarrier spacing setting for CSI-RS.

[0280] A case (condition 2) may be specified in which a specific higher layer parameter (e.g., a parameter indicating that the default TCI state operation (e.g., Rel. 16 operation) is to be followed for each CORESET pool index (e.g., enableDefaultTCI-StatePerCoresetPoolIndex)) is configured for the UE, and a PDCCH configuration (e.g., PDCCH-Config) including multiple (e.g., two) different values ​​of CORESET pool index (e.g., coresetPoolIndex) is configured within the CORESET (e.g., ControlResourceSet).

[0281] The UE / base station may apply this embodiment in cases other than condition 2.

[0282] For example, the UE may apply this embodiment when a specific higher layer parameter (e.g., a parameter indicating that the default TCI state behavior (e.g., Rel. 16 behavior) is to be followed per CORESET pool index (e.g., enableDefaultTCI-StatePerCoresetPoolIndex)) is not set.

[0283] RRC parameters relating to the unified TCI state may be configured for the UE.

[0284] The RRC parameter related to the unified TCI state may be, for example, a parameter related to the joint / DL TCI state (eg, dl-OrJointTCI-StateList).

[0285] The UE may be indicated / activated for multiple (eg, two) indicated TCI states based on RRC parameters for unified TCI states.

[0286] When the UE is configured with a parameter related to the joint / DL TCI state (e.g., dl-OrJointTCI-StateList) and has multiple (e.g., two) indicated TCI states, the UE may determine the indicated TCI state to apply to the DL channel / signal (e.g., A-CSI-RS) based on a specific method.

[0287] The specific method may be, for example, at least one of the following options 2-1 and 2-2.

[0288] [Option 2-1] The UE may apply a specific indication TCI state to the A-CSI-RS resource set or the CSI-RS resources within the A-CSI-RS resource set.

[0289] The particular indicated TCI state may be, for example, the first (or second) indicated TCI state (see FIG. 9A).

[0290] Option 2-1 simplifies the implementation of the UE / base station.

[0291] [Option 2-2] The UE may not support buffering capability using multiple (e.g., two) default beam / QCL / TCI states in a particular frequency range (e.g., FR2 / FR2-1 / FR2-2).

[0292] The UE does not have to report support for this capability.

[0293] This capability may be, for example, the same as the buffering capability using two default beams for a single DCI-based multi-TRP.

[0294] The capability may be, for example, a buffering capability using two default beams for multi-DCI based multi-TRP.

[0295] The capability may be, for example, a buffering capability using two default beams for single / multiple DCI-based multi-TRP, or a common capability for single DCI multi-TRP and multi DCI multi-TRP.

[0296] The buffering capability using two default beams for single DCI-based multi-TRP may be used for single DCI-based multi-TRP operation or for multiple DCI-based multi-TRP operation.

[0297] The buffering capability using two default beams for multi-DCI based multi-TRP may be used for multi-DCI based multi-TRP operation or for single DCI based multi-TRP operation.

[0298] The capability may be a (specific) capability for the A-CSI-RS, or may be a common capability for multiple DL channels / signals (eg, PDSCH / A-CSI-RS).

[0299] If the capability is not reported, the UE may apply a specific indication TCI state to the A-CSI-RS resource set or to the CSI-RS resources within the A-CSI-RS resource set.

[0300] The particular indicated TCI state may be, for example, the first (or second) indicated TCI state.

[0301] Otherwise (e.g., if the capability is reported), the UE may apply the first / second indicated TCI state to the A-CSI-RS resource set or the CSI-RS resources within the A-CSI-RS resource set based on / according to / depending on the configuration of specific RRC parameters within the A-CSI-RS resource set (see Figure 9B).

[0302] The specific RRC parameter may be, for example, a parameter indicating the application of a unified TCI state (e.g., followUnifiedTCI-State).

[0303] The UE may be configured with an RRC parameter (e.g., dl-OrJointTCI-StateList) for the unified TCI state, with multiple (e.g., two) indicated TCI states, and with a PDCCH configuration (e.g., PDCCH-Config) including multiple (e.g., two) different values ​​of CORESET pool index (e.g., RRC parameter coresetPoolIndex) within the CORESET (e.g., RRC parameter ControlResourceSet).

[0304] In this case, the first and second indication TCI states may correspond to a first value CORESET pool index (e.g., 0) and a second value CORESET pool index (e.g., 1), respectively.

[0305] The UE may determine / assume that the first indicated TCI state and the second indicated TCI state correspond to a first value CORESET pool index (e.g., 0) and a second value CORESET pool index (e.g., 1), respectively.

[0306] Other Operations In certain conditions, the UE may apply certain QCL assumptions to the reception of A-CSI-RS.

[0307] The specific condition may be at least one of the following: The UE is configured with an RRC parameter (e.g., dl-OrJointTCI-StateList) related to the unified TCI state. The UE has one indicated TCI state (the UE indicates / activates one indicated TCI state). Regardless of the setting of a parameter (e.g., followUnifiedTCI-State) indicating the application of the unified TCI state, the indicated TCI state is associated with the PCI of a cell different from the serving cell. At least one CORESET is configured in the BWP where the A-CSI-RS is received.

[0308] The particular QCL may be the QCL assumption used for the CORESET associated with the monitored search space with the lowest (or highest) controlResourceSetId in the latest slot in which one or more CORESETs in the serving cell's active BWP are monitored.

[0309] In the case of carrier aggregation (CA), if the specific QCL type (e.g., QCL type D) of the A-CSI-RS from each CC in a band is different in a certain slot, the QCL assumption (e.g., QCL type D assumption) of the CSI-RS in a specific CC in the band (e.g., the CC with the lowest (or highest) CC ID) may be applied to the A-CSI-RS in multiple CCs in the band (e.g., all A-CSI-RS).

[0310] If a UE is configured with an RRC parameter related to the unified TCI state (e.g., dl-OrJointTCI-StateList), has one indicated TCI state, and the indicated TCI state is associated with the PCI of the serving cell, the indicated TCI state may be applied to the A-CSI-RS regardless of the setting of a parameter indicating the application of the unified TCI state (e.g., followUnifiedTCI-State).

[0311] According to the second embodiment described above, it is possible to appropriately apply a unified TCI state using single / multiple DCI-based multi-TRP.

[0312] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0313] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0314] When the 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 Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0315] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

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

[0317] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0318] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0319] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0320] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0321] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0322] The specific UE capability may indicate at least one of the following: Supporting specific processing / operation / control / information for at least one of the above embodiments (e.g., buffering received signals using multiple indicated TCI states), Number of supported bufferable indicated TCI states of received signals.

[0323] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0324] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0325] Furthermore, at least one of the above-described embodiments may be applied when the UE is configured / activated / triggered with specific information related to the above-described embodiments (or performing the operations of the above-described embodiments) by higher layer / physical layer signaling, for example, the specific information may be information indicating enabling a buffer for received signals using multiple indicated TCI states, any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

[0326] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0327] (Supplementary Note A) The following inventions are added in relation to one embodiment of the present disclosure. [Supplementary Note A-1] A terminal comprising: a receiver that receives higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and a physical downlink control channel configuration including a plurality of different control resource set (CORESET) pool indices, and receives downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), and a controller that determines an indicated TCI state to apply to the PDSCH based on at least one of a frequency range, a report of a capability of buffering multiple beams for multiple DCI-based multiple transmit / receive points (TRPs), and an offset from the last symbol of the DCI to the start symbol of the PDSCH. [Supplementary Note A-2] The terminal according to Supplementary Note A-1, wherein, when the terminal does not report the capability and the offset is smaller than a specific threshold, the controller applies to the PDSCH an indicated TCI state associated with a specific CORESET pool index value among the plurality of different CORESET pool indices. [Supplementary Note A-3] The terminal according to Supplementary Note A-1 or Supplementary Note A-2, wherein the frequency range is a first frequency range, or the terminal reports the capability, or the terminal does not report the capability and the offset is greater than a specific threshold, the control unit applies to the PDSCH an indication TCI state associated with a value of a CORESET pool index corresponding to the DCI. [Supplementary Note A-4] The terminal according to any of Supplementary Note A-1 to Supplementary Note A-3, wherein the capability is a common capability with a buffering capability of multiple beams for single DCI-based multi-TRP.

[0328] (Supplementary Note B) The following inventions are added with respect to one embodiment of the present disclosure: [Supplementary Note B-1] A terminal including: a receiver that receives higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and receives downlink control information (DCI) that triggers an aperiodic channel state information reference signal (A-CSI-RS), and a controller that, when a parameter indicating that a default TCI state operation is to be followed for each control resource set (CORESET) pool index is not set, determines an indicated TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of a frequency range, a report of buffering capability for multiple beams for multiple transmit / receive points (TRPs), and an offset from the last symbol of a physical downlink control channel that transmits the DCI to the start symbol of the A-CSI-RS. [Supplementary Note B-2] The terminal according to Supplementary Note B-1, wherein, if multiple indicated TCI states are indicated based on the higher layer parameter and the offset is smaller than a specific threshold, or if the terminal does not report the capability, the control unit applies a first indicated TCI state of the multiple indicated TCI states to the resource or the resource set. [Supplementary Note B-3] The terminal according to Supplementary Note B-1 or Supplementary Note B-2, wherein, if multiple indicated TCI states are indicated based on the higher layer parameter and the terminal reports the capability, the control unit applies at least one of a first indicated TCI state and a second indicated TCI state of the multiple indicated TCI states to the resource or the resource set based on a parameter indicating application of a unified TCI state. [Supplementary Note B-4] The terminal according to any of Supplements B-1 to B-3, wherein the capability is at least one of a capability of buffering multiple beams for single DCI-based multi-TRP and a capability of buffering multiple beams for multiple DCI-based multi-TRP.

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

[0330] 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0331] The wireless communication system 1 may also 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)), etc.

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

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

[0334] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0335] 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 (CCs) and dual connectivity (DC).

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

[0337] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0338] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

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

[0340] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

[0341] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0342] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. 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-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0343] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

[0345] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0346] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

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

[0348] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0349] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0350] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

[0352] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0353] 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, as the DL-RS, 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. may be transmitted.

[0354] 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 an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0355] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0356] 11 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

[0358] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0360] The transceiver 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 transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0361] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0362] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0363] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0364] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0365] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

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

[0367] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

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

[0369] The transceiver 120 (reception 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 (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0370] The transceiver 120 (measurement unit 123) may perform measurements on 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 measure received power (e.g., Reference Signal Received Power (RSRP)), received 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.

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

[0372] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0373] The transceiver unit 120 may transmit a physical downlink control channel configuration including higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and different control resource set (CORESET) pool indexes, and may transmit downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH). The control unit 110 may determine an indicated TCI state to apply to the PDSCH based on at least one of a frequency range, a report of buffering capability for multiple beams for multiple DCI-based multiple transmission / reception points (TRPs), and an offset from the last symbol of the DCI to the start symbol of the PDSCH (first embodiment).

[0374] The transceiver unit 120 may transmit upper layer parameters related to a unified Transmission Configuration Indication (TCI) state and may transmit downlink control information (DCI) that triggers an aperiodic channel state information reference signal (A-CSI-RS). When the control unit 110 does not set a parameter indicating that a default TCI state operation is to be performed for each control resource set (CORESET) pool index, the control unit 110 may determine an indicated TCI state to be applied to a resource or resource set of the A-CSI-RS based on at least one of a frequency range, a report of buffering capability for multiple beams for multiple transmission / reception points (TRPs), and an offset from the last symbol of a physical downlink control channel that transmits the DCI to the start symbol of the A-CSI-RS (second embodiment).

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

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

[0377] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

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

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

[0381] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0382] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0383] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0384] The transceiver 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, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

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

[0386] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0387] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

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

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

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

[0391] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The 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 the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0392] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0393] The transceiver unit 220 may receive higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and a physical downlink control channel configuration including different control resource set (CORESET) pool indexes, and may receive downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH). The control unit 210 may determine an indicated TCI state to apply to the PDSCH based on at least one of a frequency range, a report of buffering capability for multiple beams for multiple DCI-based multiple transmission / reception points (TRPs), and an offset from the last symbol of the DCI to the start symbol of the PDSCH (first embodiment).

[0394] If the terminal does not report the capability and the offset is smaller than a specific threshold, the control unit 210 may apply an indication TCI state associated with a specific CORESET pool index value among the different multiple CORESET pool indexes to the PDSCH (first embodiment).

[0395] If the frequency range is a first frequency range, or if the terminal reports the capability, or if the terminal does not report the capability and the offset is greater than a specific threshold, the control unit 210 may apply an indication TCI state associated with the value of a CORESET pool index corresponding to the DCI to the PDSCH (first embodiment).

[0396] The capability may be a common capability with the buffering capability of multiple beams for a single DCI-based multi-TRP (first embodiment).

[0397] The transceiver unit 220 may receive upper layer parameters related to a unified Transmission Configuration Indication (TCI) state and may receive downlink control information (DCI) that triggers an aperiodic channel state information reference signal (A-CSI-RS). When a parameter indicating that a default TCI state operation is to be followed is not set for each control resource set (CORESET) pool index, the control unit 210 may determine an indicated TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of a frequency range, a report of buffering capability for multiple beams for multiple transmission / reception points (TRPs), and an offset from the last symbol of a physical downlink control channel that transmits the DCI to the start symbol of the A-CSI-RS (second embodiment).

[0398] If multiple indicated TCI states are indicated based on the upper layer parameters and the offset is smaller than a specific threshold, or if the terminal does not report the capability, the control unit 210 may apply a first indicated TCI state of the multiple indicated TCI states to the resource or the resource set (second embodiment).

[0399] When multiple indicated TCI states are indicated based on the upper layer parameters and the terminal reports the capabilities, the control unit 210 may apply at least one of a first indicated TCI state and a second indicated TCI state among the multiple indicated TCI states to the resource or the resource set based on a parameter indicating the application of a unified TCI state (second embodiment).

[0400] The capability may be at least one of a capability of buffering multiple beams for a single DCI-based multi-TRP and a capability of buffering multiple beams for multiple DCI-based multi-TRP (second embodiment).

[0401] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0402] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0403] For example, a base station, a user terminal, or the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0404] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0405] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

[0407] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0408] The processor 1001 also reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. 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 the other functional blocks may be implemented in a similar manner.

[0409] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0410] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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

[0412] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0413] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

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

[0415] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

[0417] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0418] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

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

[0420] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0421] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0422] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0423] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0424] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0425] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0426] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0427] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0428] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0429] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0430] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0431] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0432] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0433] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

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

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

[0436] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

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

[0438] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0439] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0440] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0441] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0442] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0443] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0444] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0445] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0446] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0447] 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," "receiving entity," etc. may be used interchangeably.

[0448] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0449] The group may include, for example, at least one of 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, a panel group, and the like.

[0450] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0451] In addition, in the present disclosure, the terms 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 read interchangeably.

[0452] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0453] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0454] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0455] In the present disclosure, terms such as "base station (BS)," "radio 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," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0456] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0457] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

[0458] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0459] A mobile station may also be referred to as 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 suitable terminology.

[0460] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0461] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0462] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0463] 14 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air 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.

[0464] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0465] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0466] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0467] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0468] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0469] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, 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 Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

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

[0471] 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 an external device. For example, it transmits and receives various information to and from the external device 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. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

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

[0473] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0474] 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, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

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

[0476] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0477] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0478] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0479] Each aspect / embodiment described in the present disclosure may be a technology other than 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 (x is, for example, an integer or decimal number)), 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0480] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0481] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0482] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0483] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0484] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0485] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0486] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...." "does not expect ..." may be interchangeably read as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

[0488] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0489] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0490] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0491] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0492] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0493] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0494] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0495] In the present disclosure, terms 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. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0496] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0497] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiving unit that receives higher-layer parameters related to the Unified Transmission Configuration Indication (TCI) state and receives downlink control information (DCI) that triggers a non-periodic channel state information reference signal (A-CSI-RS), A terminal having a control unit that determines an instruction TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of the frequency range, whether or not the ability to buffer multiple beams for a single DCI-based multi-transmit / receive point (TRP) is reported, and the offset from the last symbol of the physical downlink control channel (PDCCH) transmitting the DCI to the start symbol of the A-CSI-RS.

2. The terminal according to claim 1, wherein the control unit determines the instructed TCI state to apply to the A-CSI-RS resource or resource set based on at least one of the frequency range, whether or not the ability to buffer multiple beams for multi-DCI based multi-TRP is reported, and the offset from the last symbol of the PDCCH transmitting the DCI to the start symbol of the A-CSI-RS, if no parameter is set for each control resource set (CORESET) pool index indicating that it follows the operation of a default TCI state.

3. The terminal according to claim 1, wherein the control unit does not report the capability when the frequency range is a first frequency range, but reports it when the frequency range is a second frequency range.

4. The control unit makes one of the following predetermined cases with respect to the offset: - If the reported predetermined threshold is a predetermined value based on the subcarrier interval for the CSI-RS, and no parameters indicating the triggering of the A-CSI-RS with beam switching triggering operation are provided, then the offset is determined to be smaller than the predetermined threshold. - When a non-zero power (NZP) CSI-RS resource set is configured that provides a predetermined threshold and parameters indicating the triggering of the A-CSI-RS with beam switching triggering operation, and the repeat transmission parameter is set to "off", the offset is determined to be smaller than a predetermined value based on the subcarrier interval for the CSI-RS. The terminal according to claim 1, wherein a parameter indicating the triggering of the A-CSI-RS with beam switching triggering operation is provided, and the NZP CSI-RS resource set is configured such that the repeat transmission parameter is set to "on", the offset is determined to be smaller than a predetermined threshold reported.

5. The process involves receiving higher-layer parameters related to the Unified Transmission Configuration Indication (TCI) state and receiving downlink control information (DCI) that triggers an aperiodic channel state information reference signal (A-CSI-RS), A wireless communication method for a terminal, comprising the step of determining an instruction TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of the following: a frequency range, whether or not there is a report of the ability to buffer multiple beams for a single DCI-based multi-transmit / receive point (TRP), and an offset from the last symbol of the physical downlink control channel (PDCCH) transmitting the DCI to the start symbol of the A-CSI-RS.

6. A transmitting unit that transmits higher-layer parameters related to the Unified Transmission Configuration Indication (TCI) state and transmits downlink control information (DCI) that triggers a non-periodic channel state information reference signal (A-CSI-RS), A base station having a control unit that determines an instruction TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of the frequency range, whether or not the ability to buffer multiple beams for a single DCI-based multi-transmit / receive point (TRP) is reported, and the offset from the last symbol of the physical downlink control channel (PDCCH) transmitting the DCI to the start symbol of the A-CSI-RS.

7. A system including a terminal and a base station, The aforementioned terminal is A receiving unit that receives higher-layer parameters related to the Unified Transmission Configuration Indication (TCI) state and receives downlink control information (DCI) that triggers a non-periodic channel state information reference signal (A-CSI-RS), The system includes a control unit that determines an instructed TCI state to apply to a resource or resource set of the A-CSI-RS based on at least one of the frequency range, whether or not the ability to buffer multiple beams for a single DCI-based multi-transmit / receive point (TRP) is reported, and the offset from the last symbol of the physical downlink control channel (PDCCH) transmitting the DCI to the start symbol of the A-CSI-RS, The aforementioned base station is A transmission unit that transmits the aforementioned upper layer parameters and transmits the DCI, A system having a control unit that determines the instructed TCI state.