Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one aspect of the present disclosure includes: a reception unit that receives information indicating a unified transmission configuration index (TCI) state and one piece of downlink control information indicating a plurality of UL transmissions; and a control unit that determines a unified TCI state to apply to the plurality of UL transmissions on the basis of at least one of: the information indicated by the downlink control information; a transmission-reception point (TRP) index corresponding to the UL transmissions; and a control resource set pool index corresponding to the UL transmissions.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

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

[0006] The application of the configured / activated / instructed Transmission Configuration Indication state (TCI state) to multiple types of signals (channel / RS) is being considered. However, there are cases where the method for applying the TCI state is unclear. If the method for instructing the TCI state is unclear, it may lead to a decrease in communication quality, throughput, and other problems.

[0007] Therefore, this disclosure provides a terminal and wireless communication method that can appropriately control communication even when multiple types of signals (channels / RS) are supported, such as when a Transmit Setting Instruction (TCI) state is applied to multiple types of signals (channels / RS). 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0008] A terminal according to one aspect of this disclosure includes: a receiving unit that receives downlink control information (DCI) including a field that indicates one or both of a first measurement reference signal (SRS) resource set and a second SRS resource set, corresponding to a first transmission setting instruction (TCI) state and a second TCI state, respectively; and a control unit that determines, based on the field, whether to apply the first TCI state, the second TCI state, or both the first and second TCI states to uplink (UL) transmission. Furthermore, when both the first TCI state and the second TCI state are applied, the UL transmission is a simultaneous UL transmission using multiple panels. . [Effects of the Invention]

[0009] According to one aspect of this disclosure, communication can be properly controlled even when multiple types of signals (channels / RS) are supported as transmit setting instruction states (TCI states). [Brief explanation of the drawing]

[0010] [Figure 1] Figures 1A and 1B show an example of a unified / common TCI framework. [Figure 2] Figures 2A and 2B show an example of a DCI-based TCI status indicator. [Figure 3] Figure 3 shows an example of the application time for the Unified TCI status indicator. [Figure 4] Figures 4A-4D show an example of a multi-TRP. [Figure 5] Figures 5A and 5B show an example of a beam direction method for a multi-TRP. [Figure 6] Figures 6A and 6B show an example of a unified / common TCI framework when a CORESET pool index is configured. [Figure 7] Figure 7 illustrates an example of the challenges in applying a unified / common TCI framework to UL channels / signals or DL ​​reference signals when a CORESET pool index is configured. [Figure 8] Figure 8 shows an example of a method for determining the unified / common TCI state in single DCI-based UL transmission according to the first embodiment. [Figure 9] Figure 9 shows an example of the correspondence between SRS resources (sets) and TCI states according to the first embodiment. [Figure 10] Figure 10 shows another example of the correspondence between SRS resources (sets) and TCI states according to the first embodiment. [Figure 11]FIG. 11 is a diagram showing another example of the correspondence between the SRS resource (set) according to the first embodiment and the TCI state. [Figure 12] FIG. 12 is a diagram showing an example of a method for determining a unified / common TCI state when a CORESET pool index according to the second embodiment is set. [Figure 13] FIG. 13 is a diagram showing an example of a timing advance group (TAG) to which a cell included in a cell group belongs. [Figure 14] FIG. 14 is a diagram showing an example of a MAC CE for a timing advance command. [Figure 15] FIG. 15 is a diagram showing an example of a method for determining a unified / common TCI state and a TAG when a CORESET pool index according to the third embodiment is set. [Figure 16] FIG. 16 is a diagram showing an example of a method for determining an SRS resource in UL transmission (for example, PUSCH transmission) according to the fourth embodiment. [Figure 17] FIG. 17 is a diagram showing another example of a method for determining an SRS resource in UL transmission (for example, PUSCH transmission) according to the fourth embodiment. [Figure 18] FIG. 18 is a diagram showing another example of a method for determining an SRS resource in UL transmission (for example, PUSCH transmission) according to the fourth embodiment. [Figure 19] FIGS. 19A and 19B are diagrams showing examples of joint ACK / NACK feedback and separate ACK / NACK feedback, respectively. [Figure 20] FIG. 20 is a diagram showing an example of a method for setting a PUCCH resource according to the fourth embodiment. [Figure 21] FIG. 21 is a diagram showing another example of a method for setting a PUCCH resource according to the fourth embodiment. [Figure 22] FIG. 22 is a diagram showing another example of a method for setting a PUCCH resource according to the fourth embodiment. [Figure 23]Figure 23 shows another example of how to configure the PUCCH resource according to the fourth embodiment. [Figure 24] Figure 24 shows another example of how to configure the PUCCH resource according to the fourth embodiment. [Figure 25] Figure 25 shows another example of how to configure the PUCCH resource according to the fourth embodiment. [Figure 26] Figure 26 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 27] Figure 27 shows an example of the configuration of a base station according to one embodiment. [Figure 28] Figure 28 shows an example of the configuration of a user terminal according to one embodiment. [Figure 29] Figure 29 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Figure 30] Figure 30 shows an example of a vehicle according to one embodiment. [Modes for carrying out the invention]

[0011] (TCI, spatial relations, QCL) In NR, it is being considered to control the receive processing (e.g., at least one of receive, demapping, demodulation, and decoding) and transmit processing (e.g., transmit, mapping, precoding, modulation, and encoding) of at least one of the signal and channel (referred to as signal / channel) at the UE based on the Transmission Configuration Indication state (TCI state).

[0012] The TCI state may represent the one applied to the downlink signal / channel. The equivalent of the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0029] (Default TCI state / Default spatial relationship / Default PL-RS) In Rel.16, a PDSCH may be scheduled in a DCI having a TCI field. The TCI state for the PDSCH is indicated by the TCI field. The TCI field in DCI format 1_1 is 3 bits, and the TCI field in DCI format 1_2 is up to 3 bits.

[0030] In RRC connection mode, if the first DCI-based TCI information element (upper layer parameter tci-PresentInDCI) is set to "enabled" for a CORESET scheduling a PDSCH, the UE assumes that a TCI field exists in the DCI format 1_1 of the PDCCH sent by that CORESET.

[0031] Furthermore, if a second DCI-based TCI information element (upper layer parameter tci-PresentInDCI-1-2) is set in the UE for a CORESET that schedules a PDSCH, the UE assumes that the DCI format 1_2 of the PDSCH sent in that CORESET contains a TCI field with the DCI field size indicated by the second DCI-based TCI information element.

[0032] Furthermore, in Rel.16, a PDSCH may be scheduled with a DCI that does not have a TCI field. The DCI format of such DCI may be DCI format 1_0, or DCI format 1_1 / 1_2 in the case where the TCI information element within the DCI (upper layer parameter tci-PresentInDCI or tci-PresentInDCI-1-2) is not set (enabled). If a PDSCH is scheduled with a DCI that does not have a TCI field, and 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 that DCI) is greater than or equal to 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 the CORESET (e.g., the scheduling DCI).

[0033] In RRC connection mode, both when the DCI-internal TCI information elements (upper layer parameters tci-PresentInDCI and tci-PresentInDCI-1-2) are set to "enabled" and when the DCI-internal TCI information elements are not set, if the time offset between the reception of the DL DCI (the DCI that schedules the PDSCH) and the corresponding PDSCH (the PDSCH scheduled by that DCI) is less than the threshold (timeDurationForQCL) (applicable condition, condition 1), then, 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 within the active DL BWP of its CC (for a specific 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 within the active DL BWP of the scheduled CC.

[0034] In Rel.15, separate MAC CEs are required for the activation / deactivation of PUCCH spatial relations and for the activation / deactivation of SRS spatial relations. PUCCH spatial relations follow SRS spatial relations.

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

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

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

[0038] In Rel.15, the spatial relationships of PUCCH scheduled by DCI format 0_0 follow the spatial relationships of the PUCCH resource with the lowest PUCCH resource ID among the active spatial relationships of PUCCH on the same CC. The network must update the PUCCH spatial relationships on all SCells, even if no PUCCH is sent on a SCell.

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

[0040] The application conditions for default spatial relationships / default PL-RS for SRS may include the setting of the default beam path loss enablement information element for SRS (upper layer parameter enableDefaultBeamPlForSRS). The application conditions for default spatial relationships / default PL-RS for PUCCH may include the setting of the default beam path loss enablement information element for PUCCH (upper layer parameter enableDefaultBeamPlForPUCCH). The application conditions for default spatial relationships / default PL-RS for PUSCH scheduled by DCI format 0_0 may include the setting of the default beam path loss enablement information element for PUSCH scheduled by DCI format 0_0 (upper layer parameter enableDefaultBeamPlForPUSCH0_0).

[0041] In Rel.16, if RRC parameters (a parameter to enable the default beam PL for PUCCH (enableDefaultBeamPL-ForPUCCH), a parameter to enable the default beam PL for PUSCH (enableDefaultBeamPL-ForPUSCH0_0), or a parameter to enable the default beam PL for SRS (enableDefaultBeamPL-ForSRS)) are set for the UE, and no spatial relationship or PL-RS is set, the UE will apply the default spatial relationship / PL-RS.

[0042] The above threshold may also be called the 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. The above threshold may be reported by the UE as UE capability (per subcarrier interval).

[0043] If the offset (scheduling offset) between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and at least one TCI state set for the serving cell of the scheduled PDSCH includes "QCL type D", and the UE has enabled two default TCI states (enableTwoDefaultTCIStates-r16), and at least one TCI code point (code point of the TCI field in the DL DCI) indicates two TCI states, then the UE assumes that the DMRS port of the serving cell's PDSCH or PDSCH transmission occasion is quasi co-located with respect to the RS and QCL parameters associated with the two TCI states corresponding to the lowest code point of the TCI code point containing two different TCI states (two default QCL assumption determination rule). The two default TCI states-enable-r16 behavior for two default TCI states for PDSCH is enabled when at least one TCI code point maps to two TCI states.

[0044] In Rel.15 / 16, the following default TCI states for PDSCH are specified: a default TCI state for single TRPs, a default TCI state for multi-TRPs based on multi-DCIs, and a default TCI state for multi-TRPs based on single-DCIs.

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

[0046] Rel.15 / 16 specifies the default spatial relationships and default PL-RS for PUSCH / PUCCH / SRS, respectively.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0060] It is assumed that N=M=1 will be supported in Rel.17. For example, it may be supported that RRC / MAC CE / DCI designate a single common beam (e.g., common beam), and that single common beam may be applied to the channel / reference signals of multiple DL / ULs.

[0061] Figures 1A and 1B show an example of a unified TCI framework. Figure 1A shows an example of a joint DL / UL TCI state (e.g., Joint DL / UL TCI state), and Figure 1B shows an example of a separate TCI state (e.g., Separate TCI (DL TCI state and UL TCI state)).

[0062] In the example in Figure 1A, the RRC parameter (information element) sets up multiple TCI states for both DL and UL. In this disclosure, the TCI states set up by the RRC parameter may be referred to as configured TCI states or configured TCI states. The MAC CE may activate multiple TCI states from among 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 an indicated TCI state or indicated TCI state.

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

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

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

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

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

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

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

[0070] The method for setting / instructing the TCI state (e.g., joint DL / UL TCI state) in Figure 1A and the method for setting / instructing the application of the TCI state (e.g., separate TCI state) in Figure 1B may be switched between. Whether the joint DL / UL TCI state or the separate TCI state is applied may be set from the base station to the UE by higher-layer parameters.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084] With respect to the Rel.17 TCI state, any TCI state other than the unified TCI state may mean a Rel.17 TCI state configured using MAC CE / RRC (configured Rel.17 TCI state). In this disclosure, 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.17TCI state does not have to be shared with at least one of the following: UE-specific reception in PDSCH / PDCC (updated using Rel.17 DCI / MAC CE / RRC), dynamic grant (DCI) / configured grant PUSCH, and multiple (e.g., all) dedicated PUCCH resources. The configured Rel.17TCI state may be configured in RRC / MAC CE per CORESET / per resource / per resource set, and the configured Rel.17TCI state may not be updated even if the above-mentioned directive Rel.17TCI state (common TCI state) is updated.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0119] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmissions to the UE. Furthermore, it is being considered that the UE will perform UL transmissions to one or more TRPs.

[0120] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID (e.g., PCI) or a virtual cell ID.

[0121] Figures 4A-4D illustrate examples of multi-TRP scenarios. In these examples, it is assumed, but not limited to, that each TRP can transmit four different beams.

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

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

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

[0125] Figure 4C shows an example of a case where each of the multi-TRPs transmits a portion of the control signal to the UE, and the multi-TRP transmits the data signal (this may be called master-slave mode). Part 1 of the control signal (DCI) may be transmitted by TRP1, and part 2 of the control signal (DCI) may be transmitted by 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] Figure 4D shows an example of a multi-TRP where each of the multi-TRPs transmits a separate control signal to the UE, and the multi-TRP transmits data signals (this may also be called multi-master mode). TRP1 may transmit a first control signal (DCI), and TRP2 may transmit a second control signal (DCI). The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0127] When scheduling multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) as shown in Figure 4B using a single DCI, that DCI may be called a single DCI (S-DCI, single PDCCH). Similarly, when scheduling multiple PDSCHs from a multi-TRP (as shown in Figure 4D) using multiple DCIs, these multiple DCIs may be called multiple DCIs (M-DCI, multi-PDCCH (multiple PDCCH)).

[0128] Each TRP in a multi-TRP system may transmit different transport blocks (TBs), code words (CWs), and layers. Alternatively, each TRP in a multi-TRP system may transmit the same TB, CW, and layer.

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

[0130] Furthermore, multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

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

[0132] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition spanning multiple TRPs is being considered. Support for repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) spanning multiple TRPs on the frequency domain, layer (spatial) domain, or time domain is being considered. In scheme 1, multiple PDSCHs from multiple TRPs are performed using space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are performed using frequency division multiplexing (FDM). In scheme 2a, the redundant version (RV) is the same for multiple TRPs. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are performed using time division multiplexing (TDM). In Scheme 3, multi-PDSCH signals from multi-TRPs are transmitted within a single slot. In Scheme 4, multi-PDSCH signals from multi-TRPs are transmitted within different slots.

[0133] Such multi-TRP scenarios allow for more flexible transmission control using high-quality channels.

[0134] NCJT using multiple TRPs / panels may utilize high ranks. To support ideal and non-ideal backhauls between multiple TRPs, both single DCI (single PDCCH, e.g., Figure 4B) and multi-DCI (multi-PDCCH, e.g., Figure 4D) may be supported. For both single and multi-DCI, the maximum number of TRPs may be 2.

[0135] An extension of the TCI is being considered for single PDCCH designs (primarily for ideal backhaul). Each TCI code point within 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 as defined in Rel.15, one TCI state without a CORESET Pool Index (CORESETPoolIndex) (also known as TRP Info) is set for one CORESET.

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

[0138] (Beam direction for multi-TRP) For beam designation of multi-TRPs, the following two mechanisms (e.g., beam designation method 1 / beam designation method 2) are expected to be supported.

[0139] [Beam direction method 1] The UE may receive a single beam indication (e.g., DCI). Based on the TCI field contained in that single beam indication, the UE may determine / decide on multiple TCI states (corresponding to one or more TRPs).

[0140] Beam designation method 1 is suitably applicable in an ideal backhaul environment. Beam designation method 1 may also be suitably applied, for example, in single DCI-based transmission.

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

[0142] Figure 5A shows an example of beam designation method 1. In Figure 5A, the UE receives one beam designation. This beam designation 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 contained in the beam designation. The first TCI state may correspond to a first TRP. The second TCI state may correspond to a second TRP.

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

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

[0145] Beam designation method 2 is suitably applicable in non-ideal backhaul environments. Beam designation method 2 may be suitably applied, for example, in multi-DCI based transmissions.

[0146] Figure 5B shows an example of beam designation method 2. In Figure 5B, the UE receives two beam designations. The UE determines a first TCI state based on the TCI field contained in one of the two beam designations. The UE determines a second TCI state based on the TCI field contained in the other beam designation.

[0147] In a multi-DCI-based multi-TRP, if MAC CE / DCI indicates one TCI state, then each TRP (or each CORESET pool index) will have its own TCI state (e.g., indicated TCI state).

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

[0149] Thus, in existing systems (e.g., Rel.17 and earlier), a TCI field included in a DCI associated with a single CORESET pool index can indicate a joint / DL / UL TCI state specific to the same CORESET pool index value. In the unified TCI framework, a joint / DL / UL TCI state may mean at least one of the following: 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), or a separate UL TCI state (a TCI state that applies only to UL).

[0150] When single DCI-based multi-TRP is supported / applied, if one instruction (e.g., single DCI) indicates one or more (e.g., two) indicated joint DL / UL TCI states, the question arises as to how to apply those indicated joint DL / UL TCI states to each channel / reference signal (RS) (see Figure 7).

[0151] Figure 7 shows a case where a beam indicator #1 (e.g., the TCI state field of the DCI) indicates a first indicated TCI state and a second indicated TCI state. In this case, the first TCI state may be applied to the first PDSCH (e.g., corresponding to the first TRP), and the second TCI state may be applied to the second PDSCH (e.g., corresponding to the second TRP).

[0152] On the other hand, sufficient consideration has not been given to which TCI states (e.g., indicated joint TCI states) should be applied to / associated with other channels / RS (e.g., PUSCH / PUCCH / SRS / CSI-RS) (see Figure 7).

[0153] Thus, the cases in which the UE cannot determine which TCI state to apply have not been adequately considered. If this consideration is insufficient, the TCI state may not be applied appropriately, potentially leading to a decrease in communication quality, throughput, and other problems.

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

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

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

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

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

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

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

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

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

[0163] In this disclosure, the terms panel, receiving panel, UE panel, UE capability value, UE capability value set, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group, resources (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, etc., may be interpreted interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0183] (Wireless communication method) This embodiment may be applied to a single DCI-based multi-TRP. A single DCI-based multi-TRP may refer to an operation in which multiple channels / signals are scheduled / triggered / activated by a single DCI (e.g., a single DCI).

[0184] For example, a single DCI-based multi-TRP may include at least one of the following: a push repetition scheduled by a single DCI (e.g., S-DCI M-TRP push repetition), a pucch repetition scheduled / triggered by a single DCI (e.g., S-DCI M-TRP pucch repetition), or a simultaneous UL transmission using multiple panels based on a single DCI (e.g., S-DCI M-TRP STxMP). Alternatively, a single DCI-based multi-TRP may include PDSCH / PUSCH / PUCCH / SRS / CSI-RS scheduled / triggered / activated by a single DCI.

[0185] In a single DCI-based multi-TRP configuration, a TRP ID may be defined / notified. The TRP ID (e.g., TRP ID={0,1}) may be read as or associated with, for example, the TCI status (e.g., {1st TCI,2nd TCI}) and the control resource set pool index (e.g., CORESETPoolIndex={0,1}). For example, information regarding the TRP identifier may be explicitly set / instructed from the base station to the UE via RRC / MAC CE / DCI.

[0186] Alternatively, the TRP ID may be associated with an implicit ID. For example, for PUSCH, an SRS resource set (e.g., 1st / 2nd SRS resource set) may be associated with the TRP.

[0187] For each TRP, one or more (e.g., two) indicator TCI states may be announced depending on the channel / signal. For a particular channel / signal, only one indicator TCI state may be announced.

[0188] Furthermore, this embodiment is not limited to single-DCI-based multi-TRPs, but may also be applied to multi-DCI-based multi-TRPs.

[0189] <Embodiment 0> In the first embodiment, an example of notification of a unified TCI status for a single DCI-based multi-TRP is described.

[0190] In a single DCI-based multi-TRP configuration, an explicit TRP ID may be set / indicated for each channel / RS. Alternatively, an implicit TRP ID may be set / indicated for each channel / RS. Each channel / RS may be interpreted as at least one of PUSCH, PUCCH, SRS, CSI-RS, PDSCH, or PDCCH.

[0191] For example, a single DCI-based multi-TRP might use a TRP ID, while a multi-DCI-based multi-TRP might use a CORESET pool index. Alternatively, the CORESET pool index might be associated with a TRP ID. In this case, the CORESET pool index might be applied to both single-DCI-based and multi-DCI-based multi-TRPs.

[0192] The UE may apply an indicated TCI state (e.g., indicated TCI) to all channels / RS if one indicated TCI state is indicated by RRC / MAC CE / DCI. One indicated TCI state may mean one indicated joint / UL TCI state or one indicated joint / DL TCI state.

[0193] If multiple (e.g., two) indicated TCI states are indicated by RRC / MAC CE / DCI, the UE may apply one or both of the two indicated TCI states depending on the TRP ID corresponding to each channel / RS.

[0194] <First Embodiment> In the first embodiment, an example of assigning one or more unified TCI states (e.g., indicator TCI states) to a UL transmission (e.g., a PUSCH transmission) scheduled by a single DCI is described. While PUSCH is used as an example in the following description, it may be applied to other channels / reference signals. The assignment may be rephrased as mapping / association / linking.

[0195] For a PUSCH scheduled / triggered / activated by a single DCI (e.g., a repeating PUSCH or two or more PUSCHs), multiple (e.g., two) indicator TCI states may be assigned based on at least one of the following options 1-1 to 1-2.

[0196] [Option 1-1] For a pusher scheduled / triggered / activated by a single DCI, multiple (e.g., two) instruction TCI states may be assigned using RRC / MAC CE.

[0197] [Options 1-2] For a PUSCH scheduled / triggered / activated by a single DCI, the DCI may be assigned one of several indicator TCI states (or one of a selected set of states). The DCI used to indicate the indicator TCI state and the DCI used to schedule / trigger / activate the PUSCH may be different DCIs or the same DCI.

[0198] Based on at least one (or both) of the following options 1-2-1 and 1-2-2, DCI may indicate two indicated TCI states.

[0199] 《Option 1-2-1》 For a single DCI-based multi-TRP, the configuration of two SRS resource sets (for example, an SRS resource set with usage=CB / NCB) may be supported. Each PUSCH may be transmitted using at least one of the joint / UL TCI state and TPC parameters corresponding to the SRS resource set (or SRS resource) indicated by a given rule / upper layer / DCI.

[0200] The association between an SRS resource set (or SRS resource) and a joint / UL TCI state or TPC parameter may be defined in the specification, or it may be set by the base station to the UE via RRC parameters, etc.

[0201] 《Option 1-2-2》 If a DCI contains an SRS resource indicator field (e.g., an SRS resource set indicator field), an SRS resource set (or SRS resource) may be indicated by that SRS resource set indicator field. For example, the SRS resource set indicated by that SRS resource set indicator field may be at least one of the following: 1st, 2nd, both (1st, 2nd), or both (2nd, 1st) (e.g., SRS resource set indicator field={1st, 2nd, both(1st, 2nd), both(2nd, 1st)}). The SRS resource set (or SRS resource) may be associated with a predetermined TCI state (or TRP ID).

[0202] If two SRS resource sets are configured (for example, SRS resource sets with CB / NCB usage), the SRS resource set indicator field may be present in DCI format 0_1 / 0_2. A DCI containing the SRS resource set indicator field may schedule / trigger / activate a PUSCH.

[0203] Figure 8 shows an example where two SRS resource sets (here, SRS resource sets #0 and #1) are directed. Here, one DCI schedules two PUSCHs (here, PUSCH #0 and PUSCH #1), and this DCI directs two SRS resource sets / SRS resources. It also shows the case where PUSCH #0 corresponds to SRS #1 of SRS resource set #0, and PUSCH #1 corresponds to SRS #2 of SRS resource set #1.

[0204] The UE may determine predetermined parameters for a PUSCH scheduled / activated by a DCI (e.g., DCI format 0_1 / 0_2) from the indicative joint / UL TCI state applied to the SRS resource indicated by the DCI. The predetermined parameters may be a UL transmission filter (e.g., UL transmission filter), a path loss reference signal (e.g., PL-RS), or UL power control parameters for the PUSCH (e.g., UL PC parameter setting). The UL power control parameters may be parameters applied to the power control of the PUSCH (at least one of P0, α, and closed loop index).

[0205] A predetermined field (one or more fields) in the DCI may indicate an SRS resource set and at least one of the SRS resources contained within each SRS resource set. Here, a predetermined field in the DCI may indicate the SRS resource corresponding to PUSCH#0 and the SRS resource corresponding to PUSCH#1.

[0206] If an SRS resource set instruction field (or SRS resource instruction field) is not included in / does not exist in the DCI (for example, when PUSCH is scheduled by DCI format 0_0), an SRS resource set (or SRS resource) may be selected by a predetermined rule, or an SRS resource set (or SRS resource) may be indicated by a higher-layer parameter. The predetermined rule may be, for example, an SRS resource set index (for example, a first SRS resource set with a small index is selected).

[0207] [SRS Resources (Sets) and Indicated TCI Status] In a single DCI-based push, if the SRS resources indicated by the DCI (e.g., SRI included in the DCI) correspond to joint / UL TCI states and TPC parameters (e.g., closed-loop power control states (e.g., CL-PC state) / cumulative values ​​of TCP commands, etc.), then it is important how the two indicated TCI states are applied (or assigned) to each RSR resource (set).

[0208] For example, PUSCH may apply the joint / UL TCI status and TPC-related parameters of the SRS resource set (or SRS resource) corresponding to the SRI. As an example, at least one of Alt.1-1 to Alt.1-2 below may be applied.

[0209] 《Alt.1-1》 If one directive joint / UL TCI state is specified, that single directive joint / UL TCI state may be assigned / applied to all SRS resources (sets).

[0210] Alt1-1 may be limited to SRS resources (sets) with specific uses. These specific uses may include codebooks / non-codebooks (e.g., CB / NCB). In this case, configured joint / UL TCI state may be applied to SRS resources (sets) with other uses.

[0211] 《Alt.1-2》 If two directive joint / UL TCI states are specified, one of the two specified directive joint / UL TCI states may be assigned / applied to each SRS resource (set).

[0212] For example, a UE may apply a first directive joint / UL TCI state to a first SRS resource set (or a first SRS resource included in an SRS resource set) and a second directive joint / UL TCI state to a second SRS resource set (or a second SRS resource included in an SRS resource set). The assignment / assignment rules between SRS resources (sets) and unified TCI states (or TRP IDs) may be defined in the specification or set by RRC parameters.

[0213] Figure 9 shows the case where the first instruction joint / UL TCI state #1 is assigned to the first SRS resource set #0 (or SRS#0 / SRS#1), and the second instruction joint / UL TCI state #2 is assigned to the second SRS resource set #1 (or SRS#2 / SRS#3).

[0214] This makes it possible to instruct each SRS resource set with a separate instruction joint / UL TCI state. By instructing the UE whether one or both SRS resource sets correspond to a PUSCH, you can instruct the UE whether to apply one or both instruction TCI states.

[0215] Since PUSCH and the SRS corresponding to PUSCH's SRI are expected to utilize the same spatial relationship / precoder, applying the first embodiment allows the mechanism for PUSCH and SRS to utilize the same spatial relationship / precoder to be maintained even in Rel.18 and beyond. This enables improved base station reception performance and appropriate PUSCH precoder instruction.

[0216] Alt1-2 may be limited to SRS resources (sets) with specific uses. These specific uses may include codebooks / non-codebooks (e.g., CB / NCB). In this case, configured joint / UL TCI state may be applied to SRS resources (sets) with other uses.

[0217] [Variation 1] If only one SRS resource set (for example, an SRS resource set with use CB / NCB) is configured / instructed, the UE does not need to assume that two instruction joint / UL TCI states are instructed.

[0218] Furthermore, if only one SRS resource set (for example, an SRS resource set with CB / NCB usage) is configured, different instruction joint / UL TCI states may be applied / assigned to different SRS resources within that single SRS resource set. For example, SRS resources with smaller code points in the DCI's SRI field may correspond to a first instruction joint / UL TCI state, and SRS resources with larger code points in the SRI field may correspond to a second instruction joint / UL TCI state (see Figure 10).

[0219] A small code point may mean code point 0 (e.g., use is CB) or code point 0 / 1 (e.g., use is NCB). A large code point may mean code point 1 (e.g., use is CB) or code point 2 / 3 (e.g., use is NCB). Here, we have shown the case where the SRI field is 1 or 2 bits, but it is not limited to these.

[0220] Figure 10 shows an example where, when only one SRS resource set #0 is configured / instructed, SRS resource #0 and SRS resource #1 included in that SRS resource set #0 correspond to different TCI states. Here, SRS resource #0 corresponding to code point 0 corresponds to the first TCI state, and SRS resource #1 corresponding to code point 1 corresponds to the second TCI state.

[0221] In this way, by assigning different TCI states to multiple SRS resources contained within the same SRS resource set, it becomes possible to switch between joint / UL TCI states using the SRI field, even if only one SRS resource set is configured.

[0222] [Variation 2] If two SRS resource sets (for example, an SRS resource set with CB / NCB usage) are configured, different instruction joint / UL TCI states may be applied to / assigned to multiple SRS resources within the same SRS resource set.

[0223] For example, an SRS resource with a small code point in the DCI's SRI field may correspond to a first indicated joint / UL TCI state, while an SRS resource with a large code point in the SRI field may correspond to a second indicated joint / UL TCI state (see Figure 11).

[0224] A small code point may mean code point 0 (e.g., use is CB) or code point 0 / 1 (e.g., use is NCB). A large code point may mean code point 1 (e.g., use is CB) or code point 2 / 3 (e.g., use is NCB). Here, we have shown the case where the SRI field is 1 or 2 bits, but it is not limited to these.

[0225] Figure 11 shows an example where, when one SRS resource set #0 and SRS resource set #1 are set / instructed, multiple (in this case, two) SRS resources within each SRS resource set correspond to different TCI states. Specifically, SRS resource #0 and SRS resource #1 within SRS resource set #0 correspond to different TCI states, respectively, and SRS resource #2 and SRS resource #3 within SRS resource set #1 correspond to different TCI states, respectively.

[0226] Figure 11 shows a case where the same code point in SRS resource set #0 and SRS resource set #1 corresponds to the same TCI state (for example, code point 0 corresponds to the first TCI state / code point 1 corresponds to the second TCI state), but it is not limited to this. The TCI states corresponding to the SRS resources included in each SRS resource set may be set separately by RRC or the like.

[0227] <Second Embodiment> In the second embodiment, an example of setting / applying a unified TCI state to a single DCI-based multi-TRP is described. For example, this is suitably applicable to cases where a CORESET pool index is used for a single DCI-based multi-TRP, and it is supported that an indicated joint TCI state is indicated for each of multiple (e.g., two) CORESET pool indexes. The CORESET pool index may be read as a TRP index.

[0228] 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 established by higher-layer signaling. Alternatively, the association between the TRP ID and each channel / resource / resource set / reference signal may be made implicitly based on predetermined rules.

[0229] A TRP ID may be a CORESET pool index. A 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). Note that the number of CORESET pool indexes is not limited to two; three or more CORESET pool indexes may be defined / supported.

[0230] 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 a TRP with a smaller index (e.g., TRP ID=0), and the second TRP may be a TRP with a larger index (e.g., TRP ID=1).

[0231] For example, consider a case where 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 12). In this case, the first TCI state #1 may be indicated by the PDCCH / DCI transmitted at the first CORESET pool index #0, and the second TCI state #1 may be indicated by the PDCCH / DCI transmitted at the second CORESET pool index #1.

[0232] 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 12). Figure 12 shows the case where the first TCI state #1 is applied to PUSCH #1 sent to the first TRP #0 (or PUSCH #1 corresponding to the first TRP #0).

[0233] On the other hand, the second TCI state #2 may be applied to channels / resources / resource sets / reference signals associated with the second CORESET pool index #1 (or the second TRP #1).

[0234] The TRP ID may be a predetermined ID (for example, a new ID). Each predetermined 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).

[0235] 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 indexes. Alternatively, UL transmissions associated with different CORESET pool indexes may belong to different timing advance groups (TAGs).

[0236] The following describes an example of associating a TRP ID (or CORESET pool index / specified ID) with a channel / resource / resource set / reference signal.

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

[0238] Case 1 The TRP ID may be associated with a scheduling PDCCH / search space (or search space set) / CORESET. This association may be set / activated / instructed by the RRC / MAC CE.

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

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

[0241] Case 3 The TRP ID may be associated with the TCI status indicated to PUSCH. This association may be set / activated / indicated by the RRC / MAC CE.

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

[0243] A TRP ID may be set for each SRS resource set. SRS resource sets may be associated with 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}).

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

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

[0246] In addition, when a plurality of TCI states / SRI / SRS resources / SRS resource sets are specified for dynamic PUSCH, the TRP ID related to the dynamic PUSCH may be related to at least one of the above plurality of TCI states / SRI / SRS resources / SRS resource sets. For example, when two TCI states are specified for dynamic PUSCH, the TRP ID related to the dynamic PUSCH may be related to at least one of the first TCI state and the second TCI state among the two TCI states.

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

[0248] [Configured grant PUSCH] The TRP ID (or, CORESET pool index) related to the configured grant PUSCH may be determined based on at least one of the following cases.

[0249] Case 1 The TRP ID may be associated with the configured grant configuration. The association may be set / activated / instructed by RRC / MAC CE.

[0250] The TRP ID may be set in the upper layer parameters related to the configured grant (e.g., ConfiguredGrantConfig). Alternatively, the TRP ID may be associated with the ConfiguredGrantConfigIndex.

[0251] 《Case 2》 For type 2 configured grants, the TRP ID may be associated with the PDCCH / search space (or search space set) / CORESET that transmits the DCI for activation. Such association may be set / activated / instructed by RRC / MAC CE.

[0252] 《Case 3》 The TRP ID may be instructed by the DCI for activation.

[0253] 《Case 4》 The TRP ID may be associated with the TCI state indicated for the PUSCH. Such association may be set / activated / instructed by RRC / MAC CE.

[0254] 《Case 5》 The TRP ID may be associated with the SRI. Alternatively, the TRP ID may be associated with the SRS resource / SRS resource set indicated for the PUSCH. Such association may be set / activated / instructed by RRC / MAC CE. Note that the SRS resource / SRS resource set may correspond to the SRS for a predetermined use (e.g., CB / NCB).

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

[0256] 《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.

[0257] The above-mentioned settings, grant settings / PDCCH / CORESET / TCI status / SRI / SRS resources / SRS resource sets may be set / activated / specified by RRC / MAC CE / DCI.

[0258] Furthermore, if multiple TCI states / SRIs / SRS resources / SRS resource sets are specified for a configuration grant push, the TRP ID associated with that configuration grant push may be associated with at least one of the above multiple TCI states / SRIs / SRS resources / SRS resource sets.

[0259] The UE determines / selects the joint / UL TCI state to apply to the configured grant PUSCH based on one of the association rules described above.

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

[0261] Case 1 When a PUCCH resource / PUCCH transmission is instructed / triggered by a DCI, the TRP ID may be associated with the PDCCH / search space (or search space set) / CORESET that transmits the DCI. This association may be set / activated / instructed by the RRC / MAC CE.

[0262] Alternatively, the TRP ID may be indicated by a DCI that instructs / triggers the PUCCH resource / PUCCH transmission.

[0263] "Case 2" The TRP ID may be associated with the PUCCH resource. Such association may be set / activated / instructed by RRC / MAC CE.

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

[0265] "Case 3" The TRP ID may be associated with the TCI state or spatial relation information indicated for the PUCCH. Such association may be set / activated / instructed by RRC / MAC CE.

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

[0267] "Case 5" The TPC related parameters for dynamic PUCCH may be, for example, path loss reference signal (e.g., PL-RS), predetermined parameters (e.g., P0, alpha), closed loop index (e.g., close loop index).

[0268] "Case 6" The TRP ID may be a predefined / fixed value. For example, for a 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.

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

[0270] The UE determines / selects the joint / UL TCI state to apply to PUCCH based on one of the association rules described above.

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

[0272] Case 1 If an SRS is triggered by a DCI (for example, in the case of a periodic SRS), the TRP ID may be associated with the PDCCH / search space (or search space set) / CORESET that transmits the DCI. This association may be set / activated / instructed by the RRC / MAC CE.

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

[0274] Case 2 The TRP ID may be associated with an SRS resource / SRS resource set. This association may be configured / activated / instructed by the RRC / MAC CE.

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

[0276] Case 3 The TRP ID may be associated with TCI status or spatial relationship information directed to the SRS. This association may be set / activated / directed by the RRC / MAC CE.

[0277] Case 4 TPC-related parameters for SRS (e.g., TPC-related parameters) may include, for example, a path loss reference signal (e.g., PL-RS), predetermined parameters (e.g., P0, alpha), and a closed-loop index (e.g., close loop index).

[0278] Case 5 The TRP ID may be a predefined / fixed value. For example, for an 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 apply to all SRSs.

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

[0280] Furthermore, the association (correspondence) between SRS and 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 in question.

[0281] The UE determines / selects the joint / UL TCI status applicable to the SRS based on one of the association rules described above.

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

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

[0284] Alternatively, if CSI-RS is triggered by DCI (e.g., A-CSI-RS), the TRP ID may be indicated by that DCI.

[0285] Case 2 The TRP ID may be associated with a CSI-RS resource / CSI-RS resource set. This association may be configured / activated / instructed by the RRC / MAC CE.

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

[0287] Case 3 The TRP ID may be associated with TCI status or spatial relationship information indicated to the A-CSI-RS. This association may be set / activated / indicated by the RRC / MAC CE.

[0288] 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) can apply to all CSI-RSs.

[0289] Case 5 The specified joint / DL TCI status may be applied to a specific CSI-RS. A specific CSI-RS may be at least one of the following: A / SP / P CSI-RS, CSI-RS with / without repetition, CSI-RS with / without trs information (trs-info), CSI-RS for mobility, and CSI-RS for BM / CSI.

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

[0291] The UE determines / selects the joint / UL TCI status applicable to the CSI-RS based on one of the association rules described above.

[0292] [PDCCH] For PDCCHs in a single DCI-based multi-TRP, the UE may apply an indicated joint / DL TCI state (e.g., indicated joint / DL TCI state) specific to that CORESET pool index value to PDCCHs in CORESETs associated with the same CORESET pool index value.

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

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

[0295] In this case, at least one of the following rules may apply to PDCCH.

[0296] Rule 1 For a specific CORESET (e.g., CORESET#0), if a higher-level parameter (e.g., followUnifiedTCIstate) is set to indicate adherence to a unified TCI state, the indicated TCI state may be applied. Otherwise, the mechanism of the existing system (e.g., Rel.15) may be applied to that specific CORESET. The mechanism of the existing system (e.g., Rel.15) may, for example, indicate that the specific CORESET adheres to a TCI state activated by MAC CE, or that it is SSB and QCL.

[0297] Rule 2 Alternatively, the indicated TCI state may always be applied to any CORESET other than a specific CORESET (e.g., CORESET#0) that has USS / CSS type 3.

[0298] Rule 3 Alternatively, if followUnifiedTCIstate is set for a CORESET other than a specific CORESET (e.g., CORESET#0) that has CSS other than CSS type 3, the instructed TCI state may be applied to that CORESET. Otherwise, the configured TCI state for that CORESET may be applied to that CORESET.

[0299] Note that rules other than those described in rules 1-3 above may also apply. For example, the same or different rules as rules 1 / 2 / 3 may apply depending on certain conditions. The specified conditions may be any of the following: • Which CORESET it is (for example, whether it is a specific CORESET (CORESET#0)), • What type of search space is it (for example, CSS or USS, and if CSS, is it CSS type 0 / 0A / 1 / 2 / 3)? • Whether or not a higher-level parameter (e.g., followUnifiedTCIstate) is set to indicate adherence to the Unified TCI state.

[0300] Alternatively, regardless of the configuration (e.g., CSS / USS / followUnifiedTCIstate / CORESET#0), for all CORESET / PDCCH, the indicated TCI state related to the corresponding CORESET pool index may be applied.

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

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

[0303] When the scheduling offset < timeDurationForQCL, regardless of the CORESET (e.g., scheduling CORESET) for scheduling 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 rules of the existing system (e.g., Rel.16) may be applied. When the default QCL rules are applied, the QCL corresponding to the lowest CORESET ID having the same CORESET pool index in the latest monitoring slot may be applied to the scheduled PDSCH.

[0304] If the scheduling offset is greater than or equal to timeDurationForQCL, the QCL assumption for PDSCH may be the same as the QCL assumption for scheduling CORESET. This may mean that the QCL assumption depends on the QCL assumption used for scheduling CORESET.

[0305] [followUnifiedTCIstate] For each channel / signal, the setting / application of a higher-layer parameter (e.g., followUnifiedTCIstate) indicating adherence to a unified TCI state may be extended.

[0306] 《PUSCH》 For a PUSCH, the relevant higher-level parameter (e.g., followUnifiedTCIstate) does not need to be defined. For example, all / some PUSCHs may follow the indicated joint / UL TCI state.

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

[0308] 《PUCCH》 For a PUCCH, the relevant higher-level parameter (e.g., followUnifiedTCIstate) does not need to be defined. For example, all / some PUCCHs may follow the indicated joint / UL TCI state.

[0309] Alternatively, the higher-level parameter (e.g., followUnifiedTCIstate) may be configurable / supported in the PUCCH configuration (e.g., PUCCH-Config) / scheduling CORESET. For example, if the higher-level parameter is set, the associated PUCCH may follow the instructing joint / UL TCI state; otherwise, the PUCCH may follow the setting joint / UL TCI state.

[0310] 《SRS》 For an SRS, the relevant higher-level parameter (e.g., followUnifiedTCIstate) does not need to be defined. For example, all / some SRSs may follow the indicated joint / UL TCI state.

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

[0312] Furthermore, only a limited type of SRS (e.g., only some SRSs) may conform to the indicated joint / UL TCI state. Some SRSs may be used for at least one of the following: codebook, non-codebook, beam management, antenna switching, and positioning. Alternatively, some SRSs may be at least one of a periodic SRS, a semi-persistent SRS, and aperiodic SRS with different time-domain operations.

[0313] 《PDCCH》 For a PDCCH, the relevant higher-level parameter (e.g., followUnifiedTCIstate) does not need to be defined. For example, all / some CORESETs (or the PDCCHs corresponding to those CORESETs) may follow the indicated joint / UL TCI state.

[0314] Alternatively, the higher-level parameter (e.g., followUnifiedTCIstate) may be configurable / supported in the PDCCH configuration (e.g., PDCCH-Config) / CORESET / SearchSpace (or SearchSpace Set). For example, if the higher-level parameter is configured, the associated PDCCH / CORESET / SearchSpace (or SearchSpace Set) may follow the indicated joint / UL TCI state; otherwise, the PDCCH / CORESET / SearchSpace (or SearchSpace Set) may follow the configured joint / UL TCI state.

[0315] Furthermore, only a limited number of PDCCH / CORESET / searchspaces (or searchspace sets) (for example, only some PDCCH / CORESET / searchspaces (or searchspace sets)) may conform to the indicated joint / UL TCI state. Some PDCCH / CORESET / searchspaces (or searchspace sets) may be specific CORESETs (e.g., CORESET#0) / CORESETs other than CORESET#0 / CSS / USS. In the case of CSS, at least one of CSS types 0 / 0A / 1 / 2 / 3 may also be selected for some searchspace sets.

[0316] 《PDSCH》 For a PDSCH, the relevant higher-level parameter (e.g., followUnifiedTCIstate) does not need to be defined. For example, all / some PDSCHs may follow the indicated joint / UL TCI state.

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

[0318] <Third Embodiment> In the third embodiment, an example of timing advance control in a single DCI-based multi-TRP is described.

[0319] [TA / TAG] When using multiple TRPs, the distance between the UE and each TRP may differ. Multiple TRPs may be contained within the same cell (e.g., a serving cell). Alternatively, some TRPs may correspond to a serving cell, while others correspond to non-serving cells. In this case, it is conceivable that the distance between each TRP and the UE will differ.

[0320] In existing systems, the transmission timing of UL (Uplink) channels and / or UL signals (UL channels / signals) is adjusted by Timing Advance (TA). The reception timing of UL channels / signals from different user terminals (UEs) is adjusted at the base station (TRP: Transmission and Reception Point, also known as gNB: gNodeB, etc.).

[0321] The UE may control the timing of UL transmission by applying a timing advance (multiple timing advance) for each pre-configured Timing Advance Group (TAG).

[0322] When applying multiple timing advances, Timing Advance Groups (TAGs) are supported, categorized by transmission timing. 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.

[0323] When applying Multiple Timing Advance, the UE can independently adjust the transmission timing of the cells belonging to each TAG, allowing the radio base station to synchronize the uplink signal reception timing from the UE, even when using multiple cells.

[0324] TAGs (for example, serving cells belonging to the same TAG) may be defined by higher-level parameters. The same timing advance value may be applied to serving cells belonging to the same TAG. The timing advance group containing a MAC entity's SpCell may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAG).

[0325] In existing systems (e.g., Rel.16 NR), the setting of up to four TAGs is supported per cell group (e.g., MCG / SCG) (see Figure 13). Figure 13 shows a case where three TAGs are set for a cell group containing SpCell and SCell#1~#4. Here, 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 belong to the third TAG (TAG#2).

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

[0327] A MAC CE for timing advance commands (TAC MAC CE) may be configured to include a field for the timing advance group index (e.g., TAG ID) and a field for the timing advance command (see Figure 14).

[0328] In a single DCI-based multi-TRP, the association between TAGs and UL channels / signals may be controlled depending on whether a unified TCI state is set / applied. For example, if a unified TCI state (e.g., joint / UL TCI state) is set, the association between TAGs and UL channels / signals may be used for both TAG association (e.g., association between TAG and UL channel / signal) and indicating joint / UL TCI state association (e.g., association between indicating joint / UL TCI state and UL channel / signal). The association between TAGs and TCI states / CORESET pool indices may be predefined / set, or it may be set from the base station to the UE via RRC parameters.

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

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

[0331] For example, a TAG ID may be set as part of a joint / UL TCI state (or spatial relationship). For UL transmissions, a TAG ID associated with a joint / UL TCI state (or spatial relationship) may be used.

[0332] [Option 3-2] You may associate the TAG with a CORESET pool index (or TRP index).

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

[0334] For at least one of the Type 1 configurations, grant PUSCH, periodic / semi-persistent SRS, and periodic / semi-persistent PUCCH, the CORESET pool index may be set by the RRC parameter.

[0335] [Option 3-3] You may associate the TAG with the SSB group.

[0336] For UL transmissions, the UE may adopt a TAG associated with the SSB group. If the Path Loss Reference Signal (PL RS) is an SSB, the UE may adopt a TAG associated with the SSB group to which the PL RS of the UL transmission belongs. If the PL RS is a CSI-RS, the UE may adopt a TAG associated with the SSB group to which the QCL source SSB of the PL RS (e.g., the QCL source SSB) belongs.

[0337] [Options 3-4] TAG association can be performed as follows: For dynamically scheduled / activated channels / signals, the TAG associated with the CORESET pool index of the CORESET transmitting the scheduled PDCCH is used for UL transmission. For periodic / semi-persistent UL channels / signals (not scheduled / activated by DCI), the TAG ID may be set by the RRC parameter.

[0338] In option 3-4, all dynamically scheduled / activated channels / signals may be associated with TAGs based on the CORESET pool index of the scheduling / activating PDCCH.

[0339] Options 3-1 / 3-2 / 3-4 assume a relationship between "TAG" and "TCI status or CORESET pool index".

[0340] Assume a scenario where multiple (e.g., two) timing advances (e.g., TAs) are configured for a single DCI-based multi-TRP, and a CORESET pool index is set up.

[0341] In such cases, when a joint / UL TCI state is set, the association between the TRP ID (or CORESET pool index) and each channel / resource / resource set / reference signal may be used for both the purpose of selecting / determining a single indicator joint / UL TCI state for each channel / reference signal and determining the TA.

[0342] When multiple (e.g., two) timing advances (e.g., TAs) are configured for a single DCI-based multi-TRP and a CORESET pool index is set, 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 15). Figure 15 shows 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.

[0343] Alternatively, if multiple (e.g., two) timing advances (e.g., TAs) are configured for a single DCI-based multi-TRP, and a CORESET pool index is configured, and no joint / UL TCI state is configured, the association between the TRP ID (or CORESET pool index) and each channel / resource / resource set / reference signal may be used solely for the purpose of determining the TA.

[0344] If a Joint / UL TCI state is set, this may be interpreted as if a higher-level parameter indicating adherence to a Unified TCI state (e.g., followUnifiedTCIstate) is set. If a Joint / UL TCI state is not set, this may be interpreted as if a higher-level parameter indicating adherence to a Unified TCI state (e.g., followUnifiedTCIstate) is not set.

[0345] <Fourth Embodiment> In the fourth embodiment, an example of transmission control in simultaneous UL transmission using multiple panels (for example, simultaneous multi-panel UL transmission (SiMPUL), simultaneous UL transmission from multiple panels (STxMP)) will be described.

[0346] This embodiment may be applied to a single-DCI-based multi-TRP utilizing a CORESET pool index. The CORESET pool index may be read as a TRP index. In the following description, the operation in a multi-DCI-based multi-TRP may be applied to a single-DCI-based multi-TRP. In this case, it may be read as one DCI among the multi-DCIs (e.g., first DCI#0 or second DCI#1) scheduling / activating / triggering PUSCh#0 and PUSCH#1. Also, one DCI may direct multiple (e.g., two) SRS resource sets (or SRS resources) to the UE.

[0347] [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)) to one or more transmission / reception points (TRPs) may be supported to improve UL throughput / reliability.

[0348] In this disclosure, simultaneous UL transmission using multiple panels, STxMP, SiMPUL, and UL transmission in the same time domain using multiple panels may be interpreted interchangeably.

[0349] In this disclosure, the terms panel, receiving panel, UE panel, UE capability value, UE capability value set, panel group, etc., may be interpreted interchangeably.

[0350] 《PUSCH, a single DCI-based multi-TRP》 The STxMP PUSCH for single DCI-based multi-TRP is being considered for transmission using the following methods: • SDM (Spatial Decomposition Multiplexing) scheme. • FDM (Frequency Division Multiplexing) - B scheme. • FDM-A scheme. • SFN (Single Frequency Network) based transmission scheme. • SDM repetition scheme.

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

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

[0353] The FDM-A scheme may also be a method in which different portions of a frequency domain resource of a single PUSCH (transmission opportunity) are transmitted from different UE panels.

[0354] An SFN-based transmission scheme may also be a method in which all of the same layer / DMRS ports on a single pusher are transmitted simultaneously from multiple (two) different UE panels.

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

[0356] 《PUSCH Multi-DCI based Multi-TRP》 For STxMP pushers in a multi-DCI-based multi-TRP, multiple (two) pushers may be associated with different TRPs. These multiple different pushers may be transmitted from different UE panels.

[0357] The total number of layers for N PUSCH instances may be 2 × N.

[0358] Furthermore, the multiple PUSCHs may include at least one of the following: a PUSCH scheduled by DCI, a PUSCH for a configured grant, and a PUSCH for message 3 / message A.

[0359] Furthermore, these multiple PUSCHs may completely / partially overlap in the time domain, completely / partially overlap in the frequency domain, or not overlap in the frequency domain.

[0360] 《PUCCH, a single DCI-based multi-TRP》 The STxMP PUCCH for single DCI-based multi-TRP is being considered for transmission using the following methods: • FDM-A scheme. • FDM-B scheme. • SFN-based transmission scheme.

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

[0362] The FDM-B scheme may also be a method in which multiple (two) FDM-decoded PUCCHs (transmission opportunities) of the same UCI in the same PUCCH format are transmitted simultaneously from different UE panels.

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

[0364] For each of the above schemes, specific PUCCH formats to be supported are being considered.

[0365] 《PUCCH, a multi-DCI based multi-TRP》 For STxMP PUCCHs in multi-DCI-based multi-TRP, multiple (two) PUCCHs may be associated with different TRPs. These multiple different PUCCHs may be transmitted from different UE panels.

[0366] Furthermore, these multiple PUCCHs may completely or partially overlap in the time domain.

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

[0368] [Multi-DCI based STxMP PUSCH] Different DCIs associated with different CORESET pool indices may schedule different PUSCHs on different UE panels. In this case, two PUSCHs can be sent simultaneously. In single DCI-based PUSCH transmissions using a CORESET pool index (or TRP index), a single DCI may schedule different PUSCHs.

[0369] Each PUSCH may be associated with a single SRS resource set having a predetermined use (e.g., usage=CB / NCB). At least one of different SRIs and different joint / UL TCI states may be associated with different PUSCHs associated with different CORESET pool indexes.

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

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

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

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

[0374] For example, one SRI / TPMI field in 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 a set of SRI / TPMIs for that CORESET pool index. In the case of a single DCI base, one DCI (e.g., two fields) may indicate multiple SRI / TPMIs.

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

[0376] Figure 16 illustrates the case where the SRS resource indicated in the SRI field of the first DCI#0 (here, SRS#1) is applied to PUSCH#0 scheduled by the first DCI#0 associated with the first CORESET pool index #0. It also illustrates the case where the SRS resource indicated in the SRI field of the second DCI#1 (here, SRS#2) is applied to PUSCH#1 scheduled by the second DCI#1 associated with the second CORESET pool index #1.

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

[0378] For PUSCHs to which multi-DCI-based simultaneous UL transmission is applied, the same joint / UL TCI state may be applied between the SRS resource (e.g., an SRS resource with usage=CB / NCB) and the scheduled PUSCH (e.g., a PUSCH associated with an SRI). This allows the UE to assume the same UL beam between the PUSCH and the designated SRI.

[0379] If the joint / UL TCI status is set, at least one of the following options 4A-1 to 4A-2 may be applied.

[0380] [Option 4A-1] The directive joint / UL TCI state associated with a CORESET pool index (={0,1}) may apply to all SRS resources within a given SRS resource set associated with the same CORESET pool index (e.g., an SRS resource set with usage=CB / NCB).

[0381] Figure 17 shows a case where an instruction 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 SRS resource set #0 (usage=CB) associated with the first CORESET pool index #0. This instruction joint / UL TCI state may also be applied to DCI#0, PUSCH#0, SRS#0, and SRS#1.

[0382] Furthermore, Figure 17 shows a case where an instruction joint / UL TCI state associated with a second CORESET pool index #1 is applied to multiple SRS resources (e.g., SRS#2, SRS#3) included in SRS resource set #1 (usage=CB) associated with the second CORESET pool index #1. This instruction joint / UL TCI state may also be applied to DCI#1, PUSCH#1, SRS#2, and SRS#3.

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

[0384] [Option 4A-2] Multiple instruction joint / UL TCI states associated with the CORESET pool index (={0,1}) may be indicated. One of these instruction joint / UL TCI states may be applied to each SRS resource. The correspondence (or mapping) between SRS resources and instruction joint / UL TCI states may be predefined or set by higher-level layer parameters, etc.

[0385] Figure 18 illustrates a case where multiple (e.g., two) directive 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 SRS resource set #0 (usage=CB) associated with the first CORESET pool index #0. The directive joint / UL TCI states (and SRS resources) to be applied may be instructed to the UE by the SRI field included in the first DCI#0 used for scheduling PUSCH#0.

[0386] Furthermore, this illustrates a case where multiple (e.g., two) directive 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 SRS resource set #1 (usage=CB) associated with the second CORESET pool index #1. The directive joint / UL TCI states (and SRS resources) to be applied may be instructed to the UE by the SRI field included in the second DCI#1 used for scheduling PUSCH#1.

[0387] In this way, by associating different instruction joint / UL TCI states with each SRS resource, it becomes possible to flexibly control which instruction joint / UL TCI state is applied.

[0388] Furthermore, multiple TCI states may be indicated for one or more SRS resources within the same SRS resource set.

[0389] [Multi-DCI based STxMP PUCCH] For simultaneous UL transmissions to 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.

[0390] Rel.16 supports both joint ACK / NACK (HARQ-ACK) feedback (mode) and separate ACK / NACK (HARQ-ACK) feedback (mode).

[0391] Joint ACK / NACK feedback may be set when a single DCI-based multi-TRP is configured, or when a multi-DCI-based multi-TRP is configured.

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

[0393] In joint ACK / NACK feedback, ACK / NACKs for PDSCHs sent from multiple TRPs are sent to a single TRP using a single PUCCH resource (see Figure 19A).

[0394] In separate ACK / NACK feedback, ACK / NACKs for PDSCHs transmitted from each TRP are sent to that TRP using a certain PUCCH resource, and ACK / NACKs for PDSCHs transmitted from each other TRP are sent to that other TRP using a different PUCCH resource (see Figure 19B).

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

[0396] In this case, while UE operation using multiple TRPs is possible for joint ACK / NACK feedback, the UE will always send PUCCH to a single beam / TRP, resulting in reduced resource utilization efficiency.

[0397] Furthermore, separate ACK / NACK feedback cannot function because it would be impossible to send it to one TRP using one PUCCH resource and to another TRP using a different PUCCH resource.

[0398] Therefore, the following describes an example of how to configure PUCCH resources when using multiple TRPs and when a common TCI state is indicated. The UE may determine the PUCCH resources according to at least one of the following options 4B-1 and 4B-2.

[0399] [Option 4B-1] The PUCCH resource may be determined / selected based on the association between the CORESET pool index and the PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config).

[0400] 《Option 4B-1-1》 For each CORESET / SRS resource set (usage=CB / NCB), a PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be configured for the UE. In the following explanation, CORESET / SRS resource set (usage=CB / NCB) may be interpreted as TRP / TCI state.

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

[0402] Figure 20 shows an example of how to configure PUCCH resources according to embodiment 4B-1-1. In the example shown in Figure 20, the UE is configured with a PUCCH resource set corresponding to the first CORESET / SRS resource set (usage=CB / NCB) and a PUCCH resource set corresponding to the second CORESET / SRS resource set (usage=CB / NCB).

[0403] Each CORESET / SRS resource set (usage=CB / NCB) may have up to a first number of PUCCH resource sets (e.g., 4). Each PUCCH resource set may have up to a second number of PUCCH resources (e.g., 8). The UE selects one PUCCH resource set from the configured PUCCH resource sets based on the UCI payload size (number of bits). In the example shown in Figure 20, if the number of bits in the UCI is N0 (e.g., 2) or less, the UE decides to use the first PUCCH resource set. Also in the example shown in Figure 20, if the number of bits in the UCI is greater than N0 and N1 or less, the UE decides to use the second PUCCH resource set.

[0404] In the example shown in Figure 20, the UE determines the PUCCH resource set / PUCCH resource corresponding to the CORESET / SRS resource set (usage=CB / NCB) based on the settings for each CORESET / SRS resource set (usage=CB / NCB).

[0405] Furthermore, for each CORESET / SRS resource set (usage=CB / NCB), the PUCCH resource set setting corresponding to the first (or second) CORESET / SRS resource set (usage=CB / NCB) may use the PUCCH resource set setting defined in existing specifications (e.g., Rel. 15-17). Alternatively, for each CORESET / SRS resource set (usage=CB / NCB), the PUCCH resource set setting corresponding to the first (or second) CORESET / SRS resource set (usage=CB / NCB) may use the PUCCH resource set setting newly defined (e.g., in Rel. 18 or later).

[0406] Furthermore, for each CORESET / SRS resource set (usage=CB / NCB), the PUCCH resource set setting corresponding to the second (or first) CORESET / SRS resource set (usage=CB / NCB) may utilize the PUCCH resource set setting defined in a new version (for example, Rel. 18 or later).

[0407] 《Option 4B-1-2》 A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for each CORESET / SRS resource set (usage=CB / NCB) for the UE.

[0408] A single PUCCH resource may be associated with a single CORESET / SRS resource set (usage=CB / NCB). The UE may be directed to a PUCCH resource associated with a single CORESET / SRS resource set (usage=CB / NCB). A CORESET / SRS resource set (usage=CB / NCB) may be independently associated with each PUCCH resource.

[0409] For each PUCCH resource, information (flags / indicators) may be set to indicate which of the indicated TCI states it is associated with. For example, this information may indicate either the first TCI state or the second TCI state.

[0410] If this information is not set, the UE may determine that the PUCCH resource is associated with a specific TCI state (for example, the first (or second) TCI state).

[0411] The beam indication feature for each PUCCH resource group, as defined in Rel.16, may be used to associate CORESET / SRS resource sets (usage=CB / NCB) with PUCCH resources.

[0412] For example, the UE may determine the association between a CORESET / SRS resource set (usage=CB / NCB) and a PUCCH resource by following steps 1 through 3 below: • The PUCCH resources of the PUCCH resource group (for example, PUCCH resource groups 0 to 3) are configured (Step 1). Step 2 establishes an association between the PUCCH resource group and either the first TCI state or the second TCI state. When one or more (two) TCI states are indicated using MAC CE / DCI, multiple (e.g., all) PUCCH resources associated with the indicated TCI states are updated (Step 3).

[0413] The beam direction feature for each PUCCH resource group, as defined in Rel.16, does not need to be used.

[0414] In this case, an association may be established between the UE and either the first TCI state or the second TCI state.

[0415] Figure 21 shows an example of how to configure the PUCCH resource related to option 4B-1-2. In the example shown in Figure 21, 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 PUCCH resource is the same as in the example shown in Figure 20.

[0416] In the example shown in Figure 21, the UE determines the PUCCH resources corresponding to each CORESET / SRS resource set (usage=CB / NCB) based on the settings of the PUCCH resource set common to each CORESET / SRS resource set (usage=CB / NCB). In the example shown in Figure 21, among the PUCCH resources included in the PUCCH resource set, PUCCH resources with PUCCH resource indicators (PRI) from "000" to "011" are associated with the first CORESET / SRS resource set (usage=CB / NCB), and PUCCH resources with PRIs from "100" to "111" are associated with the second CORESET / SRS resource set (usage=CB / NCB). Based on these associations, the UE determines the PUCCH resources associated with each CORESET / SRS resource set (usage=CB / NCB).

[0417] Note that the settings common to each CORESET / SRS resource set (usage=CB / NCB) may be those of the PUCCH resource set defined in existing specifications (e.g., Rel. 15-17). Alternatively, the settings common to each CORESET / SRS resource set (usage=CB / NCB) may be those of the PUCCH resource set newly defined (e.g., in Rel. 18 or later).

[0418] According to option 4B-1-2, the joint TCI state / separate (UL) TCI state of a PUCCH resource can be specified by using the selection of a PUCCH resource with a PRI / Control Channel Element (CCE) index.

[0419] 《Variation 1 of Option 4B-1-2》 A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for each CORESET / SRS resource set (usage=CB / NCB) for the UE.

[0420] A single PUCCH resource may be associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB). The UE may indicate a PUCCH resource associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB).

[0421] For one or more (e.g., some or all) PUCCH resources, information (flags / indicators) may be set to indicate which of the indicated TCI states they are associated with. For example, this information may indicate either the first TCI state or the second TCI state.

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

[0423] When multiple (two) TCI states are indicated, the UE may decide to apply the multiple indicated TCI states. This case may apply, for example, to at least one of the repeated transmission of PUCCH to a multi-TRP (as defined in Rel. 17) and the simultaneous transmission of PUCCH using a multi-panel (as defined in Rel. 18 and later).

[0424] When multiple (two) TCI states are indicated, the UE may decide to apply one of the indicated TCI states. The determination of this one TCI state may be specified in advance, set in the RRC, indicated in MAC CE / DCI, or depend on the UE implementation. This case may apply to PUCCH transmissions other than repeated PUCCH transmissions to multi-TRPs (as defined in Rel. 17).

[0425] Figure 22 shows an example of how to configure PUCCH resources according to Modification 1 of Option 4B-1-2. In the example shown in Figure 22, 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 PUCCH resources is the same as in the example shown in Figure 20.

[0426] In the example shown in Figure 22, the UE determines the PUCCH resource corresponding to each CORESET / SRS resource set (usage=CB / NCB) based on the settings of the PUCCH resource set common to each CORESET / SRS resource set (usage=CB / NCB).

[0427] In the example shown in Figure 22, two TCI states are indicated for one or more specific PUCCH resources (PUCCH resource groups). The UE decides to apply both TCI states to one or more specific PUCCH resources (PUCCH resource groups).

[0428] Furthermore, in the example shown in Figure 22, one or two TCI states are indicated for PUCCH resources other than the one or more specific PUCCH resources (PUCCH resource groups) mentioned above. If two TCI states are indicated for these PUCCH resources, the UE determines which of the two TCI states to apply based on specific rules.

[0429] Note that the settings common to each CORESET / SRS resource set (usage=CB / NCB) may be those of the PUCCH resource set defined in existing specifications (e.g., Rel. 15-17). Alternatively, the settings common to each CORESET / SRS resource set (usage=CB / NCB) may be those of the PUCCH resource set newly defined (e.g., in Rel. 18 or later).

[0430] According to variation 1 of option 4B-1-2, the joint TCI state / separate (UL) TCI state of a PUCCH resource can be specified using RRC / MAC CE / DCI / specific rules.

[0431] Furthermore, to specify one of the two specified TCI states, a new DCI field may be defined, a combination of (special) DCI fields may be used, or existing DCI fields may be used. For example, the association between the index of the first specified TCI state and the index of the second specified TCI state and the TCI code point may be set in the UE using RRC.

[0432] 《Variation 2 of Option 4B-1-2》 A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for each CORESET / SRS resource set (usage=CB / NCB) for the UE.

[0433] A single PUCCH resource may be associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB). The UE may indicate a PUCCH resource associated with one or more (two) CORESET / SRS resource sets (usage=CB / NCB).

[0434] According to variation 2 of option 4B-1-2, the joint TCI state / separate (UL) TCI state of a PUCCH resource can be specified using RRC / MAC CE / DCI / specific rules.

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

[0436] For example, the association may apply a first TCI state to a PUCCH resource associated with an even (or odd) first parameter. Alternatively, the association may apply a second TCI state to a PUCCH resource associated with an odd (or even) first parameter.

[0437] Furthermore, instead of the even (or odd) first parameter mentioned above, the association may be associated with the first TCI state by the lower half of the PUCCH resources (PRI) per PUCCH resource set. Also, instead of the odd (or even) first parameter mentioned above, the association may be associated with the second TCI state by the lower half of the PUCCH resources (PRI) per PUCCH resource set.

[0438] Furthermore, the UE may determine the TCI state of a PUCCH resource based on the TRP index of the scheduled PDSCH / scheduled 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 decide to apply the first (or second) TCI state to that PUCCH resource.

[0439] The UE does not need to assume / expect that the same PUCCH resource in the same slot will be directed by PRIs from multiple (two) TRPs.

[0440] Figure 23 shows an example of how to configure PUCCH resources according to Modification 2 of Option 4B-1-2. In the example shown in Figure 23, 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 PUCCH resources is the same as in the example shown in Figure 20.

[0441] In the example shown in Figure 23, the UE determines the PUCCH resource corresponding to each CORESET / SRS resource set (usage=CB / NCB) based on the settings of the PUCCH resource set common to each CORESET / SRS resource set (usage=CB / NCB).

[0442] In the example shown in Figure 23, an even-numbered PRI is associated with a first indicated TCI state, and an odd-numbered PRI is associated with a second indicated TCI state. This association may be specified in advance in the specifications. Based on this association, the UE determines which indicated TCI state to apply to PUCCH.

[0443] Note that the settings common to each CORESET / SRS resource set (usage=CB / NCB) may be those of the PUCCH resource set defined in existing specifications (e.g., Rel. 15-17). Alternatively, the settings common to each CORESET / SRS resource set (usage=CB / NCB) may be those of the PUCCH resource set newly defined (e.g., in Rel. 18 or later).

[0444] [Option 4B-2] Different DCIs associated with different CORESET pool indexes may point to different PUCCH resources. In this case, the PUCCH resources may be pointed to using a predetermined field contained in each DCI. The predetermined field may be a PUCCH resource pointing field (e.g., a PRI field).

[0445] In Figure 24, the first PUCCH resource (here, PUCCH resource #0) is specified by the PRI field of the first DCI #0 corresponding to the first CORESET pool index #0. Similarly, the second PUCCH resource (here, PUCCH resource #7) is specified by the PRI field of the second DCI #1 corresponding to the second CORESET pool index #1.

[0446] If the base station supports assigning different spatial relationships to different PUCCH resources via RRC / MAC CE, then no specification extension is necessary.

[0447] If Option 4B-2 is applied, the RRC / MAC CE may configure / instruct the association between the CORESET pool index and each PUCCH resource / PUCCH resource group / PUCCH resource set. For example, a higher-layer parameter for the PUCCH configuration (e.g., PUCCHConfig) may be set to specify the CORESET pool index (or TRP ID) corresponding to each PUCCH resource.

[0448] Alternatively, the association between the designated joint / UL TCI state and the PUCCH resource / PUCCH resource group / PUCCH resource set may be set / instructed by RRC / MAC CE.

[0449] If a DCI associated with a CORESET pool index indicates an indicative joint / UL TCI state, that indicative joint / UL TCI state may apply to all (or some) PUCCH resources (or all PUCCH resources in a PUCCH resource group) (see Figure 25).

[0450] Figure 25 assumes a case where 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 at the first CORESET pool index #0, and the second TCI state #1 may be indicated by the PDCCH / DCI transmitted at the second CORESET pool index #1.

[0451] This also shows how the association between PUCCH resources and CORESET pool indexes is set / instructed by RRC / MAC CE. Here, 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.

[0452] The UE may receive information regarding the association between the CORESET pool index and the PUCCH resource via the RRC parameter / MAC CE. If PUCCH resources #0-#3 are specified, the UE will send a PUCCH using the first TCI state #1. If PUCCH resources #4-#7 are specified, the UE will send a PUCCH using the second TCI state #2.

[0453] Furthermore, the DCI corresponding to the first CORESET#0 may indicate one of the PUCCH resources #0-#3, and the DCI corresponding to the second CORESET#1 may indicate one of the PUCCH resources #4-#7. Alternatively, the DCI corresponding to the first CORESET#0 may indicate one of the PUCCH resources #0-#7, and the DCI corresponding to the second CORESET#1 may indicate one of the PUCCH resources #0-#7.

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

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

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

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

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

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

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

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

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

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

[0464] The specific UE capability may represent at least one of the following: • To support unified TCI in single DCI-based multi-TRP configurations. • Supports joint TCI / separate TCI, • Support for multiple (e.g., two) timing advances. • Support for simultaneous UL transmission (e.g., STxMP) • The specified TCI is applied to the CORESET and associated PDSCH that have CSS.

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

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

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

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

[0469] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A terminal having: a receiving unit that receives information indicating a Unified Transmit Configuration Index (TCI) state and one downlink control information that instructs multiple UL transmissions; and a control unit that determines a Unified TCI state to apply to the multiple UL transmissions based on at least one of the information indicated by the downlink control information, a transmit / receive point (TRP) index corresponding to the UL transmission, and a control resource set pool index corresponding to the UL transmission. [Note 2] When multiple sounding reference signal (SRS) resource sets are configured, the control unit determines a unified TCI state to apply to the multiple UL transmissions based on at least one of the SRS resource sets and SRS resources corresponding to each UL transmission, as described in Appendix 1. [Note 3] The control unit determines, based on the downlink control information, at least one of the SRS resource sets and SRS resources corresponding to each UL transmission, as described in Appendix 1 or Appendix 2. [Note 4] When multiple unified TCI states are indicated, the control unit applies different unified TCI states to multiple SRS resource sets or multiple SRS resources included in the same SRS resource set, as specified in any of the terminals in Appendix 1 to Appendix 3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0514] The transmitting / receiving unit 120 may transmit information indicating the Unified Transmit Configuration Index (TCI) status and one downlink control information instructing multiple UL transmissions.

[0515] The control unit 110 may indicate a unified TCI state to be applied to multiple UL transmissions based on at least one of the information indicated by the downlink control information, the transmit / receive point (TRP) index corresponding to UL transmission, and the control resource set pool index corresponding to UL transmission.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0533] The transmitting / receiving unit 220 may receive information indicating the Unified Transmit Configuration Index (TCI) status and one downlink control information instructing multiple UL transmissions.

[0534] The control unit 210 may determine a unified TCI state to apply to multiple UL transmissions based on at least one of the information indicated by the downlink control information, the transmit / receive point (TRP) index corresponding to the UL transmission, and the control resource set pool index corresponding to the UL transmission.

[0535] If multiple sounding reference signal (SRS) resource sets are configured, the control unit 210 may determine a unified TCI state to apply to the multiple UL transmissions based on at least one of the SRS resource sets and SRS resources corresponding to each UL transmission.

[0536] The control unit 210 may determine, based on the downlink control information, at least one of the SRS resource sets and SRS resources corresponding to each UL transmission.

[0537] If multiple unified TCI states are indicated, the control unit 210 may apply different unified TCI states to multiple SRS resource sets or to multiple SRS resources included in the same SRS resource set.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0625] This application is based on Japanese Patent Application No. 2022-182134, filed on November 14, 2022. All of its contents are included here.

Claims

1. A receiving unit that receives downlink control information (DCI) including a field that indicates one or both of the first measurement reference signal (SRS) resource set and the second SRS resource set, corresponding to the first transmission setting instruction (TCI) state and the second TCI state, respectively. The system includes a control unit that determines, based on the aforementioned field, whether to apply the first TCI state, the second TCI state, or both the first and second TCI states to an uplink (UL) transmission, The UL transmission when both the first TCI state and the second TCI state are applied is a simultaneous UL transmission using multiple panels, in a terminal.

2. The process of receiving downlink control information (DCI) which includes a field indicating one or both of the first measurement reference signal (SRS) resource set and the second SRS resource set, corresponding to the first transmission setting instruction (TCI) state and the second TCI state, respectively. The process includes determining, based on the aforementioned field, whether to apply the first TCI state, the second TCI state, or both the first and second TCI states to the uplink (UL) transmission, A wireless communication method for a terminal, wherein the UL transmission when both the first TCI state and the second TCI state are applied is a simultaneous UL transmission using multiple panels.

3. A transmitting unit that transmits downlink control information (DCI) including a field that indicates one or both of the first measurement reference signal (SRS) resource set and the second SRS resource set, which correspond to the first transmission setting instruction (TCI) state and the second TCI state, respectively. The system includes a control unit that, based on the field, instructs whether to apply the first TCI state, the second TCI state, or both the first and second TCI states to an uplink (UL) transmission, The UL transmission when both the first TCI state and the second TCI state are applied is a simultaneous UL transmission using multiple panels, according to the base station.

4. A system having terminals and base stations, The aforementioned terminal is A receiving unit that receives downlink control information (DCI) including a field that indicates one or both of the first measurement reference signal (SRS) resource set and the second SRS resource set, corresponding to the first transmission setting instruction (TCI) state and the second TCI state, respectively. The system includes a control unit that determines, based on the aforementioned field, whether to apply the first TCI state, the second TCI state, or both the first and second TCI states to an uplink (UL) transmission, When both the first TCI state and the second TCI state are applied, the UL transmission is a simultaneous UL transmission using multiple panels. The aforementioned base station is A system having a transmitting unit that transmits the DCI.

Images