Terminal, wireless communication method, and base station

Abstract

Appropriate application of TCI status. [Solution] The system includes a receiving unit that receives a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state using multiple transmit / receive points (TRPs), and a control unit that determines whether the TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state, based on at least one of the following: a first field included in the MAC control element that indicates the number of TCI states corresponding to TCI code points, and a second field that indicates the association between the TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

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

[0006] Furthermore, Rel.17 considers the use of a unified TCI state applicable to multiple types of signals (channel / reference signal). In addition, Rel.18 and later considers the use of a unified TCI state in systems utilizing multiple transmit / receive points (TRPs).

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

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately apply the TCI state. [Means for solving the problem]

[0009] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state that utilizes multiple transmit / receive points (TRPs); and a control unit that determines whether the TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state, based on at least one of a first field that indicates the number of TCI states corresponding to TCI code points included in the MAC control element, and a second field that indicates the association between the TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state. [Effects of the Invention]

[0010] According to one aspect of this disclosure, the TCI status can be appropriately applied. [Brief explanation of the drawing]

[0011] [Figure 1] Figures 1A and 1B show an example of a unified / common TCI framework. [Figure 2] Figures 2A and 2B show an example of a DCI-based TCI status indicator. [Figure 3] Figures 3A and 3B show examples of RRC fields and DCI fields in Rel. 17. [Figure 4] Figure 4 shows an example of a unified TCI state activation / deactivation MAC CE. [Figure 5] Figures 5A and 5B show an example of the configuration of MAC CE according to the second embodiment. [Figure 6] Figure 6 shows an example of the configuration of MAC CE according to Embodiment 3-1. [Figure 7] Figure 7 shows an example of the MAC CE configuration related to option 3-2-1. [Figure 8]FIG. 8 is a diagram showing an example of the configuration of the MAC CE according to Option 3-2-2. [Figure 9] FIG. 9 is a diagram showing an example of the configuration of the MAC CE according to the fourth embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the schematic configuration of a wireless communication system according to an embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the configuration of a base station according to an embodiment. [Figure 12] FIG. 12 is a diagram showing an example of the configuration of a user terminal according to an embodiment. [Figure 13] FIG. 13 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a vehicle according to an embodiment.

MODE FOR CARRYING OUT THE INVENTION

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

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

[0014] The TCI state is information regarding the quasi - co - location (QCL) of signals / channels, and may also be referred to as spatial reception parameters, spatial relation information, etc. The TCI state may be set for each UE for each channel or each signal.

[0015] QCL is an indicator showing the statistical properties of signals / channels. For example, when a certain signal / channel is in a QCL relationship with another signal / channel, it may mean that at least one of Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same (QCL for at least one of these) among these different multiple signals / channels.

[0016] Note that the spatial reception parameter may correspond to the reception beam of the UE (e.g., reception analog beam), and the beam may be specified based on spatial QCL. The QCL (or at least one element of QCL) in this disclosure may be read as sQCL (spatial QCL).

[0017] Multiple types (QCL types) of QCL may be defined. For example, four QCL types A - D may be provided where the parameters (or parameter sets) that can be assumed to be the same are different.

[0018] A UE's assumption that a certain control resource set (CORESET), channel, or reference signal is in a relationship of a specific QCL (e.g., QCL type D) with another CORESET, channel, or reference signal may be called a QCL assumption.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0052] If there is no DLorJointTCIState or UL-TCIState (UL TCI state) setting in the BWP within that CC, the UE can apply the DLorJointTCIState or UL-TCIState setting from the reference BWP of the reference CC. If DLorJointTCIState or UL-TCIState is set in any CC within the same band, it is not assumed that TCI-State, SpatialRelationInfo (spatial relationship information), and PUCCH-SpatialRelationInfo (PUCCH spatial relationship information) are set, except for SpatialRelationInfoPos (positional spatial relationship information) within that band. The UE assumes that if the UE sets the TCI-State in any CC within the CC list by simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE will not set the DLorJointTCIState or UL-TCIState in any CC within that CC.

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

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

[0055] (Indication of TCI status) The Rel.17 Unified TCI Framework supports the following modes 1 through 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI-based TCI state indication with DL assignment (DCI format 1_1 / 1_2 with DL assignment) [Mode 3] DCI-based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] (PUSCH repeated) In Rel.17, the introduction of PUSCH's repetition is being considered.

[0083] The RRC field and DCI field related to the repetition of PUSCH will be explained below using Figures 3A and 3B.

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

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

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

[0087] The SRS resource set indicator field has 2 bits. When the SRS resource set indicator field indicates code point "00 (0)", it indicates a single TRP operation using the first TRP (TRP1). When the SRS resource set indicator field indicates code point "01 (1)", it indicates a single TRP operation using the second TRP (TRP2). When the SRS resource set indicator field indicates code point "10 (2)", it indicates a multi-TRP operation in the order of the first TRP (TRP1) followed by the second TRP (TRP2) in the repeated PUSCH operation. When the SRS resource set indicator field indicates code point "11 (3)", it indicates a multi-TRP operation in the order of the second TRP (TRP2) followed by the first TRP (TRP1) in the repeated PUSCH operation (see Figure 3B).

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

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

[0090] (UL TCI state) In NRs Rel.16 and later, the use of the UL TCI state as a beam designation method for ULs is being considered. Notification of the UL TCI state is similar to notification of the UE's DL beam (DL TCI state). Note that the DL TCI state may be interpreted interchangeably with the TCI state for PDCCH / PDSCH.

[0091] The channel / signal (which may also be called the target channel / RS) on which the UL TCI state is set (specified) may be at least one of the following: PUSCH (DMRS for PUSCH), PUCCH (DMRS for PUCCH), Random Access Channel (Physical Random Access Channel (PRACH)), 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, the RS that has a QCL relationship with the channel / signal may be associated with the panel ID for receiving or transmitting the RS. This association may be explicitly set (or specified) by higher-layer signaling (e.g., RRC signaling, MAC CE, etc.) or implicitly determined.

[0094] The correspondence between RS and panel ID may be set in the UL TCI status information, or it may be set 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 AD, another QCL type, or may include a predetermined spatial relationship, associated antenna ports (port index), etc.

[0096] If a UE is given a relevant panel ID for a UL transmission (for example, specified by DCI), it may perform the UL transmission using the panel corresponding to that panel ID. The panel ID may also be associated with a UL TCI state, and if a UL TCI state is specified (or activated) for a given UL channel / signal, the UE may identify the panel to be used for transmitting that UL channel / signal according to the panel ID associated with that UL TCI state.

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

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

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

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

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

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

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

[0104] (Unified TCI State Activation / Deactivation MAC CE) Rel.17 specifies MAC CE for activating / deactivating the unified TCI state.

[0105] Figure 4 shows an example of a unified TCI state activation / deactivation MAC CE. The MAC CE shown in Figure 4 includes a field indicating the serving cell ID, a field indicating the DL BWP ID, a field indicating the UL BWP ID, a TCI state ID field ("TCI state ID j" (where j is an integer between 1 and N)), a field indicating the number of TCI states corresponding to the corresponding TCI code point ("Pi" (where 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 using the MAC CE to activate a unified TCI state (joint TCI state or separate (DL / UL) TCI state).

[0107] (analysis) Incidentally, future wireless communication systems (e.g., Rel.18 and later) are considering introducing a unified TCI state framework for multi-TRP operation.

[0108] It is being considered that either the application of unified TCI states defined up to Rel.17 (e.g., modes related to Rel.17) or the application of unified TCI states defined from Rel.18 onwards (e.g., modes related to Rel.18, unified TCI states in multi-TRP operation) will be performed using RRC / MAC CE.

[0109] In the multi-TRP operation of existing specifications (up to Rel.16), the number of TCI states applied to a scheduled channel (e.g., PDSCH) is controlled by the DCI (which may also be called a scheduling DCI) that schedules the channel.

[0110] Specifically, if there is one TCI state indicated by the DCI, the UE decides to use a single TRP, and if there are two TCI states indicated by the DCI, the UE decides to use a multi-TRP. In this way, the UE switches between single-TRP and multi-TRP based on the number of TCI states indicated by the DCI.

[0111] On the other hand, in cases where a multi-TRP is configured from Rel.18 onwards and a unified TCI state is applied, it is being considered that the TCI state indicated by the beam-indicating DCI will be applied starting after the transmission of the HARQ-ACK related to the DCI and after the beam application timing (BAT) has elapsed.

[0112] Therefore, if switching between single TRP and multi-TRP is performed based on the number of instructed TCI states (instructed TCI states), it is considered that switching by scheduling DCI as in the existing specifications will not be possible.

[0113] Specifically, the UE is instructed by RRC / MAC CE / DCI with up to X TCI states (indicated TCI states / unified TCI states) (where X is an integer greater than or equal to 2 (e.g., 2 or 4)), and then the scheduling DCI selects / determines one or more TCIs (e.g., two) from these X TCI states.

[0114] In Rel.18 and later versions, where such cases are possible, the UE cannot recognize how many TCI states have been indicated until the DCI decoding is complete.

[0115] Therefore, in Rel.18 and later, a DCI field (which may also be called a TCI selection field) has been introduced to switch between single TRP and multi-TRP for scheduled DL channels / signals, and its use in modes related to Rel.18 is being considered.

[0116] It is being considered that the DCI format for scheduling / activating DL channels / signals (e.g., DCI format 1_1 / 1-2 (which may also be called DL DCI)) should include certain fields (new DCI fields, TCI selection fields).

[0117] The DL channel / signal may be, for example, a PDSCH / CSI-RS. In this disclosure, the PDSCH may be a PDSCH dynamically scheduled by DCI, or a semi-persistently scheduled PDSCH (SPS PDSCH). In this disclosure, the CSI-RS may be an A / SP / P-CSI-RS.

[0118] When the code point of a particular field contained in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a first value (e.g., "00"), the UE may apply a particular indicating TCI state (e.g., the first indicating (joint / DL) TCI state of two indicating (joint / DL) TCI states) to multiple (e.g., all) DL channels / signals (e.g., multiple (all) PDSCH DMRS ports corresponding to one or more PDSCH transmission opportunities) scheduled by that DCI.

[0119] When the code point of a particular field contained in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a second value (e.g., "01"), the UE may apply a particular indicating TCI state (e.g., the second indicating (joint / DL) TCI state of two indicating (joint / DL) TCI states) to multiple (e.g., all) DL channels / signals (e.g., multiple (all) PDSCH DMRS ports corresponding to one or more PDSCH transmission opportunities) scheduled by that DCI.

[0120] When the code point of a particular field in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a third value (e.g., "10"), the UE may apply multiple indicative TCI states (e.g., both the first indicative (joint / DL) TCI state and the second indicative (joint / DL) TCI state) to the reception of the DL channel / signal scheduled by that DCI.

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

[0122] When the code point of a particular field in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a fourth value (e.g., "11"), the UE may use a specific method to determine whether to apply the indicated TCI state.

[0123] For example, when the code point of a particular field in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a fourth value (e.g., "11"), the UE may apply multiple indicator TCI states (e.g., both the first indicator (joint / DL) TCI state and the second indicator (joint / DL) TCI state) to the reception of the DL channel / signal scheduled by that DCI.

[0124] For example, when the code point of a particular field in a DL DCI (e.g., DCI format 1_1 / 1_2) indicates a fourth value (e.g., "11"), the multiple indicating TCI states may be applied in a second order (e.g., second indicating TCI state followed by first indicating TCI state).

[0125] However, when introducing this specific field, there may be cases where the number of bits / size / payload of the DL DCI in the Rel.17 mode differs from that in the Rel.18 mode. In this case, the UE may not be able to properly decode the DCI. Furthermore, the size of this DCI has not been sufficiently considered.

[0126] Furthermore, the MAC CE for activating / deactivating TCI states in the unified TCI state framework specified in Rel.17 includes a field ("Pi" (where i is an integer greater than or equal to 1)) indicating the number of TCI states (TCI state IDs) corresponding to the corresponding TCI code point. On the other hand, in the unified TCI state framework specified in Rel.18, if the number of corresponding TCI states remains the same as before, there will be insufficient number of TCI states that can be instructed.

[0127] However, the configuration of MAC CEs for activating / deactivating TCI states in the unified TCI state framework specified in Rel.18 has not been sufficiently considered.

[0128] Furthermore, MAC CE for activating / deactivating the unified TCI state in multi-DCI-based multi-TRP systems has not been sufficiently considered.

[0129] If these considerations are insufficient, the TCI state to be applied to each channel / signal may not be determined correctly, potentially leading to a decrease in communication throughput.

[0130] Therefore, the inventors devised a method for appropriately performing operations related to the unified TCI state.

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

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

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

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

[0135] In this disclosure, the upper-layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages).

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

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

[0138] In this disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interpreted as mutually exclusive.

[0139] In this disclosure, the terms single DCI, single PDCCH, multi-TRP based on a single DCI, activating two TCI states on at least one TCI code point, mapping at least one code point of a TCI field to two TCI states, and setting up a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a particular channel / CORESET may be interpreted as mutually exclusive.

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

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

[0142] In this disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI code point may be interpreted as mutually exclusive.

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

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

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

[0146] In this disclosure, a first TRP may correspond to a first TCI state (the first indicated TCI state). In this disclosure, a second TRP may correspond to a second TCI state (the second indicated TCI state). In this disclosure, an nth TRP may correspond to an nth TCI state (the nth indicated TCI state).

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

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

[0149] In this disclosure, schedule, trigger, and activate may be interpreted interchangeably. In this disclosure, operation, option, and choice may be interpreted interchangeably.

[0150] In this disclosure, TCI state, indicated TCI state, unified TCI state, and indicated joint / DL TCI state may be interpreted as mutually exclusive.

[0151] In this disclosure, the unified / indicating TCI states defined in Rel.17, the Rel.17 unified / indicating TCI states, the unified / indicating TCI states not corresponding to multi-TRP operation, and the unified / indicating TCI states may be interpreted interchangeably. In this disclosure, the unified / indicating TCI states defined in Rel.18, the Rel.18 unified / indicating TCI states, the unified / indicating TCI states corresponding to multi-TRP operation, and the unified / indicating TCI states may be interpreted interchangeably.

[0152] In this disclosure, the term "Unified / Indicative TCI State" may be used with or without the prefix Rel.X (where X is any number). In this disclosure, Rel.X and subsequent terms are interchangeable.

[0153] In this disclosure, the terms "Application of Unified TCI State as defined up to Rel.17", "Modes relating to Rel.17", "Modes relating to Rel.17 TCI State", "Modes relating to Rel.17 Unified TCI State", "Rel.17 TCI Mode", "Rel.17 Unified TCI State Mode", and "First Mode / Setting" may be interpreted interchangeably. In this disclosure, the terms "Application of Unified TCI State as defined in Rel.18", "Modes relating to Rel.18", "Modes relating to Rel.18 TCI State", "Modes relating to Rel.18 Unified TCI State", "Rel.18 TCI Mode", "Rel.18 Unified TCI State Mode", and "Second Mode / Setting" may be interpreted interchangeably.

[0154] In this disclosure, MAC CE for Rel.17 Unified TCI State, MAC CE for Activating / Deactivating Rel.17 Unified TCI State, and the First MAC CE may be interpreted as mutually exclusive. In this disclosure, MAC CE for Rel.18 Unified TCI State, MAC CE for Activating / Deactivating Rel.18 Unified TCI State, and the Second MAC CE may be interpreted as mutually exclusive.

[0155] In this disclosure, the following can be interpreted interchangeably: setting a Rel.18 unified TCI state, setting a Rel.18 unified TCI state for a single DCI-based multi-TRP, and setting a DCI field for Rel.18 (e.g., a TCI selection field).

[0156] In this disclosure, size, number of bits, fields, and payload may be interpreted as interchangeable.

[0157] (Wireless communication method) <First Embodiment> The first embodiment relates to the size / bit count / payload of DCI.

[0158] The DCI in this embodiment may be, for example, a DCI related to multi-TRP operation (beam-indicating DCI).

[0159] In this embodiment, the DCI may be, for example, a DCI related to the indication of the unified TCI state (beam indication DCI).

[0160] The DCI in this embodiment may be, for example, a DCI (beam-indicating DCI) for single-DCI-based multi-TRP operation.

[0161] The Rel.18 Unified TCI state in this embodiment may be, for example, the Unified TCI state in a single DCI-based multi-TRP operation.

[0162] The first embodiment is broadly divided into embodiments 1-1 and 1-2. The UE / network (NW, e.g., base station) may be configured to apply either embodiment 1-1 or 1-2, or a combination of embodiments 1-1 and 1-2.

[0163] Embodiment 1-1 The size of the DCI may be determined based on specific settings.

[0164] This specific setting may be configured, for example, through higher-layer signaling (e.g., RRC).

[0165] The UE may determine the size of the DCI based on specific RRC settings. The NW may determine the size of the DCI based on specific RRC settings.

[0166] For example, the size of the DCI may be constant in a particular RRC configuration.

[0167] For example, UE may assume / determine that the size of DCI is constant in a particular RRC configuration.

[0168] [Option 1-1-1] The first mode and the second mode may be set / switched based on RRC signaling.

[0169] If a second mode is set for the UE, the UE may assume / expect / determine that the (unified) TCI state will be activated / deactivated using the second MAC CE.

[0170] If a second mode is set for the UE, the UE does not need to assume / expect / determine that the (unified) TCI state will be activated / deactivated using the first MAC CE.

[0171] [Option 1-1-2] The first and second modes may be configured / switched based on RRC signaling / MAC CE.

[0172] If a second mode is set for a UE by RRC signaling, the UE may assume / expect / determine that the (unified) TCI state will be activated / deactivated using either the first MAC CE or the second MAC CE.

[0173] The size of the DL DCI (e.g., DCI format 1_1 / 1_2) may be determined based on the RRC parameters set.

[0174] For example, if at least one of the second mode and the existence of a specific field in the DCI (e.g., a TCI selection field) is set using RRC, the UE may assume / determine that the specific field exists in the DL DCI.

[0175] When a UE receives a first MAC CE instruction, the UE may ignore the value of the specific field. The first MAC CE instruction may mean at least one of the following: that each TCI code point has one joint / DL TCI state, and that each TCI code point has one UL TCI state.

[0176] In this case, for example, the UE may reuse the particular field for other purposes. The UE may determine that the particular field will be used for other purposes.

[0177] When a second MAC CE instructs a UE, the UE may use the value of the specific field to determine whether to use a single TRP or a multi-TRP. When a second MAC CE instructs a UE, the value of the specific field may be used to instruct the UE to dynamically switch between single-TRP and multi-TRP. The second MAC CE instruct may mean at least one of the following: that each TCI code point has one or more joint / DL TCI states, and that each TCI code point has one or more UL TCI states.

[0178] Embodiment 1-2 The size of the DCI may be determined based on specific instructions.

[0179] The specific instruction in question may be, for example, an instruction via higher-layer signaling (e.g., MAC CE).

[0180] The UE may determine the size of the DCI based on the instructions of a specific MAC CE. The NW may determine the size of the DCI based on the instructions of a specific MAC CE.

[0181] For example, the size of the DCI may be constant in a particular MAC CE instruction. For example, the size of the DCI may not be constant in a particular RRC configuration.

[0182] For example, the UE may assume / determine that the size of the DCI is constant in the instructions for a particular MAC CE.

[0183] For example, UE may assume / determine that the size of DCI is not constant in a particular RRC configuration.

[0184] The first mode and the second mode may be configured / instructed / switched based on MAC CE.

[0185] If a second mode is set / instructed to the UE by the MAC CE, the UE may assume / expect / determine that the (unified) TCI state will be activated / deactivated using either the first MAC CE or the second MAC CE.

[0186] The size of the DL DCI (e.g., DCI format 1_1 / 1_2) may be determined based on the number of (joint / DL / UL) TCI states corresponding to each TCI code point included in the configured / instructed MAC CE.

[0187] For example, if at least one of the second mode and the existence of a specific field in the DCI (e.g., a TCI selection field) is set / instructed, and an instruction is given to use the first MAC CE, the UE may assume / determine that the specific field does not exist in the DL DCI.

[0188] The first MAC CE instruction may mean at least one of the following: that each TCI code point has one joint / DL TCI state, and that each TCI code point has one UL TCI state.

[0189] For example, if at least one of the second mode and the existence of a specific field in the DCI (e.g., a TCI selection field) is set / instructed, and an instruction is given to use the second MAC CE, the UE may assume / determine that the specific field exists in the DL DCI.

[0190] The second MAC CE instruction may mean at least one of the following: that a minimum of one TCI code point has one or more joint / DL TCI states, and that a minimum of one TCI code point has one or more UL TCI states.

[0191] In this case, the value of the specific field may be used to instruct the UE to dynamically switch between single TRP and multi-TRP.

[0192] According to the first embodiment described above, the DCI size for indicating the TCI state can be appropriately determined.

[0193] <Second Embodiment> The second embodiment relates to the configuration of a second MAC CE.

[0194] The second MAC CE may include a field (e.g., "Pi" (where i is an integer greater than or equal to 1)) indicating the number of TCI states (TCI state IDs) corresponding to the corresponding TCI code point. This field may be called the second field.

[0195] The second field may be an extension of the first field, which indicates the number of TCI states (TCI state IDs) corresponding to the corresponding TCI code points included in the first MAC CE (e.g., "Pi" (where i is an integer greater than or equal to 1).

[0196] For example, the number of bits in the second field may be different from the number of bits in the first field. For example, the number of bits in the second field may be greater than the number of bits in the first field.

[0197] For example, the second field may be defined by combining (adding) the first field with other fields.

[0198] For example, the number of bits in the second field may be a specific number of bits (e.g., 2 bits).

[0199] For example, if the second field indicates a first value (e.g., "00"), it may indicate that the number of TCI states / TCI state IDs for the corresponding TCI code point is a first number (e.g., 1).

[0200] For example, if the second field indicates a second value (e.g., "01"), it may indicate that the number of TCI states / TCI state IDs for the corresponding TCI code point is a second number (e.g., 2).

[0201] For example, if the second field indicates a third value (e.g., "10"), it may indicate that the number of TCI states / TCI state IDs for the corresponding TCI code point is a third number (e.g., 3).

[0202] For example, if the second field shows a fourth value (e.g., "11"), it may indicate that the number of TCI states / TCI state IDs for the corresponding TCI code point is the fourth number (e.g., four).

[0203] The maximum number of TCI states / TCI state IDs that can be indicated for each TCI code point may be a first number (e.g., 1) or a second number (e.g., 2) in the case of a joint TCI state. The maximum number of TCI states / TCI state IDs that can be indicated for each TCI code point may be any of the first number (e.g., 1) through a fourth number (e.g., 4) in the case of a separate (DL / UL) TCI state.

[0204] Either the joint TCI state or the separate (DL / UL) TCI state may be set / indicated using RRC / MAC CE.

[0205] Regardless of whether a joint TCI state or a separate (DL / UL) TCI state is set / indicated, the UE may assume / determine that the second field has a specific number of bits (e.g., 2 bits).

[0206] The UE may assume / determine the number of bits in the second field based on whether a joint TCI state or a separate (DL / UL) TCI state is set / indicated.

[0207] For example, if the Joint TCI state is set / indicated, the UE may assume / determine that the second field has a number of bits less than a certain number (e.g., 1 bit). For example, if the Separate TCI state is set / indicated, the UE may assume / determine that the second field has a certain number of bits (e.g., 2 bits). This allows for a reduction in MAC CE overhead depending on the configuration.

[0208] The second MAC CE may include a field ("D / U") indicating that the TCI status of the corresponding TCI status field is DL / Joint or UL.

[0209] For example, if the field shows a first value (e.g., 0), the UE may determine that the TCI state of the corresponding TCI state field is the UL TCI state. For example, if the field shows a second value (e.g., 1), the UE may determine that the TCI state of the corresponding TCI state field is the Joint / DL TCI state.

[0210] The MAC CE used to indicate the joint TCI state and the MAC CE used to indicate the separate TCI state may be the same MAC CE.

[0211] The MAC CE used to indicate the joint TCI state and the MAC CE used to indicate the separate TCI state may be different MAC CEs.

[0212] Figures 5A and 5B show examples of the configuration of a MAC CE according to the second embodiment. In the examples shown in Figures 5A and 5B, the fields included in the MAC CE indicate whether the state is joint TCI or separate (DL / UL) TCI. These fields may be the hatched fields (locations of reserved bit fields) shown in each figure.

[0213] Figure 5A shows a MAC CE indicating the joint TCI state. In this case, the "Pi" field in this MAC CE is represented by 1 bit.

[0214] Figure 5B shows a MAC CE indicating that the separate TCI state is indicated. In this case, the "Pi" field in this MAC CE is represented by 2 bits.

[0215] According to the second embodiment described above, it is possible to appropriately indicate the unified TCI state related to multi-TRP while facilitating implementation.

[0216] <Third Embodiment> The third embodiment relates to the configuration of the second MAC CE.

[0217] The third embodiment allows for more flexible indication of the TCI state compared to the second embodiment described above.

[0218] The third embodiment is broadly divided into embodiments 3-1 and 3-2. The UE / network (NW, e.g., base station) may be configured to apply either embodiment 3-1 or 3-2, or a combination of embodiments 3-1 and 3-2.

[0219] Embodiment 3-1 If a joint TCI state is set / instructed for a UE, and the second field (for example, a field indicating the number of TCI states (TCI state IDs) corresponding to the corresponding TCI code point (for example, "Pi" (where i is an integer greater than or equal to 1))) indicates a first value (for example, 0), then the number of corresponding TCI states (TCI state IDs) may be one.

[0220] In this case, the MAC CE may include a field (for example, "Qi" (where i is an integer greater than or equal to 1) indicating whether the single TCI state corresponds to a first TCI state or a second TCI state (see Figure 6). In this disclosure, this field may also be called a third field, which may indicate the association between the TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state.

[0221] The field names included in MAC CE as shown in this disclosure are merely examples and are not limited to these examples. Furthermore, the association between the value represented by a field and the meaning of the corresponding field is also merely an example and is not limited to these examples.

[0222] The third field may be defined / exist / appear based on the value of the second field.

[0223] For example, the third field may be included in the MAC CE if at least one of the second fields indicates a first value (e.g., 0). For example, the third field may not be included in the MAC CE if all of the second fields indicate a second value (e.g., 1).

[0224] When the third field shows a first value (e.g., 0), the UE may determine that the corresponding TCI state is the first (or second) TCI state. When the third field shows a second value (e.g., 1), the UE may determine that the corresponding TCI state is the second (or first) TCI state.

[0225] Embodiment 3-2 The UE may be set / instructed to be in a separate TCI state.

[0226] In Embodiment 3-2, the second field may have a specific number of bits (for example, 2 bits).

[0227] For example, when the second field indicates a first value (e.g., "00") (where there is only one TCI state / TCI state ID for the corresponding TCI code point), a bit field (e.g., 1 bit) is needed to indicate whether the TCI state corresponding to each TCI state ID is the first TCI state or the second TCI state.

[0228] For example, when the second field indicates a second value (e.g., "01") (and there are two TCI states / TCI state IDs for the corresponding TCI code point), there are four possible patterns for the TCI states corresponding to each TCI state ID: (DL,DL), (DL,UL), (UL,DL), and (UL,UL).

[0229] In the case of patterns (DL,DL) and (UL,UL), for example, by determining / defining the TCI state corresponding to the first TCI state ID as the first TCI state and the TCI state corresponding to the second TCI state ID as the second TCI state, it is considered unnecessary to have a bit field indicating whether the corresponding TCI state is the first or second TCI state.

[0230] On the other hand, in the case of the (DL,UL) and (UL,DL) patterns, it is thought that a bit field is needed to indicate whether the corresponding TCI state is the first TCI state or the second TCI state.

[0231] For example, UE may assume / determine that the pattern of the two corresponding TCI states is only the pattern (DL,UL) (or the pattern (UL,DL)).

[0232] If the pattern of the two corresponding TCI states is (DL, UL), then the field needs to indicate whether each TCI state is (first DL TCI state (ID), first UL TCI state (ID)), (first DL TCI state (ID), second UL TCI state (ID)), (second DL TCI state (ID), first UL TCI state (ID)), or (second DL TCI state (ID), second UL TCI state (ID)). Therefore, it is considered that the bit field indicating whether the corresponding TCI state is the first or second TCI state requires at least two bits.

[0233] For example, when the second field indicates a third value (e.g., "10") (where the corresponding TCI code point has three TCI states / TCI state IDs), there are two possible TCI state patterns corresponding to each TCI state ID: (DL,DL,UL) and (DL,UL,UL).

[0234] Therefore, for TCI states of the same type (DL or UL), it is considered unnecessary to have a bit field indicating whether the corresponding TCI state is the first or second TCI state, by determining / defining, for example, the TCI state corresponding to the first TCI state ID as the first TCI state, and the TCI state corresponding to the second TCI state ID as the second TCI state.

[0235] Otherwise, for the UL TCI state in the case of (DL,DL,UL) and the DL TCI state in the case of (DL,UL,UL), a bit field (e.g., 1 bit) is considered necessary to indicate whether it is the first TCI state or the second TCI state.

[0236] For example, when the second field indicates a fourth value (e.g., "11") (where there are four TCI states / TCI state IDs for the corresponding TCI code point), the only possible TCI state pattern corresponding to each TCI state ID is (DL, DL, UL, UL). Therefore, for example, by determining / defining DL and UL, the TCI state corresponding to the first TCI state ID as the first TCI state and the TCI state corresponding to the second TCI state ID as the second TCI state, respectively, it is considered unnecessary to have a bit field indicating whether the corresponding TCI state is the first or second TCI state.

[0237] Thus, the existence and number of bits of fields included in MAC CE have not been sufficiently examined.

[0238] In this embodiment, a field for indicating whether the corresponding TCI state is a first TCI state or a second TCI state will be described.

[0239] The MAC CE may include a bit field indicating whether the corresponding TCI state is a first TCI state or a second TCI state. In this disclosure, the field may also be a field indicating an association between the TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state.

[0240] The field may be defined / exist / appear based, for example, on the value of a second field (for example, a field indicating the number of TCI states (TCI state IDs) corresponding to the corresponding TCI code point (e.g., "Pi" (where i is an integer greater than or equal to 1))).

[0241] The field in question may be defined / exist / appear regardless of the value of the second field, for example.

[0242] [Option 3-2-1] The field in question may be defined, for example, by a combination of multiple fields.

[0243] The field may include, for example, at least one of a fourth field (e.g., "Qi" (where i is an integer greater than or equal to 1)) and a fifth field (e.g., "Ni" (where i is an integer greater than or equal to 1)) (see Figure 7).

[0244] The fourth and fifth fields may each be defined by a specific number of bits (for example, 1 bit).

[0245] The fourth field may be referenced, for example, when the second field indicates the first / second / third value. The fourth field may be ignored, for example, when the second field indicates the fourth value.

[0246] A fourth field may exist, for example, when the second field represents the first / second / third values.

[0247] The fifth field may be referenced, for example, when the second field indicates a second value. The fifth field may be ignored, for example, when the second field indicates a value other than the second value.

[0248] The fifth field may exist, for example, when the second field indicates a second value.

[0249] By configuring the MAC CE as in Option 3-2-1, MAC CE overhead can be reduced by defining only the minimum necessary MAC CE fields / octets.

[0250] [Option 3-2-2] A field indicating whether the corresponding TCI state is a first TCI state or a second TCI state may be defined, for example, as a single field.

[0251] In this disclosure, the field may be referred to as the sixth field (for example, "Qi" (where i is an integer greater than or equal to 1)) (see Figure 8).

[0252] The sixth field may be defined by a specific number of bits (for example, 2 bits).

[0253] For example, when the sixth field indicates a first value (e.g., "00"), the UE may determine that the DL TCI state corresponding to the first (or second) TCI state ID field and the UL TCI state corresponding to the first (or second) TCI state ID field are the first DL TCI state and the first UL TCI state, respectively.

[0254] For example, when the sixth field indicates a second value (e.g., "01"), the UE may determine that the DL TCI state corresponding to the first (or second) TCI state ID field and the UL TCI state corresponding to the first (or second) TCI state ID field are the first DL TCI state and the second UL TCI state, respectively.

[0255] For example, when the sixth field indicates a third value (e.g., "10"), the UE may determine that the DL TCI state corresponding to the first (or second) TCI state ID field and the UL TCI state corresponding to the first (or second) TCI state ID field are the second DL TCI state and the first UL TCI state, respectively.

[0256] For example, when the sixth field indicates a fourth value (e.g., "11"), the UE may determine that the DL TCI state corresponding to the first (or second) TCI state ID field and the UL TCI state corresponding to the first (or second) TCI state ID field are the second DL TCI state and the second UL TCI state, respectively.

[0257] Please note that the correspondence between the values ​​of these fields and the application of the TCI status is merely an example and is not limited to the examples shown.

[0258] By configuring MAC CE as in option 3-2-2, it is possible to properly instruct the UE on how to associate TCI states without complicating its operation.

[0259] According to the third embodiment described above, it is possible to appropriately indicate whether the TCI state activated by MAC CE is the first TCI state or the second TCI state.

[0260] <Fourth Embodiment> The fourth embodiment relates to the configuration of the second MAC CE.

[0261] The second MAC CE may be a MAC CE for multi-DCI based multi-TRP.

[0262] The configuration of the second MAC CE may be an extension / modification of the configuration of the first MAC CE.

[0263] The second MAC CE may include at least one of the following fields: a field indicating the CORESET pool index (e.g., "CORESETPoolIndex"), a field indicating the serving cell ID, a field indicating the DL BWP ID, a field indicating the UL BWP ID, a TCI state ID field ("TCI state ID j" (where j is an integer between 1 and N)), a field indicating the number of TCI states corresponding to the corresponding TCI code point ("Pi" (where 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") (see Figure 9).

[0264] The UE may determine whether the TCI state indicated by the MAC CE corresponds to either the first CORESET pool index or the second CORESET pool index based on the field indicating the CORESET pool index.

[0265] For example, when the field indicating the CORESET pool index indicates a first value (e.g., "0"), the UE may determine that the TCI state indicated by the field corresponds to the CORESET pool index of the first value (e.g., "0").

[0266] For example, when the field indicating the CORESET pool index indicates a first value (e.g., "1"), the UE may determine that the TCI state indicated by the field corresponds to the CORESET pool index of the second value (e.g., "1").

[0267] According to the above fourth embodiment, the activation / deactivation of the unified TCI state in the multi-DCI-based multi-TRP can be appropriately performed.

[0268] <Variation> In the present disclosure, the MAC CE for joint TCI state indication and the MAC CE for separate TCI state indication may be defined as a common MAC CE or as different MAC CEs.

[0269] For each embodiment of the present disclosure, the embodiment for the indication of the separate TCI state may be applied to the joint TCI state indication method, or the embodiment for the joint TCI state indication may be applied to the separate TCI state indication method.

[0270] In this disclosure, a MAC CE for single DCI-based multi-TRP and a MAC CE for Rel.17 unified TCI state may be identified by different Logical Channel IDs (LCIDs).

[0271] In this disclosure, the MAC CE for multi-DCI and the MAC CE for the Rel.17 unified TCI state may be identified by different LCIDs or by a common LCID.

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

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

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

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

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

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

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

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

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

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

[0282] The specific UE capability may represent at least one of the following: • To support specific processing / operations / controls / information (e.g., Rel.18 Unified TCI State) for at least one of the above embodiments. • The number of unified TCI states supported.

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

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

[0285] Furthermore, at least one of the embodiments described above may be applied when the UE is set / activated / triggered by upper layer signaling / physical layer signaling to perform certain information (or the actions of the embodiments described above) related to the embodiments described above. For example, such certain information may be information indicating the activation of the Rel.18TCI state, or any RRC parameters for a particular release (e.g., Rel.18 / 19).

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

[0287] (Supplementary Note) Regarding one embodiment of the present disclosure, the following inventions are appended. [Supplementary Note 1] A receiving unit that receives a Medium Access Control (MAC) control element for activating a unified Transmission Configuration Indication state (TCI) state using a plurality of transmission and reception points (TRPs), Based on at least one of a first field indicating the number of TCI states corresponding to a TCI code point included in the MAC control element, and a second field indicating an association between the TCI state corresponding to each TCI state ID field and either a first TCI state or a second TCI state, a control unit that determines which of the first TCI state and the second TCI state the TCI state corresponding to each TCI state ID field corresponds to, a terminal having the control unit. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the control unit determines the size of beam indication downlink control information based on at least one of settings and instructions using upper layer signaling. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the number of bits of the first field is different between the case where a joint TCI state is set and the case where a separate TCI state is set. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the control unit determines the presence of the second field based on the value of the first field.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0332] The transmitting / receiving unit 120 may transmit a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state that utilizes multiple transmitting / receiving points (TRPs). The control unit 110 may indicate whether the TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state by using at least one of the following in the MAC control element: a first field indicating the number of TCI states corresponding to TCI code points, and a second field indicating the association between each TCI state ID field and either the first TCI state or the second TCI state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0349] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

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

[0351] The transmitting / receiving unit 220 may receive a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state that utilizes multiple transmitting / receiving points (TRPs). The control unit 210 may determine whether the TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state, based on at least one of a first field included in the MAC control element, which indicates the number of TCI states corresponding to TCI code points, and a second field which indicates the association between the TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state.

[0352] The control unit 210 may determine the size of the beam instruction downlink control information based on at least one of the settings and instructions using upper-layer signaling.

[0353] The number of bits in the first field may differ depending on whether a joint TCI state is set or a separate TCI state is set.

[0354] The control unit 210 may determine the presence of the second field based on the value of the first field.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0401] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0402] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0403] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0404] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., may be interpreted as being interchangeable.

[0405] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0406] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL properties," "specific QCL type (e.g., type A, type D) properties," and "specific QCL type (e.g., type A, type D)" may be interpreted as interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0438] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered as "judging (deciding)" something about an action. In this disclosure, "judgment (decision)" may be interpreted interchangeably with the actions described above.

[0439] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not assuming that…” may be interpreted as “assuming that…”

[0440] In this disclosure, “expect” may be interpreted as “be expected.” For example, “expect(s) …” (where “...” may be expressed as a that clause, an infinitive, etc.) may be interpreted as “be expected ….” “does not expect …” may be interpreted as “be not expected ….” Furthermore, “An apparatus A is not expected …” may be interpreted as “An apparatus B other than apparatus A does not expect …” (for example, if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

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

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

[0449] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately 0 (immediately after or immediately before). A time offset may also be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on the information provided.

[0450] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0451] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

Claims

1. A receiving unit that receives a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state using multiple transmit / receive points (TRPs), A terminal having a control unit that determines whether a TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state, based on at least one of a first field indicating the number of TCI states corresponding to a TCI code point included in the MAC control element, and a second field indicating the association between a TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state.

2. The terminal according to claim 1, wherein the control unit determines the size of beam instruction downlink control information based on at least one of settings and instructions using upper layer signaling.

3. The terminal according to claim 1, wherein the number of bits in the first field differs depending on whether a joint TCI state is set or a separate TCI state is set.

4. The terminal according to claim 1, wherein the control unit determines the existence of the second field based on the value of the first field.

5. The steps include receiving a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state using multiple transmit / receive points (TRPs), A wireless communication method for a terminal, comprising the step of determining whether a TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state, based on at least one of a first field indicating the number of TCI states corresponding to a TCI code point included in the MAC control element, and a second field indicating the association between a TCI state corresponding to each TCI state ID field and either the first TCI state or the second TCI state.

6. A transmitting unit that transmits a Medium Access Control (MAC) control element that activates a unified Transmission Configuration Indication state (TCI) state using multiple transmit / receive points (TRPs), A base station having a control unit that indicates whether a TCI state corresponding to each TCI state ID field corresponds to the first TCI state or the second TCI state, using at least one of a first field indicating the number of TCI states corresponding to a TCI code point included in the MAC control element, and a second field indicating the association between a TCI state corresponding to each TCI state ID field and either a first TCI state or a second TCI state.

Images