Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one embodiment of the present disclosure includes: a reception unit that receives first downlink control information (DCI) used in a beam instruction, and second DCI which schedules or triggers an uplink (UL) signal; and a control unit that, on the basis of a specific field included in the second DCI, determines one or more Transmission Configuration Indication (TCI) states to be applied to the UL signal, from a plurality of TCI states specified by the first DCI, and determines whether the UL signal is a signal that uses one transmission / reception point (TRP) or a signal that uses a plurality of TRPs. According to the one embodiment of the present disclosure, it is possible to suitably determine a QCL assumption / TCI state.

Description

Technical Field

[0001] This disclosure relates to terminals and wireless communication methods in next-generation mobile communication systems. law, basis area Stations and systems related.

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] In future wireless communication systems (e.g., NR), it is being considered that 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 relationships).

[0006] Furthermore, it is being considered to indicate TCI states applicable to multiple types of signals (channel / reference signals) using downlink control information. However, the relationship between the number of TCI states indicated and the signals to which those TCI states apply is unclear. If such a relationship is not clear, it may lead to a decrease in communication quality, throughput, and other problems.

[0007] Therefore, this disclosure relates to a terminal that appropriately determines the QCL assumption / TCI state, and a wireless communication method. law, basis earth Stations and systems One of the purposes is to provide it. [Means for solving the problem]

[0008] A terminal relating to one aspect of this disclosure is , multiple Transmission Configuration Indication (TCI) states The first downlink control information (DCI) and the uplink (UL) used in the display channel Schedule Rusu A receiving unit that receives a second DCI and, based on a specific field included in the second DCI, the first DCI indicates The aforementioned multiple number T C I-shape From the state, the UL channel 1 to apply Two TCI states The UL determines multiple TCI states and channel However, it utilizes a single transmit / receive point (TRP). Is it a channel, or multiple Use a number of TRPs on the channelA control unit that determines whether it exists, Yes death, If the second DCI does not include the specific field, the control unit determines the index of the TCI state to apply to the UL channel using the settings obtained by upper-layer signaling. . [Effects of the Invention]

[0009] According to one aspect of this disclosure, the QCL assumption / TCI state can be appropriately determined. [Brief explanation of the drawing]

[0010] [Figure 1] Figures 1A and 1B show an example of a unified / common TCI framework. [Figure 2] Figures 2A and 2B show an example of a DCI-based TCI status indicator. [Figure 3] Figure 3 shows an example of the application time for the unified TCI status indicator. [Figure 4] Figures 4A and 4B show an example of the association between PUCCH resources / resource groups and indicated TCI states. [Figure 5] Figures 5A-5C show an example of the application of the indicative TCI state according to the first embodiment. [Figure 6] Figures 6A and 6B show an example of the application of the instructed TCI state according to Embodiment 1-1. [Figure 7] Figures 7A and 7B show an example of the application of the instruction TCI state related to the variation of Embodiment 1-1. [Figure 8] Figure 8 shows an example of information regarding the indicated TCI states and the number / order of indicated TCI states indicated by the scheduling DCI. [Figure 9] Figure 9 shows an example of an instruction for the TCI state according to Embodiment 1-2-1. [Figure 10] Figure 10 shows an example of an instruction for the TCI state according to Embodiment 1-2-2. [Figure 11] Figure 11 shows another example of the TCI status indication according to Embodiment 1-2-2. [Figure 12] Figure 12 shows an example of an instruction for the TCI state according to Embodiment 1-3. [Figure 13] FIG. 13 is a diagram showing an example of a field in the DCI according to Embodiments 1-4. [Figure 14] FIG. 14 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a configuration of a base station according to an embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a configuration of a user terminal according to an embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. [Figure 18] FIG. 18 is a diagram showing an example of a vehicle according to an embodiment.

Mode for Carrying Out the Invention

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

[0012] The TCI state may represent what is applied to a downlink signal / channel. What corresponds to the TCI state applied to an uplink signal / channel may be expressed as a spatial relation.

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

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

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

[0016] QCL may have multiple types (QCL types). For example, there may be four QCL types AD that differ in that they can be assumed to be identical parameters (or parameter sets).

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

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

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

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

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

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

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

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

[0025] [Data Physical Layer Procedure / Antenna Port QCL] A UE can configure a list of up to M TCI-State (TCI state) settings within the upper-layer parameter PDSCH-Config for decoding the PDSCH, according to the detected PDCCH with the DCI intended for that UE, a given serving cell, and the UE itself. Here, M depends on the UE capability maxNumberConfiguredTCIstatesPerCC.

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

[0027] In the case of two DL RSs, the multiple QCL types are not the same, regardless of whether the references refer to the same DL RS or different DL RSs. The QCL type corresponding to each DL RS is given by the higher-level 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 Status] The TCI-State associates one or two DL reference signals (RS) with the corresponding QCL type. If an additional physical cell identifier (PCI) is set for that RS, the same value is set for both DL RSs.

[0029] (Unified / Common TCI Framework) According to the unified TCI framework, multiple types of channels / RS (UL / DL) can be controlled by a common framework. The unified TCI framework does not define TCI states or spatial relationships for each channel, as in Rel. 15, but rather may specify a common beam (common TCI state) and apply it to all UL and DL channels, or a common beam for UL may be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

[0030] One common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (two common beams in total) are being considered.

[0031] The UE may assume the same TCI state (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set) for UL and DL. Alternatively, the UE may assume different TCI states for UL and DL respectively (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).

[0032] The default beams for UL and DL may be aligned by beam management based on MAC CE (MAC CE level beam indication). Alternatively, the default TCI status of PDSCH may be updated to match the default UL beam (spatial relationship).

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

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

[0035] The number of TCI states corresponding to each of the one or more TRPs may be defined. For example, the number of TCI states N (≧1) applied to the UL channel / RS (UL TCI states) and the number of TCI states M (≧1) applied to the DL channel / RS (DL TCI states) may be defined. At least one of N and M may be notified / set / instructed to the UE via upper layer signaling / physical layer signaling.

[0036] In this disclosure, when N=M=X (where X is any integer), it may mean that X TCI states (joint TCI states) common to the UL and DL (corresponding to X TRPs) are notified / set / instructed to the UE. Also, when N=X (where X is any integer) and M=Y (where Y is any integer, Y=X), it may mean that X TCI states (corresponding to X TRPs) for the UL and Y TCI states (corresponding to Y TRPs) for the DL (i.e., separate TCI states) are notified / set / instructed to the UE, respectively.

[0037] For example, if N=M=1 is written, it may mean that the UE is notified / set / instructed to have a TCI state common to one UL and DL for a single TRP (a joint TCI state for a single TRP).

[0038] Furthermore, if, for example, N=1 and M=1 are specified, it may mean that the UE is separately notified / configured / instructed to have one UL TCI state and one DL TCI state for a single TRP (separate TCI states for a single TRP).

[0039] Furthermore, for example, if N=M=2 is written, it may mean that the UE is notified / set / instructed to have a common TCI state for multiple (two) TRPs and multiple (two) ULs and DLs (a joint TCI state for multiple TRPs).

[0040] Furthermore, if it is written as N=2, M=2, for example, it may mean that the UE is notified / configured / instructed to have multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs (separate TCI states for multiple TRPs).

[0041] In the above example, we described the case where the values ​​of N and M are 1 or 2, but the values ​​of N and M may be 3 or greater, and N and M may be different.

[0042] Support for N=M=1 is being considered in Rel.17. Support for other cases is being considered in Rel.18 and later.

[0043] In the example in Figure 1A, the RRC parameter (information element) sets up multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the set up TCI states. DCI may indicate one of the activated TCI states. DCI may be a UL / DL DCI. The indicated TCI state may be applied to at least one (or all) of the UL / DL channels / RS. A single DCI may indicate both UL TCI and DL TCI.

[0044] In the example shown in this diagram, one point may represent a single TCI state that applies to both UL and DL, or it may represent two TCI states that apply to UL and DL respectively.

[0045] At least one of the multiple TCI states set by the RRC parameter and the multiple TCI states activated by MAC CE may be called a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by MAC CE may be called an active TCI pool (active common TCI pool).

[0046] In this disclosure, the higher-layer parameters (RRC parameters) that set up multiple TCI states may also be referred to as configuration information that sets up multiple TCI states, or simply as "configuration information." Furthermore, in this disclosure, being directed to one of multiple TCI states using DCI may mean receiving instruction information that directs to one of the multiple TCI states included in DCI, or simply receiving "instruction information."

[0047] In the example in Figure 1B, the RRC parameter sets up multiple TCI states (joint common TCI pool) for both DL and UL. MAC CE may activate multiple TCI states (active TCI pool) from the set up multiple TCI states. Separate active TCI pools for UL and DL may be set up / activated.

[0048] A DL DCI, or a new DCI format, may select (instruct) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) DL channels / RS. 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. A UL DCI, or a new DCI format, may select (instruct) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) UL channels / RS. UL channels may be PUSCH / SRS / PUCCH. Thus, different DCIs may instruct UL TCI and DL DCI separately.

[0049] From Rel.17 NR onward, MAC CE / DCI is expected to support beam activation / instruction to TCI states associated with different physical cell identifiers (PCIs). Furthermore, from Rel.18 NR onward, MAC CE / DCI is expected to support instruction to change serving cells to cells with different PCIs.

[0050] [Data Physical Layer Procedure / Antenna Port QCL] In order to provide reference signals for the DMRS of PDSCH and PDCCH, and CSI-RS within a CC, and further, if UL TX (transmit) spatial filters are available for dynamic grant and configured grant-based PUSCH and PUCCH resources, and SRS within a CC, the UE can configure a list of up to 128 DLorJointTCIState (TCI State for DL ​​or Joint) settings within PDSCH-Config (PDSCH Configuration) to provide references for determining those UL TCI filters.

[0051] If there is no DLorJointTCIState or UL-TCIState (UL TCI state) setting in the BWP within that CC, the UE can apply the DLorJointTCIState or UL-TCIState setting from the reference BWP of the reference CC. If DLorJointTCIState or UL-TCIState is set in any CC within the same band, it is not assumed that TCI-State, SpatialRelationInfo (spatial relationship information), and PUCCH-SpatialRelationInfo (PUCCH spatial relationship information) are set, except for SpatialRelationInfoPos (positional spatial relationship information) within that band. The UE assumes that if the UE sets the TCI-State in any CC within the CC list 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 will not set the DLorJointTCIState or UL-TCIState in any CC within that CC.

[0052] The UE receives an activation command used to map up to eight TCI state and / or TCI state pairs to the code point of the DCI field 'Transmission Configuration Indication' (TCI) for one or a set of CC / DL BWPs, if available, with one TCI state for a DL channel / signal and one TCI state for a UL channel / signal. If a set of TCI state IDs is activated for a set of CC / DL BWPs, and for one of the CC / DL BWPs if available, the same set of TCI state IDs is applied to all DL and / or UL BWPs in the indicated CC, where the list of applicable 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 code point, the UE applies the specified DLorJointTCIState and / or UL-TCIState to one or a set of CC / DL BWPs; if the specified mapping to a single TCI code point is applied, the UE applies the specified DLorJointTCIState and / or UL-TCIState to one or a set of CC / DL BWPs.

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

[0054] (Indication of TCI status) The Rel.17 Unified TCI Framework supports the following modes 1 through 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI-based TCI state indication with DL assignment (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

[0055] A UE with a TCI state set 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 set 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 include a DL assignment if one is available.

[0056] If DCI format 1_1 / 1_2 does not have a DL assignment, UE can assume (verify) the following for that DCI: - CS-RNTI is used to scramble CRC for DCI. - The values ​​of the following DCI fields (special fields) will be 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 set to all '0's for FDRA type 0, all '1's for FDRA type 1, or all '0's for DynamicSwitch (similar to the PDCCH validation for DL ​​semi-persistent scheduling (SPS) or UL grant type 2 scheduling releases).

[0057] The DCI in Mode 2 / Mode 3 described above may also be called beam-indicating DCI.

[0058] In Rel.15 / 16, if the UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. Similar behavior is being considered for the relationship between Rel.17 TCI state support and the interpretation of the TCI field. If the UE is configured with Rel.17 TCI state, it is being considered that 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 ignores the TCI field.

[0059] In Rel.15 / 16, whether or not a TCI field exists (DCI-PresentInDCI information) is set for each CORESET.

[0060] In DCI format 1_1, the TCI field is 0 bits if the upper layer parameter tci-PresentInDCI is not enabled, and 3 bits otherwise. If the BWP indicator field points to a BWP other than the active BWP, the UE follows these behaviors: [Operation] If the higher-layer parameter tci-PresentInDCI is not enabled for the CORESET used in the PDCCH that transmits the DCI format 1_1, the UE assumes that tci-PresentInDCI is not enabled for all CORESETs in the specified BWP; otherwise, the UE assumes that tci-PresentInDCI is enabled for all CORESETs in the specified BWP.

[0061] In DCI format 1_2, the TCI field is 0 bits if the upper layer parameter tci-PresentInDCI-1-2 is not set, and otherwise is 1, 2, or 3 bits as determined by the upper layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE follows these behaviors. [Operation] If the higher-layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used in the PDCCH that transmits the DCI format 1_2, the UE assumes that tci-PresentInDCI is not enabled for all CORESETs in the specified BWP; otherwise, the UE assumes that tci-PresentInDCI-1-2 is set for all CORESETs in the specified BWP with the same value as tci-PresentInDCI-1-2 set for the CORESET used in the PDCCH that transmits the DCI format 1_2.

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

[0063] Figure 2B shows an example of DCI-based separate DL / UL TCI status indication. For each value in the TCI field for separate DL / UL TCI status indication, at least one TCI status ID is associated: one indicating the TCI status for DL ​​only, and one indicating the TCI status for UL only. 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.

[0064] (Instructed TCI state / Set TCI state) Regarding the Rel.17 TCI state, the unified / common TCI state may also mean the Rel.17 TCI state indicated using (Rel.17) DCI / MAC CE / RRC (indicated Rel.17 TCI state).

[0065] In this disclosure, indicated Rel.17 TCI state, indicated TCI state, unified / common TCI state, TCI state applicable to multiple types of signals (channel / RS), and TCI state for multiple types of signals (channel / RS) may be interpreted as mutually exclusive.

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

[0067] With respect to the Rel.17 TCI state, any TCI state other than the unified TCI state may mean a Rel.17 TCI state configured using the MAC CE / RRC (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.

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

[0069] It is being considered that the instruction Rel.17TCI state should be applied to UE-specific channels / signals (RS). Furthermore, it is being considered that the UE should be notified using higher-layer signaling (RRC signaling) whether to apply the instruction Rel.17TCI state or the configured Rel.17TCI state to non-UE-specific channels / signals.

[0070] The RRC parameters for the Rel.17 TCI state (TCI state ID) are being considered to have the same configuration as the RRC parameters for the TCI state in Rel.15 / 16. The Rel.17 TCI state is being considered to be set / instructed for each CORESET / resource / resource set using RRC / MAC CE. Furthermore, it is being considered that the UE will make decisions regarding this setting / instruction based on specific parameters.

[0071] It is being considered that the update of the instruction TCI state and the update of the configuration TCI state will be performed separately for the UE. For example, if the unified TCI state for the instruction TCI state is updated for the UE, the configuration TCI state does not need to be updated. Furthermore, it is being considered that the UE will make decisions regarding such updates based on specific parameters.

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

[0073] Furthermore, regarding intra-cell beam indication (indication of TCI state), it is being considered that indication Rel.17TCI state will be supported for UE-specific CORESETs and PDSCHs associated with those CORESETs, and for non-UE-specific CORESETs and PDSCHs associated with those CORESETs.

[0074] Furthermore, for inter-cell beam indications (e.g., L1 / L2 intercell mobility), it is being considered that the indication Rel.17TCI state will be supported for UE-specific CORESETs and PDSCHs associated with those CORESETs.

[0075] In Rel.15, whether or not to instruct a CORESET#0 to have a TCI state depended on the base station implementation. In Rel.15, for CORESET#0 that has been instructed to have a TCI state, that instructed TCI state is applied. For CORESET#0 that has not been instructed to have a TCI state, the SSB and QCL selected during the most recent PRACH transmission are applied.

[0076] In the unified TCI state framework since Rel.17, the TCI state related to CORESET#0 has been examined.

[0077] For example, in the unified TCI state framework from Rel.17 onwards, whether or not to apply the indicated Rel-17 TCI state associated with the serving cell for CORESET#0 is determined by the RRC for each CORESET, and if it is not applied, the existing MAC CE / RACH signaling mechanism (legacy MAC CE / RACH signaling mechanism) may be used.

[0078] Furthermore, the CSI-RS associated with the Rel.17TCI status applied to CORESET#0 may be QCL associated with the Serving Cell PCI (Physical Cell ID) (similar to Rel.15).

[0079] For CORESET#0, a CORESET with a common search space (CSS), and a CORESET with both CSS and a UE-specific search space (USS), the RRC parameter may be set for each CORESET to determine whether or not to follow the instruction Rel.17TCI state. If the instruction Rel.17TCI state is not set to be followed for a particular CORESET, the set Rel.17TCI state may be applied to that CORESET.

[0080] For non-UE-dedicated channels / RSs (excluding CORESETs), the RRC parameter may be set for each channel / resource / resource set to determine whether or not to follow instruction Rel.17TCI status. If the channel / resource / resource set is not set to follow instruction Rel.17TCI status, the set Rel.17TCI status may be applied to that channel / resource / resource set.

[0081] (beam application time (BAT)) In Rel.17, regarding DCI-based beam indication, the following considerations 1 and 2 were examined concerning the application time of the beam / unified TCI state indication (beam application time (BAT) conditions).

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

[0083] In the example in 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.

[0084] For DCI basebeam indications in Rel.17, it is being considered that at least one Y symbol should be set for each BWP / CC in the UE.

[0085] If the SCS differs among multiple CCs, the Y symbol values ​​will also differ, potentially resulting in different application times among the multiple CCs.

[0086] [Consideration 2] For CA cases, the timing / BAT for applying the beam instruction may follow one of the following options 1 to 3. [Option 1] Both the first slot and the Y symbol are determined on the carrier with the minimum SCS among the one or more carriers to which the beam indication is applied. [Option 2] Both the first slot and the Y symbol are determined on the carrier with the minimum SCS, which is one or more carriers to which the beam indication is applied, and the UL carrier carrying its ACK. [Option 3] Both the first slot and the Y symbol are determined on the UL carrier that carries its ACK.

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

[0088] The application time (Y symbol) for beam indication to CA may be determined on the carrier with the minimum SCS among the carriers to which beam indication is applied. MAC CE base beam indication in Rel. 17 (when only a single TCI code point is activated) may follow the Rel. 16 application timeline for MAC CE activation.

[0089] Based on these considerations, it is being considered that the following actions should be defined in the specifications. [Operation] When a UE transmits the last symbol of a PUCCH with HARQ-ACK information corresponding to a DCI that conveys a TCI state indication, the indicated TCI state with the Rel.17TCI state may begin to be applied from the first slot that is at least Y symbols after the last symbol of that PUCCH, where Y may be a higher layer parameter (e.g., BeamAppTime_r17[symbol]). Both the first slot and the Y symbol may be determined on the carrier with the minimum SCS among the carriers to which the beam indication is applied. At some point in time, the UE may assume one indicated TCI state with the Rel17TCI state for DL ​​and UL, or one indicated TCI state (separate from DL) with the Rel17TCI state for UL.

[0090] X[ms] may be used instead of Y[symbol].

[0091] Regarding application time, it is being considered that the UE should report at least one of the following UE capabilities 1 and 2. [UE ability 1] Minimum application time per SCS (the minimum number of Y symbols between the last symbol of the PUCCH carrying the ACK and the first slot to which the beam is applied). [UE ability 2] The minimum time gap between the last symbol of the beam indicator PDCCH(DCI) and the first slot to which the beam is applied. The gap between the last symbol of the beam indicator PDCCH(DCI) and the first slot to which the beam is applied may satisfy the UE capability (minimum time gap).

[0092] UE capability 2 may be an existing UE capability (e.g., timeDurationForQCL).

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

[0094] Regarding the application time, parameters set by the base station (e.g., BeamAppTime_r17) may be optional fields.

[0095] (Direction / management of beams within a cell (intra-cell) / between cells (inter-cell)) From Rel.17 NR onward, MAC CE / DCI is expected to support beam instruction to TCI states associated with different PCIs. Furthermore, from Rel.18 NR onward, MAC CE / DCI is expected to support instruction to change serving cells to cells with different PCIs.

[0096] Instruction Rel.17TCI state may be shared (applied) to both UE-dedicated channels / RS and non-UE-dedicated channels / RS within a cell.

[0097] Instruction Rel.17TCI status may be shared (applied) only to individual UE channels / RSs between cells.

[0098] Between cells, for non-UE individual channels / RS, the RRC parameter may be set to determine whether or not to follow instruction Rel.17TCI state for each PDSCH (PDSCH setting) / CORESET (CORESET setting). UE individual channels / RS may not follow their RRC parameter and may always follow instruction Rel.17TCI state.

[0099] In this disclosure, a non-UE individual CORESET may mean a CORESET with CSS, and a UE individual CORESET may mean a CORESET with USS. In this disclosure, a non-UE individual PDSCH may mean a PDSCH scheduled by a CORESET with CSS, or a PDSCH scheduled by a CORESET with CSS other than type 3CSS. In this disclosure, a UE individual PDSCH may mean a PDSCH scheduled by a CORESET with USS, or a PDSCH scheduled by a CORESET with USS or type 3CSS. For example, for each PDSCH configuration (PDSCH-Config), an RRC parameter (e.g., followUnifiedTCIstate) may be set whether or not to follow instruction Rel.17TCI state, and this setting may not apply to UE individual PDSCHs (UE individual PDSCHs always follow Rel.17TCI state), but may apply to non-UE individual PDSCHs.

[0100] (Channel / RS to which the indicated TCI state applies) The indicated TCI state by MAC CE / DCI may be applied to the following channels / RS.

[0101] [PDCCH] If followUnifiedTCIState is set for CORESET0, the indicated TCI state will be applied. Otherwise, the Rel.15 specification will be applied to that CORESET. That is, CORESET0 will follow the TCI state activated by MAC CE, or will be QCL with SSB. • For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state is always applied. For CORESETs with CSS other than CSS type 3 and index other than 0, if it is configured to follow a unified TCI state, the indicative TCI state will be applied. Otherwise, the configured TCI state for that CORESET will be applied.

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

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

[0104] [PUCCH] • The instructed TCI state is always applied to all individual (dedicated) PUCCH resources.

[0105] [PUSCH] • For dynamic / configured grant pushes, the instructed TCI state is always applied.

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

[0107] (analysis) Incidentally, in Rel.18 and later, it is being considered to switch between single-TRP and multi-TRP settings / operations depending on the number of TCI states indicated by the beam indicator DCI.

[0108] On the other hand, Rel.18 is considering supporting coherent joint transmission (CJT) using up to four TRPs. Joint transmission (JT) may also mean simultaneous data transmission from multiple points (e.g., TRPs) to a single UE.

[0109] Rel.17 supports NCJT from two TRPs. PDSCHs from the two TRPs may be precoded and decoded independently. Frequency resources may be non-overlapping, partially overlapping, or fully overlapping. If overlap occurs, a PDSCH from one TRP will interfere with a PDSCH from the other TRP.

[0110] For CJT, data from the four TRPs may be coherently precoded and transmitted to the UE over the same time-frequency resources. For example, the same precoding matrix may be used to consider channels from the four TRPs. Coherence may mean that there is a constant relationship between the phases of multiple received signals. Using 4TRP joint precoding, signal quality may be improved and there may be no interference between the four TRPs. The data may only be subject to interference outside the four TRPs.

[0111] To support CJT, there can be more than two indicated TCI states (for example, up to four per BWP / CC), and a UE notified of more than two TCI states by RRC / MAC CE / DCI may be unable to determine whether to perform single TRP or multi-TRP operation.

[0112] In this case, if a certain number of indicated TCI states are indicated, the UE may decide to apply multi-TRP. For example, if one indicated TCI state is indicated, the UE may apply single-TRP operation, and if two or more indicated TCI states are indicated, the UE may apply multi-TRP operation.

[0113] Furthermore, with Rel.16 / 17's multi-TRP, it is possible to switch between single-TRP and multi-TRP using scheduling DCI, except for the repetition of PDCCH.

[0114] In the single DCI-based multi-TRP NCJT / repetitions defined in Rel.16, single-TRP and multi-TRP can be switched by the number of TCI states indicated in the TCI field.

[0115] In the NCJT / repetition of multi-DCI based multi-TRP as defined in Rel.16, single-TRP and multi-TRP can be switched based on whether the TCI state indicated by the DCI corresponding to each CORESET pool index is the same or not.

[0116] In the single DCI-based multi-TRP push iterations specified in Rel.17, the single-TRP and multi-TRP push iterations can be switched based on the SRS resource set indicator field in DCI format 0_1 / 0_2 for switching between single-TRP push iterations and multi-TRP push iterations.

[0117] In the iteration of a single DCI-based multi-TRP PUCCH as defined in Rel.17, one or two spatial relationships are activated for one PUCCH resource (resource group), and the single-TRP and multi-TRP can be switched by selecting one PUCCH resource via the DCI (specifically, the PUCCH resource indicator (PRI) / control channel element (CCE) index included in it).

[0118] In the iteration of PDCCH as defined in Rel.17, there is no way for DCI to switch the number of active TCI states (i.e., single TRP and multi-TRP) of a single CORESET.

[0119] Considering these factors, it is desirable that the operation of the unified TCI state as defined in Rel.18 and later also be performed by scheduling DCI to switch between single TRP and multi-TRP.

[0120] However, the method for switching the number of TRPs using DCI in the operation of the unified TCI state has not been sufficiently considered. If this consideration is insufficient, it may lead to a decrease in communication quality, throughput, and other problems.

[0121] Therefore, the inventors have conceived a method that allows for appropriate switching between single-TRP and multi-TRP in the operation of a unified TCI state, and that allows for the appropriate determination of the QCL assumption / TCI state to be applied to each channel / signal.

[0122] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0123] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0124] In this disclosure, terms such as notice, activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0125] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0126] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0127] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

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

[0129] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0130] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, indicated TCI state, quasi-co-location (QCL), QCL assumptions, etc., may be interpreted interchangeably.

[0131] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information" may be interpreted as mutually exclusive as "a set of spatial relationship information," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive.

[0132] Furthermore, the panel identifier (ID) and the panel may be interchangeable. In other words, TRP ID and TRP, CORESET group ID and CORESET group, etc., may be interchangeable.

[0133] In this disclosure, TRP, transmit point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in the TCI field may be interpreted as one another.

[0134] In this disclosure, the transmission / reception of a channel / signal using a single TRP may be interpreted as the TCI states (joint / separate / indicator TCI states) being equal in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repetition), or the number of TCI states (joint / separate / indicator TCI states) being one in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repetition).

[0135] The transmission / reception of a channel / signal using a single TRP may be interpreted as the TCI state (joint / separate / indicating TCI state) being different in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repetition), or the number of different TCI states (joint / separate / indicating TCI states) being multiple (e.g., two) in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repetition).

[0136] In this disclosure, single TRP, single TRP system, single TRP transmission, and single PDSCH may be interpreted interchangeably. In this disclosure, multiple TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interpreted interchangeably.

[0137] In this disclosure, the terms single DCI, single PDCCH, multi-TRP 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 up a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a particular channel / CORESET may be interpreted as mutually exclusive.

[0138] In this disclosure, the following can be interpreted interchangeably: single TRP, channel / signal using a single TRP, channel using one TCI state / spatial relationship, multi-TRP not being activated by RRC / DCI, multiple TCI states / spatial relationships not being activated by RRC / DCI, no CORESET pool index value of 1 being set for any CORESET, and no code point in a TCI field being mapped to two TCI states.

[0139] In this disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI state / spatial relationships, multi-TRP being activated by RRC / DCI, multiple TCI state / spatial relationships being activated by RRC / DCI, and at least one of single-DCI-based multi-TRP and multi-DCI-based multi-TRP may be interpreted as mutually exclusive.

[0140] In this disclosure, the following can be interpreted interchangeably: setting a CORESET pool index (CORESETPoolIndex) value for a multi-DCI-based multi-TRP and CORESET, and setting multiple specific indexes (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a specific channel / CORESET.

[0141] In this disclosure, TRP#1 (first TRP) may correspond to CORESET pool index = 0, or 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 to the second of two TCI states corresponding to one code point in the TCI field.

[0142] In this 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 code point may be interpreted as mutually exclusive.

[0143] In this disclosure, the following terms may be interpreted interchangeably: multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, two CORESET pool indices, or CORESET pool index = 1 (or a value of 1 or more).

[0144] In this disclosure, beam indicator DCI, beam indicator MAC CE, and beam indicator DCI / MAC CE may be interpreted as interchangeable. In other words, an indication of the TCI state for a UE may be made using at least one of DCI and MAC CE.

[0145] In this disclosure, repetition, repeated transmission, and repeated reception may be interpreted as mutually exclusive.

[0146] In this disclosure, channel, signal, and channel / signal may be interpreted as interchangeable. In this disclosure, DL channel, DL signal, DL signal / channel, DL signal / channel transmission / reception, DL reception, and DL transmission may be interpreted as interchangeable. In this disclosure, UL channel, UL signal, UL signal / channel, UL signal / channel transmission / reception, UL reception, and UL transmission may be interpreted as interchangeable.

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

[0148] In this disclosure, a first TRP may correspond to a first TCI state. In this disclosure, a second TRP may correspond to a second TCI state. In this disclosure, an nth TRP may correspond to an nth TCI state.

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

[0150] In the embodiments of this disclosure described below, the application of multiple TCI states in transmission and reception using multiple TRPs will mainly be described in terms of a method targeting two TRPs (i.e., when at least one of N and M is 2). However, the number of TRPs may be three or more, and each embodiment may be applied in accordance with the number of TRPs. In other words, at least one of N and M may be a number greater than 2.

[0151] In this disclosure, receiving DL signals (PDSCH / PDCCH) using an SFN may mean receiving the same data (PDSCH) / control information (PDCCH) from multiple transmission / reception points using the same time / frequency resources. Alternatively, receiving DL signals using an SFN may mean receiving the same data / control information from multiple TCI states / spatial domain filters / beams / QCLs using the same time / frequency resources.

[0152] (Wireless communication method) <Embodiment 0> In this embodiment, the mapping / association of instruction TCI states to each channel will be described.

[0153] The UE may use the beam indicator DCI / MAC CE to indicate y indicator TCI states, where y may be, for example, up to 4, up to a number greater than 4, or up to a number less than 4.

[0154] The UE may select x indicator TCI states from y indicator TCI states and apply them to each channel / signal.

[0155] The UE may receive at least one of the following using upper-layer signaling (RRC / MAC CE) / DCI: information about x and information about which x of the y indicated TCI states to apply.

[0156] The value of x may vary depending on the type of channel / signal. The value of y may vary depending on the type of channel / signal, or it may be the same.

[0157] In the case of single TRP operation, y may be a first value (e.g., 1). For example, if y is 1, the UE may be assumed to be operating in the unified TCI state as defined in Rel. 17.

[0158] In multi-TRP operation, y may be a second value (e.g., 2). Alternatively, in multi-TRP operation, y may be a third value (e.g., 4). Using a third value for y in multi-TRP operation allows for more flexible beam direction.

[0159] In the case of operations related to CJT, y may be a third value (for example, 4).

[0160] In the embodiments of this disclosure, the joint TCI state is described as the main example, but the separate (UL / DL) TCI state can also be applied as appropriate.

[0161] If y indicated TCI states are indicated for joint TCI states, then 2y indicated TCI states may be indicated for separate (UL / DL) TCI states. For example, if a maximum of 4 joint TCI states are indicated, then a maximum of 4 UL TCI states and a maximum of 4 DL TCI states may be indicated (i.e., a maximum of 8).

[0162] In this disclosure, within the same BWP / CC, either the joint TCI state or the separate (UL / DL) TCI state may be set / indicated by RRC / MAC CE / DCI. Also, in this disclosure, within the same BWP / CC, both the joint TCI state and the separate (UL / DL) TCI state may be set / indicated by RRC / MAC CE / DCI.

[0163] 《PDCCH, a single DCI-based multi-TRP》 A mapping / correspondence relationship may be established between the UE and the configuration / instruction TCI state (joint / DL TCI state) and the CORESET / CORESET group.

[0164] This setting may also be configured using higher-layer signaling (RRC).

[0165] For each CORESET, one or more (e.g., two) indices may be set for the indicated TCI states (e.g., the first / second indicated TCI states).

[0166] For a CORESET that is configured to follow a unified TCI state (e.g., followUnifiedTCIstate), x TCI states selected from y indicative TCI states may be applied to that CORESET.

[0167] For example, for a CORESET in which a single frequency network (SFN) scheme (e.g., SFN scheme A / B) is not set, x may be a first value (e.g., 1). For example, for a CORESET in which an SFN scheme (e.g., SFN scheme A / B) is set, x may be a second value (e.g., 2).

[0168] 《PDSCH, a single DCI-based multi-TRP》 When a single DCI-based multi-TRP PDSCH is configured, switching between a single-TRP PDSCH and a multi-TRP PDSCH via scheduling DCI may be supported.

[0169] For PDSCH, x TCI states selected from y indicated TCI states may be applied.

[0170] For example, x for a single TRP PDSCH may be a first value (e.g., 1). For example, x for a multi-TRP PDSCH (e.g., NCJT / repetition / SFN with single DCI-based multi-TRP) may be a second value (e.g., 2).

[0171] 《PUCCH, a single DCI-based multi-TRP》 When multi-TRP PUCCH (repetition) is configured, the scheduling DCI may support switching between single-TRP PUCCH (repetition) and multi-TRP PUCCH (repetition).

[0172] For PUCCH, x TCI states selected from y indicated TCI states may be applied. These x may be indicated by a scheduling DCI.

[0173] For example, the value of x for a single TRP's PUCCH (repetition) may be a first value (e.g., 1). For example, the value of x for a multi-TRP's PUCCH (repetition) may be a second value (e.g., 2).

[0174] If PUCCH (repeat) is not set for a multi-TRP, one TCI state selected from y indicated TCI states may be applied to PUCCH.

[0175] The selection of the single TCI state may be predetermined in the specifications, or it may be set by higher-layer signaling (RRC).

[0176] The TCI states of PDSCH and its associated PUCCH may be the same or different. For example, if PDSCH requires two TCI states and the associated PUCCH requires one TCI state, the UE may select two (x=2) TCI states for PDSCH / PUCCH and ignore the second TCI state for PUCCH.

[0177] 《PUSCH, a single DCI-based multi-TRP》 When multiple TRP push iterations (multiple (e.g., two) SRS resource sets of CB / NCB) are configured, switching between single TRP push iterations and multi-TRP push iterations may be supported via a specific field in the scheduling DCI.

[0178] The specific field in question may be, for example, an SRS resource set indicator field. The scheduling DCI may be, for example, DCI format 0_1 / 0_2.

[0179] For PUSCH, x TCI states selected from y indicated TCI states may be applied. These x may be indicated by a scheduling DCI.

[0180] For example, the value of x for a single TRP's PUSCH (repetition) may be a first value (e.g., 1). For example, the value of x for a multi-TRP's PUSCH (repetition) may be a second value (e.g., 2).

[0181] If PUSCH (repeat) is not set for a multi-TRP, one TCI state selected from y indicated TCI states may be applied to PUSCH.

[0182] The selection of the single TCI state may be predetermined in the specifications, or it may be set by higher-layer signaling (RRC).

[0183] PDCCH, a multi-DCI based multi-TRP architecture. A specific field within the DCI (DCI format 1_1 / 1_2 (with / without DL assignment)) corresponding to the CORESET Pool Index value may be used to indicate the indicated TCI state (Joint / DL / UL TCI state) corresponding to the same CORESET Pool Index value.

[0184] For a CORESET pool index with a first value (e.g., 0), y1 indicator TCI states may be indicated, and for a CORESET pool index with a second value (e.g., 1), y2 indicator TCI states may be indicated.

[0185] For a CORESET to which the first value of the CORESET pool index is set, x TCI states selected from y 1 indicated TCI states may be applied to that CORESET.

[0186] For a CORESET to which a second value CORESET pool index is set, x TCI states selected from y2 indicated TCI states may be applied to that CORESET.

[0187] For example, for a CORESET in which no SFN scheme (e.g., SFN scheme A / B) is set, x may be a first value (e.g., 1). For example, for a CORESET in which an SFN scheme (e.g., SFN scheme A / B) is set, x may be a second value (e.g., 2).

[0188] For each CORESET, one or more (e.g., two) indices may be set for the indicated TCI states (e.g., the first / second indicated TCI states). These settings may be set using upper layer signaling (RRC).

[0189] 《Numbers related to the indicated TCI state》 The following details the above x and y for each channel / signal.

[0190] The above x may also be the number of TCI states applied to each channel / signal from the above y (including y1 and y2) indicator TCI states.

[0191] The above x may be determined separately for each channel / signal to which it is applied. It may also be supported that the above x differs for each channel / signal to which it is applied.

[0192] Of the above y instruction TCI states, the TCI state to be applied may be determined separately for each channel / signal to which it is applied. Of the above y instruction TCI states, it may be supported that different TCI states are applied to each channel / signal to which it is applied.

[0193] Of the above y instruction TCI states, the applicable TCI state may be determined separately for each channel / signal resource / resource set / CORESET to which it is applied. It may also be supported that different TCI states are applied for each channel / signal resource / resource set / CORESET to which it is applied.

[0194] [CSI-RS / TRS / SSB / SRS] For a specific reference signal (e.g., CSI-RS / TRS / SSB / SRS), x may be a specific value.

[0195] The specific value may be 1.

[0196] Furthermore, the specific value may be 2 or greater. For example, in the repetition of a specific reference signal using multi-TRP, x may be 2 or greater.

[0197] The type of reference signal may be a specific type (e.g., A / SP / P).

[0198] The specific reference signal may be limited to CSI-RS / SRS.

[0199] A specific reference signal may be set using upper-layer signaling (RRC). For example, a specific reference signal may be a reference signal to which a specific RRC parameter (e.g., followUnifiedTCIstate) is set.

[0200] The specific reference signal may be a reference signal for a specific application / purpose. For example, the specific reference signal may be at least one of the following: a CSI-RS with repetition, a CSI-RS without repetition, a CSI-RS with tracking reference signal information (trs-info), a CSI-RS for beam management, or an SRS for use in CB / NCB / beam management / antenna switching.

[0201] [PDSCH] For a specific channel (e.g., PDSCH), x may be a specific value.

[0202] The specific value may be, for example, a value greater than or equal to 2 (for example, 2).

[0203] For example, for a single DCI-based multi-TRP PDSCH(NCJT / repetition / SFN), the specific value may be 2.

[0204] For example, when the specific value is 2, the UE may assume / determine the reception of a single DCI-based multi-TRP PDSCH (NCJT / repeated / SFN).

[0205] The specific value could be, for example, 1.

[0206] For example, the specific value may be 1 for at least one of the single TRP PDSCH and the multi-DCI-based multi-TRP PDSCH. The multi-DCI-based multi-TRP PDSCH may indicate one indicated TCI state for each CORESET pool index.

[0207] For example, when the specific value is 1, the UE may assume / determine the reception of at least one of a single TRP PDSCH and a multi-DCI-based multi-TRP PDSCH.

[0208] Furthermore, for a multi-DCI based multi-TRP PDSCH, if one DCI indicates multiple (e.g., two) indicator TCI states for the CORESET pool index, then x may be 2.

[0209] [PDCCH] For a specific channel (e.g., PDCCH), x may be a specific value.

[0210] The specific value may be, for example, a value greater than or equal to 2 (for example, 2).

[0211] For example, for SFN's PDCCH (for example, when an SFN scheme (scheme A / B) is set for CORESET), the specific value may be 2.

[0212] For example, when the specific value is 2, the UE may assume / determine that it has received the SFN's PDCCH.

[0213] The specific value could be, for example, 1.

[0214] For example, for PDCCH other than the PDCCH of SFN, that specific value may be 1.

[0215] For example, when the specific value is 1, the UE may assume / determine that it has received a PDCCH other than the SFN's PDCCH.

[0216] The value of x for PDCCH may be determined / set / indicated for each CORESET / search space. Alternatively, the value of x for PDCCH may be determined / set / indicated for multiple (e.g., all) CORESETs / search spaces in a given BWP / CC.

[0217] [PUCCH] For a specific channel (e.g., PUCCH), x may be a specific value.

[0218] The specific value may be, for example, a value greater than or equal to 2 (for example, 2).

[0219] For example, the specific value may be 2 for at least one of the following: PUCCH repetitions (e.g., when cyclic / sequential beam hopping is configured) and PUCCH for Simultaneous Transmission across multiple panels (STxMP) (e.g., PUCCH repetitions for frequency division multiplexing (FDM) / spatial division multiplexing (SDM) / SFN).

[0220] For example, when the specific value is 2, the UE may assume / determine that at least one of the following has been received: a repetition of PUCCH and a PUCCH of STxMP.

[0221] The specific value could be, for example, 1.

[0222] For example, for PUCCH other than at least one of the PUCCH repetitions and STxMP PUCCH, the specific value may be 1.

[0223] For example, when the specific value is 1, the UE may assume / determine the reception of a PUCCH other than at least one of a PUCCH repetition and an STxMP PUCCH.

[0224] The value of x for PUCCH may be determined based on the intended use of PUCCH. For example, if a PUCCH does not contain a specific UCI (e.g., HARQ-ACK), then x for that PUCCH may be 1. For example, if a PUCCH contains a specific UCI (e.g., HARQ-ACK), then x for that PUCCH may be 2.

[0225] The value of x for a PUCCH may be determined based on how the PUCCH is triggered. For example, if a PUCCH is not triggered by DCI, x for that PUCCH may be 1. For example, if a PUCCH is triggered by DCI (for example, a PUCCH to which a HARQ-ACK is sent), x for that PUCCH may be 2.

[0226] The value of x for PUCCH may be determined / set / instructed for each PUCCH resource / resource group in BWP / CC.

[0227] Furthermore, x for PUCCH may be determined / set / instructed for multiple (e.g., all) PUCCH resources / resource groups in a given BWP / CC.

[0228] Figures 4A and 4B illustrate an example of the association between PUCCH resources / resource groups and instructed TCI states. In the example shown in Figure 4A, PUCCH resource groups (PUCCH resource groups #1-#4) and PUCCH resources (PUCCH resources #1-#8) are set for the UE. These PUCCH resources / resource sets may be set in a BWP (BWP#1) within a CC (CC#1). The correspondence between PUCCH resource groups and PUCCH resources is as shown in Figure 4A.

[0229] Figure 4B shows the relationship between the four TCI states indicated by the beam indicator TCI state and the index corresponding to each TCI state.

[0230] As shown in Figure 4A, each PUCCH resource group is associated with an index relating to the TCI state to be applied. The UE may determine the TCI state corresponding to each PUCCH and the number of such TCI states based on the associated index and the TCI states corresponding to the index shown in Figure 4B.

[0231] In this way, by setting / determining / instructing the index of the instructed TCI state on a per-PUCCH resource / resource group basis, it is possible to switch between single TRP and multi-TRP operation in the scheduling DCI (which includes the PRI / CCE index field).

[0232] Furthermore, the setting / indication / updating of the TCI status index on a PUCCH resource unit / resource group basis may be performed using upper-layer signaling (RRC / MAC CE) / DCI (beam-indicating DCI).

[0233] Furthermore, the instruction TCI state applied to a PDSCH scheduled by the same DCI, and the number of instruction TCI states (x), may be determined based on at least one of the instruction TCI state applied to the PUCCH resource and the number of instruction TCI states (x).

[0234] Furthermore, the instruction TCI state applied to a PUCCH resource and the number of instruction TCI states (x) may be determined based on at least one of the instruction TCI state applied to a PDSCH scheduled by the same DCI, and at least one of the number of instruction TCI states (x).

[0235] [PUSCH] For a specific channel (e.g., PUSCH), x may be a specific value.

[0236] The specific value may be, for example, a value greater than or equal to 2 (for example, 2).

[0237] For example, for at least one of the following, the specific value may be 2: PUSCH repetition (e.g., when multiple (e.g., two) SRS resource sets of CB / NCB are configured) and STxMP PUSCH (e.g., when frequency FDM / SDM / SFN PUSCH repetition and each layer of PUSCH is transmitted on a separate beam).

[0238] For example, when the specific value is 2, the UE may assume / determine that at least one of the following has been received: a repeated PUSCH and an STxMP PUSCH.

[0239] The specific value could be, for example, 1.

[0240] For example, for any PUSCH other than at least one of the repeated PUSCH and the STxMP PUSCH, the specific value may be 1.

[0241] For example, when the specific value is 1, the UE may assume / determine the reception of a PUSCH other than at least one of a repeated PUSCH and an STxMP PUSCH.

[0242] In this embodiment, PUSCH may be, for example, at least one of a configured grant PUSCH and a DCI-scheduled PUSCH.

[0243] The value of x for PUCCH may be determined based on the DCI that schedules PUCCH. For example, if PUCCH is scheduled in a specific DCI format (e.g., DCI format 0_1 / 0_2), then x for PUCCH may be 2. For example, if PUCCH is scheduled in a DCI format other than the specific DCI format (e.g., DCI format 0_1 / 0_2), then x for PUCCH may be 1.

[0244] According to the first embodiment described above, the number of instruction TCI states to be applied to each channel / signal can be appropriately determined.

[0245] <First Embodiment> In this embodiment, the application of the indicative TCI state will be described in detail.

[0246] The operation outline of this embodiment will be explained using Figures 5A-5C.

[0247] Figure 5A shows an example of the application of the indicative TCI state according to the first embodiment.

[0248] The UE may first receive the beam instruction DCI. Alternatively, the UE may receive the scheduling / triggering DCI for each channel / signal.

[0249] In the example shown in Figure 5A, the UE first receives the beam instruction DCI (DCI#0). Then, the UE receives the scheduling DCIs (DCI#1-#4) which schedule PDSCH#1-#4 respectively.

[0250] The beam indicator DCI may indicate y indicator TCI states. These indicator TCI states may be identified by an index corresponding to the indicator TCI state.

[0251] For example, DCI#0 indicates four indicator TCI states, each of which is identified by a first to fourth index (see Figure 5B).

[0252] The UE may update the indicated TCI state to one indicated by a new beam indicated DCI (see, for example, the correspondence shown in Figure 5C) after a certain time has elapsed (beam application time (BAT), the time indicated by BeamAppTime_r17) since the transmission of the HARQ-ACK corresponding to PDSCH#1-#4.

[0253] The UE may determine which TCI state to apply from among the indicated TCI states based on the beam indicated DCI, based on specific fields included in the scheduling DCI.

[0254] For example, the UE may indicate an index for one or more (e.g., two) instruction TCI states based on specific fields included in the scheduling DCI.

[0255] When the UE is instructed with an index related to a plurality of indicated TCI states, the UE may determine at least one of the TCI state (or states) to be applied and the order of the TCI states among the plurality of indicated TCI states based on a specific method.

[0256] The specific method will be described in detail below.

[0257] In the example shown in FIG. 5A, it shows that DCI #1 applies the indicated TCI state of the first index to PDSCH #1, DCI #2 applies the indicated TCI state of the second index to PDSCH #2, DCI #3 applies both the indicated TCI state of the first index (the first TCI state) and the indicated TCI state of the second index (the second TCI state) to PDSCH #3, and DCI #4 applies both the indicated TCI state of the third index (the first TCI state) and the indicated TCI state of the fourth index (the second TCI state) to PDSCH #4.

[0258] The following describes the specific method for determining the indicated TCI state to be applied to each channel / signal.

[0259] The UE may follow at least one of the methods described in Embodiments 1-1 to 1-4 below.

[0260] 《Embodiment 1-1》 The UE may determine at least one of the TCI state to be applied to each channel / signal and the order of the TCI states based on a specific field included in the scheduling / triggering DCI.

[0261] The UE may select / determine x (one or more) TCI states from y indicated TCI states based on the specific field.

[0262] The specific field may be a new field defined after Rel. 18. [[ID=~32]]

[0263] In this disclosure, a scheduling / triggering DCI may be a DCI that schedules a channel (e.g., PUSCH / PDSCH / PUCCH) or a DCI that triggers a signal (e.g., SRS / CSI-RS). A scheduling / triggering DCI may be in a specific DCI format (e.g., DCI format 0_1 / 0_2 / 1_1 / 1_2).

[0264] The specific field may be a field that indicates one of the indices of y indicated TCI states.

[0265] The correspondence between a code point in a specific field and an index of an indicated TCI state may be defined / configured / instructed / notified to the UE (see Figure 6B). The UE may determine the TCI state (index of the indicated TCI state) to apply to the scheduled / triggered channel / signal based on the specific field and this correspondence.

[0266] This correspondence may be defined in the specifications beforehand, set / instructed to the UE by higher-layer signaling (RRC / MAC CE), or indicated by a specific DCI.

[0267] The specific DCI may be, for example, a beam-indicating DCI. The UE may update the index corresponding to each code point in a particular field using the beam-indicating DCI.

[0268] The specific field may have a specific number of bits (e.g., 2 bits). This specific number of bits may be defined in the specification beforehand, or it may be set in the UE by upper-layer signaling (RRC / MAC CE).

[0269] The UE may apply the indicated TCI state corresponding to the index indicated in a specific field to the channel (e.g., PDSCH / PUSCH / PUCCH) / signal (e.g., CSI-RS / TRS) corresponding to the scheduling / triggering DCI.

[0270] Figures 6A and 6B show an example of the application of the instruction TCI state according to Embodiment 1-1. In the example shown in Figure 6A, the UE is scheduled PDSCH#4 and PUCCH#4 by the scheduling DCI (DCI#4).

[0271] In the example shown in Figure 6A, the UE is instructed to use a field included in the scheduling DCI to specify the index of the TCI state to apply to the channel. In the example shown in Figure 6B, this field indicates the code point "00".

[0272] Based on the correspondence shown in Figure 6B above, the UE is instructed to select a first index corresponding to code point "00". The UE then applies the instruction TCI state corresponding to this first index to PDSCH#4 and PUCCH#4. In the example shown in Figure 6B, TCI state #1, which is the instruction TCI state of the first index (joint / DL TCI state), is applied to PDSCH#4, and TCI state #1, which is the instruction TCI state of the first index (joint / UL TCI state), is applied to PUCCH#4.

[0273] Note that the DL channel / signal in this embodiment is not limited to the PDSCH / RS scheduled / triggered by the scheduling / triggering DCI. The DL channel / signal in this embodiment may be any other PDSCH (e.g., a PDSCH other than the scheduled PDSCH) or any other RS ​​(e.g., an RS other than the triggered RS).

[0274] Also, the UL channels / signals in this embodiment are not limited to the PUSCH / PUCCH / RS scheduled / triggered by scheduling / triggering DCI. The UL channels / signals in this embodiment may be any other PUSCH / PUCCH (for example, PUSCH / PUCCH other than the scheduled PUSCH / PUCCH), or any other RS (for example, RS other than the triggered RS).

[0275] [Variation of Embodiment 1-1] The specific fields included in the scheduling DCI may be one or more.

[0276] The UE may determine the TCI state to be applied to each channel / signal based on a plurality (for example, two) of specific fields (here, the first field and the second field).

[0277] The UE may be instructed by the first field with a first index regarding the indicated TCI state, and may be instructed by the second field with a second index regarding the indicated TCI state.

[0278] When the TCI state to be applied to the channel / signal is one, the UE may determine the one TCI state based on the first (or second) field.

[0279] When the TCI states to be applied to the channel / signal are plural (for example, two), the UE may determine the two TCI states based on the first field and the second field.

[0280] The correspondence between the index indicated in the first field (the first index) and the index indicated in the second field (the second index) may be the same. Alternatively, the correspondence between the index indicated in the first field (the first index) and the index indicated in the second field (the second index) may be separate (different) correspondences.

[0281] Figures 7A and 7B show an example of the application of the instruction TCI state related to the variation of Embodiment 1-1. In the example shown in Figure 7A, the UE is scheduled to perform PDSCH#4 and PUCCH#4 (PUCCH#4-1 and PUCCH#4-2) by the scheduling DCI (DCI#4).

[0282] In the example shown in Figure 7A, the UE is instructed of the TCI state index to apply to the channel using fields included in the scheduling DCI. In the example shown in Figure 7A, the first index field indicates code point "00", and the second index field indicates code point "10".

[0283] UE determines the applicable TCI state based on the correspondence shown in Figure 7B. The example shown in Figure 7B illustrates the case where the correspondence for the first index and the correspondence for the second index are the same.

[0284] In the example shown in Figure 7A, there is one TCI state applied to PDSCH#4. In this case, the UE applies the indicated TCI state (in this case, TCI state #1) corresponding to the first index indicated by code point "00" to PDSCH#4.

[0285] Furthermore, in the example shown in Figure 7B, there are two TCI states applied to PUCCH#4 (PUCCH#4-1 and PUCCH#4-2). In this case, the UE applies the indicated TCI states (in this case, TCI state #1 and TCI state #4) corresponding to the second index indicated by code point "10" to PUCCH#4 (PUCCH#4-1 and PUCCH#4-2, respectively).

[0286] In this disclosure, a channel / signal to which multiple (e.g., two) TCI states are applied may mean a channel / signal that utilizes multiple TRPs.

[0287] Furthermore, the behavior of DCI fields that indicate one or more indices, as described in Figures 7A and 7B above, may only be used / applied when PUCCH (repeat) for multi-TRP is set for the UE. If PUCCH (repeat) for multi-TRP is not set, the UE may assume that there are no DCI fields that indicate one or more indices.

[0288] Furthermore, in this disclosure, if an operation requiring one indicator TCI state (e.g., a single TRP operation) is configured and multiple indicator TCI states are indicated, the UE may determine one indicator TCI state from the multiple indicator TCI states using RRC / MAC CE / DCI (new DCI field).

[0289] The number of bits in the new DCI field may be determined based on the number of indicated TCI states (e.g., y).

[0290] Figure 8 shows an example of information regarding the indicated TCI states and the number / order of indicated TCI states indicated by the scheduling DCI. In the example shown in Figure 8, the correspondence between the code points of a specific field included in the scheduling DCI and the indicated TCI states and the number / order of indicated TCI states indicated by the beam indicated DCI is shown.

[0291] The UE may use the specific fields described above to indicate a single code point representing that correspondence.

[0292] In the example shown in Figure 8, code point "00" indicates that one instruction TCI state is applied to the corresponding PDSCH, and that the applied TCI state is the first TCI state. Similarly, code point "01" indicates that one instruction TCI state is applied to the corresponding PDSCH, and that the applied TCI state is the second TCI state.

[0293] Furthermore, in the example shown in Figure 8, code point "10" indicates that two instruction TCI states are applied to the corresponding PDSCH, and that the applied TCI states are, first, the first TCI state, and then the second TCI state. Similarly, code point "11" indicates that two instruction TCI states are applied to the corresponding PDSCH, and that the applied TCI states are, first, the second TCI state, and then the first TCI state.

[0294] For example, if a UE is instructed by a field of the scheduling DCI (e.g., the TCI field) to specify an indicative TCI state for a first index and an indicative TCI state for a second index, and a specific field of the scheduling DCI instructs the application of one TCI state and the application of the first TCI state (i.e., the code point "00"), then the UE applies the indicative TCI state for the first index to the PDSCH corresponding to the scheduling DCI.

[0295] The correspondence shown in Figure 8 may be defined in the specifications beforehand, or it may be set / updated for the UE using higher-layer signaling (RRC / MAC CE).

[0296] Embodiment 1-2 The UE may determine, based on specific fields included in the scheduling / triggering DCI, at least one of the TCI states to apply to each channel / signal and the order of the TCI states.

[0297] Based on the specific field, the UE may select / determine x (one or more) TCI states from y indicated TCI states.

[0298] The specific field in question may be an existing field (as defined up to Rel. 17). The specific field in question may be an extended version of an existing field (as defined up to Rel. 17).

[0299] For a specific DL channel (e.g., PDSCH), a specific field included in the DCI may be used to indicate x TCI states.

[0300] The UE may follow at least one of the following embodiments 1-2-1 and 1-2-2 to determine x TCI states for a particular DL channel.

[0301] [Embodiment 1-2-1] The UE may determine the instruction TCI state to apply to a particular DL channel (e.g., PDSCH) based on specific fields included in the DCI.

[0302] The DCI in question may be, for example, a DCI that schedules the specific channel (e.g., DCI format 1_1 / 1_2).

[0303] The DCI in question may be, for example, a DCI other than a beam-indicating DCI.

[0304] The specific field in question may be an existing field (as defined up to Rel. 17). The specific field in question may be an extended version of an existing field (as defined up to Rel. 17).

[0305] The specific field in question may not be a field used in the operation of Rel.17.

[0306] The specific field in question may be, for example, a TCI status (TCI) field. Alternatively, the specific field may be a field other than a TCI status (TCI) field.

[0307] The UE may apply the TCI state indicated in the particular field to the particular DL channel (e.g., PDSCH) and the UL channel associated with that particular DL channel (e.g., PUCCH).

[0308] Figure 9 shows an example of TCI state indication according to Embodiment 1-2-1. In the example shown in Figure 9, the code points of the TCI field in the scheduling DCI correspond to one or more (two) indexes of applicable TCI states and at least one of the first to fourth joint TCI states.

[0309] In the example shown in Figure 9, the UE determines the index of the TCI state to apply to the DL channel scheduled in the scheduling DCI based on the indicated TCI field. The TCI state applied by the UE is the indicated TCI state by the currently applied beam indicated DCI. In the example shown in Figure 9, the UE does not apply the indicated TCI states (the 1st to 4th joint TCI states) corresponding to the TCI fields in the scheduling DCI to the scheduled DL channel.

[0310] Furthermore, the instruction TCI state (the first to fourth joint TCI states) corresponding to the TCI field in the scheduling DCI may indicate the TCI state that is applied after the BAT has elapsed following the transmission of the UL channel (HARQ-ACK) corresponding to the DL channel scheduled in the scheduling DCI.

[0311] [Embodiment 1-2-2] The UE may determine the instruction TCI state to apply to a particular DL channel (e.g., PDSCH) based on specific fields included in the DCI.

[0312] The DCI in question may be, for example, a specific DCI (e.g., DCI format 1_1 / 1_2).

[0313] The specific DCI may be a DCI with DL assignment, a DCI that schedules DL channels (PDSCH), or a DCI without DL assignment, or a DCI that does not schedule DL channels (PDSCH).

[0314] The specific field in question may be an existing field (as defined up to Rel. 17). The specific field in question may be an extended version of an existing field (as defined up to Rel. 17).

[0315] The UE may apply the TCI state indicated in the particular field to the particular DL channel (e.g., PDSCH) and the UL channel associated with that particular DL channel (e.g., PUCCH).

[0316] Figure 10 shows an example of TCI state indication according to Embodiment 1-2-2. In the example shown in Figure 10, the code point of the TCI field in the scheduling DCI corresponds to either one or more (two) indexes of applicable TCI states and at least one of the first to fourth joint TCI states.

[0317] In the example shown in Figure 10, the UE determines the index of the TCI state to apply to the DL channel scheduled by the scheduling DCI, based on the indicated TCI field.

[0318] If the UE is given one or more (two) TCI state indices and corresponding code points (for example, code points "000"-"011" in Figure 10) to apply, it does not update the indicated TCI state, but applies the indicated TCI state corresponding to the indicated index from among the already indicated (y) indicated TCI states to the channel / signal.

[0319] If a code point (for example, code points "100" to "111" in Figure 10) is indicated for at least one of the first to fourth joint TCI states, the UE may update several (y) already indicated TCI states to the indicated TCI state indicated by that code point.

[0320] The correspondence shown in Figure 10 may also be set / instructed to the UE using higher-layer signaling (RRC / MAC CE). As shown in Figure 10, the correspondence may or may not include information (column) indicating whether or not the TCI status has been updated.

[0321] Note that the correspondence shown in Figure 10 may be a correspondence between DCI with DL assignment and DCI scheduling DL channels (PDSCH), or it may be a correspondence between DCI without DL assignment and DCI not scheduling DL channels (PDSCH).

[0322] Figure 11 shows another example of TCI state indication according to Embodiment 1-2-2. In the example shown in Figure 11, the code point of the TCI field in the scheduling DCI corresponds to at least one of the first to fourth joint TCI states.

[0323] Figure 11, compared to Figure 10 above, shows that every code point in the indicated TCI field corresponds to at least one of the first to fourth joint TCI states.

[0324] In this case, the UE may update any of the code points indicated to update any (y) already indicated TCI states to the TCI states indicated by that code point.

[0325] The correspondence shown in Figure 11 may also be set / instructed to the UE using higher-layer signaling (RRC / MAC CE). As shown in Figure 11, the correspondence may or may not include information (column) indicating whether or not the TCI status has been updated.

[0326] Note that the correspondence shown in Figure 11 may also relate to DCI without DL assignment, or DCI without scheduling a DL channel (PDSCH).

[0327] The correspondence shown in Figure 11 may be used in at least one of the following cases: when there is no PDSCH schedule, and when it is not necessary to notify the TCI state index to be applied for PDSCH. In this case, the application of the TCI state to PUCCH may be the embodiment 1-2-1 described above, or the embodiment 1-3 described later.

[0328] Embodiments 1-3 The UE may determine, based on specific fields included in the scheduling / triggering DCI, at least one of the TCI states to apply to each channel / signal and the order of the TCI states.

[0329] Based on the specific field, the UE may select / determine x (one or more) TCI states from y indicated TCI states.

[0330] The specific field in question may be an existing field (as defined up to Rel. 17). The specific field in question may be an extended version of an existing field (as defined up to Rel. 17).

[0331] The specific field in question may be, for example, at least one of the PRI field and the CCE index field.

[0332] For a specific UL channel (e.g., PUCCH), a specific field included in the DCI may be used to indicate x TCI states.

[0333] For the UE, it is possible to set / activate / instruct x indices corresponding to TCI states for each PUCCH resource (resource group) in advance using upper layer signaling (RRC / MAC CE) / physical layer signaling (DCI).

[0334] For example, the UE may determine the corresponding (x or y) TCI states for each PUCCH resource (resource group) based on the PUCCH resource instructions provided by DCI.

[0335] Figure 12 shows an example of TCI status instruction according to Embodiment 1-3. In the example shown in Figure 12, PUCCH resource groups (PUCCH resource groups #1-#4) and PUCCH resources (PUCCH resources #1-#8) are set for the UE. These PUCCH resources / resource sets are set using the PUCCH settings (PUCCH-Config) in a BWP (BWP#1) within a CC (CC#1). The correspondence between PUCCH resource groups and PUCCH resources is as shown in Figure 12.

[0336] Furthermore, as shown in Figure 12, an index relating to the TCI state to be applied is associated with each PUCCH resource group. Based on this associated index and the selected PUCCH resource (PRI / CCE index field), the UE determines x TCI states from the y TCI states indicated by the beam instruction DCI.

[0337] In this way, by setting / determining / instructing the index of the instructed TCI state on a per-PUCCH resource / resource group basis, it is possible to switch between single TRP and multi-TRP operation in the scheduling DCI (which includes the PRI / CCE index field).

[0338] Furthermore, the setting / indication / updating of the TCI status index on a PUCCH resource unit / resource group basis may be performed using upper-layer signaling (RRC / MAC CE) / DCI (beam-indicating DCI).

[0339] The following describes cases in which the indicated TCI state is updated by the beam indicated DCI / MAC CE.

[0340] In embodiments 1-3-1 and 1-3-2 below, we assume that one or more PUCCH resources #A, to which one instruction TCI state is associated (set), and PUCCH resources #B, to which multiple (e.g., two) instruction TCI states are associated (set), are each set using upper layer signaling (RRC).

[0341] [Implementation 1-3-1] The UE may be instructed by the beam instruction DCI / MAC CE to update a unified TCI state (instructed TCI state) to a single TCI state (instructed TCI state).

[0342] The UE may update PUCCH resource #A to a new TCI state as instructed.

[0343] The UE may update PUCCH resource #B to a single new TCI state indicated (Option 1-3-1-1). That is, the UE may update all of the multiple (e.g., two) indicated TCI states associated with PUCCH resource #B to a single new TCI state indicated.

[0344] The UE does not have to update PUCCH resource #B to a new indicated TCI state (Option 1-3-1-2). The UE may ignore the instruction to update PUCCH resource #B to a single indicated TCI state. PUCCH resource #B, which has multiple (e.g., two) indicated TCI states, does not have to have its TCI state updated by a beam instruction DCI / MAC CE indicating a single TCI state.

[0345] The UE may update at least one (or part of) TCI states associated with PUCCH resource #B to a new TCI state indicated (Option 1-3-1-3). For example, if a PUCCH resource is associated with a first TCI state and a second TCI state, the UE may decide to update either the first or second TCI state to a new TCI state indicated.

[0346] In option 1-3-1-3, the TCI state to be updated (for example, the first TCI state or the second TCI state described above) may be specified in advance in the specification, or it may be set in the UE by upper layer signaling (RRC / MAC CE).

[0347] [Embodiment 1-3-2] The UE may be instructed by the beam instruction DCI / MAC CE to update a unified TCI state (instruction TCI state) to multiple (e.g., two) TCI states (instruction TCI states).

[0348] The UE may update PUCCH resource #A to a new set of multiple (e.g., two) TCI states as instructed (Option 1-3-2-1).

[0349] The UE does not have to update PUCCH resource #A to multiple (e.g., two) indicated TCI states (Option 1-3-2-2). The UE may ignore instructions to update PUCCH resource #A to multiple (e.g., two) indicated TCI states. PUCCH resource #A associated with one indicated TCI state does not have to have its TCI state updated by beam instructions DCI / MAC CE indicating multiple (e.g., two) TCI states.

[0350] The UE may update one TCI state associated with PUCCH resource #A to one of several (e.g., two) new TCI states indicated (Option 1-3-2-3). For example, if a beam indicator DCI / MAC CE indicates updating a first TCI state and a second TCI state, the UE may decide to update one TCI state associated with PUCCH resource #A to either the first TCI state or the second TCI state.

[0351] In option 1-3-2-3, the TCI state used for the update (for example, the first TCI state or the second TCI state described above) may be specified in advance in the specification, or it may be set in the UE by upper layer signaling (RRC / MAC CE).

[0352] The UE may update PUCCH resource #B to a new set of (e.g., two) TCI states as instructed.

[0353] In the above embodiments 1-3-1 / 1-3-2, the UE may select one TCI state from a plurality (e.g., two) of TCI states based on a specific method.

[0354] Such specific methods may be defined in the specifications beforehand, for example. For example, the UE may select the first (or second / last) TCI state from among several (e.g., two) TCI states. Alternatively, for example, the UE may select the TCI state with the lowest (or highest) index from among several (e.g., two) TCI states.

[0355] Furthermore, the specific method may be based on, for example, the correspondence between TCI status / PUCCH and an index related to TRP (e.g., CORESET pool index / TRP ID / TRP index). The UE may determine which TCI status to update based on the TRP associated with the TCI status / PUCCH.

[0356] An association may be established between a PUCCH resource (resource group) and an index related to the TRP for the UE. If an index related to the TRP is associated with an indicated TCI state (for example, if at least one of the first / second TCI states and the CORESET pool index is associated with the beam indicated DCI), the UE may decide to update the TCI state associated with that index related to the TRP for each PUCCH resource (resource group).

[0357] Embodiments 1-4 The UE may determine, based on specific fields included in the scheduling / triggering DCI, at least one of the TCI states to apply to each channel / signal and the order of the TCI states.

[0358] Based on the specific field, the UE may select / determine x (one or more) TCI states from y indicated TCI states.

[0359] The specific field in question may be at least one of the following: an existing field (defined up to Rel. 17) (or a field that is an extension of an existing field) and a newly defined field (defined from Rel. 18 onwards).

[0360] The existing field in question may be, for example, an SRS resource set indicator field. Alternatively, the existing field may be, for example, a field other than an SRS resource set indicator field.

[0361] For a specific UL channel (e.g., PUSCH), a specific field included in the DCI may be used to indicate x TCI states.

[0362] [Embodiment 1-4-1] If multiple (e.g., two) SRS resource sets are configured for specific purposes (e.g., codebooks / non-codebooks), the UE may use a specific field (e.g., an SRS resource set indicator field) to indicate which TCI state index to apply to the channel (e.g., PUSCH).

[0363] In this case, the UE may decide whether to repeat the PUSCH operation using a single TRP or a PUSCH operation using multiple TRPs, based on a specific field (for example, the SRS resource set indicator field).

[0364] Figure 13 shows an example of a field in DCI according to Embodiment 1-4. In the example shown in Figure 13, the association between the code point of the SRS resource set indicator field and the single TRP / multi-TRP scheme is shown.

[0365] For example, if the UE is instructed to use a single TRP operation with the first TRP (TRP#1) when it is directed to the code point "0 (00)" in the SRS resource set indicator field.

[0366] For example, if the UE is instructed to use a single TRP with a second TRP (TRP#2) when it is directed to the code point "1(01)" in the SRS resource set indicator field, it will determine that it is instructed to use a second TRP (TRP#2).

[0367] For example, if the UE is instructed to use code point "2(10)" in the SRS resource set indicator field, it will determine that it is instructed to perform a multi-TRP operation using the first TRP (TRP#1) and the second TRP (TRP#2). In this case, the UE will determine that it is instructed to apply the first TCI state to the channel related to the first TRP and the second TCI state to the channel related to the second TRP.

[0368] For example, if the UE is instructed to use code point "3(11)" in the SRS resource set indicator field, it will determine that it is instructed to perform a multi-TRP operation using the first TRP (TRP#1) and the second TRP (TRP#2). In this case, the UE will determine that it is instructed to apply the first TCI state to the channel related to the second TRP, and the second TCI state to the channel related to the first TRP.

[0369] Furthermore, the first TRP may correspond to the first SRS resource set of the CB / NCB (in Rel. 17). In Rel. 18 and later, the UE may determine the first TRP to be the first TCI state. Also, the second TRP may correspond to the second SRS resource set of the CB / NCB (in Rel. 17). In Rel. 18 and later, the UE may determine the second TRP to be the second TCI state.

[0370] [Embodiment 1-4-2] The specific field for selecting / determining x (one or more) TCI states from y indicated TCI states may be one of the fields described in Embodiment 1-1 above.

[0371] In other words, the above embodiment 1-1 may be used for selecting / determining a TCI state to apply to a specific UL channel (e.g., PUSCH).

[0372] For example, the specific fields described in Embodiment 1-1 above may indicate one or more indexes. The behavior of DCI fields indicating one or more indexes may only be used / applied when a multi-TRP PUSCH iteration (two SRS resource sets with usage CB / NCB) is configured for the UE. If a multi-TRP PUSCH iteration (two SRS resource sets with usage CB / NCB) is not configured, the UE may assume that there are no DCI fields indicating one or more indexes.

[0373] The embodiments 1-4-1 and 1-4-2 described above may be used in combination or individually.

[0374] For example, the UE may use upper-layer signaling (RRC / MAC CE) to determine which of the above embodiments 1-4-1 and 1-4-2 is to be used.

[0375] According to the first embodiment described above, the instruction TCI state to be applied to each channel / signal can be appropriately determined, and the DCI can be used to switch between single-TRP operation and multi-TRP operation based on the number of TCI states applied.

[0376] <Variation> In each embodiment of this disclosure, the fields relating to the TCI state index applied to each channel / signal may not be included in a particular DCI format.

[0377] The specific DCI format in question may be, for example, a DCI format for scheduling a PUSCH (e.g., DCI format 0_0 / 0_1).

[0378] If a particular DCI format does not include a field for that index, the UE may derive the TCI state index to apply to the channel / signal scheduled / triggered in that particular DCI format based on the field for that index indicated in a DCI format other than that particular DCI format.

[0379] If a particular DCI format does not include a field for that index, the UE may determine the TCI state index to apply to channels / signals scheduled / triggered in that particular DCI format using a predefined index (e.g., minimum / maximum index) or a setting via upper-layer signaling (RRC / MAC CE).

[0380] <Supplement> [Notification of information to UE] In the embodiments described above, notification of any information from a Network (NW) (e.g., a Base Station (BS)) to a UE (in other words, reception of any information from a BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0381] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0382] If the above notification is made by a DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

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

[0384] [Notification of information from UE] In the embodiments described above, notification of any information from the UE (to the NW) (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0385] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID, not specified in existing standards, in the MAC subheader.

[0386] If the above notice is issued by the UCI, the notice may be sent using PUCCH or PUSCH.

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

[0388] [Regarding the application of each embodiment] At least one of the embodiments described above may be applied if certain conditions are met. These conditions may be specified in a standard or notified to the UE / BS using upper-layer signaling / physical layer signaling.

[0389] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0390] The specific UE capability may represent at least one of the following: • To support specific processing / operation / control / information for at least one of the above embodiments (e.g., switching between single TRP and multi-TRP operation using a unified TCI state), • Support for notifying DCI of the index of the instruction TCI state to be applied to each channel / signal. • The number of y and x that support at least one of them.

[0391] Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).

[0392] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0393] Furthermore, at least one of the embodiments described above may be applied when the UE is configured / activated / triggered by upper layer signaling / physical layer signaling to configure / activate specific information (or perform the actions of the embodiments described above) related to the embodiments described above. For example, such specific information may be information indicating the activation of switching between single-TRP and multi-TRP operation using a unified TCI state, or arbitrary RRC parameters for a particular release (e.g., Rel. 18 / 19).

[0394] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 / 17 may be applied.

[0395] (Note A) The following invention is added with respect to one embodiment of this disclosure. [Note A-1] A receiving unit that receives a first downlink control information (DCI) used for beam direction and a second DCI that schedules or triggers downlink (DL) signals, A terminal having a control unit that determines, based on a specific field included in the second DCI, one or more Transmission Configuration Indication (TCI) states to be applied to the DL signal from a plurality of Transmission Configuration Indication (TCI) states indicated in the first DCI, and determines whether the DL signal is a signal that uses one transmit / receive point (TRP) or a signal that uses multiple TRPs. [Note A-2] If a specific field indicates one TCI state, the control unit determines that the DL signal is a signal that utilizes one transmission / reception point. The terminal as described in Appendix A-1, in which the control unit determines that the DL signal is a signal that utilizes the multiple transmission and reception points when multiple TCI states are indicated by the aforementioned specific field. [Note A-3] The terminal described in Appendix A-1 or Appendix A-2, wherein the specific field indicates at least one of the number of TCI states applied to the DL signal and the order of the TCI states applied to the DL signal. [Note A-4] The aforementioned DL signal is a physical downlink shared channel (PDSCH), The terminal described in any of Appendix A-1 to A-3, wherein the control unit determines the TCI state to be applied to the physical uplink control channel corresponding to the PDSCH based on specific fields of the first DCI and the second DCI.

[0396] (Note B) The following invention is added with respect to one embodiment of this disclosure. [Note B-1] A receiving unit that receives a first downlink control information (DCI) used for beam direction and a second DCI that schedules or triggers an uplink (UL) signal, A terminal having a control unit that determines, based on a specific field included in the second DCI, one or more Transmission Configuration Indication (TCI) states to be applied to the UL signal from a plurality of Transmission Configuration Indication (TCI) states indicated in the first DCI, and determines whether the UL signal is a signal that utilizes one transmit / receive point (TRP) or a signal that utilizes multiple TRPs. [Note B-2] If a specific field indicates one TCI state, the control unit determines that the UL signal is a signal that utilizes one transmission / reception point. When multiple TCI states are indicated by the aforementioned specific field, the control unit determines that the UL signal is a signal that utilizes the multiple transmission and reception points, as described in Appendix B-1. [Note B-3] The terminal as described in Appendix B-1 or Appendix B-2, wherein the specific field indicates at least one of the number of TCI states to apply to the UL signal and the order of the TCI states to apply to the UL signal. [Note B-4] The aforementioned UL signal is a physical uplink control channel (PUCCH), The control unit further determines one or more TCI states to apply to the PUCCH based on an index set for each PUCCH resource or PUCCH resource group, as described in any of the terminals in Appendix B-1 to B-3.

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

[0398] Figure 14 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0399] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and so on.

[0400] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

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

[0402] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0403] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

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

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

[0408] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

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

[0410] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0411] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0413] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0414] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0416] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0417] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0418] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0419] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0420] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

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

[0423] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

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

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

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

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

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

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

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

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

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

[0433] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.

[0434] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0435] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

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

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

[0438] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0439] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing 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.

[0440] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0441] The transmitting / receiving unit 120 may transmit a first downlink control information (DCI) used for beam direction and a second DCI for scheduling or triggering a downlink (DL) signal. The control unit 110 may use specific fields included in the second DCI to indicate one or more Transmission Configuration Indication (TCI) states to apply to the DL signal from among a plurality of Transmission Configuration Indication (TCI) states indicated in the first DCI, and may indicate whether the DL signal is a signal that utilizes one transmit / receive point (TRP) or a signal that utilizes multiple TRPs (0th and 1st embodiments).

[0442] The transmitting / receiving unit 120 may transmit a first downlink control information (DCI) used for beam direction and a second DCI for scheduling or triggering an uplink (UL) signal. The control unit 120 may use specific fields included in the second DCI to indicate one or more Transmission Configuration Indication (TCI) states to apply to the UL signal from among a plurality of Transmission Configuration Indication (TCI) states indicated in the first DCI, and may indicate whether the UL signal is a signal that utilizes one transmit / receive point (TRP) or a signal that utilizes multiple TRPs (0th and 1st embodiments).

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

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

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

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

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

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

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

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

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

[0452] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

[0453] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

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

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

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

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

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

[0459] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0460] The transmitting / receiving unit 220 may receive a first downlink control information (DCI) used for beam direction and a second DCI for scheduling or triggering a downlink (DL) signal. The control unit 210 may determine one or more Transmission Configuration Indication (TCI) states to apply to the DL signal from a plurality of Transmission Configuration Indication (TCI) states indicated by the first DCI, based on a specific field included in the second DCI, and determine whether the DL signal is a signal that utilizes one transmit / receive point (TRP) or a signal that utilizes multiple TRPs (0th and 1st embodiments).

[0461] If the specific field indicates one TCI state, the control unit 210 may determine that the DL signal is a signal that utilizes one transmit / receive point. If the specific field indicates multiple TCI states, the control unit 210 may determine that the DL signal is a signal that utilizes multiple transmit / receive points (0th and 1st embodiments).

[0462] The specific field may indicate at least one of the number of TCI states to be applied to the DL signal and the order in which the TCI states to be applied to the DL signal (first embodiment).

[0463] The DL signal may be a physical downlink shared channel (PDSCH). The control unit 210 may determine the TCI state to apply to the physical uplink control channel corresponding to the PDSCH based on specific fields of the first DCI and the second DCI (first embodiment).

[0464] The transmitting / receiving unit 220 may receive a first downlink control information (DCI) used for beam direction and a second DCI for scheduling or triggering an uplink (UL) signal. The control unit 210 may determine, based on a specific field included in the second DCI, one or more Transmission Configuration Indication (TCI) states indicated in the first DCI to apply to the UL signal, and determine whether the UL signal is a signal that utilizes one transmit / receive point (TRP) or a signal that utilizes multiple TRPs (0th and 1st embodiments).

[0465] If the specific field indicates one TCI state, the control unit 210 may determine that the UL signal is a signal that utilizes the one transmit / receive point. If the specific field indicates multiple TCI states, the control unit 210 may determine that the UL signal is a signal that utilizes the multiple transmit / receive points (0th and 1st embodiments).

[0466] The specific field may indicate at least one of the number of TCI states to apply to the UL signal and the order in which the TCI states to apply to the UL signal (first embodiment).

[0467] The UL signal may be a physical uplink control channel (PUCCH). The control unit 210 may further determine one or more TCI states to apply to the PUCCH based on an index set for each PUCCH resource or PUCCH resource group (first embodiment).

[0468] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0469] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0470] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 17 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0471] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0472] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

[0474] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

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

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

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

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

[0479] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0481] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0482] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0483] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0484] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

[0485] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0486] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0487] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0488] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0489] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0490] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0491] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0492] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0493] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0494] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

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

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

[0497] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0498] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0499] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0500] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0501] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0503] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0505] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0506] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0507] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0508] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0509] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0510] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0511] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0512] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0513] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0514] 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0515] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0516] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0517] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0519] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

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

[0521] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0522] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0523] Figure 18 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

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

[0525] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0526] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression signal of accelerator pedal 43 acquired by accelerator pedal sensor 55, brake pedal depression signal of brake pedal 44 acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by object detection sensor 58.

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

[0528] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0529] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0530] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0531] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0533] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0534] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0535] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.

[0536] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0537] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0538] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0539] Each aspect / embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0540] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0541] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0542] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0543] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0544] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0545] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

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

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

[0548] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

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

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

[0551] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

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

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

[0554] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives a first downlink control information (DCI) used to indicate multiple Transmission Configuration Indication (TCI) states and a second DCI for scheduling an uplink (UL) channel, The system includes a control unit that, based on a specific field included in the second DCI, determines from the plurality of TCI states indicated in the first DCI one or more TCI states to apply to the UL channel, and determines whether the UL channel is a channel that uses one transmit / receive point (TRP) or a channel that uses multiple TRPs, The control unit determines, if the second DCI does not include the specific field, the index of the TCI state to apply to the UL channel using the setting by upper layer signaling.

2. The terminal according to claim 1, wherein the specific field is a field that indicates an index of one or more TCI states to be applied to the UL channel.

3. A step of receiving a first downlink control information (DCI) used to indicate a plurality of Transmission Configuration Indication (TCI) states and a second DCI for scheduling an uplink (UL) channel, The steps include: determining, based on a specific field included in the second DCI, one or more TCI states to apply to the UL channel from the multiple TCI states indicated in the first DCI, and determining whether the UL channel is a channel that uses one transmit / receive point (TRP) or a channel that uses multiple TRPs; A wireless communication method for a terminal, comprising the step of determining the index of the TCI state to apply to the UL channel using settings by upper layer signaling if the second DCI does not include the specific field.

4. A transmission unit that transmits to a terminal a first downlink control information (DCI) used to indicate multiple Transmission Configuration Indication (TCI) states and a second DCI for scheduling an uplink (UL) channel, The system includes a control unit that uses a specific field included in the second DCI to indicate one or more TCI states to apply to the UL channel from the plurality of TCI states indicated in the first DCI, and indicates whether the UL channel is a channel that uses one transmit / receive point (TRP) or a channel that uses multiple TRPs, The control unit controls the transmission of upper-layer signaling that causes the terminal to determine the index of the TCI state to apply to the UL channel if the second DCI does not include the specific field, at the base station.

5. A system including a terminal and a base station, The aforementioned terminal is A receiving unit that receives a first downlink control information (DCI) used to indicate multiple Transmission Configuration Indication (TCI) states and a second DCI for scheduling an uplink (UL) channel. The system includes a control unit that, based on a specific field included in the second DCI, determines from the plurality of TCI states indicated in the first DCI one or more TCI states to apply to the UL channel, and determines whether the UL channel is a channel that uses one transmit / receive point (TRP) or a channel that uses multiple TRPs, If the second DCI does not include the specific field, the control unit determines the index of the TCI state to apply to the UL channel using the setting by upper layer signaling. The aforementioned base station is A transmitting unit that transmits the first DCI and the second DCI to the terminal, The system includes a control unit that uses the specific field included in the second DCI to indicate one or more TCI states to apply to the UL channel from the plurality of TCI states indicated in the first DCI, and indicates whether the UL channel is a channel that utilizes one TRP or a channel that utilizes multiple TRPs, The control unit of the base station controls the transmission of upper-layer signaling that causes the terminal to determine the index of the TCI state to apply to the UL channel if the second DCI does not include the specific field.

Images