Terminal, wireless communication method, base station, and system

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that determines which of a first unified transmission configuration indication (TCI) state that does not involve the use of a plurality of transmission and reception points (TRP) and a second unified TCI state that involves the use of a plurality of TRPs is to be used; and a transmission and reception unit that uses the first unified TCI state to perform the transmission and reception of a signal to / from a single TRP or uses the second unified TCI state to perform the transmission and reception of a signal to / from a plurality of TRPs based on a single downlink control information (DCI). This one aspect of the present disclosure makes it possible to appropriately apply TCI states.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

[0006] In addition, in Rel. 17, the use of a TCI state (unified TCI state) applicable to multiple types of signals (channels / reference signals) is being considered. Furthermore, in Rel. 18 and later, the use of a unified TCI state in systems using multiple transmission / reception points (TRPs) is being considered.

[0007] However, there has been insufficient consideration as to how to switch between the operation according to the unified TCI state defined in Rel. 17 and the operation according to the unified TCI state defined in Rel. 18 and later. If this consideration is insufficient, communication may not be performed appropriately, and communication throughput may decrease.

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

[0009] A terminal according to one aspect of the present disclosure has a control unit that determines whether to use a first unified Transmission Configuration Indication state (TCI) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state that uses the multiple TRPs, and a transceiver unit that uses the first unified TCI state to transmit and receive signals for a single TRP, or uses the second unified TCI state to transmit and receive signals to which multiple TRPs based on a single downlink control information (DCI) are applied.

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

[0011] Figures 1A and 1B are diagrams illustrating an example of a unified / common TCI framework. Figures 2A and 2B are diagrams illustrating an example of a DCI-based TCI status indication. Figures 3A and 3B are diagrams illustrating an example of an RRC field and a DCI field in Rel. 17. Figure 4 is a diagram illustrating an example of a unified TCI status activation / deactivation MAC CE. Figure 5 is a diagram illustrating an example of a DCI size according to the first embodiment. Figure 6 is a diagram illustrating an example of a DCI size according to the second embodiment. Figure 7 is a diagram illustrating another example of a DCI size according to the second embodiment. Figure 8 is a diagram illustrating an example of an association between a code point of a TCI field and a TCI status according to the second embodiment. Figure 9 is a diagram illustrating another example of an association between a code point of a TCI field and a TCI status according to the second embodiment. Figure 10 is a diagram illustrating another example of an association between a code point of a TCI field and a TCI status according to the second embodiment. Figure 11 is a diagram illustrating an example of a method for setting / activating / updating an index related to a TRP according to the third embodiment. 12A and 12B are diagrams illustrating an example of a MAC CE according to the third embodiment. FIG. 13 is a diagram illustrating an example of a MAC CE according to embodiment 4-1. FIG. 14 is a diagram illustrating another example of a MAC CE according to embodiment 4-1. FIG. 15 is a diagram illustrating another example of a MAC CE according to embodiment 4-1. FIG. 16 is a diagram illustrating an example of a MAC CE according to embodiment 4-2. FIG. 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 18 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 19 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 20 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 21 is a diagram illustrating an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

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

[0020] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

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

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

[0023] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

[0024] An SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] The DCI in the above-mentioned mode 2 / mode 3 may be called a beam instruction DCI.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] (PUSCH Repetition) In Rel. 17, the introduction of PUSCH repetition is under consideration.

[0083] The RRC field and DCI field related to PUSCH repetition will be described below with reference to Figures 3A and 3B.

[0084] RRC fields related to PUSCH transmission defined up to Rel. 16 include a field related to the SRS resource set of the codebook (CB) / non-codebook (NCB), a field related to mapping (power control) between the SRI and the PUSCH (sri-PUSCH-MappingToAddModList), and a field related to P0 of the PUSCH for each SRI (p0-PUSCH-SetList).

[0085] DCI fields related to PUSCH transmission defined up to Rel. 16 include an SRS resource indicator field, a field indicating precoding information and the number of layers, a field related to the association between PTRS and DMRS, and a TPC command field.

[0086] In Rel. 17, if two SRS resource sets of CB / NCB are configured, an SRS resource set indicator field is added to DCI format 0_1 / 0_2.

[0087] The SRS Resource Set Indicator field has two bits. If the SRS Resource Set Indicator field indicates code point "00 (0)", it indicates single-TRP operation using the first TRP (TRP1). If the SRS Resource Set Indicator field indicates code point "01 (1)", it indicates single-TRP operation using the second TRP (TRP2). If the SRS Resource Set Indicator field indicates code point "10 (2)", it indicates multi-TRP operation with the first TRP (TRP1) followed by the second TRP (TRP2) in a PUSCH repetition. If the SRS Resource Set Indicator field indicates code point "11 (3)", it indicates multi-TRP operation with the second TRP (TRP2) followed by the first TRP (TRP1) in a PUSCH repetition (see Figure 3B).

[0088] When the SRS resource set indicator field is added to DCI format 0_1 / 0_2, new RRC fields are added: a field related to the mapping (power control) of the second SRI and the PUSCH (sri-PUSCH-MappingToAddModList2) and a field related to P0 of the PUSCH for each second SRI (p0-PUSCH-SetList2) (see FIG. 3A). These fields are used as fields for the second TRP (TRP2), and the existing fields are used as fields for the first TRP (TRP1).

[0089] Furthermore, when an SRS resource set indicator field is added to DCI format 0_1 / 0_2, a second SRS resource indicator field, a field indicating second precoding information and the number of layers, a field relating to the association of second PTRS and DMRS, and a second TPC command field are added to the DCI format (see FIG. 3A). These fields are used as fields for the second TRP (TRP2), and the existing fields are used as fields for the first TRP (TRP1).

[0090] (UL TCI Status) In Rel. 16 NR, the use of the UL TCI status as a UL beam indication method is being considered. Notification of the UL TCI status is similar to notification of the UE's DL beam (DL TCI status). Note that the DL TCI status may be interchangeably read as the TCI status for PDCCH / PDSCH.

[0091] The channel / signal (which may be referred to as a target channel / RS) to which the UL TCI state is set (specified) may be, for example, at least one of a PUSCH (DMRS of PUSCH), a PUCCH (DMRS of PUCCH), a random access channel (Physical Random Access Channel (PRACH)), an SRS, etc.

[0092] Furthermore, the RS (source RS) that has a QCL relationship with the channel / signal may be, for example, a DL RS (e.g., SSB, CSI-RS, TRS, etc.) or a UL RS (e.g., SRS, SRS for beam management, etc.).

[0093] In the UL TCI state, an RS that has a QCL relationship with the channel / signal may be associated with a panel ID for receiving or transmitting the RS, which may be explicitly configured (or specified) or implicitly determined by higher layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0094] The correspondence between the RS and the panel ID may be set by being included in the UL TCI status information, or may be set by being included in at least one of the resource setting information, spatial relationship information, etc. of the RS.

[0095] The QCL type indicated by the UL TCI status may be an existing QCL type A-D, or may be another QCL type, and may include a predetermined spatial relationship, associated antenna ports (port index), etc.

[0096] When a UE is assigned an associated panel ID for an UL transmission (e.g., assigned by a DCI), the UE may perform the UL transmission using the panel corresponding to the panel ID. The panel ID may be associated with a UL TCI state, and when a UL TCI state is assigned (or activated) for a given UL channel / signal, the UE may identify the panel to use for the UL channel / signal transmission according to the panel ID associated with the UL TCI state.

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

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

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

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

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

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

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

[0104] Unified TCI State Activation / Deactivation MAC CE: In Rel. 17, a MAC CE is defined for activating / deactivating unified TCI states.

[0105] 4 is a diagram illustrating an example of a unified TCI state activation / deactivation MAC CE. The MAC CE illustrated in FIG. 4 includes a field indicating a serving cell ID, a field indicating a DL BWP ID, a field indicating a UL BWP ID, a TCI state ID field ("TCI state ID j" (j is an integer between 1 and N)), a field indicating the number of the TCI state corresponding to the corresponding TCI state field ("Pi" (i is an integer between 1 and N)), a field indicating that the TCI state of the corresponding TCI state field is DL / joint or UL ("D / U"), and a reserved bit field ("R").

[0106] The UE is activated to a unified TCI state (joint TCI state or separate (DL / UL) TCI state) using the activation by this MAC CE.

[0107] (Analysis) Incidentally, in future wireless communication systems (for example, Rel. 18 and later), it is being considered to introduce a unified TCI state framework in multi-TRP operation.

[0108] In multi-TRP operation, indication of one or more TCI states by a single DCI (single-DCI) and indication of one or more TCI states by multiple DCIs (multi-DCI) are considered.

[0109] In a single DCI, it is considered that one or more TCI states are indicated in one TCI field.

[0110] It is considered that in multi-DCI, one or more TCI states are indicated in at least one of the following ways: ・Reuse the scheme of single-DCI-based multi-TRP (defined up to Rel. 16), i.e., indicate one or more TCI states with one TCI field. ・An existing TCI field in a DCI format (e.g., DCI format 1_1 / 1_2, DCI format with / without DL assignment) related to one value of CORESET pool index is used to indicate joint / DL / UL TCI states corresponding to the same CORESET pool index. ・An existing TCI field in a DCI format (e.g., DCI format 1_1 / 1_2, DCI format with / without DL assignment) is used to indicate all joint / DL / UL TCI states corresponding to two (both) CORESET pool indices. - Existing TCI fields in DCI formats (e.g., DCI formats 1_1 / 1_2, DCI formats with / without DL assignment) associated with one value of CORESET pool index are utilized to indicate joint / DL / UL TCI states corresponding to the same or different CORESET pool indexes.

[0111] In addition, in the PUSCH / PUCCH repetition of multi-TRP specified in Rel. 17, support for (dynamic) switching between single-TRP and multi-TRP is being considered.

[0112] For this PUSCH, a new DCI field of the SRS resource set indicator may be used for this switching.

[0113] For the PUCCH, the switching may be performed by activating one or more (eg, two) spatial relationships for each PUCCH resource.

[0114] However, in the unified TCI state framework introduced in Rel. 18 and later, when the beam application time is taken into consideration, the number of instruction TCI states cannot be controlled using DCIs that schedule each channel / signal (scheduling DCIs).

[0115] Furthermore, different UE operations need to be defined for the unified TCI states defined in Rel. 17 and those defined in Rel. 18 and later.

[0116] For example, in the unified TCI state specified in Rel. 18 and later, the introduction of a DCI field (either a new DCI field or an existing DCI field) is being considered to (dynamically) switch between single-TRP and multi-TRP. On the other hand, the unified TCI state specified in Rel. 17 does not support multi-TRP operation, and therefore does not require a special field for switching.

[0117] In addition to the above-mentioned switching, it is also being considered that the unified TCI state defined in Rel. 17 and the unified TCI state defined in Rel. 18 and later differ in beam application time (BAT), default QCL / TCI state, association of the designated TCI state with each channel / RS, and the like.

[0118] However, there has been insufficient consideration on how to indicate / switch between the unified TCI state defined in Rel. 17 and the unified TCI state defined in Rel. 18 and later. If this consideration is insufficient, the TCI state to be applied to each channel / signal may not be determined appropriately, which may result in a decrease in communication throughput.

[0119] Therefore, the present inventors have conceived a method for appropriately performing operations related to the unified TCI state.

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

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

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

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

[0124] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

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

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

[0127] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0128] In the present disclosure, the terms panel, receiving panel, UE panel, UE capability value, UE capability value set, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, 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 relation group, Code Division Multiplexing (CDM)), The terms "CDM (Corrective Multiplexing) group," "reference signal group," "CORESET group," "Physical Uplink Control Channel (PUCCH) group," "PUCCH resource group," "resource (e.g., reference signal resource, SRS resource)," "resource set (e.g., reference signal resource set)," "CORESET pool," "downlink Transmission Configuration Indication state (TCI state)" (DL TCI state), "uplink TCI state" (UL TCI state), "unified TCI state," "common TCI state," "indicated TCI state," "Quasi-Co-Location (QCL)," "QCL assumption," and the like may be read interchangeably.

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

[0130] Furthermore, the panel identifier (ID) and the panel may be interchangeable. That is, the TRP ID and the TRP, the CORESET group ID and the CORESET group, etc. may be interchangeable.

[0131] In the present disclosure, the terms TRP, transmission point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in the TCI field may be read interchangeably.

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

[0133] Transmission / reception of a channel / signal using a single TRP may also be interpreted as the TCI states (joint / separate / indicated TCI states) being different in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repeat), or the number of different TCI states (joint / separate / indicated TCI states) being multiple (e.g., two) in the transmission / reception of the channel / signal (e.g., NCJT / CJT / repeat).

[0134] In this disclosure, the terms single TRP, single TRP system, single TRP transmission, and single PDSCH may be interchangeable. In this disclosure, the terms multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interchangeable.

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

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

[0137] In the present disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI states / spatial relationships, multi-TRP enabled by RRC / DCI, multiple TCI states / spatial relationships enabled by RRC / DCI, and at least one of multi-TRP based on a single DCI and multi-TRP based on multiple DCI may be read interchangeably.

[0138] In the present disclosure, the terms "multi-TRP based on multi-DCI," "one CORESET pool index (CORESETPoolIndex) value being set for a CORESET," and "multiple specific indexes (e.g., TRP indexes, CORESET pool indexes, or indexes corresponding to TRPs) being set for a specific channel / CORESET" may be read interchangeably.

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

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

[0141] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index = 1 (or a value greater than or equal to 1) may be read interchangeably.

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

[0143] In the present disclosure, repetition, repeated transmission, and repeated reception may be read interchangeably.

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

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

[0146] In the present disclosure, a first TRP may correspond to a first TCI state. In the present disclosure, a second TRP may correspond to a second TCI state. In the present disclosure, an n-th TRP may correspond to an n-th TCI state.

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

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

[0149] In the present 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. Also, receiving DL signals using an SFN may mean receiving the same data / control information using the same time / frequency resources and / or using multiple TCI states / spatial domain filters / beams / QCLs.

[0150] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "unified TCI state in which multi-TRP is not configured / used / applied," "unified TCI state defined in Rel. 17," "Rel. 17 unified TCI state," and "first unified TCI state" may be interchangeable.

[0151] In the present disclosure, the terms "indication TCI state," "unified TCI state," "unified TCI state in which multi-TRP is configured / used / applied," "unified TCI state in which multi-TRP can be configured / used / applied," "indication TCI state in which multi-TRP is configured / used / applied," "indication TCI state in which multi-TRP can be configured / used / applied," "unified TCI state specified in Rel. 18," "Rel. 18 unified TCI state," "unified TCI state for multi-TRP," and "second unified TCI state" may be interpreted interchangeably.

[0152] (Wireless Communication Method) The UE may apply (Rel. 17 / 18) indicated TCI states to specific channels / signals.

[0153] The specific channel / signal may be a UE-specific (dedicated) DL channel / signal, which may be a UE-specific PDCCH / PDSCH / CSI-RS (e.g., aperiodic (A-) CSI-RS).

[0154] The specific channel / signal may be a specific UL channel / signal, which may be at least one of a DCI-indicated (dynamic grant-indicated) PUSCH, a configured grant PUSCH, multiple (all) specific PUCCHs (resources), and an SRS (e.g., an aperiodic (A-) SRS).

[0155] In each embodiment of the present disclosure, an example in which the number of TCI states indicated to the UE is one or two is mainly described, but the number of TCI states indicated is not limited to this. For example, the number of TCI states indicated to the UE may be three or more (for example, four).

[0156] Each of the following embodiments of the present disclosure may be applied to a PDSCH with a single TRP.

[0157] The PDSCH of a single TRP may be scheduled with a specific DCI (DCI format). The specific DCI format may be, for example, DCI format 1_0 (or a DCI format that does not include a TCI field). The specific DCI format may be DCI format 1_1 / 1_2. The specific DCI format may indicate one TCI state.

[0158] The QCL assumption for the PDSCH of a single TRP may be the default TCI state, which may be one TCI state (in any DCI format).

[0159] The UE may not be configured for multi-TRP repeated transmission, and the single-TRP PDSCH may be scheduled as a PDSCH with single layer MIMO.

[0160] The single-TRP PDSCH may be the PDSCH when the UE is not configured with multi-TRP (e.g., CORESET pool index).

[0161] The PDSCH of a single TRP may be a PDSCH scheduled with a CORESET of at least the CSS. The PDSCH of a single TRP may be a PDSCH scheduled with a CORESET of only the CSS (or a CSS excluding the Type 3 CSS).

[0162] Each of the following embodiments of the present disclosure may be applied to a multi-TRP PDSCH.

[0163] The PDSCH of a single TRP may be scheduled with a specific DCI (DCI format), which may be DCI format 1_1 / 1-2, and which may indicate two TCI states.

[0164] The QCL assumption for the multi-TRP PDSCH may be the default TCI state, which may be two TCI states (in any DCI format).

[0165] The UE may not be configured for multi-TRP repeated transmission, and the multi-TRP PDSCH may be scheduled as a PDSCH with multi-layer MIMO.

[0166] The multi-TRP PDSCH may be a PDSCH when the UE is configured for multi-TRP repetition transmission, and may then be scheduled as a PDSCH with repetition (using TDM / FDM / SDM).

[0167] The multi-TRP PDSCH may be a PDSCH when the UE is configured with SFN scheme A / B. The multi-TRP PDSCH may be a PDSCH with multiple TCI states.

[0168] Each of the following embodiments of the present disclosure may be applied to a single TRP PDCCH.

[0169] The PDCCH of a single TRP may be a PDCCH associated with a CORESET in which the SFN scheme A / B is not configured.

[0170] The PDCCH of a single TRP may be a PDCCH associated with a CORESET in which repetitive transmission (of two linked SSs) is not configured.

[0171] Each of the following embodiments of the present disclosure may be applied to a multi-TRP PDCCH.

[0172] The multi-TRP PDCCH may be a PDCCH associated with a CORESET in which SFN scheme A / B is configured.

[0173] Each of the following embodiments of the present disclosure may be applied to a single TRP PUSCH / PUCCH.

[0174] The PUSCH / PUCCH of a single TRP may be a PUSCH / PUCCH in which repeated transmission of a multi-TRP is not configured.

[0175] Each of the following embodiments of the present disclosure may be applied to multi-TRP PUSCH / PUCCH.

[0176] The PUSCH / PUCCH of the multi-TRP may be a PUSCH / PUCCH for which repeated transmission of the multi-TRP is set.

[0177] Each of the following embodiments of the present disclosure may be applied to single / multi-TRP CSI-RS / SRS.

[0178] First Embodiment In the first embodiment, switching between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state will be described.

[0179] The UE may be able to switch between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state using RRC signaling. The UE may also determine to switch between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state using RRC signaling.

[0180] For example, the UE may assume / determine that the Rel. 18 TCI state is configured / applies if certain RRC parameters are configured.

[0181] For example, the UE may assume / determine that the Rel. 17 TCI state is configured / applies if the particular RRC parameter is not configured.

[0182] Also, for example, if the specific RRC parameter is not configured, the UE may assume / determine that the TCI state specified in Rel. 15 is configured / applied. The TCI state specified in Rel. 15 may mean a TCI state other than the unified TCI state in which multi-TRP is not configured.

[0183] The specific RRC parameters may be new RRC parameters defined in Rel.

[0184] The particular RRC parameter may be one or more existing (defined in Rel. 17) RRC parameters (or a combination of RRC parameters).

[0185] For example, the UE may assume / determine that the Rel. 18 TCI state is configured / applied if at least one of the following parameters is configured: - Unified TCI state configuration parameter (e.g., DL or Joint TCI state parameter (DLorJointTCIState) / UL TCI state parameter (UL-TCIState)) - Multi-TRP configuration parameter.

[0186] In the present disclosure, the multi-TRP configuration parameter may be, for example, a CORESET pool index (CORESETPoolIndex) (with multiple different values). Also, the multi-TRP configuration parameter being configured may be interpreted as the presence of an SRS resource set indicator field, the presence of a second TPMI / SRI / TPC command field, the association of multiple TCI states with one DCI code point, or the indication / configuration of multiple unified TCI states using RRC / MAC CE / DCI.

[0187] The size of the DCI format when the unified TCI state for multi-TRP is set may be different from the size of the DCI format when the unified TCI state for multi-TRP is not set.

[0188] For example, the size of the DCI format when the unified TCI state for multi-TRP is set may be smaller than the size of the DCI format when the unified TCI state for multi-TRP is not set, thereby reducing the overhead of the DCI.

[0189] 5 is a diagram illustrating an example of a DCI size according to the first embodiment. In the example illustrated in FIG. 5, when a unified TCI state for multi-TRP is set, the DCI format includes DCI fields #1 to #4, and when a unified TCI state for multi-TRP is not set, the DCI format includes DCI fields #1 to #3 but does not include DCI field #4 (DCI field #4 is not used).

[0190] In addition, the field not included in the DCI format when the unified TCI state for multi-TRP is set (for example, DCI field #4 in Figure 5) may be one or more fields.

[0191] A field not included in a DCI format when the unified TCI state for multi-TRP is set (e.g., DCI field #4 in Fig. 5) may be, for example, a field used (only) for the unified TCI state for multi-TRP, such as a field included in a specific DCI format (e.g., DCI format 0_1 / 0_2 / 1_1 / 1_2) used for switching between single-TRP and multi-TRP.

[0192] A field that is not included in a DCI format when a unified TCI state for multi-TRP is set (e.g., DCI field #4 in Figure 5) may be, for example, at least one of the SRS resource set indicator field and the second TPMI / SRI / TPC command field that are included in a specific DCI format (e.g., DCI format 0_1 / 0_2).

[0193] According to the first embodiment described above, a unified TCI state that appropriately uses multi-TRP can be set using RRC signaling.

[0194] Second Embodiment In a second embodiment, switching between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state will be described.

[0195] <<Switching Method>> The UE may be configured with (parameters related to) the unified TCI state for multi-TRP using RRC signaling.

[0196] The UE may then use the MAC CE to switch between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state. The UE may use the MAC CE to determine whether to switch between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state.

[0197] In the case of single / multiple DCI, if multiple (e.g., two) TCI states are activated by the MAC CE for at least one TCI field codepoint, the UE may assume / determine that a Rel. 18 TCI state is configured / applied / activated / indicated.

[0198] In case of multiple DCIs (e.g., when multiple different values ​​of CORESET pool index are configured), if multiple (e.g., two) TCI states are activated by the MAC CE for each CORESET pool index, the UE may assume / determine that a Rel. 18 TCI state is configured / applied / activated / indicated.

[0199] Also, if the CORESET pool index (CORESET pool index with multiple different values) is activated based on at least one method described in the third embodiment below, the UE may assume / determine that the Rel. 18 TCI state is configured / applied / activated / indicated.

[0200] In this embodiment, the setting of the unified TCI state for multi-TRP using RRC signaling may mean the setting of the unified TCI state for multi-TRP described in the first embodiment above.

[0201] In cases other than the above where the UE assumes / determines that the Rel. 18 TCI state is configured / applied / activated / indicated, the UE may assume / determine that the Rel. 17 TCI state is configured / applied / activated / indicated.

[0202] The size of the DCI format when the unified TCI state for multi-TRP is configured / activated / indicated may be the same as the size of the DCI format when the unified TCI state for multi-TRP is not configured / activated / indicated, in which case there is no need to change the DCI size when a MAC CE is activated, thereby reducing the number / load of blind detection of DCI / PDCCH by the UE.

[0203] DCI fields included in the DCI format when the unified TCI state for multi-TRP is configured and multiple TCI states are activated, but unused in the DCI format when the unified TCI state for multi-TRP is configured and multiple TCI states are not activated, may be treated as reserved bits, in other words, the UE may ignore such DCI fields.

[0204] The DCI field may also be used for other purposes, for example, to indicate the resource / TCI status of a scheduled channel (e.g., PDSCH / PUSCH).

[0205] 6 is a diagram showing an example of a DCI size according to the second embodiment. In the example shown in FIG. 6, a DCI format (first DCI format) in the case where a unified TCI state for multi-TRP is configured and multiple TCI states are activated includes DCI fields #1 to #4. A DCI format (second DCI format) in the case where a unified TCI state for multi-TRP is configured and multiple TCI states are not activated includes DCI fields #1 to #4, but the value of DCI field #4 is treated as a reserved bit.

[0206] In addition, the DCI field treated as the above-mentioned reserved bit may be common to at least one of the fields not included in the DCI format when a unified TCI state for multi-TRP is set in the first embodiment described above.

[0207] In the present disclosure, one TCI state may refer to at least one of one joint TCI state, one DL TCI state, and one UL TCI state, and in the present disclosure, multiple TCI states may refer to at least one of multiple joint TCI states, multiple DL TCI states, and multiple UL TCI states.

[0208] Also, the size of the DCI format when the unified TCI state for multi-TRP is configured / activated / indicated may be different from the size of the DCI format when the unified TCI state for multi-TRP is not configured / activated / indicated. In other words, the size of the DCI may be changed in the MAC CE that switches between the Rel. 17 unified TCI state and the Rel. 18 unified TCI state.

[0209] For example, the size of the DCI format when the unified TCI state for multi-TRP is set may be smaller than the size of the DCI format when the unified TCI state for multi-TRP is not set, thereby reducing the overhead of the DCI.

[0210] 7 is a diagram showing another example of DCI size according to the second embodiment. In the example shown in FIG. 7, when a unified TCI state for multi-TRP is set and multiple TCI states are activated, the DCI format includes DCI fields #1 to #4. When a unified TCI state for multi-TRP is set and multiple TCI states are not activated, the DCI format includes DCI fields #1 to #3 but does not include DCI field #4 (DCI field #4 is not used).

[0211] In addition, a field that is not included in the DCI format when a unified TCI state for multi-TRP is set and multiple TCI states are activated (e.g., DCI field #4 in Figure 7) may be common to at least one of the fields that are not included in the DCI format when a unified TCI state for multi-TRP is set in the first embodiment described above.

[0212] <<Activated / Indicated TCI States>> In the following, the combinations of TCI states activated in MAC CE and indicated in DCI are described.

[0213] In DL reception / UL transmission, at least one of the following TCI state combinations may be indicated for one CC / BWP or (a set of) multiple CCs / BWPs: [In the case of joint DL / UL TCI states] - First joint TCI state, second joint TCI state. [In the case of separate DL / UL TCI states] - First DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state. - First DL TCI state, first UL TCI state, second DL TCI state. - First DL TCI state, first UL TCI state, second UL TCI state. - First DL TCI state, second DL TCI state, second UL TCI state. First UL TCI state, second DL TCI state, second UL TCI state. First DL TCI state, second DL TCI state. First UL TCI state, second UL TCI state.

[0214] Note that, similar to Rel. 17, the unified TCI state framework may support the indication of one joint TCI state, and similar to Rel. 17, the unified TCI state framework may support the indication of one pair of DL and UL TCI states.

[0215] Although the above combinations are described separately for the joint TCI state and the separate TCI state, the above combinations are merely examples. For example, a code point in one TCI field may be associated with a joint TCI state and a separate (DL / UL) TCI state.

[0216] In other words, the UE may be supported to be simultaneously configured with the joint TCI state and the separate TCI state, and the UE may report UE capability information supporting this function to the network (e.g., base station).

[0217] The UE may determine / update / change the TCI state based on the indicated combination.

[0218] The UE may determine to apply the indicated TCI state, and may maintain the TCI state that was applied before the indication was issued for the TCI states that are not included in the indicated combination.

[0219] For example, a combination of a first DL TCI state, a first UL TCI state, and a second DL TCI state is instructed to the UE. In this case, the UE may determine to update the instructed TCI state, and to use the TCI state that was applied until the instruction was issued for the non-instructed TCI state (in this case, the second UL TCI state).

[0220] The UE may determine to apply the indicated TCI state, and at this time, the UE may determine to discard the TCI state that was applied before the indication was issued for the TCI state that is not included in the indicated combination.

[0221] For example, a combination of a first DL TCI state, a first UL TCI state, and a second DL TCI state is instructed to the UE. In this case, the UE may determine to update the instructed TCI state, and to discard the TCI state that was applied until the instruction was issued for the non-instructed TCI state (in this case, the second UL TCI state).

[0222] The UE may decide to maintain / discard a particular TCI state for a TCI state that is not indicated.

[0223] For example, the UE may decide to maintain (or discard) the first TCI state for the non-indicated TCI state.

[0224] For example, the UE may decide to discard (or maintain) the second TCI state for the non-indicated TCI state.

[0225] The UE may decide to maintain / discard the TCI state corresponding to a particular TRP for non-indicated TCI states.

[0226] For example, the UE may decide to maintain (or discard) the TCI state corresponding to the first TRP for the unindicated TCI state.

[0227] For example, the UE may decide to discard (or maintain) the TCI state corresponding to the second TRP for the unindicated TCI state.

[0228] Note that this embodiment may be applied (only) to the case of single DCI-based multi-TRP, or may also be applied to the case of multi-DCI-based multi-TRP.

[0229] <<Association of Code Points in TCI Field with TCI States>> [Single DCI-based Multi-TRP] Fig. 8 is a diagram showing an example of association of code points in the TCI field with TCI states according to the second embodiment. Fig. 8 shows a case where one TCI state is associated with a code point in one TCI field, and a case where multiple TCI states are associated with a code point in one TCI field, for each of the cases of a joint TCI state and a separate TCI state.

[0230] In the example shown in Figure 8, when one TCI state is associated with one TCI field code point, a MAC CE that activates a Rel. 17 TCI state may be used, and when multiple TCI states are associated with one TCI field code point, a MAC CE that activates a Rel. 18 TCI state may be used.

[0231] For example, the UE may use the MAC CE to switch between a case where one joint TCI state is associated with a code point in one TCI field and a case where multiple joint TCI states are associated with a code point in one TCI field.

[0232] For example, the UE may use the MAC CE to switch between a case where one separate (DL / UL) TCI state is associated with a code point in one TCI field and a case where multiple separate (DL / UL) TCI states are associated with a code point in one TCI field.

[0233] For example, the UE may use the MAC CE to switch between a case where one joint TCI state is associated with a code point in one TCI field and a case where multiple separate (DL / UL) TCI states are associated with a code point in one TCI field.

[0234] For example, the UE may use the MAC CE to switch between a case where one separate (DL / UL) TCI state is associated with a code point in one TCI field and a case where multiple joint TCI states are associated with a code point in one TCI field.

[0235] The switching shown in FIG. 8 may be performed using RRC / MAC CE.

[0236] For at least one (or all) TCI states activated by a MAC CE (for Rel. 18), one TCI state may be associated with a codepoint in one TCI field, and for at least one (or all) TCI states activated by a MAC CE (for Rel. 18), multiple (e.g., two) TCI states associated with a codepoint in one TCI field may have the same TCI state ID.

[0237] In this case, the UE may perform the operation in the case where one TCI state is indicated in this embodiment, or alternatively, in this case, the UE may perform the operation in the case where multiple TCI states are indicated in this embodiment.

[0238] Fig. 9 is a diagram showing another example of association between code points in the TCI field and TCI states according to the second embodiment, showing a case where a joint TCI state is indicated.

[0239] As shown in Figure 9, when a TCI state in which one joint TCI state is associated with all TCI codepoints is activated using the MAC CE defined up to Rel. 17, the UE performs the operation defined in Rel. 17.

[0240] Also, as shown in Figure 9, when a TCI state in which multiple (two) joint TCI states are associated with a TCI codepoint is activated using the MAC CE defined in Rel. 18, the UE performs the operations defined in Rel. 18 (operations related to a unified TCI state in multi-TRP).

[0241] Also, as shown in Figure 9, when a TCI state in which one joint TCI state is associated with all TCI codepoints is activated using the MAC CE defined in Rel. 18, the UE performs the operations defined up to Rel. 17 or the operations defined in Rel. 18 (operations related to the unified TCI state in multi-TRP).

[0242] Although the example shown in FIG. 9 is a description relating to a joint TCI state, it is also applicable to a separate (DL / UL) TCI state.

[0243] [Multiple DCI-based Multi-TRP] Figure 10 is a diagram showing another example of association between code points in the TCI field and TCI states according to the second embodiment. Figure 10 shows a case where one TCI state is associated with a code point in one TCI field corresponding to Rel. 17 operation, and a case where one TCI state is associated with a code point in one TCI field corresponding to Rel. 18 operation, for both the joint TCI state and the separate TCI state.

[0244] Rel. 17 operation may refer to the case where a single TRP is used, and Rel. 18 operation may refer to the case where multiple TRPs (based on multiple DCIs) are used.

[0245] In the example shown in Figure 10, the association between the codepoints of the TCI fields and the TCI states corresponding to Rel. 18 operations may be set / activated / defined per index (CORESET pool index) for the TRP.

[0246] In the example shown in Figure 10, if one TCI state is associated with a codepoint in one TCI field corresponding to Rel. 17 operation, a MAC CE that activates the Rel. 17 TCI state may be used, and if one TCI state is associated with a codepoint in one TCI field corresponding to Rel. 18 operation, a MAC CE that activates the Rel. 18 TCI state may be used.

[0247] For example, the UE may use the MAC CE to switch between a case where one TCI state is associated with a codepoint in one TCI field corresponding to Rel. 17 operation and a case where one TCI state is associated with a codepoint in one TCI field corresponding to Rel. 18 operation.

[0248] For example, the UE may use the MAC CE to switch between a case where one joint TCI state is associated with a codepoint in one TCI field corresponding to Rel. 17 operation and a case where one joint TCI state is associated with a codepoint in one TCI field corresponding to Rel. 18 operation.

[0249] For example, a UE may use a MAC CE to switch between a case where one separate (DL / UL) TCI state is associated with a codepoint in one TCI field corresponding to Rel. 17 operation and a case where one separate (DL / UL) TCI state is associated with a codepoint in one TCI field corresponding to Rel. 18 operation.

[0250] For example, a UE may use a MAC CE to switch between a case where one joint TCI state is associated with a codepoint in one TCI field corresponding to Rel. 17 operation and a case where one separate (DL / UL) TCI state is associated with a codepoint in one TCI field corresponding to Rel. 18 operation.

[0251] For example, a UE may use a MAC CE to switch between a case where one separate (DL / UL) TCI state is associated with a codepoint in one TCI field corresponding to Rel. 17 operation and a case where one joint TCI state is associated with a codepoint in one TCI field corresponding to Rel. 18 operation.

[0252] The switching shown in FIG. 10 may be performed using RRC / MAC CE.

[0253] According to the second embodiment, a unified TCI state that utilizes multi-TRP can be appropriately activated using MAC CE.

[0254] Third Embodiment In the third embodiment, switching between single TRP and multi-TRP for multi-DCI-based multi-TRP will be described.

[0255] The UE may be configured with an index for the TRP (e.g., a CORESET pool index) using RRC signaling, which may have multiple (e.g., two) different values.

[0256] The index may be activated / updated to the UE using a MAC CE.

[0257] If the index is not activated / updated, the UE may assume / determine that the index is not configured. In other words, if the index is not activated / updated, the UE may assume / determine that a single TRP is configured (or may fall back to single TRP operation).

[0258] 11 is a diagram showing an example of a method for setting / activating / updating indexes related to TRPs according to the third embodiment. In the example shown in FIG. 11, first, for the UE, CORESETs #0 to #2, each having a CORESET pool index value of 0, and CORESETs #3 and #4, each having a CORESET pool index value of 1, are set.

[0259] Then, the UE is activated by the MAC CE with CORESET pool indices corresponding to each of CORESETs #0 to #4, and further updated (activated) by the MAC CE with CORESET pool indices corresponding to CORESETs #0, #2, and #3.

[0260] In the following, the MAC CE that activates / updates the index for the TRP is described.

[0261] The MAC CE may be a new MAC CE defined in Rel. 18 or later.

[0262] Fig. 12A is a diagram showing an example of a MAC CE according to the third embodiment. The MAC CE shown in Fig. 12A includes a field indicating a serving cell ID, a field indicating a CORESET ID, and seven specific fields (which may be "R" fields or reserved bit fields in Fig. 12A). Note that the number of specific fields (seven in Fig. 12A) is merely an example and is not limited to this number.

[0263] The UE may determine whether to activate / update the index for the TRP based on the values ​​indicated by a specific number of specific fields (five in FIG. 12A ) among the specific fields. For example, if the specific field indicates a first value (e.g., 0), the UE may determine that the index for the TRP corresponding to the field is not to be activated / updated.

[0264] For example, if a particular field indicates a first value (eg, 0), the UE may determine that the index for the TRP corresponding to the field is deactivated.

[0265] The UE may determine whether to activate / update the index for the TRP based on the value indicated by the specific field. For example, if the specific field indicates a second value (e.g., 1), the UE may determine that the index for the TRP corresponding to the field is activated / updated.

[0266] If it is determined that the index for the TRP corresponding to the field is updated, the UE may determine to change the value of the index for the corresponding TRP.

[0267] One MAC CE may be used to activate / update indexes (e.g., CORESET pool indexes) for multiple TRPs for multiple CORESETs, where multiple specific fields may be represented as bitmaps corresponding to each CORESET.

[0268] Furthermore, the MAC CE that activates / updates the index related to the TRP may be a specific MAC CE, such as a new MAC CE (defined in Rel. 18 or later), an existing MAC CE (defined up to Rel. 17), or an extended MAC CE of an existing MAC CE (defined up to Rel. 17).

[0269] For example, an existing MAC CE (defined up to Rel. 17) or an MAC CE that is an extension of an existing MAC CE (defined up to Rel. 17) may be a MAC CE for activating / deactivating a (unified) TCI state, including a field related to an index related to a TRP.

[0270] Fig. 12B is a diagram showing another example of a MAC CE according to the third embodiment. The MAC CE shown in Fig. 12B is a MAC CE used to activate / deactivate the unified TCI state described above.

[0271] In the example shown in FIG. 12B, a specific number (five in FIG. 12B) of reserved bit fields (which may hereinafter be referred to as specific fields) are used to activate / update indexes related to TRPs.

[0272] The UE may determine whether to activate / update the index for the TRP based on the value indicated by the specific field. For example, if the specific field indicates a first value (e.g., 0), the UE may determine that the index for the TRP corresponding to the field is not to be activated / updated.

[0273] For example, if a particular field indicates a first value (eg, 0), the UE may determine that the index for the TRP corresponding to the field is deactivated.

[0274] The UE may determine whether to activate / update the index for the TRP based on the value indicated by the specific field. For example, if the specific field indicates a second value (e.g., 1), the UE may determine that the index for the TRP corresponding to the field is activated / updated.

[0275] If it is determined that the index for the TRP corresponding to the field is updated, the UE may determine to change the value of the index for the corresponding TRP.

[0276] One MAC CE may be used to activate / update indexes (e.g., CORESET pool indexes) for multiple TRPs for multiple CORESETs, where multiple specific fields may be represented as bitmaps corresponding to each CORESET.

[0277] According to the third embodiment described above, even when a unified TCI state using multi-TRP is applied, multi-DCI-based multi-TRP operation can be performed appropriately.

[0278] Fourth Embodiment In the fourth embodiment, a MAC CE that activates / deactivates a unified TCI state using multi-TRP will be described.

[0279] The UE may activate / deactivate the unified TCI state using a MAC CE described in at least one of the following embodiments 4-1 to 4-3.

[0280] <<Embodiment 4-1>> The MAC CE of embodiment 4-1 may be used in at least one of a single DCI-based multi-TRP and a multi-DCI-based multi-TRP.

[0281] The UE may activate / deactivate the unified TCI state using multiple TRPs using a MAC CE that is an extension of the unified TCI state activation / deactivation MAC CE defined in Rel. 17 and earlier (see FIG. 13).

[0282] The MAC CE may include a field (“Pi” (i is an integer equal to or greater than 1)) indicating whether the code point of the ith TCI field includes the second TCI state.

[0283] For example, if the Pi field indicates a first value (e.g., 0), it may indicate that the corresponding TCI codepoint does not include a second TCI state (or that the corresponding TCI codepoint indicates only one DL / joint or UL TCI state).

[0284] For example, if the Pi field indicates a second value (eg, 1), it may indicate that the corresponding TCI codepoint includes a second TCI state.

[0285] The MAC CE may include a field (“Qi” (i is an integer equal to or greater than 1)) indicating whether the code point of the ith TCI field includes the third TCI state.

[0286] For example, if the Qi field indicates a first value (e.g., 0), it may indicate that the corresponding TCI codepoint does not include a third TCI state (or that the corresponding TCI codepoint indicates two (first and second) DL / joint or UL TCI states).

[0287] For example, if the Qi field indicates a second value (eg, 1), it may indicate that the corresponding TCI codepoint includes a third TCI state.

[0288] The MAC CE may include a field (“Si” (i is an integer equal to or greater than 1)) indicating whether the code point of the i-th TCI field includes the fourth TCI state.

[0289] For example, if the Si field indicates a first value (e.g., 0), it may indicate that the corresponding TCI codepoint does not include a fourth TCI state (or that the corresponding TCI codepoint indicates three (1st-3rd) DL / joint or UL TCI states).

[0290] For example, if the Si field indicates a second value (eg, 1), it may indicate that the corresponding TCI codepoint includes a fourth TCI state.

[0291] When none of the Pi fields indicates the second value (e.g., 1), the Qi field and the Si field may be absent in the MAC CE. When none of the Qi fields indicates the second value (e.g., 1), the Si field may be absent in the MAC CE.

[0292] If the first TCI state, the second TCI state, the third TCI state, and the fourth TCI state correspond to DL (or joint), UL, DL (or joint), and UL, respectively, the first TCI state, the second TCI state, the third TCI state, and the fourth TCI state may correspond to the first DL / joint TCI state, the first UL TCI state, the second DL / joint TCI state, and the second UL TCI state, respectively.

[0293] If the first TCI state, the second TCI state, and the third TCI state correspond to DL (or joint), UL, and UL, respectively, the first TCI state, the second TCI state, and the third TCI state may correspond to the first DL / joint TCI state, the first UL TCI state, and the second UL TCI state, respectively.

[0294] If the first TCI state, the second TCI state, and the third TCI state correspond to DL (or joint), DL (or joint), and UL, respectively, the first TCI state, the second TCI state, and the third TCI state may correspond to the first DL / joint TCI state, the second DL / joint TCI state, and the second UL TCI state, respectively.

[0295] For example, when two TCI states are indicated and the two TCI states indicate DL and UL, respectively, it is not possible to determine whether the two TCI states indicate a first DL TCI state and a first UL TCI state, respectively, or a second DL TCI state and a second UL TCI state, respectively.

[0296] Therefore, a field indicating the number of first (or second) TCI states per code point in the TCI field ("Ti" field (i is an integer equal to or greater than 1)) may be added to the MAC CE shown in FIG. 13 (see FIG. 14).

[0297] The UE may determine the number of first (or second) TCI states per codepoint of the corresponding TCI field based on the value of Ti.

[0298] For example, if Ti is a first value (e.g., 0) for the ith TCI field codepoint, the UE may determine that the number of first (or second) TCI states per TCI field codepoint is 1 (or 2).

[0299] For example, if Ti is a second value (e.g., 1) for the ith TCI field codepoint, the UE may determine that the number of first (or second) TCI states per TCI field codepoint is 2 (or 1).

[0300] The position of the Ti field in the MAC CE is not limited to the example in Fig. 14. For example, the Ti field may be located in an octet higher in rank (with a smaller index) than the octet of the Pi field.

[0301] Furthermore, for example, when one TCI state is indicated and the one TCI state indicates DL (or UL), it is not possible to determine whether the one TCI state indicates the first DL (UL) TCI state or the second DL (UL) TCI state.

[0302] Therefore, when a single TCI state is indicated in a MAC CE, the UE may determine that single TCI state to be the first TCI state.

[0303] Furthermore, a field / octet indicating whether the TCI state when one TCI state is indicated is the first TCI state or the second TCI state may be added to the MAC CEs shown in Figures 4, 13, and 14. Based on the field, the UE may determine whether the TCI state when one TCI state is indicated is the first TCI state or the second TCI state.

[0304] [Modification of Embodiment 4-1] The MAC CE of embodiment 4-1 may be used in at least one of a single DCI-based multi-TRP and a multi-DCI-based multi-TRP.

[0305] The UE may activate / deactivate the unified TCI state using multiple TRPs using a MAC CE that is an extension of the unified TCI state activation / deactivation MAC CE defined in Rel. 17 and earlier (see FIG. 15).

[0306] The MAC CE may include a field (“Pi” (i is an integer equal to or greater than 1)) indicating which first (joint / DL / UL) TCI state is included in the code point of the i-th TCI field.

[0307] For example, if the Pi field indicates a first value (eg, 0), it may indicate that the corresponding TCI codepoint includes a first DL / joint (or UL) TCI state.

[0308] For example, if the Pi field indicates a second value (eg, 1), it may indicate that the corresponding TCI codepoint includes a first DL / joint TCI state and a first UL TCI state.

[0309] The MAC CE may also include a field (“Qi” (i is an integer equal to or greater than 1)) indicating which second (joint / DL / UL) TCI state is included in the code point of the i-th TCI field.

[0310] For example, if the Qi field indicates a first value (eg, 0), it may indicate that the corresponding TCI codepoint includes a second DL / joint (or UL) TCI state (only).

[0311] For example, if the Qi field indicates a second value (eg, 1), it may indicate that the corresponding TCI codepoint includes a second DL / joint TCI state and a second UL TCI state.

[0312] 15 may include a field indicating whether the TCI state corresponding to the code point in the TCI field is the first TCI state or the second TCI state. The field may have a specific number of bits (e.g., 8). The field may correspond to the code point in the i-th TCI field.

[0313] If the field indicates a first value (e.g., 0 (or 1)), the UE may determine that the code point of the TCI field corresponding to the field indicates only the first TCI state.

[0314] If the field indicates a first value (eg, 0 (or 1)), the UE may ignore the value of the corresponding Qi field.

[0315] If the field indicates a second value (e.g., 1 (or 0)), the UE may determine that the code point of the TCI field corresponding to the field indicates only the second TCI state.

[0316] If the field indicates a second value (eg, 1 (or 0)), the UE may ignore the value of the corresponding Pi field.

[0317] 15 may also include a field indicating whether the TCI state corresponding to the code point of the TCI field is the first (or second) TCI state, or the first TCI state and the second TCI state. This field may have a specific number of bits (e.g., 8). This field may correspond to the code point of the i-th TCI field.

[0318] If the field indicates a first value (e.g., 0 (or 1)), the UE may determine that the code point of the TCI field corresponding to the field indicates only the first (or second) TCI state.

[0319] If the field indicates a first value (eg, 0 (or 1)), the UE may ignore the value of the corresponding Qi (or Pi) field.

[0320] If the field indicates a second value (e.g., 1 (or 0)), the UE may determine that the code point of the TCI field corresponding to the field indicates a first TCI state and a second TCI state.

[0321] 15 may also include a field indicating whether the TCI state corresponding to the code point in the TCI field is the first TCI state, the second TCI state, or both the first TCI state and the second TCI state. The field may have a specific number of bits (e.g., 18). The field may correspond to the code point in the i-th TCI field.

[0322] Based on the value of the field, the UE may determine whether the TCI state corresponding to the code point in the TCI field is the first TCI state, the second TCI state, or both the first TCI state and the second TCI state.

[0323] <<Embodiment 4-2>> The MAC CE of embodiment 4-2 may be used in multi-DCI-based multi-TRP.

[0324] The UE may activate / deactivate the unified TCI state using multiple TRPs using a MAC CE that is an extension of the unified TCI state activation / deactivation MAC CE defined in Rel. 17 and earlier (see FIG. 16).

[0325] The MAC CE may include a field indicating a CORESET pool ID (index).

[0326] When a field indicating a CORESET pool ID (index) included in a MAC CE indicates a first value (e.g., 0), the UE may determine that the MAC CE applies to a channel (e.g., PDSCH / PUSCH) associated with a CORESET having a CORESET pool index of the first value.

[0327] When a field indicating a CORESET pool ID (index) included in a MAC CE indicates a second value (e.g., 1), the UE may determine that the MAC CE applies to a channel (e.g., PDSCH / PUSCH) associated with a CORESET having a CORESET pool index of the second value.

[0328] <<Embodiment 4-3>> A UE may activate / deactivate a unified TCI state using multiple TRPs by using a unified TCI state activation / deactivation MAC CE defined up to Rel. 17.

[0329] At this time, the UE may determine whether the TCI state indicated by the MAC CE is a joint TCI state or a separate TCI state based on the value indicated by the reserved bit included in the MAC CE. In this case, the UE may make the determination using one reserved bit.

[0330] For example, if the one reserved bit indicates a first value (eg, 0), the UE may determine that the TCI state indicated in the MAC CE is a joint (or separate) TCI state.

[0331] For example, if the one reserved bit indicates a second value (for example, 1), the UE may determine that the TCI state indicated in the MAC CE is a separate (or joint) TCI state.

[0332] Furthermore, the UE may determine whether the TCI state corresponding to (the position of) the reserved bit is the joint TCI state or the separate TCI state based on the value indicated by the reserved bit included in the MAC CE. In this case, the UE may make this determination using multiple (e.g., eight) reserved bits.

[0333] For example, if the reserved bit indicates a first value (eg, 0), the UE may determine that the corresponding TCI state is a joint (or separate) TCI state.

[0334] For example, if the reserved bit indicates a second value (eg, 1), the UE may determine that the corresponding TCI state is a separate (or joint) TCI state.

[0335] According to the fourth embodiment described above, it is possible to appropriately define a MAC CE that activates a unified TCI state when using multi-TRP.

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

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

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

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

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

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

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

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

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

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

[0346] The specific UE capabilities may indicate at least one of the following: Supporting specific processing / operations / control / information for at least one of the above embodiments (e.g., unified TCI state using multiple TRPs), Supporting switching between Rel. 17 unified TCI state and Rel. 18 unified TCI state using RRC / MAC CE.

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

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

[0349] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer / physical layer signaling. For example, the specific information may be information indicating that a unified TCI state using multi-TRP is enabled, any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

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

[0351] (Supplementary Note A) The following inventions are added to one embodiment of the present disclosure. [Supplementary Note A-1] A terminal having: a control unit that determines whether to use a first unified Transmission Configuration Indication state (TCI) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state that uses the multiple TRPs; and a transceiver unit that uses the first unified TCI state to transmit and receive signals for a single TRP, or uses the second unified TCI state to transmit and receive signals to which multiple TRPs based on a single downlink control information (DCI) are applied. [Supplementary Note A-2] The terminal according to Supplementary Note A-1, wherein the control unit makes the determination based on at least one of Radio Resource Control (RRC) signaling and Medium Access Control (MAC) control elements. [Supplementary Note A-3] The terminal according to Supplementary Note A-1 or Supplementary Note A-2, wherein a size of a DCI for scheduling a specific channel when the first unified TCI state is used is different from a size of a DCI for scheduling the specific channel when the second unified TCI state is used. [Supplementary Note A-4] The terminal according to any one of Supplementary Note A-1 to Supplementary Note A-3, wherein when it is determined to use the second unified TCI state, a TCI state in which multiple TCI states are associated with a code point in one TCI field is activated.

[0352] (Appendix B) The following inventions are appended to one embodiment of the present disclosure. [Appendix B-1] A terminal having: a control unit that determines whether to use a first unified Transmission Configuration Indication state (TCI) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state that uses the multiple TRPs; and a transceiver unit that uses the first unified TCI state to transmit and receive signals for a single TRP, or uses the second unified TCI state to transmit and receive signals in which multiple TRPs are set based on multiple downlink control information (DCI). [Appendix B-2] The terminal according to Appendix B-1, wherein the control unit makes the determination based on at least one of Radio Resource Control (RRC) signaling and Medium Access Control (MAC) control elements. [Supplementary Note B-3] The terminal according to Supplementary Note B-1 or Supplementary Note B-2, wherein a size of a DCI that schedules a specific channel when the first unified TCI state is used is different from a size of a DCI that schedules the specific channel when the second unified TCI state is used. [Supplementary Note B-4] The terminal according to any one of Supplementary Note B-1 to Supplementary Note B-3, wherein the transceiver unit receives at least one of a first Medium Access Control (MAC) control element that activates a control resource set pool index and a second Medium Access Control (MAC) control element that updates the control resource set pool index.

[0353] (Supplementary Note C) The following inventions are added to one embodiment of the present disclosure. [Supplementary Note C-1] A terminal comprising: a receiving unit that receives a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) using multiple transmission / reception points (TRPs); and a control unit that determines activation of the unified TCI state based on a specific field included in the MAC CE. [Supplementary Note C-2] The terminal according to Supplementary Note C-1, wherein the specific field is at least one of a field indicating whether the MAC CE includes both a first unified TCI state and a second unified TCI state, a field indicating whether the MAC CE includes a third unified TCI state, and a field indicating whether the MAC CE includes a fourth unified TCI state. [Supplementary Note C-3] The terminal according to Supplementary Note C-1 or Supplementary Note C-2, wherein the MAC CE includes a field indicating the number of unified TCI states corresponding to one TCI code point. [Supplementary Note C-4] The terminal according to any one of Supplementary Note C-1 to Supplementary Note C-3, wherein the specific field is a control resource set ID field.

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

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

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

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

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

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

[0360] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

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

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

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

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

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

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

[0367] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

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

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

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

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

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

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

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

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

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

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

[0378] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0379] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

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

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

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

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

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

[0385] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

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

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

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

[0391] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

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

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

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

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

[0396] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

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

[0398] The control unit 110 may instruct whether to use a first unified Transmission Configuration Indication (TCI) state (Rel. 17 unified TCI state) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state (Rel. 18 unified TCI state) that uses multiple TRPs. The transceiver unit 120 may use the first unified TCI state to transmit and receive signals for a single TRP, or may use the second unified TCI state to transmit and receive signals in which multiple TRPs (single-TRP-based multi-TRP) based on a single downlink control information (DCI) are configured (first and second embodiments).

[0399] The control unit 110 may instruct whether to use a first unified Transmission Configuration Indication (TCI) state (Rel. 17 unified TCI state) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state (Rel. 18 unified TCI state) that uses the multiple TRPs. The transceiver unit 120 may use the first unified TCI state to transmit and receive signals for a single TRP, or may use the second unified TCI state to transmit and receive signals in which multiple TRPs (multi-DCI-based multi-TRPs) based on multiple downlink control information (DCIs) are configured (first and second embodiments).

[0400] The transceiver 120 may transmit a Medium Access Control (MAC) control element to activate a unified Transmission Configuration Indication (TCI) state using multiple transmission / reception points (TRPs). The controller 110 may indicate activation of the unified TCI state using a specific field included in the MAC CE (fourth embodiment).

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

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

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

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

[0405] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

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

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

[0410] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

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

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

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

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

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

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

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

[0418] The control unit 210 may determine whether to use a first unified Transmission Configuration Indication (TCI) state (Rel. 17 unified TCI state) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state (Rel. 18 unified TCI state) that uses the multiple TRPs. The transceiver unit 220 may use the first unified TCI state to transmit and receive signals for a single TRP, or may use the second unified TCI state to transmit and receive signals to which multiple TRPs based on a single downlink control information (DCI) are applied (first and second embodiments).

[0419] The control unit 210 may make the determination based on at least one of Radio Resource Control (RRC) signaling and Medium Access Control (MAC) control elements (first and second embodiments).

[0420] The size of the DCI that schedules a specific channel when the first unified TCI state is used may be different from the size of the DCI that schedules the specific channel when the second unified TCI state is used, or may be the same (first and second embodiments).

[0421] When the control unit 210 determines to use the second unified TCI state, a TCI state in which multiple TCI states are associated with a code point in one TCI field may be activated (second embodiment).

[0422] The control unit 210 may determine whether to use a first unified Transmission Configuration Indication (TCI) state (Rel. 17 unified TCI state) that does not use multiple transmission / reception points (TRPs) or a second unified TCI state (Rel. 18 unified TCI state) that uses multiple TRPs. The transceiver unit 220 may use the first unified TCI state to transmit and receive signals for a single TRP, or may use the second unified TCI state to transmit and receive signals in which multiple TRPs are configured based on multiple downlink control information (DCIs) (first and second embodiments).

[0423] The control unit 210 may make the determination based on at least one of Radio Resource Control (RRC) signaling and Medium Access Control (MAC) control elements (first and second embodiments).

[0424] The size of the DCI that schedules a specific channel when the first unified TCI state is used may be different from the size of the DCI that schedules the specific channel when the second unified TCI state is used, or may be the same (first and second embodiments).

[0425] The transceiver 220 may receive at least one of a first Medium Access Control (MAC) control element that activates a control resource set pool index and a second Medium Access Control (MAC) control element that updates the control resource set pool index (third embodiment).

[0426] The transceiver unit 220 may receive a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication (TCI) state (Rel. 18 unified TCI state) that utilizes multiple transmission / reception points (TRPs). The control unit 210 may determine activation of the unified TCI state based on a specific field included in the MAC CE (fourth embodiment).

[0427] The specific field may be at least one of a field indicating whether the MAC CE includes both a first unified TCI state and a second unified TCI state, a field indicating whether the MAC CE includes a third unified TCI state, and a field indicating whether the MAC CE includes a fourth unified TCI state (fourth embodiment).

[0428] The MAC CE may include a field indicating the number of unified TCI states corresponding to one TCI codepoint (fourth embodiment).

[0429] The specific field may be a control resource set ID field (fourth embodiment).

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

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

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

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

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

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

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

[0437] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0463] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

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

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

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

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

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

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

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

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

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

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

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

[0476] In the present 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," "panel," etc. may be used interchangeably.

[0477] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

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

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

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

[0481] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0497] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

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

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

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

[0501] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

[0506] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0507] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

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

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

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

[0511] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

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

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

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

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

[0516] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiving unit that receives downlink control information (DCI) indicating a combination of unified Transmission Configuration Indication (TCI) states, and a control unit that maintains unified TCI states that are not indicated for update by the combination among a plurality of applicable unified TCI states, wherein the combination includes at least two of a first downlink TCI state, a first uplink TCI state, a second downlink TCI state, and a second uplink TCI state, a terminal.

2. The first downlink TCI state and the first uplink TCI state correspond to a first transmission and reception point (TRP), and the second downlink TCI state and the second uplink TCI state correspond to a second TRP, the terminal according to Claim 1.

3. The receiving unit receives upper layer parameters, and the control unit determines whether to use a unified TCI state using a single transmission and reception point (TRP) or a unified TCI state using a plurality of TRPs based on the setting of the upper layer parameters, the terminal according to Claim 1.

4. The terminal according to Claim 1, further comprising a transmitting unit that transmits capability information indicating support for a unified TCI state using a plurality of transmission and reception points (TRPs).

5. A step of receiving downlink control information (DCI) indicating a combination of unified Transmission Configuration Indication (TCI) states, and a step of maintaining unified TCI states that are not indicated for update by the combination among a plurality of applicable unified TCI states, wherein the combination includes at least two of a first downlink TCI state, a first uplink TCI state, a second downlink TCI state, and a second uplink TCI state, a wireless communication method of a terminal.

6. A base station, comprising: a transmission unit that transmits downlink control information (DCI) indicating a combination of unified Transmission Configuration Indication (TCI) states; a control unit that determines that among a plurality of unified TCI states applied to a terminal, unified TCI states not indicated for update by the combination are maintained in the terminal; wherein the combination includes at least two of a first downlink TCI state, a first uplink TCI state, a second downlink TCI state, and a second uplink TCI state.

7. A system including a terminal and a base station, wherein the terminal includes: a reception unit that receives downlink control information (DCI) indicating a combination of unified Transmission Configuration Indication (TCI) states; a control unit that maintains unified TCI states not indicated for update by the combination among a plurality of unified TCI states being applied; wherein the combination includes at least two of a first downlink TCI state, a first uplink TCI state, a second downlink TCI state, and a second uplink TCI state; and the base station includes: a transmission unit that transmits the DCI.