Terminal, wireless communication method, base station and system

Abstract

A terminal according to an embodiment of the present disclosure is characterized by including a receiving unit for receiving indication information relating to a plurality of transmission configuration indicator (TCI) states to be applied to a plurality of signals, and a control unit for applying the plurality of TCI states respectively to signals that utilize a plurality of transmission / reception points, on the basis of the indication information, wherein each of the plurality of TCI states is either a TCI state to be applied to both a downlink (DL) signal and an uplink (UL) signal, or is one of a TCI state to be applied to a DL signal and a TCI state to be applied to an UL signal. This embodiment of the present disclosure enables TCI state indication to be performed appropriately.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

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

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

[0008] A terminal according to one aspect of the present disclosure has a receiving unit that receives instruction information of multiple transmission configuration indication (TCI) states to be applied to multiple signals, and a control unit that applies the multiple TCI states to signals that use multiple transmission and reception points based on the instruction information, each of which is a TCI state that is applied to both a downlink (DL) signal and an uplink (UL) signal, or a TCI state that is applied to a DL signal and a TCI state that is applied to a UL signal.

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

[0010] 1A and 1B illustrate an example of communication between a mobile station and a transmission point (e.g., remote radio head). 2A to 2C illustrate an example of Schemes 0 to 2 for SFN. 3A and 3B illustrate an example of Scheme 1. 4A to 4C illustrate an example of a Doppler pre-compensation scheme. 5 illustrates an example of simultaneous beam updating across multiple CCs. 6A and 6B illustrate an example of common beams. 7A and 7B illustrate examples of single DCI-based multi-TRP transmission and multi-DCI-based multi-TRP transmission, respectively. 8A and 8B illustrate an example of a TCI field in a DCI. 9A and 9B illustrate an example of setting / indicating a joint TCI state in a single DCI-based multi-TRP. 10A and 10B illustrate an example of setting / indicating a separate TCI state in a single DCI-based multi-TRP. 11A and 11B are diagrams illustrating an example of setting / indicating a joint TCI state corresponding to a first value of the CORESET pool index in a multi-DCI-based multi-TRP. FIGS. 12A and 12B are diagrams illustrating an example of setting / indicating a joint TCI state corresponding to a second value of the CORESET pool index in a multi-DCI-based multi-TRP. FIGS. 13A and 13B are diagrams illustrating an example of a CC-specific TCI state pool and a CC-common TCI state pool, respectively. FIG. 14 is a diagram illustrating an example of setting a CC list according to aspect 1-2-B. FIG. 15 is a diagram illustrating another example of setting a CC list according to aspect 1-2-B. FIG. 16 is a diagram illustrating an example of determining a TCI state according to aspect 2-1 / 2-2. FIG. 17 is a diagram illustrating an example of determining a TCI state according to aspect 2-3. FIG. 18 is a diagram illustrating an example of determining a TCI state according to aspect 2-4. 19A and 19B are diagrams showing examples of joint ACK / NACK feedback and separate ACK / NACK feedback, respectively. Fig. 20 is a diagram showing an example of a PUCCH resource configuration method according to aspect 3-1. Fig. 21 is a diagram showing an example of a PUCCH resource configuration method according to aspect 3-2. Fig. 22 is a diagram showing an example of a PUCCH resource configuration method according to variant 1 of aspect 3-2.Fig. 23 is a diagram showing an example of a method for configuring PUCCH resources according to Variation 2 of Aspect 3-2. Fig. 24 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 25 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 26 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 27 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. Fig. 28 is a diagram showing an example of a vehicle according to an embodiment.

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

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

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

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

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

[0016] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

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

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

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

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

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

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

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

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

[0025] For the PDCCH and PDSCH, the QCL Type A RS is always configured, and the QCL Type D RS may be configured additionally. Since it is difficult to estimate Doppler shift, delay, etc. by one-shot reception of the DMRS, the QCL Type A RS is used to improve the accuracy of channel estimation. The QCL Type D RS is used to determine the receiving beam when receiving the DMRS.

[0026] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is notified as a QCL type C / D RS depending on the TCI status of the PDSCH. By notifying the TCI status, the UE can use information obtained from past periodic reception / measurement results of TRS1-1 for reception / channel estimation of the DMRS for the PDSCH. In this case, the QCL source of the PDSCH is TRS1-1, and the QCL target is the DMRS for the PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0046] Note that multiple TRPs may correspond to the same cell identifier (cell identifier (ID)) or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0047] Multi-TRPs (e.g., TRPs #1 and #2) may be connected by ideal / non-ideal backhauls to exchange information, data, etc. Each TRP of a multi-TRP may transmit a different code word (CW) and a different layer. Non-Coherent Joint Transmission (NCJT) may be used as a form of multi-TRP transmission.

[0048] In the NCJT, for example, TRP#1 modulates and layer-maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding, and TRP#2 modulates and layer-maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

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

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

[0051] Multiple PDSCHs from multiple TRPs (which may be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from multiple TRPs may be scheduled using multiple DCIs (multiple DCI, multiple PDCCHs) (multi-master mode, multi-DCI based multi-TRP).

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

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

[0054] In order to support multi-TRP transmission within a cell (with the same cell ID) and between cells (with different cell IDs) based on multiple PDCCHs, in the RRC configuration information for linking multiple pairs of PDCCHs and PDSCHs with multiple TRPs, one control resource set (CORESET) in the PDCCH configuration information (PDCCH-Config) may correspond to one TRP.

[0055] If at least one of the following conditions 1 and 2 is satisfied, the UE may determine that the transmission is a multi-TRP transmission based on the multi-DCI. In this case, the TRP may be replaced with the CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values ​​of the CORESET pool index (e.g., 0 and 1) are set.

[0056] If the following condition is met, the UE may determine that it is a multi-TRP based on a single DCI. In this case, two TRPs may be interpreted as two TCI states indicated by the MAC CE / DCI. [Condition] "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to indicate one or two TCI states for one codepoint in the TCI field in the DCI.

[0057] The DCI for common beam instruction may be a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)), or may be a UE-group common DCI format.

[0058] (Multi-TRP PDCCH) For the reliability of a multi-TRP PDCCH based on a non-single frequency network (SFN), the following considerations 1 to 3 are considered: [Consideration 1] Coding / rate matching is based on one repetition, and the same coded bits are repeated in other repetitions. [Consideration 2] Each repetition has the same number of control channel elements (CCEs), the same coded bits, and corresponds to the same DCI payload. [Consideration 3] Two or more PDCCH candidates are explicitly linked to each other. The UE knows the link before decoding.

[0059] The following options for PDCCH repetition are considered: 1-2, 1-3, 2, 3.

[0060] [Option 1-2] Two sets of PDCCH candidates (within a given search space (SS) set) are associated with two TCI states of the CORESET, respectively, where the same CORESET, the same SS set, and PDCCH repetitions on different monitoring occasions are used.

[0061] [Options 1-3] Two sets of PDCCH candidates are associated with two SS sets, respectively. Both SS sets are associated with a CORESET, and each SS set is associated with only one TCI state of that CORESET. Here, the same CORESET and two SS sets are used.

[0062] [Option 2] One SS set is associated with two different CORESETs.

[0063] [Option 3] Two SS sets are associated with two CORESETs, respectively.

[0064] In this way, it is considered that two PDCCH candidates in two SS sets for PDCCH repetition are supported and the two SS sets are explicitly linked.

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

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

[0067] In Rel. 17 and later, the following enhancements 1 and 2 regarding PDCCH / CORESET are being considered.

[0068] In the case where multiple antennas (small antennas, transmission / reception points) having the same cell ID form a single frequency network (SFN), up to two TCI states can be set / activated for one CORESET by higher layer signaling (RRC signaling / MAC CE) (Enhancement 1). SFN contributes to at least one of the operation and reliability improvement of HST (high speed train).

[0069] Furthermore, in repeated transmission of PDCCH (which may simply be referred to as "repetition"), two PDCCH candidates in two search space sets are linked, and each search space set is associated with a corresponding CORESET (Enhancement 2). The two search space sets may be associated with the same or different CORESETs. For one CORESET, one (maximum one) TCI state can be configured / activated by higher layer signaling (RRC signaling / MAC CE).

[0070] If two search space sets are associated with different CORESETs with different TCI states, this may mean a multi-TRP repeat transmission. If two search space sets are associated with the same CORESET (CORESET with the same TCI state), this may mean a single-TRP repeat transmission.

[0071] (HST) In LTE, placement of HST (high-speed train) in tunnels is difficult. Large antennas transmit both inside and outside the tunnel. For example, the transmission power of a large antenna is approximately 1 to 5 W. For handover purposes, it is important for the UE to transmit outside the tunnel before entering it. For example, the transmission power of a small antenna is approximately 250 mW. Multiple small antennas (transmitting and receiving points) with the same cell ID and a distance of 300 m form a single frequency network (SFN). All small antennas within the SFN transmit the same signal at the same time on the same PRB. It is assumed that a terminal transmits and receives signals to a single base station. In reality, multiple transmitting and receiving points transmit the same DL signal. When moving at high speed, transmitting and receiving points of several kilometers apart form a single cell. Handover occurs when crossing cells. This reduces the frequency of handovers.

[0072] In NR, it is assumed that a beam transmitted from a transmission point (e.g., RRH) is used to communicate with a terminal (hereinafter also referred to as a UE) included in a moving object (high speed train (HST)) such as a train moving at high speed. Existing systems (e.g., Rel. 15) support transmitting a unidirectional beam from an RRH to communicate with a moving object (see FIG. 1A).

[0073] 1A illustrates a case in which RRHs are installed along the moving path (or moving direction, traveling direction, or travel path) of a moving object, and a beam is formed from each RRH in the moving direction of the moving object. An RRH that forms a beam in one direction may be called a unidirectional RRH. In the example illustrated in FIG. 1A, the moving object receives a negative Doppler shift (−fD) from each RRH.

[0074] Here, we show a case where a beam is formed in the direction of travel of the moving body, but this is not limited to this, and a beam may be formed in the opposite direction to the direction of travel, or a beam may be formed in any direction regardless of the direction of travel of the moving body.

[0075] In Rel. 16 and later, it is assumed that multiple (e.g., two or more) beams are transmitted from the remote radio head (RRH). For example, it is assumed that beams are formed in both the moving direction of the mobile unit and the opposite direction (see FIG. 1B).

[0076] 1B shows a case where RRHs are installed along the movement path of the moving object, and each RRH forms a beam in both the moving direction of the moving object and the opposite direction of the moving direction. An RRH that forms beams in multiple directions (e.g., two directions) may be called a bi-directional RRH.

[0077] In this HST, the UE communicates as if it were a single TRP. In base station implementations, it is possible to transmit from multiple TRPs (same cell ID).

[0078] 1B, when two remote radio heads (RRH#1 and RRH#2) use SFN, the mobile station switches from a signal with a negative Doppler shift to a signal with a positive Doppler shift, which increases power, midway between the two remote radio heads. In this case, the maximum Doppler shift change range that requires correction is from −fD to +fD, which is twice as large as that in the case of unidirectional remote radio heads.

[0079] In the present disclosure, a positive Doppler shift may be interpreted as information about a positive Doppler shift, a Doppler shift in the positive (positive) direction, or Doppler information in the positive (positive) direction, and a negative Doppler shift may be interpreted as information about a negative Doppler shift, a Doppler shift in the negative (negative) direction, or Doppler information in the negative (negative) direction.

[0080] Here, as HST schemes, the following schemes 0 to 2 (HST scheme 0 to HST scheme 2) will be compared.

[0081] In scheme 0 of FIG. 2A, a tracking reference signal (TRS), a DMRS, and a PDSCH are transmitted in common (using the same time and frequency resources) to two TRPs (RRHs) (normal SFN, transparent SFN, HST-SFN).

[0082] In scheme 0, the UE receives DL channels / signals equivalent to a single TRP, so there is one TCI state for the PDSCH.

[0083] In addition, Rel. 16 specifies an RRC parameter for distinguishing between transmissions using a single TRP and transmissions using an SFN. When a UE reports corresponding UE capability information, the UE may distinguish between reception of a DL channel / signal using a single TRP and reception of a PDSCH assuming an SFN based on the RRC parameter. On the other hand, the UE may also perform transmission and reception using an SFN assuming a single TRP.

[0084] In Scheme 1 of Figure 2B, TRSs are transmitted TRP-specifically (using different time / frequency resources depending on the TRP). In this example, TRS1 is transmitted from TRP#1 and TRS2 is transmitted from TRP#2.

[0085] In Scheme 1, there are two TCI states for the PDSCH since the UE receives DL channels / signals from each TRP using TRS from each TRP.

[0086] In Scheme 2 of FIG. 2C, TRS and DMRS are transmitted individually for each TRP. In this example, TRS1 and DMRS1 are transmitted from TRP#1, and TRS2 and DMRS2 are transmitted from TRP#2. Compared to Scheme 0, Schemes 1 and 2 can suppress sudden changes in Doppler shift and appropriately estimate / compensate for Doppler shift. Because the DMRS in Scheme 2 is increased more than that in Scheme 1, the maximum throughput of Scheme 2 is lower than that of Scheme 1.

[0087] In Scheme 0, the UE switches between single TRP and SFN based on higher layer signaling (RRC information element / MAC CE).

[0088] The UE may switch between Scheme 1 / Scheme 2 / NW pre-compensation schemes based on higher layer signaling (RRC information elements / MAC CE).

[0089] In Scheme 1, two TRS resources are set for the HST's forward direction and its reverse direction, respectively.

[0090] In the example of Figure 3A, the TRPs (TRPs #0, #2, ...) transmitting DL signals in the direction opposite to the HST transmit a first TRS (a TRS arriving before the HST) in the same time and frequency resource (SFN). The TRPs (TRPs #1, #3, ...) transmitting DL signals in the direction of travel of the HST transmit a second TRS (a TRS arriving after the HST) in the same time and frequency resource (SFN). The first TRS and the second TRS may be transmitted / received using different frequency resources.

[0091] In the example of FIG. 3B, TRS1-1 to 1-4 are transmitted as the first TRS, and TRS2-1 to 2-4 are transmitted as the second TRS.

[0092] Considering beam operation, the first TRS is transmitted using 64 beams and 64 time resources, and the second TRS is transmitted using 64 beams and 64 time resources. The beams of the first TRS and the beams of the second TRS are considered to be equal (the QCL Type D RSs are equal). By multiplexing the first TRS and the second TRS into the same time resource but different frequency resource, resource utilization efficiency can be improved.

[0093] In the example of Fig. 4A, RRHs #0-#7 are arranged along the movement path of the HST. RRHs #0-#3 and RRHs #4-#7 are connected to baseband units (BBU) #0 and #1, respectively. Each RRH is a bidirectional RRH, and forms beams in both the direction of travel of the movement path and the opposite direction using each transmission / reception point (TRP).

[0094] In the received signal of the example of Figure 4B (Single TRP (SFN) / Scheme 1), when the UE receives a signal / channel (a beam in the direction of travel of the HST, a beam from behind the UE) transmitted from TRP #2n-1 (n is an integer greater than or equal to 0), a negative Doppler shift (-fD in this example) occurs. Also, when the UE receives a signal / channel (a beam in the direction opposite to the direction of travel of the HST, a beam from in front of the UE) transmitted from TRP #2n (n is an integer greater than or equal to 0), a positive Doppler shift (+fD in this example) occurs.

[0095] In Rel. 17 and later, a Doppler pre-compensation scheme (pre-Doppler compensation scheme, Doppler pre-compensation scheme, network (NW) pre-compensation scheme, HST NW pre-compensation scheme, TRP pre-compensation scheme, TRP-based pre-compensation scheme) is being considered for a base station to use when transmitting a downlink (DL) signal / channel from a TRP to a UE in an HST. By performing Doppler compensation in advance when transmitting a DL signal / channel to a UE, the TRP can reduce the effect of Doppler shift when the UE receives the DL signal / channel. In the present disclosure, the Doppler pre-compensation scheme may be a combination of Scheme 1 and Doppler shift pre-compensation by the base station.

[0096] In the Doppler pre-compensation scheme, it is being considered that the TRS from each TRP is transmitted without Doppler pre-compensation, and the PDSCH from each TRP is transmitted with Doppler pre-compensation.

[0097] In the Doppler pre-compensation scheme, the TRPs that form beams in the direction of travel and the TRPs that form beams in the opposite direction of travel perform Doppler compensation before transmitting DL signals / channels to UEs within the HST. In this example, TRP #2n-1 performs positive Doppler compensation, and TRP #2n performs negative Doppler compensation to reduce the effect of Doppler shift when the UE receives the signal / channel (Figure 4C).

[0098] Note that in the situation of Figure 4C, there may be two TCI states for the PDSCH, since the UE receives DL channels / signals from each TRP using TRS from each TRP.

[0099] Furthermore, in Rel. 17 and later, dynamic switching between single-TRP and SFN using the TCI field (TCI state field) is being considered. For example, one or two TCI states are configured / indicated at each TCI code point (TCI field code point, DCI code point) using an RRC information element / MAC CE (e.g., Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) / DCI (TCI field). A UE may determine to receive a single-TRP PDSCH when one TCI state is configured / indicated. Alternatively, a UE may determine to receive a multi-TRP SFN PDSCH when two TCI states are configured / indicated.

[0100] (Simultaneous Beam Update of Multiple CCs) In Rel. 16, one MAC CE can update the beam index (TCI state) of multiple CCs.

[0101] The UE can be configured with up to two applicable CC lists (e.g., applicable-CC-list) by RRC. When two applicable CC lists are configured, the two applicable CC lists may correspond to in-band CA in FR1 and in-band CA in FR2, respectively.

[0102] The PDCCH TCI state activation MAC CE activates the TCI states associated with the same CORESET ID on all BWP / CCs in the applicable CC list.

[0103] Activation of TCI State for PDSCH The MAC CE activates the TCI state on all BWP / CCs in the applicable CC list.

[0104] A-SRS / SP-SRS Spatial Relationship Activation The MAC CE activates the spatial relationships associated with the same SRS resource ID on all BWPs / CCs in the applicable CC list.

[0105] In the example of Figure 5, the UE is configured with an applicable CC list indicating CCs #0, #1, #2, and #3, and a list indicating 64 TCI states for CORESET or PDSCH of each CC. If one TCI state of CC #0 is activated by a MAC CE, the corresponding TCI state is activated in CCs #1, #2, and #3.

[0106] Such simultaneous beam updating is considered applicable only to the single TRP case.

[0107] For PDSCH, the UE may follow the procedure A. [Procedure A] The UE receives an activation command to map up to eight TCI states to codepoints of the DCI field (TCI field) within one CC / DL BWP or within one set of CCs / BWPs. If one set of TCI state IDs is activated for one set of CCs / DL BWPs, then the applicable list of CCs is determined by the CC indicated in the activation command, and the same set of TCI states applies to all DL BWPs within the indicated CCs. Only if the UE is not provided with different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states, can one set of TCI state IDs be activated for one set of CC / DL BWPs.

[0108] For PDCCH, the UE may follow procedure B. [Procedure B] If the UE is provided with up to two lists of cells for simultaneous TCI state activation by the simultaneous TCI cell list (simultaneousTCI-CellList) via the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList-r16 and simultaneousTCI-UpdateListSecond-r16), the UE shall apply antenna port quasi co-location (QCL) provided by TCI states with the same activated TCI state ID value to CORESET with index p in all configured DL BWPs of all configured cells in one list determined from the serving cell index provided by the MAC CE command. A simultaneous TCI cell list can be provided for simultaneous TCI state activation only if the UE is not provided with multiple different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states.

[0109] For semi-persistent (SP) / aperiodic (AP)-SRS, the UE may follow procedure C. [Procedure C] When spatial relation information (spatialRelationInfo) for SP or AP-SRS resources configured by the SRS resource information element (higher layer parameter SRS-Resource) for one set of CCs / BWPs is activated / updated by MAC CE, where the applicable list of CCs is indicated by the simultaneous spatial update list (higher layer parameter simultaneousSpatial-UpdateList-r16 or simultaneousSpatial-UpdateListSecond-r16), the spatial relation information is applied to SP or AP-SRS resources with the same SRS resource ID in all BWPs within the indicated CC. The spatial relation information (spatialRelationInfo) for the SP or AP-SRS resources configured by the SRS resource information element (higher layer parameter SRS-Resource) for one set of CCs / BWPs is activated / updated by the MAC CE only if the UE is not provided with different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states.

[0110] The simultaneous TCI cell list (simultaneousTCI-CellList) and the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16) are lists of serving cells whose TCI relationships can be updated simultaneously using MAC CE. simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16 do not include the same serving cell.

[0111] The simultaneous spatial update list (at least one of the upper layer parameters simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16) is a list of serving cells whose spatial relationships can be updated simultaneously using MAC CE. simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16 do not include the same serving cell.

[0112] Here, the simultaneous TCI update list and the simultaneous spatial update list are configured by the RRC, the CORESET pool index of the CORESET is configured by the RRC, and the TCI code point mapped to the TCI state is indicated by the MAC CE.

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

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

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

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

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

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

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

[0120] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / instructed to the UE.

[0121] Furthermore, when N=X (X is any integer) and M=Y (Y is any integer, Y may be X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) are notified / configured / indicated to the UE. The UL TCI state and the DL TCI state may mean a TCI state common to the UL and DL (i.e., a joint TCI state), or may mean a TCI state for each of the UL and DL (i.e., a separate TCI state).

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

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

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

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

[0126] Furthermore, for example, when N=2 and M=1, this may mean that two TCI states common to the UL and DL are notified / configured / instructed to the UE. In this case, the UE may use the two configured / instructed TCI states as UL TCI states and use one TCI state of the two configured / instructed TCI states as a DL TCI state.

[0127] Also, for example, when N=2 and M=1, this may mean that two UL TCI states and one DL TCI state are notified / configured / instructed to the UE as separate TCI states.

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

[0129] The case where M>1 / N>1 may indicate at least one of TCI status indications for multiple TRPs and multiple TCI status indications for inter-band CA.

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

[0131] In the example of FIG. 6A, a point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL, respectively.

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

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

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

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

[0136] The existing DCI formats 1_1 / 1_2 may be used to indicate the common TCI state.

[0137] The DCI format indicating the TCI status may be a specific DCI format, for example, DCI format 1_1 / 1_2 (defined in Rel. 15 / 16 / 17).

[0138] The DCI format (DCI format 1_1 / 1_2) indicating the TCI state may be a DCI format without a DL assignment. In the present disclosure, the DCI format may be interchangeably referred to as a DCI format without a DL assignment, a DCI format (DCI format 1_1 / 1_2) that does not schedule a PDSCH, a DCI format (DCI format 1_1 / 1_2) that does not include one or more specific fields, or a DCI format (DCI format 1_1 / 1_2) in which one or more specific fields are set to fixed values.

[0139] For a DCI format without DL assignment (a DCI format that does not include one or more specific fields), the specific fields may be fields other than the TCI field, the DCI format identifier field, the carrier indicator field, the bandwidth portion (BWP) indicator field, the Time Domain Resource Assignment (TDRA) field, the Downlink Assignment Index (DAI) field (if configured), the Transmission Power Control (TPC) command field (for the scheduled PUCCH), the PUCCH resource indicator field, and the PDSCH-to-HARQ feedback timing indicator field (if present). The specific fields may be set as reserved fields or ignored.

[0140] For DCI formats without DL assignment (DCI formats in which one or more specific fields are set to fixed values), the specific fields may be a Redundancy Version (RV) field, a Modulation and Coding Scheme (MCS) field, a New Data Indicator field, and a Frequency Domain Resource Assignment (FDRA) field.

[0141] The RV field may be set to all ones. The MCS field may be set to all ones. The NDI field may be set to zero. The FDRA field of type 0 may be set to all zeros. The FDRA field of type 1 may be set to all ones. The FDRA field for dynamic switch (higher layer parameter dynamicSwitch) may be set to all zeros.

[0142] A common TCI framework may have separate TCI states for DL ​​and UL.

[0143] (Analysis) The TCI state introduced in Rel. 17 (Rel. 17 TCI state, common TCI state) is considered to indicate one TCI state (M=1, N=1, or M=N=1). In other words, the Rel. 17 TCI state is considered to be applicable to situations using a single TRP.

[0144] It is being considered that the TCI states / spatial relationships defined up to Rel. 15 / 16 (excluding TCI states related to positioning reference signals) and the Rel. 17 TCI states will not be set in the same band.

[0145] In this case, features (e.g., operations using multiple TRPs) that use the Rel. 15 / 16 TCI state / spatial relationship defined in Rel. 15 through Rel. 17 cannot be configured in the same band as the Rel. 17 TCI state.

[0146] Therefore, there is a need to extend the common TCI states (Rel. 17 TCI states) to support features using Rel. 15 / 16 TCI state / spatial relationships, including multi-TRP schemes (e.g., using MAC CE / DCI to indicate more than one TCI state).

[0147] For example, in Rel. 18 and later, it is being considered to make the common TCI state applicable to at least one of the multi-TRP schemes specified in Rel. 16 / 17, such as: ・Single DCI-based NCJT PDSCH (Rel. 16) ・Multiple DCI-based NCJT PDSCH (Rel. 16) ・Single DCI-based SDM / TDM / FDM PDSCH repeat transmission (Rel. 16) ・Multiple TRP-based PDCCH / PUCCH / PUSCH repeat transmission (Rel. 17) ・Inter-cell operation for multi-TRP (Rel. 17) ・Beam management for multi-TRP (Rel. 17) ・HST / SFN (Rel. 17)

[0148] Furthermore, the extension of the common TCI state may be used for beam indication in inter-band carrier aggregation, in which one or more TCI states of different bands may be indicated using one MAC CE / DCI.

[0149] However, in the transmission and reception of signals / channels using multi-TRP, the setting / indication / application of a common TCI state has not been sufficiently considered. If the setting / indication / application method of the TCI state is not sufficiently considered, it may lead to a deterioration in communication quality, a deterioration in throughput, etc.

[0150] Therefore, the inventors have come up with a method for appropriately setting / indicating / applying TCI states when transmitting and receiving signals / channels using multi-TRP, even when the TCI state is applied to multiple types of signals / channels.

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

[0152] In the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, sequence, list, set, group, group, cluster, subset, etc. may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0153] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0154] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), RRC messages, and settings may be read interchangeably.

[0155] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. In the present disclosure, the MAC CE, an update command, and an activation / deactivation command may be read interchangeably.

[0156] The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI, SIB1), Other System Information (OSI), etc.

[0157] In the present disclosure, beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D for TCI state / QCL assumption, RS of QCL type A for TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be read interchangeably. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be read interchangeably.

[0158] In the present disclosure, the terms panel, UE panel, panel group, antenna group, UE capability value, UE capability value set, specific (pool) index included in PUSCH configuration, specific (pool) index included in PUCCH configuration, specific (pool) index included in SRS configuration, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CONTROLLER RESEARCH SET ... 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), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc.The UE capability value set may include, for example, the maximum number of supported SRS ports.

[0159] The panel may be associated with at least one of a group index of an SSB / CSI-RS group, a group index of a group-based beam report, and a group index of an SSB / CSI-RS group for group-based beam reporting.

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

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

[0162] In this disclosure, the terms "single TRP," "single TRP system," "single TRP transmission," and "single PDSCH" may be interchangeable. In this disclosure, the terms "multiple TRP," "multiple TRP system," "multiple TRP transmission," and "multiple PDSCH" may be interchangeable. In this disclosure, the terms "single DCI," "single PDCCH," "multiple TRP based on a single DCI," and "activating two TCI states on at least one TCI codepoint" may be interchangeable.

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

[0164] In the present disclosure, "multi-TRP," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

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

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

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

[0168] The QCL in the present disclosure may be interchangeably read as QCL Type D.

[0169] In the present disclosure, expressions such as "TCI state A is of QCL type D, the same as TCI state B," "TCI state A is the same as TCI state B," and "TCI state A is of QCL type D with TCI state B" may be interpreted interchangeably.

[0170] In the present disclosure, the code point of the DCI field 'Transmission Configuration Indication', the TCI code point, the DCI code point, and the code point of the TCI field may be read interchangeably.

[0171] In the present disclosure, the terms "single TRP" and "SFN" may be interchangeable. In the present disclosure, the terms "HST," "HST scheme," "high speed mobility scheme," "scheme 1," "scheme 2," "NW pre-compensation scheme," "HST scheme 1," "HST scheme 2," and "HST NW pre-compensation scheme" may be interchangeable.

[0172] In the present disclosure, a PDSCH / PDCCH using a single TRP may be interpreted as a PDSCH / PDCCH based on a single TRP, or a single TRP PDSCH / PDCCH. Also, in the present disclosure, a PDSCH / PDCCH using an SFN may be interpreted as a PDSCH / PDCCH using an SFN in multi-mode, a PDSCH / PDCCH based on an SFN, or an SFN PDSCH / PDCCH.

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

[0174] In the present disclosure, at least one of the following terms may be interchangeable: HST-SFN scheme, SFN scheme for Rel. 17 or later, new SFN scheme, new HST-SFN scheme, HST-SFN scenario for Rel. 17 or later, HST-SFN scheme for HST-SFN scenario, SFN scheme for HST-SFN scenario, scheme 1, HST-SFN scheme A / B, HST-SFN type A / B, Doppler pre-compensation scheme, scheme 1 (HST scheme 1), and Doppler pre-compensation scheme.

[0175] In the present disclosure, the terms Doppler pre-compensation scheme, base station pre-compensation scheme, TRP pre-compensation scheme, pre-Doppler compensation scheme, Doppler pre-compensation scheme, NW pre-compensation scheme, HST NW pre-compensation scheme, TRP pre-compensation scheme, TRP-based pre-compensation scheme, HST-SFN scheme A / B, and HST-SFN type A / B may be interchangeable. In the present disclosure, the terms pre-compensation scheme, reduction scheme, improvement scheme, and correction scheme may be interchangeable.

[0176] In the present disclosure, a PDCCH / search space (SS) / CORESET with linkage, a linked PDCCH / SS / CORESET, and a PDCCH / SS / CORESET pair may be interchangeable. In the present disclosure, a PDCCH / SS / CORESET without linkage, an unlinked PDCCH / SS / CORESET, and a standalone PDCCH / SS / CORESET may be interchangeable.

[0177] In the present disclosure, two linked CORESETs for PDCCH repetition, two CORESETs respectively associated with two linked SS sets, may be read as interchangeable.

[0178] In the present disclosure, SFN-PDCCH repetition, PDCCH repetition, two linked PDCCHs, and one DCI being received across the two linked search spaces (SS) / CORESETs may be read interchangeably.

[0179] In the present disclosure, PDCCH repetition, SFN-PDCCH repetition, PDCCH repetition for higher reliability, PDCCH for higher reliability, PDCCH for reliability, and two linked PDCCHs may be read as interchangeable.

[0180] In the present disclosure, the terms PDCCH reception method, PDCCH repetition, SFN-PDCCH repetition, HST-SFN, and HST-SFN scheme may be read interchangeably.

[0181] In the present disclosure, the PDSCH reception method, single DCI-based multi-TRP, and HST-SFN scheme may be interchangeable.

[0182] In the present disclosure, the single DCI-based multi-TRP repetition may be an NCJT of an enhanced mobile broadband (eMBB) service (low priority, priority 0) or a repetition of a URLLC service (high priority, priority 1) of an ultra-reliable and low latency communications service.

[0183] In each embodiment of the present disclosure, a PDSCH for multiple TRPs based on a single DCI may be interchangeably read as a PDSCH to which TDM / FDM / SDM for multiple TRPs (as defined in Rel. 16) is applied.

[0184] In each embodiment of the present disclosure, the PDSCH for multiple TRPs may be interchangeably read as the PDSCH to which TDM / FDM / SDM for multiple TRPs based on a single DCI (specified in Rel. 16) is applied.

[0185] In each embodiment of the present disclosure, PUSCH / PUCCH / PDCCH for multiple TRPs based on a single DCI may be interchangeably read as repeated transmission (repetition) of PUSCH / PUCCH / PDCCH for multiple TRPs (defined in Rel. 17 and later).

[0186] In each embodiment of the present disclosure, the SFN PDSCH / PDCCH may be interchangeably read as the SFN PDSCH / PDCCH defined in Rel. 17 and later.

[0187] In each embodiment of the present disclosure, configuring the use of multiple TRPs based on multiple DCIs may mean setting a CORESET pool index of 1. Also, configuring the use of multiple TRPs based on multiple DCIs may mean setting two different CORESET pool index values ​​(e.g., 0 and 1).

[0188] In each embodiment of the present disclosure, UL transmission using multiple panels may refer to a UL transmission scheme using multiple panels of a UE with DCI enhancement.

[0189] In each embodiment of the present disclosure, if a joint TCI state / separate TCI state in the unified TCI state framework is not applicable to each channel / signal, the aforementioned default TCI state / QCL / spatial relationship may be used to determine the TCI state / QCL / spatial relationship of each channel.

[0190] The following embodiments of the present disclosure may be applied to transmission and reception of any channel / signal that is subject to the unified TCI state framework defined in the above-mentioned Rel. 17 and later.

[0191] In the present disclosure, applying a TCI state to each channel / signal / resource may mean applying the TCI state to transmission and reception of each channel / signal / resource.

[0192] In the present disclosure, small, few, short, and low may be read as interchangeable. Also, in the present disclosure, ignore, drop, etc. may be read as interchangeable.

[0193] In the present disclosure, the terms "highest (maximum)" and "lowest (minimum)" may be interpreted interchangeably. Also, in the present disclosure, "maximum" may be interpreted interchangeably as "the nth (n is any natural number)" larger, larger, higher, etc. Also, in the present disclosure, "minimum" may be interpreted interchangeably as "the nth (n is any natural number) smallest," smaller, lower, etc.

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

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

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

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

[0198] In each embodiment of the present disclosure below, the application of multiple TCI states in transmission and reception using multiple TRPs will be mainly described, focusing on a method targeting two TRPs, but the number of TRPs may be three or more (multiple), and each embodiment may be applied to correspond to the number of TRPs.

[0199] (Wireless Communication Method) <Tenth Embodiment> Single DCI-based multi-TRP may be assumed to be supported when multi-TRP utilizes an ideal backhaul (see FIG. 7A).

[0200] In this case, one beam indication DCI may indicate multiple (e.g., up to two) TCI states for each TRP.

[0201] In the present disclosure, one TCI state may mean one joint (DL / UL) TCI state, or may mean at least one of one DL (separate) TCI state and one UL (separate) TCI state.

[0202] Multi-PDCCH (DCI) may be assumed to be supported when multi-TRPs utilize ideal / non-ideal backhaul (see FIG. 7B).

[0203] In this case, one DCI associated with one TRP (CORESET pool index) may indicate the TCI state corresponding to the TRP.

[0204] The ideal backhaul may be called DMRS port group type 1, reference signal related group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may be called DMRS port group type 2, reference signal related group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

[0205] The field indicating the TCI status (TCI field) included in the DCI may follow at least one of the following options 0-1 and 0-2.

[0206] [Option 0-1] The TCI field defined up to Rel. 15 / 16 may be reused (see Figure 8A). As shown in Figure 8A, one TCI field may be included in the DCI. The number of bits in the TCI field may be a specific number (e.g., 3).

[0207] [Option 0-2] The TCI field defined in Rel. 15 / 16 may be extended (see FIG. 8B). For example, the DCI may include multiple TCI fields (e.g., two). The number of bits in each TCI field may be a specific number (e.g., three).

[0208] In options 0-2, no DCI overhead is added for DCIs without DL assignments, while DCI overhead is added for DCIs with DL assignments.

[0209] For single DCI-based multi-TRP, in the case of joint TCI states, the DL / UL (joint) TCI state may be activated for the UE using MAC CE, and the UE may then be indicated the first DL / UL (joint) TCI state and the second DL / UL (joint) TCI state using DCI (beam indication) (see Figure 9A).

[0210] The TCI code point indicated by the beam indication may correspond to one or more (two) TCI states (first joint TCI state / second joint TCI state) (see FIG. 9B).

[0211] In the example shown in Figure 9B, all TCI code points corresponding to the active TCI state correspond to two TCI states, but an association may be used in which at least one TCI code point corresponding to the active TCI state corresponds to two TCI states. By using such an association, it is possible to dynamically switch between single TRP and multi-TRP.

[0212] For single DCI-based multi-TRP, in the case of separate TCI states, the DL (separate) TCI state and the UL (separate) TCI state may be activated for the UE using a MAC CE. The UE may then be indicated the first DL (separate) TCI state and the first UL (separate) TCI state and the second DL (separate) TCI state and the second UL (separate) TCI state using a DCI (beam indication) (see FIG. 10A).

[0213] The TCI code point indicated by the beam indication may correspond to one or more (two) TCI states (first separate (DL / UL) TCI state / second separate (DL / UL) TCI state) (see Figure 10B).

[0214] In the example shown in Figure 10B, all TCI code points corresponding to the active TCI state correspond to two TCI states (first separate (DL / UL) TCI state / second separate (DL / UL) TCI state), but an association may be used in which at least one TCI code point corresponding to the active TCI state corresponds to two TCI states. By using such an association, it is possible to dynamically switch between single TRP and multi-TRP.

[0215] Note that, in FIG. 10A , an example is shown in which separate TCI states are activated for the DL TCI state and the UL TCI state with respect to the TCI state activated by the MAC CE. However, even in the case of separate TCI states, the activated DL TCI state and the UL TCI state may include a common TCI state.

[0216] For multi-DCI based multi-TRP, the TCI state may be configured by RRC, activated by MAC CE, and / or indicated by DCI per CORESET pool index.

[0217] For multi-DCI based multi-TRP, in case of joint TCI state, the TCI state may be configured by RRC, activated by MAC CE, and indicated by DCI to the UE for a CORESET pool index of a first value (e.g., 0) (see Figure 11A). The indicated TCI state corresponding to the CORESET pool index of the first value may be referred to as the first TCI state.

[0218] The TCI code point indicated by the beam indication may correspond to one TCI state (first joint TCI state) (see FIG. 11B).

[0219] For multi-DCI based multi-TRP, in case of joint TCI state, the TCI state may be configured by RRC, activated by MAC CE, and indicated by DCI to the UE for a CORESET pool index of a second value (e.g., 1) (see Figure 12A). The indicated TCI state corresponding to the CORESET pool index of the second value may be referred to as the second TCI state.

[0220] The TCI code point indicated by the beam indication may correspond to one TCI state (second joint TCI state) (see FIG. 12B).

[0221] When the DCIs corresponding to each CORESET pool index indicate the same TCI state (TCI state ID) (for example, when TCI state #7 corresponding to TCI code point "111" in Figures 11B and 12B is indicated), the UE may determine that one TCI state is indicated. In this case, the UE may operate using a single TRP.

[0222] Although the above multi-DCI based multi-TRP has been described as an example using a joint TCI state, it can also be applied appropriately to cases using a separate TCI state.

[0223] In this disclosure, the terms indicated TCI state, Rel. 17 TCI state, common TCI state, and unified TCI state may be interchangeable. In this disclosure, the terms common TCI state, Rel. 17 TCI state, and Rel. 18 TCI state that apply to channels / signals that utilize multiple TRPs may be interchangeable.

[0224] The UE may apply the indicated TCI state to a particular channel / signal.

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

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

[0227] One or more (eg, two) indicated TCI states may be indicated based on the method described in the 0th embodiment above.

[0228] First Embodiment In the first embodiment, application of TCI states and the number of TCI states to be set / activated when at least one of M and N is 2 or more will be described.

[0229] The UE may apply up to M and / or N TCI states (joint TCI states, separate (DL / UL) TCI states) to DL / UL channels / signals.

[0230] The UE may be configured / instructed to have at least one of a maximum of M and N (e.g., M and N are numbers greater than or equal to 2) TCI states (joint TCI states, separate (DL / UL) TCI states).

[0231] At this time, the UE may be configured with a channel / RS / resource / resource set corresponding to the index related to the TRP.

[0232] The index related to the TRP may be interchangeably read as a TRP index, a CORESET pool index, a (UE) panel index, or a UE Capability Set index.

[0233] Different panel indices may correspond to different numbers of antenna ports. When performing beam reporting, the UE may report a corresponding panel index for each beam (report).

[0234] The first / second index of the index related to the TRP may be interchangeably read as the first / second set ID and the first / second TCI state in a single DCI-based multi-TRP.

[0235] The first / second index of the index related to the TRP may be read interchangeably as the first / second value CORESET pool index in a multi-DCI based multi-TRP.

[0236] For each channel / RS / resource / resource set of DL / UL channels / RSs that can share Rel. 17 TCI states, whether one or more (e.g., two) indicated TCI states apply may be configured / indicated to the UE.

[0237] The setting / indication may be configured / indicated, for example, in a scenario using inter-cell multi-TRP. The setting / indication may be based on a report of corresponding UE capability information. In this case, the source RS for the TCI state may be an RS (e.g., SSB) associated with a PCI (additional PCI) different from the physical cell index (PCI) of the serving cell. Whether the source RS for the SSB associated with such an additional PCI can be applied to the UL TCI state (e.g., N) may be independently configured for the UE.

[0238] The UE may directly configure / instruct the PCI value for the PCI, or may configure / instruct the PCI with a re-indexed index within the configured PCI list.

[0239] <<Aspect 1-1>> In aspect 1-1, the maximum number of TCI states set for a UE will be described.

[0240] The UE may apply M DL TCI states and / or N UL TCI states (or M (N, where M=N) joint TCI states), where M and N may be 2 or greater than 2.

[0241] In this disclosure, the case where at least one of M and N is greater than 1 is described as (M, N)>1. Also, in this disclosure, the case where M and N are 1 is described as (M, N)=1.

[0242] In this case, the maximum number of joint TCI states configured for a UE may be a specific number (for example, a number specified in Rel. 17 (for example, 128)).

[0243] In this case, the maximum number of separate DL TCI states configured for the UE may be a specific number (for example, a number specified in Rel. 17 (for example, 128)).

[0244] In this case, the maximum number of separate UL TCI states configured for the UE may be a specific number (for example, a number specified in Rel. 17 (for example, 64)).

[0245] In this case, the number of joint / separate TCI states configured for the UE may be greater than the number specified in Rel. 17. For example, the number of joint / separate TCI states configured for the UE may be the number specified in Rel. 17.

[0246] In addition, in aspect 1-1, the set joint / separate TCI state may be interpreted as an activated joint / separate TCI state and an active joint / separate TCI state, respectively.

[0247] The (maximum) number of configured / activated TCI states for joint / separate TCI states in the case (M, N)>1 may be limited to a specific number.

[0248] For example, the number of configured / activated TCI states for joint / separate TCI states in the case of (M, N)>1 may be limited to the number of configured / activated TCI states for joint / separate TCI states with (M, N)=1 reported using UE capability information in Rel.

[0249] For example, the number of configured / activated TCI states for joint / separate TCI states in the case of (M, N) > 1 may be limited to the number of configured / activated TCI states for joint / separate TCI states in the case of (M, N) > 1 reported using the UE capability information in Rel.

[0250] In addition, the number of TCI states to be set / activated in this aspect may be determined for each BWP (setting).

[0251] Example 1-2 In example 1-2, a list of CCs / BWPs configured in a UE will be described.

[0252] In CA under the unified TCI framework of Rel. 17, it is considered that CC-specific TCI state pools / configurations (Case 1) and CC-common TCI state pools / configurations (Case 2) will be supported.

[0253] (Case 1) Figure 13A shows an example of a CC-specific TCI status pool, in which a TCI status list in a PDSCH configuration is configured for BWP1 in CC1, and a TCI status list in a PDSCH configuration is configured for BWP1 in CC2.

[0254] (Case 2) Figure 13B shows an example of a CC common TCI status pool. In this example, a TCI status list in the PDSCH configuration is set for BWP1 in CC1, and a TCI status list in the PDSCH configuration is not set (absent) for BWP1 in CC2.

[0255] The UE may refer to a TCI status pool configured in another specific BWP / CC (reference BWP / CC) to determine the TCI status of a BWP / CC for which a TCI status pool is not configured.

[0256] The UE may perform the TCI status pool lookup according to at least one of aspects 1-2-A and 1-2-B described below.

[0257] In the following embodiments, the "CC" will be mainly described, but the "CC" may be appropriately read as "BWP".

[0258] [Aspect 1-2-A] A UE may be configured with a CC list including multiple CCs using higher layer signaling (RRC signaling).

[0259] In order to determine the TCI state of a CC for which a TCI state pool is not configured, the UE may determine a CC for which a TCI state pool is configured (reference BWP / CC) among the multiple CCs. The UE may determine / update / apply the TCI state of the CC for which a TCI state pool is not configured by referring to the TCI state pool configured for the determined CC.

[0260] This CC list may be used to configure the TCI state pool in the above case 2. This CC list may also be used to update / indicate the (unified) TCI state (ID) using MAC CE / DCI.

[0261] The CC list may indicate all CCs in the same band.

[0262] [Aspect 1-2-B] A UE may be configured with a CC list including multiple CCs using higher layer signaling (RRC signaling).

[0263] The UE may be configured with a first CC list that is used to update / indicate the (unified) TCI state (ID) using MAC CE / DCI.

[0264] The first CC list may, for example, indicate all CCs in the same band.

[0265] The UE may be configured with a second CC list that is used to configure the TCI status pool in case 2 above.

[0266] In order to determine the TCI state of a CC for which a TCI state pool is not configured, the UE may determine a CC for which a TCI state pool is configured (reference BWP / CC) among multiple CCs included in the second CC list. The UE may determine / update / apply the TCI state of the CC for which a TCI state pool is not configured by referring to the TCI state pool configured for the determined CC.

[0267] A specific number of the second CC lists may be set for each cell / cell group, and the specific number may be, for example, up to 4. The specific number may be determined based on the reported UE capability information.

[0268] Fig. 14 is a diagram showing an example of CC list configuration according to aspect 1-2-B. Fig. 14 illustrates the above-mentioned case 1. In the example shown in Fig. 14, a TCI status pool (list) is configured for each of CC #1 (BWP #1 in CC #1), CC #2 (BWP #1 in CC #2), and CC #3 (BWP #1 in CC #3). The TCI status list is configured within the PDSCH configuration.

[0269] In the example shown in Fig. 14, a first CC list used for updating / indicating the (unified) TCI state (ID) using MAC CE / DCI is configured for the UE. The first CC list includes a list (first CC list #1) including CC #1 (with BWP #1) and CC #2 (with BWP #1), and a list (first CC list #2) including CC #3 (with BWP #1).

[0270] In the example shown in Figure 14, the UE is instructed by the MAC CE / DCI of the TCI state ID (here, TCI state #2) for CC #1 (at BWP #1) and CC #2 (at BWP #1) based on the first CC list, and is also instructed by the MAC CE / DCI of the TCI state ID (here, TCI state #4) for CC #3 (at BWP #1).

[0271] Note that a plurality of first CC lists may be set. In the example shown in Fig. 14, a plurality of first CC lists are set.

[0272] Furthermore, the indication of the TCI state IDs in CC #1 (BWP #1 therein) and CC #2 (BWP #1 therein) and the indication of the TCI state ID in CC #3 (BWP #1 therein) may be performed by separate MAC CE / DCIs, or may be performed by a common MAC CE / DCI.

[0273] Fig. 15 is a diagram showing another example of CC list configuration according to aspect 1-2-B. Fig. 15 illustrates the above-mentioned case 2. In the example shown in Fig. 15, a TCI status pool (list) is configured for CC #1 (BWP #1 therein), and a TCI status pool (list) is not configured for CC #2 (BWP #1 therein) and CC #3 (BWP #1 therein). The TCI status list is configured within the PDSCH configuration.

[0274] In the example shown in Fig. 15, a first CC list (indicating multiple CCs / BWPs using a common MAC CE / DCI) is configured for the UE to update / indicate the (unified) TCI state (ID) using the MAC CE / DCI. The first CC list includes a list (first CC list #1) including CC #1 (BWP #1 in) and CC #2 (BWP #1 in), and a list (first CC list #2) including CC #3 (BWP #1 in).

[0275] In the example shown in Figure 15, a second CC list (indicating multiple CCs / BWPs using a common TCI status pool) is configured for the UE, which is used to configure a TCI status pool in the above-mentioned Case 2. The UE refers to a TCI status list configured for a specific CC among the multiple CCs included in the second CC list. In the example shown in Figure 15, the second CC list includes CC #1 (with BWP #1), CC #2 (with BWP #1), and CC #3 (with BWP #1).

[0276] In the example shown in Figure 15, the UE refers to the TCI status list in CC #1 (BWP #1 in CC #1) for CCs / BWPs in which the TCI status list is not configured (CC #2 (BWP #1 in CC #2) and CC #3 (BWP #1 in CC #3)) based on the second CC list. In other words, for CCs / BWPs in which the TCI status list is not configured, the UE determines the TCI status from the TCI status list of the CC / BWP in which the TCI status list is configured.

[0277] In the example shown in Figure 15, the UE is instructed by the MAC CE / DCI of the TCI state IDs (here, TCI state #2 in the TCI state list for CC #1) for CC #1 (BWP #1 in CC #1) and CC #2 (BWP #1 in CC #1) based on the first CC list. For example, when the UE receives a MAC CE / DCI indicating a TCI state for one CC in the first CC list, the UE may apply the TCI state indicated by the MAC CE / DCI to the other CCs in the first CC list. Also, the UE is instructed by the MAC CE / DCI of the TCI state ID (here, TCI state #4 in the TCI state list for CC #1) for CC #3 (BWP #1 in CC #3).

[0278] 15, the first CC list and the second CC list indicate different CCs (i.e., include different combinations of CCs), but the present invention is not limited to this. The first CC list and the second CC list may indicate the same CC.

[0279] In addition, at least one of the first CC list and the second CC list may be set in plural numbers. In the example shown in Fig. 15, plural first CC lists are set and one second CC list is set.

[0280] Furthermore, the indication of the TCI state IDs in CC #1 (BWP #1 therein) and CC #2 (BWP #1 therein) and the indication of the TCI state ID in CC #3 (BWP #1 therein) may be performed by separate MAC CE / DCIs, or may be performed by a common MAC CE / DCI.

[0281] In addition, when a plurality of first CC lists are configured and a TCI state (ID) is indicated using MAC CE / DCI in at least one CC / BWP included in a list among the plurality of lists, the UE may apply the indicated TCI state (ID) to a plurality of (e.g., all) CCs / BWPs included in the list. The UE may apply the TCI state separately for each of the plurality of lists.

[0282] When a first CC list covering all CCs / BWPs is configured, the UE may determine / assume / expect that the TCI status (ID) is indicated using MAC CE / DCI for each CC / BWP.

[0283] Different CC lists may not contain the same CC / BWP.

[0284] The same CC list may contain BWPs / CCs corresponding to different settings / instructions, such as settings / instructions for (M, N)=1 (settings / instructions specified in Rel. 17) and settings / instructions for (M, N)>1 (settings / instructions specified in Rel. 18 and later).

[0285] All BWPs / CCs included in the same CC list may correspond to the same setting / instruction, which may be, for example, either the setting / instruction for (M, N)=1 (setting / instruction specified in Rel. 17) or the setting / instruction for (M, N)>1 (setting / instruction specified in Rel. 18 or later).

[0286] The same CC list may include BWP / CCs corresponding to different TCI state modes, such as a joint TCI state mode and a separate TCI state mode.

[0287] All BWPs / CCs included in the same CC list may be BWPs / CCs corresponding to the same TCI state mode, which may be, for example, either a joint TCI state mode or a separate TCI state mode.

[0288] In addition, in the above case 2 (in at least one of aspects 1-2-A and 1-2-B), the maximum number of CCs for which the TCI status pool is set among multiple (e.g., all) CCs included in the CC list may be a specific number (e.g., one).

[0289] Also, for the UE, the existing / new / common / separate CC lists for the M and / or N TCI state IDs may be updated / activated.

[0290] According to the first embodiment described above, even when at least one of M and N is 2 or more, it is possible to appropriately determine the number of TCI states to be applied and set / activated.

[0291] Second Embodiment In a second embodiment, application of an indicated TCI state will be described.

[0292] The UE may be indicated multiple (e.g., two) TCI states using MAC CE / DCI (DCI with / without DL assignment).

[0293] The UE may be configured to share the indicated TCI state (Rel. 17 TCI state) across multiple DL / UL channels / signals.

[0294] The DL / UL channels / signals may be at least two channels / RSs described in the 0th embodiment.

[0295] The UE may follow at least one of the following aspects 2-1 to 2-4. Hereinafter, an example in which the number of indicated TCI states is two will be mainly described, but the number of indicated TCI states may be greater than two.

[0296] In addition, in at least one of the following aspects 2-1 to 2-4, an RRC parameter may be set to the UE indicating either that one TCI state is indicated or that two TCI states are indicated.

[0297] For example, the RRC parameter indicating that one TCI state is indicated (or applied) may be an RRC parameter (e.g., followUnifiedTCI-State-r17) indicating that one indicated TCI state in Rel. 17 is to be followed. The RRC parameter may be set for each configuration of a specific resource (e.g., CORESET).

[0298] For example, the RRC parameter indicating that one TCI state is indicated (or applied) or two TCI states are indicated may be an RRC parameter (e.g., followUnifiedTCI-State-r17 / followTwoUnifiedTCI-State-r18) indicating that one or two indicated TCI states are to be followed in Rel. 17 / 18. The RRC parameter may be set for each configuration of a specific resource (e.g., CORESET).

[0299] If an RRC parameter (e.g., followTwoUnifiedTCI-State-r18) that indicates following two indicated TCI states in Rel. 18 is configured, the UE may determine that two TCI states are indicated and apply both of the indicated TCI states.

[0300] In addition, the RRC parameter "followTwoUnifiedTCI-State-r18" may indicate one of the following values: applying the first TCI state of the two indicated TCI states (e.g., "first / 1st"), applying the second TCI state of the two indicated TCI states (e.g., "second / 2nd"), and applying both of the two indicated TCI states (e.g., "both").

[0301] In addition, instead of the RRC parameter "followTwoUnifiedTCI-State-r18", the UE may be configured to follow either the first TCI state of the two indicated TCI states (e.g., "follow1stUnifiedTCI-State-r18"), the second TCI state of the two indicated TCI states (e.g., "follow2ndUnifiedTCI-State-r18"), or both of the two indicated TCI states (e.g., "followBothUnifiedTCI-State-r18").

[0302] <<Aspect 2-1>> The UE may apply two indicated TCI states to DL / UL channel / RS.

[0303] The DL / UL channel / RS may be, for example, at least one of a PDSCH using multi-TRP, repeated transmission (repetition) of PDSCH / PDCCH / PUSCH / PUCCH using multi-TRP, SFN PDCCH / PDSCH, and an SRS (resource set) with codebook (CB) / non-codebook (NCB) usage.

[0304] The UE may decide which of the indicated TCI states to apply based on certain rules.

[0305] The specific rule may be, for example, a rule defined in an existing specification (Rel. 16).

[0306] For example, the UE may determine that the first of the two indicated TCI states is the TCI state associated with the first TCI state (defined in Rel. 16) and a CORESET pool index of a first value (e.g., 0), and the UE may determine that the second of the two indicated TCI states is the TCI state associated with the second TCI state (defined in Rel. 16) and a CORESET pool index of a second value (e.g., 1).

[0307] Also, for example, for an SRS resource set with codebook (CB) / non-codebook (NCB) usage, the UE may apply the first TCI state of the two indicated TCI states to the SRS resource set with a lower (or higher) SRS resource set ID, and the second TCI state to the SRS resource set with a higher (or lower) SRS resource set ID.

[0308] <<Aspect 2-2>> The UE may apply one of two indicated TCI states to a DL / UL channel / RS.

[0309] The DL / UL channel / RS may be, for example, at least one of PDSCH without multi-TRP, repeated transmission (repetition) of PDSCH / PDCCH / PUSCH / PUCCH without multi-TRP, PDCCH / PDSCH without an SFN scheme, and CSI-RS.

[0310] The UE may determine which of the indicated TCI states to apply based on a specific rule, which may be at least one of the following aspects 2-2-A to 2-2-C.

[0311] [Aspect 2-2-A] The specific rule may be, for example, a rule defined in the existing specifications (Rel. 16).

[0312] For example, the UE may determine that the first of the two indicated TCI states is the TCI state associated with the first TCI state (defined in Rel. 16) and a CORESET pool index of a first value (e.g., 0), and the UE may determine that the second of the two indicated TCI states is the TCI state associated with the second TCI state (defined in Rel. 16) and a CORESET pool index of a second value (e.g., 1).

[0313] The UE may determine which of the determined first / second TCI states to apply.

[0314] [Aspect 2-2-B] The UE may determine that a specific TCI state applies from among two indicated TCI states.

[0315] For example, the UE may decide to apply the first (or second) TCI state of two indicated TCI states.

[0316] [Aspect 2-2-C] The UE may be configured to apply one of two indicated TCI states using higher layer signaling (RRC / MAC CE).

[0317] The UE may decide which of the two indicated TCI states to apply based on configured higher layer parameters.

[0318] Figure 16 is a diagram showing an example of determining the TCI state according to aspect 2-1 / 2-2. In the example shown in Figure 16, a setting corresponding to CORESET #1 and a setting corresponding to CORESET #2 are configured as CORESET settings for the UE. The setting corresponding to CORESET #1 includes followUnifiedTCI-State-r17 and parameters for setting SFN scheme A (SFN scheme A), and the setting corresponding to CORESET #2 includes followUnifiedTCI-State-r17. In addition, two TCI states (TCI #1 and TCI #2) are indicated to the UE.

[0319] In the example shown in Figure 16, the UE determines that two TCI states are applicable to the SFN scheme for CORESET #1 and determines to apply two indicated TCI states (TCI #1 and TCI #2). Also, the UE determines to apply a specific TCI state (TCI #1 in the example of Figure 16) among the two indicated TCI states for CORESET #2.

[0320] In the example shown in Figure 16, the determination of the application of the TCI state based on the setting of CORESET is shown, but it can also be applied as appropriate to the setting of specific DL / UL channels / RSs / resources / resources other than CORESET (for example, the DL / UL channels / RSs described in the above-mentioned embodiment 0).

[0321] <<Aspect 2-3>> The UE may determine not to apply two indicated TCI states to multiple (e.g., all) DL / UL channels / RSs to which the indicated TCI states (common TCI states) are applicable.

[0322] For each CORESET / resource / resource set / channel / RS configuration for DL / UL channels / RSs that can share the Rel. 17 indicated TCI state, the UE may be configured to apply one indicated TCI state (e.g., apply the indicated TCI state in Rel. 17) or multiple (two) indicated TCI states (e.g., apply the indicated TCI state in Rel. 18 or later).

[0323] The DL / UL channels / RS may be at least two of the DL / UL channels / RS described in the above-mentioned 0th embodiment.

[0324] The UE may be configured to apply multiple (two) indicated TCI states for channels / RSs where multiple (two) TCI states are applicable, for example, using the RRC parameter "followTwoUnifiedTCI-State-r18".

[0325] The channel / RS to which the multiple (two) TCI states can be applied may be, for example, at least one of PDSCH using multi-TRP, repeated transmission (repetition) of PDSCH / PDCCH / PUSCH / PUCCH using multi-TRP, SFN PDCCH / PDSCH, and SRS (resource set) with codebook (CB) / non-codebook (NCB) usage.

[0326] The UE may be configured to apply one indicated TCI state for channels / RSs for which one (only) TCI state is applicable, for example, using the RRC parameter "followUnifiedTCI-State-r17".

[0327] The channel / RS to which the one (only) TCI state can be applied may be, for example, at least one of PDSCH without multi-TRP, repeated transmission (repetition) of PDSCH / PDCCH / PUSCH / PUCCH without multi-TRP, PDCCH / PDSCH without an SFN scheme, and CSI-RS.

[0328] When two TCI states are indicated for a channel / RS configured to apply one indicated TCI state, the UE may determine not to apply either of the two indicated TCI states. Alternatively, when two TCI states are indicated for a channel / RS configured to apply one indicated TCI state, the UE may determine to apply either of the two indicated TCI states.

[0329] Furthermore, the UE does not need to assume / expect that in different CORESET configurations, a parameter indicating the application of multiple (two) indicated TCI states and a parameter indicating the application of one indicated TCI state are respectively configured.

[0330] In this case, the UE may determine which of the two indicated TCI states to apply in accordance with at least one of the above-mentioned aspects 2-2-A to 2-2-C. Alternatively, the UE may determine which of the two indicated TCI states to apply in accordance with the following aspect 2-4.

[0331] Figure 17 is a diagram showing an example of determining a TCI state according to aspect 2-3. In the example shown in Figure 17, a setting corresponding to CORESET #1 and a setting corresponding to CORESET #2 are configured as CORESET settings for a UE. The setting corresponding to CORESET #1 includes followTwoUnifiedTCI-State-r18 and parameters for setting SFN scheme A (SFN scheme A), and the setting corresponding to CORESET #2 includes followUnifiedTCI-State-r17. In addition, two TCI states (TCI #1 and TCI #2) are indicated to the UE.

[0332] In the example shown in Figure 17, the UE determines that two TCI states are applicable to the SFN scheme for CORESET #1 and determines to apply the two indicated TCI states (TCI #1 and TCI #2). The UE also determines that neither of the two indicated TCI states applies for CORESET #2. In this case, the application of the already applied / indicated TCI state (TCI #5 in Figure 17) is maintained, and the TCI state is not updated.

[0333] In the example shown in Figure 17, the determination of the application of the TCI state based on the setting of CORESET is shown, but it can also be applied as appropriate to the setting of specific DL / UL channels / RSs / resources / resources other than CORESET (for example, the DL / UL channels / RSs described in the above-mentioned embodiment 0).

[0334] <<Aspect 2-4>> The UE may be configured with an RRC parameter indicating which of the two indicated TCI states to apply, or whether to apply both.

[0335] For example, the above-mentioned "followTwoUnifiedTCI-State-r18" may be used as the RRC parameter.

[0336] The RRC parameter may indicate one of a first TCI state, a second TCI state, or both the first TCI state and the second TCI state.

[0337] When two TCI states are indicated using MAC CE / DCI, the UE may apply the RRC parameters to determine the TCI state.

[0338] For example, when the RRC parameter indicates a first TCI state, the UE may determine to apply the first TCI state of the two indicated TCI states.

[0339] For example, when the RRC parameter indicates a second TCI state, the UE may determine to apply the second TCI state of the two indicated TCI states.

[0340] For example, when the RRC parameter indicates both a first TCI state and a second TCI state, the UE may determine that both of the two indicated TCI states apply.

[0341] Figure 18 is a diagram showing an example of determining a TCI state according to aspect 2-4. In the example shown in Figure 18, a setting corresponding to CORESET #1 and a setting corresponding to CORESET #2 are configured as CORESET settings for a UE. The setting corresponding to CORESET #1 includes followBothUnifiedTCI-State-r18 and parameters for setting SFN scheme A (SFN scheme A), and the setting corresponding to CORESET #2 includes follow2ndUnifiedTCI-State-r18. In addition, two TCI states (TCI #1 and TCI #2) are indicated to the UE.

[0342] In the example shown in Figure 18, the UE determines that two TCI states are applicable to the SFN scheme and determines to apply two indicated TCI states (TCI #1 and TCI #2) for CORESET #1. In this case, "followBothUnifiedTCI-State-r18" may be a parameter indicating the application of both the first TCI state and the second TCI state.

[0343] Furthermore, the UE determines to apply one TCI state (TCI #2 in FIG. 18 ) for CORESET #2 based on the instruction of follow2ndUnifiedTCI-State-r18 included in the configuration of CORESET #2. At this time, "follow2ndUnifiedTCI-State-r18" may be a parameter indicating the application of the second TCI state.

[0344] In the example shown in Figure 18, the determination of the application of the TCI state based on the setting of CORESET is shown, but it can also be applied as appropriate to the setting of specific DL / UL channels / RSs / resources / resources other than CORESET (for example, the DL / UL channels / RSs described in the above-mentioned 0th embodiment).

[0345] According to the second embodiment described above, one or more designated TCI states can be appropriately applied to each channel / RS.

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

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

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

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

[0350] In joint ACK / NACK feedback, ACK / NACK for PDSCH transmitted from each of a certain TRP is transmitted to that TRP using a certain PUCCH resource, and ACK / NACK for PDSCH transmitted from each of another TRP is transmitted to that other TRP using a different PUCCH resource (see Figure 19B).

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

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

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

[0354] Therefore, in the third embodiment, a method for configuring PUCCH resources when multi-TRP is used and a common TCI state is indicated will be described.

[0355] The UE may determine the PUCCH resource according to at least one of the following aspects 3-1 and 3-2.

[0356] <<Aspect 3-1>> A PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be configured for a UE for each TRP / TCI state.

[0357] The UE may determine the PUCCH resource corresponding to the TRP / TCI state based on the settings for each TRP / TCI state and transmit the HARQ-ACK.

[0358] 20 is a diagram illustrating an example of a method for configuring PUCCH resources according to aspect 3-1. In the example shown in FIG. 20, a PUCCH resource set corresponding to a first TRP / TCI state and a PUCCH resource set corresponding to a second TRP / TCI state are configured for a UE.

[0359] A maximum of a first number (e.g., four) of PUCCH resource sets corresponding to each TRP / TCI state may be configurable. A maximum of a second number (e.g., eight) of PUCCH resources within each PUCCH resource set may be configurable. The UE selects one PUCCH resource set from the configured PUCCH resource sets based on the payload size (number of bits) of the UCI. In the example shown in Figure 20, if the number of bits of the UCI is equal to or less than N0 (e.g., 2), the UE determines to use the first PUCCH resource set. Also, in the example shown in Figure 20, if the number of bits of the UCI is greater than N0 and equal to or less than N1, the UE determines to use the second PUCCH resource set.

[0360] In the example shown in FIG. 20, the UE determines the PUCCH resource set / PUCCH resource corresponding to the TRP / TCI state based on the settings for each TRP / TCI state.

[0361] Among the settings for each TRP / TCI state, the setting of the PUCCH resource set corresponding to the first (or second) TRP / TCI state may use the setting of the PUCCH resource set specified in existing specifications (e.g., Rel. 15-17). Alternatively, among the settings for each TRP / TCI state, the setting of the PUCCH resource set corresponding to the first (or second) TRP / TCI state may use the setting of the PUCCH resource set newly specified (e.g., in Rel. 18 or later).

[0362] Furthermore, among the settings for each TRP / TCI state, the setting of the PUCCH resource set corresponding to the second (or first) TRP / TCI state may utilize the setting of a PUCCH resource set that is newly defined (for example, in Rel. 18 or later).

[0363] <<Aspect 3-2>> A PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) common to each TRP / TCI state may be configured for the UE.

[0364] One PUCCH resource may be associated with one TRP / TCI state. The UE may be indicated the PUCCH resource associated with one TRP / TCI state. Each PUCCH resource may be independently associated with a TRP / TCI state.

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

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

[0367] The beam indication feature for each PUCCH resource group defined in Rel. 16 may be used to associate TRP / TCI states with PUCCH resources.

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

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

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

[0371] Figure 21 is a diagram showing an example of a method for configuring PUCCH resources according to aspect 3-2. In the example shown in Figure 21, a PUCCH resource set common to each TRP / TCI state is configured for a UE. The configuration of the PUCCH resource set and PUCCH resources is the same as in the example shown in Figure 20.

[0372] In the example shown in Figure 21, the UE determines the PUCCH resources corresponding to the TRP / TCI states based on the configuration of a PUCCH resource set common to each TRP / TCI state. In the example shown in Figure 21, among the PUCCH resources included in the PUCCH resource set, PUCCH resources with PUCCH resource indicators (PRI) of "000" to "011" are associated with the first TRP / TCI state, and PUCCH resources with PRIs of "100" to "111" are associated with the second TRP / TCI state. The UE determines the PUCCH resources associated with each TRP / TCI state based on this association.

[0373] The common setting for each TRP / TCI state may be the PUCCH resource set setting defined in existing specifications (e.g., Rel. 15-17). Alternatively, the common setting for each TRP / TCI state may be the PUCCH resource set setting defined anew (e.g., in Rel. 18 or later).

[0374] According to aspect 3-2, PUCCH resource selection using PRI / control channel element (CCE) index can be used to indicate joint TCI status / separate (UL) TCI status of PUCCH resources.

[0375] <<First Modification of Aspect 3-2>> A PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) common to each TRP / TCI state may be configured for the UE.

[0376] One PUCCH resource may be associated with one or more (two) TRP / TCI states. The UE may be indicated which PUCCH resources are associated with one or more (two) TRP / TCI states.

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

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

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

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

[0381] Figure 22 is a diagram showing an example of a method for configuring PUCCH resources according to Variation 1 of Aspect 3-2. In the example shown in Figure 22, a PUCCH resource set common to each TRP / TCI state is configured for a UE. The configuration of the PUCCH resource set and the PUCCH resource is the same as the example shown in Figure 20.

[0382] In the example shown in FIG. 22, the UE determines the PUCCH resource corresponding to the TRP / TCI state based on the configuration of the PUCCH resource set common to each TRP / TCI state.

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

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

[0385] The common setting for each TRP / TCI state may be the PUCCH resource set setting defined in existing specifications (e.g., Rel. 15-17). Alternatively, the common setting for each TRP / TCI state may be the PUCCH resource set setting defined anew (e.g., in Rel. 18 or later).

[0386] According to the first modification of aspect 3-2, the joint TCI state / separate (UL) TCI state of the PUCCH resource can be indicated using RRC / MAC CE / DCI / specific rules.

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

[0388] <<Second Modification of Aspect 3-2>> A PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) common to each TRP / TCI state may be configured for the UE.

[0389] One PUCCH resource may be associated with one or more (two) TRP / TCI states. The UE may be indicated which PUCCH resources are associated with one or more (two) TRP / TCI states.

[0390] According to the second modification of aspect 3-2, the joint TCI state / separate (UL) TCI state of the PUCCH resource can be indicated using RRC / MAC CE / DCI / specific rules.

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

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

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

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

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

[0396] Figure 23 is a diagram showing an example of a method for configuring PUCCH resources according to Variation 2 of Aspect 3-2. In the example shown in Figure 23, a PUCCH resource set common to each TRP / TCI state is configured for the UE. The configuration of the PUCCH resource set and PUCCH resources is the same as the example shown in Figure 20.

[0397] In the example shown in FIG. 23, the UE determines the PUCCH resource corresponding to the TRP / TCI state based on the configuration of the PUCCH resource set common to each TRP / TCI state.

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

[0399] The common setting for each TRP / TCI state may be the PUCCH resource set setting defined in existing specifications (e.g., Rel. 15-17). Alternatively, the common setting for each TRP / TCI state may be the PUCCH resource set setting defined anew (e.g., in Rel. 18 or later).

[0400] According to the third embodiment described above, even when multi-TRP is used and a common TCI state is indicated, it is possible to appropriately determine PUCCH resources.

[0401] Note that the third embodiment may be applied only when separate ACK / NACK feedback is configured in multi-DCI-based multi-TRP. In joint ACK / NACK feedback or single-TRP, when the network (base station) wants to update the joint TCI state / separate (UL) TCI state of the PUCCH, MAC CE / DCI-based joint TCI state / separate (UL) TCI state update (the update method specified in Rel. 17) may be used for the indicated TCI state.

[0402] The third embodiment may also be applied when joint / separate ACK / NACK feedback is configured in multi-DCI-based multi-TRP. In single-DCI-based multi-TRP, if the network (base station) wants to update the joint TCI state / separate (UL) TCI state of the PUCCH, MAC CE / DCI-based joint TCI state / separate (UL) TCI state update (the update method specified in Rel. 17) may be used for the indicated TCI state.

[0403] Furthermore, the third embodiment may be applied to at least one of when a multi-DCI-based multi-TRP is configured / indicated and when a single-DCI-based multi-TRP is configured / indicated. Note that when a single-DCI-based multi-TRP is configured / indicated and the network (base station) wants to update the joint TCI state / separate (UL) TCI state of the PUCCH, the MAC CE / DCI-based joint TCI state / separate (UL) TCI state update (the update method specified in Rel. 17) may be used for the indicated TCI state.

[0404] The third embodiment may also be applied when a specific upper layer parameter is configured, i.e., when a single TRP is configured.

[0405] <Modifications> Each embodiment / aspect / option of the present disclosure may be supported in intra-cell / inter-cell beam direction.

[0406] In each embodiment / aspect / option of the present disclosure, a TRP-specific (additional) Transmitted Precoding Matrix Indicator (TPMI) field / SRI field for a PUSCH using multiple TRPs in Rel. 17 may be used.

[0407] <Other Embodiments> A higher layer parameter (RRC IE) / UE capability corresponding to a function (feature) in at least one of the above embodiments may be defined. The UE capability may indicate that the function is supported.

[0408] A UE configured with higher layer parameters corresponding to the function (enabling the function) may perform the function. It may also be specified that "a UE not configured with higher layer parameters corresponding to the function shall not perform the function (for example, in accordance with Rel. 15 / 16)."

[0409] A UE that reports a UE capability indicating that it supports the function may perform the function. It may also be specified that a UE that does not report a UE capability indicating that it supports the function shall not perform the function (e.g., in accordance with Rel. 15 / 16).

[0410] If the UE reports a UE capability indicating that it supports the function and the corresponding higher layer parameters are configured, the UE may perform the function. It may also be specified that "if the UE does not report a UE capability indicating that it supports the function or if the corresponding higher layer parameters are not configured, the UE shall not perform the function (e.g., in accordance with Rel. 15 / 16)."

[0411] The UE capability may indicate whether the UE supports this feature.

[0412] The function may be the application of common / uniform TCI conditions.

[0413] The function may be the application of joint DL / UL TCI conditions.

[0414] The function may be application of separate DL / UL TCI conditions.

[0415] UE capability may be defined as whether it supports joint DL / UL TCI states (modes).

[0416] UE capability may be defined as whether it supports the M=1, N=2 joint DL / UL TCI state (mode).

[0417] UE capability may be defined as whether it supports the M=2, N=1 joint DL / UL TCI state (mode).

[0418] UE capability may be defined as whether it supports M=2, N=2 joint DL / UL TCI states (modes).

[0419] UE capability may be defined as whether or not it supports separate DL / UL TCI modes.

[0420] UE capability may be defined as whether it supports separate DL / UL TCI state with M=1, N=2.

[0421] UE capability may be defined as whether it supports separate DL / UL TCI state with M=2, N=1.

[0422] UE capability may be defined as whether it supports separate DL / UL TCI states with M=2 and N=2.

[0423] The UE capability may be defined in terms of the reported number (total number) of TCI states configured in RRC signaling for the first / second TCI state.

[0424] The UE capability may be defined in terms of the reported number (total number) of TCI states activated in the MAC CE for the first / second TCI state.

[0425] UE capability may be defined as whether it supports a common TCI state for single DCI-based multi-TRP.

[0426] UE capability may be defined as whether or not it supports common TCI state for multi-DCI based multi-TRP.

[0427] The UE capability may be defined as whether it supports a common TCI state for single DCI-based multi-TRP and a common TCI state for multi-DCI-based multi-TRP.

[0428] UE capability may be defined as whether or not it supports at least one of the methods described in the first embodiment above and at least one of the methods described in the fourth embodiment above.

[0429] UE capability may be defined as whether it supports separate BATs in different TRPs (CORESET pool indices).

[0430] According to the above and other embodiments, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0474] The transceiver unit 120 may transmit instruction information of multiple transmission configuration indication (TCI) states (multiple common TCI states) to be applied to multiple signals (channels / RSs). The control unit 110 may use the instruction information to instruct that the multiple TCI states be applied to signals using multiple transmission / reception points (multi-TRPs). Each of the multiple TCI states may be a TCI state (joint TCI state) applied to both a downlink (DL) signal and an uplink (UL) signal, or a TCI state applied to a DL signal and a TCI state (separate TCI state) applied to a UL signal (first and second embodiments).

[0475] The transceiver 120 may transmit configuration information (e.g., PUCCH configuration / PUCCH resource set configuration) regarding a physical uplink control channel (PUCCH) resource set corresponding to one or more transmission configuration indication (TCI) states. The controller 110 may use the configuration information to indicate a PUCCH resource corresponding to each TCI state (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0493] The transceiver unit 220 may receive instruction information of multiple transmission configuration indication (TCI) states (multiple common TCI states) to be applied to multiple signals (channels / RSs). The control unit 210 may apply the multiple TCI states to signals using multiple transmission / reception points (multi-TRP) based on the instruction information. Each of the multiple TCI states may be a TCI state applied to both a downlink (DL) signal and an uplink (UL) signal (joint TCI state), or a TCI state applied to a DL signal and a TCI state applied to a UL signal (separate TCI state) (first and second embodiments).

[0494] The transceiver 220 may receive a list (first / second list) of cells to which the instruction information applies. Different lists may not include the same cells (first embodiment).

[0495] The control unit 210 may also determine to apply one of the multiple TCI states to signals other than signals that use the multiple transmission / reception points (e.g., channels / RSs that use Shintsuru TRP) (second embodiment).

[0496] The transceiver 220 may receive at least one of first setting information (e.g., followUnifiedTCI-State-r17 / follow1stUnifiedTCI-State-r18 / follow2ndUnifiedTCI-State-r18) that sets application of one TCI state among the plurality of TCI states, and second setting information (e.g., followTwoUnifiedTCI-State-r18 / followBothUnifiedTCI-State-r18) that sets application of the plurality of TCI states. The controller 210 may control application of at least one of the plurality of TCI states based on at least one of the first setting information and the second setting information (second embodiment).

[0497] The transceiver 220 may receive configuration information (e.g., PUCCH configuration / PUCCH resource set configuration) regarding a physical uplink control channel (PUCCH) resource set corresponding to one or more transmission configuration indication (TCI) states (TRPs). The controller 210 may determine a PUCCH resource corresponding to each TCI state based on the configuration information (third embodiment).

[0498] The configuration information may be a configuration of a PUCCH resource set corresponding to one TCI state (TRP). The transceiver unit 220 may receive a plurality of pieces of the configuration information (third embodiment).

[0499] The configuration information may be a configuration of a PUCCH resource set common to a plurality of TCI states (TRPs) (third embodiment).

[0500] The transceiver 220 may receive information (flag / indicator) regarding the association between the PUCCH resource and the TCI state index included in the configuration information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a receiving unit for receiving indication information of a plurality of transmission configuration indication (TCI) states to be applied to a plurality of signals, and a Radio Resource Control (RRC) parameter indicating an applied TCI state among the plurality of TCI states; a control unit that determines whether to apply the plurality of TCI states or to apply a first or second TCI state of the plurality of TCI states based on the RRC parameters.

2. 2. The terminal according to claim 1, wherein the control unit determines to apply the plurality of TCI states for a first control resource set (CORESET) when a first RRC parameter indicates application of the plurality of TCI states, and determines to apply the first or second TCI state for a second CORESET when a second RRC parameter indicates application of the first or second TCI state.

3. The receiving unit receives configuration information regarding physical uplink control channel (PUCCH) resource sets corresponding to the plurality of TCI states and information indicating TCI states associated with PUCCH resources included in the PUCCH resource sets; 2. The terminal according to claim 1, wherein the control unit determines to apply the plurality of TCI states to one or more specific PUCCH resources based on the setting information and the information indicating the TCI state, and determines to apply any one TCI state of the plurality of TCI states to PUCCH resources other than the one or more specific PUCCH resources.

4. The terminal described in claim 3, wherein the one or more specific PUCCH resources to which the multiple TCI states apply are used for at least one of repeated transmission of PUCCH to multiple transmission / reception points (TRPs) and simultaneous transmission of PUCCH using multiple panels.

5. receiving an indication of a plurality of transmission configuration indication (TCI) states to be applied to a plurality of signals, and a Radio Resource Control (RRC) parameter indicating an applicable TCI state from the plurality of TCI states; and determining, based on the RRC parameters, whether to apply the plurality of TCI states or a first or second TCI state among the plurality of TCI states.

6. a transmitter that transmits indication information of a plurality of transmission configuration indication (TCI) states to be applied to a plurality of signals, and a Radio Resource Control (RRC) parameter indicating an applicable TCI state among the plurality of TCI states; a control unit that uses the RRC parameter to instruct whether to apply the plurality of TCI states or to apply a first or second TCI state among the plurality of TCI states.

7. A system having a terminal and a base station, The terminal includes a receiving unit that receives indication information of a plurality of transmission configuration indication (TCI) states applied to a plurality of signals and a Radio Resource Control (RRC) parameter that indicates an applied TCI state among the plurality of TCI states; a control unit that determines whether to apply the plurality of TCI states or to apply a first or second TCI state among the plurality of TCI states based on the RRC parameter; The base station includes a transmitter that transmits the instruction information and the RRC parameters; a control unit that uses the RRC parameters to instruct whether to apply the plurality of TCI states or the first or second TCI state.