Terminal, wireless communication method, base station and system

Abstract

A terminal according to an aspect of the present disclosure has: a transmission unit that simultaneously transmits a first UL channel scheduled by first downlink control information (DCI) corresponding to a first control resource pool index, and a second UL channel scheduled by second DCI corresponding to a second control resource pool index; and a control unit that determines a sounding reference signal (SRS) resource related to the first UL channel by means of the first DCI, and determines a sounding reference signal (SRS) resource related to the second UL channel by means of the second DCI.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

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

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

[0008] A terminal according to one aspect of the present disclosure includes a transmitter that simultaneously transmits a first UL channel scheduled by first downlink control information (DCI) corresponding to a first control resource pool index and a second UL channel scheduled by a second DCI corresponding to a second control resource pool index, and a controller that determines a sounding reference signal (SRS) resource associated with the first UL channel by the first DCI and determines a sounding reference signal (SRS) resource associated with the second UL channel by the second DCI.

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

[0010] 1A and 1B are diagrams illustrating an example of a unified / common TCI framework. FIGS. 2A and 2B are diagrams illustrating an example of a DCI-based TCI status indication. FIG. 3 is a diagram illustrating an example of an application time of a unified TCI status indication. FIGS. 4A to 4D are diagrams illustrating an example of a multi-TRP. FIGS. 5A and 5B are diagrams illustrating an example of a beam indication method for a multi-TRP. FIGS. 6A and 6B are diagrams illustrating an example of a unified / common TCI framework when a CORESET pool index is configured. FIG. 7 is a diagram illustrating an example of a problem in applying the unified / common TCI framework to UL channels / signals or DL ​​reference signals when a CORESET pool index is configured. FIG. 8 is a diagram illustrating an example of a method for determining a unified / common TCI status when a CORESET pool index is configured according to the first embodiment. FIG. 9 is a diagram illustrating an example of a timing advance group (TAG) to which cells included in a cell group belong. FIG. 10 is a diagram illustrating an example of a MAC CE for a timing advance command. Fig. 11 is a diagram illustrating an example of a method for determining a unified / common TCI state and a TAG when a CORESET pool index is configured according to the second embodiment. Fig. 12 is a diagram illustrating an example of a method for determining an SRS resource in UL transmission (e.g., PUSCH transmission) according to the third embodiment. Fig. 13 is a diagram illustrating another example of a method for determining an SRS resource in UL transmission (e.g., PUSCH transmission) according to the third embodiment. Fig. 14 is a diagram illustrating another example of a method for determining an SRS resource in UL transmission (e.g., PUSCH transmission) according to the third embodiment. Figs. 15A and 15B are diagrams illustrating examples of joint ACK / NACK feedback and separate ACK / NACK feedback, respectively. Fig. 16 is a diagram illustrating an example of a method for configuring a PUCCH resource according to the third embodiment. Fig. 17 is a diagram illustrating another example of a method for configuring a PUCCH resource according to the third embodiment. Fig. 18 is a diagram illustrating another example of a method for configuring a PUCCH resource according to the third embodiment. Fig. 19 is a diagram showing another example of the method for configuring PUCCH resources according to the third embodiment. Fig. 20 is a diagram showing another example of the method for configuring PUCCH resources according to the third embodiment.Fig. 21 is a diagram showing another example of a PUCCH resource configuration method according to the third embodiment. Fig. 22 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 23 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 24 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 25 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. Fig. 26 is a diagram showing an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may assume different TCI states for UL and DL (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool). Whether the joint TCI state or the separate TCI state is applied may be configured (or switched) by the RRC / MAC CE.

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

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

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

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

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

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

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

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

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

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

[0060] It is assumed that N = M = 1 is supported in Rel. 17. For example, it is supported to indicate one common beam (e.g., a common beam) by RRC / MAC CE / DCI, and the one common beam may be applied to multiple DL / UL channels / reference signals.

[0061] 1A and 1B illustrate an example of a unified TCI framework. FIG. 1A illustrates an example of a joint DL / UL TCI state, and FIG. 1B illustrates an example of a separate TCI state.

[0062] In the example of FIG. 1A , RRC parameters (information elements) configure multiple TCI states for both DL and UL. In this disclosure, the TCI states configured by the RRC parameters may be referred to as configured TCI states or configured TCI states (e.g., configured TCI states). The MAC CE may activate multiple TCI states from the configured TCI states. The DCI may indicate one of the activated TCI states. In this disclosure, the TCI state indicated by the DCI may be referred to as indicated TCI state or indicated TCI state (e.g., indicated TCI state).

[0063] The DCI may be a UL DCI (e.g., a DCI used to schedule a PUSCH) or a DL DCI (e.g., a DCI used to schedule a PDSCH). The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both a UL TCI and a DL TCI.

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

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

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

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

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

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

[0070] The method of setting / indicating the TCI state (e.g., joint DL / UL TCI state) in Fig. 1A and the method of setting / indicating the application of the TCI state (e.g., separate TCI state) in Fig. 1B may be switched between. Whether the joint DL / UL TCI state or the separate TCI state is applied may be configured by a base station to the UE by a higher layer parameter.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084] Regarding the Rel. 17 TCI state, a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using (Rel. 17) MAC CE / RRC (configured Rel. 17 TCI state). In this disclosure, the terms configured Rel. 17 TCI state, configured TCI state, configured joint 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0138] (Beam Indication for Multi-TRP) It is assumed that the following two mechanisms (e.g., beam indication method 1 / beam indication method 2) will be supported as beam indication for multi-TRP.

[0139] Beam Indication Method 1: The UE may receive a beam indication (e.g., DCI) and may determine / judge multiple TCI states (corresponding to one or more TRPs) based on the TCI fields included in the beam indication.

[0140] Beam pointing method 1 can be preferably applied in an ideal backhaul environment. Beam pointing method 1 may be preferably applied, for example, in single DCI-based transmission.

[0141] For beam directing method 1, a minimum BAT may be defined in a non-ideal backhaul environment (e.g., multiple DCI-based transmission). Also, for beam directing method 1, an additional BAT corresponding to at least one of the multiple TRPs may be defined in a non-ideal backhaul environment (e.g., multiple DCI-based transmission).

[0142] 5A illustrates an example of beam indication method 1. In FIG. 5A, a UE receives a beam indication. The beam indication may indicate two TCI states (a first TCI state and a second TCI state). The UE determines the first TCI state and the second TCI state based on one or more TCI fields included in the beam indication. The first TCI state may correspond to a first TRP. The second TCI state may correspond to a second TRP.

[0143] [Beam Indication Method 2] The UE may receive multiple (e.g., two) beam indications (e.g., DCIs). The UE may determine / judge one or more TCI states corresponding to each beam indication based on the TCI fields included in the multiple beam indications. For example, the UE may determine a first (DL / UL) TCI state based on the first beam indication and a second (DL / UL) TCI state based on the second beam indication.

[0144] The first beam designation / first TCI state may correspond to the first TRP / first CORESET pool index (e.g., a CORESET pool index of a first value (e.g., 0)) / first CORESET (1st CORESETs). The second beam designation / second TCI state may correspond to the second TRP / second CORESET pool index (e.g., a CORESET pool index of a second value (e.g., 1)) / second CORESET (2nd CORESETs).

[0145] Beam pointing method 2 can be preferably applied in a non-ideal backhaul environment, and may be preferably applied to, for example, multi-DCI-based transmission.

[0146] 5B illustrates an example of beam indication method 2. In FIG. 5B, a UE receives two beam indications. The UE determines a first TCI state based on a TCI field included in one of the two beam indications. The UE determines a second TCI state based on a TCI field included in another of the two beam indications.

[0147] In a multi-DCI-based multi-TRP, when one TCI state is indicated by a MAC CE / DCI, a TCI state (e.g., an indicated TCI state) is indicated for each TRP (or each CORESET pool index).

[0148] For example, the unified TCI state corresponding to the first TRP (or the first CORESET pool index #0) is indicated by the RRC parameters / MAC CE / DCI for the first CORESET pool index #0 (see Fig. 6A), and the unified TCI state corresponding to the second TRP (or the second CORESET pool index #1) is indicated by the RRC parameters / MAC CE / DCI for the second CORESET pool index #1 (see Fig. 6B).

[0149] Thus, in existing systems (e.g., Rel. 17 and earlier), the TCI field included in the DCI associated with one CORESET pool index can indicate a joint / DL / UL TCI state specific to the same CORESET pool index value. The joint / DL / UL TCI state may mean at least one of a joint TCI state (a TCI state that applies to UL and DL), a separate DL TCI state (a TCI state that applies only to DL), and a separate UL TCI state (a TCI state that applies only to UL) in the unified TCI framework.

[0150] If the TCI state field of the DCI associated with the CORESET pool index (={0,1}) indicates one indicated joint / DL / UL TCI state (e.g., indicated joint DL / UL TCI state), the question arises as to how to apply the indicated joint / DL / UL TCI state to each channel / reference signal (RS).

[0151] For example, it is assumed that the indicated joint / DL / UL TCI state associated with the corresponding CORESET pool index (={0, 1}) is applied to the PDCCH. If the indicated joint / DL / UL TCI state is indicated in the TCI field of the DCI transmitted with a certain CORESET pool index, the UE may apply the indicated joint / DL / UL TCI state to the PDCCH transmitted with the same CORESET pool index.

[0152] It is also assumed that for a PDSCH, the indication joint / DL / UL TCI state associated with the PDCCH (or CORESET pool index (={0,1})) that schedules / activates the PDSCH applies.

[0153] For example, a first TCI state (e.g., a first indicated joint TCI state) associated with the first CORESET pool index #0 may be applied to a PDCCH transmitted in a CORESET associated with a first CORESET pool index (=0) (see FIG. 7 ), and a second TCI state (e.g., a second indicated joint TCI state) associated with the second CORESET pool index #1 may be applied to a PDCCH transmitted in a CORESET associated with a second CORESET pool index (=1).

[0154] Also, for a PDSCH scheduled / activated on a PDCCH associated with a first CORESET pool index #0, the indicated joint TCI state associated with the PDCCH (or the first CORESET pool index #0) may be applied. For a PDSCH scheduled / activated on a PDCCH associated with a second CORESET pool index #1, the indicated joint TCI state associated with the PDCCH (or the second CORESET pool index #1) may be applied.

[0155] On the other hand, there has been insufficient consideration as to which TCI state (e.g., indication joint TCI state) should be applied / associated to other channels / RS (e.g., PUSH / PUCCH / SRS / CSI-RS) (see Figure 7).

[0156] In this way, there is insufficient consideration of cases where the UE cannot determine the TCI state to apply. If this consideration is insufficient, the TCI state cannot be applied appropriately, which may lead to a deterioration in communication quality, a decrease in throughput, etc.

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

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

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

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

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

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

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

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

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

[0166] In the present disclosure, the terms panel, receiving panel, UE panel, UE capability value, UE capability value set, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM)), The terms "CDM (Corrective Multiplexing) group," "reference signal group," "CORESET group," "Physical Uplink Control Channel (PUCCH) group," "PUCCH resource group," "resource (e.g., reference signal resource, SRS resource)," "resource set (e.g., reference signal resource set)," "CORESET pool," "downlink Transmission Configuration Indication state (TCI state)" (DL TCI state), "uplink TCI state" (UL TCI state), "unified TCI state," "common TCI state," "indicated TCI state," "Quasi-Co-Location (QCL)," "QCL assumption," and the like may be read interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0186] (Wireless Communication Method) <First Embodiment> In the first embodiment, an example of setting / applying a unified TCI state to a multi-TRP based on a multi-DCI will be described. For example, this method can be suitably applied to a case where a joint TCI state is indicated for each of multiple (e.g., two) CORESET pool indices.

[0187] A TRP identifier (e.g., TRP ID) may be associated with each channel / resource / resource set / reference signal. The association between the TRP ID and each channel / resource / resource set may be configured by higher layer signaling. Alternatively, the association between the TRP ID and each channel / resource / resource set / reference signal may be implicitly established based on a predetermined rule.

[0188] The TRP ID may be a CORESET pool index. The CORESET pool index may be defined as a first CORESET pool index (e.g., index 0) and a second CORESET pool index (e.g., index 1). The number of CORESET pool indices is not limited to two, and three or more CORESET pool indices may be defined / supported.

[0189] For example, the first CORESET pool index #0 may correspond to the first TRP, and the second CORESET pool index #1 may correspond to the second TRP. If two TRPs are supported / configured, the first TRP may be the TRP with the smaller index (e.g., TRP ID = 0). The second TRP may be the TRP with the larger index (e.g., TRP ID = 1).

[0190] For example, assume that the first TCI state #1 corresponds to the first CORESET pool index #0 (or the first TRP #0), and the second TCI state #2 corresponds to the second CORESET pool index #1 (or the first TRP #1) (see Figure 8). In this case, the first TCI state #1 may be indicated by the PDCCH / DCI transmitted by the first CORESET pool index #0, and the second TCI state #1 may be indicated by the PDCCH / DCI transmitted by the second CORESET pool index #1.

[0191] In this case, the first TCI state #1 may be applied to the channel / resource / resource set / reference signal associated with the first CORESET pool index #0 (or the first TRP #0) (see Figure 8). Figure 8 shows the case where the first TCI state #1 is applied to the PUSCH #1 transmitted to the first TRP #0 (or the PUSCH #1 corresponding to the first TRP #0).

[0192] On the other hand, a second TCI state #2 may be applied to the channel / resource / resource set / reference signal associated with the second CORESET pool index #1 (or the second TRP #1).

[0193] The TRP ID may be a predefined ID (e.g., a new ID). Each predefined ID may be associated with a different timing advance (TA). For example, different TAs may be applied to UL transmissions associated with different IDs. Alternatively, UL transmissions associated with different IDs may belong to different timing advance groups (TAGs).

[0194] Similarly, each CORESET pool index may be associated with a different Timing Advance (TA). For example, different TAs may be applied to UL transmissions associated with different CORESET pool indices. Alternatively, UL transmissions associated with different CORESET pool indices may belong to different Timing Advance Groups (TAGs).

[0195] An example of association between a TRP ID (or a CORESET pool index / predetermined ID) and a channel / resource / resource set / reference signal will be described below.

[0196] [Dynamic PUSCH] The TRP ID (or CORESET pool index) associated with the dynamic PUSCH may be determined based on at least one of the following cases:

[0197] Case 1: A TRP ID may be associated with a scheduling PDCCH / search space (or search space set) / CORESET, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0198] For example, if a scheduling PDCCH (or scheduling DCI) for a dynamic PUSCH is associated with TRP ID=0, the PUSCH scheduled by the PDCCH may be associated with TRP ID=0.

[0199] <<Case 2>> The TRP ID may be indicated by a scheduling DCI. For example, the TRP ID may be indicated by a new DCI field or an existing DCI field of the scheduling DCI (e.g., DCI format 0_1 / 0_2).

[0200] Case 3: The TRP ID may be associated with the TCI state indicated for the PUSCH, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0201] Case 4: The TRP ID may be associated with the SRI. Alternatively, the TRP ID may be associated with an SRS resource / SRS resource set indicated for the PUSCH. This association may be configured / activated / indicated by the RRC / MAC CE. Note that the SRS resource / SRS resource set may correspond to an SRS for a specific purpose (e.g., CB / NCB).

[0202] A TRP ID may be configured for each SRS resource set. The SRS resource set may be associated with a usage = CB / NCB. Alternatively, the lowest / highest SRS resource set ID may be implicitly associated with a given TRP ID (e.g., TRP ID = {0, 1}).

[0203] <<Case 5>> The TPC-related parameters for the dynamic PUSCH (e.g., TPC related parameters) may be, for example, a path loss reference signal (e.g., PL-RS), a predetermined parameter (e.g., P0, alpha), or a closed loop index (e.g., close loop index).

[0204] The above-mentioned PDCCH / CORESET / TCI state / SRI / SRS resource / SRS resource set may be configured / activated / specified by RRC / MAC CE / DCI.

[0205] In addition, when multiple TCI states / SRIs / SRS resources / SRS resource sets are specified for a dynamic PUSCH, the TRP ID associated with the dynamic PUSCH may be associated with at least one of the multiple TCI states / SRIs / SRS resources / SRS resource sets. For example, when two TCI states are specified for a dynamic PUSCH, the TRP ID associated with the dynamic PUSCH may be associated with at least one of the first TCI state and the second TCI state.

[0206] The UE determines / selects the joint / UL TCI state to be applied to the dynamic PUSCH based on any of the association rules described above.

[0207] [Configuration Grant PUSCH] The TRP ID (or CORESET pool index) associated with the configuration grant PUSCH may be determined based on at least one of the following cases.

[0208] Case 1: The TRP ID may be associated with a configured grant configuration, and this association may be configured / activated / instructed by the RRC / MAC CE.

[0209] The TRP ID may be configured in higher layer parameters for the configured grant (e.g., ConfiguredGrantConfig), or may be associated with ConfiguredGrantConfigIndex.

[0210] Case 2: For Type 2 configuration grants, the TRP ID may be associated with the PDCCH / search space (or search space set) / CORESET carrying the activating DCI, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0211] <<Case 3>> The TRP ID may be indicated by the activating DCI.

[0212] Case 4: The TRP ID may be associated with the TCI state indicated for the PUSCH, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0213] Case 5: The TRP ID may be associated with the SRI. Alternatively, the TRP ID may be associated with an SRS resource / SRS resource set indicated for the PUSCH. This association may be configured / activated / indicated by the RRC / MAC CE. Note that the SRS resource / SRS resource set may correspond to an SRS for a specific purpose (e.g., CB / NCB).

[0214] A TRP ID may be configured for each SRS resource set. The SRS resource set may be associated with a usage = CB / NCB. Alternatively, the lowest / highest SRS resource set ID may be implicitly associated with a given TRP ID (e.g., TRP ID = {0, 1}).

[0215] Case 6: The TRP ID may be a predefined / fixed value. For example, for a configuration grant, the TRP ID may be fixed to a specific value (e.g., 0). This may mean that only one indicated joint / DL TCI state (e.g., indicated joint / DL TCI state) can be applied to all PUSCHs.

[0216] The above-mentioned configuration grant configuration / PDCCH / CORESET / TCI state / SRI / SRS resource / SRS resource set may be configured / activated / specified by RRC / MAC CE / DCI.

[0217] In addition, when multiple TCI states / SRIs / SRS resources / SRS resource sets are specified for the configured grant PUSH, the TRP ID associated with the configured grant PUSH may be associated with at least one of the multiple TCI states / SRIs / SRS resources / SRS resource sets.

[0218] The UE determines / selects the joint / UL TCI state to be applied to the configured grant PUSCH based on any of the association rules described above.

[0219] [PUCCH] The TRP ID (or CORESET pool index) associated with the PUCCH may be determined based on at least one of the following cases:

[0220] <<Case 1>> If a PUCCH resource / PUCCH transmission is indicated / triggered by a DCI, the TRP ID may be associated with the PDCCH / search space (or search space set) / CORESET that carries the DCI, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0221] Alternatively, the TRP ID may be indicated by the DCI that indicates / triggers the PUCCH resource / PUCCH transmission.

[0222] Case 2: The TRP ID may be associated with a PUCCH resource, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0223] Alternatively, PUCCH resource groups may be configured and different timing advances may be applied to different PUCCH resource groups. Multiple (e.g., two) PCCH resource groups may be configured / associated with two TRPs, respectively.

[0224] Case 3: The TRP ID may be associated with the TCI status or spatial relationship information indicated for the PUCCH, and this association may be configured / activated / indicated by the RRC / MAC CE.

[0225] Case 4: The TRP ID may be associated with UCI transmitted on the PUCCH. For example, the TRP ID may be associated with HARQ (or a PDSCH corresponding to HARQ), SR, or CSI report.

[0226] <<Case 5>> The TPC-related parameters for the dynamic PUCCH may be, for example, a path loss reference signal (for example, PL-RS), a predetermined parameter (for example, P0, alpha), or a closed loop index.

[0227] Case 6: The TRP ID may be a predefined / fixed value. For example, for PUCCH, the TRP ID may be fixed to a specific value (e.g., 0). This may mean that only one indicated joint / DL TCI state (e.g., indicated joint / DL TCI state) can be applied to all PUCCHs.

[0228] The association (correspondence) between PUCCH and TRP ID may be different for each PUCCH format. The association (correspondence) between PUCCH and TRP ID may be different for PUCCHs of different UCI types (in other words, the association between PUCCH and TRP ID may be different between PUCCH for a first UCI type and PUCCH for a second UCI type).

[0229] The UE determines / selects the joint / UL TCI state to be applied to the PUCCH based on any of the association rules described above.

[0230] [SRS] The TRP ID (or CORESET pool index) associated with the SRS may be determined based on at least one of the following cases:

[0231] <<Case 1>> If the SRS is triggered by a DCI (e.g., in the case of aperiodic SRS), the TRP ID may be associated with the PDCCH / search space (or search space set) / CORESET that carries the DCI. This association may be configured / activated / instructed by the RRC / MAC CE.

[0232] Alternatively, the TRP ID may be indicated by the DCI that triggers the SRS.

[0233] Case 2: A TRP ID may be associated with an SRS resource / SRS resource set, and the association may be configured / activated / instructed by the RRC / MAC CE.

[0234] Alternatively, the association between TRP IDs and SRS resources / SRS resource sets may be predefined. For example, for codebook (CB) / non-codebook (NCB) SRS, if two SRS resource sets are configured for two TRPs, the two SRS resource sets may be associated with two TRP IDs, respectively. The first SRS resource set (e.g., the SRS resource set with a lower ID) may be associated with the first TRP #0, and the second SRS resource set (e.g., the SRS resource set with a higher ID) may be associated with the second TRP #1.

[0235] Case 3: The TRP ID may be associated with the TCI status or spatial relationship information indicated for the SRS, and the association may be configured / activated / indicated by the RRC / MAC CE.

[0236] <<Case 4>> The TPC-related parameters for SRS (e.g., TPC related parameters) may be, for example, a path loss reference signal (e.g., PL-RS), a predetermined parameter (e.g., P0, alpha), or a closed loop index (e.g., close loop index).

[0237] Case 5: The TRP ID may be a predefined / fixed value. For example, for SRS, the TRP ID may be fixed to a specific value (e.g., 0). This may mean that only one indicated joint / DL TCI state (e.g., indicated joint / DL TCI state) can be applied to all SRS.

[0238] The association (correspondence) between an SRS and a TRP ID may differ depending on the usage of the SRS resource set corresponding to the SRS. For example, a different TRP ID correspondence may be used for each (or some) of the usages: codebook, non-codebook, beam management, antenna switching, and positioning.

[0239] Furthermore, the association (correspondence) between an SRS and a TRP ID may differ depending on the time domain behavior (e.g., periodic, semi-persistent, aperiodic) of the SRS resource set corresponding to the SRS.

[0240] The UE determines / selects the joint / UL TCI state to be applied to the SRS based on any of the association rules described above.

[0241] [CSI-RS] The TRP ID associated with the CSI-RS may be determined based on at least one of the following cases.

[0242] Case 1: When CSI-RS is triggered by DCI (e.g., A-CSI-RS), the TRP ID may be associated with the PDCCH / CORESET / search space set that carries the DCI. This association may be configured / activated / instructed by the RRC / MAC CE.

[0243] Alternatively, if the CSI-RS is triggered by a DCI (eg, an A-CSI-RS), the TRP ID may be indicated by the DCI.

[0244] Case 2: A TRP ID may be associated with a CSI-RS resource / CSI-RS resource set, and the association may be configured / activated / instructed by the RRC / MAC CE.

[0245] Alternatively, the association between TRP IDs and CSI-RS resources / CSI-RS resource sets may be predefined. A CSI-RS resource ID / CSI-RS resource set ID with a lower / higher ID may be associated with TRP ID #0. Another CSI-RS resource ID / CSI-RS resource set ID may be associated with TRP ID #1.

[0246] Case 3: The TRP ID may be associated with the TCI state or spatial relationship information indicated to the A-CSI-RS, and the association may be configured / activated / indicated by the RRC / MAC CE.

[0247] Case 4: The TRP ID may be predefined / fixed. For example, the TRP ID associated with a CSI-RS may be a specific value (e.g., 0). This may mean that only one indicated joint / DL TCI state (e.g., indicated joint / DL TCI state) may be applied to all CSI-RSs.

[0248] Case 5: The indicated joint / DL TCI state may be applied to a specific CSI-RS, which may be, for example, at least one of an A / SP / P CSI-RS, a CSI-RS with / without repetition, a CSI-RS with / without trs information (trs-info), a CSI-RS for mobility, and a CSI-RS for BM / CSI.

[0249] Different options (or cases) may be applied to the CSI-RS for different purposes (e.g., CSI-RS with / without repetition, CSI-RS with / without trs information (trs-info), CSI-RS for mobility, etc.) Different options (or cases) may be applied to different CSI-RS for different time domain operations (e.g., periodic / semi-persistent / aperiodic).

[0250] The UE determines / selects the joint / UL TCI state to be applied to the CSI-RS based on any of the association rules described above.

[0251] [PDCCH] For PDCCH in multi-DCI based multi-TRP, the UE may apply the indicated joint / DL TCI state specific to the CORESET pool index value to PDCCHs in the CORESET associated with the same CORESET pool index value.

[0252] In this case, the indication joint / DL TCI state may be configured to be applied to all PDCCHs, or may not be configured to be applied to all PDCCHs. For example, the indication joint / DL TCI state may not be applied to some CORESETs (or may be applied only to some CORESETs).

[0253] If a joint / DL TCI state is configured and a CORESET pool index is configured for at least one CORESET, one joint / DL TCI state indication may be supported for each CORESET pool index (={0,1}).

[0254] In this case, at least one of the following rules may be applied to the PDCCH.

[0255] <<Rule 1>> For a specific CORESET (e.g., CORESET #0), if an upper layer parameter (e.g., followUnifiedTCIstate) indicating that the unified TCI state should be followed is set, the indicated TCI state may be applied. Otherwise, the mechanism of the legacy system (e.g., Rel. 15) may be applied to the specific CORESET. The mechanism of the legacy system (e.g., Rel. 15) may, for example, mean that the specific CORESET follows the TCI state activated by the MAC CE, or may be SSB and QCL.

[0256] <<Rule 2>> Alternatively, the indication TCI state may always be applied to a CORESET other than a specific CORESET (e.g., CORESET #0) with USS / CSS type 3.

[0257] Rule 3: Alternatively, if followUnifiedTCIstate is set for a CORESET other than a specific CORESET (e.g., CORESET #0) with at least a CSS other than CSS type 3, the indicated TCI state may be applied. Otherwise, the configured TCI state for that CORESET may be applied to that CORESET.

[0258] Note that rules different from the above rules 1 to 3 may be applied. For example, the same rule as rules 1, 2, and 3 or a different rule may be applied depending on a predetermined condition. The predetermined condition may be any of the following: - Which CORESET it is (for example, whether it is a specific CORESET (CORESET #0)), - Which search space type it is (for example, whether it is CSS or USS, or in the case of CSS, whether it is CSS type 0 / 0A / 1 / 2 / 3), - Whether an upper layer parameter indicating that the unified TCI state is to be followed (for example, followUnifiedTCIstate) is set or not.

[0259] Alternatively, the indication TCI state associated with the corresponding CORESET pool index may be applied to all CORESET / PDCCHs regardless of the setting (e.g., CSS / USS / followUnifiedTCIstate / CORESET#0).

[0260] [PDSCH] If a joint / DL TCI state is configured and a CORESET pool index is configured for at least one CORESET, one joint / DL TCI state indication per CORESET pool index (={0,1}) may be supported.

[0261] In this case, for the PDSCH, the QCL assumption of the PDSCH (or the indicated TCI state applied to the PDSCH) may be controlled based on the relationship between the scheduling offset and a threshold indicating the time duration for the QCL (e.g., timeDurationForQCL).

[0262] If scheduling offset<timeDurationForQCL, regardless of the CORESET (e.g., scheduling CORESET) that schedules the PDSCH, if the indicated TCI state is associated with the serving cell PCI, the indicated TCI state associated with the CORESET pool index may be applied to the scheduled PDSCH. Otherwise (e.g., if the indicated TCI state is not associated with the serving cell PCI), the default QCL rule of the legacy system (e.g., Rel. 16) may be applied. If the default QCL rule is applied, the QCL corresponding to the lowest CORESET ID with the same CORESET pool index in the latest monitoring slot may be applied to the scheduled PDSCH.

[0263] If the scheduling offset ≥ timeDurationForQCL, the QCL assumption of the PDSCH may be the same as the QCL assumption of the scheduling CORESET, which may mean that the QCL assumption depends on the QCL assumption used for the scheduling CORESET.

[0264] [followUnifiedTCIstate] For each channel / signal, the setting / application of a higher layer parameter (eg, followUnifiedTCIstate) indicating that the unified TCI state is to be followed may be extended.

[0265] <<PUSCH>> For PUSCH, the corresponding higher layer parameters (e.g., followUnifiedTCIstate) may not be defined. For example, all / some PUSCHs may follow the indicated joint / UL TCI state.

[0266] Alternatively, the corresponding higher layer parameter (e.g., followUnifiedTCIstate) may be configurable / supported in the PUSCH configuration (e.g., PUSCH-Config) / scheduling CORESET. For example, if the corresponding higher layer parameter is configured, the associated PUSCH may follow the indicated joint / UL TCI state; otherwise, the PUSCH may follow the configured joint / UL TCI state.

[0267] <PUCCH> For PUCCH, the corresponding higher layer parameters (e.g., followUnifiedTCIstate) may not be defined. For example, all / some PUCCHs may follow the indicated joint / UL TCI state.

[0268] Alternatively, the corresponding higher layer parameter (e.g., followUnifiedTCIstate) may be configurable / supported in the PUCCH configuration (e.g., PUCCH-Config) / scheduling CORESET. For example, if the corresponding higher layer parameter is configured, the associated PUCCH may follow the indicated joint / UL TCI state, otherwise the PUSCH may follow the configured joint / UL TCI state.

[0269] <<SRS>> For SRS, the corresponding higher layer parameters (e.g., followUnifiedTCIstate) may not be defined. For example, all / some SRS may follow the indication joint / UL TCI state.

[0270] Alternatively, the corresponding higher layer parameter (e.g., followUnifiedTCIstate) may be configurable / supported in the SRS configuration (e.g., SRS-Config) / triggering CORESET. For example, if the corresponding higher layer parameter is configured, the associated SRS may follow the indicated joint / UL TCI state, otherwise the PUSCH may follow the configured joint / UL TCI state.

[0271] Note that only limited types of SRS (e.g., only some SRS) may follow the joint / UL TCI indication. Some SRS may be SRS used for at least one of codebook, non-codebook, beam management, antenna switching, and positioning. Alternatively, some SRS may be at least one of periodic SRS, semi-persistent SRS, and aperiodic SRS, which have different time-domain behavior.

[0272] <<PDCCH>> For PDCCH, the corresponding higher layer parameter (e.g., followUnifiedTCIstate) may not be defined. For example, all / part of CORESET (or PDCCH corresponding to the CORESET) may follow the indication joint / UL TCI state.

[0273] Alternatively, the higher layer parameter (e.g., followUnifiedTCIstate) may be configurable / supported in a PDCCH configuration (e.g., PDCCH-Config) / CORESET / search space (or search space set). For example, if the higher layer parameter is configured, the associated PDCCH / CORESET / search space (or search space set) may follow the indicated joint / UL TCI state; otherwise, the PDCCH / CORESET / search space (or search space set) may follow the configured joint / UL TCI state.

[0274] In addition, only limited types of PDCCH / CORESET / search spaces (or search space sets) (e.g., only some PDCCH / CORESET / search spaces (or search space sets)) may follow the indication joint / UL TCI state. Some PDCCH / CORESET / search spaces (or search space sets) may be a specific CORESET (e.g., CORESET#0) / CORESET / CSS / USS other than CORESET#0. In the case of CSS, at least one of CSS types 0 / 0A / 1 / 2 / 3 may be selected for some search space sets.

[0275] <<PDSCH>> For PDSCH, the corresponding higher layer parameters (e.g., followUnifiedTCIstate) may not be defined. For example, all / some PDSCHs may follow the indicated joint / UL TCI state.

[0276] Alternatively, the corresponding higher layer parameter (e.g., followUnifiedTCIstate) may be configurable / supported in the PDSCH configuration (e.g., PDSCH-Config) / scheduling CORESET. For example, if the corresponding higher layer parameter is configured, the associated PDSCH may follow the indicated joint / UL TCI state; otherwise, the PDSCH may follow the configured joint / UL TCI state.

[0277] Second Embodiment In a second embodiment, an example of timing advance control in a multi-DCI-based multi-TRP system will be described.

[0278] [TA / TAG] When multiple TRPs are used, the distances between the UE and each TRP may be different. The multiple TRPs may be included in the same cell (e.g., serving cell). Alternatively, one TRP may correspond to the serving cell and the other TRPs may correspond to non-serving cells. In this case, the distances between each TRP and the UE may be different.

[0279] In existing systems, the transmission timing of an uplink (UL) channel and / or an UL signal (UL channel / signal) is adjusted by a timing advance (TA). The reception timing of the UL channel / signal from different user terminals (UE) is adjusted by a radio base station (TRP: Transmission and Reception Point, also referred to as gNodeB: gNB) side.

[0280] The UE may control the timing of UL transmission by applying timing advance (multiple timing advances) for each pre-configured timing advance group (TAG).

[0281] When multiple timing advances are applied, Timing Advance Groups (TAGs) classified by transmission timing are supported. The UE may control the UL transmission timing for each TAG assuming that the same TA offset (or TA value) is applied to each TAG. In other words, the TA offset may be set independently for each TAG.

[0282] When multiple timing advance is applied, the UE independently adjusts the transmission timing of cells belonging to each TAG, so that even when multiple cells are used, the radio base station can synchronize the reception timing of uplink signals from the UE.

[0283] TAGs (e.g., serving cells belonging to the same TAG) may be configured by higher layer parameters. The same timing advance value may be applied to serving cells belonging to the same TAG. The timing advance group including the SpCell of a MAC entity may be called a Primary Timing Advance Group (PTAG), and the other TAGs may be called Secondary Timing Advance Groups (STAGs).

[0284] In existing systems (e.g., Rel. 16 NR), the configuration of up to four TAGs per cell group (e.g., MCG / SCG) is supported (see Figure 9). Figure 9 shows a case where three TAGs are configured for a cell group including SpCell and SCell #1 to #4. Here, the SpCell and SCell #1 belong to the first TAG (PTAG or TAG #0), SCell #2 and SCell #3 belong to the second TAG (TAG #1), and SCell #4 belongs to the third TAG (TAG #2).

[0285] A timing advance command (TA command) may be notified to the UE using a MAC control element (e.g., MAC CE). The TA command indicates a transmission timing value of an uplink channel and is included in the MAC control element. The TA command is signaled from the radio base station to the UE at the MAC layer. The UE controls a predetermined timer (e.g., a TA timer) based on the reception of the TA command.

[0286] The MAC CE for the timing advance command (TAC MAC CE) may include a field for a timing advance group index (for example, TAG ID) and a field for the timing advance command (see FIG. 10).

[0287] In a multi-DCI-based multi-TRP, the association of a TAG with an UL channel / signal may be controlled depending on whether a unified TCI state is configured / applied. For example, when a unified TCI state (e.g., a joint / UL TCI state) is configured, the association of a TAG with an UL channel / signal may be used for both TAG association (e.g., association of a TAG with an UL channel / signal) and association of an indicated joint / UL TCI state (e.g., association of an indicated joint / UL TCI state with an UL channel / signal). Note that the association between a TAG and a TCI state / CORESET pool index may be predefined / configured or configured by the base station to the UE via an RRC parameter.

[0288] For multi-DCI based multi-TRP operation, at least one of the following options 2-1 to 2-4 may be applied to associate a TAG with a target UL channel / signal.

[0289] [Option 2-1] TAGs may be associated with TCI state / spatial relationships.

[0290] For example, the TAG ID may be configured as part of the joint / UL TCI state (or spatial relationship). For UL transmissions, the TAG ID associated with the joint / UL TCI state (or spatial relationship) may be utilized.

[0291] [Option 2-2] A TAG may be associated with a CORESET pool index.

[0292] For a dynamically scheduled / activated PUSCH, the TAG associated with the CORESET pool index of the CORESET carrying the PDCCH that schedules / activates the PUSCH may be applied to the UL transmission (e.g., PUSCH).

[0293] For at least one of the type 1 configuration grant PUSCH, periodic / semi-persistent SRS, and periodic / semi-persistent PUCCH, the CORESET pool index may be configured by an RRC parameter.

[0294] [Option 2-3] A TAG may be associated with an SSB group.

[0295] For UL transmission, the UE may employ a TAG associated with an SSB group. If the path loss reference signal (PL RS) is an SSB, the UE may employ a TAG associated with an SSB group to which the PL RS for UL transmission belongs. If the PL RS is a CSI-RS, the UE may employ a TAG associated with an SSB group to which the QCL source SSB (e.g., QCL source SSB) of the PL RS belongs.

[0296] [Options 2-4] TAG association may be performed as follows: - For dynamically scheduled / activated channels / signals, the TAG associated with the CORESET pool index of the CORESET carrying the scheduled PDCCH is used for UL transmission; - For periodic / semi-persistent UL channels / signals (if not scheduled / activated by DCI), the TAG ID may be configured by RRC parameters.

[0297] In options 2-4, all dynamically scheduled / activated channels / signals may have TAG association based on the CORESET pool index of the scheduling / activating PDCCH.

[0298] In options 2-1 / 2-2 / 2-4, an association between "TAG" and "TCI state or CORESET pool index" is assumed.

[0299] Assume that multiple (e.g., two) timing advances (e.g., TAs) are configured for a multi-DCI-based multi-TRP, and a CORESET pool index is configured.

[0300] In such a case, when a joint / UL TCI state is configured, the association of a TRP ID (or CORESET pool index) with each channel / resource / resource set / reference signal may be used for both the purpose of selecting / determining one indicated joint / UL TCI state for each channel / reference signal and for determining the TA.

[0301] When multiple (e.g., two) timing advances (e.g., TAs) are configured for multi-DCI-based multi-TRP and a CORESET pool index is configured, a different timing advance (TA) may be associated with each TRP ID (or CORESET pool index). For example, different TAs may be applied to UL transmissions (e.g., UL channels / signals) associated with different TRP IDs (or CORESET pool indexes) (see Figure 11). Figure 11 illustrates the case where different TAs are applied to UL transmissions (here, PUSCH #1 and PUSCH #2) corresponding to different TRP IDs (or CORESET pool indexes) or belong to different TAGs.

[0302] Alternatively, in the case where multiple (e.g., two) timing advances (e.g., TA) are configured for a multi-DCI-based multi-TRP and a CORESET pool index is configured, if the joint / UL TCI state is not configured, the association of the TRP ID (or CORESET pool index) with each channel / resource / resource set / reference signal may be used for the purpose of determining the TA only.

[0303] The case where the joint / UL TCI state is set may be interpreted as the case where an upper layer parameter indicating that the unified TCI state is followed (e.g., followUnifiedTCIstate) is set. The case where the joint / UL TCI state is not set may be interpreted as the case where an upper layer parameter indicating that the unified TCI state is followed (e.g., followUnifiedTCIstate) is not set.

[0304] Third Embodiment In a third embodiment, an example of transmission control in simultaneous UL transmission using multiple panels (for example, simultaneous multi-panel UL transmission (SiMPUL) or simultaneous UL transmission from multiple panels (STxMP)) will be described.

[0305] [Simultaneous multi-panel UL transmission (SiMPUL)] In future wireless communication systems (e.g., Rel. 18 and later), simultaneous UL transmission using multiple panels (e.g., simultaneous multi-panel UL transmission (SiMPUL), simultaneous UL transmission from multiple panels (STxMP)) may be supported to one or more Transmission / Reception Points (TRPs) to improve UL throughput / reliability.

[0306] In the present disclosure, simultaneous UL transmission using multiple panels, STxMP, SiMPUL, and UL transmission in the same time domain using multiple panels may be read interchangeably.

[0307] In the present disclosure, the terms panel, receiving panel, UE panel, UE capability value, UE capability value set, panel group, etc. may be read interchangeably.

[0308] <<Single DCI-based Multi-TRP PUSCH>> It is being considered that the STxMP PUSCH for single DCI-based multi-TRP will be transmitted using the following transmission schemes: SDM (Spatial Division Multiplexing) scheme, FDM (Frequency Division Multiplexing)-B scheme, FDM-A scheme, SFN (Single Frequency Network)-based transmission scheme, and SDM repetition scheme.

[0309] The SDM scheme may be a scheme in which different layers / DMRS ports of one PUSCH are precoded separately and transmitted simultaneously from different UE panels.

[0310] The FDM-B scheme may be a scheme in which multiple (two) PUSCHs (transmission opportunities) of the same / different redundancy versions (RVs) of the same transport block (TB) are transmitted from different UE panels in non-overlapping frequency domain resources and the same time domain resources.

[0311] The FDM-A scheme may be a scheme in which different portions of the frequency domain resources of one PUSCH (transmission opportunity) are transmitted from different panels of UEs.

[0312] The SFN-based transmission scheme may be a scheme in which all of the same layers / DMRS ports of one PUSCH are transmitted simultaneously from multiple (two) different UE panels.

[0313] The SDM repetition scheme may be a scheme in which multiple (two) PUSCHs (transmission opportunities) with different RVs of the same TB are transmitted simultaneously from multiple (two) different UE panels.

[0314] <<Multi-DCI-based Multi-TRP PUSCH>> For a multi-DCI-based multi-TRP STxMP PUSCH, multiple (two) PUSCHs may be associated with different TRPs. The different PUSCHs may be transmitted from different UE panels.

[0315] The total number of N PUSCH layers may be 2×N.

[0316] Furthermore, the multiple PUSHs may be at least one of a PUSH scheduled by DCI, a PUSH for configured grant, and a PUSH for message 3 / message A.

[0317] Furthermore, the multiple PUSCHs may be fully / partially overlapping in the time domain, fully / partially overlapping in the frequency domain, or non-overlapping in the frequency domain.

[0318] <<PUCCH for Single DCI-Based Multi-TRP>> It is being considered that the STxMP PUCCH for single DCI-based multi-TRP will be transmitted using the following transmission schemes: FDM-A scheme, FDM-B scheme, and SFN-based transmission scheme.

[0319] The FDM-A scheme may be a scheme in which different frequency domain portions of one PUCCH resource are transmitted from different UE panels.

[0320] The FDM-B scheme may be a scheme in which multiple (two) PUCCHs (transmission opportunities) with the same UCI and the same PUCCH format are FDM-modulated simultaneously from different UE panels.

[0321] The SFN-based transmission scheme may be a scheme in which the same PUCCH / DMRS for PUCCH is transmitted simultaneously from different UE panels.

[0322] For each of the above schemes, the specific PUCCH formats that are supported are considered.

[0323] <<PUCCH for Multi-DCI-Based Multi-TRP>> For STxMP PUCCH for multi-DCI-based multi-TRP, multiple (two) PUCCHs may be associated with different TRPs. The different PUCCHs may be transmitted from different UE panels.

[0324] Furthermore, the multiple PUCCHs may fully / partially overlap in the time domain.

[0325] In multi-DCI-based multi-TRP, simultaneous UL transmission of PUSCH+PUSCH, PUCCH+PUCCH, and PUSCH+PUCCH is supported.

[0326] Multi-DCI based STxMP PUSCH Different DCIs associated with different CORESET pool indices may schedule different PUSCHs in different UE panels, in which case two PUSCHs can be transmitted simultaneously.

[0327] Each PUSCH may be associated with one SRS resource set having a predetermined usage (e.g., usage=CB / NCB). Different SRIs and / or different joint / UL TCI states may be associated with different PUSCHs associated with different CORESET pool indices.

[0328] For TPMI / SRI indication in multi-DCI-based simultaneous UL transmission (e.g., multi-DCI based STxMP PUSCH+PUSCH), multiple (e.g., two) SRS resource sets may be configured for a given purpose (e.g., CB or NCB). In this case, a TRP ID (or a CORESET pool index) may be associated with each SRS resource set.

[0329] For example, among multiple (e.g., two) SRS resource sets having a predetermined use (CB / NCB), a first TRP#0 (or a first CORESET pool index#0) may be associated with an SRS resource set having a lower ID (or a higher ID), while a second TRP#1 (or a second CORESET pool index#1) may be associated with another SRS resource set having a predetermined use (CB / NCB).

[0330] Alternatively, the TRP ID (or CORESET pool index) associated with each SRS resource set may be configured by a higher layer parameter.

[0331] For a PUSCH to which multi-DCI-based simultaneous UL transmission is applied, a multi-DCI-based TCI for multi-TRP may be applied.

[0332] For example, one SRI / TPMI field of each DCI may indicate the SRI / TPMI of the scheduled PUSCH. In this case, up to two SRS resource sets may be configured. Each DCI associated with a CORESET pool index may indicate the SRI / TPMI of the SRI / TPMI set for that CORESET pool index.

[0333] A first SRS resource set (e.g., the SRS resource set with the lower ID (or higher ID)) may be associated with TRP ID #0 (or CORESET pool index #0), and a second SRS resource set (e.g., the SRS resource set with the higher ID (or lower ID)) may be associated with TRP ID #1 (or CORESET pool index #1).

[0334] 12 shows a case where an SRS resource (here, SRS #1) indicated in the SRI field of a first DCI #0 associated with a first CORESET pool index #0 is applied to a PUSCH #0 scheduled by the first DCI #0. Also, a case where an SRS resource (here, SRS #2) indicated in the SRI field of a second DCI #1 associated with a second CORESET pool index #1 is applied to a PUSCH #1 scheduled by the second DCI #1.

[0335] The association between the SRS resource set and the CORESET pool index may be defined in the specification or may be configured in the UE by an RRC parameter. Figure 12 shows a case where the first CORESET pool index #0 is associated with the SRS resource set #0, and the second CORESET pool index #1 is associated with the SRS resource set #1.

[0336] For a PUSCH to which multiple DCI-based simultaneous UL transmission applies, the same joint / UL TCI state may be applied between an SRS resource (e.g., an SRS resource with usage=CB / NCB) and a scheduled PUSCH (e.g., a PUSCH associated with an SRI), allowing the UE to assume the same UL beam between the PUSCH and the indicated SRI.

[0337] If the Joint / UL TCI state is set, at least one of the following Option 3A-1 to Option 3A-2 may apply.

[0338] [Option 3A-1] The indication joint / UL TCI state associated with a CORESET pool index (={0,1}) may be applied to all SRS resources in an SRS resource set (e.g., SRS resource set with usage=CB / NCB) associated with the same CORESET pool index.

[0339] 13 illustrates a case where an indication joint / UL TCI state associated with a first CORESET pool index #0 is applied to multiple SRS resources (e.g., SRS #0, SRS #1) included in an SRS resource set #0 (usage=CB) associated with the first CORESET pool index #0. The indication joint / UL TCI state may be applied to DCI #0, PUSCH #0, SRS #0, and SRS #1.

[0340] 13 also illustrates a case where the indication joint / UL TCI state associated with the second CORESET pool index #1 is applied to multiple SRS resources (e.g., SRS #2, SRS #3) included in the SRS resource set #1 (usage=CB) associated with the second CORESET pool index #1. The indication joint / UL TCI state may be applied to DCI #1, PUSCH #1, SRS #2, and SRS #3.

[0341] In this case, although the scheduling DCI (e.g., DCI format 0_1 / 0_2) cannot control the UL beam by DCI, simple operation is possible because the scheduling DCI, the scheduled PUSH and the associated SRS resources all have the same joint / UL TCI state.

[0342] [Option 3A-2] Multiple indication joint / UL TCI states associated with a CORESET pool index (={0, 1}) may be indicated. One of the multiple indication joint / UL TCI states may be applied to each SRS resource. The correspondence (or mapping) between the SRS resource and the indication joint / UL TCI state may be predefined or configured by a higher layer parameter or the like.

[0343] 14 illustrates a case where multiple (e.g., two) indication joint / UL TCI states for a first CORESET pool index #0 are applied to multiple SRS resources (e.g., SRS #0, SRS #1) included in an SRS resource set #0 (usage=CB) associated with the first CORESET pool index #0. The indication joint / UL TCI state (and the SRS resource) to be applied may be indicated to the UE by an SRI field included in the first DCI #0 used for scheduling PUSCH #0.

[0344] Also, a case is shown in which multiple (e.g., two) indication joint / UL TCI states for a second CORESET pool index #1 are applied to multiple SRS resources (e.g., SRS #2, SRS #3) included in an SRS resource set #1 (usage=CB) associated with the second CORESET pool index #1. The indication joint / UL TCI state (and SRS resource) to be applied may be indicated to the UE by an SRI field included in a second DCI #1 used for scheduling PUSCH #1.

[0345] In this way, by associating different indication joint / UL TCI states with each SRS resource, it becomes possible to flexibly control the indication joint / UL TCI state to be applied.

[0346] In addition, multiple indicated TCI states may be indicated for one or more SRS resources in the same SRS resource set.

[0347] Multi-DCI Based STxMP PUCCH For simultaneous UL transmission for multiple DCIs (e.g., STxMP PUCCH for mDCI), different DCIs associated with different CORESET pool indices may indicate different PUCCH resources with different joint / UL TCI states.

[0348] In Rel. 16, joint ACK / NACK (HARQ-ACK) feedback (mode) and separate ACK / NACK (HARQ-ACK) feedback (mode) are supported.

[0349] Joint ACK / NACK feedback may be configured when single DCI-based multi-TRP is configured or when multiple DCI-based multi-TRP is configured.

[0350] Separate ACK / NACK feedback may be configured when multi-DCI based multi-TRP is configured.

[0351] In joint ACK / NACK feedback, ACK / NACK for PDSCH transmitted from multiple TRPs is transmitted to one TRP using one PUCCH resource (see FIG. 15A).

[0352] In separate ACK / NACK feedback, ACK / NACK for PDSCH transmitted from each TRP is transmitted to that TRP using a certain PUCCH resource, and ACK / NACK for PDSCH transmitted from each other TRP is transmitted to that other TRP using a different PUCCH resource (see Figure 15B).

[0353] In Rel. 17, the indicated TCI state applies to all UE-specific PUCCH resources.

[0354] In this case, for joint ACK / NACK feedback, UE operation using multiple TRPs is possible, but the UE will always transmit PUCCH to one beam / TRP, resulting in reduced resource utilization efficiency.

[0355] In addition, separate ACK / NACK feedback cannot be performed because it is not possible to transmit a certain TRP using one PUCCH resource and transmit another TRP using a different PUCCH resource.

[0356] Therefore, the following describes an example of a method for configuring PUCCH resources when multi-TRP is used and a common TCI state is indicated. The UE may determine the PUCCH resources according to at least one of the following options 3B-1 and 3B-2.

[0357] [Option 3B-1] A PUCCH resource may be determined / selected based on an association between a CORESET pool index and a PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config).

[0358] <<Option 3B-1-1>> A PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be configured for a UE for each CORESET / SRS resource set (usage = CB / NCB). Note that in the following description, the CORESET / SRS resource set (usage = CB / NCB) may be replaced with the TRP / TCI state.

[0359] The UE may determine the PUCCH resource corresponding to the TRP / TCI state based on the configuration for each CORESET / SRS resource set (usage=CB / NCB) and transmit HARQ-ACK.

[0360] 16 is a diagram showing an example of a PUCCH resource configuration method according to aspect 3B-1-1. In the example shown in FIG. 16, a PUCCH resource set corresponding to a first CORESET / SRS resource set (usage = CB / NCB) and a PUCCH resource set corresponding to a second CORESET / SRS resource set (usage = CB / NCB) are configured for a UE.

[0361] A first number (e.g., four) of PUCCH resource sets corresponding to each CORESET / SRS resource set (usage = CB / NCB) may be configurable. A second number (e.g., eight) of PUCCH resources within each PUCCH resource set may be configurable. The UE selects one PUCCH resource set from the configured PUCCH resource sets based on the payload size (number of bits) of the UCI. In the example shown in FIG. 16 , if the number of bits of the UCI is equal to or less than N0 (e.g., 2), the UE determines to use the first PUCCH resource set. Also, in the example shown in FIG. 16 , if the number of bits of the UCI is greater than N0 and equal to or less than N1, the UE determines to use the second PUCCH resource set.

[0362] In the example shown in FIG. 16, the UE determines the PUCCH resource set / PUCCH resource corresponding to the CORESET / SRS resource set (usage=CB / NCB) based on the configuration for each CORESET / SRS resource set (usage=CB / NCB).

[0363] In addition, among the settings for each CORESET / SRS resource set (usage = CB / NCB), the setting of the PUCCH resource set corresponding to the first (or second) CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set specified in existing specifications (for example, Rel. 15-17). Alternatively, among the settings for each CORESET / SRS resource set (usage = CB / NCB), the setting of the PUCCH resource set corresponding to the first (or second) CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set newly specified (for example, in Rel. 18 or later).

[0364] Furthermore, among the settings for each CORESET / SRS resource set (usage = CB / NCB), the setting of the PUCCH resource set corresponding to the second (or first) CORESET / SRS resource set (usage = CB / NCB) may use the setting of a PUCCH resource set that is newly defined (for example, in Rel. 18 or later).

[0365] <<Option 3B-1-2>> A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be configured for each CORESET / SRS resource set (usage=CB / NCB) for the UE.

[0366] One PUCCH resource may be associated with one CORESET / SRS resource set (usage = CB / NCB). The UE may be instructed which PUCCH resource is associated with one CORESET / SRS resource set (usage = CB / NCB). Each PUCCH resource may be independently associated with a CORESET / SRS resource set (usage = CB / NCB).

[0367] For each PUCCH resource, information (flag / indicator) may be set to indicate which of the indicated TCI states the PUCCH resource is associated with, for example, the information may indicate either the first TCI state or the second TCI state.

[0368] If the information is not configured, the UE may determine that the PUCCH resource is associated with a specific TCI state (eg, the first (or second) TCI state).

[0369] The beam indication feature for each PUCCH resource group defined in Rel. 16 may be used to associate a CORESET / SRS resource set (usage = CB / NCB) with a PUCCH resource.

[0370] For example, the UE may determine the association of a CORESET / SRS resource set (usage=CB / NCB) with a PUCCH resource according to the following steps 1 to 3: PUCCH resources of a PUCCH resource group (e.g., PUCCH resource groups 0 to 3) are configured (step 1). Association of a PUCCH resource group with either a first TCI state or a second TCI state is configured (step 2). When one or more (two) TCI states are indicated using the MAC CE / DCI, multiple (e.g., all) PUCCH resources associated with the indicated TCI states are updated (step 3).

[0371] The feature of beam direction for each PUCCH resource group defined in Rel. 16 may not be used.

[0372] In this case, an association between the PUCCH resource and either the first TCI state or the second TCI state may be configured for the UE.

[0373] Figure 17 is a diagram showing an example of a method for configuring PUCCH resources according to Option 3B-1-2. In the example shown in Figure 17, a PUCCH resource set common to each CORESET / SRS resource set (usage = CB / NCB) is configured for the UE. The configuration of the PUCCH resource set and the PUCCH resource is the same as the example shown in Figure 16.

[0374] In the example shown in Figure 17, the UE determines the PUCCH resources corresponding to the CORESET / SRS resource set (usage = CB / NCB) based on the configuration of the PUCCH resource set common to each CORESET / SRS resource set (usage = CB / NCB). In the example shown in Figure 17, among the PUCCH resources included in the PUCCH resource set, PUCCH resources with PUCCH resource indicators (PRI) of "000" to "011" are associated with the first CORESET / SRS resource set (usage = CB / NCB), and PUCCH resources with PRIs of "100" to "111" are associated with the second CORESET / SRS resource set (usage = CB / NCB). The UE determines the PUCCH resources associated with each CORESET / SRS resource set (usage = CB / NCB) based on this association.

[0375] In addition, the setting common to each CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set specified in the existing specifications (for example, Rel. 15-17). Alternatively, the setting common to each CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set newly specified (for example, in Rel. 18 or later).

[0376] According to option 3B-1-2, PUCCH resource selection using PRI / Control Channel Element (CCE) index can be used to indicate joint TCI status / separate (UL) TCI status of the PUCCH resource.

[0377] <<First Modification of Option 3B-1-2>> A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be configured for each CORESET / SRS resource set (usage=CB / NCB) for the UE.

[0378] One PUCCH resource may be associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB). A UE may be indicated which PUCCH resources are associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB).

[0379] For one or more (e.g., some / all) PUCCH resources, information (flag / indicator) indicating which TCI state of the indicated TCI state the PUCCH resource is associated with may be set. For example, the information may indicate either the first TCI state or the second TCI state.

[0380] When one or more (two) TCI states are indicated using MAC CE / DCI, multiple (eg, all) PUCCH resources associated with the indicated TCI states may be updated.

[0381] When multiple (two) TCI states are indicated, the UE may determine that the multiple indicated TCI states apply. This case may apply, for example, to at least one of repeated PUCCH transmission for multiple TRPs (defined in Rel. 17) and simultaneous PUCCH transmission using multiple panels (defined in Rel. 18 and later).

[0382] When multiple (two) TCI states are indicated, the UE may determine to apply one of the indicated TCI states. The determination of the one TCI state may be specified in advance in the specification, configured by RRC, indicated in MAC CE / DCI, or may depend on the UE implementation. This case may also be applied to PUCCH transmissions other than repeated PUCCH transmissions for multiple TRPs (defined in Rel. 17).

[0383] Figure 18 is a diagram showing an example of a method for configuring PUCCH resources according to Variation 1 of Option 3B-1-2. In the example shown in Figure 18, a PUCCH resource set common to each CORESET / SRS resource set (usage = CB / NCB) is configured for the UE. The configuration of the PUCCH resource set and the PUCCH resource is the same as the example shown in Figure 16.

[0384] In the example shown in FIG. 18, the UE determines the PUCCH resource corresponding to the CORESET / SRS resource set (usage=CB / NCB) based on the configuration of the PUCCH resource set common to each CORESET / SRS resource set (usage=CB / NCB).

[0385] In the example shown in Fig. 18, two TCI states are indicated for one or more specific PUCCH resources (PUCCH resource groups). The UE determines that two TCI states apply to one or more specific PUCCH resources (PUCCH resource groups).

[0386] In the example shown in Fig. 18, one or two TCI states are indicated for PUCCH resources other than the one or more specific PUCCH resources (PUCCH resource groups). When two TCI states are indicated for these PUCCH resources, the UE determines to apply one of the TCI states based on a specific rule.

[0387] In addition, the setting common to each CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set specified in the existing specifications (for example, Rel. 15-17). Alternatively, the setting common to each CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set newly specified (for example, in Rel. 18 or later).

[0388] According to variant 1 of option 3B-1-2, RRC / MAC CE / DCI / specific rules can be used to indicate the joint TCI status / separate (UL) TCI status of PUCCH resources.

[0389] Note that a new DCI field may be defined, a (special) combination of DCI fields may be used, or an existing DCI field may be used to indicate one of the two indicated TCI states. For example, an association between an index of the first indicated TCI state, an index of the second indicated TCI state, and a TCI codepoint may be configured in the UE using RRC.

[0390] <<Second Modification of Option 3B-1-2>> A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be configured for each CORESET / SRS resource set (usage=CB / NCB) for the UE.

[0391] One PUCCH resource may be associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB). A UE may be indicated which PUCCH resources are associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB).

[0392] According to variant 2 of option 3B-1-2, RRC / MAC CE / DCI / specific rules can be used to indicate the joint TCI status / separate (UL) TCI status of PUCCH resources.

[0393] An association may be defined between at least one of the DCI code point of the PRI, the PUCCH resource ID, the PUCCH resource group ID, the PUCCH resource set ID, and the TCI code point (first parameters) and the index of the first indicated TCI state and the index of the second indicated TCI state.

[0394] For example, the association may be an association in which a first TCI state is applied to PUCCH resources associated with an even (or odd) first parameter, and the association may be an association in which a second TCI state is applied to PUCCH resources associated with an odd (or even) first parameter.

[0395] Alternatively, the association may be such that the lower half of the PUCCH resources (PRI) per PUCCH resource set is associated with the first TCI state instead of the even (or odd) first parameter, or such that the lower half of the PUCCH resources (PRI) per PUCCH resource set is associated with the second TCI state instead of the odd (or even) first parameter.

[0396] The UE may also determine the TCI state of a PUCCH resource based on the index of the TRP of the scheduled PDSCH / scheduling PDCCH (DCI) in a multi-DCI-based multi-TRP scenario. For example, for a PUCCH resource for a PDSCH scheduled by a PDCCH corresponding to a first value (or a second value), the UE may determine to apply the first (or second) TCI state to the PUCCH resource.

[0397] The UE may not assume / expect that the PRIs from multiple (two) TRPs indicate the same PUCCH resource in the same slot.

[0398] Figure 19 is a diagram showing an example of a method for configuring PUCCH resources according to Variation 2 of Option 3B-1-2. In the example shown in Figure 19, a PUCCH resource set common to each CORESET / SRS resource set (usage = CB / NCB) is configured for the UE. The configuration of the PUCCH resource set and the PUCCH resource is the same as the example shown in Figure 16.

[0399] In the example shown in FIG. 19 , the UE determines the PUCCH resource corresponding to the CORESET / SRS resource set (usage=CB / NCB) based on the configuration of the PUCCH resource set common to each CORESET / SRS resource set (usage=CB / NCB).

[0400] In the example shown in Figure 19, even-numbered PRIs are associated with a first indicated TCI state, and odd-numbered PRIs are associated with a second indicated TCI state. This association may be specified in advance. The UE determines the indicated TCI state to apply to the PUCCH based on this association.

[0401] In addition, the setting common to each CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set specified in the existing specifications (for example, Rel. 15-17). Alternatively, the setting common to each CORESET / SRS resource set (usage = CB / NCB) may use the setting of the PUCCH resource set newly specified (for example, in Rel. 18 or later).

[0402] [Option 3B-2] Different DCIs associated with different CORESET pool indices may indicate different PUCCH resources. In this case, the PUCCH resources may be indicated using a predetermined field included in each DCI. The predetermined field may be a PUCCH resource indication field (e.g., a PRI field).

[0403] In Figure 20, a first PUCCH resource (here, PUCCH resource #0) is specified by the PRI field of a first DCI #0 corresponding to a first CORESET pool index #0. Also, a second PUCCH resource (here, PUCCH resource #1) is specified by the PRI field of a second DCI #1 corresponding to a second CORESET pool index #1.

[0404] If it is supported for the base station to indicate different spatial relationships for different PUCCH resources by RRC / MAC CE, no extension to the specification may be made.

[0405] When Option 3B-2 is applied, the RRC / MAC CE may configure / indicate an association between a CORESET pool index and each PUCCH resource / PUCCH resource group / PUCCH resource set. For example, a CORESET pool index (or a TRP ID) corresponding to each PUCCH resource may be configured in higher layer parameters related to PUCCH configuration (e.g., PUCCHConfig).

[0406] Alternatively, the RRC / MAC CE may configure / indicate the association between the indicated joint / UL TCI state and the PUCCH resource / PUCCH resource group / PUCCH resource set.

[0407] If the DCI associated with the CORESET pool index indicates an indicated joint / UL TCI state, then this indicated joint / UL TCI state may apply to all (or some) PUCCH resources (or all PUCCH resources of a PUCCH resource group) (see Figure 21).

[0408] 21, it is assumed that the first CORESET #0 corresponds to the indicated joint / UL TCI state #1 (first TCI state), and the second CORESET #1 corresponds to the indicated joint / UL TCI state #2 (second TCI state). In this case, the first TCI state #1 may be indicated by the PDCCH / DCI transmitted by the first CORESET pool index #0, and the second TCI state #1 may be indicated by the PDCCH / DCI transmitted by the second CORESET pool index #1.

[0409] Also shown is a case where the association between PUCCH resources and CORESET pool indexes is configured / instructed by RRC / MAC CE, where PUCCH resources #0-#3 are associated with the first CORESET pool index #0, and PUCCH resources #4-#7 are associated with the second CORESET pool index #1.

[0410] The UE may receive information about the association between the CORESET pool index and the PUCCH resource via RRC parameters / MAC CE. When PUCCH resources #0-#3 are indicated, the UE performs PUCCH transmission using the first TCI state #1. When PUCCH resources #4-#7 are indicated, the UE performs PUCCH transmission using the second TCI state #2.

[0411] Note that the DCI corresponding to the first CORESET #0 may indicate any one of PUCCH resources #0 to #3, and the DCI corresponding to the second CORESET #1 may indicate any one of PUCCH resources #4 to #7. Alternatively, the DCI corresponding to the first CORESET #0 may indicate any one of PUCCH resources #0 to #7, and the DCI corresponding to the second CORESET #1 may indicate any one of PUCCH resources #0 to #7.

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

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

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

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

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

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

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

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

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

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

[0422] The specific UE capability may indicate at least one of the following: - Supporting unified TCI in multi-DCI based multi-TRP; - Supporting joint / separate TCI; - Supporting multiple (e.g., two) timing advances; - Supporting simultaneous UL transmission (e.g., STxMP); - The indicated TCI applies to the PDSCH associated with the CORESET having CSS.

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

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

[0425] At least one of the above-described embodiments may also be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer / physical layer signaling, such as information indicating enabling switching between single-TRP and multi-TRP when using unified TCI state, or any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

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

[0427] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1-1] A terminal having a receiver that receives one or more downlink control information (DCI) indicating a unified transmission configuration indicator (TCI) state, and a controller that determines the unified TCI state to apply to at least one of an uplink channel, an uplink reference signal, and a downlink reference signal, based on a transmission / reception point (TRP) index or a control resource set pool index. [Supplementary Note 1-2] The terminal according to Supplementary Note 1-1, wherein the receiver receives information regarding an association between the TRP index or the control resource set pool index and at least one of the uplink channel, the uplink reference signal, and the downlink reference signal. [Supplementary Note 1-3] The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the TRP index or the control resource set pool index corresponds to at least one of a downlink control channel, a control resource set, and a search space set used for transmitting DCI used for scheduling or activating at least one of the uplink channel, the uplink reference signal, and the downlink reference signal. [Supplementary Note 1-4] The terminal according to any of Supplements 1-1 to 1-3, wherein the TRP index or the control resource set pool index is associated with a parameter used for transmitting at least one of the uplink channel, the uplink reference signal, and the downlink reference signal.

[0428] [Supplementary Note 2-1] A terminal comprising: a receiving unit that receives one or more downlink control information (DCI) indicating a unified transmission configuration indicator (TCI) state; and a control unit that applies the unified TCI state to a downlink control channel transmitted on a specific control resource set when the unified TCI state is indicated for each of a plurality of control resource pool indexes used for transmitting the one or more DCIs. [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, wherein the control unit determines the specific control resource set based on at least one of a control resource set index, a corresponding search space type, and whether or not a higher layer parameter related to the application of the unified TCI state is configured. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein the control unit determines the TCI state to apply to the downlink shared channel based on a relationship between a scheduling offset between the DCI and a downlink shared channel scheduled by the DCI, and a time period for quasi-co-location (QCL). [Supplementary Note 2-4] The terminal according to any one of Supplementary Note 2-1 to Supplementary Note 2-3, wherein the control unit applies the unified TCI state to at least one of a downlink control channel, a control resource set, and a search space set associated with the control resource pool index when an upper layer parameter related to the application of the unified TCI state is set.

[0429] [Supplementary Note 3-1] A terminal comprising: a receiving unit that receives one or more downlink control information (DCI) indicating a unified transmission configuration indicator (TCI) state; and a control unit that determines a timing advance of an UL transmission based on a transmission / reception point (TRP) index or a control resource set pool index, wherein different timing advances are applied to UL transmissions associated with different TRP indices or different control resource set pool indices. [Supplementary Note 3-2] The terminal according to Supplementary Note 3-1, wherein, when the unified TCI state is configured or supported, the control unit determines the timing advance of the UL transmission and the unified TCI state to be applied to the UL transmission based on the TRP index or the control resource pool index. [Supplementary Note 3-3] The terminal according to Supplementary Note 3-1 or Supplementary Note 3-2, wherein an association between a timing advance group corresponding to each UL transmission and the unified TCI state or the control resource pool index is defined or configured.

[0430] [Supplementary Note 4-1] A terminal comprising: a transmitter unit configured to simultaneously transmit a first UL channel scheduled by first downlink control information (DCI) corresponding to a first control resource pool index and a second UL channel scheduled by a second DCI corresponding to a second control resource pool index, and a controller configured to determine a sounding reference signal (SRS) resource associated with the first UL channel by the first DCI and to determine a sounding reference signal (SRS) resource associated with the second UL channel by the second DCI. [Supplementary Note 4-2] The terminal according to Supplementary Note 4-1, wherein an association between a transmission / reception point (TRP) index corresponding to the first control resource pool index or the first DCI and an SRS resource set is predefined or configured. [Supplementary Note 4-3] The terminal according to Supplementary Note 4-1 or Supplementary Note 4-2, wherein the controller applies a unified transmission configuration indicator (TCI) state associated with the first control resource set pool index to a plurality of SRS resources included in an SRS resource set associated with the first control resource set pool index. [Supplementary Note 4-4] The control unit applies a plurality of unified transmission configuration indicator (TCI) states associated with the first control resource set pool index to a plurality of SRS resources included in an SRS resource set. The terminal according to any one of Supplementary Note 4-1 to Supplementary Note 4-3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0475] The transceiver 120 may transmit one or more downlink control information (DCI) indicating a unified transmission configuration indicator (TCI) state. The controller 110 may control the unified TCI state applied to at least one of an uplink channel, an uplink reference signal, and a downlink reference signal based on a transmission / reception point (TRP) index or a control resource set pool index.

[0476] The control unit 110 may apply the unified TCI state to the downlink control channel transmitted on a specific control resource set when the unified TCI state is indicated for each of multiple control resource pool indexes used to transmit one or more DCIs.

[0477] The controller 110 may determine the timing advance of the UL transmission based on a transmission / reception point (TRP) index or a control resource set pool index, and different timing advances may be applied to UL transmissions associated with different TRP indices or different control resource set pool indices.

[0478] The transceiver 120 may receive a first UL channel scheduled by first downlink control information (DCI) corresponding to a first control resource pool index and a second UL channel scheduled by a second DCI corresponding to a second control resource pool index, both of which are simultaneously transmitted from the terminal. The controller 110 may indicate a sounding reference signal (SRS) resource associated with the first UL channel by the first DCI and indicate a sounding reference signal (SRS) resource associated with the second UL channel by the second DCI.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0496] The transceiver 220 may receive one or more downlink control information (DCI) indicating a unified transmission configuration indicator (TCI) state. The transceiver 220 may receive information regarding an association between a TRP index or the control resource set pool index and at least one of the uplink channel, the uplink reference signal, and the downlink reference signal. The controller 210 may determine a unified TCI state to apply to at least one of the uplink channel, the uplink reference signal, and the downlink reference signal based on the transmission / reception point (TRP) index or the control resource set pool index.

[0497] The TRP index or the control resource set pool index may correspond to at least one of a downlink control channel, a control resource set, and a search space set used for transmitting DCI used for scheduling or activating at least one of the uplink channel, the uplink reference signal, and the downlink reference signal. The TRP index or the control resource set pool index may be associated with parameters used for transmitting at least one of the uplink channel, the uplink reference signal, and the downlink reference signal.

[0498] When the unified TCI state is indicated for each of a plurality of control resource pool indexes used to transmit one or more DCIs, the control unit 210 may apply the unified TCI state to downlink control channels transmitted on a specific control resource set. The control unit 210 may determine the specific control resource set based on at least one of a control resource set index, a corresponding search space type, and whether or not higher layer parameters related to the application of the unified TCI state are configured. The control unit 210 may determine the TCI state to apply to the downlink shared channel based on a relationship between a scheduling offset between a DCI and a downlink shared channel scheduled by the DCI, and a time period for quasi-co-location (QCL). When higher layer parameters related to the application of the unified TCI state are configured, the control unit 210 may apply the unified TCI state to at least one of the downlink control channel, the control resource set, and the search space set associated with the control resource pool index.

[0499] The controller 210 may determine a timing advance of an UL transmission based on a transmission / reception point (TRP) index or a control resource set pool index. Different timing advances may be applied to UL transmissions associated with different TRP indices or different control resource set pool indices. If a unified TCI state is configured or supported, the controller 210 may determine the timing advance of the UL transmission and the unified TCI state to be applied to the UL transmission based on the TRP index or the control resource pool index. An association between a timing advance group corresponding to each UL transmission and the unified TCI state or the control resource pool index may be defined or configured.

[0500] The transceiver 220 may be permitted / supported to simultaneously transmit a first UL channel scheduled by a first downlink control information (DCI) corresponding to a first control resource pool index and a second UL channel scheduled by a second DCI corresponding to a second control resource pool index. The controller 210 may determine a sounding reference signal (SRS) resource associated with the first UL channel by the first DCI, and may determine a sounding reference signal (SRS) resource associated with the second UL channel by the second DCI.

[0501] An association between a first control resource pool index or a transmission / reception point (TRP) index corresponding to the first DCI and an SRS resource set may be predefined or configured.

[0502] The controller 210 may apply a unified transmission configuration indicator (TCI) state associated with a first control resource set pool index to a plurality of SRS resources included in an SRS resource set associated with the first control resource set pool index. The controller 210 may apply a plurality of unified transmission configuration indicator (TCI) states associated with the first control resource set pool index to a plurality of SRS resources included in the SRS resource set, respectively.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0549] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A receiver that receives a first radio resource control (RRC) parameter indicating an association between a first control resource set (CORESET) pool index and a first sounding reference signal (SRS) resource set, and a second RRC parameter indicating an association between a second CORESET pool index and a second SRS resource set; a controller that applies a first indicated transmission configuration indication (TCI) state associated with the first CORESET pool index to all SRS resources in the first SRS resource set and applies a second indicated TCI state associated with the second CORESET pool index to all SRS resources in the second SRS resource set; A terminal having a transmitter that simultaneously transmits a first physical uplink shared channel (PUSCH) scheduled by first downlink control information (DCI) corresponding to the first CORESET pool index and a second PUSCH scheduled by a second DCI corresponding to the second CORESET pool index.

2. A method of receiving a first radio resource control (RRC) parameter indicating an association of a first control resource set (CORESET) pool index with a first sounding reference signal (SRS) resource set, and a second RRC parameter indicating an association of a second CORESET pool index with a second SRS resource set; applying a first indicated transmission configuration indication (TCI) state associated with the first CORESET pool index to all SRS resources in the first SRS resource set and applying a second indicated TCI state associated with the second CORESET pool index to all SRS resources in the second SRS resource set; and simultaneously transmitting a first physical uplink shared channel (PUSCH) scheduled by first downlink control information (DCI) corresponding to the first CORESET pool index and a second PUSCH scheduled by a second DCI corresponding to the second CORESET pool index.

3. A transmitter that transmits a first radio resource control (RRC) parameter indicating an association between a first control resource set (CORESET) pool index and a first sounding reference signal (SRS) resource set, and a second RRC parameter indicating an association between a second CORESET pool index and a second SRS resource set; a controller that applies a first indicated transmission configuration indication (TCI) state associated with the first CORESET pool index to all SRS resources in the first SRS resource set and applies a second indicated TCI state associated with the second CORESET pool index to all SRS resources in the second SRS resource set; A base station having a receiving unit that receives a physical uplink shared channel (PUSCH) scheduled by first downlink control information (DCI) corresponding to the first CORESET index and a second PUSCH scheduled by a second DCI corresponding to the second CORESET pool index, which are simultaneously transmitted from a terminal.

4. A system having a terminal and a base station, The terminal a receiving unit that receives a first radio resource control (RRC) parameter indicating an association between a first control resource set (CORESET) pool index and a first sounding reference signal (SRS) resource set, and a second RRC parameter indicating an association between a second CORESET pool index and a second SRS resource set; a controller that applies a first indicated transmission configuration indication (TCI) state associated with the first CORESET pool index to all SRS resources in the first SRS resource set and applies a second indicated TCI state associated with the second CORESET pool index to all SRS resources in the second SRS resource set; a transmitter configured to simultaneously transmit a first physical uplink shared channel (PUSCH) scheduled by first downlink control information (DCI) corresponding to the first CORESET pool index and a second PUSCH scheduled by a second DCI corresponding to the second CORESET pool index; The base station A system comprising a transmitter that transmits the first RRC parameters and the second RRC parameters.